Related
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
I recently flashed the newest Trinity Kernel on my Nexus 7. I still have the stock ROM. I tried to tweak the CPU settings with ROM Toolbox and the most I can overclock is 1400mhz. Why can't I overclock to 1600? Is it because of the stock ROM? I'm looking into Glazed Jelly Bean as a custom ROM but I'm not sure I want or need to use a custom ROM at this point.
Any suggestions?
Because he dropped the Max. You probably flashed A111 correct? That's a TSVZ meaning it is slightly over clocked and undervolted kernel meant for battery not for performance.
Sent from my Nexus 7 using Xparent White Tapatalk 2
U2Bono269 said:
I recently flashed the newest Trinity Kernel on my Nexus 7. I still have the stock ROM. I tried to tweak the CPU settings with ROM Toolbox and the most I can overclock is 1400mhz. Why can't I overclock to 1600? Is it because of the stock ROM? I'm looking into Glazed Jelly Bean as a custom ROM but I'm not sure I want or need to use a custom ROM at this point.
Any suggestions?
Click to expand...
Click to collapse
try a96, its one of my faves. it has a max of 1700mhz http://goo.gl/mLUCZ
Mildly on topic question ... do you notice any imporvments with overclocking? My first experience with overclocking as on my Hero, and then Galaxy S1, but this N7 just feels so fast i cant see overclocking making it any smoother? lol
thanks
myke66 said:
Mildly on topic question ... do you notice any imporvments with overclocking? My first experience with overclocking as on my Hero, and then Galaxy S1, but this N7 just feels so fast i cant see overclocking making it any smoother? lol
thanks
Click to expand...
Click to collapse
yes. its noticeable, but not like on the older devices.
simms22 said:
yes. its noticeable, but not like on the older devices.
Click to expand...
Click to collapse
Nice, ill have to look into rooting sometime soon.
Ok, I got the a96 and I've flashed it...
Is there a detailed changelog for each version? The a111 said it was a 1600mhz kernel so I don't understand why it was dropped down to 1400. That's where my confusion was.
I did notice some increase in speed at 1400. I was having some stuttering issues with Dead Trigger and Minecraft PE, and they were less with the 1400. I've got it running at 1600 now but I don't know what it will do to the battery or how well it will perform. I'll find out later. I've run through the battery pretty quickly today, but I was tinkering with it A LOT so it's not accurate.
What kind of tweaks could I do using Rom Toolbox that would help me maximize my battery while overclocking to 1.6?
Dont over clock.. i dont even see a need to. I use the ondemand gov which stutters a little but using interactive clears that up. Also using the CFQ IO as it is the stock IO used. Its stock so its gotta be good . Also you should turn F-Sync off that helps quite a bit. Also you could toggle auto hotplug and make it only run two cores while gaming and then turn it back on when finished so that way it will hotplug cores as it sees necessary. You could also up the voltages a little bit, some CPU's dont like the lower voltage and that will cause stuttering and glitching just up them by 25mV and see if it clears if not try another 25mV.
I will try those things, but I really want to play with overclocking and learn what happens. This is my first Android device so I'm experimenting and playing around.
But I have one more question...I've overclocked to 1.5...I found 1.6 to be the same as 1.5. But it seems that after an hour or so, it resets to 1.3. in ROMToolbox. Why is this?
Don't use rom toolbox. Use the Trinity app. It sticks just fine for me. Besides you support the dev to make better kernels.
Sent From My Toro+ via White Tapatalk
simms22 said:
try a96, its one of my faves. it has a max of 1700mhz http://goo.gl/mLUCZ
Click to expand...
Click to collapse
i **** my pants a little when it says "system succesfully corrupted, please freak out now"
MRsf27 said:
i **** my pants a little when it says "system succesfully corrupted, please freak out now"
Click to expand...
Click to collapse
Lol its a joke... its the updater-script you can make it say anything... :laugh:
MRsf27 said:
i **** my pants a little when it says "system succesfully corrupted, please freak out now"
Click to expand...
Click to collapse
ha!
youre not the first
Overclocking past 1.4 Ghz doesn't result in any major usability improvements. I've gone up to 1.7 Ghz and the only thing it does is make my tablet really warm and unstable. All you really need for improving system performance is I/O tweaks to speed up app and page loading, and a little bit of GPU overclocking to help with the transitional effects.
and, to be honest, depending which trinity kernel im using, im using either 1100 or 1150mhz mostly. on a111 im using 1100mhz and on a96 i used 1150mhz. with those speeds everything is still fast but a bit better on battery
Overclocking
If you want a little more information about the the overclocking if you havent already you might want to check out http://forum.xda-developers.com/showthread.php?t=1788759 its the official thread of the trinity kernel for grouper.
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.
Hello everyone, I wanted to know what are the real risks of overclocking on our tablet,
what could happen? what might happen is in relation with the temperature? if it is, the temperature at which you should start to worry? please seek an experienced user to correct information, I would like to bring my TF300 to overclock higher, like TF700 around 1.7 GHz in performance mode. Please stop me if I'm doing a stupid time thx
hi,
there isn't a real risk, on most devices you wil need a custom kernel that support's a higher clock freq, but when you overclock to high your divice wil just crash and reboot, then the clock freq's are normaly set to stock, so i dont think there is a real risk about it.
but i wouldn't go higher then 1.6 with TF300T...
None of the oc kernels are dangerous
Sent from my SGH-T989 using xda app-developers app
can u give me a download of a flashable by recovery stable OC kernel?
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.