Related
Hey guys. This is Badass Kernel, a modified version of AU Kernel with a little bit too many additions to fit in the Original Development section.
Logs are disabled in this kernel. This is not a bug, it's a feature.
Compatibility:
Android 4.2.2
CM10.1
AOSPA
PAC
AOKP
Android 4.0.4/4.1.2
CM9
CM9.2
AOSP
Touchwiz ICS V5
So.. new stuff:
1.0
CPU Undervolt down to (0-1-2-4-6).
A_U's bootsplash
Added Badass CPU Governor
Added Badass GPU control
Replace ZRAM LZO compression with Google Snappy compression which is a lot faster
Kernel Samepage Merging enabled by default
Writeback tweaked to do the work only when the screen is off
Added ROW I/O scheduler
Tweaked smartassV2 for more battery saving
Tweaked CFQ and Deadline
1.1
Added frandom support for CrossBreeder to finally work properly
Fixed memory leak in android binder
Restored and updated Lazy CPU Governor (expected: smooth UI, much better battery life and some lag in the first 20-30 seconds after boot)
Filesystem tweaks
Memory tweaks
Added SFB net scheduler and Veno TCP congestion algorithm for better use of internet
Disabled a lot of debugging
1.2
Implemented Dynamic Filesync and enabled by default
Proportional Rate Reduction for TCP
Correct AXI bus values for CPU
Re-added 825 and 844 MHz frequencies (be careful with these as they're not stable, they were left out with a reason)
Trimming /cache every 15 minutes if media playback is stopped.
Updated LowMemoryKiller driver (if you use ram manager or scripts for setting minfree, here are some really good values:3072,4096,12800,14336,15360,19200)
New bootsplash (HTC-alike)
1.2.1
Fixed Snappy
Further UV (0-1-2-3-6)
1.2.2
Enabled Compaction and linked it to LowMemoryKiller
Updated Deadline(now it's better than ROW)
Changed kernel compressor/decompressor from GZIP to the much faster LZ4.
Writeback tweaks from Linus Torvalds
Added TCP congestion algorithms: Hybla, Westwood, Highspeed-TCP. Default is Hybla because in tests, performed better than the rest.
1.3
Enabled Triple Buffering (component of Project Butter by Google)
Added Tiny RCU for smaller memory footprint
Added BoostPulse interface for SmartassV2
1.3.1
Added BoostPulse interface for SmartassH3 and updated it with a new variable(boost_freq) to suit the governors ramping policy
1.4
Lots of code optimizations
AHB Overclocking for faster R/W operations[787 MHz and higher don't have this kind of overclocking because of instability)
New 652 MHz undervolted frequency
CPU Unaligned Access (much faster booting time because of better kernel decompression)
Buffer values updated from Samsung original sources(Triple Buffering, Camera)
SmartassH3 and KSM parameters tweaked for better battery life
1.5
CPU clocks rework
Modified AXI Bus to allow lower CPU frequencies
Added completely stable 68 MHz frequency
New undervolt settings (0-0-1-2-3-5-6-7)
Rewritten Badass CPU and GPU control driver to make more use of 68 MHz frequency
Tuned SmartassH3 to make more use of low frequencies
Added fully functional zCache and ZsmAlloc, backported from 3.4 kernel
1.5.1
Added LowBattery Powersave feature for Badass governor
Badass parameters are more performance biased now
Recalculated Frame Buffer Size for Triple Buffering
Clean-up(remove deprecated CPU governors)
1.6
Add newest Adaptive RED Net Scheduler from 3.4 kernel and make it default.
Replace Snappy Compression with LZ4 Compressor(this is the fastest compressor on the market)
Make our kernel probably the first 2.6 kernel to have these two features
1.6.1
Update LZ4 Compressor from original sources and make it fully functionable
1.7
Replace zRam XvmAlloc with the better ZsmAlloc integration
Update zRam from 3.0 drivers
Make zRam LZ4 decompressor work faster in the same CPU cycles
1.8
Add SIOPlus scheduler (finally something equal or better than deadline)
Add CPU Idle driver to support C4 Deeper Sleep state
Add Wheatley governor to make more use of the new C4 state.
Change Bootsplash
1.9
New governor: WheatleyPlus
Reworked scaling down logic for less calculation
Added BoostPulse interface
Linked BoostPulse to the touchscreen driver (now the governor can really "sense" a touch and boost the frequency after a specific time threshold)
Added Triphasic scaling up logic from Badass (Phase2 is 360 MHz and Phase3 is 480 MHz)
Fixed the Deep Sleep states verification for scaling
Added GPU Control Driver
Added Sampling Down Momentum for dinamically changing the factor for scaling down
Updated OnDemand governor (it's pretty good at the moment)
Remove Badass and Lazy as they were deprecated
Link BoostPulse to the touchscreen driver for SmartassH3 and OnDemand
Optimize the CPU clock structure for WheatleyPlus
Update SIOPlus and add fluid tunables
Introduce Dynamic Cache Pressure
Revise Dynamic Writeback algorithm
Introduce Timer Slack Controller (aka Timer Coalescing, explanation below)
Deep Sleep tweaks
Backport OOM Killing algorithm from 3.8 kernel
Backport LowMemoryKiller and Timed GPIO drivers from 3.8 kernel
Add Whitelist feature to LowMemoryKiller (you can write PIDs of the processes you want to whitelist, in this file > /sys/module/lowmemorykiller/parameters/w_list ~ below you'll find the script for doing this at boot)
Android Binder update
CFS kernel scheduler optimizations
GPU driver optimizations and code cleanup
Make sure that the GPU turns off when the screen is off
Make the sleep states transitions faster
1.9.1
Finetune WheatleyPlus for better responsiveness
Optimize WheatleyPlus for overclocking on 652 MHz and 768 MHz
Fixed graphical glitches(hopefully)
1.9.2
Every bug fixed
Removed WheatleyPlus
Updated Interactive governor to the latest version from 3.8 sources
Add Dynamic Interactive governor (98% the same as Interactive, but it dynamically changes its parameters according to the load)
Dynamic PLL Overclock
Further undervolt until 768 MHz (the latter allows us to do this without losing performance)
Predefine minfree and adj values
Fully functional App Whitelist (example script here)
Forced unaligned access
Fast Charge (use this to enable it: FastCharge.apk - 1.29 MB) [Disconnect USB Cable - Turn ON - Connect USB Cable]
Timer Slack Controller: (this is a copy-paste from boype's thread)
What does the timer slack feature do?
Timer slacking aims to synchronize applications' and processes' CPU requests. The goal is to wake up the CPU less often in oder to save battery. What you need to know here is the following: waking the CPU up and putting it back to sleep again consumes power. Imagine that four apps wake the CPU up four times each in one second. While without timer slacking the CPU would be woken up 16 times, it is desirable to coordinate the wakeups. If done right, the CPU would wake up less often, effectively allowing power savings and longer sleep periods. This is what timer slacking does.
I have activated timer slacking only for background applications, so that everything else stays as responsive as you know it.
Apple has recently introduced this feature under the name 'timer coalescing' with their Mac OSX Maverick (link).
More information: How Apple does timer slacking ('Timer coalescing') (Scroll a little down to the diagrams)
LZ4 Compressor:
LZ4 is a very fast compressor, based on well-known
LZ77 (Lempel-Ziv) algorithm. Originally a fork from LZP2, it provides
better compression ratio for text files and reaches impressive decompression
speed, in the range and beyond 1GB/s per core (!), especially for binary files.
These speeds are scalable with multi-threading modes, quickly reaching
RAM speed limits on multi-core systems.
ROW I/O scheduler:
The ROW scheduling algorithm will be used in mobile devices as default
block layer IO scheduling algorithm. ROW stands for "READ Over WRITE" which
is the main requests dispatch policy of this algorithm.
The ROW IO scheduler was developed with the mobile devices needs in mind.
In mobile devices we favor user experience upon everything else, thus we want
to give READ IO requests as much priority as possible. The main idea of the ROW
scheduling policy is just that: - If there are READ requests in pipe - dispatch them,
while write starvation is considered.
Download:
AOKP/AOSP ICS:BadassKernel-AICS.zip - 4.78 MB
AOKP:BadassKernel-AOKP.zip - 4.79 MB
CyanogenMod 9.2BadassKernel-ICS.zip - 4.76 MB
AOSPA:BadassKernel-PA.zip - 4.79 MB
CyanogenMod 10:BadassKernel-CM10.zip - 7.03 MB
CyanogenMod 10.1:BadassKernel-JB.zip - 4.79 MB
Various tweaks
Script for adding apps to LowMemoryKiller's whitelist:Whitelist
(you have to edit it to add your own apps, then move it to init.d and set correct permissions. right now you can only add one app, I'll fix this in the next version)
Script to enable zRam with optimized disksize for Fit: View attachment zRamV2.zip (flashable zip) [UPDATED]
Jeeko's PureAudio fixed for CM10.1 and AOKP: View attachment PureAudio__1.0_-_STUDIO.zip [ Please thank Jeeko for this awesome mod. ]
NOTE: This version of PureAudio is compatible with absolutely any equalizer or player.
If you have Titanium Backup installed, in the menu you'll find an option named "Integrate sys Dalvik into ROM". Use it.
This is something like odexing your system, but keeps the classes.dex files inside the apps. Don't worry if you don't have a lot of system space, Titanium will odex as much as it can until the free space runs out.
TIP: So in latest version of CrossBreeder, the OP added some system tweaking which interferes with our kernel. So I edited those parts to match our settings and device limits.
If anyone wants to install CrossBreeder:
-First uninstall by flashing this file: CrossBreeder_Uninstall_7.2.13.zip - 943.12 KB
-Then install this custom version: CrossBreeder_7.2.13-Badass.zip - 1.59 MB
Sources:
GitHub
Credits:
A_U for compiling the base kernel
franco for the various tweaks I cherry-picked from his source
androidarmv6 for fixing bluetooth
Ezekeel for his Wheatley governor
How to install the kernel?
Subdin said:
How to install the kernel?
Click to expand...
Click to collapse
Flash the zip.....
Sent from my GT-S5670 using xda premium
droider007 said:
Flash the zip.....
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
to install cm(9,10,10.1)
and just flash the kernel??????
CM 10.1 kernel isn't a zip...
NM99 said:
CM 10.1 kernel isn't a zip...
Click to expand...
Click to collapse
rename it to .zip
---------- Post added at 11:50 PM ---------- Previous post was at 11:49 PM ----------
droider007 said:
rename it to .zip
Click to expand...
Click to collapse
but don't try its not booting.......wait for a fix....:good:
I'll wait for the fix.
NM99 said:
I'll wait for the fix.
Click to expand...
Click to collapse
Changed the ramdisk, now it should boot. All versions are flashable zips, you don't have to reinstall the ROM for installing a kernel.
Keep a flashable zip with your original kernel on sd in case this doesn't boot.
I flashed kernel for CM10.1 RC6 of erikcas and it works without problems for me.
ZmisiS said:
I flashed kernel for CM10.1 RC6 of erikcas and it works without problems for me.
Click to expand...
Click to collapse
Alright, good to hear that.
Thanks for reporting. This means that the other versions will work too.
alin.p said:
Changed the ramdisk, now it should boot. All versions are flashable zips, you don't have to reinstall the ROM for installing a kernel.
Keep a flashable zip with your original kernel on sd in case this doesn't boot.
Click to expand...
Click to collapse
I'll be sure to flash it soon.
Just a question, I flashed the tweaks on this thread and Fly-On Scripts.. After flashing the kernel, do I need to flash them again?
---------- Post added at 06:33 PM ---------- Previous post was at 05:34 PM ----------
Just a little update, just flashed the kernel. No problems at all, it feels smooth as it can be. I'm running it 68-768Mhz with no problems.
Wake up in the morning..
Open xda (5670 forum)..
see something new anddd..
ohmyglob! FINALLY! SIR ALIN.P's KERNEL!
Best morning news and goodness in the morning! ooohh yeah! Time to test this baby out! By the way, I'd love to see your ROM here sir Alin! THANKYOU!
Kernel works perfectly at 768Mhz, something that I couldn't OC to before. I tryed to OC to 806Mhz and my Fit rebooted automatically. :lol:
Now I'm trying to use 787Mhz to see what can happen.
EDIT: Can't OC over 768Mhz. At 787 the G-Fit keeps running for 15 mins until it locks at whatever it's doing for forever and from 806 onwards it just reboots automtically. At least that's what my G-Fit does, don't know what about the others. Just sharing my personal experience so far with the Badass Kernel.
NM99 said:
I'll be sure to flash it soon.
Just a question, I flashed the tweaks on this thread and Fly-On Scripts.. After flashing the kernel, do I need to flash them again?
---------- Post added at 06:33 PM ---------- Previous post was at 05:34 PM ----------
Just a little update, just flashed the kernel. No problems at all, it feels smooth as it can be. I'm running it 68-768Mhz with no problems.
Click to expand...
Click to collapse
The kernel installs in its own partitions, it doesn't mess with the /system or /data. So you don't need to reinstall anything, only the kernel will be modified when flashing.
About the OC, the kernel uses the same clocks as the stock kernel, with a little tweaks for stability and battery life(Undervolt and refined AXI bus). I was expecting 768 to be the maximum, that's a physical limit. I can't do anything about it. Anyway, I added 748 MHz in case 768 is unstable for some of you.
Jhayzt said:
Wake up in the morning..
Open xda (5670 forum)..
see something new anddd..
ohmyglob! FINALLY! SIR ALIN.P's KERNEL!
Best morning news and goodness in the morning! ooohh yeah! Time to test this baby out! By the way, I'd love to see your ROM here sir Alin! THANKYOU!
Click to expand...
Click to collapse
Thank you too!
I just ported my ROM too. The no-gapps might still have some problems, not sure about it. I had only two reports and 30 downloads, maybe the errors are /data related and individual.
I'll be away for two weeks to prepare for my exams, so I'll answer your questions then.
alin.p said:
The kernel installs in its own partitions, it doesn't mess with the /system or /data. So you don't need to reinstall anything, only the kernel will be modified when flashing.
About the OC, the kernel uses the same clocks as the stock kernel, with a little tweaks for stability and battery life(Undervolt and refined AXI bus). I was expecting 768 to be the maximum, that's a physical limit. I can't do anything about it. Anyway, I added 748 MHz in case 768 is unstable for some of you.
Thank you too!
I just ported my ROM too. The no-gapps might still have some problems, not sure about it. I had only two reports and 30 downloads, maybe the errors are /data related and individual.
I'll be away for two weeks to prepare for my exams, so I'll answer your questions then.
Click to expand...
Click to collapse
For 768 MHz which governor, minimum and maximum CPU frequency?
camera!
video camera dont work on cm9!
with this kernel!
[/url][/IMG]On CM10.1 RC6 of erikcas all works except Skype.
Please answer the question: For 768 MHz which governor and minimum CPU frequency?
ZmisiS said:
On CM10.1 RC6 of erikcas all works except Skype.
Please answer the question: For 768 MHz which governor and minimum CPU frequency?
Click to expand...
Click to collapse
Governor....smartassH3 or badass
Min freq......122 or 68.....
Sent from my GT-S5670 using xda premium
alin.p said:
Alright, good to hear that.
Thanks for reporting. This means that the other versions will work too.
Click to expand...
Click to collapse
Thanks for such a speedy update... :good:
Hey guys, a new version of Crossbreeder has been released.. Can I install it or it can give problems with the kernel?
Aurora Kernel - N900xxx TW
This kernel is intended for battery-saving with keeping maximal possible performance
based newest NE6 sources
Linux 3.4.93 Update
Optimized Cortex-A15 4.10 LINARO Toolchain
see Features for details
Features:
- based on newest NE6 sources
- Linux upstream patches to 3.4.93
- SELINUX permissive
- Synapse support
- init.d support
- OC up to 2.8GHZ
- GPU OC from Snapdragon 801 (up to 587MHz)
- complete dts based kernels Voltage control by faux123
- IntelliPlug driver (for mpdecision replacement) by faux123
- IntelliThermal control driver (better than stock thermal control) by faux123
- Hardlimit CPU control interface by yank555:
- TouchWake by yank555
- PowerSuspend driver by yank555 with default set to hybrid-mode (autosleep and panel hook)
- FauxSound
- UKSM
- FastCharge Support
- LED Control
- mdnie Control by wootever
- Many governors: nightmare, dancedance, intelliactive, intellidemand, uberdemand, wheatley, smartmax, smartmax_eps, lionheart, pegasusq, darkness, hyper, badass, abyssplugv2, adaptive, conservative, ondemand, userpsace, powersave, interactive, performance
- More schedulers: noop, deadline, row, cfg, bfq, fiops, sio, zen
- enabled all TCP congestion controls: veno, westwood, cubic, reno, bic, highspeed, hybla, htcp, vegas, scalable, lp, yeah, illinois
- TCP congestion control default to veno
- new ARMv7 l2 cache
- Filesystem support: Ext2, Ext3, Ext4, FAT32, NTFS, USB OTG, exFAT with many fixes and optimizations (AIO, etc...)
- added multiple compression support for example LZ4, many patches
- F2FS support
- faster glibc
- frandom
- faster crypto libs
- Kernel XZ
- Ramdisk LZ4
- many fixes, updates, patches and enhancements from many sources
- many I already forgot
Check Synapse and thread to know all features
Changelog:
this post
Synapse profiles:
this post
DOWNLOADS
Direct downloads, look at my hosting:
mojosmirror.com
Downloads @ dev-host
Source: Github
Credits and many thanks to:
Much thanks to faux123 and yank555 for their great kernel
thanks to wootever for having always nice and useful commits
thanks to Imoseyon for having always nice and useful commits, too
thanks to civato for helping me starting here with studying his code
thanks to Myfluxi, labodj and Cl3Kener for commits
thanks to UpInTheAir for all his work with his Synapse interface
thanks to GuneetAtwal for some single picks
thanks to franciscofranco, zamcum, ZaneZam, CM-team, Codeaurora, ... and everyone else I forgot!
PM me, if you find your work not mentioned here
XDA:DevDB Information
Aurora Kernel Note 3, Kernel for the Samsung Galaxy Note 3
Contributors
MojoManagement
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R11v2
Stable Release Date: 2014-06-15
Created 2014-05-09
Last Updated 2014-08-29
Reserved
Reserved
Changelog
R11 (aka Synapse release)
NOTICE:
Due to heave Synapse changes again, I recommend to clear Synapse data, before you flash
If you feel unsnappy, raise Touchboost values, completely set both down to 300MHz at init
Synapse settings added & reworked (spent whole day into Synapse primarily)
Synapse can now make a flashable zip from your backup profile to share with others (look under tab Synapse)
Removed some sound pre-settings and removed FauxSound control for now to prevent still unknown issues
a few more fixes
R10 (beta)
NOTICE:
I recommend to clear Synapse data!!!
Synapse should now have enough options for daily settings
So please dont mix apps for setting kernel features
Synapse settings added (very hard work.....half day wasted here...)
S-Browser crash fixed on S5 ports
Sound issues fixed and quality should be improved
completely switched to UKSM now
a few more fixes and patches from different sources again
PS:
Please dont complain about voltage control in Synapse
If you want to experiment with voltages, you can set them one by one yourself
R9 (beta)
NOTICE: this will break some of Faux Control App functions, especially frequency setting, until Faux updates
If you dont want to run a beta, stick with R8 until stable release
There is currently not voltage, thermal, screen, zswap control in Synapse!
update to Linux 3.4.92
Synapse is back (but not everything is implemented), check yourself, big thanks to UpInTheAir, which made a very detailed Synapse layout, which I used as base
Hardlimit Interface update to 2.0a, you can now set screen on and screen off max/min frequencies separately, wakeup kicks, touchboosts, DVFS lock... check Synapse
GPU OC with Snapdragon 801 values (up to 587MHz)
Ramdisk is now LZ4 compressed (need to check kernel for LZ4, too)
Led Control updated to V1.2
IntelliPlug updated to newest version
Logger can be enabled/disabled through sysfs interface
many fixes and patches from different sources again
R8
finally working NE6 base with all known features
R7
updates base to NE6
same as R6
R6
switched to faux123-yank555 kernel as new base
over 300 commits added, patches, fixes, enhancements, etc...
see features
r5
lower power frequency 268,8MHz should work now as expected
lowered voltage for 268,8MHz (its really low, report if unstable)
new govs: lagfree and smartassv2, both tuned
updated and optimized fiops scheduler (which I recommend for internal)
optimized BFQ scheduler (which I recommend for external...)
linux update to 3.4.91
CIFS support (experimental)
enabled ksm (experimental)
swap support
updated toolchain to Linaro 4.9.1 05/2014
LZ4/LZO updates
some sound patches
many arm patches
some memory patches
more I forgot ...
r4
more fixes and enhancements
more govs: intelliactive, abyssplugv2, conservativex, adaptive
Dynamic FSYNC is back
permanent async FSYNC from HTC
PowerSuspend updates: hooked to AutoSleep and Panel, first sleep hook wins
experimental low power frequence
zen scheduler added
few more things
r3
over 60 fixes, patches and enhancements since r2
LZ4
crypto optimizations
faster glibc
very fast random generation (10-50 times faster)
gpu patches
linux update
many more
r2
over 50 fixes, patches and enhancements at all from beta
support for N900T
updated busybox (problems fixed)
updated ramdisk
mpdecision improved (also recommend Intelli Hotplug)
more compiler improvements
scheduler patches
dynamic fsync disabled (more later)
cpu patches for msm
enabled last kernel message
many more
Community profiles for Synapse:
How to use shared profile?
Flash shared profile in recovery
Reboot to system
OpenSynapse
Go to tab "Synapse"
Check if last backup says "flashed" at the end (time buggy at the moment sorry)
Press "Restore & Close Synapse"
Open Synapse
Press X[ Cancel/B] at the top to use restored settings (if you press "✓ Apply" your last settings will be restored)
R11:
gianton:
Here's my current setup I'm testing on r11. It's more for battery saving, if you play lots of games set the governor to intelliactive.
Click to expand...
Click to collapse
Link to post for download
Tried to download but link empty
Sent from my SM-N9005 using Tapatalk
Does it have ntfs r/w support?
Sent from Hacker OS
IzArsha said:
Does it have ntfs r/w support?
Sent from Hacker OS
Click to expand...
Click to collapse
Should work if I did not make any mistake
panjaby said:
Tried to download but link empty
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Downloads tested, all links should be working
Awesome kernel. Just one question, does it support GPU OC?
blogslogger said:
Awesome kernel. Just one question, does it support GPU OC?
Click to expand...
Click to collapse
Not yet, because I remember problems with frequencies are not used and also decrease performance with gpu set to 550
I just find the correspondending post by sorg
sorg said:
http://forum.xda-developers.com/member.php?u=3986004
About GPU overclock:
My phone is Samsung SHV-E330S, which is basically GT-N9005 in S4 case, so 99% hardware is the same.
According to my investigation in GPU overclocking, frequencies are handled fully inside RPM firmware. Frequencies in .dtsi files aren't used. RPM uses its own frequency table and cannot be changed from linux side. So, your GPU OC simply doesn't affect actual GPU frequencies. Linux GPU governor will think it uses new frequencies and will actually switch to a wrong frequency (because RPM will use hardcoded unmatched freq table) - so everything will go wrong (as you already noticed, probably).
I've monitored GPU/PLL hardware registers and saw, they work according RPM's table and not affected by .dtsi settings.
There is the only way to overclock SD800 GPU is by modifying PLL settings (as it was done for SD600 GPU). There is PLL for highest GPU powerlevel's frequency which used solely by GPU (just like in SD600). But performance increase is not so high as it could be from increasing RAM frequency OC (which i didn't manage to tweak yet).
P.S.: I don't know about N9005, but in E330S standard highest frequency is 550MHz (according to PLL settings) instead of 450MHz as advertized in MSM8974 (not AB or AC), although in .dtsi files max frequency is 450MHz. Good bonus from Samsung
Probably, in N9005 it's the same.
Click to expand...
Click to collapse
I might have a look into that in the future
Does it work with ND5 update
bhasg1007 said:
Does it work with ND5 update
Click to expand...
Click to collapse
Yeah, I am on ND5 rom with ND5 bl and NC2 modem
Downloaded Thanks for the reply will try now
Can I flash this kernel over lean kernel?
Tia
Sent from my SM-N9005 using XDA Premium 4 mobile app
Cool! A new kernel! gonna try it now and will be back with results in a day or two
Sent from my SM-N9005 using XDA Premium 4 mobile app
ghalib87 said:
Can I flash this kernel over lean kernel?
Tia
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Of course
MojoManagement said:
Downloads tested, all links should be working
Click to expand...
Click to collapse
Apologies. The fault must be on my end.
If I open the first link with chrome it goes blank with mojo wesite bit if I open the link directly with es downloader it downloads
Sent from my SM-N9005 using Tapatalk
MojoManagement said:
Not yet, because I remember problems with frequencies are not used and also decrease performance with gpu set to 550
I just find the correspondending post by sorg
I might have a look into that in the future
Click to expand...
Click to collapse
Thankyou for your patience. It was quite helpful to learn a new thing.
I have got a problem when put on usb charge it stays on high frequency and instead of charging, the phone battery gets dischaged slowly. anything i have to do.
Welcome to Frosted Kernel for the HTC One S (Ville)
Code:
#include <std/disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. :P
* blah blah blah you get the point.
*/
Why I created a SECOND kernel:
So for those of you living under a rock (jk), I already maintain Void Kernel for the One S, so why would I bother creating another? Well @Rapier started having issues, so I PM'd him a patch. He sais he would test it later but commented on how Void LP and IceCode LP were feeling a bit sluggish (they share the same base) where as the stock CM 12 Kernel is super smooth. I then tried the CM 12 stock kernel and realized that he was right. So I forked the CM stock kernel and added some basic features and sent it to him. He commented on how the OC values weren't sticking properly and the Benchmarks were really low but how it was smooth. So I fixed the OC, and added @show-p1984's MSM_MPDEC and MSM_THERMAL to speed it up and when I benchmarked it, I got 6788 in quadrant. That was a couple of hours ago. Now, I'm releasing it into the wild. The main focus of the Bricked Edition (like Bricked Kernel before it) is speed and stability. Undervolting is doable but you have to do it yourself and if you get random reboots I will not help you there. Enjoy Frosted Kernel everybody!
I'm really sorry for the noobish question, but how do I tweak this kernel's settings? Which app should I use?
Click to expand...
Click to collapse
Rapier said:
For Bricked edition you can use TricksterMOD, for Intelli edition you can use FauxClock (but that's paid app)
Sent from nowhere over the air...
Click to expand...
Click to collapse
For Wake Controls: http://forum.xda-developers.com/showpost.php?p=59179565&postcount=169
(Thanks derkleinebroicher!)
Post #1: Disclamer, Why I created this Kernel
Post #2: Download and Features for Bricked Edition
Post #3: Changelog for Bricked Editon
Post #4: Download and Features for Intelli Edition
Post #5: Changelog for Intelli Edition
Post #6: Download and Features for Void Edition
Post #7: Changelog for Void Edition
Post #8: Link to Discussion Thread
XDA:DevDB Information
Frosted Kernel, Kernel for the HTC One S
Contributors
javelinanddart, Rapier, jrior001, rmbq, AKToronto, show-p1984, flar2, faux123, Rapier, Winstarshl, derkleinebroicher, unimatrix.ø, Loreane Van Daal
Source Code: github.com/FrostedKernel/android_kernel_htc_msm8960
Kernel Special Features:
Version Information
Status: Stable
Created 2015-02-15
Last Updated 2015-03-21
Bricked Edition Features:
Compiled with the Lastest Linaro Toolchain Optimized for Cortex-A15 by @Christopher83
Compiled with -O3 Optimization
XZ Compression (-O3 creates larger code, need it to keep it in check)
Voltage Control by @faux123
CPU Overclocking to 1.836GHz (Stable too!)
CPU Underclocking to 192MHz (Also Stable)
GPU Overclocking to 512MHz (Stable but phone gets really warm)
BLN by @rmbq
Sweep2Wake and Sweep2Sleep by @show-p1984
DoubleTap2Wake and DoubleTap2Sleep by @flar2
Pocket Detection by @flar2
TCP Congestion Control Algorithms: Bic, Cubic, Westwood (default), HSTCP, Hybla, Vegas, Scalable, Low Priority, Veno, Reno, YeAH, and Illinois
CPU Governors: Performance, Powersave, Userspace, Ondemand, Interactive, Conservative, Intellidemand, Intelliactive, Intellimm, TRIPNDROID, Lionheart, Badass (default), SmartassV2, ElementalX, and Preservative
GPU Governors: Ondemand, Performance, and Simple
I/O Schedulers: Noop, ROW, Deadline, CFQ, BFQ, FIOPS (default), SIO, SIO Plus, FiFo, TRIPNDROID, ZEN, and Vr
MSM_MPDECISION and MSM_THERMAL by @show-p1984
MSM_MPDECISION Input Boost Available
Lastest CAF + Latest Linux 3.4 Source
Vibrator Intensity Control
Amazing Build Flags
Fast Charge
Module Support
Export Krait Variant
exFAT Support
UTF-8
FRANDOM Support
Asynchronous Fsync
KCal Control by @faux123
Sound Control by @faux123
91% Compatible with KControl
F2FS Support
QSEECOM Support
Frosted Bricked Installer Features:
AROMA Installer with Holo Theme
License (GPLv2)
Terms of Use (Disclaimer)
Changelog
Date Updated
Kernel Edition
Confirmation Screen
Reboot Option at the End
Add Init.d Support
Enable Insecure Kernel
Remove Governor Overrides
Things to do:
Command Line Interfacing
Downloads:
https://www.androidfilehost.com/?w=files&flid=26289
https://mega.co.nz/#F!F15SCBzL!9dMuU3o3nS5rlLUEFuenfg
https://www.mediafire.com/folder/bc9iobppko517/Bricked_Edition
Code:
[SIZE="5"][B]Bricked Edition Changelog:[/B][/SIZE]
Mar 10
-MAJOR clean up of source
Mar 01
-QSEECOM Support
-Wake Controls disabled by default
Feb 24
-Revert GPU Memory Usage Feature
Feb 23
-Merge with CM
-Badass GPU Control
-Update Toolchain
-Revert Badass GPU Control
Feb 22
-GPU Memory Usage Feature for KControl
Feb 21
-Add SIO Plus I/O Scheduler
-Fix Logic Derp in Simple GPU Governor
Feb 20
-Update MSM_MPDECISION
-Set Multi Core Power Saving Mode to 2 by Default
Feb 18
-Build KControl Module as a Module
-Add KCal Control
-Add Sound Control
-Add F2FS
Feb 17
-Build exFAT into the kernel
-Build SCSI_WAIT_SCAN into the kernel
-Try building @show-p1984's KControl Module in to the kernel
-Added SmartassV2 Governor
-Added Asynchronous Fsync
-Merge with CM
-Lower Thermal Throttle Values
Feb 16
-Export Krait Variant
-More I/O Schedulers
-More CPU Governors
-Bump OC Voltages
-Choose Badass and FIOPS as default
-Add exFAT Support
-Add FRANDOM Support
-KControl GPU Module
Feb 15
-Fix OC to 1.836GHz
-MSM_THERMAL
-Compiled with -O3
-Switch to XZ Compression
-Added Module Support
-Added Simple GPU Governor
Feb 14
-Linaro GCC 4.9 Optimized for Cortex-A15
-Bump all stock Voltages to 1150000
-Bump OC Voltages
-CPU OC to 1.836GHz
-CPU UC to 192MHz
-MSM_MPDEC
-Merge with CAF
-Merge Linux 3.4.106
Feb 13
-Initial Fork of CM
-Wake Controls
-BLN
-Voltage Control
-CPU and GPU OC to 1.728GHz and 512MHz
Intelli Edition Features:
Compiled with the Lastest Linaro Toolchain Optimized for Cortex-A15 by @Christopher83
Compiled with -O3 Optimization
XZ Compression (-O3 creates larger code, need it to keep it in check)
Voltage Control by @faux123
CPU Overclocking to 1.836GHz (Stable too!)
CPU Underclocking to 192MHz (Also Stable)
GPU Overclocking to 512MHz (Stable but phone gets really warm)
BLN by @rmbq
Sweep2Wake and Sweep2Sleep by @show-p1984
DoubleTap2Wake and DoubleTap2Sleep by @flar2
Pocket Detection by @flar2
TCP Congestion Control Algorithms: Bic, Cubic, Westwood (default), HSTCP, Hybla, Vegas, Scalable, Low Priority, Veno, Reno, YeAH, and Illinois
CPU Governors: Performance, Powersave, Userspace, Ondemand, Interactive, Conservative, Intellidemand (default), Intelliactive, Intellimm, TRIPNDROID, Lionheart, Badass, SmartassV2, ElementalX, and Preservative
GPU Governors: Ondemand, Performance, and Simple
I/O Schedulers: Noop, ROW, Deadline, CFQ, BFQ, FIOPS (default), SIO, SIO Plus, FiFo, TRIPNDROID, ZEN, and Vr
Intelli_Plug and Intelli_Thermal by @faux123 (Use Eco Performance in Fauxclock, TricksterMod chooses it by default, otherwise it lags too much)
Lastest CAF + Latest Linux 3.4 Source
Vibrator Intensity Control
Amazing Build Flags
Fast Charge
Module Support
Export Krait Variant
exFAT Support
UTF-8
FRANDOM Support
Dynamic Fsync by @faux123
KCal Control by @faux123
Sound Control by @faux123
F2FS Support
QSEECOM Support
Frosted Intelli Installer Features:
AROMA Installer with Holo Theme
License (GPLv2)
Terms of Use (Disclaimer)
Changelog
Date Updated
Kernel Edition
Confirmation Screen
Reboot Option at the End
Add Init.d Support
Enable Insecure Kernel
Remove Governor Overrides
Things to do:
Command Line Interfacing
Downloads:
https://www.androidfilehost.com/?w=files&flid=26435
https://mega.co.nz/#F!ssgDCBxQ!YXmLgPTkoeAPhHxSsGdBIw
https://www.mediafire.com/folder/7sef2akc9tb4y/Intelli_Edition
Code:
[SIZE="5"][B]Intelli Edition Changelog:[/B][/SIZE]
Mar 10
-MAJOR clean up of source
-Update Intelli_Plug to version 4.0
Mar 01
-QSEECOM Support
-Wake Controls disabled by default
-Revert Badass GPU Control
-Revert Memory History Usage Feature
Feb 23
-Merge with CM
-Badass GPU Control
-Update Toolchain
Feb 22
-GPU Memory Usage Feature for KControl
Feb 21
-Add SIO Plus I/O Scheduler
-Fix Logic Derp in Simple GPU Governor
Feb 20
-Set Multi Core Power Saving Mode to 2 by Default
Feb 18
-Build KControl Module as a Module
-Add KCal Control
-Add Sound Control
-Add F2FS
Feb 17
-Initial Fork from Bricked Editon
-Dynamic Fsync
-Intelli_Plug instead of MSM_MPDECISION
-Intelli_Thermal instead of MSM_THERMAL
-Merge with CM
Reserved 3
Reserved 4
Link to Discussion Thread:
http://forum.xda-developers.com/htc-one-s/general/kernel-rain-kernel-javelinanddart-t2948552/
This was the Old Void Kernel Thread. I check both threads often.
@javelinanddart whatever you did, you did it right. Just flashed it and of course is to early to tell but looks extremly good. It's the first time I've OCed my ville so high (to max 1.8 GHz) and looks stable so far, no reboots and it doesn't get warmer either.
Proc was ramping up to the max also which was not happening in that test version also Quadrant finish the tests faster than ever. I didn't get 6800 score as you did but that could have many causes and that's not so important for me. What I care most is that phone flyes now and it doesnt reboot (yet...we'll see in time how stable it is).
Even if it lacks some of the other kernel features for now, it looks to me the best LP custom kernel so far. That's really good...trully. I do hope it won't misbehave in time cause I love how my phone feels now.
Sent from nowhere over the air...
javelinanddart said:
First Build is UP!
Named frostedbrickedlp1502215.zip in my AFH. MEGA and Mediafire mirrors coming soon are live as well! Enjoy!
Click to expand...
Click to collapse
Niceee) I go flash and test)
Ohh...
Test1 - bug buttons on screen off... have this too....
Rapier said:
@javelinanddart whatever you did, you did it right. Just flashed it and of course is to early to tell but looks extremly good. It's the first time I've OCed my ville so high (to max 1.8 GHz) and looks stable so far, no reboots and it doesn't get warmer either.
Proc was ramping up to the max also which was not happening in that test version also Quadrant finish the tests faster than ever. I didn't get 6800 score as you did but that could have many causes and that's not so important for me. What I care most is that phone flyes now and it doesnt reboot (yet...we'll see in time how stable it is).
Even if it lacks some of the other kernel features for now, it looks to me the best LP custom kernel so far. That's really good...trully. I do hope it won't misbehave in time cause I love how my phone feels now.
Sent from nowhere over the air...
Click to expand...
Click to collapse
Thanks
I set the voltages pretty high for stability and @show-p1984's ThermalD is working it's magic
To fix the OC problem, the Ville Regulator file wasn't accepting voltages past 1300000 even though it could handle up to 1450000
I raised the Max and it allowed the OC
EDIT: About features, there will be two versions. This and Frosted Void Edition. Void Edition will include lots of extra features where as Bricked edition is meant to be a revival of sorts of @show-p1984's Bricked Kernel. I'll add Govs and I/O Scheds but no Sound Control or KCal on this one or extra stuff like that. I might look at intelli_plug in the future but I like this because it's so smooth and fluid even if the battery life isn't as good. (Probably could be tuned with KControl to get similar battery life)
EDIT 2: DO NOT USE KERNEL TUNER IT DOESN'T WORK ON MY DEVICE IT CAUSES A BOOTLOOP
You may or may not get similar results. It got a slow down and a bootloop for me
Winstarshl said:
Niceee) I go flash and test)
Click to expand...
Click to collapse
Thanks! I hope you like it!
I use Kernel Tuner 2014 just for setting the OOM values cause neither FauxClock or TicksterMOD have them preset. After I apply the values with kernel tuner I save them as presets in Trickster. I'm not so happy with this approach but I could not find a better alternative at this point
Sent from nowhere over the air...
Rapier said:
I use Kernel Tuner 2014 just for setting the OOM values cause neither FauxClock or TicksterMOD have them preset. After I apply the values with kernel tuner I save them as presets in Trickster. I'm not so happy with this approach but I could not find a better alternative at this point
Sent from nowhere over the air...
Click to expand...
Click to collapse
You could use an init.d script
I think the installer has one or two, I just didn't set the permissions to run the script because they're leftover from the speed tweak removal
BTW, I'm working on the To-Do list under the OP. Trying to keep it close to Bricked Kernel's feature list. Did I forget any simple features?
javelinanddart said:
...BTW, I'm working on the To-Do list under the OP. Trying to keep it close to Bricked Kernel's feature list. Did I forget any simple features?
Click to expand...
Click to collapse
Don't think you forgot anything but I didn;t understood if BLN is already added or it will be...cause if it's added already it's not working. I see the option to activate it in Trickster but still I got no light on those buttons when a notification come
HM...strange...just sent myself a text message and now it's working. But On other notifications like the ones from tapatalk or G+, it didn't. Forget that, I'll test it more to see what's happening
Rapier said:
Don't think you forgot anything but I didn;t understood if BLN is already added or it will be...cause if it's added already it's not working. I see the option to activate it in Trickster but still I got no light on those buttons when a notification come
HM...strange...just sent myself a text message and now it's working. But On other notifications like the ones from tapatalk or G+, it didn't
Click to expand...
Click to collapse
That's probably a bug with the apps or the notifications system in lp
It works fine for me but I don't use Tapatalk and I don't know how to "fix" BLN either because some apps work and some don't
We will have to see. I'm getting the -O3 bugs ironed out. It's a pain in the *** because all the fixes for Prima don't work with the newer drivers. And they're each 12000 lines long. Trying to fix them is horrifying. I'll add Fastcharge after that and finish the rest of the to-do list soon after
EDIT: -O3 is done but when I tried to flash it, It didn't boot. @AKToronto expressed a concern about how -O3 makes the code bigger and how there's an upper limit to the kernel size. I think I hit it. I switched to XZ and am building it now to test. XZ increases the boot time a little bit but once it's booted, it makes no difference.
EDIT 2: Yep, boots with XZ. Installing Quadrant to test speed.
EDIT 3: Got 6000 in Quadrant. I think it might've been really lucky to get 6788 earlier but it terms of fluidity there's no difference
Try it yesterday, good battery life but there are some random reboots for me
javelinanddart said:
Thanks! I hope you like it!
Click to expand...
Click to collapse
Maybe compile kernel without (s2w, s2p, d2w, d2p)? Because when screen off, this func not off... in this kernel too(..
grorg said:
Try it yesterday, good battery life but there are some random reboots for me
Click to expand...
Click to collapse
Really? What settings have you enabled/chosen? Have you tweaked the voltages?
Winstarshl said:
Maybe compile kernel without (s2w, s2s, d2w, d2s)? Because when screen off, this func not off... in this kernel too(..
Click to expand...
Click to collapse
Definitely will do once today's update rolls out
The point of them is to wake up the phone is the screen is off, therefore they have to be on when the screen is off
Introduction
This kernel is based on Smartpack kernel by @sunilpaulmathew. The kernel has undergone many changes to further improve both battery life and performance from already what was an excellent kernel for the S5.
Features
CPU Governors - yankactive, impulse, ondemandplus, adaptive, smartmax, smartmax_eps, wheatley, nightmare, alucard, intellidemand, intelliactive, zzmoove, interactive, conservative, ondemand, powersave, lionheart, performance
IO Schedulers - zen, sioplus, deadline, cfq, bfq, tripndroid, vr, row, noop, fifo
GPU governors - simple_ondemand, msm_adreno_tz and more
Hotplugs - mpdecision, intelliplug
TCP algorithms- All enabled. Westwood default for best performance.
Franco Sound Control
Dynamic Hotplug
Dynamic Fsync
LCD notifier
Disabled CRCs for performance
Linaro 7.2 Toolchain
Supported Variants
klte: SM-G900F, SM-G900V, SM-S902L
kltekor: SM-G900K, SM-G900L/SM-G900S
kltedv: SM-G900I ,SM-G900P
klteduos: SM-G900FD, SM-G900MD
No other variants are supported
Download
AFH - https://www.androidfilehost.com/?w=files&flid=240642
How to install
1. Ensure you are not running a custom kernel already (can conflict)
2. Flash my kernel
3. Wipe dalvik/cache
4. Reboot
Credits
Sunilpaulmathew - For kernel base and scripts
Linus Torvalds - For linux kernel
Lord Boeffla - For many tweaks and patches
nathanchance - For Linaro TC
faux123 - For intell* governors/hotplugs
alucard12 - For alucard hotplug
haggertk - For LOS14.1
franciscofranco - For franco sound control
Source:
Github - https://github.com/gsstudios/LOS-plus-kernel
Changelogs
See github page
Kernel Adiutor Suggestions
Battery Savings
CPU Governor - Nightmare
Hotplug - Intelliplug
IO sched - ZEN
GPU governor - simple_ondemand
Performance
CPU Governor - Ondemandplus
Hotplug - Intelliplug
IO sched - ZEN
GPU governor - msm_adreno_tz
You can change around these settings or add your own if you like
What app do I use to tune this kernel?
I highly recommend Kernel Adiutor. It's free, open-source and is on the Google Playstore.
When will feature xyz be added?
I'll add it if I think everyone will benefit from this change, and that also means that I must find this feature to be useful.
Donations
While I am glad people want to help with the development through donations, I am generally opposed to accepting any form of donation.
Microphone not working?
Make sure the microphone gains in the sound section of KA is > 0. Alternatively, ensure that apply on boot has been unticked.
How do I use intellithermal?
In the CPU hotplug tab in KA, disable the two sliders underneath the slider for intellithermal. Then you may switch on intellithermal.
How can I help with development?
If you see or encounter any issues, let me know on github or on an XDA post. If you want to help develop, you can easily fork this project on github, add your own changes, then submit a pull request.
I'm back into kernel development after taking a long break since maintaining Dorimanx kernel for the S5. :highfive:
I've just released my first build (v1) which I've tested for some time now. Please let me know if there are any issues with the usual bug report format (dmesg + logcat + description of issue).
I just like a give another special thanks to @sunilpaulmathew for allowing me to use his kernel as base and for being open to the opensource community
Enjoy
Good to see you back to Kernel development... :good:
It will be a good deal for our S5 users
and hope you will still be active in my thread...
Saber said:
I'm back into kernel development after taking a long break since maintaining Dorimanx kernel for the S5. :highfive:
I've just released my first build (v1) which I've tested for some time now. Please let me know if there are any issues with the usual bug report format (dmesg + logcat + description of issue).
I just like a give another special thanks to @sunilpaulmathew for allowing me to use his kernel as base and for being open to the opensource community
Enjoy
Click to expand...
Click to collapse
I'll try it, I just want perf fixes
Further testing has reveal that Faux sound control values don't stick after setting them in KA. This issue will be resolved in the next build.
Regards, Saber
Is this the kernal that was going to help with the RR issues? Thanks for this kernal.
BadToThePhone said:
Is this the kernal that was going to help with the RR issues? Thanks for this kernal.
Click to expand...
Click to collapse
If you mean the performance issues with Smartpack + RR, then yes. However, it will take some tweaking it get it "buttery smooth".
Saber said:
If you mean the performance issues with Smartpack + RR, then yes. However, it will take some tweaking it get it "buttery smooth".
Click to expand...
Click to collapse
already noticing a HUGE difference in performance. It's phenomenal. Howcome I/O for internal is missing in KA
Does Faux audio interfere with V4A?
GeTex said:
already noticing a HUGE difference in performance. It's phenomenal. Howcome I/O for internal is missing in KA
Does Faux audio interfere with V4A?
Click to expand...
Click to collapse
I guess you mean internal IO scheduler? Works fine on my end. Maybe reflash kernel or try one of the modded KA apps.
As for faux sound control and V4A, I think you can have both, as long as you don't tune the values for faux sound (which BTW is broken until the next release).
Saber said:
I guess you mean internal IO scheduler? Works fine on my end. Maybe reflash kernel or try one of the nodded KA apps.
As for faux sound control and V4A, I think you can have both, as long as you don't tune the values for faux sound (which BTW is broken until the next release).
Click to expand...
Click to collapse
Internal I/O is missing from menu's, kernel clearly is flashed
good to know
GeTex said:
Internal I/O is missing from menu's, kernel clearly is flashed
good to know
Click to expand...
Click to collapse
Odd, I would imagine it would be an issue with KA unable to detect the paths required for IO tuning. Maybe problems with permissions? Any logs because I'm running out of ideas...
@Saber and @GeTex Can you please post your recommended settings? Battery is more important to me than performance. Would appreciate it very much.
BadToThePhone;75181281 [user=5811506 said:
@Saber[/user] and @GeTex Can you please post your recommended settings? Battery is more important to me than performance. Would appreciate it very much.
Click to expand...
Click to collapse
There's many ways to go about it, I cannot comment immediately and I'd rather work with @Saber first on a good configuration but so far I can recommend this
Change CPU gov to ondemandplus
Change CPU hotplug to intelliplug, change hytersis value to 4, change screen of freq to 10xx MHz, use profile balanced and touch boost on
Change internal I/O to sio or sioplus, readahead to 1024, external I/O to noop and readahead 2048, change swappiness to 30 and vfs cache pressure to 130, or keep 100 for neligable benefits, turn on KSM with an interval of 1000 or 500 for slightly better performance at cost of minor battery, make sure Zram is set to 420mb or less. Turn off the thermal drivers and use intellithermal on defaults
With a brand new battery I have 4hr10 screentime and 1d standby, that is with alot of background stuff such as 20 minute GPS pings and weather updates, wifi and data and GPS always on
Battery life isn't up to date yet, will need to test a few more days
I was previously using these settings. Do any of these still apply? Thanks
Cpu governor: nightmare
Cpuhotplug: intelliplug
Touchboost: on
Cpu threshold: 1250
Thermal: intellithermal on, vdd and corecontrol off
Gpu: adreno idler
I/o scheduler: zen
Sleep between scans: 1000ms
Power suspend mode: autosleep
Fast charge on
Fsync On
BadToThePhone said:
I was previously using these settings. Do any of these still apply? Thanks
Cpu governor: nightmare
Cpuhotplug: intelliplug
Touchboost: on
Cpu threshold: 1250
Thermal: intellithermal on, vdd and corecontrol off
Gpu: adreno idler
I/o scheduler: zen
Sleep between scans: 1000ms
Power suspend mode: autosleep
Fast charge on
Fsync On
Click to expand...
Click to collapse
No adreno idler in this kernel. Best to use power suspend mode hybrid for better battery life (uses display state + kernel sleep).
Edit: Also no UKSM. You can enable KSM if you like, but I personally don't need it.
BadToThePhone said:
@Saber and @GeTex Can you please post your recommended settings? Battery is more important to me than performance. Would appreciate it very much.
Click to expand...
Click to collapse
Please read my second post. Main goal of my profile is good battery + performance balance without that "lag" in RR. Change around the profile if you like to suit your taste (e.g. zzmoove instead of ondemandplus).
Saber said:
Please read my second post. Main goal of my profile is good battery + performance balance without that "lag" in RR. Change around the profile if you like to suit your taste (e.g. zzmoove instead of ondemandplus).
Click to expand...
Click to collapse
Is following your suggested settings plus what @GeTex recommended doing too much? Thanks alot
BadToThePhone said:
Is following your suggested settings plus what @GeTex recommended doing too much? Thanks alot
Click to expand...
Click to collapse
It's a little more extra compared to my recommendations, but either is fine for good balance.
When turning on intellithermal do I have to turn off vdd and corecontrol? Also do I have to turn off mpdescion?
****Ares-Kernel****
****By****
****The~Skater~187****
This kernel is a combination of SmartPack/Boeffla-Venom Samsung Galaxy S5 Lineage OS kernel, with some tweaks and additions from around the net. I have decided that since SmartPack was EOL and with sunilpaulmathews ok, I would just combine our two kernels (since fbs has Boeffla-Kernels covered) to make it easier for me to maintain his work and my own.
/* DISCLAIMER! *\
*I am not responsible for any damage to your device*
* Everything you are doing on your device is at your own risk*
*Don't forget to make a back up before flashing*
~~~~~~~~~~~~~~~Flash at own risk~~~~~~~~~~~~~~~~~~
/* Supported devices *\
klte: SM-G900F, SM-G900AZ, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L
kltekor: SM-G900K/L/S
kltedv: SM-G900P/I
klteduos: SM-G900FD, SM-G900MD
kltekdi: SCL23
/* Compatibility *\
DO NOT FLASH OVER CUSTOM KERNELS!
This kernel is only meant to work on Lineage-OS 15.1/16 and nothing else. However, it may work on other LOS-15.1/16 (and AOSP) based Oreo/Pie ROMs
This kernel will NOT work in Samsung Stock and other TW ROMs.
/* How-to-Install *\
*Download Kernel*
1. Go to recovery (TWRP recommend)
2. Flash Kernel
3. Reboot and enjoy
/* Incorporated SmartPack Features *\
Build from latest Lineage OS source code.
Built using latest GCC-8.x.
Anykernel for compatibility with maximum devices.
Linux Kernel version is updated to 3.4.113
Kernel tweaker app recommend: SmartPack-Kernel Manager (Please note: official Kernel Adiutor is NOT fully compatible with this kernel).
Added features include...
CPU voltage control
CPU Freq Gov: INTELLIDEMAND, INTELLIACTIVE, SMARTMAX, LIONHEART, NIGHTMARE, ADAPTIVE, ALUCARD, ZZMOVE, etc.
(for those who want to use zzzmove, I strongly suggest to carefully read this forum post by @Saber)
CPU hotplugs: Lazyplug, Alucard, and mako hotplug.
Full control over AC, USB and Wireless charging rate in SmartPack-Kernel Manager (Default charging rates: AC: 1800 mA; USB 700 mA; Wireless: 900 mA).
Boeffla Sound to control speaker and headphone volume.
(for official KA users, follow these instructions by @Exzu to create respective custom controllers for Boeffla Sound and Fast Charge.)
Adreno_Idler
CPU Input boost (configurable in SmartPack-Kernel Manager)
IO schedulers: FIOPS, SIO, VR, ZEN, FIFO, TRIPNDROID.
TCP congestion algorithms: Westwood, reno, cubic etc.
FRandom
Dynamic sync control 2.0
Boeffla Generic Wakelock Blocker
268 MHz CPU underclocked frequency cycle
Additional 27 MHz GPU frequency step (idle frequency)
KCAL v2
SELinux "Enforcing" by default (can be switched to "Permissive" in SmartPack-Kernel Manager)
a lot more...
/* Incorporated Boeffla-Venom Features *\
*Enable OC to 2995:
-DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. (I AM NOT RESPOSIBLE FOR YOUR DEVICE)
*Fast Charge
*ZZmoove adjusted to acommodate Overclocking (Thanks to Legitsu)
*Tweak bandwith on higher OC steps (Thanks to ktoonsz)
*Deadline I/O Tweaks (Ktoonsz)
*Fix memory leak with sysfs when stats table are freed (Ktoonsz)
*Bump up Max Voltage (Adjusted for higher OC) (Ktoonsz)
*Dirty Writeback Tweaks
*Increased VM_MAX_READAHEAD to 512 (default)
*Increased default entropy levels (both read and write)
*Optimized Kernel Samepage Merging
*QuickWakeup (Thanks CrazyGamer)
*PowerSuspend (Thanks Faux123)
*Cortex_A15 Optimizations (Fusion-Rom Dev Team)
*Slimbus Overclock (Ktoonsz)
*Slimbus Optimized Overclocking Of Master Component (CrazyGamer)
*VFP Tweaks (Ktoonsz)
*EXT4 Tweaks(Ktoonsz)
*GPU Overclocked up to 657 (Ktoonsz)
*Disable Swap Readahead
*Increase Maximum Swappiness
*Kernel mode neon (ShinySide)
*Disable Direct Reclaim File Pages
*Enable Unaligned Capability For ARM (CrazyGamerGR)
*Update min-default adreno frequency to be 200 MHz (kholk)
*Fixed memory entry leak when calling Adreno Convertaddr (Shubhraprakash Das)
*Changed clock rates to 19.2 MHz (Faux123/Qualcomm)
*Optimized Sched/Fair a bit (Faux123)
*Applied many new compiler optimizations (Synergy kernel Team & Decimalman)
*Zswap: Uses LZ4 now (if available)
*Support for LZ4-compressed kernel
*Fix memory leak in Mass Storage
*Added back Intellithermal V.2 Thermal Engine (for those who prefer it)
*Modified LowMemoryKiller (fbs)
/* Downloads Can Be Found Here *\
https://app.box.com/s/nx7nuf7vb2eubd5sfrr5rerjsatcp42i
/* Special note to Korean S5 users *\
(Thanks to sunilpaulmathews defconfig files)
Flashing this kernel after AOSP/LOS based Oreo/Pie ROMs originally build for the klte (SM-G900F) variant SHOULD allow the use of those ROMs on SM-G900S/K/L.
/* Acknowledgements *\
@haggertk for LineageOS for Galaxy S5
@Lord Boeffla
@franciscofranco
@Sultanxda
@arter97
@faux123
@CrazyGamerGR
@Saber
@nathanchance
@ZaneZam
@osm0sis for AnyKernel project
@Grarak for Kernel Adiutor
@sunilpaulmathew
@justjr for SmartPack efficiency profile
@ktoonsez
@KazuDante
@fbs
@kholk
@decimalman
@Synergy Kernel Team
Many other XDA developers
XDA:DevDB Information
Ares-Kernel, Kernel for the Sprint Samsung Galaxy S5
Contributors
The~Skater~187, sunilpaulmathew
Source Code: https://github.com/187MoD/Ares-Kernel
Kernel Special Features: Boeffla-Venom + SmartPack Kernels
Version Information
Status: Beta
Current Beta Version: Beta-v1.6
Beta Release Date: 2019-02-15
Created 2019-02-15
Last Updated 2019-08-26
***Ares Kernel Changelog***
~~~~~Beta-v1.7~~~~~
*Up-to-date with Lineage-OS source as of 01.01.2020
*Update Intelli-plug to version 3.9 (Compliments of Pascua28)
*sound: Compiled with -Os optimization (Compliments of Pascua28)
*A few other optimizations
~~~~~Beta-v1.6~~~~~
*Up-to-date with Lineage-OS source as of 08.25.2019
*Compiled using Bleeding-Edge Toolchain 9.2
*Cortex A-15 MSM-memutil optimizations for better memory performance
*GPU compiler optimizations
*Enable: Frontswap
*Enable: Runtime compcache
*Removed un-supported SOC features (Thanks pascua28)
*Fix possible memory leak in slub.c (Thanks pascua28)
*Add Missing xor-neon file
*Compiled with many new compiler optimizations
*Plus more
~~~~~Beta-v1.5~~~~~
*Up-to-date with Lineage-OS source as of 07.15.2019
~~~~~Beta-v1.4~~~~~
*Up-to-date with Lineage-OS source as of 05.27.2019
*Compiled with "Bleeding-Edge-Toolchain" 9.1
*Compiled with 03 compiler optimizations
~~~~~Beta-v1.3~~~~~
*revert: disabled "CAF" cpu policy save code (Fixed cores not scaling properly)
*MSM Limiter updated
~~~~~Beta-v1.2~~~~~
*Up-to-date with Lineage-OS source as of 03.19.2019
*reverted to stock Lineage-OS LMK (Low Memory Killer)
*bumped OC up to 3072 -DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. I AM NOT RESPONSIBLE FOR YOUR DEVICE!)
*bumped up voltage overhead to hopefully help stabilize new OC step
*added Intelliplug_hotplug driver (Now default hotplug service)
*added Touchboost driver (adjusted for 3072 oc)
*added MSM CPU Limiter (adjusted for 3072 oc)
*enabled Arch Power
*added the ability to Toggle Arch Power And Sleepers (compatible with SmartPack Manager)
*disabled "CAF" cpu policy save code (Faux123)
*added msm_mem_utils for added memory performance
*disabled constant spam in dmesg from 'undefined instruction' print statement in traps.c
*ZZmoove: adjusted to acommodate Overclocking to 3072
*added Boeffla-compiled In-Kernel Busybox
*some other things
~~~~~Beta-v1.1~~~~~
*Up-to-date with Lineage-OS source as of 03.02.2019
*Ares-Kernel boot script: update default profile settings (credits: justjr)
*import Core Control fix (sunilpaulmathew)
*import "Hotspot" fix (sunilpaulmathew)
*added a compatible version of "Tuned" LowMemoryKiller (fbs)
*added support for lz4 compressed kernel
*added some compression tweaks to help with boot performance
*driver/char: add missing frandom commits
*fs/sdcardfs/mmap.c: add AIO optimization flag compatibility fix up
*kernel/power: add missing quickwakeup commit
*Optimized ARM RWSEM Algorithm (Faux123)
*Tuned thermal management a bit
*Some other stuff
~~~~~Beta-v1.0~~~~~
-Initial Merge of SmartPack/Venom Sources
*Synced With latest LineageOS Sources as of 02.13.19
*Built with Latest 8.2.1 toolchain using SunilPaulMathews build Framework
*Compatible With Kernel Auditor & Should Be Compatible SmartPack-Kernel Manager
*Enable OC to 2995:
-DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. I AM NOT RESPOSIBLE FOR YOUR DEVICE)
*Boeffla Sound
*Fast Charge
*ZZmoove: adjusted to acommodate Overclocking (Thanks to Legitsu)
*Enable 268 mhz underclock (Thanks to SunilPaulMatthew)
*Tweak bandwith on higher OC steps (Thanks to ktoonsz)
*Tweak deadline: Allow 0ms deadline latency, increase the read speed (Ktoonsz)
*Set audience sleep delay to 0 to fix delay upon making phone calls
*Async I/O latency to a ssd greatly increased (34% gain,kleikamp & Ktoonsz)
*Fix possible memory leak with sysfs when stats table are freed (Ktoonsz)
*Bump up Max Voltage (Adjusted for higher OC) (Ktoonsz)
*Dirty Writeback Tweaks
*Increased VM_MAX_READAHEAD to 512
*Increased default entropy levels (both read and write)
*Optimized Kernel Samepage Merging
*QuickWakeup (Thanks CrazyGamer)
*PowerSuspend (Thanks Faux123)
*Cortex_A15 Optimizations (Fusion-Rom Dev Team)
*Add Missing Graphite Define (Ktoonsz)
*Slimbus Overclock (Ktoonsz)
*Slimbus Optimized Overclocking Of Master Component (CrazyGamer)
*VFP Tweaks (Ktoonsz)
*EXT4 Tweaks(Ktoonsz)
*GPU Overclock up to 657 (Ktoonsz)
*Disable Swap Readahead
*Boeffla wakelock blocker (Thanks to sunilpaulmathew & franciscofranco)
*Increase Maximum Swappiness
*Kernel mode neon (ShinySide)
*Disable Direct Reclaim File Pages
*Enable Unaligned Capability For ARM (CrazyGamerGR)
*Update min-default adreno frequency to be 200 MHz (kholk)
*Fixed memory entry leak when calling Adreno Convertaddr (Shubhraprakash Das)
*Change clock rates to 19.2 MHz (Faux123/Qualcomm)
*Optimize Sched/Fair a bit (Faux123)
*Applied many new compiler optimizations (Synergy kernel Team & Decimalman)
*Zswap: Uses LZ4 now (if available)
*Support for LZ4-compressed kernel
*Fix memory leak in Mass Storage
*Alucard, LazyPlug & Mako Hotplugging
*Enabled VNSWAP
*Added back Intellithermal V.2 Thermal Engine (for those who prefer it)
*Modified LowMemoryKiller (fbs)
# All Changes
# Signed Off
# By
# The~Skater~187
Reserved
~~~~~~~~~~~ Please note~~~~~~~~~~~
If you need support, please supply the following or support will not be given:
*Device Variant
*Current Rom & Android Version
*Bootloader & Baseband version
*Recovery & Version
*Recovery Log
I can't help if the only details given are "It didn't work" or "I can't flash this".
One More For Good Measure
YES.!!!!
sdfat code have syntax errors, aren't even compiling here.. humm
ok, fixed it and stealed it
Thanks for ur good kernel. Flashed on haggertk android pie no problem so far. At first I was getting random reboots,it caused by my magisk modules. I disable them and the problem fix. Thanks again.
LKT magisk module on this kernel cause random reboots.
Thanks for your work
So I popped over to this thread you linked to from the Venom thread and want to make sure I'm clear. This kernel (Ares-Kernel) should not be used on a Resurrection Nougat based ROM? I think that Resurrection Nougat ROM is a Lineage 14 based ROM, correct? Or even though it is Lineage 14 based, can the Areas-Kernel still be used because it is based off Lineage.
Thanks for any clarification. Left this post in other thread to just to make sure I got it in right spot. Disregard which ever one is posted in wrong spot. Thanks.
awesome dude!!! thank you so much! i'm really glad that someone continues the smart-pack kernel!
:laugh: big, Big, BIG Thank you @The~Skater~187! Really appreciate your effort and dedication in helping to keep this old phone alive and competitive! :highfive:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as the tunable io_is_busy 0 to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
justjr said:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
Click to expand...
Click to collapse
I do apologize about the credit issue, I thought I had put your name in the acknowledgment section right before ktoonsz last night, as I noticed your name on a few of the files in the RamDisk. I will definitely straighten that out and thank you for pointing that out. You are correct, I so far have just synced SmartPack source, then started applying things from my other kernel for now. I wanted to get something up-to-date and stable out for you guys before I started diving deeper into other kernel related things.
As for the rest of your suggestions, I will look into them for sure. Feel free to p.m. me with any thoughts or other suggestions.
Sent from my kltespr using Tapatalk
The~Skater~187 said:
I do apologize about the credit issue, I thought I had put your name in the acknowledgment section right before ktoonsz last night, as I noticed your name on a few of the files in the RamDisk. I will definitely straighten that out and thank you for pointing that out. You are correct, I so far have just synced SmartPack source, then started applying things from my other kernel for now. I wanted to get something up-to-date and stable out for you guys before I started diving deeper into other kernel related things.
As for the rest of your suggestions, I will look into them for sure. Feel free to p.m. me with any thoughts or other suggestions.
Sent from my kltespr using Tapatalk
Click to expand...
Click to collapse
Many thanks!
On other news, I was getting some random reboots, and found out that it was because of my undervolt settings. It's super weird, because they never gave me any problems since 3~4 months with the smartpack kernel, and it should be a setting particular to my specific device/cpu, and have the same limits across any kernel. I used the same across lots of roms, and different versions of smartpack, for nougat, oreo and pie, so, I hope you can see why I find this very weird.
But, I don't know if it's actually a 'bug', I will find some time to fine tune it, raise some voltages to see where I can go with Ares kernel without crashing. For now I'm using the default voltages.
justjr said:
Many thanks!
On other news, I was getting some random reboots, and found out that it was because of my undervolt settings. It's super weird, because they never gave me any problems since 3~4 months with the smartpack kernel, and it should be a setting particular to my specific device/cpu, and have the same limits across any kernel. I used the same across lots of roms, and different versions of smartpack, for nougat, oreo and pie, so, I hope you can see why I find this very weird.
But, I don't know if it's actually a 'bug', I will find some time to fine tune it, raise some voltages to see where I can go with Ares kernel without crashing. For now I'm using the default voltages.
Click to expand...
Click to collapse
I did do a bit of an overhaul on the voltage table when I added the higher oc steps, due to the fact that on my other kernel lower voltages stock we're causing problems and random freezes.
Sent from my kltespr using Tapatalk
Yeah, I'm sure you know, undervolting need to be done step by step, making sure the lowest you can go, device specific, so risking repeating myself, same voltages should probably 99,99% of the time works across any kernel/rom on a given device. I don't think it is the undervolt anymore.
It took a while but I still had some reboots with default voltage, once I was finally able to press up and home right after it, so it rebooted directly to TWRP and I copied the last_kmsg, it's attached, all configs were on default. I hope it helps to find out what it may be.
I'm back on smartpack for now, cause the same setup and profile runs without no problems, so I think it should not be a problem just on my end, is it? Anybody else?
Fun fact, I was are able to dirty install smartpack kernel over ares and vice-versa and it detected and updated itself without any problems.
I'm able to go kinda low here with no crashes:
660
670
680
690
700
710
720
730
745
750
775
795
825
865
925
965
990
1005
1035
1060
@The~Skater~187 edit: oh, I just noticed, there's no option to input 268 MHz voltage. My voltages are getting placed on the wrong frequency because of that, found the problem!
I recovered the backup I just made before installing the kernel, I had installed the shushified bootleggers 3.0 on top of the unshushified 3.0, they are the same rom except for official (shushified) status, but anyway, that may be the cause of some of my problems, adding up to the 268 missing voltage that was overlooked by me.
After that I installed Ares kernel again with no undervolt and gone to sleep. Woke up today, and no reboots, then I was trying to test undervolting it and found out about the missing 268 voltage, so every previous voltage I used was getting used on 1 clock step above, so, not enough power for sure.
Just put my exactly same volts on their correspondent freq and no reboots until now!
It also seems that Core Control is staying enabled and VD Restrictions is disabled correctly now too. So, if you experience the same you may disregard it as well.
Thanks for this!!
Great so far, this with Pie ROMs is the best battery life I've had since stock.
4-5 hours sot, 7h active, 12h idle..(gsam stats) on this original 2800mah. I've gone from 4-5 charges a day to 1-2.
And kernel brightness control keeps the flickers away.
Edit: did notice both vdd and core thermals being active, didn't cause any overheating/reboots (i often run cpu info as overlay) but I stuck with core control only to be safe. It doesn't stick after reboot.
S5 klte
Latako said:
Edit: did notice both vdd and core thermals being active, didn't cause any overheating/reboots (i often run cpu info as overlay) but I stuck with core control only to be safe. It doesn't stick after reboot.
S5 klte
Click to expand...
Click to collapse
Yeah, after some further analysis, I came to find out exactly the same.
After a reboot both VDD and CC come back up, and I have to do a little dance, like, disable vdd and cc, enable intellithermal, then enable only cc, or something like that, then it will stick with only cc until the next reboot.
Ok, so I decided I'm going keep an "unofficial" SmartPack kernel going (nothing more than source updates will be applied) as well as my off shoot kernel project. I will have it available for you guys tomorrow evening.
Sent from my kltespr using Tapatalk
justjr said:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as the tunable io_is_busy 0 to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
Click to expand...
Click to collapse
So is it possible to use your profile without any errors?