1. This Kernel doesn't work with Android 4.4.x. It's CLEARLY stated in the title and the op.
2. This is for the I9100G. I think you have a the non-g-model?
And still you give so few information that I can't even try to direct to anywhere cause I don't know what you had on your phone before, neither do I know what you aim for.
But oh **** it's kinda important. Damn, really wish someone could read your mind ...
The true reason dual boot can't make it to KitKat and above for now? Selinux was permissive in JB and enforcing in KitKat and above, which is why it still boots in JB. Unless I change selinux to permissive for all (which is not desirable), it will not work in KitKat and above. Wondering why other newer devices have multi rom support? Blame Samsung, i9100g's kernel structure is very different from others.
I installed this kernel and after it prompted i should reboot. when i rebooted my phone stop at the booting image and cannot not go further, i tried again to boot into recovery but cannot, what should i do now. plz
Thank you for not putting ANYWHERE in the original post that this is for i9100G, i found this kernel via search and now i've bricked my device and i have to reflash everything from the begining
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
[U]v16:[/U]
- Support for PAC ROM
- Support for CM's newly implemented multi-sim framework
- Updated to Linux kernel 3.0.101 (EOL)
- ExFAT module now compiled from source
- Updated recovery to CWM 6.0.4.4
- For explicit changelogs, refer to my Github (commits are more detailed now)
[U]v15:[/U]
- Support for Android 4.3
- Updated to Linux kernel 3.0.98
- Reduced size of kernel modules (kernel zip package now a lot smaller
- Updated recoveries to CWM 6.0.4.0, TWRP to 2.6.3 and Philz to 5.15.0
- New modified CWM recovery! Features:
- Touch control!
- Battery status
- Prompt before commencing backup (avoids accidental backups)
- Advanced restore for /preload
- Rainbow mode! (to activate, scroll down the list for 5 times, scroll back up again to deactivate)
- For explicit changelogs, refer to my Github (commits are more detailed now)
[U]v12:[/U]
- Full rebase of kernel source! Now it is at [url]https://github.com/Ryuinferno/Blazing_Kernel_t1[/url]
- With the rebase of sources, hiccups are eliminated, try it and you will know why...;)
(there were some code errors when patching the old source)
- Updated to Linux kernel 3.0.88
- Data usage stats fixed
- Compiled with Linaro 4.7.4 toolchain optimised for Cortex-A9 (yes, toolchain compiled by me too)
- Updated recoveries to CWM 6.0.3.5, TWRP to 2.6 and Philz to 5.08.5
- Timer slack and dyanmic timer slack control
- CK3 tweaks
- Updated graphics driver (now also compiled with Linaro!)
- For explicit changelogs, refer to my Github (commits are more detailed now)
[U]v11:[/U]
- Updated to Linux kernel 3.0.75
- BLX
- Dynamic Fsync
- Dynamic Dirty Page Writeback
- Dyanmic mutex spin management
- CRC32 algorithm
- Updated voltage control
- Latest sync with CM for better compatibility
- Fixed MTP not working in stock for certain people
- Philz recovery now available!
- Compiled using Linaro 4.7.4 toolchain
[U]v10:[/U]
- Updated to Linux kernel 3.0.60 (this is a real update, applied patches [B]step by step[/B] instead of skiping those in between
(there's one kernel that skipped most of the patches and went to 3.0.75 straight away lol,
reverted the 3.0.76 and applied 3.0.77, and claims that it is on 3.0.77 now...lol...
and I tried to advice him, but always ignored...:silly:))
- Fixed random reboots in recovery
- Removed interactiveX governor (main cause of the reboots)
- zRAM support (for fun...lol)
- swap support (for fun...lol)
- exFAT module support (sdcards can be formatted in exFAT format now)
- Compiled using Linaro 4.7.3 toolchain
[U]v9:[/U]
- Initial dual base kernel commit
- Bring forward all features from v8
- Dual boot support
#!/system/bin/sh
# Ryuinferno @ XDA
chmod 666 /dev/frandom
chmod 666 /dev/erandom
mv /dev/random /dev/random.ori
mv /dev/urandom /dev/urandom.ori
ln /dev/frandom /dev/random
ln /dev/erandom /dev/urandom
That looks accurate, but it's a little hard to understand. A basic explanantion of zRAM is that zRAM compresses an actual block of RAM in order to have more RAM available to the system. If you make the compression too high with zRAM then your device will actually go slower as a result. An example of going over the top would be adding 256MB of RAM using zRAM on a phone that only has 768MB RAM (that's almost a 50% compression rate because ~600MB is available to the user). zRAM also requires the CPU to compress and decompress the data.
su
echo 0 > /proc/sys/vm/dynamic_dirty_writeback
su
echo 1 > /proc/sys/vm/dynamic_dirty_writeback
su
echo "3000" > /proc/sys/vm/dirty_writeback_active_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_suspend_centisecs
su
echo 0 > /dev/cpuctl/timer_slack.min_slack_ns
echo 50000 > /dev/cpuctl/timer_slack.min_slack_suspend_ns
su
echo 0 > /dev/cpuctl/apps/timer_slack.min_slack_ns
echo 100000 > /dev/cpuctl/apps/timer_slack.min_slack_suspend_ns
su
echo 100000000 > /dev/cpuctl/apps/bg_non_interactive/timer_slack.min_slack_ns
echo 250000000 > /dev/cpuctl/apps/bg_non_interactive/timer_slack.min_slack_suspend_ns