Related
I had problems which corrupted the title bar of my Ameo (UK, T-Mobile) after about 8 - 10 hours. I can't exactly pin down what caused it, but when I disabled Batti and removed it from my Startup folder the problems totally disappeared.
I'm using WM6 Project Black 2.0 as downloaded.
Has anyone else experienced such problems?
Yes, I am on Tmobile in the UK, and am running the project black 2.0 rom.
I have to reset my phone each morning to get it working on this rom, and at about 4-6pm i get a corrupted title bar which requires another reset.
I havent looked into the problem yet, but will try removing Batti and see what happens
I also suffer from very heavy battery drain with this rom, I took my phone off charge at 10am this morning, and it is now down to 10% and giving me warnings about charging it, I have tried running it right down till it turns off after 10 seconds, then charged it up overnight without turning it on, but this didnt help at all
I do still like the new rom, and wont be going back to WM5, but these 2 problems are a little annoying on a daily basis
Let me know if disabling Batti from start up fixes the issue of the title bar. I experience a similar issue and am working on isolating it myself. It doesn't happen daily on mine but too often nevertheless. I finally have time to troubleshoot so I'll try to post my results as soon as i find some. I'm going to test Batti first based on this info and see if that fixes the issue. I also noticed that sometimes when the bar does that, some other areas of the screen freak out and sometimes the device locks up. We'll see. Thnx for the post.
I'm creating a new thread as I can't find any with an issue like this .
The problem rised durimg my latest holidays. I believe it was someaway related to exposing my S2 to sun heat (I used it as a GPS nav in the windshield of my car).
One day I found it in a bootloop (Samsung Galaxy Logo). I was not doing anything unusual (like writing a ROM or fiddling with it).
Removing the battery and then putting it back didn't fix the issue.
Luckily, I could enter recovery mode and restore a nandroid backup, after that everything was working fine again.
Unfortunately the next day it happened again. Same synthoms, same solution, fine back again.
In the following days unfortunately the problem continued to happen. It appeared randomly, apparently not related to what I was doing with the phone.
I was attributing the problem to an hw failure, so I was planning to replace the phone (or have it repaired).
To make a long story short, I tracked down the issue to the battery.
When the phone was in the bootloop, one of the things I tried was to replace the battery with a spare one I have, with no results.
But later I found that inserting the spare battery, restoring the nandroid and leaving the spare battery in without replacing it with the original one, stopped the issue to happen. The phone worked okay for a week or so, but when I replaced the spare battery with the original one, immediate bootloop!
So I'm reasonably sure that the problem is due to the buttery, but, honestly I really can't understand why, by simply replacing the battery with the spare one, doesn't fix the problem by itself (without requiring the nandroid restore).
It looks like the bad battery is causing a change in the system that make it unbootable even if you replace the battery with a good one. This doesn't make much sense, to me...
Do anyone have a clue of what is happening here? Enybody with similar issues?
TIA
alcal60 said:
I'm creating a new thread as I can't find any with an issue like this .
The problem rised durimg my latest holidays. I believe it was someaway related to exposing my S2 to sun heat (I used it as a GPS nav in the windshield of my car).
One day I found it in a bootloop (Samsung Galaxy Logo). I was not doing anything unusual (like writing a ROM or fiddling with it).
Removing the battery and then putting it back didn't fix the issue.
Luckily, I could enter recovery mode and restore a nandroid backup, after that everything was working fine again.
Unfortunately the next day it happened again. Same synthoms, same solution, fine back again.
In the following days unfortunately the problem continued to happen. It appeared randomly, apparently not related to what I was doing with the phone.
I was attributing the problem to an hw failure, so I was planning to replace the phone (or have it repaired).
To make a long story short, I tracked down the issue to the battery.
When the phone was in the bootloop, one of the things I tried was to replace the battery with a spare one I have, with no results.
But later I found that inserting the spare battery, restoring the nandroid and leaving the spare battery in without replacing it with the original one, stopped the issue to happen. The phone worked okay for a week or so, but when I replaced the spare battery with the original one, immediate bootloop!
So I'm reasonably sure that the problem is due to the buttery, but, honestly I really can't understand why, by simply replacing the battery with the spare one, doesn't fix the problem by itself (without requiring the nandroid restore).
It looks like the bad battery is causing a change in the system that make it unbootable even if you replace the battery with a good one. This doesn't make much sense, to me...
Do anyone have a clue of what is happening here? Enybody with similar issues?
TIA
Click to expand...
Click to collapse
If you have never changed the original battery in 2 years,it is normal that it will fail at a moment. Get a new one from ebay for 5$
GamingDj said:
If you have never changed the original battery in 2 years,it is normal that it will fail at a moment. Get a new one from ebay for 5$
Click to expand...
Click to collapse
Sorry if I didn't make my point clear enough. The failure of a battery is nothing to write about.
If you have a bad battery that is causing a bootloop for some reason, you expect that by replacing the bad battery with a good one, you should be able to boot again. This is not the case for me, this is the reason I'm curious about this.
Hi guys! I'm new around here, I've been lurking the forums for the past year or 2.
I originally had a i9000. Had it rooted, flashed & running 4.2.2 Hellybean, it was a dream, easiest android phone i've ever dealt with.
Today, I bring you a device that is so mind boggling and mysterious, it's ridiculous. Before you ask, yes I've searched and searched countless hours on end & sleepless nights. Trying to work out how to PERMANENTLY fix this device.
Straight up, I'm going to tell you what I've done, what I've tried, where the phone came from, model of the phone & all the useless stuff.
OKAY. Go.
I got the Samsung Galaxy S2 (i9100T) off a friend recently, about a month or two back. He didn't have a back cover for it, and the camera was all smashed up (back camera). It was running on 4.1.2 Vodaphone Stock DVLSH. It had a few issues when the phone got to me.
I wasn't sure if the phones battery was depleted, but I had to muck around with the phone for a couple of hours just to get the damned thing to turn on.
When I had got the phone to turn on, I kept getting "Warning! Battery Disconnected!" messages, this was frustrating. I eventually let the phone fully charged before I mucked around with it and ignored the warning.
When it was fully charged, I went straight to rooting it. I first rooted it by flashing CF-Root and then flashed a custom rom. (Xylon AOKP. 4.2.2)
From here on, the phone started to randomly restart, drop signal, lose battery after random restarts, get semi boot loops.
So I flashed a different stock (XWPL8) and got rid of the Samsung Galaxy SII i9100T boot logo and it was changed to Samsung Galaxy SII i9100.
After this, I then again rooted the phone but this time a different method and used Siyah kernel and flashed Carbon rom 4.2.2.
I still encountered the same problem as Xylon 4.2.2.
So I kept reverting back to stock, re-rooting & trying again.
I've tried countless methods.
POSSIBLE HARDBRICK RECOVERY DON'T TAKE MY WORD THOUGH: I've even managed to HardBrick the device (yes I mean hardbrick, i didn't even JTAG to bring it back... I flashed Dorimax Kernel at some point and it hardbricked it to all ****.) I spent a few days trying to unbrick it when finally I just plugged it into the charged and forced it to internally turn on (i believe) and let the battery deplete (the phone was hot even when i unplugged it. So I let the battery drain.) Yes I even battery pulled and tried to reboot it to see if I could boot recovery or download or the rom even before I tried any of this! (absolutely nothing.)
I took out my SIM card after a full day of letting it drain (just to be sure) plugged it in, took out the battery while the charger was plugged in, put the battery back in, unplugged the charger while holding power, and plugged it back in and I got the charging logo booted into download mode after 80% charge and flashed stock again.
Now the problem(s) with the phone:
SEMI-BOOTLOOPS: Every time i've rooted the phone and even flashed different roms just to make sure, it does a "semi boot-loop" I've searched everywhere for people with the same problem but found nothing on it.
What it does, is it turns on (boots the samsung logo.) turns off, turns back on, turns off, turns back on etc and then after about 2-8 times of doing is usually it boots to the ROM and the phone works for awhile.
RANDOM REBOOTS: I don't get these much anymore since I found a solution where someone had just folded up a receipt and pushed the battery up against the prongs because it had about .5mm movement off the prongs. This fixed most of the random reboots and don't see many anymore.
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?: This one I'm not 100% sure what it is, I read it's the S.O.D (Sleep of Death). Which is common on 4.0.4 and was apparently fixed in later Android versions. But sometimes, when I lock my phone, or my phone goes to sleep, the screen stays black even after I press the home button or the power button, at first I thought just restart it by battery pull or holding down power like everyone says, yeah it works, my phone boots up and does a semi-bootloop and goes back on eventually, but one day I left it on in the mysterious S.O.D. and waited 5-10 mins pressed the power button and it unlocked... This one really has me baffled and it does it a LOT.
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!: Okay, so sometimes when the phone finally turns on, the screen is really bright, like the brightness is still on half, but it's a lot more noticeable on how much brighter it is, it's nearly like a white.
It's really really BRIGHT. Phone shouldn't be able to look/get that bright. After a reboot though it goes away and goes back to normal but this leads me to believe something to do with the battery just a hunch.
RANDOM FREEZES!??!?: Sometimes the phone will just randomly freeze, I can be doing something and it'll just freeze, it won't turn off, I still get picture on the screen but it's frozen and I can't do anything until I either battery pull or reboot it by holding down the power button.
Before anyone asks, yes, I Factory Reset from recovery, Wipe Cache & Dalvik Cache before, I flash a new rom etc.
- My GApps matches with my Android versions each time.
- The ROMs I have flashed are compatible with my phone.
- And I've made sure everything I have done is completely compatible with my phone and android version.
What I think!:
SEMI BOOT-LOOPS:
This one, I don't think much of, it's got me baffled. It could be something to do with the Boot-Loader, could be something to do with a bad flash (but I've even tried double flashing a single rom.)
the eMMC could be damaged in a certain way that it causes these self proclaimed "semi boot-loops"
RANDOM REBOOTS:
This one, I've pretty much fixed with the help of lurking the internet over and over for hours, so this indicates a battery problem, will be replacing it this week. (Yes I'm aware that this battery problem could be causing everything else to play up and that it could all be due to the battery but can we leave the battery out of this just for now so I have more options on how to fix it.)
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?:
I believe that this could be due to either a high load on the CPU (maybe not so much high but a really low load that it goes into a state of nothing for awhile.) It drops into a mode where it's turned off (something bigger than deep-idle.)
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!:
I haven't changed voltages or messed with any voltages on my phone, but I believe that it does indeed have something to do with the CPU & GPU voltages or even the BATTERY Voltages either undervolting or being to high.
RANDOM FREEZES!??!?:
I think this one is something to do with my phone not liking the voltages stock set to it.
I read that somewhere Freezing the System Alarm Clock can fix the random reboots, so I've done that and also pushed the battery up with a bit of receipt so it touches the prongs completely.
Anyway, right now, the phone is on Stock Kernel with CWM Recovery6, with PacMan's 4.3.1 Nightly release on XWLP8 Baseband and it still does this all.
I know i'm asking for a lot of help and I'm probably going to get yelled at by Devs or forum mods or some body because I've done something wrong.
But if it doesn't belong here, move it please.
IT TRULY IS A PHONE FROM HELL.
-Thanks, Just another man who wants to fix silly problems for fun.
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Hey guys thanks for the speedy replies! I love waking up to instant replies!
theunderling said:
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Click to expand...
Click to collapse
Sorry, I was half asleep when writing all this! I am getting a new battery this week! But I wanted to have a go at trouble shooting it but crossing out the battery from the list of problems seeing as it's being replaced this week @theunderling
MistahBungle said:
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
Click to expand...
Click to collapse
It may sound like it @MistahBungle but I have faith and I come down to being very patient with technology even when I do reach ticking time bomb mode. I believe I can fix it if I just get the right help !
If the new battery doesn't do anything, It might be the logic board and i'll just go buy a new one.
Jimsilver73 said:
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Click to expand...
Click to collapse
@Jimsilver73 It really is!
I'm not the most wealthy person or have money to just throw at things like new phones etc etc. I'd love to see what I can do on my side and try and trouble shoot every problem for even the simpilest of DIY Solutions. I get a kick out of mucking with phones and computers.
Your probably right, but I was thinking that does Dori kernel keep stock voltages or does it change the voltages at all? Because it just managed to Hardbrick its self a few hours after flashing it which was odd, which led me to suspect that my phone didn't like the Dori Kernel & Carbon Rom Combination!
@theunderling I will try that Hawkers script by the way!
Is this the one? http://forum.xda-developers.com/showthread.php?t=2100558
Phone having no back cover and camera smashed suggests that there is a physical damage to the phone, i wouldn't even try battery to this one, it may just kill the new battery if there is some kind of water damage, tho you seem like having fun trying to repair it Yes, that's hawkers script, use it and couple of ROMs, (ICS,GB etc) to see if there is a software problem. If you can dissamble it, you can check if there are some contact problems between pieces.
Hi @Dakura thanks for the reply!
The camera isn't smashed completely, but at fist I thought that the camera would be screwing up the phone in someway.
I know for sure as well that there is no water damage, and the phone was just sitting around he lost the back cover randomly after he had bought an iPhone 4S.
I can disassemble it, I just need to find my little screw driver I use for stand-off changing on PC cases.
I read somewhere that the proximity sensor has a bit to do with things, so seeing as the back cover isn't on, that maybe dust got into it while it was in his draw and that's the reason for screen-offs? because the phone is still responsive. I can receive calls & text messages just the screen is black and doesn't come back on.
The warning in 4.0.4 "Warning! Battery Disconnected!" leads me to think that in versions above 4.0.4 (4.1.2 for example) don't have warnings and the phone just turns off.
**major update**
@Dakura @theunderling @Jimsilver73 @MistahBungle
Hey guys, so I've just taken the back CASING not the cover. Off the phone.
I've been looking for breaks in solder points on the Logic Board and around it.
- The Camera ISN'T smashed it was the lens on the case..
- Looks a tad dusty.
- Semi Boot-Loops have disappeared! booted the phone with the case off and the semi boot loops are gone tried booting multiple times each time with success!
- No breaks on the logic board from what I can see as far!
- For some reason the Camera app would not connect to the Camera. "Can't connect to Camera!" maybe the camera flex cable isn't in properly.
- First boot with case off, battery gave false reading of -1021032418914 (something along those lines). That's usually caused by a lose battery correct me if I'm wrong?
- Everything seemed a lot more responsive and working.
Hmmm.
So removing the screws and taking the back casing off made the Semi Boot-Loops go away.
Maybe a part of the back casing was pushing on the Logic board and shorting it out?
Maybe the screws torque where messing with it (e.g. on a HDD with computers the simpliest change in toque on the screws in the HDD can screw the HDD.)
But the torque of the screws where very loose.
Any ideas are much appreciated!!
Yep, probably a short-circuit or dust problem or displacement somewhere around there. What you said proves that somehow the phone was physically damaged. You may need to actually disassemble all the pieces, inspect them and put them all back together, and it still may not work, for now, try cleaning the dust and tighten the screws, fasten the board.
@Dakura thanks for the help today Dakura!
Finally got around to putting everything back together after an evaluation, made the flex-cables all snug and tightened up the screws a lot!
The phone appears to be working now.
at 100% it even vibrates now when i tap things it never used to.
I couldn't quite locate the problem, but I have a feeling that one of the flex cables could have come loose but only just enough to generate fluctuation of power between full and under to keep the phone on.
Hopefully the phone stays stable!
@theunderling thanks for recommending me HawkerPauls Nuke script, I'll be using that every time I re-rom my phone from now on!
Will update the thread on a possible fix for anyone else with this problem.
It's always good to run through every possibility and solution to fix problems before going out and blowing money.
Okay first of all, I've scoured not only XDA but even Google for an answer to this problem to no avail. So if anyone has/knows of any thread that has the answer, please kindly reply or notify me so we can have this thread removed.
Here goes,
I'm experiencing a very unique (afaik) problem with my Galaxy S3. This started a few months back, when the phone started getting random reboots/ freezes and terrible battery life on ANY ROM/Kernel. I've tried CM, SlimBean/Kat, and even Stock and nothing worked. Finally I figured maybe the battery was shot. So a few days ago I went and got a new battery, and that's when it got weird.
I used the latest SlimKat after replacing the battery and after powering on the device, EVERYTHING seems perfect. It's really fast and responsive, battery drain while screen is on is extremely acceptable, things worked like new again. UNTIL I switched off the display, after 5 mins, I pulled out the phone and it was switched off. At first I thought maybe the initial charge wore down so I charged the phone to full, then powered it on. Again, everything went smoothly BUT, after switching off the display for more than 1 minute, the phone shuts off automatically.
I switched to the latest stock 4.3 ROM and restored everything to factory settings and it seems to have helped at first. As usual, everything is fast and battery doesn't drain so much BUT, after putting the phone to sleep, it takes 5-10 seconds for the screen to wake after pressing the power button, and even if it wakes up, it becomes EXTREMELY laggy and often freezes requiring a reboot. As usual, after a fresh reboot, everything becomes awesome again until I have to turn the display off for more than a minute.
I've tried everything, even installing an app that prevents deep sleep but the problem persists. It improved a little after flashing stock rom and reverting everything back so I'm really hoping this isn't a hardware issue. Is there maybe something else I can try, settings/software-wise? The phone is almost 2 years old and is already out of warranty.
I'm hoping it's not the sleep of death thing because the phone isn't exactly bricked. I can still use it for as long as it doesnt have to go into deep sleep (I turn it off before putting in my pocket and turn it on again when I need to browse/use the camera which is all it's good for in its current state.)
Also, the symptoms don't really fit the usual "Sleep of Death/Brickbug" Symptoms I've read about.
Hey, I remember having a similar problem. I formatted both my internal sd and external sd. Haven't had any problems ever since. Hope this helps.
Sent from my SM-N9005 using XDA Free mobile app
Already tried that. I did full wipes/formats on all my installs. I even tried not having an external SD inserted for the Odin installs. I tried not installing any app on the phone and it still gets messed up after going to sleep. As fresh installed AOSP or Pure Stock ROM. Odin flashes no problem so I'm really hoping nothing hardware-wise is messed up. I had to re-flash PIT after getting a new battery though, could I have messed something up there that would lead to this?
There is an app for that deep sleep syndrome, it's on playstore its calles brick check or something like that, if you cant find just google it.
And I dont think that could be software problem, BUT depends on what apps you used, flashes you made.
Hope it hepls
Well, i don't think its deith break, but i had the same essue with unofficial 4.3 and then at official 4.3 it worked well,
it may be a break in the motherboard or something.. as u tried every rome avilable it couldn't be softwear thing..
the app for emmc firmware is called 'eMMC check', you can find it on playstore
edit: does your phone heat up? or battery? did your display ever turned blue when waking up from sleep?
it could be also a short with your display/motherboard or other connectors or battery connector... and the protection kicks in
if you're good with tools and phone is not under warranty, you could disassemble it and reassemble/reseat the connectors
or, could be the power button shorting, if you decide to open it, examine the power button
@Eibram did you ever undervolt or overclock when using custom kernels or roms? Because it could be hardware damage.
Also, do as they tell you above, check if you have the insane f01 emmc chip. I know it's a common missconception going around that since 4.1.2 the SDS got fixed, but it didn't really get fixed since it's a firmware problem in the emmc patched through software which just makes it highly unlikely to happen (but not impossible).
I did some minor undervolting way back before JB came out but not since over half a year ago. I did the eMMc check and yes, I do have the inane chip.
Just an update, I re-flashed a PIT file and a rescue firmware and it seems to have helped a bit. It was running fine for over 12 hours aside from a random reboot just now.
I'm observing the phone right now to see wether the reboot was just coincidental. I really wish this is just a software thing.
Okay one more update, 2 days in and I've only experienced the one random reboot. It's still sometimes slow when waking up, but something around 2-5 secs sore not 5-15 seconds slow. I'm thinking that must be due to touchwiz bloat.
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.