Official releases of GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
Pixel 4a (5G) and Pixel 5 are end-of-life and shouldn't be used anymore due to lack of security patches for firmware and drivers. We provide extended support for harm reduction.
Keyboard: add new implementation of multi-locale spell checking support to fix crashes and other issues
Sandboxed Google Play compatibility layer: add Android Auto support with the compatibility layer eliminating the need for most of the permissions and a permission menu with 4 toggles for granting the minimal special access required for wired Android Auto, wireless Android Auto, audio routing and phone calls
Settings: remove confusing mention of Android Auto from Connected devices screen
exempt non-app system processes from Sensors permission enforcement (fixes some issues including gpsd crashes)
fix Bluetooth auto-turn-off race condition to avoid crashes
work around upstream race condition bug in biometric service
disable support for pre-approving PackageInstaller sessions due to incompatibility with Network permission toggle
fix several upstream bugs in handling crash reports mainly to improve our user-facing crash reporting system
use GrapheneOS Widevine provisioning proxy by default
add settings for changing Widevine provisioning server
add configuration for setupdesign and setupcompat libraries to improve system UI theme
kernel (Pixel 8, Pixel 8 Pro, Generic 5.15): update to latest GKI LTS branch revision including update to 5.15.142
kernel (Generic 6.1): initial port of GrapheneOS changes for use with emulator builds
force disable network ADB in early boot to improve verified boot security (no user-facing change since it's currently disabled by default later in the boot process, but not robustly)
So is there Android auto support now? If so, is there a documentation that lists what data is and is not protected when using Android Auto with GrapheneOS as opposed to stock Pixel
Yes, it does support Android Auto on the latest release. The implementation works with four separate toggles allowing different kinds of access. A list of what the toggles give access to appear when you try to toggle them on. Documentation on Sandboxed Google Play's Android Auto implementation will also be added to the website in the future.
That's great to hear. Do you need the Android Auto app for that? I'm only asking because GrapheneOS is my first Android in a while and I have never used Android Auto before
Sandboxed Google Play could be ported to other OSes.
I would like to let you know that a ROM is Read Only Memory, which means unchangeable permanent storage. The area the Operating System is stored, is in fact a writeable drive, unlike a ROM. This means referring to GOS as a ROM makes no sense and as such should be called an aftermarket OS or alternative OS.
Damn , I have a 3a and a 4a I would like to make to permanent dedicated car phones. Would be great if android auto could be ported to the old ones to get some use of them.
I know , not supported and updated , but would make more sense to use an old GOS phone separate from the main phone rather than using the same for everything.
This is not a bad idea. However, why not just flash stock Android on that and use it solely for that purpose? Just a suggestion.
I mean, if you'll only use it for that, what's the harm, right?
I'm fine using OSM only, and my car comes with an android tablet as main display, so I thank God I have no need for AA.
Made a solution with rooted calyx and microG. Spotube and organic maps. Well I could have used stock however unsure what are passed on in between car and Google.
A yea, issue is of course that I would miss the GOS Google play implementation and GPS baseband isolation. As far as I know MicroG won't do it for Android auto . Could add play to another rom, calyx or lineage, but then it's not really that limited the way I want it.
I did make a experiment with a rooted stock pixel but very hard to cover all bases and make it work even with root