GC-Offlinizer stops when phone goes to sleep

rvheddeg shared this problem 4 years ago
Solved

I was trying to use GC-Offlinizer at night (over Wifi). But this morning I see that it had only done 45 caches. It was frozen/crashed and I had to restart the phone.

When I retried this functionality, I need to babysit the phone, keeping the screen on, for it to work? I see now that while writing this post, the GC-Offlinizer has just stopped working. It stays with the same cache for over half an hour. I have Cancelled the operation, and restarted it, but I think this could be improved.

Could you enhance this plz?

"Use Live API" was always checked, in case this is important.

Comments (8)

photo
1

Hello,


understand. Please try it with next Locus version. It should be OK now.

photo
1

Are you sure it is OK? I must say that I don't understand the behavior. When using the Offlinizer (with Wifi) by family it works much better then at home (also Wifi). At home it stops regularly on some random cache. Most of them don't even have images...

The network is good I think, I'm using it constantly, even now for writing this post on my laptop.

I have done now a second test. I have enabled route tracking, in the hope that it will work better now. I'll keep you informed, but the following weeks I'm going on a vacation, so it will become harder to post.

Version 2.20.1.7 RC

photo
1

So even with new test version, there are still problems? In this case, it won't be probably problem that you phone goes sleep, but something different.


I rememeber I tried it on quite a lot of caches and no problem, but I'll rather do another test also. Thanks

photo
1

I activated track recording, and everything went smooth until Locus tried GC1QMVJ. It's not the only one where I have problems with, but this one seems to be causing trouble everytime.

photo
1

I have another geocache where the GC-Offlinizer fails: GC1PKR0Would you also take a look at the behavior of the GC-Offlinizer itself? After hitting upon these 2 geocaches the Offlinizer just stops, instead of giving an error and carry on.

photo
1

Thanks,


both caches has some images that are not stored on exactly that address and has some redirects to new location. But it seems not to work correctly. For me, Locus skip these images correctly, but it may be based on Android version. So shortly, it looks like issue in Android version more then in Locus code. I added automatic skip for such images, so please check it in next version. Thanks

photo
1

Just for your information, I'm using Android 4.4.2

photo
1

Hi,


I believe that in current Locus version it works ok. Yesterday I was just solving some issues with redirects (this case) in this topic http://help.locusmap.eu/responses/wms-problem and seems it helps also on mentioned problem here. So in current version it should work - Locus skip images that may cause troubles. In next version, Locus will also follow redirect request to new URL, so it should download more images then now