Locus looses heading

Hallgeir Gjesdal shared this problem 2 years ago
Solved

Some weeks ago I updated my Note 3 to Lollipop 5.0..at the same weekend I updated Locus to the newest version.


Every 2-10 seconds locus loose heading, and I'm sure this didnt happen 2 months ago when my device was running Kitkat 4.4.2.

No rooted and N9005..


I recorded my screen running locus and cgeo simultaneously to show the issue.

https://drive.google.com/file/d/0B6yeLu9CW8zwMExDcUVsd2NmRHc/view?usp=docslist_api

As you can see, cgeo does not show this behaviour.


Can other Note 3 users on Lollipop chim in here and confirm?

Or is my device broken?


More info can be provided


Hallgeir

Comments (28)

photo
1

Good day Halllgeir,


thank you for your report. I saw such problem few months ago, but unfortunately I do not remember what happen, but problem was not fixed. May I ask if you are willing to invest little time into this? Because I need to send you a special Locus version that will print our some extra information. It is possible?

photo
1

Oki, if you find some time, here is a fresh new Beta version: https://drive.google.com/file/d/0B_Nr4CT8osmtMzJudTJzd0VaZmM/view?usp=sharing , please install it and run for a while. When your problem appear close it. In directory Locus/logs should be a new log files, so send them to me. If you will be able to do this today, it will be perfect, because it looks like I will have to publish tomorrow one more version (for a long time). Thanks

photo
1

I need permission to get the file..


Some investigation:

Using external BT gps runs OK. Heading when driving is correct allways.


Internal gps:

Oritentation setting under Sensor... no filtering seem to be applied.

Very often gps show between 1-4 km/h even when standing still.

Every 2-10 second it looses all contact with satellits (reconnects next second).. can easily be spotted in gps test applications too.


Hallgeir

photo
1

Link to file was invalid, I've changed it an minute later but seems that your clicked on link in email. Try it once more please with link directly from web.


But "Every 2-10 second it looses all contact with satellits" - is very interesting. This happen also with different application, so this should be cause. If such information will be visible in logs, I may only do some workaround like "ignore rapid changed during 2 seconds", which should solve it ...

photo
1

Still need permission... even from web.

Cant you just zip it to my registered email?

This "losing all satellite connections"-issue happened when Lollipop arrived. Pretty sure, never seen it on Kitkat!

Factory reset and wipe thing performed after upgrading, so my device should be fresh.

photo
1

Hmm weird, but you are correct with permission. I already send same file to other guy and it worked, crazy.


Anyway this will definitely work http://leteckaposta.cz/613770932 (I prefer it over email as app is almost 20 MB big and not every email is able to handle it). Thanks for extra info!

photo
1

Installed!

Will take it for a spin right now..

How to share logfiles? Zipped here or what?

Sorry, newbee on this subject :-)

photo
1

:) no problem ... zipped here will be fine. Thanks!

photo
photo
1

Oki, a quick spin around the corner.

Log and gpx file in zipped file here..

photo
1

Thanks it helps. Even worst then I though. You device send two locations, one after another, with same coordinates. Unfortunately in log, I see only seconds and not milliseconds which I need. Anyway I did a small improvement.


So please second try to Locus version and second try to Google Drive sharing: https://drive.google.com/file/d/0B_Nr4CT8osmtdzN2X2dyNzZlQ28/view?usp=sharing , thank you!

photo
1

Thanks for putting your effort on this subject!

I know I can write millisecond to GPX-file from "Ultra GPS Logger"- app

But I'm at work now...until 23.30

Will that help?

photo
1

nono I was talking about milliseconds in my log. Because I wanted to know, exact difference. Anyway If you find time on test till tomorrow, lets say 10 o'clock morning, it will help. Tomorrow will be one more version on Google Play and if new beta won't work perfectly, I may improve it little more.

photo
1

Okay, sir!

Installed...

I will jump the window and provide you the files you need in half an hour..


Do you have any idea why this issue is happening?

And I'm the only one affected?

photo
1

Thank you!


Absolutely no idea. As I wrote in first post, I remember one guy who had same problem few moths, maybe an year, ago. It seems to be some software issue because reported locations are exactly same, just differ in altitude value! So Locus gets two same locations almost in same time which leads to zero bearing. I'm anyway sure, that it is solvable.

photo
1

Yes, done!

Much better, but issue still happens occasionally. And rotate mapview is kind of broken in test version.

photo
1

Perfect, thanks. I think that this fix works. In logs I see that you device send second location with exactly same location with delay around 10 - 120 milliseconds after first. I set limit to 100 ms and this is a reason, why few incorrect locations passed this test. So increase to 200 ms should be enough here.


You wrote about broken map rotate. Hmm are you sure? Because nothing around this changed here. Sometimes helps calibration of compass (rotate around all three axis). If something new happen, try to describe it little bit please, thanks!

photo
1

Need to check rotation later..

Has performed *#0*# and enter Sensor...got blue line and 3 on magnetic sensor. I allways do this after reboot.

All logging performed in horizontal dashboard mount..


OT: God, I miss my beloved SGS II with gps hack (enabled static navigation)....if I moved 1 meter, it updated position instantly.

I got it in a drawer somewhere, maybe its time to light up its screen again!

photo
1

Don't tell me about SGS 2. Best phone ever, I personally used for almost three years! :)

photo
1

Rotation is ok, sure!

As soon i ticked of Auto change.. speed over 1 m/s.. i got ridd of the epileptic behaviour of mapscreen..

Case closed for now.. g'night ☺

photo
1

Menion, latest version 3.11.2 solved heading/bearing problem completely. No mistakes there :-)

Pinpointing the problem and fixed in 24 hours..

Thank you and your team so very much!


OT:

I should be able to by you guys a beer or a caffe latte at least!

Some of the problems and issues you guys on support deal with mean a lot for people like me to get sorted.

What about I purchase LoCoins, then donate some of them back to you?

What about a poll to add a donate button in Locus Store?

photo
1

You are welcome Hallgeir!


What about keeping your money and enjoying Locus during trips? No really, no need to donate or something like this. Even after these years, I love my work and money are not motivation for me. Best you can do as a "reward" for me, is to think 10 minutes about being Vegan, and yes, I'm serious ;). Have a nice day

photo
1

Sadly, issue is back.

Did you drop some code?

Last week there was an update to my phone..Note 3, N9005, NEE (nordic)

Maybe a version change?

photo
1

Good day,

unfortunately nope. I'm checking source code that handle locations and it's same as before. I also see my fix with comment because of this problem. What changes is how Locus Map handle orientation from internal hardware sensors, but it was not this case.


I do not understand this. Note 3 is very commonly used device. Usually people complain on every problem that found and you are only one who has troubles like this with such common device, weird.


Anyway what exactly is problem now? Still exactly same issue, so blue direction arrow change to north direction for a while and then again continue correctly, so as on old video?


I'm checking code once more and direction of this arrow is really computed only from GPS coordinates, so there has to again be some issue with GPS values that Locus Map receive. It will probably needs test version again ...


Test version: http://nas.asamm.com:8080/share.cgi?ssid=0ypkZt5

Start, simulate and after problem appear, close app and send me last log from Locus/logs directory, thanks.

photo
1

Same problem, will do test version in the afternoon. Thanks for looking into this!


There is nothing special with my Note, and issue just recently came back.


Cannot tell if it was a Locus update or the Phone software update :-)

Software update was probably related to "EU free roaming" and security patches..

Would'nt be surprised if its related to my internet provider's GPS clock.. AGPS.. mismatch.. and problems only apply to same device and ISP! I strongly believe that even if you set this device to use "only GPS", it will still use celltower data for location.

I remember when i got the Note in my hands, i was not over-entustiastic of its GPS performance (coming from beloved SGII) and even read on an internet page that Note 3/Locus users should do tracking in "Only GPS" mode to prevent zaggy lines. Oh well, my Note 3 will do a suicide attempt as soon as Note 8 is available :-)

BTW, credit to the Note 3, it has served me well.


I'll be back

photo
1

There you go!


Screen recording of your Locus test apk and Locus Pro in a multi window.

https://drive.google.com/file/d/0B6yeLu9CW8zwVUhxTXRGVG94dkE/view?usp=drivesdk


Attached is the log when running only test apk and Ugps logs if they can provide extra info or timestamps.


Should I add that my moving speed show 1,8 km/h or 3,6 km/h even if im completely still.. most of the time? Has been like this for year, probably all the time. Is it normal?

photo
1

Thanks for a logs, it helped.


Oki, so let's try next version ( Beta or final on Google Play ). Issue should be solved now.

photo
1

Thank you Menion!


Updated and everything is prima :-)

photo
1

Ah I'm really glad to hear it, thanks for confirmation!

photo