llelectronics | # 481 | 2016-02-20, 22:29 | Report

Nope I checked the permissions.
And as the file is found but giving an error message it must be something else.

Running 2.0.0.10 btw. Maybe you have a newer version were it works.

frullewulle | # 482 | 2016-02-20, 22:40 | Report

i've updated to 2.0.1.7, but don't think that does a lot

i don't change screen settings anymore after reboot.
every change there gives a bit higher cpu usage for both, sensors.qcom and sensorfwd

llelectronics | # 483 | 2016-02-20, 23:37 | Report

Upgraded to 2.0.1.7 but no change. Still the same error message when I try to get this .so file to start.
So there must be something else different here.

What I noticed is that. When doing a big change in the accelerometer and pressing on the power button I immediately get the high cpu usage. Holding the phone still and pressing the power button until the lock screen appears and pressing it again and the sensor processes go immediately down again and won't go up at this stage.

Not sure whats wrong there but its reproducable everytime.

jellyroll | # 484 | 2016-02-21, 12:27 | Report

How did you disabled sensors.qcom in init.hammerhead.rc? Did you edit lines or just deleted some stuff?

frullewulle | # 485 | 2016-02-21, 13:35 | Report

putting # in front of some specific sensor lines almost in the end of the file.

But have already restored it.
Now i'm trying to disabled some sensors in /etc/sensorsfw/primaryuse.conf
disabled accelerometer, magnetometeradaptor, gyroscopeadaptor, orientationadaptor

proximity and alsadpter are still working
huge improvement in cpu usage

i always restart the phone to be sure that every service is fully restarting

I believe that the orientationadapter is the main reason for the big cpu usage, and after a while also a bigger memory usage

llelectronics | # 486 | 2016-02-21, 13:43 | Report

Yeah exactly that correspondents with my observations.

romu | # 487 | 2016-02-22, 09:47 | Report

@llelectronics: just added your watchdog service to my N5, let you know how things are going. Thanks a lot, that could be really helpful/

llelectronics | # 488 | 2016-02-22, 18:06 | Report

Just an update on my script or in general the restarting when process is to high for an amount of time.
I encountered already several times that lipstick or whatever does the rotation for the UI sometimes keeps hanging.
So "Messwerk" still shows the gyroscope still working though apps don't rotate anymore.
Not sure what triggers that but I fear it might be reloading the sensorfwd service at a specific point where it kills lipsticks ability to use it.

The only solution I found so far for this restarting lipstick via settings utitlites (or using the terminal command)

So in general this script or any other script are just workarounds that might trigger sideeffects.
We need to fix the real problem somehow that is clearly connected to the gyroscope sensors.

jellyroll | # 489 | 2016-02-22, 23:12 | Report

The best solution I could find so far is disabling some sensors. This results in a longer battery life.

llelectronics | # 490 | 2016-02-23, 00:25 | Report

Based on the suggestion to replace the binary blob .so file.
I searched for one that
1) works on my version without issues
2) does not suffer from that bug

and tada I found an .so file from Android 5.0.2 that works flawlessly and for the first few hours I am testing it currently I had no high cpu usage of sensor.qcom or sensorfw anymore.

Before testing it on your own. Remove my script or the .service file or any other solution you had installed that restarts sensorfwd to make sure it works for you to.
I tested it on my updated 2.0.1 installation.

Get this sensors.msm8974.so file extract it and put the sensors.msm8974.so into /vendor/lib/hw/

Make sure to make a backup of the file thats already in there just in case.

After that reboot your device.
Now try testing with top open in a ssh session and see if it works for you.

For me its working fine and I now get a clearly longer battery life as its also using almost nothing of the cpu when using the accelerometer to switch orientation in browser or video player. (or do the shaking test)

Hope that settles it finally :P