Related
Dirrk's Kernel Official Release
These are my kernels from samsungs crappy source! I am not responsible for you guys breaking your phone, which will happen if you do not FOLLOW THE DIRECTIONS. again FOLLOW THE DIRECTIONS.
Thanks to jt1134 for fixing voodoo, skeeterslint for helping me on the kernel builds and koush for clockwork and his ramdisk.
A lot of credit goes out to everyone in #samsung-fascinate on irc.freenode.net, they all helped contribute to jt1134s and my success and anyone who helped tests our 40+ versions before release.
If you want my source its all on github.
www.github.com/Dirrk
All of these kernels have the voodoo fix which is using ext4 for your /data partition. If you complain about your quadrant scores being lower you deserve a smack. Also sgtmack has confirmed that you can just install over jts if you choose to do so or any of my other versions.
SV = Standard Voltage and LV = Lower Voltage
Version D01 & D012 no animations
LV-1000
LV-1100
LV-1200
SV-1100
SV-1200
D02 with Animations
SV1100
SV1200
LV1000
LV1100
LV1200
LV1250
D01 & D02 Downloads
I just got the source for 2.2 and will be working on it asap.
These are clockwork installs. To be safe I would remove voodoo if you are using any of the older version already. To remove voodoo open your /sdcard/voodoo folder and make a new directory named disable_lagfix and restart your phone.
Enjoy
cool o mondo whats the dif between standard and low? and the highest is 1.2ghz right? do i need set cpu to make it work?
questions....
1. if we already have the latest 0.2 Voodoo Ext4 lagfix installed will this affect it?
2. do we need SetCPU?, i assume we do since this is a kernel not an app and i know we wouldn't be flashing an overclocking utility with no controllable GUI
If you don't use Setcpu, it will default to 800. So you can run it without, but it will be slower.
I did the remove_voodoo file thing to disable the first voodoo, then flashed this one. It worked great.
My phone doesn't like the 1200 lv kernel. I can run slower at lv, not 1.2. Every phone is different. If the lv kernel crashes, just flash the stock voltage one.
what scaling should we choose?
i installed SetCPU, chose autodetect
at first it showed 800Mhz max and 100Mhz min, after a few seconds it showed 1200max and 100min
"Conservative" is the default scaling, should we leave it that way?
jamesnmandy said:
what scaling should we choose?
i installed SetCPU, chose autodetect
at first it showed 800Mhz max and 100Mhz min, after a few seconds it showed 1200max and 100min
"Conservative" is the default scaling, should we leave it that way?
Click to expand...
Click to collapse
Conservative is the way to go...others have been known to cause issues.
so if lv doesnt work do we have to unistall it to flash sv?
No, I've been flashing over them with no problems. As long as the new kernel has voodoo, you can flash over the old one.
ok, something isn't right
already had voodoo 0.2 lagfix installed, fyi
before (with 0.2 voodoo lagfix already installed)
Linpack 8.128 MFLOPS
Quadrant 1646
after installing D01 1200LV:
Linpack 7.946 MFLOPS
Quadrant 1726
so i was like why is it slower on Linpack? rebooted
went into SetCPU, shows 1200max 100min, Set on Boot has never been checked and still isn't. conservative scaling still selected
i never had to re-do the autodetect, it went straight for 1200max 100min at boot without me doing anything
and now im getting 6.4's in Linpack......rebooted ran it, got 6.4, said meh, flaked out...ran again....6.4.....ran Quadrant, got 1481....
how exactly do we uninstall this?
Dirrk, can you share/quantify the actual voltage differences between standard and low. I'll assume standard is the max 1300mV??
jamesnmandy said:
ok, something isn't right
already had voodoo 0.2 lagfix installed, fyi
before (with 0.2 voodoo lagfix already installed)
Linpack 8.128 MFLOPS
Quadrant 1646
after installing D01 1200LV:
Linpack 7.946 MFLOPS
Quadrant 1726
so i was like why is it slower on Linpack? rebooted
...
how exactly do we uninstall this?
Click to expand...
Click to collapse
Just a suggestion: Before you uninstall, try wiping data/cache. When I was flashing all the earlier jt and Dirrk kernels, it always seemed to help with the quadrants.
I know it's not SUPPOSED to affect any of that stuff, but after a few flashes, my phone would start to act funny, and that cleared it up 100% of the time.
Good luck!
-Z
I just did the 1200 standard voltage and it is working beautifully
Seems like the downloads are the same as the ones without voodoo. Am i missing something? I dowloaded dirrk_sv1200.zip and the files in it are the same as the one before the voodoo fix.
Sent from my SCH-I500 using XDA App
doing the 1200 sv d01 dropped my quadrant score from 1805 to 1494. probably going to go back to the voodoo .02 lagfix.
johnnyv5 said:
Seems like the downloads are the same as the ones without voodoo. Am i missing something? I dowloaded dirrk_sv1200.zip and the files in it are the same as the one before the voodoo fix.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You got to do the d01 ones.
I'm being directed to Google docs when I click the link am I missing something ?
magicriggs said:
I'm being directed to Google docs when I click the link am I missing something ?
Click to expand...
Click to collapse
That's correct. Log in and then refresh. You will see the list.
1750 quadrant/7.99 mflops on LV 1200
LV seems stable through a few rounds of benchmarks
Does LV not go up to 1200 that often or is that just me?
Q: If I install one of these kernel's would re-flashing/reverting back to the stock kernel be an easy task (just some Odin work)? Or would it be more involved?
Edit: I see that you can flash these kernel's on top of each other. I'm just wondering if you can flash the stock kernel on top of these as well or if that would cause problems. Thanks!
Hello
I've got a problem
well I'm using the Setcpu app and i've got everything to work and it's overclocking my LG Optimus t to 806MHz but sometimes it crashed the phone completely and I have to take the battery out because it's completely unresponsive.
dose anyone know what's the problem because I know my phone can do 806MHz but it just crashed after a hour or so.
Your phone obviously can't handle it. Set it to a lower clock speed. This is normal in overclocking. Not all copies of the same hardware are capable of the same speeds.
dam ok ill try 800MHz that might help
You should read about these things before you make any changes..... 730mhz is the stable clock speed that has been tested.
yh well I am new to Android so I don't know everything.
Dont push your CPU to do frequencies it cant. Unless of course you want an expensive paperweight.
748 Mhz is more than enough overclock. Infact Stick to 729MHz.
The simple rule for OC is to increase freq step by step. Increase one step. Test if its stable. If it is then increase one more step. Test again. If not stable decrease to the last stable state.
is it must root ur phone then can overclock the processor ?
yes but once you've rooted your phone and you've got a overclock app EG: setcpu.
but if it's not letting go past your phones original cpu frequency then you will need a to install a custom kernel.
http://forum.xda-developers.com/showthread.php?t=901247
That link will take you to a selection of kernels you can chose from.
Then put the ZIP file on the root of your SD card.
Then you will need to install it via your custom recovery mode and install it from your SD card.
alex ainsley said:
yes but once you've rooted your phone and you've got a overclock app EG: setcpu.
but if it's not letting go past your phones original cpu frequency then you will need a to install a custom kernel.
http://forum.xda-developers.com/showthread.php?t=901247
That link will take you to a selection of kernels you can chose from.
Then put the ZIP file on the root of your SD card.
Then you will need to install it via your custom recovery mode and install it from your SD card.
Click to expand...
Click to collapse
okays,thx for ur explanation
will flashing void echo custom rom once i buy new microsd
but,once i buy microsd
how i flash ??
copy all content on current stock microsd to new microsd ??
http://tablet-crunch.blogspot.com/2011/01/video-tutorial-how-to-root-install.html
Check this video i did it this way and it went smoothly.
And my phone only gets a 948mHz max overclock.
Mike Shinoda said:
http://tablet-crunch.blogspot.com/2011/01/video-tutorial-how-to-root-install.html
Check this video i did it this way and it went smoothly.
And my phone only gets a 948mHz max overclock.
Click to expand...
Click to collapse
I hope you meant 748!
Else its Snapdragon territory!
Hey guys, I'm currently running CM6, and when I tried to upgrade to CM7, from the version with overclocking and undervolting added, my fone always reboot and lag continously, unusable until i restore using factory reset.It never happened with any previous version of CM7. A couple day back, I tried the overclocking tweak for CM6, and the same thing happens. I have to restore using Xrecovery. Does anyone knows what the problem is ? I really want overclocking function
stable overclocking is 768 or less.... this much i knw some dev will help you
You did say that you used the overclocking patch , but did not tell did you use SetCPU with set on boot option ? Also what is ur max and min settings in setcpu ?
Anyways , not sure if you will now be able to go inside setcpu , since ur phone is restarting.
On mini pro , for me 780+ Mhz caused reboot. And if you have setcpu set to set it on each boot , then u will end up in infinite loop. For me it happened , but luckily if you do not touch ur phone (touch screen touch ;-) ) after a reboot , it wont reboot (atleast for me).;
So after a reboot :
1. connect phone to PC
2. use adb to uninstall the setcpu
3. reboot again.
This time you should not be having trouble as your phone should behave normally.
Again install setCPU (if you are interested still !!) and set the max to anything below 760Mhz.
What should we do if there is the reboot loop but setcpu is already uninstalled? Or if its installed but overclock is not set on boot?
Hey thanks for the help, but I can't do anything at all with the phone after the patch, with or without setcpu. It booted up, on lockscreen, lag for 30sec and continous reboot then -.-''
Sent from my U20i using XDA Premium App
will make much more sense letting people know what you have done. Just the normal OC module should not have ur phone rebooting.
Does the phone reboot if you do not touch it but just keep it connected to PC ? please answer or else its very hard to try and figure out an answer.
if you feel its causing an issue , then u got to figure out a way to disable that module.
The module gets loaded as x8oc.ko.
In CM6 - v4 , this is not there by default but will appear in hw_config.sh if you have patched it.
So u got to get /system/etc/hw_config.sh and comment out the line insmod for x8oc.ko and anything associate with it .
Did fresh install of v4 after factory reset, resulted in no overclock options and completely stable. Installed oc zip from cm6 oc thread which resulted in infinite reboots even when attached to pc, was not able to touch any settings. Reflashed v4 without factory reset and am back to no overclock and completely stable. Setcpu was not installed, recently installed on fresh v4, no options beyond 600mhz.
yep ..if u did a fresh install of v4 , it means the overclock is not functional as the module is not loaded in it.
Changelog for v4 says overclocked and undervolted, but never mind that. Installing oclock.zip as per instructions in that thread results in infinite reboot, does not stay up long enough to use adb shell or access setcpu. The fresh install of v4 does have overclock options in cyanogenmod settings, but values cannot be edited.
Are you implying that v4 will not support the oclock.zip or simply replying only to first sentence of explanation?
Any help is appreciated.
ok . so let me explain ( i know its quite hard on both ways ) . The overclock module (x80c.ko) is NOT loaded by the default V4 version. So if the module is not loaded Cyanogen setting will only show you the max (600 Mhz i thnk) and min (122 Mhz - I think). I did not find that module to be loaded in any of the init* scripts or in hw_config.sh. But the module is present with the build in the modules folder (but not active as its not loaded with insmod).
So if you just coming just after applying V4 - with no other patch. Then you do not have active overlocking module - hence overclocking wont work with SetCPU. Cyanogen does NOT provide you a scope to change the frequencies - you need setCPU - (you can change the max thru command line after enabling the module).
Now if you have patched the same with the oc patch , you have the module active (insmod works) , but another line of it in the hw_config.sh (patched one) does not become effective for me (some people reported it worked for them though).
The constant reboot which i faced was because i (with the help of SetCPU) had set very high frequency (causing the system to become unstable).
So inorder to fix it , you can do the following:
1. Full wipe through xrecovery
2. Apply V4 again.
3. Change hw_config.sh to add the insmod command to load x8oc.ko module.
4. Reinstall setcpu and see if you can set the max/min to safe values (say around 719 Mhz max and min as 300 or 400 Mhz).
5. If you see the system to be stable , well and good.
If by above , setCPU does not detect max/min (max should be 825 Mhz) , then you need to add the echo x27 > /proc/x8oc to hw_config just after the insmod line of x8oc.ko. (you will see some threads where sleep 2 or sleep 4 is also asked to be put in , but for unknown reason it did not work for me).
Whew!! that was long . But thats the way it worked for me.
For me when the reboots were happening , i had my phone connected to PC , but i was not touching the phone at all (if i touch , it used to reboot - but adb shell was working if i do not touch it).
If any further clarificaiton required , i would be glad to assist.
But before puting in a query , please try and give as much information was to what you did after which the reboots started (not just saying that i did the OC patch - cos for me just the OC patch never resulted into the reboots).
Thank you for that awesome explanation and sorry for the lack of relevant information earlier in the thread.
Should be able to do as you have suggested when I get home and will report back, either way your explanation has made it all clear and I can see where I have missed important steps. Many thanks.
Edit: edited hw config.sh, inserted insmod, sleep and echo lines. Stable ay 729, reboots at 748. Thanks again
good to know it worked !
same problem with my minni.... reboot again and again
Check your baseband, it must be xxx15 or it won't work because of different kernel
Nah got everything rite, basband and kernel, just when I apply the OC tweak, the fone would boot up, but freeze at lockscreen. IT DOES BOOT UP, BUT STUCK AT LOCKSCREEN !!! So bloody annoying, then stuck on bootloop until restore /system using xrecovery
Sent from my U20i using XDA Premium App
Don't apply the oversclock tweak from xrecovery, instead try editing hw_config.sh to have:
# x8 overclock
insmod /system/lib/modules/x8oc.ko
sleep 2
echo x27 > /proc/x8oc
I believe i had the same issue until i did this, then it was stable.
my mini max cpu is only 691 mhz or else the reboots and its laggy as hell. LIKE all your work every wear
have your lovely MDDI on to it help alot but still scrolling lag. maybe fresh install via seus?
wrong thread
I installed Setcpu everything was working great till I lowered the the minimum Frequency to around 700MHZ & I checked the "Set On Boot". It started to reboot the phone continuously I went back unchecked the "Set on Boot" which helped but when I go back in Setcpu it would reboot again.
I tried setting the frequency to the max & it would freeze & reboot quicker. I tried putting the Setcpu safemode in the root of the sd card but it didnt do anything.
I uninstalled SetCpu & updated the RUU on my Rezound it solved the reboots & it seemed everything was running as normal until when the phone was auto-syncing the phone froze for about 10-seconds then everything was back to normal. I heard about flashing the .zip file but I don't know how & I'm not installing Setcpu again to find out.
I'm wondering if the freeze had anything to do with the SetCpu. Everything is deleted once you update the RUU so I don't believe there should be any left over files from the SetCPU. I'm not sure if there on my sd card I was thinking of formatting the SD.
It would never freeze like that before I installed the new update but I never did have Setcpu installed once I got the phone. So I'm wondering if this problem lies with the Setcpu or the new RUU update for the Rezound which is 2.01.605.11?
Probably SetCPU, if you tweak the setting too much (or putting it in awkward settings) it can create errors.
Might have to do with which kernel you are running. Some kernels, such as dsb, play better with certain cpu apps. dsb likes Antutu CPU Master.
Hmm could be something on the user side like kernel or perhaps if you installed a bad downloaded stock rom because I have have been using setcpu since day one with no errors on stock kernel on any rom. If you had a kernel installed prior it may still be installed which allows the cpu to ramp up to unstable speeds such as >1512 mhz.
Even if you were to try set an OC kernel to stable speeds, it will always ramp up to highest speeds, even higher than set. All in all, I would recommend to reflash stock kernel and made sure to flash boot.img which is most important. Hope this helps!
feralicious said:
Might have to do with which kernel you are running. Some kernels, such as dsb, play better with certain cpu apps. dsb likes Antutu CPU Master.
Click to expand...
Click to collapse
eh, dsb hasn't given me problems with SetCPU.
Weird
I only use setCPU, I have all the other ones too just about but they are all uninstalled because they usually just don't work as well, I use incredicontrol for undervolting, and that's it. Dsbs works with incredicontrol too... The kernel could be the issue and not the app but who knows
I'm currently using meanrom ics 2.6 and I've tried butteredtoast kernel and anthrax and mac kernel and none will allow me to change frequencies on the fly. I'm wondering if it is a rom script or if anyone knows how to fix it. I have read that many people have had problems with anthrax kernels but i can't get them to stick with any and there isn't any real clear answers i could find, but a few of the same question.
and help would be greatly appreciated:good:.
If I remember right, meanrom has post boot scripts that set frequencies. You'll have to remove Mikey's tweaks. Look in init.qcom.post_boot.sh .
Do you know where his scripts are because i have deleted the init.qcom.post_boot.sh and the problem still persists
I have tried setcpu and cpu master and neither will keep the settings. They have changed for anywhere between 1 minutes to about 3 hours but i will turn on the screen and the widget and app will show the default speed of 1.5ghz
rockerdudelive said:
Do you know where his scripts are because i have deleted the init.qcom.post_boot.sh and the problem still persists
Click to expand...
Click to collapse
Also are in /system/etc/init.d/