Messages

@ Ulrich Kiermayr:
I assume that this is intentional or perhaps unavoidable. Due to the perspective, the map elements would have to be displayed smaller and smaller/closer together on the horizon (theoretically infinitely), which would no longer be possible to render meaningfully.

I don't think so. Given the visible street names in the blank area, there is no (in) visible horizon. It is just a little tilt where there is still only ground visible. Moreover, a horizon would be a straight line (not a 90°corner)

To me it looks like there are just three tiles missing on top.

Greetings, uk

Speaking of tilt: for me, the map is incomplete, when tilted.

You cannot view this attachment.

LG uk

[@Žajdlík Josef]

@Žajdlík Josef
Hmm, I see no problem here. Both maps version 2024+? No other vector Czech or Slovak map in the device? Auto-loading for vector maps in the settings enabled?

Today I noticed the same between Austrian and Hungarian offline maps. No automatic loading.

Greetings, Ulrich

Hi there!

I'm out in the woods right now on a hike and figured out that the "keep the position" get lost as soon as I zoom in or out. Can someone confirm this, please? Thanks.

4.32.0.7

I think, it is because you have "hold map center" turned off (no lock on the center symbol. Can you confirm this?


You cannot view this attachment.

Greetings, Ulrich

I'll probably have to update this screen to the new system we use for UI. I consider this a minor problem. Will try to look at it, but can't promise a quick solution for now. Thanks for understanding.

I also consider it a minor problem. I just wanted to note it for completeness, so that you are aware of the issue. 👍

greetings, Ulrich

Hi,

There are 2 more "hidden underneath the  Android home Bar" issues in the preset editor:

1. Editor itself
You cannot view this attachment.

2. The sub editor, where the visible items are selected
You cannot view this attachment.

Greetings, Ulrich

One more thing: since the Map content button is not working:

Is there any other way to turn on/off or configure the LoPoint highlighting?

Greetings

version 4.32.0.6 published. Sorry for the previous .5 version. Minor issue on A11-.

Just for completeness: Map items Issue also present in 4.32.0.6

Greetings, Ulrich

05 version on Android 10 - Instant ctd and it doesn't even write a log. In lack of the 04 installer I cannot use it now.

Android 16 - no FC for me 🤷

lG Ulrich

Hi @Menion. 4.32.0.5 fixes all Dashboard crashes.
But there is a new odd issue: The Map items button does not open the map Items sidebar, but now the NTRIP Manager.

You cannot view this attachment.

You cannot view this attachment.

Lg Ulrich

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 👍🙂