after i load any one of the many kernels on my Nexus 7, I use ROM control and can see its at 1300 but can slide all the way to 1800. once i do this and even mark set on boot and then exit... the speed always goes back to 1300. in all my benchmarks it shows 1300 was the speed but if i go back into rom tool back it shows 1300 as the setting as if i never changed it however i can still slide to 1800.
even tried a reboot and still no luck.
what am i supposed to use?
what kernel are you using?
Sent from my Nexus 7 using xda app-developers app
kickmobile said:
what kernel are you using?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
it was called
1.8ghz650GPUNopix.zip
and now i just installed
grouper-faux123-kernel-v010ultimate.zip which now defaults to 1500 with the slider allowing ability to go up to 1700 but always goes back to 1700.
whats the point of giving the ability to change CPU speed in ROm tool box if it doesnt want to remember what you set it to. so annoying.
its not the kernels fault. your rom is "broken", you need the powerhal fix, it should be in your rom but it isnt. theres a flashable powerhal fix floating around the forums. also, some cpu control apps include it, like the Trinity Kernel Toolbox.
When this happens to me with Antutu CPU Master I just bring the minimum down to 51 and then drag it back to whatever I want. I'm also just running the CM10 nightlies.
Related
SetCPU. In my personal opinion, one of the best Android apps out there. It lets you overclock/underclock your phone. Here I will describe how to set it up for the Vibrant so you do not brick/crash your phone.
1. Uncheck/DO NOT Check Set on Boot (this will cause crashes in most phones if checked)
2. Set the CPU Governor type to "Conservative"
3. If you're using a kernel such as JAC's OC/UV(/VOODOO) set the MAX Clock speed at 1.2Ghz, also set the MINIMUM clock speed at 200MHz (not doing this could cause random crashes/reboots/freezes)
4. Don't underclock too low (as this could cause crashes), I recommend nothing below 750MHz (although it could *probably* run at 400MHz, no lower though!)
5. Don't blame the dev of your kernel or SetCPU's dev if you break your Vibrant, you shouldn't do something you know nothing about.
6. Set a warning up so if your Vibrant gets hotter than 115° Fahrenheit SetCPU will alert you. (125° Fahrenheit is when your Vibrant will start to get damaged.)
7. Always ask if this works on the ROM you have flashed before you try to use it on the ROM.
8. SetCPU is free for XDA members only.
9. This will NOT work on the Vibrant's Stock kernel, a new one must be flashed (such as JAC's OC/UV(/VOODOO) kernel or Kingklick's OC/UV Kernel)
That is all.
A couple of things:
1. It's been found that setting the minimum to 200 MHz is too low on some ROMs and can cause problems with some applications, like Pandora. Users have reported that setting the minimum to 400 MHz alleviates those problems.
2. SetCPU is and has been free for some time to XDA members. However, if you like the application, you should throw the dev some coins and buy it in the market or make a donation.
NikolaiT said:
SetCPU. In my personal opinion, one of the best Android apps out there. It lets you overclock/underclock your phone. Here I will describe how to set it up for the Vibrant so you do not brick/crash your phone.
1. Uncheck/DO NOT Check Set on Boot (this will casue crashes in most phones if checked)
2. Set the CPU Governor type to "Conservative"
3. If you're using a kernel such as JAC's OC/UV(/VOODOO) set the MAX Clock speed at 1.2Ghz, also set the MINIMUM clock speed at 200MHz (not doing this could cause random crashes/reboots/freezes)
4. Don't underclock too low (as this could cause crashes), I recommend nothing below 750MHz
5. Don't blame the dev of your kernel or SetCPU's dev if you break your Vibrant, you shouldn't do something you know nothing about.
6. Set a warning up so if your Vibrant gets hotter than 115° Fahrenheit SetCPU will alert you. (125° Fahrenheit is when your Vibrant will start to get damaged.)
7. Always ask if this works on the ROM you have flashed before you try to use it on the ROM.
8. SetCPU is not (and probably never will be) free, so DO NOT bug the dev for a free copy.
9. This will NOT work on the Vibrant's Stock kernel, a new one must be flashed (such as JAC's OC/UV(/VOODOO) kernel or Kingklick's OC/UV Kernel)
That is all.
Click to expand...
Click to collapse
I am interested in how you have determined this.
How legit are these instructions, im interested in this app. Since im running bionix 1.9.1 jacs oc/uv rom.
Sent from my SGH-T959 using XDA App
I agree with most of what the OP is saying, I've been using setcpu since my G1. I'm currently running Fusion 1.0 with JAC kernel. I have 200 min with 1200 max. No set on boot and no profiles. I'm not sure about the damage temp, I've ran the gps for an hour with the phone in direct sunlight and it hasnt gotten that high.
This is what works for me, as well as many other users, and the issues posted here have been reported by many users. Also to the person with JAC's OC/UV Kernel, this app is required. If it isn't used, you can experience random freezes/crashes/reboots.
opiomorph said:
A couple of things:
1. It's been found that setting the minimum to 200 MHz is too low on some ROMs and can cause problems with some applications, like Pandora. Users have reported that setting the minimum to 400 MHz alleviates those problems.
2. SetCPU is and has been free for some time to XDA members. However, if you like the application, you should throw the dev some coins and buy it in the market or make a donation.
Click to expand...
Click to collapse
Yes, this is true, but the only time time the vibrant will reach 200MHz (100MHz if SetCPU isn't used) is when the phone is idle.
Double post, apologies.
i have set on boot checked on bionix 1.9.1 with no problems. 200min,1200max, conservative.
Im running the bionix 1.9.1 with jacs oc/uv. I havent installed the set cpu app yet and my phone is running great. Im working on getting up the nerve to try it.
Sent from my SGH-T959 using XDA App
GreggoryD502 said:
Im running the bionix 1.9.1 with jacs oc/uv. I havent installed the set cpu app yet and my phone is running great. Im working on getting up the nerve to try it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Do eet! The worst that will happen is that your CPU can't handle an overclock and you'll be stuck at 200/1000. Cross your fingers!
It is worth the money for the developer, for sure.
Also, can you post your source for the temperatures you listed? Seems kind of low for Fahrenheit. Especially since where I live those temps are just above room temperature sometimes
Ok. Just installed and set 1200.max 400 min. Will post latet let everyone know.if I notice a differnce. Phone does seem snappier, or could be.my imagination. Lol
Sent from my SGH-T959 using XDA App
Quick, possibly dumb question. Do I have to reset the settings if I turn my phone off and turn back on?
Sent from my SGH-T959 using XDA App
GreggoryD502 said:
Quick, possibly dumb question. Do I have to reset the settings if I turn my phone off and turn back on?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
not if you have 'set on boot' checked. but some people claim that setting can cause problems. however i've been running bionix 1.9.1 with set on boot checked since 1.9.1 came out with 0 problems. otherwise, yes, you have to reset it every time you reboot.
Thanks. Ill check set on boot and see what happens.
Sent from my SGH-T959 using XDA App
Be careful about "Set on Boot", it someone resets SetCPU and underclocks your phone to the point of crashing shortly after it boots. This is a pretty common issue but it doesn't happen to all users.
funeralthirst said:
not if you have 'set on boot' checked. but some people claim that setting can cause problems. however i've been running bionix 1.9.1 with set on boot checked since 1.9.1 came out with 0 problems. otherwise, yes, you have to reset it every time you reboot.
Click to expand...
Click to collapse
i dont have set on boot checked, and my settings are preserved on reboot
Ive been using set on boot for several days now, and no issues so far. To be honest I cant really tell any difference in the phones performance. But im not really pushing it either.
Sent from my SGH-T959 using XDA App
NikolaiT said:
9. This will NOT work on the Vibrant's Stock kernel, a new one must be flashed (such as JAC's OC/UV(/VOODOO) kernel or Kingklick's OC/UV Kernel)
.
Click to expand...
Click to collapse
This does work on stock vibrant kernel. I have it on JI6 stock except for Root and mods. The OP is correct that you cannot over clock on stock.
As a battery saver for JI6 possibly. Also I am currently using it as an attemped fix for my Gallery freeze, lockup/CPU hog issue.
Sent from my SGH-T959 Gallery freezing Vibrant using XDA App
hi all been a member for a long while from HTC 8525 days, just wanna say i love this site, saw that the app was free for members, but i love supporting you guys i bought the app anyway! thanks for all the hard work all of you put in... im sure we all appreciate it!
I have moved from CM7 to Hombase 5.4, and found that setcpu no longer seems to do anything. on CM7 it worked as i had hoped, underclocking the phone when i was doing low intensity stuff like texting, and pushing it up to full power for videos etc. now it does nothing but tell me core temps, which are always high as its always running at 1Ghz.
Can anyone explain how to get it back to underclocking?
Many Thanks
Try a different kernel.
Sent from my CM860
ishamm said:
I have moved from CM7 to Hombase 5.4, and found that setcpu no longer seems to do anything. on CM7 it worked as i had hoped, underclocking the phone when i was doing low intensity stuff like texting, and pushing it up to full power for videos etc. now it does nothing but tell me core temps, which are always high as its always running at 1Ghz.
Can anyone explain how to get it back to underclocking?
Many Thanks
Click to expand...
Click to collapse
This is a known issue with the OC faux kernel. I was running into the same problem with his enhanced stock kernel after using webtop. After reflashing the enhanced stock 0.2.0 it would still get stuck at max 1Ghz after using webtop, but a reboot would get the underclocking working again.
I only tried the webtop hack to see if I could get it working. I haven't gone back into it at all so I don't know if this is something that will reoccur. Although I will say that with my day to day use I have not run into any clocking issues since.
Thanks, is there a page somewhere which details which kernels do what and which would work with my rom?
Sent from my MB860 using xda premium
ishamm said:
Thanks, is there a page somewhere which details which kernels do what and which would work with my rom?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
This is the page for faux's kernels. As far as details, start reading and searching through that thread as well as the threads for any ROMS you are using. 99% of the time people will either have the same problem (and possible fix), the other 1% of the time they will identify a bug (i.e. maxed out CPU).
Keep in mind faux does have different kernels for Froyo, GB, and CM7.
For some reason even if I move the slider from 1300my to 1000, when I touch the screen with at least 3 fingers for a few seconds it pegs out at 1300. I read our cpu's are daisy chained so to speak
so the 2nd core kicks in when needed. I tried cpu tuner and it gives the option to powersave and only use one core or if you choose performance it will allow Both cores. Just might be setcpu isn't designed fully for our dual core setup.
thanks for the link to kernels, but i cant find one for HomBase, or a Kernel only download on the homebase thread. i have the Version2, which has some blur, but only the 1.0Ghz clock kernel. where could i get the 1.3GHz download by itself, to see if that might help, as its the one CM7 had iirc
Thanks
ishamm said:
thanks for the link to kernels, but i cant find one for HomBase, or a Kernel only download on the homebase thread. i have the Version2, which has some blur, but only the 1.0Ghz clock kernel. where could i get the 1.3GHz download by itself, to see if that might help, as its the one CM7 had iirc
Thanks
Click to expand...
Click to collapse
Get the 1.3 from the faux thread that I linked to. They're in the very first post...
CM7 is the only ROM that has its own custom faux kernel. For all other ROMS just match the kernel to the build the ROM is based off of (Froyo or GB). If you're using V.2 of Homebase then use the GB one.
Update: Also, there are other kernels out there. I was only using faux's as an example since you were using CM7 and Homebase.
thanks, ive now got the 1.3Ghz kernel installed successfuly, but it still seems like setcpu will not underclock. i dont know if its normal, but the "Scaling" option is greyed out, and i cant get access to the Advanced tab. is there something im doing wrong in setcpu itself?
thanks again
ishamm said:
thanks, ive now got the 1.3Ghz kernel installed successfuly, but it still seems like setcpu will not underclock. i dont know if its normal, but the "Scaling" option is greyed out, and i cant get access to the Advanced tab. is there something im doing wrong in setcpu itself?
thanks again
Click to expand...
Click to collapse
Lack of underclocking is a known issue with the latest OC kernel. I'm unclear whether it's actually a bug with the kernel or with setCPU not supporting dual core devices. But yeah, there's a problem with it right now. I'm on the stock enhanced, and other than the webtop issue I mentioned above, it works fine.
Scaling/advanced are not available, this is something that is determined by the kernel you are using not the app.
ok so if i understand you right i would be best off using the stock enhanced kernel (for now), as it will underclock fine?
ishamm said:
ok so if i understand you right i would be best off using the stock enhanced kernel (for now), as it will underclock fine?
Click to expand...
Click to collapse
It's working perfectly for me, except after webtop use (which I don't normally use).
I'm still having the same issues regardless of weather I choose power save or performance it will not underclock, and those are the only governors I get the option of :s
Sent from my MB860 using xda premium
So I'm kind of new to messing around with tablets but learning a few things. On my Nexus 7 I decided to put Cyanogenmod 10 on it so I could customize a few things. I then decided I wanted to overclock the max CPU frequency past 1300 MHz so I installed Trinity 7 kernel. Now I'm able to run it at 1700 MHz which runs a few apps much faster but after exiting out of the apps and going back to check on the max CPU frequency and it's set back down to 1300 MHz.
Does anyone have an idea what could be causing this? So far there's only one app I'm overclocking for so it's not a big issue but it would still be nice to figure out the issue.
Thanks
I down loaded too. I just changed the governer to performance and it stays on 1600 etc on set cpu
EsX GingaNinja said:
So I'm kind of new to messing around with tablets but learning a few things. On my Nexus 7 I decided to put Cyanogenmod 10 on it so I could customize a few things. I then decided I wanted to overclock the max CPU frequency past 1300 MHz so I installed Trinity 7 kernel. Now I'm able to run it at 1700 MHz which runs a few apps much faster but after exiting out of the apps and going back to check on the max CPU frequency and it's set back down to 1300 MHz.
Does anyone have an idea what could be causing this? So far there's only one app I'm overclocking for so it's not a big issue but it would still be nice to figure out the issue.
Thanks
Click to expand...
Click to collapse
There might be an option for "set at boot." Try that.
mccolvinj said:
I down loaded too. I just changed the governer to performance and it stays on 1600 etc on set cpu
Click to expand...
Click to collapse
That's not the solution. The performance governor keeps the cpu speed at max frequency at all times (even when screen is off). That will eat up your battery quick.
v9s said:
There might be an option for "set at boot." Try that.
Click to expand...
Click to collapse
Thanks that seemed to have fixed it though I figured out you have to turn that on THEN pick the max CPU frequency. Doing it the other way around won't change anything, I think that's what I tried before.
Also mccolvinj I'd personally leave it on interactive so it will just use the max CPU when needed or at least that's what I got out of the descriptions of governors I looked up.
EDIT: Nevermind...that only temporarily fixed it, it went back to 1300 after a bit. Maybe I installed Trinity 7 wrong?
Does trinity have superuser permissions?
Sent from my Nexus 7 using xda app-developers app
winged mantis said:
Does trinity have superuser permissions?
Click to expand...
Click to collapse
I think so since it's rooted, is there a way I can check or give it permissions?
you need the powerHAL "fix". your rom should include it, but i guess it doesnt. search the n7 forums for a flashable. or, the trinity kernel toolbox app includes the "fix" just in case your rom doesnt.
EsX GingaNinja said:
I think so since it's rooted, is there a way I can check or give it permissions?
Click to expand...
Click to collapse
Check in the superuser app
Sent from my Rezound using xda app-developers app
kernels arent rooted, your roms are. you can flash a custom kernel on a rom without root. the only difference is that you wouldnt be able to control the cpu with ant cpu control apps, the apps need root.
ive posted the solution already. either find the flashable powerHAL fix or use the trinity kernel toolbox to control the kernel. tkt includes the powerHAL fix.
Do you know any good alternatives for TricksterMod that support OC and undervolting? I'm running latest ParanoidAndroid with M-kernel. Help much appreciated!
Why do you want to use another app? If you read OP of M-Kernel, you will see that only trickster is supported to change parameters. Extract from the OP: "The only app supported for changing any kernel parameters and settings is TricksterMod".
Odp: TricksterMod replacement
I want to try another one, because when I downclock to 1,2 Ghz, there seems to be no direct voltage change option for that frequency, closest is 1170 and 1230 Mhz. So I have no idea which one should I change.
That's the way the nexus 7 gets frequencies. Instead of using specific voltages, it uses an incremental table.
Sent from my Nexus 7 using xda app-developers app
Yep, i've read that tegra uses the table as a reference... Even if there the kernel has clock speeds that directly relate to the one you are going to use, -50mv does not mean a direct -50mv sent to the core. Also, tegra does auto 'cold zone' undervolt when it's capable. Hence, the voltage set contrasted to the frequence set in any software is relative to tegra but not 100% definitive...
Odp: TricksterMod replacement
Thanks, seems like undervolting my Nexus won't be as easy as I thought.
Dont worry too much about it. It's just like your local speed limit, if 40mph/kph you wont stay exactly at 40 all the time, neither always below or always above. It will be a reference and realtime decisions are made based on road conditions. Somewhat simillar here.
Im lucky to have a good chip, able to run at 1.6G with voltages meant for 1.2 stock... Able to push it lower but it starts locking up once in a while. It might take a few days so have fun! Remember to backup anything important just in case =>
I am looking to try and run an N64 emulator smoother. I've been searching Google high and low for a custom kernel that wall allow my to overclock my phone, but I am left stumped so I come here. Might I also add that I am running android 4.4.2.
O/C requires a custom kernel.. Find one you like and flash it via TWRP or CMR..
use an app like mulitcore cpu control or rom toolbox to then change clock frequencies. The s4 already has overheating problems.. overclocking is not going to help and will eat your battery. Increacing clock freqs wont help much.
autonomousperson said:
O/C requires a custom kernel.. Find one you like and flash it via TWRP or CMR..
use an app like mulitcore cpu control or rom toolbox to then change clock frequencies. The s4 already has overheating problems.. overclocking is not going to help and will eat your battery. Increacing clock freqs wont help much.
Click to expand...
Click to collapse
Delete
Sent from my Nexus 5 using XDA Free mobile app