GrapheneOS version 2023123000 released (Supports Android Auto)
GrapheneOS version 2023123000 released (Supports Android Auto)
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.
Tags:
- 2023123000-redfin (Pixel 4a (5G), Pixel 5)
- 2023123000 (Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, emulator, generic, other targets
Changes since the 2023121200 release:
- 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 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Generic 5.10): update to latest GKI LTS branch revision including update to 5.10.204
- 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)
- Vanadium: update to version 120.0.6099.115.0
- Vanadium: update to version 120.0.6099.144.0
- AppCompatConfig: update to version 2
- GmsCompatConfig: update to version 88
- GmsCompatConfig: update to version 89
- GmsCompatConfig: update to version 90
- Auditor: update to version 78
You're viewing a single thread.
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.
Awesome. Would it be too much to ask that you share the process. I'm sure some people would love to do the same. Not me though, im fine getting surprised by horrible traffic 🤣🤣
Sure , not sure I remember all steps :) but calyx install as regular but stop it before locking bootloader. Magisk root ( need to patch using the app) ACCA on fdroid for battery charge controll (since I leave it in the car) Aurora store (need to use for "installin like Google" Beta versions of spotube and organic maps. AA AIO tweaker
Magisk modules Android auto 4 microG , Shamiko, Zygisk-LSPosed
https://github.com/Rikj000/Android-Auto-XLauncher-Unlocked Can't remember the guide I used ,sorry
Trying to get video working on display as well :) VLC did not work out of the box unfortunately
My wife is going to hate you. I'm throwing you under the bus because I'm ordering a Pixel 7a for this sole purpose. 🤣🤣
Lol :) then you can probably do something similar using GOS as well
I daily-drove GOS for over a year, but ended up getting away over the (ex?) lead developer's rants. Not that it affects me personally, couldn't care less honestly. However, as hardened as the OS may be, at the end of the day it takes some level of trust in developers to use their stuff, and I can't trust someone with those levels of mental health issues living in denial of those issues existing. If he would have humbly acknowledged the issue, and at least had attempted to deescalate the situation, that would be a different story, so I ended up going back to CalyxOS, with it being the second best option for privacy, as far as I'm aware. That's not to say anyone else should follow my steps, this is how I see things, not how I believe everyone else should. Other than that distrust, I have absolutely nothing but great things to say about GOS.
Yea I had a run in with him as well in the matrix room. However, water under the bridge. He stepped down a while back . Things seems better now overall. Btw I also used RHvoice for voice directions on organic maps. Should also say that it is still a bit buggy, but I expect it to improve once it out of nightly versions.
Oh, I can see myself going back at some point. I am taking advantage of this decision to test drive Calyx again (it had been over a year since the last time). Both projects are different, which most people don't get. GOS is all about security, which certainly makes privacy easy, but privacy is not it's main goal. Calyx is all about privacy, by whatever means necessary, security is one of its focuses, just not at the expense of usability and UX. I have a pretty solid network security at home, and don't go out much, which helps me feel comfortable with Calyx, and I love the interface and user experience. But with GOS I have many more security tweaks to play with, which I honestly miss sometimes.
As for voice directions on any navigation app (or any app for that matter) I've always turned those off, regardless of the app, even when I wasn't privacy conscious. I just find it really annoying, specially since it interrupts music while driving. To each his own I guess.
The 3a and 3a XL are no longer supported by GrapheneOS, but they are still supported by CalyxOS so you could try to run Android Auto on that.
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
https://github.com/sn-00-x/aa4mg Just found this , seems I'm going to use the spare rooted calyx one for this. Back to the classics.. would be pretty cool if someone would build something that's made for use as android auto only.