Related
WARNING
Overclocking/undervolting could cause crashes with loss of data, or even damage hardware including the CPU or GPU.
Voodoo support included since 1.5, remove all non-Voodoo lagfixes before installing.
This works for me, but you are ultimately responsible for what happens to your device and your data - have backups, preferably on an external SD that you remove for initial testing.
These are unsigned and will not flash via stock recovery. Use ROM Manager to flash, with ROM Manager you also don't need to rename them as it can select any zip file from internal storage.
Features:
Voodoo lagfix support - should work correctly flashed over other Voodoo beta4 kernels, remove non-Voodoo lagfixes before installing.
BLN support to allow use of touch-button lights to indicate pending notifications when screen is off. The lights will light for all statusbar notifications, unless disabled in the app producing the notification (not all apps will have an option to do this, I don't think any stock Samsung apps do).
Stock voltages/clocks at boot, runtime configuration of clocks and voltages via sysfs, nilfs2 and ext2/3/4 filesystem support, two-stage user init - early scripts for mounting filesystems, late ones for running services. Default I/O scheduler is BFQ, BFQ/CFQ/anticipatory all perform roughly the same in benchmarks with multiple threads competing for I/O. Typical wakeup between instant and about one second, built with the binutils 2.19.1 / gcc 4.3.4 toolchain.
User clock/voltage configuration can be read from/written to /sys/devices/system/cpu/cpu0/cpufreq/freq_volt_table. Copy this file to get the defaults, edit your copy and write back over the original to update, or save your new file in /sdcard/sd/config, /sdcard/config, or /system/etc/config to have it applied on boot. The first column is CPU clock, the second GPU clock, the third CPU voltage, the fourth internal voltage. Changing values besides CPU clock/voltage is not recommended. You must keep 100MHz as the lowest speed. Clocks are in KHz, voltages in mV. Modify at your own risk, I find that my phone runs 1.2GHz @ 1.3V just fine, but yours may vary.
Be aware that your phone might appear to run fine with overclock/undervolt at first but crash later due to some error in calculation or data transfer - i recommend a good number of runs on something like Quadrant, and at least five minutes or so of SetCPU stress test for each frequency you add or change.
User inits must be placed in /system/etc/init.d, and properly named - names starting with "E" will run before /data and /dbdata are mounted, names starting with "S" will run right before startup is completed and normal Android services start. Inits are sorted by name, so you can follow the initial E or S with a number to change the order in which they will run. Scripts need not be executable, and will be run with the shell provided in initramfs for Voodoo support (busybox ash). If either /data or /dbdata is not a mount point after E scripts are completed, /user_early_init.sh will attempt to mount an rfs filesystem there from the usual location. If you want to mount a filesystem that is some other type, you will need to do so in a user script. If you want to format /data with another filesystem, you must edit the partition table to change the partition number - I have disabled the code in /sbin/init that rewrites the partition table, but if it finds something on standard /data partition that does not look like a valid RFS filesystem, it will reformat it.
If you want to build yourself, see the toolchains thread for known-working tools. Run
Code:
make ARCH=arm i897_defconfig
make ARCH=arm menuconfig [COLOR="blue"]optional[/COLOR]
make CROSS_COMPILE=/path/to/toolchain/arm-none-eabi- zImage [COLOR="blue"]change if using a different toolchain[/COLOR]
tar c -C arch/arm/boot/zImage >captivate_zimage.tar
Flash captivate_zimage.tar as PDA in Odin - see other threads for how to use Odin and where to get it. Use menuconfig to select a different initramfs source if you wish, by default an included one at usr/initrd_files will be used.
Starting with v1.4, create a .build_config file to change any variables and run build_kernel.sh to build tar flashable with Odin or update.zip. As of v1.5.2 you can also use .build_config to inject commands and files into update.zip builds.
CREDITS
raspdeep - the original OC code
curio - Voodoo lagfix original concept and script
neldar - BLN support
atinm - BLN port for Captivate
BusyBox, buildroot, crosstool-ng, nilfs2 - see respective projects for original contributors and source
v1.7ClockworkMod Recovery
flashable binary: mediafire mirror | github mirror
github source
BETA ClockworkMod Recovery replaces stock recovery
BETA support for backup/restore with Voodoo enabled
v1.6BLN Support
flashable binary: View attachment i897-unhelpful-v1.6.zip | mediafire mirror | github mirror
github source
BLN support - use the touch-button lights to alert of pending notification when screen is off.
Disable check for SGH-I897 device, since this can fail on Captivate hardware if an alternate ROM is flashed.
v1.5.3Bugfix release
flashable binary: View attachment i897-unhelpful-v1.5.3.zip | mediafire mirror | github mirror
github source
Revert from the config based on kepler_rev02_defconfig, suggested by the 9/6 code drop, to aries_rev02_defconfig. The config change appears to have been responsible for the power drain problems seen in v1.5.1 and v1.5.2.
v1.5.2Bugfixes and Voodoo lagfix support
flashable binary: View attachment i897-unhelpful-v1.5.2.zip | View attachment i897-unhelpful-v1.5.2.tar.7z | mediafire mirror | github mirror
github source
Odin-flashable tar file (inside 7z to allow upload to XDA), please use only to recover from bad flash of v1.5.1, the update.zip contains scripts that are important if you're running SRE.
Voodoo lagfix support
Restore correct stock voltage (1.275V) for 1GHz
Update sources and config from Captivate 9/6 source drop
Update modules from JH7 OTA
LZMA initramfs compression to reduce compressed kernel size / allow larger initramfs
Enhanced update.zip support allows developers to easily inject their own commands and files into update.zip on build, and allows run_programs scripts to produce screen output and can flash kernel/modem partitions directly.
v1.4.1BUGFIX for SRE users
flashable binary: View attachment i897-unhelpful-v1.4.1.zip | View attachment i897-unhelpful-v1.4.1.tar.7z | mediafire mirror | github mirror
github source
Bug with SRE + 1.4 causing storage to become unavailable should be fixed by this kernel, fix works on my phone but some have reported problem spontaneously ifxing itself.
v1.4Load OC/UV config from file, system early init (for developers).
downloads removed due to bugs
github source
Built with gcc-4.4.3
build_kernel.sh reads variables from .build_config, or from config file specified by $BUILD_CONFIG, so you can keep the script file clean.
Early system init - E* scripts in /sbin/init.d run before user early init, for developers to include startup scripts.
System init loading of OC/UV table - searches for config/freq_volt_table on external SD, then internal SD, then in /system/etc.
ADB checks uses the first shell found from the list bash, ash, /system/xbin/sh, /system/bin/sh, sh.
Correctly set cpufreq policy on table change - should fix resets of maximum clock to 1GHz after new tables are loaded.
v1.3.1OC/UV configuration
flashable binary: View attachment i897-unhelpful-v1.3.1.zip | mediafire mirror | github mirror
github source
Stock clocks/voltages at boot, user can add new clocks and change voltages at runtime - see above for details.
Modify stock init to avoid rewriting partition table at boot - change the partition table for internal SD, resize partitions or remake /data with a different partition number so it can be safely formatted with another filesystem.
v1.2Bugfix / update.zip / dev features
flashable binary: View attachment 389189 | mediafire mirror | github mirror
github source
Fix scaling bug, performance level was set past end of table on sleep
Scaling enhancement, selectable clock source for GPU
GPU clocked at 222MHz for all speeds except 100MHz, where it matches CPU clock
Basic build_kernel.sh script, edit to change configuration - builds unsigned update.zip with default kernel config by default
Add interactive CPU governor - enabled in build but conservative is still configured as the default
v1.1Bugfix release
flashable binary: mediafire mirror | github mirror
github source
Rework of user init, resolves lost-settings-on-boot issue for me.
v1.0Initial release for Captivate I897
flashable binary: mediafire mirror | github mirror
github source
nilfs2, ext2/3/4 filesystems
separate early and late user init
600MHz and 1.2GHz speeds, use SetCPU to enable 1.2GHz
fast scaling from low speed, skipping from 100MHz to 800MHzOther Downloads
User Init Scripts
mediafire, github - enable 1.2GHz overclock on startup
mediafire, github - start Mobile AP background service
Does this include the ability to clock at 1000 mhz?
Sent from my Nexus One using XDA App
You're my hero.
*edit*
_Opiate_ said:
Does this include the ability to clock at 1000 mhz?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yea it is, I have it set at 1200 in setcpu and I saw it hit 1000mhz a few times just watching it.
Yes, the scaling steps are 100MHz, 200MHz, 400MHz, 600MHz, 800MHz, 1GHz, and 1.2GHz. 1.2GHz is disabled at startup until the user enables it, so that the kernel can be used without overclocking.
Sent from my SAMSUNG-SGH-I897 using XDA App
So will this undo the MobileAP that was just put out. I know we had to flash a custom kernel to enable that. Will this undo it?
Clienterror said:
You're my hero.
*edit*
Yea it is, I have it set at 1200 in setcpu and I saw it hit 1000mhz a few times just watching it.
Click to expand...
Click to collapse
Never mind I just flashed it. No On demand?
Unhelpful said:
Yes, the scaling steps are 100MHz, 200MHz, 400MHz, 600MHz, 800MHz, 1GHz, and 1.2GHz. 1.2GHz is disabled at startup until the user enables it, so that the kernel can be used without overclocking.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thats great. Hell just running it at 1000mhz is a slight improvement in Quadrant. Before when I was running the stock kernel I never saw it clock above 800mhz.
Also no wake up lag at all!!!!!!!!! Great fraking job man!!!!!
jhernand1102 said:
So will this undo the MobileAP that was just put out. I know we had to flash a custom kernal to enable that. Will this undo it?
Click to expand...
Click to collapse
This does not run wlp2pservice in the init.rc, but a user script can easily be written to do that - I already have one on my phone, I'm going to add a section for init scripts in the OP when I get the chance.
Can you toss up a donation link plz :-D
Unhelpful said:
This does not run wlp2pservice in the init.rc, but a user script can easily be written to do that - I already have one on my phone, I'm going to add a section for init scripts in the OP when I get the chance.
Click to expand...
Click to collapse
Thanks for the info...looking forward to trying this out once there is a script so MobileAP still works...
jhernand1102 said:
Thanks for the info...looking forward to trying this out once there is a script so MobileAP still works...
Click to expand...
Click to collapse
Yeah that's one reason I still use my Nexus One mainly. The ability to tether is built right in to Froyo. But I can wait for tethering till we have a kernel that will do both. I prefer to play with this kernel now. Lol
Sent from my Nexus One using XDA App
_Opiate_ said:
Yeah that's one reason I still use my Nexus One mainly. The ability to tether is built right in to Froyo. But I can wait for tethering till we have a kernel that will do both. I prefer to play with this kernel now. Lol
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yeah hopeful it can be put in the same kernel then we can have the best of both worlds...
I just found something strange. When I reboot and enter set cpu the phone say I have to chose my device again so I have to choose autodetect again.
Sent from my SAMSUNG-SGH-I897 using XDA App
do we just flash this with odin ? in the op there are many intrsuctions on putting stuff here and there i got lost
_Opiate_ said:
I just found something strange. When I reboot and enter set cpu the phone say I have to chose my device again so I have to choose autodetect again.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Every time I reboot it's all in Russian again like the first boot with JM5 lol.
Crizthakidd said:
do we just flash this with odin ? in the op there are many intrsuctions on putting stuff here and there i got lost
Click to expand...
Click to collapse
Yep, just use 7zip and extract the .tar then flash with odin3 as PDA.
Wow, unhelpful you are the MAN. Put up a donate link, I'll send a few beers your way.
Works!!
Unhelpful, you're probably one of the MOST helpful people on this forum. haha
minor bug, usb debugging doesn't seem to stay on between reboots.
and i can't seem to send emails using the gmail client anymore
IStern said:
minor bug, usb debugging doesn't seem to stay on between reboots.
and i can't seem to send emails using the gmail client anymore
Click to expand...
Click to collapse
ditto on the usb debugging, wont stay on between reboots
I managed to get init.d working on the EE03 leak but it broke logcat, I switched to the no-op scheduler and it seems to be quite a bit more responsive =p
I wish I could post how I did it but xda thinks a file path is an outside link and wont let me submit it...
Is this useful at all? I don't know much about android but I'm a linux nerd by profession
chairface said:
I managed to get init.d working on the EE03 leak but it broke logcat, I switched to the no-op scheduler and it seems to be quite a bit more responsive =p
I wish I could post how I did it but xda thinks a file path is an outside link and wont let me submit it...
Is this useful at all? I don't know much about android but I'm a linux nerd by profession
Click to expand...
Click to collapse
Makes sense that noop i/o would be more responsive as it's designed for flash memory devices. Init.d is supported by default in cm7 and it's always handy to have it around for keeping things out of the original init.<device>.rc without having to recompile initramfs.
All you need is 10 posts and you'll be able to post whatever you need.
You can also use the 'CODE' tags to paste paths, etc.
init.d was enabled via the initramfs in the kernel. Scrips go in /system/etc/init.d - and have on every ROM with initscripts enabled.
Thanks for the tip on the scheduler - feel free to play around with the other settings. Have a look at the tweaks thread for some possibilities.
k0nane said:
init.d was enabled via the initramfs in the kernel. Scrips go in /system/etc/init.d - and have on every ROM with initscripts enabled.
Thanks for the tip on the scheduler - feel free to play around with the other settings. Have a look at the tweaks thread for some possibilities.
Click to expand...
Click to collapse
/system/bin/sh can't parse if [ <x> ] statements...
the block in twilightzone.sh that says
<code>
if [ -d /etc/init.d ]
then
run-parts /etc/init.d
fi
</code>
should be changed to
<code>
/sbin/busybox [ -d /etc/init.d ] && /sbin/busybox run-parts /etc/init.d
</code>
thanks for all your hard work man
also the updater-script has to set everything in /etc/init.d to 755 - it doesn't in ee03
I wasn't aware init.d support was there until after I wrote the script.
oh haha
I changed /system/bin/sh to point to busybox... the only thing it seems to break is logcat =\
before I did this nothing in /etc/init.d worked, if I did
/sbin/twilightzone.sh
it wouldn't run /etc/init.d but if I did busybox sh /sbin/twilightzone.sh it did
I probably broke a lot of other stuff doing this too but it's working well so far.
while I have someone knowledgeable here, is it possible to extract/repack the zImage? I'm assuming either ACS did that or used an older 2.2 kernel
~~~~~ Latest release
A500 - V1.0.1 (first stable release)[Size=+1]
ezT20-v1.0.1-a500_S.zip
MD5: 73e25f9970dc5f34d863a2c7155968d2
[/SIZE]
**Please remove all undervolting and overclocking before installing, as different kernels will use the CPU differently, This may require you thus to change the OC/UV levels to be stable with this kernel.
While plenty of work has gone into ensuring this kernel was fit for use: I take no responsibility for any problem the use of this kernel may cause, and/or loss of data if you fail to backup your data before installing it. Proceed at your own risk
Notice: This kernel will only operate on an unlocked ICS bootloader, for the a500 this is the patched bootloader
A500 Installation: : simply flash the zip from recovery, this will extract and replace the zImage (linux kernel) from your current rom; and leave your existing ramdisk unchanged.
A501 Installation: :Your ICS rom requires to load the new simdetect_switch.ko module on boot, if your rom dose not have support for this, but has support for init.d scripts please first install the patchkit ezT20_a501_patchkit_S.zip MD5: 617f558555c13d215103cd3669d3c009, (This kit only includes the init.d script to load the simdetect_switch module if it exists, and doesn’t include the actual kernel or modules)
After the patch kit is installed (or if it has been previously installed/is part of your rom) you can flash the a500 zip above to install the kernel + related modules.
CM (9 and 10) installation Install per your device above, then install the audio patch init.d scripif you have audio problems: ezT20cmaudio_patch_S.zip MD5: 26251900115b0ca433f26f4d95e7f269 (see this post for more information)
Are you an A100 user? you are in the wrong place see here
~~~~~ ICS Kernel Features
- BFQ IO scheduler (details here)
(BFQ is now the default scheduler, previously was noop)
- Lulzactive CPU governor (by tegrak with a500 modifications by myself)
(Interactive will be the default governor for most roms, as defined on the ramdisk, however lulzactive is recommended)
- Max OC speed: 1504MHz (default 1000MHz)
- Min OC speed: 216MHz (default 216MHz)
- Fixed voltage tables to allow OC on devices previously unable to on A500-OCTestV3 and A100-OCTestV1
- initial 3g support thanks to patches from Vash (v1.0.0 - a501) .. switched to acer's code in v1.0.1 (a501/a101)
- ability to disable acer audio settings (v1.0.1)
~~~~~ Kernel Notes/Warnings
** A specialized lulzactive configuration program can be found at: https://play.google.com/store/apps/...1bGwsMSwxLDMsImNvbS50ZWdyYWsubHVsemFjdGl2ZSJd
(note setCPU will also let you change the values, I only mention tegrak's app as it may make it easier to understand what is being changed)
** The kernel ought to work in place of the stock ICS kernel, roms requiring special kernels may not function with this kernel
** de-odexed roms may have graphical artifacts that are made more serious by this kernel, civato and I have been working on a build.prop tweak to re-generate odex like dex files on de-odexed roms to solve this
** Voltage display may not be accurate (a rework of the UV logic is planned) note UV offsets are accurate.
The following is using the following:
* My Near stock rom
* My disk-io tweak for the rom
* lulzactive Min: 216 Max 1504
* BFQ scheduler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
~~~~~ Kernel History
This kernel is the continuation of the Overclocked Test kernel, originally posted for the A500 here and subsequently for the A100 here
~~~~~ Credits
Thanks to:
* richardtrip - original OC and MIN/MAX code
* tegrak - for lulzactive
* civato - for being a willing advanced tester
* Bobg1231, Metallkasten, pio_masaki, Moscow Desire - additional testers
* Vash - A501 3g modem patch set
* Acer/NVidia for providing the source to our devices
* The countless number of people that have created the linux kernel in the form it is today
~~~~~ Release Build list w/ source links
v1.0.1 ezT20-v1.0.1-a500_S.zip
MD5: 73e25f9970dc5f34d863a2c7155968d2
Github: https://github.com/ezterry/AcerTabKernel
Tag: ezT20_kernel_v1.0.1
Tarball: https://github.com/ezterry/AcerTabKernel/tarball/ezT20_kernel_v1.0.1
v1.0.0 ezT20-v1.0.0-a500_S.zip
MD5: 007f00e576bf82f9439f9567685dd255
Github: https://github.com/ezterry/AcerTabKernel
Tag: ezT20_kernel_v1.0.0
Tarball: https://github.com/ezterry/AcerTabKernel/tarball/ezT20_kernel_v1.0.0
NET-USB modules [Experimental] for this version: http://forum.xda-developers.com/showpost.php?p=27887611&postcount=52
v0.9.9 ezT20-v0.9.9-a500_S.zip
MD5: c43844babbd96ab43399a100d74d60de
Github: https://github.com/ezterry/AcerTabKernel
Tag: ezT20_kernel_v0.9.9
Tarball: https://github.com/ezterry/AcerTabKernel/tarball/ezT20_kernel_v0.9.9
~~~~~ Change Log
v1.0.1
*) Import of acer's 3g code [A101 and A501]
*) audio updates to better work with CM roms when cm audio patch is applied ezT20cmaudio_patch_S.zip MD5: 26251900115b0ca433f26f4d95e7f269
*) Allow lower min-voltage
v1.0.0
*) cleanup graphics logic with more patches from the nvidia tegra test kernel (and other patches to prevent the graphic under-runs causing screen flashes on some roms) [applies to all devices]
*) modify lulzactive (yet again) to attempt to stem a rare deadlock .. frequently resulting in a SoD overnight on my tab (probably not most peoples constant SoD problem) [applies to all devices]
*) Add Acer A501 patches for 3g modem [applies to A501]
*) fix some touch events on the A50X caused by the a100 patch set rolling back the a500 touch driver, the touch drivers are separate so this ought not impact the a100 [a50x only]
v0.9.9
Initial release, providing some bugfixes and new features to the previous OCTestV3
**build instructions in second post
Developers Corner
~~~~~ Background
As you may know the linux kernel is considered Free Software under the GPL.
To the creators of the GPL licence this means:
The Free Software Definition said:
“Free software” means software that respects users' freedom and community. Roughly, the users have the freedom to run, copy, distribute, study, change and improve the software. With these freedoms, the users (both individually and collectively) control the program and what it does for them.
Click to expand...
Click to collapse
Full text here
This means when Linus Torvalds changed the licensing from "Non-Comercial" use to the GPLv2 he was no longer preventing the kernel from being used in commercial products (as is obvious by its use on all android devices) However requested that anyone who received a copy of the software, get or be offered a copy of the source as well, and to be allowed to modify that source and distribute those changes to someone else, with the only restriction being they must also provide the source so the next person can also make changes.
Mind you this dosn't mean free software is actually free. Countless hours of hard work by countless people make the kernel what it is today.
While we all must provide the source, if something isn't already in the kernel that you want you have only the following options:
1) find someone willing to make the change
2) pay someone to make the change
3) roll up your sleeves and make the change yourself.
Also note one makes you give away changes you write to the linux kernel, you only must give the source to those who already have the binary.
~~~~~ This Guide
This guide will help you build the kernel yourself on your computer from source, this is in hopes that you may take an interest in how both the build system, and kernel its self works.
Instructions will be primarily focused on both linux, and cygwin users; however osx users may also be able to follow this guide with only minor modifications.
If you do make changes you think the public is interested in I will also be happy to review and potentially include it in my future builds, remember however while its polite to credit me for the codebase provided, you may always distribute you modified versions of the kernel as long as you adhere to providing the source per the GPLv2 to those you distribute it to.
~~~~~ Getting Started - Downloading The Toolchain
The toolchain is the compiler used to convert the 'C' code of the kernel into the arm instructions red by your device.
To build this kernel I use a custom android toolchain based on gcc4.6.3;
Pre-built binaries are available for x86 linux, cygwin, and osx:
1) Download the one for your platform
x86 Linux: toolchain-4.6.3.tar.bz2 (Sha1: c8c57aba6ad92e9acddf29ba
Cygwin: toolchain-4.6.3.cygwin.tar.bz2 (Sha1: 6947e1c1ba95195019f542eb8ba0708667b63eca)
OSX: toolchain-4.6.3.darwin.tar.bz2 (Sha1: 9a977f0672863fdd9501383a6ad1e30723281f
Additional details about these files are on my Android Software post:
http://forum.xda-developers.com/showthread.php?t=1686310
All users may wish to look over the cygwin building requirements there to ensure there system has the required packages.
Other information on the post will include information about retrieving the source to the tool chain its self and another overview of building android kernels in general, and not just this specific Acer kernel.
2) Now that you have the toolchain you want to extract it; this can be done anywere but I recommend for the sake of this guide in your posix home directory
this is done by running at your posix prompt (cygwin terminal in windows normal terminal in linux/osx)
Code:
mkdir -p ~/android
cd ~/android
tar -xjvf </path/to/>toolchain-4.6.3.cygwin.tar.bz2
substitution '</path/to/>toolchain-4.6.3.cygwin.tar.bz2' with the file you downloaded above
all versions will extract then to '~/android/toolchain-4.6.3/' all the files required to build arm binaries
~~~~~ Getting the source code
This can be done many ways, if you want to build a specific version the tarball may be easiest, however it is recommended that you use the git revision control software if you wish to make changes, as this helps keep track of the changes, and publish them on services such as github. (in addition its easier for other people to take the changes into there own work without you loosing credit)
3) To get the AcerTabKernel source change directory into the ~/android directory used to make the toolchain
Code:
cd ~/android
4) run the command to fetch a copy of my git repository
Code:
git clone git://github.com/ezterry/AcerTabKernel.git
5) change into that directory
Code:
cd AcerTabKernel
~~~~~ GIT only, switching code views
Once you have the source code you can always refresh it with git fetch origin, however more work is required to update the local files
Option A: following a branch (recommended if you want the latest source)
6.A.1) run 'git branch -a'
you will likely see the following:
master - you local version of the master branch
remotes/origin/HEAD -> origin/master -- indication master is the default branch
remotes/origin/master -- the remote version of master (as of the last 'git fetch origin' or 'git pull' command)
remotes/origin/tegra_overclock -- the remote version of tegra_overclock (as of the last 'git fetch origin' or 'git pull' command)
the two branchs of interest are as follows:
master - the acer A100/A500 source including my enhancements w/o overclocking support
tegra_overclock - the full enhancement list with overclocking
6.A.2) Create a local version of tegra_overclock
run:
Code:
git branch tegra_overclock origin/tegra_overclock
6.A.3) Switching branches
you can switch between the branches by calling
Code:
git checkout <branch name>
so if you want to build this kernel you will call:
git checkout tegra_overclock
Option B: retrieving a specific tag
6.B.1) If you want the code to a specific kernel you can force the checkout of a tag
Code:
git chekout -f [color=gray]<tagname>[/color]
so for the v0.9.9 you can run
Code:
git checkout -f ezT20_kernel_v0.9.9
This will fetch the code, however you local branches will not be updated if you make changes, see on screen note for details
~~~~~ Building the kernel
Once you have the code you can build the kernel (or make other changes first)
7) Set up your build enviroment
Most steps above need not be done any time you make a change; however every time you want to build from a new terminal you must set up that terminals environment as follows
A) add the toolchan to your path:
Code:
export PATH=$HOME/android/export PATH=$HOME/android/toolchain-4.6.3/bin:$PATH
B) run the following commands to prepare the cross compiler from within the directory with the code (ie 'cd ~/android/AcerTabKernel')
Code:
export ARCH=arm;export CROSS_COMPILE=arm-linux-androideabi-;export KERNEL_DIR=`pwd`
*note I make this one line to make it easier to copy and paste all at once
8) Now that the enviroment is set up we can configure the kernel by running
For A500 Kernels:
Code:
make picasso_defconfig
For A100 Kernels:
Code:
make vangogh_defconfig
This will grab the default configuration for the device (same as /proc/config.gz on the running kernel) in the source tree this is arch/arm/config/picasso_defconfig or arch/arm/config/vangogh_defconfig
9) if you want to change the config (add/remove modules and components or change the kernels name):
Code:
make menuconfig
this will provide the kernel configuraiton gui that allows you to update the many kernel options including adding modules.
10) build the binary kernel
Code:
make -j5
you should replace the 5 in -j5 with the number of CPU cores in your computer + 1. 5 is ideal for a quadcore CPU.
If the number is lower/higher the kernel will take longer to build. (slightly higher however will have minimal impact)
11) prepare the modules (makes sure the modules are ready for use, they are built in the previous step)
Code:
make modules
~~~~~ Packaging the kernel
At this point you can find the kernel in arch/arm/boot/zImage and if you search for files ending in *.ko you will find all the built modules
However here I will describe creating the update.zip installer
Note this may look difficult as the process is mostly manual not automated
12) Download the template (I will assume you are in the directory with the kernel source still)
Code:
wget [url]http://android-git.devnull.name/gh/tepl/acer_kernel_tmpl.tar.bz2[/url]
This template contains the update_binary, unpackbootimg and mkbootimg binaries
In addition it has the ufsd.ko acer stok module (a closed source kernel module used for mounting ntfs disks) the updater-script you will use, and a nfo.prop template
koush is to thank for the unpackbootimg source (unpackbootimg/mkbootimg I built using the A500 Public Recovery source tree, updater_binary is from the stock ICS installer)
13) for future use move the template outside your source directory in case you delete/refresh it
Code:
mv acer_kernel_tmpl.tar.bz2 ~/android/
14) make the update.zip work directory
Code:
tar -xjvf ~/acer_kernel_tmpl.tar.bz2
15) copy over the zImage
Code:
cp arch/arm/boot/zImage acer_kernel_tmpl/[color=gray]<kernel_name.zImage>[/color]
the kernel_name can be any name you wish to call the kernel
16) copy in the modules
Code:
cp `find | grep ko$ | grep -v ufsd` zImage acer_kernel_tmpl/system/lib/modules/
17) copy in modules.order
cp modules.order acer_kernel_tmpl/system/lib/modules/
18) edit the nfo.prop
update the values as per the comments, this will control the displayed output during install
as well as allow you to specify any name for the zImage to be installed without
touching the edify script
19) generate the installer zip
Code:
cd acer_kernel_tmpl
zip -r ../kernel_install.zip .
cd ..
now kernel_install.zip can be flashed from clockworkmod (as an unsigned zip) or you may optionally sign the zip now to publish
~~~~~ What next
What next is up to you, there are many source files to look at some never used for our devices.. and many that I've never looked at.
One important thing however is learning the basics of git revision control, and how to maintain your local mirror and keep it in sync with the version I have on github.
Other interesting git features include remotes allowing you to compare source from other kernel repositories and even cherry-pick individual commits from other users.
If you know how to code, learning this isn't difficult so off to 'git help' and google you go
Hi there Terry - looking forward to giving this a try. Also, thanks for going above-and-beyond on the GPL thing and giving really detailed instructions - I've never compiled for Android in my life so it made interesting reading.
Hey
Can wé flash it with cwm or wé néed es nvflash
Thank s
rayman95 said:
Hey
Can wé flash it with cwm or wé néed es nvflash
Thank s
Click to expand...
Click to collapse
Look what I found in the OP
Installation: simply flash the zip from recovery, this will extract and replace the zImage (linux kernel) from your current rom; and leave your existing ramdisk unchanged.
Click to expand...
Click to collapse
But if you are using it on the flexreaper rom , please use the patch from that thread .
It has got this kernel in it but also the tweaked build.prop.
Read OP of this thread regarding de-odexed roms.
civato said:
Look what I found in the OP
Click to expand...
Click to collapse
To be fair I added that line after reading the question and bashing my head..
(anyway nvflash really has no idea what to do with raw zImage files.. as that is all that is in the zip; the boot.img that needs to be flashed to your device also requires a ramdisk.. as indicated now in the op the update script extracts the one currently installed on your tab to generate a full boot.img with the new kernel)
ezterry said:
To be fair I added that line after reading the question and bashing my head..
Click to expand...
Click to collapse
ssssssssst nobody needs to know
I'll try to make a clean patch for A501 support. For now it's a mess =)
vache said:
I'll try to make a clean patch for A501 support. For now it's a mess =)
Click to expand...
Click to collapse
well if you followed my commits this last week or two.. things didn't quite go as cleanly with any of these other patches as I'd hope either.. (what 5+ commits trying to iron out issues in lulzactive.. it really didn't want to play well with interactive in the same kernel build.. and these are all ones I thought worked.. pushed to github..then needed to edit.. if it didn't work before I pushed to gh I'd have modified the commit)
Anyway looking forward to it as I know some people are interested.
I am curious about the lulzactive governor ... it isn't something pulled out of little finger like smartass governor, right (and full of crap, such as "sleep frequency")?
Skrilax_CZ said:
I am curious about the lulzactive governor ... it isn't something pulled out of little finger like smartass governor, right (and full of crap, such as "sleep frequency")?
Click to expand...
Click to collapse
Smarass and lulzactive are based on googles interactive, and really don't have much more overhead just more tuneing.
Sleep frequency is screen off frequency.. (useful if music is running or a background task to not OC, default is the 800mhz level.. lower is prob not wise since it will only be this high if something needs the cpu..) if your tablet is actually asleep its in suspend to ram mode and the cpu is off.. (at least until a wake lock fires or you push the power button) .. prob the most useful state of this is when I have my computer attached by usb preventing the full sleep.. but the power wire is not.
otherwise its a more tuned version of interactive. Allowing tunable quicker ramp ups or slower ramp downs.. I'm just using my own pre-tuned defaults ... edit: it ought to be noted I've also added a super ramp up if the inc_cpu_load is <91% (default value is 75%) and the current cpu utilization is > (100 -((100-inc_cpu_load)/4)) .. (94% with inc_cpu_load=75%) to ramp to max speed and not the ramp up interval of 2 speed steps (as will still happen if the cpu is between 75% and 93%)
Times in state shows a good balance of speeds as needed, and the device is responsive unlike say on demand.
The biggest problem with all the interactive based governors is how they intercept kernel idle .. pm_idle global hook.. replace the function and call the original.. until you start having more modules being enabled and disabled until the pointer is pointing somewhere random and your system crashes.. switch all of that to a register/unregister system based off the one in x86_64
I see, so just some tune.
ezterry said:
if your tablet is actually asleep its in suspend to ram mode and the cpu is off..
Click to expand...
Click to collapse
Yeah exactly ... that's why I said "full of crap, such as sleep frequency".
SoD issues
EZTerry -
I have gotten SoD with nearly all ICS kernels that have been released, both from Acer OTA and with Flexreaper and yours. The only one that I do NOT get any SoD from is the .022 pre-release one that Civato put up on one of the FR builds a while back. Since you seem to be one of the resident experts on kernels for the A500, do you have any idea what differences exist between the .022 build and the current ones, including your OC ones, that could possibly be contributing to the SoD?
For instance, I loaded the latest FlexReaper Extreme Rev 4 (which uses your latest OC kernel) and got peristent SoDs. I flashed back to the non-OC kernel (to get the normal modules back) and then loaded .022 from a flashable copy I had kept. I haven't had any SoD since. No OC, of course, but at least it's stable...
I saw your post about sending you the logs. Still plan to try that, but for now I'm happy with a working tablet.
BakaNeko59 said:
EZTerry -
I have gotten SoD with nearly all ICS kernels that have been released, both from Acer OTA and with Flexreaper and yours. The only one that I do NOT get any SoD from is the .022 pre-release one that Civato put up on one of the FR builds a while back. Since you seem to be one of the resident experts on kernels for the A500, do you have any idea what differences exist between the .022 build and the current ones, including your OC ones, that could possibly be contributing to the SoD?
For instance, I loaded the latest FlexReaper Extreme Rev 4 (which uses your latest OC kernel) and got peristent SoDs. I flashed back to the non-OC kernel (to get the normal modules back) and then loaded .022 from a flashable copy I had kept. I haven't had any SoD since. No OC, of course, but at least it's stable...
I saw your post about sending you the logs. Still plan to try that, but for now I'm happy with a working tablet.
Click to expand...
Click to collapse
But how is ezterry going to know what is differents or how can he help if he doesn't have a logcat.
If ezterry needs to test every rom situation we need to start paying him for giving us better support then we will ever get from acer.
So please provide logcat.
PS:
f is looking real good m8.
will report to you tomorrow .......
civato said:
But how is ezterry going to know what is differents or how can he help if he doesn't have a logcat.
If ezterry needs to test every rom situation we need to start paying him for giving us better support then we will ever get from acer.
So please provide logcat.
PS:
f is looking real good m8.
will report to you tomorrow .......
Click to expand...
Click to collapse
Well, now that I have a stable working build, I can do a backup and then play with the new kernels to get the logcat. I was just so happy to get a working build that I hadn't considered my next step.
I'll play some more when I get home from work since I can't have my tablet in my office.
You wouldn't care to provide a step by step guide of how to get the logcat info would you? I know it requires adb, but not much else. Also, in another post you mentioned getting the last_kmsg (or last_kmesg - I forget). How do we get that?
Thanks. I appreciate the help.
BakaNeko59 said:
EZTerry -
I have gotten SoD with nearly all ICS kernels that have been released
Click to expand...
Click to collapse
SoD is simple to understand in these terms:
Think of your computer or laptop, you request it to suspend to ram or sleep depending on your OS
It does so, turns into the low power state but is otherwise off, and waits for your return.
When you try to turn the computer on it attempts to wake up but then instead crashes.
This is exactly what is happening, android noted nothing was running and suspended the tablet to ram, either was woken up by you pushing power or a timer the operating system set when it went to sleep.
However before fully starting again the system crashed.
In development of the kernel sometimes I run into such problems with bugs in the oc code, or undervolting too far.. but once I call a kernel stable-ish it can usually last the day with many sleep/wake cycles.. can't say there is never an odd sod but its not common.
The question for you the is: what when wrong.. the easiest way to see is the kernel log of the now crashed kernel.. this requires looking at the /proc/last_kmsg file but this is a little tricky if you needed to force power off the tab (the log is stored in ram thus is completely wiped after 8-10 seconds of the tab being powered off.
When it does exits adb pull can grab the file as soon as the android animation begins.
Sent from my Galaxy Nexus using Tapatalk 2
Does this kernel have cifs module built-in? I can't try by myself right now, my a500 is in vacation at acer's repair facility.
ezterry said:
.
The question for you the is: what when wrong.. the easiest way to see is the kernel log of the now crashed kernel.. this requires looking at the /proc/last_kmsg file but this is a little tricky if you needed to force power off the tab (the log is stored in ram thus is completely wiped after 8-10 seconds of the tab being powered off
Click to expand...
Click to collapse
Does the last_kmsg ONLY exist if there's a fault registered or does it get updated regularly during operation? In other words could I create a continuously running script (for debugging only of course) that copies the last_kmsg file to another location before the system actually crashes? Then when it enters sleep the last file copied would have the information you need? Or is there a way to execute a script early enough in the boot process to copy the file during that first 8-10 seconds of power up so that it is easier to acquire?
Or how about a batch file that simply loops the command "adb pull /proc/last_kmsg last_kmsg" continuously on my PC? If the file doesn't exist it doesn't get copied - if it does exist it gets copied, and if the system crashes and doesn't respond, the last file copied should exist either before or after I manually power off and on the tablet. Hmmmm - guess I'll give it a try...
Sorry - just thinking out loud now
Thanks.
Sent from my A500 using Tapatalk 2
so is it as easy as flashing in CWM over any ics rom?
can i flash this with AOKP??
thank you =]
BakaNeko59 said:
Or is there a way to execute a script early enough in the boot process to copy the file during that first 8-10 seconds of power up so that it is easier to acquire?
Click to expand...
Click to collapse
What do you mean the file is there until reboot if the log data is found, so there is no hurry to pull it off the device.
The logdata is only stored in ram.. so if you power off overnight or while microwaving a frozen dinner.. when you turn the tab back on no data will remain.
Ram however will hold its values for a short time without power however, if you needed to force the tablet off by holding power for 5 seconds you have under 10 seconds to power back on the device if you wish to see any of the log. (and you need to leave it off 3 seconds or it will ignore your pressing power.)
Introduction :
Under the request of some friends of mine, I decided after some time of write, to release this script for public testing.
This package of binaries, scripts and libraries, will fix the lags on your Android smartphone or tablet, and make it smoother and faster!
Features and Improvements :
- Full memory management with 5 different configs.
- Zipalign apps in "/system" at every boot, and apps in "/data" every 48 hours.
- CPU governors tweaks and improvements for better performance and battery life.
- Increased SD Card read-ahead cache to 2048 KB to improve SDCard write/read speed.
- Nos entropy seeder generator engine used to reduce lags.
- Ad blocking.
- Battery life improvements.
- SQLite and database optimizing every 48 hours.
- Network TCP tweaks.
- Kernel, VM and sysctl tweaks and improvements.
- File system speedup.
- Build.prop tweaks and improvements.
- Cleans log files and tombstones at every boot.
- Many other tweaks for better performance and battery life!
Requirements :
- Android 2.3.x (Gingerbread) and higher.
- Kernel with init.d support.
- Root.
- ClockworkMod. (4 or higher)
- At least 4 MB of free space in "/system".
How to install :
1. Download the flashable zip.
2. Rebooting into recovery mode.
3. Install Fly-On RAM manager. (optional)
4. Install Signed_Fly-On_Mod_V3.0.zip stock or CM according to your ROM.
5. Reboot and feel the smoothness!
In the package :
+/etc/init.d/ scripts :
-ram_manager: It's a complete memory manager, with 5 different versions.
-02logdelete1: Cleans log files and tombstones at every boot.
-09sdcardspeedfix: Set SDCard readahead speed to 2048 KB.
-darky_zipalign: Zipalign apps in "/system" at every booting.
-zipaligndata: Zipalign apps in "/data" every 48 hours.
-98fly_core: Contains various tweaks and improvements. (3G/VM/sysctl/kernel/battery life tweaks etc.)
-sqlite_optimize: Optimizing database of apps every 48 hours.
-s78sensitive_touchscreen: Improves the sensivity of your touchscreen.
+/system/xbin/ :
-sqlite3
-zipalign
-Openvpn
+/system/lib/
-libncurses.so (Stock version only).
Compatibility :
- This package will work with all android devices that have init.d support!
- Fly-On Mod works with Gingerbread, Ice Cream Sandwich, Jelly Bean, but in Ice Cream Sandwich and Jelly Bean ADJ Values are hard coded into the services.jar or .odex, that's why for Ice Cream Sandwich and Jelly Bean you will need a patched services.jar, you can follow this great guide by zeppelinrox (thanks to him): Click here.
- You can also use Fly-On Mod with V6 SuperCharger. (If you didn't flash the ram_manager config)
- The ram_manager configs are for phones with 512MB RAM. (Lower and higher than that too)
- If you have 1024MB/2048MB RAM use supercharger instead!
Important informations :
About RAM managers :
+ Balanced version, is for people with moderate apps use.
+ Gamers version, is for people playing HD/3D games.
+ Multitasking version, is for people that use a lot of apps at the same time.
+ Hard multitasking version, is for people with huge amount of apps running at the same time. (Very agressive values!)
+ Nexus version, contains values from Google source used in nexus devices.
Note also that:
- Multitasking version have lesser free ram than Balanced/Gamers/Nexus, but this thing doesn't mean they are the best, choose the ram config according to your use!
- Don't use any Task Killer with this Mod!
- Fly-On Mod main package comes with 2 different versions, CM version is for CyanogenMod ROMS and AOSP based ROMS (like AOKP), then stock version is for stock ROMS and custom ROMS based on stock!
- If you have bad battery life the problem is from an app waking your phone from sleep, it's not my script!
- Don't use Fly-On Mod with any other tweaking script as they will conflict!
- If you want to use Fly-On Mod in your ROM or your Mod ask for permissions first and give me credits!
- If you have any question ask me in the thread instead of PMs or I will not reply!
- Read well the thread before posting any newbie questions and do not ask for an already answered question!
Some users feedback :
l0lh4rd said:
The script is great!!!!!!!!!! Really feeling comfortable at 312MHz-156MHz/Smartass V2/noop, which under these settings without the scripts would make me miserable
Click to expand...
Click to collapse
ronnieryan said:
Version 8 has awesome boot time, only 38 seconds for me
Click to expand...
Click to collapse
KnightlyNinja said:
this version is awesome. ram usage is very low 150 mb only.Superb work haha:victory::silly:
Click to expand...
Click to collapse
KnightlyNinja said:
great. this is one of the best tweak available in xda. it improves smoothness , battery and performance. Almost does the work of a good kernel. Hoping to see more improvements in future.
great work sir.
Click to expand...
Click to collapse
sad25kag said:
╔╦╦╦═╦╦╦╗╔╦╦╗
║║║║║║║║║║║║║
║║║║║║║║║╠╬╬╣
╚══╩═╩══╝╚╩╩╝
Working great and faster on MIUI rom.
░░░░░░░░░░░░▄▄
░░░░░░░░░░░█░░█
░░░░░░░░░░░█░░█
░░░░░░░░░░█░░░█
░░░░░░░░░█░░░░█
██████▄▄█░░░░░██████▄
▓▓▓▓▓▓█░░░░░░░░░░░░░░█
▓▓▓▓▓▓█░░░░░░░░░░░░███
▓▓▓▓▓▓█░░░░░░░░░░░░░░█
▓▓▓▓▓▓█░░░░░░░░░░░░███
▓▓▓▓▓▓@░░░░░█
▓▓▓▓▓▓█████░░░░░░░░██
█████▀░░░░▀▀███████
Sent from my GT-S5570 using Tapatalk 2
Click to expand...
Click to collapse
Chemical SidePearl said:
@slaid480
Here is a talking sentence between me and my friend that is watching my phone flying with cm10.1....
Friend: Have you ever heard the definition of INSANITY ???
Me:Yup,it's the new Fly-ON mod by @slaid480.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
pykfree said:
I put this script in PAC 4.2.2 ROM.. working fine.. it give more performance on my phone.. thank's dude
Click to expand...
Click to collapse
tcris45 said:
Ty man for those awesome tweaks
Click to expand...
Click to collapse
golfgtiedition30 said:
Instaled on rom stocklite v8...no problems its working well :thumbup:
Click to expand...
Click to collapse
nizar.nasani said:
well i test it on the last cm10.1 by biel after new flashing today and still for now no problems and works perfect and thnx btw
Click to expand...
Click to collapse
Credits:
-Thanks to Darky for the base zipalign script.
-Special thank to pikachu01, zacharias.maladroit,collin_ph and juwe11!
-Big thank to zeppelinrox and Exit_Only !
-voku1987 and mcbyte_it.
-My Friend Maroc-OS For the big Help!
-Any XDA Member That helped Me out in This Project!
-Google!
If you liked this mod,please rate this thread to 5 stars and press the Thanks button and if it's possible buy a coffee for me,it will help me to work, support and keep this project up to date!
This Thread is reserved for sharing information about Scripts in Android and how they Tweak the Android system through the Linux kernel and what are requirements of Running Scripts correctly!
Main Goal of Scripts:
Well,Scripts Has a lot of Goals,Such as optimizing,improving and in Some Lines we can say,Scripts can:
-Improve Performance and GUI Smoothness
-Improve Battery Life
-Tweak and Optimize the Android engine!
Requirements of using Some Scripts:
Since Android is Based on Linux,there is a possibility to use Linux Scripts to attempt the Goals Listed before in the thread,and like any Tweak you want to Apply there is some requirements you need to Use correctly those Scripts and some of the mportanst are :
-Custom Kernel that support init.d(Custom Kernel=Modified Linux kernel,for example in GALAXY ACE Forums here we have:CF-Root-All CM kernels,etc...)
-Having ClockWorkMod 5 or above to Flash Scripts
-at Least 2 MB free in /system
-Root Access(BusyBox should be included)
Useful Info About Tweaks:
-LMK(LowMemoryKiller):
The LowMemoryKiller is a constant debate between more free RAM and more multitasking capabilities as free RAM (more than 60MB free) is actually wasted RAM.
The LowMemoryKiller is actually a feature in the Android OS for better memory management.
This is an important feature due to the perennial problem of having low free memory causing lagginess and slowness in launching apps. When you have free memory lingering around the number of 40MB or less, the Android OS just lags like hell.
What this would mean is, you would want to tweak the LMK to not have the situation of it having less than 40MB (or even close to that).
The modern Linux machine in the Android ecosystem relies on a mechanism called Low Memory Killer (LMK) to consistently free up RAM. This is due to Android's internal mechanism of caching apps (and never fully exiting them) when you press the back button. This is to enable faster app switching and provide a seamless experience for apps usage model. Android also, by itself will also constantly look for often used apps to cache them for faster app opening. This will happen even before your system fully boots.
Now, when you mention LMK, the most obvious thoughts that come up are minfrees and Out Of Memory (OOM) groupings. Yes, those two are integral parts when it comes to LMK. The issue here is that no one actually mentioned that there are two LMK systems in Android, that being:
- Linux LMK
- Android Dalvik VM LMK
Journaling/Barriers:
This has been a touchy subject here in XDA for most people who debate about it. Most recently,Some Scripts included a way to disable journaling on these partitions:
/system (System is read only, it's safe to remove journaling. However, you will not see speed increase by removing it as you're not writing onto /system 99.99% of the time unless you're using Titanium backup to remove system apps or copying init.d scripts to it)
/cache (Cache can be rebuilt on the fly. Data corruption on it is not game breaking)
/data (All of your data on your phone is here. Removing journaling can risk data corruption. Read more below)
On whether we need journaling or not, I will pose this situation:
Journaling is required to maintain data consistency in events that could lead to data corruption. Data could get corrupted in a number of situations:
- Misbehaving app that constantly writes without syncing/committing data to the disk
- Power loss due to forced reboots or bootloops when data is partially written/committed into disk
Memory Leaks
If you found out that your Android is laggy after sometime and a reboot will make it faster, then you're experiencing memory leaks. "free" is a command to show your currently free memory. It will not necessarily be the same value as your phone's free memory.
Busybox
Well,Busybox is required to perform all of your superuser activities in your android phone. There are some problems associated with this when ROM developers decide to use a certain version of Busybox that are incompatible with the binaries that we use in our phones. When you found out that after changing your kernel/ROM:
- You still have superuser and Titanium Backup still works but, Root Explorer/File Expert can't copy files correctly to the /system after mounting R/W!!
MinFree:
Minfree is part of the Kernel (present on both Gingerbread and Ice Cream Sandwich) and It an Option available in Linux kernel Optimized for Android to Improve MultiTasking and It differs from a Phone to another because of the RAM available in users space.
The Minfree is hopefully adjustable Like the LMK to optimize Multitasking to a lot of options(like:aggressive,gaming,balanced,etc...)
The Minfree Option can be Found as a part of Linux Scripts for better RAM management!
Network Tweaks:
Well,in Linux Scripts for Android you can find some Tweaks that increase the speed of you Network Download/Upload and those with various types of Netwoks Like 3G,Wi-Fi,etc...
Build.Prop Tweaks
Well,those Tweaks can generally be found in Build.prop in /system and they are for various improvements Such as allowing Phone to Sleep better,changing wi-fi scan interval,changing window animation delay,some network Tweaks,possibility to change density,etc...
SD Card Speed Fix:
This is a Tweaks that Has the goal of increasing the read-ahead speed of your SD Card,and that by changing the valories of SD card readahead Like:
-256kb
-512kb
-2048kb
-4096kb
Smoothness Tweaks
Well with the Linux Kernel there is a possibility to add some Tweaks to the Linux scripts and those to optimize the GUI Smoothness and also Lock Home launcher in Memory!!
Credits:
Well,what I can say is that I shared those useful Info after some research and my experience with Linux/Unix,and those some of My main Target that I use to find some of the useful info:
-XDA Forums
-Goolge
Change Log:
Fly-On V0.1:(8/4/2013)
initial release.
Fly-On V0.2:(16/4/2013)
-re-writed and cleaned script.
-New zip-aligning script based on Darky's zip-aligning script.
-Adjusted Values to be adapted to this device hardware.
-Deleted touch sensitivity tweaks(useless).
-Corrected Min-free values.
-Many other minor stuff...
Fly-On V0.3:(17/4/2013)
(If you are coming from an old version,below V0.3 you will need to delete all scripts in your /system/etc/init.d folder)
Now Fly-On Mod is a full package of scripts:
-Replaced the main Fly-On script with 3 scripts to avoid any functionality problem and ensure more stability (S98system_tweak,05LagFixer,09sdcardspeedfix)
-Added some useful build.prop Tweaks(for better performance and battery life)
-Fixed the Low memory killer bug with the new Lagfixer script.
Fly-On V0.4:(17/4/2013)
-New SQlite_optimize script .
-New Script For Network TCP optimizations.
-Adjusted Min-Free Values for better Multitasking!
Fly-On V0.5:(19/4/2013)
-Fixed permissions Via Updater-script to Make sure that scripts are properly working!
-Some cleaning to the S98system_tweak script!
Fly-On V0.6:(20/4/2013)
Delete all old Fly-On scripts before installing V0.6!
this update contains various improvements bugfixes and changes with a full new script:
-Deleted 05Lag_fixer script!
-Deleted S97network_tweaks!
-New 08Fly_engine script with a lot of tweaks and improvements:
+Full Memory management
+Sysctl tweaks
+Kernel and VM tweaks
+File system speedUp
+Ext4 tweaks
+Improved Wifi_Idle for better battery Life!
-Updated zip-aligning script for faster zip-aligning and short boot time!
Fly-On V0.7:(21/4/2013)
-added xbin to make sure that zipalign and fly_engine scripts are working properly!
-Now with two versions:
+Stock version for Stock gingerbread samsung roms and roms based on samsung roms!
+CM version for cyanogenmod7/9/10 Based roms and AOSP GB/ICS/JB roms too!
Fly-On V0.8:(22/4/2013)
-Fixed errors on Fly_engine script.
-Added I/O scheduler tweaks.
Fly-On V0.9:(25/4/2013)
-Fixed sqlite3 bin permissions.
-Removed journalism on EXT4 partition(greatly increase I/O).
-added remountCM_fullext4 script for CM version.
Fly-On V1.0:(27/4/2013)
If you are coming from Fly-On V0.9 there is no need to delete the old scripts!
-deleted fly_engine script(contain a lot of errors,I will be working on rewriting it).
-added a new ram_manager script (Full memory fix and management).
-fixed proper permissions for all scripts.
Fly-On V1.1(29/4/2013)
-Deleted swapon tweak as it's only causing troubles!
-heavily modified updater-script to make the /system/etc/init.d folder clean while installing the Mod!(there is no longer need to delete scripts manually)
Fly-On V1.2(2/5/2013)
-added new script 02logdelete1 to delete logs+tombstones!Huge thank to -CALIBAN666- for the idea and the big help!
-updated the updater-script with more scripts to delete in init.d folder
-Fly-on mod is now more stable than before!
Fly-On V1.3(3/5/2013)
-Fixed sdcard readahead speed(need some testing)
-Under the request of some users the ram_manager script is now separated from the CWM flashable zip and It has it's own CWM package!
-Under the request of some users the ram_manager script is now with two version : one for multitasking and the other one for hard gamers!
-Some cleaning to the 98system_tweaks script(deleted unseful stuff)
Fly-On V1.4:(7/5/2013)
-New Ram manager config(Balanced)for people with moderate apps use!
-Tried to fix deletelog script(I'm not sure need testing)
Fly-On V1.5:(9/5/2013)
-Fully Re-writed Fly_engine script ensuring maximum compatibility with:
+I/O scheduler tweaks(choose noop for maximum compatibility).
+File system speedup.
+Various sysctl tweaks - Kernel, VM, file system!
Fly-On V1.6:(10/5/2013)
-Fixed Bug with 02logdelete1 script,thanks to -CALIBAN666- !
-Renamed 085Fly_engine to Fly_engine to provide any invalid argument!
-Added Openvpn binary.
-Some minor fixes to the Fly_engine script.
Fly-On V1.7:(11/5/2013)
-Updated 02logdelete1 script with new features and improvements thanks to : -CALIBAN666- .
-Added Default.prop which contains Extra fly_engine tweaks!
-Deleted some tweaks from Fly_engine script(the ones that could conflict with 98system_tweak script).
-Fixed proper Fly_engine script permissions through the Updater-script.
Fly-On V1.8(12/5/2013)
-New RAM manager config(Nexus)It's the original Google config!
-Updated sqlite3 binary
-Modified the CWM installation package to make It detect your android version and install the binaries according to it!
Fly-On V1.9:(13/5/2013)
-Modified Fly_engine script with some tweaks added:
+tune2fs feature(Disable journalism).
+Disabled normalize sleeper.
+Deleted I/O specific tweak for noop I/O scheduler.(Feel free to use any scheduler with Fly-On)
Fly-On V2.0:(15/5/2013)
-Added new RAM manager(hard multitasking)!
-Added new script to improve your touchscreen sensitivity !
-Delete 02deletelog1 for know(will be back after fixing bugs on It).
-Now you can install It over adrenaline engine/velocity directly(Edited CWM installation script).
-Fixed a small error in 98system_tweak script.
Fly-On V2.1:(17/5/2013)
-Fully reworked 98system_tweak script with:
+Lesser script size(from 23kb to 19kb).
+ Edited many values for more smoothness and better battery life.
-Some few modifications to the Fly_engine script.
-Added many info to the first post!
Fly-On V2.2:(18/5/2013)
-02logdelete script is back and it's working properly!
-Fixed a small error in 98system_tweak.
-Reduced 98system_tweak size from 19KB to 17KB.
Fly-On V2.3:(20/5/2013)
-Heavily Edited 98system_tweak with:
+New governor Tweaks!
+Edited many values for better performance/battery life.
+Deleted few lines that are causing issue on some phones!
Fly-On V2.4:(23/5/2013)
-Fixed 02logdelete1 script!Now It's working properly thanks to :vampire: !
-New script 98fly_core It's the fusion of 98system_tweak and Fly_engine scripts(to avoid any incompatibility/stability issues).
-Removed "Disable EXT4 journalism" feature as It's incompatible with many devices that runs a system partition other than ETX4.
Fly-On V2.5:(27/5/2013)
-Fully reworked 09sdcardspeedfix script(reduced size from 3Kb to 1Kb).
-Some cleaning to the zipalign script.
Fly-On V2.6:(31/5/2013)
-Cleaned up 98Fly_core script.
-Some misc changes to the sqlite_optimize script.
Fly-On V2.7:(1/6/2013)
-Reverted back to old 09sdcardspeedfix script(compatible with more devices).
-Fixed a small bug with the 98fly_core script.
-Deleted s78sensitive_touchscreen script for now.
Fly-On V2.8:(2/6/2013)
-New zipalign data script used to zipalign apps on /data at every 48H.
-New sqlite optimizing system at every 48H.
-Deleted remountCM_fullext4 from CM version (another step to make Fly-On more universal).
Fly-On V3.0:(5/6/2013)
-fixed a small issue in 98fly_core script.
-Reworked the 02logdelete1 script.
-Reworked zipaligndata script.
-Reverted back to old sqlite optimizing script.
-Added partition remount tweaks for I9300 in a single package.
-Added Fly-on uninstaller for Version 2.4+ .
Fly-On V3.0 RC0:(9/6/2013)
-Added NOS entropy seeder generator engine,big thank to Exit_Only.
-Added hosts file for ad blocking.
-Fixed uninstaller(no more need to mount /system).
Fly-On V3.0 RC1:(18/06/2013)
-Added NOS entropy init.d script with light/moderate/aggressive profiles and sets moderate by defaults thanks again to EXIT_ONLY !
-Added new 99logdelete script to execute 02logdelete1 script properly at boot thanks to Erikeleria!
-Many minor changes.
reserved
Awesome to see you back Slaid! This script ought to be great!
PulseDroid said:
Awesome to see you back Slaid! This script ought to be great!
Click to expand...
Click to collapse
Thank you for the support !
Testing!!!!
I am testing ur scripts on ULTIMATUM ROM by following your instructions and removing all default scripts of /system/etc/init.d
and now its not booting
might be because it has int2ext
so it obviously wont boot
Sent from my S500 using xda app-developers app
Dont use too many script ..just check the init.d folder there are already plenty of scripts in there ...
Sent from my GT-S5830 using xda app-developers app
It works with int2ext?
Compatibility:
Fly-On Mod works with GB/ICS/JB But in ICS/JB Min-free and LowMemoryKiller options are not working,because in ICS/JB android OS set Min-free/LMK values to the default after Booting,so 05Lagfixer script will not work for ICS/JB.
Click to expand...
Click to collapse
Too bad, on JB this script (fly on mod) has very little impact !
denis022 said:
Too bad, on JB this script (fly on mod) has very little impact !
Click to expand...
Click to collapse
If you want total effect on ICS/JB you will need to patch services.jar like mentionned in SuperchargerV6 !
My battery life boosted like hell
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-S5830 using xda premium
Jpbest said:
It works with int2ext?
Click to expand...
Click to collapse
Delete all the others files in ini folder and leave the int2ext then flash this one it will boot for sure. Im testing at the moment and using int2ext also.
Fly-On v0.6 is Up
V0.6 is now Up with various changes and fixes check It out!!!!
slaid480 said:
V0.6 is now Up with various changes and fixes check It out!!!!
Click to expand...
Click to collapse
Oh, man..I think I gonna kill you Just now I reflashed ROM and restore all backups and settings, because when I installed script, then something bad happend to link2sd and now I have to do it again, because I damn want this new version... D'oh!
Thanks for your work man
after flashing new rom
i get
"error in /sdcard/Fly-On_Mod_V0.6_Slaid480.zip
installation aborted"
Hany Ibrahim said:
after flashing new rom
i get
"error in /sdcard/Fly-On_Mod_V0.6_Slaid480.zip
installation aborted"
Click to expand...
Click to collapse
Ok let me check if there is an error in the updater script
Edit:error confirmed and new file uploaded!
Sent from my GT-I9000 using xda premium
slaid480 said:
Ok let me check if there is an error in the updater script
Edit:error confirmed and new file uploaded!
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
working perfect
Hany Ibrahim said:
working perfect
Click to expand...
Click to collapse
That's It thanks for reporting the updater script error!
Khaon presents his kitchen for
Xioami MI2(s) devices
I am not responsible for any damage to your phone.
Read before downloading or posting in the thread:
Proceed with caution if you have no experience.
Introduction
You will find in this thread links to my kernel and a custom CM rom compiled with linaro toolchains and with optimized flags. The rom is shipped with my kernel
This kernel is based on cyanogen's. It ingrates various patches, in my opinion, stock kernel misses. It supports both ext4 and f2fs partitions.
This is a xda debDB project, so feel free to fill in bug reports, feature(s) request and review!
This kernel works on cyanogenmod rom and maybe some other AOSP roms!!
It uses, for now, a simple all kernel repack script. Thus, this repack method is not guaranteed to work at 100%for your custom rom!
Roms reported working so far : Omni Rom, Gummy rom, Paranoid rom, Pacman Rom, CM11 also
The kernel is fully supporting f2fs, if will correctly mount your partition as long as they were formated with f2fs and ext4.
You don't need to edit the rom's script, it will detect itself your partition's filesystem.
For those who don't know what is f2fs
F2FS (Flash-Friendly File System) is a flash file system created by Jaegeuk Kim (Hangul: 김재극) at Samsung for the Linux operating system kernel.[2]
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Click to expand...
Click to collapse
Some benchmarks to point out the performance difference between EXT4 and F2FS
AndroGuide benchmarks : ext4 vs f2fs ( seemes to be using the most recent f2fs)
XDA's benchmark : ext4 vs f2fs
Phoronix's benchs ext4 vs btfrs vs f2fs
Another Phoronix's bench
Click to expand...
Click to collapse
Features :
Compiled with lastest stable linaro - 4.9.2-201409
Compiled with appropriated optmizated flags : O3, etc.
Any kernel script
CPU Governors : onDemand,msm-dcvs,interactive, intelliactive,conservative, performance, userspace
GPU Governors: onDemand,performance,interactive
I/O schedulers : noop, cfq, row,deadline, bfq v7r6(tweaked for nand devices)
CPU hotplug drivers : intelli_plug
intelli_thermal
Support and up to date with upstream f2fs revision branch
Mounts dynamically your partition as long as they were formatted with ext4 or f2fs(not working yet with data f2fs with TDB and sys2)
CPU UC/OCing
GPU OCing up to 500 Mhz
FauxSound 3.6
supports kernel neon mode
kernel image compressed with lz4 algorithm for faster boot
arm optimized crypto algorithms
frandom: A fast random number generator for replacement to urandom
uksm in replacement for ksm
Westwood+ TCP congestion control algorithm
And many more patches(see my github!).
Instructions :
Code:
[B]Kernel:[/B]
1. Reboot to your recovery
2. Install the zip
3. Wipe your caches( /cache & dalvik-cache)
4. reboot & enjoy!
[B]Rom: [COLOR="Red"][FONT="Arial Black"][SIZE="2"]THE ROM IS SHIPPED WITH ORIGINAL CM11 KERNEL[/SIZE][/FONT][/COLOR][/B]
1. Just install the zip! (if you have some partition ith f2fs it will detect itself)
[B]Format cache and data partitions to f2fs:[/B]
You can use @XperianPro 's [URL="http://forum.xda-developers.com/mi-2/development/rom-cyanogenmod-11-modified-edition-t2873261"]philz's recovery[/URL] he built for his modified rom
or use my custom twrp recovery, [B]need to use 2.8.1.0 and onwards[/B]
[SIZE=1].[/SIZE]
Download LinkCredits :
Cyanogenmod and particulary @@m11kkaa for their work on this device
Samsung for f2fs filesystem
@faux123for his work ( intelli_plug, intelli thermal, fauxsound, intelliactive)
@franciscofranco for his gpu governor
@osm0sis for his any kernel script 2.0
Linaro team for their work on the toolchain
XDA:DevDB Information
Khaon's kitchen for the Xiaomi mi2(s), ROM for the Xiaomi Mi 2
Contributors
Khaon, @faux123,@m11kkaa,@franciscofranco
Source Code: https://github.com/Khaon/mi2_kernel/tree/khaon
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Snapshot
Stable Release Date: 2014-10-27
Created 2014-09-27
Last Updated 2015-01-05
XDA:DevDB Information
Khaon's kitchen for the Xiaomi mi2(s), ROM for the Xiaomi Mi 2
Contributors
Khaon, @faux123,@m11kkaa,@franciscofranco
Source Code: https://github.com/Khaon/mi2_kernel/tree/khaon
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Snapshot
Stable Release Date: 2015-01-13
Created 2014-09-27
Last Updated 2015-01-13
Reserved
Changelog :
13/01
khaon said:
apq8064:final voltage for new L2 cache speed frequencies
merged with google's androidd 3.4 branch: squashed the following commits:
Merge remote-tracking branch 'common/android-3.4' into lollipop
ARM: pull in <asm/simd.h> from asm-generic
ARM: be strict about FP exceptions in kernel mode
ARM: move VFP init to an earlier boot stage
crypto: create generic version of ablk_helper
ARM: add support for kernel mode NEON
crypto: sha - Handle unaligned input data in generic sha256 and sha512.
crypto: sha512_generic - set cra_driver_name
crypto: sha512 - Expose generic sha512 routine to be callable from other modules
crypto: create generic version of ablk_helper
defconfig updated:enabled arm crypto
KEYS: Provide signature verification with an asymmetric key
KEYS: Asymmetric public-key algorithm crypto key subtype
KEYS: Implement asymmetric key type
crypto: add crypto_[un]register_shashes for [un]registering multiple shash entries at once
ARM: 8120/1: crypto: sha512: add ARM NEON implementation
ARM: 8119/1: crypto: sha1: add ARM NEON implementation
ARM: 8118/1: crypto: sha1/make use of common SHA-1 structures
crypto: arm-aes - fix encryption of unaligned data
CRYPTO: Fix more AES build errors
ARM: add .gitignore entry for aesbs-core.S
ARM: add support for bit sliced AES using NEON instructions
ARM: move AES typedefs and function prototypes to separate header
ARM: 7837/3: fix Thumb-2 bug in AES assembler code
ARM: 7723/1: crypto: sha1-armv4-large.S: fix SP handling
ARM: 7626/1: arm/crypto: Make asm SHA-1 and AES code Thumb-2 compatible
arm/crypto: Add optimized AES and SHA1 routines
sync with f2fs upstream branch
squashed few commits from CAF:
mm: vmscan: lock page on swap error in pageout
Staging: android: binder: More offset validation
Input: Send events one packet at a time
binder: NULL pointer reference
staging: binder: add vm_fault handler
staging: binder: Change binder mutex to rtmutex.
Click to expand...
Click to collapse
08/11
@khaon said:
rom
compiled with ftree-vectorize extra flags
kernel
cpufreq: create a helper function to get CPU utilization. Picked from @stratosk
aries_defconfig updated
block: zen: fix a bug in add_request, should use rq_is_sync
Adjust zen comments
Some cleanups to zen I/O scheduler
block:zen:I/O scheduler adjustments, reduce fifo_batch to 1
Add Zen I/O scheduler. Similar to SIO, primarily based on no-op and deadline. Intended to be mostly FCFS. Simpler than SIO in many ways, one of them being write requests/read requests have mostly the same priority.
f2fs: updated to upstream branch
added the new mount option fastboot for f2fs partition
This commit add a new mount option : fastboot
If a system wants to reduce the booting time as a top priority, now we can use a mount option, -o fastboot. With this option, f2fs conducts a little bit slow write_checkpoint, but it can avoid the node page reads during the next mount time.
Click to expand...
Click to collapse
As usual the rom is shipped with regular kernel, tdb users will have to flash tdb kernel
Click to expand...
Click to collapse
[/HIDE
[/QUOTE]
24/10
f2fs: remove pointless bit testing in f2fs_delete_entry()
f2fs: revisit inline_data to avoid data races and potential bugs
f2fs: fix possible data corruption in f2fs_write_begin()
f2fs: use current_sit_addr to replace the open code
f2fs: rename f2fs_set/clear_bit to f2fs_test_and_set/clear_bit
f2fs: set raw_super default to NULL to avoid compile warning
f2fs: introduce f2fs_change_bit to simplify the change bit logic
f2fs: remove the redundant function cond_clear_inode_flag
f2fs: remove the seems unneeded argument 'type' from __get_victim
f2fs: avoid returning uninitialized value to userspace from f2fs_trim_fs()
f2fs: declare f2fs_convert_inline_dir as a static function
f2fs: use kmap_atomic instead of kmap
f2fs: reuse make_empty_dir code for inline_dentry
f2fs: introduce f2fs_dentry_ptr structure for code clean-up
f2fs: should not truncate any inline_dentry
f2fs: reuse core function in f2fs_readdir for inline_dentry
f2fs: fix counting inline_data inode numbers
f2fs: add stat info for inline_dentry inodes
f2fs: avoid deadlock on init_inode_metadata
f2fs: fix to wait correct block type
f2fs: reuse find_in_block code for find_in_inline_dir
f2fs: reuse room_for_filename for inline dentry operation
f2fs: update f2fs documentation for inline dir support
f2fs: enable inline dir handling
f2fs: add key function to handle inline dir
f2fs: export dir operations for inline dir
f2fs: add a new mount option for inline dir
f2fs: add infra struct and helper for inline dir
f2fs: avoid infinite loop at cp_error
f2fs: avoid build warning
f2fs: fix to call f2fs_unlock_op
f2fs: avoid to allocate when inline_data was written
f2fs: use highmem for directory pages
f2fs: fix race conditon on truncation with inline_data
f2fs: should truncate any allocated block for inline_data write
f2fs: invalidate inmemory page
f2fs: do not make dirty any inmemory pages
[*]cpufreq:intelliactive:tweaked tunnables
[/LIST]
20/10
Kernel:
mm: Added filesystem dynamic read-ahead (Credits to Chad Gooldman)
block, bfq: add Early Queue Merge (EQM) to BFQ-v7r6 for 3.4.0
block: introduce the BFQ-v7r6 I/O sched for 3.4
12/10:
fixed occasional errors that were preventing to mount correct partitions at boot
09/10
f2fs: updated to revision branch
aries: corrected the default max freq bouncing
intelli thermal : introducting, patched to upstream revision
aries : corrected voltage regulator !!! Voltage < 700 mV weren't correctly applied because of it.
28/09
GPU :
GPU overclocking : initial support
Sound:
Imported fauxSound 3.6[/
27/09:
GPU:KGSL : interactive governor: initial support
Kernel:add support for LZ4-compressed kernel
arm: add support for LZ4-compressed kernel
lib: add support for LZ4-compressed kernel
decompressor: add LZ4 decompressor module
ARM: 7583/1: decompressor: Enable unaligned memory access for v6 and above
frandom: A fast random number generator as a kernel module for Linux.
SELinux: Fix memory leak upon loading policy
FS:f2fs: initial suport with sources from upstream revision
writeback: fix race that cause writeback hungMM:mm: Increase VM_MAX_READAHEAD to 512
mm: ukms : initial support ukms is an improvement upon KSM. Some basic data structures and routines are borrowed from ksm.c
CHROMIUM: mm: Fix calculation of dirtyable memory
Block:block: cgroups, kconfig, build bits for BFQ-v7r5-3.4
block: introduce the BFQ-v7r5 I/O sched for 3.4
Async I/O latency to a ssd greatly increased, 34% gain (Creds: kleikamp)
block: Reserve only one queue tag for sync IO if only 3 tags are available
ext4: speed up truncate/unlink by not using bforget() unless needed
deadline: Allow 0ms deadline latency, increase the read speed
mmc: disable CRC check
crypto:arm/crypto: Add optimized AES and SHA1 routines
crypto: sha1: add ARM NEON implementation
crypto: arm-aes - fix encryption of unaligned data
ARM: add .gitignore entry for aesbs-core.S
ARM: add support for bit sliced AES using NEON instructions
ARM: 7837/3: fix Thumb-2 bug in AES assembler code
ARM: 7723/1: crypto: sha1-armv4-large.S: fix SP handling
ARM: 7626/1: arm/crypto: Make asm SHA-1 and AES code Thumb-2 compatible
ARM: 8118/1: crypto: sha1/make use of common SHA-1 structures
arm : kernel neon mode:ARM: be strict about FP exceptions in kernel modee
ARM: move VFP init to an earlier boot stage
ARM: add support for kernel mode NEON
ARM:intelli_plug : initial import
Intelli_plug: kernel sched/core: add per cpu nr_running stats
intelli_plug: refactor stats calculation code to be less intrusive
Voltage Control: initial voltage control for MSM S4-Pro SOC
ARM : vfp : using hard float now
Intelliactive : iniatial introduction from faux123's mako repo
Reserved
Great news! Will test definitely.Did i miss the download button or isn't released yet?
T3sla said:
Great news! Will test definitely.Did i miss the download button or is isn't released yet?
Click to expand...
Click to collapse
Ahah, my bad, by misstake it seems I deleted the link. It is fixed!
http://forum.xda-developers.com/devdb/project/dl/?id=8790
Look on top of the trhead
Only aosp or cm too?
wifi and bluethoot dont work in Moonlight Nexus 5 experience rom.
http://forum.xda-developers.com/mi-2/orig-development/rom-nexus-5-experience-rom-m2-2s-t2881568
I have also screen tearing. Any plans on anykernel version?
paul89rulez said:
wifi and bluethoot dont work in Moonlight Nexus 5 experience rom.
http://forum.xda-developers.com/mi-2/orig-development/rom-nexus-5-experience-rom-m2-2s-t2881568
I have also screen tearing. Any plans on anykernel version?
Click to expand...
Click to collapse
kekkojoker90 said:
Only aosp or cm too?
Click to expand...
Click to collapse
At the moment I am running cyanogenmod rom and everything is working. All other issues on other roms are related most likely to the ramdisk. A first try is to repack. Otherwhise I can port the kernel for any rom.
i think that its better to do an universal version (anykernel metod) for you (porting your kernel to all roms is difficult). Btw do as you wish, i m ready for test any Moonlight\Mokee version
paul89rulez said:
i think that its better to do an universal version (anykernel metod) for you (porting your kernel to all roms is difficult). Btw do as you wish, i m ready for test any Moonlight\Mokee version
Click to expand...
Click to collapse
Well, I don't know what exactly is any kernel, I just wanted at first to share my own kernel for cyanogenmod since that's what I am running. However, it is with pleasure I would do an universal kernel just I need to look into any kernel :silly:. any ressources are welcome!
Op was updated with features to come and warn users that it is fully working only on cyanogen
here you go
AnyKernel
http://forum.xda-developers.com/showthread.php?t=1906391
Koush sources:
https://github.com/koush/AnyKernel
paul89rulez said:
here you go
AnyKernel
http://forum.xda-developers.com/showthread.php?t=1906391
Koush sources:
https://github.com/koush/AnyKernel
Click to expand...
Click to collapse
Yeah I was just beeing busy to implement that. In fact it is just a repack of the the current rom ramdisk. However, like I said above, it is the first try, but it ain't 100% of the time working. Stay tunned then about to release a new updater-script zip
updater-script uptated to use khoush's any kernel repack
Seg fault on unpackbootimg
Khaon said:
Yeah I was just beeing busy to implement that. In fact it is just a repack of the the current rom ramdisk. However, like I said above, it is the first try, but it ain't 100% of the time working. Stay tunned then about to release a new updater-script zip
Click to expand...
Click to collapse
Problem with AOSB too.Screen tearing, wifi, bluetooth don't work, i guess all AOSP based roms will have the same problem.Waiting for the new one.Just a friendly request, it would be nice if you could add charge limiter, if it's possible of course.
T3sla said:
Problem with AOSB too.Screen tearing, wifi, bluetooth don't work, i guess all AOSP based roms will have the same problem.Waiting for the new one.Just a friendly request, it would be nice if you could add charge limiter, if it's possible of course.
Click to expand...
Click to collapse
What do you mean exactly? A sysfs interface to sec the max amperage?
Testing it with project lungo. Very good khaon!
paul89rulez said:
Testing it with project lungo. Very good khaon!
Click to expand...
Click to collapse
Everything working on lungo?
Btw, this is my result after a fresh restart and no ART neither f2fs.
Is this any good? Honestly doesn't really know.
Khaon said:
What do you mean exactly? A sysfs interface to sec the max amperage?
Click to expand...
Click to collapse
I don't know how exactly is implemented but i mean limit the charge level, e.g. stop charging when it hits 90%.The point behind this feature is that batteries last longer if you don't charge them to full capacity.It's better to charge them at lower level and more frequently instead of less full charges.A lot of laptops have this feature, also a relevant link i found.There is a very analytical post at batteryuniversity.com about the subject, i can search if you wanna read.