Live geocaches no longer work.

I just emailed the log file(s) as is occurred again.

I am using Locus 3.31.1 and geocacing4locus 2.2.4.

Hello Jan,

Sorry for later answer, I was off a few days.

Anyway I don't see any issue on Geocaching4Locus add-on side. From logs you send me is seen that periodic updates from Locus Map was successfully received by add-on, that's ok. Next I see 4 attempts to send Live map geocaches to Locus Map, first with 0 geocaches because Locus Map has been sent to background before finish, next three attempts sent 31 geocaches to Locus map without any crash or error.

@Menion Do you have any idea what could go wrong on the Locus map side?

App versions:

Locus map Pro 3.31.1

Geocaching4Locus 2.2.4 (latest one)

Hmm as I think about it, only possible problem should probably be that G4L send data to incorrect version of Locus Map app.

Jan, do you have installed both (Locus Map Pro, Locus Map Free (Beta)) at once? If so, suggest to try to un-install Free/Beta version if it helps.

I currently have Locus Map Pro, Locus Offline Maps, Locus Map Tweak, GSAK Database, and Geocaching4Locus installed.

I verified that GC4L is downloading data by monitoring the data usage per app, and when panning the map, the amount of data transferred by GC4L indeed increases.

After killing Locus and restarting it, the live maps work. Until some time later when the problem reoccurs.

So I think you are right that GC4L is downloading the data, but not sensing it correctly to Locus itself. Is there logging in Locus Pro such we can verify if the data is actually transferred between the different processes?

Jan, you wrote also in your previous post that "When opening Locus after a while (not closing it, just running in background), the GPS appears suddenly off and the live map problem occurs.". When you open Locus like this, also initialization dialog appear? It looks like Locus is completely terminated by your system (when put to background), is it possible?

May you please try to enable settings > misc > Locus as a service option in Locus Map, if this makes a difference? Thanks.

I see only possible problem if app incorrect set inner parameter "is running" to correct value. Should not happen, but ...

Hi guys. I have the same issue, or similar, because for me, Live map is not working at all :(... I believe it is since last Locus update, but that is not for sure. When I turn on live map, usually there is a new icon in status bar indicating it is doing something /downloading caches/, but now, it does not appear there at all (not even for a second). Restart of Locus does not help, restart of the phone either. I have noticed this issue about 4 days back and it is still the same. I have Locus Pro 3.32.2 and G4L 2.2.6 (17878f9), Honor 8. I am using option "Run Locus Map as service" since always and "Connect with add-ons" (periodic updates) is also enabled. I tried to disable/reenable it, no difference....

Nearest caches option works correctly. Anything else you want me to try?

Hi skubko,

Could you try this one if it helps?

https://geocaching4locus.eu/users-guide/live-map#toc-issue-live-map-doesn-t-work

Well, I have EMUI 5.0.3, but none of those options are available on my phone. Anyway, I know about one particular setting (that I have off because of tracks in Locus) - Ignore battery optimization, but that one is enabled for both, Locus and G4L. So, in this way, G4L is "protected" that the system will not kill it in order to save the battery. So, that did not help apparently.

But, good news, while I was playing around with setting, I found one that helped me and now Live map is working again! However, that setting does not sound logical at all (at least to me), but I am glad it helped.

Settings -> Apps ->Geocaching4Locus -> Battery -> Close after screen locked.

Recently I was playing with this setting and I enabled it for many applications (which can be closed after screen is locked). For whatever reason this caused G4L Live map to stop working. When I disabled it now, Live map is working back again! Again, it does not seem logical, because I am not locking screen, so I do not understand why it should kill the application but I am glad it helped. I will probably review my other apps now and will disable that option back as it can cause issues like this :(...

I am glad it works now! Anyway thanks for hint. I added it to app User's guide.

I am glad it works as well, thanks for the hint (to look for some particular settings) ;)