Training Manager does not start when the track record was previously enabled. Only together with the track record at the same time (Training auto-start).
This is a bug or a feature?
Good day Igor,
may you describe me more precisely how to simulate your problem? What happen when you tap on a training configuration in "Training manager" screen?
Good day Menion
To begin, here are the settings, just in case
Any other settings - with the same problem.
1. Turn on the GPS, track record and start to walk around. TM starts normally, before the first sound of the android.
(here I am talking about this)
...now I continue ...
2. Stop TM in "Settings-->Track Recording-->Training Manager" by taping on the profile name "Пешком 100м"
Repeatedly tap the name of the profile, it starts
But, the sound message is not received from him. All the sounds from the TM stops. Telephone generally continues to voice the remaining notifications as usual.
The same applies if the TM was not specified in the "Training AUTO-start", аnd it was an attempt to start the TM after track recording has already been started earlier.
...details does not happen :)
UPD: also, after a spontaneous stop TM repeated stop / start doesn't help. Sometimes you have to restart the entire Locus
thanks for a precise description. I've changed this topic to a "problem" and we should continue in discussion here (instead of two separated topics).
Issue you have is not usual behavior. I use Training manager a lot and usually together with navigation, music player, some special Locus notifications and never noticed such problem.
Currently only idea I have is to create a log by this method, right after problem occur, and we will see if in log will be any useful information, why this happen. Thanks
Good day, Menion
Used settings TM:
This journal, written immediately after stopping TM, as in the instructions.
Another example today.
I had to give root access to record the CatLog log. The settings are the same. Audio stream - Music.
thank you for your log. Unfortunately nothing useful was found there only some information that TTS is from certain moment not correctly initialized, but no information why.
May you please try this Locus Map Free Beta version: https://nas.asamm.com/share.cgi?ssid=0mEEY1W . I've made few modifications and mainly enabled a lot of logging about tts ( you will also see orange toast messages with read text ) . So if possible, try it and in moment you notice it stop work, create me please log again. Thank you!
Btw: really weird that you are till now only one, who has such troubles ...
It is preferable to bugreport.txt or from CatLog?
If you do not care, then CatLog is easier to read and handle. Thanks
Good morning, Menion
Sequence of events:
1. Started Locus, started recording the track yesterday profiles
2. Termination of voice notifications from TM
3. Start LogCat and save the whole log
Correctly I do?
Version Locus your new 18.104.22.168
perfect, thanks for a log. I think I've found it ...
On first line is information that your device memory manager (SPCM) decided to kill "Vocalizer TTS" engine. On second line is information from system TextToSpeech system, that it won't no longer work. Problem is that this information is not forwarded to Locus and in application it still looks that all is just fine. On last like is information that Vocalizer was terminated by system. Seems your device is really aggressive when we talk about terminating of applications.
So as first step, I should look in your device and put Vocalizer TTS to list of application excluded from termination or if you use any application that clear memory or some similar nonsense, please disable it.
No software optimizers, there is «Smart Manager» of samsung.
I froze it. TM now talked longer, but still stopped, after the incoming call - CatLog
And... other programs that use vocalizer it continues to work...(Talking clock, Shouter...)
Stop TM without any apparent external events, out of the blue. "Smart Manager" - frozen. CatLog
thanks for a logs. Situation is exactly same as before ... your device simply terminate TTS system and because Locus consider once initialized system as ready to use, it never try to initialize it again. I made a workaround for this, so Locus will now periodically test if something was spoke, and if not ( 3 failed attempts ), it will try to restart this TTS system.
So if possible, please try this beta version: https://nas.asamm.com/share.cgi?ssid=0ZJIMbq . So in case, Android again terminate TTS engine, Locus should after around 1, max. 2 minutes, restart whole system on background and it should start work again. So no panic, give Locus at least 2 silent minutes :). Thanks
Thank you, Menion
I will be tough test 8 version this weekend! By the way, that was done by me earlier:
- rooted device
- "froze" using Titanium Backup Smart Manager from Samsung (because his list of exceptions was not Vocalizer)
- updated VocalizerEx 22.214.171.124t --> VocalizerEx2 126.96.36.199t2
(tested with version Locus 188.8.131.52) and the number of stops dropped to about 10%, earlier it was 50/50 for 20 minutes. Thank you for taking so much efforts in solving my problem!
I am reporting a significant improvement TM operation stability. Tested throughout the week on versions 184.108.40.206 and 9.
It seems that the problem is solved. The pause of a few moments caught, but they did not interfere. "Smart Manager" was "unfreeze" in the active state
My immense gratitude!
Hello, glad to hear it. I still do not understand why it works as works, but fine that this auto-restart helps here.
Perhaps the solution is complex. Because my device only 1GB of RAM and too aggressive Android.
Also I by councils of the forum 4pda.ru:
And still - if not restart the TTS by the Locus... it is unlikely this would help :)
Comments have been locked on this page!