Jump to content

Blue Tooth Tag Support Broken after update of NOKIA 6 2017 (TA-1021) to Android 9


Lox68

Recommended Posts

The following fixed the issue:

1. Enable Developer options in Android 9

2. In Developer menu change AVRCP to v1.3 instead of default 1.4.

3. Turn off battery optimization for Bluetooth app in system settings.

Just now, Lox68 said:

The following fixed the issue:

1. Enable Developer options in Android 9

2. In Developer menu change AVRCP to v1.3 instead of default 1.4.

3. Turn off battery optimization for Bluetooth app in system settings.

Thanks for the update. Hopefully that might help Max track down and repair whatever Google did with Android Pie.

Andre

8 hours ago, Lox68 said:

2. In Developer menu change AVRCP to v1.3 instead of default 1.4.

3. Turn off battery optimization for Bluetooth app in system settings.

2. I'm or Oreo but only have AVRCP 1.5 or 1.6 over and above 1.4  ....

3. By the BT app, you mean Poweramp?

 

Ta

15 hours ago, dvhttn said:

2. I'm or Oreo but only have AVRCP 1.5 or 1.6 over and above 1.4  ....

3. By the BT app, you mean Poweramp?

 

Ta

On Oreo 8.1 I had no problems with BT tags on my BMW 3 touring (2015) so I never checked the settings in developer options.

By the BT app I mean the BT system service, only visible when you choose "Show System".

OK. Difficult to know if this is Poweramp or the radio I have (Kenwood KMM-BT302, a couple of years old but on the latest firmware). I've tried to reset the PA bluetooth settings to 'default' and the PA audio settings to 'default' (in Advanced Tweaks). I've tried all 3 AVRCP profiles I have in the developer settings on my phone (AVRCP 4, 5 and 6) but none of this gets me artist/track etc on my headunit. What did work briefly was when I did a hardware reset on my headunit which caused track info. to appear for a few moments after which it reverted to 'situation normal' which is showing track number and track run-time.

I'm leaning to the conclusion that it's actually the HU that's the problem, based on past experiences and the number of BT issues people mention online with BT and car HUs which turn out to be the HU fault. But if someone can convince me I'm wrong please step forward ...... 

31 minutes ago, dvhttn said:

OK. Difficult to know if this is Poweramp or the radio I have (Kenwood KMM-BT302, a couple of years old but on the latest firmware)

Have you tried disabling all the Android Auto features in PA?

Andre

11 minutes ago, dvhttn said:

Not seen any .......   hmmm ...  Any pointers to where they are? (I'm on 820)

Settings > Misc. May not solve your problem, but one or two people have reported turning them all off helps with BT data content.

Andre

2 hours ago, andrewilley said:

Settings > Misc. May not solve your problem, but one or two people have reported turning them all off helps with BT data content.

Andre

 

Right, found them. But no change. Still only trrack number and elapsed time on the display. Still leaning towards the HU though. It does work fine on the wife's Honda HU in her car. That runs on a custom version of Android 4.x ......

1 hour ago, dvhttn said:

Right, found them. But no change. Still only trrack number and elapsed time on the display. 

For what it's worth, my Hyundai BT car headunit displays only the track title and artist name, no track number or running time at all. And instead of the album name and cover art (both of which it shows in its local USB file player mode) just the BT device name (e.g. "Andre's Galaxy Note 3") is shown. Stupid design or what?

Andre

22 hours ago, maxmp said:

For Android it's usually resolved by unpairing and pairing the device (car headunit) again.

Probably not that as I have to repair every time I change ROMs on my phone. I've done this several times since installing PA 8xx but I'll try and remember to test this tomorrow. Thinking about it I don't 'delete' the pairing from the HU, just re-pair so I'll ensure I delete from phone and HU before the re-pair process.

On 3/19/2019 at 9:35 PM, maxmp said:

For Android it's usually resolved by unpairing and pairing the device (car headunit) again.

Nope. Deleted the pairing on my phone and turned BT off. Deleted the pairing from my car's HU then turned everything on and paired again. Still just the track number and elapsed time showing.

 

So, I did a little test. Cleared out the 'BT last processed commands' list first. I started PA with no BT devices nearby and chose a new track on 'pause'. Turned the car HU on and waited for it to connect to my phone (connecting is set to automatic but takes 30 seconds or so). Started the track and played about 5 seconds. Hit 'pause' on the PA screen on my phone then turned the car HU off. Below is the complete list of 'BT last processed commands'. There's always the chance that I'm doing something wrong/have something set incorrectly so I wonder if someone more knowledgeable with BT could point anything out? The HU is a Kenwood KMM-BT302.  Thanks.

==================
10:27:15.324 HeadsetPlugReceiver headset event
connection BT=true am mode=0
==================
10:27:21.896 HeadsetPlugReceiver headset event
connection BT=true am mode=0
==================
10:27:59.295 HeadsetPlugReceiver headset event
disconnection BT=false am mode=0 no_keep_notif_on_dscn=false
==================
10:27:59.299 HeadsetPlugReceiver headset event
disconnection BT=true am mode=0 no_keep_notif_on_dscn=false
==================
10:27:59.319 HeadsetPlugReceiver headset event
disconnection BT=true am mode=0 no_keep_notif_on_dscn=false

 

Just did more testing. Samsung Music also doesn't send track information to my HU, just the same track number and elapsed time. As the HU displays the correct information for a brief time after I hard reset it then I'm inclined to believe a HU issue.

  • 4 months later...

@dvhttn is other plays also fail with track info, then it's related to actual BT to HU connection and protocols and can't be fixed/worked around on app level. On Android app doesn't have direct access to AVRCP, instead there is another "userland" app (Bluetooth app) which receives track info via standard API and communicates with the BT device.

I got situation like that only after major ROM updates when (I guess) some stored BT data becomes invalid - re-pairing helps with that.

 

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...