Related
Hello!
I've had my HTC EVO 3D for 16 months. Everything is stock . 1 Week ago my battery begun to drain awfully fast, up to 2%/minute at lowest brightness. Charging the battery with screen on keeps the battery at the same % or sometimes it goes slowly down. I tried to factory reset the phone (thought there was an app eating my battery) but it didn't help. Everything excluding mobile network is turned off. "what has been using the battery" tells me:
Screen: 78%
Cell standby: 12%
Phone idle: 10%
Is it time for a new battery or?
Question 2:
I've heard about many screen problems with the EVO 3D. My bottom part of the screen doesnt work (buttons does). I tried the draw test and it's impossible to touch the bottom of the screen. Anyone got this problem?
i had a similar problem. my battery drained WAAAY fast. only lasts about an hour on use, and 4 hours on standby. drain rate equal to yours as well. you say your EVO is 16 months, mine is 8. maybe my problem was the same as yours but half (lol). my screen was non responsive on the bottom at times as well. i also had this little dark spot on the screen. like a smudge right in the middle. it didnt affect anything but it was bothersome to look at. i got similar battery usage, but what the phone doesnt tell you is the truth about the radios. i live in a place with poor signal. and just recently i discovered that the worse the signal is, the more the battery will drain. because the 3G or 4G radio has to stay on for longer to retrieve data, which eats the battery in a flash. in your case it could be out of plain usage. i dont know. anyways. i checked the battery to realize it had a bump. like a little swollen. i also realized that with the battery cover off the battery kinda sticked out a little, unlike when i got it. realized as well that with the cap off the smudge on the screen disappeared, and the touch interface was not giving me trouble. then i arrived to the conclusion that poor battery life was due to poor reception, and the screen problems were caused by my battery applying pressure to the display from the inside. i bough a pair of replacement batteries from Anker, and i dont have any problems. the battery life is a little longer as well.
maybe that could not be the case with you, but check your battery just in case. and also try to run your phone for a while on airplane mode, and if you see a great battery life increase like i did, then its the reception. if not, the battery either went bad, or you have a battery vampire app lurking around. and if that is the case, try the greenify app (root required) so you can hibernate all apps while you dont use them, and eliminate their background process. and if after that you dont see any battery increase, or you notice your battery being a little swollen like mine was (if you dont see it swollen try putting it on a flat surface, and see if its laying flat), then yes, its time for a new one. it cant hurt getting a new one, using the same battery for 16 months should have decreased the battery's performance anyways. but note that if the battery life problem is due to network connectivity, a new battery will only help a little.
hope i helped!
I noticed my NT with CM11 nightly installed(http://forum.xda-developers.com/showthread.php?t=2560827) becomes very unstable when battery drops below 50%. For example, menu pops up by itself, apps launch by themselves, screen changes by itself, and you name it. It is like it has its own mind! But once I plug in the charger, then everything goes back to normal. Anyone else has this issue or is it just me?
Penguin101 said:
I noticed my NT with CM11 nightly installed(http://forum.xda-developers.com/showthread.php?t=2560827) becomes very unstable when battery drops below 50%. For example, menu pops up by itself, apps launch by themselves, screen changes by itself, and you name it. It is like it has its own mind! But once I plug in the charger, then everything goes back to normal. Anyone else has this issue or is it just me?
Click to expand...
Click to collapse
I have only seen it really bad if I had flashed the 10 touch LCD firmware, and on the units Ive seen it, reverting to stock LCD firmware corrected it.
50% seem unusually high for that, but even using stock B&N software there have been reports of whacky behaviour when the battery gets low.
I have had this problem with both stock ROM and CM10.x (2-touch) when my battery is in the 20-30% range. 50% is indeed a bit high for the NT to act up.
You might want to look into the battery calibration apps (I myself have not used them). Some of these apps suggest the optional step of letting the battery completely discharge after a calibration, but personally I would skip that optional step as there have been reports of difficulty in recharging NTs that are completely discharged.
I just registered because I made a discovery which I think is worth sharing here, and that is, as the title says, that having Knock On enabled drains the battery considerably. Also I'm pretty sure it started happening after the KitKat upgrade, so it's not an inherent problem.
I can't post a thumbnail or normal link as a new forum user, so please paste this into your address bar to see the proof pic:
i.imgur.com/pqtUlSM.png (only 60kb)
In that image, the blue bubbles mean the times when I disabled Knock On, and the red one when I enabled it. The phone had Wi-Fi enabled and was idle almost all the time with light usage after the last bubble, but it's not the most relevant part.
My G2 is a 32GB D802 from Vodafone Spain, and it's unrooted and untouched, except I disabled all the bloatware I could. I don't use any app for battery or software management.
That's all, check for yourselves and let's hope LG fixes it in the upcoming Knock Code update.
Edit: realized about attachments.
Klementh said:
I just registered because I made a discovery which I think is worth sharing here, and that is, as the title says, that having Knock On enabled drains the battery considerably. Also I'm pretty sure it started happening after the KitKat upgrade, so it's not an inherent problem.
I can't post a thumbnail or normal link as a new forum user, so please paste this into your address bar too see the proof pic:
i.imgur.com/pqtUlSM.png (only 60kb)
In that image, the blue bubbles mean the times when I disabled Knock On, and the red one when I enabled it. The phone had Wi-Fi enabled and was idle almost all the time with light usage after the last bubble, but it's not the most relevant part.
My G2 is a 32GB D802 from Vodafone Spain, and it's unrooted and untouched, except I disabled all the bloatware I could. I don't use any app for battery or software management.
That's all, check for yourselves and let's hope LG fixes it in the upcoming Knock Code update.
Click to expand...
Click to collapse
It's a little like saying the battery is used more when I'm not in Airplane mode, or if I have the screen on...
These are Smartphones and are designed to be used. Certain features may consume a little power, but that's why we have a huge battery. I'm not sure if you see this as a problem or not, but I get 2-3 days of moderate usage with everything on and syncing. With Knock on - I've never turned it off. Great feature.
I attach my KK battery life for reference - very acceptable.
And yes, Knock code (for what use that gimmick will be - remember the fuss over the now-forgotten Face Recognition?) will obviously use a little battery.
LenAsh said:
It's a little like saying the battery is used more when I'm not in Airplane mode, or if I have the screen on...
These are Smartphones and are designed to be used. Certain features may consume a little power, but that's why we have a huge battery. I'm not sure if you see this as a problem or not, but I get 2-3 days of moderate usage with everything on and syncing. With Knock on - I've never turned it off. Great feature.
I attach my KK battery life for reference - very acceptable.
And yes, Knock code (for what use that gimmick will be - remember the fuss over the now-forgotten Face Recognition?) will obviously use a little battery.
Click to expand...
Click to collapse
Sounds logical LenAsh, but you ignored the part when I said It started happening with KK. See the almost straight line before the red bubble? that's how it looked like on JB after a night with Knock On enabled.
edited
Might be true! Almost everyone on KK says that -
1. KnockOn is much more responsive
2. battery life has gone down
Its quite possible that LG increased the current draw and/or polling period of KnockOn to get #1 which causes #2.
So it uses like .2%/hr vs .1%/hr or something? Meh.
ECrispy said:
Might be true! Almost everyone on KK says that -
1. KnockOn is much more responsive
2. battery life has gone down
Its quite possible that LG increased the current draw and/or polling period of KnockOn to get #1 which causes #2.
Click to expand...
Click to collapse
For me the battery life has actually gone up since KitKat.
I do agree that KnockOn could consume a bit of power. But I could not live without this feature.
I got better battery life with KK! :/ But the difference isnt that big with non KK! Still an improvement though!
cool to know. turned off forever. good riddance.
I flashed Malladus 2.0.1 and I noticed the LG Gravity Sensor does not show up as a "battery drain" anymore, yet double tap still works perfectly. Battery life is also improved.
Hello all, I hope I'm posting in the right section.
I've been searching for info on the battery drain problem for some time now. I have used GSam and System Panel to find the culprit and observe it for a while and I think I see what is happening. Don't know if there is anything to be done but I'm hoping there is a fix out there.
Background:
Stock Verizon Samsung Galaxy S4, stock Rom on latest OTA update (screen shot attached)
One morning around Christmas time my phone drained the battery from full to 10% in about 5 hours. I had my phone in my pocket like every other day at work, I had noticed it was heating up as well. I got an error message at some point that morning about some kind of "Samsung Power Share" I had never heard of. Then I could not get the phone to charge unless powered off, and that very slowly; it was the "grey battery" problem. This problem persisted for several days and then turned intermittent then nearly back to normal, though never quite right.
What I've done:
Wipe cache, FDR, replaced USB charge port, replaced stock battery with Anker battery.
The new charge port dramatically improved recharge time and eliminated the grey battery error but I still have terrible battery life compared to earlier in this phone's life, in other words, compared to before the latest OTA which appears to be a disaster. Didn't notice any significant improvement with the new battery.
Here's what I've seen:
As soon as the battery drops below 50% the rate of discharge maxes out and this matches up almost exactly with the activity or CPU usage of the system process "krtccd." (See attached pics showing krtccd activity corresponding with increased battery drain below 50%). GSam shows the "Kernel Android OS" (in which is krtccd) using 50% of the battery where it used to be that the screen was the biggest drain, pic attached.
Is there any way to control "krtccd" as it seems to go rogue? Why does it only seem to go rogue when the battery gets below 50%?
This is a company owned phone so rooting is not an option unfortunately.
Thank you so much for any input you may have!
I apologize if this posted in the wrong part of the forum. I did do a lot of attaching for info on what the krtccd process does and why it changed so drastically with the last OTA update but I can't find much out there or in here. I don't have the option to root phone so am I such with this weird poor performance whenever the battery drops below 50%?
Thanks again, I appreciate any input you guys have.
As a follow-up, here is a screen shot from System Panel this morning showing that "krtccd" stopped activity as soon as the battery began to charge. I don't get it, it's like it spins full bore in the background sabotaging the battery for the last 50%.
BTW, the discharge last night (in my first set of screen shots) happened while the phone dat idle on my windowsill, don't think I even turned the screen on during that whole time as I was in discussion with a friend. It's weird...
Rooted Galaxy S4 (Sprint)
Same issue. Can anyone provide any information on what this process does?
Someone opened an issue report with android open source.
Issue 160689: KRTCCD Bug?
[Notes:
• I put this thread in this section because of the "Other" tag. If it is unrelated consider moving my post, thank you.
• This is an issue report for my device, I am not saying that everybody got the same. ]
Hello,
I got a battery issue on my Samsung Galaxy Core Prime for at least more than a year.
The problem is: almost everytime, my phone crash when arround 40% battery level. It's not an informatic crash but... I'm not sure. The phone just suddenly shut down, not as it ran out of battery, displaying the shutdown logo and going to sleep, it behave like I pulled off the battery.
This is not a battery misplacement problem because the shutdown doesn't happen a totally random way: it never triggered over 50% for now.
Moreover, the battery level goes wrong after such crash. Even after waiting some time with battery out of phone I got randomly a new battery percentage that will be either lower, same or even higher than when it crashed. So maybe the whole problem is due to a shift between real battery percentage and what phone determined.
I also noticed that when rebooting after the crash the phone speakers make a weird sound, a kind of "shhhhhhhh" even with silent mode enabled and no system sound, and when it happens phone recrash on booting (system) logo.
I personally don't think it's system's fault, because between the first time it happened and now I may have flashed at least 6 times my ROM and made various wipes. Also somebody getting the same phone model than me never got such problem, even tough he is not rooted and has recent firmware. In the end the problem getting worse and worse again (=more frequent) so I'm almost sure it's a material problem.
But which one? Is this directly battery's fault or is it captor's fault? Actually I threatened the battery very badly, it's true. But everything I did — overcharging, emptying battery at the time I thought that was a good thing because of a suppoesed memory effect like nickel batteries, using charger block from an older device with a bit different configuration — should have shortened the battery's life, however it's just like the battery is now discharging a bit faster but got a kind of danger zone where you're not sure that it will keep behaving normally, so much that some measurements and developing apps determined that my battery have a good health, that is maybe absolutely FALSE.
Talking about this danger zone, I also noticed something even stranger over all.
Depending of what I do, I got higher or lower chance to have my phone crashing under 40% level:
- If Wifi is enabled, the phone got arround a half more chance to shut down unexpectedly.
- This is worse when using data consuming app (i.e. Youtube)
- Using more hardware also increase this phenomenon (when using camera) and enabling flash instantaneously and almost everytime crash the phone.
Here are what I reported.
What do you think?
It has happened to me many times. So i normally keep it charging all the time to be safe.
Prime said:
It has happened to me many times. So i normally keep it charging all the time to be safe.
Click to expand...
Click to collapse
All the time for real? Be careful, that's not a good practice. Unless you removed the battery first, this will get worse if you do that.
I have a similar but possibly unrelated problem.
If i charge upto 100%, the battery goes directly to 0 after around 50%.
If i charge upto 50%, then the battery drains rapidly after around 20%.
I don't think its a battery problem because its the same with two replacement batteries and a stock battery. (Or maybe I have a bad luck and bought ****ty batteries)
Will post a screenshot soon...
I have the Same problem i changed the battery twice but i still have the issue
rms112 said:
I have a similar but possibly unrelated problem.
If i charge upto 100%, the battery goes directly to 0 after around 50%.
If i charge upto 50%, then the battery drains rapidly after around 20%.
I don't think its a battery problem because its the same with two replacement batteries and a stock battery. (Or maybe I have a bad luck and bought ****ty batteries)
Will post a screenshot soon...
Click to expand...
Click to collapse
What you posted is close to what I noticed, so it is not unrelated.
This is weird that after buying two more batteries the issue still occure...
I've this problem too :/ (G361H)
I have this problem too. This is the batteries fault only.
Atronid said:
[Notes:
• I put this thread in this section because of the "Other" tag. If it is unrelated consider moving my post, thank you.
• This is an issue report for my device, I am not saying that everybody got the same. ]
Hello,
I got a battery issue on my Samsung Galaxy Core Prime for at least more than a year.
The problem is: almost everytime, my phone crash when arround 40% battery level. It's not an informatic crash but... I'm not sure. The phone just suddenly shut down, not as it ran out of battery, displaying the shutdown logo and going to sleep, it behave like I pulled off the battery.
This is not a battery misplacement problem because the shutdown doesn't happen a totally random way: it never triggered over 50% for now.
Moreover, the battery level goes wrong after such crash. Even after waiting some time with battery out of phone I got randomly a new battery percentage that will be either lower, same or even higher than when it crashed. So maybe the whole problem is due to a shift between real battery percentage and what phone determined.
I also noticed that when rebooting after the crash the phone speakers make a weird sound, a kind of "shhhhhhhh" even with silent mode enabled and no system sound, and when it happens phone recrash on booting (system) logo.
I personally don't think it's system's fault, because between the first time it happened and now I may have flashed at least 6 times my ROM and made various wipes. Also somebody getting the same phone model than me never got such problem, even tough he is not rooted and has recent firmware. In the end the problem getting worse and worse again (=more frequent) so I'm almost sure it's a material problem.
But which one? Is this directly battery's fault or is it captor's fault? Actually I threatened the battery very badly, it's true. But everything I did — overcharging, emptying battery at the time I thought that was a good thing because of a suppoesed memory effect like nickel batteries, using charger block from an older device with a bit different configuration — should have shortened the battery's life, however it's just like the battery is now discharging a bit faster but got a kind of danger zone where you're not sure that it will keep behaving normally, so much that some measurements and developing apps determined that my battery have a good health, that is maybe absolutely FALSE.
Talking about this danger zone, I also noticed something even stranger over all.
Depending of what I do, I got higher or lower chance to have my phone crashing under 40% level:
- If Wifi is enabled, the phone got arround a half more chance to shut down unexpectedly.
- This is worse when using data consuming app (i.e. Youtube)
- Using more hardware also increase this phenomenon (when using camera) and enabling flash instantaneously and almost everytime crash the phone.
Here are what I reported.
What do you think?
Click to expand...
Click to collapse
My device goes at 60%, 40%, etc. and then it starts repedeatly pressing the right side of my screen and not letting me tap the screen, so I lock it and unlock it very fast and I can use the touchscreen for a few moments, before it shuts down without the shutdown screen and makes a *tick* sound, almost like there was an electrical shock inside the battery. I have a PRF and TWRP 2.8.7.0.
EdyCommentaries said:
My device goes at 60%, 40%, etc. and then it starts repedeatly pressing the right side of my screen and not letting me tap the screen, so I lock it and unlock it very fast and I can use the touchscreen for a few moments, before it shuts down without the shutdown screen and makes a *tick* sound, almost like there was an electrical shock inside the battery. I have a PRF and TWRP 2.8.7.0.
Click to expand...
Click to collapse
Got exactly the same problem. You can try to change the battery but in my opinion the only good solution would be to buy another phone. This is personally what I did, as this model gets old really early.
EdyCommentaries said:
My device goes at 60%, 40%, etc. and then it starts repedeatly pressing the right side of my screen and not letting me tap the screen, so I lock it and unlock it very fast and I can use the touchscreen for a few moments, before it shuts down without the shutdown screen and makes a *tick* sound, almost like there was an electrical shock inside the battery. I have a PRF and TWRP 2.8.7.0.
Click to expand...
Click to collapse
I have this same exact problem and the only fixes according to me is to buy a new phone or replace the battery. Also I noticed that the battery of my device has bulged.
RIP, I have the SM-G360T1, stock based custom ROM with TWRP 3.0.1 and this thing's started to give up. Same issues as the people above encountered. The phantom touches are getting wayyy more repetitive, the battery all of a sudden goes down to an extremely low percentage, even at medium to high percentages (such as 50-60%) and even shuts off without any notification. I also had cases where the phone would completely turn off with no shutdown animation AT ALL, plus a spontaneous but audible *TICK* that follows it. Device performance in general also started to horribly depreciate.
Well, to be fair, I had this device for 3 years and I guess it had its day. Time to upgrade.
My device has started to shut off at 80% battery levels and even worse the device gives just about 25-30 min of SOT. Also stressing the device in any way.. games, YouTube et al just causes it to shut down. I now permanently have a battery pack connected to it at all times. But even after all this, the gives good standby time. Notably the device stand for 3+hrs on 3% battery.
Still my phone is in a pathetic condition. ?
Edit - I just got a new battery (aftermarket brand though) and the ghost touches along with sudden shutdown has gone. Also the OG battery was never touching the connectors properly or the battery placement design was not proper, cause the new aftermarket battery was not connected to the connectors properly.
Peace ?
i also got this problem on my sm-g360HU , try chaging different roms and buying a new battery pack, but still this sudden drain battery still exist, it seems like it's the hardware problem already.