Locus interupts Track recording with display off.

Roman Brziak shared this problem 1 year ago
Solved

Locus is closing during Track recording with display off.

Locus is running as service is ON = Settings -> Miscellaneous -> Locus as service.

Locus is "protecteed" application.

Phone Honor6, H06-L12, ROM EMUI 3.1, Android 5.1.1

Comments (101)

photo
1

Good day Roman,


please check if this manual helps you: http://docs.locusmap.eu/doku.php?id=manual:faq:gps_lost_fix_android6

photo
1

Hello.

Thanks for fast response. I change power saving mode, and also checked in Locus to confirm logout on back button to avoid unwanted logout. Seems working, I will test again.

photo
1

Perfect, glad to hear it!

photo
1

Hello again. Unfortunatelly, problem not solved. From change of Power Saving mode, from 10 recordings Locus stopped 4 times. It's a lot, and unknown random. Never at beginning of recordings, all 4 times on longer trails (2-3 hrs). Last time I tried to switch to flight mode, eliminate possible interaction with calls / SMS, but Locus switched off again.

Are there any predefined actions for hard buttons (volume, power)?

I am using camera on mobile during trails to take fotos from time to time.

I am wondering if this cann't interfere Locus function.

photo
1

Good day Roman,


quite complicate task. Are you sure there isn't any "hidden" settings in your device that may have power to disable GPS when screen is turned off?


What about Locus, are you using "GPS auto-off" function? Also what you see when you turn on the screen ... Locus start from scratch, like when you tap on launcher icon (so you see loading dialog) or Locus just sit as you leave it, just GPS is turned off? Anything suspicious may be useful.

photo
1

Hello. What I know is that putting application into "protected" should keep system from shutting down when display off. And Locus is there.


GPS is set:

Disable when hidden is ON

Track recording is ON

Guidance is ON

But I will switch Disable when hidden OFF


When recording is interupted, Locus is starting from scratch. Also, icons on uper left corner, Locus as Service, Position from GPS and Recording are lost. So it seems Locus is somehow shut-down by system?

photo
1

Good day Roman,

sorry for a late answer. We are currently discuss some other troubles with Honor devices here http://help.locusmap.eu/topic/locus-going-to-pause-during-track-recording , maybe it is somehow connected (even if mentioned topic is more about lost GPS connection).


Unfortunately such problems in last months are mainly made by some "improvements" and optimizations in devices. Locus is do it's best to keep alive at all costs, but these settings are usually more powerful :). So if Locus is killed after some time, there usually exists any settings in you device, that should define to Locus higher priority.

photo
1

Hello.

Finaly found settings that can help for Honor / Huawei owners with EMUI 4.0

Settings / Apps / Advanced / Ignore Batery Otimization.

On top, change from Allowed to All apps. Find Locus Map, switch to Allowed.

photo
1

These are answers I like :). Thank you very much for sharing these information. Michal (already responded in second topic) will for sure included this into our manual.

photo
1

Hello.

I thought I solved problem by tis setup, but settings not working - as nothing I did in last 4 months.

That's why I decided to go back to old ROM. Currently I am on android 4.4.2, missing some system functions, just to make Locus run properly. It took me 2 days to rollback and reinstall all.

And first real recording on bike ends just as before, what a dissapointment.

My setup:

Miscelaneous

"Confirm on exit" - ON

"Locus map as service" - ON

GPS and Location

Position acquired - ON

Position Lost - ON

Disable when hidden - OFF

Track Recording - ON

Guidance - ON

ROM setup

POWER PLAN Smart (switching to Normal right now)

Keep Running after screen off - Locus ON

In list of Background power-intensive applications, Locus is with note "Prevent system sleep"

Obviously, not so successfully.

How Locus stop / crash:

Normally, when Locus on and tracking, 3 icons on notification bar

- Location set by GPS, Recording, Locus as service

Stop / crash means all 3 icons are gone, when starting Locus, it loads like new start, Recording is Paused, and message "There is unfinished recording" appears.

I can see where it finished, and when I put Record button again, it track is discontinuous.

If you need more info, I will provide.

I can provide track recording to you, I can send any possible log Locus is generating, I am willing to help to solve the issue.

Are you able to get any Honor / Huauwei phone to test?

photo
1

Thank you Roman for copy your post here, it will be better.


And to your problem ... what you wrote change situation a lot. Fact that Locus Map is completely terminated by your system say, that issue is not in any battery optimization (confirmed by downgrade to 4.x version of Android where no such feature existed), but problem has to be some really aggressive application in your device that take care of freeing RAM memory and terminating un-needed (which this app consider as not-anymore-needed) application . Aren't you using any battery optimization tool?

photo
1

Hello. Thanks for fast response.

No, I do not use any additional batery optimization - I know it's not good for Android performace, since it can forcefully shut down apps which than can consume more batery during next startups.

Today, 3 hrs of walking, and Locus was fine.

Isn't it possible that different profile = different frequency GPS readings can be an issue?

And more info, when I was testing yesterday in walking mode for 7 hrs, icon of Locus run as Service was some times lost, but symbol of recording kept. I can send printscreen if needed.

Strange.

photo
1

Roman, I have absolutely no idea ...


Seems I'm working in parallel on four topics that have all same problem ... terminated Locus on Huawei devices, like this new one: http://help.locusmap.eu/topic/record-interrupt#comment-32175


Only Huawei cause troubles ... seems I'll have to purchase one soon to have something to test.

photo
1

It might have nothing to do with Huawei... I also have Locus randomly and quietly die while recording tracks (Galaxy Note 4 with 5.1.1 and also 6.0.1). This happens on one out of ten days on average... more or less since a year or so. Older versions of Locus were rock solid in this regard. Obviously... back then we also had older kernels...


Anyway... is it not possible that Locus simply crashes due to a bug and disappears? Maybe it has nothing to do with the kernel terminating you forcefully at all.


Silent crashes are super-annoying, because the user will not notice anything until he looks at his phone... which could be hours when it's tucked away in a backpack. Unfortunately, Locus still does not offer positive audio feedback during track recording :-(.


As it stands now, I really don't feel very safe with Locus when I know I absolutely rely on track recording. Like when you climb up a glacier in perfect sunshine but might have to track back when visibility goes to null. Your life can depend on a properly recorded track then. I find myself pulling out my phone way too often in these situations, just to make sure Locus is still running.


Positive audio feedback for track recording really is THE ONLY WAY to fix this "turning your users into nervous wrecks" problem. Couldnt you play a configurable sound whenever a point is successfully written to the database? Locus has sound support at dozens of other places, but the possibly dangerous "track recording lost" situation is not covered.


This would also help testers in figuring out when exactly Locus dies and thus might help finding a reason. As it stands now, Locus is simply gone and people only notice much later... without any clue on what was going on an hour ago.

photo
1

Understand. There should nothing like "silent crash". When application crash based on own issue, there always should be dialog with "Locus Map has died" text after you turn your devices screen on.


If you have rooted device, it is possible to start recording of logs by logcat application together with start of track recording of Locus. With rooted device, in this log should be real reason why Locus has died.

Possitive feedback ... there is already existing idea with this request, right?

photo
1

Hello.


I do not want to be too optimistic, too little testing so far.

But, after change of POWER PLAN from Smart to Normal last 3 trackings were OK (60 km, 20 km, 30 km). All other settings as described before.

Honor 6, EMUI 3.0 (B317), Android 4.4.2, Locus 3.18.9

I am rooted, so if there will be any crash, I'll start to log.

photo
1

So Locus did it again :-( On Android 4.4.2, Locus 3.18.9

Silent crash and "unginished tracking" message after restart.


Did you test on some Huawei mobile?

I am going to test older version you give me link to - if I will find download.

If not, can you upload again? I'll let you konow.

photo
photo
1

Hello Menion

I have Honor 6 since december 2014 I think. Problems appears later, until october 2016 tracking was fine.

Some 35 recordings on bike only, not mentioning skialp and trips were OK.


Originally phone came with EMUI 3.0, that's why I recently rolled back ROM.

As you know, this is not 100% solution.

Only think came to my mind is Locus instalation.

After rollback to EMUI 3.0, I installed via Google Play, but than I overwrited Lucus folder on memory from backup and restore data via Titanium Backup. I did it to keep downloaded offline maps.


I can test complete clean instal, but I prefer to test older versions of Locus.

Some from beginning of 2015.

Where to download?

Now I am on 3.18.9

photo
1

Oki,

try this version from middle of March 2015 : https://nas.asamm.com:443/share.cgi?ssid=0tmWBYI

photo
1

Hello


Now I am on 3.7.1 version. How to restrict update via Google Play?

I'd like to keep this version - at least for a while.

Saturday, 30+ km hiking, and Locus again crashed.

Sunday, 90+ bike, Locus OK - so it's not always, but it's really unpredictable...


Did you test Locus on Huawei / Honor phone yourself?

photo
1

Hello Roman,

open playstore on your device

my apps/open Locus/click top right 3-dot button/uncheck autoupdate

done

Wolfgang

photo
1

thanks balloni. Roman, I wanted to write you here immediately after new version will be published. I had to purchase Huawei device with latest EMUI rom. And indeed ... this new rom completely terminate Locus after an hour with information "Locus eats too much battery, terminating...". I've anyway found one change that seems to helped. You will see in next version.

photo
1

Hi. Thanks for that info, good news.

Please include info about device and EMUI / Android version you tested.

photo
1

Crazy Huawei. More I play with it and test, more I feel, this problem has no solution.

Anyway suggest to try latest Locus Map 3.19.0 and you will see. If it won't work, I see in EMUI 4.1 these options that I'm also trying to test:


  • settings > Apps > Advanced > Ignore optimisations > All apps > disable optimisations for Locus Map
  • settings > Apps > Locus Map > Battery > System wakeup (has anyone idea what this do?)
  • settings > Apps > Locus Map > Battery > Keep running after screen off
  • settings > Advanced settings > Battery manager > Power plan > Performance
  • settings > Advanced settings > Battery manager > Protected apps > make Locus Map protected

Uff ... seems that Huawei (Google) tries to make our life (mainly life of developers) really easier ... :/

Btw. I was able with all these settings, keep recording for a whole day with disabled screen and device in backpack during trip. Device on table is after hour moved to new "Doze" mode and there is nothing, Locus Map may do with it.

photo
1

Hello.


Quite bad news...

As I wrote above, with OLD EMUI 3.0 (Android 4.4.2), and OLD version of Locus (3.7.1) it was the same two weeks ago: 30+ km hiking Locus silent crash, next day 90+ on bike no problem.

So, it's random, unpredictable.


From comments here, it's not limited on Huawei and EMUI only - Note 4 user has similar experience.

Maybe I am going to try Locus on OLD Galaxy2 mobile...

Not a problem with licence, if I will have instalation on 2 Android devices?

photo
1

Hmm then in Android 4.x won't be probably any change with new version.


I can't imagine, why now it should make any difference, when nothing in core system that take care about recording changed.


Anyway feel free to try it everywhere you wants, there is no limit on number of devices that may use Locus under same account.

photo
photo
1

I think the positive feedback suggestion was made around five years ago. Not sure it survived the numerous site / forum incarnations though.

I checked the syslog a few times when Locus was gone but never found anything useful. I normally don't notice quickly though... hours might have passed. And then I am usually too mad at Locus for not recording my track to do serious debugging :).

photo
1

It happened again just now btw... Locus was simply gone quietly and I lost the last 30 minutes... too bad for OSM... it was a really nice trail.

photo
1

I looked into syslogs a few times btw... but never found anything useful. Normally... when that happens and I lose my track recording, I am too mad at Locus to do some serious debugging :)

The audible feedback suggestion was there like five years ago... not sure it survived the multiple support forum changes though.

photo
1

Do you have rooted device? If so, please install app called CatLog from google play and start recording of logcat together with recording of track in Locus. With this we may get full log with problem no matter when it happen. Thanks

photo
photo
1

Me and a friend were both track logging a longer trip together with Locus, both on a Note 4 with latest pro. I had "mysterious disappearings" on 3 out of 5 days (5.1.1) while he had none (6.0). Not sure if thats just a coincidence... but it seems to me that Marshmallow actually improves things.

photo
1

I also encountered this problem. Android 4.4.2 HUMMER H1 +

photo
1

I kind of solved this problem by using MemoryLocker

photo
1

Hello Oleg,

interesting application. May you write us later when you will have more experiences with this application? If this really helps, it should be quite useful tool for many Locus Map users. Thanks!

photo
1

Well, when will be able to use Locus few hours - will write

photo
1

Yesterday recorded the track in the off-screen time: 3 hours, today, too, recorded a track length of 3 hours. Not one error

photo
1

Thank you Oleg, appreciate it.


Thanks to this information, I was able to find out some curious news about this problematic. So in next Locus Map version will be implemented one "hack" that should prevent Locus from being killed as well. Hope it will help as well.

photo
1

It reveals a "bug". Phone is in the mute screen, writes track. The satellites are visible. Then I hear the signal, which is configured to include GPS. I turn on the screen and saw before the program starts to download again, now it will not boot, but hanging a window with a proposal to stop, pause and continue the track record. I press a hard button cancel - all working on. I'm not programmed android, only Windows. I assume that your program gets the termination signal and gives the user a dialogue stops recording a track. Here it needs to be somehow not show if the program in the background. If you need to clarify something - write, send all that is necessary. Sorry for my English

photo
1

still closes the application. Through SSHDroid I see that after a GPS signal has changed connectivity PID of the process and the start time coincides with the time signal. Subjectively, this happens less often than without a locker

photo
1

What a stupid system it's going to be, when even such hacks are not able to keep application running. It's really more then stupid ...

photo
photo
1

Catch the same problem on ALCATEL one touch with Adroid 4.2.2. Really strange because it doesn't have any "optimization" settings. At autumn all was ok and there is no new firmware.

photo
1

Ah sorry for previous post, wrong topic.


Tim, I'm sorry about troubles, but I really do not have any better solution how to keep Locus alive ... at least not known to me, solution.

photo
2

Same here with Android 4.2. (I reported this already to not proper url, in czech language.)

Menion, are you really sure the problem comes from system and is not inside Locus? (yes, from my next text it looks like system is the orgigin - systems power off.) It is very time consuming to make tests of thing which 2 hours works and then fails three times in 10 minutes, but I want to do it, because for me Locus is No.1 (for OSM mapping) and I want have it working. I will test it on reinstalled system without nothing new.

In fact my system is very clean now too. Problem occurs when installed in basic memory (without SD card), same when installed on SD card. In new installation I have only(!) turned the settings "Show addresses" off, and the problem appeared. With setting "Show addesses" back to on - disappeared. I made this 4-times there and back and I was pretty sure that this is rule and I have found it. But next day the problem appeared with "on" setting too :(

When I leave Locus with the power button, then GPS works or stop work maybe immediately (of course I cannot see the state with display off).

If it works: it will continue work always and if I turn my device on 2 hours later, I will have perfect trace.

If it doesn't work, GPS turns on when I turn device on, and Locus (of course) connect the last point to current position with a direct line. Trace is total unusable. It is always from beginning (time of turning the device off), never from somewhere between.

(I can come one day to Vysočany and go few hours arround houses near to your company, if you want to see it and work on it a little.)

Thanks, Mirek

photo
1

Good day Mirek,

I'm absolutely not! sure. I'm not a 100% grandmaster developer and I can imagine that in Locus is something wrong. On second side, Locus Map is quite big app, but except rare cases, I always use official suggested methods.


I'm really sorry to hear, that Locus starts to cause troubles on 4.x devices. Unfortunately all my testing devices are already updated to 5.1+, so it's hard for me to test it. Even if so, this will be heavily dependent on device + Android so not applicable to all 4.x devices.


Anyway, do you have your device rooted? If so, we may do here one useful test by recording log with application called CatLog. In this log may be some system information that may say why was GPS stopped.

Also, when you turn on device and GPS is off, is map visible immediately or is Locus starting like when you tap on Locus icon for the first time (so you should see loading dialog in most cases and whole start takes a while)? I'm asking because it may signalize if Locus Map was completely closed by system or just GPS was disabled.

photo
1

Yes, Mirek described problem very precisely.

When I turn device on Locus starting as first time (initializing maps and so on) - so it was completely closed.

I'm sure it's problem of new versions , in october all works just fine.

photo
1

I rutovanny phone with 4.4.2 and I can try to start a debug version. And it looks like the entire application crashes, because the device is disconnected from the tracks and the recording screen. I am connected to the phone via SSH and see the PID of the process. Then I hear a signal that the connected GPS. Look for "ps" - is another process with another PID and start time corresponds to signal the resumption of GPS. Moreover, raising the priority does not work apparently. Apologies for the English translate with Google

photo
1

@Tim: really interesting. In latest version was only one single change that was affecting if Locus map will be enabled as long as possible. Anyway it cause some unwanted visible toast notification so it will be disabled in new version (coming probably today). Anyway I can't imagine that this may have some side effect like completely termination of app ... you will see.


@Oleg: hmm and is possible to get from you a log few minutes before and after you notice that application is completely terminated? In log should be visible some information why this happen ( usually ....) .

photo
1

I'm just starting to learn android and linux too, not specialist. Tell me how to get the right log, I will try to send it

photo
1

I had rooted the device earlier. Now I have reinstalled to the factory version and device is not rooted, but I can root it, no problem (but I don't know much about this).

I can again return to completely factory installation or make everything you want with the phone (root it..), because Locus is for me priority.

Version is 4.2.1.


I have other problem. Probably this is something completly different, but I write it here to be sure that some "reset" procedure doesn't run somewhere where it makes bad job:

If I assign offline map (maps from osm.paws.cz), turn the device power off, then

- if I go back in few seconds, there is no problem, I see the offline map

- if I go back in few minutes, Locus is switched back to the default online map

photo
1

>> menion: is map visible immediately or is Locus starting like...

I cannot answer this at now. At this time, after PowerOff/PowerOn: map is visible immediately. GPS is running when recording is active, and Locus(?) writes the messages (GPS off, GPS on) when recording is paused.

Locus settings are all defaults. But I don't know if the problem occurs now or not. I can answer this better tommorow.

photo
1

Switching map to online (got the same) is just another side of closing app in background. So I got earlier version here (http://help.locusmap.eu/topic/locus-pro-switches-back-to-online-map) and will test it this evening. I will recommend other 4.x users do the same and report here.

photo
1

Same problem and same phone here as Tim's (Alcatel POP C1 One Touch).

photo
photo
1

Have tested a little version 3.18.9. Problem seemed to dissapear. Will test more.

photo
2

Here:

3.18.9 - works excellent.

3.19.0 - doesn't work; both problems: turn the GPS off, offline map is not saved.Tim, can you confirm this?


If it is really so, then it is a little strange story. However much more important is that it will be good news for Locus team and for us: things can be found and fixed.

Btw (3.19-3.21): Isn't the problem with the map saving? I have seen some different behaviour between my todays versions (21, 19, 18.9) when I have selected the offline map, so maybe authors made some changes there? What if the user chooses in 19-21 the external offline map and saves it by completely leaving Locus while GPS is inactive? Will the map+GPS fail in the next use of Locus?

But I don't know if I will prefer tomorrow to downgrade from 18.9 to 21 to test it....

photo
1

PS: I haven't removed Locus folders while moving from version to version.

photo
photo
1

Resume: for me latest "stable" version is 3.18.9. It is quite enough for me and I will not update app without solution of this case.

photo
1

I may have found a solution to our problem. First of all, I have the problem not only flew when the track, but just when the GPS. So I started the program, joined SSH and run command "free". I found that less than 4 MB of available memory of the 485 MB. Then I removed all unnecessary programs, and to the maximum stop various unnecessary services (weather, phone, e-mail etc). As a result, telephone spent more than 30 hours, the program never crashes recorded almost completely in the background on first track 20 hours, the second for 8 hours. Free memory was within 30-60 MB.

It seems so works Low Memory Killer. It has config what if less 20 MB of memory to kill the processes "aggressive." Therefore, whether the information can not combo box where the name of the map, coordinates etc to add information about free memory and remaining battery?

photo
1

@Tim: I see no problem with using older version, glad you found a solution. Maybe it should be similar problem to what wrote Oleg below ..


@Oleg: nice observation, thanks. I usually take care mainly about CPU/battery usage. Used memory (RAM) , was not my priority because most modern devices has a lot of memory. Battery is usually problem ...


Display remaining memory in top panel won't solve it. I'll rather invest little time and try to find problematic places that may consume extra memory, thanks for push! Meanwhile avoid map overlays, wms maps and try to limit number of visible objects on the map at once ...

photo
1

Yes, I try to unload almost every app and stop every unnecessary service but problem remain. I think that from 3.19 the memory usage became above same limit that can affect memory killer behavoir. So it may be solved by bying new phone :о) More important that I can use Locus again without problem, I really like it.

photo
photo
1

This is not about your program, memory can take very different program. Just the memory indicator in the program could signal to users that the memory is small, the program can be killed. A manual can write that if the memory on the device is less than 500 MB, you may encounter a similar situation. And offer to remove the program and stop the service. And your program at the track record and vector map isplzovat 50-70 MB. I think this is normal

photo
1

Ah I thought that Locus Map consumed almost everything from 485 MB, sorry.


This is anyway really crazy ... displaying "Free memory" value in top panel with hope, user notice this and close some other programs or use any 3rd party program for this .. it's something only usable for tiny part of Locus users, but aggressive memory killers is something that affect most of users. As I wrote, I'll try to find some problems with memory in Locus and optimize it little bit ...

photo
1

If described in the manual for which this information is, for example, to make a special note: for users with 500 MB of memory. A memory indicator do red if it has less than 20 MB.

A memory optimization thing is always useful, but in this case the memory of "eat" other programs and even the optimized Locus still does not get it. Still it will not work until the user releases sufficient memory

photo
1

Understand.


And isn't in this case better use some application that may deal with it directly, like : https://play.google.com/store/apps/details?id=mem.usage&hl=en ? Such kind of apps is anyway something I usually really can't recommend ... as they in most cases cause more troubles then usage.

photo
1

Well, I will compare that shows the program and the command "free"

photo
photo
1

More in thread: http://help.locusmap.eu/topic/locus-pro-switches-back-to-online-map

In my opinion:


3.18.9 + testing version from the thread above (Menion, ~11 Jan): excellent

3.19-3.21: fatal broken (with Power Off: GPS often turns off, Offline map changes to some/default online map)

photo
1

>> Oleg: No idea if I will have some (additional) problems with low memory in the future. But at this time my phone has enough memory and is near the factory orginal state, and of course no additional memory killer/managery is present (just Locus was installed). Still I have fatal problems in 3.19-21 versions.

photo
1

Unfortunately, in original condition and only android Google Apps eat just 350 MB, Locus - 60 MB. Therefore, if you run something else, or it runs itself, is already a memory and does not remain.

In short, I found this recipe is the solution to your problem.

photo
1

>> Oleg: Maybe I don't understand you well. I use now the testing version from Menion which, I think, is very similar in memory management/requirements to 3.21. 3.21 has the problem, testing version hasn't.

From previous I think the reason of correct behaviour is not more of free memory, but Menions change in the testing version (Menion knows exactly what he has changed).

Maybe you are correct that in 3.19-3.21 the problem is caused with low memory (in such case only few Locus users would come across this problem). I have no motivation to install 3.19-3.21 back. But what I can do with current testing version is: I will install some additional Android stuff to see if with very low memory the testing version remains stable or if it will have some problems.

photo
1

>> Menion

I made more testing and 3.21.1-BETA fails for me too (sometimes).

It looks like Locus is completly restarted:

- track recording window comes up,

- version info notice comes up,

- initialization notice comes up,

- gps on notice comes up

This happens only sometimes, usually often or always during ~10 minutes. Then again ~10 minutes works well. Sometimes (once in 30 minutes?) the offline map goes away. It is really difficult to find any logic in this behaviour. So maybe low memory...


I have now 3.18 only, because this is last stable version.

But I am ready to test again, if you decide to go step by step during separate commits between 3.18 and 3.19.

photo
1

I see the difference here, but I am not sure with it (maybe I make some mistake again?):


Track recording on, then close Locus, then run it again:


In 3.18 the track recording will automatically CONTINUE.

In newer versions (3.21.1-BETA) track recording IS PAUSED.

photo
1

Hello Mirek,

sorry for a late response.


Difference if Locus Map start recording in paused mode or in recording mode is based on time since last correctly stored location. If this time is less then 10 minutes, recording continue immediately, otherwise it is paused.


About problems with crash/terminating. In latest Beta version you test, it was already reverted to code from 3.18 version. At least part that affect GPS connection. I'll have to switch back to my older Sony Z1C device with Android 5 and used this device for a while. Sorry, I have no new good news for You (and others) for now ...

photo
1

My info was about CLOSED and RE-OPENED application.

Not about running application.

If 3.18 will CONTINUE track recording after its restart, then the trace will be correct.

If 3.21.1-BETA IS PAUSED after restart, then the trace hangs.

(That is for case that Android forces some "accidental" restart or something similar to restart of Locus....?)

photo
photo
1

>> switch from offline to online map


Why not save the changed configuration immediately after user chooses the new map ??

photo
1

I should, it is not a problem, anyway it is not a solution to real problem that happen here.

photo
photo
1

>>3.19.0 - doesn't work; both problems: turn the GPS off, offline map is not saved.Tim, can you confirm this?

3.22.2 - The same both problems. Meizu MX6.

photo
1

Fresh news - I flash my 512Mb Alcatel OT C3 to unofficial software (Android 4.4.4 , to get it work with bluetooth LE pulsometer). Side effect was that now latest Locus work quite stable! I think that is because in unofficial software many unneeded (for me) system progs was deleted.

photo
1

Update to my situation.


After changing phone to OnePlus 3T, no problems with Locus anymore.

Different ROMs (stock only), Android 6, Android 7.0 and now Android 7.1.1.

I can start tracking in Locus and forget about it, after 6 hrs everyting running well.

So I guess in my case root cause was EMUI ROM from Huawei and their agressive battery saving.

photo
1

Hmm, my OnePlus 3t sometimes stops tracking if I exit Locus and have the screen off, even though I don't have power optimization on for it. It's probably because it's not the active app though.

photo
1

So it works great for you now. As the 3.18 version :)

photo
photo
1

I may only confirm that Huawei optimization is hell, which Locus Map is still not able to conquer. Good you have a working solution!

photo
1

Hi Urs, I had the same problem upon updating to android 7. It reset the battery optimisation for all apps and I had to select it again.

Do you see a warning near the bottom when starting track recording (see screenshot)? Have you tried turning off battery optimisation directly within android settings?

I hope this was helpful ...

photo
1

Thank you for your advice. I didn't notice the hint in the track recording dialog. But it seems that the forced standby mode is switched off for all apps (see print screen) So, I will try out with the GPS Locker App, although this is not very user-friendly, since I have use one more app simultanously.

photo
photo
2

Hi,


maybe this info helps you too.


c.s.g.

photo
1

Thank you, I'll try out the GPS Locker, see comment above.

photo
1

3.23.2: again tracking interruptions with locus stops running. Starting shows init information. Oneplus 3.

photo
1

Hello. So problem is back. I am on 3.23.2 and same problem. Seems I was too optimistic about Locus.

OnePlus 3T is my second phone with this issue.

photo
1

Last functional version of Locus, 3.18, is here: https://gitlab.com/zvolsky/locus318 (use the Download button).

I have the PRO version only so you should pay to the Locus authors.

If I will get a FREE version (e-mail: zvolsky@seznam.cz), I will replace or add it.

photo
1

Thanks Mirek, I'll give it a try to use the older version, because with the recent nothing helped. Not memory locker, not locus as a service, not change standby setting to 30 min.

photo
1

Problem persists with 3.18, though less frequently. And the "over query limit" issue is back with 3.18. Hm, not good.

photo
1

What a pity. (I think you are sure that the version was not auto-upgraded. Because earlier (before I have found the possibility turn off the update in Google Play) the version usually has upgraded very fast.)


So, for me 3.18 really helps. But this is on 4.2 Android. Maybe the benefit is for 4.2 only, maybe for some hardware only.

photo
1

I'm really surprised that old version helps on this problem. In latest two/three months, I had reverted some code from 3.18.x version to latest versions with hope, it should help here. So technically, there should be no difference (between old and latest versions) when we speak about "work with GPS".


I really really suggest to check all possible method of device optimizations ( we try to collect them here ). For now, I have unfortunately no better solution how to keep Locus Map & GPS connection more robust, I'm sorry.

photo
1

Hi, Menion. Yes few months earlier you made the testing version with renewed code from 3.18, but behaviour was same as with the 3.19-3.21, ie. bad for me. My Android 4.2 was almost clean (after factory reset).

So I cannot believe you have found the proper code change which between 3.18->3.19 has introduced the problems (for me). Or .. there must be something else. Changed compiler,..?

Or it can be specific splitting of memory in my phone. However 3.18 works after factory reset and after few apps has been installed, too.

photo
1

Yes, this is of course possible. Since 3.18, there were huge number of changes in Android compiler, system for code protection, Android support libraries etc. These are anyway changes, that are almost impossible to investigate.

Hmm it's not the first issue that happen last months only on 4.x devices. It looks for me that with new Android versions ( that from my point of view does not bring any useful features ), support for 4.x version is more and more complicated, sad.


Anyway weird is that by Rudiger tests, even older version does not help here.


I'm really sorry guys, for now, I have no working solution. What about other apps, did you tried some other applications for track recording? And what about some apps like GPS Keeper, did anyone tried it? Not sure, but worth a try.

photo
photo
1

Same Problem with OnePlus 3 Android 7.1.1.

Tried memory locker - no effect. Switched back to locus 3.18 as desribed here http://help.locusmap.eu/topic/locus-interupts-track-recording-with-display-off

Problem persists though less frequently.

Now back to Locus 3.23.2. I´ll give "GPS Locker" a try and will report.

photo
1

Tried GPS keeper and GPS locker today, no success. Still interruptions.

Locus being stopped and has to be manually started anew. Message

"incomplete track...." as usual. Locus 3.18, OnePlus 3 Android 7.1.1.

All Locus GPS auto-off settings are inactive.

When starting

tracking, locus recognizes system battery optimizations as mentioned by jimmyfromthepieshop. The

"deactivate" button leads to android settings. Battery saving is already

off though. See attached screenshots.

photo
1

Now, with newest Oneplus OTA Update (OxygenOS 4.1.6), problem is gone. They mentioned "battery optimizations" here: https://forums.oneplus.net/threads/oxygenos-4-1-6-7-1-1-ota-for-oneplus-3-and-3t.547283/

photo
photo
1

Same problem to me, recording stops after few minutes. But is worst now, I reset to default setting and now I cant see shadows.

photo
1

I changed some battery settings, it had some application restrictions when display is locked, now is all ok. It seems to work well. I didnt tried longer than one day.

photo
photo
1

Hi all, as this topic is the same as this http://help.locusmap.eu/topic/locus-interupts-track-recording-with-display-off, I',m merging them.

photo
1

I am on long 28 days hiking trip, now making 22 day.

Using Locus from the first day.

Locus has no issues when moving.

It ends almost 100% during stops.

We make break, take pictures, drink water / eat. In open space, so GPS should be still available.

During that breaks, Locus is gone.

When walking, no issues, no interruptions.

During these days, Locus breaks several times each day.

Only once there was message from Android about app with high battery consumption.

So it shows, that the problem is not Android, but Locus itself, purely managing tracking and loving position when not moving?

photo
1

Not sure about this. Crashes were erratically.

Now, with newest Oneplus OTA Update (OxygenOS 4.1.6), problem is gone. They changed some battery settings.

photo