Gidday - This morning I woke up to find my phone had switched itself off during the night while on charge.
Last night I put my phone to charge through USB connected to my PC in sleep mode. I've been charging the phone like this since I got it 3 weeks ago and its been working fine.
When I woke up in the morning I found the phone off and when I gave the power button a short press expecting it to show me the time all I got was a battery charging symbol.
When I went to bed I had the standard "Clock" feature running that comes standard with the Neo so it acts like a bedside clock and I always have the Wifi on when I'm at home.
No other applications were running in the background apart from the normal stuff but I'm quite concerned that the phone turned itself off while I was sleeping because I use the alarm feature to wake me up when I need to go to work and I know these Android phones do not wake themselves up to run the alarm.
Any ideas what could be causing this?
Now this is very funny you say this because this happens to me,,, but I'm convinced I turn it off myself,in my sleep my partner confirms lol
But seriously could of just been a reboot
As long as it don't happen again it should be no great consern ''unless you sleep in for work'' lol
Sent from my Xoom using xda premium
I heard charging like this(from night to morning) is not good for the battery.The owner of the shop where I brought my W595,Neo V specially told me NOT to do this,as he said this can reduce both battery life and phones life.Anyway don't get that much concerned about itself switching off mate after only happening it once.But if can in future don't charge like that.
lol kormatoes ,I on the other hand when ppl call in night sometimes I was told that I just answer it and instead talking keep it beside my pillow thinking it was alarm and go back to sleep xD
Was the phone fully charged when you woke up? If not I would guess something went wrong with the laptop..
I've never left my phone plugged into a laptop for charging, I always use the wall plug overnight.. And don't worry, plugging your phone in every night is not bad for your battery it control's the charge and drops down to 98% when it gets to 100% before charging again.. This trickle effect on a li-ion battery is fine (would have been bad for nicad or nimh tho) and your using a laptop usb which only delivers about 500ma that's a really nice slow (low C) charge rate, li-ion and li-poly batteries love to keep topped up, what they hate is to be discharged to much. (my 2c)
If you're really worried about this (random shutdown) happening on a work day then use the wall charger the phone came with.. Just to eliminate any other factors that might have contributed to it turning off (use the laptop on your days/nights off to try and replicate the fault) would be interesting to figure it out what caused it..
Kiwi
Sent from my MT15i using xda premium
Thanks for your comments guys.
I'm not sure why charging it via usb is going to do it any harm? or was the guy in the shop trying so say that its not good to have the phone plugged into the charger for hours on end once it gets fully charged? either way I've been thinking that charging via usb is better for the battery because its a lower energy input and therefore charges the battery slower/cooler which in turn should make it last longer (just guessing here - no science to back this up)
Then there is the having it plugged in while at 100% - I've noticed that the phone somehow disconnects itself and stops charging the battery when at 100%. I noticed this today when I started my phone after its surprising shutdown = the battery was fully charged (because it had been plugged in all night) and the battery display refused to show me that the phone was plugged in (when it was) so I turned on the flash light feature and blasted some music to drop the %tage down and sure enough as soon as the percentage dropped below 100% the indicators on the phone started to show the batter was charging (both via the lightening bolt in the normal battery icon and also on my battery monitor which tells me if its charging and how much longer it will be charging for).
I'm looking forward to seeing if the phone is still on tomorrow when I get up.
Any more ideas much appreciated - once might not sound like much but if the alarm/phone had the potential to be even the slightest bit unreliable then I'm going to have to go back to the old alarm clock. At least with my Nokia I could even switch the phone off and the alarm would still chime (we've all experienced this with the old school phones) but I notice that android hasn't managed this yet.
kiwiBratwurst said:
Was the phone fully charged when you woke up? If not I would guess something went wrong with the laptop..
I've never left my phone plugged into a laptop for charging, I always use the wall plug overnight.. And don't worry, plugging your phone in every night is not bad for your battery it control's the charge and drops down to 98% when it gets to 100% before charging again.. This trickle effect on a li-ion battery is fine (would have been bad for nicad or nimh tho) and your using a laptop usb which only delivers about 500ma that's a really nice slow (low C) charge rate, li-ion and li-poly batteries love to keep topped up, what they hate is to be discharged to much. (my 2c)
If you're really worried about this (random shutdown) happening on a work day then use the wall charger the phone came with.. Just to eliminate any other factors that might have contributed to it turning off (use the laptop on your days/nights off to try and replicate the fault) would be interesting to figure it out what caused it..
Kiwi
Sent from my MT15i using xda premium
Click to expand...
Click to collapse
Thanks for your thoughts Kiwi (I've only just figured out who this is ) - The laptop was in sleep mode and from what I've experienced the only thing that works when in this mode is the usb ports - the Wifi and the Bluetooth shut down and I'm guessing that the processor mostly shuts down too? guessing here?
But even so what on the computer might cause the phone to crash?
hilfordjames said:
I'm not sure why charging it via usb is going to do it any harm? or was the guy in the shop trying so say that its not good to have the phone plugged into the charger for hours on end once it gets fully charged?
Click to expand...
Click to collapse
Sorry if my earlier post was confusing,he told me its not good to have it plugged into the charger for longer periods of time after its fully charged.I too normally charge it with pc as phone came with one usb cable + charger plug with usb port & usb cable is always attached to my pc.Anyway about that keeping it for the whole night is bad theory I'm not sure if its correct or wrong but I prefer not keeping it plugged in for like 6-7 hours everyday while it only need 2-3 hours maximum to fully charge.
But even so what on the computer might cause the phone to crash?
Click to expand...
Click to collapse
Normally if phone crashes it reboots right ? instead switching off ?
Thilina said:
Sorry if my earlier post was confusing,he told me its not good to have it plugged into the charger for longer periods of time after its fully charged.I too normally charge it with pc as phone came with one usb cable + charger plug with usb port & usb cable is always attached to my pc.Anyway about that keeping it for the whole night is bad theory I'm not sure if its correct or wrong but I prefer not keeping it plugged in for like 6-7 hours everyday while it only need 2-3 hours maximum to fully charge.
Normally if phone crashes it reboots right ? instead switching off ?
Click to expand...
Click to collapse
I've noticed that when you reboot while plugged in, it might just go right into charge mode. Try turning it on, and then plug it in righ thereafter. Likely it will not boot, but go to the charge animation.
Can't try it myself, phone's in for repair
sdk16420 said:
I've noticed that when you reboot while plugged in, it might just go right into charge mode. Try turning it on, and then plug it in righ thereafter. Likely it will not boot, but go to the charge animation.
Can't try it myself, phone's in for repair
Click to expand...
Click to collapse
Hmm interesting theory - but I've tried it and the phone has restarted : (
Probably a good thing but still no closer to finding the solution except I'm wondering if it was because my ROM memory was pretty much full? So in case it was I've moved a few things from System apps to User apps in the hope that the phone wont switch off by itself again.
hilfordjames said:
Hmm interesting theory - but I've tried it and the phone has restarted : (
Probably a good thing but still no closer to finding the solution except I'm wondering if it was because my ROM memory was pretty much full? So in case it was I've moved a few things from System apps to User apps in the hope that the phone wont switch off by itself again.
Click to expand...
Click to collapse
If you're rooted, I can recommend Link2SD.
HilfordJames and I have discussed this in length already so this is more for other people's benefit..
Link to sd can be dangerous, as can forcing apps to sd that don't offer the choice normally, app developers block the option to install to sd for a reason, that is usually because the app accesses services that can become corupt or crash if the app is suddenly ejected from the phone (like when you mount the sd card on the computer) so its best to leave those apps on the internal memory.
The most likely reason for the overnight shutdown would be (as you said) that you had filled your system memory up with user apps.
Sure enough once you've deleted all that bloatware from the system you have heaps of room just begging to be filled in the system partition.. But you gotta leave some room in there (about 60-70mb should be enough)
I think another thing could be if your computer somehow woke up in the middle of the night and accessed (auto mounted) your phones sd card, sounds unlikely but I've had laptops run scheduled updates in the middle of the night when they were supposed to be "asleep" if this happened and you had an application running off sd card that uses phone services (like Wifi, bluetooth etc) this may have crashed the phone.. And as it was plugged into power remained shutdown.. Once again (AFAIK) these apps should be installed on the phone not sd card. (games and similar apps are fine on sd card)
Just a couple of theories, but I think we are on the right track
Kiwi
Sent from my MT15i using xda premium
Yip all good.
Since transferring a lot of the files/apps back to user memory I've not had the phone auto shutoff and I've tested it by leaving it on the CPU at night as well and it seems fine - although I now charge it from the wall charger if I'm working the next day just to be on the safe side.
Related
So.. I have googled the crap out of this problem and seen loads of issues raised, but nothing solved.
I am coming from a Dell Streak and grabbed me a galaxy s 2 from craigslist a couple months back.
It has been running fine and I have tried a few roms/kernels and a few days ago I got the following error:
When charged to 100%, I get the notification to unplug, when I do, it sticks. No big deal but even when the phone battery has dropped to around 80% it stays.
It does not go into MTP mode or think it is plugged in via USB. Although, before this problem originated, the phone continuously vibrated between charging and not, when not plugged in.
I have calibrated the battery, tried a mixture of roms/kernels and I am now on unrooted stock. The problem still occurs and sometimes it does not recognise a USB connection, like today.
Probably worth mentioning that when turning on (and not plugged in) the phone does not turn right on, just boots into the battery screen and flashes between the battery charging and the overheating symbol.
Anyone got any ideas?
encima said:
So.. I have googled the crap out of this problem and seen loads of issues raised, but nothing solved.
I am coming from a Dell Streak and grabbed me a galaxy s 2 from craigslist a couple months back.
It has been running fine and I have tried a few roms/kernels and a few days ago I got the following error:
When charged to 100%, I get the notification to unplug, when I do, it sticks. No big deal but even when the phone battery has dropped to around 80% it stays.
It does not go into MTP mode or think it is plugged in via USB. Although, before this problem originated, the phone continuously vibrated between charging and not, when not plugged in.
I have calibrated the battery, tried a mixture of roms/kernels and I am now on unrooted stock. The problem still occurs and sometimes it does not recognise a USB connection, like today.
Probably worth mentioning that when turning on (and not plugged in) the phone does not turn right on, just boots into the battery screen and flashes between the battery charging and the overheating symbol.
Anyone got any ideas?
Click to expand...
Click to collapse
Turn off the phone and put it on charging. Once it beeps that its fully charged, quickly unplug the battery for 5-10 minutes. Should work and 'recalibrate' your battery
Sent from my GT-I9100 using XDA App
Thanks, giving a go now.
Do you need root to calibrate though? I am on stock firmware and not in front of a windows machine to use ODIN.
Vlad the Cat said:
Turn off the phone and put it on charging. Once it beeps that its fully charged, quickly unplug the battery for 5-10 minutes. Should work and 'recalibrate' your battery
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
OK, charged to 100% and got the full notification.
Left battery out for 10 mins and whacked it back in.
Turned on and it went to the overheating sign again.
Booted into the samsung recovery and I can boot into android from there.
Battery says it is as 88, cannot calibrate as I do not have root atm.
Any ideas?
encima said:
So.. I have googled the crap out of this problem and seen loads of issues raised, but nothing solved.
I am coming from a Dell Streak and grabbed me a galaxy s 2 from craigslist a couple months back.
It has been running fine and I have tried a few roms/kernels and a few days ago I got the following error:
When charged to 100%, I get the notification to unplug, when I do, it sticks. No big deal but even when the phone battery has dropped to around 80% it stays.
It does not go into MTP mode or think it is plugged in via USB. Although, before this problem originated, the phone continuously vibrated between charging and not, when not plugged in.
I have calibrated the battery, tried a mixture of roms/kernels and I am now on unrooted stock. The problem still occurs and sometimes it does not recognise a USB connection, like today.
Probably worth mentioning that when turning on (and not plugged in) the phone does not turn right on, just boots into the battery screen and flashes between the battery charging and the overheating symbol.
Anyone got any ideas?
Click to expand...
Click to collapse
i am actually having the exact same problem FYI im using exynos extreme rom 7.2 i think nt sure its getin worse before it used to detect usb mode somrtimes now it dosent!
encima said:
OK, charged to 100% and got the full notification.
Left battery out for 10 mins and whacked it back in.
Turned on and it went to the overheating sign again.
Booted into the samsung recovery and I can boot into android from there.
Battery says it is as 88, cannot calibrate as I do not have root atm.
Any ideas?
Click to expand...
Click to collapse
Get root and use the battery calibration tool from the market. The best idea so far. I suggest rooting with CF-Root, its fast and easy - its basically still your stock kernel but just with root.
If you really need the warranty or you'r scared of root you can install cf-root, calibrate the battery, then re-flash a stock kernel (unroot)
Sent from my GT-I9100 using XDA App
If i helped you, press thanks. Thanks.
Done and done.
Calibrated, even bought a new battery. Tried various other roms and appears to be an issue. Phone knows when USB is plugged in but does not seem to recognise the unplugging of the charger. And stays at 100% for a while before dropping down to like 80.
One thing to note is that this seemed to happen around the time of buying a dock for the samsung from Amazon, by Kidigi. I plugged the phone in to the dock without a USB cable connected to the dock and the dock LED lit up, making the phone think it was charging. Is this likely to have caused it/messed up the micro usb forever?
Thanks again guys!
well i think ive figured out what the problem was
Its due to overcharging or keeping the charger connected after battrey is full which has caused a hardware damage
im not sure if this is true but this is the closest explanation i can get the phone shows connected to charger even when diconnected only when i keep it connected for long time even after its battrey is full my usb connection has completely stopped working
---------- Post added at 01:56 PM ---------- Previous post was at 01:49 PM ----------
encima said:
Done and done.
Calibrated, even bought a new battery. Tried various other roms and appears to be an issue. Phone knows when USB is plugged in but does not seem to recognise the unplugging of the charger. And stays at 100% for a while before dropping down to like 80.
Thanks again guys!
Click to expand...
Click to collapse
well that the same problem with me when it shows connected to charger at 100% i restart it then the phone drops to ~80% battery although its 100% which makes the app battery monitor widget think i have a 1977mah battery while i have the standard 1650mah battery this must be the extra 20% which disappeared after the restart for me
I thought it may have been an overcharging problem, although no other phone I have owned has had this problem.
I let the battery charge all the way down (it stayed at 1% for about 3 hours) until it shut itself off. I left it on the side and it created a clicking noise, it was trying to turn the phone on as it knew the battery was in, even though it was depleted.
I plugged it in via USB to charge and it tried to turn on straight away. Shut it down and charged by plug until the 100% notification then turned on.
Still the same problem but one of my battery widgets warned that the battery was over voltage for a while before calming down.
If the phone cannot be off with the battery in, what could be causing that?
encima said:
If the phone cannot be off with the battery in, what could be causing that?
Click to expand...
Click to collapse
It has been known to be caused by a defective circuit board for the USB connector.
So, it needs a samsung return, I assume?
i have the same problem with overheating and usb plugged when there is nothing connected
i changed the usb port from the phone but it still having the problem!!!
i will try to put a new battery and see if it work and after post a reply
So the past two nights iv let my rezound battery go dead. The problem is it wont charge a dead battery. It charges if there is some battery and its on but when it is dead it is dead. The fix was I had to put the rezound battery in my tbolt to get a little bit of juice.
Any ideas or similar problems? I am unlocked with the htc unlock tool and running nils business sense?
Could it be a rom bug?
Don't let your battery die. It's bad for it anyway.
Sent from the Rez Beast
Once the battery is dead what does the LED on the phone do? If it blinks for a while it is either too hot or too dead to turn on, but it can still charge eventually. If the LED is not coming on at all I would pull the battery out and connect the charger with no battery and see if the LED comes on. If still no luck, get a new charger.
Blinks then Charges
I had the battery die on me once (on a prior battery and prior rezound). The phone will blink orange for a WHILE (I tried 3 different chargers not knowing what it was), but eventually started to charging. I think patience is needed. If, after 15 minutes, you still aren't charging, then that's something (but longer if the phone was also hot).
If I hit he power button with or without the battery in the led will light for a short time. I had it plugged in all night and no charge. I used two different plugs.
As for not letting it die. I know its not ideal but I couldn't help it.
jdmba said:
I had the battery die on me once (on a prior battery and prior rezound). The phone will blink orange for a WHILE (I tried 3 different chargers not knowing what it was), but eventually started to charging. I think patience is needed. If, after 15 minutes, you still aren't charging, then that's something (but longer if the phone was also hot).
Click to expand...
Click to collapse
+1. Same thing here.
KORM via the beast known as the Rezound.
I let my phone die completely once. I freaked out that my phone wasn't charging. I went onto HTC's site and it said that it could take 20 or more for the led to turn on while charging if the phone was completely dead. Just plug it in and be patient. It will charge and the led will eventually turn on.
Sent from my Vigor using xda premium
I had this problem too, and am a little concerned I have a defective phone
So I had this issue happen this weekend. My daughter was using the phone when it died. Couldn't get it restarted. (I am unlocked via HTC, stock ROM with bloat removed. Phone is a week old.)
After messing with it using the factory charger/cable and other chargers/cable combinations I got nothing. Light would only intermittently come on for a second or two then go back off.
I charged it over night with the factory charger/cable. Didn't work the next day. Charged it all day and night with my old charger/cable that I know works. Didn't work.
Tried multiple variations of taking out the Battery/Sim/SD card and using the plug-in chargers & CPU USB variations with no success.
Luckily, I had ordered a new spare battery and it came in the mail before I returned the phone. Plugged it and it started up fine.
But my concern is that my phone is not properly charging. I have also had other similar charging/battery life issues that raise concern.
As far as not letting it die, **** happens and phones die, if this is a reoccurring problem, that in my mind is pretty unacceptable. A phone should charge when its plugged in no matter what. I may end up returning it to see If just got a defective phone/battery.
My phone will turn on then off and im starting to think it has something to do with the battery. But when it started it was in tue yelllow on the status bar, now i have it charging without being turned on and the indicator light is on but hopping mine will fire up soon. This all just happened to me within the last two hours lol, already called verizon to get a replacement but still going down there tomorrow.
Sent from my SCH-I800 using xda premium
DLink888 said:
So I had this issue happen this weekend. My daughter was using the phone when it died. Couldn't get it restarted. (I am unlocked via HTC, stock ROM with bloat removed. Phone is a week old.)
After messing with it using the factory charger/cable and other chargers/cable combinations I got nothing. Light would only intermittently come on for a second or two then go back off.
I charged it over night with the factory charger/cable. Didn't work the next day. Charged it all day and night with my old charger/cable that I know works. Didn't work.
Tried multiple variations of taking out the Battery/Sim/SD card and using the plug-in chargers & CPU USB variations with no success.
Luckily, I had ordered a new spare battery and it came in the mail before I returned the phone. Plugged it and it started up fine.
But my concern is that my phone is not properly charging. I have also had other similar charging/battery life issues that raise concern.
As far as not letting it die, **** happens and phones die, if this is a reoccurring problem, that in my mind is pretty unacceptable. A phone should charge when its plugged in no matter what. I may end up returning it to see If just got a defective phone/battery.
Click to expand...
Click to collapse
As far as not letting it die, **** happens and phones die.
--I agree, but once it gets down to 5%, why not just turn it off knowing the problems people are having so wide spread now.
Under the exact same conditions I have had the same problem with a warm battery reboot. It seems to occur when you are talking on the phone and let it die. Once it dies the phone will not reboot. My wife has the exact same phone. When I put her battery in my phone the phone works fine. My wife’s phone dies every night and she simply plugs it in the wall and it charges no problem. Again the conditions seem to be related to the battery dying while it is hot. If the battery dies while the phone is cool and not used then it seems to reboot no problem. I will go to Verizon tomorrow to look for a fix. I will let you know what happens.
I'm also having this problem but i can return my phone because i unlock it or can i return it ?
Check and see if your battery is 3.7 or 3.8v . I wonder if it is related to the charging issue with the 3.8v battery some people seem to be having.
mjh68 said:
Check and see if your battery is 3.7 or 3.8v . I wonder if it is related to the charging issue with the 3.8v battery some people seem to be having.
Click to expand...
Click to collapse
it's a 3.8v what do you recommend i do ?
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
gsgleason said:
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
Click to expand...
Click to collapse
I had the same issue with my OG Droid. Would kill the battery and it would stay dead, even after a whole night of charging. The above method seemed to work for me.
I make 100% sure mine never goes totally dead after an experience I had with my Droid Charge.
I accidentally let it die completely (I fell asleep when it was almost dead & it ran all night). The next morning it was off, I put in a fully charged battery & it fired right up but started FCing like crazy. Every single thing I clicked on force closed immediately, I had never seen anything like it.
I was running a custom ROM & kernel & had done a nandroid BU the day before. I restored the BU & the phone ran perfectly again, but that scared me enough that I made darn sure it never happened again LOL........
gsgleason said:
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
Click to expand...
Click to collapse
That didn't work for me i just won't let it run down i guess.
Holy ****!!! I think I may have found the fix! I have had the same exact problem as everyone in here. It seems to happen once I root. My Rezound would die completely, then after plugging it in, the light would come on for 5 seconds or less then shut off. I plugged it into my computer and Windows makes the USB Connected sound, so I figured something is happening.
I went into my command prompt and *adb devices*. It showed my device, but says in recovery mode. I then *adb reboot bootloader* and the bastard rebooted into bootloader! From there, I chose "REBOOT" and it fired right back up! Anyone who is having this problem, please try this and let me know if it works for you!
***UPDATE***
It appears when the battery dies all the way and then doesn't charge, the phone is automatically going into recovery mode even though nothing shows on the screen. I had my SIM card out when I tried this the first time, then when putting my SIM back in, it started doing the same thing. But again, it was going directly into recovery mode. This time, I tried a simple *adb reboot* and BAM! I'm back up and running! Again, let me know if this works for you, or if you need help doing this, let me know.
thehomebiscuit said:
Holy ****!!! I think I may have found the fix! I have had the same exact problem as everyone in here. It seems to happen once I root. My Rezound would die completely, then after plugging it in, the light would come on for 5 seconds or less then shut off. I plugged it into my computer and Windows makes the USB Connected sound, so I figured something is happening.
I went into my command prompt and *adb devices*. It showed my device, but says in recovery mode. I then *adb reboot bootloader* and the bastard rebooted into bootloader! From there, I chose "REBOOT" and it fired right back up! Anyone who is having this problem, please try this and let me know if it works for you!
***UPDATE***
It appears when the battery dies all the way and then doesn't charge, the phone is automatically going into recovery mode even though nothing shows on the screen. I had my SIM card out when I tried this the first time, then when putting my SIM back in, it started doing the same thing. But again, it was going directly into recovery mode. This time, I tried a simple *adb reboot* and BAM! I'm back up and running! Again, let me know if this works for you, or if you need help doing this, let me know.
Click to expand...
Click to collapse
Yes... HTC phones never charge "powered off" When you turn it off and then put it on the charger, it is actually entering/booting a special screen off recovery mode during charging.
CWM recovery on the rezound has trouble charging a completely dead battery.
Use Amon RA recovery.
So last night before I went to sleep, my NT had about 40% battery life left in it. I'm currently running the final alpha build of CM7. I've been experiencing really bad wifi loss issues and have kept the 'Never' option enabled under the wifi sleep policy (thinking that would help hold the connection).
I woke up to find the NT was turned off. Figured that was odd as I was only asleep for about 5hrs. I turned it on and then noticed it got into the OS and then died. I did see the battery icon was red briefly.
I then plugged it into the wall and it was boot looping. I saw the 'n' logo pop up, screen went black, 'n' logo, etc. etc.
After numerous attempts of holding down the power button for 20+ seconds, holding power+vol down for 10 seconds, plugging it with or without an sd card into the wall and computer, nothing is happening.
The computer does see something as I'm hearing the common connected/disconnected tone from the USB port. Now I'm noticing that plugged into the wall, the 'n' on the cable stays orange. It never turns green.
Did it go 'poof' in the night somehow?
[EDIT] Ok after leaving it plugged into the wall for about 15mins, it suddenly turned on but had a google framework FC error. Yeah, not sure what I should do at this point. It appears to be charging...
It's been noted by others that if the power level goes below 15% you mustn't turn the device off if you don't have the original charger nearby. If it dies you need to charge it with the original charger for a bit before it'll power back up.
I assume this means that you can't run it off the cable while you've got a completely dead battery. That kind of stinks but isn't too surprising, a lot of devices are like that.
So does that mean that if the device is <40% of battery I need to plug it in if I won't be around it for a while? Not sure I'm cool with that. Battery life was great all day yesterday but somehow it dropped 40% in under 5hrs while asleep.
I can't really say much as I haven't dealt with it personally. People were talking about it in a couple threads about the NT's charger and unique 12 pin cable.
Here's what I understand from what I've read:
You can run it until it's empty all you like. You'll just need to use the Nook's factory charger (or a compatible 2A charger with bridged D- and D+ pins) AND (this is the important one) the factory USB cable to charge it.
If you run it until it dies you have to charge it for a little while before it'll turn on again, BUT you have to use the original cord and charger. It won't charge off of a regular micro USB cable nor will it work if you're using a 2A or smaller charger that doesn't have the middle two pins bridges (the Apple UBS chargers won't work nor will your PC's USB ports, for example).
The NT will charge, albeit slowly, if connected with a third party cable or USB charger (without the data lines D- and D+ bridged), but not if the device's power has been depleted.
So I suspect something sucked up a lot of juice while you weren't using your NT. Not a huge deal, but definitely annoying. Plug it in for 15 minutes and you can get rolling again.... BUT only if you're using the original charger and cable. Lovely isn't it? It's not a huge problem but it is annoying. I wish you could at least use the device with a dead battery while plugged in.
I just mention the charger/stock cable thing because I'm sure someone will probably see this post in the future and may be having that particular problem resuscitating their NT.
Cool, yeah I don't specifically set out to run it down to zero but since the device is clean with minimal stuff running in the background, it's difficult to know when this might happen again. I assumed I'd wake up with like 20-25% battery left. The framework FC is also something I'm concerned about but maybe it was just a fluke.
Ah well, really do appreciate your input and I'll be sure to keep the stock cable/adapter on hand when I'm on the go.
Battery showed fully charged, I rebooted to do another CWM backup and then when it came back up it showed 84% charged. Lol. And this pic made me laugh even more. Time to get that lady from Poltergeist involved I think...
The Google Framework force close is typical of stock rooted NTs. I don't believe it ever did any harm to anything though. Just that it sometimes appears on reboot.
I'll ask one additional question as to not make another topic since it's related.
Opinions on battery calibration with the NT? That was one of the reasons I didn't charge it last night as I wanted to fully run it down and then fully charge it back up. Does the NT require this with a new rom install? That pic above shows the battery gauge clearly wasn't correct initially.
Your battery is draining overnight because wifi is running the whole time (as you stated in your first post).
Sent from my SCH-I500 using Tapatalk
ckevinwelch said:
Your battery is draining overnight because wifi is running the whole time (as you stated in your first post).
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
That's what I obviously thought of at first but it didn't drain nearly as much when I was using it throughout the day. The only thing I can think of is maybe the fuel gauge itself was wrong from the start, which refers back to my calibration question.
My GS2 has the sleep policy set to 'Never' as well and only loses maybe 7-8% after being asleep for around 7-8hrs and it certainly uses more juice in sleep due to the cell communication, etc.
Piece of cake. Although the replacement is a bit lower MhA it's a lot better than the old battery
pepi4 said:
Piece of cake.
Click to expand...
Click to collapse
That's nice to know. Is there a step-by-step guide for it?
Although the replacement is a bit lower MhA it's a lot better than the old battery
Click to expand...
Click to collapse
Which replacement battery did you get?
http://www.batteryship.com/htmlos/htmlos.cgi/batteryship/catalog.html
You even get free tools and they are not junk
How to that I used ... Hard to get pass the women robot talking LOL
https://www.youtube.com/watch?v=3F0glSyvj2s
At first I wondered about this being a smaller battery if it would run down fast. It doesn't !!! Works very well !!!
I changed out my battery with one from the above site, but now every time I plug a USB cable in it to charge it immediately shuts off. Anyone have any ideas what could cause this? Wonder if I got a bad battery..
mpry1 said:
I changed out my battery with one from the above site, but now every time I plug a USB cable in it to charge it immediately shuts off. Anyone have any ideas what could cause this? Wonder if I got a bad battery..
Click to expand...
Click to collapse
That could be a bad/shorted battery. Mine is still going strong! I would try and reverse everything and start over. When I did mine my vol controls didn't work. Didn't have the connector snapped down good enough
I was looking at this one (still am actually although the one you got is cheaper):
https://www.youtube.com/watch?v=3F0glSyvj2s
http://www.newpower99.com/Barnes_No...cement_Kit_p/barnes and noble nook tablet.htm
I am still trying to see if there is a setting that somehow caused my NT to freak out when the battery reaches 23%
But I have this bad feeling I will need to purchase a new battery. By the way, if the nook just shuts off watch the screen closely it usually says "battery too low" for a second before switching off. And if that is the case after plugging it in, you likely have a bad one and I would call the company to get a replacement.
I have been looking around and the only new replacement batteries I find are the two mentioned and both are 3200mh rather than 4000 of the original. How is your battery life since you changed it? Seems like it should be 1/4th what we had when new (or close to it). Or don't you really notice at this point? I have thought about ebay but then they are used batteries and you have no idea how many cycles are left, and likely hold 1/4th less anyway due to their age. *shurgs* not sure which way to go. As of now I am still having a "freak out" situation at about 23% (roughly). If it doesn't get any worse I can live with that, but from what I have read it will only get worse. :/
Anyone know of a battery app I could use to "adjust" the shut down threashold? I have one that will alert me to whatever I set so if I am not watching it will warn me so that will work if I don't have one that will actually shut it down. I know the "calibrating" apps don't do anything except delete the one file that is only usage stats from the last time it was plugged in, so I don't think there is a real way to calibrate it.
Update:
And on another note with the "spare parts" app the 'battery history' option errors with "the application spare parts ) process.com.andriod.spare_parts_ has topped unexpectedly, please try again." Is this normal? It is version 2.3.7. NT Hidden Settings app application settings/battery use works fine and shows the amount of everything that has used the battery since it was last plugged in/charged. Could this error be a sign of the problem with the phantom touches and inaccurate battery display? And if it is a sign of something broken, what and how do I fix it?
I received a replacement battery and it is doing the same thing, so somehow during the battery switch something got wonkey with my nook. It charges OK just powers off to do it. Since it's used by my kids now it's not essential to be on while charging, but I'd still like to figure this out.
mpry1 said:
I received a replacement battery and it is doing the same thing, so somehow during the battery switch something got wonkey with my nook. It charges OK just powers off to do it. Since it's used by my kids now it's not essential to be on while charging, but I'd still like to figure this out.
Click to expand...
Click to collapse
Which battery did you get? And very strange it shuts off when you plug it in. Never seen or heard of that before. It should boot up if off. Or do you mean the screen goes off/goes to sleep but not full shut down when you plug it in? If it is going to sleep, that is likely a app or setting that is doing it. Not sure which but you might want to check any battery apps you have or your settings. It would also depend on which ROM you are running, stock (which I am running) or something else.
Both batteries were the one mentioned in the original post. It doesn't go to sleep when I plug it in, it completely shuts off like no power at all. It will not boot up until I unplug the USB from a power source, although it will fully charge while it is plugged in. I've never seen anything like this and I've been messing with android since my original moto droid 1.
mpry1 said:
Both batteries were the one mentioned in the original post. It doesn't go to sleep when I plug it in, it completely shuts off like no power at all. It will not boot up until I unplug the USB from a power source, although it will fully charge while it is plugged in. I've never seen anything like this and I've been messing with android since my original moto droid 1.
Click to expand...
Click to collapse
Very strange indeed. The only thing I would say to do is turn the USB debugging on and off a few times, to see if that makes a difference. It shouldn't but if you tried two different brands of battery, sounds like it is the hardware on the nook. But that is one really weird bug.
Something interesting I discovered. While I did get a new battery, I decided to do some experimenting. Researching this issue a lot of people said you need to delete the "battery file". There even use to be a option in CWM to remove this file. The thing is the file is deleted every time you plug in the device. So that is not going to help.
Further digging found that some devices you need to plug them in and let them charge. Or run them down for say 20-30 minutes without sleeping then plug in and let it charge fully. For some devices this "resets" the battery management system.
What I found in my tests is the battery gets harder to charge with age. While the little n light might show green, it is likely only 80% charge sometimes 90%. And it takes awhile for it to really get to 100%. What I did was let it charge up to that full 100% which may take hours. I got a nice battery app that alerts me when it gets below 25% after that things can get crazy with phantom touches. I also have it set to give a audio alert when it reaches 100%, this way I know when it is fully charged.
I know the charge it fully (when it actually says 100% and I get a audio alert when this happens) before 50% or so has helped a lot. At one point the phantom touches started to happen at higher than 25% reaching almost 35%, last time I did a test to see when phantom touches started was 17% so it is much better. Not to the level when I bought the device, but still very useable.
I will put in the new battery sometime I am sure as it is taking longer and longer to reach the full 100% (but that is normal for lithium ion batteries.) it is certainly useable in this state and the phantom touch issue is not getting worse. I think the biggest issue was charging it until the n light went green and as the battery ages, the battery manger gets thrown off for some reason and charging to the true 100% helps recalibrate it.
Therefore I would run it for 20 minutes without letting it go to sleep, then charge until it is really full (usually leave it plugged in overnight and that should do it). Do this a few times and see if the battery is better.
Oh another thing I did. Power it off fully (hold down power button then tap shutoff) then plug it in to charge. Let the charger wake, reboot, and charge the device. This I also think helps recalibrate the system. Although I never did it when I ran it for 20 minutes then charged to full. But I am sure powering off then plugging in to charge at times made a difference as well.
I've just bought one of these batteries, hoping it'll be better than my old one.
It should be. It won't be quite as it was when it was new, as these new batteries don't have the capacity compared to the originals that B&N installed (perhaps a hour or two less runtime compared to the originals). But it will be better than a well used Nook Tablet battery that is fading fast.
I don't know if I need a new battery just yet, but I am experiencing the issue of the power being killed when plugging the Nook into the wall or USB (which means transfers over an SD card, which is a pain). I only spent $5 to get it and I can see why someone might have thought it was broken, since they probably plugged it in to charge it but it wouldn't turn on while plugged in. It does charge while off, however.
What I've noticed in my experience is that if I turn it on, I can plug it in while the Nook is on the N screen, and then it'll go to the Cynoboot screen still plugged in, but the second it goes to boot the OS it turns off.
Anyone have any ideas on why it would allow itself to be on until it tries to boot to the OS?
So my phones battery discharged from almost full to completely empty last night while plugged in. It seems to be charging fine right now however but I did fiddle around with it a bit. Even if it wasn't plugged in it discharged way too fast for regular standby and non of the "use since last full charge" look odd. Anyone else had anything like this happen?
So it turns out a least part of the problem was that my charge cable is damaged, it only works when plugged in in one direction. I still don't know why it was apparently running flat out all night though.
I wouldn't worry about it; there's no telling what a bad cable can or cannot do with your software. For all we know the software was unable to go to sleep because it constantly started charging, then stopped, then started again... Cut your losses, buy a decent cable and forget about the issue
One thing I tend to do to keep my phone behaving: I reboot it every so often (at least once a week).