[KERNEL]Netarchy Nexus for NS + NS4G (22-Oct-2011) Testing: 1.4.1 - Nexus S Android Development

Netarchy Nexus represents my foray into the world of kernel development for the Nexus S, having previously been working on kernel builds for the Evo 4g.
Current Change List vs the stock kernel:
- BFS (Courtesy of work by Con Kolivas) *In builds as marked*
- Overclocking up to 1.4ghz enabled *overclocking not active by default, use a tool such as SetCPU or CM7's cpu performance settings to overclock* (Remember kids, not all phones tolerate overclocking equally)
- BFQ (Courtesy of work by Paolo Valente)
- Voodoo Sound driver - Courtesy of Project Voodoo
- Voodoo Color (as of 1.2.4) - Courtesy of Project Voodoo
- CIFS support
- TUN support
- NFS support (as of 1.2.4)
- Updated kernel base
- Cpu policy fix to avoid crashes with SetCPU and screen off profiles (Courtesy of work by coolbho3000)
- EXT4 remount tweak
- Interactive Governor (Use a tool such as SetCPU to change governors if you want to use it *still in need of some tuning*)
- BLN on i9020 models (As of 1.3.0.1) Thanks to work by Neldar.
- BLN on i9023 models (as of 1.3.0.8) Thanks to work by akent.
- Sysfs interface to custom-under/over volt in realtime (As of 1.3.0.4)
- Smartass Governor (as of 1.3.0.11)
- SLQB (as of 1.3.1)
- Ezekeel's backlight dimmer sysfs interface (As of 1.4.0)
- Ezekeel's Deep Idle modifications (As of 1.4.1)
Click to expand...
Click to collapse
Kernel builds are currently tested against a stock rom and CM7, while they may work unchanged in other roms, your mileage may vary.
All source code is available on my github (see signature).
Be safe, -ALWAYS- make a backup before flashing!
Click to expand...
Click to collapse
*Standard Disclaimer: All packaged builds are provided with no guarantees as to their safety. By flashing, you assume any and all potential risks that running a custom kernel might entail.*
*A note to overclockers: If your phone is unstable when running an overclock speed, your particular phone probably can't handle that overclock and you should choose a lower clock.*
All kernel builds mirrored HERE.
*It is generally a good idea to wipe Cache and Dalvik-Cache when flashing a new kernel build to avoid certain problems usually related to Dalvik-Cache*
Downloads:
Experimental Version: 1.4.1 (These are testing builds that are more likely to have issues)
2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones):
CFS BUILDS:
Netarchy Nexus - 1.4.1-cfs (For stock 2.3.4 or higher roms)
Netarchy Nexus - 1.4.1-cfs-universal (Universal for non-stock 2.3.4 or higher roms)
BFS BUILDS:
Netarchy Nexus - 1.4.1-bfs (For stock 2.3.4 or higher roms)
Netarchy Nexus - 1.4.1-bfs-universal (Universal for non-stock 2.3.4 or higher roms)
"Stable" Version: 1.3.7
2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones):
CFS BUILDS:
Netarchy Nexus - 1.3.7-cfs-2.3.4 (For stock 2.3.4 roms)
Netarchy Nexus - 1.3.7-cfs-2.3.4-universal (Universal for non-stock 2.3.4 roms)
BFS BUILDS:
Netarchy Nexus - 1.3.7-bfs-2.3.4 (For stock 2.3.4 roms)
Netarchy Nexus - 1.3.7-bfs-2.3.4-universal (Universal for non-stock 2.3.4 roms)

Code:
Changelog:
Revision 1.4.1:
- Updated Ezekeel's Touchkey Dimmer to version 3.0 bugfix 4
- Integrated Ezekeel's Deep Idle mod, current to bugfix 5
- 45,333 rabid naked bunnies were harmed during the making of this kernel
Revision 1.4.0:
- Revert a patch that caused random reboots in certain usage situations
- Added Ezekeel's backlight dimmer sysfs interface (See instructions in second post on how to use)
Revision 1.3.9:
- Return to Deadline as default IO scheduler, using BFQ v2 could cause bugged encounters such as a never ending boot
- Applied kernel tweaks from the recent 2.3.5 OTA (mostly relevant for sprint users)
Revision 1.3.8:
- BFQ updated to BFQv2-r1
- Some build options that may have contributed to random reboots have been modified
Revision 1.3.7:
- Voodoo Sound driver updated to v10
- Testing out tiny rcu
- Touchscreen tweaks are no longer applied by default on boot. Users can still custom tweak touchscreen settings if desired
by editing /system/etc/init.d/98touchscreen and rebooting as before.
Revision 1.3.6:
- Wifi driver changes, rolled back some code that was causing problems
- Added Cyaniris' touchscreen tweaks back in the form of a user customizable sysfs interface (courtesy of work by Cyaniris).
Users can set custom values by editing /system/etc/init.d/98touchscreen , followed by a reboot for the changes to take effect.
Currently the default values are set, users that find the defaults not optimal might want to try some suggested settings by Cyaniris
of 35 for touchthr, and 20 for noisethr.
- Corrected a bug that would have caused reboots and/or other assorted badness when having the phone sleep at a frequency other than 800mhz
(Confession: I was an idiot and forgot to move over this fix from my 2.3.3 kernel trees when making the new kernel trees for 2.3.4, woops!)
Revision 1.3.5:
- Wifi driver updates, bugfixes
- JHash3 Added
- Cpu cache clearing fixes
- New compiler toolchain for builds, using gcc 4.5.2
- Interactive governor adjustments
- IO scheduler set to Deadline, seems to have a nice balance in performance
Revision 1.3.4:
- Remove touchscreen adjustments for now, they were causing problems on some phones.
Touchscreen tweaks will be revisited for a future build
- Add auto group process scheduler for CFS builds
Revision 1.3.3:
- Touchscreen adjustments that may improve touch response
- Update Voodoo Sound driver to version 9
Revision 1.3.2:
- Update BFS builds to BFS404
- Add Simple IO Scheduler and set as default
Revision 1.3.1:
- Smartass screen-off speed adjusted to address unresponsive programs during screen-off
- Smartass adjustments to improve responsiveness
- SLQB slab allocator added to help optimize memory allocation performance
- Some build configuration changes that may improve overall feel
- Ondemand governor up threshold adjusted to improve battery usage while still maintaining responsiveness
Revision 1.3.0.12:
- Adjustments to smartass to improve performance (there is probably still room for improvement)
- Default I/O Scheduler set to CFQ (previously BFQ), this may prove to be more stable in certain situations
- Some adjustments made to the CFS scheduler that may result in a better overall feel to CFS builds
Revision 1.3.0.11:
- Added Smartass Governor
(Not enabled by default, use setcpu or CM's cpu performance
settings to change if you want to try it out)
- Raised voltage cap to 1600mV for crazy people that
want to turn their phone into a reactor ;D
- Set config options in 2.3.4 kernel builds that should enable
NS4G compatibility for our newly arriving sprint friends.
Welcome to club nexus ;D
Revision 1.3.0.10:
- Update kernel base to 2.6.35.13
- Excessive stuttering in apps such as Gun Bros should be resolved
or significantly improved; some problems with memory handling
were introduced in 2.6.35.12 and are resolved in .13
Revision 1.3.0.9:
- The cause of super-lag has been found (Big thanks to twitch153 for helping me test)
- Introducing Universal builds! These universal builds are designed to be flashed on any
non-stock rom of the series marked (ie; Universal 2.3.3)
- Misc other tweaks to the kernel config that may result in an even smoother overall
experience
Revision 1.3.0.8a:
- Fix issue preventing USB debugging (and adb), and sdcard space from working
Revision 1.3.0.8:
- Updated to support the 2.3.4 rom update
- Lots of updates from upstream, including components needed to support
the forthcoming nexus s 4g (yes that means that I will be supporting the ns4g)
- Back to the 2.6.35.12 kernel base, the sdcard tweak has been scaled back
as it appears to have been causing excess lag
- BLN work for i9023 models from akent included (not tested), i9023 users may
find they can now use BLN
Revision 1.3.0.7:
- Revert back to 2.6.35.11 base until I can track down the cause of ridiculous lag in the .12 base
(Not that .11 was a bad performer by any means ;D)
- BFS builds updated to BFS401
- BFS users should find that they have regained their bootanimation
Revision 1.3.0.6:
- Voodoo driver updated to v8
- Custom voltage sysfs interface has changed,
the method used in 1.3.0.4 and 1.3.0.5 is not compatible.
See the guide in the 2nd post for details on the new method.
Revision 1.3.0.5:
- Raised max voltage cap by 50 mV for people who want to try raising the voltage a little bit on 1.4ghz
- More tweaks to try and address instances of "super-lag"
Revision 1.3.0.4:
- Corrected a bug that could cause a slightly higher voltage to be used at certain speeds (resulting in slightly faster battery drain)
- Added a sysfs interface for manipulating voltage levels at various speeds, see 2nd post for details
(read: this allows the possibility of custom under/over volting in realtime)
- Used a different build configuration that may address the occasional "super-lag" that appeared in 1.3.0.3
Revision 1.3.0.3:
- Update kernel base from 2.6.35.11 to 2.6.35.12
- Updated BFS version from BFS 363 to BFS 400 (BFS builds only)
- Raised default read-ahead value from 128 to 2048 (read: sd speed tweak built-in, scripts not necessary)
Revision 1.3.0.2:
- Updated Voodoo Sound driver to version 7
- Fixed a bug that made the sysfs file "scaling_available_freqs" not exist
Programs that must read this file for discovering/controlling available cpu speeds can now do so.
(This also means that CM7 users can set their cpu speeds from the cyanogenmod performance
settings instead of having to use SetCPU)
Revision 1.3.0.1:
- Add initial BLN support (Currently only functional on SAMOLED models [i9020])
Download the BLN control app from the market to use BLN functionality
Revision 1.3.0.0:
- More adjustments to the default colours to try and de-smurf the
previous adjusted defaults while still avoiding "Yellow tint shock"
- Voodoo sound updates (see github commit if you want more details)
- Fixed a bug that caused boot times to take significantly longer than necessary
Revision 1.2.9:
- Voodoo Sound v5 driver update
- Adjust default colours to avoid the initial "Yellow tint shock"
Revision 1.2.8:
- Voodoo Color gamma fix
Revision 1.2.7:
- Voodoo Color driver updates/fixes
Revision 1.2.6:
- Bring panel code up to date with official kernel
- Update Voodoo Color driver to v2
- Release initial cm7 2.3.3 compatible builds
Revision 1.2.5:
- Add 2.3.3 compatible builds
- Incorporate many updates from the newer 2.3.3 kernel sources,
including wifi driver updates, touchscreen updates, drivers for
future SLCD nexus-s variants, and more
(far too many bugfixes and updates to list, review the commit list on my github if you want details)
- Ext4 tweak should be working again in stock builds
Revision 1.2.4:
- Add NFS modules
- Make TUN built-in rather than modular (this may address issues some have had loading the driver)
- Add Voodoo Color
Revision 1.2.3:
- Update kernel base to 2.6.35.11
- Removed the ~56fps cap
- Conservative governor tweaked to perform better for users that choose to use it
- Greater rom compatiblity, particularly with roms that use specialized init scripts
Revision 1.2.2:
- 1.3ghz and 1.4ghz added to the frequency table for overclockers
- Default cpu speed on boot is 1000mhz, use a tool such as SetCPU to overclock
(No doubt I'll get some flack for this, but it's a very bad idea to boot into the max possible overclock when not all phones can tolerate it, so I consider it a necessary evil)
- Interactive Governor added, use a tool such as SetCPU to change to it if you want to try it out (Probably needs a bit of tuning to avoid annihilating battery, we shall see)
- CFS and BFS variants are now available
- Infused with the power of 1000 rabid naked bunnies
Revision 1.2.1:
- Ext4 hack should be working properly now
Revision 1.2:
- Fixed a condition where limiting max speed to 1000 would result in
potential underclocking to 800 (Thanks DebauchedSloth)
- Set hi-res timer to 1000hz
- Gave a little more power to the cpu at 1.2ghz, this may help those
having trouble running at 1.2 be more stable
- Integrated ext4 hack into the ramdisk builds
(ext4 hack is not technically a kernel issue but worth pointing out)
Revision 1.1:
- 1.2ghz overclock *really* works now -Thanks for the help Morfic-
- Cpu policy fix to avoid crashes with SetCPU and screen off profiles
(Courtesy of work by coolbho3000)
Revision 1.0:
- Initial release
- Add BFS scheduler
- Add 1.2ghz overclock
- Add BFQ
- Add Voodoo Sound driver
- Add CIFS support
- Add TUN support
- Update kernel base to 2.6.35.10
Custom Under/Over volting 101:
Code:
**As of 1.3.0.6 the method of custom voltage control has changed, read carefully!**
It is now possible for users to define custom levels of under/over
volting via a new interface in sysfs.
The interface file in sysfs can be found at
/sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
By default, the custom values are all zeroed out, so a
` cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table `
will show:
1400mhz: 1450 mV
1300mhz: 1400 mV
1200mhz: 1350 mV
1000mhz: 1250 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 950 mV
100mhz: 950 mV
Modification of voltages is possible by echoing a string of 8 values
to the sysfs interface via the console, where the order of values
goes left to right from highest frequency affected to lowest.
To adjust the mV for a particular higher or lower than the default,
echo values divisible by 5 like in the following example from an adb shell (this is JUST an example, not guaranteed working values ;D):
` echo "1500 1400 1325 1275 1200 1050 900 850" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table `
Which has the following effect when examining UV_mV_table:
1400mhz: 1500 mV
1300mhz: 1400 mV
1200mhz: 1325 mV
1000mhz: 1275 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 900 mV
100mhz: 850 mV
Rom developers, you can conceivably create custom scripts to
apply various under/over volt settings
For reference, these are the default voltages:
Default Frequency Voltage Table:
1400mhz: 1450 mV
1300mhz: 1400 mV
1200mhz: 1350 mV
1000mhz: 1250 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 950 mV
100mhz: 950 mV
Additionally, there is currently a safety cap of 1600mV for max voltage,
setting a value higher than 1600mV will currently not have an effect greater than 1600mV.
(Read: You can set a value higher than 1600, but it will get dropped to 1600 behind the scenes)
This can be altered for future builds if I get feedback asking for it.
Backlight Dimmer:
Ezekeel said:
Based on the latest BLN version 9, I made some modifications to implement a backlight dimmer which does not need an external program (like cron) to trigger an off-switch.
To activate the dimmer, just echo the dim interval in ms (this is milliseconds; 1000ms = 1s) into /sys/class/misc/backlightnotification/in-kernel-dimmer. If you pass a value of 0, the dimmer will be deactivated.
Click to expand...
Click to collapse
FAQ:
Code:
Q: I'm getting a "Device or Kernel version not supported" error in Voodoo Control Plus!
A:The error is referring to the generic modules that voodoo control plus comes with to support
kernels that don't already have voodoo built-in (such as a completely stock kernel).
You can safely ignore this error, as voodoo is already built into the kernel.
Q: I'm getting SOD's (Sleep of Death) when undervolting!
A: You are probably undervolting too far
Q: OMG I'm getting a black screen (no boot animation) when booting a 2.3.3-based rom!
A: This tends to happen mostly on BFS builds, though it *can* occur on cfs builds (and even on the
stock kernel). The exact cause of this glitch is not known at this time, however, it is purely cosmetic.
You will notice that the bottom buttons are lit, and if you were to run adb logcat, you will see that the
phone is active. The phone is actually booting, just be patient.
Q: What are BFS and CFS?
A: They are task schedulers (they determine what processes get cpu time, how much, etc).
CFS (Completely Fair Scheduler) is the default scheduler in the official mainline kernel. It's a tried, tested, stable scheduler.
BFS (Brain **** Scheduler) is a third party scheduler written by Con Kolivas that must be patched into the kernel, and replaces the CFS scheduler. It tends to be faster in certain tasks, and is usually pretty stable, but sometimes there can be performance quirks.

Downloading and Testing! THx
Is using setCPU advised?

EDIT: Removed to avoid confusion as the info previously contained in this post is now outdated and invalid.

Someone give a shout out if this works with cm! Haven't got time to test it myself today. And thanks for your work!
Sent from my Nexus S using XDA App

I will put this in my ROM

Thanks
Just a heads up
Doesn't work with CyanogenMod 7 nightly

netarchy said:
SetCPU is not necessary.
You're free to use it of course, just remember that the NS idles at 800mhz, so if you use a screen off profile, take that into account.
Click to expand...
Click to collapse
Done. Works great with MoDaCo r10

demo23019 said:
Thanks
Just a heads up
Doesn't work with CyanogenMod 7 nightly
Click to expand...
Click to collapse
Thanks for heads up, thats sad. But thanks to the OP for the kernel its so nice to see.
Sent from my Nexus S using Tapatalk

Welcome.
Coolbho3k has a fix up. rewriting policies to enter sleep at 800 and restoring after.
Don't have link handy. You find it on his twitter.
Sent from my Nexus S

morfic said:
Welcome.
Coolbho3k has a fix up. rewriting policies to enter sleep at 800 and restoring after.
Don't have link handy. You find it on his twitter.
Sent from my Nexus S
Click to expand...
Click to collapse
Thanks for the tip

AAAAAAAAAAAAAAAAALOOOOVEEEEIIIIT !!!!!
1.4HGZ PLEEEASE

To make it cm7 compatible he can split_bootimg the cm7 kernel.
I'm looking into making one kernel working on both Bionix and cm7.
Currently it's 3 builds, Bionix, cm7 and stock for me. If I can unify it, I'll let you know.
Sent from my Nexus S

Please for CM7 KANG

dingdonghei said:
Someone give a shout out if this works with cm! Haven't got time to test it myself today. And thanks for your work!
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
nope, no boot with cm7. but it very successfully made my screen go black. woot!

Man this sounds good...tempted to flash my rom from nightly to try this thanks Dev for giving us more options.

morfic said:
To make it cm7 compatible he can split_bootimg the cm7 kernel.
I'm looking into making one kernel working on both Bionix and cm7.
Currently it's 3 builds, Bionix, cm7 and stock for me. If I can unify it, I'll let you know.
Sent from my Nexus S
Click to expand...
Click to collapse
THANK YOU MR MORFIC !!!!!!!!!!!!!!!
1.4Ghz it's possble ? sorry

morfic said:
To make it cm7 compatible he can split_bootimg the cm7 kernel.
I'm looking into making one kernel working on both Bionix and cm7.
Currently it's 3 builds, Bionix, cm7 and stock for me. If I can unify it, I'll let you know.
Sent from my Nexus S
Click to expand...
Click to collapse
Koush's anykernel can serve that purpose. It splits out the ramdisk from the current boot on the phone and combines it with the zImage of the new kernel (meaning no having to manually repack ramdisks to make various rom-compatible builds), then flashes the new boot image.
Once I have it playing nice with the NS I'll be able to post universal builds. One of the many things on my todo list ;D

Nice. Loved your work on my evo and stoked to try it here. More kernel devs means more choice and hopefully a richer collaborative spirit
Sent from my CM7 Nexus S!

kenvan19 said:
Nice. Loved your work on my evo and stoked to try it here. More kernel devs means more choice and hopefully a richer collaborative spirit
Sent from my CM7 Nexus S!
Click to expand...
Click to collapse
100% ! 100%

Related

[KERNEL] [2.6.29.6] [Flashable-.zip] [LAGFIX][BFQ][Oc][Uv] #3 "Patches 'O Klick"

[KERNEL] [2.6.29.6] [Flashable-.zip] [LAGFIX][BFQ][Oc][Uv] #3 "Patches 'O Klick"
So after countless hours of failure, I finally found my issue. It was an embarrassing one, but O well. What we have here is a fully stable kernel for the Vibrant. I have spent many hours on this and have been running it on my vibrant for some time now. Be sure to read the changelog for full info. At 1.2 Ghz I was getting MFLOPS scores pushing 10 MFLOPS! Performance is surely nice on this one. Another thing to note is the undervolting on my kernel. This will give optimal battery life for users. So, please enjoy, and post and errors with a logcat
This is compiled for the stock ROM. It will work on FrankenTwiz, Bionix, and many ROMs. Let me know what ROMs you try it on, and what ones it works best with.
hurrpancakes said:
This would be my first time using an oc/uv kernel. I know to get the oc, I have to go into setcpu and put the scaling to conservative, which I've already done. Ran quadrant, and got a score of 2790!
Great kernel!
Click to expand...
Click to collapse
mygti02 said:
wow......this kernel is amazingly fast......screw quadrant....mine is only coming up in the 900's but its way faster than the last lag fix i was using that was giving me 2700+ ratings in quadrant.
Great job!!
Click to expand...
Click to collapse
Instructions:
- Download the latest .zip provided below
- Put it on the root of your storage (the 14Gb one)
- Go into ClockWork Recovery
- Flash the .zip like you would a ROM
- Reboot
ENJOY!
Credits: Cyanogen, Wesgarner, Euegene_373, Barakinflorida
Download: http://kingxklick.com/forum/viewtopic.php?f=27&t=230
All my code is on
As you would expect, I am not responsible for anything that happens to your device
If you like my work follow me on Twitter:
CFS Changelog
Kernel #3
- NOW patched up to 2.6.29.6 from .29 (In settings it will still read as just 2.6.29)
- Many bug fixes to the kernel itself from the linux project
- Numerous patches to the CPU scheduler 'CFS' which we are currently using
- *NEW* 'Interactive' CPU Governor (You can enable this in SetCPU)
- Bluetooth patch: Enter active mode before establishing a SCO link. *thanks for finding the code Wesgarner*
- Root UID 0
- Root GUID 0
- AUFS2 standalone patches *via Cyanogen*
- Built with Cortex-a8
- Compiled with Neon Optimizations
- Using CT-NG toolchain *optimized for our CPU's*
- IPv6 fixes via mainline
- Netfilter tether: Fix unaligned memory access
- Netfilter stability enhancements *all via mainline, thank them*
- Much more I will add
Kernel #2
- Implemented "Speedy King Lag Fix"
- Some more voltage tweaks since it is going well
- NEW 'Interactive' Governor support
- Conservative governor tweaks (via Herver)
- Touchscreen is more responsive
- Compiled with optimizations (forgot to do this on #1)
- Compiled with neon opt
- Kernel compacted a little
Kernel #1
- Based off of Samsung Kernel Source
- Overclockable up to 1.2 Ghz! (thanks for the code unhelpful)
- Undervolted mid range frequencies for long battery life!
- Bluetooth patches (via Nick Pelly)
- Capped boot speed at 1 Ghz
- Using CFS CPU scheduler
- Added NEW BFQ I/O scheduler support! (thanks dark)
- Added CGROUPS block for BFQ
- BFQ scheduler set to default
- Anticipatory scheduler support
- Deadline scheduler support
- CFQ scheduler support
- Noop scheduler support
- Conservative CPU Governor set to default
- Ondemand CPU governor support
- Userspace CPU governor support
- Added support for EXT4 filesystems
- More I will add
thanks man, nice to have something we dont' have to flash in Odin
Great work!
Nice to see you in the vibrant neck of the woods king. I'll give this a shot in the morning. If I'm not going to oc will I notice much of a difference between this and the stock kernel?
Cyanogen, King...feel right at home coming from a 32B phone.
Paging Dr B said:
Nice to see you in the vibrant neck of the woods king. I'll give this a shot in the morning. If I'm not going to oc will I notice much of a difference between this and the stock kernel?
Click to expand...
Click to collapse
most definately, overclocking should be fairly stable though, ftw
kingklick said:
most definately, overclocking should be fairly stable though, ftw
Click to expand...
Click to collapse
is this cool too flash with the leaked JI2 Rom?
cdw9800 said:
is this cool too flash with the leaked JI2 Rom?
Click to expand...
Click to collapse
as long as samsung has not changed anything vital in their initramfs we should be just fine !
kingklick said:
as long as samsung has not changed anything vital in their initramfs we should be just fine !
Click to expand...
Click to collapse
ok ima give it a shot and report back
This is gonna sound noob but here it goes. I've never done research on what exactly kernels are and this is all new to me.
This new kernel I can flash like Rom will over clock my device to 1.2ghz or will it give me the option to? Can overclocking hurt my device in the long run?
Does this come with tools to over and underclock when I need to?
Any other info would be great. I'm on Eugene Franklin twis v2, no voodoo or lagfix yet.
Any other info would be awesome.
Sent from my SGH-T959 using XDA App
Works awesome on Frankin-Twiz update 1
buttery smooth
Works with Bionix
Installed, booted fast. Thanks for your hard work.
Good to see you back, King! Do you think this will work ok on Eugene's Hybrid R3? Also, I know some Vibrants (like mine) didn't like jacs OC kernel. Same issues here, or did the undervoltage kernel fix it?
Sent from my SGH-T959 using XDA App
Can we have info on how to revert this kernal back to stock if needed?
Very nice, glad to see another person compiling Vibrant kernels. Have you considered including the voodoo beta4 in one of your future builds?
Working fine on Vibrant 9
Will this work with a lagfix already installed?
What does the bluetooth patch do? I'm hoping improved A2DP quality, please say its so
Sent from my SGH-T959 using XDA App
so.. is it working with JI2?
all4degame said:
Can we have info on how to revert this kernal back to stock if needed?
Click to expand...
Click to collapse
You should just be able to flash it through recovery. It's available as a flashable zip in one of Eugenes threads.
Sent from my SGH-T959 using XDA App

[Kernel]Netarchy Nexus: Yerba Mate(ICS) Stable: 1.0.3 Testing: N/A (4-Jan-2012)

Netarchy Nexus, Codename Yerba Mate, is a custom kernel based on the official ICS kernel sources, and the current subject of my experimentation on the Nexus-S.
Current Change List vs the stock 3.0.8 kernel:
- Overclocking up to 1.4ghz enabled *overclocking not active by default, use a tool such as SetCPU or CM7's cpu performance settings to overclock* (Remember kids, not all phones tolerate overclocking equally)
- Voodoo Sound driver - Courtesy of Project Voodoo
- Voodoo Color - Courtesy of Project Voodoo
- CIFS support
- TUN support
- NFS support
- Updated kernel base (Currently 3.0.14)
- Cpu policy fix to avoid crashes with SetCPU and screen off profiles (Courtesy of work by coolbho3000)
- EXT4 remount tweak
- BLN - Courtesy of work by Akent, Neldar, and Morfic
- Custom Voltage Interface - Courtesy of Ezekeel
- Deep Idle - Courtesy of Ezekeel
- Backlight Dimmer - Courtesy of Ezekeel
Click to expand...
Click to collapse
Kernel builds are currently tested against a stock rom, while they may work unchanged in other roms, your mileage may vary.
All source code is available on my github (see signature).
Be safe, -ALWAYS- make a backup before flashing!
Click to expand...
Click to collapse
*Standard Disclaimer: All packaged builds are provided with no guarantees as to their safety. By flashing, you assume any and all potential risks that running a custom kernel might entail.*
*A note to overclockers: If your phone is unstable when running an overclock speed, your particular phone probably can't handle that overclock and you should choose a lower clock.*
Downloads:
Testing Version: N/A (These are testing builds that are more likely to have issues)
ICS based Nexus S and NS4G Roms:
"Stable" Version: 1.0.3
ICS based Nexus S and NS4G Roms:
Netarchy Nexus - Yerba Mate - 1.0.3 (For stock ICS)
Netarchy Nexus - Yerba Mate - 1.0.3 (Universal for non-stock ICS roms)
Changelog:
Code:
Revision 1.0.3:
- Add Ezekeel's fix for the cam issue that interfered with deep idle
Revision 1.0.2:
- Fix mobile data stats not being correctly logged, the culprit responsible has been severely beaten with a feather duster
- Testing some build/config changes in the interests of stability
Revision 1.0.1:
- Adjust voltage cap to correctly max out at 1600mV, not 1350mV
- Add Ezekeel's BLD and Deep Idle patches
- Initiate construction of a new mecha-rabid naked bunny in the interests of eventual world domination
Revision 1.0:
- Initial release
FAQ:
Code:
Q: I'm getting a "Device or Kernel version not supported" error in Voodoo Control Plus!
A:The error is referring to the generic modules that voodoo control plus comes with to support
kernels that don't already have voodoo built-in (such as a completely stock kernel).
You can safely ignore this error, as voodoo is already built into the kernel.
Q: I'm getting SOD's (Sleep of Death) when undervolting!
A: You are probably undervolting too far
.
lol when I do this my thread gets deleted/moved/renamed by the devs. I suggest you hurry
yehhhs...netarchy is coming back...
i hope so it make change for nexus ICS..
Good to see you back dude.
Nice! Thx
10chars
Welcome back most awaited kernel for me. Downloading now.
Flashed it. No problems so far.
can you please up the available voltage range to 1475 mV? my device needs at least 1400 to handle 1.3ghz.
right now it's capped to 1350 for me in setcpu.
igor.tonky said:
can you please up the available voltage range to 1475 mV? my device needs at least 1400 to handle 1.3ghz.
right now it's capped to 1350 for me in setcpu.
Click to expand...
Click to collapse
, cap was supposed to be 1600, woops! I'll fix that in the next build.
Welcome back! Just like the good old days.
Beamed from my Nexus S
YES NETARCHY FOR ICS
Now I can really start playing with ICS.
Will be LiveOC and Deep Idle suppport?
any performance tweak in this kernel?
That weird dim-green tint thing when turning the screen on and off is back. I can't seem to get rid of it like I did in GB.
welcome back netarchy
Yay Netarchy is back!
Nuked from Nexus S with ICS using XDA Premium app
my first impression is that this one is blazing fast. No delays whatsoever. Good job so far!
will keep it for a while and see how the stability works out. is it a bfs or cfs kernel by the way?
NS4G please

[KERNEL] fps v0.4 kernel for stock/MCR [2012-02-08]

fps kernel by dr4go​
This kernel is based on the newly released LG v20Q sources, but also includes every (still) needed fix from imperticus' NeoBlaze kernel. It should work on both Froyo and Gingerbread stock and MoDaCo based ROMs. It won't work with CyanogenMod based ROMs.
Prerequisites:
For the SWAP Enabler you need at least 384MB of free disk space on your /data/ partition. And because the swap enabler just triggers the creation of a swapfile it would be best if the data partition wouldn't be too full when executing it (fragmentation will decrease the swap performance by a whole lot!)
Features:
- EXT2/3/4 built in
- NTFS R/W built in
- OC/UV support, overclocking up to 1552MHz [based on cpasjuste] - I recommend SetCPU (http://forum.xda-developers.com/showthread.php?t=505419)
- SDRAM, VDE and GPU overclock [morfic]
- Voodoo Sound [supercurio]
- VR I/O scheduler
- BFQ I/O scheduler (default)
- SLQB memory allocator
- CIFS, TUN
- SWAP support (including swap notify patch for people who want to play around with compcache)
Credits:
- cpasjuste
- beene
- rmcc
- pastime1971
- morfic
- supercurio
- hell_97
- msk
- faux123
- imperticus
Greetings:
- carburano
- juri256
- ryan
INSTALLATION
1. Remove "boot settings" from Pimp My Cpu to reset to default values
2. Reboot into CWM (v5.0.2.7-r2 recommended)
3. Install zip file from SDCARD
4. Reboot
Kernel sources: Github
Personal note: Although I've already been built a lot of kernels (for the HTC Desire HD and also the LG Optimus 2X) I've never released them to public. And I mainly decided to do it, because I'm really really unsatisfied by the performance of this device. Imho it could and should perform a lot better. Join me if you would like to be part of this adventure.
And to conclude with imperticus words: Please also don't forget the 'Thanks button'.
CHANGELOG
2012-02-08
**Kernel v0.4:
- Based on LG's v20Q codebase
- Total removal of RAM hack (may be preliminary, hadn't the chance to look into a few issues, yet...)
- 1st try to fix 50hrs+ issue and a bluetooth incompatibility
2012-01-12
**Kernel v0.3a:
- Reverted the linux kernel patching series (apparently we are stuck on v2.6.32.9)
- Reduced RAM hack to 32MB
- Changed frequency table again (1015MHz replaced with 1040MHz)
- _safe installer added (@ Lo_RaT_PeNaT: that's the version for you to try)
2012-01-10
**Kernel v0.3:
- Improved battery usage
- Fixed a small Synaptic problem
- Patched to 2.6.32.53
- Changed default scheduler to BFQ
- Added some arm 2.6.35+ cpu features (=for snappier phone handling)
- Tweaked .config
- Faster startup time
- Improved EXT4 write performance
- Changed wifi driver
- Lots of sysctl tweaks
- Changed default max frequency to 1216MHz (previously 1408MHz)
- Changed frequency table (added a new frequency 1552MHz, removed 1100MHz)
- Tweaked voltages
- Integrated 64MB Hack
History:
Code:
[u]2012-01-09[/u]
**Kernel v0.2a_repack:
- Merged both installers (of v0.1 and v0.2) and created new one (it no longer overwrites the build.prop file)
[u]2011-12-31[/u]
**Kernel v0.2a:
- Reverted battery voltage scaling fix for Froyo sources
**Kernel v0.2:
- Added SWAP support
- Improved EXT2 and EXT3 performance
- Added NTFS R/W support
- Drastically improved disk and memory read and write speeds when heavy I/O is involved
- Added kernel version to status and removed localversion from it
- Integrated swap notify patch (if anybody wants to use compcache)
- New installer (and dalvik cache is now also automatically wiped)
- Changed default min frequency to 216MHz (previously 389MHz)
- Changed default max frequency to 1408MHz (previously 1015MHz)
- Changed default governor
**SWAP Enabler v0.1:
- First public release
**SWAP Disbler v0.1:
- First public release
[u]2011-12-28[/u]
**Kernel v0.1:
- First public release
FAQ
1. Does fps stand for frames per second?
No, it doesn't. And I will never ever release this information to anyone here. Sorry folks.
2. What is the difference between the normal and the safe version?
Only the installer. If you're stuck when booting, please try the _safe version. Otherwise it is the same kernel.
3. ...more to follow...
It's a great news to have a new kernel to try!
Edit:
ROM:Gueste2x_v2.1(base on v20e&v20m)
1.After 3 times test, quadrant score is about 2800 at 1Ghz.(HP SR1 is about 3300)
2.Andrev OC can work. I really like Myrt's apps to set UV&OC.
installed kernel on stock gingerbread rom.
got a quadrant score of 5700+ at OC 1.2 ghz (VR I/O scheduler)
changed I/O scheduler to BFQ and my score jumped to 6000+
dr4go,
Will you add swap support to your kernel? Because this is really great feature for our low memory device )
Fast. Smooth. Thanks!
Sent from my LG-P990 using XDA App
How come these kernels doesn't work with both CM7 and stock (like MCR) based ROMs? Isn't it possible to fix it? Modles? Kernel version? Too much patches provided by LG?
Remember HTC Hero development back in the days; almost all kernels worked independent on ROM. It was an exception (more or less) if the kernel didn't work with a specific ROM.
Looks like a great kernel, but won't flash a stock based ROM over CM.
What about battery life?
Sent from my LG-P990 using Tapatalk
ryaneu said:
installed kernel on stock gingerbread rom.
got a quadrant score of 5700+ at OC 1.2 ghz (VR I/O scheduler)
changed I/O scheduler to BFQ and my score jumped to 6000+
Click to expand...
Click to collapse
Could you please tell me how to change I/O scheduler?
ryaneu said:
installed kernel on stock gingerbread rom.
got a quadrant score of 5700+ at OC 1.2 ghz (VR I/O scheduler)
changed I/O scheduler to BFQ and my score jumped to 6000+
Click to expand...
Click to collapse
Thanks, that is exactly the information I need to improve the kernel. During HTC Desire HD days, there was no better scheduler than the VR I/O scheduler.
Could you also share your results you get with the Anticipatory-, NoOp- and Deadline-I/O scheduler? That way I could select the best one of those.
Thank you in advance.
dr4go
feav said:
dr4go,
Will you add swap support to your kernel? Because this is really great feature for our low memory device )
Click to expand...
Click to collapse
Noted. Imo you are right, that it would be a great feature for the LG Optimus P990.
Still a lot on my todo list... I already wanted to release it a few days back (as you may have noted I made the last commit on December 12th - since then I'm using it on my device.
Lastly... regarding the todo list: it's done when it's done - and as always: No information released to public before a new kernel it's out.
Stay tuned folks.
sibbor said:
How come these kernels doesn't work with both CM7 and stock (like MCR) based ROMs? Isn't it possible to fix it? Modles? Kernel version? Too much patches provided by LG?
Remember HTC Hero development back in the days; almost all kernels worked independent on ROM. It was an exception (more or less) if the kernel didn't work with a specific ROM.
Looks like a great kernel, but won't flash a stock based ROM over CM.
Click to expand...
Click to collapse
Don't get me wrong: I never had CM installed on any of my previous Android devices. My kernel may work on CM, but honestly... I have no clue.
Yes I've also wanted to try CM once, but as you know... you don't have time for everything.
If you are willing to test it, just flash my kernel (but leave also any other working CM kernel on your SDCARD just in case it doesn't boot anymore) and if you do so... please report back... also what works or what doesn't work...
Thanks in advance,
dr4go
I dealt want to try this kernel buy I do not want to f**k up my phone because it is very good with v20o and rock stable.
is it possible to post a stock kernel so I can return without a flash?
thanks
KillerbeeNL said:
I dealt want to try this kernel buy I do not want to f**k up my phone because it is very good with v20o and rock stable.
is it possible to post a stock kernel so I can return without a flash?
thanks
Click to expand...
Click to collapse
You can find your current kernel inside your zip file of your current ROM. And I doubt that it's the stock kernel you've currently have...
dr4go said:
You can find your current kernel inside your zip file of your current ROM. And I doubt that it's the stock kernel you've currently have...
Click to expand...
Click to collapse
its the rebuild stock v20o from hell_97 with same changelog v20o (?)
EDIT its hypnos v2.0 sp1 v20o version
KillerbeeNL said:
its the rebuild stock v20o from hell_97 with same changelog v20o (?)
Click to expand...
Click to collapse
This is your current kernel you have.
To restore it, there are two possibilities:
1) Copy it to your sdcard and flash it inside a root terminal using the commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p5
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p5
2) Copy the boot.img file inside your nvflash folder, and execute:
Code:
nvflash --bl fastboot.bin --download 10 boot.img
dr4go said:
This is your current kernel you have.
To restore it, there are two possibilities:
1) Copy it to your sdcard and flash it inside a root terminal using the commands:
Code:
dd if=/dev/zero of=/dev/mmcblk0p5
dd if=/sdcard/boot.img of=/dev/mmcblk0p5
2) Copy the boot.img file inside your nvflash folder, and execute:
Code:
nvflash --bl fastboot.bin --download 10 boot.img
Click to expand...
Click to collapse
tnx ..i made a nandbackup with CWM from my current rom and now a have flashed your kernel so if anything goes wrong I can go back
I will test this kernel for a couple of days for stability and battery use.
what's with the "windowsmgr.max_events_per_sec 120 " ??
LG 2X lcd screen has a refreshrate of 72hz so anything higher than 72 fps (120) could cause tearing in animations (?)
thanks for your effort and time
KillerbeeNL said:
tnx ..i made a nandbackup with CWM from my current rom and now a have flashed your kernel so if anything goes wrong I can go back
I will test this kernel for a couple of days for stability and battery use.
what's with the "windowsmgr.max_events_per_sec 120 " ??
LG 2X lcd screen has a refreshrate of 72hz so anything higher than 72 fps (120) could cause tearing in animations (?)
thanks for your effort and time
Click to expand...
Click to collapse
Max_events_per_sec sets OS(software opengl related params) related frames. While actual hw fps is setted in tegra frame buffer kernel driver. Increasing refresh rate at HW level(at kernel level) gives fake higher 2d (as benchmarking software read hw refresh rate to judge 2D),Infact worsen performance and in a long run it damages LCD Controllers and can be dangerous Actual supported refresh rate is 60hz for mobile QVGA and HVGA and you may find 60-62 with other company except LG.
Sent from my LG-P990 using Tapatalk
spica1234 said:
Max_events_per_sec sets OS(software opengl related params) related frames. While actual hw fps is setted in tegra frame buffer kernel driver. Increasing refresh rate at HW level(at kernel level) gives fake higher 2d (as benchmarking software read hw refresh rate to judge 2D),Infact worsen performance and in a long run it damages LCD Controllers and can be dangerous Actual supported refresh rate is 60hz for mobile QVGA and HVGA and you may find 60-62 with other company except LG.
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
So, which value is recommended??? Leave it at 60??? Or 72 in our case????
Cheers!
el_charlie said:
So, which value is recommended??? Leave it at 60??? Or 72 in our case????
Cheers!
Click to expand...
Click to collapse
windows.mgr_max_events_per_sec <---that value is not at all harmfull you can keep any if you want 150-200

[KERNEL][STABLE] Badass Kernel 1.9.2

Hey guys. This is Badass Kernel, a modified version of AU Kernel with a little bit too many additions to fit in the Original Development section.
You'll find my ROM right here!
Logs are disabled in this kernel. This is not a bug, it's a feature.
Compatibility:
Android 4.2.2
CM10.1
AOSPA
PAC
AOKP
Android 4.0.4/4.1.2
CM9
CM9.2
AOSP
Touchwiz ICS V5
So.. new stuff:
1.0
CPU Undervolt down to (0-1-2-4-6).
A_U's bootsplash
Added Badass CPU Governor
Added Badass GPU control
Replace ZRAM LZO compression with Google Snappy compression which is a lot faster
Kernel Samepage Merging enabled by default
Writeback tweaked to do the work only when the screen is off
Added ROW I/O scheduler
Tweaked smartassV2 for more battery saving
Tweaked CFQ and Deadline
1.1
Added frandom support for CrossBreeder to finally work properly
Fixed memory leak in android binder
Restored and updated Lazy CPU Governor (expected: smooth UI, much better battery life and some lag in the first 20-30 seconds after boot)
Filesystem tweaks
Memory tweaks
Added SFB net scheduler and Veno TCP congestion algorithm for better use of internet
Disabled a lot of debugging
1.2
Implemented Dynamic Filesync and enabled by default
Proportional Rate Reduction for TCP
Correct AXI bus values for CPU
Re-added 825 and 844 MHz frequencies (be careful with these as they're not stable, they were left out with a reason)
Trimming /cache every 15 minutes if media playback is stopped.
Updated LowMemoryKiller driver (if you use ram manager or scripts for setting minfree, here are some really good values:3072,4096,12800,14336,15360,19200)
New bootsplash (HTC-alike)
1.2.1
Fixed Snappy
Further UV (0-1-2-3-6)
1.2.2
Enabled Compaction and linked it to LowMemoryKiller
Updated Deadline(now it's better than ROW)
Changed kernel compressor/decompressor from GZIP to the much faster LZ4.
Writeback tweaks from Linus Torvalds
Added TCP congestion algorithms: Hybla, Westwood, Highspeed-TCP. Default is Hybla because in tests, performed better than the rest.
1.3
Enabled Triple Buffering (component of Project Butter by Google)
Added Tiny RCU for smaller memory footprint
Added BoostPulse interface for SmartassV2
1.3.1
Added BoostPulse interface for SmartassH3 and updated it with a new variable(boost_freq) to suit the governors ramping policy
1.4
Lots of code optimizations
AHB Overclocking for faster R/W operations[787 MHz and higher don't have this kind of overclocking because of instability)
New 652 MHz undervolted frequency
CPU Unaligned Access (much faster booting time because of better kernel decompression)
Buffer values updated from Samsung original sources(Triple Buffering, Camera)
SmartassH3 and KSM parameters tweaked for better battery life
1.5
CPU clocks rework
Modified AXI Bus to allow lower CPU frequencies
Added completely stable 68 MHz frequency
New undervolt settings (0-0-1-2-3-5-6-7)
Rewritten Badass CPU and GPU control driver to make more use of 68 MHz frequency
Tuned SmartassH3 to make more use of low frequencies
Added fully functional zCache and ZsmAlloc, backported from 3.4 kernel
1.5.1
Added LowBattery Powersave feature for Badass governor
Badass parameters are more performance biased now
Recalculated Frame Buffer Size for Triple Buffering
Clean-up(remove deprecated CPU governors)
1.6
Add newest Adaptive RED Net Scheduler from 3.4 kernel and make it default.
Replace Snappy Compression with LZ4 Compressor(this is the fastest compressor on the market)
Make our kernel probably the first 2.6 kernel to have these two features
1.6.1
Update LZ4 Compressor from original sources and make it fully functionable
1.7
Replace zRam XvmAlloc with the better ZsmAlloc integration
Update zRam from 3.0 drivers
Make zRam LZ4 decompressor work faster in the same CPU cycles
1.8
Add SIOPlus scheduler (finally something equal or better than deadline)
Add CPU Idle driver to support C4 Deeper Sleep state
Add Wheatley governor to make more use of the new C4 state.
Change Bootsplash
1.9
New governor: WheatleyPlus
Reworked scaling down logic for less calculation
Added BoostPulse interface
Linked BoostPulse to the touchscreen driver (now the governor can really "sense" a touch and boost the frequency after a specific time threshold)
Added Triphasic scaling up logic from Badass (Phase2 is 360 MHz and Phase3 is 480 MHz)
Fixed the Deep Sleep states verification for scaling
Added GPU Control Driver
Added Sampling Down Momentum for dinamically changing the factor for scaling down
Updated OnDemand governor (it's pretty good at the moment)
Remove Badass and Lazy as they were deprecated
Link BoostPulse to the touchscreen driver for SmartassH3 and OnDemand
Optimize the CPU clock structure for WheatleyPlus
Update SIOPlus and add fluid tunables
Introduce Dynamic Cache Pressure
Revise Dynamic Writeback algorithm
Introduce Timer Slack Controller (aka Timer Coalescing, explanation below)
Deep Sleep tweaks
Backport OOM Killing algorithm from 3.8 kernel
Backport LowMemoryKiller and Timed GPIO drivers from 3.8 kernel
Add Whitelist feature to LowMemoryKiller (you can write PIDs of the processes you want to whitelist, in this file > /sys/module/lowmemorykiller/parameters/w_list ~ below you'll find the script for doing this at boot)
Android Binder update
CFS kernel scheduler optimizations
GPU driver optimizations and code cleanup
Make sure that the GPU turns off when the screen is off
Make the sleep states transitions faster
1.9.1
Finetune WheatleyPlus for better responsiveness
Optimize WheatleyPlus for overclocking on 652 MHz and 768 MHz
Fixed graphical glitches(hopefully)
1.9.2
Every bug fixed
Removed WheatleyPlus
Updated Interactive governor to the latest version from 3.8 sources
Add Dynamic Interactive governor (98% the same as Interactive, but it dynamically changes its parameters according to the load)
Dynamic PLL Overclock
Further undervolt until 768 MHz (the latter allows us to do this without losing performance)
Predefine minfree and adj values
Fully functional App Whitelist (example script here)
Forced unaligned access
Fast Charge (use this to enable it: FastCharge.apk - 1.29 MB) [Disconnect USB Cable - Turn ON - Connect USB Cable]
Timer Slack Controller: (this is a copy-paste from boype's thread)
What does the timer slack feature do?
Timer slacking aims to synchronize applications' and processes' CPU requests. The goal is to wake up the CPU less often in oder to save battery. What you need to know here is the following: waking the CPU up and putting it back to sleep again consumes power. Imagine that four apps wake the CPU up four times each in one second. While without timer slacking the CPU would be woken up 16 times, it is desirable to coordinate the wakeups. If done right, the CPU would wake up less often, effectively allowing power savings and longer sleep periods. This is what timer slacking does.
I have activated timer slacking only for background applications, so that everything else stays as responsive as you know it.
Apple has recently introduced this feature under the name 'timer coalescing' with their Mac OSX Maverick (link).
More information: How Apple does timer slacking ('Timer coalescing') (Scroll a little down to the diagrams)
LZ4 Compressor:
LZ4 is a very fast compressor, based on well-known
LZ77 (Lempel-Ziv) algorithm. Originally a fork from LZP2, it provides
better compression ratio for text files and reaches impressive decompression
speed, in the range and beyond 1GB/s per core (!), especially for binary files.
These speeds are scalable with multi-threading modes, quickly reaching
RAM speed limits on multi-core systems.
ROW I/O scheduler:
The ROW scheduling algorithm will be used in mobile devices as default
block layer IO scheduling algorithm. ROW stands for "READ Over WRITE" which
is the main requests dispatch policy of this algorithm.
The ROW IO scheduler was developed with the mobile devices needs in mind.
In mobile devices we favor user experience upon everything else, thus we want
to give READ IO requests as much priority as possible. The main idea of the ROW
scheduling policy is just that: - If there are READ requests in pipe - dispatch them,
while write starvation is considered.
Download:
AOKP ICS:BadassKernel-AICS.zip - 4.74 MB
AOKP:BadassKernel-AOKP.zip - 4.77 MB
AOSP 4.0.4:BadassKernel-ICS.zip - 6.41 MB
CyanogenMod 10:BadassKernel-CM10.zip - 7.01 MB
CyanogenMod 9.2:BadassKernel-CM9.2.zip - 4.74 MB
CyanogenMod 10.1:BadassKernel-JB.zip - 4.77 MB
Various tweaks
Script for adding apps to LowMemoryKiller's whitelist:Whitelist
(you have to edit it to add your own apps, then move it to init.d and set correct permissions. right now you can only add one app, I'll fix this in the next version)
Script to enable zRam with optimized disksize for our Mini: View attachment zRamV2.zip (flashable zip) [UPDATED]
Jeeko's PureAudio fixed for CM10.1 and AOKP: View attachment PureAudio__1.0_-_STUDIO.zip [ Please thank Jeeko for this awesome mod. ]
NOTE: This version of PureAudio is compatible with absolutely any equalizer or player.
If you have Titanium Backup installed, in the menu you'll find an option named "Integrate sys Dalvik into ROM". Use it.
This is something like odexing your system, but keeps the classes.dex files inside the apps. Don't worry if you don't have a lot of system space, Titanium will odex as much as it can until the free space runs out.
TIP: So in latest version of CrossBreeder, the OP added some system tweaking which interferes with our kernel. So I edited those parts to match our settings and device limits.
If anyone wants to install CrossBreeder:
-First uninstall by flashing this file: CrossBreeder_Uninstall_7.2.13.zip - 943.12 KB
-Then install this custom version: CrossBreeder_7.2.13-Badass.zip - 1.59 MB
Sources:
GitHub
Credits:
A_U for compiling the base kernel
franco for the various tweaks I cherry-picked from his source
androidarmv6 for fixing bluetooth
Ezekeel for his Wheatley governor
Uhhm.... You mention CyanMobile, that's mean this kernel works for Gingerbread ?
Which android version is this kernel for...and will changing the ram disk make it compatible with others too?
Sent from my GT-S5570 using Tapatalk 2
Kay, i'll try it on CM7.2
F4uzan said:
Kay, i'll try it on CM7.2
Click to expand...
Click to collapse
I thought your mini was bricked....?!
Sent from my GT-S5570 using Tapatalk 2
@F4uzan I don't think it's for gingerbread..A_U kernel is for cm10.1 so maybe he miswrote...
i think this kernel should be for JB and/or CM 10.1.
hsay said:
I thought your mini was bricked....?!
Sent from my GT-S5570 using Tapatalk 2
Click to expand...
Click to collapse
LOL, forgot to tell you, they done it in only 5 hours ! I'm proud how fast they work. BTW, kernel didn't work for GB, i'm stuck at Bootsplash
Sorry, I forgot to mention the compatible roms
The kernel is for 4.2.2 and that includes CM10.1, AOSPA, PAC and AOKP.
Yes, changing the ramdisk would make it compatible with every rom based on 4.0+ .
I mentioned CyanMobile because that is the name of the maintainer of the repository on github. I think it is based on the kernel used by squadzone for CyanMobile because it has traces of those weird governors (lulzactive, darkside, smoothass etc.)
alin.p said:
Sorry, I forgot to mention the compatible roms
The kernel is for 4.2.2 and that includes CM10.1, AOSPA, PAC and AOKP.
Yes, changing the ramdisk would make it compatible with every rom based on 4.0+ .
I mentioned CyanMobile because that is the name of the maintainer of the repository on github. I think it is based on the kernel used by squadzone for CyanMobile because it has traces of those weird governors (lulzactive, darkside, smoothass etc.)
Click to expand...
Click to collapse
Thanks BTW, tried it on CM10.1, seem smoother and faster.
I think you should change "CyanMobile" to "Squadzone"
can anyone change the ramdisk and make it work on aosp.also i have a question if i am using patched service jar with flymod and ram manager will this kernel affect performance.
darkshadow1997 said:
can anyone change the ramdisk and make it work on aosp.also i have a question if i am using patched service jar with flymod and ram manager will this kernel affect performance.
Click to expand...
Click to collapse
Upload your boot.img here and I will change it.
And none of those would interfere with the kernel.
In the meantime, I will upload a script to enable zRam, you might wanna check it out after you flash the kernel.
alin.p said:
Upload your boot.img here and I will change it.
And none of those would interfere with the kernel.
In the meantime, I will upload a script to enable zRam, you might wanna check it out after you flash the kernel.
Click to expand...
Click to collapse
Man, I'm already impressed with A_U's Kernel , and wanna test yours. Here's the boot.img (I think it's from cm9 but it's still ICS, same thing, right?) Thanks BTW.
Tested and everything work like a charm to restart, phone got restart and stay on boot animation
Edit .: manual reboot make phone boot
Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2
Hello bro...!! i am uploading stock Android AOSP ICS kernel built by Paul.... i.e. not from any modded roms based on dat...
thanks a ton.. and finally I am happie that even our device is seeing some new kernels.. i always wondered why almost all devices have so many kernels and ours not as dat much..
plz change the ramdisk... anytime your free. no ETA's right now m using ur undervolted AU kernel for aosp ics.. wanna say this.. no deep sleep in my phone... bt still i get insane battery backup now... like 8 hrs... thats too much THANKS
i seriously dont want to change from TW UX V5 to 4.2.2... .
I would say that the kernel is very good, but I think that it could add things known to speed mod kernel (no speed mod for galaxy mini). Please Alin.p kernel to develop even better and allowed the acceleration of 10.1 cm (speed)
RicardoQ5 said:
Man, I'm already impressed with A_U's Kernel , and wanna test yours. Here's the boot.img (I think it's from cm9 but it's still ICS, same thing, right?) Thanks BTW.
Click to expand...
Click to collapse
aniketh12 said:
Hello bro...!! i am uploading stock Android AOSP ICS kernel built by Paul.... i.e. not from any modded roms based on dat...
thanks a ton.. and finally I am happie that even our device is seeing some new kernels.. i always wondered why almost all devices have so many kernels and ours not as dat much..
plz change the ramdisk... anytime your free. no ETA's right now m using ur undervolted AU kernel for aosp ics.. wanna say this.. no deep sleep in my phone... bt still i get insane battery backup now... like 8 hrs... thats too much THANKS
i seriously dont want to change from TW UX V5 to 4.2.2... .
Click to expand...
Click to collapse
Here is the kernel: View attachment BadassKernel-ICS.zip
You have the same ramdisk so this should be compatible for both of you.
Deep sleep is working with this kernel. What your problem might be: constant wakelocks from badly written apps (use Wakelock Detector to check that) or min frequency of the CPU set too high. 122-600 MHz with SmartassV2 and Deadline I/O and you won't have any problem.
piotr9821 said:
I would say that the kernel is very good, but I think that it could add things known to speed mod kernel (no speed mod for galaxy mini). Please Alin.p kernel to develop even better and allowed the acceleration of 10.1 cm (speed)
Click to expand...
Click to collapse
Thanks for telling me about SpeedMod. I'm looking into it and see what I can port.
As for the acceleration, are you talking about Hardware Acceleration? Because this is already working in this kernel.
can u upload/commit ur sources? i would like to see some stuff..thanks.
alin.p said:
Here is the kernel: View attachment 2017226
You have the same ramdisk so this should be compatible for both of you.
Deep sleep is working with this kernel. What your problem might be: constant wakelocks from badly written apps (use Wakelock Detector to check that) or min frequency of the CPU set too high. 122-600 MHz with SmartassV2 and Deadline I/O and you won't have any problem.
Thanks for telling me about SpeedMod. I'm looking into it and see what I can port.
As for the acceleration, are you talking about Hardware Acceleration? Because this is already working in this kernel.
Click to expand...
Click to collapse
No bro.. my problem is with Power button.. Itz not working.. hence my deep sleep is not working in any rom at all...
itz definitely not the kernel prob. I am sure.. and all these days i used to get worst battery backup.. this hinders me from using 4.2.2 rom for a long time.
Any way now thankz to you and A_U combined efforts with this kernel I feel like a BEAST and with TW UX v5.. Man my phone is Legendary now.. I love it more than ever...!! Thankz a lot.. and yeah.. already pressd THANKZ button a lot....
A_U said:
can u upload/commit ur sources? i would like to see some stuff..thanks.
Click to expand...
Click to collapse
It is right here: https://github.com/alin23/android_kernel_samsung_msm7x27
I'll update the OP in a few hours with the source and a new update.
The first commits are really messy because I didn't know much about git.
aniketh12 said:
No bro.. my problem is with Power button.. Itz not working.. hence my deep sleep is not working in any rom at all...
itz definitely not the kernel prob. I am sure.. and all these days i used to get worst battery backup.. this hinders me from using 4.2.2 rom for a long time.
Any way now thankz to you and A_U combined efforts with this kernel I feel like a BEAST and with TW UX v5.. Man my phone is Legendary now.. I love it more than ever...!! Thankz a lot.. and yeah.. already pressd THANKZ button a lot....
Click to expand...
Click to collapse
Well, there are applications that can put your device to sleep by touching the overlay or the shortcut on the homescreen. It is exactly the same as pressing the power button.
Here is one of the most popular: https://play.google.com/store/apps/details?id=com.jiubang.goscreenlock.plugin.lockscreen

[KERNEL][Z][6.0.1][CM/AOSP] Airless Kernel

Introduction
The idea for creating this kernel came up around a year ago, during early LP custom ROM builds. I thought it would be a nice idea to fork the most advanced kernel at the time, EvoMix, developed by our renowned Olivier, Joe (SuperHanns) and Alex, and add to it the latest upstream 3.4 patches as well as mix its features with another good kernel, KMA.
After that experiment turned out not so bad, me and fellow xda user BrateloSlava got an idea to continue developing that mixed kernel with our own cherry-picks from the best kernels available for various devices, and use it in my builds of RR and later GZR Tesla ROM.
Now, one year later, I continued the development that BrateloSlava did on the kernel for the last months for my Tesla and Validus ROMs, and I thought it would be a nice idea to extend this kernel's availability to the users of all custom ROMs around at the moment.
So, here is Airless Kernel for Xperia Z, compatible with all CM/AOSP based Marshmallow ROMs.
Features:
CPU
- Governors: ondemand, interactive, performance, intellimm, yankactive, yankdemand, zzmoove, barry_allen
- Multicore Power Saving - tries to group tasks into the least cores possible
- Schedule workqueues on awake CPUs
- CPU Frequency underclock (192 MHz) and overclock (1.7 GHz) capability
- Voltage regulation
Thermal management
- Simplified and efficient thermal driver
- Flexible ramp threshold temperature
GPU
- Governors: simple, ondemand, performance
- 27 MHz idle frequency for ideal power saving
- Overclocked to 487 MHz
Sound
- Faux Sound Control allowing amplified speaker, headphones and microphones volume
Misc
- RGB subtractive color control
- I/O Schedulers: sioplus, bfq, fiops, zen, row, deadline, noop
- Dynamic FSYNC
- Kernel Samepage Merging
- ARM Auto Hotplug (mpdecision replacement) - no tunables
- Gentle Fair Sleepers
- PM: Power Suspend as a replacement to Early Suspend
- TCP congestion protocols: westwood, highspeed, cubic, reno
- Disabling of some well known wakelocks (e.g. msm_hsic_host)
- Double Tap to Wake
- Fast Charge
- Vibration Strength control
- Compiled with latest UBER 5.x GCC toolchain
- Latest upstream patches: 3.4.112
- Many build flag optimizations (graphite, Ofast)
Download
Latest version (20160901)
Installation:
- Make sure you're running a CM or AOSP-based Marshmallow ROM (Resurrection Remix, AOKP, etc..)
- Flash the zip in TWRP 3.0 (tested, recommended) or other compatible recovery
- Reboot
Source code
Github link
Bug reporting rules
Only use the DevDB bug report tool for reporting bugs, provide proper logs and state the ROM, its XDA thread and version you're using. All other reports will be ignored!!
You assume all responsibility for anything that may happen
and I cannot and will not be held responsible
for anything that may happen to your device as a result of flashing a kernel.
*FLASH AT YOUR OWN RISK*
XDA:DevDB Information
Airless Kernel, Kernel for the Sony Xperia Z
Contributors
airlessproject, BrateloSlava
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2016-09-01
Created 2016-05-09
Last Updated 2016-09-01
Tunables for reducing minimal brightness:
Code:
### Reduce backlight brightness
## to revert to default - enter 0
echo "8" > /sys/module/leds_lm3533_ng/parameters/lm3533_bl_reduction;
## values of brightness, lower than lm3533_bl_brightness_min, are being decreased by lm3533_bl_reduction
echo "30" > /sys/module/leds_lm3533_ng/parameters/lm3533_bl_brightness_min;
Important: disable mpdecision in Kernel Adiutor. This kernel has its own hotplugging driver.
Oh god thanks, i can't wait to try this kernel :fingers-crossed:
Sent from my D6503 using Tapatalk
THX! works great! on AOKP
Sent from my Xperia Z using XDA-Developers mobile app
Thanks bro.Good work.
@airlessproject
RGB subtractive color control
Click to expand...
Click to collapse
How do I make make use/activate it?
Also, could you please add pre-tuned Gamma settings like Tommy-Geenexus did for his Zombie Kernel? As you are well aware, the XZ screen by default is very dull and could do with extra constract/saturation.
Thanks
Edit--
After flashing this kernel, it feels a bit sluggish as if it's saving too much power.
Will install it now. Can you add lower brightness like in zombie kernel?
There is already lower brightness, you'll just need to set up a init.d script with these lines:
Code:
### Reduce backlight brightness
## to revert to default - enter 0
echo "8" > /sys/module/leds_lm3533_ng/parameters/lm3533_bl_reduction;
## values of brightness, lower than lm3533_bl_brightness_min, are being decreased by lm3533_bl_reduction
echo "30" > /sys/module/leds_lm3533_ng/parameters/lm3533_bl_brightness_min;
I may add pre-tuned gamma for next builds, until then use the RGB control in Kernel Adiutor -> Screen.
If you feel it's slow, just tune some parameters in kernel adiutor, like up_threshold in the cpu governor, disable multicore power saving etc. Also check if there's a stuck throttled cpu max frequency, that can happen sometimes if it throttles during boot.
Anyway for me it's not sluggish at all, I wouldn't have published it if it was.
Also I'd like to kindly remind all to use the devdb feature and at least provide logs for any problems you encounter and state the ROM you use and its version.
Devs are not psychic to know what's going on with your usage.
Sent from my E6553 using Tapatalk
Please make this kernel for Xperia ZL!
Zotmen said:
Please make this kernel for Xperia ZL!
Click to expand...
Click to collapse
Sorry, I'm not planning to make blind builds.
If there's any dev that owns odin and is willing to do it, he can freely rebuild my kernel for it, just keep the source references and filename.
Sent from my E6553 using Tapatalk
Nice to see a Custom Kernel for our old phone . Thank you for your hard work, it really made a difference in speed on my phone running the latest version of RR.
As a request, can you add to the GPU the 400Mhz option? I mean I'm not fond of overclocking, and prefer to use the stock speed regarding the CPU and the GPU.
DragosBad said:
As a request, can you add to the GPU the 400Mhz option?
Click to expand...
Click to collapse
Unfortunately an additional frequency cannot be added due to known problems with frequency decisions of the driver when it's added, so it would have to be fully non-overclocked if we want to have 400 MHz.
I can assure you that there's no significant battery drain with 487 MHz nor any other issue, but if you totally insist on having stock max frequency, I can provide an optional version of the kernel with GPU OC disabled.
Sent from my E6553 using Tapatalk
airlessproject said:
Unfortunately an additional frequency cannot be added due to known problems with frequency decisions of the driver when it's added, so it would have to be fully non-overclocked if we want to have 400 MHz.
I can assure you that there's no significant battery drain with 487 MHz nor any other issue, but if you totally insist on having stock max frequency, I can provide an optional version of the kernel with GPU OC disabled.
Sent from my E6553 using Tapatalk
Click to expand...
Click to collapse
No need to do this. I will just downclock to 320Mhz, since the difference in performance isn't that big to affect my daily use. Anyway you are awesome for making this offer.:good: You don't see this kind of thing everyday.
Sd card corrupted error after flash((
How to fix?(
I don't want to format it
I tried sd card on computer and it worked...
Is it safe for those who are on customized rom??
mohamadtigre said:
Sd card corrupted error after flash((
How to fix?(
I don't want to format it
I tried sd card on computer and it worked...
Click to expand...
Click to collapse
Logs please, also which ROM and version did you use it with.
pedro.pambasag said:
Is it safe for those who are on customized rom??
Click to expand...
Click to collapse
This is only for custom Marshmallow ROMs (RR, AOKP, CM etc.)
Sent from my E6553 using Tapatalk
How to unlock BL.?
I wish to going MM rom..:'(
Sent from my C6603 using XDA-Developers mobile app
Xzborneo87 said:
How to unlock BL.?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z/development/tutorial-xperia-z-zl-bootloader-t2153261
Great job mate. Is it compatible with cm 12.1 nighlty?

Categories

Resources