It seems that finally a full workable solution (confirmed by a few users) is available here:
Just flash the zip file and reboot.
I didn’t tried myself so it would be good to get some more feedback… 
Just tried it on my OnePlus 8T and got the “No Free Space” message so I couldn’t install it. Is there any way I can expand the system partition (preferably without building my own image)?
1 Like
Hello.
The app will be discontinued soon, gg prefer its ‘gg assistant’ for Android 12…
Did some quick reading on the MicroG github, and from what I can tell, Android Auto would most likely have to be installed as a system app by /e/ themselves in one form or another. Option 2 or 3 won’t preinstall Android Auto, but makes it available should the user desire it later. Option 3 would probably be the best way for /e/ to do it so users who don’t want anything Google on their devices aren’t forced to have it. But again, the /e/ team would have to do this.
2 Likes
I agree, both option 2 and 3 would be great!
Unfortunately, it does not seem to be the case that this is planned short- or mid-term. Android Auto is such a great feature and it’s so sad that it can’t be used with /e/ so far.
I am on LOS19 for microG right now. With apply that Magisk module my result was mixed:
Phone connects to car and AA is shown in car display. Maps is shown as icon but not opened on car’s screen.
Anyhow, I tested this offline (no wifi, no mobile data), later one the idea is to disable the ethernet access by firewall.
It would be interesting what to do, to have a minimal setup to have a navigation mirrored on screen of car. So without (or passive) gmaps, gapp, speech.
Could someone else test this on /e/OS or LOS18.1? (android 11)
I’m not sure I understand the problem here; is it the same as mine?
I have just bought a new car. Unfortunately, no GPS… just android auto.
I have a FairPhone 4 on which I have installed /e/OS (version 1.10) as I don’t want google in my life.
To project the phone onto the car screen, I think I need to install Android Auto. If App Lounge doesn’t offer this, then my data will probably go to google (which I don’t want).
What is the alternative to projecting the phone onto the screen? Is there a way to install android Auto on /e/OS? What data is likely to go to google?
Thank you for your help
Indeed, at the moment there’s no solution to run Android Auto on a Fairphone 4 stable as you can not install magisc module without rooting your device (and thus loose all your data).
Hopefully /e/ devs are working hard on an opensource solution to make it work with Android Auto APIs in the future.
1 Like
Hi All,
I recently installed an EONON Android Headunit in my car and wanted to connect my Murena Phone. Android Auto does not work as you may know.
I tested out a number of different apps and the one that was most promising and was able to connect a Murena phone to an android headunit is CarbitLink-EasyConnection.
This app needs to be installed on the headunit and the phone and it will allow you to mirror and control your phone via usb (without needing bluetooth) and can also connect over wifi without a usb cable.
I think if the headunit was connected to the phone’s hotspot then this may also work but have not tested yet.
When you mirror it will show you all your phone apps on the headunit and when you use Maps (Magic Earth) for example it will flip to landscape mode on your headunit.
I havent quite figured out how to relay the audio from the phone to the headunit but I think this permission is under Settings >Apps>CarbitLink> App Info on your Murena Phone.
Hopes this helps! 
2 Likes
GrapheneOS is getting Android Auto, so maybe some day we could see AA also in e/os/?
https://igamesnews.com/mobile/grapheneos-will-add-android-auto-even-if-it-doesnt-include-google-apps-or-services/
1 Like
Graphene goes fundamentally different about Play Services (sandboxed full play services) than the microG distributions. sn-00-x proposed some patches for Calyx (microG distribution) on how to integrate that’d be transferable to /e/, for people building their own device image at least that aren’t keen on going the magisk route.
For a lengthy discussion of the approaches (including Graphene), see the last 2-3 comments leading up to the closing one by microGs Marvin: https://github.com/microg/GmsCore/issues/897#issuecomment-1869670768
Android Auto compatibility is a very long awaited feature in /e/os. Dev Team knows that and @GaelDuval knows that very well. But it’s just not easy to implement as you can read in many posts in this and other fóruns.
Let’s just hope in 2024 the dev team will find a “magic” solution for non rooted devices.
3 Likes
Dear @Manoj , until now, Roadmap for 2024 wasn’t released. Is there anyone who can explain /e/os users what is being done to add the long awaited compatibility with Android Auto?
I’ve been a very happy /e/os user for a few years now. Have bought FP3 and FP4 from Murena Store. But Android Auto is a must have that is preventing me from buying a FP5.
Thanks for the reminder. Will request Gaël to share the roadmap for 2024
4 Likes
There’s still this open feature request:
https://gitlab.e.foundation/e/backlog/-/issues/7098
The last commit was more than 7 months ago though…