Android auto communication error 22 on Samsung S7 with /e/ os 4.0

Using /e/OS Applications
1

Hello,

I have a Samsung Galaxy S7 that I just updated to /e/OS 4.0 as soon as the OTA update notification appeared. The update completed successfully and the phone is working normally.

After the update, I decided to install Android Auto by following the official /e/ Foundation guide.

Unfortunately, when I connect the phone to my car via USB, Android Auto does not start. Instead, the car immediately displays the following error:

“Communication Error 22”

Here is what I have already tried:

  • Disabled the App Tracker Blocker.

  • Disabled the Ad Blocker.

  • Disabled Location Spoofing.

  • Disabled IP Address Hiding.

  • I am not using a VPN.

  • Rebooted the phone.

  • Reconnected the USB cable several times.

The installation seemed to complete without any errors, but I still get the same “Communication Error 22” every time I connect the phone.

Has anyone experienced this issue with /e/OS 4.0 or knows what could be causing it?

Any help would be greatly appreciated.

Thank you!

2

Hello @Djolitsu, Welcome to the /e/ users forum.

not sure it is acurate.
I don’t use this feature, but i remember a working “howto” here on the forum…

3

Thanks for your reply.
I tried with the stubs apps, but I got the same result : ““Communication Error 22””
if anyone has another idea ?

4

Which build are you on the official or community build. Pl can you share the build details.

5

e_herolte-user 12 SQ3A.220705.004 eng.root.20260610.161511

6

Personally, I use this method on my pixel 6. I uninstalled the Google/Maps/Speech apps, then I installed the three apps from this dependency link, allowing unknown sources.
google tts.apk
maps.apk
velvet.apk

7

what is velvet.apk ? where do you find it ?

8

Are you on A12? AA works only for A13 and higher

9

Yes you’re right I am n Android 12.
I don’t know why I though the /e/OS version was linked to the Android Version.
SO you find why it is not working…

10

Yes this can be a little complex to understand. Two threads might help e/OS + Android OS version names and numbers? - #3 by aibd

Then when @Manoj asked you, you did not reply with the full_version_string which is [HOWTO] Give complete /e/OS version info easily for support, answers, comparison etc

… so those who replied had to guess.

11

I have got the same problem. (pixel 8 with /e/os 4)

whatever Google-stubs I try to install it always end with “this app can not be installed because the package does not seem to be valid”

I guess this may be because ao /e/ os v4 …. but I actualy don’t know.

12

My post above may help you to check the Android version, that is the critical thing. That /e/OS is at v4.0 was not the significant thing for the OP but that he was using Android 12 (S).

13

I will receive an Samsung S10 phone in e few dyas compatible with Android 16.
Will try with this phone and keep you up to date.
But Yes I think we need Android > 12

14

btw I use Arch, err sorry Android 15.

15

Ok I tried on a Samsung S10 with /e/os 4.0 with Android 16 (Community Build)
And Android Auto seems to work perfectly.

So my issue seems to come from A12 not compatible with AA.

1 Like
16

there is something new.
after some reset of the data of the Android auto application, there is now a possible new connection to my car, but it always end with a message from AA that claim there is not enought notifications to allow the connection, however all notifications are green (allowed) on my phone panel. I have got the feeling to advance on this issue, but now I am stuck, just another way.