E/os 3.6+ and Android Auto

Using /e/OS Applications
1

Hi everyone,

I write here because I havent found any solution for the moment.

I have a FP6 with /e/os installed, and I regularly use Android Auto with my car.

Everything was ok with /e/os 3.5.

Once I had updated with /e/os 3.6, Android Auto was able to connect only once per day (first connection)

Update on /e/os 3.7, 3.7.1, same behavior, it’s very hard to get a working connection.

I precise : it’s not the car, neither the cable. It works perfectly with my professional phone (Samsung A52s).

I have manually updated Android Auto from App Lounge : nothing has changed.

What’s seems weird to me : usb settings is shown grey when connected to m’y car (charging by default, no file transfer). Impossible to change this…

Any idea on how to solve this ?

Thanks a lot,

Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online services

phone
phone427×374 173 KB

2

Hi everyone,

Just some details for archive, in case someone has the same problem in the future.

The problem seems to appear each time I forgot to disconnect my phone from the car before leaving it.

When so, I suspect some car energy saving that doesn’t cleanly disconnect the phone from the car leading to missing usb recognition at the next connexion.

Still investigating for more details…

Best regards,

4

Bonsoir,

Thanks for this feedback.

Does the phone connect once a day, then refuse to reconnect if the car entertainment system has shutdown while the phone was still connected ?

6

What is working for me :

1/ on your phone, go on App Lounge to Android Auto, and update if needed (update is not automatically done, I don’t know why).
2/ restart your phone
3/ restore factory settings on your car interface
4/ connect your phone ; android auto config should start

When stopping your motor, always disconnect your phone before leaving. For me, knowing this rule, it works quite properly…

Let me know of your test!

Bonne soirée (j’écris en anglais pour que le poste soit référencé) !

8

Don’t drop. You can install these stubs that will fool AA to think that Google apps are installed:

3 Likes
Fully degoogling
Android auto communication error 22 on Samsung S7 with /e/ os 4.0
12

Nice!
Thanks for the feedback.

One simple trick that may help : some apps are compatible with Android Auto but are not validated by google.
For that :

  • Go to Android Auto parameters (on Parameters, go to Android Auto)
  • Go to version and tap on it multiple times (at least 10 times fast) and validate the developper mode when the prompt appears.
  • Then click on the 3 dots on the right upper corner. A new entry should have appeared “developper parameters” ; go on it.
  • Find and check the entry “unknown sources”

The next time, compatible applications should appear on your Android Auto.
Best regards,

16

If you try to update stubs, you’ll get a warning that the update has failed and after that those updates don’t appear in App lounge anymore.

17

This topic was automatically closed after 60 days. New replies are no longer allowed.