Just as the title says, but here's some more details.
I have my cpu set to 1.1Ghz during the normal day 245Mhz min.
I have my widget on my homescreen and a custom profile set for when the screen is off for 368max and 245min.
When I turn my screen on and unlock it, it lags on my screen and says 368 max, then it jumps to the 1.1 and everything is fine.
It seems to lag there longer than it used to, has anyone else noticed this problem.
I used to have Pershoots Kernel on 6.1, do you think if I put Pershoots Kernel back on it will eliminate the lag and switch to 1.1 faster than it does now?
Just some thoughts and advise would be great, thanks guys.
Sent from my HTC Vision using XDA App
I would ditch setCPU and use CM's built in overclocking settings. set your clock speed to whatever you like and use the ondemand governor.
your screen wake lag will almost certainly disappear and I bet your battery life doesn't change a bit. you can play around with it, of course, and find what's best, but I have found that since CM introduced built-in overclocking, it is more functional to use it instead of setCPU. my battery life hasn't changed a bit, partly because when the phone is in an idle state it is underclocked by default, and also because I don't have setCPU constantly having to think to make changes to my clock speeds and governors based on what profiles I've set up.
Related
so im currently running MCK 2.2 rom with the updated kernel but without compcache enabled because i havent been able to get it working yet.
here's the problem though, about once a day my phone will slow down to an unberable speed... just like it used to with the OEM Rom.
when I open up SetCpu (which i know isnt supposed to do anything on the hero) it tells me that my CPU is running at 245mhz, but the control bars in SetCPU are set for 528/480mhz... when i hit refresh the phone comes back up to 528/480 and its fast(er) again...
anybody have any ideas on this one?
dmc971989 said:
so im currently running MCK 2.2 rom with the updated kernel but without compcache enabled because i havent been able to get it working yet.
here's the problem though, about once a day my phone will slow down to an unberable speed... just like it used to with the OEM Rom.
when I open up SetCpu (which i know isnt supposed to do anything on the hero) it tells me that my CPU is running at 245mhz, but the control bars in SetCPU are set for 528/480mhz... when i hit refresh the phone comes back up to 528/480 and its fast(er) again...
anybody have any ideas on this one?
Click to expand...
Click to collapse
What gov. are you using on setcpu?
theoottesen said:
What gov. are you using on setcpu?
Click to expand...
Click to collapse
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Similar problem...
dmc971989 said:
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Click to expand...
Click to collapse
I have a similar problem. I experience serious slowdowns (compcache enabled or disabled) about once per day. I have not verified the CPU speed as I'm not using SetCPU. I am using the "performance" governor in MCK.
My typical solution is a reboot.
im just curious if this is the original problem or a new one cause by this rom setup... because I dont ever recall reading anything about the CPU getting stuck at 245mhz from sleep mode being the source the slow downs....
Have you tried disabling the location services to verify it's not that particular bug you're seeing/experiencing?
x99percent said:
Have you tried disabling the location services to verify it's not that particular bug you're seeing/experiencing?
Click to expand...
Click to collapse
yes, i keep them disabled...
jamesthomas128 said:
I have a similar problem. I experience serious slowdowns (compcache enabled or disabled) about once per day. I have not verified the CPU speed as I'm not using SetCPU. I am using the "performance" governor in MCK.
My typical solution is a reboot.
Click to expand...
Click to collapse
I look in the kernel and there are two sets of settings: The profiles and a set of setting for the kernel speed (this is split into min/max for screen on and min/max for screen off)
For screen on, it is set for 480000 min/528000 max
For screen off, it is set for 245760 min/245760 max
If the screen is off, it's possible that the kernel went into the lower settings and didn't come back.
I've heard different reports on whether the profiles work in the Hero. I'm curious myself. I do know the stock rom has everything locked, but since the kernel source has been released and Modaco released his kernel, I'm not so sure if the lock statement is true anymore.
I'm compiling a kernel as we speak with the cpu frequency scaling on. Had some issues with the cpufreq.h file not seeing two variables necessary for the userspace profile, but hopefully I was able to fix that (won't know until I run it).
tkirton said:
I look in the kernel and there are two sets of settings: The profiles and a set of setting for the kernel speed (this is split into min/max for screen on and min/max for screen off)
For screen on, it is set for 480000 min/528000 max
For screen off, it is set for 245760 min/245760 max
If the screen is off, it's possible that the kernel went into the lower settings and didn't come back.
I've heard different reports on whether the profiles work in the Hero. I'm curious myself. I do know the stock rom has everything locked, but since the kernel source has been released and Modaco released his kernel, I'm not so sure if the lock statement is true anymore.
I'm compiling a kernel as we speak with the cpu frequency scaling on. Had some issues with the cpufreq.h file not seeing two variables necessary for the userspace profile, but hopefully I was able to fix that (won't know until I run it).
Click to expand...
Click to collapse
im fairly positive that the CPU is getting stuck in the sleep mode while the rest of the phone is not, causing me these issues... the problem is i dont know how to fix them
dmc971989 said:
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Click to expand...
Click to collapse
Ok, modaco rom sets the governor to "performance" on boot. This essentially "sticks" your CPU to max throttle.
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Will tell you where you are, governor wise..
I'm not entirely sure what setCPU does, I've never used it, but I assume it just tweaks your top and bottom Mhz and maybe changes governor to performance when the screen is on? If it's configured properly? Maybe not, who knows?
If you want the best battery life, put the governor back to msm7k, it's a custom governor modified by HTC to make your battery last longer.
I changed the following line in modaco.sh:
echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
to:
echo "msm7k" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_govern
and haven't noticed any slowdown from it.. my battery is lasting longer than it did on Stock or Fresh 1.1...
Currently running VillainROM 10.3.0 (with Sense UI)
Does anyone get problems regularly on the slightest of underclocking (using SetCPU)?
Min at 245:
- Alarm wont turn off (only snoozes)
- Clock on Lock screen wont update
Min at 128:
- Music player becomes stuttery, took a few minutes for screen to power on to turn off music
Noone else seems to have mentioned it ?
Am I doing something wrong?
And its a bit worrying considering so many custom ROMs come pre-clocked.
Totally a hardware issue. Your phone just can't cope with the lower speeds. Not all can.
Mine will do 19mhz on sleep and wake immediately etc. but most others won't
Villainrom should default to the stock settings unless you install something like setcpu and define oc settings.
Not sure about other roms but I guess they do similar unless otherwise stated.
ah cheers.
i knew that some phones couldnt reach a particular Max clock speed, but didnt know it was a similar case with the Min clock speed too
You should try Cronos Droid. I am having the exact same problem as you on all OC'ed 2.1 roms, except Cronos Droid.
My settings on Cronos:
Screen on: 710 mhz
Screen off: 160 mhz
this may be posted in the wrong section but i would like everyone running froyo to test this out
HERE IS THE LINK TO GET THE LATEST SETCPU
http://forum.xda-developers.com/showthread.php?t=505419
So I have been doing some experiments on ways to save battery life....I think i have made a break through it is not fully tested i would like for some of you to try it out.
with the latest updates to your ROM itself, setcpu, superuser, and the addition of cache cleaner and the incredible AUTOKILLER (a must have) i have been able to run extremely low setcpu sleep profiles without any noticeable loss of performance.
Believe it or not i have my sleep profile down clocked to 19200mhz with out "noticeable" performance loss
i would like for some of you if possible to try these profile out for a while and see how it works out for you
DEFAULT 480min---whatever you want max (mine is 787) ondemand (for performance)
OR DEFAULT 245min---whatever max (for even more battery savings)
SLEEP 192min---480max ondemand (works great even without sleep to wake lag)
it works dont believe me then check out set cpus new feature "time in state"
open setcpu
go over to info
scroll down a little and you will see the times in state your phones cpu runs in the most
you should now see values at the lowest state of 19200
if this works in theory we can benefit from longer battery life
and faster charging
please try these out and report back to the post or PM me...this could be good
Thanks
UPDATE 8/22 EDIT: some users are having success running an even lower default 19min--whatever max (thats even more savings) will be looking into it
try these even lower profiles
DEFAULT 122min--whatever max (screen ON cpu does not drop below 122mhz)
Screen OFF 19min--245max (no lag just ran pandora and cardio trainer at the same time here no lag from sleep to wake either)
or Screen Off 19min--480 max for more performance
REMEMBER not to have conflicting profiles and to have SCREEN OFF at your highest priority
please post here your own findings and results
Thanks again
UPDATE 08/24/2010
after experimenting with other speeds i have finally settled on these speeds for my personal taste on performance and battery savings
MY FINAL SETTINGS...
DEFAULT 19MIN---786 or whatever MAX on demand
SCREEN OFF 19MIN---480 MAX on demand (highest priority) think deeply about why this is the highest
TEMP <40 19MIN---528MAX (screen off overrides this which cools anyway)
BATT <40 19MIN---604MAX
next more into advanced settings....coming soon
UPDATE 08/26/2010
im almost at the holy grail here
try this set up
SCREEN OFF 19--480 (95 priority)
TEMP <40 19--580 (90 priority)
ADVANCED SETTINGS
SAMPLING RATE---100000
UP THRESHOLD---98
ignore nice ---0
power save bias---0
hit apply (if you like it check set at boot)
ALL CPUS ARE NOT CREATED EQUALLY WE ALL KNOW THIS SO DONT EXPECT MY EXACT SETTING TO WORK FOR EVERY SINGLE PHONE
I CAN ONLY OFFER A STARTING POINT BUT ITS UP TO YOU TO TWEAK IT BUT ITS WORK
I HOPE THIS HELPS
things to notice....
in the main screen in setcpu watch the main frequency values bounce up and down...after a few seconds the values seem to stabilize at the lowest frequency of 19
in time of state screen even when screen on most of the time the 19 freq get the most values
i need a few guys to run, test and monitor the values that i just posted ^^^HERE^^^
this may further the battery life once we stabilize the frequency to 19 most of the time while keep the SAME performance which i think i may have did
run some linpacks and quadrants with those setting
i got
5.4 linpack running 787max
431 quad running 787max
then it drops back to 19 and stabilizes
hope this works and please post all your feed back and setting so we can learn this and get it perfect
thanks
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
thisisreallygay said:
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
Click to expand...
Click to collapse
19 is even lower try it
Oh 19200? Wow I wasn't paying attention well enough. I'll try it.
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
I wonder what it's like when receiving a call. I just set it and I'm not having any lag with just turning it on or anything. I'll test it out with other things. I hope this greatly improves my battery.
roirraW "edor" ehT said:
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
Click to expand...
Click to collapse
shame on you for keeping that secret all to yourself
SHAME
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Search for it on his website, idk what his website is you'll have to search for it. Or download a ROM with it already in it.
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
thisisreallygay said:
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Click to expand...
Click to collapse
hmm last time i was on sense rom sense fell apart if you clocked lower than 245
epically receiving a phone call
but i only test this method on froyo
I've heard that too. Although I don't know what is bad about it.
sh_mohanna said:
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
HERE
http://forum.xda-developers.com/showthread.php?t=505419
eklipze said:
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
Click to expand...
Click to collapse
i heard that too but all froyo dev have a 245 to 710 stock on their roms
thats why i kinda spilt the two profiles and why 245min--- is experimental
leave your screen off for a while and see if the ime of state shows up
also make sure not to have conflicting profiles running in setcpu
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
thisisreallygay said:
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
Click to expand...
Click to collapse
oh ok tainted is not vanilla
tainted IS sense with sense removed with vanilla remaning hence the word tainted
some sense is still there
i think
Yeah it's got sense contacts and stuff but vanilla messaging. But it has the sense dialer so I think it would also have lag with calls if the sense ones were having lag. And I just tested it and it took a lil while for it to recognize whose number it was but it still gave me plenty of time to answer the call. I'll be testing to see how it improves battery. Thanks for the find
Im also testing setcpu Advanced settings batery life (without performance loss)
What settings are those?
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off
rjmjr69 said:
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off
Click to expand...
Click to collapse
I'm running Baked Snack 1.1, doesn't matter what rom or kernel I use though, it still happens.
It doesn't matter if I use overclock widget or SetCpu, if I were to set it so that my phone underclocks to 200mhz or 400mhz while the screen is off it freezes and I have to pull the battery.
Same here im running stock and i've tried setcpu and no matter what i hav to pull the battery out everytime. So i uninstalled it.
Sent from my Epic 4G
I had the same problem set the cpu with min of 400 and max off 800 should fix your problem
Sent from my SPH-D700 using XDA App
It means that there is not enough voltage run that frequency on your phone. Some times these kernel developers undervolt the phone which all phone don't support at all. Try some other kernel like the xtreme kernel. That kernel actually work for me and I can underclock my phone without freezing.
rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience
murso74 said:
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience
Click to expand...
Click to collapse
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.
I'm running Baked Snack 1.3 and found it to be stable at 1.2ghz using OC Widget. With screen on I have it set to min 400 and max 1200. With screen off it's set to min 400 max 600.
I too am having this problem. No mater what rom or kernal I use. It seems as if Setcpu and Overclock widget sometimes cant read the frequencies and let the phone underclock to 19.2Mhz which is probably like trying to wake the dead!
I wonder if it has anything to do with the new Superuser.apk? it always seems like setcpu is trying to get permissions. Maybe, I dont really know. Can one of you really smart people look into this?
In the meantime the only profile that I have set is screen off Max 800 Min 400, maybe that will work?
same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.
What i've gathered over the last several months, is that SetCPU profiles are buggy with our phone. Its recommended not to use profiles.
I'm fairly certain that SetCPU should not be used without a custom kernel that allows for over/under clocking. If you're on the latest ViperROM then you are using a kernel that we have no source code for, therefore it doesn't support over/under clocking; rendering SetCPU useless and prone to cause problems.
mattallica76 said:
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.
Click to expand...
Click to collapse
My SetCPU is using conservative and I haven't had any problems so far. I am running BonsaiROM 1.14.
jemarent said:
same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.
Click to expand...
Click to collapse
If you have it set to under 200 with the screen off it won't wake up after a while.
I've had the same problem on all builds and ROMs that I've used. The only constant through all the different setups I've used were Advanced Task Killer and SetCPU. I stopped using ATK (with auto-kill on screen off, I use EStaskmanager for manual killing when phone is on) and the problem seems to be mostly fixed. It does still happen once in a blue moon though, say once every day or two.
Phoenix Kernel/Syndicate ROM 2.1
SetCPU: 100min/1200max
Screen off: 100min/200max
Batter < 30%: 100min/600max
I tried to search for a thread relating to this but couldn't find anything, if anyone knows of one a link would be appreciated.
OK, so I flashed Motleys kernel 2 days ago. Everything was running fine, I had it OC'd to 1.6 and it was super fast and smooth. I had set the governor to "on-demand" to try and save some battery life(over "performance"), and also because it seemed like the CPU would run at full 1.6 constantly if it was set to performance (I don't know if that's how it should be or not, but this isn't the issue). I used System Tuner to OC it like he recommended in his thread.
Yesterday I set it to performance to run some benchmarks, and then continued using it on performance to see how it felt. About an hour and a half later I also started messing with my home screen and apps and ended up accidentally using Quick Boot to take me to the bootloader. After powering it back on I checked System Tuner to set the governor and once I did I noticed, according to System Tuner, that 2-4 of the cores are running at full 1.6 and the CPU usage is from 25%-100% even though I have nothing open.
I flashed my recovery via Clockworkmod Recovery, Motleys kernel is now replaced by the stock kernel, however I'm still having the same issue, but just at 1.3. Any idea why the CPU is running so high, for apparently no reason?
.....
OK, so I just checked System Tuner again and the CPU doesn't seem to be doing as bad now, but it's still all over the place and I don't have anything else open. Here are the times:
Offline - 77%
340MHz -11%
475Mhz 1%
1.2Ghz - 5%
1.3Ghz - 1%
Compared to yesterday when it had said 1.3GHz 79% or something like that (and was running nothing but system tuner).
So, yeah, that does seem a lot better but one thing remains; the CPU usage still jumps up to almost 50% and once again, I am running nothing but System Tuner, so something still doesn't feel right.
I think ondemand governor is causing the CPU to shoot up so often and quickly.(That's all I can think of.) I always use interactive and it's usually the preferred governor. Ondemand is more for people who play lots of games and they need the extra boost. If you game a lot then I guess you should still to it.
Sent from my Nexus 4 using Tapatalk 2