[i9300][2014/JUN/10][AOSP] Yank555.lu kernel v1.7a-beta3

Which toolchain do you prefer ?

Poll ended at 16 May 2013, 20:05

Toolchain A - Google 4.4.3
26
21%
Toolchain B - Google 4.7
63
52%
Toolchain C - Linaro 4.7 2013.04
33
27%
 
Total votes : 122

[i9300][2014/JUN/10][AOSP] Yank555.lu kernel v1.7a-beta3

Postby yank555 » 12 Mar 2013, 21:41

Anoucement :

IMPORTANT: As notified in due time, my CM10.2 kernels do NOT support proprietary Custom Rom frameworks anymore. So if your Custom Rom did not implement the generic framework class framework-2.jar but his own naming convention, you may get a boot loop. Do not whine about this here but advise your Custom ROM dev to fix this. I will not change this ever again.
The most prominent custom kernels for CM will follow the same approach (aligned between AndiP, Googy, Teufel, Psndna, Temasek and me).


Before proceding, please consider learning from Garfield :

Image
(Thanx to MuertoKo for this educational image)

I have spend numerous hours coding, merging ... and writing this OP, so please have the decency to at least read it before asking questions.


Disclaimer

FIRST OF ALL, do a Nandroid backup before flashing !


By flashing this kernel you agree to do this at your very own risk ! I will and can not be
held responsible for whatever may happen as a consequence of using this kernel / script generator.
This software is made available to you as is, no waranties can be given.

If you do not agree to these terms, then please use your browser's back key.


ROM Compatibility

This kernel is based on CyanogenMod CM10 kernel sources, so it is intended only to be used on CM10 based ROMs.

The kernel has been tested on the following Android 4.1.x AOSP/CM ROMs :
  • [url="http://forum.xda-developers.com/showthread.php?t=1745003"]Paranoid Android[/url] 2.54 by gokussjx
  • Helly_Bean (CM10) / Hellybean 20130114
  • CM10 & CM10.1
  • Slimbeam ROMs / 4.2.1 RC1 / RC2.2
  • Temasek's nightly V99 / v56
  • AOKP
  • Jelly BAM
  • Rootbox (incl. 4.2.2)
  • Baked blackbean 6
  • PACman ROM
  • LiquidSmooth-RC9
  • temasek V35 ... V64
  • cyanway beta 3
  • Resurrection Remix 3.1.4
  • ReVolt JB I9300
  • kodec II
  • rootbox rom
  • ReVolt 3.2 (4.2.1 AOKP)
  • N.E.A.R rom 1.2x
  • carbon rom 1.3 based on 4.2.2
  • Slim Rom 4.2.1
  • Carbon 1.5beta, 1.6
  • Omega v5.0 ◄●►AOKP JB Build 5
  • ... (you tell me ;))

The kernel has been tested on the following Android 4.2.x AOSP/CM ROMs :
  • [url="http://forum.xda-developers.com/showthread.php?t=1745003"]Paranoid Android[/url] all 4.2.2 by gokussjx
  • SuperNexus 2.0
  • CM10.1 Nightly
  • SlimBeam 4.2.2
  • BeanStalk 4.2.2
  • JellyBam 7.5.0
  • SentinelRom
  • ... (you tell me ;))

It won't work on Samsung JB (nor ICS) ROMs...


What To Expect Using This Kernel

First of all, the main reason this kernel even exists is because I make it for my own personal use. As some users started using it as well (link in my signature), which was absolutely fine by me, I decided to start a thread for it rather than reply to PMs, as I added one or the other feature upon request by a user even if I don't use that feature personnally (e.g. zram support).

Main objectives for this kernel :

  1. be as stable as possible to be usable as a perfect daily kernel (conservative approach)

  2. give a good battery life while being snappy

  3. give users an easy and safe way to customize settings

  4. be and stay as close to stock CM10 as possible

  5. allow only for moderate CPU OC (up to 1.6GHz)

  6. include some standard Linux features missing in stock kernel (e.g. swap support)

  7. include interesting commits by other devs (giving proper credit, of course !)

  8. updated to kernel.org Linux

What NOT To Expect Using This Kernel

  • experimental modifications

  • cutting edge development

  • thrive to be the first, fastest, best, most advanced ... kernel ever !

    I just suspect there is a public for genuine slightly modified kernels that are a no fuzz to use, and which are aimed towards "standard power users" as opposed to "hungry beta testers and debuggers" (been there, done that, fun time in my HD2 times helping as I could on Dorimanx kernel). But I need my S3 on a daily bases, privately and for work, so my S3 just has to work.

  • your S3 being able to walk your dog, fry your eggs or even toast your bread ... :D

Credits & Thanx

This is the most important bit of them all, a small place to pay tribute to all those who have helped me making this kernel :

  • Faux123

    Thanx for helping me get started, out of an almost 20 years break on Linux kernel compiling (at the time it was Linux 0.47 if I remember well), helping me build my compile box(es), upfront getting my first Android kernel compiled, making mods, merging sources, using github in general ... and always taking the time to explain and help out !

  • Corrsea

    Huge thanx for thorough testing and usefull advice, since my first steps on Android, at the time we were both running Tytung's Nexus HD2 on our initially WinMo device, chasing any possible bugs there were to iron out.

  • MuertoKo

    Thanx for pushing me here and there to go further with my kernels, and for testing them on your daily and reporting back.

  • uberto.costanzo & F3nr1s

    Thanx for your support, for testing the kernel and reporting back.

  • Amarullz

    And last but nowhere least, huge thanx to Amarullz for giving us such a great tool, without Aroma Installer flashing kernels / ROMs would still be stone-age kind of voodoo magic, now it has become a proper user experince, giving everybody an easy way to customize whatever is being flashed !

------------------------------------

Kernel Cleanup Script, to be flashed when going to a different kernel :

Kernel configuration & log files removal (MD5 313529df6427e5f560b1001748f347b5)
Nexus 5 (aka. Hammerhead) 32Gb
Note 3 SM-N9005 32Gb Proudly eFused
SGS3 GT-I9300 32Gb
HTC Sensation XE
HTC HD2
TF300TG 32Gb

Image
Credits FAdrums !
User avatar
yank555
-----------
 
Posts: 3471
Joined: 11 Mar 2013, 20:51
Has thanked: 922 times
Been thanked: 4589 times

Changelog

Postby yank555 » 12 Mar 2013, 21:51

Changelog And Download Links

===========================================================
I ask one simple and single thing in return for you to use my work for free,

DO NOT POST MIRRORS OF MY KERNELS ANYWHERE !

You can post as many links to this thread as you want, but no uploading of
my work on file sharing servers or attaching them to posts on other
forums !You can post as many links to this thread as you want, but no uploading of
my work on file sharing servers or attaching them to posts on other
forums !


Only exception : Discussing my work or sharing Links to here on Android-Hilfe.de
is hereby expressly unwanted ! They have no respect for devs and I don't want
any contribution from me on their forum, neither directly nor indirectly !


Thanx.
=======================================================


Lastest beta kernels :

  • OMNI v1.7a-beta3 can be found here.
  • OMNI v1.7a-beta1 can be found here.

Changelog OMNI v1.7 :

  • updated zzmoove to v0.8
  • updated zzmoove v0.8 yank battery and battery extreme profiles
  • updated ramfs to OMNI nightly 20140321
  • updated boeffla-sound to v1.6.5 (AndiP71)

  • This kernel works on OMNI and SlimKat and Temasek (V22 or newer).


Changelog CM11 v1.7 :

  • updated zzmoove to v0.8
  • updated zzmoove v0.8 yank battery and battery extreme profiles
  • updated ramfs to CM11 nightly 20140322
  • updated to latest CM11 kernel sources

  • This kernel works on stock CM11 only.


Changelog CM11 v1.6j :

  • timekeeping: Fix time moving backwards (Ajay Nandakumar)
  • binfmt_elf.c: use get_random_int() to fix entropy depleting (Jeff Liu)
  • added CM's alternative vibrator config path in sysfs (I've just had enough with that crap, now both paths are available at the same time, Yank555.lu)
  • updated fs namespace (so cifs should work again, tomkasick)
  • updated zzmoove to 0.8-beta9 : (D)ynamic (S)ampling (R)ate / scaling up block threshold and cycles / inbuilt profiles (ZaneZam)
  • ramfs : updated to CM11 nightly 20140205
  • fixed incompatibility with newer CWM recoveries

  • This kernel works on stock CM11 only.


Changelog OMNI v1.6j :

  • timekeeping: Fix time moving backwards (Ajay Nandakumar)
  • binfmt_elf.c: use get_random_int() to fix entropy depleting (Jeff Liu)
  • updated zzmoove to 0.8-beta9 : (D)ynamic (S)ampling (R)ate / scaling up block threshold and cycles / inbuilt profiles (ZaneZam)
  • ramfs : updated to OMNI nightly 20140205
  • fixed incompatibility with newer CWM recoveries
  • added CM's alternative vibrator config path in sysfs (I've just had enough with that crap, now both paths are available at the same time, Yank555.lu)
  • updated fs namespace (so cifs should work again, tomkasick)
  • reverted black crush fix (AndiP71)
  • reverted sharpness fix (disabled by default, AndiP71)
  • added mdnie hijack controls for color calibration, black crush and sharpness (Yank555.lu)

    Code: Select all
     * /sys/class/mdnie/mdnie/hijack : 0 = disbaled / 1 = enabled
     *
     *    Enable / Disable hijacking of mdnie settings (default = disabled)
     *
     * /sys/class/mdnie/mdnie/sharpen : 0 = disbaled / 1 = enabled
     *
     *    Enable / Disable screen sharpness (default = enabled, stock Samsung Update 12+)
     *
     * /sys/class/mdnie/mdnie/black : -128 to +128
     *
     *    Global black level, will shift black RGB setting by this value (default = 0)
     *
     *    NB: Effectively applied values for black will never be below 0 nor above 255 !
     *
     *        So there is no use setting Black RGB to (0,0,0) and this to -10, the result
     *        will still be (0,0,0).
     *
     * /sys/class/mdnie/mdnie/{color}_red   : 0 to 255
     * /sys/class/mdnie/mdnie/{color}_green : 0 to 255
     * /sys/class/mdnie/mdnie/{color}_blue  : 0 to 255
     *
     *    Allows to set the RGB values for the base colors :
     *
     *      - red
     *      - green
     *      - blue
     *      - cyan
     *      - magenta
     *      - yellow
     *      - black
     *      - white
     *
     *    (default = Samsung's natural mode)


  • This kernel works on OMNI and SlimKat and Temasek (V22 or newer).


Changelog CM11 v1.6i :

  • updated to Samsung Update 13 sources
  • fixed battery temp not working (showing 30.0 all the time) -> This is a long fixed bug, but still present in stock CM (ramfs), thank Temasek for fixing it !
  • Sharpness and black crush fix not usable as they require newer Samsung mdnie, which CM11 hasn't included yet, will be added once CM moves forward.

  • This kernel works on stock CM11 only.


Changelog OMNI 4.4.2 v1.6i :

  • updated to Samsung Update 13 sources
  • added black crush fix (AndiP71)
  • added sharpness fix (disabled by default, AndiP71)
  • fixed battery temp not working (showing 30.0 all the time)
  • Aroma script generator : added sharpness fix option

  • This kernel works on OMNI and SlimKat and Temasek (V22 or newer).


Changelog CM11 v1.6h :

  • updated ramfs to CM11 20131220 nightly
  • updated ramfs : set SELinux to permissive
  • updated ramfs : updated mini busybox to support mounting cifs and priority for swap
  • updated mali r3p2 drivers from Update 12 source drop (GPU OC is lost for now !)
  • updated AROMA to 2.70RC2
  • Aroma script generator : implement zram using 4 devices
  • updated ramfs : removed symlinks for (u)mount from mini mini busybox to fix /system not being remounted r/w (v1.6h+)

  • This kernel works on stock CM11 only.


Changelog OMNI 4.4.2 v1.6h++ :

  • fixed virbration strength setting on Temasek's unofficial CM11

  • This kernel works on OMNI and SlimKat and Temasek (V22 or newer).


Changelog OMNI 4.4.2 v1.6h+ :

  • fixed root not working on SlimKat

  • This kernel works on OMNI and SlimKat and Temasek (V22 or newer).


Changelog OMNI 4.4.2 v1.6h :

  • ramfs : set SELinux to permissive
  • ramfs : updated mini busybox to support mounting cifs and priority for swap
  • Aroma script generator : implement zram using 4 devices

  • This kernel works on OMNI and SlimKat and Temasek (V22 or newer).


Changelog OMNI 4.4.2 v1.6g (compared to CM10.2 v1.6g) :

  • updated mali r3p2 drivers from Update 12 source drop (GPU OC is lost for now !)
  • removed GPU OC settings from Aroma and script generator
  • updated AROMA to 2.70RC2
  • updated OMNI kernel : s3cfb: i9300 update12
  • updated OMNI kernel : fix muted headset mic after button press
  • ramfs : updated to OMNI nightly 20131214
  • ramfs : added superuser daemon support (fixed root not working on SlimKat, v1.6+)
  • ramfs : fixed a derp I made when I added superuser daemon support (v1.6++)

  • This kernel works on OMNI and SlimKat and Temasek (V22 or newer).


Changelog CM10.2 v1.6g :

  • updated zzmoove to 0.8beta : (D)ynamic (S)ampling (R)ate / scaling up block threshold and cycles / inbuilt profiles (ZaneZam)
  • made h/w keys backlight on screen touch compatible with older CM philisophy, kernel side handling, mixed with bits of ROM side handling because of SlimBean 4.3 build 1.4 (Yank555.lu)
  • added zen I/O scheduler (through AndiP71)
  • added compatibility for one additional generic framework jar ("framework-2.jar")
  • added SPEEDUP_KEYRESUME from dsc-team kernel (suggested by _2bad4u_)
  • added CPU-idle and sched_mc_power_savings options in Aroma (requested by janres155)
  • compiler flags updated to generate Position Independent Code
  • updated to kernel.org Linux 3.0.101 [EOL]
  • updated ramfs to latest CM10.2 (20131022)

    IMPORTANT: As notified in due time, my CM10.2 kernels do NOT support proprietary Custom Rom frameworks anymore. So if your Custom Rom did not implement the generic framework class framework-2.jar but his own naming convention, you may get a boot loop. Do not whine about this here but advise your Custom ROM dev to fix this. I will not change this ever again.
    The most prominent custom kernels for CM will follow the same approach (aligned between AndiP, Googy, Teufel, Psndna, Temasek and me).

  • Yank555.lu-CM10.2-v1.6g.zip
    (MD5 80dd04ef7344a935b6fb388b825f1652)
    (9.82 MiB) Downloaded 2003 times

  • Support for CM10 and CM10.1 has been dropped at this point, this will be the last CM10.2 kernel as well.

Changelog CM10.1 v1.6f++ :

  • added support for CM10.1 based MIUI ROMs (thanx to AndiP71 for the info)

Changelog CM10.1 / CM10.2 v1.6f+ :

  • added frandom kernel module (through AndiP71)
  • added frandom kernel module load on boot in Aroma
  • updated : GPU clock and voltage control - update voltage table on ASV detection on boot (AndiP71)
  • updated CM10.x kernel : Revert "wakelock: use single threaded workqueueus" (Codeworkx)
  • build script : strip debugging symbols from kernel objects


Changelog CM10.1 / CM10.2 v1.6f :

  • updated : GPU clock and voltage control - sysfs voltage interface only accepts multiples of 2500microVolt, legacy interface unchanged (Yank555.lu)
  • added GPU threshold settings in Aroma
  • added native Samsung exFAT support (OSRC) (1)
  • added support for 4 concurrent zram devices (2)
  • made h/w keys backlight on screen touch compatible with newer CM philisophy, ROM side handling (Yank555.lu) (3)
  • added ROM / kernel side handling of h/w keys backlight in Aroma (3) (4)
  • boeffla-sound 1.6.2 : change detection to Wolfson logic (AndiP71)
  • boeffla-sound 1.6.2a : reworked the detection to fix issues on CM (Yank555.lu)
  • boeffla-sound 1.6.2b : reworked the way detection changes are applied (Yank555.lu)
  • boeffla-sound 1.6.2c : removed a check in fm radio detection that shouldn't be necessary anymore (Yank555.lu)
  • boeffla-sound 1.6.3 : added change detection specifics for note devices (AndiP71)
  • boeffla-sound 1.6.4 : code cleanup mainly (AndiP71)
  • updated zzmoove to 0.7d : various fixes and optimizations (ZaneZam)
  • updated zzmoove yank battery profile
  • updated zzmoove yank extreme battery profile
  • updated CM10.x kernel : cypress: report led status via sysfs (Codeworkx)
  • updated CM10.2 kernel : smdk4412: max77693_haptic: move sysfs node (Codeworkx / Jiangyi) (3)
  • updated CM10.2 kernel : netfilter: qtaguid: rate limit some of the printks (JP Abgrall) (3)
  • updated CM10.2 kernel : netfilter: xt_qtaguid: Allow tracking loopback (JP Abgrall) (3)
  • updated CM10.2 kernel : netfilter: xt_qtaguid: extend iface stat to report protocols (JP Abgrall) (3)
  • updated CM10.2 kernel : netfilter: xt_qtaguid: remove AID_* dependency for access control (JP Abgrall) (3)
  • updated ramfs to latest CM10.2 (20130911) (3)
  • updated "extreme" GPU clock profile
  • updated to kernel.org Linux 3.0.96

    (1) ROM side support needed. Also read this warning and don't come crying you lost your data as I'll just repoint you there !

    (2) set zram to disabled in Aroma and use an init.d script to use up to 4 concurrent zram swap devices

    (3) only applicable to CM10.2

    (4) Please read this if you are having issues with the h/w keys backlight !

  • Yank555.lu-CM10.1-v1.6f.zip
    (MD5 33c2dd84585a49bcfdec143d8342bb12)
    (18.34 MiB) Downloaded 301 times

  • Yank555.lu-CM10.2-v1.6f.zip
    (MD5 ecf66b22639b669bc89b5e336d26903a)
    (19.88 MiB) Downloaded 811 times

  • Android 4.1.x support most likely dropped, I think it's time to move on, we now have 4.3 already

Changelog CM10 / CM10.1 / CM10.2 v1.6e :

  • added : Hardwarekeys light on screen touch switchable (Yank555.lu)
  • added : GPU clock and voltage control (via temasek) (1) (2)
  • fixed : GPU clock and voltage control - higest freq. step voltage not being initialized (Yank555.lu) (2)
  • updated : GPU clock and voltage control - full freq. range voltage table added, automatic voltage update for all freq. steps (Yank555.lu) (2)
  • updated : GPU clock and voltage control - revamped the whole interface, keeping the old legacy interface in place (Yank555.lu) (2)
  • updated : GPU clock and voltage control - added a gpu_voltage_delta to be applied when voltage table is reset, allows to globally over-/undervolt (Yank555.lu) (2)
  • Forced Fast Charge v1.4a : return "invalid argument" when writing a wrong value in sysfs tunables
  • Touch Wake v1.1a : fixed proxy sensor detection (Yank555.lu)
  • updated zzmoove to 0.6a : autodetect CPU freq. table sorting, not for exynos, but for other platforms (Yank555.lu)
  • updated zzmoove to 0.6b : hotplugging revisited to reduce plugging (ZaneZam)
  • updated zzmoove to 0.7 : hotplugging freq. thresholds introduced (Yank555.lu)
  • updated zzmoove to 0.7 : hotplugging disable in sleep (ZaneZam)
  • zRam : changed compression fron snappy v3 to lz4 (Yank555.lu)
  • updated zzmoove yank battery profile
  • updated zzmoove yank extreme battery profile
  • wifi : reduced wakelock times (DerTeufel)
  • ramfs : included CM's no in-call sound workaround in ramfs, will work in any case, even without ROM support (Yank555.lu)
  • updated to Samsung Update 11 sources
  • updated to kernel.org Linux 3.0.89
  • activated unaligned-access in compiler flags
  • added SELinux support (3)
  • updated to latest CM10.2 kernel : max8997: move sysfs node for pwm level (Codeworkx) (3)

    (1) no support will be given on issues if GPU is not set to stock when this happens ... I mean it ... really !!

    (2) only applicable to CM10.1 / CM10.2

    (3) only applicable to CM10.2


Changelog CM10(.1) v1.6d :

  • updated zzmoove to 0.6 :
    • removed fixed scaling lookup tables and use the system frequency table instead changed scaling logic accordingly for this modification (thx and credits to Yank555)
    • reduced new hotplug logic loop to a minimum
    • again try to fix stuck issues by using seperate hotplug functions out of dbs_check_cpu (credits to ktoonesz)
    • added support for 2 and 8 core systems and added automatic detection of cores were it is needed (for setting the different core modes you can use the macro 'MAX_CORES'. possible values are: 2,4 or 8, default are 4 cores) reduced core threshold defaults to only one up/down default and use an array to hold all threshold values
    • fixed some mistakes in 'frequency tuneables' (Yank555):
      • stop looping once the frequency has been found
      • return invalid error if new frequency is not found in the frequency table
  • Touch wake : added infinite mode (AndiP71)
  • Touch Wake v1.1 : hopefully fixed all occasional misbehaving on powerkey switch off, on "when in call" and slight code cleanup and optimising (Yank555.lu)
  • Forced Fast Charge v1.4 : added separate setting for wireless charger
  • Reverted : staging: android: lowmemorykiller: Don't count reserved free memory (Arve Hjonnevag)
  • updated CM10.1 kernel : added support for USB CD-Rom drives (jpeg729)
  • updated CM10.1 kernel : user configurable vibration intensity "/sys/vibrator/pwm_val (0-100)" (sbrissen)
  • updated ramfs to CM10.1 latest nightly (20130703) <= only for CM10.1 kernel !
  • updated zzmoove yank battery profile
  • extended touchboost : added user selectable frequency (Yank555.lu)
  • updated to kernel.org Linux 3.0.86


Changelog CM10(.1) v1.6c :

  • updated zzmoove to 0.5.1b
    • Display frequency control (switch to 40Hz when load is low)
    • Fastscaling revamped (configurable in number of levels to skip, up and down !)
    • Early demand
    • Sampling down reintroduced
    • Sampling down momentum
    • now really fixed the governor switching issues! (gotcha bitch! *g*)
    • again some changes in scaling logic from Yank555 (thx and credits)
    • simplified some tuneables by using already available stuff instead of using redundant code (thx Yank555)
    • reduced/optimised hotplug logic and preperation for automatic detection of available cores (maybe this fixes also the scaling/core stuck problems)
  • extended fast scaling options for zzmoove in Aroma
  • added early suspend options for zzmoove in Aroma
  • updated zram (Jiang Liu through faux123)
  • added Touch Wake (Ezekeel through AndiP)
  • fixed a bug in Aroma (dynamic fsync was always turned on)
  • removed all Aroma profiles except 'Full stock' and 'Yank'
  • added option in Aroma to just flash the kernel without changing settings (I highly recommend to not use this when changing kernel version, use at your very own risk !!!)
  • updated yank battery profile in Aroma for zzmoove 0.5
  • added a new yank battery 'extreme' profile in Aroma with updated tunable settings for zzmoove 0.5
  • updated ZaneZam's profiles to fit zzmoove v0.5
  • updated to kernel.org Linux 3.0.83


Changelog CM10(.1) v1.6b :

  • updated to kernel.org Linux 3.0.81
  • update ramfs to latest CM10.1 nightly
  • updated ROW scheduler (Tatyana Brokhman through faux123)
  • updated Snappy compression (used in zRam, through googyanas)
  • added block: Add support for reinsert a dispatched req (Tatyana Brokhman through faux123)
  • added block: Add API for urgent request handling (Tatyana Brokhman through faux123)


Changelog CM10(.1) v1.6a :

  • updated to kernel.org Linux 3.0.80
  • updated SDS fix to v2 (SDS v2 fix extracted from Samsung Update 8 source drop by Yank555.lu, was not yet included by CM to their kernel)
  • updated all Samsung changes up to Update 10 (only Update 8 were missing so far btw.)
  • CM10.1 kernel update : cm3663: fix initial proximity sensor state (codeworkx)
  • CM10.1 kernel update : makefile: mach-exynos: Separate 4x10 and 4x12 objects (sakindia123)
  • updated dynamic fsync: add reboot notifier to force flush outstanding data (faux123)
  • updated dynamic fsync: add kernel panic notifier to force flush outstanding data (faux123)
  • updated CPU hotplug, writeback: Don't call writeback_set_ratelimit() too often during hotplug (Srivatsa S. Bhat)
  • updated cpufreq: Resolve CPUFREQ_NOTIFY issue (Archana Sathyakumar)
  • updated cpufreq: Retain only online cpus in managed_policy->cpus (Srivatsa Vaddagiri)
  • updated zram (Jerome Marchand, noahdesu, nitingupta910, Sergey Datsevich through faux123)

  • Yank555.lu-CM10.1-v1.6a.zip
    (MD5 3db208a3f0244695dca9a9c592a29c9d)
    (18.25 MiB) Downloaded 819 times

  • Kernel for Android 4.1.x skipped, please use v1.6b above (contains also all changes listed for 1.6a)

Changelog CM10(.1) v1.6 :

  • updated to kernel.org Linux 3.0.78
  • increased kernel default entropy settings (64/128 -> 256/512)
  • updated dynamic fsync (Faux123)
  • updated mutex (Waiman Long)
  • added glibc versions of lib/memcopy & lib/string (Miao Xie)
  • updated LZO (Markus F.X.J. Oberhumer)
  • added many ARM specific optimizations (Ashwin Chaugule, David McCullough, Dave Martin, Rob Herring, Nicolas Pitre, Sumit Bhattacharya, Brent DeGraaf, Will Deacon)
  • switched the protection of percpu_counter list to spinlock (Al Viro)
  • updated hrtimer (Michael Bohan)
  • improved asynchronous I/O latency to a solid-state disk (Dave Kleikamp)
  • switched to Joe's RCU optimized for small multi-core systems (Joe Korty)
  • updated R/W semaphores (Michel Lespinasse, Thomas Gleixner)
  • added lib/kstrtox: common code between kstrto*() and simple_strto*() functions (Alexey Dobriyan)
  • added procfs: add num_to_str() to speed up /proc/stat (KAMEZAWA Hiroyuki)
  • added vsprintf: optimize decimal conversion (again) (Michal Nazarewicz)
  • added timer: optimize apply_slack() (Felix Fietkau)
  • added lib: Sparc's strncpy_from_user is generic enough, move under lib/ (David S. Miller)
  • added word-at-a-time: make the interfaces truly generic (Linus Torvalds)
  • added lib: add generic strnlen_user() function (Linus Torvalds)
  • added lib: Fix generic strnlen_user for 32-bit big-endian machines (Paul Mackerras)
  • added kernel: Move REPEAT_BYTE definition into linux/kernel.h (David S. Miller)
  • added mm: implement WasActive page flag (for improving cleancache) (Dan Magenheimer)
  • added SCHEDULER: Autogroup patch group by current user android UID instead of task ID (godmachine81)
  • added scheduler: compute time-average nr_running per run-queue (Diwakar Tundlam)
  • added proc: enhance time-average nr_running stats (Alex Frid)
  • added scheduler: Re-compute time-average nr_running on read (Alex Frid)
  • added rq_stats: add run queue statistic collection to kernel tick scheduler (Faux123)
  • added Input: Send events one packet at a time (Ping Cheng)
  • Big thanks to Faux123 for most of the above, which I found in various of his repos !

  • Please consider using zzmoove optimized when using my settings, I changed it to yank-battery in CM10.1 kernel only, but I reverted back to optimized myself (and all 4 other kernels), it's just snappier.
    Yank555.lu-CM10.1-v1.6.zip
    (MD5 ec099c32638b925c90ac7f2f29603ce2)
    (18.25 MiB) Downloaded 1771 times

  • Yank555.lu-Android-4.1.x-v1.6.zip
    (MD5 a03fe34c8a4fd2436bcf17dfb29781d6)
    (18.23 MiB) Downloaded 158 times

Changelog CM10(.1) v1.5m :

  • compiled with Google's 4.7 toolchain (so far my prefered, not necessarily the result of the poll !)
  • updated to kernel.org Linux 3.0.77
  • CM10.1 kernel update : update bcmdhd driver from GT-9505 Source (sbrissen)


Changelog CM10(.1) v1.5l :

  • compiled with Google's 4.4.3 toolchain / Google's 4.7 toolchain / Linaro 4.7 2013.04 toolchain
    (Don't ask, I won't tell you which is which for now, I'm waiting on your feedbacks ;))
  • Reverted : optimized for size (broke camera on CM10.1)
  • updated to kernel.org Linux 3.0.76
  • updated dynamic fsync to 1.1 (faux123)
  • changed zRam to Snappy compression (Zeev Tarantov)
  • added ARM cpu topology definition, Multi-core scheduler support, SMT scheduler support (Vincent Guittot)
  • added touchboost control via sysfs (AndiP71)
  • added touchboost setting in Aroma
  • added fastscaling setting for zzmoove in Aroma
  • minor fixes applied

  • IMPORTANT : If using my settings you find scrolling to be choppy, please do enable Touchboost !
  • Compiled with Google's 4.4.3
    Yank555.lu-CM10.1-v1.5l-A.zip
    (MD5 abfb87a81a05b8e2928960a8f71fa631)
    (16.88 MiB) Downloaded 624 times

  • Compiled with Google's 4.7
    Yank555.lu-CM10.1-v1.5l-B.zip
    (MD5 3bb82ba74a48ba519d1e2bad5fc3916c)
    (18.2 MiB) Downloaded 767 times

  • Compiled with Linaro 4.7 2013.04
    Yank555.lu-CM10.1-v1.5l-C.zip
    (MD5 07e4e55a680c008ccffb80f751a2ef07)
    (18.18 MiB) Downloaded 521 times

  • Android 4.1.x skipped, use v1.5m above

Changelog CM10(.1) v1.5k :

  • updated zzmoove to 0.4 : screen off freq. limit introduced
  • updated to kernel.org Linux 3.0.73


Changelog CM10(.1) v1.5j :

  • Forced Fast Charge v1.3 : fix fast charge for dock and OTG modes, add wireless charger support
  • updated LED control adding fully customizable intensity override (respecting low power mode)


Changelog CM10(.1) v1.5i :

  • updated LED control adding blinking/fading speed (up to 5x as fast) and intensity (normal = Samsung, bright = CM)
  • updated LED control adding various fading effects (slope operations made available through sysfs interface)
  • updated to kernel.org Linux 3.0.72


Changelog CM10(.1) v1.5h :

  • applied Samsung update 10 source drop diff. to update 9
  • reverted : staging: android: lowmemorykiller: Add config option to support oom_adj values (Arve Hjonnevag, via faux123)

    This caused apps all being put in foreground or visible applications category, huge thanx to d8389 for pointing that out !


Changelog CM10(.1) v1.5g :

  • added zzmoove governor (credits and many thanx to zanezam)
  • added 3 profiles for zzmoove governor in Aroma (profiles by zanezam)
  • added one more profile based on battery by zanezam, revisted by me to keep even less cores online
  • added separate settings for internal and external I/O scheduler and readahead
  • yankasusq : push CPU freq to current max on wakeup

  • Yank555.lu-CM10.1-JB-kernel-v1.5g-aroma.zip
    (MD5 837fb45c82c04d3ca204988413b03cd5)
    (16.54 MiB) Downloaded 422 times

  • Yank555.lu-Android-4.1.x-JB-kernel-v1.5g-aroma.zip
    (MD5 3bddb2744568243724e7424a6c82a64f)
    (16.52 MiB) Downloaded 28 times

Changelog CM10(.1) v1.5f :

  • updated to kernel.org Linux 3.0.71
  • samsung-battery: Reduce battery-monitor wakelock timeouts (AndreiLux)

    Main reason for releasing 1.5f was the reintroduction of the Android 4.1.x (aka. CM10) kernel, so I could have both inline on the same levels. Only difference being the fact that CM10 kernel still has the old mali drivers and CM10 ramfs, whereas CM10.1 kernel comes with updated mali drivers and updated CM10.1 ramfs


  • Yank555.lu-CM10.1-JB-kernel-v1.5f-aroma.zip
    (MD5 e8ce049517cbba3764f08272822e15b2)
    (16.52 MiB) Downloaded 696 times

  • Yank555.lu-Android-4.1.x-JB-kernel-v1.5f-aroma.zip
    (MD5 78e2bd90276f4e7ddfd4b686e033f865)
    (16.51 MiB) Downloaded 91 times

Changelog CM10.1 v1.5e3 :


Changelog CM10.1 v1.5e2 :


Changelog CM10.1 v1.5d2 :


Changelog CM10.1 v1.5d :

  • staging: android: lowmemorykiller: Don't count reserved free memory (Arve Hjonnevag)
  • updated zcache (via faux123)
  • activated cleancache and zcache (always active, not switchable)
  • updated to kernel.org Linux 3.0.70
  • updated ramfs to latest CM10.1 nightly (20130323) - fixes cifs mounts to not show content

  • Yank555.lu-CM10.1-JB-kernel-v1.5d-aroma.zip
    (MD5 7f697c0155e2b8740ab190511dbc255b)
    (16.52 MiB) Downloaded 16 times

Changelog CM10.1 v1.5c :

  • updated to latest CM10.1 kernel changes :
    • bcmdhd: kang from d2 (Entropy512)
    • wireless backport from 3.4 (bbelos)
    • WIFI: Use kernel version 3.4 ifdef's (bbelos)
    • bcmdhd: reenable IPv6, disable multicast in suspend (codeworkx)
    • bcmdhd: disable GAN_LITE_NAT_KEEPALIVE_FILTER (codeworkx)
  • updated to kernel.org Linux 3.0.69

  • Yank555.lu-CM10.1-JB-kernel-v1.5c-aroma.zip
    (MD5 2b8627a6592c63944da8692f1a7c9b01)
    (16.51 MiB) Downloaded 7 times

Changelog CM10.1 v1.5b :

  • YankasusQ : freq_step & sampling_rate untouched in suspend mode
  • ramfs : added pgrep to /sbin (fix kernel settings not set on some ROMs)
  • CM10.1 kernel update : s3cfb: disable spam (codeworkx)
  • CM10.1 kernel update : s5c73m3: print s_ctrl and g_ctrl values (codeworkx)
  • CM10.1 kernel update : s5c73m3: only use camera fw from system if newer than on data (codeworkx)
  • CM10.1 kernel update : display: updates for t0 devices (codeworkx)
  • CM10.1 kernel update : melfas touch: report touch events to cypress for backlight timeout (codeworkx)
  • updated to kernel.org Linux 3.0.68

  • Yank555.lu-CM10.1-JB-kernel-v1.5b-aroma.zip
    (MD5 83de6bb8dd2510c00c10bd5db3b71444)
    (18.06 MiB) Downloaded 35 times

Changelog v1.5a CM10.1

  • included again : staging: android: lowmemorykiller: Add config option to support oom_adj values (Arve Hjonnevag, via faux123)
  • renamed busybox in ramfs to "mount" and symbolically linked "umount" to it so busybox updater won't see 2 busybox installations
  • Forced Fast Charge v1.2b : Restore compliance to Samsung JB code for normal AC charge
  • updated to Boeffla-Sound: Engine 1.6.0
    • speaker tuning introduced (1.5.1)
    • mic mode discontinued (1.5.1)
    • mic level separate for general recording and call usage implemented (1.5.1)
    • stereo expansion added (1.6.0)
    • mono downmix added (1.6.0)
  • added option in Aroma to enable/disabled speaker tuning in Boeffla Settings
  • added standby max. cpu frequency to YankasusQ governor (screen off)
    IMPORTANT

    Please bear in mind when setting the standby max CPU freq.
    that Samsung uses 1.4GHz by default, so it's not about beating
    any kind of record, as going too low may result in a sleep of death !!
    Battery pull or long power key will be necessary to get out if it rather
    unproperly I might add !
  • updated to kernel.org Linux 3.0.67

  • Download link for CM10.1 with mail driver update only (Correct MD5 is 82be29acfb02943c0b5c4303e4c9108c, old MD5 was 8fc7e6e7cf8084d890ad3a670a7daf80)

Changelog v1.5 CM10.1

  • updated to kernel.org Linux 3.0.66
  • mali: update to r3p1-01rel1 (codeworkx)
    To use this kernel on CM10.1, please be certain (as long as the ROM side driver is not included in the nightlies) to :

    1) Flash codeworkx's update (it contains more than the kernel !)

    2) Flash my updated kernel

    I expect next nightlies (20130223) to have the needed update in the ROM libs to cope with the mali changes in the kernel.


  • Download link for CM10.1 with mail driver update only (MD5 e0c0d89f6621484ffc39e40204176e48)

Changelog v1.5

  • bcmdhd: update from jb update 7 (codeworkx)
  • added YankasusQ governor (battery friendlier when screen on)
    Based on PegasusQ. Introducing cpu frequency limitations based on the number of cores online.

    sysfs additions :

    - cpu_max_freq_1 : max. freq. applied when running on 1 core (defaults to 1.0GHz)
    - cpu_max_freq_2 : max. freq. applied when running on 2 cores (defaults to 1.1GHz)
    - cpu_max_freq_3 : max. freq. applied when running on 3 cores (defaults to 1.2GHz)
    - cpu_max_freq_4 : max. freq. applied when running on 4 cores (defaults to 1.4GHz)
    - cpu_max_freq_current : currently applied max. frequency (read-only)

    NB: hotplug frequencies and rq thresholds have been revised up to keep the device running on as little cores as possible.
  • added options in Aroma for YankasusQ configs (8 configs, 2x @1.3GHz, 2x @1.4GHz, 2x @1.5GHz and 2x @1.6GHz)
  • added presets in Aroma for YankasusQ configs (Stock Powersave & Balanced, OC Powersave & Balanced)
  • removed ondemand, userspace, powersave, performance governors (not optimised for quadcore anyway)
  • Aroma preset "Customize" is now called "Full Stock" and defaults to replicate a full stock kernel
  • added support for nfs (as kernel modules)
  • added option in Aroma to load nfs kernel modules at startup
  • updated to kernel.org Linux 3.0.64

  • I made a mistake, new governor settings were not set correctly, please redownload and be certain to have the new MD5 ! Sorry for this !

  • Download link for AOSP/CM Android 4.1.x (MD5 1c9d43a5f2abdb69fd253713721ac3da, old b9a8cc6271b32948ef4b5febea983fde)

  • Download link for AOSP/CM Android 4.2.x (MD5 ca14fc7e6d03b546f1d5d50b18cc0795, old 471b56fbb62e01ce739f5092688c1edd)

Changelog v1.4i


Changelog v1.4h


Changelog v1.4g

  • updated to Boeffla-Sound: Engine 1.4.9
    • Completely neutralized mic_mode to avoid any interference to related registers when not used (fix for call issues with certain firmwares) by not doing any actions until mic_mode is enabled + using cached registers when restoring default mode back
    • mic_mode is now exclusive and not "intelligent" anymore. If you want to make calls, switch mic_mode back to default first
    • Safety-net introduced to avoid writing empty mic register cache values back to the registers in any case (thx to Yank555 for this idea)
    • fix reported issue about boeffla sound starting up in enabled mode is causing a boot loop
  • removed mic setting from Aroma completely, no need to change set it during boot
  • updated to kernel.org Linux 3.0.61
  • staging: android: lowmemorykiller: Add config option to support oom_adj values (Arve Hjonnevag)
  • staging: android: lowmemorykiller: Don't count reserved free memory (Arve Hjonnevag)
  • changed Aroma theme as I regularly got half blinded flashing the kernel in dark environments
  • added a new log file "/data/kernel-boot.log" which will records the kernel initialisation process (including all settings applied) in clear text
  • added a "wait for Android to start" before starting to set the kernel configuration (AndiP71)

  • LMK changes included, so please do consider to reexperiment to find your best settings starting with Stock Settings

  • Download link for AOSP/CM Android 4.1.x (MD5 7320248053e705fec1ffdcba9c800483)

  • Download link for AOSP/CM Android 4.2.x (MD5 bc4e734eedace47062acd54264f8080b)

Changelog v1.4f

  • updated to Boeffla-Sound: Engine 1.4.8 (AndiP71)
    • finally completely neutralize mic_mode to avoid any interference to related registers when not used (further fix for call issues with certain firmwares)

  • Download links removed

Changelog v1.4e

  • updated to Boeffla-Sound: Engine 1.4.7 (AndiP71)
    • reverted some changes supposed to fix the call issues in combination with mic_mode and call detection
    • mic_mode is now exclusive and not "intelligent" anymore. If you want to make calls, switch mic_mode back to default first.
  • added support for ISO 9680 incl. Joliet filesystem (as a kernel module)
  • added support for UDF filesystem (as a kernel module)
  • added option in Aroma to load ntfs kernel module at startup (module was present for quite some time already)
  • added option in Aroma to load ISO 9680 (& Joliet) kernel module at startup
  • added option in Aroma to load UDF kernel module at startup

  • Download link for AOSP/CM Android 4.1.x (MD5 39ea1bd2c09f543778e97a742e1ca63e)

  • Download link for AOSP/CM Android 4.2.x (MD5 54448acbcf2e4ea780e859a581ceb5d2)

Changelog v1.4d

  • updated to Boeffla-Sound: Engine 1.4.6 (AndiP71)
    removed an optimisation in the call detection routine that was identified to cause timing issues in combination with some roms which in the end lead to improper handling of mic mode settings
  • updated to Boeffla-Sound: Engine 1.4.5 (AndiP71)
    fix reported issue about boeffla sound starting up in enabled mode is causing a boot loop

  • Download link for AOSP/CM Android 4.1.x (MD5 65ce480d99b80168ab0f9caba75031ce)

  • Download link for AOSP/CM Android 4.2.x (MD5 3c93e11c02df0befe1598402b497038b)

Changelog v1.4c

  • updated to kernel.org Linux 3.0.80
  • updated to Boeffla-Sound: Engine 1.4.4 (AndiP71)
    fix issue with mic mode functionality interfering with call functionality sometimes (where partner could not hear anything during a call)
  • updated CM kernel sources : update mdm & update sensors and firmware (cmenard)

  • Download links removed, script generator was not run correctly, kernel only running in stock stettings, sorry for this :o

Changelog v1.4b

  • updated to kernel.org Linux 3.0.59

  • Download links removed, script generator was not run correctly, kernel only running in stock stettings, sorry for this :o


Changelog v1.4a

  • updated to kernel.org Linux 3.0.58
  • updated to latest CM10(.1) kernel sources (kept vsync uevent only in 4.1.x kernel, and both vsync uevent and sysfs in 4.2.x)
  • updated Boeffla-Sound to Engine 1.4.3 (AndiP71)

  • Download links removed, script generator was not run correctly, kernel only running in stock stettings, sorry for this :o


Changelog v1.4

  • Boeffla-Sound: Engine 1.4.2 (AndiP71) - Huge thanks for offering me to include his hard work and great sound engine
  • Sudden Death Syndrom Fix (mmc: Soft-patch MoviNAND VTU00M (16GB) eMMC failure - All credits to AndreiLux for extracting this fix from SGS3 JB Update 7 source drop)

  • Download link for AOSP/CM Android 4.1.x (MD5 76ccd46de1f2048be442c1e2a4e05fda)

  • Download link for AOSP/CM Android 4.2.x (MD5 1bac1ece20f037438ef9ea29744d4e50)

Changelog v1.3g


Changelog v1.3f third release


Changelog v1.3f second release

  • updated to latest CM kernel sources (except exynos-mem patch and FIMC use)
  • changed release names to keep both better apart :
    • AOSP/CM Android 4.1.x (aka. CM10)
    • AOSP/CM Android 4.2.x (aka. CM10.1)

Changelog v1.3f

  • added support for XBOX 380 gamepad (modules loadable by Aroma option, as per request by 4ndr0 on http://www.android-hilfe.de)
  • removed /dev/exynos-mem alltogether since it can't be used anyway with chmod 400
  • in Aroma, predefined presets now only change defaults, but you can review the exact settings and change any if you want

  • Download link for CM10 (MD5 8aa4c9739d5f10d9bab6c0002abba1e7)

  • Download link for CM10.1 (MD5 cb3df248f5ac231e9fb7934eba5fbdaf)

Changelog v1.3e

  • added lulzactiveq governor (credits Gokhanmoral, Roberto, Tegrak and AndiP71, as per request by Shaitan on http://www.android-hilfe.de)
  • added ROW scheduler (credits Tatyana Brokhman, as per request by Enrico0802 on http://www.android-hilfe.de)
  • removed hardcore sharpness fixes
  • added mount/umount (busybox) to ramdisk in /sbin for 100% cifs mount compatibility
  • default installation modes have been updated :

    • Yank555.lu :
      • CPU : 1.6GHz, LulzactiveQ
      • I/O : 512Kb readahead buffer, row scheduler
      • LMK : Medium
      • Swap : hardswap, no zram, swappiness 70
      • Fastcharge : enabled, 1000mA USB & AC
      • Soundlevel : speaker +3, stock for headphones
      • Dynamic fsync : enabled
      • CIFS kernel modules : enabled
      • Flash : ask
      • init.d support : no

  • Download link (MD5 0ad8852a3a741c6500e822884e92886e)

Changelog v1.3d


Changelog v1.3c


Changelog v1.3b

  • added option in Aroma to load all needed kernel modules for cifs support on boot (if you get "invalid argument" error on mounting, be sure to use a compatible busybox version !)
  • the kernel is 100% identical to 1.3a, so no need to flash it if you don't need cifs support !
  • default installation modes have been updated :

    • Stocklike :
      • CPU : 1.4GHz, I/O not as CPU load
      • I/O : 256Kb readahead buffer, cfq scheduler
      • LMK : not set
      • Swap : no hardswap, no zram, swappiness not set
      • Fastcharge : disabled
      • Soundlevel : stock for speaker & headphones
      • Dynamic fsync : disabled
      • CIFS kernel modules : disabled
      • Flash : kernel and config
      • init.d support : ask


    • Power :
      • CPU : 1.6GHz, I/O as CPU load
      • I/O : 512Kb readahead buffer, cfq scheduler
      • LMK : not set
      • Swap : no hardswap, no zram, swappiness not set
      • Fastcharge : disabled
      • Soundlevel : stock for speaker & headphones
      • Dynamic fsync : enabled
      • CIFS kernel modules : disabled
      • Flash : kernel and config
      • init.d support : ask


    • Yank555.lu :
      • CPU : 1.6GHz, I/O as CPU load
      • I/O : 512Kb readahead buffer, sio scheduler
      • LMK : Medium
      • Swap : hardswap, no zram, swappiness 70
      • Fastcharge : enabled, 1000mA USB & AC
      • Soundlevel : speaker +3, stock for headphones
      • Dynamic fsync : enabled
      • CIFS kernel modules : enabled
      • Flash : ask
      • init.d support : no

  • Download link (MD5 ba173907729d640b51ab8a24e80f74d8)

Changelog v1.3a

  • updated to kernel.org Linux 3.0.56
  • Fixed bug in Aroma, kernel is now flashed when selecting presets (sorry for that !)
  • changed default installation settings for Yank555.lu :


    • Yank555.lu :
      • CPU : 1.6GHz, I/O as CPU load
      • I/O : 512Kb readahead buffer, cfq scheduler
      • LMK : Medium
      • Swap : hardswap, no zram, swappiness 70
      • Fastcharge : enabled, 1000mA USB & AC
      • Soundlevel : speaker +3, stock for headphones
      • Dynamic fsync : enabled
      • Flash : ask
      • init.d support : no

  • Download link (MD5 0c06d7b07e964b04fc4f28efc0700885)

Changelog v1.3

  • updated to kernel.org Linux 3.0.54
  • added default installation modes that won't ask questions and use a set of default configs :


    • Stocklike :
      • CPU : 1.4GHz, I/O not as CPU load
      • I/O : 256Kb readahead buffer, cfq scheduler
      • LMK : not set
      • Swap : no hardswap, no zram, swappiness not set
      • Fastcharge : disabled
      • Soundlevel : stock for speaker & headphones
      • Dynamic fsync : disabled
      • Flash : kernel and config
      • init.d support : ask


    • Power :
      • CPU : 1.6GHz, I/O as CPU load
      • I/O : 512Kb readahead buffer, cfq scheduler
      • LMK : not set
      • Swap : no hardswap, no zram, swappiness not set
      • Fastcharge : disabled
      • Soundlevel : stock for speaker & headphones
      • Dynamic fsync : enabled
      • Flash : kernel and config
      • init.d support : ask


    • Yank555.lu :
      • CPU : 1.6GHz, I/O as CPU load
      • I/O : 512Kb readahead buffer, sio scheduler
      • LMK : Medium
      • Swap : hardswap, no zram, swappiness 100
      • Fastcharge : enabled, 1000mA USB & AC
      • Soundlevel : speaker +3, stock for headphones
      • Dynamic fsync : enabled
      • Flash : ask
      • init.d support : no

  • Download link (MD5 e20142b7f4370a59a7479170d6535507)

Changelog v1.2a

  • added SIO I/O scheduler
  • added swapon command for zram, as on some ROMs setting initstate to 1 is not enough

  • Download link (MD5 116213bd772e4ff1aab6549871abe18e)

Changelog v1.2

  • added sound output level mod (separated setting for speaker & headphones) - HUGE THANX to AndiP for providing me with invaluable information, couldn't have done this without his help !
  • Dynamic fsync control (faux123) activated now (forgot to activate it in kernel config, sorry for that !!)

  • Download link (MD5 4d2fdc7fa2deae4e754175f7f8ece463)

Changelog v1.1


Changelog v1.0a

  • added scaling_available_frequencies sysfs interface (sorry forgot to include that one...)

  • Download link (MD5 117f9d675bd9b7b56a4902d6c7e56c66)

Changelog v1.0

  • based on CyanogenMod CM10 kernel for i9300 sources (Linux 3.0.31)
  • updated to kernel.org Linux 3.0.52
  • using Paranoid Android 2.54 ramdisk
  • swap support
  • /proc/config.gz support
  • optimized for size
  • Aroma installer with options
  • USB Forced Fast Charge v1.2a (Yank555.lu)
  • CPU OC up to 1.6GHz (Yank555.lu)
  • Triangle Away support (Chainfire)
  • Dynamic fsync control (faux123)
  • TCP westwood congest ctrl (faux123)
  • Proport. Rate Reduction TCP (faux123)
  • ARM AES/SHA1 (faux123)
  • JIT compiler for packet filters(faux123)
  • fix ipv6 protocol lookup (faux123)
  • ipv4 check ret.val. dst_alloc (faux123)
  • ipv6 check ret.val. dst_alloc (faux123)
  • updated LZO compression (faux123)
  • do_fsync() to fget_light() (faux123)
  • reduce mali utilization sampling timeout (AndreiLux)
  • mdnie: custom settings (AndreiLux) - Includes hardcore sharpnes fixes, and black gamma curve adjustment for black crush
  • ntfs (rw) support (kernel support only)
  • zram support (Android optimized)

  • Download link (MD5 fd4bbc970ef350621a8a3ed9c8003e8c)

  • Please do consider this v1.0 as beta, I've started working on this CM10 kernel this evening, and it's just done compiling, so you're testing this with me ;)
[/list]

============================================
This kernel contains the sudden death fix as of v1.4
and the exynos-mem fix as of v1.3c.
============================================


----------------------------------------------------------------------------------------------------------
Important : Should I have given wrong credit, please PM me, I'll update asap.
Attachments
Yank555.lu-CM10.1-v1.6e.zip
(MD5 1a5d8ae7a011665b165eea3ed1ddf9f8)
(18.29 MiB) Downloaded 136 times
Nexus 5 (aka. Hammerhead) 32Gb
Note 3 SM-N9005 32Gb Proudly eFused
SGS3 GT-I9300 32Gb
HTC Sensation XE
HTC HD2
TF300TG 32Gb

Image
Credits FAdrums !
User avatar
yank555
-----------
 
Posts: 3471
Joined: 11 Mar 2013, 20:51
Has thanked: 922 times
Been thanked: 4589 times

Re: [2013/MAR/09][AOSP/CM ROMs] Yank555.lu kernel v1.5b

Postby yank555 » 12 Mar 2013, 21:51

Aroma Settings Explained

Here is a list with explanations about the several options you have in Aroma installer :


  • CPU frequency settings


    • CPU Governor


      • PegasusQ

        This is the stock governor provided by Samsung to control the exynos CPU frequencies and cores hotplugging (switching cores on and off).

      • PegasusQ-IO

        Still the same stock governor at work, but this will set the governor's "io is busy" property to either 1 (= yes) or 0 (= no). If set to yes, this means that if the CPU is waiting for io's to complete, it the governor will consider this as load, and continue to throttle up the CPU freq. If on the other hand it is set to no, in this case, the governor considers this as not being a load, and CPU freq. will start throttling down.

        I like to keep this to yes, as I'm a convinced "race to idle" theory fan, which means best battery drain is achieved if we do what we have to do as fast as possible (higher CPU clock) so we can put cores to sleep sooner and save juice. There are also others that say better battery is achieved by keeping the CPUs on low freqs. but taking longer.

        Don't expect the difference to be huge, and whatever your oppinion on this, I'd rather provided you with the choice, so it's up to you what you consider being the "truth" :D

      • YankasusQ

        This is a PegasusQ governor with a few modifications of my own. It will have the "io is busy" set to 1 by default (see above for details) and has the hotplug parameters changed (thresholds for frequencies and run queue) so as to try to have as little cores online as possible at any given time.

        So far, we're still in a stock Pegasus environment.

        I've also added 4 more parameters that now allow to set the CPU max. frequency for any of the core setups, so you get a CPU max. frequency for single core mode, for dual-core mode, for 3-core mode and for quad-core mod.

        As well, the latest update added a screen off max frequency, which can be set in Aroma. This should keep the freq. low when the phone must is woken up during screen off.

        IMPORTANT

        Please bear in mind when setting the standby max CPU freq. that Samsung uses 1.4GHz by default, so it's not about beating any kind of record, as going too low may result in a sleep of death !! Battery pull or long power key will be necessary to get out if it rather unproperly I might add !


      • LulzactiveQ

        This is a different governor that has been ported to the SGS3 and adapted from dual core to quad core. It will scale up and down the CPU frequencies more aggressively and also hotplug faster (switch cores on sooner but also switch them off sooner).

        The result is a better responsiveness, but at the cost of a little battery.

      • zzmoove (explanations by zanezam, author of the governor, thanx !!)

        Basically this is the ported SGS1 version of the well known "smoove" governor from the good old midnight kernel from Michael Weingaertner (mialwe) with a modified CPU hotplug implementation of the ktoonservative governor from ktoonesz. The original implementation from ktoonesz worked well but I observed that on idle most of the time only one cpu was going to sleep. Well that was not enough for me so I made a modification to put the other cpu's also to sleep (except cpu0). That means that this governor uses more often only one cpu on idle and as a consequence of that it needs less energy. Depending on System load and governor settings all 4 cores will be instantly up again if it is needed.

        So what you can expect now from this thingy is a battery-friendly behaving hotplug conservative governor which uses a frequency lookup table for faster upscaling (so called "smooth scaling"). So this is more a energy-saving than a performer.

        Tuneables/Defaults:
        Sampling Rate (default=2) /sys/devices/system/cpu/cpufreq/zzmoove/sampling_rate
        Sampling Down Factor (default=4) /sys/devices/system/cpu/cpufreq/zzmoove/sampling_down_factor
        Up Threshold (default=70) /sys/devices/system/cpu/cpufreq/zzmoove/up_threshold
        Down Threshold (default=52) /sys/devices/system/cpu/cpufreq/zzmoove/down_threshold
        Ignore Nice Load (default=0) /sys/devices/system/cpu/cpufreq/zzmoove/ignore_nice_load
        Freqency Step (default=5) /sys/devices/system/cpu/cpufreq/zzmoove/freq_step
        Smooth Up (default=75) /sys/devices/system/cpu/cpufreq/zzmoove/smooth_up
        Smooth Scaling for sleep (Screen off) (default 100) /sys/devices/system/cpu/cpufreq/zzmoove/smooth_up_sleep
        Up Threshold for sleep (Screen off) (default 90) /sys/devices/system/cpu/cpufreq/zzmoove/up_threshold_sleep
        Down Threshold for sleep (Screen off) (default 44) /sys/devices/system/cpu/cpufreq/zzmoove/down_threshold_sleep
        Sampling Rate for sleep (Screen off) (default 2) /sys/devices/system/cpu/cpufreq/zzmoove/sampling_rate_sleep_multiplier
        The amound of cores which should run at "screen off" (default 0) /sys/devices/system/cpu/cpufreq/zzmoove/hotplug_sleep
        Up Threshold Hotplug 1 core up (default=68) /sys/devices/system/cpu/cpufreq/zzmoove/up_threshold_hotplug1
        Up Threshold Hotplug 2 cores up (default=68) /sys/devices/system/cpu/cpufreq/zzmoove/up_threshold_hotplug2
        Up Threshold Hotplug 3 cores up (default=68) /sys/devices/system/cpu/cpufreq/zzmoove/up_threshold_hotplug3
        Down Threshold Hotplug down to 1 core (default=55) /sys/devices/system/cpu/cpufreq/zzmoove/down_threshold_hotplug1
        Down Threshold Hotplug down to 2 cores (default=55) /sys/devices/system/cpu/cpufreq/zzmoove/down_threshold_hotplug2
        Down Threshold Hotplug down to 3 cores (default=55) /sys/devices/system/cpu/cpufreq/zzmoove/down_threshold_hotplug3

        Available profiles in Aroma :

        - default : Governor defaults as compiled
        - battery : Battery saving
        - optimized : Balanced setup between battery saving and performance
        - performance : Trimmed to perform rather than save battery
        - yank-battery : Most battery saving, lower hotplugging



      • To sum it up, consider at least this :


        • LulzactiveQ : Snappiest, ideal for games, worst in battery life

        • PegasusQ : Stock, balance between snappiness and battery

        • YankasusQ : Battery saving governor, least snappy, best battery

        • zzmoove : The faster reacting, trimmable to perform or save battery

      • CPU Idle Mode :

        1. IDLE - Clock is gated but power on CPU core remains (static power consumption still active)
        2. AFTR - Clock is gated, power on CPU cores removed and L2 cache power remains. Static power consumption mostly eliminated.
        3. LPA - Cache power removed.
        4. AFTR or LPA cannot be entered if second core is active.
      • Multicore power saving :

          Significance: Increases multi-core awareness!?

          Sched_mc aims to schedule tasks between multiple cores in the CPU. Sched_mc can be a) OFF (value 0), b) load balance (value 2) the cores by keeping the load even between them or c) power-save balance (value 1) by loading first core until it's 100% loaded. Hotplugging does load balancing already by taking care of thresholds, run queues, process priorities, cut-off frequency, etc. So there's no use of sched_mc = 1. Powersave balancing which overloads first core will increase the time to relieve first core (as compared to same task balanced between both the cores). This will cause delay to hit deep-idle states, since only first core can enter AFTR/LPA states.
          Disable sched_mc. There could be only one situation where load balancing or weird-overloading of first core can be useful - when we use dual core mode. Sched_mc is valid only when both cores are online. If someone uses dual-core mode sched_mc is worth a try to handle task-loads across cores.

        Source


    • CPU maximum frequency

      I'd say this one's pretty selfexplaining, it will let you chose at what maximum frequency you want to limit your CPUs. Stock is 1.4GHz, so allowing (up to 1.6GHz) more means you're overclocking the CPUs (expect better perfomance, but to the cost of a slightly higher battery drain !), restricting this to anything lower than 1.4GHz means you're underclocking the CPUs (you can expect to save some battery juice, but to the cost of lesser performance.)

      Since our S3 has quite a powerfull CPU, if you use your S3 for basic tasks only (browing, texting, calling, reading emails...) you may use lower freqs. and not feel any real loss in speed, but if you're gaming etc. expect to feel the difference.

    NB: You will se a different list of options if you chose YankasusQ governor, as it will allow for more frequencies as explained above.

  • MMC I/O Settings

    These settings will be applied only 2 minutes after boot is completed, as we need to wait that the external sd card has become ready in the system before applying this.


    • MMC readahead buffer

      This will set how much more of a file the system will read than an app actually asks for, so that when the app asks for the next data, it is already available, thus winning the time to go get it on internal / external memory.

      Sounds nice, first reflex, put it to the max. As you can see, I've limited the choices to 4Kb max, that is not a technical limit, but more of a failsafe against this very same reflex.

      While reading files sequentially, e.g. from the beginning to the end like on MP3s or movies, more is better since we are going to read what's next in the file anyway, we want to listen to the rest of that song, watch the rest of that movie, if on the other hand the app reads randomly within a file, like a database would do, e.g. your satnav reading the map for you, it will jump reading from here to there, what is the point of reading too much ahead in this case ? Well none, you'll have your system read loads of data that the app is never going to ask for, so it's counterproductive.

      As so often in life, you need to find the perfect balance, but this balance may be different depending on what you do more...

    • MMC I/O Scheduler

      I'll keep this one short, have a look here, considering that we only have "noop, dealine, cfq, sio and row" in this kernel. I couldn't tell you more about this anyway ;)

      Just a few words about the latest addition, ROW, since that one is not explained in the linked thread. ROW has been specifically designed for flash memory storage (e.g. our internal / external memory). It will handle READ operations with higher priority, while delaying WRITE opterations to when there's time for it, but at some point, writes will have to be done anyway, so they won't be delayed forever, obviously.

      It makes the device really feel more responsive and to be honest, it's the only scheduler I ever really actually "felt" a difference.

  • Low Memory Killer Presets

    All the apps you run are put into different categories (as a degree of importance or a kind of service they provide).

    Memory is divided into memory blocks that apps can use. In Android one memory block has 4096 bytes. Each category will have a number of memory pages limit, which as soon as free memory drops below of that limit, will make LMK start killing tasks of that category.

    So the higher the limits, the sooner it will start its blood bath and kill away, or put otherwise, the higher the limit, the more free memory you will have at any given time.

    ALMK is your guardian of free memory if you will.

    Again, balance is key, too high, and you'll end up not having any multitasking at all, but loads of free memory that's not used, bad idea, too low, you might run out of memory, which induces lag and might even trigger Linux's OOM (out of memory killer), which will shot a sight without looking what it's shooting at (more or less), so you don't want to wake that monster either.

    Plus depending on the use of swap and what kind of swap, these settings will also have an indirect impact.

  • Virtual memory

    Perfect transition to swap ;)

    As I just said, memory is divided into memory blocks of 4096 bytes. Each memory block holds also the information when it has been used for the last time.

    Considering this, one single app will be using many blocks. Some of those the app will be using a lot, some it won't. Take a simple card game. When you're playing, you're not using the app's settings menu, thus not using any of the blocks that hold those parts of the app.

    Swap is a process that is used in most of modern operating systems. The virtual memory management system (that's swap !) will swap out all the blocks that were not used for a certain time, this "certain time" is influenced by swappiness and a few other parameters that we can change.

    The plus is that the memory blocks that have been swapped out will free up RAM to be used by other apps, thus allowing for more apps to run at the same time.

    On the other hand, if you need a swapped out block, that will cost extra time, since it's not located in memory any more but on the swap partition, so it will need to be reloaded into RAM (possibly by swapping out another block to make room for this).

    That should give you a glimpse on the benefits and the costs of using swap. There's that damn balance once again...

    That should also give you an idea of why LMK settings matter, since if almost no free ram is available, a swap in will generally cost a swap out first then the swap in !

    Consider swap as a way to have only part of the apps in RAM instead of having all of it, and as such allowing for more apps to run at the same time.

    BTW, it does not add RAM, you can only add RAM by actually adding physical RAM, anyone telling you otherwise is either lying or does not know what she/he's talking about ;)


    • Hardswap

      My favorite, since it adds virtual memory, without taking anything for it, swapped out memory pages are stored on a separate partition on the external SD card. The drawback is it's actually slower than using internal memory, but I don't like that, wearing internal memory is kind of bricking the phone, where wearing out an SD card just means replacing it, much cheaper. And it's much slower than zram, but ... read ahead ... ;)

    • zram

      The one I don't like that much. It's fast, yes. It will take less RAM than it will give swap in return, still true as it uses compression to store the swapped out memory pages, so you'll be fitting more pages in swap than swap actually uses pages to store them.

      But, there's always a but, you now understand that swap is not RAM, so taking RAM away to use as swap, is removing RAM from running apps. The more zram, the more RAM you take from your apps to acutally run.

      But again, since it's the fastest, maybe it's going to fit your need better than hardswap, so you need to try, and with Aroma, that's real easy to do :D

    As a sidenote, it might be interesting to read the FAQ in my hardswap thread if you want to know some more about this.

  • Fast charge

    My favorite first kernel mod, the one that gave me the courage to go the whole way to compiling a kernel as I just needed to port it on my Sensation at the time.

    This is the S3 flavour of the mod, it has a few options :


    • Substitute

      This is the classic fast charge mod, which just tells the device to charge on a USB port as if it were an AC charger. It's a but simplistic, but back in the days (that's just a few months back actually) it was fine.

      I've kept the logic, since there are apps on Play Store that allow to enable / disable this mode from an app/widget.

      But I consider this deprecated.

    • Custom current

      Now the S3's hardware allows for something quite nicer, we can actually set the charging rate as we wish ! In this mode, well you just chose at what rate you would like to charge your battery when connected to a USB port (475mA/h is default) or an AC wall charger (1000mA/h is default).

      Be aware that you may fry your USB port if you draw too much and it overheats, but if it's a port that fully complies to the standard, it should shut down (stop giving current) if you draw too much from it.

      Also, charging at higher rate than 1000mA/h (= wall charger rate) you may shorten the life of your battery, so it's up to you to use this, again, with balance ;)

  • Dynamic fsync settings

    This is a goodie by faux123, so all credits go to him for creating this unique feature !

    Many kernels just disable synchronous writes to file to speed up system. While this works neatly, it is also dangerous as processes believe that file writes are actually sync'ed to disk (or mmc media in our case) while this is not yet true !

    The gain is a noticably smoother user experience, but the risk of doing so is to have a corrupted filesystem if the device crashes, user pulls battery, battery fully depleats ... so that the device is turned off unexpectedly.

    To allow for the benefit, but to minimize the risk, faux123 created dynamic fsync, which while the screen is on, will defer file sync temporarily, but when screen gets turned off, a flush is called to synchronize all outstanding writes keeping your data safe.

    Now it's up to you to either use this unique feature (that has been enabled by default up until v2.2) or choose to stay stock by disabling it, thus writes being done synchronously, which is safer but also slower.

  • Boeffla Sound Engine by AndiP

    First off, huge thanks to Andi for offering me to incluse his amazing sound engine !!

    This engine allows to control the hardware sound processor, as such it's not a software implementation that consumes CPU power and other resources, it "only" chnages the hardware settings that our hardware is capable of and which Samsung didn't allow us to use, why ever...

    If you want on the fly control over the Boeffla Sound Engine, please check out the Boeffla Sound App on Play Store !!

    It's the easiest way to control it and it's the only truely interactive way, so I'd advise to use it ;)

    Nonetheless, these are the options available in Aroma installer for the Boeffla Sound Engine :


    • Master switch

      enabled - pretty selfexplaining, this will activate the Sound Engine

      disabled - pretty selfexplaining, too, this will leave the Sound Engine off, so you're on stock Samsung sound

      don't set - use this if you intend to use the APP the control the Sound Engine or if you're rather into implementing your own init.d script to set it up

    • Speaker - Output level

      This feature is the same that I previously implemented in my Sound Level Mod, it allows to make the speaker louder, but be careful not to blow the speaker !!

    • Headphones - Output level

      This feature is also the same that I previously implemented in my Sound Level Mod, it allows to make the headphones louder, but be careful not to blow your ears !!

    • Headphones - Equalizer Mode

      sat.prev. - enable hardware equalizer with saturation prevention (will compress sound if the output is too high to prevent distortions)

      enabled - enable hardware equalizer without saturation prevention

      disabled - keep the hardware equalizer off (stock behaviour)

    • Headphones - Equalizer Setting

      These are a few presets for the hardware equalizer, while standard will keep all bands at 0, you'll just need to test the other presets for yourselves (eargasm, pleasant4ears, bass-extreme, Yankgasm).

    • Headphones - Privacy Mode

      This setting causes the speaker to be completely muted for notification sounds, phone ring signals etc. as long as a headphone is plugged in. This avoids people looking at you when you are wearing headphones and receive a notification, which is by standard played via both speaker and headphones. Now, nobody will notice anymore when you get alerts while wearing headphones.

      But that means, the speaker will not work as long as you have your headphones plugged in !!

    • Headphones - DAC direct

      By switching DAC direct to on, you will bypass the output mixer in the signal path and connect the DAC directly to the headphone amplifier.

      Expected impact: Better sound quality when using headphones, potentially some minor battery savings.

    • Headphones - DAC 128bit oversampling

      This setting changes the oversampling rate from 64 to 128 bit.

      Expected impact: Better sound quality when using headphones, potentially some minor additional battery drain.

    • Headphones - FLL clock tuning

      This setting changes the FLL configuration of the Wolfson WM1811 audio hub.

      Expected impact: Better sound quality when using headphones.

    • Microphone - Sensitivity mode

      By this setting you can configure the microphone mode when you want to record videos etc. in very loud and noisy environments. Ever tried it and your audio was completely distorted and over-saturated? By this setting, you can avoid this in future.

      Note: Of course this setting is automatically disabled as soon as you use your phone for a call.

      concert - highest reduction, for extremely loud environments
      noisy - high reduction, for very loud environments
      light - medium reduction, for loud environments
      stock - no modificaiton in microphone sensitivity

      Expected impact: You can record also in very loud environments and audio is not distorted.

  • Kernel modules

    I've made these supports as kernel modules, I see no need to have it in the kernel if you don't need them.

    • CIFS network filesystem support

      This will load the kernel modules for CIFS support at boot time. Apps like CIFS Manager can do that for you, but if you are keen to use CIFS shares from your S3 like I do, preloading them at boot is a good idea.
    • NFS network filesystem support

      This will load the kernel modules for NFS v3 support at boot time.
    • NTFS filesystem support

      This will load the kernel modules for NTFS support at boot time, which will allow to mount NTFS partitions on SD cards or external harddrives.

      Please note that the kernel only provides the modules, mounting the partitions will not be done automatically, you will have to do this either yourself or using some kind of app.
    • ISO 9660 filesystem support

      This will load the kernel modules for ISO 9600 filesystem support at boot time, which is used on CDs or DVDs.

      Please note that the kernel only provides the modules, mounting the partitions will not be done automatically, you will have to do this either yourself or using some kind of app.
    • UDF filesystem support

      This will load the kernel modules for UDF filesystem support at boot time, which is used on CDs or DVDs.

      Please note that the kernel only provides the modules, mounting the partitions will not be done automatically, you will have to do this either yourself or using some kind of app.
    • XBOX 360 gamepad support

      This was a user request which was quite easy to implement, but again, I did it as a kernel module as, for instance I don't use it, and I suppose quite a few won't, so only those that really use their Xbox gamepad to play should preload the module on boot.

      This only works if you connect the gamepad to your S3 using an USB OTG cable ! It won't work wirelessly.

  • init.d script support

    The hardest to explain :rolleyes:

    Let me try it this way. Most mods will change settings, and to do this so that those settings stick, they need to do it everytime your device boots.

    To do so, there is a folder called init.d, it's actually located in "/system/etc/init.d" and it will hold scripts which will be executed everytime your device boots.

    Well and this "will be executed" is the thing we need to focus on here. This can be either handled by the kernel (or rather ramdisk to be more precise, which comes with the kernel), or it can be handled by the ROM (like this is the case in mike's ARHD ROMs).

    So depending on the ROM you have, you either need the ramdisk to handle this, or the opposite just don't want it to take care of that, since if both do, the scripts will be executed twice, which may be fine, but may also be a problem...

    So you need to know what your ROM does here, and according to what the ROM does, have or not have the ramdisk do it.

    So to make this as easy as possible, ask in your ROM thread if the ROM handles init.d.

    If the ROM does, then choose no in Aroma.

    If the ROM does not, then choose yes in Aroma.
Nexus 5 (aka. Hammerhead) 32Gb
Note 3 SM-N9005 32Gb Proudly eFused
SGS3 GT-I9300 32Gb
HTC Sensation XE
HTC HD2
TF300TG 32Gb

Image
Credits FAdrums !
User avatar
yank555
-----------
 
Posts: 3471
Joined: 11 Mar 2013, 20:51
Has thanked: 922 times
Been thanked: 4589 times

Re: [2013/MAR/09][AOSP/CM ROMs] Yank555.lu kernel v1.5b

Postby yank555 » 12 Mar 2013, 21:51

Frequently Asked Questions

  • Are exFAT formated sd cards supported ? or Now I flashed this kernel my sdcard is not detected anymore ?

    So far, no, there's no exFAT support.

    exFAT is a Microsoft proprietary format for which we don't have sources. There is a way to force the kernel to load the module, but since 64Gb sdcards can be formated in FAT32 as well (not in Windows, though), I so far didn't see the need to include that hack. It's against my open source religion.

    Blame Microsoft for making exFAT closed source and balme Google way more for using it anyway :(

  • Does this kernel support undervolting, are there plans to add support ?

    I have no undervolting in the kernel, and no plans to include it either, as it makes no measurable battery life difference whatsoever.

    At best, it keeps the device a little cooler, but I never had temp issues.

    I've done my fair share of testing back then on the htc Sensation, undervolting as low as -100mV, without any noticable battery life increase, at -125mV all I got was occasional random reboots.

    So what it will bring most certainly is instability and that will flood the kernel thread with hotreboot and freeze posts because most users tend to just exagerate and use more UV than their device in fact can handle.

    It may seem stable at first, but may not stay so as frequency is throttled up, you'd need to finetune every step to do it properly... a lot of work for a mere placebo effect, so for me absolutely not worth adding it.

    Anyway, that's just my oppinion on the topic, I don't pretend to own the BIG TRUTH on that, this is just based on my observations.

    My kernels, though, will be made according to my oppinion obviously ;)

  • Is there a way to remove this kernels configuration scripts when going for another kernel ?

    All leftovers are passive, e.g. they won't get executed by any other kernel as I created a file of my own and have an own entry in init.rc to execute it. New kernel = new ramdisk = new init.rc = no execution.

    The files are :

    • /system/etc/init.kernel.sh
    • /system/etc/init.hardswap.sh (only if you chose hardswap = yes)
    • /data/kernel-boot.log
    • /data/kernel-script.log
    • /data/hardswap.log (only if you chose hardswap = yes)
    • /data/swap.*.log (only if you chose hardswap = yes)

    I've made a flashable kernel cleanup zip that will remove everything in preparation to flash a different kernel, so your system becomes perfectly clean again, as if my kernel never had been there.

    Kernel configuration & log files removal (MD5 313529df6427e5f560b1001748f347b5)
Nexus 5 (aka. Hammerhead) 32Gb
Note 3 SM-N9005 32Gb Proudly eFused
SGS3 GT-I9300 32Gb
HTC Sensation XE
HTC HD2
TF300TG 32Gb

Image
Credits FAdrums !
User avatar
yank555
-----------
 
Posts: 3471
Joined: 11 Mar 2013, 20:51
Has thanked: 922 times
Been thanked: 4589 times

Re: [2013/MAR/09][AOSP/CM ROMs] Yank555.lu kernel v1.5b

Postby yank555 » 12 Mar 2013, 21:51

Usage statistics for an average day with these settings :

  • CPU : 1.6GHz, PegasusQ I/O as CPU load
  • I/O : 512Kb readahead buffer, sio scheduler
  • LMK : Medium
  • Swap : 256Mb hardswap, no zram, swappiness 70
  • Dynamic fsync : enabled

Image

Image

Image

Image

Image
Nexus 5 (aka. Hammerhead) 32Gb
Note 3 SM-N9005 32Gb Proudly eFused
SGS3 GT-I9300 32Gb
HTC Sensation XE
HTC HD2
TF300TG 32Gb

Image
Credits FAdrums !
User avatar
yank555
-----------
 
Posts: 3471
Joined: 11 Mar 2013, 20:51
Has thanked: 922 times
Been thanked: 4589 times

Re: [2013/MAR/09][AOSP/CM ROMs] Yank555.lu kernel v1.5b

Postby yank555 » 13 Mar 2013, 21:54

I just saw that PA3.10 official now has the new mali updates, which means it will run on v1.5b kernel.

JP.
Nexus 5 (aka. Hammerhead) 32Gb
Note 3 SM-N9005 32Gb Proudly eFused
SGS3 GT-I9300 32Gb
HTC Sensation XE
HTC HD2
TF300TG 32Gb

Image
Credits FAdrums !
User avatar
yank555
-----------
 
Posts: 3471
Joined: 11 Mar 2013, 20:51
Has thanked: 922 times
Been thanked: 4589 times

Re: [2013/MAR/09][AOSP/CM ROMs] Yank555.lu kernel v1.5b

Postby Railius » 14 Mar 2013, 06:10

Sup Yank, nice page, can you remember me the steps to test if hardswap is working?
yank555 v1.5b with PA 3.10
Thanks in advance
Railius
 
Posts: 3
Joined: 13 Mar 2013, 19:44
Has thanked: 1 time
Been thanked: 0 time

Re: [2013/MAR/09][AOSP/CM ROMs] Yank555.lu kernel v1.5b

Postby yank555 » 14 Mar 2013, 08:31

Railius wrote:Sup Yank, nice page, can you remember me the steps to test if hardswap is working?
yank555 v1.5b with PA 3.10
Thanks in advance


Just type this in a terminal :

su
free
cat /proc/swaps

JP.

Sent from my Sotmax V15 / Yank555.lu SGS3 U8 kernel v3.3a (Linux 3.0.68) powered Galaxy S3 i9300 using Tapatalk 2
Nexus 5 (aka. Hammerhead) 32Gb
Note 3 SM-N9005 32Gb Proudly eFused
SGS3 GT-I9300 32Gb
HTC Sensation XE
HTC HD2
TF300TG 32Gb

Image
Credits FAdrums !
User avatar
yank555
-----------
 
Posts: 3471
Joined: 11 Mar 2013, 20:51
Has thanked: 922 times
Been thanked: 4589 times

Re: [2013/MAR/09][AOSP/CM ROMs] Yank555.lu kernel v1.5b

Postby planeta89 » 14 Mar 2013, 22:53

Thanks Yank!!the best kernel!
planeta89
 
Posts: 26
Joined: 14 Mar 2013, 18:40
Location: Moscow
Has thanked: 38 times
Been thanked: 5 times

Re: [2013/MAR/09][AOSP/CM ROMs] Yank555.lu kernel v1.5b

Postby ekie84 » 15 Mar 2013, 01:47

Flashing v1.5b now :D
ekie84
 
Posts: 39
Joined: 13 Mar 2013, 23:49
Has thanked: 24 times
Been thanked: 12 times

Next

Return to Kernels

Who is online

Users browsing this forum: No registered users and 1 guest