My S9+ (exynos) does not appear to be entering deep sleep. There doesn't appear to be any unusual activity other than cell standby being quite high (was in a low signal area this morning but not usually the case)
Currently unable to install better battery stats but was interested to see if anyone else had been experiencing this, potentially since the last update and if there was:
A) a specific app or process causing this
B) solution to the issue
Any help appreciated
Related
Hi all,
Only had my galaxy s2 for about two weeks now and still sorta learning about everything. Have tried a few different ROMs and kernels but one problem seems to remain no matter what I change to.
I have done a lot of searching on battery life and was shocked to hear that even with moderate use, people can get way over a whole day of battery life. When i first got my phone (I left it on stock (KI3) ROM for about a week) the battery was gone within about 8 hours. I then tried checkrom v4.0 with three different kernels (speedmod, hellcat, and the one that came with checkrom) and still had mostly the same problem, perhaps got an extra 1-2 hours of battery life? Note that every time I was testing for battery life I had sync, wifi, data turned off and brightness turned down. I also tried running batista70 with the provided kernel, and then later with a stock KI4, which took my battery life up to about 12 hours (a significant improvement but still not as good as i'd like) with moderate use (a 30 min phonecall, maybe an hour of web browsing, and perhaps 20 messages?).
After a bit more research I came across a nifty little app called Cpuspy so put it to use. Leaving the phone with any data/process hungry apps turned completely off, I reset the timers and left it for about an hour. Note that I did this for just about every ROM/kernel combination that I tried. The results were strange. After looking at other people's screencaps for cpuspy, I could see that their "deep sleep mode" state was active for anywhere between 70% and 95% of the time tested. My "deep sleep mode" on the other hand was never more than 50% (at one stage it was at about 20%) and this is after leaving the phone completely idle, no data, no wifi, no gps, no.. well no nothing basically. Every single time i test my deep sleep now, it sits at between about 45%-50%, for some odd reason it seems "capped" at 50%.
Next people would normally say "try betterbatterystats to check the partial wakelocks" and that is the very next thing I did. Setting it to test "since unplugged", turning everything off again, unplugging the phone, and leaving the phone for two hours, the results seemed like they were negative for partial wakelocks. There were only a few processes that were detected in the time and all of them only lasted a matter of seconds. Unless I was using the app incorrectly, it seems that wakelocks aren't my problem. The phone IS entering deep sleep mode, but in cpuspy it seems to be in 500mHz 20% of the time, 200mHz 30% of the time, and deep sleep 50% of the time.
I have just flashed back to stock ROM, except this time i am trying KI4 instead of KI3. Even though i've tried KI4 with batista before (yielding yet again the same results) I thought it would be a good idea to flash to KI4 completely, upgrading the modem and such in the process. Testing it again, it seems to be the same, no more than 50% deep sleep state when left completely idle. The next step will be to chuck a CFroot on and install betterbatterystats again with stock KI4 and check for wakelocks again.
I really would love to do more thorough testing and provide you guys with some less vague information (i.e. screencaps and stuff) but as I dont have a spare phone I am kinda relying on my new gs2 and can't leave it completely idle all the time. Tonight I will do a BBS test along with cpuspy and advise of the results.
Apologies for the long-winded explanation, I just wanted to provide as much information as I could on the issue to prevent having to explain more later.
Any assistance or suggestions would be highly appreciated!
P.s. I've done many forum and google searches on the issue but I can't seem to find anyone with the same problem (most of them are for the phone not entering deep sleep state at all). If I have overlooked an important article/forum post please throw a link my way.
Thanks!
Update: For some reason I decided to try checking the sleep time with my sim removed and I was getting closer to 100% deep sleep! I then proceeded to try a friend's optus sim in my phone(mine is telstra on nextg network I.e. uses WCDMA) And once again the deep sleep time was normal. The only difference between the sim cards is the optus one doesn't use wcdma. Went into the phone's "secret" menu (that's just what my brother calls it ) and switched the network type to WCDMA Only from WCDMA preferred and I -think- it's helping with deep sleep. I am about to do some thorough testing with this setting and I'm hoping for some promising results!
All I can assume is there's something to do with the network constantly "deciding" which network to use I.e. not necessarily the switching itself, but some sort of polling perhaps? Just a guess.. I don't know a lot about mobile networks so I wont pretend I know what I'm talking about.
Anyway, will keep you all posted (that is, to anyone who's reading this). If anyone has any input at all it would be appreciated (even just information about mobile networks and stuff)
Cheers!
Hi,
I got an I9108 recently (from China Mobile). Found a very serious and strange battery drain issue. The phone works normal at day time. but at night, 8 hours stanby can eat 50-60% of my battery, for both of my batteries. Had a check by the service center, they siad the phone has no issue, and gave me two brand new batteries, problem still exist. I turned off almost everything: Wifi, GPS, background update, GSM data, etc. Battery usages shows Android OS is eating >80%.
One funny thing I noticed is: if I put the phone in a warm environment (say in quilt when sleeping), the battery drain seems to be normal: around 5% for 8 hours stanby.
I installed Battery Monitor Widget, and set current monitor to be every 5 minutes. I noticed that normal standby (day time, it is normally warm as I will put the phone in my pocket) current is around 5-10ma. When making a call, the current is around 25-40ma. But at mid night (realtively cold, may 10-15C), the current can easily be 50-60ma (not evry minute). So basically night time stanby is consuming more battery than a call.
Anyone see similar issue before? Any solution? Help is great appreciated.
Find/install BetterBatteryStats (thread on here or Market). Allow your phone to run overnight/for at least a couple of hours with it installed.
Read the first 10 pages/last 10 pages of the BBS thread on here so you have an idea of the info the guys on the thread will need from you in order to identify what's causing this drain & help you possibly improve this battery drain issue.
Ok, I've download BetterBatteryStats. will let it run for today and send updates tomorrow.
Looks to me the issue does not seem to be App related. Since it goes with working temperature, may it be possible that at night CPU just could not down the frequency to 300MHz but just keep working at 1200MHz?
anyway, will see how it goes for tonight.
Had it run for a night. Found partial wakelock: RIJL, ActivityManager and Alarm Manager are the tops 3, but all below 1.5%. AlarmManager seems to have a lot of count though (>2000)
For Kernal Wakelock, found samsung-battery is the one using 35%.
How should I fix it?
Ask in the BBS thread on here (search for it).
Got my issued solved by replacing the MB. Now stanby battery drain down to 5-8% for a night (8-10 hours).
Thanks for help anyway
I was wondering if anyone was experience a problem with the mediapad. I have two units and they have both been experience the same symptom. The unit would awake from deep sleep mode and drain the battery with the screen on and the CPU on full. I have been monitoring my tablet and the cpuspy records the tablet in deep sleep mode for 136:46 with other CPU speeds at less than 2 minutes. However, at 1188mhz, it was recorded for 4:56 minutes which is draining the battery so when I turn it on, it notifies me that it has 2% left. I've used betterbatterystats but I don't quite understand how to read the data. It says that it's been away for approx 5 hours which is when the CPU was at 1188mhz.
More info
This was happening on HC as well, so I'm wondering maybe if these units are defective if no one else is experiencing it. Having said that, I've read that huawei warranty/CS is horrendous.
Any help would be appreciated it is appearing on two identical units.
Cheers!
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?
Hi,
I've been using this G5 for more than 6 months. At the beginning it performed good, reaching easily 5h of SOT with localization, 3g, wifi and everything on. Recently I noticed a huge drop in battery because I only get 3h of SOT with a similar usage.
Yesterday I did a factory reset (v20a EUR) and then also rooted it to inspect wakelocks. The factory reset did not solve anything but I got some more information with BBS.
Android System: WifiOffDelayIfNotUsed
Google Play Services: NlpWakeLock
I didn't perform a test over the whole battery cycle because leaving the device alone for just 3 minutes is enough to notice a greater number of wakelocks with the same label. Really: leaving the screen off for a minute will increase the wakelock time of 10 seconds.
Turning off the wifi and switching to 3g seems to completely solve the issue. Disabling "keep wifi active during sleep" doesn't solve the problem.
Do you have any suggestion?