switching off the display makes OSMTracker forget tiles

[PontiacCZ]

Screen 1: OSMTracker is tracking, all tiles in the current area are downloaded. Then I switch off the display to save battery...

Screen 2: after switching on the display I see this - couple of tiles are missing. OSMTracker reloads them, it takes some time and data from my data limit. In the end everything is loaded just like in the first screenshot. Then again I turn off the display...

Screen 3: ... to find out that after switching it on I have lost another tiles. And again, it starts reloading the missing tiles.

Sometimes when mapping I get to areas without service and then no reload can occur so I am a little bit blinded.

OSMTracker for Android v0.6.11
HW: Nexus 6 (Android 6.0.1)

[nguillaumin]

We use the OSMDroid library to draw the map, so it's quite certainly an issue with it, although I couldn't find a similar one in their bug tracker.

Since I lack the time to work on the app, it's unlikely to get fixed as I would need time to make a reproducible case for the OSMDroid guys...

[PontiacCZ]

Just wanted to let you know that I posted this problem to OSMDroid's issue list as well (see the link above) and obtained an answer which might be of some help. Not sure.

[nguillaumin]

Hehe, I was sure we would end up bouncing the issue between OSMTracker and OSMDroid 😉

Since I'm not the one who implemented the map view in OSMTracker, I have no idea how it's configured at our end. I'll have a look when time permits.

[nguillaumin]

Also, if you could:

• Try to export a track as GPX and confirm it works
• Go to the "About" screen, click on the debug button and paste the content here

Cheers.

[PontiacCZ]

1. I use OSMTracker about once a week, no problem with exported GPXs, they load into JOSM fine. So the GPX files exported from the OSMTracker definitely work.
2. I did tap on the Debug button and I guess it was supposed to export a diag file, but this is what I got instead:
   

[nguillaumin]

Thanks, that was what I was after. That confirms that there's no problem writing to the external storage.

There are a few updates on the upstream issue which seem to suggest it's indeed a bug with OSMDroid (they managed to reproduce it with a different application than OSMTracker). We'll see what happens...

[nguillaumin]

Upstream issue is now fixed, we'll have to wait for them to package a release, and update our dependency to the new version.

[PontiacCZ]

I've been watching the OSMDroid's issue as well. Looking forward to the updated version. :-)

[PontiacCZ]

Have they already packaged the fixed release?

[nguillaumin]

They have, I just upgraded it. I'll try to release soon.