GrapheneOS, a privacy-focused version of Android, is adding Android Auto support

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.

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.
- Pixel hardware is some of the easiest to get/best/cost effective with an unlocked bootloader.
  
  Too bad the only affordable ones are those that have little to no support left.
- 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.
- I think because on other manufacturer android phones, like Samsung, you'd have to de-Google and also de-Samsung.
- I'm betting it's because Pixels have some unique hardware/ software quirks or something.
  
  iirc they are the only phones that allow adding custom avb keys and then relocking the bootloader

Oh hell yeah. That was a big issue when I tried out gOS last year.

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.
  
  deleted

I'm still iffy about grapheneos after the rossman issue. Any other good alternatives?
- iirc that developer doesn't work on grapheneos anymore
  
  Daniel Micay says he will retire from lead developer and move on to management role, yet I think he is still committing a lot of the code https://github.com/GrapheneOS/platform_manifest/commits/14
  However, I do believe he is very devoted to improving the privacy and security for all users, despite his communication issue. So I personally still uses grapheneos.
  Similar alternatives are divest and calyx, but it seems like graphene is still the best for me and probably for most beginners and experts alike.
- If you need Android Auto, the closest thing you'll get is LineageOS with some sort of GApps, but those are far from the "privacy and security first" goals of GrapheneOS.
  If you are looking for something private/"FOSS-focused" and don't need Android Auto, I like CalyxOS a lot, and have heard good things about DivestOS.
- I generally like Louis Rossmann, but his arguments in the GrapheneOS video were beyond stupid. He says that he can't trust GrapheneOS because it's developed by Daniel Micay. I guess he doesn't understand that GrapheneOS is open source and anyone can see the code. Then he switched back to the proprietary Google ROM. So he's trusting proprietary software that's filled with spyware over privacy-respecting open source software that can be audited by anyone.
  You don't seem to understand the situation either and you blindly follow some YouTuber. I'd advise you to overthink your opinion on this topic.

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.
  
  It works with microG but you still need the proprietary Auto app.

About time!

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.
  Edit: i meant to ask: "would they have to approve it?"
- Google Pay support
  I can not comprehend this. Ditching Google is why I yearn for alternatives to stock Android.
  
  Here's an example and why I'm not on a custom ROM. My job has "restaurant credit" as one of the benefits. That's 200 euros a month in a card that can only be used through Google/Apple pay.
  So either I skip the money or I need a second phone with me all the time.
  
  Privacy isn't a binary choice. Obviously I would love for there to be an alternative to Google Pay but no such service exists.
  The most private form of payment is to use cash but that's just hugely inconvenient in 2024. Sometimes it would be nice to be able to pay from my phone when I don't have my wallet on me but custom ROMs don't allow it.

I really hope google pay is next, but safety net makes that hard
- play integrity.

oh wow! i doubt im going to use that feature because android auto is insufferable but that's still really neat!
- I am curious why you think that? My reasons for liking it are the fact that it essentially just works, and gives me a consistent UI across multiple vehicles. What are your issues with it?
  
  I'm just fundamentally against those tablets in cars. I've never seen a single good implementation of it. This first question I always have is... what can this do that my phone cant do easier, faster, and better? And 100% of the time I've had to ask this it has been nothing. I just use a phone grip on either my dashboard or my windshield and that accomplishes the same thing without having to use the massive, clunky, and usually dysfunctional tablet stuck on my console. Another enormous complaint is that most cars that work like this also remove aux/tape/cd and then BURY the bluetooth audio option underneath a bunch of finnicky android auto shit that has so many different problems all of which wouldn't exist in the first place if i could just set my phone in a clamp and plugged in the aux cable. The only benefit android consoles have i can tell it has is being big if you have bad eyesight.
- 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?
  
  He's probably gonna reply aux cable lol
  
  I use a phone holder... It has better viewing angel, don't require any connection (except bluetooth for audio) and even better, it don't cost a new head unit, both in price and in e-waste.
  
  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.

Is it easy to install graphenos on iOS? I got an iPhone 14. Does anyone have a good recommendation to help me through the process?
- deleted
- GrapheneOS only works on Pixels. Also, you can't install anything other than iOS on an iPhone.
- It was probably a mistake to buy an apple device if you want to run and Android ROM.
- https://grapheneos.org/faq#supported-devices