Develop Bugs

[INFO] Galaxy nexus all-in-one guide with tweaks for performance and battery life

ok, from my android tweaking and modding i know it can be somewhat hard to find everything you might need to make the most of your galaxy nexus so i will put links to them here along with providing support and my own little discoveries here...
This will include everything from guides to different type of tweaks, recommended settings, flashable mods, etc...you name it and it will probably be in here (as i update it)
Any suggestions are highly appreciated and will be added with proper credit
***disclaimer- I am not responsible for any damage you may do to your device, please make sure to have a backup before doing any of these tweaks***
(still a work in progress and expect much much more to come)

Guides/Toolkits
[GNex TOOLKIT] Drivers, Backup, Unlock, Root, CWM, Flash, Mods + MORE [VERIZON]
[EASIEST ROOT/UNLOCK TOOLKIT] Wugfresh Galaxy Nexus Root Toolkit v1.4

Build.prop tweaks
To use these just mount /system rw, open build.prop in a text editor, add/modify whichever lines you want, save, reboot recovery, wipe cache and dalvik cache, then reboot
Code:
#incoming ringer delay (already in build.prop) sets how soon (in ms) the phone starts ringing when a call comes in. set between 0 and 3000
ro.telephony.call_ring.delay=
Possible battery saver-
Code:
#disable sending usage data to google
ro.config.nocheckin=1
Code:
#sleep mode for battery savings. 0 power collapse suspend, 1 power collapse (best), 2 apps go to sleep, 3 show clock and wait, 4 wait for interrupt
pm.sleep_mode=
Code:
#change lcd density (already in build.prop), which is like changing the resolution on a windows computer can be anywhere from 240 to 360 (stock 320)
ro.sf.lcd_density=
Performance enhancement, may also help with battery life
Code:
#dalvik cache virtual memory size
dalvik.vm.heapsize= (stock 256m, recommended 320m)
dalvik.vm.heapstartsize= (stock 16m)
dalvik.vm.heapgrowthlimit= (stock 128m)
Can improve overall scrolling fluidity and speed
Code:
# This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec= (recommended 275)
General performance tweak
Code:
#disable the zygote loader
ro.wmt.blcr.enable=0
Extended jni checking is costly in terms of performance and battery life so disabling them is suggested
Code:
#disable extended dalvik jni checking
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=0
Helps with overall performance
Code:
debug.performance.tuning=1
video.accelerate.hw=1
Helps increase picture/video taking quality and video viewing
Code:
#Raise Photo and video quality?
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.hprof.vid.fps=65
Code:
#help to free up unused ram
persist.sys.purgeable_assets=1
Disables notification of usb debugging
Code:
#stop usb debugging on notification
persist.adb.notify=0
enables/disables (set to 0) dithering
Code:
#Improve screen quality at the cost of performance
persist.sys.use.dithering=1
Code:
#Use dalvik JIT compiler (Just In Time compiler is much faster and should be enabled by default)
dalvik.vm.execution-mode=int:jit
Code:
#disable camera sound?
persist.sys.camera-sound=0
Dalvik vm dexopt tweaks (USE ONE OR THE OTHER, NOT BOTH, i prefer option 2)-
option 1- disable dalvik checking, increases free ram but less optimized dalvik cache
Code:
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,u=n,o=v
option 2- enable more checking for a better performing dalvik cache but may use a little more ram
Code:
dalvik.vm.verify-bytecode=true
dalvik.vm.dexopt-flags=v=f,u=n,o=v

Init.d tweaks
To use mount /system rw, go to /system/etc/init.d create new file, add the lines in, save, and set permissions to rwxr-xr-x
Code:
#disable logcat
rm dev/log/main

Recoveries/Radios/Etc
List of flashable verizon radios-
radiosvzw-all-radios-in-flashable-zip/
Team win recovery project (custom touchscreen recovery-
twrp-212-touch-recovery-2012-04-20/
Clockwork recovery touch toro-
recovery-clockwork-touch-5.8.0.2-toro.img
clockwork recovery no skip edition-
recoverycdma-clockwork-recovery-v5504-no-skip-edition/

Mods/other
Suggested color control settings-
whitest whites
red 200
green 200
blue 265
gamma red -6
gamma green 0
gamma blue 8
omap4 gamma 6 (1.2 via franco app)
Morfic battery saving settings-
Red 135
green 135
blue 200
gamma red 0
gamma green 0
gamma blue 0
omap4 gamma 6 (1.2 via franco app)
Franco suggested settings-
Red 180
Green 192
Blue 200
gamma red -4
gamma green 0
gamma blue 5
omap4 gamma 6 (1.2 via franco app)
Custom auto brightness tweaks (super power save + conservative power save settings)
For both sets of settings-
Light sensor filter enabled yes
Window length 5s
Reset threshold 400 lux
Sample interval 5s
Use custom yes
Screen dim level 1
Allow light decrease yes
Decrease hysteresis 50%
Conservative power save settings-
Edit other levels under screen column-
15
17
19
21
23
25
27
30
32
40
49
54
65
75
100
125
146
179
211
225
Super power save settings-
Edit other levels under screen column-
6
8
9
11
12
14
16
19
23
27
33
40
50
64
85
97
111
146
178
225

Look here:
http://forum.xda-developers.com/showthread.php?t=1599025&highlight=battery
and here:
http://forum.xda-developers.com/showthread.php?t=1462020&highlight=battery

metalspring said:
Suggested color control settings for whitest whites-
red 200
green 200
blue 265
gamma red -6
gamma green 0
gamma blue 8
omap4 gamma 6 (1.2 via franco app)
Click to expand...
Click to collapse
Could you add the recommended overall color multiplier values?
Red 180
Green 192
Blue 200
Gamma (cannot remember, might be 1.2)

Hi,
Maybe an explanation for each tweaks would be great
X tweaks do this (for battery life or performance) but do this,etc...
The tweaks for the build.prop already exists (there is maybe 3/4 or more threads) in the Android section,some of these have not effect in ICS...
And maybe the general section is more appropriate...?
In any case thanks for this.

viking37 said:
Hi,
Maybe an explanation for each tweaks would be great
Click to expand...
Click to collapse
most have a simple explanation, the ones that dont are general performance/battery life tweaks
any in particular you dont understand?
I'll be happy to add in more detailed explanations on those

metalspring said:
most have a simple explanation, the ones that dont are general performance/battery life tweaks
any in particular you dont understand?
I'll be happy to add in more detailed explanations on those
Click to expand...
Click to collapse
Me,I understand because I've tested most of these and I use Google to understand what they do.But most of the users will ask,for sure...
You suggest some tweaks...I think you could suggest an explanation that comes with.
Not just a compilation of tweaks...
It's just my opinion...

Theshawty said:
Could you add the recommended overall color multiplier values?
Red 180
Green 192
Blue 200
Gamma (cannot remember, might be 1.2)
Click to expand...
Click to collapse
Those are included in the franco app but i guess i can put them in too, maybe morfics battery saver ones too if someone posts them (or i find them somewhere)
viking37 said:
Me,I understand because I've tested most of these and I use Google to understand what they do.But most of the users will ask,for sure...
You suggest some tweaks...I think you could suggest an explanation that comes with.
Not just a compilation of tweaks...
It's just my opinion...
Click to expand...
Click to collapse
I did add some explanations but i still think many explain themselves...unless you're talking about the dalvik dexopt ones...those are somewhat technical

metalspring said:
List of flashable verizon radios-
radiosvzw-all-radios-in-flashable-zip/
Team win recovery project (custom touchscreen recovery-
twrp-212-touch-recovery-2012-04-20/
Clockwork recovery touch toro-
recovery-clockwork-touch-5.8.0.2-toro.img
clockwork recovery no skip edition-
recoverycdma-clockwork-recovery-v5504-no-skip-edition/
Click to expand...
Click to collapse
These all look to be only Verizon / cdma versions,why post this in the GSM section?

For Trinity Spiceeeee use these values:
Multipliers:
Red 135(0000)
Green 135(0000)
Blue 200(0000)
Gamma: 0,0,0
Give your brain some time to adjust like Master Morfic says and you'll never wanna go back to stock colors again
Also play around with Gamma/Omap4 control for contrast
Verstuurd van mijn Galaxy Nexus met Tapatalk

odin13 said:
For Trinity Spiceeeee use these values:
Multipliers:
Red 135(0000)
Green 135(0000)
Blue 200(0000)
Gamma: 0,0,0
Give your brain some time to adjust like Master Morfic says and you'll never wanna go back to stock colors again
Also play around with Gamma/Omap4 control for contrast
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
Are you sure they're the same? also what about OMAP?

What do you mean?
Verstuurd van mijn Galaxy Nexus met Tapatalk

odin13 said:
What do you mean?
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
1) Are you sure the values are the same or they're just similar?
2) What did you set for OMAP4 Gamma Interface?

3rdstring said:
These all look to be only Verizon / cdma versions,why post this in the GSM section?
Click to expand...
Click to collapse
I just put the Verizon/cdma versions up first since that's what I have, I'll add in the sprint and GSM versions too if someone can give me a link to them

Just tried some of your tweaks (build.prop) and coloursettings and everything seems to be working fine. Colours look similiar to Trinities, little better imo. While scrolling a bit it feels a little bit faster, but that can just be the result of a placebo though.
Thnx for posting this!

Added custom auto brightness tweaks for custom roms with that option (should help save a lot of battery, actually can go lower than manual brightness)

[Kernel][AOSP][2.02 | November 2nd] Plasma kernel

{
"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"
}
I. Thanks!
.
Disclaimer: I take no responsibility for any damage that might occur to your device. You proceed strictly at your own risk. This is a work in progress.​Thank you for your interest in Plasma kernel, I hope you enjoy it. I've poured hundreds upon hundreds of hours of work into putting together a kernel that best showcases our hardware. Plasma kernel would not be possible without super-smart people like AndreiLux, DerTeufel, temasek, googyanas, faux123, and the regular contributors to the official cm kernel repositories. Please donate to them to support their hard work!​.
II. Features
CPU frequency range: 100MHz to 2.16GHz
ZZMoove, PegasusQ, performance (with support for multiple cores), and LulzactiveQ CPU governors
Zen, noop, deadline, row, cfq, sio, vr schedulers
Experimental Wolfson AND Voodoo Sound support (choose one or the other on the Audio tab of STweaks, then REBOOT!)
CPU voltage control
Linux 3.0.101
AndreiLux: Screen color calibration with mdnie-control
GPU over/underclock and over/undervolt
Control the frequency and voltage of all 5 GPU steps
Support for GPU clocks from 54MHz to beyond 800MHz
Control GPU governor sampling rate
Built with 4.8 toolchain
Built with -O3 and other optimizations
Extra panel brightness (<299)
Faux123: Dynamic fsync control (v1.2)
AndreiLux: Charging control
Support for STweaks
Control screen refresh rate (can be reduced to save battery)
AndreiLux: Memory/internal voltage control interface
AndreiLux: Adaptive Body Bias (ABB) control
AndreiLux: Digital brightness control/reduction (better than ScreenFilter)
LED control (with some color mixing adjustments by me)
Touchwake support, including touchkeys (enable in Screen tab of STweaks)
Multi-touch kernel-based gesture engine
Proportional Rate Reduction for TCP
Joe's RCU
Temasek: Frandom module (enable on the Memory/Internal tab of STweaks and REBOOT!)
S-Pen settings on the S-PEN tab of STweaks
zCache
Support for 4x parallel "Turbo ZRAM" (settings are on the "I/O / RAM" tab of STweaks)
UKSM
Enhanced Touchwake/Slide2Wake functionality
Arc-swipes to turn your phone on with one hand (Screen tab of STweaks)
Long-tap-off to turn your device off with one hand (Screen tab of STweaks)
Power off gesture: tap the top of the screen and a touchkey at the same time to trigger suspend
Change your power manager (PM) CPU lock frequency
Press the home button 4 times to toggle the screen negative
Press the home buttom 3 times as fast as you can to toggle the screen into nightmode (red)
exFAT support
For more, take a look at the commits
.
III. What's NewDon't forget to check out what was new in 2.0b7 and 2.0b12!​
[ZRAM Total Disk Size]: By default ZRAM is setup as four (4x) swaps operating in parallel at equal priorities. Set this to the TOTAL amount of RAM you wish to dedicate to ZRAM, and STweaks will automatically divide it evenly by four.
[UKSM Enable]: Enable the UKSM daemon that will continuously scan memory for duplicate data.
[UKSM Daemon Sampling Rate]: How often the daemon checks for duplicate data.
[UKSM CPU Usage Limit]: How much system load (CPU usage) the daemon will use.
[Long-tap-off Always On]: Found in its own section under the Touchwake section. When enabled Longtapoff will always work, regardless of how you woke your device. Takes effect immediately.
[Many ZZMoove settings]: Many ZZMoove settings on the newly created "ZZMoove Scaling" and "ZZMoove Hotplug" tabs. Descriptions coming soon.
.
IV. Download / Donate
Support the development of Plasma kernel by DONATING if you find it useful!
AOSP 4.3.x only!
Plasma kernel v2.02 for Sprint Note 2 (L900)
Plasma Gesture Pack
Support the development of Plasma kernel by DONATING if you find it useful!
​.
V. Changelog
v2.02 (November 2nd, 2013)
Tracked audio/media skipping bug to disabled loggers (thanks pappschlumpf!) By default logging is now enabled. While you can still disable it, it will always be reset upon reboot.
Changes to write-back caching (thanks temasek)
Support for switching touchkey backlight driver from ROM/kernel (bottom of Screen tab in STweaks) (thanks Yank555-lu)
Some bug fixes for Slide2Wake
​.
VI. Archived Changelogs
2013-10-29 | v2.00
Linux 3.0.101 (thanks temasek)
Hopeful bugfixes for untouchable screen, and taps on top triggering suspend
Should you encounter a problem like that, cycling on and off (power button) should now reset any state variables
Fix FC issues. Works with more ROMs, including the latest AOSP nightlies
Allow pm_idx_freq to be set as high as 1600 MHz, theoretically could slightly speed up waking from deep sleep. Set on "Plasma Tuneables" tab of STweaks
Added several new tuneable ideas to zzmoove
Added "ZZMoove Scaling" and "ZZMoove Hotplug" tabs to STweaks. The descriptions are still a work in progress
Moved mDNIe controls to their own "Color" tab
Greatly enhanced the longpressoff feature's reliability and ease of use (by upgrading to scheduled_work)
Slide2Wake and arc swipes now trigger CPU and memory frequency locks to speed up waking
Slide2Wake and arc swipes no longer accidentally send input in the milliseconds after the screen comes on, but before you finished your gesture
Added option to Screen tab of STweaks to enable Longtapoff always, regardless of how the device woken
Expanded the trigger areas for slide2wake and arc swipes
ZRAM/swap is working and compatible with "Turbo ZRAM" (4x parallel ZRAM swaps for quad core devices) (thanks googyanas)
ZRAM settings in STweaks now allows you to set one total size of RAM that will be divided into 4x ZRAM swaps. Setting to 0 disables all swaps. Changes are applied instantly. No need for any other ZRAM/swap apps or init.d scripts.
UKSM (Ultra KSM (Kernel Samepage Merging)) enabled, with settings on the "I/O / RAM" tab of STweaks. Mostly just a novelty, but what it does is continuously checks RAM for duplicate pages to save space
zCache enabled and always running
Cleancache enabled
Frontswap enabled
Enabled LOWMEM_CHECK (thanks googyanas)
Enabled SPEEDUP_KEYRESUME as discussed in temasek's thread (Placebo effect? Maybe. Better ask Brian Molko. A cookie for you if you understand that reference) (thanks googyanas)
Added my own wake-speed ideas (2-second max-CPU-speed lock, and 2-second max-bus/RAM-speed lock on KEY_POWER press)
Permanently fixed (hopefully) the laggy, skippy, media bug
Toggle negative screen mode by taping the home button 4 times quickly (but NOT as fast as you can) (based on a commit by gokhanmoral)
Toggle nightmode (red) screen mode by pressing the home button 3 times VERY quickly (pretty much as fast as you can) This is purposely designed to be a dim red, as searing bright 255 red isn't particularly easy on your eyes in the dark. Fun fact: this (and the negative one described above) are functional even during boot...triple tap to see your bootscreen turn red
CPUFreq bug fixes/commits (thanks DerTeufel)
Permanent TRIM (thanks googyanas)
Added shell scripts to quickly and easily see statistics with as little typing as possible. Open a command prompt on your device, type "su" and press enter to ascend to root. Now you can type "szc" and press enter to see zCache statistics (szc = show zcache). Or type "ssw" to see swapfile/zRAM statistics (ssw = show swap). Note: Some statistics don't fully populate until a few minutes after boot
Experimental: Set ZZMoove governor for battery savings by obtaining a root shell as described above, then typing "zzb" and pressing enter (zzb = zzmove battery). Does not reapply after reboot.
Compiler optimizations
​2013-07-19 | v1.67
- Updated to Linux 3.0.84 [thanks, temasek]
- Enabled support for SELinux
- Fixed some bugs with the stylus touchkey block
- Voodoo was removed
- Sound-control is permanently enabled. Anything Voodoo did, sound-control can do.
- A bunch of ROW and other smaller cherry-picks
- Fixed some STweaks bugs
- Fixed some gestures in the Gesture Pack
​2013-06-26 | v1.65
- Updated to Linux 3.0.83 [thanks, temasek]
- Better battery life, particularly while idle. [thanks, temasek]
- Gesture engine now has support for two special gesture flags; TKEYS and EXCLUSIVE
- S-Pen: Disabled the booster and made it optional, as well as what frequency it boosts to. By default this used to lock at 800MHz when you used the pen, which has shown to be way overkill for the most part.
- S-Pen: Adjust input averaging strength (2 or 3 are the only useful settings. Wanna see what the actual input is from the digitizer? Set this to 0 and draw a line. Yeah...now you see what the poor driver has to filter out)
- S-Pen: Adjust box filter strength for pen input and hover input. Mostly experimental.
- S-Pen: Set minimum pressure before pen input is registered.
- S-Pen: Set fixed pressure (driver will never report sensitivity, and instead uses this value)
- S-Pen: Disable side button (for those that don't use it, it can really get in the way at times)
- S-Pen: X and Y axis offset (tweak this to your screen and usage. Samsung defaults this to -30 for right handed users)
- S-Pen: When the pen is within hovering distance, the touchkeys will now be disabled. When out of range, the block will be held for a definable period before restoring them. This means you can naturally write without fearing the buttons will come on and do crazy stuff.
- S-Pen: Disable touchscreen and gestures when drawing
- GPU: Frequency, voltage, and up/down threshold are available for each of the 5 steps.
- GPU: Expanded GPU clock options: 54, 100, 160, 200, 266, 275, 300, 333, 350, 400, 440, 500, 533, 600, 640, 666, 700, 733, 750, 800+ MHz.
- GPU: Adjustable GPU scaling driver polling frequency (sampling rate) [thanks, AndreiLux]
- GPU: Lock GPU to one user-defined step.
- GPU: Limit the GPU to less than 5 steps.
- GPU: Increase default GPU polling frequency to 100ms (stock was 1000ms (!!!) and causing laggy performance within the first few seconds of using your device). [thanks, AndreiLux]
- Fixed some STweaks bugs.
- A bunch of predefined gestures in the Gesture Pack.
​2013-06-11 | v1.60 [733 GPU overclock] / [No GPU overclock]
- Updated to Linux 3.0.81
- Added section to Screen tab in STweaks for touchkey backlight control (for ROMs without controls built in)
- Implemented mechanism to manually control the display panel's refresh rate (no, you can't go higher than 60fps )
- Added support for lcdfreq scaling in PegasusQ (on PegasusQ Scaling tab of STweaks)
- Added support for lcqfreq scaling on touch (on Screen tab of STweaks)
- Option to force lcdfreq's limited state to constantly be on, effectively giving you control of panel refresh rate (on Screen tab of STweaks)
- Made PegasusQ screen-off multicore policy enforcement more robust
​2013-06-08 | v1.58 [733 GPU overclock] / [No GPU overclock]
- Updated to Linux 3.0.80
- Switched to TCP Veno
- Updated zzmoove to version 0.4
- Added a sysfs entry to control the PM lock frequency
- Added screen-off tunables for PegasusQ, LulzactiveQ and zzmoove
- Added screen-off hotplugging to LulzactiveQ
- Led-control: more accurately mix LED colors
- Led-control: custom requests for white (255/255/255) are adjusted to obtain the most realistic actual color
- Led-control: change system notification (charging/charged) LED brightness level (LED tab of STweaks)
- Frandom module (enabled on the Memory/Internal tab of STweaks. A reboot is required after changing this setting!)
- Experimental: Reduce mdm wakelocks
- Updated row scheduler
- Experimental: Support for both Voodoo and Wolfson/sound-control. They both do they same thing though. Choose one on the Audio tab of STweaks, then reboot.
- Wacom: add sysfs entry for pen inserted (/sys/devices/virtual/sec/sec_epen/epen_pen_inserted)
- Dynamic fsync tweaks
- Many small cherrypicks
​2013-05-06 | v1.50 [733 GPU overclock] / [No GPU overclock]
- Updated to Linux 3.0.76
- Sbrissen's WiFi driver from the GT-9505
- Kernel-based multi-touch gesture support. Enable it on the Screen tab of STweaks. Flashable sample script to be added to this post soon.
- Touchwake now wakes from the touchkeys in addition to screen taps
- Updated zzmoove governor with changes from DerTeufel
- PegasusQ: calculate gradient of CPU load to early increase frequency
- Added LulzactiveQ governor
- Stopped an insane amount of kernel logging in cpuidle-exynos4
- Updated Wacom drivers
- Updated camera drivers
- Added Proportional Rate Reduction for TCP
- Added missing flexrate code and removed the default touchbooster
- Joe's RCU​2013-04-27 | v1.43 [733 GPU overclock] / v1.43 [No GPU overclock]
- Touchwake support. Enable it on the Screen tab of STweaks
- Some dynamic fsync commits​2013-04-26 | v1.42
- Updated to Linux 3.0.75
- Reworded the settings in STweaks for ABB
- Fixed a bug in Adaptive Body Bias (ABB) that caused certain frequencies to be offset. 800MHz was in slice 3 (instead of 2) and 1600MHz was in slice 4 (instead of 3). If you have been undervolting these frequencies recently, you need to reevaluate your stability at them now.​2013-04-25 | v1.41
- Updated to Linux 3.0.74
- Adaptive Body Bias (ABB) control. This is only for the most hardcore users. I suggest reading the note above, as well as this thread.
- Snappy compression added to zRAM
- Some kernel updates to speed up hotplugging
- Correctly applied load averaging patch to fix moire pattern
- New LED control. Offers better control over LED fading. If your ROM has its own fade control, be sure to match your chosen setting in the LED tab of STweaks to avoid possible issues
- mDNIe digital brightness reduction. Ever notice how the lowest screen brightness setting is still very bright, especially in a dark room? Many of us nighttime users have had to manually enable apps like ScreenFilter to overlay a black layer to artificially dim the screen via software. This is somewhat like that, but more accurate and done at the video driver level in the kernel. To summarize, it seamlessly allows you to reduce the typical brightness control beyond its normal minimum by digitally darkening the display data after a certain point. This is very cool, as it's all automatic once you initially tweak it - goodbye ScreenFilter! Adjust the settings on the Screen STweaks tab.
- Expanded explanation of ABB on its STweaks tab
- Unaligned memory access where possible
- Fixed a bug that was causing frequencies greater than 1600 to become stuck as the current frequency
- Added the zzmoove governor and tweaked it for this kernel
- Update ramdisk​2013-04-17 | v1.34 [733 GPU overclock] / [No GPU overclock]
- Updated to Linux 3.0.73
- Flexrate now works
- Other, smaller changes​2013-04-10 | v1.32 [733 GPU overclock] / [No GPU overclock]
- Fixed MTP​2013-04-09 | v1.31 [733 GPU overclock] / [No GPU overclock]
- Forgot to include Front End Delay code last time
- Smarter CPU usage; assign more work to only 1 core when at lower frequencies
- Ability to change memory and internal voltages
- Boot a device from storage
- WiFi driver updates
- Other driver updates
- Updated to Linux 3.0.72
- Compiled with -O3
- Added support for Android zRAM (settings are in I/O tab of STweaks)
- Updated STweaks
- Started building optional non-GPU overclocked versions for those who don't want it
- Many, many small additions, such as better entropy (see commits for individual credits)​2013-04-03 | v1.20 [733 GPU overclock only]
- Added support for STweaks​2013-04-02 | v1.12 [733 GPU overclock only]
- Original​
​.
VII. SourceSource for Plasma kernel can be found on my github.​

FAQ:
Q: I have no earpiece volume!
Be sure to choose Voodoo Sound or Sound Controls on the Audio tab of STweaks, then reboot.​Q: I can stably run this kernel. How can I use the screen-off settings so I can save battery?
You will have to intentionally crash your system to find your lowest value, and should definitely make a nandroid first. Then be sure to turn off dynamic fsync on the bottom of the I/O tab of STweaks, as this being enabled could cause data loss from a crash. When you are done with that, the first thing will be to lower the PM Lock Frequency. Try 600MHz, press Apply, then put your device to sleep, give it a few seconds, and see if it wakes. Be sure it's going into deep sleep! If it wakes up instantly, it wasn't in deep sleep. After booting, things like mediascanner can take minutes to finish and release their partial wakelocks. If you are sure it went into deep sleep, repeat with a lower frequency until you cannot wake. Pull the battery and reboot. Once it boots up, go into STweaks and set PM Lock Frequency to the last stable frequency. You must do this before the screen goes off, or else it'll crash again when it enters deep sleep!
Now, once you are sure of your stable PM frequency, move on to the next step. Set CPU Screen-Off Max Frequency to 200MHz. Use your device for a few minutes or hours or whatever. If you find music skips too much, or calls are slow to wake up the phone, set this to 300MHz, but now be prepared for a possible SOD if your device cannot handle scaling that low. If you experience one, leave this setting at 300MHz, and enable "Keep sleep max frequency fixed" and set CPU Screen-Off Fixed Max Frequency to 200MHz. If your phone was slow to wake at 200MHz before, try setting this to 300MHz.
Err, a bit of a vestigial tail here...don't forget to set Screen-Off Frequency For Responsiveness (it's higher up in the PegasusQ Scaling tab) to whatever your lowest screen-off frequency is. It isn't needed anymore and I should have taken it out probably. Like its waking counterpart, it is a threshold below which aggressive upscaling is used. Basically, it's the frequency the CPU will want to hover at, in this case, while the screen is off.​Q: Explain the PegasusQ screen-off settings.
CPU Screen-Off Max Frequency - This becomes the effective policy max as soon as you press the power button. Setting this too low may cause slow waking, or choppy music. Ideally this is just like normally setting the max policy; i.e. the governor will try to get frequencies as low as possible without going over this. This means if you get skips in your music at 200MHz, you can set this to 300MHz and the governor will be able to grab that extra power if it needs it. The problem is, some devices get finicky when they're bouncing around between sub-PM Lock frequencies and will crash. That's where the Fixed Sleep Frequency setting comes in. Read on.
Up Threshold While Screen-Off - This becomes the effective Up Threshold value as soon as you press the power button. Setting this higher will make the CPU more reluctant to scale higher (go faster).
PM Lock Frequency - This typically hardcoded value normally overrides the governor to throttle the CPU to 800MHz every time the system itself is unsuspended. This means it happens thousands of times a day, and can significantly add up after a few hours. I found different devices could handle different frequencies, so I made this is adjustable and added an interface to lulzactiveq and zzmoove. 500MHz works very stably for me.
After Boot Delay - Gives your device a grace period after booting during which none of the screen-off policies will be enforced so your start up tasks can be completed quickly.
Enable Fixed Sleep Frequency - This is where things get sorta confusing. If your device can't scale while sleeping, most likely it will be able to tolerate just sticking to one low frequency. But this has a downside...you disable the scaling logic of the governor, so you either have to suffer degraded screen-off performance (skips in your music) with a battery-saving frequency, or set this higher, but then that means you'll be pegging this higher frequency now even though you just needed it occasionally. But yay, I had an idea to put a one-way toggle in there. Read on.
CPU Screen-Off Fixed Max Sleep Frequency - So here's the thing. All devices can handle low scaling just fine, as long the screen is merely off (e.g. listening to music, etc). Once the system falls into deep sleep, that's when stability issues arise. So I had an idea... When you play music, you usually interact with the screen then turn it off, but it never actually goes into deep sleep until it's done playing. So I made it so the above Screen-Off Max Frequency will be used, including scaling, until deep sleep is called for. Then from that point on it will become fixed to this setting's frequency until you turn the screen back on, then the toggle gets reset.
v1.60 Release Notes
Control your panel refresh frequency - This is inspired by and based on AndreiLux's commits last year. Samsung includes a driver called "lcdfreq" that allows for scaling of panel refresh frequency to save power. It toggles between two states: limited and unlimited. Not all devices actively use this feature in stock builds, but it is possible to enable nonetheless. When in limited mode the panel's refresh rate is reduced from 60Hz (58 actual) to 40Hz (41 actual). I went a step further and made it so the limited mode's panel divider can be set manually (25, 27, 29, 31, 34, 37, 41, 45, 50, 60 fps). I also made it so the limited mode can now be forced, effectively allowing you to adjust the default refresh rate of your panel to save battery. Not everyone needs/wants 60fps. How much battery will this save? I don't know yet, but if you want to find out, the option is on the Screen tab of STweaks. Be sure to check the force checkbox. Very low rates will introduce flickering to some eyes (remember, this is a refresh rate being adjusted, not just fps).
Lcdfreq in PegasusQ - Note: This is irrelevant if you have decided to lock your refresh rate as described above. AndreiLux implemented this last year, and I modified it a bit and added more tunables. When enabled, PegasusQ will try to control the state of lcdfreq based on CPU load. Some of you may know AndreiLux abandoned this due to problems with flickering, but I have taken a different approach. His goal was to provide 60Hz as quickly as possible, which ended up frequently alternating between the two states. I'm aiming for the opposite - to stick with limited as long as possible and only boost it during heavy use (like a game). When bounced around between limited and unlimited too rapidly, there can be visible flickering and tearing, and different frequencies seem to slightly affect the color balance, which makes it even more noticeable. Quite possibly why Samsung doesn't use this on Note 2's.
lcdfreq_kick_in_down_delay - When PegasusQ decides it wants to call for the panel to be kicked down (into limited mode) it will have to ask this many times before actually doing it.
lcdfreq_kick_in_up_delay - When PegasusQ decides it wants to call for the panel to be boosted (into unlimited mode) it will have to ask this many times before actually doing it.
lcdfreq_kick_in_freq - Before PegasusQ will consider limiting the refresh rate, the CPU must be running at this frequency or below.
Boost lcdfreq on touch - Immediately boosts to the unlimited state, regardless of what PegasusQ calls for. A commit by AndreiLux. At some point I may add to this to make it time based (i.e. hold the boost for x amount of seconds after a touch).
Control the touchy backlight - On the Screen tab of STweaks. For ROMs that don't provide this support natively, otherwise it may be unreliable.
v1.65 Release Notes
Control your GPU - Over/underclock your GPU! Over/undervolt your GPU, too! Settings explained on the GPU tab of STweaks. Support for frequency, voltage, up/down threshold and GPU governor sampling rate.
Lock/Limit your GPU - You can lock your GPU to a specific step, or limit it to a definable maximum number of steps (e.g. 2 or 3)
Control S-Pen booster - Control/disable the S-Pen CPU booster. Stock is 800MHz, but I find that overkill.
S-Pen X,Y Axis Offset - For some reason Wacom sets this to like 30,30 depending on handedness. I have no idea why, I prefer 0,0. For most users I recommend checking the box on the S-Pen tab in STweaks and leaving the sliders at 0,0.
S-Pen Box Filter - Depending upon what you use your S-Pen for, this makes it much easier to draw shapes, but harder to do finer things, like writing. Think of it as "snap to grid".
Gestures! - Be sure to scroll down to the FAQ section to read how to use them.
Q: How do gestures work?
Flash the gesture pack and reboot. This places the action and handler scripts in /etc/init.d to be run on boot. The available gestures are listed on the Gestures tab of STweaks. You may customize the scripts, but be warned that flashing the zip again will overwrite them.
Some gestures will require you to hold down a touchkey while performing them. Be sure to have a Touchkey Modifier Delay set in STweaks (Screen tab). 100-200ms works well. Now any time you touch and hold a touchkey and then touch the screen within the delay you just set, you will activate gesture-only mode, during which the touchscreen will no longer send touch events to the operating system, only the gesture engine. This means you won't get any bleed through of gesture draws into the foreground app. It's also a safety of sorts, to prevent critical gestures from being accidentally triggered. The downside is, you can't have your cake and eat it...well, not without some delay at least. If the touchkey modifier was simply piggybacked onto the touchkey driver that would be nice, but it would also mean every time you used it, it would also report the touchkey (Menu/Back) event. Or, if you blocked it always, well then obviously your touchkeys wouldn't work anymore. So a compromise is using a very short delay, and after that delay is up, the touchkey driver checks to see if the screen has been touched and the touchkey is still down. If it has been touched, then gesture-only mode is set in the touchscreen driver until all fingers are up. If the screen has NOT been touched after the delay, then the touchkey driver assumes it's just a normal touchkey press and reports it like normal. This may seem like an insanely small delay, but it's meant for you to touch the touchkey and start drawing with another finger *simultaneously*.
tl;dr: Flash the gesture pack, go to the Screen tab and set the Touchkey Modifier Delay to 150ms or so, then apply it. Now test it. First swipe from near the bottom-left corner, up towards the middle-right side. Nothing should happen. Now repeat, this time putting a finger down on the touchkey and holding, while *at the same time* starting to drawing this simple gesture. Aim to have both fingertips touch down at the same time. If it goes well, the virtual power key will be pressed and it will go into suspend. If you have trouble, increase the delay until you get more practice. Eventually you'll be able to do this gesture one-handed by touching the touchkey with the side of your thumb, and sliding/flicking your index or middle finger outward in an arc.​.
Useful Apps (no affiliation):
BetterBatteryStats XDA / Play
Awesome tool that lets you see both kernel and partial wakelocks, as well as the average percent battery drain.​CPU Spy XDA / Play
Provides a GUI to CPU time-in-state data.​Micro CPU Monitor Play
One of my favorite apps ever, this puts a very small 1px bar across the top of the screen for each core. It can be set to come from left or right, the background can be set transparent, and the bar thickness and color are adjustable. Very useful for quickly (and discretely) noticing abnormally high CPU usage.​top Play
Provides a GUI to the linux command 'top'. Provides a very reliable way to see what processes are using the most CPU time.​System Monitor Play
This app makes monitoring CPU history easy, and makes it especially easy to see the effects of hotplugging tweaks because of the way it clearly displays the state of each core.​.
Notes:
How to use the mdnie-control interface:
AndreiLux and Slimer777 have gone to great lengths to create an extremely accurate internal color profile using a spectrophotometer. The color accuracy is terrific. Most computers and tech use a very unnaturally cool color temperature (blue tint to white), so many people are taken by surprise when they see how yellow reality actually is. You need some time to get used to the new colors, but if you are still not pleased with the result, AndreiLux has setup MANY options for you to tweak in STweaks. Personally, I recommend increasing the chroma saturation weight.
Settings can easily be configured in the STweak app now. Download it from the Play Store.​
A bit about body bias:
To summarize this feature: When we traditionally change voltages (SetCPU, Performance Control, etc), we are changing the gate voltage of the transistors. This can be a difficult concept to grasp, so here's a super-simple analogy to help: Imagine a light switch instead of a transistor. You reach your finger out to flick it. The force your finger applies would be analogous to the gate voltage. However transistors also have a body voltage, which can be thought of as the resistance behind the switch. By applying a positive difference between the gate and body, (which usually, but not always, equates to reducing the body voltage) we can make the proverbial switch "looser" so it's easier to flip, but now that it's looser, it's starting to leak a small amount of current as a result. So why would we want to do this if it will be leaking more? Because now that the switch is looser, we'll hopefully need less gate voltage (aka finger pressure in the analogy) which would save more power than was lost with that leakage. Or, for someone overclocking instead of undervolting, the "loose" switch will be easier to flip, and you may achieve an overclock not possible by merely ramping up the gate voltage (brute force) in your voltage control app of choice. Basically like the old saying "two steps forward, one step back" - we get something good, but have to sacrifice a little power lost through leakage. But how about the opposite scenario? What if in the analogy you have a really strong finger? Then you're leaking power for no reason because you don't need a "loose" switch. So, we can take advantage of that fitness and tighten it up by applying a negative body bias (also called a Reverse Body Bias, or RBB). This will make the transistor harder to switch, but plug up the leak and therefore increase power efficiency.
Ok, so why does all this exist? Why not just have an enormous negative bias (RBB) from the factory and save all that power lost through leakage? Because not all chips are equal, and not all transistors on the same chip are even equal. Temperature, manufacturing techniques, a few atoms of contamination, etc can make the chip less "fit" and unable to switch as easily as others. So how do they help these weakling transistors from getting the entire chip sent to the factory garbage can? Well, on one hand the gate voltage can be increased, but that is a last resort since it would waste too much power. Before it comes to that, they get a crutch in the form of a positive body bias (also called a Forward Body Bias, or FBB), which hopefully you'll remember was the subject of the first scenario above. And remember what that does? It makes them easier to switch, but at the cost of slightly decreased power efficiency. This offers better power savings when compared to increasing the gate voltage.
Samsung knows all this, and bins their chips according the ASV level, which can be thought of as the "quality" of the chip. The higher the ASV number, the better the chip, and the less power it needs to do its job. At the factory they mix increased gate voltages with varying body voltages to end up with a table of stock body biases. Long story short, this is how they deal with less-than-perfect chips. It's a lottery for the buyer. But since their values aren't tailored to your chip - the hope is that maybe you can scrape by with a bit less power than Samsung thought a chip of that grade could. So what AndreiLux has done is implemented new scaling logic/control code that lets you adjust the body voltage, and thus the body bias. Thanks to him, we now have another tool to help us squeeze a little bit more power out of our chips.
Calculating your body bias is incredibly simple: bodybias = gatevoltage - bodyvoltage. If you know the voltage of a given frequency, you can calculate your body bias by taking the gate voltage (what it says for that frequency in your usual voltage adjustment app) and then subtracting the value of the slice that corresponds to the range the example frequency was in on the ABB tab of STweaks. This can get tricky, because people forget that "body bias" is a difference between two values. If you start off with a stock negative body bias, that is to say that your body voltage is higher than your gate voltage, increasing your body voltage will actually be increasing your bias and you'll be needlessly wasting more power. However if you start off with a positive stock body bias, adding to the body voltage will actually be decreasing your bias since it will be bringing you closer to the gate voltage.​

Re: [Kernel][AOSP] Matrix kernel
Nice work. For the first time I
am first after the OP.
Sent from my SPH-L900 using xda app-developers app

Re: [Kernel][AOSP] Matrix kernel
Thanks!
Sent from my SPH-L900 using xda premium

Re: [Kernel][AOSP] Matrix kernel
About to flash!
Sent from my SPH-L900 using Tapatalk 2

Working smoothly on current cm nightly with set CPU..so far at least

Re: [Kernel][AOSP] Matrix kernel
Thanks for this :thumbup:
-TeaM VeNuM Like A Boss :flipoff2:
-SoA: Son's of Android™

Re: [Kernel][AOSP] Matrix kernel
This requires immediate flashing.
Sent from my SPH-L900 using Tapatalk 2

Re: [Kernel][AOSP] Matrix kernel
can you use stweaks with this kernel?
Sent from my SPH-L900 using Xparent Blue Tapatalk 2

Wonderful effort = Great work! Thanks :good:

Re: [Kernel][AOSP] Matrix kernel
Thank you for your hard work, just flashed! So far so good! :thumbup:
Sent from my SCH-l900 using xda premium

raw2000j said:
can you use stweaks with this kernel?
Click to expand...
Click to collapse
Yay, I figured it out. Going on 44 hours without a wink of sleep, but at least customized STweaks are on their way!

Thank you so much!!! I was dieing for a Perseus Kernel implementation for AOSP. Thank you very much ffolkes and AndreiLux for all of the hard work you guys have been putting into making our phones the best they can be!
I'm currently running this kernel with Carbon 1.6 and my phone just flies!!!

Re: [Kernel][AOSP][1.20|April 3rd] Matrix kernel
No problems so far on 50mhz and the kernel seems to be using way less battery. Colors are kinda washed out though. Would like to see trinity colors :thumbup:
Sent from my SPH-L900 using Tapatalk 2

Flashed this earlier today. Will give my findings in a day or so.

Re: [Kernel][AOSP][1.20|April 3rd] Matrix kernel
Nice. This kernel works great. Battery last forever.
Sent from my SPH-L900 using Tapatalk 2

I've only noticed 1 problem so far... Wifi hotspot no longer works on aokp. Anybody else have the same problem on other roms?

Re: [Kernel][AOSP][1.20|April 3rd] Matrix kernel
Rooster85 said:
No problems so far on 50mhz and the kernel seems to be using way less battery. Colors are kinda washed out though. Would like to see trinity colors :thumbup:
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Trinity colors would be awesome but just tune them w/s-tweaks..
@op Tks! So far so good, will throw stats up in a few days.
Edit
Sent from my SCH-l900 using Tapatalk 2

Re: [Kernel][AOSP][1.20|April 3rd] Matrix kernel
flashback7 said:
Trinity colors would be awesome but just tune them w/s-tweaks..
@op Tks! So far so good, will throw stats up in a few days.
Edit
Sent from my SCH-l900 using Tapatalk 2
Click to expand...
Click to collapse
Any idea of how to match them?
Sent from my SPH-L900 using Tapatalk 2

Re: [Kernel][AOSP][1.20|April 3rd] Matrix kernel
From today...
Sent from my SPH-L900 using Tapatalk 2

[Q] Slide2Wake?

Is there any kernel or standalone app that I should flash to get Slide2Wake (Touch Control like on Nexus 4) for Note 2?
I really miss it from nexus 4, it saves the home/power button.
Thanks

ibr4him said:
Is there any kernel or standalone app that I should flash to get Slide2Wake (Touch Control like on Nexus 4) for Note 2?
I really miss it from nexus 4, it saves the home/power button.
Thanks
Click to expand...
Click to collapse
This Kernel has it supports both Sammy and AOSP
[Kernel] Devil - Linux 3.0.83 - Aosp&Sammy - Dualboot - no ExFAT - 27/06
Features (changes compared to Perseus):
- updated Linux Kernel base to 3.0.83
- DevilQ cpu governor (default)
- block updated from Linux 3.3 (better i/o performance)
- row i/o scheduler updated from Linux 3.4
- fiops v2 i/o scheduler
- working for Aosp and Sammy at once (Big thx to Gokhanmoral for making this possible)
- Portet Ezekeel's Touchwake Feature (from nexus s)
- Oc up to 2 Ghz
- Backport from Linux 3.5 smp driver parts
- Cm Wifi driver (from D2 Linux 3.4 kernel)
- possibility to set high/low power mode for wifi when screen is off
- LulzactiveQ cpu governor (from siyahkernel, thx again to Gokhanmoral)
- Hotplug Cpu Governor
- Proportional Rate Reduction for TCP
http://kernelnewbies.org/Linux_3.2#h...7963f165302b6e
- improve memcopy/memmove
- Using Voodoo Sound
- mdnie: toggling mdnie negative effect with home button (Gokhanmoral)
- Reverted LED Control

Thanks, but touchwake is different than slide2wake.

ibr4him said:
Thanks, but touchwake is different than slide2wake.
Click to expand...
Click to collapse
you just need to swipe the screen from horizontal or Vertical it will wake up your device
if still different can you explain or a sample video on youtube so i can check .

TouchWake:
This mod allow user to wake the device by touching the screen without pressing the power/lock button. You can specify how long the screen will wait for touch before its fully locked. (i.e need power button to unlock it)
Click to expand...
Click to collapse
Slide2Wake:
It enables a quick sleep mode via a swipe across the capacitive keys from right to left, and an easy unlock from wake via a swipe from left to right. Thus you can turn your phone on and off without ever actually touching the screen.
Click to expand...
Click to collapse
Difference:
With TouchWake there is a specific timeout within which you can touch ANYWHERE to unlock, whereas Slide2Wake has no timeout and you have to slide (less accidental wakeups) to unlock.

ibr4him said:
TouchWake:
Slide2Wake:
Difference:
With TouchWake there is a specific timeout within which you can touch ANYWHERE to unlock, whereas Slide2Wake has no timeout and you have to slide (less accidental wakeups) to unlock.
Click to expand...
Click to collapse
ok i got it as if now we only have touch to wake may be near in future this should be developed.

[KERNEL] ElementalX N5 8.14 (Nougat) 9.02 (Oreo)

ElementalX Kernel
for Nexus 5 (hammerhead)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
Easy installation and setup with AROMA installer
Best balance of performance and battery life
Advanced color control
USB fastcharge (optional)
Sweep2sleep (optional)
Sweep2wake and doubletap2wake (optional)
Disable wake functions with timeout or power button
Wake Gestures app support
MultiROM support
Disable fsync (optional)
Sound control
Cooler color preset (optional)
backlight dimmer (optional)
Underclock or overclock CPU
L2 and bus overclocking options
Choose automatic minimum voltage
kernel-based thermal control
GPU overclocking options
voltage control
NTFS read/write and exFAT support
init.d support
Charge light support (enabled by some ROMs)
No forceencrypt
Google+ Community
Installation
1. Flash in recovery
For maximum compatibility with all ROMs, ElementalX uses your existing ramdisk.
Do NOT flash this over other custom kernels!
You should only flash ElementalX over the kernel that came with your ROM!!!
Download
Android 8.1.0 (Oreo) (Might work, might not, who knows...)
ElementalX-N5-9.02
Android 7.1.1 (Nougat, but also works on Marshmallow)
ElementalX-N5-8.14
Android 6.0.1 (Marshmallow)
ElementalX-N5-6.27
Note: 6.25 is for ROMs with July security patches or later! Please use 6.17 if WiFi doesn't work
App to customize Wake Gestures:
http://elementalx.org/wake-gestures/
Source
https://github.com/flar2/ElementalX-N5
_____________________________________
XDA:DevDB Information
ElementalX Kernel, Kernel for the Google Nexus 5
Contributors
flar2
Source Code: https://github.com/flar2/ElementalX-N5
Kernel Special Features:
Version Information
Status: Stable
Created 2013-11-09
Last Updated 2018-03-03

Notes
REVIEWS
NOTES
ElementalX Configuration File
Your choices in the Aroma installer are used to build a configuration file. The config file is located at /etc/elementalx.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere!)
If settings are not sticking:[*]Make sure you have busybox installed correctly and updated to the latest version[*]Make sure the file permissions for /etc/init.d/99elementalx are set to execute. [*]Check to see if any /etc/init.d scripts or apps (such as Kernel Tuner or TricksterMod) are interfering with your settings.
ElementalX Log File
Every boot, a log file is created at /data/local/tmp/elementalx-kernel.log. This file shows the date and time and all settings that have been applied. Use this to verify and troubleshoot configuration options.
ElementalX Governor
The ElementalX CPU governor has been specifically designed and tuned to get the best balance between battery life and performance. By default, it is more conservative than Ondemand. During routine usage, the CPU frequency does not ramp up very often. If gboost is enabled, during gaming or any other graphics intensive situation, the CPU frequencies boost much easier in order to maintain maximum performance. There is also a built in input boost. There are several tunables specific to the governor:
input_event_min_freq: takes four values separated by comma. These are the input boost frequencies for cores 0, 1, 2, and 3 (default 1728000, 1267200, 1267200, 1267200)
input_event_timeout: this is the length of time in milliseconds that the input boost will be active (default 500). Setting this to 0 disables input boosting.
ui_sampling_rate: when you touch the screen, the sampling rate changes temporarily to whatever you set here (default 15000)
two_phase_frequency: this sets the max frequency for moderate loads. Accepts four frequency values separated by comma, for cores 0, 1, 2, and 3. (default 1728000, 1728000, 1728000, 1728000)
How does it work? It's basically a multiphase ondemand governor.
The basic governor is very conservative for most phone activities, spending most of its time at 1267MHz. If there is graphics load, we switch to a two phase ondemand. The first phase runs with a max freq of 1728MHz (default). If the load increases, it goes to max frequency (default is 2265MHz) and the minimum frequency changes to 1267200 (I will probably make this tunable)
The input boost does a couple things. First, it lowers the sampling rate for the timeout duration to make the governor more responsive. Second, it boosts the frequency of any online cores. You can disable this by setting input_event_timeout to 0.
If you want to experiment, delete /system/lib/hw/power.msm8974.so and set the input_event_timeout to about 1000. But I recommend leaving it alone for optimal smoothness.
Faux Clock/TricksterMod/Kernel Tuner/etc
You don't need these apps because the ElementalX installer sets everything up automatically, but if you want to check or change settings, you can use these apps. Just be aware that some of them (e.g. Kernel Tuner) are set by default to apply settings on boot, which can interfere with the settings you chose in the ElementalX installer.
Overclocking
Overclocking (or underclocking) is optional. The installer lets you choose the maximum frequency. You can set the maximum frequency individually for each CPU core in the installer. Whatever frequencies you chose in the installer will be set at boot for each CPU. Not all devices can handle overclocking. I don't recommend overclocking, this device is fast enough. If you overclock, the CPU frequency will likely be throttled due to heat. I recommend the stock frequencies, as this device is plenty fast.
CPU voltages
The installer allows you to choose from several undervolting options. These automatically undervolt the lowest frequency (300MHz) where the CPU spends most of its time. The voltages for other frequencies are assigned based on the PVS bin of your phone. CPU voltages are fully customisable with apps such Kernel Tuner or Trickster Mod, but I recommend leaving these other voltages as-is unless you are prepared to do a lot of testing. Be careful, lowering voltages can cause instability. Generally, having reboots while the phone is asleep or other weird problems is a sign that your minimum voltage is too low.
GPU Governor
The default GPU govenror is ondemand. It works well and is recommended for best balance between performance and batter life. The simple governor is also available, but ramps up the GPU frequency much quicker than ondemand, so may impact battery life. The governor can be set in /etc/elementalx.conf
fsync
fsync can be disabled if you're looking for the last ounce of performance. I recommend leaving it enabled as there is a slight risk of data loss if your phone shuts off unexpectedly before filesystems are synced.
Max screen off frequency
The default max screen off frequency is 1190MHz, which is a good balance between limiting the voltage/frequency and the time required to complete tasks while the screen is off. This can be changed manually at /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
Installing a new ROM
If you install a new ROM, it will probably replace this with the stock kernel and will definitely overwrite /etc/init.d/99elementalx and /etc/elementalx.conf so you will lose your settings and certain features. So always reinstall the kernel after installing a ROM.
NTFS and exFAT support
This is for anyone who wants to use OTG to connect a USB stick or portable harddrive formatted with Microsoft's NTFS or exFAT filesystems. You will need Stickmount or a similar app.
F2FS support
F2FS support is built into the kernel, however, you will need to have an F2FS compatible kernel installed before you install ElementalX to get all the proper ramdisk stuff.
Wake Gestures
This is a new feature similar to the Motion Launch Gestures on the HTC One m8. Requires this app:http://elementalx.org/wake-gestures/
Set /sys/android_touch/wake_gestures to 1 to enable input events for wake gesture actions. Set to 0 to use traditional sweep2wake or doubletap2wake (wakes up the phone and turns on the screen only).
Note that if you enable wake_gestures, nothing will happen if you don't install the Wake Gesture Xposed module.
Sweep2wake
Sweep2wake allows you to turn on your phone by swiping your finger across the screen. There are four sweep actions that will work
Gesture........Value
Sweep right......1
Sweep left........2
Sweep up.........4
Sweep down....8
Add up the values for each gesture you want to enable and put the total in /sys/android_touch/sweep2wake. For example, to enable all gestures, the value is 15 (1+2+4+8). To enable sweep right, sweep left and sweep up, the value is 7 (1+2+4)
/sys/android_touch/sweep2wake
Doubletap2wake
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping anywhere on the screen. This causes significant battery drain. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/doubletap2wake
0 = disabled
1 = enabled (bottom of screen only)
2 = enabled (full screen)
Vibration Strength
Haptic feedback can be enabled for the wake gestures in /sys/android_touch/vib_strength. This setting takes a number between 0 and 90. Default is 20. Setting this to 0 disables haptic feedback for gestures.
S2W/DT2W power key toggle
If enabled, turning the screen off with the power button disables s2w and dt2w to save battery (since s2w/dt2w cause significant battery drain). When you turn the screen back on, s2w and dt2w return to their previous settings. If the screen times out, s2w/dt2w are not disabled this is only if you use the power button to turn it off. You can edit /etc/elementalx.conf to change the setting on boot.
S2W/DT2W Timeout
Doubletap2wake and sweep2wake can be automatically disabled after a certain number of minutes. I give a few choices between 5 and 120 minutes in the installer. Default is 30 minutes. You can put in whatever you want in /etc/elementalx.conf.
When the screen is turned on, the timeout is canceled and will start again next time you turn the screen off. This means that if you have your screen set to come on for incoming messages or notifications, the timeout will start over again.
If you also enabled the power button to toggle s2w/dt2w, there is no timeout when you use the power button, the wake functions are immediately disabled (same as before).
You can edit /etc/elementalx.conf to change the setting on boot.
Sweep2Sleep
Sweep2Sleep allows you to put the device to sleep by sweeping your finger across the navigation bar area. Unlike Sweep2wake, this does not cause any battery drain. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/sweep2sleep
0 = disabled
1 = sweep right
2 = sweep left
3 = sweep left or right
Color preset
There are two color presets: stock and slightly cooler. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/module/mdss_dsi/parameters/color_preset
0 = stock color
1 = slightly cooler color
Backlight dimmer
Backlight dimmer allows you to adjust the LCD screen brightness lower than is possible with stock. Be careful, you can lower the brightness so much you can barely see it. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/module/lm3630_bl/parameters/backlight_dimmer
0 = disabled
1 = enabled
USB fastcharge
USB fastcharge is optional. This will allow you to charge at a faster rate when connected to a USB port. The default limit for USB ports is 500ma, this increases it to 900ma. Be sure that the computer/laptop/whatever you are plugged into can handle it. Some will automatically cap it at 500ma. Please note that this does not force AC charge mode like previous implementations of force fastcharge. Your battery setting will still say USB mode. You can edit /etc/elementalx.conf to change the setting on boot.

Changelog
Sep29, 2014 - ElementalX-N5-1.10
-revert i2c update
-clean up voltage control
-ext4 speedup
Sep15, 2014 - ElementalX-N5-1.09
-update to fauxsound 3.6
-i2c update
-update audio subsystem (cm version only)
Sep10, 2014 - ElementalX-N5-1.08
-update msm-sleeper
-fix installer
Sep 6, 2014 - ElementalX-N5-1.07
-fix permissions for vib
Sep 5, 2014 - ElementalX-N5-1.06
-fix permissions for vib and color settings
-update msm-sleeper
-fix flashlight permissions
-add support for USB Keyboard app
Aug 25, 2014 - ElementalX-N5-1.05
-fix long timeouts in wake_timeout
-support 3G USB dongles
-lower i2c clockrate
Aug 8, 2014 - ElementalX-N5-1.04
-latest updates to fauxsound
-support Logitech Unifying Receiver
-NFS support
Aug 3, 2014 - ElementalX-N5-1.03
-security updates and fixes
-ability to use proprietary chargers
July 2, 2014 - ElementalX-N5-1.02
-fix touchboost not enabled on recent builds (CM/CAF version)
June 29, 2014 - ElementalX-N5-1.01
-CAF updates to audio subsystem (CM/CAF version)
June 19, 2014 - ElementalX-N5-1.00
-rebase
-all features same as before
June 10, 2014 - ElementalX-N5-0.44
-update installer
-various tweaks and optimizations
-fix slimport irq not enabled
June 4, 2014 - ElementalX-N5-0.43
-update with Android 4.4.3 kernel source
-fix vibration intensity
June 3, 2014 - ElementalX-N5-0.42
-faster boot up
-revert enable proprietary charger
June 1, 2014 - ElementalX-N5-0.41
-new wake timeout method
-various fixes and optimizations
-stereo call recording support (untested)
-update installer
May 25, 2014 - ElementalX-N5-0.40
-fix installer
-adjust vertical sweep length
-adjust doubletap timeout
-update slimbus oc (@poondog/@zeroinfinity)
May 25, 2014 - ElementalX-N5-0.39
-bidirectional sweep2sleep
-omnidirectional sweep2wake
-wake gestures interface (requires xposed module)
-optional haptic feedback for gestures
-updated installer
-option to use stock ondemand governor
-build with Linaro GCC 4.9.1 toolchain (@Christopher83)
-other fixes and optimizations
Apr 25, 2014 - ElementalX-N5-0.38
-adjust hardfloat compile option
Apr 21, 2014 - ElementalX-N5-0.37
-update F2FS support
Apr 5, 2014 - ElementalX-N5-0.36
-revert sched tweaks
Apr 2, 2014 - ElementalX-N5-0.35
-update backlight_dimmer
-rgb color control (savoca)
-a few fixes and optimizations
Mar 17, 2014 - ElementalX-N5-0.34
-fix installer typo
-fix playback of secure video
Mar 16, 2014 - ElementalX-N5-0.33
-add F2FS support
-add wake function timeout option
-add readahead options
-update installer
Mar 4, 2014 - ElementalX-N5-0.32
-many CAF updates and fixes
-rework and cleanup elementalx governor
-ROW is default i/o scheduler again
Feb 27, 2014 - ElementalX-N5-0.31
-s2w/dt2w power button toggle fix
-update backlight dimmer (more gradual steps)
-revert some changes from 0.30
Feb 22, 2014 - ElementalX-N5-0.30
-deadline is default i/o scheduler
-update backlight dimmer (more gradual steps)
-export storage for usb otg
-update installer
-save elementalx.conf to sdcard
-express installer sees all options now
-many optimizations and fixes (see github)
Feb 1, 2014 - ElementalX-N5-0.29
-fix photos taken with flash
Jan 27, 2014 - ElementalX-N5-0.28
-cyanogenmod support
Jan 26, 2014 - ElementalX-N5-0.27
-CAF updates to audio
-update installer
-save elementalx.conf to sdcard
-express installer sees all options now
Jan 21, 2014 - ElementalX-N5-0.26
-improve compatibility with various ROMs
Jan 20, 2014 - ElementalX-N5-0.25
-remove simple GPU gov
-update gamma sysfs interface (credit: myfluxi)
-enable C2 and C3 states
-maintain touchboost in all ROMs
-update Aroma Installer to 2.70RC2
-fix installer cmdline creation
-fix green line on videos
-express installer keeps previous max freq, l2 and uv options
Jan 11, 2014 - ElementalX-N5-0.24
-slight boost to elementalx governor
-small boost to l2/bus for touchboost frequency
-many fixes and optimizations (see github)
-update installer
-add DriveDroid support
Jan 5, 2014 - ElementalX-N5-0.23
-tweak deadline i/o scheduler
-slimbus overclock (credit: poondog)
-implement always on rgb led support (requires rom support)
-i/o scheduler option in installer
-express version
Jan 1, 2014 - ElementalX-N5-0.22
-update installer
-doubletap2wake default is bottom of screen only
-doubletap2wake fullscreen option
-various tweaks and optimizations
Dec 30, 2013 - ElementalX-N5-0.21
-revert some tweaks
-update installer
-cfq is default scheduler
Dec 28, 2013 - ElementalX-N5-0.20
-move elementalx.conf back to /etc
-update installer
-remove async_fsync
-restore enable/disable fsync option
Dec 26, 2013 - ElementalX-N5-0.19.1
-move elementalx.conf to /data/local/elementalx.conf
Dec 26, 2013 - ElementalX-N5-0.19
-adjust doubletap2wake sensitivity and return to full screen
-slight boost to elementalx gov
-return to older backlight dimmer mod
-move /etc/elementalx.conf to /sdcard/elementalx.conf
-option for stock thermal throttling
-update installer
Dec 21, 2013 - ElementalX-N5-0.18
-restrict doubletap to bottom half of screen and make less sensitive
-elementalx is default CPU governor
-add gboost option
-add cooler thermal option
-various tweaks and optimizations
-update installer
ElementalX-N5-0.17
-fix multirom support
-default i/o scheduler is FIOPS
ElementalX-N5-0.16
-replace backlight dimmer option with @showp1984's backlight mod
-add asynchronous fsync from HTC One
-remove fsync options (no longer needed)
-Makefile adjustments
-slight adjustments to elementalx governor
-update gamma control support
-add kexec-hardboot (multirom support)
-update installer
ElementalX-N5-0.15
-experimental elementalx governor
-Makefile adjustments
ElementalX-N5-0.14
-fix cpu frequencies
ElementalX-N5-0.13
-update config
ElementalX-N5-0.12
-update for Android 4.4.1
-various tweaks and optimizations
ElementalX-N5-0.11
-various tweaks and optimizations
-update gamma control interface
ElementalX-N5-0.10
-ramdisk options
-experimental gamma support (@myfluxi and @faux123)
-adjust Makefile optimizations
-adjust mpdecision parameters (slightly less aggressive)
ElementalX-N5-0.9
-prevent touches during phone calls while screen is off and s2w or dt2w are enabled
ElementalX-N5-0.8
-wifi fixes
-faux123 sound fixes
-remove some CPU frequencies
ElementalX-N5-0.7.2
-update installer for greater compatibility with various ROMs
ElementalX-N5-0.7.1
-use existing ramdisk
ElementalX-N5-0.7
-add option for sweep2sleep only
-add option for S2W/DT2W power key toggle
ElementalX-N5-0.6
-add doubletap2wake
ElementalX-N5-0.5
-add color presets
-add sweep2wake (thanks @show-p1984)
-dimmer backlight option
-increase default screen off frequency to 1190MHz
ElementalX-N5-0.4.1
-do not use existing ramdisk
ElementalX-N5-0.4
-add CIFS support
-revert shut down cores while screen off
-remove early_suspend
-max screen off frequency optional
-update installer
-use existing ramdisk
-remove ultra optimization
-add faux123 sound patches
ElementalX-N5-0.3
-max screen off freq 730MHz
-shut down cores while screen off
-use lowest GPU frequency (200MHz)
-restore early_suspend
-simple GPU governor
-overclocking up to 3GHz
ElementalX-N5-0.2
-use Aroma installer
-installer ensures mpdecision and thermal-engine are present
-init.d support
-increase thermal limits
-add CPU optimization levels
-CPU overclock to 2726MHz
-automatic undervolting
-add TCP congestion algorithm options
-add fstrim to init script
-add exfat support
-Input: Send events one packet at a time
-cleanup from other kernels
-wireless bug fixes
ElementalX-N5-0.1
-Makefile optimizations
-optimized AES and SHA1 routines
-undervolting option
-add /dev/frandom
-show pvs number in sysfs
-NTFS r/w support
-optimized AES and SHA1 routines
-add FIOPS and SIO i/o schedulers
-force fastcharge
-lib/int_sqrt.c: optimize square root algorithm
-AIO: Don't plug the I/O queue in do_io_submit()
-voltage control
-add option to enable/disable fsync
-update ARM topology
-add cpu_power driver
-enable loadable kernel module support
-build -O3 with linaro 4.7 toolchain

It is here!!! Love your kernel on Flo!

omg <3
i just wish there were ways to flash boot.img without connecting the device to my computer.
i was in bed and had to get up just to flash this!
i had no doubt that it was worth it!

rootuser11 said:
omg <3
i just wish there were ways to flash boot.img without connecting the device to my computer.
i was in bed and had to get up just to flash this!
i had no doubt that it was worth it!
Click to expand...
Click to collapse
Try flashify from play store
Sent from my Nexus 5 using Tapatalk

Now this will be interesting. Checking out
Sent from my Nexus 5 using Tapatalk

dex2grigg said:
Try flashify from play store
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
<3

I hope to work on a nice installer tonight

nice!! man im sooo happy i got a nexus phone now! love having great kernels to play with thanks flar:good:

Nice to have you here, my One loves your work: )
Sent from a mobile Gadget...

Wohooooo really nice I am happy that your here your kernel for the One is just awesome!
Gesendet von meinem Nexus 5 mit Tapatalk

This awesomeness does not stop.... lol thank you!
Sent from my Nexus 5 using XDA Premium 4 mobile app

I flashed without any hesitation, loved your work on the HTC One! So great to have you here :highfive:

Double tap to wake on the n5 can't wait!!!
Sent from my Nexus 5 using Tapatalk

AWESOME!! I loved the ElementalX kernel on my HTC One!

djkinetic said:
Double tap to wake on the n5 can't wait!!!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i prefer swipe2wake to avoid wake up your phone accidentally when it's still in your pocket :victory:

Excellent news to see this up and running. Was a beauty on my HTC One and should be the same on my Nexus 5.
Sent from my Nexus 5 using xda app-developers app

Ran a quick test of your Kernel with PSX ROM test build for N5.
Very nice
Sent from my Nexus 5 using XDA Premium 4 mobile app

Always used your kernels on the sprint One, glad to see you got a nexus.
Sent from my Nexus 5 using Tapatalk

[FINAL] [KERNEL] [5.0.1/5.0.2/5.1.1] [TW] [24 March] [15.0] VoLTaqe Kernel

Welcome to VoLTaqe Kernel
I dont permit any mirror or dont use any of my idea without permission or unless giving usable credit !
To developers: I dont permit to use my kernel like stock kernel on your roms or any option like aroma installer.
As you know i dont have device so need some testing before release. So i created a group on telegram who intend about this, you can join freely for tests and chats.
https://telegram.me/joinchat/DJI0VgiEbcHZte17B9_3fw
Features:
- Built from Samsung's latest I9500XXUHOL1 Lollipop Kernel Sources
- Linux kernel version update to 3.4.5
- Built with Uber 4.9
- Used my own 1.25.0 busybox
- ExFAT, NTFS, NFS, CIF Support
- Disabled android logger as a default setting
- Cpu Voltaqe Control
- Cpu Underclock
- Cpu Core Number Control
- Gpu Voltaqe Control
- Gpu Overclock
- Gpu min/max Value Control
- Wolfson Sound Control
- Battery Charge Control
- Screen Control
- Led Control
- Touchscreen Control
- Touchkey Control
- Memory Interface Voltaqe Control
- PowerSuspend Driver Control
- Battery Scaling Calibration Option
- Synapse Support
- Init.d Support
- Selinux set to Permissive
- Governors: interactive, userspace, powersave, performance, ondemand, lulzactive, impulse, lazy, tripndroid, preservative, barry_allen, optimax, bluactive, HYPER, ondemanplus, smartassV2, pegasusq, zzmoove, intellimm, darkness, intelliactive, wheatley, smartassH3, nightmare, intellidemand, alucard, asswax, abyssplugv2.
-About governors you can read this : http://ajgupta.github.io/android/2015/01/28/CPU-and-GPU-governors/
- I/O Schedulers: noop, deadline, row, cfq,bfq, fiops, sio, zen.
Many more...
How to Correct Installation:
1 - Disable namemount option on SuperSU app
2 - Place kernel zip to externalsd
3 - Reboot into recovery and flash the zip
4 - Reboot to system
5 - (Optional) Open synapse, click the "understood" button and tweak with your desire.
6- Done.
Download:
Download Latest TOUCHWIZ Version: 15.0 ( Support 5.0.1, 5.0.2, 5.1.1 )
You can control all kernel features with Synapse app. Download from Google Play Store.
If anything going wrong flash stock kernel: www.voltaqe.com/Stock-Kernel.zip
Big Thanks to Who Donate This Project: @turkishforce123,
@ch4qr1 , @zetlaw @turquoise.blue,
@body150165, @avokain, @glennsamuel32, @RememberMe164, @Vurda
You can buy me some beer for a night hard work partner
Thanks to:
@AndreiLux, @faux123, @senzatiOn- (perfect banners)
VoLTaqe-Kernel-Source.tar.gz: *** MOD EDIT: dead link ***
XDA:DevDB Information
VoLTaqe, Kernel for the Samsung Galaxy S 4
Contributors
VoLTaqe
Kernel Special Features:
Version Information
Status: Stable
Created 2015-05-12
Last Updated 2016-01-01

Changelog 15.0
- Logger enabled by default
- Bug fixes and improvement
Changelog 14.9
- Fixed last busybox problem which has faulty busybox on roms
- Correct links on rom files
Changelog 14.8
- Busybox updated to my own 1.25.0
- Fixed all busybox problems
- Fixed crontab not starting problem
- Updated rom busybox too
- Fixed some mismatch problem on backup/restore
Changelog 14.7
- Fixed restoring profile according to testers
- Attempt to fix some fcs appearing on 14.6
- Performance tweaks
Changelog 14.6
- Fixed battery profile not showing on first boot
- Attempt to fix load battery profile (need reports)
- Reduced log level for decrease kernel load
Changelog 14.5
- Added clever backup/restore function
- Added battery profile
- Fixed leak and added lowmemorykiller tab
- Better multitasking tweaks
- Dm-crypt running high priority workqueue for better io results
- Dm-verity running high priority workqueue for better io results
- Decrease mmc load for better io performance
Changelog 14.4
- Reworked from OL1 sources
- All features adapted except cpu overclock and governors ( governors will add later )
- Fixed freeze right after boot
- Fixed memory leak on rom systemui.apk ( Which sticking on ram, no need for it and it releasing nearly 95mb ram on long term)
- Fixed random reboot when heating too much
- Increase thermal values 5C more
- Clear page active before releasing pages
- Reduced time spent in congestion_wait on kswapd
- Improved boot time on Pit
- Dont waiting anymore for congestion when mem is high
- Account for highmem during kswapd reclaim on lowmemorykiller
- Added lmk parameters tunning codes
- Lowmemorykiller kill apps one by one
- Fix the too small buffer for dname
- Allowing sleep kswapd if it has been running too long
- Fixed loggers on off states
- Reduced entropy values balance for battery and performance
- HID drivers disabled
- Added exynos core control
Changelog 14.3
- Much relief lmk config
- Lmk will clear ram after 30 seconds after claim high limit
Changelog 14.2
- Rearranged ALL synapse scripts
- Continuesly reboot problem on some ported roms fixed (according to testers)
- Added cortexbrain
- Added ability to disconnect wifi when screen off (disabled by default)
- Added ability to kill mediaserver for battery save when screen off (enabled by default)
- Cronjobs improvement
- Improved a7 overclock
- Disabled some debugs for lighter kernel
- Added screen brightness level to synapse
- Disabled kernel panic which causing random reboot sometimes
- Battery informations added to battery tab about charging
- Flasher-script changed and added ability to clean synapse data every flash
- Fixed double led enable option
- Lmk option deleted (will add later)
- Fixed synapse boot canceled problem on every boot
- Added swap state information to synapse
- Added modules section which kernel dont has by default ( read description on synapse )
- Attempt to increase performance
- Fixed lag on ondemand governor
- Many more i dont remember
Changelog 14.1
- Interactive and conservative governors fixed freezing when select on synapse
- Deleted abysplug hotplug governor because of no more compatible
- Userspace hotplug control deleted
- Kernelspace late wake problem fixed
- Updated hotplug main codes from 3.10
- Implement park/unpark facility on kthread
- Allocate idle thread for each possible cpu during boot
- Optimize calls to smp_processor_id() in idle_threads_init
- Fix comment mismatch over idle_threads_init
- Provide infrastructure for percpu hotplug threads
- Fix UP bug in smpboot hotplug code
- Allow selfparking per cpu threads
- Store task reference in a separate per cpu variable
- Use smpboot threads on stop_machine
- Mark per cpu stopper enabled early
- Prevent unpark race which puts threads on the wrong cpu
- Use hotplug thread infrastructure on softirq
- Yield simpler on rcu
- Use smp_hotplug_thread facility for RCUs per-CPU kthread on rcu
Changelog 14.0
- Drains fixed
- Freezes fixed
- Added min gpu value control
- Added clock infos hotplug sections too like cpufreq
- Cron activities improved
- Backup/Restore tab deleted ( really bored sorry )
- Usb otg deleted because of leaks
- RGB color order
- Improved multi task
Changelog 13.9
- Deleted all tima debugs and craps
- Fixed Google DNS
- Added battery profile
- Added adaptive governor ( dont use with very high hotplug value, it will too laggy )
- Thermal limit changed to 95 from 85 ( causing some problem for heavy users )
- Many more
Changelog 13.8
- Fixed slow awake and freezes
- Fixed hotplug
- Activated hotplug by default
- Hotplug time reduced from 4 to 1 second
Changelog 13.7
- Smartmax added again
- All io tabs fixed ( thanks for report )
- IPv6 controls added (synapse)
- Ability to backup/restore wifi passwords (synapse)
Changelog 13.6
- Dvfs control passed no more changed max freq ( not perfect )
- Negative mode toogle fixed
- Usb modes fixed
- Fixed more governor for exynos tree
- Useless governors removed
- Hotplug setting to comfortable one for a few minutes ( fix for phone start )
Changelog 13.5
- Smartmax and uberdemand governors deleted
- Added zzmoove and impulse governors
- Fixed alucard nightmare darkness governors sticking some freqs
- Much relief cpu control
- Much better task cron
- OP updated with some root information ( lucky patcher fix )
- Fixed profiles not showing problem after update kernel
Changelog 13.4
- Cpu overclock to 2 Ghz
- Fixed google's bull**** ram leaks
- Now you dont have to restart your phone because of high ram after a few day usage
- Best ram management
- New versions wont reset your synapse data anymore
- Alucard governor added ( feature request )
- Screen resolutions control added ( feature request ) ( Thanks to alberto )
- Dont remember but many more. You will definetily feel.
Changelog 13.3
- Source base updated to XXUHOL1
- Lowmemorykiller improvement
- Ext4 improvement
- Touchkey changes
Changelog 13.2
- Added hotplug again
- Hotplug enabled by default for 3 cores
- Default screen wake up cpu freq set to 1.6Ghz
- Enabled Power-efficient control to hotplug section
- Deleted cpu max core control option because it is useless (hotplug active)
- Added Abyssplug hotplug governor
Changelog 13.1
- Added 23 cpu governors
- Fixed some cpu freqs sticking
- Ported a few utulities from snapdragon
- Rearranged every synapse script
Changelog 13.0
- Fixed mif crash random reboot
- Extreme battery life on idle mode
- Reduced wifi and mobile data drains
- Faster charging without overheat
- Remove irq affinity warnings for better idle
Changelog 12.9
- Fixed swaps (some heavy users continuesly boot problem)
- Android logger enabled by default
- Deleted backup/restore function because we dont need it and have better option (Titanium backup)
- Used dha tweaks ( If someone report i'm getting continuesly reboot, i will kill )
- Ram usage reduced
- Add parameter for check and activate root every boot
- Dont remember
Changelog 12.8
- Added unused cpu freqs on synapse (about)
- Added which time which freq used live show (about)
- Increased sound quality
- A7 core overcloked by default
- Default scheduler switch to noop and bfq
- Optimized modem wakes
- Disabled useless touch features
- Added power_efficient control to synapse (cpufreq)
Changelog 12.7
- Ramdisk updated to OL1
- Fixed cpu freqs sticking highest level problem when select 2 or 3 core
- Fixed reported random reboots
- Cleaned cpufreq driver
- F2FS deleted ( no compatible tw rom for now so no need )
- Fixed logger settings not sticking after reboot
- Much more selinux policy deleted
Changelog 12.6
- Exynos cpu max core control
- Now interactive calculate load before freq change
- True idle mode on neighbour driver
- True idle mode on regulatory timeout on wireless
- True idle mode on move rfkill poll work
- Disabled usb wakelocks and debugs
- True idle mode and powersave on LED blink work
- Clock sync work on power mode
- Time driver won't update idle time if cpu offline now
- Root restricts blocked
Changelog 12.5
- Deleted knox limitations on kernel
- Fixed private mode ( why peoples dont report guessing ? )
- Tweaked ondemand for more battery
- Process killing much as possible when going deep sleep
Changelog 12.4
- Fixed restore option ( FC still there but applying settings perfectly )
- Disabled needless kernel wakelocks
- Added control for disabled wakelock
- Better deep sleep when phone idle
- Frandom updated
- Ext4 improvements
- New logger system
- Conservative deleted for now, will add with snapdragon governors later
- Cortex deleted
- Setting up best config other than configurable ones
- Etc, etc sorry dont remember because i already spend many time.
Changelog 12.3
- Usb keyboard/mouse control
- Usb ptp mode control
- Added gps region select for faster GPS lock ( most of s6 port roms have wrong file )
- Now you can monitor which dns you have on synapse
- Rearranged screen controls for not sticking problem ( tried many times now sticking perfectly after reboot after clicking X )
- Some changes on touchscreen driver
- Disabled secure storage checks
- Disabled useless selinux features
- Some samsung dvfs disabled (renamed cpu max freq, so you cant control other than synapse)
- Attempt to fix shutters
Changelog 12.2
- Gpu overclock
- MIF voltage control
- Full touch boost control
- Correct voltage values
- Etc etc dont remember
Changelog 12.1
- Modem wakelock timeouts reduced
- Fixed l2_hsic keeping awake on deep sleep
- Zram deleted (no need anymore)
- Arm improvements
- Fixed scaling_freq crashes from samsungs sh*t rom frameworks ( %50 will work later too )
- Fixed samsung's typo fail on vdd value which causing crash
Changelog 12.0
- F2FS improvement
- Attempt to increase battery life more
- Experimental wakelock reduces
- Zram activated
- Improved battery life when using mobile data
- Fixed some crash which didnt effect any problem
- Many dont remember
Changelog 11.9
- Fixed fail codes on cpu driver
- Fixed freezes from cpu
- Improved smoothness
- Touchscreen controls
- Compiled with mine gcc from google source
- Gcc optimizated by me for 5410 core
- Many.
Changelog 11.8
- Reworked from I9500XXUHOH7 samsung source
- Ramdisk updated to I9500XXUHOH7
- F2FS support added for cache and data
- Added hotplug control
- Added lowmemorykiller control
- Added swap control
- Swap size update to 1000 mb
- Random reboot fixed
- Aurora users continuesly reboot problem solved
- Cpu overclock deleted
- Gpu overclock deleted ( will add later )
- Ram usage reduced
- Best control on ram
- Ext4 errors fixed
- Frandom updated
- Laptop mode control
- Enabled NTFS R/W support
- Some fixed for CIFS
- Enabled ISO & UDF CDROM support
- Enabled XPAD (Xbox game controller) support
- Some fsync changes
- Added row scheduler and set to default ( best on my benchmarks )
- Ksm values changes for better idle forms
- Many more lowmemorykiller patch for better management
- Ext4 speed up
- Mutex driver changes
- Changes for better battery
- Many more i dont remember
Changelog 11.7
- Private mode fixed
- Some wrong swaps corrected
- Another performance increasing try
- Kernel size reduced nearly 400kb
- Usb modes working good now. No need unplug, plug
Changelog 11.6
- Fixed lowmemorykiller
- Kernel clearing ram perfectly now ( It reduced freezes )
- Overheat reduced ( Of course not extremely because of our hardware )
- Mass storage fixed
- Sound quality improved
- Reduced high ram usage because of uksm source
- Many more.
Changelog 11.5
- Linux base updated to .109
- Fixed sometimes lockscreen opening delay
- Fixed irq random reboots
- Fixed mmc random reboots
- Fixed ext4 permission and causing random reboots
- Added frandom and tweaked
- Default governor changed to voltaqe
- Ram usage reduced nearly 150 mb
- Fixed heavy browsers lagging
- Many more dont remember all of them
Changelog 11.4
- Touchkey fixed
- Allocate idle thread for each possible cpu during boot
- Fixed comment mismatch over idle threads init
- Provide infrastructure for percpu hotplug threads
- Fixed bug in smpboot hotplug code
- Allow selfparking per cpu threads
- Store task reference in a separate per cpu variable
- Used smpboot threads on stop machine driver
- Mark per cpu stopper enabled early
Changelog 11.3
- Fixed all random reboots from kernel side
- Fixed cifs and ntfs
- Optimized memory control for better management and cpu boost
- Recent menu optimizations ( faster than any others )
- Fixed hotplug mechanism
- Fixed all known aosp bugs
- Used official cm ramdisk meaning supporting official cm and official cm based aosp roms too
- Max cpu core control option added back
- More responsive and fast
- Lcd power drain reduced
- Make more scalable by doing less atomic operations
- Queue mutex spinners with MCS lock to reduce cacheline content
- Make scheduler aware of cpu frequency state
- Optimization for tcp
- Optimized SLUB memory allocator
- GENTLE_FAIR_SLEEPERS fixes
- Speedup ext4
- Improved INT/MIF
- Disabled add_random for more performance on block
- Send events one packet at a time on input driver
- Optimized square root algorithm
- Added support for 2MB allocations on Gpu utulity
- Allowed clocksources to be selected earlier during boot
- Added sysfs entry for cdrom to LUNs
- Check for accessory device before disconnecting HIDs
- Fixed bad hashing of dentries
- Added a missing permission check to do_umount
- Reduced the worst case latencies
- Passed readahead info down to the i/o scheduler
- CPU unaligned access path
- Fixed the too small buffer for dname
- Optimized memcpy for cortex-A15
- Reduced log level on wireless driver
- Clean up anycast when an interface is destroyed
- Corrected kernel panic when accessing wireless driver
- Make watermarks tunable separately
- Added a sysctl to make optimistic addresses useful candidates
- Removed compressed copy from zram in-memory
- Upstream fixes on tick
- Break out early if freq equals to target_freq
- Improve debug prints on cpu driver
- Reduced more latency
- Added new routines to cpu driver
- Avoid flushing all workqueues
- Sync ro remount after blocking writers
- Optimized memory allocation on block
- Optimized memory operations
- Protected sysfs handler from invalid memory access
- Allowed request end to coincide with disksize
- Added auto loading of module for zram
- Fixed invalid memory access on zram
- Disabled allocation failure logging
- Changed ratio to 90% for bad compress
- Used rbtree instead of prio tree
- Removed obsolete simple_strtoul
- Removed useless variable in vmap_block
- Removed unused bdi_pending_list
- Put unused inodes to LRU after writeback completion
- Guarantee new group-entities always have weight
- Reduced IPI store
- Shorten freezer sleep time using exponential backoff
- Switch the protection of percpu_counter list to spinlock
- Consider preemption when migrating hrtimer cpu_bases
- Prevent enqueue of hrtimer on dead CPU
- Introduced a small and naive hashtable
- Used new hashtable implementation workqueue
- Used new hashtable implementation ksm
- Used new hashtable implementation elevator
- Invoke low power mode if card is not present
- Sync ro remount after blocking writers
Changelog 11.2
- Reduced latencies on softirq
- Lowmemorykiller improvement
- Fixed memory leak with sysfs when stats table are freed
- Optimized ARM RWSEM algorithm
- Update RWSEM from Linux 3.10.61
- Increased performance
Changelog 11.1
- Fstrim fixed
- Backup/restore fixed
- Hotplug fixed
- Much more smooth
- Bug fixes and improvement
Changelog 11.0
- Enabled standby ARP and multicast packet filters
- Optimised smart wake affine logic
- Let minimally loaded cpu balance the group
- Fixed inaccurate accounting for real-time task
- Increased bdi_min_ratio to 5 for better writeback
- Reduced wakelock time
- Fixed possible memory leak on nbd
- Fixed possible memory leak gpio
- Enabled wifi mac address changing support
- Optimized Wifi
- Optimized cpufreq table
- Break out early if freq equals to target_freq
- No more random reboot
Changelog 10.9
- Deep sleep timer reduced 20 seconds to 10
- Art mechanism changes
- Block driver completely fixed now
- Touchscreen driver fixed
- Random reboots reduced
- Set original governor to interactive
- Set hotplug agressive
- Other battery tweaks
Changelog 10.8
- Overheat reduced
- Fixed sensorhub causing random reboot
- Fixed ext4 causing random reboot
- Useless debugs disabled
- Ondemand-sec some errors corrected
- Performance improved
Changelog 10.7
- Wifi connection problem completely solved (AOSP)
- Disabled softkey vibration when device lock (AOSP)
- Default scheduler set to cfq
- Script for delete synapse data every flash
Changelog 10.6
- Sensor problems solved
- Ondemand-sec governor cpu3 stop and freeze problem solved
- Reduced modem wakelocks
- Cpu core mechanism set to battery save
- More tweaks for performance and battery stability
Changelog 10.5
- Hotplug improvement
- Fixed private mode for s6 users
- Changed hotplug default values for better battery save
- Adb insecure again
- Cpu driver changes for new governors
- Most responsive cpu values
- Many more.
Changelog 10.4
- Linux kernel base update to 3.4.108
- Built with Stock ARM Toolchain 4.8
- Compatible with all tw roms
- Fixed random reboots
- Fixed cpu freqs
- Stable a15 values
- Deleted 2 ghz a15 overclock
- Added CortexBrain
- Added lowmemorykiller control
- Added know disabler to synapse
- Added powersuspend control
- Added usb mode changer
- Added filesystem controller
- Fixed rom builder wrong parameters
- Reboot option added to synapse
- Added backup/restore option
- Kernel entropy control
- Optimize Recent Menu option
- UKSM implement
- Dynamic dirty page writeback control
- Dynamic fsync control
- Added all available tcp congestion controllers
- Kernel and rom logger control
- Live gpu state
- Bug fixes and improvement
- Many more look to synapse
Changelog 10.3
- Fixed wifi on AOSP
- Tweaked wlan_rx better deep sleep
- Reduced Sensorhub wakelocks
- Disabled hsic wakelocks on deep sleep
- Added busybox to /sbin
- Fixed cpu max value sticking
- Fixed laggy governor tab on synapse
- Improvement for hotplug
- Added min gpu value control
Changelog 10.2
- FC problems completely gone from kernel side
- Hotplug improved
- Fixed not working QoS implements, working perfect now
- A15 overclock fixed ( now going perfectly without random reboot)
- Some of possible memory leak fixed
- Wlan rx control option
- Blocked some of useless wakelock
- VoLTaqe governor updated for more battery
Changelog 10.1
- Hotplug control added back
- Performance tweaks
- Enabled basic ksm

How to report bug ? Please reporting your problem like answer this questions.
- Of course need logs. If you have random reboot or else you have to send log ( dmsg, last_kmsg ) from synapse/cortexbrain section. It will save logs to sdcard/volt. Another info after user command reboot not helping me. Please send log after reboot system itself not from you.
- Which rom are you using ?
- Which mod are you using ?
- When having issue ? ( A good explain can solve your problem without log because i can try too with my phone ).
- Have you got any other third party app about issue ?
- Have you got any other kernel tweak app other than synapse ?
How to use my phone like usb keyboard/mouse ?
- First of all you have to start adb debugging. You already dont know how to, google it.
- Install Usb Keyboard APP on Play Store.
- Lastly connect your phone to system via USB cable. It's done !

Bizde sizin gibi geliştirici türklerle gurur duyuyoruz
Good news bro, thanks.

GreaT News Downloading And Testing
Report if Any bugs Found

Wow another kernel for our device and with stweaks support

Wooooooooooooooooooow
Great news is coming
thanks man

khatkhatik said:
Wooooooooooooooooooow
Great news is coming
thanks man
Click to expand...
Click to collapse
I'm always here for help
melekbarca said:
Wow another kernel for our device and with stweaks support
Click to expand...
Click to collapse
Please try and report
ameshiya said:
GreaT News Downloading And Testing
Report if Any bugs Found
Click to expand...
Click to collapse
waiting reviews
nebulafire said:
Bizde sizin gibi geliştirici türklerle gurur duyuyoruz
Good news bro, thanks.
Click to expand...
Click to collapse
Biz Türküz kardeş hep birbirimizi destekleriz
Not at all

I flash it with twrp 2.8.5
Wipe Dalvik, Cache, Preload
and now it takes 15 mins and hanging on samsung logo
Im using prism 16
whats wrong?

khatkhatik said:
I flash it with twrp 2.8.5
Wipe Dalvik, Cache, Preload
and now it takes 15 mins and hanging on samsung logo
Im using prism 16
whats wrong?
Click to expand...
Click to collapse
Remove battery and try again

It worked like charm :good:
thx man
android is now optimizing my 400 apps
I really love to play with freq and voltage of cpu and gpu :laugh:
I will report my experience after that

Everything is going well Now I Will Try To Undervolt it And Test All Stuff
Thx For The GreaT Work (Y)

Ohh nice to see kernel development on this device is back! Thank's for your effort man :thumbup:
Sent from my Galaxy S4

now its hanging on start application page (after optimizing apps)
I think I have to do a clean installing

Wow!Another kernel!Will check and report after collage .now lazy as it have to optimise my 500 apps at boot?
Keep calm coz IPL belongs to KKR

Does this kernel works with AOSP's roms too? or just simple TW's roms.
Thanks!!!

nesallx said:
Does this kernel works with AOSP's roms too? or just simple TW's roms.
Thanks!!!
Click to expand...
Click to collapse
Sorry i forget mention about that. I will build for aosp next month

Keep it up bro. You are great

Great work. Now i'll have to come back to stock rom to review this new fully featured kernel.
If possible plz make another version for CM roms.

codybank_789 said:
Great work. Now i'll have to come back to stock rom to review this new fully featured kernel.
If possible plz make another version for CM roms.
Click to expand...
Click to collapse
He told that he would support CM in 1 month.Give him time mate[emoji2]
Keep calm coz IPL belongs to KKR