Conversation

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
There's a lot of Google not supporting its own stuff on its own phones
Image
8
202
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
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
3
Replying to and
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
5
Replying to
Possible Samsung has decent processing for the normal camera mode in other apps. You could try comparing HDR and Camera modes in low light. It should be easy to see if HDR is actually doing better by reducing noise. Normal mode could just be doing it less aggressively though.
1
1
Replying to
Pixel 4a and later (it's strangely not available on the Pixel 4 and Pixel 4 XL) use the high quality preview toggle (disabled by default) to provide HDRnet for preview. CameraX uses this automatically. We haven't confirmed if video HDRnet is provided to other apps for Pixel 6.
2
1
Show replies
Replying to and
It made sense for Pixels to do it because there was no such thing as Camera2/CameraX extensions. They did it all the way back with the Pixel 2 when they added the Pixel Visual Core, which wasn't used by Google Camera, only other apps.
1
2
Replying to and
Pixel 3 had that too, then Pixel 4 moved to Pixel Neural Core also providing the AOSP neural net acceleration API. They moved to simply using the Qualcomm DSP after that point which is what Google Camera did all along. It partially used Pixel Neural Core but not Visual Core.
2