Messages

Just tried ...12 on G5 and M5. What worked before now crahses at start. Sometimes after a long wait and the initial messages, sometimes right away.

No start issue on my LG G5 and Note 3 and M5 tablet. Will try newest version later today again.
World map fix confirmed.
Overlay zooms still in disarray - need more data points, Menion, beyond my mail ?

I tracked 1000s of miles when at window seats, using Locus.
Some observations, though:
- GPS sensitivity differs heavily between different models (Samsungs quite OK, Moto G3 great, LG G5 a mess)
- the App GPS locker requests GPS from Android independently/ in parallel to Locus - will help to understand where the bottleneck lies.
Good luck & cheers
Michael

100000+ Downloads seit 2010 oder so ?
Jetzt 6 Leute am Arbeiten ...
Reichtum sieht anders aus.

PS: the new version will be a beta through Google Play?

Thank you Menion, I understand the mechanics now, with the second picture.
Most prob. I will put a 0.5 into the mbtiles as a default.
I understand very well you want to preserve the new feature of dpi sensitivity as a general feature.
Will test myself  V. 10 ASAP.

[@michaelbechtold]

@michaelbechtold
"I prefer that every user has his/her own say adn choice" > you already made a choice when you created these maps. There also was no setting in Locus Map to rescale map labels and you decided to create them a lot bigger than are in almost all other online maps!

So what I offer, is to create a new map with the included parameter, that will say to Locus Map "scale this map only to 50% compare to other online maps".

I made a choice in the past indeed, and it more or less worked for all Apps and all devices. With the new Locus approach there is a FACTOR of 4 that breaks everything, and it triggered a more fundamanetal rethinking :-) Anyway, I do not want to fight philosophy battles.
And your proposal should do the job, although I do not exactly understand the mechanics (will 50% be hardcoded in Locus ? Will it be a parameter for the world maps ?).

TXs and cheers
Michael

Yes, Menion, in the initial versions of the world maps, I set the label sizes for Maperitive so that in Locus (old version) as well as some other Apps, the labels were readable easily.
With Locus (new) there exists no label size that would fit Locus as well as other Apps.
Your suggestion to add a scale parameter into the map DB itself I can handle easily. Yet, this would imply that I have to make a choice for all users. I'm not known to be shy, but nevertheless I prefer that every user has his/her own say adn choice, hence a parameter inside Locus would be better. Not everybody dares to patch sqlitedbs, aklthough it is pretty easy with SqliteBrowser.

When recording a track, always a FC happens with 3.37.2.9
Report by system sent.

Hi Menion, you know my "addiction" to Lucus since years, but we have to admit there are other people who use other apps in addition or instead.
When testing ANY raster map with Locus and with Orux you notice factors between the scales. For the same map you need a 4x magnifying glass in Orux. And I do not propose a discussion who is right or wrong here.
Alos, for raster maps, the battery argument does not hold, I suppose. Displaying images is highly optimized by Smartphone architecture, more or less tiles do not really matter, hence the scaling below 100% does not hurt. Yet, rendering vector maps is the real battery power burden.
So, to make all ends meet, I propose you give the overview map its own scaling factor, hence vector processing in higher ZLs will not be affected by a scale down.

Well, my understanding was that you personally would not employ <100% scale. Which does not imply you deny that to everybody else ...
The map is the W1-10MBT from OAM, used as world map.
I also got the PlayeStore update on my LG G5.
Here I can manually reach 70%, but a "+" jumps to 100% rather than 70% with the next ZL.
In any case, a scale definition for the world maps would help.

Hi Menion, just installed the latest alpha on a M5 tablet.
Scaling below 100% is not there. At the same time - other than before - a manual adjustment is now only possible down to 80%, then it jumps to lower ZL and crazy % >100%. But then, when I tap "+", it jumps to 133%, regardless of the scale I adjusted manually. I.e. User has lost control.

[@michaelbechtold]

@michaelbechtold
hmm so your request: allow "Maps > Advanced features > Increase map resolution" select values below 100% right? I've just tested it and it seems to work. Anyway, I'm personally not a big fan of this. 50% scale means 4x more map tiles = slower map, slower app, lower battery. Is there any particular map that needs some special scaling? Every online map has own scale factor, so it is possible to rescale a single online map individually to be "same" as other maps.

Thank you Menion. Currently I am manually working with 70%, which is only a factor of 2. Driver for this is a proper balance between World Map and Vector Maps.
If there would be an "own scale factor" for world map, like for the online maps, that would do as well.

TXs Menion.
I understand zoom lock. But to get to the 70% in the first place, fiddling with this jumping threshold is annoying.
Why not allow a general scale factor below 100% - all needs met. Usage up to the taste of the user.

Hi Menion,
the meaning of "incorrect" is defined by the PURPOSE of the search.
A pretty usual scenario I am used to is:
1) you are on the ride, have a quick break
2) you plan to be in a place 30km away as next target
3) at the break (#1) you think about what to do after the next target
Currently you have to live with irrelevant data, based on your GPS position - OR have to switch off GPS, etc., etc..
4) and finally you forget to switch it on again :-((
What about a radio switch "from: GPS / Map Center" ?
All users happy for any scenario :-))
Cheers
Michael

PS: heading to Karlovy Vary in an hour from now - any hints for this region ?