Develop Bugs

[KERNEL] SpeedMod Froyo [K13E HPCall VoodooSnd7 SharpnessFix STABLE] - Galaxy S I9000 Android Development

Hi people. This kernel aims to be fast, compatible, stable, and have good battery life. It makes our Galaxy S run the way it should.
This kernel is for the International Galaxy S (I9000) and Bell Mobility Vibrant (I9000M)
The SpeedMod kernel for the AT&T Captivate is available here: http://forum.xda-developers.com/showthread.php?t=893880
Note: Only lagfixes using EXT4 are robust. Other lagfixes run the risk of data loss on freezing, hard-reboots, or sudden power loss.
WARNING: Before you try any lagfix, make sure that you have enough free space on your Internal SD. You should have at least more free space than data+dbdata+cache combined.
Latest K13E (12-Apr) - Voodoo Sound v7. Lowmemorykiller fixes. Improved display sharpness using AMOLED processing mode in MDNIE. Support for voice calls through headphones. Check here for more info and downloads.
>>> Click here for the installation procedure using Odin.
>>> If you have questions, please read the FAQ: Frequently Asked Questions first!
>>> What is the SpeedMod kernel?
Latest features:
- Compiled using codesourcery 2010.09: Faster and more battery efficient
- The only properly working Tiny RCU implementation, thanks to Paul McKenney
- More efficient: Removed debug logging from kernel and Android
- Most updated version of my Enhanced Universal Lagfix fork with improved stability
- Full Android 2.2.1 ROM compatibility
This kernel has:
- Based on JPX Android 2.2.1 kernel source
- Works on all stock Froyo 2.2 and 2.2.1 ROMs and popular custom ROMs
- 340MB RAM
- Enhanced version of sztupy's Universal Lagfix
- Includes neldar's BackLightNotification 2.3 from https://github.com/project-voodoo/backlightnotification/tree/master/kernel_patches/
- Sharpness (AMOLED mode) & color fixes for the screen
- SpeedMod: Replaced kernel jhash2 with jhash3
- Includes my Startup Tweaks from http://forum.xda-developers.com/showthread.php?t=813309
- Adjusted kernel HZ value to improve smoothness
- Uses BFQ IO scheduler by default, from http://algo.ing.unimo.it/people/paolo/disk_sched/sources.php
- Updated ext4 code in kernel from http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/
- Properly working Tiny RCU for better speed and efficiency from http://android.git.kernel.org/?p=ke...it;h=9b1d82fa1611706fa7ee1505f290160a18caf95d
- Patched lowmemorykiller for compatibility with Tiny RCU from http://android.git.kernel.org/?p=ke...ff;h=5545554aac04918ece318270d63cbfcb015577a9
- Optimized compiler flags: -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp
--------------------------------
FOR BEGINNERS:
This kernel is based on sztupy's Universal Lagfix: Lagfix and root options are accessible by booting into the Recovery Menu.
To get the best speed, it is recommended that you enable all Tweaks from the Recovery Menu. Tweaks are under SpeedMod features. Info on Tweaks: http://forum.xda-developers.com/showthread.php?t=813309
How to root: http://forum.xda-developers.com/showpost.php?p=8896862&postcount=90
Kernel HZ value: HZ=500 is smoother, HZ=256 is Samsung default.
--------------------------------
Memory configs (K10J and later):
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=2048
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=4096
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500
CONFIG_WLAN_SAMSUNG_MEMSIZE_BCM=256
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=12288
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=12288
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=32768
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=32768
CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=10240
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMD=3072
Memory configs (K10I and earlier):
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=4096 *#
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=8192 *#
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500
CONFIG_WLAN_SAMSUNG_MEMSIZE_BCM=256
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=11264 **
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=11264 **
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=30720 ##
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=30720 ##
CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=1024 *#
CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=6144 ^^
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMD=3072
** FIMC0/2 = Below this and 720P video recording won't work
## MFC0/1 = Below this and 720P video playback won't work
*# PMEM/PMEM_GPU1/JPEG = Taken from default values for Galaxy Tab
^^ TEXTREAM = Too low and 3G video call stops working
THANKS: Big thanks to sztupy for his kernel compiler VM and ULFK, lastufo for testing compiler optimizations, ykk_five for testing memory configs, and others who gave ideas or helped.
--------------------------------
WARNING: If you use a custom boot animation, apps like One Click Lag Fix will not work because it disables the playlogos1 script hack.
The files with ending with -CWM are for flashing using Clockwork Recovery.
These other zip files are for flashing with ODIN.
--------------------------------
About USB Mounts:
>>> Click here to download the USB mount fixes. Latest SpeedMod versions do not need this fix. The fix is for using K12E or older with 2.2 ROMs. It fixes the problem where Internal SD mounts as a read-only drive on the PC, or if the External SD does not get mounted.
>>> If you have questions, please read the FAQ: Frequently Asked Questions first!
>>> CLICK HERE to DOWNLOAD the kernels.

Thank you! very useful..

Sounds good!
Could it be used in conjunction with Doc's ROM?

Implementing this in my next "Darky's Raw Steel Edition v3.1"

Cant wait. How about version A3 - O3, standart HZ (or 200, which ever you think is better) and OC (sources are already out)?
For now this is the ultimate kernel, without a doubt.
Btw, tried out HZ 100 quite extensively last night (plus ext4-ext2 and all tweaks). It is indeed not as smooth (with 6 pages of widgets in launcherpro, maximum memory consumption with 100 HZ - when you go to screen previews first drawing is slightly laggy. Without 100 - it is smooth on first attempt).
Battery life.. Well, subjectively - better, I would even say much better. But it needs more testing.

Startup script speed tweaks
# Tweak cfq io scheduler
Tweaked settings of the disk io scheduler more for flash memory. Defaults are optimized for spinning harddisks. Lowered the idle wait, re-enable the low latency mode of cfq, removed the penalty for back-seeks and explicitly tell the kernel the storage is not a spinning disk.
# Tweak kernel VM management
Set tendency of kernel to swap to minimum, since we don't use swap anyway.
Lower the amount of unwritten write cache to reduce lags when a huge write is required.
Increase tendency of kernel to keep block-cache to help with slower RFS filesystem.
Increase minimum free memory, in theory this should make the kernel less likely to suddenly run out of memory.
# Tweak kernel scheduler
Make the task scheduler more 'fair' when multiple tasks are running. This has a huge effect on UI and App responsiveness. These values (less aggressive settings) are 20% of the Linux defaults, and about half of the Android defaults.
# Miscellaneous tweaks
Manually set the starting dalvik heap size.
Increase wifi scanning gap to reduce battery usage.
@ Hardcore can you paste your Startup Reference, on your post too for a quick Faq for ppl here, looking for details on the tweaks.
Thanks

Ferdimage said:
Startup script speed tweaks
# Tweak cfq io scheduler
Tweaked settings of the disk io scheduler more for flash memory. Defaults are optimized for spinning harddisks. Lowered the idle wait, re-enable the low latency mode of cfq, removed the penalty for back-seeks and explicitly tell the kernel the storage is not a spinning disk.
# Tweak kernel VM management
Set tendency of kernel to swap to minimum, since we don't use swap anyway.
Lower the amount of unwritten write cache to reduce lags when a huge write is required.
Increase tendency of kernel to keep block-cache to help with slower RFS filesystem.
Increase minimum free memory, in theory this should make the kernel less likely to suddenly run out of memory.
# Tweak kernel scheduler
Make the task scheduler more 'fair' when multiple tasks are running. This has a huge effect on UI and App responsiveness. These values (less aggressive settings) are 20% of the Linux defaults, and about half of the Android defaults.
# Miscellaneous tweaks
Manually set the starting dalvik heap size.
Increase wifi scanning gap to reduce battery usage.
@ Hardcore can you paster this Ref on your post too for a quick Faq for ppl here, looking for details.
Thanks
Credit: Extralife (for pasting on another thread)
Click to expand...
Click to collapse
Thanks mate, very informative.

Ferdimage said:
Credit: Extralife (for pasting on another thread)
Click to expand...
Click to collapse
These tweaks are actually by hardcore, and his explanation =))

Any chance of incorporating the 1.2Ghz overclock?

Very interested in A1 gonna try it out when im home. I preffer speed over battery ^^

You actually changed any code in the source. Or just in config and compile flags? Want to compile kernel (voodoo sources) with this.
Sent from my GT-I9000 using XDA App

dereknas said:
Any chance of incorporating the 1.2Ghz overclock?
Click to expand...
Click to collapse
+1
Hope you could compile with the latest alpha OC using http://forum.xda-developers.com/showthread.php?t=822027
EDIT: Seems raspdeep already has this on his OC kernel, trying

Will this work on stock JP6?

_Rayearth said:
Will this work on stock JP6?
Click to expand...
Click to collapse
yes
10 char

dupel said:
yes
10 char
Click to expand...
Click to collapse
Kewl!
Looking forward to it

mms will fc when I receive or send mms. I think it has to do with the jpg memory size?

zenkinz said:
mms will fc when I receive or send mms. I think it has to do with the jpg memory size?
Click to expand...
Click to collapse
Thanks for the feedback. I'll test it. UPDATE: Just tested sending MMS with Image. It works for me.
BTW, files uploaded!

Can you post some details about jhash3? What's the gain?

First Impression with O2 and HZ=500. It is just me or it is waaay much smoooother the user interface? The scrolling and even opening applications experience feels closer my old HTC Desire.
Let's see battery life, but something changed with this latest kernel (Have been using your ones from the other thread).

Hi! Who can explain to me what is the difference miz these compilations nucleus.
Phone now works flawlessly. It should change or not???
http://forum.xda-developers.com/showthread.php?t=811660

Related

I have been sharing my CM7/CM9 builds for some time in several thread, which culminated in the MackayROM. I picked up with jellybean where I stopped with ICS. MackayROM is based on CyanogenMod sources, with several performance enhancements.
About Cyanogen: CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.1 (JellyBean), which is designed to increase performance and reliability over stock Android for your device.
Disclaimer: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
If you run into errors, I may not be able to solve it!
If you know a solution to a problem, either upload it yourself to Gerrit Code Review or contact me through pm.
The ROM is based on CM10 with the following changes:
-Mackay Kernel: http://forum.xda-developers.com/showthread.php?t=1842324
-Set of cherries picked from gerrit (differing by the day)
-Some handmade patches I did myself to the source code
Feature request are OK, but remember:
1. I try to stay close to stock
2. I will not include additional apps, unless they can be build from source
3. The time I spend on features depends on how much I like them myself
Changelog of 1.9.0 compared 1.8.5:
CM10 sources of 16-Feb-2013
Kernel:
-Updated to linux kernel 3.0.64
-Ported all new features of the JB4.2 kernel (improvements to ROW (default) & BFQ + Interactive (default), added 1100/1300MHz steps)
Full changelog of 1.9.0 compared to stock CM10:
CM10 sources of 16-Feb-2013
Mackay kernel 0.190: http://forum.xda-developers.com/showthread.php?t=1842324
-updated to linux kernel version 3.0.64
-396MB RAM
-SIO scheduler
-Deadline tuning (thanks to DerTeufel)
-BFQv5 scheduler (with upstream improvements)
-ROW scheduler (tweaked, default scheduler)
-many improvements to IO schedulers in general
-SmartassV2 governor
-Wheatley governor
-Conservative tuned
-Interactive governor (default - updated to android 3.4 code + fixes)
-Call volume hack (using “Settings>Advanced Settings”* to set volumes)
-Reduced battery polling interval
-Fast charge (activate through “Settings>Advanced Settings”* or the QuickCharge toggle in MackayROM)
-WiFi PM_FAST mode selection (activate using “Settings>Advanced Settings”*)
-Battery life extender (set through “Settings>Advanced Settings”*)
-CustomVoltage (set using NSTools)
-1100-1400MHz OC steps
-Custom kernel splash (Thanks to Malcho)
-Updated charging logo to match open charger
-Disabled swap & zram
-Improve memcopy/memmove
-Improve the performance of memcpy and memmove
-Kill task closest in size to memory needed to free
-LOAD_FREQ (4*HZ+61) avoids loadavg Moire
-Entropy tweaks: http://lwn.net/Articles/489734/
-backport CPUIDLE from 3.5
-arm/crypto: Add optimized AES and SHA1 routines
ROM comes with stock colour & stock LED. Version with voodoo colour, BLN, and VC+BLN can be downloaded from:
http://rootaxbox.no-ip.org/kasper_h/kernels/JB/
*“Settings>Advanced Settings” only available with Mackay ROM 1.8.5+
*also available through the Galaxy S & Mackay app in the launcher
AriesParts (App name “Galaxy S & Mackay) – now also shown in launcher:
Add mackay kernel settings options:
>WiFi PM mode selection
>Fast Charge
>BLX settings
>Processor settings (governor/frequencies)
>IO scheduler
bootable/recovery:
Mackay recovery (based on CWM 6.0.2.7)
Clear NSTools settings
Clear init.d settings
Remove wipe battery function
Add reboot menu
fix default backup format selection menu
Show battery status in recovery
Aroma FileManager
Include using soft keys to navigate the menu (thanks fishears for the idea)
Added apps:
-Gapps (121011)
-AngryGPS
-YouTube HD (wifi, 3G, also with screen off, normal colour scheme)
-Asus email widget
vendor/cm:
Adapt for custom MackayROM building (bootanimation, ROM&file name)
Custom bootanimation (Thanks to Malcho)
device/samsung/aries-common:
Sets app-close to 1000 ms
Set default to ondemand governor
external/wpa_supplicant_8:
Save frequency to network config
hardware/samsung:
F4k 720p patch for bigmem kernels
frameworks/base:
Cid icon when USB connected
Changed USB page icon from beandroid to USB logo
Option to enable gfx effects
Right/center clock
Monitor device storage directly in /data/data
Navigation bar
Add an "Automatically Connect" option for WiFi networks
Allow purging of assets
Add option to enable/disable Electron Beam Animation
frameworks/native:
surfacetexture: Select texture target based on pixel format
Calculator:
Calculator feature degrees/radians in SIN/COS/TAN
DeskClock:
DeskClock: Fix the build
DSPManager:
Move DSP Manager into settings
Email:
download ZIP (and many other filetypes) files attached to emails
Exchange:
Exchange: calendar sync window linked to email sync window
Settings:
Option to enable gfx effects
Change Profiles to use the default header
Move DSP Manager into settings
Right/center clock
Removed user stats
Navigation bar
Change behavior when back pressed in PerformanceSettings
Fix issue with Portuguese translations
Add an "Automatically Connect" option for WiFi networks
Add option to enable/disable Electron Beam Animation
Trebuchet:
Add 2 Hotseat preferences
providers/MediaProvider:
Make sure to always release the wake lock
Coming from stock Samsung ROM/CM7:
-The safest way is to flash CM9 first and then flash Mackay ROM. Going directly from Samsung ROM/CM7 to Mackay ROM may lead to loosing IMEI.
Can be flashed on top of any CM9/CM10 build:
-Coming from CM9 or CM10-builds with an old/different partition layout (older than 0817, helly bean): your phone will be wiped (except SD card)
-Coming from a recent CM10 build (0817 or later): this is a non-wipe update
>Gapps is included in the zip since 1.2.0, so separate flashing of gapps is not needed!
-Custom kernels can be used only if patched for the new partition layout
Credits:
-teamhacksung/pawitp for making CyanogenMod work on our ancient phone
-stratosk/DerTeufel/Mialwe for the inspiration I got from their kernels
-theos0o for creating such a nice YouTube HD app
-rootax &xdafileserver for providing a high-speed server for high quality downloads
-Malcho for his bootanimation & kernel splash
Downloads:
https://s.basketbuild.com/devs/kasperhettinga/sgs/rom/pre-KK/

Eh, Eh, Eh. Another JB ROm! Nice! Thank you .

thanks a lot

Thanks friend :good:

What a fast update?!
Gesendet von meinem GT-I9000 mit Tapatalk 2

UltrasFrankfurt said:
What a fast update?!
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
No no, it`s first version of ROM (not kernel)
Moin, mein Freund ...noch unterwegs so spät?

@kasper_h: very cool to see you finally made it to jellybean-country with your rom and kernel! i always liked the idea of your work and will now gladly test the jellybean-builds you produce.
thx again and keep up your good work!
greetz,
sUsH

tried most of the jb's on here and was looking for a change. Downloaded and flashed. So far so good. Feels snappy, my tomb runner is smooth. no FCs yet. quite impressed so far.
Sent from my GT-I9000 using xda premium

Can i used this rom for a daily use ?
Also how can i put low vibration

Haw sh*t,dropbox fact : generating too much traffic...

I got a wifi issue. It will stop downloading after a few seconds. Wifi indicator still shows full bars just dies. 3g working ok i think...
Sent from my GT-I9000 using xda premium

Bejda said:
Haw sh*t,dropbox fact : generating too much traffic...
Click to expand...
Click to collapse
yep, seems like there's some serious downloading going on...
maybe kasper_h or somebody else can do a mirror?
greetz n thx,
sUsH

RuffBuster said:
I got a wifi issue. It will stop downloading after a few seconds. Wifi indicator still shows full bars just dies. 3g working ok i think...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I have no idea what the problem can be, new problem to me. Can you provide a logcat?
sUsH667 said:
yep, seems like there's some serious downloading going on...
maybe kasper_h or somebody else can do a mirror?
greetz n thx,
sUsH
Click to expand...
Click to collapse
Uploaded to mediafire: http://www.mediafire.com/?mgwdnls5hhrbsnw

This includes the new partitions, yes?

AlexsamaM said:
This includes the new partitions, yes?
Click to expand...
Click to collapse
First post, last couple of lines. If you already have new partitions, you're set. If you don't have them, the installer creates them.
Benjamin

Downloading the ROM right now. I haven't tried your earlier ROMs and kernels but I have heard a lot of good things about them. I wish you all the very best.
PS: What's the hoopla about the new partition layout? I'm sorry to be stupid but I have tried reading posts and it just doesn't seem to get into my head. If someone can explain the differences between the older and the newer layout or even give me a link to read, I'd be very grateful

Thx for this rom. I see your default governor is smartassv2, do you prefer it over wheatly? And how does the new bfq scheduler differ from sio?

dherre65 said:
Thx for this rom. I see your default governor is smartassv2, do you prefer it over wheatly? And how does the new bfq scheduler differ from sio?
Click to expand...
Click to collapse
http://lmgtfy.com/?q=wheatley+governor
http://forum.xda-developers.com/showthread.php?p=19846297

dherre65 said:
Thx for this rom. I see your default governor is smartassv2, do you prefer it over wheatly? And how does the new bfq scheduler differ from sio?
Click to expand...
Click to collapse
SmartassV2 and SIO have always worked very well for me and other, so that's why I set them as default. Wheatley & BFQ v4 are both still in testing, so others can choose them as well, but I don't want to make them the default just yet.
BTW, for me, wheatley & bfq work very well.

adityak28 said:
Downloading the ROM right now. I haven't tried your earlier ROMs and kernels but I have heard a lot of good things about them. I wish you all the very best.
PS: What's the hoopla about the new partition layout? I'm sorry to be stupid but I have tried reading posts and it just doesn't seem to get into my head. If someone can explain the differences between the older and the newer layout or even give me a link to read, I'd be very grateful
Click to expand...
Click to collapse
The idea is simple, /system & /data have been swapped. Now /data is on the faster part of the internal memory (which is beneficial because there is lots of writing on /data) and /system (which is only read) is on the slower part of the internal memory. Disadvantage is that /data is now limited to 422MB, so people with lots of apps complain (although the solution here is to move apps to SD to save space on the smaller /data).

Mpokang kernel​
This kernel focuses on MAX USABLE RAM. As we know, the GNex has 1GB of RAM. A big part of it (300+ MB) is reserved for various things.
Is it really needed? No, it looks like that actual usable RAM can be much much more.
Feature List:
Many features, just as many as every other kernel. The differentiating points of this kernel are:
1) First kernel with the pioneering RAM reclaiming: from 693 --> 773 MB RAM.
2) Most available RAM: Still has the most RAM available.
3) Flexibility: Choose any of the 3 variations that suits you
4) Sophisticated ZRAM mechanism: zsmalloc from Linux kernel 3.11, enhanced zram mem operations
5) First and only kernel at the moment with huge 50%+ memory performance boost
As of v10, three (3) variations of Mpokang kernel for everyone to choose according to his needs.
Performance is the same, only the available RAM changes:
SuperRAM: 773 MB RAM -- Some rare video apps (or the gay CM video camera) may not work properly.
CM "gay" :silly: : 762 MB RAM -- All video apps work OK but still 720p, suitable for CM based roms.
1080p version: 751 MB RAM -- 1080p fully working, compatible with everything, even Android 4.2.2. Does not contain ramdisk. Clean rom installation required.
To sum up: For Android 4.3 all variations are applicable. For Android 4.2.2 ONLY the 1080p variation applies.
Valuable Notes
Note 1: Many redundant and practically useless stuff is removed. Badass sounding governors and schedulers, which don't actually offer anything were removed.
Note 2: Interactive gov from kernel 3.4, hyper gov and SIOPlus, deadline and row are the best out there. Maybe FIOPS on the future.
Note 3: In general .. more useless stuff removed equals more RAM. This does not apply to the SuperRAM variation, where many many features can be added as modules without reducing the available memory.
Kernel source: https://github.com/mpokwsths/mpokang_kernel
DOWNLOADS:
Moderation - Deleted Links.
FAQs:
Q: When using SuperRAM version I have trouble running apps like Video editor, video calling in some apps.
A: Some rare apps don't like this extreme RAM reclaiming. Use another variation.
Q: My screen colors seem a bit changed. Even if I change them like I used to in TricksterMod...
A: It's because of Purple Tint Fix. Many users experience that ugly tint, and this kernel cures it. Slightly change your color settings in Trickster. If, whatever you do, the colors look bad, report it here and I will see what I can do.
Q: I want the full 1GB of RAM. Is this possible?
A: No, full 1GB is unachievable (with TI's ION code). But if someone is willing to drop all the media support (camera, video, media playback) close to 900MB is achievable.

Changelog:
Ver. 1:
- Now using ramdisk (Osmosis modified). Now you can flash the kernel unconditionally (no more screwing from other ramdisks) and my preferred settings are kept.
- Introduction of Cleancache from kernel 3.7
- Introduction of Zsmalloc, Zcache and Frontswap from kernel version 3.8
Ver. 2:
- Reclaimed 4 MB of RAM (now it should be at 771 MB) from the frame buffer. TI has been very generous spending GNex's RAM all over the place.
- Pushed some commits from ASPK, mainly memory hotplugging related
- Went back to Anykernel format. No ramdisk since there were some complains of problems with some roms.
- Fixed vfs_cache_pressure (script not needed)
- Some memory reservation and ram leaks fixing (900KB RAM more).
- Should have a bit better battery consumption since I altered the dirty ratios.
Ver. 3:
- Modified the installation script. Now it copies the hacked Power HAL to the system so that altered gov settings do not reset after screen off (No need to check "Frequency Lock" in Trickster now).
- Removed a bunch of useless stuff. The kernel itself shrunk significantly. Boot time should be faster than ever.
- Reclaimed another 600K
- Changed interactive governor default settings. Only above_highspeed_delay needs to change to 20000 now.
Ver 4:
- Disabled all kernel debugging (should be a bit faster)
- Reclaimed another 512KB (compared to 4.1)
- Added some battery preservation routines (should consume a little less battery when watching videos)
- Some scheduler tinking
Ver. 5:
- Updated Linux kernel 3.0.88 --> 3.0.94
- Enabled ZRAM from kernel 3.7 (thanks Boype & Faux)
- Disabled Cleancache & Zcache
- Some more battery preservation additions
- Enabled full Hard Float kernel building.
Ver. 6
- ARM patches for slightly improved performance
- pushed a commit for ZRAM that will provide somewhat better memory management
- some other changes for the next version (ZRAM working together with Zcache & Frontswap)
Ver. 7
- Using Linaro Toolchain 2013.09
- Updated Linux 3.0.94 --> 3.0.96
- Improved mem operations of zram
- Backported zsmalloc from latest kernel 3.11 (zsmalloc = zram memory allocator)
- Some kernel scheduler and timer fixes
- Changes in VFS cache pressure and swappiness values to find the sweet spot
Ver. 8
- Several mutex code commits (multithreading optimization)
------ ARM: 7467/1: mutex: use generic xchg-based implementation for ARMv6+
------ mutex: place lock in contended state after fastpath_lock failure
------ ARM: mutex: use generic atomic_dec-based implementation for ARMv6+
------ mutex: dynamically disable mutex spinning at high load
- Added VUSIM voltage regulation. This is a screen regulator, so undervolting it should save some power (I have it at 1500mV without problems)
- ARM: mm: lazy cache flushing on non-mapped pages
- A couple of cache related optimizations for Cortex-A9
- Set default temperature limit @ 75C. Should be absolutely safe.
- voltage.h: Set VDDMIN to 810 - Smartreflex calibrated MPU min voltage now is 810mV
- i2c: use usleep_range to wait instead of msleep (imoseyon reported potential performance benefits)
- ARM: 7178/1: fault.c: Port OOM changes into do_page_fault
- readahead: fault retry breaks mmap file read random detection
- Some scheduler improvements?
Ver. 9
- Updated Linux 3.0.96 --> 3.0.98
- New ramdisk for the kernel. Now it can be flashed unconditionally anytime.
- Enabled loadable module support.
- Compiled many modules as external modules. Reclaimed 400KB of RAM.
- Reverted the 300Hz kernel timer. The load calculation was all over the place
- Reverted some UV commits (especially IVA) that seemed to produce freezes and SODs. Hopefully they are fixed.
- Some CPU cache code and kernel scheduler improvements.
- Added the io_is_busy interface to Interactive governor
- Now, apps that seeked 1080p won't crash anynore. 1080p support is removed in the media_profiles.xml
- Altered some default settings: color scheme slightly colder, interactive above_highspeed_delay=20000, io_is_busy=1

Yay, new kernel! Gonna test it when you pushed a build up

Looking forward to it
Sent from my Galaxy Nexus using Tapatalk 2

Going to need some testers. Are you interested? All the people interested for testing, sign up here.

I'm ready if you can enable module for PGM. Can't live without it

ronnie_1712 said:
I'm ready if you can enable module for PGM. Can't live without it
Click to expand...
Click to collapse
+1
Sent from my Galaxy Nexus using Tapatalk 2

A kernel who can be really different ! It deserve to be tested. I'm interested :good:

I shall test this kernel.
Also, it would be nice if you could list down stuff that you changed/added compared to stock kernel.

Looks awesome! I could be a tester!
Sent from my Galaxy Nexus using xda premium

Tester !!

Def would love being a tester for this. Always on the edge
Sent from my Galaxy Nexus using xda app-developers app
---------- Post added at 07:25 AM ---------- Previous post was at 07:22 AM ----------
Question- does it break anything such as 1080p recording an such, I remember a time when I had my sensation that a couple of devs had kernels that gave more ram but took away some of the functionality, jus wondering if this is the case, bcuz in all honesty I can live without such high end things when they simply eat away at my battery lol
Sent from my Galaxy Nexus using xda app-developers app

Another tester!

Yes,give me something to test.:thumbup:
sent from my maguro via tapatalk

Subbed, this is going to be awesome.

Well, it seems that there are many components than can provide some RAM slices. 1080p in camera seems to cost almost 40 MBs. With fully usable 720p and photos etc, we are at 72-73 MBytes more RAM than other kernels. Test build will be up tonight or tomorrow morning.

I would also love to test this kernel. Good luck!
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

mpokwsths said:
Well, it seems that there are many components than can provide some RAM slices. 1080p in camera seems to cost almost 40 MBs. With fully usable 720p and photos etc, we are at 72-73 MBytes more RAM than other kernels. Test build will be up tonight or tomorrow morning.
Click to expand...
Click to collapse
Ahhh I see figures, this is gonna b friggin sweet
Sent from my Galaxy Nexus using xda app-developers app

mpokwsths said:
Started my own kernel development.
This kernel focuses on MAX USABLE RAM.
As we know, the GNex has 1GB of RAM. A big part of it (300+ MB) is reserved for various things.
Is it really needed? No, it looks like that actual usable RAM can be much much more. Started testing some builds and the results are very encouraging. Only a screenshot for now:
Stay tuned!
Click to expand...
Click to collapse
Sik-1 said:
Ahhh I see figures, this is gonna b friggin sweet
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
+1 !!
This will be awesome !!
Will this be based off on AK, just curious as you had the Ak kernel re-released many times ?

Great job !

Okay, so we all know how good Mpokang kernel is. Unfortunately the dev hasn't been active and people have been modifying his kernels to make them work on 4.4 (KitKat).
This a thread which looks exactly like the original Mpokang thread, but the only difference being that it contains the download links to the Mpokang kernels which work on Android 4.4 KitKat. I have absolutely no contribution in the development of this kernel and if you like Mpokang, then please don't thank me, rather go to THIS THREAD and thank the OP. And the entire credit for this goes to @metalspring as he has been the one who modified the Mpokang kernels to make them work on KitKat.
Note
TouchControl/PGM works only on SuperRam. TouchControl/PGM will not work on CM version or 1080p version.​
Mpokang kernel​
This kernel focuses on MAX USABLE RAM. As we know, the GNex has 1GB of RAM. A big part of it (300+ MB) is reserved for various things.
Is it really needed? No, it looks like that actual usable RAM can be much much more.
Feature List:
Many features, just as many as every other kernel. The differentiating points of this kernel are:
1) First kernel with the pioneering RAM reclaiming: from 693 --> 773 MB RAM.
2) Most available RAM: Still has the most RAM available.
3) Flexibility: Choose any of the 3 variations that suits you
4) Sophisticated ZRAM mechanism: zsmalloc from Linux kernel 3.11, enhanced zram mem operations
5) First and only kernel at the moment with huge 50%+ memory performance boost
As of v10, three (3) variations of Mpokang kernel for everyone to choose according to his needs.
Performance is the same, only the available RAM changes:
SuperRAM: 773 MB RAM -- Some rare video apps (or the gay CM video camera) may not work properly.
CM "gay" :silly: : 762 MB RAM -- All video apps work OK but still 720p, suitable for CM based roms.
1080p version: 751 MB RAM -- 1080p fully working, compatible with everything, even Android 4.2.2. Does not contain ramdisk. Clean rom installation required.
Valuable Notes
Note 1: Many redundant and practically useless stuff is removed. Badass sounding governors and schedulers, which don't actually offer anything were removed.
Note 2: Interactive gov from kernel 3.4, hyper gov and SIOPlus, deadline and row are the best out there. Maybe FIOPS on the future.
Note 3: In general .. more useless stuff removed equals more RAM. This does not apply to the SuperRAM variation, where many many features can be added as modules without reducing the available memory.
Kernel source: https://github.com/mpokwsths/mpokang_kernel
DOWNLOADS: (All of these work on KitKat ie Android 4.4.x) <MODERATOR EDITED - LINKS REMOVED>
FAQs:
Q: When using SuperRAM version I have trouble running apps like Video editor, video calling in some apps.
A: Some rare apps don't like this extreme RAM reclaiming. Use another variation.
Q: My screen colors seem a bit changed. Even if I change them like I used to in TricksterMod...
A: It's because of Purple Tint Fix. Many users experience that ugly tint, and this kernel cures it. Slightly change your color settings in Trickster. If, whatever you do, the colors look bad, report it here and I will see what I can do.
Q: I want the full 1GB of RAM. Is this possible?
A: No, full 1GB is unachievable (with TI's ION code). But if someone is willing to drop all the media support (camera, video, media playback) close to 900MB is achievable.
Changelog:
Ver. 1:
- Now using ramdisk (Osmosis modified). Now you can flash the kernel unconditionally (no more screwing from other ramdisks) and my preferred settings are kept.
- Introduction of Cleancache from kernel 3.7
- Introduction of Zsmalloc, Zcache and Frontswap from kernel version 3.8
Ver. 2:
- Reclaimed 4 MB of RAM (now it should be at 771 MB) from the frame buffer. TI has been very generous spending GNex's RAM all over the place.
- Pushed some commits from ASPK, mainly memory hotplugging related
- Went back to Anykernel format. No ramdisk since there were some complains of problems with some roms.
- Fixed vfs_cache_pressure (script not needed)
- Some memory reservation and ram leaks fixing (900KB RAM more).
- Should have a bit better battery consumption since I altered the dirty ratios.
Ver. 3:
- Modified the installation script. Now it copies the hacked Power HAL to the system so that altered gov settings do not reset after screen off (No need to check "Frequency Lock" in Trickster now).
- Removed a bunch of useless stuff. The kernel itself shrunk significantly. Boot time should be faster than ever.
- Reclaimed another 600K
- Changed interactive governor default settings. Only above_highspeed_delay needs to change to 20000 now.
Ver 4:
- Disabled all kernel debugging (should be a bit faster)
- Reclaimed another 512KB (compared to 4.1)
- Added some battery preservation routines (should consume a little less battery when watching videos)
- Some scheduler tinking
Ver. 5:
- Updated Linux kernel 3.0.88 --> 3.0.94
- Enabled ZRAM from kernel 3.7 (thanks Boype & Faux)
- Disabled Cleancache & Zcache
- Some more battery preservation additions
- Enabled full Hard Float kernel building.
Ver. 6
- ARM patches for slightly improved performance
- pushed a commit for ZRAM that will provide somewhat better memory management
- some other changes for the next version (ZRAM working together with Zcache & Frontswap)
Ver. 7
- Using Linaro Toolchain 2013.09
- Updated Linux 3.0.94 --> 3.0.96
- Improved mem operations of zram
- Backported zsmalloc from latest kernel 3.11 (zsmalloc = zram memory allocator)
- Some kernel scheduler and timer fixes
- Changes in VFS cache pressure and swappiness values to find the sweet spot
Ver. 8
- Several mutex code commits (multithreading optimization)
------ ARM: 7467/1: mutex: use generic xchg-based implementation for ARMv6+
------ mutex: place lock in contended state after fastpath_lock failure
------ ARM: mutex: use generic atomic_dec-based implementation for ARMv6+
------ mutex: dynamically disable mutex spinning at high load
- Added VUSIM voltage regulation. This is a screen regulator, so undervolting it should save some power (I have it at 1500mV without problems)
- ARM: mm: lazy cache flushing on non-mapped pages
- A couple of cache related optimizations for Cortex-A9
- Set default temperature limit @ 75C. Should be absolutely safe.
- voltage.h: Set VDDMIN to 810 - Smartreflex calibrated MPU min voltage now is 810mV
- i2c: use usleep_range to wait instead of msleep (imoseyon reported potential performance benefits)
- ARM: 7178/1: fault.c: Port OOM changes into do_page_fault
- readahead: fault retry breaks mmap file read random detection
- Some scheduler improvements?
Ver. 9
- Updated Linux 3.0.96 --> 3.0.98
- New ramdisk for the kernel. Now it can be flashed unconditionally anytime.
- Enabled loadable module support.
- Compiled many modules as external modules. Reclaimed 400KB of RAM.
- Reverted the 300Hz kernel timer. The load calculation was all over the place
- Reverted some UV commits (especially IVA) that seemed to produce freezes and SODs. Hopefully they are fixed.
- Some CPU cache code and kernel scheduler improvements.
- Added the io_is_busy interface to Interactive governor
- Now, apps that seeked 1080p won't crash anynore. 1080p support is removed in the media_profiles.xml
- Altered some default settings: color scheme slightly colder, interactive above_highspeed_delay=20000, io_is_busy=1
Ver. 10 - Changelog not available
Click to expand...
Click to collapse

thx for this kernel:good:

Thanks for setting this thread up, hopefully KitKat discussion will migrate over here.
Sent from my Galaxy Nexus using Tapatalk

Does the cm v10 work with new cm battery?
WHATCHOO TALKING BOUT WILLIS?

fcisco13 said:
Doors the cm v10 work with new battery?
WHATCHOO TALKING BOUT WILLIS?
Click to expand...
Click to collapse
I don't think so, because it has a ramdisk too unlike the 1080p version. You can give it a shot. If it doesn't, use SuperRam.
Maybe @metalspring can modify the CM v10 to fix the battery issue on it (if it exists).

Thanks for new thread

does anyone know how to modify kernels to work on 4.4.x?
id really like to mod. @faux123 kernel to work. best battery life ive had in a long time.
and SUPER smooth too

I know I'm a little dense. That being said, I think a warning is needed for the battery fixing 4.4.2 version. That is to say please note that it is only for CM builds after a certain date. Tried using it on ShinyROM with hilarious results

That's why i use 1080 version

AbhishekS said:
I don't think so, because it has a ramdisk too unlike the 1080p version. You can give it a shot. If it doesn't, use SuperRam.
Click to expand...
Click to collapse
I know you clearly stated in OP you didn't create this. You're just sharing it. I know you just wanted to bring the 4.4 discussion out of the original page to here. But xda admins may not be too happy
Then again I may not be right, but just giving you a heads up
Sent from my Galaxy Nexus using Tapatalk

Well I don't think that will be an issue because a 4.4 exclusive thread will certainly help reduce the confusion going on in the original Mpokang thread. And I'm sure anything which helps reduce the confusion and complexities will be appreciated by the admins/mods.
Sent from my Galaxy Nexus using Tapatalk

akash3656 said:
I know you clearly stated in OP you didn't create this. You're just sharing it. I know you just wanted to bring the 4.4 discussion out of the original page to here. But xda admins may not be too happy
Then again I may not be right, but just giving you a heads up
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Xda mods will be unhappy because he posted the wrong kernel source
Sent from my Galaxy Nexus using xda app-developers app

Grarak said:
Xda mods will be unhappy because he posted the wrong kernel source
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I've posted the same ones in the OP which @mpokwsths has provided us. Yes, they aren't up-to -date but unfortunately that's all that we have.
Sent from my Galaxy Nexus using Tapatalk

AbhishekS said:
I've posted the same ones in the OP which @mpokwsths has provided us. Yes, they aren't up-to -date but unfortunately that's all that we have.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
It's not enough
You said it's a modified kernel by metal
So where are his sources?
Sent from my Galaxy Nexus using xda app-developers app

Grarak said:
It's not enough
You said it's a modified kernel by metal
So where are his sources?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Here's a thought: why don't you ask the person who created the kernel?

I installed this version "v10 SuperRAM (for newer builds - fixes broken battery)" with omniMetal but the battery always reports 0%

This kernel makes my phone fly..
Sent from my Galaxy Nexus using XDA Premium HD app

noviz69 said:
I installed this version "v10 SuperRAM (for newer builds - fixes broken battery)" with omniMetal but the battery always reports 0%
Click to expand...
Click to collapse
Umm try rebooting your phone. If problem persists, install the normal SuperRam. I guess the broken battery thing exists only on the newer CM11 builds.
Sent from my Galaxy Nexus using Tapatalk

Wow, this modified kernel by metal + cm11 playfulgod + banks gapps standard, makes my Gnex Super-fast-smooth-savebattery (ART on)..GPS locked less then a sec
Sent from my Galaxy Nexus using xda app-developers app

Does v10 1080p have battery glitches on cm11?

Final notice: Since my Z5 died (it's broken into pieces, glass shattered) - development is effectively halted - NO more updates - sorry
This is a Stock (Sony) ROM Kernel and WILL NOT work on AOSP, CM, etc.
aka SunKernel for Z4/Z3+ & Z4/Z3+ Dual - Stock ROM (for now only stock)
This is an extension of the Xperia Z5/Z5 Dual "sumire" main thread over at: https://forum.xda-developers.com/xp...und-z5-wip-t3340725/post65936553#post65936553
Finally !
So the kernel is now also available for the (somewhat forgotten) Z4/Z3+ series
Please understand that I can't test whether it works due to lack of that very device - Enjoy !
Keep in mind that building for the Z5 "Stock" ROMs and "Stock" Kernels, you're constantly facing the following tradeoff:
compatibility with pre-built "core" kernel modules (e.g. texfat [proprietary exfat microSD fs driver])
compatibility with pre-built "goodies" kernel modules (e.g. video and other acceleration, hwcodecs, ...)
losing features that can NOT be replaced by similar ones (e.g. ecryptfs, wlan, exfat, etc.)
when going too far the device doesn't boot or simply hangs on bootanimation
this resulted in a couple branches (at least several dozen) that are partially or totally broken :silly:
[snip]
...
[snip]
More info on the Latest Kernel can be usually found at:
AT the end of the thread
( I KNOW - I should have reserved a few posts for better overview )
---------------------------------------------------------------------------------
[Download] How to get the current ("corona", 5.11) Kernel(s) - Step by Step:
1)
Choose your device from one of the 4 folders
Z5 + Z5 Dual: https://drive.google.com/open?id=0BykGGWB96CBQQy05VURLbzJTZlU
Z5 Compact: https://drive.google.com/open?id=0BykGGWB96CBQVE0tb2dieTZMXzg
Z5 Prem + Z5 Prem Dual: https://drive.google.com/open?id=0BykGGWB96CBQaVZTdnF5QnVTMU0
Z4/Z3+ + Z4/Z3+ Dual: https://drive.google.com/open?id=0BykGGWB96CBQa2xBdHR5TzlrNUE
2)
At the upper right, click on "List View"
3)
At the top of the table, there are 3 labels (name, owner, [last] modified, File size)
click on "Last modified", the newest Kernels should be shown either at the top, or at the bottom
4)
Download the latest Kernel
5)
???
6)
Profit !
Click to expand...
Click to collapse
Before starting to test/use keep in mind that this is WIP (work in progress),
that means - NO guarantees,
backups before flashing are a MUST (especially your microSD card content !)
stability, speed, improved battery and satisfaction are a great side-effect to have.
You have been WARNED !
Enjoy !
Obligatory Source:
(according to the rules in single commits no giant blobs, authorship kept)
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2/branches

Features:
(will add more later if I forgot anything)
Features said:
@AndroPlus for build-scripts, kernel patches
@Tommy-Geenexus for kernel patches, fixes
pstore
LPM (low power mode, battery efficiency)
fix high load average (lower battery consumption)
microSD, internal SD reliability improvements
cpuidle improvements (battery efficiency)
fix page thrashing in case of low memory situation (when you disable zram)
vmalloc improvements (less memory fragmentation, better reliability of camera, wifi, etc. drivers with long runtime)
FauxSound
KCAL
WLAN: disable memdesc and ramdumps (thanks to @Tommy-Geenexus )
notification LED changes to green+blue (cyan), when battery is really full (thanks to @Tommy-Geenexus )
Powersuspend, QuickWakeup, Power Efficient Workqueues,
improved vibrator, faster/more reliable interactivity
bluetooth hidp, fix disconnect on idle timeout
a few general stability fixes & reliability improvements
added wakelock switches (only use, if you observe high drain with specific functions; might cause instabilities or higher battery drain !)
big.LITTLE optimization flags; aggressive compiler optimization flags
disabled KSM, it's a battery drainer and magically gets enabled by Sony's ROM so remove it
added BFQ i/o scheduler (now YOU show me where it's smoother ! )
improved noop i/o scheduler - now it's more bare, previously it was similar to simple i/o scheduler - now it should be optimum for bare metal SSD/microSD access
GPU default set to 180 MHz
cpu governors: added ZZMoove, elementalX
added vibrator intensity switch support
added a bunch touchpad (screen) and fingerprint scanner fixes & improvements
support for Sumire DSDS (dual sim) (testing, used single SIM ramdisk)
kudos to all devs working on android, whether at Linux Foundation (Linux Kernel), Android (Google), Codeaurora, XDA or elsewhere - YOU ROCK !
this one looks to be more battery friendly
WIP branch
NEW features
sys-fs interface to control vibrator intensity (some kernel tools might support it)
lowered init value of screen during bootup: now you shouldn't get 100% BLINDED when rebooting :cyclops:
core 0 and 4 are now always on (per default, unless you play around with core_ctl) - allows changing governor settings for the big cores
mmc crc checksum is disabled by default (?) - 30% or more higher performance, re-enable if you favor integrity
KEXEC support - give @Myself5 's MultiROM a test-drive if you're curious (http://forum.xda-developers.com/xperia-z5/orig-development/mod-multirom-v33x-t3374763)
added Alucard cpufreq governor, if it's too laggy, unstable, etc. - I'm throwing it out the airlock
added a few additional changes thanks to @AndroPlus
.
224 version bump (224 ROMs ONLY)
RAM (working memory) energy efficiency improvements, thanks to @AndroPlus to spot it
overclocking support "big" core ~ 2.1 GHz, "little" core ~ 1.7 GHz (the "little" core is less tolerant for OC, less stable)
changed optimization flags (evaluation), should now be more stable but also faster, efficient
.
Z4/Z3+ support
Click to expand...
Click to collapse
Notes:
Trilliard said:
If you have systemless root and systemless xposed on your system, you have to flash latest betaSU and latest systemless xposed framework immediatly after flashing a new Kernel. If you dont do this you will get a bootloop.
Click to expand...
Click to collapse
Overclocking:
The following threads are for the Z5 - so naturally the thermal engine needs to be adapted to work on the Z4/Z3+
http://forum.xda-developers.com/xperia-z5/general/tweak-improve-performance-reduce-t3387879
http://forum.xda-developers.com/showpost.php?p=67444047&postcount=150 ( @_LLJY 's thermal-engine modifications are attached )
Source:
https://github.com/zachariasmaladro...i_r2/commits/Sun-Kernel_32.2.A.0.224_vI.1_2_8
Download: AndroidFileHost :
SunKernel_for_Z4_Z3Plus 224_I.1_2_8
224_I.1_2_8 Changelog said:
Changelog:
- 224 version bump (224 ROMs ONLY)
- RAM (working memory) energy efficiency improvements, thanks to @AndroPlus to spot it
- overclocking support "big" core ~ 2.1 GHz, "little" core ~ 1.7 GHz (the "little" core is less tolerant for OC, less stable)
- changed optimization flags (evaluation), should now be more stable but also faster, efficient
- "ivy" support (Z4/Z3+)
Click to expand...
Click to collapse
Thanks

it is coming thx very much

twrp can not mount mtp

works great

Flashed your Kernel Today, no problems with Systemless Root, flashed Systemless Xposed - no problems here. Everything works fine... Now lets have a look at what we can do

If you don't mind a small request to @zacharias.maladroit, I want to use your kernel and features are good, but can you make a kernel build with default clock of CPU and GPU reduced to 50% before boot (it should be same in recovery also) and i want to manually change its default clock through kernel auditor if i want later. Reason is my phone gets heated during boot due to its running at max frequencies.
Thanks for your work and I hope you wont mind giving me this option.
EDIT: Faux sound is not working and it does nothing when i change it from kernel auditor.

GryTEcHoG said:
If you don't mind a small request to @zacharias.maladroit, I want to use your kernel and features are good, but can you make a kernel build with default clock of CPU and GPU reduced to 50% before boot (it should be same in recovery also) and i want to manually change its default clock through kernel auditor if i want later. Reason is my phone gets heated during boot due to its running at max frequencies.
Thanks for your work and I hope you wont mind giving me this option.
EDIT: Faux sound is not working and it does nothing when i change it from kernel auditor.
Click to expand...
Click to collapse
use ex kernel

death_note7 said:
use ex kernel
Click to expand...
Click to collapse
What you mean ? Which kernel you are referring to ? Does that kernel have all the features of Zach's ? If so give me link as I can't find it. I liked Zach's kernel but during boot my phone gets hot due to default max freq and also faux sound is not working (which does nothing when i change sliders from kernel auditor app).

Flashed this kernel working well, systemless root, xposed and ex kernel manager. Letting it sit in till I start messing with settings.

GryTEcHoG said:
What you mean ? Which kernel you are referring to ? Does that kernel have all the features of Zach's ? If so give me link as I can't find it. I liked Zach's kernel but during boot my phone gets hot due to default max freq and also faux sound is not working (which does nothing when i change sliders from kernel auditor app).
Click to expand...
Click to collapse
Kernel Adiutor Sound controls are broken,
please use Faux Sound Control instead, that works;
I'll see what I can find on that CPU + GPU reduction during bootup,
but this will take some time, focusing on several projects (Android + non-Android) at the same time, so need to triage

zacharias.maladroit said:
Kernel Adiutor Sound controls are broken,
please use Faux Sound Control instead, that works;
I'll see what I can find on that CPU + GPU reduction during bootup,
but this will take some time, focusing on several projects (Android + non-Android) at the same time, so need to triage
Click to expand...
Click to collapse
cool enjoy your works

zacharias.maladroit said:
Kernel Adiutor Sound controls are broken,
please use Faux Sound Control instead, that works;
I'll see what I can find on that CPU + GPU reduction during bootup,
but this will take some time, focusing on several projects (Android + non-Android) at the same time, so need to triage
Click to expand...
Click to collapse
I've tried that also but seems to me only Headphones are working and speakers does nothing. Can you please try again and let me know ?
For the GPU/CPU, It would be better if you down clock them by 50% default and clock it higher after OS is loaded using init.d or something else.
Thanks

same problem here
please do a fix with the broken sound using audio output.. Only headset working flawlessly. thank

please add a touch boost swich in the next update,and fix twrp mtp mode,can not link with computer.thx

I used kernel Andro v31 and now i flash and use Zachs kernel, but SuperSu automatic updated and now i can't install binary for it. Anyone can help me?

i use this kernel i want to know how to flash supersu2.76 and how to shut cpu 4..please

renkahinkaru said:
i used kernel andro v31 and now i flash and use zachs kernel, but supersu automatic updated and now i can't install binary for it. Anyone can help me?
Click to expand...
Click to collapse
??????

RenkaHinkaru said:
I used kernel Andro v31 and now i flash and use Zachs kernel, but SuperSu automatic updated and now i can't install binary for it. Anyone can help me?
Click to expand...
Click to collapse
Dont let it update then...
---------- Post added at 03:27 AM ---------- Previous post was at 03:26 AM ----------
death_note7 said:
same too,abandoned this kernel itâ??is overheat than stock kernel
Click to expand...
Click to collapse
Its hot, its not overheating. Temps should only be considered as overheating when >80

Features:
(will add more later if I forgot anything)
Features said:
@AndroPlus for build-scripts, kernel patches
@Tommy-Geenexus for kernel patches, fixes
pstore
LPM (low power mode, battery efficiency)
fix high load average (lower battery consumption)
microSD, internal SD reliability improvements
cpuidle improvements (battery efficiency)
fix page thrashing in case of low memory situation (when you disable zram)
vmalloc improvements (less memory fragmentation, better reliability of camera, wifi, etc. drivers with long runtime)
FauxSound
KCAL
WLAN: disable memdesc and ramdumps (thanks to @Tommy-Geenexus )
notification LED changes to green+blue (cyan), when battery is really full (thanks to @Tommy-Geenexus )
Powersuspend, QuickWakeup, Power Efficient Workqueues,
improved vibrator, faster/more reliable interactivity
bluetooth hidp, fix disconnect on idle timeout
a few general stability fixes & reliability improvements
added wakelock switches (only use, if you observe high drain with specific functions; might cause instabilities or higher battery drain !)
big.LITTLE optimization flags; aggressive compiler optimization flags
disabled KSM, it's a battery drainer and magically gets enabled by Sony's ROM so remove it
added BFQ i/o scheduler (now YOU show me where it's smoother ! )
improved noop i/o scheduler - now it's more bare, previously it was similar to simple i/o scheduler - now it should be optimum for bare metal SSD/microSD access
GPU default set to 180 MHz
cpu governors: added ZZMoove, elementalX
added vibrator intensity switch support
added a bunch touchpad (screen) and fingerprint scanner fixes & improvements
support for Sumire DSDS (dual sim) (testing, used single SIM ramdisk)
kudos to all devs working on android, whether at Linux Foundation (Linux Kernel), Android (Google), Codeaurora, XDA or elsewhere - YOU ROCK !
this one looks to be more battery friendly
WIP branch
NEW features
sys-fs interface to control vibrator intensity (some kernel tools might support it)
lowered init value of screen during bootup: now you shouldn't get 100% BLINDED when rebooting :cyclops:
core 0 and 4 are now always on (per default, unless you play around with core_ctl) - allows changing governor settings for the big cores
mmc crc checksum is disabled by default (?) - 30% or more higher performance, re-enable if you favor integrity
KEXEC support - give @Myself5 's MultiROM a test-drive if you're curious (http://forum.xda-developers.com/xperia-z5/orig-development/mod-multirom-v33x-t3374763)
added Alucard cpufreq governor, if it's too laggy, unstable, etc. - I'm throwing it out the airlock
added a few additional changes thanks to @AndroPlus
.
224 version bump (224 ROMs ONLY)
RAM (working memory) energy efficiency improvements, thanks to @AndroPlus to spot it
overclocking support "big" core ~ 2.1 GHz, "little" core ~ 1.7 GHz (the "little" core is less tolerant for OC, less stable)
changed optimization flags (evaluation), should now be more stable but also faster, efficient
.
Z4/Z3+ support
224_I.1_2_9:
during bootup ony the small core cluster is active == cooler bootup, but potentially also slower (it should however be fast enough)
Overclocking: active after Boot, BIG core @2.2 GHz, adjust with Kernel Adiutor, etc.
Click to expand...
Click to collapse
Overclocking:
The following threads are for the Z5 - so naturally the thermal engine needs to be adapted to work on the Z4/Z3+
http://forum.xda-developers.com/xperia-z5/general/tweak-improve-performance-reduce-t3387879
http://forum.xda-developers.com/showpost.php?p=67444047&postcount=150 ( @_LLJY 's thermal-engine modifications (for Z5) are attached )
Source:
https://github.com/zachariasmaladro...i_r2/commits/Sun-Kernel_32.2.A.0.224_vI.1_2_9
Download: AndroidFileHost :
SunKernel_for_Z4_Z3Plus 224_I.1_2_9
224_I.1_2_9 Changelog said:
Changelog:
during bootup ony the small core cluster is active == cooler bootup, but potentially also slower (it should however be fast enough)
Overclocking: active after Boot, BIG core @2.2 GHz, adjust with Kernel Adiutor, etc.
Click to expand...
Click to collapse
Thanks

Left for posterity, but no further development will occur (see 4/30/2020 post)...
Here's a script that I helped some good guys out with developing "back in the day" (Franco's Dev Team - you can look them up!). Actually, it is a trimmed, consolidated version of the set-of-scripts we came up with. If you search, you can find osm0sis still hosts the original files, and those that I have been maintaining since the Galaxy Nexus went extinct (through L, M, N, and now O), I believe. Note that those scripts will no longer on Android 10 - and probably not even on 9 - so I don't recommend actually using them.
This script has all of the original tuning scripts put into a single file, having stripped out anything that stopped working between Kit-Kat and Android 10 (which was substantial), and some very small improvements I've found over the years. I also added a few things more to my personal usage preference for this Pixel-2/XL version. It has also been trimmed to work on the Pixel 2 / Pixel 2 XL stock kernel whilst outputting no errors, on all android versions through Android 10, and now on Magisk 19.4+.
Notes:
- This script is lean and mean, but it's not rocket science.
- I didn't invent anything here. Feel free to use (or not), distribute, alter, whatever; to your satisfaction, giving credit for redistribution only to "Franco's Dev Team", and maybe me if you're feeling generous.
- Again, I have verified it works on my personal Pixel 2 XL, and is compatible with all Android versions, Kernels, and Magisk versions.
- It actually improves many benchmark scores (you know the usual culprits) without lowering any on my device. But, you know what that's worth (one device, only a few items likely significant on a statistical basis).
- It won't make your phone run any worse. It might even feel a bit "snappier", but YMMV.
- If you feel this script is good, bad, or does nothing, feel free to thank me - or hang me in effigy, as appropriate.
- I do not plan to do heavy maintenance on this, but I will keep it up to date so it at least safely runs on the Pixel 2 / 2XL as long as I own one. I will post updates with a minimal change log (it's a script, you can read it!).
Disclaimer:
I can't see how this could possibly cause irreparable harm to any android device on which it is run.
However, I suppose untested configurations may (rarely) have slow-downs, reboots, or other effects.
REGARDLESS, it is offered as-is with no warranty, and you choose to run this at your own risk.
Requirements:
Root
BusyBox installation (I recommend the Magisk module by osm0sis)
Knowledge of how to execute a linux script and/or where to place it / allow permissions to run on boot
Usage:
Download attachment to your device
Place file in /data/adb/service.d (for Magisk-rooted devices, using Magisk 18.0+)
remove ".txt" extension (leaving the .sh extension)
Ensure permissions are right (0755)
Reboot and wait 2 minutes
Credits:
Franco's Dev Team, esp. osm0sis
Google
Others as noted in the script file header

Change Log:
Version 34 (98pks34.sh):
Version added with no disabling of zram.
V33 is still active for those who don't need / want zram.
V33 generic is still active as well (V34 generic would be the same as generic version does not alter zram).
Version 33 (98pks33.sh):
- Updated with Franco Dev-Team tuned Deadline scheduler (still the fastest). Script uses this if Deadline is available in your scheduler, else it defaults to using Noop.
- Other very minor tweaks based on testing, and some code cleanup
Version 32 (98pks32.sh):
- Updated for Magisk 19.4 (primarily eliminated mounting calls on / and /system to prevent root interference or verity problems due to SAR implementation now standard)
- Backed off the schedutil governor performance tweaks just a bit, still more performance oriented then v30 and prior, just not as extreme
- Removed wakelock blocking (for now) for evaluation. Most kernels already block safe wakelocks anyway. If I find none of the benefits I'm looking for, I may add them back in the next release.
- Released corresponding device-generic version due to important Magisk / SAR compatibility updates
Version 31 (98pks31.sh):
- Simplified some VM settings / reverted to stock where no difference was noted
- Simplified some block IO parameters / reverted to stock where no difference was noted
- Increased transmission queue buffer based on latest testing (still lower than stock)
- Tuned Schedutil governor settings to bias for more performance, reduce lag
- Increase GPU min frequency to 342 MHz step (2nd from bottom) based on testing to reduce lag
- Note that these changes did not appreciably affect battery life in testing
- Simplified output file write-out
- Released official "generic device" companion script of this version for those asking
Version 30 (98pks30.sh):
! GOOD TO GO FOR Q-FINAL / A-10 !
- Re-enabled stock zram - was causing freezes after about 24-36 hours of uptime
- Re-enabled vm tweaks for increased battery life (disabled pdflush periodic writebacks, lowered potential for large data writes causing hang-ups as a result in dirty ratios, adjusted cache pressure to not favor dentry/inodes quite so hugely over pagecache)
- Blocked a few more known and safe-to-block wakelocks
Version 29 (98pks29.sh):
Reverted some changes that were causing some serious jank / freezes:
- Went back to noop
- Reintroduced periodic pdflush writeback (although less frequent than stock)
Version 28 (94pks28.sh):
Biggest changes in a while!
- Increased run delay to 2 minutes to stay out of kernel apps' way
- Reverted tcp_ecn to 2 (stock) for slight decrease in network latency
- Substantial vm tweaks for increased battery life (disabled pdflush periodic writebacks, lowered potential for large data writes causing hang-ups as a result in dirty ratios, adjusted cache pressure to not favor dentry/inodes quite so hugely over pagecache)
- Right-sized nr_requests for any scheduler (not just noop) relative to built-in Android queue-depth
- Changed scheduler to deadline* with Franco Dev Team's tuning tweaks (still fastest i/o I can manage in testing)
* Device-generic version (94pks28generic.sh) was left unchanged with noop scheduler
Version 27 (94pks27.sh):
- Fixed for Android Q while keeping backward compatibility with prior Android versions.
- Increased run delay to 90 seconds to stay out of magisk module or kernel apps' way.
Version 26 (94pks26.sh):
- Updated one minor (but hard to find), error in mount option filesystem tweaks that had been causing data connectivity issues on custom ROM's using this script or BlackenedMod.
- SPECIAL THANKS to @sublimaze for testing iterations until we found the root cause of this issue!
Version 25 - skipped, test versions for @sublimaze to help me figure out data connection issues.
Version 24 (94pks24.sh):
- Updated ext4 filesystem tweaks for even better battery life and performance
- Small reduction of entropy pool size based on other user feedback
Version 23 (94pks23.sh):
- Change header to list new Magisk 18.0+ late-start boot service folder location
- SEE ALSO OP FOR THIS LOCATION
Version 22 (94pks22.sh):
- Force read_ahead_kb to 1024 for faster I/O performance on all realistic file sizes
Version 21 (94pks21.sh):
- Increased load delay at boot back to 60s.
Version 20 (94pks20.sh):
- Added .sh extension to file to allow more flexibility for future tuning (now just delete .txt, but leave .sh in the file name before copying to run location)
- Slightly increased load time at boot to 40s to ensure script runs even for users with many magisk modules
- Reduced foreground app schedtune boost to 5% (was 10%) for battery saving when multiple apps are open with no perceived detriment to performance or app switching
- Increase dirty_expire and dirty_writeback timings for less overhead, reduced battery, and improved performance with no ill effects noted
- Reverted GPU min clock increase due to my testing finding the speed benefit was not noticeable but battery life was negatively affected
Version 19 (94pks19):
- Reduced load time at boot (enabled by re-ordering of script) to 30s
- tcp_ecn set to 1 for across-the-board network speed enhancement when handshake allows
- reduced txqueuelen to 128 for network speed enhancement on 4g/wifi (less bufferbloat)
- added wakelock blocker courtesy of @xFirefly93, but only for blocking wakelocks I have actually seen in BBS for Pixel 2 / XL.
Version 18 (94pks18):
- Increase cpu governor up-rate-time; VERY significant battery help with no performance degradation noticed.
- Reduce vm dirty ratio and dirty expires slightly to reduce potential (although unlikely) excess caching and latency from memory write-out.
- Slight code re-ordering for potential quicker boot delay in the future
Version 17 (94pks17):
- Schedtune code cleanup
- GPU min frequency set to 342 (performance boost with no adverse battery drain per @xFirefly93 testing)
- Increase cpu governor down rate limit by 25% for better performance with minimal battery life impact.
Version 16 (94pks16):
- Revert dir-notify-disable
- Fix a minor dirty-expire vm derp I made many, many releases ago
- Adjust dev/stune/schedtune parameters to ensure users won't have frequency scaling issues on any kernel, allowing cpu's to actually settle and sleep. This wasn't likely before, but is now virtually impossible, while performance improvement during app switching is still present!
Version 15 (94pks15):
- Fs dir-notify disable.
- Schedtune parameter tweaks for performance increase.
Credit: Both of the above were initiated by @xFirefly93, I only slightly modified the Schedtune parameters.
Version 14 (94pks14):
- Revert disabling service_locator, otg_wakelock, and debug kernel modules - no real battery save noted in testing; and I had some issues with apps hanging that required location services that were resolved by getting rid of this code.
- Change rq_affinity from 2 to 1 - I verified with I/O benchmark testing that this provides a slight increase in I/O performance, especially reads and sqlite operations. No battery life impact noted during days of testing.
Version 13 (94pks13): Internal test build - not released (probably would have been unlucky anyway )
Version 12 (94pks12):
- Turn off iostats - by popular request (slight battery save)
- Increase vm stat_interval to 60 - Thx to xFirefly93 (slight battery save)
- Disable service_locator, otg_wakelock, and debug kernel modules - Thx to xFirefly93 (slight battery save)
Version 11 (94pks11):
- Delay script start by 30 seconds for users with multiple late-start scripts or other Magisk modules
- Increase timer for vm dirty writeback (saves battery from less wake-ups, cache integrity still reasonably protected by low dirty background ratio)
- Slight kernel entropy increase
Version 10 (94pks10):
- Increase min_free_kbytes - better performance based on testing
- Reduce entropy read_wakeup_threshold - to prevent blocking apps or commands if entropy drops
- Thrift ipv4 / network settings that were ineffectual - cleanup with better or same performance based on testing
- Reduce scheduler nr_requests - less overhead, subjective latency reduction
- Revert to default read_ahead_kb - better performance based on testing
Version 9 (94pks9):
- Slight change-up on kernel entropy settings to keep pool about half-full.
- tcp_max_syn_backlog and tcp_ecn parameters added (thanks @Juzman for getting me to look at these!) that seem to help network throughput slightly - they certainly don't hurt.
- Added fstrim for data, cache, and system partitions at end of script - because why not do this on every boot?
Version 8 (94pks8):
New file location noted in header: /sbin/.core/img/.core/service.d
- Need to place script in this directory for Magisk 16.3 onward
- Backward compatible for previous versions back to 14.5
Script now executes 70% faster after boot
- Only sleeps for 30 seconds; verified to still run through Magisk late start service
Added file system optimizations for /system partition
Adjusted min_free_kbytes to 7 GB from 7.5
- Should slightly raise available RAM for each node, no oom increase or other ill-effects verified through dmesg / kmesg logs
Reverted vm.vfs_cache_pressure to 20
- Less subjective latency based on testing
Script success / fail write-out file now time stamped for users local time rather than UTC/GMT
Version 7 (94pks7):
- Removed LMK (yay!) based on multiple requests, advice from @Scott, and my verifying that nothing I tried improved over stock.
- Added back in some block-level scheduler queue tweaks that are not consistent (and not optimized) on all blocks in the stock configuration as I thought they were
- Cleaned up and re-organized the code - inspiration from @Juzman
- Re-evaluated vm settings @Scott) and network tweaks @Juzman); I don't believe this resulted in any changes (except I'm trialing cache_pressure at 60 vice 20), but thanks for their advice, research, testing, and participation (which is also now credited in the script).
Version 6 (94pks6):
- Added feature: script now writes out a file "pks_script_result" to the /storage/emulated/0 (root of internal storage) directory when executed.
- If the file is present after attempting to run (or after a reboot if you have it in su.d, init.d, or service.d folders) then this indicates the script executed.
- If when you open the file in a text viewer it has a time/date stamp and the phrase "94pks6 successfully executed!", then it ran without errors.
- If when you open the file it says instead "94pks failed." then it threw some error code upon execution... but it was probably minor enough that the changes were applied (or the file wouldn't have been written ).
All the above is at least in theory. It seems to be working that way on my device. Thanks to @Scott for the suggestion!
Version 5 (94pks5):
- Lowered last lmk slot (empty apps) much further - no appreciable loss of available RAM during my testing, less redraws in chrome tabs and reloading of recent apps.
Version 4 (94pks4):
- Fixed aggressive Lowmemorykiller / memory over-commit interaction issue (only last LMK slot now much more aggressive than stock, vm.overcommit_memory reverted to "1" (stock). The interaction with previous settings could cause an issue where no additional apps could be opened (they were immediately killed).
- Very minor tweaks to some vm caching parameters
Version 3 (94pks3):
Corrected swap off command to not throw error flag on execution
Altered tx_queue_len replacement command to skip non-linked file and not flag error on execution
Thanks @Lessaj and @veetoe for helping
Version 2 (94pks2):
1). Increased LMK levels
---- I tested for weeks, we have gobs of RAM, it should really only affect empty apps
2). Turned off swap and de-allocated zram space
---- With 4GB of RAM, do we need zram? I don't think so. I found benchmarks and day-to-day performance to be slightly better without it, plus this is further enabled by increased LMK levels (in theory).
3). Reduced the vm dirty expire / writeback by a factor of 10 (still far more aggressive than stock)
---- No real effect here, just walking back to stock since I see no real effect with these parameters on Pixel 2.
4). Enabled Schedutil governor IO_wait_boost flag for both little and big clusters.
---- Should boost performance / reduce latency during high I/O events, found it to marginally increase some benchmarks and subjective performance feel without affecting battery (YMMV).

What if one doesn't have service.d in magisk?
Sent from my Pixel 2 XL using Tapatalk

I might give this a go in the morning. Add it and reboot in a full charge before I go to work. Using Flash kernel with my 2 XL, but hey, I'm always down for tweaking and tuning. I'll report back.

bryantjopplin said:
What if one doesn't have service.d in magisk?
Click to expand...
Click to collapse
You won't see it in the app. Use a root browser of some kind.
Root Partition/Magisk/.core/service.d
That would be the file path.

It wasn't there, just added it. Picture confirmed it was a folder
Sent from my Pixel 2 XL using Tapatalk

TheGeekyNimrod said:
I might give this a go in the morning. Add it and reboot in a full charge before I go to work. Using Flash kernel with my 2 XL, but hey, I'm always down for tweaking and tuning. I'll report back.
Click to expand...
Click to collapse
Should work fine with custom kernels... I'm just not sure if any of the tweaks might not already be in Flash - I know a couple aren't. Thanks for giving it a try and reporting back.
TheGeekyNimrod said:
You won't see it in the app. Use a root browser of some kind.
Root Partition/Magisk/.core/service.d
That would be the file path.
Click to expand...
Click to collapse
Thanks for helping others out while I was away!
bryantjopplin said:
It wasn't there, just added it. Picture confirmed it was a folder
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
That's truly odd - I've had 3 different devices with Magisk and they always had that folder. Could be that it was hidden to your file explorer of choice, especially since some of the folder names start with, or have "." in them? I dunno. Hopefully adding the folder manually like you did just works.

pkgnex said:
Should work fine with custom kernels... I'm just not sure if any of the tweaks might not already be in Flash - I know a couple aren't. Thanks for giving it a try and reporting back.
Thanks for helping others out while I was away!
That's truly odd - I've had 3 different devices with Magisk and they always had that folder. Could be that it was hidden to your file explorer of choice, especially since some of the folder names start with, or have "." in them? I dunno. Hopefully adding the folder manually like you did just works.
Click to expand...
Click to collapse
Using root explorer since OG Droid. Others are inferior imo. Thanks for checking up.
Sent from my Pixel 2 XL using Tapatalk

I had to show hidden files in Solid Explorer to see that folder! Thanks for the script!
Sent from my Pixel 2 XL using Tapatalk

bryantjopplin said:
Using root explorer since OG Droid. Others are inferior imo. Thanks for checking up.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Same one I use!
henderjr said:
I had to show hidden files in Solid Explorer to see that folder! Thanks for the script!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You're welcome.

Easy way to tell if the script is working? Or pretty much seeing this here is enough?

henderjr said:
Easy way to tell if the script is working? Or pretty much seeing this here is enough?
Click to expand...
Click to collapse
Which kernel are you running? If it's stock, the easiest way to tell for sure is to install a kernel editor (EX by FLAR2 is a good one, but there are others if you have to pay for that one, I forget) and see if some of the parameters in the script "took" like low memory killer values, vm parameters, entropy values, read-ahead kb, io-scheduler being noop instead of CFQ, etc. I know Flash uses cfq as the default sceduler, so if you're returning noop, that would indicate the script ran. I'm not sure what the default scheduler is on Despair's Snoke.
One thing - I don't think the folder you have it in is right. I think the path should be (root)/Magisk/.core/service.d NOT (root)/DEV/Magisk/IMG/.core/service.d
Just remembered, another way to see if it ran is to open Magisk manager, go into settings, click "log" and select the "Magisk" tab. You should see a bunch of stuff, but near the bottom you should see:
: ** late_start service mode running
: * Running service.d scripts
service.d: exec [94pks]

pkgnex said:
Which kernel are you running? If it's stock, the easiest way to tell for sure is to install a kernel editor (EX by FLAR2 is a good one, but there are others if you have to pay for that one, I forget) and see if some of the parameters in the script "took" like low memory killer values, vm parameters, entropy values, read-ahead kb, io-scheduler being noop instead of CFQ, etc. I know Flash uses cfq as the default sceduler, so if you're returning noop, that would indicate the script ran. I'm not sure what the default scheduler is on Despair's Snoke.
One thing - I don't think the folder you have it in is right. I think the path should be (root)/Magisk/.core/service.d NOT (root)/DEV/Magisk/IMG/.core/service.d
Just remembered, another way to see if it ran is to open Magisk manager, go into settings, click "log" and select the "Magisk" tab. You should see a bunch of stuff, but near the bottom you should see:
: ** late_start service mode running
: * Running service.d scripts
service.d: exec [94pks]
Click to expand...
Click to collapse
I'm stock 8.1 right now besides Magisk with Adaway.
The script is is in both places though I only remember putting it in one. Wonder if one is a copy of the other.
Anyway I see it in the logs so we should be good. Thanks again!

henderjr said:
I'm stock 8.1 right now besides Magisk with Adaway.
The script is is in both places though I only remember putting it in one. Wonder if one is a copy of the other.
Anyway I see it in the logs so we should be good. Thanks again!
Click to expand...
Click to collapse
One location is probably a sym-link to the other, then. Good to know!
I'm still running 8.0, so at least I now know it works on 8.1 as well.

On 8.1.0....
Seems??? To work. Little snappier

imaverik said:
On 8.1.0....
Seems??? To work. Little snappier
Click to expand...
Click to collapse
Thanks for the feedback! That's my experience as well.
These tunes/mods don't have as much of an effect as they used to, but I think they still offer a little improvement.

Any impact on battery,good or bad?

skinza said:
Any impact on battery,good or bad?
Click to expand...
Click to collapse
Should not affect battery at all, either way.
I guess in theory the faster network settings and io should mean you won't need your screen on as much, but any effect would not be noticeable.

So I've used the script alongside Flash Kernel beta and a few tweaks of my own. Can't really say I've noticed a battery difference as I also use Disable service and others. But I do feel there is a slight increase in response time whether it's touch, transition, fingerprint, etc.

pkgnex said:
Which kernel are you running? If it's stock, the easiest way to tell for sure is to install a kernel editor (EX by FLAR2 is a good one, but there are others if you have to pay for that one, I forget) and see if some of the parameters in the script "took" like low memory killer values, vm parameters, entropy values, read-ahead kb, io-scheduler being noop instead of CFQ, etc. I know Flash uses cfq as the default sceduler, so if you're returning noop, that would indicate the script ran. I'm not sure what the default scheduler is on Despair's Snoke.
One thing - I don't think the folder you have it in is right. I think the path should be (root)/Magisk/.core/service.d NOT (root)/DEV/Magisk/IMG/.core/service.d
Just remembered, another way to see if it ran is to open Magisk manager, go into settings, click "log" and select the "Magisk" tab. You should see a bunch of stuff, but near the bottom you should see:
: ** late_start service mode running
: * Running service.d scripts
service.d: exec [94pks]
Click to expand...
Click to collapse
Followed the above instructions
Ran no problem