Related
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.
Since I have got it (2 weeks ago) i have picked up my phone make a call, and on about 7-8 occasions, have noticed that the phone is turned off, and I can't get it to turn on. The only solution is to take out the battery and put it back in. Has anyone else experienced this. I have updated to JH2 firmware, but it still happens. I even got a new battery for the phone (Bell employee let me swap with another phone that was going back to samsung for gps issues), but the problem still happens once in awhile (like every 2 days, sometimes more sometimes less). Anyone have any ideas? thanks
UPDATE: Someone mentioned for me to call my phone the next time this happens to see if it rings. They said it might stuck in sleep mode? Not sure, i just pullthe battery and then it works
I've had this happen, but only when the GPS was on. If it's happening with the GPS off, I'm guessing you've got a lemon.
So far I've not needed to take the battery out, though. I've always been able to reboot by holding the power button down for 5-10 seconds instead.
Yes I have been experiencing the same problem. From what I can see, it seems like the phone is over heating then it locks up. My only fix was to install a battery temperature monitor and also kill any tasks that are not needed by the phone. My phone hasn't locked like that since I've been doing that.
Sent from my GT-I9000M using XDA App
I have not had this problem. Been on a call for about 1-2 hours one time and the phone was fine. I was able to switch it to speaker, bluetooth, open other apps, and etc without any problems. I don't run task managers. I do have one, but I rarely use it.
Interesting...I experienced this for the first time today. Picked up my phone from teh night stand after having it plugged in all night and it was off. Had to pull the battery to get it to come on. The battery was about 85% charged when it came back on. It worked ok since but the battery drained kinda quick. I am using an aftermarket battery, got the 2 batts and charger on ebay. So I put the other battery in and havn't had any issues. I wonder if it over heated while charging? What apps are you guys running? The one I am running that would be most suspect would be weatherbug elite, and I just installed it a day or 2 before this happened.
I think it is a GPS issue. I got this phone on the first day of release. I’ve never had this problem until just days ago. I hadn't used the GPS extensively before last Thursday and Friday. During my business trip I had the GPS on for almost two days straight and during these two days I experienced the blank screen, shut down twice. I had to cycle the battery to get it to boot.
I had this happen to me while using Set CPU. Check out this thread. http :// forum.xda-developers.com/showthread.php?t=727006
take out spaces and what not.
I had this problem on my g1 but it started to get worst an I soon need too keep my mobile always connected to a charger so out turned into a landline phone lol but it was because I somehow broke a middle cell in my battery and need replacing but I don't know what to say about yours cause you tried a different battery :S
Sent from my T-Mobile G1 using XDA App
Experienced a freeze just a few hours ago while running the navigate application.
Trying to show my wife how uber cool it was and all. Switched on GPS, launched maps, chose directions, method / navigate. GPS locked and had my location pinned down until I reached the corner and suddenly the GPS kicked me to a location about 5 blocks away then froze the phone, requiring a battery pull and reboot.
Sent from my SGH-T959 using XDA App
I've been trying hard to avoid the Epic update, since my phone was working great. I was getting almost 20 hours battery before being asked to charge, using about 30 minutes phone calls, 1 hour "display on" time, bluetooth/wifi off, GPS only when needed.
The nagging update available message would always pop up, and I'd always tell it to install later.
Somehow, I must have accidentally selected update while getting out of the car today, since I saw the phone installing firmware and then reboot.
After the reboot, my Sprint Hotspot stopped working. Now when I activate it, it turns my 3G radio off. Prior to this, I could activate (and use) Sprint Wifi tethering even though I am not specifically subscribed to it. Now, it still "activates" but shuts down my data connection.
Even worse, when I try to activate 4G, it just hangs the phone. I tried factory resetting, which did not solve the problem. Still no more 4G. Also, I noticed my battery getting really hot, and the smell of smoke inside the case. The battery went from 50% to 9% within a minute!! I don't have any explanation on how the update caused this.....
This update fried my phone! I'm going to try the Odin method back to DG27. If that doesn't work, the phone is going back!
DO NOT UPDATE if you can avoid it!!
that sucks
I'm having a really really hard time believing the ota update had anything to do with anything you described.
Sent from my SPH-D700 using Tapatalk
styckx said:
I'm having a really really hard time believing the ota update had anything to do with anything you described.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Me too, but I don't know what else could have caused it. Just tried Odin, still can't get 4G to work.
I don't think there's much else I can try. The phone just hangs when I enable 4G. Tried factory reset, Odin back to DG27. No luck.
Any ideas?
Dont listen to this guy -- you want the DI07 update on your phone. It has vital improvements to the radio and kernel. It doesn't break 4G or ruin battery life.
it has happened to many of us,including me..i also started a thread in the development forum..i talked to a service rep and they instructed me to do a msl reset,which required a msl code the give and no luck..this happened to me last week.since then i swapped my phone for another unit an was weary of updaing again,but i did and everything works fine now.im guessing a bad batch of phones or bad dowload/install of update ota.return it for another
Sent from my SPH-D700 using XDA App
Before the update, I was getting about 14-15 hours of battery with my average daily use. After the update I'm swapping batteries every 6 or 7 hours. I started tracking power consumption a few days ago with Spare Parts. I flashed back to stock with odin, and installed the DI07 update. The only apps I installed were Battery Indicator Pro and Spare Parts. I noticed right away that the running time was always close to 100%. That means that the phone is not sleeping. Under "Partial Wake usage", Android System is running almost the same amount of time the phone is powered on. It's not spiking the CPU, but running just enough to create a partial wakelock. This behavior is consistent on every boot. Normally, Android System should only keep the system awake about 3 or 4 minutes per hour of uptime at most. I think they botched something in the update.
Tonight I reverted back to DG27 and the problem is now non-existent. I only have one Epic to test, so I'm curious to see if anyone else gets different results. If it's just my Epic, then I will be returning it for another.
Anyone feel like experimenting?
I'm going on 18 hours now since I reverted back to DG27 and I'm still on the same battery. I would be on my third battery right now if I was still running DI07. I don't think I'm gonna be updating till Sprint releases another fix. Other than Media Hub and the loss of battery life, I noticed no changes while running DI07.
Sent from my SPH-D700 using Tapatalk
I'm getting over 18hrs since update. It maybe just like the HTC phone when you flash the rom the battery life goes down for the first few full charges then after that it's fine. Maybe I'm just lucky because I'm not having all the drama you guys and others are having.
infamousjax said:
Dont listen to this guy -- you want the DI07 update on your phone. It has vital improvements to the radio and kernel. It doesn't break 4G or ruin battery life.
Click to expand...
Click to collapse
Any why should we listen to you? Can you describe your source of knowing how this update has "vital improvements" to the radio and kernal? What are the nature of these improvements?
Thanks
-Everyone
Not sure what the particular improvements are... but check your phone info and you will see that the baseband was changed, which means a new radio was implemented. Also, in the release notes it specified that there were some "Qualcomm Updates", and since Qualcomm engineers the radio in our phones, it doesn't take much brain capacity to put 2 and 2 together.
I've updated and have experienced none of these problems. (As I suspect is true of most of the people here.)
infamousjax said:
Dont listen to this guy -- you want the DI07 update on your phone. It has vital improvements to the radio and kernel. It doesn't break 4G or ruin battery life.
Click to expand...
Click to collapse
It ABSOLUTELY ruins battery life. If it doesn't ruin your battery life specifically, then your one lucky sun of gun. It cut my battery life in half. I used to be able to go to 11pm and never even get a battery warning! Now, my phone completely shuts down by late afternoon while I'm still at work. DI07 is a horrible update. I don't know what Samsung/Sprint did, but my screen is dimmer, battery life took a major dump, and the phone does not seem any faster, actually slower if anything. My phone also seems to be hot all the time, even after it's supposedly been asleep for hours. With DG27 it was always felt cool when pulling it out of my holster and not hot like it is now.
Testing...testing
After running DG27 for almost 24 hours with great results, I decided to give the DI07 update another shot. But first I made a Nandroid backup in CWM before I accepted the update. After about two hours on DI07, it was clear the phone was not sleeping again when the screen was off.
So now I'm gonna try another experiment. I've done a system restore from my Nandroid backup to DG27. Except that the Baseband(radio) is still DI07 because Nandroid doesn't touch the radio. I'm thinking that this will tell us if the new radio is the culprit, or if they just botched something in the DI07 ROM.
Dev's, let me know if I'm off base here. I will report as soon as I have any relevant results.
compujock said:
It ABSOLUTELY ruins battery life. If it doesn't ruin your battery life specifically, then your one lucky sun of gun. It cut my battery life in half. I used to be able to go to 11pm and never even get a battery warning! Now, my phone completely shuts down by late afternoon while I'm still at work. DI07 is a horrible update. I don't know what Samsung/Sprint did, but my screen is dimmer, battery life took a major dump, and the phone does not seem any faster, actually slower if anything. My phone also seems to be hot all the time, even after it's supposedly been asleep for hours. With DG27 it was always felt cool when pulling it out of my holster and not hot like it is now.
Click to expand...
Click to collapse
Heres what will help:
Run the root script, delete all sprint bloatware, and keep track of all the services running on your phone. I'm getting 20 hours of battery with heavy usage on the DI07 update.
Also, try the bump charging method which has helped me a lot. Turn the phone on, let it fully charge, unplug, let it fully charge, turn back on.. rinse and repeat. It helps.
The update is not what is causing bad battery life. The screen dimming is part of the auto-brightness setting and/or power saving setting which should be helping the battery more than killing it.
Get System Panel/spare parts or any kind of task manager to MONITOR (not kill) processes running on your phone.
Here's a post from another forum, so I'm not the only person with a dead 4G radio. I believe it was temporally related to the update, but reverting back to DG27 didn't fix it.
Link: http://forum.androidcentral.com/sprint-epic-4g/36985-4g-doesnt-work-after-di07-update.html
"I have been out of town in a non-4G area since applying the DI07 update. Got home earlier today and just went to turn on 4G and it no longer is working!!
When I enable 4G (through the pull-down or the settings menu) now it just says "On..." and then "Unknown..."
Anyone else that has applied the update and lives in a 4G area seeing similar behavior?? I am currently backing up me SMS messages so I can do a hard-reset to see if that will fix it."
infamousjax said:
Heres what will help:
Run the root script, delete all sprint bloatware, and keep track of all the services running on your phone. I'm getting 20 hours of battery with heavy usage on the DI07 update.
Also, try the bump charging method which has helped me a lot. Turn the phone on, let it fully charge, unplug, let it fully charge, turn back on.. rinse and repeat. It helps.
The update is not what is causing bad battery life. The screen dimming is part of the auto-brightness setting and/or power saving setting which should be helping the battery more than killing it.
Get System Panel/spare parts or any kind of task manager to MONITOR (not kill) processes running on your phone.
Click to expand...
Click to collapse
Infamous,
These are all good suggestions for basic power management under normal circumstances, but for some reason this update has introduced an issue that causes the Android System process to prevent the phone from sleeping. Why it's not affecting everyone I don't know. Some people had to take their phones back to the Sprint store after the update because they got so hot and would not cool down unless turned off.
Anyway, if you are getting 20 hours on heavy use, you obviously don't have the bug. But to anyone who thinks they might, you can check using Spare Parts.
First, if you've just rebooted, turn the screen off and let it sit for a few minuets. Open Spare Parts and click Battery history. By default it displays 'Other usage'. If your 'Running' percentage is 100% or close to it, and your 'Screen on' percentage is anything other than your 'Running' percentage, then your phone is not sleeping when the screen is off.
Next change the top tab from 'Other usage' to 'Partial wake usage'. This will show you what is preventing it from sleeping. You can click on whatever is at the top of the list to see its partial wake time. If it's 'Android System', the partial wake time should not be any more than about 1 minute per hour of system uptime. For example, if your phone has only been on for 10 minuets, and 'Android System' has a partial wake time of 2 minutes, you have a problem.
Found more info here.
http://forum.androidcentral.com/sprint-epic-4g/37034-those-batt-issues-after-upgrade.html
This is great info, according to Spare Parts and your info, I have a severe problem. I have just killed DRM
The update went through automatically Sat night, battery has dived at least
50%. Reboot at that time.
Battery History
Total in all Time Since Reboot (2 days)
Running 30.5% 99.7
Screen On 16.7 18.3
I see the problem, don't know if DRM dead will fix, is there anything else I can do?
I am rooted (or at least I was, I stayed stock and added Wireless Tether, it is broken). So not happy there either.
I will charge and check this tomorrow to see what changes or if there are any other suggestions.
Thetwo apps running none stop are I! Agent Service in Android System and GTalkService in Goggle, using over 10 mb ram
Other usage is still almost 100%, Screen time has gone down, but Wifi On is same as Running and I have it turned off every which way I can find as with nothing showing on top bar.
Partial Wakelock: Andoid System is on 113 hrs of25 since boot.
**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.
Hi
I have recently started having a problem with what I presume to be the battery of my Nexus 4. It seems to have started suddenly about a week ago, though was working absolutely fine before. I don't think it was due to any specific app having been installed. I have also done a factory reset on it, but that didn't solve the problem.
Basically, the battery will discharge to about 75%. The phone will then suddenly switch off; turning the phone back on, it simply shows the battery to be fully depleted and switches off. If I plug it into a power source, the phone turns back on and begins charging, from 0%, though seems to suddenly fully charge it within about half an hour.
My phone has not been rooted.
I would really appreciate any help/advice on this issue as it is incredibly frustrating having to have my phone almost permanently on charge.
I have attached two screenshots of the battery usage graph.
Thanks!
bab88 said:
Hi
I have recently started having a problem with what I presume to be the battery of my Nexus 4. It seems to have started suddenly about a week ago, though was working absolutely fine before. I don't think it was due to any specific app having been installed. I have also done a factory reset on it, but that didn't solve the problem.
Basically, the battery will discharge to about 75%. The phone will then suddenly switch off; turning the phone back on, it simply shows the battery to be fully depleted and switches off. If I plug it into a power source, the phone turns back on and begins charging, from 0%, though seems to suddenly fully charge it within about half an hour.
My phone has not been rooted.
I would really appreciate any help/advice on this issue as it is incredibly frustrating having to have my phone almost permanently on charge.
I have attached two screenshots of the battery usage graph.
Thanks!
Click to expand...
Click to collapse
If you are on stock, try flashing the stock image(4.2 or 4.3 up to you) there's plenty of threads on here thatll guide you thro the process.
I've had the same issue about three times, during the first week of using my Nexus 4 (about half a year ago). I've already had my mind made up to RMA it, but waited for it's shut-off to happen once more to collect some evidence of this problem and... it never happened again. I'm pretty confident that I didn't install anything that might have helped (I only installed BetterBatteryStats to check the instant drain, but really doubt it could change anything, it's just statistics), and I've never factory wiped the phone's data yet.
I've been searching for answers around the internet back in May, but never found anything of value, so my only advice is... wait a little, and if it doesn't get better itself return it to the merchant. My previous HTC phone was restarting almost everyday from the first day I bought it, until a month later I returned it for warranty repairs and after they changed almost all internals of the phone it never crashed again (till today, since I still use it as GPS and media player when running).