Turn-by-Turn Loses Audio While Navigating

music4all shared this problem 2 weeks ago
In Progress

Greetings. Also, congratulations and big thanks for Locus Pro -- best outdoor nav app ever. Now with a bit of a glitch though. Since my Galaxy S6 upgraded to Android Nougat, when I navigate my TCX Courses, I can hear the turn-by-turn instructions just fine for a while. Then, sometimes, the audio just gets lost, and I can no longer hear any text-to-speech voices.

This seems to happen whenever I go off course on real-time outdoor navigation. First, I hear the Locus warning beeps to let me know I'm going the wrong way... Soon, audio for Locus Pro is lost.

Other apps relying on text-to-speech also lose audio at this time, by the way. Interestingly, when I close Locus (completely close--not just clicking twice on the Back button, but by *also* clicking on the Recent Apps button, then on the Close All, or on the "X" for the Locus app specifically), then the other apps instantly regain text-to-speech audio (without having to close them first).

I can then re-open Locus, and audio for turn-to-turn navigation text-to-speech will be back to normal in Locus too. Ahem--until this problem happens again, that is; and then I must restart Locus once again, etc. Very annoying (and not great for navigation!).

I think someone else reported a similar problem on this support forum (their problem title: "No voice command when using navigation over GPX tracks" -- I use tracks from imported TCX Courses, but I imagine there is something in common between their GPX problem and the one I'm describing here. Hmm...).

Oh, by the way, in case you wonder: yes, I have aleardy gone into settings, and tried to switch between Media and Notifications audio streams. Same thing happens on both streams. Also, as you will notice in the explanation above, TTS works just fine, except temporarily, when this problem occurs with Locus.

Again, I only noticed this problem after my Galaxy S6 upgraded to Android Nougat. I wonder though... Maybe Nougat has nothing to do with this problem, and the glitch is really just something that started with a recent Locus update. Hmm... hmm... Maybe both Nougat and Locus? ;)

Either way, I would HUGELY appreciate it if you could please look into this asap. THANKS!

Comments (7)

photo
1

Good day,

firstly thank you for a precise bug report and sorry for a complications.

Best to fix this problem should be simulate it on my own device, which may be a problem here. Anyway we may try it. If you open settings for TTS in Locus ( settings > language ), what TTS engine and what language for Locus and TTS engine you use? ( best to just post screenshot of this "TTS settings screen" ).

photo
1

Hi Menion,

Many thanks for your quick reply. Here are the screenshots you requested (two, total, are attached). Let me know if you need additional info, any other screenshots, log reports, etc., and I'll gladly provide.

Cheers

photo
1

Hello,

you are using same ( I just use UK version ) localization as me and I'm sure it works correctly for me.

Oki, so it possible, try to simulate this problem and once it happen, please create a log by this method. There is no guarantee that in log will be something useful, but maybe it will. If not, I'll have to create for you special version that will print out more information into log file. Thank you.

photo
1

Ok, great. Give me a few days (it might take a little while, since I don't always know when this will happen--though it usually does occur as I described in my bug report, so that should make it a bit easier to replicate). As soon as I have the log ready, I'll send it your way. More soon. Thanks again, Menion!

photo
1

Hi Menion,

I created the log you asked for, by clicking on the locusmap.eu link you provided, and following the instructions under the section entitled: "Devices with Android 4.2 and higher." I then sent the log your way (again, per the instructions).

FYI, the Locus bug happened approximately 2 hours and 45 minutes after starting a ride that I did on Sunday, June 11. The ride was about 45 miles long. Shortly after the bug happened, I did go ahead and completely close Locus (per my original Locus bug report--i.e., not just by clicking twice on the Back button on my phone, but also by clicking on the Recent Apps button and then on the "X" for the Locus app).

As always, just just by completely closing Locus, the other apps were able to immediately regain audio for their text-to-speech capabilities. All other events on this June 11 Locus bug occurrence were pretty much identical to the bug report I wrote originally, but, should you need additional info on this, please feel free to let me know.

Thanks once more, and I look forward to hearing back from you.

Cheers

photo
1

Good day music4all,

firstly thanks for a log. Unfortunately I did not found anything useful inside ... well, it was expected.

Based on your description, I think that problem is that Locus gain focus on audio playback ( it means that Locus Map has priority in playing of TTS sound ), but for some reason, this "focus" is not disabled.

I've added into app few more checks and focus should be correctly disabled. I've also added in app few more error logs that should be printed in case of problem. So please try next version and if same issue happen, create for me a log once more. Thank you and sorry for a complications.

photo
1

Hi Menion,

You're most welcome for the log. Sorry to hear there was nothing useful in it. But I think you're correct when you suspect the issue might have something to do with audio focus. It certainly seems that way whenever it happens.

Big thanks for adding more audio focus checks and error logs. I'll be sure to try the next version. I'll keep you posted on how it all goes. And, if the same problem happens again, I'll be more than glad to create a log for you once more, yes.

Cheers