This object is in archive! 

Problem true bearing

Juris shared this problem 9 years ago
Closed

http:--youtu.be-467rLfh45U8


Hello, on the motion of the

cursor rotates chaotic.


Deivice - Huawei Y550.

Replies (9)

photo
1

Hi Juris,

please make a test with following settings in "sensors":


check first segment "use hardware compass"

uncheck "Auto change"

use "Medium filter" in "Orientation filter"


and report what happens

photo
1

HI,

I tried, but to no avail.

photo
1

Good day Juris,


1. did you tried any other application? I think such issue with be more in device itself, then in Locus.

2. you may try to calibrate a compass in your device. Just use Locus and enable this rotation. Then wave with your device in hands a while (usually rotate a device around all three axis). This may helps here (it usually solve my similar issues I rarely have with device).

photo
1

HI


1 Other APP is working correctly. No errors! (Oruxmaps, Google maps, Osman, Waze)


2. Calibrated also.


I think that on this Devaisu locus does not work correctly.


Thanks

photo
1

I'm checking more precisely your video.


Seems that compass is working correctly for you, right? Important information - blue moving cursor is not depend on any of settings you tried. It simply take previous received location from GPS and compute bearing to new received GPS location. And this is angle that cursor is rotated on screen.


So, when i look carefully, it looks that every second when new orientation is computed, in really small moment, cursor rotates to 0° and then immediately to new orientation. Hmm weird. Aren't you using any external application that modify your GPS locations before you use them in Locus? Or some external BT device or something like this?

photo
1

HI


The compass works properly!

External applications do not use! With an external device to the BT everything is working correctly!

Other APP (Orux maps, Google maps Waze) works correctly!thank you

photo
1

Good day Juris,


I'm sorry for a very late response. I was firstly hoping that I I'll be able to simulate same problem on my device and in the end, I completely forget on this problem.


Anyway during these two months, no one reported issue even closely similar to yours and I wasn't also able to simulate it on my own device (best case). So i have to leave this topic as is for now, because I have no idea how to solve this issue, that looks more like a problem in your device then directly in app.

Replies have been locked on this page!