OBDLink CX connection issue / Missing BLE button for BYD Seal U (Android)

Dear ABRP Support Team,

I am writing to report a persistent issue trying to connect an OBDLink CX dongle to ABRP via BLE.

My Setup:

• Car: BYD Seal U (Design trim, 87 kWh)

• Dongle: OBDLink CX (officially recommended by you)

• Device: Android Smartphone

The Problem:

1. When selecting my actual car model (BYD Seal U) in the ABRP vehicle settings, the "OBD (BLE)" button is completely missing under the live data connection menu. I am only offered "Enode" or "Generic".

2. As a workaround, I changed the vehicle profile to the regular BYD Seal (Sedan), which successfully made the "OBD (BLE)" button appear.

3. However, when trying to connect the OBDLink CX via this button, the connection fails immediately every time with a standard error message ("OBD connection failed").

Troubleshooting steps I have already taken (Hardware is 100% fine): To rule out any user or hardware errors, I have thoroughly tested the setup:

• Hardware Check: The OBDLink CX works perfectly and connects when using the official native OBDLink app.

• BLE Channel Cleared: I ensured the dongle is not paired in the Android Bluetooth system menu. I also force-closed the native OBDLink app to ensure the BLE channel is completely free for ABRP.

• App & Cache Reset: I cleared both the ABRP app cache and the Android system Bluetooth cache.

• Permissions: ABRP has full permissions for "Nearby Devices" and "Location" (Always On).

• No Conflicts: I completely deleted my Enode connection in ABRP before attempting the BLE connection to avoid any session conflicts.

It seems that the ABRP app either lacks the proper OBD configuration for the BYD Seal U, or the workaround using the sedan profile gets rejected by the car's specific data structure.

Could you please look into this and advise on how I can get the OBDLink CX working with my BYD Seal U? Will there be an official BLE OBD profile update for the Seal U soon?

Thank you in advance for your help.