[DEV] [KERNEL] UNOFFICIAL - Jelly Bean optimized Kernel for A100 - Acer Iconia Tab A100

Current release: Version 2.0 (stable) [09/06/2012]
SOURCE CODE: Available at GitHub
*WARNING PLEASE USE AT YOUR OWN RISK*​
DISCLAIMER​
FIRST OF ALL THIS IS NOT AN OFFICIAL KERNEL, IT IS NOT SUPPORTED BY OFFICIAL CM10 ROMS OR ANY PREVIEW ROMS.
ONCE YOU INSTALL THIS KERNEL YOU WILL NOT BE SUPPORTED IN THE CM10 / CM9 OFFICIAL/UNOFFICIAL DEVELOPMENT THREADS
OF ANY FORUM i.e XDA, SLATEDROID, etc.. THIS MEANS THAT YOU MUST NOT REPORT ANY ANDROID / CM BUGS TO THE ORIGINAL
COMMUNTIY THREADS FOR THE ROM YOU USE! YOU MAY HOWEVER REPORT ANY CM/ANDROID/KERNEL RELATED ISSUES TO THIS THREAD ONLY!
Click to expand...
Click to collapse
Features
CPU Overclocking up to 1500mHz (default is set at stock 1000mhz)
Stable GPU Overclock @ 450mhz (scales from 300 - 450)
Userspace CPU undervolting support
Brick prevention/precaution - disabled MMC_CAP_ERASE function from kernel
I/O Schedulers: BFQ, CFQ, SIO, DEADLINE, NOOP, V(R) (Default VR as of v1.3 - prior to 1.2 default = deadline)
Autogroup Scheduler patched to work with Android via User ID task grouping
CPU Governors: Lionheart, SavagedZen, Lazy, Scary, Intellidemand, LagFree, Wheatley, Lulzactive, SmartAssv2, Interactive, Ondemand, Powersave, Userspace, Performance (depending on ROM - interactive governor is usually set as default gov from userspace during init)
ARM libs from Linux 3.x (v2.0+)
Android Drivers from Linux 3.x (v2.0+)
Linux Security from Linux 3.x (v2.0+)
Cleancache + Zcache Support (v2.0+)
Working Zram - to enable see instructions below (v2.0+)
Fixed Video driver glitches (v1.4+)
Cleaned up tons dmesg errors and warnings (v2.0+)
Memory management fixes and patches from 3.x (v2.0+)
Alsa SoC Tiny HAL patch for better compatibility with Jelly Bean and ICS (reduces/eliminates popping sounds)
Plus various other improvements to kernel configuration and code.
Downloads: (if anyone experiences issues downloading from the androidfilehost mirrors please contact [email protected] to notify of outage as requested by afh admin, thanks!)
Current Stable:
Code:
[URL="http://goo.im/devs/godmachine81/a100_kernel/gm-a100-v2.0-signed.zip"]version 2.0[/URL]
Previous Releases:
Code:
[URL="http://beta.androidfilehost.com/?fid=9390062577138008066"]version 1.5[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-v1.3a-signed.zip"]version 1.3a[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-v1.2b-signed.zip"]version 1.2b[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.1-signed.zip"]version 1.1[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.0.1b-signed.zip"]version 1.0.1b[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.0.1-signed.zip"]version 1.0.1[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.0-signed.zip"]version 1.0-pre[/URL]
Tools:
Code:
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/toggle-ag.sh"]toggle-ag[/URL] Tool to Enable/Disable Autogroup and check the status.
'toggle-ag' now included with kernel zip as of 1.3a and is located at /system/xbin/toggle-ag - You may run from a terminal or create Script Manager widgets for each of the script arguments:
Code:
toggle-ag status
toggle-ag on
toggle-ag off
toggle-ag help
Please remember that this script has to be ran as root if you plan to enable/disable autogroup, however you may run as regular user to check the status or get the help dialog.
Important info on toggle-ag script usage (from the script comments):
#**Please note that toggling back and forth the scheduler will
#produce undesired effects, as it takes the system a few minutes
#to switch the process scheduler each time effectively. Imagine
#all processes that run in the backround are rearranged each time
#you switch the process scheduler. In other words you shouldn't
#toggle back and forth to make comparisons as they WILL NOT be
#effective immediately!!
Click to expand...
Click to collapse
Goo Manager Support (NEW!)
You can now download my custom kernels, recovery, tweaks, etc from Goo Manager, available on the Play Store. Goo Manager is similar to ROM Manager, except it works very well with my release of TWRP 2.2.2.0.
First time use instructions:
Set Download path to: /sdcard/goomanager/ in "Settings" (This is important as the location on Android and TWRP need to both be exact same!)
Go back to the main screen in Goo Manager and click Browse Compatible Roms
Choose 'godmachine81'
For kernels choose a100_kernel (you are welcome to look around in my other directories)
Choose the release you wish to download
Choose 'begin download'
You will see a notification for 'Download Finished' - Tap on it
It will prompt you to Select Zip(s) to flash, you may choose more than 1!
After you have selected all the zips you want to flash, go to the option 'Order and flash selected' or if you want to add a zip from a custom location, choose the 'Add zip from another location option'
Once in the Order and flash menu, it is important that you set the order to flash in the proper order, when you are sure it is right, then click Flash (First time you use Goo Manager, it will prompt you that an OpenRecovery is needed, choose that you already have one)
After You click flash, the system will reboot to TWRP, flash your .zip files, and reboot back to android without any user interaction.
ZRAM
What is it?
Zram was developed so that systems with a limited amount of physical ram may allocate a percentage of that to a system swap device using compression. By compressing the data that is in the swap space you can fit more data into the same amount of ram. For example App#1 is consuming 500mb of a total 725mb ram, this leaves you with 225mb free. If you have Zram enabled then App#1 may begin to swap to the zram device, when doing this you will have an advantage, because any amount of data from App#1 that gets swapped out to Zram will be compressed meaning it is actually using less physical ram. So instead of only 225mb free of 725mb you may now end up with something more like 400mb free because data from App#1 is compressed in Zram, in this example thanks to compression you cut the 500mb memory usage of App#1 to 325mb. Zram should have a minimal impact on performance while giving you the benefit of fitting more data into the amount of physical ram your device has.
HOWTO
This kernel includes functional ZRAM support, however to take advantage of it you must enable it from userspace (Android). Cyanogen Mod has an option in Settings > Performance > Memory to enable Zram, however it doesn't properly work - I'm not sure exactly how it is coded in the cm sources, but when you enable zram it doesn't create the zram swap device like it should. To work around this I wrote the following flashable .zip files that contain a script to automatically create the zram swap device at boot, please download and flash the size you wish to allocate to zram:
Zram - 100MB (14% ram)
Zram - 150MB (20% ram)
Zram - 200MB (28% ram)
Zram - 250MB (34% ram)
Zram - 300MB (41% ram)
Zram - 350MB (~50% ram)
To Disable/Remove Zram
In the event that you want to disable Zram then just remove the file(s) at:
/system/etc/init.d/50zram-*
After the 50zram- file has been removed, just reboot your device and you will no longer have Zram enabled. To re-enable just reflash one of the above files.
Flash Back stock kernel?
For those who wanted it: stock-kernel-signed.zip click here to download the stock ICS Kernel - This is the Stock CM kernel from The Android_Device_Acer_A100 Prebuilts on github.
To cut down on general discussion in this thread please note that I have been in the Freenode IRC Dev channel a lot lately. server: irc.freenode.net channel: #iconia-dev - My IRC handle is godmachine81 Join me there for general discussion if you don't mind. Thanks!
Video of Kernel in action on CM10 (appologize for audio and poor quality)
*All references to the Xtreme releases has been removed due lack of time needed to maintain it aside from the stable releases - will update the thread when I Xtreme development gets back underway
ChangeLog:
2.0
Backport several bits mainline code from Linux 3.5 - including Security, ARM Libs, MM, and Android specifics
Zcache + Cleancache added
Ability to concatenate kernel cmdline configuration to Bootloader's cmdline without breaking compatibility with any bootloaders ( needed for zcache/cleancache to work)
Zram patches and updates
Clean up dmesg logs
Deadline IO Sched tweak (1:1 ratio writes/fifo) - VR remains default IOsched
CONFIG: turn off some verbose logging/debugging to reduce overhead, enabled Load Lens Correction Data to smooth out camera operation
TweakIO init script included by default to optimize disk read/write performance
Several other small patches and tweaks to underlying sources
1.6
Minor patches to sources and configuration
1.5
GPU voltage and frequency updates
Interactive governor updated from N7 grouper
Adjust frequency scaling per core for new interactive gov.
1.4
This release was a testing Xtreme release which has recently been removed due to lack of development
1.3a
Script: toggle-ag now included in zip, installs to /system/xbin/toggle-ag
Default IO Scheduler V(R)
Default CPU Governor Lulzactive
1.2b
Bug Fix release for 1.2 - BFQ randomly causing "black screen" issue immediately after boot animation, preventing full boot - reboot resolved issue in most cases, but comes back at random on boot - Setting default I/O scheduler to NOOP until BFQ issue is resolved.
1.2
Autogroup per UID instead of TTY task (huge improvement to autogroup on android)
Set BFQ as default I/O Scheduler
Allocator: Switch to SLUB from SLAB
Remove verbose debugging symbols
Set proper firmware/calibration paths for WiFi in configuration
1.1
Add userspace support for undervolting
GPU OC (400mHZ) on CPU OC > 1000mHZ
Fix "Recent Apps" bug - The glitchy behavior when loading an app cached in the "Recent Apps" menu. Pointed out by DarkNight
Tune SmartassV2 for better behavior and ideal freq set at 760mHZ
Add the following CPU Governors: Lionheart, SavagedZen, Lazy, Scary, Intellidemand, LagFree, Wheatley
Deprecated the non-autogroup release also known as (default)
various other improvements to CPU, voltage, video.
1.0.1b
Add SmartAssv2 CPU Governor
Fix LOCALVERSION
1.0.1
Patched MMC_CAP_ERASE as precautionary to avoid hard brick
1.0-pre
V(R) I/O scheduler Added
SIO I/O scheduler Added
Zram sources backported from 3.0 resolved compile issue
Alpha (First public download)
Overclock added: Min Freq: 216 Max Freq: 1504
CPU Governors: Lulzactive, Ondemand, Interactive, Conservative, Userspace, Performance, Powersave
IO Schedulers: Noop, Deadline, CFQ, BFQ
Autogroup or Default Kernel available
Patch for Tiny HAL - resolves popping in audio on JB/ICS
Click to expand...
Click to collapse
If you would like to help out with the continuance of kernel development for your Acer Iconia Tab A100 please consider a small donation to help out with bills, baby formula, wipes, diapers, etc. All donations are very appreciated by my family and I! Thanks
​

This kernel is pretty slick, tested a previous version of it, nothing but good things to say of it, hit thanks on your way to flash this.
Tapatalked from my Galaxy S II.

pio_masaki said:
This kernel is pretty slick, tested a previous version of it, nothing but good things to say of it, hit thanks on your way to flash this.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Same to all your projects pio_masaki! I always hit the "thanks" for you too buddy! BTW, the kernel you have been testing is the equivalent in the downloads section to the "default", you may want to take a stab at the "autogroup" kernel. I have been testing it with great responsiveness. Also added in SIO and tweaked some timings/voltages in the new downloads. Glad to hear you have had good results thus far

linuxsociety said:
Same to all your projects pio_masaki! I always hit the "thanks" for you too buddy! BTW, the kernel you have been testing is the equivalent in the downloads section to the "default", you may want to take a stab at the "autogroup" kernel. I have been testing it with great responsiveness. Also added in SIO and tweaked some timings/voltages in the new downloads. Glad to hear you have had good results thus far
Click to expand...
Click to collapse
Yup I have every intention of banging that new kernel, waiting a minute while I build yet another CM10 for further testing of the autobrightness levels, added a couple more slots into the array, should have it nailed this time.

pio_masaki said:
Yup I have every intention of banging that new kernel, waiting a minute while I build yet another CM10 for further testing of the autobrightness levels, added a couple more slots into the array, should have it nailed this time.
Click to expand...
Click to collapse
Was really curious to see how BFS performed with Jelly Bean /ICS either one, but i've not had any luck with getting BFS to run stable so I removed it from my kernel tree for the time being. If i can get a full port to the grouper tree with all our device sources, I'm pretty confident I can get a newer revision of BFS to working. From most of my experience with other devices and other x86 systems though, the BFS doesn't out perform Autogroup anyway, but its mostly just curiosity that makes me want to go through all the trouble of getting it working with tegra2. On another note, I'm not sure why but regardless of the kernel or configuration I use Jelly Bean seems to have a weaker performance in any benchmark than the same kernel/configuration used in ICS. I'm yet to figure out where the bottleneck is in JB. (testing with linpack, quadrant, antutu benchmark all produce lower scores than with ICS) The thing that is most important to me is the actual user experience and feel that you get and not some benchmark score.. I can say that JB is very smooth and the scores don't mean nothing if you don't look at them!!

Awesome kernel! Seems stable enough, audio also works
sent from my A1/500 Iconia slab of awsomeness

Every time I download the zip file and try to flash it I get a Failed message. I am using TWRP to flash with.

tidewaterns said:
Every time I download the zip file and try to flash it I get a Failed message. I am using TWRP to flash with.
Click to expand...
Click to collapse
download it again

tidewaterns said:
Every time I download the zip file and try to flash it I get a Failed message. I am using TWRP to flash with.
Click to expand...
Click to collapse
In TWRP do you have MD5 verification enabled? If you do then it should work after you turn that off, the zip file is signed with SignAPK.jar so it should work without any issues. I have personally flashed both to my device using TWRP. If you are using adb through TWRP to push the .zip then you shouldn't be pushing it to /sdcard/ in recovery the proper location for internal storage is /data/media/ so if you have pushed it to /sdcard/ in adb then it will exist in a directory where permissions aren't accurate for the loader. Push with adb to /data/media if in recovery, or push to /sdcard/ if pushing with adb while your tablet is booted to Android OS.
If for some reason the .zip files are corrupted on github for other users please let me know and I will recompile, recompress, resign, and reupload.. Thanks

Fransis88 said:
download it again
Click to expand...
Click to collapse
Francis88: I assume the zip files flashed ok for you? Anyone else having problems?

Mine works fine. Flashed with twrp. Of course, I cleared dalvik before I flashed. The rebooted. Works fine.
sent from my A1/500 Iconia slab of awsomeness

I really don't like flashing from internal, and twrp, at least 2.1.1, says sdcard for whatever one is mounted. Keep that in mind when flashing in twrp. I think 2.2 says sdc instead. Also in jellybean it goes to storage/sdcard0 for internal sdcard1 for external sdcards. You can probably still use the old paths but those are the correct paths for jellybean.
Tapatalked from my Galaxy S II.

I copy everything to my SD card. You can flash from it.
Actually, I've only ever flashed from internal once, it was jb gapps
sent from my A1/500 Iconia slab of awsomeness

das_webos_transformer said:
I copy everything to my SD card. You can flash from it.
Actually, I've only ever flashed from internal once, it was jb gapps
sent from my A1/500 Iconia slab of awsomeness
Click to expand...
Click to collapse
Well I'm not saying you can't its more of a personal call to never store stuff I don't want to lose on internal, especially since it gets wiped when I wipe for testing.
Tapatalked from my Galaxy S II.

I think there may be some confusion when I say "internal" and "/sdcard" Assuming that one doesn't have an external sdcard, then /sdcard would be internal storage while in android OS (meaning ICS, Gingerbread, Honeycomb, Jellybean, etc), and that same path would be /data/media while in TWRP/CWM (Recovery mode). I've never had my external sdcard (removable one) to mount at /sdcard or /mnt/sdcard on my a100 so I assumed it was safe to recommend flashing from there as I have never had any issues with it, but like I mentioned in the previous post, /sdcard is only your internal user storage while booted into Android OS and not while in Recovery, while in Recovery the symlink doesn't exist so the right location is /data/media..
If anyone isn't familiar with the hierarchical file system and the mount points for their device, then I strongly encourage them NOT to use experimental ROMS, Kernels, etc. including this one. The kernel is a very critical part of the software on the device, and without a working kernel, you WILL NOT have a working device. So if something happens that you don't have the original kernel backed up and a way to flash it, or a full backup that you can access from recovery, then testing experimental kernels is like playing with fire..
A soft brick is highly possible if you obtain: A) the wrong kernel for your device B) a corrupted download kernel -OR - C) An experimental kernel that may be misconfigured or contain "bad" source code. << All of these can be repaired easily from recovery if you have a known good version to restore from, but if you have trouble flashing one kernel that is known to flash successfully for others, then what happens when you get the Fail message when trying to restore your working kernel/system??
Hope nobody takes this the wrong way, just trying to look out for people before things go bad. Good luck..

pio_masaki said:
Well I'm not saying you can't its more of a personal call to never store stuff I don't want to lose on internal, especially since it gets wiped when I wipe for testing.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I have never had to wipe the internal user storage AKA /data/media & /sdcard while testing any build, Of course it would be very easy to mess things up and accidentally wipe it from recovery, but I've never ran into any issues needing my internal SD wiped (so far).
Pio_masaki you could be talking about something else by internal storage though? Like /system or / or somewhere other than /data/media, /mnt/sdcard[0-] ?

linuxsociety said:
I have never had to wipe the internal user storage AKA /data/media & /sdcard while testing any build, Of course it would be very easy to mess things up and accidentally wipe it from recovery, but I've never ran into any issues needing my internal SD wiped (so far).
Pio_masaki you could be talking about something else by internal storage though? Like /system or / or somewhere other than /data/media, /mnt/sdcard[0-] ?
Click to expand...
Click to collapse
No I mean internal SD. I fully wipe /data including /data/media. Occasionally I dd zero them all too.
Tapatalked from my Galaxy S II.

linuxsociety said:
In TWRP do you have MD5 verification enabled? If you do then it should work after you turn that off, the zip file is signed with SignAPK.jar so it should work without any issues. I have personally flashed both to my device using TWRP. If you are using adb through TWRP to push the .zip then you shouldn't be pushing it to /sdcard/ in recovery the proper location for internal storage is /data/media/ so if you have pushed it to /sdcard/ in adb then it will exist in a directory where permissions aren't accurate for the loader. Push with adb to /data/media if in recovery, or push to /sdcard/ if pushing with adb while your tablet is booted to Android OS.
If for some reason the .zip files are corrupted on github for other users please let me know and I will recompile, recompress, resign, and reupload.. Thanks
Click to expand...
Click to collapse
I do not have MD5 verification enabled. Every time I try to flash it gets to the Verifying partition sizes then I get a failed in red on the screen.

tidewaterns said:
I do not have MD5 verification enabled. Every time I try to flash it gets to the Verifying partition sizes then I get a failed in red on the screen.
Click to expand...
Click to collapse
I would redownload, that's usually a cause if everything else is good. Any error message, like status 7?
Tapatalked from my Galaxy S II.

I finally got it installed and I overclocked it to 1504 mhz . Thanks for your help!
Sent from my A100 using xda premium

Related

[kernel][2.6.29](18th Sep) OC/UV kernel with user configurable UV apk -Voodoo support

Thanks to Leshak , AndSecTest, mimocan, Unhelpful, xan, Supercurio and husq510 for the help.
This project started based on information found here:
http://forum.xda-developers.com/showthread.php?t=740514
But is has soon revolved into more fixes, patches and hacks. Thanks to all the developers involved and do buy them beers so they can continue to work on the fixes.
I've tested it to work on my phone but i cannot guarantee it will work on yours or if it will damage your phone so use it at your own risk. See known issues below if the problems have been resolved
Primary Features
- ext2/3/4
- Support I/O Scheduling for CFQ (stock), Noop, Deadline and Anticipatory
- Overclock and Undervolt support
- Overclocking for better performance. If you do not want to OC, use SetCPU to set Max at 1Ghz and enable checkbox Set on boot
- User defined Undervolt to save battery especially at lower frequencies. Use Xan's app for easy GUI control - here
- Also use Xan's app to change IO scheduling
- Rooted ADB shell for Android commander compatibility
Requirement
- i9000
- For Eclair 2.1 Only (Will not work on Froyo firmware)
My setup for cross compile without wakeup lag
- Use ct-ng crosstool
- Copy config file from arm-unknown-linux-gnueabi
Download
See attachment
Stock Kernels for reverting
Stock JM3 v3 kernel
Stock JM2 kernel
Stock XWJM5 kernel
Instructions:
- Extract the tar file from .7z
- Load tar file in PDA using ODIN and flash
- Do not check repartition and do not use pit file
- Use SetCPU to adjust frequencies
Reporting Problems
Please provide information below to help me understand:
kernel version: (eg oc120uv2-ctng)
UVLF setting (if kernel supports): (eg 50)
UVHF setting (if kernel supports): (eg 25)
descriptions:
Known Issues
- ondemand setting is unstable (need more verifications)
TO DO LIST
- BFS scheduling
- kernel modules (submit request)
Changelog
oc120_voodoo_b4.2
- enable CWM support even with voodoo ext4. Caveats: CWM will unmount /data after nandroid backup, you will not be able to remount /data in ext4 until you reboot back to recovery. Also, restore does not work when trying to restore /data.
- fixed check for debug_mode (it used to create logs in /sdcard/Voodoo/logs regardless if you enable*debug in /sdcard/Voodoo/)
oc120_voodoo_b4.1
- BLN patch v4 from neldar (http://forum.xda-developers.com/showthread.php?t=772672)
- All credit goes to author
- Signed update.zip format so rename file to update.zip and copy to /sdcard
- use recovery to flash
oc120_voodoo_b4
- updated to voodoo b4 (http://project-voodoo.org) - please read Documentation/FAQ, if you have previous installed Voodoo Beta1, please uninstall before upgrading
- Excludes color patch for later release
- All lagfix credit included in this build goes to Supercurio, please buy him a beer or two so he can continue on working on the project
oc120_voodoo_b3.1
- fixed init.d not working
oc120_voodoo_b3
- remove performance governor from startup cos i9000 dont need that
- added init.d support
oc120_voodoo_b2
- Use stock GPU ~200mhz table
- Voodoo2 lagfix (http://project-voodoo.org) - please read Documentation/FAQ, if you have previous installed Voodoo Beta1, please uninstall before upgrading
- Excludes color patch for later release
- All lagfix credit included in this build goes to Supercurio, please buy him a beer or two so he can continue on working on the project
oc120uv2
- Unhelpful patch for GPU table (http://github.com/Unhelpful/linux-galaxy/commit/5a729d3e2189159a20b00e0c331f0b112490e075)
- Interactive governor (http://github.com/Unhelpful/linux-galaxy/commit/aea72a98a2f261901d6f28f2d1deae3921d35948)
- user configurable UV settings (default value = 0 for UVLF and UVHF) for conservative governor only
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (for 100-800mhz)
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (above 800mhz)
- for example # echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (will UV by 50mV for 100-800mhz)
- for example # echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (will UV by 50mV for 1-1.2ghz)
- Setting increment of 25 (eg 25,50,75,100). Anything out range may hang
- Anything above 100 will be set to 100 (but I doubt you can get 100mV without crashing)
- After setting, do ur benchmarks and if everything is stable, you can add the command above into your init script depending which lagfix you have, add into your script.
Thanks!
Some questions:
1) the first thread about oc mentioned 1.2ghz, was this unstable for you?
2) Is this over-volted, under-volted, or no changes in voltage?
3) I'm guessing if I update to this kernal, I will loose any features of other kernals, like the lag-fix kernal?
I hope you can persuade the other devs to include this in their roms.
It this just for the unbranded SGS or does it work for TMO vibrant too?
Novek said:
It this just for the unbranded SGS or does it work for TMO vibrant too?
Click to expand...
Click to collapse
the kernel is just for the international version
it is just a test, i hv not test the limit yet.. this is a new phone so want to take it easy
i kept the voltage stock so just overclock a little and if its stable, will do more . More testing and reading is needed before i touch on the voltage.
it does not include mimocan's mod, i will work on it next release
Not Work
Hi GS S user,
not work in XXJP3 rooted Firmware!
Flash, Boot and go in Recovery menu!
Sir-ay said:
Hi GS S user,
not work in XXJP3 rooted Firmware!
Flash, Boot and go in Recovery menu!
Click to expand...
Click to collapse
XXJP3 is froyo.. android 2.2
he clearly states it works in eclair... android 2.1
Nice job cant wait to see how high the new hummingbird cpu can go. The galaxy s 2 has same cpu and is running at 2 ghz (if the leaked info is correct). I hope we can push it up to 2ghz with out to much voltage/heat increase.
[[ Cold ]] said:
XXJP3 is froyo.. android 2.2
he clearly states it works in eclair... android 2.1
Click to expand...
Click to collapse
upps
I will OC!!!!!!!!!!
Do you notice the postive effects of the overclock in any way? What does it do with benchmarks? Also do you test for (temperature) stability with some games as well, as they use the graphics card a lot which is on the same chip. Even when not overclocked the SGS can get prettty warm.
Installs nicely, oc ok to, but dont see that much increase in linpack.
Nice work tho.
Any chance to have ext 4 support in next update?
Thanks :
updated to v2
raspdeep said:
updated to v2
Click to expand...
Click to collapse
you're fast, lol. Thanks.
INeedYourHelp said:
your fast, lol. Thanks.
Click to expand...
Click to collapse
update before i go to bed
Guys, how do I use SetCpu?
Was 1.2ghz unstable?
Sent from my SGH-T959 using XDA App
interested in this... Allthough the phone does seem to get hot during heavy use, it doesn't get 'too' hot.
I have seen about 47 degrees celcius max read from battery temp (which seems to be cpu temp on our phones as my battery was stone cold)
Hi any possibility get v1 without mimocan.
Got samset including it nd sgs wnt boot cause of mimocan included.
thanks
I am using JM2. Does this make my phone any faster? Does it maked it lag free?
After tested this oc.. i am bit unsure: i get no performance increase... Is it confirmed that its functional?

[Kernel][DEV] pax0r kernel v0.4 for LG P350 (Optimus ME, Pecan)

THIS KERNEL IS NOW OBSOLETE, DON'T USE IT.
Mine newest and stable kernel releases are now integrated into my version of CyanogenMod 7.2, please use only a kernel provided with that ROM, not this one.
Im leaving it for historical reason or for some geeks
The testing release of kernel for p350 based on kernel by drapalyuk - taken from kernel and rom + sources
I do not take any resposibility for bricked devices!
This kernel aims to optimize the performance, responsivity and battery life so please share your opinion about these factors and your ideas.
If you are experiencing any problems with WiFi or 3G try much less tweaked but more stable LITE version.
Instalation:
Download zip to your phone
Get the Custom Recovery for p350
Reboot into recovery
Backup your boot partition (if you like risk you can ommit this step )
Choose Flash zip menu
Turn off verification (as I dont signed my kernel yet)
Flash downloaded zip
Reboot and enjoy
Changelog(2.6.32.48 version):
[0.4]
Fixed black screen after wakeup issue
Added vr and sio I/O schedulers (SIO is default)
Added smartassv2 governor
VM_MAX_READAHEAD changed to 512
[0.3]
Kernel version updated to 2.6.32.48
BFS CPU Scheduler
Applied few tweaks from https://github.com/arco/buzz-kernel-2.6.32/
Some other small tweaks (List of applied patches is on github)
Compiled with newest Linaro toolchain with -Ofast flag and tuned to our architecture
LITE version:
For all guys having problems with internet connection on my kernel there is a LITE version.
It contains less tweaks thant normal version but should not have problems with internet. This version is much less tweaked so it should be more stable.
What is in lite version:
Kernel version 2.6.32.9 (not updated)
Smartass v2 governor
SIO and VR IO schedulers (SIO as default)
VM_MAX_READAHEAD changed to 512
Compiled with newest Linaro toolchain with -Ofast flag and tuned to our architecture
If you dont have any problems with 0.4 version I reccomend NOT to install Lite version
DOWNLOADS
version v0.4: http://hotfile.com/links/139705983/d792c47/kernel-pax-0-4.zip.html
version Lite: http://hotfile.com/links/139705851/518d0ef/pax0r-kernel-lite.zip.html
SOURCE: https://github.com/pax0r/pecan_kernel
Thx for:
drapalyuk - for biggest work for this device
All other devs for Android kernel - as I can learn so much from all of your work!
Debuging Info
or how to help make it better
If you have any problems with my kernel and you want to help in some way - here it is some info how you can.
Just after apearing of the problem please get logs from your device.
How to do it:
Info on CM wiki how to get Logcat
http://wiki.cyanogenmod.com/wiki/Logcat
Info about getting kmesg:
Open Terminal Emulator (or shell with ADB if you know how)
Write the following commands:
Code:
su
cat /proc/kmsg > /sdcard/kmsg.log
There should be new file kmsg.txt on your sdcard. Copy it to your PC.
info about last kmsg after sudden reboot/crash
Same as for normal kmesg but the command now should be:
Code:
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Created file will be named last_kmsg.txt
Attach all logs to your post (prefered way is to use http://pastebin.com/
Of course if you have any programming skills you can tinker with my sources as you wish and send patches to me
Hi Pax0r,
I will test the new kernel!
Great, file not found
Sent from my Optimus Me using XDA App
thanks from the Philippines bro..
downloading it now.. will let you know how it goes..
edit : just booted up and already like it.. i had a problem with drape's rc3 kernel because everytime my phone went to sleep and i would wake it up, the screen would just stay black and the buttons would light up and i would have to touch the screen for it to turn on.. now that problem is history!!! thanks paxor!!!!
SikatPimp said:
edit : just booted up and already like it.. i had a problem with drape's rc3 kernel because everytime my phone went to sleep and i would wake it up, the screen would just stay black and the buttons would light up and i would have to touch the screen for it to turn on.. now that problem is history!!! thanks paxor!!!!
Click to expand...
Click to collapse
i still experience that problem. well after the kernel's flashed, does that mean it will run the next time the phone's booted up?
downloading...
edit:screen stays black like before..
uploaded to mediafire
Daryll99 said:
Great, file not found
Sent from my Optimus Me using XDA App
Click to expand...
Click to collapse
here..i uploaded it to mediafire. enjoy
www . mediafire . com/ ?l5cqpdhvi8c8acw
ikazu said:
i still experience that problem. well after the kernel's flashed, does that mean it will run the next time the phone's booted up?
Click to expand...
Click to collapse
ok i just got excited. it seems i still get the touch screen problem but it happens less frequently now and right now i am also cruising at 825 mhz with no fc yet !!!
SikatPimp said:
ok i just got excited. it seems i still get the touch screen problem but it happens less frequently now and right now i am also cruising at 825 mhz with no fc yet !!!
Click to expand...
Click to collapse
tried playing games with 825 freq?
---------- Post added at 05:23 AM ---------- Previous post was at 05:21 AM ----------
on screen animation dsnt work either
Thx for feedback.
I also noticed the 'black screen issue' sometimes and working on it. Drapalyuk fixed it in CM but its not in his sources :/
What versions of ROM (CM, 2.2 etc) do you use?
only angry birds... can't tell any difference but still no fc
---------- Post added at 02:17 PM ---------- Previous post was at 02:08 PM ----------
I'm using drape's 20.10 rom... and before i would reflash to try and get that black screen took care of but in a couple days it would come back.. and it isnt so bad.. it doesn't really effect anything.. but after flashing your kernel i am getting them less now so thats a plus..
So you know How to compile the kernel
will you try to add more features ???
can you add these features
Code:
* shifted to TinyRCU kept it as default
* enabled support for various file systems
o EXT3
o EXT4
o JBD
o RFS
o JFS
o NTFS (with R/W)
* TUN/TAP now integrated into kernel
* enabled support for various network file systems
o NFS (client/server)
o CIFS
* optimized kernel for size
* enabled LZMA/GZ2/LZO compressing support for ramdisk
* bumped jHash to v3
* increased VM MAX READAHEAD to 512KB
* corrected "current kernel" string in CWM app & Tweaks app
* Universal CF-Root and CWM for I9003 Gingerbread by amit.bagaria
* CPU Governors
1. InteractiveX
2. Savaged-Zen
3. SmartAssV2
4. BrazilianWax
5. Smoothass
6. Lagfree
7. Smartass
8. Scary
9. MinMax
10. Interactive
* I/O Schedulers
1. BFQ-v2-rc1
2. V(R)
3. SIO
I flashed the kernel and now everytime i try to turn on the wifi its says error, it wont turn on. And please fix the blackscreen issue.
Daryll99 said:
I flashed the kernel and now everytime i try to turn on the wifi its says error, it wont turn on. And please fix the blackscreen issue.
Click to expand...
Click to collapse
Maybe try flash again.
If it would not work I will check on this issue later.
There must be some problem with loading wifi module for your phone...
vivekkalady said:
So you know How to compile the kernel
will you try to add more features ???
can you add these features
Code:
* shifted to TinyRCU kept it as default
* enabled support for various file systems
o EXT3
o EXT4
o JBD
o RFS
o JFS
o NTFS (with R/W)
* TUN/TAP now integrated into kernel
* enabled support for various network file systems
o NFS (client/server)
o CIFS
* optimized kernel for size
* enabled LZMA/GZ2/LZO compressing support for ramdisk
* bumped jHash to v3
* increased VM MAX READAHEAD to 512KB
* corrected "current kernel" string in CWM app & Tweaks app
* Universal CF-Root and CWM for I9003 Gingerbread by amit.bagaria
* CPU Governors
1. InteractiveX
2. Savaged-Zen
3. SmartAssV2
4. BrazilianWax
5. Smoothass
6. Lagfree
7. Smartass
8. Scary
9. MinMax
10. Interactive
* I/O Schedulers
1. BFQ-v2-rc1
2. V(R)
3. SIO
Click to expand...
Click to collapse
I will try do as much as I can - thx for some kind of list of 'thigs I should look at'. Few comments I have:
About governors - there will be smartass v2 for sure in next version - I just hadnt time to integrate it in this release (I tested it earlier at it really was smartass )
I/O Schedulers - deadline is quite enough for sd cards, but I will look into this SIO as it is based on deadline - thx for hint. I think rest of them is not needed.
File Systems - do we really need support for them? More supported format means bigger kernel.
"optimized kernel for size" - I prefer optimize for speed and it is done
Thanks again for this list - looks very interesting
Havent find the Governer in the cyanogen Mod ??
do I have to use external apps to select that governer??
edit : wifi working Fine
vivekkalady said:
Havent find the Governer in the cyanogen Mod ??
do I have to use external apps to select that governer??
edit : wifi working Fine
Click to expand...
Click to collapse
The governor does not come with the cyanogen mod ofLG p350. No you can't use external apps to install that governor,assuming it is smartass
Sent from my Optimus Me using XDA App
pax0r said:
File Systems - do we really need support for them? More supported format means bigger kernel.
Click to expand...
Click to collapse
It would be great if ntfs file system is supported as it is fast
Sent from my Optimus Me using XDA App
Daryll99 said:
The governor does not come with the cyanogen mod ofLG p350. No you can't use external apps to install that governor,assuming it is smartass
Sent from my Optimus Me using XDA App
Click to expand...
Click to collapse
I know that Dude
But we need external apps to select which Governer and I/O scheduler to be used even if it is in the boot.img. Not installing but selecting
no-frill app is used in my phone (i9003) it contains all the above items in the list i have specified earlier
Its from i9003 by doomload it contains all the things
https://github.com/DooMLoRD/SGS-SL-i9003
Hm... I can select governor from CM menu (performance -> CPU settings - not sure about english names ; ) but be aware of a fact that there is no smartass here (yet ), just standard ones (ondemand,usersapce,powersave,performance)
Sadly your kernel from i9003 is .35 one an here we have .32 so patches do not apply so easy...
But when I will have more time (Im in the middle of Bsc thesis ) I will try to port some .35 kernel for p350

[KERNEL] [LG ROMS ONLY] [D802 Only] StockMOD Kernel v3.00 [3rd Dec 13]

StockMOD Kernel for D802 international phones
Suitable for Official LG and LG-based roms ONLY
Only for D802 International models​
Features:
- ExFAT support for USB OTG / Card readers with large drives
- CIFS network share mounting supported
- Voltage control support (no built in UV, but configurable via apps like SetCPU)
- Optimised kernel libraries
- MSM SoC + Kernel "always-on" logging and debugging disabled to save CPU cycles
- Simple GPU governor
- Ondemand governor tweaked for lower latency speed shift changes
- Internal kernel function fixes (ie, memory leaks, scheduler fixes)
- SIO scheduler (default, noop, cfq and ROW are available)
- high performance, low latency kernel
- compiled with Os flags and neon-vfpv4 FPU enabled
- Westwood+ TCP congestion control
- Built from official LG v10a kernel source
- Lokified during flash
Installation:
- Download .zip and copy to phone
- Reboot to recovery
- Recommended to take full system backup, including EFS partition
- Flash .zip
- Reboot
- 1st reboot may take a little longer than usual
Please do not:
Do not ask for other models to be supported, at this time is D802 only. Other models may follow in the future
Do not ask for extra features. This is to be a stock-compatible replacement kernel only. If LG didn't add it, I probably wont either.
Do not ask for support of other roms, such as CM / AOSP. Im a LG based rom user, if you want a kernel for another type of rom either use one of the available ones we already have or learn to compile your own.
Download
Download the kernels from my FTP here > FTP Directory
Archive of older versions https://app.box.com/s/k8prx3pyxgd866aidd9x
Changelog:
v3.00
- Carefully rebased, some previously used commits removed
- Back to O2 compression
- (most of) Viking's Ondemand governor settings preapplied
- Added init.d script support
- Fixed battery drain and temperature issue some had
- Reverted to a more stock-like config for less issues
v2.60
- Reverted all VM and ramdisk changes, back to kernel defaults
- Reverts most ramdisk changes, rebuilt from fresh stock ramdisk dump
- Should fix android and network logging
- Decreased Ondemand CPU frequency shift latency to 8ms
- Removed some GPU logging functions
- Stock GPU governor is default
- Full neon-vfpv4 FPU optimisations
- Fixed 3d game problems some had with 2.20+beta 2.50
v2.20
- Some configuration changes
- Some minor system tweaks
- Firewall logging re-enabled
v2.06
- Cleaned up ramdisk
- Sensible, well tested VM and Ondemand values set during boot
- CIFS network mount support added
- Increased vibrator strength
- CPU Sync (idle before rampdown) frequency increased to 1190mhz (default is 960mhz, battery life / heat seem virtually unaffected)
- Simple GPU governor set as default (no longer needs manual activation)
- 99% kernel debugging and logging now disabled. (Android logger still available)
- Ondemand governor is recommended
v2.03
- Once again a complete rebuild
- Fixed CPU utilisation issue with v2.00
v2.00
- Rebuilt from scratch (code cleanup)
- Switched to full neon-vfpv4 compiler flags for fpu
- Switched to Google GCC 4.8 toolchain
- Switched to O2 optimisation level
v1.03
- Fixed audio interference on headset
- Improved UI smoothness
- Faster boot
v1.02
- Added Westwood+ TCP congestion control
- Disabled more debugging and logging for adreno and krait cpu
- More internal fixes
v1.01
- More internal kernel fixes
- Reduced minimum CPU voltage than is user configurable to 700mv (default voltages are unchanged)
- Disabled some ramdisk controlled LG specific logging and debugging (more CPU cycles saved)
v1.00
- First release
Sources:
Kernel sources github > Kernel Github
Ramdisk + Build script > Ramdisk Github
Credits and thanks:
- LG
- Wootever (for loki flash scripts and binaries, and some elements of the build script)
- Faux123, Gokhanmoral, franciscofranco and the CM team for some commits
If you want to return to the original D802 10b International kernel please download and flash the zip attached to this post
reserved2
Hi,
Yeah!
Glad to to have been a tester
Thanks for your kernel! This one looks great
viking37 said:
Hi,
Yeah!
Glad to to have been a tester
Thanks for your kernel! This one looks great
Click to expand...
Click to collapse
thank you for being a patient tester! your feedback was appreciated, as well as the time you have been testing it for me. :good:
g.lewarne said:
thank you for being a patient tester! your feedback was appreciated, as well as the time you have been testing it for me. :good:
Click to expand...
Click to collapse
Re,
You're welcome
I just saw that you had added SIO i/o scheduler, thanks for this... It has always worked well for me, I mean for my devices
viking37 said:
Re,
You're welcome
I just saw that you had added SIO i/o scheduler, thanks for this... It has always worked well for me, I mean for my devices
Click to expand...
Click to collapse
ah yes, thanks for the reminder, will add that to OP
I have flashed this kernel combined with your ROM and so far so good.
Love the rom. Trying the kernel!.
Sent from my LG-D802 using Tapatalk
Bootloop after installing kernel.
Sent from my LG-D802 using Tapatalk
gentlemandroid17 said:
Bootloop after installing kernel.
Click to expand...
Click to collapse
Hi,
Weird, no issue here. You are the first
Maybe a bad download?
EDIT: you are on LG based rom, right?
Agreed. Flashed on Rayglobe 2.6 about 2 hours ago and have been running fine since.
Sent from my LG-D802 using Tapatalk
I also have Bootloop after installing kernel.
installed on the : [ROM][Stock][LG-G2 D802 international] StockMOD rom, Fast, Fluid, Lagfree - v1.06
I am on g.lewarne's rom. First boot went fine. Got bootloop on reboot.
Sent from my LG-D802 using Tapatalk
gentlemandroid17 said:
I am on g.lewarne's rom. First boot went fine. Got bootloop on reboot.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Are you guys running any "set xxx parameter on reboot" type of apps ?
I've been flashing these kernels, as have my esters for nearly a week and have not had any issues with them. The only thing I can think is you have an app which is trying to do something on boot up....
My phone was stock fresh, full wiped, installed my rom, then all the test kernels and 0 issues
gentlemandroid17 said:
I am on g.lewarne's rom. First boot went fine. Got bootloop on reboot.
Click to expand...
Click to collapse
I just tested, no bootloop after reboot...
You have not flash something else (a tweak or a mod) or modifying something? Undervolt (too much and set on boot)?
I don't know, maybe wait g.lewarne...
viking37 said:
I just tested, no bootloop after reboot...
You have not flash something else? A tweak/mod? Undervolt (too much and set on boot)?
I don't know, maybe wait g.lewarne...
Click to expand...
Click to collapse
im starting to wonder if there are some subtle phone hardware variations that we are not aware of... ? (and im not talking 16/32gb since kernel is the same according to LGs sources)
either that or its is some app installed trying to do something funky....
@ g.lewarne, exept the CPU binning, I don't know
viking37 said:
@ g.lewarne, exept the CPU binning, I don't know
Click to expand...
Click to collapse
IKR
I mean, in Wootevers kernel thread there have been similar reports of sporadic non-compatability and although our kernels are quite different, the basic hardware controlling bits are the same. Even if the SoC had different variations, why would the stock LG kernel work for everyone when one built from their own source wont ?
Its either an app, or the sources LG share are not the "real" ones they use, which I have some suspicions about for other reasons
gentlemandroid17 said:
I am on g.lewarne's rom. First boot went fine. Got bootloop on reboot.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
is your phone a branded phone ?

[KERNEL][AOSP 4.4.x][2GHz/1.89 GHz] UBER 4.1 | LINARO 4.7.4

Hey Everyone,
I'm by no means a pro at kernel building but I've put lots of effort into these kernels so I thought I'd share them with you. The Uber kernel will always be updated to the latest Kernel version and will be overclocked to 1890 MHz or 1998 GHz (2 GHz) you decide which option you are willing to do. Unlike some of the other T-mobile Galaxy S II Hercules developers out there, I actually have a Galaxy S II and plan on having it until Summer 2014. This means that EVERY KERNEL I POST HAS BEEN TESTED AND IS WORKING although it might not be perfect (few things in life ever are).
Even though I don't post anything unless it works I still don't want to be liable for user errors. In other words, if you flash one of these Kernels your warranty is void and I AM NOT RESPONSIBLE for any data loss or bricked devices etc. ​A Clean install is ALWAYS recommended. That does not necessarily mean you can't install these kernels on you current build it just means that you might have problems if you do. Recently apps have been getting corrupted for whatever reason whether on Stock or AOSP and in most cases they cause RRs and SODs. If you find yourself in one of those situations a clean install is the easiest fix. If you want to try and save you apps then connect to you phone while in recovery using adb. Then type adb shell. Now once you are in that shell you can run this command to fix your apps "e2fsck -yfDC0 /dev/block/mmcblk0p25" it could take anywhere from a few minutes to an hour depending on the state of your apps.
​
[AOSP 4.4.x UBER KERNEL LINK]
UBER 4.1 - 1.89 GHz RELEASE for AOSP 4.4 KitKat
UBER 4.1 - 2 GHz RELEASE for AOSP 4.4 KitKat​
​
All old Kernels can be found on Dev Host via this link (be careful you read file names and descriptions carefully if you choose to take a peek around) http://d-h.st/users/Cl3Kener/​
Installation Instructions
**** IMPORTANT!!! USE TWRP 2.6.1.0+ for 4.4 kernels!!! Failure to do so may result in bootloops due to changes made to TWRP to accommodate SELinux in 4.4 ROMs (Links include flashable TWRP installation zips credits to meekrawb. Just flash them in your current recovery! ) ****
1. For best results a install these kernel after a fresh ROM install (although it still should work if you don't do that)
2. Reboot into recovery (MAKE SURE YOU USE THE RIGHT ONE!!! (See red print above))
3. Flash Kernel Zip
4. Reboot and let Settle for ~10 minutes
5. Install Trickster MOD from the App Store for access to all of the options.
6. Change the settings to something other than INTERACTIVE (Especially if you run it with BFQ it will give you the worst screen lag ever). Then enable "Set at Boot" and push the check mark button at the top right hand portion of the screen or else you will lose your configurations.
7. Enjoy!!!
​
Error Reporting
I am always open to hearing about your errors although just telling me something went wrong without giving me details does me absolutely no good. So here are my expectations if you do want to complain about something not working:
1. Please list the ROM you are using,
2. The IO scheduler you were using
3. The CPU governor you were using
4. The CPU frequency range (192/1080 etc)
5. What you have done to attempt to fix it.
6. If you were able to simulate it again using the same settings.
7. Anything else you think is applicable to the issue
I would also hope that you would consider trying some of the following things to fix your issue before you ever report it because most of these things will fix the problem without me even having to change a thing.
1) Fix file permissions using a program that does a thorough job. I recommend using the fix file permissions in ROM manager because it is the best I’ve seen. For the record, I don’t actually use ROM manager for anything other than fixing permissions. Please consider trying this first because it tends to fix most of the FC/RR/SOD errors you might have.
2) Make a backup and install a clean version of the ROM you are running and see if you are still experiencing those same errors. You may have corrupted files if you’ve been dirty flashing.
3) If that doesn’t solve it, redownload and reflash, maybe something got corrupted but it still managed to flash. This happens sometimes and I can cause you grief.
4) For advanced users pull a logcat. I know not everyone knows how to do this but you can learn if you check out this OP or other ones like it
SPECIAL THANKS TO:
Android88 - because he is awesome and encouraged me to create this thread!
Samsung - for the source code to build these Kernel (and for making the phone)
Ayysir - for his wonderful tutorial on making a bash script to build kernels and for helping me out all of the time with everything!
Elbermu - For Bringing Thermal and Sweep2Wake to Hercules and for the help!
Bmg002 - For his extensive work fixing/rewriting my init.d scripts
Gruntparty - For completely redoing/fixing the build.prop injector I use for my AOSP Kernels
I Am The Frost - For being my first and best tester on xda. He's debugged several issues in these kernels for me
UBER Kernel Repositories can be found at https://github.com/Cl3Kener/HERC-KERNELS and are properly labeled for your convenience (see the branches)
Informational Links
Here is a fantastic guide on "Innards" of Kernels
Optimizing Linaro Keychains
Building a Bash Script to make Kernels​
JOIN MY GOOGLE COMMUNITY IF YOU WANT INSTANT UPDATES ON ANY OF ANDROID STUFF I DO. ​
​Reserved!
XDA:DevDB Information
[KERNEL][AOSP 4.4.x][2GHz/1.89 GHz] UBER 4.1 | LINARO 4.7.4, a Kernel for the T-Mobile Samsung Galaxy S II
Contributors
Cl3Kener
Kernel Special Features:
Version Information
Status: Beta
Created 2013-12-02
Last Updated 2014-01-30
Changelogs
Changelogs
Changelog UBER 4.1 Release
- ONLY FOR ANDROID 4.4.2 CM 12/16 Nightlies and beyond!!!!
- Kernel Version 3.0.101 - Linaro 4.7.4 2013.12
- USB fastcharge
- MORE TCP Options "Veno as default
- Fsync toggle - disable for better performance but beware that if your phone crashes you will lose data.
- Overclocked CPU 1890 or 2GHz/ GPU 3D = 320 2D = 266
- IO Schedulers - cfq, bfq, row, noop, deadline, sio, vr, FIFO, and zen
- CPU Governors - intellidemand, interactivex, lazy, wheatley, smartass, badass, lionheart, minmax, fantasy, savagedzen, scary, HYPER and samsung.
- Frandom Lag Reducer
- Smaller sized kernel due to xz compression.
- CPU link - elbermu
- Sweep2wake - thanks dennis rassmann (@show-p1984) for his awesome code and elbermu for modifying it to fit this device!
- Thermal - thanks once again to dennis rassmann (@show-p1984) for his awesome code and elbermu for modifying it to fit this device!
- IO Booster
- CPU Power - Vincent Guittot
- Frontswap Support
- Google "Snappy" compression/decompression
- KGSL GPU Control - carvsdriver​​
Additional Info
Terminal commands to enable/change a kernel features if you are don't like kernel tuning apps
Fsync
To enable - echo 1 > /sys/module/sync/parameters/fsync_enabled
To disable - echo 0 > /sys/module/sync/parameters/fsync_enabled
USB Fast Charge
To enable - echo 1 > /sys/kernel/fast_charge/force_fast_charge
To disable - echo 0 > /sys/kernel/fast_charge/force_fast_charge
Set Thermal Values
Go to /sys/kernel/msm_thermal/conf/ in a root file browser and change the values
Set MPDecision Values
Go to /sys/kernel/msm_mpdecision/conf/ in root file browser and change the values
Disable CPU Link
echo 0 > /sys/kernel/cpu_gov_sync/force_cpu_gov_sync
Recommended CPU Govs by Category
For Performance
Performance Governor - Full OC
HYPER - full oc
Lionheart - full oc
For good battery life with decent performance use
Intellidemand
Interactivex
Ondemand
Samsung
Lazy
Moderately Conservative
Badass
Conservative
Wheatley (debatable could be in the above category)
Very Conservative
Powersave
SavageZen
not sufficient info? checkout out this op
​
Sweet! New kernel!
Sent from my SGH-M919 using Tapatalk
Sweet! Will try this out right now :good:
Flashed beautifully thanks @CI3kener
Sent from my SAMSUNG-SGH-T989 using Tapatalk
gotta love the uber, thank you kener
Sent from my SAMSUNG-SGH-T989
Thank You !
Will this work on alpha 3??
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
JNMM said:
Will this work on alpha 3??
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Yes ?
Sent from my SAMSUNG-SGH-T989 using Tapatalk
3 New Performance Boosters
Hey Everyone,
For those of you who haven't heard I've been using "Koding" as my new kernel build server. Space is very limited with my free account but if you'd like you can click here and signup to help me get more free space. You'll also find that you can learn how to code just about anything (java, html5, php, to name a few). Many developers and adding tutorials and sharing their projects so if you are interested in that stuff make sure to sign up!
I've made two nightlies this morning which need testing. For those of you who were around for my 4.3 you might recall that somewhere along the line there was suddenly a curious SD Card Mounting/Unmounting that would happen after unlocking the phone. I had made so many commits in such a short time frame that I was unsure which one caused the error. I've gone back and added my top three performance improving commits from the questionable series to see if any of these three commits caused the error (I certainly hope they did not, I really hope it was caused by the LZ4 compression and not the performance boosters). Let me know if you see any problems as you use these nightly kernels!!! Remember these are for 4.4 ONLY!!!
Here are the links!
UBER 1.89 GHz
UBER 2 GHz
Cheers!
Cl3Kener
just to let you know i have not been getting the sd card error on the 4.4 uber
Signed up on Koding maybe you can teach me a thing of two (^o^)
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Confirmed working on almites cm build
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
BETA2 For 12/16 CM Nightlies and Beyond
Hey Everyone!
Well Team Chopsticks finally got video working although from what I can tell all of the work was actually all done by our very own @bryan2894 who went and found the patches that fixed the video!!! Great work @bryan2894!!! Part of this video fix included the kernel so here is an updated kernel with the patch needed. This kernel will only have fixed video on CM 12/16 nightlies and beyond. I bet it might work with earlier but you might as well update if you are a CM user so what's the point?
Anyhow, enjoy the updates!
Cheers!
Cl3Kener
PS since I know someone will ask, This actually does work great with the 12-14 HellKat build since it also has working video because we grabbed the patches from CM before they were merged.
Sent from my SAMSUNG-SGH-T989
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
syan8182 said:
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
Click to expand...
Click to collapse
That stuff is nonsense. The latest TWRP in fact is much better for this phone and flashing this or any other ROM here IMHO. I tested both CWM and TWRP on more than one occasion and results were identical. For me TWRP is also much easier to get into when you have an issue with a new ROM booting and you need to get into recovery via the power & volume up buttons.
syan8182 said:
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
Click to expand...
Click to collapse
I've flashed CM11 (my builds) about 10 times in the last month and have been using TWRP 2.6.1.0 since Sept. without issue.
Just don't try to flash TWRP from within GooManager, either flash from recovery or use Odin (best).
Since the video recording is working now I moved to CM11 using the @Almite (Rom) and @Cl3Kener (Uber 2GHz kernel) and I can tel you this is solid Rock combination in performance and stability even those are still in Nightlies/Beta so thank you all for this amazing team work...
Is it possible to add the BLN notification (I know some don't like it but usually this the feature can be disabled)
Thanks

Custom Lolipop Kernel for Asus Zenfone 2 ZE551ML/ZE550ML

Note: This kernel will work on stock firmware2.20.40.184, 2.20.40.183, 2.20.40.178, 2.20.174, 2.20.40.168, 2.20.40.165, 2.20.40.164 and may be lower, also working on some stock-based ROMs(EchoeROM V3,for example).
Disclaimer: I am not responsible for your broken phone , broken memory card, etc. All my kernels I test first on my own phones , and then upload here
If you like my works please do not forget donate to me(PayPal account you may find in my profile)
Bootloader unlock is required for every custom rom, custom kernel, custom recovery. Unlock Tool here:http://forum.xda-developers.com/zenfone2/general/tool-one-click-bootloader-unlock-root-t3155884
Changelog:
03.06.2016
Full NTFS support for SD card
NTFS OTG full support by sibling Asus File Manager(read/write), from others file managers you can to see OTG NTFS devices, may see OTG NTFS devices from file chooser but you can't edit data. But you can edit platform.xml via NextAPP SDfix and can write on NTFS OTG devices
14.05.2016
Migration to newest source code from Zenfone Zoom ZX551ML from 20 april 2016
Ramdisk from 183 firmware
Some optimization in code
17.04.2016
Full support exFAT SDcard format, now you may write/delete/rename by standart method of Android 5
16.04.2016
Great game performance
Remove Hotplug driver
Remove -Ofast optimization(loud words-not take effects, placebo)
Remove optimization flag -march=silvermont(loud words, did not work on 3.10 kernels)
Remove touchboost from Interactive governor
Modified Interactive, Interactive Pro, Intel, Cyan governors: CPU2 and CPU3 turn off when screen off
Idle from Linux kernel 4.6
Gpu governor simple_ondemand from Linux kernel 4.6
Based on source code from Zenfone Zoom ZX551 from march 17
zram and kernel compression is LZ4
04.03.2016
Rework MSM Hotplug, now only CPU0+CPU1 online, no dancing CPUs.
For humor and proof that overclock in others kernels is fake added "overclock" to 5GHz
28.02.2016
Re-work MSM Hotplug. Now if load more than 79 but lower than 99- only another 1 core go to online(CPU2 or CPU3)) and processor working on 3 cores online, if load more than 99- CPU3 and CPU2 go to online together and processor working on all 4 cores online DO NOT set fast lane 99 and higher!!!
Made 12 thermal states for video adapter a place of 3. If on 457 MHz have overheating- freq go to 400 MHz, if overheating on 400- go to 355, if hot on 355-go to 320 MHz and so on. In stock kernel if overheating on 457 MHz- processor goes in 200 MHz and was lags in games
25.02.2016
Compile with new march=silvermont optimizationmarch=silvermont(thanks to @Dan_Jacques )
Tuning MSM hotplug for Zenfone 2: now interface faster, smoother even when min cpus online = 2. And maybe drain battery less.
Unlocked almost all hidden GPU frequencies. Now available gpu frequencies 106, 133,160,177 MHz(I think this NOT fake underclock). I made Kernel Auditor version for our GPU PowerVR 6430 (see screnshots here http://i10.pixs.ru/storage/5/8/1/Bezimyanni_7545670_20843581.png ) https://drive.google.com/file/d/0BxVRXQGBg4DTaThjQUtoRFBrdms/view?usp=sharing
21.02.2016
Based on Asus Zenfone Zoom source code
Fixed hotplug driver and tuning(Now drain battery much less and fixed charging: now no overheating)
Added Cyan governor
Changed Interactive governor to Interactive from Asus Zenfone Zoom
18.02.2016
Now 2 different versions: for ZE551ML and for ZE550ML, Tuning MSM Hotplug(2 cores always online, Fast Lane up to 150), added Interactive Pro governor and set by default
04.02.2016
Interactive governor by default, realtime Hotplugging now on any governors, on Interactive too(Extra CPU cores disabled without load) Idea and work @mrg666 . You may to set parameters of hotplug driver via Kernel Auditor, point "CPU Hotplug"
Remove Hotplug governor(no longer needed)
Kernel Features:
1.Based on Zenfone Zoom ZX551ML source
2. Add zram support in LZ4 format(no need to turn on it, if no problem with multitasking and never no need to turn on for devices with 4GB RAM), kernel compression LZ4 too
3. Adaptation InteractiveX V2 governor for quad core devices, I make that 2 cores go to offline, when screen off
4. Processor work in "1 cpu per module" mode a place of "2 cores per module"(4 independent cpus, not pair)
5. Ofast and march=silvermont(thanks @Dan_Jacques optimization with GCC 4.9
6. Init.d support. You should install BusyBox in /xbin folder/
7. SELinux Permissive
8. KVM support (Kernel Virtual machine for Intel)
9. Added SWAP support
10. USB-HID mouse & keyboard functions(required USB Keyboard app from GPhttps://play.google.com/store/apps/details?id=remote.hid.keyboard.client&hl=en)
11. Ultra kernel samepage merging(UKSM) a place of KSM. Disabled by default, if you want you may turn on it via Kernel auditor
12. Full auto brightness. I removed minimal level 15, now level 5
13. More governovs and I/O schedulers
14.Zram disabled
15. More TCP algorithms, Westwood by default
16. Unlocked GPU frequencies 106, 133, 160, 177 MHz
17. NTFS support for SD card and OTG
Deprecated features:
1.Hotplug governor by default. Extra CPU cores disabled without load(it have been removed sinse 04/02/2016)
2. For correct work on ZE550ML you should change DPI to 320, for example via init.d script(root required).
1). Before flash kernel, you should install BusyBox in xbin folder, then create init.d folder in system/etc and set 755 permissions on it.
2) Download dpi320.zip, then extract dpi320 file and put it in system/etc/init.d folder, check that on it set 755 permissions
https://yadi.sk/d/6hg6bDDioCNbT
3). You may flash kernel.
3. Interactive governor from Asus ZenPad S 8.0 by default with some tuning(for example, hi_speed freq = 1583 MHz) and hotplugging additions( 2 cores go to offline, when screen off) Idea and work by @TheSSJ
4. Realtime hotplugging for all governors. You may to set parameters of hotplug driver via Kernel Auditor, point "CPU Hotplug"
5. Interactive governor from Asus Zenfone Zoom by default with some tuning(for example, hi_speed freq = 1750 MHz), InteractiveX and Interactive Pro have hispeed_freq 1750 MHz too.
Step 1:
You should download files for flashing:
ADB v1.0.32: Download from Google Drive
IMG file with kernel:
03.02.2016 https://yadi.sk/d/FuJhWqc9oCLZy
04.02.2016 https://yadi.sk/d/PcDiDaumoJMb7
All versions from 18.02.2016 and higher will be here: https://drive.google.com/folderview?id=0BxVRXQGBg4DTSVV5Q19mSVUxQk0&usp=sharing
Step2:
You should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash boot bootXX.XX.img
,where XX.XX- numbers after word "boot"
Step3:
Reboot to Android.
Method 2( via TWRP, without PC)​1. Download bootXX.XX.img
2. Go to recovery mode
3. Click Install, choose this bootXX.XX.img, choose boot partition and flash
4. Then reboot
Method 3(via Terminal Emulator, without PC)(root required)​1. Download bootXX.XX.img and put it in root of internal memory
2. in command prompt write
Code:
su
dd if=/sdcard/bootXX.XX.img of=/dev/block/by-name/boot
reboot
And device started with custom boot.img
XDA:DevDB Information
Custom Lolipop Kernel for Asus Zenfone 2 ZE551ML/ZE550ML, Kernel for the Asus ZenFone 2
Contributors
BORETS24
Source Code: https://github.com/BORETS24/Kernel-for-Asus-Zenfone-2.git
Kernel Special Features:
Version Information
Status: Testing
Created 2016-02-02
Last Updated 2016-09-03
Nice work, especially the Hotplug features (maybe you should transfer your post under http://forum.xda-developers.com/zenfone2/development ?)
nazagan said:
maybe you should transfer your post under http://forum.xda-developers.com/zenfone2/development ?)
Click to expand...
Click to collapse
Maybe... How I can to do this?
Can you add flashable zip please? thank you.
serhangelgor said:
Can you add flashable zip please? thank you.
Click to expand...
Click to collapse
Why?
Method 2(through CWM/TWRP, without PC)
1. Download bootXX.XX.img
2. Go to recovery mode
3. Click Install, choose this bootXX.XX.img, choose boot partition
4. Then reboot
Or you can flash without PC and without custom revovery
Method 3(through Terminal Emulator, without PC)(root required)
1. Download bootXX.XX.img and put it in root of internal memory
2. in command prompt write
Code:
su
dd if=/sdcard/bootXX.XX.img of=/dev/block/by-name/boot
reboot
And device started with custom boot.img
BORETS24 said:
Why?
Method 2(through CWM/TWRP, without PC)
1. Download bootXX.XX.img
2. Go to recovery mode
3. Click Install, choose this bootXX.XX.img, choose boot partition
4. Then reboot
Or you can flash without PC and without custom revovery
Method 3(through Terminal Emulator, without PC)(root required)
1. Download bootXX.XX.img and put it in root of internal memory
2. in command prompt write
Code:
su
dd if=/sdcard/bootXX.XX.img of=/dev/block/by-name/boot
reboot
And device started with custom boot.img
Click to expand...
Click to collapse
hey bro, if you don't mind can I add up a few things for you?? it will reduce your work and since you are on kernel 3.10.20 you can try to use my direct jump patch to jump to kernel.org v3.10.94 here's the link https://github.com/Zenfone2-Dev/direct-kernel-patch
and nice work.
installed and opened only 1 core, its too good and battery life is amazing, thanks so much for this amazing work, can you add underclock feature? it will give more batterry life
serhangelgor said:
can you add underclock feature? it will give more batterry life
Click to expand...
Click to collapse
No, I don't want to add fake underclock. It give more interface freeze and nothing else besides placebo effect and boastfulness. I started to make kernel for zenfone 2 in july 2015 and using "underclock" some time- no different battery life between 500 and 250 MHz, I tried and 166 MHz and even 83 MHz- no effect besides slow and freeze interface.
say99 said:
hey bro, if you don't mind can I add up a few things for you?? it will reduce your work and since you are on kernel 3.10.20 you can try to use my direct jump patch to jump to kernel.org v3.10.94 here's the link https://github.com/Zenfone2-Dev/direct-kernel-patch
and nice work.
Click to expand...
Click to collapse
Thank you very much, may be apply this patch in future.
BORETS24 said:
Thank you very much, may be apply this patch in future.
Click to expand...
Click to collapse
made a pull request keep working and if you want you can switch to gcc 5.3.0 toolchain https://github.com/Zenfone2-Dev/x86_64-toolchain-GCC-5.3.0
BORETS24 said:
No, I don't want to add fake underclock. It give more interface freeze and nothing else besides placebo effect and boastfulness. I started to make kernel for zenfone 2 in july 2015 and using "underclock" some time- no different battery life between 500 and 250 MHz, I tried and 166 MHz and even 83 MHz- no effect besides slow and freeze interface.
Click to expand...
Click to collapse
BORETS24, can you add F2FS support? I feel the IO more smooth with it (in other phones there is a huge difference between ext4 and f2fs, like Moto G), but requires changes in kernel config file (easy) and a modified ramdisk with edited fstab (more complicated). There is an Project T version that includes a fstab with the needes changes [link=http://forum.xda-developers.com/zenfone2/development/project-t-custom-kernel-zenfone-2-t3150822/post64366155]here[/link] (but only boot with all /system /data / cache formatted in F2FS). With the correct lines, it's possible to make a mixed fstab, and supports both fs.
Changelog:
04.02.2016
Interactive governor by default, realtime Hotplugging now on any governors, on Interactive too(Extra CPU cores disabled without load), remove Hotplug governor(no longer needed)
BORETS24 said:
Changelog:
04.02.2016
Interactive governor by default, realtime Hotplugging now on any governors, on Interactive too(Extra CPU cores disabled without load), remove Hotplug governor(no longer needed)
Click to expand...
Click to collapse
hey bro, I can't find the commit for realtime hotplugging
Sent from my ASUS_Z00A using Tapatalk
Im using it, looks good, thanks
say99 said:
hey bro, I can't find the commit for realtime hotplugging
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
If will no critical bugs I will upload to Github, need time for test by users.
BORETS24 said:
If will no critical bugs I will upload to Github, need time for test by users.
Click to expand...
Click to collapse
just an advice : always upload up the commits and make two builds, test builds and stable builds, you can always revert the things you pushed to git
Sent from my ASUS_Z00A using Tapatalk
say99 said:
just an advice : always upload up the commits and make two builds, test builds and stable builds, you can always revert the things you pushed to git
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I'm just recently start to use Github, for me easier delete changes from sources on PC Ubuntu than from github before changes,I keep stable source in zip archieves, old school And I can't to know which version of boot.img is stable which is not. Will make two unstable build? Alone I can't test everything, all hope on users. If you don't want to wait, I may to say that use Autosmp hotplug driver...
BORETS24 said:
I'm just recently start to use Github, for me easier delete changes from sources on PC Ubuntu than from github before changes,I keep stable source in zip archieves, old school And I can't to know which version of boot.img is stable which is not. Will make two unstable build? Alone I can't test everything, all hope on users. If you don't want to wait, I may to say that use Autosmp hotplug driver...
Click to expand...
Click to collapse
haha I can understand maybe that's y I added up the build script. A single command and you get a flashable zip without any need to manage them and that command is ./buildzf2
and yeah I have changed the defconfig in script and made a pull request so just get a hold on that
Sent from my ASUS_Z00A using Tapatalk
Add to description of kernel:
You may to set parameters of hotplug driver via Kernel Auditor, point "CPU Hotplug"
I really love your works. You made a big update for this cpu. Can you make a undervolt for this kernel, master ?

Categories

Resources