Develop Bugs

[KERNEL] [09 MAR 2011] --Kernel GL_Core v11-- 1190 / uv EXT2/3/4 CIFS EB -magldr+cLK-

Presenting, my HD2 NAND Android kernel!​
Summary
To provide, stable, fast and up to date kernels for our HD2s running either DFT or CWM nand android
Features
- 1190, 1190 Undervolt auto scaling versions available. listed is kernel MAX speed, it will scale to anything less depending on demand and ROM installed. Default max seepd is 998 without the use of an overclocking app
- Faster IO tweak taken from hastarins kernel tree
- Latest YAFFS driver
- Always built from latest source tree
- Very responsive kernel configuration
- Battery efficient
- Supports EXT 2 / 3 / 4, depending our your chosen ROM
- RMNET / PPP both supported, depending on your chosen ROM
- Bluetooth, WiFi, LED notifications all working correctly
- Smartass (default), Interactive and all standard CPU governors supported
- CIFS supported
- MAX defualt speed is 998, use setCPU or similar to overclock if you so wish
- cLK supported
- Automatic Extended Battery Support
Choosing your kernel
1190Mhz
This should work perfectly on nearly every HD2. It offers good speed at a slight cost to battery life. It will, depending on how your chosen ROM implements it, scale anywhere between 245-1190 Mhz depending on load
1190Mhz Undervolt
Same performance as 1190Mhz above, but with lower CPU voltage settings. It will work perfectly on most phones, but not all. If you experience FCs or random reboots then chose one of the aforementioned versions. This kernel offers significant battery life improvements if it works for you.
About the source and GPL compliance
The kernel is built direct from main GIT. You can access the commit logs and sources here on gitorious
The changes and modifications as mentioned in the changelog, and my build .config are all in my separate patch file, which you can download here
Download
All the kernels are supplied on one zip package. Contained within the package are the 2 kernel zImages and the associated modules. Chefs and advanced users will know what to do with these.
Download v11 (files only) --> http://htcfanboys.com/CleanEx/Kernel/DISTRIBUTION KERNELv11.zip
Download CWM ZIPs FOR NON TYPHOON ROMS (*series A*)
http://forum.xda-developers.com/showpost.php?p=11968195&postcount=408
Download CWM ZIPs FOR TYPHOON ROMS / ROMS SHIPPED WITH TYTUNG v6 (*series B*)
these include the wpa_supplicant fix for Wifi / bootlooping
http://forum.xda-developers.com/showpost.php?p=11974837&postcount=471
(the RAM named ones are for typhoon ram build)
Flash under cwm.
Wipe Cache and Dalvik Cache.
~~~~IMPORTANT~~~~
If you are not sure you need the WiFi patch, flash the *series A* kernel. If you find your phone bootlooping / wifi crashing, flash the *series B* kernels
As a backup, the wifi patch remains attached to this post
Changelogs
v11
- Pulled new updates from GIT
- Automatic Extended Battery support
- cLK patches and support built in
- some cleanups
- config changes, more responsive (quadrant wont improve thats IO bound)
v10
- Bug fixes, WiFi should work for everyone without the patch
- Imported the i2c, gsensor, GPU decoupling driver patches to new build tree
- Removed all debugging from kernel (99.9% people dont need it)
- Some build config changes, little more responsive
v9
- Fixed WiFi driver for non GB builds
- Fixed default CPU speed @ 998 max
- Fixed crashes / bootloops / random reboots
v8
- Switch to main branch, import speed mods from previous version
- Fix WiFi for GB / non-GB builds
- config changes for better response times
v7
- Switched to tytungs branch
- Swapped tytungs GB only WiFi driver for main one from primary GIT
- Added CIFS support
- Removed 998 / 1536 speeds
- 1190 Normal is not undervolted and will work for everyone
- 1190 uv is undervolted and might not work for everyone
- Reverted to SLAB, should fix bootlooping
- Other minor config changes
v6
-First public release
Disclaimer
I am not responsible for any damage, loss of data or earnings resulting from the use of my kernels. Users who wish to use an overclock kernel do so on the understanding that running any device outside its normal operating parameters may have damaging consequences
Credits:
Cotulla, Bepe, Hastarin, Tytung, Rafpigna, Markinus and all other kernel source contributors as mentioned on the GIT Commit logs.
Fadzy, JoPlayer, Dave and Jan-Willem for their never ending support, friendship, help and good laughs.

First! This is in a kleandroid 2.55?

yes....and no
its just been recompiled, and i added pure 998mhz for people who have phones that cant take the faster speeds!

Awesome! This is the best kernel, have been using it for like three days and it gives me the best battery life and performance. I loved it. I'll pack this one into cwm zip when I get home and flash it.
Edit: how much does battery life actually improve with the uv one? Now I'm torn between the uv and oc to 1.5ghz. Battery or performance?
Sent from my HD2 running Android on NAND

Can anyone test this on sergio's coredroid 1.4 and post results? I would but dont have my computer for a couple days.

g.lewarne
Please add 998Mhz kernel to next update CleanDroid!

Derek0228 said:
Awesome! This is the best kernel, have been using it for like three days and it gives me the best battery life and performance. I loved it. I'll pack this one into cwm zip when I get home and flash it.
Edit: how much does battery life actually improve with the uv one? Now I'm torn between the uv and oc to 1.5ghz. Battery or performance?
Sent from my HD2 running Android on NAND
Click to expand...
Click to collapse
you might get maybe possible 15% more battery time out of the UV kernel. in ideal circumstances in a perfect world of course

CWM
How to use that? :-(
Any zip to use on cwr?

felipemadox said:
How to use that? :-(
Any zip to use on cwr?
Click to expand...
Click to collapse
Not yet, it is still underway.

I made some cwm zips, before going to sleep. I wasn't able to test them because it's late, but they should work. If g.lewarne wants to post them in the OP, i have no problem. Inside the zip, after you download, there are 4 more zips, one for 998, 1190, 1536(this one doesn't work for me) and 1190 UV. Just flash the one you like and enjoy!
http://www.multiupload.com/DPR3F7TW7J
http://www.mediafire.com/?sqg55hze9evgchb
If you find this useful donate me a click on my thanks button.

Thanks derek.

g.lewarne said:
Thanks derek.
Click to expand...
Click to collapse
Once tested, please update, i will test a rom on it.

raviluke said:
Once tested, please update, i will test a rom on it.
Click to expand...
Click to collapse
I can't test anything now as im off to bed . Its 2am and I did a 14 hour day. Yawn!

report
Derek0228 said:
I made some cwm zips, before going to sleep. I wasn't able to test them because it's late, but they should work. If g.lewarne wants to post them in the OP, i have no problem. Inside the zip, after you download, there are 4 more zips, one for 998, 1190, 1536 and 1190 UV. Just flash the one you like and enjoy!
Please give feedback, again I say, they should work but haven't tested them. I've made all his previous kernel versions cwm zip, and flashed them successfully.
http://www.multiupload.com/DPR3F7TW7J
http://www.mediafire.com/?sqg55hze9evgchb
Click to expand...
Click to collapse
Thank you!
1190Mhz Undervolt its working here.

1536 does not work for ne! Causes random reboot on boot. If you want to test it, do so, but i'm pretty sure it's a problem with the kernel, not with the zip, because the one g.lewarne uses on his rom had 1536 and caused random reboots too, cant be a coincidence . Also, youre welcome!
I flashed the 1190 to test, now off to flash the UV one!
Sent from my HD2 running Android on NAND

raviluke said:
Once tested, please update, i will test a rom on it.
Click to expand...
Click to collapse
It works, but not the 1536 one, or at least not for me.
Sent from my HD2 running Android on NAND

Might I just point out that in real world situations the 1190 kernels are just as fast. 1536 is really just a gimmick but some people want it so there you to. Myself, I run my own personal 1305

Sorry for spamming this thread, but I must ask, is uv dangerous? If so, what are some steps I have to follow to prevent my phone from getting fu'd? Like for example,i know that for the 1536, we shouldn't have it always o/c'd to the 1.5ghz.
Sent from my HD2 running Android on NAND

Derek0228 said:
Sorry for spamming this thread, but I must ask, is uv dangerous? If so, what are some steps I have to follow to prevent my phone from getting fu'd? Like for example,i know that for the 1536, we shouldn't have it always o/c'd to the 1.5ghz.
Sent from my HD2 running Android on NAND
Click to expand...
Click to collapse
Uv Isn't dangerous in the same way, the only problem is possible crash, cpu is safe

Derek0228 said:
I made some cwm zips, before going to sleep. I wasn't able to test them because it's late, but they should work. If g.lewarne wants to post them in the OP, i have no problem. Inside the zip, after you download, there are 4 more zips, one for 998, 1190, 1536(this one doesn't work for me) and 1190 UV. Just flash the one you like and enjoy!
http://www.multiupload.com/DPR3F7TW7J
http://www.mediafire.com/?sqg55hze9evgchb
If you find this useful donate me a click on my thanks button.
Click to expand...
Click to collapse
Installed the UV Kernel on Coredroid v1.4 TMOUS ver its getting stuck at GO GO GO

[KERNEL] [GPL] [4.3] FuguMod kernel (3.0.101) (open, stable, reliable and secure)

FuguMod kernel is now available for the Galaxy Nexus.
It has been reported to work both on GSM and CDMA versions. But I can only test it on GSM version myself.
You can download them at:
http://fugumod.org/galaxy_nexus/
Source and changelog can be found here:
https://github.com/renaudallard/gnexus_kernel
IRC channel:
irc.freenode.net #fugumod
To install, just download the appropriate version for your ROM (4.0.x) and flash it with fastboot (RAW version: fastboot flash boot kernel-$VERSION.img) or flash it with CWM (CWM/zip version).
Please note that not all versions exist in CWM format.
4.0.2 version is based on official google initramfs + init.d support (is now in deprecated state, no future updates will be brought)
4.0.3 version is based on the initramfs of AOSP + init.d support. it is compatible with 4.0.4
4.0.4 version is based on the initramfs of AOSP + init.d support. it is compatible with 4.0.3
4.1.x version is based on the initramfs of AOSP + init.d support.
4.2.x version is based on the initramfs of stock kernel
4.3 version is based on the initramfs of stock kernel (use that one for CM, not reco)
4.3-reco version is based on the initramfs of stock kernel, even with install-recovery.sh enabled (so supersu can work, but if you don't have supersu, don't use it)
for experimental versions, do not flash if you are not ready for big troubles, they may not even boot, burn your phone and eat your cat.
Features:
- stackprotector
- various security enhancements
- RCU boost
- Automatic process grouping
- TUN (compiled in kernel)
- latest 3.0 linux kernel
- newer wifi driver
- gamma/color hack
- CM9 compatibility
- PaX (from r333)
- grsec (from r624)
- TouchWake from Ezekeel (from r778)
Versions
Kernels are based on the below version scheme
kernel_FuguMod_20120111_r20-4.0.3.img
20120111 is the date it has been packaged
r20 is the release number
4.0.3 is the ROM it is compatible with
Color offsets
In CM9, just use the built in function.
For other ROMs, the settings offsets are in
/sys/class/misc/samoled_color/
For example green_v1_offset
Just edit the three green red and blue color settings. Default value is 60.
It can be done on the console with a command like this: echo 55> /sys/class/misc/samoled_color/green_v1_offset
Stable vs Testing
There are sometimes kernels in testing folder. These may be very stable or may not boot at all. Be sure to have an USB cable and fastboot under the hand if you try one of these. That said, in general, if they stay into testing folder for more than 15 min, they should at least boot and work more or less. I tend to remove non booting kernels from testing folder in less than 10 min (depending a little bit on the speed testers take them), and so if you see them one hour later, you should assume they are safe enough to flash.
So, in general Stable is the safest bet, but Testing may be the best. I, myself, generally run testing one.
Deprecated folder
In general, unless you really know what you are doing, you should avoid flashing those, they are mainly there for historical reasons.
Radio drops and blueish/faded screens
Please ensure you are running the correct firmware for bootloader and baseband, like in the matrix in bottom of that page: http://source.android.com/source/building-devices.html
For those where problems persist after flashing recommended versions, try "echo 0 > /sys/kernel/debug/smartreflex/sr_core/autocomp"
OTG unmounting internal SD
Please see http://forum.xda-developers.com/showpost.php?p=24040652&postcount=174
Mirrors
bootloaders: http://fugumod.org/bootloaders-gn/
basebands: http://fugumod.org/modem/galaxy_nexus/
Check for vulnerabilities
http://www.xray.io
Compatibility with hackish style apps
All apps which require direct memory write, access to symbols or memory offsets or modules will NOT work. And, no, don't ask they won't be supported in the future.
Security
If you want good security when your phone is stolen, in addition to encryption, don't forget to turn debugging off. Also, use enpasschanger to change your encryption password, any short PIN encryption can be cracked in a few minutes easily (for example, using my script at http://pastebin.com/Mdu06RZN)
Redistribution
As per GPL, you are authorized to redistribute this kernel with any of your custom ROMs provided you give out the source code like I do. You can link to my github in your distribution site.
However, if you modify the kernel yourself, whatever the modification is (compiling it yourself with a different compiler is a modification), you are not authorized to name it FuguMod, although you can credit me and tell the base comes from FuguMod but you cannot call the kernel itself FuguMod.
Touchwake
to enable it "echo 1 > /sys/devices/virtual/misc/touchwake/enabled"
to make it always on: "echo 1 > /sys/devices/virtual/misc/touchwake/always"
Beware, touchwake is known to sometimes produce screen locks
PGM
See "Compatibility with hackish style apps". Use touchwake instead.
Lost root
Use supersu instead of superuser from chainsDD (superuser from koush seems to work fine too). Change the setting in SuperSU to ignore CM root setting if you are running CM.
Updater app
https://play.google.com/store/apps/details?id=my.zin.rashidi.android.fugumod
root on 4.3
Currently only reco version has support for root access with supersu. Keep in mind that su access is now (as of 4.3) provided by a daemon, which may drain your battery or worse. Please think about your uses for root to see what is better fit for you.

W00t fugumod on the nexus!!
Will try it, thanks for dropping this here.

I'm totally happy

Finally! A kernel we can rely on Thanks alot mate, looking forward to further developments on this. I remember FuguMod fondly on the SGSII

Nitroz said:
Finally! A kernel we can rely on Thanks alot mate, looking forward to further developments on this. I remember FuguMod fondly on the SGSII
Click to expand...
Click to collapse
You probably mean SGS1.

I'm not entirely sure how accurate setcpu is at reading frequencies, but it seems to be stuck at 700mhz after a reboot. Moving the sliders a bit allows the cpu to use the entire range of 350-1200mhz as intended. I'm on AOKP milestone 2 if it matters and using r26.

Haven't yet tried this, but maybe min frequency when booting is set to 700mhz?
when you open setcpu, is the min slider at 350mhz?
What governor are you using? Not sure it matters though, but it might so.

maybe try using cpuspy to read the usage. Also, there may be something in your init.rd limiting the frequencies
Sent from a Nexus

Yes, min and max are set at 350/1200 on the sliders, but the green text says it's at 700/1200. Governor is the default interactive. Right now, I'm only using setcpu as a tool to view my frequencies as everything is "under observation" as I've only had this phone for a week. I did a reboot last night before going to bed. When I woke up 6 hours later, batt was down to 92%. Which is a quite fast considering I only had 5 hours of sleep. That's when I noticed that frequency was pegged at 700mhz the whole time. I tried opening other apps that should ramp up the speed, but as far as I can tell, it was still at 700.
Now, as I said, I'm only using setcpu to check my frequencies so "set at boot" isn't applied. When I apply "set at boot," min/max is at 350/1200 after a reboot and CPU scales up and down properly. So does this mean the default setting of the kernel is 700/1200? The thing is, even with max at 1200. I can't seem to make it scale up to 1200.
EDIT:
nikademus said:
maybe try using cpuspy to read the usage. Also, there may be something in your init.rd limiting the frequencies
Sent from a Nexus
Click to expand...
Click to collapse
I don't seem to have an init.rd file anywhere. I did a search using root explorer.
Edit 2:
CPUSpy says I'm only using 700 and DeepSleep even after running Asphalt 6. This is after a reboot without setting anything at boot with setcpu.

j.go said:
Yes, min and max are set at 350/1200 on the sliders, but the green text says it's at 700/1200. Governor is the default interactive. Right now, I'm only using setcpu as a tool to view my frequencies as everything is "under observation" as I've only had this phone for a week. I did a reboot last night before going to bed. When I woke up 6 hours later, batt was down to 92%. Which is a quite fast considering I only had 5 hours of sleep. That's when I noticed that frequency was pegged at 700mhz the whole time. I tried opening other apps that should ramp up the speed, but as far as I can tell, it was still at 700.
Now, as I said, I'm only using setcpu to check my frequencies so "set at boot" isn't applied. When I apply "set at boot," min/max is at 350/1200 after a reboot and CPU scales up and down properly. So does this mean the default setting of the kernel is 700/1200? The thing is, even with max at 1200. I can't seem to make it scale up to 1200.
EDIT:
I don't seem to have an init.rd file anywhere. I did a search using root explorer.
Edit 2:
CPUSpy says I'm only using 700 and DeepSleep even after running Asphalt 6. This is after a reboot without setting anything at boot with setcpu.
Click to expand...
Click to collapse
OK, 4.0.3 init.rc I have been given is the one from Francisco Franco and it limits the minimum frequency to 700mhz. This will be solved in next build, in a few minutes. Although you should be able to go over 700Mhz

nikademus said:
OK, 4.0.3 init.rc I have been given is the one from Francisco Franco and it limits the minimum frequency to 700mhz. This will be solved in next build, in a few minutes. Although you should be able to go over 700Mhz
Click to expand...
Click to collapse
Ah, well that's good to hear. Maybe the conditions needed to raise the frequency are not being met. Not that I know anything about kernels...

j.go said:
Ah, well that's good to hear. Maybe the conditions needed to raise the frequency are not being met. Not that I know anything about kernels...
Click to expand...
Click to collapse
Try the latest version, I removed all Francisco tweaks.

nikademus said:
Try the latest version, I removed all Francisco tweaks.
Click to expand...
Click to collapse
All right, I'll give it a spin tonight and post how it goes. Thanks!

I think I will be upgrading my phone to 4.0.3. This would mean I would not support 4.0.2 as I would not be able to test it properly. Are there users here who need the 4.0.2 version?

great
R37 für 4.0.3 runs flawless.
I use CM9 kang by fitsnugly.

R40 also flawless on fitsnugglys CM9 kang

r41 is out, probably last release for today

I flashed the latest KANG from today and the 122211 gapps with R41.
Works like a charm so far

aosp kang built today, flashed R43 just now. booted fine first try, wifi/bluetooth are fine, data call as well, rebooted, set scheduler/gov to deadline/ondemand, min/max freq to 1.2ghz, score on antutu maxing out around 5200, 5300. with my modified stock, i hit 6200+ in those conditions.
switch back to cfq/interactive, sd write speed goes up a bit to 10.4mb/s (deadline was just under 9.4mb/s), cpu integer 1304, float 1099, pushes score up a bit but still not reaching 5400 (this is with all tests selected, 2d/3d, database..). tweaked lowmemorykiller, antutu score jumps to 5600+.
but benchmarks mean almost nothing, i know. overall it's pretty smooth, fast on bootup, ocasional "lag" here and there (but that may be Mr. Android's fault).
will report more as the kernel settles in.
thanks nikademus.
edit: just re-installed gta. it seems i have no in-game sounds at all? it's fine until it gets to the main menu though. anybody else seeing this? happening on stock kernel too, wth..
edit2: jumping on r44.

flashed R44 on the latest fitsnugly kang. all is well. as expected, as only unused modules have been removed

[Kernel][TW][AOSP][KK][JB]MaxFour GT-I9500 (5410)[v14]

The first time I made AdaMax was for the Chinese Galaxy S4 Duos GT-I9502. I ported Adam kernel and added more tweaks from other kernels like Persus, halaszk (5420). After several releases, I decidec to spread this kernel to more models. So I built the v8 for both Chinese and international GT-I9500. This thread it for hosting it.
This week, i successed compiling for the s4 with 5410 cpu. As we know GT-I9500, GT-I9502 and SCH-I959. They share almost same compiling configure and their own ramdisk. So I compile them together with almost same features.
At last, I have to make following declarations, AGAIN:
Take your own risk and responsibility on flashing this kernel. I am not responsibale for any loss of your hardware, software, data or warranty.
Read this OP from start to finish before flashing the packages or asking any questions. There is a Q&A section. Any questions already answered will be ignored by me and may be insulted by other members. So save your your keyboard, your time and your data traffic.
No ETAs.
Don't ask me to make this kernel for a specific rom. There are basically only two kinds of roms, AOSP and TouchWiz. So I compile for these two kinds with differnet SDK levels. If it dose not work on some rom, don't blame me and ask me to adapt the rom for it.
If you found a new version, but its download link is not directly showed in this OP, that means it is a version I don't think good enough to be a release. So take your own risk to use it. I will remember your feedback, try to make changes, but not respond with posts.
Thanks to a lot of people, I will add their names here... @wanam, [email protected], @Dees_Troy and Team Win, @AndreiLux
As my habit, I always put the download link first:
v15: https://github.com/maxfu/android_kernel_samsung_exynos5410/releases/tag/v15-9500
File name instruction:
touchwiz: for most used international GT-I9500 with exynos5410 cpu.
aosp: for AOSP KitKat 4.4 roms like CM, ramdisk comes from CM 11
kk442: kernel for KitKat 4.4.2
jb43: kernel for Jelly Bean 4.3
jb442: kernel for Jelly Bean 4.2.2
lite: live version is built with stock zImage and maxfour initrd. It has limited maxfour features. And sometimes selinux f**ks up the STweaks.
boot: system kernel package
recovery: recovery kernel package
kernel: system + recovery combined kernel package
*.tar/*.tar.md5: Odin package
*.zip: CWM/TWRP recovery package
example.1: boot-i9500-aosp kk442-v10f1tc.zip means a system kernel image CWM/TWRP flashable package for international I9500 with TouchWiz KitKat 4.4.2 roms.
example.2: kernel-i9500-aosp-kk442-v10f1tc.tar.md5 means a system recovery combined odin package for international I9500 with AOSP roms like CM.
Old versions:
v14: https://sourceforge.net/projects/maxfuacm/files/Kernel/MaxFour/v14/GT-I9500/
v13: https://sourceforge.net/projects/maxfuacm/files/Kernel/MaxFour/v13/GT-I9500/
v12: https://sourceforge.net/projects/maxfuacm/files/Kernel/MaxFour/v12/GT-I9500/
v11: https://sourceforge.net/projects/maxfuacm/files/Kernel/MaxFour/v11/GT-I9500/
v10f1: https://sourceforge.net/projects/maxfuacm/files/Kernel/MaxFour/v10f1/GT-I9500/
You can always go to the following addresses to see whether there is a new version:
https://github.com/maxfu/android_kernel_samsung_exynos5410/wiki
https://github.com/maxfu/android_kernel_samsung_exynos5410/releases
I open the issue section for the source code, you can report problems here. Please provide at least version aosp/touchwiz jb/kk.
https://github.com/maxfu/android_kernel_samsung_exynos5410/issues/new
The source code:
You can
git clone https://github.com/maxfu/android_kernel_samsung_exynos5410.git
git clone https://github.com/maxfu/initramfs_samsung_galaxy_s4.git
git clone https://github.com/maxfu/toolchains.git
use the build.sh for exynos in toolchains/script ro build the kernel.
you need to su before build the kernel cause the ramdisk belongs to root.
Since this is a side product of my kernel for GT-I9502 which is the phone I am currently using. I don't actually test this build for GT-I9500, so I really need feedback. And please backup your rom before using this.
Features:
Built with OSRC KK 4.4 source and ramdisk, now it should work on many 4.4 roms.
Contains most features from Adam kernel including Wolfson Audio Control. For I9502 which uses yamaha sound chip, Wolfson Audio Control will be hidden automatically since it does not work.
From v10, the kernel is renamed to MaxFour due to wamam's request.
Kernel + Recovery release at one time, recovery based on TWRP with EFS_GSM (for Chinese Duos devices) support.
Compiled with GCC 4.8 toolchain from Google NDK r9c.
Packed in LZMA format to make smaller images.
Native exfat support based on OSRC exfat source code.
UCI script for STweaks and may be others.
Unlocked some hidden CPU frequency: 2.0GHz, 1.9GHz, 1.8GHz, 1.7GHz, 800MHz, 700MHz for big cores; 1.3GHz, 1.2GHz, 400MHz,
300MHz, 200MHz for little cores. Frequencies over stock like 1.7GHz for big cores and 1.3G for little cores are implemented in tc*/overclock version.
Added more STweaks settings which are not included in Adam kernel, including CPU power management, Tools with reboot options, GPU settings, CPU governor.
Android logger is compiled as standanlone module, so user can disable it completely to save power.
Tc/overclock version contains Persus dvfs for GPU with 700MHz overclock, thanks to AndreaLux.
Built-in Seeder entropy generator to provide lag reduction although it is not significant as it was on Gingerbread.
Built-in busybox with auto-installation.
Optimize on ram.
Added several I/O Schedulers including ZEN and ROW.
Built-in dynamic eMMC read ahead
Built-in Asynchronous Fsync
Compiled with compile flag for Cortex-A15 and NEON
Disable KNOX and SELinux when booting, selinux will be set to permissive with the boot command line.
init.d support.
A lot of changes and fixes.
Disabled a lot of rarely used devices support.
PS:
*1. TC means turbocharged, so it is overclock
Change Log:
v15:
Rebuild with GT-I9502 CHN KK Opensource from OSRC.
Upgrade KSM (Kernel Samepage Merging) to uksm (Ultra KSM) which has Super quiet CPU usage, Ultra scan speed and High CPU efficiency.
Support init.d.
Lower CPU frequencies presented in previous versions, voltage options coming soon.
GPU tweak presented in previous versions.
STweaks cueerntly unsupported, coming soon.
mDNIe and Sound Control coming soon.
AOSP support coming soon.
v14:
Upgrade kernel to 3.4.10
Implement AES-ARM and SHA1-ARM crypto algorithm
Rollback selinux related script to v11
v13:
Rebuilt source tree from HNC6 source.
Most features kept
INT, MIF, MEMIO settings removed, these should not be touched
Should be much better than v12
Fixed video bug for AOSP, I think it is fixed
Upgraded AOSP initramfs, may fix the modem/signal problem
Set ro.secure and ro.adb.secure to 0
Camera lag? Less.
Upgraded busybox
v12:
I don't want to talk about it, this version is totally a rubbish
v11:
STweaks: Added Chinese UI, works on Chinese system, when the language is set to other ones, English UI will show. An templete is provided for more translations.
STweaks: Added boost mode in the Misc tab. The boost mode is found when the news of Samsung cheating on benchmark softwares came out. When a benchmark software is detacted running, the boost mode will be on to allow higher temprature and faster CPU scaling. Simply turn on this mode will not provide any visable change, it should be used with CPU, GPU, INT, MIF clock operations.
STweaks: Added control for Internal, Memory Interface and Memory I/O.
STweaks: Added a button to switch the USB mode to Mass Storage Mode, which is classical mode before GingerBread got out dated.
STweaks: Added a CPU wake lock switch.
STweaks: Added instructiuon of Sound Control being not available on models other than I9500.
STweaks: Added instruction of GPU voltage control being not available on non-tc versions.
Kernel: Added a odin mode. Now we can reboot to download mode with "adb reboot odin". The original commands still work.
v10f1:
initial build for XDA users.
Q&A:
I did not reserve a post for this section, so I will put the Q&A here in the OP.
Q: Which package should I use? A: boot is what you need. recovery is just a side product.
Q: Which version I should use? A: Please the "File name instruction" section in the OP, you will find the answer.
Q: Do I need to wipe the data after I flash? A: Well I don't think you need, but due to some report, wiping data can solve certain problems after flashing this kernel. So whatever you like, please backup data before you flash or wipe.
Q: Which rom does this kernel support? A: I can't tell, please refer to the File name instruction section, if you rom is not mentioned there, it is not supported?
Q: Does this support MIUI? A: Official MIUI is based on touchwiz 4.2.2. So please refer to Q2,3,4.
Q: There is no OC in tc version. A: In the init.rc there is a script limiting the CPU frequency to 1.6GHz, so you should use STweaks to unlock it. Please open /sys/devices/system/cpu/cpu0/cpufreq/UV_uV_table, if there is 2000 1900 1800 and 1700, then there is OC, just unlock it.
Q: Some app FC? A: Usually FCs are not due to the kernel, check the rom first, and settings etc, the kernel should be the last reason, cause it just provide the bridge between the system hal and hardware. Report the fc, I will take a look, but I can not say I can fix it.
Q: Battery life? A: It is due to your habit, just like driving a car, a Toyota Prius can use 10L gas if driven by somebody like Michael Schumacher. As my test, due to my habit with non tc version, it is better than stock.
Q: Do I need STweaks to run the kernel? A: The kernel can run without it, but with it you can have more options.
Q: STweaks shows "unextected error"? A: This situation usually happens at the first time STweaks starts, it is OK. Just go on using STweaks.
Q: STweaks FCs. A: Well this sometimes is due to the kernel, sometimes. Here is something you can do: Wipe the STweaks' data, remove /data/.maxfour and /data/.adamax, check the superuser software and give STweaks root access. And yes you need root access. At last, use normal version.
Q: Auto root? A: Use the CWM zip package. And I would take it out soon. Sometimes it breaks root.
Q: Not actually auto-root with v13? A: Yes, v13 will put a wizard like app which will lead you download SuperSU, only when your rom is not rooted.
Q: Conservative governor stock at certain frequency? A: Don't use it, only ondemand governor is optimized for 5410 with big.little cores.
Q: Can you add something? You must do something? Please do something? A: I take advice, but not demand. The reason is simple: I make this kernel due to my interests, not purchase orders. I am not funded for doing this. If the advice is good, I'd take it. If it is just a personal preference, I have to consider it.
Q: Got very low volume of sound? A: Use stweaks, I9500 has wolfson sound control.
Q: Video color is not correct, got blur faces. A: v13 should have this issue fixed.
Q: No internal storage access permission. A: I will make a workaroung later. For now, remount it with rw option through adb.
Q: Random reboot. A: Well, it exists, I admit. I don't know why. I will look for the reason.
Q: After flashing, the phone won't boot. A: Well, I can't guarantee that this kernel works everywhere. And please check if you are using the correct version.
Q: When is your next release? A: I don't know either.
Q: I flashed, it doesn't work. A: Well, it does not work. I don't know why cause it just don't work. I only answer information-rich questions. Questions like this is only a waster of your keyboard, your time and your data traffic. Please at least tell me which version and what rom you are using.
Q: Anything asked above. A: I will keep silence. Other people may insult for this.
Q: Why don't you answer/respond our questions? A: I am a employee, husband, father and son of someone other than XDA and you.

maxfu said:
The first time I make AdaMax is for the Chinese Galaxy S4 Duos GT-I9502. I ported Adam kernel and added more tweaks from other kernels like Persus, halaszk (5420). After several releases, I decidec to spread this kernel to more models. So I built the v8 for both Chinese and international GT-I9500. This thread it for hosting it.
Thanks to a lot of people, I will add their names here...
As my habit, I always put the download link first:
https://github.com/maxfu/android_kernel_samsung_galaxy_s4/releases/tag/9500v8
The uploading is still on going...
Features:
Based on OSRC GT-I9500 JB Opensource Update4 source tree.
Contains most features from Adam kernel, so this kernel is called Adam + Max.
Kernel + Recovery release at one time, recovery based on TWRP with EFS_GSM (for Chinese Duos devices) support.
Compiled with GCC 4.8 toolchain from Google NDK r9c.
Packed in LZMA format, smaller images.
Native exfat supportbased on OSRC exfat source code.
UCI script for STweaks and may be others.
Unlocked some hidden CPU frequency: 2.0GHz, 1.9GHz, 1.8GHz, 1.7GHz, 800MHz, 700MHz for big cores; 1.3GHz, 1.2GHz, 400MHz,
300MHz, 200MHz for little cores.
Frequencies over stock are implemented in overclock (tc/turbocharged) version.
Added more STweaks settings from Adam kernel, including CPU power management, Tools, CPU settings, CPU governor.
Logger module is compiled as standanlone module, so user can disable it completely to save powew.
Overclock (tc/turbocharged) version contains Persus dvfs for GPU with 700MHz overclock, thanks to AndreaLux.
Disabled a lot of rarely used devices support.
Built-in Seeder.
Built-in busybox with auto-installation.
Optimize on ram.
Added several I/O Schedulers including ZEN and ROW.
Built-in dynamic eMMC read ahead
Compiled with compile flag for Cortex-A15 and NEON
Disable KNOX and SELinux when booting
init.d support.
A lot of changes and fixes.
Click to expand...
Click to collapse
Most features of Adam & Perseus Kernel. Does this include the Wolfson Audio Control?

Paolonicus said:
Most features of Adam & Perseus Kernel. Does this include the Wolfson Audio Control?
Click to expand...
Click to collapse
I kept the feature, so it should show up in STweaks on I9500. I am using 9502 which does not have the feature so I can not test it. When I compile for 9500, sound control is enabled.

@maxfu Is this kernel for the 4.3 or 4.4.2?

a2441918 said:
@maxfu Is this kernel for the 4.3 or 4.4.2?
Click to expand...
Click to collapse
Sorry I did not directly mention. It is for 4.3 JellyBean.

maxfu said:
Sorry I did not directly mention. It is for 4.3 JellyBean.
Click to expand...
Click to collapse
Can you please mention it in the op please it's very confusing.
Thanks.
Sent from my GT-I9500 using Tapatalk

Will there be version for Kitkat?
This is something that prevents me from flashing the newer version of Android.

Paolonicus said:
This is something that prevents me from flashing the newer version of Android.
Click to expand...
Click to collapse
If Samsung releases the source code for 4.4, I will.

Paolonicus said:
This is something that prevents me from flashing the newer version of Android.
Click to expand...
Click to collapse
I have a good news for you. I found I9500XXUFNB1: GT-I9500_KK_Opensource.zip, so I will push it up in several days.

How about battery life and performance compared to stock kernel?
Sent from my GT-I9500 using XDA Premium 4 mobile app

snxxxxx said:
How about battery life and performance compared to stock kernel?
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well it is hard to say. If you use the normal version, it should be battery friendly. The tc version is overclocked. Due to my 3DMark result, the overclock version maxied out the First and Second stage tests.

maxfu said:
Well it is hard to say. If you use the normal version, it should be battery friendly. The tc version is overclocked. Due to my 3DMark result, the overclock version maxied out the First and Second stage tests.
Click to expand...
Click to collapse
If you can Make it AOSP support also

Thanks maxfu for the contribution...will try soon. You didn't mention about the screen color option from perseus kernel. Is it there?

Yesss at last some hope for 4.4 custom kernel!! Thank you Maxfu for continuing Wanam's legacy.

Wow!
maxfu said:
I have a good news for you. I found I9500XXUFNB1: GT-I9500_KK_Opensource.zip, so I will push it up in several days.
Click to expand...
Click to collapse
Sweet! Can't wait to try you kernel! Thanks a bunch!

For AOSP, I will try.
Sent from my GT-I9502 using xda app-developers app

great to see another addition to kennels for gt -9500. please also add support fir miui.
Sent from my GT-I9500 using Tapatalk

Some Proposals
1. Auto Install Stweaks
2. Clearly describe CPU Options which one for big cores and which for little cores
3. Don't lock GPU Frequency at 532MHz as i see by default ... maybe more relaxed 177-532 settings?
4. SELinux is set to Permissive by default ... maybe set as Disabled?
and maybe some very useful Insecure version please?
ro.secure=0
ro.adb.secure=0
(computer translation)

Hi, I already flashed Adam Kernel on my S4. Can I simply flash this Kernel on recovery or do I need to do something else?

Dnssuffix said:
Thanks maxfu for the contribution...will try soon. You didn't mention about the screen color option from perseus kernel. Is it there?
Click to expand...
Click to collapse
If it is in Adam kernel, then it is here. There is a screen tab in STweaks.

[KERNEL] TonoKrnl for Nexus 7 (2013)

EDIT: I want to remind everyone DO NOT FILE AN UBUNTU BUG REPORT WITH THIS KERNEL INSTALLED, ALWAYS REVERT BACK TO THE STOCK KERNEL IF YOU HAVE AN ISSUE BEFORE FILING
This is my first actual Kernel project, so please be gentle.
This kernel is ONLY for the Nexus 7 (2013) flo. I do not know if it boots on the deb, theoretically it should as I don't have any flo specific options and there are config options for Deb in the Kernel configuration. It should work for those on stable, rc or rc-proposed and may possibly work on devel (not sure) as long as devel has not released a new kernel package (3.4.0-5-flo+)
I have cherry-picked some battery optimizations from bricked-flo, elementalx-flo (4.4 branch) and some additional commits elsewhere in an attempt to not only improve battery-life but also to bring some Android features (DoubleTap2Wake) to Ubuntu Touch.
Currently it has the following:
- ROW I/O scheduler
- Beginnings of OCing (pulled from ElementalX, I think I'm missing some commits to make this relevant though)
- ElementalX's kernel thermal control
- binfmt_misc support
- CD/DVD Filesystem Support for external optical drives (ISO9660/UDF)
- Some Slimbus enhancements
- Battery life optimizations (changing default MHz, etc.)
- Default CPU governor changed from Performance to Interactive (yes, they had it set to Performance, not sure why.)
- Direct Rendering Interface/Direct Rendering Manager (XFree86 + msm_kgsl_drm)
- and more!
You can check my github for the items cherrypicked into it and there is even a current release which has seen my battery drop 4% in the last 30 minutes with the screen fully on (no autolock), WiFi on and Bluetooth.
The name of the kernel is still up for change, TonoKrnl is not going to be it's final name unless everyone likes it.
Repository is at: http://github.com/ShadowEO/TonoKrnl
Releases can be found: https://github.com/ShadowEO/TonoKrnl/releases
Status of Github Repo: It builds. It boots and it runs. I am trying my hardest not to push changes that break building.

Reserved for future use. Currently the status of the kernel's updates can be found on the issue tracker: https://github.com/ShadowEO/TonoKrnl/issues/5
Be patient, if you don't see new releases right away, it's because I'm still in the process of generating them, check back later.
-- Release 1.0.3-UBports (11/19/2017): A lot was done to bring this kernel back into usable state, see below:
Added OTG Charging
Added initscripts for turning on features (Requires the rootfs to be mounted read/write for manual installation, see my latest post #16 I think...)
Created patches to be applied against a clean UBports kernel tree for certain features (right now, only DT2W and USB Charging)
(USB Host Charging was pulled from flar2's ElementalX source code, it is not turned on by default and can be turned on with
Code:
echo 1 > /sys/module/msm_otg/parameters/usbhost_charge_mode
Feature is tested and does work.
Developers:
1.0.3 brought the kernel tree back into a buildable state and also cleaned up some problems with the previous releases. I am in the process of generating a kernel patchset which will be able to be applied to a clean kernel to bring those features to the stock UBports kernel source. After I complete generating the kernel patchset, I will be rebasing the entire kernel project onto a clean tree (As I am absolutely certain that I have problems like unfinished cherry-picks [missing commits] etc.). Be patient regarding these patches, as I am re-adding the features I pulled in originally by hand rather than cherry-picking them as I appear to have fuxxed up somewhere cherry-picking previously.
If you have any random reboots, try:
Code:
echo 1 >/sys/module/msm_watchdog/parameters/runtime_disable
If you still receive random reboots afterwards or if you received them previously but the above command fixes them, please open an issue on my project tracker with a copy of /proc/last_kmsg attached.
Kernel TODO:
Generate kernel patchset and then rebase onto clean kernel tree
Finish Kernel Feature Documentation and publish (these docs will give information on tweaking the changes to the kernel, such as readahead buffer, turning on/off DT2W, turning on/off usbhost charging, etc.)
Move TonoKrnl initscripts into ramdisk, should make them more robust and reliable.
Create ZIP installer for TWRP recoveries (this is needed for automatic installation of kernel modules, since /lib/modules is a read-only, bound mountpoint for the Android LXC container. To fix this, we just have to move /lib/modules out of the Android container.

Allow me two questions:
Which kernel repository is this branched off? Apologies if that is dumb question, my git and kernel knowledge is cursory at best, but I can't seem to figure this out looking through your github repo.
ShadowEO said:
- Direct Rendering Interface/Direct Rendering Manager (XFree86 + msm_kgsl_drm)
Click to expand...
Click to collapse
What's the intention behind this? Does this have anything to do with enabling the freedreno driver for the GPU and would that pave a way to a setup without Mir, but with wayland or X?

doniks said:
Allow me two questions:
Which kernel repository is this branched off? Apologies if that is dumb question, my git and kernel knowledge is cursory at best, but I can't seem to figure this out looking through your github repo.
What's the intention behind this? Does this have anything to do with enabling the freedreno driver for the GPU and would that pave a way to a setup without Mir, but with wayland or X?
Click to expand...
Click to collapse
This started off with the debian source package for linux-image-flo in the Ubuntu archives which is the kernel for our device. The reason you are having trouble with figuring it out is because I started with the base (Ubuntu's 3.4.0-5-flo+), pulled it into an empty git repo and then started cherry-picking features. It was originally going to be for my own personal consumption as I didn't know how well a custom kernel would be received by the touch community (so far, in all the communities I've posted it, you were the only one to ask any questions ), but since I already had a git repo up, figured that I may as well share it. So here I am, an amateur working on the Linux kernel, and learning a lot.
My full intent was to improve the experience (even marginally) on Ubuntu Touch for the Nexus 7 2013, I wanted to bring the mobile kernel features previously found on the desktop that myself or others may find useful (hence binfmt support for qemu-user), there really is no reason for me to turn on DRI/DRM except to allow playing with Wayland and X, yes, that part is correct, and I have tested the freedreno driver with it (Freedreno does get the KGSL DRI device and does start X)
In addition I found some interesting choices in the kernel in terms of battery life, it would seem that the CPU governor used by the default Ubuntu Kernel is Performance, which would explain why the battery dies so fast, I tried to pull in some battery optimizations from a couple other kernels around the Android scene for the device. So far I'm pleased with the results, and recently found that both the original cherry-picking done for DT2W worked along with the code to add fast charging.
I've had to put the project on hold due to work issues, but once I'm able to work on it again, I'm reverting the last 100 changes pulled in that broke my tree and going from there since my original targets in terms of features actually worked. (I'm pretty sure it was some recent changes to the CPU hotplug driver that killed it, I can no longer compile the kernel without mpdecision on, so that's my likely suspect.)

Thanks for your explanations!
ShadowEO said:
This started off with the debian source package for linux-image-flo in the Ubuntu archives which is the kernel for our device.
Click to expand...
Click to collapse
So something like apt source linux-image-flo? And then to build you use the instructions in the package also?
there really is no reason for me to turn on DRI/DRM except to allow playing with Wayland and X, yes, that part is correct, and I have tested the freedreno driver with it (Freedreno does get the KGSL DRI device and does start X)
Click to expand...
Click to collapse
Exciting!
In addition I found some interesting choices in the kernel in terms of battery life, it would seem that the CPU governor used by the default Ubuntu Kernel is Performance, which would explain why the battery dies so fast
Click to expand...
Click to collapse
I'm really only speculating, but my conjecture to previous mentions of odd govenor choices in android kernels was that the actual android power management magic is happening behind the backs of the governors. But, I'm really just babbling. I don't know much of anything about this. You seem to be getting impressive improvements!
I'm reverting the last 100 changes pulled in that broke my tree and going from there since my original targets in terms of features actually worked.
Click to expand...
Click to collapse
So, that means: "If you want to try it now, don't use v1.0.2, but use v1.0.2-alpha for now." Is that about correct?

doniks said:
Thanks for your explanations!
So something like apt source linux-image-flo? And then to build you use the instructions in the package also?
there really is no reason for me to turn on DRI/DRM except to allow playing with Wayland and X, yes, that part is correct, and I have tested the freedreno driver with it (Freedreno does get the KGSL DRI device and does start X) Exciting!
In addition I found some interesting choices in the kernel in terms of battery life, it would seem that the CPU governor used by the default Ubuntu Kernel is Performance, which would explain why the battery dies so fast
I'm really only speculating, but my conjecture to previous mentions of odd govenor choices in android kernels was that the actual android power management magic is happening behind the backs of the governors. But, I'm really just babbling. I don't know much of anything about this. You seem to be getting impressive improvements!
I'm reverting the last 100 changes pulled in that broke my tree and going from there since my original targets in terms of features actually worked. So, that means: "If you want to try it now, don't use v1.0.2, but use v1.0.2-alpha for now." Is that about correct?
Click to expand...
Click to collapse
I removed the problem download, the only ones available are the source tree downloads and the last known good build I had, I have also tested to ensure that the last build up there works as well as it's the one I'm running on my device until I have time to go through the tree again.
As for building, essentially yes, but you have to build the image separately. Due to how Ubuntu currently has the filesystem set up and with Android's boot images, its not feasible to really package it in a traditional sense. Essentially what I did was create a chroot, apt-get source linux-image-flo and then to get a working defconfig I used the config.* files found in Debian.flo and Debian.master, from there was the tree that I used as my base.
Then run make with the following to customize:
Code:
ARCH=arm make menuconfig
ARCH=arm make -j <number of processors>
To build the image, you'll need to grab the boot image from your device and tear it apart using a abootimg them rebuild it with the Ubuntu ramdisk. If you are using MultiROM, you can just drop it in the folder for your ROM.
Edit: As for the weird choice of governors, I noticed during my investigations (via the cpufreq-info package) that while Android is managing the CPUs that are online (I found it's running it's own version of mpdecision behind the scenes inside the LXC container), it's not doing anything to the CPU governor. That's all managed in the kernel right now through CPUFreq it appears and in the stock kernel it's set to performance, as for the reason for it, I'm not sure myself.. The other governors ARE there though, just unused right now.

ShadowEO said:
This kernel is ONLY for the Nexus 7 (2013) flo. I do not know if it boots on the deb, theoretically it should as I don't have any flo specific options and there are config options for Deb in the Kernel configuration.
Click to expand...
Click to collapse
Jup, it does boot on my deb! I've downloaded the .img, put the tablet in bootloader mode and did
fastboot boot TonoKrnl-1.0.2-flo.img
It booted without problems, and so far it's running for about half an hour or so without any problems. Wifi, sound, video, usb mouse, all work fine.

doniks said:
Jup, it does boot on my deb! I've downloaded the .img, put the tablet in bootloader mode and did
fastboot boot TonoKrnl-1.0.2-flo.img
It booted without problems, and so far it's running for about half an hour or so without any problems. Wifi, sound, video, usb mouse, all work fine.
Click to expand...
Click to collapse
Wow, that's great to hear, I wasn't sure but I was definitely curious since I had seen options for both Deb and Flo in the makeconfig page.
If you can script it in (or edit sysfs.conf) to have it write a 1 to /sys/android_touch/doubletap2wake while it's booting, you can have working DT2W and there's quite some others to mess around with under /sys :3 CPU governors are somewhere there too, just don't have it offhand.
Since you are testing it out, have you noticed any changes in the device's normal battery life? The stock kernel seems to drain 1% every 1 1/2 minutes on my Flo, not doubting that the power optimizations ARE working (I know I'm getting much better life), I'm just wanting to ensure that it's not a placebo effect that I'm experiencing.

ShadowEO said:
If you can script it in (or edit sysfs.conf) to have it write a 1 to /sys/android_touch/doubletap2wake while it's booting, you can have working DT2W
Click to expand...
Click to collapse
After
Code:
echo 1 | sudo tee /sys/android_touch/doubletap2wake
I can indeed (sometimes) wake it with double tapping. I have since quite a while (with the standard kernel) the situation that its really hard to wake up. I have to press the powerbutton many many times. Feels like it is sleeping really deeply.
Since you are testing it out, have you noticed any changes in the device's normal battery life? The stock kernel seems to drain 1% every 1 1/2 minutes on my Flo, not doubting that the power optimizations ARE working (I know I'm getting much better life), I'm just wanting to ensure that it's not a placebo effect that I'm experiencing.
Click to expand...
Click to collapse
Well, I haven't noticed anything. I might just not be in the best position to judge. I rarely have it unplugged for more than a couple of hours at a time and I don't generally monitor the battery status closely. That being said though, I have very definitely never experienced anything remotely close to 1% per 1.5 min!
If you have a particular test/measurement you'd like to see - let me know.

doniks said:
After
Code:
echo 1 | sudo tee /sys/android_touch/doubletap2wake
I can indeed (sometimes) wake it with double tapping. I have since quite a while (with the standard kernel) the situation that its really hard to wake up. I have to press the powerbutton many many times. Feels like it is sleeping really deeply.
Well, I haven't noticed anything. I might just not be in the best position to judge. I rarely have it unplugged for more than a couple of hours at a time and I don't generally monitor the battery status closely. That being said though, I have very definitely never experienced anything remotely close to 1% per 1.5 min!
If you have a particular test/measurement you'd like to see - let me know.
Click to expand...
Click to collapse
I may be exaggerating slightly, but normally my tablet goes from 100% to 95% in about 5 minutes while I'm using it after taking it off the charger (in Ubuntu only, may be an rc-proposed thing too). I haven't seen that behavior since changing kernels. I'm gonna see if I can go ahead and start reverting commits today or possibly reset back to the last known good commit.
As for the screen problems, I think there is a bug in the current doubletap2wake driver, if you look at dmesg after using DT2W for a while, you'll see it being spammed with error messages from the touchscreen driver.
That could possibly be related. Additionally, I think the minimum processor speed defaulted to 384MHz (I didn't touch any processor clock speeds in here) which the Performance governor would never had let the processor hit. So it's likely that the minimum processor speed will need bumped up at least one step there, I get some stuttery behavior on the command line when the screen is off which I hadn't received on the stock kernel.
Edit (07/01/16): I'm not sure what else I can really bring to the table here, mpdecision running in the android LXC container defeats any meaningful changes to the clock speed. I also noticed mention that you shouldn't have two hotplugging daemons running at the same time, effectively that is what the new developments would've brought in. I think my best option to continue this would be to wait until the Xenial transition and see if they make any changes for me to update on.
I'm also quite a novice, so besides cherry picking commits, I'm not sure what else I can do.

ShadowEO, is bluetooth working on your device? With your kernel or with the one from Canonical?
I can't seem to get anything at all to show up on my deb.

I am so embarrassed that I didn't check this thread in so long. Ya, Bluetooth still works on my device with either kernel. Sometimes it doesn't seem to like to power on, so if you are having trouble, try this.
Open Terminal,
do sudo bluetoothctl and see if Nexus 7 (2013) shows up in there. If it does, type power on and hit enter. You should see the bluetooth indicator show up in the status bar. If it doesn't, exit bluetoothctl and do these from a root prompt:
start bluetooth-touch
start bluetooth-touch-flo
Sometimes the commands may take a little bit of time (no idea why honestly), but after those, you should see bluetooth start. At that point, if you still don't, fully power the device down and try again.
For whatever reason, the bluetooth scripts fail every so often, haven't been able to look into it much due to personal things IRL taking up all my time the last few months.

It's been a long while since I touched this project, but I have finally cleaned up the kernel source tree and ensured that it builds properly!
Two features that must remain disabled however are GOVERNOR_ELEMENTALX and MSM_SLEEPER as they are currently broken and do not function as of right now. The defconfig for flo also has sane defaults for the UBports Ubuntu Touch distribution (installable via the UBports installer application) and has DT2W enabled (but not turned on, that requires some extra work) by default.
You should also no longer need to disable the MSM watchdog using the instructions in the OP, running the kernel now and haven't experienced near as many random reboots I used to with the previous version! (I wonder if that was a UTouch problem, because I DO get random reboots sometimes using certain apps, but they're very rare... Then again, I'm not sure if UBports made any initramfs changes for the Flo when they added it to their system-image server, which they may have, since it's in the ubports-touch/15.04 distribution instead of their ubuntu-touch mirror for older, no-longer supported devices)
To turn on DT2W, you must follow the instructions on the github page for the 1.0.2 release.
NOTE: I highly recommend building the kernel from source rather than downloading a release! I have yet to add the current stable release to the github releases page! I also have a zip file with some helper scripts and configuration that can be installed into the UBports rootfs to turn DT2W and Kernel Samepage Merging on at startup. In case that's useful, I'm adding the zip to this post. To install, simply remount your root as read/write, extract the ZIP to / and then "chmod +x /sbin/tonokrnl-init" and reboot. Upon reaching the lightdm greeter, you should be able to shut the screen off, then double tap it to wake.
The files contained in the zip are:
/sbin/tonokrnl-init - Helper Script to start DT2W and KSM
/etc/sudoers/tonokrnl - Allows the user-session upstart config to run the helper script, which requires root.
/home/phablet/.config/upstart/tonokrnl.conf - Upstart configuration to run /sbin/tonokrnl-init using sudo (requires the sudoers file)
Off-topic slightly: The reason this project got set aside, was due to my IRL work, and because I had stopped using Ubuntu Touch and was testing out other ways of getting Linux onto the N7 'flo'. I messed with the Sailfish distribution found in the Nexus 7 2013 forum, then went to postmarketOS and messed with that (it's cool, but rather bare, not enough desktop packages to make it useful [no osk, etc]), then attempted to boot a debian distribution with the Linaro mainline kernel from John Stultz (couldn't even get X11 to start, the system did boot though! Perhaps mesa/libdrm needed recompiling with freedreno support...) and then finally came back to Ubuntu Touch via UBports!
Back on Topic, if you decide to use this kernel (either by building it yourself, or using the new UBports-1.0.3 release that will go up soon!) and install the attached helper scripts (or even find your own solution to on-boot DT2W, KSM, and the Interactive governor) please let me know your experiences! I noticed after turning KSM on that the web browser didn't crash as much, but I'm not sure if it's a placebo effect or not.
(I wonder if @flar2 has a 3.4.0 patchset I can apply rather than attempting to cherry-pick ElementalX into the kernel... That would be amazing to have ElementalX's additions to the kernel under Ubuntu Touch. [Please don't be angry I used a mention flar, I just wanted to ask if you had a patchset for the flo's kernel [version 3.4.0])

[KERNEL] [EOL] [OnePlus3T] [OOS 5, 4, 3] Boeffla-Kernel (16-01-2019)

*** This kernel is now end-of-life, not supported and developed anymore !!! ***
Hi all,
some of you know me from the other OnePlus or Samsung devices areas, where I provide my kernels already for more than three years to OnePlus 3, 2, one and X, Galaxy S5, S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.)
Please note:
I am not heading to have as many features as possible implemented, this is not my design goal. If you are more into that, move on to other, good existing kernels. If you are searching for a good mix of improvements and new functions while not sacrificing stability, you are welcome here (see below the history section for more info).
Compatibility
Important: This kernel is only meant to be compatible with official OnePlus OOS and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
To add: An open beta (aka community build) is NOT an official build supported here. If you use a community build and have issues, don't complain or even report. I am not merging any kernel changes from open betas into my kernels !!
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
This kernel is ONLY compatible to OxygenOs stock, nothing else !!!
If you are using a custom rom that bases on OxygenOs, it might work. However, if it does not work, do not expect me to do tweak to make the kernel running with your favorite rom. I would not do it - my one and only reference is OxygenOs stock.
It is not supposed to be compatible to CM, HydrogenOS etc.
Also note: You have to use Boeffla-Config app which I provide on my homepage to tweak the kernel. 3rd party apps will not be able to unleash the full power of the kernel.
Installation
Read the install instructions in the support section on the Boeffla Site.
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (outdated at the moment).
Click here to learn about using the config app (outdated at the moment).
I will refuse to give support if you do any undervolting/overclocking and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
I will refuse to give support if you have xposed framework installed and reporting any kind of weird issues. My opinion to xposed it quite clear: too powerful for >90% of the users that just mess up their system with it.
Otherwise, you can get in touch with me via the support e-mail address: [email protected]
Please provide kernel version, rom version, a detailed issue description and ideally supporting screenshots or log files.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for OxygenOS 4.x.x kernel - Click here
Change log for OxygenOS 3.x.x kernel - Click here
Known issues
none
Features
Note: This kernel only runs on OOS 3.x.x for the OnePlus 3T - nothing else !!!
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 (you need at least version 2.4.21 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Dash charging fully supported
The two CPU clusters (big and little cpu) can be configured completely separate in terms of min/max frequencies, governors and CPU core profiles
Additional governors: Impulse, zzmoove, elementalx, conservative, ondemand, blu_active
Additional schedulers: fiops, bfq, sio, sioplus, fifo, vr, tripndroid, zen, maple
No CPU overclocking and voltage interface, no GPU overclocking and voltage interface
USB charge rate bumped up to 900 mA
Boeffla charge analysis (display of charger type and charge current in Boeffla-Config app in real time)
Boeffla touchkey LED control (LEDs fully off, LED on screen touch, configurable duration)
CPU core profiles to restrict number of CPU cores being used (the OP3 does not hotplug based on load)
Notification LED control (effect + speed for blinking/fading, brightness for continuous notification like battery charging etc.)
Boeffla-Sound engine: Headphone volume and speaker volume (only lowering volumes for speaker)
Dynamic FSync (activated if screen on, deactived if screen off), configurable
Input boost frequencies and duration configurable per CPU cluster, input boost switch
Show CPU frequency usage per CPU and frequency in Boeffla-Config
Show GPU frequency usage per frequency in Boeffla-Config
KCal V2 Color control
Display backlight limits configurable (to avoid display brightness gets too low in some situations)
Display backlight dimmer
Swipe2wake gestures
Control haptic feedback of gestures (except fingerprint)
Haptic feedback intensity control
Swipe2sleep gestures
Boeffla generic wakelock blocker V1.1.0 (documentation)
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (only when data volume is formated with ext4, stock default is f2fs)
Kernel logger (dmesg) configurable
CIFS support (module, do not mount inside /data, if you rooted with Chainfire SuperSu, make sure you uncheck the namespace separation in SuperSu app)
NFS support (module)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Many additional TCP congestion algorithms available
Entropy values configurable
Hardware touch keys are locked as long as screen is in use (touched) for better usability
Swap supported
Doze mode switchable
Verifiedbootstage flag remove to avoid triggering safetynet
Various minor kernel tweaks
Doze mode configurable in Boeffla-Config
Full selinux strict support (switchable to permissive on demand)
Show speedbin information (PVS level) in Boeffla-Config app
init.d support (in /system/etc/init.d - set correct permissions!)
Entropies configurable
Automatic EFS backup
Integrated full busybox 1.27.2 (own compilation)
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Security patches included, which are not in the official repo
Google gcc 4.9 toolchain (64 bit) used for best stability
Always based on latest OOS kernel sources (https://github.com/OnePlusOSS/androi...neplus_msm8996)
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History and design targets
Basically I created my first Boeffla-Kernel in 2012 as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. Also it does not aim to have the broadest feature set available everywhere.
It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!!
These design targets are also valid for the OnePlus kernel here!!!
This said, I will definitely NEVER implement:
things I do personally not need
things I do not like
things that are in any way dangerous
anything which is highly experimental
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it if it falls into the listed categories. Everything else I am happy to check and decide.
And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.
I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...
Compatibility
To reiterate it again: Flash the kernel only if you are running a compatible rom !!!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from the downloads section on www.boeffla.de.
You need at least version 2.4.21 or higher for the OnePlus 3T Boeffla Kernels.
Donation
If you like my work, feel free to donate: Donation-Link
If you donate at least 2,49 EUR (to be in line with the donation app prices on Google Play store), you will receive a personal donation code which unlocks some nice little comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* ZaneZam
* Grarak
* Yank555
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Mialwe
* Entropy512
* Faux
* Harunjo
* FranciscoFranco
* Ak
* Osm0sis
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in your custom recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi

Latest change log:
OOS4
http://kernel.boeffla.de/oneplus3t/boeffla-kernel-oos/oos4xx/changelog.htm
OOS3
http://kernel.boeffla.de/oneplus3t/boeffla-kernel-oos/oos3xx/changelog.htm

--- Reserved 2 ---

Here we go!
First beta is online for you guys.
As always, find everything on www.boeffla.de
And just to stress it again: It is the VERY FIRST beta, so expect bugs!
Have fund
Andi

nice! downloading right now!
so happy to see you again andi! your kernel was simply the best on my galaxy S5 and I missed your affords in my S7!
so happy flashing to everyone!
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

After jumping from kernel to kernel (since there are many more kernel devs here than on the OP2) with various minor niggles, finally back to the one I feel fits my needs best. This release brings me relief, as now I don't have to go kernel hopping again, and I think Boeffla provides the best support of all. No bugs so far, multirom boot menu works, everything runs great.
Out of curiosity, is the kernel systemless? (Can I revert to stock by just flashing stock boot.img from latest ROM zip?) I ask because flashing the entire stock ROM takes a long time, and the TWRP loading time is also long.
Also, ext4 tweaks is not hidden for me and is enabled when a profile is reset to default settings. I'm on the default filesystems. (f2fs data, ext4 everything else)
Should I leave ext4 tweaks on or off?
PS: I was probably the first person to like and subscribe to this thread. (within 5 minutes of thread creation)
Edit: Flashable stock kernels? Perfect, thank you @Lord Boeffla ! Does it revert any custom kernel to stock kernel?

Been with Boeffla since S3 and via OPO this will be my third phone with the kernel.
Thanks!
Skickat från min ONEPLUS A3003 via Tapatalk

knpk13 said:
After jumping from kernel to kernel (since there are many more kernel devs here than on the OP2) with various minor niggles, finally back to the one I feel fits my needs best. This release brings me relief, as now I don't have to go kernel hopping again. No bugs so far, multirom boot menu works, everything runs great.
Out of curiosity, is the kernel systemless? (Can I revert to stock by just flashing stock boot.img from latest ROM zip?) I ask because flashing the entire stock ROM takes a long time, and the TWRP loading time is also long.
Click to expand...
Click to collapse
This is not possible on OOS in a clean way.
The kernel comes with modules which are placed in /system/lib/modules too.
So only flashing stock boot.img would not replace the kernel modules by stock ones. So it is only a "half-good" solution.
But, as most of the time, I have a solution for you
Look here: http://boeffla.de/index.php/downloads/downloads-general
Flashable stock kernels for the 3T, which also include the modules.
Guess this is what you need.
Andi

knpk13 said:
Also, ext4 tweaks is not hidden for me and is enabled when a profile is reset to default settings. I'm on the default filesystems. (f2fs data, ext4 everything else)
Should I leave ext4 tweaks on or off?
Click to expand...
Click to collapse
This is something I might need to correct in the app then. Leave them off, there is no ext4 anymore on /data volue with stock OOS (but the f**inkg f2fs).
I will look into that over the next days then.
EDIT: Just tried it - cannot replicate that. Maybe your /data partition is indeed formatted in ext4???
(you can check by firing the following command in a terminal: mount | grep data)
Andi

Lord Boeffla said:
This is something I might need to correct in the app then. Leave them off, there is no ext4 anymore on /data volue with stock OOS (but the f**inkg f2fs).
I will look into that over the next days then.
Andi
Click to expand...
Click to collapse
I reopened the app, and ext4 tweaks was off. But when I click on reset profile settings, it turns on. But on reopening again, it turns off automatically every time, so I guess it's working fine. Yes I'm sure I'm on f2fs.

knpk13 said:
I reopened the app, and ext4 tweaks was off. But when I click on reset profile settings, it turns on. But on reopening again, it turns off, so I guess it's working fine.
Click to expand...
Click to collapse
Yep, and also means, your data partition is not formatted with f2fs (my op3t came with /data on f2fs)... lucky you. I love ext4 much more, I even consider reformatting /data with ext4 soon, hehe.
Andi

Ok guys, evening hours here in Germany.
I am off for today. If you have any questions, you can also move over and read in the OP3 thread. The devices are - concerning my kernel - 99,99% the same.
So you would most probably find all answers to your questions already there.
Tomorrow I will catch up again.
Andi

Lord Boeffla said:
Yep, and also means, your data partition is not formatted with f2fs (my op3t came with /data on f2fs)... lucky you. I live ext4 much more, I even consider reformatting /data with ext4 soon, hehe.
Andi
Click to expand...
Click to collapse
I'm sure I'm on f2fs. Even TWRP says I'm on f2fs. 3T comes stock with f2fs. This is the output of mount | grep data, but since I'm using magisk I think the output has many partitions and I can't make sense of it.
I think the ext4 tweaks toggle is working fine since it reverts to off automatically when the app is restarted. Thanks!
Here is the output: https://hastebin.com/iwokiramek.hs

Welcome to the 3t Lord Boeffla.. Enjoyed having your kernels and support on the s5 when I was running that phone.. Look forward to the same here..
Sent from my ONEPLUS A3000 using Tapatalk

Lord Boeffla said:
But, as most of the time, I have a solution for you
Look here: http://boeffla.de/index.php/downloads/downloads-general
Flashable stock kernels for the 3T, which also include the modules.
Guess this is what you need.
Andi
Click to expand...
Click to collapse
nice, been waiting for this since day one. :good:

So it is not oos 4.0.0 compatible
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

inzaghi75 said:
So it is not oos 4.0.0 compatible
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
No. OOS 4 has not yet been officially released and no kernel source has been released.

christmas is here since andi is our santa.
welcome to the 3T world.
loyalists like me have been waiting for you perhaps since the device was launched.
glad OnePlus and XDA did such an awesome thing to distribute devices to devs.
been following your work for a while now.
your kernel turned my OpO into a beast.
just flashed onto my 3T.
will report issues as and when(and if) I can find them.
cheers

Glad to see you here Andy!
finally you will develope on 3T:good:

Glad to see you here Andi:victory:
I use your kernel since Galaxy S3, also flashed it on my opo and my wife's opt.
:good: Now the kernel it's running very well on my new op3t.