Locus Pro switches back to online map
Hi,
I use Locus Pro with screen always on and with lock overrinding. It worked quite well for a while in the past. Then, with one of the updates, switching the screen on again become slightly problematic because the app had to reload itself and it took more time than earlier. Not always, but from time to time. This was only a bit disturbing but not a big problem.
Then from the last update on (3.21.0) the problem became more serious because the app also forgot the map when I switchde the srceen off. When I switched the screen back on, Locus showed only "Unknown problem" instead of the map. After a few occasions, I realized that it somehow switched back to an online map I used earlier (quite long ago, like months) even though when I switched it off, I was using an offline map. And, as I didn't have connection out in the field, it couldn't show anything. It still doesn't happen all the time but only at times (always at the worst moment, of course :-)). Mostly when I'm recording the track and I switch the screen back after a long time (like 40 minutes).
My phone is not the best in hardware, it's an Alcatel POP C1 with only 512 MB RAM but I used Locus Pro on it without problems for more than about a year. Could it be a memory problem? Should I revert back to an earlier version? (Ist there a way to do that?) I tried killing all other apps before starting Locus and also running Locus as a service but nothing helped yet.
This Saturday I go on a hike where it would be very important to use my Locus, so I hope you can help me.
The same problem 
Good day Péter,
sorry to hear about these problems.
You wrote that "app had to reload itself" ... this definitely means that Locus Map was killed by system while it was at background. It is not usually a problem of low RAM memory, but more it's by an aggressive system or by any 3rd party app that may do such problems. Mainly in case, you have enabled "Locus as a service" or during "track recording".
I do not know what Android version you use, but we have collected some commonly used settings in Android, that may help with this problem. Check here. Most of them is anyway valid for Android 5+ or 6+.
Aren't you using any memory optimizer app or something that may work with running applications? It may be source of troubles.
Hope this helps You!
Good day Péter,
sorry to hear about these problems.
You wrote that "app had to reload itself" ... this definitely means that Locus Map was killed by system while it was at background. It is not usually a problem of low RAM memory, but more it's by an aggressive system or by any 3rd party app that may do such problems. Mainly in case, you have enabled "Locus as a service" or during "track recording".
I do not know what Android version you use, but we have collected some commonly used settings in Android, that may help with this problem. Check here. Most of them is anyway valid for Android 5+ or 6+.
Aren't you using any memory optimizer app or something that may work with running applications? It may be source of troubles.
Hope this helps You!
Hi Menion,
My Android version is 4.2.2 and I don't use any memory optimizers, battery savers and other apps like that. But I didn't have this problem with earlier versions of Locus Map. Was there any enhancements in the last few upgrades that could cause such behaviour?
Hi Menion,
My Android version is 4.2.2 and I don't use any memory optimizers, battery savers and other apps like that. But I didn't have this problem with earlier versions of Locus Map. Was there any enhancements in the last few upgrades that could cause such behaviour?
Good day Péter,
I'm sorry to hear about such problems. I have to say that I no more use Locus Map in the field with Android 4.x device, anyway because by stats, almost 40% of users still use Locus Map on 4.x devices, this seems to be unicate problem on your device.
Unfortunately there is no known method to me, how to keep Locus Map itself more alive. So one option is to check if there is any extra settings in your device (usually in "battery settings"), how to keep Locus Map alive. Second option is that I may send you some older version (needs to know how old or which version), that you may use.
Good day Péter,
I'm sorry to hear about such problems. I have to say that I no more use Locus Map in the field with Android 4.x device, anyway because by stats, almost 40% of users still use Locus Map on 4.x devices, this seems to be unicate problem on your device.
Unfortunately there is no known method to me, how to keep Locus Map itself more alive. So one option is to check if there is any extra settings in your device (usually in "battery settings"), how to keep Locus Map alive. Second option is that I may send you some older version (needs to know how old or which version), that you may use.
Hi,
I've been heavily testing Locus in the last few days and tried different things. I moved the app from the sd card to the phone memory. Then I deleted the Turistautak_Classic.sqlitedb and .sqlitedb-journal files from Locus' mapsOnline directory. (The map of turistautak.hu is the online map that comes on from time to time.) These did not help, the problem still occurs. (And the deleted files came back automatically.)
I think the first problems occured two updates earlier (problem: app reloading when screen switched back) and then became more serious with the last update (problem: app reloading + switching back automatically to online map). So I would need the version that was published two steps earlier. I don't know the number, sorry.
You can send it to my Gmail address that is banindr. Thanks for your great support!
Hi,
I've been heavily testing Locus in the last few days and tried different things. I moved the app from the sd card to the phone memory. Then I deleted the Turistautak_Classic.sqlitedb and .sqlitedb-journal files from Locus' mapsOnline directory. (The map of turistautak.hu is the online map that comes on from time to time.) These did not help, the problem still occurs. (And the deleted files came back automatically.)
I think the first problems occured two updates earlier (problem: app reloading when screen switched back) and then became more serious with the last update (problem: app reloading + switching back automatically to online map). So I would need the version that was published two steps earlier. I don't know the number, sorry.
You can send it to my Gmail address that is banindr. Thanks for your great support!
Oki, so please try these versions (I'm sending two just for sure):
3.18.9, 29. 8. 2016, download
3.19.0, 12. 10. 2016, download
Hope this helps.
Oki, so please try these versions (I'm sending two just for sure):
3.18.9, 29. 8. 2016, download
3.19.0, 12. 10. 2016, download
Hope this helps.
I removed the app, deleted all its directories I found and then reinstalled it (the actual version) but the problem came back. So now I tried it with 3.18.9 and I'm testing it.
To make things easier, I put the quick map switcher icon into the right panel, so if it switches maps, I can easily switch it back. (Well, it won't be that easy with my frozen hands in the –15 °C that's forecasted for Saturday night but I will try. :-))
Thanks again! I will come back to you with any news.
I removed the app, deleted all its directories I found and then reinstalled it (the actual version) but the problem came back. So now I tried it with 3.18.9 and I'm testing it.
To make things easier, I put the quick map switcher icon into the right panel, so if it switches maps, I can easily switch it back. (Well, it won't be that easy with my frozen hands in the –15 °C that's forecasted for Saturday night but I will try. :-))
Thanks again! I will come back to you with any news.
Hello Péter,
oki fine.
I may improve remembering of maps after Locus is terminated, this is possible (currently last map is stored when Locus is correctly closed) anyway it won't solve main problem = that Locus is completely closed by system and needs to reload again.
If you wants to invest it little more, it should be possible to create a log by this method, right after you notice that Locus was again "killed". In log should be (no guarantee) some useful information from system, why Locus Map was closed.
Hello Péter,
oki fine.
I may improve remembering of maps after Locus is terminated, this is possible (currently last map is stored when Locus is correctly closed) anyway it won't solve main problem = that Locus is completely closed by system and needs to reload again.
If you wants to invest it little more, it should be possible to create a log by this method, right after you notice that Locus was again "killed". In log should be (no guarantee) some useful information from system, why Locus Map was closed.
Update: I reverted back to 3.18.9 -- and it's working wonderfully! Locus comes back instantly after switching screen on and it keeps the offline map just as it should. I used it Saturday night on a 7-hour night hike and it never let me down, track recording also worked fine.
So it must be a problem with the new version (3.21.0). I haven't checked 3.19.0 yet but I'm planning to test that version too. I also want to go through the change logs to see if I can see something that corresponds to my problem.
I will come back to you if I have any news. (I see we're already at 3.21.1 since then. I will test that one too.)
Update: I reverted back to 3.18.9 -- and it's working wonderfully! Locus comes back instantly after switching screen on and it keeps the offline map just as it should. I used it Saturday night on a 7-hour night hike and it never let me down, track recording also worked fine.
So it must be a problem with the new version (3.21.0). I haven't checked 3.19.0 yet but I'm planning to test that version too. I also want to go through the change logs to see if I can see something that corresponds to my problem.
I will come back to you if I have any news. (I see we're already at 3.21.1 since then. I will test that one too.)
>> Péter Wolf: Peter, are you sure with problems with the beta?
>> Menion: I have more worked this weekend (20km track, ~6hours, pauses,..) with the beta and for me on A4.2.1 it works excellent (same like 3.18.9):
- Locus offline map is stable (no unwanted change to default online map),
- GPS works stable in Track recording
- the map stays always on top (with Power Off + Power On)
3.18.9 + this beta: excellent
3.19-3.21: fatal broken
>> Péter Wolf: Peter, are you sure with problems with the beta?
>> Menion: I have more worked this weekend (20km track, ~6hours, pauses,..) with the beta and for me on A4.2.1 it works excellent (same like 3.18.9):
- Locus offline map is stable (no unwanted change to default online map),
- GPS works stable in Track recording
- the map stays always on top (with Power Off + Power On)
3.18.9 + this beta: excellent
3.19-3.21: fatal broken
Maybe my problem is that I'm not sure what I have really tested:
I have reinstalled without completly remove settings (locus folder structure).
I am pretty sure that I have installed the 21-beta but I remember I haven't no starting dialog for new version (my meaning was: this is normal for the beta). Now I have found in Menu, About app.. the version 3.18.9.
If somebody will test later, please be sure that starting dialog with text "this is testing version valid until.." appears and in the Menu, "About..." you really have 3.21 BETA.
Now I have reinstalled to 3.19 and then to 3.21-beta. Now I received initial "beta warning text" and version in About is 3.21-BETA.
However, in first minutes 3.21-BETA behaves good too - we will see later.
....... + 20 minutes:
still behaves good. But in Menu, About now displays 3.19 !!!! Crazy !!
Maybe my problem is that I'm not sure what I have really tested:
I have reinstalled without completly remove settings (locus folder structure).
I am pretty sure that I have installed the 21-beta but I remember I haven't no starting dialog for new version (my meaning was: this is normal for the beta). Now I have found in Menu, About app.. the version 3.18.9.
If somebody will test later, please be sure that starting dialog with text "this is testing version valid until.." appears and in the Menu, "About..." you really have 3.21 BETA.
Now I have reinstalled to 3.19 and then to 3.21-beta. Now I received initial "beta warning text" and version in About is 3.21-BETA.
However, in first minutes 3.21-BETA behaves good too - we will see later.
....... + 20 minutes:
still behaves good. But in Menu, About now displays 3.19 !!!! Crazy !!
I'm sorry for crazy mistakes. I have now 2 Locus installations:
3.21.1-BETA has FREE icon, in application list Uninstall IS accessible.
3.19 has PRO icon, in application list Uninstall ISN'T accessible. Why is Uninstall not possible ??
My standard icon launches in this situation 3.19 version. Didn't you make similar mistake, Peter? Have you really clean reinstalled? Can you confirm that in Android application list you haven't Locus twice? (of course only I do such stupidities, but I'm asking to be 100% sure...)
I'm sorry for crazy mistakes. I have now 2 Locus installations:
3.21.1-BETA has FREE icon, in application list Uninstall IS accessible.
3.19 has PRO icon, in application list Uninstall ISN'T accessible. Why is Uninstall not possible ??
My standard icon launches in this situation 3.19 version. Didn't you make similar mistake, Peter? Have you really clean reinstalled? Can you confirm that in Android application list you haven't Locus twice? (of course only I do such stupidities, but I'm asking to be 100% sure...)
Hello guys,
I'm closing this issue, discussion may continue here, it is a same issue. Current problem with incorrect map after open, is because Locus Map is terminated meanwhile, not because of incorrectly remembered map. Thanks for understanding.
Hello guys,
I'm closing this issue, discussion may continue here, it is a same issue. Current problem with incorrect map after open, is because Locus Map is terminated meanwhile, not because of incorrectly remembered map. Thanks for understanding.
Replies have been locked on this page!