This object is in archive!
Training schemes and hardware devices not started after reboot
Solved
Today I noticed that after changing a battery in the middle of a ride Locus didn't attempt to start bluetooth and later I noticed it didn't tell me how many kilometers I rode. Not connecting hardware devices wouldn't be that much of an issue as there's the bluetooth manager, but there seems to be no way to start a training scheme manually.
The same problem 
Good day Tomáši,
here is one important question. Imagine that you pause track record in the middle of the trip. Later you start it again (un-pause) : in this case, do you expect, Locus again connects to to defined devices and start certain training program? What if you already changed (temporary) some of these parameters, like you already stopped using some BT device, or changed training event to different one (use three dot menu to activate/disable certain training).
Because restoring track record after change of battery is exactly same as pause/un-pause. And because I'm quite unsure about how to do it in real, currently no reconnection happen.
I'll gladly listen more opinions on this topic.
2.
Good day Tomáši,
here is one important question. Imagine that you pause track record in the middle of the trip. Later you start it again (un-pause) : in this case, do you expect, Locus again connects to to defined devices and start certain training program? What if you already changed (temporary) some of these parameters, like you already stopped using some BT device, or changed training event to different one (use three dot menu to activate/disable certain training).
Because restoring track record after change of battery is exactly same as pause/un-pause. And because I'm quite unsure about how to do it in real, currently no reconnection happen.
I'll gladly listen more opinions on this topic.
2.
Well, to be entirely honest, from a user experience perspective I would expect Locus to remember whatever was active at pause/shutdown time and restore it on unpause/restart. From a devoloper perspective I'm afraid this might be too cumbersome (pause/unpause) or downright impossible without periodically saving current settings (shutdown/restart).
Anyway, I didn't notice that I could ativate/deactivate training schemes in the Training manager. I thought it's just a settings panel, not something I could use while on the road. With this in mind, would you mind adding a Training manager shortcut to this menu:
That would be quite a nice workaround. But at least I now know how to reactivate it manually, so thanks. :-)
Well, to be entirely honest, from a user experience perspective I would expect Locus to remember whatever was active at pause/shutdown time and restore it on unpause/restart. From a devoloper perspective I'm afraid this might be too cumbersome (pause/unpause) or downright impossible without periodically saving current settings (shutdown/restart).
Anyway, I didn't notice that I could ativate/deactivate training schemes in the Training manager. I thought it's just a settings panel, not something I could use while on the road. With this in mind, would you mind adding a Training manager shortcut to this menu:
That would be quite a nice workaround. But at least I now know how to reactivate it manually, so thanks. :-)
I was thinking about it and let's start in next version small improvement.
I've added small test, how much time left since last stored point. This test is done at start of Locus when some older, unfinished recording is found. I've also set limit to two minutes.
So, if you start Locus and last recorded point will be less then two minutes old, Locus will take a break in recording as "accident", recording start in active mode (so not in pause), and all defined auto-start actions starts also (sensors, training, live-tracking).
Otherwise, recording will be in "pause" as is not happen.
This should cover all cases, when you need a restart device or change a battery. What you think?
I was thinking about it and let's start in next version small improvement.
I've added small test, how much time left since last stored point. This test is done at start of Locus when some older, unfinished recording is found. I've also set limit to two minutes.
So, if you start Locus and last recorded point will be less then two minutes old, Locus will take a break in recording as "accident", recording start in active mode (so not in pause), and all defined auto-start actions starts also (sensors, training, live-tracking).
Otherwise, recording will be in "pause" as is not happen.
This should cover all cases, when you need a restart device or change a battery. What you think?
Seems okay, although I'm not sure if I can do it in 2 minutes. But we'll see. :-)
What about adding the Training manager to that menu, though? Don't you think that would be a good idea anyway?
Seems okay, although I'm not sure if I can do it in 2 minutes. But we'll see. :-)
What about adding the Training manager to that menu, though? Don't you think that would be a good idea anyway?
2 minutes are for first testing. We will see in practice. Colleague asked me "why to limit it at all, why not always automatically continue in recording" ... to be true, I have no clear opinion, so test in field shows.
About TM in menu - not sure to be true. I'll try to collect more ideas and mainly votes around training manager and then I plan some bigger improvement, so keep this in mind and when you'll see I started work on it, remind me this if you will still miss this button. Thanks for understanding.
2 minutes are for first testing. We will see in practice. Colleague asked me "why to limit it at all, why not always automatically continue in recording" ... to be true, I have no clear opinion, so test in field shows.
About TM in menu - not sure to be true. I'll try to collect more ideas and mainly votes around training manager and then I plan some bigger improvement, so keep this in mind and when you'll see I started work on it, remind me this if you will still miss this button. Thanks for understanding.
Okay. It's true that if this 2 minute fix will work I may not miss the button at all. :-)
Okay. It's true that if this 2 minute fix will work I may not miss the button at all. :-)
Well, my crap of a phone apparently can't even reboot within 2 minutes (judging from the fact I had to turn things on manually today), so if this feature should be useful, I'll need at least 5.
Well, my crap of a phone apparently can't even reboot within 2 minutes (judging from the fact I had to turn things on manually today), so if this feature should be useful, I'll need at least 5.
Hello Tomáš, five minutes? Well, here comes what I wrote before: "Colleague asked me "why to limit it at all, why not always automatically
continue in recording" ... to be true, I have no clear opinion, so test
in field shows" ... so what about set it to 10 minutes. it's still time you may spend on simple change of battery ... search for battery, open cover, change, close, start ..., so 10 minutes may cover it.
So next, version ...
Hello Tomáš, five minutes? Well, here comes what I wrote before: "Colleague asked me "why to limit it at all, why not always automatically
continue in recording" ... to be true, I have no clear opinion, so test
in field shows" ... so what about set it to 10 minutes. it's still time you may spend on simple change of battery ... search for battery, open cover, change, close, start ..., so 10 minutes may cover it.
So next, version ...
Okay, ten minutes should do it. :-)
Okay, ten minutes should do it. :-)
Replies have been locked on this page!