[ Info ]
RC-1 Released
[ WARNING ]
Use this at your own risk!!
I am not responsible for any damange to your phone, pc, that you will get fired because alarm doesn't work
[ Features ]
- Overclock up to 1,15GHZ DON'T OVERCLOCK, JUST SELECT THE 1GHZ OPTION IN OVERCLOCK APP
- Cpu governess
- I/O Schedulers
- Recovery
- lots of new drivers
- Smooth
[ How to install ]
1. Download the boot.img
2. Flash it with fastboot (Fastboot flash boot boot.img)
3. Go to recovery, advanced and wipe dalvik cache!
4. reboot
5. ENJOY!!
READ THE FULL THREAD BEFORE ASKING ANY QUERIES OR REPORTING ANY BUGS/ISSUES
Credits:
Krabappel2548
Doomlord
KeiranFTW
Kamarush
ThJap!
Deepunknown
Shaan (S Advance)
Munjeni
my sources: https://github.com/nickholtus
Nick
If you want to user abt of thuis files, pm me first
Downloads:
Kernel: RC-1 Boot.img
just realised: this is my 1000ste post here on xda
RC-1
-Totally rebased the kernel
-Mainstream update 3.0.69
-Updated st-ericsson drivers
-Added lots of fixes (more then 80!)
-Added governers
-Added I/O schedulers
-A lot of other things!!!
-DONT USE OC, JUST USE THE 1 GHZ OPTION, otherwise system will lag. Will be removed in next version, this oc option was for test purposes)
last one
reserved..
just in case
Are the sources for Xperia P and U out?
yes they are
Thanks!
Flashed kernel a few minutes ago, looking good so far. I'm using smartassv2 governor and deadline scheduler, no overclock.
Hopefully there won't be any bugs to report
Just one thing: it would probably be a good idea to post stock WiFi modules, for those folks that may want to go back from your kernel to the stock one.
---------- Post added at 10:41 AM ---------- Previous post was at 09:56 AM ----------
Aaargh... scratch that, there are some issues with the new governors:
Scrolling in LauncherPro (between screens, in the app drawer) is jerky. Also in Pulse News and Pocket (ReadItLater), although not as bad as with the launcher.
It's the same for smartassv2, minmax, interactive.
Ondemand and performance are fine, smartass (not v2) is a bit better but still laggy.
Also, the device is slow to wake up, with any governor: takes about 2-3sec for the screen to turn on, after pressing the power button.
EDIT- forgot to mention, I'm running KA02 ROM... there may be conflicts with one of the init.d scripts that come with the ROM.
Would appreciate it if anyone running stock firmware would test the kernel and report back.
cezarL said:
Thanks!
Flashed kernel a few minutes ago, looking good so far. I'm using smartassv2 governor and deadline scheduler, no overclock.
Hopefully there won't be any bugs to report
Just one thing: it would probably be a good idea to post stock WiFi modules, for those folks that may want to go back from your kernel to the stock one.
---------- Post added at 10:41 AM ---------- Previous post was at 09:56 AM ----------
Aaargh... scratch that, there are some issues with the new governors:
Scrolling in LauncherPro (between screens, in the app drawer) is jerky. Also in Pulse News and Pocket (ReadItLater), although not as bad as with the launcher.
It's the same for smartassv2, minmax, interactive.
Ondemand and performance are fine, smartass (not v2) is a bit better but still laggy.
Also, the device is slow to wake up, with any governor: takes about 2-3sec for the screen to turn on, after pressing the power button.
EDIT- forgot to mention, I'm running KA02 ROM... there may be conflicts with one of the init.d scripts that come with the ROM.
Would appreciate it if anyone running stock firmware would test the kernel and report back.
Click to expand...
Click to collapse
The new governors just aren't optimized yet for new Xperia devices
It has nothing to do with the tweaks, but I can try to add some specific tweaks for the new governors, it might help
Sent from my MT15i using XDA
krabappel2548 said:
The new governors just aren't optimized yet for new Xperia devices
It has nothing to do with the tweaks, but I can try to add some specific tweaks for the new governors, it might help
Sent from my MT15i using XDA
Click to expand...
Click to collapse
Choice is good, but so many governors? I am no expert on this matter, which is exactly my point. Someone with a good understanding on how governors work should add options for, say, three scenario's:
- Performance. When needed, throttle to max. overclocked speed and switch to faster speeds sooner
- Medium, scenario between energy saving and performance.
- Energysaving. Do not overclock, set the clock the lowest setting possible when screen off, sleep mode and use moderate throttling just enough to ensure the device doesn't feel laggy but isn't as snappy as Performance.
Or.. post the settings for these scenario's here
hi,
i just added 4 governes
most of them are stock
ok good news
After a lot of testing, editing etc with Krabappel2548 we have got more frequences
normally we have 4 freq, now we have got 7 working
Release: Soon
also added 1.2ghz (if everything goes well)
Awesome work guys!
Just a couple of days of struggling with study, and then I''ll finally have some time to experiment with the phone. Hopefully this new kernel will allow a nice improvement in battery life
have a little improvement in battery life.
working on that...
nickholtus said:
have a little improvement in battery life.
working on that...
Click to expand...
Click to collapse
Yes, we are working on the kernel, we just added extra governors, I/O schedulars and extra CPU freq
ICS kerrnel v2 is released and on the Fileserver now Nick, maybe a little changlog?
quick panel
--
krabappel2548 said:
ICS kerrnel v2 is released and on the Fileserver now
Click to expand...
Click to collapse
Flashed v2, very slowly, even in his native launcher in ondemand mode.
On V1 was ok, only 2 times rebooted itself in sleep mode.
select another governer
conservative is fast
v2b or v3 will be released today or tomorrow without any lag
nickholtus said:
ok good news
...
also added 1.2ghz (if everything goes well)
Click to expand...
Click to collapse
Is there any problems with 1.2 GHz freq that you didn't include it to the ROM For now the highest freq is 1.15GHz...
no didn't add it
maybe in the next update (if we get some things figured out)
Related
[KERNEL][23/07] █░ SGSII | 2.6.35.7-MirageS2 [v5]- STOP BATT DRAIN | OC 1600mhz ░█
Firstly, I'm not responsable if you brick your phone doing overclock or a bad use of this kernel. So, be careful.
This kernel is built from a custom modified source by me (I've added and modified some things to an updated SGS2 source), I've tried to modify it to get the lowest battery drain, so this kernel should stay in a step between performance and battery, if you like some more performance you can download SetCPU, or other custom app to modify freqs and default governor.
What's included:
-For XXKG1/G2/G3 (should work with olders too)
-Modified Freq range 11 steps (200-400-500-600-800-900-1000-1200-1400-1504-1600 Mhz)
-CPU UV sysinterface (thanks to ninphetamine)
-Modified cpufreq.c to force processor to go step-by-step in freqs.
-Default Freq: 500-1200 Mhz ondemand (the best to get low batt drain, should drain lower in sleep)
-Lowest maximum freq blocked to 400mhz (so if you put 200-200, it will run 200-400, locked due to better performance)
-Available governors: interactive-smartass-conservative-userspace-powersave-ondemand-performance (custom modded smartass, ondemand and interactive governors)
-CFS Scheduler.
-SLQB Allocator.
-CFQ Block IO Scheduler (Available: no-op, deadline, cfq)
-Modified Initramfs from saturn_de (thanks to him and Chainfire) - I've added some values to this init.rc to get lower battery drain and some performance. (some different from saturn)
-CWM 4.0.0.2 Recovery
-Disabled Profiling support and debugs, added ThumbEE, Improved Control Group Support.
-Added some CFQ IO tweaks
-Changed dalvikvm heapsize to 60m (this should improve performance on tasking)
-Touchscreen fix added (thanks to vicenzo91)
*[email protected]
*[email protected]
*int:fast is not included due to performance problems.
*not compatible with tegrak OC (tested with SetCPU)
test with performance 1504mhz, vfs_cache_pressure=100 and dalvik 64m (default vfs=70, you can modify it downloading Sysctl Config from Market)
v5:
*set samsung-update1 as base (fix reboots)
*added slqb patch
*removed bfq
Download:
SERVERS:
[USA]SGSII-2.6.35.7-MirageS2-v5
[DEUTSCHLAND]SGSII-2.6.35.7-MirageS2-v5
[Mirror]http://sgsii.z4mb0.net/Kernels/SGSII-2.6.35.7-MirageS2-v5.tar Mirror by El TeKi thanks
reserved.....
Wow nice to see you here. Will try it out immediately
Sent from my GT-I9100 using XDA Premium App
looks really really really promising... trying it now
how come i only get scores around 3200 with every rom and kernel? and everyone else has so high
going to try this one soon
yeaaa baby !!
Good to see you here Neo. Been a Aurax/Reflex fan on the Desire...
This is good news!
Regards
Awesome, will try this when i get home
Sent from my GT-I9100 using XDA Premium App
Just flashed. Oc to 1.5ghz. First quadrant 4566
will give feedback on batt consumption soon
Hope to see soon a rom made by you..... On my old desire i had your auraxtsense!!! U are great
Very nice neo. I'm a fan of your desire rom.. now u make a kernel for sgs2. No doubt, i will try it in the future. I hope u release your own version rom for sgs2.
+1
Sent from my GT-I9100 using XDA App
+2
Sent from my GT-I9100 using XDA App
trunks986 said:
Hope to see soon a rom made by you..... On my old desire i had your auraxtsense!!! U are great
Click to expand...
Click to collapse
Soon mate, soon. Thanks
Holy shiznit,who would've thought we'd be seeing you here Neo?I gotta thank you for the first rom that made me actually love my Desire.Not the only one,but it was the first whatsoever.
I'd like to tell you a thing or two(or three ) though.
1)You should add support for SetCPU's voltage control.I know there are other apps that do the same thing,but the number of people using SetCPU is massive.And on the Galaxy S 2,undervolting is very important,especially to avoid issues with overheating.
2)Could you pleaaaase lower the max clock by only 4MHz?My phone is unstable at 1504MHz with 1350mV,while it's rock stable at 1500Mhz with 1325mV.And I'm serious,4MHz only and it makes a huge difference,while performance-wise it's the same.
3)You could also overclock the GPU.200MHz with 750mV min and 400MHz with 1100mV max seems stable for everyone.You can gain quite a lot of performance,while it doesn't heat or consume more.You can also test if what I say is true yourself.
Else that those three...Well,welcome to our world pal!The world of power!
I don't know what you did to get 5000 in productivity on smartbench11 cos I can't hit more than 4300 even with the vfs setting changed...and yes I am overclocked to 1.5ghz and locked there.
Hi can make a kernel with default clock with 1,5ghz please ?
Yanardag said:
Hi can make a kernel with default clock with 1,5ghz please ?
Click to expand...
Click to collapse
Just download SetCPU and set the min and max to full.
Mirror http://www.megaupload.com/?d=4LLP5HPF
Another mirror http://www.multiupload.com/L215724GBY
Just flashed your kernel. Thanks
Is auto brightness broken ? The brightness goes to 100% on autobrightness eventhough it is night and there is no light
Tried wiping dalvik cache but did not help
EDIT: Covering the light sensors with a black blanket did not change anything. So there seems to be a problem with auto brightness. I am on stock KG1 leaked rom
Ok guys this is my first overclocking app, including the following features:
Simple management of Processor Frequencies (Min and max)
Governors management with a gesture (Swipe down)
IO Schedulers management with a gesture (Swipe up) *new
Save as safe feature, wich means you have less chance to make some excesive overclock damage
Run at boot option
Visualization Settings
Requirements:
Android 2.2+
Kernel support for overclocking
Rooted device
Features planned:
-Profiles and notifications
-Voltage control (if kernel supports)
-AutoSet best config *new
Links at second post.
Some screenshots
02/04/2012 - v1.2
Fixed some fc while switching frequences on SeekBar
Fixed wrong sort of frequencies (now always from lesser to greater)
New ICS UI (only for ICS devices)
Almost done time / temperature profiles
Changed write method to command echo "frequency" > /sys/blah...
Current ram usage - 5MB, size 45.9KB
24/01/2012 - v1.1
Profiles implemented
Save as safe feature is better now (long click to show current saved)
Profiles (for now only battery level)
Notification system (also customizable led color settings*)
Independent performance settings submenu (for now just "pi" test, wich means a load test calculating pi number on loops)
Bugfixes and improvements
Current ram usage - 2.3MB, size 45.4KB
*This feature may not work on some devices
20/01/2012 - v1.0
First release
Official List of Current Working Devices:
Samsung Galaxy S / S2 - Fully working
Sony Ericsson Xperia Family - Fully working
Huawei U8800 (IDEOS x5) - Fully working
Milestone 1 - Fully working
LG Optimus One / 2X - Fully working
LG GT540 - Fully working
Which kernel is better for this app??
icerebro said:
Which kernel is better for this app??
Click to expand...
Click to collapse
That doesn't depends on kernel, app will adapt on any kernel if it support overclock (all kernels in mini and mini pro does support oc)
I've tested and works perfectly...!
I used with Naa Kernel and Rom
As soon as I set vlaue 768 and apply phone reboots. I this just me?
hey!! D4.
nice to see u again in this forum. thank you
Banwell13 said:
As soon as I set vlaue 768 and apply phone reboots. I this just me?
Click to expand...
Click to collapse
this happens to me too (not thru the app, i OC using CMsettings) some minipro's can seemingly go only upto 691 MHZ withh one oc module..
for example with nAa kernel i can go only upto 691Mhz but with zombipanic kernel i can go to 800Mhz dunno y...
hey! d4. i saw gpu overclock stuff in ur github sources. any progress??
siddardha21 said:
hey! d4. i saw gpu overclock stuff in ur github sources. any progress??
Click to expand...
Click to collapse
Nope, GPU clocks seems to be complex to mod. And now im not in vacations so my time is not a lot cuz im almost always busy
Good work D4!!
and the app it's really small 33KB!!
just suggestions:
1
it's possible to have the stability test in a single option too?
...not linked to the save as safe feature??
2
..to write somewhere the swipe options
just in case of memory loss
thanks
ciribaski said:
Good work D4!!
and the app it's really small 33KB!!
just suggestions:
1
it's possible to have the stability test in a single option too?
...not linked to the save as safe feature??
2
..to write somewhere the swipe options
just in case of memory loss
thanks
Click to expand...
Click to collapse
I will do your first suggestion, was already planned, the other one i dont know if is so relevant
It seems my kernel doesn't support over clocking
The sliders are not moving, I guess I will have to replace the kernel. which one do you suggest? I have an Arc S.
DeepUnknown said:
It seems my kernel doesn't support over clocking
The sliders are not moving, I guess I will have to replace the kernel. which one do you suggest? I have an Arc S.
Click to expand...
Click to collapse
Could you tell me your Kernel's name (even better upload a screenshot of about phone in settings)?, also 2 more things, is your phone rooted, and did you allow superUser permissions to simple OC ?
Hi,
I cannot choose any IO schedulers - I have only 'noop' in every governor.
HTC Desire Z here and my kernel is 2.6.35.14-Andromadus-Flinny-v1 (from Andromadus ICS v8 rom).
Any suggestion?
Greets & thx for the app!
can i use this to underclock stock kernel?
stemer said:
Hi,
I cannot choose any IO schedulers - I have only 'noop' in every governor.
HTC Desire Z here and my kernel is 2.6.35.14-Andromadus-Flinny-v1 (from Andromadus ICS v8 rom).
Any suggestion?
Greets & thx for the app!
Click to expand...
Click to collapse
Can you upload a screenshot?, that may be because your kernel only supports noop io scheduler.
EDIT: On my stock kernel with no custom io schedulers, the list is reduced, so that does means your kernel only supports Noop scheduler.
romy134 said:
can i use this to underclock stock kernel?
Click to expand...
Click to collapse
Im not sure, but i will try and say you
EDIT: Yes you can, but with the new version, will release soon. Also, sliders cant be moved if your kernel does not support overclock, but you can setup easily a powersave governor, wich will underclock your cpu
universal?
what devices does this app support? all androids running 2.2+ or just xperia? i would assume that with SetCPU mentioned in the op that it is universal, but wanted to make sure. TIA
esthernrob said:
what devices does this app support? all androids running 2.2+ or just xperia? i would assume that with SetCPU mentioned in the op that it is universal, but wanted to make sure. TIA
Click to expand...
Click to collapse
My aim is to make it universal and lightweight as hell! ill need support from all devices owners, for now, it should work on any device, anyway please test it. I will release a "more universal" version soon, im talking about 2 days, almost done now.
ok nice app but its been done alread about the exac same thing with NOFRILLS CPU thats out in the market for free and has been out longer and suports more languages . so dont know why this app got recognition on xda while nofrills cpu didnt and its been out longer... if anyone intrested look up nofrills cpu its the same thing ..... ps. im not tolling or hateing just thought id point it out ...
LuPuS 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"
}
Hello there, I was reading about Governors on a thread
and was curious about these governors that I hadn't seen before and wanted to try them.
So then I came across this great thread by paxChristos and decided I would try compile a kernel with new Governors and io-scheduler.
I've taken out a couple of things while compiling the kernel as well. I have been using it for a good few days now
and thought I should share these Governors to other Xplay users.
I googled for a name and came across LuPuS :highfive: that is why the boot logo is what it is
Well hope you all enjoy and I will be adding more governors soon when I get time
Thanks to all those who have helped me making this, paxChristos for his advice & tutorial.
Lightnindude, FXP and Cyanogenmod for their sources :good:
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]
What Works --
Wifi - (flash modules)
Data
Camera
Panorama
Video Recording (720p now works)
Video Playback
Front Camera
Bluetooth
Everything Else that works on FXP & Mjolnir
What doesn't work --
ALS (Disabled)
Anything that doesn't work on FXP & Mjolnir
Included in kernel
[/LIST]
Added Io-schedulers --
- Noop
- Anticipatory
- Deadline
- CFQ
- BFQ
- SIO
Added Governors --
- lagfree
- brazillianwax
- smoothass
- scary
- savagedzen
- smartass
- smartassv2
- interactivex
- minmax
- powersave
- performance
- conservative
- ondemand
- interactive
- userspace
+
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
- Supports ext 2,3
- Updated zRam
- Lzo compression/decompression speed has doubled on average.
- Init.d support
- Fudgeswap
- And much more
- O/C and stable upto 2ghz, although I do not recommend O/C to 2ghz for long periods of time, do so at your own risk.
Show your support for the kernel and my work by putting this in your signature, its only a quick one I done up with my limited time
Code:
http://i.imgur.com/xtWNL.png
Downloads in post 2
Instructions for the CWM Recovery And Aroma File Manager--
--When phone vibrates tap the back key to enter CWM Recovery v6.
--When phone vibrates tap the volume down key to enter Aroma File Manager
I would like to say a big thanks to -
paxChristos - Tutorial / Help
xeozus
NobodyAtAll
Faux123
Erasmus
Leedroid
Jerpelea
KeiranFTW - for his PNG to RLE conversion script
Lightningdude - Sources / Help
FXP - Sources
Cyanogenmod - Souces
DooMLoRD - Everything he's done for XPLay
Supervenom - For the amazing AOKP rom
Solomon4400 - For helping me test (there where a few dodgy ones before I got it to work random reboots and stuff )
CosmicDan - For the amazing CWM / Aroma File Manager - AND LuPuS MIUI[CM9 BASED]
tempest918 - For the New Logo
amarullz - For Aroma File Manager
Kernel sources -b ics
https://github.com/garwedgess/LuPuS-CM-iCs
Changelog
*** Previous changelog was messed up so I'll include everything in here ***
Code:
[B][U]v9[/U][/B]
- Improved Battery Life alot :)
- Thumbee support
- EXT 2/3 & 4 supported
- Init.d supported
- Init.d scripts added (run at boot)
- SLQB Memory allocator
- ARM7 optimizations
- Brought OC back down to 1.6 max (no need for it above 1.6 unless u want to kill your device)
- Kernel sources completely reworked started from scratch o Sony xx.587 sources
- Tiny RCU
- Updatedd patched and fixed LZO
- lowered vfs cache pressure
- Increased Wifi- Range and added support for channel 14
- 0 % Battery patch - Thanks @ Bazoocaze
- Better memory copy
- Better memory move
- Deep sleep issue fixed
- LMK Optimizations (LowMemoryKiller)
- VDD support (voltage conrol)
- Linaro Optimzations
- Compaction added
- KSM
- CIFS (improved support)
- NTFS
- Updated to newest SIO Io-Scheduler
- Google Snappy Compress & Decompress
- Added Vibrate To Recovery (Notification to enter CWM)
- Wifi module size drasticly reduced
** Possibly missing a few things **
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.
So zRam does not work on them, below i've added a zram enabler .zip to flash via CWM[/B]
- If for whatever reason you want to disable Zram after you have flashed the .zip, just go to ect/init.d and delete 00zram
Wifi-modules included - Thanks @ CosmicDan
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
v9-LiNaRo-480p Recording
LuPuS-v9-480.img
MD5 = 3b33c08252a845e7cd8374d112f05e9f
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
v9 LiNaRo-720p Recording
LuPuS-v9-720.img
MD5 = 225f5abdfc30643e9763ff3ad95c17af
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
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
Please Click Thanks :good:
Great, I'll try it! :good:
Alejandroch said:
Great, I'll try it! :good:
Click to expand...
Click to collapse
Cool make sure you download and flash the the wifi modules in CWM!!
Yo I highly rate this kernel and the dev he is really great! Gratz wedgess do your thing.
Sent from my R800i using xda app-developers app
Cool thanks for the great work, the Intellidemand governor sounds very interesting.....!
Thanks for sharing your source, I like to strip system down to 240MB to give data some more space.
EDIT: I have shared with you my RAMDisk image for your consideration wedgess, maybe you will like it. It is taken from latest CM9 Ramdisk with the following changes:
- Replaced FreeXperia Recovery with DoomLords' Recovery
- Changed Recovery key to Back (instead of Volume-Down) and added a short vibration (just like DoomKernel)
- Bootlogo unchanged, still original FXP one
- Maybe some other small things, can't remember. Tree-compare it to FXP Ramdisk if you like to make sure.
I would release my own kernel with these changes but we already have two CM9-based kernels now, I don't really want to!
CosmicDan said:
Cool thanks for the great work, the Intellidemand governor sounds very interesting.....!
Thanks for sharing your source, I like to strip system down to 240MB to give data some more space.
EDIT: I have shared with you my RAMDisk image for your consideration wedgess, maybe you will like it. It is taken from latest CM9 Ramdisk with the following changes:
- Replaced FreeXperia Recovery with DoomLords' Recovery
- Changed Recovery key to Back (instead of Volume-Down) and added a short vibration (just like DoomKernel)
- Bootlogo unchanged, still original FXP one
- Maybe some other small things, can't remember. Tree-compare it to FXP Ramdisk if you like to make sure.
I would release my own kernel with these changes but we already have two CM9-based kernels now, I don't really want to!
Click to expand...
Click to collapse
Thanks intellidemand is great, its the governor I'm using at the moment. Recovery should already be the BACK button as I edited the ramdisk with my own boot logo and sbin. I used dooms touch recovery before but just wanted something simple if people want I could change eventually
Sent from my Xperia Play using xda premium
wedgess said:
Thanks intellidemand is great, its the governor I'm using at the moment. Recovery should already be the BACK button as I edited the ramdisk with my own boot logo and sbin. I used dooms touch recovery before but just wanted something simple if people want I could change eventually
Sent from my Xperia Play using xda premium
Click to expand...
Click to collapse
Did you add vibrate too? I always miss the trigger on FXP kernel lol. I don't like the full Touch Recovery either because you can't see long filenames properly, but the one from his ICS Beta kernel is just like CWM Recovery.. but it does have the touch-enabled buttons down the bottom, or is that the same one you mean...? I understand it can be annoying bumping the screen on that and making a mistake selection, but DoomLord Recovery has some useful features... power-off is a good example, I hate having to pull the battery out to power off (seems dangerous).
Well yeah let the crowd decide, nothing is stopping me from repacking it myself for my use of course Cheers.
CosmicDan said:
Did you add vibrate too? I always miss the trigger on FXP kernel lol. I don't like the full Touch Recovery either because you can't see long filenames properly, but the one from his ICS Beta kernel is just like CWM Recovery.. but it does have the touch-enabled buttons down the bottom, or is that the same one you mean...? I understand it can be annoying bumping the screen on that and making a mistake selection, but DoomLord Recovery has some useful features... power-off is a good example, I hate having to pull the battery out to power off (seems dangerous).
Well yeah let the crowd decide, nothing is stopping me from repacking it myself for my use of course Cheers.
Click to expand...
Click to collapse
Haha ye that's the one I mean just personally prefer the original CWM, I agree with the power off but I just reboot system now and don't battery pull I'm open to suggestions though maybe I could make a version for people who prefer it that way??
Sent from my Xperia Play using xda premium
wedgess said:
Haha ye that's the one I mean just personally prefer the original CWM, I agree with the power off but I just reboot system now and don't battery pull I'm open to suggestions though maybe I could make a version for people who prefer it that way??
Sent from my Xperia Play using xda premium
Click to expand...
Click to collapse
Here's an idea. Keep Vol-Down as FreeXperia Recovery (as it is originally), Back key as DoomLord Recovery, and Menu key as Aroma FileManager? That would be KICKASS. Looking at bootrec and bootrec-device scripts in sbin, seems easy enough to do! If you like that and would like a hand, send me a PM! Or we can keep bumping the thread discussing it :laugh: (Why not, valid dev. discussion that everyone can learn from)
CosmicDan said:
Here's an idea. Keep Vol-Down as FreeXperia Recovery (as it is originally), Back key as DoomLord Recovery, and Menu key as Aroma FileManager? That would be KICKASS. Looking at bootrec and bootrec-device scripts in sbin, seems easy enough to do! If you like that and would like a hand, send me a PM! Or we can keep bumping the thread discussing it :laugh: (Why not, valid dev. discussion that everyone can learn from)
Click to expand...
Click to collapse
this would be great, two days ago i was just looking on how to insert the doomlord recovery in the FXP kernel XD
Good work
Good work man.
:good:
I was reading your post and I thing governor: Lulzactive is not very effective.
I'm not phone deveolper, I'm only normal programmer.
So if I am wrong please explain.
I think it will make cpu freq very jumping, in every interval.
x=>60 - higher state
x<60 - lower state
so in average load it will do something like: ^v^v^v^v (higher->lower->higher->lower...)
what about:
x>60 - higher state
x<60&&x>40 - stay
x<40 - lower state
Gh61 said:
Good work man.
:good:
I was reading your post and I thing governor: Lulzactive is not very effective.
I'm not phone deveolper, I'm only normal programmer.
So if I am wrong please explain.
I think it will make cpu freq very jumping, in every interval.
x=>60 - higher state
x<60 - lower state
so in average load it will do something like: ^v^v^v^v (higher->lower->higher->lower...)
what about:
x>60 - higher state
x<60&&x>40 - stay
x<40 - lower state
Click to expand...
Click to collapse
Old Version: 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. THIS IS THE VERSION IT IS NOW
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
inc_cpu_load=70
pump_up_step=2
pump_down_step=1
If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
I WILL CHANGE TO THIS ONE IN A COUPLE OF DAYS
I will leave the old version in there and put the newer one as v2
Click thanks if you like this
wedgess said:
Old Version: 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. THIS IS THE VERSION IT IS NOW
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
inc_cpu_load=70
pump_up_step=2
pump_down_step=1
If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
I WILL CHANGE TO THIS ONE IN A COUPLE OF DAYS
I will leave the old version in there and put the newer one as v2
Click thanks if you like this
Click to expand...
Click to collapse
Sounds good, yeah the whole stay-at-current-if-between-60-and-40-percent is not really the nature of lulzactive, it's designed to have very responsive ramping. If you want a "stable" governor give the ondemand a go (or one of the ones it's based on, such as interactive or interactivex). Lulzactive is like a mix between interactive and smartass. Reference: http://forum.xda-developers.com/showthread.php?t=1369817
At the moment I'm having problems with lulzactive2 but if I can't fix it I still have other ones which I've added and am currently testing some of them. More to come....
Sent from my Xperia Play using xda premium
wedgess said:
At the moment I'm having problems with lulzactive2 but if I can't fix it I still have other ones which I've added and am currently testing some of them. More to come....
Sent from my Xperia Play using xda premium
Click to expand...
Click to collapse
...such as bfq scheduler and all three FXP-Recovery/DoomLord-Recovery/AromaFM ;D
EDIT: It should be noted that this kernel is based on the official CyanogenMod 9 RC2 release for the Xperia Play, not FXP-CM9. I don't know how different it will behave but there are a lot of sourcecode changes compared to the FXP-CM9.
CosmicDan said:
...such as bfq scheduler and all three FXP-Recovery/DoomLord-Recovery/AromaFM ;D
EDIT: It should be noted that this kernel is based on the official CyanogenMod 9 RC2 release for the Xperia Play, not FXP-CM9. I don't know how different it will behave but there are a lot of sourcecode changes compared to the FXP-CM9.
Click to expand...
Click to collapse
Fxp is CyanogenMod for xperia.
Sent from my R800x using xda app-developers app
idiotzach15 said:
Fxp is CyanogenMod for xperia.
Sent from my R800x using xda app-developers app
Click to expand...
Click to collapse
Yes I know that, but FXP is an unsupported and unofficial fork. This kernel however, based on official cm9 for zeus, has been modified for inclusion into the official CM9 device tree. There are a LOT of source-level differences, for example the official CM9 for zeus (including this kernel) has no bfq scheduler and revised netfilter code (which wifi tethering relies on, it needs to be tested). And many other things. The reason I'm stating this is because the tutorial we have for building a zeus kernel uses the original fxp-cm9 kernel as a base.
It was info for those who want to use/examine the Lupus source for whatever reason. I for one can't build the kernel from source, I get ipt_ecm.c errors (trying to sort it out with wedgess help, seems to be case-insensitive source and/or mismatched netfilter code from different kernels). Either wedgess has committed an untested source change or my toolchain (from Doomlord) or Linux environment is borked.
Seems that mounting USB Mass Storage in Recovery is broken with this kernel, or is it just me? Can anybody else test it?
CosmicDan said:
Seems that mounting USB Mass Storage in Recovery is broken with this kernel, or is it just me? Can anybody else test it?
Click to expand...
Click to collapse
I know for a fact that DooMLoRD's recovery doesn't call the UMS properly with CyanogenMod. Last time I looked into it, I read that it's something to do with whatever rom you're running, in conjunction with the kernel, itself. In other words, DooMLoRD makes his stuff to work with stock, and because of that, there will be differences when using his stuff with CyanogenMod.
Thomas.Raines presents
The Lightning Zap! kernel for the Nexus 4 Mako
ATTN:
I thomas.raines, nor it's affiliates claim responsibility for anything you do to damage, destroy, brick, explode, or otherwise mess up your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features:
Improved performance
Improved battery life
Improved network speeds
Improved boot times
Smoother scrolling
Better responsiveness
Cleaner file systems
Governor tweaks for amazing speed and performance without sacrificing battery life
Improved Memory and Ram tweaks
Improved Internet speed
kexec hack for dual booting with MultiRom.ak
Overclocked cpu
sweep2wake/doubletab2wake (disabled by default. must be enabled via script by uncommenting lines 7 and 8 in /etc/init.d/05s2w then reboot)
Amazing kernel tweaks, build.prop mods, init.d scripts and more!
Governors:
POWERSAVE
USERSPACE
ONDEMAND
INTERACTIVE
BADASSS
INTELLIDEMAND
LIONHEART
ONDEMANDX
SMARTASS2
GALLIMAUFRY
LAZY
io-schedulers
NOOP
DEADLINE
CFQ
SIO
See 2nd post for download links and changelogs
Instructions:
Make a backup
Download .zip to PC
Transfer .zip to your sdcard
Or just download it straight to your phone
Reboot to recovery
Flash
Reboot
Wait 10 minutes
Enjoy the Lightning Zap!
See 2nd post for download links and changelog
**The first boots usually takes the longest especially after a fresh install. If you pull a logcat during the first boot, you may see a few errors with the vacuum script. This is normal, and will be "fixed" after the phone has built the databases for the apps.
Please allow 24 hours after install and 1 full charge cycle before reporting results. Always provide me with a logcat with any issues you may experience.
Source Code:
mako-lz kernel
vendor_lz-kernel (LZ vendor files for ROM compiling)
Special thanks to:
jrummy16 for Root Browser Lite
show-p1984 for bricked kernel (used for rebase)
Download Links and Changelogs
Nexus-4-Mako-LightningZap_p5.1.2.zip
cpufreq adjustments
led driver adjustments
Import RB tree adjustments from Motorolla
Input packet management adjustments
EOL
https://github.com/LightningZap/and...mmit/9ee0e0e3f9cf2733c554f0da69724c79f71cb4d9
Nexus-4-Mako-LightningZap_p5.1.1.zip
Fixed voltages and frequencies
uv_bin overhaul
Fixed inconstancies in installer
Guys and gals with slow binned cpus, MAKE SURE YOU SET THE MIN VOLTAGE TO 700. Or you will get random reboots like crazy. On a side note. I would strongly suggest wiping dalvik (art) and cache before flashing. If not, your device may shutdown immediately after it is done booting. Nothing to really worry about, just simply hold the power button for a few seconds till the google screen appears, and you should be good.
Nexus-4-Mako-LightningZap_p5.1.0.zip (dl link unavailable)
Major upstream update (166 commits)
TCP tweaks
Added GCC optimizations
Updated linaro toolchains
If you are having random reboot issues or you get stuck on the Google screen, try raising your min voltage to 700MHz. If that still doesn't work, let me know here. Please try to attach a dmesg log and make sure you tag me in the post so I don't miss it (@thomas.raines)
Enjoy!
Nexus-4-Mako-LightningZap_p5.0.2.zip
Added intelli_plug to handle CPU hot swapping
Disbabled MSM_HOTPLUG
Bumped to 5.0.2
Set min CPUFREQ to 9450
Changed Aroma installer defaults to my recommendations.**NOTE** If overclocking, I recommend using higher voltage min...
Included a LightningZap! tailored init.mako.rc that sets vibrator amp to 100, disables all that unneeded cpu governor junk and more...
Nexus-4-Mako-LightningZap_p5.0.1.zip
Bump to 5.0.1
added 5.0 emmc support
speedup /proc/net/unix
network speed tweak
exec_hardboot:updated with more current patch.
Avoids bogus error messages for the suspend aborts.
Avoid using global variable total_cpus
added sound control Thanks @faux123
Nexus-4-Mako-LightningZap_p5.0.zip
Update kernel to Lollipop 5.0
Added script to fix wonky sdcard issue. (5.0 was changing it from /sdcard/<your files> to /sdcard/0/<your files>. Script prevents that from happening and all is well)
All the same greatness of Lightning Zap! 4.4.X with no issues
Enjoy folks!
Nexus-LightningZap_p4.4-3.3.zip
Added remaining uv options to table
Backlight dimmer options
USB Fast Charge
CPUFREQ:rework of all tables. New implementation of freq's using PVS.
cpufreq: properly sync current scaling governor across all cores
Slight boost in L2 cache. Corrected number of cpufreqs
enable max screen off freq on/off support
added RESTRICT_ROOTFS_SLAVE
Added fsync on/off support:Enabled by default
Added f2fs and exfat support
Inspired by elementalx's flashing format using Aroma Installer, I have revamped cpufreq and uv tables, as well as added a few options.
You can now set your default options with the installer. Just follow the prompts as you go thru.
The flashing instructions are the same; however, at the end of the flashing process, you will have an option to save the log. I would recommend doing so. But only share it with me if you have an issue.
The installer is not without it's little glitch. Occasionally, your screen might flash and appear to be going from screen to screen in recovery after the installation process has finished. Nothing to worry about. Just let it settle down and then reboot. I only had this issue in philz_touch.
With the L2 cache boost, and the lightningzap booster, those pesky random reboots due to L2 cache failing to sync are a thing of the past.
One thing to note, when selecting your cpufreq, this will set you MAXIMUM. Meaning, even with an app, you will not be able to go over the default you set. Select carefully. I would recommend setting core 1 to the highest you desire and then setting the other 3 cores lower in the case you need more. And just use trickstermod to adjust as necessary. Oddly enough, even if you set the cores individually and cores 2-3 lower than core 1, your max will be whatever core 1 was set on. But if you adjust them reverse to what I said, then you will be limited to whatever default core 1 is. Hopefully that makes sense.
I have also linked all cores. This means that when you use Trickstermod app to set your cpufreq, it applies it to ALL cores. I have notice some apps, like kernel tweaker, do not do this as they are not written correctly for multi-core processors. Most of the defaults like voltages, fsync, and sweep2* can still be controlled with trickstermod even if you disable them during install.
TBH the only thing you cannot change, is your max cpufreq (meaning, if you choose 1512(stock) as your max during install, the only way to raise it is to re-install the kernel. However, you can still fine tune it).
Another note, max freq is set to 1620; however, if you can still set it higher, will just have to use trickster mod to fine tune it...
Previous Changelogs and links
Nexus4-LightningZap_p4.4-3.2.zip
Dropped mpdecision
Added msm_hotplug (With updates)Reconfigured voltage table. Boots @ 700000uV on 94500mHz
Possible UV/OV is now 600000uV min 1450000uV max (Be careful with this as too low/high for your device could cause instability. Test your settings BEFORE setting it to set at boot. If you go below the thresholds, your device will become EXTREMELY unstable, reboot, say you should have listened and then blow up in your face...lol. Not really, but it will go into a kernel panic and reboot)
And FYI, the voltages are reported in uV not mV. If you don't know, 1000uV = 1mV; therefore, the kernel boots @ 700000 is 700mV...
Nexus4-LightningZap_p4.4-3-1.zip
Added sec_dvfs_dual. All CPU's handle hotplugging better now
Added lulzactive cpu gov
add row and fiops schedulers
set fiops as default scheduler
Working on getting smartassv2 to compile...
added LCD Gamma Hack from faux kernel
Nexus4-LightningZap_p4.4-3.zip
2 stage update on this one.
Stage 1
Dropped bricked base and went back to kk4.4 (AOSP & CAF) base
Revamped OC/UV. Still compatible with Trickster Mod app
(Because I dropped the bricked base and went back to original base, you won't have full control on thermald and mpdecision for now. Working on adding it, please be patient)
Stage 2 With results of the latest poll in mind:
Dropped the following governors:
Conservative
Gallimaufry
Ondemandx
Userspace
Made Intellidemand/deadline as default
Nexu4-LightingZap_p4.4-2.zip
Complete revamp of base. Used bricked kernel as base (thanks to show-p1984)
Created new branch for revamp (bricked-lz) Keeping kk4.4 branch for now.
Per user requests:
Moved RootBrowser to /data **Must remove it from /system/app prior to flashing
Removed voltage control app. No longer compatible with vc.
Fully compatible with TricksterMod app
Vote on the next poll for your favorite governor & io-scheduler (If I can get it setup right)
Nexu4-LightingZap_p4.4-1.2.zip
Reverted back to Linux Android Kernel version 3.4.0 due to instability
Bumped to p4.4-1.2
Revamped mako_defconfig in order to enable loadable modules
changed build cifs & tun as modules
Left WiFi modules as hard-coded drivers to avoid WiFi issues on other Roms (Sorry about this one guys and gals)
Nexus4-LightningZap_p4.4_1.1.zip
Bumped to latest stable kernel version 3.84.4 (LightningZap version p_4.4-1.1)
Added sweep2wake and doubletap2wake from bricked-kernel Mako (special thanks to show-p1984)
sweep2wake and doubletap2wake is disabled by default. To enable one or both, refer to this post
Nexus4-LightningZap_p4.4_1.zip
Initial release
Just a note, some combinations of governors and io-schedulers don't mix well and you could experience instability like freezes and reboots. Before posting an issue, change your governor and or io-scheduler. This will help me narrow down any issues. And by all means, please let me know which combination you experienced an issue with, and what exactly occurred.
Note that certain ROMs like Omni and Ubuntu Touch that use a modified initramfs or some other kernel modification, may not work with this kernel. I am working on it now.
thomas.raines said:
Hold up... getting the link now
Click to expand...
Click to collapse
Great seeing you here! My brother uses your kernel on his E4GT and he likes it a lot.
I hope you do good work for the N4 as well. :good::good::good::good:
thomas.raines said:
Hold up... getting the link now
Click to expand...
Click to collapse
The OP says it's for Blaze 4G You might want to edit it to avoid confusion Thanks for your work, sir. I had use yours in my Blaze 4G.
Maybe a bit explanation of governors? Like for lionheart and galli
Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
Wow I saw you in the Blaze fourms. Great to see you developing on the N4!
Sent from my Nexus 4 using xda app-developers app
Saw you in the et4g forums
Sent from my Nexus 4 using Tapatalk
I'm glad people say this is real looked like a hoax to zap my n4!
So who has flashed this?
sent from a toilet...
phone always fc's for me on 3 different AOSP roms
Thanks for the kernel......Testing-----------------:good:
CallMeAldy said:
phone always fc's for me on 3 different AOSP roms
Click to expand...
Click to collapse
Can you be more specific?
CallMeAldy said:
phone always fc's for me on 3 different AOSP roms
Click to expand...
Click to collapse
by chance you tried it in the rom Purity? by that I have not had problems with.:good:
Hello.
Thank you for you hard work.
I was wondering which governor and scheduler do you suggest.
Edit : Can you possibly add swipe to wake?
Yadro said:
Hello.
Thank you for you hard work.
I was wondering which governor and scheduler do you suggest.
Edit : Can you possibly add swipe to wake?
Click to expand...
Click to collapse
The governor and scheduler really varies from person to person and dependent upon their usage of the device. I think Lionheart with noop is a great combination for power and battery saving from the light user all the way up to the medium user which is why I made it default. Some have suggested that intellidemand is very good as well, but sacrifices a bit of battery saving yet adds a slight bit of performance.
I have considered adding sweep 2 wake on some of my other kernels, but haven't truly decided on it yet. I think I'm going to give it a try tonight though.
Update available
Read changelog for details
To enable sweep2wake and doubletab2wake:
use an app like kcontrol
in and adb shell or in terminal on the phone type:
Code:
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/doubletap2wake
Or, I have made it even easier. In root browser, navigate to /system/etc/init.d. Open the script named 05s2w and remove the # from lines 7 and/or 8, then reboot. This will enable sweep2wake and/or doubletab2wake. You can enable both or just one of them.
thomas.raines said:
The governor and scheduler really varies from person to person and dependent upon their usage of the device. I think Lionheart with noop is a great combination for power and battery saving from the light user all the way up to the medium user which is why I made it default. Some have suggested that intellidemand is very good as well, but sacrifices a bit of battery saving yet adds a slight bit of performance.
I have considered adding sweep 2 wake on some of my other kernels, but haven't truly decided on it yet. I think I'm going to give it a try tonight though.
Click to expand...
Click to collapse
Thanks! So far i'm enjoying this kernel a lot! Working out for me on XenonHD.
---------- Post added at 08:49 AM ---------- Previous post was at 08:48 AM ----------
thomas.raines said:
Update available
Read changelog for details
To enable sweep2wake and doubletab2wake:
use an app like kcontrol
in and adb shell or in terminal on the phone type:
Code:
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/doubletap2wake
Or, I have made it even easier. In root browser, navigate to /system/etc/init.d. Open the script named 05s2w and remove the # from lines 7 and/or 8, then reboot. This will enable sweep2wake and/or doubletab2wake. You can enable both or just one of them.
Click to expand...
Click to collapse
okay i'll try that now too.
---------- Post added at 09:00 AM ---------- Previous post was at 08:49 AM ----------
Why is the default read ahead on the scheduler 16xxx? Isn't that a bit much?
M3drvr said:
Why is the default read ahead on the scheduler 16xxx? Isn't that a bit much?
Click to expand...
Click to collapse
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
thomas.raines said:
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
Click to expand...
Click to collapse
I wasn't too worried. Just wondering. Thanks! So far the new kernel very good. The first 5 minutes of it being installed there were quite a few lags and glitches. But after that, its smooth as ever!
thomas.raines said:
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
Click to expand...
Click to collapse
That's to be expected while the kernel settles in. Glad you're enjoying it!
Sent from my Nexus 4 using xda app-developers app
Should MPDecision be enabled if using the noop scheduler and Lionheart governor? Or whats your recomendation?
Hey guys,
Here is my second kernel project for you all to try. I did my first kernel project on the Google Pixel/XL.
Some may know me from my ghostpepper\butterfly Interactive governor Tweaks from the HTC 10. And later also the widely used Pnp Mod.
I hope to achieve great performance while maintaining stability with this kernel.
I did a few performance tweaks and audio tweaks.
Features are:
Included blu_active CPU governor (you have to rename system/etc/pnp.xml to system/etc/pnp.xml.bak and reboot in order to use blu_active)
Enabled MAPLE, SIO, SIOPLUS, FIOPS, ZEN, TRIPNDROID, FIFO and DEADLINE IO scheduler
Enabled advanced TCP Congestion Control
Included GPU Boost
S2S across navbar area
KCAL color calibration
Button Mapper Support
Fsync On/Off support
Green Pulsating Notification LED
Fingerprint Double Tap to sleep support
Interface to boost memory bandwith upon turning on the screen to achieve faster wake up time
Slimbus Enhancement may improve audio quality
Button Light Notification from @tbalden
IO Sched Switcher
Interface to boost UFS Storage Controller
Power Efficient Workqueues
Adreno Idler
Fast Charging
Reworked GPU Section
Before flashing don´t forget to backup your Boot partition in TWRP.
Download flashable/sideloadable ZIP for twrp:
https://www.androidfilehost.com/?w=files&flid=191735
Changelog:
0.2
https://forum.xda-developers.com/showpost.php?p=72750714&postcount=10
0.2_2
https://forum.xda-developers.com/showpost.php?p=72826947&postcount=13
0.2_6
https://forum.xda-developers.com/showpost.php?p=72894272&postcount=17
0.3_07
https://forum.xda-developers.com/showpost.php?p=73022574&postcount=36
0.4
https://forum.xda-developers.com/showpost.php?p=73293957&postcount=95
To fine tune the Kernel please use EXKM app from @flar2. Even if it´s paid this guy deserves it definitely!
Disclaimer for using blu_active!!!
you have to rename system/etc/pnp.xml to system/etc/pnp.xml.bak and reboot in order to use blu_active
I would like to thank:
@flar2 for his complete work
@tbalden for his led tricks, adreno boost etc
@Flinny for helping me with compiling the kernel!
@savoca for Kcal
@Eliminater74 for bringing me into the kernel game
@Sultanxda
@eng.stk
@osmosis
@frap129
and all others that helped me on my way
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07
Source: https://github.com/freak07/kernel_htc_msm8998
Nice to see you on board! This device deserves all the attention, happy that you joined as well.
tbalden said:
Nice to see you on board! This device deserves all the attention, happy that you joined as well.
Click to expand...
Click to collapse
Thank you for the nice welcoming
Next release will have some upstream commits
Also you all are welcome to give some feedback.
nice to see that development is kicking up this weekend
Best kernel on Pixel XL nice to see you here. Good luck with everything :good:
So it seems that CPU OC isn’t working quite well with my chip. Tried yesterday 2,5 ghz for the big cluster and it didn’t even make it through boot process.
New release will be this evening.
Please report back how the kernel works for you.
Also please state the model you are on. But it should work for dual and single sim I guess.
Freak07 said:
So it seems that CPU OC isn’t working quite well with my chip. Tried yesterday 2,5 ghz for the big cluster and it didn’t even make it through boot process.
New release will be this evening.
Please report back how the kernel works for you.
Also please state the model you are on. But it should work for dual and single sim I guess.
Click to expand...
Click to collapse
Bro I think overclocking is really not necessary with our SD 835
=dave= said:
Bro I think overclocking is really not necessary with our SD 835
Click to expand...
Click to collapse
Yeah that’s true but it’s nice to explore all possibilities. That’s what xda is about.
Update to 0.2
Hey guys and girls,
here is the update to 0.2
includes all previous features
Changelog:
- patches to loadavg
- Upstream: reimplement mb2cache
- mm: slub: Default slub_max_order to 0
The kernel runs really nice for me.
Download: https://www.androidfilehost.com/?fid=889764386195910663
Have fun with it and a nice day
P.S.: Next release will have some surprises. But I want to make sure it is stable.
Thanks for your work, i will give this a try
So how is everyones experience?
new kernel release will be soon :victory:
Update to 0.2_2
Hey guys and girls,
the promised update is here. It may not seem like much but I managed to put a few new things in the kernel.
I had a play with different IO schedulers. As you may have noticed the new storage of our device is already blazing fast but I tried to make it even faster.
So I managed to built in the maple Io scheduler from @frap129. It results in slightly better IO speeds than stock in my tests. But this is only the first part of the IO journey.
Next release will have another IO gov, but I try to optimize it first and test it extensively.
additionally this kernel now includes the IO sched switcher from @Sultanxda
Description is as follows:
"This driver changes the I/O scheduler for a specified request queue to
Noop when the screen turns off in order to improve power consumption while
the screen is off, as well as reduce resume latency when the screen is
turned back on. After the screen is turned back on, the driver will change
the I/O scheduler back to what it originally was after a 10000ms delay."
This means screen turns on faster and phone will drain less battery when in deep sleep. :good:
In addition to boosting DDR bandwidth we now also give a boost to our storage when the screen gets turned on.
Changelog 0.2_2:
- included maple IO scheduler from @frap129
- included IO switcher from @Sultanxda
- boost ufs storage controller when turning the screen on.
- included BLN from @tbalden ( give him a big thanks!)
Download: https://www.androidfilehost.com/?fid=817550096634782138
have fun with it and happy flashing!
Donations are not mandatory but always welcome
Donate: http://paypal.me/freak07
P.S.: there is more to come.
Freak07 said:
Hey guys and girls,
the promised update is here.
Click to expand...
Click to collapse
Just flashed today. Running very fast and smooth. I'll see about battery life tomorrow. Excellent job on this.
Good Job! Thanks for your work
Battery life seams better for my usage. Haven't experienced any lag. Everything is smooth. I'm not much of a gamer, but have played a couple an they are smooth as well.
Update to 2.2_6
Hey guys and girls,
Update time again.
New version 0.2_6. I ran this for a week and it is absolutely stable for me.
Changelog:
- some backport and upstream patches
- add backlight dimmer
- optimize for performance instead of size ( that is also why the download is ~1mb bigger)
- enable RCU boost to decrease latency even further
- set timer for interrupting the kernel to 300 (performance increase)
- random driver from linux 4.12
- add tripndroid IO scheduler
Download:
https://www.androidfilehost.com/?fid=673368273298968729
Have fun with it. The kernel flies for me now. Well even more than before!
Quite happy about the battery life.
Without power saver, medium usage I would say :good:
Fantastic! Just curious, do you run this on stock ROM or one of the customized ones?
doyou37 said:
Fantastic! Just curious, do you run this on stock ROM or one of the customized ones?
Click to expand...
Click to collapse
I am currently on viper rom because I had to test if the kernel runs on the new base.