Related
I have had my 8525 for over a month (an upgrade from a one year old 8125), but have recently been noticing a different problem than described on this or other PDA forums. If I am sitting around with the device and actively browsing and streaming content I have noticed the device will get pretty warm to the touch and then some problems start occuring....I loose the ability to use the touchscreen (can only use the buttons)...and....the 'select' button will start acting like the right softkey button. If I soft reset the device it does not fix the problems, but if I turn the device off and let it sit for a while and then reboot (after it has cooled off) everything works fine. Hardware problem? Anyone else experienced any of these problems? Thanks!
From what I've read here, perhaps you are seeing the "screen calibration bug" which is a heat related bug and there are threads about it.
I've watched two movies back to back (about 3 hours) on my 8525 with TCPMP, screen brightness set low, and it didn't get very warm at all.
Maybe G3 use when browsing with bright screen creates more heat? In any case I'd consider it defective.
Yep, I'd agree. Actually I have seen this problem posted before. You have an extreme example of the "heat expansion causing screen problems" issue. You can try loosening the screws on rear of screen, but honestly if it's in warranty get it replaced.
Try a hard reset (don't think it will change anything) and if it's still the same then it's certainly a hardware prob.
Mike
Thanks for the advice. I have noticed that I can use the device as a gps navigator with the screen 'on' for several hours and don't have the overheating problem or any problem with the screen, just when browsing and streaming via PIE using 3G. I will contact warranty exchange and try another unit.
Hi folks,
Am tearing my hair out with an overheating 8525. The icon shows the phone is charged up but about 2 hours later it is warning me to recharge or lose my data. During the 2 hours I have not used the phone at all. Any ideas? Another lemon phone, or is there something working in the background that keeps it "on" all the time? Other than this issue, it seems to be a pretty decent phone...
my previous device (imate k-jam/htc wizard/ same as 8125) and current hermes (jasjam) get pretty warm when browsing for a while or streaming as well as wi-fi, but i get no problems, so i'd say its a hardware problem too.
The first time my k-jam got hot it scared me and i thought the device was gonna fry. But i stream a lot with 3g on my jasjam and it gets pretty hot for a phone but nothings happened yet, and i let my k-jam get pretty hot all the time and it never malfunctioned from that.
tanguera said:
Hi folks,
Am tearing my hair out with an overheating 8525. The icon shows the phone is charged up but about 2 hours later it is warning me to recharge or lose my data. During the 2 hours I have not used the phone at all. Any ideas? Another lemon phone, or is there something working in the background that keeps it "on" all the time? Other than this issue, it seems to be a pretty decent phone...
Click to expand...
Click to collapse
You can check for any running programmes under memory in Settings. You should disconnect wifi when not connected - this causes battery drain and heat build up. You should also use a task manager to shut all programmes not actively being used (just tapping X does not close them. You should also check that messaging is not set to look for mail every few minutes and probably should do the "fake server trick" if you don't use push mail. Battery certainly should not flatten in two hours.
Mike
mikechannon said:
You can check for any running programmes under memory in Settings. You should disconnect wifi when not connected - this causes battery drain and heat build up. You should also use a task manager to shut all programmes not actively being used (just tapping X does not close them. You should also check that messaging is not set to look for mail every few minutes and probably should do the "fake server trick" if you don't use push mail. Battery certainly should not flatten in two hours.
Mike
Click to expand...
Click to collapse
Checked settings and it had IE and several other programs running. I've unchecked them, don't have it set to receive email on the device. I'm keeping my fingers crossed. Thanks. This came at the worst time since I'm going out of town - will check back in a couple of days - unless I've tossed it out of the plane....
tanguera said:
Checked settings and it had IE and several other programs running. I've unchecked them, don't have it set to receive email on the device. I'm keeping my fingers crossed. Thanks. This came at the worst time since I'm going out of town - will check back in a couple of days - unless I've tossed it out of the plane....
Click to expand...
Click to collapse
That may help a bit, but I think a task manager is an essential to save you looking in running programmes all the time. Something like the freeware "Magic Button" shows in the task bar all running programmes and allows you to close them down fully istead of the default which is just to minimise them. Link below. I'm still concerned that if it's heating up it is more than just a running programme though - normally it's wifi or other radio function that causes this.
http://www.pocketgear.com/software_detail.asp?id=7438
Mike
i would like to add to this... i recently had a similiar problem happen on my 8525.. my phone was sleeping but very very warm to the touch... so i turn it on, opened my task manager and noticed nothing was running, but my battery was dropping about 20% per hour... i performed a soft reset and the problem went away.. i dont know what caused it, but a soft reset fixed it.. and even though it was hot my screen was still responsive, but something was causing some serious battery drain. and i cant report accurate temp stats cause ikarus battery status today plugin seems to report temp backwards.. for example, when i wake my phone its sitting at 115F per battery status, but when the battery was real hot the other day it was reporting 90F. so its obviously backwards on reporting, but it does show a 25F difference...
shogunmark said:
i would like to add to this... i recently had a similiar problem happen on my 8525.. my phone was sleeping but very very warm to the touch... so i turn it on, opened my task manager and noticed nothing was running, but my battery was dropping about 20% per hour... i performed a soft reset and the problem went away.. i dont know what caused it, but a soft reset fixed it.. and even though it was hot my screen was still responsive, but something was causing some serious battery drain. and i cant report accurate temp stats cause ikarus battery status today plugin seems to report temp backwards.. for example, when i wake my phone its sitting at 115F per battery status, but when the battery was real hot the other day it was reporting 90F. so its obviously backwards on reporting, but it does show a 25F difference...
Click to expand...
Click to collapse
Yes, I think I've had that a couple of times. I have always just assumed that I'd left wifi on but not connected to any network - cos that doesn't half drain the battery (although curiously not every time - sometimes it seems quite ok left on, not connected and without getting hot). Perhaps it only gets hot if it's had a sniff at a network but fails to connect but keeps trying continuously.
This though would just be a very occasional thing, something more regular giving only 2 hours battery life is a bit puzzling.
Mike
mikechannon said:
Yes, I think I've had that a couple of times. I have always just assumed that I'd left wifi on but not connected to any network - cos that doesn't half drain the battery (although curiously not every time - sometimes it seems quite ok left on, not connected and without getting hot). Perhaps it only gets hot if it's had a sniff at a network but fails to connect but keeps trying continuously.
This though would just be a very occasional thing, something more regular giving only 2 hours battery life is a bit puzzling.
Mike
Click to expand...
Click to collapse
well with wifi yes, i had that with the wizard to (left it connected all night while plugged into my charger, needless to say it wasnt responsive when i woke up). But with my 8525 it was just idle, no wifi, connected on 3G but not passing data.. very weird situation to just drain like that..
I would recommend you try a different memory card. I had the same problem but found out it was a microSD card, the phone would get hot and battery would start dropping drastically - I changed to another memory card and the problem went away.
-mix
Any idea what's going on here?
mixmaven said:
- I changed to another memory card and the problem went away.
-mix
Click to expand...
Click to collapse
What's going on here? This sounds just plain weird. Care to share the manufacturer?
teambnet said:
What's going on here? This sounds just plain weird. Care to share the manufacturer?
Click to expand...
Click to collapse
Don't know what mixmaven will say, but I suppose it's possible that quality of manufacture or poor contacts could cause the device to consume excess power trying to establish network connections or simply loop itself trying to register the card.
Mike
shogunmark said:
i would like to add to this... i recently had a similiar problem happen on my 8525.. my phone was sleeping but very very warm to the touch... so i turn it on, opened my task manager and noticed nothing was running, but my battery was dropping about 20% per hour... i performed a soft reset and the problem went away.. i dont know what caused it, but a soft reset fixed it.. and even though it was hot my screen was still responsive, but something was causing some serious battery drain. and i cant report accurate temp stats cause ikarus battery status today plugin seems to report temp backwards.. for example, when i wake my phone its sitting at 115F per battery status, but when the battery was real hot the other day it was reporting 90F. so its obviously backwards on reporting, but it does show a 25F difference...
Click to expand...
Click to collapse
Well, my phone is no longer a phone, just an expensive paperweight. It was completely useless in Miami, and I could get maybe ONE call in before it would shut off from battery drain. I had NO programs running in the background, but I could see the battery charge plummeting before my eyes. Now it no longer holds a charge at all. Maybe 10 or 15 minutes, max. I'll try a soft reset like you did, but I'm not holding my breath. Battery also continues to run incredibly hot to the touch, even when "sleeping". In addition, I'm now also having ActivSync problems.... What a lemon.
Forgot to mention that it takes forever to find the network. I can't tell if I have a software, hardware, or network problem.
Sorry, just catching up - I've been out of town and obviously incommunicado...
I don't think this has anything to do with either the wifi or the memory card as it drains and heats with both the card and wifi in/on and out/off. Someone had suggested I check the running programs and only once did I see IE running. The only other program that seems to run even when it's not connected to the PC is the ActivSync.
I've done a warm reset, so I'll report any progress. Unless I throw it out the window first. I may just take it back and ask for a whole new kit....
could be a bad battery also... or a defective phone, i would maybe try the battery first, if that doesnt work then i would warranty the phone! But this has only happened to me only like twice or so, and in every case a soft reset fixed it...
Well, I've reset the thing and left it fully charged and unplugged since my last post. Still holding the charge and remains cool to the touch. Of course, I haven't used it at all, so the drive test still remains....
When my phone is sitting idle (screen off) it will randomly decide to power itself off. Has anyone else noticed this? Any ideas on what could be causing it?
The Balvenie said:
When my phone is sitting idle (screen off) it will randomly decide to power itself off. Has anyone else noticed this? Any ideas on what could be causing it?
Click to expand...
Click to collapse
you mean randomly power itself ON, right?
if that is the case, it's normal, it just mean it woke up to connect to the internet, to get updates of news, emails, or whatever it was scheduled to pick up
nope. i mean it randomly turns itself off. this topic is being discussed over on the att captivate galaxy forum section.
interesting, so it's going from stanby mode, to complete OFF... nope never seen that happen to my i9000 model
yep totally powered off... completely sucks... looks like there are a bunch of ppl that have this issue with the captivate on att. $10 says its some lame piece of software that att puts on your phone that's causing the problem.
it's possible, i've read here a few users having crazy power issues (battery draining very fast) with their SGS i9000, but after wiping it out clean, to start anew, then the power problem is gone away.
so yes, a software could cause something weird like that.
Factory reset and so far so good
Hey guys,
I use a Galaxy S here in Hong Kong and I had the same random shut down issue constantly happen when my screen went off...
I tried everything, check temperature of cpu, etc. etc. and nothing worked, it just got worse and worse.
I even changed the battery to use the spare one that came with this. Still problematic.
Used SET CPU to limit the cpu to 400mhz, still problems.
Finally I did a factory reset and so far so good.
I only have the original system installed with the Remember the Milk app installed.
24 hours, no problems.
Installed AppBrain app.
Then I installed 3G WatchDog
12 hours, no problem.
Then I installed Paperdroid
12 hours, so far no problems at all.
If I run into an issue I'll post it here. But I think it definitely was a software issue.
Update - it randomly shut down on me
Alright guys, it shut down on my randomly today in the afternoon......
I dont know if it's the re-charging that screwed it up?
Because after my factory reset, last night was the first time i charged it....
Hmmm
This happened to me too - two days in a row until noon it would shut down two or three times - i uninstalled SetCpu and for now (24 hours) it hasn't happened again. I am not sure if it was the one responsible but it started happening after i installed two programs and i uninstalled them after it started happening. I uninstalled Visual Task Switcher first but on the next day it turned off again, then i unsinstalled SetCpu and it hasn't happened again - maybe some wrong profile settings but i didn't feel like experimenting
I had this issue once too in about 40 days.
I was reading an sms and then i turned into standby and put it in my pocket. Later, maybe 40 minutes i came home and my phone was completely off. I do not remember if i had to take out the battery before to get it on again.
I was wondering why it happened. Maybe it was caused by an app i had opened. Battery still was at 40%.
But since it only occured once in 40 days i doesn´t bother me.
Interesting you mention this as it just happened to me today for the first time. I took it out of my pocket and wtf? The phone was off. Very strange... Using the i9000 on the stock Eclair rom.
Should send back for warranty
Sent from my GT-I9000 using XDA App
software clash?
Well the phone suddenly switched off for me, but this time I turned off APPBRAIN and so far so good.
In fact, I came across an app called NoLED and since it kind of keeps ht phone on, while I have it on my desk, I'm able to be notified of stuff and so far with that, the phone hasnt' shut off.
I'm still experimenting with what works, but try turning off AppBrain and see if you still have the random shut off issue....
i use app brain all the time to keep my apps in sync
not the cause of the problem, that's for sure
my phone can last a whole day even with app brain running
OP, do you have MSN Talk installed on your phone? I have this same problem, seems to happen more when I am running MSN talk in a low signal area.
«try a new sim card. «Could be faulty. «i am on my 3rd phone and all of them had this same problem. «i bought a new sim card 4 days ago, and hasnt happened since. «but then again, this problem usually happens to me once every 3rd-5th day anyways, so i dont know if i am in the clear yet.
Me too, shutdown everyday
Hi guys
After upgrade OS to I9000ZSJG4, Phone random shutdown everyday.
Yep still shuts down
Tried keeping AppBrain off, still shuts down.
Used NoLED so the screen kind of stays on, still shuts off..
So far shut off on me after 40 hrs... this is really stupid.
I am this close to taking it back, but I genuinely think it's a software issue than a hardware issue...sigh
Anyone have any luck figuring this out?
Same problem no solution yet
Hi
I too have the same problem, haven't found any solution yet.
The temperature etc is all good, there is no pattern in shutdown issues.
I have tried factory reset and no new application, it still shut down while using in built browser.
I had the same thing happen to me while skiing in Whistler last weekend. It died twice. I attributed it to the cold. I normally use a 3000mah battery up there, but left it back the house that day. Afterwards while charging in the car and even charging it at home it died prematurely again. It was the eBay aftermarket variety 1500mah knock off. I have since changed back to the Samsung OEM battery. I haven't had an issue with it since. My assumption is that the knock offs in my case cannot handle the heat cycles of charging and then the cold as well as the original. Or they have a limited lifespan, well below OEM specs. I am now only using the 3000mah battery on the weekends to hedge my bet on the quality of manufacture, as it seems to be from the same factory as the 1500.
**Update** See new note added 2/16/13 at bottom!
Trying to provide a single informational resource on three, typically related issues:
1. My N7 turns off randomly
2. My N7 dies early at ___% battery (you fill in the value)
3. My N7 turned itself off, and won't turn back on
There’s a ton of threads all over the net regarding these issues, some providing unintentionally misleading info, some progress towards actually defining the issue and posing possible solutions. Reports of these issues started back when the N7 was first released and continue to this day. These issues have been reported to Google, but who knows whether or not the Google God will attend to them anytime soon.
What follows is what I’ve learned about these issues, how they affected most users, and how they were resolved for most users. This is not intended to capture every possible exception.
Issue #1:
For some users, their N7 just turns off randomly, regardless of battery level. For them, a loose battery connector is typically the cause. Popping off the back cover, re-seating the connector and possibly putting a tiny piece of tape to keep it secured over time is the fix.
Issue #2:
Many users notice that their N7’s turn off by itself, typically when the battery is at the lower-end of the % scale – anywhere from 40% down to 20% or so. Most users think that their N7 is running out of power "early" – but it seems that the 40% - 20% indication is erroneous - the battery is really at 0%, and is turning off as it should. This appears to be the caused by a software glitch that Google has to address. Doing a Factory Reset and a battery pull appears to remedy this issue for just about everyone. Please note that a corollary to this issue is the observation that once charged, the N7 remains at 100% far longer than it should.
Issue #3:
Taken out of context, having an N7 that won’t start seems like a terrible thing. But in most cases, it’s caused by Issues #1 and #2.
- If Issue #1 caused it: reconnect the loose cable, recharge your battery if needed, and you are good-to-go.
- If #2 caused it, your N7 battery is dead. Plug your N7 into the original power supply, patiently wait a few minutes then patiently hold down the power button up to 30 seconds (actually look at your watch – it’s gotta be “up to 30 seconds”!), for just about everyone reporting, it’ll start up just fine.
- If both of these methods don't work, try powering-down via the bootloader: plug your N7 into the charger, press Volume-Down and Power at the same time, in the bootloader choose "Power-Off Device", unplug your N7 and plug it back in. Do you see the battery meter? If so, you're done.
- While the original power supply should be the best to use in these troubleshooting procedures, if you are not getting a resolution of this issue, some N7 owners have had success with power supplied by USB via PC. Give it a try.
Since these problems are widespread, there are a number of “fixes” offered other than those above, that are somewhat anecdotal – they only “work” in one/couple instances and therefore there’s no real evidence that they are relevant. This group includes:
- Using battery calibration apps to fix the problem
- Dumping battery stats
- Uninstalling a specific " troublesome" app
Some users send their N7’s back to Google, and their new N7’s are deemed "fine". A number of knowledgeable users have speculated that most of these N7’s sent back really only suffered from the fixable issues listed above. To support this notion, some have reported that the replacements have the same “defects” as their first units, and they continue to send them back.
My experience:
My N7 worked perfectly for the first two weeks of ownership. Then it started turning off at 30% and 23%. I also noted that once I charged-up, my N7 would stay at 100% forever, leading me to believe that the battery readings were hosed-up. After these problems started, it would not go below the 30%-20% thresholds. The first time I tried to power it up - it wouldn't - and I thought is had totally borked. I tried eventually figured out that I needed to add power, wait, then hold down the power button. Worked every time.
For me, I wanted to know if I had a loose battery connector - a common problem, even though my N7 was not shutting down randomly, it was always at low battery levels. I figured that I'd just do the two things that research showed would work for sure, and would cover two different issues. I popped the back off, found that the connector as well-seated, but I pulled it off anyway to do the "battery pull". I reconnected and added a bit of electrical tape to keep it secured. I then did a Factory Reset using the option under "Settings/Backup and Reset". My N7 has been absolutely PERFECT since - just as most users report.
There is still the apparent issue of Google fixing the issue that causes the battery indication to be inaccurate.
I hope that this post serves to help others that experience these issues.
_______________________________________________
Update 2/16/13
I noticed in the past 2 days that my N7 started staying on 100% for prolonged periods of time. I figured that it once again lost it's ability to provide accurate battery status. Therefore, I projected that when it gets down to 30% or so, it'll turn off. It did.
I did the fixes I outlined in the OP and this time they didn't work. After pulling the battery and doing a factory reset, it still indicated 30% battery left - and I KNOW it's really at/near 0%.
I've been monitoring this issue since I made this thread and I've noticed that a growing number of N7 users were fixing this issue by simply turning off their N7's for a period of time. So I gave that a go.
I plugged my N7 in for about 20 minutes to give it the juice it would need to restart after the period of time being turned off. Then, I unplugged it and turned it off. Waited an hour, and when I restarted it, the battery had been recalibrated to 0%. Awesome!
So where does this leave us? Here are my thoughts:
- Since there are a number of different causes that result in the symptoms listed in the OP, those fixes are still relevant for those specific causes.
- We should add this latest fix to the collection, as it worked perfectly for me today.
- It's possible that our N7's should be periodically turned off - possibly overnight as it charges. I know that I plan to occasionally do this. If you don't have a disconnected/loose battery cable, or some issue with software that is remedied by a Factory Reset, maybe your N7 just needs to be turned off to recalibrate every now and then. Update: As of 5/3013, my N7 has been flawless. It's entirely possible that this is because I shut-down my N7 every week or two to recalibrate.
As always, I hope this keeps N7 users from freaking out, or sending their N7's back - unless it's really necessary.
And as I said in the OP, Google really needs to address this, as there's plenty of evidence that many N7 owners experience these issues. I'll update my report to Google.
Stock 4.1 upgraded to 4.2.1
No Root/unlock
Software or Hardware? Who know's..
I received my N7 on dec 20th 2012, still haven;t gotten to use it more than a day or 2... had battery issues off the hope, shut of at 21% ish... tried turning it on... just got screen flickering. Tried chargin it for hours, still nothing... after submitting an RMA after a couple days of charging with device on or off or with screen flickering ,,,nothing worked. Hung up with support... tried with USB connected to PC... got the device to boot.
I also in between random variations of cables and what not I did the D/C on battery ... didn't do much for me.
Charged device to 100% used down to 60% charged to 75%
Used again for 5 minutes
Device turned off.
Wouldn't boot
Another day of messing around... got it to turn on
Booted, battery was at 0% said it was shutting down
Tried a few more times (without charging) Just shut down cause battery was at 0%
Tried again, Booted said battery was at 85%
Light Use
Plugged in to charge, got home from work next day, device won't turn on
Been 3 days
New device form RMA gets in today.
If it comes with 4.1 I am going to run it for a few days because when i received my first device, it seemed to be working fine for the first 2 hours... got my device setup then decided to do the update to 4.2.1
Immediately my device shut down and gave me a screen flickering issue... did hard reset (held power for like 10 sec) device turned on... then experienced all the crap above.
So if i update after a couple days... and then run into issues... it would tell myself that there could be an issue with the update... but who knows as all the reading I have been doing, every scenario is different.
Google told me to submit a second RMA if it continues.... I'd rather not have the device if I just have to keep returning it.
Blesseld said:
Stock 4.1 upgraded to 4.2.1
No Root/unlock
Software or Hardware? Who know's..
I received my N7 on dec 20th 2012, still haven;t gotten to use it more than a day or 2... had battery issues off the hope, shut of at 21% ish... tried turning it on... just got screen flickering. Tried chargin it for hours, still nothing... after submitting an RMA after a couple days of charging with device on or off or with screen flickering ,,,nothing worked. Hung up with support... tried with USB connected to PC... got the device to boot.
I also in between random variations of cables and what not I did the D/C on battery ... didn't do much for me.
Charged device to 100% used down to 60% charged to 75%
Used again for 5 minutes
Device turned off.
Wouldn't boot
Another day of messing around... got it to turn on
Booted, battery was at 0% said it was shutting down
Tried a few more times (without charging) Just shut down cause battery was at 0%
Tried again, Booted said battery was at 85%
Light Use
Plugged in to charge, got home from work next day, device won't turn on
Been 3 days
New device form RMA gets in today.
If it comes with 4.1 I am going to run it for a few days because when i received my first device, it seemed to be working fine for the first 2 hours... got my device setup then decided to do the update to 4.2.1
Immediately my device shut down and gave me a screen flickering issue... did hard reset (held power for like 10 sec) device turned on... then experienced all the crap above.
So if i update after a couple days... and then run into issues... it would tell myself that there could be an issue with the update... but who knows as all the reading I have been doing, every scenario is different.
Google told me to submit a second RMA if it continues.... I'd rather not have the device if I just have to keep returning it.
Click to expand...
Click to collapse
Sorry to hear of this.
Not sure that I read that you did the Factory Reset, as suggested in the OP.
Give that a try.
Pulling the battery and/or doing a full Factory Reset is the fix for the vast majority of N7 users.
You may be an exception to that. Hope not.
Ya I have done the factory reset and battery pull, after the reset it just reset to 4.2.1 it came with 4.1.
Then it shut down on me again, I have my new unit it now. Running solid so far, good battery charge... not taking forever. hasn't shut down yet.
I'm going to run it on 4.1 for a day or 2 then update. Hopefully I don't run into issue after the update... it was probably coincidence but i ran into problems after updating on my first N7 to 4.2.1
Well, then unlike many other N7 owners, since you did both the battery pull and Factory Reset, you can rest assured that you didn't waste your time sending your N7 back - it needed replacement.
Good luck with it!
Just reporting back with a status. The fixes I described above seem to be working perfectly for days now. Check my OP and give those recommendations a shot if you're having any issues. Hope this helps to simplify a potentially confusing landscape and to resolve these issues for other N7 owners.
Two of the ”fixes” that folks anecdotally reported... using a battery calibration app and clearing battery stats are 100% guaranteed not to work. Those who actually ascribe any effect to them are merely using faulty reasoning. Quite simply, the calibration apps are just another method of wiping battery stats. Nothing at all in batterystats.bin has any bearing on battery life or reported charge indication.
This isn't directed at anyone in particular. Rather, I'm just expounding on something from the OP.
Definitely a very useful thread, given what seems to be a not too uncommon issue. As an aside, I've also experienced the problem after flashing a new kernel. Reflashing the previous kernel corrected the issue.
Sent from my Nexus 7 using Tapatalk HD
najaboy said:
Two of the ”fixes” that folks anecdotally reported... using a battery calibration app and clearing battery stats are 100% guaranteed not to work. Those who actually ascribe any effect to them are merely using faulty reasoning. Quite simply, the calibration apps are just another method of wiping battery stats. Nothing at all in batterystats.bin has any bearing on battery life or reported charge indication.
This isn't directed at anyone in particular. Rather, I'm just expounding on something from the OP.
Definitely a very useful thread, given what seems to be a not too uncommon issue. As an aside, I've also experienced the problem after flashing a new kernel. Reflashing the previous kernel corrected the issue.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
najaboy:
Excellent background on those two "fixes", and I agree 100%.
In creating this thread, I didn't want to really slam-dunk any of the "fixes" that other people have offered in other threads. But the research shows that you are exactly right: calibration apps and wiping battery stats will do absolutely nothing - guaranteed.
It's amazing how many misleading threads I had to wade-through to get to the fixes I recommend. No wonder so many people have returned their N7's to get one that "doesn't have the issues".
Crisis averted
billykxda said:
Trying to provide a single informational resource on three, typically related issues:
1. My N7 turns off randomly
2. My N7 dies early at ___% battery (you fill in the value)
3. My N7 turned itself off, and won't turn back on
There’s a ton of threads all over the net regarding these issues, some providing unintentionally misleading info, some progress towards actually defining the issue and posing possible solutions. Reports of these issues started back when the N7 was first released and continue to this day. These issues have been reported to Google, but who knows whether or not the Google God will attend to them anytime soon.
What follows is what I’ve learned about these issues, how they affected most users, and how they were resolved for most users. This is not intended to capture every possible exception.
Issue #1:
For some users, their N7 just turns off randomly, regardless of battery level. For them, a loose battery connector is typically the cause. Popping off the back cover, re-seating the connector and possibly putting a tiny piece of tape to keep it secured over time is the fix.
Issue #2:
Many users notice that their N7’s turn off by itself, typically when the battery is at the lower-end of the % scale – anywhere from 40% down to 20% or so. Most users think that their N7 is running out of power "early" – but it seems that the 40% - 20% indication is erroneous - the battery is really at 0%, and is turning off as it should. This appears to be the caused by a software glitch that Google has to address. Doing a Factory Reset and a battery pull appears to remedy this issue for just about everyone. Please note that a corollary to this issue is the observation that once charged, the N7 remains at 100% far longer than it should.
Issue #3:
Taken out of context, having an N7 that won’t start seems like a terrible thing. But in most cases, it’s caused by Issues #1 and #2.
- If Issue #1 caused it: reconnect the loose cable, recharge your battery if needed, and you are good-to-go.
- If #2 caused it, your N7 battery is dead. Plug your N7 into the original power supply, patiently wait a few minutes then patiently hold down the power button up to 30 seconds (actually look at your watch – it’s gotta be “up to 30 seconds”!), for just about everyone reporting, it’ll start up just fine.
Since these problems are widespread, there are a number of “fixes” offered other than those above, that are somewhat anecdotal – they only “work” in one/couple instances and therefore there’s no real evidence that they are relevant. This group includes:
- Using battery calibration apps to fix the problem
- Dumping battery stats
- Uninstalling a specific " troublesome" app
Some users send their N7’s back to Google, and their new N7’s are deemed "fine". A number of knowledgeable users have speculated that most of these N7’s sent back really only suffered from the fixable issues listed above. To support this notion, some have reported that the replacements have the same “defects” as their first units, and they continue to send them back.
My experience:
My N7 worked perfectly for the first two weeks of ownership. Then it started turning off at 30% and 23%. I also noted that once I charged-up, my N7 would stay at 100% forever, leading me to believe that the battery readings were hosed-up. After these problems started, it would not go below the 30%-20% thresholds. The first time I tried to power it up - it wouldn't - and I thought is had totally borked. I tried eventually figured out that I needed to add power, wait, then hold down the power button. Worked every time.
For me, I wanted to know if I had a loose battery connector - a common problem, even though my N7 was not shutting down randomly, it was always at low battery levels. I figured that I'd just do the two things that research showed would work for sure, and would cover two different issues. I popped the back off, found that the connector as well-seated, but I pulled it off anyway to do the "battery pull". I reconnected and added a bit of electrical tape to keep it secured. I then did a Factory Reset using the option under "Settings/Backup and Reset". My N7 has been absolutely PERFECT since - just as most users report.
There is still the apparent issue of Google fixing the issue that causes the battery indication to be inaccurate.
I hope that this post serves to help others that experience these issues.
Click to expand...
Click to collapse
Brand new Nexus 7 purchased today, came with 4.1 and I applied 4.2.1. Difficulties getting it powered on in the first place and lots of reboots and apparent crashes. Factory reset once and found some of those other threads you mentioned, disabled location services and that seemed to help a bit but still getting reboots. More digging and I found your post. Took your advice and pulled off the back of the Nexus 7, pulled the battery up and the connector basically fell out, it obviously wasn't seeded properly. Popped it back in properly and it's working much better now, although I'm going to give it 24 hours to make sure my issues are resolved. I just created an account in here to thank you. Think I'll stick around and see what else I can learn.
got my nexus 7 at September 2012,
got no problem with the abttery at the first charge,
but few weeks later, the battery started to die at 20% , then died at 30%, i didnt notice until i saw the battery history, it just jumped from 30% to 0%,
keep in mind that i'm not using the asus standard charger (dont know if this affect us)
tried charging it with the original charger, look like the problem is fixed, the battery died at 5%.
not sure if this is a coincidence or not
sorry for the bad English
Hazmatilda said:
Brand new Nexus 7 purchased today, came with 4.1 and I applied 4.2.1. Difficulties getting it powered on in the first place and lots of reboots and apparent crashes. Factory reset once and found some of those other threads you mentioned, disabled location services and that seemed to help a bit but still getting reboots. More digging and I found your post. Took your advice and pulled off the back of the Nexus 7, pulled the battery up and the connector basically fell out, it obviously wasn't seeded properly. Popped it back in properly and it's working much better now, although I'm going to give it 24 hours to make sure my issues are resolved. I just created an account in here to thank you. Think I'll stick around and see what else I can learn.
Click to expand...
Click to collapse
Congrats!
Go enjoy your new N7!
webslasher said:
got my nexus 7 at September 2012,
got no problem with the abttery at the first charge,
but few weeks later, the battery started to die at 20% , then died at 30%, i didnt notice until i saw the battery history, it just jumped from 30% to 0%,
keep in mind that i'm not using the asus standard charger (dont know if this affect us)
tried charging it with the original charger, look like the problem is fixed, the battery died at 5%.
not sure if this is a coincidence or not
sorry for the bad English
Click to expand...
Click to collapse
Have you tried the recommendations in the op?
billykxda said:
Have you tried the recommendations in the op?
Click to expand...
Click to collapse
I guess you solved your issue?
Re: N7 Turns Off/Won't Turn Back On - A Summary...
I did have issue #2. I already had fully charged over night. Battery indicator showed 100% for a while, so I figured the problem wasn't solved. What I did was shut down my N7, then hook it up to the charger, boot my N7, unhooked it from charger, played 1 level in Amazing Alex and checked battery indicator again: 99%. I hope this means I solved the problem for now
Verstuurd van mijn Nexus 7 met Tapatalk
Fotogravin said:
I did have issue #2. I already had fully charged over night. Battery indicator showed 100% for a while, so I figured the problem wasn't solved. What I did was shut down my N7, then hook it up to the charger, boot my N7, unhooked it from charger, played 1 level in Amazing Alex and checked battery indicator again: 99%. I hope this means I solved the problem for now
Verstuurd van mijn Nexus 7 met Tapatalk
Click to expand...
Click to collapse
Interesting. There have been reports of people addressing this problem by just turning off their N7 for a while, booting back up and all is well. Others like you added the plug/unplug charger to the mix and that seemed to work for them.
This issue has been reported to Google as well - there is a thread on Googles defect site that also lists all sorts of "fixes" that people have attributed to this issue.
Still, the only highly-repeatable fixes I've seen in various threads/forums are in the OP. But, who knows? If you can get your N7 past these issues, it's a good thing!
Re: N7 Turns Off/Won't Turn Back On - A Summary...
Hi, you can add me to the list. My N7 often turn off itself when battery level is under 50%. I have tried everything (factory reset, flash stock image...) but problem still persists.
So i have a N7 with half battery capacity most of the time. I hope next update will fix it otherwise i'll send it to Asus.
Edit: mine just switch off at nearly 25%, i'll try to downgrade to 4.1.2 and see if it helps...
Sent from my Nexus 7 using xda premium
roswell782 said:
Hi, you can add me to the list. My N7 often turn off itself when battery level is under 50%. I have tried everything (factory reset, flash stock image...) but problem still persists.
So i have a N7 with half battery capacity most of the time. I hope next update will fix it otherwise i'll send it to Asus.
Edit: mine just switch off at nearly 25%, i'll try to downgrade to 4.1.2 and see if it helps...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi!
Did you try all of the suggestions in the OP?
-bk
Re: N7 Turns Off/Won't Turn Back On - A Summary...
Hi, i didn't open the battery cover because i don't want to lose my warranty, i prefer to let Asus do it for me.
My history with Asus is finished, bought 3 products from them, 3 have problems...
Btw: of course downgrade to 4.1.2 did nothing
Thanks for your answer and have a good weekend.
Cheers, Ros.
Edit: RMA asked, hope Asus will fix it.
Sent from my GT-I9300 using xda premium
My N7 is driving me crazy. Bought it last year around October, and it seemed fine at first. Battery would die at around 4-5% which is acceptable. Then it started getting worse over time. At this time it was completely stock - locked and not rooted. It got to the point where it would shut itself off when it reached 40%, so I decided to factory reset, pull battery, unlock, root and install Paranoid Android, hoping this would solve (or help) the issue.
Did all my unlocking and rooting last night, installed PA, set everything up, then started reading on my N7. Device turned off at 65% now. To say that I'm disappointed is an understatement. I'm all out of ideas on what I can do to fix this thing. I charged it overnight and disconnected it from the charger 3 hours ago, and it's still at 100%, even though I've used it quite a bit. Infuriating.
ynrozturk said:
My N7 is driving me crazy. Bought it last year around October, and it seemed fine at first. Battery would die at around 4-5% which is acceptable. Then it started getting worse over time. At this time it was completely stock - locked and not rooted. It got to the point where it would shut itself off when it reached 40%, so I decided to factory reset, pull battery, unlock, root and install Paranoid Android, hoping this would solve (or help) the issue.
Did all my unlocking and rooting last night, installed PA, set everything up, then started reading on my N7. Device turned off at 65% now. To say that I'm disappointed is an understatement. I'm all out of ideas on what I can do to fix this thing. I charged it overnight and disconnected it from the charger 3 hours ago, and it's still at 100%, even though I've used it quite a bit. Infuriating.
Click to expand...
Click to collapse
Sorry to hear this. This is what I'd recommend...
Take the N7 back to bone stock to reduce the number of variables. Follow my suggestions in the OP (I know you've already done them - but I'd still "do the drill" again). If this doesn't work, you can try some of the outlier suggestions that others have made that are less substantiated - why not at that point? If it's still a no-go, I'd return it. For your money, you deserve a perfect N7.
First I would like to say I can't remember how the keys are called, all I know they are the menu and back keys, and that they should light up for a second and turn off until used again.
I'm having couple of problems with my phone being awake all times, battery drain and mostly overheating.
Some hours ago, my phone was reaching battery temperature of about 42ºC while screen off and apparently "nothing" abnormal running in background. After restarting the device, first thing coming to mind was to put it in the fridge for a couple of minutes to let it cool down.
The problem is, 2 minutes turned out to be some hours. When I removed it from the fridge, I noticed the hardware keys weren't lighting up. Restarted, still nothing. They work, but won't light.
What could it be? Maybe the low temperature did something to it? Or was it condensed water from the fridge? What can I do to make them go back fully functional again?
Issue solved, the overheating made it go back working once more.
Maybe try putting your phone in a bag of rice for 24 hrs to draw the moisture out
Sent from my Gt-i9505
So I have the T-Mo variant, H918, and its all stock, no root no nothing. I am having an issue with the phone getting really warm and sometimes hot and then it freezes and sometimes reboots. There have been times when I needed to pull the battery to reboot it. Even then sometimes it freezes on boot requiring another battery pull. I've also noticed that the battery will die very quickly. I was at 85% and about 15 minutes later it was at 2%, this has happened to me several times. It was just sitting on my desk with the screen off. I have warranty replacement coming from T-Mo. Just curious if anyone else is having this issue or something similar.
I'd check the battery stats to see if its a specific app that's running out of control or something. I got a Verizon phone and never had that happen.
Yea I've done that on each occasion as well as checked the memory usage. Nothing out of the ordinary going on. The biggest draw on battery and resources is the os.