This object is in archive!
Locus Map Classic is closed by Android
Closed
Hello,
my Locus Map Classic, version 3.64.1 is closed by Android about a second after starting.
A message from the system says the app has an error and has therefore been closed. The app should only be started again after the error has been rectified. I should contact the developer of the app.
Reinstalling the app did not fix the error.
kodela
PS:
After a second reinstallation, the app no longer closes.
The same problem 
The app no longer crashes immediately after opening since the second reinstallation. However, it keeps crashing when planning a route. After that it can be opened again. But the last steps are lost.
The app no longer crashes immediately after opening since the second reinstallation. However, it keeps crashing when planning a route. After that it can be opened again. But the last steps are lost.
Android error message
Android error message
The app no longer crashes immediately after opening since the second reinstallation. However, it keeps crashing when planning a route. After that it can be opened again. But the last steps are lost.
Android error message:
The app no longer crashes immediately after opening since the second reinstallation. However, it keeps crashing when planning a route. After that it can be opened again. But the last steps are lost.
Android error message:
Hallo,
Du musst Dich nicht entschuldigen, Fehler können immer passieren.
Ob ich ein Protokoll eines Absturzes übermitteln kann, weiß ich nicht.
Es waren bisher 22 Abstürze, 21 am 23.12.2022 und einer am 26.12.2022.
Die Tage dazwischen habe ich nicht mit Locus Map Classic gearbeitet.
Am 26.12.2022 habe ich langer mit LMC gearbeitet und hatte nur einen
Absturz. Heute hatte ich noch keinen Absturz.
Für die bisherigen Abstürze wird es vermutlich kein Debug-Protokoll
geben, oder doch?
Ich werde wie im Locus Map Manual unter "Devices with Android 4.2 and
higher" beschrieben vorgehen und versuchen einen Bug-Report für einen
künftigen Absturz zu bekommen und diesen übermitteln.
Konrad Demmel
Hello,
You don't have to apologize, mistakes can always happen.
I don't know if I can submit a log of a crash. There have been 22
crashes so far, 21 on 12/23/2022 and one on 12/26/2022. The days in
between I didn't work with Locus Map Classic.
On 12/26/2022 I worked with LMC for a long time and only had one crash.
I haven't had a crash today.
There probably won't be a debug log for the previous crashes, will there?
I will proceed as described in the Locus Map Manual under "Devices with
Android 4.2 and higher" and try to get and submit a bug report for a
future crash.
Konrad Demmel
Hallo,
Du musst Dich nicht entschuldigen, Fehler können immer passieren.
Ob ich ein Protokoll eines Absturzes übermitteln kann, weiß ich nicht.
Es waren bisher 22 Abstürze, 21 am 23.12.2022 und einer am 26.12.2022.
Die Tage dazwischen habe ich nicht mit Locus Map Classic gearbeitet.
Am 26.12.2022 habe ich langer mit LMC gearbeitet und hatte nur einen
Absturz. Heute hatte ich noch keinen Absturz.
Für die bisherigen Abstürze wird es vermutlich kein Debug-Protokoll
geben, oder doch?
Ich werde wie im Locus Map Manual unter "Devices with Android 4.2 and
higher" beschrieben vorgehen und versuchen einen Bug-Report für einen
künftigen Absturz zu bekommen und diesen übermitteln.
Konrad Demmel
Hello,
You don't have to apologize, mistakes can always happen.
I don't know if I can submit a log of a crash. There have been 22
crashes so far, 21 on 12/23/2022 and one on 12/26/2022. The days in
between I didn't work with Locus Map Classic.
On 12/26/2022 I worked with LMC for a long time and only had one crash.
I haven't had a crash today.
There probably won't be a debug log for the previous crashes, will there?
I will proceed as described in the Locus Map Manual under "Devices with
Android 4.2 and higher" and try to get and submit a bug report for a
future crash.
Konrad Demmel
Replies have been locked on this page!