This object is in archive!
Minimize when track recording withput extra question
Declined
I consider the extra question (Minimize or Stop&Exit) when pressing Back during track recording pretty annoying. Suggesting having this question optional, based on general setting, e.g. as follows:
Back press when track recording:
- always stop recording and exit
- always keep recording and minimize
- show question
Old version did not have thia extra question, it was more convinient to me (as I always need "keep recording and minimize" option).
Thanks for consideration. DanH.
I like this idea 
Good day Dan,
I have to ask, why you want to minimize Locus by back button, when all Android devices has also a home button, which serve exactly this purpose (minimize app)?
Good day Dan,
I have to ask, why you want to minimize Locus by back button, when all Android devices has also a home button, which serve exactly this purpose (minimize app)?
Good day Menion,
I ever thought its not the same, especially from power consumprion point of view. Home button minimizes the whole app, its still running on background and power consumption is higher. Back + minimize kills the application and keeps only the recording service running.
Actually I have not tested real difference recently, if any. Just ever thought its different. And battery life is important for long trips.
Good day Menion,
I ever thought its not the same, especially from power consumprion point of view. Home button minimizes the whole app, its still running on background and power consumption is higher. Back + minimize kills the application and keeps only the recording service running.
Actually I have not tested real difference recently, if any. Just ever thought its different. And battery life is important for long trips.
How "back" and "home" buttons works is something, developers has influence on. In case of Locus, I'm almost (99 %) sure, that if you try simple test
1. record at least one hour track only by track record widget
2. record same track over menu in Locus (while Locus is running but minimized)
battery consumption should be same, or at least really really close to same. I'm trying as much as possible, to disable all feature that may consume battery, when Locus is minimized. But truth is, that I never precisely tested it.
Anyway if only reason for your "idea" is battery consumption, I rather invest time to optimizing battery consumption in cases, when Locus is minimized by Home button.
Second part of this, is "how to do it". When you start record by widget, Locus only initialize service that records data (and few features around), but not main map core. Only when you start app by icon, map core is initialized. Anyway when you close Locus by back, there is no feature like "close map core". Android apps usually handle this "back" action automatically. But because I wants to be sure that Locus is really closed, Locus execute "kill" command on itself, so app is completely closed. So I wanted to say, that task you wants is also quite complicate to do for now.
Hope it is clear what I wrote. Thanks for understanding.
How "back" and "home" buttons works is something, developers has influence on. In case of Locus, I'm almost (99 %) sure, that if you try simple test
1. record at least one hour track only by track record widget
2. record same track over menu in Locus (while Locus is running but minimized)
battery consumption should be same, or at least really really close to same. I'm trying as much as possible, to disable all feature that may consume battery, when Locus is minimized. But truth is, that I never precisely tested it.
Anyway if only reason for your "idea" is battery consumption, I rather invest time to optimizing battery consumption in cases, when Locus is minimized by Home button.
Second part of this, is "how to do it". When you start record by widget, Locus only initialize service that records data (and few features around), but not main map core. Only when you start app by icon, map core is initialized. Anyway when you close Locus by back, there is no feature like "close map core". Android apps usually handle this "back" action automatically. But because I wants to be sure that Locus is really closed, Locus execute "kill" command on itself, so app is completely closed. So I wanted to say, that task you wants is also quite complicate to do for now.
Hope it is clear what I wrote. Thanks for understanding.
Thank you Menion! I may perform the real battery consumption testing,... let you know if any "strange" results...
Thank you Menion! I may perform the real battery consumption testing,... let you know if any "strange" results...
Replies have been locked on this page!