Has anyone else been using CPU Spy to monitor Deep Sleep? I haven't once seen my phone going in to Deep Sleep. Anyone else?
Yeah I used it since yesterday. I've frozen a ton of bloatware via TB and it went into deep sleep for 7.5hrs last night while I was asleep. I'm seeing a crazy amount of different CPU speeds in there too though. Very odd.
I actually removed all the damn bloatware instead of freezing them. But then I added my own apps that I normally use. But I think I have finally weed out the damn app that is causing my deep sleep issues. it's either FriendCaster Pro or Google Music Beta...
I gave it a try yesterday when I first picked it up. Seems to either idle really high, or low depending on what your doing. Hardly ever used the mid range cpu frequencies.
yes! Once the source code can be.... had.... Kernel development would begin. As anyone have seen using CPU Spy, the governor either MAX out the CPU or just lower it to the minimal, it "rarely" stays in the middle. With some "tweeking" how the CPUFreq works we can probably save battery
mbze430 said:
Has anyone else been using CPU Spy to monitor Deep Sleep? I haven't once seen my phone going in to Deep Sleep. Anyone else?
Click to expand...
Click to collapse
I have been using it for a couple of weeks now along with Antutu CPU Master. After charging, I usually reboot my phone and deep sleep kicks in. I use Antutu to lower the CPU speed to 192 mhz.
RAVEN6 said:
I have been using it for a couple of weeks now along with Antutu CPU Master. After charging, I usually reboot my phone and deep sleep kicks in. I use Antutu to lower the CPU speed to 192 mhz.
Click to expand...
Click to collapse
Are you having any problems with Antutu keeping the setting at 192, after I reboot my phone Antutu keeps changing the low setting up to 384? Yes I have it set to apply on boot. I sent the Antutu devs an email a few days ago asking them about this, but no reply?
Sent from, The Eclectic Chair.
I thought this was the deep sleep issue that people have with certain chargers?? plug charger in and let screen turn off then turn screen on and unlock, then unplug charger. Check to see if it goes into deep sleep then or just reboot the phone after charging....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Related
The problem is, no matter what program I use, if I set the Tab to downclock at 100/200 or even 100/400 when the screen is off, the phone will freeze in sleep and force me to reset the tablet pressing the power buttornfor 7 seconds.
Anybody else have this issue?
Sent from my Milestone
do you use SerCPU?
I set is 100/400, it sometimes work but my phone was getting random reboot.
So I disabled it...
Sent from my GT-P1000 using XDA App
same issue with me , if I set the cpu to 100 to 300 it would hang or crash coming out of sleep mode . I ended up removing setcpu and going back to stock . i expect the Cooked roms will resolve this later on .
Probably kernel related. If i select the Set On Boot option, after a reboot both min/max freqs will change to a min of 19 and max of 500. Probably best to leave it until we have devs working on it.
Sent from my GT-P1000
there's really no need to underclock when the screens off, you know that right?
infamousjax said:
there's really no need to underclock when the screens off, you know that right?
Click to expand...
Click to collapse
Get an app to graph the cpu use, and you will see the cpu spike when sleeping.
So, in short, yes: downclocking with the screen off really help the battery life
Sent from my Milestone
It doesn't make much difference as the cpu scaling does a more than adequate job, but whatever wets your whistle
So my phone would constantly either cut off or not wake up (not sure which) if I left it idle for a few minutes. The only way to get it going again was to pull the battery then power it back on. It seemed like a lot of people were having this issue so I started playing around to see how I might fix it. I used Set CPU and turned up the minimum clock speed from 212 mhz to 312 mhz. It's been a couple of hours now and it seems to be working fine, with little noticeable effect on battery life. Hope this helps.
that happened to me today. It was my first time running juice defender and set cpu on screen off to 216/312.
No more of that for me... Ill start shutting off connections myself to save battery.
Sent from my LG-P999 using XDA Premium App
I had the opposite happen. setcpu was causing me to get the sleep of death and reboot loops until I disabled it.
I have been noticing bad battery life recently and I checked my setcpu settings and for some reason my phone never goes below 602 MHz. I have my profile set to 389 as the lowest frequency. I was wondering if anyone knows the problem and if there is anything I can do about this.
Sent from my LG-P999 using XDA
Bump
Sent from my LG-P999 using XDA
there was another thread (Here) about 5 days before you posted this. Read that... this is just part of what i posted:
this phone (and alot of newer ones) are using an idea called Race to idle.
this means that the cpu will kick its cpu speed up higher than it needs to get things done faster, so it can get back to a low power idle state faster.
In reality your cpu is really going in and out of sleep states hundreds or thousands of times a second, the frequency is just kicked up so that it can spend less time computing, and more time sleeping.
for the hell of it try downloading an app that shows you cpu usage in %
that number is the amount of time that the cpu is in a fully awake state vs being in its first stage sleep state, LP1.
if nothing happens for a bit longer than it will go into an even lower power state called LP2. frequency can still be set to a higher number (like 600mhz or even 1ghz) but the cpu is actually not doing any calculations. its sleeping till something needs it.
also, changing cpu speed takes a long time (cpu wise), the cpu has to pause, change speed, then wake up. so the less it does this the less lag you have.
Click to expand...
Click to collapse
Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...
FirePoncho86 said:
Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...
Click to expand...
Click to collapse
teuv runs at 880mhz.
its possible that an app or a background process is active. try this free app from the market, its called diagnosis https://play.google.com/store/apps/details?id=eu.thedarken.diagnosis&hl=en
I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)
FirePoncho86 said:
I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)
Click to expand...
Click to collapse
1096... thats not teuv, that the t11 kernel. heres the latest teuv http://goo.gl/5JwMT im using this one at the moment
My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s
FirePoncho86 said:
My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s
Click to expand...
Click to collapse
if you just booted, it should(for about 2-4 minutes) then it should drop. unless you have an active live wallpaper, an app thats not written very well, or a process thats gone wild. try that app i linked, let it run for a few hours, maybe you can find the cause.
My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...
FirePoncho86 said:
My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...
Click to expand...
Click to collapse
sounds like a bad download of teuv.
Bad download? I flashed it properly and it booted fine, until after the "optimizing applications" screen
is this the first charge since you flash the kernel? If it is, let the battery run out, charge it full and take a look at it again. I find that ICS really take a full charge to stablize its battery... my first charge after flashing a new kernel has always use a lot more battery than the second charge.
Alright, I'll try that... Also I went back to aosp+ because I really like it.
Also, android system is always using 20% cpu, even on idle..
I remember performing some tests with frequencies and deep idle - I wanted to find out the minimum frequency required to run music player screen-off with few concurrent processes. I remember reading how 400mhz is the optimal frequency for deep idle but cpu spy would always report it cruising at 1ghz and cross referenced with nstools DI stats, it was supposedly in deep idle. With DI off and bumping up the frequency to 800mhz, 1ghz took up the majority of operation time. Long story short, whatever combination I tested did not garner desirable results. That was a couple weeks ago, though. I've since given up on figuring it out.
Wait, are you having the same problem as me?Ive lost 5% battry just by having the screen on for 9 minutes...
I am running cm9(beast mode wifi calling one ) atm but I have a heat issue with my phone around the camera and speaker area where the phone is really hot but by the battery n bottom half it is much cooler.
is this normal for you guys? N gals? And even if I turn of the phone n it cools to 91 is shoot back up again
Sent from my SGH-T959V using xda app-developers app
I'm running on demand btw and around of charge 98-113 charging 109-123
Sent from my SGH-T959V using xda app-developers app
idunno why but we have the same problem..
i think that the reason why it heat up is because you overclocking it?
when i set it max it really heat up quickly.
Install betterbatterystats and see how much CPU you are using and on what.
Sent from my SGH-T959V using xda premium
Sometimes I have this problem while charging my phone, it actually will not charge at all through the night. I think this happens when it is warm, because in the summer, the phone overheats in my pocket and dies out
dgmoodey said:
Sometimes I have this problem while charging my phone, it actually will not charge at all through the night. I think this happens when it is warm, because in the summer, the phone overheats in my pocket and dies out
Click to expand...
Click to collapse
i do that but it goes to 200 mhz never 100
xtrem88 said:
i do that but it goes to 200 mhz never 100
Click to expand...
Click to collapse
That's a 'feature' of the ICS+ kernels. While 100MHZ is the minimum, if it's actually set to that, the kernel is set to go back to 200MHZ anytime it gets the chance. You can watch this happen if your scheduler/governor app actually updates on current min/max speeds. ROM Toolbox PRO, SetCPU, ROM Control, and CM's Performance controls all display this shifting, though with luck you can sometimes get it to stick at 100MHZ. It just takes some persistence.
The modem on the phone isn't very good.
It even happens on stock where if you go in and out of dead zones, it will "SEARCH" for network and become burning hot, so it's a common problem that happens year round. It's a great way to kill battery. That's also why if you leave you phone in a sock drawer, it's going to last longer than if it's in your pocket walking around.
airfluip1 said:
The modem on the phone isn't very good.
It even happens on stock where if you go in and out of dead zones, it will "SEARCH" for network and become burning hot, so it's a common problem that happens year round. It's a great way to kill battery. That's also why if you leave you phone in a sock drawer, it's going to last longer than if it's in your pocket walking around.
Click to expand...
Click to collapse
well i left i think it was kj2 and flashed lb6 and i started using greenify hasn't really happened now
No to open another thread I have a Android backup issue any suggestions?
And power managed is on even though wifi is off
Sent from my SGH-T959V using xda app-developers app
I never got my phone to go into deep sleep when I selected ondemand (or maybe it was ondemandx). I would try a couple of the other governors & see if that would help.
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
OndemandX gives me good sleep, but forces the phone to minimum speeds when the screen is off. That tends to cause issues if I'm trying to use GPS or music without the screen burning.
As to what will work best... that depends on unique your phone, its apps, any tweaks that have been made, and your specific combination of scheduler/governor settings. I'm a fan of SIO, but sometimes the tweaks make that (and deadline) stick at max MHZ, in which case noop is great. At various times, I go with any of the SA2-based 'intelligent' options (SavagedZen, brazilianwax, SmoothAss, or SmartAssv2) or the OndemandX/Conservative basic sets. The others have gotten stuck more often and tended to allocate more processor than I think it needs.
I've always had the best luck with smartassv2. I think it's a good tradeoff between good battery life and quick processor speedups in order to prevent lag, plus I haven't had the issue of the processor locking up while the screen is off.
FBis251 said:
I've always had the best luck with smartassv2. I think it's a good tradeoff between good battery life and quick processor speedups in order to prevent lag, plus I haven't had the issue of the processor locking up while the screen is off.
Click to expand...
Click to collapse
That's usually the one I always fall back on too despite new ones all the time and everything, it's my default now on any ROM.