GrapheneOS build: 2026042101
Car: Audi A4/A5 with MIB3 MMI (firmware 39.20-232601)
Connection: Wired USB only (car does not support wireless Android Auto)
Summary:
Android Auto stopped working after a recent GrapheneOS update. It previously worked in a secondary Google user profile. It now fails in both the secondary user profile and the Owner profile.
Key errors from Android Auto log:
- com.google.android.projection.gearhead:car: Failed to find entry 'classes.dex': Entry not found — appears repeatedly on every launch, even after clean reinstall from GrapheneOS App Store
- com.google.android.projection.gearhead:car: ART APEX data files are untrusted — appears in Owner profile log
auditd: avc: denied { read } for comm="binder:XXXX" name="u:object_r:odsign_prop:s0" — SELinux denial on startup
- auditd: avc: denied { read } for name="u:object_r:qemu_sf_lcd_density_prop:s0" — repeated SELinux denial
CAR.GH: Channel: UNKNOWN — after fresh reinstall, channel fails to initialize
ConnectACarActivity: LIFECYCLER_STOP_ACTIVITY time=1ms — the first-time car pairing wizard opens and immediately closes, preventing setup from completing
What I've tried:
- Clean uninstall and reinstall of Android Auto, Google Play Services, Google Services Framework from GrapheneOS App Store
- Granted all permissions including microphone, phone, contacts, calendar, call logs, notifications
- Enabled "exploit protection compatibility mode" for Android Auto
- Enabled "display over other apps" and "modify system settings"
- Enabled all 4 toggles in Settings → Apps → Sandboxed Google Play → Android Auto
- Set Bluetooth AVRCP to 1.4 in Developer Options
- Disabled Bluetooth A2DP hardware offload
- Cleared cache and data for Android Auto and Google Play Services-
- Rebooted phone and MMI multiple times
- Tested on both Owner profile and secondary Google user profile
- logged in to google account
Additional context:
Android Auto previously worked on this device in a secondary Google user profile before the recent GrapheneOS update ( not 100% sure it is the update though)
The classes.dex not found error persists across multiple clean reinstalls, suggesting a system-level incompatibility introduced in a recent build
The car MMI consistently sends STRING_COUNT=0 in the USB accessory handshake, though this may be a secondary issue caused by Android Auto failing to initialize properly.
Any help is welcome