[KERNEL] Basic with a Twist SGS4G KJ6 1.1.3

---

Basic with a Twist SGS4G KJ6 Kernel

BML, don't flash if you have partitions converted to MTD.

Use at your own risk, I take no responsibility for anything that may happen to your phone because of this kernel.

This kernel is for those who don't want to be on the very cutting edge (CM7) but rather want stability without sacrificing too many recent features. It is based mostly on Bryan's 0.0.2d commit that supposedly never had problems with silent reboots. I made some changes to the config to bring it even more to the standard Samsung VibrantPlus in terms of hardware settings, but at the same time to optimize it for speed. I will add only tried and true features to this kernel, the ones that other kernel developers have used successfully.

Special thanks to bhundven (Bryan), FBis251, TeamAcid.

Features

• initramfs from TeamAcid, including CWM5, SuperSU, forced ext4, etc.
• Usual CIFS, TUN. I didn't include FUSE, if anybody needs it let me know.
• BLN. Use BLN Control app from market to activate.
• Voodoo Sound so paid app is not needed. Voodoo Sound app from market is required. Once installed, enable Smart Amplifier, it's the best thing you can do to improve music listening experience with our phone.
• jhash3 for faster hash calculations. Used widely across the kernel, especially in networking.
• OC/UV support with extended frequency table. Added 600Mhz, 900Mhz, 1.1Ghz, 1.2 Ghz, 1.3 Ghz, 1.4 Ghz. Use SetCPU or Xan's Voltage Control to enable and control frequency and voltages. Tegrak can be used only with no-OC/UV version.
• ondemandX and smartassV2 governors. One of these should probably be preferred over stock ondemand. Change with SetCPU or similar.
• TinyRCU. More lightweight version, it fits better our single CPU system.
• Swap support, although I don't recommend using it.
• SIO and BFQ I/O schedulers in addition to noop, deadline, and cfq that we already have.

Install
Flash with CWM or SGS Kernel Flasher. ODIN version is available only for OC/UV kernel.

Download
CWM:
v1.1.3
v1.1.3 (no OC/UV)
v1.1.2
v1.1.2 (no OC/UV)
ODIN:
v1.1.3
v1.1.2

Notes
* OC/UV version is very conservatively undervolted to -25mV. The preset voltages are still higher than on regular I9000, which has the same CPU. I'm running additional -50mV (total -75mV) for all frequencies without issues, but you may have them, every CPU is different!
* It is recommended to create a CWM recovery file before modifying voltages. This option is available in both SetCPU and VoltageControl.
* OC-ing to 1.4 Ghz is not recommended, especially for extended periods of time.
* Voodoo ext4 conversion, or "lagfix", is enabled and forced by default. There is not way and no need to go back to RFS.

Source
www.github.com/AntonX

Changelog

1.1.3
CWM 5.0.2.8 (blue) in initramfs
Disabled a little more of Samsung debugging

1.1.2
Minor changes to initramfs voodoo extension scripts
More neutral boot logo

1.1.0
Initramfs script will not force su update
Couple of small changes

1.1rc2
Few small changes

1.1rc1
Added BFQ and SIO I/O schedulers
Switched to TinyRCU
Added Swap support
Small change to Vibetonz

1.0b5
Some changes to OC/UV
Better BLN fix
Increased write timeout for bad SDHC cards
Added ondemandX and smartassV2 governors
Renamed the title, it's becoming less and less Basic...

1.0b4
Added native OC/UV support

1.0b3
Minor BLN changes
Replaced jhash.h with jhash3 code
Updated initramfs with SuperSU 0.88

1.0b2
Added BLN, first attempt

1.0b1
Original release

Let me be the first to push you....please consider BLN lol, that would be awesome!

Could you point me to the right repository/branch?

I'm curious to see your changes and I'm probably not looking in the right place on github.

Please add BLN

Originally Posted by bhundven

Could you point me to the right repository/branch?

I'm curious to see your changes and I'm probably not looking in the right place on github.

Well, I didn't upload anything yet. If you tell me how to control the frigging repository from Windows I'll do it right away

But seriously I want to make absolutely sure that this kernel doesn't have this nuisance of silent reboots. Because it they still present there is no need to have this kernel.

No matter what happens, if Vooodoo sound works without problems, I'll give you the code if you want it.

Originally Posted by AntonX

Well, I didn't upload anything yet. If you tell me how to control the frigging repository from Windows I'll do it right away

But seriously I want to make absolutely sure that this kernel doesn't have this nuisance of silent reboots. Because it they still present there is no need to have this kernel.

No matter what happens, if Vooodoo sound works without problems, I'll give you the code if you want it.

I'm about to post something to my cm7 thread, so heads up.

But stock kj6 kernel (if you download it from opensource.samsung.com and apply a few of my changes to fix tfsr and add initramfs) still has the same reboot issue.

I'm gonna start comparing some of the code from the froyo kernel to see wtf is going on. I fixed a problem with rild and random reboots are back.

I'm finding that the problem is related to suspend. The reboot happens when everything quiets down.

Originally Posted by AntonX

If you tell me how to control the frigging repository from Windows I'll do it right away

Haha, I don't even know. Don't use Windows?!?

put BLN in!!!! (i would do it myself, REALLY, i would but i don't know how)

Originally Posted by bhundven

But stock kj6 kernel (if you download it from opensource.samsung.com and apply a few of my changes to fix tfsr and add initramfs) still has the same reboot issue.

I'm operation on the assumption that 0.0.2d never had silent reboots. Nobody ever reported having them with this version. I have never ever experienced a reboot with it myself. That's why I took it as the base.
I haven't really looked what you did right after 0.0.2d. Seems like you switched to aries config instead from vibrantplus. Any particular reason? Anyway, I reverted it back and even slightly more back. Then you did some clean up and modified bunch of code. I don't care about cleaning somebody else's code like this. Unused functions and variables will be optimized out by the compiler anyway. To get rid of annoying warnings I just used -Wno-unused switch to gcc in the Makefile.
So - hard to tell what's happened between 0.0.2d and 0.1.0 (or 0.1.1?), but something must have happened. Too many people reported it to support this.

Great initiative Anton!
Flashing it on 2 devices. I will update in 3 days.

Sent from my SGH-T959V using XDA