So I'm running baked snack here and really beginning to enjoy it and this whole root thing. I've installed setcpu but every time I back out of the interface it goes down to 691 no matter how high I set it or on any profile. Does this not work with baked snack? Am I overlooking something or did I set it up wrong(I used auto detect when I started)?
Did you flash a different kernal?
Sent from my PC36100 using XDA App
Nope I flashed kernel 3 I think or what ever came included in the baked snack.
should I DL that kernel by itself and then flash over the Baked snack with it? and whats the difference between flash over and flash ontop of?
Damn the stupidity of it all... lol. I set my profile to 691 if my battery was under 40% which it was... but now when I plug my phone in the cpu goes up to 1ghz which I have it set to but my battery keeps going down. Now this is a problem here if I'm not able to charge my phone while the setcpu is running it will get really annoying really fast. Considering the app manager that I have refuses to close it so I have to manually go to settings > applications > manage applications then go to setcup and force close it to charge my phone it seems. Do you guys think its a problem with my cpu being set to high while charging should I drop it down a whole bunch for the charge process too? That doesn't seem like a very needed thing to do I would assume it would be able to charge just fine without that. Looks like I got a lot to learn about this whole rooted phone thing.
Check your profiles in setcpu and make sure you don't have one that's at that speed with the highest priority. If that all checks out fine I would flash kernal 2 (my favorite) don't wipe just flash. And as for your question over or on top they mean the same thing and that's flashing the kernal without wiping.
Sent from my PC36100 using XDA App
Also do you have overclock widget running as well? If so they might be fighting eachother
Sent from my PC36100 using XDA App
not even quite sure where the overclock widget is. I looked to see if setcpu had a widget and it wasn't in the widget menu. Where as most of my other installed apps have a widget assossiated with them. I'll look into kernel #2 right now, I still have some more flashing to do.
crimeslunk said:
not even quite sure where the overclock widget is. I looked to see if setcpu had a widget and it wasn't in the widget menu. Where as most of my other installed apps have a widget assossiated with them. I'll look into kernel #2 right now, I still have some more flashing to do.
Click to expand...
Click to collapse
Overclock widget is just another widget you can download that runs seperatly from SetCPU. You should have a SetCPU widget though. I would try reinstalling SetCPU also
Related
[Q] cm7 cpu setting or setcpu?
well atm i am running an evo 4g with cm7 and i just switched my kernel to savaged zen and it's running great. my phone was rebooting on its own w/ the regular cm7 kernel i think its b/c i was using setcpu and people are saying it messes up cm7.
so i was wondering if anyone knew if i can use setcpu with cm7 and savaged as the kernel or if it's possible to make profiles on the cpu settings on cm7 i saw some1 post somewhere that you can but they never explained how.
p.s. please also visit this thread on battery life
AFirst of all, all SavagedZen kernels are Havs kernels (as far as I remember, I'll double check in a few). Anyway, if you are using a Havs kernel, changing cpu settings is pointless/counteractive. I would either leave the settings alone or switch to a no-havs kernel. You can check in settings>about phone.
EDIT: However, if you must mess with the settings, you can find them in Cyanogenmod Settings under Performance Settings. I don't know of a way to set profiles from that screen, though - only max/min & governor.
hi i have an evo running cm7 and i had setcpu and my phone kept restarting however i looked up setcpu again in the market and it said that they just ran an update to stop the problem with cm7, does this mean that setcpu is better to use than the cpu setting in cm7?
Green_Arrow said:
hi i have an evo running cm7 and i had setcpu and my phone kept restarting however i looked up setcpu again in the market and it said that they just ran an update to stop the problem with cm7, does this mean that setcpu is better to use than the cpu setting in cm7?
Click to expand...
Click to collapse
You shouldn't need setcpu use the cpu setting in cm7. They put it there for a reason, those guys are sharp!
I still use setcpu because I like my screen off profiles etc. You should update your setcpu if it prompted you to. I think the latest changes were for cm7/GB.
Sent from my PC36100 using XDA Premium App
Yes but it doesn't let u make profiles unlike setcpu, or does it?
I believe the profiles is definately the most useful
Sent from my PC36100 using XDA Premium App
It says it was for cm7
Sent from my PC36100 using XDA Premium App
I believe the SavageZen governor is a specially tweaked/optimized version of the SmartAss governor.
And if you use Smartass/SavageZen governor, I think it also automatically undervolts when sleeping, and essentially mimics what a screen-off profile in SetCPU would do.
plainjane said:
AFirst of all, all SavagedZen kernels are Havs kernels (as far as I remember, I'll double check in a few). Anyway, if you are using a Havs kernel, changing cpu settings is pointless/counteractive. I would either leave the settings alone or switch to a no-havs kernel. You can check in settings>about phone.
EDIT: However, if you must mess with the settings, you can find them in Cyanogenmod Settings under Performance Settings. I don't know of a way to set profiles from that screen, though - only max/min & governor.
Click to expand...
Click to collapse
but how exactly does havs control battery usage? and if i use setcpu wouldn't the havs not function only setcpu will function b/c of priority?
serdna75 said:
I believe the SavageZen governor is a specially tweaked/optimized version of the SmartAss governor.
And if you use Smartass/SavageZen governor, I think it also automatically undervolts when sleeping, and essentially mimics what a screen-off profile in SetCPU would do.
Click to expand...
Click to collapse
how do u use Smartass/SavageZen governor?
Threads Merged... please post your question once.
Green_Arrow said:
how do u use Smartass/SavageZen governor?
Click to expand...
Click to collapse
In CM Settings, go to Performance Settings & then CPU settings. Under available governors choose SavagedZen or Smartass. I'd try them out & see which you like the most. I prefer SavagedZen, I seem to get better battery life & performance.
egzthunder1 said:
Threads Merged... please post your question once.
Click to expand...
Click to collapse
Thanks, sorry its my 2nd day on this forum
plainjane said:
In CM Settings, go to Performance Settings & then CPU settings. Under available governors choose SavagedZen or Smartass. I'd try them out & see which you like the most. I prefer SavagedZen, I seem to get better battery life & performance.
Click to expand...
Click to collapse
thanks atm im using the savagedzen, and jw is autokiller memor optimizer useful now or not?
Green_Arrow said:
thanks atm im using the savagedzen, and jw is autokiller memor optimizer useful now or not?
Click to expand...
Click to collapse
Personally I have never needed a task killer while on CM7, so I am going to recommend against it.
Well I had talked to someone else that is using it like that and they said they get amazing battery life
Sent from my PC36100 using XDA Premium App
I say no toward any kind of task killer. First of all, they're pointless. You're killing stuff that isn't using any power to begin with, which then restarts anyway. The task killer itself is actually doing something, running on a set schedule, where as the tasks you're killing are just sitting in memory for faster opening.
It bugs me that even the techs at Sprint recommend it, so every person that doesn't know anything about how their phone works thinks it's necessary. Then in the market for every clock widget you see everyone going "like zomg the clock doesn't keep time your app sucks 1*" because the damn task killer is killing it. That's if they can even figure out how to use it & not complain that it "won't open", despite clear instructions on how to put a widget on your screen.
Sorry, totally went off on a rant there.
But yeah, stay away from task killers & let Android do its job. You don't have to have a ton of memory free for your phone to run perfectly fine under normal usage. I don't notice a difference between 300mb & 50mb free. If you don't worry about it, you won't either.
Free memory does not equal more battery.
plainjane said:
I say no toward any kind of task killer. First of all, they're pointless. You're killing stuff that isn't using any power to begin with, which then restarts anyway. The task killer itself is actually doing something, running on a set schedule, where as the tasks you're killing are just sitting in memory for faster opening.
It bugs me that even the techs at Sprint recommend it, so every person that doesn't know anything about how their phone works thinks it's necessary. Then in the market for every clock widget you see everyone going "like zomg the clock doesn't keep time your app sucks 1*" because the damn task killer is killing it. That's if they can even figure out how to use it & not complain that it "won't open", despite clear instructions on how to put a widget on your screen.
Sorry, totally went off on a rant there.
But yeah, stay away from task killers & let Android do its job. You don't have to have a ton of memory free for your phone to run perfectly fine under normal usage. I don't notice a difference between 300mb & 50mb free. If you don't worry about it, you won't either.
Free memory does not equal more battery.
Click to expand...
Click to collapse
but doesn't free memory mean less things are running or even being used just a tad bit which does mean a better battery life?
Green_Arrow said:
but doesn't free memory mean less things are running or even being used just a tad bit which does mean a better battery life?
Click to expand...
Click to collapse
No. Memory has nothing to do with battery.
Screen, radios, and CPU use battery and that's about it.
Sent from my PC36100 using XDA App
matt2053 said:
No. Memory has nothing to do with battery.
Screen, radios, and CPU use battery and that's about it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
So do u agree w/ system panel/juice defender?
Sent from my PC36100 using XDA Premium App
I'm using the virus rom airborne rc6 and the netarchy 4.3.4 kernel. I went to the app market and downloaded the overclock widget since I had used it on another evo. Whenever I set it up or go to set it up I should say the phone locks up and requires a battery pull. Start the phone back up and it freezes again on the lock screen not allowing you to use it. A restore or wipe is required. I was thinking it was the Rom or kernel so I downloaded valpeak Rom and a kernel and it did the same thing on it. Just wondering if anyone had heard seen or experienced something like this before ? Is there another over clock program that's good and stable ?
Thanks in advance
Virus Rom airborne rc6
Netarchy toastmod kernel
jshaddix865 said:
I'm using the virus rom airborne rc6 and the netarchy 4.3.4 kernel. I went to the app market and downloaded the overclock widget since I had used it on another evo. Whenever I set it up or go to set it up I should say the phone locks up and requires a battery pull. Start the phone back up and it freezes again on the lock screen not allowing you to use it. A restore or wipe is required. I was thinking it was the Rom or kernel so I downloaded valpeak Rom and a kernel and it did the same thing on it. Just wondering if anyone had heard seen or experienced something like this before ? Is there another over clock program that's good and stable ?
Thanks in advance
Virus Rom airborne rc6
Netarchy toastmod kernel
Click to expand...
Click to collapse
You need to clock it at a lower maximum speed. Some chips can't handle overclocking as well as other chips can. My phone can only be overclocked to like 1.1, and anything over that, I have the same issues you are explaining. Set the maximum speed a little lower and see if that helps.
That's just it when I try to set it up it freezes. I contacted the developer of the app and they said its on my end. I used the valpak before and could clock to 1.2 I'm wondering if there isnt something wrong with the kernels lime maybe they did a software update on the app and it doesn't agree with Rom or kernel. I've heard good things about set cpu I may try it. Thanks for your help
jshaddix865 said:
That's just it when I try to set it up it freezes. I contacted the developer of the app and they said its on my end. I used the valpak before and could clock to 1.2 I'm wondering if there isnt something wrong with the kernels lime maybe they did a software update on the app and it doesn't agree with Rom or kernel. I've heard good things about set cpu I may try it. Thanks for your help
Click to expand...
Click to collapse
Yeah I know what you mean, you just gotta hurry and get into the app and lower the max speed before the app gets superuser permission and freezes again. Or if you have the SDK on your pc and know how to use adb, you could remove the app from the phone while connected to a pc in recovery. Also, I use setCPU, and I've had nothing but good experiences with it. I've never used Overclock widget so I can say anything about it.
try flashing a different kernel its happened to me before and thats what i had to do then i changed the max and flashed back to the other kernel
re
Leukay said:
Yeah I know what you mean, you just gotta hurry and get into the app and lower the max speed before the app gets superuser permission and freezes again. Or if you have the SDK on your pc and know how to use adb, you could remove the app from the phone while connected to a pc in recovery. Also, I use setCPU, and I've had nothing but good experiences with it. I've never used Overclock widget so I can say anything about it.
Click to expand...
Click to collapse
Thats how i fixed it. I ended up using the computer to remove the app and used setcpu. I normally dont care about the over clocking ability but the battery life sucks on the virus Rom. The roms great just crappy battery life. Thankfully that worked we will see if by underclocking it helps if not ill have to look for a different Rom. Thanks for your help man.
I installed the latest Virtuous 1.0.2 rom with the latest advanced kernel and before I can even open up the setcpu app, my screen is completely unresponsive. I'm guessing that means my phone can't handle 1.51GHz? I wanted to tone it down to 1.2ish, but can't even get into the app.
Download cpu tuner and change it back to 806. Ur phone is running at 1.5 now and that's what's messing up.
Sent from my HTC Vision using XDA Premium App
ericc191 said:
I installed the latest Virtuous 1.0.2 rom with the latest advanced kernel and before I can even open up the setcpu app, my screen is completely unresponsive. I'm guessing that means my phone can't handle 1.51GHz? I wanted to tone it down to 1.2ish, but can't even get into the app.
Click to expand...
Click to collapse
open up the file information for setcpu, tap force stop, tap clear data, uninstall.
then reinstall setcpu and reset the clock speed to something that wont destroy your cpu in 2 months.
mputtr said:
open up the file information for setcpu, tap force stop, tap clear data, uninstall.
then reinstall setcpu and reset the clock speed to something that wont destroy your cpu in 2 months.
Click to expand...
Click to collapse
Yeah I don't want to fry this phone lol. It's supposed to be my backup and that means a good 2 or 3 years. In any case, I think I'll just stick with 1.2GHz for awhile. Are MoDaCo roms still considered top notch for something simple, clean, and fast?
I froze all of the DRM services as shown in the picture below, yet it is still hogging battery resources as shown below.
Does anyone know how this is possible and how to fix this?
I'm using SleeperRom 1.0.11 and Shadow Kernel 1.03+.
Thanks.
That doesn't help. Percentages don't mean anything. ALL your applications have to run through android system. Take off android from your phone and you can't run anything. To see what is using your battery check Betterbatterystats. What files have the most time on them? Check processes and partial wakes if your battery drains while your phone is in standby. Also get CPUSpy and make sure your phone goes into deep sleep when in standby and not on charge.
Just because it lists DRM in the android system does not mean it is using more than a second or two of quick checking services. This is why some apps screw up if it is removed instead of just frozen. It has to check if the files are still on your phone.
Thanks, i'll try that app. I assumed that since it was at the top, it was using the most. Since updating to SleeperRom 1.0.11 and Shadow Kernel 1.03+, my battery does not seem to be as good even though I have not changed the way I use my phone. This is why I was investigating.
after checking betterbatterystats, I don't even see the DRM service anywhere within the app, so I guess that is good.
I guess my phone just doesn't agree with the update to sleeper 1.0.11 and shadow 1.03+
akuentzler said:
Thanks, i'll try that app. I assumed that since it was at the top, it was using the most. Since updating to SleeperRom 1.0.11 and Shadow Kernel 1.03+, my battery does not seem to be as good even though I have not changed the way I use my phone. This is why I was investigating.
Click to expand...
Click to collapse
I have not tried that combo but is there a default overclocking setting? I tried SleeperROM before and it defaulted to 1100 Mhz overclock. If you came from a ROM with no OC set then that would explain it.
kennyglass123 said:
I have not tried that combo but is there a default overclocking setting? I tried SleeperROM before and it defaulted to 1100 Mhz overclock. If you came from a ROM with no OC set then that would explain it.
Click to expand...
Click to collapse
I usually don't touch the overclock settings and I always to do clean wipe when installing my roms, so whatever is default should stay.
voltage control is set to conservative, min 100, max 1000 Mhz.
akuentzler said:
I usually don't touch the overclock settings and I always to do clean wipe when installing my roms, so whatever is default should stay.
voltage control is set to conservative, min 100, max 1000 Mhz.
Click to expand...
Click to collapse
If you set that as apply on boot after the wipes if you mean data wipe, and install then it should be 1000 max. Easiest way is just check CPUspy. Have you changed brightness on your display? Did the ROM add any apps like Gtalk with video that you didn't have before that may need to be frozen? Definitely get Betterbatterystats and check what's running.
kennyglass123 said:
If you set that as apply on boot after the wipes if you mean data wipe, and install then it should be 1000 max. Easiest way is just check CPUspy. Have you changed brightness on your display? Did the ROM add any apps like Gtalk with video that you didn't have before that may need to be frozen? Definitely get Betterbatterystats and check what's running.
Click to expand...
Click to collapse
I think the major difference is the shadow kernel and the use of voodoo color. I was previously on samurai 2.0.6 or 2.0.8 i think.
I have always had auto brightness on. Betterbatterystats did not reveal anything out of the ordinary.
I guess i'll just try a new rom/kernel combo and see if I can get better results. Thanks for your help Kenny. Betterbatterystats is a nice tool i had not known about.
No problem. I did find that voodoo color and the voodoo control app use a little extra battery plus having to increase brightness a little with voodoo color used up a little more battery.
Sent from my SPH-D700 using XDA App
Is anyone having problems with setcpu on any of the ICS leaks or cm9? My phone just freezes up upon boot and has to essentially be redone for the phone to boot. The second setcpu runs, my phone locks up. I have a screen off profile with max at 800mhz. I also tried it without the screen off profile. I have decided to hold off with the app until it is more stable.
Sent from my SPH-D710 using Tapatalk
dtruong23 said:
Is anyone having problems with setcpu on any of the ICS leaks or cm9? My phone just freezes up upon boot and has to essentially be redone for the phone to boot. The second setcpu runs, my phone locks up. I have a screen off profile with max at 800mhz. I also tried it without the screen off profile. I have decided to hold off with the app until it is more stable.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I have setcpu with screenoff and in call set at 800 mhz and no issues. I'm suspecting something with your kernel perhaps or maybe just a bad flash?
Alternate
dtruong23 said:
Is anyone having problems with setcpu on any of the ICS leaks or cm9? My phone just freezes up upon boot and has to essentially be redone for the phone to boot. The second setcpu runs, my phone locks up. I have a screen off profile with max at 800mhz. I also tried it without the screen off profile. I have decided to hold off with the app until it is more stable.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Same problem, I have official ICS Rom for Galaxy S2 and several programs are freezing my phone when trying to overclock (or lowerclock). The only program working good for me is "No Frills"
Same here. I had to get rid of set cpu bcuz it would freeze the phone. Now i just have tegrak and i wish it had profiles...
Sent from my SPH-D710 using XDA
I have the same problem, tried setcpu on miui ics, cm9, custom ics roms, it freezes my phone on all ics based roms?
It gives problems on GB as well, and freezes my phone. I suspect its the new version.
My experience was the opposite. I kept freezing with tegrak (free).
I bought ultimate, and havent froze yet. Got profiles so its easy to save battery when you need. No more editing init.d scripts...
RayTrue04 said:
Same here. I had to get rid of set cpu bcuz it would freeze the phone. Now i just have tegrak and i wish it had profiles...
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Antutu CPU Master works well and has profiles.
i had this same issue, the second i downloaded setcpu my phone started freezing for long periods of time, does anybody know if this is because it is conflicting with the presets built into the ROM?
SetCPU is for custom kernels, while tegrak is for stock. Im not sure of any custom ICS kernels besides the repacks. My phone was unplugged for 16 hours using tegrak and FC24. And he only problems i had were on the free versi0n.
My solution would be to check out tegrak if SetCPU is giving you issues.
Some roms come with undervolt scripts built in, SeCPU could be conflicting. Not sure though.
If you check Calk's ics ROM thread in Android Development, his latest release notes say something about having an issue with Ics freezing at 800, so it could have something to do with that. Don't know more myself, but hopefully that points you in the right direction!
Sent from my SPH-D710 using XDA
Not to be a smart***. But everyone does realize that ICS is designed to handle all this for you right? Thats why I never included these cpu or voltage tweaks in my ICS roms. No reboots or freezes... Some may not get issues... But most will if you use them