Locus Map - forum

Development => Android versions => Locus Map => Topic started by: Menion on March 30, 2022, 15:24:43

Title: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on March 30, 2022, 15:24:43
New Locus Map (4) version

Important links
- list of news (https://help.locusmap.eu/announcement/locus-map-version-4-8-30-3-2022) of public versions
- Blog post (in preparation...)
- Public versions (http://bit.ly/lmVersions)
- Beta versions (http://bit.ly/lmVersionsTest)

Versions
30. 3. 2022 - Locus 4.8.0
31. 3. 2022 - Locus 4.8.1
4. 4. 2022 - Locus 4.8.2
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on March 30, 2022, 15:27:39
I'm a little bit in hurry releasing a new version with a bunch of interesting changes. I believe all will work as expected. This version comes with a new system for purchases we were working on for a long time. And hopefully, I'll have more time for interesting features ... finally  :).

Locus Map Classic will be published within the next days...
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on March 30, 2022, 15:59:01
Hello menion
thanks for new version :)
i have tried to start a 14 day trial version
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on March 30, 2022, 16:45:25
Damn what is it? I'll have to wait for Petr and we will check it immediately, thanks.

Sent from my Pixel 5 using Tapatalk

Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: voldapet on March 30, 2022, 17:12:08
@balloni55 - would you please try it again? :)

EDIT: please send me also PM with your current account (email address) in the Locus Store and current Google Play account
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on March 30, 2022, 17:25:30
Quote from: voldapet on March 30, 2022, 17:12:08
@balloni55 - would you please try it again? :)

EDIT: please send me also PM with your current account (email address) in the Locus Store and current Google Play account
Hello Petr
done :)

on next try to start a 14 day trial a window open that i should pay 23,99€/J
no option for a free 14 day-test

Wolfgang

Perhaps i am not allowed to test it because I already have had an annual subscription
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Tapio on March 30, 2022, 19:00:52
a) Changelog says it backs up map themes. But looking into it, the change I see is it added router profiles.
OK, I tested... It does not use the currently configured MapsVector/_themes, but the default one on intSD, empty here

b) Terminology. Dashboard screen uses "Themes" as a term.

c) Toggling of 2 maps via longtap: nice
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Žajdlík Josef on March 30, 2022, 20:19:45
After updating to version 4.8.0, the entire menu shifted almost a third of the screen height. Android 8, Samsung A3. The route scheduler is fine, it's just on the main screen with the map. Any idea what about it?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Andrew Heard on March 30, 2022, 23:29:49
@menion I have the same issue as @Žajdlík Josef - see attached

@menion can you clarify 2 items in the release notes:

1) special "Position" parameter for dashboards - I experimented with "whole screen overlay" & other options + "resize by top| bottom panel" but it didn't fix the bottom panel layout bug reported in screen cap.

2) "united dashboard selection & edit" - this has already been discussed in 4.7 beta. It appears the new behavior is: if dashboard is active then single tap to hide, if dashboard is inactive then single tap to display list. So now in order to edit active dashboard, it must 1st be made inactive, then a 2nd tap to display the list, then dot-dot-dot menu to edit. Previously I thought a double tap had some special behavior but I was fooling myself, it is just same as single tap. This is a backward step from having a "Dashboard Editor" button but maybe there is some special trick.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on March 31, 2022, 08:27:04
@tapio
a) ah, custom "mapsVector" directory, thanks, fixed
b) fixed

@Žajdlík Josef
I'm stupid, thanks, will be fixed today

@Andrew Heard
1) right. The issue was caused by the work on the dashboard, but it may be fixed only by the new version.
2) I'm convinced that a single united "Dashboard manager" screen is the ideal solution, but I'm open to improvements of course.

The steps you wrote are correct. Most easy is now a long click on the dashboard button in the panel.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Tapio on March 31, 2022, 12:44:50
Quote from: Menion on March 31, 2022, 08:27:04
"Dashboard manager" screen is the ideal solution, but I'm open to improvements of course.
I start dashboard manager from main menu only. No button in toolbar.

Case1: A dashboard was active. Then this dashboard will just be disabled. Manager does not appear.
Case2: No dashboard was active. Manager appears.

This is unexpected UI behaviour. Not good. Atm the command is 50% a toggle, 50% a call for dashboard manager.

I would prefer, if case1 was extended: disable dashboard and call manager.

Just like the GPS manager/gps on/off, the toggling of dashboard should be behind longtap. That would be consistent ui imo.

You may also make the  dashboard entries toggles (bold text if enabled). With maybe the manager not closing when tapping a dashboard entry.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on March 31, 2022, 13:12:26
Hmm thanks, good point.

And what about an even more simple solution based on what you wrote:

Dashboard icon in functions panel
- simple click > open Dashboard manager
- long click menu > option to hide if visible

Dashboard icon in the main menu or "All function"
- simple click > open Dashboard manager

The dashboard manager will have highlighted the currently active dashboard and the tap on it, hide the dashboard as well. What you and others think? This should make it really clear, but right a little bit slower due to missing "toggle" on click in the function panel. But don't know how others, but I use always presets and if not, then still needs a list of dashboards to pick the correct one.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on March 31, 2022, 15:54:31
start navigation > FC
routing engine doesn´t matter
e.g. from GPS to selected point on map, start navigation locus close immediately
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on March 31, 2022, 15:54:47
Oki, new version 4.8.1 published, so give it a try.

Most of the problems should be fixed I believe.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Tapio on March 31, 2022, 17:38:33
Quote from: Menion on March 31, 2022, 15:54:47
Oki, new version 4.8.1 published, so give it a try.

Most of the problems should be fixed I believe.
Dashboard, perfect behaviour for me. I also turn them on/off via presets and do changes now via the main menu. Very minor thing: if you press that star on top of dashboard manager, it says "install default themes".
Full Backup, themes included, fixed, yes.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Tapio on March 31, 2022, 17:47:08
Something is wrong with the longtap map toggle. I switch between OAM vector map and a downloaded SQL Satmap. It's not fully downloaded, maybe that's a problem?

Eg toggling from the OAM map to the Satmap shows an empty map instead. Map picker says "Adaptive - Base map".

Edit: no. Happens from oam to Asamm online map as well. What I did in between the toggling was refresh the map preview of a track. EDIT2: Yes, this seems to cause the problem.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on March 31, 2022, 17:52:09
Fine, thanks for the push before!

And "Themes" ... well it is because I call internally the whole system as "Dashboard" and every single configured view as "Dashboard theme", so there may be a usage of the word "Theme". I'll unite it, thanks.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on March 31, 2022, 18:56:36
Quotestart navigation > FC
you are quite fast 8)
solved with V 4.8.1
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Andrew Heard on March 31, 2022, 23:46:50
Quote from: tapio on March 31, 2022, 17:47:08
Eg toggling from the OAM map to the Satmap shows an empty map instead. Map picker says "Adaptive - Base map".
I have a similar experience to @tapio. Here's my theory: Locus doesn't remember 2nd last map after app exit, so first long tap toggle displays blank map. It is necessary to manually select a 2nd map, then the long tap toggle will work correctly. So question becomes, should Locus now remember current & previous maps at exit & restore these settings upon execution so that long-tap map switch works across app instances?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: tannenzäpfle on April 01, 2022, 07:15:03
@Andrew
same Problem here but I found a solution, see enclosed screenshot

click on "Für mich freigegeben" (released for me)
On the next screen, you will find  subdirectory "versions" with the 4.8.

Hartmut

Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on April 01, 2022, 07:43:28
QuoteMost easy is now a long click on the dashboard button in the panel.

@menion - a long click on the dashboard button in the main menu just results in Change dialog where I can reassign that button to new function?
confirm
Quoteclick on "Für mich freigegeben" (released for me)
On the next screen, you will find  subdirectory "versions" with the 4.8.
i found V4.8.1 under "final download"
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Andrew Heard on April 01, 2022, 08:18:12
Quote from: Menion on March 31, 2022, 13:12:26
The dashboard manager will have highlighted the currently active dashboard and the tap on it, hide the dashboard as well. What you and others think?
@menion: 4.8.1: It wasn't obvious how to hide the active dashboard until I returned to your post on this subject. Would it be more obvious & consistent to use same user interface/ model as points & tracks, with an eye icon next to each dashboard name? Subtle difference, only one "eye" can be active at a time of course. See mockup...
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Tapio on April 01, 2022, 09:22:36
Maybe because you aren't used to? He uses the bold text system already IIRC in the recording presets and audio trainers. Also systems where there's just one item active.
Hmm but I can see, it's a rather unusual ui. Maybe a "Use" entry in the "..." menu helps so people find something in any case.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 01, 2022, 09:30:24
Quick toggle between maps

Hmm thanks. App registered all selections of maps. I've improved it and it will register only big map screens now.

Release & Beta versions

guys, release, and beta versions have their own directories. Currently, the latest public is a "release" version so the Beta channel contains only an older version.

Dashboard

as @tapio wrote, I really use this system on more places. But agree it is not perfectly clear that tapping on highlighted item disables it. Maybe a simple description "Tap to hide" under the highlighted title should help to make it clear?

Option over "...", right also a solution. Btw. long click on the "Dashboard" in the function panel offer also "hide" option.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on April 01, 2022, 12:44:28
QuoteBtw. long click on the "Dashboard" in the function panel offer also "hide" option.
~ sec 20  ????
https://www.dropbox.com/s/xg2cylzy66q3sy5/Longclick.mp4?dl=0
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Tapio on April 01, 2022, 14:32:22
Quote from: balloni55 on April 01, 2022, 12:44:28
QuoteBtw. long click on the "Dashboard" in the function panel offer also "hide" option.
~ sec 20  ????
https://www.dropbox.com/s/xg2cylzy66q3sy5/Longclick.mp4?dl=0
No, in the side panel.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: CabrioTourer on April 02, 2022, 13:47:22
First a problem mentioned by others, too. Because of Quick map toogle locus should save last two maps across App exit.
Otherwise after App start the feature doesn't work.
That's anoying bec of the old unfound bug track shaping points lost I restart App after every route planner usage. Means I have non working quick map toogle often the day

Second is an old bug. Taping planned track on map has two different kinds of "detail" popup. One with 3dot menu. One without. Otherwise they looks identical for me.

I think the one witout 3dot menu comes in first track selection after App start. On second selection the other with 3dot is used. But I'm not exactly sure. See Screenshots.
I need most of the time the route planner which is inside 3dot menu.

Btw:  quich map toogle is a great feature. I use it often to switch beteen "normal" and Satellit map.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: luce on April 02, 2022, 19:12:56
Hello!
In the actual version 4.8.1., the "alternative version of the turn off method" (https://forum.locusmap.eu/index.php?topic=7632.msg65925#msg65925)
doesn't work any more. I have to put my device password every time after Locus activated the screen.
Any idea what's the reason for this?
Best, Lucas
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: luce on April 02, 2022, 19:26:24
... And another thing... I know I'm not the first one to ask this... What about moving the "hide" button to the bottom bar? There is enough space and hiding a track is one of the most used actions.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: freischneider on April 02, 2022, 21:35:52
Quote from: luce on April 02, 2022, 19:26:24
... And another thing... I know I'm not the first one to ask this... What about moving the "hide" button to the bottom bar? There is enough space and hiding a track is one of the most used actions.
For me, hiding is not the most common function. I use it very rarely. If then mostly in the track manager. 
and I find the bottom bar is already very full. If they work here with touch gloves it needs the distance.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 02, 2022, 21:57:21
@CabrioTourer
I know I know. Andrew already reported this a few days ago here (https://help.locusmap.eu/topic/27716-on-saving-a-recorded-track-one-of-two-panels-are-displayed) and I'm still unable to correctly simulate it. But I'll look at it more precisely at Monday, promise  :)

@luce
Alternative turn-off method > hmm I did no changes here. Interesting ...

"Hide" button. Agree with @freischneider, there is no space for another button. Anyway to explain: the app simply creates a list of buttons that should be placed at the bottom and only a certain number is visible, the rest is in the "three-dot" menu. So I promised a long time ago some kind of customization here > and this is ideal adept > allow to define order of these buttons.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Andrew Heard on April 03, 2022, 06:19:13
Quote from: Menion on April 02, 2022, 21:57:21
...So I promised a long time ago some kind of customization here > and this is ideal adept > allow to define order of these buttons.
nice idea!
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 04, 2022, 19:25:32
*** New version 4.8.2 *** uploaded to Google Play.
(and also finally! renamed Locus Map Classic 3.59.0)

And customizable track screen buttons? Later ;D
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on April 05, 2022, 08:12:53
Hello menion
when do you provide the AFA version (4.8.2 and 3.59.0) for download?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 05, 2022, 09:47:42
Ah damn, I was a little tired in the evening and fully forget about this ...

Sorry, versions uploaded, thanks!
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: joeloc on April 05, 2022, 10:03:13
Long tap on map content to toggle last two maps is nice! A little problem though: I believe when Locus restarts and maybe also when I select a new overlay map, you forget the previously used map and replace it with the overlay map. That doesn't make much sense, I never want the overlay to move into one of the toggle spots.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 05, 2022, 10:50:19
Hmm, a simple function is not so easy :). The app keeps internally the list of last selected maps and does not make difference between base map or overlays. Anyway agree, it makes sense to keep a list only of the base maps. I'll improve it.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: michaelbechtold on April 05, 2022, 22:04:49
Distance MARKER gets into the screenshot now (4.8.2), but the distance VALUE is still missing ...
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 05, 2022, 22:05:57
You have no idea how complicated this task is  8)
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: baegas on April 08, 2022, 03:16:52
Hello Menion,
I recently asked a question about the horizontal accuracy display on an external Bluetooth GPS receiver.
Now, horizontal accuracy is displayed. However, in order to display horizontal accuracy, in the case of U-bolx GNSS module, you need to use the "U-center" setting program to use "GxGST" in the default nmea message setting.
So U-blox module can be configured easily. However, among GNSS modules from other companies, there are cases where the "GxGST" setting cannot be found in the module's setting program.
So I personally think it would be nice to be able to change or use existing settings in expert settings for modules that cannot display "GxGST". Is it possible?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 08, 2022, 13:16:06
Do you want that Locus Map, when connected to any USB GNSS unit, set up this unit to send also GST messages? This is close to impossible as every unit uses its own system how to configure it.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 08, 2022, 16:01:43
New Beta 4.8.2.1 version published (link to download in my signature as usual).

Interesting news
- fixed a lot of problems with WMS maps, so if anyone of you uses them, give it please a try
- small experiment: picture-in-picture support when navigating. To activate it, open the nav menu during navigation and tap "PiP" button in the toolbar

Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: lor74cas on April 08, 2022, 19:27:41
Hello,
I played with wms in the attachments on the left 4.8.2 on the right 4.8.2.1:
with the same configuration I was unable to display the same level on both.
http://serviziogc.regione.fvg.it/geoserver/ows?SERVICE=WMS&
I also think that a filter is needed for the levels in the case of this service they are really many and you have to scroll through the list to find the one you want.

On the page for selecting the wms services already available, a filter based on the current position would be required. Services not available for your area are useless.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Tapio on April 08, 2022, 22:13:08
Re: pip - what is it showing, what would I need?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 08, 2022, 22:54:49
@lor74cas
thanks for testing. Hmm, I'll check it in the next days and let you know ...

@tapio
nice one. Should be better now with re-generated versions.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: joeloc on April 09, 2022, 08:21:02
I can't pinpoint it exactly, but since a couple of weeks I seem to suffer from disappearing points. Sometimes, or more likely quite often, whenever I create a new point (with long tap), the previous point I added simply goes away. The new point is fine, the previous point disappears completely from the database.

Happens quite a lot, but not always apparently. Probably also is related to what I do in-between adding points. No more clues yet, but maybe you can think of something already.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Tapio on April 09, 2022, 10:03:49
Re: PIP
Works now. Bug with increasing its size per tap. Last step makes it fullscreen just for a moment, then window disappears.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: lor74cas on April 09, 2022, 13:48:32
Quote from: tapio on April 09, 2022, 10:03:49
Re: PIP
Works now. Bug with increasing its size per tap. Last step makes it fullscreen just for a moment, then window disappears.
Confirmed now it works. But take a look at the blue bottom banner in the attachment.
P:S:
I'm not the best tester for this type of function, I prefer small devices so I always use full screen.
Locus always on top  8)
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: T-mo on April 09, 2022, 14:46:26
beta 4.8.2.1
pip: wow great, very much appreciated
some notes:
- the double-arrow-button or double-tap brings it to fullscreen,but then immediately puts it in background or whatever..same with close-button
- by design pip seems to run in a separate process, so when using android opened apps, we have to not go back to last locus-process which is pip,but the next one then
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on April 09, 2022, 15:00:40
PIP screencast
https://www.dropbox.com/s/v5itmmuz558frhc/PIP.mp4?dl=0

sec.5 > click edit >LM go to background
sec.31 > swipe down and click to get LM to foreground > PIP is grayed
sec.57 >recal LM with app icon > PIP is blank
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: luce on April 09, 2022, 18:20:00
I can't find this PiP button although I have the most recent app version (4.8.2.1). What am I doing wrong?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: lor74cas on April 09, 2022, 18:29:09
Quote from: luce on April 09, 2022, 18:20:00
I can't find this PiP button although I have the most recent app version (4.8.2.1). What am I doing wrong?
Download it again from testing folder I think there is a new one with the same name


Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: luce on April 09, 2022, 18:36:34
No difference, also with the actual version...
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: lor74cas on April 09, 2022, 18:50:43
https://drive.google.com/file/d/1CZHlk_ykJg14mXmLPMU83rv0YBIb38Hy/view?usp=drivesdk

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: luce on April 09, 2022, 19:15:00
Thanks lor74cas... but still the same... :)
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: luce on April 09, 2022, 19:19:28
Another thing:

The Vienna WMS map is displaying data again  ;D ;D ;D, but...

- The WMS adress that works again now is
https://data.wien.gv.at/daten/wms?service=WMS&request=GetCapabilities&version=1.1.1

- the data is shown but the scaling seems to be wrong. Everything is very small (see the metro lines and stations of Vienna in screenshot 4).

The entry that is currently in the Locus WMS library (see screenshot 3) shows data but much too small, only in light grey and lines are only one px wide) – see screenshots 1 and 2. When I show an "empty" map, I can see the items. As soon as I use a normal map, the items are much too small and too light to recognise. Seems to have something to do with this thing called SLD...

So could you please to change the WMS adress in the Locus WMS library... and is it possible to change the scaling of a WMS map?

Best, Lucas
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: luce on April 09, 2022, 19:33:01
And yes, a search filter for the WMS layers would be great. For Vienna, these are MANY  ;)

https://1drv.ms/v/s!AredTfs4J1f5gt8AYWEtDwuTaU_eAA
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: CabrioTourer on April 10, 2022, 12:15:26
I would like to ask for a change that's not the most important. Anyway. maybe it's easy to fix.

I do route planning in two steps. In first I put shaping points just aproximately. This makes it fast to plan.
In a second step I use itinerary view to move points exactly onto street.

When itinerary view is started screen is splited in two parts. Upper part is the map, showing selected point. Bottom the list of points. Bottom shows just the first 7 points in my case.

There are two problems when selecting point 8 - x.
The scrolling in point list makes the list fullscreen.
Selecting a point shrinks list again to bottom screen and most of the time not showing the selected one.

The result is a constant scrolling down again and again when working on point 8 until end.
I added a video to show it.

Would it be a big change to keep the split screen even while scrolling list of points and keep their position when selecting a point?
Then it will be much easier to go through the list point by point.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: joeloc on April 10, 2022, 20:00:32
When Locus force-quits (unfortunately still happens, I blame Samsung) while I track is being recorded, recording continues after restarting. However, the Icon (green arrow, red button) does not reflect this and keeps showing green instead of red.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: lor74cas on April 11, 2022, 09:49:17
Hello,
yesterday I was able to see how much Locus Map Web has improved, which now also integrates all data such as heart rate, slope, speed, etc.
However, I noticed something strange, the speed shown in the graphs is wrong. The same behavior can also be found in the app.
I noticed the error because while recording the track with locus I also record with a Garmin Forerunner.
At the points where I stopped, Garmin lowers the speed to 0, while Locus shows an almost constant speed even more evident if you stop downhill.
I am aware that locus records the points only on the basis of the filters set in the setup, in my case 25mt of distance, 5seconds of interval and 50mt of precision, but when one is stopped, a speed other than 0 cannot be shown in any case.
I understand that by not recording the points where you remain stationary in place, the speed data is more difficult to determine, but Locus recorded a point 10.75 km and 3 minutes later a second point at 10.77. So in those 3 minutes it will certainly not be able to register a zero speed, but at least close to 0, instead it shows about 13 km / h. It appears that instead of showing the speed determined between the two points being recorded, the instantaneous speed at the point is shown.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: slarti76 on April 11, 2022, 10:37:03
Hi Menion
I know, I've been coming up with this several times before, but I'm trying it again - perhaps now that Locus 4 is running more and more smoothly, you find the time:
It's about the MapShading: I'm still unhappy that the resolution of the shading is artificially lowered between ZL12 and 13. I posted screenshots before, could do it again, but it's easy to see for everyone. The difference is so stark that setting the Magnify Factor to 200% in ZL12 still produces better shading than ZL13.
One might argue that it's partly astethic, but at least for the Slope Shading, it is not: For snow tours in the mountains, the 30° slope level is the most important factor for avalanche risk assessment, and losing obviously possible resolution here is just a shame.
I know, speed can be a problem here, but for most modern phones it isn't, so it's just wrong to force the resolution-decrease for a specific ZL for everyone.
I think it would make a nice "Expert Setting" to be able to increase the ZL or turn this "Optimization" off completely.
What do you (or anyone else) think?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Andrew Heard on April 11, 2022, 13:50:22
I have observed the same incorrect chart data ie. non zero speed in the chart when should be stopped.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 11, 2022, 14:22:04
PiP > thanks all for the feedback. I did a few improvements over the weekend so in the next Beta, it will be a lot better!

@lor74cas
What exactly is the problem with the WMS map in this post (https://forum.locusmap.eu/index.php?topic=7885.msg67464#msg67464)? When I play with it, all seems to work correctly.

Recorded speed > this is an old problem with detection of the "not moving" behavior. You are correct that the app currently simply records a speed value received from the GNSS unit. What should be done is to, based on the device sensors (or by attached speed sensor), register movement and based on this modify speed values. The task to do.

@joeloc
Disappearing points: this sounds like a serious issue. There were no changes in the database system for a very long time. Hmm, sorry, no idea.

Restoring recording after crash: Do you mean the small "rec" button on the left above the menu & map content buttons? Interesting, I'm trying to simulate it and it is always correctly restored to the red button with small green <> white animation in the inner circle.

@luce
PiP is available only since Android 8+, sorry I forget to mention this.

WMS > which layers you have enabled? All I've tried looks ok, thanks.

@CabrioTourer
thanks for the description. You are right, current behavior is really weird. I'll look at it.

@slarti76
I did some benchmarks and spend some time on it.
Result: agree that difference is significant. Even that detailed shading is around 60% slower, I've moved limit from the zoom level 12 to 15! You will see in the next app version.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: lor74cas on April 11, 2022, 15:57:25
Quote from: Menion on April 11, 2022, 14:22:04
@lor74cas
What exactly is the problem with the WMS map in this post (https://forum.locusmap.eu/index.php?topic=7885.msg67464#msg67464)? When I play with it, all seems to work correctly.
on the left is shown, on the right the data is not shown
opacity 100% on on the left, on right nothing
if we have more than one layer wich is the order?
and if we use also sat map as layer?

Quote from: Menion on April 11, 2022, 14:22:04
@lor74cas
Recorded speed > this is an old problem with detection of the "not moving" behavior. You are correct that the app currently simply records a speed value received from the GNSS unit. What should be done is to, based on the device sensors (or by attached speed sensor), register movement and based on this modify speed values. The task to do.
I think the only sensor you can count on is the phone's gps, currently there are points that are not taken into consideration due to the filters so the speed data should be calculated as the distance from the last known point and the current point and the time elapsed between their detection.
Currently I believe point A is detected with a speed of 10Km / h then one stops and so B, C ... F are discarded, then it starts again with G but it is detected when you are already moving again at 10km / h for this reason I think Locus assumes, at the point where one has remained stationary, a speed of 10 km / h.
For me it would be more logical that the speed was determined by the distance and time between A and G as it is an information not altered by the missing points like speed in the point.
It will not reach 0, but it will always be closer to 0 than 10.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Andrew Heard on April 12, 2022, 01:15:13
Quote from: Menion on April 11, 2022, 14:22:04
Recorded speed > this is an old problem with detection of the "not moving" behavior. You are correct that the app currently simply records a speed value received from the GNSS unit. What should be done is to, based on the device sensors (or by attached speed sensor), register movement and based on this modify speed values. The task to do.

Quote from: lor74cas on April 11, 2022, 15:57:25
I think the only sensor you can count on is the phone's gps
@lor74cas I politely disagree - the accelerometer sensor is very sensitive for detecting movement. It is used very effectively for movement activated alarm apps, and Locus compass. Movement detection on a modern Garmin GPS is more responsive & accurate than Locus for this reason. My cycling friends (many) Garmin devices will know within a second when the device is stopped or moving. At present with a stationary device there could be +/-5m noise or more in GPS position, and Locus will therefore assume small continual movement when actually fully stopped. A combination of accelerometer (optional setting) & GPS could potentially eliminate this error.

keen interest from others - see ideas like https://help.locusmap.eu/topic/using-the-gravity-sensor-orientation-sensor-or-accelerometer-to-move-the-map - 32 votes

https://help.locusmap.eu/topic/improving_gps_position_with_gyroscope_and_accelerometer - 19 votes
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 12, 2022, 07:47:45
@lor74cas
have to agree with Andrew. GNSS is definitely not a reliable sensor. Also, because of this, the app suffers by many problems, not just speed but almost all other variables are affected. I computed speed a long time ago just as the difference in distance/difference in time = result was really bad  :). Jump 20m when standing still is not unusual and in 1-second frequency, it creates a really nice chart.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: luce on April 13, 2022, 09:03:43
My activated WMS layers are:

U-Bahn Bestand - Linien - generalisiert
and
U-Bahn Bestand - Haltestellen - generalisiert

The lines and stations look quite thin and small to me – but okay, using the zoom lock and then zooming in works for me :)

Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Andrew Heard on April 13, 2022, 09:45:45
Still the underlying www.useresponse.com help system (which Locus uses as for their help system https://help.locusmap.eu) RSS links are all broken, so I have added an "Idea" into their own help system. Funny (sad?) the only two categories are "Idea" & "Question", no "Problem" category, so it seems they don't expect problems in their own system or service.

https://help.useresponse.com/topic/31432-rss-feed-link-is-broken

It means there is no indication via RSS when someone adds a new help topic ;-(
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Andrew Heard on April 13, 2022, 23:47:48
The 3 RSS links have been fixed. That was quick. Maybe I should have contacted them a long time ago, but @menion isn't that an issue the Locus team would have been keen to get fixed too?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 14, 2022, 13:14:48
*** Beta version 4.8.2.2 published ***
- PiP fine-tuned
- and 11 other changes

@Andrew Heard
They have problems only as tickets > so only a private.

Anyway, thanks you've reported it! We also report issues there, maybe once per month and they usually publish a new version of the help desk system once a month, so I'm sure, it will be fixed with the next update.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Andrew Heard on April 14, 2022, 23:47:03
Quote from: Menion on April 14, 2022, 13:14:48
Anyway, thanks you've reported it! ...it will be fixed with the next update.
@menion - already fixed
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: razvaneduard on April 15, 2022, 14:59:53
Locus Map 4.8.2.2

I tried navigation simulation and there is no voice instructions:
- I planned  a small route, Activity type Car, saved it
- in skyplot screen in top menu I choose simulation > track > and choose the saved track
The movement simulation is working but at turn point no voice instruction.

Is not yet fully implemented?

Thanks
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on April 15, 2022, 19:49:16
Thanks for dashboard toggle button 8)

dashboard and custom screen have identical icons :-[
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Viajero Perdido on April 15, 2022, 20:06:38
I navigated (car mode) to a trailhead, no problems.  Turn-by-turn directions.

Once on that trail, every attempt to navigate to a point farther down the trail (bike or hike mode), resulted in guidance instead ... the style of guidance I never use, with a single square guidance icon in the upper-left.  And just "beep", instead of "after 20 metres..." that I was expecting with "navigation".  The trail is properly tagged in OSM (foot=yes, bicycle=yes) and hasn't changed in years.

I need to investigate this further.  (4.8.2 gold)

EDIT:  The named trail passing through N53 18.852 W112 57.329 in Alberta is interesting.  Those coords are roughly the midpoint of a single way of several kilometers, with appropriate tags for hike routing.  However, within that single way, some attempts at navigation give navigation, some give guidance (eg, from those coords west to the junction).  I can't figure out the logic.  (And should an app ever give you something different than you asked for?)  Same results on two devices.

Thanks in advance.  Not urgent; enjoy the weekend.  :)
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Christian on April 15, 2022, 23:08:16
LM4 latest Version
Statistics called from within Route Planer
little bit of easteregg :(
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: luce on April 17, 2022, 08:07:06
Hm... I'm not sure what I should think about the new hill shading. Although the resolution is obviously better, the map looks a little flat and less three-dimensional to me, and a bit "pixelated", if you know what I mean (see comparison at zoom level 15). Hill shading in LM3 looks smoother somehow...
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: michaelbechtold on April 17, 2022, 08:30:43
smooth == inaccurate
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: CabrioTourer on April 18, 2022, 09:37:51
Small feedback for menion:  Thanks for the improvement of itinerary list in planner. Works perfect.  :)
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 20, 2022, 08:39:18
@razvaneduard
I'm quickly testing it and it seems to work correctly even for planner routes. You may give a try and modify "speed_for_moving_cursor_when_gps_off" parameter in the Locus/config.cfg file to something like "speed_for_moving_cursor_when_gps_off=3.0" if this makes a difference.

@balloni55
identical dashboard & custom screen buttons > ah thanks. I'll have to get rid of this old "Custom screen" system soon  >:(

@Viajero Perdido
I see the problem probably. When you plan a really short route where are none! navigation commands (no instruction to turn) and you have disabled generating of navigation commands by the shape (settings > navigation > advanced > Frequency of commands), app does not recognize route as navigation route so it starts a guidance mode instead. Hmm ...

This looks like quite confusing behavior. I'll change it to the next app version and when you select "navigation", it will always start this mode even without a valid navigation command.

@Christian
I know I know, sorry. It should be already fixed in the latest beta version and the new version is in preparation.

@luce
I agree with michaelbechtold. Maybe not so nice, but definitely a little more detailed. Anyway as you may see on your screenshots, there are some graphical glitches that I was not yet able to solve. Hope that current style is not a problem.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: slarti76 on April 20, 2022, 10:31:03
Quote from: Menion on April 20, 2022, 08:39:18
@luce
I agree with michaelbechtold. Maybe not so nice, but definitely a little more detailed. Anyway as you may see on your screenshots, there are some graphical glitches that I was not yet able to solve. Hope that current style is not a problem.
I also agree that the detail is more important (hey, I was the one asking for it ;) ). But when I compare the screenshots, the new one also looks less saturated. Perhaps a little tweaking of the alpha value for the shading would make the effect more pronounced and thus better looking?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: razvaneduard on April 20, 2022, 11:34:03
Quote from: Menion on April 20, 2022, 08:39:18
@razvaneduard
I'm quickly testing it and it seems to work correctly even for planner routes. You may give a try and modify "speed_for_moving_cursor_when_gps_off" parameter in the Locus/config.cfg file to something like "speed_for_moving_cursor_when_gps_off=3.0" if this makes a difference.

I modified
   Locus/config.cfg : speed_for_moving_cursor_when_gps_off=3.0
but still no voice commands.
With this modification it shows now direction instruction , but only for the first point.
Before this did not appeared.

Here is  screen capture, for a small navigation simulation:
https://drive.google.com/file/d/1zfvG0K0OjeDooy4c1kFJBZSf2rXv3-CF/view?usp=sharing
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: 0709 on April 20, 2022, 12:06:04
@ Menion.
https://forum.locusmap.eu/index.php?topic=7831.msg67007#msg67007
I will report back, so here is the result. 
https:// will be added.  = Confirmed by the RouteYou developper
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Viajero Perdido on April 21, 2022, 02:41:27
Quote from: Menion on April 20, 2022, 08:39:18When you plan a really short route where are none! navigation commands (no instruction to turn) and you have disabled generating of navigation commands by the shape (settings > navigation > advanced > Frequency of commands), app does not recognize route as navigation route so it starts a guidance mode instead.

Thanks for the quick fix; I'll check it out soon.  I did have "maximum deviation from route" = 250m (and navs shorter than that), which might've triggered the problem.  But not in an obvious way.   :)  Cheers.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: joeloc on April 21, 2022, 16:53:32
Since a couple of years now, Locus dies frequently and silently on current Samsung devices. This happens 3 times a day at least for me at the moment (Samsung Galaxy S20FE), mostly while I do other stuff with the phone. For example, when I take a few pictures or videos with the Samsung Camera App, you can almost bet on Locus (and its track recording) either dying or more likely being killed by Samsungs aggressive OS. NONE of the messy Android options on this will help, nor will running Locus as a service change things. Locus simply dies silently and will obviously no longer record any track.

This is a real shame... and it's basically getting worse with every OS update. I run a "watchdog" since a few months that checks for Locus every minute and restarts it when it's gone. That kind of works against losing tracks, but is really an ugly solution.

It happens to me and to a friend as well (Galaxy S20 Ultra), we both have comparatively large databases. Maybe that makes Locus use more memory and Samsung more likely to kill it when running other apps? I have no clue really, and I can't make any suggestions on how to fix this. I just wanted to point out that this long standing problem is far from being solved... and it's a major nuisance if you cannot rely on your track being recorded.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on April 21, 2022, 18:56:11
QuoteI'll have to get rid of this old "Custom screen" system soon
i hope you still remember your promise regarding "rotation" and "sliding compass". ;)
https://forum.locusmap.eu/index.php?topic=4744.msg38694#msg38694
:) :)
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: michaelbechtold on April 21, 2022, 19:10:32
Quote from: joeloc on April 21, 2022, 16:53:32
Since a couple of years now, Locus dies frequently and silently on current Samsung devices. ...

This happened on my Android 12 S10 (2019) last week (on a 350 km ride) and today again (on a 10 km hike).

Runs as a service, too. And my database is also large, exceeds 1 GB.

Here is some mind food for @Menion:
The older log file ended with those messages:
10:52:43.336   D   zzbcz   checkDayNightState()
10:57:43.327   D   zzbcz   checkDayNightState()
Then a new log file started at 11:02, and this is also the time of the last track point for more than an hour.
At 13.27 the tracking resumed, in the background it seems. Because - very weird - I only noticed that Locus (4.8.2.2 beta) UI was not running some minutes later. I restarted and Locus complained about OS optimization killing it).
Good luck ...!
TXs and cheers
Michael

11:02:42.873   D   getInt   register(android.net.conn.CONNECTIVITY_CHANGE)
11:02:42.881   D   AppLifeManager   refreshPeriodicSetup(), adding refresher for o.zzbcz@aa9b237
11:02:42.885   D   AppLifeManager   refreshPeriodicSetup(), adding refresher for o.zzayk@c17d3a4
11:02:42.900   D   getInstallBeginTimestampSeconds   initialize(o.getContext$read@a079422)
11:02:42.906   D   UpdateSegmentsWorker$write   setupWorker(KEEP)
11:02:42.979   W   isGooglePlayServicesAvailable   onCreate(), id: 20357260, serviceId: 101
11:02:42.981   W   isGooglePlayServicesAvailable   initialize(), id: 20357260, serviceId: 101
11:02:43.032   D   getContainerId   customOnCreate()
11:02:43.072   D   setDisableAdvertisingIdentifiers   validateDbItems(SQLiteDatabase: /sdcard/Locus/data/database/waypoints.db, groups, _id, uuid, time_created, time_updated)
11:02:43.075   D   setDisableAdvertisingIdentifiers   validateDbItems(), invalid: 0
11:02:43.078   D   setDisableAdvertisingIdentifiers   validateDbItems(SQLiteDatabase: /sdcard/Locus/data/database/waypoints.db, waypoints, _id, uuid, time_created, time)
11:02:43.111   D   setDisableAdvertisingIdentifiers   validateDbItems(), invalid: 0
11:02:43.154   D   setDisableAdvertisingIdentifiers   validateDbItems(SQLiteDatabase: /sdcard/Locus/data/database/tracks.db, groups, _id, uuid, time_created, time_updated)
11:02:43.161   D   setDisableAdvertisingIdentifiers   validateDbItems(), invalid: 0
11:02:43.163   D   setDisableAdvertisingIdentifiers   validateDbItems(SQLiteDatabase: /sdcard/Locus/data/database/tracks.db, tracks, _id, uuid, time_created, time_updated)
11:02:47.617   D   setDisableAdvertisingIdentifiers   validateDbItems(), invalid: 0
11:02:47.730   E   stopSelfResult   initialize()
java.lang.NullPointerException: mapContent must not be null
   at o.JobInfo.v_(:395)
   at o.stopSelfResult.initViewTreeOwners(:692)
   at o.JobInfo.<init>(:220)
   at o.getContainerId.MediaMetadataCompat(:420)
   at o.isGooglePlayServicesAvailable.onCreate(:73)
   at android.app.ActivityThread.handleCreateService(ActivityThread.java:4940)
   at android.app.ActivityThread.access$1900(ActivityThread.java:310)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2300)
   at android.os.Handler.dispatchMessage(Handler.java:106)
   at android.os.Looper.loopOnce(Looper.java:226)
   at android.os.Looper.loop(Looper.java:313)
   at android.app.ActivityThread.main(ActivityThread.java:8663)
   at java.lang.reflect.Method.invoke(Native Method)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)

java.lang.NullPointerException: mapContent must not be null
   at o.JobInfo.v_(:395)
   at o.stopSelfResult.initViewTreeOwners(:692)
   at o.JobInfo.<init>(:220)
   at o.getContainerId.MediaMetadataCompat(:420)
   at o.isGooglePlayServicesAvailable.onCreate(:73)
   at android.app.ActivityThread.handleCreateService(ActivityThread.java:4940)
   at android.app.ActivityThread.access$1900(ActivityThread.java:310)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2300)
   at android.os.Handler.dispatchMessage(Handler.java:106)
   at android.os.Looper.loopOnce(Looper.java:226)
   at android.os.Looper.loop(Looper.java:313)
   at android.app.ActivityThread.main(ActivityThread.java:8663)
   at java.lang.reflect.Method.invoke(Native Method)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)

11:02:47.732   W   isGooglePlayServicesAvailable   initialize(), id: 20357260, serviceId: 101
11:02:47.737   D   getContainerId   onStartCommand(null), id: 20357260
11:02:47.746   D   Product   onReceive(o.setKeyline@5346827, Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4200010 (has extras) }), network change: OnNetworkChanged(isOnline=true, isWifiConnected=false)
11:02:47.749   D   getInstallBeginTimestampSeconds   onEvent(OnNetworkChanged(isOnline=true, isWifiConnected=false)), requestSync: false
11:02:47.750   D   zzbcz   checkDayNightState()
11:02:47.759   W   WidgetTrackRecordCore   onUpdate(o.setKeyline@5346827, android.appwidget.AppWidgetManager@58925f3, []), no widget IDs to refresh
11:02:47.772   D   setCheckedIcon   onStart: activate(), res: true, suc: true
11:02:47.776   W   WidgetTrackRecordCore   onUpdate(o.setKeyline@5346827, android.appwidget.AppWidgetManager@58925f3, []), no widget IDs to refresh
11:02:48.198   D   setCheckedIcon$MediaBrowserCompat$CustomActionResultReceiver   onStart: fetchAndActivate(), res: true, suc: true, ex: null
11:02:48.207   D   setCheckedIcon   loadSslCertificates(), cert 'cert_zbgis_skgeodesy_sk_20211016.cer' not active
11:02:48.213   D   setCheckedIcon   loadSslCertificates(), cert 'cert_kataster_skgeodesy_sk_20211016.cer' not active
11:02:48.216   D   setCheckedIcon   loadSslCertificates(), cert 'cert_outdooractive_com_20200125.cer' not active
11:02:48.220   D   setCheckedIcon   loadSslCertificates(), cert 'cert_road_atlasltd_cz_20210630.cer' not active
11:07:52.125   D   zzbcz   checkDayNightState()
11:10:23.232   W   OptimizationDetectorImpl   analyzeEvents(), optimization detected!, events: IsAliveEvent[timeStart: 11:04:05, timeEnd: 11:07:06, expectedDelay: 60000, requireAwake: true, true, delayed: true], IsAliveEvent[timeStart: 11:07:06, timeEnd: 11:10:20, expectedDelay: 60000, requireAwake: true, true, delayed: true]
11:12:52.112   D   zzbcz   checkDayNightState()
11:17:54.109   D   zzbcz   checkDayNightState()
11:22:54.136   D   zzbcz   checkDayNightState()
11:27:54.090   D   zzbcz   checkDayNightState()
11:32:54.110   D   zzbcz   checkDayNightState()
11:33:46.184   D   Product   onReceive(o.setKeyline@5346827, Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4200010 (has extras) }), network change: OnNetworkChanged(isOnline=false, isWifiConnected=false)
11:33:46.192   D   getInstallBeginTimestampSeconds   onEvent(OnNetworkChanged(isOnline=false, isWifiConnected=false)), requestSync: false
11:33:58.797   D   Product   onReceive(o.setKeyline@5346827, Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4200010 (has extras) }), network change: OnNetworkChanged(isOnline=true, isWifiConnected=false)
11:33:58.801   D   getInstallBeginTimestampSeconds   onEvent(OnNetworkChanged(isOnline=true, isWifiConnected=false)), requestSync: false
11:35:28.286   D   Product   onReceive(o.setKeyline@5346827, Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4200010 (has extras) }), network change: OnNetworkChanged(isOnline=false, isWifiConnected=false)
11:35:28.289   D   getInstallBeginTimestampSeconds   onEvent(OnNetworkChanged(isOnline=false, isWifiConnected=false)), requestSync: false
11:35:28.459   D   Product   onReceive(o.setKeyline@5346827, Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4200010 (has extras) }), network change: OnNetworkChanged(isOnline=true, isWifiConnected=false)
11:35:28.463   D   getInstallBeginTimestampSeconds   onEvent(OnNetworkChanged(isOnline=true, isWifiConnected=false)), requestSync: false
11:37:54.130   D   zzbcz   checkDayNightState()
11:42:54.092   D   zzbcz   checkDayNightState()
11:47:59.095   D   zzbcz   checkDayNightState()
11:53:00.123   D   zzbcz   checkDayNightState()
11:58:00.122   D   zzbcz   checkDayNightState()
12:03:01.111   D   zzbcz   checkDayNightState()
12:08:11.135   D   zzbcz   checkDayNightState()
12:13:11.204   D   zzbcz   checkDayNightState()
12:18:55.127   D   zzbcz   checkDayNightState()
12:23:57.114   D   zzbcz   checkDayNightState()
12:28:57.120   D   zzbcz   checkDayNightState()
12:29:25.527   D   glUniform4fv   onStartSync(time.google.com)
12:29:28.301   D   glUniform4fv   onSuccess(-2866, 2776)
12:29:28.306   D   glUniform4fv   onStartSync(time.google.com)
12:29:28.382   D   glUniform4fv   onSuccess(-2927, 76)
12:33:57.137   D   zzbcz   checkDayNightState()
12:39:00.092   D   zzbcz   checkDayNightState()
12:44:35.121   D   zzbcz   checkDayNightState()
12:49:39.453   D   zzbcz   checkDayNightState()
12:54:39.392   D   zzbcz   checkDayNightState()
13:00:00.142   D   zzbcz   checkDayNightState()
13:05:12.088   D   zzbcz   checkDayNightState()
13:10:12.127   D   zzbcz   checkDayNightState()
13:15:12.121   D   zzbcz   checkDayNightState()
13:20:12.164   D   zzbcz   checkDayNightState()
13:25:12.145   D   zzbcz   checkDayNightState()
13:27:40.907   D   doAction$IconCompatParcelizer   wrap(android.app.ContextImpl@b972a47), set custom locale: en
13:27:40.984   I   obtainMessage   MEMORY info: MainActivity - onCreate(), savedInstanceState: Bundle[{com.google.app_measurement.screen_service=Bundle[mParcelledData.dataSize=120], MA_PANEL_RIGHT_VISIBILITY=8, clearFragments=false, android:viewHierarchyState=Bundle[mParcelledData.dataSize=7724], MA_PANEL_BOTTOM_VISIBILITY=true, appId=0.5124987718850051, androidx.lifecycle.BundlableSavedStateRegistry.key=Bundle[mParcelledData.dataSize=2564], MAC_SCREEN_LOCK_LOCKED=false, android:lastAutofillId=1073744339, android:fragments=android.app.FragmentManagerState@9c3012}] (41ms)
13:27:40.987   I   obtainMessage    - nativeHeapSize: 56.06 MB
13:27:41.000   D   readDiffed   currentActivity set to com.asamm.locus.basic.features.mainActivity.MainActivityMap@e0eccf8
13:27:41.042   D   eglGetCurrentDisplay$RemoteActionCompatParcelizer   db, creating CRS database, refresh: false, valid: true, file: /data/user/0/menion.android.locus/app_various/crs.db, size: 5222400
13:27:41.046   D   eglGetCurrentDisplay$RemoteActionCompatParcelizer   db com.asamm.locus.projection.crs.CrsDatabase_Impl@3d84922 created, dao: o.glBindBuffer@babafb3
13:27:41.055   D   setGLWrapper   ReLinker: Beginning load of proj...
13:27:41.059   D   setGLWrapper   ReLinker: proj (null) was loaded normally!
13:27:41.069   W   getPreferences   setCorrectBackgrounds(false), enabling hardware acceleration
13:27:41.125   D   BluetoothGattDescriptor   init started
13:27:41.138   D   BluetoothGattDescriptor   init done
13:27:41.174   I   getGooglePlayServicesAvailabilityRecoveryIntent   initActions(), completed, actions: 83
13:27:41.176   D   zzary   validatePanels(), duplicate action 10065 detected
13:27:41.177   D   zzary   validatePanels(), duplicate action 10065 detected
13:27:41.179   D   zzary   validatePanels(), duplicate action 10065 detected
13:27:41.184   D   zzary   validatePanels(), duplicate action 10065 detected
13:27:41.186   D   zzary   validatePanels(), duplicate action 10065 detected
13:27:41.187   D   zzary   validatePanels(), duplicate action 10065 detected
13:27:41.189   D   zzary   validatePanels(), duplicate action 10065 detected
13:27:41.190   D   zzary   validatePanels(), duplicate action 10065 detected
13:27:41.272   D   getVendorId   setState(WAITING, false), attempt to set same existing state
13:27:41.276   W   FMA-glUniform4i   getDirectoryDefault(), pref: PrefSetDirectory [key: KEY_S_DEFAULT_FOLDER_EXPORT_2, value: , isDefault: true], root: /sdcard/Locus
13:27:41.577   W   setMaximumScale   Unknown type:exportStorageEntry, {"iconLink":"","length":241664,"id":"\/storage\/emulated\/0\/Locus\/export","lastModified":1650295203000,"mimeType":"","history":[],"title":"export","parentId":"\/storage\/emulated\/0\/Locus","isDirectory":true,"storageId":0}
13:27:41.579   E   SAAgentV2   loadQueueFromStorage()
java.lang.StringIndexOutOfBoundsException: length=1132; regionStart=1125; regionLength=-1
   at java.lang.StringFactory.newStringFromBytes(StringFactory.java:71)
   at o.cONN.MediaBrowserCompat$MediaItem(:127)
   at o.getAccessoryId.readObject(:329)
   at o.cOh.read(:107)
   at o.SAAgentV2$1.RatingCompat(:380)
   at o.SAAgentV2$1.<init>(:66)
   at o.SAAgentV2$1.<init>(Unknown Source:0)
   at o.SAAgentV2$1$MediaBrowserCompat$CustomActionResultReceiver.RemoteActionCompatParcelizer(:458)
   at com.asamm.locus.basic.features.mainActivity.components.MacPanelBottom.MediaBrowserCompat$SearchResultReceiver(:339)
   at com.asamm.locus.basic.features.mainActivity.components.MacPanelBottom.write(:286)
   at com.asamm.locus.basic.features.mainActivity.components.MacPanelBottom.read(:291)
   at com.asamm.locus.basic.features.mainActivity.components.MacPanelBottom.RemoteActionCompatParcelizer(:160)
   at com.asamm.locus.features.mainActivity.components.MacBase.RemoteActionCompatParcelizer(:110)
   at com.asamm.locus.features.mainActivity.panelHelper.PanelHelper.RemoteActionCompatParcelizer(:80)
   at o.pauseSession.read(:396)
   at o.pauseSession.onCreate(:195)
   at android.app.Activity.performCreate(Activity.java:8290)
   at android.app.Activity.performCreate(Activity.java:8270)
   at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1329)
   at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4009)
   at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4201)
   at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:103)
   at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
   at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2438)
   at android.os.Handler.dispatchMessage(Handler.java:106)
   at android.os.Looper.loopOnce(Looper.java:226)
   at android.os.Looper.loop(Looper.java:313)
   at android.app.ActivityThread.main(ActivityThread.java:8663)
   at java.lang.reflect.Method.invoke(Native Method)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)

java.lang.StringIndexOutOfBoundsException: length=1132; regionStart=1125; regionLength=-1
   at java.lang.StringFactory.newStringFromBytes(StringFactory.java:71)
   at o.cONN.MediaBrowserCompat$MediaItem(:127)
   at o.getAccessoryId.readObject(:329)
   at o.cOh.read(:107)
   at o.SAAgentV2$1.RatingCompat(:380)
   at o.SAAgentV2$1.<init>(:66)
   at o.SAAgentV2$1.<init>(Unknown Source:0)
   at o.SAAgentV2$1$MediaBrowserCompat$CustomActionResultReceiver.RemoteActionCompatParcelizer(:458)
   at com.asamm.locus.basic.features.mainActivity.components.MacPanelBottom.MediaBrowserCompat$SearchResultReceiver(:339)
   at com.asamm.locus.basic.features.mainActivity.components.MacPanelBottom.write(:286)
   at com.asamm.locus.basic.features.mainActivity.components.MacPanelBottom.read(:291)
   at com.asamm.locus.basic.features.mainActivity.components.MacPanelBottom.RemoteActionCompatParcelizer(:160)
   at com.asamm.locus.features.mainActivity.components.MacBase.RemoteActionCompatParcelizer(:110)
   at com.asamm.locus.features.mainActivity.panelHelper.PanelHelper.RemoteActionCompatParcelizer(:80)
   at o.pauseSession.read(:396)
   at o.pauseSession.onCreate(:195)
   at android.app.Activity.performCreate(Activity.java:8290)
   at android.app.Activity.performCreate(Activity.java:8270)
   at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1329)
   at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4009)
   at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4201)
   at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:103)
   at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
   at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2438)
   at android.os.Handler.dispatchMessage(Handler.java:106)
   at android.os.Looper.loopOnce(Looper.java:226)
   at android.os.Looper.loop(Looper.java:313)
   at android.app.ActivityThread.main(ActivityThread.java:8663)
   at java.lang.reflect.Method.invoke(Native Method)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)

13:27:41.615   D   getFormattedEnergy   prepareExpandedContainer(), layout not valid or not expandable
13:27:41.623   W   FMA-glUniform4i   getDirectoryDefault(), pref: PrefSetDirectory [key: KEY_S_DEFAULT_FOLDER_MAPS_VECTOR, value: , isDefault: true], root: /sdcard/Locus
13:27:41.632   D   glEnable$IconCompatParcelizer   setHighlight(com.android.internal.policy.PhoneWindow@255eea), required: false
13:27:41.636   D   MainActivityDashboardImpl   isDashboardVisible(), top visible

Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: slarti76 on April 21, 2022, 23:08:30
Some thoughts about PIP:
First of all, I like it very much - finally playing Pokémon GO on the bike and navigating with Locus at the same time (don't tell the police ;).
I tried it today, but still had 4.8.2.1 - before I write a post, I thought I'd update... But something's broken in .2: I can't increase the size of the window to more than half the width of my screen. Before, I could increase it to like 90% of full width. Like this, it's much too small. It's also 3:2 now, instead of 1:1, but it's always fixed, which I find an unnecessary restriction. Depending on app that is overlayed I'd prefer to be able to change size more or less freely.
I'm also not able anymore to move it anywhere - the window is either magnetic on the left or right, I can't have it in the middle.
All that worked before (apart from the ratio which was always fixed).
Some more observations:

PS: I never had a problem when switching between PIP and Fullscreen, Locus never disappeared or the like.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: slarti76 on April 21, 2022, 23:16:28
Oh, I also tried the improved map shading. My result is very surprising: While the slope shading is greatly improved (screenshots 1&2), the Hill Shading shows no improvement at all (screenschots 3&4).
All screenshots are ZL12 with 2xEnlargement and ZL13.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Andrew Heard on April 22, 2022, 00:30:18
Quote from: joeloc on April 21, 2022, 16:53:32
...I run a "watchdog" since a few months that checks for Locus every minute and restarts it when it's gone.
@joeloc sorry to read of your troubles - I don't have those problems, will keep 2017 Samsung phone as long as possible, but could you possibly share more details of your "watchdog" - just curious. Best wishes Andrew.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 22, 2022, 11:26:11
@razvaneduard
sorry it does not work, but I see no reason why it should not work by default. It is a little more complicated to find a reason and because it is really a feature for testing, I do not want currently spend time on it, thanks for understanding.

@joeloc
"3 times a day"? May you create a log after the app crash? Anyway, I had some time ago also troubles with the camera and it was an unsolvable problem. The camera app was so memory-hungry, that system killed everything on background ...

Anyway fact that the database is big should have no impact here. SGS20 is so powerful device, uff. Let's try a log, please. At least to verify that it is/isn't a problem directly of the app.

@balloni55
heh, I remember. That's why I still keep the "custom screens" feature in the app  :). How you were able to find this 7 years old post  :o

@michaelbechtold
hard to say if this is the same issue as in the case of joeloc. These app logs usually do not contain final crash that caused termination, unfortunately. If there are situations where it happens almost always, I suggest reducing the memory requirements of the Locus just for tests. Disable some overlays, disable shading, reduce the amount of points/tracks visible on the map ...

@slarti76
Locus & Pokémon GO  ;D

Thanks for the tests! You were really able to resize and move this PiP window fully freely? Weird, it should not be possible. It is also not possible to define own custom buttons there. For this, you may simply use the split-screen mode of your device, you do not need a PiP.

Anyway
- map rotation > agree, I'll look at it.
- map zoom > there should be no changes when switching to PiP, so you should see a zoom visible on current map.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: slarti76 on April 22, 2022, 12:00:00
Quote from: Menion on April 22, 2022, 11:26:11
@slarti76
Locus & Pokémon GO  ;D
Guilty pleasure... ;)

Quote from: Menion on April 22, 2022, 11:26:11Thanks for the tests! You were really able to resize and move this PiP window fully freely? Weird, it should not be possible.
Well, as I said, ratio was fixed, but I could make it much bigger. Is that really not supposed to be possible? I mean, e.g. if I use VLC as pop-up, I can resize it to like 90% of the screen width (but also the ratio is fixed).
Ah, I just realized something: A video is, of course, in landscape - so resizing to full width is possible. Locus was initially 1:1, which obviously also allowed it. Once you changed the ratio to 3:2, it's not possible anymore, because then you could basically resize it the more or less full screen size. So Android doesn't allow it. Of course it's ridiculous why Android forces this on the user, also that snapping to left or right of screen, but we all know Google...
Does that sound like a possible explanation to you? (I don't have a portrait video around that I could try with VLC...)
Anyway, perhaps you could at least let the user choose whether it wants the pop-up in portrait, landscape, or square. Everything after that is Android, and we have to live with it. But 3:2 portrait is very likely not what you want in every situation...

Quote from: Menion on April 22, 2022, 11:26:11It is also not possible to define own custom buttons there. For this, you may simply use the split-screen mode of your device, you do not need a PiP.
Sure, ok. But then why have that bar at all? As I said, just put the Navi Icon in the upper left and voilà - space saved...

Quote from: Menion on April 22, 2022, 11:26:11Anyway
- map rotation > agree, I'll look at it.
Thx
Quote from: Menion on April 22, 2022, 11:26:11- map zoom > there should be no changes when switching to PiP, so you should see a zoom visible on current map.
Oh, you're right, didn't realize that. However, I had "Automatic Zooming" on, and that doesn't seem to work in PIP - could that be enabled there, too?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: joeloc on April 22, 2022, 17:08:42
Quote from: Andrew Heard on April 22, 2022, 00:30:18
Quote from: joeloc on April 21, 2022, 16:53:32
...I run a "watchdog" since a few months that checks for Locus every minute and restarts it when it's gone.
@joeloc sorry to read of your troubles - I don't have those problems, will keep 2017 Samsung phone as long as possible, but could you possibly share more details of your "watchdog" - just curious. Best wishes Andrew.
My watchdog is a super simple macro for MacroDroid. It checks periodically for the presence of Locus notification (since apparently direct check for running apps is forbidden in newer Androids). If there is no Locus notification, it plays some warning text and simply starts Locus. Locus resumes track.recording nicely in this case, which is really all I care about.

@menion, I'd love to do logs n stuff, but apparently play store refuses to deliver beta versions (even though it says it does). So atm I'm still running public 4.8. Wasn't there a web page with the beta APKs. somewhere?

Camera is the main culprit when it comes to killing Locus, today it happened again. Just once though. It also happens to me when web surfing though... or when using the booking.com app. Anything really. Whenever Locus is in the background, it is in grave danger.

Funny though, only Locus gets killed. I never have problems with other background stuff, like Audible, VLC-Player for radio streams, etc.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: CabrioTourer42 on April 22, 2022, 21:48:26
"Wasn't there a web page with the beta APKs. somewhere?"

Link is at the bottom of every menion post. Check the one on page 6.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: joeloc on April 22, 2022, 22:02:38
Quote from: CabrioTourer42 on April 22, 2022, 21:48:26
"Wasn't there a web page with the beta APKs. somewhere?"

Link is at the bottom of every menion post. Check the one on page 6.
Thanks for helping a blind guy :-)

To make this posting worthwhile, menion, please look at the two pics. Can you make the altitude text under the arrow not clip so aggressively? It disappears completely when only one pixel is invisible, why? Also, if there are spaces, remove them. And replace the / with a space maybe? All that saves pixels without harming visibility. Maybe even render the units in fontsize/2?

I know I can make fonts smaller, but that's counter productive on a bumpy mountain bike in bright sunlight wearing dark glasses :-).

PS, the red and blue stuff on the map is the Strava Heatmap Overlay. Right here in Andalucia it shows about 300% more tracks and trails than OSM even knows about. Extremely useful... might be even worth askin Strava for an official agreement to include that somehow?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 22, 2022, 23:58:08
*** Beta version 4.8.2.3 ***

Among some fixes etc, one specialty for @balloni55 ;). Expert settings > Premium for LoCoins. And then check the screen with "Premium purchase". There should be a new option. We are still not perfectly sure where to please this option, so for now, it is hidden behind "Expert settings".

@slarti76 & @joeloc, thanks for your posts. I'll look at it (and answer) in the next few days ...
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Tapio on April 23, 2022, 07:09:45
Premium/LoCoins, interesting, this makes me notice my subscription renewal was end of march, which I didn't notice, my bad🙂 Money is a thing here unfortunately, I probably would have tried to put Locoins into it, but... so what... I will use the last money I have for asamm, I hope the business can stay successful.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: lor74cas on April 23, 2022, 10:06:41
Quote from: tapio on April 23, 2022, 07:09:45
Premium/LoCoins, interesting, this makes me notice my subscription renewal was end of march, which I didn't notice, my bad Money is a thing here unfortunately, I probably would have tried to put Locoins into it, but... so what... I will use the last money I have for asamm, I hope the business can stay successful.
The same for me, maybe next year

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on April 23, 2022, 11:28:40
thank you for implementing the payment option "premium version" with LoCoins.
unfortunately I can test it only in a year, because I had in the meantime a 2 weekly test subscription which has automatically renewed itself without asking... :-\

my credit on GooglePlay is 0 euro, but I had allowed the alternative payment option with PayPal, my mistake :-[

When looking over it I noticed 3 more things
- icons in expert settings are not completely displayed
- button to pay monthly is blue/active, it should be gray/inactive > when clicked an error message occurs
- in the subscription page should be visible hints about how the payment is done

Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Tapio on April 23, 2022, 12:19:24
I wonder how much a premium gold or silver subscription would cost converted to LoCoins. Currently I have like 800, stacking up, because of the sporadic Asamm "we have a gift for you"...
EDIT: Ah I see, Gold = 2100 per year according to above screenshot.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on April 23, 2022, 12:50:20
Quote from: tapio on April 23, 2022, 12:19:24
EDIT: Ah I see, Gold = 2100 per year according to above screenshot.
Paying with LoCoins is a bit more expensive then, I will do it anyway, also to support the team

100 LoCoins > 1,19Euro that makes 24,99 Euro/year vs. GooglePlay 23,99/year
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: joeloc on April 23, 2022, 14:07:06
Is the overlay not rendered at all when it's max zoom differs too much from current zoom? My Strava Heatmap has a max zoom of 11 (the russian server doesn't serve more at the moment I guess). Locus at Zoom 16, all is fine. Locus at Zoom 17, overlay is not rendered at all. See pics.

Or do overelays disappear at Zoom 17 in general? Can I prevent this? I'd always like to see the Heatmap,.no matter what.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: joeloc on April 23, 2022, 20:30:40
Planning my future route, I scroll through the map in my intended direction and find an interesting looking place. First thing is setting a waypoint, name is mostly correct due to Locus query magic. Now I want to Google that place... and juggle with edit/clipboard/copy/paste/madness to get the name.into a web browser. Could you add "google search" to the sharing menu in Locus? It should work for points/tracks/everything that has a "name" basically.

Would make life a bit easier on the road.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 23, 2022, 20:51:36
@tapio & @balloni55 & @lor74cas
sorry, we wanted to have this feature completed till 2021, but we were too optimistic.

But thanks for your support. I'm sure, people that work together with me on Locus Map (GIS) appreciate it  ;)

Price: when we work with LoCoins, we use some "average price" for LoCoin, so the price should be close to equal. There is many people who have quite a lot of LoCoins (for example rewards for help with translations, some gifts from us etc.) and till now, there was no useful place where to spend a higher number of LoCoins. We also plan, hopefully soon, features where users should be able to pay with LoCoins to other users, so ...

Anyway purchasing LoCoins and then Premium for LoCoins does not make sense.

@balloni55
- icons in "expert" > I know. Looks easy, but I still did not find a solution  ???
- button to purchase monthly Premium > may you post me a visible error? Thanks
- "in the subscription page should be visible hints about how the payment is done" > what do you mean by this?

@joeloc
hmm what happens to you is expected to be true. All maps have a hardcoded maximal rescale of 1600% (5 zoom levels). Based on tests, maps rescaled more than 1600% are completely useless.
I understand your use case, but can't imagine using the same heat map images in another zoom level rescale to 3200% or more. Really unique solution I believe, sorry.

Sharing the name > try to tap on the "Share > Text message". Here, the name should be pre-filled so only tap on big "Share" button should be enough.

EDIT:
style of texts along the line: I know the current solution is not ideal. It is close to impossible to draw along these lines texts in two font sizes as I do in the dashboard ... unfortunately. Maybe there is some nice font that has numbers bigger than letters?
About hiding > it is about available space. So once we reduce the required width, the text remains visible even for shorted part of the line...
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: joeloc on April 24, 2022, 08:53:53
@menion, i understand that scaling too much doesn't make much sense for anything else. For a Heatmap though, resolution doesn't really matter much. And things that magically disappear are just irritating :-). I am only bothering you with this btw because the Heatmap has become the tool of choice for finding my way. It beets OSM hands down even in places where people maintain OSM nicely... and especially where they don't. You can even judge the difficulty of a trail easily... it's almost magic for mountain biking.

Maybe the hardcoded zoom limit could be turned into something in providers.xml for the future?

Speaking about disappearing things besides the  max zoom issue: the overlay disappears way too often when internet is bad and I zoom around. I know you like blaming the server, but really... there is just no reason for something to disappear when it was loaded just minutes ago. It's especially frustrating when this is your main source for navigation because your offline maps contain nothing. Are you sure your tile caching works correctly? It seems to me you invalidate the cache too early, like when you send the http request for new data (at new zoom level). All cached things.should remain valid until new data is successfully received obviously, not just requested. Just an idea... that's how it "feels" here.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: balloni55 on April 24, 2022, 08:55:39
Quotebutton to purchase monthly Premium > may you post me a visible error?
see attachement
Quotein the subscription page should be visible hints about how the payment is done" > what do you mean by this?
the normal user is used to pay via GooglePlay directly or PayPal and he doesn't know that there is also a possibility to pay with LoCoins.
This possibility he notices only if he goes the way about "other purchase options".

maybe a selection menu
"pay with LoCoins"/ "pay via GooglePlay" would be useful
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: joeloc on April 24, 2022, 08:58:46
Regarding sharing names... not sure I get what you meant. I want to web search for any names on the map with the least hassle possible. Tap a POI, select share, select websearch. Tap a track, select share, select websearch, long tap anything on the map, select share, select websearch.

How would I do this in current Locus? To get from any name on the map (eg Refugio Coolplace) to
https://www.google.com/search?q=refugio+coolplace

websearch meaning: send whatever "name" to default browser default search engine.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: lor74cas on April 24, 2022, 09:21:41
A little inconsistencies in the map download window.
The two terms are in conflict one says "updating" the other says "done"(https://uploads.tapatalk-cdn.com/20220424/8d91ba9940eec0a16a08c2be9b3ee86b.jpg)

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: joeloc on April 24, 2022, 23:58:11
Here are my logs when Locus was killed by Samsung Camera today. Sorry for size, can't really edit huge text files properly on the road.

The log is filled with thousands LiveTracking failed due to offfine events every second or so. A possible problem in Locus, unrelated to killing? At least it pollutes the log... but does it really need to be tried every second? Shouldn't it just wait for online status change or something? Interval is configured to 3 minutes.

17:33:37.457   D   LiveTrackingCustomService   sendNewEvent(false)
17:33:37.460   W   LiveTrackingCustomService   handlePendingEvents(), device is not online, send later
17:33:38.473   D   LiveTrackingCustomService   sendNewEvent(false)
17:33:38.477   W   LiveTrackingCustomService   handlePendingEvents(), device is not online, send later
17:33:39.487   D   LiveTrackingCustomService   sendNewEvent(false)
17:33:39.554   W   LiveTrackingCustomService   handlePendingEvents(), device is not online, send later
17:33:40.466   D   LiveTrackingCustomService   sendNewEvent(false)
17:33:40.471   W   LiveTrackingCustomService   handlePendingEvents(), device is not online, send later
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: CabrioTourer on April 25, 2022, 16:10:50
Is there any documentation how cloud sync works?
I try to find out what is the rule if a track was change on two devices.
The "compute sync plan" doesn't help. To be true I think it's useless.
In my case it reports 185 pull deletion for tracks.
But cloud and local should be more or less the same.
Without a report which tracks are affected and why the plan is useless in my pov.
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Menion on April 25, 2022, 16:16:52
New version 4.9, so please, the new topic here (https://forum.locusmap.eu/index.php?topic=7917.msg67619#msg67619).

@joeloc
In the new version is an option to set an "unlimited" scale for overlay, so try it please.

About missing map tiles > it is not a problem too short validity of the cache, but rather a problem in how the app fills gaps with map tiles from other zoom levels.

Sharing names > oki, understand. Hmm, there is probably no solution for now, agree ...

@balloni55
I had not enough time to check your report about the purchase of premium a little deeper before the new version. I'll look at it next few days.

@lor74cas
thanks, I'll look at it.

@CabrioTourer
docs? Hmm, nope. The last wins, always. Does it help?
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Neoaliphant on April 27, 2022, 13:21:23
Quote from: balloni55 on April 23, 2022, 12:50:20
Quote from: tapio on April 23, 2022, 12:19:24
EDIT: Ah I see, Gold = 2100 per year according to above screenshot.
Paying with LoCoins is a bit more expensive then, I will do it anyway, also to support the team

100 LoCoins > 1,19Euro that makes 24,99 Euro/year vs. GooglePlay 23,99/year

ive just paid with locoins, bought 1060 locoins for £9.63
google play subsctiption is £20.99    with locins the same is £19.07 so locoins is cheaper....
and as i havnet been using the free 600 locoins a year, even cheaper again...
Title: Re: [APP] - version 4.8.+ ( 04/2022 )
Post by: Viajero Perdido on April 27, 2022, 17:55:44
4.9 seems to have fixed the navigation-becomes-guidance issue I mentioned upthread, thanks.

Can't be absolutely sure without spoofing GPS or physically going back to the trail, but I'm pretty sure.  :)