T:TTS Service error, code -7

Graf Geo shared this question 20 days ago
Answered

I recently had a very strange problem with the voice output during navigation. When setting off on a planned hike, I launched Track Navigation as usual and an orange error message appeared: “T:TTS Service error, code -7”.

I tried the usual quick fixes: restarting the app, clearing the cache, restarting the device, moving the TTS file so that a new one would be created, and reinstalling the app, but none of it helped. This error message appeared every time I started the navigation.

In the end, we set off on our hike without any voice instructions; the navigation itself was working, just without the voice prompts. So I had to keep looking at the screen. After about an hour and a half, or 5 to 6 km, I suddenly and quite unexpectedly heard a voice instruction. A miracle cure? From that moment on, everything ran smoothly again, even after restarting the navigation or the app. So it seems to have been a temporary problem – hopefully a one-off. Nevertheless, I’d have liked to know what might have caused it. Attached is a screenshot of the message.

*** Translated with http://www.DeepL.com/Translator (free version) ***

Replies (2)

photo
1

Hi,

what version of Locus Map do you use?

This comment is in trash! Restore
photo
1

Last beta 4.36.1.2

But I don’t know if it’s down to the version. I’d already had it the day before, and there were no problems with the TTS then. And there haven’t been any since then either.

This comment is in trash! Restore
photo
photo
1

Hi,

the issue is on the TTS engine side. The -7 error means a network timeout, so you probably use network-dependent voice synthesis. Switch it to local, and the error shouldn't reoccur.

This comment is in trash! Restore
photo
1

Thanks for your reply. Hmm, where can I find that setting? According to the AI, it’s an Android setting, but I can’t find a ‘network/local’ option. The speech engine (Google) and language packs have always been installed correctly. A test in flight mode also works without any problems; voice instructions are given.


When I started the route where the error occurred, there really was no network connection. But that’s been the case on hundreds of routes before, and it’s always worked anyway. Sometimes I even navigate in flight mode; I’ve never had any problems. Strange.

This comment is in trash! Restore
photo
1

Maybe it was some accidental glitch. I suppose you can't simulate the problem again?

This comment is in trash! Restore
photo
1

No, it’s only happened this once so far. If it happens again, I’ll get in touch.

This comment is in trash! Restore
photo
Leave a Comment
 
Attach a file
You can't vote. Please authorize!