Compass calibration stuck at 33%. [closed]

Compass calibration stuck at 33%. [answered]

asked 2014-12-23 13:43:33 +0300

ApB
27604 ●302 ●421 ●409

updated 2014-12-23 15:31:34 +0300

As the title suggests. No matter how much i move/rotate it around it doesn't seem to get past that? Reboot didn't help.

Checked with both CSD tool and one of the compass apps.

Any ideas?

The question has been closed for the following reason "the question is answered, an answer was accepted" by eric
close date 2014-12-29 10:20:04.040308

Comments

discovered the same issue just a minute ago

Charly ( 2014-12-23 13:53:12 +0300 )edit

I noticed the same after updating to vaarainjärvi (1.1.1.27). Just day before I had no issues with calibration, it was almost always perfect.

japa-fi ( 2014-12-23 21:53:41 +0300 )edit

Same issue here.

Cl2ment ( 2014-12-27 11:00:40 +0300 )edit

It seems that this has been fixed/implemented with Sailfish OS 3.2.0.x (changelog).

I am able to calibrate my Sony Xperia XA2 Dual Sim device with the CSD tool and the test passes, whereas the test failed on SFOS 3.1.0.x and the calibration level was stuck at 0.666667. The android app 'HERE WeGo' also seems to interpret the compass values correctly.

I suppose this also should work on other devices now.

Alex ( 2019-11-01 12:37:10 +0300 )edit

answered 2014-12-27 10:46:40 +0300

llornkcor

4741 ●36 ●37 ●45

Previously, the calibration level was not set against anything. Now it reflects what the android sensors reports -

0% = SENSOR_STATUS_UNRELIABLE

33% = SENSOR_STATUS_ACCURACY_LOW

66% = SENSOR_STATUS_ACCURACY_MEDIUM

or 100% SENSOR_STATUS_ACCURACY_HIGH

I have only been able to get SENSOR_STATUS_ACCURACY_LOW out of the driver.

edit flag offensive delete publish link

Comments

The compass probably works the same as it was on previous versions. The sensor status is what is reported wrong AFAI understand.

ApB ( 2014-12-27 12:47:07 +0300 )edit

Thanks llornkcor for additional information. But still wondering, why the CSD and the native compass apps are not working anymore? You mentioned "Now it reflects what the android sensors reports" but it is not working with the native Sailfish applications as it used to do, so was this broken earlier or did it get broken recently?

ziili ( 2014-12-27 12:52:23 +0300 )edit

Thanks ApB, so the problem would be only at the status, the compass itself would be still OK? That complicates the application usage as they are requiring calibration due this.

ziili ( 2014-12-27 13:14:52 +0300 )edit

As the author of the "Orienteering Compass" native app (in Jolla Store), I also noticed this. Seems that the compass calibration reading does not give very useful values for the applications. Before 1.1.1.27, the value given was always 100%, now it seems to be max 33% (as Lorn said above). I have not done anything yet for my application, but I am planning to simply fix it by multiplying the calibration value by 3. :-)

jussivuorisalmi ( 2015-01-14 20:47:59 +0300 )edit

@jussivuorisalmi

The most "correct" way IMO would be to disable calibration until the driver is fixed.

ApB ( 2015-01-14 20:53:14 +0300 )edit

Compass calibration stuck at 33%. [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by eric
close date 2014-12-29 10:20:04.040308

Comments

1 Answer

Comments

Question tools

Stats

Related questions

Compass calibration stuck at 33%. [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by eric close date 2014-12-29 10:20:04.040308

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by eric
close date 2014-12-29 10:20:04.040308