Bluetooth Transmitter Latency

Uncle Phil

Uncle Phil

Site Supporter
Joined
Feb 26, 2007
Messages
10,936
Age
72
Location
In The Holler West Of Nashville, Tennessee
Bike
4 ST1100(s)
2024 Miles
029048
I've been fussing around with BT transmitters trying to find a good one that is USB powered.
I thought I had it but it appears that the BT 5.0 ones I had have some latency built in that I have not found in BT 3.0.
I had a BT 5.0 connected to a GPS testing out the voice interface.
It would play the GPS commands about 5-15 seconds after the GPS 'spoke' them.
As in "Turn Here" and you had already made the turn.
Or "Turn in 1,000 feet" and you were already at the corner.
Anybody else run into this?
 
Uncle Phil said:
I've been fussing around with BT transmitters trying to find a good one that is USB powered.
I thought I had it but it appears that the BT 5.0 ones I had have some latency built in that I have not found in BT 3.0.
I had a BT 5.0 connected to a GPS testing out the voice interface.
It would play the GPS commands about 5-15 seconds after the GPS 'spoke' them.
As in "Turn Here" and you had already made the turn.
Or "Turn in 1,000 feet" and you were already at the corner.
Anybody else run into this?
Click to expand...
I've heard of people complaining of Bluetooth latency in milliseconds, never in tens of seconds!?
 
Josh_ST said:
I've heard of people complaining of Bluetooth latency in milliseconds, never in tens of seconds!?
Click to expand...
Probably depending on the brand/product...
Comparing the SENA Freewire/SLR II combo stereo sound between fairing speakers and helmet headset (so 1x analog to BT, then 1x BT back to analog) gives some delay/echo...
Using a no-name/Chinesium BT dongle OTOH might cause higher latency due do "lame" chipsets...
 
Speed obviously has some affect but the delay is very noticeable - enough to be able to count from the 'screen' occurrence to the prompt.
I've got some old BT 2+ devices coming that I plan on trying.
Maybe it's something about the newer BT 5+ causing it.
I do remember someone on the board talking about latency with BT on their communicators.
 
Uncle Phil said:
I do remember someone on the board talking about latency with BT on their communicators.
Click to expand...
Some on the SENA FB-group complain heavily about latency from headset to headset in rider/pillion usage...
The BT protocols of the higher generations seem to require quite more CPU power to encrypt & decipher...
 
ST1100Y said:
Some on the SENA FB-group complain heavily about latency from headset to headset in rider/pillion usage...
The BT protocols of the higher generations seem to require quite more CPU power to encrypt & decipher...
Click to expand...
My hunch is that is the issue.
My older BT units did not do that so maybe these 'new' old ones will not either!
 
Is it posible to use an older protocol that does not use encryption? Disable encryption?

Another thought has to do with interference, if possible try without the engine running to test, maybe in a car
 
FWIW, here's what I think I discovered about it.
It appears that when a 'new' version of BT (like 5.0 and greater) tries to connect to an 'old' version of BT (like 2.0), it has to do some sort of 'recalibrating'.
Given all the other 'stuff' 5.0 is doing, that 'requirement' appears to be taking up extra time and causing the increased latency.
When I try to use a 5.0 with my 2.0 GPS systems, the latency makes it worthless.
When I used 2.1< with them, latency is minimal and it works fine.
At least that's my story and I am sticking with it! ;)
 
Uncle Phil said:
I've been fussing around with BT transmitters trying to find a good one that is USB powered.
I thought I had it but it appears that the BT 5.0 ones I had have some latency built in that I have not found in BT 3.0.
I had a BT 5.0 connected to a GPS testing out the voice interface.
It would play the GPS commands about 5-15 seconds after the GPS 'spoke' them.
As in "Turn Here" and you had already made the turn.
Or "Turn in 1,000 feet" and you were already at the corner.
Anybody else run into this?
Click to expand...
I've been experiencing frustrating latency with my Sena 50S, particularly when using voice guidance with Garmin and sometimes even worse with Google Maps. I have an Android phone and have tried using the 'Bluetooth Codec Changer' app to downgrade to a less CPU-intensive codec, which has helped somewhat.
Since, I also learned that it is possible to change the codec through the Advanced developer settings on Android without using an App.
I've used inexpensive Chinese Bluetooth headsets for years without encountering similar issues, including the annoying echo I often get with the Sena during phone calls. Hopefully, this information will be helpful.
While the Sena 50S mesh is excellent, I wish it didn't drain the battery so quickly. Even with moderate usage, it often runs out of power in less than six hours.
 
Sidekick said:
I've been experiencing frustrating latency with my Sena 50S, particularly when using voice guidance with Garmin and sometimes even worse with Google Maps. I have an Android phone and have tried using the 'Bluetooth Codec Changer' app to downgrade to a less CPU-intensive codec, which has helped somewhat.
Since, I also learned that it is possible to change the codec through the Advanced developer settings on Android without using an App.
I've used inexpensive Chinese Bluetooth headsets for years without encountering similar issues, including the annoying echo I often get with the Sena during phone calls. Hopefully, this information will be helpful.
While the Sena 50S mesh is excellent, I wish it didn't drain the battery so quickly. Even with moderate usage, it often runs out of power in less than six hours.
Click to expand...
A solution to the 'short' battery life of the Senas is a little 'charging' block you can slip into your jacket pocket and plug into the Sena charging port -


Yeah, the latency can make the GPS instructions 'too little, too late'.
Bluetooth is great until it isn't ... ;)
 
Here's some more 'interesting' stuff on the issue -

If the codec is not matched, then the configuration will immediately revert to SBC
(basic codec with the lowest audio quality), which is prone to audio delays.
For example when a pair of Bluetooth 5.3 headphones is paired with a Bluetooth 4.2 device,
it can only utilize the features of the lower Bluetooth version,
which will limit its performance, and the audio output of your Bluetooth headphones
will eventually have a higher latency.

So I guess my 'guess' was correct.
The issue I have is finding a BT 2.0 receiver that actually works.
I've tried several from Amazon and EBay with no success.
 
I have one of these with me that you're welcome to try, I'm hanging out with the camper at Switchback creek campground (Snake SToc) until the Wednesday of the BRG, then I'll be at the BRG, then on to Davis for WV-SToc.

smartbean-blue

smartbean-blue
www.antecmobileproducts.com www.antecmobileproducts.com

Their site says it's v3 o_O
 
You must log in or register to reply here.
Back
Top Bottom