Ok in short my battery is not charging at all. I have had this kaiser for a month mayb, but the battery for almost a year. I we away for the weekend and forgot my charger so my phone died. I plug into charger and charging light comes on but when i try and turn it on phone boots then dies as it has no power from cable or battery.
Phone is COMPLETELY stock + tf2d.
AT&T Tilt
Any ideas anyone?
I just updated my phone (even tho it has no battery...). So right i went into bootloader and flashed the offical rom, it died at 13% then retarted and finished flashing....idk if it was supposted to do that or not idk. but now it boots and does the samething as if it has no battery...idk what the deal is .
The battery is heating up like its charging...
It remained updating from 13%-100% and didnt die but i dont think it can charge while updating..but after updating when installing it dies as soon as it gets to "clearing storage"
update
i believe i have a mechanical issue now not a battery issue. This is because even tho it says its charging the battery the phone SHOULD be able to boot under power cable only without battery....but it does not....seems i shall be calling at&t....
jug6ernaut said:
This is because even tho it says its charging the battery the phone SHOULD be able to boot under power cable only without battery....but it does not....
Click to expand...
Click to collapse
Nope, HTC phones and most others can't boot just off the power cable with no battery.
I just updated my phone (even tho it has no battery...).
Click to expand...
Click to collapse
If you had read the warnings in the flashing application you'd have seen it says to ensure your battery is charged before flashing. If your battery is flat and the phone turns off during flash (which looks like it has happened here) it leaves you with an incomplete flash and unusable OS, no wonder it crashes randomly. If you have HardSPL you can recover from that, but as you said you're completely stock it might be a lot more problematic.
lol no no my friend you miss understand what im saying.
Trust me i know the warnings of flashing(300+ flashes many failed...happens when making ur own roms), and knowing these i flashed anyways. What i was trying to point out was that it went through the flash all the way even tho during the same amount of time it would have died during booting, the flash was successful but idky.
The phone is not crashing randomly it has no battery power lol. This problem has nothing to do with flashing because before this it was 100% stock...
Are you sure the kaiser can not boot purly off external power? I was almost positive i had done this before.
Hey guys, I need some help with my G1. I regularly do conditioning for my phone and for some reason, even if my phone has a full charge, it just turns off and I can't turn it back on until I put it on a charger or wait about two hours. Also the phone doesn't give me a notification that it's shutting down. Not sure if this is the right topic to put it in but thanks for the help!
EDIT: I have been using Cyanogen v4.2.13 and I've checked my battery status on my phone and it says that it's in good condition
Ive been having the same problem. Hopefully someone can help us!
me too!
I have this exact problem. I have the latest CyanogenMod - v4.2.13 ROM on my phone. I read somewhere that the auto wallpaper switching apps caused this. But even after uninstalling the app my phone randomly shuts down.
i guess you can try going back to a earlier cyanogen rom or any rom and see if that changes the problem, if not, i guess you can try to wipe, and to the htc recovery and all that and go back to 4.2.13, im still new at this whole thing so its just a thought
Same here
I'm not sure what the deal is. I think that I have dirt in my SD connector or something because mine runs out of memory and reboots sometimes. Other times it works for days. Still other times, it goes into a reboot loop until I take the sd card out and re-seat it.
Perhaps the weak sd connection is the culprit. Are other people keeping the phone in a pocket that generates lint and dust?
Does a battery pull / replace seem to fix the problem?
i keep mine in my front pocket all day everyday lol
I say take a sledgehammer to it, that way it'll die reliably rather than randomly
I reflashed radio, spl, rom, partitioned, wiped, everything! Still shut itself off today. I had to turn it back on with the charger connected to get it back again.
Hey guys, I found the problem. My battery couldn't hold a charge so I would suggest getting a new battery if you had the same problem as I did. Be sure to condition/calibrate it so it'll last longer.
EDIT: Also only put your phone on a charger if the battery is extremely low.
Change Battery
I tried at least 4 different ROMs(with wipe/reset) and it did the same thing. So it's not the software. As a finally test I swapped batteries with my wife (also has a G1). No random shut down on my phone but her phone did. So it's definitely a battery issue. Also, I noticed my battery has swollen quit a bit. New battery on it's way.
Right off the bat, my Revo is non-responsive, no buttons will light, backlight, vibration, sound, and of course no splash screen since the screen isn't lighting. The only sense that it is partly there is after a time connected to USB/wall charger the battery warms as if it is charging. Yet, there is no indication during charge on the screen, it stays totally black as described above.
I have been poring over forum posts, CWR threads, and the like, but have come up short on a method of reviving this puppy. thecubed had posted something that seemed promising but doesn't work for me here. At all steps, the phone remains non-responsive and connecting it to the PC yields no mass storage connection. The only step I have abbreviated is letting it charge for an hour since the phone had charged about four hours since it shut down.
Two evenings ago, I flashed from Revolt ROM 1.0 to 1.1. It was successful but since I had just gone through battery calibration and running my battery down until the phone shut down the day before when I flashed it to 1.0, I was hoping (naive?) that I wouldn't have to do it this time (yes, naive!). So, I left the phone on all night, on the wall charger.
I was using it the next day and at one point, while using it in a low reception area, browsing the web, it rebooted on me. No biggie, had that happen in the past. After reboot however, the battery level seemed different so I wanted to get it topped off then calibrate. 1-2 hours later I noticed that the calibration app was showing the mV lower and capacity was at 70%. The battery felt unusually hot. I shut it down, removed the battery and cooled both battery and phone in a small fridge to accelerate the process (was near time to leave work).
Next boot was I recall having an extra FC, one beside the CarHome normal FC with Revolt ROM 1.1. This boot the battery showed maybe 20% capacity so I said "screw it" and deleted battery.bin with the battery calibration app (I recall the mV was low, in the 3600 range). I discharged it on the way home and left the display on to run the last couple percent down. It appeared to try and shutdown but ended abruptly. That was the last time I saw any life from my Revo.
The day after its first and only ever root, I did have an odd occurrence which I posted.
Boot Trouble - Rooted After Phone Downloaded OTA, Not Installed
That time, I had not installed a ROM yet but the phone got itself into a boot up funk. Removing the battery, connecting to wall charger, watching buttons flash ~5 times, disconnecting (which stopped the flashing lights), then battery in, power on... success! I was hoping that would happen this time around but I haven't been able to.
Full history, being my first root, I used S1C successfully, installed Titanium Backup (ran system and app backup), and RevoToolkit. The phone did download the OTA but I never let it install, instead selecting to delay it by 24hrs when it asked to install. Fearing that deadline and getting one more warning that it wanted to reboot and install the OTA, I went ahead and installed the Revolt ROM 1.0. All went fine, no drama. The next afternoon I thought going to 1.1 was going well too, until this brick hit me.
My hope of hopes is it's just a bad battery and the phone won't respond because the mV is too low. Reading thecubed's comment in his first link (above) how recoverable this phone is lends me hope.
It sounds like a bad battery. I would take it to a verizon store and see if you can try a different battery. If it still will not boot then they should warranty it out for you.
Sent from my VS910 4G using XDA Premium App
P.s. I never do anything for my battery. I charge until full then use until empty. Yesterday with moderate tI heavy use I made it from 6am until 8:30 pm
Sent from my VS910 4G using XDA Premium App
Thanks for the responses. I will be going to VZW shortly to figure this out. This phone is maybe two months old so hopefully the battery is the answer *fingers crossed*
Impressive battery life! At my office, I'm in a bit of a metal cubicle area and a bit low on signal strength. My phones will sometimes use up the battery trying to keep connected, it seems, so I am usually plugged in most of the time.
While I have your ear, thanks for the great work on Revolt ROM. I am very happy with it and look forward to its future development
Good news and bad.
The good news was they swapped in a new battery and the phone worked. Having the warranty, it didn't cost anything.
The bad news is that it looks like there may be another problem. On the way out of the store the battery was indicating 1% so I quickly got it on the charger in the car. Driving home, about 10 minutes later, I got a warning for battery temperature. Thinking the low battery may just be taking a charge and getting hot from that, I turned the car A/C on full, took the back cover off, and kept the phone in the cold air.
In about two minutes, just feet from home, I noticed the display was off. Faintly I could see the battery charge symbol that shows when the phone is powered down and charging, but the backlight was off and I couldn't see if there was any color or animation to it.
As soon as I shut the car off and the power quit, that faint display disappeared, full black, dead. Now it seems it is behaving exactly the same. I haven't fiddled with it much, holding out hope of hopes it can be started and maybe recovered.
Could calibrating the battery at the wrong time have caused something like this? Do batteries have a safety lockout if they overheat? To be fair, I was running an intensive app at the time, Waze GPS. Maybe the battery didn't keep up and the phone decided it was too low and shut off. I will post back after letting it sit, cool, hopefully charge, and see what comes of it.
My phone is behaving exactly the way you describe too. A couple of days with Revolt 1.1, and this is the only problem. I had my phone hooked to a lithium ion usb battery pack all day, and it showed "100%" while hooked up, but as soon as I disconnected the battery pack, the battery icon changed to red, then it refused to boot like the situation described in the Revolt 1.1 thread in Development. It also would not go into charge mode on the battery pack, but when I came home and hooked it to a genuine AC adapter and it went into power-off charge display. I'm going to give it a few hours on the charger before I attempt to boot it again, and I'll report back.
Still no luck. I haven't charged it too much yet for fear that it isn't charging properly. Seeing the new battery work for about 20 minutes yesterday lent me hope that if I figure out how to get a fresh battery in or just shell out for another new one, I can have a window of opportunity to change ROMs and see if that has anything to do with it.
This morning I got out my digital multimeter to measure the battery pos to neg and am getting nothing (unless you consider 0.01v something). I tested my old LG clamshell's bulging, old, and damaged 1000mAh battery and it reads 3.99v but couldn't keep my old phone up (lacks oomph now).
Comparing that battery to the Revo's, they have the same four contact pattern but different connection scheme which just stops contact when test fitting. After shaving down its casing on the bottom a little bit, it was just enough to make contact. Using four hands (yes, I am very talented ) to hold the phone, hold the test battery properly, and hold the power button, I was able to get the power-up vibration and the first LG splash screen. We lost it after that but that's likely due to the very weak test battery and/or losing contact while holding it in the Revo.
Since the spankin' brand-new battery is now reading zero, I'm left second guessing my decision of not shutting the phone down when I got the temperature warning. Maybe these batteries do have an internal protection to prevent runaway failure and it too is trash. I have no experience with this otherwise so this is just guesswork.
I'm contemplating rigging the new battery into my old LG phone to see if it can tell it "all clear" and charge it up. I'll post anything I find out here. Any other suggestions are highly welcome. Still, last ditch, I'm pretty certain I can set up another ROM to flash on the SD ahead of time, get another battery, and Clockwork to test another ROM if it's the phone or ROM. I may have had 20 minutes of uptime on the last battery.
I think I've gotten to the bottom of my problem. It's a syndrome of things that I have hopefully untangled.
First off, I had been messing with Power Manager, and wanted the phone to not sleep or timeout the display when plugged into both AC and USB. I figured that would help when I'm plugged into the computer, but it was probably a bad choice.
Yesterday I was out on a boat, which probably put me into a weak signal area, causing the phone to expend extra energy staying locked on a tower. In addition, I had plugged it into the external USB power pack, and thrown them in a bag together. This did two very bad things: 1) It allowed heat to build up from both the charging and 2) it invoked the "USB powered" Power Manager profile which kept the display active which created both additional heat AND crazy battery drain.
Here's what I think happened:
1. The battery overheated
2. The USB battery pack couldn't charge as fast as the display and radio could suck it out -- so five hours in that mode BOTH drained the internal battery AND tapped into about 30% of the external battery pack.
3. The USB battery pack will not provide enough initial juice to restart a flat-dead, overheated phone, or the firmware "knows" it is hooked to USB and refuses to start the phone -- for some bizarre reason.
So, I think my phone demonstrated normal behavior for a flat-dead, overheated phone, and hooking it up to AC brought it right back to life -- after about 5 hours of continuous charging. The battery also got very warm during charging -- more than I recall feeling ever in the past.
I'm hoping there is nothing that software power management could have done to physically damage the battery, but I assume Verizon would claim it could -- as part of the reason they forbid system modifications, and therefore withdraw their warranty if you modify.
At this point I think I have dodge a bullet, and my phone is fine -- other than a few of the quirks others are seeing in Revolt 1.1 (Phone occasionally FC, etc.)
Good to hear your phone is fine. Seems like mine is too as posted above but time will tell. I got the Revo battery set up and charging on my old phone. It seems to be connected well enough. The phone complained the first try that there was no battery but my second try has it displaying that it is charging. The battery isn't warm at all but maybe that's due to a different charging rate for the old phone's 1000mAh battery vs. the Revo's 1500mAh. Or, it really isn't connected perfectly. We shall see.
Success. The surrogate charge setup got the Revo battery up to 4.11v and indicated charge complete. The Revo completed a full boot on the battery and appeared normal.
Not normal was quick heating (still unsure of the cause). Going straight to Battery Calibrator, it indicated 68% and around 3.7v and falling. Not wanting to push my luck, I shut it down. Battery now read 3.9v. Not bad but it sure seems to be getting drained quickly which would explain all the heat. Going to set up later and see if I can get it back to stock and see if the behavior persists.
I don't know how to fix any of your issues but I would like to say thanks for giving such a detailed display of what you've been doing to fix this problem should anyone else run into this issue. Also, That picture in you one post: That is the most jerry rigged set-up to charge a phone I have ever seen in my life and I love it. Good luck getting your phone working I hope everything turns out for the best.
You're welcome. It was a bit of impromptu brainstorming with some fellow tinkerers that helped come up with a way to test charge the battery. Having it come back to life
I've come to a conclusion. Somehow, I think when the battery overheats, it must internally soft protect itself. Charging it on the old phone reset it and then it worked again on the Revo. Why the old phone works and not the Revo, unsure. That would at least explain why the battery tested at zero volts before the charging rig.
After many starts and stops on my Revo now, I have found that what was heating up first was the casing of the phone. I'm guessing heat conduction of heat from the processor as it wasn't the display which was set to minimum brightness (those are the main heat sources, right?). Looking into Settings > About > Battery Stats, it only showed Android System at 98%. It seems like the processor got locked into some some high power continuous use situation which survived reboots.
The battery gets hot later due to the high consumption and proximity to the hot casing (processor), especially with the back on. Withing 1-2 minutes from start, the sides of the phone would be quite warm and after 5 minutes becomes concerning. It seems that's why the battery was never able to get to 100%, but instead its percentage was always falling, phone over consuming greater than charge rate.
With the processor going full tilt, battery cover on, protective case on phone, sitting in a warm car without A/C, that got the battery too hot within 20 minutes. It was a similar situation with the prior battery when the problem cropped up.
I don't know what the cause of this predicament was in the first place however. The phone was plain stock, then rooted, later flashed Revolt 1.0, then Revolt 1.1. Between Titanium Backup, RevoToolkit for CWM, basically nothing unusual, I have no idea how it happened. Maybe I should have done Decrap first since I've read others doing such. Thinking back to my first post/thread, I had a boot issue and only had rooted, Titanium, and RevoToolkit, no ROMs yet.
And, don't get me wrong. I'm not placing blame anywhere, just documenting my "progress." There was a time I was on Revolt where it wasn't behaving this way. I am left without a solid conclusion as to the cause.
How to avoid the battery drain?
I had a similar situation, downgraded and then installed Revolt 1.3. Can't say what did it, but the battery got hot and drained so far it would even start charging.
I got the battery charged on the old phone, and the new one, with Revolt 1.3 is working. But I'm not sure how to make sure the overheating/draining problem doesn't occur again. After 10 minutes the phone is starting to get hot again, battery is down to 57%. With the phone on or off, it does not charge the battery, even with an AC wall charger. With the phone on, it indicates 57% charge, with the phone off, the battery icon just sits at red, no charging is happening. I erased the battery stats in ClockworkMod, but is there anything else to do? Any other ideas?
It sounds like Haxid had it happen and he got back to LG stock and unrooted, all good.
http://forum.xda-developers.com/showthread.php?t=1233668
Mine happened again this time totally dead battery. Trying to get some charge in it now to boot and remove cwm so I can take it to verizon.
Decrap 1.0 rom this time w/ CWM
I do not believe it is the rom. It has to be an app or hardware.
Were you having spontaneous reboots? That's when it happened to me, after a spontaneous reboot.
Good luck. Hope it all works out.
Bait-Fish said:
Were you having spontaneous reboots? That's when it happened to me, after a spontaneous reboot.
Good luck. Hope it all works out.
Click to expand...
Click to collapse
No my phone is actually super stable it just is sucking battery like its candy. Been off charger only 1 hour right now and its down to 83%. It has to be an app doing it but I have no idea which one. The phone shows 64% battery usage by android system.
When mine was hogging battery, same here. All I saw was Android process.
just to add my 2 cents here. I noticed my phone draining like crazy, I tried everything, then I changed the battery. boom. everything is now stable. I'm going to try to exchange that battery I think its my drain and reboot culprit.
Hi - a few days ago my SGN turned off when I was playing GTA so I plugged it in and kept playing it. I noticed that battery levels were reported as ~50% before the first switch offs then 14% when I switched it on again. Then it happened again a few times then it turned off when I switched on WiFI just after booting. Basically over the last day or so it started turning off during the boot animation and wouldn't even boot most of the time.
So after reading a few threads here I tried flashing to stock GB then stock JB - it pretty reliably boots to the language choice screen then switches off on the next screen which turns on WiFi as it happens, not sure if this is relevant but wierdly when it was switching off in GTA it seemed to be at the same spot each time in the game. The thread which I got method from said to use Kies but I could only use Odin to flash JB since it turned off before it finished:\
Also discovered that whilst it will switch off on the CWM screen even it appears to be fine when it's in download mode.
So looking at another method to fix this here I put Note into download mode and ran down the battery, left it for 10 minutes, turned it on again until it died again, left it for an hour and fully charged it off wall outlet. Basically this appeared to do nothing for the situation.
So I don't know what to do next - any suggestions? I'm pretty sure it's some issue with the battery but I don't know what: it can sit for hours and hours in download mode to run flat without switching off but will switch off during CWM recovery and just after booting stock JB ATM.
I'm thinking I'll grab a cheapo battery off Ebay and see what happens to start with. Can anyone suggest anything else?
I'm sure You can use the phone while keeping it on constant charge. How old is your battery? This is surely a battery problem and i suggest you to buy the original samsung battery. And once you change your battery, do not overcharge the battery by keeping it for charging overnight and such ways.
Varad297 said:
I'm sure You can use the phone while keeping it on constant charge. How old is your battery? This is surely a battery problem and i suggest you to buy the original samsung battery. And once you change your battery, do not overcharge the battery by keeping it for charging overnight and such ways.
Click to expand...
Click to collapse
It was restarting when it's plugged in to charger but I just switched it on and got past all the OS setup steps so fingers crossed. Turned off as soon as I uplugged the charger though.
Battery is original and quite old, got the device late 2011. Thanks for the advice.
Replace the battery asap with original one as if the battery is overused, it may swell up and damage the back cover. Do hit thanks if i helped
So I've had this phone for about a year now, the moment I got it I unlocked the bootloader, rooted it and flashed cyanfox (cm11 fork) onto it.
It's been serving me great ever since, no problems whatsoever with it.
But as of a few days back I found it with a black screen, unresponsive. I connected the charger and it light up the green led solid, tries to boot but can't get past the boot loader message
This continues in an almost endless loop until getting to a 'battery 1%' screen with it showing the battery. After that I'm able to boot it up without problem
I first thought that was the end of it.. I finally got it too boot all seemed fine, battery showed 3% at start up bit voltage was suggesting it was 100%. It flashed to 100% later.
Good, no problem until then. But when leaving it over night to charge and disconnecting it from the charger this morning it turned off again. And now it's back in the bootloop when on charger :crying:
also important to mention is that when it crashes and gets into the bootloop on charger(0% battery and all) it was at 50-100% before the crash.
If anyone has any ideas what might be the cause I'd be very thankful
Main problem(s):
-random crashes instantly rendering battery % as 0 while there is still charge
-getting atrix hd to turn on at <1% battery
Some maybe useful information:
-it does say 'battery OK' in fastboot while connected to the wallcharger
-after I get it to boot it will run just fine on battery and charge as normal, but will crash/brick again after some time
-I can get into boot selection screen and fastboot, but only on wallcharger
-I cannot get to fastboot when connected to use, pc doesn't see the phone
-It won't boot past the bootloader('Motorola logo' for you on not unlocked bootloaders) no matter the boot selection(recovery, bp tools etc)
-This is a second hand model already in use by me (the second owner) for over a year now
-no custom kernel, only rom, cyanfox 4.4.2 (cm11 based)
-the few times it got past the bootloop and I was able to boot was on my aftermarket charger (stock charger will make the green led light up but no proof of being able to get past bootloop over time on it)
I've had dead batteries before.. and since It looked good last time I got it on (it won't go on at all now) I was skeptic about the battery being dead. But a quick test of the multimeter gives me <1v :crying:
I know batteries can be drained pretty bad.. but this just seems a bit extreme.. I'll try to get it to boot for a while.
Thanks in advance for any helpful solutions or ideas on the matter
EDIT: Got it on again last night, turned off this morning when pulling out the charger, was at 100%. Checked battery and again read around 1V.
blaming the battery, ordered a new one just in case, should be here in a month or so. Still open for suggestions on the matter
Catblaster said:
I've had dead batteries before.. and since It looked good last time I got it on (it won't go on at all now) I was skeptic about the battery being dead. But a quick test of the multimeter gives me <1v :crying:
I know batteries can be drained pretty bad.. but this just seems a bit extreme.. I'll try to get it to boot for a while.
Thanks in advance for any helpful solutions or ideas on the matter
EDIT: Got it on again last night, turned off this morning when pulling out the charger, was at 100%. Checked battery and again read around 1V.
blaming the battery, ordered a new one just in case, should be here in a month or so. Still open for suggestions on the matter
Click to expand...
Click to collapse
Did you fix it somehow in the end?
My Atrix HD freezes after several minutes(sometimes even on wall charger). Bought new battery, tried to reset everything: usb storage, cash, system, factory reset. Went back to ROM I was using before(stable) but didn't help.
?
michael8s said:
Did you fix it somehow in the end?
My Atrix HD freezes after several minutes(sometimes even on wall charger). Bought new battery, tried to reset everything: usb storage, cash, system, factory reset. Went back to ROM I was using before(stable) but didn't help.
?
Click to expand...
Click to collapse
It ended up being the battery, all problems were gone after I changed the battery.
Which in the end wasn't so bad because I'd been wanting to upgrade my eb20 to an eb40
No Idea to what it could be in your case.
Everything working appart from that? no battery hickups or things not working properly?
Catblaster said:
It ended up being the battery, all problems were gone after I changed the battery.
Which in the end wasn't so bad because I'd been wanting to upgrade my eb20 to an eb40
No Idea to what it could be in your case.
Everything working appart from that? no battery hickups or things not working properly?
Click to expand...
Click to collapse
"0% battery after crashes" that is what was happening in the begging, so I thought it is the battery. I changed it to UB40
but everything's got worse. With the new battery I have crashes even when the battery is almost full.(but not always, for example I can play movie from youtube normally, but when I try to send sms or something else it crashes ).
Hard to believe that there is something with the new battery(I have it just one week+It took a month to ship from ebay).
I tried to flash another ROM, but still have freezes.
Last thing sometimes battery charges normally but then suddenly jumps to ~100%. Now I try to flash Stock ROM, but eventually soft bricked the phone. (+had "battery low" in fastboot, while charging animation was saying 100%)
Where did you buy EB40?
____________________________________
It turned out that EB40 battery was bad, after replacing it with another one everything work