Honestly this is one of the only things holding me back from going to graphene. Once this is available to non alpha users I might make the switch properly.
Absolutely. Android Auto is a must for me.
I’m on stable, and using it.
I tried out this OS last year and really loved it, until I went on a road trip and couldn’t use Android Auto. This is huge and will make GrapheneOS an extremely attractive option to privacy minded people.
I think Android Auto is really the only thing keeping me from completely de-googling. Many times in the past I’ve installed some stripped down ROM or whatever but I always go back because Android Auto is too convenient.
I wish there was a nice open source alternative that worked with my head unit.
So you can have Android Auto while beinging degoogled. I do. As others have pointed out there is: https://github.com/sn-00-x/aa4mg
It’s a bit of a faff to install, but works.
The problem I found is no SatNav that can take into account traffic. The best I’ve found is “Organic Maps”, but it is open and works without the Google infrastructure. No getting round that traffic knowledge makes Google Maps better.
I have non AA things forcing me towards having to at least partly re-google.
I’ve been eying GrapheneOS as a way to compromise without being compromised.
Oh hell yeah. That was a big issue when I tried out gOS last year.
To me it is super weird that GrapheneOS positions itself as a way to degoogle - but it is only supported on google’s Pixel hardware.
They only support Pixel hardware because it’s currently the only line that meets their list of requirements. I’d guess that if something came around which beat the Pixel line, they’d support it…but I also don’t see anyone positioned to do that right now.
Though it’s worth mentioning that the developers don’t emphasize degoogling all that much and their community often have a bit of tension with degooglers who come to join them. The OS certainly meets the needs of those of us getting away from Google but the developers have no problem recommending workflows that go through Google (albeit with regular app access rather than the privileged and deeply integrated access on stock Android) when they’re more secure than the alternatives. For example, they’ll regularly suggest using sandboxed Google Play over F-Droid or Aurora Store, again because of their stance of prioritizing security above all.
It can sometimes be a bit annoying when your priorities are more about avoiding corporate surveillance than protecting yourself from attackers or a snooping government, but their work ends up supporting both regardless.
That sounds like a reasonable position. Google would have an advantage in getting timely AOSP and security updates, but getting that stuff done should be a high priority for all manufacturers anyway. As for the rest of the list, there are things I don’t know about - but at a glance it looks fair enough. So I guess there could and probably should be other phones trying to meet those conditions.
For example, they’ll regularly suggest using sandboxed Google Play over F-Droid or Aurora Store
Because many of my used apps are only available in Google Play.
GrapheneOS gives you options that you don’t have to use. I don’t agree with you.
You know what Aurora Store is, right?
About time!
Is Androit Auto proprietary? Does it depend on Google services (beyond GoogleMaps)?
Yes it’s proprietary and depends on a lot of Google services. Usually if you want it on a custom ROM, you need to use the full GApps packages. No Android Auto on smaller GApps packages.
I’d have rather seen Google Pay support than Android Auto though I imagine it’s a lot less feasible.
Google would have to approve the OS by whitelisting it
Yeah that’s definitely not going to happen lol
Would they? Why? I’m asking as I’m unaware of what restrictions are in place for it to work.
They would not. Best case scenario is that you can trick Google into thinking your device/OS is legit. It’s of no benefit to them to in any way compromise the security of their highly sensitive payments app.
Because it requires full safetynet compliance
Awesome. I’ve been using GrapheneOS on my Pixel 7 for almost a year now and it’s been great. I won’t be using this feature, but am happy it might attract more users.
I’m still sour that Google disables hdmi/DP over USB-C on Pixels on purpose, and it bothers me that Graphene devs never bothered adding it back.
I think it’s available on the Pixel 8. Graphene OS enabled USB-C video out a couple of months ago.
I really hope google pay is next, but safety net makes that hard
oh wow! i doubt im going to use that feature because android auto is insufferable but that’s still really neat!
What don’t you like about Android Auto? What alternative would you use to interface with a vehicle head unit if you didn’t AA?
what baseless_discourse said. a windshield or dashboard mounted phone clamp. it is far cheaper, easier, and downright better, for myriad reasons. viewing angle is better, music playing is unspeakably easier, system resources are almost guaranteed to be better, software compatibility is better, etc.
I much prefer utilizing the head unit already installed in my car. Otherwise, before I did just use my phone.
