Related
FOR 1.5 ROMS ONLY.
Thanks to teknologist, maxisma, toastcfh, and all those who contributed to cracking the CPU open for overclocking.
Looking at the CDMA forums, it seems they were a step ahead of us with their kernel speedups. With help from their work, and particularly, from toastcfh, I've been able to patch and compile a kernel based on teknologist 1.9 with added features and speed.
Added features and changes so far:
- BFS, brainfuck scheduler. Basically, helps the CPU respond faster.
- Overclock. Up to 768MHz is enabled, but defaults to a safer 595MHz. It should be compatible with SetCPU. Be sure to use the custom setting.
- Deadline I/O scheduler. It should make file read and write operations a tad faster. We'll see if it really does.
Git repo: http://github.com/Soaa-/-lightspeed/tree/master/kernel-hero/
It runs at 595MHz! How do I make it faster?
Download and install SetCPU. It's available for free on xda-developers, but you can support the author by buying a copy on the market. Launch SetCPU and pick the custom option.
My phone doesn't wake sometimes! Or, it wakes and the crashes!
Use SetCPU and set the CPU governor to 'performance'. Try lowering the clock speed if the problem persists.
Can I flash this on recovery?
The first overclocked kernel was available only as sources, and binaries had to be flashed manually. Lightspeed comes as a standard update.zip package to be flashed through recovery though.
Does Wi-fi work?
Yes.
Does compcache/ramzswap work?
No idea. I don't use it.
Is it noticeably faster?
Yes. This isn't a 5% increase in speed, where the difference is only seen through benchmarks. Most phones can handle 691MHz, which is a 30% increase in speed. The lucky ones who can clock up to 768MHz get a 45% increase. The net result is a more responsive phone.
Does the CPU frequency scale to usage?
It can, if you keep the ondemand CPU governor. However, there have been reports of instability using the ondemand governor, so the performance governor is recommended instead.
Do you accept donations?
Not yet, as my work so far has just been putting other people's work together. My priority now is to make our phones better, not to make money.
0.1.1
Integrated setcpu.txt into update.zip.
0.1
Initial release
Hi,
Looks great! Does it work in 2.1 roms?
Greetz
I want to know also
Does it work on 2.1 oms ??
Sorry, the kernel is made for 1.5 ROMs only. The only decent kernel for 2.1 is still the same leaked one from a while back, I think.
ok, gonna try it now on a 1.5 rom, with setcpu.
let you know if speed is there
i use a stock rom, and have the recovery menu so can i put the zip on the sd card and then flash it ?
I am also interested in a guide on how to install/flash this properly.
Just like knudsen81 said. Everything working perfect with CPU running on 595Mhz.
From what I see, it should be flashed like all other kernels so just like ROM or radio.
Does this kernel scales overclocking depending on CPU load? For ex. lowers when idle or screen turned off.
ZeppeMan said:
Just like knudsen81 said. Everything working perfect with CPU running on 595Mhz.
Click to expand...
Click to collapse
when setcpu launches, it doesnt have the "auto detect" option
when i click on custom, it shows 528 max and no more..
what am i doing wrong here?
flashed the update.zip like a normal rom/radio btw.
Good job! looking forward for testing. What's actually missing from making overclocking work with 2.1?
mixxy said:
when setcpu launches, it doesnt have the "auto detect" option
when i click on custom, it shows 528 max and no more..
what am i doing wrong here?
flashed the update.zip like a normal rom/radio btw.
Click to expand...
Click to collapse
I used Overclock widget to see the speed of the CPU. I only wanted to confirm if the 595Mhz was true
Also Linpack score went from 2.3 to 2.6.
mixxy said:
when setcpu launches, it doesnt have the "auto detect" option
when i click on custom, it shows 528 max and no more..
what am i doing wrong here?
flashed the update.zip like a normal rom/radio btw.
Click to expand...
Click to collapse
Create a file named setcpu.txt at the SD card (so it will be /sdcard/setcpu.txt)
and enter the following into that file:
Code:
96000,115200,134400,153600,172800,192000,211200,230400,249600,268800,288000,307200,326400,345600,364800,384000,403200,422400,441600,460800,480000,499200,518400,537600,556800,576000,595200,614400,633600,652800,672000,691200,710400,729600,748800,768000
This will allow setting frequencies from 96 to 768 MHz via SetCPU
Thanx 4 the great work.
2 questions.
first, what does "Git repository" means and when will u release it?
second, can i flash it over Modaco 3.2 through recovery mode?
sorry 4 my bad english.
k0rner said:
Create a file named setcpu.txt at the SD card (so it will be /sdcard/setcpu.txt)
and enter the following into that file:
Code:
96000,115200,134400,153600,172800,192000,211200,230400,249600,268800,288000,307200,326400,345600,364800,384000,403200,422400,441600,460800,480000,499200,518400,537600,556800,576000,595200,614400,633600,652800,672000,691200,710400,729600,748800,768000
This will allow setting frequencies from 96 to 768 MHz via SetCPU
Click to expand...
Click to collapse
thanks for the help, lets try this out and see what happens =P
worked like a charm, thanks a lot =)
Does the camera work?
Camera, WiFi should work because it's an (old) 1.5 Kernel.
Other overclocked kernel works faster than this one (and with this one i've freezed ..) ..
With the other linpack gives me 3.2 3.3
with this 2.6 at max ..
:/
Flemmard said:
Other overclocked kernel works faster than this one (and with this one i've freezed ..) ..
With the other linpack gives me 3.2 3.3
with this 2.6 at max ..
:/
Click to expand...
Click to collapse
Have you set the cpu to 768? because the other kernal runs at 710 by default where as this runs at 595 but can be clocked all the way up to 768.
Please read the forums before complaining it doesn't do something.
Is anyone having luck with overclocking? I've tried various kernels and am now running whatever is included in Calkulin's ROM, but anytime I go over 1.036 GHz with Overclock Widget, the phone locks up...anyone able to run the 1.26ish GHz setting? What kernel?
Sent from my Evo...
Not all phones can handle being overclocked to higher settings than their processors were made for
For instance I am good all the up to 1190mhz but any higher and I get a restart
1.152 is max for me.
Sent from my FROYO'D EVO using xda app
awenthol said:
Is anyone having luck with overclocking? I've tried various kernels and am now running whatever is included in Calkulin's ROM, but anytime I go over 1.036 GHz with Overclock Widget, the phone locks up...anyone able to run the 1.26ish GHz setting? What kernel?
Sent from my Evo...
Click to expand...
Click to collapse
the only kernel that has got me up to 1.226 is Snap 8.1 on CM^. I was able to run 1.226 stable where as with any other kernel/rom combo, I was only able to get mine up to 1.9.
So there is some truth to the every Evo is different theory when it comes to overclocking capability, but there are also some variable in the kernels such as voltages that can allow for higher clock speeds
nertch 4.18 @ 1.228
Thanks...that's kind of what I was hoping/expecting to hear. I didn't think they would set it up to go to 1.26ish if someone hadn't been able to get it to work.
mine will only goto about 1.2 before a restart so give it a shot and see how it goes haha.
I am using fresh 3.2 rom and netarchy 4.1.8 bfs kernel running @ 1.267
Does anyone know how to over clock you're DI to say 1.2? Thanks for any help.
You first need to root your phone, then install a kernel that is compatible with whatever rom you are using, then you need to install an OCing app like SetCPU and adjust accordingly.
I'm rooted running the 2.2 RUU and I have set cpu. So do I just need a kernal? Which one?
i reccomend King Kernel bfs #4, best freaken kernel ever... its located... here
so when i install this kernal is it ok to just bump the cpu speed up to 1.2? are there any guides to do this?
makos101 said:
so when i install this kernal is it ok to just bump the cpu speed up to 1.2? are there any guides to do this?
Click to expand...
Click to collapse
A lot of factors come into play when you start overclocking, every rom will respond differently.
The first thing to do before anything is to do a complete nandroid back up.
When overclocking keep in mind that the more you overclock the more chances you have of making your system unstable.
I have experimented a quite a bit and I have found that the King Kernal #4 seems to work well for me and at 1.2 it seems to be pretty stable. Any higher than that and my phone will sometimes re-boot itself for no apparent reason.
Again, your rom may handle things different so experiment and see what works best for you.
And remember - Do a complete backup first!
I'm using the number 4 kernal and it only goes to 1.19 is this what you mean by 1.2? I have to keep mine at 1.1 ghz at 1.19 my di gets unstable
Ya that's as high as they can oc these chips. I can only get to 115 safely 119 just crashes. But the charging experience will be better than stock with the BFS #4.
Sent from my ADR6300 using XDA App
Could you guys please tell me what your settings for setcpu are?
I want better battery life and a faster cpu but im noticing that my phone almost needs a wake up time when i come out of screen off.
Thanks so much
makos101 said:
Could you guys please tell me what your settings for setcpu are?
I want better battery life and a faster cpu but im noticing that my phone almost needs a wake up time when i come out of screen off.
Thanks so much
Click to expand...
Click to collapse
If you are experiencing slow wake up, try increasing the min cpu speed to something around 460. Better batt life and increased speed takes a lot of experimenting. Your OC speed might differ from others due to differences in the phones cpu. For example, I have never been able to oc to 1.19 without the phone freezing or rebooting. My phone can handle 1152 but 1113 is perfect. In my opinion, ROMs have something to due with best batt-speed combo. I am running Ruby 1.1.1 with a setcpu profile of Screen off=245 without any wake lag. Other ROMs I have tried had wake up lag at that speed profile.
My set up:
(ROM-ASOP) Ruby 1.1.1
King's #1 ASOP "I told you so"- only works with ASOP
With the ROM's "Gem" performance scaling setting off, I use setcpu to OC to 1113, min is 245. I have a profile set to SCREEN OFF = 384 max/245 min.
I haven't worried about battery life since I started using King's kernals (I've tried them all with every compatible ROM on xda). I have several posts elsewhere on XDA showing 12 plus hours on a single bump charge and heavy phone use. Good enough for me. Stock cpu speed plus Sense ROM seems slow to me now.....to each his own though.
I hope to get some help because i value the opinions of those on this forum. Currently i am running virtuous 2.7 with virt. kernal v2. I am rooted, s-off, 2.15.xx radio. I want performance without draining my battery. What are the best settings to use in setcpu?
I did try king's kernal #4, but it was rebooting. switched kernals this morning.
One other app I use in conjunction with SetCPU is MinFreeManager. This will readjust your free ram to a higher standard. But with SetCPU I have it at 1113/Ondemand with no custom profiles. One other thing I really don't set is the Set on Boot option. I don't know why but I do. So with SkyRaider Vanilla 3.0 RC3/ KingX Kernel #4/ and MinFreeManager my phone fly's. I can't say for certain what settings you need for your phone but 1113-1115 is preferred by "most" phones and keep the set on boot option off. I keep a Galaxy S live wallpaper running and pandora while browsing the web and no lag what-so-ever.
CyanogenMod 6.0.2 and KingX kernel #1 with the same setup runs almost as smooth.
Hope this helps you out.
So i was looking around on App Brain for some rooted apps, and came across this. Figured i would give it a shot, figured no one had tried it yet on a dinc 2. And what do you know it works, Set my clock to 1.024, of course you have to be rooted to try this app. but since there aren't a lot of kernels out there, and the one that is doesnt work well with my rom, figure i will give this a shot for a while.
Anybody try this app? Confirm this works, seems to work for me.
I have used it, but it doesn't overclock because the stock cpu clock is 1GHz, or 1024MHz. I guess it could be used to underclocking, but thats about it.
Hmm seems to run a bit better...but who knows...at least its something until i can get a working kernel.
Any little bit helps
SetCPU overclocks right? I've got mine set at 1.305 MHz, but it has no modified Kernel, so I wanted to be sure that I'm really getting 1.3 GHz out of my processor
Nachobass25 said:
SetCPU overclocks right? I've got mine set at 1.305 MHz, but it has no modified Kernel, so I wanted to be sure that I'm really getting 1.3 GHz out of my processor
Click to expand...
Click to collapse
Download a system info app. Will tell you your CPU speed
sent from an under rated phone
I use it... I love it.
It even lets you set I/O scheduler.
Also, if your phone does an "unclean" reboot, the app wont apply your setting on next boot.
Setcpu will not overclock unless you have an oc kernal. You must be using a non-stock one.
Sent from my ADR6350 using XDA App
This app will give you your CPU stats so you can test, so you can underclock or overclock. Depending on what you want.
Hey I just bought a 32 GB Gnex and got it yesterday but it seems to be unstable at anything above the stock max frequency of 1230 MHz. I've tried Paranoid Android and last night's CM10 nightly and they would both freeze and immediately reboot upon setting it to 1305 MHz. I then flashed the Zen kernel on top of CM10 and I like that it can go up to 1.8 GHz but whenever I set anything beyond 1.23 GHz it starts to lag for about 1-3 seconds. When I knock it back down to 1.23 GHz everything is fine again.
This is the first OMAP device I have since I had the OG Droid back in 09, I loved how they were extremely overclockable and I'm going to be pretty sad if mine has to stay at stock speeds. I've tried using JRummy's ROM Toolbox Pro and the built in Performance settings to try and set the frequencies but it doesn't seem to make a difference on which one I use. I've been using the OnDemand and Interactive(x) Governors.
Is this a known problem or am I alone on this?
some CPUs have a higher tolerance than others for overclocking. looks like you got one of the super low tolerance ones.
I hope that's not the case :-/
brando56894 said:
Hey I just bought a 32 GB Gnex and got it yesterday but it seems to be unstable at anything above the stock max frequency of 1230 MHz. I've tried Paranoid Android and last night's CM10 nightly and they would both freeze and immediately reboot upon setting it to 1305 MHz. I then flashed the Zen kernel on top of CM10 and I like that it can go up to 1.8 GHz but whenever I set anything beyond 1.23 GHz it starts to lag for about 1-3 seconds. When I knock it back down to 1.23 GHz everything is fine again.
This is the first OMAP device I have since I had the OG Droid back in 09, I loved how they were extremely overclockable and I'm going to be pretty sad if mine has to stay at stock speeds. I've tried using JRummy's ROM Toolbox Pro and the built in Performance settings to try and set the frequencies but it doesn't seem to make a difference on which one I use. I've been using the OnDemand and Interactive(x) Governors.
Is this a known problem or am I alone on this?
Click to expand...
Click to collapse
you need to disable smart reflex mpu if you want to overclock. smart reflex doesnt know overclocking, so it sets your voltages to low for an overclocked cpu. thus, instant instability.
to disable smart reflex manually, use a terminal emulator. type su(press enter) then type these 3 lines and press enter after each..
*
echo "0" > /sys/kernel/debug/smartreflex/sr_mpu/autocomp
0 to disable, 1 to enable.
btw, some cpu control apps give you options to disable/enable smart reflex.
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
edit: still unstable at 1.42 GHz, also what apps would those be that allow this? Antutu CPU Master Pro only has an option to disable PerfLock.
the way to overclock is to keep moving in small increments upward and burn testing them to check for stability. Don't go straight for a 50% overclock. move up and find your threashold, and when you do start tweaking to see if you can slowly creep beyond that
brando56894 said:
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
Click to expand...
Click to collapse
The 3 lines would be:
Code:
echo "0" > /sys/kernel/debug/smartreflex/sr_mpu/autocomp
echo "0" > /sys/kernel/debug/smartreflex/sr_core/autocomp
echo "0" > /sys/kernel/debug/smartreflex/sr_iva/autocomp
Frankly, though, don't expect 1.8GHz to be stable.
Your particular device's components might not hold it together with that oc.
Sent from my i9250
Darunion said:
the way to overclock is to keep moving in small increments upward and burn testing them to check for stability. Don't go straight for a 50% overclock. move up and find your threashold, and when you do start tweaking to see if you can slowly creep beyond that
Click to expand...
Click to collapse
Yea I know (I used to OC the CPU on my PC), I just wanted to go for something big to see if it could handle it.
Edit: seems to be stable at 1.4 GHz, I'm going to keep increasing it to see what the limit is. I'm assuming i'd have to turn off smartreflex on each boot so I should probably put it in a script in /etc/init.d correct?
brando56894 said:
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
edit: still unstable at 1.42 GHz, also what apps would those be that allow this? Antutu CPU Master Pro only has an option to disable PerfLock.
Click to expand...
Click to collapse
the trinity kernel toolbox lets you disable/enable smart reflex. plus, extremely few gnex will oc to 1.8ghz. and on top of that, to oc even to 1.4 or 1.5ghz, youll need to adjust your voltages to get yourself stable. every device likes different voltages.
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
i can oc my gnex(using trinity kernel) to 1.803ghz.. but to use stable for every day, 1.689ghz is a good speed for my device. a majority of devices wont even oc that high and stable. stable being the key word.
brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
I'd find it surprising that you got 4 different overclock levels stable in 30 minutes. There's a difference between "it boots", "it boots and runs some apps", and "stable".
brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
Is she impressed by your turbo-nerd status?! :silly:
Haha she was an iSheep but I made her get an SGS3 and I turned her into an Android geek, now she flashes ROMs on her own lol
Cilraaz said:
I'd find it surprising that you got 4 different overclock levels stable in 30 minutes. There's a difference between "it boots", "it boots and runs some apps", and "stable".
Click to expand...
Click to collapse
Yea it wasn't stable in the true sense of the word, I meant it just didn't freeze every minute or so.
Sent from my Galaxy Nexus using Tapatalk 2
I'm running the 11/4 build of Paranoid Android with v3.0.51-ZenSeries v4 Tuna and I having problems setting CPU frequencies via Trinity Kernel Toolbox. The frequency will stick until I switch to another app, then when I come back to the app it will be at the stock max frequency. I am also unable to use the built in frequency tuner when using TKT.
I've tried stress testing it with stability test and even when the frequencies will stick in TKT (ex. 1.4 GHz) Stability Test will report that its at 1.1 GHz. WTF is going on here? I have all three of the smart reflex values disabled.
brando56894 said:
I'm running the 11/4 build of Paranoid Android with v3.0.51-ZenSeries v4 Tuna and I having problems setting CPU frequencies via Trinity Kernel Toolbox. The frequency will stick until I switch to another app, then when I come back to the app it will be at the stock max frequency. I am also unable to use the built in frequency tuner when using TKT.
I've tried stress testing it with stability test and even when the frequencies will stick in TKT (ex. 1.4 GHz) Stability Test will report that its at 1.1 GHz. WTF is going on here? I have all three of the smart reflex values disabled.
Click to expand...
Click to collapse
dont use PA cpu settings. do you have any other cpu control apps installed? make sure theres nothing enabled in PA cpu settings, nothing. then reboot. wait 2-3 after bootup then open tkt and try using it. is the problem still there?
It seems to be sticking now for the moment, but I haven't had anything in PA CPU settings before I rebooted anyway. I do not have any other CPU OC apps installed either. Stability test is reporting the correct frequency also. Thanks.
brando56894 said:
It seems to be sticking now for the moment, but I haven't had anything in PA CPU settings before I rebooted anyway. I do not have any other CPU OC apps installed either. Stability test is reporting the correct frequency also. Thanks.
Click to expand...
Click to collapse
sweet.
if you were checking before 3 minutes after bootup, then that was the issue. whatever it was, lets hope it doesnt come back.
I was setting the values after the phone had been up for hours, idk what the problem was :-\q