Join now - be part of our community!

[Bluetooth] No track info on car head unit after Oreo update

shotfirer
Visitor

[Bluetooth] No track info on car head unit after Oreo update

DSC_0546.JPGBasically it's the same problem described here, but in my case it appeared after I upgraded my XP Dual to Oreo. When streaming music from my phone to my car audio via Bluetooth connection, instead of the current track metadata I'm seeing only an empty screen.  Audio stream is working, as well as next/previous track steering wheel controls. Play/pause button is working only for Pause, Play command is not working.

The solution from the XZ thread doesn't work for me. To be presice it works partially. Downgrading AVCRP to 1.4-1.5 does the trick only for the first song. For any track playing later I get "Unknown" in all metadata fields.

My car is 2013 Mazda CX-5 and I'm using Google Play Music as a music source. I've tried unpairing/repairing several times – no luck. It's very disappointing, that this problem seems to exits for a very long time, and exactly nothing was done to fix this.

3 REPLIES 3
shotfirer
Visitor

OK, despite that no one seems to care about that, I'll post a solution that (partially) solved the problem for me:

  1. Turn on Bluetooth
  2. Delete all pairings
  3. Turn off Bluetooth
  4. Go to Settings – Apps & notifications – App info – Three dots menu – Show system
  5. Clean data (not cache) for the Bluetooth, Bluetooth MIDI provider, btidd
  6. Reboot the phone (optional, but recommended)
  7. Go to Settings – System – Developer options (Google how to enable that)
  8. Scroll down to Networking – Bluetooth AVRCP Version. Set it to AVRCP 1.5
  9. Turn on Bluetooth, pair your device

You should be fine now. For older devices you could try to set AVRCP to 1.4.

Sometimes my car still losing it, displaying "Unknown" for all metadata and Play/Pause now working, which can be fixed only by reconnecting the phone. But since the same behaviour was observed under 7.1.1, I'd say it's not worse than before.

Sunsetblvd
Visitor

Yes. Works fine for my Audi A3 2015 after 6 months whit problem. Just change back to AVRCP 1.5

Thanks for help. 

Tangena
Visitor

Hi!

I had same issue on PIE and your solution solved the problem. Thanks