Nexus 5X strawberry juice save attempt. - Device Repair

Hello people,
I am trying to diagnose/save my old Nexus 5x.
It got soaked in strawberry juice a week ago. I wiped it off as much as I could, and left it. I did not test it, because the battery had run out days ago. After trying to charge it yesterday, I noticed it would not charge or turn on anymore.
In a rescue attempt, I opened up the phone (and was surprised how easy it was to get the bare pcb in my hand), and found a ****ton of gunk. The juice didn't only get in, the acid also did its work on the steel parts. I cleaned it as much as possible with a cleaning cloth, and finished with and electric toothbrush, to get the gunk out of all the nooks and crannies. It turned out quite clean again, although I cannot see if it also got under the main IC's.
Before the cleaning, I got my hopes up because I saw the gunk was mainly concentrated around the battery connector. I think the juice or corrosion shorter the battery terminals and depleted the battery. After cleaning it properly I measured only 0,8V.
To my surprise, after reassembly, the phone worked again. It started taking charge, and after a minute or 2, I could start it up. It worked as normal and it was taking on 1,5A of current. I left it like that for a while, and then I noticed it stopped charging at 50% charge. The voltage was 3.2v according to AccuBattery app, and the battery temperature 49C. The latter was odd, since the battery felt cool. Nowhere near 49C. So I'm also doubting the voltage value of 3.2v.
Anyway, the phone was still working at that point. It was just wouldn't go past 50% charge. I tried unplugging the charger (phone stayed on, so battery works at least a bit) and reconnecting. But it still wouldn't charge. After trying to reboot, it never came back to life since. Basically, when I plug in the charger, the red light starts flashing (and phone is drawing 700-800mA. After a couple seconds, the screen comes on, showing the battery icon. After that, the Google icon shows. And then it shuts down again. At that point, the current also drops to a stable 300mA @ 7,5v. It does not charge though. All the power seems to go into one of the main IC's (not the charging one), which is heating up noticeably in this state.
Can anyone tell me what could be happening? Why is the IC drawing that power while off and "charging"? Any tips? The faced the phone booted and worked for a while, gave me hope.
Edit: Now its drawing 650mA @ 7,5v after being plugged in instead of the previous 300mA.
Edit2: It's booting! Drawing 600mA @5v.now while phone is on, while idle and under load no change. I'll keep you posted. AccuBattery and android say it has 50% charge again, but shows a negative charging current.

Related

Tilt battery voltage not sensed by phone?

I have this strange problem that just cropped up. After a full recharge the other day the battery showed normal draining. When I tried to recharge it wouldn't; neither from the wall charger or usb by computer. So the battery showed steady drain unless charging, but never got more charge. Finally when turning on the phone on battery alone it shows 1% charge, and there's nothing I can do about it, the phone will turn itself off.
Diagnostics: I measured the battery voltage and it is ~4.2 volts. This seems like a full battery yet the phone doesn't see it.
I measured the voltage at the battery terminals in the phone while hooked up to charger which was ~4.2 volts. So it seems the battery is being charged.
Why is the phone not seeing the battery charge? Is the battery dead even though it measures 4.2v?
I did run the gps before this happened using gps tool, bit I think I turned it all off. Anyway more than one soft reset didn't help.
Thanks,
Ed
ATT Tilt 8925 running gthing Blackwood rom with Vista BatteryHide. Original ATT radio.
No real answer here but perhaps something to try:
I am dealing with another member who has a similar problem.
http://forum.xda-developers.com/showthread.php?t=377675&page=2 From post 17 onward.
With battery in, the orange charge light comes on and all seems normal. However with a few seconds of turning on the message that the main battery is critcally low comes up and the phone turns off. He has tried another battery with the same result. This happens even with the charger connected.
(EDIT: I have now read that his has - for no obvious reason started to work ok - Now even more convinced it's a charging circuit lock-up issue - given time and possibly a bit of battery fiddling and it comes good in the end - see No 2 below)
Now I'm wondering whether this could be one of two things:
1.
A hardware fault - possibly in the charging circuit or more crudely one of the battery circuit board connectors is not connecting.
OR
2.
The circuit that controls charging has to put it crudely become "stuck" in a similar fashion to those who get the RLOD red LED showing when they connect the charger. A commonly accepted trick for overcoming the RLOD is to connect the charger and wriggle the battery on and off the four contact pins. This presumably has the effect of forcing the charging circuit to re-set itself. I just wonder whether it might have the same effect in your situation.
Mike
hey.. that would be me with the similar issue.
i just tried a couple more things.. check out the thread.
More info.
Battery in and out holding the power button had no effect. Phone runs fine while plugged in. Plug it in and after 5 seconds the amber LED turns to red. While plugged in the red led will flash amber every so often.
I measured the battery voltage as I turned the phone on, it dropped to ~ 3.98v, then came back to 4.1v as the phone turned itself off. It gets all the way to my Today screen before going off. Just sitting in the phone with it off is 4.1v. Hook up the charger and the battery sees 4.18 and rising after 20 seconds. These are direct measurements at the battery terminals while in the phone.
So this looks like a software issue to me. The phone is charging the battery and there is plenty of power to run the phone, the phone somehow doesn't see it that way. It sees a dead battery. Well, I guess it could be a voltage sensor gone bad , somewhere somehow. Next step is to hard reset and see if it makes any difference.
edit: While plugged in and the screen on, the led stays amber. When the screen goes off(set for 2 minutes) the led turns red. Screen back on, led amber. I just set the screen not to go off while plugged in(charging), we'll see. The power is showing 7% now and says charging, too early to tell if it's rising or not.
edit 2: It stayed on the charger for several hours and never moved past 7%. Tried a hard reset with no luck. Next step is to send it to a repair shop(I bought it used) and hopefully spend only the $95-$125 they quoted.
Will keep you apprised.
Ed
elknimrod said:
I have this strange problem that just cropped up. After a full recharge the other day the battery showed normal draining. When I tried to recharge it wouldn't; neither from the wall charger or usb by computer. So the battery showed steady drain unless charging, but never got more charge. Finally when turning on the phone on battery alone it shows 1% charge, and there's nothing I can do about it, the phone will turn itself off.
Diagnostics: I measured the battery voltage and it is ~4.2 volts. This seems like a full battery yet the phone doesn't see it.
I measured the voltage at the battery terminals in the phone while hooked up to charger which was ~4.2 volts. So it seems the battery is being charged.
Why is the phone not seeing the battery charge? Is the battery dead even though it measures 4.2v?
I did run the gps before this happened using gps tool, bit I think I turned it all off. Anyway more than one soft reset didn't help.
Thanks,
Ed
ATT Tilt 8925 running gthing Blackwood rom with Vista BatteryHide. Original ATT radio.
Click to expand...
Click to collapse
Att Tilt Power/Battery Issues.
I am having somewhat similar issues with my Tilt, with the power/battery problems as described previously. I woke up this morning, and attempted to turn my phone on, and it wouldnt come on at all. I then plugged it into the ac adapter, and the LED comes on, and goes green. I waited a few moments, then powered the phone on to take a look at the battery life, and the phone boots up, then reboots during the splash screen. After it reboots itself, I check the battery indicator and it shows 1%. If I exit the battery screen, and re-enter it, it will say 100%. Now, as soon as I remove the charger from the system, it automatically powers down. I played with it for about 15 minutes, but needed to head to work, so I took the phone with me, and attempted to use my car charger. Same problem. Now, I figured, fine, I'll see how it behaves while I am at work, so I brought my charger to work, and have it plugged in at my desk, and if I leave it plugged in and on, it stays on for about 5 minutes, then automatically reboots. LED stays green, but phone will not stay on, if unplugged, or plugged in for longer than 5 minutes. I have never dropped it, and have babied the phone like no other, concidering I paid $400 for it. I'm a little bummed out, but cant determine if its a battery or hardware problem. Any advice/input for me from any of you guys? before I head to the ATT store, and cry for a new phone? Thanks a bunch for any responses to this.
*UPDATE* After I got off work, I went into my local ATT store, explained the situation, and was given a brand new replacement phone in like 10 minutes. I was under 30 days owning it, so he just swapped it out, barley any questions asked. (altho i explained my situation in detail as it was). So.... hopefully it doesnt happen again, or else I'll have to use the warranty. Anyways, Any insight on what may cause this would always be helpful for both myself and the community. =)
new news
EDIT: They got it Monday and I got it back Friday. Good turnaround! They fixed the problem, it works perfectly now. I recommend these people.
Ed
Sent it off to Cell Phone Repair(CPR) in Chicago that gave me an estimate of $95 (inc. ship. back) based on my description. They just called and told me it was corrosion around and in the power/usb port. They got it yesterday and will send it back repaired tomorrow with a 90 day warranty. No more saunas for this phone(it was only one! )
I'll let you know if they work out well or not.
Ed
elknimrod said:
I have this strange problem that just cropped up. After a full recharge the other day the battery showed normal draining. When I tried to recharge it wouldn't; neither from the wall charger or usb by computer. So the battery showed steady drain unless charging, but never got more charge. Finally when turning on the phone on battery alone it shows 1% charge, and there's nothing I can do about it, the phone will turn itself off.
Diagnostics: I measured the battery voltage and it is ~4.2 volts. This seems like a full battery yet the phone doesn't see it.
I measured the voltage at the battery terminals in the phone while hooked up to charger which was ~4.2 volts. So it seems the battery is being charged.
Why is the phone not seeing the battery charge? Is the battery dead even though it measures 4.2v?
I did run the gps before this happened using gps tool, bit I think I turned it all off. Anyway more than one soft reset didn't help.
Thanks,
Ed
ATT Tilt 8925 running gthing Blackwood rom with Vista BatteryHide. Original ATT radio.
Click to expand...
Click to collapse

Battery does not charge

So friday I noticed that the time would lag. sometimes 20 minutes, sometimes 2 hours behind, a soft reset put it back in normal time. Weird. Today I went to grab it to go to work as it had been charging all night long with a steady green light. I open it up and there is a red icon for the battery...23%..... I hook it back up to the AC adapter and see what it does, it shows a plug to symbolize charging and I check it 30 minutes later, it has dropped to 20%. My bluetooth is off. I now have it hooked up to the AC adapter and removed the battery, i have the battery on a charging dock and the TyTn II has a faint red LED where the normal area for the charging LED is. I am gonna see whats happening in an hour with the battery...
Has this bricked?
Time lags and battery does load now. Its only been in use for 9 months, never been dropped.
Pete
I love how people never think the battery is going bad and always think it's the phone right off the bat.
Try another battery and see what happens. Hopefully you bought it new and still have the warranty on it.
Okaaaaaaaaaay....I do not lack in the technical department. The battery charges on the dock and I got it up to 100%. I loaded it back in the TyTn and let it sit for 3-4 hours and it dropped to 90%. I hooked up the AC Charger to it and I got the steady light up on top like it normally charged before all this. The battery continued to drain. I now have it powered completely off and using my old KRZR....(smartphone to cell phone....wonderful) I have a new battery on the way for a week now so it should arrive shortly.
Some wiring leading from the Mini-usb to the actual battery must be corroded or something. I cant explain it...I do live by the sea, and if the contacts are not gold plated in there...I can see some problems occurring. I doubt the warranty would still be intact as I have upgraded the ROM to Win 6.1
read here:
http://forum.xda-developers.com/showthread.php?t=448467
Thanks Garfield....I knew there had to be some sort of explanation....

Does your phone get hot charging USB?

Please, I'd like to see feedback from people on what circumstances people are seeing their phone get hot charging USB. If your phone gets hot on a USB charge, try powering down the phone completely and then charge on USB, does it still get hot?
And please, if your phone gets hot on USB charge, post how you're charging, your ROM, and how hot does it get? There are many applications for this. I use Battery Snap, you can use any program you like. If you don't have a program, please don't guess at the poll, but feel free to post results in a reply.
Also one would assume ambient temperature in the room is typical, but if yours is not (<20c, >28c) please post that information too.
Please answer the poll by the typical range of temperature your phone gets on a USB charge. I'd suggest charging around the 50-60% mark to get more consistent results.. For example charging if the phone is at 95% wouldn't be useful information etc..
One more slight constraint; if your phone gets hot "one time" but not other times, I'm inclined to think there was something else going on with the phone at that time. If your phone is consistently hot when charging USB then post results here.
Reserved in case I need to add any info..
I charged my phone off my Dell M6400's docking station today, started the charge after pulling the phone out of my horizontal case and the phone was 29.5C, I looked multiple times at the highest I saw it was 31.3, and most of the time 31.1. Using Battery Snap for the data. Started charge at 80%, as that's what charge it was from this morning until 4pm when I started I do not have USB Debug enabled by default on my phone, nor did I have mass storage.. When I got the mount prompt I just hit the back button.
Phone is about neutral to the touch, slightly cool. Normally when it's on my desk like this it's fairly cold to the touch, so I'll have to update later when I've put the phone in the same place without charging, but I'm guessing it's a few degrees warmer on the charger than off of it.
I'll repeat this a bit over the weekend here too as I have time, this time I'll set the phone sit on the desk for a while first, check temperature, then charge.
Please do post when you provide input on the poll so we know the circumstances... I mean, if your computer room is 35C and your phone gets 40C charging, I think that's reasonable My office here is around 24-25C.
Charged again today from about 75%, house is around 23C (wife likes it cold..meh) and the phone was 27C max charging on USB.
My AT&T Nexus One purchased June 2 from Google overheats and reboots.
Here's what I've found out:
I charge with the original AC Adapter and this only happens when I'm charging and the battery is LESS than 40%.
If the battery is 50% or higher, it's fine.
When the Battery is less than 45%ish, the phone gets hotter and hotter, from 33C up to 39.3C (is what I last see), then it will SHUTDOWN AND REBOOT. When it reboots, it would be about 37-38C. If it's still under 45%, temp will keep rising again, till 39.3% and REBOOT again, takes about 5-10 minutes for this to happen.
Weird thing is, if you pop the battery out and FEEL it, IT IS NOT HOT AT ALL. It's the DAMN phone that OVERHEATS.
2 nights ago, I was charging and reading in bed. IT DID THIS 3 TIMES IN A FREAKING ROW.
7AM EST, I called HTC, and doing a Device Swap.
Have not received my replacement unit yet. Funny thing is, HTC told me they send out device swaps of JUST THE PHONE, no battery no battery cover. So I have to keep my battery and battery cover. And I told them about my overheat/charging/battery issue, and they said if it still happens to mine, they can send me a new battery.
Anyways I will be testing the replacement unit with my battery and make sure it's VERY low to see if it overheats and reboots.
Other info: This happened in OFFICIAL STOCK FRF91. I'm currently running CyanogenMOD 6 RC1.
nxt said:
My AT&T Nexus One purchased June 2 from Google overheats and reboots.
When the Battery is less than 45%ish, the phone gets hotter and hotter, from 33C up to 39.3C (is what I last see), then it will SHUTDOWN AND REBOOT. When it reboots, it would be about 37-38C. If it's still under 45%, temp will keep rising again, till 39.3% and REBOOT again, takes about 5-10 minutes for this to happen.
Click to expand...
Click to collapse
Hmm, yeah that sounds like hardware problems to me.. Curious, what are you using to measure? I'd assumed the battery temp stuff was really the battery, not .. something else?
In my case when my phone is cool, the whole phone is cool, not just blindly looking at numbers of course.
Again, would the folks voting really high temps try the things in my first post, and let us know what the ambient temperature of the room is, how hot the phone feels vs the measurement, what's being used to measure it... But particularly I'm curious if totally powering down the phone makes the problem go away.
Dial *#*#INFO#*#* then select Battery Information. It will tell you temperatures there. But I think the temps there is phone temp not batt temp, since in my case when it days 39.3C and I pull the batt, it feels less hot than the phone itself.
Also for my case, it does get hot and reboot while USB charging. Reported 3 time in a row again yesterday and I got pissed and HAD to turn the phone off.
Anyways, waiting for my replacement u from HTC.
Well got my replacement Nexus One today, serial number is higher than my 1 month old Nexus One.
I got it go to up to 39.8C and it did not shutdown and reboot, but stuff started crashing.
Music playing would stop, then if I try to start the song again or choose another one, Music app would Force Close.
Started Navigation app and that right away FC.
Anyone experiencing this?
I think you are using a goofy USB cable, or your room is HOT. Because the only time I've had my phone overheat, I was at a pool, in the sun. The phone's temp was 45 c also. I could still use it, but it was burning hot. An app notified me of the temp (I had it set that way) and I turned the phone off.
stuff said:
I think you are using a goofy USB cable, or your room is HOT. Because the only time I've had my phone overheat, I was at a pool, in the sun. The phone's temp was 45 c also. I could still use it, but it was burning hot. An app notified me of the temp (I had it set that way) and I turned the phone off.
Click to expand...
Click to collapse
I'm using both the original AC adapter and usb cables from google.
Also AC has been on it's under 80F in the room.
The other day on the unit that keep rebooting, when I was navigating, i had to hold it up to the AC vent while i was driving to be able to use it... lol... sigh.
I usually only charge on ac but i think i can easily hit 37-39 while charging for over 30 minutes. Its has been up to 40.5 before i think but there were no crashes or anything. everything was stable (its hot but not enough to be seriously scared or anything)
the room at night is around 24? varies alot but the phone also sits on my bed and/or pillow/blanket. try not to cover it when i sleep.

(Not) Brick - Didn't Calibrate Battery After ROM

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.

SGS charging without charger plugged in

The other day I was in a hospital and my phone was next to the bed but the charger wire was tangled in the bed. So a nurse came up and rolled out the bed and the phone fell from quite high on the (hard) floor.
It still worked, screen wasn't cracked so I didn't think much of it.
But now, the phone can be charged with the charger. As soon as I unplug the charger there are 2 things that can happen:
1. The phone keeps saying it's charging. Other than that the phone is fully functional. Battery drain is much higher though, in 10 minutes I lose 7% battery.
2. The charging icon in the battery will flash on and off. When I switch off the screen, the lock-screen immediatly turns on and the text charging blinks, it's like someone is plugging in the charger and takes it out immediatly, battery drain is even higher when this occurs, I lose 50% within the hour, depending of what I'm doing.
Sometimes the problem is not there, the phone will function normally, but the problem will come back within 1 or 2 hours and usually when I plug in a charger and take it out later. Also, sometimes it seems the phone is not charging and the charge indicator will stay at a certain percentage but when I reboot the phone it it fully charged (according to the indicator).
First I thought it was an android problem. But when I switch off the phone the charging image appears as well and starts blinking, also the menu and back button flash on and off. It's also quite difficult to switch on the phone at this point and the battery image shows only the outline of the battery, not how much charge is in it.
So far I tried 2 other chargers, 2 other batteries (1 original Samsung and 1 after market). Rebooted the phone many times and left the battery out for an hour.
Anyone knows of what causes such a problem? Of course, the fall was the start of the problem. Could there be some pins bent in the usb socket of the phone?
vinz3nt said:
The other day I was in a hospital and my phone was next to the bed but the charger wire was tangled in the bed. So a nurse came up and rolled out the bed and the phone fell from quite high on the (hard) floor.
It still worked, screen wasn't cracked so I didn't think much of it.
But now, the phone can be charged with the charger. As soon as I unplug the charger there are 2 things that can happen:
1. The phone keeps saying it's charging. Other than that the phone is fully functional. Battery drain is much higher though, in 10 minutes I lose 7% battery.
2. The charging icon in the battery will flash on and off. When I switch off the screen, the lock-screen immediatly turns on and the text charging blinks, it's like someone is plugging in the charger and takes it out immediatly, battery drain is even higher when this occurs, I lose 50% within the hour, depending of what I'm doing.
Sometimes the problem is not there, the phone will function normally, but the problem will come back within 1 or 2 hours and usually when I plug in a charger and take it out later. Also, sometimes it seems the phone is not charging and the charge indicator will stay at a certain percentage but when I reboot the phone it it fully charged (according to the indicator).
First I thought it was an android problem. But when I switch off the phone the charging image appears as well and starts blinking, also the menu and back button flash on and off. It's also quite difficult to switch on the phone at this point and the battery image shows only the outline of the battery, not how much charge is in it.
So far I tried 2 other chargers, 2 other batteries (1 original Samsung and 1 after market). Rebooted the phone many times and left the battery out for an hour.
Anyone knows of what causes such a problem? Of course, the fall was the start of the problem. Could there be some pins bent in the usb socket of the phone?
Click to expand...
Click to collapse
I had a problem recently in which even though I kept my phone on charging (and it showed that it is charging), the battery percentage either remained same or it went down even though it was plugged in.. went to samsung and they said the usb port is damaged and they replaced it.. I think the same resolution will be for your problem
Mmm....makes sense. What does Samsung charge for that?
Sent from my GT-P7310 using XDA Premium HD app

Categories

Resources