Audio cuttet via Bluetooth
-
Hello MRA User,
I have the Problem, that Audio commands via bluetooth a cuttet at beginning. When I use Audio Output via the iPhone speaker, everything works fine.
For sure it has to do with Delay to the Bluetooth device.
On other Apps you can set up a Delay for Bluetooth Audio.
Anybody Else with this Problem?
Thanks
Günter -
It happens to me with AA. Generally audio starts when the number of meters to next turn are almost gone, something like: "(in fortyfi)ve meters turn left".
-
I've the same problem in AA as wel in the car as on the motorbike.
-
Okay... I'm not the only one i see. I thought it was my (cheap Aliexpress) bluetooth headset... But apparently it is not. I never paid any attention to it or got frustrated about it since i assumed it was my headset causing this issue.
Love to see a fix!
-
Yes, I have already experienced this in alpha stage indeed, but we were unable to verify that this is unexemplary behaviour. In fact after some attempts to fix it, we were convinced the problem is down to my Ford Sync3 headend (which is known to be problematic in multiple areas...).
It would be nice to know with which Android Auto systems you are having this problem.
For the record, in my case: what happens is that the first syllables of any voice instruction are being cancelled. The audio duck (lowering the music volume) is done immediately before the first (wrong) syllable is audible (which is very abrupt, one second would be nice). After the voice instruction, it takes about 4 seconds for the audio duck to return to normal volume (which is far too long in my opinion). It happens ONLY when connected to Android Auto, with music coming from the headend itself (so NOT when your phone is the music source).
-
Mijn ervaring: als de autoradio in gebruik is slikt de routebegeleiding bij mij ook de eerste woorden in. Als ik muziek speel via spotify (android auto) dan wordt alle teks wel uitgesproken.
-
I remember the TomTom Rider days when you could still edit the audio files yourself. Some headsets also had this problem. The solution was to extend each audio file by half a second at the beginning. This was because the Bluetooth connection had to be established before the audio file was sent.
I don't know how much this helps. Nowadays, the announcements are generated by the smartphone itself. Perhaps you would have to open the channel first and then start the announcement with a delay. -
It's a frustrating issue indeed.
We verified that we do everything correctly (in theory)
I've delayed the start of the audio instructions by 1 second if you are connected to Android Auto but Android Auto almost seems to ignore this.
As users also indicate, the behavior differs depending on if you are listening to the car radio or to spotify. But we don't know what you are listening to.
We simply communicate to Android:- MyRoute-app wants priority
- Please "duck" (lower the volume of) other apps
- Wait 1 second (if connected to Android Auto) otherwise we don't add an extra wait
- Speak the instruction
- Tell the OS we are finished so other audio can gain priority again
This is how it should work and how it works well for a lot of users.
The whole ecosystem of Android, the amount of different (bluetooth) configurations, Flutter as development platform and our priorities simply don't help in getting this solved
-
It's a frustrating issue indeed.
We verified that we do everything correctly (in theory)I've delayed the start of the audio instructions by 1 second if you are connected to Android Auto but Android Auto almost seems to ignore this.
As users also indicate, the behavior differs depending on if you are listening to the car radio or to spotify. But we don't know what you are listening to.
We simply communicate to Android:- MyRoute-app wants priority
- Please "duck" (lower the volume of) other apps
- Wait 1 second (if connected to Android Auto) otherwise we don't add an extra wait
- Speak the instruction
- Tell the OS we are finished so other audio can gain priority again
This is how it should work and how it works well for a lot of users.
The whole ecosystem of Android, the amount of different (bluetooth) configurations, Flutter as development platform and our priorities simply don't help in getting this solved
@Corjan-Meijerink, Indeed, the 1 second pause did seem to help, but it is just not enough, for my specific case I mean. You absolutely cannot introduce a longer pause everyone not having this problem
My theory, not being held back by any knowledge, is that some AA devices simply do not honour the "wants priority" command, but listen to audio (voice) itself and decide (too late) to duck for themselves.the behavior differs depending on if you are listening to the car radio or to spotify.
Yes, but that is quite logical. When playing spotify (or anything else) from your phone, the media channel is continuously open. The phone ducks spotify, and not AA.
