You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was an sepolicy change needed for the Pixel 6 / 6 Pro in order to allow the camera software to access the DSP for accelerated image processing. Before that, Google Camera on Pixel 6 was slow too (please see here: https://issuetracker.google.com/issues/227166806#comment8
Was that change incorporated in the Pixel 7? Has it been properly validated that it doesn't need some tweaking for the minor differences? Thanks.
The text was updated successfully, but these errors were encountered:
The sepolicy being referenced was intentionally removed by GrapheneOS to simply prevent it having privileged direct hardware access as attack surface reduction. Nothing is blocking it from using the hardware unprivileged at the cost of processing performance, it just does not have privileged direct access like it does on stock OS.
No plans to add this sepolicy back. Said issue will likely get fixed.
@Rubber-Duckie Full Tensor image processing functionality is available to Pixel Camera on GrapheneOS. Not sure why you're posting here, but you're completely wrong and misusing this as a discussion board.
Google Camera's processing speed is very slow on Pixel 7 / 7 Pro devices, especially, Portrait processing that take over a minute to process. Many people reported this issue on GOS forums: https://discuss.grapheneos.org/d/1815-google-camera-very-slow-portrait-mode-processing/25
There was an sepolicy change needed for the Pixel 6 / 6 Pro in order to allow the camera software to access the DSP for accelerated image processing. Before that, Google Camera on Pixel 6 was slow too (please see here: https://issuetracker.google.com/issues/227166806#comment8
Was that change incorporated in the Pixel 7? Has it been properly validated that it doesn't need some tweaking for the minor differences? Thanks.
The text was updated successfully, but these errors were encountered: