Android Auto and FP5

I installed A15 3.3 /e/OS and I am going to test again how Android Auto is working. There is manual here and I am wondering shall I install all mentioned components (google app, gmaps, google speech and AA itself)? I am not going to use google maps, I am using SherpaTTS so I think I will need to install only google app and AA, am I right? Or maybe there are some important apps in gmaps or speech essential for AA to work on murena OS? What do you think? Or maybe you already have some experience to share?

Anyway I am going to test AA with only gapp istalled and I’ll let you know the result.

[Update] unfortunately all fout apps needs to be installed - it’s AA requirement :frowning: But I cas say that for the first time on FP5 I was able to see AA launched after my car was connected. Good job, team!

1 Like

After reading your post, I was a bit sad but proceeded to install all four of the Google Apps listed in the e/os docs in the hopes of getting Android Auto to work on my Fairphone 6 now updated to e/os 3.3.

I had read about others trying out stubs to replace all Google Apps other than Auto itself (Maps, Google, Speech Synthesis) which apparently resulted in breaking all navigation software, including Magic Earth.

In a last hope effort, I decided to try the stubs mentioned in the iodeos docs and am happy to report that these seem to work perfectly, allowing me to navigate in the car using the bundled Magic Earth app without having any Google Apps apart from Android Auto installed :slight_smile:

I’m not sure whether installing the full apps before uninstalling and replacing them with stubs was crucial in getting this to work but my complete workflow was something like this:

  1. Install all Apps via Aurora in the order recommended by e/os docs (might be unnecesary, see above)
  2. Reboot
  3. Manually grant Android Auto all necessary permissions
  4. Uninstall all apps apart from Android Auto
  5. Install stubs recommended by iodeos docs (directly on phone, without adb)
  6. Reboot
  7. Allow “Unknown sources” in Android Auto developer settings, disable “Wireless Android Auto”
  8. Start using Android Auto

Edit: Another possibly missing piece to the puzzle I just remembered (because there was another update): A think I might have updated Magic Earth via Aurora.

4 Likes

Maybe there is some issue on FP6, On FP5 I’ve just installed it and it worked. I even installed first just google app and AA and tried if it will work - after connecting to car I saw info that remaining two apps need to be downloaded. So I install speech and gmaps and connected again and that’s it. No reboot needed. I noticed just few small issues:

  • when I start Magic Earth for the first time in a car and tried to start navigation I saw a message that I need to do some action on my phone, but there was no message. So I disconnected, started navigation on my phone, then I saw a message (not remember what, just needed to confirm some) and next time when I connected to car navigation went smoothly
  • Some issue with CoMaps and speech synthesis - not sure why the voice in CoMaps is not acceptable - I have Google Speech and Sherpa as well but don’t know yet why it doesn’t work in CoMaps.

Oh I’m sure that it would have “just worked” using the regular Google Apps on FP6 as well!

My point is that I was more than a little surprised to find that I was able to get around installing the other Google Apps using stub versions after reading other reports to the contrary. That’s why I tried to list in detail what I remember of my steps in getting there.

I’m very confident it will just work using the regular Google Apps and even somewhat confident that you can just install the stubs right away and get it working, without all that back-and-forth :slight_smile:

2 Likes

“stubs" that is what I missed in your previous post :wink:

I think it may be possible one day. but now I’d be glad if I can use it without installing maps and speech from Google. Google app should be enough at this point, microg in a future…

Hi, thanks for that workflow,

on my Murena FP5 (fresh /e/os 3.3) I just installed the stubs. It did work first try, thanks to all involved.

Now Aurora wants to update google. I ignore this, right?

Greetings,

zig

Definitely don’t; mico-G spoofs Google components and Aurora might potentially put Google back in the system. Best to set Aurora to Not update from other sources.

1 Like

I would like to try this, but how do I actually install the stubs? I need to get the apk files, but I can’t find a download link on the Github page? Also, should I install the Android Auto app first and the stubs then, or does it not matter?

Pixel 7 with eOS 3.3

1 Like

Hi Kalle,

I installed AA first but don’t know if that is important.

You find the download link when you click on the list entry. Another window opens for the chosen stub. In the lowest box (“code” “blame”) you click the three dots and voilà there’s your download button.

HTH

1 Like

Hm, my car (Opel Corsa) first says Android auto is available, but then gives an error message.

:roll_eyes:

What is the error message?

It’s in Finnish, but something like compatibility problem, checking again. On the phone, Android auto seems to be installed from Aurora, but not visible among the apps.

:thinking:

Hello there, i still have issues with Android auto.

I have installed all apps, but when i connect my FP5 eOS 3.4 to my car (dacia Sandero), the display shows an error message: “bluetooth device not supported”.

How can I fix that?