Greetings,
since couple of weeks ago my battery life has been exhausted, with minimal usage on my ZTE Blade G i dont get more than approx 16 hours of battery life. I studied what could possibly be the case, so i started with programs like GSAM battery, betterbatterystats and such, and there I learned a lot about wakelocks. Since the beginning of my quest to determine and fix this problem there was a certain wakelock called "gpio_kp". This wakelock uses my CPU approx 95% of the time, and make my device 100% awake, all time, which destroys my battery life. I tried everything from tweeking certain apps, settings, removing and reinstaling applications, I even installed another stock ROM, wakelock detector, even app called "Unbounce" that requires xposed but there i couldnt find "gpio_kp" wakelock. So i unbounced a lot of wakelocks but still "gpio_kp" remained.
Atm as i write this to you, completely helpless, craving for salvation my Betterbatterystats shows this on Kernel wakelocks:
"gpio_kp" 2h 46m 31 s Cnt: (c/wc/ec)0/0/0 98.5%
"powermanagerservice" 1m 24s Cnt: (c/wc/ec)494/0/0 0.8%
as u can see gpio_kp uses almost 100% time of the cpu... while second on the list is only 0.8%.. Looking forward to some answers and solution, i googled a lot about this, and didnt find any solutions, maybe this could be ground braking android wise.
kaLuta said:
Greetings,
since couple of weeks ago my battery life has been exhausted, with minimal usage on my ZTE Blade G i dont get more than approx 16 hours of battery life. I studied what could possibly be the case, so i started with programs like GSAM battery, betterbatterystats and such, and there I learned a lot about wakelocks. Since the beginning of my quest to determine and fix this problem there was a certain wakelock called "gpio_kp". This wakelock uses my CPU approx 95% of the time, and make my device 100% awake, all time, which destroys my battery life. I tried everything from tweeking certain apps, settings, removing and reinstaling applications, I even installed another stock ROM, wakelock detector, even app called "Unbounce" that requires xposed but there i couldnt find "gpio_kp" wakelock. So i unbounced a lot of wakelocks but still "gpio_kp" remained.
Atm as i write this to you, completely helpless, craving for salvation my Betterbatterystats shows this on Kernel wakelocks:
"gpio_kp" 2h 46m 31 s Cnt: (c/wc/ec)0/0/0 98.5%
"powermanagerservice" 1m 24s Cnt: (c/wc/ec)494/0/0 0.8%
as u can see gpio_kp uses almost 100% time of the cpu... while second on the list is only 0.8%.. Looking forward to some answers and solution, i googled a lot about this, and didnt find any solutions, maybe this could be ground braking android wise.
Click to expand...
Click to collapse
You can try Android Development and Hacking > Android Apps and Games > [APP][2.2+] [v.1.5+] Wakelock Detector- What keeps your phone awake when it sleeps? to get more information about this wakelock.
Has something to do with device IO = Input/Output ... I found one reference of gpio_kp in a thread about USB host drivers.
So it could be related to USB connection. Check the USB port of your device. Maybe it has to be cleaned again.
And if you had a USB cable connected, reboot your device before recording a new BBS dumpfile, as sometimes a kind of USB connection wakelock is still active even after disconnecting the USB cable.
For more help about battery life and its optimization, please post in the Android Development and Hacking > Android Apps and Games > [APP][2.1+][05 Jul. - V1.16] BetterBatteryStats thread.
It_ler said:
You can try Android Development and Hacking > Android Apps and Games > [APP][2.2+] [v.1.5+] Wakelock Detector- What keeps your phone awake when it sleeps? to get more information about this wakelock.
Has something to do with device IO = Input/Output ... I found one reference of gpio_kp in a thread about USB host drivers.
So it could be related to USB connection. Check the USB port of your device. Maybe it has to be cleaned again.
And if you had a USB cable connected, reboot your device before recording a new BBS dumpfile, as sometimes a kind of USB connection wakelock is still active even after disconnecting the USB cable.
For more help about battery life and its optimization, please post in the Android Development and Hacking > Android Apps and Games > [APP][2.1+][05 Jul. - V1.16] BetterBatteryStats thread.
Click to expand...
Click to collapse
I already tried wakelock detector before, and it only showed me that system was using it, it didnt give me too much information so I deleted it, now I installed it again but there is no information that i need.
I cleaned USB port, reinstaled usb drivers, rebooted, and now since restart BBS shows this in kernel wakelock:
gpio_kp 20m 13s 63.7%
power manager 1m 1s 3.2%
wakelock detector says out of 33 m since restart:
total wake time 33 m 39s
screen on time 13 m 16 s
awake 20 m 23 s
which is somewhat confusing.
gpio_kp percentage will go up, as the time flies, it looks as it needs some time before it gets active after restart.
kaLuta said:
I already tried wakelock detector before, and it only showed me that system was using it, it didnt give me too much information so I deleted it, now I installed it again but there is no information that i need.
I cleaned USB port, reinstaled usb drivers, rebooted, and now since restart BBS shows this in kernel wakelock:
gpio_kp 20m 13s 63.7%
power manager 1m 1s 3.2%
wakelock detector says out of 33 m since restart:
total wake time 33 m 39s
screen on time 13 m 16 s
awake 20 m 23 s
which is somewhat confusing.
gpio_kp percentage will go up, as the time flies, it looks as it needs some time before it gets active after restart.
Click to expand...
Click to collapse
Please post an idle dump in bbs thread I have already linked.
There you will hopefully get a better advice.
Thanks for your understanding.
My tapatalk signature:
Device: SGS5 (SM-G900F)
ROM: AllianceROM v5.3
Kernel: Stock G900FXXU1ANG7
Recovery: PhilZ-touch CWM
Modem: G900FXU1ANG7
If you have any question about or any issue with your SGS2, just ask in the New members friendly Q&A thread.
... for the SGS5, just ask in the Noob friendly S5 All in one support thread
If you need general help/assistence, please go to XDA-Assist.
Related
Hey guys,
N00b here.
I've read the n00b guide and also searched around in the forum. I did find a thread similar to mine however I couldn't really get any useful info out of it and maybe since then new tools are available to help me track my problem, so I post my question.
So... on to it...
My Nexus S is suddenly having high keep-awake times. About phone tells me a battery usage of 32% android system, followed by 21% Display. Android system has a keep awake time of 3h 51m and a CPU total of 7m 52s. All this over the course of 19 hours. I don't have a screenshot with me but it's clear that the phone is awake a lot when the screen is off.
Automatic updates are off.
Some days ago everything was fine. My google acount is only synching contacts and calendar and even that is turned off when I'm not at home. Even so, I saw a high usage of the keep-awake bar even when the screen was off.
I've installed some weather widgets and battery info widgets and the update cycles of weather applications are around 45 mins so I wouldn't see a reason for such a high period of keep-awake cycles.
Anyway, each phone is a phone, is there an application that can tell you what is keeping the phone awake ? I have installed Watchdog lite but it doesn't show anything abnormal. I've installed Spare Parts Plus but it can't show me the battery usage history because apparently stock 2.3.4 Gingerbread doesn't support it.
So now I'm stick with trying to disabled notifications on one app, remove its widget and see if it helps. If it doesn't.. go to the next. This is quite tedious work really.
Still the battery life is ok I guess... 50% after 19 hours however I haven't played around with it much but I would be happier to have a low keep-awake cycle for the Android System like I had some days ago.. makes me feel like everything is fine
Thanks for any hints guys!
Having the same issue as well.. I have my widgets and such to only check every 4-6 hours, but the awake time in the battery stats is nearly on all the time.
Keep awake time is 4 hours and 22 min, out of 12 hours of battery. I'm left with 42 % battery with only 1 hr 15 min on screen time (texts and such, no games).
Hmmm a memory drain of 60% in 1 hour is quite a bit heavy. I would suggest you to download Watchdog lite from the app store and use it's real time CPU analyzer to try and see what's consuming the most.
Once I had weatherbug going rogue. But then it showed up in the battery usage list with a high CPU usage and clicking on the item I could see a high awake time so I uninstalled it.
At the moment I've removed some of my widgets and so far it seems to be OK. However tonight I had some weird awake times again. I uninstalled Battery Info widget from the phone and I'll see if it all goes well tonight. Then I'll start to activate the other widgets I had deactivated before to see what happens.
Also I downloaded aCatLog from the app store. Pretty interesting tool... you can see what's going on in the logs. I see a few Java exceptions every now and then.. never a good sign as they might not be handled properly by the application code that threw them. I see evernote synch problems, a data traffic counter throwing exceptions and K-9 to have problems with idle connection reset by peer. And I often see the garbage collector working. But I assume all this is normal. Switching to the event log it's too much information to absorve. Nevertheless I haven't seen in any of those logs an explicit request or grant of a system wake lock.
mindwalkr said:
My Nexus S is suddenly having high keep-awake times.
Click to expand...
Click to collapse
Did you recently enable Latitude, by any chance?
Try top -m 5 -n 1 in terminal
fallenguru said:
Did you recently enable Latitude, by any chance?
Click to expand...
Click to collapse
No Latitude enabled
snandlal said:
Try top -m 5 -n 1 in terminal
Click to expand...
Click to collapse
Do I need to download Terminal Emulator from the market to do this ? Or do I need to download the Android SDK and connect to the device via USB ? I need to check out to do this, never done it before and this is my first android phone.. only a week old
Again this morning my awake time was on for quite a bit (I guess 1 hour). I got an extract of the main log...
Some things are curious, the following occurs more or less each half hour. I am signed out of gtalk why was the service trying to keep alive ?
06-08 06:10:03.656 W/GTalkService( 189): [GTalkConnection.18] doConnect: caught XMPPError connecting to mtalk.google.com:5228.: (502)
06-08 06:10:03.656 W/GTalkService( 189): -- caused by: java.net.SocketTimeoutException: Connection timed out
06-08 06:10:03.660 D/GTalkService( 189): [GTalkConnection.18] connectionClosed: connId=0, error=CONNECTION FAILED
This is also giving me trouble, I might uninstall my Traffic Counter app
06-08 06:42:30.710 W/System.err( 4015): java.io.FileNotFoundException: /data/data/com.carl.trafficcounter/app_pref_bytes_last/0_0_bytes_last (No such file or directory)
Evernote seems to have some issues as well sometimes
06-08 06:44:36.371 I/com.evernote.android.edam.TAndroidHttpClient( 5320): 25: Response received in: 126718ms
06-08 06:44:36.398 E/com.evernote.client.SyncService( 5320): Sync failed
06-08 06:44:36.398 E/com.evernote.client.SyncService( 5320): org.apache.thrift.transport.TTransportException: java.net.UnknownHostException: www.evernote.com
And that's all I could see. Everything else seems to be garbage collection WiFi activities and what not..
It seems that I've narrowed down Go Weather as what's making my Android System stay awake. I couldn't see anything really useful on logcat about this but empiric observations seem to confirm it.
If I remove the Go Weather widget and turn off it's background updates (hourly), then restart the phone... I see the Android System incrementing some 3-4 mins keep awake time per hour. If I set the widget again and turn on Go Weather's background updates, after an hour the Android System keep awake time goes up like 15-20 mins or so. If at this point I remove the Go Weather widget and turn off it's background updates, the Android System keep awake will still go up at the same rate as if the Widget was there. If I restart the phone without the widget, then the Android System keep awake seems to increase back to regular 3-4 mins per hour.
The funny thing is that according to Permission Dog, Go Weather doesn't even use the WAKE permission so I would rule it out as what was keeping Android System awake.
Android System was driving me crazy too. I figured out that when my WiFi was enabled, it would continually keep the phone awake when the screen was off. So I just toggle the wifi off when I'm not using it, and android system behaves now.
I'm curious as to what changed though, because when I was using stock 2.3.4 and CM7.0.3 I would leave wifi on all day, and android system didn't cause any battery issues.
Hello all, I recently noticed that my OPO was not going into deep sleep. So I installed wakelock detector and to my surprise, nothing out of the ordinary was going on. I proceeded to wipe the dalvik and cache, still nothing, won't deep sleep. Last night I flashed franco kernel in the hopes that it would solve the problem, guess what, nothing, still won't deep sleep. The phone just drops to 300mhz and stays there for the minimum frequency.
I'm running liquid smooth 3.2 (4.4.4) with the recently flashed franco kernel.
Do you guys have any other suggestions on what to do?, I was just about to flash an entirely new rom and keep it barebones till the end of the week when cm 12s and oxygen os are released.
I'm experiencing exactly the same issue..
amd-dude said:
Hello all, I recently noticed that my OPO was not going into deep sleep. So I installed wakelock detector and to my surprise, nothing out of the ordinary was going on. I proceeded to wipe the dalvik and cache, still nothing, won't deep sleep. Last night I flashed franco kernel in the hopes that it would solve the problem, guess what, nothing, still won't deep sleep. The phone just drops to 300mhz and stays there for the minimum frequency.
I'm running liquid smooth 3.2 (4.4.4) with the recently flashed franco kernel.
Do you guys have any other suggestions on what to do?, I was just about to flash an entirely new rom and keep it barebones till the end of the week when cm 12s and oxygen os are released.
Click to expand...
Click to collapse
Maybe the PlayServices are the Problem somewhere here is a guid to prevent them to keep your phone awake
Actually play services did not come up in the battery stats to indicate it was indeed active. I ran through anything, there is nothing causing unnecessary wakelocks. So that's why I'm confused.
amd-dude said:
Actually play services did not come up in the battery stats to indicate it was indeed active. I ran through anything, there is nothing causing unnecessary wakelocks. So that's why I'm confused.
Click to expand...
Click to collapse
Play Services doesn't always show up as Play Services in the battery stats page in your settings menu, it quite often will show up as Android OS.
Transmitted via Bacon
timmaaa said:
Play Services doesn't always show up as Play Services in the battery stats page in your settings menu, it quite often will show up as Android OS.
Transmitted via Bacon
Click to expand...
Click to collapse
Not even that, as I said there was nothing android related nor was there any app in wakelock detector that was showing signs of a wakelock. For good measure I did follow the many guides on stopping google services etc. and none of them worked. Phone still won't go into deep sleep. Strangely enough it was wasn't affecting my battery life that much, was still getting about 6hrs on screen time with 14% battery left.
amd-dude said:
Not even that, as I said there was nothing android related nor was there any app in wakelock detector that was showing signs of a wakelock. For good measure I did follow the many guides on stopping google services etc. and none of them worked. Phone still won't go into deep sleep. Strangely enough it was wasn't affecting my battery life that much, was still getting about 6hrs on screen time with 14% battery left.
Click to expand...
Click to collapse
Sounds to me like your battery stats might just be screwy.
Transmitted via Bacon
So now I'm wondering, as well. What would an example of good/excellent deep sleep look like? % drop over time?
My battery stats show cell standby at 1%, phone idle at 1%, and over over eight hours go from 100% to about 86%. Would that drain be considered deep sleep, or good deep sleep?
I had a similar issue and able troubleshoot successfully.
Device:
- POCO F1
- MIUI 12.0.3.0, Android 10
- Magisk 21
What tried but didn't help
- There is no wake-locks active
- Tried Battery Saver and Ultra Battery Saver
- Tried Airplane mode
- Tried rebooting
- There is no significant battery drain (only 1.6% per hour)
- Tried disabling Proximity sensor
- Tried wiping dalvik-cache
I have followed the guide by Intel at https://software.intel.com/content/...-no-sleep-issues-in-android-applications.html
As I mentioned earlier, there is no active wakelock, that is why the troubleshooting was much difficult.
I have digged into `/sys/kernel/debug/wakeup_sources` and sorted processes based on the column `prevent_suspend_time`. The process `qtidataservice` was on the top. Not sure what it is, but it's probably from Qualcomm and running under the `radio` user.
The `strace` was showing nothing. I have simply killed that process. It's eventually re-created with a new PID. Interestingly the device began to go Deep-sleep while in idle.
100% Awake, Galaxy S5. Better Battery Stats Kernel Wakelocks "File could not be read"
I've had my Samsung Galaxy S5 for over a year. A while back I updated the OS a couple of times, and now it's on Lollipop (5.1.1). Lately the battery life is very low, although I don't think this started at the same time as the upgrades.
I've tried to use Better Battery Stats to figure out why. It concurs with the Battery control panel that my phone is staying Awake all of the time, never in sleep mode. Most of the time is at the 300MHz cpu speed. Unfortunately when I try to view the Kernel Wakelocks section of BBS, it just says "File could not be read" and presents me no statistics. I was using an old version of BBS, and have just updated to the newest version and this behavior persists.
According to the Battery control panel my top consumers of battery life are Android OS (10-20%), Android System, Bluetooth, Screen, Google Play Services, Cell standby (2-5%), and then a bunch of apps at <5% each..
Hello,
Welcome to XDA.
If your device is rooted you can try the Wakelock Detector from playstore to check your wakelocks. There are also apps to control your wakelocks and you can also use the Kernel Auditor app to further manage your device's behavior.
I didn't see a question in your post but you can try posting your issue in the forum linked below.
http://forum.xda-developers.com/galaxy-s5/help
The experts there may be able to help, good luck.
Thanks, I'll try the s5 help forum
So I picked up a Nvidia Shield K1 this weekend and this night I thought to see how effrctive DOSE was.
I went to bed with 96% battery and woke up to a 70% battery.
I havent tweaked anything in my tablet its completly stock.
I'm going to upload a screenshot to prove it. The tablet wws in sleep mode trough this screenshot and not being used as it wpuld sugest.
My question is, is there a way to solve this?
Sorry if my english is bad, and thanks to anyone whom can help me!
Sent from my SHIELD Tablet K1 using XDA Free mobile app
Filz0r said:
So I picked up a Nvidia Shield K1 this weekend and this night I thought to see how effrctive DOSE was.
I went to bed with 96% battery and woke up to a 70% battery.
I havent tweaked anything in my tablet its completly stock.
I'm going to upload a screenshot to prove it. The tablet wws in sleep mode trough this screenshot and not being used as it wpuld sugest.
My question is, is there a way to solve this?
Sorry if my english is bad, and thanks to anyone whom can help me!
Sent from my SHIELD Tablet K1 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
Have you the Marshmallow update?
Yes I updated it as soon as turned it on
Sent from my XT1524 using XDA Free mobile app
I had the same problem but i think a factory reset solved it.
Strange, I haven't this issue. I have upgraded to Marshmallow once opened from its box, and unlock bootloader/root just after.
Maybe an application which blocks the doze mode?
Have you tried a wakelock detector? You should be able to track down what exactly is eating up your battery.
Check out GSam Battery Monitor, works for me!
Yes, GSam or BetterBatteryStats (link of the XDA post)
There's a thread on the NVidia forum about a similar drain, and in many cases the tablet also runs quite hot when it should be doing next to nothing.
forums.geforce.com/default/topic/904962/shield-tablet/android-6-0-update-battery-drain-by-miscellaneous-app-new-shield-k1-model-/
It appears to be a bug after the 6.0 update, it triggers the /system/bin/logd process.
You can check if you have the same bug by running adb shell with
Code:
top -m 5
(for 5 highes using processes) when it drains quickly, and look for the /system/bin/logd process.
It doesn't necessarily mean that it's the same bug, but considering the fact that quite a lot of people experience the same issue..
On the forum many users reported improvements when turning app optimization off, occasionally turning wifi off and on again and setting 'Keep Wi-Fi on during sleep' to 'Only when plugged in' or 'never'.
I have had some good results by selecting 'Only when plugged in' and by turning off 'Help NVIDIA improve SHIELD' in 'About tablet', but we'll have to wait on NVidia to fix this.
Same issue since marshmallow, runs hot with light use and huge battery drain. Been busy so haven't tried to debug or even reset yet but good to know its not just me.... Will unlock and root (will be a factory reset) soon, hope all will be fixed with this
Downgraded to 5.1.1 for the bad battery drain on marshmallow so I'm waiting to see if nvidia issues a update
I sufferring too the issue about abnormal battery drain, and I can't find a way to disable the touchboost (that clock at max cpu&gpu at same time)
so I searched for a kernel manager app compatible since 27th December when I installed my K1 with ota 6.0 , the only one that was updated is Ex Kernel Manager app (latest version 2.41 because 2.38 etc doesn't work) setting it on eco power mode or underclocking cpu to max 1224Mhz (if tablet is turned off or restarted must be set again), lcd set at 60% brightness but auto on, gave to me 26hrs. of active use on internet websurfing, movies and some light gaming at fallout shelter (2%) with wifi on all time and bluetooth for some.
Now I'm happy again ^_^
Regards
aaronne said:
I sufferring too the issue about abnormal battery drain, and I can't find a way to disable the touchboost (that clock at max cpu&gpu at same time)
so I searched for a kernel manager app compatible since 27th December when I installed my K1 with ota 6.0 , the only one that was updated is Ex Kernel Manager app (latest version 2.41 because 2.38 etc doesn't work) setting it on eco power mode or underclocking cpu to max 1224Mhz (if tablet is turned off or restarted must be set again), lcd set at 60% brightness but auto on, gave to me 26hrs. of active use on internet websurfing, movies and some light gaming at fallout shelter (2%) with wifi on all time and bluetooth for some.
Now I'm happy again ^_^
Regards
Click to expand...
Click to collapse
Hmm, I was actually hoping on keeping one of my devices completely stock/unrooted for a change, makes it easier for OTA's and takes less of my time on tinkering with it
That being said, when looking at CPU Spy it seems the CPU govenor isn't really flexible, most of the CPU states are sleep, 204MHz, 312MHz, 1044MHz, 1530MHz and 2218MHz, and little to no time on the other states.
I'm no kernel expert, but it seems to me that battery life could be extended without performance issues if it wouldn't immediately switch to high CPU states but the states in between...
Anyway, haven't had these abnormal drains since I changed the settings I mentioned earlier. Misc drain snuck a couple of percent yesterday, but lightyears away from what it used to.
I've done those changes and so far the battery life has improved a lot, one more thing my WiFi sometimes drops out of the blue does anyone else have this issue?
Sent from my SHIELD Tablet K1 using XDA Free mobile app
Filz0r said:
I've done those changes and so far the battery life has improved a lot, one more thing my WiFi sometimes drops out of the blue does anyone else have this issue?
Sent from my SHIELD Tablet K1 using XDA Free mobile app
Click to expand...
Click to collapse
Haven't had a dropout as far as I know, but I did notice a WiFi performance drop once or twice. I was still connected, but webpages wouldn't load untill I'd reset the WiFi adapter. Those were also the times that a slight misc drain appeared.
I received NVidia shield v2 K1 with lollipop out of the box.
it updated via OTA to Marshmallow 6.0 and I had to revert back and block it from updating cos it was way to buggy for me, main problem was Wi-Fi/No internet issue. The tablet was a paper weight without internet.
N.B it did connect to the Wi-Fi. Rebooted my router, rebooted tablet, turned airport mode on/off , Changed frequencies and still nothing. My other devices could connect and have internet without issue.
N.B. It could connect to Wi-Fi, just no internet icon !
frentrop said:
There's a thread on the NVidia forum about a similar drain, and in many cases the tablet also runs quite hot when it should be doing next to nothing.
forums.geforce.com/default/topic/904962/shield-tablet/android-6-0-update-battery-drain-by-miscellaneous-app-new-shield-k1-model-/
It appears to be a bug after the 6.0 update, it triggers the /system/bin/logd process.
You can check if you have the same bug by running adb shell with
Code:
top -m 5
(for 5 highes using processes) when it drains quickly, and look for the /system/bin/logd process.
It doesn't necessarily mean that it's the same bug, but considering the fact that quite a lot of people experience the same issue..
On the forum many users reported improvements when turning app optimization off, occasionally turning wifi off and on again and setting 'Keep Wi-Fi on during sleep' to 'Only when plugged in' or 'never'.
I have had some good results by selecting 'Only when plugged in' and by turning off 'Help NVIDIA improve SHIELD' in 'About tablet', but we'll have to wait on NVidia to fix this.
Click to expand...
Click to collapse
+1,
I had to set WiFi to Never on during sleep, I also use the debloater app to pretty much disable all Nvidia apps. My standby time has increased dramatically. But I hope nvidia releases an official fix.
Sent from my ONE E1005 using Tapatalk
Hi guys, I recently updated to 6.0 and have issues with battery drain during sleep. I see that I have a lot of wake locks by GOOGLE_C2DM. Attached is the export from GSAM.
First I thought it was Facebook and Instagram which had the C2DM services, I uninstalled the apps but still have the wake locks.
GSam Labs - Battery Monitor - Export Data
Kernel (Android OS)
Jan 28, 2016 9:18:27 AM
Usage Details
CPU Usage:14h 13m 2s
CPU Usage (Background Only):14h 13m 2s
Keep Awake:4h 18m 5s
Number of Wake Locks:35
Bytes Sent:26.08 KB
Bytes Received:54.92 KB
App UID:0
Wakelock Detail
GOOGLE_C2DM0.4s(35)
Included Packages
Included Processes
file-storage
mmcqd/0rpmb
wifi_scan_polic
cfinteractive
wl_event_handle
nvmap-bz
kauditd
sdcard
zygote
irq/80-soctherm
ueventd
kswapd0
surfaceflinger
watchdogd
debuggerd
watchdog/0
watchdog/1
watchdog/2
watchdog/3
tlk_daemon
jbd2/mmcblk0p13
jbd2/mmcblk0p14
jbd2/mmcblk0p18
jbd2/mmcblk0p23
jbd2/mmcblk0p8-
icfb-kthread
su
adbd
lmkd
logd
netd
spi0
spi3
vold
/init
rcu_preempt
khubd
rcu_sched
irq/105-tegradc
irq/118-4-0058
kthreadd
installd
kworker/0:0
kworker/0:1
kworker/0:2
kworker/0:3
kworker/0:4
kworker/0:5
kworker/0:6
kworker/0:7
kworker/0:8
kworker/0:9
kworker/1:0
kworker/1:1
kworker/1:2
kworker/1:3
kworker/1:4
kworker/1:5
kworker/2:0
kworker/2:1
kworker/2:2
kworker/2:3
kworker/3:0
kworker/3:1
kworker/3:2
kworker/3:3
healthd
dhd_watchdog_th
irq/259-spi0.0
mmcqd/0
irq/77-tegra_ac
irq/77-tegra_mo
ksoftirqd/0
ksoftirqd/1
ksoftirqd/2
ksoftirqd/3
wpa_supplicant
migration/0
migration/1
migration/2
migration/3
irq/189-gk20a_s
dhd_dpc
dhd_rxf
kworker/0:0H
kworker/0:10
kworker/0:1H
kworker/0:2H
kworker/1:0H
kworker/1:1H
kworker/1:2H
kworker/2:0H
kworker/2:1H
kworker/3:0H
kworker/3:1H
kworker/u8:0
kworker/u8:1
kworker/u8:2
kworker/u8:3
kworker/u8:4
kworker/u8:5
kworker/u8:6
kworker/u8:7
kworker/u8:8
kworker/u8:9
kworker/u9:1
irq/321-mpu6xxx
kworker/u8:10
kworker/u8:11
kworker/u8:12
tegradc.0/a
tegradc.0/b
tegradc.0/c
tegradc.0/d
tegradc.0/e
tegradc.1/a
tegradc.1/b
tegradc.1/c
tegradc.1/d
tegradc.1/e
no, it is : /system/bin/logd -> this process gets stuck due to a third party error.
Just install OS Monitor and reset this Process if it runs into a high load.
nVidia will Release a Patch within the next days or a week, there is a announcment for that and a beta update for tester.
I install Deep Sleep app and set it to SLUMBERER MODE, now my battery only goes down 2% overnight. I'm happy with the results. Don't mind having notifications appear after I wake up device.
frentrop said:
.
.
.
I have had some good results by selecting 'Only when plugged in' and by turning off 'Help NVIDIA improve SHIELD' in 'About tablet', but we'll have to wait on NVidia to fix this.
Click to expand...
Click to collapse
Hi,
Did this fix your problem permanently?
I bought mine 3 days ago, updated to mm 2 days ago and yesterday, voila, drain occurred while browsing pages I think, or some YouTube or streaming video...
I will try this today when I come back.
Hello all,
My phab 2 Pro is draining its battery too fast with the screen off. Using Battery Historian I've been able to pinpoint it down to something keeping the phone awake when it should be sleeping. The problem is it happens randomly and I haven't been able to "connect" it to a specific app or setting.
The "kernel wakeup reason" that Battery Historian shows as the (I think so anyway) culprit is "Abort:Wakeup IRQ -1169425744 (null) pending". The number after "IRQ -" changes from log to log.
Something else that keeps popping up on the "Userspace wakelock" line with short bursts is "RILJ". This is precisely during the period that the phone is "awake" but the screen is off. So maybe the RILJ and the IRQ thing have something to do with each other?
Steps I took:
Full factory reset
Uninstalled ALL apps that can be uninstalled.
Disabled ALL apps that can be disabled, apart from things that have to stay like keyboard.
Switched of any Location setting that can be switched off
Switched of all syncing that can be switched off
Enabled developer options (to be able to pull the bugreport.txt off the device using adb)
Engaged airplane mode
But even with all of these steps, which leaves the phone totally unusable (but I have another daily driver) this weird kernel wakelock still happens frequently, draining the battery very fast. Going from 38% down to 9% in just 6 hours, with the screen off(!) is plainly unacceptable.
Are there other users out there experiencing the same? I know of one guy who posted lasted year, but maybe there are more out there?
Can anybody help with this? I have no idea what to do now I more or less now where the problem lies. I'm no coder and don't know anybody at Lenovo...
Regards,
Sander
Is not normal what happens to you, but as a remote solution ... try to get into the applications that are working, and look at google services, there is one that spends a bestiality, it is called fileakintentoperation $ external that application next to the others Spend a lot of ram, I ended up blocking the services of google play and play store, and I assure you that the battery lasts for more than two days
rogerbcn said:
Is not normal what happens to you, but as a remote solution ... try to get into the applications that are working, and look at google services, there is one that spends a bestiality, it is called fileakintentoperation $ external that application next to the others Spend a lot of ram, I ended up blocking the services of google play and play store, and I assure you that the battery lasts for more than two days
Click to expand...
Click to collapse
Hi Rogerbcn,
thanks for replying.
Could you type the name of the app/service again? Google doesn't return anything on "fileakintentoperation" .
I already have the Google play and Play Store apps disabled, unfortunately, that didn't help.
Regards,
Sander
Is just below, where are the services of google play, and is also a service, but after reading that you have disconnected and you also have disconnected play store, gives me your battery or is badly calibrated or is to change, Take it to the sat of lenovo and assert your guarantee that for that we have spent 500 dollars / euros,regards
[rogerbcn] is probably correct and that you may have a defective battery. I use greenify and it seems to extend battery life about 23% for app hibernation.
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
I resolved with task killer (kil 1 sec. After lockscreen)
edit: not resolved... anyone has other experience?
Seems to be resolved.
I used greenify, with doze go (adb solution)