Recently, I've been using Locus in the car (Gold version). When I navigate a pre-saved track, Locus crashes after approximately 2 to 2,5 hours.
This has happened consistently in the version of mid July 2024, to the latest version installed early August.
One moment, the app is showing the navigation screen, the other moment it is simply completely gone. No dialog, no warning, no report from Android, the app just closes. When re-opening the app, it is no longer in navigation mode, but just starts fresh.
I can then restart the navigation on the saved track and it then runs for about 2 to 2,5 hours again before the same crash happens.
Attached are two log files found in the "log" folder created by the latest version of Locus.
Unfortunately, I won't be able to test for a while as I do not have long drives planned.
The same problem 
Hi,
sorry for any inconvenience, we'll check the log and investigate possible issues (however, we can't simulate the problem mentioned in the SSL topic and nobody else has reported it). You can downgrade from our public repository at https://bit.ly/lmVersions.
Hi,
sorry for any inconvenience, we'll check the log and investigate possible issues (however, we can't simulate the problem mentioned in the SSL topic and nobody else has reported it). You can downgrade from our public repository at https://bit.ly/lmVersions.
Hi skvedo,
could you please record video of your crash? You can use AZ Recorder (https://play.google.com/store/apps/details?id=com.hecorat.screenrecorder.free). Thank you in advance.
Marek, Locus teram
Hi skvedo,
could you please record video of your crash? You can use AZ Recorder (https://play.google.com/store/apps/details?id=com.hecorat.screenrecorder.free). Thank you in advance.
Marek, Locus teram
I have added 2 more recordings to folder linked above.
I had Locus running in background and recording. It started crashing once I opened map and was moving around in it.
I have added 2 more recordings to folder linked above.
I had Locus running in background and recording. It started crashing once I opened map and was moving around in it.
Attached log from yesterday on 4.25
Still same issues. Worst thing is that it seems to work for like 2 hours and then started crashing every few minutes (I have the log from that day, but it is 200MB)
Last weekend I want for few days of bikepacking and had to use old phone for Locus (which is slow and clumsy.
When I tried to record the crashes, it seemed that recording affect it (repeatedly crashing in seconds vs holding for minutes after started recording).
My Gold subscription was just renewed but I can't fully enjoy it.
Attached log from yesterday on 4.25
Still same issues. Worst thing is that it seems to work for like 2 hours and then started crashing every few minutes (I have the log from that day, but it is 200MB)
Last weekend I want for few days of bikepacking and had to use old phone for Locus (which is slow and clumsy.
When I tried to record the crashes, it seemed that recording affect it (repeatedly crashing in seconds vs holding for minutes after started recording).
My Gold subscription was just renewed but I can't fully enjoy it.
Hi skvedo,
we are not able to simulate your problem. At least we can try to identify problem with beta version with advanced logging:
Thank you very much!
Hi skvedo,
we are not able to simulate your problem. At least we can try to identify problem with beta version with advanced logging:
Thank you very much!
I have the same. After navigating for about 2 hours, the app crashes. Always after two hours. Logs are attached. Both showing a nullpointer exception.
I have the same. After navigating for about 2 hours, the app crashes. Always after two hours. Logs are attached. Both showing a nullpointer exception.
So I have installed adb on my computer and collected some logs this way.
First crash file just opening Locus and it crashed right when I listed PID from 'ps'. Second crash after few seconds of panning with map on screen.
Logs obtained by running 'logcat -p <PID> > <file>'
This looks pretty severe to me.
--------- beginning of crash
08-14 06:32:48.157 30357 30523 F libc : Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xb4000072a1ffb790 in tid 30523 (Thread-44), pid 30357 (n.android.locus)
So I have installed adb on my computer and collected some logs this way.
First crash file just opening Locus and it crashed right when I listed PID from 'ps'. Second crash after few seconds of panning with map on screen.
Logs obtained by running 'logcat -p <PID> > <file>'
This looks pretty severe to me.
--------- beginning of crash
08-14 06:32:48.157 30357 30523 F libc : Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xb4000072a1ffb790 in tid 30523 (Thread-44), pid 30357 (n.android.locus)
This weekend, on 31-08-2024, I had a chance to try to reproduce the problem again and indeed, there were crashes.
In the morning, between 8:00 and 8:45, I was editing a track in the route planner. The attached log file shows that during the morning, there are several NullpointerExceptions, all pointing to Locus trying to get the length of a null array
I left home around 8:45 by car. I used the pre-computed track with navigation prompts and I set the phone to nagivation mode. The screen was set to stay on and centered with direction up (so the map is rotating).
The first crash happened around around 9:10. There's no exception in the log, but at 9:16:13 it just shows "new start". This is because I had to restart the app after it crashing during navigation. I took an interactive bug report in Android using the developer mode, which is available, but way too large to upload here.
I arrived at my destination around 11:00.
Then, around 11:30, I left again, but this time by bicycle. I put the phone in navigation mode again and again started to navigate a pre-defined track. This time, not in navigation mode, but in track-follow mode (only beeps, no voice prompts). Around 12:00 again the app crashed and I restarted it (can be seen as a "NEW START" in the log at 12:02. Just before 12:00, a ConcurrentModificationException is logged. I did not manage to do a full bugreport.
No crashes happened further on that day (in the car, so in navigation mode). It crashed again around 12:18, hence the new start at 12:21 in the log file. An Android bug report is available for that crash too.
Around 12:35, I stopped navigation as I was almost home, hence the new start at 12:37 was not due to a crash.
I have sent the links to the two large bugreports of Android via e-mail. They are 50 MB ZIP files.
This weekend, on 31-08-2024, I had a chance to try to reproduce the problem again and indeed, there were crashes.
In the morning, between 8:00 and 8:45, I was editing a track in the route planner. The attached log file shows that during the morning, there are several NullpointerExceptions, all pointing to Locus trying to get the length of a null array
I left home around 8:45 by car. I used the pre-computed track with navigation prompts and I set the phone to nagivation mode. The screen was set to stay on and centered with direction up (so the map is rotating).
The first crash happened around around 9:10. There's no exception in the log, but at 9:16:13 it just shows "new start". This is because I had to restart the app after it crashing during navigation. I took an interactive bug report in Android using the developer mode, which is available, but way too large to upload here.
I arrived at my destination around 11:00.
Then, around 11:30, I left again, but this time by bicycle. I put the phone in navigation mode again and again started to navigate a pre-defined track. This time, not in navigation mode, but in track-follow mode (only beeps, no voice prompts). Around 12:00 again the app crashed and I restarted it (can be seen as a "NEW START" in the log at 12:02. Just before 12:00, a ConcurrentModificationException is logged. I did not manage to do a full bugreport.
No crashes happened further on that day (in the car, so in navigation mode). It crashed again around 12:18, hence the new start at 12:21 in the log file. An Android bug report is available for that crash too.
Around 12:35, I stopped navigation as I was almost home, hence the new start at 12:37 was not due to a crash.
I have sent the links to the two large bugreports of Android via e-mail. They are 50 MB ZIP files.
Hi Britte,
please get Locus Map permission for all-time access to the location and exclude Locus from all means of battery optimization so that the app can run in the background, see http://docs.locusmap.eu/doku.php?id=manual:faq:gps_lost_fix_android6. Also, try switching Google Services assisted location off in Locus settings - GPS&sensors.
Hi Britte,
please get Locus Map permission for all-time access to the location and exclude Locus from all means of battery optimization so that the app can run in the background, see http://docs.locusmap.eu/doku.php?id=manual:faq:gps_lost_fix_android6. Also, try switching Google Services assisted location off in Locus settings - GPS&sensors.
When the app crashes, if it's possible please make a bugreport immediately and send the file here for analysis. Thanks.
When the app crashes, if it's possible please make a bugreport immediately and send the file here for analysis. Thanks.
Sounds like the exact same symptoms as https://help.locusmap.eu/topic/35283-locus-crashing
Also on a recent (fully updated) phone, since August.
I assume it's behaving the same as mine: the app just closes. No message from Android, Device Maintenance does not show any crashed apps and restarting Locus means you have to restart navigation too.
Sounds like the exact same symptoms as https://help.locusmap.eu/topic/35283-locus-crashing
Also on a recent (fully updated) phone, since August.
I assume it's behaving the same as mine: the app just closes. No message from Android, Device Maintenance does not show any crashed apps and restarting Locus means you have to restart navigation too.
Hi Britte,
we are very sorry but the crash is caused by a native Android library which is a part of the operating system. For now, we cannot eliminate this threat because it's impossible to simulate it and of course, we can't edit system code. As we are unable to fix this issue, I've refunded your Premium subscription.
Hi Britte,
we are very sorry but the crash is caused by a native Android library which is a part of the operating system. For now, we cannot eliminate this threat because it's impossible to simulate it and of course, we can't edit system code. As we are unable to fix this issue, I've refunded your Premium subscription.
I'll be on a trip this weekend with ample time to generate further logs. I'll setup the logging and provide you with them. I understand the bug is in a native library (if you let us know which, we may also be able to report or upvote the bug with Google), but who knows it can be avoided anyway.
I'll be on a trip this weekend with ample time to generate further logs. I'll setup the logging and provide you with them. I understand the bug is in a native library (if you let us know which, we may also be able to report or upvote the bug with Google), but who knows it can be avoided anyway.
https://help.locusmap.eu/topic/35897-app-suddenly-shuts-down seems closely related
https://help.locusmap.eu/topic/35897-app-suddenly-shuts-down seems closely related
I installed v4.23.1 over 3 weeks ago because of another topic and used it intensly. Not a single crash, neither in navigation nor panning nor editing of points & tracks.
β Something inside Locus must have been changed between 4.23.1 and 4.24.3 that causes the library bug to materialize in form of crashs. Analysis of these changes may allow to changes calls to that library in a way that current Locus 4 versions do not crash any more.
β Users affected by the crashes do not have to use Locus v3 in order to have a usable Locus, but only need to install Locus v4.23.1 (manual) and disable automatic updates β allowing to use most of the advantages of Locus v4 π
I installed v4.23.1 over 3 weeks ago because of another topic and used it intensly. Not a single crash, neither in navigation nor panning nor editing of points & tracks.
β Something inside Locus must have been changed between 4.23.1 and 4.24.3 that causes the library bug to materialize in form of crashs. Analysis of these changes may allow to changes calls to that library in a way that current Locus 4 versions do not crash any more.
β Users affected by the crashes do not have to use Locus v3 in order to have a usable Locus, but only need to install Locus v4.23.1 (manual) and disable automatic updates β allowing to use most of the advantages of Locus v4 π
I have to agree. I also have not seen the app crashing anymore since the last version. No need to install manually, just use the update from the playstore.
I have to agree. I also have not seen the app crashing anymore since the last version. No need to install manually, just use the update from the playstore.
I haven't used Locus much since October due to repeated cold illnesses (wasn't biking outside). So no comprehensive testing on my side.
After upgrade to Android 15 in October 2024 it seemed crashes were not frequent (at least not with Locus in foreground). I remember one. But that was when I switched to WhatsApp and podcast player. Maybe different issue killing Locus to free up resources.
In February 2025 everything on my phone started crashing including system UI (up to reentering PIN to sim card).
I had bite the bullet and made painful factory reset and new setup (as probably would be asked to if tried warranty). Phone UI stopped crashing but didn't tested Locus.
One app I have noticed crashes after this was Iris (visualization of trams in Brno, associated timelines..), always on map screen.
At April 5th I have participated in randonner ride and experienced frequent Locus crashes. They were sometimes little different. Locus on lock screen was stuck on black screen until I swiped to menu and reopened Locus. This was probably 50:50 behaviour to just crashing totaly to lock screen. No repeated crashes after app restart (within seconds) which I experienced before.
Later I noticed crashes happened when I selected guidance on route. It crashed in background within few minutes. For last 50 km I rode with just route displayed on map (no out of route notification, no ETA or distance left fields) without crash.Yesterday when starting Locus for a ride, I got new version notification. Changelog looked like it could be solving crashes during navigation. I tested and not single crash yesterday.
For now it seems promising to me.
After phone factory reset, reinstalling and clean setup of all apps I was prompted by Strava to allow some sort of mode where event if foreground UI will crash, background component should be able to record ride.
Can't find it in permissions list now.
I haven't used Locus much since October due to repeated cold illnesses (wasn't biking outside). So no comprehensive testing on my side.
After upgrade to Android 15 in October 2024 it seemed crashes were not frequent (at least not with Locus in foreground). I remember one. But that was when I switched to WhatsApp and podcast player. Maybe different issue killing Locus to free up resources.
In February 2025 everything on my phone started crashing including system UI (up to reentering PIN to sim card).
I had bite the bullet and made painful factory reset and new setup (as probably would be asked to if tried warranty). Phone UI stopped crashing but didn't tested Locus.
One app I have noticed crashes after this was Iris (visualization of trams in Brno, associated timelines..), always on map screen.
At April 5th I have participated in randonner ride and experienced frequent Locus crashes. They were sometimes little different. Locus on lock screen was stuck on black screen until I swiped to menu and reopened Locus. This was probably 50:50 behaviour to just crashing totaly to lock screen. No repeated crashes after app restart (within seconds) which I experienced before.
Later I noticed crashes happened when I selected guidance on route. It crashed in background within few minutes. For last 50 km I rode with just route displayed on map (no out of route notification, no ETA or distance left fields) without crash.Yesterday when starting Locus for a ride, I got new version notification. Changelog looked like it could be solving crashes during navigation. I tested and not single crash yesterday.
For now it seems promising to me.
After phone factory reset, reinstalling and clean setup of all apps I was prompted by Strava to allow some sort of mode where event if foreground UI will crash, background component should be able to record ride.
Can't find it in permissions list now.
I just came back from a 5000 km motorcycle trip using Locus on the phone for navigation of pre-made tracks. Every day, there would at least be one moment when the phone would stop responding, but it was never reproducible. The patterns was always the same though.
On the phone, I'm running Locus in the foreground (set to show the map with heading up) and in the background the BMW app is running when connected to the bike. This provides data to show the speed-limit on the bike's dash and it records the trip (including bike-parameters).
After riding for some time, the speed-limit would disappear from the dash and moments later, the phone-screen would freeze. No crash-dialog would appear, but it would simply stop responding. In that case, I had to stop, close Locus and wait. The phone then needs a few moments and after that I can restart Locus and restart navigation.
My IT-intuition says that there was, at those points, a problem with the memory on the phone and to my surprise, the release notes for version 4.30 talk about a major memory leak in the fixed in the coordinate transformation library. It would not surprise me if that was the problem I had, but I will be testing this again on a longer trip only in a month or so.
I just came back from a 5000 km motorcycle trip using Locus on the phone for navigation of pre-made tracks. Every day, there would at least be one moment when the phone would stop responding, but it was never reproducible. The patterns was always the same though.
On the phone, I'm running Locus in the foreground (set to show the map with heading up) and in the background the BMW app is running when connected to the bike. This provides data to show the speed-limit on the bike's dash and it records the trip (including bike-parameters).
After riding for some time, the speed-limit would disappear from the dash and moments later, the phone-screen would freeze. No crash-dialog would appear, but it would simply stop responding. In that case, I had to stop, close Locus and wait. The phone then needs a few moments and after that I can restart Locus and restart navigation.
My IT-intuition says that there was, at those points, a problem with the memory on the phone and to my surprise, the release notes for version 4.30 talk about a major memory leak in the fixed in the coordinate transformation library. It would not surprise me if that was the problem I had, but I will be testing this again on a longer trip only in a month or so.
Since Locus 4 v.4.25.1, the app keeps crashing, and the developer has been pushing ahead with features I personally have no interest in, without any real intention of resolving them. And now, backups aren't even working. They keep blaming others, saying it's the theme, the shadows, the maps. Now, even though they recognize that the app is the problem, they show no intention of improving it. How about going back to the basics and finding a fundamental solution?
Since Locus 4 v.4.25.1, the app keeps crashing, and the developer has been pushing ahead with features I personally have no interest in, without any real intention of resolving them. And now, backups aren't even working. They keep blaming others, saying it's the theme, the shadows, the maps. Now, even though they recognize that the app is the problem, they show no intention of improving it. How about going back to the basics and finding a fundamental solution?
Hi guys,
there were already some fixes for problems with the memory in May/June. Seems, there are still users that suffer from random app crashes when moving with the map.
I'm not 100% sure, that fix I made this week will solve exactly this problem. Problem with "Out of memory" crashes is, that the real reason is hard to find.
Anyway ... new version 4.31.2 just published. It awaits on confirmation from Google review team, but may be sideloaded from our public drive here. So give it please a try!! Thanks a lot.
Hi guys,
there were already some fixes for problems with the memory in May/June. Seems, there are still users that suffer from random app crashes when moving with the map.
I'm not 100% sure, that fix I made this week will solve exactly this problem. Problem with "Out of memory" crashes is, that the real reason is hard to find.
Anyway ... new version 4.31.2 just published. It awaits on confirmation from Google review team, but may be sideloaded from our public drive here. So give it please a try!! Thanks a lot.
Replies have been locked on this page!