Related
Normal: http://www.tabbal.net/files/Dragon-Kernel-Voodoo-v3.1.2.zip
OC: http://www.tabbal.net/files/Dragon-Kernel-Voodoo-OC-v3.1.2.zip
I rebased on the latest source from Samsung, JPX. Yes, it's still i9k based. Hopefully it helps a little with battery and such, won't know till it's been out for a while. The speedmod patch has also been updated, but the OC patch is the same. I also included my backport of the auto-group scheduler patch. So far, both of them are working well for me.
Both kernels are voodoo enabled and will enable voodoo if you don't already have it. If you don't want that, you need to install the voodoo-disable zip before flashing, or just put the disable-lagfix file in place before flashing. If you already have voodoo enabled on your phone, you do NOT need to disable it before flashing these kernels, as long as your current kernel has voodoo recovery (red Clockwork recovery), you are good to go.
Tested on Nero V5, but should work on other Froyo based ROMs as well.
If you are going to try the OC version, please download both of them and have the normal version ready, just in case. You can also use adb push from Clockwork if you can get it booted to recovery. Clockwork also has USB storage you can enable to be able to mount your phone's memory cards from a computer, so that you can put the non-OC version on there if you get stuck.
NEW for OC users.
The OC kernel defaults to 1Ghz. To enable OC, you can use the Voltage Control app that the OC ZIP installs for you. This is a MODIFIED version, so please don't update it. Load the app, then pull up the "states" drawer at the bottom of the screen. Select the frequencies you want to enable. Then set the "Limit clock to" spinner to set the max clock rate the system will use. You can change the UV settings if you like as well. To test, hit menu then apply for now. When you are happy, use "save as boot settings" and the system will set the frequencies at boot. I recommend you only change one thing at a time, and throughly test, before setting at boot. Bad OC/UV settings can cause all sorts of instability issues. Flash the stock clocked kernel if you get stuck, then delete /system/etc/init.d/S_volt_scheduler before flashing the OC kernel back on. That will force the system to boot limited at 1Ghz again. If you are so stuck you can't get to recovery, you can use download mode to apply a stock kernel with heimdall, just pull the zImage from the ZIP and flash that.
I'm not sure it will help anyone to post your OC/UV setup as every phone is different. But feel free to try it if you like. I haven't done much more than test that it can set the options and my phone is still running fine at 1280. I'll experiment with other speeds and such later.
Please note: Not every phone will work at any particular frequency. Many can run 1.4 just fine, others can't do much better than the stock 1Ghz. I recommend trying one step at a time, and testing throughly before setting at boot. Run some games and such to really push the system. I also recommend using only one or two OC settings enabled in the states. Every frequency step requires the system to notice you are asking for more CPU than the threshold, resulting in lag getting up to speed. I run with only 1400 enabled from the OC section and disable 200 just to speed up the transitions.
Changes from v3.1.1
Fixed sensors (auto rotation, auto dim screen, compass, etc)
Updated OC code to be more stable, courtesy of Morfic. Many thanks to him for providing code and assistance.
Updated Voltage Control app to reflect the standard voltages used.
My phone runs stable at 1.4Ghz now.
Changes from v3.1:
Fixed Mobile AP on Bionix V.
Changes from v3.0:
Updated speedmod patch to k12p
Updated Voodoo Sound to V2
Credits:
Speedmod patch from here: http://forum.xda-developers.com/showthread.php?t=822756
OC patch from here: http://forum.xda-developers.com/showthread.php?t=822027
Supercurio for voodoo and voodoo sound
Sweet!! gonna test it out now..thanks for this!!
Downloading now
THANK U!! flashing right now (normal version)
just flashed it and for some reason screen looks dimmer (to conserve more battery i guess??) or is it just me? one more thing speedmod is not really necessary right?
So this thing helps with battery?
Sent from my SGH-T959 using XDA App
downloading now...was just thinking about flashing the new trigger rom from Einherjar to try it out....will flash this with it and report back any problems
Been running the OC kernel at 1280 with CFQ, everything runs smooth and lightning fast!! Not one reboot or freeze up. Linpack is in the 20's. Thanks again T!!!
Edit: had this running on my phone for almost 2 hrs
KA6 DeOdexed
Will this work on the KA6 DeOdexed leak rom with voodoo lagfix enabled?
So far, so good at 1.2
Nicely done. I had 2.7 for a few hours and it kept freezing up. Hope this is the sweet spot. Just for clarity, the only difference between "apply for now" and "save as boot settings" is that the settings will need to be re-done when rebooted? Sorry if that's a completely "duh" question. One more: having the Voltage Control app now, is it recommended to freeze or uninstall Set CPU, or does Voltage Control trump Set CPU, or, vice versa? I notice the main screen does theoretically allow the slide bar to go to 1.4. TIA...
It's running great. At first, it got stuck while flashing the kernel and I had to odin back but it's fine now.
As far as battery life is concerned, it has only been about two hours so I can't say. The kernel itself has voodoo sound v2 so even ttabbal hasn't had it for long (as that JUST came out) so no one will know what kind of battery life the phone has.
On a side note: ttabbal: Did you get my PM about the FM radio? Is the module loaded trying to access the non-existing hardware? I wonder if that is what's killing the battery on the non-vibrant kernels. (Doesn't the 959D also have a FM radio?)
I tried to push it to 1400 with cfq but got a freeze up instantly. Went back to 1280, now everything is running smooth again. One thing I noticed though, my wifi is broke
My wifi is working...did yours stop working after you pushed 1400?
w00t! thanks ttabbal for being the Dev to provide Voodoo sound!
Mine stopped at 1.4 too. But right now im running 1.2 with 25 under. 25 under on 1. 50 on most the others except 100 which I went 75 under. Right now its really stable and fast so ill leave it like this for boot and try other stuff with the apply now. Hint only hit on boot if its 100% stable. Be careful with setcpu too.
Sent from my SGH-T959 using XDA App
Fedburin said:
My wifi is working...did yours stop working after you pushed 1400?
Click to expand...
Click to collapse
Yeah..noticed it stopped after I pushed 1400.. So be warned
love your kernels. i will have to donate again
So does this kill the wifi hardware at 1.4? If so, ttabbal has to modify the first post. (Or I will do it if he doesn't and we start getting more people complaining.)
On another note: Voodoo sound = gooooooood
Anyone else notice the automatic brightness setting is WAY dark? I've been running the T959D dragon kernel and this one is alot darker by default.
Thanks for the heads up.
Sent from my SGH-T959 using XDA App
bahnburner said:
Anyone else notice the automatic brightness setting is WAY dark? I've been running the T959D dragon kernel and this one is alot darker by default.
Click to expand...
Click to collapse
yeah, its the new version of speedmod that he incorporated, link to that thread is in the op
Probably is something on my Nook Color. But since I upgraded yesterday from 41 to 7.0.2 there is noticeable degradation of youtube videos playing on the default browser. Used to be fluid now is very choppy.
About the NC
Stock ROM 1.20 (upgraded yesterday)
CM 7.0.2 (from SD using Verygreen's instructions)
NO other kernel changes
EDIT: I think I confused everyone on my post..
I meant that I kept the NC stock ROM and upgraded to the new one (1.2) released by B&N on 4/25
The NC is running CM 7.0.2 from uSD without kernel changes. CPU settings: Performance. Max: 925Mhz
Haven't had that problem, have you tried flashing with the new kernel, OC at 1.3, check it out... that might help.
Do you know if after updating CM7 I need to reset or clear something?
I guess that could be the cause of my issues.
There's a 1.3 kernel??? Dalgrin's? Where?
silentbushido said:
Haven't had that problem, have you tried flashing with the new kernel, OC at 1.3, check it out... that might help.
Click to expand...
Click to collapse
shawn605 said:
There's a 1.3 kernel??? Dalgrin's? Where?
Click to expand...
Click to collapse
Kernel Manager app
Do not set the overclock on boot until you know its stable.
Have not had that You Tube problem here.
Dalingrin's beta kernels are up to 1.2 and 1.3 I believe; but they are beta; 1.3 would not load on my CM7.02 set up at all, and then you have to revert back to get your tablet back. Others are reporting it is working fine, but the safe bet is to wait until he officially releases one IMO.
LBN1 said:
Have not had that You Tube problem here.
Dalingrin's beta kernels are up to 1.2 and 1.3 I believe; but they are beta; 1.3 would not load on my CM7.02 set up at all, and then you have to revert back to get your tablet back. Others are reporting it is working fine, but the safe bet is to wait until he officially releases one IMO.
Click to expand...
Click to collapse
The 1.3ghz is ready to release. It is just a matter of whether your Nook can handle the overclock or not. It should boot regardless though. The overclock is not set until after the OS boots to UI.
did you have OC before installing 7.02? installing 7.02 resets your cpu back to 800 MHz, and you need to reinstall OC kernels to get it back to what you had before
lanzagas said:
Do you know if after updating CM7 I need to reset or clear something?
I guess that could be the cause of my issues.
Click to expand...
Click to collapse
Been using the 1.3 oc kernel flashed through kernel manager. Seems to be working fine at 1.3 with oc set in cm settings.
No YouTube issues for me on new cm7.
Loving my week old nook color so far.
Sent from my HTC HD2 using XDA App
I didn't have a OC kernel before nor after.
I was using CM7 CPU settings. Max:925Mhz.
I had the 1.1 stable overclock before and currently am using it again. When I added the 1.3 uimage onto my Nook and tried to reboot, it stopped before the CM7 logos popped up. Blank screen with a "-" cursor and that's about it.
Glad to hear it is almost ready to be released, and will certainly try it again.
Oh, thanks Dalingrin for all your hard work on the kernels!
When I plug my phone in to charge it stays at 800mhz instead of throttling down to 100-400mhz like its supposed to. I'm on pinnacle ROM and its taking forever to charge. Anyone else have this issue and maybe have a fix for it? Thanks.
Are you using Tegrak?
Yes, I do have it set to throttle down and using Ondemand scheduler.
Kill it and check if it get fixed. I recommend rebooting it after you change tegrak's settings.
Killing it seemed to have worked for now. How can I fix it so I can still overclock? It hasn't done it all the time, Just recently but I haven't installed any new apps or anything.
Sent from my Cappy using the XDA app.
Try clearing the app's cache. Maybe even Dalvik if you have too? Don't know.
I'll try, thanks man.
Sent from my Cappy using the XDA app.
well, getting rid of tegrak didn't help. Still charges and stays at 800mhz.
Sent from my Cappy using the XDA app.
Try unistalling it then installing it? I've used tegrak on 2.3.3 and 2.3.4 and never had any issues with it.
prbassplayer said:
Try unistalling it then installing it? I've used tegrak on 2.3.3 and 2.3.4 and never had any issues with it.
Click to expand...
Click to collapse
Tried that and still no difference......can't figure it out.
What Freq and Voltage you running on each level? Are you using Tweaks? You said you had it "Ondemand" scaling but what min-max Freq?
Edit: I decided to test Tegrak on a 2.3.5 Beta Fusion build, seems to work fine.
Edit 2: Flashed another 2.3.5 beta build and I got that problem you had. Ill keep looking in to it
prbassplayer said:
What Freq and Voltage you running on each level? Are you using Tweaks? You said you had it "Ondemand" scaling but what min-max Freq?
Edit: I decided to test Tegrak on a 2.3.5 Beta Fusion build, seems to work fine.
Edit 2: Flashed another 2.3.5 beta build and I got that problem you had. Ill keep looking in to it
Click to expand...
Click to collapse
It might be a problem with something included in Pinnacle but I can't narrow it down.
Ondemand 100min-1200max with stock voltage settings.
Na Fusion VII Beta is doing the same thing. I think its a tweak on the kernel maybe? I've been kinda busy and will be for the next few days, so don't know when I'll mess with different kernels.
I'll try the other kernel option and see what I can find.
Sent from my Cappy using the XDA app.
I'm having the same issues on continuum with latest talon kernel. And it's been installed on my phone for weeks now and the problem just started. I also have an issue with media server running constant and it gets the phone hot and drains the batt....not sure if the two things are related, but it all just happened all of a sudden.
rmntruexjr said:
I'm having the same issues on continuum with latest talon kernel. And it's been installed on my phone for weeks now and the problem just started. I also have an issue with media server running constant and it gets the phone hot and drains the batt....not sure if the two things are related, but it all just happened all of a sudden.
Click to expand...
Click to collapse
Using cpuspy or other monitoring software, what speed is it stuck at when charging? Are you running tegrak as well?
Sent from my Cappy using the XDA app.
Well tried a fresh install of Fusion and it still does it......
Geezer000 said:
Well tried a fresh install of Fusion and it still does it......
Click to expand...
Click to collapse
Ya Just used Fasty KI2 and It does it with out Tegrak. What ever it is, its anoying not enough to reflash to stock to check if its the rom or kernel.
prbassplayer said:
Ya Just used Fasty KI2 and It does it with out Tegrak. What ever it is, its anoying not enough to reflash to stock to check if its the rom or kernel.
Click to expand...
Click to collapse
I have flashed Fasty ki2, Fusion, Pinnacle, Apex and so far they all do it with or wothout tegrak.
Fresh look bump.....
I have galaxy s since last one year and i love it... However my phone has become very slow these days.. I tried several roms and kernels.. Formatted both internal and external SD cards... But still it is very slow... I remember that I dropped it 3-4 times... Is it because of it?
Can someone suggest me please... What should I do...
Sent from my Galaxy S using Tapatalk
Maybe over clock it ...? I thought the new ROMs would have helped. It could be the fact that your phone is older now and some internal hardware has been worn out
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)
309041291a said:
Maybe over clock it ...? I thought the new ROMs would have helped. It could be the fact that your phone is older now and some internal hardware has been worn out
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)
Click to expand...
Click to collapse
Can I do anything related to the hardware? I mean how can i check if it is not giving 100%?
Sent from my Galaxy S using Tapatalk
I'm no expert so I'm not sure. Best bet would be to replace the hardware which Costs a ton of money. Its better to just a get a new phone. Either that or maybe mess around with new ROMs some more. Maybe you are wiping your phone incorrectly or maybe you use it too much
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)
my suggest...
1. update your firmware to last version (2.3.6).
2. try to change kernel and custom rom.
3. maybe, with some different kernel and custom rom, you can choice the better option for your device. for example, try using kernel semaphore (gingerbread) and custom rom F1 or other.
I would be very surprised if physical trauma has simply caused a slow-down in speed. It would more likely show itself as random reboots and other more obvious symptoms.
Much like Windows, after a lot of use, it slows down - you have said that you've flashed other roms, maybe you just haven't come across a good one; there are after all a lot of different ones...
I would suggest the deodex-ed / rooted stock rom from RAMAD Gingerbread JVT. As I remember it was always quite stable and fast.
The hardware components inside a modern phone will not wear-out after a year - they are not moving parts! - when ram or a processor wears out it usually results in total system crashing not just a slow down.
Thank you all for your feedbacks and suggestions. I use my phone a lot. Usually i use TV out a lot as i do not have a cable connection in my hostel room. I use my phone a lot. I flashed it atleast more than 100 times. I have not seen any reboots, crashed , soft reboots etc very often. When i use MIUI rom my phone is very fast indeed however , it does not have a TV Out and therefore i have to use a stock based rom.. i will try Rammad's GB Rom as per your suggestion and will report back. As i told you that i dropped it a couple of times, is it possible that any of the Internal components have become loose?
Have you ever tried Advanced task killer? Or even killed tasks?
zadusimple said:
Thank you all for your feedbacks and suggestions. I use my phone a lot. Usually i use TV out a lot as i do not have a cable connection in my hostel room. I use my phone a lot. I flashed it atleast more than 100 times. I have not seen any reboots, crashed , soft reboots etc very often. When i use MIUI rom my phone is very fast indeed however , it does not have a TV Out and therefore i have to use a stock based rom.. i will try Rammad's GB Rom as per your suggestion and will report back. As i told you that i dropped it a couple of times, is it possible that any of the Internal components have become loose?
Click to expand...
Click to collapse
Did you try the ics roms. These r pretty fast..specially team icssgs.
Sent from my GT-I9000 using Tapatalk
Try ICSSGS RC 4.2. I had the same situation as you. It was fine for one year and I was using Darky rom by that time. Suddenly I started feeling that my phone is too slow. Lot of stuck. Sometimes I had to remove battery just to restart.
Now running above ICS rom with Devil 14.2 Kernel its rocking ...
yeah I'd suggest u the advanced taskkiller too
in options you can set the auto killlevel to safe, so that it kills smth like games in the background but not important apps
since then my phone is quite fast even with stockrom
gezze said:
yeah I'd suggest u the advanced taskkiller too
in options you can set the auto killlevel to safe, so that it kills smth like games in the background but not important apps
since then my phone is quite fast even with stockrom
Click to expand...
Click to collapse
Yeah, and you can just use the ATK widget when you close out of something press the icon and it kills all the background apps...
I will surely try ATK and ICS roms as per your suggestions...
Sent from my Galaxy Nexus using Tapatalk
keep us updated...
Just get stock jw1, flash with reparation to wipe everything, then do a factory reset via secret dial code. Now install semaphore 2.5.0 kernel. Dl superuser to get root. Now install thunderbolt tweaks the main package and the 60lmk other addon(read thread how to) . This is the best setup i can think of in terms of speed bat life and functionality. Next step look in pikachus Android optimization thread and remove the bloatware listed there, basically remove as much bloat as possible. Enjoy ur fast phone.
Sent from my GT-I9000 using Tapatalk
Perhaps you should try the ICSSGS RC4.2 with Devil 14.2 LED VC Kernel. I'm on it and its awesome, my phone lags no more and I'm using it for my primary phone.
Sent from my Galaxy S using XDA Premium
Hello friends.
I have a Galaxy S 9070 almost 1 year old and he is currently rooted and the Cocore 9.8 TWRP and use Cocore Manager to adjust the kernel options.
From a while now he began to crash randomly, sometimes crashes when squeegee Facebook app, Whatsapp app, in the middle of a video in Youtube app.
It is very annoying having to restart the phone to continue what I was doing!
Could anyone help me figure out what might be happening?
henriqueberthem said:
Hello friends.
I have a Galaxy S 9070 almost 1 year old and he is currently rooted and the Cocore 9.8 TWRP and use Cocore Manager to adjust the kernel options.
From a while now he began to crash randomly, sometimes crashes when squeegee Facebook app, Whatsapp app, in the middle of a video in Youtube app.
It is very annoying having to restart the phone to continue what I was doing!
Could anyone help me figure out what might be happening?
Click to expand...
Click to collapse
Did you overclocked it? If you did - that is the reason.
I'm not using overclock.
Min clock: 200mhz
Max clock: 1000mhz
Hovernor: pegasusq
I/O: sio
henriqueberthem said:
I'm not using overclock.
Min clock: 200mhz
Max clock: 1000mhz
Hovernor: pegasusq
I/O: sio
Click to expand...
Click to collapse
Try using CoCore 8.2. And revert settings that you have changed to default and see what happens.
Deepsleep should be 3 or 4, on 5 it gives same result that you are getting. Freez and reboot on some time.
My deepsleep is "3".
henriqueberthem said:
My deepsleep is "3".
Click to expand...
Click to collapse
Then do first thing I told you before that. Without any customization, and with 8.2 version.
Ok, I'm going to flash to 8.2 cocore and keep the default configuration for testing
I tested version 8.2 with the settings in stock and did not freeze in no time.
But I think this version a bit outdated. Could test a newer version?
I looked today launched a new version of cocore, I think I'll install it and test.
In my archives I also have the 8.3, 8.6 and 9.6.
henriqueberthem said:
I tested version 8.2 with the settings in stock and did not freeze in no time.
But I think this version a bit outdated. Could test a newer version?
I looked today launched a new version of cocore, I think I'll install it and test.
In my archives I also have the 8.3, 8.6 and 9.6.
Click to expand...
Click to collapse
Try that newest.
8.2 was pretty good. No matter if it is old.
I tried the newest (Cocore E-v10) and still suffering from random freezes, causing the responses to touch are noticeably slower.
At this time I will flashing to version 9.6
Hello friend.
I tested the newest version of the kernel (refresh-r08 @ 14-Jul) and a few days ago that had no reboot.
But before I used the app tweek (cocore manager v2.1 or Kui) and believe they left is that my system unstable, because after that they uninstalled and I started to tweek the command promt using the Busybox my system has become lighter and reliable.
So it leads me to believe the problem was in the app customization.