Daniel Micay
Daniel Micay
Is it still an issue in Android 16 QPR1? There's a high chance it will be fixed in Android 16 QPR2. It's very likely not caused by anything GrapheneOS changes.
That doesn't indicate it's specific to GrapheneOS rather than an AOSP issue also impacting the stock Pixel OS too.
Don't use an unreliable 3rd party keyboard. We don't have a confirmation of if this is still an issue after Android 16 QPR1 though.
Any keyboard can support being used BFU via Direct Boot but it requires them to specifically add support for it. The built-in keyboard of course supports it.
@GenEmSec yes
> Any ETA for when this is planned to be addressed? How far out is QPR2 from us, or will you consider addressing the issue downstream if it's sufficiently far...
Device trees are not used for any devices anymore since AOSP doesn't provide those. Not sure what you mean by that. We're overloaded with a huge amount of work to...
I said there was a high chance it would be fixed in QPR2 if it's not already fixed in QPR1 because it's almost certainly an upstream bug and they're probably...