Messages

Not here. But the more I do such things, the more likely it is that it does not render v4 maps at all... then I have do delete cache and restart.

The Mate 20 X is awesome. Great performance and a battery with its 5000 mAh beast. Did not test longer periods of track recording, but I'm convinced it will work. Have added Locus to the power management exceptions etc... And track recording seems to be more precise than my Sony Z1 because it uses more satellite systems. Yesterday it say about 40 satellites at the same time...

Hey Menion, in my recording panel there's room for 18 items, can you allow for more than 14 items?

On my phone there is plenty of room for Locus left menu. There could be another row of commands, i. e. 8 instead of 6. Menion pls :-)

[@tapio]

@tapiomap does not render?? We are talking again about OAM maps right? Oki, as I wrote to Viajero, I'll start to use them to see if there is something to improve, thanks.

Yes, happened, but rarely. I think it happens especially after manually switching between OAM maps, going to map center.Zooming out, going somewhere else, zooming back in...I don't know.
Well now I am on the migration from a Sony Z1 to a Huawei Mate 20 X, will see how things go.
Now all formerly big smartphones are tiny for me.

It is not able to use the notch area, right? An my phone it is pretty small, just the camera. EDIT: Android has an option to enforce use of notch area per-app.

Good first impression as for performance. But sporadically, tends to happen when I'm out in the wilds :-D, map does not render. Or I am too impatient, waiting a minute. I see grey and a grid. Workaround is to delete cache, restart Locus, wait like 2 minutes because it does some initializing, especially on the big world map.
Used map is an oam v4, size 500 Mb, ie not a huge one.

Thanks, so Mate 20 Pro seems to be no more problem, I hope same applies for Mate 20 X, which I'll probably buy. https://dontkillmyapp.com/ is funny :-) So Huawei leading the list :-)
Well, listing Sony Stamina mode is stupid because that mode clearly is a "You cannot use any app, but save all energy for phone/sms" mode.

Hi guys,

I am aware there were massive power management problems of Huawei smartphones with Locus Map. To my knowledge aggressive power management on Huawei side turned off GPS, or suspended Locus...
I am now seriously considering buying a Mate 20 Pro or Mate 20 X (monster phone, but huge battery!)

I think, the least I have to do is to put Locus to some power management exceptions on Android side, IDK. What I definitely do not want to have is endless debugging of problems...

Are such problems solved? Maybe Mate 20 Pro or X users here?

Thx

I think the trigger for this series of issues is a choice BRouter DEV made: it enforces a new selection of storage path for the BRouter storage. I saw 3 or 4 options when upgrading to 1.5.x
You make the wrong choce, you are doomed - and to manually repair.

Before, I had configured Brouter BRF files to be in [ext]\Brouter\BRF\ (I think) - a choice which the dialog did not give me. At this point I was already thinking "OK, I will have to spend much time here now". I chose the [ext]\Android\Data\ path which is always a good idea, but the result was: I had to copy the brf files manully there. And I had to copy the routing files to a brouter-path on the internal SD, for Locus to find them. I was thinking: 1 of 100 people are able to solve that on their own

Does it have performance issues? I have never seen that behaviour before in Locus:
I have no POI loaded and no tracks; Locus works fine.
Now I load all tracks from a folder (39) - and Locus is unusable. Moving the map takes long, double tap for showing/hiding the toolbars is unresponsive and very laggy. Feels like 100% CPU consumption.
My device is a Sony Z1, ie. not a new one, but I have never experienced Locus to be this way. Have also restarted device, no change.

Probably, thx. Then I have never seen it I guess.

"Active items" - how can I make that item appear again? I turned it on in the options, loaded my tracks, points and Lomaps POI. Blue tab bottom left does not appear.

That store refresh thing is what I also noticed in current Google Play version.

Great news about POI.

Wasn't aware of brouter new versions. Just did play store updates.

Perhaps the app is not looking for "the same filename but ext", but for hard coded lower case variant.

No. Only Menion can know. E.g.: Netherlands.osm.map+Netherlands.osm.db works.
I keep in mind: "full lowercase is better"