- cross-posted to:
- android@lemmy.ml
- cross-posted to:
- android@lemmy.ml
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 must log in or register to comment.
Yissss... Now it finally is time to give graphene another go as daily driver (pun intended)
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.
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
Yes, to use Android Auto, the Android Auto app has to be installed. It should be installed from the GrapheneOS Apps repository (app).
Amazing. Just waiting for the documentation now to see what data is collected with it. Granted I do not have a car with Android auto but probably will in the future
