[Q] Nexus 7 in non-rooting caused bootloop... - Nexus 7 Q&A, Help & Troubleshooting

Okay, here's my problem with my Nexus 7. I went to drop a deuce (too much info) and woke up my Nexus 7 as it has replaced bathroom reading material, and well that's about it with a nice Galaxy Note that does the job just as well. Anyway, there was system update, (i'm guessing for 4.2.1 as I had just upgraded a week ago to 4.2 I believe). My battery was too low to do the update so it just quit on doing the update which was fine. When I was done with the tablet I plugged it in and figured I would hit it up that night when I got home from work.
Well, didn't touch it that night but when I got out of the shower the next morning I noticed it was awake. I watched it for a sec and the screen went to that tv off animation but much different, covering the whole screen and lasting a little bit longer and not really as smooth or animated looking, more like an actually fizzy screen. Then I noticed it rebooted. So I took it off the charger, it did the same damn thing again. Plugged it into my laptop and tried to power it on myself and it's unresponsive. Then, it turns on by itself and goes once again into a bootloop with the same fizzy screen. It also was only at 17% meaning it wasnt charging all day and if it was it was just using battery on the constant bootlooping (no idea how long it was going on for). So, I cannot use it at this point.
Anybody else had the same issues? Any solutions? Here is the link to the youtube video showing the actual problem.
http://youtu.be/uW_JX9Aorvk
fast forward to the 3:35 mark after the first power down to see the actual shutoff noise and fizzy screen. If you listen closely you will hear the actual fizzy sound it makes.
Lastly, my device is on 4.2 i believe and has not been messed with as far as rooting is concerned. Just the normal OTA updates from Google. Any help would be much appreciated :fingers-crossed:

Related

4.1.83 - random reboots a thing of the past?

I realized today that I hadn't had a random reboot in a while. From day 1 I could count on 1-2 random rebooted with my Atrix.
Sure enough, my uptime is 280hrs+, which is in line with when I took the OTA update. My wife's phone appears to be the same, and it was rebooting at a similar rate to mine before the update.
Both are rooted/non market enabled but not modded.
How's your stability been on 4.1.83?
Sent from my MB860 using XDA App
I had one strange reboot this morning, my phone had been lagging up a lot, along with the screen not turning on when I pressed the sleep button.
I look down a minute later and I see the Motorola logo. But afterwards it seemed just dandy.
Random reboots
I just bought this phone Friday at 7:45pm. It was working fine when I got home Friday night after purchasing it. I hooked it up to my pc and got the needed updates to 4.1.57.MB860.ATT.en.US. Saturday morning I installed one game bejeweled and advance task manager before heading out to work.
I got back home around 1:30pm and started setting up my contacts on the phone. Around 6:00pm I left the phone plugged into my pc and heard the phone rebooting from the other room. At first I thought maybe there was an update and that's why it was rebooting.
Two hours later it did the same thing again with no warning about a reboot when I was manually adding new contacts. I notice there was another update available to version 4.1.83 which I now have installed on the phone and it's still rebooting on its own.
I also noticed that my battery was right at 60% and while plugged up to my pc it was only recharging 10% every hour on the hour not sure if that's normal for this phone.
(Two hours later battery power at 90% with a solid green power light visible but taking forever to reach 100%)
Also right after the 4.1.83 update the phone would reboot and then the battery light on the phone would just randomly flash red with the motorola logo sitting on the screen. I had to pop the battery out, waited for about 30's before putting the battery back in and powering it back up and it still sat on the logo screen with the red flashing light.
(The battery is now at 100% but 3mins after unplugging it from the pc it displays 90% again all I've did is watch it reboot on its own.)
I removed the battery again but waited for about 5mins before powering it up and this time it actually booted up like normal and about 30mins later another reboot.
I also noticed that as soon as I finish watching a video with youtube the phone reboots a few seconds after the screen goes to sleep. Now as I am writing this comment I decided to uninstall that advance task manager program and do a reboot. The phone is at 80% and after I watch about three videos with youtube the phone didn't reboot.
I have no idea what's up with this phone and I really like it alot except for this mysterious rebooting not to mention other people experiencing random reboots. I read online where a lot of people where saying it was due to a bad battery and that they got a new battery from Att and the problem went away.
I am really thinking about turning this one in for a new replacement but some people are saying even after doing that they still kept having the problems.
Could this really be something wrong with the updates that is causing issues with the phone or is it just a bunch of bad batteries?
Battery?
Back again, in the post I made earlier I mentioned how the phone wouldn't randomly reboot when the battery was around 80% well the battery charged to 90% and the random rebooting has started up again and it has rebooted 3 times back to back now that it is at 90%.......I think I am going back to the Att store when they open today and try getting a new battery............
nickleboy said:
Back again, in the post I made earlier I mentioned how the phone wouldn't randomly reboot when the battery was around 80% well the battery charged to 90% and the random rebooting has started up again and it has rebooted 3 times back to back now that it is at 90%.......I think I am going back to the Att store when they open today and try getting a new battery............
Click to expand...
Click to collapse
If I were you I would get a replacement phone. I did have one random reboot since updating to 4.1.83 and that was the first ever I've noticed with my phone. Otherwise I haven't noticed any issues. As for charging via a pc I did hear that was slow. I charge via power outlet or using a car adapter and both are fairly quick. Good luck.
Battery?
I decided to do a factory reset on the phone first and the funny thing is after the reset, the phone still showed that it had the latest update installed even though I still had to go through the setup process just like when I first purchased the phone. So far it appears to be working and hasn't rebooted on me yet. No rebooting after playing Youtube videos either. The only small pet peeve I have at the moment is the Facebook & MySpace contact photos will not show up for some unknown reason in the contacts sections, they're just empty picture frames. The contact photos that do show up are the ones from my google gmail account and I manually added those online myself so those automatically transfer when my phone syncs with the gmail account.
And the MySpace widget doesn't show a photo as well but the info in the widget is current. That's way better than experiencing random rebooting when you really need your phone the most.
nickleboy said:
I decided to do a factory reset on the phone first and the funny thing is after the reset, the phone still showed that it had the latest update installed even though I still had to go through the setup process just like when I first purchased the phone........
Click to expand...
Click to collapse
This is normal. A FR cleans all of the user data reseting it back to a "clean" version of the flashed rom.
I can say that I have also not had any reboots since .83 but it is also the first time i have loaded gingerblur.

[Q] Nexus 7 issue. Help please

Ok guys, Hi.
I am a noob, but have been stalking the forum for along time and I have yet to see this issue.
My Nexus 7 16GB I have had since day one, and as of yet (apart from the storage I/O issue, fixed with 4.1.2 and factory reset) have had no hardware issues.
It has replaced my laptop in use and is pretty much always with me, so to say it's had heavy use is an understatement. Today however I was browsing Reddit and I knew the charge was low, around 13%, and suddenly it turned off. Not thinking anything about it, plugged it in and came back 15 mintues later. Turned it on and was finefor around 45 seconds, then the screen flickered lines up and down and then switched off...
Now shows 5% battery and does does the same everytime, have tried restarting and have tried recovery to no avail.
This is what it does - youtu. be / LwLybeSNjL4 I know I shouldn't post links, but it's the only way to show
Any help would be great, otherwise RMI?

N7 Turns Off/Won't Turn Back On/Battery Status Issues - The Fixes **UPDATE**...

**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.

Nexus 4 switching off at night while charging

I know this has been discussed plenty of times but I just have some more questions of my own I'd like to ask.
So my N4 just switches off over night after being charged to like 95-100%.
It is usually fully charged (green LED) but won't turn on if I want to wake the screen.
I have to hold the power button for like 5 seconds for it to switch off. Then I am able to boot it again.
If i just unplug the charger, wait like 30s to a minute, the screen will wake, it works as usual. But the phone restarted (!!!) without any boot animation or anything. Just like nothing happened. If I then go into settings -> battery you can see the phone switched on just a minute ago.
This is happening like everynight for me now, so I had to use my old phone as an alarm clock as I slept in quite a few times actually
I searched like all forums and tried everything but I cannot dissolve this issue.
I even turned off deep sleep in dev options and stuff alike, monitored temperatures and stuff. Nothing conclusive though.
So I just have no idea why this keeps happening.
It happened with different roms and different kernels. Root or not rooted.
A friend of mine has a N4 as well and he does not have this problem at all. He does not have a custom rom flashed or anything.
But I read on other forums that even users with stock rom had this problems.
I think this is a quite common problem with the Nexus 4 device, isn't it?
Anyone solved it yet? Or does at least know the CAUSE for this?
I mean srsly there is like nothing on the forums..
Is it software related? Hardware related? Did I **** something up?
Is this a valid reason to send my phone back to google and get a new (working) one?
Everything else just works flawlessly. I mean the N4 with PA on it works so smooth like a charm.
I DO NOT WANT TO GIVE IT BACK!
noone? really?
I don't remember this being a common problem, though maybe I missed something.
If I was you I would wipe everything and re-flash stock. Then if it still happens return the phone, it shouldn't be doing that and I wouldn't put up with that if it was my phone. But it's your choice.
Sent from my Nexus 4
I have the same problem and I believe that this and similar issues are becoming increasingly mentioned on various sites on the net. XDA tread - http://forum.xda-developers.com/showthread.php?t=2077148 which gives some idea as to what people are doing to get to the bottom of the problem.
There is further info here - https://code.google.com/p/android/issues/detail?id=35139 which starts with Sleep of Death issues on JB4.1.1 (on the Galaxy Nexus but has more recently focused on the Nexus 4).
Initially the problem occurred maybe 3 times a week. I'm running a Stock N4 and whether stock or custom does not seem to make any difference.
I re-flashed a stock image and thought I had solved the problem. The phone ran okay for a few weeks and then reverted to random SOD's normally at night whilst charging. If I use airplane mode at night I have no problems. It has also become unresponsive/deep sleep on three occasions during the day. More recently I have stopped leaving wifi enabled unless I need it I no longer use airplane mode and have not had any further problems --- so far ---
For me at least, the problem might be wifi related.
This happened to me this morning. I have my phone on charge every night and it probably hits 100% about 3am every morning. I have the alarm set at 7am to wake me, and has done every morning since I got it last month. However I have now slept in twice (this morning was catastrophic) due to waking up to find my phone was switched off and my alarm subsequently didnt sound!! I have wifi left on, but all my apps are closed down, and only the alarm app running.
To switch it back on I have to hold the down the power button for in between 5-10 seconds for it to reboot.
Does anyone know why this is happening? The Nexus 4 is perfect in every other way, I'm gutted to find a fault after raving so much about it!
Same thing is happening to me every night !
I have the same problem, but it happens sporadically, so I never know when I'm going to end up sleeping in. It's infuriating.
It just happened again this morning. I had Wi-Fi disabled, so I know it has nothing to do with that.
Tronno1 said:
I have the same problem, but it happens sporadically, so I never know when I'm going to end up sleeping in. It's infuriating.
It just happened again this morning. I had Wi-Fi disabled, so I know it has nothing to do with that.
Click to expand...
Click to collapse
Sounds like a rogue app is triggering the phone to crash or something?
Have you tried a factory reset?
This bs caused me to be late to a final exam... I was so mad when I woke up and saw that it was 2 hours later than the time my alarm was set to sound.. Only started happening with 4.4+ updates.
Sent from my Nexus 4 using xda app-developers app
Factory reset?
Sent from my Nexus 4, while driving in my Evo9.
Hey man,
My girlfriends nexus 4 did this as well and she got it RMA'd with no questions asked and a brand new one sent out, they told her to do a factory reset; this worked for a few days then went back to normal again.
- Sent from my Nexus 7
Charging cable
I have had this problem eventually with every android phone I've ever owned but it seems by replacing the charging cable with a new one the problem goes away. It seems that there is a weird thing with android where if the cable doesn't sit completely snug or straight the battery can charge but the phone won't realize this and go to sleep. Also seen the opposite happen where the phone thinks that the battery is charging and in fact it hasn't. When you unplug it suddenly goes from full charge to nothing. Haven't seen that last one on my Nexus 4 yet though. So I would try replacing the cable (not necessarily the charger) usually worked for me on other phones. Also I would suggest not to leave the phone and cable hanging off the end of a table. Make sure it's in enough that it sits flat. I think this is how I slightly bent mine.

brand new Galaxy S4 with battery problems and no help from Samsung!

Hi Everyone
I’ve bought yesterday a brand new Samsung Galaxy S4 here in Brazil (model GT-I9515L, it’s a Snapdragon 600 4G one), and I’m kinda worried about my battery life, which drags 1% every one or two minutes on simple Wi-Fi web browsing, I have been from 100% to zero in less than two hours, and I honestly don’t think that is normal.
I’ve tried a lot of things, I tried disabling some battery dragging features like the gestures, gps and etc, and still got terrible battery life
I’ve noticed that if I sit the phone down idle (screen off but powered on), it doesn’t seem to drag the battery much, when idle it seems equal to my Nexus 4 that I had previously, I'm starting to miss this phone more and more since I got the Galaxy.
The charging time is normal too, it goes from 0 to full in average time, two hours or so.
My phone is in 4.4.2 Kitkat (TouchWiz, unrooted) I’ve haven’t done anything to the phone other than apply OTA updates once it turned on the first time.
I’ve tried doing a factory reset via the settings menu (is this the same thing than reseting from recovery?) and not installing anything after but still got the battery drain problem.
Thinking that it was a faulty battery or phone I’ve brought it back to the store (an official Samsung Store here in Brazil), but they told me that my software was out-of-date, which I thought was strange because both the Software Update menu in phone settings and Kies found no updates to be applied.
I watched them as they put my phone in Odin mode and plugged my phone into one of the store’s computers, opened a program called “samsung master” in order to update my phone, but they couldn’t do it because my “Knox” was somehow messed up (which isn’t because it shows as 0x0) and told me to come back another day when the technician is there.
I became really frustrated with this, so far what I could diagnose was that somehow that my battery drain problem is a software one, and is solved by some kind of update that isn’t available by Kies, just in Samsung stores.
Can you guys give me any directions? I’m open to suggestions and if you guys need any other information, please tell me that I can post here, sorry for my English because I’m brazilian.
Drain almost always applies to when your screen is off. If you don't have drain while your screen is off, then it's perfectly normal.
2 hours of screen on time is perfectly normal. Your screen uses power, not much you can do about that.
Lennyz1988 said:
Drain almost always applies to when your screen is off. If you don't have drain while your screen is off, then it's perfectly normal.
2 hours of screen on time is perfectly normal. Your screen uses power, not much you can do about that.
Click to expand...
Click to collapse
When it's off, the batteery seems to last, but the performance is way worse than on my Nexus 4 (which is known for it's bad battery performance) when it comes to screen time, I've got near the double web browsing time on the nexus.
Your galaxy drains battery like this too? it seems insane to me. 2hours from 100% to zero without any of the features, brightness on the lowest level, only Wi-Fi on, I don't think every galaxy is like this.
When I brought them to the store, the salesperson told me that it had an update to be applied, but when I search for an update or put it into kies it shows me as up-to-date, do you guys know anything about that?
Here you can find the latest
http://www.sammobile.com/firmwares/
Though I doubt a firmware upgrade would change it.
And yes, 2 to 2 1/2 hours screen on time is what I get.

Categories

Resources