Join now - be part of our community!

Bluetooth issue with Android 8 :(

Tatty
Visitor

Bluetooth issue with Android 8 :(

Hi All

Sorry if I am going over a point that has already been covered but I have read most of the topics but I cannot see this issue being raised.

So I have upgraded to Android 8.

Every day I Bluetooth my phone to my car to play my music and take calls if needed.

My Car is a Ford Focus with Sync 2, prior to the “upgrade” my stereo picked up all my song titles and artists. 

Since the upgrade I keep getting unknown artist and song title, the only thing that has changed is my os.

This is also happening with my wife’s BMW mini (both 66 plate cars)

I have removed my phone a number of time and change the AVRCP version between the 3 options available.

All I can think is there is an issue with the Bluetooth not sending the metadata, as everything else works fine (phone, text messages etc).

Any ideas or fixes welcome as Sony Support have not been able to fix the issue and will not pass me over to the software development team.

Please Help

Thanks 

24 REPLIES 24
profile.country.fr_FR.title
Pod_Bol
New

Hi, 

I've the same problem, Sony France have no idea to resolve this. '' please reset your phone'',' 'restart your phone' '. They don' t listen what we ask, they just take our money. My next phone should be a Samsung. 

coconut3
Visitor

Hi, I got the same problem as you exactly...

Got a Ford Focus with Sync 2, was working fine with the Bluetooth Audio (showing song and artist name). But once update to Oreo then it always show Unknown...

Tried unpairing and pair again, not working.

Tried iOS and Nougat, both working fine.

Please help us!!!

ilmeseguer
Visitor

I have the same problem. My car is vw polo. I have this provlem with sony nougat and now with oreo is not repaired. Sony dont said anything about this and dont give us a solution. This is probably my last sony phone. I have all the z versions and anyone works perfect. 

profile.country.US.title
Qatrium
Expert

Try this workaround:

  1. Unpair both devices from each other.
  2. Go to Settings -> System -> About phone -> tap multiple times on "Build number" until you enable "Developer options"
  3. Go back to Settings -> System -> Developer options -> Networking -> Bluetooth AVRCP Version -> Choose AVRCP 1.4 or 1.5
  4. Restart your phone
  5. Pair devices and test.
JarNuu
Visitor

The workaround does not fix the problem at least with XZ Premium + Toyota Touch 2 with Go.

With AVRCP 1.4 I managed to play music that is stored on my device (not showing information). But music from Spotify or YouTube cannot be played. 

JBL Charge 3 and JBL 450BT headset started to play music (previously had problems with them as well) normally with all AVRCP versions.

 

profile.country.fr_FR.title
Pod_Bol
New

In developper mode I have the same issue. I read some musique, but the text don't change while I change song.

profile.country.fr_FR.title
Pod_Bol
New

Hi, 

After the reboot of my Phone, it's work. 

Developer mode Bluetooth 1.4

Thanks for the tips. 

Bluetooth 1.6 doesn't work properly. 

Tatty
Visitor

I have tried to 1.4,1.5 and 1.6

Music works in 1.4 fine  not 1.6

Still all unknown song title and artist even with them named correctly as they where on pervious OS 🙁

alexGolen
Visitor

It's funny but ever sinse I've upgraded to Android 7, my song data stopped from being displayed on my 2016 Mazda 3. I've had the Z3 back with Android 6 and everything was working fine, then once upgraded to Android 7 it stopped and I kept getting UNKNOWN artist, album and songs names... Same was with my Z5 when I had it. AND the same was with the XZP when I bought it.

The interesting thing is that it was still working all fine when I used to pair it with another car which was a Toyota Venza.

BUT once I upgraded to Android 8 on the XZP, it seems to have fixed this issue. SO, the conclusion here is that it really depends on the Car/Phone combination. The Oreo update broke it for some cars, but have fixed it for others... My advice - just get used to it and hope for it to be fixed in future OS updates...