Android Auto Crashes when destination added

alma

I'm experiencing a strange issue with Android Auto and my Pixel 8 Pro running the latest version of GrapheneOS.

Here's the situation:

My car supports both Android Auto (AA) and Apple CarPlay, with both wired and wireless connections. I tested AA using two different phones (non-GrapheneOS), and both wired and wireless connections work perfectly in my car.

However, my Pixel 8 Pro running GrapheneOS behaves differently:
All required AA permissions are enabled.
Battery optimization is disabled for Android Auto and Google Play Services.
Permissions are fully granted for both.

Issue details:
Wireless connection:
When I connect via Bluetooth, the phone detects Android Auto and prompts me to continue on the car's display — but nothing happens. The car just shows my Pixel as a regular Bluetooth device and doesn't initiate Android Auto.

Wired connection:
Android Auto launches immediately and works fine at first. However, as soon as I enter a destination into any GPS app (Here WeGo, Waze, Magic Earth), Android Auto crashes completely.
If I just open the apps and let the maps load without starting navigation, Android Auto continues to work without crashing.

To isolate the issue further:
I tested my Pixel with a friend's car that uses a Carlink AA dongle — and everything worked fine.
I then tried using the same dongle in my own car with my Pixel, and the crash behavior reappeared.

In summary:
My car works fine with other phones.
My Pixel works fine with other cars.
But my Pixel + my car = problems 🤣

Before I go through a factory reset, flashing the stock ROM, or reinstalling GrapheneOS to rule out device-side bugs...
Is there a way to access Android Auto logs to help identify what’s going wrong?

Extra info:
I'm using User Profiles on GrapheneOS, with a dedicated profile just for Android Auto. The admin profile is unused except for a VPN.

Thanks in advance for any help!

other8026

alma Before doing anything else, make sure the OS, Google Play, Google Play Services, and Android Auto are all up to date. If they're all up to date logs could be helpful.

When it crashes, do you see a popup with a crash log? If not, try triggering the crash, then go to Settings > Apps > All apps > Android Auto > View logs.

alma

other8026

Hey, thanks for your reply.
I went through this, and honestly couldn't identify anything helpful but on the other hand
I don't have too much experience on reading logs. Here it is if someone could help...

I've seen some permission issues but nothing that could explain the crash only on adding a destination...
Logcat generation procedure
1) Entered AA profile
2) Connected Pixel with Car through cable (AA Wired) (No wireless try on this one)
3)Nav App started and map was loaded + Spotify started and music was playing
4) Driving without adding a destination all good.
5) After a short period, a destination was added and on the map zoom in animation the AA was crashed.
6) Logcat saved.

I had to upload the logcat since I couldn't post due to been greater than the allowed characters on a post...
Logcat
Virus Total Scan

Thanks in advanced.

other8026

alma I've passed a link to this thread along, but keep in mind that weird issues like this are harder to troubleshoot since the developers may not be able to reproduce the crashes you're experiencing. Also the developers are preparing for the Android 16 QPR1 update coming up soon so they're very busy with that right now.

It's also totally possible this is caused by some rare bug with Android Auto that will be fixed in a later Android Auto update and the other devices you tested with have a different or newer version installed.

alma

other8026

Thanks a lot for your help.
I'll wait for any info and updates from the developers/app side if any...

For what is worth, I tried also to install on owner's profile and had the same exact issue...
I would like to completely reset the phone and retrying but currently I'm operating daily with 7 user profiles...
Would I be able to eventually image backup/restore the phone with Seedvault? (profiles, apps, data, etc) or I must eventually backup everything idividualy and restore like viber.whatsapp etc? ex Viber is not able to restore if you don't backup to cloud... is Seedvault able to overcome this? I never had the chance to backup/restore GrapfeneOS before...

Thanks.

other8026

alma I don't actually use Seedvault myself, but I probably should. I believe it should work fine for profiles. You could always try backing up a profile then restoring it to a new profile before factory resetting to see if it works first.

alma

other8026

Thanks a lot!
I'll do just that...

alma

Good day,

I'm back with hopefully more info.
Yesterday I updated to the latest GOS version, and also to AA Beta, instead of the Stable release...

Today I decided to give it another go, and this time it was the first time that after the crash, an actuall android auto crashed message appeared to my phone.
Until now I was only be abe to grap the general log from the app settings...

So here it is an actual crash log that was generated automatically as soon as I added a destination to my Nav App.
Please let me know if I should open a GitHub issue, or if posting here is sufficient.

Thank you in advance.

type: crash
osVersion: google/husky/husky:16/BP2A.250805.005/2025090600:user/release-keys
userType: full.secondary
flags: dev options enabled
package: com.google.android.projection.gearhead:147658654, targetSdk 36
sharedUid: com.google.android.projection.gearhead
process: com.google.android.projection.gearhead:projection
processUptime: 27892 + 502 ms
installer: app.grapheneos.apps
GmsCompatConfig version: 161

ibg: Unable to access car
	at hyh.p(SourceFile:61)
	at hyh.g(SourceFile:13)
	at isq.er(SourceFile:32)
	at jay.a(SourceFile:47)
	at tug.c(SourceFile:183)
	at jaz.l(SourceFile:19)
	at jaw.a(SourceFile:20)
	at ibd.u(SourceFile:163)
	at iit.a(SourceFile:923)
	at nzo.f(SourceFile:19)
	at ojl.run(SourceFile:618)
	at android.os.Handler.handleCallback(Handler.java:995)
	at android.os.Handler.dispatchMessage(Handler.java:103)
	at android.os.Looper.loopOnce(Looper.java:248)
	at android.os.Looper.loop(Looper.java:338)
	at android.app.ActivityThread.main(ActivityThread.java:9106)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:593)
	at com.android.internal.os.ExecInit.main(ExecInit.java:50)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:371)
Caused by: oqc: java.lang.IllegalStateException: OutOfCarLifecycle
	at otg.d(SourceFile:123)
	at otg.c(SourceFile:1)
	at oop.h(SourceFile:19)
	at oop.b(SourceFile:9)
	at ojg.x(SourceFile:10)
	at nyh.F(SourceFile:5)
	at nki.g(SourceFile:1)
	at isd.a(SourceFile:1015)
	at ibm.a(SourceFile:245)
	at hyh.p(SourceFile:1)
	... 20 more
Caused by: java.lang.IllegalStateException: OutOfCarLifecycle
	at android.os.Parcel.createExceptionOrNull(Parcel.java:3357)
	at android.os.Parcel.createException(Parcel.java:3333)
	at android.os.Parcel.readException(Parcel.java:3309)
	at android.os.Parcel.readException(Parcel.java:3251)
	at ggb.eZ(SourceFile:11)
	at obb.B(SourceFile:7)
	at oiq.a(SourceFile:225)
	at oop.r(SourceFile:14)
	at oip.call(SourceFile:241)
	at oop.b(SourceFile:1)
	... 26 more

de0u

alma Does this happen if developer options are off? Which car?

alma

Hey,

Yes I just checked with Dev Ops Off, car is the new Peugeot 3008

I just tried more than 20 straight times and same issue.
Unforthunately the AA in my phone never crashed again so no crash log.
Out of the 20 times only once the Here we go crashed let me know if I should post this log just in case.
Keep in mind I've tried in the past also with Magic Earth and Waze and all three of them doing the same...
Also I haven't installed MAPS if that is important to know...
The crash usually happens at the car's side not in my phone...

At this point I think it just don't like GOS and even a complete reset will not fix it and may be pointless.

ron

alma and what if you have maps installed? Does it make a difference?

alma

Guys fingers crossed, that was it.
Installed Maps and after I gave it Location permissions, I can now add destination to all nav apps without crashing.

I will come back with an update after an actual driving session but hopefully that was it.

I feel stupid now that I was pulling my head off all this time without firstly install Maps...

What remains unresolved though is that wireless connection does not work, my car still thinks it is just connected to a BT device...

alma

Update on this: Well indeed it does work after installing Maps, but!
I have to open Maps first and add a destination and then exit the app and open my preferred Nav App in order to work...

So just installing or even open G Maps does not fix it. I have to also add a destination and then exit for AA not crashing. 😩