Conversation

Replying to
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.
Image
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.
Image
10
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
It's possible they added virtual zoom in the S22. We've had a ton of reports from Samsung users that they have all 5 CameraX extensions even on 2 year old phones but that multi-camera support isn't available. Interested to know if it is actually available on the newer phones.
2
1
Replying to
If they've finally shipped on the newer phones, that's incredibly good news for our camera app because the main complaint we've been getting is lack of multi-camera support on Samsung phones. Seems they must have shipped it in an update if it's working on them those now.
1
1
Replying to and
Most of the features people want beyond this require CameraX to be expanded with new APIs: video frame rate, H.264, AVIF/RAW for images, manual exposure control beyond exposure compensation slider, manual focus, etc. Some things we can do via Camera2Interop which we did with EIS.
1
1
Replying to and
I think we may be able to provide a fair bit of white balance control via Camera2Interop. It's only possible to do things which are set up when initializing the camera though. Can't currently use dynamic APIs like focus that aren't part of setting up camera use case in advance.
1
Replying to
Would you say with a lot of this stuff it's not really on app developers like Snapchat, Instagram and TikTok for having bad quality in their apps and it's a little bit on Google for providing half-assed or annoying APIs or OEMs not adding support
7
Replying to
Wait, it's still not required in CTS? I thought they added that in like Android 10. It's crazy they haven't yet, that feels like almost everything is on them then.
1
Show replies
Replying to and
There are also a massive amount of bugs with the Camera2 implementations across non-Pixel and devices (Samsung has a very good implementation on their newer devices though). That's another reason to use Camera1: Camera2 is often buggy overall and especially features like EIS.
1
2
Replying to and
We've found that many vendors are cheating on CTS certification. They are clearly failing many CTS tests, especially in areas like camera. Many of the mandatory camera tests can't possibly be passing and yet somehow they have a certified device allowing them to ship Google Play.
1
2
Show replies