Messages

[[DE translation]]

[DE translation]

Hmm ... alles klar ... tut mir leid
Ich muss wohl meine Arbeitsweise ändern ...

EDIT:
In den letzten Monaten musste ich viele größere Änderungen am Kern der App vornehmen. Aufgrund der Komplexität der App und mangelhafter interner Testmechanismen sind unerwünschte Probleme in die öffentlichen Versionen gelangt.

Ich muss im Hintergrund noch einige weitere Änderungen vornehmen, um die App für die nächsten Jahre vorzubereiten. Ich kann nur versprechen, vorsichtiger zu sein und alles bis Juli fertigzustellen. Das ist der Plan.

Ich bitte euch also um noch ein wenig Geduld. Zögert nicht, mich anzusprechen, falls noch Probleme bestehen. Außerdem stelle ich euch gerne einen Gold-Gutschein als Entschädigung für die Unannehmlichkeiten zur Verfügung. Schreibt mir einfach.

Puh, habt ein schönes Wochenende ...

Übersetzt mit DeepL.com (kostenlose Version)

[EN]
Hmm ... fully understood... sorry
I probably need to change the way I work...

EDIT:
last few months, I had to do a lot of major changes in the app core. Because of app complexity and bad internal testing mechanisms, unwanted issues passed to public versions.

I still need to do some more changes on the background to have app prepared for next years. I may only promise to be more careful and finish all till the July. That's the plan.

So I may ask only for a little more patience. Do not worry to push to me if there still remains any problems. Also, I'll gladly provide a Gold voucher as a compenstation of troubles. Just write to me.

Uff, have a nice weekend ...

[Google Drive is another version 4.33.0.9]

Hi guys,
I wasn't reading your responses (just really quickly), so sorry. Will look at it next week.

Instead, on the Google Drive is another version 4.33.0.9 ... more of an "alpha". So, do not update if you are ok with 4.33.0.8 and need a stable weekend version.

Otherwise, short list of changes for the brave 

   - chg: completely new picker for locations integrated into main search view
   - add: support for custom user-defined locations in Android Auto
   - fix: AR view, incorrect points movement
   - fix: Android Auto - centering on the found point
   - fix: Android Auto - crash when starting navigation in some cases
   - add: Android Auto - "Route overview" mode during active navigation
   - fix: clear highlight of selected (track) waypoint
   - fix: crash when taking a photo to LoPoints
   - fix: minor problems in chart system
   - fix: new chart consuming tap events if not needed
   - add: support for In-app updates system (app will inform about the new version if not updated for 1+ month)
   - fix: crash when 2+ track recording widgets were used
   - fix: memory leak in scanner for BT4 devices
   - fix: memory leak in main screen panels
   - fix: crash when cache directory is temporarily unavailable on external storage
   - chg: Dashboard charts now do not display value bubbles
   - fix: wrong colors and checkbox ignoring in track overview generator
   - fix: Dashboard charts correctly use defined text color
   - chg: improved prevention of navigation on overlapping segments
   - fix: too early "End of navigation" on circular routes
   - fix: photo description/caption missing from KMZ export
   - fix: internal server error when downloading multiple Pocket Queries
   - fix: severe performance regression with large point folders (1 000+ points)
   - chg: ensure visible directional arrows when highlighting a track

Zdravím,
je to takový tajnější ... zkus prostý dlouhý stisk na fotku přímo v detailu bodu.

Yes, Claude Opus 4.6 analysed this.

---

I also wanted to confirm to myself that there is nothing wrong with the code we did.

At least, I'm still after five years, unable to find a difference, and AI "confirm it".

Hi balloni,
oki, should be improved in the next version.

What do you mean by the "FolderComment"?

[What's happening]

Hi guys,
I've let AI analyse source codes of old Locus Classic and new Locus Map, search over the web and do some bigger analysis ... here is the result ...


What's happening

Samsung devices include a hidden system service called SDHMS (Samsung Device Health Manager Service, package com.sec.android.sdhms). Among other things, it has a "Brightness Limit" feature that reduces display brightness at a hardware level — below the Android brightness API. This is why the brightness slider stays at maximum (255) while the screen visibly dims to roughly 200 nits (~30% reduction). The normal brightness API has no idea this is happening.

This is the same mechanism that users previously fixed using Alliance Shield X — those "two hidden switches" were the SDHMS settings "Brightness Limit Off" and "CP TM Off".


Why LM4 but not Classic?

Samsung also runs a service called GOS (Game Optimizing Service) that downloads a list of app package names from Samsung's servers and applies throttling to them. In March 2022, it was publicly revealed that GOS throttles over 10,000 apps — not just games, but also Instagram, Netflix, Google Keep, and even Samsung's own apps like Samsung Pay. The throttling was proven to work by package name: a Korean researcher showed that renaming an app's package to match a throttled app immediately triggered the restrictions.

Both LM4 and Classic share the same core rendering code. The only significant difference is the package name: menion.android.locus (LM4) vs menion.android.locus.pro (Classic). If Samsung's server-side list includes LM4's package but not Classic's, that alone would explain the entire issue — same code, same device, different behavior.

This also explains why:

• Google Maps is also affected — it's likely on the same list
• TwoNav/OZI are fine — smaller apps, not on the list
• Some Samsung devices are immune — different firmware versions carry different lists/thresholds
• Android/One UI updates sometimes help — Samsung recalibrates thresholds with updates
• Non-Samsung devices are never affected — no SDHMS/GOS

How to verify (for affected Samsung users)

If anyone with the problem is willing to test, here are two approaches:

Option A — Check if SDHMS brightness limit is the cause:

• Install Shizuku (https://shizuku.rikka.app/) — requires enabling USB Debugging via ADB
• Install System UI Tuner from Play Store
• Through lock screen shortcuts, access the SDHMS thermal settings
• Toggle off "Brightness Limit Off" and "CP TM Off"
• Test LM4 in direct sunlight

If brightness holds steady, we've confirmed the cause.

Option B — Check if GOS has LM4 on its list:

Connect your Samsung device to a PC with ADB and run:
adb shell dumpsys package com.samsung.android.game.gos
Look for any reference to menion.android.locus in the output.


What can be done from the app side?

Unfortunately, there is no Android API that lets an app opt out of Samsung's SDHMS brightness throttling. The throttling happens at a layer below what apps can control. Possible paths forward:

• Contact Samsung developer support to request removal of the package from any throttle list
• Expose a diagnostic in LM4 that reads PowerManager.getThermalHeadroom() (Android 11+) so users can see if Samsung is reporting thermal pressure
• Document the workaround for affected users (Shizuku + System UI Tuner method described above)

If anyone can run the tests above and share results, it would help confirm whether this is indeed the SDHMS/GOS mechanism at work.

Jestli ti zlobí záloha a jsi ochoten nasdílet jí, pošli a já se na to rád obratem podívám! Děkuju!

Hmm ... so was there any problem in the XML itself? Not sure, right?

Hi, it is not possible to reset line styles for all folders at once, sorry.
Every folder has own style so feel free to reset all problematic styles manually.

Even a root folder has its own style. Just move to the root folder and tap on the "home" icon in the top-left to get the quick menu with the "Edit" option. Or under the three-dots menu > Tools > Edit.

Zdravím Josko,

promiň, nemám nicméně hlášen zásadní problém s poslední 4.33.0 verzí.

Ty jsi tou pře-instalací přišel o tvoje data, nebo jsi je měl zachované? Pokud zachované, v "logs" adresáři by mohli být soubory se zaznamenanými pády ...

Díky.

[version 4.33.0.8 (1211)]

Damn, another complication! All these bugs are caused by the update of the external libraries. In this case, it is the internal so-called "EventBus" that misses updates for 3+ years. It no longer works correctly with the most recent Android tools > another big modification is ahead because of this. For now, patched with a small hack ...

New version 4.33.0.8 (1211). Sorry, and thanks for the help!

[fixed in 4.33.0.7 (1211)]

Thanks guys, nasty bug ... fixed in 4.33.0.7 (1211)!

@Andrew Heard
thanks for the feedback. I'll look at it during the next week.

Have you tried the latest version I've just published?

[Locus Map 4.33.0.6 (1211)]

Locus Map 4.33.0.6 (1211)

Some nice additional and risky versions before the holidays.
  - add: integrated Augmented Reality solution (similar to old malfunction add-on)
  - chg: all "config.cfg" settings moved to the Expert settings (and config.cfg support removed)
  - chg: track recording widget rework (10+ year old solution rewrote to modern coat)
  - chg: major (really MAJOR) update of various internal libraries (unexpected behaviours may happen)
  - chg: another iteration in the "Smooth movement" algorithm
  - fix: multiple tracks selected at once
  - add: option to display waypoints (not the navigation orders) on the charts
  - add: support for tap on waypoints on the chart + highlight
  - add: zoom buttons in screen with track charts
  - fix: crash on Android 16 when setting the language
  - fix: rare crash in long click on the main map screen
  - fix: prevent crash when Sync screen resumes before sync is initialized
  - chg: improved line style to support "dotted style" (just dots on trackpoints)
  - chg: "Choose guidance dialog" rework
  - fix: geocache wpt list strips '*' due to Markdown italic conversion
  - chg: improved reliability of downloading maps from Locus Store
  - fix: improved handling of "Route URL" and better match to web planner version

Interesting.

You do not see any custom map in the Map manager > "Online" tab? Rather sort maps in this tab by "All maps" (at the top topbar) and now you should have all maps listed at the bottom with "User maps" header. Like on my screenshot.