Hey guys!
So from observations by @rkoby13 and myself, there seems to be a demand for regular builds of DorimanX's kernel!
This thread will serve as a place for logs, reports, and discussion relating to these unofficial builds by me.
Currently the plan is to compile v9 builds, whenever @dorimanx adds major updates or significant modifications to his source, however this may, and probably will, result in UNSTABLE AND EXPERIMENTAL RELEASES
Disclaimer:
Dori tests highly experimental commits prerelease, and if your device is damaged, wiped, or in any way negatively affected by these releases it's not the fault of Dorimanx, or me. In flashing these releases you accept full responsibility for any consequences of its use.
In this op, I'll have a log of which builds are most stable and which ones have bugs reported or major issues in code, and builds with extreme issues will be removed.
As x.39 was just released, the first build will be uploaded after the next major addition to the kernel sources, and every major change after that.
If there is a commit that I have not considered major but is important to you, either reply to the thread or pm me with a link to the commit, and I'll probably update the build to include it. In future, I may also build v8 kernels until their end of life, if many people show a desire for this
Finally, just a reminder not to post logs or reports/discuss these builds in any other thread, thanks
I'll also soon be adding my new and improved stweaks settings guide, nearly everything is covered now.
Source: http://github.com/dorimanx/dorimanx-SG2-I9100-Kernel
http://github.com/dorimanx/initramfs3
if anyone has a domain they'd like to offer to mirror I'd be glad (hint hint)
dorimanx has decided to help out with building sometimes, and he'll post here! and apparently no one reads whole op, is this big enough?
latest build by cybernetus http://www.dorimanx.ataliba.net
aaaaaand computoncio has a fileserver too now!
http://dorimanx.casoncia.org
Changelogs:
9.39
v1 - 23/8 up!
- ram value display fixed
- toggle to completely stop logcat from writing
(accidentally messed up defconfig and reset it so the kernel id is the same as usual but I renamed the zip)
v2 - 26/8 up!
-compiled with linaro 13.08 gcc 4.8.2 (tuned and optimised by dori for i9100 and his kernel)
- zzmoove updated to 0.7b
- cortex brain tuned and some bugs fixed
v3 - 27/8 up
-various driver updates, cleans and optimisations
v4 - 27/8 up
-as previous
-fix for reset profiles on boot
v5 - 29/8
-ton of pulled 3.11.y driver update
-cleaning
-more optimisations from stantrc (new dev )
-there was something else I saw but I forgot
9.40
v10 cybernetus - 9/9
- changelog
Eskriminal's New and Improved DorimanX Stweaks Guide!
Starting off, I will not be covering stock standard info such as cpu clock, voltage, or the most basic governor variables. @droidphile has a brilliant comprehensive guide to these things and more, search!
Now let's get started! This guide will be in the same order as stweaks itself, and if i miss anything that you wanted, pm me
Topic 1. Advanced/Custom Cpu Governor variables
Here will be discussed governors such as nightmare, darkness, and perhaps zzmoove (if i have time), and their variables.
Freq_step
this controls how large the step up should be when the cpu load hits either the up_threshold, or the inc_cpu_load, depending on your governor.
It is a percentage, where the percentage involved is that of the cpu clock prior to the switch.
Down_threshold/dec_cpu_load
same as up_threshold or inc_cpu_load, but in the reverse, these dictate at what load to decrease frequency
Cpu_up_rate/cpu_down_rate
these values determine how many readings of cpu load will be collected (i.e. 60% or 80%) before being compared to the inc_cpu_load or dec_cpu_load respectively
Freq_step_dec
the same as freq_step, but for decreasing frequency
Freq_step_dec_at_max_freq
identical to freq_step_dec, but while cpu is at values above freq_for_responsiveness_max
Up_sf_step/Down_sf_step
both have detailed descriptions in app from alucard
<more to come>
Topic 2. Memory Management
This tab in stweaks dictates whether Dorimanx kernel should control the Android memory management system (Auto Oom Control switch)
The settings here control how it should control it, with the more aggressive the setting, the quicker apps will be killed at low memory.
<more to come>
Topic 3. GPU Tab
The GPU settings are all identical in function to the way CPU control works, with the frequency steps available and voltage/threshold changes.
The GPU utilisation timeout controls how fast the gpu should respond to a heavy load.
With the thresholds, as with cpu the higher they are the slower it will scale frequencies up, and the faster it'll scale down.
<more details to come>
Topic 4. Screen Tab
Here all screen settings and brightness controls are changeable.
min_bl controls how fast auto-brightness should increase screen brightness level, when this value is higher the screen will stay on minimum brightness for longer.
min_gamma and max_gamma control the minimum and maximum brightness available to auto-brightness
LCD Power Reduce lowers screen brightness to save battery
Screen colour modes control colour levels
Gamma Shift changes all brightness system-wide up or down based on the value put in
FB early suspend delay controls delay after sleep should activate before running the screen off animation
Vibration force controls the power of vibrations system-wide
Slide2Wake toggles waking the device by swiping across the screen from left to right
mDNIe Negative Toggle enables or disables inverting colours by pressing the home button the number of times set below
Touch screen tweaks control sensitivity options - They're advanced, and usually don't need to be touched
Topic 5. Sound Tab
Most settings are self-explanatory, if anyone wants this actually explained, shoot me a pm.
Topic 6. Big Collection, all Misc. Kernel settings! (BLN, CRON, Logger, Auto wifi etc.)
BLN controls whether to switch on backlights when notifications are received during phone sleep.
The bln effect controls the light mode of these keys (doesn't work with BLN without wakelock)
Notification timeout controls the maximum length of time the keys should be on before turning off (doesn't work with BLN without wakelock)
LED timeout controls the timeout on backlight keys during phone use
BLNWW sets BLN to run without forcing the cpu to stay out of deep sleep, saving battery
LED fadeout controls the effect when the keys switch off
LED on touch determines whether the keys will turn on when pressed during use
LED voltage level controls the key brightness
CRON is a timed automatic service which can be used to run various optimisations and updates as detailed in the 'Other' tab in Stweaks
Fix Permissions may solve fcs in apps
Zipaligning apps may optimise them to run faster
Database optimising will clear and compact the system data, potentially increasing system performance
GPS zone changes to your local ntp server may decrease gps lock times and increase accuracy
USB settings control the device storage mount mode.
Charge current levels control speed of charging from various sources, with the higher the current, the faster the flow and therefore charge
Resetting the fuel guage chip may solve issues when battery appears to drop after reboots, as the chip will recalibrate
The Ad-blocker will block advertisements by ip in most apps
Filesystem tools attempt to recover corrupt partitions on the disk
Root settings control device root security
Cortexbrain controls the switching between various things based on screen state including cpu governor and clock, io scheduler, auto wifi, auto data, and logger control
The android logger writes logs of system errors, disable unless you plan on using this
auto data disables mobile data when the screen is off, with the delay before doing so below it (auto wifi is the same for wireless internet)
Various tweaks change system values relevant to each one
Eco tweaks modifies hotplugging logic when battery drops below the eco-level threshold to save battery by preferring use of only a single cpu core
This is just a preliminary guide, my corrupted hdd destroyed the other one I'd been writing for @rkoby13
Reserve one more! Just in case!
Sent from my GT-I9100 using XDA Premium 4 mobile app
and another at the recommendation above
Sent from my GT-I9100 using Tapatalk 2
Hehe, can't wait. This is an good idea.
Galaxy S2 powered by Dorimanx!
so what do you guys think of v8? want me to build it also?
Sent from my GT-I9100 using Tapatalk 2
Great idea
Posté via Vanilla Rootbox
Can you please build a dori Kernel for 4.3 where internal sd card is switched? Internal -> external.
Gesendet von meinem Galaxy S2 mit CM10.1
SWTR said:
Can you please build a dori Kernel for 4.3 where internal sd card is switched? Internal -> external.
Gesendet von meinem Galaxy S2 mit CM10.1
Click to expand...
Click to collapse
we'll see, unless many people want it it's probably not worth patching the changes in if I can
Sent from my GT-I9100 using Tapatalk 2
@eskriminal
can you just link to git where you build from?....or maybe build one kernel....if there are any new commits ....because place holders are not allowed at xda.....you need at least source link ma8 .....and keep up great job.....because last one you shared with me was awesome build.....although latest 9.39 is a beast.........waiting for new commits and build.....
rkoby13 said:
@eskriminal
can you just link to git where you build from?....or maybe build one kernel....if there are any new commits ....because place holders are not allowed at xda.....you need at least source link ma8 .....and keep up great job.....because last one you shared with me was awesome build.....although latest 9.39 is a beast.........waiting for new commits and build.....
Click to expand...
Click to collapse
edited op to include source and info for when downloads are up
Sent from my GT-I9100 using Tapatalk 2
hi guys..im using philz touch kernel..i want little more brightness ..so which kernel has got the maximum brightness ?? i dont have issues with battery drain
hunkyycbz said:
hi guys..im using philz touch kernel..i want little more brightness ..so which kernel has got the maximum brightness ?? i dont have issues with battery drain
Click to expand...
Click to collapse
any dorimanx build has gamma control in the screen tab on stweaks, raise it to increase brightness
Sent from my GT-I9100 using Tapatalk 2
I bought an optimus g for wife, but started to play with it, lock bootloader, hard to root, no custom kernel for oc. It's nice to see that s2 community it's still active.
Regarding domain, maybe ApriliaM3 from neatrom thread, he has an huge one with mods, kernels, rom.
http://d-h.st/users/ApriliaM3/?fld_id=8738#files
Galaxy S2 powered by Dorimanx!
Agreed. Nice to see the i9100 community still active
I have a question. What is a "V8" kernel and if its good stuff, why isn't included in Dorimanx official build? I'm assuming because of possible bugs?
StatusQuo209 said:
Agreed. Nice to see the i9100 community still active
I have a question. What is a "V8" kernel and if its good stuff, why isn't included in Dorimanx official build? I'm assuming because of possible bugs?
Click to expand...
Click to collapse
maybe you lost track....but dorimanx kernel has 2 branches....8.xx & 9.xx....
8.xx has support for Samsung stock JB roms...aswel as aosp/aokp/cm....<---4.2.2 and bellow...to 4.1.2...
9.xx branch supports 4.2.2 and 4.3 only...aokp/cm/aosp roms and dualboot between them....and with 9.xx you have more ram avaliable ....other things you can find in original dorimanx kernel thread....
v8, for official roms. v9, custom roms.
Dorimanx put sources in git daily and build his kernel. Anyone who could and want, take his sources and make an kernel, based on his sources. So, that's what we are here on this thread, we wait to grab and test an custom kernel
Galaxy S2 powered by Dorimanx!
rkoby13 said:
maybe you lost track....but dorimanx kernel has 2 branches....8.xx & 9.xx...8.xx has support for Samsung stock JB roms...aswel as aosp/aokp/cm....<---4.2.2 and bellow...to 4.1.2...
9.xx branch supports 4.2.2 and 4.3 only...aokp/cm/aosp roms and dualboot between them....and with 9.xx you have more ram avaliable ....other things you can find in original dorimanx kernel thread....
Click to expand...
Click to collapse
dude! I totally lost my mind. Lol. I totally got confused, I know there is a version 8 of the kernel. I was thinking that this was like the "V6 Supercharger" mod that some people use. I thought there was a new version or something that was kernel based. Hahaha. Thanks for clearing that up for me bud.
Excuse my ignorance...
StatusQuo209 said:
Agreed. Nice to see the i9100 community still active
I have a question. What is a "V8" kernel and if its good stuff, why isn't included in Dorimanx official build? I'm assuming because of possible bugs?
Click to expand...
Click to collapse
aaaaand V8.xx is official..,just like 9.xx
bugs(if any) are the same.....but 9.39 is.....<3
Related
Read the Known Issues section of this post below along with the FAQ a few posts down before posting.
A few people have asked about I9100 builds of my Daily Driver kernel for the SGH-I777. I normally hate blind development, but since most I9100 guys are doing it for I777 targets, I may as well try going the other way. Since it fails the definition of being a "daily driver" as I own an I777 and not I9100 - it will not be using the Daily Driver name.
This should be compatible with most stock-derived Gingerbread firmwares, with a few exceptions listed below. It is NOT compatible with CM7/MIUI or any other AOSP-derived firmware. It is NOT compatible with ICS and WILL NOT BE until ICS kernel source for the I9100 is released. At that point a new thread will be created for those kernels. I am testing it currently with self-deodexed/debloated/Hellraised XWLA4.
The following firmware bases are likely to deliver poor battery life with this kernel due to wifi bugs in the firmware:
XXKI3, UCKK6, XWKK5 - especially UCKK6 and XWKK5
This kernel series is intended to be similar in spirit to my Daily Driver series for the Infuse at http://forum.xda-developers.com/showthread.php?t=1212795
It is built from sources at https://github.com/Entropy512/linux_kernel_sgh-i777/commits/oc_codeworkx, and initramfs at https://github.com/Entropy512/initramfs_sgh-i777/commits/master
My general goals are to focus on stability and battery life. If it comes to a tradeoff between performance and the above two, I will choose stability/battery life. In general I will choose stability first, with the exception of undervolting.
I keep my initramfs clean - There are no tweaks or other automated scripts built into this kernel. For a collection of tweaks I am working on and documentation on them, see http://forum.xda-developers.com/showthread.php?t=1378080
Current features:
I9100 Update3 base
Touchscreen drivers from I777 source code base
codeworkx's cpuidle patch - should improve battery life a bit. In most cases it will likely not improve things much, but in rare cases it will result in significant improvements. (I only have one partially-reproducible test case on the Infuse so far)
JHash 3
BFQ I/O scheduler
CIFS module in initramfs
CWM 5.0.2.8 compiled from CM7 sources on 2/28/2012
"insecure" kernel (meaning root in ADB)
CPU governor set to Conservative by default to conserve some battery - this will make your device slightly less responsive, use SetCPU or a similar app to return to ondemand if you want it, or reduce the conservative polling interval
Filesystem readahead tweaks in initramfs
netarchy's Sleep of Death fix
netarchy's conservative governor tuning patch - should improve responsiveness of devices when using the conservative governor if you reduce the polling interval (misnamed as sample_rate) - the I9100 community calls this "lionheart" even though it's really only a 2-line patch
Battery charge current monitoring (CurrentWidget) support - only reports charge current and not discharge, and reports a value 2.85 times the actual current. Use CurrentWidget's "operation on value" to divide by 2.85.
Miscellaneous bugfixes pulled from Ninphetamine and CM7 sources - see github for details
/system/etc/init.d support in initramfs - Note that this only runs stuff in /system/etc/init.d - ROM developers or you need to create it. Attached is an example script that will change the CPU frequency governor to ondemand if placed in /system/etc/init.d and set to executable
Four "use at your own risk" features that trade performance for stability - See Post #4 for details
Standard bootanimation support
/proc/last_kmsg crash debugging support
NFS modules in initramfs - note that they must be insmodded in a specific order: sunrpc.ko, lockd.ko, then nfs.ko
Fix for fuel_alerted perma-wakelocks
Fix for wifi tethering on I9100 ROMs that have been Hellraised to I777
Bump up TCP buffer sizes in initramfs to match that of the Infuse - may help network performance in some cases
cpuidle driver from Tab 7 Plus kernel - allows entry into AFTR more often - includes MFC interoperability fix (Should not break video playback.)
Support Bluetooth HID on newer firmware bases
3-step GPU clock/voltage control
Extended hotplug tuning
Support for Xan's ExTweaks universal tuning app - https://market.android.com/details?id=com.darekxan.extweaks.app
Planned features, short term:
Determine if issues with PINlock when running I9100 firmwares on I777 have kernel involvement, and fix them if this is the case.
Planned features, mid-term:
Potentially my first departure from "standard" governors, with a focus on improving hotplugging logic
Planned features, long-term:
Improved battery charge algorithm for faster charging - Initial research indicates we have an alternate battery charger chip (MAX8922) that differs from the MAX8997 used in the I9100. We DO have an 8997 also - but on our device for some reason Samsung decided to use an alternate chip instead of using the 8997's built-in charging. This means we have far fewer options (90,400,660 mA) in terms of charge rates compared to the I9100 (from 200 to 950 in 50 mA steps). So we might not be able to implement any fancy charging algorithms.
Features not planned:
BFS process scheduler - I have only once ever seen a test case where this clearly outperformed the mainline Linux scheduler (multithread x264 encoding) - The mainline schedule was fixed in the next release and BFS now has no performance benefits
Any feature that trades off stability or data integrity for performance unless it can be disabled entirely and defaulted to "off"
Any feature that cannot have functionality tested without a paid app. Interface-only checks don't cut it - I don't want users complaining that the app they paid for didn't work because an interface check worked but function didn't
Touch recovery - too prone to unintentional user input in dangerous situations. I will reconsider this with ICS.
ARM_TOPOLOGY/SCHED_MC - See http://forum.xda-developers.com/showpost.php?p=23193259&postcount=100 for details
Known issues:
Power management regression somewhere between 12/8/11 and 1/2/12 - Intermittent high drain without high AOS or reduced deep sleep percentage when on some wifi networks - seems more likely if GPS is used when connected to wifi. Wifi with high AOS/reduced deep sleep is not a kernel problem. This appears to only happen on some firmwares - it happens on XXKI3 but not XWKL1. It is likely connected to a wifi power management bug in some firmwares. A debugging feature in 2/7 and later will allow identification of such firmwares - see http://forum.xda-developers.com/showpost.php?p=22581928&postcount=1777 for details
Some people have reported touchkey lights becoming disabled until the screen is turned off and back on again. Under investigation - seems to mainly happen on firmwares with BLN-modded liblights even if the BLN app isn't used
Internal and External SD card are swapped in CWM currently
Keymap is a little funky in CWM for I9100 users. VolUp/VolDn to move, Power to select is reported to work, but bottom keys are funky. Working on it
A few users have reported that when Hellraising I9100 firmwares to I777, they are unable to set up a PIN-lock. If this occurs for I9100 users on their own devices, I need to look into initramfs fixes and this will be my top priority.
Basic flashing instructions for .tar releases (NOTE - There are currently no releases in this category. These instructions only remain for heimdall+ZIP users:
(Tested on Linux, not tested MacOS/Windows but should work) Heimdall - Extract the contents of the tar file, enter download mode, and flash with the following command line:
Code:
heimdall flash --kernel zImage
Flashing instructions for .zip releases:
Flash in CWM, or extract the zImage and use the Heimdall instructions above.
Please do not ask how to enter download mode or install Heimdall/Odin in this thread - these are basic generic skills anyone flashing custom firmwares on Samsung devices should know and plenty of documentation exists elsewhere. If you really need to ask, use the General forum, or if created, the Q&A forum. I want to try to keep this thread clean and only with bug reports and issues specific to this release, not general HOWTO or troubleshooting posts. Some of the information you need is in jivy26's FAQs thread at http://forum.xda-developers.com/showthread.php?t=1288112 - Reading at least the first post of this thread in its entirety is STRONGLY recommended.
Bug reports:
If you have a crash (reboot all the way to Galaxy S I9100 screen), use ADB dump the contents of /proc/last_kmsg and post
If you have oddball behavior, include a clearly reproducible test case with your report, or use ADB to obtain a dmesg and logcat capturing the odd behavior at the time of error.
Similar to flashing - using ADB and obtaining last_kmsg, dmesg, and logcat dumps are basic skills that anyone working with custom firmwares on Android devices should have. If you need help with these, do some searching, or post in the General forum or Q&A forum.
Firmware ("ROM") Developers:
While I cannot restrict anyone from putting this kernel into a ROM as long as links are given to the github sources for GPL compliance, I request that anyone who includes this kernel in a firmware release does the following out of courtesy:
Link to this thread
Clearly indicate in your firmware changelog which Daily Driver kernel release is included in your firmware release whenever you change DD releases - this lets users identify whether a fix is present in the kernel they're using or not
Kernel Developers:
Similar to my request for ROM developers, while I can't restrict you from doing anything, I ask as a courtesy that if you cherry-pick my commits, you do the following:
Please don't rebase my commits into a large multi-feature without consulting me - rebasing related bugfixes together is OK.
Please try not to implement lots of unrelated features or bugfixes in a single git commit - it makes it hard to reimplement that when Samsung drops new sources or releases a new device
ALL OF MY RELEASES ARE NAMED BY RELEASE DATE - MMDDYYYY. See the changelog for differences between Experimental (exp) and non-exp versions for days where dual releases are made.
Change Log
The primary change log will be kept in my I777 kernel thread at http://forum.xda-developers.com/showpost.php?p=18129037&postcount=2
Unless I9100-specific items are implemented, this post will simply indicate which I777 release the kernel corresponds to.
3/7/2012:
Corresponds to Daily Driver 3/7/2012
03/05/2012:
Corresponds to Daily Driver 3/5/2012
03/04/2012-B:
Corresponds to Daily Driver 3/4/2012-B
03/04/2012:
Corresponds to Daily Driver 3/4/2012
03/03/2012-B:
Corresponds to Daily Driver 3/3/2012-B
03/03/2012:
Corresponds to Daily Driver 3/3/2012
Initial release was bad, that was an I777 build. Reuploaded at 4:22 PM Eastern Standard time on 3/3 - Redownload if you downloaded before that
3/02/2012:
Corresponds to Daily Driver 3/02/2012
2/28/2012:
Corresponds to Daily Driver 2/28/2012
IMPORTANT: Internal/External sdcards have been swapped in CWM to be consistent with Android standards!
2/26/2012:
Corresponds to Daily Driver 2/26/2012
Initial release, 02/15/2012:
I know it's dated 2/15 and not 2/26, because that's when it was built. Thanks to khartaras for indicating that it isn't at least a horrible turd when used on an I9100.
This release corresponds to the 2/15/2012-C release of I777 Daily Driver
Here Be Dragons
This post is for features present in the kernel that are "use at your own risk" - They have either potential or guaranteed negative side effects if used.
Overclocking (CPU):
Enable using SetCPU or a similar app
USE AT YOUR OWN RISK. DO NOT REPORT BUGS OR PROBLEMS IF YOU ARE OVERCLOCKING OR UNDERVOLTING. IF YOU EXPERIENCE ANY STABILITY PROBLEMS, DISABLE ALL OC/UV
Overclocking (GPU):
See Ninphetamine kernel for documentation - Same control method
USE AT YOUR OWN RISK. DO NOT REPORT BUGS OR PROBLEMS IF YOU ARE OVERCLOCKING. IF YOU EXPERIENCE ANY STABILITY PROBLEMS, DISABLE ALL OC
Per-File fsync() disable:
This allows you to disable per-file write forced syncs. (e.g. if an app tries to force a write straight to disk, it'll just go to cache). This achieves the same goal as the modded sqlite hacks seen in tweaks such as USAS, however it can be disabled at runtime.
WARNING: THIS CAN CAUSE DATA LOSS OR CORRUPTION IN A CRASH
To enable, do the following in a terminal, or add it to an init.d script (look at my ondemand script as an example):
Code:
echo "1" > /sys/module/sync/parameters/fsync_disabled
And to disable (return to the default):
Code:
echo "0" > /sys/module/sync/parameters/fsync_disabled
Good for around 200 points of epeen in the database benchmarks in Antutu or 500-600 points of epeen in Quadrant. Real-world benefit: Probably not worth the data integrity risk, but you've got a choice now.
Backlight Notifications (BLN):
This allows the touchkey backlights to be used for notifications. Some stock apps (such as stock MMS) don't support it. Supposedly services.jar mods can change this.
This WILL drain your battery when a notification is active due to a wakelock that holds deep sleep. Sorry, it's either this or instability for the time being.
In addition to the BLN control app, the ROM needs a modified liblights file for this to work
Attached here - Liblights - both BLN-modified (extracted from VillainROM 3.0) and stock I777
To install, take the file and push it to /system:
Code:
adb remount
adb push <file> /system/lib/hw/lights.SGH-I777.so
adb chmod 644 /system/lib/hw/lights.SGH-I777.so
Then reboot
Note that on a Hellraised ROM, you need to replace SGH-I777 with GT-I9100. This includes manually ported ROMs like Cognition 777
Like my prerooted system image, this file is compressed using 7-Zip to prevent people from trying to flash it with CWM
OK, right now this post only has documentation of one "special but safe" feature:
To enable debugging of high deleted_wake_locks time, I've set this up to allow wake_lock_destroy() to be debugged without enabling DEBUG_WAKE_LOCK (which spams dmesg with a ton of stuff not needed for wake_lock_destroy() debugging). To enable, add 32 to the value of /sys/module/wakelock/parameters/debug_mask - This defaults to 3, so the proper value is 35.
Code:
echo "35" > /sys/module/wakelock/parameters/debug_mask
Return this to 3 to set it back to the default.
With this, you'll see wake_lock_destroy debugging information in your dmesg output. This is only needed if you have very high deleted_wake_locks times.
The following is known to cause deleted_wake_locks:
Turning off wifi will convert all wlan wakelocks into deleted_wake_locks
FAQ
Q: I installed this and still don't have root?
A: I keep a clean initramfs. There are NO tweak scripts in it, and no autoinjection scripts. To root your device, flash one of ChainsDD's Superuser packages in CWM
Q: I don't like the default I/O governor, why is it this way?
A: Clean initramfs (if you need to flash a kernel cleaner script after my kernel, I have failed or an app cluttered up your init.d) - If you want to change the default governor and tune the filesystem, see my init.d scripts thread.
Q: Why is it so laggy by default?
A: I don't believe in having half my patches tuning default values of things the user can change. In addition, as stated above - battery life is valued over performance, so default governor settings will be biased towards battery. My personal recommendation if you wish to increase performance (at the cost of battery life) is to drop the sample_rate for the conservative governor using SetCPU or a similar tool - this will significantly improve performance. It provides nearly all of the benefits of the original "lionheart" without allowing the sample_rate to go dangerously low. In a future release I'm going to drop the minimum a little bit more.
Q: Something went wrong. I'm using some stupid comprehensive tweakscript. Y U NO FIX?
A: I will not support anyone who is using a comprehensive tweak script (Thunderbolt, V6 Supercharger, etc. - ESPECIALLY V6 Supercharger, as its developer has multiple times in the past put in dangerous tuning options. For example, he disabled the panic reboot timeout, which combined with Samsung's ****ty wifi driver on the Tab 7 Plus, led to multiple Tabs draining their battery all the way to the battery's failsafe cutoff.) If a specific individual tweak causes a problem, let me know - but you'd better know EXACTLY which tweak it is. In addition to the above issues with V6SC, many "tweak scripts" achieve their goals by trading filesystem integrity for performance, and irresponsibly don't warn the user about this fact. See, for example, the fsync disable feature above - it's dangerous, but don't say I didn't warn you it was.
Q: What voltages do you use?
A: This is irrelevant. Every device is different, if a given set of voltages worked on all devices, Samsung would've made it stock. I will report any discussion of voltage recommendations to the moderator for cluttering the thread. If you're undervolting, you need to take responsibility and do it on your own.
Q: Why don't you support AOSP firmwares (CM7, etc.)?
A: I know that the CM team frowns upon alternate kernels as it makes their testing job more difficult. Similarly, supporting too many firmware bases makes my job more difficult. Out of respect for the skills of codeworkx and atinm, I will not release kernels that could make their life harder. I periodically give them the heads-up on patches that I think are important though.
Q: What's with the toilet humor of the name?
A: Long ago in the Infuse community, there was a person (lemons) that was starting to do some smali hacks (camera modding and such), and was planning on eventually releasing a ROM. He was a pretty good guy, and had lots of potential. He and others joked that since it was his first attempt, it should be called ****ROM. Sadly, lemons never followed through and just disappeared, so for months, ****ROM never became a reality. Eventually it was realized in the form of a deodexing/porting/basic modding guide for I777 users at http://forum.xda-developers.com/showthread.php?t=1505685. In addition - I hate hype and marketing, better to set expectations low and let the code prove itself on its own merits. Since I'm blind-developing, I can't just say it's my daily driver because in this case, I am unfortunately not eating my own dogfood.
Q: Why don't you base on 2.6.35.14?
A: That would be my Experimental series. It's temporarily on hold for a variety of reasons but will return once I finish reimplementing some patches. The great thing about git branching is I've been able to maintain .7 and .14 trees simultaneously with ease.
Q: Sometimes my touchscreen is unresponsive right after a wakeup, why?
A: It seems, based on reports from khartras and teiglin, that TouchScreenTuner does not play well with the I777 touchscreen drivers. I'm not sure if it's even necessary with them - in the months since October, the only time I have ever received touchscreen complaints from I777 users was when running I9100 update3 touchscreen drivers. TST may just be working around broken drivers...
Reserved for ?????
Thanks for this. I will try later.
Again very thanks.
Enviado do meu Galaxy S2 usando TapaTalk
Going to try this kernel for the sole reason that I think you're a great guy on here and I enjoy reading your informative posts - you always seek to educate rather than put people down.
Thanks Entropy.
Uploaded a new release, this has just a few small patches, bringing it up to the same base as Daily Driver 2/26/2012
As a compulsive lurker, reader and searcher, ive been looking forward to this release..
Alongside Pulser and Ninpo, your informative postings and professional ethic enable users like myself to maximize the potential of our devices.
Thanks mate, i have no doubt this will be brilliant..
Thanks Entropy, I've missed your work since I moved from Infuse over here instead of to I777-land. I do have a question, though--I note the only "nonstandard" I/O scheduler you included was BFQ. Do you find sio/vr problematic, or do they just not provide any benefit from your perspective?
teiglin said:
Thanks Entropy, I've missed your work since I moved from Infuse over here instead of to I777-land. I do have a question, though--I note the only "nonstandard" I/O scheduler you included was BFQ. Do you find sio/vr problematic, or do they just not provide any benefit from your perspective?
Click to expand...
Click to collapse
I'm considering adding these - I've found that alternate governors/schedulers often cause more problems than they solve.
Thanks for sharing your kernel with us i9100 users Enthropy. I really like your stability+ battery approach. Will be giving the kernel a good go.
Sorry...this kernel is comparible with jkay brightness profile?
Inviato dal mio GT-I9100 usando Tapatalk
coloxim said:
Sorry...this kernel is comparible with jkay brightness profile?
Inviato dal mio GT-I9100 usando Tapatalk
Click to expand...
Click to collapse
No - And right now, I am unaware of any kernel that is. As much as I like JKay's work, I believe he lacks understanding of how screen brightness works on the I9100 and I777.
Even JKay is unaware of any kernels that support those profiles. See entry 12 in his FAQ.
To implement additional brightness steps, an additional gamma table for each brightness step needs to be implemented - https://github.com/Entropy512/linux_kernel_sgh-i777/blob/master/drivers/video/samsung/ld9040_gamma.h
So until FAQ section 12 has clearly defined (and achievable) requirements for compatibility, or JKay declares a specific kernel compatible in FAQ section 12 of his mod, I won't be doing anything. Creating a custom gamma table entry is not easy as it requires a LOT of tweaking and good colorimeter hardware. Supercurio has done it at high brightness levels to my knowledge, but I don't think he's done it for low brightness levels and I don't think he's added extra gamma tables for additional brightness steps.
Edit: I have seen that Speedmod and Redpill do change the table entries for the lowest two brightness settings - however, they don't add any new bins, so the brightness change is achieved even on JKay profiles that don't supposedly require kernel support. e.g. JKay's "dark, requires kernel support" are pointless because the only kernels that actually provide dimmer minimum backlight do so even with his profiles that don't claim to require custom kernels. (And the "super dark" and "dark" profiles will behave the same regardless of kernel.)
What's interesting is hardcore did it for only two of three available panel types. Either two of Samsung's panel types are brighter than others, or hardcore did this without testing on some panel variants and just thought "the numbers are different, I'll change them". I'll look into playing with this as it would be nice to have lower minimum brightness, but it's somewhat low priority as it's easy to simply make things look like **** if you're not careful.
its possible to make your kernel fully compatible with the cmw manager of chainfire
for now some fonctions are desactivate
anyway i m testing it now and all seems to be good
So far so good mate.
Batterylife we will see in a day or two but all in all running fine.
Thanks and go ahead with ur work.
CHEERS ;-)
Sent from my Galaxy S2 - I9100 with SensatioN Rom!
F3nr1s said:
its possible to make your kernel fully compatible with the cmw manager of chainfire
for now some fonctions are desactivate
anyway i m testing it now and all seems to be good
Click to expand...
Click to collapse
Others have asked me this - if he has compatibility guidelines posted somewhere, I'll take a look at them.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Battery in deep sleep is exceptional, 2% lost in 5 hours with WiFi enabled and emails syncing.
Sent from my GT-I9100 using XDA App
Facality
weird name for a kernel..or for pretty much anything..dude
Imitated, but NEVER duplicated!
Rock solid stability and great performance for your SGH-I777.
Features:
Full support for Kernel Screen Gestures Builder
WIFI Driver ported from SG4
New Mali V2 Video Driver
Overclocking up to 1400 MHz
Be very careful with voltage settings. UnderVolting usually causes bad things..
Slide2Wake is now automatically disabled while on a call. (Modded for less battery drain)
Native USB Tethering.
Native Wi-Fi Tethering
File systems support: Ext3/4, FAT32, NFS, CIFS, NTFS
Added tweaks to increase I/O Speed.
Added tweaks to increase CPU speed
Removed all the debuggers
Better picture quality thanks to camera tweaks
BLN without Wakelock - see STweaks BLN tab to activate.
Touch Keys Light change with the screen brightness
MMC_CAP_ERASE not present
Sound boost controls in STweaks.
Added mdnie interface and made hardcore’s sharpness tweaks optional
5 GPU FREQ Steps from 108Mhz to 520Mhz
Ultra KSM from 3.9.y kernel.
[/LIST]
Installation Instructions:
Wipe cache
Wipe dalvik
Install AJK - DO NOT REBOOT YET...
While still in recovery, go to advanced and reboot recovery
After recovery has been restarted, go into kernel specific options and Reset ExTweaks profiles
Fix permissions in recovery
Reboot and enjoy the new kernel
{
"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"
}
NoSwap - for Cooked and AT&T stock JB
MicSwap - for ShoStock3 and other ported i9100 ROMs
AOSP - for any AOSP ROM, such as CM10.2
AJK v4.9 NoSwap
Dev-Host
Goo
AJK v4.9 MicSwap
Dev-Host
Goo
AJK v4.9 AOSP
Dev-Host
Goo
NOTE: Changelog information for builds prior to v3.2 was somehow deleted while the thread was closed (at my request...) for a short while.
I will try to recover the lost changelog information and add it as I can.
Changelog:
v5.0 (in development)
Updated ROM compatibility - now works on all current ROMs
Fixed SoD when using ZZMOOVE as sleep governor
Imported the latest Samsung ramdisk files
Fixed an issue where profiles might be reset
- Any further profile issue MUST be due to a ROM or rogue app issue.
- The logs I have seen are indicating that the profile was deleted by something. Kernel is not capable of this...
v4.9
Fixed JB_Sound_Fix on Samsung based ROMs
Fixed a small profile issue
Fixed an issue with CPU grouping
Improved ROM compatibility
Misc fixes & tweaks
New battery profile
New performance profile - Highly recommended! Great performance & very good battery life!
GPIO pin definitions fixed
There's more but I forgot to write it down as I went...
v4.8
Small FileSystem tweak
Improved ROM compatibility
Disabled the boot logo for now
v4.7
Fixed various issues with CM10.1.3 RC2
Sync'd CM10.x init files with CM sources
Set ROOT to default ON for CM10.2
Updated ZZMOOVE to v0.7d
Set default profile sleep scheduler to BFQ
New Battery profile, based on ZZMOOVE v0.7d
New boot logo by Teknodad1974
v4.6
Tuned battery & performance profiles a bit
Tweaked CortexBrain
Fixed a small profile bug
Updated ZZMOOVE governor
-new ZZMOOVE governor is VERY smooth (smoothest gov I have found), uses slightly more battery than Hyper.
v4.5
Nice new boot logo by Teknodad1974
Recovery background remains plain black to make it easier to read recovery text
Fixed a small issue with recovery
Added exFAT support
Updated governors & i/o schedulers
Updated profiles
Updated Stweaks
Added the Dorimanx implementation of CPU Voltage Groups. This will let people see why some phones UV easily and some cannot UV.
v4.4
Added support for Android 4.3
Some code cleanup
Tweaked touchscreen and display to improve smoothness
v4.3
Reverted part of the frequency cleanup as it caused a slight hesitation in the UI
v4.2
Bugfix - corrected CPU frequency table
Boots & settles in much faster now
v4.1
Undervolting has been given a reprive thanks to topiratiko & samprocat
Use UV with CAUTION and expect no support when using UV
CPU frequency table has been tuned down to 6 primary frequencies for efficiency
CPU voltages have been corrected in the profiles to account for the new frequency table
Fixed mic swapping (MicSwap version only, obviously)
Due to the changes made to the CPU frequency table and the CPU voltage table,
it is CRITICAL that you follow the installation instructions exactly as outlined here.
S959G users please ask for assistance from more experienced S959G users
if you need assistance..
PLEASE do not just ignore the need for profile resets!
This version will start off slow (possibly VERY SLOW) and will speed
up as it settles in. First boot can take a LONG time. This is both normal and expected.
v4
Project "SMOOTH UI" is now complete!
You should notice better performance in every way. If not, you're doing something wrong!
Fixed poor performance on Samsung ROMs - they did not like the OOM settings in v3.9 .
Any trouble reports that do not include a logcat will be ignored.
v3.9
New boot logo by Teknodad1974
Corrected the context on the Stweaks->Screen tab
Removed BLN "blink" and "fade" options as they do not work on our phones
Added a new "AJK Tweaked" OOM profile (Stweaks->Memory tab)
Most people will see a nice improvement from the new OOM profile
Slide2wake fix should be functional now
Ad-Block is expanded & updated. This is a complete ad blocking solution now
Ad-Block can be added/removes d in Stweaks->Other
Ad-Block can be updated automatically via setting in Stweaks->Other
v3.8
AKA: THE ONE
Nightmare has been tuned and should be much more stable now
Added ZZMOOVE governor by ZaneZam (a great battery or sleep governor)
New topiratiko tuned profile
MAJOR smoothness improvements made by Project "SMOOTH UI"
Re-added Touchscreen Sensitivity setting in Stweaks
Added touchscreen revision detect button in Stweaks -> Screen
Added additional touchscreen settings for different touchscreen type
Many thanks to the testing team for working hard and relaying good
information for me to build upon. :highfive:
Special thanks to topiratiko for providing invaluable information
and letting me bug him into the wee hours of the mornings
testing new kernels. :good:
v3.2
WiFi toggle bug is a thing of the past (has been for weeks now on AJK actually...)
Slide2Wake is now disabled while you are on a call.
New Mali V2 drivers - best graphics performance on the i777.
S4 code implemented for WiFi.
I will have to populate this later as it somehow got removed while
my thread was locked for maintenance.
Some suggested reading:
A Comprehensive (but not by any means definitive) Guide to Wakelocks
Please remember that this kernel was created for my friends & family to use, and I also share it here.
You are not obligated to use it. If you do decide to use this kernel, that does not give you the right to be disrespectful.
Please report any bugs that you find, and be sure to include a last_kmsg and/or logcat...it is impossible to troubleshoot without it.
Reporting something 1 time is sufficient. If someone else has already reported it, you do not need to re-report the same bug.
Remember the 2 primary rules here on XDA are:
1) Be respectful.
2) Use the search functions - both the XDA search and Google.
If you are experiencing issues that no one else is having, then it is not the kernel at fault....
Special thanks to:
Entropy512 (CyanogenMod, kernels, much more for the community)
Gokhanmoral (Siyah Kernel)
Dorimanx (Dorimanx Kernel)
@razen_kain for all the feedback & support (to everyone here)
@mr-cook for all he does for the SGSII community
@topiratiko for his tireless testing, great feedback & support and the topiratiko profile
@4-2ndtwin for his tireless testing, great feedback & support
@samprocat for his tireless testing, great feedback and tremendous support.
And a special thanks to all the donators. Your donations are greatly appreciated!
ROM Devs:
I request that anyone who includes this kernel in a firmware release does the following out of courtesy:
1) Link to this thread
2) Clearly indicate in your firmware changelog which AJK version is included in your firmware release. This lets users identify whether a fix is present in the kernel they're using or not.
Kernel source new repo available here.
Use the "master" branch.
Compiled using the supplied linaro 12.x toolchain.
Touchscreen Tuning process
1. Open ExTweaks
2. Select Screen tab
3. Go to "Batt Move Filter", increase it BY ONE and apply
4. Test it, if it still stutter, increase ONE STEP ONLY and apply
5. Repeat step 4 till the stutter/jitter is gone. Don't set it too high as it'll result the touchscreen capability lost
6. If "Batt Move Filter" is OK without any jitter again, connect your charger and go to "Chrg Move Filter"
7. Repeat step 4 till you satisfied and again: DON'T SET IT TOO HIGH, ONLY INCREASE TILL THE JITTER/STUTTER IS GONE
Do this at your own risk!
If you lost the touch capability caused by too high value then you will need to reset ExTweaks profile in recovery.
I can say its different for each device as the test shown:
-My S2: Batt Filter 16 & Chrg Filter 50, stutter/jitter gone completely, below that value the screen is stuttering/jittering.
-My son's S2: Batt Filter 13 & Chrg Filter 46, stutter/jitter gone completely, below that value the screen is stuttering/jittering.
-My daughter's S2: Batt Filter 14 & Chrg Filter 48, stutter/jitter gone completely, below that value the screen is stuttering/jittering.
A few battery saving tips:
Assuming that you are getting a decent deep sleep % and have no wakelocks, the single biggest way to improve battery life is to reduce the screen brightness.
Go into Stweaks and navigate to the Screen tab, then scroll down til you find GAMMA SHIFT and set this to -10 to -20 .. the darker the screen the better the battery life can be. As a general rule, keep the screen as dark as you can while still having it visible and functional.
Some other battery saving tips would include:
Set Stweaks->CPU->MAX NORMAL FREQUENCY to 800MHz. This works fine on my phone, but some people may need to bump this to 1000MHz for some apps.
Do not use Slide2Wake as this does increase battery consumption by 10% to 20% depending on which touchscreen your device has.
Make sure that you are using ZZMOOVE as your CPU-TUNING (SLEEP) governor as it gets the best deep sleep %.
Use Greenify to Greenify all your apps. This usually makes a noticeable difference.
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
Yessssssssss I love you aj!!! Slight type on the features where it says it supports jb Mali on the second Mali it says mail
Sent from my GS4 running CM11 Kandy Kane
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
Thanks aj gonna use it on jellybam 5.1.0
hi!
last time i did this "Reboot recovery and go into kernel specific options and Reset Stweaks profiles"
the phone sim-locked!?!
this will happen again??
Solaris_XD said:
hi!
last time i did this "Reboot recovery and go into kernel specific options and Reset Stweaks profiles"
the phone sim-locked!?!
this will happen again??
Click to expand...
Click to collapse
I am unsure of how a sim-lick can occur due to this.
To be on the safe side, try using the kernel without resetting the profiles. It *might* not cause any issues for you.
Just installed on Shostock3. So far everything works (including BLN!) except screen shot. Home+Power does not take a screen shot.
Will monitor for battery life...
jhermit said:
Just installed on Shostock3. So far everything works (including BLN!) except screen shot. Home+Power does not take a screen shot.
Will monitor for battery life...
Click to expand...
Click to collapse
Battery life has been great for the folks who have been testing this kernel for the past 4 to 6 weeks.
Remember that you may need to tweak some settings in Stweaks to get it working in a way that is good for you & your phone.
As for screenshots, try using power + vol down .
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
Thanks man! Will install right away
Sent from my i777 using xda premium
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
Just flashed with Slimbean RC1, so far so good.
Sent from my SGH-I777 using Tapatalk 2
AJ Newkirk said:
I am unsure of how a sim-lick can occur due to this.
To be on the safe side, try using the kernel without resetting the profiles. It *might* not cause any issues for you.
Click to expand...
Click to collapse
I ask myself the same question!!!
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
jhermit said:
Just installed on Shostock3. So far everything works (including BLN!) except screen shot. Home+Power does not take a screen shot.
Will monitor for battery life...
Click to expand...
Click to collapse
Why not just use the screenshot option in the power menu.
Sent from my SGH-I777 using Tapatalk 2
bswann said:
Why not just use the screenshot option in the power menu.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Or that :laugh:
Thanks! Will try this out.
Re: [KERNEL] Siyah-i777 v7.0 [JB] [4.2.1]
122ninjas said:
Yessssssssss I love you aj!!! Slight type on the features where it says it supports jb Mali on the second Mali it says mail
Sent from my GS4 running CM11 Kandy Kane
Click to expand...
Click to collapse
Slight typo in the word typo...
bswann said:
Why not just use the screenshot option in the power menu.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Because there is no screenshot option in the power menu...
Volume-+Power does not work.
AJ, YOU ARE THE MAN! I wanted to try JellyBam, but didn't want to give up Siyah. I was going to get set up to compile it for myself this morning....and just happened to notice that you had done it.....with STYLE too. Props!
jhermit said:
Because there is no screenshot option in the power menu...
Volume-+Power does not work.
Click to expand...
Click to collapse
It works fine here. Not sure why power + vol down wouldn't work for you.
great news!!!! now my i777 + hellybean will be perfect.!!!.
thanks!!!
thanks to
@sleekmason for his tutorial
@franciscofranco for his sources and hotplug algorithm
@oubeichen for msm_kcal_ctrl port
Features:
-franco hotplug algorithm
-custom thermal throtteling
-cpu: interactive
-uv: table exposed
-faux123 gamma control
-various fixes and optimizations
changelog:
v28: 17.08.2015
-updated to newest changes
-removed synapse (flash it yourself)
-governor is conservative now
-reverted some changes to hotplug
-scheduler: noop
-updated toolchain
-livebump instead of loki
-official CM only
how to change hotplug values
the values are located in
Code:
/sys/class/misc/mako_hotplug_control/
there you have
cpufreq_unplug_limit
Code:
if frequency is higher than this cores wont be offlined for a period
max_load_counter
Code:
maximal samples counted to offline cores (higher values = longer time to offline core)
high_load_counter
Code:
- info missing yet -
load_threshold
Code:
threshold to online a core
min_time_cpu_online
Code:
minimum time a core stays online
timer
Code:
samples per second (1 = 10 samples; higher values = less samples)
brightness
If you experience brightness issues it is because you are using base 4.2.2
to avoid issues flash 4.4.2 base
you can find a flashable zip here:
http://forum.xda-developers.com/showthread.php?t=2762526
reboot or crash?
send me last_kmsg
BACKUP BOOT AND SYSTEM FIRST!
Download !!!OFFICIAL CM ONLY!!!: https://www.androidfilehost.com/?fid=24052804347795577
XDA:DevDB Information
mani.Kernel, Kernel for the LG G Pad 8.3
Contributors
ckret
Source Code: https://github.com/drbeat/kernel_lge_v500
Kernel Special Features: franco hotplug, UV table, gamma adjustment, custom thermal throtteling
Version Information
Status: Stable
Created 2015-01-23
Last Updated 2015-08-17
Is this for AOSP?
Inviato dal mio LG-V500 utilizzando Tapatalk
Rapepini said:
Is this for AOSP?
Inviato dal mio LG-V500 utilizzando Tapatalk
Click to expand...
Click to collapse
yes its for aosp
Cool, a new kernel ! Small question before I make the jump : what do you mean, generic touchboost not working ? Is this an issue for everyday use ?
Generic touchboost is a generic driver for boosting up the CPU in touch
Franco has this in his kernels but i couldnt make it work
So i implementend the touchboost in the existing lge touch driver
Shouldnt be an issue for usage since i am using this kernel myself as daily driver
Working great so far. Using on vanir ROM. Thanks!
How far have u overclocked it. And how does it perform
zombieryder said:
How far have u overclocked it. And how does it perform
Click to expand...
Click to collapse
Didnt overclock it
Never said i did
They pad has a quadcore with 4x1.7 GHz
No need for oc
I tried running this on the following ROM:
[ROM][v500][KK][4.4.4][LINARO/SABERMOD] AOKP [WEEKLY BUILDS][20140705]
The first issue I ran into was that the screen brightness was locked at the highest level. I have read that you need to have the 4.4.2 base when running these 4.4.4 ROMs in order for screen brightness to work. It looked to me like installing this kernel upgraded to the 4.4.4 base, which would explain why that became broken.
Is it therefore safe to assume that this kernel is only for ROMs running the 4.4.4 base and not the 4.4.2 base?
Thanks
Well, no problem with autobrightness for me, and I have switched to 4.2.2 base to avoid the dim screen at startup. Been running it for the biggest part of the day, and found no real issue for now. Good work.
As for what doesn't seem to work, I was thrilled to see the gamma option in trickster mod, and thought I would be able to calibrate my screen correcly for the first time. Sadly, it seems the changes are registered (Trickster mod says they are saved allright), but there is no evolution whatsoever : the screen stays the same (and believe me, I have tried the most extreme settings to be sure I would notice the subtlest of changes).
i dont know about the bases
i think i have the 4.2.2 base but i am not sure
and currently gamma is not working. i am looking into that, but it seems quite hard
ckret said:
i dont know about the bases
i think i have the 4.2.2 base but i am not sure
and currently gamma is not working. i am looking into that, but it seems quite hard
Click to expand...
Click to collapse
Well at least, the option shows up in trickster mod, so I guess you're not so far from it. Anyway, your kernel seems to run very well. Thanks!
For sure opened the brightness...in fact ALL the way & no way to lower more.
Also, I lost sound.(Not for sure now about that one) All else fine, but NO gama control, and no 'on demand' - only 'interactive & 2 others'...
So giving it up for now, but thank you for the compiling & I'm sure you'll get it right next time!
Cal-123 said:
For sure opened the brightness...in fact ALL the way & no way to lower more.
Also, I lost sound.(Not for sure now about that one) All else fine, but NO gama control, and no 'on demand' - only 'interactive & 2 others'...
So giving it up for now, but thank you for the compiling & I'm sure you'll get it right next time!
Click to expand...
Click to collapse
i am aware of the brightness problem
gamma control not yet given, since i cant find the gamma address
interactive is optimized so its selected as default in this kernel
v3 feels alot smoother
dont know if there are any issues with cabc enabled
you gotta try out and report me
Running v3 on Mahdi. Smooth so far. Will report back in a few days.
Sent from my LG-V500 using Tapatalk
I was testing v3 and brightness value is fixed and wont change for me. I'm using CM11 M8.
wind0zer said:
I was testing v3 and brightness is fixed and wont change for me. I'm using CM11 M8.
Click to expand...
Click to collapse
The brightness seems to be *the* big issue with all the kernel builds. But when mentioned to other kernel builders or porters, they don't understand the 'why' of the need for more brightness. I feel the same way...I would like to be running at 40% brightness and see everything OK, but just so I could possibly save some battery 'time'. But frankly I really don't know why - 5 or more hours is long enough in one day on a tablet for me. Seems to be enough for Oubeichen, who I think is a fine kernel analyzer or porter.
What I would like to see is what Oubeichen put into this kernel found here and which I'm running but is v3.4.xxx (can't remember! and am on a computer now):
http://forum.xda-developers.com/showpost.php?p=54153699&postcount=196
Even though this is early version kernel, I'm running it with no problems - it has about 7 or 8 Processor settings such as Progressive, Conservative...etc. and several I/O's such as Noop and all the others that are not shown on the later 3.4.0 kernels. Nice settings to have to play around with IMO.
As aicjofs said brightness is a BASE issue
If you run the kernel on the 4.4.2 base you will have no Problem
I can compile it for your 4.2.2 base but i dont just geht why you dont upgrade
Having 1000000 options isnt as good as having optimized options
If you want to know what the issue is you have to look jnto the AIC thread. He stated the difference for autobrightness on the bases
i have added a sys interface so ppl with 4.2.2 base can also use this kernel
just read first post
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
*** 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