Related
Hey all,
My wife and I both have Nexus S phones bought together sometime in Jan. Both phones are running stock Android 2.3.2, no rooting or anything done yet.
Right now her phone is behaving weirdly, while mine is perfectly normal. I suspect that her battery is messed up somehow, but I can't figure out what to do.
For the last day or so, when her phone hits <15% battery, the low battery warning pop-up appears.. and just keeps reappearing. No matter how many times the pop-up is acknowledged, the pop-up just does *not* go away until we connect the phone to a charger. Sort of an aggressive warning
This means that the phone won't let itself be put to sleep, keep the screen turned off or anything -- unless we connect the phone to a charger. I feel as though the battery is charging slowly, but I can't be sure.
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display. This behavior goes away if the phone is connected to the charger. My phone does not show this behaviour - display goes off the moment I press the power button, regardless of charging status.
Any thoughts?
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S? We removed the battery and put it back in (which is basically a soft reset apparently) and now it seems as though the battery has lost calibration or something. Have not done a hard reset yet -- should I go ahead and try that too?
Thoughts/help much appreciated. This is very worrisome!
satishev said:
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display.
Click to expand...
Click to collapse
Sounds like it has a glitch in the software. Try wiping everything. Go into settings, unmount the USB memory, erase the USB memory, then do a factory reset. That will reload the firmware back into active memory for the phone and wipe anything out of the USB memory that might be causing this issue. I usually do a factory reset with a new phone after I play with it for a while anyway, and it doesn't hurt the phone at all. You simply lose your texts, contacts, photos, etc. Just copy or backup anything you need to keep and wipe it clean.
If that doesn't fix it, then you need to get it replaced.
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S?
Click to expand...
Click to collapse
Once you do a factory reset, turn off the phone and fully charge it using the supplied AC charger (don't use the computer port to charge), unplug it and wait a minute then re-connect the charger again for another hour, unplug it, turn on the phone and start using it.
Let us know if the reset fixes the issue.
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
satishev said:
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
Click to expand...
Click to collapse
Well a factory reset is a lot easier and faster than a return/exchange and accomplishes the same thing.
A new symptom has just surfaced -- right now, when my wife tries to lock the phone, it locks the screen but won't switch off the display. No matter how many times the phone is restarted, or the lock button is pressed, the display never actually goes off (timeout has been varied from 15 secs to 1 minute, to no avail). Phone was completely charged as of today morning, so its not popping any low battery warnings.. just not switching off display.
It definitely seems like a battery/software glitch of some kind. We've not done the factory reset yet (she's at work, and this just started happening). Just thought I'd keep the thread updated.
I went ahead and factory reset the phone, as well as manually installed the 2.3.3 update. Figured between the system reset and the update, something should get fixed
Restoring settings was relatively painless (love how everything just gets set up the way it was due to backing up everything with Google). We have the phone charging now (overnight), will update again tomorrow morning once its full charged and my wife is using it as normal.
Fixed?
Hey @satishev
I have the exact same problem, did yours get fixed?
thanks
Hey crobbie, sorry I forgot to update the thread.
After factory reset and update to 2.3.3, the phone has been working normally (so far). All issues related to battery/display are gone! Looks like it was some kind of software glitch that was causing it to read battery state incorrectly (Another symptom I had noticed was that on alarm/dock mode it would keep flashing a charging icon, despite no charger being connected). Initially after reset, the battery usage was acting wonky, but that worked itself out and everything is showing what I expect.
If interested, a blog post summarizing process/ZIPs for all updates to date can be found here.
Thanks, bfksc for all your help
Hi Guys.
Hooray! My TF finally turned on again this morning after 1 and a half days of not turning on.
Is there any way to clear/reset/wipe battery stats without being rooted. As in previous posts, my TF thinks the battery is dead when I restart it even though it is either full or nearly full. Thought I would try and wipe the battery stats to see if that helps. I don't want to root as I may have to send back to ASUS and if I can't turn it back on again, then I can't unroot.
I haven't been able to turn on for a day and a half, nor could I get into APX mode. I did however get the large depleted battery flash on screen when trying to start up yesterday.
Didn't you get a replaced one?
Battery Stats can be deleted from CWM, but I don't know if there's another way of doing it if you're not rooted. Also if you've got a new device, I will suggest you run it a couple of times to see if it works as intended or not before deleting the stats...
AzureusPT said:
Didn't you get a replaced one?
Battery Stats can be deleted from CWM, but I don't know if there's another way of doing it if you're not rooted. Also if you've got a new device, I will suggest you run it a couple of times to see if it works as intended or not before deleting the stats...
Click to expand...
Click to collapse
Hi Azureus.
Unfortunately I couldnt get a replacement as the box it came in was somehow thrown out with the christmas rubbish, so they wont take it back. They will only send it off to Asus for me. Im not sure now whether to root and then wipe stats, Just worried it wont come back on at all.
Seg
IIRC someone else posted something similar a while back.
Try a factory reset before you do anything else.
baseballfanz said:
IIRC someone else posted something similar a while back.
Try a factory reset before you do anything else.
Click to expand...
Click to collapse
Do you reckon factory reset will help? The battery reads fine i android, its just when you try to power up it shows the depleted battery icon sometimes and then doesnt show anything other times, just doesnt start.
Seg
Seg2012 said:
Do you reckon factory reset will help? The battery reads fine i android, its just when you try to power up it shows the depleted battery icon sometimes and then doesnt show anything other times, just doesnt start.
Seg
Click to expand...
Click to collapse
I can't say for certainty, I just remember that's what was posted. Trying to find that post but it's buried somewhere.
At the least it doesn't hurt to try a factory reset. If it still doesn't help than you can root after that.
I think your problem is related to the "deep sleep" trouble more than the battery stats itself.
baseballfanz said:
I can't say for certainty, I just remember that's what was posted. Trying to find that post but it's buried somewhere.
At the least it doesn't hurt to try a factory reset. If it still doesn't help than you can root after that.
I think your problem is related to the "deep sleep" trouble more than the battery stats itself.
Click to expand...
Click to collapse
Cheers Baseball.
I was reluctant to do a factory reset as this would require a restart and I really didnt want to wait a day and a half for the damn thing to start back up again. While I was at the shop today, I got them to check the charger, he in turn said it wasnt working and gave me a new one. Strange how my battery was telling me that I had 99%. Anyway, I bit the bullet and downgraded to .19 so I could root again and do the wipe battery stats. Low and behold, after my TF turned off to restart and do the install of the .19 software, it didnt turn back on. So I thought I would plug it in and then press the power button as this had become the norm. To my amazement, after plugging in and before I could press the power button, the TF fired up and continued to install the downgrade. Hooray!!!
I am now just pumping in the last 2% of battery needed then going to wipe cache, date, dalvik and battery, then hopefully, and I say this with fingers crossed, that that might be the end to my issues.
Seg
I found those sudden reboots happening on my device, XT1033 with ART unrooted running the single sim firmware. Everything was fine for a long time, but the last weeks its been happening. It simply freezes, no matter doing what going into a point that when I press the power/lock, the screen won't even turn itself back on, forcing myself to force-reboot in order to work again. I also notice that when it happens, the device has a downfall in the battery graph even tho not much was consumed and even losing a couple minutes on the screentime. I will embed a photo.
Maybe switching back to Dalvik fixes it? Or something else is the issue? I got no "weird" apps installed. Suggestions?
Nobody?
Before to think if it's a battery problem you have tried to switch to dalvik and see what happens on long time?
denzel09 said:
Before to think if it's a battery problem you have tried to switch to dalvik and see what happens on long time?
Click to expand...
Click to collapse
Not exactly, mainly because it never happened before. I am using ART since it updated to KK, started recently only.
rogeriorp said:
Not exactly, mainly because it never happened before. I am using ART since it updated to KK, started recently only.
Click to expand...
Click to collapse
Can you grab logcat log? Maybe it can say something when it happens.
The best way to do this is by Eclipse -> CatLog viewer. You won`t loose log messages when device will be rebooted.
Did you try wiping cache / dalvik ? System will rebuild everything so you won`t loose your data and it can fix your problem.
Cheers,
fabus said:
Can you grab logcat log? Maybe it can say something when it happens.
The best way to do this is by Eclipse -> CatLog viewer. You won`t loose log messages when device will be rebooted.
Did you try wiping cache / dalvik ? System will rebuild everything so you won`t loose your data and it can fix your problem.
Cheers,
Click to expand...
Click to collapse
I did only wipe cache partition before, never the dalvik. I might give it a try the next time it happens.
Also, to catch a logcat requires root? If so I can't grab one.
rogeriorp said:
I did only wipe cache partition before, never the dalvik. I might give it a try the next time it happens.
Also, to catch a logcat requires root? If so I can't grab one.
Click to expand...
Click to collapse
Try catlog, i don't remember if need root honestly
Alright, got the guidances. Thank you both for the help, will leave some feedback later on.
An update: it happened twice in a row just now. Switched back to Dalvik just in case. Will keep this one post updated to not spam.
rogeriorp said:
I found those sudden reboots happening on my device, XT1033 with ART unrooted running the single sim firmware. Everything was fine for a long time, but the last weeks its been happening. It simply freezes, no matter doing what going into a point that when I press the power/lock, the screen won't even turn itself back on, forcing myself to force-reboot in order to work again. I also notice that when it happens, the device has a downfall in the battery graph even tho not much was consumed and even losing a couple minutes on the screentime. I will embed a photo.
Maybe switching back to Dalvik fixes it? Or something else is the issue? I got no "weird" apps installed. Suggestions?
Click to expand...
Click to collapse
I just unlocked, rooted, flashed recovery and custom ROM on a refurb unit. I had kinda the same issue with this phone out the box stock. Mine will work perfect as long as its plugged in to either PC or wall charger. Once unplugged, pushing power to wake causes screen to shutoff after a few seconds or freeze, then reboot. Doesn't seem to be software related, as a clean install of pacman did nothing different. Touchscreen gets very unresponsive, also causing reboots.
sent from my Gs3
rogeriorp said:
An update: it happened twice in a row just now. Switched back to Dalvik just in case. Will keep this one post updated to not spam.
Click to expand...
Click to collapse
- LogCat requires root to see system messages, otherwise you will see only high layer user messages.
- I tryied ART and didn`t have such issue, just came back to Dalvik because I noticed that ART uses more cache (which impacts overall virtual SD capacity) and didn`t see any improvement in performance.
@joeyhdownsouth - could you give us logcat / dmesg log on some share? It seems you have some issues while charging. It can be causes either by wrong charger (too high/low current, but moto should control it) or maybe some app causes this when you unplugs usb cable.
Anyway - without log we cannot say anything.
Cheers,
I have this phone for 4 months already, its weird it happens out of no where tbh. Switched back to Dalvik yesterday and no issue yet, switching runtimes compile them all over again right?
rogeriorp said:
I have this phone for 4 months already, its weird it happens out of no where tbh. Switched back to Dalvik yesterday and no issue yet, switching runtimes compile them all over again right?
Click to expand...
Click to collapse
yes, you should see "Updating Android" with application number every time you switch DALVIK<->ART.
Cheers,
fabus said:
- LogCat requires root to see system messages, otherwise you will see only high layer user messages.
- I tryied ART and didn`t have such issue, just came back to Dalvik because I noticed that ART uses more cache (which impacts overall virtual SD capacity) and didn`t see any improvement in performance.
@joeyhdownsouth - could you give us logcat / dmesg log on some share? It seems you have some issues while charging. It can be causes either by wrong charger (too high/low current, but moto should control it) or maybe some app causes this when you unplugs usb cable.
Anyway - without log we cannot say anything.
Cheers,
Click to expand...
Click to collapse
Waiting on Motorola charger to come in, then if no change, I'll pull a logcat.
sent from my Gs3
I also experienced the last 3 days complete freezes. No idea what was going on...
Unfortunately I couldn't pull any log messages from the phone by that time. Half an hour later it just responded normally... Didn't see if it rebooted in between or what exactly happened
Just a heads up: going back to Dalvik got me rid off those freezes. Something on ART was messed up.
rogeriorp said:
Just a heads up: going back to Dalvik got me rid off those freezes. Something on ART was messed up.
Click to expand...
Click to collapse
I never even checked to see which one it was using when I first got it.
sent from my Gs3
joeyhdownsouth said:
I never even checked to see which one it was using when I first got it.
sent from my Gs3
Click to expand...
Click to collapse
By deault it is Dalvik. If you have new phone so it will be Dalvik.
Did you said two posts before that you were using some 3rd party charger (not Motorola cable)?
Funny, but yesterday I had similar issues with freezes and random reboots. I was using some cable taken from Friend (not Motorola) and weird things started to happening:
- It was indicated on a screen that phone is charging (probably discovered usb cable plugged it), but it was discharging faster and started rebooting (because it reached below 1% battery state) and after some reboots battery was so discharged that phone couldn`t come up.
This usb cable was attached all the time to my phone and a computer.
- Next I connected phone to my reglar charger for night (from Zte Tablet, but really good and charges fast, never had issues with it) and it was fully charged.
On the morning I played music for 15 minutes by loudspeaker and then put phone into my pocket for 10 minutes (walk to take a bus).
When I took my phone back into my hand battery was dropped to 1%! (from over 95% to 1% in 10 minutes), but phone didn`t shut down.
This 1% remain for couple of hours (something like 2-3) without shutting phone down.
I took another charger and connected to it again - phone was charged to 100% in less than 30 min (usually takes up to 3hrs) and now works like before (no huge and weird battery drain).
Btw. I`m on faux kernel 007m.
Weird... looks like moto g doesn't like be connected to a PC by other cable than Motorola
For quite a long time I did not make any change on Nexus ROM or applications, but yesterday my Nexus turns off while I was web browsing. I tried to turn it on but it refuses. It is only possible with USB cable plugged in, but then it constantly turns on for 1 second and then turns off, and this is going in endless loop as soon as USB cable is plugged in. But with unplugged cable NEXUS can not be powered on.
The video can be seen on this link
https://www.dropbox.com/s/cvyxii4ctm4aqgu/VID_20141110_190522.mp4?dl=0
Yesterday I somehow manage to get in recovery mode and I wipe cache and Nexus boot ROM, but after 30 minutes of usage it again turns of by itself. After that for more than 100 times I tried to get to recovery mode but I could not.
So, I think that my only chance to wipe cache and put new ROM is through ADB. But I do know how to do that. Can anyone help me?
P.S. I both my NEXUS in US, but I live in Croatia (EU) and Google tells that they can not make exchange for other NEXUS (although my phone is under warranty) because they can only do that for postal address inside US. Because I do not live there and any of my friends or relative will travel in US soon my only way to get my NEXUS working is through ADB.
sounds as your power button is "stuck'.
Try the LG RMA. Worked for me here in Belgium
brom25 said:
Try the LG RMA. Worked for me here in Belgium
Click to expand...
Click to collapse
Where did you both your Nexus, and in which country did you send RMA request?
DTFuser said:
For quite a long time I did not make any change on Nexus ROM or applications, but yesterday my Nexus turns off while I was web browsing. I tried to turn it on but it refuses. It is only possible with USB cable plugged in, but then it constantly turns on for 1 second and then turns off, and this is going in endless loop as soon as USB cable is plugged in. But with unplugged cable NEXUS can not be powered on.
The video can be seen on this link
https://www.dropbox.com/s/cvyxii4ctm4aqgu/VID_20141110_190522.mp4?dl=0
Yesterday I somehow manage to get in recovery mode and I wipe cache and Nexus boot ROM, but after 30 minutes of usage it again turns of by itself. After that for more than 100 times I tried to get to recovery mode but I could not.
So, I think that my only chance to wipe cache and put new ROM is through ADB. But I do know how to do that. Can anyone help me?
P.S. I both my NEXUS in US, but I live in Croatia (EU) and Google tells that they can not make exchange for other NEXUS (although my phone is under warranty) because they can only do that for postal address inside US. Because I do not live there and any of my friends or relative will travel in US soon my only way to get my NEXUS working is through ADB.
Click to expand...
Click to collapse
Shake your phone vigorously for a minute, I've been using that as a temp fix for a dodgy power button exactly as you've described
topgeardave said:
Shake your phone vigorously for a minute, I've been using that as a temp fix for a dodgy power button exactly as you've described
Click to expand...
Click to collapse
And what you did after shaking? I try but I did not helped.
DTFuser said:
And what you did after shaking? I try but I did not helped.
Click to expand...
Click to collapse
It usually helps the button back out again, I think you should RMA to LG, I'm sure they're worldwide. You could always open up the phone and try unsticking the power button if you can't be bothered sending it back.
topgeardave said:
It usually helps the button back out again, I think you should RMA to LG, I'm sure they're worldwide. You could always open up the phone and try unsticking the power button if you can't be bothered sending it back.
Click to expand...
Click to collapse
Power button is not what cause the problem. I found many reports about the same problem, like on this page
http://www.reddit.com/r/Nexus5/comments/29tr5n/nexus_5_wont_turn_on_google_screen_keeps_flashing/
but nothing which I tried did not helped. But certainly power button is not causing the problem.
When the problem appears for the first time I manage to get into recovery and wipe cache, and after that phone booted ROM. After 30 minutes of working phone turns off and now I'm not able to get even into recovery.
DTFuser said:
Power button is not what cause the problem. I found many reports about the same problem, like on this page
http://www.reddit.com/r/Nexus5/comments/29tr5n/nexus_5_wont_turn_on_google_screen_keeps_flashing/
but nothing which I tried did not helped. But certainly power button is not causing the problem.
When the problem appears for the first time I manage to get into recovery and wipe cache, and after that phone booted ROM. After 30 minutes ow working phone turns off and now I'm not able to get even into recovery.
Click to expand...
Click to collapse
Ah damn, sorry to hear mate. Go to LG, only solution you have left.
im in the same boat my phone was just working for the past since i had it and now just like 20 minutes ago it just shut off and now doing the constant turning on and off crap
and im rooted with the latest build from pac-man (a clean install), cant even get into the fast boot and recovery to recover to stock since its doing this bootloop thing
any more help would be amazing
Edited - problem fixed it was something up with the power button, got a couple hard wacks and it booted up perfect
meechieballer said:
im in the same boat my phone was just working for the past since i had it and now just like 20 minutes ago it just shut off and now doing the constant turning on and off crap
and im rooted with the latest build from pac-man (a clean install), cant even get into the fast boot and recovery to recover to stock since its doing this bootloop thing
any more help would be amazing
Edited - problem fixed it was something up with the power button, got a couple hard wacks and it booted up perfect
Click to expand...
Click to collapse
So, since shaking, hard wacks, and anyting physical did not helped after your post I dismantle my phone and without back plate and upper plate on chips my phone works perfectly. So it seems that upper plate which covers chips is the cause of the problem.
For me, not even disassembling has helped, so I bought another motherboard and put it into my phone.
Dancsi said:
For me, not even disassembling has helped, so I bought another motherboard and put it into my phone.
Click to expand...
Click to collapse
the problem occured and i found what it was my power button it wasnt staying in place like its tilting so now i got to buy a new button for it :/
As far as I remember, the button is soldered to the board, and can not be bought separately. I know the second thing for sure, since I was also only searching for a separate button in the beginning...
Hi,
I bought Z5 3 days ago and I noticed little(?) problem with my battery. It is unable to charge above 98% (stops at 96 to 98). Should I worry about?
Reboot, charge again.
Battery needs time to settle
Sent by XDA fax
Does quick the quick charge 2.0 thing just work always or do you have to turn it on somewhere?
Sent from my Xperia z5 by Tapatalk
Duvel999 said:
Reboot, charge again.
Battery needs time to settle
Sent by XDA fax
Click to expand...
Click to collapse
I've tried restaring twice without positive effect so far.
Never had such problem with ANY device EVER.
I´d recommend a complete and total RESET of the device. Of course you´ll loose all your data on the device
AND I can´t tell if that helps, but there is no better idea to get rid of that annoying behaviour of the device. Sorry.
Possibly you got lucky and got a defect one
DJ-Tumor said:
Never had such problem with ANY device EVER.
I´d recommend a complete and total RESET of the device. Of course you´ll loose all your data on the device
AND I can´t tell if that helps, but there is no better idea to get rid of that annoying behaviour of the device. Sorry.
Possibly you got lucky and got a defect one
Click to expand...
Click to collapse
OK, just a made simple step... Turned off Z5 and left it for charge. It charged successfully to 100%
Now had not charging problem on my Z5 premium,
Restarted, reset , data wipe etc..
xperia companion reset, now does not even connect to computer
seems to be bricked.
any other suggestions?
first try clearing cache partition which can also help calibrate the battery (power button and volume up until you feel 3 vibrations)