This object is in archive! 

Track recording doesn't get GPS fix every 60 seconds

Kevin Kaland shared this question 8 years ago
Answered

I tried turning on auto-GPS off since track recording is very battery-intensive. But I found that the GPS never seemed to come on. I had to turn off auto-off when screen on and have it manually get a fix. But I couldn't get the 60-second interval to work. What's a good way to troubleshoot this? Pro user.

Replies (8)

photo
1

Hi Kevin,


what are your other GPS auto-off settings? Max search time and min. accuracy?

photo
1

60s and 100m.

photo
1

Sometimes it happens that the device can't fix GPS position within those 60s. Try to prolong the interval

photo
1

Thanks, will try. Will I still get battery benefits with a longer search interval? When it's out of my pocket it gets a fix in seconds, but maybe it takes longer otherwise...

photo
1

Of course you will, however you should set the trackpoint recording interval longer than the search interval. And keep in mind that such settings influence the accuracy of your track recording - it's acceptable e.g. for mountain hiking when the movement is very slow and absolutely not suitable for e.g. cycling and faster activities.

photo
1

Hi again,


I tried playing with the settings, but no luck. No trackpoints were added unless I manually toggled GPS off/on.


Auto-off settings:


GPS and Location ->

GPS update interval: 60s

Min accuracy: 100m

Max. search time: 120s

Keep auto-off enabled; Checked


Track recording ->

Foot ->

Distance interval: 1m

Time interval: 60s

Recording conditions: Both

Required accuracy: 100m

Record only when moving: Off

Record when GPS is off: Off

photo
1

As I wrote before, set the trackpoint recording interval longer than the search interval. Another problem may be in the recording profile settings. If you have 1m, 60s and BOTH conditions it obviously rarely happens when these two conditions meet. Set e.g. 60s, 100m and select OR.

photo
1

Thanks. Why should the trackpoint interval be longer? Why is it rare that both conditions are met? It doesn't mean that I move 1m within 60 seconds?

photo
1

Kevin, In general android system menu: Gps (position) "Main switch" is ON ? Do not swith to OFF.

photo
1

The GPS auto on/off overrides your recording profiles settings so it's not necessary to have 60s interval between trackpoints if GPS is switched on once in 60s. As for conditions - in 60s you normally walk cca 60m so imagine the speed you should go if you want to meet both your conditions - 1m in 60s. Set your walking profile e.g. to 2m, 10s.

photo
1

Yeah, I figured that the main auto-off settings would take precedence. I'll try it again in "OR" mode on the walking profile with a longer search time...

photo
1

Yep. When I allow GPS while the screen is on, I have no issues. But it does not work while tracking with the screen off if I enable auto-off to take battery. It does work without auto-off enabled.

On 2 Mar 2016 18:46, "Locus Map" <locus.map@asamm.com> wrote:

photo
1

Is your Gps module powered on/off in the expected time sequences (60s) ?

Test 1. Using Locus screen ON. Test 2. Using Locus screen OFF.

1. Screen on: Gps power on/off (60 s) sequence monitored directly, see the "location Icon" activity in the top notion bar.

2. Screen off: Gps module on/off (60s) power monitor by app: Powertutor.

https://play.google.com/store/apps/details?id=edu.umich.PowerTutor&hl=nl

Powertutor: Start Profiler -> System viewer -> see Gps. In options (set number of data points) set record history size to the last 5 minutes. View previous gps on/off power activity while your screen was off.

As my phone in use has a large capacity battery I always use continuous trackrecord.

But I had 2 testrecords with gpsauto- off (60s)/screen off, both succesfull. Locus Screen ON/ OFF by the proximity sensor Locus display (de)activate. Warning: Resulting trackpoints are not generated in precise 60 sec segments. Sequence is set by: GPS off +60 sec -> Gps-on -> + wait position fix -> + wait to meet the accuracy condition -> = Point record !

1. Gps and Location:

-Disable when hidden: UNSET

-Track recording: Keep gps on when track recording is paused and screen off: SET.

-Gps auto-off / Gps update interval: 60s / Required accuracy: 30m / Max search time: 60s.

(set the required accuracy > 30m if a lot of expected points are missing.)

2. Track Record:

-Distance interval: 1m / Time interval: 1sec / Required accuracy: 30m / Recording conditions: Distance OR Time.

In attachment: Recorded gpx example tracks.

photo
1

@0709, screen on is fine. Not sure what's happening with screen off. Maybe I'll try Powertutor some time. Currently, I have just been recording without auto-off. It's too much work so far to get working, and ViewRanger for example manages to record tracks alright without using quite as much battery. I'll just remember to bring my mobile charger along with me when I can, and eventually I will probably use an external Bluetooth GPS.

photo
1

Succes, do not give up ! Should work.

photo
1

Kevin, I would check one more thing - does Locus have permission to access GPS in the device standby mode? Newer androids and android-based platforms have this additional settings for e.g. battery-saving modes etc.

photo
1

How do I check? I'm on a Samsung Galaxy S5 with Android 5.0. I know that they instituted a new runtime permission API at some point, and some apps moved to using that...but Locus has never asked me for any. Let me know.

photo
1

Locus does not have to ask for anything - in some devices it's just put automatically in some kind of battery-saving mode that doesn't permit access to GPS in standby mode. I don't own a Samsung so I don't know your particular situation - have a look at your settings > security or battery optimization or other similar if there is anything that might prevent Locus from functioning properly.

photo
1

Maybe +/- a similar problem as:

http://help.locusmap.eu/topic/gps-turns-off-when-screen-is-off

(I' m still running Locus on A 4.x versions only...no problems).

photo
2

True, maybe it is being optimized by Samsung's app optimizer thing. Supposed to save battery life. Let me try excluding it from that.

photo
1

btw, I did turn off the battery-saving functionality but it still didn't work screen off. So I dunno. I gave up and I just record all the time. I plan to get a Garmin watch or something eventually and use it over Bluetooth, which should be less battery-intensive.

Replies have been locked on this page!