Related
Hi all,
some of you know me from the Samsung devices area, where I provide my kernels already for more than two years to Galaxy S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.).
Maybe you also know me from my OnePlus One kernels I added in winter last year to my portfolio.
Finally I got a Samsung Galaxy S5 afew weeks ago and decided to port my kernel also to this device. This is a sponsored device, so I want to say a big thank you to the people that made it possible, namely the ones in the German Smartphone Forum www.hubo.in !!!
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).
For the CM Boeffla-Kernel, please go HERE.
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
Compatibility
Important: This kernel is only meant to be compatible with official Samsung stock firmware 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 !!
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app.
Click here to learn about using the config app.
I will refuse to give support if you do any undervolting 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.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for Android 5.0 kernels: KLICK HERE
Features
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Additional governors: zzmoove (Note: not considered stable at the moment, you might face reboots!!!), intelliactive, intellidemand, wheatley, smartmax, slim, intellimm, nightmare, lionheart, pegasusq
Zzmoove supporting native hotplugging profiles
Additional schedulers: fiops, bfq, sio, tripndroid, zen
Many Hotplug tweak profiles (Default, Optimized, 1 core max, 2 cores max, 3 cores max, 2 cores min, 3 cores min, 4 cores min, 2 cores exact, 3 cores exact)
Wake up gestures implemented (double-tap-to-wake, swipe to wake)
Boeffla-Sound engine (Headphones and speaker volume configurable)
Configurable vnswap
zSwap configured fix to Samsung stock value of 1280 MB
True dynamic FSync (activated if screen on, deactived if screen off), configurable
Touch boost frequency configurable, touch boost switch
CPU Overclocking up to 2.84 GHz
CPU Voltages interface for undervolting/overvolting
GPU idle frequency 27 Mhz added
GPU governor selection support
Show GPU frequency usage per frequency in Boeffla-Config
Color control to adjust RGB color space + inverted mode
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
System Tweaks predefined supported (default is off)
Android logger (logcat) configurable
Kernel logger (dmesg) configurable
Charge rates for AC charger, USB and wireless charging separately configurable (set charge rate to 0 to have stock charge logic back)
Charge information display support via Boeffla-Config V2 app
CIFS support (module, Important: make sure you unchecked option "Mount namespace separation" in SuperSU settings; do not mount inside /data or /storage)
NFS support (module)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Swap supported (but not recommended, zSwap used already)
init.d support (in /system/etc/init.d - set correct permissions!)
Default entropies increased
Automatic EFS backup
Full support for mpdecision for best compatibility and smoothness
(Important: use Boeffla-Config to configure min/max CPU frequencies + governors + schedulers only - or explicitely allow other apps/processes to overwrite this in Boeffla-Config settings, but expect weird side effects)
Integrated full busybox 1.23.1 (own compilation)
Auto-Root by kernel possible by request
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Presets supported in Boeffla-Config by kernel (Extreme power, power, normal, battery friendly and battery saving)
Google gcc 4.8 toolchain used for best stability
Initramfs of latest Samsung firmware
Based on latest Samsung sources
Kernel runs with SELinux enforcing by default, just as Samsung stock kernel for S5 - but can be configured to work in permissive mode in Boeffla-Config settings
Knox and Samsung rom security warnings removed
Note: I do NOT upstream the kernel to higher Linux kernel versions anymore as this usually has zero benefit but likely introduces new issues + is a waste of effort in the end
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 Galaxy S5 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
f2fs - it is known to cause various issues and compatibility problems
a CAF based kernel
anykernel method to use the ramdisk of the installed rom
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 correct kernel depending on whether you are on Samsung Stock, CM12 or CM11 !!!
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.1.72 or higher for the Galaxy S5 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
* Yank555
* ktoonsez
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Entropy512
* Faux
* Ak
... 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 logs:
Android MM 6.0.1
http://kernel.boeffla.de/sgs5/boeffla-kernel/mm60/changelog.htm
*** You want my support? Then stick to my rules ***
Guys, I am receiving more and more completely useless support requests in different threads. Useless because people provide nothing to be able to help, not even the minimal possible information they could give.
Hence, I will now remind anyone again on the support guide lines stated here:
http://boeffla.de/index.php/support/support
Also you need to ensure you follow the installation guide lines incl. trouble-shooting stated here:
http://boeffla.de/index.php/support/installation-how-to
And to cut a long story short: If you do not at least provide what I request in the support guide lines, I will IGNORE YOUR REQUESTS IN FUTURE.
Straight and simple. I have enough of people wasting my time just because they are too lazy to write details.
Period.
Also as a reminder:
you use xposed? -> no support, everything is your own issue
you use a custom rom and not the official stock or CM one? -> good luck, you are on your own
you undervolt or overclock? -> have fun, but without my support
Sorry, this might sound harsh (and it is meant to sound harsh), but you cannot imagine about how crappy support requests can be. Stating something does not work is just not enough.
Please consider that!!!
Andi
yeahh, dr andi so glad to see you here ..
You can also submit g900h variant? I can a beta tester
MOKIAAA said:
yeahh, dr andi so glad to see you here ..
You can also submit g900h variant? I can a beta tester
Click to expand...
Click to collapse
I am sorry, nothing changed in my attitude and golden rules over the past years.
No device, no kernel.
Apart from that, I need to stop adding new kernels now, it just gets too many already. And once I realize quality does drop, I have to stop.
Andi
Thank you,Andi
Thanks to @Lord Boeffla, finally today you've released your awesome kernel. Of course I saw @ZaneZam thanks to you too and I know we might have another version will be compiled and supported. Nice
Hi all,
Great kernel
Works very fine
Check this out...
Thanxxxx to the Lord for the hard work in the last week's
It's hard to access root rights on my device with Stock Deodexed Prerooted Rom. I've flashed Update-SuperSu 2.46 in TWRP, but RootChecker checked with no Root installed on device
ghoster76 said:
It's hard to access root rights on my device with Stock Deodexed Prerooted Rom. I've flashed Update-SuperSu 2.46 in TWRP, but RootChecker checked with no Root installed on device
Click to expand...
Click to collapse
Not a problem with Samsung Stock BOB7 firmware.
Andi
Hey Lord,
thanks for your awesome work! I really liked your kernel for the S3, even better you're now developing for the S5.
Immer weiter so men Jung!
Grüße aus Köln
Lord Boeffla said:
Not a problem with Samsung Stock BOB7 firmware.
Andi
Click to expand...
Click to collapse
I'm using BOC7 , and reflashing again
Thanks a lot Lord! Used to love it on my S3
Best configuration for battery-performance?
works great on BOC7.
Thank
borjaag said:
Thanks a lot Lord! Used to love it on my S3
Best configuration for battery-performance?
Click to expand...
Click to collapse
We need you guys to find that out, the S5 is not my daily-usage phone. So all I get is quite hypotethical at the moment.
Andi
Andi, forgive me, does it work on ANG7?
Never mind, Lollipop upwards
Looks good so far on XtreStoLite!
I'm just wondering if you are planing to add full sound configuration options?
Your sound implementation options allowed superb sound on S3 and I guess I'm not the only one missing it on S5
Looking forward to next versions!
f0xy said:
Andi, forgive me, does it work on ANG7?
Never mind, Lollipop upwards
Click to expand...
Click to collapse
See OP, first line. Clear "maybe"... I tested against BOB7 only as I cannot install 10 different roms. But you will tell us?
MewCore said:
Looks good so far on XtreStoLite!
I'm just wondering if you are planing to add full sound configuration options?
Your sound implementation options allowed superb sound on S3 and I guess I'm not the only one missing it on S5
Looking forward to next versions!
Click to expand...
Click to collapse
Would love to. But it is a completely different sound chip used in the S5, compared to the S3.
And it seems there is no way to get hold of any documentation for it (wdc9230), which would allow us dev to explore more of the chips capabilities.
If you saw a kernel providing more sound options, I am happy to get the information about it and checking if it can be ported. Then we would even know what the audio hub can do and what not...
Or someone can get Qualcomm to hand me over the documentation of their audio hub, then also more is possible. But many devs for sure have tried that in the past years already, so I am not very optimistic.
Andi
Battery friendly seems so good for daily usage at the moment, but Battery Saving with zzmoove / battery yank seems pretty lags. Hope it be implemented some next versions.
I'm Running BOC7
ghoster76 said:
Battery friendly seems so good for daily usage at the moment, but Battery Saving with zzmoove / battery yank seems pretty lags. Hope it be implemented some next versions.
I'm Running BOC7
Click to expand...
Click to collapse
Yes, it lags. And it is a hardly battery focussed preset, so it must lag.
That is why you have the choice.
Andi
Introduction
This is a kernel for XT1572/XT1575 built from stock sources (marshmallow-6.0.0-release branch) with cherry picks from other kernels and some ports/mods done by me. It started as a personal build tailored to my preferences but just thought I'd share in case somebody might find it useful. My main goal is building the smoothest kernel I can get so performance is top priority.
This kernel is for stock ROM MPH24.49-18*
Disclaimer
Although I have experience with Linux kernels on desktops and servers this is my first Android kernel. I've been running this kernel on my XT1572 for a few days and seems pretty stable but that doesn't mean it's risk free. In fact I wouldn't dare to install it if you don't have a proper backup and some basic skills to deal with unexpected situations.
Features
Aroma Installer
CPU profile scripts (see this)
Color control (KCAL)
Frandom
Updated to kernel version 3.10.101
Overclocking (a53: 1536MHz a57:2016MHz)
Underclocking (302MHz)
Additional CPU governors (ElementalX, Intelliactive, Lionheart, BioShock, BluActive, Wheatley, InteractiveX/Interactive, Impulse, Zzmoove)
Additional I/O schedulers (SIO, FIOPS, Zen, BFQ, SIOPLUS)
Bricked Hotplug
Updated ZRAM driver
Updated Lowmemorykill driver
Basic init.d support
KSM and UKSM
Voltage readings
Fsync on/off
Touchboost on/off
Vibration control
KEXEC Hardboot (MultiROM support)
Patched cdrom code (DriveDroid support)
DoubleTap2Wake/Sweep2Wake/Sweep2Sleep (EXPERIMENTAL)
Power efficient workqueues
Support for additional FS: NTFS, NFS, CIFS
Additional Xpad drivers (read this)
Device as USB trackpad/keyboard driver (read this)
WiFi module optimizations
Many minor optimizations
Optimization flags
UBER Toolchain 4.9
Installation instructions
Download ZIP and flash from TWRP/Flashify. Read the following notes carefully before flashing.
Important notes:
This kernel is still experimental, make a proper backup first
You need to be rooted
DO NOT play with DT2W/S2W before reading the release notes and the update
In case you want to tune some parameters (ie: CPU frecuencies) I recommend you install EX Kernel Manager, Kernel Adiutor or Kernel Adiutor-Mod.
If you're using Kernel Adiutor to control vibration or TCP congestion read this.
Questions? Read the FAQ before posting.
Download
Latest version is v0.14 (see release notes)
https://www.androidfilehost.com/?w=files&flid=49225
Donations
Although quite a deal of the important work has been done by the developers mentioned in the Credits section I spend many hours working on this. If you feel like helping me out I'd appreciate some tiny donations to cover some minor expenses.
Thanks to all of you who have donated, it's very much appreciated.
Profiles
One of the FAQ in most kernel related threads is "What are the best settings for .....?". This is the 10 million question since the usage pattern can be very different for each user. However, I understand less experienced users will appreciate some hints in this department, so that's why I'm posting some basic settings you can use as a starting point.
It's your job to further tune them to suit your needs. You should be able to modify these settings with whatever Kernel Control App you like the best, although not all settings are available in every app, in such a case tune those you can. The list is not complete (just the most importante settings) and is loosely based on Kernel Adiutor arrangement.
Please, keep in mind these are subjective values (based of personal preferences or popularity) and some people might like other settings for whatever reasons.
Performance Profile: Very smooth and responsive but average battery life
CPU
LITTLE Cluster
CPU Governor: bluactive
CPU Max Frequency: 1536MHz
CPU Min Frequency: 302MHzBIG Cluster
CPU Governor: bluactive
CPU Max Frequency: 2016MHz
CPU Min Frequency: 302MHz
NOTE: If you get N/A or weird values when trying to change settings on BIG cores it means both have been hotunplugged. To work around this select "performance" governor, make your desired changes and then select you previous governor.CPU Boost
Input Boost Frequency Core 1: 960MHz
Hotplug
MSM MPDecision
Minimum CPU online: 2
Maximum CPU online: 6
Max Cores Screen Off: 2
Idle Frequency: 384MHz
Thermal
Core Control: Off
VDD Restriction: Off
Temperature Throttle: On
GPU
Max Frequency: 600MHz
Min Frequency: 180MHz
Govenor: cpufreq
I/O
Scheduler: noop
Read-ahead: 1024KB
Balanced Profile: Above average battery life with good performance on most situations
CPU
LITTLE Cluster
CPU Governor: interactive
CPU Max Frequency: 1440MHz
CPU Min Frequency: 302MHzBIG Cluster
CPU Governor: interactive
CPU Max Frequency: 1632MHz
CPU Min Frequency: 302MHz
NOTE: If you get N/A or weird values when trying to change settings on BIG cores it means both have been hotunplugged. To work around this select "performance" governor, make your desired changes and then select you previous governor.CPU Boost
Input Boost Frequency Core 1: 960MHz
Hotplug
MSM MPDecision
Minimum CPU online: 2
Maximum CPU online: 5
Max Cores Screen Off: 2
Idle Frequency: 768MHz
Thermal
Core Control: Off
VDD Restriction: Off
Temperature Throttle: On
GPU
Max Frequency: 600MHz
Min Frequency: 180MHz
Govenor: msm-adreno-tz
I/O
Scheduler: noop
Read-ahead: 1024KB
Battery Profile: Good battery life at the expense of somewhat limited performance
CPU
LITTLE Cluster
CPU Governor: ondemand
CPU Max Frequency: 1440MHz
CPU Min Frequency: 302MHzBIG Cluster
CPU Governor: ondemand
CPU Max Frequency: 1632MHz
CPU Min Frequency: 302MHz
NOTE: If you get N/A or weird values when trying to change settings on BIG cores it means both have been hotunplugged. To work around this select "performance" governor, make your desired changes and then select you previous governor.CPU Boost
Input Boost Frequency Core 1: 960MHz
Hotplug
MSM MPDecision
Minimum CPU online: 1
Maximum CPU online: 3
Max Cores Screen Off: 2
Idle Frequency: 960MHz
Thermal
Core Control: Off
VDD Restriction: Off
Temperature Throttle: On
GPU
Max Frequency: 450MHz
Min Frequency: 180MHz
Govenor: simple_ondemand
I/O
Scheduler: noop
Read-ahead: 1024KB
Thanks To/Credits
vadimtk
flar2
franciscofranco
nimrodsv
anarkia1976
savoca
myfluxi
AudioGod
osm0sis
nychitman1
jollaman999
imoseyon
showp1984
HashBang173
neobuddy89
rehpyc
Alcolawl
soniCron
Spasticdroid
XDA:DevDB Information
Frankenclark, Kernel for the Moto X Style (Pure)
Contributors
dirtyhank
Source Code: https://github.com/dirty-hank/frankenclark/
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 0.14
Created 2016-01-10
Last Updated 2016-10-11
Changelog
v0.14 (2016-08-29)
Proper KCAL control (thanks to @Spasticdroid)
Updated xpad driver for compatibility with gamepads/controllers (thanks to @Spasticdroid)
Driver to use device as USB trackpad and keyboard (thanks to @Spasticdroid)
Misc minor updates (see github)
100Hz version uses stock compiler flags
v0.13 (2016-06-21)
Update to Linux Kernel 3.10.102
Misc minor updates (see github)
New start-up CPU governor profiles: bluactive, maddog and silverfish
v0.12 (2016-05-15)
Disable DT2W/S2W while phone call is in progress
New CPU governors: impulse, zzmoove
New and updated CPU profile scripts
Runtime CPU profile switcher script (see release notes)
Minor changes to Aroma installer
v0.11.1 (2016-05-01)
Aroma Installer update (see release notes)
v0.11 (2016-04-27)
Aroma Installer
Better camera focus
Less CPU usage from DT2W/S2W
Minor updates and bugfixes
v0.10 (2016-04-03)
Updated lowmemorykiller driver
BFQ and SIOPLUS I/O schedulers
Updated ZRAM driver (on by default)
User togglable WLAN wakelocks
Basic init.d support (see release notes)
Misc minor updates
v0.9 (2016-03-20)
Update to Linux Kernel 3.10.101
Bug fixes
Changes from Google update to N5X and N6P (see release notes)
v0.8 (2016-03-06)
Update to Linux Kernel 3.10.99
Power efficient workqueues
NTFS support
NFS and CIFS support (you'll probably need additional user space binaries)
v0.7.1 (2016-02-28)
Workaround for the dimmed screen upon unlock bug when DT2W/S2W is enabled
v0.7 (2016-02-21)
Hotplug thresholds tuned to keep BIG cores offline more often
KEXEC Hardboot (MultiROM support)
Patched cdrom code (full DriveDroid support)
DoubleTap2Wake/Sweep2Wake/Sweep2Sleep (HIGHLY EXPERIMENTAL, Read this)
v0.6 (2016-02-07)
Vibration control (non-haptic)
Relaxed CPU macros for better power usage
File hosting now on AndroidFileHost
v0.5.2 (2016-02-03)
Fixed USB and WiFi Tethering
Minor tweaks
v0.5.1 (2016-02-01)
Changes to installer
v0.5 (2016-01-31)
Update to Linux Kernel 3.10.95
InteractiveX governor (as patches to the interactive gov)
Bricked Hotplug
KSM and UKSM (disabled by default, use Kernel Adiutor to enable)
Many minor optimizations
WiFi module optimizations
Modules recompilation
Disabled core_ctl (due to broken module after some internal changes to kernel)
Voltage readings (any attempt to modify values is silently ignored)
v0.4.1 (2016-01-24)
Prevent msm_performance from messing with the user selected min/max CPU frequencies
v0.4 (2016-01-23)
New CPU governors (ElementalX, Intelliactive, Lionheart, BioShock, BluActive, Wheatley)
New I/O scheduler (Zen)
Default I/O scheduler set to noop with a read ahead of 1024kb
Fixed bug CVE-2016-0728
Minor optimizations
Introduce ZIP installer (Anykernel2)
v0.3 (2016-01-18)
Color control (KCAL)
frandom support
New optimization flags
ZRAM disabled by default
v0.2 (2016-01-14)
Updated to Linux kernel 3.10.94
Underclocking (302MHz)
v0.1 (2016-01-10)
First public version
FAQ
I get random reboots, what is happening?
This kernel overclocks both clusters by default (a53: 1536MHz a57:2016MHz) and although this is very safe for most devices some CPUs are in the lowest spot of the binning spectrum and can't handle O/C very well. In such a case use a kernel control app (see the OP for references) to limit the maximum CPU frequencies, play with them until you find stable values for your device.
What are the best settings for battery life/performance/whatever?
That's hard to tell as every user is different. You can find some basic profiles in the OP you can use as a starting point. Notice the differences between then and build you own.
Why do some BIG cluster settings display N/A?
Why can't I change some settings on the BIG cluster?
If you get N/A or weird values when trying to change settings on BIG cores it means both are offline ("hotunplugged"). To work around this select "performance" governor, make your desired changes and then select you previous governor. You can also disable hotplug, make the changes, and enable hotplug again.
DoubleTap2Wake doesn't work sometimes. How can I get it to work all the time?
When device goes into suspend mode first tap is often missed (I suspect this is caused by Moto Sensor Hub). If you tap three times and get the timing right you'll probably make it work most of the time. As an alternative, Sweep2Wake works almost all the time
DT2W/S2W is acting weird or disabling itself
Make sure Moto Display is disabled. Open the Moto app, click on the stars in the top right corner, select Display and set to Off
Can I use this kernel in ROM X/Y/Z?
This is for stock ROM MPH24.49-18 only. It'll probably work on any stock based ROM but not guaranteed.
I use stock ROM but WiFi is not working
Due to some internal changes all modules had to be recompiled (WiFi included). In order to expose the new modules without modifying the system partition I had to implement a hack that requires root. Make sure you're properly rooted.
What's the deal with ZRAM?
ZRAM is a technique to increase memory available to the apps at the expense of CPU time. Memory space from apps not being used is compressed into a memory swap area and uncompressed on the fly whenever needed. As you can imagine this compress/uncompress process burns CPU cycles, potentially leading to worse battery life, lag and higher temperatures. Since this device comes with 3GB I can only think of one scenario where ZRAM can be beneficial: heavy multitaskers who care more about apps not reloading than battery life. For the rest of users enabling ZRAM doesn't make much sense in my opinion, and that's why it's disabled by default.
UPDATE: v0.10 includes an updated ZRAM driver that improves performance significantly. So much so that the benefits seem to outweigh the costs and it's been enabled by default.
What's the deal with KSM/UKSM?
Since many apps use the same libraries/resources it's very likely that at any given time there are multiple copies of the same data on different memory locations. KSM/UKSM tries to take advantage of that fact by scanning memory pages periodically and consolidating that multiple copies into a single shared copy. Much as like ZRAM it can have a good effect on heavy multitasking performance but at the expense of CPU cycles, and thus it's only recommended in the same scenario as ZRAM. Disabled by default
Ok, so do I enable ZRAM/KSM/both/neither?
I honestly think most users will be better off not using neither. If you feel like you need extra RAM I'd try KSM first, then ZRAM. Using both at the same time is overkill unless you are an ultra multitasker, in which case you should probably get a 4GB device anyway
How do I get WiFi on 6.0.1?
It's a modem version mismatch issue, you need to downgrade the modem. See this post.
Love to see more options! Thanks for sharing!!
Yeah this will be very good
Only One think that would be awesome try to implement the double tap to wake
Awesome! More custom kernels are always welcome are there many governors to choose from?
krohme said:
Awesome! More custom kernels are always welcome are there many governors to choose from?
Click to expand...
Click to collapse
Right now only the stock governors are available but I plan on adding a few
Can't we install it through twrp???
guraki said:
Can't we install it through twrp???
Click to expand...
Click to collapse
Yes, TWRP supports boot image flashing
I lost root after the kernel install....
---------- Post added at 03:22 PM ---------- Previous post was at 02:39 PM ----------
Seems to work fine!!! Any battery life expectations?
guraki said:
I lost root after the kernel install....
---------- Post added at 03:22 PM ---------- Previous post was at 02:39 PM ----------
Seems to work fine!!! Any battery life expectations?
Click to expand...
Click to collapse
As I said on the OP my main goal is performance/smoothness, so I haven't specifically sought better battery life. That being said I'm getting about the same battery life as stock with better performance, that works for me.
Nevertheless, I'm very interested on how it works for other configurations and usage patterns.
@dirtyhank could you please add hotplugging to the kernel? Preferably one that allows you to select how many cores to run as well as which ones, as in run the two A57s and turn off the four A53s. Currently I'm running two A53s at 1.2Ghz and the remaining four cores are always off.
The screenshot is from Lolipop, and it is the only reason why I havent upgraded to MM. Turning off cores definitely makes a difference on battery life.
Also, if possible, adding a lower speed to the min speed. Will gladly test anything you thow my way. Thanks in advance.
Is there any chance for a CM13 version and a DT2W fork from elementalx?
sir-harlekin said:
Is there any chance for a CM13 version and a DT2W fork from elementalx?
Click to expand...
Click to collapse
DT2W maybe, CM13 unlikely.
very nice thank you! slowly slowly we getting more and more things. Just making sure this is only for stock based rom/s Thanks!!
cerobles1 said:
@dirtyhank could you please add hotplugging to the kernel? Preferably one that allows you to select how many cores to run as well as which ones, as in run the two A57s and turn off the four A53s. Currently I'm running two A53s at 1.2Ghz and the remaining four cores are always off.
The screenshot is from Lolipop, and it is the only reason why I havent upgraded to MM. Turning off cores definitely makes a difference on battery life.
Also, if possible, adding a lower speed to the min speed. Will gladly test anything you thow my way. Thanks in advance.
Click to expand...
Click to collapse
What kernel are you using on LP?
patt2k said:
very nice thank you! slowly slowly we getting more and more things. Just making sure this is only for stock based rom/s Thanks!!
Click to expand...
Click to collapse
Yep, stock ROM, I'll edit the OP
dirtyhank said:
Yep, stock ROM, I'll edit the OP
Click to expand...
Click to collapse
Awesome gonna flash this soon
I hope a port for CM based roms might be possible in the future! Thanks for sharing your work and replying so quickly!
dirtyhank said:
Yep, stock ROM, I'll edit the OP
Click to expand...
Click to collapse
Getting bootloop on TruePure rom 2.4. Anything I can try to avoid bootloops?
Welcome to: The One Bad Ass ROM
Hello everyone, I would like to present OBAR (One Bad Ass ROM) a ROM that I successfully built for the Note 4 is now on our LG, well for Sprint at-least. So here it is, a Stock, de-bloated, modified ROM that is based off of ZV6 to bring the absolute best performance and battery life to your phone! Hope you guys enjoy! EDIT (5/02): As of now we have our very own OBAR Kernel,
I'd like to let you know all about it so seek the second post
Stock Specifications:
Based On Stock LS997ZV6 (Nougat - 7.0.1)
Our Very Own OBAR Kernel! (See second post for details)
Rooted & Busy Boxed
De-Bloated
Magisk or SuperSU Compatible (SuperSU built in)
No Sprint Bloat
OBAR Features:
Enabled High Independence Mode
Enabled Guest Features (Max: 5)
Enabled Hotspot
Added Build.Prop Tweaks
Added Custom Kernel Adiutor
Fixed Data On Boot
Improved Net Speeds
Improved Scrolling Speeds
Improved RAM Management
Insane Battery Life
Insane init.qcom.post_boot Modifications (Improves Overall Performance/Battery/Stability)
And more I forgot...
Install:
Download
Transfer To Phone
Reboot To Recovery
Wipe System, Data, Cache, Dalvik Cache (x3)
Format System (Backup Your Internal Storage First)
Install Stock OBAR Rom
Wait About 15 min To Boot
Enjoy
Downloads:
Rom Releases
Kernel Releases
Older Versions
After Install: (Recommended)
Initial boot will boot twice.
Please allow about 15 minutes to boot up after initial boot. (Due to it being deodexed)
Recommended to wait up to five minutes on initial boot before doing anything, then do a full restart.
To get back Developer Options go in to Settings, About Phone and rapidly tap Build Number until it says your a developer.
Important Notes:
Yes there is static on boot.
For those who get stuck in a "TWRP LOOP" see here.
Don't ask if this will work on other variants I will ignore your question. I will not support other variants with this ROM, sorry. Sprint only. You can always flash it and find out.
Credits:
@me2151 - For the Official LS997ZV6 Base and root method of course!
@svadev - For the SVA Deodexing tool!
@Ticklefish - For the TickleMyAndroid Tool!
@DTDMike - For the ability to enable High Independence Mode.
@ashirviskas - For enabling the dual speaker mod.
@warBeard_actual - For the crazy init.qcom.post_boot Modifications
@Team DevDigitel - For a working base and great help!
@freeza - For teaching me how to build my first kernel!
@BackCheck - Major help with figuring out how to get the kernel to fully work properly!
Disclaimer: I do not and will not take any responsibility towards anything that happens to your phone after flashing.
XDA:DevDB Information
Stock LS997, ROM for the LG V20
Contributors
SaintZ93, me1212
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: LS997
Based On: Stock
Version Information
Status: Stable
Current Stable Version: Release 1
Stable Release Date: 2017-03-26
Created 2017-02-09
Last Updated 2017-03-26
Okay guys OBAR now contains its own kernel! So I want to give you a bit of information that may help you to decide how you want to set up it up! I will always keep this post updated with all the latest version release information. Will label dates next to each new update to show what is new!
I/O Scheduler Information - GPU:
FIOPS - This is an IOPS based I/O scheduler. It will try to distribute IOPS equally among all processes in the system. It's mainly for Flash based storage.
SIO - The Simple I/O scheduler is an extremely simple scheduler, based on noop and deadline, that relies on deadlines to ensure fairness. The algorithm does not do any sorting but basic merging, trying to keep a minimum overhead. It is aimed mainly for aleatory access devices (eg: flash devices).
NOOP - The no-op I/O scheduler is a minimal scheduler that does basic merging and sorting. Its main uses include non-disk based block devices like memory devices, and specialised software or hardware environments that do their own scheduling and require only minimal assistance from the kernel.
DEADLINE - The deadline I/O scheduler is simple and compact. It will provide CSCAN service with FIFO expiration of requests, switching to a new point in the service tree and doing a batch of IO from there in case of expiry.
CFQ - The CFQ I/O scheduler tries to distribute bandwidth equally among all processes in the system. It should provide a fair and low latency working environment, suitable for both desktop and server systems.
BFQ - The BFQ I/O scheduler tries to distribute bandwidth among all processes according to their weights. It aims at distributing the bandwidth as desired, independently of the disk parameters and with any workload. It also tries to guarantee low latency to interactive and soft real-time applications. If compiled built-in (saying Y here), BFQ can be configured to support hierarchical scheduling.
BFQIO - Enable hierarchical scheduling in BFQ, using the cgroups filesystem interface. The name of the subsystem will be bfqio.
ZEN - FCFS, dispatches are back-inserted, deadlines ensure fairness. Should work best with devices where there is no travel delay.
Governor Information - CPU:
Simple Ondemand - Chooses frequency based on the recent load on the device. Works similar as ONDEMAND governor of CPUFREQ does. A device with Simple-Ondemand should be able to provide busy/total counter values that imply the usage rate. A device may provide tuned values to the governor with data field at devfreq_add_device().
Performance - Sets the frequency at the maximum available frequency. This governor always returns UINT_MAX as frequency so that the DEVFREQ framework returns the highest frequency available at any time.
Powersave - Sets the frequency at the minimum available frequency. This governor always returns 0 as frequency so that the DEVFREQ framework returns the lowest frequency available at any time.
Userspace - Sets the frequency at the user specified one. This governor returns the user configured frequency if there has been an input to /sys/devices/.../power/devfreq_set_freq. Otherwise, the governor does not change the frequnecy given at the initialization.
Blu_active - This allows you to get a full dynamic cpu frequency capable system by simply loading your cpufreq low-level hardware driver, using the 'interactive' governor for latency-sensitive workloads.
Nightmare (NEW 5/15) - This is a PegasusQ modified, less aggressive and more stable. A good compromise between performance and battery. In addition to the SoD is a prevention because it usually does not hotplug.
Darkness (NEW 5/15) - It's based on nightmare but more simple and fast, basic configs but very complex structure. It is an updated nightmare gov and improved stability, so far it is quite stable in tests.
Chill (NEW 5/15) - Use the CPUFreq governor 'chill' as default. This allows you to get a full dynamic frequency capable system by simply loading your cpufreq low-level hardware driver. A conservative based governor that aims to provide more aggressive battery savings while screen is off.
Dance Dance (NEW 5/15) - Based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It is a performance focused governor but also blends with some battery savings.
Adreno Idler Information:
Enabled - Uses a different calculation method on top of Adreno TZ just for calculating frequency for idle to reduce the wasted power coming from stock Adreno TZ while maintaining high-performance.
Other Information:
Moved Core Control To Kernel - Moved core control from out-of-tree module into the kernel proper. Core control monitors load on CPUs and controls how many CPUs are available for the system to use at any point in time. This can help save power. Core control can be configured through sysfs interface.
Moved Core Control Trace Events To Scheduler
Added A Knob To Disable The core_ctl (Core Control) - The CPU hotplug tests does not work with core_ctl compiled statically into kernel. Provide an interface to disable the hotplug by core_ctl.
Enabled LZ4 Compression & Added ExFAT Filesystem
Fixed Various Issues
Source Code: https://github.com/SaintZ13/obar_kernel
Nice can't wait to try this out!
Sent from my SM-N920P using Tapatalk
Thanks for the new ROM! Does this add back the stock LG gallery and music player, or are those still removed?
Cubit33 said:
Thanks for the new ROM! Does this add back the stock LG gallery and music player, or are those still removed?
Click to expand...
Click to collapse
Yes there included. I accidently removed a file that connects to Sprint. Will add it later and upload!
SaintZ93 said:
Yes there included. I accidently removed a file that connects to Sprint. Will add it later and upload!
Click to expand...
Click to collapse
Thanks! Looking forward to testing.
Would you guys prefer this to be straight stock or should I mod it up?
Mod it up!
Sent from my LG-LS997 using Tapatalk
SaintZ93 said:
Would you guys prefer this to be straight stock or should I mod it up?
Click to expand...
Click to collapse
Mods are great, but I'd also be a fan of posting your base rom that is just the "stock features" you have listed above. A slim base version in addition to the modded out version basically.
Mods, mods, mods
So glad to see you over here on the sprint V20 Saint! You always put out great ROMs and you never disappoint! Looking forward to this one.
BTW, mod it up!
Thread closed temporarily at OP's request
Edit: Reopened at OP's request
Okay guys I was finally able to mod it up and make it a very worthy ROM. Enjoy!
Glad you found it useful, man.
warBeard_actual said:
Glad you found it useful, man.
Click to expand...
Click to collapse
Hey man thanks for it! Now your scaring people by being out of the axon threads hahaha
dowloading now
thanks @SaintZ93
OBAR for the note 4 was great
SaintZ93 said:
Would you guys prefer this to be straight stock or should I mod it up?
Click to expand...
Click to collapse
Mod it up. Viper4 and 3minit battery are my favorite add ons.
Some debloat is nice.
I used to run OBAR on either my note 3 or 4.
Downloaded and excited to try it out - but loving classic rom to much to try it out just yet. Soon.
Thank You
Mod the daylights out of it!! I been dying for a good one like that WETA rom but cant use it. Im always dying to try something new tho
Running good on my v20. Nice and smooth. :good::good::good:
Used to love this on my note 4 good to see u bro
*** 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
I'm not responsible for any damage to your device. So be advised.
Kernel Features:
-CPU Overclocked (BIG cores to 2.01GHz and LITTLE cores to 1.44GHz);
-Intellithermal;
-AdrenoBoost;
-AdrenoIdler;
-Faux Sound Control (Headset only);
-Slimbus (Audio bridge) Overclocking;
-WCD9335 HiFi selector at kernel side;
-WCD9335 High Performance enabled by default;
-KSM;
-CRC disabled;
-Dynamic FSYNC;
-PowerSuspend Driver;
-Arch Power and Gentle Fair Sleepers;
-DTS Eagle sound integration;
-Power Efficient Workqueue;
-Wireguard;
-Boeffla Wakelock blocker;
-Ultra KSM;
-Compillation arm neon vfpv4 optimization flags and cortex optimization flags;
-Audio amplifier power limits incrased to reduce distortion;
-Quick charge tweaks (2500mA before go to 61% battery, after Qnovo QNS decides what charging current will deliver to optimum battery life) - Should be used with QC 2.0 / 3.0 specific charger!!!
-> Changelog 22/08/2018
-Updated linux to 3.10.94;
-CPU OC: 2.15GHz BIG / 1.53GHz LITTLE;
-GPU OC: 650MHz;
-Quick charge: For older batteries (with full charge capacity less than 2300mA, charging will occour in nomal mode (1800mA), with more than this, maximum allowed current for battery charging is of 2400mA);
-Added UHQA Audio enabled by default;
-Added TCP Congestion algorythms;
-Added maple IO scheduler;
-Sysfs to view headphone impedance and buck voltage;
->INET LRO for better WiFi and Mobile connection.;
-> Included mixer paths customized for better audio use!
->Changelog 28/08/2018
-Updated linux to 3.10.95;
-GPU Overclock stable at 700MHz! Really effective GPU overclocking;
-CPU Overclocking confirmed working;
-AutoSMP Hotplug;
-CPU Energy updates for low power modes;
-HMP Scheduler Tweaks;
-Neon Kernel Mode;
-Maple IO Sched and another kernel congestion algorythms (westwood default);
-Disabled signature verification.
->Changelog 11/03/2019
...After a long time whtout news, here i am...
-> Tested a stable overclocking at 753MHz in GPU (need testers too);
-> CPU BIG 2.15GHz reduced to 2.016GHz to improve heavy cpu tasks stability;
-> Added IO schedulers;
-> Added more governors;
-> Added more TCP congestion;
-> Screen refresh rate bumped to 66Hz instead 60Hz (testing);
-> Using latest sony patches (EOL);
-> Updated CPU efficiency scheduler detection;
-> Improved QNS charging for more safety and battery friendly;
-> Improved thermal-engine and mixer paths for better User Experience;
-> GPU overvoltage incrased in 753MHz mode to improve stability and try to reduce lags / flickering in some devices.
->Changelog 17/03/2019
-Removed hotplugs (placebo);
-Tunned clocking (lower voltage at lower clocks);
-Fixed venus /video codec clocking (test it for video playback / bugs);
-Removed screen tearing (test it please);
-> Changelog 20/03/2019
-Reduced GPU maximum overclock to 660MHz and enabled a native powerlevel of 621MHz instead 600MHz one;
-Venus (video codec) clock incrased to 541MHz at heavy video playback (HD+);
-Screen refresh rate incrased to 72Hz;
-MDP stabilized clock at 400MHz;
-Tunned PLL Clocks (RAM OC);
-Improved thermal-throttling;
-Enabled arch power by default;
-Updated mixer paths
-> Changelog 23/12/2019 (testing) (xmas special)
-Taked back 700 MHz GPU clock instead 660 MHz and incrase 15 mV at gpu voltage (700 MHz only) to improve stability;
-Tweaked charging (qnovo);
-Tunned Audio (speakers and headphones) a little bit more;
-Tweaked thermal engine to meet with performance adjustments;
-Updated kernel base to 3.10.88 upstreammm (from 3.10.84).
Re-starting in 2020 (i plan to update this kernel monthly with upstreams until 3.10.108, maybe it can have another mods that i may want to tune). Remember: Higher performance, higher heating, more power consumption. Be aware of this kernel if you dont want any of this things! Merry Christmas for your all and see you in the next decade =D
Notice: Linux Kernel downgraded from 3.10.95 to 3.10.84 no noticeable performance reduction because of this (for now i havent time to update all versions and fix bugs to 3.10.1xx.
NEW: See here the GeekBench scores with GPU and CPU Overclocks:
CPU: https://browser.geekbench.com/v4/cpu/9553786
GPU: https://browser.geekbench.com/v4/compute/3807917 //NEW BENCHMARK!
-> Include DRM fix, not rooted, should flash root after install kernel.
*all credits are on github source on commits.
github source: https://github.com/LuizPauloDamaceno/kernel-copyleft
Download: https://androidfilehost.com/?fid=4349826312261682492
*Make boot partition backup! Dont ask-me for ETA or "dont work on specifc version", i'm done this in my limited free time and just for fun, so, if you having problems with this kernel just restore some boot partition backup.
*Antutu benchmark done with maximum performance settings without any safety valve (thermal-engine disabled with command stop thermal-engine at terminal emulator and all governors in performance, io manager deadline).
LuizPauloDamaceno said:
Hello friends, soon i'm gona publish my project for this device. The kernel special features includes QC tweaks (2500mA charging with QC 2.0+ Chargers), GPU Overclocking (to 750MHz) and CPU overclocking (1.44GHz LITTLE and 2.01GHz BIG).
Its comming the SUZU KILLER!!!
Click to expand...
Click to collapse
Good news, but oreo kernel source (3.10) have not yet been released...
will you use 4.4 or 4.9?
linckandrea said:
Good news, but oreo kernel source (3.10) have not yet been released...
will you use 4.4 or 4.9?
Click to expand...
Click to collapse
kernel source to oreo is "kernel-copyleft" no longer maintened from sony, but uses a common code.
https://github.com/LuizPauloDamaceno/kernel-copyleft
Released. See first topic.
Does this work on Nougat?
---------- Post added at 09:40 AM ---------- Previous post was at 09:38 AM ----------
Is it only for F5122?
A Good Kid said:
Does this work on Nougat?
---------- Post added at 09:40 AM ---------- Previous post was at 09:38 AM ----------
Is it only for F5122?
Click to expand...
Click to collapse
Tested on oreo and compilled for oreo.
But it says kernel F5122.. I have f5121
It is for every oreo build or only for 97?
You could oc it 1.5ghz cuz the same cpu on a5 I overclocked it to 1.5 from 1.2
A Good Kid said:
But it says kernel F5122.. I have f5121
Click to expand...
Click to collapse
It's working on my F5121.
Sent from my Xperia X using XDA Labs
This kernel is not safe at all.
Just to be sure you know what you are doing.
This commit is freakin too dangerous. It can burn your controller, and I think it will for 1,5-2 yo devices after some chargings. I'm not even talking about these ones: this and this. And that's only a start, thankfully I am too lazy to get deeper into your commits but I am 100% sure they are as dangerous as this one. Are you just randomly putting pieces of code from another kernels and you don't care about safety of users that will use your kernel?
And yes I know it's called Extreme, but this thing is just... oh wait, you called that "Suzu killer". Then I don't have any claims anymore, lol.
@LuizPauloDamaceno hi! can you add this 2 commits to your kernel? It's for SuperUserMod.
zezell said:
Just to be sure you know what you are doing.
This commit is freakin too dangerous. It can burn your controller, and I think it will for 1,5-2 yo devices after some chargings. I'm not even talking about these ones: this and this. And that's only a start, thankfully I am too lazy to get deeper into your commits but I am 100% sure they are as dangerous as this one. Are you just randomly putting pieces of code from another kernels and you don't care about safety of users that will use your kernel?
And yes I know it's called Extreme, but this thing is just... oh wait, you called that "Suzu killer". Then I don't have any claims anymore, lol.
Click to expand...
Click to collapse
I see you know basics of reading... And, if you see my git you will see another kernels for another devices that have similar things. So, i haven't fault if another devs burn phones doing these things. My suzu is recently bought and i'm using my kernel with stock thermal configurations, that helps stabilizing things. None of my another kernels have users reclamations of "burned boards", i only improve configurations that already is done by factories. But as i see you dont give to you the work of see mine another works.
"Are you just randomly putting pieces of code from another kernels and you don't care about safety of users that will use your kernel? " This is my work, another kernels just add "force fast charge" to force it maximum current always, for example. Mine one incrases the limits but software can take all control over the current that is used at charging for example.
About the security, i use my essential modifications for two weeks or more before post anything on git or public download and my face was on risk for the initial tests.
Please, make some questions before post "things" (to dont say another words) that can prejudice the job of developers. You is free to use or not my kernel and you is advised on first post. About "killer", have you already saw about "irony"? xD
lubik1 said:
@LuizPauloDamaceno hi! can you add this 2 commits to your kernel? It's for SuperUserMod.
Click to expand...
Click to collapse
will be added on next release, thanks for suggestion! =D
I know you said dont ask this stuff but im in a real need so I try my luck, can you make this work on X compact?
Updated! See changelog!
Kianush said:
I know you said dont ask this stuff but im in a real need so I try my luck, can you make this work on X compact?
Click to expand...
Click to collapse
sorry but i dont do things for devices that i havent.
LuizPauloDamaceno said:
will be added on next release, thanks for suggestion! =D
Click to expand...
Click to collapse
LuizPauloDamaceno said:
Updated! See changelog!
Click to expand...
Click to collapse
no security disabling commits added?
What about safety net? Is it patched or it breaks the SN checks?
Updated! See changelog!