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'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!
Long story short it works out of the box with any retina MBP at 60hz - I did have to use Switchresx to get my monitor to
RépondreSupprimerthe max resolution.