Ladies and Gentlemen,
It gives me great pleasure to introduce to you an unofficial port of the Z1
Pimped Kernel
This is a kernel for CM11 based ROMs and uses -caf. If your ROM isn't faily new and doesn't use -caf then don't expect this kernel to boot. It was built inside Carbon and I have tested in there, it should boot CM/FXF, SlimKat, LiquidSmooth, Carbon, Omni, etc. I don't know how well it will boot PA/PAC/etc that are further away from this codebase but you are welcome to try. As this is a first build so expect some FCs and reboots, and and not all features will work. Please read the OP to see what is on offer. Things that won't work are LCD/Touchscreen/DT2W, and others may be prone to bugs.
This has kernel is built with Linaro SaberMod Toolchain 4.7 and -O2 etc optimisations (not as many as the slimkat kernel). Performance seems good, and the ability to underclock/volt and turn off cores should give extra battery life.
Please don't use this unless you know how to get out of trouble/bootloops/non-boot/lost recovery/etc. I nor Androguide.fr take any responsibility for dead or undead Z-Ultras
Kernel features are controllable through Androguide.fr's Pimp My Z1 app, (thread here).
{
"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"
}
Download:
togari-BluePimp-4.4.4-dt2w-ext4-20140810_1122.zip
Very minor change to LEDs, and boot splash http://forum.xda-developers.com/devdb/project/dl/?id=7497
test v0.3 for new 4.4.4 AOSP/cm-11 ROMs
togari-BluePimp-108-dt2w-ext4-20140709_1741.zip
old 4.4.4 and 4.4.2/3 ROMs
30/6/2014 4.4.4 build with dt2w
Build 4 31-05-2014
Build 4 31-05-2014 dt2w
Features (C&P from OP):
Sound Control: Faux123's GPL Sound Control 3
Color Calibration Control: LCD_KCAL interface ported to the Z1 by @DooMLoRD, gives full control over the RGB channels of the display
GPU OC: 200MHz / 320MHz / 389MHz / 487.5MHz / 533MHz / 600MHz frequency scaling steps
CPU OC: up to 2.26GHz
CPU Voltage Control: use TricksterMod for the moment
DoubleTap2Wake: double-tap the screen to wake-up the device
Intelliplug: Faux123's latest intelliplug hotplugging driver with eco mode (v5.0)
[*]MPDecision: showp1984's open-source & customizable msm_mpdecision hotplugging driver
Dynamic Fsync: Faux123's Dynamic File Sync v1.5
PowerSuspend: Faux123's power_suspend driver (replacing early_suspend)
Snake Charmer: Faux123's msm_cpufreq_limit CPU frequency limiter driver
Fast Charge: Faux123's fast_charge driver, allowing to set the amperage of the charger or USB port your device is plugged-in to
CPU Boost: Faux123's CPU Input Boost module (will soon add controls for it in Pimp My Z1)
GPU Wake-on-touch: allows touch events to wake the GPU if it was previously in slumber
KSM: Kernel Same-page Merging enabled
F2FS Support: Samsung's F2FS nand-optimized file system support
exFAT Support: Samsung's open-source exFAT driver
zRam Support: support for zRam memory compression
CPUPower: Linaro's cpupower PM driver
Async Fsync: Asynchronous file sync
MSM_Sleeper: Support for setting the max CPU frequency when screen is off through sysfs
Kernel mode NEON: NEON-accelerated XOR framework & support for NEON instructions in kernel mode
Overall Stats: CPU overall stats on a per-core basis
Compression: XZ Compressed & LZ4 compression algorithm support
Sched MC: Multi-Core Power Savings support
Sched SMT: Multi-Thread Power Savings support
Arch_Power: arch-specific power sched features enabled
Workqueue: backported from kernel 3.7, allows CPU hotplug to keep idle workers (learn more)
Toolchain: Built with Linaro GCC 4.8
Optimizations: Built with -O2 and many optimization flags
Kexec-hardboot ?: attempted to port @Tassadar's kexec-hardboot patches from the nexus 5, needs testing and confirmation that it works
Additional Governors:
Intellidemand
Intelliactive
Pegasusq
Nightmare
Hyper
Alucard
InteractiveX2
SmartassV2
Lagfree
Wheatley
Lionheart
Badass
Additional I/O Schedulers:
SIO (SImple Ondemand)
FIOPS (Fair Input/Output Per Second)
BFQ (Budget Fair Queueing)
VR
Additional TCP Congestion Algorithms:
BIC
Westwood
HSTCP
Hybla
HTCP
Vegas
Veno
Scalable
LP
YeAH
Illinois
Click to expand...
Click to collapse
Change Log:
http://forum.xda-developers.com/showpost.php?p=50603486&postcount=2
Sources:
Androguide.fr kernel sources: PimpedKernel
My additions for the ZU (see BluePimp branch): BlueEther
Credits:
Thanks to Androguide.fr fro bringing all of the together
Thanks to faux123 for all his contributions to the android kernel community, many of which are implemented here
Thanks to showp1984 for his msm_mpdecision hotplug driver
Thanks to DooMLoRD for all the cherry-picked features from his DoomKernel
Thanks to krabapel2458 for the inital port from DoomKernel of features like GPU OC, some governors and more.
And of course, thanks to FreeXperia and Kali- in particular, for the device bring-up
Click to expand...
Click to collapse
Disclaimer:
# Neither I nor any contributors to this kernel can nor will be held
# responsible for any damage or any kind of problem related to its use.
# You are using this piece of software AT YOUR OWN RISK.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
Click to expand...
Click to collapse
Disclaimer #3, I'm not responsible for dead or undead Z-Ultras from using this ROM and kernel, OC at you own peril
XDA:DevDB Information
Unofficial Pimped Kernel, Kernel for the Sony Xperia Z Ultra
Contributors
blueether, Androguide.fr, DooMLord, faux123, krabapel2458, FXP/CM, Kali-, reaper61616 (dt2w)
Kernel Special Features: Sound Control, GPU OC, Intelliplug, PowerSuspend, Dynamic Fsync, exFAT, F2FS, KSM, Intellidemand, Intelliactive, SmartassV2, InteractiveX2, Lionheart, Wheatley, Badass, Lagfree, BFQ, SIO, FIOPS, Westwood, Hybla, HSTCP, HTCP, Veno, Illinois, LP, BIC...
Version Information
Status: Testing
Created 2014-04-25
Last Updated 2014-08-09
What's working and not
Kernel Bugs:
Camera FCs - maybe more of a CM issue than this kernel
Tested ROMs:
Carbon - (non public test build): Working
Carbon - Build 8: Working
SlimKat: Working
LiquidSmooth: Working
FXF CM11: Working
CM11: Working
AOSP: Not tested yet
AOKP: Not tested yet
AICP: Not tested yet
Lungo: Not tested yet
PAC-man: Not tested yet
PA: Working
Chameleon OS: Not tested yet
GPe: Won't boot
Quick run down using Pimp my Z1:
CPU
Min/Max works after a save (pressing 'Done' does nothing?)
[*]Per core Looks to work
[*]Interactive/performance/ondemand and conservative all seem to work as expected
TCP not tested
GPU
Min/Max (200/450) Looks to work
[*]Performance/msm_cpufreq/msm_adreno-tz/powersave/etc all seem to work as expected
cpubw_hwmon reboots the ZU
Power Managerment
Multi-Core Moderate hard to tell if working
[*]Multi-Core Aggresive Looks to work as expected
[*]Intelli plug and eco mode - Look to work well except Pimp my Z1 FCs when trying to change # of cores and gets stuck on 1
Power suspend not tested
LCD Colour
Voltage controle - looks to be working
I/O, Memory and Misc. not tested but options look to work
Sound Control
Speeker Gain works
not tested the others
Touchscreen
None are active - as expected
And i am subscribed to this
Keep it up mate xD
joluke said:
And i am subscribed to this
Keep it up mate xD
Click to expand...
Click to collapse
Build 2 Uploaded.
2014-04-24
Updated to Linux kernel version 3.4.86
Re-added GPU OC up to 600MHz and hopefully fixed the issues some people had with it
Added zRam support (thanks to DooMLoRD)
Added msm_sleeper (thanks to DooMLoRD), controls coming to Pimp My Z1 soon
Added memutils optimizations (thanks to DooMLoRD)
Merged a lot of slimbus/slim-ngd/slim_msm/qdsp6v2/wcd9xxx & other audio-related optimizations from franciscofranco's nexus 5 kernel
Merged some OOM, ocmem & other memory-management-related optimizations from franciscofranco's nexus 5 kernel
Merged a fix for msm_z180 memory leak from franciscofranco's kernel
Some other random cherry-picks
Use caution when OCing the CPU/GPU
blueether said:
Ladies and Gentlemen,
It gives me great pleasure to introduce to you an unofficial port of the Z1
Pimped Kernel
Click to expand...
Click to collapse
Thanks, we will test. Good modifications.
Kernel v2 boots and works with slim kat ,thanks bro [emoji106]
t0pstar said:
Kernel v2 boots and works with slim kat ,thanks bro [emoji106]
Only display settings from the pimp my app don't work (dt2w,s2w ...)
Click to expand...
Click to collapse
Does the camera work? Just had a FC than couldn't connect
DT2W/S2W/etc all use a different touch-screen driver than we use on the ZU
blueether said:
Does the camera work? Just had a FC than couldn't connect
Click to expand...
Click to collapse
When I open camera directly after boot it works fine ,
when not I have also FC
Im using camera kk app and it works fine. Just first time camera is not moving (it stops on first "seen" frame), but it is on every kernel (maybe rom's, maybe app's bug) and after killing it in recent apps and starting again everything works fine
Strange for me is that this kernel has more governors etc, and i always thought that coz it we should have less ram, and there is more than ie unofficial slimkat kernel
Edot: Is there any chance for f2fs version in the future? Its a lot better than ext4, so it can make our ZUs fly even better than now
Sent using C6833 - Carbon KitKat/Pimped Z1 Kernel
ch3mn3y said:
Im using camera kk app and it works fine. Just first time camera is not moving (it stops on first "seen" frame), but it is on every kernel (maybe rom's, maybe app's bug) and after killing it in recent apps and starting again everything works fine
Strange for me is that this kernel has more governors etc, and i always thought that coz it we should have less ram, and there is more than ie unofficial slimkat kernel
Edot: Is there any chance for f2fs version in the future? Its a lot better than ext4, so it can make our ZUs fly even better than now
Sent using C6833 - Carbon KitKat/Pimped Z1 Kernel
Click to expand...
Click to collapse
after a bit of flashing and testing the no outgoing calls is a bug in the test build of Carbon not this kernel so all is good on this front.
This kernel boots the last couple of Carbon builds, back to at least the 19/4 so that's another plus.
I'd not really had the camera issue that many people had had in the last few weeks on the CM based ROMs so it's sort of new for me.
You made it!!! Congrats and THANKS! Perhaps it's time I go back to a non-stock ROM now, just to try this kernel...
I found other problem (at least for me) with pimp my z1. I cant set 2nd core governor, coz it always return to intelliactive last saved? (im not sure as sometimes it stays on last saved sometimes on earlier), now, as i know how it works, its not the problem to set governor I want, but its strange bug. I would use trickster but there I cant set different governors for every core (As i found out set governor is only for first core)
EDIT: Maybe someone answers: What is Pen Mode in this app? If it is what I think we dont need it as our phone support mostly everything as a pen. The same for gloves i think
Has anyone tried this Kernel on CM11, if so any problems?
Sent from my Xperia Z Ultra using Tapatalk
Next few things:
-
1. After reboot very often CPU governors are changed.
2. Additionaly to setting governors: They are setting itself. Before I set nightmare/nightmare/powersave/powersave and after going back to menu and againd CPU Control it was nightmare/<last saved?>/powersave/powersave. Now after reboot it was nightmare/nightmare/nightmare/nightmare (with per-core on) and after menu->CPU Control nightmare/intelliactive/powersave/powersave (intelliactive wasnt last saved or anything)
3. Sometimes after reboot Pimp my Z1 returns GPU settings to default ones
4. Power Managments, I/O tweaks, Memory managments too - Misc on the other hand are always remembered correctly
Yes I have "set on boot" on. Strage coz mostly (4/6 for now) everything is remembered correctly ie now after next "test" reboot
ch3mn3y said:
Next few things:
-
1. After reboot very often CPU governors are changed.
2. Additionaly to setting governors: They are setting itself. Before I set nightmare/nightmare/powersave/powersave and after going back to menu and againd CPU Control it was nightmare/<last saved?>/powersave/powersave. Now after reboot it was nightmare/nightmare/nightmare/nightmare (with per-core on) and after menu->CPU Control nightmare/intelliactive/powersave/powersave (intelliactive wasnt last saved or anything)
3. Sometimes after reboot Pimp my Z1 returns GPU settings to default ones
4. Power Managments, I/O tweaks, Memory managments too - Misc on the other hand are always remembered correctly
Yes I have "set on boot" on. Strage coz mostly (4/6 for now) everything is remembered correctly ie now after next "test" reboot
Click to expand...
Click to collapse
I'm wonder if it is more the app than the kernel?
I have managed to peg the first core at fill tilt once and another time to have all 4 core online all the time. The second issue can be solved by turning all the options off in Power Management, it's a known race condition by the looks.
~5% battery drain over night, but it looks like google services are causing wakelocks again on my ZU
Its hard to say coz there is bo more apps which can let to use most od options kernel has (ie trickstermod let set governor for all, i/o too for both memories). But i would think its app+phone compatibilty issue not kernel, but not sure about it
Sent using C6833 - Carbon KitKat/Pimped Z1 Kernel
Just flashed this kernel with the latest carbon rom and working great very fast will test for the next few days and see how the battery life is - thanks for the great kernel
Sent from my SM-T320 using XDA Premium HD app
blueether said:
~5% battery drain over night, but it looks like google services are causing wakelocks again on my ZU
Click to expand...
Click to collapse
After first night it was worse for me - 13%. It coukd be coz kernel was just flashed ot coz my set up, but its too much
But this second core governor annoying.me too. I found out that if i set it few times it stay till sometime after reboot (just after reboot and getting su rights, governors are right(. Anyone has similar problem? Can moving app to system/app helps?
Sent using TF300T - CyanogenMod 11.0/GEASS (F2FS)
ask
it work with this rom
http://forum.xda-developers.com/showthread.php?t=2606414&page=71
mimoun103 said:
it work with this rom
http://forum.xda-developers.com/showthread.php?t=2606414&page=71
Click to expand...
Click to collapse
No it wont, this is for AOSP/CM11.
The Port of DooMLorD's kernel is much the same feature wise and will work with monx's rom
Related
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.
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"
}
This kernel can be used on any JB CM BASED JB 4.1 or 4.2
Disclaimer
Code:
[COLOR="DarkOrchid"]#include[/COLOR] [COLOR="Magenta"][/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)
Bluetooth
Everything Else that works on FXP and any other JB kernel
What doesn't work --
Anything that doesn't work 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!
Intellidemand2 - Thanks to faux123 and CosmicDan for mods
Uses d_bus ramping, quick and smooth and performance based, do not complain about battery drain on this
governor but it will make everything feel more like project butter
What else-----
-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).
- Alot of changes to code to try improve smoothness ect
- Wifi signal lock on should now be quicker / stronger then before
--When LEDS change green, pink then blue press volume down to enter CWM Recovery
I would like to say a big thanks to -
slz.kiev - for amazing PACman ROM & Testing
FXP - Sources
Cyanogenmod - Souces
DooMLoRD - Everything he's done for XPeria
wechy77 - For helping me test
tempest918 - For the New Logo
xeozus
NobodyAtAll
Faux123
Erasmus
Leedroid
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
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.
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.
Changelog ...............
Code:
[hide]
[B][v1] [/B]
- Initial release
- 25 Governors
- 6 Io-Schedulers
- SLQB memory allocator
- Built with linaro 4.6 toolchains
- Swap
- Zram enabled
- Custom voltage control supported
- Supports USB OTG
- Supports ext2, 3 & 4
[B][U]v2[/U][/B]
- Couple of extra tweaks - improvements to battery
- Fixed Wifi issues
- Reverted my disabling of disabling sched_feautures if you get that :P
- Added USB OTG modules needed for USB OTG ( find attached zip at the end of the post)
- Added stable freq-table for higher OCing upto 2ghz
[B][U]v3[/U][/B]
- Completely scrapped previous sources and started fresh
- CWM fixed thanks @ Scritch007
- Built with Linaro 4.7
- Optimized for Linaro
- Thumbee
- Reverted to 1.6 max OC
- Lzo patched
- Use Google Snappy Compression / Decompression
- Added TINY RCU
- Fixed Battery drain ( Tester lost 0.2% overnigh with wifi on ) :victory:
- Uses uncompressed Image {why .img size is bigger)
- Custom improvements for overall smoother performance
[B][U]v4[/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
- TWRP recovery - thanks @ championswimmer & TWRP team
[B][U]v5[/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
- Thanks [user=4402161]@Wechy77[/user] for LuPuS TWRP theme
[B]v6[/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]v6[/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]v7[/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 [user=2799345]@M66B[/user]
[B]v8[/B]
- Fixed reboot to recovery on 4.2 (not sure if i broke it on 4.1)
---- 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]v9[/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-Jellybean-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.
480p
LuPuS_urushi_jBv9-ram.img
md5 = 3ff24d7e343beb483aa81d7bcfa1b5f5
[/LIST]
720p
LuPuS_urushi_jBv9.1-full.img
md5 = 1effb6e2ba80afbb55d1bd9d30a426fd
[/LIST]
Mirrors -- all LuPuS Kernels can be found here
www.goo.im/devs/wedgess
Wifi is built in to kernels ramdisk NO MODULES NEEDED
If your MD5 doesn't match re-download
Everithing works fine so far. See benchmark scores.
Sent from my Xperia Ray using xda premium
Wow...nice one! Really responsive! Just wanted to point out that in addition to all the features listed in the OP, that you can undervolt
with this kernel....didn't see it as a feature in the OP...
Thanks!
justmpm said:
Wow...nice one! Really responsive! Just wanted to point out that in addition to all the features listed in the OP, that you can undervolt
with this kernel....didn't see it as a feature in the OP...
Thanks!
Click to expand...
Click to collapse
Lol ye i forgot to add it in to op thanks for reminding me.
Edit- Put of couple of more things into 3rd post, anymore I can remeber will be added
Sent from my GT-I9300 On Official JB
wedgess said:
Lol ye i forgot to add it in to op thanks for reminding me.
Edit- Put of couple of more things into 3rd post, anymore I can remeber will be added
Sent from my GT-I9300 On Official JB
Click to expand...
Click to collapse
very smooth, but has a problem the wifi seems works not stablely, sometimes cause reboot and sometimes cannot been disconnected.
feelow said:
very smooth, but has a problem the wifi seems works not stablely, sometimes cause reboot and sometimes cannot been disconnected.
Click to expand...
Click to collapse
Did you reboot? I have no problem with wifi. Only at first boot I had this problems.
Sent from my Xperia Ray using xda premium
testing...
(thx for your effort sofar :good
1st impression: lower scores on Antatu than with standard PAC-kernel.
i'd like to have a better battery life, so now testing "virtuous/sio, 806/134".
or are there better suggestions?
(like to keep a snappy Ray )
"Custom voltage control supported" not working. The PAC romcontrol says: not supported by your kernel
Wechy77 said:
"Custom voltage control supported" not working. The PAC romcontrol says: not supported by your kernel
Click to expand...
Click to collapse
I don't think that part of RC has been activated....it also doesn't work with the kernel from champilnswimmsr's aokp build. I am using incredicontrol from the play store...but a lot of other apps will let you change the volts.
justmpm said:
I don't think that part of RC has been activated....it also doesn't work with the kernel from champilnswimmsr's aokp build. I am using incredicontrol from the play store...but a lot of other apps will let you change the volts.
Click to expand...
Click to collapse
is there a list of recommended (or safe) voltage settings for the Ray?
Yes i know in rom control it still says not supported not sure why but u can always use SetXperia app from playstore to change it
And poster who asked about safe settings. Try down step -25mv at a time and see what is stable for you. If u get reboots then its obviously not stable.
Or else safest way if your wortied then dont undervolt at all. What maybe stable for someone might not be stable for you
Sent from my GT-I9300 On Official JB
I tryed thi kernel for my CM10 rom. And it seems buggy. Antutu points is lower than on stock kernel, and the perfomance is bad too, including games and UI.
_TREM_ said:
I tryed thi kernel for my CM10 rom. And it seems buggy. Antutu points is lower than on stock kernel, and the perfomance is bad too, including games and UI.
Click to expand...
Click to collapse
lol ok first off this is not stock kernel so you can't compare it to STOCK,Ssecondly i'm not sure what governors, io scheds and frequencies you are using. People who have tested have reported it being smooth and performance being greater not worse. Also I obviously use my own kernels on my own device and my experience is the complete opposite of yours. You sure it not 'your' CM10 rom. Buggy!! how? please do elaborate.
Anyone else confirm what the above pster has said ??
Using it now for some hours with Virtous and SIO and looks very promising. Speed of ROM is for me the same and I dont play games. But Battery seems to be great! I left the screen off a lot and have like 95% deep sleep, so pretty well battery ;D I use FXP142.
EDIT: just tested the game "granny smith'. Runs good! But I didnt test with another kernel.
[GER]Roxxor said:
Using it now for some hours with Virtous and SIO and looks very promising. Speed of ROM is for me the same and I dont play games. But Battery seems to be great! I left the screen off a lot and have like 95% deep sleep, so pretty well battery ;D I use FXP142.
EDIT: just tested the game "granny smith'. Runs good! But I didnt test with another kernel.
Click to expand...
Click to collapse
Ye virtuous is supposed to be more battery friendly then smartassv2
Intellidemand2 would be best performanced based but not the best on battery.
Sent from my GT-I9300 On Official JB
Thanks for the great kernel, really liking the Superbad governor.
I left my ray on during the night, to see what the battery would do...
(i mean screen off, but wifi+3g on)
from 100 to 74% in 9 hours.
8:40 deep sleep (94%)
806/134 virtuous/sio
I cannot compare btw, usually i charge at nighttime, but usage seems quite high?
was hoping for about 90% battery left or something, but like i said, not tested with other kernels.
I think I caught a "wifi" bug. Yesterday the wifi cut out and wouldn't turn back on...after rebooting everything was fine for a few hours and then wifi stopped working. I am not sure if it is really wifi or something else, because if I go into settings I see that wifi is on, I can turn it off but it won't turn back on...if I leave settings and pull down the status bar it show wifi as "on"...when I go back into settings it shows wifi as "on"...and no networks are shown that can be connected. You can do this over and over and every time you reenter settings it says wifi is on. I think it also causes a wakelock from wifestatemanager.
I went into recovery and formatted system and reinstalled PACman v15...a few hours later the problem returned. I flashed in a different kernel and it seemed OK....now I have your kernel on ChampionSwimmer's AOKP ROM and I am waiting to see if the bug returns.
I am not sure if there is something specific I do that activates the bug, so I don't have a logcat of it happening. I attached a logcat of me trying to turn on and off wifi in settings. I also attached the battery stats report from Better Battery Stats in case the wakelock is informative....
{
"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"
}
Click to expand...
Click to collapse
"This is your last chance.
After this, there is no turning back.
You take the blue pill -
the story ends, you wake up in your bed and
believe whatever you want to believe.
You take the red pill
- you stay in Wonderland and
I show you how deep the rabbit-hole goes."
- Morpheus, The Matrix
(Copyright belongs to the Wachowski Brothers... Larry and Andy)
Click to expand...
Click to collapse
Kernel Source: RedPill Source Based on N7100 Source Drop (until Rev1.00). Rev1.01 and beyond are currently based on N8000 sources. This Kernel is for the N7100 International Version Only!!!
MatrixPills Image by Corinne Wilger. Visit her site HERE.
What Some HyperDroid RedPill Users Have Said:
"so far this the only kernel which gives me the least wakelocks.. or hardly any.... good job..
i dont care about benchmarks which ppl are whining about.. i would say this kernel rockz" - xinfinityoO
Click to expand...
Click to collapse
"Batterywise the best kernel on my device - had not encountered just 2% loss in 7 hours at night for a very long time"- zikarus
Click to expand...
Click to collapse
"first impressions... blazing fast...smooth... hopefully no issues
(well never had one with previous releases anyways)...cheers pongster!"- jermitano
Click to expand...
Click to collapse
"I am stunned. The battery life looks great. Very smooth and stable and great response. Great work guys."- mariosraptor
Click to expand...
Click to collapse
"Awesome work! That's the least I could say. Real development and all that done during free time.
I've made donations but that won't be enough to show my gratitude. I know you don't do that for money but
that's the only way I can think of tell you all how grateful I am."- mbutandola
Click to expand...
Click to collapse
Click to expand...
Click to collapse
RedPill Features
Highlights
Exynos-Abuse Secured (Thanks to AndreiLux for the original low level patch & Samsung for the Official Fix)
SDS patch included
Ramfs from Stock Kernel + Busybox and its various functions in /sbin
Versions up to Rev1.00 were Based on Samsung Galaxy Note 2 N7100 Source Drop Release 1; Rev1.01 and up are based on N8000 Sources
Included patches for performance, stability and battery life
Init.d support
SetCPU, ROM Toolbox and Voltage Control Support
CPU Overclocking and Undervolting Support (Thanks to AndreiLux)
GPU Overclocking and Undervolting Support (Thanks to AndreiLux)
Enable or Disable File Syncing
(fsync disabled by default as I've tweaked the system for optimum latency designed for Flash Storage)
CFS Autogroup by Mike Galbraith Enabled
CPU Topology and Sched_MC enabled
AFTR and LPA enabled
A lot of tunables via sysfs included (Use ROM Toolbox or similar Utility to easily change it)
Git Implementation of SHA-1 for 12% faster boot time
CPU set at 1.6Ghz at Boot for faster boot time (Thanks to Imoseyon)
LZO compressed kernel using optimized values for the size of the kernel for faster boot time (Using faster lzo code from mainline)
CIFS Support (cifs.ko located in /lib/modules) | Tweaked Ext4 Filesystem
(Patches + Mount Options + Tweaked IO Schedulers leaning towards latency for Flash Storage)
sio | zen | row | noop | deadline (tweaked for better latency and balanced throughput for Mobile NAND based devices)
Tweaked the mount options for Ext4 to adapt to the current focus on latency
pegasusq CPU Governor (Thanks to AndreiLux for the some of the new governor specific logic he added)
WiFi Multicast Blocked (Thanks to Entropy512)
Using Google Toolchain 4.7 + compiler optimizations specific for that version (Thanks Google & Linaro)
Power Saving Features:
AFTR + LPA enabled
sched_mc enabled (set at 2 by default)
ARM CPU Topology enabled
No HZ enabled
Boot Time Features:
Used git Implem of SHA-1 for 12% Boot time improvement
Added [PATCH] arm: remove "optimized" SHA1 routines by Linus Torvalds
Added [PATCH] arm: remove stale export of 'sha_transform' Linus Torvalds
Set Clockspeed at 1.6Ghz at Boot time to ensure all critical tasks have enough power to perform them while
the governors/maxfreq isn't set yet. (Thanks to Imoseyon for this hack)
CPU Features
Supports CPU Overclocking and Undervolting (Thanks to AndreiLux)
Supports GPU Overclocking or Undervolting (Thanks to AndreiLux)
pegasusq CPU Governor pegasusq set as default (obviously)
Filesystem Features (Currently Supported)
ExFat (Using Proprietary Samsung Modules) *Stock based RedPill only
Fat32
Ext2/3/4
CIFS (cifs.ko is in /lib/modules)
Ext2Int for N7100 (Thanks to mattiadj for idea and base script that I used to get it fully working on N7100 and RedPill) (ExFAT and FAT32 only) *Stock based RedPill only
I/O Schedulers
SIO (2012 0.2 version) (tweaked for Flash) Set as Default
deadline (tweaked for Flash)
zen (Thanks to bbedward)
noop
row (Thanks to Tanya Brokhman)
Tweaked values in deadline and SIO I/O scheduler to give better than average throughput while attemting to improve latency (if not more aggressive). Based on our initial (indicative, not conclusive... yet) testing, having these in line with the vm dirty, expire, writeback values + ext4 mount options to "schedule" write outs as fast as the system can handle it works quite well to balance throughput with latency expected in a mobile device. We took the big picture view and tested our tweaks instead of copy pasting random "known" good values and challenged some assumptions even we had at the start. The result is a mobile device tuned for average throughput and balanced battery life with good latency (not the lowest latency out there, but given the benefits of better I/O throughput and potential battery savings + extending the lifetime of NAND Based storage I think it was a compromise worth taking) I could have tweaked it for extremely great throughput and battery savings but that wouldn't be fun to use. I hate micro-lags myself.
Our Test Data regarding I/O schedulers and Kernel Tweaks can be found HERE.
The blog post that describes what we are trying to do can be found on my blog post HERE. (Thanks to s2d4)
Memory Features
Custom minfree values tweaked for 2GB RAM
Tweaked vm values in sysctl that's optimized for latency
Display Features
Stock mdnie values for more vivid details on the current generation of AMOLED Displays
Performance Patches Enabled
Mike Galbraith's Ultimate CFS Performance Patch (CFS Autogroup)
*More info on this here: https://lkml.org/lkml/2010/11/20/91
Added the CGroup Patch:*Added [PATCH] cgroup: Provides a way of tasks grouping by timer slack value
by Kirill A. Shutemov Based on patch by Jacob Pan. Introduces per cgroup timer slack value
which will override the default timer slack value once a task is attached to a cgroup. It's useful in mobile devices where
certain background apps are attached to a cgroup and minimum wakeups are desired.
Experimental Latency Related Patches
Disabled "fsync disabled" by default
(can be enabled by doing an echo "0" > /sys/class/misc/fsynccontrol/fsync_enabled
in a terminal emulator or as a script for gscript or scriptmanager) (Or use STweaks to toggle it) (Thanks to Ezekeel)
Using the tweaked Ext4 filesystem + scheduler and mount options leaning towards latency + vm values in the kernel
makes the most of the speed of Flash Storage based devices. At the speed at which the data is written to and from the kernel
to the Fast Storage devices, you would only lose up to 1 second worth of data at most IF the kernel crashes.
I don't plan on that happening so I enabled the system to get the maximum possible performance in this area.
Tweaked Ext4 Filesystem (Patches + Mount Options + Tweaked IO Schedulers leaning towards latency)
Tweaked the mount options for Ext4 to adapt to the current focus on latency
3rd Party Kernel Apps Support
STweaks by gokhanmoral
ROM Toolbox by jrummy
SetCPU by michaelhuang
System Tuner
Voltage Control | ExTweaks by xan
Credits and Disclaimer
Credits: (Huge props to all the devs I've learned from by reading and studying their code)
faux123
Ezekeel
franciscofranco
supercurio
hardcore
Netarchy
Hacre/Ninpo
Chainfire
Erasmux
Imoseyon
gokhanmoral
Tegrak
Entropy512
AndreiLux
cattleprod
dvtonder
All the hardworking Kernel Devs at lkml.org
(Linus Torvalds, Jens Axboe, Mike Galbraith, etc.)
Special Mention to the following:
To my mates at the HyperDroid Dev Team: (who help me test and refine the features of our kernel for our ROM)
D.O.C. (formerly doctorcete) (for the friendship and being an example of diplomacy in
dealing with usual ****storm of questions from users who refuse to search and read)
kristofpetho (for his excellent work on the HyperNote and his patience with dealing with bugs that destroy the user experience)
Arighi (for the initial guidance on how to get the kernel booting and working & a lot of battery driven patches)
AF974 (for the Overcome based Recovery on S2 that's so bad ass I want to stay in recovery all the time.)
petsasj (for his great work on HyperDroidParts for S2 and all future Apps that are just pure awesomesauce!)
sicopat (for letting us use his server and helping us out with a lot of things smali)
s2d4 | phly-phantom | amerikian (for testing everything at the risk of the potentially time sucking Soft Brick...)
Disclaimer: I made this for my personal use and has been personally tested by me and my team (HyperDroid Dev Team).
While it may work for other N7100 International ROM's, we have not tested it personally.
You have the liberty to choose to use this Kernel and by flashing this Kernel you will have
surrendered your right to complain that you lost your Warranty. If you're smart enough to figure
out WHY you need a Custom Kernel, you SHOULD be smart enough to undo it if you need your
device serviced officially. If your device explodes, melts or otherwise disintegrates from its awesomeness
I shall NOT be held responsible.
Reposting the Kernel: Please don't repost this kernel anywhere else.
Keep the download links intact as I have taken the effort to provide fast links for everyone.
If you can't understand English well enough and feel the need to re-post this kernel on
a foreign language web site or forum, please let me know first and link to this page...
(Google Translate can make it easier to read in your Native Language)
RedPill Stable Change Log
Current and Future Changelogs can be found HERE.
Rev1.01
Completely Rebased on N8000 Source
Use newest and official Exynos-Abuse patch from Samsung (Thanks to AndreiLux for the additional patches re: static cma regions)
Fix Freezes for some Devices when transferring large files via USB
Fix SOD for some Devices
Change CPU Idle Settings back to stock
Remove Dynamic FSync (Ability to enable or disable FSync is still available)
Removed ROW I/O as sio/deadline/zen perform better in our tests
USB Charging Rate increased to 1700
Tweaked pegasusq for battery life (limit sampling rate in suspend)
Removed Conservative (as new tweaked pegasusq can save battery with the right settings)
Added Dynamic STweaks XML Implementation by AndreiLux (Thanks to AndreiLux)
Updated STweaks (Thanks to Gokhan Moral)
use get_random_int() to fix entropy depleting (Thanks to Jeff Liu)
Updated sensorhub driver, device sensors
SDS patch included (Thanks to AndreiLux)
Rev1.00
Exynos-Abuse Secured thru the low-level fix by AndreiLux (Thanks to AndreiLux)
Using Official Google Toolchain 4.6.x
Added the latest (v5.4) of the "faster crc32 algorithm" by Bob Pearson and Darrick Wong (Thanks to both of them)
Added faux123 Dynamic fsync (Thanks to faux123)
Enable Dynamic FSync and FSync Control to co-exist (Please read STweaks option to gain a better understanding)
Backported ROW I/O scheduling algorithm (Thanks to Tatyana Brokhman)
Revert to using original N7100 source bcmdhd drivers to fix WiFi for some users
Added ability to increase brightness to 255 (Thanks to nebkat)
Tick and workqueue updates from upstream kernel source (Please see commit log for details)
Remove ntfs auto mounting since people use ExFAT and FAT32 while NTFS can be loaded by 3rd party tools
Tweaked Ext2Int mount options
Tweaked System mount options
Rev0.10
Revert ExtSdCard mount points to default (To enable Ext2Int Tweak by mattiadj to work)
Added bbedward's zen i/o scheduler (Included in Stweaks options as well)
Added Option to OC to 1.8GHz after several weeks of testing for stability (Thanks to AndreiLux)
Added AndreiLux's STweaks Dynamic Config for CPU_UV, min/max freq and i/o scheduler (Thanks to AndreiLux)
Added updated pegasusq logic from newer Samsung sources (Thanks to AndreiLux for Original Port)
Added option in STweaks to swap internal and external sdcard (Thanks to mattiadj for original idea and script, which I then took and edited to ensure Full compatibility with N7100)
Added Proportional Rate Reduction for TCP (Thanks to faux123)
Tweaked deadline i/o scheduler
Rev0.9
Added Scoobydoo Sound (gokhanmoral's port of supercurio's Voodoo) (Thanks to gokhanmoral)
Added Scoobydoo specific Stweaks presets (Thanks to gokhanmoral)
Added sjkoon's Scoobydoo Sound fixes (Thanks to sjkoon)
Added android logging as a module (Use STweaks to toggle)
Rev0.8
Added STweaks support (Thanks to gokhanmoral)
Custom STweaks Entries specific to RedPill Features
Using Latest 201211 Linaro 4.7.3 Toolchain
Added NTFS Automounting support (for sdcard formatted as NTFS only, not OTG) Please Test if this works as I use FAT32
Added led blinking or fading choice from CM10 (Thanks to codeworkx and XpLoDWilD)
Rev0.7
Added UV Capability (arm voltages only) Implementation by AndreiLux (Thanks to AndreiLux)
Increase USB Charging rate by AndreiLux
Increased it even more to match AC charging rates (Experimental)
lowmemorykiller patches by Cyanogen Steve Kondik
Experimental optimizations to try and fix ZK camFW bug
Loads of Samsung OSRC updates c/o AndreiLux (Thanks to AndreiLux)
Wacom, Firmware, epen, sensorhub, camera firmware among others c/o AndreiLux (Thanks to AndreiLux)
Bug Fixes by AndreiLux on sound related source files
Rev0.6
Wakelock patch to save power (Thanks to Andrea Arcangeli)
Apply SCHED_FIFO to kthreadd (Thanks to Steve Muckle )
Testing latest Linaro 4.7 Toolchain
Camera Fix for ZKFI07 camFW (Thanks to nebkat)
Experimental Hotplug Awareness based on Load for Other Governors (Thanks to franciscofranco)
Updated lzop compression from current upstream version for a significant speed improvement (Thanks to Markus F.X.J. Oberhumer )
ARM: disable preemption in machine_shutdown (Thanks to Mike J. Chen)
Check source on github for detailed commit logs and messages
Rev0.5
Applied Vermagic patch to enable proper loading of proprietary modules (Thanks to jt1134)
Improved Latency of schedulers
Removed cfq and enabled sio as default io scheduler
Tweaked Pegasusq for smoother performance (Can be changed using SetCPU)
Ext4 patches from mainline for optimization and stability
Workqueue patches from mainline
Timer patch from mainline
Sched Race in Task Group Patch from mainline
Busfreq back to default voltages (for public release)
Fixed ExFat Loading Error (SLUB instead of SLQB)
LZO compressed kernel for more more speed
No Screen Sharpening (Only AndreiLux's Black crush fix which is in fact for the S3. Thanks for the Heads up AndreiLux)
Removed Auto EFS Backup to speedup boot process (You have an EFS Backup already, right?)
Rev0.4
Blocked multicast (Thanks to Entropy512)
Tweaked Pegasusq to start early in the boot process
CIFS built-in (no modules)
Tunneling built-in
Testing Out ezterry's 4.6.3 Toolchain
Fsync control by Ezekeel
Increased mmc timeout (Thanks to AndreiLux)
Added a few compiler optmizations for 4.6.3 Toolchain
Rev0.3
Sharpness Tweak by Hardcore (Thanks to hardcore)
Black Crush Fix by AndreiLux (Thanks to AndreiLux)
XZ Tweaked for faster boot and more efficient RAM
Enable 1.6Ghz at Boot time to speed it up just a bit more (Thanks to Imoseyon)
Various ARM topology patches
Enabled Timer Slack Controller
Rev0.2
Adjust tweaks in ramdisk
Tweaked CFQ
SMP fixes by Russel King
XZ compressed kernel (fast and small)
ARM topology
Sched_mc set at 2
Disabled Mali State Tracking
CIFS as a module
Rev0.1
Used N7100 source drop
Tweaked deadline and sio for throughput and better battery life
Tweaked conservative and pegasusq for slightly more aggressive performance
No UV
No OC
Using new SHA-1
Enabled Cleancache
Enabled Mike Galbraith's Sched Autogroup
Applied AndreiLux's sensor hub fix (Thanks to AndreiLux)
Using SLQB
CFQ by default
Using RWSEM Algorithm by Code Aurora
Tweaked kernel values using the redpill.sh in the ramdisk
Enabled init.d
Auto Backup of EFS
Using Toolchain 4.4.3
--------------------------------------------------------------------------------------
Naming convention:
x.y.z
"x and y" means they are stable releases tested by peers worldwide and have proven to be good enough to be a daily driver.
"z" is added to connote its an unstable release that is currenty being tested for new features introduced. Not for the faint hearted.
e.g. 0.2 is a stable release; 0.2.1 is an unstable test release
features in 0.2.1 that make the cut will make it 0.3 or the next stable release and so on...
RedPill Ultimate & AOSP Changelog
**AOSP (Will work with CM10 Based ROM's only)
Current and Future Changelogs can be found HERE.
Rev0.5
RedPill Stable PLUS:
AOSP specific Ramfs Tweaks
r3p0 mali
SLQB
jRCU instead of Tree Preempt RCU (Better for low latency and designed with small SMP systems like mobile devices in mind) (Thanks to Joe Korty)
mdnie, haptic, leds and touch leds patches by codeworkx and XpLoDWilD (Thanks to codeworkx and XpLoDWilD)
Added UV Capability (arm voltages only) Implementation by AndreiLux (Thanks to AndreiLux)
Increase USB Charging rate by AndreiLux (Thanks to AndreiLux)
Check source on github for detailed commit logs and messages
Rev0.6
Added gokhanmoral's additional bcmdhd-cm for CM10 (Thanks to gokhanmoral)
Experimental optimizations to try and fix ZK camFW bug
Rev0.7
Loads of Samsung OSRC updates c/o AndreiLux (Thanks to AndreiLux)
Wacom, Firmware, epen, sensorhub, camera firmware among others c/o AndreiLux (Thanks to AndreiLux)
Bug Fixes by AndreiLux on sound related source files (Thanks to AndreiLux)
Rev0.8
Added STweaks support (Thanks to gokhanmoral)
Custom STweaks Entries specific to RedPill Features
Using Latest 201211 Linaro 4.7.3 Toolchain
Added NTFS Automounting support for sdcard (Please test this as I use ExFAT)
Rev0.9
Added Scoobydoo Sound (gokhanmoral's port of supercurio's Voodoo)
Added Scoobydoo specific Stweaks presets (Thanks to gokhanmoral)
Added sjkoon's Scoobydoo Sound fixes
Remove Debugging but keep kallsyms for Scoobydoo
Rev0.10
Added bbedward's zen i/o scheduler (Included in Stweaks options as well)
Added Option to OC to 1.8GHz after several weeks of testing for stability (Thanks to AndreiLux)
Added AndreiLux's STweaks Dynamic Config for CPU_UV, min/max freq and i/o scheduler (Thanks to AndreiLux)
Added updated pegasusq logic from newer Samsung sources (Thanks to AndreiLux for Original Port)
Added option in STweaks to swap internal and external sdcard (Thanks to mattiadj for original idea and script, which I then took and edited to ensure Full compatibility with N7100)
Added Proportional Rate Reduction for TCP (Thanks to faux123)
Tweaked deadline i/o scheduler
Updated ramfs to 4.2.1
Rev0.11
Exynos-Abuse Secured thru low-level fix by AndreiLux (Thanks to AndreiLux)
Using Official Google Toolchain 4.6.x
Added Dynamic Writeback from 3.1 (Thanks to franciscofranco for the port)
Added the latest (v5.4) of the "faster crc32 algorithm" by Bob Pearson and Darrick Wong (Thanks to both of them)
Enable Dynamic FSync and FSync Control to co-exist
Backported ROW I/O scheduling algorithm (Thanks to Tatyana Brokhman)
Added ability to increase brightness to 255 (Thanks to nebkat)
Tick and workqueue updates from upstream kernel source (Please see commit log for details)
Remove ntfs auto mounting since people use ExFAT and FAT32 while NTFS can be loaded by 3rd party tools
Tweaked System mount options
Disable Ext2Int while I find a way to get around the new emulated mounts for multiuser support 4.2.1 brings (You can still use directory bind for some games and apps with large data requirements)
--------------------------------------------------------------------------------------
ULTIMATE VERSION HAS BEEN DISCONTINUED & DEPRECATED SINCE MOST FEATURES ARE FOUND ON STABLE
**Ultimate (Will not work with ExFat since I used SLQB)
Rev0.7
RedPill Stable PLUS: (New Features In Development will be on this Release)
SLQB
Busfreq Undervolting (less 100 mV)
LCD Undervolting
Touch LED Undervolting
jRCU instead of Tree Preempt RCU (Better for low latency and designed with small SMP systems like mobile devices in mind)
Added UV Capability (arm voltages only) Implementation by AndreiLux | gokhanmoral
lowmemorykiller patches by Cyanogen Steve Kondik
Check source on github for detailed commit logs and messages
Rev0.8
Experimental optimizations to try and fix ZK camFW bug
Loads of Samsung OSRC updates c/o AndreiLux (Thanks to AndreiLux)
Wacom, Firmware, epen, sensorhub, camera firmware among others c/o AndreiLux (Thanks to AndreiLux)
Bug Fixes by AndreiLux on sound related source files (Thanks to AndreiLux)
Remove all Debugging
Added STweaks support (Thanks to gokhanmoral)
Rev0.9
Using 201211 Linaro 4.7.3 Toolchain
Added led blinking or fading choice from CM10 (Thanks to codeworkx and XpLoDWilD)
Added NTFS Automounting support
Custom STweaks Entries specific to RedPill Features
Rev0.10
Added Scoobydoo Sound (gokhanmoral's port of supercurio's Voodoo) (Thanks to gokhanmoral)
Added Scoobydoo specific Stweaks presets (Thanks to gokhanmoral)
Added sjkoon's Scoobydoo Sound fixes (Thanks to sjkoon)
Added back android logging (Use STweaks to toggle)
ULTIMATE VERSION HAS BEEN DISCONTINUED & DEPRECATED SINCE MOST FEATURES ARE FOUND ON STABLE
--------------------------------------------------------------------------------------
FAAAQ's
Kernel Frequently Asked & Answered Questions (FAAAQ)
What exactly IS the RedPill?
The RedPill is a custom kernel for the Galaxy Note 2 (N7100) International version. It's aptly named to provide users a choice. This is how I would have built Samsung's stock kernel. So, I used the Samsung Source from their site as a base and added relevant patches that are built on the shoulders of giants... such as arighi, gokhanmoral, Entropy512, AndreiLux, codeworx, netarchy, hacre, franciscofranco, Ezekeel, imoseyon, Erasmux, cattleprod, hardcore, faux123, etc. and all the kernel hackers of the world that work on making this usable for all of us... I claim nothing to be original or created by myself... I simply put together features others have created that I personally would like to see and use in my own device and share it with the world because I can AND choose to do so... While I do bugfix the occasional compile error and test for near perfection, it's nothing compared to those who write most of the code for the Linux kernel. Major props to all of them!
Where is the source for building this Kernel?
You can find the source HERE. I love GPL and We should all support Open Source Software and its Developers. Please Note that Open Source doesn't mean all of this magically wrote and patched itself... it takes a lot of FREE time to do this and would appreciate if you let us know how you've improved the code.If you know what you're doing, you can easily build your own kernel too. *Please let me know if you have any improvements you feel should be included and send me a pull request. *If it tests okay, it may be included in the next release.
FYI, I'm not particularly fond of devs who release their source as tarballs. (I'm looking at 'ya Samsung!) I'm pretty sure you use a tool like git internally to manage all the changes and revisions. Why do you have to make it so hard for those that want to play with the source by releasing it in a tarball instead of publishing it on github or bitbucket? If you're a kernel dev that does this I consider you "open-forced" NOT "open source". If you don't want to use git and can't be bothered with it why not make a patch and upload that instead?
Does the RedPill support ROMs for N7105 and other N7100 variants?
As of the current Revision Released, I will not be working to making it work on a device I don't currently own. I only build kernels I can actually test myself. While "building blind" might work, I prefer to break my own device before someone else's as they probably paid good money and worked hard/smart to be able to afford the device. FYI, I'm also not in favor of devs who build blindly then ask for donations so they can support the device. I want to own my device, not let it be owned by those who donated their hard earned money to get you the device. I've seen too many "devs" build blindly then ask for a donation so they can support the device, only to find a newer, better and faster device comes out and then chooses to buy that instead of the device he built blindly for and actually got donations to buy it. Talk about Bait and Switch!
Why doesn’t the RedPill have high benchmarks?*
That’s done on purpose to keep YOU away. Seriously. The way the VM system is tweaked (dirty ratio’s, minfree values, etc.) + the focus on better latency in any type of load + a lot of other small tweaks all lead to good performance and battery drain in actual use (I like using my device and not keep it sleeping to bloat my battery stats, thank you). This may not give you the benchmark scores you want to be able to show off… which is good since it means YOU stay away from this kernel and continue to rely on benchmarks rather than actual usage.
Why should I even ROOT my device? Is a custom kernel more secure?
With the Exynos-Abuse Exploit out for ANYONE to use, you're probably better off rooting and installing a custom kernel that includes the fix of AndreiLux. (RedPill and Perseus as of this writing) Now I know it will void the warranty, as you all are aware of, but if the only way to secure your device and your personal data (You don't want anyone to see your google search terms and results as well as those "private" moments that you may have kept for yourself just like any normal person) is to root and install a secured kernel, what choice is Samsung giving you?
Can you imagine what a nefarious and talented malware developer could do with this? They could break your system and have a pop-up that says "Pay up to free your system from being one of my mobile drones"... OR "Donate to get the full features of your device" (This one actually happens a lot on XDA... some talented dev gives you partial features to lure you in... then WHAM, BAM, THANK YOU MA'AM... If you want the full features, please donate yada yada yada...) I digress, as always.
Now, would you rather wait till Samsung officially patches this exploit and run the risk of exposing yourself to the risks this exploit opens you up to? Don't assume malware devs aren't rushing their current code to try and pry their way into your system using this exploit. For all we know, they're busy trying to cover up a similar exploit and currently awaiting Play Store approval. Yes, even the Play Store Apps can compromise your system. Even if Samsung does act fast, (not as fast as AndreiLux since he fixed it in a jiffy) how sure are you that your system hasn't been compromised? You wouldn't even know it.
The best reason to root RIGHT NOW is to completely secure your system, now more than ever. If you need to claim a warranty, you can tell them:
a. I had no choice, you messed up, xda-devs cleaned it up.
b. Flash back stock kernel and remove any trace of root and your use of a custom binary.
c. Completely brick your phone and tell Samsung that the exynos-mem exploit was actually used by malware that zapped your system dead.
I'm not a fan of any of these choices since I believe warranties should be honored by the manufacturer, especially if the bug they created was the reason for the claim for warranty in the first place.
How do I know I'm secured from the Exynos-Abuse Exploit?
Don't rely on apps that tell you whether you're vulnerable or not as the low level kernel fix AndreiLux implemented doesn't need to change the permissions of the /dev/exynos-mem.
Try running Chainfires Exploit APK and try getting the exploit to say anything else but "FAILED"... or head over to the thread HERE and download the exynos-abuse binary and run it from a terminal.
$./exynos-abuse
Click to expand...
Click to collapse
If your shell changes from $ to # then the exploit was successful, if not then you're safe.
Can the RedPill be OC'd and UV'd?
It can be UV'd and OC'd.By default, I've decided to keep all voltages and clock speeds stock as experience has taught me that NOT ALL DEVICES ARE CREATED EQUAL. You can UV the CPU arm voltages and OC using 3rd party Apps that do that. (SetCPU, VoltageControl)
Can the RedPill GPU be OC'd and UV'd?
Yes. Thanks to AndreiLux. You'll need to use STweaks to fully configure this. YMMV as always.
Why a tweaked deadline and SIO I/O scheduler?
The deadline I/O scheduler by Jens Axboe has proven itself as a low overhead, high throughput and acceptable latency I/O scheduler. *When tweaked for NAND based Mobile devices, it does even better. *While it "starves" writes by default with a 2:1 Read:Write ratio, this can easily be tuned via sysfs.
Why is my favorite governor (whichever it is) not available?
Simplicity is the Ultimate Sophistication, as Leonardo Da Vinci eloquently said. *Based on extensive testing and user feedback, we gathered that these 2 governors included gave the best performance and battery life on our device. Simple choice to have only the best ones available based on actual testing and feedback. *I included only these governors so you all have a simple choice to make in finding your favorite one. *These are all tunable via sysfs so you can skew it towards battery or performance based on what is important for you. *Don't expect uber smoothness and 16 hours screen-on time though... *there will be compromises when leaning towards any of the two factors most users consider important in a kernel.
Why LZO Compression for the Kernel?
It decompresses much faster than any other, bar none. Since the kernel size and compression speed is not an issue when using LZO in the kernel. (You only decompress the zImage when booting. Compression is done when building the kernel) Don't believe me, believe the data right HERE.
Why ARM Topology and sched_mc?*(From linaro.org)
"The sched_mc function adds a power saving awareness to the Linux scheduler which is tuned for performance by default. When sched_mc is enabled, the scheduler tries to gather the running processes in a minimal number of cpus and clusters. This choice of the location of a process is done thanks to the cpu topology function which describes the affinity between cpus."
(more info HERE)
Why is my AndroidOS usage so high?
This is most likely a reporting error from Android itself. Use Better Battery Stats to closely watch what really eats your battery. That has shown to be more reliable. (If I were Android, I'd fold buy out BBS and fold its code in by default) If you still have doubts, do a real world battery test, as some have done, and they saw that their battery consumption actually remained the same or in some cases even improved. YMMV, of course. Let's not fall for "placebos" here and say that "hmmmm.... since AndroidOS must be high than my battery doesn't last as long!"
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Ultimate Version FAAAQ DEPRECATED SINCE MOST FEATURES ARE FOUND ON STABLE
Why SLQB? (According to its author, Nick Piggin)* (Only for the Ultimate Revision)
”SLQB is a slab allocator that focuses on per-CPU scaling, and good performance with order-0 allocations. Fastpaths emphasis is placed on local allocaiton and freeing, but with a secondary goal of good remote freeing (freeing on another CPU from that which allocated).” Using this on the Stable version breaks ExFat from working properly. Thus, the Ultimate version is for those who don't need ExFat support.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
HyperDroidDevs FAAAQ
Where do I report Issues or Get Community Support?
Use this thread to report issues, preferably with a last_kmsg, dmesg in a text file or a logcat. How do you do those? I'll let you use XDA's brilliant search function. And no, it's not broken, the search function that is. (I've heard that so many times... "Search isn't working so I posted a question here instead...")
Where are the HyperDroidDevs and their Team from?
We are an international team of crazy people who all have real life day jobs that are mostly not related in any way to Android Development. We're crazy enough to spend sleepless nights trying to make our devices (which we all personally own and have NOT been donated) better than how we received it. We come from all over. I am from the Philippines, where it's always FUN to be! We have Devs and Team members from Spain, Greece, France, Finland, Germany, Italy, Netherlands, Canada, USA, India, Poland, Philippines and even more countries.
How do I show my appreciation? Can I donate to you?
You can show your appreciation concretely in several ways:
Pressing the "Thanks" Button on XDA
Follow me on Twitter @sarcastillo and "Like" our Facebook Page
Report issues politely and completely
Donating any amount is completely up to you. *I look at donations as a "tip" for a job well done, rather than a "wage" or a "bounty" to get things done. *And Tipping is always up to you... the tipper. *I won't stop development if you don't donate, that's for sure, as I do this mainly for myself and my HyperDroid mates to begin with. I make more money running my own business than this hobby so “tips” are not a necessity… it just tells me how many people actually find the work useful enough to say thank you via a financial gesture.
This Kernel will ALWAYS be FREE to Download and USE, even if the time spent making it IS NOT FREE. *That's Open Source. (The time people spend on open source projects could have been used to spend more time with their families, for example. But the Devs commitment to get something done right is almost always tugging at him to Dev just a little bit more) *
*I've personally donated to Devs who've done things I would never have been able to figure out at the time they did figure stuff out. *Learning anything new takes time and time, in my book, is more important than money as I can't turn back time, while I can always earn money. SO I donate to Devs who spend their free time making Stuff better and easier for those of us who haven't figured out how to get it done.
Download Links
Download Links: (CWM/TWRP Version Only)
I've put the links down here to ensure you at least TRY to read the IMPORTANT info posted above.
Don't forget to enjoy the RedPill; it's Awesomeness Delivered!
RedPill
RedPill Stable Revision 1.42:
Click to download RedPill Rev1.42 (For Samsung Based ROM's for N7100) (DEPRECATED | NOT SUPPORTED)
RedPill Stable Revision 1.47:
Click to download RedPill Rev1.47 (For Samsung Based ROM's for N7100)
RedPill AOSP
RedPill AOSP Revision 1.47:
Click to download RedPill AOSP Rev1.47 (FOR CM10.1 and 4.2.2 based AOSP ROM's for N7100) (DEPRECATED | NOT SUPPORTED)
RedPill AOSP Revision 1.52:
Click to download RedPill AOSP Rev1.52 (FOR CM10.1 and 4.2.2 based AOSP ROM's for N7100)
One more for good measure
Really. One more.
Last one for me.
pongster said:
One more for testing
Click to expand...
Click to collapse
Mine again.
you had said that you would delete it in 5 minutes ,but what time is now?
Although my English is not good, I like xda forums very much, like the each friend! I hope you can point out my grammar mistakes to improve my English, thank you very much!
Thanks!!!
C-C-C-C-C-Combo breaker!
Edit: fail. Thanks guy above me -_- lol
Sent from my Galaxy Note II using Tapatalk 2
Y test thread??
Nice to see u here..looking 4ward to great themes now..
5 minutes over
Sent from my GT-N7100 using Tapatalk 2
Me
Sent from my GT-N7100 using xda premium
Woooooohhhhhooooo
Finally d kernel I was waiting for..
(Also waiting for siyah 2 b true)
Thank you so much pongster..
Used 2 loooove ur work on s2 and now on sn2..
Thank you very much..
Sent from my GT-N7100 using Tapatalk 2
Can use the kernel on hyper Rom? Thx
Sent from my GT-N7100 using xda premium
Obviously, this isn't really a test thread. I simply named it as such for the first 5 minutes so I could reserve the necessary posts I need to establish the HyperDroid RedPill Kernel thread.
DamBadz said:
Can use the kernel on hyper Rom? Thx
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
On HyperNote and other Samsung Based ROM's for the N7100
hiack said:
you had said that you would delete it in 5 minutes ,but what time is now?
Although my English is not good, I like xda forums very much, like the each friend! I hope you can point out my grammar mistakes to improve my English, thank you very much!
Thanks!!!
Click to expand...
Click to collapse
Please see my response in Post#18
I would never open Off-Topic threads anywhere. On any forum.
STi Kernel
Add some boost to your life today!
{
"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"
}
STi Kernel is a Siyah derivative. Thank those people involved including AJ Newkirk for inspiring me.
This kernel is for AoCP / AOSP / AOKP / JB-AOKP /CM10 + CM10.1/CM10.2 / cMIUI (Only) / Sense 4 All / SAMSUNG ICS & JB Stock ROMs.
Will fill out more later.....
Whats unique:
Code:
Compiled using Linaro 13.07
Featuring new governors: Skywalker & Wrexy
Stweaks compatible
Updated often with commits from Dorimanx Kernel
Give my profile a shot in EXTweaks ;)
Changelog:
Code:
2.40
-----
Linaro Update!
Swapped STweaks for EXTweaks
Governor tailoring...
more changes.... will upload later !
2.39
-----
Custom Changes:
Linaro 4.8-2013.07
Added skywalker and wrexy back in :) ***major updates to both***
Jthatch_default is back!
Merged new linux 3.10 changes
MORE TO COME! Stay posted :)
Changlog below is directly from dorimanx's thread:
Kernel is updated to 3.10.Y and beyond.(hybrid)(we have 90% from 3.11.Y kernel!)
This is JB Tuned Kernel only! not supporting any 2.x.x/4.0.x roms!
Dual CPU support
Default CPU governor: NIGHTMARE
CFS CPU SCHEDULER Tweaks.
Default CPU frequency: 200-1200 MHz (MAX OC up to 1.6Ghz speed!)
Kernel Support STweaks and 5 Profiles.
Overclocking to 1600 MHz. (via ANY CPU Tweak Apps or STweaks)
Kernel support 16 CPU steps! 1600Mhz->100Mhz by static default!
You can set MIN/MAX CPU Freq in STweaks app! + lots of CPU tweaks.
Kernel will sleep in deep sleep on 200Mhz->800Mhz as Samsung requesting to prevent SOD.
Support undervolt/overvolting via sysfs interface/apps interface. and STweaks (800-1500mV) (all set to best)
Be very careful with voltage settings! (all set already)
Default I/O Scheduling: ROW
More I/O Scheduling present in kernel: DEADLINE, VR, NOOP, FIFO, CFQ, SIO, ZEN, BFQ
Native USB Tethering.
Native Wi-Fi Tethering
File systems support: Ext3/4, FAT32, NFS, CIFS, NTFS
Added tweaks to increase I/O Speed.
Added tweaks to increase CPU speed
Removed all the debuggers to free kernel from unneeded jobs, and logs.
More Govs present, HYPER, conservative, performance, pegasusq, nightmare, darkness, scary, zzmoove, ondemand(default sleep gov), sleepy.
ZRAM SWAP add more 150/300/600MB compressed RAM, activated by STweaks, set to off by default.
Tweak camera (better picks quality)
Kernel Include Siyah Recovery with Dual ROM support!
In Recovery you have section to select kernel profile. Performance, default, battery, the default is DEFAULT.
You can disable ROOT in STweaks app!
Tuned for I/O Mega Speed SQLite is injected to ROM after install.
BLN by GM! lights time out, and blink/breathing effect, see STweaks BLN tab to activate! (READ ABOUT BLNWW!)
New Kernel Management app STweaks by GM! installed with kernel.
BLN without Wakelock to save battery when BLN active till timed out. by GM.
Touch Keys Light change with the screen brightness! by GM.
Massive script for kernel/ROM management made by Voku,Alucard and me
It's will work by auto and set lots of tweaks: NET tweaks, GPU tweaks, CPU management, Deep Sleep Tuning, Charging states, and more!
It's name is cortexbrain-tune.sh
WE SAFE (MMC_CAP_ERASE not present) in kernel MMC Code!
MMC code merged with SAMMY Update 10 + 3.10.y updates!
FM-RADIO WORKING! (you need Spirit FM PAID!!!!) or Sammy ROM with FM APP.
Touch screen color + touch thresholds are in STweaks,
Kernel Cleaning Script is build IN! by VOKU.
BT Support for SAMMY 4.1.2 and all 4.2.X
Video(GPU) + Camera Driver from SAMMY JB/CM10.1 + patches
WIFI Driver 1.61.56 ported from SG4
Modem Driver from SAMMY JB SOURCE
SMP Processor code updated from Kernel 3.10.Y
RCU + SRCU Processor code updated from Kernel 3.10.Y
Kernel Code for on screen gestures by Tungstwenty fixed by MARIO1968
All FS used Code merged with 3.10.rc5 kernel
SLUB fully merged with 3.10.Y Google Android kernel
SCHED CORE fully merged with 3.10.Y kernel.
RAM merged with 3.10.Y Google Android kernel.
VFP updated to MAX from 3.10.Y
Slide2Wake by FLUXI, (swipe from left to right on turned off screen to wakeup device, tweak can be turned on/off in STweaks, this mod use 5% battery! (Modded by GM for less battery drain)
Sound boost controls by FLUXI in STweaks.
New Mali V2 Video Driver combined with old to support JB STOCK in one kernel(8.X branch) by Gokhanmoral/me/CM-TEAM!
In 9.X branch we have MALIv2 ONLY video driver for CM/AOKP new ROMS! no STOCK SUPPORT!.
Added mdnie interface and made hardcore’s sharpness tweaks optional by GM!
5 GPU FREQ Steps from 108Mhz to 520Mhz by GM!
Ultra KSM from 3.9.y kernel.
2.38(Special Finals Week Edition)
-----
Merge linux patch 76
Wrexy , Interactive, and Nightmare Tweaks
Adjusted profiles slightly
Added support for ShoStock
A lot of file updates (too long to list)
Some other fun stuff
2.37
-----
Still having issues with WiFi Toggle...
Updated to latest Linaro 13.03
Adjusted all voltages across the board in all the profiles
Merge linux patch 3.0.74
Some DHD Updates that haven't fixed the WiFi toggle
Looking into the AP issue too....
Some other small merges.
Fixed Voodoo Louder Compatibility(works flawlessly now)
2.36
-----
WiFi toggle should be fixed!
Newest Mali Driver from Note8
Loop.c updates
Bluetooth updates
More changes!
2.35
------
Added Hybrid Profile (Mix between battery and my default)
Better OOM Support (out of memory)
Linux 3.0.70 Main Merges
Some WiFi Tweaks
More little changes
2.34
------
Re-addded profile check feature(Fixed as of 12:14:13 EST)
Added LIFO I/O Scheduler
Tuned Wrexy a little bit more
Changed around some settings in Stweaks
Power Management Updates
Lowmemkill updates
Tuned Performance profile to be more for "Gaming"
ETC....
2.33
------
Merge some changes from newest linux 3.4
Updated all I/O schedulers a bit
Fixed Sammy JB sound fix
Made Wrexy a little less aggressive
More changes
2.32
------
Revert Linux 3.0.68
Updated BFQ scheduler
Other small merges
2.31
------
Merge Linux 3.0.68 patch
Update Nightmare Gov
Other small changes
Stweaks corrections
New Jthatch Battery Profile!
2.30
-------
RIL issue fixed
Updated to latest linaro
2.29EX1
-------
Fixed Overclocking for real :)
CM10.1 Init Updates
Merges from stuff from latest kernel release
Cleaned up redundant coding.
2.27
-------
More governor tweaks, mostly Wrexy
Added Data Auto On/Off to Stweaks
There was more but my computer died so I haven't updated github yet.
2.26
-------
Should work with roms with the JDQ39 bases(AKA AOSP Roms)
Updated Wrexy a little bit
Made some changes to some of the Stweaks profiles
Tuned MALI driver slightly (thanks to Dorimanx)
Some other goodies I'm missing!
2.25
-------
Still no luck on OC for other govs beside Performance, I'm looking into it
Updated Stweaks a little bit, set my profiles sleep I/O to ROW.
Adjusted some stuff for Wifi AP for JB roms.
Adjusted Wrexy slightly
Some other changes.
2.24
-------
Made common kernel version number.
Added performance gov to stweaks.
2.23
--------
New MALI is only compatible with newest CM10.1 2/24 build(for now)
All the stuff translates to, new MALI driver! I got it to you first because I'm the man ;)
2.22
---------
Undervolting works for real this time!
Moved Battery section in Stweaks to the top (I use reset fuel gauge a lot)
Changed default sleep I/O to FIFO
Other small changes.
2.20(Formally 2.19)
---------
Added new FIFO I/O Scheduler.
Gave Linaro 13.01 another shot.. So far so good.
Removed rav4_kar profile from stweaks.
Added 1300 MHz step back in to make coding easier.
Meh, I forget but there was other stuff. Check out github if interested.
2.18
---------
Merges from newly released Linux 3.0.66 Kernel:
2.17
---------
Changed default governor to Wrexy
Updated Exynos thermal drivers
Some more Stweaks changes
Not much else to change, running solid
2.16
---------
A few more merges from linux 3.8
Fixed some stweaks errors still showing 1.5 & 1.6MHz frequencies
2.15
---------
Removed 1600,1500, 1300, and all half step frequencies
A few stweaks changes
2.14
---------
Changed kernel name to STi kernel
Added support for Samsung JB ROMs JHLS4, ZCLSF & ZCLSH
INSTALLATION
1) Reboot into recovery.
2) Wipe Dalvik Cache and Cache
3) It was implied to install the kernel here
4) Reboot Recovery and Clear Stweaks profiles
5)Fix permissions
6) Reboot
RELEASES
2.40EX14 MICSWAP
ROM RUNNING NEWEST MALI DRIVER
SERIOUSLY DON'T INSTALL THIS ON A ROM THAT USES THE OLD DRIVER. YOU'VE BEEN WARNED
Download
2.34
http://d-h.st/9Pk
Best known version to date
2.39 NOMICSWAP
Not released yet.....
ARCHIVE
Get old versions here
NIGHTLIES
Use caution
For changes,look on github. Nightlies are not LTS releases.
Nightlies
SOURCES
Kernel Source Github
Special thanks to:
Dorimanx (Dorimanx Kernel)
Voku1987 (Dorimanx Kernel)
Alucard_24 (Dorimanx Kernel)
Entropy512 (CyanogenMod)
Gokhanmoral (Siyah Kernel)
Special thanks to my testers:
bleedingthru
topiratiko
voldomart13
RockRatt
Obviously if there are any issues please report them! But please only report them once.
WREXY & SKYWALKER
Wrexy is a conservative based governor. Its similiar to the Lionheart gov. It tends to stay out of higher frequencies to favor lower frequencies but performance is not hindered. Personally I use this as my CPU Awake gov
Skywalker is a SavageZen based governor. I would not recommend this as a CPU awake kernel because it'll stay in the higher frequencies... but as a Sleep kernel, it stays in the low frequencies and almost instantly puts your phone into deep sleep. You'll also experience no lag on wakeup and no skipping of music! Its the best CPU Sleep GOV in my opinion
I highly recommend running a kernel cleaning script in between installs
https://www.dropbox.com/s/wixdh29muostxl2/Ultimate_Kernel_Cleaning_Script_v2.6.5.zip
Need a 5GHz WiFi fix? Click below to grab a flashable zip!
**Note this patch is specified for people in the US**
http://db.tt/2h4N5Imt
Reserve some more :good:
Interested in developing?
Ask me the 3 lines of code that separate our phone from the I9100!
Re: [Kernel]STi v2.22 [JB/ICS]
First! Can't wait to try this out! Thanks!
Sent from my Pink Unicorn stable
Re: [Kernel]STi v2.22 [JB/ICS]
You missed a step in your installation instructions!
(INSTALL KERNEL?)
Sent from my SGH-S959G
mr-cook said:
You missed a step in your installation instructions!
(INSTALL KERNEL?)
Sent from my SGH-S959G
Click to expand...
Click to collapse
Lol that was implied but I updated the OP just for you
Re: [Kernel]STi v2.22 [JB/ICS]
This kernal is the shizzle u guys wont be disappointed
Sent from my SGH-I777 using xda app-developers app
Re: [Kernel]STi v2.22 [JB/ICS]
What does wrexy and Skywalker do?
Sent from my SGH-i777 using xda app-developers app
Re: [Kernel]STi v2.22 [JB/ICS]
jthatch12 said:
Lol that was implied but I updated the OP just for you
Click to expand...
Click to collapse
No instructions required here.
Just trying to save you the headache later. Of people having problems from fixing permissions first, or some other off the wall "I followed the instructions claim".
Sent from my SGH-S959G
Re: [Kernel]STi v2.22 [JB/ICS]
can you point me to a list of which roms have the new vs old MALI driver plz? I'm pretty sure, however, that I'm currently on the old one (jellybam 4.1/CM10). love the name BTW... although I admit I'm an R32 guy myself.
Sent from my SGH-I777 using xda premium
tonysave said:
What does wrexy and Skywalker do?
Sent from my SGH-i777 using xda app-developers app
Click to expand...
Click to collapse
Meh, thats something I was gonna fill out later since I'm at school studying:
Long story short:
Wrexy is a conservative based governor. Its similiar to the Lionheart gov. It tends to stay out of higher frequencies to favor lower frequencies but performance is not hindered. Personally I use this as my CPU Awake gov
Skywalker is a SavageZen based governor. I would not recommend this as a CPU awake kernel because it'll stay in the higher frequencies... but as a Sleep kernel, it stays in the low frequencies and almost instantly puts your phone into deep sleep. You'll also experience no lag on wakeup and no skipping of music! Its the best CPU Sleep GOV in my opinion
VR32 said:
can you point me to a list of which roms have the new vs old MALI driver plz? I'm pretty sure, however, that I'm currently on the old one (jellybam 4.1/CM10). love the name BTW... although I admit I'm an R32 guy myself.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Gotta love boost :highfive:. Um I don't have the time to make a complete list right now. If you're on the old jellybam and the new MALI driver hasn't been implemented yet, then version 2.22 is for you. I would expect to see that most of the ROMs will implement the new MALI driver soon. The newest CM10.1 build 2/24 is the first ROM(I know of ) that has the new MALI driver.
Re: [Kernel]STi v2.22 [JB/ICS]
Yea glad to see there still life for the i777. I already download and installed. This kernel seems faster than ajs on helly bean. Thanks loving the new kernel.
Sent from my SGH-I777 using xda app-developers app
Re: [Kernel]STi v2.22 [JB/ICS]
cyberbandit1998 said:
Yea glad to see there still life for the i777. I already download and installed. This kernel seems faster than ajs on helly bean. Thanks loving the new kernel.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Nice to hear man. After a few weeks of testing with only good results I felt today was the perfect release date!
Sent from my SGH-I777 using xda premium
Re: [Kernel]STi v2.22/3 [JB/ICS]
Smooooooooooooooov
Android Open Collective Project 412
Samsung Galaxy SII
Boosted 2.2
I really hope this works for me, coz AJK doesn't work on my phone. Can't figure out why, hoping for better luck on this one. Finger crossed!
Re: [Kernel]STi v2.22/3 [JB/ICS]
rk249 said:
I really hope this works for me, coz AJK doesn't work on my phone. Can't figure out why, hoping for better luck on this one. Finger crossed!
Click to expand...
Click to collapse
Mail driver update
Sent from my SGH-I777 using xda premium
Re: [Kernel]STi v2.22/3 [JB/ICS]
I think I found a bug. Im oc to 1300 but it not being used. CPU spy saying 1300 unused. Using your default profile with featured governors featured on op.
PS. Changed oc to 1400 same result. No oc on oc kernel
Sent from my SGH-I777 using xda app-developers app
Re: [Kernel]STi v2.22/3 [JB/ICS]
cyberbandit1998 said:
I think I found a bug. Im oc to 1300 but it not being used. CPU spy saying 1300 unused. Using your default profile with featured governors featured on op.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
As stated wrexy stays out of higher frequencies. Like seriously it won't touch it. Switch to performance gov and you'll see OC is working
Sent from my SGH-I777 using xda premium
{
"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"
}
Phoenix Kernel
Phoenix -Kernel For Optimus L1 II (vee1)
E410-E411
Features
Based on the STOCK Source v10g from LG
CPU Voltage Control: use TricksterMod for the moment
Toolchain: Built with GCC 4.7 toolchain from SABERMOD
Linux: 3.4.13
CPU OC: up to 1.4GHz
GPU OC: up to 190 Mhz
Swap
F2FS Support
zRam Support: support for zRam memory compression
KSM: Kernel Same-page Merging enabled
Dynamic management of dirty page writeback
Undervolt
Dynamic Fsync: Faux123's Dynamic File Sync v1.2
Frontswap
Battery Life eXtender (BLX)
ARM optimizations
Fast Charge: chad0989 fast_charge driver, allowing to set the amperage of the charger or USB port your device is plugged-in to (default disabled)
Kernel mode NEON: NEON-accelerated XOR framework & support for NEON instructions in kernel mode
Lowered swappiness (60 -> 45)
Optimized AES and SHA1 routines for ARM cpu architecture
Optimized SLUB memory allocator
Optimized ARM RWSEM (read/write semaphore)
exFAT support
Fast Random generator (frandom) support
Optimizations: Built with -O2 and many optimization flags
Additional Governors:
- SmartassV2
Additional I/O Schedulers:
- SIO (SImple Ondemand)
- SIO PLUS (SImple Ondemand PLUS)
- VR
- Zen
- Fiops
- Bfq
Click to expand...
Click to collapse
The REQUIREMENTS
A unlocked bootloader
Custom Recovery CWM/PHILZ/TWRP
A brain with the ability to read
The will to recycle your warranty papers
The INSTRUCTIONS
Copy the zip to your sdcard
boot into recovery
flash the zip
reboot
enjoy
SOME INFO OF SOME KERNEL THINGS
SWAP
Swap is, in short, virtual RAM. With swap, a small portion of the hard drive is set aside and used like RAM. The computer will attempt to keep as much information as possible in RAM until the RAM is full. At that point, the computer will begin moving inactive blocks of memory (called pages) to the hard disk, freeing up RAM for active processes. If one of the pages on the hard disk needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the hard disk ('swapped'). The trade off is disks and SD cards are considerably slower than physical RAM, so when something needs to be swapped, there is a noticeable performance hit.
Unlike traditional swap, Android's Memory Manager kills inactive processes to free up memory. Android signals to the process, then the process will usually write out a small bit of specific information about its state (for example, Google Maps may write out the map view coordinates; Browser might write the URL of the page being viewed) and then the process exits. When you next access that application, it is restarted: the application is loaded from storage, and retrieves the state information that it saved when it last closed. In some applications, this makes it seem as if the application never closed at all. This is not much different from traditional swap, except that Android apps are specially programed to write out very specific information, making Android's Memory Manager more efficient that swap.
OVERCLOCK
Overclocking is the process of making a computer or component operate faster than the specified clock frequency by the manufacturer by modifying system parameters. One of the most important techniques is running at a higher clock rate (more clock cycles per second; hence the name "overclocking")
Operating voltages may also be changed (increased), which can increase the speed at which operation remains stable.
Advantage:
You can get more performance from your chipset, you can see visible changes in runtime applications and more as time instant response.
Disadvantage:
* Overclocking is always risky if something is configured improperly and may also result in permanent damage of your hardware. As long as it is done safely you are good to go.
* You may see some increased power consumption.
* Extreme overclocking might kill your hardware.
UNDERVOLTING
The process where you provide less voltage to your cpu rather than the stock voltage.
Advantage:
* Reduced heat from your device.
* Good battery life.
Disadvantage:
* Extreme undervolting will make your device unstable and some times even end up with a boot loop.
Click to expand...
Click to collapse
The THANKS
Ceastel
srfarias
showp1984
markus-oberhumer
faux123
sashalevin
ardbiesheuvel
mrg666
pinkflozd
kleikamp
jankara
marcusk
sergey-senozhatsky
tiny4579
gregkh
CastagnaIT
DOWNLOAD
Do you like my Kernel? use this buttons for support me
Fanpage: like = future project
https://www.facebook.com/Phoenix-DEV-1719991991571980/
XDA:DevDB Information
Kernel Phoenix, Kernel for the LG Optimus L1 II
Contributors
chijure, chad0989, srfarias
bala_gamer
Source Code: https://github.com/chijure/android_kernel_lge_vee1
Kernel Special Features: OC CPU 1.4 Ghz, GPU 190 Mhz, UV, Fast Charge, Voltage Control, Swap, Zram, KSM, Dynamic Fsync, Frontswap, BLX, F2FS, Exfat, Frandom, Linux 3.4.4, SmartassV2, SIO, VR, SIO PLUS, FIOPS, BFQ, ZEN...
Version Information
Status: Stable
Stable Release Date: 2015-07-23
Current Stable Version: 07
Beta Release Date: 2015-07-23
Created 2015-06-06
Last Updated 2015-07-23
completely unstable when you try o/c,ruined my phone....did you try it before post it?
manosper said:
completely unstable when you try o/c,ruined my phone....did you try it before post it?
Click to expand...
Click to collapse
yes everything works perfectly
CHANGELOG
CHANGELOG
2015-06-01 Phoenix v1
Initial relase
USB force fast charging
Overclock 1.4 Ghz
Added SIO Schedulers
Enable Deadline
2015-06-08 Phoenix v2
Enable SWAP
Enable ZRAM
Enable Ksm
SLUB SLAB Optimization
linux 3.4.3
swappiness 60-->45
random.c: entropy tweaks
sched: disabled GFSleepers for ui performance
Add optimized AES and SHA1 routines
2015-06-10 Phoenix v3
Disabled useless CPU clock for better scalability
Optimized Adreno drivers
Add Dynamic management of dirty page writeback
Enabled SIO iosched
Fix OVERCLOCK ( no more restarts stable up to 1.3 GHz)
Adding UNDERVOLT
Dynamic sync control
Tweak Zcache
add frontswap and Tweaks
2015-06-19 Phoenix v4
Added ARM optimizations
Linux 3.4.4
CRT animation workaround for JB
default disable Sync Control
Add Voltage Control: add sysfs interface and enabled
Add cpufreq: add smartassv2
Added Battery Life eXtender (BLX)
Add V(R) I/O Scheduler
Add Zen IO scheduler
Add Simple IO scheduler plus
Add support for kernel mode NEON
2015-06-28 Phoenix v5
fs: Asynchronous I/O latency to a solid-state disk greatly increased
writeback: Fix occasional slow sync(1)
sync: make sync() satisfy many requests with one invocation
jbd2: optimize jbd2_journal_force_commit
writeback: fix race that cause writeback hung
add exFat support
decompressor: Add LZ4 decompressor module
lib: Add support for LZ4-compressed kernel
lib: Add support for LZ4-compressed kernel
lib: Add support for LZ4-compressed kernel
Add support for kernel mode NEON
Add Phoenix Defconfig
mach: Add adb reboot recovery
scripts: setlocalversion: Do not append last commit hash
add Frandom
Fix gcc 4.7
2015-07-06 Phoenix v6
lib/memcopy: use glibc version
lib/string: use glibc version
Optimized ARM RWSEM algorithm
scheduler: compute time-average nr_running per run-queue
proc: enhance time-average nr_running stats
scheduler: Re-compute time-average nr_running on read
Disable vermagic!
defconfig:Fix WIFI module
Fix USB Force Fast charge …
overall_stats: add overall stats for all available cores
overall_stats: make dual/quad core stats configurable via meunconfig
overall_stats: forward port to kernel 3.4+
Add BFQ
Add FIOPS
ARM: 7583/1: decompressor: Enable unaligned memory access for v6 and above
lib/lzo: Optimize code for CPUs with inefficient unaligned access
kernel: Move REPEAT_BYTE definition into linux/kernel.h
2015-07-23 Phoenix v7
Enable ZSMALLOC
ZRAM FIX BUILD
F2FS Support
Overclock GPU 190 Mhz
linux 3.4.13
Ploblems
the kernel is perfect :laugh: , more than 1,267 Ghz on the unit is giving restart random
so I can use up to 1200 GHz, without the device restart
Josenildo lopes said:
Ploblems
the kernel is perfect :laugh:, more than 1,267 Ghz on the unit is giving restart random
so I can use up to 1200 GHz, without the device restart
Click to expand...
Click to collapse
if I think still unstable remove those frequencies and leave in 1.267 Ghz
Why does it stutter so much beyond 1.2GHz? Changing the I/O from sio to deadline helped a bit, but using anything beyond 1.2GHz will make games stutter. 1.396GHz is slower than 1.0GHz, and the sound stops for a bit every 2-5 seconds
EDIT: Restarting fixed it. Everything is faster now.
EDIT2: Touchscreen stops responding on games when there's a framerate drop, so if something happens and a game suddenly drops to 10-5fps then I can't move.
EDIT3: The GoneMAD music player makes everything slower now and the audio stutters if you do anything while playing music, the My Boy! and Snes9x emulator are a lot slower, dodonpachi resurrection, ikaruga (3D) and dynamix are slower but cytus is faster. Going back to previous kernel.
and our incredible even o'que did, I'm still using this kernel, and play hard, and realized that my l1 this heating less, not to mention the best fps in games station,
that good, a kernel full of improvements, overclocked and not very warm, and that saves a lot of battery, get to play hours, good
I hope to continue updating the kernel, because it get better than ja ta :fingers-crossed:
_hhhh_ said:
Why does it stutter so much beyond 1.2GHz? Changing the I/O from sio to deadline helped a bit, but using anything beyond 1.2GHz will make games stutter. 1.396GHz is slower than 1.0GHz, and the sound stops for a bit every 2-5 seconds
EDIT: Restarting fixed it. Everything is faster now.
EDIT2: Touchscreen stops responding on games when there's a framerate drop, so if something happens and a game suddenly drops to 10-5fps then I can't move.
EDIT3: The GoneMAD music player makes everything slower now and the audio stutters if you do anything while playing music, the My Boy! and Snes9x emulator are a lot slower, dodonpachi resurrection, ikaruga (3D) and dynamix are slower but cytus is faster. Going back to previous kernel.
Click to expand...
Click to collapse
the truth is I also have the toolchain think those errors back to using gcc 4.4.3 has given me a great performance and pesea velicidad be an outdated gcc
Josenildo lopes said:
and our incredible even o'que did, I'm still using this kernel, and play hard, and realized that my l1 this heating less, not to mention the best fps in games station,
that good, a kernel full of improvements, overclocked and not very warm, and that saves a lot of battery, get to play hours, good
I hope to continue updating the kernel, because it get better than ja ta :fingers-crossed:
Click to expand...
Click to collapse
I will continue updating and adding more features to improve the performance of l1 now working to make hybrid between 3.10.x
How do I overvolt/undervolt my CPU? I tried with the Voltage Control Lite and TricksterMod apps but the voltage options are not there.
_hhhh_ said:
How do I overvolt/undervolt my CPU? I tried with the Voltage Control Lite and TricksterMod apps but the voltage options are not there.
Click to expand...
Click to collapse
this works by now remove the instability generated but soon we will see in future more stable updates
Sent from my XT1032 using XDA Premium mobile app
His GPU
I noticed that the clock it is in 133 Mhz, whereas before it was 145 Mhz, you down?
and if possible, what do you think of to overclock the GPU Too I, and put options to control the frequency with governors?
already that the GPU l1 and very old, and these options I say, perhaps an improved
Josenildo lopes said:
I noticed that the clock it is in 133 Mhz, whereas before it was 145 Mhz, you down?
and if possible, what do you think of to overclock the GPU Too I, and put options to control the frequency with governors?
already that the GPU l1 and very old, and these options I say, perhaps an improved
Click to expand...
Click to collapse
to overclock the GPU greatly improves performance and if I think adding but with frequencies scaling and Governors but first I want to finish the project of hybrid kernel
Sent from my XT1032 using XDA Premium mobile app
wow
ours got 11904 points in AnTuTu benchmarck, and incredible, I come up even close to the bike and which has 12766 points, that is amazing
My l1 earlier reached a maximum of 6000 points kkkk :laugh:
This Kernel works on all variants(Single/Dual/Tri)?
-Working on support of VeeKernel to support CM11-
Josenildo lopes said:
ours got 11904 points in AnTuTu benchmarck, and incredible, I come up even close to the bike and which has 12766 points, that is amazing
My l1 earlier reached a maximum of 6000 points kkkk [emoji23]
Click to expand...
Click to collapse
haha [emoji14] if you give a good score in Antutu Benchmark
Enviado desde mi XT1032 mediante Tapatalk
Caio99BR said:
This Kernel works on all variants(Single/Dual/Tri)?
-Working on support of VeeKernel to support CM11-
Click to expand...
Click to collapse
I think if use a defconfig generic
Enviado desde mi XT1032 mediante Tapatalk
chijure said:
I think if use a defconfig generic
Enviado desde mi XT1032 mediante Tapatalk
Click to expand...
Click to collapse
has some cm November of the L3 II works in the L1 II but does not work the touch and I can not get a logcat that is not activated
Enviado desde mi XT1032 mediante Tapatalk
chijure said:
has some cm November of the L3 II works in the L1 II but does not work the touch and I can not get a logcat that is not activated
Enviado desde mi XT1032 mediante Tapatalk
Click to expand...
Click to collapse