This object is in archive!
Improve new unknown GPS location messagebox
Solved
This warning message box may be displayed when Locus is started (introduced recently) to alert the user to invalid GPS location. But I don't think it is always working correctly.
- Sometimes after a week of phone turned off or at least no valid location the warning is NOT displayed.
- Sometimes after Locus exit, then run again "fairly soon" the warning IS displayed but I don't think it needs to be. What is the location cache timeout?
- Sometimes (as in screen capture below) the warning text could be improved (or not displayed) - no point saying "Consider enabling GPS" when the GPS IS enabled but is just waiting for the first fix - see GPS icon/button on right side is orange i.e. enabled. Suggestion - if GPS is enabled AND user has GPS icon/button on main screen there is no need for any warning because the color indicates the current GPS state.
The same problem 
Good day Andrew,
quite complicated question. Location has timeout 2 hours if I remember correctly. Anyway it is not cached in Locus, but is requested from Android system itself. So it should be some last cached location stored in device from GPS or from Network location (wi-fi, cell-id). This is answer on first two points.
Last one ... agree. In case GPS is enabled in Locus, it won't popup this dialog next time. Thanks.
Btw. I'm mark this topic as "solved" anyway I'm aware of issues in first two points. When I'll find/see/read some possible solution, I'll definitely improve it.
Thanks for sharing!
Good day Andrew,
quite complicated question. Location has timeout 2 hours if I remember correctly. Anyway it is not cached in Locus, but is requested from Android system itself. So it should be some last cached location stored in device from GPS or from Network location (wi-fi, cell-id). This is answer on first two points.
Last one ... agree. In case GPS is enabled in Locus, it won't popup this dialog next time. Thanks.
Btw. I'm mark this topic as "solved" anyway I'm aware of issues in first two points. When I'll find/see/read some possible solution, I'll definitely improve it.
Thanks for sharing!
Thanks for fixing point #3. Points #1 & 2 "on hold" than "solved" I think. Sub-optimal Android behavior.
Thanks for fixing point #3. Points #1 & 2 "on hold" than "solved" I think. Sub-optimal Android behavior.
Replies have been locked on this page!