bbs.blackview.com

Recently brought this phone and the compass is not even remotely stable. Tried a multitude of different ways to calibrate it, including *#87# and no luck. Looking at posts for previos models this seems to be a firmware issue. When can we expect a firmware update that will fix this?
Just updated the phone to BL6000Pro_EEA_S1000A_V1.0_20210317V19_20210317-1642

Woolley wrote:

Recently brought this phone and the compass is not even remotely stable. Tried a multitude of different ways to calibrate it, including *#87# and no luck. Looking at posts for previos models this seems to be a firmware issue. When can we expect a firmware update that will fix this?
Just updated the phone to BL6000Pro_EEA_S1000A_V1.0_20210317V19_20210317-1642

Hello, the Android 11 is planning to update on June.

I use the compass frequently and it does work most times, but I do notice that at times its not stable and constantly needs recalibration.  There likely is a problem with holding the calibration or magnetic interference; Blackview please review and fix this.

There is another issue with the compass and that is that the raw data from the sensors is reporting True North rather than the typical Magnetic North.   All other Android devices I have used report Magnetic North from the sensors (I am an Android programmer so I test each one in detail), even my old BV9800.  But this BL6000 device reports True North which is a declination corrected north value.  So you will need to make sure in any software that uses the compass sensors (mapping, star gazing, etc...), that you do not use the True North setting (which is typical) or you will get double declination corrected inaccurate compass readings. I have tested this with a real compass.  Blackview, please fix this issue as no other devices send corrected True North data directly from the sensors.  True North is normally calculated in the software.

Mike