Hi, I’ve been trying to setup Android Auto with no luck so far.
Following the documentation provided How to setup Android Auto with /e/OS? neither the car nor the phone seem to recognise the attempt to use AA after connecting the phone with a compatible cable. The car definitely support AA, I’ve also taken care to use the most recent versions of all the necessary software, I’ve also tried granting the apps associated with AA all possible permissions with no luck.
I can’t seem to connect to the car in the first place. If I understand correctly, upon having installed all the necessary apps and connecting the phone to the car, I should get some kind of AA screen telling me that either the phone or the car recognises the other but in my case nothing happens.
I thought about turning off advanced privacy for AA, but AA does not appear in any of the lists under advanced privacy; I can only seem to manage its permissions where I’ve allowed it to do everything. Under Advanced privacy, the only setting left is to allow trackers for the required Google app, though that seems to have no effect.
So, I went through Android Auto hell a few months back, and wrote a forum post documenting the procedures I did, that worked. Here’s a link to the post with just-the-steps, though the whole thread is probably worth a look:
For clarity, /e/OS does support AA out of the box, but where I ran into issues was when apps were sideloaded. The provided procedures ensure that any AA compatible app shows up on your car’s screen, irrespective of where it came from.
It only shows Android auto compatible apps if it is installed with original google play store app, or the king installer app. (when using aurora store or fdroid, it will never get in android auto carscreen, maybe with kinginstaller app to install apk from apkmirror)
And Android Auto = WELCOME TO THE GOOGLE VENDOR LOCKIN (you need also google assistant app, google app, google maps app, google calendar app, google messenger app, google phone app, all dependencies that android auto need, so you going to google your ungoogled /e/OS.
I use a older phone with Android for Android auto. Keep in mind, most Android auto freedom is possible with Android 13 or lower. When you use Android 14 or higher, android auto is more limited Here a howto (it is in Dutch explains how to get fullscreen video/iptv/webbrowser/audio/etc in your car enterttainment system compatible with Android auto, you can use translator)
A manual connection through the AA app is also not possible. Neither the car nor the phone seem to recognise each other – i.e. when I connect them, nothing happens. Were you able to find AA under advanced privacy?
I have A15 and the newest e/OS version installed.
According to the documentation only google, google maps, and google speech recognition are the necessary dependencies.
Maybe excluse aa app from advanced privacy (settings / advanced privacy / app trackers & ads / in apps list see if you can find androidauto then disable the “toggle on trackers control”).
Keep in mind, android auto also forces a bluetooth connection to the car. (so wired/usb or wireless android auto connection + bluetooth connection)
I was struggling with the AA installation on my Xiaomi Mi 9 Lite phone running /e/OS v4.1.1. I followed How to setup Android Auto with /e/OS, but Android Auto was not available for me in App Lounge at all. The pre-installed AA version was just a stub.
I did the following:
Downloaded Android Auto version 17.1.662414-release from APKMirror
Installed APKMirror Installer (beta) from App Lounge
Installed Android Auto with APKMirror
Enabled notifications for AA in Settings > Notifications > App Notifications
Thank you for this advice. I followed the various steps without any issues, and AA is updated to its latest version. However, I am unable to disable notifications: the checkbox is grayed out. Do you know why?
For now, I am stuck at the same point as when I first received the phone: the AA icon appears on my Fairphone, but the car (Skoda Scala 2019) does not seem to recognize it (I immediately get a “connection failed” message). The AA app does not open on either the phone or the car.
I am starting to think I will just stick with Bluetooth and use the phone in GPS mode…
Sorry to ask a dumb question but I fell In miss a bit of bases and I’m trying to understand. Please correct me/add where relevant.
I see three or maybe 4 roads for Android auto with e/os:
I put the play store and all the Google apps on my phone and android auto works great, but I ruined the whole idea of an e/os phone
I start with magisk, but it is so complicated, unstable with updates that this will probably a failure (as it requires quite some skills which I don’t think I have - don’t bite more off than you can chew)
compromise: can I run the Google apps on my phone in work profile/shelter? I know this is privacy wise not the best solution, but probably the best I can manage.
The option above described by @suuruu (Android Auto version 17.1.662414-release from APKMirror) is this one of the routes above or does it work differently? (Like: does it work with MicroG, Google Play, Magisk or another service?).
Can someone help me how I do this? Example: I have Google maps running in work profile is e/os Fairphone, and i haven’t figured out whether I have the play services (and in which part: work profile, or total phone) or it is just by microg. I find privacy important but my knowledge is limited and I find it difficult to understand this fully (or at least I’m worried to miss parts).
Sorry, but I just linked the official page rather than sound too opinionated on your larger point.
Personally I would have no interest in connecting to or owning a Googled car. I have not researched the purchase of a new car but it may be difficult / impossible for a degoogler to buy a new car now.