Wonky Battery sensor suddenly goes form 60% to 0 - Xperia Z3 Compact Q&A, Help & Troubleshooting

I'm trying to figure out the best solution for my wife's Z3 compact. It's unrooted running Lollypop. Besides a shortened battery life, which could just be a battery needing to be replaced situation, her battery sensor is very wonky... often it will appear it has plenty of charge like 80 or 60 and then suddenly drop to zero and shut down... plugging it in after that but not booting it will also show 0 percent.
We've tried both clearing the cache by holding up and power when its off for 3 vibrations and also when its on hard shutting it down with the button next to the SD card but the problem still persists.
I'm thinking I'll replace the battery, but since its a hassle with this model (I'll have to buy a heat gun) I wanted to check in here in case this sounds like larger problem then just a battery near the end of its life.
Thanks.

If you try a complete factory reset or flash a new firmware and it still has issues, I would just replace the battery. This happened to my Z1 and when I replaced the battery it was back to new.
Instead of a heat gun you could try a strong hair dryer. Also, you might need to re-glue the back cover afterwards as the adhesive might be worn out when you take it off.

Related

power management all messed up

hey, got a big problem with my kaiser:
my power management is all messed up.
sometimes the phone charges for 3 hours and the bar displays 15% power. after unplugging and replugging power cable battery is 100% all the sudden.
sometimes i have like 70% power left, the phone shuts down and wont start until i plug in power. then it says 2% power.
sometimes the power drops from 100% to 50% after using music player for 20 min.
i tried to load completely and use the phone until battery empty, then take out battery and relaod until full. seems not to work...
any fix for this?
Try cleaning the battery contacts
Also, is it an old battery? They eventually lose the ability to keep a good charge. Might be time for a new one.
contacts seem to be clean...
phone and battery are about 10 months old, shouldnt be a problem?
They might look clean, but you often can't tell
try a little isopropyl alcohol (10%) on a swab and gently clean the contacts on both the battery side and the device. Let it dry for about 5 minutes then swab the contacts lightly with a clean dry cloth.
Now look at the spring-up contacts on the device side. If any of them look like they are too low and might not be making sufficient contact, use a small screwdriver to GENTLY pry it up a little.
Your battery at 10 months should still have some good life left in it, if it's more than 18 months old it might be time to look at a new one.
maybe it's your ROM? try flashing..
is the rom responsible for power management? or can it have something to do with radio / hard spl?
Not to offend any of the posters. But why would anyone waste there time replying to a thread with a title like this one. I personally don't have a problem with it, but this is a open community and its pretty shameful on the op's behalf.
holzzelt said:
hey, got a big problem with my kaiser:
my power management is all ****ed up.
sometimes the phone charges for 3 hours and the bar displays 15% power. after unplugging and replugging power cable battery is 100% all the sudden.
sometimes i have like 70% power left, the phone shuts down and wont start until i plug in power. then it says 2% power.
sometimes the power drops from 100% to 50% after using music player for 20 min.
i tried to load completely and use the phone until battery empty, then take out battery and relaod until full. seems not to work...
any fix for this?
Click to expand...
Click to collapse
please watch your language.

(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.

Nook HD Plus - charging issue.

No technical skills here. I have a "regular" Nook HD Plus with no modifications. Version 2.2.1
Started w/weird charging ... It would say battery full when on the charger, then as soon as taken off charger would say a random % charge like 15%.
Then had some overheating problems - if running on battery it would heat up and turn off then restart - If I ran it with the charger connected, had no problems.
Now, not taking a charge. The indicator light turns amber for a few seconds then goes to green. Says discharging even though plugged in.
Have tried shutting it down but that had no effect.
Found a replacement battery online w/tools to open the unit up and replace but am not sure if it's the battery, the charging cable, or if the unit heating up damaged a board or something. Currently have about 15% charge left, and can access programs and games w/no problem.
So what's your educated guess ... if I replace the battery will that fix it, or should it be retired.
If you think it should be retired, a recommendation for a new tablet would be appreciated.
Mostly use it for reading, games, Facebook - things like that.
Appreciate the help.
What would you lose by opening it up and replacing the battery if you're considering retiring it?
I had a problem where it would restart whenever the speaker was on the highest setting and it made a loud noise. I simply opened it up, checked it out, and somehow that fixed it. Maybe it was a short circuit? I don't know, but I didn't have anything to lose by it. I recently also thought my battery was bad as the HD plus didn't turn on but all I had to do was keep trying a hard reset. You could also put a custom rom on it. That helped with my overheating issues and usually does the same with Android phones that I have had.
Cool to see someone else from Miami here too.
It MAY be the battery, but I would strongly suggest backing apps up, then going into the stock recovery, and doing a full factory reset from there.

Xperia Z3+ Power Shut off

In addition of to very short battery life post MM (6 hrs to 50%) I've been having an issue with power management. It has happened a number of times when my battery has been between 30 and 50%. The unit will power down giving me an out of power message and if I reboot the battery indicator will show 30-50% before immediately showing empty and powering down again. Even a short connection to a power source seems to reset the problem and I can use the phone normally until it gets down to sub-10% when it drains quickly again. This does not happen every-time it reaches this level and may be related to the final 15-20% of power disappearing very quickly.
I've returned the unit to Sony and they say a bent frame and damaged screen are the cause and the repair isn't covered by the warranty. The screen looked fine when I sent it off to them and there was no discernible damage to the frame. The unit lives in a smart cover and stays out of back pockets.
The Sony support form has other users with similar sounding problems and I wonder whether anyone here has encountered similar. Next, does the Sony repair explanation sound plausible, they want £130 to fix something that doesn't seam to be related to the initial problem.
Pucking SONY CARE always gives false statements.

top part of phone get hot after screen replacement

Hello
My screen cracked so I ordered a new on ebay. However after I have put the phone back in its shell the top part gets pretty hot. I opened it and started it without the aluminum shell to test and there were no heat? Anyone know what it might be?
Thanks In advance!
That isn't likely to be the screen. My phone gets warm too. About 4 days ago out of nowhere I noticed the upper part of the screen feeling warm, it turns out my phone had stopped sleeping properly and Google services had resumed chomping on my battery when the screen was off.
Tho when i don't keep it in the aluminium case it's not warm at all, turned on and I have logged on my simcard/wifi. I have left it on outside of the case for 1 hour and it don't get warm at all. However in the case it gets super hot as soon as it boots and then after 15-25m it turns off probably because it's too hot
Happened the same last night with me.
Put a download and slept, and in the morning it was all drained of battery and it showed that it shut down after minutes after I slept with 90%battery.
It was weird. Had to keep pressing power button for 40 sec approx for the phone to turn on.
It's working fine now though
did anyone of you even read my post? I said after a screenreplacement. It didn't just happened randomly. however i fixed it. I removed the camera and the earspeaker and reinstalled them used some alcohol on the contact points on the case and the earspeaker and it seemed to fix it if anyone has this problem later down the road
Hi jullleee, I have the same problem as u after I replaced the screen. The phone getting too hot on the top (one plus 3). On charge it becomes more hot and faster on very high temperature than without charging. Also the battery dont charge . Why did u reconnect the ear speaker and the camera ? Thank you in advance
DestinyisGone said:
Hi jullleee, I have the same problem as u after I replaced the screen. The phone getting too hot on the top (one plus 3). On charge it becomes more hot and faster on very high temperature than without charging. Also the battery dont charge . Why did u reconnect the ear speaker and the camera ? Thank you in advance
Click to expand...
Click to collapse
For anyone coming across this thread I just had the same problem when replacing my Oneplus 3 screen. It seemed to work, and I plugged it in, but it said "battery too low charge for a while", then I got the 0% and seemed to charge and then restart, and then be back at 0% and be stuck in this boot / charging loop. My battery had died hard when my screen died so I thought maybe it just needed to charge for a while, but the top half of the phone got very hot.
So I took it apart again and it turns out the issue for me was with the top ribbon cables that cross the battery. Where they connect to the main board was very tight and it was difficult to get both of them in place properly. Usually they kind of overlapped and one stuck up slightly. It was fixing their placement before bolting down their cover that fixed this issue for me.
Edit: Never mind. Still searching for my issue. Taking the back case off will let it work normally but whenever i snap it on it goes back into this charging loop, I still suspect it's an issue with these two cables and the case is putting pressure in the wrong spot or something but I'm not really sure yet.
I had the same problem, the issue was the fact that i plugged the ribbon cable the other way around.

Categories

Resources