Conversation

Daniel Micay
@DanielMicay
twitter.com/DanielMicay/st This should all be figured out now. Expect to see GrapheneOS Pixel 5a support in the near future. Pixel 6 will be much harder to add than this. Ideally we'll get gotten memory tagging implemented for hardened_malloc beforehand since it'll likely have it.
Quote Tweet
Daniel Micay
@DanielMicay
Hoping that github.com/GrapheneOS/ker resolves the Pixel 5a audio issues. They moved to a different DAC in the Pixel 5a compared to the Pixel 4a (5G). Other than that, it's almost entirely the same hardware. I'm curious if it's actually substantially better than the previous one.
1
22
Daniel Micay
@DanielMicay
Replying to
@AlwaysCurious__
It's nearly the same as the Pixel 4a (5G) and to a slightly lesser extent the Pixel 5. It's way easier to add support for it than any past devices. Auditor / AttestationServer support was the straightforward first step and then the other usual things but way less work than usual.
1
Daniel Micay
@DanielMicay
Replying to
@DanielMicay
and
@AlwaysCurious__
The main difference is that they moved to a new DAC/amplifier so there's a new audio driver and it wasn't set up to be built into the kernel rather than as a dynamic kernel module. github.com/GrapheneOS/ker GrapheneOS builds all modules into the kernel and disables DKM support.
github.com
add missing configuration for in-tree build · GrapheneOS-Archive/kernel_google_barbet_techpack_au...
1