{
"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"
}
High performance & power saving tweaks for all devices (THAT ACTUALLY WORK)
Introduction
LKT is a cumilation of different strategies that target certain kernel settings. What makes this special and stand out from the crowd is being universal and device specific at the same time. And it's also BS free. Using simple functions LKT detects the hardware of your device then it applies the corresponding changes. It does support all mainstream platforms including Snapdragon, Kirin, MediaTek etc. covering hundreds of devices.
These tweaks have been tested and can stand up to 12-14H of SOT with no-compromise on performance all smooth as a baby's bottom.
However, it should be noted that this does not apply to gaming, facebook, snapchat, instagram and heavy camera usage ...etc
Nothing can be done for anything that is an automatic battery killer and forces maximum resources usage at all the time.
How does it work?
LKT aims to achieve a balance between power consumption and performance. Compared to tuning the parameters manually, LKT adopts Project WIPE open source interactive parameters for all mainstream SOCs that are generated via machine learning AI and can adapt to multiple styles of workload sequences. This idea is similar to EAS, which takes into account both performance and power consumption costs through power consumption models and workload sequence. But obviously, EAS has a much lower response time and replaces tuning with decision logic. In addition, it also includes other parameter tuning, such as HMP scheduler parameters, virtual Memory, GPU, IO blocks tuning, and doze rules to unify the rest of the kernel parameters for a more consistent experience.
LKT also supports schedutil and other EAS governors in devices like the Pixel 2. Unlike interactive, schedutil does not provide a wide range of tuning parameters but there are some workarounds. In Snapdragon 835 for example depending on what profile is selected, LKT limits the maximum frequency of big cores accordingly because big clusters power efficiency of SD835 dramatically decreases above 2 GHz, as a trade of losing 15% performance, improving power consumption by 40% or more is a much better deal.
Features
Multi-Profile
Improved smoothness & battery life
Advanced interactive governor tuning (Project WIPE)
EAS devices Support
RAM management enhancements
IO blocks enhancements
Enabled & configured wakelock blocking
Disabled a excessive logging at kernel level (Improves battery life as well as performance)
Other miscellaneous adjustments to enhance power efficiency
Profiles
Battery - Can acheive ~2 hours or more longer on-screen battery life, may lag in some scenarios where the load fluctuates dramatically.
Balanced - Can acheive ~1.5 hours or more longer on-screen battery life with little performance compromise .(Recommended)
Performance - Can acheive ~1 hour longer on-screen battery life , same as balanced profile with more responsiveness. .
Turbo - Ideal for intense high demanding tasks, where the load drastically fluctuate (not necessarily in games) . Will ensure reducing lags by ~90% for no more than ~20% increase power in consumption.
Click to expand...
Click to collapse
Requirements
Magisk or SuperSU or init.d support
Busybox
Installation
Flash in TWRP or Magisk manager
Follow the given instructions
Reboot
Read the FAQ from here or here before asking anything. (Regularly updated)
Credits
Code:
Project WIPE contributors [URL="https://github.com/yc9559/cpufreq-interactive-opt/tree/master/project/20180603-2"]Github[/URL]
yc9559 - @CoolApk
cjybyjk - @CoolApk
[U]Special Thank[/U]
Zackptg5 & ahrion - Unity template
topjohnwu - Magisk
osm0sis - Busybox
Contributors
@korom42
Sources
Original XDA thread
Github
License
Licensed under the GNU General Public License v3
Donate to support further LKT development
FAQ(frequently asked question)
Also check for FAQ here (More often updated)
• How do I apply these tweaks?
Simply flash LKT zip in recovery or Magisk app then reboot.
• Do I have to be rooted?
Yes, LKT needs either Magisk or SuperSU or init.d support.
Beware that LKT is a collection of advanced tweaks that act on kernel level. If you don't know how it works, then please try this at your own risk. I won't be responsible for any damage or loss. Never forget to make backups.
• What are the available profiles ?
Battery: Can acheive ~2 hours or more longer on-screen battery life, may lag in some scenarios where the load fluctuates dramatically
Balanced: Can acheive ~1.5 hours or more longer on-screen battery life with little performance compromise (recommended)
Performance: Can acheive ~1 hour longer on-screen battery life , same as balanced profile with more responsiveness
Turbo: Ideal for intense high demanding tasks, butter smooth gaming for a long periods. Will ensure reducing lags by ~90% for up to ~20% more power consuption than stock.
Click to expand...
Click to collapse
• How to switch between profiles?
Method 1
To access the command controls screen using terminal type
Code:
su
lkt
Then follow the instructions
Method 2
Now you can also you run these commands to directly switch profiles (must run with root permissions)
Code:
lkt 1 (for battery profile)
lkt 2 (for balanced profile)
lkt 3 (for performance profile)
lkt 4 (for turbo profile)
Method 3
You can also to re-flash the module twice to change the profile but you will have to reboot using this way.
• Can I use LKT with another MOD ?
** Compatibility list** You can still these mods since they do not affect LKT parameters.
Universal XML Patcher
GMS Doze
ForceDoze, Naptime, Greenify, Amplify, Power Nap
MCS (Magic charging switch) & Charging control mods..etc
BlackenedMod (Pixel 2)
** Incompatibility list ** Do not use similar mods with LKT, here is a list of some known MODs that will interfere
AKT (Advanced Kernel Tweaks)
Spectrum
Helix Engine
L-Speed
GovTuner
Every bullsh*t placebo MOD like : CrossBreeder, NFS, KITANA, FeraDroid ..etc
Heavily tweaked ROM such as : xXx (OP6/6T)
• Will this work on my ROM & Kernel ?
It should work on almost every Stock, AOSP or Lineage based ROM & Kernel
The only problem is with heavily tweaked ROMs, they can interfere with LKT.
• Will this work on my device?
This mod support a large list of devices you can check the compatibility list.
• How to make sure that LKT is working ?
Using a file explorer with root access check LKT logs in the location below ( share & upload yours in case of having troubles)
Code:
/data/LKT.prop
•I cannot find or open LKT logs
To properly open LKT.prop you need a file manager with root access your app may not be working correctly. Here's some apps I can recommend
MiXplorer
FX File Explorer + ROOT addon
You can also access your alogs using terminal by running this code
First type su then copy and past this line :
Code:
cat /data/LKT.prop
• My logs are incomplete
Make sure you are using the latest version of Magisk 18.0+
Install busybox by @osm0sis
• My device Lags or not longer smooth What do I do?
This can happen and it's a normal thing. As I have stated before, all these tweaks have been done for fit certain usage which might not be the same as yours. Because this, your device may lag in some scenarios under heavy loads (If you are experimenting huge lags, you have done something wrong). And yes, this can be fixed. We have a couple of ways of fixing it. First of all if you are using battery profile try switching to another one, if this doesn't help you consider the following steps :
Do a factory reset
Get rid of unnecessary background apps
Try a different ROM or Kernel
Try another profile
• These settings don't work & I'm not getting great screen on time
Keep in mind these tweaks have been tested on certain scenario that might not the same as yours, read the introduction in OP to understand more about this. However if you are getting worse results than before you are probably doing something wrong and here are some recommendations for you
Do a factory reset
Get rid of unnecessary background apps
Try a different ROM or Kernel
Try another profile
• How to update LKT?
Dirty flash the new zip or install the update via Magisk manager and it will automatically upgrade.
• How to uninstall LKT?
Flashing the module for the second time will remove LKT. You can also remove it from Magisk app.
Compatibility
Snapdragon 845
Snapdragon 835
Snapdragon 820-821
Snapdragon 810-808
Snapdragon 801-800-805
Snapdragon 660
Snapdragon 652-650
Snapdragon 636
Snapdragon 625-626-630
Snapdragon 615-616
Snapdragon 450
Snapdragon 435
Snapdragon 430
Snapdragon 425
Snapdragon 410-412
Snapdragon 400
Exynos 9810 (Samsung)
Exynos 8895 (Samsung)
Exynos 8890 (Samsung)
Exynos 7420 (Samsung)
Kirin 970 (Huawei)
Kirin 960 (Huawei)
Kirin 950-955 (Huawei)
kirin 650-655-658-659 (Huawei)
Helio x20-x25 (MT6797-MT6797T)
Helio x10 (MT6795-MT6795T)
Helio P10 (MT6755)
Intel atom Z3560-3580
Click to expand...
Click to collapse
**Please note that even if your device isn't listed here some parameters may still apply
Changelog
Code:
v1.5.2 (11/03/2019)
- Disabled GPU thermal restrictions on Mediatek SoCs
- Various fixes and CPU enhancements for Mediatek SoCs
- Removed zRAM (SWAP) configuration
- Other minor changes & enhancements
- Bug fixes
v1.5.1 (07/03/2019)
- Bug fixes
v1.5.0 (06/03/2019)
- EAS fixes and performance enhancements
- GPU parameters adjustements
- Disabled GPU thermal restrictions on Snapdragon SoCs
- Adreno Idler tweaks enhancements
- Storage scheduler enhancements
- Memory management enhancements
- Various zRAM & SWAP optimisations
- Other minor changes & enhancements
- Bug fixes
v1.4.9 (09/02/2019)
- Memory management adjustments
- Fixed interactive governor parameters being overwritten by system after a while for some devices
- Added back deep-sleep enhancements props
- SWAPs/zRAM are no longer disabled
- Auto-detect existing profile when upgrading (user interaction is not needed anymore)
- Minor bug fixes
v1.4.8 (05/02/2019)
- Increased delay after boot
- Bug fixes
v1.4.7 (04/02/2019)
- EAS profiles fixes
- CPU boost fixes for some devices
- Memory management enhancements
- Removed any deep-sleep related tweaks
- Bug fixes
v1.4.6 (02/02/2019)
- Important bug fixes
- zRAM is not tweaked anymore and left for the kernel (only disabled for devices +6GB RAM)
v1.4.5 (01/02/2019)
- Re-worked EAS profiles
- Prefer schedutil on EAS kernels
- Added CPUSET optimizations
- Added schedtune optimizations
- Added control groups (CGroups) optimization
- Enabled zRAM for 4GB RAM devices
- Enabled & adjusted Low memory killer
- IO block tuning enhancements
- FileSystem (FS) enhancements
- Enabled Fast Dormancy (may help with cellular network idle drain)
- Major bug fixes
v1.4.4 (19/01/2019)
- Unity template update 3.2
- SoC detecion enhancements
- Increased delay at boot before applying tweaks to 1 min
- Minor enhancements
- Bug fixes
v1.4.3 (16/01/2019)
- Unity template update v3.1
- Fixed changing LKT profile not sticking after reboot
- Added ability to change profiles with simple commands (useful for tasker)
```
lkt 1 : for battery profile
lkt 2 : for balanced profile
lkt 3 : for performance profile
lkt 4 : for turbo profile
```
- EAS fixes
- Improved compatibility for custom kernels
- Removed Low Memory Killer tweaks
- Swapping is no longer disabled for devices less than 4GB RAM
- Bug fixes
v1.4.2 (01/01/2019)
- More Bug fixes
v1.4.1 (01/01/2019)
- Fixed some bugs after last update
v1.4.0 (01/01/2019)
- SoC detecion enhancements
- Bug fixes
v1.3.9 (29/12/2018)
- Added command line controls
- Now LKT perefers interactive if kernel has both schedutil & interactive
- Less aggressive LMK
- Crash fix for some devices
- Other minor changes & bug fixes
To access the new commands screen using terminal type
```
su
lkt
```
Then follow the instructions
v1.3.8 (28/12/2018)
- SoC detection issues fixes for samsung & other devices
v1.3.7 (27/12/2018)
- Fixed system crash & missing logs after last update
- Other minor changes
v1.3.6 (27/12/2018)
- Fixed soc.txt file not being created when SoC detection fail
- Added new wakelocks to block
- Adreno Idler parameters changes
- Minor enhancements
- Bug fixes
v1.3.5 (26/12/2018)
- SoC detection issues fixes
- Reduced entropy values
- Minor enhancements
- Bug fixes
v1.3.4 (24/12/2018)
- Added support for snapdragon 4xx series
- Added support for Helio P10 (MT6755), kirin655, kirin658, kirin659
- Fixed LTE Signal bug
- Fixed some parameters not being applied
- Fixed detection bug for snapdragon 660
- Added device support check in logs
- Unity template update 2.2
- Script enhancements
- Bug fixes
v1.3.3 (23/12/2018)
- EAS parameters adjustments
- Reverted HMP scheduler changes
- Fixed RAM capacity & CPU frequency not displayed properly in LKT.prop
- Crashes bug fix
- Scrolling bug fix
- Crashing apps bug fix
- Minor enhancements
- Bug fixes
v1.3.2 (22/12/2018)
- Minor installation bug fixes
v1.3.1 (22/12/2018)
- EAS tuning is back for more devices (manual parameters - not WIPE)
- EAS parameters adjustments
- HMP scheduler adjustments
- Updated RAM detection method
- Memory management fixes
- LMK enhancements
- Added Lazyplug tunning
- Removed busybox check
- Module template updated to latest UNITY 2.1
- Module installation fixes
- Minor enhancements
- Bug fixes
v1.3.0 (19/12/2018)
- Fixed hardware auto-detection fail after last update for some devices
- Added support for sultanxda cpu boost implementations
- Updated to latest UNITY template 2.0
- Bug fixes and refinemetns
v1.2.9 (18/12/2018)
- Important chip detection fixes
- Improved swap detection & removal
- Bug fixes
v1.2.8 (18/12/2018)
- Bug fixes for manual chip detection workarround
v1.2.7 (18/12/2018)
- Minor fixes
v1.2.6 (17/12/2018)
- Added manual workarround for devices with unrecognized chip (Huawei,Xiaomi etc..)
- Removed EAS support (except sd845) untill further notice (too experimental)
- Corrected SD845 configs
- Agressive tunded LMK for Turbo profile for better gaming experience
- Fixed Termux app conflicts
- Bug fixes and refinemetns
v1.2.5 (17/12/2018)
- Added Performance & Turbo profiles
- Added partial support (balanced profile only) for exynos9810, kirin650, sd615
- Fixed battery drain for EAS devices
- Fixed some devices not being recognized (again)
- Fixed some bugs with low RAM devices
- Fixed RAM capacity not being displayed correctlly
- Script refinements
- A lot of bug fixes
v1.2.4 (16/12/2018)
- Fixed connectivity issues for some devices
- Improved SOC chip recognition for some devices
- Other minor bug fixes & refinements
Thanks to @pKrysenko & all telegram group members for testing
v1.2.3 (15/12/2018)
- Minor bug fixes
v1.2.2 (14/12/2018)
- EAS parameters enhacements
- Memory tuning enhancements
- Added support to SD615/SD616
- Changed hardware detection method
- I/O scheduler changes
- Removed forced doze for GMS & ril services
- Improved scrolling & FPS in applications
- Added detailed battery health check
- Other minor bug fixes & improvements
v1.2.1 (07/12/2018)
- Fixed a bug that makes governor parameters not stick after a while
- Fixed a bug where CPU is not recognized correctly (Improved SoC detecting)
- Other minor bug fixes & improvements
v1.2 (05/12/2018)
- Added missing cpu boost for some SoCs on balanced profile
- Improved swap detection & disabling (again)
- Reviewed & removed some stuff
- Other minor bug fixes & improvements
v1.1 (04/12/2018)
- Fixed a bug where chip name in upper case isn't recognized
- Swap partitions detecting improvements
- Some small but important script code fixes
Thanks to whalesplaho @XDA for testing and discovering this
v1.0 (04/12/2018)
- First release
Downloads
• Google Drive
You can also download LKT from Attachments or Magisk repo
Beta testing & Support
• Join our telegram chat
Will this change any of my settings in kernel auditor and HEBF optimizer? Cause you said don't use with L speed and L speed can change some of my kernel parameters in kernel auditor and HEBF can if not setup the right way.... Does this module have a U.I
PoochyXXX
PoochyX said:
Will this change any of my settings in kernel auditor and HEBF optimizer? Cause you said don't use with L speed and L speed can change some of my kernel parameters in kernel auditor and HEBF can if not setup the right way.... Does this module have a U.I
PoochyXXX
Click to expand...
Click to collapse
It's better to not use any other mods with this so they won't conflict, if your device is supported you won't need anything else
This module does have a UI, to access it via terminal type su then lkt and follow the instructions. Please refer to the help section next time before asking anything.
korom42 said:
It's better to not use any other mods with this so they won't conflict, if your device is supported you won't need anything else
This module does have a UI, to access it via terminal type su then lkt and follow the instructions. Please refer to the help section next time before asking anything.
Click to expand...
Click to collapse
Alright will do
PoochyXXX
Unistaller zip.......?
Plz
Sent from my GT-I9500 using Tapatalk
nomigujjar said:
Unistaller zip.......?
Plz
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Read the FAQ
Hello,
My device is Samsung Note 4 - SM-N910F.
I'm not on Samsung but on AOSP (6.0.1 - because of some outdated xposed mods) as I prefer stock, bloatware-less, android ROM.
The thing is, battery life has always been worse than original Samsung ROM, mainly because of doze not being strict enough, and lack of wakelocks optimisation.
Naptime, Greenify and Amplify helped me reducing those issues, along with Kernel Adiutor underclock increasing battery life. And Icebox for freezing battery using when screen is turned off.
Now comes your work, I flashed your zip. I was a bit skeptical of what it could make to my OS to magically improve battery life... But I have to be honest, it improved blocking those ridiculous wakelocks when my phone is idle.
See by yourself : 0.2% of battery during 6h sleep (airplane mode on, because radio waves). When it is usually 0.8% to 1%. Ofc when phone is used like using camera, it won't do magic over battery, but those unnecessary wakelocks event seems to be fixed.
So, yes. Thank you, thank you very much.
I got a weird bug on the poco f1 using lkt (mostly balanced profile) when I charge my battery indicator get stuck to 75%. However it still charge since it rest a bunch of time stuck to 75%
Rom xiaomi.eu
Kernel Extreme kernel v9
Hello. I installed the zip without problems and restarted my phone. Nowhere, however, do I see something of cloudy. Neither at Mtweaks or in the info settings themselves. How do I know that it works now? And how can I change the profiles?
cosmobi said:
Hello. I installed the zip without problems and restarted my phone. Nowhere, however, do I see something of cloudy. Neither at Mtweaks or in the info settings themselves. How do I know that it works now? And how can I change the profiles?
Click to expand...
Click to collapse
Read the F.A.Q
Does this mod stay active after each reboot? Or do I've to select each profile on reboot
fi5z.x9 said:
Does this mod stay active after each reboot? Or do I've to select each profile on reboot
Click to expand...
Click to collapse
Yes it does stay active by saving the selected profile even after reboot.
Would you consider LeeDroid a heavily tweaked ROM, and one that would interfere with LKT? I removed all L-Speed settings, and I'm getting incredible performance yet slightly less SOT. I'm willing to make the sacrifice, unless you would advise against using this MOD with LeeDroid. Thanks in advance for any response, and awesome work!
How does this mod compare to the NFS-Injector module? Can they be used safely together
Hi, how do I change profile.. I am on balanced need to go to performance
I tried reinstalling but while reinstalling it automatically detected device in balanced and didn't ask me to change
Harshdeepagrawal said:
Hi, how do I change profile.. I am on balanced need to go to performance
I tried reinstalling but while reinstalling it automatically detected device in balanced and didn't ask me to change
Click to expand...
Click to collapse
MDV106 said:
How does this mod compare to the NFS-Injector module? Can they be used safely together
Click to expand...
Click to collapse
If you took 10 seconds to read the FAQ you wouldn't have to ask these questions.
https://telegra.ph/LKT---FAQ-03-25
korom42 said:
If you took 10 seconds to read the FAQ you wouldn't have to ask these questions.
https://telegra.ph/LKT---FAQ-03-25
Click to expand...
Click to collapse
Thanks for sarcasm
korom42 said:
If you took 10 seconds to read the FAQ you wouldn't have to ask these questions.
https://telegra.ph/LKT---FAQ-03-25
Click to expand...
Click to collapse
Im glad I didnt, this module is useless anyway.
MDV106 said:
Im glad I didnt, this module is useless anyway.
Click to expand...
Click to collapse
Right.. it clearly is ??
Related
[KERNEL] [2.6.32.24] [HAVS] [BFS] [BFQ] KiNgxKernel #11/#11 "Con is an Artist"
I DO NOT have an HTC Evo, but would LOVE to have one for development, and am saving for one. Bear with me until then I just wanted to say thank you to the few who have donated. I am almost there, any help is appreciated!!! I plan to have my HTC Evo fairly soon
DO NOT FORGET TO READ THE ENTIRE POST ON MY SITE, THERE IS IMPORTANT INFO
So, just as the name implies, this is an Evo kernel with SVS (Static Voltage Scaling) & HAVS (Hybrid Adaptive Voltage Scaling.) A huge thanks to estes for the havs code and raven for being the first to implement it into the nexus kernel. What this does is provide SUPERIOR BATTERY life with stability to boot. Just flash the .zip in your favorite recovery image. Enjoy and post any bugs with a logcat please.
This is compatible with any 2.2 Sense ROM
Code:
Also, a little info on HAVS and AVS:
The purpose of HAVS is to minimize the power used by the CPU by determining
and setting the optimal voltage. At the same time, the maximum voltage by
which HAVS can scale to is fixed to a specified voltage depending on the
CPU frequency in order to prevent scaling to a higher voltage than what is
normally used at a specified voltage. The optimal voltage is actively determined
for each frequency and temperature. HAVS actively adjusts the CPU voltage as the
CPU frequency and temperature changes.
Code:
While we are at it, some info on BFS:
What is BFS(Brain **** Scheduler):http://ck.kolivas.org/patches/bfs/sched-BFS.txt
FAQS about BFS:http://ck.kolivas.org/patches/bfs/bfs-faq.txt
nugzo said:
I have full adb. I didnt have it when i upgraded from previous king kernels. Had to do a full wipe. Reinstalled rom and installed kernel before rebooting. adb works perfect. full access.
Click to expand...
Click to collapse
ENJOY!
Credits: Cyanogen, Netarchy (epson fps panel fix), toastcfh, ffolkes - all for bits of their code (see changelog), Koush for his any kernel .zip, AssasinsLaminent (nova fix), and most importantly, HTC for their kernel source
Download: CFS Kernel #11 & BFS Kernel #11[/URL] Date: 10/28/10 9:40 PM PST
If you Like my work follow me on twitter:
All my code is on github:
I am not responsible for anything that happens to your device
ChEeRs
BFS Changelog
Kernel #11
- HAVS is now OUT. We are not currently using it
- Using SVS for voltage regulation at the moment
- Battery life should be great now
- I forgot about an awful lot of longs and ints that will overflow on 32 bit now with u64 deadlines. Fix them.
- Add some macro tidiness
- Make sched_clock sanity checking robust and standardised, using jiffy
difference as upper limit, and use nominal 1us when difference cannot be
trusted.
- In layman's terms these are all MAJOR fixes to his BFS scheduler
- These fixes will provide a performance and stability boost
- Higher clockspeeds are more stable!
- More I will add
Kernel #10
- Performance boost!
- More stable due to BFS overhaul
- Patched up BFS scheduler to BFS 330
- Patched in *NEW* BFS TEST patch that applies over 330 (from CKolivas himself)
* Major overhaul of queued changes
* Micooptimise multiplications/divisions to be shifts where suitable
* Drop the "skip_clock_update" concept as we update the niffies each time we
update the rq clocks, thus we want to update it more often
* Add a local last_task variable to each runqueue which keeps a copy of the
last non-idle task that ran on this CPU. Use this value to determine that a
task is still cache warm on this CPU even if it has run elsewhere in the
meantime. This improves throughput on relatively idle systems with >2 logical
CPUs
* Change SCHED_BATCH tasks to refill timeslices and reset deadline every time
they're descheduled as they've been flagged as latency insensitive, likely
fully CPU bound tasks. This should decrease the impact running batch tasks
has on other tasks
* Bypass rechecking deadline when we know that prev will run again in schedule
* Change all deadline accounting to use nanosecond values
* Rework try_preempt
* MUCH MUCH more check my patch code if you please
- Voltage tweaks for stability
- Compiled with toolchain optimizations
- Neon optimizations this time around
Kernel #9
- Finally released
- Board files fixed to allow lower undervolt
- Undervolted to 825Mhz for safe frequencies
- Higher clockspeeds WILL be more stable now
- Compiled CIFS module per request
- Regulator tweaks
- Removed some bloat
- Now using ondemand governor by default, feel free to change it
- Battery charging tweaks (like my inc kernel)
- You guys are going to like this one
Kernel #8
- Reverted BFS Scheduler to 318
- Reverted GPU changes causing stutters
- Other minor fixes
Kernel #7
- Updated BFS Scheduler all the way up to 330
- MANY fixes to HAVS code *thanks for some of them netarchy*
- Regulator being properly used now
- Usleep fixes for sleep mode *via nnode*
- Longer battery life as a result of these major changes
- Volume boost tweaks
- Torture test disabled
- Torture test support disabled
- More I will add
Kernel #6
- Minor code cleanup
- Now undervolted to 825Mv! *Longer batter life*
- Ksgl tweaks for performance
- Higher clock speeds should now be more stable
- Wifi module tweaks
- Other things I will add
Kernel #5
- Rpc changes/tweaks
- V4L2 code disabled now for media interface
- Vmalloced tweaks via @cyanogen *PERFORMANCE BOOST*
- Tweaks for stability
- More I will add
Kernel #4
- BIG update
- Code cleanup
- Undervolted even more (Battery life is LONG)
- Compiled with neon optimizations
- Conservative governor threshold tweaked (via netarchy)
- Conservative Governor sampling rate tweaked per user request
- GPU edits for performance
- 5MB of memory reserved for the Adreno GPU
- Kernel will boot faster as a result of "set read ahead" changes
- Various wifi module tweaks
- Packet Filtering set to turn off after 1s
- Bluetooth sleep bug fixed *via kmobs via kernelzilla*
- More I will add
Kernel #3
- Added BFQ I/O Scheduler
- Default scheduler is bfq
- Fixed atomic functions in bfq *thanks cyanogen and co*
- Cleaned up/removed unneeded code
- HAVS is still included and functioning
Kernel #2
- Updated BFS Scheduler all the way up to 318
- Manual patches made by me to successfully get it working 100%
- Minor bug fixes
- Things I'll add
Kernel #1
- Fresh sources
- FAST
- Based off of CFS Kernel #7
- Applied BFS 313 (Brain **** Scheduler by Con Kolivas)
- HAVS implemented
- Minor bug fixes
CFS Changelog
Kernel #11
- Kernel now patched up to 2.6.32.24
- Bug fix causing battery drain
- Reverted some UV levels causing instability
- CFS updates
* Implement different treatment for idle shares
* Fix CFS 'Over-scheduling' bug
* sched: Fix granularity of task_u/stime()
* sched, cputime: Introduce thread_group_times()
* sched: Fix select_idle_sibling()
* sched: cpuacct: Use bigger percpu counter batch values for stats counters
* sched: fix racy fair sched*trq
* sched: Cleanup select_task_rq_fair()
- EXT4 support now!
- EXT4 compiled as a module
- EXT4 filesystem bug fixes
* ext4: Fix potential quota deadlock
* ext4: Fix BUG_ON at fs/buffer.c:652 in no journal mode
* ext4: fix memory leaks in error path handling of ext4_ext_zeroout()
* ext4: Prevent creation of files larger than RLIMIT_FSIZE using fallocate
* ext4: Ensure zeroout blocks have no dirty metadata
* ext4: Consolidate inlign pages
- CIFS bug fixes for stability and security
* cifs: Fix a malicious redirect problem in the DNS lookup code
* cifs: don't attempt busy-file rename unless it's in same directory
* cifs: remove bogus first_time check in NTLMv2 session setup code
- Netfilter IPv6 bug fixes
- Memory leak fixed in firmware
- CPU Governor fixes
- Mutex bug fix
* mutex: Don't spin when the owner CPU is offline or other weird cases
- Using xen_clocksource_read now for scheduler (part of 2.6.32.18 patchset)
- vmscan: raise the bar to PAGEOUT_IO_SYNC stalls
- SLAB fixes
- drm: Only decouple the old_fb from the crtc is we call mode_set*
- arm fixes: arm: fix really nasty sigreturn bug
- RDS memory leak fixed
- mm: page allocator: update free page counters after pages are placed on the free list
- mm: page allocator: calculate a better estimate of NR_FREE_PAGES when memory is low and kswapd is awake
- So much more, check my code if you please
Kernel #10
- Patched up to Linux Kernel version 2.6.32.17 (all commits an android kernel would need, no extra bloat) *All credit goes to the linux project, check my github for authors please*
- CFS updates
* Implement different treatment for idle shares
* Fix CFS 'Over-scheduling' bug
- EXT4 support now!
- EXT4 compiled as a module
- EXT4 filesystem bug fixes
* ext4: Fix potential quota deadlock
* ext4: Fix BUG_ON at fs/buffer.c:652 in no journal mode
* ext4: fix memory leaks in error path handling of ext4_ext_zeroout()
* ext4: Prevent creation of files larger than RLIMIT_FSIZE using fallocate
* ext4: Ensure zeroout blocks have no dirty metadata
- CIFS bug fixes for stability and security
* cifs: Fix a malicious redirect problem in the DNS lookup code
* cifs: don't attempt busy-file rename unless it's in same directory
* cifs: remove bogus first_time check in NTLMv2 session setup code
- Netfilter IPv6 bug fixes
- Memory leak fixed in firmware
- CPU Governor fixes
- Mutex bug fix
- Using xen_clocksource_read now for scheduler (part of 2.6.32.18 patchset)
- Much more I will add
Kernel #9
- Board files fixed to allow lower undervolt
- Undervolted to 825Mhz for safe frequencies
- Higher clockspeeds WILL be more stable now
- Compiled CIFS module per request
- Regulator tweaks
- Removed some bloat
- Now using ondemand governor by default, feel free to change it
- Battery charging tweaks (like my inc kernel)
- MANY fixes to HAVS code *thanks for some of them netarchy*
- Regulator being properly used now
- Usleep fixes for sleep mode *via nnode*
- Longer battery life as a result of these major changes
- Volume boost tweaks
- Torture test disabled
- Torture test support disabled
- Ksgl tweaks for performance
- Higher clock speeds should now be more stable
- Wifi module tweaks
- More I will add
Kernel #8
- Added BFQ I/O Scheduler
- Default scheduler is bfq
- Fixed atomic functions in bfq *thanks cyanogen and co*
- Cleaned up/removed unneeded code
- HAVS is still included and functioning
- Code cleanup
- Undervolted even more (Battery life is LONG)
- Compiled with neon optimizations
- Conservative governor threshold tweaked (via netarchy)
- Conservative Governor sampling rate tweaked per user request
- GPU edits for performance
- 5MB of memory reserved for the Adreno GPU
- Kernel will boot faster as a result of "set read ahead" changes
- Various wifi module tweaks
- Packet Filtering set to turn off after 1s
- Bluetooth sleep bug fixed *via kmobs via kernelzilla*
- Rpc changes/tweaks
- V4L2 code disabled now for media interface
- Vmalloced tweaks via @cyanogen *PERFORMANCE BOOST*
- Tweaks for stability
- Now undervolted to 825Mv! *Longer batter life*
- Ksgl tweaks for performance
- Higher clock speeds should now be more stable
- Wifi module tweaks
- More I will add
Kernel #7
- Added new CPU Governor - 'Interactive Governor' thanks Mike Chan @google
- Still using Conservative Governor
- Now overclockable to speeds up to 1.26Ghz (Not all phones can run 1.26, if your phone locks up, OC lower)
- Bluetooth tweaks (double check that bluetooth works for me please)
- Even more undervolted
- Wireless 'n' support
- Switched to 'cfq' scheduler
- Open VPN Modules
- Other things I will add
Kernel #6
- Overclocking should be 100% functioning
- SetCPU works now
- Overclockable up to 1.113 (Will raise this number soon )
- Added CPU Governor "OnDemand"
- Added CPU Governor "UserSpace"
- Added CPU Governor "Performance"
- Added CPU Governor "Conservative"
- Default CPU governor changed to "Conservative"
Kernel #5
- Five point multitouch (thanks for the code ffolkes)
- ADB working for most.... (wierd)
- Speed tweaks
- CPU Governors updated
- CPU tables updated
- Code is live
Kernel #4
- Much faster
- Much smaller kernel, removed all bloat
- ADB should work now, let me know
- Overclocking should work, let me know
- Switched scheduler to deadline
- More audio tweaks (per request, I forget who asked)
- Included a slew of modules, should cover any module you'd need
- More I will add
Kernel #3
- OC capability should work via terminal
- Netfilter (Wifi tether) built into the kernel
- Added OnDemand CPU governor
- Added UserSpace CPU governor
- Added Conservative CPU governor
- Default governor is currently OnDemand
Kernel #2
- Speed boost
- Five point multi touch support (believe this was ffolkes, thank you)
- FPS unlocked now! (thanks toast)
- Audio Boost Tweaks (LOUD)
- Integrated code to use 3 point for sensors that do not support 5 (thank you ffolkes)
- Kernel should work on CM6 now (let me know)
- Kernel should now detect screen arch on boot (thanks cyanogen)
- Should support both epson and n
- OC Capable now - up to 1.26 Ghz!
- Voltages lowered significantly for even better battery life
- Changed default scheduler to cfq
- Cleaned up unneeded code
- More I will add
Kernel #1
- First kernel for the HTC Evo
- Based off of the HTC source code - 2.6.32.12
- Added drivers for Static Voltage Scaling (SVS)
- Added drivers for Hybrid Adaptive Voltage Scaling (HAVS)
- Using CFS
- No OC capabilities as of now
- Cameras should work fine
- WiFI should work fine
- Bluetooth should work fine
- All things you would expect to work should be working, let me know
Any chance we could see some of the Desire's audio values in this kernel?
neckface said:
Any chance we could see some of the Desire's audio values in this kernel?
Click to expand...
Click to collapse
if I can find the code for it, yes.
You evo users have no idea what HAVS is like
I can't wait to see the feedback
kingklick said:
You evo users have no idea what HAVS is like
Click to expand...
Click to collapse
Well, for me, I have no idea what it is at all lol
Mind explaining what it does plz? =P
kingklick said:
if I can find the code for it, yes.
You evo users have no idea what HAVS is like
I can't wait to see the feedback
Click to expand...
Click to collapse
If you don't find it before I get home, I'll pm the directory to you.
And yeah, I haven't a clue what that is. Lol
This is interesting... any more details?
- Sent via my EVO 2.2 (Fresh 3.1.0.1) from the back seat of your Momma's car.
What on Earth is HAVS?
after a little googling...
Hybrid Adaptive Voltage Scaling (HAVS)
david279 said:
after a little googling...
Hybrid Adaptive Voltage Scaling (HAVS)
Click to expand...
Click to collapse
MMhhh can't wait to try this one out
Is FPS unlocked on this?
Does this work for all 2.2 roms?
bigant262 said:
Is FPS unlocked on this?
Click to expand...
Click to collapse
as of now, most likely not. It can easily be implemented
jaysmi32 said:
Does this work for all 2.2 roms?
Click to expand...
Click to collapse
YUP! should have no issues
If one was to push this to their device on top of whatever custom kernel/rom running.. would things start to get messy?
whats the best recommendation ?
kingklick said:
as of now, most likely not. It can easily be implemented
YUP! should have no issues
Click to expand...
Click to collapse
Thanks for the quick reply. I'll wait until you put it in. Will look forward to updates on this.
ok guys kernel is live =)
let me know if you have any other questions
I'm done playing for the day but I'm def keeping an eye on this thread. I can't wait to see some real world test results. I have a feeling this thread is going to blow up by the time I get up in the morning.
While I would absolutely love HAVS, I also don't want to lose the modifications in netarchy's kernel with the FPS cap unlocked. Any way you could possibly integrate that into your kernel?
An update.zip would be grand, too.
I have netarchy kernel 4.0.3a with Fresh 3.1.0.1... can i simply flash this over it?
- Sent via my EVO 2.2 (Fresh 3.1.0.1) from the back seat of your Momma's car.
cosine83 said:
While I would absolutely love HAVS, I also don't want to lose the modifications in netarchy's kernel with the FPS cap unlocked. Any way you could possibly integrate that into your kernel?
An update.zip would be grand, too.
Click to expand...
Click to collapse
Yup, if he sends me his code
HondaCop said:
I have netarchy kernel 4.0.3a with Fresh 3.1.0.1... can i simply flash this over it?
- Sent via my EVO 2.2 (Fresh 3.1.0.1) from the back seat of your Momma's car.
Click to expand...
Click to collapse
yes, use fastboot to flash the kernel itself, then adb push the modules
{
"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"
}
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
FEATURES:
-Based on latest sources
- Compiled off Linaro 4.9.3!
- Philz Recovery 6.48.4
-Insecured
-/system mounted as rw
-CPU Overclockable upto 1.7Ghz
-GPU Overclockable to 500Mhz
-Optimized RWSEM Algorithms
-LZO compression for faster boot
-Disabled GENTLE_FAIR_SLEEPERS
-Dynamic Fsync control
-Optimized AES and SHA1 routines
-Neon optimizations
-Removed old SHA1 routines
-Optimized git implementation for SHA1
-Lowered vfs cache pressure size to 20
-Enabled ARCH_POWER
-Optimizations to default SLUB allocator
-Patch for depleting entropy requiring no need of frandom or any rngd tweaks
-Tuned CFS parameters
-Asynchronous I/O latency to a solid-state disk greatly increased
-Optimized conservative governor
-Optimizations to Android lowmemorykiller
-Faster NOATIME and NODIRATIME fs mounting flags
-CPU Voltage Control
-Lowered log buffer shift
-O3 Optimizations
-Optimized apply_slack() method for size and speed
-Lock initial TCP window size to 64k (Improves network ping and output)
-Dynamic management of dirty page writebacks
-Philz recovery
- Introducing Intelli_thermal - A new thermal protection mechanism ported to MSM8930 by me, originally developed by faux123 (Replaces stock msm_thermal)
- Introducing ThunderSonic Sound Engine - A sound control driver wholly developed by me
- Introducing Charger Control 2.0 - A charger current rate control driver wholly written by me
- Nullified all the RAM and battery issues by disabling some unnecessary stuff!
- Added zSwap from Linux 3.11 [More RAM love? ]
- Added frontswap
- Added vnswap - a virtual swap page file residing the RAM memory pool.
- Disabled FRAME_POINTER slowing down the kernel
- Added Intelli_active governor
- Tuned the kernel for Cortex-A15
- Disabled lots of debugging
- Added native LZ4 compression support
- Added full support for Android Kitkat in separate version
- Fixed second core frequency overiding issue
- Now powered by AROMA Installer
- Disabled proc fs config storage swelling the kernel
- Added generic input joystick support
- Loads of other code cleanups and arbitrary optimizations
- Introduced in GPU Voltage Control
- Added BFQ IOScheduler
- FIOPS IOScheduler
- Added Assload of new TCP Congestion controls
- Improved IO throughput
- Merged some writeback patches to improve vmscan module
- Added native Samsung F2FS filesystem support
- Linux MM Readahead set to 256k
- Recovery some RAM by reducing android logger memory allocation
- Patches to improve deep sleep
- Disabled useless userspace and powersave governors
- Switched to XZ kernel compression
- Removed ARM tracer debug code
DOWNLOAD:
Mirror 1
GPL Compliance:
http://bit.ly/1cypvyz
Just a statement regarding kernel source: The Kernel Source is of course covered under GPL version 2. Free software does NOT mean no work or time was spent working on it. I have donated a large sum of my free time to this kernel. If you want to include my kernel in your project or use my source code, please mention it in your post, give proper credits.
Opensource does not mean 'Out-of-credit'
Thank you.
Credits:
@DD-Ripper : For amazing logo design!
@faux123- For his various kernel patches and features.
And all others mentioned on my github in contributors tab.
XDA:DevDB Information
ThunderZap Kernel, Kernel for the Sony Xperia L
Contributors
varun.chitre15
Kernel Special Features: Stability coupled with Velocity!
Version Information
Status: Stable
Created 2013-09-22
Last Updated 2015-08-29
Reserved
ThunderZap 4.9 - November 7
Code:
- Compatibility with CM12 beta 2
- SELinux enabled and set to permissive
ThunderZap 4.8-r2 - Not released
Code:
- Fix un-bootability issues with some phones
- 1.7 Ghz OC now available for Kitkat variant too
- SELinux enabled and set to permissive
ThunderZap 4.8 - November 22
Code:
- Lollipop compatibility
- ThunderSonic Engine 2.0 - Implemented locking mechanism
- Pushed CPU Clock to 1.7Ghz - (Lollipop only)
- Merged Lollipop patches from CAF
- BFQ IOScheduler updated to v7r6
- Optimized Low memory killer to reduce aggressiveness
- Memory management patches from Nexus 6 kernel
- CPUFreq optimizations from Nexus 6 kernel
- Patches to TCP from upstream
ThunderZap 4.7 - September 14
Code:
- Updated exFAT to latest upstream version
- Huge bunch of Samsung F2FS updates
- TWRP 2.8.0.0New
- Philz Touch 6.57.5 Updated
- Dual recovery is here!New - TWRP+Philz Touch
- Fixed in-recovery 1970 timing mismatch
- Optimizations to cpufreq driver
- New governor: SmartMax: This is my new favorite governor, an ideal choice for optimum performance and battery backup
- New IOScheduler: TripNDroid: My second favorite scheduler after BFQ!
- Optimized GPU flags
- Sysfs interface to control GENTLE_FAIR_SLEEPERS on the fly
- BFQ scheduler optimized for SSD
- Disabled add_random method for improved IO performance
- Moved to Linaro 4.7 from Linaro 4.6
- Enabled aggressive multi-core power savings
- Updated base CAF sources with over 100 new patches that go to VIDC, Adreno GPU driver, qssecom daemon, touchscreen driver etc
- Updated wifi driver from latest CAF sources
- Speedup in /proc/net/unix access
- Optimizations to ext4 filesystem from upstream.
v4.6 - July 10
Code:
Introduced in GPU Voltage Control - instructions on Post #3
- Pushed CPU clock to 1.6Ghz
- Added BFQ IOScheduler v7-r5 (my favorite one)
- Brought back FIOPS IOScheduler
- Added Assload of new TCP Congestion controls
Code:
* .westwood (default)
* .reno
*. bic
*. highspeed
*. hybla
*. htcp
*. vegas
*. veno
*. scalable
*. yeah
*. lp
*. illinois
- Improved IO throughput
- Merged some writeback patches to improve vmscan module
- Added native Samsung F2FS filesystem support
- Linux MM Readahead set to 256k
- Recovered some RAM by reducing android logger memory allocation
- Patches to improve deep sleep
- Disabled useless userspace and powersave governors
- Switched to XZ kernel compression
- Removed ARM tracer debug ****
- Philz touch updated to 6.48.4
- Merged all CAF kernel changes
- Compatibility to latest CM releases(model number issues)
v4.5-r1 - June 16
Code:
- Merged in all CAF kernel changes
- Philz touch updated
- Compatibility with new CM build
v4.5 - June 14
Code:
- Added compatibility for Kitkat
- CPU freq down to 1.5Ghz
- Philz recovery
- Updated wifi driver
- Updated CAF source to Android 4.4.3
- Fixes to Thundersonic Engine for future app compatibility
- Removed some unused features, rest all features intact!
v4.1-r2 - Mar 20
Code:
- Added compatibility to CM11-M4
- [Color="Red"]Workaround for internal storage - Now you can have full access to your internal storage at a new mount point in /storage/sdcard2! on any 4.4 ROM
[/Color]
v4.1 - Mar 10
Code:
- Removed GPU OC, ROW & FIOPS IOscheduler
- Updated TWRP to latest 2.7.0.0
- TWRP : Working implementation of reboot recovery
- Fixed the shutdown and logolooping problems
v4.0 - Mar 06 - Major release
Code:
- Introducing Intelli_thermal - A new thermal protection mechanism ported to MSM8930 by me, originally developed by faux123 (Replaces stock msm_thermal)
- Introducing ThunderSonic Sound Engine - A sound control driver wholly developed by me
- Introducing Charger Control 2.0 - A charger current rate control driver wholly written by me
- Nullified all the RAM and battery issues by disabling some unnecessary stuff!
- Upgraded sources to 3.4.82 [More than 3000 new improvements]
- Added SELinux support
- Overclocked upto 1.7Ghz - With the second core overiding issue almost vanished we don't have any issue with higher OC
- Added support for Microsoft XBox 360 Xpad controller (experimental)
- Added zSwap from Linux 3.11 [More RAM love? ]
- Added frontswap
- Added vnswap - a virtual swap page file residing the RAM memory pool.
- Disabled FRAME_POINTER slowing down the kernel
- Asynchronous Fsync from HTC kernels
- Added Intelli_active governor
- Added ROW IOScheduler
- Added FIOPS IOScheduler
- GPU OC upto 533Mhz
- Enabled hardware real-time clock write access - Fixes mismatched timestamps in recoveries and their backups
- Tuned the kernel for Cortex-A15
- Disabled lots of debugging
- Added native LZ4 compression support
- Added full support for Android Kitkat in separate version
- CD-ROM emulation via sysfs lun file (Thanks to @FrozenCow)
- Fixed second core frequency overiding issue
- Added TWRP 2.6.3.0(latest) in separate version
- Updated CWM to 6.0.4.7(latest)
- Now powered by AROMA Installer
- Disabled proc fs config storage swelling the kernel
- Added generic input joystick support
- CWM Recovery changes: Completely working reboot recovery implementation
- Loads of other code cleanups and arbitrary optimizations
v3.1 - Dec 28
Code:
- Disabled Memory compaction - should fix overusage of RAM issue
- Optimized and reduced voltage table by 62mV
- Merged 15.3.A.1.12 sources - Kernel is now future compatible with the new firmware
- Boosted the display panel frame-rate slightly for more smooth UI
- Added back the Westwood TCP Congestion control and set it as default - Should manage all Network traffic more efficiently!
v3.0 - Nov 28
Code:
*. Major update - Read changelog [URL="http://forum.xda-developers.com/showthread.php?p=47935391"]here[/URL]
v2.0-rc1 - Aug 07
Code:
*. Voltage table fixed causing phone freeze
v2.0 - Aug 03
Code:
*. Initial release
FAQs
Well lets begin, almost all features can be controlled using the TricksterMOD
How to access recovery?
Keep pressing volume down button when you see Thunderzap logo
Now special things about this!-
1. You can also use camera key to boot into recovery! hell yeah! BUT remember, NOT to use it for your first recovery boot. Make first recovery boot only using vol down key! Remember this. If you do so, phone will stuck up on ThunderZap logo and your key combo will get swapped and remapped to Volume up and you would need to use Vol up to boot into recovery until the next kernel flash.
2. You can also reboot to recovery from your Android OS directly! Yes I have done it! But same criteria as above! not to use that way for first boot. After you are done with first recovery boot you can use camera key, terminal way anytime!!
So how to use the terminal way?
Open terminal emulator[NOT adb shell]
Gain su permissions and type
Code:
start-cwm
And within a minute you will be in CWM!
How to determine which TCP congestion to use??
Latency - Download - Upload
cubic:
1st run: 15ms - 10,75Mbps - 7,82Mbps
2nd run: 14ms - 10,84Mbps - 8,06Mbps
reno:
1st run: 13ms - 15,51Mbps - 6,73Mbps
2nd run: 13ms - 14,73Mbps - 8,51Mbps
bic:
1st run: 12ms - 10,38Mbps - 8,61Mbps
2nd run: 13ms - 10,78Mbps - 8,62Mbps
westwood:
1st run: 11ms - 17,65Mbps - 8,30Mbps
2nd run: 13ms - 13,28Mbps - 8,29Mbps
highspeed:
1st run: 13ms - 10,76Mbps - 7,94Mbps
2nd run: 16ms - 14,42Mbps - 8,52Mbps
hybla:
1st run: 14ms - 11,19Mbps - 7,44Mbps
2nd run: 14ms - 13,47Mbps - 7,56Mbps
htcp:
1st run: 14ms - 13,24Mbps - 7,03Mbps
2nd run: 15ms - 10,85Mbps - 8,00Mbps
vegas:
1st run: 14ms - 8,49Mbps - 6,62Mbps
2nd run: 14ms - 12,00Mbps - 7,07Mbps
veno:
1st run: 13ms - 9,58Mbps - 8,13Mbps
2nd run: 13ms - 8,50Mbps - 7,64Mbps
scalable:
1st run: 18ms - 12,01Mbps - 8,73Mbps
2nd run: 14ms - 13,96Mbps - 8,23Mbps
lp:
1st run: 14ms - 14,90Mbps - 8,68Mbps
2nd run: 14ms - 13,44Mbps - 8,72Mbps
yeah:
1st run: 14ms - 13,37Mbps - 8,28Mbps
2nd run: 17ms - 13,89Mbps - 8,14Mbps
illinois:
1st run: 13ms - 12,93Mbps - 8,24Mbps
2nd run: 16ms - 13,97Mbps - 6,46Mbps
Click to expand...
Click to collapse
See above chart and decide which to use! But westwood has been set as default!
Some of them from above chart won't be present, so watch only those which are present in feature list.
Q. How to use vibration intensity control?
echo "your-value" > /sys/devices/virtual/timed_output/vibrator/level
Values range is 12-31. None other
Q. How to use ThunderSonic Engine?
It is a sound control driver. There are two interfaces which you can control
1. Headphone boost - I made this feature because louder volume than max volume in earphones rushes more adrenaline in me making music more enjoyable.
Turning this On will give you instant significant volume boost in earphones which is greater than what you get when the volume is max. Just make the volume maximum and turn this ON and you will notice it
How to turn on:
In terminal emulator/ adb shell, get su permissions and then type
Code:
echo 1 > /sys/kernel/thundersonic_engine/headphone_boost
and use 0 to turn off
2. Speaker boost - In crowded areas I felt speakers of XL fall short in terms of volume magnitude. So I made this to increase speaker volume speakers beyond its limit and now my phone sounds even louder than those dirt cheap china phones
This is 8-leveled boost interface. That means there are 8 boost levels. The default is 3 on TZ
How to turn on
Code:
echo X > /sys/kernel/thundersonic_engine/speaker_boost
where X can be any value from 4 to 8 depending upon the volume boost you require To reset back to default use value 3
Use above features with caution. Using headphone boost for a long time may damage your ears. And do not use speaker boost for a long time. If for some songs you hear crackling of speakers then reset its boost level to 3 or a relatively lower level of 4 or 5
Q. How to use charger control?
1. AC current control: In times of hurry I felt the charging times to be too long and so I made this. With this you can control the charging current rate through wall charger.
Before doing anything you first need to enable the master switch of the control or else the values you write will be negelected
How to enable master switch
Code:
echo 1 > /sys/kernel/charger_control/enabled
After this you can use custom current values like this
Code:
echo X > /sys/kernel/charger_control/custom_ac_current
where X can be any value in mA (Milliamperes) I use 1600 i.e 1600mA which completes my phone's charging from 3% to 100% in around 1 hour 30 mins.
The stock current ranges from 1000-1100mA and takes around 2 hour 30 mins to 3 hours. Avoid using values higher than 2200.
2. USB current control: Everyone knows the charging rate from PC via USB is damn slow. Many new PC's have newer USB ports which can offer current rates higher than 1500mA but still our kernel only pulls 500mA. I made this to control it yourself
As usual you need master switch enabled to write the new values.
How to use
Code:
echo X > /sys/kernel/charger_control/custom_usb_current
where X can be any value in Milliamperes. I use 1500 i.e 1500mA
Q. How to use GPU Voltage Control?
Currently there are no GPU voltage controlling apps. The upcoming ThunderZap control app supports that.
Obtain current voltage values
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/gpu_mv_table
Output will be something like this:
945 mV
1050 mV
1150 mV
Change these values:
Code:
echo "930 1000 1100" > /sys/devices/system/cpu/cpu0/cpufreq/gpu_mv_table
This will change the voltages as below
930 mV
1000 mV
1150 mV
Q. I am having abnormal battery drain
Most of the time the kernel isn't responsible for this.
a) Make sure you are on stock frequency of 1Ghz. Sometimes the frequency is getting overridden to 1.5Ghz even if you didn't set that. To avoid such situations use frequency lock option from Trickstermod kernel app.
b) The kernel is not pre-undervolted any more. You can undervolt it on your own. Optimum value is 75mV. Don't undervolt more than that
Q. How to use extra modules provided
Best way is to use init.d script to load them on boot.
e.g If you want to use the NTFS file system module. You have to first place the ntfs.ko module provided in /system/lib/modules. Then you need to create an init.d script in /system/etc/init.d with any name say 99modules with following code
Code:
#!/system/bin/sh
insmod /system/lib/modules/ntfs.ko
Next you need to give that file all permissions and reboot the phone and you are done!
P.S: Loading external modules affects battery life of the phone.
reserved
Good work.
All the best.
Good job man.
Best of luck! :highfive:
Post #3 updated with all controlling stuff!
Enjoy!
I've some concerns :-
1) As you can see from screenshot, default boot frequency of cpu0 is 1188 MHz while of cpu1 jumps to 1566MHz on load.
This is one of few reasons I disabled overclock in my kernel. One should enable intelliplug and disable mp decision to fix this.
Code:
su
stop mpdecison
2) Eco-Mode? Isn't it for quad core devices? Turning it off disables two cores. And we've only two.
3) Intelliplug works well.
4) Your voltage table is wrong. 1242MHz runs at lower voltage than 1188MHz. It's also irregular.
for example all 384,432,486 MHz run at same voltages.
5) Your ramdisk.cpio contains another ramdisk.cpio + pack script. Remove these junks.
6) xz -e offers best compression ratio but it's way slower than lzop (which in turn has poorest compression ratio).
So, xz compressed kernel is light weight but takes longer time ( usually 3-4 seconds more to decompress fully) than lzop compressed one.
You can see benchmark comparsion of gzip,xz,lzma etc here
In all xz compressed kernel doesn't boot fast in any way.
That's it for now
Rachit Rawat said:
I've some concerns :-
1) As you can see from screenshot, default boot frequency of cpu0 is 1188 MHz while of cpu1 jumps to 1566MHz on load.
This is one of few reasons I disabled overclock in my kernel.
2) Eco-Mode? Isn't it for quad core devices? Turning it off disables two cores. And we've only two.
3) Intelliplug works well.
4) Your voltage table is wrong. 1242MHz runs at lower voltage than 1188MHz. It's also irregular.
for example all 384,432,486 MHz run at same voltages.
Click to expand...
Click to collapse
1. True (I will be releasing a 1.2Ghz version of kernel tomorrow who are not that much concerned with gaming)
2. This is true as well. But this works with dual core too according to my last 20 days testing and I have noticed gradual improvement in battery backup. I will contact faux123 to reconfirm my observations.
4. Thanks! Didn't observe that. Will fix it with tomorrow's minor update
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
@Rachit Rawat
Quick fix for the issue 1 of cpu1 getting maxed out!
Do this- Change freq to any other step and put it back to original. Now try doing a heavy task and see where cpu1 is getting capped at!
Just try it out
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
varun.chitre15 said:
@Rachit Rawat
Quick fix for the issue 1 of cpu1 getting maxed out!
Do this- Change freq to any other step and put it back to original. Now try doing a heavy task and see where cpu1 is getting capped at!
Just try it out
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
Click to expand...
Click to collapse
why not just turn on intelliplug and disable mpdecision?
Rachit Rawat said:
why not just turn on intelliplug and disable mpdecision?
Click to expand...
Click to collapse
I already have done that and I saw the maxing out of cpu1 myself right after you posted even though I have intelli_plug on
The trick I mentioned fixed that
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
May I ask for a simple explanation concerning intelli_plug?
So it is a hotplug alternative, that means it switches unused cpu-cores off. Which results in same speed and half battery - consumption in cost of stability if cpu is in heavy use? And Eco-mode keeps the second core switched off permanently, or nearly?
If I am getting this correctly, then we transform our device into a single-core phone (which would be good itself, we can easier the cpus use with greenify to reduce background processes, right?).
My questions are:
Can that harm the processor (if we dont overclock?) and
if we do not use Eco-mode, will we have the single-core-effect and lagfree games?
Greets
Sent from my C2105 using xda premium
keenofhiphop said:
May I ask for a simple explanation concerning intelli_plug?
So it is a hotplug alternative, that means it switches unused cpu-cores off. Which results in same speed and half battery - consumption in cost of stability if cpu is in heavy use? And Eco-mode keeps the second core switched off permanently, or nearly?
If I am getting this correctly, then we transform our device into a single-core phone (which would be good itself, we can easier the cpus use with greenify to reduce background processes, right?).
My questions are:
Can that harm the processor (if we dont overclock?) and
if we do not use Eco-mode, will we have the single-core-effect and lagfree games?
Greets
Sent from my C2105 using xda premium
Click to expand...
Click to collapse
No, let me try.
Hotplugging means plugging out second core when not needed and plugging it in back when phone is doing some heavy work.
Consider few situations.
1. You are using a mere app like Instagram. In this case there is no need of second core and only first core can process the app smoothly. Here the second is asked to go offline and only first core runs.
2. Now you open NFSMW which is a heavy game. Now the phone understands that there is situation of heavy load, so it plugs in second core that is asks it go online and start sharing the workload from first core.
So this mechanism was managed by mpdecision named service previously. Intelli_plug is alternative mechanism to it. It is more efficient than mpdecision. That is improved algorithms of detecting whether second CPU is really needed or no. It determines that very intelligently and performs a very quick action providing much smoother User experience.
Now ECO-Mode , it just makes intelli_plug a bit lazy. It avoids plugging in second core for many situations and forces first core to do all work as far as I observed. It does plug in second core when phone is in very need of it. This saves a lot of battery.
And no, these features do not cause any harm to hardware because mpdecision does same thing but inefficiently.
I hope everything is clear here.
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
varun.chitre15 said:
No, let me try.
Hotplugging means plugging out second core when not needed and plugging it in back when phone is doing some heavy work.
Consider few situations.
1. You are using a mere app like Instagram. In this case there is no need of second core and only first core can process the app smoothly. Here the second is asked to go offline and only first core runs.
2. Now you open NFSMW which is a heavy game. Now the phone understands that there is situation of heavy load, so it plugs in second core that is asks it go online and start sharing the workload from first core.
So this mechanism was managed by mpdecision named service previously. Intelli_plug is alternative mechanism to it. It is more efficient than mpdecision. That is improved algorithms of detecting whether second CPU is really needed or no. It determines that very intelligently and performs a very quick action providing much smoother User experience.
Now ECO-Mode , it just makes intelli_plug a bit lazy. It avoids plugging in second core for many situations and forces first core to do all work as far as I observed. It does plug in second core when phone is in very need of it. This saves a lot of battery.
And no, these features do not cause any harm to hardware because mpdecision does same thing but inefficiently.
I hope everything is clear here.
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
Click to expand...
Click to collapse
nice kernel varun
one question
Can i turn off both intelli-lug and mpdecision at same time ? and i cant see any setting for intelli-plug in trickstermode i mean how can i turn it off , only MPdecision setting is der
Thanks
naitik2012 said:
nice kernel varun
one question
Can i turn off both intelli-lug and mpdecision at same time ? and i cant see any setting for intelli-plug in trickstermode i mean how can i turn it off , only MPdecision setting is der
Thanks
Click to expand...
Click to collapse
Don't turn both of them off, you will face heavy battery drain. Turn off mpdecision and turn on intelli_plug
And switch for intelli_plug is there in trickstermod in special tab.
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
@varun.chitre15 can you upload to mediafire? I have problems downloading from goo.im
Sent from my C2105 using xda premium
PayPal Donations
please do the following:
Sign in to your PayPal account page
Go to 'Send Payment'
Enter my email id "[email protected]"
option "Personal payment" doesn't work for India, please set "Online purchases". and check Goods or Service (preferably service)
Make the payment of the desired amount of donation you want to send.
Thank you for your kind donations!
Super kernel
varun.chitre15 said:
Click to expand...
Click to collapse
Super stable. Reserved for more detailed review :laugh:
varun.chitre15 said:
I have mirrored the kernel on dev-host.
Check first post.
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
Click to expand...
Click to collapse
one more thing
Any news about JetMode ?
SmoothMod Kernel (SMK) for Samsung Galaxy Tab 3 8.0 3G (SM-T311), also may work on WiFi version (SM-T310), all stock and CM ROMs.
Development discontinued, read reason here.
This kernel is developed to give you more smoothness and stability than you can have on stock kernel and others.
Warning. Kernel may work on your device/ROM and may not. For me it works at all ROMs and for many people (on 4PDA.RU forum) it works too. Some people say (or said before kernel worked, this also can be) it doesn't work. So do a kernel backup please before you flash it first time. I've never had boot or usage problems with SMK, but it could be because i'm its developer (though it can not be the reason for that I'm always successfully boot it..). So it seems that our devices of the same model might be different. Be careful as I can not help you.
Features:
- Kernel version updated up to 3.2.26 and keeps updating
- Safe CPU overclock to 1.9 GHz with CPU-Boost kernel driver developed also by myself
- Custom (and only here) governor Smooth that is made to give both good battery saving and absolute smoothness. Uses GPU load and io_wait to additionally increase frequency at the right time.
- Kernel has a custom Android service smkd that controls all its features and provides many tweakable settings that you can change very simply: through terminal command "smkd" (instructions below) or "by hands" at folder "/smk" (like usual linux kernel settings at "/proc/sys/{kernel|vm|net}"). The program is written in C language, not as a script, for performance (shell-scripts are very slow when comparing with optimized C-programs).
- Tweak Menu that can be found if you type 'smkd' in your terminal.
- SmoothnessControl - one of smkd's functions that tries to guarantee UI smoothness to your tablet even if there are very CPU-hungry (but not I/O) apps/programs running like android.process.media and others. By default disabled. To enable, type this: 'su -c "scd --enable"' in terminal emulator. To disable, type 'scd --disable'.
- CPU Undervolt controlled through smkd.
- DynBS program (also developed by me) used by smkd to improve battery saving by 40% and more.
- Boeffla Sound Engine with custom settings, not working with Boeffla Sound Control app because smkd controls them (it's needed because smkd fixes engine's sound effects bug). Settings are stored folder "/smk" in files beginning with "boeffla.".
- Cron scheduler configured from file /sdcard/cron/root.
- All the custom tweakable settings described upper are reloading instantly after you change them or on delete (cron schedule file is also under the same watch).
- Kernel is compiled with optimized HYPER-TOOLCHAIN with gcc version 6.0 and maximally optimized compiler configuration.
Customizing kernel:
There is now nothing that needs to be explained, as customizing is pretty simple! Just type command 'smkd' (without quotes) and go through the menu (by entering appropriate symbols) as you want, changing parameters as you need.
Ask, if you have questions
If you have questions or suggestions about my kernel, feel free to write about that here and I will try to answer.
F.A.Q.:
Q.: Do I need to wipe Dalvik/ART cache before/after flashing this kernel?
A.: It is even not useful to wipe caches because they are used by Android only, not by kernel. So, it's not needed.
Q.: The kernel does not boot! What do I have to do to boot it?
A.: Write a message in this thread providing info about what ROM do you use, what Android version it is and what kernel build (kk/lp/mm) and version you are trying to boot. I will reply to that message and try to fix that problem.
Author: me, igoryan94
Download from Google Drive
Before flashing this kernel please do a backup yours first!
Warning! If you have a Jellybean/Kitkat rom, then download the smoothmod-kernel-kk-... build. If you use Lollipop (CM12), then your build to download will be ...-lp.... If it is a Marshmallow (CM13), then download mm build.
Other choice will cause your device to not be able to boot!
(Sorry for my (maybe )bad english)
Plans:
-
Developing now:
-
Changelogs (old*):
1.2.1/1.2.2:
- Returned possibility to load a profile from command line (command 'smkd --load [name]' or 'smkd ld [name]')
- Added custom setting for apps CPU time, now it has two groups: idle and high.
Idle group gives an app very small amount of CPU time, use for hungry apps that you don't need.
High group grants an app a 95% of all CPU time. Use to speed up some apps or games.
It is all very similar to Greenify and others, excepting that this is not battery saving solution, only to smooth up your Android, as Greenify disables an app and CGroup lowers app's CPU execution time available to it.
- I/O settings fully rebalanced for smoothness for system processes and apps processes
- Also added control group for I/O that does like one for CPU, but for I/O and developed its correct (for Android) behavior.
- Current configuration name in smkd menu now correctly saves and loads after reboot.
- Default LMK level changed to 125
XDA->SMK:
1.2:
- Got a smoother UI with better CGroup tweaking
- In case of some situations smkd will notify user with drawing a small square of some color at the left upper screen edge (portrait orientation). For overheat the color is red. When SmoothnessControl gets to work, color is light blue/cyan. If device's load is too high, the color will be blue.
"Notification" will blink when screen updates because the framebuffer devices are not support this method of screen drawing. But it works for now and I think that it is very useful to know the reasons of device's lags and freezes.
- Menu now immediately reacts to input, instead of pressing some characters and then Enter. Modified all menus that way so the interface is now much better.
- When exiting menu, parameters are automatically saved to default profile. No need to care about it anymore...
- Added Quick settings also to RAM and I/O
- Main menu: moved all "p)" menu elements to main menu level, it is quicker to access now
- Some more Quick settings options added
- Added Quick settings to my menu templates, so I will add this to most of the new menus in the future
- Main Quick settings colors changed to blue, additional are still white
- Overclock to 1920 MHz lowered to 1800 MHz because 1800 is much more stable (1920 causes reboots on Marshmallow on my tablet)
- Device now reboots when charging speed is too bad. By default this is disabled. Also added setting "Charge cycle time" and Quick settings for that so you can quickly set up to what charge speed you need (reboots are helpful but not very good for users that want to play device when it charges).
- 'Boost' feature disabled so now DynBS will work as always even when device is laggy
Previous:
1.1.22:
- CPU, Boeffla Sound and Network setting menus in smkd now have the Quick settings feature that helps to configure them by one click instead of tweaking them each
1.1.21.1:
- DynBS updated: now it uses frequencies from 350 to 700 MHz too, so more battery can be saved.
1.1.21:
- smkd now has menu interface which opens by default by command 'smkd' without options.
- All setting commands are removed. Use menu instead.
- In Cyanogenmod ROMs SystemUI is restarted every time when screen becomes disabled, so you may never see it lags or freezes again.
- PCS renamed to SC (SmoothnessControl).
- Overclock enables when device is laggy even when it is disabled in settings
- Redone temperature control: now smkd monitors a device temperature instead of CPU. It leads to better smoothness. Also overheat situations disable some functions like I/O readahead, ZRam, KSM.
- Overheat prevention function fully removed
- Governor Smooth now enables both cores on gestures with two or more fingers instead of simple tap.
1.1.20:
- Added charging compensation: now when battery charging is too slow, CPU Topology and voltage will be changed appropriately for quicker charge.
- Touch boost changed from 1400 to 1000 MHz, but it also boosts busfreq to 400 instead of 267 MHz. Results in better reaction on screen touch.
- Governor Smooth's default sampling_rate changed from 27000 to 16000 for quicker reaction
1.1.19:
- Added ARM CPU Topology for better multithread scheduling
- Some CPU Scheduler changes for smoothness or power saving (tweakable)
- Improved smkd UI code
1.1.18.1:
- Fixed performance/smoothness problems.
1.1.18:
- Added new default configuration "throughput"
- GPU acceleration is now forced for all apps and it is changeable from smkd.
- I/O scheduler SIOPlus added.
- DynBS is returned (one user asked for it as it really saves battery, as he said).
1.1.17:
- User profiles are no more exist, replaced with default configurations" instead. They are: smooth, battery, ram and cool. After each launch of smkd (mostly on reboot) configurations are removed and recreated to always be fresh and up to date.
- Added ability to create, rename and delete profiles by normal way, but default profiles cannot be replaced, deleted or renamed through smkd (only "by hands").
- GPU settings: composition and forced GPU-acceleration from Android settings for developers.
- Tripndroid and Zen I/O schedulers are added.
1.1.16.1:
- Configurations loading is now be always successful (but only if appropriate file exists), without that annoying errors "try again later, please..."
- Small tweaks optimization
1.1.16:
- Overclock now disabled by default, as it was on 1.1.14 and before, for battery saving (overclock eats too much battery). Can be enabled with command 'smkd -c -o 1'. Temperature control is now optimized for both CPU overclock and hardware maximal frequency modes.
- smkd interface improved a little.
- KSM functionality added with some fixes for Mali GPU driver bugs in userspace.
- Default temperature limit is now 64 C (before it was 67 C). This is done for more stability when the weather is hot.
- Some changes for smoothness and stability...
1.1.15:
- Overclock is enabled now for any time when screen is enabled (no more boost).
- Developed overheat preventing functions that cool device when temperature is between 90% of threshold and higher. CPU frequency will be set according to temperature for the moment (for every 2% will be a different frequency). Function can be disabled but it is not recommended.
- All cooling functions now control voltage too to be more effective.
- Governor Smooth tweaked for more balance (oc_nr_run_threshold->6)
- Governor Smooth: changed logic: half-overclock (to 1.7 GHz) will occur if number of processes running is a half of oc_nr_run_threshold tunable.
- smkd now controls I/O scheduler and I/O readahead settings, they are tweakable with smkd command. Profiles change this parameters too.
1.1.14:
- smkd tweaker program fully translated to english and comes now in two languages. Now it uses Android's property 'persist.sys.language'.
If your device configured for any language excepting russian, then program will be in english for you. At the other case it will print out text and messages in russian.
- Improved custom configurations in smkd. Now it loads profiles synchronous with service (by using mutex) instead of relaunching it with shell stop/start (it was too slow and even buggy to do that).
- DynBS will not be in kernel anymore, it is not so effective as needed. Instead, I've added a profile tweaks for my governor Smooth, that tweaks easily changeable from smkd (cmd. "smkd -c -s [0-2]").
1.1.13:
- Cron scheduler now works correctly (i'm happy ), doing exactly what was scheduled by the user at the exact times.
- I don't remember what was in this version because forgot this as I worked on 1.1.14 intensively.
-----
* Newer versions contain changelogs in install archive itself.
Very good kernel. Use [5.1.1] Resurrection Remix 5.5.9 + SMK 1.0.20.1 lp.
Nerovinger said:
Very good kernel.
Click to expand...
Click to collapse
Thanks
stuck at bootanimation..
Sent from my SM-T311 using XDA-Developers mobile app
so.hell said:
stuck at bootanimation..
Sent from my SM-T311 using XDA-Developers mobile app
Click to expand...
Click to collapse
What ROM do you use? Android version, SMK version?
AICP BY GR8NOLE.
SMK V-1.1.12
i try dirty flash n clean flash.stuck at bootamination..
Sent from my SM-T311 using XDA-Developers mobile app
so.hell said:
AICP BY GR8NOLE.
SMK V-1.1.12
i try dirty flash n clean flash.stuck at bootamination..
Sent from my SM-T311 using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks like it will not work on AICP ROM, on Cyanogenmod 13 and ResurrectionRemix kernel works fine (I've tested that)... Sorry The reason for that I can not fix this problem is that I do not know (even cannot know) how to make an init.rc (this file starts all Android services on boot) file universal (to support absolutely all ROMs at one time). This is also the reason for three builds of kernel: kk, lp and mm...
Nice kernel. But can you please make a version of your kernel work with the T310 (WiFi)?
Stuck at Bootanimation
ROM: Resurrection Remix 5.6.9 by powermetza
Android Version:6.0.1
SMK version 1.1.12
pawas99 said:
Stuck at Bootanimation
ROM: Resurrection Remix 5.6.9 by powermetza
Android Version:6.0.1
SMK version 1.1.12
Click to expand...
Click to collapse
Try to flash on a clean ROM (with backup of cource)... All fine for me on RR.
Luis_0 said:
Nice kernel. But can you please make a version of your kernel work with the T310 (WiFi)?
Click to expand...
Click to collapse
I can't as i don't know much about modding in '/init.rc' script and also about what differences it has in kernels for T310, T311 and T315... Sorry.
There are too much incompatibilities with builds that are now (they must work everywhere but they don't)...
Ok. Added one question to poll. There are three variants for ROM and two for working or not (six at all), for me all works fine, so I voted for the first three answers.
Version 1.1.14 developer testing ends now, smkd fully translated to english. I will now build the kernel and then begin uploading it to Google Drive.
(sorry for my incorrect english)
igoryan94 said:
Try to flash on a clean ROM (with backup of cource)... All fine for me on RR.
Click to expand...
Click to collapse
Stuck at bootanimation even after flashing on a clean ROM.
waiting for update..
Hey @igoryan94,
Thanks a lot for making this great kernel!
I've flashed the KK version along with the stock ROM http://forum.xda-developers.com/showthread.php?t=2789510. It works very nicely. Would you please show an instruction (or a specific terminal command for newbies like me) of how to overclock CPU to 1.9GHz? Currently the max speed is 1.5Ghz according to kernel audit.
Thanks again
Hey I cant change the cpu frequent through kernel adiutor. As soon as i change the freq to 1920 it changes back to 1500.
igoryan94 said:
I can't as i don't know much about modding in '/init.rc' script and also about what differences it has in kernels for T310, T311 and T315... Sorry.
Click to expand...
Click to collapse
@gr8nole could help him in this?
xdaSEx10 said:
Hey @igoryan94,
Thanks a lot for making this great kernel!
I've flashed the KK version along with the stock ROM http://forum.xda-developers.com/showthread.php?t=2789510. It works very nicely. Would you please show an instruction (or a specific terminal command for newbies like me) of how to overclock CPU to 1.9GHz? Currently the max speed is 1.5Ghz according to kernel audit.
Thanks again
Click to expand...
Click to collapse
CPU frequency is automatically changed to 1920 MHz when special conditions are met (they are: "blocked" processes and waiting for I/O).. Version 1.1.5 will have full 1920 MHz CPU frequency.
I will now upload "developer" version of kernel 1.1.15_dev for KitKat users. If you want, test that) It is not fully contains all changes that i've done, but I'm not at home now and cannot compile new build... For now it has smooth overheat prevention and overclock fully enabled.
Hunter97 said:
Hey I cant change the cpu frequent through kernel adiutor. As soon as i change the freq to 1920 it changes back to 1500.
Click to expand...
Click to collapse
Please wait for SMK version 1.1.15, it will use 1920 MHz as a default frequency always excepting overheat moments (that will disapear very quickly) and governor's battery saver mode.
You can also use a developer version 1.1.15_dev if you use JellyBean/KitKat as your ROM.
Ok, "dev" version released for testing.
When I will return home, I will release another testing version that has an I/O scheduler change functionality, optional Overheat Prevention and changing min_freq to minimal (50 MHz) when temperature event occurs. Maybe it will have even more features (I have smkd code with me, PC is only needed for compiling kernel and ramdisk).
on NoleKat.T310. v1.1 KK 4.4.2 not boot. on CM13 it's ok, but, for me, the best android versioni for this tablet is kk stock and i install NoleKat.T310. v1.1.
jamax80 said:
on NoleKat.T310. v1.1 KK 4.4.2 not boot. on CM13 it's ok, but, for me, the best android versioni for this tablet is kk stock and i install NoleKat.T310. v1.1.
Click to expand...
Click to collapse
SMK will not boot on T310. Only T311.
Features and Description :
Azure App is a profiler app wich have total 8 of profile, each profile have different kind of tunings and different processor have different kind of tunings too. and thereis no placeabo effect in this app nor collect your data.
so here is the Profile simple explanation :
- Chill = Chilling with social media, youtube and small games without worrying about battery drain.
- Chill Max = Chill with more performance
- Smart Casual = Near Default kernel Settings but with better Mem management and better CPU tunings
- Low IQ = Have Performance between Chill and Lazy Plus, Best for Social media and some multitasking. ( New )
- Fast AF = Means hope to push your phone to the limit = more heat
- Game Mode = enchanted version of Fast AF with slightly improve CPU consistency and restrict app usage
- Lazy Boi = Extreme Low power profile that hope to maxed out battery backup will cause LAG !
- Lazy Plus = up to 1.5x better performance than Lazy boi but hope still have similiar Battery Backup
Supported Processor type
- SD636HMP/EAS/OC
- SD675EAS
- SD660 non OC
Just Remember Each Processor / device have totally different tunings.
And dont use other module otherwise will destroy enything..
For More Information you can visit this channel..
https://t.me/r0thAzureApp
Also Check Azure App Website
https://r0thbaby.github.io/AzureAppWebsite/
Love my work ? You can buy me a cup of coffee
https://www.paypal.me/r0thbaby
Cheers
r0th Baby.
Status : ALPHA
Version : 0.2.6
last Update : 09/07/2020
Changelog
Changelog 0.2.6
- Some profile tunings changes
- Change Ram tunings ( Balance mode )
- Change Custom Doze Tunings
- Fixing Compability now works smarter
- Free Up Mem pass the state ( more faster to do the work )
- Heavily Optimize app code
- Reduce App size by 30%+
- Gms Doze Fixed
- Easier to win the reward
- Try to Fix Visible and non Visible bugs
- Lots of under the hood changes not worth writing about, but equally important
Thanks to @project_gh0st and https://instagram.com/fake.itt team for the icon. dont forget to follow the Instagram for more Cool Content
Changelog 0.2.5
- Added Core Control Feature ( not working for violet )
- Added Surprise me only for 4 winners ( send ss and tag me if you win )
- Add Fixing Compatibility ( will fix every time device reboot and open azure app )
- Add Free ram status in Neo UI
- Add save default doze and revert in Doze manager
- Battery Calibration now working fine
- Thermal backup and delete now have revert button
- Seperate Ultra Battery saving for Old CPU and Newer CPU
- New Battery manager UI, More Fresh
- Some profile tunings changes
- Fix Visible and non Visible bugs
- Lots of under the hood changes not worth writing about, but equally important
Changelog 0.2.4
- App now works on all sdm636/sdm660/sdm675EAS devices/kernel/rom/stock rom with fixes inside ( PLEASE UNINSTALL THE OLD APP VERSION AND INSTALL THIS VERSION )
- Mem setting now more battery oriented
- Some profiles more battery oriented
- Ultra ram setting now patched with LMKD settings trying to prevent instantly getting closed and hold more app inside memory ( BETA )
- X00T thermal change to Backup and Delete Thermal ( for all kind of phone )
- Ultra Battery saving setting changed to more battery oriented
- Fix Visible and non Visible bugs
- Lots of under the hood changes not worth writing about, but equally important
Older Changelog
Changelog 0.2.3
- Added new kernel support for Requiem
- Added new feature Ultra Ram Setting
- Chill become slower ( More Battery Oriented )
- Change theme now required to restart app ( Prevent mem leak )
- Change App icon and other icon, thanks to Ghost
- Reduce APK size by 1mb+ ( now app much faster )
- Change Activity now will have garbage collection triggered
- Fix lots of bugs ( Visible and non Visible bugs )
- Lots of under the hood changes
Older Changelog 0.2.2
- All profile except Low IQ slightly improved ( Battery Oriented )
- Introduce 3rd UI -> Neomorphism UI : Tips -> Tap azure logo to reset profile back to default
- Change theme now required no restart
- Lot of fixes including for violet and zen+ also more bugs fixes
- Mem management now Battery Oriented
- Hack kernel checker detection so its slightly faster
- Custom doze tweak improved
- Lots of under the hood changes
Older Changelog 0.2.1
- Support Xenium Kernel ( EAS )
- Support Zen+ kernel ( STOCK )
- Support Violet device with Azure Kernel
- Source Clean Up
- Remove manual kernel checker, and become Automatic kernel Checker, more fast, more flexible, more easy to use
- Each UI now will have toggle to switch between the UI
- Fix TRB GameIT Mode Detector for Both UI error
- Fix Mode checker issue
- Stupid IQ now using some lazy boi settings ( can be seen in mode checker log 2)
- Fix Chill lock Issue
- Improve some profile for some kernel
Older Changelog 0.2.0
Changelog 0.2.0
- Support Wolf Kernel ( Caf, Non Caf, EAS)
- New Ultra Battery Saving
- New Experimental UI
- New quick tiles now working as free up memory
- Improve Custom DOZE Tweak
- Fix New UI Bug
- Fix Internal Conflict
- Lock Chill Performance
- Chill Max now fully unlock the performance
- Prevent Lazy Boi get extra performance
- EAS TUNINGS Is In ALPHA STAGE( DONT HOPE TOO MUCH, I WILL KEEP UPDATING EACH EAS PROFILE ! )
- Lots of under the hood changes
Older Changelog 0.1.9
- Fix some bugs in new Ui and Original UI
- Change Original Thermal to Thermal Option
- New Experimental feature UI
- Add Cryzen Kernel Support
- Add new mode Low IQ = Have performance between Chill and Lazy plus
- Custom Doze tunings improved
- Source Cleanup ( Reduce APK size by 90%+ and Reduce installed size by 35%+ also moderately increase app performance )
- Cheking kernel more faster than before
- Fix all typo in some modes
- Lots of under the hood changes
Older Changelog 0.1.8
Change log 0.1.8
• Fix Issue where Lazy and Lazy Plus not giving a lag at all
• Fix New UI bug
• Fix Mode Checker
• Better Looking New UI
• All modes for all supported device / kernel has been refreshed UP TO 1.5x BATTERY SAVING WHILE MAINTAINING ALMOST SAME PERFORMANCE
• New Doze Manager (Located in Experimental Feature)
• New Once you turn on the new UI, it will save and you dont have to turn on again after closing the app
• New HD Icon has been refreshed by Albert Wesker
• New System Tweak with search and match (So no placebo effect Given)
• Better Memory Management on all modes
• So much Under the hood change
• Lots of Under the hood Fixes
• Change Thermal Gaming Mod to Original Thermal (due its bad using that thermal)
• Original UI now Fits all DPI
Screenshot
There is 2 Theme available to select, Doze Manager, also Battery manager, Kernel Checker and Experimental feature ( New UI V 1.6), Neomorphism UI
ROAD MAP
Tap for Full Screen View
v0.2.1 Cannot detect Xenium kernels, please fix this
{Mod edit: Quoted post deleted}
Thx, dev..
Problem solved
Snow and non snow variant
What is the difference between snow and non snow variant? and how to know my device is snow variant, or non snow?
Kucing menangid said:
What is the difference between snow and non snow variant? and how to know my device is snow variant, or non snow?
Click to expand...
Click to collapse
Snow have snow effect and non snow doesnt have it... open battery manager if thereis a snow falling apart then your version is snow. if doesnt. its not snow
Features and Description :
Azure App is a profiler app wich have total 8 of profile, each profile have different kind of tunings and different processor have different kind of tunings too. and thereis no placeabo effect in this app nor collect your data.
so here is the Profile simple explanation :
- Chill = Chilling with social media, youtube and small games without worrying about battery drain.
- Chill Max = Chill with more performance
- Smart Casual = Near Default kernel Settings but with better Mem management and better CPU tunings
- Low IQ = Have Performance between Chill and Lazy Plus, Best for Social media and some multitasking. ( New )
- Fast AF = Means hope to push your phone to the limit = more heat
- Game Mode = enchanted version of Fast AF with slightly improve CPU consistency and restrict app usage
- Lazy Boi = Extreme Low power profile that hope to maxed out battery backup will cause LAG !
- Lazy Plus = up to 1.5x better performance than Lazy boi but hope still have similiar Battery Backup
Supported Processor type
- SD636HMP/EAS/OC
- SD675EAS
- SD660 non OC
Just Remember Each kernel / device have totally different tunings. and this is not a universal App that works on all kind of ****
And dont use other module otherwise will destroy enything..
For More Information you can visit this channel..
https://t.me/r0thAzureApp
Also Check Azure App Website
https://r0thbaby.github.io/AzureAppWebsite/
Love my work ? You can buy me a cup of coffee
https://www.paypal.me/r0thbaby
Cheers
r0th Baby.
Status : ALPHA
Version : 0.2.4
last Update : 13/06/2020[/QUOTE]
Changelog 0.2.4
- App now works on all sdm636/sdm660/sdm675EAS devices/kernel/rom/stock rom with fixes inside ( PLEASE UNINSTALL THE OLD APP VERSION AND INSTALL THIS VERSION )
- Mem setting now more battery oriented
- Some profiles more battery oriented
- Ultra ram setting now patched with LMKD settings trying to prevent instantly getting closed and hold more app inside memory ( BETA )
- X00T thermal change to Backup and Delete Thermal ( for all kind of phone )
- Ultra Battery saving setting changed to more battery oriented
- Fix Visible and non Visible bugs
- Lots of under the hood changes not worth writing about, but equally important
Thanks to @project_gh0st and https://instagram.com/fake.itt team for the icon. dont forget to follow the Instagram for more Cool Content
Changelog 0.2.3
- Added new kernel support for Requiem
- Added new feature Ultra Ram Setting
- Chill become slower ( More Battery Oriented )
- Change theme now required to restart app ( Prevent mem leak )
- Change App icon and other icon, thanks to Ghost
- Reduce APK size by 1mb+ ( now app much faster )
- Change Activity now will have garbage collection triggered
- Fix lots of bugs ( Visible and non Visible bugs )
- Lots of under the hood changes
Older Changelog 0.2.2
- All profile except Low IQ slightly improved ( Battery Oriented )
- Introduce 3rd UI -> Neomorphism UI : Tips -> Tap azure logo to reset profile back to default
- Change theme now required no restart
- Lot of fixes including for violet and zen+ also more bugs fixes
- Mem management now Battery Oriented
- Hack kernel checker detection so its slightly faster
- Custom doze tweak improved
- Lots of under the hood changes
Older Changelog 0.2.1
- Support Xenium Kernel ( EAS )
- Support Zen+ kernel ( STOCK )
- Support Violet device with Azure Kernel
- Source Clean Up
- Remove manual kernel checker, and become Automatic kernel Checker, more fast, more flexible, more easy to use
- Each UI now will have toggle to switch between the UI
- Fix TRB GameIT Mode Detector for Both UI error
- Fix Mode checker issue
- Stupid IQ now using some lazy boi settings ( can be seen in mode checker log 2)
- Fix Chill lock Issue
- Improve some profile for some kernel
Older Changelog 0.2.0
Changelog 0.2.0
- Support Wolf Kernel ( Caf, Non Caf, EAS)
- New Ultra Battery Saving
- New Experimental UI
- New quick tiles now working as free up memory
- Improve Custom DOZE Tweak
- Fix New UI Bug
- Fix Internal Conflict
- Lock Chill Performance
- Chill Max now fully unlock the performance
- Prevent Lazy Boi get extra performance
- EAS TUNINGS Is In ALPHA STAGE( DONT HOPE TOO MUCH, I WILL KEEP UPDATING EACH EAS PROFILE ! )
- Lots of under the hood changes
Older Changelog 0.1.9
- Fix some bugs in new Ui and Original UI
- Change Original Thermal to Thermal Option
- New Experimental feature UI
- Add Cryzen Kernel Support
- Add new mode Low IQ = Have performance between Chill and Lazy plus
- Custom Doze tunings improved
- Source Cleanup ( Reduce APK size by 90%+ and Reduce installed size by 35%+ also moderately increase app performance )
- Cheking kernel more faster than before
- Fix all typo in some modes
- Lots of under the hood changes
Older Changelog 0.1.8
Change log 0.1.8
• Fix Issue where Lazy and Lazy Plus not giving a lag at all
• Fix New UI bug
• Fix Mode Checker
• Better Looking New UI
• All modes for all supported device / kernel has been refreshed UP TO 1.5x BATTERY SAVING WHILE MAINTAINING ALMOST SAME PERFORMANCE
• New Doze Manager (Located in Experimental Feature)
• New Once you turn on the new UI, it will save and you dont have to turn on again after closing the app
• New HD Icon has been refreshed by Albert Wesker
• New System Tweak with search and match (So no placebo effect Given)
• Better Memory Management on all modes
• So much Under the hood change
• Lots of Under the hood Fixes
• Change Thermal Gaming Mod to Original Thermal (due its bad using that thermal)
• Original UI now Fits all DPI
There is 2 Theme available to select, Doze Manager, also Battery manager, Kernel Checker ( AUTOMATIC KERNEL CHECKER ) and Experimental feature, Neomorphism UI
ROAD MAP
What is the defferent between show and non show?
Tarif.tk said:
What is the defferent between show and non show?
Click to expand...
Click to collapse
Snow effect and no snow effect
This app delete all my music form sd card whay!! It happens when i cleaned cached dada. I know Cached dada does not mean to delete music file trush app.?
Tarif.tk said:
This app delete all my music form sd card whay!! It happens when i cleaned cached dada. I know Cached dada does not mean to delete music file trush app.
Click to expand...
Click to collapse
No way it could delete your music. ive only delete cache from dalvik. it must be something else. no music stored to dalvic cache
@r0th Baby Thread is being closed as it is a duplicate of this thread. Please note duplicate threads are not allowed as per the forum rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
Click to expand...
Click to collapse