[Kernel][FEATURED] Venom Kernel v3.1 [aio_otfp][MM][N] - K3 Note Original Android Development

[Kernel][FEATURED] Venom Kernel v3.1 [aio_otfp][MM][N] - K3 Note Original Android Development

{
"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"
}
Venom Kernel for K3 Note (aio_otfp) -- Based on Renice kernel source
Venom is designed for maximum performance and battery backup. It is made for people who depend on their phone every day.
It is feature Enriched kernel which makes your device even better than before.
Compiled with UBERTC 6.x
Features :
RGB color control
Working LED.
Vibration control using thunderquake engine module by varun.chitre15
Performance optimizations
USB fast Charging enabled by default
TCP Congestion Algorithm (TCPCA) set to Westwood by default
All other TCPCA added
Double tap to wake enabled
So much customisable dt2w, like screen area, time for tap, relative distance between taps... Much more
Fixes for blueborne bluetooth vulnerability at kernel level
Entropy tweaks -- Increased entropy values in random.c
Network tcp window tweak -- Lock window size to full for maximum speed
Enabled Forced fast charge
CPU governors :
(In alphabetical order)
Alucard
Conservative
Darkness
Intelliactive
Intellidemand
InteractiveB
InteractivePlus
Ondemand
Pegasusq
Performance
Poison --- Default custom governor made by me (based on ThunderX)
Powersaver
Renice
ThunderX
Userspace
Wheatley
Features of my Poison governor :
Dynamic CPU frequency transition mode engine. More info in Poison governor thread.
Smoothness tuning.
Best governor for this device because it is K3-specific
Custom tunables :
Can be found here, in my poison governor thread.
Has a total of 12 custom tuneables !!!!! :laugh::victory::highfive:
NOTE : There are 21 only for A7000-a and K3 release only has 12 tunables.
https://forum.xda-developers.com/lenovo-a7000/development/explanation-poison-cpu-governor-t3691304
(All information about the modes and tuneables in Poison governor thread)
Installation :
For custom roms:
Reboot to recovery
Flash the Kernel Zip
Reboot to system and Enjoy
For Vibe/Bootlooping Roms:
Reboot to Recovery
Take Nandroid backup of boot partition
Unpack ROM's boot.img (present in ROM zip almost always)
Replace the kernel file (Image-gz.dtb, bootimg-kernel, zImage) with proper name
Repack the boot image and flash
Reboot to System and Enjoy
Download links and Changelog :
See second post
Works Better in Custom roms (MM and N (based on MM libs) only)
Stock + Vibe Roms also Supported [MM only]
Note:
* Take a Nandroid backup before installing
Appreciate me by thanking me... Or... You could donate to me if you're an Indian!!!
Donation :
How to donate ??
---> Simple. Send me a PM or mail me ( [email protected] ) and say that you're willing to donate. Further instructions will be sent by me.
---> Or you can simply gift me xda ad-free
I also want to build venom for myself!
Sure! You can find the link for the venom kernel source below in xda DevDB info.
The source link is for A7000 device only so it doesn't work on K3 out of the box.
Everything that venom has is present in the given source link.
You can pick the features from there and Base it on renice source by sandeep.sethi
XDA:DevDB Information
Venom Kernel for aio_otfp [MM][N], Kernel for the Lenovo K3 Note
Contributors
tanish2k09, Sandeep.sethi, GSandeep, daniel_hk, Aryan Kedare, Rohan Taneja, Team M.A.D
Source Code: https://github.com/tanish2k09/Kernel_aio_row-Venom-S/
Kernel Special Features: Custom CPU governor, custom code, dynamic tuneables
Version Information
Status: Stable
Current Stable Version: 3.1
Stable Release Date: 2017-11-15
Created 2017-11-15
Last Updated 2018-04-22

Latest build :
Venom carnage edition :
http://goo.gl/r5KhkA
Old builds :
http://goo.gl/BuwKEh
(Venom kernel initial maximum edition)
Changelog :
Latest Build (Carnage) (25122017) :
Code:
1) Tweaked poison for more performance. Now you will feel that kernel is much more smooth than ever.
2) Added vibrator engine with real-time linking with poison. You'll feel it when you try yourself and see what this means.
3) Upgraded to dt2w 2.0 with haptic feedback (customisable vibration level) and more efficient structure and checks. My code is 1/3 of original code. Now dt2w is much faster and smoother.
4) Livedisplay fixed thax to painkiller3
5) WiFi autoconnect fixed thax to [user=4948627]@daniel_hk[/user]
6) Open hotspot fixed (use hotspot fix zip by sandeep) with venom
7) Added pocket mode override mechanism. Now you can tap 3 times within 0.8 seconds to override proximity sensor. Number of taps and timeout is customisable with poison.
8) New tunables details :
a) dt2w_vibe : Control vibration level on dt2w. Change to 0 to disable dt2w haptic feedback.
b) vibrator_on_lock : Disables vibrator on screen off completely. Capacitive buttons won't vibrate on screen off, notifications won't vibrate phone on screen off, but calls will turn screen on and then vibrator will activate. This is a good feature for those who want no notification disturbances but also don't want to enable silent mode.
c) pocket_mode_dt2w_override_taps_number : This is the value of the number of taps that you will have to tap within timeout to wake up the screen even in proximity mode.
d) pocket_mode_dt2w_override_taps_timeout : This is the value of the time in milliseconds within which you will have to tap to override pocket mode.
e) dt2w_tap_distance : Merged dt2w_tap_distance_x and _y into a single variable and changed the distance calculation from rectangular linear to circular radial. This us the radius of the circular region with the center as the first tap coordinates, within which you will have to tap second time within timeout to activate dt2w. Easy.
9) Merged x and y distance tunables into a single radius.
10) Enabled 5Ghz WiFi by default (thanks to daniel_hk) (request by [user=4695623]@FPSUsername[/user])
11) Enabled 7 cores while booting. (Thax to gsandeep)
Build 15112017-1244 :
Code:
Initial release.

Misc
Deleted and reserved again.

Users told me that the link I posted was bootlooping.
I've uploaded a last known working stable build instead.
Link in post 2 updated.
Kindly re-flash

tanish2k09 said:
Users told me that the link I posted was bootlooping.
I've uploaded a last known working stable build instead.
Link in post 2 updated.
Kindly re-flash
Click to expand...
Click to collapse
Great Work!
And
Im here for testing your kernel.

Works on stock 6.0 roms?
Or just for 7.0 LOS based?

Is there a posivility having bootloop if normal flashing it kn vibesavon 3.6?

inouext said:
Works on stock 6.0 roms?
Or just for 7.0 LOS based?
Click to expand...
Click to collapse
It works on all roms which are compatible with renice kernel.
TatsuyaKaneki2015 said:
Is there a posivility having bootloop if normal flashing it kn vibesavon 3.6?
Click to expand...
Click to collapse
Same behaviour like renice kernel.
I have mentioned that I don't have device so you can't expect me to tell you anything related to working or not working.
However, since this kernel is based on renice, it will do the exact same things like renice kernel. Think of this kernel as a renice kernel but with some extra features.

Anyone tested this, how the performance after this??

Eduardo27 said:
Anyone tested this, how the performance after this??
Click to expand...
Click to collapse
You should try yourself instead of asking others.
Your own opinion matters. :good::highfive:

u did a good job on poison...getting good screen on time...but there's some drawbacks like it lags while trying to play 1080p 60 fps in youtube...and lags while browsing with chrome
yup it's kind of laggy... even while browsing through photos..using es file manager+so on......
I'm in mode 1....I know mode 2 would be smoother....
but I'm liking the battery backup.....is there any possible way to tune up it a little more to get a little more performance +backup balance?
@tanish2k09

Cpt.mactavish said:
u did a good job on poison...getting good screen on time...but there's some drawbacks like it lags while trying to play 1080p 60 fps in youtube...and lags while browsing with chrome
yup it's kind of laggy... even while browsing through photos..using es file manager+so on......
I'm in mode 1....I know mode 2 would be smoother....
but I'm liking the battery backup.....is there any possible way to tune up it a little more to get a little more performance +backup balance?
@tanish2k09
Click to expand...
Click to collapse
It is quite obvious that battery backup and performance are inverse of each other. Both can't be perfect at the same time. One of them has to be sacrificed for other.
I'm warning you that increasing performance WILL decrease BB.
In case you still want to proceed to a better performance, do following :
1) Change poison tuneable "Awake_ideal_freq" to the max freq (16xx)
2) Or use some more powerful governor. Note that others aren't mtk-specific so battery backup will be less than poison 100%
3) While the step 1 should be enough for faster processing, you may use poison with addition to mode 2.
4) Change ROM to other than compiled nougat ones. They have a lag problem with low cpu frequencies. Marshmallow should be fine.
5) For faster pic loading, it has been tested that fiops iosched performs fastest. Slightly noticable.
6) Use darkness governor as an alternative for slightly performance oriented device.
// Destroy the thanks button on my post and kernel if you like it

Sir, does this kernel support with lenovo a7000 plus? Because i got bootloop when flash the kernel. Not even reaching the boot animation, its just get on the first lenovo logo then just black screen, and sometimes keep rebooting. Really wanted to try it.
device : Lenovo a7000 plus
twrp : 3.1.1-3 when install rom then 3.0.2-7 to install modem patch for a7k plus.
rom : Daniel_hk's latest LineageOs rom, (31oct)

tanish2k09 said:
It is quite obvious that battery backup and performance are inverse of each other. Both can't be perfect at the same time. One of them has to be sacrificed for other.
I'm warning you that increasing performance WILL decrease BB.
In case you still want to proceed to a better performance, do following :
1) Change poison tuneable "Awake_ideal_freq" to the max freq (16xx)
2) Or use some more powerful governor. Note that others aren't mtk-specific so battery backup will be less than poison 100%
3) While the step 1 should be enough for faster processing, you may use poison with addition to mode 2.
4) Change ROM to other than compiled nougat ones. They have a lag problem with low cpu frequencies. Marshmallow should be fine.
5) For faster pic loading, it has been tested that fiops iosched performs fastest. Slightly noticable.
6) Use darkness governor as an alternative for slightly performance oriented device.
// Destroy the thanks button on my post and kernel if you like it
Click to expand...
Click to collapse
your fastcharging seems to be good too.....I'm using gsandeep's unofficial RR....so far it is the best rom for k3.....
I've changed to mode 2..which is performance oriented ....and performance has increased..... but I thought is there any tweak to be made for tweaking mode 1...for slight performance increase...

Cpt.mactavish said:
your fastcharging seems to be good too.....I'm using gsandeep's unofficial RR....so far it is the best rom for k3.....
I've changed to mode 2..which is performance oriented ....and performance has increased..... but I thought is there any tweak to be made for tweaking mode 1...for slight performance increase...
Click to expand...
Click to collapse
Step 1 and step 6
Good to hear that you're liking the kernel. Unfortunately there are only 12 customisable variables in k3 version. My a7000 has almost everything customisable from cpu modes to dt2w screen trigger area to gesture sensitivity...

tanish2k09 said:
Step 1 and step 6
Good to hear that you're liking the kernel. Unfortunately there are only 12 customisable variables in k3 version. My a7000 has almost everything customisable from cpu modes to dt2w screen trigger area to gesture sensitivity...
Click to expand...
Click to collapse
btw,your kernel doesn't support livedisplay of LOS/LOS based roms...any fix for that?

Cpt.mactavish said:
btw,your kernel doesn't support livedisplay of LOS/LOS based roms...any fix for that?
Click to expand...
Click to collapse
I didn't get the time to add that.
I can't help you with it this year at least.
My main motive for releasing this kernel was to prove my skills with my poison governor. There are people like daniel_hk himself who doubt me greatly. He is failing to understand that I am not underskilled, but rather I prefer to not spend the time I have right now as a student, into ROM development.
With poison, you would experience at least 10-15% battery increase and a decent performance, unless needed for heavier tasks, which can be adopted to using the modes.
I hope you liked poison. Maybe early 2018 I will update this kernel with more new features. One of them being livedisplay. If you actually see, there isn't too much time to wait. It's just a month approx and you'll not even know when it passes. That's the thing about time. It's mind-boggling
//Some people need to learn to press the thanks button.

looking for your next updates....with livedisplay....and hope to have more optimizations...on backup+minimum usable performance

Battery Backup
Please tell me about battery backup of k3 note after flash this kernel in vibe os . ???

Like Renice kernel v11, sometimes wifi dropped and not auto reconnect. Can you fix that in next version?

Related

[KERNEL] [GPL] [4.3/4.4] [8th June] Oxydo -V18

Presenting Oxydo kernel for the Nexus 7 Grouper and Tilapia
{
"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"
}
1. Features
Nothing here. Move along to post #2. See the changelog.
[/LIST]
2. Instructions
Flash in recovery. You know how to.
3. Warning and disclaimer
The usual. I am not responsible for any harm caused to your tablet by this kernel. You decide whether you want to flash this or not and therefore you face the consequences. But don't worry. This has been tested and the results were pretty good.
4. Downloads
https://www.dropbox.com/sh/pwe87rpzciojb9z/I3UHL9pLE4
Notes are available in changelog.
GENERAL:
1) For modules ZIPs, extract and insmod manually.
2) The last one is usually for the latest version of Android.
5. SOURCE: https://github.com/souljaboy11792/oxydo-grouper
6. Credits
In no specific order
franciscofranco
flar2
Mahdi-786
Metallice
spasrksco
_motley
ashik992
faux123
show-p1984
intersectRaven
davidmore
poondog
Tasssadar
redeyedjedi
dexviajiboy
Everyone else whose patches I may have used directly or indirectly
Google and Android
Supporters and testers and well-wishers and haters and random people.
Allah Almighty

7. Changelog
V1 (XX)
Initial release
Linux 3.2.46
Franco's hotplug
Various small changes
V2 (XX)
JRCU
Scaling bug fixed. Goes as far as 102MHz now.
Slight (pointless, but fun) increase in RAM (about 0.5MB), as logger is compiled as module.
Included hso.ko and ppp_async.ko modules on user demand. ( @xDeadaheaDx )
Included Lazy CPU governor and ZEN I/O scheduler on user demand. ( @ckisgen )
Updated to Linux 3.2.47
V3 (XX)
Merged changes required for 4.3.
Updated to Linux 3.2.49.
Fixed ADB issues that persisted on stock kernel.
No longer build the modules because I think unsigned modules loading is messed up now. Have to check.
V4 (XX)
Ramdisk from M-KERNEL. Fixes all issues.
New method for enabling/disabling logger (more info in 3rd post).
V5 (XX)
Sysfs interface to control min/max backlight. Highly experimental. Referenced M-KERNEL. Check post #3.
V6 (XX)
Backlight control still isn't fixed. Going to try something else now.
sweep2wake and doubletap2wake in experimental versions. Check post #3.
V7 (XX)
New code for min/max backlight and brightness. Check post #3
sweep2wake and doubletap2wake given newer life thanks to flar2.
Reverted to 446MHz GPU OC.
V8 (XX)
Added shortsweep option.
Enabled AUDIT to fix SELinux issues.
Added a table in /sys/devices/system/cpu/cpu0/cpufreq (gpuc_UV_mV_table) that shows the clock speed and voltage applied to GPU. Intended for it to be rw but it cannot be saved for some reason.
Updated ASIX drivers to USB 3.0.
hso and ppp_async as modules.
CIFS (optional) available as module.
Enabled KSM.
V9 (XX)
Decreased s2w timeout to allow more time for valid swipes.
Fix s2s in portrait mode.
Fix mounts in the ramdisk. They are as hey should be now.
Added USB DAC patches (please try this and lemme know whether this works)
Added USB host mode patch.
May be more changes but I'm too tired right now.
V10 (XX)
Dynamic Fsync. Credits - faux123.
Reverted the USB hostmode patches that broke OTG.
smartassv2 governor as a module. Credits - Ricardo Gomez.
Changed dithering mode to fix gradients.
Another attempt at USB DACs. Please test it.
700MHz GPU OC as default. Set it to boot at 446MHz if you want to (will stick properly). Certain freqs that are not listed as steps in the DVFS will not stick.
V11 (XX)
600MHz GPU OC as default. Scales properly now. Don't increase in TricksterMOD (doesn't stick between boots; supposed to be that way because 600+MHz causes screen turds). Decreasing works.
V11-446 (XX)
V11 with 446MHz GPU default. Should reduce FCs.
V12 (11th October, 2013)
Switched to 484MHz GPU OC.
Switched to SLAB on user request.
Introduced wake_locks to help with wake functions.
Introduced sysfs parameter to control area of screen that can be used to complete s2s.
V13 (8th November, 2013)
Now has s2w and s2s portrait mode area parameters exposed to sysfs.
PPP and hso now built inline
smartass2 tunables exposed to sys/devices/system/cpu/cpu0/smartass2. Takes ages and at least ten Terminal Windows to configure.
Uses zImage, so compatible with every 4.3+ ROM for now. Even 4.4.
cifs.ko module already in ZIP file so bye-bye modules.zip
V14 (27th November, 2013)
Now s2w and s2s trigger area are in sysfs (properly; no modular interface now).
logger enabled by default.
Use UKSM
GPU OC till 750 supported (may be unsupported in some devices; but it works).
OTF scaling included.
t3_variant info in debugfs.
Include smartmax governor from maxwen. Really good.
Updated to 4.4 source.
V15 (16th December, 2013)
All s2s trigger area functions are in android_touch (even landscape ones)
USB hostmode patches added. Check FAQ
USB DAC patches added but I dunno if this works
logger has been allocated even less RAM. Some of it is there just so you can debug crap.
audit debug is disabled.
interactive governor updated from Francisco Franco's repo.
smartmax is now the default governor.
Updated to 4.4.1 (??) source. I don't really remember.
Updated all the way to Linux 3.2.53 (the last in the 3.2.y series). First ever grouper kernel to do so. There are some nasty reverts though.
V15 SELinux=disabled (19th December, 2013)
NOTE:FLASH THIS ONLY IF THE OTHER VERSION DOESN'T WORK. PLEASE HAVE A BACKUP OF THE ENTIRE TABLET ESPECIALLY THE BOOT PARTITION BEFORE EXPERIENTING.
SELinux disabled. Hopefully fixes fragmentation issues over Kit Kat ROM. Just a temporary fix for now.
V16 (2nd February, 2014)
Linux 3.2.54.
interactive governor updated from Francisco Franco's repo.
BFQ scheduler
V16-aospal (2nd February, 2014)
Selinux disabled for a few kk ROMs like aospal.
V17 (11th April, 2014)
Linux 3.2.56.
SELinux disabled by default.
f2fs support (thanks @ss2man44). RAMDISK NOT INCLUDED!! Flash LegoKernel first and then oxydo over that to have f2fs and oxydo kernel.
baseband_xmm wakelock given timeout. More info in post #3.
Stock hotplug.
Various changes here and there.
V18 (8th June, 2014)
Merged changes for 4.4.3 from Google
Revert to Franco's initial hotplug routine, and instad of disabling screen, just disable framebuffer for faster wakeups. Courtesy of franciscofranco.

8. FAQ
1. How do I enable logger? What about hso and ppp_async?
Ans:
For builds with modules:
Download the modules zip. Unzip them to you sdcard, and note the path. Fire up the Terminal. Issue these commands one by one:
Code:
su
insmod /path/to/logger.ko (only in V2)
insmod /path/to/hso.ko
insmod /path/to/cifs.ko
insmod /path/to/ppp_async.ko
To check whether they are working (they are, don't worry):
Code:
lsmod
Should output something like
logger.ko 54334 [permanent] ... blah.
You can also try:
Code:
dmesg | grep "logger"
dmesg | grep "hso"
ppp_async doesn't show any message.
To disable hso.ko and ppp_async.ko (you can't disable logger.ko once it's insmod'ed, but a simple reboot will rmmod it):
Code:
rmmod hso.ko
rmmod ppp_async.ko
For builds without modules:
To enable logger (it is off by default), issue this command in Terminal Emulator
Code:
echo "1" > sys/kernel/logger_mode/logger_mode
To disable it, just echo 0 instead.
2. Why won't my device reach 51MHz even though it's listed in the frequency list?
Ans: I have set the min rate for G cores to 102MHz. 51MHz IMO is a very stupid frequency in that it will do nothing basically. Even my 3 year old cellphone doesn't stay at 51MHz. It should be a LP core frequency (it actually was) but since Franco's hotplug driver doesn't call on the LP core, it's not reachable.
3. How do I control minimum - maximum backlight through sysfs?
Let me begin by saying that this feature is highly experimental. I can tell though that it works.
Okay so in /sys/module/board_grouper_panel/parameters you'll see two files:
min_bl - Write in a reasonable value preferably at least 30 less than max_bl. Default is 10. Not safe. Switch to 11.
max_bl - Write in a reasonable value preferably at least 30 more than min_bl.
This is what happens. *takes deep breath*
When your brightness is greater than zero but less than the min_bl, it gets changed to the min_bl. And when it's greater than max_bl, it's changed to max_bl. Otherwise it's just normal brightness levels (where's the fun in that, right? )
PLEASE DON'T WRITE THE VALUES OF min_bl OR max_bl WHILE YOU'RE HIGH, DRUNK OR JUST DOWNRIGHT BAT-CRAP CRAZY!
There's no limit to the madness that may happen as a result.
4. How do I configure sweep2wake and doubleetap2wake? What exactly are they?
Sweep2wake and doubletap2wake are basically two versions of the same thing - they wake your device up after you have put it to sleep (not metaphorically) without using the physical buttons on the side. This is still slightly buggy. If at first it doesn't work. Touch the screen once and then tap it twice.
For sweep2wake/sleep you basically swipe along the bezels (not on the bezels though) where the soft keys would be.
For doubletap2wake, just tap twice on the screen during sleep, and it should wake up.
To configure sweep2wake go to /sys/android_touch and open up sweep2wake
0 = disbaled
1 = sweep2wake/sleep
2 = sweep2sleep
To configure doubletap2wake go to /sys/android_touch and open up doubletap2wake
0 = disabled
1 = enabled
To configure shortsweep go to /sys/android_touch and open up shortsweep
0 = disabled.
1 = enabled.
This drains battery a little faster than stock would, so yeah. Don't use it (i.e. disable it) if you want to save battery, or set up a script.
There is also a wake_timeout file. It holds the time that the dt2w wakelock will remain active after the screen is suspended.
NOTE: s2w wakelock times aren't configurable and it will stay on for 15 seconds after the screen has been suspended.
Insert the time in seconds. (60 = 1 minute; 3600 = 1 hour)
If both are disabled no wakelocks are registered and held.
5. How do I get USB OTG to work?
Go to /sys/kernel/usbhost.
echo 0 to usbhost_fixed_install_mode.
I haven't tested (hostmode, and fast charge/hostmode charge) this myself, so feedback is appreciated.
You need StickMount unless your ROM supports native OTG.
6. Why is SELinux disabled?
To get it booting on some Kit Kat ROMs. Booting in permissive may work, but I haven't tested it yet.
8. Why is my device so awesome now?
OH STAHP IT YOU! And you weren't reading carefully enough, otherwise you would have pointed out that I missed #7.
69. <== LOL!11eleventy!!1! How do I configure baseband wakelock timeout?
Go to /sys/module/baseband_xmm_power/parameters and open up the bb_timeout file.
0 means the wakelock will be held for 1 second after it is acquired.
Values are in seconds.
I used timeout instead of disabling it completely because, although there have been no problems reported, thus far, to arise from this modification, it's better to be safe (not disabling completely but making it timeout after a while) than sorry (losing functionality although it seems unlikely)
9. A POST ON RECOMMENDED SETTINGS AND STUFF
"Interactive @ 1.5GHz and GPU @ 484MHz (or even 446MHz) + no screen wake controls (if you don't use them) should give you excellent battery life and performance. You can adjust CPU speeds too."
- sgt. meow
Idea of @keneth_c
Oh and this works awesome with the IceColdJelly AOKP ROM for Tilapia. Be sure to try it out.
Works fab on 4.3 stock. Don't believe in benchmarks though.

First downloading now
Sent from my Nexus 7 using Tapatalk 4 Beta

Sweet gonna try this out
Sent from my Nexus 7 using Tapatalk HD

Using it and loving it....THANKS MAN.... :good:

Glad you guys like it. I'm building v2 right now. But it'll be a number of builds before I get the next bits right.

Take Your time......we are here for testing...

New kernel for our n7. Fine:thumbup:
Sent from my Xperia Neo using xda app-developers app

So any UV UC or OC support? Most probably to be announced in v2....

Thanks for the kernel, will test soon!

This kernel has proper OC and UV/OV. It works for me.

Think I'm gonna test this - looks interesting... :cyclops:

sgt. Meow said:
glad you guys like it. I'm building v2 right now. But it'll be a number of builds before i get the next bits right.
Click to expand...
Click to collapse
your kernel is by far the best...it made ppsspp games smoother.......

Will check it out soon! Should be interesting to see where this goes in 4.3. You should try build with the optimizations that are in Purified Kernel. And add lower brightness support (from M-Kernel)
Sent from my GT-I9300 using xda premium

@sgt. meow is it possible to update to 3.4?
Sent from my Nexus 7 using Tapatalk 4 Beta

infatality said:
@sgt. meow is it possible to update to 3.4?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Its already 3.2
Not an easy job that
Sent from my Nexus 7 using xda app-developers app

poondog said:
Its already 3.2
Not an easy job that
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Haha.. Was wondering if possible.. Well.. Good to see a kernel updated beyond 3.1.10
Sent from my GT-I9100 using Tapatalk HD

infatality said:
Haha.. Was wondering if possible.. Well.. Good to see a kernel updated beyond 3.1.10
Sent from my GT-I9100 using Tapatalk HD
Click to expand...
Click to collapse
Well to put this in context, its very easy to update from say 3.0.86 to 3.0.87, its only a diff patch and its applied and built in 3 mins on a fast machine.
To update from 3.0.y to 3.1.y, or in this case 3.1.y to 3.2.y is a lot of work, there's no patch for it as its all porting if code mostly manually, very big feat. Its nearly impossible
Sent from my Nexus 7 using xda app-developers app

Saber-Toothed-Squirrel was also updated to 3.2.46.
And yes it is possible. But it won't be an update as much as a slight change in the Makefile. I tried it once.

[MOD] Tweak Me v1.0.3 [CPU | GPS | RIL | RAM | SWAP | +MORE]

~RESERVED~

Did you really thiink that it is necessary to flash a ROm after Flashing this MOD????

blogodoblogodo said:
Did you really thiink that it is necessary to flash a ROm after Flashing this MOD????
Click to expand...
Click to collapse
You flash it after you have a ROM installed. Same as if you were to flash Sultan's aroma installer to tweak the kernel.

Maybe i didn't understand well, thank you, just ask to be sure... it would be the first time that a MOd need to be flash before installing ROm...
Okéy sorry, my fault:good::good:

Yay cool, another mod for our senny. but what can i do with this I can't do within ViperS Rom?
I can adjust cpu clock with the vipers.zip
I can decide on which continent i am, to select right gps settings,
I can adjust capacitative backlight brightness in venom tweaks
Only thing i can't is change the RIL. But what benefits do I have by changing the RIL?
I don't want to talk bad about this, no. Thanks for the developement this old device is getting. Maybe this is usefull for others. I think I forgot that not everyone is using ViperS rom ^^

Eezay said:
Yay cool, another mod for our senny. but what can i do with this I can't do within ViperS Rom?
I can adjust cpu clock with the vipers.zip
I can decide on which continent i am, to select right gps settings,
I can adjust capacitative backlight brightness in venom tweaks
Only thing i can't is change the RIL. But what benefits do I have by changing the RIL?
I don't want to talk bad about this, no. Thanks for the developement this old device is getting. Maybe this is usefull for others. I think I forgot that not everyone is using ViperS rom ^^
Click to expand...
Click to collapse
All of the options are different from what can be done, for example: changing your min frequency, isn't done in rom.zip and it also doesn't disable pnp manager. You can't decide/choose what continent you're in. You also can't select custom brightness levels for buttons. You may benefit from better coverage/data speeds.
I am not going to put anything in this that can be done in ROM as that would be pointless [emoji6]
Sent from my HTCSensation

I want Sweep2wake to Vipers 5 PLEASEEEEEEEEEEEEEEEE

hinxnz said:
All of the options are different from what can be done, for example: changing your min frequency, isn't done in rom.zip and it also doesn't disable pnp manager. You can't decide/choose what continent you're in. You also can't select custom brightness levels for buttons. You may benefit from better coverage/data speeds.
I am not going to put anything in this that can be done in ROM as that would be pointless [emoji6]
Sent from my HTCSensation
Click to expand...
Click to collapse
Yeah I thought so, you're right. These tweaks, e.g. button backlight or cpu clock, are more specific.
Plus, I just checked my signal. My bedroom is in the ground floor and I barely got any signal. Now it seems to be stronger and I don't necessarily have to stand near the window to call someone. :good::laugh:

hinxnz said:
Tweak Me v1.0.1..........................
.
Designed for ViperS v5.x
.
.
.
.
......About
CPU tweaks able you to adjust your min. frequency and throttling without disabling PNP Manager
GPS configurations
RIL alternatives for your cellular radio
Capacitive buttons backlight brightness adjustment
100% compatible with ViperS v5.x but may also work with other ROMs
All tweaks are removable within the Tweak Me installer
More to come - your very welcome to contribute your ideas
.
......Installation
First make a Nandroid backup in recovery.
No wiping is necessary
Then flash as you would a ROM
.
......Changelog
...........v1.0.0
..... - Initial release
...........v1.0.1
..... - Added more CPU tweaks [Performance Plus & Power Saving Plus]
..... - Added another RIL [HTC-RIL_4.0.0035HMQ]
.
......Downloads
.Tweak Me v1.0.0 - https://dl.dropboxusercontent.com/u/55494910/Tweak%20Me/Tweak_Me_v1.0.0.zip......MD5 - 7534D1DB535B41531950E499AE905205
.
.Tweak Me v1.0.1 - https://dl.dropboxusercontent.com/u/55494910/Tweak%20Me/Tweak_Me_v1.0.1.zip......MD5 - FAE3398476E8CB302B2EB243293E6384
.
.
If you like my MOD and want to show your appreciation just hit the thanks button in the
bottom left corner and rate my thread 5 stars in the top right corner.
Also I would like to thank you for using or trying my MOD!.
.
Click to expand...
Click to collapse
Hi, just added link to this thread in the FAQ thread. :good:
I'm going to try this MOD as I come back home, but I have a couple of questions:
Is it possible to set the CPU max screenoff frequency (in next releases of course)? Because in Venom Tweaks (after disabling PnPMgr) I can set any value in that field, but the value is always reverted to 192MHz... So I think it's not working at all.
Where did you find alternative RILs for this ROM? I tried to flash some RILs in the past but I completely lost mobile signal.
If I change button brigthness with your MOD, which settings should I keep in Venom tweaks for that option? Is "Default" ok?"
Thanks again mate
Eezay said:
Yeah I thought so, you're right. These tweaks, e.g. button backlight or cpu clock, are more specific.
Plus, I just checked my signal. My bedroom is in the ground floor and I barely got any signal. Now it seems to be stronger and I don't necessarily have to stand near the window to call someone. :good::laugh:
Click to expand...
Click to collapse
Which RIL version gives you the best results?

TheWall-[ITA] said:
Hi, just added link to this thread in the FAQ thread. :good:
I'm going to try this MOD as I come back home, but I have a couple of questions:
Is it possible to set the CPU max screenoff frequency (in next releases of course)? Because in Venom Tweaks (after disabling PnPMgr) I can set any value in that field, but the value is always reverted to 192MHz... So I think it's not working at all.
Where did you find alternative RILs for this ROM? I tried to flash some RILs in the past but I completely lost mobile signal.
If I change button brigthness with your MOD, which settings should I keep in Venom tweaks for that option? Is "Default" ok?"
Thanks again mate
Click to expand...
Click to collapse
Thanks it's not possible to adjust max screenoff freq. as it's not supported by kernel. Max screenoff isn't 192MHz though it's 1026MHz.
The RIL's are from the Sensation and the Ville C2. You won't lose mobile signal changing RIL's with this method as with the traditional HTC RIL's from the Radio/RIL thread, they contain other non compatible files that cause network loss.
Default is ok to choose in Venom Tweaks for button backlight. I choose 30 in mod, as I like it dim when it comes on in the dark.

hinxnz said:
Thanks it's not possible to adjust max screenoff freq. as it's not supported by kernel. Max screenoff isn't 192MHz though it's 1026MHz.
The RIL's are from the Sensation and the Ville C2. You won't lose mobile signal changing RIL's with this method as with the traditional HTC RIL's from the Radio/RIL thread, they contain other non compatible files that cause network loss.
Default is ok to choose in Venom Tweaks for button backlight. I choose 30 in mod, as I like it dim when it comes on in the dark.
Click to expand...
Click to collapse
Just flashed the zip: changed my RIL and dimmed capacitive buttons. Awesome job :victory:
Can you explain how various CPU throttling methods work? Are they related to some governor, or are they simply different versions of the "ondemand"?
Thanks again

TheWall-[ITA] said:
Just flashed the zip: changed my RIL and dimmed capacitive buttons. Awesome job :victory:
Can you explain how various CPU throttling methods work? Are they related to some governor, or are they simply different versions of the "ondemand"?
Thanks again
Click to expand...
Click to collapse
They tweak the ondemand governor.
- With the performance and power saving options, it adjusts things like the up threshold and sampling rates.
- With performance plus and power saving plus options, it basically has the same tweaks as performance and power saving options but also tweaks other frequencies such as two phase freq.
I could add an option to change the governor though but we only have ondemand, userspace, powersave and performance.

hinxnz said:
They tweak the ondemand governor.
- With the performance and power saving options, it adjusts things like the up threshold and sampling rates.
- With performance plus and power saving plus options, it basically has the same tweaks as performance and power saving options but also tweaks other frequencies such as two phase freq.
I could add an option to change the governor though but we only have ondemand, userspace, powersave and performance.
Click to expand...
Click to collapse
Nice :good:
I think you don't need to add the option to change governor: ondemand is the only one which is really useful.

First post updated with v1.0.2
- See changelog for more details.

Nice update, couple of questions though, I'm currently using Multi Swap at 60%
1. Will this clash - ie, do I need to uninstall multi swap?
2. Can I change your swapiness to 60% to have same configuration?

-Jonny- said:
Nice update, couple of questions though, I'm currently using Multi Swap at 60%
1. Will this clash - ie, do I need to uninstall multi swap?
2. Can I change your swapiness to 60% to have same configuration?
Click to expand...
Click to collapse
1 - Yes but when you install the Lite version, it will remove your existing MultiSwap installation anyway.
2 - The swappiness is set to 20 in the lite version and is recommended but yeah you can change it by either editing the init.d script or flashing the swappiness tweak again.
Edit: I may add swappiness options in a future release. Something like 10, 20, 40, 60.
I do find 20 is a good value though as swap doesn't fill to quickly and completely in most heavy RAM situations but it's there when needed and no decrease in performance noticeably what so ever.

network response problem
Hi,
I've a weird issue with rom sense : network responsiveness is very bad with rom sense like ViperS 5.1.0.
I've not this issue with a non sense rom (unorom, carbonrom...). Everything app open quickly. But it's very long with a sense rom.
So this mod can help me or not?
I give my RIL (if ti's the source of my issue) : 11.76C.3504.00P_11.29A.3504.18_M
Thanks

[Legenda] said:
Hi,
I've a weird issue with rom sense : network responsiveness is very bad with rom sense like ViperS 5.1.0.
I've not this issue with a non sense rom (unorom, carbonrom...). Everything app open quickly. But it's very long with a sense rom.
So this mod can help me or not?
I give my RIL (if ti's the source of my issue) : 11.76C.3504.00P_11.29A.3504.18_M
Thanks
Click to expand...
Click to collapse
That's not you RIL, that's your RADIO. Using this mod you can try a different RIL. Try the 4.0.0037 and see how it goes.

TheWall-[ITA] said:
That's not you RIL, that's your RADIO. Using this mod you can try a different RIL. Try the 4.0.0037 and see how it goes.
Click to expand...
Click to collapse
Ahh my radio!! good thought. I'm dl the mod and i'll try!
I keep you in touch.
EDIT : I think my issue is over. The network responsiveness is quick with my apps like Twitter.
Thanks

[T-Mobile TW][Nadia Kernel][05-March-2015][4.4.4][Faux Sound]Emotroid Team

- Nadia nightly Kernel Note 4 -
SM-N910F/ SM-N910G/ SM-N910T/ SM-N910W8
Introducing the Emotion Revolution Roms & Nadia Kernels for Android Devices.Emotroid Rom/Kernel is a modified, aftermarket firmware/Kernel distribution few Android devices (Note 2, Note 4, HTC M8). Based on the Android Open Source Project , Emotroid Rom & Kernel is intended to increase performance and stability over Android-based Devices released by sellers, for example, Samsung, HTC and so forth. Emotroid additionally offers a mixed bag of features & improvements that are not presently found in stock variants of Android.
{
"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"
}
*** Disclamer***
Your warranty is now void.
We are not responsible for any damage or problems you may have!
YOU are choosing to make these modifications.
Click to expand...
Click to collapse
First of all I want to say this that is one project which just started and gradually we will improve it. In this community there are very good developers and we are not traying to compete with them. This is just a hobby and we do it because we like Android. This kernel is only for SM-N910F SM-N910G SM-N910T and SM-N910W8 and we don't have plans to make it compatible with other versions of Galaxy Note 4. We hope that you will not only download the kernel but also you will leave your feedback with pros and cons and you should respect our efforts.
Don't be scared by the nightly denomination of the kernel.
Thread IndeX
POST 1: Kernel Information, Changelog, Credits,Screenshots
POST 2: Synapse, Recommended settings, FAQ, etc.
POST 3: Know/Reported issues
Request new features here
Features:
Quote:
Based on Samsung Open Source N910FXXU1ANIE
Compiled with Toolchain Linaro GCC 4.9.3 2014.12 Cortex A15
Linux version 3.10.0
PowerSuspend Driver
Intelli-Plug V3.9
Sweep2wake
Simple GPU Algorithm
Voltage Control
Intelli-Thermal
mDNIe Hijack Mode
Led Control
CRC Settings
Advanced TCP control
S-View flip cover hack
Selinux Permissive
Sched: LOAD_FREQ (4*HZ+61)
Reduced wakelocks
Frandom number generator
Synapse full support
March- 5 -2015 nightly r7
-Added KCAL - Advanced color control (Thanks to @savoca for his great job) check this thread for more info
March- 3 -2015 nightly r6
-Based on XXU1ANK4 (KitKat version) and compatible with "F,G,T,V,W8"
-Kernel compiled with Linaro Toolchain 4.9.3 2015-02
-FauxSound updated to 3.6
-Fixed some issues in FauxSound and Synapse
-cpufreq: Introduced new relation for freq selection Introduce CPUFREQ_RELATION_C
-Interactive Governor: Use CPUFREQ_RELATION_C
-Added Gentle fair sleepers (Synapse -> KERNEL TWEAKS)
-Enabled Kernel SamePage Merging (KSM) (Synapse -> KSM)
-Added key disabler (Synapse-> SCREEN/MISC)
-Added userspace vibration strength control (Synapse-> SCREEN/MISC)
-Changed some stuff in Synapse
-Reverted some commits
-Another minor changes
January- 27 -2015 nightly beta r5
-FauxSound implemented
-FauxSound in Synapse (Thanks to Placiano)
-Added high performance mode in Synapse->Sound
-Fixed battery drain on wifi (My fault)
-Reverted another commits
January- 16 -2015 nightly r4
-Fixed cpu voltage control (No more 0MHz frequency in cpu voltage table)
-ASoC: wcd9xxx: use hwdep node for codec calibration
-ASoC: wcd9320: use hwdep nodes to get calibration
-ASoC: wcd9xxx: Changes for High performance mode
-ASoC: wcd9xxx: Change PA on and VDDIO switch sequence
-ASoC: wcd9xxx: Avoid micbias glitches during audio playback
-In conclusion better quality sound on headsets
-Sched/fair: reduced latency
-Decreased DHD_PACKET_TIMEOUT_MS to 250 ms (Before 500ms)
-Drecreased time to enter sleep
-Net: wireless: Increased scan entry expiration to fit new scan time
-PM: devfreq: Use high priority workqueue
-Msm: kgsl: Report correct GPU frequency in sysfs
-Some minor changes
January- 11 -2015 nightly r3
-Added Frandom as module and set by default (Synapse>I/O>Frandom) "For more info check this"
-Network speed tweak
-Reduced wakelocks "wlan_rx_wake" and "wlan_ctrl_wake"
-dtsi: realigned voltages with userspace values (Thanks to twistedumbrella)
-cpu-boost more performance (Thanks to franciscofranco)
-sched: LOAD_FREQ (4*HZ+61) "For more info check this"
-Interactive governor imported from the Nexus 6 (No more lag on interactive)
-Added bluactive and interactive_pro governors
-Reverted some changes that made the kernel laggy in some cases.
-Selinux set to permissive by default
-Gpu: msm: for higher priority you want to use nice level of -7
-Now you can change the governor tunables from Synapse (Issue fixed) (Thanks for the tip to AndreiLux)
-Synapse shows all the available gpu governors (Thanks to my friend Friedrich!)
-Cleaned some things in Synapse
-Other minor changes
January- 4 -2015 nightly r2
-Fixed Ondemand governor
-mm: slub: Default slub_max_order to 0 (Improved performance)
-Increased io performance
-writeback: fix occasional slow sync
-Fixed min frequency (Finally!)
-msm: Fix high load average from uninterruptible waits
-Cpu boost sysfs to enable/disable it (Synapse>cpu drivers)
-S-View hack (Twistedumbrella) enable/disable (Synapse>miscellaneous)
-Minor fixes
January- 1 -2015 nightly r1
-Based on Samsung Open Source N910FXXU1ANIE
-Compiled with Toolchain Linaro GCC 4.9.3 2014.12 Cortex A15
-PowerSuspend Driver
-Intelli-Plug V3.9
-Stereo Call Recording Support
-cpufreq_limit: don't override cpu min frequency
-Fast Charge V1.2
-Sweep2wake
-Simple GPU Algorithm
-Sysfs interface to Enable/Disable Logger Android (Default disable)
-Voltage Control
-Intelli-Thermal V1
-mDNIe Hijack control
-Advanced TCP control (westwood default)
-Sysfs interface to Enable/Disable CRC
-Dynamic Fsync Control V1.5
-Added Intelliactive, Smartmax and SmartassV2 governors
-Led Control
-Panel Color Control
-mDnie mode adapter for Synapse
-Selinux Enforcing/Permissive
-Synapse Support
Click to expand...
Click to collapse
Installation instructions
You need to have TWPR, CWM o Philz Recovery.
Download the last kernel
Reboot in recovery mode
Make backup (recommended)
Flash the zip
Downloads
Strictly No Mirrors Please. In the event that you need to make one ask us first with purpose behind what valid reason.
Current Version
After flash the kernel go to play store and download Synapse apk.
Nadia nightly r7 KK (Mediafire)
App to control your display : Color Control
Old version
Nadia nightly r6 LL (Mediafire)
Nadia nightly r6 KK (MEGA)
Nadia nightly beta r5 (Mediafire)
Nadia nightly r3 (Mediafire)
Nadia nightly r4 (MEGA)
Nadia nightly r4 (AndroidFileHost)
Nadia nightly r3 (Mediafire)
Nadia nightly r3 (MEGA)
Nadia nightly r3 (AndroidFileHost)
Nadia nightly r2 (Mediafire)
Nadia nightly r2 (MEGA)
Nadia nightly r2 (AndroidFileHost)
Nadia nightly r1 (Mediafire)
Nadia nightly r1 (MEGA)
Nadia nightly r1 (AndroidFileHost)
Click to expand...
Click to collapse
Our Projects:
Emotion Revolution for N7100 XDA / HtcSpain
EmotionMIUI for N7100 XDA / HtcSpain
Nadia nightly kernel for N7100
Nadia nightly kernel for m7
N910F/G XDA


Source code:
Nadia kernel Github
Thanks To/Credits
Andip71, AndreiLux, apb_axel, Civato, Christopher83, DerTeufel, Faux123, Ffolkes, Flar2, Franciscofranco, Franlov, Friedrich420, Gokhanmoral, Infernum, LoungeKatt (TwistedUmbrella), Vanito, Yank555.lu, ZaneZam.
I hope I have not forgotten anyone!
Hit the "thanks" button if you like our work.
You can follow new updateshere (Spanish)
XDAevDB Information
Nadia Kernel, Kernel for the Samsung Galaxy Note 4
Contributors
Pafcholini, aukhan, jcanonico
Source Code:https://github.com/Pafcholini/Nadia-...-KK-OpenSource
Kernel Special Features: Faux Sound Support
Version Information
Status: Nightly
Current Stable Version: Nadia nightly r4
Stable Release Date: 2015-01-16
Current Beta Version: Nadia nightly beta r
Beta Release Date: 2015-01-27
Created 2015-01-01
Last Updated 2015-01-27
Twitter: @Pafcholini
Click to expand...
Click to collapse

Reserved
Recommended settings & FAQ Synapse and all available options:
- LIVE STATISTICS: Time in states, Uptime,etc.
- CPU - GOV: cpu scaling, cpu governor and governor tunables.
- CPU voltage: separate frequency voltage.
- GPU: GPU scaling min/max frequency, GPU governor, Simple GPU Algorithm.
- I/O: schedulers, internal storage read-ahead, externalSD read-ahead, Frandom Module, Scheldure Tunables Internal/External
- CPU DRIVERS: PowerSuspend and Intelli-Plug
- THERMAL: Intelli-Thermal Control
- MISCELLANEOUS: Dynamic FSYNC Driver, Logger Mode, CRC Settings, S-View bypass, Selinux Status, Optimize Database.
- BATTERY: Live Statistics and Fast Charge
- MDNIE/SCREEN: Panel Control, mDNIe Mode and mDNIe Mode Hijack
- LED: Led Control
- SCREEN WAKE CONTROL: Sweep2Wake Control
- KERNEL TWEAKS: low memory killer, kernel entropy, panic and panic on oops.
- NETWORK: tcp congestion control, hardering the TCP/IP stack to SYN attack,ignore pings,etc.
- VM-FS: dirty radio, swappiness,etc.
- BUILD.PROP: Build.prop Tweaks
- LOGS: Clearn Synapse, Logcat and Dmseg
- INFO-REBOOT: info about the kernel, reboots,etc.
Click to expand...
Click to collapse
Balance between performance and battery
Quote:
Above is what I use personally. MAY NOT be optimal for all. Share your settings.
CPU frequency: 2649MHz/300MHz
CPU governor: Intelliactive or Bluactive for performance/ Interactive for battery
CPU voltaje: -25uV ((Be careful!! If you low voltages much you can get bootloop or battery drain.)
GPU: default values
I/O schedulers: row for both
PowerSuspend: hybrid hook
MPDECISION for performance/ Intelli-Plug for battery
Intelli-Thermal: enabled
MISCELLANEOUS: fsync enabled, logger mode disabled, crc disabled (you choice), Selinux Permissive
TCP: westwood for both
Click to expand...
Click to collapse
Aukhan recommended settings
1.
2.
F.A.Q
Can I flash this kernel on Note 4 SM-N910C or other variant?
No, you can not. This kernel is only for SM-N910F, SM-N910G, SM-N910T and SM-N910W8.
When I switch to Ondemand governor I noticed that cpu-boost is disabled.
Exactly, Ondemand and cpu-boost doesn't work well together. When you switch to Ondemand governor cpu-boost will be disabled automatically. Don't re-enable cpu-boost if you are using Ondemand governor. (Synapse>CPU DRIVERS)
Which app can control this kernel?
By default, the kernel is controlled by Synapse, but you can use the app that you like (Trickster Mod, Kernel Tweaker, etc.).
I flashed the kernel and Synapse says: "No support UCI detected".
Reflash the kernel, since it was a bad installation and Synapse does not detect the scripts.
After flashing the kernel lost root what to do?
In case you loose root just flash SuperSU
Any recommended settings to follow using Synapse?
At the beginning of the second post.
After flash the kernel some apks give me FC.
Go to Google Play Store and reinstall those apks.
From where can I remove int.d script?
Go to /system/etc/init.d using any root based file manager and delete.
Note: There is an important one related to superSU and if you remove it by mistake you're gonna have trouble with root permissions.
My device doesn't show any reaction to undervolting (battery life is same as before) or gets unstable even on light undervolting?
Use DVFS disabler Module(standalone) (dynamic voltage and frequency scaling), this feature was kept in touchwiz for benchmark boosting purposes and will conflict with any undervolting and custom governors because it scales the voltages and frequency on regular intervals and is framework integrated, so gets a higher priority than kernel based voltage and scaling controls.
For people who don't know what is DVFS please refer Wikipedia.
Min/Max frequency don't stick?
If your frequency settings don’t stick, it's because on certain Qualcomm devices, there are certain system services (thermald/mpdecision/project butter) or kernel service that rewrite frequency settings based on current thermal status and/or touch input.
I made a logcat but my file is empty. How I can "fix" it?
By default Android logger is disable. Go to Synapse > MISCELLANEOUS and enable Logger Mode.
What is it PowerSuspend?
This new powersuspend PM kernel driver is a replacement for it and existing early_suspend drivers. It should give better battery life.
What is it Intelli-Plug?
Intelliplug is a replacement for mp decision. Intelli-Plug is Faux123 open source solution to Qualcomm's closed source mpdecision. Intelli-Plug is disable by default. It conflicts with mpdecsion, so is HIGHLY recommend turning off mpdecision when using intelli-plug! (If you use Synapse the change is automatic. If you enable Intelli-plug mpdecision will turn off).
What is it Intelli-Thermal?
an intelligent MSM thermal throttling kernel driver designed to replace the
closed sourced thermald(aemon) from Qualcomm.
What is it Frandom?
Frandom is a kernel random number generator, which is 10-50 times faster than what you get from /dev/urandom. And it uses very little (/dev/frandom) or none (/dev/erandom) of the kernel's entropy pool, so it is very useful for applications that require a handy source for lots of random data.
What is it CRC?
CRC is a mechanism aiming to prevent data corruption when is enabled (reduce the performance around 30%). So if you disable it improve the performance but your data can be corrupted. Use it at your risk.
/sys/module/mmc_core/parameters/crc

Reserved1
Know/Reported/Fixed issues Know issues
1. Synapse doesn't show CPU governor tunables.
I'm trying to fix it. FIXED
2. Sometimes Synapse (and others kernel control apks) show that the min frequency is 1190MHz (or other frequency).
Just cancel it. FIXED
3. Ondemand doesn't work well. FIXED
Thanks for the report @Vangelis13
Any other Issues you may Report us and we will fix it

Reserved2
Reserved2

Reserved3
Reserved3

Reserved4
Reserved4

Reserved
Reserved last

Does WiFi calling works in this kernel?

mliou said:
Does WiFi calling works in this kernel?
Click to expand...
Click to collapse
I am assuming yes could you please flash and report back.

aukhan said:
I am assuming yes could you please flash and report back.
Click to expand...
Click to collapse
I will test it tonight but I read somewhere that it needs to be based on T-Mobile source for it to work.

I just want to say that I'm SO glad to see this thread / kernel in this subforum. To all my fellow N910T users: I've been using this kernel for a few weeks now after testing every other kernel available, and I've had the best experience by far on my N4 running Nadia kernel. The most recent release is incredible; stable as... something that's super-stable , FauxSound implementation! I have the paid FauxSound app and the sound quality of everything (in call and otherwise) is simply fantastic, if anything ever "goes wrong" for any reason, in my experience booting into recovery, reflashing the kernel and wiping dalvik/cache will fix it 99% of the time. I really encourage N910T users to give this kernel a shot. It solved pretty much every problem I was experiencing previously with my N4, and really made it run like I felt that the current primo device on the market should run! :good:
Edit: Make sure to install BusyBox on Rails, free from the Play store along with this kernel. You'll have problems with Synapse otherwise... very important - just wanted to make a note of that Also, settings-wise, I mostly used @aukhan's settings in the video and undervolted -25mV across the board, which is a very solid place to start from.

Just FYI wifi calling fails to connect

papped said:
Just FYI wifi calling fails to connect
Click to expand...
Click to collapse
I think the only way this works is if OP start from scratch using tmobile base.

I can also confirm that Wi-Fi calling gets error 82 failure to connect while using this kernel.
That said, if you don't need Wi-Fi calling this is an excellent, snappy, and stable build from my testing despite being in beta. I live in an area with good signal and I am impressed with it for sure. Dev has done good work here and brought another excellent kernel option to our device. :good:

jazzmachine said:
I just want to say that I'm SO glad to see this thread / kernel in this subforum. To all my fellow N910T users: I've been using this kernel for a few weeks now after testing every other kernel available, and I've had the best experience by far on my N4 running Nadia kernel. The most recent release is incredible; stable as... something that's super-stable , FauxSound implementation! I have the paid FauxSound app and the sound quality of everything (in call and otherwise) is simply fantastic, if anything ever "goes wrong" for any reason, in my experience booting into recovery, reflashing the kernel and wiping dalvik/cache will fix it 99% of the time. I really encourage N910T users to give this kernel a shot. It solved pretty much every problem I was experiencing previously with my N4, and really made it run like I felt that the current primo device on the market should run! :good:
Edit: Make sure to install BusyBox on Rails, free from the Play store along with this kernel. You'll have problems with Synapse otherwise... very important - just wanted to make a note of that Also, settings-wise, I mostly used @aukhan's settings in the video and undervolted -25mV across the board, which is a very solid place to start from.
Click to expand...
Click to collapse
Thanks a lot as you were first to confirm that the kernel is running smooth that is when we decided let's have a dedicated thread in here.

AlkaliV2 said:
I can also confirm that Wi-Fi calling gets error 82 failure to connect while using this kernel.
That said, if you don't need Wi-Fi calling this is an excellent, snappy, and stable build from my testing despite being in beta. I live in an area with good signal and I am impressed with it for sure. Dev has done good work here and brought another excellent kernel option to our device. :good:
Click to expand...
Click to collapse
Starting from the scratch becomes a little difficult I am sure there should be an alternate way of fixing this let me talk to @Pafcholini as he has moved to new place Internet is not setup yet so waiting for him.

AlkaliV2 said:
I can also confirm that Wi-Fi calling gets error 82 failure to connect while using this kernel.
That said, if you don't need Wi-Fi calling this is an excellent, snappy, and stable build from my testing despite being in beta. I live in an area with good signal and I am impressed with it for sure. Dev has done good work here and brought another excellent kernel option to our device. :good:
Click to expand...
Click to collapse
Starting from the scratch becomes a little difficult I am sure there should be an alternate way of fixing this let me talk to @Pafcholini as he has moved to new place Internet is not setup yet so waiting for him.

Flashing now.

Ditto

Me, too.

[KERNEL][29-08-2015] ~=~ EliteKernel M9 ~=~

EliteKernel M9 150829 (F2.10)
Run cool without hassle.
Tested on international HTC One M9 only.
This experimental kernel is a tweaked version of ElementalX by flar2, all credits for the base kernel go to him, I also recommend you buy his kernel settings app to show appreciation.
EliteKernel aims to:
- optimize performance on lower frequencies
- reduce frequencies / cores optimally for daily usage and medium weight games
- decrease heat under sustained heavy load
- optimize CPU, memory, I/O and native performance
- better battery life
Be aware that I made this kernel primarily for myself, I may go to extremes to achieve my goals and that might cause issues with some devices. I guarantee no support whatsoever and any modifications you make to your device are solely your responsibility.
Usage:
1) make backup in recovery
2) copy .zip to phone
3) flash in recovery
Uninstallation:
- Restore a backup (system + boot should be enough)
- Or reflash your ROM, then any mods you use and flash different kernel on top of it
NOTE: This kernel is experimental, it is only 100% tested on latest compatible ARHD. It is essential that you backup your ROM first, just in case.
Do NOT use Antutu benchmark, it wreaks havoc on the CPU settings until you restart the phone!
Many thanks to flar2 and all the great devs of various parts and modules that made this possible.
.
XDA:DevDB Information
EliteKernel M9, Kernel for the HTC One (M9)
Contributors
nik3r, flar2
Source Code: https://github.com/niker/EliteKernel-M9
Kernel Special Features: Better battery life, less overheating.
Version Information
Status: Beta
Current Beta Version: 150829
Beta Release Date: 2015-08-29
Created 2015-06-26
Last Updated 2015-08-29

READ ME FIRST:
If you have problems, try to flash older versions chronologically before reporting it. Find the newest version where the problem did not yet occur and describe it to me in this thread along with the ROM you are using. If you won't state the last working version I most likely cannot help you!
FAQ:
How to change core configuration: http://forum.xda-developers.com/showpost.php?p=62284915&postcount=50
Click to expand...
Click to collapse
Experimental 5.1.x downloads:
EliteKernel M9 150810 - http://elite-force.eu/emm9/m9_elitekernel_150829.ziphttp://elite-force.eu/emm9/m9_elitekernel_150828.zip
Click to expand...
Click to collapse
Older versions:
Android 5.1.x below
http://elite-force.eu/emm9/m9_elitekernel_150828.zip
http://elite-force.eu/emm9/m9_elitekernel_150810.zip
http://elite-force.eu/emm9/m9_elitekernel_150808.zip
Android 5.0.x below
http://elite-force.eu/emm9/m9_elitekernel_150629.zip
http://elite-force.eu/emm9/m9_elitekernel_150626.zip

Reserved
Changelog:
* version_patch (EX base version)
150829 (3.05):
- optimized frequencies for 2:2 core setup
- improved camera performance on x:2 core setup
150828 (3.05):
- synced with elementalX
- experimental 2:2 setup 150810 (3.02):
- added integrated rngd (you can ditch your seeder app)
- added Westwood+ TCP congestion control as default
- switched to XZ image compression
150808 (3.02):
- synced with flars 2.10 base
- lowered temp cap slightly
- otherwise same settings as before
150629 (1.02):
- minor memory tweaks
- core affinity tweaks
- activated KMS by default in conservative mode
150626 (1.01):
- ElementalX CPU governor default and tweaked for faster drop
- SIO I/O sched default and tweaked
- KMS included but disabled by default
- misc boot-time tweaks
- /data/local/userinit.sh support for custom commands (runs last after kernel init)
- CPU cores defaults to 3little-2big
- CPU freqs limited to little=960MHz; big=1248MHz; GPU=600MHz
- disabled forcing frequency while MTP is active (cooler charging)
- CPU affinity to big cores when present
- disabled most CPU touch boosting
- sweep2sleep disabled for now
Click to expand...
Click to collapse
.

Amma test it right now but am on viper 2.3.1 with latest 2.7..... Firmware would it work ?

From what I read in ElementalX thread, it would boot in 2.7, with some issues like camera not working. Personally I would stay on stock kernel until the new source and next time keep old firmware until there's full kernel support, it's rarely worth it otherwise.

Is it work with 2.x firmware (android 5.1)?

nik3r said:
From what I read in ElementalX thread, it would boot in 2.7, with some issues like camera not working. Personally I would stay on stock kernel until the new source and next time keep old firmware until there's full kernel support, it's rarely worth it otherwise.
Click to expand...
Click to collapse
I can confirm that everything is working as it should and the phone is smooth and ice cold ...even the camera is working fine sweet

sallam5010 said:
I can confirm that everything is working as it should and the phone is smooth and ice cold ...even the camera is working fine sweet
Click to expand...
Click to collapse
Same here ...

Heh I don't know about *ice* cold, but it takes a lot longer in Hearthstone to reach high 30's. Used to be at 43°C+ in a blink of an eye.
Someone should confirm, but it seems like the core affinity works (I hope) and power saving makes very little difference in games. Basically it should prefer to clock up the 2 big cores on high load and keep little cores at 768MHz and lower. Looks like the little cores heat up considerably more at frequencies over 960MHz. I was experimenting with a 2:2 core setup but it was actually worse due to the need for higher average freq.

nik3r said:
Heh I don't know about *ice* cold, but it takes a lot longer in Hearthstone to reach high 30's. Used to be at 43°C+ in a blink of an eye.
Someone should confirm, but it seems like the core affinity works (I hope) and power saving makes very little difference in games. Basically it should prefer to clock up the 2 big cores on high load and keep little cores at 768MHz and lower. Looks like the little cores heat up considerably more at frequencies over 960MHz. I was experimenting with a 2:2 core setup but it was actually worse due to the need for higher average freq.
Click to expand...
Click to collapse
what about a 6 core setup? 4 and 2. 4 at 1.2GHz and 2 at 1.8GHZ?

When the little cores are clocked that high, they can run as hot as the big ones, with far less performance. Performance wise extra core makes no difference. But don't take my word for it and try for yourself. Everything you need is in /elitekernel folder in the delayed script. Copy over the lines you want to change to /data/local/userinit.sh the more people experiment the better

What kind of battery stats are those of you with 2.7 and this kernel getting?

New version
EliteKernel M9 (5.0.x) 150629 is released
Changes:
- synced the base with EX 1.02 (still no gestures, will get to that later)
- minor memory tweaks
- more core affinity tweaks
- activated KMS by default in conservative mode
Enjoy

5.1 version
Hi and many thanks for the effort.
Do you have any ETA for the 5.1 version? Looks like it´s running smooth, but just to know before stepping in. I´m currently on ARHD 10.0 and complaining about heating issues.
BTW, is this kernel related to Buckmarble´s Elite for M8? Best one I´ve ever used.

Nope this is related to EliteMod for DesireZ and EliteKernel for One X+. Pretty much the same idea, X+ was overheating like a **** before I got my hands on it
You only need so much power in real life scenarios, but try playing your super-smooth games when you can barely hold the phone with your sweaty hands. My goal is to fix that without excessive real-life performance drop. The sweet spot is keeping the phone below 40°C. Also keeping the temperatures low prevents artificial throttling, which has much worse impact than lower but steady performance.
The 5.1 version will come out shortly after HTC releases the source, it is out of our hands now. I'm pretty sure flar2 is sitting at his desk looking at htcdev.com and pressing F5 every minute
For future reference it is a good idea not to upgrade firmware/ROM until there's a kernel source to support it.

rickylambert said:
Hi and many thanks for the effort.
Do you have any ETA for the 5.1 version? Looks like it´s running smooth, but just to know before stepping in. I´m currently on ARHD 10.0 and complaining about heating issues.
BTW, is this kernel related to Buckmarble´s Elite for M8? Best one I´ve ever used.
Click to expand...
Click to collapse
Every base we have to wait for htc to release source since 5.1 is leaked/beta have to wait for official ota then maybe up to a month after that source will come..

Really like this kernel. From its idea to its execution. Solid work. Though I have one problem: The Camera doesn't work.
Htc One M9, running LeeDroid 7.6.1 firmware version 1.40. Flashed LeeDroid v3.0 kernel and camera works fine. Is this a kernel specific problem or did something simply get screwed up during flashing?

I'm not aware of any problem with the camera unless you are on the latest 2.7 firmware + 5.1 ROM. Does pure ElementalX work?

nik3r said:
I'm not aware of any problem with the camera unless you are on the latest 2.7 firmware + 5.1 ROM. Does pure ElementalX work?
Click to expand...
Click to collapse
ElementalX works as does the LeeDroid v3.0 Kernel. I'm currently running 1.40 Firmware on a 5.0.2 based ROM. I went back and flashed ElementalX, the camera worked perfectly. Then I flashed this kernel and the camera launched but lagged immensely. I restarted the camera app and then it completely stopped working. :/
UPDATE 10:12PM EST: If I bump the maximum CPU frequency up from 960mhz to 1555mhz, the lag while using the camera is largely diminished (though, not gone). In Google Messenger, attempting to attach a photo is also extremely laggy. The gallery in the screenshot below lags like a mofo when scrolling. This lag is not evident on other Kernels.
{
"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"
}

Oh, I see what you're describing, I didn't use HTC camera app in ages so didn't realize the image preview lags like that. Google camera app has no such problem though, that's ridiculous to require this much power just to shoot stills .
It's not as bad for me as you describe, I get occasional 1-1.5 second lag in the preview, suppose it would be much worse in powersaving.
This explains why on stock ROM, using the camera app force disables power saving (yes HTC, I noticed)... it's easier than to fix their code
Honestly I am not sure what to do about this, there's currently no way to do exceptions like that. It would require an app that would assign CPU profiles to other apps, specific to M9. I will experiment with this more when I have some time, we need to determine the least possible amount of power/cores required to run it smoothly.
AD: Decreasing image resolution to medium in camera can make most of the lag go away, still it's not quite gone.

[Kernel][Tuneable][STOCK/CM] SmoothMod Kernel for SM-T311

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.

Database Info

welcome