{
"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"
}
This is the home of KingKernel development for sailfish/marlin
Created by: @kingbri and @Sweetie
Our philosophy: The idea is to create a kernel that is packed with features, but doesn't compromise stability or battery life.
This kernel is compiled with the latest, bleeding edge Clang 9.x
Features:
- Based on EAS v3.5
- Has 4.4 ports from mm, RCU, zram, etc...
- Cpufreq: chill, updated schedutil, blu_schedutil, bioshock, conservativex to name a few
- Adrenoboost and @Sultanxda's cpu_input_boost driver ported to 3.18
- Dynamic SchedTune boost
- Spectrum Support
- Franco performance profiles for P
- Switches to noop I/o when screen is locked
- CFQ default, maple I/o sched included
- exFAT fs support
- f2fs support
- OC gpu to 710 Mhz
- TCP westwood: default
- High brightness mode and Backlight dimmer included
- Vibration control
- Boeffla WL blocker with wakelocks blocked
- Audio High perf mode enabled by default
- Sound control
- And so.... so much more
Update Schedule:
Always upstreamed to latest sources
Always updated to latest patches
Will notify about updates in changelog
How to flash:
Non-root:
Flash as normal in TWRP
KingKernel features what I call "boot tweaks" that activate themselves on every boot and change some values. These are composed of the small stuff such as setting default gov values and miscellaneous tweaks.
Root (Use any autoflasher, I reccomend FrancoKernel manager since it can flash anything):
[*]Make sure you're rooted first
[*]Either flash through TWRP or your favorite autoflasher (FKM)
[*]Reboot and you should be good!
My policy on flaming/rude commentary:
Flaming - posting of a provocative or offensive message to provoke an angry response:
I WILL NOT condone these posts in any way, shape, or form. If you are flaming me or anyone else, you will be reported and private messaged saying that you have been flaming and you need to stop. If you have an issue with the kernel, please reply here for stable and the TG chat for betas
However, Off Topic comments are encouraged!
KingKernel beta builds- I know that you have heard of beta builds before, so here are the instructions to download and reach me for reporting bugs
[*]Downloads located here: [url]https://github.com/King-Kernel/beta-builds[/URL]
[*]MAKE SURE TO READ THE README inside the GitHub page
[*]I will not answer bugs in this thread, please reference the telegram group section for me to answer
Mod Edit: Link Removed
Downloads (Stable): [url]https://github.com/King-Kernel/stable-builds[/URL]
Source code: [url]https://github.com/King-Kernel/KingKernel-marlin[/URL]
Current Version v4.2
Linux - 3.18.134
Security - Feb. 2019
Feature changes:
-Changeup some boost values
-Purge blackenedmod
-Add in boot tweaks
-Use pigz for zipping
-Add skip_override
-more stuff...
Since my build environment can change frequently, I'm going to post the current environment here (hardware stays the same):
mid-2012 MBP with 16GB of ram and core i5 processor
Building on a 256GB external SSD running Solus Budgie
Custom rom stuff to remove:
BenzoRom: remove /system/etc/init/benzorom-io.rc (interferes with setting default io sched to cfq on kernel)
PixelDust: its init.rc sets multiple default values that interfere with the kernel settings, however the boot tweaks should counteract these actions pushed by the ROM
Magisk Modules:
None.
My position on kernel modding:
I'm fine if you mod your phone in any way, shape, or form. Based on some testers, people have been saying that the kernel works better by itself without using any mods. The init.rc only sets some defaults and cosmetic values. If you are planning on using a kernel mod, just know that I DON'T support them. I'll try to fix your issue of course, but it's not guaranteed that your issue will be fixed, please contact the mod dev to fix the issue
Pixel and Pixel XL users!
I'll be making a new branch (the really unstable one)
Which will have a lot of new features, also it'll be quite unstable.
We will filter those features slowly in the stable branch.
If you guys need any new feature! Then reply to this or PM me (with commit link or the thread where you saw that) I'll try my best to add that.
Booted and smooth so far on lineage PIE. Elementary OS is a beautiful distribution, I ran it for a minute before switching to deepin.
Also, any info on the bluschedutil governor? I usually run sched or schedutil because of the whole eas thing. But I seen it and haven't been able to search anything. Currently running it
noidea24 said:
Booted and smooth so far on lineage PIE. Elementary OS is a beautiful distribution, I ran it for a minute before switching to deepin.
Also, any info on the bluschedutil governor? I usually run sched or schedutil because of the whole eas thing. But I seen it and haven't been able to search anything. Currently running it
Click to expand...
Click to collapse
It's in the Blu spark kernel for op6 and is just schedutil with multiple mods
[do replies really require a title? I am losing my original thought to reply..]
Downloading and testing. I am still fairly new to android development but not computers in general. I have compiled a kernel.
Would you mind posting your workflow from git to make? Possibly your bash history so I and others can have proper command syntax / reference?
I have a Dell PowerEdge R710 with dual Intel Xeon X5550's + 80+GB memory and a bunch of 300GB 15.3k SAS drives running Debian Jessie.
Its a older server but it took only 40 minutes to build Carbon Rom. I could assist with build from time to time if your laptop fans ever require a break. ;hj
(I also have same model, think it was the first generation Intel built MBP. It can't run anything past Snow Leopard or Lion but it runs Windows 10 really well; as alternative method to syncing a iPhone as new versions of iTunes require macOS that my MBP cannot upgrade to.)
Thank you for your contributions to the internet.
Be well.
@kingbri
What is up with this commit? Why would you have to pick a fix of someone else's bad pick?
github.com/King-Kernel/KingKernel-marlin/commit/6142c211378ffc1d282a35c1d25e41992c500f89
Also, this commit doesn't have any authorship. Is this your 100% original code?
github.com/King-Kernel/KingKernel-marlin/commit/04cb51eb014e86d25c550e82df6f66bcca1c886a
Thanks in advance. I would love to run this kernel after getting a satisfactory response.
fight_the_kang said:
What is up with this commit? Why would you have to pick a fix of someone else's bad pick?
github.com/King-Kernel/KingKernel-marlin/commit/6142c211378ffc1d282a35c1d25e41992c500f89
Click to expand...
Click to collapse
He didn't pick that, that commit doesn't exist in nine7nines kernel at all. He committed as nine7nine (something he keeps doing). That commit is 100% kingbri's, yet he is giving nine7nine the authorship and making nine7nine look like a fool.
@kingbri: fix it.
This is something that has been bugging me since the original conversation back with nine7nine. Fix it.
I've been in contact with github over this. I'm also trying to get in contact with nine as well to make a dmca claim.
What you are doing is in violation of the gpl.
So I sat in his telegram and decided to see what he has been saying. So first off he denied he'd ever heard of it, you can scroll down on this forum and see the original King-Kernel thread I'll leave a screenshot attachment, let's call it exhibit a.).
Then he warned the person and said only talk about this in private. Exhibit b.)
And just for archival sake. Exhibit c.) the actual dev letting him know about this MONTH'S ago.
Edit: I'd love a response that isn't full of it, or even better a full apology and fix.
AllusionPDX said:
So I sat in his telegram and decided to see what he has been saying. So first off he denied he'd ever heard of it, you can scroll down on this forum and see the original King-Kernel thread I'll leave a screenshot attachment, let's call it exhibit a.).
Then he warned the person and said only talk about this in private. Exhibit b.)
And just for archival sake. Exhibit c.) the actual dev letting him know about this MONTH'S ago.
Edit: I'd love a response that isn't full of it, or even better a full apology and fix.
Click to expand...
Click to collapse
I just got banned from his chat for trying to have the type of discussion that needs to happen to address the issue. This thread should be closed at this point
Firstly, I would like to say that I'm sorry that I didn't address the git issues when they came up 3 months ago, it was a tough place for me and I had to take a hiatus. However, this situation wasn't dealt with properly. I said that I'll fix the issues, but these people kept berating me with insults and didn't listen that i'm fixing the issues. So, I am fixing them as I post this, but the issues need to be discussed in a calm and formal matter and not just straight up insulting me. This is the end of this discussion
kingbri said:
Firstly, I would like to say that I'm sorry that I didn't address the git issues when they came up 3 months ago, it was a tough place for me and I had to take a hiatus. However, this situation wasn't dealt with properly. I said that I'll fix the issues, but these people kept berating me with insults and didn't listen that i'm fixing the issues. So, I am fixing them as I post this, but the issues need to be discussed in a calm and formal matter and not just straight up insulting me. This is the end of this discussion
Click to expand...
Click to collapse
1) no one is insulting you. No one in this thread has said anything to you that could be considered an insult. If anything, you are insulting us by banning us from your telegram group to avoid fixing the problem
2) you are the one who has not handled the situation properly. It takes a fraction of a day to fix a commit yet this whole drama has been going on for months and you have been too stubborn to just fix it. Again, banning people and ignoring the problem is not the way to deal with it
Sent from my Pixel 2 XL using Tapatalk
slothdabski said:
1) no one is insulting you. No one in this thread has said anything to you that could be considered an insult. If anything, you are insulting us by banning us from your telegram group to avoid fixing the problem
2) you are the one who has not handled the situation properly. It takes a fraction of a day to fix a commit yet this whole drama has been going on for months and you have been too stubborn to just fix it. Again, banning people and ignoring the problem is not the way to deal with it
Click to expand...
Click to collapse
It's a start. He did apologize. Hopefully he will learn.
https://github.com/King-Kernel/KingKernel-marlin/issues/1
Commits fixed. the branches KingKernel and KingKernel-oct-stable now have the fixed authorship of the commits. If the commits show up in the search bar, it's from the branches that are NOT the ones listed above
@slothdabski and @shagbag913, i'm gonna unban you guys from the TG chat
kingbri said:
Commits fixed. the branches KingKernel and KingKernel-oct-stable now have the fixed authorship of the commits. If the commits show up in the search bar, it's from the branches that are NOT the ones listed above
@slothdabski and @shagbag913, i'm gonna unban you guys from the TG chat
Click to expand...
Click to collapse
Thank you, appreciate it [emoji106]
Sent from my Pixel 2 XL using Tapatalk
Related
Read the Known Issues section of this post below along with the FAQ a few posts down before posting.
A few people have asked about I9100 builds of my Daily Driver kernel for the SGH-I777. I normally hate blind development, but since most I9100 guys are doing it for I777 targets, I may as well try going the other way. Since it fails the definition of being a "daily driver" as I own an I777 and not I9100 - it will not be using the Daily Driver name.
This should be compatible with most stock-derived Gingerbread firmwares, with a few exceptions listed below. It is NOT compatible with CM7/MIUI or any other AOSP-derived firmware. It is NOT compatible with ICS and WILL NOT BE until ICS kernel source for the I9100 is released. At that point a new thread will be created for those kernels. I am testing it currently with self-deodexed/debloated/Hellraised XWLA4.
The following firmware bases are likely to deliver poor battery life with this kernel due to wifi bugs in the firmware:
XXKI3, UCKK6, XWKK5 - especially UCKK6 and XWKK5
This kernel series is intended to be similar in spirit to my Daily Driver series for the Infuse at http://forum.xda-developers.com/showthread.php?t=1212795
It is built from sources at https://github.com/Entropy512/linux_kernel_sgh-i777/commits/oc_codeworkx, and initramfs at https://github.com/Entropy512/initramfs_sgh-i777/commits/master
My general goals are to focus on stability and battery life. If it comes to a tradeoff between performance and the above two, I will choose stability/battery life. In general I will choose stability first, with the exception of undervolting.
I keep my initramfs clean - There are no tweaks or other automated scripts built into this kernel. For a collection of tweaks I am working on and documentation on them, see http://forum.xda-developers.com/showthread.php?t=1378080
Current features:
I9100 Update3 base
Touchscreen drivers from I777 source code base
codeworkx's cpuidle patch - should improve battery life a bit. In most cases it will likely not improve things much, but in rare cases it will result in significant improvements. (I only have one partially-reproducible test case on the Infuse so far)
JHash 3
BFQ I/O scheduler
CIFS module in initramfs
CWM 5.0.2.8 compiled from CM7 sources on 2/28/2012
"insecure" kernel (meaning root in ADB)
CPU governor set to Conservative by default to conserve some battery - this will make your device slightly less responsive, use SetCPU or a similar app to return to ondemand if you want it, or reduce the conservative polling interval
Filesystem readahead tweaks in initramfs
netarchy's Sleep of Death fix
netarchy's conservative governor tuning patch - should improve responsiveness of devices when using the conservative governor if you reduce the polling interval (misnamed as sample_rate) - the I9100 community calls this "lionheart" even though it's really only a 2-line patch
Battery charge current monitoring (CurrentWidget) support - only reports charge current and not discharge, and reports a value 2.85 times the actual current. Use CurrentWidget's "operation on value" to divide by 2.85.
Miscellaneous bugfixes pulled from Ninphetamine and CM7 sources - see github for details
/system/etc/init.d support in initramfs - Note that this only runs stuff in /system/etc/init.d - ROM developers or you need to create it. Attached is an example script that will change the CPU frequency governor to ondemand if placed in /system/etc/init.d and set to executable
Four "use at your own risk" features that trade performance for stability - See Post #4 for details
Standard bootanimation support
/proc/last_kmsg crash debugging support
NFS modules in initramfs - note that they must be insmodded in a specific order: sunrpc.ko, lockd.ko, then nfs.ko
Fix for fuel_alerted perma-wakelocks
Fix for wifi tethering on I9100 ROMs that have been Hellraised to I777
Bump up TCP buffer sizes in initramfs to match that of the Infuse - may help network performance in some cases
cpuidle driver from Tab 7 Plus kernel - allows entry into AFTR more often - includes MFC interoperability fix (Should not break video playback.)
Support Bluetooth HID on newer firmware bases
3-step GPU clock/voltage control
Extended hotplug tuning
Support for Xan's ExTweaks universal tuning app - https://market.android.com/details?id=com.darekxan.extweaks.app
Planned features, short term:
Determine if issues with PINlock when running I9100 firmwares on I777 have kernel involvement, and fix them if this is the case.
Planned features, mid-term:
Potentially my first departure from "standard" governors, with a focus on improving hotplugging logic
Planned features, long-term:
Improved battery charge algorithm for faster charging - Initial research indicates we have an alternate battery charger chip (MAX8922) that differs from the MAX8997 used in the I9100. We DO have an 8997 also - but on our device for some reason Samsung decided to use an alternate chip instead of using the 8997's built-in charging. This means we have far fewer options (90,400,660 mA) in terms of charge rates compared to the I9100 (from 200 to 950 in 50 mA steps). So we might not be able to implement any fancy charging algorithms.
Features not planned:
BFS process scheduler - I have only once ever seen a test case where this clearly outperformed the mainline Linux scheduler (multithread x264 encoding) - The mainline schedule was fixed in the next release and BFS now has no performance benefits
Any feature that trades off stability or data integrity for performance unless it can be disabled entirely and defaulted to "off"
Any feature that cannot have functionality tested without a paid app. Interface-only checks don't cut it - I don't want users complaining that the app they paid for didn't work because an interface check worked but function didn't
Touch recovery - too prone to unintentional user input in dangerous situations. I will reconsider this with ICS.
ARM_TOPOLOGY/SCHED_MC - See http://forum.xda-developers.com/showpost.php?p=23193259&postcount=100 for details
Known issues:
Power management regression somewhere between 12/8/11 and 1/2/12 - Intermittent high drain without high AOS or reduced deep sleep percentage when on some wifi networks - seems more likely if GPS is used when connected to wifi. Wifi with high AOS/reduced deep sleep is not a kernel problem. This appears to only happen on some firmwares - it happens on XXKI3 but not XWKL1. It is likely connected to a wifi power management bug in some firmwares. A debugging feature in 2/7 and later will allow identification of such firmwares - see http://forum.xda-developers.com/showpost.php?p=22581928&postcount=1777 for details
Some people have reported touchkey lights becoming disabled until the screen is turned off and back on again. Under investigation - seems to mainly happen on firmwares with BLN-modded liblights even if the BLN app isn't used
Internal and External SD card are swapped in CWM currently
Keymap is a little funky in CWM for I9100 users. VolUp/VolDn to move, Power to select is reported to work, but bottom keys are funky. Working on it
A few users have reported that when Hellraising I9100 firmwares to I777, they are unable to set up a PIN-lock. If this occurs for I9100 users on their own devices, I need to look into initramfs fixes and this will be my top priority.
Basic flashing instructions for .tar releases (NOTE - There are currently no releases in this category. These instructions only remain for heimdall+ZIP users:
(Tested on Linux, not tested MacOS/Windows but should work) Heimdall - Extract the contents of the tar file, enter download mode, and flash with the following command line:
Code:
heimdall flash --kernel zImage
Flashing instructions for .zip releases:
Flash in CWM, or extract the zImage and use the Heimdall instructions above.
Please do not ask how to enter download mode or install Heimdall/Odin in this thread - these are basic generic skills anyone flashing custom firmwares on Samsung devices should know and plenty of documentation exists elsewhere. If you really need to ask, use the General forum, or if created, the Q&A forum. I want to try to keep this thread clean and only with bug reports and issues specific to this release, not general HOWTO or troubleshooting posts. Some of the information you need is in jivy26's FAQs thread at http://forum.xda-developers.com/showthread.php?t=1288112 - Reading at least the first post of this thread in its entirety is STRONGLY recommended.
Bug reports:
If you have a crash (reboot all the way to Galaxy S I9100 screen), use ADB dump the contents of /proc/last_kmsg and post
If you have oddball behavior, include a clearly reproducible test case with your report, or use ADB to obtain a dmesg and logcat capturing the odd behavior at the time of error.
Similar to flashing - using ADB and obtaining last_kmsg, dmesg, and logcat dumps are basic skills that anyone working with custom firmwares on Android devices should have. If you need help with these, do some searching, or post in the General forum or Q&A forum.
Firmware ("ROM") Developers:
While I cannot restrict anyone from putting this kernel into a ROM as long as links are given to the github sources for GPL compliance, I request that anyone who includes this kernel in a firmware release does the following out of courtesy:
Link to this thread
Clearly indicate in your firmware changelog which Daily Driver kernel release is included in your firmware release whenever you change DD releases - this lets users identify whether a fix is present in the kernel they're using or not
Kernel Developers:
Similar to my request for ROM developers, while I can't restrict you from doing anything, I ask as a courtesy that if you cherry-pick my commits, you do the following:
Please don't rebase my commits into a large multi-feature without consulting me - rebasing related bugfixes together is OK.
Please try not to implement lots of unrelated features or bugfixes in a single git commit - it makes it hard to reimplement that when Samsung drops new sources or releases a new device
ALL OF MY RELEASES ARE NAMED BY RELEASE DATE - MMDDYYYY. See the changelog for differences between Experimental (exp) and non-exp versions for days where dual releases are made.
Change Log
The primary change log will be kept in my I777 kernel thread at http://forum.xda-developers.com/showpost.php?p=18129037&postcount=2
Unless I9100-specific items are implemented, this post will simply indicate which I777 release the kernel corresponds to.
3/7/2012:
Corresponds to Daily Driver 3/7/2012
03/05/2012:
Corresponds to Daily Driver 3/5/2012
03/04/2012-B:
Corresponds to Daily Driver 3/4/2012-B
03/04/2012:
Corresponds to Daily Driver 3/4/2012
03/03/2012-B:
Corresponds to Daily Driver 3/3/2012-B
03/03/2012:
Corresponds to Daily Driver 3/3/2012
Initial release was bad, that was an I777 build. Reuploaded at 4:22 PM Eastern Standard time on 3/3 - Redownload if you downloaded before that
3/02/2012:
Corresponds to Daily Driver 3/02/2012
2/28/2012:
Corresponds to Daily Driver 2/28/2012
IMPORTANT: Internal/External sdcards have been swapped in CWM to be consistent with Android standards!
2/26/2012:
Corresponds to Daily Driver 2/26/2012
Initial release, 02/15/2012:
I know it's dated 2/15 and not 2/26, because that's when it was built. Thanks to khartaras for indicating that it isn't at least a horrible turd when used on an I9100.
This release corresponds to the 2/15/2012-C release of I777 Daily Driver
Here Be Dragons
This post is for features present in the kernel that are "use at your own risk" - They have either potential or guaranteed negative side effects if used.
Overclocking (CPU):
Enable using SetCPU or a similar app
USE AT YOUR OWN RISK. DO NOT REPORT BUGS OR PROBLEMS IF YOU ARE OVERCLOCKING OR UNDERVOLTING. IF YOU EXPERIENCE ANY STABILITY PROBLEMS, DISABLE ALL OC/UV
Overclocking (GPU):
See Ninphetamine kernel for documentation - Same control method
USE AT YOUR OWN RISK. DO NOT REPORT BUGS OR PROBLEMS IF YOU ARE OVERCLOCKING. IF YOU EXPERIENCE ANY STABILITY PROBLEMS, DISABLE ALL OC
Per-File fsync() disable:
This allows you to disable per-file write forced syncs. (e.g. if an app tries to force a write straight to disk, it'll just go to cache). This achieves the same goal as the modded sqlite hacks seen in tweaks such as USAS, however it can be disabled at runtime.
WARNING: THIS CAN CAUSE DATA LOSS OR CORRUPTION IN A CRASH
To enable, do the following in a terminal, or add it to an init.d script (look at my ondemand script as an example):
Code:
echo "1" > /sys/module/sync/parameters/fsync_disabled
And to disable (return to the default):
Code:
echo "0" > /sys/module/sync/parameters/fsync_disabled
Good for around 200 points of epeen in the database benchmarks in Antutu or 500-600 points of epeen in Quadrant. Real-world benefit: Probably not worth the data integrity risk, but you've got a choice now.
Backlight Notifications (BLN):
This allows the touchkey backlights to be used for notifications. Some stock apps (such as stock MMS) don't support it. Supposedly services.jar mods can change this.
This WILL drain your battery when a notification is active due to a wakelock that holds deep sleep. Sorry, it's either this or instability for the time being.
In addition to the BLN control app, the ROM needs a modified liblights file for this to work
Attached here - Liblights - both BLN-modified (extracted from VillainROM 3.0) and stock I777
To install, take the file and push it to /system:
Code:
adb remount
adb push <file> /system/lib/hw/lights.SGH-I777.so
adb chmod 644 /system/lib/hw/lights.SGH-I777.so
Then reboot
Note that on a Hellraised ROM, you need to replace SGH-I777 with GT-I9100. This includes manually ported ROMs like Cognition 777
Like my prerooted system image, this file is compressed using 7-Zip to prevent people from trying to flash it with CWM
OK, right now this post only has documentation of one "special but safe" feature:
To enable debugging of high deleted_wake_locks time, I've set this up to allow wake_lock_destroy() to be debugged without enabling DEBUG_WAKE_LOCK (which spams dmesg with a ton of stuff not needed for wake_lock_destroy() debugging). To enable, add 32 to the value of /sys/module/wakelock/parameters/debug_mask - This defaults to 3, so the proper value is 35.
Code:
echo "35" > /sys/module/wakelock/parameters/debug_mask
Return this to 3 to set it back to the default.
With this, you'll see wake_lock_destroy debugging information in your dmesg output. This is only needed if you have very high deleted_wake_locks times.
The following is known to cause deleted_wake_locks:
Turning off wifi will convert all wlan wakelocks into deleted_wake_locks
FAQ
Q: I installed this and still don't have root?
A: I keep a clean initramfs. There are NO tweak scripts in it, and no autoinjection scripts. To root your device, flash one of ChainsDD's Superuser packages in CWM
Q: I don't like the default I/O governor, why is it this way?
A: Clean initramfs (if you need to flash a kernel cleaner script after my kernel, I have failed or an app cluttered up your init.d) - If you want to change the default governor and tune the filesystem, see my init.d scripts thread.
Q: Why is it so laggy by default?
A: I don't believe in having half my patches tuning default values of things the user can change. In addition, as stated above - battery life is valued over performance, so default governor settings will be biased towards battery. My personal recommendation if you wish to increase performance (at the cost of battery life) is to drop the sample_rate for the conservative governor using SetCPU or a similar tool - this will significantly improve performance. It provides nearly all of the benefits of the original "lionheart" without allowing the sample_rate to go dangerously low. In a future release I'm going to drop the minimum a little bit more.
Q: Something went wrong. I'm using some stupid comprehensive tweakscript. Y U NO FIX?
A: I will not support anyone who is using a comprehensive tweak script (Thunderbolt, V6 Supercharger, etc. - ESPECIALLY V6 Supercharger, as its developer has multiple times in the past put in dangerous tuning options. For example, he disabled the panic reboot timeout, which combined with Samsung's ****ty wifi driver on the Tab 7 Plus, led to multiple Tabs draining their battery all the way to the battery's failsafe cutoff.) If a specific individual tweak causes a problem, let me know - but you'd better know EXACTLY which tweak it is. In addition to the above issues with V6SC, many "tweak scripts" achieve their goals by trading filesystem integrity for performance, and irresponsibly don't warn the user about this fact. See, for example, the fsync disable feature above - it's dangerous, but don't say I didn't warn you it was.
Q: What voltages do you use?
A: This is irrelevant. Every device is different, if a given set of voltages worked on all devices, Samsung would've made it stock. I will report any discussion of voltage recommendations to the moderator for cluttering the thread. If you're undervolting, you need to take responsibility and do it on your own.
Q: Why don't you support AOSP firmwares (CM7, etc.)?
A: I know that the CM team frowns upon alternate kernels as it makes their testing job more difficult. Similarly, supporting too many firmware bases makes my job more difficult. Out of respect for the skills of codeworkx and atinm, I will not release kernels that could make their life harder. I periodically give them the heads-up on patches that I think are important though.
Q: What's with the toilet humor of the name?
A: Long ago in the Infuse community, there was a person (lemons) that was starting to do some smali hacks (camera modding and such), and was planning on eventually releasing a ROM. He was a pretty good guy, and had lots of potential. He and others joked that since it was his first attempt, it should be called ****ROM. Sadly, lemons never followed through and just disappeared, so for months, ****ROM never became a reality. Eventually it was realized in the form of a deodexing/porting/basic modding guide for I777 users at http://forum.xda-developers.com/showthread.php?t=1505685. In addition - I hate hype and marketing, better to set expectations low and let the code prove itself on its own merits. Since I'm blind-developing, I can't just say it's my daily driver because in this case, I am unfortunately not eating my own dogfood.
Q: Why don't you base on 2.6.35.14?
A: That would be my Experimental series. It's temporarily on hold for a variety of reasons but will return once I finish reimplementing some patches. The great thing about git branching is I've been able to maintain .7 and .14 trees simultaneously with ease.
Q: Sometimes my touchscreen is unresponsive right after a wakeup, why?
A: It seems, based on reports from khartras and teiglin, that TouchScreenTuner does not play well with the I777 touchscreen drivers. I'm not sure if it's even necessary with them - in the months since October, the only time I have ever received touchscreen complaints from I777 users was when running I9100 update3 touchscreen drivers. TST may just be working around broken drivers...
Reserved for ?????
Thanks for this. I will try later.
Again very thanks.
Enviado do meu Galaxy S2 usando TapaTalk
Going to try this kernel for the sole reason that I think you're a great guy on here and I enjoy reading your informative posts - you always seek to educate rather than put people down.
Thanks Entropy.
Uploaded a new release, this has just a few small patches, bringing it up to the same base as Daily Driver 2/26/2012
As a compulsive lurker, reader and searcher, ive been looking forward to this release..
Alongside Pulser and Ninpo, your informative postings and professional ethic enable users like myself to maximize the potential of our devices.
Thanks mate, i have no doubt this will be brilliant..
Thanks Entropy, I've missed your work since I moved from Infuse over here instead of to I777-land. I do have a question, though--I note the only "nonstandard" I/O scheduler you included was BFQ. Do you find sio/vr problematic, or do they just not provide any benefit from your perspective?
teiglin said:
Thanks Entropy, I've missed your work since I moved from Infuse over here instead of to I777-land. I do have a question, though--I note the only "nonstandard" I/O scheduler you included was BFQ. Do you find sio/vr problematic, or do they just not provide any benefit from your perspective?
Click to expand...
Click to collapse
I'm considering adding these - I've found that alternate governors/schedulers often cause more problems than they solve.
Thanks for sharing your kernel with us i9100 users Enthropy. I really like your stability+ battery approach. Will be giving the kernel a good go.
Sorry...this kernel is comparible with jkay brightness profile?
Inviato dal mio GT-I9100 usando Tapatalk
coloxim said:
Sorry...this kernel is comparible with jkay brightness profile?
Inviato dal mio GT-I9100 usando Tapatalk
Click to expand...
Click to collapse
No - And right now, I am unaware of any kernel that is. As much as I like JKay's work, I believe he lacks understanding of how screen brightness works on the I9100 and I777.
Even JKay is unaware of any kernels that support those profiles. See entry 12 in his FAQ.
To implement additional brightness steps, an additional gamma table for each brightness step needs to be implemented - https://github.com/Entropy512/linux_kernel_sgh-i777/blob/master/drivers/video/samsung/ld9040_gamma.h
So until FAQ section 12 has clearly defined (and achievable) requirements for compatibility, or JKay declares a specific kernel compatible in FAQ section 12 of his mod, I won't be doing anything. Creating a custom gamma table entry is not easy as it requires a LOT of tweaking and good colorimeter hardware. Supercurio has done it at high brightness levels to my knowledge, but I don't think he's done it for low brightness levels and I don't think he's added extra gamma tables for additional brightness steps.
Edit: I have seen that Speedmod and Redpill do change the table entries for the lowest two brightness settings - however, they don't add any new bins, so the brightness change is achieved even on JKay profiles that don't supposedly require kernel support. e.g. JKay's "dark, requires kernel support" are pointless because the only kernels that actually provide dimmer minimum backlight do so even with his profiles that don't claim to require custom kernels. (And the "super dark" and "dark" profiles will behave the same regardless of kernel.)
What's interesting is hardcore did it for only two of three available panel types. Either two of Samsung's panel types are brighter than others, or hardcore did this without testing on some panel variants and just thought "the numbers are different, I'll change them". I'll look into playing with this as it would be nice to have lower minimum brightness, but it's somewhat low priority as it's easy to simply make things look like **** if you're not careful.
its possible to make your kernel fully compatible with the cmw manager of chainfire
for now some fonctions are desactivate
anyway i m testing it now and all seems to be good
So far so good mate.
Batterylife we will see in a day or two but all in all running fine.
Thanks and go ahead with ur work.
CHEERS ;-)
Sent from my Galaxy S2 - I9100 with SensatioN Rom!
F3nr1s said:
its possible to make your kernel fully compatible with the cmw manager of chainfire
for now some fonctions are desactivate
anyway i m testing it now and all seems to be good
Click to expand...
Click to collapse
Others have asked me this - if he has compatibility guidelines posted somewhere, I'll take a look at them.
{
"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"
}
Battery in deep sleep is exceptional, 2% lost in 5 hours with WiFi enabled and emails syncing.
Sent from my GT-I9100 using XDA App
Facality
weird name for a kernel..or for pretty much anything..dude
please leave non-dev related posts here: http://forum.xda-developers.com/showthread.php?t=1658647
{
"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"
}
Features:
based on JB sources
DISABLED CAP_ERASE (No superbrick bug)
All-in-1kernel because it supports CM9, CM10, Samsung, MIUI and Boot-to-Gecko (B2G) ROMs with a single kernel image. (no Sense4all support)
Dual booting support for all supported ROM types. See droidphile's post for Dual Booting FAQ
Custom CWM touch recovery with swipe gestures and double-tap selection
6-steps CPU freq
5-step GPU frequency levels. VPLL Mode to have additional frequency steps. defaults frequencies: 66-108-166-267-330.
Auto-root. You can also remove root via STweaks app and install it without rebooting your phone again. Auto-root can be disabled as well.
CPU Overclock/Undervolt support (we have two interfaces for that. both of them are defacto standard)
Tweakable vitalij's value (set to 5 as default)
Adjustable touchpad led brightness
Fixed fuelalert wakelocks
You can completely disable android logger using STweaks app
Faster charging for misc and USB modes. There are 3 modes (AC, Misc, USB) and normally last two of them support only slow charging. You can have charging speed of AC by increasing it (especially user while charging in car or using USB port)
Cpu governor optimizations
Gpu voltage, clock and stepcount interfaces (GPU Overclock/Undervolt)
Screen brightness curve settings with original panel gamma values. panel values unchanged, so you will get stock colors and will be able to use supercurio's voodoo display app when it is released. brightness modification will only change auto-brightness response.
BLN support both for Samsung and CM ROMs (you can use STweaks, Nstools or BLNControl app from the market to enable it)
Breathing or Blinking effect for BLN. (Make sure you don't enable blinking in any other BLN app) Use STweaks to select one of them.
Better touch sensitivity
Available CPU Governors: Pegasusq (default), Ondemand, Lulzactive, SmartassV2, Interactive and Conservative, Performance, Userspace, Powersave
CIFS as module
Available I/O schedulers: CFQ (default), noop, Deadline, SIO, V(R)
J4FS as module
ARM topology support (SCHED_MC)
Automatic EFS Backup
Lots of I/O tweaks and filesystem optimizations via some parts of thunderbolt scripts.
USB Mass Storage mode is working in CWM Touch Recovery and you can mount both internal and external sdcard as a disk drive
NTFS automounting for USB sticks. When you plug in an NTFS formatted USB flash it will be automatically mounted to /mnt/ntfs folder.
USB mouse and keyboard support
built-in profile support with default, battery and performance presets (you can change them in CWM Recovery). Even using everything default will save you a lot of battery juice.
Eargasm for headphone amplification (in STweaks) as free Voodoo Louder replacement
Almost everything is configurable such as scheduler features, hotplug thresholds, GPU frequencies, voltages, arm topology modes... and they are configurable via simple and free STweaks app which is embedded in the kernel and soon in Google Play & Opensource
Adjustable mDNIe settings
optional sharpness tweaks from hardcore
mDNIe negative effect toggle with home button (press it four times)
Touch gesture support by Tungstwenty. (http://forum.xda-developers.com/showthread.php?t=1831254)
BLNWW (BLN Without Wakelock)
Slide2Wake (originally by Fluxi)
More to come...
Known Problems:
no known problems yet
Thanks To:
Chainfire, Codeworkx, Arighi, Tegrak, Vitalij, Entropy512, Netarchy, koush, Creams, sk8erwitskil, hardcore, Pikachu, myfluxi, Tungstwenty
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..
Download Link: http://www.gokhanmoral.com/
for beta versions: http://d-h.st/users/siyah/testingIRC support and chat:
Server: irc.FreeNode.net
Channel: #siyah-kernel
web client: http://siyah.twosx.net/ (thanks to omniwolf)Changelog:
See http://www.gokhanmoral.com/ for changelog.
You can find the sources at http://github.com/gokhanmoral/siyahkernel3
and initramfs at http://github.com/gokhanmoral/initramfs3
Todo:
these are my future plans and some of them are dreams only...
apply chargecurrent modifications even if the cable is connected on boot
add optional teamwin recovery
make dual-boot timeout configurable
implement BFN (BackFlashNotification)
scheduling for BLN
organize recovery menu items
higher polling rate for light sensor
remap mouse right button to back button
exfat support
fix blnww battery drain issue (may not be possible)
implement dual-booting with GB+ICS ROMs
faster switch between first and second ROMs without needing to reboot if possible.
...
troubleshooting
READ THESE FIRST
Never report any bugs to CM9/CM10 threads if you use it together with SiyahKernel
Do not ask questions to me directly. This is a common thread, not my personal inbox. Ask your questions in the thread and do not target them to anyone.
Do not expect answers to all your questions. There are some questions which nobody knows the answer of.
Do not forget that this is a development thread. There is another thread in general section for those who wants to discuss battery life and chats. If your post does not include a feature request, bug report or suggestion it should be posted to the other thread.
No ETA for new version. Even if I sometimes talk about release dates those may change and they change for some good reason or because of my real-life obligations.
Make use of "Search this Thread -> Advanced Search"
Never ever discuss anything deep-sleep related in this thread. I do not make modifications to prevent sleep and 99% of deep sleep problems are application/ROM related. discuss it in general section. I do not want any positive ("this kernel sleeps like a baby") or negative ("There is a big problem with deep sleep. Please fix it") messages in my development thread.
If you do not provide details about your configuration and settings nobody can help you or nobody will care about your problem/bug report. The problems without details (ROM, settings, preferably the version that the problem first happened or the one that you don't experience the problem) will be ignored.
Never ever report any SOD issues if you are undervolting/overclocking and make sure you attach last_kmsg log. If you don't know what it is report the problem to the other thread because one more post without any useful information on dev thread will help noone including yourself.
FAQ:
Q: I am having some random lockups with some apps
A: try removing root by using STweaks app and restart.
Q: What is the difference between STweaks and ExTweaks?
A: Both have similar functionality. ExTweak is Xan's implementation of the UCI interface (which is designed by Xan and me with the helps of AndreiLux and implemented in the kernel as open scripts by me) and STweaks is mine. I was hoping Xan would release the sources of ExTweaks (without profile support) but he changed his mind and I decided to open STweaks. Soon they will have almost identical functionality, so you can use whichever you like.
Q: Does this kernel work on XXXXXX-ROM?
A: If the ROM is based on Samsung Stock ICS Rom LPQ or newer, it should. Otherwise, search the thread... If you cannot find any reference to that ROM, try the kernel. You won't lose anything by trying this kernel. Worst case scenario is to reflash your previous kernel or ROM. You can backup your previous kernel with Hellcat's k-tool from the market.
Q: Where is CM9, MIUI or Samsung ROM versions?
A: There is only one version. Both ROMs are supported with a single kernel image.
Q: What is the best settings?
A: It is the one you try yourself and like.
Q: I have just lost 20-30% battery by just rebooting/flashing the kernel. Is it a bug?
A: No. It happens because of our fuel gauge chip which doesn't require calibration goes crazy sometimes. It is not related with kernel or ROM. Just reset fuel gauge chip using STweaks app (or remove the battery and wait 3 minutes) and then charge your phone.
Q: BLN doesn't work.
A: you need to enable it in stweaks or BLN app. if you have more than one app to configure bln make sure all of them use the same settings.
Q: BLN works in test mode but it doesn't work otherwise.
A: if test mode works you should blame the apps. Stock messaging and email apps may not support BLN and in some other applications you may need to enable notifications. Either find another application or change your ROM.
Q: Can I use breathing effect without using BLN?
A: for now, breathing effect only works in BLN. There is no way of using it otherwise.
Q: I need to disable and re-enable BLN in stweaks to get it working again. What is the problem?
A: You may have another BLN related application (BLNapp, nstools, or a script) which disables BLN after stweaks apply the setting at early boot stage. you have to either uninstall that app or enable BLN in that app as well.
Useful Links:
Almost everything that you need to know about Kernels, schedulers and so by droidphile
Another great post explaining more and ICS differences by droidphile
Although I put it in the first post, this is my github for kernel sources, initramfs and some more
You can find all the answers you need here, even those that I don't know
There is a CWM flashable package in this post for those who prefers mass storage mode to MTP
Another way (app) of having mass storage mode: USB Mass Storage for ICS App
Everything you need to know about Dual Booting (FAQ & Guide) from droidphile
Another Dual Boting Guide from Phistachio
Very good work Gokhan, as always!
I have finally got my first ics kernel booting on my phone too, have to add all features now!
PS: really want to see your new cpu driver....i really understand almost nothing on the new one lol
Wireless & Ad hoc network
Hopefully it will support wireless and ad hoc network connection like the one you created for gingerbread kernel.
If they don't understand what's gokhan is doing for himself and freely shares it with us! Just leave them alone.
Thanks man i knew you will be fast but now I'm shocked.
Sent from my GT-I9100 using Tapatalk
And to help you on your way even the CM9 kernel has been built from source and released tonight to help further your support for ICS ROM's hopefully *cough*SlimICS*cough*
Don't blame me for this question i didn't know where to ask it . Why gokhan's status is still senior member? Why not a recognized developer? all the developments he has done on kernels counts for something or what?
Sent from my GT-I9100 using Tapatalk
mekhonte said:
Don't blame me for this question i didn't know where to ask it . Why gokhan's status is still senior member? Why not a recognized developer? all the developments he has done on kernels counts for something or what?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I guess he's not applied for it (I would need to check to be certain), but if he wants to apply, he's more than welcome to (application process is opening again soon)
henrybravo said:
Are you talking about this? (From the OP)
Click to expand...
Click to collapse
I am talking about touchscreen responsiveness same as in CM9 with LP6 kernel.
I slept off on the keyboard waiting. GM can we expect download link soon? Its 5:00am here and I think I need to catch some sleep before going to office... I havent waited for my GF so much.. Damn..
I'll make myself a coffee and test it for 10-20 mins then upload to my blog as first beta...
I finished everything except for BLN. I tried, but could not finish it because of lack of complete cm9 repository in my vm. if anybody can compile liblights, everything else is in the kernel now. If nobody compiles it by then, I will do that in this week, hopefully.
I am surprised with the changes in the platform specific parts. I wasn't expecting that Samsung would make a change in that crap but they did and it looks much better. I have a theory that they outsourced the kernel part (maybe to odroid guys) because some parts look very good which is not something I expect from Samsung softwarewise
anyway. it was a real fun for me. I hope it will be at least as much fun to use it for you.
let the celebrations begin
it's up
and a last minute addition was made for smartassv2 lovers
I guess I take the credit of installing it first.. Installed .. Siyah 3.0b1 CWM . Thanks Golkhan...
Which defconfig did you use to start from? u1_defconfig?
Taking a dinner break before resuming this.
I'll be very busy this week. that is why I spent some time tonight to make this release.
I'll edit the OP later.
and.. somebody asked why I am not a recognized developer...
Pulsar is right, I did not apply
I think I still have some more to do before doing that.
it's good to be a senior member.
I find the recognition in your comments, not in a title.
Entropy512 said:
Which defconfig did you use? u1_defconfig?
Taking a dinner break before resuming this.
Click to expand...
Click to collapse
yes, I used u1_defconfig.
and I'm happy that this release has also at&t parts..
you won't struggle much
gokhanmoral said:
I'll be very busy this week. that is why I spent some time tonight to make this release.
I'll edit the OP later.
and.. somebody asked why I am not a recognized developer...
Pulsar is right, I did not apply
I think I still have some more to do before doing that.
it's good to be a senior member.
I find the recognition in your comments, not in a title.
Click to expand...
Click to collapse
Are you using an auto detect initramfs here (ie does this work on cm9?)
pulser_g2 said:
Are you using an auto detect initramfs here (ie does this work on cm9?)
Click to expand...
Click to collapse
yes, I do. but I think samsung used another mali driver in the release. that may cause blank (black) screen. I am not sure if latest CM9 can use LPQ or LP7 kernels but if it can then this beta will support CM9 and most clones.
Welcome to the first custom kernel for the Samsung Galaxy Note 4.Providing instability to the masses since October 21, 2014
This kernel currently supports most North American carriers. Automatic selection is provided through the use of specialized recovery packages that will detect your device version and make appropriate adjustments.
Mereology (from the Greek μερος, ‘part’) is the theory of parthood relations: of the relations of part to whole and the relations of part to part within a whole. I do not take responsibility for anything these days, but I'll try to do my part and help.
Click to expand...
Click to collapse
Installing N910T ROMs on N910W8
Start with NJ3 stock firmware
Odin Flash CF-AutoRoot
Odin Flash TWRP
Make a full backup
Wipe system, data, cache, dalvik-cache
Install N910T Rom
Reboot System
Reboot Recovery
Install Stockish / Deported
Reboot System
Thank force70 for the guide
Known Issues:
DVFS set to ignore and secure storage disabled often resolve the lag. If you need either of these, stock / stockish are required.
Warning: I only have the T-Mobile version of the Galaxy Note 4
XDA:DevDB Information
StarKissed [ATT, CAN, TMO, USC, VZW], Kernel for the Samsung Galaxy Note 4
Contributors
twistedumbrella
Source Code: http://github.com/StarKissed/starkissed-kernel-trlte
Kernel Special Features:
Version Information
Status: Testing
Created 2014-11-07
Last Updated 2015-01-22
[Kernel] StarKissed [ATT, CAN, SPR, USC, TMO, VZW]
No mirrors please. Updates are posted 1 - 3 times per day.
Check the StarKissed website for compile info (not downloads)
Recovery Packages [Goo]
http://goo.im/devs/playground/galaxynote4/
Kernel source
http://github.com/StarKissed/starkissed-kernel-trlte
Retrieving a Kernel Log:
Code:
cat /proc/last_kmsg /sdcard/kernel_log.txt
SELinux Prerequisites:
The build.prop WILL override the kernel. It needs to be edited to match the desired settings.
Code:
(SELinux disable)
ro.build.selinux=0
(KNOX disable)
ro.config.tima=0
ro.config.knox=0
Potentially Inactive:
Potentially Unsafe:
pegasusQ
Features / Interfaces:
Linux 3.10.13 Linux 3.10.0
SELinux permissive
KNOX disabled
init.d support
Overclock to 2.8, Underclock to 268
Stereo call recording support
MNDIE Control
Motorola Memory Utils
Slimbus Overclock
Optimistic IPV6
intelli-plug (with arm64 updates)
Power Suspend
Simple GPU gov
HardLimit
intelli-thermal v1
Power Suspend Driver v1.5
Sweep2Sleep
Forced Fast Charge v1.2 (+ Wireless Charge Boost)
Advanced TCP avoidance
LZ4 compression
Dynamic FSync
add'l entropy: frandom, erandom (enabled via init.d)
add'l filesystems: NTFS, F2FS, CIFS
io: sio, fifo, zen, vr, bfq, fiops
gov: lionheart, dancedance, smartmax, pegasusQ, smartassV2, intellidemand, umbrella_core
CPU optimizations
Network optimizations
KNOX root and logging permissions
TIMA support, but disabled by default
S-View hack to use any cover
Common Interfaces
^ Borrowed from faux123 since many interfaces are MSM universal
Code:
cpu governor: /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
cpufreq: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
intelliplug: /sys/module/intelli_plug/parameters/intelli_plug_active
gpu governor: /sys/class/kgsl/kgsl-3d0/pwrscale/trustzone/governor
gpu freq: /sys/class/kgsl/kgsl-3d0/max_gpuclk
simple GPU gov:: /sys/module/msm_kgsl_core/parameters/simple_laziness
simple GPU gov: /sys/module/msm_kgsl_core/parameters/simple_ramp_threshold
io scheduler: /sys/block/mmcblk0/queue/scheduler
io scheduler readahead: /sys/block/mmcblk0/queue/read_ahead_kb
dynamic fsync: /sys/kernel/dyn_fsync/Dyn_fsync_active
usb fastcharge: /sys/kernel/fast_charge/force_fast_charge
intellithermal: /sys/module/msm_thermal/parameters/enabled
cpu voltage: /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
Power Suspend
Code:
/sys/kernel/power_suspend/power_suspend_state
/sys/kernel/power_suspend/power_suspend_mode (0 - auto, 1 - panel, 2 - userspace, 3- hybrid)
Hardlimit
Code:
/sys/kernel/cpufreq_hardlimit/scaling_max_freq_screen_on
/sys/kernel/cpufreq_hardlimit/scaling_max_freq_screen_off
/sys/kernel/cpufreq_hardlimit/scaling_min_freq_screen_on
/sys/kernel/cpufreq_hardlimit/scaling_min_freq_screen_off
/sys/kernel/cpufreq_hardlimit/wakeup_kick_freq
/sys/kernel/cpufreq_hardlimit/wakeup_kick_delay
/sys/kernel/cpufreq_hardlimit/touchboost_lo_freq
/sys/kernel/cpufreq_hardlimit/touchboost_hi_freq
/sys/kernel/cpufreq_hardlimit/userspace_dvfs_lock (0 - allow, 1 - ignore, 2 - refuse)
MNDIE Control
Code:
/sys/class/mdnie/mdnie/mode (0 - dynamic, 1 - control, 2 - natural, 3 - movie, 4 - auto)
/sys/class/mdnie/mdnie/...
hijack
curve
copy_mode
sharpen
red_red
red_green
red_blue
cyan_red
cyan_green
cyan_blue
green_red
green_green
green_blue
magenta_red
magenta_green
magenta_blue
blue_red
blue_green
blue_blue
yellow_red
yellow_green
yellow_blue
black, 0664
black_red
black_green
black_blue
white_red
white_green
white_blue
scenario
App & Donations:
StarKissed [SKU] on Google Play allows you to configure many of the options provided by this kernel. Issues or comments about the app can be posted at the XDA StarKissed app thread
Donations are not being collected through the forum. If you would like to donate, you may do so through StarKissed [SKU] on Google Play by using the donate options located in the top right (the green dollar bill guy).
Will be nice if you can provide two different build. One without all the fancy things that some people wont have use for, such as overclocking, close to stock as possible but still provide stability, smoothness, and better battery life.
Some kernel makers just slap everything they can onto a kernel and in the long wrong, it is simply instable or provide hicups (that they will never own up to lol)
Nice job twisted keep it coming...
mgbotoe said:
Will be nice if you can provide two different build. One without all the fancy things that some people wont have use for, such as overclocking, close to stock as possible but still provide stability, smoothness, and better battery life.
Some kernel makers just slap everything they can onto a kernel and in the long wrong, it is simply instable or provide hicups (that they will never own up to lol)
Click to expand...
Click to collapse
I don't provide anything I wouldn't run on my own device. If you want it to be stock, vote for stock. If that is what wins, that is what I will build. It is enough to provide a single kernel for a bunch of devices without trying to keep track of per-device versions. I slap everything I can onto a kernel, test it, then delete or fix the broken stuff. My github is always current and anything I changed is clearly published to point the finger at whoever it needs to be pointed at.
Lol just throwing it out there , that is my vote
I vote like mgbotoe! Thank you sir!
Sent from my SM-N910T using XDA Free mobile app
Only thing I am seeking is SE Linux Permissive. Thanks for all your work!
Tried flashing the files (that are highlighted) in picture attachment using odin 3.07, got a fail. What am I doing wrong? Anyone else flash yet? How'd ya do it and did it work out ok?
Thanks Ahead.
Glen
Hardlimit by yank555 I'd like to see, along with your hotplug of choice, I like intelliplug myself, some govs, I usually stick with interactive anyways, maybe some mdnie controls etc etc. Lol I'm just tossing out what I enjoy..but, you tell me, what do you normally build in your kernels.?
re: kernels
twistedumbrella said:
I don't provide anything I wouldn't run on my own device. If you want it to be stock, vote for stock. If that is what wins, that is what I will build. It is enough to provide a single kernel for a bunch of devices without trying to keep track of per-device versions. I slap everything I can onto a kernel, test it, then delete or fix the broken stuff. My github is always current and anything I changed is clearly published to point the finger at whoever it needs to be pointed at.
Click to expand...
Click to collapse
I just hope that you have already gotten some sort of windows pc so you
won't be having all those problems you were having for the past 3-4 days
due to using a mac computer.
Good luck with your kernels.
p.s. my vote is the same as mgbotoe's
glensta said:
Tried flashing the files (that are highlighted) in picture attachment using odin 3.07, got a fail. What am I doing wrong? Anyone else flash yet? How'd ya do it and did it work out ok?
Thanks Ahead.
Glen
Click to expand...
Click to collapse
I've heard Odin doesn't like the files. I use Heimdall but I'll be looking into that.
Misterjunky said:
I just hope that you have already gotten some sort of windows pc so you
won't be having all those problems you were having for the past 3-4 days
due to using a mac computer.
Good luck with your kernels.
p.s. my vote is the same as mgbotoe's
Click to expand...
Click to collapse
You're starting to sound like the Best Buy reps when Windows 8 came out. At least before they had to start telling everyone 8.1 was coming to fix how terrible it turned out being once people started using it.
You have to run cygwin or an Ubuntu VM inside windows to build Android. You can run windows AND Ubuntu as windowed applications on Mac. Seems unnecessary when the real issue is consistency in the cm repos. The instructions say to get the Linux compiler ports, while detection identifies the platform compilers.
And fast change it you can
Sent from my SM-N910T using XDA Premium 4 mobile app
---------- Post added at 08:56 PM ---------- Previous post was at 08:56 PM ----------
jpeps said:
And fast change if you can
Sent from my SM-N910T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SM-N910T using XDA Premium 4 mobile app
How about color/gamma controls???
jpeps said:
And fast change it you can
Sent from my SM-N910T using XDA Premium 4 mobile app
---------- Post added at 08:56 PM ---------- Previous post was at 08:56 PM ----------
Sent from my SM-N910T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't know how good of an idea messing with the adaptive charging would be, but I'll look into it. It depends if that functionality is tied into the USB port charging or not.
It is great that you have done this work and I (along with a bunch of others) are really grateful - it would be nice if we could flash this -
Doesn't work with Odin - not sure about the other option you mentioned, I personally have never used that method -
So - any instructions you can offer would be great - unless you feel it is not appropriate to flash this yet?
Your help - and input is greatly appreciated.
mocsab said:
It is great that you have done this work and I (along with a bunch of others) are really grateful - it would be nice if we could flash this -
Doesn't work with Odin - not sure about the other option you mentioned, I personally have never used that method -
So - any instructions you can offer would be great - unless you feel it is not appropriate to flash this yet?
Your help - and input is greatly appreciated.
Click to expand...
Click to collapse
Use flashify with the img file. Flash the boot option.
{
"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"
}
mgbotoe said:
Will be nice if you can provide two different build. One without all the fancy things that some people wont have use for, such as overclocking, close to stock as possible but still provide stability, smoothness, and better battery life.
Some kernel makers just slap everything they can onto a kernel and in the long wrong, it is simply instable or provide hicups (that they will never own up to lol)
Click to expand...
Click to collapse
I agree with this wholeheartedly. I personally loved leanKernel on my Note 3 - all the latest fixes and improvements without 40000 things that only crazy experimenters and overclockers would use. I'd love a solid, lean, and mean daily-driver kernel.
twistedumbrella said:
https://goo.im/devs/playground/trltetmo/kernel/. So what should be included? You are welcome to cast your vote for how this kernel evolves.
Click to expand...
Click to collapse
If you could somehow throw in faux sound support that would be awesome .. I miss raising my volume just a bit for alarms...
Anyways Thanks a lot bro
siraltus said:
I agree with this wholeheartedly. I personally loved leanKernel on my Note 3 - all the latest fixes and improvements without 40000 things that only crazy experimenters and overclockers would use. I'd love a solid, lean, and mean daily-driver kernel.
Click to expand...
Click to collapse
Ironically, modifying imoseyon's kernels was how I first learned to build. I took his and added those one or two additional things I found somewhere else and wanted to use. Right now, I am working on getting intellidemand updated for this kernel, but I am only looking to get a few options that really work well so if there are better, let me know.
For the TCP congestion avoidance, it appears that enabling advanced options somehow broke selection. It appears to work just fine, but that troubles me. I don't want to force a setting for that, but if it comes down to it, I may have to limit the options.
Veno, from some documentation I've recently read, was the optimal option for mobile network performance. I believe it was reno that was best for wifi performance, but I have to go back and read up again.
I added some code for fast charge to be verified, but the layout is much different than most Samsung phones, so I won't know if it works until I attempt to blow up my phone.
{
"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"
}
Code:
*** Disclamer
Please behave responsibly and avoid thermonuclear war. I am
not responsible for any bricked devices, etc.
Introduction
This is Zest Kernel. It's an optimized kernel for our device which includes a few nifty features. Built, on every security update, you'll have the best of the best. Features will be listed below and shared, to the most of my ability, across all my supported devices. This isn't just my kernel it's yours too - request any features you like and I'll try to add them in. However, I'm also busy with studies so please don't ask for dumb stuff.
Click to expand...
Click to collapse
Images
Possibly the fastest kernel for our device, here's an AnTuTu benchmark from a fellow user on BLOD (four cores only):
Click to expand...
Click to collapse
Features
Built on UBERnaro toolchain
PaX security commits
DTS Android port commits
@franciscofranco 's battery optimizations
@UltraM8 's SLIMBUS modifications
High tickrate to avoid jitter
My hi-res audio backports
Fauxsound audio gain control
Kali Netunter HID and aircrack-ng support
Backported features for NexusPieX
Click to expand...
Click to collapse
Installation instructions
* Flash via TWRP, or Franco Kernel Manager
* Enjoy!
Click to expand...
Click to collapse
Download
Latest is on my website, all versions available at ftp://ftp.lasterhub.me.
Click to expand...
Click to collapse
FAQ
PM me in XDA's Google TG group.
Click to expand...
Click to collapse
Special Thanks To
Code:
* @franciscofranco for his kernel base
* @Skittles9823 for LMK values
XDA:DevDB Information
Zest Kernel Projecc, Kernel for the LG Nexus 5X
Contributors
LazerL0rd
Source Code: https://gitlab.com/ZKP/bullhead
Kernel Special Features: Fastest kernel for the Nexus 5X (bullhead)
Version Information
Status: Stable
Created 2018-03-29
Last Updated 2019-02-16
Reserved
Gpu can be overclocked with this kernel?
Ryder. said:
Gpu can be overclocked with this kernel?
Click to expand...
Click to collapse
No, would you like that though? I can try include in the next release.
Personally, I find GPU Performance Profiel to be sufficient. You can enable in a Kernel Manager I advise FKM (franco kernel manager) as my kernel supports his performance profiles.
It looks really interesting, will test it right now.
For feature request I will ask only one thing : more battery as it's the main problem of this device , the next must come after.
Thanks for your work and be brave for your studies!
LazerL0rd said:
No, would you like that though? I can try include in the next release.
Personally, I find GPU Performance Profiel to be sufficient. You can enable in a Kernel Manager I advise FKM (franco kernel manager) as my kernel supports his performance profiles.
Click to expand...
Click to collapse
Yes, i would like that, for gaming. I prefer only the overclock, not a performance profile
Update released! Bug fixes and cleaned up some code.
Any chance to add sweep or double tap to lock screen? thx
Is it OC by default or just possible to OC. Would rather appreciate if on default clocks as default.
---------- Post added at 10:46 PM ---------- Previous post was at 10:45 PM ----------
Aaand, thanks a ton for giving more hope and support for our beloved Bull.
Ryder. said:
Yes, i would like that, for gaming. I prefer only the overclock, not a performance profile
Click to expand...
Click to collapse
Well there's more than one factor when gaming, CPU also counts. I was advised by @frap129 not to OC the graphics as it'll cause too many hearing issues. The OC'd CPU may improve your gaming.
mosta00 said:
Any chance to add sweep or double tap to lock screen? thx
Click to expand...
Click to collapse
I can try in the next beta update however personally I strongly dislike this feature.
jugoslavpetrovic said:
Is it OC by default or just possible to OC. Would rather appreciate if on default clocks as default.
---------- Post added at 10:46 PM ---------- Previous post was at 10:45 PM ----------
Aaand, thanks a ton for giving more hope and support for our beloved Bull.
Click to expand...
Click to collapse
The OC clocks are set if you use the performance profile within the governor. But during the normal (balanced) profile the only OC bit is maximum clock speed. This can of course be overrided via a Kernel Manager but I'd advise for it to be left.
And, your welcome ?
First of all, just want to thank you for this kernel. Seems to be running extremely well so very nice job on this. Much appreciated :good:
I have 2 questions/requests:
1. I noticed that in the little cluster ""hispeed_freq" is set to 0. I just wanted to confirm that this is correct since I've never seen this set to 0 before in any profile that I can recall.
2. If you haven't already, could you please add disable force encryption to the kernel? I didn't see this listed in the posted features. Thank you.
Thanks again for this kernel. Really liking it a lot so far
Lughnasadh said:
First of all, just want to thank you for this kernel. Seems to be running extremely well so very nice job on this. Much appreciated :good:
I have 2 questions/requests:
1. I noticed that in the little cluster ""hispeed_freq" is set to 0. I just wanted to confirm that this is correct since I've never seen this set to 0 before in any profile that I can recall.
2. If you haven't already, could you please add disable force encryption to the kernel? I didn't see this listed in the posted features. Thank you.
Thanks again for this kernel. Really liking it a lot so far
Click to expand...
Click to collapse
1) Yeah, it's meant to be like that. My kernel uses a Franco-style governor profile with my own changes for performance. There are many different ways to use governor profils and this style uses input as a base to up the CPU.
2) I believe forced encryption is disabled already, I can add it to the features list. For me it's more of a security flaw than a feature though, lol.
@LazerL0rd - One question. By "smoother LED notifier" do you mean the LED animation that jollakernel has which starts sloooowly from nothing to the right color? I'm asking because I dislike jolla's (and Shadow Kernel's) implementation. I like it as shown in this video which is how past kernels such as Phasma had it.
LazerL0rd said:
2) I believe forced encryption is disabled already, I can add it to the features list. For me it's more of a security flaw than a feature though, lol.
Click to expand...
Click to collapse
Yeah I never understood why you would want to not use encryption. Benchmarks even show there is no real life advantage in speed so you just lose security.
LazerL0rd said:
1) Yeah, it's meant to be like that. My kernel uses a Franco-style governor profile with my own changes for performance. There are many different ways to use governor profils and this style uses input as a base to up the CPU.
2) I believe forced encryption is disabled already, I can add it to the features list. For me it's more of a security flaw than a feature though, lol.
Click to expand...
Click to collapse
1) Thanks for the clarification
2) I actually agree .
Benjamin_L said:
Yeah I never understood why you would want to not use encryption. Benchmarks even show there is no real life advantage in speed so you just lose security.
Click to expand...
Click to collapse
Maybe there is a real life battery drain using encryption.
nirogu325 said:
@LazerL0rd - One question. By "smoother LED notifier" do you mean the LED animation that jollakernel has which starts sloooowly from nothing to the right color? I'm asking because I dislike jolla's (and Shadow Kernel's) implementation. I like it as shown in this video which is how past kernels such as Phasma had it.
Click to expand...
Click to collapse
I couldn't find the commit for Phasma's one but if you could provide it for me I'll have a look. I have mine based off jolla's one but I changed it a bit to be less slow.
jugoslavpetrovic said:
Maybe there is a real life battery drain using encryption.
Click to expand...
Click to collapse
Very small extra drain with the ARM optimizations I have in my defconfig (and so do quite a few other kernels). FBE (file-based) uses a bit more on the first unlock but then after it's fine. The battery drain isn't noticiable.
Another update today! This time it's coming with audio driver improvements, tell me what you think!
Sorry for the delay in adding requested features, I'm trying to build my kernel for a few other devices so time is short atm. They're coming soon though
LazerL0rd said:
Another update today! This time it's coming with audio driver improvements, tell me what you think!
Sorry for the delay in adding requested features, I'm trying to build my kernel for a few other devices so time is short atm. They're coming soon though
Click to expand...
Click to collapse
Awesome. Just added IceSound this morning so perfect timing.
Thank you.
Welcome to Quantic a Kernel built specially for Redmi k30 PRO/ POCO F2 Pro codename: lmi
One of the most used kernel on Custom ROMS on Cepheus chosen by developers and one of the most battery friendly on Redmi k20 Pro community
/* I'm not responsable for any damage on your device, for X or Y reason, also I'm not responsable if you loose your alarm and got fired and also the thermonuclear war, anything like that, installing this kernel you renounce to make me responsable of any unwanted behavior of your device */
/*Compatible ONLY with Android 11 (Excluding MIUI)*/
Hi everyone, I want to introduce you my new kernel named Quantic-Kernel, this is my personal build kernel with my prefered features. Hope everyone enjoy it and I'll be maintaining it so people can used it with their preferred AOSP ROM(See details below)
FEATURES
Fixed Camera not working on AOSP ROMs
Reduced logging events
Deleted Focaltech touch testing driver
Swapped scheduler from WALT to Pure PELT (No google implementation)
Enabled ZRAM up to 2GB with lz4 compressor
Upstreamed lz4 compressor
Removed log events on drm by XiaoMi
Android Binder tweaks
ion and iommu rewrittes by kerneltoast
Using new efficient minimum CPU Frequencies
Deactivated CAF CPU Boost following MIUI stock kernel parameters
Deactivated MSM_Performance
FIX CPU Capacity issues
Frame commit, touch request, display rendering and drm are processed using big cores to achieve performance at the lowest energy consumption
Cleaned up XiaoMi code from Android 10
WARNING: This kernel is a forward port of the old MiCode release from Xiaomi (from sm8250.0 tag to SMxx50.0 tag) with some missing stuff reversed by custom code, which can lead into unwanted and NOT reported bugs, be careful, this kernel is a release for people that wan't to test new and distinct development stuff and to have a little preview of what we could achieve with a newer source from XiaoMi, PLEASE KINDLY REVIEW BUGS SECTION.
INSTALLATION PROCEDURE
Make a TWRP backup of BOOT and DTBO partitions
Flash Quantic-Kernel_rX.zip
Reboot to system
Enjoy it
BUGS:
WiFi broken
Some people may experience that mic is not working on CALLS (only happens on dialer app)
NOT WORKING ON MIUI A11 ?
DOWNLOAD HERE: https://github.com/Official-Ayrton990/android_kernel_xiaomi_sm8250/releases/tag/r3.1
TELEGRAM CONTACT
https://t.me/aicplmi <-- Discussion group for support
Thanks List
To kdrag0n
To kerneltoast
To alk3p
To @TeamMex
To Dynescape
SCREENSHOTS ATTACHED BELOW
XDA:DevDB Information
Quantic Kernel, Kernel for the Redmi K30 Pro
Contributors
Ayrton990
Source Code: https://github.com/Official-Ayrton990/android_kernel_xiaomi_sm8250 (branch QK-eleven)
Kernel Special Features:
Version Information
Status: Alpha
Current Beta Version: r1
Beta Release Date: 2021-02-26
Created 2021-02-26
Last Updated 2021-07-19
You like my work? gift me a coffee by PayPal
Or you can simply hit the like (thanks) button to promote me on XDA Forums
Reserved 2
@ poster
Great Work, been awaiting a custom kernel to calm my itch abit, looking forward to seeing this progress, installing it on Octavi OS rn, ill check back with a review
efinityy said:
@ poster
Great Work, been awaiting a custom kernel to calm my itch abit, looking forward to seeing this progress, installing it on Octavi OS rn, ill check back with a review
Click to expand...
Click to collapse
Didn't boot on Octavi OS, Didnt have time to pull a kmesg, I'll get to it this evening
Great work, hope it will be completely finished soon. Thanks
OnT: works great on latest derpfest rom, except for wifi ofcourse. UX feels alot smoother and battery drain on standby is notably reduced.
efinityy said:
OnT: works great on latest derpfest rom, except for wifi ofcourse. UX feels alot smoother and battery drain on standby is notably reduced.
Click to expand...
Click to collapse
Thanks for feedback, mate
THREAD CLEANED
@dhaern @efinityy I read the messages and while I understand what you both were trying to say and where you guys are coming from, but please make sure that you're mindful of words you use to make sure they're not coming off as demanding, offensive, hateful, mocking.. well, you get the drift. I implore you both to re-read Rule 2 of the Forum Rules.
This is just a friendly reminder to keep it civil, on-topic and refrain from putting fuel to fire by responding to posts that you think don't belong in the thread. Just report if you feel something isn't right and let us take care of it for you, so that we can make your experience on the forum better.
Now let's all take a deep breath, and get back on topic, shall we? Thanks guys!
Regards,
shadowstep
Forum Moderator
realy want to try this kernel but will be wifi fixed soon?
Thanks fot your effort dev.
You are only one who keep developing kernel for poco f2 pro
I have request I don't if it could be done or not
Many users complain green tint and black crush display and I figured out it may be something to be edited in display refresh rate and total pixels (like CRC app for overclocking refresh rate for windows)
when aggressive refresh rate is done or excess of total pixels added the screen turns to defects like tints and color crush
So if you can decrease total pixels untill reached it is minimum limit it will solve these defects for poco f2 pro displays
magaedy said:
Thanks fot your effort dev.
You are only one who keep developing kernel for poco f2 pro
I have request I don't if it could be done or not
Many users complain green tint and black crush display and I figured out it may be something to be edited in display refresh rate and total pixels (like CRC app for overclocking refresh rate for windows)
when aggressive refresh rate is done or excess of total pixels added the screen turns to defects like tints and color crush
So if you can decrease total pixels untill reached it is minimum limit it will solve these defects for poco f2 pro displays
Click to expand...
Click to collapse
This sounds interesting, as this is an issue i have alot, especially with DC dim turned on, spotify for example has a green hue from top to bottom, fading the further down you go
EDIT; upon looking through the commits i can see some fiddling is done with the screen, hopes are high
efinityy said:
This sounds interesting, as this is an issue i have alot, especially with DC dim turned on, spotify for example has a green hue from top to bottom, fading the further down you go
EDIT; upon looking through the commits i can see some fiddling is done with the screen, hopes are high
Click to expand...
Click to collapse
Where this fiddling is done and by whom ?
magaedy said:
Where this fiddling is done and by whom ?
Click to expand...
Click to collapse
in the OPs source github link.
efinityy said:
in the OPs source github link.
Click to expand...
Click to collapse
guide us, master, and show directly path for our dream
Commits · Official-Ayrton990/android_kernel_xiaomi_sm8250
CAFest Kernel for Xiaomi-SM8250 based on LA.UM.9.12.r1-08000-SMxx50.0 Tag - Commits · Official-Ayrton990/android_kernel_xiaomi_sm8250
github.com
there you go
{
"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"
}
efinityy said:
Commits · Official-Ayrton990/android_kernel_xiaomi_sm8250
CAFest Kernel for Xiaomi-SM8250 based on LA.UM.9.12.r1-08000-SMxx50.0 Tag - Commits · Official-Ayrton990/android_kernel_xiaomi_sm8250
github.com
there you go
View attachment 5251009
Click to expand...
Click to collapse
and with uat help?
New Quantic Kernel Update is out with bugfixes:
Changelog
- Fixed broken WiFi
- Fixed mic on audio calls
- Upstreamed LTS to 4.19.188 (Learn why is important to merge LTS to Linux Kernel: https://source.android.com/devices/architecture/kernel/releases?hl=en#long-term-stable-kernels)
- Upstreamed CAF Tag to: LA.UM.9.12.r1-11000-SMxx50.0
- Latency improvements on UI
- f2fs substantial speed improvements
- Support for TTL data fixation
- Added FOD command fixation on dtbo. FOD now should be reliable than before.
- WALT Scheduler tweaked to reduce latency through tasks
- Affine touchscreen IRQs to the prime CPU cluster
- Optimize interrupt dispatcher by assigning pm_qos as low latency and to avoid cpu idle on interrupts requests.
- Set BBR as default algorithm for TCP Congestion
- Drop some non-eficient and unused defconfigs
- Fix some dynamic allocations
- Swtiched to SLMK to avoid apps closing from the background
- Fix battery drain present when locking device with LTE only enabled by fixing an unbounded workqueue
- Use LZ4 algorithm for ZRAM and set by default 2GB instead of 3GB
- Fix a Important race condition on DRM to avoid security exploits
- Disabled AUDIT as selinux is no more dependent of it.
- Using SD865+ GPU Max frequency
- Reduced logs to the minimum to reduce performance overhead
- Imrpoved UFS performance by optimizing current driver and scrapping out XiaoMi's jank code.
Download here: https://github.com/Official-Ayrton990/android_kernel_xiaomi_sm8250/releases/tag/r1
Donate here: paypal.me/ayrton990
Telegram group for support: t.me/aicp_lmi
Regards, Ayrton!
Doesn't work with hentai os. Doesn't boot.
wifi work now? sombody on shapeshift 2.4 ? work?