RIN Kernel for D850
Close to stock with some sugar added ... delicous!
Hey guys and girls,
you may have seen my unified stock kernel thread already (or may not, but doesn't matter). This kernel is my attempt to build up on the fixed source and add some additional features for us mod lovers to thinker with and to personalize your device to your usage. For now, I'll keep it close to my stock source and just pull some additional features and fixes in, but not to much. That may change in the future (maybe even soon), but for now, I'll stick to that paradigm.
First of, DISCLAIMER, I'm not responsible for bricked devices, dead unicorns, rainbows with missing colors, world war, nose bleed, void warranty (you know that already, don't you? your warranty is void now and it's your fault ) or any other harm happening to your device, you or people around you!
What does it serve? (Features)
Built with sabermod 4.9 toolchain
IO Schedulers
BFQ
CFQ
DEADLINE
FIFO
FIOPS
NOOP
ROW (default)
SIO
TRIPNDROID
VR
ZEN
Governors
Adaptive
Conservative
DanceDance
IntelliActive
IntelliDemand
Interactive (default)
Lagfree
Lionheart
OnDemand
Performance
Powersave
SmartassV2
Userspace
Wheatley
Smartmax
TCP Congestion Algorithms
BIC
Westwood
Vegas
Veno
Yeah
HTCP
Cubic (default)
Reno
init.d support
intelliplug
intelli thermal v2
Memutil optimizations
Voltage control
SoundControl
OC to 2.7GHz and UC support
Cpu limiter
2-Way Call Recording support
Simple GPU Algorithm
Simple_ondemand GPU Governor fixed
exFat support
ntfs support (bugged)
Oversharpening fix
DriveDroid support
android logger sysfs toggle (disabled by default)
high priority workqueue
Many under the hood fixes
Stability
More to come
How to apply it? (Installation)
IMPORTANT: Read through all the requirements, steps and warnings before you do anything, if any requirement doesn't match or you don't know what one or more of the steps below mean or do, ask before you do any of them, if you don't know how all the steps can be done, let it be, I warned you, if you don't do and something bad happens, I'll just laugh at you!!
Requirements? Yes!
D850
Custom Recovery
Stock or Stock Based ROM (no AOSP)
How to flash the kernel?
Download zip
Place on internal or external SD
Reboot to recovery
Choose install zip
Search for the downloaded zip
Confirm flashing
Wipe cache
Reboot
Have fun
How to boot unbumped kernels?
Only needed for the img files prior version 1.7
Plugin your device to the PC
Open a terminal and execute
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/stock-laf.img # backup the stock download mode to your external sd
exit # exit the superuser shell
exit # exit the adb shell
adb pull /storage/external_SD/stock-laf.img . # backup the download mode image from you external sd to the PC
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf # remove the stock download mode
BEWARE, THIS WILL REMOVE YOUR DOWNLOAD MODE!!! YOU WON'T BE ABLE TO FLASH KDZ FILES BEFORE YOU RESTORED IT!!!!
Turn off the device completely, plug in the USB-cable, if you pulled it out and start the device by holding vol up + power till you see some white text on the screen, fastboot should be written somewhere on the screen, afterwards execute the following command on the PC (while in the directory you've downloaded the kernel image to).
D850:
Code:
fastboot boot D850-rin-1.6.img # boot the kernel
BEWARE, NEVER USE FLASH AT FASTBOOT ONLY BOOT, IT WILL TRIGGER SECURITY OF THE LOCKED BOOTLOADER AND YOU WON'T BE ABLE TO BOOT ANYMORE!!!!
You're done now and booted to the custom kernel!
How to make sure you're running the kernel?
To check if you properly booted into the kernel execute this in the command line (terminal emulater or through adb shell):
Code:
cat /proc/version
it should show
Code:
Linux version 3.4.0-rin-g58903a9-dirty ([email protected]) (gcc version 4.9.1 20140710 (prerelease) (crosstool-NG linaro-1.13.1+bzr2673 - Linaro GCC 2014.07 - Cortex-A15) ) #53 SMP PREEMPT Thu Aug 14 13:26:42 CEST 2014
Once more a warning READ IT!!:
BEWARE, when you reboot you'll boot to the stock kernel, you'll have to boot the custom kernel over fastboot every time, when you boot normally, you'll be on the stock kernel, this won't lead to issues, but you'll miss the benefits of this kernel, I know that's not optimal, but the best we can get with the locked bootloader.
How to restore Download mode?
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/storage/external_SD/stock-laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf # restore the stock download mode from the backup on your external sd
Changes? (Changelog)
26.11.2014/1.8.5
Less frequency steps to UC (better performance for governors hitting each step)
Oversharpening fix (Credits to @Skin1980)
Kernel now flashed with dd within recovery
Added external radio-iris-transport module to fix fm radio
20.11.2014/1.8
build with sabermod 4.9
Graphite build flags
NTFS support
sysfs interface for android logger (Logger disabled by default)
TCP cong algorithms (BIC, Westwood, HTCP, Vegas, Veno, Yeah)
More frequency steps between 300Mhz and 2.7Ghz
17.11.2014/1.7.2
Raise max microvolt at cpu for pm8941 and pma8084 (Possible Green Screen Fix)
Additional warnings fixed
12.11.2014/1.7
images bumped
flashable zip
init.d support (busybox needed)
AIO optmimizations enabled
intelli plug added (credits to @faux123)
****load of warnings fixed
23.10.2014/1.6
D850 support added
Simple GPU Algorithm Support
Overclocking up to 2.76 Ghz
exfat support
intelli-thermal v2 added
smartmax governor added
memutil optimizations
build with NEON kernel mode
2-way call recording patch
DriveDroid cdrom emulation support
Faux SoundControl
Simple-OnDemand fixed
Cpu Freq Limiter
some small fixes and enhancements
14.08.2014/1.0.1
net/ipv4|include/asm-generic: Enhancement of out of bounds fix
14.08.2014
Initial release
Full list of commits can be found here
Where to get it from? (Downloads)
AndroidFileHost | xda | dev host | google drive | trialsrider1
Let me test!! (Beta Testing Community)
Google+ LG G3 Beta Testing Community
Show me the so(u)rce(ry)! (Source Code)
https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-kitkat
Donators (huge thanks, you're simply great )
@Toneman07
@Helloworld294
@shaarky
@Dreamxtreme
@guyd
@mosincredible
@tobitege
@AndroidUzer
Credits
XDA
Google
LG
@HolyAngel
@faux123
@KAsp3rd
@myfluxi
@trialsrider1
@Skin1980
@Lord Boeffla
@GuneetAtwal
@DooMLoRD
If you like my work, please show your appreciation by pressing the thanks button, if you want to do more, i've nothing against a little donation, but I'm as happy when you just thank me by pressing the button
XDA:DevDB Information
Rin Kernel, Kernel for the AT&T LG G3
Contributors
Tectas
Source Code: https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-kitkat
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.8.5
Stable Release Date: 2014-11-26
Created 2014-10-24
Last Updated 2015-01-09
Any questions? (FAQ)
How can I toggle the android logger?
File Explorer Method:
Go with a root explorer to /sys/kernel/logger_mode and open the logger_mode file.
Remove everything inside that file and put the number 1 to enable and 0 to disable the logger into it and save the file.
Terminal Method:
Enable the logger
Code:
echo 1 > /sys/kernel/logger_mode/logger_mode
Disable the logger
Code:
echo 0 > /sys/kernel/logger_mode/logger_mode
My internal sd is not working, what to do?
Open adb shell or a terminal emulator and type
Code:
su
restorecon -v -R /data/media
Cool. I am not into kernels UT that KS for extending support to the D850.
Wow nice congrats
Will this be easier to use once the Bump! Support is added?!
I will try it out now, but it will be able to be permanent once it is able to be Bump!'ed right?
Sent from my LG-D850 using XDA Free mobile app
sublimejosh2000 said:
Will this be easier to use once the Bump! Support is added?!
I will try it out now, but it will be able to be permanent once it is able to be Bump!'ed right?
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, as soon as the bump method is released I can build a flashable and you can flash it through recovery like usual and don't have to worry about booting it through fastboot.
Sent from my LG-D855
Thanks for brining your kernel to us. This is a great day for AT&T!!!
Would flash image gui tool be able to flash this for us? I used it before on other devices
Sent from my LG-D850
traesnaidensdad said:
Would flash image gui tool be able to flash this for us? I used it before on other devices
Sent from my LG-D850
Click to expand...
Click to collapse
Not till the bump tool is released.
Sent from my LG-D855
When I flash this one, I end up going to a green screen saying HW Reset. I got options to go into Download Mode or reboot. If I reboot, the Kernel doesn't get booted.
17akota said:
When I flash this one, I end up going to a green screen saying HW Reset. I got options to go into Download Mode or reboot. If I reboot, the Kernel doesn't get booted.
Click to expand...
Click to collapse
Interesting, just out of interest, to which version did you update through ota?
Could you try to remove the laf partition to get to fastboot mode and boot to it?
(just replace recovery with laf at the steps to remove the recovery, to boot to it, shut the device down completely, plug in the USB and boot the device through holding vol up + power)
Sent from my LG-D855
The D850 never got any official OTAs that I'm aware of, but I'm on AndroidNow 1.6.
That's what I did initially, but this time I flashed it by removing Recovery. I'll try the LAF fastboot though.
Great work on this.....
Personally I am going to wait for a bumped version - just to make sure I don't screw something up when trying to flash this.....
On that note, have you tried to reach out to the bump team? Perhaps if you explain that you have a kernel waiting to be bumped, they might manually bump the image for you. I know they are trying to work out a method to automate this process, but they have the ability to manually bump stuff right now!
can we get a flashable zip of this please
bkeaver said:
can we get a flashable zip of this please
Click to expand...
Click to collapse
We cannot get a flashable zip until team codefire gets the bump site up and can bump the kernel! The same thing that is holding up a slew of custom romz. This almost reminds me of a Geico commercial and a caveman being under a rock lol.
Deadly venom rom will posted soon. If you want to check it out when the link is up.
Sent from my LG-D850 using XDA Free mobile app
Would love to use this kernel
Sent from my LG-D850 using Tapatalk
So I can flash this with flashify?
Until some sort of twrp zip is made?
I don't really understand the whole is it bump'd or not thing :-/
Granted I did it. I have twrp
Could you give steps if you successfully flashed it plz?
Sent from my LG-D850 using XDA Free mobile app
jaladhjin said:
So I can flash this with flashify?
Until some sort of twrp zip is made?
I don't really understand the whole is it bump'd or not thing :-/
Granted I did it. I have twrp
Click to expand...
Click to collapse
No, sorry, not yet, the problem is, there is a tool needed (not completely true though, it could be signed without the tool as well, but it'd need the fitting certificate, which has only team codefire) to sign not stock kernel images and make them flash and bootable, this tool is the bump tool, which is not released yet.
Sent from my LG-D855
Related
Update 2013-04-01 (3.1.10-10.4.4.25-that6):
With a small fix for a crash when reading a file in /sys, the revolutionary pre-init system from v5, and a more complete Data2SD package:
http://forum.xda-developers.com/showpost.php?p=39822992&postcount=239
Update 2013-03-24 (3.1.10-10.4.4.25-that5):
The latest experimental kernel is here: http://forum.xda-developers.com/showpost.php?p=39528295&postcount=227
Update 2013-03-05 (3.1.10that4):
The latest kernel is up: http://forum.xda-developers.com/showpost.php?p=38797590&postcount=194
New features: User voltage control and Data2SD auto-detection.
End Update 2013-03-05
Update 2013-02-06 (3.1.10that2):
After positive feedback from testers and due to popular demand, here is my latest kernel with the experimental new "ROW" I/O scheduler. If you want to know more, read the documentation in the patch here: https://patchwork.kernel.org/patch/1862241/ . Please note that this is a rather new development and not yet merged into a mainstream kernel, so it has not been widely tested. However, all results from XDA members were neutral or positive so far.
End update 2013-02-06
Since Asus seemed to have forgotten to release the 10.4.4.25 kernel sources, I reminded them politely - and finally the sources are available for download from their support site!
This is the first kernel ever that I cross-compiled myself - be gentle.
zImage (kernel binary) features:
- Asus 10.4.4.25 base
- fsync control
- ISO 9660 + UDF support (CD/DVD filesystems)
- CIFS (for mounting Windows shares)
New in 3.1.10that2 (2013-02-06):
- ROW I/O scheduler (prioritize READ requests over WRITE requests on eMMC/SD cards) included as default
New in 3.1.10that4 (2013-03-05):
- User voltage control for undervolting
New in 3.1.10-10.4.4.25-that5 (2013-03-24):
- Penguins! (framebuffer console)
New in 3.1.10-10.4.4.25-that6 (2013-04-01):
- No more crash when reading /sys/bus/nvhost/drivers/tegradc/tegradc.0/nvdps
Ramdisk features:
- insecure adbd
- init.d support
- does not set lcd_density (dpi unlocked)
in the -data2sd versions only:
- mount points modified for the Data2SD mod (see http://forum.xda-developers.com/showthread.php?t=1962507)
New in 3.1.10that4 (2013-03-05):
- auto-detection of data2sd - if the microSD card is inserted at boot time and it contains a second partition, it is assumed to be a data2sd partition and mounted as /data. Otherwise, the system is booted with /data mounted to internal storage as usual.
New in 3.1.10-10.4.4.25-that5 (2013-03-24):
- moved auto-detection of data2sd to scripts in /system for easier customization (read the release post for details)
Credits:
- Linux kernel devs and Asus for the base
- Gentoo devs for their easy "crossdev" toolchain-generation tool
- scrosler for the original CleanROM, from where I got the ramdisk mods
- Ezekeel for the fsynccontrol patch (http://rootzwiki.com/topic/14685-kernel27-jul-glados-v20-for-jb/page__st__700#entry607555)
- clemsyn, for finding the fsynccontrol patch and integrating it into his kernel
- faux123 for the user voltage control patch which clemsyn integrated into his kernel
- sbdags and buhohitr for testing
- dasunsrule32 for finding the ROW I/O scheduler and testing it with the CM kernel
- snypa for notifying me of dasunsrule32's research
- blackmambazzz for making the ROW scheduler compile with 3.1
Flashable ZIP:
This kernel (and all others in this thread) is compatible with stock-based (Asus Android 4.1.1) ROMs that set lcd_density (dpi) in build.prop - in other words, this is the preferred kernel for CleanROM Inheritance.
2013-04-01: v6: Latest version:
Get it here: http://forum.xda-developers.com/showpost.php?p=39822992&postcount=239
2013-03-24: v5:
Get it here: http://forum.xda-developers.com/showpost.php?p=38797590&postcount=227
2013-03-05: v4:
Get it here: http://forum.xda-developers.com/showpost.php?p=38797590&postcount=194
2013-02-06: (3.1.10that2):
View attachment that-kernel-10.4.4.25-2.zip
View attachment that-kernel-10.4.4.25-2-data2sd.zip (for Data2SD users only)
2013-01-30: Original version (3.1.10that1) without ROW:
View attachment that-kernel-10.4.4.25-1.zip
A version for data2sd users is here -> http://forum.xda-developers.com/showpost.php?p=37392834&postcount=5
Sources:
zImage compiled from stock Asus 10.4.4.25 base with following config and patches:
View attachment config.txt
View attachment ril-include-fix.patch
View attachment fsynccontrol.patch
New in 3.1.10that2 (2013-02-06):
View attachment v4-1-2-block-Adding-ROW-scheduling-algorithm-for-3.1.patch
Boot image repackaged as described here: http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4
(You might now ask "where is the overclocked version"? I decided to start with a known stable base for my first release - if this one turns out to work fine, the oc build comes next.) - for overclocked version, read next post!
Overclocked!
This is 3.1.10that1-oc - the version with clemsyn's overclocking patches. Please note that I only extracted and then applied his patches to the current kernel and typed "make" - I don't understand all the scary frequency and voltage tables, and I don't know how it works in detail. However I got up to 7130 points in this benchmark thingy, and system tuner shows 1.8 GHz, so it appears to do something.
Please note that this is only the kernel, and it does not contain clemsyn's changes for the Asus performance modes. As you may know, the 3 Asus performance modes are activated by running shell scripts in /system/etc named cpu1.sh to cpu3.sh. Clemsyn's kernels replace balanced mode with performance mode, and performance mode with the new overclocked mode. This kernel does not do that, it leaves your modes as they were!
Depending which kernel you were using before, the following will happen:
- Coming from a stock kernel, you keep balanced and performance modes, and the extra overclocking mode can only be activated by executing /system/etc/cpu4.sh. If you want, you can rename cpu2.sh to cpu2_original.sh, cpu3.sh to cpu2.sh and cpu4.sh to cpu3.sh, then you have performance mode as default instead of balanced, and overclocking mode if you activate "performance mode" - same as clemsyn's. If this is too complicated for you, you can either flash clemsyn's kernel directly before this one, or wait until someone repackages this kernel.
- Coming from clemsyn's kernel, performance modes should work as before. Please don't ask me which specific variant of clemsyn's kernels this one is comparable with - he released only one source package, which I used, but many different kernel binaries. I can't recreate other versions without clemsyn releasing sources for those specific versions.
zImage (kernel binary) features:
- all of the above
- Overclocking and voltage control
Ramdisk features:
- same as non-overclocked version
Additional credits:
- clemsyn, for his amazing overclocking kernel
Flashable ZIP:
3.1.10that2-oc with ROW scheduler (2013-02-06):
Internal storage: View attachment 1703857
For Data2SD: View attachment 1704016
3.1.10that1-oc (2013-01-31):
Internal storage: View attachment that-kernel-10.4.4.25-1-oc.zip
For Data2SD: View attachment that-kernel-10.4.4.25-1-oc-data2sd.zip
Sources:
same as non-overclocked version plus this patch extracted from clemsyn's "tfcombofinal" source:
View attachment clemsyn-tfcombofinal-oc.patch
Config: View attachment config.txt
Have fun, and don't fry your tablets!
Excellent work my friend! Will test it out later. :cyclops:
Excellent work my friend...dream comes true. BTW, currently I'm on data2sd, is it possible to make one for data2sd? Thanks.
buhohitr said:
Excellent work my friend...dream comes true. BTW, currently I'm on data2sd, is it possible to make one for data2sd? Thanks.
Click to expand...
Click to collapse
Good idea.
View attachment that-kernel-10.4.4.25-1-data2sd.zip
(Note: This is 100% untested - if you tell me that it works, I'll add it to the OP. ) Now tested by buhohitr, thanks. :good:
Same zImage with the ramdisk from the previous data2sd kernel.
Note: this is not a data2sd installer, it's only a new kernel to drop into an existing data2sd installation.
Working well so far! :good:
_that said:
Good idea.
View attachment 1690048
Note: This is 100% untested - if you tell me that it works, I'll add it to the OP. Same zImage with the ramdisk from the previous data2sd kernel.
Click to expand...
Click to collapse
Great news! Your new data2sd kernel is working very well. All data mountings are correct and fsync is woring wonder! Great job!
1. When PC hook up to device, on PC I see:
a. Internal - ext4 parition on microsdcard
b. Micro - Fat32 partition on microsdcard
c.-SD - Dock SDcard.
2. Disabled fysnc - working wonder, gain 600+ on Quadrant.
I have been using Sandisk Extreme Pro class 10 (95mb/s) and it's very stable (Did not work before with Clemsyn Kernel). With fsync disabled, a gain of 600 point bring Quadrant to 6639 from 5995/6005 without OC. The tablet is super smooth and fast with fsync disabled. I can see the apps are launching faster from stand still, if they already in memory, BAM it's there. Browser also faster, Gallery loaded much faster and I got over 2 thousand pictures. In summary, I'm impress and very happy....just couldn't wait for the OverClock version.. Again, great job _that!! :good::good:
Edit: I will be running this for a week to see if any issue with journaling and fsync disabled on this super fast sdcard. Will report back.
Update 1/30 @ 10:30pm est - After 4 1/2 hrs, this tablet stills running smooth and quick. Very happy with this kind of performance, probably the best to date. What I'm really exciting about is, there still more room for performance....when "_that Overclock kernel" arrived..
tried this on PA, and I get a message, upgrading apps, but then it hangs. Is this to work on all ROMS, or just stock?
gvsukids said:
tried this on PA, and I get a message, upgrading apps, but then it hangs. Is this to work on all ROMS, or just stock?
Click to expand...
Click to collapse
Should be just for stock Cleanrom.
Tried this fantastic kernel in the last 5 hours and it is smooth, had no problem at all. Epic Citadel reports a benchmark of 38.9 fps.
Can't wait to try the OC version of it. Also waiting for the SanDisk Extreme to arrive from Amazon to try out the data2sd too.
Re: [KERNEL] 3.1.10that1 ★ 10.4.4.25 + fsync + ISO9660 + CIFS
I can confirm that data2sd version is working great. Waiting for the OC version. Good job!
So how does one disable fsync?
Flash this kernel, reflash ROM with no kernel option and fsync disable checked, or?
Just flashed this kernel. I have disabled fsync and my tablet has sped up. Thanks for this kernel _that.
---------- Post added at 04:28 PM ---------- Previous post was at 03:34 PM ----------
inSaN1Ty_X said:
So how does one disable fsync?
Flash this kernel, reflash ROM with no kernel option and fsync disable checked, or?
Click to expand...
Click to collapse
1. Reflash CleanRom 3.2.1
2. Disable Fsync during the installer
3. Reboot
4. Wipe Devlink Cache/Cache
5. Flash this kernel
This should disable fsync with this kernel.
Απ: [KERNEL] 3.1.10that1 ★ 10.4.4.25 + fsync + ISO9660 + CIFS
Hello i just want to say thanks, i am using the data2sd version without any problem.
If someone is interested in the kernel changes between 10.4.4.23 and 10.4.4.25 can follow this link to my github.
Looks like Asus has made some changes in the mmc management:
Code:
/*
* SD Workaround: downgrade frequency for seldom specific sdcard
*/
https://github.com/blackmamba97/asus-kernel-tf700t/compare/10.4.4.23...10.4.4.25
@_that I hope its ok that I have used your config because I dont have Cleanrom installed atm and so I cant pull the config.gz
blackmambazzz said:
@_that I hope its ok that I have used your config because I dont have Cleanrom installed atm and so I cant pull the config.gz
Click to expand...
Click to collapse
Sure, that's the point of me publishing all the sources as detailed as I can - take whatever you can use.
By the way, there is a nice script in the kernel sources that extracts a config from a zImage, it's in scripts/extract-ikconfig and you pass a zImage to it as a parameter. Maybe that's useful for you one day.
buhohitr said:
What I'm really exciting about is, there still more room for performance....when "_that Overclock kernel" arrived..
Click to expand...
Click to collapse
myeepad said:
Can't wait to try the OC version of it.
Click to expand...
Click to collapse
ariadnejro said:
Waiting for the OC version.
Click to expand...
Click to collapse
Made for you...
http://forum.xda-developers.com/showpost.php?p=37390637&postcount=2
_that said:
This is 3.1.10that1-oc - the version with clemsyn's overclocking patches. Please note that I only extracted and then applied his patches to the current kernel and typed "make" - I don't understand all the scary frequency and voltage tables, and I don't know how it works in detail. However I got up to 5780 points in this benchmark thingy, and system tuner shows 1.8 GHz, so it appears to do something.
Please note that this is only the kernel, and it does not contain clemsyn's changes for the Asus performance modes. As you may know, the 3 Asus performance modes are activated by running shell scripts in /system/etc named cpu1.sh to cpu3.sh. Clemsyn's kernels replace balanced mode with performance mode, and performance mode with the new overclocked mode. This kernel does not do that, it leaves your modes as they were!
Depending which kernel you were using before, the following will happen:
- Coming from a stock kernel, you keep balanced and performance modes, and the extra overclocking mode can only be activated by executing /system/etc/cpu4.sh. If you want, you can rename cpu2.sh to cpu2_original.sh, cpu3.sh to cpu2.sh and cpu4.sh to cpu3.sh, then you have performance mode as default instead of balanced, and overclocking mode if you activate "performance mode" - same as clemsyn's. If this is too complicated for you, you can either flash clemsyn's kernel directly before this one, or wait until someone repackages this kernel.
- Coming from clemsyn's kernel, performance modes should work as before. Please don't ask me which specific variant of clemsyn's kernels this one is comparable with - he released only one source package, which I used, but many different kernel binaries. I can't recreate other versions without clemsyn releasing sources for those specific versions.
zImage (kernel binary) features:
- all of the above
- Overclocking and voltage control
Ramdisk features:
- same as non-overclocked version
Additional credits:
- clemsyn, for his amazing overclocking kernel
Flashable ZIP:
Internal storage: View attachment 1693162
For Data2SD: View attachment 1693164
Sources:
same as non-overclocked version plus this patch extracted from clemsyn's "tfcombofinal" source:
View attachment 1693163
Config: View attachment 1693166
Have fun, and don't fry your tablets!
Click to expand...
Click to collapse
Excellent. Note I mod Clemsyn's cpu.sh files so that balanced mode is balanced mode which theorectically means I can now make a 1.3 1.8 and a 1.5 1.8 version of this
Off to do some testing.
Looks like Kernel Installer 1.8 is in the making.
I can confirm that oc data2sd version is working great.
Thanks great job :good:
sbdags said:
Excellent. Note I mod Clemsyn's cpu.sh files so that balanced mode is balanced mode which theorectically means I can now make a 1.3 1.8 and a 1.5 1.8 version of this
Off to do some testing.
Looks like Kernel Installer 1.8 is in the making.
Click to expand...
Click to collapse
Nothing like quoting yourself. Yes it works. Now running a 1.3 1.8 GHz version of this kernel
Many thanks _that. Time to thank you with a donation. :good:
NEXT 2.1.8 placeholder: http://forum.xda-developers.com/showpost.php?p=51678873&postcount=472
STOP! This kernel supports ONLY Samsung Jelly Bean 4.1.x, 4.2.2, CM 10.1.x, 10.2, and 11.0 ROMs. It won't work on ICS, CM 9, CM 10.
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY TAB 2 PROJECT!
IMPORTANT NOTES:
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Sources:
Kernel sources at http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk
Features:
Samsung stock 4.1.x, 4.2.2 (since 1.8.3), CM 10.1.x and CM 10.2 (since 1.8.3) support with a single kernel image
For stock ROM: external SD card - internal media swapper script included
Samsung proprietary exFAT modules are loaded. CM 10.1 exFAT support files attached at post #2
For CM/CM based ROM, P31xx only: auto rotate screen default orientation depend on ro.sf.hwrotation value, camera orientation fix included
Dual-booting. You can have Samsung JB and CM 10.1 ROMs on a single device at the same time.
Nice looking AROMA based boot menu
Using CyanogenMod kernel source, updated to p3110 source for newer WLAN (Youtube HD bugfix on stock ROM), modem, sensors driver, and etc for both P31xx and P51xx target
CPU clock: 300MHz, 600MHz, 800MHz, 1.008GHz, 1.2GHz, 1.35GHz, 1.42GHz, 1.48GHz, and 1.52GHz, locked @ 1.008GHz on boot
GPU clock: 153.6MHz, 307.2MHz, 384MHz, and 512MHz, 307.2MHz as the default maximum clock
CPU voltage control. You can use Android Tuner/System Tuner/Trickster MOD to set CPU voltage
The ramdisk base on JB 4.1.2 (stock ROM) and JB 4.2.2 (CM 10.1)
Using newer PowerVR SGX 540 kernel modules and binaries blob
row, bfq, sio, and vr scheduler support
Governor bug fix. Replace Samsung's interactive governor with default OMAP4 3.0.31 interactive governor from omapzoom.org, plus pegasusq and lulzactive
NFS and CIFS/samba (not loaded by default) filesystem support
LZMA compressed initrd, to keep boot image smaller than 8MB
swap support. zram and cleancache with a working zcache driver, enabled by default
kernel config, insmod configs.ko and then you can access /proc/config.gz
external modem support, for PPP Widget (not loaded by default, P31xx need powered USB hub for external modem)
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Remove a lot of debug message from touchscreen driver, display, mmc, modem, etc
linaro arm-linux-gnueabihf- cross compiler, compiler optimization applied
SuperSU v1.41 for stock ROM
Self compiled BusyBox v1.22.0-git in /sbin, config file based on CM's BusyBox bbconfig output. fstrim applet patch applied, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. For stock ROM: this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Post boot script support (/system/etc/init.post_boot.sh)
For stock ROM: custom boot animation support (/data/local/bootanimation.zip or /system/media/bootanimation.zip if exists, Samsung boot animation as a fallback). If a bootanimation.zip found, the boot sound will be turned off as well as the shutdown animation.
Modified mount options
adb insecure, adb mode in charge state also insecure
Advanced TCP congestion support, westwood as the default congestion
No /system/etc/hosts patch, you can install AdAway from F-Droid
Known Problems:
Thanks To:
gokhanmoral, amarullz, Phil3759, Chainfire, cmenard, codeworkx, imoseyon, coolbho3k, Faux123, AuxLV
brolee93 for latest P51xx Samsung stock boot image
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
Downloads:
PhilZ Touch blackhawk version attached, PhilZ Touch 5.08.5 attached at post #3
NEXT kernel beta release attached
NEXT tool: http://forum.xda-developers.com/showthread.php?t=2285366
exFAT support files for CM/CM based ROM: http://forum.xda-developers.com/showthread.php?t=2285366 post #2
Todo:
More features in NEXT tool
Special Thanks:
@behemot24, @shakatu, @ironmaskusa, @tetakpatak
XDA:DevDB Information
[KERNEL][SINGLE/DUAL][JB/KK][STOCK/CM]blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 2
Contributors
ketut.kumajaya, Android-Andi
Kernel Special Features: Dual boot stock and AOSP based ROM
Version Information
Status: Stable
Current Stable Version: 2.4
Created 2014-09-21
Last Updated 2014-10-29
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Changelog:
21/04/2014 2.2:
Flash-Friendly File System (f2fs) support
Full github commits 8/4 - 20/4/2014: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-11.0
Update proprietary blobs, proprietary-vendor-samsung-update.zip
28/10/2013 2.1.4 -> 2.1.5:
Updated to upstream 3.0.101 kernel
Audit and SELinux enabled
Smartreflex completely disabled
GPU frequencies not exposed to STweaks bug fixed
Do not load exFAT modules on CM 10.2
Full changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
27/10/2013 2.1.3 -> 2.1.4:
Ramdisk updated to sync with latest CM 10.2
21/10/2013 1.8.3 -> 2.1.3:
Update init script for PAC
Disable almost all kernel debugging support except KALLSYMS. Kernel failed to boot with CONFIG_KALLSYMS disabled
Turn all CPUs online when governor gets changed, hotplug bug workaround
SIO and VR I/O scheduler
Initial STweaks support, big thanks @gokhanmoral. Download STweaks app from Play store to access almost all NEXT related settings (CPU governor, frequency, and voltages; GPU governor and frequency limit; surfaceflinger rotation; I/O scheduler; logger; CIFS, Xbox controller, and USB modem support; and dual boot related settings).
Update overclock codes, remove gpu_oc interface: https://github.com/kumajaya/android...mmit/94ac45a10213de400c7bf3c01b5c5b052ae8ba18
sgxfreq: add sysfs interface to store frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
sgxfreq: limit frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
The latest Android Tuner app needed to control the modified OMAP GPU control interface but the dirty way by editing /etc/init.post_boot.sh always available
Separated vendor blobs for JB 4.1.x and JB >= 4.2, @poppolo2001 fix applied
With CPU and GPU overclock, CPU under/over voltage, upstream kernel 3.0.96 by @CodyF86
Complete changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
10/08/2013 1.6.3 -> 1.8.3:
Initial upcoming Samsung 4.2.2 support
Initial CM 10.2 support. Do not flash blackhawk-next-cm-exfat-vold.zip! CM 10.2 already has an open source/reverse engineered exFAT filesystem support
Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directly after flashing NEXT 1.8.3!
Updated to upstream Linux kernel 3.0.41 (incremental patch)
The first kernel utilizing the new ducati firmware, the first kernel preserved 804MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk.zip if you switch to another kernel
zram switched to zsmalloc, zram optimized for Android disabled
XBox 360 USB controller with BigX LED support enabled (by @iks8 request). Modules not loaded by default, edit /system/etc/init.d/02modules to activate it.
23/07/2013 1.6.2 -> 1.6.3:
Add android_reboot applet to NEXT's busybox (a quick port from Android toolbox) to fix AROMA boot menu fail to boot into recovery/bootloader as reported by @kinung
I hate bug!
22/07/2013 1.5 -> 1.6.2:
Hotplug CPU governor working properly with cleancache enabled, zcahe memory corruption problem fixed!
Static linked busybox compiled from source, fstrim patch applied. Busybox config based on CM's busybox bbconfig output. Total 46 new busybox applet, add priority option to swapon applet
zRAM swap per CPU core, same priority value. CM's /system/bin/compcache script updated to handle 2 zRAM devices. Reference: http://wiki.gentoo.org/wiki/Zram
Stock ROM default zRAM size 26% RAM size. Following CM's standard, user can set zRAM value for example to 30% by typing "setprop persist.service.zram 30" over Terminal Emulator or over "adb shell setprop persist.service.zram 30". CM user can use Settings application: Performance - Memory management - zRam.
Swappiness value changed to 90
LZO compression updated to current upstream version, optimized for arm. Reference: http://git.kernel.org/cgit/linux/ke.../?id=b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50
zRAM support optimized for Android, utilizing the new lzo library.
cleancache support with working zcache driver, utilizing the new lzo library
entropy threshold tweaks, /dev/random linked to /dev/urandom
github 14-22/07/2013 commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk
12/07/2013 1.4.1 -> 1.5:
Decrease CPU voltage for frequencies below 1.2GHz, increase CPU voltage for frequencies above 1.2GHz
Re-enable MMC_CAP_ERASE for I/O speed improvement, run "fstrim -v /data" and "fstrim -v /cache" manually to TRIM your filesystem or run LagFix (fstrim GUI, download it from Play)
Remove my old hack in cpufreq driver
Newer PowerVR SGX540 3D kernel module and vendor binaries, in sync to CM-10.1. You must update both 1st and 2nd ROM to renew both ROM vendor binaries!
SuperSU v1.41
16/06/2013 1.4 -> 1.4.1:
I/O speed improvement, 1.3 and 1.4 bugfix
SuperSU v1.34 - thanks Chainfire
nooc: Smartreflex class 3 re-enabled, voltage control disabled
04/06/2013 1.3 -> 1.4:
Selected kernel modules, scripts, and binaries integrated in boot.img, single flash for 1st and 2nd ROM
Kernel compression back to gzip, boot.img compression switched to lzma for better compression (I need more space)
Auto root (for stock)
Auto busybox (for stock)
External sdcard and internal media swapper script integrated in boot.img (for stock as 1st ROM)
Override init.d CPU governor setting on boot completed (technical reason/by design). Please use an app "on boot" or /etc/init.post_boot.sh to set CPU governor
init script reworked (again), simplified
Standalone nooc version, no longer as an addon for standard NEXT
Untested CRT off animation support
NEXT users, please update your kernel to 1.3 version to avoid filesystem corruption risk on Samsung stock/stock based ROM! Please read Dual Boot FAQs how to update your kernel!
01/06/2013 beta -> 1.3:
Better data integrity on both 1st and 2nd ROM
Ramdisk init scripts reworked, inline with the latest Samsung (Taiwan BRI 04/2013) and CM (29/05/2013 nightly)
Inline with P31xx, that's way this port version directly jump to 1.3
Updated exFAT modules (don't know it's better or worse, it's closed source)
Default CPU clock still 1.008GHz, default GPU clock 307.2MHz. Non OC version as an addon
Both version tested on P3100 (remember, I have no access to P51xx device). Booted, upscale graphics, touchscreen not work, wrong orientation sensor, swapped volume button, got 1280x800 screenshots :laugh:
30/05/2013: Initial beta release.
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p11 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel
b) Flash new ducati vendor blobs (since 1.8.x)
c) Flash latest PhilZ Touch - blackhawk repack version - recovery
d) Atleast 90% battery left.
e) 2 GB free on internal SD.
f) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
vi) Flash new ducati vendor blobs again (since 1.8.x)
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Flash blackhawk's NEXT tool, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Flash new ducati vendor blobs again (since 1.8.x)
viii) Reboot into primary recovery
ix) Flash aosp ROM as 1st ROM
x) Flash blackhawk's NEXT kernel again
xi) Flash new ducati vendor blobs again (since 1.8.x)
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel, flash new ducati vendor blobs again (since 1.8.x)
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in primary and secondary recovery. Yes, on both 1st and 2nd ROM. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition (since 1.4 version). Flash new ducati vendor blobs (since 1.8.x) on both ROM may be required to ensure vendor blobs match to the kernel
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
26. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
27. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
28. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p10 = /data
mmcblk0p9 = /system
mmcblk0p7 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk0p11 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p10 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p11 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Dual Boot Exercises
http://forum.xda-developers.com/showthread.php?t=2285366 post #4.
Was waiting for this :victory:
Sent from my GT-P5110 using XDA Premium HD app
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button or better my DTM button
PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Marionette said:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
Dual Boot FAQs #29.
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
brolee93 said:
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
Click to expand...
Click to collapse
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Running smoothly for Zap Blaster.
ironmaskusa said:
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Click to expand...
Click to collapse
I actually watched your HDMI problem. It's one of the reasons this dual boot solution was born. Glad I could help you, thanks for your support :good:
shakatu said:
Running smoothly for Zap Blaster.
Click to expand...
Click to collapse
Really? And all your init.d scripts removed by NEXT
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
shakatu said:
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
Click to expand...
Click to collapse
Personally, I found that Zap Blaster works well my device (p5113) because of the IR and such.. plus at the time it was overclockable and my HDMI output worked well with it. So, I decided to use it for awhile.. but I could not resist CM because it runs so smooth and I love how clean and reliable it has always been on me for this device as well as other devices I have owned.
Again, I am very happy about this DUAL boot option and I don't think I will change my setup for a time to come... My tablet is perfect now, in my opinion. Thanks again, KK.
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
behemot24 said:
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
Click to expand...
Click to collapse
For free A lot of clicks to install NEXT package but why people missed to click my Thanks button
EDIT:
This kernel version will directly jump to 1.3 in order to sync with P31xx version. Still inspecting line by line using diff tool to make sure already in sync
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
rap3rman said:
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Two apps I never use on my tablet, so I haven't tested them...
ketut.kumajaya said:
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
Click to expand...
Click to collapse
yeah ok i see this .
can you add Stweaks support ?
Hey all,
This kernel works on stock 4.2 ROM's only.
Disclaimer
This kernel, in any way, won't make your device fly or break antutu charts. What I can only promise is a consistent performance with reliable battery life.
Instructions:
flash zip in recovery
Features:
Integrated CWM
Linaro 4.9.1
kexec hardboot support
Full SELinux Support with upstream fixes
Userspace voltage control
Updated prima wlan with CAF fix for delayed notifications
1.2 GHz max frequency
More GPU clocks with optional overclock to 450 MHz
CAF backport fixes
vibrator intensity control
Kill debug wherever possible to reduce overheads
general tweaks here and there
Note: For full in-depth info, checkout my commits and release notes. I am not huge fan of bloated feature list since end-user may find it too difficult to grasp.
Although every feature is controllable through sysfs, I would still recommend trickster mod or kernel tuner app for tweaking.
Kernel will boot with my recommended settings but you can change them if you know what you're doing.
Download
Source
Release Notes
1. r1
* Initial release
* Hotplug driver: This kernel uses stock mpdecision by qcom. I won't be switching to other custom hotplug driver in a foreseeable future.
* Single initrd: I wasn't happy with standard method of packing two ramdisks inside an initrd. This caused unnecessary cpu overheads while decompressing boot ramdisk especially heavily compressed ones like xz and rewriting data to rootfs /. So I forked a process from init.rc to detect keychecks and exec recovery init from stock initrd itself. This improves upon the situation above by having everything we need in stock initrd itself. Boot times also become relatively shorter. I would recommend kernel developers to switch to this method.
* Kexec Hardboot : zip will automatically install all required kexec binaries.
Place your zImage and ramdisk.img in /sdcard/kexec/* and in terminal type:
do-kexec.sh
kexec -e
* Vibrator intensity control:
sys interface is located at /sys/devices/virtual/timed_output/vibrator/level
* Updated Prima: Stock fw used ancient prima 3.2.1.1h. I upstreamed it to 3.2.2.0 with CAF fix for delayed wifi notifications.
* sched_mc_power_savings = 1
Tries to group tasks into least cores possible. Battery friendly. 1 is moderate. 2 is extreme. 0 disables it.
* Userspace voltage control by @faux123:
I modified the original code by introducing a useful pr_info to actually output voltage change requested in mV. Also some cosmetic conditional and looping changes.
To determine the last voltage change, type dmesg | grep requested
The sys interface is located at:
/sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels.
Sample command to decrease voltages at all frequencies by 10mV
echo "-10000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
By default, kernel comes with 20mV undervolt.
* patch CVE-2014-0196
* add row and sio iosched
* Enable writing to hardware rtc
* More gpu scaling levels : 450 MHz and 128 MHz
* External modules.zip : cifs.ko, ntfs.ko, nls_utf8.ko, hid-sony.ko
* HID driver for Sony / PS2 / PS3 BD devices : hid-sony.ko
ramdisk will automatically insmod it if found.
* VM_MAX_READAHEAD512
* sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire
* lib: Update RWSEM to Linux 3.10
* lib/int_sqrt.c: optimize square root algorithm
* enable some more TCP Cong methods
* deadline tweaks
* partially nuke cci stuff
* switch to noatime and nodiratime
This option stops recording the last file access time when the file is just read. The noatime option eliminates all the writes to the disk each time a file was just read which previously used to happen with atime. However a write is made to a disk in case if a file is being changed/written. Easy on cpu and battery.
* tick: Upstream fixes
* xz compression for zImage ( best compression ratio ) and gz for ramdisk
* kill debug such as DETECT_HUNG_TASK, DEBUG_ATOMIC_SLEEP etc. which cause unnecessary CPU overheads
* enable adb RSA authentication
ro.adb.secure=1
* ro.debuggable=1
* Various CAF backport fixes including fixes to SELinux
Please don't ask for:
1. Anything that ends with *to-wake/sleep/dance
Got a bug?
cat dmesg and pastie me.
Credits:
@faux123: for voltage control
@franciscofranco: for some patches I took from his mako repo
@varun.chitre15 : for some patches i took from his caf repo
1.17 fw + vengeance r1 super smoooooth thank you
Great work
Thanks a lot
Sent from my C2105 using XDA Premium 4 mobile app
Ah, another great work from you. Gonna try it tomorrow!
Again, thanks for the work! I'm your loyal kernel-user since i got my miro vengeance-ed
Offline charging was borked due to ramdisk. Links reupdated with fixed version. Also softer vibrate when entering recovery.
Make this kernel available to CM11 4.4.4 KitKat please
Because most of us are currently using CM11
Sparksys said:
Make this kernel available to CM11 4.4.4 KitKat please
Because most of us are currently using CM11
Click to expand...
Click to collapse
although im agree with your comment "Make this available for cm", if there is no devs for JB, then this device will die. Its nice to have someone who still developing JB Kernel
FajarMF28 said:
although im agree with your comment "Make this available for cm", if there is no devs for JB, then this device will die. Its nice to have someone who still developing JB Kernel
Click to expand...
Click to collapse
You are right
Even TZ and phantom must back to support jb
Sent from my Xperia L using XDA Premium 4 mobile app
Great work!!
Hello everyone. I tell them that I decided to try this kernel. Return to the stock ROM, take a few hours and the phone is going well, really feel the change, note the phone faster, more stable, the battery has performed very well so far no trace of the sensor bug the only bad thing as it is that if we turn off the phone's date and time settings are lost.
i need flash external modules too?? *unsure*
for now i flashed vengeance zip only ... how to fix date error?
thedemon786 said:
i need flash external modules too?? *unsure*
for now i flashed vengeance zip only ... how to fix date error?
Click to expand...
Click to collapse
You can read more about external modules in release notes.
Can you clarify a bit more on date issue?
rachitrawat said:
You can read more about external modules in release notes.
Can you clarify a bit more on date issue?
Click to expand...
Click to collapse
i think he mean that
Time and date rest in every reboot
Like is happened before with kk ROMs (just think)
Sent from my Xperia L using XDA Premium 4 mobile app
david makarove said:
i think he mean that
Time and date rest in every reboot
Like is happened before with kk ROMs (just think)
Sent from my Xperia L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Strange. I just rebooted my phone and there's no reset. Maybe I'll investigate later. I have been busy lately. [emoji1]
i was sent to 1970 LOL ... only at first boot ... its fine now
thedemon786 said:
i was sent to 1970 LOL ... only at first boot ... its fine now
Click to expand...
Click to collapse
Why some heavy 3d games have random stuttering effect after some time of playing them.. (frontline:commando 2 for example)
When i clock it to 1188 it does give me that lag free performance of some heavier games compared to stock kernel. (actuly it gives me the best performance in terms of gaming.... beats almost all other kernels. Even thunderzap and phantom can't reach this type of smoothnes in terms of gaming...but then again its custom 4.4 so i got used to lag).
Games runs amazing on 1188 but after some time it just get random freeze and start stuttering...can't even get to handle my phone to quit from the app because it wont get back to normal)
Any specific solution to this problem?
PS: Im back on stock because it doesn't have this issue with stuttering and if it does it only last for few seconds but the performance is quite lower then vengeance...
vuk030 said:
Why some heavy 3d games have random stuttering effect after some time of playing them.. (frontline:commando 2 for example)
When i clock it to 1188 it does give me that lag free performance of some heavier games compared to stock kernel. (actuly it gives me the best performance in terms of gaming.... beats almost all other kernels. Even thunderzap and phantom can't reach this type of smoothnes in terms of gaming...but then again its custom 4.4 so i got used to lag).
Games runs amazing on 1188 but after some time it just get random freeze and start stuttering...can't even get to handle my phone to quit from the app because it wont get back to normal)
Any specific solution to this problem?
PS: Im back on stock because it doesn't have this issue with stuttering and if it does it only last for few seconds but the performance is quite lower then vengeance...
Click to expand...
Click to collapse
try permormance gov maybe?
thedemon786 said:
try permormance gov maybe?
Click to expand...
Click to collapse
It has nothing to do with gov settings...
I encountered this with older version of phantom or thunderzap for JB also but never had it on kitkat.
Problem is that current kitkat kernels doesn't give that much of a boost in termps of gaming..... (atleast not for me)
I remember Varun mentioning about flashing the kernel immediately after u flash the ROM file, ftf in this case. Try that. Also means you will have to format your device.
Great Kernel
rachitrawat said:
Strange. I just rebooted my phone and there's no reset. Maybe I'll investigate later. I have been busy lately. [emoji1]
Click to expand...
Click to collapse
Greetings friend, I congratulate you for your great contribution, I am testing and everything is going well. In my case also is being presented the problem that I lose the time and date settings every time I reboot the phone. addition also happens that my manager asks me root file permissions every time I go to do some operation (copy, paste, etc.) and folders are appearing very strange names in both internal and external memory. Thanks for your help.
Yep, date and time resetted every boot. Just like the old version of Thunderzap JB bugs. I think Varun has already fixed that.
Q&A for [Kernel][23/10/14][D850]Rin Kernel 1.6
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Kernel][23/10/14][D850]Rin Kernel 1.6. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
i tried this method I. my att g3
Tectas said:
RIN Kernel for D850
Close to stock with some sugar added ... delicous!
Hey guys and girls,
you may have seen my unified stock kernel thread already (or may not, but doesn't matter). This kernel is my attempt to build up on the fixed source and add some additional features for us mod lovers to thinker with and to personalize your device to your usage. For now, I'll keep it close to my stock source and just pull some additional features and fixes in, but not to much. That may change in the future (maybe even soon), but for now, I'll stick to that paradigm.
First of, DISCLAIMER, I'm not responsible for bricked devices, dead unicorns, rainbows with missing colors, world war, nose bleed, void warranty (you know that already, don't you? your warranty is void now and it's your fault ) or any other harm happening to your device, you or people around you!
What does it serve?
Built with linaro 4.9.1 cortex-a15 optimized toolchain
IO Schedulers
BFQ
CFQ
DEADLINE
FIFO
FIOPS
NOOP
ROW
SIO
TRIPNDROID
VR (default)
ZEN
Governors
Adaptive
Conservative
DanceDance
IntelliActive
IntelliDemand
Interactive (default)
Lagfree
Lionheart
OnDemand
Performance
Powersave
SmartassV2
Userspace
Wheatley
Smartmax
Voltage control
SoundControl
Intelli-Thermal v2
Many under the hood fixes
Stability
More to come
How to apply it?
IMPORTANT: Read through all the requirements, steps and warnings before you do anything, if any requirement doesn't match or you don't know what one or more of the steps below mean or do, ask before you do any of them, if you don't know how all the steps can be done, let it be and wait for the bootloader unlock, I warned you, if you don't do and something bad happens, I'll just laugh at you!!
Requirements? Yes!
D855/P/K, F400/K/S/L, D850
Root
How to use the command line
PC
working fastboot
working adb
How to boot the kernel?
Plugin your device to the PC
Open a terminal and execute
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/stock-laf.img # backup the stock download mode to your external sd
exit # exit the superuser shell
exit # exit the adb shell
adb pull /storage/external_SD/stock-laf.img . # backup the download mode image from you external sd to the PC
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf # remove the stock download mode
BEWARE, THIS WILL REMOVE YOUR DOWNLOAD MODE!!! YOU WON'T BE ABLE TO FLASH KDZ FILES BEFORE YOU RESTORED IT!!!!
Turn off the device completely, plug in the USB-cable, if you pulled it out and start the device by holding vol up + power till you see some white text on the screen, fastboot should be written somewhere on the screen, afterwards execute the following command on the PC (while in the directory you've downloaded the kernel image to).
D850:
Code:
fastboot boot D850-rin-1.6.img # boot the kernel
BEWARE, NEVER USE FLASH AT FASTBOOT ONLY BOOT, IT WILL TRIGGER SECURITY OF THE LOCKED BOOTLOADER AND YOU WON'T BE ABLE TO BOOT ANYMORE!!!!
You're done now and booted to the custom kernel!
How to make sure you're running the kernel?
To check if you properly booted into the kernel execute this in the command line (terminal emulater or through adb shell):
Code:
cat /proc/version
it should show
Code:
Linux version 3.4.0-rin-g58903a9-dirty ([email protected]) (gcc version 4.9.1 20140710 (prerelease) (crosstool-NG linaro-1.13.1+bzr2673 - Linaro GCC 2014.07 - Cortex-A15) ) #53 SMP PREEMPT Thu Aug 14 13:26:42 CEST 2014
Once more a warning READ IT!!:
BEWARE, when you reboot you'll boot to the stock kernel, you'll have to boot the custom kernel over fastboot every time, when you boot normally, you'll be on the stock kernel, this won't lead to issues, but you'll miss the benefits of this kernel, I know that's not optimal, but the best we can get with the locked bootloader.
How to restore Download mode?
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/storage/external_SD/stock-laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf # restore the stock download mode from the backup on your external sd
Changes?
23.10.2014/1.6
D850 support added
Simple GPU Algorithm Support
Overclocking up to 2.76 Ghz
exfat support
intelli-thermal v2 added
smartmax governor added
memutil optimizations
build with NEON kernel mode
2-way call recording patch
DriveDroid cdrom emulation support
Faux SoundControl
Simple-OnDemand fixed
Cpu Freq Limiter
some small fixes and enhancements
14.08.2014/1.0.1
net/ipv4|include/asm-generic: Enhancement of out of bounds fix
14.08.2014
Initial release
Full list of commits can be found here
Where to get it from?
D850-rin-1.6.img: AndroidFileHost | xda | dev host
md5sum: cd843592764abee8cb03dc701612832e
Show me the so(u)rce(ry)!
https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-kitkat
Donators (huge thanks, you're simply great )
@Toneman07
@Helloworld294
@shaarky
Credits
XDA
Google
LG
@HolyAngel
@faux123
@KAsp3rd
myfluxi
If you like my work, please show your appreciation by pressing the thanks button, if you want to do more, i've nothing against a little donation, but I'm as happy when you just thank me by pressing the button
XDA:DevDB Information
Rin Kernel, Kernel for the AT&T LG G3
Contributors
Tectas
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.6
Stable Release Date: 2014-10-23
Created 2014-10-24
Last Updated 2014-10-24
Click to expand...
Click to collapse
phone and on the fastboot screen out it says that the file was to large... What does that mean and where did I go wrong
Was wondering if you will bump the kernel now that their site is live?
http://apps.codefi.re/bump/
kpparry0156 said:
phone and on the fastboot screen out it says that the file was to large... What does that mean and where did I go wrong
Click to expand...
Click to collapse
Please don't quote whole OPs...
Are you sure you took the right file? Just from saying "that's the procedure I've used" I can't tell, sorry, if that's exactly how you've done it, it has to work, as for anybody else, if you did something slightly different, you need to tell.
guyd said:
Was wondering if you will bump the kernel now that their site is live?
http://apps.codefi.re/bump/
Click to expand...
Click to collapse
Jup, coming today
bump kernel?
It's coming out today.. So I can bump a custom kernel or the rin 1.6 kernel for the d850 correct
kernel
Nice
Have you tried using any other toolchain? I came from arrrghhh's anykernel, which was built on SaberMod, which was very snappy as compared to Linaro in my testing.
Sent from my LG-D850
Sinterion said:
Have you tried using any other toolchain? I came from arrrghhh's anykernel, which was built on SaberMod, which was very snappy as compared to Linaro in my testing.
Sent from my LG-D850
Click to expand...
Click to collapse
Yes, tried sabermod already, it's just even stricter than linaro at compiling, have to change a bit stuff, to be able to compile with it, but it's already on the schedule.
Sent from my LG-D855 using Tapatalk
Tectas said:
Yes, tried sabermod already, it's just even stricter than linaro at compiling, have to change a bit stuff, to be able to compile with it, but it's already on the schedule.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Cool! Well if you need a tester for the D850, just shoot a PM my way!
Sent from my LG-D850
Curious why some devices get the green screen and some don't. I installed cloudy, then tried installing the kernel zip and same thing. Let me know if you want me to test anything if you get to a point and need someone that's getting the green screen, I'll be more than happy to help
Kernel Version Info
When I go to "Kernel Version" under "Software Information" it shows the Kernel Version as 3.4.0
Is this normal? Or is it supposed to say "Rin Kernel 1.7.1"?
What is the most efficient or favorite setup for Kernal
Thanks for getting a flashable zip file out! I was waiting for this because I didn't want to risk messing something up with the original installation method. From what I have read, people really like the kernel. I'm DLing it now!
OP. Any plans to make custom kernel's for AOSP Roms?
Sent from my LG-D850 using XDA Free mobile app
animator776 said:
When I go to "Kernel Version" under "Software Information" it shows the Kernel Version as 3.4.0
Is this normal? Or is it supposed to say "Rin Kernel 1.7.1"?
Click to expand...
Click to collapse
Yes, that's normal. Has something to do with the Linux version.
guyd said:
Yes, that's normal. Has something to do with the Linux version.
Click to expand...
Click to collapse
Ok, thanks. I was wondering because I've flashed kernels in the past that display a custom kernel version i.e. "Dorimanx"
I believe the kernel version that is displayed can be changed in the build.prop
Anyone care to post their stable settings for this kernel? I remember a similar thread for the S4 which really helped guys like me who aren't real familiar with all of the different kernel tune-ables.
I've searched the dev thread and this one but didn't see any reports about icon themes reseting after reboot. I finally flashed this kernel tonight and each time I've rebooted after tweaking cpu freqs, the icon theme I'd applied using Nova Launcher reverts back to default icons. I've been on stock kernel since July and this has only happened since flashing this kernel a few hours ago. Any ideas?
JediSooner said:
I've searched the dev thread and this one but didn't see any reports about icon themes reseting after reboot. I finally flashed this kernel tonight and each time I've rebooted after tweaking cpu freqs, the icon theme I'd applied using Nova Launcher reverts back to default icons. I've been on stock kernel since July and this has only happened since flashing this kernel a few hours ago. Any ideas?
Click to expand...
Click to collapse
I'm using Nova with some alternate icons without issue. Don't know what to tell you except it's working fine for me.
Problem solved and it wasn't anything kernel related. I forgot that I was playing with moving apps to SD the other day and moved all of my icon packs. Apparently, regardless of the launcher being used, it will load before the SD card initializes, so the icon packs aren't found. I've moved then back to the phone and all is well. Google is definitely my friend.
This post can be updated anytime.
For korean support and for those who can translate Korean, visit my blog:
http://kykint.tistory.com/
Download TWRP Recovery v2.8.7.0 for G906SKL
/* Requirements */
* Galaxy S5 broadband LTE-A (SM-G906S, G906K, G906L)
* Samsung stock firmware or Dokdo-projct
- Kitkat: ANK1
- Lollipop: BOG2 for G906K, BOH1 for G906S/L
* Custom recovery (Philz, TWRP, etc)
/* Note before using */
* Backup important data before installing
* Upon installation, every warranty inclusing KNOX becomes void
* I, kykint, am not responsible for any inconvenience or problems that occur while using this kernel
* Only one hotplug driver should be on (mpdecision, intelli_plug, alucard_hotplug, lazyplug)
Lazyplug is currently not supported on kernel customizing applications. Wait until their developers update.
* Dokdo-Project version of lolliwiz is highly experimental. Don't complain about battery drain.
It also does not support uninstaller yet.
/* About new installer */
Since Release 9, the installer will automatically extract your device's ramdisk, merge it with lolliwiz kernel, and then install it.
Upon installation, if a backup folder (/system/lolliwiz-bak) is found, it will automatically restore it first and then continue installation.
It will backup original boot.img and sensors library to the backup folder (/system/lolliwiz-bak) while installing.
There might be some problems regarding this new installer, so please keep the following instructions in mind.
* When installing another variant's ROM, do not install lolliwiz right after flashing ROM.
Install the stock kernel of your variant, and then install lolliwiz.
* Those who have been using R8 or older version of lolliwiz must flash stock kernel first before installing R9 or later.
* Do not install stock kernel when lolliwiz is installed on your device.
Only install stock kernel when uninstaller fails to remove lolliwiz and restore to stock kernel.
/* Kernel features */
Built with custom compiled krait-optimized UBERTC 5.2.1
Various compile optimization flags
Various improvements backported from Linux mainline
CPU Governors: franco interactive & conservative, intelliactive, and a lot more
I/O Schedulers: CFQ, ROW, DEADLINE, SIO, FIOPS
Custom hotplug drivers: intelli_plug, alucard_hotplug, lazyplug
CPU Voltage control
Adreno_idler GPU governor addon
Simple_ondemand is not crashing anymore
Display gamma control
Dynamic FSync Control
SELinux set as permissive by default
FauxSound ported for wcd9330 (LP only)
Support for kernel mode NEON
Optimized Kernel Samepage Merging
Quickwakeup driver by Motorola
Random driver ported from latest Linux mainline
Adaptive LowMemoryKiller
Full support for F2FS
Power-efficient Workqueue
Unaligned access support for lib
Init.d script support
Various minor fixes and improvements
/* Changelogs */
Refer to the 3rd post
/* Kernel customization */
Recommended applications: Kernel Adiutor, TricksterMod
/* Downloads */
Lolliwiz & stock kernels
Previous versions of lolliwiz
LW-G906-Dokdo-R*.zip : for Dokdo-Project users
LW-G906-R*_F2FS.zip : for F2FS users
/* F2FS Conversion Manual */
Refer to the 2nd post.
/* Chatters */
Release 9 and 10 are mostly bug fix releases, so there isn't much difference.
Kitkat support has been put off to R11, and if a bug is found again and R11 happens to be released early, it will be put off to later release again.
Still, I'm considering EOL of kitkat version as it is becoming harder to support the old Linux version.
/* Contacts */
You can contact me through telegram @maplezeon, but I won't listen to complaints.
On weekdays I'm mostly at school, from 7am to 10pm, so there's no much time for chats.
/* Source */
http://pc.cd/U2YrtalK
/* Special thanks to */
세이님, 티라미슈님, hsk님, arter97님, JustArchi, Christopher83, faux123,
franciscofrancoeng.stk, flar2, imoseyon, friedrich420, Google, Samsung
and every single one of you guys, for using my kernel
XDA:DevDB Information
Lolliwiz Kernel for SM-G906, Kernel for the Samsung Galaxy S 5
Contributors
kykint
Source Code: http://pc.cd/U2YrtalK
Kernel Special Features:
Version Information
Status: Stable
Created 2015-04-28
Last Updated 2015-09-11
Changelogs
Release 10 - Sep 7
Reverted GCC 5+ compatibility improvement patches
=> Hopefully fixed some applications disappearing
Unaligned access enabled explicitly for lib
Release 9 - Sep 6
Brand new installer
=> Now support all three variants (S/K/L), boot.img and sensors library are backed up in /system/lolliwiz-bak
Add uninstaller
Fixed proximity sensor not working
=> Caused by Merge of G906K Kernel source, solved by installing sensors library from OG2 firmware
Applied patches regarding media driver
Updated lz4 source and enable unaligned access
NVIDIA's power savings patch
Westwood as default TCP congestion control method
Optimized intelli_plug
New hotplug driver: Lazyplug by arter97
=> Currently not supported on kernel setting applications, wait for updates
Some GCC 5+ compatibility improvements
Release 8 - Sep 1
Added experimental support for Dokdo-Project
(Compatible with all three variables and every version of Dokdo-Project)
KK support dropped at the moment
LP: Common: Merged G906K OG2 kernel source
LP: kt: Merged OG2 ramdisk
LP: skt,lgu: Merged OH2 ramdisk
LP: kt: fixed a typo in ramdisk
Linux 3.10.70
Full F2FS support + source updated to the latest
Power-efficient workqueue
Random driver backported from Linux 4.2+
Another new hotplug driver - Alucard hotplug
Custom built UBERTC with Krait optimizations
New build optimization flags
Fixed min cpu frequency changing on its own
Dynamic fsync disabled by default
built-in support for NTFS
Other miscellaneous fixes and updates
Release 7 - Jun 28
LP: Imported patches from upstream (1,000+ patches)
LP: Linux 3.10.59
KK: Imported patches from upstream (300+ patches)
KK: Linux 3.10.6
Compile optimization flags from arter97's kernel, big thanks to @arter97
Added adreno_idler addon for adreno-msm-tz GPU governor
Removed Simple GPU Algorithm
Switched to UBER Toolchain, GCC 5.1
Added motorola's quickwakeup driver
Added patches to reduce wakelock
Backported random driver from Linux 4.0.6
Optimized KSM
Added adaptive_lmk
Various small fixes & improvements
Release 6 - May 30
Added support for KitKat
Fixed wrong boot.img arguments
Fixed Sweep2Sleep not working on some variants
Removed SEANDROID warning on boot logo
Added advanced TCP congestion methods
Disabled crc check for better performance
Merged BOE1 changes
Ramdisk compressed with LZ4
Other small tweaks & fixes
Release 5 - Apr 20
Removed smartassV2 CPU Governor
Added mythx_plug CPU Governor
Added support for kernel NEON mode
Removed Franco's Sound Control
Ported FauxSound for work with wcd9330
Applied patches for gpu and video driver
Imported latest interactive & conservative governor from franco's shamu kernel
Added support for KSM on/off
Enabled tuning option for Cortex-A15
Some minor fixes from faux123
F2FS Conversion manual
/* F2FS Conversion Manual */
(for LP and Dokdo-Project only, no KK support)
(Not tested on Dokdo-Project)
I will not add any additional explanations about F2FS, since this is a very risky task and recommended only for experts,
and since not knowing about F2FS means that you're not one of them.
Cautions
1. Conversion process of /data partition and filesystem will wipe away every single data in your device,
so every data in internal sdcard should be backed up on your PC.
2. Flashing /cache partition image when the device has already been converted to F2FS will format /cache partition to EXT4,
so manual conversion process of /cache partition to F2FS must be done again.
3. The /cache partition image mentioned above is included in stock firmware package, so be careful when installing stock firmware
4. Inside stock firmware is included a stock kernel which only supports EXT4, so again, be careful when installing stock firmware
5. /data and /cache partition must be set to the same filesystem, both EXT4, or both F2FS
6. I personally recommend that every process be done using my TWRP recovery, which will be posted in a seperate thread later.
7. The F2FS version of kernel zip has a '_F2FS' tag at the end of its filename, while EXT4 has nothing.
Be careful, Dokdo-Project version supports both EXT4 and F2FS, so they're not seperated,
and when converting to F2FS on Dokdo-Project, you can skip kernel switching(reinstalling) process.
How to change filesystem on TWRP
Wipe > Advanced Wipe > (Select a partition) > Repair or Change File System > Change FIle System > (choose between EXT4 and F2FS) > Swipe to Change
* It takes a great amount of time when changing to EXT4, up to several minutes.
How to check current filesystem on TWRP
Wipe > Advanced Wipe > (Select a partition) > Repair or Change File System
and you'll see your current filesystem on the upper part of the screen.
Converting to F2FS
0. For stability, flash uninstaller first if you already have lolliwiz installed.
1. Install F2FS version of Lolliwiz. (_F2FS.zip)
2. Change the filesystem of /data and /cache partition to F2FS.
3. Reboot into recovery mode again.
Back to EXT4
0. For stability, flash uninstaller first if you already have lolliwiz installed.
1. Install EXT4 version of Lolliwiz.
2. Change the filesystem of /data and /cache partition to EXT4.
3. Reboot into recovery mode again.
Installing stock firmware on F2FS
1. Reboot into download mode and install stock firmware with odin as usual.
2. When the installation finishes, it'll automatically reboot into recovery mode and flash CSC package.
Wait until androboy disappears and the device reboots again.
3. Reboot into download mode again.
4. Install my TWRP.
5. Reboot into recovery right after installing.
6. Install F2FS version of lolliwiz.
7. Format /cache partition to F2FS
8. Run factory reset if needed. This is an option.
9. Reboot.
If the device won't boot even if you carefully followed all of the above instructions, repeat the process again.
Thanks
Thanks I was on the Korean forums yesterday trying to translate lol.
I noticed there's a test for b5. Giving it a try.
One issue I seem to have on b4 and 5 test is that no matter what kernel tuning app I use if I turn off mpdecision and intelliplug on, after a reboot mpdecision always comes back on.
Audioboxer said:
I noticed there's a test for b5. Giving it a try.
One issue I seem to have on b4 and 5 test is that no matter what kernel tuning app I use if I turn off mpdecision and intelliplug on, after a reboot mpdecision always comes back on.
Click to expand...
Click to collapse
Kernel settings are set to defaults on each reboot and the default setting on hotplug is mpdecision on, intelli_plug off. That's why every kernel app has the ability to restore previous settings after reboot. Try enableing them, kernel adiutor works fine for me
kykint said:
Kernel settings are set to defaults on each reboot and the default setting on hotplug is mpdecision on, intelli_plug off. That's why every kernel app has the ability to restore previous settings after reboot. Try enableing them, kernel adiutor works fine for me
Click to expand...
Click to collapse
Thanks, but I told it to save settings. It's weird as all the settings were saved, including intelliplug on, but mpdecision was turned on as well. I'll uninstall it and start again!
Do you have a donation link btw?
Edit: Here is what I mean
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit2: Strange, I reflashed the kernel and it is now working!
Audioboxer said:
Thanks, but I told it to save settings. It's weird as all the settings were saved, including intelliplug on, but mpdecision was turned on as well. I'll uninstall it and start again!
Do you have a donation link btw?
Edit: Here is what I mean
Edit2: Strange, I reflashed the kernel and it is now working!
Click to expand...
Click to collapse
Nice to hear it's working well now.
I don't get donations, maybe you could donate to the REAL developers out there, they're always working hard for us XD
Very interesting!
I'm reading the Asian forums since a week and I have found that this kernel is well used.
How can I flash back stock kernel if something happens? And where can I find stock kernels??
If they are unavailable, I'd like to make my own Odin tar.md5 files for flashing stock kernel.
Can I follow the script/batch procedure (found here on Xda) that produces the tar.md5 flashable files?
Tnx!!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Thanks
PIRATA! said:
Very interesting!
I'm reading the Asian forums since a week and I have found that this kernel is well used.
How can I flash back stock kernel if something happens? And where can I find stock kernels??
If they are unavailable, I'd like to make my own Odin tar.md5 files for flashing stock kernel.
Can I follow the script/batch procedure (found here on Xda) that produces the tar.md5 flashable files?
Tnx!!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
No worries, I'll upload stock kernels for recovery/odin as soon as I get back home
kykint said:
No worries, I'll upload stock kernels for recovery/odin as soon as I get back home
Click to expand...
Click to collapse
Can you do it also for KitKat if you have then?
Tnx.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Sharing battery based profile still in testing
Hi everyone ,
i would like to share my battery based profile.
I used Trickstermod kernel app taken from bbs dot sonyue dot com
( The kernel app is under attachment)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install the app.
2. Open the app, at top left a list will open, Choose the General
3. Change the following
I/O Control:
Read Ahead Buffer Size 1024
Schedular fiops
CPU Frequency Control
Frequency Lock ON
Min 300000 (choose the lowest scroll to the top first)
Max 1574400
CPU Governor Control
Governor Conservativex
------------------------------------------------------------------------------------------------------------------------------------------
4. Now Choose Specific
Mp-Decision OFF
Intelli-Plug ON
Dynamic FSYNC ON
GPU Governor Powersave
GPU Max Frequency 240
Intelli-Thermal Control ..........> Intelli-Thermal ON
MPU Voltages
( I undervolted from Snapdragon 805 thread in xda)
< 300MHz 700
< 345MHz 710
< 422MHz 720
< 499MHz 730
< 576MHz 740
< 652MHz 750
< 729MHz 760
< 806MHz 770
< 883MHz 780
< 960MHz 820
< 1036MHz 830
< 1113MHz 840
< 1190MHz 850
< 1267MHz 860
< 1344MHz 870
< 1420MHz 880
< 1497MHz 890
< 1574MHz 900
< 1651MHz 910
< 1728MHz 920
< 1804MHz 930
< 1881MHz 940
< 1958MHz 950
< 2035MHz 960
< 2112MHz 975
< 2188MHz 990
< 2265MHz 1005
< 2342MHz 1020
< 2419MHz 1035
< 2457MHz 1040
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Or You can download the profile in attachment and do the following:
1. Download the profile and extract it.
2. Go to your phone storage and look for a folder name tm_profiles
3. Paste it there.
4. Open the trickstermod app.
5. press at the top left and choose Tool.
6. You will find Global Profile. press restore and choose my profile Battery Test V2 pvs11 .
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope you will test it guys and my aim is just battery light user no gaming.
Please feedback its just test if you more knowledge share as i already contacted the OP permission to open a profile thread.
@kykint
Undervolting source
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
kardinal969 said:
Hi everyone ,
i would like to share my battery based profile.
I used Trickstermod kernel app taken from bbs dot sonyue dot com
( The kernel app is under attachment)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install the app.
2. Open the app, at top left a list will open, Choose the General
3. Change the following
I/O Control:
Read Ahead Buffer Size 1024
Schedular fiops
CPU Frequency Control
Frequency Lock ON
Min 300000 (choose the lowest scroll to the top first)
Max 1574400
CPU Governor Control
Governor Conservativex
------------------------------------------------------------------------------------------------------------------------------------------
4. Now Choose Specific
Mp-Decision OFF
Intelli-Plug ON
Dynamic FSYNC ON
GPU Governor Powersave
GPU Max Frequency 240
Intelli-Thermal Control ..........> Intelli-Thermal ON
MPU Voltages
( I undervolted from Snapdragon 805 thread in xda)
< 300MHz 700
< 345MHz 710
< 422MHz 720
< 499MHz 730
< 576MHz 740
< 652MHz 750
< 729MHz 760
< 806MHz 770
< 883MHz 780
< 960MHz 820
< 1036MHz 830
< 1113MHz 840
< 1190MHz 850
< 1267MHz 860
< 1344MHz 870
< 1420MHz 880
< 1497MHz 890
< 1574MHz 900
< 1651MHz 910
< 1728MHz 920
< 1804MHz 930
< 1881MHz 940
< 1958MHz 950
< 2035MHz 960
< 2112MHz 975
< 2188MHz 990
< 2265MHz 1005
< 2342MHz 1020
< 2419MHz 1035
< 2457MHz 1040
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Or You can download the profile in attachment and do the following:
1. Download the profile and extract it.
2. Go to your phone storage and look for a folder name tm_profiles
3. Paste it there.
4. Open the trickstermod app.
5. press at the top left and choose Tool.
6. You will find Global Profile. press restore and choose my profile Battery Test V2 pvs11 .
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope you will test it guys and my aim is just battery light user no gaming.
Please feedback its just test if you more knowledge share as i already contacted the OP permission to open a profile thread.
@kykint
Undervolting source
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
Click to expand...
Click to collapse
Good!
I'm following the Asian forum where I've found this kernel and related config app, from which I've read that there's a modified version of the app....And for this please give me some infos.
I'm also searching for some interesting custom rom as I see there are some, like the KingWolf one or the Milan one.
Any help on using this kernel with some roms?
Tnx!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
PIRATA! said:
Can you do it also for KitKat if you have then?
Tnx.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
I uploaded lollipop stock kernels for both recovery and odin. I'll upload for kitkat as well when I get the latest kitkat firmware.
Sorry, this might be a dumb question, but I'd rather ask it then brick my only smart-phone:
I'm currently on miscom's ROM (see here: http://forum.xda-developers.com/galaxy-s5/development/galaxy-s5-g906-custom-rom-t2848569)
Also using Philz recovery
How do I get to the Lolliwiz Kernel safely? Can I keep my apps, settings and so on?
Again, sorry. This is my first android phone (but certainly not the last one!) and I'm pretty clueless... But getting the miscom kernel on it was pretty easy with a bit of reading...
mcbrite said:
Sorry, this might be a dumb question, but I'd rather ask it then brick my only smart-phone:
I'm currently on miscom's ROM (see here: http://forum.xda-developers.com/galaxy-s5/development/galaxy-s5-g906-custom-rom-t2848569)
Also using Philz recovery
How do I get to the Lolliwiz Kernel safely? Can I keep my apps, settings and so on?
Again, sorry. This is my first android phone (but certainly not the last one!) and I'm pretty clueless... But getting the miscom kernel on it was pretty easy with a bit of reading...
Click to expand...
Click to collapse
Make a backup of whole apps with TitaniumBackup first, then backup system, data, boot in philz recovery(run custom backup) and flash stock lollipop through odin. miscom's rom is 4.4.2 as I know of, and my kernel supports 5.0.1 only at the moment.
If your phone bootloops after flashing lollipop, factory reset through philz and restore apps from TitaniumBackup, or flash back stock kitkat firmware and then restore system, data, boot in recovery.
Note that flashing stock firmware will blow away your recovery and you should manually install it again with odin. Also, factory reset through philz will preserve your internal sdcard but stock recovery WILL NOT.
kykint said:
Make a backup of whole apps with TitaniumBackup first, then backup system, data, boot in philz recovery(run custom backup) and flash stock lollipop through odin. miscom's rom is 4.4.2 as I know of, and my kernel supports 5.0.1 only at the moment.
If your phone bootloops after flashing lollipop, factory reset through philz and restore apps from TitaniumBackup, or flash back stock kitkat firmware and then restore system, data, boot in recovery.
Note that flashing stock firmware will blow away your recovery and you should manually install it again with odin. Also, factory reset through philz will preserve your internal sdcard but stock recovery WILL NOT.
Click to expand...
Click to collapse
Wait a minute!!! I though that factory reset in Philz recovery for G906 was not working and doing that would brick the phone!!!!!
I've read this in the info thread on the S5 G906 here on XDA!!!
Look under here in the Known issues:
prodigiez said:
.........
CWM
Unofficial PhilZ recovery is also available as below
Credit to hsk for unofficial CWM
updated : adb fix for cwm
Source: http://www.matcl.com/?m=bbs&bid=appDB&where=subject|tag&keyword=hsk&uid=231166
PhilZ Touch official thread http://forum.xda-developers.com/showthread.php?t=2201860
Download unofficial philz cwm here
This document is unofficial (Unofficial) ported version.
There may be bugs, so please use at your own risk.
Before flashing this, you must understand the contents of this post after you decide whether to apply please.
G906S/K/L = Tested working.
Flashing guide
Flash philz cwm with Odin as AP/PDA
Uncheck Auto Reboot and Start flashing.
Once completed , disconnect the USB cable and enter recovery manually by pressing the combination key.
Recovery time and date synchronization
PhilZ Settings - GUI Preferences - Time Setup - Change date and time - Qualcomm Time Daemon and (x) check - Yes Load Time Daemon
PhilZ Settings - GUI Preferences - Time Setup - Time Zone ( your preferred timezone )
Date / time will be synchronized with the system.
Reboot device.
Known issues:
KNOX Warranty 0x1
.
Wipe Data / Factory Reset from Clean to Install a New ROM feature is not working and might brick your device. Do not use this feature. If you brick your device , you may download the stock firmware from sammobile and flash it with ODIN.
CWM does not work with adb. CWM now works with ADB
CWM does not work with aromafm.
Credit to : XDA , PhilZ , hsk , bluecloud ,dougiebee and whoever involve. Tks
.......
Click to expand...
Click to collapse
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Great.... Bricked it.... Gonna need you guys' help again....
Did it like instructed... After flashing stuck lollipop, stuck on the second boot logo ("olleh o" for me).
Since recovery went back to stock, tried a factory reset and cache delete from the stock recovery... no help....
UPDATE: HOLD THE HELP!!! Unbricked it! On Stock Lollipop now... Working on it... Will get back to you....