Messages

Not crashing even with Dashboard on. Android 10

Thanks, so the Android version could in deed be a contributing factor. 🤔👍

LG uk

Crash on navigation would indeed be serious. Cannot confirm after a quick check though. I started navigation, then turned off screen for some seconds and then back on. Manually.

So I did some testing: crash only happens when a dashboard is Active. It does not matter what is in the dashboard - even a completely empty one triggers the crash. If I disable the dashboard, crash is gone.

Can someone confirm this?

Greetings, Ulrich

This workaround is only valid for guidance mode. Navigation always crashes, regardless of the dashboard (or anything else navigation draws on the screen).

Maybe also related to the Android version (S23, Android 16).

Greetings, Ulrich

Crash on navigation would indeed be serious. Cannot confirm after a quick check though. I started navigation, then turned off screen for some seconds and then back on. Manually.

So I did some testing: crash only happens when a dashboard is Active. It does not matter what is in the dashboard - even a completely empty one triggers the crash. If I disable the dashboard, crash is gone.

Can someone confirm this?

Greetings, Ulrich

Crash on navigation would indeed be serious. Cannot confirm after a quick check though. I started navigation, then turned off screen for some seconds and then back on. Manually.

I did a quick check and the issue seems to be related to my dashboard. Have to do some more checking

LG uk

[1. app crash in navigation]

Merry Christmas from me as well:

I hit a serious bug in 4.32.0.4

1. app crash in navigation
When in navigation or guidance when the screen goes off, the app crashes/closes/disappears.
This is regardless of the settings of screen control or run as a service. (Problem is: this makes this version quite unusable).

I checked the log and it seems, the app dies, when the screen goes back on. This is the error message:

Code Select Expand

16:57:03.820 E a uncaughtException(Thread[main,5,main])
java.lang.RuntimeException: Unable to resume activity {menion.android.locus/com.asamm.locus.basic.features.mainActivity.MainActivityMap}: java.lang.RuntimeException: All children of ConstraintLayout must have ids to use ConstraintSet
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:6269)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:6342)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:73)
at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:63)
at android.app.servertransaction.TransactionExecutor.executeLifecycleItem(TransactionExecutor.java:169)
at android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:101)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:80)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:3150)
at android.os.Handler.dispatchMessage(Handler.java:110)
at android.os.Looper.loopOnce(Looper.java:273)
at android.os.Looper.loop(Looper.java:363)
at android.app.ActivityThread.main(ActivityThread.java:10060)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)
Caused by: java.lang.RuntimeException: All children of ConstraintLayout must have ids to use ConstraintSet
at d5.n.e(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:45)
at bx.c.invoke(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:354)
at com.asamm.locus.basic.settings.dialogs.PrefDashboardSelection.q(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:108)
at mt.c.onResume(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:110)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1720)
at android.app.Activity.performResume(Activity.java:9691)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:6239)
... 14 more


2. Nav Bar draw over (inconvenient):
The nav Bar draws over the sensors manager, which makes the connect button of the last sensor (almost) unreachable.
(Fun fact: also the screenshot ends above the nav Bar, therefore i had to take a photo 😉)

You cannot view this attachment.

Greetings Ulrich
And as always, if I can help debugging, just tell me, what I should do 👍🙂

Hi,

There is still an issue with the top panel overlapping with other elements: in my case it is the top guidance or navigation panels overlapping with my dashboard (see screenshot). Before, the dashboards top right corner was *below* the top bar. Now the top right corner of the dashboard always is on the top right corner of the screen resulting in the overlap.

You cannot view this attachment.

Greetings, Ulrich

So, based on automatic reports (on the Crashlytics), I do not see any other problem with 4.31.5. I was also today without any issue, so it looks very stable, perfect!

No issues today for me as well (Bike tour)

As a temporary solution, when using Locus, in your phone settings under "Lock Screen - Secure Lock Options," try disabling the side key lock and setting a maximum auto-lock time. This will allow you to turn on the screen without any issues, while your phone's security settings will still work as before. If you're familiar with Tasker, you can automate this process.

Actually the feature works. Turning it on is just not persistent over a restart of the app.

You cannot view this attachment.

Did something change with the way Locus handles language settings in 4.31.3? After I installed that (from Google Play), Locus suddenly started up in German. I checked the settings immediately, but Locus was set to "System default" and my system was definitely set to "English (UK)". Don't even know why Locus would choose German, I'm living in German-speaking country but have everything set to English - only the mobile provider might be identifiable as German.

But it gets worse: So I set Locus manually to "English (UK)", which worked, but now my times are still shown with "AM/PM", although I definitely also have "24h clock" set in my system settings (am/pm is the work of the devil ). Unfortunately, that's something I can't explicitly override in Locus under "Language & Units".

Any idea?

I also noticed, that it started in German.

Hi,

There is a new issue in 4.31.3

The setting "Unlock the screen" is not persistent across program restarts. It always resets itself to off.

You cannot view this attachment.

Also in the Presets, this option can't be added to a preset despite being offered in the options.

You cannot view this attachment.

Greetings, Ulrich

Es geht weiter wie bisher, Fehler wurden beseitigt und neue eingebaut. Ich warte auf den Tag, wo mal eine Fehlerfreie Version erscheint.
Ich frage mich, wie die anderen das machen.
Keine meiner vielen Apps (154) ist so fehlerhaft.
Viele davon laufen einfach und das schon seit Jahren und ohne ständige Updates zur Fehlerbeseitigung.
Die Listen mit Nachbesserungen in den Versionshinweisen wären mir echt zu peinlich.

Nur aus Interesse: warum verwendest du LocusMap (noch immer), wenn du so unglücklich damit bist?

Es gäbe ja genug Alternativen.

LG uk

Sent from my SM-S918B using Tapatalk

Pre-release version for quick test if someone is interested.

Backup is (still) broken.
You cannot view this attachment.

Today I noticed something odd: In the warning list in route planner:

You cannot view this attachment.

The list only uses the upper third of the window, the lower part stays empty. This is also a bit confusing - it took me a while to realize, that the list has more than 3 items and is scrollable in the upper part.

You cannot view this attachment.

Greetings, Ulrich

[Version 4.30.1.8]

Version 4.30.1.8
  - fix: (SILVER) incorrect offset for top dashboard

Regarding the Dashboard.
@Menion: Any chance to implement this: https://help.locusmap.eu/topic/37768-more-dashboard-variables-for-next-via-point

I think/hope this is minor - but would make life on a biketour a lot more convinient.

lG uk - doing some intensive testing for the next 3 weeks on bike vacation.

[@Ulrich Kiermayr]

@Ulrich Kiermayr
track sync problem > it was a fresh, new, manually created route? Or some older, already synced here and there? Hard to simulate it right? Hmm.

@Menion In both cases it was an newly created track. I think(!) I shared the track (via link) before the cloud sync ran. (but not 100% sure though)

But I agree, its hard to simulate. The Post was more of a heads up, wether others also experience issues. I will observe it - and maybe figure out something reproducable. ;-)

Greetings, uk