Disclaimer:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* blah blah blah you get the point.
*/
1# post: Disclamer - special thanks
2# post: Current release & source
3# post: FAQ - bugs - future features
Donator List: (huge thanks for support)
here
Suggested kernel control app: trickstermod
I don't know if it works because i don't own the device but i have got ville which is pretty similar
[GUIDE]How to compile a kernel
Credits and Thanks:
dsixda, showp1984, ngtools, faux123, Christopher83, franciscofranco, msm8960 team, jrior001
XDA:DevDB Information
AOSP Bubba Kernel, Kernel for the Sprint HTC EVO 4G LTE
Contributors
rmbq
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2014-07-26
Current Beta Version: 24 Apr
Beta Release Date: 2014-04-24
Created 2014-04-23
Last Updated 2014-07-26
Reserved
Features:
Based on linux 3.4.99
Compiled with linaro toolchain 4.9.1 2014.07 optimized for cortex-a15
Linaro -O3 optimization
avaiable CPU governors: interactive, ondemand, performance, powersave, intellimand, intelliactive
avaiable GPU governors: ondemand, performance, simple
avaiable schedulers: row, deadline, noop, cfq, bfqv7r4, fiops, sio
Sleepy Plug
NTFS read & write support
exfat support
UTF8
Voltage control
Sweep2Wake
Double tap 2 wake
Pocket detection
Intelli-thermal
zRam with LZ4 compression
zCache with LZ4 compression
CPU OC to 1.7 GHz
GPU OC to 512MHz (3D) and 320MHZ (2D)
Faux sound control v. 3
Improved alghorithm: SHA1, AES, SQRT, lib/string (glibc version), lib/memcopy (glibc version), XOR (neon)
dynamic fsync by faux123
fastcharge
powersuspend driver (replace earlysuspend)
KCAL control (RGB)
heavly patched memory allocators, RWSEM and mutex (take a look at my github, too many changes to make a list here)
Changelog:
Code:
[JUL 26 2014]
Revert "prctl: adds the capable(CAP_SYS_NICE) check to PR_SET_TIMERSLACK_PID."
Revert "prctl: adds PR_SET_TIMERSLACK_PID for setting timer slack of"
add qseecom support
some defconfig changes
cpufreq: revert CAF's cpu policy save code
sched/cpuidle: reduce IPI storm. Backport upstream 3.16
mm, hugetlb: improve page-fault scalability
mm: per-thread vma caching
update compiler to linaro toolchain 4.9.1 2014.07 optimized for cortex-a15
update to 3.4.99
added KCAL control by faux and fixed by me
add F2FS support
Revert "msm: htc: update mem mapping"
[JUL 17 2014]
update to 3.4.98
sync with cm
sync with codeaurora/kk_2.7-stable
update sleepy_plug
bfq: BFQ-v7r5
bugfix from google (see github)
[JUN 29 2014]
Remove JustArchi GCC flags cos they are unstable
update to 3.4.95
sync with CM
sync with codeaurora/kk_2.7-stable
ext4: Speedup WB_SYNC_ALL pass called from sync(2)
[JUN 19 2014]
update compiler to linaro toolchain 4.9.1 2014.06 optimized for cortex-a15
update to 3.4.94
remove -fdata-sections GCC flag (cause of reboot issue)
sync with CM
sync with codeaurora/kk_2.7-stable
updated sleepy_plug
[JUN 09 2014]
sync with codeaurora/kk_2.7-stable
memset patch to fix bootloops
[JUN 08 2014]
3.4.92
reverted some KGSL CAF patches
removed -ftrace flag
sync with CM
improved int_sqrt algorithm
update bfq to v7-r4
[MAY 28 2014]
sync with codeaurora/kk_2.7-stable
update sleepy_plug
cpufreq: ondemand: Calculate load_at_max_freq based on current policy->max
sched: add do_avg_nr_running to fix avg_nr_running
increase base address
revert 24 May changes
[MAY 24 2014]
Increase ramdisk_offset
[MAY 19 2014]
update to 3.4.91
merge codeaurora/kk_2.7_rb1.38
update bfq to v7-r3
sleepy_plug now supports quadcore CPUs
fix headset support (CM)
new GCC flags
update compiler
[MAY 03 2014]
block: support volname for HTC devices with proc/emmc support
[MAY 02 2014]
compiled with Linaro GCC 4.9.1 optimized for cortex-a15
sync with CM
update devices_htc from Jet jb 4.3 kernel
update headset driver from Jet jb 4.3 kernel
update memory mapping (more RAM avaiable)
update pn544 driver
update bma250 driver
[APR 29 2014]
update to 3.4.88
sync with codeaurora/kk_2.7-stable
some other CAF patches
[APR 25 2014]
fix s2w
[APR 24 2014]
added s2w and dt2w with pocket detection (from torched sources)
enable BLN
[APR 23 2014]
first release
If you like my work please consider making a donation, I spend almost all my free time on making this kernel the best
i'll buy another phone to continue to support the android development!
Download:
androidfilehost folder: http://www.androidfilehost.com/?w=files&flid=14092
normalToQV: http://www.androidfilehost.com/?fid=23501681358544069
(if you don't see the new version just wait some minutes, it's uploading)
Kernel Source: Github
Reserved
Q: What is QV version?
A: QV means "qualcomm voltages". qualcomm made a patch and stuck all voltages to 1150mv to improve stability. QV version has got all 1150 mv for each freq (like older 3.4 kernels).Q: I plugged in my pen drive but i can't found it
A: look in /mnt/usbdisk folder.Q: What's and how i enable/disable fastcharge?
A: with fast charge an USB charger will recognized as AC charger. it won't charge your phone faster with an AC charger. it may not charge your phone faster with an USB charger.
with the usb cable UNPLUGGED edit /sys/kernel/fast_charge/force_fast_charge:
0 -> disable
1 -> enable
than plug in the cableQ: i've got random reboots, what do you need?
A: first read here
write this info:
kernel version
ROM
governor
scheduler
undervolted? if yes don't undervolt
QV version? if no use it
last_kmsg
Q: what's BLN and how i enable/disable it?
with BLN on when you received a notify the soft key will blink.
to enable/disable edit /sys/class/leds/button-backlight/blink_buttons:
0 -> disable
1 -> enableQ: what's s2w and how i enable/disable it?
Sweep2wake allows you to wake up your device by swiping your finger across the capacitive buttons from left to right. Swiping from right to left will put it back to sleep (sweep2sleep).
to enable/disable edit /sys/android_touch/sweep2wake:
0 -> disable
1 -> enableQ: what's dt2w and how i enable/disable it?
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping the capacitive buttons.
to enable/disable edit /sys/android_touch/doubletap2wake:
0 -> disable
1 -> enableWhat's sleepy_plug and how can i activate/deactivate it?
sleepy plug it's an hotplug driver (it decide when turn on the second core) i wrote. it's an experimental driver and it may have got performance problem. if you notice some decrease in performance report it.
to enable/disable edit /sys/module/sleepy_plug/parameters/sleepy_plug_active:
0 -> disable
1 -> enableInstall instruction:S-OFF:
- flash the zip in recovery
- wipe caches (optional)S-ON:
Windows & Linux:
flash kernel zip.
stay in recovery after flashing the zip
from command prompt (ot terminal) on PC:
Code:
adb pull /tmp/newboot.img
adb reboot-bootloader
fastboot flash boot newboot.img
fastboot reboot
OLD S-ON INSTRUCTION:
Linux:
- flash awesome kernel cleaning script: http://d-h.st/HDi (optional)
- flash the zip in recovery (obsolete, for older kernels with modules outside built outside)
- use zImage switcher to make a new boot.img
-
Code:
fastboot flash boot newBoot.img
Windows: (don't ask me how it works or everything else, i don't know and they have got tutorials on their site)
- repack your ROM boot.img with mine zImage using Virtuous Ten Studio http://www.virtuous-ten-studio.com/index.php/downloads
-
Code:
fastboot flash boot newBoot.img
Bugs 3.4:
None
If you want to use my kernel for your ROM just use it and cit me in credits
This is pretty sick gonna give it a whirl as soon as I'm free, but I had thought that HTC hasn't released our kernel to the devs so this will probably brick our devices since it's a port right ??
the kernel
Sent from my EVO using xda app-developers app
ultimatelegend1 said:
This is pretty sick gonna give it a whirl as soon as I'm free, but I had thought that HTC hasn't released our kernel to the devs so this will probably brick our devices since it's a port right ??
the kernel
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
i don't know what you are saying!
you have got official CM support (idd you have got, for example, this ROM http://forum.xda-developers.com/showthread.php?t=2633324 that is AOSP). this kernel is for aosp so, what's the problem?
Nice work MBQ! thanks a lot for this I'm going to be using it tonight
Sent from my EVO using Tapatalk
U see after the sense 5 4.3 update our phones received the partition layout changed and with it came an updated kernel but since HTC hasn't released the new kernel this could possibly brick phones on the new layout but it might work with phones on the old layout, listen I'm no expert if anyone here on the new partition flashes this plz do report back so that we can now if this is compatible
Sent from my EVO using xda app-developers app
ultimatelegend1 said:
U see after the sense 5 4.3 update our phones received the partition layout changed and with it came an updated kernel but since HTC hasn't released the new kernel this could possibly brick phones on the new layout but it might work with phones on the old layout, listen I'm no expert if anyone here on the new partition flashes this plz do report back so that we can now if this is compatible
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
this kernel doesn't change the partition layout
P.S. you can't brick the phone flashing a kernel
I didn't say that it would change the layout , and thanks for the new info I thought that flashing an incompatible kernel could possibly brick a device
Sent from my EVO using xda app-developers app
Will definitely give this a go tomorrow and report back with results.
Sent from my SPH-L720 using Tapatalk
I couldn't wait until tomorrow. I first gave this a run using a nandroid of an OmniRom build, and I noticed that there are a few things that work or don't work well/at all. I tried again on a clean flash, and achieved the same results.
Working
USB Fast charge (yay)
Overclock
Not working
Sweep2whatever
Doubletap2wake
Custom governors not available
Custom schedulers not available
Not Working Well
I noticed that it is causing screen tearing during the transitions.
I experienced trouble connecting to my car bluetooth, but I'm not sure if that's rom related.
Sent from my HP Pavilion g6 Notebook PC using Tapatalk
new version is up! with s2w dt2w and BLN
knock knock and s2w aren't working for me
rmbq said:
new version is up! with s2w dt2w and BLN
Click to expand...
Click to collapse
About to test right now.
aarsyl said:
I couldn't wait until tomorrow. I first gave this a run using a nandroid of an OmniRom build, and I noticed that there are a few things that work or don't work well/at all. I tried again on a clean flash, and achieved the same results.
Working
USB Fast charge (yay)
Overclock
Not working
Sweep2whatever
Doubletap2wake
Custom governors not available
Custom schedulers not available
Not Working Well
I noticed that it is causing screen tearing during the transitions.
I experienced trouble connecting to my car bluetooth, but I'm not sure if that's rom related.
Sent from my HP Pavilion g6 Notebook PC using Tapatalk
Click to expand...
Click to collapse
about Sweep2whatever Doubletap2wake new version should fix them.
Custom governors not available & Custom schedulers not available: strange, which app are you using?
I noticed that it is causing screen tearing during the transitions.: could be try to use interactive governor
I experienced trouble connecting to my car bluetooth, but I'm not sure if that's rom related.: on ville it's working so i don't think it's kernel related (same chip)
rmbq said:
about Sweep2whatever Doubletap2wake new version should fix them.
Custom governors not available & Custom schedulers not available: strange, which app are you using?
I noticed that it is causing screen tearing during the transitions.: could be try to use interactive governor
I experienced trouble connecting to my car bluetooth, but I'm not sure if that's rom related.: on ville it's working so i don't think it's kernel related (same chip)
Click to expand...
Click to collapse
Ok....update.
I flashed today's build (QV version), and here are the changes.
- The different governors now show up.
- Sweep/Doubletap options don't show up in TricksterMOD.
- I tried to force sweep2wake to work through Kernel Tuner, but the phone froze after I applied the new settings.
- I didn't notice your post soon enough to try the interactive governor. I will post an update soon.
aarsyl said:
Ok....update.
I flashed today's build (QV version), and here are the changes.
- The different governors now show up.
- Sweep/Doubletap options don't show up in TricksterMOD.
- I tried to force sweep2wake to work through Kernel Tuner, but the phone froze after I applied the new settings.
- I didn't notice your post soon enough to try the interactive governor. I will post an update soon.
Click to expand...
Click to collapse
have you got these files?
/sys/android_touch/sweep2wake
/sys/android_touch/doubletap2wake
rmbq said:
have you got these files?
/sys/android_touch/sweep2wake
/sys/android_touch/doubletap2wake
Click to expand...
Click to collapse
I'm a little busy right now, and I have already restored my Sense nandroid, so I can't check. I'm quite a busy bee when it comes to roms, so I will get back to you soon.
rmbq said:
have you got these files?
/sys/android_touch/sweep2wake
/sys/android_touch/doubletap2wake
Click to expand...
Click to collapse
Yes those two files are there.
when setting either of them to 1, when trying to us it my phone reboots.
Also no changes made after reboot seem to stick
Sent from my EVO using Tapatalk
shadowxaero said:
Yes those two files are there.
when setting either of them to 1, when trying to us it my phone reboots.
Also no changes made after reboot seem to stick
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
can you give me a last_kmsg?
Related
The goal of this kernel is above all stability with the secondary goals of increased performance and increased battery life. I use this phone for several hours a day for work and therefore it must be reliable. I am not focusing on providing a million options for governors, etc. In addition to those main goals of the kernel, I have an additional secondary goal of removing as much HTC code as possible from the kernel.
This is based on the 2.04 kernel source release from HTC with a huge number of modifications. Thanks to faux123, showp, harsh, mdeejay, zarboz and dsb9938 whose kernels I have pulled some commits from.
The unique features of this kernel are:
New init.d scripts to allow some tweaking without needing any 3rd party apps
* See the next post for details.
Replaced HTC's mpdecision with a new custom hot-plug driver that I created:
* This hot-plug driver is more aggressive about bring cores on and off-line to match the load on the system.
* Bringing cores online earlier makes your phone more responsive / smooth.
* Taking cores offline earlier improves battery life.
* It ramps up very quickly on resume to avoid lag.
Replace HTC's thermald with a new custom thermal driver that I created:
* Unlike all other thermal drivers, it uses "trip-points" to let the phone tell the kernel when it is overheating. The other thermal drivers poll every X ms and read the temperature instead.
* By using trip-points, there is 0 battery consumption unless the phone is overheating.
* By using trip-points, there is an instant reaction to temperature changes.
* It's probably nearly impossible to cause thermal shutdown without being in a desert!
Replaced HTC's bluetooth drivers with Code Aurora Forums (CAF) version.
Replaced HTC's lightsensor table with one that is more sensible and that matches what other devices use. If you have custom auto-brightness settings, you'll probably need to tweak them after installing this kernel.
There are many additional changes to boost performance and battery life:
* Linaro -O3 compiled (Linaro 4.8).
* Overclocking from mdeejay's kernel.
* Underclocking to 192MHz.
* I disable tons of HTC debugging crap left enabled and needlessly consuming battery.
* Improvements to the core locking code of the kernel.
* Patches that transform traditional locks into RCU backed data structures.
* CAF version of the ondemand and conservative governors.
* hsic wakelock changes from dsb9938's kernel.
* CAF changes to power management to sleep faster and waste less CPU during suspend.
* Improved code for moving data to/from user-space and manipulating strings within the kernel.
Other features:
* Include all mainline Linux changes to keep up-to-date on bug fixes.
* Voltage control (faux123) to allow user-space under-volting.
* BFQ I/O scheduler.
* CAF lowmemorykiller.
* Force fast charge.
Links
A link to each version is included in the changelog entry. Scroll down to the changelog to download the latest version.
Source (GitHub):
* Kernel source
* Merging of upstream into the stock kernel
* Build tools
Installation Instructions:
If you are S-OFF you can flash the update.zip in recovery.
If you are S-ON, then after you flash the update.zip in recovery then, while still in recovery, you must run
Code:
adb pull /tmp/boot.img
<reboot into bootloader>
fastboot flash boot boot.img
Changelog:
Version 2.0.41: August 25, 2013: Linux 3.4.58, HTC colour "enhancement"
* Merged Linux versions 3.4.53 - 3.4.58
* Added the ability to enable / disable the HTC colour enhancement (this lets you see if you like it or not)
Version 2.0.38: July 7, 2013: Linux 3.4.52
* Linux version 3.4.51 / 52 merged in
* Reverted a small change to the PWM values used for the display (it wasn't giving any value so why change ti)
Version 2.0.34: June 24, 2013: colour enhancement, fixes, debug messages
* Toned done yet more HTC debugging messages
* Enable UTF-8 codepage support for Windows file-systems
* Fix error in HTC's light-sensor calibration table (overflows the 16-bit number they are using)
* Avoid buffer overflow in acdb driver
* Remove HTC's colour enhancement gamma correction (beaups)
Version 2.0.32: June 15, 2013: linux 3.4.49, scheduler & mutex improvements
* Linux 3.4.49
* Three scheduler performance improvements
* Move to more standard and slightly faster mutex implementation
Version 2.0.30: June 8, 2013: linux 3.4.48, small fixes
* Linux 3.4.48
* Fix CVE-2013-2595
* Decrease latency in cpufreq frequency changes
Version 2.0.27: May 26, 2013: init.d governor, 3.4.47
* Ability to specify the cpufreq governor at boot time (see second post).
* Linux 3.4.47
* Remove an annoying HTC debugging message
Version 2.0.26: May 23, 2013: init.d tweaks, 3.4.46, no default undervolting
* Added PVS information to /proc/cpuinfo in case you wanted to knoiw what it is for your phone.
* Linux upstream version 3.4.46
* Improve how I set the CPU frequences to safe levels for boot without having to reset them every time a core is hot-plugged in.
* New init.d scripts for some common tweaks (see post #2).
Version 2.0.23: May 13, 2013: Lightsensor fix, 3.4.45, faster freq. changes:
* Fix an error transcribing the lightsensor ranges into the source.
* Update to Linux 3.4.45
* cpufreq: use a high priority to target new frequencies to allow faster changes under load
Version 2.0.20: May 12, 2013: Lightsensor, 3.4.44, undervolt for "fast":
* Use a new lightsensor table to get a more granular light reading If you have custom auto-brightness settings, you'll probably need to tweak them after installing this kernel.
* Update to Linux 3.4.44
* Undervolted for devices binned "fast" by -100mV.
* CAF fix for cpufreq driver.
Version 2.0.17: May 7, 2013: Linaro 4.8.0 build, minor CAF fixes:
* Moved to updated Linaro 4.8.0 based toolchain (theoretically faster, less battery likely it's unnoticeable)
* CAF: change boot-up order for cpufreq
* CAF BT: recover from a hardware error by resetting the device
Version 2.0.15: May 2, 2013: boot hang fix, 3.4.43, CPU frequencies, brightness, misc fixes:
* Linux 3.4.43
* Small fixes from CAF (bluetooth, usb)
* Restore the CPU frequences/voltages from 1.x.y kernels (previously I was using HTC's new tables)
* simple_plug: keep cores online during boot
* use the correct brightness ranges for our display (HTC cut off the lowest brightnesses).
* fix a race condition on boot with the binder kernel services
Version 2.0.9: April 23, 2013: 3.4.41 and small fixes:
* Linux 3.4.41
* Small fixes from CAF
* Clean up some more HTC crap in the kernel
Version 2.0.6: April 17, 2013: boot changes, linux 3.4.40:
* Linux 3.4.40 (upstream).
* Limit CPU speeds during boot to stock speeds.
* Enable the thermal driver 5 seconds into the boot (previously was 30 seconds).
* Small changes to the ramdisk from the 2.04 update (I forgot these before).
Version 2.0.3: April 15, 2013: on_demand, battery, HTC spew:
* HTC insists on adding more and more debugging messages to the kernel log. Clean these up.
* OnDemand: revert a CAF change I made and disable io_is_busy.
* Remove HTC's over-volting for CPUs binned anything other than nominal.
* defconfig changes to ease building the kernel for CM10.1 (no you can't use this one for CM10.1!).
Version 2.0.0: April 11, 2013: 2.04 (OTA) source drop:
* Updated to Linux 3.4.39
* Updated to HTC's release of 2.04 source
* cgroup permissions fix
* Otherwise the same as 1.2.6
* Note: After running this for a day, I feel like the battery is draining faster and the phone is hotter than it should be. I'm looking into that.
Changelog from 1.2.x
Version 1.2.6: April 4, 2013: ramdisk fix, lowmemorykiller, hsic wakelocks:
* Fix a problem where the ramdisk was no longer disabling mpdecision and thermald. This issue causes a very minor additional battery drain that has now be fixed (Thanks t1gartist!).
* CAF updates to lowmemorykiller.
* Reapply elkay's HSIC fixes by pulling the real commits from CAF (instead of his hand copied commits) which fixes two problems in his commits.
1.2.2: April 1, 2013: linux 3.4.38, lag fixes, bluetooth drivers, cleanup:
* Undo some dubious commits (or extra code included in unrelated commits, what I meant by "early mistakes"). I reexamined every commit in the kernel to decide whether to keep it or remove it.
* Bluetooth drivers are the current CAF msm-3.4 drivers.
* Additional CPU speed and governor information added in /proc/cpuinfo.
* Cleaner patching to upstream linux (see my github repo for the clean upstream patching).
* Linaro -O3 compilation was redone from scratch because there were some problems found by kern3l in the original patches I pulled, I wanted to ensure that there were no other problems so I redid the work myself.
Changelog from the 1.0.x series:
1.0.27: Mar 25, 2013: thermald, simple_plug
* Make the previous changes to simple_plug less aggressive about turning cores back off when applications force them online. We now detect that this has occurred and give the application 2 minutes to be in charge before we force the state back to what we want.
* Change thermald default throttling to be slightly less strict.
1.0.25: Mar 21, 2013: Linux 3.4.37, simple_plug, performance
* Linux 3.4.37
* simple_plug: add a verify mode (every 5 seconds => almost 0 cost) that fixes the state when apps bring cores on/off-line (e.g. kernel tuner).
* rwsem performance improvements
* CAF improvements (correctness, performance) of the power management layer
1.0.21: Mar 16, 2013: Linux 3.4.36
* Linux 3.4.36
* Small bug fixes from CAF
1.0.18: Mar 7, 2013: Linux 3.4.35
* Linux 3.4.35
1.0.17: Mar 4, 2013: Linux 3.4.34, Linaro 4.7-2013.02, thermald fix
* Linux 3.4.34.
* Linaro 4.7: stopped using 4.8 beta builds due to stability fears and lack of apparent benefit from it. The latest 4.7 drop back-ports some optimizations anyway.
* lowmemorykiller: switch to the CAF version of the low memory killer.
* Fixed several bugs in HTC's thermal driver that could cause the termal driver to miss thermal events.
1.0.15: Feb 26, 2013: Battery optimization, performance, thermal & hotplug improvements
* governor: make ondemand the default governor
* GPU: Very minor GPU overclock to 487MHz (from mdeejay).
* msm_thermal: react better when temperature decreases.
* simple_plug: be slightly less aggressive about bringing cores online.
* New suspend mode PM_SUSPEND_FREEZE
* Oprimization for RWSEM lock handoffs.
* RCU locking in cpufreq!
* Disable more HTC debugging code.
1.0.11: Feb 22, 2013: Battery optimizations, Linaro 4.8 build, update.zip format
* Disable HTC's PNP power manager and adaptive policy services (used for thermald / mpdecision which are already disabled).
* Turn off all the kernel code that was polling to compute the state needed for thermald / mpdecision.
* Turn off a bunch of HTC statistic collection and debugging that isn't needed and wastes battery.
* Linux 3.4.33: fixes a kernel memory corruption/hang in all 3.0 and 3.4 kernels
* Sparkco's 4.8 Linaro build is now being used to compile the kernel
* Moved to update.zip format with less commonly used modules moved to loadable modules.
1.0.8: Feb 19, 2013: Switch to different OC values
* Now using mdeejay's over/unclocking (hopefully solving the L2 cache corruption panic).
* thermal driver is less aggressive about throttling the phone with an additional early step down to stock speed
(50C => 1.5GHz, 75C => 1.3GHz, 83C => 918MHz, 90C => 384MHz).
* Linux 3.4.32 (although no changes that would affect our phone).
1.0.7: Feb 15, 2013: thermal driver no longer polls for state
* Linux 3.4.31.
* Now using the 2013-01 build of the Linaro toolchain.
* Major rewrite of the thermal driver to remove polling (now uses essentially no power).
* Tweaks to the hot-plug driver to reduce CPU consumed to reduce power consumed.
1.0.5: miscellaneous optimizations
* Optimization: use optimized memcpy for user-space copies
* Update to linux 3.4.30
* Tons more cleansing of excessive debugging output
* Use RCU_FAST_NO_HZ as caf claims to have found that this improves battery life
* More linaro -O3 fixes from kern3l via dsb
1.0.2
* cm3629 driver, removed power button pocket check (sounds like a good idea, doesn't work and is a likely candidate for an infrequent sensor drain coming from the proximity sensor not turning off).
* cm3629 remove some unused functionality.
* Two small fixes from kern3l via dsb9938's kernel.
* clean some log messages.
1.0.0
* Merge linux 3.4.29
* simple_plug: a new CPU hot-plug driver (default)
* msm_thermal: a new thermal throttling driver (default)
* faux123's intelli_plug (disabled by default)
* faux123's intellidemand governor (default)
* disable mpdecision and thermald in initrd
* dsb9938's overclocking tables, GPU fix and more -O3 changes
* optimizations/fixes from faux123's mako kernel
* Based on elkay's LK kernel which is based on dsb9938's kernel.
* Includes all elkay's HSIC fixes, but nothing beyond that.
* Linaro -O3 compilation (zarboz) and other compiler flags (dsb9938).
* Disabled remote assistance because that just creeps me out.
* NTFS and CIFS.
* Various optimizations and improvements (faux123's mako kernel, similar to dsb9938's pulls from there).
* Force fast-charge (dsb9938).
* Voltage control (faux123).
* Latest OnDemand and Interactive governors from faux123's mako kernel.
* Large set of scheduler fixes / improvements (faux123).
* Underclocking (but not overclocking right now) to 192 MHz.
* BFQ I/O scheduler (default).
* Cleaned up debugging to make the kmsg more useful.
FAQ
sweep2wake: I have no plans to add that to this kernel at this time.
FAQs
init.d tweaks
I really like Zarboz's goal of trying to get rid of the need for 3rd party apps to make the common changes that we want to make to some of the configurable parameters of the kernel. I created some scripts that run on boot (init.d) because I install my kernel so many times that I would go insane if I had to use an installer. By using these scripts and configuration files on the sdcard, I can just configure it once and keep installing away to my heart's content.
After installing this kernel, there will be:
/system/etc/init.d/99crpalmer
run at boot, even if you switch to another kernel. It is safe to leave this file there and to let it run as it only makes changes if the kernel contains "crpalmer" in the version.
The tweaks are:
CPU Frequencies
* Frequencies loaded from /sdcard/crpalmer-cpufreq-min and /sdcard/crpalmer-cpufreq-max
* Governor loaded from /sdcard/crpalmer-cpufreq-governor
* If you specify either or both of these frequencies, it will lock down all of the CPU frequency controls. I had to do this because HTC overrides them in a script that is run very late in the boot process (thanks HTC!).
* E.g. adb shell su -c "echo 192000 > /sdcard/crpalmer-cpufreq-min"
* E.g. adb shell su -c "echo 1728000 > /sdcard/crpalmer-cpufreq-max"
* E.g. adb shell su -c "echo interactive > /sdcard/crpalmer-cpufreq-governor"
Undervolting
* + or - value loaded from /sdcard/crplamer-uv
* The undervolting in 2.0.23 for FAST binned CPUs would be specified as:
* E.g. adb shell su -c "echo -100 > /sdcard/crpalmer-uv"
Lightsensor
* My light sensor changes didn't sound like they worked well for everyone. If you don't like them you can disable them by:
* E.g. adb shell touch /sdcard/crpalmer-stock-lightsensor
HTC Colour "Enhancement"
* If this file is present then the stock colour "enhancement" will be used, otherwise it will be disabled.
* Introduced in kernel 2.0.41.
** E.g. adb shell touch /sdcard/crpalmer-color-enhancement
My WIFI Won't Turn On
If your WIFI won't turn on then the most likely cause is that either you didn't flash the boot.img (e.g. not S-OFF) or your modules don't match the kernel. To figure out what's wrong, first boot the ROM after having installed my kernel. Second, verify that you are running my kernel by running
adb shell cat /proc/version
and seeing that it says crpalmer in (it should match the version that you think you installed, but at least saying crpalmer is a good start). Then do:
adb shell dmesg -c
(turn on wifi)
adb shell dmesg
and look for an error that says crpalmer in it (something like a module version mismatch error). If you see that, it should tell you the version number of the modules that are installed and the version of the kernel.
Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
Thanks for this. Looks good. :thumbup:
Sent from my ViperDNA
nice, moar kernel development :highfive:
welcome aboard
Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
So no modules to flash?
Sent from my HTC6435LVW using Tapatalk HD
idkwhothatis123 said:
So no modules to flash?
Click to expand...
Click to collapse
That's right. No need to flash the return-to-stock modules either.
Thank you for this! I also find it hilarious that you including instructions for benchmarking. To this day I still wonder why people actually care about benchmarks as they have little to no impact on real world performance.
Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
azndan2 said:
Thank you for this! I also find it hilarious that you including instructions for benchmarking. To this day I still wonder why people actually care about benchmarks as they have little to no impact on real world performance.
Click to expand...
Click to collapse
Self defense... I didn't want to deal with people getting 8K scores and blaming me.
Antutu is actually really useful for testing the thermal driver.
Very nice, does this have the latest changes that were just removed from elkays kernel? Also, could you add the lionheart gov?
Nice to see another kernel to choose from, I will give it a shot this weekend. Will you eventually put any you tweaks? Also, can this be flashed with FlashGui?
Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
orangechoochoo said:
Nice to see another kernel to choose from, I will give it a shot this weekend. Will you eventually put any you tweaks? Also, can this be flashed with FlashGui?
Click to expand...
Click to collapse
just tried, flashgui won't even let you flash it. Gotta wait till I get home I guess!
Sent from my HTC6435LVW using Tapatalk 2
Thanks for giving it a shot.
Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
codezzie said:
Very nice, does this have the latest changes that were just removed from elkays kernel? Also, could you add the lionheart gov?
Click to expand...
Click to collapse
I looked at elkays changes and it removes a background task that encourages a USB device to power down. This may or may not be a good thing. I'll see how elkay's testing goes before I pull in the change. If it goes well, I'll give it a try.
Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
orangechoochoo said:
Nice to see another kernel to choose from, I will give it a shot this weekend. Will you eventually put any you tweaks? Also, can this be flashed with FlashGui?
Click to expand...
Click to collapse
What tweaks? It.already has a lot of improvements...
Any idea what flashgui accepts as input?
I didn't see any mention of gpu tweaks so I didn't want to make assumptions, hence my question.
EDIT: I just noticed my autocorrect changed "gpu" to "you" in my post you responded to.
Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
crpalmer said:
Any idea what flashgui accepts as input?
Click to expand...
Click to collapse
Flashgui worked for me. Renamed file to "boot.img" and ignored the warnings. I like living on the edge. Booted up and shows this kernel version. Thanks for this.
Stay thirsty, my friends
Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
Had a glitch with it already, phone was sleeping, got a message on gtalk and it locked full on vibration, blinking the led, wouldn't wake up and eventually rebooted after maybe 10 seconds. I've had this happen on one of the dsb kernels too, I think. Wiped caches again, hasn't occurred again so far.
Happened not 10 minutes after flashing it so I'm chalking it up to kernel making itself at home, just a note that it happened.
Edit: just rebooted again getting an email notification, UKB 1.3. Seems I can't receive a notification while the phone is sleeping or it jams up and reboots.
Sent from my HTC DNA
Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
matteebee said:
Flashgui worked for me. Renamed file to "boot.img" and ignored the warnings. I like living on the edge. Booted up and shows this kernel version. Thanks for this.
Stay thirsty, my friends
Click to expand...
Click to collapse
Just did the same thing, was coming back to edit my last post lol
Sent from my HTC6435LVW using Tapatalk 2
pio_masaki said:
Had a glitch with it already, phone was sleeping, got a message on gtalk and it locked full on vibration, blinking the led, wouldn't wake up and eventually rebooted after maybe 10 seconds. I've had this happen on one of the dsb kernels too, I think. Wiped caches again, hasn't occurred again so far.
Happened not 10 minutes after flashing it so I'm chalking it up to kernel making itself at home, just a note that it happened.
Edit: just rebooted again getting an email notification, UKB 1.3. Seems I can't receive a notification while the phone is sleeping or it jams up and reboots.
Sent from my HTC DNA
Click to expand...
Click to collapse
After it reboots, can you try to get a log with
adb shell cat /proc/last_kmsg > last_kmsg.txt
and send a link to the last_kmsg.txt file?
orangechoochoo said:
I didn't see any mention of gpu tweaks so I didn't want to make assumptions, hence my question.
EDIT: I just noticed my autocorrect changed "gpu" to "you" in my post you responded to.
Click to expand...
Click to collapse
Ah, that makes more sense... I'm planning on including dsb's changes to any overclocking, etc. but I don't have the knowledge to tweak these settings myself.
Disclaimer:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* blah blah blah you get the point.
*/
1# post: Disclamer - special thanks
2# post: Current release & source
3# post: FAQ - bugs - future features
Donator List: (huge thanks for support)
here
Suggested kernel control app: trickstermod
I don't know if it works because i don't own the device but i have got ville which is pretty similar
[GUIDE]How to compile a kernel
Credits and Thanks:
dsixda, showp1984, ngtools, faux123, Christopher83, franciscofranco, msm8960 team, jrior001
Features:
Based on linux 3.4.99
Compiled with linaro toolchain 4.9.1 2014.07 optimized for cortex-a15
Linaro -O3 optimization
avaiable CPU governors: interactive, ondemand, performance, powersave, intellimand, intelliactive
avaiable GPU governors: ondemand, performance, simple
avaiable schedulers: row, deadline, noop, cfq, bfqv7r4, fiops, sio
Sleepy Plug
NTFS read & write support
exfat support
UTF8
Voltage control
Sweep2Wake
Double tap 2 wake
Pocket detection
Intelli-thermal
zRam with LZ4 compression
zCache with LZ4 compression
CPU OC to 1.7 GHz
GPU OC to 512MHz (3D) and 320MHZ (2D)
Faux sound control v. 3
Improved alghorithm: SHA1, AES, SQRT, lib/string (glibc version), lib/memcopy (glibc version), XOR (neon)
dynamic fsync by faux123
fastcharge
powersuspend driver (replace earlysuspend)
KCAL control (RGB)
heavly patched memory allocators, RWSEM and mutex (take a look at my github, too many changes to make a list here)
Changelog:
Code:
[JUL 26 2014]
Revert "prctl: adds the capable(CAP_SYS_NICE) check to PR_SET_TIMERSLACK_PID."
Revert "prctl: adds PR_SET_TIMERSLACK_PID for setting timer slack of"
add qseecom support
some defconfig changes
cpufreq: revert CAF's cpu policy save code
sched/cpuidle: reduce IPI storm. Backport upstream 3.16
mm, hugetlb: improve page-fault scalability
mm: per-thread vma caching
update compiler to linaro toolchain 4.9.1 2014.07 optimized for cortex-a15
update to 3.4.99
added KCAL control by faux and fixed by me
add F2FS support
Revert "msm: htc: update mem mapping"
[JUL 17 2014]
update to 3.4.98
sync with cm
sync with codeaurora/kk_2.7-stable
update sleepy_plug
bfq: BFQ-v7r5
bugfix from google (see github)
[JUN 29 2014]
Remove JustArchi GCC flags cos they are unstable
update to 3.4.95
sync with CM
sync with codeaurora/kk_2.7-stable
ext4: Speedup WB_SYNC_ALL pass called from sync(2)
[JUN 19 2014]
update compiler to linaro toolchain 4.9.1 2014.06 optimized for cortex-a15
update to 3.4.94
remove -fdata-sections GCC flag (cause of reboot issue)
sync with CM
sync with codeaurora/kk_2.7-stable
updated sleepy_plug
[JUN 09 2014]
sync with codeaurora/kk_2.7-stable
memset patch to fix bootloops
[JUN 08 2014]
3.4.92
reverted some KGSL CAF patches
removed -ftrace flag
sync with CM
improved int_sqrt algorithm
update bfq to v7-r4
[MAY 28 2014]
sync with codeaurora/kk_2.7-stable
update sleepy_plug
cpufreq: ondemand: Calculate load_at_max_freq based on current policy->max
sched: add do_avg_nr_running to fix avg_nr_running
[MAY 19 2014]
update to 3.4.91
merge codeaurora/kk_2.7_rb1.38
update bfq to v7-r3
sleepy_plug now supports quadcore CPUs
fix headset support (CM)
new GCC flags
update compiler
[MAY 03 2014]
block: support volname for HTC devices with proc/emmc support
[MAY 02 2014]
compiled with Linaro GCC 4.9.1 optimized for cortex-a15
sync with CM
update devices_htc from Jet jb 4.3 kernel
update headset driver from Jet jb 4.3 kernel
update memory mapping (more RAM avaiable)
update pn544 driver
update bma250 driver
OC to 1.7GHz
[APR 29 2014]
fix boot
update to 3.4.88
sync with codeaurora/kk_2.7-stable
some other CAF patches
max OC to 1.5 GHz
[APR 28 2014]
fixed boot (?)
[APR 24 2014]
first release
If you like my work please consider making a donation, I spend almost all my free time on making this kernel the best
i'll buy another phone to continue to support the android development!
Download:
androidfilehost folder: http://www.androidfilehost.com/?w=files&flid=14183
normalToQV: http://www.androidfilehost.com/?fid=23501681358544069
(if you don't see the new version just wait some minutes, it's uploading)
Kernel Source: Github
Q: What is QV version?
A: QV means "qualcomm voltages". qualcomm made a patch and stuck all voltages to 1150mv to improve stability. QV version has got all 1150 mv for each freq (like older 3.4 kernels).Q: I plugged in my pen drive but i can't found it
A: look in /mnt/usbdisk folder.Q: What's and how i enable/disable fastcharge?
A: with fast charge an USB charger will recognized as AC charger. it won't charge your phone faster with an AC charger. it may not charge your phone faster with an USB charger.
with the usb cable UNPLUGGED edit /sys/kernel/fast_charge/force_fast_charge:
0 -> disable
1 -> enable
than plug in the cableQ: i've got random reboots, what do you need?
A: first read here
write this info:
kernel version
ROM
governor
scheduler
undervolted? if yes don't undervolt
QV version? if no use it
last_kmsg
Q: what's BLN and how i enable/disable it?
with BLN on when you received a notify the soft key will blink.
to enable/disable edit /sys/class/leds/button-backlight/blink_buttons:
0 -> disable
1 -> enableQ: what's s2w and how i enable/disable it?
Sweep2wake allows you to wake up your device by swiping your finger across the capacitive buttons from left to right. Swiping from right to left will put it back to sleep (sweep2sleep).
to enable/disable edit /sys/android_touch/sweep2wake:
0 -> disable
1 -> enableQ: what's dt2w and how i enable/disable it?
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping the capacitive buttons.
to enable/disable edit /sys/android_touch/doubletap2wake:
0 -> disable
1 -> enableWhat's sleepy_plug and how can i activate/deactivate it?
sleepy plug it's an hotplug driver (it decide when turn on the second core) i wrote. it's an experimental driver and it may have got performance problem. if you notice some decrease in performance report it.
to enable/disable edit /sys/module/sleepy_plug/parameters/sleepy_plug_active:
0 -> disable
1 -> enableInstall instruction:S-OFF:
- flash the zip in recovery
- wipe caches (optional)S-ON:
Windows & Linux:
flash kernel zip.
stay in recovery after flashing the zip
from command prompt (ot terminal) on PC:
Code:
adb pull /tmp/newboot.img
adb reboot-bootloader
fastboot flash boot newboot.img
fastboot reboot
OLD S-ON INSTRUCTION:
Linux:
- flash awesome kernel cleaning script: http://d-h.st/HDi (optional)
- flash the zip in recovery (obsolete, for older kernels with modules outside built outside)
- use zImage switcher to make a new boot.img
-
Code:
fastboot flash boot newBoot.img
Windows: (don't ask me how it works or everything else, i don't know and they have got tutorials on their site)
- repack your ROM boot.img with mine zImage using Virtuous Ten Studio http://www.virtuous-ten-studio.com/index.php/downloads
-
Code:
fastboot flash boot newBoot.img
Bugs 3.4:
None
If you want to use my kernel for your ROM just use it and cit me in credits
Great thread and great work. I will be flashing this tonight over a fresh install of snapshot M5 CM11! I'll let you know how it runs, hopefully smooth as butter. Thanks again
rmbq said:
Disclaimer:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* blah blah blah you get the point.
*/
1# post: Disclamer - special thanks
2# post: Current release & source
3# post: FAQ - bugs - future features
Donator List: (huge thanks for support)
here
Suggested kernel control app: trickstermod
I don't know if it works because i don't own the device but i have got ville which is pretty similar
[GUIDE]How to compile a kernel
Credits and Thanks:
dsixda, showp1984, ngtools, faux123, Christopher83, franciscofranco, msm8960 team, jrior001
Click to expand...
Click to collapse
Can you compile a 4.1.2 SENSE5 kernel? all working
Don't care about my awkward English
zhaotiantian said:
Can you compile a 4.1.2 SENSE5 kernel? all working
Don't care about my awkward English
Click to expand...
Click to collapse
I don't work on sense
Inviato dal mio One S utilizzando Tapatalk
looks great.. just flashed CV on new cm11 nightly.. bootloops htc screen
Non QV bootloops on HTC Quietly Brilliant screen. CM 11 4/14 nightly. I'll try the QV another day.
I think I used wrong voltages for you, freq it's 1.5 GHz instead 1.2. I'll make another version asap
I'm running CM11 snapshot M5, I'm not sure which version to flash. Thanks for the work!
Sent from my Incredible 4G LTE using Tapatalk
try the new version!
still no boot for me, tried new non-qv..
and this one? http://www.androidfilehost.com/?fid=23329332407590054
^^ there we go! that one works so far so good.. only thing i noticed is max cpu option is still 1728, i don't think this phone can go above 1512, but i may be wrong?
edit: also, trying to disable the button backlight is buggy. the 3 lights will still blink intermittently..
itrx said:
^^ there we go! that one works so far so good.. only thing i noticed is max cpu option is still 1728, i don't think this phone can go above 1512, but i may be wrong?
Click to expand...
Click to collapse
officially only 1242MHz even ... but it runs fine at the usual (slight) OC 1458MHz or 1512 ... but also 1674 is fine ... just consumes more battery and gets hotter. even up to 1809MHz should be stable for most, but that is way to hot and batt-sucking imho!
official booting version is up, i limited OC to 1.5, 1.7 is too much xD
rmbq said:
official booting version is up, i limited OC to 1.5, 1.7 is too much xD
Click to expand...
Click to collapse
for reference our/my: on the Infernal / Infernal-K99 (ICS-Sense custom kernel) ... 1512 / 1458 was set as the std max CPU freq, but we allowed up to 1809 on Infernal (which I admit is rather really high xD) ... and 1674 max OC on Infernal-K99 => the max OC of 1674 is usually auto-selected for the 2nd-core on demand whereas the 1st core admits to whatever limit is set (thus usually 1458)
no real heat probs at all since months with that setting ... 1809 tended to get rather hot (e.g. on reboots) ... not so with 1674 (and a not too high voltage as set in std)
oh, and limiting the "OC" to 1512 isn't really an OC limit ... as that was std for the MSM8960 on almost all devices! (just fireball got an artificial limit of 1242 to further improve on batt runtime). so from that point of view, only everything _above_ 1458/1512 should be considered OC.
just my 2c
PS: apart from that, thanks for working on fireball AT ALL ... there aren't many devs left here unfortunately
on a note: please also enable 192MHz as the lowest CPU freq while you are at it ... never heard any complaints about it for our custom-kernels ... _and_ it greatly improves on total runtime, if 192MHz as lowest for CPU is set ... instead of the regular 384MHz only
cheers,
kimba99
Kernel is pretty smooth and getting great battery life, thank you indeed! I'd agree with adding 192Mhz as well.
kimba99 said:
for reference our/my: on the Infernal / Infernal-K99 (ICS-Sense custom kernel) ... 1512 / 1458 was set as the std max CPU freq, but we allowed up to 1809 on Infernal (which I admit is rather really high xD) ... and 1674 max OC on Infernal-K99 => the max OC of 1674 is usually auto-selected for the 2nd-core on demand whereas the 1st core admits to whatever limit is set (thus usually 1458)
no real heat probs at all since months with that setting ... 1809 tended to get rather hot (e.g. on reboots) ... not so with 1674 (and a not too high voltage as set in std)
oh, and limiting the "OC" to 1512 isn't really an OC limit ... as that was std for the MSM8960 on almost all devices! (just fireball got an artificial limit of 1242 to further improve on batt runtime). so from that point of view, only everything _above_ 1458/1512 should be considered OC.
just my 2c
PS: apart from that, thanks for working on fireball AT ALL ... there aren't many devs left here unfortunately
on a note: please also enable 192MHz as the lowest CPU freq while you are at it ... never heard any complaints about it for our custom-kernels ... _and_ it greatly improves on total runtime, if 192MHz as lowest for CPU is set ... instead of the regular 384MHz only
cheers,
kimba99
Click to expand...
Click to collapse
about OC ok, i didn't know your device can handle 1.7 GHz and i'll enable it again in next version.
about 192MHz i don't know if i ever will enable it
rmbq said:
about 192MHz i don't know if i ever will enable it
Click to expand...
Click to collapse
About over/down clock/voltage CPU & GPU, please check this post:
http://forum.xda-developers.com/showthread.php?t=2217285?&p=51891887
duki994 Kernel for Stock TouchWiz LP ROMs
A personal project that had good results and I wanted to share it with others
It's based on official Samsung sources for Lollipop firmware.
Important note:
This kernel should work on any custom ROM that is stock lollipop based
Features:
* Wolfson Audio control (thanks to @AndreiLux)
* Battery charging control (thanks to @AndreiLux)
* CPU voltage control for both A7 and A15 cluster (thanks to @AndreiLux)
* Exposed all OPP voltage controls (thanks to @AndreiLux)
* Powersuspend v1.7 by @faux123 and @Yank555
* LMK, MM and FS powersuspend mods ported from @dorimanx's LG G2 kernel
* SCHED code fixes
* SCHED: HMP thresholds changed and new patches implemented
* Many changes related to ARM instruction code and lowlevel ARM core management
* Enabled NEON mode in kernel with full VFPV4 support
* Added new SHA256 and SHA512 NEON accelerated algortihms - now blazing fast
* UKSM (Ultra Kernel Samepage Merging) - algorithm that's better optimized than standard KSM
* WiFi standby wakelocks (PNO wakelock) reduced
* WiFi userspace power mode/DTIM change (for advanced users ONLY)
* WiFi driver switched from deprecated earlysuspend to use newer powersuspend driver (this is to fix some of bugs that could lead device kernel crash)
* NET updates
* Enabled all TCP congestion protocols and set Westwood as default (best wireless performance)
* Disabled KNOX
* SELinux disabled in kernel
* Fully configurable in Synapse (download from Google Play)
/* Important note to other devs */
You cannot include this to your ROMs. I can't be responsible if anything goes wrong, I can't help with any issues without knowing kernel version and users should be routed to this thread if they want this kernel, or if you recommend it. I think that it's best to separately view custom ROM and custom Kernel, so each dev (ROM or Kernel one) can work on bugs/features and make it as compatible as it can.
However, you can add this thread link and mention me in your thread, so people would know where to ask if some kernel problem arises
Warranty void
By flashing this kernel you will void your warranty. I'm not responsible if you brick your device, or if someone starts nuclear war.
Note:
Don't change voltages on "Busses" tab if you don't know what you are doing. It can reboot your phone if your memory controllers, ISP or MMC controllers can't handle low voltage.
WiFi pasword resetting fix:
Code:
1. open your build.prop file
2. find line ro.securestorage.support
3. change it from true to false (if not already false)
This line being on true will make your WiFi not work good with this kernel. This is due to Samsung's rooting restriction and other Samsung specific workarounds to stop rooting and flashing. Any custom ROM probably has this line changed to false.
Changelogs:
Version 1.4 BETA
Billion critical updates from my G900H version:
* MM code
* new LMK driver
* Exynos interactive governor updated
* IRQ code revamped
* OF code revamped
* New 8-band EQ sound-control
* Numerous ALSA updates and fixes
* Numerous Wolfson DAC driver updates
* MemInfo code updates
etc. list is enormous
Version 1.3
*MM page allocation changes. and others. Now more than 50% faster page_alloc
*RCU and SRCU updates from S6 and upstream + CAF
*NET updates
*USB fixes and updates
*dma mapping ARM fix
Version 1.2.1
*Synapse
->added ROW scheduler to test (experimental)
*Several BLOCK code updates and typo fixes. Some serious bugs fixed.
*Fully updated ROW I/O sched added (experimental)
Version 1.2
* Synapse:
-> disabled min cpu freq control. not needed.
-> added new I/O schedulers
* Massive updates to BLOCK, SHCED, MM, WORKQUEUE critical code
* Added FIOPS and BFQ I/O schedulers
* EXT4 updates to fix possible kernel crashes
* ZSWAP now uses ultra fast and light on cpu LZ4 compression
* CPUFREQ optimizations
* Updated BFQ, FIOPS, DEALINE scheds with fixes and optimizations
Version 1.1
*Synapse:
* Added live cpu stats for all 8 cores (quad A7 and quad A15 cores)
* Added live CPU temperature monitoring
* Added live battery temperature and health status
* Disabled broken battery input current feature (shows 0mA for our PMIC chip)
* Added misc tab:
+ ability to take logcat,dmesg,last_kmsg
+ HMP Little packing switch ON/OFF and explanation
* Added optimized ARM RWSEM algorithm
* Fixed HMP so HMP little packing would work good with our implementation
* thermal IPA(Intelligent Power Aware) now updates power tables immediately when voltage changed from Synapse
* entropy depletion fixes
* Enabled FRANDOM random number generator module for more entropy and less lag
* Added NEON instruction accelerated SHA256/SHA224 algorithm. Now we have SHA384/SHA512, SHA256/SHA224 and SHA1 algorithms NEON accelerated - blazing fast
* HMP little packing switch for Synapse
Experimental option made by nvidia. It groups tasks so more of them would be scheduled across power saving cores (A7 cores in our CPU). It may or may not save battery depending on your usage.
Downloads:
Here it is
https://app.box.com/s/vt70dzo7fzgnlyik4mxkiaaj7xkhjaot
Special thanks:
@AndreiLux for his awesome Synapse app, audio control, charging control, sources and many features/updates and upgrades to Exynos kernel code
@UpInTheAir for his source that I looked when I had bugs, and for his fixes/workarounds
@dorimanx for inspiring me to start developing and his LMK and MM mods
@bonuzzz for his custom KitKat kernel for Galaxy Alpha and his sources
@apb_axel for UKM and his scripts that helped me a lot in making custom Synapse config
XDA:DevDB Information
G850, Kernel for the Samsung Galaxy Alpha
Contributors
duki994
Source Code: https://github.com/duki994/SM-G850_Kernel_LP/
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2016-08-12
Created 2015-11-02
Last Updated 2016-08-12
Reserved
How to build this kernel guide
PREREQUISITES
What you need installed to compile
gcc, gpp, cpp, c++, g++, lzma, lzop, ia32-libs flex
If on 64bit Linux, install gcc multilib
Project folder structure
--project_root/ #### can have any name
-----ramdisk_source/ ## defined by RAMDISK_TMP var in script
-----ramdisk_tmp/ ## defined by RAMDISK_DIR var in script
-----kernel_source/ #### can have any name
-----RELEASE/
TOOLCHAIN INFO
Toolchain is already into kernel dir. You just need to have
correct folder structure and run this script. Everything will be auto-built
FLASHABLE ZIP
Flashable zip will be located in project_root/RELEASE directory
and will have name Kernel-slte.zip
All other explanations here:
https://github.com/duki994/SM-G850_Kernel_LP/blob/master/build_kernel.sh
Clone ramdisk source in ramdisk_source
Clone kernel in kernel_source folder
Be sure to have project directory structure as written above
After that, you just need to run:
sudo bash build_kernel.sh
in kernel folder. And voila. After finished you have Kernel-slte.zip in RELEASE directory
If it show any errors, open kernel source and type in terminal:
chmod -R 755 *
Then repeat sudo bash build_kernel.sh
awesome job, thank you
finally undervolt .. yay
ayamgoreng said:
awesome job, thank you
finally undervolt .. yay
Click to expand...
Click to collapse
When you have time, report how it works
Sent from my LG-D802 using Tapatalk
Is it possible to other variants like Galaxy Alpha SM-G850L Korean? Thanks
duki994 said:
When you have time, report how it works
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I reduce voltage A15,A7 (every speed) by roughly 20mv
gaming (coc,asphalt,etc) for roughly 1 hour; result=stable :good:
edit: volume in the audio also work, louder headphone.
Thanks, I'll try it.
how the battery with this kernel?
gtrs36 said:
Thanks, I'll try it.
how the battery with this kernel?
Click to expand...
Click to collapse
Battery? It's better than stock for me. For screen on, this morning I had 50mins SOT and 87% battery left. That's even better than my LG G2, which is a beast according to tests
My father uses Galaxy Alpha, and yesterday he managed to get 4h SOT with HSDPA data on.
When screen off (in suspended mode) it's very low power consumption due to Powersuspend driver. It's better than stock.
exaflare said:
Is it possible to other variants like Galaxy Alpha SM-G850L Korean? Thanks
Click to expand...
Click to collapse
I have no access to G850L model. I don't know if it will work.
During this week, if I have enough time, I'll download G850L source and build it with all mods/features and give you to test it
thanks duki994.
which app I need install to control on the kernel?
hi!
1. how do You undervolt by 20mv, in synapse i have steps like 1x,xxMv and can set up -25Mv??
2. I have strange warning message after installed this kernel. it says phone needs to reboot. after reboot the same. just annoying
duki994 said:
Battery? It's better than stock for me. For screen on, this morning I had 50mins SOT and 87% battery left. That's even better than my LG G2, which is a beast according to tests
My father uses Galaxy Alpha, and yesterday he managed to get 4h SOT with HSDPA data on.
When screen off (in suspended mode) it's very low power consumption due to Powersuspend driver. It's better than stock.
Click to expand...
Click to collapse
did you UV or what settings did you use ?
m_p11 said:
hi!
1. how do You undervolt by 20mv, in synapse i have steps like 1x,xxMv and can set up -25Mv??
2. I have strange warning message after installed this kernel. it says phone needs to reboot. after reboot the same. just annoying
Click to expand...
Click to collapse
1. Our voltage regulator accepts 6.25mV step. So you can UV/OV in multiples of 6.25. When you do math, 6.25mV x 4 = 25mV
You can't UV -20mV. You can UV -18.75m (3 x 6.25mV). Next step is -25mV (4 x 6.25mv).
Ursurobertt said:
did you UV or what settings did you use ?
Click to expand...
Click to collapse
No UV. All stock. Only changed earpiece volume (incall speaker volume) to higher (+4dB if I recall good from this morning). It's for better hearing incall
UV generally doesn't reduce battery consumption (it's maybe 1%-3% less power usage). Real benefit of UV is lower CPU heat and prolonged life of motherboard.
Some chips can't handle UV at all. Some can be UV by as much as -150mV. It all depends on specific chip that came out of fabric process. Note that UV brings instability on some devices.
Sent from my LG-D802 using Tapatalk
duki994 said:
Battery? It's better than stock for me. For screen on, this morning I had 50mins SOT and 87% battery left. That's even better than my LG G2, which is a beast according to tests
My father uses Galaxy Alpha, and yesterday he managed to get 4h SOT with HSDPA data on.
When screen off (in suspended mode) it's very low power consumption due to Powersuspend driver. It's better than stock.
Click to expand...
Click to collapse
hi dude
what setting are used on your father Alpha,stok or I should change in synapse
hensk said:
hi dude
what setting are used on your father Alpha,stok or I should change in synapse
Click to expand...
Click to collapse
Look at post above yours. I explained everything
Sent from my LG-D802 using Tapatalk
recent button does not works after flashing this kernel.. recent button works fine with stock kernel...
likhon02 said:
recent button does not works after flashing this kernel.. recent button works fine with stock kernel...
Click to expand...
Click to collapse
On which ROM are you? Everything works for me on stock. I have to see if anything changes it.
Did you set secure storage to false in build prop?
I'l automate that in next build.
Kernel doesn't mess with options like recent buttons and Java written parts of Android OS.
Sent from my LG-D802 using Tapatalk
duki, you didn't answer to my question.
gtrs36 said:
duki, you didn't answer to my question.
Click to expand...
Click to collapse
Please read OP before asking. Everything is said there.
Synapse is the app with which you can change settings of this kernel.
duki994 said:
On which ROM are you? Everything works for me on stock. I have to see if anything changes it.
Did you set secure storage to false in build prop?
I'l automate that in next build.
Kernel doesn't mess with options like recent buttons and Java written parts of Android OS.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I am on ozcan rom 4.1. my recent button only works with Nordic based stock which is NEE G850FXXU2COI3 5.0.2 11.09.2015 5614954 and ozcan rom..and with any other rom like rr and cm12.1 my recent button does not work.. secure storage is false by default on build.prop .
HandBag Kernel
"Every single feature" Held together with duct tape and magic
Development for the Moto X Style/Pure seems a little quiet, so I decided to patch together my own kernel. I think this is the perfect chance to learn git and the build system for android. Feature requests are welcome!
Disclaimer
Please note that this is my first kernel and that stability and battery life are not guaranteed. Actually, nothing is guaranteed. I am not responsible for bricked devices or lost data. Flash at your own risk.
You will most definitely have to adjust the default settings. Expect lags and fun stuff.
Also note that this kernel is meant for LineageOS based roms. Tested and running daily on XT1575.
Features
Based on Lineage OS source
Additional CPU Governors (Alucard, ElementalX, Despair, Chill, IntelliActive, Lionheart, BioShock, BluActive, Wheatley, ZZMove, Impulse, Relaxed)
Additional I/O Schedulers (Deadline, NOOP, Maple, Row FIOPS, SIO, SIOPlus, TripNDroid, VR, Zen)
Additional Hotplug Drivers (Alucard Hotplug, Autosmp, Bricked Hotplug, MSM Hotplug, Lazyplug) Causes laggy wakeup
Additional TCP congestion algorithms (Default westwood)
KSM/uKSM
Overclock/Underclock
Voltage control
Wake Gestures by flar2
Fsync, Inputboost, Touchboost, and Wakelock Toggles
Kexec Not needed yet
Ofast Actually Os for now (Kernel gets too big and there's no decompression for aarch64)
UBER Toolchain 6.0 Linero Toolchain 6.3.1
Dynamic Fsync
Adreno Idler/Boost
AnyKernel2 Installer
Backlight Dimmer
Color control (KCal)
To-Do
I dunno, you tell me.
Installation
Flash in recovery
Note: AnyKernel2 will use your existing ramdisk. It's recommended to flash over the kernel that came with your rom or a previous version of my kernel. Refer to AnyKernel2 for restoring after a bad flash.
Downloads
See Downloads Tab under thread title: https://forum.xda-developers.com/devdb/project/?id=20678#downloads
There are two branches:
msm - Uses the stock msm_core_ctl to handle hotplugging
hotplugs - Uses custom hotplugging solutions (Currently only bricked_hotplug)
Special Thanks and Credits
flar2
franciscofranco
nathanchance
frap129
dirtyhank
showp1984
engstk
faux123
neobuddy89
ZaneZam
yank555-lu
HashBang173
varunchitre15
Cl3Kener (UBERTC)
osm0sis (AnyKernel2)
trashy111 (For build server hardware)
... and various other helpful developers!
If I missed someone who should be on here,
please feel free to let me know.
XDA:DevDB Information
HandBag Kernel, Kernel for the Moto X Style (Pure)
Contributors
XDleader555
Source Code: https://github.com/XDleader555/HandBag-Kernel-Clark
Kernel Special Features:
Version Information
Status: Testing
Created 2017-05-15
Last Updated 2018-02-27
Changelog
02/27/18 - v2.3.5
handbag-msm:
Added more overclock values
Separated voltage control to upper and lower bounds for fine tuning
Merged Security commit for WPA exploit
07/31/17 - v2.3.3
handbag-msm:
Forgot to re-enable msm_core_ctl hotplug (oops)
Older Changelogs:
07/30/17 - v2.3.2
Add voltage control
07/28/17 - 4:59PM - msm branch - v2.3.1
Bring back alucard governor
Bring back power efficient workqueue
Bring back Dynamic fsync
Bring back uKSM and patches
Add LCD Notifier
Disable trace_printk
Disable sched_hrtick
07/28/17 - 12:39AM - msm branch - v2.3
Re-enable msm_performance (Default Kernel Hotplugging)
Update Zen Tune from 4.5 to 4.10
Enable Partial Resume
Revert Stack Protection from Strong to Normal
Add Software CRC toggle
Revert Alucard, Autosmp, bricked, msm_hotplug, lazyplug Hotplugs
Revert Dynamic fsync
Revert powersuspend and state_notifier
Temporarily Revert power efficient work queues
Revert KEXEC patches until someone complains
Temporarily Revert uKSM
A lot of other various cherry picks reverted
06/23/17 - 3:23PM - v2.2
Add Alucard Hotplug and Autosmp Hotplug
Add Alucard CPU Governor
Set some cpu defaults on boot from frap129's electron kernel
Cherry-pick f2fs patch to avoid syncing kernel panics
Increase thermal threshold from 46C to 60C. Light load happens around 55C, so we're always throttling
Disable thermal core control (You can re-enable it if you like)
Dynamic Fsync
Add CIFS support
REVERT: wrong vibe control commit
06/15/17 - 11:41PM - v2.1
REVERT: Merge F2FS changes up to May 20th 2016
REVERT: Small updates to msm mdss
REVERT: Switched to bricked_hotplug as default
REVERT: Show cpu voltages (Not actually useful)
REVERT: Update linux from 3.10.102 -> 3.10.105
REVERT: zRam, zSwap, zMalloc Updates
REVERT: linux/random backport from linux 4.1.40
REVERT: Those various "optimizations"
REVERT: Anything relating to state_notifier and system_wq
Bring back PowerSuspend. Why fix what ain't broke.
Add patch to avoid f2fs kernel panic/bootloop when downgrading/upgrading (sidegrading?) to v2.1
05/31/17 - 12:50AM - v2.0
Merge F2FS changes up to May 20th 2016
Small updates to msm mdss
Switched to bricked_hotplug as default
This should really be 1.9.1, but I already made it 2.0. Too lazy to fix ¯\_(ツ)_/¯
05/30/17 - 1:37AM - v1.9
Switch toolchains from UberTC 6.0 to Linero 6.3.1
Add relaxed cpu governor
Show cpu voltages (No editing unfortunately)
Slimbus overclock
UNREVERT: zSwap, zMalloc Updates
Removed powersuspend (not needed)
linux/random backport from linux 4.1.40
Various optimizations I probably missed
05/26/17 - 3:38AM - v1.8
UNREVERT: Update linux from 3.10.102 -> 3.10.105
UNREVERT: zRam updates
disabled zSwap (I don't think anyone uses this, correct me if I'm wrong)
converted msm_hotplug to use state_notifier
converted bricked_hotplug to use state_notifier
05/25/17 - 8:14PM - v1.7.1
Fixed overclock frequency not showing
Fixed enabling/disabling of state_notifier in tuning apps (turns off hotplug suspend)
converted msm_hotplug to use state_notifier I need to touch up on C
05/24/17 - 10:16PM - v1.7
Cleaned source code tree
REVERT: Update linux from 3.10.102 -> 3.10.105
REVERT: Moved msm_hotplug to system_wq
REVERT: Interactive CPU governor pulled from Pixel source
REVERT: zRam, zSwap, zMalloc Updates
REVERT: Overclocking/Underclocking (Just temporary, ran out of time)
05/24/17 - 3:16AM - v1.6
Update linux from 3.10.102 -> 3.10.105
Added Lazyplug
Moved msm_hotplug to system_wq
Avoided boot issue caused by msm_hotplug by setting Lazyplug as default. (msm_hotplug still works if set by user)
05/22/17 - 2:37AM - v1.5
Wake Gestures: Fixed touchscreen not responding when enabling gestures with the screen off
Wake Gestures: Fixed touchscreen not responding in ambient display
Wake Gestures: Phone call detection
Set msm_hotplug as default
Tweaked msm_hotplug defaults slightly
Increased default idle frequency for bricked_hotplug to 600mhz
05/21/17 - 7:38AM - v1.4
Added Wake Gestures by flar2 (DT2W, S2W, S2S)
Added uKSM
Interactive CPU governor pulled from Pixel source (Seems to have fixed our crashing issue)
Added Despair and Chill CPU governors
Power efficient work queue mode (wq_power_saving)
KEXEC
Updated zmalloc and zram
Adreno Boost
Overclocking/Underclocking
05/17/17 - 7:50PM - v1.3
Removed msm_core_ctl to prevent conflicts with bricked hotplug
Renamed bricked_hotplug to prevent confusion
Added msm_hotplug v2.4
Fixed touchboost for those who actually like that
Added color calibration (KCAL)
05/17/17 - 5:57AM - v1.2
Added Governors (IntelliActive, Lionheart, BioShock, BluActive, Wheatley, ZZMove, Impulse)
Added Adreno Idler
Small optimizations
Disabled Touchboost by default
Added Kernel PowerSuspend
05/16/17 - 12:33PM
Fixed backlight dimmer
Removed userspace governor
05/15/17 - 3:29AM
Initial Release
It's highly recommended that you apply your own settings with a kernel manager until I add bootup scripts
Frequently Asked Questions
Q: How do I logcat?
A: You'll need adb or root
Through adb:
Code:
adb logcat -b all -d > %userprofile%/Desktop/logcat.txt
Through your phone:
Download a terminal app
Code:
su
logcat -b all -d > /sdcard/logcat.txt
It'll take about 10 seconds for the command to work. Preferably catch the log as soon as you boot.
Upload the logcat found at the output directory as an attachment.
Q: Where is hybrid mode for powersuspend?
A: https://forum.xda-developers.com/showpost.php?p=72405702&postcount=92
Q: Which Roms work with this kernel? Does it work on CAF Roms?
A: Lineage OS. No guarantees for other Roms, but users have reported that it works on:
Mokee OS
Resurrection Remix
Dirty Unicorns (CAF?)
AICP
CrDroid
Q: What app should I use to tune this kernel?
A: I prefer EX Kernel Manager, but Kernel Adiutor works well too.
Q: Can we get X feature?
A: Working on it.
Nice
Will give it a try!
Great work
---------- Post added at 12:39 PM ---------- Previous post was at 12:38 PM ----------
aakashverma0007 said:
Nice
Will give it a try!
Click to expand...
Click to collapse
Waiting for your new video on this kernal's reviews
Nice work! I was gonna do something similar but I never had time. If I do I might do it for caf-aosp roms. I will flash this kernel with resurrection remix and give some feedback! Very nice job
confirmed working on Mokee OS nightly for 20170514
This won't work with something like CypherOS which is AOSP based right?
you can try... backup your boot.img in recovery, if anything goes wrong you can always recover from that
Confirmed working on Resurrection remix latest weekly.
Bro please include KCAL support if possible. The piece I have does not render good colors. It would be awesome then. Thanks for your efforts.
Bwangster12 said:
This won't work with something like CypherOS which is AOSP based right?
Click to expand...
Click to collapse
I get massive bluetooth battery drain on CypherOS. Trying a different kernel MAY be something that could fix that?
Bwangster12 said:
I get massive bluetooth battery drain on CypherOS. Trying a different kernel MAY be something that could fix that?
Click to expand...
Click to collapse
The Bluetooth drain is just cypher os itself. Other people said they had that problem even on they're Google plus page. Just use a different room like crdroid- resurrection remix, or just plain old lineage, or mokee. You got some nice options.
Curlyfry2121 said:
The Bluetooth drain is just cypher os itself. Other people said they had that problem even on they're Google plus page. Just use a different room like crdroid- resurrection remix, or just plain old lineage, or mokee. You got some nice options.
Click to expand...
Click to collapse
First of all... I feel like no one has recognized the BT drain on CypherOS... so thank you for that. Trying other roms is what I've been doing. I'm currently on Tesla and like it a lot... but have desparately wanted a rom thats as similar to a Google Pixel as possible. Pure Nexus hasn't been updated to Nougat and CypherOS seemed to be what I wanted. Things like Lineage, Tesla, RR, Dirty Unicorns all have their own things. At least with Tesla, I installed Substratum and pixel themes... just not exactly like the Pixel-ness of CypherOS.
Any plans for hotplugging? I'm not really requesting it just wondering what you have in store for the future.
Curlyfry2121 said:
Any plans for hotplugging? I'm not really requesting it just wondering what you have in store for the future.
Click to expand...
Click to collapse
I plan on packing in as many features as possible. Hotplugging is on the list after I get the CPU Governors and boot up scripts in.
Bwangster12 said:
I get massive bluetooth battery drain on CypherOS. Trying a different kernel MAY be something that could fix that?
Click to expand...
Click to collapse
You can try disabling Bluetooth scanning under location setting or disable one of the relevant wakelocks using my kernel with your favorite kernel manager. (I prefer EX Kernel Manager)
XDleader555 said:
I plan on packing in as many features as possible. Hotplugging is on the list after I get the CPU Governors and boot up scripts in.
You can try disabling Bluetooth scanning under location setting or disable one of the relevant wakelocks using my kernel with your favorite kernel manager. (I prefer EX Kernel Manager)
Click to expand...
Click to collapse
Nice, will test any new versions released as soon as possible. Keep up the good work ?
Works on dirty unicorns, which is a caf based rom, so I'm surprised this is working and there's nothing really wrong except in ex kernel manager and I tried kernel auditor I enable backlight dimmer and when I turn the screen off and back on the brightness is much higher than what I have it set as. Anyone else have that?
Same thing on Resurrection remix
XDleader555 said:
I plan on packing in as many features as possible. Hotplugging is on the list after I get the CPU Governors and boot up scripts in.
You can try disabling Bluetooth scanning under location setting or disable one of the relevant wakelocks using my kernel with your favorite kernel manager. (I prefer EX Kernel Manager)
Click to expand...
Click to collapse
YAY thanks! really and truly this phone needs better hotplug to manage the battery better.
Curlyfry2121 said:
Works on dirty unicorns, which is a caf based rom, so I'm surprised this is working and there's nothing really wrong except in ex kernel manager and I tried kernel auditor I enable backlight dimmer and when I turn the screen off and back on the brightness is much higher than what I have it set as. Anyone else have that?
Same thing on Resurrection remix
Click to expand...
Click to collapse
I haven't cherry picked the code for backlight-dimmer yet. Currently having some issues with getting Ofast to work. I'll probably keep Ofast disabled and work on adding features.
EDIT:
Apparently, I did cherry pick it. I'll look into it.
EDIT2:
Fixed, seems like flar2 did something different for the Nexus 5x backlight. Check the downloads tab for the most recent kernel.
Argon kernel, for Android 8.1 & 9.0 ROM's (bacon).
Disclaimer:
use this kernel at your own risk. Flashing it without any knowledge of what you're doing may brick your device. I'm not responsible for any software/hardware damage.
Argon v11 is the last version for Oreo! Starting from v12 only Pie is supported.
Changelog:
v16.1 (August 11th)
support for OTG Y cables
minor bug fixes and security patches
Previous releases:
v16 (August 2nd)
kernel code base synced with LineageOS
lots of misc. bug fixes and small improvements
sdfat driver now replaces both vfat and exfat
some f2fs backports
v14 (April 24th)
built with the newest GCC toolchain for ARM
dynamic management of dirty page writebacks
some useless drivers have been removed (this might give us a few additional MB's of RAM)
a couple of improvements for the random number generator driver
IRQ threading is enabled by default (as suggested by Con Kolivas)
v13 (March 31st)
memory bandwidth overclock
lots of small updates and improvements (mainly for the assembly memory routines)
a few updates for the impulse CPU governor
new TCP congestion control algorithm: 'ascarex'
v12 (March 10th)
official Pie support (LineageOS 16 & Lineage-based ROMs)
small bug fixes and misc. tweaks
a few updates for the "impulse" CPU gov
memory management backports from Linux 3.8
lighter kernel (some debugging options have been turned off)
v11 (January 27th)
built with the newest ARM toolchain
power-efficient workqueues have been implemented in a couple of places
minor source updates & fixes
DDR bandwidth boost has been fixed
important updates for Sultan's CPU boost driver
v10.2 (January 19th)
synced with our LineageOS kernel (mainly bug fixes and security patches)
v10.1 (January 12th)
some source updates and bug fixes
v10 (December 29th)
built with the latest GCC 8 toolchain by Arm
some debugging options are disabled (this might slightly improve performance)
lots of small bug fixes and source updates
v9 (December 11th)
zzmoove governor updated to the latest version
boosted L2 cache frequencies
Spectrum support
Sultanxda's simple thermal driver (replaces Intellithermal)
miscellaneous kernel updates, backports and fixes
dynamic fsync has been (temporarily?) removed
v8.1 (November 23rd)
lots of kernel source updates & fixes
exFAT/sdFAT support
new CPU governors: intellimm, yankactive, zzmoove and impulse
dynamix fsync (disabled by default)
v8 (November 4th) - diff against v6:
built with GCC 8
old charging drivers (these are stable and work properly for everybody)
several improvements for the audio drivers, the memory management libraries, the CPU boosting driver, f2fs, zram, etc.
latest sdcardfs fixes from Google
Intellithermal (with configurable throttling threshold)
latest security fixes
CPU overclocking (disabled by default)
updated bricked hotplug
UKSM with automatic toggling (wip, it's not fully working as of now)
async fsync for ext4 and f2fs
v7.7 (October 23rd)
rebased on top of v7 + all the extra changes of v7.6
msm_hotplug removed (bricked is the default hotplug)
v7.6 (October 23rd)
completely rebased on top of Argon v6.1 (which seems to be the latest stable release) + the following changes
built with GCC 8.2
MSM hotplug enabled by default
cpu_input_boost improvements
latest sdcardfs updates
several other security fixes and improvements
v7.1, v7.2, v7.3, v7.4, v7.5 (October 10th - 11th - 15th - 16th - 17th)
stability fixes
v7 (October 9th)
msm_hotplug replaces bricked as the default hotplug
optimizations for msm8974 boards
older charging drivers from LineageOS 14.1 (they seem to fix all charging problems)
some more minor tweaks, fixes and optimizations
v6.1 (September 30th)
mpdecision is replaced by bricked hotplug by default
v6 (September 27th)
stability fixes
AIO optimizations reverted (this fixes filesystem errors for ext4 users)
slimbus overclock
several improvements and updates (for the ext4 fs, the LMK and many other drivers)
charging current interface
cpu_input_boost by Sultanxda (it replaces CAF's cpu_boost)
v5 (September 19th)
zram is supported
AIO optimizations & backports
minor tweaks and updates
v4 (September 15th)
Per-process reclaim
minor updates and improvements (including security fixes)
v3 (September 8th)
DDR bandwidth boost on screen unlock
misc. kernel updates, fixes and improvements
v2 (August 31st)
several secuirty fixes and kernel source updates
f2fs driver updates
new CPU hotplug: bricked hotplug
power-efficient workqueues are implemented in more drivers
v1 (August 24th)
based on idprophecy's kernel, thus it should be compatible with any Oreo ROM
built using QUVNTNM-TC, based on GCC 7.3.x
CPU underclocking (268,8 MHz)
several compiler optimizations enabled
sound contol by franciscofranco
lots of miscellaneous fixes and improvements
sysfs interface for Gentle Fair Sleepers and Arch power
power-efficient workqueues
Downloads
Latest version: here.
Argon kernel on MEGA
Argon kernel on AndroidFileHost
Thanks to:
@idprophecy
@dorimanx
@faux123
@Sultanxda
@CertifiedBlyndGuy
@osm0sis
@franciscofranco
@GalaticStryder
@nikhil18
the LineageOS team
and all the other authors of the hundreds of commits in Argon's github repo!
XDA:DevDB Information
Argon kernel for Oneplus One, Kernel for the OnePlus One
Contributors
Tomoms
Source Code: https://github.com/Tomoms/argon_kernel
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 16.1
Stable Release Date: 2019-08-11
Created 2018-08-24
Last Updated 2019-08-11
Reserved
How to set up the charging speed interface in Kernel Adiutor?
First thing, download the attached zip and decompress it. You'll find two .json files in it, place them in your internal storage and open KA. Go in the "Custom controls" tab, tap on the "+" button, choose "Import" and select the first of the files you downloaded, then import the second one too. Done! You can now delete the two files.
Keep in mind that the "0" value means that the standard charging logic will be used, and that the AC charging speed cannot be set to a value lower than 200 mAh, even though the slider allows you to set any value. If you set any value between 1 and 199, the driver will fallback to 200.
working fine with AEX 5.7.
is it compatible with oxygen os blobs or sultan blobs?
Running well for me on AEX 5.7.
antfior93 said:
is it compatible with oxygen os blobs or sultan blobs?
Click to expand...
Click to collapse
Starting from Oreo, all ROMs implement Sultan's camera, thus this kernel only supports Sultan's camera HAL.
New version is available
It's an important updates that brings lots of improvements (mainly "under the hood"), for more info I suggest you to check my Github repo!
Really nice work. Don't want to sound rude or something but is there a chance of getting a Pie build? ?
rolarocka said:
Really nice work. Don't want to sound rude or something but is there a chance of getting a Pie build?
Click to expand...
Click to collapse
Most probably, this kernel already works on Pie
You just need to flash it, then flash the Kernel Permissive Patcher (link - needed to set SELinux to Permissive before booting the OS) and you should be good to go. If you try, let me know the result!
What is the stock setting this kernel comes in? I want to try it but don't want to use root (for now). So I'm wondering what settings are default. Would kinda make this a flash and forget kinda kernel
twowheeler said:
What is the stock setting this kernel comes in? I want to try it but don't want to use root (for now). So I'm wondering what settings are default. Would kinda make this a flash and forget kinda kernel
Click to expand...
Click to collapse
The stock settings are kind of good. Not the best you could get, but close (I'll tweak the default configuration a little more in the future). If you're using idprophecy's ROM you will end up having maple as the default I/O scheduler, while if you're using other ROMs, I'm pretty sure you won't. Anyway, if you flash this kernel, I'm sure you'll benefit from the general improvements I implemented, which do not need any tweak to be enabled.
Works well on following ROMs;
-AOSiP 20180825( Argon v1 )
-TugaPower O25 ( Argon v2 )
Hi i installed it over AEX 5.7 . it works but charging is buggy. Keeps disconnecting and connecting .
tamboli007 said:
Hi i installed it over AEX 5.7 . it works but charging is buggy. Keeps disconnecting and connecting .
Click to expand...
Click to collapse
I have the same thing on all ROMs based on the LOS core. And this kernel is based, as I understand it, on the LOS core ... For example, with FranoKernel there are no such problems.
tamboli007 said:
Hi i installed it over AEX 5.7 . it works but charging is buggy. Keeps disconnecting and connecting .
Click to expand...
Click to collapse
MrYuraB said:
I have the same thing on all ROMs based on the LOS core. And this kernel is based, as I understand it, on the LOS core ... For example, with FranoKernel there are no such problems.
Click to expand...
Click to collapse
I experience the same issue when using a certain non-original (yet good-quality) cable. The weird thing is that if I charge the phone while it's turned off, it charges perfectly. Anyway, I can try to fix this issue. It shouldn't be difficult. I'll keep you informed.
Good to see you're still contributing for Bacon.
Tomoms said:
I experience the same issue when using a certain non-original (yet good-quality) cable. The weird thing is that if I charge the phone while it's turned off, it charges perfectly. Anyway, I can try to fix this issue. It shouldn't be difficult. I'll keep you informed.
Click to expand...
Click to collapse
Yesterday I tried to send you message, but it is why it is not sent... I agree
I've uploaded a new kernel!
Argon v3 is a small yet important update: it brings DDR bandwidth boost on screen unlock (basically, the RAM bandwidth is boosted when you unlock your phone so that opening an app immediately after waking the device from idle takes less time) and some general fixes & improvements for the kernel. More details are available on Github, as usual
Tomoms said:
I've uploaded a new kernel!
Argon v3 is a small yet important update: it brings DDR bandwidth boost on screen unlock (basically, the RAM bandwidth is boosted when you unlock your phone so that opening an app immediately after waking the device from idle takes less time) and some general fixes & improvements for the kernel. More details are available on Github, as usual
Click to expand...
Click to collapse
I've been loving the Kernel on AEX 5.7, but I've needed to reboot a few times because the screen won't turn on, or the screen has frozen.
Do you think that could be from the default underclock?
@Ruggerxpunk Same issue on my side since V2 version, but I don't have any logs cause I'm not using it at this moment.