ALL THANKS AND CREDITS GO TO THE ONE AND ONLY KTOONSEZ FOR THIS AWESOME KERNEL AND GIVING ME THE OPPORTUNITY TO PROVIDE THESE BUILDS.
Welcome!
I am in no way affiliated with Ktoonsez or his work. I’m just a simple member of the XDA community who happens to be a huge supporter of this kernel and its creator. This is just my way of giving back. I am aware of some of the issues that may occur on specific kernel builds for some users as well as the difficulties faced when fine tuning the kernel and this is my response to that:
This is by no means intended to replace any of the original KT-SGS5 kernel threads. The purpose of this thread is simply to work in conjunction with them by providing a variety of builds for which users can experiment with and see which versions perform as intended on each of their respective device models. As on previous Samsung devices I am also bringing back the Ktweaker Shop filled with tons of pre-configured settings compiled by myself and others in attempt to further assist S5 users with improving their overall experiences on this device or to simply use as a baseline to work upon tweaking further. So I’ve gathered just about all of the current and previous kernel builds I had hidden within my pc as well as all the various Ktweaker settings and am sharing them with the public. I hope this makes a difference for all you guys. ENJOY!! :good:
POST #2: Reserved for UNIFIED KLTE(G900) BUILDS
POST #3: Reserved for the KTWEAKER SHOP
POST #4: Reserved for TEST PROFILES
If at any given time you aren't already on the kernel and Ktoonsez hasn't updated his links, there'll be no need to flash previous builds when you want to receive OTA's as ALL posts will be updated regularly upon future releases. So please be sure to refer back here for all builds from this point moving forward!
I will NOT be held liable for anything that may occur to your device nor will Ktoonsez. So please...
***FLASH AT YOUR OWN RISK***
If you encounter any suspicious issues when updating the kernel, follow my recommended procedure for the best possible results:
1) Backup current Ktweaker settings
2) Open any root browser (make sure it's mounted as r/w) then navigate to /system/app/ and delete the Ktweaker and KTmoniter apk's
3) Navigate to your sdcard and delete the Ktweaker folder OR rename it by adding a ".bak" extension without the quotes.
4) {Optional} Clear all Superuser logs
5) Reboot Recovery
6) Flash kernel
7) Reboot
8) Copy any saved profiles back into /sdcard/Ktweaker/Profiles/
9) Restore Ktweaker settings
10) Profit?
NOTE: If at any point Ktoonsez no longer wants this thread open it will be closed without question.
Please visit original kernel thread for change logs, extras, etc...
If you like and support his work, donate with this link:
http://forum.xda-developers.com/donatetome.php?u=4325945
**********KLTE**********
KT-SGS5 kernel features
•Must have a S5 model G900T or G900P or G900V (Dev Edition ONLY!!!) or G900F or G900M or G900W8
•Must have a Touchwiz Rooted ROM
•Must have CWM/TWRP based recovery installed
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•KTweaker app for kernel control
•KTweaker Widgets
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•exFAT for Touchwiz and AOSP
•F2FS compatible with AOSP 4.4
Click to expand...
Click to collapse
Downloads
Touchwiz Lollipop 5.0 VERSIONS:
https://copy.com/nnRWaceoApyWveLV
AOSP Lollipop 5.0 VERSIONS:
https://copy.com/sPBzkxDrTUsdh08m
AOSP Lollipop 5.1 VERSIONS:
https://copy.com/kA6cUoKDCZWNSrG7
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/3jfvgKqLUKUr
AOSP KitKat 4.4 VERSIONS:
https://copy.com/IVmYJgQZWmD6
{
"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"
}
Welcome to the Ktweaker Shop!
Here you will find all of the pre-configured settings provided by myself and some of our fellow users. As a proud member of Team Kernelizers, I am offering a variety of profiles specifically for S5 users with their personal needs in mind as it's pretty clear no everyone favors the same governor, scheduler, etc.. Any suggestions are always welcome. All future settings will be added here for sharing and discussing our settings as well as gaining approval on a profile to be added into the built-in Shop in Ktweaker. Keep in mind that results will always vary per device regardless on the settings being used.
All profiles have been grouped into 3 sub-categories; "Conservative", "Balanced", and "Performance", which are used to classify each profile based on their overall performance and what they are expected to deliver to your device. The 4th sub-group is where you can find some of our best "Projects" in which offers 2 or more profiles for each. Make your selections based on your usage and apply what works best for you and your phone. We're here to help eachother out and with more options comes better experiences for everyone running this kernel. Big thanks to ALL who have contributed!
So shop around.. pick and choose.. load and go!!
Installation
Download links will include the specified profile(s) as well as an "Adjustments" and "About" file. The "Adjustments" file is just a simplified view of all the changes made to a profile compared to stock settings.
1. Download the file(s) to your phone.
2. Copy ONLY the XML(s) (DO NOT copy the "Adjustments" or "About" file) to "/sdcard/KTweaker/Profiles" using a file Manager of your choice.
3. Open the Ktweaker app and click on the "Profiles" setting at the top of the slider drawer OR scroll to the bottom and select "Profiles & Scripts" then click "Restore Profile from sdcard".
4. The file you just copied should be listed there. Select the one you want to apply and confirm.
5. Make sure the "Set options on boot" setting at the top of the slider drawer shows a little green boot icon below it, indicating the settings will be applied upon reboot.
6. Profit!
Conservative
Asking Alexandria
This is a battery driven profile in which focuses on saving as much juice as possible while also maintaining stability and providing an extremely snappy feel to your phone. It is quite possibly one of the smoothest and snappiest battery saving profiles available.
Why Asking Alexandria?
It's named after yet another one of my top favorite metalcore bands and I chose this because Alexander The Great basically ruled the world at one point and "Alexandria" is the female equivalent to that name, which has become known to mean the "one who comes to save warriors".
"Asking" was an addition to the title name as an indication in the sense that we are all asking Alexandria what she can really do to our phone.
https://copy.com/X8tAZauB2Nw7DDmF
Bless The Child
Based on Ktoonservateq and aimed towards battery. This is specifically for all the battery hungry users out there wanting to conserve as much power as possible. So don't expect the BEST but rather decent performance out of this one.
https://copy.com/DnyKoDtbGzFeBhKj
Dead By April v3 (updated: 5~7~15}
This profile attempts to bring some of the best battery life possible to your device. It is similar to Bless The Child but takes things a step further . It now focuses more on snappiness but still maintains it's well known battery conservation. It manages to maintain a smooth ui for your average daily use.
https://copy.com/YbVh8fJui0Wg
Balanced
Balanced Bull v4 (updated: 5~7~15}
These settings are very special to me as they were my very first, dating back to the Galaxy S3, and is a profile designed for my own personal usage pattern. It has become notable for it's fairly smooth interface and amazing battery life. If this stacks up to your standards then I encourage you to use it!
https://copy.com/XaUC96AHpYd0
ECLIPSE v3 (updated: 5~7~15}
This is a performance oriented option where great battery life is also expected to intervene. This not only will bring an incredibly stable, smooth, and snappy feel to your device but will also benefit towards longer lasting battery so you can love and enjoy your phone the way you were meant to.
https://copy.com/YolJstsJPAFb
Ktoonsified v4 (updated: 3~25~15}
This profile was put together by none other than the BOSS himself, @ktoonsez! This is a performance oriented option in which also offers a great deal of battery life. Haven't tried these settings yet? then what are you waiting for!! Load em up and be prepared for one of the smoothest and snappiest experiences ever!
https://copy.com/VPykcXYipZea
Ktoonsified {MOD}
This profile is intended to work as an alternative to the original Ktoonsified profile. It was modified to slightly boost performance and is specifically for the users experiencing issues on Ktoonsified such as screen wake and incoming call delays, media stutters, or 3D frame drops. Use this profile to repair most if not all your issues and expect an even faster and smoother UI.
NOTE: The adjustments text file will show you the changes I've made from the original Ktoonsified profile.
https://copy.com/JgW2M2wjkmat
SmoothManic v2 (updated: 7~16~14}
This profile was put together by none other than the BOSS himself, @ktoonsez!
The idea with this is to get the CPU really high on 2 cores when screen is touched and then bring them both back down really quick so UI is super smooth but don't kill the battery by hanging out at that high Mhz step.
Click to expand...
Click to collapse
https://copy.com/G7m7dWYh9u6j
SmoothManic {MOD}
Smoothmanic v2 was slightly modified in order to bring the profile up to speed with the most recent kernel changes. It should provide a slight boost in performance but continues to follow a similar scaling mechanism as the original.
NOTE: The adjustments file will show you the changes I've made from the original profile.
https://copy.com/1hHIF7rtw1Rcqwz4
Undisputed 3 (updated: 5~7~15}
This is a universal performance setup in which combines the essential elements of other profiles by providing equal battery life, speed, performance, and stability to bring the ultimate experience to your device.
https://copy.com/nuMTnp4wkQpW
Performance
Feed The Machine v3 (updated: 5~7~15}
The exact opposite of Bless the Child. This is a performance oriented option for all hardcore users. If battery isn't a priority for you then this is a great option.
https://copy.com/FFvQ3DRRUbu1iedM
From Ashes To New
This is a straight performance profile. It's similar to Feed The Machine and Rebirthing in the sense that it syncs the cores to the boosted frequency on touch and almost instantaneously jumps right back down to 300MHz. The difference between the profiles is that this one makes better use of all the cores. However, due to the rapid scale down I think most people will find battery life to be surprisingly good for this type of profile
https://copy.com/WQRuc72k8Faarx4j
KTGaming v2
This profile was put together by none other than the BOSS himself, @ktoonsez! This is a super performance oriented option which allows me to play any game with ZERO LAG!!!!!!!
Click to expand...
Click to collapse
https://copy.com/q7URWZu7qnzV
SmoothGaming
This profile is based on the SmoothManiac MOD but with performance enhancenents to provide a much smoother gaming experience. These enhancements include a much higher sampling interval as well as offline blocks to allow frequencies to scale and hotplug at a more reasonable pace.
https://copy.com/qeqe7fw9o0Xs0gxw
Projects
Comatose
This project was inspired by the album of the same name by my #1 favorite rock band of all time, Skillet. It consists of 3 profiles of which are also named after 3 of my favorite tracks from this album (included in the "Extras" folder) and all focus on one key element; VARIETY.
As the name suggests, "Comatose" is geared towards battery conservation. It focuses on keeping CPU low for a prolonged period but utilizes 3 of the 4 cores on touch and the 4th on demand for fluidity. Sample rates have been decreased heavily as to increase polling and allow the other cores to quickly spike towards higher frequencies for a given task then immediately drop back down as if the component had been knocked unconscious.
The second profile is "Rebirthing". This profile will counteract the affects of Comatose by heavily boosting performance as a means to bring life and energy back into this profile that remains unconscious. Rebirthing is intended for those seeking a performance-based version of Comatose but who knows... For such a power hungry profile you may just be surprised by the great battery life it also delivers.
Some of you may not favor the heavy battery conservation that "Comatose" offers or the overall power consumption of "Rebirthing" and much prefer a mashup of elements delivered between the 2 and that is the purpose of "Whispers In the Dark". This profile is directed towards finding the right balance between these 2 profiles while still acting as a it's own profile. It utilizes most of the performance aspects from "Rebirthing" Like "Comatose" it uses a fairly high up_threshold for that extra boost in battery performance. The profile also idles at the same minimum cpu as "Comatose" but ALL profiles run at stock 2457Mhz.
All profiles maintain the same concept of rapid cpu polling. So yes, cpu will be working consistently but my theory here is that more polling will allow the kernel to rapidly check CPU usage, thus allowing CPU to change more frequently according to the load, which in turn will prevent persistent pegging of even higher frequencies and instead consume various amounts of power in various scenarios depending on your usage, consuming even less when a specific task has completed and immediately dropping the load.
This also applies to screen off states but that goes back to what was explained in this post regarding high vs low sampling rates and how they can greatly increase idle times depending on your screen off max.
https://copy.com/wzq0Edm2xueOxZJd
If you'd like to contribute to the Ktweaker Shop all you need to do is post the profile you'd like to share and include a brief description of it's purpose. It will then be tested thoroughly by the community and based on feedback will be submitted here in the Shop for approval and sent out to the dev so he can add the profile to the Shop in Ktweaker!
Useful Links
Information about profiles can be found HERE
Interested in learning how to fine tune this kernel but not sure of where to start?
Please refer to this Ktweaker User Guide (thanks to @Perseus71) and you'll be tweaking in no time!
HERE is a great app by @elesbb that will allow the end user to set individual governor options for Ktoonservativeq when turning on the screen, charging, or playing media.
Click HERE for a widget that will allow you to quickly change your charging mA current (thanks to @elesbb).
Ktoonservativeq tunables explained HERE
Reserved
Mine..
Just in case
Thanks for this great work [emoji106][emoji106]
Sent from my SM-G900T using Tapatalk
Wow tnx for you
work
Sent from my SM-G900T using XDA Premium 4 mobile app
Question,
Why do you state to wipe cache and dalvic 'after' flashing and kt said 'before' ?
I have always done it before flashing a new kernel so the new settings would be applied, I thought.
Thank you for your work and this thread @LuigiBull23
T-Mobile Galaxy S5
EDIT
I just read his OP on his thread and it states the same as yours about wiping AFTER install.
Is there an explanation as far as doing it before vs after?
---------- Post added at 06:37 AM ---------- Previous post was at 06:31 AM ----------
Post #2, the shop.
Typo? These are for the s5 right? Lol
[emoji12]
T-Mobile Galaxy S5
em0ney14 said:
Question,
Why do you state to wipe cache and dalvic 'after' flashing and kt said 'before' ?
I have always done it before flashing a new kernel so the new settings would be applied, I thought.
Thank you for your work and this thread @LuigiBull23
T-Mobile Galaxy S5
EDIT
I just read his OP on his thread and it states the same as yours about wiping AFTER install.
Is there an explanation as far as doing it before vs after?
---------- Post added at 06:37 AM ---------- Previous post was at 06:31 AM ----------
Post #2, the shop.
Typo? These are for the s5 right? Lol
[emoji12]
T-Mobile Galaxy S5
Click to expand...
Click to collapse
Wiping caches before flashing should have the same result as wiping after. It's just what KT recommends. I also have never had issues wiping beforehand.
As far as the typo goes, I copied and pasted that post from my S4 Thread and haven't completed my edits yet lol.
I was just busting your ballz about the s4 > s5 typo. I figured as much. Hehe.
Anyways, thanks for the explanation on wiping cache / dalvic.
I haven't had any issue in doing it before or after either, just wanted it to be clear.
Thank you!
T-Mobile Galaxy S5
Glad to have all the S4 KTweaker Shop folks here on the S5. I feel at home again. ;]
LuigiBull23 said:
ALL THANKS AND CREDITS GO TO THE ONE AND ONLY KTOONSEZ FOR THIS AWESOME KERNEL AND GIVING ME THE OPPORTUNITY TO PROVIDE THESE BUILDS.
Welcome!
I am in no way affiliated with Ktoonsez or his work. I’m just a simple member of the XDA community who happens to be a huge supporter of this kernel and its creator. This is just my way of giving back. I am aware of some of the issues that may occur on specific kernel builds for some users as well as the difficulties faced when fine tuning the kernel and this is my response to that:
This is by no means intended to replace any of the original KT-SGS5 kernel threads. The purpose of this thread is simply to work in conjunction with them by providing a variety of builds for which users can experiment with and see which versions perform as intended on each of their respective device models. As on previous Samsung devices I am also bringing back the Ktweaker Shop filled with tons of pre-configured settings compiled by myself and others in attempt to further assist S5 users with improving their overall experiences on this device or to simply use as a baseline to work upon tweaking further. So I’ve gathered just about all of the current and previous kernel builds I had hidden within my pc as well as all the various Ktweaker settings and am sharing them with the public. I hope this makes a difference for all you guys. ENJOY!! :good:
POST #2: Reserved for UNIFIED KLTE BUILDS
POST #3: Reserved for the KTWEAKER SHOP
POST #4: Reserved for SCRIPTS & TEST PROFILES
No need for flashing previous builds to receive OTA's as all posts will be updated regularly upon future releases. So please be sure to refer back here for all builds from this point moving forward!
I will NOT be held liable for anything that may occur to your device nor will Ktoonsez. So please...
***FLASH AT YOUR OWN RISK***
If you are manually UPDATING the kernel, follow my recommended procedure for best possible results:
1) Backup current Ktweaker settings
2) Navigate to Settengs > Apps > Ktweaker
3) Clear cache and data then force stop
4) {Optional} Open any root browser, mount as r/w, then navigate to /system/app/ and delete Ktweaker apk
5) {Optional} Clear all Superuser logs
6) Reboot Recovery
7) Flash kernel
8) Wipe cache/dalvik
9) Reboot
10) Restore Ktweaker settings
11) Profit?
NOTE: If at any point Ktoonsez no longer wants this thread open it will be closed without question.
Please visit original kernel thread for change logs, extras, etc...
If you like and support his work, donate with this link:
http://forum.xda-developers.com/donatetome.php?u=4325945
Click to expand...
Click to collapse
em0ney14 said:
I was just busting your ballz about the s4 > s5 typo. I figured as much. Hehe.
Anyways, thanks for the explanation on wiping cache / dalvic.
I haven't had any issue in doing it before or after either, just wanted it to be clear.
Thank you!
T-Mobile Galaxy S5
Click to expand...
Click to collapse
dynospectrum said:
Glad to have all the S4 KTweaker Shop folks here on the S5. I feel at home again. ;]
Click to expand...
Click to collapse
:) .[URL
[/URL]p
Anyone using dead by april? Just wondering how much better battery life it gets you. I've been running it for a couple days and I'm seeing a bit worse battery than stock.
aooga said:
Anyone using dead by april? Just wondering how much better battery life it gets you. I've been running it for a couple days and I'm seeing a bit worse battery than stock.
Click to expand...
Click to collapse
Depends on how you use it. The profile is intended for conserving battery by undervolting the CPU and throttling it. If you have cpu intense apps that require phone awake all the time, the results won't be great. In that case its not a profile for your usage pattern.
Perseus71 said:
Depends on how you use it. The profile is intended for conserving battery by undervolting the CPU and throttling it. If you have cpu intense apps that require phone awake all the time, the results won't be great. In that case its not a profile for your usage pattern.
Click to expand...
Click to collapse
Thanks a lot.
Can I use mobile Odin for this. Never used mobile Odin before
Sent from my SM-T230NU using Tapatalk
slicknsxy said:
Can I use mobile Odin for this. Never used mobile Odin before
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
It's flashable in recovery.
aooga said:
It's flashable in recovery.
Click to expand...
Click to collapse
Any way to go back to factory. Without restoring?
Sent from my SM-T230NU using Tapatalk
slicknsxy said:
Any way to go back to factory. Without restoring?
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
Back up just the boot partition in twrp. Then restore it.
I think that's what you mean. Correct me I'm wrong.
Sent from my SM-G900T using Tapatalk
Related
Although some parts can be considered as original, all are based on inspirations, examples and other people's code.
I have no claim to be original. I am only trying to make my (and probably other's) SGS2 experience better and fun.
I do this for fun. so, if you just want to argue with me please don't. use the energy coming from your youth in something useful.
SiyahKernel v2.6.14
FEATURES
Can be flashed on Samsung ROMs and AOSP Based ROMS. Currently all Samsung 2.3.4, 2.3.5, 2.3.6, 2.3.7 based ROMS, CM7 (CM9 or any other ICS based ROMs are not supported) and MIUI ROMS are supported.
Based on linux kernel 2.6.35.14 + drivers from Samsung sources
Auto-Rooting
CWM touch Recovery with gesture support
Custom boot animation support
Supports SetCPU (OC upto 1600MHz, UC downto 100MHz)
User customizable frequency steps. You can edit "freq_table" and use 25MHz as the lowest step and 1696MHz as the highest. You have 8 steps (it is fixed) but the frequencies can be set.
Supports undervolting (UV between 800 mV and 1500 mV)
Supports voltage control via SetCPU (thanks to netarchy, ninpo, hacre)
Stock voltages as default
smartassV2, lulzactiveV2 governors. and lots of other governors which are available as modules
Default governor is lulzactive (200-1200MHz)
Tweaked ondemand and conservative governors
no compiler optimization. it is just a myth.
Touchscreen fix (thanks to vitalij)
Increased touchscreen sensitivity
GPU clock (thanks to netarchy), voltage and scaling thresholds control interface.
I/O, scheduler, hotplug and vm tweaks
automatic battery calibration. (removed. thanks to Entropy512. we do not need battery calibration for SGS2)
Available I/O schedulers: noop, deadline, CFQ, BFQV3r2(default), V(R), SIO
Available CPU governors: see this thread for the list of available governors and modules (thanks to droidphile)
/system/etc/init.d startup scripts support
Automatic backup of efs partition. You will have the files in your sdcard as well as /data/.siyah directory. copy them to a safe location in case you may need them later.
BLN (thanks to creams), liblights is autoinstalled if the existing one doesn't support BLN
supports advanced touch tune driver. thanks to vitalij Link. the control app from Web, from Mobile. Thanks to tegrak for the driver patch file download
2nd core application support (thanks to tegrak)
Automounting of NTFS volumes for USB sticks (ntfs on external card is not supported). although your rom says "clear storage", just check /mnt/usb folder. ntfs drives will be automatically mounted in read-only mode.
LZOP compression for the kernel to have very fast decompression. We have a VERY BIG kernel image because we have ntfs-3g, CWMManager and lots of other things both in initramfs and payload.
Integrated new&faster sha-1, crc32 slice-by-8, crc32c, jhash and rwsem algorithms
SCHED_MC enabled to have less power consumption.
Lower brightness levels for low-light conditions to save battery.
Brightness behaviour modification via setting min_bl, min_gamma and max_gamma values. you can control the lowest and hightest levels used in autobrightness.
Native BLN support for CM7 based roms.
Three GPU stepping (160-267-300) instead of two
optimized and configurable hotplug thresholds and rates.
Thunderbolt! script integrated (thanks to pikachu01)
Voodoo louder app support (thanks to supercurio)
Current Widget support while charging the device.
ExTweaks (uci.sh) support. (Thanks to xan and AndreiLux) ( https://market.android.com/details?id=com.darekxan.extweaks.app )
CIFS, SLUB, FUSE, NTFS, cgroup_timer_slack,... and lots of other mambojambo that I forgot...
Download link: http://www.gokhanmoral.com/
FLASHING GUIDE
TO FLASH TAR:
If you already have root, use DarkyOTA app from the market ( https://market.android.com/details?id=com.ficeto.darkyromota ) .
If not, use ODIN.
TO FLASH ZIP:
Use CWM Recovery and install zip file. Wiping cache&dalvik cache is recommended for those who use BLN.
if you lose root after flashing the kernel (unlikely), flash http://goo-inside.me/superuser/su-2.3.6.3-efgh-signed.zip in CWM.
Some Example Init.d Scripts
Example CWM-flashable /system/etc/init.d/99gpuv script (thanks to AndreiLux)
Example GPU/CPU undervolting and underclocking scripts by kwerdenker
Improved version of CPU undervolting script by kwerdenker
Another couple of nice init.d scripts created by fenomeno83
flashable lionheart cpu governor and setting default i/o scheduler to deadline (remove /system/etc/init.d/01lionheart to uninstall. thanks to knzo for the tweaked conservative governor settings)
releases can be found here: http://www.gokhanmoral.com/
source code repository: http://bitbucket.org/gokhanmoral/siyahkernel
CHANGELOG
see http://www.gokhanmoral.com/ for the changelog.
TODO
more and more optimizations for less battery drain
ICS edition when samsung releases new kernel sources
stable wifi driver which doesn't cause a lot of wakelocks with proper offloading
BLN notifications without wakelocks
OTA application (just to prevent users downloading wrong kernel for their device. other than that, it will be useless for a kernel)
THANKS:
Samsung, supercurio, hardcore, Hacre, RAvenGEr, tegrak, cattleprod, codeworkx, hellcat, creams, vitalij, arighi and others I might have forgotten...
{
"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"
}
Who Should NOT Use This Kernel?
If you are going to use very low voltage settings and complain about having lockups, you SHOULD NEVER use this kernel... just run away! This kernel is just as stable as the stock kernel if you do not modify any settings. Do not blame the kernel if you change the voltage or clock settings. If you do so I will blame your stupidity. I will not remove any feature just because some dumb users select wrong settings. If you are a rookie with an uncontrollable instinct of modifying advanced settings please use speedmod or stock kernel.
This kernel generally contain some experimental code and some of them may be even undocumented. I have different release strategy. I always use the latest version and if I notice any problem I try to fix it. However, I do not use all the features of the phone. So, if you notice any problem please report it. bug reports are welcomed, whining is not.
If you judge a kernel by quadrant score, please, I beg you, don't use this kernel. I don't have enough time nor motivation to answer your questions... Some people got 8000+ quadrant (search the thread) and there is no way you can beat them anyway.. so, go away...
If you are one of those who judges a kernel while sleeping ("oh my god!! lost %1 during sleep"-guy) please use another kernel, sleep and never wake up. it will maximize your battery and minimize the tension in the thread.
If you still believe in battery calibration, discuss it in some thread else. we respect all religions but missionary acts are not welcomed in this thread.
99.9% of the code belong to others. I have some modifications and/or additions to the kernel as C code or scripts but they are so little compared to the original code base. If you think you are better developer than I am, don't waste your time (and mine) as I accept it beforehand so please just go away.
FAQ
Q: Does this kernel support Samsung's ICS leak, CM9 or any ICS edition?
A: No, it does not.
Q: Does this kernel support latest Samsung i9100 ROM?
A: Yes, it does. Unless otherwise stated, you can use this kernel on latest Samsung ROMs (official and leaks). it is tested on 2.3.4, 2.3.5, 2.3.6.
Q: Can I use this kernel on I9100G?
A: No, you cannot. Only european i9100 models are supported. Also, I compile ntt-docomo version for each release but beta versions do not support gps and digital tv on ntt-docomo devices.
Q: Does this kernel support CM7 or any other AOSP based roms?
A: Yes, but it only support cm7 or miui based roms for now. If you are using another aosp based Rom tell me and I will support it.
Q: Can I use app protectors with this kernel?
A: Yes, you can. Android logger is enabled by default.
Q: Some custom lockscreens or protectors do not work with this kernel. Can you fix it?
A: see the question above.
Q: What is smartassV2 governor?
A: It is a governor to control CPU frequency. This governor has a built-in "profile" similar to SetCPU but the profile has no upper frequency limit. It tends to stay on lower frequencies when the screen is off and scale up very slowly, so screen off will use lower clock rate thus conserve more battery, but it also has a fast wake up feature so that user interaction will not see the lag when switching from Sleep to Wake state.... (So SetCPU Profiles are sorta redundant when using this governor, you can still use SetCPU to OC to higher than default Clock frequency).
Q: What is the best UV settings?
A: There is nothing as best UV settings. You have to find the best settings for your device for yourself. Start by decreasing 25mV on each freq and decrease it every day until your device becomes unstable.
Q: What can I do to have the best battery life ever?
A: put your phone into airplane mode. if you don't like to do it read the guide below.
Q: Which roms are supported?
A: All android 2.3.4 and 2.3.5 roms are supported. Try the latest version. if you have any problems leave a post to this forum and ask for help.
Q: I get random reboots or freezes. What should I do?
A: Before reporting any problems you have to make sure that you are using stock voltage values. Some phones cannot handle undervolting. Secondly, you have to give details. When did it happen, which rom are you using, can you reproduce it, do you have any custom init scripts which changes kernel parameters such as freq voltage or anything else?
Q: do I need to recalibrate the battery?
A: You don't need to calibrate battery for SGS2. Thanks to Entropy512 to pointing out that our device uses MAX17042 which is specifically designed not to require calibration.
Q: do I need to perform any wipe?
A: no. you don't have to wipe anything. however, try wiping cache and dalvik cache if you have any force closes or any other issues before reporting the issue.
Q: Is the battery life better/worse?
A: maybe... you'll never know if you don't try... People are reporting that they are having the best battery but it may not be the case for your device.
Q: where is the interface to change GPU clock and voltage?
A: There is no GUI (graphical user interface). the interface is used via device files. you have to use init.d scripts to adjust the values. there are some examples in the first post about how to use init.d scripts and gpu voltage/clock interface.
Q: Which governor is the best? Which I/O scheduler is the best?
A: You have to try them and select the one you like. There is a very good explanation about governors and i/o schedulers here: http://forum.xda-developers.com/showthread.php?t=1242323
Q: My phone doesn't go into deep sleep mode. Why?
A: try to clear cache and dalvik cache by using CWM recovery and make sure that your phone is not connected to a charger. it does not go into deep sleep when it is charging.
Q: Which version is the best?
A: supposedly, the latest version is the best. But if the latest version is beta there may be unstable code in it. testing the beta version and reporting bugs will help me. but it's your choice... try and see... maybe this kernel is not stable for your device at all, who knows... I will not answer any "what is the best?" questions and I kindly ask you not to ask that kind of questions since there is no answer to that.
Q: How does the automatic battery calibration work?
A: Automatic battery calibration feature is removed as it was useless for SGS2.
Q: What is an init.d script?
A:init.d scripts are the scripts which are executed during the boot time. actually, they are meant to initialize and deinitialize system daemons and manage some startup/shutdown tasks. but in android world they are just "autoexec.bat"s. so, it is a mix of rc.d and init.d directories in linux distros. everything in /system/etc/init.d are executed during the booting process. since it is not standard in every android device,some developers choose to execute files starting with "S" and some execute everything. in this kernel, everything in /system/etc/init.d is executed. you can create a script to change, lets say, voltages, schedulers, apply tweaks, run overclocking daemon or run anything else you can imagine.
Q: My phone doesn't go into deep sleep. What is wrong?
A: Make sure that you have cleared cache and dalvik-cache after you install the kernel. Also, reboot once more after the flashing. the phone doesn't go into deep sleep if it is connected to a charger or to a computer. There may be an application running in the background which is preventing deep sleep. In that case you can check which app causing the problem with "BetterBatteryStats" application (search in Google).
Q: I want more info about CPU governors.
A: There is a great post about cpu governors (thanks to droidphile): http://forum.xda-developers.com/showpost.php?p=19339524&postcount=10023
If you still want more info, try them by yourself.
Q: Can I use this kernel with I9100T?
A: Yes, you can. the only difference between I9100 and I9100T is that they have different SAR values.
quick and dirty guide to have less battery drain:
- use 2G-only if you don't need 3G
- monitor programs which cause wake-lock. use betterbatterystats and either uninstall or tweak them
- do not use task killers. see the previous item and find the malicious programs instead of repeatedly killing them.
- do not activate google latitude on maps.
- if you don't need pushmail, uncheck gmail sync and use k-9 mail to pull mail, lets say, every 1 hour or so.
- go to settings / location and security. disable "use wireless networks" and "use gps satellites". enable them when you need them, other than that keep them disabled.
- disabling auto-brightness and using a low brightness level helps. do you know that you can adjust the brightness by swiping your finger across the notification bar? try it...
- using juicedefender may help, but it may also cause more drain. test it yourself.
- if you need more speed than 2.5G (i.e. edge) disable HSDPA (*#301279#, select 2 then select 1). you will have 3G instead of H(SDPA) and I think it is fast enough
- disable fast dormancy. dial *#9900# and disable.
- disable auto sign in for google talk (search for talk in appdrawer and use settings to disable automatic sign in)
- disable samsung update and don't use samsung gadgets if you are not in love with them. (this part may be taken care of the rom developers)
- try several radios. I recommend you to try KE7, KG2 and KH3 and choose the one which suits you best. KG2 seems to be the best for me. however, in terms of battery life, there is not much difference between those three.
- be aware that more you use your phone more the battery drains don't complain like "my battery drains quite fast but I did not use my phone. I only played angry birds for hours without making a single call" or don't expect to have a decent battery life if you use your phone as a computer or download torrents using your phone.
i think i will wait 4 feedback because it's based on u2 source.
But good job anyway
cheers
Just flashed this on checkrom. Lost my haptic feedback and wifi.
Sent from my GT-I9100 using Tapatalk
sileshn said:
Just flashed this on checkrom. Lost my haptic feedback and wifi.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I've just noticed that I haven't uploaded the version that I am using. sorry for that. I will recompile and upload again.
gokhanmoral said:
I've just noticed that I haven't uploaded the version that I am using. sorry for that. I will recompile and upload again.
Click to expand...
Click to collapse
Take your time and post the sources as well, else this thread will get locked pretty quick.
Sent from my GT-I9100 using Tapatalk
Tebrikler dostum.. Great work..
sileshn said:
Take your time and post the sources as well, else this thread will get locked pretty quick.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
yes, I know that is why I have asked for patience in OP. If the moderators were a bit more patient maybe I would be using some other kernel and wouldn't bother to compile my own
I've uploaded the recompiled kernel. enjoy.
Salam!
Any benchmarks results sir?
Sent from my GT-I9100 using Tapatalk
sileshn said:
sileshn
Click to expand...
Click to collapse
Thank you sir
Sent from my GT-I9100 using Tapatalk
So~ Any battery life improvement using this kernel sileshn?
Desperate for battery saving stuff for my lovely S2~
03188lee said:
So~ Any battery life improvement using this kernel sileshn?
Desperate for battery saving stuff for my lovely S2~
Click to expand...
Click to collapse
you have to try.
smartassv2 governor with 200-1200mhz setting is very satisfying and the battery lasts at least as long as speedmod-v27 for me.
bfq scheduler maybe
..........will u add it in the next release?
CFQ scheduler really drain too much power.....
Sick Enough To Die said:
bfq scheduler maybe
..........will u add it in the next release?
CFQ scheduler really drain too much power.....
Click to expand...
Click to collapse
I have already added. testing now..
power drain change is not noticable though.
Did you get better battery life than REGEmod-U1?
gokhanmoral said:
you have to try.
smartassv2 governor with 200-1200mhz setting is very satisfying and the battery lasts at least as long as speedmod-v27 for me.
Click to expand...
Click to collapse
chonshon said:
Did you get better battery life than REGEmod-U1?
Click to expand...
Click to collapse
I haven't tested it, but theoretically smartassv2 governor that I am using in the kernel should give better battery life than ondemand with a little (not even noticable) sacrifice of performance. you don't need to use any setcpu profiles with smartass governors.
test it. it may or may not give better battery life for you.
I will. Thank you.
gokhanmoral said:
I haven't tested it, but theoretically smartassv2 governor that I am using in the kernel should give better battery life than ondemand with a little (not even noticable) sacrifice of performance. you don't need to use any setcpu profiles with smartass governors.
test it. it may or may not give better battery life for you.
Click to expand...
Click to collapse
great work
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
Thomas.Raines presents
The Lightning Zap! kernel for the Nexus 4 Mako
ATTN:
I thomas.raines, nor it's affiliates claim responsibility for anything you do to damage, destroy, brick, explode, or otherwise mess up your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features:
Improved performance
Improved battery life
Improved network speeds
Improved boot times
Smoother scrolling
Better responsiveness
Cleaner file systems
Governor tweaks for amazing speed and performance without sacrificing battery life
Improved Memory and Ram tweaks
Improved Internet speed
kexec hack for dual booting with MultiRom.ak
Overclocked cpu
sweep2wake/doubletab2wake (disabled by default. must be enabled via script by uncommenting lines 7 and 8 in /etc/init.d/05s2w then reboot)
Amazing kernel tweaks, build.prop mods, init.d scripts and more!
Governors:
POWERSAVE
USERSPACE
ONDEMAND
INTERACTIVE
BADASSS
INTELLIDEMAND
LIONHEART
ONDEMANDX
SMARTASS2
GALLIMAUFRY
LAZY
io-schedulers
NOOP
DEADLINE
CFQ
SIO
See 2nd post for download links and changelogs
Instructions:
Make a backup
Download .zip to PC
Transfer .zip to your sdcard
Or just download it straight to your phone
Reboot to recovery
Flash
Reboot
Wait 10 minutes
Enjoy the Lightning Zap!
See 2nd post for download links and changelog
**The first boots usually takes the longest especially after a fresh install. If you pull a logcat during the first boot, you may see a few errors with the vacuum script. This is normal, and will be "fixed" after the phone has built the databases for the apps.
Please allow 24 hours after install and 1 full charge cycle before reporting results. Always provide me with a logcat with any issues you may experience.
Source Code:
mako-lz kernel
vendor_lz-kernel (LZ vendor files for ROM compiling)
Special thanks to:
jrummy16 for Root Browser Lite
show-p1984 for bricked kernel (used for rebase)
Download Links and Changelogs
Nexus-4-Mako-LightningZap_p5.1.2.zip
cpufreq adjustments
led driver adjustments
Import RB tree adjustments from Motorolla
Input packet management adjustments
EOL
https://github.com/LightningZap/and...mmit/9ee0e0e3f9cf2733c554f0da69724c79f71cb4d9
Nexus-4-Mako-LightningZap_p5.1.1.zip
Fixed voltages and frequencies
uv_bin overhaul
Fixed inconstancies in installer
Guys and gals with slow binned cpus, MAKE SURE YOU SET THE MIN VOLTAGE TO 700. Or you will get random reboots like crazy. On a side note. I would strongly suggest wiping dalvik (art) and cache before flashing. If not, your device may shutdown immediately after it is done booting. Nothing to really worry about, just simply hold the power button for a few seconds till the google screen appears, and you should be good.
Nexus-4-Mako-LightningZap_p5.1.0.zip (dl link unavailable)
Major upstream update (166 commits)
TCP tweaks
Added GCC optimizations
Updated linaro toolchains
If you are having random reboot issues or you get stuck on the Google screen, try raising your min voltage to 700MHz. If that still doesn't work, let me know here. Please try to attach a dmesg log and make sure you tag me in the post so I don't miss it (@thomas.raines)
Enjoy!
Nexus-4-Mako-LightningZap_p5.0.2.zip
Added intelli_plug to handle CPU hot swapping
Disbabled MSM_HOTPLUG
Bumped to 5.0.2
Set min CPUFREQ to 9450
Changed Aroma installer defaults to my recommendations.**NOTE** If overclocking, I recommend using higher voltage min...
Included a LightningZap! tailored init.mako.rc that sets vibrator amp to 100, disables all that unneeded cpu governor junk and more...
Nexus-4-Mako-LightningZap_p5.0.1.zip
Bump to 5.0.1
added 5.0 emmc support
speedup /proc/net/unix
network speed tweak
exec_hardboot:updated with more current patch.
Avoids bogus error messages for the suspend aborts.
Avoid using global variable total_cpus
added sound control Thanks @faux123
Nexus-4-Mako-LightningZap_p5.0.zip
Update kernel to Lollipop 5.0
Added script to fix wonky sdcard issue. (5.0 was changing it from /sdcard/<your files> to /sdcard/0/<your files>. Script prevents that from happening and all is well)
All the same greatness of Lightning Zap! 4.4.X with no issues
Enjoy folks!
Nexus-LightningZap_p4.4-3.3.zip
Added remaining uv options to table
Backlight dimmer options
USB Fast Charge
CPUFREQ:rework of all tables. New implementation of freq's using PVS.
cpufreq: properly sync current scaling governor across all cores
Slight boost in L2 cache. Corrected number of cpufreqs
enable max screen off freq on/off support
added RESTRICT_ROOTFS_SLAVE
Added fsync on/off support:Enabled by default
Added f2fs and exfat support
Inspired by elementalx's flashing format using Aroma Installer, I have revamped cpufreq and uv tables, as well as added a few options.
You can now set your default options with the installer. Just follow the prompts as you go thru.
The flashing instructions are the same; however, at the end of the flashing process, you will have an option to save the log. I would recommend doing so. But only share it with me if you have an issue.
The installer is not without it's little glitch. Occasionally, your screen might flash and appear to be going from screen to screen in recovery after the installation process has finished. Nothing to worry about. Just let it settle down and then reboot. I only had this issue in philz_touch.
With the L2 cache boost, and the lightningzap booster, those pesky random reboots due to L2 cache failing to sync are a thing of the past.
One thing to note, when selecting your cpufreq, this will set you MAXIMUM. Meaning, even with an app, you will not be able to go over the default you set. Select carefully. I would recommend setting core 1 to the highest you desire and then setting the other 3 cores lower in the case you need more. And just use trickstermod to adjust as necessary. Oddly enough, even if you set the cores individually and cores 2-3 lower than core 1, your max will be whatever core 1 was set on. But if you adjust them reverse to what I said, then you will be limited to whatever default core 1 is. Hopefully that makes sense.
I have also linked all cores. This means that when you use Trickstermod app to set your cpufreq, it applies it to ALL cores. I have notice some apps, like kernel tweaker, do not do this as they are not written correctly for multi-core processors. Most of the defaults like voltages, fsync, and sweep2* can still be controlled with trickstermod even if you disable them during install.
TBH the only thing you cannot change, is your max cpufreq (meaning, if you choose 1512(stock) as your max during install, the only way to raise it is to re-install the kernel. However, you can still fine tune it).
Another note, max freq is set to 1620; however, if you can still set it higher, will just have to use trickster mod to fine tune it...
Previous Changelogs and links
Nexus4-LightningZap_p4.4-3.2.zip
Dropped mpdecision
Added msm_hotplug (With updates)Reconfigured voltage table. Boots @ 700000uV on 94500mHz
Possible UV/OV is now 600000uV min 1450000uV max (Be careful with this as too low/high for your device could cause instability. Test your settings BEFORE setting it to set at boot. If you go below the thresholds, your device will become EXTREMELY unstable, reboot, say you should have listened and then blow up in your face...lol. Not really, but it will go into a kernel panic and reboot)
And FYI, the voltages are reported in uV not mV. If you don't know, 1000uV = 1mV; therefore, the kernel boots @ 700000 is 700mV...
Nexus4-LightningZap_p4.4-3-1.zip
Added sec_dvfs_dual. All CPU's handle hotplugging better now
Added lulzactive cpu gov
add row and fiops schedulers
set fiops as default scheduler
Working on getting smartassv2 to compile...
added LCD Gamma Hack from faux kernel
Nexus4-LightningZap_p4.4-3.zip
2 stage update on this one.
Stage 1
Dropped bricked base and went back to kk4.4 (AOSP & CAF) base
Revamped OC/UV. Still compatible with Trickster Mod app
(Because I dropped the bricked base and went back to original base, you won't have full control on thermald and mpdecision for now. Working on adding it, please be patient)
Stage 2 With results of the latest poll in mind:
Dropped the following governors:
Conservative
Gallimaufry
Ondemandx
Userspace
Made Intellidemand/deadline as default
Nexu4-LightingZap_p4.4-2.zip
Complete revamp of base. Used bricked kernel as base (thanks to show-p1984)
Created new branch for revamp (bricked-lz) Keeping kk4.4 branch for now.
Per user requests:
Moved RootBrowser to /data **Must remove it from /system/app prior to flashing
Removed voltage control app. No longer compatible with vc.
Fully compatible with TricksterMod app
Vote on the next poll for your favorite governor & io-scheduler (If I can get it setup right)
Nexu4-LightingZap_p4.4-1.2.zip
Reverted back to Linux Android Kernel version 3.4.0 due to instability
Bumped to p4.4-1.2
Revamped mako_defconfig in order to enable loadable modules
changed build cifs & tun as modules
Left WiFi modules as hard-coded drivers to avoid WiFi issues on other Roms (Sorry about this one guys and gals)
Nexus4-LightningZap_p4.4_1.1.zip
Bumped to latest stable kernel version 3.84.4 (LightningZap version p_4.4-1.1)
Added sweep2wake and doubletap2wake from bricked-kernel Mako (special thanks to show-p1984)
sweep2wake and doubletap2wake is disabled by default. To enable one or both, refer to this post
Nexus4-LightningZap_p4.4_1.zip
Initial release
Just a note, some combinations of governors and io-schedulers don't mix well and you could experience instability like freezes and reboots. Before posting an issue, change your governor and or io-scheduler. This will help me narrow down any issues. And by all means, please let me know which combination you experienced an issue with, and what exactly occurred.
Note that certain ROMs like Omni and Ubuntu Touch that use a modified initramfs or some other kernel modification, may not work with this kernel. I am working on it now.
thomas.raines said:
Hold up... getting the link now
Click to expand...
Click to collapse
Great seeing you here! My brother uses your kernel on his E4GT and he likes it a lot.
I hope you do good work for the N4 as well. :good::good::good::good:
thomas.raines said:
Hold up... getting the link now
Click to expand...
Click to collapse
The OP says it's for Blaze 4G You might want to edit it to avoid confusion Thanks for your work, sir. I had use yours in my Blaze 4G.
Maybe a bit explanation of governors? Like for lionheart and galli
Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
Wow I saw you in the Blaze fourms. Great to see you developing on the N4!
Sent from my Nexus 4 using xda app-developers app
Saw you in the et4g forums
Sent from my Nexus 4 using Tapatalk
I'm glad people say this is real looked like a hoax to zap my n4!
So who has flashed this?
sent from a toilet...
phone always fc's for me on 3 different AOSP roms
Thanks for the kernel......Testing-----------------:good:
CallMeAldy said:
phone always fc's for me on 3 different AOSP roms
Click to expand...
Click to collapse
Can you be more specific?
CallMeAldy said:
phone always fc's for me on 3 different AOSP roms
Click to expand...
Click to collapse
by chance you tried it in the rom Purity? by that I have not had problems with.:good:
Hello.
Thank you for you hard work.
I was wondering which governor and scheduler do you suggest.
Edit : Can you possibly add swipe to wake?
Yadro said:
Hello.
Thank you for you hard work.
I was wondering which governor and scheduler do you suggest.
Edit : Can you possibly add swipe to wake?
Click to expand...
Click to collapse
The governor and scheduler really varies from person to person and dependent upon their usage of the device. I think Lionheart with noop is a great combination for power and battery saving from the light user all the way up to the medium user which is why I made it default. Some have suggested that intellidemand is very good as well, but sacrifices a bit of battery saving yet adds a slight bit of performance.
I have considered adding sweep 2 wake on some of my other kernels, but haven't truly decided on it yet. I think I'm going to give it a try tonight though.
Update available
Read changelog for details
To enable sweep2wake and doubletab2wake:
use an app like kcontrol
in and adb shell or in terminal on the phone type:
Code:
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/doubletap2wake
Or, I have made it even easier. In root browser, navigate to /system/etc/init.d. Open the script named 05s2w and remove the # from lines 7 and/or 8, then reboot. This will enable sweep2wake and/or doubletab2wake. You can enable both or just one of them.
thomas.raines said:
The governor and scheduler really varies from person to person and dependent upon their usage of the device. I think Lionheart with noop is a great combination for power and battery saving from the light user all the way up to the medium user which is why I made it default. Some have suggested that intellidemand is very good as well, but sacrifices a bit of battery saving yet adds a slight bit of performance.
I have considered adding sweep 2 wake on some of my other kernels, but haven't truly decided on it yet. I think I'm going to give it a try tonight though.
Click to expand...
Click to collapse
Thanks! So far i'm enjoying this kernel a lot! Working out for me on XenonHD.
---------- Post added at 08:49 AM ---------- Previous post was at 08:48 AM ----------
thomas.raines said:
Update available
Read changelog for details
To enable sweep2wake and doubletab2wake:
use an app like kcontrol
in and adb shell or in terminal on the phone type:
Code:
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/doubletap2wake
Or, I have made it even easier. In root browser, navigate to /system/etc/init.d. Open the script named 05s2w and remove the # from lines 7 and/or 8, then reboot. This will enable sweep2wake and/or doubletab2wake. You can enable both or just one of them.
Click to expand...
Click to collapse
okay i'll try that now too.
---------- Post added at 09:00 AM ---------- Previous post was at 08:49 AM ----------
Why is the default read ahead on the scheduler 16xxx? Isn't that a bit much?
M3drvr said:
Why is the default read ahead on the scheduler 16xxx? Isn't that a bit much?
Click to expand...
Click to collapse
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
thomas.raines said:
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
Click to expand...
Click to collapse
I wasn't too worried. Just wondering. Thanks! So far the new kernel very good. The first 5 minutes of it being installed there were quite a few lags and glitches. But after that, its smooth as ever!
thomas.raines said:
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
Click to expand...
Click to collapse
That's to be expected while the kernel settles in. Glad you're enjoying it!
Sent from my Nexus 4 using xda app-developers app
Should MPDecision be enabled if using the noop scheduler and Lionheart governor? Or whats your recomendation?
Welcome to the first custom kernel for the Samsung Galaxy Note 4.Providing instability to the masses since October 21, 2014
This kernel currently supports most North American carriers. Automatic selection is provided through the use of specialized recovery packages that will detect your device version and make appropriate adjustments.
Mereology (from the Greek μερος, ‘part’) is the theory of parthood relations: of the relations of part to whole and the relations of part to part within a whole. I do not take responsibility for anything these days, but I'll try to do my part and help.
Click to expand...
Click to collapse
Installing N910T ROMs on N910W8
Start with NJ3 stock firmware
Odin Flash CF-AutoRoot
Odin Flash TWRP
Make a full backup
Wipe system, data, cache, dalvik-cache
Install N910T Rom
Reboot System
Reboot Recovery
Install Stockish / Deported
Reboot System
Thank force70 for the guide
Known Issues:
DVFS set to ignore and secure storage disabled often resolve the lag. If you need either of these, stock / stockish are required.
Warning: I only have the T-Mobile version of the Galaxy Note 4
XDA:DevDB Information
StarKissed [ATT, CAN, TMO, USC, VZW], Kernel for the Samsung Galaxy Note 4
Contributors
twistedumbrella
Source Code: http://github.com/StarKissed/starkissed-kernel-trlte
Kernel Special Features:
Version Information
Status: Testing
Created 2014-11-07
Last Updated 2015-01-22
[Kernel] StarKissed [ATT, CAN, SPR, USC, TMO, VZW]
No mirrors please. Updates are posted 1 - 3 times per day.
Check the StarKissed website for compile info (not downloads)
Recovery Packages [Goo]
http://goo.im/devs/playground/galaxynote4/
Kernel source
http://github.com/StarKissed/starkissed-kernel-trlte
Retrieving a Kernel Log:
Code:
cat /proc/last_kmsg /sdcard/kernel_log.txt
SELinux Prerequisites:
The build.prop WILL override the kernel. It needs to be edited to match the desired settings.
Code:
(SELinux disable)
ro.build.selinux=0
(KNOX disable)
ro.config.tima=0
ro.config.knox=0
Potentially Inactive:
Potentially Unsafe:
pegasusQ
Features / Interfaces:
Linux 3.10.13 Linux 3.10.0
SELinux permissive
KNOX disabled
init.d support
Overclock to 2.8, Underclock to 268
Stereo call recording support
MNDIE Control
Motorola Memory Utils
Slimbus Overclock
Optimistic IPV6
intelli-plug (with arm64 updates)
Power Suspend
Simple GPU gov
HardLimit
intelli-thermal v1
Power Suspend Driver v1.5
Sweep2Sleep
Forced Fast Charge v1.2 (+ Wireless Charge Boost)
Advanced TCP avoidance
LZ4 compression
Dynamic FSync
add'l entropy: frandom, erandom (enabled via init.d)
add'l filesystems: NTFS, F2FS, CIFS
io: sio, fifo, zen, vr, bfq, fiops
gov: lionheart, dancedance, smartmax, pegasusQ, smartassV2, intellidemand, umbrella_core
CPU optimizations
Network optimizations
KNOX root and logging permissions
TIMA support, but disabled by default
S-View hack to use any cover
Common Interfaces
^ Borrowed from faux123 since many interfaces are MSM universal
Code:
cpu governor: /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
cpufreq: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
intelliplug: /sys/module/intelli_plug/parameters/intelli_plug_active
gpu governor: /sys/class/kgsl/kgsl-3d0/pwrscale/trustzone/governor
gpu freq: /sys/class/kgsl/kgsl-3d0/max_gpuclk
simple GPU gov:: /sys/module/msm_kgsl_core/parameters/simple_laziness
simple GPU gov: /sys/module/msm_kgsl_core/parameters/simple_ramp_threshold
io scheduler: /sys/block/mmcblk0/queue/scheduler
io scheduler readahead: /sys/block/mmcblk0/queue/read_ahead_kb
dynamic fsync: /sys/kernel/dyn_fsync/Dyn_fsync_active
usb fastcharge: /sys/kernel/fast_charge/force_fast_charge
intellithermal: /sys/module/msm_thermal/parameters/enabled
cpu voltage: /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
Power Suspend
Code:
/sys/kernel/power_suspend/power_suspend_state
/sys/kernel/power_suspend/power_suspend_mode (0 - auto, 1 - panel, 2 - userspace, 3- hybrid)
Hardlimit
Code:
/sys/kernel/cpufreq_hardlimit/scaling_max_freq_screen_on
/sys/kernel/cpufreq_hardlimit/scaling_max_freq_screen_off
/sys/kernel/cpufreq_hardlimit/scaling_min_freq_screen_on
/sys/kernel/cpufreq_hardlimit/scaling_min_freq_screen_off
/sys/kernel/cpufreq_hardlimit/wakeup_kick_freq
/sys/kernel/cpufreq_hardlimit/wakeup_kick_delay
/sys/kernel/cpufreq_hardlimit/touchboost_lo_freq
/sys/kernel/cpufreq_hardlimit/touchboost_hi_freq
/sys/kernel/cpufreq_hardlimit/userspace_dvfs_lock (0 - allow, 1 - ignore, 2 - refuse)
MNDIE Control
Code:
/sys/class/mdnie/mdnie/mode (0 - dynamic, 1 - control, 2 - natural, 3 - movie, 4 - auto)
/sys/class/mdnie/mdnie/...
hijack
curve
copy_mode
sharpen
red_red
red_green
red_blue
cyan_red
cyan_green
cyan_blue
green_red
green_green
green_blue
magenta_red
magenta_green
magenta_blue
blue_red
blue_green
blue_blue
yellow_red
yellow_green
yellow_blue
black, 0664
black_red
black_green
black_blue
white_red
white_green
white_blue
scenario
App & Donations:
StarKissed [SKU] on Google Play allows you to configure many of the options provided by this kernel. Issues or comments about the app can be posted at the XDA StarKissed app thread
Donations are not being collected through the forum. If you would like to donate, you may do so through StarKissed [SKU] on Google Play by using the donate options located in the top right (the green dollar bill guy).
Will be nice if you can provide two different build. One without all the fancy things that some people wont have use for, such as overclocking, close to stock as possible but still provide stability, smoothness, and better battery life.
Some kernel makers just slap everything they can onto a kernel and in the long wrong, it is simply instable or provide hicups (that they will never own up to lol)
Nice job twisted keep it coming...
mgbotoe said:
Will be nice if you can provide two different build. One without all the fancy things that some people wont have use for, such as overclocking, close to stock as possible but still provide stability, smoothness, and better battery life.
Some kernel makers just slap everything they can onto a kernel and in the long wrong, it is simply instable or provide hicups (that they will never own up to lol)
Click to expand...
Click to collapse
I don't provide anything I wouldn't run on my own device. If you want it to be stock, vote for stock. If that is what wins, that is what I will build. It is enough to provide a single kernel for a bunch of devices without trying to keep track of per-device versions. I slap everything I can onto a kernel, test it, then delete or fix the broken stuff. My github is always current and anything I changed is clearly published to point the finger at whoever it needs to be pointed at.
Lol just throwing it out there , that is my vote
I vote like mgbotoe! Thank you sir!
Sent from my SM-N910T using XDA Free mobile app
Only thing I am seeking is SE Linux Permissive. Thanks for all your work!
Tried flashing the files (that are highlighted) in picture attachment using odin 3.07, got a fail. What am I doing wrong? Anyone else flash yet? How'd ya do it and did it work out ok?
Thanks Ahead.
Glen
Hardlimit by yank555 I'd like to see, along with your hotplug of choice, I like intelliplug myself, some govs, I usually stick with interactive anyways, maybe some mdnie controls etc etc. Lol I'm just tossing out what I enjoy..but, you tell me, what do you normally build in your kernels.?
re: kernels
twistedumbrella said:
I don't provide anything I wouldn't run on my own device. If you want it to be stock, vote for stock. If that is what wins, that is what I will build. It is enough to provide a single kernel for a bunch of devices without trying to keep track of per-device versions. I slap everything I can onto a kernel, test it, then delete or fix the broken stuff. My github is always current and anything I changed is clearly published to point the finger at whoever it needs to be pointed at.
Click to expand...
Click to collapse
I just hope that you have already gotten some sort of windows pc so you
won't be having all those problems you were having for the past 3-4 days
due to using a mac computer.
Good luck with your kernels.
p.s. my vote is the same as mgbotoe's
glensta said:
Tried flashing the files (that are highlighted) in picture attachment using odin 3.07, got a fail. What am I doing wrong? Anyone else flash yet? How'd ya do it and did it work out ok?
Thanks Ahead.
Glen
Click to expand...
Click to collapse
I've heard Odin doesn't like the files. I use Heimdall but I'll be looking into that.
Misterjunky said:
I just hope that you have already gotten some sort of windows pc so you
won't be having all those problems you were having for the past 3-4 days
due to using a mac computer.
Good luck with your kernels.
p.s. my vote is the same as mgbotoe's
Click to expand...
Click to collapse
You're starting to sound like the Best Buy reps when Windows 8 came out. At least before they had to start telling everyone 8.1 was coming to fix how terrible it turned out being once people started using it.
You have to run cygwin or an Ubuntu VM inside windows to build Android. You can run windows AND Ubuntu as windowed applications on Mac. Seems unnecessary when the real issue is consistency in the cm repos. The instructions say to get the Linux compiler ports, while detection identifies the platform compilers.
And fast change it you can
Sent from my SM-N910T using XDA Premium 4 mobile app
---------- Post added at 08:56 PM ---------- Previous post was at 08:56 PM ----------
jpeps said:
And fast change if you can
Sent from my SM-N910T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SM-N910T using XDA Premium 4 mobile app
How about color/gamma controls???
jpeps said:
And fast change it you can
Sent from my SM-N910T using XDA Premium 4 mobile app
---------- Post added at 08:56 PM ---------- Previous post was at 08:56 PM ----------
Sent from my SM-N910T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't know how good of an idea messing with the adaptive charging would be, but I'll look into it. It depends if that functionality is tied into the USB port charging or not.
It is great that you have done this work and I (along with a bunch of others) are really grateful - it would be nice if we could flash this -
Doesn't work with Odin - not sure about the other option you mentioned, I personally have never used that method -
So - any instructions you can offer would be great - unless you feel it is not appropriate to flash this yet?
Your help - and input is greatly appreciated.
mocsab said:
It is great that you have done this work and I (along with a bunch of others) are really grateful - it would be nice if we could flash this -
Doesn't work with Odin - not sure about the other option you mentioned, I personally have never used that method -
So - any instructions you can offer would be great - unless you feel it is not appropriate to flash this yet?
Your help - and input is greatly appreciated.
Click to expand...
Click to collapse
Use flashify with the img file. Flash the boot option.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mgbotoe said:
Will be nice if you can provide two different build. One without all the fancy things that some people wont have use for, such as overclocking, close to stock as possible but still provide stability, smoothness, and better battery life.
Some kernel makers just slap everything they can onto a kernel and in the long wrong, it is simply instable or provide hicups (that they will never own up to lol)
Click to expand...
Click to collapse
I agree with this wholeheartedly. I personally loved leanKernel on my Note 3 - all the latest fixes and improvements without 40000 things that only crazy experimenters and overclockers would use. I'd love a solid, lean, and mean daily-driver kernel.
twistedumbrella said:
https://goo.im/devs/playground/trltetmo/kernel/. So what should be included? You are welcome to cast your vote for how this kernel evolves.
Click to expand...
Click to collapse
If you could somehow throw in faux sound support that would be awesome .. I miss raising my volume just a bit for alarms...
Anyways Thanks a lot bro
siraltus said:
I agree with this wholeheartedly. I personally loved leanKernel on my Note 3 - all the latest fixes and improvements without 40000 things that only crazy experimenters and overclockers would use. I'd love a solid, lean, and mean daily-driver kernel.
Click to expand...
Click to collapse
Ironically, modifying imoseyon's kernels was how I first learned to build. I took his and added those one or two additional things I found somewhere else and wanted to use. Right now, I am working on getting intellidemand updated for this kernel, but I am only looking to get a few options that really work well so if there are better, let me know.
For the TCP congestion avoidance, it appears that enabling advanced options somehow broke selection. It appears to work just fine, but that troubles me. I don't want to force a setting for that, but if it comes down to it, I may have to limit the options.
Veno, from some documentation I've recently read, was the optimal option for mobile network performance. I believe it was reno that was best for wifi performance, but I have to go back and read up again.
I added some code for fast charge to be verified, but the layout is much different than most Samsung phones, so I won't know if it works until I attempt to blow up my phone.
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