Messages

Hi Menion.

The linked picture in gpx track description is not displayed in Locus.
File: BOM_navwpt.zip

+ attachment (Add picture). See gif.

[Change Point name in Locus]

Change Point name in Locus

Rename the associated photo.
Use Android file explorer or by photo galery app.
https://play.google.com/store/apps/details?id=gallery.photos.video.quickpic.fastopenphotosvideos&hl=en

By add + attachment recouple the renamed photo.
https://docs.locusmap.eu/doku.php?id=manual:user_guide:points:management&s#attachments
- Remove the old (now greyed out) photo path.

https://forum.locusmap.eu/index.php?topic=7016.msg60193#msg60193

+ Zwei Befehle zusammenfassen Option deaktivieren.

Das Deaktivieren von Strict wird Ihr Problem sicherlich lösen.
Der strenge Modus (Sie müssen JEDEN Streckenpunkt "verbrauchen") war außergewöhnlich bedacht für MTB-Strecken, die manchmal mehrere Überlappungen auf derselben Straße verwenden. Eine abweichung kontte daher manchmal die falsche "Überlappung" wählen. Mit dem strict modus können Sie das verhindern, aber das hat auch viele Nachteile. Zum beispiel, wenn Sie das GPS-Signal verlieren, während Sie durch einen tunnel fahren. Nach dem Verlassen müssen Sie dan mit 'Nächster Punkt' korrigieren. Und dan hoffen dass Locus auf dem richtigen Track-Segment landet, wenn es sich um einen überlappenden Teil des Tracks handelt. Wie im Lotto. "Ohne gewähr"
Rat. Verwenden Sie strict niemals, es sei denn, Sie wissen genau, warum Sie es dringend benötigen.

@ JackRussel.
Ohne Neuberechnung.  (Und ganz wichtig , nicht strict !)
Beim erneuten zusammenfügen des entwurfs in vorwärtsspur-entwurfsrichtung übernimmt die navigation den entwurf automatisch wieder ? Nein ?
Bitte fügen Sie ein beispiel einer design-navigationsspur bei. Zusammen mit der problemspur (Rekord). Beide als gpx.

Routeplanner > Add Via Point > Edit Name, symbol, and comment > Save > Navigate.
Dies könnte Sie auch interessieren.  https://help.locusmap.eu/topic/n-a_145

I tested....The Android time out does turn the screen off. Android time out set for this test = 15 seconds.
Observe the turn alert display ON action, than the DIM action soon followed by total display OFF.
The typical Android time out sequence. By the screen recorder the dim is not optimally displayed. In real direct screen view is observable nicely. Compare with display OFF by Locus Pro: Is immediately without dim action.
All next turn alerts notice always the same sequence. (I did not record the turn instruction sound).
Need other app than the Locus active one ?  For example Geocaching app =  asks the PIN.

Video: https://youtu.be/2yHtJBKCZDo
Settings: See picture. (login to the forum)

The proximity Gesture sensor.
I have experiences with 2 (old) Samsung, 2 THL and a Xiamo Mi A2 Lite Phone.
On these phones the method was and is perfectly functional.
See a wave action in use in an old video recording here.
By very low memory Samsung Ace (gps use only).
No Google services nor play, no fingerprint, no PIN, no SIM.
Locus Free apk install and external gesture proximity app name DTSO.
There is not shown any display activation at turns because operating Locus Free !

https://youtu.be/NM59pgl3ZAU  Goto 48 sec for the first wave display OFF action.

Samsung S10.
I do read some phones have a very unsensitiv sensor, and the S10 sensor is one such a troublemaker. :-((
https://help.locusmap.eu/topic/display-activation-samsung-galaxy-s10#comment-85870
https://help.locusmap.eu/topic/gesture-screen-control-not-working

[IS]

OK fine...problem hopefully solved by these complex settings.

Well I must admit that I was a bit surprised by the nature of the original question and especially by the reference to the Komoot app and others.

Locus Pro (if allowed) IS Device Administrator.
So I assumed that Locus Pro users always use the practical Gesture control for manual display control. For a cyclist with gear mounted on the handlebars by a single wave, and for walking by a double wave. No PIN, even if set to display always on. I recently even had a small discussion about this subject with the Locus team to simplify the entire display setting, so I better keep quiet now ;-)

But first here another hidden treasure and secret by changing the config.cfg file setting.

By a (single) gesture wave set the display continuously ON (gesture wave action ON than has the highest priority). This until by a subsequent (single) wave you set the display back to OFF. The standard ON/OFF sequence is than continued, so steered by the navigation instructions and the auto display off time out setting.

Interesting mode, as when you are approaching complicated street patterns, you can leave the map activ for a while. When the difficult part is over then you just go back to normal by a next (single) Gesture Wave. Very usefull imo.

It concerns a setting in the config.cfg.  Change default setting 0 to 1.
With the current Locus version config.cfg you will find the item on line 204.

# Disable "Turn off if idle" when screen was turn on by gesture (default: false)
turn_on_screen_by_gesture_disable_auto_screen_off = 1

Close Locus then edit the config.cfg (notepad ++). Then restart Locus and ready.

See attachment.  Display on/off feature in Locus Pro 
https://docs.locusmap.eu/doku.php?id=manual:user_guide:settings:control#screen_on_off_control
See auto screen turn off. (Set to 0)

Auto screen turn-off
setting of the interval before turning the screen off again
is set in 5 second steps from 0 to 120 seconds. 0 = screen turning off is disabled (until the system (Android) turns the screen off)

I agree Henk with that warning. Also the one I do use as is shown in the demo video, does have a magnetic closure. (And I suppose most such flip cases do have).  I know also "GusGF" does not use a flip case 

[display OFF]

Did you test all these scenarios while navigating with LM?

Did you ?

General rule: "The app that turns the display OFF must turn the display ON".

Locus Pro Panel: "Display (de)activate" SET @ navigation.

- @ navigation display OFF by auto screen turn-off function in that panel. (You have set)
- Than display ON should be triggered only by function (gesture) in that same Panel.

If you do not like, you should not use display OFF function by the Locus panel.
Than only use the standard Android display time out.  Example 15 sec or 30 sec etc.
- Locus Panel: "Display (de)activate" > Auto screen turn-off: SET: 0.
- Locus Panel: "Always Screen On": SET: OFF

Display OFF by the Android time out > Fingerprint will reliably open Display without entering PIN @ navigation.

By the way. A function NOT offered by Locus.  Nice to have for (walking) users with a flip case ?
I do not need...so I do not suggest in New Idea. See a video how it could look like.
https://youtu.be/odWv_dptYUI

[OFF]

*Fingerprint Unlock Tests. What I found.

A. Display OFF by Android only. (Screen Sleep time out or by short push power button )

Komoot Android screen time out > Display OFF > Fingerprint unlock > Display ON (complete unlock)
Locus Android screen time out > Display OFF > Fingerprint unlock > Display ON (complete unlock)

B. Display OFF by a Locus map Pro action. (Locus Device Administrator /Locus Map as service )

(Settings > Controlling > Display > Screen ON/OFF control)

When Locus map Pro triggers a Display OFF,  than Fingerprint unlock asks PIN.

By the actual Locus map Pro version.

1. Display OFF > Push Power button > Display ON. (Partial unlock, Locus map, no keyboard)
2. Display OFF > Proximity Wave Unlock > Display ON. (Partial unlock, Locus map, no keyboard)
3. Display OFF > Fingerprint Unlock > Phone asks PIN > Tap Return Button > Display ON. (Partial unlock, Locus map, no keyboard)
4. Display OFF > Fingerprint Unlock > Phone asks PIN > Enter PIN > Display ON > (Complete unlock, keyboard activ)

Enter PIN if you need other Android app, e.g the keyboard app.

Wie wird man sie los?
- Exportieren Sie Ihre Route in eine einfache gpx-Datei und importieren Sie dann diese exportierte gpx-Datei wieder, um sie als Navigation track_route zu verwenden.
- Da gpx unbekannte Icons nicht unterstützt, werden diese durch das Standard-Icon ersetzt.