CachyOS: Android (Xiaomi) keeps disconnectiong

[ThatzOkay]

It connects for a moment and i can see the Android Auto notification. But then it errors out and disconnects again.

[17:07:33.803] [AaManager] wired bridge ready on 127.0.0.1:5278, dialling loopback
[17:07:33.803] [AaManager] wired AA bridge started on loopback
[17:07:33.803] [ProjectionService] started in AA mode (wired)
[17:07:33.804] [AaManager] wired loopback connected → spawning AaSession
[17:07:33.805] [AaSession] display 1920×1080 (AR 1.778) → AA tier 1920×1080 (AR 1.778) @200dpi, PAR e4=10000
[17:07:33.804] [AaManager] wired loopback connected → spawning AaSession
[17:07:33.805] [AaSession] display 1920×1080 (AR 1.778) → AA tier 1920×1080 (AR 1.778) @200dpi, PAR e4=10000
[17:07:33.805] [AaSession] clusterDisplayed=true (screens=[main]; channel will be advertised in SDR)
[17:07:33.805] [AaSession] cluster 12280×720 (AR 1.778) @180dpi, PARe4=10000
[17:07:33.884] [ControlChannel] Servie="Android" brand="Xiaomi 23127PN0CG"phone_info={"instanceId":"c066f1a3-cb0e-4e15-8c90-fa12ef088049"}
[17:07:33.885] ══════ SESSIONS · creain={"instanceId":"c066f1a3-cb0e-4e15-8c90-fa12ef088049","usbSerial":"c1f688e9","ip":"127.0.0.1"} ══════
  #1  androidauto usb  held   main:- cluster:-         keys: inst=c066f1a3-cb0e-4e15-8c90-fa12ef088049
ip=127.0.0.1
[17:07:33.886] [ProjectionService] active session -> #1 androidauto
[17:07:33.886] [SESSIONS] codec-restore #1 androidauto: session=- map=- → gstVideoCodec=h264
[17:07:33.886] ══════ SESSIONS · activate #1 androidauto (prev none) ══════
  #1  androidauto usb  ACTIVE main:- c066f1a3-cb0e-4e15-8c90-fa12ef088049ip=127.0.0.1
[17:07:33.899] [ControlChannel] unhan

[17:07:36.398] [AaManager] wired bridCancelled
[17:07:36.398] [AaManager] wired bridge error: transferOut error: Cancelled
[17:07:36.399] [Session loopback] disconnected: socket closed
[17:07:36.399] [AaEventBridge] AAStac) — supervisor stays up for retry
[17:07:36.400] ══════ SESSIONS · close #1/androidauto → IDLE ══════
  (no sessions)
[17:07:36.401] [ProjectionService] wired AA bring-up with device vid=0x18d1 pid=0x2d01                  [17:07:36.401] [AaManager] _startWireAP bridge
[17:07:36.401] [UsbAoapBridge] switchAndOpen isAccessoryMode=true vid=0x18d1 pid=0x2d01                 [17:07:36.914] [AaManager] wired bridP accessory interface: claimInterfaceerror: interface is busy (errno 16)                                                                     [17:07:36.914] [AaManager] wired bridaim AOAP accessory interface:claimInterface error: interface is busy (errno 16)                                                      [17:07:36.914] [ProjectionService] wie — session not running, retrying
[17:07:37.755] [UsbAoapBridge] device reset failed: Error: reset error: device disconnected (errno 19)
[17:07:37.756] [UsbAoapBridge] accessory device closed                                                  [17:07:37.756] [AaManager] wired brid
[17:07:37.761] [USBService] Phone detach during re-enumeration window — suppressed
[17:07:37.915] [ProjectionService] wired AA bring-up with device vid=0x18d1 pid=0x2d01
[17:07:37.915] [AaManager] _startWiredBridge: bringing up wired AOAP bridge                             [17:07:37.915] [UsbAoapBridge] switchvid=0x18d1 pid=0x2d01
[17:07:38.417] [AaManager] wired bridge error: Failed to open AOAP accessory device: open error: device not found (errno 2)
[17:07:38.417] [AaManager] wired bridge start failed: Failed to open AOAP accessory device: open error: device not found (errno 2)
[17:07:38.417] [ProjectionService] wired AA bring-up returned false — session not running, retrying
[17:07:39.110] [USBService] attach vid=0x18d1 pid=0x2d01 cls=0x0 serial=c1f688e9 → dongle=false accessory=true phoneCandidate=true la
[17:07:39.110] [USBService] Accessory-mode re-attach during re-enumeration window — bridge owns it (reset)
[17:07:39.121] [USBService] attach vid=0x18d1 pid=0x2d01 cls=0x0 serial=c1f688e9 → dongle=false
accessory=true phoneCandidate=true la
[17:07:39.121] [USBService] Accessory-mode re-attach during re-enumeration window — bridge owns it
(reset)

[17:07:40.420] [ProjectionService] wiid=0x18d1 pid=0x2d01
[17:07:40.420] [AaManager] _startWiredBridge: bringing up wired AOAP bridge
[17:07:40.421] [UsbAoapBridge] switchvid=0x18d1 pid=0x2d01
[17:07:40.428] [AaManager] wired bridge ready on 127.0.0.1:5278, dialling loopback
[17:07:40.428] [AaManager] wired AA bridge started on loopback
[17:07:40.428] [ProjectionService] st
[17:07:40.429] [AaManager] wired loopback connected → spawning AaSession
[17:07:40.429] [AaSession] display 1920×1080 (AR 1.778) → AA tier 1920×1080 (AR 1.778) @200dpi, PAR e4=10000

EDIT: codeblock

[f-io]

release? custom build? latest nightly? I do not have an arch test system atm to reproduce this.

Can you test this on a different host, just to verify your phone is fine? A lot of Chinese phones do not support Android Auto by default, as they are blocked for the Google Playstore. I'm always testing with GrapheneOS.

[ThatzOkay]

It's the latest git running on CachyOS arch linux. I'll try with my PI tommorow which runs raspbian OS lite. I can see the Android Auto App in the playstore and it is installed

[f-io]

please double check with rasperry pi OS (trixie), if it does work we know this is os related.

[ThatzOkay]

Had to reset Android Auto APP Cache and Data. Seems to work again. If anyone else gets this issue. First try clearing Cache if that does not work reset Data of the app.