The phone takes like two seconds when waking up. I mean the screen doesn't wake up right after pressing the wake_drop buttons (home and power). It makes delay like about two seconds. Anybody got any clear explanation of this?
Custom or stock ROM? Lots of app running in the background?
Sent from my WT19i using xda premium
stock rom and I don't have a lot of apps running in the background. Maybe it's a kernel problem..
Its called CPU Scaling. Even if you don't have a CPU scaling/monitoring app, the CPU drops to 245Mhz when sleeping. So these 2 seconds happen because it takes a lot more time to start everything @245Mhz than it does @1024Mhz
If phone is stock, it should not have any problems with CPU scaling. Stock kernel can regulate CPU speed quite fast and should not have problems.
My CPU minimal is 122 MHz(max is 1 GHz), governor is ondemand and never had lag.
Also, CPU apps require root, in some cases also custom kernel.
Sent from my WT19i using xda premium
It's not a problem. It's how it works. The OP see's it as a problem from his perspective...
I am not seeing it as a problem. It's just my other android phones like hd2 take about 500ms to wake up. This phone takes about 1.5 seconds.
dumraden said:
ts called CPU Scaling. Even if you don't have a CPU scaling/monitoring app, the CPU drops to 245Mhz when sleeping. So these 2 seconds happen because it takes a lot more time to start everything @245Mhz than it does @1024Mhz.
Click to expand...
Click to collapse
[URL="http://forum.xda-developers.com/member.php?u=4473694" said:
Someguyfromhell [/URL];4473694]If phone is stock, it should not have any problems with CPU scaling. Stock kernel can regulate CPU speed quite fast and should not have problems.
My CPU minimal is 122 MHz(max is 1 GHz), governor is ondemand and never had lag.
Also, CPU apps require root, in some cases also custom kernel.
Click to expand...
Click to collapse
Thanks guys. You gave a clear explanation.
Oh, just to mention, I get wakeup lag sometimes also, why, I haven't found cause yet.
Related
I was curious... does SetCpu work for this phone like Milestone Overclock? What's the difference, aside from SetCPU having more options?
They are both free (well SetCPU only free for XDA), but everyone uses milestone OC here and I'm wondering if there's a reason for that.
syrenz said:
I was curious... does SetCpu work for this phone like Milestone Overclock? What's the difference, aside from SetCPU having more options?
They are both free (well SetCPU only free for XDA), but everyone uses milestone OC here and I'm wondering if there's a reason for that.
Click to expand...
Click to collapse
There is difference between two applications. Milestone overclock actually overclocks the processor while setcpu doesn't. Setcpu just changes clock frequency of CPU ranging from minimum to maximum. It allows you to make user profiles depending on which frequency of processor will be controlled. It actually helps battery last battery longer. BTW setcpu is paid application
SetCPU is used for setting CPU parameters. Like the range of mhz your CPU works at. Also setting profiles (CPU mhz when the phone is charging, reach temperature, battery lower than... etc.). But it cannot be used for overcharging, that's why we use Milestone overclock...
Sent from my XT720 using XDA App
jackfrost3821 said:
There is difference between two applications. Milestone overclock actually overclocks the processor while setcpu doesn't. Setcpu just changes clock frequency of CPU ranging from minimum to maximum. It allows you to make user profiles depending on which frequency of processor will be controlled. It actually helps battery last battery longer. BTW setcpu is paid application
Click to expand...
Click to collapse
Setcpu is free for XDA members bud, find it here
how should i adjust my advanced settings? im overclocked at 850mhz
LibertyMonger said:
Setcpu is free for XDA members bud, find it here
Click to expand...
Click to collapse
Thank you I wasn't knowing it is free for xda members!
I personally think Setcpu creates glitches in phone routine. Say when I play music and turn off the display, after I turn it on it pauses music a bit. I uninstalled it, problem seems to be no more. Still I can't confirm if the bug was created because of setcpu plus the battery life is not increased exponentially with setcpu.
Thanks for the answers
jackfrost3821 said:
I personally think Setcpu creates glitches in phone routine. Say when I play music and turn off the display, after I turn it on it pauses music a bit. I uninstalled it, problem seems to be no more. Still I can't confirm if the bug was created because of setcpu plus the battery life is not increased exponentially with setcpu.
Click to expand...
Click to collapse
I think I agree, lol. Android has it's own built in "Setcpu" it's supposed to do a good job on it's own. I have been using it lately and not really sure it is much of an advantage. I'm gonna go a few days without I think and see. Same with battery calibration, I use 3 backup batteries so if it works it really can't work properly when switching batteries but they all always seem calibrated the same whether I use it or not.
SetCPU works with msoc but it is more of a parameter setting app. Imagine if you were oc to 1200 all the time. That would be foolish bc your processor would burn up that is to say if you battery stayed charged long enough to do it. Im set at 1100/74 but I don't need it like that all the time. When my screen is off, why do I need it that high. I do bc I listen to alot of online media, MLB, Jango, Pandora, and if the screen is on it makes temp go up. I do, you may not need it that high. SetCPU allows me to set that parameter to adjust the CPU down and underclock it if I need to. Also if my battery is too hot, I don't need it to be fast as lightning compounding heat, so I set it for a specific temp and it underclocks when I hit it. Here is a screen shots to show my settings.
LibertyMonger said:
I think I agree, lol. Android has it's own built in "Setcpu" it's supposed to do a good job on it's own. I have been using it lately and not really sure it is much of an advantage. I'm gonna go a few days without I think and see. Same with battery calibration, I use 3 backup batteries so if it works it really can't work properly when switching batteries but they all always seem calibrated the same whether I use it or not.
Click to expand...
Click to collapse
Exactly that is what I've tried, uninstalled SetCPU to see the battery performance. It was really unnoticeable the battery drain with and without Setcpu. I use Autokill Memory Optimizer which seems to be providing good results as well as performance enhancement.
Nah that pause has nothing to do with setcpu. I get that all the time.
Sent from my Milestone XT720 using XDA App
exist2resist said:
Nah that pause has nothing to do with setcpu. I get that all the time.
Sent from my Milestone XT720 using XDA App
Click to expand...
Click to collapse
Yes it has to do with SetCPU if your minimum frequency is less. In screen lock profile select min frequency to 550Mhz instead of 250Mhz. Music won't pause while waking up your device. It works!
jackfrost3821 said:
Yes it has to do with SetCPU if your minimum frequency is less. In screen lock profile select min frequency to 550Mhz instead of 250Mhz. Music won't pause while waking up your device. It works!
Click to expand...
Click to collapse
I guess you are correct.
But currently I removed the SetCPU. And I see much better performance now. I was min at 250MHz. Even the quadrant score is much better now.
Thanks for your insight
I remove setcpu and do a comparison too. I'm using CM 7.1.0 of fjfalcon and it lasts 1.5-2 days with minimal usage on setcpu. Now let's see if it's barely unnoticable.
but I think set cpu to 250mhz during the night when you don't use your phone may prolong battery life.
Woodrube said:
SetCPU works with msoc but it is more of a parameter setting app. Imagine if you were oc to 1200 all the time. That would be foolish bc your processor would burn up that is to say if you battery stayed charged long enough to do it. Im set at 1100/74 but I don't need it like that all the time. When my screen is off, why do I need it that high. I do bc I listen to alot of online media, MLB, Jango, Pandora, and if the screen is on it makes temp go up. I do, you may not need it that high. SetCPU allows me to set that parameter to adjust the CPU down and underclock it if I need to. Also if my battery is too hot, I don't need it to be fast as lightning compounding heat, so I set it for a specific temp and it underclocks when I hit it. Here is a screen shots to show my settings.
Click to expand...
Click to collapse
Dude! with those settings what is your battery life like?
my minimum is at 125mhz and max at 250mhz (when screen off) and I lose 30% over night! and it barely lasts 8hours D:
what ROM are you on?
Do you guys know how the smartass governor works?
As I understand solution for "998 MHz with screen on" bug is found: http://forum.xda-developers.com/showthread.php?t=1225411&page=17#post16944722
We need to replace only one governor.
I don't want to play with different ROMs and kernels and I'm looking for simplest solution.
Is it possible to compile it as a module ("ondemand_mod" for ex.) and add it to stock ROM?
Or any other (simple) way?
Wrong section ...
Sent from my X10i using Tapatalk
Why wrong Section, this is Development to get the CPU Governor working correctly
Wolfbreak said:
Why wrong Section, this is Development to get the CPU Governor working correctly
Click to expand...
Click to collapse
Exactly, this is the right section for such request.
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
My_Immortal said:
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
Click to expand...
Click to collapse
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
As I see it's possible to compile and use governor as module.
Could someone compile it? And assemble as xRecovery package?
Or point me where to read about compiling for arm, where to get tools and so on...
Karlson2k said:
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
Click to expand...
Click to collapse
The thing is, on 245 MHz, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Xperia X10i via Tapatalk
My_Immortal said:
The thing is, on 245 MHz with high load, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Click to expand...
Click to collapse
There is no need to work on 245MHz as proper governor rise frequency automatically when it's necessary.
And really no stress for CPU to work an low frequency at full load. Moreover - CPU will consume more power at 500Mhz with 45% load than at 250Mhz with 95% load.
Sometime I use phone for navigation - long time with screen on and very low load. In this scenario battery drains very fast.
And last one - I like to have everything working properly. In case that I'll really need high frequency all the time I'll use other governor. I just want to have a choice.
I need a simple solotion for this too..I use z kernel and I found that Thego2s kernel fixed this problem..I was going to flash that kernel but think that has a bug and stoucks on logo ..can some one sayas a simple way?
Yes, I think a lot of people would prefer to use just small and simple fixes rather than replacing the whole kernel with a lot of nice but (personally) unnecessary features.
I am waiting for developers to release a fix for this problam
So ive been told that underclocking or undervolting might actually harm battery life instead of helping it by making the process slower before it completes.
What are the best set cpu settings for battery life?
If i decide I dont want to use setcpu how can i restore the default values?
Search for the setcpu thread by lennyuk.
All your answers are in there. Sorry don't have the link but you will find it. Think it might be in android development and hacking section??
Edit:
http://forum.xda-developers.com/showthread.php?t=1158102
Sent from my GT-I9100 using XDA App
digitallysick said:
So ive been told that underclocking or undervolting might actually harm battery life instead of helping it by making the process slower before it completes.
What are the best set cpu settings for battery life?
If i decide I dont want to use setcpu how can i restore the default values?
Click to expand...
Click to collapse
UC/UV/OC can harm your phone if not properly taken care of.
Each cpu is different so there is no 'best settings'. If i share my settings, it might not be stable in your phone, or may be you can undervolt more than me which means your cpu can handle lower voltages better than mine.
You can use an init.d script (if your kernel supports) or SetCpu or Voltage Control to overclock/underclock/undervolt.
First thing, search through kernel threads and find a kernel you think suits your taste best.
Next, using setcpu or voltage control, set a min and max global frequency.
Now for each frequency lower the voltage by 25 mv (from stock). Keep doing this until your phone becomes unstable or hangs. Use the last settings that didn't cause any problems.
I have a profile which works only at night
from 11pm to 6 am 500mhz with power save.
Once i tried 1000mhz conservative, for the whole day, does seem to give me more battery life at the end of the day.
ProNewb said:
I have a profile which works only at night
from 11pm to 6 am 500mhz with power save.
Once i tried 1000mhz conservative, for the whole day, does seem to give me more battery life at the end of the day.
Click to expand...
Click to collapse
Shouldn't the phone be in deep sleep (200mhz) at night? If you're not using it ofcourse.
TheSaw said:
Shouldn't the phone be in deep sleep (200mhz) at night? If you're not using it ofcourse.
Click to expand...
Click to collapse
Deep Sleep doesn't mean locking on to lowest frequency supported by kernel. (200 mhz on stock).
Deep sleep is the state where both cores shut off, and system (O.S) goes to sleep, governor stays idle, etc etc. There will be some background processes running too, but cpu is not using 200 mhz throughout deep sleep.
EDIT: Or you meant a screen off profile.
TheSaw said:
Shouldn't the phone be in deep sleep (200mhz) at night? If you're not using it ofcourse.
Click to expand...
Click to collapse
The phone should be in deep sleep, but some apps don't let the phone sleep at night thanks to there inefficient coding.
Anyway it does seem to use less battery, without this profile, I loose around 9% in 6 hours, but now I loose only 4-5%.
Sent from my GT-I9100 using XDA App
digitallysick said:
So ive been told that underclocking or undervolting might actually harm battery life instead of helping it by making the process slower before it completes.
What are the best set cpu settings for battery life?
If i decide I dont want to use setcpu how can i restore the default values?
Click to expand...
Click to collapse
just unistall setcpu and then reboot your phone and then you go back to default values
Ive been running the "cm7-1.4highpro-test-rev3" kernel and it runs great. I've been bumping up my undervolting slowly, and im at -475 at 216 mhz, which (in theory) should be the undervolt clock speed that will save me most battery becasue i have phone set to go between 216 mhz and 312 mhz when screens off. Ive got both 216 and 312 mhz undervolted extremely heavily and i haven't seen ANY issues. The rest of clock speeds are at -100 or so, and if i push much further than that the phone locks up and does weird stuff. This would lead me to believe that the undervolting IS indeed working. But can the processor really run at -475 @216mhz and [email protected] without any side affects?? I haven't once had it get stuck in sleep mode with screen off or ANYTHING, so im a bit unsure if it is actually undervolting or not.. Myrt undervolt shows that my phone is undervolted to the specific settings i set within SetCpu. I also havent seen much, if any, difference with battery life. With 10 hours of idle time, straight idle screen off whole time, wifi, gps, mobile data, 4g, bluetooth, all that stuff off and after 10 hours my battery is down to 85%.
I limited uv clocks, so there is a low limit. One day ill add more low end clocks but it won't matter because the photon uses a separate clock for suspend. I knew people would try to uv to 500 with it set on boot and screw there phone up. So this way I didn't have thousands of user error related uv issues. Uv does works but its more for high end than low end. Low end uv causes sleep of death.
w0lf215 said:
Ive been running the "cm7-1.4highpro-test-rev3" kernel and it runs great. I've been bumping up my undervolting slowly, and im at -475 at 216 mhz, which (in theory) should be the undervolt clock speed that will save me most battery becasue i have phone set to go between 216 mhz and 312 mhz when screens off. Ive got both 216 and 312 mhz undervolted extremely heavily and i haven't seen ANY issues. The rest of clock speeds are at -100 or so, and if i push much further than that the phone locks up and does weird stuff. This would lead me to believe that the undervolting IS indeed working. But can the processor really run at -475 @216mhz and [email protected] without any side affects?? I haven't once had it get stuck in sleep mode with screen off or ANYTHING, so im a bit unsure if it is actually undervolting or not.. Myrt undervolt shows that my phone is undervolted to the specific settings i set within SetCpu. I also havent seen much, if any, difference with battery life. With 10 hours of idle time, straight idle screen off whole time, wifi, gps, mobile data, 4g, bluetooth, all that stuff off and after 10 hours my battery is down to 85%.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
haha ok I understand, just thought I was going crazy there for a bit, or had the most amazing tegra 2 known to man. is there a way to UV the suspend mode then or no? And is my battery life at idle about average or low considering the UV. do you have any kernels for CM7 that aren't limited for UV? Thanks for reply, and all your hard work on the photon!!
Sent from my MB855 using XDA App
Changing suspend voltage can only be done in source. I havnt played with it yet because i need to test it on a stable kernel that way i know any issues would come from it. As far as extra uv steps its planned after wifi fix. I wont add 500 new steps probably 2 steps at a time(-25 steps). Im also planning on changing my clock table(multiples of 216 only). I might make a half step 1.0 kernel underclocked to 108~192. It will be mem underclocked and gpu/avp underclocked. With lower voltage tables on everything. Default scheduling will be powersave. Which you can check out with cpu master right now. That kernel will also have a tweaked 2 core start/stop.
w0lf215 said:
haha ok I understand, just thought I was going crazy there for a bit, or had the most amazing tegra 2 known to man. is there a way to UV the suspend mode then or no? And is my battery life at idle about average or low considering the UV. do you have any kernels for CM7 that aren't limited for UV? Thanks for reply, and all your hard work on the photon!!
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
"That kernel will also have a tweaked 2 core start/stop. "
Holy ****!
That would be the best thing
All new ones this week have tweaked 2nd core
DethMetalz69 said:
"That kernel will also have a tweaked 2 core start/stop. "
Holy ****!
That would be the best thing
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Im building a battery version of top secret now
Sent from my MB855 using XDA App
Just finally got around to rooting my USA SGP 5.0 yesterday and download SetCPU 2.24. I set the max clock to 400MHz but noticed that it would periodically jump up to 800MHz. Am I to conclude that it is not properly setting the max speed? ie. not doing anything at all?
thanks!
No, this is normal for this device. When you touch the screen, the driver or the kernel increase the speed to 800MHz, but when you let it go, it will jump back to whatever you set in SetCPU. The driver or kernel overwrites the settings, this is done by Samsung to increase the responsiveness of the device. There's nothing you can do about it.
Interesting... So I want to be able to set a profile so that when the screen is off, the max speed is 200MHz. I am assuming that listening to music does not require the CPU to be clocked at max speed. That said, do we know if the CPU automatically clocks down when not needed? If it does, then does that mean that SetCPU is doing nothing to help with battery life?
I don't know how well the CPU clocks down when not needed. Run some tests with and without caping the CPU and see what SetCPU shows you in terms of clock speed. I have SetCPU on my device because i like to set exact limits to my CPU and not rely on some algorithms to figure it out.
It seems to work whenever I switch the governer to ondemand. Conservative, not so often.
Sent from my YP-G70 using xda app-developers app
If you can buy tegrac overclock..you can undervolt any FQ and overclock how many you want.
Sent from my Nexus 7 using xda app-developers app
Nevermind... I just uninstalled SetCPU. I had set it to max out at 400MHz. I surfed the web for a while and then watched youtube for 1.5 hours and noticed that I dropped from 70% to 45% battery life. I've never seen my battery drain so fast, even when watching full movies. I might give Tegrak a try but I think I'm done with SetCPU for now...