Compass "Auto-change" freeze
Hello menion
following behavior appeared to me a few times since last big modification of "compass settings" with PRO
my setting for compass "Auto-change 3,6km/h"
So once again this morning on geocache tour it happened to me after ~ 1:30 of locus start respectively ~50minutes after track record start at ~7:30 UTC /9:30CEST
From this time map/compass rotation work only while walking fast, if i walk slow or stand still the map/compass stand fixed on last?? GPS moving info
For me it looks like that "Auto.change" didnt work and rotation info is frozen to sat info.
I can solve problem if i restart locus, so today the next hour locus worked as expected.
in zip you will find
-NMEA
-track.gpx
-2 screencasts with sound, i spoke what i´ve done
perhaps you can find any interesting info for solving this problem
The same problem 
Good day balloni,
thank you for very precise bug report.
Big surprise for me is, that even a compass screen does not work for you, because there should be always used sensor values ( not sure if already in latest Pro though ... ).
Unfortunately from your data, I'm unable to read any useful info. May you please try to simulate this issue with new "test version" here. I've enabled logging of sensor values into Locus/logs files so right after problem appear, there should be something useful I hope. Thank you!
Good day balloni,
thank you for very precise bug report.
Big surprise for me is, that even a compass screen does not work for you, because there should be always used sensor values ( not sure if already in latest Pro though ... ).
Unfortunately from your data, I'm unable to read any useful info. May you please try to simulate this issue with new "test version" here. I've enabled logging of sensor values into Locus/logs files so right after problem appear, there should be something useful I hope. Thank you!
Hi menion
thanks for apk, i´ll try to simulate this behavior
I've enabled logging of sensor values into Locus/logs files so right
after problem appear, there should be something useful I hope
to be sure, this log file will be written
- automaticly ?
- i have create a log ?
- i have to click top left to create this log ?
Big surprise for me is, that even a compass screen does not work for you, because there should be always used sensor values
if all works fine the magnetic compass is always used in compass screen even setting is set to "auto change" and i move fast.
Since now i thought this auto change influence map and compass screen, so i think an additional hint inside manual would be helpfull
http://docs.locusmap.eu/doku.php?id=manual:user_guide:settings:sensors&s[]=auto&s[]=change&s[]=compass
Hi menion
thanks for apk, i´ll try to simulate this behavior
I've enabled logging of sensor values into Locus/logs files so right
after problem appear, there should be something useful I hope
to be sure, this log file will be written
- automaticly ?
- i have create a log ?
- i have to click top left to create this log ?
Big surprise for me is, that even a compass screen does not work for you, because there should be always used sensor values
if all works fine the magnetic compass is always used in compass screen even setting is set to "auto change" and i move fast.
Since now i thought this auto change influence map and compass screen, so i think an additional hint inside manual would be helpfull
http://docs.locusmap.eu/doku.php?id=manual:user_guide:settings:sensors&s[]=auto&s[]=change&s[]=compass
Hello,
it is created automatically so no need to worry about it.
Sensor data (magnetic compass) are used always probably since month back, it is quite new. I'm still testing it but for me, it sound a lot more logical then previous behavior, when compass was also influenced by settings. Compass is compass and it should display real device orientation.
Hello,
it is created automatically so no need to worry about it.
Sensor data (magnetic compass) are used always probably since month back, it is quite new. I'm still testing it but for me, it sound a lot more logical then previous behavior, when compass was also influenced by settings. Compass is compass and it should display real device orientation.
Hello menion
Compass is compass and it should display real device orientation.
+1, completely agree
BTW: in this test version is the old behavior
now i´ve reproduced the problem again with this testversion
my steps:
- start test version
- i create a point and "guide on" to it
- reaching this point, create the next one and "guide on" to it
similar walking on a multicache from WPT to WPT
all works fine till i reach ~20 m to the 5. point (in this example)
it was ~17:18 CEST
If i remember right, the problem appeares for me in the past between the 4. to 6. "guide on" target
see attached logfile
Hello menion
Compass is compass and it should display real device orientation.
+1, completely agree
BTW: in this test version is the old behavior
now i´ve reproduced the problem again with this testversion
my steps:
- start test version
- i create a point and "guide on" to it
- reaching this point, create the next one and "guide on" to it
similar walking on a multicache from WPT to WPT
all works fine till i reach ~20 m to the 5. point (in this example)
it was ~17:18 CEST
If i remember right, the problem appeares for me in the past between the 4. to 6. "guide on" target
see attached logfile
Good evening balloni,
really interesting. It looks that in 17:17:17 , your accelerometer sensor stopped and no more data were send into Locus Map. From what I search, there are some troubles with older version of CyanogenMode rom. Are you using it and maybe you just updated it during last weeks?
From these Locus logs, I see only that data stopped coming into app, but not why this happen. Reason, some error message, should be visible in system log, which we don't have it here.
Hmm I may try to fix it by some automatic restart of sensors in case, they stop like in this case. Anyway it's really weird that it started so suddenly for you. I rewrote part of code that compute final orientation anyway your device still use older magnetic sensor + accelerometer to compute orientation and here was no big change.
EDIT: reconnection to sensors created. When there will be more then 5 seconds pause in one of two required sensors, Locus Map will try to disconnect and connect both sensors again. We will see if it will be enough.
Good evening balloni,
really interesting. It looks that in 17:17:17 , your accelerometer sensor stopped and no more data were send into Locus Map. From what I search, there are some troubles with older version of CyanogenMode rom. Are you using it and maybe you just updated it during last weeks?
From these Locus logs, I see only that data stopped coming into app, but not why this happen. Reason, some error message, should be visible in system log, which we don't have it here.
Hmm I may try to fix it by some automatic restart of sensors in case, they stop like in this case. Anyway it's really weird that it started so suddenly for you. I rewrote part of code that compute final orientation anyway your device still use older magnetic sensor + accelerometer to compute orientation and here was no big change.
EDIT: reconnection to sensors created. When there will be more then 5 seconds pause in one of two required sensors, Locus Map will try to disconnect and connect both sensors again. We will see if it will be enough.
Hello menion
i use the original Moto G3, not rooted
additional info: this problem occur only while hiking
today on my GC bike tour i "guide on" to over 50 geocaches and the problem didnt occure
so whats different: magnetic situation on handlebar and higher speed gap to swich value.
no matter, i´ll try the next days V 3.24.3.14 RC while hiking and report.
Thanks for your help
Hello menion
i use the original Moto G3, not rooted
additional info: this problem occur only while hiking
today on my GC bike tour i "guide on" to over 50 geocaches and the problem didnt occure
so whats different: magnetic situation on handlebar and higher speed gap to swich value.
no matter, i´ll try the next days V 3.24.3.14 RC while hiking and report.
Thanks for your help
Hello menion
you can mark thread as soved.
The problem didnt appeare with Beta RC
Thanks
Hello menion
you can mark thread as soved.
The problem didnt appeare with Beta RC
Thanks
Good day balloni,
thanks for information. I'm glad that problem is solved now.
Menion
Good day balloni,
thanks for information. I'm glad that problem is solved now.
Menion
Replies have been locked on this page!