I charge my DHD every night over night, to make sure it has a full charge at the start of everyday. I've had my DHD for 16 months and I have had no problems with it ever. I've run many ROMS and kernels and its been rooted since the first week I got it. However it now overheats when I put it on charge almost every night.
I plug it in and the temperature will steadily rise from about 29 - 32C (which is what it runs at throughout the day) to over 40C, I've never seen what it actually reaches because since its over night I haven't monitored it that much. The highest I've seen it is 47C. After the first few occurrences of this I set a profile in setcpu to set the phone to 800Mhz when temperatures go over 38C. However this was to no avail. I then set it to underclock all the way down to 230Mhz when it goes over just 35C. But yet it still overheats when on charge so I don't think it has anything to do with my CPU? I changed kernels too but it still didn't help. The only reason this really annoys me is when it does over heat (lets say 1 in every 3 nights) I wake up and its just boot looping over and over until I do a battery pull. Which means my alarm hasn't been going off so I've had to dig out the old G1 the past two weeks just for it to act as an emergency alarm in case the DHD overheats.
I'm not sure what my problem is here, any insight?
Might want to try replacing the battery. Is it a third party bettery, those cheap "Gold 2000ma" batteries are notorious for overheating and being a bit rubbish. The other thing that might have happened is there is a short in the charging circuit which is causing the overheating.
I would say it's a 80% chance of it being a hardware problem. Try a different ROM if you are unsure.
If you have an o/c tool like no frills cpu control or anything like that, then that could be your issue too. Running high on cpu can cause overheat even when the phone is in sleep mode.
Sent from my HTC Desire HD using XDA App
Thanks for the replies.
I have my cpu overclocked during the day but I have a profile in setcpu which underclocks it to 230Mhz when the phone goes over 35C. I've seen this in affect and the cpu does downclock as expected yet my phone is still overheating.
I am using the stock HTC battery still and have had no issues with it before. I will try another ROM/kernel combo and see if it that resolves my issue just in case. Otherwise I might have to S-ON my phone again, put it back to stock and send it to HTC...
didge3 said:
Thanks for the replies.
I have my cpu overclocked during the day but I have a profile in setcpu which underclocks it to 230Mhz when the phone goes over 35C. I've seen this in affect and the cpu does downclock as expected yet my phone is still overheating.
I am using the stock HTC battery still and have had no issues with it before. I will try another ROM/kernel combo and see if it that resolves my issue just in case. Otherwise I might have to S-ON my phone again, put it back to stock and send it to HTC...
Click to expand...
Click to collapse
I had this same problem it was the setcpu app or no frills create another profile and put the setting on charging and turn setting down or add profile when screens off 122-245 set priorities to high hope this helps
If it's not a software issue, your battery might be faulty and you should switch it as soon as you can.
starkilling said:
If it's not a software issue, your battery might be faulty and you should switch it as soon as you can.
Click to expand...
Click to collapse
My Desire HD is fitted withe the original battery and its also getting hot during charging.
I've been monitoring my battery with 'Battery Monitor Widget' from the market, the recordings show that throughout the day my battery fluctuates between 20 - 30C depending on my usage. As soon as I plug it in however the battery immediately starts creeping up from low 30's to around 47C, this is where the monitoring stopped and has a huge gap until morning when I boot my phone again.
I applied a new profile in setcpu as suggested for charging instead of temperature and tested again last night, I set the charging profile to 230/384 min/max. The monitoring from last night shows the phone reached 40C by the time it'd charged to 100% and steadily started to cool back towards 30C, my phone was on when I woke up and functional so hopefully this is a temporary fix until I eventually have to get a new battery because I'm pretty certain its a hardware fault.
How long is the standard warranty for a Desire HD? If its 1 year then I'm out of luck and will have to buy a replacement...
didge3 said:
I've been monitoring my battery with 'Battery Monitor Widget' from the market, the recordings show that throughout the day my battery fluctuates between 20 - 30C depending on my usage. As soon as I plug it in however the battery immediately starts creeping up from low 30's to around 47C, this is where the monitoring stopped and has a huge gap until morning when I boot my phone again.
I applied a new profile in setcpu as suggested for charging instead of temperature and tested again last night, I set the charging profile to 230/384 min/max. The monitoring from last night shows the phone reached 40C by the time it'd charged to 100% and steadily started to cool back towards 30C, my phone was on when I woke up and functional so hopefully this is a temporary fix until I eventually have to get a new battery because I'm pretty certain its a hardware fault.
How long is the standard warranty for a Desire HD? If its 1 year then I'm out of luck and will have to buy a replacement...
Click to expand...
Click to collapse
Did you ever try uninstalling the setcpu app or any cpu controller and try that.. another thing what Rom are you using . Did you try wiping the battery stats in recovery
hopesfall190 said:
Did you ever try uninstalling the setcpu app or any cpu controller and try that.. another thing what Rom are you using . Did you try wiping the battery stats in recovery
Click to expand...
Click to collapse
Worth a try, Im using Virtuous Quattro RC3 at the moment. Although the ROM development seems to have died so I might try the other stock ICS ROM I see floating around for the DHD.
I've been told to dump setcpu about 948 times before due to performance issues it supposedly brings or other faults and I just cant tear myself away from it, I've had the widget on my home screen in the same place set up the same way for about 3 years across 2 different phones and about 20 different ROM's, I just cant seem to force myself to get rid of it.
Wiping my battery stats seems like a good idea and I'll make sure to do that tomorrow morning when my phone will be fully charged. I'll also change my ROM later this week and if I'm still getting issues I will TRY to ditch setcpu for a while. If I still have issues then I will have narrowed it down to some sort of hardware fault.
Related
So I was wondering what temps you guys are seeing when your phone overheats.
My phone reboots when it hits 37 C, which seems awful low. Anyone else seeing such low reboot temps?
gmichaelow said:
So I was wondering what temps you guys are seeing when your phone overheats.
My phone reboots when it hits 37 C, which seems awful low. Anyone else seeing such low reboot temps?
Click to expand...
Click to collapse
Mine doesn't reboot that low, the highest I have seen it go was like 43.7 or something
I've never had my phone reboot due to overheating even at 42°C. Running CM6.01
Sent from my Incredible using XDA App
Hmm, this is getting frustrating. I've begun to reboot at around 37 C. Is there any way to change that number? Anything to reset?
Is that CPU or battery temperature? If battery then the CPU would be much hotter.
Sent from my Droid using XDA App
Battery... but it's weird. The battery temperature gets to 37 C, and then reboot. When I very distinctly remember it before going 45+ C without a problem.
And now I'm bootlooping. Seems to start up, and is still too hot, then reboots again. Anyone have this happen to them? Lower temp reboots?
Sounds like you may have permanently damaged your device, if your battery temp were 40+ degree celsius your CPU temp would be a sustained 15+ degrees hotter. Running your device this hot often certainly could damage it over time.
Sent from my Droid using XDA App
Try a standard or increasing voltage kernel if possible.
Sent from my Droid using XDA App
fivefour said:
Sounds like you may have permanently damaged your device, if your battery temp were 40+ degree celsius your CPU temp would be a sustained 15+ degrees hotter. Running your device this hot often certainly could damage it over time.
Sent from my Droid using XDA App
Click to expand...
Click to collapse
No no, my battery isn't that hot for long amounts of time, just, like when I'm surfing for a long time or something. Trying an undervolted kernel now.
Do you have a backup battery that you can try - see if you get the same results? Batteries do occassionally stop working properly.
My phone would reboot when using GPS in the car if it was on the dashboard or mounted - I checked the temperature when it booted and didn't get stuck in a boot loop and it was around 45c.....
I returned the phone to stock and brought it back to vzw, they gave me a new battery, phone still runs somewhat hot even stock.
jp43 said:
My phone would reboot when using GPS in the car if it was on the dashboard or mounted - I checked the temperature when it booted and didn't get stuck in a boot loop and it was around 45c.....
I returned the phone to stock and brought it back to vzw, they gave me a new battery, phone still runs somewhat hot even stock.
Click to expand...
Click to collapse
But mine is rebooting at 37-38 C. Which is awfully low. I'm RUU'd, S-oned, and factory-resetted and STILL it happens. So it's a hardware problem.
Gonna take it into a Verizon store and demand a replacement on the spot x]
I can advisr from personal experience on your symptoms that you have one choice ... Return to verizon for a refurb. This is what happens when you have an early incredible with a faulty hardware radio. It gets to the point where it starts trying to compensate and super heats. You must return.
Every other suggestion would be a mask to an existing well known hardware problem.
I once left my phone in a black bag on a hot summer day. It went up to 50 C with no problems. It didn't reboot or anything.
I have one of the original Incredible's from launch day, it is usually around 43-45. Sometimes it gets warmer than that playing games. Never actually had any problems. The hottest it ever gets is on Z rom's. Those things have gotten it to 50 .
I'm on CM7 W/Slayher's 2.6.37 kernel, and it's at 42 just on the home screen. Mind you this is all on stock speeds. My phone doesn't like to overclock. Regardless of kernel. It can go to 1.113 sometimes, but any more = reboot.
On the HTC Incredible site, there is a FAQ which states the maximum recommended operating temp is ~60C.
I'm relatively sure there is no problem with the battery or the CPU doing up to ~90 for awhile because that's a fairly common temp for CPUs and Batteries to withstand. I'm sure that like most batteries , at >~50C it is less efficient, but I doubt the CPU is presented with any problems in that range.
Phones present a unique set of high-temp problems. Cooling sucks in those little enclosed boxes, and manufacturers definitely don't want your hand or ear burned, and are terrified of having a battery burn up in your hand or pocket, so that is probably why 60 is said to be max. I don't like picking up my phone when it's at all hot (~40C or more) but while experimenting with my own kernels and voltages and overclocking, I've had it reboot somewhere around 60C. Was it the temp, or was it overclocked too far? I have no idea, but I lowered both and stopped taking stupid chances with it.
This thing of rebooting at 37C seems nuts, inappropriate, and most likely a defective part, or one of the many services or apps that perhaps does the wrong thing (accesses verbotten memory, bad ptr, etc..)
A bad example for sure, but at work, many of our HP or Dell Racked servers (DL380's etc), are too hot to touch while running. They have enough fans to power a 747, and it just makes it pretty clear that in some cases, processors and other components can run at amazing temps.
--
Hey all,
I'm having serious battery drain on MIK 2.56 and pretty much any ROM that I flash. I'm running Chopsuey9.2.7 along with SetCPU profiles. I underclock the majority of the times.
My SetCPU profiles are:
Set on Boot = 691max/245min conservative
Charging = 1152/245 performance priority 100
Screen off = 245/245 ondemand priority 99
In-call = 1152/245 performance priority 98
Battery <50% = 691/245 conservative priority 97
Temp >43.7 degrees = 614/245 conservative priority 96
My evo doesn't like to be clocked at 128 or even 499. It reaches temps as high as 115-120 degrees during charging and while in my pocket (I'm thinking it may have got damaged when I used to run the SBC kernels in the early stages). Im starting to think that i have a bad battery. My battery will drain from 100% down to 80% within 5 minutes and usually will be dead within 2 1/2 hours after being off of the charger with moderate usage such as calls
text and checking email. I have Autokiller running and have set memory Lowmem settings to extreme thru Darktremor a2sd.
Any ideas/suggestions?
I personally would stop messing with setcpu, its cool to see a phone all Super fast and what not, but isn't completely necessary to govern everything you do [calling, sleeping, etc..] I only find it cool to use when I'm playing a cool ass game like contract killer: zombies for nice smooth graphic, or running a benchmark.. otherwise messsing with setcpu tends to do awkward things like drain battery when not properly adjusted, **Especially when overclocked.
My stock battery lasts all day with my current setup. I have setcpu as well but don't really mess with it. I use Smartass governor with 1075/245 for normal everyday use. If I have too many drinks and have to crash at a friends house without my charger I'll drop the max speed to about 700 and use conservative or just switch the governor to powersave. Then I've got more than enough time till I need to get back to a charger.
i got good life on that ROM using Aggressive Freedom kernel & using set cpu at 245/768 set at boot....no profiles.
So you think the use of profiles is the issue? I'm not completely sure the profile for screen off is working correctly; I ssh'd into my EVO and took a look at /proc/cpuinfo but it will not show the current cpu speed.
I'll give it a shot without profiles and see. As for the govenors, I believe Smartass was removed and replaced with InteractiveX; is InteractiveX as good?
j7jman said:
I personally would stop messing with setcpu, its cool to see a phone all Super fast and what not, but isn't completely necessary to govern everything you do [calling, sleeping, etc..] I only find it cool to use when I'm playing a cool ass game like contract killer: zombies for nice smooth graphic, or running a benchmark.. otherwise messsing with setcpu tends to do awkward things like drain battery when not properly adjusted, **Especially when overclocked.
Click to expand...
Click to collapse
I agree but with the way my profiles are set, I'm underclocking the majority of the time and only overclock when charging or on a phone call.
ive noticed i get wose battery life if i set up profiles. Worth a shot.
Sprint will test the battery for charge free I actually did it today
Sent from my PC36100 using XDA App
Could be your baseband or pri. Or maybe update ur prl through a sense rom.
If your phone has a horrible signal it will drain like crazy.
Sent from my PC36100 using Tapatalk
r.storm85 said:
Could be your baseband or pri. Or maybe update ur prl through a sense rom.
If your phone has a horrible signal it will drain like crazy.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
That's correct. Also check your spare parts app for any wake lock.
Also, if you're using a havs kernel, setcpu will conflict with the kernel. And in general, you'll always get better battery life on AOSP.
try using setcpu sometimes that will help save battery.
Disabled Profiles in SetCPU....no luck
So I disabled profiles in setCPU and am underclocking at 691/245 and battery life is still the same. I have the most recent radios/PRI/PRL as well and still getting rapid battery drain. One weird thing it does is the phone will hit 0% and shutdown; I'll place it on the charger (AC wall charger, not the usb adapter) until the orange LED stops blinking; I'll turn the phone on and once it's fully booted it will read 53%......all of this within 5mins of going dead! WTF!!!
I just wiped battery stats again in recovery and will boot and see what that does for me. I'm really starting to think the battery is partially bad....
Just left Sprint. They tested the battery and it tested bad and was swollen. I got a stock replacement free of charge although he said they normally would have charged me because the 1yr factory warranty expired. He also went on to say that the battery going bad was possibly caused from my phone being rooted which he may be partially correct. The problem began when SBC first came out and I was testing on the beta stage. It nice to have my phone off of the charger and not be down to 60% within 45 mins!
Sent from my PC36100 using XDA App
lostsoul77 said:
So I disabled profiles in setCPU and am underclocking at 691/245 and battery life is still the same. I have the most recent radios/PRI/PRL as well and still getting rapid battery drain. One weird thing it does is the phone will hit 0% and shutdown; I'll place it on the charger (AC wall charger, not the usb adapter) until the orange LED stops blinking; I'll turn the phone on and once it's fully booted it will read 53%......all of this within 5mins of going dead! WTF!!!
I just wiped battery stats again in recovery and will boot and see what that does for me. I'm really starting to think the battery is partially bad....
Click to expand...
Click to collapse
my phone has been doing this exact same thing but i took it to sprint they said my battery was good should i go to another sprint tech and let them test it out?
I'll wake up in the morning to find my phone off and extremely hot. It will also randomly reboot throughout the day and won't stop until I remove the battery. Any ideas on whats going on and what I could possibly do to fix it?
Sounds like either the screen is staying on....or its overclocked waaay to much... A voltage setting.... Or simply just some app or widget running 24/7
Causing the phone to get hot....make sure tethering and wifi are off at night while your sleeping... Kill the GPS if your passed out too...
Sent from my SPH-D710 using XDA App
Wifi may be the culprit for the overheating issue, but throughout the day wifi and 3g are barely on unless I need internet. Kinda frustrating when you're in the middle of something and your phone randomly reboots and doesn't stop rebooting until you pull the battery. lol I was also thinking it could be the rom im on (always used blazer) but no one else is having the issue therefore it's probably not the rom.
A lot of times an out of control process will cause that too. I don't know and I doubt this phone would power down if it got too hot. Rebooting seems like a no go also since that's not going to help cool it down, if anything it would heat it up. If it powered down and stayed off or shut down as soon as it started to boot - now that would make sense.
Get something like Watchdog or OS Monitor - use it to watch your processes. When it starts getting hot for no reason, check them to see if anything is running. You can set Watchdog to alert you if anything stays over xx% of cpu usage for a specific amount of time.
Do you notice any lag before this happens?
I had the problem with the overheating at night and not charging. I tracked it down to set cpu and the over clocking profile. I use my phone at night as a clock with the clock widget and found that the default over overclock profile I was using for the screen on was in effect even tho I had another profile for charging so what I did was set a profile for 100 priority to under clock to 800 starting at 9:00 PM becuase I go to bed at 10 when I have to work the next day and have had no problems since. Also I did hav some problem's with instability and rebootting at 16oo so I clocked mine to 1400 still fast but doesn't heat up the phone or cause reboots.
KCRic said:
A lot of times an out of control process will cause that too. I don't know and I doubt this phone would power down if it got too hot. Rebooting seems like a no go also since that's not going to help cool it down, if anything it would heat it up. If it powered down and stayed off or shut down as soon as it started to boot - now that would make sense.
Get something like Watchdog or OS Monitor - use it to watch your processes. When it starts getting hot for no reason, check them to see if anything is running. You can set Watchdog to alert you if anything stays over xx% of cpu usage for a specific amount of time.
Do you notice any lag before this happens?
Click to expand...
Click to collapse
The phone will lock up right before it reboots over and over. When the phone starts up it'll stay on for a couple minutes and then restart. It will keep doing so until I pull the battery.
I'll download one of those apps and see what I can find.
arsmithsr said:
I had the problem with the overheating at night and not charging. I tracked it down to set cpu and the over clocking profile. I use my phone at night as a clock with the clock widget and found that the default over overclock profile I was using for the screen on was in effect even tho I had another profile for charging so what I did was set a profile for 100 priority to under clock to 800 starting at 9:00 PM becuase I go to bed at 10 when I have to work the next day and have had no problems since. Also I did hav some problem's with instability and rebootting at 16oo so I clocked mine to 1400 still fast but doesn't heat up the phone or cause reboots.
Click to expand...
Click to collapse
I haven't used setcpu on this phone yet, so maybe the rom i'm using is overclocking the phone. This morning when I woke up around 9 it was off and very hot and did not charge, even though it was plugged in. When I turned it on, it was only at 62%. I know it was on and was working around 430 or so when I woke up in the middle of the night. I don't know if it was charging at that time or not though.
adima said:
I haven't used setcpu on this phone yet, so maybe the rom i'm using is overclocking the phone. This morning when I woke up around 9 it was off and very hot and did not charge, even though it was plugged in. When I turned it on, it was only at 62%. I know it was on and was working around 430 or so when I woke up in the middle of the night. I don't know if it was charging at that time or not though.
Click to expand...
Click to collapse
A ROM won't overclock your phone. It may have a built in overclock option but that's user defined. I had this issue also but I noticed that I would have it laying on top of a shirt or under a pillow (very dumb).
I can replicate the issue if I charge the phone and place it under my pillow. The phone will overheat and shut off. If I pop out the battery it's super hot and I have to blow on it to cool it down. I stopped doing that and just set it on the floor and charge it if need be.
I charge my phone in the daytime and leave it off the charger at night. It's safer and you never know if it can catch fire while you're sleeping.
Android300ZX said:
A ROM won't overclock your phone. It may have a built in overclock option but that's user defined. I had this issue also but I noticed that I would have it laying on top of a shirt or under a pillow (very dumb).
I can replicate the issue if I charge the phone and place it under my pillow. The phone will overheat and shut off. If I pop out the battery it's super hot and I have to blow on it to cool it down. I stopped doing that and just set it on the floor and charge it if need be.
I charge my phone in the daytime and leave it off the charger at night. It's safer and you never know if it can catch fire while you're sleeping.
Click to expand...
Click to collapse
At night I set it on my nightstand and there is nothing by it, and it only does it about once a week i'd say. Kinda frustrating when you set an alarm to get up at a certain time and it doesnt go off cuz the phones off. I do have a real alarm clock, but I know how to turn it off in my sleep. Using my phone allows me to have to answer an equation to turn the alarm off. It's no big deal if I don't get up with an alarm during the wk, but it is nice to get up early and get a head start on the day. Now that I think about it, maybe the alarm clock app i'm using is causing the phone to overheat at times...
Drat!
I was hoping someone was able to diagnose and solve this issue. I've had this same problem/behavior for the last month now. And it's only getting worse :\ Also worth noting is that when the battery overheats, it smells like dill+mint (very weird) ... so it may be a bad battery. When I get a sec, I'll run to the sprint store and pick up a new one and test that out for a while.
Take the battery out and try to spin it on a flat surface... does it spin freely? If so its bad
Sent from my SPH-D710 using Tapatalk 2
I have had this problem a couple times before but it stopped for a long while. Then last night when I was charging, it overheated and shut off but this time it won't charge again, won't turn on at all and when it's plugged in there is a very dim blue light that flashes where the notification/charging LED is. I can barely see the light flashing but it is there. When I first plug in the charger I do see the battery with the loading animation and the battery is empty but then the screen goes black after a second or less and the dim blue LED starts flashing.
I let the phone and battery cool down for a long while, took it out and set it out for a while and it still won't charge at all. This really sucks because I have a 3-day weekend and I can only play Guild Wars 2 on the hotspot on my phone that won't turn on
I am using Mijjz Blend The Goodness with Sleshepics the governers 1.2.3 kernel that was flashed through the ROM updater, it's been working fine for the past couple weeks. I am not using any overclocking/undervolting profiles or anything like that besides what was put into the kernel already.
Please help D: I really want to play Guild Wars.... Q,Q
hope this helps,
i also have setcpu install in a stock rom with overclock and underclock enable
here is the profile settings in my setcpu that might help you solve your problem
profile1.screen off => cpu speed is set 500mhz(high) to 200mhz(low) in governor.conservative mode
profile2.in call => cpu speed is set 500mhz to 200mhz in gov.ondemand mode
profile3.battery temperature is greater than 44c(111f) degree => cpu speed is set 500 to 200 conservative
profile4.11pm to 7am(sleep time) => cpu speed is set 500 to 200 conservative
profile5.battery percentages drop less than 50% => cpu speed is set 1000mhz to 200mhz in ondemand mode
whenever those conditions hits when the phone is on, setcpu will lower the speed for me and consequently reduce the heat issues for me
because i run my phone in 1.7ghz ondemand mode all the time. my phone is the white version which have a newer cpu and i know for a fact
that the older black version epic4g-touch can only go as high as 1.5ghz before problems arise such as kernel panic and overheat
good luck
I had this issue. Man, after a month of looking for a solution, i think I found a solution, at least for my issue. My phone would reboot at least 5 times in a row, and get very hot. This is what worked for me; when the phone reboots, take the battery out, wait 5 seconds, hold power button and volume down to get to reboot into recovery, wipe out Dalvik cache, and then fix permission and reboot.... Hope this works for you too.
Sent from my Samsung S2 ET4G using Tapatalk
After using the original Note, I decided I couldn't live with the battery life and decided to upgrade to the Note 2 last christmas. I was fully satisfied, and frequently got between 6 to 7h of screen time.
Sadly, since early june, I barely get half of that under normal usage (2-3 hours), and I've never been able to go a day without charging the phone. The phone is rooted but still on Rogers Canada's original firmware with the original Samsung battery.
I'm no novice to android, but I've run out of ideas. Is it normal for a battery to start loosing it's capacity after around 120 to 150 charging cycles?
1) I thought it might be related to my external microsd, because I started getting error messages that I was disconnecting, and the mediascanner process was running for an abnormally long time. I wiped the card, and the errors persisted. Finally, I removed it altogether and the mediascanner battery drain stoppped, but overall battery life didn't get any better
2) I comptetelly wiped the phone and started from scratch, reinstalling everything from the market. No change.
3) I've been checking per app battery usage with BetterBatteryStats, and I occasionnally get one misbehaving app that keeps the phone awake, so I installed Greenify to prevent a few of them from gobbling up resources. That's helped a lot, at least on BetterBatteryStats, but still the phone doesn't last longer. There is no more obviously abnormal app anymore.
4) I tough it might be related to the fact that I redirected all my work email to gmail, so I set it to manual mode, but it hasn't helped.
5) I did notice that the cpu stays either in deep sleep or at 1,1 ghz, almost without using the other speeds. I don't know that I can do anything about that with the stock kernel.
Is there something else I could be checking? The phone worked great for six months without gooing through all of that stuff, so the only thing I can think of is a hardware issue. Did I get a faulty battery?
Thanks for your insights.
Nothing lasts forever; buy a new battery
hmmm the 1.1ghz thing makes it seem like it could be a deeper issue, there is no reason it should be sticking at a frequency that high.. I would personally try to flash the stock rom fresh with odin.
That would be your issue, the high frequency, not the battery itself imo
wase4711 said:
Nothing lasts forever; buy a new battery
Click to expand...
Click to collapse
Diomonds do
please use spell check..
d-i-a-m-o-n-d-s.....:victory:
Lol
They don't last forever if they had a beginning. . .ooooh.
reminds me of this http://en.wikipedia.org/wiki/Pinocchio_paradox
I notice thst on mine im loosing juice quick when my LTE radio is on and I'm in poor coverage area. Switching to 4g/3g/2g only helps a lot. On day when I take few pics my battery takes a hit because all pictures backup performed by dropbox etc
Sent from my SGH-T889 using xda app-developers app
Hi all,
So i got a HTC 10 UAE edition from a guy two days before. He was selling it at a reasonable price and i bought it from him.
The battery was draining quite fast and i thought it might be a software issue and i installed venom rom, but problem still existed, so i turned back to stock 2.41.401.41 (Which was very hard though) .
Still the battery is draining so fast. The charger came with the phone( Quick charger ) was also not working and now i'm facing the phone's battery is draining so fast. I'm very confused whether that guy have cheated me or not. If this is a hardware issue i think i have to contact that guy soon.
adb battery stat gave me 2580mah full charge capacity and here, i'm attaching the GSAM battery logs.
Please help me on this
Thanks
Edit: Since the original charger isnt working, im using a oppo 5v- 1A charger, is dat matters on battery drain?
Mine was doing the same as yours, quick charge also stopped working. I changed the cable and it solved it for a few weeks, but the drain started again and quick charge stopped again. Tried ruu etc but no luck. I've sent mine in for repair under warranty and should get it back Monday. My guess is either the charging port is faulty or motherboard but will find out next week.
I was having the exact same problem. I downloaded an app called Lspeed (It's also on the playstore) and did some tweaking in that app as well as used the Enable doze for GMS Magisk Module and now my kernel and android system are on par with each other as far as battery drain goes. Not sure why there are only a handful of people that experience this problem but i'll edit this post with screens of my lspeed config if you want to give that a go!
Edit: Config uploaded. Some of those options are personal preference but take a look around and test it out. What you'll most likely want is to enable the light doze optimization and disable the debugging. That will most likely help in your situation.
Very strange, I'm experiencing this issue too, always receive around 2-3hrs of screen on with very high kernel use during standby. Tried flashing Leedroid, Element X to no avail.
timbohobbs said:
Mine was doing the same as yours, quick charge also stopped working. I changed the cable and it solved it for a few weeks, but the drain started again and quick charge stopped again. Tried ruu etc but no luck. I've sent mine in for repair under warranty and should get it back Monday. My guess is either the charging port is faulty or motherboard but will find out next week.
Click to expand...
Click to collapse
Mine is out of warranty. Dunno what to do now. Tried almost everything.
bilibox said:
I was having the exact same problem. I downloaded an app called Lspeed (It's also on the playstore) and did some tweaking in that app as well as used the Enable doze for GMS Magisk Module and now my kernel and android system are on par with each other as far as battery drain goes. Not sure why there are only a handful of people that experience this problem but i'll edit this post with screens of my lspeed config if you want to give that a go!
Edit: Config uploaded. Some of those options are personal preference but take a look around and test it out. What you'll most likely want is to enable the light doze optimization and disable the debugging. That will most likely help in your situation.
Click to expand...
Click to collapse
I'm currently running on pure stock. Will try this method soon. How was your battery standby before doing the tweak ?
Have you tried wiping cache? Mine drains fast depending on the load, which is usually pretty heavy daily. Plus, I don't dim my screen much. Never knew the advice command for battery. I gotta try that.
Stock Rom
Okay, so I got fed up with the battery life I've been getting and have looked more into it, I've managed to reclaim a lot of the longevity I had before updating to Nougat without hampering UI fluidity. For reference, I'm using Leedroid 3.9 with Element X v1.08 and was getting around 2hrs screen on, android system and kernel had the highest usage under GSam.
bilibox has the right idea, my idle drain was very high, L speed and Greenify both have options to enable a more aggressive Doze which worked pretty well, I lose ~10% battery overnight vs a shocking 20-30% before. I still felt battery drain was too high when active, I combined ivicask's PNP mod (balanced) with some little governor tweaks in EX Kernel manager, basically, I'm using interactive on the little cluster and elementx governor on the big cluster (which tends to be slightly more conservative in my uses). I also set min performance to 0% and downclocked the big cluster to 2Ghz, I'm focusing on these cores since they were draining a lot of power in my case.
It's not a super extensive list of tweaks nor something we haven't seen before, but I manage around 3.5hrs of screen on now which gets me through the day. Before I would have to top up around early afternoon, the phone is also really smooth and I'm happy with how everything is running. I hope this helps some people out!
ryanjsoo said:
Okay, so I got fed up with the battery life I've been getting and have looked more into it, I've managed to reclaim a lot of the longevity I had before updating to Nougat without hampering UI fluidity. For reference, I'm using Leedroid 3.9 with Element X v1.08 and was getting around 2hrs screen on, android system and kernel had the highest usage under GSam.
bilibox has the right idea, my idle drain was very high, L speed and Greenify both have options to enable a more aggressive Doze which worked pretty well, I lose ~10% battery overnight vs a shocking 20-30% before. I still felt battery drain was too high when active, I combined ivicask's PNP mod (balanced) with some little governor tweaks in EX Kernel manager, basically, I'm using interactive on the little cluster and elementx governor on the big cluster (which tends to be slightly more conservative in my uses). I also set min performance to 0% and downclocked the big cluster to 2Ghz, I'm focusing on these cores since they were draining a lot of power in my case.
It's not a super extensive list of tweaks nor something we haven't seen before, but I manage around 3.5hrs of screen on now which gets me through the day. Before I would have to top up around early afternoon, the phone is also really smooth and I'm happy with how everything is running. I hope this helps some people out!
Click to expand...
Click to collapse
Still its bad that a 3000mah battery with a smaller screen compared to other flagships giving a very low battery backup just because of software bug. From reviews, i can see that MM is giving fine SoT as well as standby. One thing i really cant is the standby. I cant even go out for a day trip. The battery will die in just 10-12hrs even on standby.
$tark3 said:
Still its bad that a 3000mah battery with a smaller screen compared to other flagships giving a very low battery backup just because of software bug. From reviews, i can see that MM is giving fine SoT as well as standby. One thing i really cant is the standby. I cant even go out for a day trip. The battery will die in just 10-12hrs even on standby.
Click to expand...
Click to collapse
That's unfortunate to hear, my battery life is pretty much in line with my friend's S7 now, newer devices can get away with larger displays because the 835 is a bit more efficient.
ryanjsoo said:
That's unfortunate to hear, my battery life is pretty much in line with my friend's S7 now, newer devices can get away with larger displays because the 835 is a bit more efficient.
Click to expand...
Click to collapse
Soon i'll have to ditch htc.
$tark3 said:
Soon i'll have to ditch htc.
Click to expand...
Click to collapse
I restore my phone and did all updates again. My battery still seems to drain very quick .in an hour with some navigation, and little screen use It went from 20% to 1 percent.
I've taken excellent care of my HTC. Before this, I had HTC 8 and loved it, until right at the 2-year mark, a small area of the screen stopped working.
This is the second time I` experience this, and sadly there won't be a third., especially after new HTC removed the headphone jack like the iPhone ... RIP HTC
Well to be honest the past couple days were to weird to me usually i get 5 - 6 SOA over 13 hours
now i get 3:30 - 4 SOA over 13 hours, same usage, and i have noticed that google service consume most of the power, i have installed doze program and kept my eye on GSM battery Monitor, after all the google service kept the kernal wake up for a long time, and keep running the hardware on the full abilities
I unistalled Gsam battery monitor and kernel usage is back to normal...
AggelosGR said:
I unistalled Gsam battery monitor and kernel usage is back to normal...
Click to expand...
Click to collapse
I have uninstalled ForceDoze and Gsam Bettery this morning but still feeling that there is something wrong, i might do some battery calibration on my free time, because i charge my phone only for 90% and it did not get lower than 20% i feel like i am losing the battery capacity
Was having the same issue, and had been searching for weeks to try and solve this. Tried rooting, factory resets, ROMs, everything.
For me the issue was Google Sync, in particular Contacts and People syncing. I disabled those and everything is back to normal. There was a program called Google Contacts Sync (Apps > Show System > Google Contacts Sync). I cleared the data on that, and then went into Accounts and Sync and turned everything off. That fixed the battery drain. I have tried turning back on Gmail, Keep and a few others and still have great battery.
I have the same issue and I don't know how to fix it. Please help