This is Zach's CameraX info app. It's cool. Google's bad at supporting the standard it pushes Android devs to use.
Samsung is, actually, the only company fully using it and using it well.
Quote Tweet
8
13
202
Conversation
For example this is what apps can access with cameraX API on the OnePlus 10 Pro. Sure camera2 might give more access, but Google is telling devs to use CameraX now so that's what's relevant.
Also only whatever default FPS is on the camera, which is likely 24 fps.
1
1
56
This is what EXCELLENT camera support looks like from an OEM. Apps can access all 3 cameras through a single logical camera, and full access to all camera extensions providing native auto, HDR, bokeh, face retouching, and night mode to any dev who wants it. Great job, Samsung.
10
7
152
Replying to
We have a comparison at twitter.com/GrapheneOS/sta. Compared to Pixels, Samsung phones have CameraX extensions and ZSL support. Pixels have proper multi-camera support via CONTROL_ZOOM_RATIO where third party apps can use the automatic switching between ultrawide, normal, telephoto.
Quote Tweet
GrapheneOS Camera device specific features:
1) Electronic Image Stabilization (EIS)
2) using ultrawide/telephoto cameras via zooming
3) image capture during video recording
4) Continuous Auto Focus (CAF)
5) Zero Shutter Lag (ZSL)
6) HDR, Night, Portrait, Face Retouch, Auto modes
Show this thread
2
8
Replying to
Are you sure Samsung phones don’t have zoom? My S22 Ultra can go from 0.5x to 10x but not beyond in graphene camera
3
5
Replying to
Nice, that means our camera app has the entire feature set on the most recent Samsung devices now. You can also enable ZSL in the advanced options but it's hard to see the difference on high end devices. It will make a difference when we add burst mode which is planned.
1
1
3
I think the main reason Pixels don't have ZSL support is because they provide HDR+ via the regular API since the Pixel 2. It substantially predates Camera2/CameraX extensions and is part of why they've been in no rush to implement those, since you have HDR+ on Pixels without it.
2
1
5
They also used part of the ZSL API in a strange way on Pixels to disable/enable HDR+. ZSL enabled means HDR+ is enabled and ZSL disabled means HDR+ is disabled. CameraX uses this on Pixel 2 / Pixel 3 to toggle HDR+ based on Latency vs. Quality mode since it was slow on those.
1
5
It's possible that has something to do with why Pixels don't implement the standard Camera2 ZSL API. You get HDR+ automatically when you use the camera API in a reasonable way and it'd be harder to implement the ZSL APIs while using HDR+ so that's probably why it's missing.
1
4
So really, Pixels do have HDR support for other apps already but it's the normal camera mode. ZSL is not available when using Camera2/CameraX extensions so it makes sense that it's missing on Pixels since normal camera mode is basically a very good HDR extension since Pixel 2.