or do I just suck?
I've been flashing NBs ICS roms since the initial release and have been nothing but impressed at the development and overall quality; however, there's one thing that seems amiss. Generally, it seems that whenever the option to OC exists (which I assume is due to the kernel but I have the foggiest on how these things work), my phone refuses to go into deep sleep. I've always written this off as something wonky with the specific build and whatever crap I install afterwards. After all, it's still in the beta.
After flashing Beta v10 -which does not have OC by default- my phone had no problem going into deep sleep after all my apps were restored. After spending the day enjoying my ICS goodness, I decided to flash the new custom kernel mostly because I'm a sheep and will do whatever the rom dev tells me to do.
My phone now won't drop below 100Mhz; this is with the kernel change being the ONLY difference. I assume that this must be culprit. Excuse the short monitor time on my screenshot, it was taken after a "trouble-shooting" reboot.
I use the included 'CPUMaster' app to set the clock settings and I've run the diagnosis app but don't understand anything it displays.
Has anyone else experienced this and what should my next troubleshooting step be?
NB set the Rom to not go into Deep sleep while being charged.
So, after charging your phone, and unplugging, you need to reboot your phone
before it will be able to go into deep sleep.
Hopefully this helps.
Deep sleep problems for me too, rebooting doesn't always solve
I got the same issue as the above guy. I'm on 10.6 with eugene373's streamline kernel. The rom is awesome, but this issue is a pain on my battery. I notice at least once a day my battery starts dropping rapidly. I check cpuspy and sure enough i'm stuck at 100 mhz. Rebooting only solves the problem about half the time and even when it does after a few hours sometimes i get stuck at 100 mhz again. This happens later in the day as well, after unplugging from charger and a reboot or two. What is going on? Any suggestions as to how to find the culprit would be much appreciated.
Xenoism said:
NB set the Rom to not go into Deep sleep while being charged.
So, after charging your phone, and unplugging, you need to reboot your phone
before it will be able to go into deep sleep.
Hopefully this helps.
Click to expand...
Click to collapse
Is this a compile time flag? Or something that can be turn on/off some other way?
InstigatorX said:
Is this a compile time flag? Or something that can be turn on/off some other way?
Click to expand...
Click to collapse
I'm curious about this too
---------- Post added at 01:16 AM ---------- Previous post was at 01:10 AM ----------
Xenoism said:
NB set the Rom to not go into Deep sleep while being charged.
So, after charging your phone, and unplugging, you need to reboot your phone
before it will be able to go into deep sleep.
Hopefully this helps.
Click to expand...
Click to collapse
I tried this and deep sleep still wasn't available.
Use BetterBatteryStats to track down what is preventing deep sleep. I ended up turning off background updates for everything except gmail to get reliable deep sleep. Turning on GPS also caused problems. Can't use GPS right now anyway, since flashing Kiss 4.1 kernal. I'd rather have 911 than GPS.
Related
Hello,
After the latest OTA release (9.4.2.13) I am having the following issues:
- Putting tablet into sleep mode (unit on, screen turned off) with WiFi off causes
tablet to shut off after approx. 10-15 minutes. To turn tablet back on I have to hold the
power button in for approx. 10 seconds.
Before this update I NEVER had this problem. WiFi is set to always stay on in Settings.
This also occurs if I set to turn WiFi off when the screen if off (in Settings).
- The battery seems to be discharging much faster now. Before the update, the battery
would last approx. 7-8 hours under normal use (web surfing, email, etc). Now, I'm lucky if I get 5-6 hours.
I currently do not have any emperical evidence to back this up. It just
seems to be draining faster. I will check to see if an app or some process
may be causing this issue.
This latest update has really annoyed me given these issues. I had none
of the issues that this update is supposed to fix (lockups, reboots, Wifi problems).
Up to this point, I have really loved this tablet. Now, I think about its problems every time I use it.
Please fix these issues and give us a tool that will allow us to revert back to older firmware releases.
Thanks for listening.
-Paul
pmuch12345 said:
Hello,
After the latest OTA release (9.4.2.13) I am having the following issues:
- Putting tablet into sleep mode (unit on, screen turned off) with WiFi off causes
tablet to shut down. To turn tablet back on I have to hold the power button in for approx. 10 seconds. Before the update I NEVER had this problem. WiFi is set to always stay on in Settings.
l
Click to expand...
Click to collapse
So you have wifi off and the setting for wifi to always be on in settings and it locks up. If you turn wifi on does it not lock up? I tried to duplicate the problem but could not. I turned off wifi on settings and was able to sleep and power on the device without troubles. (For the record Bluetooth was also off.) I believe you are having a problem but do not think the root cause is what you suspect. Maybe it is a program you have installed that I do not or vice versa. If you can hook your tablet up to a computer and capture a logcat perhaps something will show up.
Alternatively is it maybe how long you let it sleep? I only left it off for the count of ten.
Sent from my Transformer Prime TF201 using Tapatalk
I turn Wifi off prior to putting tablet into sleep mode to save on battery power.
I have not tried to leave WiFi on while in sleep mode. I will try this.
It seems to me, whether WiFi is On or Off when putting the tablet
into sleep mode should not cause the tablet to turn off after a short period
of time.
I will have to test, but the tablet is in sleep mode for at least 10-15 minutes
when it shuts off.
BTW, I never had this issue prior to this OTA release. I would be really
surprised if an application is causing this issue.
Thanks
I'm not having this issue and never had it, just like the last post says it can be caused by some application, what if you guys share the list of installed apps with some app like App Dragon App Lister (free in the market) then you can find if there are something in common, Are your primes rooted? mine is not.
regards
After the OTA i get this problem that restart every 10-15 minutes. I has been happening it me and i have been blaming the dock but now i see is the OTA that has cause this problem. Come on Asus, u can do better than this.
Yep, there IS an issue.
Last use last night was at 11:45pm and I was at 67% and at 7:07 I was at 44%. 23% overnight and while in deep sleep AND I use Tasker to shut Sync and BT and Wifi off at 10:30 pm IF they are on and I never use IPS and I am usually in Power Savings mode, so you cannot blame it on these things. Not good!
Better Battery shows AlarmReceiver as highest battery user at a mere laughable 2.8%
BUT CPU Spy shows 5:35 time in 475 clock speed... And since no other apps are clelarly burning my battery... it must be this low end 475.
Thanks Asus for (1) taking back the 1400 you gave us (2) taking back lower end 102-375 speeds I would use (3) forcing us to sit at 475 when we could be lower (4) giving me a battery drain issue I never had. Thanks
Confirmed, I am experiencing the same issue. Had to cold boot wake up after routine sleep mode this morning. Note battery dropped 50% while unused.
Sent from my Transformer Prime TF201 using Tapatalk
If you want it to go to Gary, PM him.
---------- Post added at 05:43 PM ---------- Previous post was at 05:33 PM ----------
Lock-N-Load said:
Yep, there IS an issue.
Last use last night was at 11:45pm and I was at 67% and at 7:07 I was at 44%. 23% overnight and while in deep sleep AND I use Tasker to shut Sync and BT and Wifi off at 10:30 pm IF they are on and I never use IPS and I am usually in Power Savings mode, so you cannot blame it on these things. Not good!
Better Battery shows AlarmReceiver as highest battery user at a mere laughable 2.8%
BUT CPU Spy shows 5:35 time in 475 clock speed... And since no other apps are clelarly burning my battery... it must be this low end 475.
Thanks Asus for (1) taking back the 1400 you gave us (2) taking back lower end 102-375 speeds I would use (3) forcing us to sit at 475 when we could be lower (4) giving me a battery drain issue I never had. Thanks
Click to expand...
Click to collapse
Your post was on the right track until I read your last paragraph. So unnecessary. I like your perspective to be able to hold Asus accountable/responsible in making sure our primes work like we want it to -- but all your posts end up soiling the conversation, and it's not just one or two, its all of them. Help us out here...please
So does anyone know if there is a way to revert back to the .11 update? That seemed to work the best for everyone and it'd be great to just go back to a working update.
Just to pile on, I am also seeing battery usage and awake time when it should be sleeping where as before everything was fine.
Battery was 76% last night in balanced mode before i went to bed. Woke up this morning at 8am and battery is dead, Never had an issue before this new update
pmuch12345 said:
I turn Wifi off prior to putting tablet into sleep mode to save on battery power.
I have not tried to leave WiFi on while in sleep mode. I will try this.
It seems to me, whether WiFi is On or Off when putting the tablet
into sleep mode should not cause the tablet to turn off after a short period
of time.
I will have to test, but the tablet is in sleep mode for at least 10-15 minutes
when it shuts off.
BTW, I never had this issue prior to this OTA release. I would be really
surprised if an application is causing this issue.
Thanks
Click to expand...
Click to collapse
The battery savings may or may not be valid. I am not trying to judge on battery savings or use. What I am trying to do is narrow the scope of the lock problem and determine steps to reproduce the lock. This makes it easier to avoid the problem as a user and fix the problem as a developer. I am sure that it involves the OTA update. What I am suggesting is that, without the ability to reproduce it probably involves more than just the OTA update alone.
Does that make sense?
Sent from my Transformer Prime TF201 using Tapatalk
JanetPanic said:
What I am trying to do is narrow the scope of the lock problem and determine steps to reproduce the lock.
Click to expand...
Click to collapse
You've touched on the cruxt of the issue. It appears that not all Prime's behave the same way. Prime's that were fine before the update are broken and those that were broken now work. Since the h/w's all the same, it really is a curious issue.
pmuch12345 said:
Hello,
After the latest OTA release (9.4.2.13) I am having the following issues:
- Putting tablet into sleep mode (unit on, screen turned off) with WiFi off causes
tablet to shut off after approx. 10-15 minutes. To turn tablet back on I have to hold the
power button in for approx. 10 seconds.
Before this update I NEVER had this problem. WiFi is set to always stay on in Settings.
...
-Paul
Click to expand...
Click to collapse
I have this same behavior only after a minute of manually or auto-timeout screen off.
* No problems with .11
* Installed OTA update, lockup in sleep mode started
* Uninstalled Flash and Dolphin Browser JIC, problem remained
* It is a lock up not power down. Have to hold power button 10 sec
* I can wake with power button within a minute or so
* Wifi on or off
* If I force screen to never shutoff it stays working fine as it never goes to sleep
* If I manually power down, it will power up normally
-Robert
Rather than making us wait a month for another "fix," Asus should do the right thing and give those of us who had no problems on the old FW a way to revert back. This is bogus.
Lock-N-Load said:
Thanks Asus for (1) taking back the 1400 you gave us (2) taking back lower end 102-375 speeds I would use (3) forcing us to sit at 475 when we could be lower (4) giving me a battery drain issue I never had. Thanks
Click to expand...
Click to collapse
Do you think there could be inconsistencies in the SoC? Teg3 was delayed and people were speculating that it was due to fabrication issues. It's an extremely complex design and it's odd that some devices experience issues when others don't. It could be other h/w that's inconsistent but there's nothing earth shatteringly different in the Prime other than the SoC. Just something to think about...
I can confirm lockups and reduced battery life after the update though I do not have any solid information to say what is causing it. Prior to the update I could go most of my day at work using the tablet very mildly and get home with 80% or so. Now I'm home for lunch and I'm sitting at 70% with 5 hours left in my work day. I've also experienced two lockups today and have to hold the power button for 10-15 seconds before it will boot up. I'm not incredibly worried about it, I feel like these issues will be ironed out more easily than wifi and gps issues. ; )
Sent from my Transformer Prime TF201 using Tapatalk
BarryH_GEG said:
Do you think there could be inconsistencies in the SoC? Teg3 was delayed and people were speculating that it was due to fabrication issues. It's an extremely complex design and it's odd that some devices experience issues when others don't. It could be other h/w that's inconsistent but there's nothing earth shatteringly different in the Prime other than the SoC. Just something to think about...
Click to expand...
Click to collapse
I agree, I think alot of these issues (aside from backlight bleed and GPS) have a direct correlation to Tegra3. I think the market has something to say about that too though -- how many other Tegra 3 tablets are there? When is the next non-Asus tegra 3 tab coming out? Not until May/June...
Honestly, I don't think Tegra3 does too well with CPU frequency stages. Then you have ICS on top, which is new as well. The combination could be disastrous. I'm not surprised there is issues, Asus is doing a good job staying afloat though.
Other OEMs are looking at how Asus is proceeding with this and are learning. But Asus has the advantage. They have the closest relationship with nvidia than anyone else does (I'm speculating) and thus is brings them closer to the Apple model, where control is maintained throughout all the levels of the tablet experience (App ecosystem, OEM, SoC)
Agreed, how to revert back to working binaries!
BarryH_GEG said:
You've touched on the cruxt of the issue. It appears that not all Prime's behave the same way. Prime's that were fine before the update are broken and those that were broken now work. Since the h/w's all the same, it really is a curious issue.
Click to expand...
Click to collapse
This not completely true statement. Gary already explained exactly what the update did. Raising the lower clock doped doesn't mean a broken prime...lol. my prime still works just fine after update. Yes, some are experiencing issues after update but not all. So to assume all that were fine before update are now broken is incorrect.
Hello All!
I am running the latest CM10 Jelly Bean ROM ( 8/21 nightly) and really like it for the most part - seems to be smooth, no major issues (well, keep reading), installed easily enough etc. I am pretty experienced with Android and flashing, etc.
I've had a problem that started with the ROM..my phone shuts off completely when it's charging and reaches a full charge. It's happened a couple of times. And yes, it IS charging, it's not the battery running low. lol. I reflash an ICS ROM and the problem goes away.
Any ideas?
witwolf said:
Hello All!
I am running the latest CM10 Jelly Bean ROM ( 8/21 nightly) and really like it for the most part - seems to be smooth, no major issues (well, keep reading), installed easily enough etc. I am pretty experienced with Android and flashing, etc.
I've had a problem that started with the ROM..my phone shuts off completely when it's charging and reaches a full charge. It's happened a couple of times. And yes, it IS charging, it's not the battery running low. lol. I reflash an ICS ROM and the problem goes away.
Any ideas?
Click to expand...
Click to collapse
What kernel are you running? Is it the stock kernel or did you flash devil kernel? If you flashed devil, did you modify any of the settings with the devil control app? If you did not install devil and are running with their default kernel, have you changed the settings at all? Have you UVed at all? OCed?
Also, is it really turned off completely? Like, the whole green battery charging symbol...or is it a SOD? If it's a SOD, it could likely be a kernel thing, which is why I asked all those kernel related questions ^^...although in hindsight, I should have probably asked this first, and then moved to asking about the kernel lol
Xenoism said:
What kernel are you running? Is it the stock kernel or did you flash devil kernel? If you flashed devil, did you modify any of the settings with the devil control app? If you did not install devil and are running with their default kernel, have you changed the settings at all? Have you UVed at all? OCed?
Also, is it really turned off completely? Like, the whole green battery charging symbol...or is it a SOD? If it's a SOD, it could likely be a kernel thing, which is why I asked all those kernel related questions ^^...although in hindsight, I should have probably asked this first, and then moved to asking about the kernel lol
Click to expand...
Click to collapse
Hello Xenoism!
Thank you so much for the reply. And shame on me for not giving you all of the information! I should know better! LOL.
So to answer your second question first, it turned off completely. When I press the power button, it switches on, boots up and shows a fully charged battery.
I've also noticed that the CHARGE indicator is not working...it does not show when my phone is charging (the icon in the notification bar).
I AM using the Devil kernel (1.2.1 I believe it is) as is, without any modifications except I OC to 1.3 or 1.4GHz. I've made no changes to the Voltages.
I suppose if I just reflash without DEVIL I can see if the problem continues. That really should have been my first step, right?
Again, thank you!!!
witwolf said:
Hello Xenoism!
Thank you so much for the reply. And shame on me for not giving you all of the information! I should know better! LOL.
So to answer your second question first, it turned off completely. When I press the power button, it switches on, boots up and shows a fully charged battery.
I've also noticed that the CHARGE indicator is not working...it does not show when my phone is charging (the icon in the notification bar).
I AM using the Devil kernel (1.2.1 I believe it is) as is, without any modifications except I OC to 1.3 or 1.4GHz. I've made no changes to the Voltages.
I suppose if I just reflash without DEVIL I can see if the problem continues. That really should have been my first step, right?
Again, thank you!!!
Click to expand...
Click to collapse
No problem at all, just trying to help ^^;
Trying out the stock kernel might be best, since from my experience things like this tend to be the result of some kernel related issue. If you're certain its not a sleep of death (which can be easily mistaken as the device being off, since the phone will appear off and you will need to hold the power button in order for the phone to reboot), and you haven't undervolted at all, then the answer becomes a tad more tricky. Off the top of my head, I might suggest downloading "Cpu Spy" from the market for free, and checking to see while charging what frequency your phone likes to stick around at....if for some reason the phone is staying higher than 100, it may be simply the result of it overheating overnight while charging which causes it to turn off. ^^
Make sure you do not have deep idle selected! I had the same issue. I also have an issue with charging icon (not status bar though). When phone is off and charging the battery icon doesn't turn green and show charge level, however it is charging. It doesn't effect performance at all so no worries.
Running helly 0817 with latest devil kernel.
Its peanut butter jelly(bean) time...
It is possible that because of your high overclocking, when the battery becomes high, the phone's voltage gets messed up our something and your phone shuts off.
Xenoism said:
No problem at all, just trying to help ^^;
Trying out the stock kernel might be best, since from my experience things like this tend to be the result of some kernel related issue. If you're certain its not a sleep of death (which can be easily mistaken as the device being off, since the phone will appear off and you will need to hold the power button in order for the phone to reboot), and you haven't undervolted at all, then the answer becomes a tad more tricky. Off the top of my head, I might suggest downloading "Cpu Spy" from the market for free, and checking to see while charging what frequency your phone likes to stick around at....if for some reason the phone is staying higher than 100, it may be simply the result of it overheating overnight while charging which causes it to turn off. ^^
Click to expand...
Click to collapse
Thank you for the great reply and usefull information. I actually left my phone at my sister's the other day and she lives in another city, lol, and am using a temporary replacement so I haven't had a chance to investigate further. But once I get the phone back I'll look into the Cpu Spy and also using the default kernel.
Again, thank you!
samsgun357 said:
Make sure you do not have deep idle selected! I had the same issue. I also have an issue with charging icon (not status bar though). When phone is off and charging the battery icon doesn't turn green and show charge level, however it is charging. It doesn't effect performance at all so no worries.
Running helly 0817 with latest devil kernel.
Its peanut butter jelly(bean) time...
Click to expand...
Click to collapse
Thanks for the feedback!
As I mentioned in an earlier reply, I left my phone in another city so I'll have to wait to get it back to check it out and look into the deep sleep issue...I appreciate the help and ideas!!!
K
I've had my phone for a few months now and up until recently it had no issues. It's unlocked but not s-off and I had been running cyanogenmod 10.1. When the 10.2 nightlies came out I began using them and until around 9/15 these worked great. I didn't suffer from the flickering or radio issues at all. Around that time I started noticing that my phone would occasionally shut off on its own. I thought that it was an overheating issue at first but as the problem worsened it became clear that it would happen cold. It's now at the point where it predictably happens within a minute of the phone being on, leaving the phone essentially useless. I've tried narrowing the CPU frequency range and going back to the stock ROM, neither of which has resolved the problem. Investigating logcat and bugreport didn't reveal any hints to me as to what was happening. I'm worried that it's a hardware issue but recovery and bootloader seem to be able to stay on indefinitely which gives me some hope. Does anybody have some input on additional things that I could try?
Start simple... Battery good? Battery contacts good?
j13smiley said:
Start simple... Battery good? Battery contacts good?
Click to expand...
Click to collapse
Yeah, I'm fairly sure that it's not a battery issue. The same thing happens when it's plugged into a charger and the phone will stay on in recovery regardless of me moving it around or letting it sit for long periods of time.
I have noticed something new though. If I don't enter my Google account information (doing so starts app syncing) then the phone is much more stable. It seems that I can do a simple task like turning on wireless tethering and then if I don't do anything else the phone will be stay on for hours. If I open the browser, the play store, or start moving icons around then I only have a minute or two before it will shutdown.
Removed
foobster said:
Yeah, I'm fairly sure that it's not a battery issue. The same thing happens when it's plugged into a charger and the phone will stay on in recovery regardless of me moving it around or letting it sit for long periods of time.
I have noticed something new though. If I don't enter my Google account information (doing so starts app syncing) then the phone is much more stable. It seems that I can do a simple task like turning on wireless tethering and then if I don't do anything else the phone will be stay on for hours. If I open the browser, the play store, or start moving icons around then I only have a minute or two before it will shutdown.
Click to expand...
Click to collapse
Updating to a newer 10.2 nightly might fix the problem. Otherwise get the last_kmsg file when it shuts down next time and post it here. Someone might be able to diagnose the problem.
durgis said:
Updating to a newer 10.2 nightly might fix the problem. Otherwise get the last_kmsg file when it shuts down next time and post it here. Someone might be able to diagnose the problem.
Click to expand...
Click to collapse
Thanks for the input. I'll give a newer 10.2 nightly a shot but I am seeing the issue on builds that had previously worked fine (stock and 10.1). I have no /proc/last_kmsg after an unplanned shutdown. Based on what I'm reading this might mean that it's locking up before there's a kernel panic?
two options
j13smiley said:
Start simple... Battery good? Battery contacts good?
Click to expand...
Click to collapse
Flexcard usb or your mainmotherboard is or going out
Hi guys. While i was sleeping and my phone was just waiting on my desk, it magically went to %35 battery, and since this is clearly a failure to deep sleep, i've used betterbatterystats to diagnose the problem. It's probably not because of apps because i've been using these apps for a long time and i've uninstalled the short-term ones. Now as far as i know vbus is the usb part, might be a damaged port from bad charging, and nlpwakelock is googleservices? As you can see from processor times, its never on deep sleep but always on 300-600 mhz, something is not making it sleep and what im asking is for someone to make a connection between these (because i have no idea). Otherwise, ill just wipe it and see if my usb board is faulty.
Dakura said:
Hi guys. While i was sleeping and my phone was just waiting on my desk, it magically went to %35 battery, and since this is clearly a failure to deep sleep, i've used betterbatterystats to diagnose the problem. It's probably not because of apps because i've been using these apps for a long time and i've uninstalled the short-term ones. Now as far as i know vbus is the usb part, might be a damaged port from bad charging, and nlpwakelock is googleservices? As you can see from processor times, its never on deep sleep but always on 300-600 mhz, something is not making it sleep and what im asking is for someone to make a connection between these (because i have no idea). Otherwise, ill just wipe it and see if my usb board is faulty.
Click to expand...
Click to collapse
yes nlpwakeckocks is google service location, deactivate location of g+ and restart.
the phone was not charging?
Nope, it wasn't charging,i deliberately didn't charge it in order to see what the problem is. Ok, ill try.
Hmm, still couldn't test enough, even tho the battery life is better, i still think there is a problem with deep sleeping. Ill try updating to todays nightly for today.
If you are using a custom rom i suggest clean install instead of updating the nightly, it may keep the same problem.
Dakura said:
Hmm, still couldn't test enough, even tho the battery life is better, i still think there is a problem with deep sleeping. Ill try updating to todays nightly for today.
Click to expand...
Click to collapse
Try a diff 'Kernel' and see if it resolves ur issue
Sun90 said:
Try a diff 'Kernel' and see if it resolves ur issue
Click to expand...
Click to collapse
Different kernel and rom didn't work. But i remembered that i've used my friends charger (who has a S3) sometime before, that might did something to my board. Got no guarantee but i guess i need to find a repair shop..
Hey everyone. i've had my nexus 9 for a long time now but every now and then i get a few issues with the battery for some reason and i cant find a solution that works tbh.
Right now i'm running android nougat 7.0 and the thing has been great so far but just today i realized that the battery had been draining while i was asleep.
This has been happening before android N as well, on marshmellow. at one point i even had to roll back an OTA update because my battery would drain while the tablet was idle over the course of only 4 hours.
So.. after i rolled back to the more stable version of marshmellow, that stopped happening.
but yea. now i have a similar problem on android N. i just dont understand why this is happening and its super frustrating. before i installed android N i wiped my entire tablet completely clean before i flashed it.
i knowww, its kind of a first world problem. it doesnt happen all the time but when it does its super annoying.
does anyone know what i can do to prevent this from happening? i have set it to disable wifi when screen is off so.. its not downloading or updating apps or anything.. and disabled double tap to wake.. the tablet is basically just lying still on a table all night so dont understand how it can be draining the battery at all.
thanks
sorry, since im new here i cant actually post an image yet or a link to the image.. but basically, android system and android OS is taking up huge chunks of the battery and if i look at graph i can see that my tablet was
"awake" for multiple hours even though the screen was off while i was asleep.
you could try better battery stats, there's a thread here at xda for it, see what's going on with it. I haven't noticed so far but it's only been a day. You may wanna just let it go for a few days and let the system settle, let your cache build, etc....and if you're rooted there's kernels available the you could try out and make some adjustments depending on how you use your tab. Good luck :good:
damngood98 said:
you could try better battery stats, there's a thread here at xda for it, see what's going on with it. I haven't noticed so far but it's only been a day. You may wanna just let it go for a few days and let the system settle, let your cache build, etc....and if you're rooted there's kernels available the you could try out and make some adjustments depending on how you use your tab. Good luck :good:
Click to expand...
Click to collapse
Thanks for the reply. im gonna consider if betterbatterystats if it doesnt stop draining within a day or two. i need my tablet to function properly by monday.
Last night the exact same thing happened. although this was was even worse i think. theres a tiny little snippet of "screen on" time in the battery data menu. and then it shows the long bar of " awake" throughout the entire night. and apparently this is because of android system and android OS.
it literally drained from 91 % to 36 % over the course of the night... completely unbelievable.
Try disabling all account synching, turning all location settings off, and restarting in Safe Mode. This will limit your device to just the OS and gapps. If you're still getting the battery drain, it's most likely a gapps issue. Unfortunately, I don't know an effective way to remove and replace the built-in gapps in the stock rom.
Elina39 said:
Hey everyone. i've had my nexus 9 for a long time now but every now and then i get a few issues with the battery for some reason and i cant find a solution that works tbh.
Right now i'm running android nougat 7.0 and the thing has been great so far but just today i realized that the battery had been draining while i was asleep.
This has been happening before android N as well, on marshmellow. at one point i even had to roll back an OTA update because my battery would drain while the tablet was idle over the course of only 4 hours.
So.. after i rolled back to the more stable version of marshmellow, that stopped happening.
but yea. now i have a similar problem on android N. i just dont understand why this is happening and its super frustrating. before i installed android N i wiped my entire tablet completely clean before i flashed it.
i knowww, its kind of a first world problem. it doesnt happen all the time but when it does its super annoying.
does anyone know what i can do to prevent this from happening? i have set it to disable wifi when screen is off so.. its not downloading or updating apps or anything.. and disabled double tap to wake.. the tablet is basically just lying still on a table all night so dont understand how it can be draining the battery at all.
thanks
sorry, since im new here i cant actually post an image yet or a link to the image.. but basically, android system and android OS is taking up huge chunks of the battery and if i look at graph i can see that my tablet was
"awake" for multiple hours even though the screen was off while i was asleep.
Click to expand...
Click to collapse
I've been running marshmallow since day 1 and 7.0 developer preview since day 1 as well. I am typically getting ~4 & 1/2 hours of screen on time with ~30% battery left (not rooted, nothing). If the Google apps aren't the problem, the problem may be with the battery itself where it itself is faulty and needs replacing. A good thing with replacing the battery is that it's fairly easy to do unless you accidentally ripped out the camera with it. If you were to rip out the camera by removing the back cover, then that would definitely be a problem. Memory leak in any of your non-Google apps?
Hey everyone. i think i might have found the reason why my battery is draining sometimes. lately it's been doing fine as it's rather easy to fix.
My theory is that if you put yiur tablet with the screen facing down on a table or something, it may trigger the touch input, even with the screen being off. So it's using some battery cus it thinks you're touching the screen so it has to be ready since.. if someone is touching the screen they would usually turn the device on.. but idk.
it just seems as though the battery drains whenever i put it with screen facing down.
Elina39 said:
Hey everyone. i've had my nexus 9 for a long time now but every now and then i get a few issues with the battery for some reason and i cant find a solution that works tbh.
Right now i'm running android nougat 7.0 and the thing has been great so far but just today i realized that the battery had been draining while i was asleep.
This has been happening before android N as well, on marshmellow. at one point i even had to roll back an OTA update because my battery would drain while the tablet was idle over the course of only 4 hours.
So.. after i rolled back to the more stable version of marshmellow, that stopped happening.
but yea. now i have a similar problem on android N. i just dont understand why this is happening and its super frustrating. before i installed android N i wiped my entire tablet completely clean before i flashed it.
i knowww, its kind of a first world problem. it doesnt happen all the time but when it does its super annoying.
does anyone know what i can do to prevent this from happening? i have set it to disable wifi when screen is off so.. its not downloading or updating apps or anything.. and disabled double tap to wake.. the tablet is basically just lying still on a table all night so dont understand how it can be draining the battery at all.
thanks
sorry, since im new here i cant actually post an image yet or a link to the image.. but basically, android system and android OS is taking up huge chunks of the battery and if i look at graph i can see that my tablet was
"awake" for multiple hours even though the screen was off while i was asleep.
Click to expand...
Click to collapse
Hey, there is a possibility that there is a 3rd party (non pre-installed) app that has been causing your N9 not to sleep. This is easy to test for. Just boot your Nexus 9 into safe mode the next time you are going to set it down for a while. This will disable all 3rd party apps. If it was a 3rd party app that was waking your device and draining battery, safe mode should prevent it from doing so. The hard part after that is determining which app is the culprit. Trial and error is the only method, uninstalling 3rd party apps one by one until the problem is fixed.
To boot into safe mode, hit your power button, then touch and hold the power off prompt on your screen. You will then be prompted to restart in safe mode.
Elina39 said:
it just seems as though the battery drains whenever i put it with screen facing down.
Click to expand...
Click to collapse
FYI - Custom ROMs/Kernels allow you to disable Double Tap To Wake /Swip To Wake. So, if this problem really bothers you, that's one way to fix it.