Important links
- list of news (https://help.locusmap.eu/announcement/version-3-46-26-05-2020) of public versions
Versions
26. 5. 2020 - Locus 3.46.0
The first initial publish is mainly for my personal confirmation, that there is no serious issue in underground changes. So it's published "only" to 25% of Locus Map Free. The full rollout will be in Thursday in case of no serious problems.
Longer battery life on track recording; what did you change?
Map legend. OMG. Needed so much, wasn't aware it has been discussed. Where can I find it in the App?
Hm, the 3.46 LM Pro update has not come to me from Google Play yet, even if full deployment were planned on Thursday.
Google probably involves progressive update deployment as well, perhaps for bandwidth leveling reasons
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
@tapio
Optimization during track recording: quite a long discussion on help desk, but check mainly my last post here (https://help.locusmap.eu/topic/cpu-time-increase-after-long-runtime#comment-83649).
Legend .. this is another story :). You will over time notice small badge in list of map themes. Long-click on such themes to get to it's legend.
@poutnikl
For almost two days, I see LM Pro on Google Play as published, but it's still not ready for download ...
At the top of Google Play console is only bigger information
"Due to adjusted work schedules at this time, we are currently experiencing longer than usual review times. Please expect review times of 7 days or longer."
So ... let's wait :)
- Falcos Tasker plugin is gone, I need to check that. I had a button in the toolbar.
- Now I need to confirm on exit, didn't have to before.
- Something changed in fullscreen mode. I once reported about nervous/vibrating windows - for the first time, the effect is gone it seems.
Quote from: menion on May 30, 2020, 18:34:09
@poutnikl
For almost two days, I see LM Pro on Google Play as published, but it's still not ready for download ...
with me: once an update is released I often do not get it offered as 'update available' the first days but if I go to 'Google Play>My apps & games>Installed>Locus Map Pro' I might get an Update-button (instead of the Open-button) if I switch back and forth several times - so you might get a chance if you try to 'provoke' it > if you know, just try and try, it
might work
Quote from: tapio on May 31, 2020, 07:35:32
- Now I need to confirm on exit, didn't have to before.
Settings/Expert settings/confirm on exit > switched of???
Just got it. Gone test on tuesday.
Quote from: balloni55 on May 31, 2020, 11:42:32
Quote from: tapio on May 31, 2020, 07:35:32
- Now I need to confirm on exit, didn't have to before.
Settings/Expert settings/confirm on exit > switched of???
No - update must have toggled it.
Topic from last version thread:
Quote from: menion on May 25, 2020, 06:53:51
@slarti76
Incorrect time in the "Trip time" screen happens also with the latest beta? Because I made some changes there.
Anyway same for @poutnikl : in case of weird values, please share a GPX with me so I may simulate it. Or if anyone interested, I may gladly publish the source code of this pretty simple algorithm. Maybe someone will be a better idea of how to do it.
I wanted to send the track, but in 3.46.1 trip times for this track look reasonable. Whatever you did, it worked :) Thx!
And about those toasts:I understand if you don't want to put work into that. It's not a major annoyance. I still think, whenever possible, a toast "Process successful" should be extended with some more information about what happened. Then it also becomes an option to look into a certain toast if it happens too often.
Quote from: slarti76 on June 01, 2020, 09:52:03
Quote from: menion on May 25, 2020, 06:53:51
@slarti76
Incorrect time in the "Trip time" screen happens also with the latest beta? Because I made some changes there.
I wanted to send the track, but in 3.46.1 trip times for this track look reasonable. Whatever you did, it worked :) Thx!
Can confirm problems with
travel time seem to be gone with new version.
Problem still remains:
Route planner seems to have problems to calculate correct time when adding shaping points - Same routes will have much different times in
bottom panel when adding points.
Also toogling
Include navigation hints on and off seems to change the time too.
Quick bookmark for Whatsapp with OSM link works great, thank you.
@tapio
it rarely happens that any settings change by itself. App struggle with this problem for some time and I've also some time ago discovered the possible cause. It's because of the huge amount of settings Locus Map has an Android system that was not created for such amount. So ... another task on long evenings ...
@slarti76
I'll try to improve "toasts" next time, I'll add some new. At least some small "code" at the bottom that may help to identify from where comes, should be useful, agree.
@neatwheat
the difference in times is currently most probably caused by the difference of track segment: in case, the segment is computed by the router, the time comes from this router, otherwise, time is estimated by the app based on few internal variables. I can't improve this now, but it is definitely something that needs to be "fixed" as soon as possible.
---
And new Beta version 3.46.1.1 on Google Play for weekend testing.
I tested the dark mode and found following problem.
At the diagram of the track recording the text style has to be changed. (https://uploads.tapatalk-cdn.com/20200607/7ac16a4b77b80a659af978473b46ec2a.jpg)
Gesendet von meinem XZ2C mit Tapatalk
As I know, public Locus Map Free/Pro does not have any dark mode.
Sorry, it was in the LM4.
Gesendet von meinem XZ2C mit Tapatalk
I know this is a very exotic problem, but I just got a new Samsung tablet which supports Samsung's "PC-like" mode DeX. I tried it out, but for some reason, Locus can't go to Fullscreen there. Most other apps can.
Are you aware of any explicit problem or reason for disallowing this?
If not, nevermind, it's really not a biggie. Just found it curious why Locus is different...
3,46.2 is awesome but, as with 3.46.1 it does not shut off over the back button (with confirm). Even GPS stays now active. And guiding on a track stays active. Upon restarting from the screen it says about 1 second "initialising" and it is all back with the last guiding in view.All on my Android 7.
And the same as was already with 3.45 for my wife's Android 10 phone.
So we swipe it out of the screen with last used apps and then it stops.
Hi Menion!
Thanks for your work concerning version 3.46.2 - but I am really very disapointed concerning one modified feature:
" improved visible track part on dashboard chart during navigation"
It is really bad now, that the location point in the height diagram is now not just a bit more to the left, but now this point is very, very far on the left hand side!
Up to this change it was very helpful on longer tours to see aswell some of the altitude profile, which you have already done. Now you can see just the part of the forward track.
This point has been moved now realy a bit too far to the left hand side - we want to see aswellsome of the height profile already done.
Maybe you can change this or offer a option for that in the settings.
Thank you very much, I am really concerned about this feature which was so well realised in the past...
Best wishes!
I also have the impression that Locus 3.46.2 doesn't shut off anymore. I don't see the loading screen anymore and the map screen is drawn almost instantaneously. Only after deleting temporary files, which enforces a restart, the loading screen is present.
I noticed a severe bug with the route planner:
- Take a recorded track. I had a track that was missing the first few minutes, which were on the road, so to export a nicer map, I wanted to add the start by automatic calculation with the route planner.
- So I chose my starting point on the map and selected it as "starting point", which made Locus (or rather BRouter) calculate and add the missing part.
- Everything looked fine, the rest of the track was unchanged. Note that the rest consisted now of points 2 and 3 (triangles) with the "draw manually" icon in between - but the track was unchanged.
- Now I saved - and boom! Only a straight line between points 2 and 3 was left! All actual recorded track was gone.
Now this kinda makes sense, because "draw manually" between two points means, essentially, a straight line. But it shouldn't change an existing track, and
especially shouldn't do this only after saving, keeping the user in false security about the shape of the track.
And a question/request:
I like the "Share as screenshot" function - great for creating overviews of several tracks at once. However, it always exports as JPG, and not in great quality. The track lines and icons are smudged compared with a "real" (system) screenshot which is saved as PNG. But the latter of course includes all the user interface stuff that the Locus internal function gets rid off.
So is there a way (config file setting perhaps) to make Locus save that as PNG? Or could that be added?
Quote from: menion on June 05, 2020, 17:49:22
@neatwheat
the difference in times is currently most probably caused by the difference of track segment: in case, the segment is computed by the router, the time comes from this router, otherwise, time is estimated by the app based on few internal variables. I can't improve this now, but it is definitely something that needs to be "fixed" as soon as possible.
Thanks for the info. If I may push an additional idea for that topic:
an option to have the route's
travel time (movement) be shown in
bottom panel, regardless of which routing service is chosen would be awesome (and could maybe even serve as a workaround for the shaping point problem)
Hi guys, thanks for the feedback. Sorry for a little bigger delays in my answers this week and most probably next as well .. I have a limited working time these days.
Back to work ...
@slarti76
- I do not own a new Samsung device, but as I know, the app has some problems with full-screen on modern devices, so it is possible. I have to invest more time into this later ...
- problem with editing of the track ...nice idea btw! (just be aware that app does not generaty any usable times for this new segment). I've registered this to my todo list, will check it later.
- share screenshot ... based on some testing with joeloc a longer time ago, this function saves image in JPG/80% . main reason for us was ratio of size vsquality. In this case, quality should be prefered over size, so agree.PNG should be better. If no one has any problem with it, I'll change it.
@Henk van der Spek , @Mapper
sorry, I still did not notice any similar problem, so it is currently harder to solve. If it cause any issues to you, or any battery drain, I may create a special version that will print us more into logs. I will probably needs more than one version to find out anything, but if you want to invest some time, it is probably doable ...
Let's wait for more "victims". We avoid battery drain (also due to gps staying active) by swiping Locus out of the "last used apps drawer". Even without the back button that stops Locus perfectly.
It is on two different phones anyway: a Motorola One with Android 10 (one) and my Android 7 China phone.
No worries, happy hiking.
Thx for positive replies :)
Quote from: menion on June 17, 2020, 19:15:14
@slarti76
- I do not own a new Samsung device, but as I know, the app has some problems with full-screen on modern devices, so it is possible. I have to invest more time into this later ...
Don't sweat it, it was merely an observation.
Quote
- problem with editing of the track ...nice idea btw! (just be aware that app does not generaty any usable times for this new segment). I've registered this to my todo list, will check it later.
Great! I'm aware that this is only usable for "looking at the track", not for statistics. But it's often a shame when you doing several days of trips and one day you forget to start recording in the morning. At the end you wanna print out a map with your complete tour and there's this nasty hole ;) Well, you got the idea, so thx for looking at it!
Quote- share screenshot ... based on some testing with joeloc a longer time ago, this function saves image in JPG/80% . main reason for us was ratio of size vsquality. In this case, quality should be prefered over size, so agree.PNG should be better. If no one has any problem with it, I'll change it.
Also great, thx! It would also be consistent with the word "screenshot" as Android uses it - which also writes a PNG.EDIT: Gotta correct myself, this seems to be dependent on the vendor. Samsung writes JPG, but my LineageOS devices write PNG. Still, we seem to agree that PNG makes much more sense for screenshots...
My assumption that Locus 3.46.2 doesn't shut off anymore was incorrect.
It does shut off correctly but the initializing screen is not shown anymore if I disable all my gpx tracks to be drawn on the map screen. Until this version I always saw the initializing screen, regardless if there are any tracks or POI to be loaded and drawn on the screen, this has changed now.
Since the initializing screen tells me it loads a lot of different items I thought it sould always be there but it isn't anymore.
@menion: did you change something regarding this initializing screen?
@slarti76
- Route planner problem should be fixed in the next version
- PNG - quite interesting that Samsung uses JPG.
@Mapper
no change in the recent version, but some versions ago yes. App firstly test if loading dialog is really needed and if only a few points/tracks should be loaded, no changes in maps, etc. then loading dialog is skipped and all is done silently on the background.
Hi Menion!
Are there any changes again, concerning the problem with 'height profile and location point'?
See discussion here:
https://help.locusmap.eu/topic/elevation-profile-and-navigation-cursor (https://help.locusmap.eu/topic/elevation-profile-and-navigation-cursor)
Because the feature with the height profile is (was...) so good and is very helpful on tour it would be very helpful if the height location point could be located again more in the middle (or offering some setting options).
Thanks a lot for your support and help!
Concerning the problem with this location point on the height profil:
you also need the part of the track that's behind you!
So please change again to the old version. Over the last years we had absolutely no problems with that!
Would be a great help if you change that again to the 'old' version!
Thank you very much!
The new Beta displays a banner ad
Today (again) being on a round track I lost my active guiding. It has happened to both of us on two different phones before. Both on 3.46.2 I cannot simulate it, happens seldom.
But: Restarting the guiding (along a track) it would not do that properly, see screenshot.
I was less then one-third from the finish and Locus went to the nearest point on a new lap.
Hitting nearest poimt or closest point did not help.
Starting guiding from the track list did not help.
Starting navigation with the proper profile did work (but I prefer guiding).
@Žajdlík Josef
ah, weird that it is already visible today ... you have correctly set 30. June? It should be same issue as here https://forum.locusmap.eu/index.php?topic=6817.msg60394#msg60394 , sorry.
@Henk van der Spek
should it be possible to simulate the issue on your rounded track manually? I really need to have some steps here to fix it properly :-\
The installation took place yesterday and is valid until tomorrow. Version 3.46.2.3.
Quote from: menion on June 17, 2020, 19:15:14
@slarti76
- share screenshot ... based on some testing with joeloc a longer time ago, this function saves image in JPG/80% . main reason for us was ratio of size vsquality. In this case, quality should be prefered over size, so agree.PNG should be better. If no one has any problem with it, I'll change it.
Latest beta still writes JPG. Did you forget about it or some other reason?
@Žajdlík Josef
hmm, let's hope, next version will be correctly extended :).
@slarti76
ah, I'm stupid. Image is correctly PNG, but has still ending ".jpg", thanks!
@Menion,
In latest beta I cannot select time/date for the next backup.
Sure, it was removed because it never worked correctly. App automatically wait for time, device is not actively used.
Sent from my Pixel 2 using Tapatalk
Quote from: menion on June 30, 2020, 15:03:55
Sure, it was removed because it never worked correctly.
Since long time this worked on my smartphones almost perfectly every day.
I am disappointed :-(
Perhaps a little checkbox automatic <-> timer driven?
Thank you.
Sorry, no.
Why time is important for you? The new method I use should try to find a moment when the device is not used, which should cover needs for some specific (night) time.
Quote from: menion on July 01, 2020, 08:18:33
Sorry, no.
Why time is important for you? The new method I use should try to find a moment when the device is not used, which should cover needs for some specific (night) time.
I can confirm Menion, never worked for me at all on at least 5 different phones over time.
I hope disabling it now works - I usually have it enabled only on Pro, but still get backups from Free when both are installed...
Quote from: menion on June 30, 2020, 13:56:32
@slarti76
ah, I'm stupid. Image is correctly PNG, but has still ending ".jpg", thanks!
Yeah, you're right, JPG ending, but it was atcually a PNG...
Quote from: menion on June 19, 2020, 11:24:10
@slarti76
- Route planner problem should be fixed in the next version
Quick test in 3.46.2.3, looks ok.
And a fun fact about the "Beta-testing" Quick Action Menu:
You can choose "Quick Action Menu" as function button in the QAM. Down the rabbit-hole... ;)
One more thing about the Backup:
I still think that "Back up settings only" should backup data\dashboard and data\presets directories, too. To me, they're integral settings. Right now, when I do manual backups, I always do the full backup and then delete the data\database folder from the ZIP to save space.
In Beta 3.46.2.4. I can't restore settings from a backup created in the PRO version.
Quote from: Žajdlík Josef on July 02, 2020, 14:05:59
In Beta 3.46.2.4. I can't restore settings from a backup created in the PRO version.
Yeah, had that problem, too, but wasn't sure if that's supposed to work...
The issue in backup restore found, thanks!
About content of settings-only backup: I'll think about it. Presets: right, they are some kind of settings. Dashboard are more a "content" than a setting...
Quote from: menion on July 06, 2020, 11:48:06About content of settings-only backup: I'll think about it. Presets: right, they are some kind of settings. Dashboard are more a "content" than a setting...
I disagree, but also think that it's most important to include presets, especially as I (and most others, I presume) tinker with these regularly. Can live without including dashboards...
Quote from: slarti76 on July 01, 2020, 09:55:12
One more thing about the Backup:
I still think that "Back up settings only" should backup data\dashboard
@slarti76 - I agree.
Question:
At OpenAndroMaps (https://www.openandromaps.org/) they're talking about more and more HighRes SRTM data being used (to allow altitude lines with 10m resolution).
As far as I can see, Locus still downloads the same HGT files as it did years ago, at least the size hasn't changed which strongly implies the resolution didn't improve.
Is there any chance that Locus downloads higher res data, too - where available? Or is there a source for HGT files to download and manually copy into the data/srtm directory? If Locus can use that at all?!
Hi slarti76,
you can find the LIDAR based DTMs at http://data.opendataportal.at/dataset/dtm-austria
I doubt Asamm would volunteer to host the 25MB/piece data ...
Cheers
Michael
Quote from: michaelbechtold on July 08, 2020, 10:22:59
Hi slarti76,
you can find the LIDAR based DTMs at http://data.opendataportal.at/dataset/dtm-austria
Thx! I manually tried the Swiss ones.
Good thing is, it works flawlessly with Locus. You can see the resolution is better, especially if you turn on Slope Shading, which shows more details. Simple Map Shading is also a little more detailed, but not enough to justify 10x the size.
Mountain peaks are also still not very exact, I spot-checked some and usually saw 5-15m less than the official SwissTopo says.
So, I have to admit that it's probably not worth the hugely increased space requirement.
In the end, the better data is best used in OAM, where they now have 10m contour lines instead of 20m, which definitely improves the usefullness in the mountains and moves them closer to official maps.
Fully agree.
Stable branch, there is still the issue we discussed earlier, save a track from route planner, enter route planner from this track again: it only remembers start and endpoint 😕
Still don't know why it happens sometimes, sometimes not.
Question about this changelog entry about "GPS only when app in foreground (Android 11"):
Doesn't that kinda kill all recording ability - for Locus and all GPS apps? That sounds like the end for all GPS recording apps, if I have to keep the phone on and the app open for it to record. Or do I miss something?
Sorry if that has been discussed before, but the search is not usable for searches like "Android 11"...
@slarti76
Petr periodically updates available HGT files, so they are not exactly the same. But resolution remains the same. We still do not have a mechanism for updating of these files on devices and also do not have a system to offer download more detailed elevation files. Because they are a lot bigger, it may need some "chooser" in the app UI.
Regards quality ... I think it worth it's 25MB. You may compare results on "fill elevation" over some route in mountains. The difference may be huge. And 5-15m difference on the peak? It's better than I should expect :).
And GPS stuff ... sure, it break recording, navigation atc. when the screen is turned off or the app is minimized. Unfortunately Android 10 and mainly new Android 11 hide option to use GPS always a little more, so I was forced to request "Use only when visible" at the start and "Use always" a later when any feature really needs it (like track recording).
@tapio
well, I wasn't able to simulate this problem yet ...
Quote from: menion on July 11, 2020, 12:04:32
@slarti76
Regards quality ... I think it worth it's 25MB. You may compare results on "fill elevation" over some route in mountains. The difference may be huge. And 5-15m difference on the peak? It's better than I should expect :).
What about if ZIP of HGT was supported? Then for example 25MB N49E015.hgt (Italy/ Austria) is reduced to 7MB file. Low res N49E015.hgt is 3MB, so just over double size. Or all HGTs can go into a single ZIP - maybe performance issues I guess.
ZIP is used for the transfer, but definitely not usable for real-time usage.
Quote from: menion on July 11, 2020, 12:04:32
@slarti76And GPS stuff ... sure, it break recording, navigation atc. when the screen is turned off or the app is minimized. Unfortunately Android 10 and mainly new Android 11 hide option to use GPS always a little more, so I was forced to request "Use only when visible" at the start and "Use always" a later when any feature really needs it (like track recording).
So do I understand correctly that recording in background is still possible, the user just has to once more "accept" the rights for that? Actually, I googled a little and that's what I gathered from what I found. If so, perhaps you should rephrase the Changelog entry, because that really at first makes one think that bg recording is not possible at all anymore...
What's up with version 3.47?
The Free was updated 3 days ago, but Pro is still not available. That doesn't look like some of the usual Google Play delay...
You also didn't start a new 3.47 thread...
Or does the Free Beta claim to be 3.47 (without beta) by mistake?
@slarti76
sure, the functionality itself does not change, no worry. Without recording/navigation in the background, Locus will be quite useless :).
Free version: I did this a few times before. The free version was published on Thursday only as a Free version for 25% of users. Today I'll check automatically reported problems and I'll probably tomorrow publish a version for all users, also Pro version. There were again quite a big changes in the background, so with this, I verify that there are no serious crashes I missed.