Conversation

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

@GrapheneOS

Jun 5

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

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

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.

Replying to

I'll get back home in a few minutes and screen record it for you if you want to see just to confirm

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.

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.

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.

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

Replying to

Many phones don't have the Camera2 API so if you wanted to use Camera2, you still need a fallback Camera1 implementation. That's why most apps didn't bother using Camera2. That's mostly on SoC vendors and OEMs, but also on Google for not REQUIRING providing it in the CDD/CTS.

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.

Daniel Micay

@DanielMicay

Replying to

@MaxWinebach

Based on source.android.com/compatibility/ and how the CTS is implemented, I don't think it's mandatory even for Android 12. CameraX has a fallback implementation based on Camera1 so we don't have to worry about it in our camera app, similar to it handling most widespread Camera2 bugs.

source.android.com

Android 12 Compatibility Definition | Android Open Source Project

10:17 PM · Jul 30, 2022Twitter Web App

Replying to

and

Google is also 100% capable of saying if you implement HDR, Night, Portrait, Face Retouch or Auto modes for your OEM camera app then you MUST implement them via Camera2/CameraX extensions and that if you have zoom-based multi-camera you MUST provide it via CONTROL_ZOOM_RATIO too.