[KERNEL] [May26] ElementalX-EVO-4.3 | OC | UV | ZRAM | ROW | S2W | DT2W | BLN - Sprint HTC EVO 4G LTE

{
"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"
}
Kernel for Sense-based Jelly Bean ROMs
LATEST VERSION: ElementalX-EVO-4.3 (May 26, 2013)
Code:
* Standard disclaimer:
* Your warranty is now void. Use at your own risk.
* In other words: It is your choice to use this software,
* I am not responsible for any damage or problems!
This kernel has tons of options. You can get yourself into trouble. Overclocking and undervolting takes effort, you need to test, test, test in order to find stable settings for your device. Please don't complain about reboots or crashes if you're overclocking and/or undervolting. When you find settings that work well with your specific hardware, this kernel will be very stable and have long battery life.
If you have problems, or simply don't want to endlessly tweak kernel settings, then consider trying the Bulletproof kernel: http://forum.xda-developers.com/showthread.php?t=2181243
If you do want to endlessly tweak kernel settings, and get to know your hardware intimately, then you're in the right place.
FEATURES:
based on HTC Jelly Bean source code 3.16
Aroma installer
choose CPU optimization level: vanilla, elementalx, or ultra
optimized for extended battery life
overclocking/underclocking options
minimum CPU frequency 192MHz or 384MHz
choose max screen off frequency
user voltage control
choose voltage profile in installer
GPU overclocking
sweep2wake
doubletap2wake
pocket detection to prevent accidental wakes
button light notification
/system writable
force fastcharge
optional zRam with snappy compression
NTFS r/w support
governors: intellidemand (default), badass, lagfree, lionheart
i/o schedulers: ROW (default), FIOPS, SIO
option to disable fsync
increased refresh rate for HDMI output via MHL adapter
optimized -O3 linaro 4.7.3
DOWNLOAD
Elemental-EVO-4.3
NOTE: If you downloaded this before 9pm EDT on May 26, please redownload and reinstall the file!
If you have trouble installing or using ElementalX, or you don't know what settings to choose, I recommend you try Bulletproof Kernel: http://forum.xda-developers.com/showthread.php?t=2181243
Previous versions:
Elemental-EVO-4.2
ElementalX-EVO-3.3
ElementalX-EVO-3.2
ElementalX-EVO-3.1
ElementalX-EVO-JB-v2.5: http://goo.gl/Bvx3j
ElementalX-EVO-JB-v2.3: http://goo.gl/KJlgZ
ElementalX-EVO-JB-v2.2: http://goo.gl/qSavM
ElementalX-EVO-JB-v2.1: http://goo.gl/XWDYK
ElementalX-EVO-JB-v1.2: http://goo.gl/LTYN3
ElementalX-EVO-JB-v1.0: http://goo.gl/xNUab
ElementalX-EVO-JB-v0.8: http://goo.gl/FPDra
ElementalX-EVO-JB-v0.7: http://goo.gl/KDDjK
INSTALLATION
1. Install zip from TWRP Recovery
2. Follow the instructions, if you don't know what to do, use the preselected option
3. Reboot!
S-OFF highly recommended for easy installation
The installer includes a method to flash the boot.img with s-on, however, some people still have difficulties. If it doesn't work, extract boot.img from the zip, reboot to bootloader and do:
fastboot flash boot boot.img
Note: you must still run the installer to get all the configuration files!
Please hit the Thanks button if you use this
If you really like this, please consider buying me a beer
Click to expand...
Click to collapse
Special thanks:
zarboz and Sbryan12144 for porting S2W to the One XL
jrior001 for CPU1 fix
backfromthestorm for fstrim
xHausx and amarullz for installer stuff
tbalden for bln
​
NOTES:
Configuration
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!)
The settings can be changed by editing /etc/elementalx.conf and rebooting. Advanced users can apply settings on the fly by running /etc/init.d/99elementalx as root.
There is no need to edit /etc/init.d/99elementalx. All settings are configured in /etc/elementalx.conf.
If settings are not sticking, make sure the file permissions for /etc/init.d/99elementalx are set to execute. Every time the settings are applied, a log file is created at /data/local/tmp/elementalx-kernel.log. Problems can be diagnosed by looking at the log file.
Please check to see if any /etc/init.d scripts or apps are interfering with your settings If you're on ViperXL, make sure your settings in Venom Tweaks are the same as the ones in /etc/elementalx.conf (for example, sweep2wake settings)
Kernel Tuner
You don't need Kernel Tuner because the ElementalX installer sets everything up automatically, but if you want to check or change settings, Kernel Tuner is recommended. Just be aware that Kernel Tuner is set by default to apply settings on boot, which can interfere with the settings you chose in the ElementalX installer.
Venom Tweaks force close
If Venom Tweaks closes when you try to access the CPU tab, go to Settings->Apps->Venom Tweaks and push the Clear Data button. This should fix the problem.
CPU Optimization
Vanilla: stock voltages, stock l2 cache frequency, stock bus bandwidth
ElementlaX: increases l2 cache frequency and bus bandwidth, allows you to choose voltage level in installer
Ultra: increases l2 cache frequency and bus bandwidth even more. May cause instability, please test thoroughly for stability if you use this option.
Overclocking
Overclocking (underclocking) is optional. Whatever frequency you chose in the installer will be set at boot for both CPUs. Frequencies can be changed any time using apps like No Frills or Kernel Tuner. WARNING: not all devices can handle overclocking. The stock maximum CPU frequency is 1.5GHz. In versions of the kernel prior to 4.2, the frequencies were labeled wrong so you won't be able to overclock as high with version 4.2+.
CPU voltages
CPU voltages can be changed with Venom Tweaks, Kernel Tuner or System Tuner. Be careful, lowering voltages could cause instability. If you have stability problems even at the highest voltages, try the vanilla version
Minimum CPU frequency
Sets the minimum CPU scaling frequency. 192MHz is the recommended default and should work fine on the vast majority of devices. The 384MHz option is available for devices that experience random reboots while the device is idle. It is recommended that you try increasing the minimum voltage by 25mV before changing the minimum CPU frequency.
Max screen off frequency
This sets the highest CPU frequency available while the screen is off. It is recommended to disable this for stability. Also, do not set this to 192MHz or 384MHz, as many devices experience random reboots at these frequencies. The default is 486MHz, which should be safe for most devices. If you experience random reboots while the device is asleep, set this to a higher frequency. This setting can be changed in /etc/elementalx.conf or using an app like Venom Tweaks.
GPU frequencies
3D GPU: 480 (overclocked) or 400 (stock)
2D GPU: 266 (overclocked) or 200 (stock)
Governors
Intellidemand is the default CPU governor. There are other governors included, however, intellidemend is recommended for best balance of battery life and performance.
Installing a new ROM
If you install a new ROM, it will overwrite /etc/init.d/89elementalx and /etc/elementalx.conf. The kernel will run perfectly fine without these files, but you will lose your settings and certain features.
Sweep2Wake
Sweep2wake allows you to wake up your device by swiping your finger across the capacitive buttons from left to right. Swiping from right to left will put it back to sleep (sweep2sleep). There are now options for sweep2wake/sweep2sleep, sweep2sleep only, and disabled. If you use ViperXL, make sure to enable sweep2wake in Venom Tweaks. Note that in Venom Tweaks, the sweep2sleep only option can be selected by choosing Enable (no buttons backlight).
DoubleTap2Wake
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping in the bottom inch or so of the screen, above the capacitive buttons. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/doubletap2wake
0=disabled
1=enable doubletap2wake
Pocket Detection
Pocket detection protects against accidental wakes while S2W, DT2W or L2W are enabled and the phone is in your pocket. Pocket detection uses the proximity sensor. A few people have a problem with their proximity sensor that makes DT2W not work, so I've made an option to disable pocket detection. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/pocket_detect
0=disabled
1=enable pocket detection
Button Light Notification
With Button Light Notification (BLN), the capacitive buttons will blink on and off when you have a new notification. As soon as the screen comes on, BLN is canceled and the lights will no longer blink until you have another notification. Please note that if you have your screen set to turn on when a message arrives, you will not see the buttons blinking because once the screen comes on, the button light notification is canceled. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/class/leds/button-backlight/bln
0 = disabled
1 = BLN enabled
What is zRam
zRam creates a compressed block device in RAM that is used as swap. Although it claims some of your RAM as swap, everything written to swap is compressed. This increases the apparent memory available to the system and helps with multitasking. Swap files on disk are very slow, but with zRam the swap is on RAM so it can be read as quickly as regular memory. Even though the data need to be decompressed, modern CPUs can decompress quicker than if it had to be to read from disk. The penalty is cpu usage, which could drain battery; however, this is likely negligable in daily use. I didn't enable this by default because not everyone will want it. This is for heavy multitaskers and will allow you to quickly switch between more apps and have more tabs open in your browser without refreshes.
zRam is disabled by default. If you want to enable it, edit /etc/elementalx.conf
change ZRAM=0 to ZRAM=1 and reboot.
You can check if zRam is working by typing the command "free" into the terminal. You should see the total used and free swap. If these are all 0, then zRam is not enabled. Please ensure that other apps are not changing your minfrees, zRam works best with low minfrees and high swappiness.
NTFS support
This is for anyone who wants to use OTG to connect a USB stick or portable harddrive formatted with Microsoft's NTFS filesystem. You will need Stickmount or a similar app, HTC Sense+ won't detect NTFS.
Enable/disable fsync
Disabling fsync can increase filesystem performance. However, there is a small risk of data loss if the system suddenly crashes. If you can't afford to lose data, keep fsync enabled. Many custom kernel disable fsync, I leave it enabled by default for safety reasons.
XBox controller support
There is an experimental module that supports XBox gamepads, however, some people have reported that it draws too much power and doesn't work. I've suggested trying a powered USB hub, but still not sure if it works.
Changelog:
v4.3:
-button light notification
-doubletap2wake
-pocket detection to protect accidental wakes
-optimized AES and SHA1 routines
v4.2:
-correct oc frequencies
-adjust l2 cache frequencies
-gpu overclock frequencies now 480 3D and 266 2D
-fix max screen off limit
-various patches from Linaro and CAF
-WiFi module fix (thanks thicklizard)
-avoid loadavg moire
-enable automatic process group scheduling
-max screen off frequency can be disabled
v3.3:
-optimized build compiled with -O3
-linaro 4.6.3 -> linaro 4.7.3
-force ac for unknown chargers
v3.2:
-use glibc memcopy
-use glibc string
-add /dev/frandom
-add force fastcharge
-change makefile optimizations
-tweak clocks
-fix aroma installer(?)
v3.1:
-based on HTC source code 3.16
-overclock to 2.1GHz
-minimum frequency 192 or 384MHz
-screen off frequency
-optional overclock GPU
-full voltage control
-enable/disable fsync
-intellidemand default governor
-add sweep2wake
-add zRam with snappy compression
-init.d support
-ntfs r/w support
-fix HDMI refresh rate
-add lionheart, badass governor
-add row i/o scheduler
-adjust l2 cache frequencies
-default i/o scheduler is ROW
-add fix for crash when wp_mod.ko loaded
-disable gentle fair sleepers
-xz kernel compression
-fix installer conflicts
-dual zram
-use zcache instead of qcache
-use zsmalloc instead of zxmalloc
-CPU1 governor can be set independently
-set max screen off frequency
-choose 192 or 384 minimum CPU frequency
-update cpu_power according to cpu load
-CPU optimization options: Vanilla, ElementalX or Ultra
-small tweaks to GPU settings
-fstrim at boot
-switch do_fsync() to fget_light()
-adjust readahead to 2048
-made sure that if you flash boot.img in fastboot you get vanilla version
v2.5:
-added 384 MHz frequency step when selecting 192MHz as min frequency (needed because CPU1 will not stay at 192MHz)
-adjustments to init script
v2.3:
-adjustments to init script (now works with Viper4G 3.0.1)
-added extra governors (lionheart, lagfree, interactivex2, and badass)
-new boot.img from 3.16 OTA
v2.2:
-choose minimum CPU frequency (192MHz or 384MHz)
-option to leave minimum voltage at default
-optimized CPU control module, now reads PVS efuse and sets appropriate voltage levels
-streamlined options and config file
-optional XBox controller support
v2.1:
-Option to completely disable overclocking/undervolting
-If overclocking, choose between optimization for stability or performance
-stability option does not increase L2 cache frequency and bus bandwidth
v2.0:
-added intellidemand governor (default)
-added fiops i/o scheduler (default)
-optional zram with snappy compression
-optional ntfs r/w support
-select minimum voltage (800, 825, 850, 875, or 900mV)
-added 1134 and 1242 MHz underclocking options
-increased bus bandwidth
-many changes to installer and configuration files
v1.2:
-minor changes to init.d script
v1.1:
-fix low 3D GPU setting
-undervolt option now undervolts 384MHz frequency step to 800mV
-boost L2 cache frequency for extra performance
-increase readahead buffer to 4096
-tried to fix touch in aroma installer
v1.0:
-add voltage options
v0.8:
-removed 1998MHz frequency step
-added 1647MHz frequency step
-increased voltages slightly for stability
-added option to install without boot.img
v0.7:
-tweaking install method
v0.6:
-fix installer?
Source:
ElementalX-3.2
ElementalX-JB-v2.5: http://goo.gl/uWK4r

Nice thanks! I will be trying this now after I update my SuperJELLY to r201

Niceeeeeee I'll give this a try, downloading now..

Anyone try this yet?
Basically I just need to know if the modules load or not.
If they do, we're good to go.
If not, I need someone to type this in terminal:
su
insmod /system/lib/modules/oc_mod.ko
dmesg > /sdcard/dmesg.txt
and post the relevant lines of dmesg.txt

Flashed it wouldn't let me overclock and it booted
Edit: flashed again it boots I'm overclocked too
Sent from my EVO using xda premium

Im on Super Jelly and phone wont go past boot animation

Alright, don't actually install it, we just need to test the modules.
Could someone who has the stock JB kernel extract wp_mod.ko and oc_mod.ko from the zip file and try to insmod them from the terminal and let me know what the output of dmesg is?
Also, could someone post the output of:
uname -r

It works just aroma installer is a little buggy
Sent from my EVO using xda premium

OMG!! a kernel!! thank you so much bro!! we need some kernels for this device :good: thank u.. i almost **it my self when i seen there was a new kernel!! lol... im down to help test but im only good for flashing zips.. let me kno if i can help.. thank u flar2

It works for me. Overclocked at 1.8 on superjelly
$tack$

so i take it we good to flash this??

I have a question. If the modules didn't flash.. my WiFi wouldn't work right?... Or what wouldn't work?
$tack$

I think I might have fixed the installer, not sure how things work on this device.
evo401 said:
OMG!! a kernel!! thank you so much bro!! we need some kernels for this device :good: thank u.. i almost **it my self when i seen there was a new kernel!! lol... im down to help test but im only good for flashing zips.. let me kno if i can help.. thank u flar2
Click to expand...
Click to collapse
Well, it's not exactly a custom kernel, just some modules and config files to make it work

Sorry for posting screenshots. To happy right now.
$tack$

^^I can get over 7400 on the One XL
1998 MHz likely isn't going to work.
Anyone tested /system write?
evo401 said:
so i take it we good to flash this??
Click to expand...
Click to collapse
At your own risk, I don't have this device so I don't know exactly what happens if you try to flash this.
stacksptdtdm said:
I have a question. If the modules didn't flash.. my WiFi wouldn't work right?... Or what wouldn't work?
$tack$
Click to expand...
Click to collapse
This won't affect wifi. Your existing modules stay the same.
The kernel is the stock JB kernel, I just had to modify the boot image to add init.d support.

flar2 said:
Alright, don't actually install it, we just need to test the modules.
Could someone who has the stock JB kernel extract wp_mod.ko and oc_mod.ko from the zip file and try to insmod them from the terminal and let me know what the output of dmesg is?
Also, could someone post the output of:
uname -r
Click to expand...
Click to collapse
uname -r
3.4.10-g014d33e
when i try insmod /system/lib/modules/oc_mod.ko
i receive "insmod: init_module '/system/lib/modules/oc_mod.ko' failed (file exists)"
I do have overclock though.
I'll post my dmesg since I don't know what part is needed -__- lol

it flashed using the 1809 oc but i am getting fc on messages,gmail,android media, i can open tapatalk and go thru threads but once i try to enter one i get fc. using nova widgetswill not load i used your latest alpha

flar2 said:
^^I can get over 7400 on the One XL
1998 MHz likely isn't going to work.
Anyone tested /system write?
At your own risk, I don't have this device so I don't know exactly what happens if you try to flash this.
This won't affect wifi. Your existing modules stay the same.
The kernel is the stock JB kernel, I just had to modify the boot image to add init.d support.
Click to expand...
Click to collapse
Getting there
$tack$

To stop fc u have to flash a kernel voltage stabilizer zip
Sent from my EVO using xda premium

Installer still dinky. And instead of it saying 0.6 its 0.5?
$tack$

Related

[KERNEL][PLAY] LuPuSv12-GB [STOCK-GB][LINARO 4.7.3][UPDATED 07-09-13]

LuPuS-STOCK-GB
{
"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"
}
Based Off SONY 4.0.2.A.0.84 Sources​
Disclaimer
Code:
[COLOR="DarkOrchid"]#include[/COLOR] [COLOR="Magenta"]<std_disclaimer.h>[/COLOR]
[COLOR="Blue"]/*
* Your warranty is now void.. LOL I guess you knew it already.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, you getting dumped or you getting fired because your phone
* bootloops and alarm does not go off. Please do some research if you have any
* concerns about features included in my kernel before using it! YOU and only
* YOU are choosing to make these modifications.
*/
[COLOR="Magenta"]#ifdef[/COLOR]
You have a [COLOR="DarkGreen"]question[/COLOR] post it in the [COLOR="DarkRed"]thread[/COLOR],
Instead of [COLOR="DarkGreen"]Pm'ing me[/COLOR], as other users may
experience you [COLOR="DarkRed"]problems[/COLOR]
[COLOR="Magenta"]#endif[/COLOR][/COLOR]
Included in Kernel-
-24 governors (ondemand default)
-6 io-schedulers (sio default)
-O/C up to 2ghz although not recommended
-fudgeswap
-slqb memory allocator
- Increased zram disk size
- Increased zram to 30%
- Changed LZO --- Benchmarks show compression and decompression times performance increased by double
- Linaro optimizations from my ics-beta
Lulzactive - Thanks to Tegrak
Based on Interactive and Smartass. When workload is greater than or equal to 60%, the governor scales up
CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step.
When screen is off, frequency is locked to global scaling minimum frequency
Virtuous (recommended) change with nothrills cpu or similar app
Virtuous is a modded smartassV2 which gives even more battery time then smartassV2
Intellidemand - Thanks to faux123
This is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling,
and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such.
Intellidemand does not jump to highest frequency when screen is off.
Lazy - Thanks to Ezekeel
The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand.
Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state
on a step overriding sampling interval.
Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always
select the maximum frequency while the screen is off.
-Ondemandx
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
-Lionheart:
Is a conservative-based governor. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
To 'experience' Lionheart using conservative, try these tweaks:
sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe).
up_threshold:60
down_threshold:30
freq_step:5
Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
BadAss Governor ?:
Badass removes all of this "fast peaking" to the max frequency. Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1024Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.
Overclocked to 2ghz--- don't think its to stable though---
Please give feedback wether its stable for you or not if you overclock
FudgeSwap
-Helps improve multi-tasking in low memory situations forcing apps to swap.(already in DooM's sources)
SLQB - (SLAB allocator with Queue)-
This memory allocator is designed for small number of CPUs system (such as desktop or smart phone devices). This allocator is design to be simple and it is optimized for using order-0 pages as much as possible (order-0 pages are the simplest therefore quickest type of memory in a Linux system to allocate).
Recoveries
TWRP = Volume UP
CWMVolume DOWN
LuPuS MENU
To Run LuPuS Menu use either ScriptManager get it HERE on google playstore
Or
Use Terminal Emulator get it HERE on google playstore.
Code:
su
lupus
* information is in lupus menu
0/ UKSM
1/ CIFS Menu *
Enable
Disable
2/ zRam Menu *
Enable
Disable
Set zRam size ( default is 60)
3/ Frandom Menu *
Enable
Disable
4/ Clean and Remove tweaks
Remove init.d's
5/ Tweak Menu
Note all tweaks are preset from here and option to set as init.d's
Clean all temp files
SQLITE optimizations
LMK Optimizations
Network optimizations
Defend against ARP spoofing
Remove android logger
SDcard speed tweak
Flag blocks as non-rotational
6/ Performance Menu
Note all options are se by user input from here and option to set as init.d's
Set CPU frequencies
Set Governor
Set IO-Scheduler
Voltage Control
VM tweaks (explained below)
VM Tweaks
dirty ratio and dirty background ratio 1 & 2
This controls how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
dirty_expire_centisecs
How old "dirty" data should be before the kernel considers it old enough to be written to disk. It is expressed in 100ths of a second.
dirty_writeback_centisecs
This is the interval of when the writeback daemons periodically wake up and write "old" data out to disk. It is expressed in 100ths of a second.
min free kbytes
This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
overcommit_memory
This controls overcommit of system memory, possibly allowing processes to allocate (but not use) more memory than is actually available.
0 - Heuristic overcommit handling. Obvious overcommits of address space are refused. Used for a typical system. It ensures a seriously wild allocation fails while allowing overcommit to reduce swap usage. root is allowed to allocate slighly more memory in this mode. This is the default.
1 - Always overcommit. Appropriate for some scientific applications.
2 - Don't overcommit. The total address space commit for the system is not permitted to exceed swap plus a configurable percentage (default is 50) of physical RAM. Depending on the percentage you use, in most situations this means a process will not be killed while attempting to use already-allocated memory but will receive errors on memory allocation as appropriate.
Swappiness
A property for the Linux kernel that changes the balance between swapping out runtime memory, as opposed to dropping pages from the system page cache. Swappiness can be set to values between 0 and 100 inclusive. A low value means the kernel will try to avoid swapping as much as possible where a higher value instead will make the kernel aggressively try to use swap space.
VFS Cache Pressure
File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
8/ Enable / Disable Quick Key Reset
- Reboot device quickly by Holding HOME and POWER Key (Disabled by default)
- Enable
- Disable
I would like to say a big thanks to -
paxChristos
KeiranFTW
DooMLoRD
Solomon4400 - For helping me test
tempest918 - For the Logo
xeozus
nobodyAtall
Faux123
Erasmus
Leedroid
Jerpelea
Phil3759
CTCaer
Anyone missing please PM me
downloads/changes in post 2
Kernel sources -b master
https://github.com/garwedgess/Xperia-2011-Kernel-2.6.32.9
CWM source -- https://github.com/garwedgess/android_bootable_recovery -b lupus-cwm
Changelog
Code:
[hide]
[B][U]v2[/U][/B]
[LIST]
[*]- Fixed Problems Mounting SD-Card
- Changed Recovery Images
- Added 2 New Governors
- Superbad- a "superbad" super smooth rendition of a highly optimized "smartass" governor! --- fast and smooth
- Darkside - a "slightly more agressive smart" optimized governor! --- fast and smooth
[/LIST]
[B][U]v3[/U][/B]
[LIST]
[*]- Changes to make it smoother
- Try make better battery life
- New CPU Freq Table (first time I can overclock to 1.8ghz on my PLAY)
[/LIST]
[B][U]v4[/U][/B]
*** Forgotten version - never released ***
[B][U]v5[/U][/B]
[LIST]
[*]~ Added in .400ghz on freq table (handy while listening to music-pointed out to me)
~ Added governor -[COLOR=Green][B] Intellidemand2[/B][/COLOR]
~ Kgsl - use highest performance level on wake-up from sleep
~ Lowered cpu freq on boot time, to avoid any issues on booting with the new freq table
~ KSM added
[/LIST]
[B][U]v6[/U][/B]
[LIST]
[*]- Re worked from source(still DooMs)
- 720p version & 480p version (372mb RAM)
- Fixed battery drain new kernel last much longer :)
- Wifi modules built in - thanks @[URL="http://forum.xda-developers.com/member.php?u=1844875"]CosmicDan[/URL] for script
- Memcopy
- Memory allocator
- Updated/ patched & fixed LZO
- Compaction
- Lowered vfs_cache_pressure
- Disabled gentle_fair_sleepers
- LMK optimizations (LowMemoryKiller)
- Linaro optimzations
- Improved CIFS support
- NTFS
- KSM
- Updated SIO Io-Scheduler
- Revert to 1.6 OC (for now)
- Google Snappy compression / decompression
[/LIST]
[B]v7[/B]
- Built with Linaro 4.7.3
- Added Io-Scheduler ZEN
- Added SmartassH3 Governor
- Stop Entropy from depleting
- Frandom
- Optimize Deadline IO- Scheduler
- Backport Binder from CAF 3.4.0
- Backport timed_gpio from CAF
- Update LMK
- Remove Fudgeswap
- Added Zcache
- CFS tweaks for responsivness
- Update Compaction
- Makefile optimzations
- ARM optimizations
- Optimzed Tiny RCU
- Added optimized crc32 lib from faux123
- Logger Backported from CAF
- Entropy tweaks
- Free'd RAM from logger
- fsync
- Custom partition layout ( larger data partition)
- Updated Smartassv2
- Quick keyboard reset (hold HOME + POWER)
- Snapdragon optiizations
- Improved boot time
- Improved wifi to load at first boot
- Removed Autoroot feature
- Updated and re-worked ramdisk
- Fix to check if device is CDMA if it is kernel will fix wifi
- TWRP Recovery = Volume UP
- Updated CWM = Volume DOWN
- LuPuS Menu Included
- No more modules needed to be flashed
- Reduced Kernel size
[B]v8[/B]
- Fixed reboot to recovery
---- Custom CWM
- Clean-up of menu
- Added own wipe options menu -- with extra options
- Aroma File Manager from CWM --- Must have aroma ([COLOR=Red]aromafm.zip) placed on root of sdcard[/COLOR])
- Multi zip installer
- Reboot options - Power off re-added under this menu
- Pointless but people keep asking me for it so re-added wipe battery stats also.
- LuPuS themed...
[B]v9[/B]
- Added ROW IO-Scheduler
- Tweaked Governors
[list]smartassV2
smartassH3
virtuous
lionheart
conservative
brazillianwax
lulzactive
superbad
darkside[/list]
- Improved wifi loading
- Disabled Key Reset (can be enbled in LuPuS Menu)
- mm: do uninterruptible sleep
- Reverted Entropy Patch [b](To see if lag in gaming is gone, if not let me know so I can re-add this patch)[/b]
- Other minor changes
---- CWM updated to 6.0.3.2
- Disable recovery flash will now remove nAa recovery so to be sure device does not boot into wrong CWM.
- Fixed Advanced restore
- Fixed busybox symlinks generation (aka) fixed CWM backup not working
- Fixed install from sideload being mixed up with toggle signature
- Remove confirmation from install from sideload as it can be cancelled at anytime.
- Clean-up of UI
- Some other changes which will be in CWM v6.0.3.3
---- Complete Ramdisk Clean up & Improvment
- Cam fix for CDMA, if r800x is in build.prop kernel will install camera.lib
- Reworked booting
- Supports m2sd and other ap2sd scripts
- Fixed Reboot To Recovery (It reboots to last one used IF you don't have scripts that wipe /cache on boot)
- Reworked Kernel logs, they are located in /data/local/tmp/
- Improved init.d
- lupus menu clean up and improvement
- Boot.d - If phone is taking a long time to start move suspicious init.d scripts to /system/etc/boot.d
They will be run in background and won't affect boot time.
[B][U]v10[/U][/B]
- Rebased on SONY 4.0.2.A.0.84 kernel source
- Tweaked SIO
- Tuned ROW
- Fixed all Governors to work 100% on GB
- Tweaked CPU on GB
- Removed all debigging
- Use zRam from SONY .13 ICS source
- Fixed Google Snappy zRam so device actually uses it
- More Battery friendly
- Removed SFB Net Scheduler
- Updated Tiny RCU to Bloatwatch Edition
- reverted touchpad update
[B]v11[/B]
- Fixed LAG in gaming
[/hide]
[B]v12[/B]
- Added UKSM ( can enable it in LuPuS Menu)
- Set default swapiness to 20
- Removed fsync
- Removed Cleancache
- Removed zCache
- Removed ZEN IO-SCheduler
- Tweaked Entropy
- Stopped entropy from depleting
- Fix LEDs
- Updated CWM
* brought back reboot system and Power off options to main menu
* Fixed advanced restore menu
* updated to latest CWM source
- Minor Clean-up of lupus menu
- Minor Ramdisk changes
If you like my work please consider buying me a beer or something else
by clicking the DONATE ME button, of course it isn't needed but greatly appreciated and keeps me motivated.
Downloads
If you need root for STOCK ROM
Code:
[COLOR=Purple]Root[/COLOR] : ( Flashable via recovery )
* SuperSU : [URL="http://download.chainfire.eu/204/SuperSU/"][COLOR=Green][U]Download[/U][/COLOR][/URL]
* Superuser : [URL="http://androidsu.com/superuser/"][COLOR=Green][U]Download[/U][/COLOR][/URL]
If coming from version before v7, you need to wipe all partitions..
======================== 720p Recording ========================
LuPuS_zeus_GingerBreadv12-full.img
md5 = 16294503408d6a0bf3e1cf6b89c252fc
======================== 480p Recording ========================
LuPuS_zeus_GingerBreadv12.5-ram.img
md5 = 73c431d94849d65a87acd23982b75202
If your MD5's don't match then re-download before saying it doesnt work
*******No need to flash wifi modules they are only in attachments as a backup*******
Important
Coming from a kernel with STOCK partitions??
Via fastboot enter the commands:
Code:
fastboot erase userdata
fastboot erase system
You must wipe userdata and system if coming from a STOCK partirion kernel, Otherwise u will be stuck in a loop
Click to expand...
Click to collapse
.
What is CIFS???
Server Message Block (SMB) or Common Internet File System (CIFS) are normally used to provide shared access to files on a network, mostly involving computers running MS Windows.
It allows you to conveniently mount/unmount your network accessible file resources and access the files transparently via your favourite Android app (playing music / videos, accessing documents etc.) Settings are stored on your SD card with permissions to write also to your SD card.
Now download CifsManager or similar app and configure it
Zram is not enabled by default- to enable it flash the wedgess-NEW-Zram-Enabler.zip below
If for whatever reason you want to disable it after you have flashed the .zip, just go to ect/init.d and delete 00zram
Cool, glad to see you got it working even if its not liking some of the governors.
wedgess said:
Downloads HERE
LuPuS-GB-LiNaRo.img
LuPuS-GB-WiFi-MoDuLeS.zip - (needed for working wifi)
Please Click Thanks
Click to expand...
Click to collapse
So what do you think is the best combination of governor/scheduler for gaming?
Update your ROM and tell us how it goes.
Good news,
thanks for your work man, tonight i'm gonna put some Wolf in my phone.
I hope it is as performant as your ics work.
Thanks
No lag here. Will post if there's any problems.
Wedgess thanks for making a gb kernel but can you add CDMA support for those of us on R800x on your spare time? If you dont mind I will fill you in about my xperia play.
This is a thread from doomlord that has a working CDMA kernel which is based on version 2.3.3 gb. Doomlord was able to create a 2.3.4 kernel for us R800x users but camera functionality doesn't work at all. (I was hoping for the thread to be revived but it seems development has been put to a stop) So were stuck on doomlord gb 2.3.3. Currently I'm using kernel v1 from doomlord that has a working recovery and i am not using v2 posted in the thread below.
http://forum.xda-developers.com/showthread.php?t=1368636
Since you don't have the device (that im aware of) I don't mind testing it if you wish :highfive:
Does the zram enable by default?? Or do we need to enable it??
thi3um said:
Good news,
thanks for your work man, tonight i'm gonna put some Wolf in my phone.
I hope it is as performant as your ics work.
Thanks
Click to expand...
Click to collapse
lol thanks bro its just ae smooth if not.......
chery2k said:
Wedgess thanks for making a gb kernel but can you add CDMA support for those of us on R800x on your spare time? If you dont mind I will fill you in about my xperia play.
This is a thread from doomlord that has a working CDMA kernel which is based on version 2.3.3 gb. Doomlord was able to create a 2.3.4 kernel for us R800x users but camera functionality doesn't work at all. (I was hoping for the thread to be revived but it seems development has been put to a stop) So were stuck on doomlord gb 2.3.3. Currently I'm using kernel v1 from doomlord that has a working recovery and i am not using v2 posted in the thread below.
http://forum.xda-developers.com/showthread.php?t=1368636
Since you don't have the device (that im aware of) I don't mind testing it if you wish :highfive:
Click to expand...
Click to collapse
oh ok, ill do a cdma version tomorrow or sometime over the next few days. pm me ur gtalk u can test
sdojoin said:
Does the zram enable by default?? Or do we need to enable it??
Click to expand...
Click to collapse
No it should be enabled by default
Sent from my R800i using xda premium
Thanks!! Gonna will try it asap.
You are now our KernelLord lol
Im on way to class & can't test now but I will asap. I would love to see if u found a way 2 speed up the already fast GB.
Sent from my R800i using xda premium
Does your kernel hav autoroot feature?? Just curious. I can't seem to go to my system directory using script manager. Is it just me or does anybody else hav the same issue?? It sure are feels a bit smooth than dooms'kernel.
sdojoin said:
Does your kernel hav autoroot feature?? Just curious. I can't seem to go to my system directory using script manager. Is it just me or does anybody else hav the same issue?? It sure are feels a bit smooth than dooms'kernel.
Click to expand...
Click to collapse
ye it has autoroot.ive used script manager just there to check it had no problems going to the system directory opened straight away. ye I never used dooms that much but this seems really smooth, still havent switched back to ics yet
Sent from my R800i using xda app-developers app
wedgess said:
ye it has autoroot.ive used script manager just there to check it had no problems going to the system directory opened straight away. ye I never used dooms that much but this seems really smooth, still havent switched back to ics yet
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Mybe i'm doing something wrong. Nova 3 seems to act pretty weird to. I really wonder... Mybe i should giv it a day or 2 just to get it use to with me phone hardware. Thanks again.:thumbup:
Edit; Do u think i should wipe cache n dalvik cache on the 1st boot after switching?? Mybe i should just do it just to be sure.
Originally Posted by wedgess
ye it has autoroot.ive used script manager just there to check it had no problems going to the system directory opened straight away. ye I never used dooms that much but this seems really smooth, still havent switched back to ics yet
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Mybe i'm doing something wrong. Nova 3 seems to act pretty weird to. I really wonder... Mybe i should giv it a day or 2 just to get it use to with me phone hardware. Thanks again.:thumbup:
Edit; Do u think i should wipe cache n dalvik cache on the 1st boot after switching?? Mybe i should just do it just to be sure.
Click to expand...
Click to collapse
Strange alright i tried nova3 earlier and had no problems with it, it ran smooth for me, I say wipe it to see if it makes any difference for you, no hatm in trying.
Sent from my R800i using xda app-developers app
wedgess said:
Strange alright i tried nova3 earlier and had no problems with it, it ran smooth for me, I say wipe it to see if it makes any difference for you, no hatm in trying.
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Just did. Yupp it does makes a diff. Thanks man. Nova 3 respons a bit faster n the graphic seems a lot better too. Weird...
Mybe u should make a GB Linaro rom to match this kernel.
sdojoin said:
Just did. Yupp it does makes a diff. Thanks man. Nova 3 respons a bit faster n the graphic seems a lot better too. Weird...
Mybe u should make a GB Linaro rom to match this kernel.
Click to expand...
Click to collapse
good stuff, glad to hear I know but my linux is running out of space due to the amount of kernel sources I have lol.ill have to push them all to github to make the 25gb+ space needed, which will take awhile Hoping some rom devs will release linaro built roms now, we’ll see though
Sent from my R800i using xda app-developers app
I'll give this a try with DiXperia 2 rom this rom is fastest I've seen so far with doomkernel v14. I used lupus v4 with few ics roms and ran beautifully. Missed the great gaming in gb so this is very welcome as doomlord has moved onto htc one x thanks so much can't wait to try your kernel
I'm on dixperia 2 as well , will test it too. bye the way is this kernel support CIFS mounting ?
EDIT : working great, using Virtuous governor with SIO and it's really fast, coupling with dixperia2 its hell fast
I'm using a lot of launched apps (holo launcher, holo locker, whatsapp, viber, maps, setcpu for profiles, button sevior,
callrecorder, incredicontrol, exdialer, ivona, facebook, tasker, jellyB live wallpaper) have 87 Mo free RAM and its still fast and snappier than ever thanks to ZRAM and dixperia2 tweeks
CIFS isn't enabled and still have insmod problems like in doomkernel , @wedgess could you enable it in next update plz !

[KERNEL][NEO/NEO-V] LuPuS-jBv8 [JB 4.1 & 4.2][LINARO 4.7.3][08-06-13]

LuPuS JellyBean 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"
}
Works for NEO & NEO-V ​
This kernel can be used on any JB CM BASED JB 4.1 or 4.2
After plenty of messages asking me to bring LuPuS to NEO-V, Finally got around to releasing it so......here it is Enjoy!!
Disclaimer
Code:
[COLOR="DarkOrchid"]#include[/COLOR] [COLOR="Magenta"]<std_disclaimer.h>[/COLOR]
[COLOR="Blue"]/*
* Your warranty is now void.. LOL I guess you knew it already.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, you getting dumped or you getting fired because your phone
* bootloops and alarm does not go off. Please do some research if you have any
* concerns about features included in my kernel before using it! YOU and only
* YOU are choosing to make these modifications.
*/[/COLOR]
[COLOR="Magenta"]#ifdef[/COLOR]
You have a [COLOR="DarkGreen"]question[/COLOR] post it in the [COLOR="DarkRed"]thread[/COLOR],
Instead of [COLOR="DarkGreen"]Pm'ing me[/COLOR], as other users may
experience you [COLOR="DarkRed"]problems[/COLOR]
[COLOR="Magenta"]#endif[/COLOR]
Included in Kernel
What Works --
Wifi - (flash modules)
Everything Else that works on FXP and any other JB kernel
Added Io-schedulers --
- Noop
- Anticipatory
- Deadline
- CFQ
- BFQ
- SIO
- ZEN
Added Governors --
- lagfree
- brazillianwax
- smoothass
- scary
- savagedzen
- smartass
- smartassv2
- smartassH3
- interactivex
- minmax
- + the 5or6 that are there with FXP
Lulzactive - Thanks to Tegrak
Based on Interactive and Smartass. When workload is greater than or equal to 60%, the governor scales up
CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step.
When screen is off, frequency is locked to global scaling minimum frequency
Virtuous
Virtuous is a modded smartassV2 which gives even more battery time then smartassV2
Intellidemand - Thanks to faux123
This is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling,
and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such.
Intellidemand does not jump to highest frequency when screen is off.
Lazy - Thanks to Ezekeel
The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand.
Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state
on a step overriding sampling interval.
Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always
select the maximum frequency while the screen is off.
-Ondemandx:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
-Lionheart:
Is a conservative-based governor. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
To 'experience' Lionheart using conservative, try these tweaks:
sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe).
up_threshold:60
down_threshold:30
freq_step:5
Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
BadAss Governor:
Badass removes all of this "fast peaking" to the max frequency. Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1024Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.
Superbad -
A "superbad" super smooth rendition of a highly optimized "smartass" governor!
Darkside -
A "slightly more agressive smart" optimized governor!
What else-----
-SLQB - (SLAB allocator with Queue)-(both)
This memory allocator is designed for small number of CPUs system (such as desktop or smart phone devices). This allocator is design to be simple and it is optimized for using order-0 pages as much as possible (order-0 pages are the simplest therefore quickest type of memory in a Linux system to allocate).
- Added Cleancache
- Updated zRam
- Lzo compression/decompression speed doubled on average
LuPuS MENU
You can run lupus menu from terminal or scriptmanager or similar, you must run as root or script will exit with a message
in terminal
Code:
su
lupus
* information is in lupus menu
1/ CIFS Menu *
Enable
Disable
2/ zRam Menu *
Enable
Disable
Set zRam size ( default is 60)
3/ Frandom Menu *
Enable
Disable
4/ USB OTG *
Enable
Disable
5/ Clean and Remove tweaks
Remove init.d's
6/ Tweak Menu
Note all tweaks are preset from here and option to set as init.d's
Clean all temp files
SQLITE optimizations
LMK Optimizations
Network optimizations
Defend against ARP spoofing
Remove android logger
SDcard speed tweak
Flag blocks as non-rotational
7/ Performance Menu
Note all options are se by user input from here and option to set as init.d's
Set CPU frequencies
Set Governor
Set IO-Scheduler
Voltage Control
VM tweaks (explained below)
VM Tweaks
dirty ratio and dirty background ratio 1 & 2
This controls how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
dirty_expire_centisecs
How old "dirty" data should be before the kernel considers it old enough to be written to disk. It is expressed in 100ths of a second.
dirty_writeback_centisecs
This is the interval of when the writeback daemons periodically wake up and write "old" data out to disk. It is expressed in 100ths of a second.
min free kbytes
This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
overcommit_memory
This controls overcommit of system memory, possibly allowing processes to allocate (but not use) more memory than is actually available.
0 - Heuristic overcommit handling. Obvious overcommits of address space are refused. Used for a typical system. It ensures a seriously wild allocation fails while allowing overcommit to reduce swap usage. root is allowed to allocate slighly more memory in this mode. This is the default.
1 - Always overcommit. Appropriate for some scientific applications.
2 - Don't overcommit. The total address space commit for the system is not permitted to exceed swap plus a configurable percentage (default is 50) of physical RAM. Depending on the percentage you use, in most situations this means a process will not be killed while attempting to use already-allocated memory but will receive errors on memory allocation as appropriate.
Swappiness
A property for the Linux kernel that changes the balance between swapping out runtime memory, as opposed to dropping pages from the system page cache. Swappiness can be set to values between 0 and 100 inclusive. A low value means the kernel will try to avoid swapping as much as possible where a higher value instead will make the kernel aggressively try to use swap space.
VFS Cache Pressure
File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
I would like to say a big thanks to -
FXP - J - Sources
DooMLoRD -for everything on xperia's
rakmth - For helping me test
Paul678
tempest918 - For the New Logo
CosmicDan
xeozus
NobodyAtAll
Faux123
Erasmus
Leedroid
Jerpelea
Phil3759
CTCaer
Anyone missing please PM me
Github Sources -b jellybean
https://github.com/garwedgess/semc-kernel-msm7x30
CWM source -- https://github.com/garwedgess/android_bootable_recovery -b lupus-cwm
Kernel feautures / Changelog
Code:
[hide]
[B][U]v1[/U][/B]
- All the above features plus++
- Added Governor Intellidemand2 thanks to faux123 and CosmicDan for modifying it
- Variuos improvements to make for smoother android
- built with linaro v 4.7
- Changed recovery entering will now flash green, pink and blue (PACman colours :) )
- cleancache , zram, and new lzo compression have been reverted for now
- Completely scrapped previous source and cleaned alot of code ect.
- Increased VM-max read ahead
- Updated GENLOCK
- Added cleancache
- Enabled CIFS FUSE& NTFS (Need to flash modules)
- Fixed battery dran - (for me 0.2% battery drain per hour overnight with wifi on ):victory:
- Updated SIO IO-schedule
- Reverted 2ghz to 1.6ghz
- Updated LZO compression / Decompression
- Further optimzed
- Recovery Fixed no more "DANCING" Thanks [user=3365554]@Skrit[/user]chz
- Added Tiny RCU
- Patched LZO
- Updated to Linaro 4.7 toolchain lots of custom changes
- Changed to Google snappy compression/decompression
- Much more optimizations
- 0% Battery patch ~ Thanks " Bazoocaze
- Uses uncompressed Image
- Uses Thumbee
- Wifi signal and lock-on Increased
[B][U]
v2[/U][/B]
- Improved CIFS support
- Enabled USB tether
- Disabled gentle_fair_sleepers
- Updated video drivers
- Clean up on wifi config
- Added memcopy
- Added compaction
- Back-ported binder changes
- Lowered vfs_cache_pressure
- LMK (lowmemorykiller) optimizations
- Latest CM Ramdisk changes
[B][U]v3[/U][/B]
- Built with Linaro 4.7.3 (02-01-2013)
- Free'd RAM (disabled 720p) now 381mb - Thanks at Paul678
- Makefile optimisations (snapdragon & neon) - Thanks at Paul678
- Tweaked permormance on interactive governor - Thanks at Paul678
- Tweaked SIO io sched - Thanks at Paul678
- Free'd some RAM from loggers
- Reduce swappiness
- Fix PageHead
- Fix binder. use of uninitialized variable.
- Fix kernel/net Memory Leaks
- Eliminate kstrdup memory leak
- ipv4: force_igmp_version ignored when a IGMPv3 query received
- Fix Entropy Depleting (no more depleting) - Thanks @ Kees Cook
- enable ipsec tunnel support in kernel (Latest FXP Change)
- ARM7 optimsations + more in config
- TWRP v2.4 - Thanks @ Championswimmer, TWRP Team and Wechy 77 for parts of his LuPuS theme
[B]**Probably missed out on a few things**[/B]
[B]v4[/B]
- Supports both 4.1 & 4.2 JB
- New IIO Scheduler ZEN thanks [user=2632235]@bbedward[/user]
- New Governor smartassH3 thanks [user=3057569]@Hero[/user]
- Tweaked Deadline IO scheduler
- Tweaked smartassv2
- Frandom
- SFB Net scheduler
- OC up to 1804.8MHz
- Logger backported from CAF
- Free RAM from logger
- LMK updated and optimized + various LMK tweaks
- Various ARM & RAM changes
- TinyRCU optimizations
- Optimized crc32 lib
- various VM changes
- Improved cleancache
- Undervolt LCD display, touch sensor proximity sensor & Wi-Fi thanks @ M66B
- Entropy tweaks
- Try fix for CRT animation [user=4266283]@paul678[/user]
- TWRP & CWM
- LuPuS Menu
- Auto Loading wifi
- All modules and init.d's included No need to flash anything after kernel
Plus alot more changes see [URL="https://github.com/garwedgess/semc-kernel-msm7x30/commits/jellybean"] for full list of credits and patches used[/URL]
[B]v5[/B]
- Latest changes to ALS and Button Backlight -- Thanks @ FXP
- Lowered OC to 1612.8Mhz
- Remove ALS and Button Backlight option from LuPuS Menu (no longer needed)
- Random reboots should be fixed ( for those who where having such issues )
[B]v6[/B]
- Fixed 3D from hanging under high intensity
- Fix pmem for HDPI thanks ]mikeNG (no more reboots??)
- CWM Recovery = VOLUME DOWN
- TWRP Recovery = VOLUME UP
- Clean up on LuPuS Menu
- Better wifi check
- KEY RESET ( Menu and POWER)
- Tuned Smartassv3 and SmartassH3 [user=2799345]@M66B[/user]
[B]v7[/B]
- Fixed reboot to recovery
---- Custom CWM
- Clean-up of menu
- Added own wipe options menu -- with extra options
- Aroma File Manager from CWM --- Must have aroma ([COLOR=Red]aromafm.zip) placed on root of sdcard[/COLOR])
- Multi zip installer
- Reboot options - Power off re-added under this menu
- Pointless but people keep asking me for it so re-added wipe battery stats also.
- LuPuS themed...
- Fixed "dancing android"
[/hide]
[B]v8[/B]
- Added option to enable Quick Key Reset (enable / disable via LuPuS Menu)
- Tuned Governors
* superbad
* lionheart
* virtuous
* darkside
* conservative
* smartassH3
- Really use google snappy zRam (improves zRam)
- Added zCache
- Removed persistent RAM
- Removed some more kernel debugging
- uninterruptible sleep
- Update SIO & CFQ
- Added Ultra-KSM
- Removed optimized AES & SHA1 routines
- Updated TWRP to 2.4.4
*Fixed Mount USB Storage in TWRP
- Updated CWM to latest Official CWM source
*Removed reboot options
*Re-added power off and reboot system now to main menu
- Improved wifi-loading scripts
- Clean up of lupus menu
- Fixed root issue on some devices
- Reworked kernel logs (can be found in /data/local/tmp)
- Boot.d - If phone is taking a long time to start move suspicious init.d scripts to /system/etc/boot.d
They will be run in background and won't affect boot time.
Downloads
If you like my work please consider buying me a beer or something else
by clicking the DONATE ME button, of course it isn't needed but greatly appreciated and keeps me motivated and shows your true appreciation for the time I have spent on my work and most importantly ENJOY!!
480p
LuPuS_haida_jBv8-ram.img
md5 = a0ae869597350756c9519748912f09d8
720p
LuPuS_haida_jBv8.1-full.img
md5 = 975815352d6facf6931b59dfe4af1208
Wifi is built in to kernels ramdisk NO MODULES NEEDED
Mirrors -- all LuPuS Kernels can be found here
www.goo.im/devs/wedgess
* Make sure your MD5 matches before reporting issues and please provide logcat/dmseg with any issues.
* NO ETA'S
* Help eachother out where you can
* Do not mirror my downloads[/B][/COLOR][/SIZE]
"- Recovery Fixed no more "DANCING" Thanks @skritchz" this one is not fixed. Still dancing :/
voyteckst said:
"- Recovery Fixed no more "DANCING" Thanks @skritchz" this one is not fixed. Still dancing :/
Click to expand...
Click to collapse
PM me ur gtalk and I can fix it. Just need someone to make sure its ok before release. Previous tester said it was fixed. As I dont have the device I cant tell for sure if it was fixed but as I said once someone pms me their gtalk ill fix it
Sent from my GT-I9300 On Official JB
thanks but no kernel foe CM10.1 test version??
wedgess said:
PM me ur gtalk and I can fix it. Just need someone to make sure its ok before release. Previous tester said it was fixed. As I dont have the device I cant tell for sure if it was fixed but as I said once someone pms me their gtalk ill fix it
Sent from my GT-I9300 On Official JB
Click to expand...
Click to collapse
Ok, sent.
Ok recovery now fixed OP updated with fixed recovery
Thanks @ voyteckst for testing
wedgess said:
Ok recovery now fixed OP updated with fixed recovery
Thanks @ voyteckst for testing
Click to expand...
Click to collapse
No problem.
So far it's working good (still charging). No restart when watching Youtube.Many governors to choose (which one is the best ). I'm using CM10 150 with this kernel and it's smooth. Still charging, so I'll inform how's battery performance (using sio/virtuoz/1,4GHz max). Seems to be faster (in tests) than other kernels for 4.1.
can we have support for mouse+keyboard n other perpherials...lyk there is support in night elf 1.5..n also can we get support for multiboot
Sent from my MT11i using xda premium
One of the best kernel I've tried for JB
Thanks to @wedgess, I've been using the kernel since yesterday. My phone now works smoothly!! Battery backup has improved significantly. Video playback and youtube working fine now. No random reboots (like fusion kernel). I guess we've got ourselves the best kernel here.
Thank you @wedgess
Can We Have multiboot....................
thanks.................
your work is great as always :fingers-crossed:
Can i use this kernel for cm 10.1 ???
Sent from my Xperia Neo V using xda app-developers app
vineet.patel said:
Can i use this kernel for cm 10.1 ???
Sent from my Xperia Neo V using xda app-developers app
Click to expand...
Click to collapse
No..it is only for cm10
cm 10 runs lyk butter....thanxx wedgess for ur hard work
Sent from my Xperia Neo V using xda premium
Thank you very much for the great kernel
one bug though is that the key backlight problem is back again
bambotcha said:
Thank you very much for the great kernel
one bug though is that the key backlight problem is back again
Click to expand...
Click to collapse
pls fix this wedgess
Sent from my Xperia Neo V using xda premium
after flash modules WiFi still not working
Edit: i solve problem thanks
Why don't you post this to Xperia Neo Development section(not V)? Because CM10 thread is in there so that everybody can see your work
Sent from my Xperia Neo using xda app-developers app
Finally a perfect kernel
Thanks you a lot for this kernel, I flashed it in my Neo (MT15i) and it solves all the problems, now no reboot on video apps (youtube, MX, etc.). Smartass v2 is the best governor for my device, it manages ram perfectly.
+1 to vinhpz0, in CM10 thread has at least 10 pages with kernel issues, and yours is the best kernel for CM10 (in my opinion) and should be in Neo thread.
My configuration: CM10 (FXP150), Lupus Kernel, Smartassv2, 364~1401, no zram
And it's awesome the smoothness, no lags, no random reboots, all works perfectly, thanks
would be better if button light is fixed like the PAC-man one does.

[KERNEL][ALL MDPI][JB 4.1 & 4.2] LuPuS-jBv8 [LINARO 4.7.3][06-06-13]

LuPuS-JB-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"
}
Built with Linaro
This kernel can be used on any JB CM BASED JB 4.1 or 4.2
Disclaimer
Code:
[COLOR="DarkOrchid"]#include[/COLOR] [COLOR="Magenta"]<std_disclaimer.h>[/COLOR]
[COLOR="Blue"]/*
* Your warranty is now void.. LOL I guess you knew it already.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, you getting dumped or you getting fired because your phone
* bootloops and alarm does not go off. Please do some research if you have any
* concerns about features included in my kernel before using it! YOU and only
* YOU are choosing to make these modifications.
*/[/COLOR]
[COLOR="Magenta"]#ifdef[/COLOR]
You have a [COLOR="DarkGreen"]question[/COLOR] post it in the [COLOR="DarkRed"]thread[/COLOR],
Instead of [COLOR="DarkGreen"]Pm'ing me[/COLOR], as other users may
experience you [COLOR="DarkRed"]problems[/COLOR]
[COLOR="Magenta"]#endif[/COLOR]
What Works --
Wifi - (flash modules)
Data
Everything Else that works on FXP
What doesn't work --
Anything that doesn't work on FXP
Whats Included in kernel ------------
Added Governors --
brazillianwax
smartass
Smartassv2
Savagedzen
Smoothass
Scary
InteractiveX
Minmax
Userspace
Intellidemand - Thanks to faux123
This is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling,
and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such.
Intellidemand does not jump to highest frequency when screen is off.
Lazy - Thanks to Ezekeel
The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand.
Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state
on a step overriding sampling interval.
Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always
select the maximum frequency while the screen is off.
Lulzactive - Thanks to Tegrak
Based on Interactive and Smartass. When workload is greater than or equal to 60%, the governor scales up
CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step.
When screen is off, frequency is locked to global scaling minimum frequency
- Superbad
- a "superbad" super smooth rendition of a highly optimized "smartass" governor!
- Darkside
- a "slightly more agressive smart" optimized governor!
-Ondemandx:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
-Lionheart:
Is a conservative-based governor. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
To 'experience' Lionheart using conservative, try these tweaks:
sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe).
up_threshold:60
down_threshold:30
freq_step:5
Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
BadAss Governor:
Badass removes all of this "fast peaking" to the max frequency. Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1024Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.
-Virtuous
Virtuous is a modded smartassV2 which gives even more battery time then smartassV2
Added Io-scheduler --
VR io-scheduler - Unlike other schedulers, synchronous and asynchronous requests are not treated separately,
instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.
- SIO - Simple IO-Scheduler-
SIO is the default scheduler in this kernel. It is widely-regarded as the best all-round performing IO scheduler for android. It is low on CPU usage and optimized for flash-based storage. From the creator - "Based on Noop, Deadline and V(R) IO schedulers. This algorithm does not do any kind of sorting, as it is aimed for aleatory access devices, but it does some basic merging. We try to keep minimum overhead to achieve low latencies. Asynchronous and synchronous requests are not treated separately, but we rely on deadlines to ensure fairness."
- BFQ - Budget Fair Queueing IO-Scheduler-
From Creators
* Copyright (C) 2008 Fabio Checconi
* Paolo Valente
*
* Licensed under the GPL-2 as detailed in the accompanying COPYING.BFQ file.
*
* BFQ is a proportional share disk scheduling algorithm based on the
* slice-by-slice service scheme of CFQ. But BFQ assigns budgets,
* measured in number of sectors, to tasks instead of time slices.
* The disk is not granted to the active task for a given time slice,
* but until it has exahusted its assigned budget. This change from
* the time to the service domain allows BFQ to distribute the disk
* bandwidth among tasks as desired, without any distortion due to
* ZBR, workload fluctuations or other factors. BFQ uses an ad hoc
* internal scheduler, called B-WF2Q+, to schedule tasks according to
* their budgets. Thanks to this accurate scheduler, BFQ can afford
* to assign high budgets to disk-bound non-seeky tasks (to boost the
* throughput), and yet guarantee low latencies to interactive and
* soft real-time applications.
Click to expand...
Click to collapse
I would like to say a big thanks to -
FXP / Cyanogenmod - Sources
tempest918 - For the New Logo
DooMLoRD - for patches and all the work he has done for Xpeeria's
xeozus
NobodyAtAll
Faux123
Erasmus
Leedroid
Jerpelea
Phil3759
CTCaer
Anyone missing please PM me
Kernel sources -b jellybean
https://github.com/garwedgess/semc-kernel-msm7x30
CWM source -- https://github.com/garwedgess/android_bootable_recovery -b lupus-cwm
Changelog
Code:
[hide]
[LIST]
[*]- All above Governors
- All above Io-Schedulers
- Cleancache
- KSM
- CIFS
- USB-OTG
- NTFS
- ext 2/3/4
- VDD ( Custom voltage control )
- Tiny RCU
- SLQB Memory Allocator
- Increased VM max readahead
- Wifi problem fixed
- Fixed Battery drain ( Tester lost 0.2% overnigh with wifi on ) :victory:
- CWM fixed thanks @ Scritch007
- Built with Linaro 4.7
- Optimized for Linaro
- Thumbee
- OC upto 1.6
- Lzo updated & patched
- Use Google Snappy Compression / Decompression
- Added TINY RCU
- Uses uncompressed Image {why .img size is bigger)
- Custom improvements for overall smoother performance
*** Probably a whole lot more i'm missing ***
[B][U]v2[/U][/B]
- built with latest linaro 4.7.3 (02-01-2013) - Thanks @ ChainFirex
- Added memcopy
- Added compaction
- Lowered vfs_cache_pressure
- LMK (lowmemorykiller) optimizations
- Improved CIFS support
- Enabled USB tether
- Disabled gentle_fair_sleepers
- Updated video drivers
- Clean up on wifi config
- Back-ported binder changes
- Dual recovery thanks @ singh_dd93
- TWRP recovery - thanks @ championswimmer & TWRP team
- reverted back to compressed zImage
[B][U]v3[/U][/B]
- Built with Linaro 4.7.3 (02-01-2013)
- Free'd RAM (disabled 720p) now 381mb - Thanks at Paul678
- Makefile optimisations (snapdragon & neon) - Thanks at Paul678
- Tweaked permormance on interactive governor - Thanks at Paul678
- Tweaked SIO io sched - Thanks at Paul678
- USB Tether support
- Free'd some RAM from loggers
- Buggy ALS Disabled at kernel level
- Reduce swappiness
- Fix PageHead
- Fix binder. use of uninitialized variable.
- Fix kernel/net Memory Leaks
- Eliminate kstrdup memory leak
- ipv4: force_igmp_version ignored when a IGMPv3 query received
- Fix Entropy Depleting (no more depleting) - Thanks @ Kees Cook
- enable ipsec tunnel support in kernel (Latest FXP Change)
- ARM7 optimsations + more in config
- TWRP v2.4 - Thanks @ Championswimmer, TWRP Team and Wechy 77 for parts of his LuPuS theme
[B]v4[/B]
- Supports both 4.1 & 4.2 JB
- New IIO Scheduler ZEN thanks @[URL="http://forum.xda-developers.com/member.php?u=2632235"]bbedward[/URL]
- New Governor smartassH3 thanks @[URL="http://forum.xda-developers.com/member.php?u=3057569"]Hero[/URL]
- Tweaked Deadline IO scheduler
- Tweaked smartassv2
- Frandom
- SFB Net scheduler
- OC up to 1804.8MHz
- Logger backported from CAF
- Free RAM from logger
- LMK updated and optimized + various LMK tweaks
- Various ARM & RAM changes
- TinyRCU optimizations
- Optimized crc32 lib
- various VM changes
- Improved cleancache
- Undervolt LCD display, touch sensor proximity sensor & Wi-Fi thanks @ M66B
- Entropy tweaks
- Try fix for CRT animation @[URL="http://forum.xda-developers.com/member.php?u=4266283"]paul678[/URL]
- TWRP & CWM
- LuPuS Menu
- Auto Loading wifi
- Performance governor tweak
- All modules and init.d's included No need to flash anything after kernel
Plus alot more changes see [URL="https://github.com/garwedgess/semc-kernel-msm7x30/commits/jellybean"] for full list of credits and patches used[/URL]
[/LIST]
[B]v5[/B]
- Latest changes to ALS and Button Backlight -- Thanks @ FXP
- Lowered OC to 1612.8Mhz
- Remove ALS and Button Backlight option from LuPuS Menu (no longer needed)
- Random reboots should be fixed ( for those who where having such issues )
[B]v6[/B]
- Fixed 3D from hanging under high intensity
- Fix pmem for HDPI Mike NG (no more reboots??)
- CWM Recovery = VOLUME DOWN
- TWRP Recovery = VOLUME UP
- Clean up on LuPuS Menu
- Better wifi check
- KEY RESET ( Menu and POWER)
- Tuned Smartassv3 and SmartassH3 @[URL="http://forum.xda-developers.com/member.php?u=2799345"]M66B[/URL]
[B]v7[/B]
- Compatable with MIUI5
---- Custom CWM
- Clean-up of menu
- Added own wipe options menu -- with extra options
- Aroma File Manager from CWM --- Must have aroma ([COLOR=Red]aromafm.zip) placed on root of sdcard[/COLOR])
- Multi zip installer
- Reboot options - Power off re-added under this menu
- Pointless but people keep asking me for it so re-added wipe battery stats also.
- LuPuS themed...
[/hide]
[B]v8[/B]
- Added option to enable Quick Key Reset (enable / disable via LuPuS Menu)
- Tuned Governors
* superbad
* lionheart
* virtuous
* darkside
* conservative
* smartassH3
- Really use google snappy zRam (improves zRam)
- Added zCache
- Removed persistent RAM
- Removed some more kernel debugging
- uninterruptible sleep
- Update SIO & CFQ
- Added Ultra-KSM
- Removed optimized AES & SHA1 routines
- Updated TWRP to 2.4.4
*Fixed Mount USB Storage in TWRP
- Updated CWM to latest Official CWM source
*Removed reboot options
*Re-added power off and reboot system now to main menu
- Improved wifi-loading scripts
- Clean up of lupus menu
- Fixed root issue on some devices
- Reworked kernel logs (can be found in /data/local/tmp)
- Boot.d - If phone is taking a long time to start move suspicious init.d scripts to /system/etc/boot.d
They will be run in background and won't affect boot time.
LuPuS MENU
You can run lupus menu from terminal or scriptmanager or similar, you must run as root or script will exit with a message
in terminal
Code:
su
lupus
* information is in lupus menu
1/ CIFS Menu *
Enable
Disable
2/ zRam Menu *
Enable
Disable
Set zRam size ( default is 60)
3/ Frandom Menu *
Enable
Disable
4/ USB OTG *
Enable
Disable
5/ ALS & Button Backlight *
Enable
Disable
- BOTH
5/ Clean and Remove tweaks
Remove init.d's
6/ Tweak Menu
Note all tweaks are preset from here and option to set as init.d's
Clean all temp files
SQLITE optimizations
LMK Optimizations
Network optimizations
Defend against ARP spoofing
Remove android logger
SDcard speed tweak
Flag blocks as non-rotational
7/ Performance Menu
Note all options are se by user input from here and option to set as init.d's
Set CPU frequencies
Set Governor
Set IO-Scheduler
Voltage Control
VM tweaks (explained below)
VM Tweaks
dirty ratio and dirty background ratio 1 & 2
This controls how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
dirty_expire_centisecs
How old "dirty" data should be before the kernel considers it old enough to be written to disk. It is expressed in 100ths of a second.
dirty_writeback_centisecs
This is the interval of when the writeback daemons periodically wake up and write "old" data out to disk. It is expressed in 100ths of a second.
min free kbytes
This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
overcommit_memory
This controls overcommit of system memory, possibly allowing processes to allocate (but not use) more memory than is actually available.
0 - Heuristic overcommit handling. Obvious overcommits of address space are refused. Used for a typical system. It ensures a seriously wild allocation fails while allowing overcommit to reduce swap usage. root is allowed to allocate slighly more memory in this mode. This is the default.
1 - Always overcommit. Appropriate for some scientific applications.
2 - Don't overcommit. The total address space commit for the system is not permitted to exceed swap plus a configurable percentage (default is 50) of physical RAM. Depending on the percentage you use, in most situations this means a process will not be killed while attempting to use already-allocated memory but will receive errors on memory allocation as appropriate.
Swappiness
A property for the Linux kernel that changes the balance between swapping out runtime memory, as opposed to dropping pages from the system page cache. Swappiness can be set to values between 0 and 100 inclusive. A low value means the kernel will try to avoid swapping as much as possible where a higher value instead will make the kernel aggressively try to use swap space.
VFS Cache Pressure
File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
Downloads
If you like my work please consider buying me a beer or something else
by clicking the DONATE ME button, of course it isn't needed but greatly appreciated and keeps me motivated.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
LuPuS-jB Kernel Downloads
480p
LuPuS_coconut_jBv8-ram.img
md5 = 9d3e68a798a5c1cd27fc878fcfbf3bb9
LuPuS_mango_jBv8-ram.img
md5 = 393cddbadc066bf8a001f9ccbbd1d4e0
LuPuS_satsuma_jBv8-ram.img
md5 = 26af5b64810ef5206ba475eddcf74f13
LuPuS_smultron_jBv8-ram.img
md5 = e569c6a20e82f627290907abf605664d
720p
LuPuS_coconut_jBv8-full.img
md5 = 9d384782278e4f87bee1d4f4a02d5dce
LuPuS_mango_jBv8-full.img
md5 = d76c866a8014c286a923f736fabf2d32
LuPuS_satsuma_jBv8-full.img
md5 = 2275a655cf0f0f4a0da145ff3682e3c3
LuPuS_smultron_jBv8-full.img
md5 = cd7429c95ea930379d94f89cbd58fef9
Wifi is built in to kernels ramdisk NO MODULES NEEDED
LuPuS Kernel folder
http://goo.im/devs/wedgess
DO NOT MIRROR MY DOWNLOADS
- zRam is not enabled by default unless on CM10 ROM, for AOKP to enable it flash the wedgess-zram-enabler.zip in CWM
- If for whatever reason you want to disable Zram after you have flashed the .zip, just go to ect/init.d and delete 00zram
People will ask so i'll just post it here---------to check if zRam is enabled go to terminal emulator or similar and type
Code:
free
or alternatively
Code:
cat /proc/swaps
Also added CIFS support....
What is CIFS???
Server Message Block (SMB) or Common Internet File System (CIFS) are normally used to provide shared access to files on a network, mostly involving computers running MS Windows.
It allows you to conveniently mount/unmount your network accessible file resources and access the files transparently via your favourite Android app (playing music / videos, accessing documents etc.) Settings are stored on your SD card with permissions to write also to your SD card.
Now download CifsManager or similar app and configure it
Please Click Thanks :good:
Phone wont even show the boot logo after flashing this kernel.
Phone wont even boot up.
Hold the power button,phone vibrates (normal) and after 5 seconds,i hold the power button and it vibrates again .
Whyyyyyyy? :crying:
shadik555 said:
Phone wont even show the boot logo after flashing this kernel.
Phone wont even boot up.
Hold the power button,phone vibrates (normal) and after 5 seconds,i hold the power button and it vibrates again .
Whyyyyyyy? :crying:
Click to expand...
Click to collapse
Probably because it's only been tested on mango as I couldnt fnd tseters for all devices, so if it doesnt work post ur device and ill re upload
EDIT - Oh wait you are using mango, does your md5 match the one in post #2
can I enable z ram on cm10 by going to setting/performance/ z ram on this kernel?
How is the kernel act on gaming(3d performance)?
Sent from my Xperia Mini using Tapatalk 2
I am using this kernel on PA and its too good. I would say a lot better than PA Kernel
Loving your work wedgess. THANKS ALOT
Sent from my Xperia Mini Pro using xda app-developers app
wedgess said:
Probably because it's only been tested on mango as I couldnt fnd tseters for all devices, so if it doesnt work post ur device and ill re upload
EDIT - Oh wait you are using mango, does your md5 match the one in post #2
Click to expand...
Click to collapse
Xperia mini st15i
scorpion 13 said:
can I enable z ram on cm10 by going to setting/performance/ z ram on this kernel?
How is the kernel act on gaming(3d performance)?
Sent from my Xperia Mini using Tapatalk 2
Click to expand...
Click to collapse
Ye most ROMs it should be grand with but some you may need to flash the .zip, just a back up type thingy
singh_dd93 said:
I am using this kernel on PA and its too good. I would say a lot better than PA Kernel
Loving your work wedgess. THANKS ALOT
Sent from my Xperia Mini Pro using xda app-developers app
Click to expand...
Click to collapse
Thanks glad you like and thanks for testing it out :good:
shadik555 said:
Xperia mini st15i
Click to expand...
Click to collapse
singh_dd93 tested MANGO and said all is fine, did u check the md5 it could of been a bad download
^^^^^^^^^^^^^^^^^^ Post of shame only know them by code name...............ooopppps
==========================================================================
AND PEOPLE PLEASE POST IF YOUR DEVICE BOOTED SO I CAN
________________________REMOVE UN-TESTED FROM OP____________________________​​
All kernels now booting​
wedgess said:
Ye most ROMs it should be grand with but some you may need to flash the .zip, just a back up type thingy
Thanks glad you like and thanks for testing it out :good:
singh_dd93 tested MANGO and said all is fine, did u check the md5 it could of been a bad download
Click to expand...
Click to collapse
@wedgess
Mango is SK17i
Xperia Mini ST15i is smultron
Sent from my Xperia Mini Pro using xda app-developers app
My device is smultron,not mango
thank you so much wedgess!!!!:thumbup:
Sent from my ST15i using xda premium
Phone doesn't boot, with M66B cm10 xtended rom for smultron.
mauam said:
Phone doesn't boot, with M66B cm10 xtended rom for smultron.
Click to expand...
Click to collapse
He is working on them atm. Fixed uploads will be available soon
Sent from my Xperia Mini Pro using xda app-developers app
All Kernels fixed, booting and links updated in OP
Thanks to the testers :highfive:
it's just awesome
tnx a lot wedgess
Ok, am trying it, the performance is 5% smaller than that of M66B kernel, battery life need to test further, will see tomorrow and post results. Thanks a lot to wedges and welcome to the forum .
One request i would have though: Could you add the 24 MHz frequency its wonderful for battery life, and in combination with smartassV2 it doesn't compromise performance at all.
Long rebooting (stuck) from Power Menus, I need to press Camera Key to continue
Normally reboot if I execute it from Terminal
^^^ that is a known bug.
The performance (on gaming)is lower than Fxp kernel (only a bit)
But battery saving is very good.
Sent from my Xperia mini on Jellybean
scorpion 13 said:
The performance (on gaming)is lower than Fxp kernel (only a bit)
But battery saving is very good.
Sent from my Xperia mini on Jellybean
Click to expand...
Click to collapse
Please Note this version is to see how many people will be using it ect. Next release has more improvements. What governors ect u use. Even though I dont go by antutu score mines above fxps, using intellidemand2
Sent from my GT-I9300 On Official JB

[KERNEL][ICS] ** CTCaer Kernel ** v2.8.2 [UKSM][UV/OC][Triple Buffering][RAM Hacks]

CTCaer Kernel ICS version v2.8.2
*Light. Fast. Triple Buffering. More Total Ram. Entropy*
{
"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"
}
Updated: 8 September 2013
Features:
Based on Lupus kernel .587/.13 sources
Compiled with Linaro 4.7.3
CWM by DoomLord
Works with stock wifi modules
Overclock to safe 1.4 GHz with Qualcomm's frequencies for less battery drain (max is 1.6Ghz)
Deep undervolting with aire's values
15MB more total ram
Triple Buffering like jellybean
Auto rooting with latest superuser 3.2 binaries
Init.d support (fixed double triggering, even when using install-recovery.sh method)
Dual Recovery. TWRP (volume keys), CWM (power key)
Kernel/Memory Optimizations:
UKSM (saves 20-65mb ram)
Optimised Low Memory Killer
Random Entropy generator fixes and tweaks
frandom + replaced random/urandom with frandom/erandom
Compaction for LMK
Better Memcopy/Memove
Tiny RCU for smaller memory footprint
CPU group schedulling
Cleancache
Better pmem
Kernel Samepage Merging (Can't be used in the end)
Optimized and faster Swap and Zram
Thumbee support
ARMv7a optimizations
lowered vfs cache pressure
Optimized cpufreq/governors
And more tweaks for a smoother and faster Kernel
Script to clean unused ramdisk files after boot, to free up ram (9mb)
File systems:
ntfs, ext2/3/4, filesystems support
jbd2 journaling for ext fs
CIFS, FUSE and Usb OTG Storage
512KB SD read ahead (faster reads without hogging the cpu and ram)
sd-ext support
Other:
Updated LZO
2 way call recording
Google's Snappy Compression and Decompression
Better WiFi range and enabled channel 14
0% battery patch by Bazoocaze
Working ADB and usb in Recovery, plus rooted shell
Usb network tethering
Key reset
Governor Schedulers :
Ondemandx
Performance
SmartassV2 (tweaked+fixed scheduling) [Default]
Superbad (tweaked)
lulzactiveV2
Badass
IO Schedulers :
Noop
SIO [Default]
ROW (experimental)
BFQ
CFQ
deadline
For more, check changelogs from post 2.
Info about some mods:
1.4Ghz Overclock + UV. Kept Qualcomm's frequencies table as proved to have less battery drain for some reason.
The undervoltaging is max -50mV on most frequencies, as to avoid error corrections from low voltage (errors in calculations increases drain a lot) and also to avoid cpu halts. Needs further investigating for lower values.
Now using aire's values, the best for battery for over a year.
11mb ram freed from camera and adsp pmem. This came from many tests that showed that when taking 8mp pictures, 720p video (w/ or w/o stabilizer), playing 720p video with hw decoding and hw audio decoding audio, the used pmem was max 42MB for camera pmem and 6MB for adsp. Can be freed 7-8Mb more but didnt do it for stability reasons under multimedia multitasking.
That also shows us that the stabilizer lag in camera doesn't come from the pmems. I'll try to check the camera sources and see if it's driver related.
If you find anything strange with anything that use the camera or the DSP tell me and please provide logcat logs.
Triple Buffering. At last some JB goodies to us using stock. This gives great UI and game Frame rates (tested). It uses the normal mode (as we don't have the vsync sync pulse like JB, which also auto disables it when not needed), and that means that it doesn't introduces slight lag to input. In games if you see something strange though please reply in this thread.
Random Entropy Generator. Fixes and tweaks to random generator. And also to binfmt_elf, no more entropy depletion through using shell, scripts and generally any binary. Say no to blocking random, and enjoy a smoother UI.
Now with frandom for 50x more performance.
Governors/IO scheds. No bloating here. Kept only the best for battery and performance.
The default ones are the highly optimized. If you have some tweaks for all schedulers that will increase battery and performance (always in balance), don't hesitate to tell me.
Key reset. You can reboot your phone when kernel halts or something brought your phone to its knees by pressing
Power + Home for 5s. Don't do it just for restarting it fast! This does not good to your filesystem because they can't sync,
so you can lose changes made the last seconds. Also after initiating it you don't have to press both buttons for the remaining 4s.
In 2.8 the combination is Power + Home + Volume Up for 5s.
Twrp and Cwm differences. TWRP and CWM are both recovery apps but use different apis.
CWM use nandroid backup and TWRP uses it's own.
CWM uses and old recovery API (v2) and TWRP use the newest recovery API 3
That means that you can't use a backup made with cwm in twrp, and vice versa.
In TWRP, some flashable zip will not work, until they have a newer update-binary (that supports API 3).
(That's the one provided by Team Win: update-binary-3)
If you want other info, again write here. And last but not least the kernel version number 0.8a doesn't mean that's beta. The kernel right now is highly optimized and working. The version just means that I'll try many things more to make our phone better.
Thanks:
wedgess for his great Lupus kernel sources.
aire and vdsirotkin for their great kernels that i used for many months at both GB and ICS.
DooMLoRD Well you all know why
thomas1991_12 and championswimmer for help and twrp binary accordingly
And to all Freexperia Project members for their great patches and fixes to our phones.
Changelogs
Click the link to view the changelogs or go directly to post 2
DISCLAIMER for sharing outside xda:
It got to my attention that the kernel is shared in many boards outside xda
and especially in many Asian ones. It's fine to make a complete copy of OP and changelog,
I don't mind, but you have to provide a link to this thread.
Also, the most important, please use my links for kernel binaries. If you don't do this, I can't see usage stats of my kernel.
That's why I use mediafire. It's fast, supports multiple connections, no wait time and is usable in every country.
Downloads and Sources:
Main Version:
CTCaer Kernel v2.8 1.4GHz + UV
or
CTCaer Kernel 2.8.2 UKSM special version
The special version may not work for you, cause of lower voltages. After 20 sept, i'll do proper releases.
Vdd Version:
DISCLAIMER: I will not provide help on reboots and bootloops on 1.6GHz + VDD control version.
It's here for people that need 1.6ghz and voltage control only. Default speed is 1.0Ghz.
CTCaer Kernel v2.8 1.6GHz + VDD control
If you want to use usb storage, ntfs and more you can flash these modules (if not, they are optional):
Modules for CIFS, NTFS, FUSE and USB Storage v2 ** Updated **
The updated modules bring: Updated cifs,fuse,ntfs,usb-storage and adds nls_utf8 for Unicode support, plus oprofile for people that want debugging.
CTCaer Kernel needs stock wifi modules. If you changed them, flash this:
Stock .13 WiFi modules
If you came from a kernel that you had to flash custom modules, use the flash zip above to have the stock ones again.
Some kernels, like Lupus, change the modules on their own, by just flashing the kernel and powering on the phone.
The original with Lupus are moved in /system/lib/modules.old.
Info for going back from Lupus
Many thanks @arcatarc for providing the flashable update zip.
Old Versions:
CTCaer Kernel v2.7 1.4GHz + UV
CTCaer Kernel v2.7 1.6GHz + VDD control
CTCaer Kernel v2.6 1.4GHz + UV
CTCaer Kernel v2.6 1.6GHz + VDD control
CTCaer Kernel v2.52
CTCaer Kernel v2.51
CTCaer Kernel v2.5
CTCaer Kernel v2
CTCaer Kernel v0.8a
Modules for CIFS, NTFS, FUSE and USB Storage v1
And as per GPL here are the forked sources:
https://github.com/CTCaer/CTCaer-ICS-Xperia2011
For v2.7,2.8 check v2.8 branch, because currently, I don't have time to push commits one by one.
For compiling, I used Linaro 4.7.3 and ctcaer_urushi_defconfig (1.4GHz+UV) and ctcaerVDD_urushi_defconfig (1.6GHz+Vdd)
If you liked my kernel click THANKS!
Changelog:
Older:
v0.8a:
*Initial Release.
v0.9 (renamed to v2):
*Added 1.6Ghz (UVed)
*Removed Ondemand
*Added OndemandX cpu scheduler
*Added CFQ i/o scheduler
*Removed autoroot
*Changed ro.secure to 0 for rooted ADB on default
*More ram (because of ramdisk's reduced size)
*Fixed Kernel Samepage Merging startup.
*Reduced freq to 1Ghz for kernel booting (to avoid 1.6ghz's drain). Comes back to 1.4Ghz for at bootanimation.
*Some more ramdisk changes
v2.5:
*New logo. SE strikes back with energy logo
*Deep undervolting. Thanks to Intuki for providing aire's values
*Fixes to binfmt_elf. No more random entropy depleting through using cat, ls and well every binary and script.
*Random entropy generator tweaks. I scream more UI smoothness
*Enabled cpu group scheduling
*Better pmem (updated to 2.6.35.x. For full changelog: pmem patch)
*Removed unused modules and some non-usefull debugging for a lighter Kernel
*Fixes to memory leaks on the networking side
*Fixes to android binder
*Usb network tethering support
*Added ipsec tunneling support
*Fix to cpufreq. Now you can see available frequencies through /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
*Removed KSM because after so many days nothing in our phone calls it
*Tweaks to ramdisk for faster boot
v2.51:
*Reverted pmem code to stock to fix broken adsp for videos. Sorry about that :/
*Known bug on 2.50-.51: Unstable 1.6ghz because of low voltage.
v2.52:
*Added 1.5ghz and stabilised 1.6ghz more
*Changed PATH variable at boot end so busybox is not taken from /system/bin or xbin
*Increased 720p vidc default input buffer for smoother video playback
*Fix a race in pid generation that causes pids to be reusedimmediately
MIUI compatibility:
*Added MIUI shelld service (stock based roms are not affected by this), thanks to stillka
*Reverted binder patches
v2.6:
*Split kernel to 2 versions:
1.4GHz with Undevolting
1.6GHz with Vdd (voltage) control
*More Undervolting to lower frequencies for even better battery for main version. (3 days test showed 1% per 7hours with gsm+wifi on+widget updating every 1 hour)
*Stabilized higher frequencies.
*frandom implementation inside kernel. No need for module. It's 10-50 times faster than random/urandom
Replaced random and urandom with frandom and erandom. No need for apps to do that and it's done at boot so no app or process use the old ones.
(For ramdisk modders: the script is in /sbin/bootrec. You need it for frandom replacement before android boots.)
*Enabled bfq i/o scheduler cgroup
*Fixed PATH variable for good. Now it will report the right busybox in scripts and apps that can't use their own path.
*Tweaked cgroup values for background apps and more
*Enabled memory suspend deep power down. (This will do nothing for roms that can't use it, or without a script calling it)
*Enabled scheduler tunables (like sched_latency_ns, sched_wakeup_granularity_ns and more). Here's a good read about them: sysctl scheduler tunables
Tuning them will provide some more boost to your ray. Have in mind results are different from system to system and different workloads.
v2.7:
*Default scheduler is now SIO for nand and sd
*More total ram (4MB)
*Tweaks and fixes to msm_fb and mdp, for optimized and faster rendering plus less ram usage.
*Optimizations in memory management
*Updated LMK to the latest aprl-2013 version and added some tweaks
*Updated to a more optimized Compaction
*Optimizations to RCUTiny
*Optimized smartassv2 and added Boost pulse
*Added ROW scheduler, thanks to @kast
Experimental!
(Also some optimizations from the k3.4 version are missing for now)
Any benchmark on SIO vs ROW are welcomed.
*Performance optimisations on SIO and Deadline i/o schedulers
*Updated CFQ i/o scheduler
*Reordered functions in input driver for faster touch responce
*Removed Superbad and Lulzactive to lessen the kernel threads and free ram
*Kernel decompressor optimazations to Lzo
*Added Reset by pressing Power+Home keys for 5s
Only use it when you have to. (example: kernel halt) Don't make it your new reboot way!
*Made vibrator worqueue's priority higher to lessen the lag in big cpu load
*Added compact mem per node
*Fixed performance calculation in vidc (video codec)
*Enable Fsync
*Protect a proccess from killed by LMK far too many times
*Fix to suspend power management
*Fixed init.d support not working when having install-recovery.sh for int2ext and other scripts
*And more performance and memory optimizations..
v2.8:
Team Win Recovery Project is here
Dual ramdisk TWRP (volume keys) and CWM (power key)
For differences between TWRP and CWM check "Info about some mods" in OP
Made TWRP more holo, fixed reboot into TWRP and fixed mass storage in TWRP.
Added script to remove unused ramdisk files after boot to free ram
(cpio 7,8mb. Images/other 1.5mb)
Fixed init.d for every method for good
[/B]zram now really uses snappy compression/decompression
Really fast zram and no lag when switching apps
3rd button key reset: +Volume up.
No more random reboot from pressing the keys accidentaly
Use max freq for CSI (camera serial interface) -> new bandwidth: 250 MB/s (2000Mbps)
Use max freq for Jpeg encoding unit -> 147.4Mhz to 153.6Mhz
Faster jpg encoding
Added Badass governor
Rebased WiFi signal levels to more real-world limits
Kernel panic auto-restart 30s
Enable als at boot, to reduce battery drain and washed colors when booting
Increased Cpu freq to 1024mhz in recovery
Reduced default vm swappiness to 20
More silent binder
Suspend optimizations and bugfixes
Enabled Battery show health
Before it always showed GOOD. Now it can show GOOD, OVERHEAT, DEAD, OVERVOLTAGE, COLD
Yay! New kernel for ICS... Lemme' try it. downloading~
:good:
What's the min. frequency?
Csacsifiu said:
:good:
What's the min. frequency?
Click to expand...
Click to collapse
122 :good:
flashed it, and testing.
dreezz said:
122 :good:
flashed it, and testing.
Click to expand...
Click to collapse
Then i download it.
This kernel is Fast but I Think this would be a lot more faster of the OC would go up to 1.6Ghz even though its not Battery friendly
jrchan01 said:
This kernel is Fast but I Think this would be a lot more faster of the OC would go up to 1.6Ghz even though its not Battery friendly
Click to expand...
Click to collapse
I'll consider it. I'll maybe add one with 1.6ghz or with one capped at boot at 1.4ghz. Will see
How i wish their is interactiveX & CFQ. ehehe
From the features it seem a really good kernel(i like the fact it use stock wifi modules too),tnx,but i have some questions:
1)It is undervolt embedded in kernel?
2)Can you make a version without autoroot (or can i modify your ramdisk to use in my rom)?
Tnx in advance and keep the good workin..
Sweet candy, baby! Sounds AWESOME! Flaaaashing immediately! OMG, LOL!
Triple Buffering=project butter?
OK flashed, looks promising. I am on Zelly Cream and superuser doesn't start. What now?
EDIT: Cleaned dalvik, cache, fix permissions, cleared data on superuser app. SuperSU also not able to update binary. Sorry if it's a stupid situation.
CTCaer said:
I'll consider it. I'll maybe add one with 1.6ghz or with one capped at boot at 1.4ghz. Will see
Click to expand...
Click to collapse
Thank you
seems interesting
but i cannot access Mass Storage when my Ray on standby
now i'm using zelly cream as my ROM
back to old kernel for a while
R: [KERNEL][ICS] ***** CTCaer Kernel ***** [Linaro][UV/OC][Triple Buffering][RAM Hack
Abyssmal said:
OK flashed, looks promising. I am on Zelly Cream and superuser doesn't start. What now?
EDIT: Cleaned dalvik, cache, fix permissions, cleared data on superuser app. SuperSU also not able to update binary. Sorry if it's a stupid situation.
Click to expand...
Click to collapse
That's why i don't like autoroot,try deleting(if you can)superuser apk and bin,reboot...
Inviato da me!
PablooRupertooo said:
How i wish their is interactiveX & CFQ. ehehe
Click to expand...
Click to collapse
It was in my intentions to add CFQ but forgot to re add the kernel flag. Have in mind that cfq maybe is one of the most configurable io scheds but bfq does a better job in fairness (because it's an improved cfq).
As for interactiveX I'll review it.
arcatarc said:
From the features it seem a really good kernel(i like the fact it use stock wifi modules too),tnx,but i have some questions:
1)It is undervolt embedded in kernel?
2)Can you make a version without autoroot (or can i modify your ramdisk to use in my rom)?
Tnx in advance and keep the good workin..
Click to expand...
Click to collapse
1) Yep to avoid reboot problems. (even in stock voltages and configurable vdd for example, my ray reboots.)
I'm open though to suggestions about levels. In the next days I'll play a little with the current_now and try some new voltages until i find the
sweet spots before the error corrections begin. Also if for example 750mV has the same drain with 800mV I will keep the 800 one for stability. No need for extreme undervoltaging.
2)Well to be true I didnt wanted to included but many ppl need that feature from the kernel. If will remove it? Dont know yet.
But for sure you can edit the ramdisk. Just comment out the autoroot service in init.rc or delete the autoroot.sh in /sbin.
knightthgink said:
Triple Buffering=project butter?
Click to expand...
Click to collapse
Yep. Well almost. It's what the project butter is based off.
Until now (testing it for 8days) it does a good job and the UI feels a looot better.
Need some tests from games though. I heard that triple buffering made some glitches in xperia T JB. If it's kernel related maybe i can add the patch to our sources.
Abyssmal said:
OK flashed, looks promising. I am on Zelly Cream and superuser doesn't start. What now?
EDIT: Cleaned dalvik, cache, fix permissions, cleared data on superuser app. SuperSU also not able to update binary. Sorry if it's a stupid situation.
Click to expand...
Click to collapse
Well it's not. The superuser is the latest 3.2 and does not have update ability (the button that says update is cosmetic and version informative). The autoroot script is copying the superuser and the su. You are ready to go.
Also no need for wipes. If something doesn't work it has nothing to do with caches.
EDIT:-------
rushland said:
seems interesting
but i cannot access Mass Storage when my Ray on standby
now i'm using zelly cream as my ROM
back to old kernel for a while
Click to expand...
Click to collapse
Can you describe a little your situation?
When the screen is off and you connect the phone to pc the sd doesnt show up?
CTCaer said:
1) Yep to avoid reboot problems. (even in stock voltages and configurable vdd for example, my ray reboots.)
I'm open though to suggestions about levels. In the next days I'll play a little with the current_now and try some new voltages until i find the
sweet spots before the error corrections begin. Also if for example 750mV has the same drain with 800mV I will keep the 800 one for stability. No need for extreme undervoltaging.
2)Well to be true I didnt wanted to included but many ppl need that feature from the kernel. If will remove it? Dont know yet.
But for sure you can edit the ramdisk. Just comment out the autoroot service in init.rc or delete the autoroot.sh in /sbin.
Click to expand...
Click to collapse
Many tnxs,my friend.....i'm testing it(with modded ramdisk)for now it seems to be my next kernel....
-------------EDIT-----------:
If you want i can upload my modded version(No autoroot,No init.d support,basically stock optimized ramdisk+CWM)...
CTCaer said:
Well it's not. The superuser is the latest 3.2 and does not have update ability (the button that says update is cosmetic and version informative). The autoroot script is copying the superuser and the su. You are ready to go.
Also no need for wipes. If something doesn't work it has nothing to do with caches.
Click to expand...
Click to collapse
Superuser FC. SuperSU does not update. Disabled superuser, rebooted, enabled, rebooted and it's NOT working.
Abyssmal said:
Superuser FC. SuperSU does not update. Disabled superuser, rebooted, enabled, rebooted and it's NOT working.
Click to expand...
Click to collapse
Ok. Gonna remove mine too and test it again. Give me some minutes to figure out whats wrong.
Btw you all have problem with superuser?

[KERNEL][OOS 3.x.x/OldDroid's AOSP] Arsenic.Kernel-V10 (06/12/2016)

Hi Folks!
So here is the gift i was working on! Here I present you Arsenic.Kernel for Oxygen OS and OldDroid's AOSP. Rebased to new source released by OnePlus, Some features "might" be different from cm/aosp version starting with the new naming convention (changed from "release" to "version") for these builds.
Made this Separate thread for OOS builds for better user experience and easier debugging of reports.
If you are running a Custom Kernel already then plz CLEAN FLASH Oxygen OS before flashing Arsenic, official zip doesn't offer system wipe so dirty flash wont work, you gotta clean flash manually!
Zip doesn't offer any module changes and doesnt mess with the ramdisk so you can feel free to dirty flash it over Arsenic's previous versions( Dont forget to clear data of kernel adiutor or anyother kernel control app you're using before ).
Keeping op short and simple and with keeping New users in mind, here is a brief description about kernel:
Features:
Supports Oxygen OS and OldDroid's AOSP Only!
Built with Latest GCC 4.9 toolchain from Google.
Device and target flags enhancements and improvements, etc.
Kernel compressed with XZ.
Upstream CAF fixes and changes.
USB Fast Charge.
Switched to -O2 Optimization level.
Adreno idler. Nuked in OOS builds (as of now)
Lowered Min. GPU Frequency level to 27 Mhz.
Krait C-states customizations.
ExFat support.
Disabled Lots of useless Debuggings and Redundant Code.
New Governors and I/O Schedulers.
Optimized compression.
Various Upstream backports.
SOC Driver Tuneables.
Enabled Arch Power.
Optimized RWSEM Algorithm.
FiiO USB DAC driver for better input detection
Options to disable various wakelocks.(Use them wisely!)
TCP Congestion algos (like westwood,cubic etc).
CPU Input Boost.
Voltage Control.
Various under the hood Battery and performance improvement patches(Advance users can look at my git, each commit is there with proper explaination).
Stability and Battery backup at its Peak!
Available Govs: conservative, impulse, interactive, ondemand, performance, powersave, smartmax, userspace, wheatley, yankactive, zzmoove.
Available I/O Scheds: row, bfq, fiops, noop, cfq, ZEN, Tripndroid.
Keep an eye on the changelog for more/newly add features as this list wont be updated regularly so either have a look on Changelog or just flash Arsenic and explore yourself..!
Download links:
OOS Compatible Builds :https://www.androidfilehost.com/?w=files&flid=125615
Mirror (basketbuild) : https://basketbuild.com/devs/CheckYourScreen/arsenic/onyx_oos
@OldDroid's AOSP Compatible Builds : https://www.androidfilehost.com/?w=files&flid=132260
Mirror (basketbuild) :https://basketbuild.com/devs/CheckYourScreen/arsenic/onyx_olddroid
Keep in mind:
If you are running a Custom Kernel already then plz CLEAN FLASH Oxygen OS before flashing Arsenic, Official Oxygen OS zip doesnt offer system wipe so dirty flash wont work, you gotta clean flash manually!
Zip doesnt mess with the ramdisk so you can feel free to dirty flash it over Arsenic's previous versions(Dont forget to clear data of kernel adiutor or anyother kernel control app you're using before).
Compatible with Oxygen OS and OldDroid's AOSP ONLY..!
For Custom Rom support head over to THIS THREAD
Bugs and issues:
Little longer Boot Time as compared to stock kernel - working to decrease it! (cant you wait a couple of secs. to boot? it should only bother those people who reboot every hour. lol)
Special Thanks and Credits to (in NO specific order):
@Krustak
@Joshwin Aranha
@sultanxda
@eng.stk
@Lord Boeffla
@franciscofranco
@Exodusche
XDA:DevDB Information
[KERNEL][OOS 3.x.x/OldDroid's AOSP] Arsenic.Kernel, Kernel for the OnePlus X
Contributors
CheckYourScreen
Source Code: https://github.com/CheckYourScreen/Arsenic.Kernel_onyx-oos
Kernel Special Features: Battery backup (at its best) | Performance (30-40% more than aosp/stock kernel "atleast") | Stability - (what else do you expect from a kernel...?)
Version Information
Status: Stable
Current Stable Version: V10
Stable Release Date: 2016-10-30
Created 2016-10-30
Last Updated 2016-12-07
Changelogs :
V10 (06/12/2016) -
December security patches (partial,left over patches will be merged in next release. Critical ones are merged already)
Nuked non-working GPU Govs from userspace (wont reboot when you select broken governor)
Improved Responsiveness (literally 0 delay/latency while providing input)
Fixed lots of code errors/warnings with better indentation.
Nuked LP11 state of DSI lanes
Removed unwanted debugging
Reduced resource utilizations
Fixed CVE-2015-8966
20% increase in transactions per second on memory
Reject groups/events spanning multiple hardware PMUs
No more events which causes soft lockups to prevent device entering into sleep.
40% more throughput with lower cpu consumption while swapping pages
V8 (28/11/2016) -
Merged OOS 3.1.4 changes
Optimized square root algorithm.
Security Patches
Rowhammer vulnerability patch
CPU Boost interval improvements
Fix off by one vulnerabilities
l2tp: fix oops in l2tp_eth_create() error path
Staging: android: binder: Allow using highmem for binder buffers
Add and Enable Modified ElementalX Governor
Enable DNS Resolver, NFS CIFS
lowmemorykiller: account for unevictable pages
Fixed uninitialized variables
Enabled DEVMEM and DEVKMEM
sched/loadavg: Fix loadavg artifacts on fully idle and fully loaded systems
net: sch_generic: Allow devices to opt-out net watchdog
msm_rmnet_bam: Actually disable watchdog for msm_rmnet
Switched to XZ Compression
Old Releases:
V5 (13/11/2016) -
Backports of Extra Security Patches
bam_dmux: increase wakeup timeout
usb: mtp: increase RX transfer length to 1M (faster mtp transfer rate, yup for real!)
usb: Avoid spammy warning due to misbehaving Apps
Allow ignoring system restarts and prevent kernel panic when sub system restart isn't available
Disable alot of unwanted debuggings
Enabled L2TP Extensions and Debugging.
Increased Stability!
Prevent kernel from going for a panic for any abnormal condition and fill logs instead.
Prevent kernel panic in case of abnormal ssr being issued by the system for a reboot/shutdown process.
Decreased Boot Time!
Enabled Swap
Decreased VM Swappiness to 40%
Disabled NFC and Nuke its redundant code
V2 (30/10/2016) -
Built with latest GCC 4.9 upstream toolchain
Nuked Adreno Idler.
msm8974pro: Add 27 MHz gpu frequency step (idle freq)
Add support for AudioFX
Switch to row as Default Gov.
xz: optimize sfck compression
random: increase read and write entropy levels.
Add and Enable USB Fast Charge.
Add and Enable Zen and Tripndroid I/O Scheduler.
vfs: Work around NULL pointer dereference in d_path()
mdss: move to a kthread for vsync_retire_work_handler (Backport from Pixel)
kgsl: convert some workqueues to use kthreads (Backport from Pixel)
drivers: vidc: Enable vidc debugging.
Fix DirtyCow Vulnerability.
V1 -
Same Changelog as R24 release of CM/AOSP builds. Click Here for it
Suggestions and F.A.Q's :
Suggested profile/settings for kernel adiutor:
Recommended Profile:
CPU max freq : 1.7ghz
CPU min freq : 300mhz
Governor : Impulse / Interactive (Impulse is the best gov. whereas Interactive is the Smoothest!)
Fast Charge : Enabled
Multicore Power Saving : Aggressive
Sync Threshold : 729mhz
Input Boost Freq : 652mhz
Thermal : Core Control enabled
Speaker Driver Leakage toggle(in soc driver tuneable): enabled
Krait C-States Settings toggles: enable all
GPU Gov. : msm-adreno-tz
Max. GPU Freq. : 578mhz
Min. GPU Freq. : 27mhz (use 200mhz as min. If you face any UI/UX lag or stutters)
I/O scheduler : ROW with 512kb read ahead for int. and ZEN with 512kb for external
Wake locks toggles: DISABLE ALL (this will prevent wifi and bluetooth wakelocks if your device is suffering from any-check battery graph if you get wifi on usage even after being turned off) (turn them on if you face any issue, you wont actually )
TCP Cong Algo : Westwood
Battery oriented:
CPU max freq: 1.5ghz
CPU min freq: 300mhz
governor: Impulse
Multicore Power Saving: Aggressive
Sync Threshold: 729mhz
Input Boost Freq: 652mhz
Thermal: Core Control Enabled
Speaker Driver Leakage toggle(in soc driver tuneable): enabled
Krait C-States Settings toggles: enable all
GPU Gov. : msm-adreno-tz
Max. GPU Freq. : 578mhz / 462mhz (your choice, 462 if you don't play games)
Min. GPU Freq. : 27Mhz (use 200mhz as min. If you face any UI/UX lag or stutters)
I/O sched: ROW with 512kb read ahead for int. and ROW with 384 kb for external
Wake locks toggles: DISABLE ALL (this will prevent wifi and bluetooth wakelocks if your device is suffering from any-check battery graph if you get wifi on usage even after being turned off) (turn them on if you face any issue, you wont though )
TCP Cong Algo- Westwood
Insane Battery Profile:
CPU max freq : 1ghz
CPU min freq : 300mhz
Governor : Impulse
Fast Charge : Enabled
Multicore Power Saving : Aggressive
Sync Threshold : 652mhz
Input Boost Freq : 422mhz
Thermal : Core Control enabled
CPU Voltage : -10 (Global Offset)
Speaker Driver Leakage toggle(in soc driver tuneable): enabled
Krait C-States Settings toggles: enable all
GPU Gov. : msm-adreno-tz
Max. GPU Freq. : 330mhz
Min. GPU Freq. : 27mhz (use 200mhz as min. If you face any UI/UX lag or stutters)
I/O sched : FIOPS with 512kb read ahead for int. and ROW with 384 kb for external
Wake locks toggles: DISABLE ALL (this will prevent wifi and bluetooth wakelocks if your device is suffering from any-check battery graph if you get wifi on usage even after being turned off) (turn them on if you face any issue, you wont actually )
TCP Cong Algo : Westwood
---------------------------------------
Default profile for zzmoove gov. is set to 0 by default, change it to your desired profile, more info about profiles are HERE.
I prefer ybat (profile_number=2).
---------------------------------------
Since All of these settings are not visible in official Kernel Adiutor, kindly use Kernel Adiutor Mod from HERE
F.A.Q's :
Can you add [this] and [that] feature to arsenic?
Something I pride myself with this kernel is that it does not have a bunch of random, useless features or patches mashed into it. Everything put into this kernel is thought out well and tested. I see a lot of works being made popular because it has [this] and [that] feature when really, it's nothing revolutionary(atleast to me). As a matter of fact, most things added to any kernel will not make it 5x better than any other kernel. Most of the time, simple is better; and in this case it definitely is!
Any plans of upstreaming the linux version?
No, and i wont. Though i have test builds ready but they wont make up to the release version. Upstreaming linux version doesnt make much difference infact it does degrade Arsenic's performance. Reason why i'm against it is that I've removed almost all possible useless redundant code and debugging present in it to improve kernel in all aspects, upstreaming will not only add alot of redundant code but will also add debugging functions for those redundant code! Which will not only increase kernel's size but will heavily impact on kernel's performance, battery backup and stability. Currently 3.4.0 is "THE" most stable branch and i'd like to keep it.
Why MPDecision? Why not remove the hell outta it?
You want me to remove something which was developed by some of the finest engineers of this world and is currently being shipped on almost all android devices..? Dont you think there would have been a reason why Google chose MPDecision over anyother hotplug.
What most of the users arent aware of is that, MPDecision works best with the default thermal solution, all it needs is a little touch..
As far as adding an additional hotplug, m still thinking about it.
Why so rude?
Not rude, Determined. Everything i do has a reason behind it. And I do sometimes accept feature request if they seems to be worthy.
reserved
Should i wipe system >Flash oxygen OS >SuperSU >kernel?
EDIT-Coming from boeffla kernel.
Sent from my ONE E1003 using Tapatalk
noonebhargav said:
Should i wipe system >Flash oxygen OS >SuperSU >kernel?
EDIT-Coming from boeffla kernel.
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Open Twrp > Wipe system,data,cache > Flash Oxygen OS > Reboot > Open Twrp > Flash Supersu > Reboot > Open Twrp > Flash Arsenic Kernel > Reboot.
OOS is not like a custom rom so to be on a safer side follow the above procedure.
You can dirty flash the future releases though, but if you are coming from anyother kernel then follow these above steps to avoid any conflicts.
Kernel is great Nimit few days now running like a champ!!
CheckYourScreen said:
Open Twrp > Wipe system,data,cache > Flash Oxygen OS > Reboot > Open Twrp > Flash Supersu > Reboot > Open Twrp > Flash Arsenic Kernel > Reboot.
OOS is not like a custom rom so to be on a safer side follow the above procedure.
You can dirty flash the future releases though, but if you are coming from anyother kernel then follow these above steps to avoid any conflicts.
Click to expand...
Click to collapse
So what is fast charging? Afaik our charger gives max of 1800 mA, so can you explain it a bit?
saurabh40629 said:
So what is fast charging? Afaik our charger gives max of 1800 mA, so can you explain it a bit?
Click to expand...
Click to collapse
By default hardware restricts USB charge current to <500 mA when connected to a PC/laptop, USB Fast charging driver syncs it with AC charge current rate.
Though rate varies accordingly to load average and device usage. Its managed by system for better result instead of forcing with a predefined value.
{
"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"
}
Will restoring boot.img from nandroid backup and then flashing this kernel work?
Sent from my ONE E1003 using Tapatalk
CheckYourScreen said:
By default hardware restricts USB charge current to <500 mA when connected to a PC/laptop, USB Fast charging driver syncs it with AC charge current rate.
Though rate varies accordingly to load average and device usage. Its managed by system for better result instead of forcing with a predefined value.
Click to expand...
Click to collapse
Nice... Thanks for explanation. Keep up the awesome work, will try it.
noonebhargav said:
Will restoring boot.img from nandroid backup and then flashing this kernel work?
Click to expand...
Click to collapse
Yes.. That's mostly true. But better flash oos as nimit mentioned.
noonebhargav said:
Will restoring boot.img from nandroid backup and then flashing this kernel work?
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
other custom kernels might leave postboot scripts and modified ramdisk which might conflict so, its better to clean flash.
Flash it working perfectly.
Sent from my ONE E1003 using Tapatalk
Thanks man. This made my day
Any recommended gaming settings for kernel? (no lags using current settings but slight heat)
Sent from my ONE E1003 using Tapatalk
noonebhargav said:
Any recommended gaming settings for kernel? (no lags using current settings but slight heat)
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Just set minimum freq of gpu to 200Mhz instead of 27Mhz for gaming.
And its "OnePlus X", do you really expect it not to heat even while playing games?
Even if i add some custom thermal solution it will impact on UX while playing games as it will try to throttle CPU to control heat which might bug you lol
CheckYourScreen said:
Just set minimum freq of gpu to 200Mhz instead of 27Mhz for gaming.
And its "OnePlus X", do you really expect it not to heat even while playing games?
Even if i add some custom thermal solution it will impact on UX while playing games as it will try to throttle CPU to control heat which might bug you lol
Click to expand...
Click to collapse
Changed the governor to zzmove and profile 10, working fine.
Sent from my ONE E1003 using Tapatalk
Flash it but build number is unknown

Categories

Resources