I was testing the first problem a few days ago and had no problems with it. What language for TTS are you using?
Second problem: were you able to simulate this issue more than once? Was the track really correctly recorded during the time you missed audio coach notifications? Just asking, because various system battery optimizations are hot topics these days.
ah you are right! Locus has a problem with reading negative elevation values. Fixed!
Second issue is hardly solvable to be true. What device are you using? "Camera" app is usually very "memory hungry" and seems that Locus is unable to keep alive on your device when you pick a picture. That's why you after tap on Locus in recent apps, see whole initialization process that happen only when app starts.
You may try to give Locus higher priority by menu > settings > misc > Locus as a service, but I'm worried, it won't help.
Good day Rogemar,
I was testing the first problem a few days ago and had no problems with it. What language for TTS are you using?
Second problem: were you able to simulate this issue more than once? Was the track really correctly recorded during the time you missed audio coach notifications? Just asking, because various system battery optimizations are hot topics these days.
Jiří M. aka Menion
Comments have been locked on this page!