Messages

[@michaelbechtold]

@michaelbechtold
Everything in the private folder is the expected result ... start count with it. Deadly? ... hard to say.

Exception for full filesystem access is no way. Google does not provide exceptions. Anyway  I'll be more precisely test it next weeks, so I'll, of course, inform about the final result ...

@Žajdlík Josef
currently, it is not an ideal solution. Tap on the first button in the bottom panel, it may help ...

@slarti76
works? Fine

@T-mo
what you see was in the app till version 4.3.0. In this version was introduced new full-screen mode that causes quite a lot troubles so in this Beta it is reverted to the old system - so black top useless panel on some devices.

@Pcmann
isn't there settings in "Preset" that active together with navigation and that overwrite this settings?

Hmm, this is useless file, so simply delete it without worry.
Maybe attach it here for me please, I'll check if I'll be able to simulate the same issue with your journal file. Thanks.

Ah, very good idea, thanks! Just keep on mind, that it is more a "device ID"  ... every device has its own ID. Maybe incorrectly, I started to call it "user ID".

[Beta version 4.3.2.3]

New Beta version 4.3.2.3 just uploaded.

Most of the problems should be fixed. At least the random stuck when panning with the map. @fresichneider reported that full-screen still cause problems. I'm unable to find or simulate any problem, stupid . Anyway, I'll keep looking, but full-screen on Android 9+ is something I would really like to remove completely ...

Just quick info before sleep ... four same crashes during my todays ride. I'm searching for the reason ...

Sorry for trouble!

Perfectly understand. But if "map center" is preferred, why not change it? 

[@Andrew Heard]

@Andrew Heard
As I wrote here.

You seems to really need "Always hide" option 

[@Viajero Perdido]

@Viajero Perdido
thanks. I've made an update on how the sync process starts when the app (re) starts or when the network/wifi connection changes. It should be better in the next version.

@Andrew Heard
and what is the problem with setting partial or full auto-hide option?

Hiding bottom track panel for the recorded track: how I missed this? Thanks, got it!

@baegas
thanks for the very precise video. Two devices I have with Android 9+ do not have this issue. Anyway, I've reverted some changes made to the full-screen system, so in tomorrow's coming Beta version, you may give a try, thanks!

@Christian
I'm sorry. In this rare case, I do not think that issue is directly on my side. Unfortunately, I also had a small mentioned vacation so the fix of this issue had to wait till now. Fortunately, a "disabled full-screen" workaround works.

@slarti76
Forget on the "Full-screen". Just check normal not-full-screen mode. There, on Android 9+, the map should be visible under system panels.

[@michaelbechtold]

@michaelbechtold
I'm checking the docs and I do not think so ...

It is still the same list of possible exceptions. Violation of this usually detects some robot that blocks the app. Emails on support usually end on people who are not skilled enough ...

It is another kind of "user protection" that only complicates life ...

Ah damn, one tiny issue. Thanks @baegas! I'll have to probably publish one more version today or in the morning (cause I'm then leaving for a few days on a small vacation).

[@flyingman_ch]

@flyingman_ch
You are missing hiking swiss topo maps in the list? Please check the "Available maps" option in the top toolbar of map manager. May you have disabled these maps some time ago?
Offline hiking swisstopo maps in the Store were in the app for a few years already. The difference is they were quite pricey. Now, they are for free > nice gesture from the Swiss...

@freischneider
Hmm, I still do not see any problem, no matter what I do on my own device. What device/Android version are you using? May you please also try to toggle
- app settings > Controlling > Display > Full screen
- app settings > Controlling > Display > unlock the screen

Does any of these two settings have any effect?

@ADiet
Issue detected, bug-fix version comes today, sorry for this.

@Andrew Heard
yes, I know. This is what cause the troubles with auto-hide before. I have to correctly set the visibility of the bottom panel, so if you make content visible, the bottom panel has to be visible even if is empty. We may experiment with it later, but for now, this should be a safe solution.

Scaling of panels: I wrote before that this feature is not (and won't be for now) supported in LM4. I've not yet removed this "support" from the side panel, but sorry > it will come. Panels are a little bit bigger then in LM Pro, so this scaling should not be necessary.

@baegas
I'm not sure from your description what exactly is the problem. But it may be similar to what ADiet wrote. So give a try next version, thanks.

Perfect! I do not know why there is such weird limitation, but at least we have confirmed it works, thanks too.

[@slarti76]

Hi guys,
the new version 4.3.0 is finally published. Enjoy it. And thanks for the help of course!
Let's continue in discussion in the new topic here: https://forum.locusmap.eu/index.php?topic=7496.0

@slarti76
Also a problem, I'm unable to simulate it. You test it on the "Galaxy Tab" right?

@luce
I'm still unable to simulate the same problem, funny . Will be watching it ...

@fresichneider
Are you sure you have the latest Beta? Weird. Please check the newly published version. I hope, there won't be such problem.

@Andrew Heard
Problem with double tap - check new version.

Missing "info button" > it is same as this button visible on the main map > only if there is some progress. I've updated it so it should now be visible also in case of any problem.

Hi guys, the discussion here is not necessary.

As I wrote, I'm well aware of this issue. I've compared all major parts of LM4 and LM Pro that differ and can't find any reason why it should affect screen dim. I've also updated all possible libraries that the app use and still no difference. It has to be some issue on the Samsung (if on all devices or not is not important now), but it has to be somehow connected to anything in the LM4 app ...

So for now, I blame my code, but ...

Hi,
we were already fighting this issue a long time ago. Please read the orange box in our manual below this setting and let me know if this helped.