I've tried a lot of performance-boosting and battery-saving mods, but none of them worked well together. It was a case of exclusive-OR, i.e. either set only for performance-boost OR only for battery-saving.
So I adapted 2 existing scripts (screenstate_scaling and battery tweak) and came up with SS4N1, which combines the best of both worlds ... performance-boost whenever I use my N1, and battery-saving whenever my N1 is idle.
SS4N1 : ScreenState for Nexus One
auto-switch the following settings based on screen-state (AWAKE/SLEEPING)
virtual memory
cpufreq governor
cpu scheduler
undervoltage
performance tweaks on startup
dialer optimization
remount partitions with noatime
storage/IO tuning
UI/homescreen optimization
network performance tuning
ability to enable/disable any or all of the above features
adapted from screenstate_scaling ([email protected]) & battery tweak ([email protected])
ROMs
Only tested for CM7 & MIUI, but should work with other AOSP ROMs that provide init.local.rc capability.
How to check ROM:
- Open adb shell or terminal session
- Type cat /init.rc | grep init.local.rc
- If no result, then your ROM is unsuitable for SS4N1
- If result is import /system/etc/init.local.rc or similar, then ROM is suitable
Click to expand...
Click to collapse
Kernels
SS4N1 has been available for a while now on IntersectRaven's kernel thread. Thanks again to IntersectRaven for letting me bum off his thread until now . Should also work with other N1 kernels by Redstar, Pershoot, Wildmonks and Cayniarb (Tiamat).
I'm using SS4N1 now with bbedward's Savaged-Zen kernel for Evo, as I compiled this awesome kernel for N1 with -0fast optimization using an experimental GCC 4.7.0 toolchain. Check below for download link.
Excerpt on overclocking from wildmonk ...
"Most users should be able to handle 1152MHz without any problems but some won't on 1190MHz. You'll know when your CPU can't handle a certain speed if you start to experience a sudden decrease in performance, lag, force closes, and spontaneous reboots."
Click to expand...
Click to collapse
How to enable SS4N1
Via adb shell or terminal session
SS4N1 is initially DISABLED by default. You must start an ADB shell or Terminal session then run the configuration script: sscfg
> Choose [1] Enable SS4N1
> Follow on-screen instructions to customize (refer to screenshots below)
> Exit with [6] *** Apply changes and exit ***
> Check logcat for SS4N1 entries
Via CKZTools SS4N1 GUI by zyr3x
CKZTools : ScreenState Gui for Nexus One
Click to expand...
Click to collapse
DOWNLOADS from my mediafire site
[MOD/SCRIPT] SS4N1
[KERNEL] Savaged-Zen for N1 (2.6.38.8, 128-1190, BFS/CFS, SWAP, NOOP, HAVS, AXI, HW3D)
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research if
* you have any concerns about features included in these ROMs, mods & kernels
* before flashing! 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.
*/
Changelog for SS4N1
# ===============
# SS4N1 changelog
# ===============
# Initial
# + port script from Spica to N1
#
# 20110329
# + added SD Card Speed Fix in TWEAK_STORAGE section
#
# 20110403
# + changed deprecated oom_adj to oom_score_adj for MAX_PHONE function and sscfg
#
# 20110403A
# + added auto-check of kernel version for oom-killer parameter for MAX_PHONE function and sscfg
# + updated check for cpufreq up_threshold for Auto Switch function
#
# 20110404
# + changed from init.d script to init.local.rc service to fix "hung-on-X" when not running dt-a2sd
#
# 20110505
# + modified to apply UV for Hybrid-AVS (Tiamat, SavagedZen, new-IR) and Customizable-AVS (old-IR)
#
# 20110519
# + added option for new interactiveX governor
# + removed tweaks for TCP/IP redirects
#
# 20110525
# + disabled dewonkifier feature in all preset profiles (thx 2 jyxent!)
# + tuned preset profiles to more conservative undervolt values
# + added option to display HAVS Min & Max VDD levels (CPU voltage table)
# + added option to display misc information (CPU info, kernel version, etc)
Yes finally! Thank you for bringing your expertise here! The all-in-one script perfect for everything! I've been a fan of this script for a long time now!
sir*mez said:
Yes finally! Thank you for bringing your expertise here!
Click to expand...
Click to collapse
You're most welcome! Not sure if I have the time to update this thread regularly, but I'll try my best as always.
Does it work with MIUI Roms?
aakaashjois said:
Does it work with MIUI Roms?
Click to expand...
Click to collapse
The last time I tried a few months back, yes it did.
ch33kybutt said:
The last time I tried a few months back, yes it did.
Click to expand...
Click to collapse
Thanks! It works, and quite well too!
aakaashjois said:
Thanks! It works, and quite well too!
Click to expand...
Click to collapse
Thanks for letting me know. I've updated OP and added MIUI in ROMs section.
What gains have you seen with this mod?
hotweiss said:
What gains have you seen with this mod?
Click to expand...
Click to collapse
That's the thing about this mod, it's ultimately up to the user to decide what type of profile they want. I put no stock in so-called benchmarks but UI is smooth and lag-free (especially with BFS kernel) whenever I use it and I get less than 1% battery decrease per hour overnight when phone is idle (from 100% to 96% in 7 hours).
Thanks ch33kybutt, it was about time you started your own thread for this great script! I've been using it since it's first incarnation, on MIUI alone with great success. Battery life is better, phone runs very smooth and the best thing is that you can set a different CPU governor for AWAKE/SLEEP modes plus all those tweaks.
I'd like more control over the audio volume, I feel as it's not loud enough; is it possible to add a tweakable audio boost function? Something that would make the ringtones ring louder?
Audioboost is built into the kernel upon compiling. But I think there's a volume hack app floating around the dev section that you can use.
ch33kybutt said:
Audioboost is built into the kernel upon compiling. But I think there's a volume hack app floating around the dev section that you can use.
Click to expand...
Click to collapse
Thanks for answering! I know about the app, I was wondering if that tweak can also be implemented in ss4n1.
Installation instructions?
Sent from my Nexus One using XDA App
PnkPwrRngr said:
Installation instructions?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
- Download latest zip
- Save to sdcard
- Boot phone to recovery and install zip
- Check OP for "How to enable SS4N1"
Hmmm....I think I may have to look into this one!
Seems interesting. Don't know how I missed this being posted 3 days ago.
ch33ky, are the settings in picture 8 your optimal settings?
I'm not 100% confident in making my own settings yet and I'd like to use that as a guide.
I actually set mine to whatever your first picture shows but before saving I realized picture 8 had different settings and since I flashed your kernel as well I figured I'd try out your settings..
uoY_redruM said:
ch33ky, are the settings in picture 8 your optimal settings?
I'm not 100% confident in making my own settings yet and I'd like to use that as a guide.
I actually set mine to whatever your first picture shows but before saving I realized picture 8 had different settings and since I flashed your kernel as well I figured I'd try out your settings..
Click to expand...
Click to collapse
I'm actually using the settings in pic 2 right now.
ch33kybutt said:
I'm actually using the settings in pic 2 right now.
Click to expand...
Click to collapse
How are they working for you? Picture8 settings are causing a pretty bad delay when loading multiple web pages at once and when typing it is falling WAY behind me. I have to stop every few seconds and let it catch up.
uoY_redruM said:
How are they working for you? Picture8 settings are causing a pretty bad delay when loading multiple web pages at once and when typing it is falling WAY behind me. I have to stop every few seconds and let it catch up.
Click to expand...
Click to collapse
That's probably because you're using SavagedZen governor in awake-mode. SavagedZen cpu governor is more attuned to battery-savings than performance-boost. Try switching to interactive governor instead.
Related
Code:
For Xperia Z Ultra only!
*** Disclamer
[B][COLOR="Red"]This requires an unlocked bootloader[/COLOR][/B]
This is an AOSP kitkat kernel for Xperia Z Ultra only!
[B][COLOR="Red"]I am not responsible if you brick your device[/COLOR][/B], but I will try to help you if things go wrong.
Introduction
This is a kernel I tweaked for RevolutionRom on Xperia Z1 and Z Ultra. This kernel is tweaked for better performance, battery life and smoothness. It works on all kitkat roms available for Xperia Z1.
It works on:
- Omni Rom, android 4.4 (not released yet, still testing this)
- RevolutionRom, android 4.4
- CM11, android 4.4 (will release an unofficial release soon probably)
You can find my sources on github: RevolutionDev kernel on github
Click to expand...
Click to collapse
Features
- Dual recovery: CWM Touch (Volume up) and TWRP Touch recovery (volume down)
- Faux Sound control
- GPU OC upto 600MHz
- Booting up at 2.1GHz (stock speed)
- Add OC upto 2,342 GHz
- Added VDD (Voltage Control)
- Extra Governors: Badass, Wheatley, Lionheart
- Extra I/O schedulars: Row, SIO, Fiops, BFQ
Click to expand...
Click to collapse
Installation instructions
- Reboot into fastboot
- Flash boot.img:
Code:
fastboot flash boot RevolutionKernel-ZU-v#.img (replace # with version nr)
fastboot reboot
- Enjoy
[/QUOTE]
Download
- RevolutionKernel v1.1
Click to expand...
Click to collapse
Changelog
Code:
== RevolutionKernel v1.1 [29/11] ==
Fix recovery?
== RevolutionKernel v1 [28/11] ==
- Initial release
- Dual recovery: CWM Touch and TWRP Touch recovery
- Faux Sound control
- GPU OC upto 600MHz
- Booting up at 2.1GHz (stock speed)
- Add OC upto 2,342 GHz
- Added VDD (Voltage Control)
- Extra Governors: Badass, Wheatley, Lionheart
- Extra I/O schedulars: Row, SIO, Fiops, BFQ
Click to expand...
Click to collapse
Thanks to:
Code:
- DooMLorD, Faux123 and a lot of other devs!
- sony for kernel sources
XDA:DevDB Information
[Android 4.4]RevolutionKernel for all kitkat source based roms [28/11], a Kernel for the Sony Xperia Z Ultra
Contributors
krabappel2548
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: V1 and future versio
Stable Release Date: 2013-11-29
Created 2013-11-29
Last Updated 2013-11-29
Reserved
== Kernel FAQ - GPU OC - Voltage Control - Sound Control==
Entering recovery
While booting, your device will vibrate and LED will turn puple while you see the sony kernel logo. When the phone vibrates, you need to press volume up or volume down to enter the recovery you like:
- Volume up: CWM Touch recovery
- Volume down: TWRP Touch recovery
GPU OC
OVERCLOCKING GPU WILL REDUCE BATTERY LIFE!
you can overclock/underclock GPU manually via scripts/commands...
[ how to do this manually/script ]
To check current max clock of GPU clock use:
Code:
cat /sys/devices/fdb00000.qcom,kgsl-3d0/kgsl/kgsl-3d0/max_gpuclk
To set GPU to particular frequency (overclock or underclock) use:
Code:
echo 533333000 > /sys/devices/fdb00000.qcom,kgsl-3d0/kgsl/kgsl-3d0/max_gpuclk
available scaling frequencies are:
Code:
[LIST]
[*]600000000 - 600 MHz
[*]533333000 - 533 MHz
[*]450000000 - 450 MHz (DEFAULT)
[*]320000000 - 320 MHz
[*]200000000 - 200 MHz
[/LIST]
Voltage Control
All credits for this interface go to Faux123!
WARNING!
DO NOT USE TOO HIGH OR TOO LOW VOLTAGES, SLOWLY increase the voltage one notch at a time for a particular frequency and do stability/testing for few hours. once you have verified that you CPU chip can handle that voltage ONLY then "Set at boot"/Use init.d script
You can either use an APP (like IncrediControl) [others mentioned in OP] or use an init.d script to do the work...
to see current voltage table use:
Code:
[B]cat /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels[/B]
to set voltage for a particular frequency:
Code:
[B]echo 1512000 1150000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels[/B]
will set 1512Mhz freq voltage at 1150mV
to reduce voltages for ALL frequencies:
Code:
[B]echo -25000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels[/B]
to increase voltages for ALL frequencies:
Code:
[B]echo +25000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels[/B]
Sound Control
Kernel level Sound Control
This feature has been added by faux123 himself!
The sources for this feature are covered under GPL and are released along with my kernel sources at my GITHUB repo.
[ WARNING ]
high volume can damage hearing!
Krabappel2548, DooMLoRD or faux123 are not to be held responsible if this damages ur headphones/speakers/etc
USE THIS AT YOUR OWN RISK!
There are two ways to use this interface.
manual control through sysfs interface
paid app (FauxSound Audio/Sound Control)
How to use the app FauxSound Audio/Sound Control is pretty self explanatory so I will write on how to control using the sysfs interface...
BEFORE DOING ANY ADJUSTMENTS EXIT THE APPS LIKE MUSIC PLAYER/etc!!
The interface to control the sound output is located at:
Code:
[B]/sys/kernel/sound_control_3[/B]
it has 4 control interfaces:
Camera MIC
Code:
/sys/kernel/sound_control_3/gpl_cam_mic_gain
Headphone
Code:
/sys/kernel/sound_control_3/gpl_headphone_gain
MIC
Code:
/sys/kernel/sound_control_3/gpl_mic_gain
Internal Speaker
Code:
/sys/kernel/sound_control_3/gpl_speaker_gain
each supports gain levels from 20 (-20) to 50 (+10), base is 40 (0)
(the number in the brackets correspond to the numbers displayed in the app)
say if u want to boost headphone output (both left and right channels) then use the following command:
Code:
echo "44 44" > /sys/kernel/sound_control_3/gpl_headphone_gain
u can also individually increase/decrease the gain for each right and left channel
similarly other interfaces can be controlled
TIP:
do not jump to maximum values as sometimes the headphones/speakers might start distorting the audio... slowly increase and do testing for the levels which suit you!
not all accessories will work well with boosted audio output
Thanks to romers,we can enjoy this powerful device! May I ask when does the rom release?And I can not wait! Thanks for romers!
fbfree said:
Thanks to romers,we can enjoy this powerful device! May I ask when does the rom release?And I can not wait! Thanks for romers!
Click to expand...
Click to collapse
I just released omnirom and revolutionrom is already available
Jozinek said:
sorry for question, but when to push volume button to start recovery? I try before LED blink, when LED blik, after LED blink, sometimes only once push, sometimes more, but only one succes enter to recovery from about 30 times
Click to expand...
Click to collapse
- Turn your phone off
- Press power button and immediately press and hold volume up
You'll see that the LED turn purple before it turns green for 2 seconds, and then you'll be in recovery. Let go of the volume button when you see the purple LED or when it vibrates.
Sent from my C6833 using Tapatalk
krabappel2548 said:
I just released omnirom and revolutionrom is already available
Click to expand...
Click to collapse
Anyway you make a contribution to the device, and I can do nothing:crying:
fbfree said:
Anyway you make a contribution to the device, and I can do nothing:crying:
Click to expand...
Click to collapse
Well, you can if you really want to Start reading!
Sent from my C6833 using Tapatalk
One special request if possible.
Could we get the slide to wake and slide to sleep feature please
Sent from my Xperia Z Ultra using Tapatalk 2
Sweet an OCed kernel. Cant wait to try this and report back tomorrow as soon as I get the phone...I am addicted to Ocing
shaolin95 said:
Sweet an OCed kernel. Cant wait to try this and report back tomorrow as soon as I get the phone...I am addicted to Ocing
Click to expand...
Click to collapse
Remember to backup your TA partition before you start playing around with custom ROMs and kernels.
Update coming up, newer prima wifi files Any other feature requests for this kernel?
krabappel2548 said:
Update coming up, newer prima wifi files Any other feature requests for this kernel?
Click to expand...
Click to collapse
awesome news..
i have a question for you...about the fauxsound patches you've made this kernel with...
i've not been able to retain any of my custom values on faux sound app as well as trickstermod... bought donate versions of both apps and still no luck... i have to have the sound control app running everytime i open the music application .. if i close that app, my settings get reset... i never had this problem with fancy kernel on my old galaxy nexus... i used to just use free version of trickstermod too... and my settings were always retained, even on boot... using this kernel, forget reboot, even not having the fauxsound/trickstermod app running in the background or just closing the music app, resets all customized value... not use if this characteristic is specific to your kernel or to Z Ultra... coz none of the other kernels available for the phone supports sound control anyway... so no other kernel to compare with... if there's a workaround, let me know... if its a bug, hope u can fix in the upcoming update.... thnx man... hope ur exams went well.
spicemaster said:
awesome news..
i have a question for you...about the fauxsound patches you've made this kernel with...
i've not been able to retain any of my custom values on faux sound app as well as trickstermod... bought donate versions of both apps and still no luck... i have to have the sound control app running everytime i open the music application .. if i close that app, my settings get reset... i never had this problem with fancy kernel on my old galaxy nexus... i used to just use free version of trickstermod too... and my settings were always retained, even on boot... using this kernel, forget reboot, even not having the fauxsound/trickstermod app running in the background or just closing the music app, resets all customized value... not use if this characteristic is specific to your kernel or to Z Ultra... coz none of the other kernels available for the phone supports sound control anyway... so no other kernel to compare with... if there's a workaround, let me know... if its a bug, hope u can fix in the upcoming update.... thnx man... hope ur exams went well.
Click to expand...
Click to collapse
I'll check faux's github for some updates about this Maybe it's because of 4.4 and it needs updates
krabappel2548 said:
I'll check faux's github for some updates about this Maybe it's because of 4.4 and it needs updates
Click to expand...
Click to collapse
not 4.4 mate... had the same problem when i was running your 4.3 carbon build as well.
krabappel2548 said:
Update coming up, newer prima wifi files Any other feature requests for this kernel?
Click to expand...
Click to collapse
Any joy with getting mobile data to work mate?
Mr. Droid said:
One special request if possible.
Could we get the slide to wake and slide to sleep feature please
Sent from my Xperia Z Ultra using Tapatalk 2
Click to expand...
Click to collapse
Could we get this request please ?
It's available on the nexus devices anz the HTC one and it will be perfect for a big device as ours
Sent from my Xperia Z Ultra using Tapatalk 2
Mr. Droid said:
Could we get this request please ?
It's available on the nexus devices anz the HTC one and it will be perfect for a big device as ours
Sent from my Xperia Z Ultra using Tapatalk 2
Click to expand...
Click to collapse
As long as we can disable it (for battery life sake)
Sent from my C6833 using Tapatalk
iBuzman said:
As long as we can disable it (for battery life sake)
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
It's usually an option to enable via faux app so ya it'll be perfect
Sent from my Xperia Z Ultra using Tapatalk 2
iBuzman said:
As long as we can disable it (for battery life sake)
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Yea on my nexus 5 they ate the battery real bad. Sweep to wake and double tap to wake as well. The process basically keeps your screen on hence the high battery drain. Used k-control app for faux trinity bricked and franco kernels
Sent from my Xperia Z Ultra using XDA Premium 4 mobile app
Very kernel I must say, only it seems after flashing it changes product name to 'honami' (Z1) so trying to flash anything for Z Ultra (togari) ends up with status 7. Just a detail
This is my version of crpalmer's kernel with some additional features:
-Android 5.0 support
-Sweep2Wake/Sweep2Sleep, DoubleTap2Wake (from Beastmode)
-force fast charge (credits to chad0989)
-kexec-hardboot support (for use with MultiROM, credits to Tasssadar for the multirom and the m7 patch I used)
-FauxSound (faux123)
-Moar overclockingz (up to 1890 mhz)
Note: Every chip is different, your device may not support these higher frequencies.
-GPU overclocking (up to 533 mhz) (credits to faux123, )
Note: Again, every chip is different, your device may not support higher frequencies.
-Additional CPU governors and I/O schedulers. Read about CPU governors here.
-Dynamic Fsync (faux123)
-Simple GPU Governor (faux123)
-L2 Cache overclock
-600 MHz bus overclock
-F2FS support (still no luck with getting this fully working, testers are welcome)
-LZ4 compressed kernel (faster boot)
-More TCP Congestion algorithms
-Lots of slimbus improvements thanks to poondog
For maximum performance, I recommend some optimized dalvik libraries (KitKat only):
-For 4.4.4 ROMs, use the "CM11 Dalvik_Final" zip in this post
-For older (4.4.2) ROMs:
-For 4.4.2 CM11-based ROMs released before March 1st, use my Sense dalvik libraries here.
-If you are using a 4.4.2 CM11-based ROM released after March 1st, or any ROM with this commit you will need to use the 4.4_qc-optimized_dalvik-cm11.zip here. Credits to kszaq for this one.
-For LiquidSmooth, use these Sense dalvik libraries here.
-Also, credits to kszaq because these were based on his flashable zip.
If you find any ROMs where none of these zips work, let me know and I will try to make one for that ROM.
I am not responsible for anything that happens to your phone. It is your device and your responsibility.
The following scripts are not required to change settings, they only exist as an alternative for people who don't want to use a third-party app. You can still use your favorite tuner app to tweak most of these kernel settings.
init.d tweaks
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 to configure it each time. 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. If run with a kernel that contains crpalmer in the version, it will rename mpdecision so it can't run. If you install another kernel it will then rename mpdecision back so that it will run in the new kernel. In addition to stopping the built-in mpdecision it will allow the following tweaks:
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 HTC's colour "enhancement" will be used, otherwise it will be disabled.
* If this file contains the string "m7" then it will use one of the colour enhancement that was used in the M7 kernel for a panel most like ours.
* E.g. adb shell touch /sdcard/crpalmer-color-enhancement
Click to expand...
Click to collapse
DoubleTap2Wake:
* This allows you to wake the device by double tapping in the bottom half of the screen, just above the hardware keys.
* To enable or disable, create the file /sdcard/jamiethemorris-dt2w
* If this file contains a 1, dt2w is enabled. If it contains a 0 it is disabled. Enabled by default.
Sweep2Wake/Sweep2Sleep:
* This allows you to wake the device by sweeping from left to right over the hardware keys, and sleep the device by sweeping from right to left.
* To enable or disable this, create the file /sdcard/jamiethemorris-s2w.
* If the file contains a 1, s2w and s2s are enabled. If it contains a 0, they are disabled. Enabled by default.
GPU Overclock:
* The GPU's max frequency is loaded from /sdcard/jamiethemorris-gpu-oc. If this file does not exist, the stock frequency of 400 MHz is used.
* To set this GPU overclock, you need that file containing the GPU frequency in MHz. Frequencies from 400 to 550 MHz are available.
* E.g. adb shell su -c "echo 450 > /sdcard/jamiethemorris-gpu-oc"
GPU Governor:
* You can choose from either ondemand, simple, or performance GPU governors. Default is ondemand.
* The governor is loaded from /sdcard/jamiethemorris-gpu-gov
* E.g. adb shell su -c "echo simple > /sdcard/jamiethemorris-gpu-gov"
Dynamic Fsync:
* From Faux123: The dynamic sync control interface uses Android kernel's unique early suspend / lat resume interface. While screen is on, file sync is disabled. When screen is off, a file sync is called to flush all outstanding writes and restore file sync operation as normal.
* Disabled by default. To enable or disable, create the file /sdcard/jamiethemorris-dyn-fsync. Use 0 to disable and 1 to enable.
Force Fast Charge:
* To enable or disable fast charge, create the file /sdcard/jamiethemorris-fastcharge
* Use 0 to disable, and 1 to enable. Disabled by default.
Intelliplug and Eco Mode:
* Intelliplug is a replacement hotplug driver for HTC's mpdecision, Eco Mode limits your device to dual-core operations.
* To enable or disable, use create the file /sdcard/jamiethemorris-intelliplug
* If the file contains 0, intelliplug and eco mode are both disabled and your phone will use crpalmer's hotplug driver. If the file contains a 1, intelliplug is enabled but eco mode is disabled. If the file contains the string 'eco', intelliplug and eco mode are both enabled. Both are disabled by default.
I/O Scheduler:
* To change the I/O scheduler, create the file /sdcard/jamiethemorris-iosched, and your device will use whatever I/O scheduler you specify.
* E.g. adb shell su -c "echo row > /sdcard/jamiethemorris-iosched"
Undervolt Override:
* This allows you to globally undervolt your device, but leave the 1836 MHz, 1890 MHz, and 1917 MHz frequencies at their default voltages.
* To enable or disable:
- First you need to find your PVS bin number. You can find this by checking the file /sys/module/acpuclock_krait/parameters/pvs_number.
- Create the file /sdcard/jamiethemorris-pvs and put your PVS number in that file.
- After a reboot, your device will automatically set the highest frequencies to the default voltages for your chip.
* If you are either lazy or confused, you can put '?' in the file and your phone will set itself to the voltages for a 'nominal' binned chip.
For the rest of the features and changelog, see crpalmer's original cm11 kernel thread.
Thanks: crpalmer for all of his help (before I started on this I didn't even know how to use git), coachcrey for originally inspiring me to do this, and all the other devs/builders here that may or may not know I'm learning from them constantly.
Downloads
Latest version:
Version 6.0.1
Older versions:
Older versions on Android File Host
Source:
Kernel Source
Build Tools
Recommended Settings
You can either use an app such as TricksterMod or Kernel Tweaker to set these parameters or use my scripts.
-Minimum CPU frequency: 162000
-Maximum CPU frequency: 1890000 for performance, 1512 for battery life, 1728 for balanced
-Undervolt: -100 for battery life, -50 for balanced/stability
-Color enhancement (script only): m7
-DoubleTap2Wake: Enabled for convenience or pretending you have a G2, disabled for battery life
-Sweep2Wake: Enabled for convenience, disabled for battery life
-Fastcharge: Disabled for safety, enabled for convenience
-GPU overclock: 500 MHz or 533 MHz for performance, 400 MHz or 320 MHz for battery life, 450 MHz for balanced
-GPU governor: ondemand for battery, simple for performance
-CPU governor: preservative for battery or balanced (decrease up threshold for faster response at the expense of battery), intelliactive for general performance, performance for benchmarking
-Intelliplug/Eco mode: Disabled for performance, enabled for balanced, Eco Mode for battery life
-I/O Scheduler: BFQ for balanced/stability, vr for performance
-Dynamic Fsync: Disabled for safety (less likely to have data loss in the event of sudden power off), enabled for performance, enabled for balanced
-Undervolt Override (script only): set jamiethemorris-pvs to your chip's PVS bin. Recommended for those with high overclock that are undervolted.
To make things easier for those who do not wish to use a third-party app, I have posted some zips with the necessary files. Just unzip them and put the files on your sdcard.
Default settings
Recommended settings (these are the settings I use, good performance vs. battery compromise
For best battery life
For best performance
XDA:DevDB Information
jamiethemorris's kernel, Kernel for the HTC Droid DNA
Contributors
jamiethemorris, crpalmer
Source Code: https://github.com/jamiethemorris/dna-kernel/tree/6.x
Kernel Special Features: dt2w, kexec-hardboot, overclock, fastcharge, fauxsound
Version Information
Status: Stable
Created 2014-01-28
Last Updated 2014-12-04
Changelog:
6.0.1
- All updates from CM:
- F2FS updates. Maybe F2FS works now (probably not).
- UID-based routing
- Enable selinux development
- Initial support for Lollipop (KitKat 4.4.4 ROMs are still supported)
5.8.2
- Updates from crpalmer:
* Update some video bandwidth parameters
* Interactive governor updates
- Pretty sure that's it.
5.8.1
- Updates from crpalmer:
* Patched up to linux 3.4.99 (latest version of as now)
* Patched up to latest CM (fixes a couple of CVEs, not a whole lot else was missing)
5.7.7.1:
-Force Fast Charge should now be fixed
-Make sure all cores are enabled when using performance CPU governor
5.7.7:
-Moved from Linaro 4.8.3 to 4.9.1
-Update modem restart commit from stock CM kernel
-No more intelliplug due to random reboots and the fact that simple plug works just fine. I may bring it back future versions.
-Reduce memory usage of input driver + oom tweaks that theoretically help a little bit with the touchscreen wake issue. I am still working on finding a real fix.
-SLIMBUS: m8 port, caf updates, new OC from poondog (better audio quality)
-Update BFQ to v7r3
-Update to latest F2FS driver
Older versions:
5.7.6:
-NOTE: There are 2 different zips for this version to avoid conflicts between crpalmer's simple plug and faux123's intelliplug.
-IMPORTANT: On the intelliplug version, intelliplug is enabled by default. If you disable intelliplug, there will be no hotplug driver running which will kill your battery quickly. So if you decide you don't want to use intellidemand, please use the simple plug version instead.
-Memory optimizations from Motorola
-Enable Linaro's power-efficient workqueues
-Intelliplug updates
-Merge latest CM commits
-Merge crpalmer's latest commits
-Update to Linux 3.4.86
-Update F2FS to the latest version
5.6.4:
-Hopefully fix voltage for "faster" binned chips
-Fixed random reboots when using intellidemand governor
-Fix scripts
-Disable intellidemand's active max frequency to prevent it from interfering with overclock
-Enable additional TCP congestion algorithms (thanks iHateWebOS)
-Sync s2w/dt2w/pocket detection with Beastmode
-Add Preservative governor (credits to bedalus)
-Update BFQ I/O Scheduler to v7r2
-Merge latest CM commits
-Merge crpalmer's latest commits
-Update to Linux 3.4.79
-Add LZ4 kernel compression/decompression for faster boot
-I think I forgot to mention this before, but I am now using a Cortex a-15 optimized Linaro toolchain.
5.5.5:
-Dynamic Fsync (Enable this only if you are sure your device is stable! If you have too many reboots, your data may get corrupted and you will have to reflash your ROM.)
-Simple GPU Governor
-Intelliplug hotplug driver with Eco mode (dual core operations). When this is disabled, it will use crpalmer's hot-plug driver.
-Intellidemand tweaks - I'm still working on this one, it tends to have random reboots at the moment.
-Decrease GPU OC to 533 MHz and increase bandwidth
-1917 MHz overclock is back, should be more stable now
-Sweep2wake + Sweep2Sleep
-Doubletap2sleep is not implemented in this version, sorry. Use your ROM's dt2s feature for now. I do plan on adding this back.
-Doubletap2wake can be used anywhere on the screen
-There should be scripts for all features, let me know if I missed something.
-Undervolt override for high overclocks. You can globally undervolt while leaving 1836 MHz, 1890 MHz, and 1917 MHz clocks unaffected.
-L2 cache overclock
-600 MHz bus overclock for 1674 MHz - 1917 MHz frequencies
-Support for F2FS filesystem (F2FS TWRP and MultiROM are coming as well, as soon as I have time to test)
-FIOPS I/O Scheduler
5.5.4.1:
-Now only one kernel zip
-GPU overclock is set with /sdcard/jamiethemorris-gpu-oc between 400 and 550 MHz. Default is 400.
-New wheatley governor
-Some more optimizations
5.5.4:
-Fixed video undderrun (blue flickering) issue with GPU overclock
-Updated FauxSound to 2.1
-Now only 2 kernel zips. One is stock GPU clock and the other is for 450 and 500 mhz overclocks. Default is 500 on the OC version.
-New governors: intellidemand, intelliactive, smartassV2, lagfree, badass, Lionheart
-New I/O Schedulers: zen, vr
-Improved touchscreen sensitivity - If this causes problems for people I will revert it.
-SLIMbus overclock which should in theory improve audio quality
-Various performance optimizations, see github for full details
5.5.3.4:
-Switch linaro optimization level from -03 to -0fast
-A few other optimizations, see github for full details
5.5.3.3: Up to 500 mhz GPU overclock. For now, there are 3 different downloads depending on what GPU frequency you want - stock (400 mhz), 450 mhz, and 500 mhz. There are no other changes, so if you don't want a GPU overclock there is no need to update to this version.
5.5.3.2: Up to 1890 mhz CPU overclock
5.5.3.1: Added FauxSound
Nice work man!
Sent from my HTC6500LVW using Tapatalk
Multirom link is in the op. I plan on getting s2w working soon also. The code is there, but it's made for an HTC one so it doesn't work yet. Technically logo2menu is in there as well lol
Sent from my Droid DNA using Tapatalk
Dt2w works perfect! Will this kernel be updates as CP pushes changes in the future?
HTC DNA
LG Optimus G
d08speed3 said:
Dt2w works perfect! Will this kernel be updates as CP pushes changes in the future?
HTC DNA
LG Optimus G
Click to expand...
Click to collapse
Yes, that is the plan
Sent from my Droid DNA using Tapatalk
CM double tap to sleep. Doesn't work well with dt2s. It turns off then back on.
HTC DNA
LG Optimus G
---------- Post added at 07:57 AM ---------- Previous post was at 07:56 AM ----------
d08speed3 said:
CM double tap to sleep. Doesn't work well with dt2s. It turns off then back on.
HTC DNA
LG Optimus G
Click to expand...
Click to collapse
Edit: turning the CM dt2s works. I'm guessing you have this enabled for status bar double tap to sleep?
HTC DNA
LG Optimus G
d08speed3 said:
CM double tap to sleep. Doesn't work well with dt2s. It turns off then back on.
HTC DNA
LG Optimus G
---------- Post added at 07:57 AM ---------- Previous post was at 07:56 AM ----------
Edit: turning the CM dt2s works. I'm guessing you have this enabled for status bar double tap to sleep?
HTC DNA
LG Optimus G
Click to expand...
Click to collapse
Just to clarify, in that last edit you're just saying that turning dt2s off in the settings makes the kernel's version of dt2s work right? Cause that's what I'm seeing on my phone. Thanks for the heads up, I enabled the dt2s setting a while ago but I always forget that I did so I hadn't tested it yet.
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
Just to clarify, in that last edit you're just saying that turning dt2s off in the settings makes the kernel's version of dt2s work right? Cause that's what I'm seeing on my phone. Thanks for the heads up, I enabled the dt2s setting a while ago but I always forget that I did so I hadn't tested it yet.
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
Yea. Turning off CM's dt2s settings off makes your dt2s work. I see it enabled in sys>android_touch.
HTC DNA
LG Optimus G
d08speed3 said:
Yea. Turning off CM's dt2s settings off makes your dt2s work. I see it enabled in sys>android_touch.
HTC DNA
LG Optimus G
Click to expand...
Click to collapse
Got it. Looks like this was bad timing to release a kernel, apparently we're moving from m7 to msm8960 soon...
Sent from my Droid DNA using Tapatalk
i love the convenience of s2w and dt2w and now we have it for aosp and sense! what a awesome time this is to own a dna
Swipe or double tap to sleep isn't working. Normal?
-DroidIsDNA- said:
Swipe or double tap to sleep isn't working. Normal?
Click to expand...
Click to collapse
Dt2s is working for me. S2w isn't functional yet. Is dt2w working for you?
If you have dt2s enabled in your ROM settings, make sure you disable it as out counteracts the kernel's dt2s.
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
Dt2s is working for me. S2w isn't functional yet. Is dt2w working for you?
If you have dt2s enabled in your ROM settings, make sure you disable it as out counteracts the kernel's dt2s.
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
I don't think I have it enabled in probam. Dt2w doesn't work
-DroidIsDNA- said:
I don't think I have it enabled in probam. Dt2w doesn't work
Click to expand...
Click to collapse
Did you follow the instructions in the op to enable it? It should be enabled by default I think but if not I put instructions there
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
Did you follow the instructions in the op to enable it? It should be enabled by default I think but if not I put instructions there
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
Oops I meant double tap to sleep I'm sorry
-DroidIsDNA- said:
Oops I meant double tap to sleep I'm sorry
Click to expand...
Click to collapse
That's weird then. You have to double tap the status bar in case you didn't already know that. If that's still not working, then enabling the ROMs version of it in settings should do the trick.
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
That's weird then. You have to double tap the status bar in case you didn't already know that. If that's still not working, then enabling the ROMs version of it in settings should do the trick.
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
Ohhhhhh, yeah I was double tapping above the menu keys. Status bar works flawlessly. Thanks! Idk if its in the op or if I just blanked out
-DroidIsDNA- said:
Ohhhhhh, yeah I was double tapping above the menu keys. Status bar works flawlessly. Thanks! Idk if its in the op or if I just blanked out
Click to expand...
Click to collapse
It actually wasn't in the OP, I just added it for clarification.
Is force fast charge on by default?
HTC DNA
LG Optimus G
Thomas.Raines presents
The Lightning Zap! kernel for the Nexus 4 Mako
ATTN:
I thomas.raines, nor it's affiliates claim responsibility for anything you do to damage, destroy, brick, explode, or otherwise mess up your device.
{
"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:
Improved performance
Improved battery life
Improved network speeds
Improved boot times
Smoother scrolling
Better responsiveness
Cleaner file systems
Governor tweaks for amazing speed and performance without sacrificing battery life
Improved Memory and Ram tweaks
Improved Internet speed
kexec hack for dual booting with MultiRom.ak
Overclocked cpu
sweep2wake/doubletab2wake (disabled by default. must be enabled via script by uncommenting lines 7 and 8 in /etc/init.d/05s2w then reboot)
Amazing kernel tweaks, build.prop mods, init.d scripts and more!
Governors:
POWERSAVE
USERSPACE
ONDEMAND
INTERACTIVE
BADASSS
INTELLIDEMAND
LIONHEART
ONDEMANDX
SMARTASS2
GALLIMAUFRY
LAZY
io-schedulers
NOOP
DEADLINE
CFQ
SIO
See 2nd post for download links and changelogs
Instructions:
Make a backup
Download .zip to PC
Transfer .zip to your sdcard
Or just download it straight to your phone
Reboot to recovery
Flash
Reboot
Wait 10 minutes
Enjoy the Lightning Zap!
See 2nd post for download links and changelog
**The first boots usually takes the longest especially after a fresh install. If you pull a logcat during the first boot, you may see a few errors with the vacuum script. This is normal, and will be "fixed" after the phone has built the databases for the apps.
Please allow 24 hours after install and 1 full charge cycle before reporting results. Always provide me with a logcat with any issues you may experience.
Source Code:
mako-lz kernel
vendor_lz-kernel (LZ vendor files for ROM compiling)
Special thanks to:
jrummy16 for Root Browser Lite
show-p1984 for bricked kernel (used for rebase)
Download Links and Changelogs
Nexus-4-Mako-LightningZap_p5.1.2.zip
cpufreq adjustments
led driver adjustments
Import RB tree adjustments from Motorolla
Input packet management adjustments
EOL
https://github.com/LightningZap/and...mmit/9ee0e0e3f9cf2733c554f0da69724c79f71cb4d9
Nexus-4-Mako-LightningZap_p5.1.1.zip
Fixed voltages and frequencies
uv_bin overhaul
Fixed inconstancies in installer
Guys and gals with slow binned cpus, MAKE SURE YOU SET THE MIN VOLTAGE TO 700. Or you will get random reboots like crazy. On a side note. I would strongly suggest wiping dalvik (art) and cache before flashing. If not, your device may shutdown immediately after it is done booting. Nothing to really worry about, just simply hold the power button for a few seconds till the google screen appears, and you should be good.
Nexus-4-Mako-LightningZap_p5.1.0.zip (dl link unavailable)
Major upstream update (166 commits)
TCP tweaks
Added GCC optimizations
Updated linaro toolchains
If you are having random reboot issues or you get stuck on the Google screen, try raising your min voltage to 700MHz. If that still doesn't work, let me know here. Please try to attach a dmesg log and make sure you tag me in the post so I don't miss it (@thomas.raines)
Enjoy!
Nexus-4-Mako-LightningZap_p5.0.2.zip
Added intelli_plug to handle CPU hot swapping
Disbabled MSM_HOTPLUG
Bumped to 5.0.2
Set min CPUFREQ to 9450
Changed Aroma installer defaults to my recommendations.**NOTE** If overclocking, I recommend using higher voltage min...
Included a LightningZap! tailored init.mako.rc that sets vibrator amp to 100, disables all that unneeded cpu governor junk and more...
Nexus-4-Mako-LightningZap_p5.0.1.zip
Bump to 5.0.1
added 5.0 emmc support
speedup /proc/net/unix
network speed tweak
exec_hardboot:updated with more current patch.
Avoids bogus error messages for the suspend aborts.
Avoid using global variable total_cpus
added sound control Thanks @faux123
Nexus-4-Mako-LightningZap_p5.0.zip
Update kernel to Lollipop 5.0
Added script to fix wonky sdcard issue. (5.0 was changing it from /sdcard/<your files> to /sdcard/0/<your files>. Script prevents that from happening and all is well)
All the same greatness of Lightning Zap! 4.4.X with no issues
Enjoy folks!
Nexus-LightningZap_p4.4-3.3.zip
Added remaining uv options to table
Backlight dimmer options
USB Fast Charge
CPUFREQ:rework of all tables. New implementation of freq's using PVS.
cpufreq: properly sync current scaling governor across all cores
Slight boost in L2 cache. Corrected number of cpufreqs
enable max screen off freq on/off support
added RESTRICT_ROOTFS_SLAVE
Added fsync on/off support:Enabled by default
Added f2fs and exfat support
Inspired by elementalx's flashing format using Aroma Installer, I have revamped cpufreq and uv tables, as well as added a few options.
You can now set your default options with the installer. Just follow the prompts as you go thru.
The flashing instructions are the same; however, at the end of the flashing process, you will have an option to save the log. I would recommend doing so. But only share it with me if you have an issue.
The installer is not without it's little glitch. Occasionally, your screen might flash and appear to be going from screen to screen in recovery after the installation process has finished. Nothing to worry about. Just let it settle down and then reboot. I only had this issue in philz_touch.
With the L2 cache boost, and the lightningzap booster, those pesky random reboots due to L2 cache failing to sync are a thing of the past.
One thing to note, when selecting your cpufreq, this will set you MAXIMUM. Meaning, even with an app, you will not be able to go over the default you set. Select carefully. I would recommend setting core 1 to the highest you desire and then setting the other 3 cores lower in the case you need more. And just use trickstermod to adjust as necessary. Oddly enough, even if you set the cores individually and cores 2-3 lower than core 1, your max will be whatever core 1 was set on. But if you adjust them reverse to what I said, then you will be limited to whatever default core 1 is. Hopefully that makes sense.
I have also linked all cores. This means that when you use Trickstermod app to set your cpufreq, it applies it to ALL cores. I have notice some apps, like kernel tweaker, do not do this as they are not written correctly for multi-core processors. Most of the defaults like voltages, fsync, and sweep2* can still be controlled with trickstermod even if you disable them during install.
TBH the only thing you cannot change, is your max cpufreq (meaning, if you choose 1512(stock) as your max during install, the only way to raise it is to re-install the kernel. However, you can still fine tune it).
Another note, max freq is set to 1620; however, if you can still set it higher, will just have to use trickster mod to fine tune it...
Previous Changelogs and links
Nexus4-LightningZap_p4.4-3.2.zip
Dropped mpdecision
Added msm_hotplug (With updates)Reconfigured voltage table. Boots @ 700000uV on 94500mHz
Possible UV/OV is now 600000uV min 1450000uV max (Be careful with this as too low/high for your device could cause instability. Test your settings BEFORE setting it to set at boot. If you go below the thresholds, your device will become EXTREMELY unstable, reboot, say you should have listened and then blow up in your face...lol. Not really, but it will go into a kernel panic and reboot)
And FYI, the voltages are reported in uV not mV. If you don't know, 1000uV = 1mV; therefore, the kernel boots @ 700000 is 700mV...
Nexus4-LightningZap_p4.4-3-1.zip
Added sec_dvfs_dual. All CPU's handle hotplugging better now
Added lulzactive cpu gov
add row and fiops schedulers
set fiops as default scheduler
Working on getting smartassv2 to compile...
added LCD Gamma Hack from faux kernel
Nexus4-LightningZap_p4.4-3.zip
2 stage update on this one.
Stage 1
Dropped bricked base and went back to kk4.4 (AOSP & CAF) base
Revamped OC/UV. Still compatible with Trickster Mod app
(Because I dropped the bricked base and went back to original base, you won't have full control on thermald and mpdecision for now. Working on adding it, please be patient)
Stage 2 With results of the latest poll in mind:
Dropped the following governors:
Conservative
Gallimaufry
Ondemandx
Userspace
Made Intellidemand/deadline as default
Nexu4-LightingZap_p4.4-2.zip
Complete revamp of base. Used bricked kernel as base (thanks to show-p1984)
Created new branch for revamp (bricked-lz) Keeping kk4.4 branch for now.
Per user requests:
Moved RootBrowser to /data **Must remove it from /system/app prior to flashing
Removed voltage control app. No longer compatible with vc.
Fully compatible with TricksterMod app
Vote on the next poll for your favorite governor & io-scheduler (If I can get it setup right)
Nexu4-LightingZap_p4.4-1.2.zip
Reverted back to Linux Android Kernel version 3.4.0 due to instability
Bumped to p4.4-1.2
Revamped mako_defconfig in order to enable loadable modules
changed build cifs & tun as modules
Left WiFi modules as hard-coded drivers to avoid WiFi issues on other Roms (Sorry about this one guys and gals)
Nexus4-LightningZap_p4.4_1.1.zip
Bumped to latest stable kernel version 3.84.4 (LightningZap version p_4.4-1.1)
Added sweep2wake and doubletap2wake from bricked-kernel Mako (special thanks to show-p1984)
sweep2wake and doubletap2wake is disabled by default. To enable one or both, refer to this post
Nexus4-LightningZap_p4.4_1.zip
Initial release
Just a note, some combinations of governors and io-schedulers don't mix well and you could experience instability like freezes and reboots. Before posting an issue, change your governor and or io-scheduler. This will help me narrow down any issues. And by all means, please let me know which combination you experienced an issue with, and what exactly occurred.
Note that certain ROMs like Omni and Ubuntu Touch that use a modified initramfs or some other kernel modification, may not work with this kernel. I am working on it now.
thomas.raines said:
Hold up... getting the link now
Click to expand...
Click to collapse
Great seeing you here! My brother uses your kernel on his E4GT and he likes it a lot.
I hope you do good work for the N4 as well. :good::good::good::good:
thomas.raines said:
Hold up... getting the link now
Click to expand...
Click to collapse
The OP says it's for Blaze 4G You might want to edit it to avoid confusion Thanks for your work, sir. I had use yours in my Blaze 4G.
Maybe a bit explanation of governors? Like for lionheart and galli
Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
Wow I saw you in the Blaze fourms. Great to see you developing on the N4!
Sent from my Nexus 4 using xda app-developers app
Saw you in the et4g forums
Sent from my Nexus 4 using Tapatalk
I'm glad people say this is real looked like a hoax to zap my n4!
So who has flashed this?
sent from a toilet...
phone always fc's for me on 3 different AOSP roms
Thanks for the kernel......Testing-----------------:good:
CallMeAldy said:
phone always fc's for me on 3 different AOSP roms
Click to expand...
Click to collapse
Can you be more specific?
CallMeAldy said:
phone always fc's for me on 3 different AOSP roms
Click to expand...
Click to collapse
by chance you tried it in the rom Purity? by that I have not had problems with.:good:
Hello.
Thank you for you hard work.
I was wondering which governor and scheduler do you suggest.
Edit : Can you possibly add swipe to wake?
Yadro said:
Hello.
Thank you for you hard work.
I was wondering which governor and scheduler do you suggest.
Edit : Can you possibly add swipe to wake?
Click to expand...
Click to collapse
The governor and scheduler really varies from person to person and dependent upon their usage of the device. I think Lionheart with noop is a great combination for power and battery saving from the light user all the way up to the medium user which is why I made it default. Some have suggested that intellidemand is very good as well, but sacrifices a bit of battery saving yet adds a slight bit of performance.
I have considered adding sweep 2 wake on some of my other kernels, but haven't truly decided on it yet. I think I'm going to give it a try tonight though.
Update available
Read changelog for details
To enable sweep2wake and doubletab2wake:
use an app like kcontrol
in and adb shell or in terminal on the phone type:
Code:
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/doubletap2wake
Or, I have made it even easier. In root browser, navigate to /system/etc/init.d. Open the script named 05s2w and remove the # from lines 7 and/or 8, then reboot. This will enable sweep2wake and/or doubletab2wake. You can enable both or just one of them.
thomas.raines said:
The governor and scheduler really varies from person to person and dependent upon their usage of the device. I think Lionheart with noop is a great combination for power and battery saving from the light user all the way up to the medium user which is why I made it default. Some have suggested that intellidemand is very good as well, but sacrifices a bit of battery saving yet adds a slight bit of performance.
I have considered adding sweep 2 wake on some of my other kernels, but haven't truly decided on it yet. I think I'm going to give it a try tonight though.
Click to expand...
Click to collapse
Thanks! So far i'm enjoying this kernel a lot! Working out for me on XenonHD.
---------- Post added at 08:49 AM ---------- Previous post was at 08:48 AM ----------
thomas.raines said:
Update available
Read changelog for details
To enable sweep2wake and doubletab2wake:
use an app like kcontrol
in and adb shell or in terminal on the phone type:
Code:
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/doubletap2wake
Or, I have made it even easier. In root browser, navigate to /system/etc/init.d. Open the script named 05s2w and remove the # from lines 7 and/or 8, then reboot. This will enable sweep2wake and/or doubletab2wake. You can enable both or just one of them.
Click to expand...
Click to collapse
okay i'll try that now too.
---------- Post added at 09:00 AM ---------- Previous post was at 08:49 AM ----------
Why is the default read ahead on the scheduler 16xxx? Isn't that a bit much?
M3drvr said:
Why is the default read ahead on the scheduler 16xxx? Isn't that a bit much?
Click to expand...
Click to collapse
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
thomas.raines said:
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
Click to expand...
Click to collapse
I wasn't too worried. Just wondering. Thanks! So far the new kernel very good. The first 5 minutes of it being installed there were quite a few lags and glitches. But after that, its smooth as ever!
thomas.raines said:
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
Click to expand...
Click to collapse
That's to be expected while the kernel settles in. Glad you're enjoying it!
Sent from my Nexus 4 using xda app-developers app
Should MPDecision be enabled if using the noop scheduler and Lionheart governor? Or whats your recomendation?
ChronoKernel Settings
for Chrono Kernel
Based on "NovaThor Settings"
Base features:
All "NovaThor Settings" app features
Update kernel, check latest release, view changelog
Swap storages
Full CPU control
Adjusting voltages for each frequency
CPU freq settings for suspend settings
Full BLN control
Adding modules to autoload (tcp, vpn, governors, schedulers, logcat)
ABB-charger management
Frequency of a display control
Creating logcat and kmsg
Thanks to:
ChronoMonochrome for the kernel and support!
Rox, zwliew, frapeti, t4n017 for "NovaThor Settings" app
4pda community for a test of early versions, bugreports and responses!
CyanogenMod Team for "Device Settings" app
xda community for a test and patience!
Download: View attachment ChronoKernelSettings-0991-beta.apk
Older versions:
View attachment ChronoKernelSettings-099-beta.apk
View attachment ChronoKernelSettings-0981-beta.apk
View attachment ChronoKernelSettings-097-beta.apk
View attachment ChronoKernelSettingsforStock-097-beta.apk
View attachment ChronoKernelSettings-096-beta.apk
View attachment ChronoKernelSettingsForStock-096-beta.apk
View attachment ChronoKernelSettings-095-beta.apk
View attachment ChronoKernelSettingsforStock-095-beta.apk
View attachment ChronoKernelSettings-09-beta.apk
View attachment ChronoKernelSettingsforStock-09-beta.apk
Buglist:
-
Old changelog:
0.9.7-beta:
- Added "Statistics of the processor." Thanks to @storm717 for the source code of CpuSpy!
- Added "Selecting frequencies". Although you can't disable 800 MHz and 1000 MHz, app still sends a command to enable these frequencies after a reboot.
- Added steps for extreme undervoltage for 100 MHz, 200 MHz, 400 MHz.
- Added checkbox "Disable second core."
- Added a choice of states for APE_OPP and DDR_OPP. But, strangely, only when choose the state 0 for apeopp and ddropp, the values don't change in mcde_screenon_opp, when choosing other states, apeopp and ddropp changes without problems. Nevertheless, thanks to @ChronoMonochrome for the help!
- Returned those settings that have been removed in the last version, but I removed the choice of presets for minfree - think of another implementation.
- Fixed bln_wakelock after a reboot.
0.9.6-beta:
- Optimization of the application for stock firmwares was performed.
- Added CPU activity. Now it is possible to change a governor, frequencies of the processor and schedulers of internal and external memory, and also change undervolting for each frequency on r2.17!
- Added the way of change of swap storages for stock.
- Added two Holo themes and two system themes. If you use stock firmware, MIUI (etc), you can choose system theme for apply firmware theme in app. Please, don't write if system theme will be coincide with Holo and Material themes on AOSP-based roms.
- Added "Enable increased smoothness" setting. Thank you, ChronoMonochrome!
- Added "Set a preset for minfree" setting.
- Added readahead for external storage.
- Added "Disable NovaThor Settings" (it will be "frozen" and hidden).
- Added touchboost for interactive and Zenx.
- Rewritten path options for dt2w and s2w (for r2.17).
- Fixed activation bln_wakelock.
- BLN and "Disable NovaThor Settings" items for stock firmwares are not available. Unfortunately, I did not manage to see the work BLN on stock. If someone gets enabled BLN (of course, without Xposed), please let me know.
- Removed unnecessary options and settings (at the time r2.17).
0.9.5-beta:
- added "Enable zRam". It works with init.d script.
- added choice of themes (please, test the Holo Light theme).
- choice of modules of file system is added (exfat, nilfs2, ntfs).
- added creating a dmesg is added to "Settings". Now logcat, dmesg and kmsg are created with time tag.
- option "Disable Autoboost" in GPU is returned. Thanks, Kolan007!
- change of readahead is corrected (this setting is used listpreference)
- path to a touchboost is changed.
0.9-beta:
- Initial release for xda
full changelog on russian
Ok, let's get started.
fluffi444 said:
1) Screen: Enable Touch boost: This set "only" APE boost to ON - Maybe an switch for DDR boost (bt404_ddr_boost) and an switch for each value for APE/DDR (25/50/100) would also be nice.
2) I/O: read_ahead_kb values are not set correctly - This was and is an error which was in NTsettings since beginning
3) CPU Undervolting: This could be a bit dangerours because the original setting of Chrono is already well optimized - even -12,5/25 could force reboot - Especially for the higher freq from 800-1200. Maybe its better only to undervolt the lower steps (further testing needed)
Click to expand...
Click to collapse
1. I did not do it because I have difficulties in the interpretation of APE/DDR :/
2. I'll think about how to fix it
3. I have no problem with increasing the voltage to 75.0 as well as with decreasing voltage to 75.0.
Anyone having difficulty with that?
mars_army said:
1. I did not do it because I have difficulties in the interpretation of APE/DDR :/
3. I have no problem with increasing the voltage to 75.0 as well as with decreasing voltage to 75.0.
Anyone having difficulty with that?
Click to expand...
Click to collapse
Thanks for copying my post to new thread...
1. Maybe @ChronoMonochrome can say a word to touchbooster and the infuence of APE/DDR and thier values 25/50/100
3. Yes I had... I set (just for a short test) to -50 and got instant reboot. As I said: I think Chronos voltage table for higher freq is well optimized and already quite low...
I'm using latest Rel R2.14.5 - I don't know for which kernel version you optimzed your Settings?!
As far as I know Chrono changed the LiveOPP table in the newer releases, also.
fluffi444 said:
Thanks for copying my post to new thread...
I'm using latest Rel R2.14.5 - I don't know for which kernel version you optimzed your Settings?!
As far as I know Chrono changed the LiveOPP table in the newer releases, also.
Click to expand...
Click to collapse
The values for voltage are selected in accordance with 2.14.3, including the values taken from the init.d script "00liveopp_voltage_fix".
Please read this for test undervoltage.
fluffi444 said:
Thanks for copying my post to new thread...
1. Maybe @ChronoMonochrome can say a word to touchbooster and the infuence of APE/DDR and thier values 25/50/100
Click to expand...
Click to collapse
I left here the concrete APE/DDR settings, because by kernel supported as lowest states as APE25/DDR25. For powersaving we can change these values via interface /sys/devices/pri_lcd_ws2401.0/mcde_screenon_opp (don't remember if s6d has it - will reimplement soon). By default are used DDR50/APE50(APE25/DDR25 are causing problems on some phones like display blinking, long wakeup time etc.), and touchbooster set APE100 when you touch the screen For good smoothness usually enough APE100/DDR50 which are defaults for touchscreen interfaces. For more smoothness set also DDR100 (but I think it will drain the battery too fast).
3. Yes I had... I set (just for a short test) to -50 and got instant reboot. As I said: I think Chronos voltage table for higher freq is well optimized and already quite low...
Click to expand...
Click to collapse
There are no big changes in compare with old TC's kernels. It's almost same voltage table as in liveopp 1.0.1, and IMO only one stable for most users. Although it's not well optimized in term of powersaving, because some steps use same voltage. I also admit that it's not good idea to lower voltage for all steps by same value - because some steps can't be undervolted even by -50 mV, when some steps can use as low undervoltage as -275 mV.
One more thing to mention:
GPU: The checkbox for deactivating Mali Boost is missing. Therefore the setting in "Clock Speed" (Set static gpu clock speed) has no function because Mali Boost is alway on...
fluffi444 said:
One more thing to mention:
GPU: The checkbox for deactivating Mali Boost is missing. Therefore the setting in "Clock Speed" (Set static gpu clock speed) has no function because Mali Boost is alway on...
Click to expand...
Click to collapse
Yes, Kolan007 (from 4pda) reminded me of this, I will add this setting to next update. By the way, how wrong the app exposes values for readahead?
mars_army said:
Yes, Kolan007 (from 4pda) reminded me of this, I will add this setting to next update. By the way, how wrong the app exposes values for readahead?
Click to expand...
Click to collapse
Take your time - no hurries!
Regarding readhead: 512 is set OK after an reboot- if you change to 1024 it shows as 1152 in file. Looks like the more you change the value (without reboot) the more the value changegs to a wrong direction... For me it looks like that there is an calculation error somewere...
I set 1024 (via init.d) after I set now 512 in app it shows as 640 in file
If I go back to 1024 in app it will give me 1152
2048 gives me 2048 - strange
Back to 512 gives me again 640... etc....
Next time 2048 in app gives me now 2176 - more than strange
EDIT
Looks like there is somewhere an "128 error" in calculation....
fluffi444 said:
For me it looks like that there is an calculation error somewere...
Looks like there is somewhere an "128 error" in calculation....
Click to expand...
Click to collapse
Really a problem in mathematical calculations. How it works now:
(("displayed value" / "128"+"1")*"128"="result".
Example:
(("4096"/"128")+ "1")*"128"="4224").
I tried to replace 1 to 0, but the value is set back one step. I will think that how to fix it.
The easiest solution is replace the way of setting value on listpreference (like in FSync settings).
Undervolting doesn't work with my ACE 2
Ave_Hornet said:
Undervolting doesn't work with my ACE 2
Click to expand...
Click to collapse
Please check your init.d scripts... Maybe there are some settings (chmod 444) that preventing changes for GPU and/or CPU undervolting.
fluffi444 said:
Please check your init.d scripts... Maybe there are some settings (chmod 444) that preventing changes for GPU and/or CPU undervolting.
Click to expand...
Click to collapse
I make a clean install and all works fine. Anyway thanks for help.
New version is UP!
added "Enable zRam". It works with init.d script.
added choice of themes (please, test the Holo Light theme).
choice of modules of file system is added (exfat, nilfs2, ntfs).
added creating a dmesg is added to "Settings". Now logcat, dmesg and kmsg are created with time tag.
option "Disable Autoboost" in GPU is returned. Thanks, Kolan007!
change of readahead is corrected (this setting is used listpreference)
path to a touchboost is changed.
bln_wakelock inclusion does not work ( I will think how to fix it ) .
setting ape/ddr will in the next version : /
full changelog on russian
Download version for custom roms
Download version for stock firmwares
[*] added "Enable zRam". It works with init.d script.
Works!
[*] added choice of themes (please, test the Holo Light theme).
Lovely! Nice and perfect! But Holo Light looks the same as Material Light - In my opinion
[*] choice of modules of file system is added (exfat, nilfs2, ntfs).
not tested
[*] added creating a dmesg is added to "Settings". Now logcat, dmesg and kmsg are created with time tag.
works.
[*] option "Disable Autoboost" in GPU is returned. Thanks, Kolan007!
Good!
[*] change of readahead is corrected (this setting is used listpreference)
Works! First time that this works as it should!
Thx for your work!
fluffi444 said:
But Holo Light looks the same as Material Light - In my opinion
Click to expand...
Click to collapse
I assumed that appcompat-21 contains resources for Holo, so I added the Holo Light. In next versions will be only two themes
fluffi444 said:
Thx for your work!
Click to expand...
Click to collapse
Thank you for report and test
Hi @mars_army
For now APP work great !!
You think about profiles for this APP? Like gaming,powersaving,etc.?
It would be nice
Cheers
Ave_Hornet said:
Hi @mars_army You think about profiles for this APP? Like gaming,powersaving,etc.?
Click to expand...
Click to collapse
I thought about it, but it's still in plans But first, I want to change the application's UI to group some settings.
Thank you!
I made a simple .zip to install it from Recovery.
!! This package removes the NT APP !!
If I downloaded new kernel, the app ask me to boot into recovery... Pressing OK...
And nothing happens... Only this moving circle saying "please wait..."
*** This kernel is now end-of-life and not supported nor actively developed anymore !!! ***
Hi all,
some of you know me from the other OnePlus or Samsung devices areas, where I provide my kernels already for more than five years to OnePlus 5, 3T, 3, 2, one and X, Galaxy S5, S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.)
Now I own a OnePlus 5T device and decided to port my kernels also to this device.
Please note:
I am not heading to have as many features as possible implemented, this is not my design goal. If you are more into that, move on to other, good existing kernels. If you are searching for a good mix of improvements and new functions while not sacrificing stability, you are welcome here (see below the history section for more info).
Compatibility
Important: This kernel is only meant to be compatible with official OnePlus OOS and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
To add: A community build is NOT an official build supported here. If you use a community build and have issues, don't complain or even report.
Important notes
Read first, especially when you are new to my kernels:
http://wiki.boeffla.de
Boeffla-Kernel uses the anykernel concept = Flash stock kernel of rom first !
This kernel is ONLY compatible to OxygenOs stock, nothing else !!!
If you are using a custom rom that bases on OxygenOs, it might work. However, if it does not work, do not expect me to do tweak to make the kernel running with your favorite rom. I would not do it - my one and only reference is OxygenOs stock.
It is not supposed to be compatible to CM, HydrogenOS etc.
Also note: You have to use Boeffla-Config app which I provide on my homepage to tweak the kernel. 3rd party apps will not be able to unleash the full power of the kernel.
Important: Manually disable battery optimisation for Boeffla-Config app in the rom settings (battery -> battery-optimisation)
Installation
Read the install instructions in the support section on the Boeffla Site.
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (outdated at the moment).
Click here to learn about using the config app.
I will refuse to give support if you do any undervolting/overclocking and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
I will refuse to give support if you have xposed framework installed and reporting any kind of weird issues. My opinion to xposed it quite clear: too powerful for >90% of the users that just mess up their system with it.
Otherwise, you can get in touch with me via the support e-mail address: [email protected]
Please provide kernel version, rom version, a detailed issue description and ideally supporting screenshots or log files.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting change log...)
Change log for OxygenOS 5.x.x kernel - Click here
Change log for OxygenOS 4.x.x kernel - Click here
Known issues
none known
Features
Note: This kernel only runs on OOS 4.x.x for the OnePlus 5T - nothing else !!!
Important: Manually disable battery optimisation for Boeffla-Config app in the rom settings (battery -> battery-optimisation)
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 (you need at least version 2.5.10 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Dash charging fully supported
The two CPU clusters (big and little cpu) can be configured completely separate in terms of min/max frequencies, governors and CPU core profiles
Additional governors: zzmoove, blu_active, impulse, cultivation
Additional schedulers: fiops, bfq, sio, sioplus, fifo, vr, tripndroid, maple, zen
Underclocking CPU and GPU supported
No CPU and GPU overclocking (not planned too)
No CPU and GPU voltage interfaces (not planned too)
GPU boost implemented (4 levels)
CPU core profiles to restrict number of CPU cores being used (the OP5T does not hotplug based on load)
USB charge rate bumped up to 900 mA
Boeffla charge analysis (display of charger type and charge current in Boeffla-Config app in real time)
Notification LED control (effect + speed for blinking/fading, brightness for continuous notification like battery charging etc.)
Boeffla-Sound engine V1 (headphone volume control, earpiece control in calls, microphone gain control in calls)
Dynamic FSync (activated if screen on, deactived if screen off), configurable
Input boost frequencies and duration configurable per CPU cluster, input boost switch
Show CPU frequency usage per CPU and frequency in Boeffla-Config
Show current CPU core frequencies in realtime (note: other apps than Boeffla-Config will likely display wrong information on offline cores as they are not up-to-date yet)
Show GPU frequency usage per frequency in Boeffla-Config
KCal V2 Color control
Display backlight limits configurable (to avoid display brightness gets too low in some situations)
Display backlight dimmer
Swipe2wake gestures
Boeffla generic wakelock blocker
Control haptic feedback of gestures (except fingerprint)
Haptic feedback intensity control (from 0 to 25, with 25 being 100%)
Swipe2sleep gestures
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
Kernel logger (dmesg) configurable
CIFS support (module, do not mount inside /data, if you rooted with Chainfire SuperSu, make sure you uncheck the namespace separation in SuperSu app)
NFS read-only support (module)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Many additional TCP congestion algorithms available
Entropy values configurable
Swap supported
Wireguard supported
Various kernel tweaks
Doze mode configurable in Boeffla-Config
Full selinux strict support (switchable to permissive on demand)
Show speedbin information (PVS level) in Boeffla-Config app
init.d support (in /system/etc/init.d - set correct permissions!)
Automatic EFS backup
Fully supports OOS device encryption, but does not force it
Integrated full busybox 1.27.2 (own compilation)
Compatible with systemless root
Safetynet: verifiedbootstate + additional flags removed
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Google gcc 4.9 toolchain (64 bit) used for best stability
Always based on latest OOS kernel sources (https://github.com/OnePlusOSS/android_kernel_oneplus_msm8998)
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History and design targets
Basically I created my first Boeffla-Kernel in 2012 as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. Also it does not aim to have the broadest feature set available everywhere.
It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!!
These design targets are also valid for the OnePlus kernel here!!!
This said, I will definitely NEVER implement:
things I do personally not need
things I do not like
things that are in any way dangerous
anything which is highly experimental
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it if it falls into the listed categories. Everything else I am happy to check and decide.
And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.
I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...
Compatibility
To reiterate it again: Flash the kernel only if you are running a compatible rom !!!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app Boeffla-Config V2 from the downloads section on www.boeffla.de.
You need at least version 2.5.10 or higher for the OnePlus 5T Boeffla Kernels.
Donation
If you like my work, feel free to donate: Donation-Link
If you donate at least 2,49 EUR (to be in line with the donation app prices on Google Play store), you will receive a personal donation code which unlocks some nice little comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* ZaneZam
* eng.st
* flar2
* arter97
* Grarak
* Entropy512
* Faux
* FranciscoFranco
* Ak
* Osm0sis
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in your custom recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
Latest change log:
OOS4
http://kernel.boeffla.de/oneplus5t/boeffla-kernel-oos/oos4xx/changelog.htm
--- Reserved ---
WHAT MAKES YOU THINK I WILL MAKE A KERNEL FOR ONE PLUS 5 T ?????
Sendt fra min SM-N950F med Tapatalk
Thread opened.
First beta version has just been released - 1.0-beta1.
Feature list, see OP.
Have fun
Andi
Is it compatible with open beta 2 ?
Awesome.. Was waiting for your Kernel
zebasketteur said:
Is it compatible with open beta 2 ?
Click to expand...
Click to collapse
I would assume not, as in title is says OOS 4
---------- Post added at 02:42 PM ---------- Previous post was at 02:05 PM ----------
Just flashed, seems that the max brightness is lower, with the display backlight settings unchanged. Apart from that all seems to be good.
Nice to see you here! I have use your kernels starting with Samsung S3 and after that many many devices and always being good!
zebasketteur said:
Is it compatible with open beta 2 ?
Click to expand...
Click to collapse
This is very clearly stated in the opening post.
No.
Hetex said:
[/COLOR]Just flashed, seems that the max brightness is lower, with the display backlight settings unchanged. Apart from that all seems to be good.
Click to expand...
Click to collapse
This is not changed by me. As long as you do not play in the app with the settings, this is 1:1 as in stock kernel.
Anyone else? I mean, nothing is impossible of course.
Andi
Lord Boeffla said:
This is not changed by me. As long as you do not play in the app with the settings, this is 1:1 as in stock kernel.
Anyone else? I mean, nothing is impossible of course.
Andi
Click to expand...
Click to collapse
Not sure if it is the same problem but in the first release of elementalX kernal, whether the brightness dimmer was enabled or not the brightness at maximum was half of what it should have been.
Thanks.
Lord Boeffla said:
This is not changed by me. As long as you do not play in the app with the settings, this is 1:1 as in stock kernel.
Anyone else? I mean, nothing is impossible of course.
Andi
Click to expand...
Click to collapse
You have to revert THIS exact commit in order to fix that (not working anymore on OP5T)
Welcome to OP5T mate btw :highfive:
Cheers'
Hello Boeffla
Hetex said:
Not sure if it is the same problem but in the first release of elementalX kernal, whether the brightness dimmer was enabled or not the brightness at maximum was half of what it should have been.
Thanks.
Click to expand...
Click to collapse
Good hint. Will check in that direction when more people are sure this brightness thingy is real.
Update: Analysis started...
Andi
Lord Boeffla said:
Good hint. Will check in that direction when more people are sure this brightness thingy is real.
Update: Analysis started...
Andi
Click to expand...
Click to collapse
Ok, issue analyzed, confirmed to be a bug.
Bug is fixed and beta2 already compiling. Stay tuned. And thanks for the report.
(BTW it was not the brightness dimmer but a changed brightness range sent by the rom to the kernel, so the min/max limiter was cutting too early)
Thanks
Andi
AndroidGX said:
You have to revert THIS exact commit in order to fix that (not working anymore on OP5T)
Welcome to OP5T mate btw :highfive:
Cheers'
Click to expand...
Click to collapse
Thanks. Sorry, did not see your post as I was busy analyzing.
Well... reverting a commit and losing the functionality is not the option when I can fix it, eh? :fingers-crossed:
And so I did.
MrTalon4 said:
Hello Boeffla
Click to expand...
Click to collapse
Hello MrTalon4
Andi
Hi all,
small bugfix update is out:
Version 1.0-beta2
18.01.2018
Fix: Backlight limit implementation adjusted to OP5T (display could never reach maximum brightness before)
Enjoy
Andi
Welcome,it is nice to see you here ..waiting one for oreo
marko94 said:
Welcome,it is nice to see you here ..waiting one for oreo
Click to expand...
Click to collapse
Yeah. But not before it gets out of open beta, not before it is released officially.
... my golden rule for a long time.
Andi
Welcome to the 5T-Zone
Is it possible to have WireGuard implementation for your new 5T kernel (at some point in the near future) ?
Edit:
I just rechecked the OP, already there. Too cool