hello ppl,
I have this issue with my battery:
This afternoon my battery indicated 82%. the phone shut down and after a reboot it indicated around 27% battery left.
Later in the afternoon, after a reboot, I charged it for like 2 mins. it indicated 12%
I unplugged it and rebooted into recovery (4EXT) and it indicated 60% battery lvl.
I rebooted the ROM again and this indicated 34%
this event (reading 3 different battery lvls) took place in 1 minute, and the phone was not charger connected. It went from 12, to 60 and to 34%.
This really looks like a battery stats issue but what I can't help to wonder about is the following; do recovery and the ROM use different battery stats? this particular story sure gives that impression.
I plan to wipe battery stats after a full USB charge. U guys got any pointers I could consider? I have a stock batter for about 2 years now.
ROM: CM10.1 by Albinoman
Kernel: 3.0.67 ChronicBruce Linaro
Governor: ondemand
clockspeed: MIN 384 MAX 1728
I/O schedular: SIO
note: I did not experience any battery issue with this setup for at least 4 months prior to this problem, while using this setup.
attached a SS of the battery levels after reboot and shutdowns.
Seems like you're experiencing the same issues. The battery percentage was also way higher in recovery mode than Android showed me. Never noticed that before, so I'm not sure if that's normal, or both our phones / batteries are malfunctioning.
Wiping battery stats does nothing. 2 years is quite long for a battery, get an Anker?
onemanshow85 said:
hello ppl,
ROM: CM10.1 by Albinoman
Kernel: 3.0.67 ChronicBruce Linaro
Governor: ondemand
clockspeed: MIN 384 MAX 1728
I/O schedular: SIO
note: I did not experience any battery issue with this setup for at least 4 months prior to this problem, while using this setup.
attached a SS of the battery levels after reboot and shutdowns.
Click to expand...
Click to collapse
Before buying a new battery, did you attempt to flash a new ROM? becuase you seem to run a (very) old version of CM10.1 (I believe since March?), and although it's weird this popped up after four months, it is possible to be a problem in the ROM, especially with all the bugs fixed along the way. I believe updating the ROM should be the thing to do, before trying to change hardware parts (even battery), and if it won't work, you can always buy a battery (don't ofrget to back up your current ROM first).
astar26 said:
Before buying a new battery, did you attempt to flash a new ROM? becuase you seem to run a (very) old version of CM10.1 (I believe since March?), and although it's weird this popped up after four months, it is possible to be a problem in the ROM, especially with all the bugs fixed along the way. I believe updating the ROM should be the thing to do, before trying to change hardware parts (even battery), and if it won't work, you can always buy a battery (don't ofrget to back up your current ROM first).
Click to expand...
Click to collapse
I'm a mediocre XDA visitor and phone tweaker, so I didn't realize ROM's would get obsolete that quick (in my opinion). I will try to flash a updated CM, see if that works.
ok I updated my ROM. But there's no change in my batterie's behavior: shutdowns at high battery lvls and drops from enar full to near empty after the reboot.
I'm plannign to buy an Anker. but if anyone has some pointers that would be mint.
I already did the paper between battery trick.
Another update, today i noticed that the battery is a little bit swollen. The battery casing doesn't close properly anymore. When looking closely i notice the battery being slightly thicker. I don't trust it and don't use it anymore untill i got the anker
Related
Howdy folks. I have a major problem with my t769, and was hoping someone could help me figure it out. This problem began quite some time ago and has gotten worse. My battery stopped accepting a full charge (according to the meter.)
I had been running PA (racing port) for quite a while without a problem. The problem may have cropped up due to charging the phone while off at some point. When the problem first appeared, it would only charge up to 98%. I chalked it up to the fact that some phones apparantly don't trickle charge (for battery longevity?). Then the phone would only get to ~90%, then 83%... etc.
I have tried all three kernels available to us, nothing changes. Tried several different basebands. Tried reinstalling PA, no dice. Tried changing roms. Currently on Provision rom. The battery will not charge beyond 48 percent.
My issue does not appear to be a faulty battery; I recently purchased a couple new batteries and they do the same thing. Even after charging with an external charger - the phone still misreports the battery capacity. This has the effect of reaching a battery level of 0% (according to the meter) long before the actual battery capacity is exhausted. Further to that end, the android battery stats are never automatically wiped since the phone's battery meter never actually reaches 100%. The android battery stats page currently shows 4days on battery. I suppose this is because I last manually wiped the battery stats or pulled the battery 4 days ago.
Some more odd tidbits...
When the phone's battery meter reports 0%, the phone will automatically shut off ONLY if the display is ON. If the phone reaches the 0% mark while the display is OFF, it will continue to run and sometimes readjust the battery meter in 4-5% increments. i.e. if I turn off the screen when it hits 1%, and turn back on the screen some time later and the meter will report 4%. Other times it seems it will not readjust the meter while the screen is off and will remain at 1%. When the phone reports 1%, the battery is still outputting at least 3.5v. From what I understand, most 3.7v lithium ion batteries have an approximate safe operating range of between 3.2v-4.2v.
Really odd:
It seems that once the battery is pulled, the meter will revert to 0% once the phone is booted regardless of what the meter showed before the battery pull. I have not done this in the last couple days but it has happened several times and appears to be a repeatable issue.
All of my problems could logically be caused by a battery miscalibration, save the last point.
I have tried several calibration apps in the market that don't seem to do anything. I recently stumbled on this huge thread:
http://forum.xda-developers.com/showthread.php?t=765609
I have not read through all 200+ pages but it seems this has worked for many people. Unfortunately, I've been unable to get it to report values with the lightningX2 or CM10 kernels though. It states that the CM kernel should be supported, so I don't understand why it doesn't want to spit out values.
Any help would be greatly appreciated. I've grown quite attached to this phone and would like to continue using it!
Charge your phone overnight. Reboot to recovery (leave the phone plugged in). In cwm navigate to the advanced menu. Then in that menu wipe battery stats. Then let your battery drain down as much as possible before charging it again.
That should fix it.
Sent from my SGH-T769 using xda app-developers app
Many thanks for the reply. I'm currently using TWRP and I dont believe there is a section to wipe the battery stats.
I have removed the batterystats bin manually once android has booted both when the battery is in a near-dead state and in a near-full state and neither seemed to change the meter level. Perhaps I will see a different result by removing this file through recovery before Android boots?
I may install CWM to give this a shot soon but from what I understand, and please correct me if I am mistaken, the removal of this file has no bearing on the actual battery calibration. It was said that this file only affects what is displayed in the android battery stats page. There does appear to be a lot of confusion and controversy across the forums regarding whether or not this file is indeed responsible for actual calibration between true battery capacity and the state of the battery meter.
Not sure if this is important but when charging the phone (while turned off) the bootloader charging animation seems to report a value that is consistant with what the booted meter reports. (i.e. the animation will show ~50% battery left when the meter inside android will report 48%)
anactoraaron said:
Charge your phone overnight. Reboot to recovery (leave the phone plugged in). In cwm navigate to the advanced menu. Then in that menu wipe battery stats. Then let your battery drain down as much as possible before charging it again.
That should fix it.
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
kmem said:
Many thanks for the reply. I'm currently using TWRP and I dont believe there is a section to wipe the battery stats.
I have removed the batterystats bin manually once android has booted both when the battery is in a near-dead state and in a near-full state and neither seemed to change the meter level. Perhaps I will see a different result by removing this file through recovery before Android boots?
I may install CWM to give this a shot soon but from what I understand, and please correct me if I am mistaken, the removal of this file has no bearing on the actual battery calibration. It was said that this file only affects what is displayed in the android battery stats page. There does appear to be a lot of confusion and controversy across the forums regarding whether or not this file is indeed responsible for actual calibration between true battery capacity and the state of the battery meter.
Not sure if this is important but when charging the phone (while turned off) the bootloader charging animation seems to report a value that is consistant with what the booted meter reports. (i.e. the animation will show ~50% battery left when the meter inside android will report 48%)
Click to expand...
Click to collapse
Just out of curiosity, does this happen across all roms? Does it do it for stock as well? Maybe return to stock and check? I gave up on TWRP not because I didn't like the recovery, but it seemed to be... off... somehow... The 2.4 wouldn't restore backups (and would randomly reboot), and the 2.3.3 wouldn't reboot when plugged in (it would just power off). I also had some issues with my sd card with one of them (2.3.3 I think but not sure) on one of the JB roms and I lost all of my data. After going back to CWM 5.5.0.4 I haven't had any issues.
Both TWRP versions are built on the default CM10 kernel (correct me if I'm wrong here). I went back to stock about 2 weeks ago and am getting 4-5 days on battery life (light usage) where on ANY JB kernel the most I could get was a day and a half. Perhaps there's something missing/wrong with the JB kernel, and as such, TWRP isn't working properly because of it.
Perhaps the battery isn't getting read properly... have you tried cleaning the contacts with iso alcohol?
Sorry I couldn't be more help...:crying:
It happens for the two JB roms I have tried. I've not tried to return to stock yet but if you are getting 4-5 days of light usage that is incentive enough for me to give it a whirl! I never was able to squeeze more than about a day and a half out of a JB rom on my blaze either, even before these battery problems cropped up. I started using TWRP on my last phone mainly due to the fact that it can compress the backups but I've also become more accustomed it's UI. I think I'm currently using 2.4, but I vaguely remember both the SD issue and the power off instead of reboot issue you describe with the previous rev.
I can't speak to if the recoveries are built from CM. Now that you mention it, both JB roms that I have tried on the blaze show higher than normal battery usage by media and android system processes. Are you running a complete stock ICS or GB rom, or is it some debloated one? Can you tell me which one it is?
I've cleaned both the internal battery connector and micro usb connector to no avail. You have been a great deal of help, thanks again!
One other quick Q... After returning to stock, do you still have the black and white colored (powered off) charge animation? Ever since I rooted this thing, the power off charge animation starts up with the stock color (green filled battery) but quick flashes off and changes to the black and white one. Perhaps this is part of my problem, remanants of the stock bootloader mixed with the rooted one?
anactoraaron said:
Just out of curiosity, does this happen across all roms? Does it do it for stock as well? Maybe return to stock and check? I gave up on TWRP not because I didn't like the recovery, but it seemed to be... off... somehow... The 2.4 wouldn't restore backups (and would randomly reboot), and the 2.3.3 wouldn't reboot when plugged in (it would just power off). I also had some issues with my sd card with one of them (2.3.3 I think but not sure) on one of the JB roms and I lost all of my data. After going back to CWM 5.5.0.4 I haven't had any issues.
Both TWRP versions are built on the default CM10 kernel (correct me if I'm wrong here). I went back to stock about 2 weeks ago and am getting 4-5 days on battery life (light usage) where on ANY JB kernel the most I could get was a day and a half. Perhaps there's something missing/wrong with the JB kernel, and as such, TWRP isn't working properly because of it.
Perhaps the battery isn't getting read properly... have you tried cleaning the contacts with iso alcohol?
Sorry I couldn't be more help...:crying:
Click to expand...
Click to collapse
kmem said:
It happens for the two JB roms I have tried. I've not tried to return to stock yet but if you are getting 4-5 days of light usage that is incentive enough for me to give it a whirl! I never was able to squeeze more than about a day and a half out of a JB rom on my blaze either, even before these battery problems cropped up. I started using TWRP on my last phone mainly due to the fact that it can compress the backups but I've also become more accustomed it's UI. I think I'm currently using 2.4, but I vaguely remember both the SD issue and the power off instead of reboot issue you describe with the previous rev.
I can't speak to if the recoveries are built from CM. Now that you mention it, both JB roms that I have tried on the blaze show higher than normal battery usage by media and android system processes. Are you running a complete stock ICS or GB rom, or is it some debloated one? Can you tell me which one it is?
I've cleaned both the internal battery connector and micro usb connector to no avail. You have been a great deal of help, thanks again!
One other quick Q... After returning to stock, do you still have the black and white colored (powered off) charge animation? Ever since I rooted this thing, the power off charge animation starts up with the stock color (green filled battery) but quick flashes off and changes to the black and white one. Perhaps this is part of my problem, remanants of the stock bootloader mixed with the rooted one?
Click to expand...
Click to collapse
I'm running stock rooted uvmb1 (ics), which I've debloated and customized a bit (nothing special). Stock roms have the stock battery charging animation.
The battery drain is just one of those things I can't fully explain, as I have a few other devices running CM10 or 10.1 and they have great standby/light usage battery life
Of late, I have been having heavy drain of battery on my Atrix 2. I am running JB 4.1.2 (672.300.404.ME865.Retail.en.05). Trying to troubleshoot it (including recalibration) since the last few days without luck.
The symptoms...
- Sudden shut down - Have had 50%+ charge levels. Goes down to 5% and shuts down within minutes. (You can see the random drops in the charge levels in the pic)
- Completely drained out battery charges from above 40% when plugged in & charges to 100% in no time. (that 67% charge in the attachment is within 5 mimutes of power plug in)
Does the battery need a replacement?
ravi-atrix2 said:
Of late, I have been having heavy drain of battery on my Atrix 2. I am running JB 4.1.2 (672.300.404.ME865.Retail.en.05). Trying to troubleshoot it (including recalibration) since the last few days without luck.
The symptoms...
- Sudden shut down - Have had 50%+ charge levels. Goes down to 5% and shuts down within minutes. (You can see the random drops in the charge levels in the pic)
- Completely drained out battery charges from above 40% when plugged in & charges to 100% in no time. (that 67% charge in the attachment is within 5 mimutes of power plug in)
Does the battery need a replacement?
Click to expand...
Click to collapse
Try changing battery... even i had same problem with Custom rom. Battery used to last only for 10 to 12 hours but now its more than 17 hours on JB 4.1.2 leak,,,,...Use stock rom. and remove any unncessesary apps and installl ROM again if u want :good:
How old is your Atrix 2? If over a year then battery surely begins to give lesser performance. Disable any other task killer / memory manager & just let OS do its thing. See if installing Media Scan disable from play helps & do not keep using random chargers, make use of original charger as received with phone. Finally see Better Battery Stats. It is said battery stats should never be wiped but see if it helps you and finally search for Apex's better battery life guide for many handy tips.
I disabled notifications, sync, froze higher wakelock apps & my battery life improved a bit but then it is no fun existing in a bare bones environment.
RAD7 said:
How old is your Atrix 2? If over a year then battery surely begins to give lesser performance. Disable any other task killer / memory manager & just let OS do its thing. See if installing Media Scan disable from play helps & do not keep using random chargers, make use of original charger as received with phone. Finally see Better Battery Stats. It is said battery stats should never be wiped but see if it helps you and finally search for Apex's better battery life guide for many handy tips.
I disabled notifications, sync, froze higher wakelock apps & my battery life improved a bit but then it is no fun existing in a bare bones environment.
Click to expand...
Click to collapse
The phone is just about a year and half old. The drop in battery performance is just too drastic, sometimes it doesn't even last an hour after the charge. Will try to go back to original ROM and see if it improves else will probably have to go for a new battery pack.
ravi-atrix2 said:
The phone is just about a year and half old. The drop in battery performance is just too drastic, sometimes it doesn't even last an hour after the charge. Will try to go back to original ROM and see if it improves else will probably have to go for a new battery pack.
Click to expand...
Click to collapse
Look like a battery problem to me its not the ROM but anyways turn off location services and wifi they are a big battery drainer
Use 2G when u dont need high speed.......
Try this app called Greenify https://play.google.com/store/apps/details?id=com.oasisfeng.greenify
(it helps to reduce wakelocks and improves your battery life)
:laugh: Let me know if it helped (btw chck your battery and see if its defected they are amny ways to chck it read up the forums )
i have the same problem whit any rom of 4.2. when the custom rom shows 5% i change to stock ics rom an that show me 45%
aspc2 said:
i have the same problem whit any rom of 4.2. when the custom rom shows 5% i change to stock ics rom an that show me 45%
Click to expand...
Click to collapse
Think mine is clearly a battery issue. Replaced the battery with a new one yesterday and now the phone lasts 6 hrs at least on a single charge.
CM 10.1.3
I couldn't write to developer's forum so I'm asking here.
I've recently firmwared my AT&T A2 CM 10.1.3 and battery drains really fast! The previous build was CM 10.1 (25th of June). I wiped cache and dalvik cache and firmwared CM 10.1.3. At least 3 people report that thie batteries on this ROM drain slow.
What did I do wrong???
danger86 said:
I couldn't write to developer's forum so I'm asking here.
I've recently firmwared my AT&T A2 CM 10.1.3 and battery drains really fast! The previous build was CM 10.1 (25th of June). I wiped cache and dalvik cache and firmwared CM 10.1.3. At least 3 people report that thie batteries on this ROM drain slow.
What did I do wrong???
Click to expand...
Click to collapse
Battery life varies so much from user to user that it is impossible to answer your question without A LOT more information.
Go here:
http://forum.xda-developers.com/showthread.php?t=1179809
Download the app and follow the directions in the op. That and reading through that thread itself should tell you everything you need to know about what is using up your battery.
That being said, everyone has different habits and expectations when it comes to their battery. What one person says is good battery life, another will likely say is bad. So just keep in mind that there is not a right or wrong, just what is right or wrong for you.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
Thank you fro your answer. When I used previous version of CM the battery lasted 3 days with minimal using and turning the flight mode at night on.
As long as I installed newer version with JBX kernel the battery lasts 20 hrs max.
Power Tutor says that the most hungry apps are Android System and Kernel
Hi,
My phone is almost not charging full or it doesn't show as such.
This is detailed breakup of my issue :
I put phone at charging exactly at 2pm at 2%
3pm it was at 36%
4pm it was 54%
5pm it was at 64%
6pm it was at 73%
7pm it was at 82%
7:30pm it was at 84%
after this I removed phone from charging and rebooted it. Surprisingly it showed 100%.
Battery doesn't last more than 12hrs no matter what I do. I am using Greenify too.
BT, GPS, Auto-Sync, 3G, etc all are off. WiFi On 24hrs.
Screen-off battery drain is also around 8-9% per hour.
Can I do/try something on software side before I order a new battery ?
Right now I am on Carbon ROM (20131008) with stock kernel, 1512, Ondemand, SIO, No OC. Its same on every ROM I tried except seemingly on ARHD 7.3 (used it less than 24hrs. Its rock solid and smooth.)
I would greatly appreciate any help/advice !
I also has this issue still looking for the solution
Sent from my HTC Sensation using XDA Premium 4 mobile app
the battery misreading while charging is a common htc's fault after rooting and there is no solution yet
i have the same thing while charging my device
but the difference is i don't have that fast drain
how old is your battery?
did you try a different battery?
make sure it fits correctly to the pins
Battery is just 1yr old. Yup I checked the pins. They are correctly fit.
silentvisitor said:
Battery is just 1yr old. Yup I checked the pins. They are correctly fit.
Click to expand...
Click to collapse
this is a rom issue i think as this has also happened to many people and and this happens after many days on a single rom (and u make the rom unstable)
the solution is simple just backup ur data and full wipe and flash rom again and u will be good to do for next many days (if u keep the rom stable)
I flash ROM almost every alternative day and I always do Full-Wipe
silentvisitor said:
I flash ROM almost every alternative day and I always do Full-Wipe
Click to expand...
Click to collapse
then its a battery or charger fault
Harbir said:
then its a battery or charger fault
Click to expand...
Click to collapse
How to decide which one
Are there any Battery benchmarking app that could tell me if I need a new one ?
silentvisitor said:
How to decide which one
Are there any Battery benchmarking app that could tell me if I need a new one ?
Click to expand...
Click to collapse
first try to change the charger and try it with same present battery ,then after a while if the result is same then u have no choice to replace battery and yes there r many battery apps in play store u have to find then
Harbir said:
first try to change the charger and try it with same present battery ,then after a while if the result is same then u have no choice to replace battery and yes there r many battery apps in play store u have to find then
Click to expand...
Click to collapse
Thanks and no I meant Benchmarking app Never saw any
Battery Kernel issue
I am new to xda. I actually flashed a new rom after that phone doesn't charge after switching off. Could it be a kernel issue or the rom's issue. I have a Canvas HD. And sorry if this is not the place to ask the question. I couldn't find any other thread related to this. Please help.
Similar issue here. My charging often stops at about 80%, but after a reboot the battery's full charged.
My battery also gets drained very fast, but it's about 2,5 years old so that's probably the problem.
With the CPU clock speed @1,5GHz and the GPU @266MHz i get about 15h +/-2h of battery life.
I keep battery saving ON most of the time. Bluetooth, GPS, 3G etc all OFF. WiFi ON for about 1-2h per day (if i would keep it on longer, my phone would be dead in 4-5h).
I'm using ViperS 5.2.1 right now (full wiped before install). I got the same experience on ARHD and previous ViperS versions.
Tested the charger - it's fine.
I was wondering if anybody else got an old battery like mine and how long does it last on full charge
Hi guys,
I have a HTC Sensation XE that i bought three days ago (second hand) and i have the same problem with the battery % not reading correctly.
Now this is what i observed:
- the charging is very slow - from 20% to 40% in 2-3 hours
- after 2-3 hours of charging if i reboot the phone the charging LED turns green and the battery reading says 100%.
(i tested to see if actually it got charged to 100% and it did, i turned everything on, watched a HD movie, played some games and after 5-6 hours of playing with it i still had 50%)
- tested the battery to see how fast it drains from 10% to shut down and it went on at full brightness and everything on for about an hour and something so this means there might not be any problems with the battery
- so the reading is wrong because the battery is charged after a few hours.
- i did a test to see if the same thing happens when the phone is off and i left it to charge for 2-3 hours and when i got back the charging LED was still orange. When i started the phone the LED went off and back on as green. The battery was 100% charged.
- If the same behavior happens in off mode it means it's not a ROM problem (by the way from what i know the phone is stock, the guy never did the rooting.....that's what he told me - can't know for sure).
- from my electronics background it seems the phone updates the battery information sometime at boottime. When charging, the software keeps the charging LED on because it's supposed to charge due to incorrect data but the hardware charging controller drops the charge current because the the battery is full. So this can be an incorrect sensor reading by the software or an incorrect feedback given by the hardware controller.
So what do you think, what can cause this.
Should i try rooting the device?
And i tried factory reset from android and factory reset from bootloader and the problem is still there.
Ok so i did the following:
- unlock the bootloader
- flashed CWM
- installed superuser
- wipe battery stats
- wipe device
- calibrate battery with an application from market
The problem is still there.
I figured that when in bootloader first thing you can read is the S-ON/S-OFF. Before doing the unlock it was "LOCKED" and after "UNLOCKED".
I did a relock and the status changed to "RELOCKED" so this means the guy that had the phone before me didn't root which again means the theory that says this problem occurs when the user tries to root the device is not true because it seems the behavior is observed on an unrooted device.
I will dig deeper maybe i find more ideas on what i can do.
I'm running out of software options so this is pointing at something hardware.
I'll get back with updates when i find something else.
rickarrp said:
Ok so i did the following:
- unlock the bootloader
- flashed CWM
- installed superuser
- wipe battery stats
- wipe device
- calibrate battery with an application from market
The problem is still there.
I figured that when in bootloader first thing you can read is the S-ON/S-OFF. Before doing the unlock it was "LOCKED" and after "UNLOCKED".
I did a relock and the status changed to "RELOCKED" so this means the guy that had the phone before me didn't root which again means the theory that says this problem occurs when the user tries to root the device is not true because it seems the behavior is observed on an unrooted device.
I will dig deeper maybe i find more ideas on what i can do.
I'm running out of software options so this is pointing at something hardware.
I'll get back with updates when i find something else.
Click to expand...
Click to collapse
probably it is htc's bug
the same happened to me after rooting the device
For now I will try to make some full cycles of the battery and see if anything changes. I usually use the phone at work and by the time I get home it's almost empty. Plug to charger and till morning it's full with a green light. I will have to monitor the charging times and get back with results.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Free mobile app
Well i did some full charging cycles and nothing changed, still the same long charge time(read by the phone) and with restart it bounces to 100%.
I had the original Android 4.0.3 with Htc Sense 3.6 at the time. Got 4EXT recovery and an 4.0.4 rom with Htc Sense 4.1. Did a full wipe and battery stats , installed the new 4.0.4 rom but the problem persists.
At this point i think the battery is the problem so the next thing to do is to change it. I will get back after i change it, hopefully sometime in november.
After a long time I managed to change the battery and after a few tests it seems the problem is still there. The time on battery improved as I expected but everything else is the same which means it's something hardware defective in the phone. Also did some tests with android 5.1 and the same results. Meantime I sold the phone and got a Samsung Galaxy S3 Neo. Hope this research gives some answers to someone at some point. Cheers.
Hello enthusiasts,
I'm having a problem with my HTC One Mini (from German Telekom).
The device keeps turning off at around 45% battery charge. There is no warning prior to the shutdown. You can briefly see the "Battery is low!" warning for a tenth of a second until the phone shuts down completely. It can then not be turned on again unless I plug it into the charger. When turned on immediately afterwards, while charging, the battery status has changed to 0%.
There is a screenshot attached which shows the Voltage of the battery about 2 minutes before the device shut down.
I have already used the search and found numerous threads about devices shutting down with a high battery load, but the linked tutorials are often obsolete or unappliable.
I've been studying Wikipedia articles about Lithium-Ion batteries which say that the lowest voltage for a battery generally is 2.5V. Many manufacturers implemented security measurements that keep the battery far away from this low voltage level. I expect the 0%-load to be around 3V, but 3.3V should still be rather "loaded".
Concerning the overall device duration after a full charge: It has become far worse. After first flashing Cyanogenmod M11 Snapshot M6 a fully charged battery would give me around 20h of time until it would die. I've always recharged the device when it reached about 20% charge, before it turned red. Now it barely manages to get to 12-14h. And I don't even use it heavily.
I've already tried some battery calibration apps, but they all haven't shown any influence on the symptoms.
Information about the system:
HTC One Mini
Cyanogenmod 11, Snapshot M11 released on 2014-10-08 02:18:05
Battery Apps: Battery Doctor, Greenify (no difference with or without these apps)
I'd be glad to provide more information on this matter if I forgot something, but I hope I got everything you need. Would greatly appreciate help as this problem is slowly grinding my gears.
Doctor Luk said:
Hello enthusiasts,
I'm having a problem with my HTC One Mini (from German Telekom).
The device keeps turning off at around 45% battery charge. There is no warning prior to the shutdown. You can briefly see the "Battery is low!" warning for a tenth of a second until the phone shuts down completely. It can then not be turned on again unless I plug it into the charger. When turned on immediately afterwards, while charging, the battery status has changed to 0%.
There is a screenshot attached which shows the Voltage of the battery about 2 minutes before the device shut down.
I have already used the search and found numerous threads about devices shutting down with a high battery load, but the linked tutorials are often obsolete or unappliable.
I've been studying Wikipedia articles about Lithium-Ion batteries which say that the lowest voltage for a battery generally is 2.5V. Many manufacturers implemented security measurements that keep the battery far away from this low voltage level. I expect the 0%-load to be around 3V, but 3.3V should still be rather "loaded".
Concerning the overall device duration after a full charge: It has become far worse. After first flashing Cyanogenmod M11 Snapshot M6 a fully charged battery would give me around 20h of time until it would die. I've always recharged the device when it reached about 20% charge, before it turned red. Now it barely manages to get to 12-14h. And I don't even use it heavily.
I've already tried some battery calibration apps, but they all haven't shown any influence on the symptoms.
Information about the system:
HTC One Mini
Cyanogenmod 11, Snapshot M11 released on 2014-10-08 02:18:05
Battery Apps: Battery Doctor, Greenify (no difference with or without these apps)
I'd be glad to provide more information on this matter if I forgot something, but I hope I got everything you need. Would greatly appreciate help as this problem is slowly grinding my gears.
Click to expand...
Click to collapse
Have you tried using a different ROM?
Everest_ said:
Have you tried using a different ROM?
Click to expand...
Click to collapse
I've had the stock ROM installed for about 7 months until July and then I've only installed different versions of Cyanogenmod.
Namely Snapshot M7, a Nightly one from July, back to Snapshot M7 (at this point, the problem with the battery started occuring), then a nightly from October 6th and just recently the Snapshot M11. It should be noted that I've always wiped the system partition before installing a new build.
Doctor Luk said:
I've had the stock ROM installed for about 7 months until July and then I've only installed different versions of Cyanogenmod.
Namely Snapshot M7, a Nightly one from July, back to Snapshot M7 (at this point, the problem with the battery started occuring), then a nightly from October 6th and just recently the Snapshot M11. It should be noted that I've always wiped the system partition before installing a new build.
Click to expand...
Click to collapse
Flash a stock ROM and see if it still happens.
I have this problem also on any roms. But my isn't at 45%. It's usually at around 14% or 30 something. After it reboots my battery will be 0%
I've had the stock rom running for some time now and the battery display is absolutely fine with it. As soon as I go back to my CM M11 backup and recharge the phone, the measurement gets all confused and the phone starts shutting down at ~45%-50% again.
Doctor Luk said:
Hello enthusiasts,
I'm having a problem with my HTC One Mini (from German Telekom).
The device keeps turning off at around 45% battery charge. There is no warning prior to the shutdown. You can briefly see the "Battery is low!" warning for a tenth of a second until the phone shuts down completely. It can then not be turned on again unless I plug it into the charger. When turned on immediately afterwards, while charging, the battery status has changed to 0%.
There is a screenshot attached which shows the Voltage of the battery about 2 minutes before the device shut down.
I have already used the search and found numerous threads about devices shutting down with a high battery load, but the linked tutorials are often obsolete or unappliable.
I've been studying Wikipedia articles about Lithium-Ion batteries which say that the lowest voltage for a battery generally is 2.5V. Many manufacturers implemented security measurements that keep the battery far away from this low voltage level. I expect the 0%-load to be around 3V, but 3.3V should still be rather "loaded".
Concerning the overall device duration after a full charge: It has become far worse. After first flashing Cyanogenmod M11 Snapshot M6 a fully charged battery would give me around 20h of time until it would die. I've always recharged the device when it reached about 20% charge, before it turned red. Now it barely manages to get to 12-14h. And I don't even use it heavily.
I've already tried some battery calibration apps, but they all haven't shown any influence on the symptoms.
Information about the system:
HTC One Mini
Cyanogenmod 11, Snapshot M11 released on 2014-10-08 02:18:05
Battery Apps: Battery Doctor, Greenify (no difference with or without these apps)
I'd be glad to provide more information on this matter if I forgot something, but I hope I got everything you need. Would greatly appreciate help as this problem is slowly grinding my gears.
Click to expand...
Click to collapse
I have the same problem. As soon as my phone gets to about 40%, the battery drains to 0% within minutes, even while the screen is off and no data is being used. My phone is just over a year old and running a rooted, but stock version of 4.4.2. I don't think it's ROM related since it only started doing this recently. My guess is that our phone batteries are malfunctioning. Check out this person who has the exact same problem I have on the One M8:
http://forums.androidcentral.com/htc-one-m8/396770-htc-one-m8-battery-drain-40-60-0-seconds.html
His screen shots mirror mine EXACTLY. One thing I discovered is that while charging from 0% while in recovery, I was able to see my battery percentage jump from 7% to 50% when I booted to the OS. The battery then died again minutes later. This only happened once, but I'm guessing that our phone might be displaying a higher percentage than what is true just before it dies.
I have a strong feeling this might be CyanogenMod related, as it is known to have caused great problems on dozens M4's with overheating / strange battery drain / weird stuff like that, among many other bugs.
If I were you, I would do a fully clean install of a stable Sense-based ROM and kernel on upgraded firmware and see if problem persists.
Upgrade to the latest TWRP recovery
Wipe everything
Factory/Data reset
Advanced wipe: Cache / Dalvik Cache / System / Data / Internal Storage
Format Data
Upgrade your firmware, if not done yet
Install latest InsertCoin, choose "Perform a full wipe" option in AROMA
When installer finished, uncheck "Reboot phone now" and get back to recovery
Wipe [Cache] + [Dalvik Cache]
Install latest Xceed kernel (for Android 4.4.3)
Wipe [Cache] + [Dalvik Cache]
Reboot
I wish it was that simple. Thought CM may have some known issues, my device and the other example I linked to are running stock Roms.
If it wasn't happening every single day, it wouldn't be such a big deal, but now I'm seriously worried that I can't get a full days use from it anymore and it's barely over a year old. Sending it back to HTC would be a huge pain since I'm rooted. Though I guess it would be worth it in the long run to finally have a phone that doesn't shut down at 40%
Sent from my HTC One mini using XDA Free mobile app
Hello everyone, sorry for the delay.
It looks as if there might be damage to the battery as the %-display for the battery is still wrong on a Stock ROM (rooted and outdated) that I've had on the device for a week now.
Okay guys, what to do next? I guess I would like to completely revert everything and reset the phone to 100% stock. Would you guys recommend opening a new thread for that?
Anyway, here are some details:
Kernel 3.4.10-g8974365 [email protected] #1 SMP PREEMT
CID: T-MOB101
TAMPERED
UNLOCKED
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.24.40e.00.26
OpenDSP-v19.2.0268.0927
OS-3.10.111.4
eMMC-boot 1024MB
Feb 14 2014, 17:48:26.0
I'm running a Stock branded ROM (T-Mobile Germany) with Sense 5.5 and Android 4.4.2 which is OUTDATED, however using the stock Recovery, I can NOT install OTA Updates as it stops at 50% showing the attached image (courtesy of droider.eu).
So the plan is to get the default Kernel (remove root), make the Stock ROM updateable, remove TAMPERED [might require S-OFF if I'm correct] and get everything LOCKED again (and not RE-LOCKED). I need your help to achieve all of this and it would be awesome if you could help me or just tell me to open a new thread.
Doctor Luk said:
Hello everyone, sorry for the delay.
It looks as if there might be damage to the battery as the %-display for the battery is still wrong on a Stock ROM (rooted and outdated) that I've had on the device for a week now.
Click to expand...
Click to collapse
I am in the same boat with you. I have completely given up on this battery. It's not ROM related. The battery simply doesn't hold a full charge anymore and the only remedy is to send it back to HTC for replacement. Since my phone has no insurance or warranty, I'd have to pay for it completely out of pocket. Fortunately, I've got my old HTC One S that still works perfectly and just loaded the latest KitKat Rom to it. The battery life and over-all performance of the One S is nearly better than my One Mini. I'm not feeling very compelled to get it fixed at the moment, but I'll let you guys know how much it costs if I change my mind. Good luck with yours.
Thanks, I'll just have to get mine fully back to stock to be able to turn it in... Hope it'll not be that pricy for you.
Can you get rid of the tampered warning on the boot screen? I thought it was irreversible. If not, I don't think HTC will warranty it.
Sent from my HTC One S using XDA Free mobile app
Of course you can, at least I assume you can. On the HTC One there are already guides and I guess the Mini is not that much different. It requires S-OFF though, so at least I would have to tinker around with my phone even more.
Our Plain vanilla -stockROM One mini is having similar issues:
It shuts down at battery 30%
- removed unneccessary app's - no result
- Factory reset - No result
Contacted HTC support, they advised to run self-test ( *#*#3424#*#*) in safe mode
Tried that: Boot-up in safe mode - charge full - batterytest : Put it away for the night while batterytest running, hoping for a report in the morning. Unfortunately no report, but a battery status of 1% - so no shutdown at 30%
Second time: Charged full in regular mode (100%) - reboot in safe-mode: Battery shows up @57% and could be charged for at least one hour.
Ran battery-test : after one hour of testing, battery = 91 % while 71 % is lower limit for failing battery, so battery succeeded.
Third time: Just testing the difference between battery-status in regular mode vs. safe-mode
Full charge in regular = 50% in safe mode (and able to continue charging)
Don't want to sent it away for repair: expecting to have it sent back after a couple of weeks: " we did the batterytest, and it's functioning fine. Your device is not broken"
My idea: something interfering with the battery-status indicator ?
But what ?
Any ideas ?
jamf said:
Our Plain vanilla -stockROM One mini is having similar issues:
It shuts down at battery 30%
- removed unneccessary app's - no result
- Factory reset - No result
Any ideas ?
Click to expand...
Click to collapse
not sure it works, but try this
the wiping the partition cache from stock recovery is not quite the same as factory reset
jamf said:
Tried that: Boot-up in safe mode - charge full - batterytest : Put it away for the night while batterytest running, hoping for a report in the morning. Unfortunately no report, but a battery status of 1% - so no shutdown at 30%
Click to expand...
Click to collapse
Thanks for reporting a similar problem to mine. I haven't gotten to fix mine, yet, too. Mine even powers down at 75% Battery and now has a horrible battery life of about 2h of normal usage (occasional screen activity, listening to music).
But how did you find a batterytest? I can't seem to find one in the safe-mode via that dial code. Can you explain where you found the battery test?
jamf said:
Our Plain vanilla -stockROM One mini is having similar issues:
It shuts down at battery 30%
- removed unneccessary app's - no result
- Factory reset - No result
Contacted HTC support, they advised to run self-test ( *#*#3424#*#*) in safe mode
Tried that: Boot-up in safe mode - charge full - batterytest : Put it away for the night while batterytest running, hoping for a report in the morning. Unfortunately no report, but a battery status of 1% - so no shutdown at 30%
Second time: Charged full in regular mode (100%) - reboot in safe-mode: Battery shows up @57% and could be charged for at least one hour.
Ran battery-test : after one hour of testing, battery = 91 % while 71 % is lower limit for failing battery, so battery succeeded.
Third time: Just testing the difference between battery-status in regular mode vs. safe-mode
Full charge in regular = 50% in safe mode (and able to continue charging)
Don't want to sent it away for repair: expecting to have it sent back after a couple of weeks: " we did the batterytest, and it's functioning fine. Your device is not broken"
My idea: something interfering with the battery-status indicator ?
But what ?
Any ideas ?
Click to expand...
Click to collapse
Wow - I wish you had posted this 2 days earlier! I just had a new battery purchased for my phone and I'm getting a local repair shop to replace it. Sounds like my battery could be fine and I will likely have the same results after it's replaced!
If you fully charge the phone in safe mode, does the phone battery still last the appropriate amount of time in regular mode or does it still shut off prematurely?
Doctor Luk said:
Thanks for reporting a similar problem to mine. I haven't gotten to fix mine, yet, too. Mine even powers down at 75% Battery and now has a horrible battery life of about 2h of normal usage (occasional screen activity, listening to music).
But how did you find a batterytest? I can't seem to find one in the safe-mode via that dial code. Can you explain where you found the battery test?
Click to expand...
Click to collapse
Dial *#*#3424#*#* and click <more> in the right lower corner
iourikil said:
not sure it works, but try this
the wiping the partition cache from stock recovery is not quite the same as factory reset
Click to expand...
Click to collapse
Not sure if I understand this: I did the Power-button - volume down - 'Factory reset withour keeping data" - as given on the HTC website
PuffDaddy_d said:
Wow - I wish you had posted this 2 days earlier! I just had a new battery purchased for my phone and I'm getting a local repair shop to replace it. Sounds like my battery could be fine and I will likely have the same results after it's replaced!
If you fully charge the phone in safe mode, does the phone battery still last the appropriate amount of time in regular mode or does it still shut off prematurely?
Click to expand...
Click to collapse
It still does: Fully charged in safe-mode it shuts down @30% - does seem to last longer to reach 30% level
Last night I tried a different trick:
After shutdown @30% I kept the phone off and recharged it to 29 %
I put the phone back on and drained the battery to 0% - ignoring all warnings ("please charge .... CHARGE ..... G*DDAMN START CHARGING, I'M FREAKING DYING HERE ....)
Recharged the battery while powered off from 0% to 100%
Tested this morning: Same battery level in regular mode as in safe mode (98%)
Hmmm, I seem to remember doing some thing similar by accident with my phone when I stopped charging around 30% to use it. It drained to 0 shortly after and I fully recharged while in recovery mode. The battery seemed to last longer that time, but any subsequent charging before letting the battery die seemed to result in the same poor battery life. It's not a real solution but if you can confirm that yours acts similarly, then it's more info for us to have as we try to figure this out.
Sent from my HTC One S using XDA Free mobile app
Hi all, I have 2 Motorola Photon Q (xt897).
Both phones have unlocked bootloader, TWPR installed and SIM MOD to work with italian carrier.
The first one working very well but one month ago the grapich module die. Exactly I don't know why (broken chip on motherboard?) but now it's impossibile to power up.
Rom: Carbon Rom 4.4.4 Kitkat
Initial boot image: tinyurl.com/j6rcao3
Kernel: i don't know
The second one (replacement for the first one) arriving this monday.
Seem working well but have a very bad problem: overheating and impressive battery drain: tinyurl.com/hg8c9y6
In only 5 hours the battery die (also in stand-by!). Seem that cpu working at full frequency all the time without stopping.
I found threads that suggest to change the Rom (this is an issue of CM 12.1)... for this reason I try to reflash CM12.1 and also CM 12... and finally Carbon Rom like the first one. But the problem persist.
The boot image is different from the previous one: oi42.tinypic.com/2jbuwqq.jpg and for this reason, I think there is a different kernel installed (3.0.101-g93ecbd4 [email protected] #1 mon nov 3 10:40:02 CET 2014).
Now, the kernel is the only difference from the first and the second phone.
My question is: the overheating and battery drain can be the consequence of a bad kernel?
In other words... change the Kernel can solve the problem?
Maybe do you know what kernel is in the first phone?
Do you have any kernel to suggest?
Thank you,
Lucio
Seems something is keeping the phone awake. Check your wakelocks at the very least in the battery section, or using an app.
*UPDATE*
I've try some test and I found that the overheating and battery drain continue also with the phone switched off!!!
I assumed that isn't ROMs guilt.
I think the cause can be:
- problem with the kernel taht don't shut down completely the phone and the battery drain continue (unlikely)
- short circuit in the phone motherboard (maybe wrong SIM mod?)
Now I try to open it and find where is localized the overheating (battery, cpu, chip...)
I will give you update soon!
Lucio
LucioT said:
*UPDATE*
I've try some test and I found that the overheating and battery drain continue also with the phone switched off!!!
I assumed that isn't ROMs guilt.
I think the cause can be:
- problem with the kernel taht don't shut down completely the phone and the battery drain continue (unlikely)
- short circuit in the phone motherboard (maybe wrong SIM mod?)
Now I try to open it and find where is localized the overheating (battery, cpu, chip...)
I will give you update soon!
Lucio
Click to expand...
Click to collapse
Overheating and battery drain with the phone switched off...?
Are you sure it's actually off? That doesn't make any sense whatsoever.
*2nd UPDATE*
I've performed some other test and the possible fault can be:
- USB connector: short circuit (but I didn't find overheating here)
- battery fault: it's both old battery... the first one have 3 years, the second one 3,5 years
Most probably the problem is the battery... if it's the USB connector I think I must have some other problem (eg: data syncornizing with PC... I do it without problems).
Also the battery full charging is very fast (about 2 hours) and sometimes, when I reach the 15%/20% of residual charge, the battery fall almost istantly to 0% (and the phone switched off).
Now I've buy a new battery from eBay... when I will try it I will can update you with other news...
Definitely, the problem is hardware.
Maybe some shortcut in the main board in some chip (charging chip?).
Main board changed, problem solved.
Thank you for the support!
LucioT said:
*2nd UPDATE*
I've performed some other test and the possible fault can be:
- USB connector: short circuit (but I didn't find overheating here)
- battery fault: it's both old battery... the first one have 3 years, the second one 3,5 years
Most probably the problem is the battery... if it's the USB connector I think I must have some other problem (eg: data syncornizing with PC... I do it without problems).
Also the battery full charging is very fast (about 2 hours) and sometimes, when I reach the 15%/20% of residual charge, the battery fall almost istantly to 0% (and the phone switched off).
Now I've buy a new battery from eBay... when I will try it I will can update you with other news...
Click to expand...
Click to collapse
why not move your battery from the 1st photo q to the new one and try?
I have try with the battery of the first phone but the problems remain the same... I buy also a new battery to try a final test and again nothing changed... hardware problem.
Now with the new main board all works well.
I share with you this information in hope to help other people.
Thanks for the support guys!