phnx

For our next release after 2025030800, we've added support for the Android 15 QPR2 Terminal for running other operating systems using hardware virtualization. It's currently only a terminal but Android is adding support for graphics and GPU acceleration for a future release.

Android has a greatly overhauled desktop mode on the way to replace the current primitive proof of concept in developer options. 6th gen Pixels added hardware-based virtualization support and 8th gen Pixels added USB-C DisplayPort alternate mode. It will all come together soon.

Overhauled desktop mode is already partially shipped as a disabled-by-default feature. Android enables some of it for the Pixel Tablet already but not Pixel phones. We plan to enable the same feature flags for phones too. Either way, it's an experimental developer option for now.

Beyond using a phone or tablet as a desktop by connecting a display, keyboard, mouse, etc. to the USB-C port, we want to eventually have support for GrapheneOS on laptops. There's currently no laptop close to meeting the hardware requirements we cover at https://grapheneos.org/faq#future-devices.

On Pixels, virtualization implemented based on pKVM (see https://source.android.com/docs/core/virtualization/security for how it's different from KVM) and CrosVM from extended with Android specific code. CrosVM is written in Rust so it fits in well with Android using Rust for new or rewritten low-level components.

This post is also available on social media platforms as a thread:

Bluesky: https://bsky.app/profile/grapheneos.org/post/3ljxaoabcds2j
Mastodon: https://grapheneos.social/@GrapheneOS/114132940314692519
X: https://x.com/GrapheneOS/status/1898742463277207630

ikariwths anyone?

The GrapheneOS community is world-wide, which means that people have a wide variety of sleep schedules. Also, people have various work and family responsibilities. Overall, while some questions may receive answers very quickly, it is arguably not a best practice to "bump" a question in less than 24 hours. This forum is not a real-time chat room. Those do exist for GrapheneOS (source).

phnx The pull request wasn't really adequate and we're going to work on an implementation ourselves rather than trying to get someone to make a completely different implementation than what they submitted.

cdflasdkesalkjfkdfkjsdajfd I'm not familiar on how play integrity checks works but I think it they are a workaround to bypass it GrapheneOS will to include it then let users to decide if use or not, specially now than apps, like revolut, are moving to block GrapheneOS and other custom ROMs.
If GrapheneOS cannot include it maybe can explain how auto compile a version of the software that includes it.

I don't expect the GrapheneOS developers will include any such tool--if only because it would need privileges, and thus would need to be carefully audited, and that's aside from whether the developers would want to take the project in that direction, which I suspect they don't. I also wouldn't expect the GrapheneOS developers to publish/maintain a guide on how to do something that they don't believe is in the interests of the project.

For whatever it might be worth, a GrapheneOS fork won't attest as being a legitimate GrapheneOS build. The exact details of how the UK Starling Bank is accepting GrapheneOS are unclear, but it is at least possible that the Starling app will work on genuine GrapheneOS builds but not on private builds.

Overall, spoofing integrity checks is probably doomed. It arguably makes sense to use the current time window to educate app developers in the direction of reasonable policies before unreasonable policies become further entrenched.

Everyone, nominate GrapheneOS as a beneficiary for Proton's 2024 Charity Fundraiser! It just takes a minute and you can do so here, just click on the purple "Tell us who to support" button near the upper middle of the page or click here. The Foundation being nominated will receive tens of thousands of USD. Share the link!

phnx dude you're a real hound, thanks for those links 👍

phnx These already required a reboot to kick in properly in many cases before Android 15.