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
If Samsung added that missing feature, our Secure Camera app would have the full feature set on Samsung devices. It's unfortunate they don't have it.
Very impractical to make a database of the virtual zoom range, camera ids and zoom levels to use per camera id for every phone.
It's also not currently possible to switch between the multiple cameras using CameraX without having support for this feature, since it can't be done manually yet. You can still switch manually on a device implementing this via the multi-camera API and CONTROL_ZOOM_RATIO.