Please login or register.

Login with username, password and session length
Advanced search  

Author Topic: MY19 GTS Bluetooth Profile/Capability/Codec Supported  (Read 934 times)

0 Members and 1 Guest are viewing this topic.

doitda

  • Newbie
  • *
  • Offline Offline
  • Posts: 7
  • www.CVOHARLEY.com
    • VA

MY19 GTS Bluetooth Profile/Capability/Codec Supported
« on: March 11, 2019, 10:18:28 AM »

Hey Guys. '19 CVO SG here.
I had a Samsung S8+ phone that worked fine over bluetooth for audio streaming.

I got a new Pixel 3 XL phone and was having issues with it constantly dropping the bluetooth audio streaming after 5-8 seconds. I could switch the GTS head unit to FM-mode and then back to Bluetooth, the bluetooth streaming would kick in again like it was playing the entire time, then crap out after several seconds again.
The song would continue to advance on the phone silently, thinking it was being played by the GTS, but in reality no sound was coming out of the bike.
The symptom was consistent with the GTS audio routing over the speakers or the included Sena 20s evo.
FM/AM worked as intended 100% of the time.

I am on the latest version of the GTS update released a few days ago in March.
I deleted the pairing from the head unit and the phone several times, and re-paired them with the same symptoms.

Techie-section:
I need to test some more, but may have found "some" type of fix (probably not optimal though).
I enabled the developer settings in my Pixel 3 XL and set the AVRCP from the default of 1.4 down to the oldest 1.3. Deleted and re-paired with the head unit and now the audio is consistent again like it was with the Samsung S8+ phone.

So does anyone know the bluetooth AVRCP version and codecs this '19GTS head unit supports? (1.4, 1.5, 1.6, LDAC, APTX/"-HD,AAC, SBC only?, etc..)



Thanks,
Chris

Logged

doitda

  • Newbie
  • *
  • Offline Offline
  • Posts: 7
  • www.CVOHARLEY.com
    • VA

Re: MY19 GTS Bluetooth Profile/Capability/Codec Supported
« Reply #1 on: March 11, 2019, 04:04:45 PM »

Yeah looks like the 19 GTS Boom only works with AVRCP 1.3.
Setting newer 1.4 (default), 1.5, or 1.6 the head unit won't work properly with Bluetooth streaming.
Old school 1.3 it is then..
Logged

ultrafxr

  • There are no sure answers, only better questions. - Dick Van Dyke
  • 5k CVO Member
  • ***
  • Offline Offline
  • Posts: 5465
  • No problem is so small it cannot be misunderstood.
    • TN


    • CVO1: 2020 FLHTCUTG Tahitian Teal
    • CVO2: 2017 FLHTKSE Palladium Silver/Phantom Blue/Wicked Sapphire-traded
    • CVO3: 2012 FLHTCUSE7 Electric Orange/Black Diamond-traded
Re: MY19 GTS Bluetooth Profile/Capability/Codec Supported
« Reply #2 on: March 11, 2019, 05:36:26 PM »

Holy chit.  I wish I knew WTF you were talking about.  Seriously I hope you get it figured out.
Logged



Places ridden on my bike from my driveway.
IBA member # 45520

doitda

  • Newbie
  • *
  • Offline Offline
  • Posts: 7
  • www.CVOHARLEY.com
    • VA

Re: MY19 GTS Bluetooth Profile/Capability/Codec Supported
« Reply #3 on: March 11, 2019, 09:14:24 PM »

Holy chit.  I wish I knew WTF you were talking about.  Seriously I hope you get it figured out.

Thanks, I got it figured out. The newer Google phones are embracing the newest bluetooth features.
In order to correctly pair a Pixel 3 XL with the latest firmware update to the '19 Boom GTS head unit, have to set the phone's bluetooth setting back to the oldest legacy AVRCP bluetooth setting; 1.3 (as opposed to 1.6, 1.5, or 1.4 versions).
If not, the head unit will stop streaming music from the phone's bluetooth connection.

This is specific to Harley's '19 Boom GTS unit, as the phone's will stream fine to mine and my friends cars using the later revisions of the avrcp versions.


https://en.wikipedia.org/wiki/List_of_Bluetooth_profiles#Audio/Video_Remote_Control_Profile_(AVRCP)

Here are some differences in the versions an Android 9.x phone can run:

Quote
AVRCP has several versions with significantly increasing functionality:

1.0 — Basic remote control commands (play/pause/stop, etc.)
1.3 — all of 1.0 plus metadata and media-player state support
The status of the music source (playing, stopped, etc.)
Metadata information on the track itself (artist, track name, etc.).
1.4 — all of 1.3 plus media browsing capabilities for multiple media players
Browsing and manipulation of multiple players
Browsing of media metadata per media player, including a "Now Playing" list
Basic search capabilities
Support for Absolute volume
1.5 — all of 1.4 plus specification corrections and clarifications to absolute volume control, browsing and other features
1.6 — all of 1.5 plus browsing data and track information[5]
Number of items that are in a folder without downloading the list
Support for transmitting cover arts through the BIP over OBEX protocol—For example, this profile is used in Fitbit Blaze watch to control music.
Logged
 

Page created in 0.131 seconds with 21 queries.