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.
I got an EVO myself and managed to overclock it to 1.267GHz. We could probably go even higher, but that requires more extensive changes. Here are the changed source files: http://dl.dropbox.com/u/36553/supersonic_oc-uv.tar.gz
It also includes an undervolt courtesy of pershoot (a whole 0.1V lower when idle, which should help battery drain a lot!). Here is a test update.zip: http://dl.dropbox.com/u/36553/supersonic_oc-uv_signed.zip (working WiFi). Make sure to do a nandroid backup first!
Sensors/camera do not currently work in this kernel because the source is not yet complete.
There is an overvolt on the highest frequencies. It should not cause any issues. Thanks to toastcfh for his source, Herver for creating the first booting overclocked kernel on the EVO, all the kernel devs in the N1 community, especially pershoot and kmobs, richardtrip from the Desire community, koush for anykernel updater, and all who helped to root the EVO. Enjoy!
Update 6/15: Fixed 950mV undervolt. Raised voltages from 1228800 above to improve stability. Source files updated and update.zip uploaded.
old said:
I posted these in an earlier thread, but I think I should bring this to everyone's attention. Here are some simple patches that will overclock the Evo up to 1.267GHz (though by any means it's not guaranteed to get that high!):
Edit: please don't flash the below update.zip, as it doesn't seem to boot. Devs, the patches are still below, and a zimage is in the anykernel update zip.
Update: I compiled it myself. Here is an update.zip: http://dl.dropbox.com/u/36553/update-oc_signed.zip. This uses toastcfh's sources, Koush's excellent anykernel updater and a config.gz pulled from a stock Supersonic. If this doesn't boot, no damage will be done to your phone. Just reboot into recovery and reinstall your ROM. You can test overclocking by grabbing SetCPU from my sig or changing the cpufreq values if you know how. Once we get this working, I will create an undervolted version for battery savings. I'd get an Evo, but it's sold out everywhere T_T
http://dl.dropbox.com/u/36553/supersonic_oc.zip
cpufreq.c and acpuclock-scorpion.c are in arch/arm/mach-msm, and supersonic_defconfig is just the config. I don't have an Evo, so I can't test these out, but these should work with the source files toastcfh posted earlier: http://forum.xda-developers.com/showthread.php?t=686240.
Undervolting can be achieved simply by adjusting the voltages (in mV) in the acpu_freq_tbl table in acpuclock-scorpoion.c. For those not familiar with his work, you can see pershoot's safe (but lower) voltages for the N1 here: http://github.com/pershoot/nexus-kernel/blob/master/acpuclock-scorpion.c. If you want to overvolt or go under 1000mV, you have to make one further adjustment to the voltage regulator in board-supersonic.c.
Note that the N1 and the Evo are completely different devices (with similar processors), so what may work for the N1 may not work for the Evo.
Click to expand...
Click to collapse
Awesome... until I am sure this is stable, I will wait, but I must have overclock
jigglywiggly said:
Awesome... until I am sure this is stable, I will wait, but I must have overclock
Click to expand...
Click to collapse
I don't recommend overclocking, the devices already can run warm at current settings.
But then again, you are entitled to do as you wish.
Options better than overclocking are to remove the Sprint bloatware and strip down parts of Sense, this speeds things up alot by removing excess background applications.
Well it ain't too bad, my Droid at 1 ghz(550 stock) runs great.
So this should be good too.
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
phinnaeus said:
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
Click to expand...
Click to collapse
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Well, I agree with the benchmarking comments but on the subject of Froyo... Froyo is designed to be even faster on equivalent hardware than 2.1... and 2.1 on my Evo is smooth as silk. And the Evo handles most Flash I can throw at it, so I'm not sure. I have however noticed a small performance difference with live wallpaper running, so maybe OCing will clear that up a bit.
Jus10o said:
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Click to expand...
Click to collapse
You know, this is an excellent point and I feel like I failed the developer community in some small way when you had to bring it up. You shouldn't have to provide a reason for wanting progress, it should happen for its own sake.
Proceed.
Jus10o said:
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Click to expand...
Click to collapse
Agree with everything you just said, and I am less than excited about the benchmarks with the EVO thus far
Roman G said:
Agree with everything you just said, and I am less than excited about the benchmarks with the EVO thus far
Click to expand...
Click to collapse
HAHAHA.. im sorry but i had to laugh at your sig.
Jus10o said:
HAHAHA.. im sorry but i had to laugh at your sig.
Click to expand...
Click to collapse
Ya I sold my hero a couple weeks before the EVO dropped, and had to use my wife's old phone.
phinnaeus said:
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
Click to expand...
Click to collapse
I'm not trying to start an argument at all but you have to think broader mathematically. If the processor runs at 1000Mhz or 999mhz (In the case of my N1) a .267 increase is 267mhz, a 26.7% increase in computational performance... That's pretty raw especially in cellphone terms, that have no way to vent or displace that kind of heat.
Has anyone noticed how much hotter the kickstand gets? I bet you that it's attached to something the cpu is connected to. $5 bucks says we will see KICKSTAND HEATSINK + FAN MOD 2GHZ OC! LOL
thebluecoat said:
I'm not trying to start an argument at all but you have to think broader mathematically. If the processor runs at 1000Mhz or 999mhz (In the case of my N1) a .267 increase is 267mhz, a 26.7% increase in computational performance... That's pretty raw especially in cellphone terms, that have no way to vent or displace that kind of heat.
Has anyone noticed how much hotter the kickstand gets? I bet you that it's attached to something the cpu is connected to. $5 bucks says we will see KICKSTAND HEATSINK + FAN MOD 2GHZ OC! LOL
Click to expand...
Click to collapse
This is a patch for developers, not a discussion thread for the merits (or lack thereof) of overclocking.
If you don't want to overclock your phone, nobody is making you.
It has worked out fine in the Desire and Nexus One community.
coolbho3000 said:
This is a patch for developers, not a discussion thread for the merits (or lack thereof) of overclocking.
If you don't want to overclock your phone, nobody is making you.
It has worked out fine in the Desire and Nexus One community.
Click to expand...
Click to collapse
how do i apply this ???????
can u make it flashable?
mccurt29 said:
how do i apply this ???????
can u make it flashable?
Click to expand...
Click to collapse
need to follow the directions in the first post. the .c files need to be loaded into the kernel source (right now just have toast's soruce) and the kernel has to be compiled with them.
if somebody wants to compile up a kernel with these, we could start testing. if i get some free time i'll help out here and compile a kernel but somebody else will prob beat me to it!
please someone let us know how this works out for your evo 4g... benchmark, test results... anything to show better/worse performance, whether your got ALOT warmer, or just a lil, etc.. ne information would be greatly appreciated it, i'm not a 100% noob, i just know how to follow instructions very well, doesn't mean i understand everything that's going on, just the basic concept of what i want. thank you in advance.
madunix said:
please someone let us know how this works out for your evo 4g... benchmark, test results... anything to show better/worse performance, whether your got ALOT warmer, or just a lil, etc.. ne information would be greatly appreciated it, i'm not a 100% noob, i just know how to follow instructions very well, doesn't mean i understand everything that's going on, just the basic concept of what i want. thank you in advance.
Click to expand...
Click to collapse
I'm waiting for someone to compile this first.
If nobody steps forward, I'll make my own attempt, but I'll be working blind with no test hardware.
I'm pretty sure most devs are waiting on the htc source kernal before playing with this. I can't wait but I understand them being hesitant to do too much with this for now. Still awesome of you to post it and have it rdy for when that time comes!
sounds good.
madunix said:
sounds good.
Click to expand...
Click to collapse
Your signature says you have a radio of 1.32.651.6, just to let you know that is not a radio, that is an HTC software OTA update. My radio is 1.39.00.05.31 for example
VisionKernel v1.2
Designed for SyndicateROM Frozen 1.1.0
Disclaimer
I nor any member of INC is responsible for anything that happens to your phone when using this kernel. It has been tested on mine and a few others phones to be working, but I cannot guarantee that it will work on yours. All CPU's are different, and each one takes to overclocking in different ways. That being said, don't be surprised if your phone locks up at 1.4ghz or 1.45ghz. Just set the clock down to a lower speed and it won't do it anymore; all this means is that your phone can't handle it.
Also, 1.45ghz is set at 1.400v and 1.4ghz is set at 1.375v which is definitely above the recommended voltage for the phone. This doesn't mean it will burn up your processor as they are very robust when it comes to heat dissipation, but just keep in mind that you are pushing the processor past its designed limit.
This is my first kernel release, although I have been compiling my own custom kernels since DI18. Took me a while to get the overclocking stable, a big thanks goes to tanimn and Rodderik for helping with getting 1.3ghz stable. Also, without tanimn none of this would really be possible. He has guided me through this process a lot, and I am especially thankful to him. You the man tanimn ;-)
1.45ghz is here, I cannot guarantee that it will work even at all on your phone. This is as high as I will go, no further.
Linpack: 19.84mflops
Quadrant: 2414
Changelog
*=Thanks!
v1.0
Overclocked to 1.3ghz and 1.4ghz @ 1.375v (steps are as follows)
100mhz, 200mhz, 400mhz, 600mhz, 800mhz, 1.0ghz, 1.3ghz, 1.4ghz
Added 600mhz step for better transitions *tanimn
Voodoo Sound v6 *tanimn and supercurio
Voodoo Color (mDNIe tweaks) *supercurio
FPS cap raised to 65fps for the time being, hoping to get that number higher *Rodderik
Everything else that is contained in Twilight Zone, minus the addition of voodoo color and 1.4ghz.
v1.1
Revert the refresh rate (framerate cap) to 56fps. People having problems with video choppiness, this should fix your issue. This is only temporary; as soon as someone can figure out a proper way to raise the framerate cap I will re-implement it.
Update to Voodoo Sound driver v7
v1.2
Add 1.45ghz (It's not 100% stable, use at your own risk.)
Add 1.2ghz step
Added BFQ disk scheduler
Implemented interactive CPU governor (use at your own risk, needs tweaking)
Smartass governor (still a WIP)
Add TinyRCU courtesy of tanimn
lowmemorykiller atomic notifier fixes
UV RAM and LCD; 2.7v and 1.65v respectively
UV_mV sysfs controls as well as frequency_voltage_table for use with Voltage Control and Pimp my CPU *Rodderik
New voltage/frequency tables thanks to Rodderik!
v1.3
Battery life improvement tweaks
BFQ by default
New frequencies
More...
How-to Video:
Thanks to qbking77 for making this excellent flashing tutorial! This will show you exactly how to get the kernel running on your phone.
http://www.youtube.com/watch?v=1k7hqewGoWk
*Downloads*
v1.2
Direct:
Temporarily removed.
v1.1
Direct:
www.holylivingfuck.com/ACS/Kernals/VisionKernel_v1.1.zip
More mirrors coming soon!
v1.0
Direct:
http://k0nane.info/rom/VisionKernel_v1.0.zip
Other:
http://www.mediafire.com/?tihrnrjm6cm177u
http://www.sharebeast.com/7egv5a83g9ab
*Source*
Github
Donations are never required, but always welcome
Donators:
darkfire79
epic4GEE
jbobspants
stir fry a lot
Alright, I'm swapping the twilight zone kernal for this. Thanks for an amazing job once again.
EDIT: Damned conversion from all caps.
ONE POINT FOUR JIGGAWATTS!
ACS FTW.
Great job Thomas. I'm one of those who can't push the processor past 1.2g. Despite that I have had the privilege of testing pretty much all of the Twilight kernels courtasey of Tanimn as well as the Vision kernel. Both are great kernels, and run smooth on my Epic as long as I don't push it to the highest clock. Never had a reboot or lock up pushing my phone with these kernels. Once gain thanks Thomas, I know how much time and energy you go into this kernel and it shows!
dreamsforgotten said:
Great job Thomas. I'm one of those who can't push the processor past 1.2g. Despite that I have had the privilege of testing pretty much all of the Twilight kernels courtasey of Tanimn as well as the Vision kernel. Both are great kernels, and run smooth on my Epic as long as I don't push it to the highest clock. Never had a reboot or lock up pushing my phone with these kernels. Once gain thanks Thomas, I know how much time and energy you go into this kernel and it shows!
Click to expand...
Click to collapse
You the man dreams, much appreciated my friend thank you!
Sent from my SPH-D700 using XDA App
OMGGGGGGG
Thank you !!!!!!!!!
..... So fast that Smartbench force closes
I'll try this in a few days, assuming my phone can handle 1.3 jigga hurtz first. Sure sounds good tho, thanks, I'll report back in a few days.
How is everyone's battery doing running this kernel?
nice I just downloaded this and about to set everything up. Thanks!!
Yea buddy....
Wheres me and dreams name in big red letters for pushing you to release this
Sent from my SPH-D700 using Tapatalk
can this be flashed on eb13?
MysteryEmotionz said:
Yea buddy....
Wheres me and dreams name in big red letters for pushing you to release this
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
If Tom is smart, he'll tell you the same thing I did: ***** please.
blspyro said:
can this be flashed on eb13?
Click to expand...
Click to collapse
Yes.
Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.
MikeyLee said:
Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.
Click to expand...
Click to collapse
Long story short: Quadrant sucks. Try a better benchmark.
k0nane said:
Long story short: Quadrant sucks. Try a better benchmark.
Click to expand...
Click to collapse
Any suggestions?
MikeyLee said:
Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.
Click to expand...
Click to collapse
Also you will get higher scores when you get off that old ass rom with old files and source. So like 4 months ago. Smartbench is good
Sent from my SPH-D700 using XDA App
How are you suppose to test stability of oc for your phone in setcpu? I ran the stress test at 1.3ghz with no errors was there other tests to confirm stability?
Sent from my SPH-D700 using XDA App
jbadboy2007 said:
How are you suppose to test stability of oc for your phone in setcpu? I ran the stress test at 1.3ghz with no errors was there other tests to confirm stability?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Try running something CPU intensive, such as Neocore or an3dbench.
Sent from my SPH-D700 using XDA App
And its resluts will tell me its unstable or will it be laggy or fc or re boot?
Sent from my SPH-D700 using XDA App
What I have here is a VERY BETA kernel built from the latest LeeDrOiD git with some ondemand tweaks to make it a bit more responsive, as well as AXI Scaling, an undervolted bottom end at 122mhz, and with a topend of 2016mhz.
Many phones may not run at the full upper-end, but vddsys is implemented as in the LeeDrOiD kernel, so you may increase or lower the VDD by 25 for 20160000mhz to attempt to get it working.
Currently working on getting a github page up with this source. I'm running it on the Unity rom at the moment without issue. 2016mhz should only be used for benchmarks, and not 24/7.
Two way call recording is also included, as well as a startup script to run at 1843mhz ondemand at startup.
Changelog:
June24-Initial Release...Working on Cleanup.
GitHub Page: https://github.com/synergydev
Will work on marking changes shortly. It should also be of note that because my GF's phone seems stable at [email protected], I changed the voltage at 2016 to 1.5 on the git just because it seems my phone likes high voltages.
I've tried 2000 a long time ago on my kernel, but my dhd couldn't handle it. and it handle very very low voltages, so didn't want to release a kernel with the freq that doesn't even work on dev's DHD I've even removed 1980mhz from my kernel because there really isn't any use of that freq rather than frying your DHD
I think that BuzzBumbleBee had 2000 on his kernel once, don't remember right
Good job BTW
edit:
wht is a working voltage on 2000?
I've trid up to 1.5V and it was unstable
LorD ClockaN said:
I've tried 2000 a long time ago on my kernel, but my dhd couldn't handle it. and it handle very very low voltages, so didn't want to release a kernel with the freq that doesn't even work on dev's DHD I've even removed 1980mhz from my kernel because there really isn't any use of that freq rather than frying your DHD
I think that BuzzBumbleBee had 2000 on his kernel once, don't remember right
Good job BTW
edit:
wht is a working voltage on 2000?
I've trid up to 1.5V and it was unstable
Click to expand...
Click to collapse
I'm using 1.525V at 2016, however my DHD could never run the 1.9986 in your kernel without a voltage bump (could undervolt all the way up to 1.8 however though). In this kernel, I needed to up the AXI clock at 2016 to even get it to run, let alone benchmark continuously. I still haven't been able to get it to scale with a minimum under 300mhz.
This is why I recommend reducing the VDD at that speed by 25 if anyone's DHD can't run it.
In response to the first section, I only released this because I'm an enthusiast overclocker when it comes to my desktops (water chilled and vapour phase change cooled), and I wanted my clock to read the magical "2" at the beginning for bragging rights. With AXI clock scaling, we should be able to get slightly better battery life as well at the lower clocks (at least on the N1 it seems they were able to get better battery life with it).
synergye said:
In response to the first section, I only released this because I'm an enthusiast overclocker when it comes to my desktops (water chilled and vapour phase change cooled), and I wanted my clock to read the magical "2" at the beginning for bragging rights. With AXI clock scaling, we should be able to get slightly better battery life as well at the lower clocks (at least on the N1 it seems they were able to get better battery life with it).
Click to expand...
Click to collapse
+1 on that, but don't think you're more enthusiastic when talking about OC
We can argue about that the whole day
looking forward for your git!
I think 1.2G is enough..
@LorD ClockaN: if that's an sense kernel, you know what you have to do
Your 2016 MHz ASOP kernel coming soon?
with friendly greet
starbase64
You will find the 1.8GHz+ frequencies being only theoretical, with no increase in performance with respect to a "speed bump".
I have tested that a few months ago, going as high as 2.2GHz.
The maximum "real" performance boosts only go up to 1.5GHz (I clock my kernels to 1.497GHz).
Run a smartbench, and the results will speak for themselves.
Unless you want to fry your DHD?
Tryng with virtuous sense 3 and it makes lag the sense but for the rest is quiet good
Edit: after some time the lags disappears and all is perfect now
where source code?
u canT post kernels on XDA without source code
m-deejay said:
where source code?
u canT post kernels on XDA without source code
Click to expand...
Click to collapse
He said he's working on the github page to up his source soon.So I think it's already in progress.
Good job by the way mate.Never liked the fact that kernels with the vdd interface restrict us to 1500mV!
m-deejay said:
where source code?
u canT post kernels on XDA without source code
Click to expand...
Click to collapse
What do you need it for?
Just add frequencies in multiples of 19200 to arch/arm/mach-msm/acpuclock-7x30.c
If the newly added frequency locks, add the next multiple and/or up the voltage.
No magic there.
tolis626 said:
He said he's working on the github page to up his source soon.So I think it's already in progress.
Good job by the way mate.Never liked the fact that kernels with the vdd interface restrict us to 1500mV!
Click to expand...
Click to collapse
Mine has voltage till 1.525 via vdd
Sent from Desire HD with CyanogenLordMod!!!
adwinp said:
What do you need it for?
Just add frequencies in multiples of 19200 to arch/arm/mach-msm/acpuclock-7x30.c
If the newly added frequency locks, add the next multiple and/or up the voltage.
No magic there.
Click to expand...
Click to collapse
really?
lol
Why do you explain to me?
m-deejay said:
really?
lol
Why do you explain to me?
Click to expand...
Click to collapse
Oohoo... Dev fight!! LOL
Sent from Desire HD with CyanogenLordMod!!!
wiped devik cache and flashed it to my honeysense rom and tha **** froze on startup lol any tips??
Lizzo said:
wiped devik cache and flashed it to my honeysense rom and tha **** froze on startup lol any tips??
Click to expand...
Click to collapse
Raise min freq to higher[around 1.1GHz+] to prevent voltage spikes which might be causing the freezes, try decrease the distance b/t the 2GHz and the min.
Ace42 said:
Raise min freq to higher[around 1.1GHz+] to prevent voltage spikes which might be causing the freezes, try decrease the distance b/t the 2GHz and the min.
Click to expand...
Click to collapse
uuuggghhhh... how do i raise the min b4 startup?
Lizzo said:
uuuggghhhh... how do i raise the min b4 startup?
Click to expand...
Click to collapse
echo 806400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
On adb you have to change the min freq while booting up. 800 might work. Or use 1305600 [1.3GHz].
This is madness, yes i know people will post no this is sparta, but seriously, anything over 2ghz i personally wouldn't test
adwinp said:
You will find the 1.8GHz+ frequencies being only theoretical, with no increase in performance with respect to a "speed bump".
I have tested that a few months ago, going as high as 2.2GHz.
The maximum "real" performance boosts only go up to 1.5GHz (I clock my kernels to 1.497GHz).
Run a smartbench, and the results will speak for themselves.
Unless you want to fry your DHD?
Click to expand...
Click to collapse
PMSL Benchmarks mean fuk all tbh do not reflect real world peformance running at 1.8/1.9ghz stuff like Playstation emulator etc run far much smoother and with no slowdowns etc... newbs and benchmarks lol!
is it possible to overclock the optimus 3D to 1.5ghz and above , because 1.5 worked on mine but not stable
Will not be stable. Even 1.4 ist stable for dayly use.
Edit. Sorry it is posible
please hit thanks if i helped
confused???
I don't understand that becuase 1.4ghz is perfect for me on thaiz v2.6.1 prada mix , with titan kernel , never rebooted or slowed down once , and scored 4556 on new quadrant , 4680 on old one , I am currently reconstructing an overclock app to get to 1.5ghz and be stable , but its hard , it should only be the voltage though , because i know the cpu can handle it.
Just so you all know, my Thrill 4G could go up to 1.67Ghz overclock and was stable.
It all just depends on the phone itself.
EDIT: I should also mention that I was using kernel with only init.d support. There wasn't any tweaks in it.
The Dark Lestat said:
Just so you all know, my Thrill 4G could go up to 1.67Ghz overclock and was stable.
It all just depends on the phone itself.
EDIT: I should also mention that I was using kernel with only init.d support. There wasn't any tweaks in it.
Click to expand...
Click to collapse
What You Get in antutu and Quadrant ? Damn 1.67 is crazy When i cross 1.388 Phone goes crrazy i Wonder whats the Highest clock the omap4430 can hit?
if 1.67 is possible ill make sure we all get 1.5 atleast , then well show the galaxy s2's who's boss , but i don't get a lot of time , I'm a school kid , but holidays are coming soon... ill make a kernel and rom before they end
Toxygen55 said:
if 1.67 is possible ill make sure we all get 1.5 atleast , then well show the galaxy s2's who's boss , but i don't get a lot of time , I'm a school kid , but holidays are coming soon... ill make a kernel and rom before they end
Click to expand...
Click to collapse
Lol the SGSII dev's aren't trying to go over 1.6GHz. We're already there, just don't want to destroy battery life.
Also, not every phone will be able to even make it to 1.5GHz for the fact that all the processors are built slightly different.
wow! with such a high overclock your battery will drain fast!!
The Dark Lestat said:
Lol the SGSII dev's aren't trying to go over 1.6GHz. We're already there, just don't want to destroy battery life.
Also, not every phone will be able to even make it to 1.5GHz for the fact that all the processors are built slightly different.
Click to expand...
Click to collapse
If you would please give a few secrets
sent from my acidhazard thrill
wayno140 said:
If you would please give a few secrets
sent from my acidhazard thrill
Click to expand...
Click to collapse
It was just the phone processor. Lol
I didn't do anything.
Sent from my Samsung Galaxy S II w/ DUAL BOOT: AOKP / MIUI