[vvaleta]

LICENSE for CF-Root v3.0+, ext4 tools v1.2+
As it seems a number of kernels are being based on CF-Root, and CF-Root is being included in custom ROMs, I'm going to set up a number of rules. The rules are meant to be fair to both you and me, and futher cooperation, not limit it. If you are an end-user, do not distribute kernels based on CF-Root, and do not distribute ROMs using it, you can skip this post, it is not for you. If you make kernels based on CF-Root, or your ROMs include CF-Root, read this post and follow the rules.

I don't mind you using the CF-Root hacked kernels, in fact I think it's great All parts of CF-Root are free to use/include in your own stuff, if these rules are followed.

If something doesn't work for you, feel free to PM/ask for a change. None of these rules are set in stone, maybe you have a good reason to want something different.

Usage of "CWM Manager", "Tweak Manager", and "ext4 tools" apps
- You may not modify these APKs in any way, if you include or redistribute them. Modifying icons to match your firmware/ROM theme is however allowed, but must be stated.
- You may not re-post these files anywhere else (separately from CF-Root), but you may of course link to the post (not the download directly!) in the CF-Root thread containing these files. In other words, either you include them or you don't, but you can't offer them as a separate download.
- You must use the appropriate versions, released at the same time as the kernel, or any newer version released by me. For example, if you are using CF-Root v3.0, if you use/include these apps, you must use CWM Manager 1.50+, Tweak Manager 1.20+ and ext4 Manager 1.20+.
- You must test that their functionality remains 100% intact regardless of your (kernel/ROM) modifications. If the functionality is not as expected with your (kernel/ROM) modifications but you still include the apps, you must clearly state what you know is broken.

If you are just using CF-Root in your custom ROM, but do not modify the CF-Root kernel in any way (except icons)
- You must include a notice that the ROM uses CF-Root, and the version of CF-Root used.
- You must also include a link to this thread ( http://forum.xda-developers.com/showthread.php?t=788108 )
- You should (not required) include a link to donate to me, Chainfire ( http://www.jongma.org/dx.php )
- You should (not required) inform me that you are using it either by posting in the CF-Root thread or sending me a PM. (Thanks!)
- As you are not modifying CF-Root in any way (except icons), you can skip the rest of this post

If you are using any part (that I have written) of CF-Root, basing a kernel on CF-Root or including it in your ROM and modifying it
- You must include a notice that the kernel/ROM is based on or uses CF-Root, and the version of CF-Root used.
- You must also include a link to this thread ( http://forum.xda-developers.com/showthread.php?t=788108 )
- You must include a link to donate to me, Chainfire ( http://www.jongma.org/dx.php )
- You must keep the Android properties correct (see below)
- You should (not required) inform me that you are using it either by posting in the CF-Root thread or sending me a PM. (Thanks!)

customkernel.* Android properties
These properties are used by various scripts and apps to detect/control features, and are generally (IMHO) a good thing to have and keep correct. In CF-Root these are set in /sbin/boot-patch.sh, or /sbin/boot/properties.sh, depending on CF-Root version.

These properties must be set by a script or binary that is inside initramfs. They may not be set by anything on a "normal" partition - like a script in /system or /data. This way replacing the kernel will clear the values.

customkernel.cf-root - Either "false", "true". May only be "true" if fully compatible with CWM Manager, Tweak Manager, and ext4 Manager / tools. The idea is to add your own as well. If you make "uberkern", for example, set "customkernel.uberkern" to "true" as well.

customkernel.base.cf-root - Either "false" or "true". Must be "true" if the kernel uses anything from CF-Root.

customkernel.name - Kernel name without version numbering. Somewhat an identifier. "CF-Root" in CF-Root.

customkernel.displayname - Kernel name including specifics, in case of CF-Root is it "CF-Root ...version-name...". Used to display "current kernel version" in various tools. Could be "UberHackers UberKernel v89 with Extra Monkeys" in your case

customkernel.version.number - This is an internal build number, incrementing. Newer versions always have a higher number than older versions. In CF-Root v3.0 this number is 50.

customkernel.version.name - The named version. In CF-Root v3.0 this would be "3.0".

customkernel.bootani.zip - Either "false" or "true". Whether the kernel supports "bootanimation.zip" in /data/local

customkernel.bootani.bin - Either "false" or "true". Whether the kernel supports "bootanimation.bin" in /data/local

customkernel.cwm - Either "false" or "true". Whether the kernel has ClockWorkMod included

customkernel.cwm.version - CWM's version. Must include at least the major version. Example values: "2", "2.0.1.0", "3", "3.0.0.5"

customkernel.fs.* Android properties
Filesystem support flags. RFS and VFAT are special case. RFS can only be used on "internal" partitions, VFAT is supported by all kernels. Therefore, RFS only has the "basic" flag, and VFAT is not listed at all. Values are always either "false" or "true". The * should be replaced by the filesystem name, in lowercase, with a maximum of eight characters. In CF-Root these are set in /sbin/boot-patch.sh.

customkernel.fs.* - Filesystem supported on ALL basic internal partitions: system, data, dbdata(datadata), cache.
customkernel.fs.*.sd.int - Filesystem supported on internal SD card, if such a thing exist on the device.
customkernel.fs.*.sd.ext - Filesystem supported on external (removable) SD card, if such a thing exists on the device.

CF-Root ext4 (in v3.0):

customkernel.fs.rfs true // RFS supported on basic internal partitions
customkernel.fs.ext4 true // ext4 supported on basic internal partitions
customkernel.fs.ext4.sd.int false // ext4 NOT supported on internal sd card
customkernel.fs.ext4.sd.ext false // ext4 NOT supported on external sd card

persist.tweak.* Android properties (only applies if you include Tweak Manager APK)
These properties are used by Tweak Manager and CF-Root startup scripts (/sbin/boot-patch.sh) to perform tweaks.

- You may not significantly modify behavior based on these tweak properties. You can further tweak a tweak, but the result should still fit the intent of the original tweak. For example, the noatime tweak should always apply noatime, and should not be changed to change default screen rotation or something.
- If including a new tweak which is controlled by a persist.tweak.* setting, the boot script must set a default value for this property.