Sudden change from GPS state fast to default

While I was out running yesterday OruxMaps, after about 1.5 hours, suddenly changed the track logging state from Fast to Default.
I happen to see this because I was near home and wanted to see how far I had been running. When I turned on the screen OruxMaps changed back to Fast state again.
In my log I see that every second a new track point is saved, but after about 1.5 hours only every 10 minutes a point is saved, until about 45 minutes later where I turned on the screen points was back to saved every second.
I had Default state configured to 10 minutes interval, this is why I was able to see the state change. Normally this is set to 2 second as recommended.
If you need I will send you the GPX file.

GammelGreggan wrote:While I was out running yesterday OruxMaps, after about 1.5 hours, suddenly changed the track logging state from Fast to Default.
I happen to see this because I was near home and wanted to see how far I had been running. When I turned on the screen OruxMaps changed back to Fast state again.
In my log I see that every second a new track point is saved, but after about 1.5 hours only every 10 minutes a point is saved, until about 45 minutes later where I turned on the screen points was back to saved every second.
I had Default state configured to 10 minutes interval, this is why I was able to see the state change. Normally this is set to 2 second as recommended.
If you need I will send you the GPX file.

Hi, thanks.

did you see 'restoring state' progress dialog when turned on the screen?

May be android killed OruxMaps, and it did not restored properly.

orux

I saw that OruxMaps changed map, I am not sure about restoring state.
But, if OruxMaps was shutdown, how come it logged a track point every 10 minutes as my default setting for GPS is?
Do you want me to send you the GPX file to verify the 10 minutes logging?
Looking on the track loaded to the map shows that OruxMaps has saved track points, the track log follows the road I was running on until after 1.5 hours when the track log shows straight lines between the points. This for for about 45 minutes when it starts following my road again.

GammelGreggan wrote:I saw that OruxMaps changed map, I am not sure about restoring state.
But, if OruxMaps was shutdown, how come it logged a track point every 10 minutes as my default setting for GPS is?
Do you want me to send you the GPX file to verify the 10 minutes logging?
Looking on the track loaded to the map shows that OruxMaps has saved track points, the track log follows the road I was running on until after 1.5 hours when the track log shows straight lines between the points. This for for about 45 minutes when it starts following my road again.

OruxMaps uses a Service to restart logging when android kills OruxMaps. This service has to do a lot of stuff, and (confirmed) it forgets to reload the previous fast/power save/default gps mode

It is not normal that android kills this service, but if this happens (android needs to release a lot of resources), the gps is not properly restored.

Working with this bug,

orux

Ok, I change my default GPS setting to 2 seconds to avoid this and wait for the solution.

Thanks for a superb app and your fast reply.

Yesterday I took another long run and this time I had set the default GPS tracking to 0 (always) and 20 meters.
I was using the fast setting, the trail took 2.5 hours.
Looking into the log I still see some parts where OruxMaps has missed to log every second, I see straight lines that looks like 3 to 10 minutes pause in the log, at 3-4 different occasions.

So, there seems to be some other problem with the service restarting.

I have uploaded the trip here: http://www.everytrail.com/view_trip.php?trip_id=1297826&code=197bc4c4af8606d518fec725e9e651fa

As you can see in the map there are some straight lines that shouldn't be there.

In earlier versions of OruxMaps I never saw this behavior, what could cause this now?
Changes in OruxMaps?
More apps in my phone running in background?

GammelGreggan wrote:In earlier versions of OruxMaps I never saw this behavior, what could cause this now?
Changes in OruxMaps?
More apps in my phone running in background?

Hi;

Android can kill OruxMaps if it needs resources for other applications (phone call, many applications running at once,...)

OruxMaps might not be alerted by android when killed. OruxMaps saves track points every xx minutes in the database (configurable in settings, tracks) by default every 4 minutes. If Android kills OruxMaps, you can lost the last 4 minutes, plus the time android takes to restart OruxMaps, which may be a few seconds, and the time OruxMaps takes to reacquire the gps signals.

This effect can be reduced by:
1.-Set to 1 minute 'auto save' value in configuration -- tracks.
2.-When using other applications while recording a track, OruxMaps always should be leave on top when you turn off the screen. Thus, OruxMaps have priority and will be the last to be killed.

Are you using the last betas?

orux

I am sure that OruxMaps was not in foreground, I thought pushing it to background only the track logging service was running and thus using less resources. Thanks for enlightening me, I have changed the save time to one minute as suggested.

From now on I will always have OruxMaps in foreground when putting the phone in standby.

Even if being a software developer I am not familiary to Android, I have never worked with this OS.
Thanks for your comprehensive answer.

I am not running latest beta, normally I do but this time I have not have time to install it. :-)
I will install it today.