[ROM]★[TF701T-Asus Stock Rooted][KK 4.4.2 DEODEX/ODEX 11.4.1.27][Nov 24]★

Lopburi

Member
Jun 28, 2014
34
17
0
Same here.

I am having similar battery drain issues, too. I went back to chromi and the problem persisted. Now I am back on this Rom again. Definitely something that keeps my table awake and thus drain the battery, sometimes about 5% per hour with the screen off. I too suspect Google apps. Btw, I have no dock.

Sent from my K00C using Tapatalk
Same here I'm having battery drain problem on both of my tf701t 1 is unlocked and the other one is not. The problem started about 1 week also ago on both of them and the battery drain at lease 5% per hour that's with screen off and I don't have dock also. I hope we find the fix soon.
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
0
Los Angeles, CA
Same here I'm having battery drain problem on both of my tf701t 1 is unlocked and the other one is not. The problem started about 1 week also ago on both of them and the battery drain at lease 5% per hour that's with screen off and I don't have dock also. I hope we find the fix soon.
Let's test the Google apps theory, shall we? ;)
I'm going to uninstall all Google apps updates as soon as I got it charged again (drained from 80% to zero overnight again).
If that doesn't do it, I'll reflash this rom and will not update any apps.

I froze about everything with "Google" in it in TiBu, but interestingly enough Wakelock Detector shows Google Search still at the top of the list - even when frozen!!! I don't have enough background knowledge of Android to analyze this, but could it be that some service is still calling Google Search and that is causing it to show up in the wakelock list????

I leave the dock out of it for now. I have the massive battery drain even without docking the tablet at all. So I gotta find that problem first.
 

Lopburi

Member
Jun 28, 2014
34
17
0
Let's test the Google apps theory, shall we? ;)
I'm going to uninstall all Google apps updates as soon as I got it charged again (drained from 80% to zero overnight again).
If that doesn't do it, I'll reflash this rom and will not update any apps.

I froze about everything with "Google" in it in TiBu, but interestingly enough Wakelock Detector shows Google Search still at the top of the list - even when frozen!!! I don't have enough background knowledge of Android to analyze this, but could it be that some service is still calling Google Search and that is causing it to show up in the wakelock list????

I leave the dock out of it for now. I have the massive battery drain even without docking the tablet at all. So I gotta find that problem first.
That's what happen to both of my tablet as well. :(
 

houtx2

Senior Member
Sep 16, 2011
276
41
48
Houston
Let's test the Google apps theory, shall we? ;)
I'm going to uninstall all Google apps updates as soon as I got it charged again (drained from 80% to zero overnight again).
If that doesn't do it, I'll reflash this rom and will not update any apps.

I froze about everything with "Google" in it in TiBu, but interestingly enough Wakelock Detector shows Google Search still at the top of the list - even when frozen!!! I don't have enough background knowledge of Android to analyze this, but could it be that some service is still calling Google Search and that is causing it to show up in the wakelock list????

I leave the dock out of it for now. I have the massive battery drain even without docking the tablet at all. So I gotta find that problem first.
There is considerable chatter around the web that google play services 6.5.87 is a battery hog. This is the version that I have. If someone does a fresh install, please note what version is in the ROM. This update could be our problem.
 

Daruniafx

Senior Member
Apr 25, 2008
91
34
0
Antiguo Cuscatlán
There is considerable chatter around the web that google play services 6.5.87 is a battery hog. This is the version that I have. If someone does a fresh install, please note what version is in the ROM. This update could be our problem.
I´ll do a fresh install today and back tomorrow to report my results, but definitly is not room related.
 

Lopburi

Member
Jun 28, 2014
34
17
0
Let's test the Google apps theory, shall we? ;)
I'm going to uninstall all Google apps updates as soon as I got it charged again (drained from 80% to zero overnight again).
If that doesn't do it, I'll reflash this rom and will not update any apps.

I froze about everything with "Google" in it in TiBu, but interestingly enough Wakelock Detector shows Google Search still at the top of the list - even when frozen!!! I don't have enough background knowledge of Android to analyze this, but could it be that some service is still calling Google Search and that is causing it to show up in the wakelock list????

I leave the dock out of it for now. I have the massive battery drain even without docking the tablet at all. So I gotta find that problem first.
There is considerable chatter around the web that google play services 6.5.87 is a battery hog. This is the version that I have. If someone does a fresh install, please note what version is in the ROM. This update could be our problem.
I'm not sure about "google play service 6.5.87" causing the problem. I just flashed my unlocked tf701t with "[ROM][4.4.4][Unofficial] AOKP TF701T [06-27-1014][Nightlies]" and "pa-gapps-modular-full-4.4.4" updated everything and install all of my apps. When I start flashing the rom my battery was at 97% after I flashed the rom and let it idle for 3 hours battery drop 2% to 95%. The "google play service 6.5.87" installed. :confused:

PS. My locked tf701t with stock rom battery keep dropping about 10% to 15% per hour idling.
 
Last edited:

filou76

Senior Member
Jun 21, 2014
135
138
0
battery drain prob

same problem here. i've been using aokp latest build for some weeks now with gapps pico (i.e. only play services + play store). had a battery drain problem at the beginning, after some days of usage. after i deaktivated desktop clock app (which seemed to be responsible for many wake ups) everything worked perfekt again. now since a few days the tablet just doesn't stay in sleep mode, no matter what i tried: with/without dock, wifi on/off, closing all apps with taks manager. "android os" is eating all battery within a few ours. i'll go on testing ... one of us will find the reason!
 

asinglenoob

Senior Member
Oct 30, 2012
73
19
0
There is considerable chatter around the web that google play services 6.5.87 is a battery hog. This is the version that I have. If someone does a fresh install, please note what version is in the ROM. This update could be our problem.
I've been having this issue since long before more recent Play services updates. This has been a problem for me ever since Asus went from 4.3 to 4.4.2. I started off on Asus stock, and updated to their 4.4.2 build when it released but that is when the terrible idle drain started happening. I tried moving to Cyanogen Mod, using CROMi, and currently I'm on this build, nothing helps. I read somewhere the rebooting the tablet after using it would help with idle drain but that had maybe a 25% success rate. The drain always comes back. I tried turning off Google Now voice detection settings where were suggested over at CM thread which didn't help. Tried turning off WiFi during sleep, which also didn't help. Tried turning off all location services didn't help. As soon as I pull the tablet off the charger it stays awake and refuses to enter deep sleep. If I look at stats it's generally awake 99% of the time even when screen is off. Top offenders are usually Android OS, Google Play Services, Google Search, and some combination of other apps. During this time CPU usage can also be quite high (the back of the tablet is noticeably warm to the touch). I'm still not convinced that this isn't an issue with the kernel or drivers myself. I had issues like this on a phone previously and it turned out to be some combination of drivers for LED notifications and something to do with the kernel. Another reason why the Play Services idea seems unlikely to me is that I have the newest version on my phone (Moto G LTE) and have had no issues whatsoever with battery drain. I'm not a developer though so I may not know what I'm talking about here, this is just my thought process! I'm just getting fed up with this drain, it's even more frustrating because the tablet would be perfect if I could trust it to not drain to 0% when left in my bag for a few hours.
 

wolfymozart

Senior Member
Jul 10, 2010
54
10
0
I flashed 4 ROMs: Cromix-7, two stock ROMs deodexed and CM11. The battery drain problem is always there...
In idle mode, no wi-fi, no sync, nothing running, the back of the tablet is a bit warm...
 
Last edited:

Lopburi

Member
Jun 28, 2014
34
17
0
I flashed 4 ROMs: Cromix-7, two stock ROMs deodexed and CM11. The battery drain problem is always there...
In idle mode, no wi-fi, no sync, nothing running, the back of the tablet is a bit warm...
Yep...... Same here! yesterday I flashed AOKP rom with gapps, install all of my apps and updated everything available for the first 6 hours the battery only drained about 5%. Before I go to bed I play with it for about 30mins and it has 65% of battery left but after I woke up no more battery left. I think it has to be one of the google apps that causing the problem.
 

wolfymozart

Senior Member
Jul 10, 2010
54
10
0

buda5767

Senior Member
Mar 5, 2010
91
21
0
Google Play Version 6.5.99 and CM11 Nightly:
After 20-50 sucecess deepsleep, i have nvavp problem. after this error, no deepsleep anymore. Only reboot bring deepsleep back for short time.
I think is here not a wakelock problem really if deepsleep =0%

Please tell me, if you have the same error in Suspend_stats, if you lose deepsleep modus?
If deepSleep > 0% then we have a wakelock problem.
Thanks for you soupport.

/sys/kernel/debug/suspend_stats
success: 48 fail: 19453 failed_freeze: 5361 failed_prepare: 0 failed_suspend: 5361 failed_suspend_late: 0 failed_suspend_noirq: 0 failed_resume: 0 failed_resume_early: 0 failed_resume_noirq: 0 failures: last_failed_dev: nvavp nvavp last_failed_errno: -16 -16 last_failed_step: freeze suspend
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
0
Los Angeles, CA
Google Play Version 6.5.99 and CM11 Nightly:
After 20-50 sucecess deepsleep, i have nvavp problem. after this error, no deepsleep anymore. Only reboot bring deepsleep back for short time.
I think is here not a wakelock problem really if deepsleep =0%

Please tell me, if you have the same error in Suspend_stats, if you lose deepsleep modus?
If deepSleep > 0% then we have a wakelock problem.
Thanks for you soupport.

/sys/kernel/debug/suspend_stats
success: 48 fail: 19453 failed_freeze: 5361 failed_prepare: 0 failed_suspend: 5361 failed_suspend_late: 0 failed_suspend_noirq: 0 failed_resume: 0 failed_resume_early: 0 failed_resume_noirq: 0 failures: last_failed_dev: nvavp nvavp last_failed_errno: -16 -16 last_failed_step: freeze suspend
Did you delete or rename /system/vendor/lib/mediadrm?
That totally solved it for me and is related to the nvidia DRM module.

Unfortunately I did not pull the suspend_stats when I still had the drain, but here is what I got since then:

This is after using the Autostarts app to disable GP services autostarts after boot:

[email protected]:/ $ uptime
up time: 02:21:47, idle time: 00:16:28, sleep time: 02:01:30
[email protected]:/ $ cat /sys/kernel/debug/suspend_stats
cat /sys/kernel/debug/suspend_stats
success: 49
fail: 17
failed_freeze: 7
failed_prepare: 0
failed_suspend: 10
failed_suspend_late: 0
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_early: 0
failed_resume_noirq: 0
failures:
last_failed_dev: sdhci-tegra.0

last_failed_errno: -16
-16
last_failed_step: suspend
freeze



After deleting the mediadrm folder

[email protected]:/ $

C:\adb>adb shell
[email protected]:/ $ uptime
uptime
up time: 23:38:52, idle time: 01:35:17, sleep time: 21:58:07
[email protected]:/ $

[email protected]:/ $ cat /sys/kernel/debug/s
cat /sys/kernel/debug/suspend_stats
success: 357
fail: 107
failed_freeze: 42
failed_prepare: 0
failed_suspend: 64
failed_suspend_late: 0
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_early: 0
failed_resume_noirq: 0
failures:
last_failed_dev: alarmtimer
sdhci-tegra.0
last_failed_errno: -16
-16
last_failed_step: suspend
freeze
[email protected]:/ $



C:\adb>adb shell
[email protected]:/ $ uptime
uptime
up time: 10:14:25, idle time: 02:02:32, sleep time: 07:45:02
[email protected]:/ $ cat /sys/kernel/debug/suspend_stats
cat /sys/kernel/debug/suspend_stats
success: 160
fail: 58
failed_freeze: 26
failed_prepare: 0
failed_suspend: 32
failed_suspend_late: 0
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_early: 0
failed_resume_noirq: 0
failures:
last_failed_dev: alarmtimer
alarmtimer
last_failed_errno: -16
-16
last_failed_step: suspend
suspend




C:\adb>adb shell
[email protected]:/ $ uptime
uptime
up time: 12:18:45, idle time: 00:44:32, sleep time: 11:32:41
[email protected]:/ $ cat /sys/kernel/debug/suspend_stats
cat /sys/kernel/debug/suspend_stats
success: 234
fail: 131
failed_freeze: 69
failed_prepare: 0
failed_suspend: 61
failed_suspend_late: 0
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_early: 0
failed_resume_noirq: 0
failures:
last_failed_dev: alarmtimer
sdhci-tegra.0
last_failed_errno: -16
-16
last_failed_step: freeze
suspend
[email protected]:/ $


What strikes me in your results is the incredibly high number of "fails" compared to mine....

You know about the thread here, right? http://forum.xda-developers.com/showthread.php?t=2609964
That would be the best place to continue the conversation.
 
Last edited:

Morsure

Member
Aug 11, 2008
35
0
0
Hi,

Bluetooth doesn't work on my TF701T,

I'll try to activate it, it stays in grey and the button go back to off...

Do you have an idea?

Thanks