Android OS Forum banner
1 - 20 of 1239 Posts

·
Premium Member
Joined
·
2,255 Posts
This is not my usual leanKernel since source code for GB kernel is not available yet. It's basically the stock leak kernel repacked (using supercurio's repack utils) with modified initramfs.

Features
  • full voodoo lagfix support. voodoo sound support via voodoo control plus. (until kernel source is available there's no native voodoo sound support - you must get the voodoo *plus* app which will come with a loadable module which works mostly with the stock Charge gingerbread kernel.)
  • buffers, minfree, memory tweaks
  • init.d support
  • custom boot animation support (bootanimation.zip location depends on binary included in ROM, should be either /data/local/bootanimation.zip, /system/media/bootanimation.zip, or /system/media/sanim.zip)
  • auto root & busybox fix
  • custom boot sound support (copy your mp3 to /system/media/bootsound.mp3, and reboot)
  • smartassV2, interactiveX, and CIFS module support
Changelog
  • v0.9 - initial release based on ep1q
  • v0.11 - turns out boot animation support wasn't working right, i hacked things a bit so it would work mostly. Place your bootanimation.zip in /system/media.
  • v0.20 - ok, really got bootanimation to work, i think... Also made some more memory related tweaks. If things are weird, go back to older version.
  • v0.22 - just some bootanimation clean-up. No need to update if you don't care about bootanimation
  • v1.0.1 - now based on ep1w stock kernel. Only tested on ep1w leak ROM although it should work on ep1q as well. bootanimation.zip location depends on the binary that comes with ROM (either /system/media/bootanimation.zip or /system/media/sanim.zip).
  • v1.0.3-ext4 - experimental auto ext4 conversion kernel. Use it at your own risk. should convert /system and /dbdata only. Fall back to v1.0.1 if things fail.
  • v1.0.5-ext4 - /data and /cache auto conversion to ext4. Still experimental - backup before flashing.
  • v1.1.0ext4 - enables some ext4 specific features for performance and reliability. also does file system integrity check at every boot. backup before flashing.
  • v1.2.0ext4 - some minor cleanup. fixed things so lagfix shows up as active in voodoo control app.
  • v2.0.0voodoo - worked with supercurio for proper gingerbread voodoo implementation instead of hacked froyo voodoo. Still needs to be tested more - please back up before flashing.
  • v2.0.2voodoo - i think i fixed voodoo not calculating sdcard available space correctly. also reverting back to rfs should work properly as well. *back up before flashing*.
  • v2.0.4voodoo - sdcard free space calculation more accurate and robust. Don't need to upgrade from 2.0.2 if filesystems converted fine.
  • v2.0.6voodoo - compiled voodoo's builtin busybox myself, should handle conversions for ROMs other than TBH now.
  • v2.0.7voodoo - minor update: fixed a small bug in minfree setting, added some error checking.
  • v2.0.8voodoo - removed safeguard error checking for now, it was causing phone not to boot sometimes.
  • v2.1.0voodoo - stock boot animation and sound support. (remove bootanimation.zip and reboot to get stock animation/sound, *provided* that your ROM left the stock media files in /system/media)
  • v2.2.3voodoo, v2.2.5voodoo - i think i got custom boot sound working properly now (but i've been wrong before though..). If you want custom boot sound put your mp3 in /system/media/bootsound.mp3. 2.2.5 fixes a small bug in bootsound. Only upgrade if you care about boot sounds.
  • v2.3.0voodoo - added smartassV2 support. This needs to be tested more - i may pull this update if this governor proves unstable on the charge.
  • v2.3.1voodoo - copies su and superuser.apk if they don't exist for whatever reason. Only upgrade from 2.3.0 if you lost root somehow.
  • v2.3.2voodoo - i think i accidentally broke ext4 conversion in 2.3.1. fixed. sorry guys.
  • v2.3.3voodoo - disabled smartassv2 by default. ROM dev or user can enable it via init.d if desired.
  • v2.3.4voodoo - yikes i think 2.3.3 image was corrupt. Sorry about that guys!
  • v2.4.0voodoo - (upgrade only if you care about smartass), go into terminal and type su, enter, and type either "smartass enable" or "smartass disable" without quotes. This only works with ROMs with init.d support.
  • v2.5.0voodoo - added interactiveX, and CIFS module support, bug fixed in smartassV2. Check the FAQ section for how to enable/disable the modules. (fyi - CIFS module has not been tested yet).
  • 3.0.0 - kernel is now based on ep3h (should still work for ep1w but not fully tested). TUN is now natively supported by kernel. "voodoo" removed from version number - all releases will support voodoo lagfix, if you don't want it you can disable lagfix easily.
  • 3.0.1 - oops fixed a typo in bootanimation support for sanim.zip location.
  • 3.1.0 - slow boot time fixed, enabling governors using my scripts will now make it stick at boot, install_bb will install a good version of busybox, smartass tuned a bit for the Charge clock speeds.
  • 4.0.0 - based on EP4 stock kernel now.

DOWNLOADS
voodoo kernel (back up first!):http://cl.ly/BbFu

Working recovery that I use (flash via odin): http://cl.ly/9t7H
Stock ep1w kernel: http://cl.ly/9s7d
Stock ep3h kernel: http://www.box.net/s...idlfnslmt9xe9gv

FAQ
  1. How do I tell which version i'm on? - Look in /kernel_version
  2. Why no overclock/undervolt? - Can't do it until samsung releases kernel source.
  3. How do I tell if my filesystems converted to ext4 successfully? - there are several ways but the easiest to look at the output of the "mount" command. /system, /data, /dbdata and /cache should be ext4.
  4. Ext4 conversion issues or bootloop, please send me voodoo logs. Look in /sdcard/Voodoo/logs, find the newest directory and post or send me all the logs in there.
  5. Why do I get such high quadrant scores with your kernel? First of all, Quadrant scores do not reflect real world usage, in fact no benchmarking scores do. But the difference between RFS and properly mounted EXT4 filesystems is huge in write i/o throughput. See this post for more info: http://rootzwiki.com...ll=1#post108621
  6. what about quadrant scores discrepancy between EXT4 and voodoo EXT4? Keep in mind that quadrant benchmarks i/o in multiple different ways. voodoo tuned EXT4 is much more favorable in at least one of those tests. You can test this by converting file system to EXT3 and compare scores between that and untuned EXT4. Yes you will see much higher scores in EXT3. Why? EXT3 is faster than EXT4 (untuned) for some benchmarks. Voodoo's mount options make EXT4 behave a bit like EXT3 in performance for that particular test(s). In real world? probably not much difference.
  7. How do I enable/disable modules? Each module can be disabled/enabled by these individual commands (you can issue these commands in Terminal/adb as superuser, reboot after change):
    Code:
    <br />
    		  smartass enable<br />
    		  smartass disable<br />
    		  ix enable<br />
    		  ix disable<br />
    		  cifs enable<br />
    		  cifs disable<br />
  8. What do smartass and interactiveX mean? These are custom cpu governors, for more info: http://www.imoseyon....-governors.html
 

·
Average Android
Joined
·
334 Posts
Guys. Just wanted to update my earlier comment and initial impression of battery life. 11 hours in with 30% remaining. Moderate usage but it got to sit an hour or two without being used today too. Still, this is far better than its ever been.
 

·
Supporting Member
Joined
·
47 Posts
It should be noted in the OP that this will wipe your phone if you flash it over the latest GummyCharged GBE.
 

·
Supporting Member
Joined
·
455 Posts
Tohsh said:
It should be noted in the OP that this will wipe your phone if you flash it over the latest GummyCharged GBE.
Yeah, happened to me too, It doesn't seem to matter what version of CWM you are using either as it happened on jt's original CWM to me.
 

·
Premium Member
Joined
·
2,255 Posts
Discussion Starter · #9 ·
That is bizarre. We've tested this kernel on gummy gbe. How is the phone wiped? Data, system or both?
 

·
Tweaker
Joined
·
1,210 Posts
This is a known issue with GBE. Using an older version of CWM or the newest (red version?) has been reported to fix it. This is not a kernel issue, but a CWM issue.
 

·
Supporting Member
Joined
·
455 Posts
imoseyon said:
That is bizarre. We've tested this kernel on gummy gbe. How is the phone wiped? Data, system or both?
It wiped data and maybe cache, it also reverts /data and /cache back to RFS :-/
I don't know wher the problem lies, the kernel or CWM, but I had already flashed a mod using the same recovery and didn't have the issue CWM 4.0.0.8
 

·
Premium Member
Joined
·
2,255 Posts
Discussion Starter · #12 ·
hazard209 said:
This is a known issue with GBE. Using an older version of CWM or the newest (red version?) has been reported to fix it. This is not a kernel issue, but a CWM issue.
thanks for that - saves me time. :)
 

·
Droid Nation Podcast
Joined
·
243 Posts
I tried this kernal last night with GummyCharged GBE 1.9RC2.3. I reboot my phone after flashing the kernal and the Charge went black. So it tried to get it to recovery there was no recovery it wiped it. So i was going in to put it in download and use odin and fix it but it wipe out download load mode. It basically bricked my phone. Any suggestions why?
 

·
Android Addict
Joined
·
310 Posts
"clarkkkent434 said:
I tried this kernal last night with GummyCharged GBE 1.9RC2.3. I reboot my phone after flashing the kernal and the Charge went black. So it tried to get it to recovery there was no recovery it wiped it. So i was going in to put it in download and use odin and fix it but it wipe out download load mode. It basically bricked my phone. Any suggestions why?
If u go into DL mode, do u just get a black screen? Does Odin recognize your device plugged in? If so u can try to revert back using Odin and a stock ee4 tar. Make sure the reboot option is checked in Odin. If Odin doesn't see the phone, does the samsung flashing tool see it?
 

·
Premium Member
Joined
·
2,255 Posts
Discussion Starter · #17 ·
How did you flash the kernel? It doesn't touch the recovery partition at all. If the phone is truly bricked you need to borrow a Windows pc from a friend or something. Heimdal on Mac does not work with the charge.
 

·
Android Apprentice
Joined
·
22 Posts
Alright im on gummy GBE RC2.3... wiped cache and dalvik...chose zip... rebooted and all is well... Oh and remount works as well... Good job!
 

·
I just live here
Joined
·
475 Posts
clarkkkent434 said:
I tried this kernal last night with GummyCharged GBE 1.9RC2.3. I reboot my phone after flashing the kernal and the Charge went black. So it tried to get it to recovery there was no recovery it wiped it. So i was going in to put it in download and use odin and fix it but it wipe out download load mode. It basically bricked my phone. Any suggestions why?
imoseyon said:
How did you flash the kernel? It doesn't touch the recovery partition at all. If the phone is truly bricked you need to borrow a Windows pc from a friend or something. Heimdal on Mac does not work with the charge.
Unsure what you did when you flashed this, but there's gotta be some kind of catch for a kernel to wipe your recovery and bootloaders? Sounds like you did something else to me.
 
1 - 20 of 1239 Posts
Top