Thanks. It’s not a dealbreaker, just a preference. I can live with it for now.
GrapheneOS does not recommend enabling Developer options
1 Like
Ah? What’s the reason?
More attack surface?
Android has extensive testing for the defaults but most developer options are essentially untested for production use and often cause issues. Many sound like they may be things you may want etc but are actually a bad idea and that’s often why they’re still only in developer options.
1 Like
11 Likes
Turning out to be a busy year end season for the GrapheneOS team, it would seem.
According to Ars Technica, the shifting releases may be due to how Google wants to break up the way they update Android going forward. My hope is that they land on the new cadence and continue consistently.
3 Likes
I rather wish Google just came out and explain the new way of the releases so we don’t have to keep speculating on what and why and the potential of them not releasing it at all.
But yes, I hope so too.
2 Likes
Really great to see them return to the old cadence. Hopefully this will continue.
2 Likes
I’m glad Android 16 QPR2 source came quickly after its rollout to Pixel devices. I’m excited to see the Linux Development Environment with GUI apps, though there doesn’t appear to be graphics acceleration enabled for now.
4 Likes
wasn’t experimental linux support (in developer options) since Android 15?
nvm I see what you are talking about, that’s amazing and the linux brought on Android 15 does have graphics acceleration so the UI would actually use Hardware acceleration to my understanding in that case.
But if not, I hope at some point it gets enabled.
And and then we wait for Steam for ARM and we’re golden!
P.S. I remember telling my friend that if Steam for ARM comes and we can run it on Android I am definitely switching to a gaming phone (eg. Redmagic) for that purpose and play games this way.
3 Likes