Navigation instructions are disabled under certain conditions
-
I don't know if this is related to one of the new versions or if it's an old problem.
Here's what happened today: I connected my Sena 30k headset to my iPhone as the first phone. The second phone connected is the Oukitel RT3 tablet (with MRA for navigation).
Everything works very well so far.
But when I establish a Bluetooth connection to my freind, I can no longer hear the navigation instructions.
At first, I thought, OK, the Sena headset can't connect to three Bluetooth devices.
But then I received a warning from my speed camera app.
This means that the BT connection from the Oukitel tablet is active after all.
So why are no navigation instructions coming from MRA?
When we later reached a via point, it was announced by MRA without any problems.
The question now is, why does MRA differentiate between a via point announcement and a navigation instruction? Why are via point announcet and turn instructions not?Do these announcements have a different priority in the Bluetooth protocol?
When I cancel the connection to my friend everything works fine.
Hardware
iPhone 12 pro (iOS 180.2)
Oukitel RT3 (Andr. 12)
Samsung XCover 4 (Andr. 9 Pie)
Wireless CarPlay mit (Elebest C650)
Wired CarPlay (SEAT Arona - 2021)
For more information, (Workshops) click here -
Nobody an idea?
I noticed this again yesterday during the tour.
I am not a Bluetooth specialist and can only guess how the technology works. It is also interesting to note that when the speed camera warning system makes an announcement and the BT channel (mobile phone with MRA to headset) is open, you can briefly hear the turn announcements from MRA.
However, MRA cannot open the channel for an announcement on its own. Unless it is a Viapunkt notice. For me, this means that Via announcements use different technology to turn announcements.
I know this is probably a minor issue, but shouldn't all announcements from MRA have the same priority? -
I am not sure there are priorities in the app announcements at all. It is more likely that Sena prioritizes certain channels, and I find it quite logical that intercom gets priority over Navigation. You could try to reverse the pairing order.
-
I don't know if this is related to one of the new versions or if it's an old problem.
Here's what happened today: I connected my Sena 30k headset to my iPhone as the first phone. The second phone connected is the Oukitel RT3 tablet (with MRA for navigation).
Everything works very well so far.
But when I establish a Bluetooth connection to my freind, I can no longer hear the navigation instructions.
At first, I thought, OK, the Sena headset can't connect to three Bluetooth devices.
But then I received a warning from my speed camera app.
This means that the BT connection from the Oukitel tablet is active after all.
So why are no navigation instructions coming from MRA?
When we later reached a via point, it was announced by MRA without any problems.
The question now is, why does MRA differentiate between a via point announcement and a navigation instruction? Why are via point announcet and turn instructions not?Do these announcements have a different priority in the Bluetooth protocol?
When I cancel the connection to my friend everything works fine.
@Jörgen I'm also not a (Bluetooth) specialist, but I'm willing to help.
And sorry, I'm currently not able to test it because of seasons end.
But I slightly remember, I had similar issues with my Sena 30K. I solved it by connecting my Navi at first, later my Phone as second (if necessary). The Intercom to second Sena 30K to my Sozia wasn't affected.
My priority is to get navigation instructions. The intercom smalltalk with my Sozia has lower priority and may blocked/interrupted by navigation. The Phone may is connected primarily to be able to receive traffic information for navigation App. Friends/ team mates are connected by Mesh.
