This object is in archive! 
Record interrupt (Huawei P8)
Solved
Every call sports break the record of the track. Telephone Huawey P8 Android 6.0
Every call sports break the record of the track. Telephone Huawey P8 Android 6.0
Hi,
could you please specify what you mean by "EVERY CALL SPORTS"? How is the recording broken? Interrupted or stopped? Or does the line look like it lost GPS signal (it doesn't contour roads you went along but is straight from one point to another). Do you have latest version of Locus?
Hi,
could you please specify what you mean by "EVERY CALL SPORTS"? How is the recording broken? Interrupted or stopped? Or does the line look like it lost GPS signal (it doesn't contour roads you went along but is straight from one point to another). Do you have latest version of Locus?
sorry. I use google translate and to me it seemed strange that term sports.
The problem is that every call, pauses the locus recording. Then it does not restart automatically. Each time the recording is interrupted.
sorry. I use google translate and to me it seemed strange that term sports.
The problem is that every call, pauses the locus recording. Then it does not restart automatically. Each time the recording is interrupted.
Hi, that't very strange as the processes maintaining track recording and phone call are absolutely independent. However, maybe there is some specific feature of your phone system that may influence it. Try to set Locus as service (menu >settings > miscellaneous > check Locus Map as service.
Hi, that't very strange as the processes maintaining track recording and phone call are absolutely independent. However, maybe there is some specific feature of your phone system that may influence it. Try to set Locus as service (menu >settings > miscellaneous > check Locus Map as service.
OK. Done. I have also authorized a priority display in the Information menu applications (android), notifications. I will tell you.
OK. Done. I have also authorized a priority display in the Information menu applications (android), notifications. I will tell you.
have a look also at your Android settings of battery optimization. Locus is put into background when there is a GSM call and Android 6 often kills background processes unless they are excluded from the battery optimization.
have a look also at your Android settings of battery optimization. Locus is put into background when there is a GSM call and Android 6 often kills background processes unless they are excluded from the battery optimization.
the problem persists. I noticed that happens if I visualize the path during registration, as well as with phone calls.
I set locus is not part of the energy savings. then restarts itself after a few minutes but the hole remains in the track.
I also installed the latest update of 30 June.
the problem persists. I noticed that happens if I visualize the path during registration, as well as with phone calls.
I set locus is not part of the energy savings. then restarts itself after a few minutes but the hole remains in the track.
I also installed the latest update of 30 June.
try this instruction from a similar topic: http://help.locusmap.eu/topic/locus-going-to-pause-during-track-recording#comment-29775
try this instruction from a similar topic: http://help.locusmap.eu/topic/locus-going-to-pause-during-track-recording#comment-29775
Thankyou. I have read. It should not be my problem. I had already ruled locus by saving energy. Now headlight other attempts.
Thankyou. I have read. It should not be my problem. I had already ruled locus by saving energy. Now headlight other attempts.
OK, then follow instructions how to make an error log from your phone and send it to us: http://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting. We have to see what in particular is going on in your phone as we are not able to simulate your problem.
OK, then follow instructions how to make an error log from your phone and send it to us: http://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting. We have to see what in particular is going on in your phone as we are not able to simulate your problem.
hi,
no more reactions here for one month, we hope your problem was solved.
hi,
no more reactions here for one month, we hope your problem was solved.
ho avuto un infortunio. Riprenderò ad usare Locus tra 15 giorni, forse. e ti saprò dire.
I HAD AN ACCIDENT. I HAVE RESUMED YET TO MAKE SPORT AND TO USE LOCUS. I SAY ASAP. STILL ABOUT 15 DAYS.
ho avuto un infortunio. Riprenderò ad usare Locus tra 15 giorni, forse. e ti saprò dire.
I HAD AN ACCIDENT. I HAVE RESUMED YET TO MAKE SPORT AND TO USE LOCUS. I SAY ASAP. STILL ABOUT 15 DAYS.
ciao. oggi ho fatto un giro di prova. La registrazione si è interrotta, ed è rimasta in pausa quando ha perso il segnale GPS all'interno del secondo edificio (dopo il primo edificio era ripartita). Versione 3.18.9
Hello. Today I did a test run. The recording is stopped, and remained paused when he lost the GPS signal inside the second building (after the first building was divided). version 3.18.9
Il 10/08/2016 07:40, Locus Map ha scritto:
ciao. oggi ho fatto un giro di prova. La registrazione si è interrotta, ed è rimasta in pausa quando ha perso il segnale GPS all'interno del secondo edificio (dopo il primo edificio era ripartita). Versione 3.18.9
Hello. Today I did a test run. The recording is stopped, and remained paused when he lost the GPS signal inside the second building (after the first building was divided). version 3.18.9
Il 10/08/2016 07:40, Locus Map ha scritto:
Hi,
follow these instructions and if they do not work, follow instructions how to make an error log from your phone and send it to us:http://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting. We have to see what in particular is going on in your phone as we are not able to simulate your problem.
Hi,
follow these instructions and if they do not work, follow instructions how to make an error log from your phone and send it to us:http://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting. We have to see what in particular is going on in your phone as we are not able to simulate your problem.
La gestione della batteria è standard - non risparmio energetico. Vi manderei anche il log, ma non c'è nessun errore. Il problema è che in registrazione di percorso il programma si mette in pausa e non registra più - è successo ricevendo telefonate oppure perdendo il segnale GPS - ma non da errore o crash. Solamente rimane in pausa. Succede con mappa Italia
The battery management is standard - not energy saving. There also would send the log, but there is no error. The problem is that in journey record the program will pause and no longer records - has happened getting phone calls or losing the GPS signal - but not by mistake or crash.
Only it remains paused.
Il 31/08/2016 16:45, Locus Map ha scritto:
La gestione della batteria è standard - non risparmio energetico. Vi manderei anche il log, ma non c'è nessun errore. Il problema è che in registrazione di percorso il programma si mette in pausa e non registra più - è successo ricevendo telefonate oppure perdendo il segnale GPS - ma non da errore o crash. Solamente rimane in pausa. Succede con mappa Italia
The battery management is standard - not energy saving. There also would send the log, but there is no error. The problem is that in journey record the program will pause and no longer records - has happened getting phone calls or losing the GPS signal - but not by mistake or crash.
Only it remains paused.
Il 31/08/2016 16:45, Locus Map ha scritto:
Please follow the instructions how to make an error log from your phone and send it to us: http://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting
Please follow the instructions how to make an error log from your phone and send it to us: http://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting
vedi allegati
Il 01/09/2016 11:50, Locus Map ha scritto:
vedi allegati
Il 01/09/2016 11:50, Locus Map ha scritto:
scusa. ho mandato il lo error a te invece che ad asamm. Devo mandarlo a loro??
sorry. I sent the error to you rather than to asamm. I have to send it to them ??
Il 01/09/2016 11:50, Locus Map ha scritto:
scusa. ho mandato il lo error a te invece che ad asamm. Devo mandarlo a loro??
sorry. I sent the error to you rather than to asamm. I have to send it to them ??
Il 01/09/2016 11:50, Locus Map ha scritto:
hi, no, I've informed the developer, he'll have a look at it
hi, no, I've informed the developer, he'll have a look at it
Good day tegas,
unfortunately in log is only one information about Locus right at start of log (line 17000) which say something about closing Locus Map due o crash, but no crash is in few lines before.
There is an important information - after some activity in device, you re-open Locus to check progress of recording and recording is paused. Because Locus do not perform any "automatic pause" of recording, this means only single thing - Locus Map was terminated. Question here is WHY.
Battery optimizations or doze mode or similar tasks has no effect on this. Terminating of application may be done because of few possible reasons:
- system do not have enough memory so it terminate some applications. This happen on older devices or in case, user use higher number of "memory hungry" applications, like facebook etc.
- user use any application that do this optimizations on it's own, like Grenify or any "Free my RAM" applications
So my question here is, aren't you using Grenify or similar application that may cause this?
Good day tegas,
unfortunately in log is only one information about Locus right at start of log (line 17000) which say something about closing Locus Map due o crash, but no crash is in few lines before.
There is an important information - after some activity in device, you re-open Locus to check progress of recording and recording is paused. Because Locus do not perform any "automatic pause" of recording, this means only single thing - Locus Map was terminated. Question here is WHY.
Battery optimizations or doze mode or similar tasks has no effect on this. Terminating of application may be done because of few possible reasons:
- system do not have enough memory so it terminate some applications. This happen on older devices or in case, user use higher number of "memory hungry" applications, like facebook etc.
- user use any application that do this optimizations on it's own, like Grenify or any "Free my RAM" applications
So my question here is, aren't you using Grenify or similar application that may cause this?
io uso quasi esclusivamente il telefono in wi.fi - all'interno di casa o albergo - in esterno non uso nessun programma in connessione, tranne locus (no facebook, no whatspapp, no spotify or grenify, niente di niente) il programnma si è messo in pausa da solo, senza estrarlo dallo zaino, al momento della perdita gsp, o in altre occasioni per rivevimento di chiamata vocale. Ho 3 gb liberi su 8
I use almost exclusively the phone wi.fi - in house or hotel - in the outside does not use any program in connection except locus (no facebook, no whatspapp, no spotify or grenify, no nothing). has the programnma paused alone, without removing it from the bag, at the time of gsp loss, or other opportunities to rivevimento voice call.
3 gb free in 8 tot.
Il 02/09/2016 09:25, Locus Map ha scritto:
io uso quasi esclusivamente il telefono in wi.fi - all'interno di casa o albergo - in esterno non uso nessun programma in connessione, tranne locus (no facebook, no whatspapp, no spotify or grenify, niente di niente) il programnma si è messo in pausa da solo, senza estrarlo dallo zaino, al momento della perdita gsp, o in altre occasioni per rivevimento di chiamata vocale. Ho 3 gb liberi su 8
I use almost exclusively the phone wi.fi - in house or hotel - in the outside does not use any program in connection except locus (no facebook, no whatspapp, no spotify or grenify, no nothing). has the programnma paused alone, without removing it from the bag, at the time of gsp loss, or other opportunities to rivevimento voice call.
3 gb free in 8 tot.
Il 02/09/2016 09:25, Locus Map ha scritto:
Hello tegas,
understand, thank You.
Then I have to unfortunately suggest to find different application as I do not have any solution for You for now. I'm just leaving on 14 days out of office and after arrive, plan is to purchase Huawei device with same version of Android and MIUI ROM for testing. There is quite more people with same issue. It all may anyway take more then month/two.
Thanks for understanding.
Hello tegas,
understand, thank You.
Then I have to unfortunately suggest to find different application as I do not have any solution for You for now. I'm just leaving on 14 days out of office and after arrive, plan is to purchase Huawei device with same version of Android and MIUI ROM for testing. There is quite more people with same issue. It all may anyway take more then month/two.
Thanks for understanding.
ho fatto una escursione in bici con due telefoni. Il mio attuale P8 huawei e un asus fonepad7. Effettivamente su ASUS la traccia risulta senza interruzioni, mentre su P8 ci sono. Quindi è un problema HUAWEI o GPS Huawei o di interazione con Android 6 EMUI4. Vedi se serve una patch o qualcos'altro
I did a bike tour with two phones . My current P8 Huawei and Asus fonepad7 . Actually on ASUS track it is uninterrupted while on P8 there are . So it's a problem Huawei HUAWEI or GPS or interaction with Android 6 EMUI4 . See if you need a patch or something else. Thank you
ho fatto una escursione in bici con due telefoni. Il mio attuale P8 huawei e un asus fonepad7. Effettivamente su ASUS la traccia risulta senza interruzioni, mentre su P8 ci sono. Quindi è un problema HUAWEI o GPS Huawei o di interazione con Android 6 EMUI4. Vedi se serve una patch o qualcos'altro
I did a bike tour with two phones . My current P8 Huawei and Asus fonepad7 . Actually on ASUS track it is uninterrupted while on P8 there are . So it's a problem Huawei HUAWEI or GPS or interaction with Android 6 EMUI4 . See if you need a patch or something else. Thank you
Good day Tegas,
I'm playing second day with Huawei device and have same problems like your describe. After an hour, Huawei ROM completely kill Locus with error
Which say that Huawei decided that Locus consume too much power during last hour and best is to kill it completely. Perfect.
I'll keep you informed when I find some workaround. Quite complicated task as I after every change have to wait one hour to see how this Huawei device will react ... crazy.
Good day Tegas,
I'm playing second day with Huawei device and have same problems like your describe. After an hour, Huawei ROM completely kill Locus with error
Which say that Huawei decided that Locus consume too much power during last hour and best is to kill it completely. Perfect.
I'll keep you informed when I find some workaround. Quite complicated task as I after every change have to wait one hour to see how this Huawei device will react ... crazy.
Just marking the issue as solved.
In the end, the issue was directly in Huawei ROM modifications and was solved in one of the next system updates.
Just marking the issue as solved.
In the end, the issue was directly in Huawei ROM modifications and was solved in one of the next system updates.
Replies have been locked on this page!