maybe we can check in cpu-z in android have in each device to be certain that we talk about same hardware:

in my case:
APDS-9930/QPDS-T930 proimity & light
AK8963 magnetometer

second thing: who has sfdroid running or installed and who not?
MPU6515 gyroscope
i have it installed but reverted init , so not running

I have D821E 16Gb running minimal Sailfish, no sfdroid, no dalvik.
With the last llelectronics .so the proximity is working, rotation is not.
Never seen sensors taking CPU more than 6% with this .so.
On idle phone the sensors* take less than 0.3%.

Forgot: errors appear only at phone bootup

It basically means the .so file does not support your gyroscope/accelerometer so orientation is not working.

It is really strange as it is working here in 2.0.1.7
So either it is a software thing in 2.0.1 that make it work here or we have really different sensors.

I run a D820 (European model)

MPU6515 too, didn't managed how to get the proximity/light sensor reference.

I run the @llelectronics .so, and rotation doesn't work either. With Messwerk, rotation works for X and Y axis only, not for Z axis.

Who has android partition loaded in sailfishos?
Maybe that has an influence too?

Wow thats ultra strange. I have everything working here.
Also Position Z Axis.

Also running MPU6515.

The only thing I noticed is that it took some time after reboot to kick in.
So at least 1 minute before I got data for the Z-Axis.
But I got data. See attached screenshot

I've just tested some swaps between the original driver and the new one. And I confirm that the rotation on Z axis doesn't work at all. So I switched back to the original driver and re-enabled the sensors watchdog.

Looking at https://developers.google.com/androi...mmerheadlmy48m
it seems that drivers for sensors are packaged for LG and QCom separately. I assume we should swap both.
Just an idea.

Romu, the N5 D820 is a North American model. D821 is European model.