Conversation

Replying to

With HDR and auto extensions it doesn't seem worth it

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

Replying to

I actually noticed the Pixel 4a/5/5a had worse image quality in apps than Pixel 4/4XL, so I'm not sure that change was for the best

1

Replying to

Only difference is that the preview on Pixel 4a, 4a (5G), 5, 6, 6 Pro and 6a uses HDRnet. It doesn't impact the captured images. Problem is that at least on 4a and 5th gen devices (4a (5G), 5, 5a), the preview misleads you into thinking there will be less noise than you'll get.

1

2

Replying to

and

HDRnet is a neural net trained on captured HDR+ images that's able to peek back at previous frames and emulate the look of HDR+. It does improve quality for real because it adds information from previous frames, but not as much as HDR+. Issue is they trained it on Google Camera.

1

1

Replying to

and

And the HDR+ they are currently providing to other apps, at least on 2nd, 3rd, 4th and 5th gen is not as good as the HDR+ in Google Camera. Note we have not tested how it compares on Pixel 6. It's possible the gap is smaller now since they'd have had to redo it for Pixel 6.

1

1

Replying to

and

Also worth noting: Google Camera is entirely based on the normal Camera2 API. Other apps can use the same APIs. They use Camera2 scene modes for Portrait, Night, etc. but they do all the actual processing themselves including for HDR+ with Google Camera.

1

1

Replying to

and

Production releases with Google Camera are given direct access to the Qualcomm DSP and 4th gen Pixel Neural Core via a custom SELinux domain. Google Camera works fine without the custom domain but the processing takes a bit longer since it loses that hardware acceleration.

1

1

Replying to

and

On GrapheneOS, we remove the custom domain since it's barely noticeable on modern devices and we don't want Google apps having privileged access. Google Camera still works fine for us. We could allow it to use that but removing is part of the whole sandboxed Google Play approach.

1

2

Replying to

and

Pixel 6 got rid of the custom domain for Google Camera. They moved all of that stuff into the OS via a vendor APEX with the camera HAL implementation. It's really inexplicable that they don't support all the Camera2 and CameraX extensions. They have 99% of the work done already.

1

1

Replying to

and

The reason the CameraX Night extension is missing is because the Pixel camera people wanted fancier extension support so they waited until that shipped via Camera2 extension API to support it. CameraX still has to finish implementing the advanced extension API. Bad coordination.

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

Replying to

and

And then the problem is that once CameraX ships that, which it has largely done now, Pixels still need to take advantage of it by shipping the 1 extension they provided for CameraX in addition to Camera2. It's frustrating for us Samsung has 5/5 CameraX extensions and they have 0.

1

1

Replying to

and

Most GrapheneOS Camera users are on GrapheneOS where none of the extensions are available since Pixels don't provide it yet. If Samsung had proper alternate OS support keeping hardware security features supported and published easy to use AOSP support we could support those...

1

2

Show replies