I’ve been battling a frustrating wired Android Auto compatibility issue for months. Despite exhaustive troubleshooting, OS 4.0 update, and detailed logs shared with support (Ticket #1375848), the problem remains: My Skoda infotainment misidentifies the phone as “Volcano QRD SN:26D45CA7” (Qualcomm’s internal reference design codename), causing connection loops, handshake failures, or “connect compatible device” prompts. It’s a safety concern for nav/music during drives, and wireless isn’t ideal for me.
From my logs, it’s a USB descriptor leak in the kernel gadget driver, the phone exposes QRD strings instead of “Nothing Phone (3a) Pro” during enumeration, leading to rejection.
What I’ve Tried (Chronological Summary):
Basics: Latest Nothing OS 4, high-quality USB-C cables/adapters (original Nothing and other cables), all car USB ports.
Resets & Configs: Cleared AA cache/data, forgot cars in Connected devices, factory reset infotainment, enabled USB debugging, set Default USB config to MTP/File Transfer.
App/Background Tweaks: Allowed AA unrestricted battery/background, force-stopped/reinstalled, disabled USB audio routing.
Advanced: ADB logs/dumpsys during failures (attached excerpts), USB reset commands (svc usb reset), property overrides (setprop sys.usb.product.name—failed due to read-only props).
Post-OS 4.0: Fresh bug report (Nov 29) shows same DISCONNECT after ACCESSORY=START in dumpsys usb.
Key Findings from Logs:
Dumpsys USB: Repeated CONNECT → CONFIGURED → SENDSTRING (manufacturer=“Android”, model=“Android Auto”) → DISCONNECT ~10ms after START—rejection due to unrecognized descriptor.
Input Dumpsys: “volcano-qrd-wsa883x-snd-card Headset Jack” leaks in device list (audio codec tied to USB).
ADB Getprop: No sys.usb.manufacturer/product.name props (kernel-locked); grep usb shows dwc3 controller but no overrides.
Linux MTP (Arch): Device shows “VOLCANO-QRD_SN:26D45CA7” despite file access working—proves cross-host leak.