Related
As the title states, I've compiled a kernel that OC's to 633MHZ based on Cyanogen's latest kernel. To whomever want to try it, I recommend installing the latest SetCpu before flashing the update so you can set it to a frequency that doesn't make your phone crash (instead of having one that doesn't boot at all).
Thanks to:
bcrook for his port guide and 32A patch script
cyanogen for the kernel
pershoot for his frequency table which I used as a template for mine
koush for AnyKernel
edit:
carz for his gingerbread kernel
ezTerry for the extra RAM patch
Update: made a new kernel that goes to 710MHZ, can't guarantee if it will boot for everyone so set setcpu to boot at a lower frequency (max. 576 mhz or so) and updated the 633MHZ kernel to newest cm-kernel
Update 2: for those who think they can get more out of their phone I've put up a kernel that goes to 767MHZ, when testing in SetCPU don't forget to uncheck set at boot (otherwise your phone will not boot properly)!!
Update 3: for those whore are crazy enough, or got very lucky and ended up with a phone that overclocks like hell, there is a new kernel that goes to 825 MHz now. I am not responsible for any damage that could occur!!
Update 4: new kernel using the latest version of the cyanogenmod kernel with pershoot's additions, not going to make one that stops at 633 anymore, just set it to that yourself
Update 5: have not released a new kernel for 5.0.8 but dumfuq has : http://forum.xda-developers.com/showpost.php?p=6794812&postcount=16, I've tested it and everything works fine
Update 6: made a new kernel of my own (based on cyanogen's latest for 5.0.8), not sure if it's more stable than dumfuq's and this time it goes to 787MHz: http://db.tt/QRranm
Update 7: new kernel based on cyan's latest with latest additions from pershoot's github, max feq: 787MHz, should be more stable now EDIT: sorry compiled kernel wrong , re-uped it with the right frequencies
Update 8: seeing as CM6 RC1 has been released, have updated kernel to include all latest changes, but max freq, is 748 MHz because it wouldn't boot with a higher frequency.
Download from here: http://db.tt/HA6xFY, edit: not sure it works very well, has some trouble booting on CM 6, stay away from it for the moment...
Update 9: new kernel for cm6 RC3 only goes to 710MHz otherwise it won't boot on my phone download link : http://db.tt/qhd7Wz9
Update 10: I've made a new OC kernel for anyone running Gingerbread on the new radio, it's basically carz's kernel except it goes to 710 MHz (max, seems stable so far) and adds an extra 10 MB of ram (ezTerry's patch can be found here).
I'm testing this as I'm writing, I did overclock to 633mhz, and the phone is still working
And you are SURE that the radio is NOT blocking the overclock?
Re: [OLD RADIO][KERNEL] Cyanogenmod kernel OC'd to 633MHZ
Well there is a whole thread about overclocking in the G1 section and compared to 528mhz I get at least half a megaflop extra
Linpack gets 3.6 -3.8 on 633mhz
Games work almost the same, we would need a GPU oc
Can i use this kernel with cm5.0.7-t4?
PremierITA said:
Can i use this kernel with cm5.0.7-t4?
Click to expand...
Click to collapse
Yes you can, I'm using it.
rps13 said:
As the title states, I've compiled a kernel that OC's to 633MHZ based on Cyanogen's latest kernel. To whomever want to try it, I recommend installing the latest SetCpu before flashing the update so you can set it to a frequency that doesn't make your phone crash (instead of having one that doesn't boot at all).
Thanks to:
bcrook for his port guide and 32A patch script
cyanogen for the kernel
pershoot for his frequency table which I used as a template for mine
Click to expand...
Click to collapse
can you suggest wich cpu frequency set in SetCPU?
thanks
i've flashed,
after first boot i setted SetCPU to use max = min = 633mhz, but phone lags
Can you suggest a better conf please?
In linpack.
What about reality? Is it any better?
eyegor said:
In linpack.
What about reality? Is it any better?
Click to expand...
Click to collapse
Not really, it is nothing special, the same as "stock" cyanogen 5.0.7
Without wishing to ridicularise this post. but till then will this be helpfull for daily use?
Batery ?
safeness of phone?
I cannot see a good reason to try this even once. :\
What are the supported frequencies? Can we peek at the frequency table?
I set it at 633000 but got 614mhz, my setcpu.txt are 245760,528000,576000,633000
Re: [OLD RADIO][KERNEL] Cyanogenmod kernel OC'd to 633MHZ
It breaks the 3d but there is a noticeable improvements In normal usage, it could be placebo effect though. Setting at 614mhz max 122 min
-------------------------------------
Sent via the XDA Tapatalk App
For those not using autodetect in setcpu, change your setcpu.txt frequency to 633600 if you want to set your phone to 633 MHZ, as for it being faster in general use, it seems to perform better when there are more applications open than a lower clock, but what I've noticed the most is better performance in Gameboid, though sometimes, there is clock switching bug, which requires the min frequency to be set to 122800 and then raised again. But TBH, there isn't a very big difference between 633 and 576 and the only reason I made it was for 32A users who wanted to experiment with higher frequencies.
rps13 said:
For those not using autodetect in setcpu, change your setcpu.txt frequency to 633600 if you want to set your phone to 633 MHZ, as for it being faster in general use, it seems to perform better when there are more applications open than a lower clock, but what I've noticed the most is better performance in Gameboid, though sometimes, there is clock switching bug, which requires the min frequency to be set to 122800 and then raised again. But TBH, there isn't a very big difference between 633 and 576 and the only reason I made it was for 32A users who wanted to experiment with higher frequencies.
Click to expand...
Click to collapse
Btw, What about your 3D? isit working?
Not sure, the only 3D game (at least I think it is) I've got is Tower Raiders FREE (Nexus and Droid version) and it works for me
can i use this kernel with cm5.0.7 t5?
alabasta10 said:
It breaks the 3d but there is a noticeable improvements In normal usage, it could be placebo effect though. Setting at 614mhz max 122 min
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I've installed this kernel on my cm5.0.7 t4,and for me it is better than default. Phone hasn't lag, 3d gallery works well (before install,its taks a lot of time to show photos).
I used SetCPU's profiles.
thanks! i'm hitting 3.9 to 4.xx on linpack.
Edit: i'm getting 4.1x every time with 595mhz.
Ok, sorry if this seems like a stupid question but... I have flashed/tested all of the Tiamat Kernels onto my xoom and it seems that I can only run the 1.4 Ghz Kernel with no random reboots. So I thought that if i download the higher 1.5Ghz or the 1.6Ghz and just under-clock it to 1.4Ghz that should stop it from doing random reboots, but sadly it doesnt and I still get random reboots even with Setcpu Under-clocking it to 1.4Ghz. Now is this typical or am I missing or misunderstanding something? Is there a reason why I cant use the higher Kernels and Under-clock them to 1.4Ghz and get no random reboots? I am only asking because I flashed the Riptide and under-clocked it to 1.4Ghz and it really made my xoom feel much faster and nicer in my hands and would love to keep using the Riptide Kernel.
Thanks in advance,
-Dez
I have the same issues and have been wondering the same thing.
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
nexan21 said:
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
Click to expand...
Click to collapse
I too have noticed this, after reading your post I tried keeping the Kernels but with no OC and left it at 1.0Ghz and it still has random reboots. So is there something in the Higher Kernels that are causing it to be unstable regardless of what Ghz you clock it to?
watch setcpu at times. It doesn't matter what you set the clock at in setcpu it will still go to the max clock the kernel allows. I am not sure if it is a bug with setcpu or if it is just the way the kernel works. If you reboot your Xoom when setcpu is at 1ghz, then go and play with the xoom after reboot for awhile. Go back into setcpu and look under the info tab. You will see that the cpu has indeed been running the higher clocks then 1ghz at times. It doesn't run those higher clocks much but it does. Which is most likely why you are getting lockups or reboots. My Xoom seems to love the 1.5ghz kernel but hates the 1.6ghz one.
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
tribalb said:
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The oc is in the kernal i think , i dont have setcpu installed but cpu still at times peaks at the max 1.504 ghz ac ording to
"Temp+cpu"
https://market.android.com/details?id=com.sanels.tempcpuv2&feature=more_from_developer
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
EDIT:
So I was asked what kernel I'm using... I will post my ROM + KErnel! and just to let you know, my G2x has never had any problems so that may be way my G2x can get -200 on 500 and 400
And I am using faux's CM7 Kernel Version 0.2.4
Full name:
"2.6.32.41-CM7-Faux123-v0.2.4
Mod version
CyanogenMod-EagleBlood_v1.2
Im new to setcpu, good thread for me to learn a bit more from other users...
Sent from my LG-P999 using XDA App
Yes I'm trying to decide on SetCPU or PimpMyCPU so any info is appreciated
GManLynx said:
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
Click to expand...
Click to collapse
What kernal are you using?
GManLynx said:
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
Click to expand...
Click to collapse
How are you not getting reboot problems with 400 at -200mv? I'm using faux's froyo kernel and when I undervolt at -100mv i get rebooting problems
I replied to your comment in my main post, since other people may be interested in that and that will cause them not to scan the pages.
Bump :\ I would like input
so how is your battery life?
Bad. Something about those settings messed it up. I much prefer just using the custom rom default kernel its much better on the battery
Sent from my LG-P999 using XDA Premium App
My chip could only use faux's OC 1.2ghz, using the kernel OC 1.5 would cause my phone to boot loop. I could go stable @ faux OC 1.2 with minimum UV, getting qudrant score of atleast 3000 - 3500. Another kernel that i tried is MOrfic's, I can go stable up to 1.4 Ghz/minimum UV- quadrant of atleast 4000-4300. I believe i have what they say as the "weak chip" though running OC @ 1.4 ghz doesn't make it look weak. Thanks to the great DevS!
Good evening all,
I am currently running vb with the latest above kernel and xda-edition of setcpu...
My question, has anyone found voltages that are stable?
I have always/only used tegrak, when adjusting the voltages I am able to adjust "internal" as well as "core" voltages, as you may know setcpu only allows the adjustment of one voltage. So, I set all levels to the "internal" voltages that worked for me on tegrak(scaling set to smartass), everything was working fine until I rebooted the phone... At that point the phone would boot then freeze after the third media scan, I had to flash back to the b1 kernel to get back up and running.
Any advise would be greatly appreciated.
Thank you in advance!
Sent from my SGH-T959V using xda premium
You're trying to undervolt? Anton's b5 in undervolted. I'd stick with his recommended values.
How do you actually implement these voltages? I've only used Tegrak so this is new
Sent from my SGH-T959V using xda premium
QUIETLYloud , I dont't have paid Tegrak so I cannot make a thorough test.
I tried using very old Ultimate version available someplace on the web, and it does in fact seem to mess the phone up. I didn't need to reflash, but had to uninstall Tegrak, reboot, clear caches, and rescan SD for errors. Google says that there were issues with Tegrak module and custom kernels, but they were supposedly fixed around version 1.4.
I tied the new free version 1.6.7 from Market. It doesn't let me do much (like setting on boot), but at least it seems to work correctly with frequencies.
The setup with OC kernel is a little different. Before, if you wanted to OC, you would go and enable CPU Max Frequency, which would replace 1 GHz. Do not go there! The kernel already has all overclocking frequencies available. Instead set the Scaling to the highest frequency you want to use (let's say 1.2 Ghz, which is CPU Level 2). Then go to Optimization and set desired voltages for the frequencies you chose. No need to change anything for frequencies above you max scaling, the CPU will not go there anyway. Maybe it's a good idea to completely clear Tegrak data and start setting it up form scratch.
Let me know if you succeed.
Btw common Google knowledge doesn't seem to recommend lowering internal voltages. You will not gain much, there is just not a lot of current draw there. It's the core that draws a lot of current.
EDIT: Hmm... Tegrak seems to have a problem with smartassV2 governor. If the scaling in Tegrak is set to use anything but all frequencies, including 1.4 Ghz, the governor will never lower the frequency from the highest selected. The kernel itself (with SetCPU or without) doesn't have this problem, it's only when proprietary Tegrak module is loaded.
AntonX...
I decided to scrap tegrak for the time being and use what you recommended with setcpu and left voltages alone until I have a better understanding, since doing so haven't had any problems
Sent from my SGH-T959V using xda premium
Btw I said before I set the default voltages kind of safe, even if they are slightly undervolted. I'm running the kernel UV-ed a little more with SetCPU for second day without any issues. Here are my numbers right now:
1.4 - 1350
1.3 - 1300
1.2 - 1275
1.0 - 1250
800 - 1175
400 - 1025
200 - 925
100 - 900
Hi guys
I apologize for some noobness coming this way, but I don't understand. Kernel beta5 is oc/uv - what does it mean if I don't use setcpu/tegrak?
Will kernel behave other than prior versions?
And if I decide to do use setcpu? What good does it make if uv makes no change (according to Antonx) and oc will only drain the battery even more, I mean, phone is pretty much fast, so why bother oc it?
Thanks!
Sent from my SGH-T959V
I have an unlocked and rooted but otherwise stock TF700t. I downloaded setCPU and tried to go to 1700Mhz max but it will not go above 1600. I have tried setting min 1700Mhz, tried changing governors and schedulers, but nothing will make it go above 1600Mhz. Is this something ASUS has locked down?
ka1z0ku said:
I have an unlocked and rooted but otherwise stock TF700t. I downloaded setCPU and tried to go to 1700Mhz max but it will not go above 1600. I have tried setting min 1700Mhz, tried changing governors and schedulers, but nothing will make it go above 1600Mhz. Is this something ASUS has locked down?
Click to expand...
Click to collapse
You should go and try custom ROMs and especially their kernels to overclock.
I don't think the stock yet rooted kernel allows overclocking.
For what it's worth, running the Zeus ROM, CPU Master reports 1700 Max... Although, I don't think it has anything to do with the kernel in this case (it uses stock kernel) - I think the max speed can be tuned via some settings at the OS level (via root, of course). Take a look at the cpu1.sh, cpu2.sh and cpu3.sh scripts in /etc - they are the PowerSave, Balanced and Performance modes (those scripts get run when switching modes).
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
adelancker said:
You should go and try custom ROMs and especially their kernels to overclock.
I don't think the stock yet rooted kernel allows overclocking.
Click to expand...
Click to collapse
I have stock + rooted, I can selected 1700 with SetCPU. This is stock speed, no over clocking, no custom rom required. Do you have the latest update (version .26)?
If it is set to run at max, it will run at max when needed. AFAIK it's 1700 for the 1st core and 1600 is for multi-core use.
I too have seen tbis happen except im using system tuner to set it to max. When i set it to hit 1.7 it seemed it only ran 2 cores mostly one. Not all 4. When i set max to 1.6 all 4 cores are on.
Sent from my PG86100 using Tapatalk 2