Android Auto infamous Error 22

I know there are many posts about this, but few solutions seem to work. I recent transitioned from a Pixel 7 to a Pixel 9 Pro. On the 7 AA worked fine. The 9 not so much.

Running e/os 3.1.4-a15-20250917526795-community-caiman on Pixel 9 Pro

I tried installing as per the official instructions no go

I tried the stub apps, same error

I tried side loading AA as a system app, same error

Help :slightly_frowning_face:

4 Likes

It was working with e/OS 3.2 with Android 14. Now I upgraded to Android 15 and it’s broken.

Looks like we will have to wait for it to be fixed. For the FP6 they mention a fix being pushed out to the next version.

1 Like

Just bought a FP5 and installed /e/OS on my own.

I was so stupid to think it would easily work with my car.

But forgotten how bad Google can be.

i can only pray and beg murena will soon bring out a update which makes Android Auto work in A15.

I cross my fingers for all holen also.

1 Like

Took a look in the development anouncements.

Android Auto seams to come tin the end of November!

So you can use your de-googled phone when “driving home for Christmas”! :christmas_tree:

Many thanks to the engineers and contributors.

1 Like

/e/OS v3.3 came a bit later than they planned it seems, but I got my phone upgraded and Android Auto is working now on A15.

So how did you get it working @audirs4 ? Did you install the Google Apps as per the manual mentioned above, after the ugrade to 3.3? Because with me, just upgraded to 3.3 on FP6, and the same thing happened: not connecting to my car.

Yes @bacr, I followed those instructions exactly and got it working.

The App Lounge did show for Android Auto it was installed in the search results. I had to open the details for the app and then it showed there was an update. This may have been unique to me since I had it working in A14 v3.2 and upgraded to A15 v3.2.

Just install the 4 apps as the guide states, give Google Maps location permission when using the app and enable unknown sources and you should be good!

Ultimately, I used this methode:

Tried it this evening and it worked.

@bacr Did you use the stub apps?

Yes I did. At first, it didn’t seem to work and then after a while, the AA kicked in all the same. Don’t no what triggered it to work, but it did.

Tried it again this morning, and still working :grinning_face:

I switched to the stub apps and they are working for me too, after I granted each of them the notification permission. Saved me several hundred MB of space wasted with the full apps.

Thanks.