(ZC554KL) significant "sensor_ind" kernel wakelock after upgrading to 8.1.0
After upgrading my ZenFone4 Max (ZC554KL) to 8.1.0 (WW_ZC554KL_15.2016.1812.505), increased battery consumption was observed. In the wakelock statistics of the kernel, in the first place is wakelock "sensor_ind" (1 day awake from 3 days summary work). II found out that the reason for this is the active ZenMotion feature (double tap on the screen to lock and unlock). But this feature on my Android 7.1 worked for a year without problems and without causing excessive energy consumption. (In any case, not so significant).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone have a similar problem? Can you recommend any solutions to the problem (without root) ?. I do not have root access to the phone.
In addition, I heard the version (but I'm not sure) that in this case even the root will not help. Just wait for the update from ASUS. Or use third-party software (like Gravity Screen ON / OFF) and calculate where the energy savings will be more.
I do not want to give up the touch screen on / off permanently. In my previous smartphone, the power key quickly "died."
P.S. Sorry for any errors. English is not my native language.
Related
Hello, my galaxy sl has bug in all rom.
When I use the internet with HSDPA internet crashes after a while, the network is blocked for a long time or if you restart preventing even the ability to receive calls and messages.
I am forced to restart the smartphone but I suffer a second bug, the battery goes to 0-1-2% and the smartphone is likely to go off after some minutes the battery salt alone.
I went from 10.1 cm to 10.2 then I started again with the stock and put the TheFrankestain ^ MOD
cm10.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cm10.2
Frankeistan mod
Please help me :crying:
Few months back I had battery curve somewhat like this.
I guess an old battery. Battery calibration will smoothen the curve.
I faced the same problem a weeks back.. the only way to solve such problem is by doing a proper battery caliberation, just google it to find more info on it..,
a new battery will solve your problem I had this problem last month but when I bought new battery I forgot about this bug
I'm monitoring my battery life after I returned to stock ROM and Kernel. I'm using ART, bacause I heard that the phone can have better battery management.
After 1/3 of usage I saw this on Attivo ( = Awake)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I used BetterBatteryStats and I saw this
I made a few research on internet, but I didn't find anything usefull.
I take another screenshot from the section Alarm
Now, I don't know if com.google.android.gms is the responsible of the GsmInboundSmsHandler wakelock, but I don't think so, cause I read that GsmInboundSmsHandler is a phone service.
What can I do? Because you can see that the Awake bar shows up constantly after 1/3 of battery usage.
The phone has been awaken for 1 g 17 h 42 m and the screen for 3 h 48 m. I can't really complain, but maybe the battery can do better than this.
Did you already fix it? If you did, then how? I´m having the same problem on my Moto G. The Phone APK is draining my battery. When I use Wakelocks Detector for more info it is the "GsmInboundSmsHandler". Please. Help.
Device: SM-G920F, LUX CSC, 6.0.1 May 2016 ROM, stock, not rooted
OK, so after spending three hours figuring out an insane Android System battery drain problem (caused by a *backup* wakelock worked-around by disabling Google backups), I have another problem with the Android OS battery usage. Now, this one is somewhat better - I can live with 10% drop per night (8 hours), but is still not normal. Did lots of searching on these kernel wakelocks, but no cookie:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Wifi and bluetoothing scanning for improved location are off.
2. NFC is off
3. S Health is disabled
4. Tried turning off all the "smart" Samsung features
5. Cache wiped (though I never believed in this voodoo
At this point I'm all out of ideas. Any help? Also, what's your overnight Android OS battery usage? Thanks!
We have all big thread about battery drain
I've just got a new phone for weeks but found that the battery life is not as good as my wife's one (same phone model).
After installing GSam, it seems to me that Android System is the main contributor of the battery drain. Using below as an example, there is over one thousand times of wakelock for GnssLocationProvider, 656 for *location* and 683 for *alarm*.
Any idea what can I do to further check what app(s) is actually causing these wakelocks? Many thanks for any help which could be offered.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Detecting wakelocks is pretty easy once you have a rooted phone. Fully charge your battery to 100% and install an app, called Wakelock Detector on the device.
jwoegerbauer said:
Detecting wakelocks is pretty easy once you have a rooted phone. Fully charge your battery to 100% and install an app, called Wakelock Detector on the device.
Click to expand...
Click to collapse
My phone is non-root one, but I've installed Wakelock Detector and with proper right granted.
But in WD, it still just showed the same like the screenshot I've shared in first post, i.e. those have been grouped under Android System...
after the update (09.05.) of the security app,
the screen on time is gone at the battery stats!!!
therefor is "Ruhezustand" (sorry don´t know in english) with wrong stats
I deinstalled the update and the sot is back
anyone else has this problem, or even better a solution???
hibernate, hibernation; to rest, to idle.
A bear hibernates in the winter. English is not an easy language...
Go with whatever runs best.
They just confirmed that SoT is gone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hope not forever,
if enough people complain about that,
maybe they bring it back in the next update
Also, is not showing Android System and before it was at 2º or 3rd place
What if you dont update the Security app? And if you did, just uninstall it? Is it affected by the big actual system updates?
the last apk that shows the sot, and works without problems for me,
is Xiaomi Security 7.7.2-230407.1.3 (arm64-v8a + arm-v7a)
I´ll wait if the sot comes back in future updates,
until I stay by this version