TTS voice instructions in Guidance mode not always willing to talk
I have noticed an issue regarding guidance voice in GUIDANCE mode on Locus 3.20.1 and earlier versions. As I can recall, the issue is present on Locus for some time, a year or more. Here it is:
I prepare a route in GPSies web site on my PC, transfer it in Locus and load it from Map items screen. I don't import the route. Then I start Guidance mode with TTS voice instructions and I start recording.
What I have noticed is that sometimes the voice doesn't want to talk and keeps silent, either, for the whole trip/route or just a part of the trip.
Voice silent for the whole route/trip:
This is especially true and appears often (approximately in 30% of cases) if I start guidance mode when my current position is before the starting route point of the route (regardless of how many meters) or even after the starting route point but close to it (approximately from 0 to 30 m after the point). In that case, the voice doesn't start talking at all, from the very begging of the route. Furthermore, in that case, there is no way to force it to talk again for a longer period of time, hours and hours, even a day. An example of such a route with the corresponding recorded track is shown on the attached image A1.
I have tried everything possible to revive the voice: restart the route, restart the guidance, restart Locus, clear Locus cache, kill the task, restart the phone, reinstall Locus, reinstall previous version of Locus. No way to bring the voice instructions back and for that trip/route/day you are simply out of lack. On the next day, on a new route, the voice is back again by itself and you are again happy. It seems that Locus/voice somehow keeps memory of what (stupid) thing I did and punishes me by not talking instructions.
I really appreciate very much or better to say I am in love with the voice instructions in Guidance mode, either if I am hiking or biking. Particularly, if I am biking through a forest/wilderness with many turns and crossroads. It is much easier and helpful to listen to the voice than keep looking on the screen.
Question No. 1: is it possible to make that Locus, somehow detects that my position is before starting route point and doesn't attempt to start guidance instructions until I have passed the point ? If this question doesn't make sense for you, then, is there some other solution ?
Voice silent for a part of the route/trip:
There is also an additional issue with the TTS voice instructions in GUIDANCE mode. Let's imagine I am en route which I prepared in GPSies, and I have activated recording and TTS voice instructions in GUIDANCE mode. The route which I have drawn, is a two-way or a forward-and-backward route. To be clear enough, that means, the route is drawn from starting route point forward up to the ending route point and then backward in the opposite direction following the same path to the starting route point (see attached image B1).
When the guidance voice starts talking instructions, it works fine if I pass the whole route and visit all the route points, including the ending route point.
The problem is if I decide to go back before I pass all the way forward to the ending route point. In such an instance, Locus notifies me, with beeps, that I am out of route and afterwards, often (approximately in 50% of cases), the voice doesn't talk instructions at all on the way back to the ending route point. If that happened, I succeed sometimes (approximately in 50% of cases), in forcing Locus/voice to talk instructions again, by restarting the guidance mode and/or Locus (once or several times). An additional example of a similar, problematic route is shown on the attached image B2.
Of course, if I have a simple route, like the one shown by image B1, I can draw the route in just one direction. When I go back, I just activate reverse route guidance and I avoid the problem. However, if the route is a little bit more complex, and usually it is, like the one shown by image B2, the problem remains.
So, question No. 2: is it possible to make that Locus, when it detects my backward movement along the route (i.e. before I have reached the ending route point or before the farthest route point), assume that I have abandoned the rest of the route/trip and reverse guidance. I presume that Locus can decide on whether I have abandoned the rest of the route in three ways:
1. automatically by hard-coding a distance back (i.e. 200 m),
2. by detecting that my movement back has exceeded a value in user setting,
3. by asking the user (on-screen message/question plus a voice warning) whether she/he wants to abandon the rest of the route. Maybe there is some other solution ?
I have not tested above issues in Navigation mode, so I don't know if there is the same problem.
I have tested the issues on two different devices: LG G2 - D802, on android 4.4.2 and LG Optimus L7 II, on android 4.1.2. Exactly the same Locus settings on both devices.
From my viewpoint, those issues are of high importance since I am often in wilderness and always use Locus guidance mode. This is the reason why have I written a long story above.