COMING TO GRAPHENEOS THIS NEW YEAR...
Android Auto
https://github.com/GrapheneOS/grapheneos.org/commit/0ab6930ef6a6ff6cd488aa62e240b65141003185
COMING TO GRAPHENEOS THIS NEW YEAR...
Android Auto
https://github.com/GrapheneOS/grapheneos.org/commit/0ab6930ef6a6ff6cd488aa62e240b65141003185
Huuuuuge 🤠🤙🌊🌊🌊🌊🌊🌊
How does this protect us from the data collection within the car?
Usage of Android Auto is subject to all the normal pre-requisites when using any app or service. We're adding the functionality as we always do what we can to reduce the barrier to entry, while being the preminent security/privacy OS with the broadest app compatibility.
Using Android Auto on GrapheneOS will be more restricted than it is on stock thanks to our compatibility layer for sandboxed Play Services. However just like eSIM management Android Auto will require users to understand there are some privileged access required on an OPT IN basis and toggles will be provided for these.
What won't change is our respect for users to choose what is best for them and for us to empower them to make those decisions.
Official Project Account:
Android Auto support for our sandboxed Google Play compatibility layer has been merged into GrapheneOS and should be available in the next release. It's currently going through final review and internal testing leading up to being able to make a public Alpha channel release.
The implementation uses the compatibility layer to eliminate most of the special privileges that are usually required. It provides 4 permission toggles for enabling different access for wired Android Auto, wireless Android Auto, audio routing control and phone call control.
No special access is granted by default. We've made subsets of the standard privileged permissions for these toggles for granting only minimal required access. Wired Android Auto is close to working with 0 special access required but not quite so it still needs a toggle.