Did you start messwerk to see if it was still showing something for accelerometer or orientation? Maybe it was the effect I described before where lipstick lost orientation sensor capability.
Anyhow I advise everyone to stop using watchdog and just replace the sensors so file like described in my post.
It works way better this way and running it for a couple of days I can clearly see an improved battery life.
The memory leak thing is a minor issue in my opinion as it is not always doing it. I have a memory usage about 3 MB for 2 days already so its not even an issue always.
I did not managed to track when and why the menory usage grows yet.
For me proximity sensors do not work at all with the Android 5 sensor*.so file. I rebooted several times and checked with Messwerk and MCE low power mode which stopped working, romu has similar issues.
For me proximity sensors do not work at all with the Android 5 sensor*.so file. I rebooted several times and checked with Messwerk and MCE low power mode which stopped working, romu has similar issues.
Ok very strange
Running on 2.0.1.7 ?
I wonder what could be the difference between our devices then as it is running fine here.
If it isn't software then it needs to be hardware.
Installed via CWM Recovery. Then upgraded like instruced in the same wiki to the latest version.
Did you install via another method ? Maybe used another cm base ?
If not. Then we need to find out if there is different hardware involved. But I hope it is only a software issue and not hardware related because that would mean we need different drivers for different models which makes everything a lot more complicated.
Installed via CWM Recovery. Then upgraded like instruced in the same wiki to the latest version.
Did you install via another method ? Maybe used another cm base ?
If not. Then we need to find out if there is different hardware involved. But I hope it is only a software issue and not hardware related because that would mean we need different drivers for different models which makes everything a lot more complicated.
I am using TWRP recovery and Multirom, romu? I will check things at the weekend.
Installed via CWM Recovery. Then upgraded like instruced in the same wiki to the latest version.
Did you install via another method ? Maybe used another cm base ?
If not. Then we need to find out if there is different hardware involved. But I hope it is only a software issue and not hardware related because that would mean we need different drivers for different models which makes everything a lot more complicated.
your blob file doesn't work for me either
i wonder if it depends how we unpack the file
can you upload your file again without compressing?
or for those who have problems with your blob, that they can try with mine fot couple of pages back in this thread