This object is in archive!
Map nearly stuck at zoom level 16 and above on Android 7
Closed
I upgraded my LG G5 to Android 7.0 last night. Since then Locus gets nearly stuck when zooming to level 16 and higher. My Note 3 (Android 5) with same, latest Pro and Beta does not show this problem.
The LG with Android 6 did not have the problem either.
The same problem 
Hi Michael,
with which map?
on my old SGS2 CM14 with Locus free i see no problem with e.g. locus vector map >ZL 22, or online google satellite >ZL20
Hi Michael,
with which map?
on my old SGS2 CM14 with Locus free i see no problem with e.g. locus vector map >ZL 22, or online google satellite >ZL20
Finnland and Sweden.
Both, online Google and Google Hybrid, and also the two OAMs.
In the South this problem does not appear.
And also not on my old Galaxy Note 3.
Weird.
Finnland and Sweden.
Both, online Google and Google Hybrid, and also the two OAMs.
In the South this problem does not appear.
And also not on my old Galaxy Note 3.
Weird.
In Romania (OAM, latest Elements theme), the issue starts at level 17
In Romania (OAM, latest Elements theme), the issue starts at level 17
There is a long standing issue with track styles... using anything but a plain line will slow Locus to an unusable crawl at high zooms. Maybe you have one of those and its not related to the map at all... just an idea. Or the render theme uses something similar in code to track styles for rendering on Android 7...
There is a long standing issue with track styles... using anything but a plain line will slow Locus to an unusable crawl at high zooms. Maybe you have one of those and its not related to the map at all... just an idea. Or the render theme uses something similar in code to track styles for rendering on Android 7...
Hello Michale, what means "stuck"? Locus map just slow down to unusable state, or you directly see some force close message?
If issue happen with some online Google maps, does it happen with all other online maps as well? Because it should then ...
Hello Michale, what means "stuck"? Locus map just slow down to unusable state, or you directly see some force close message?
If issue happen with some online Google maps, does it happen with all other online maps as well? Because it should then ...
Extreme slow down. You are at ZL 15, tap "+" and it takes very long for ZL 16 to be drawn. Moving the map - same.
Go back to ZL 15 and below, rushes like a charm. I used OSM instead of Google - same problem.
And it is not restricted to Skandinavia.
EDIT: But in Romania and Germany, the problem kicks in at ZL 17, not 16. I.e. map size does not matter.
And it is independent from the theme: I tested Locus internal, classic (which is light weight), Elements or Elevate - all come to near stand-still.
EDIT: Solved. The maps were from April, and it seems the new theme killed it. All fine again. Sorry for the confusion.
EDIT: Problem is back. NO idea what the hell is different in Android 7.
EDIT: The probelm occurs without and with overlay maps, regardless.
Extreme slow down. You are at ZL 15, tap "+" and it takes very long for ZL 16 to be drawn. Moving the map - same.
Go back to ZL 15 and below, rushes like a charm. I used OSM instead of Google - same problem.
And it is not restricted to Skandinavia.
EDIT: But in Romania and Germany, the problem kicks in at ZL 17, not 16. I.e. map size does not matter.
And it is independent from the theme: I tested Locus internal, classic (which is light weight), Elements or Elevate - all come to near stand-still.
EDIT: Solved. The maps were from April, and it seems the new theme killed it. All fine again. Sorry for the confusion.
EDIT: Problem is back. NO idea what the hell is different in Android 7.
EDIT: The probelm occurs without and with overlay maps, regardless.
Hello Michael,
this will be more complicated. I do not yet have device with Android 7, so I'm testing it only on emulator and there I do not see any issue.
May you please enable some basic online map, like "OSM Classic", play a while with it till it starts to slow down a lot, and then create for me a log? Thank you!
Hello Michael,
this will be more complicated. I do not yet have device with Android 7, so I'm testing it only on emulator and there I do not see any issue.
May you please enable some basic online map, like "OSM Classic", play a while with it till it starts to slow down a lot, and then create for me a log? Thank you!
Funny turn today: I had copied tons of new OAM files from PC to the LG yesterday, plus the new Ele* themes.
This noon I saw that many maps from Europe had not be copied (Finland and Romania amongst them ...). So in fact I ran a combination of new Ele themes and old OAM files from April, which seems to make trouble in high zooms
With the new OAM files and themes all is fine.
LoMaps and their themes are also fine.
Also Online maps are OK - in principle, but there seems to be little or no chaching, because I see download delays again and again for the same areas.
Funny turn today: I had copied tons of new OAM files from PC to the LG yesterday, plus the new Ele* themes.
This noon I saw that many maps from Europe had not be copied (Finland and Romania amongst them ...). So in fact I ran a combination of new Ele themes and old OAM files from April, which seems to make trouble in high zooms
With the new OAM files and themes all is fine.
LoMaps and their themes are also fine.
Also Online maps are OK - in principle, but there seems to be little or no chaching, because I see download delays again and again for the same areas.
Ah ... ok :).
About caching ... you may check if files in Locus/mapsOnline are creating and increasing it's size when you use certain map. If not, please check if you have enabled settings > maps > online maps > cache online maps
Ah ... ok :).
About caching ... you may check if files in Locus/mapsOnline are creating and increasing it's size when you use certain map. If not, please check if you have enabled settings > maps > online maps > cache online maps
The respective Online-sqliteDB does exist and has 16 MB.
Still, the display of the tiles from this DB shows white spots left or right on the way, while rendering from Vectormaps is faster and hardly shows such white tiles.
And the world map overlays are even faster.
So I am not sure what is going on with the onlien maps. But I hardly work with online maps (only did for the test purpose you asked for), so I personally to not really care.
The respective Online-sqliteDB does exist and has 16 MB.
Still, the display of the tiles from this DB shows white spots left or right on the way, while rendering from Vectormaps is faster and hardly shows such white tiles.
And the world map overlays are even faster.
So I am not sure what is going on with the onlien maps. But I hardly work with online maps (only did for the test purpose you asked for), so I personally to not really care.
My OAM/Ele theory has proven wrong.
This morning the near stand-still at ZL 16+ started again. And a restart of Locus did help. So it is something inside Locus or between Locus and Android 7.
I will try logging when I find some time.
My OAM/Ele theory has proven wrong.
This morning the near stand-still at ZL 16+ started again. And a restart of Locus did help. So it is something inside Locus or between Locus and Android 7.
I will try logging when I find some time.
SD card is fine.
But it is now reproducible:
switching on GPS in Locus creates the effect. Switching off will make
Locus fast after a slow reaction time.
SD card is fine.
But it is now reproducible:
switching on GPS in Locus creates the effect. Switching off will make
Locus fast after a slow reaction time.
Good day Michael,
is this problem still happen to you? I have finally working Android 7 on Samsung Galaxy S7 device and all works without any problems here. I can imagine to create special version that will try to measure what exactly cause these troubles, so let me know...
EDIT: I'm closing this topic. Discussion continue in "duplicate" topic here.
Good day Michael,
is this problem still happen to you? I have finally working Android 7 on Samsung Galaxy S7 device and all works without any problems here. I can imagine to create special version that will try to measure what exactly cause these troubles, so let me know...
EDIT: I'm closing this topic. Discussion continue in "duplicate" topic here.
Replies have been locked on this page!