This object is in archive!
Locus Map crashing while recording
Closed
So, I had this issue for a couple of months now, and it is really frustrating.
While I'm recording a ride, the app crashes seemingly for no reason. Sometimes, it happens after 10 minutes, sometimes after hours. I did not manage to find out any reasons for this problem, it is completely unpredictable. When I open the app again, the recording continues.
Does the app produce any crash logs that can be investigated, I'd really like to find the solution for this.
Or do you have any idea why this could happen?
The same problem 
Hi,
this behavior is most probably caused by your device battery optimization. Exclude Locus from it or turn it off. Various manufacturers have various methods, not all of them are included in the "battery optimization" settings section, they can be scattered over whole settings including security etc. All our knowledge on this problematics is summarized here: http://docs.locusmap.eu/doku.php?id=manual:faq:gps_lost_fix_android6. Plus two steps in Locus settings you can try but we are not certain they'll help in your case:
- go to Locus settings > GPS& Sensors > Google Services assisted location > ON
- go to Locus settings > Miscellaneous > Run Locus Map as service > ON
Hi,
this behavior is most probably caused by your device battery optimization. Exclude Locus from it or turn it off. Various manufacturers have various methods, not all of them are included in the "battery optimization" settings section, they can be scattered over whole settings including security etc. All our knowledge on this problematics is summarized here: http://docs.locusmap.eu/doku.php?id=manual:faq:gps_lost_fix_android6. Plus two steps in Locus settings you can try but we are not certain they'll help in your case:
- go to Locus settings > GPS& Sensors > Google Services assisted location > ON
- go to Locus settings > Miscellaneous > Run Locus Map as service > ON
Hi,
I already did all those things right when I started using Locus Map. Battery optimization is off and app is excluded from power monitoring. I also use Locus Map as a service and use the google services assisted location.
So the reason for the app crashing must be something different.
What I noticed: It seems to only happen when the screen is on, so maybe there is a rendering issue that causes the app to crash?
Hi,
I already did all those things right when I started using Locus Map. Battery optimization is off and app is excluded from power monitoring. I also use Locus Map as a service and use the google services assisted location.
So the reason for the app crashing must be something different.
What I noticed: It seems to only happen when the screen is on, so maybe there is a rendering issue that causes the app to crash?
If the app crashes when the screen is on, it is probably not caused by the battery optimization. Please make a log report and send it to us. Instructions: http://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting
If the app crashes when the screen is on, it is probably not caused by the battery optimization. Please make a log report and send it to us. Instructions: http://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting
I have sent you the report as requested. Please let me know if you find out what's causing the crash :)
I have sent you the report as requested. Please let me know if you find out what's causing the crash :)
Hi Marcel,
thanks for the log report. Unfortunately, it detects only an absolutely anonymous Locus crash in system libraries - i.e. no evident causes, reasons, triggers... Do you have Free or Pro version? I'll send an older Locus version for test.
Hi Marcel,
thanks for the log report. Unfortunately, it detects only an absolutely anonymous Locus crash in system libraries - i.e. no evident causes, reasons, triggers... Do you have Free or Pro version? I'll send an older Locus version for test.
Hi again,
download Locus Map Pro 3.29.2 from here: https://asamm.myqnapcloud.com/share.cgi?ssid=0bc9MmM and let us know if it crashes too. The link is valid for 7 days.
Hi again,
download Locus Map Pro 3.29.2 from here: https://asamm.myqnapcloud.com/share.cgi?ssid=0bc9MmM and let us know if it crashes too. The link is valid for 7 days.
I have the pro version, with offline locus maps, and use the dashboard to display some data during the ride as well. I downloaded the version from the link, and I will test it during my next ride.
I have the pro version, with offline locus maps, and use the dashboard to display some data during the ride as well. I downloaded the version from the link, and I will test it during my next ride.
Sounds like the crashes I reported months ago. Problen still not solved.
Which device and OS Version you are using?
Sounds like the crashes I reported months ago. Problen still not solved.
Which device and OS Version you are using?
identical assignment is with me !!! (Android 8).
Before version 3.34 it was ok!
identical assignment is with me !!! (Android 8).
Before version 3.34 it was ok!
Specific Version I don't know but it was introduced during summer. I noticed it around Sept/Oct. Earlier in the year Jun/Jul I used Locus a lot without any problems.
Android 8, too.
Specific Version I don't know but it was introduced during summer. I noticed it around Sept/Oct. Earlier in the year Jun/Jul I used Locus a lot without any problems.
Android 8, too.
Hi guys,
Marcel already send us a log, but unfortunately, there was nothing useful for us.
May anyone from you create a bug-report once more with latest Locus Map 3.35.1 version (as Michal wrote here)? Thanks
Hi guys,
Marcel already send us a log, but unfortunately, there was nothing useful for us.
May anyone from you create a bug-report once more with latest Locus Map 3.35.1 version (as Michal wrote here)? Thanks
I had no time to test the older version yet, but I did a 3 hour ride with the latest version (3.35.1) yesterday, and there was no crash.
Only difference to the previous ride was that I used a heart rate monitor, and the speed in the dashboard was from my ant+ speed sensor instead of gps speed.
So my guess would be an uncatched exception when calculating and displaying gps speed in the dashboard. Possibly when the device shortly loses gps and returns NaN m/s as a speed value, and the program tries to convert it to km/h and crashes?
I had no time to test the older version yet, but I did a 3 hour ride with the latest version (3.35.1) yesterday, and there was no crash.
Only difference to the previous ride was that I used a heart rate monitor, and the speed in the dashboard was from my ant+ speed sensor instead of gps speed.
So my guess would be an uncatched exception when calculating and displaying gps speed in the dashboard. Possibly when the device shortly loses gps and returns NaN m/s as a speed value, and the program tries to convert it to km/h and crashes?
Until now, I have appreciated Locus for its stability during work (recording + navigation was operating without complaints even up to 150 km of the route), until the appearance of version 3.34.
The situation is the same as Marcel's K.
I have Android 8 and any settings in the system that protect Locus from killing the process, have full access and without monitoring battery consumption.
From version 3.34, Locus crashes (closing) (!?) When recording a route, it is informed by the lack of messages from the Locus navigation. I restart Locus and the recording starts automatically, but it is in pause mode.
But it is not everything…
While working in Locus, for example modifying and planning a route, the application can close. Although recently I had to kill the Locus process because I made a black screen and the program was completely suspended.
By the way - when modifying the route, after it is saved, the message is correct, and then it turns out that nothing has been changed !? It happens, however, that the modifications are saved with a very long delay (even a few minutes). Refreshing works terribly.
I change the data in the description of the route, and in the preview in the folder you can still see old data.
You are constantly adding new applications to the application, and it just starts to fail. For me, the assurance that Locus's work is very stable and that is the priority is what counts.
I hope that I will not lose confidence in this wonderful application.
Until now, I have appreciated Locus for its stability during work (recording + navigation was operating without complaints even up to 150 km of the route), until the appearance of version 3.34.
The situation is the same as Marcel's K.
I have Android 8 and any settings in the system that protect Locus from killing the process, have full access and without monitoring battery consumption.
From version 3.34, Locus crashes (closing) (!?) When recording a route, it is informed by the lack of messages from the Locus navigation. I restart Locus and the recording starts automatically, but it is in pause mode.
But it is not everything…
While working in Locus, for example modifying and planning a route, the application can close. Although recently I had to kill the Locus process because I made a black screen and the program was completely suspended.
By the way - when modifying the route, after it is saved, the message is correct, and then it turns out that nothing has been changed !? It happens, however, that the modifications are saved with a very long delay (even a few minutes). Refreshing works terribly.
I change the data in the description of the route, and in the preview in the folder you can still see old data.
You are constantly adding new applications to the application, and it just starts to fail. For me, the assurance that Locus's work is very stable and that is the priority is what counts.
I hope that I will not lose confidence in this wonderful application.
I send two log files month ago for my crashes and got the following response:
"... I see few problems all in "native Android core". This not-technically means a huge (for now unsolvable) problem for us.
I'll look on logs, but if it will really be this kind of problem and older version worked, I see only solution in downgrade to older app version."
Do you believe this motivates to send more?
Even if it crashes in Android core it should be in your interest to find a solution or at least find a workaround.
I'm a experienced Software developer too. Sometimes it's hard to find the root cause and takes a lot of time but "use the old version" isn't the right way.
Anyway now it's winter. Not the right time to use the App often and long.
I think there will be more crash reports at summer time but then all the changesets where the problem starts will be forgotten.
Don't get me wrong. Locus is a wonderfull app. Great work!
I just think it's time to pause new features and look into this problems.
I hope you are able to run a special test mode where you simulate navigation/recording and so on.
Because of winter your customers are not in a good position to help.
At least me.
I send two log files month ago for my crashes and got the following response:
"... I see few problems all in "native Android core". This not-technically means a huge (for now unsolvable) problem for us.
I'll look on logs, but if it will really be this kind of problem and older version worked, I see only solution in downgrade to older app version."
Do you believe this motivates to send more?
Even if it crashes in Android core it should be in your interest to find a solution or at least find a workaround.
I'm a experienced Software developer too. Sometimes it's hard to find the root cause and takes a lot of time but "use the old version" isn't the right way.
Anyway now it's winter. Not the right time to use the App often and long.
I think there will be more crash reports at summer time but then all the changesets where the problem starts will be forgotten.
Don't get me wrong. Locus is a wonderfull app. Great work!
I just think it's time to pause new features and look into this problems.
I hope you are able to run a special test mode where you simulate navigation/recording and so on.
Because of winter your customers are not in a good position to help.
At least me.
Anyone here still experiencing below mentioned issues with new Locus Map versions?
Anyone here still experiencing below mentioned issues with new Locus Map versions?
Good day guys,
sorry to say it, but I do not have any working solution for these random crashes for now.
- we will update core libraries that may have an effect here, during March (most probably), so you may try March/April version of Locus Map
- we also uploaded an older version of the app here on Google Drive, so feel free to use an older version if app worker correctly for you before.
Sorry for complication!
Good day guys,
sorry to say it, but I do not have any working solution for these random crashes for now.
- we will update core libraries that may have an effect here, during March (most probably), so you may try March/April version of Locus Map
- we also uploaded an older version of the app here on Google Drive, so feel free to use an older version if app worker correctly for you before.
Sorry for complication!
Replies have been locked on this page!