[i9300][2014/jun/08][TW ROMs] Yank555.lu kernel v4.2a-beta3

Which Mali implementation should stay ? (you can change your vote anytime)

Poll ended at 30 Nov 2013, 11:38

Samsung's Update 12 (as in 4.0 and 4.0+)
169
47%
Samsung's Chinese Update 1 (as in 4.0a)
137
38%
I don't care, both are equivalent
54
15%
 
Total votes : 360

[i9300][2014/jun/08][TW ROMs] Yank555.lu kernel v4.2a-beta3

Postby yank555 » 12 Mar 2013, 20:00

======================================
Kernels up to v3.4f will only work on Samsung 4.1.2 firmwares.
Kernels starting from v4.0 will only work on Samsung 4.3 firmwares.
None of the kernels will work on leaked 4.2.x firmwares.

======================================


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 Samsung JellyBean Update 5, 6, 7 ... kernel sources, so it is intended only to be used on Samsung JellyBean based ROMs.

The kernel starting from 4.0 for Android 4.3 has been tested on :

  • ArchiDroid 1.7.1
  • WanamLite 7.2, 7.3
  • Neatrom lite+4.0
  • Duxter Rom
  • Omega ROM v51, v52, v53, v54, v55, v56
  • RevivaRom by IOIdroid
  • FoxHound 1.0 (4.3 MJ9)
  • Smart Phone Revolution
  • NeatRom 6.2
  • Smart Droid v2.1, v3.4, v4
  • ZDroid v4
  • Revolutionary S5
  • Sensation rom V7
  • ... (you tell me ;))

The kernel up to 3.4f for Android 4.1.2 has been tested on :
  • Sotmax JB Ultimate Stock v2 - v15
  • ARHD 11.0.0, 12.0,13.0 ... 18.0
  • Stock Deodexed DLIB, DLJ1, DLJ2, DLJ4
  • Stock Odexed DLJ1
  • InsertCoin 2.1.0, 3.0.0
  • WanamLite JB 4.0.1
  • Dragon Rom v4
  • Omega ROM v30 - v50.1
  • NxTGen ROM XXDLJ4
  • VikingRom 10, v6
  • VikingWay 1.1
  • Ultima Rom 4.1.1
  • Turkbey LJ1
  • crDroid V7.2
  • MIUI - RAYGLOBE V. 7
  • NeatROM lite
  • Darkyrom v8.4
  • Foxhound 1.8 MA1
  • MIUI.us 3.1.18 JRO03C based Samsung
  • official MIUI 3.2.22
  • Purelook
  • Grisza Monster Beam
  • ... (you tell me ;))


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 Samsung 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.

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.

  • Sotmax

    Huge thanx for making a perfectly stable 240dpi Samsung based ROM, that has become my a daily driver !

  • 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: 3520
Joined: 11 Mar 2013, 20:51
Has thanked: 924 times
Been thanked: 4608 times

Changelog

Postby yank555 » 12 Mar 2013, 20:33

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 :

  • KK v4.2a-beta3 can be found here. <= This kernel is for i9300 TouchWiz KK (4.4.2) port from Note II !

  • KK v4.2a-beta2 can be found here. <= This kernel is for i9300 TouchWiz KK (4.4.2) port from Note II !

  • KK v4.2a-beta1 can be found here. <= This kernel is for i9300 TouchWiz KK (4.4.2) port from Note II !

  • v4.2a-beta1 can be found here. <= Don't be afraid to test this one out, it has a new zzmoove !


Changelog v4.2 - For Samsung 4.3 ROMs only

  • updated zzmoove to v0.8
  • updated zzmoove v0.8 yank battery and battery extreme profiles


Changelog v4.1c - For Samsung 4.3 ROMs only

  • 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 XXUGNA5 ramfs


Changelog v4.1b - For Samsung 4.3 ROMs only

  • reverted triangle away support (so the app can reset counter via alternative way)
  • 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)
  • updated fs namespace (so cifs should work again, tomkasick)
  • updated 'update-binary' to enable flashing the kernel using Philz recovery
  • updated Boeffla Sound to 1.6.5 (AndiP71)
  • ramfs : updated to XWUGML4 ramfs


Changelog v4.1a - For Samsung 4.3 ROMs only

  • added black crush fix (AndiP71)
  • added sharpness fix (disabled by default, AndiP71)
  • Aroma script generator : added sharpness fix option


Changelog v4.1 - For Samsung 4.3 ROMs only

  • updated kernel to Samsung's Update 13 (MK6, for Android 4.3)
  • added CPU-idle and sched_mc_power_savings options in Aroma (requested by janres155)
  • added frandom kernel module (through AndiP71)
  • added zen I/O scheduler (through AndiP71)


Changelog v4.0b - For Samsung 4.3 ROMs only

  • reverted mali r3p2 drivers from SEA Update 1 source drop (I9300XXUGMJA, aka. the chinese release)
  • ramfs : updated mini busybox to support mounting cifs and priority for swap
  • Aroma script generator : implement zram using 4 devices
  • updated AROMA to 2.70RC2


Changelog v4.0a - For Samsung 4.3 ROMs only

  • updated mali r3p2 drivers from SEA Update 1 source drop (I9300XXUGMJA, aka. the chinese release)


Changelog v4.0+ - For Samsung 4.3 ROMs only

  • fixed custom boot animations support (Samsung already had the included by default)


Changelog v4.0 - For Samsung 4.3 ROMs only

  • update kernel to Samsung's Update 12 (for Android 4.3 only)
  • ramfs : updated to XXUGMJ9 ramfs
  • updated default USB charge level to 475mA/h (safer for new users)
  • updated fast charge to v1.5 (interface revampt)
  • updated to kernel.org Linux 3.0.101 [EOL]

  • If you are having root issues, flash this SuperSU by Chainfire.

  • Long time idle drain test shows 0.36% / h battery loss.


Changelog v3.4f

  • added native Samsung exFAT support (OSRC)
  • added support for 4 concurrent zram devices (1)
  • 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 to kernel.org Linux 3.0.96

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


Changelog v3.4e

  • Forced Fast Charge v1.4a : return "invalid argument" when writing a wrong value in sysfs tunables (Yank555.lu)
  • 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 from snappy v3 to lz4 (Yank555.lu)
  • updated zzmoove yank battery profile
  • updated zzmoove yank extreme battery profile
  • wifi : reduced wakelock times (DerTeufel)
  • updated to Samsung Update 11 sources
  • updated to kernel.org Linux 3.0.89
  • activated unaligned-access in compiler flags


Changelog v3.4d

  • 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 zzmoove yank battery profile
  • extended touchboost : added user selectable frequency (Yank555.lu)
  • updated to kernel.org Linux 3.0.86


Changelog v3.4c

  • 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 v3.4b

  • updated to kernel.org Linux 3.0.81
  • updated ROW scheduler (Tatyana Brokhman through faux123)
  • 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)
  • 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)
  • updated Snappy compression (used in zRam, through googyanas


Changelog v3.4a

  • skipped to keep in line with CM kernel version names, all included in 3.4b, see changelog above

Changelog v3.4

  • 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 !


Changelog v3.3k

  • updated to kernel.org Linux 3.0.77


Changelog v3.3j

  • changed to Google's Android Prebuilt 4.7 Toolchain
  • Reverted : optimized for size
  • 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
  • added custom boot animation support

  • IMPORTANT : If using my settings you find scrolling to be choppy, please do enable Touchboost !
    Yank555.lu-i9300-JB-kernel-v3.3j.zip
    (MD5 cd364cc371390389f51c84723ed2d00a)
    (9.42 MiB) Downloaded 1266 times

Changelog v3.3i

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


Changelog v3.3h

  • 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 v3.3g

  • updated LED control adding blinking/fading speed (up to 5x as fast) and intensity (normal = Samsung, bright = CM) (on request by mkchrissi)
  • updated LED control adding various fading effects (slope operations made available through sysfs interface)
  • fixed some apps refusing to fade even if fading was configured
  • updated to kernel.org Linux 3.0.72


Changelog v3.3f

  • 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 v3.3e

  • 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
  • samsung-battery: Reduce battery-monitor wakelock timeouts (AndreiLux)
  • updated to kernel.org Linux 3.0.71
  • updated to Samsung Update 10 source drop (very minor changes, but at least there were 2 left that were not yet included in Linux updates)


Changelog v3.3d2

  • changed Boeffla settings in script generator (set later to avoid potential mic issues)
  • added extended options in Aroma to support zram up to a size of 700Mb (instead of 250Mb)


Changelog v3.3d

  • 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


Changelog v3.3c

  • same kernel as 3.3b-beta2, but based off of SGS3-U7-v3.2a with diff. of Samsung Update 7 to 8 applied only, defconfig unchanged (as was in 3.2a)
  • updated to kernel.org Linux 3.0.69
  • fixed MHL no sound issue (reverted "ASoC: wm8994: Ensure there are enough BCLKs for four channels" by Mark Brown)


Changelog v3.3b

  • never released

Changelog v3.3a

  • YankasusQ : freq_step & sampling_rate untouched in suspend mode
  • ramfs : added pgrep to /sbin (fix kernel settings not set on some ROMs)


Changelog v3.3

  • Samsung JB Update 8 sources (Linux 3.0.31)
  • updated to kernel.org Linux 3.0.67 (proper update, including 3.0.39 memory management changes)
  • using XXELLA ramdisk
  • swap support
  • zram support (Android optimized)
  • /proc/config.gz support
  • optimized for size
  • ntfs (rw) support (as a kernel module)
  • ISO 9660 support incl. Joliet filesystem (as a kernel module)
  • UDF filesystem support (as a kernel module)
  • cifs support (as kernel modules)
  • nfs support (as kernel modules)
  • Forced Fast Charge v1.2b
  • CPU OC up to 1.6GHz
  • Triangle away support
  • dynamic fsync support (faux123)
  • TCP westwood congest ctrl (faux123)
  • Proportional 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)
  • disabled mali state tracking (AndreiLux)
  • reduce mali utilization sampling timeout (AndreiLux)
  • black crush fix (AndreiLux/AndiP71)
  • added SIO scheduler
  • added ROW v4 scheduler
  • fading LED notification with normal or high LED intesity
  • staging: android: lowmemorykiller: Add config option to support oom_adj values (Arve Hjonnevag, via faux123)
  • sysfs interface to delay fsearlysuspend (Yank555.lu, base idea Codeworkx)
  • added lulzactiveq CPU governor
  • added yankasusq CPU governor
  • removed ondemand, userspace, powersave, performance governors (not optimised for quadcore anyway)
  • Boeffla-Sound: Engine 1.6.0 (AndiP71) - Huge thanks for offering me to include his hard work and great sound engine


    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 !


  • Download link (MD5 4fb82e347c7c74c1de0bacf1983b60ed)

Changelog v3.2

  • 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

  • Download link (MD5 6b89f98f6c1f876f463844257533020b)

Changelog v3.1i

  • updated to kernel.org Linux 3.0.62
  • Disabled "staging: android: lowmemorykiller: Add config option to support oom_adj values (Arve Hjonnevag, via faux123)" since it made issues on some ROMs (that tweak OOM values obviously)

  • Download link (MD5 e4794178a578d4c65fdd9139d10441fe)

Changelog v3.1h

  • since obvioulsy most don't read and thus don't take my warning into consideration : Reverted "staging: android: lowmemorykiller: Don't count reserved free memory (Arve Hjonnevag)"
  • stopped regulator messages from flooding dmesg

  • Download link (MD5 c906c684947bc1f09722c5f273282ecd)

Changelog v3.1g

  • 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 (MD5 5cdd1c4fc91602bae31afd583f4571d7)

Changelog v3.1f

  • 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 link removed

Changelog v3.1e

  • 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 9660 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 9660 (& Joliet) kernel module at startup
  • added option in Aroma to load UDF kernel module at startup
  • reuploaded : fixed CRT-Off delay not set by script generator (please redownload)

  • Download link (New MD5 d6067f440d2c3005ff78320cfdf0833a / old MD5 413c53bac262c1bbd0a38fa7b5c1feee)

Changelog v3.1d

  • 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 (MD5 aee22c0cd9dcaec057a807b220087dff)

Changelog v3.1c

  • fading LED notification with normal or high LED intesity
  • added Aroma option differntiate the intensity if you enable fading LED notification
  • updated to kernel.org Linux 3.0.60
  • 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)

  • Download link (MD5 cb714cda591fc8b80071dde4b1658dd0)

Changelog v3.1b


Changelog v3.1a

  • fading LED notification (credits to xplodwild & codeworkx)
  • added Aroma option to enable / disabled fading LED notification

  • Download link (MD5 cfaff515a7e4abbf519c7cfddc070f47)

Changelog v3.1

  • Complete rebase on Samsung JB Update 7 sources (Linux 3.0.31)
  • updated to kernel.org Linux 3.0.58
  • using XXELLA ramdisk
  • swap support
  • zram support (Android optimized)
  • /proc/config.gz support
  • optimized for size
  • ntfs (rw) support (kernel support only)
  • Forced Fast Charge v1.2a
  • CPU OC up to 1.6GHz
  • Triangle away support
  • dynamic fsync support (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)
  • disabled mali state tracking (AndreiLux)
  • reduce mali utilization sampling timeout (AndreiLux)
  • added SIO scheduler
  • added ROW v4 scheduler
  • black crush fix (AndreiLux/AndiP71)
  • added lulzactiveq CPU governor
  • sysfs interface to delay fsearlysuspend (Yank555.lu, base idea Codeworkx)
  • Boeffla-Sound: Engine 1.4.3 (AndiP71) - Huge thanks for offering me to include his hard work and great sound engine

  • Download link (MD5 c148f18c60599e6d7354e324ce80bcc6)

Changelog v3.0b

  • updated Boeffla-Sound: Engine 1.4.3 (headset level can be set down up to 20, per shell script only)
  • option added to no set anything Boeffla related in generated kernel config script to allow user init.d scripts to succeed in configuring Boeffla settings
  • updated to kernel.org Linux 3.0.58

  • Download link (MD5 1209ecec0cbdc8429544b7732b459e8d)

Changelog v3.0a

  • Samsung JB N8020 sources (Linux 3.0.31)
  • updated to kernel.org Linux 3.0.57
  • using XXELLA ramdisk
  • swap support
  • zram support (Android optimized)
  • /proc/config.gz support
  • optimized for size
  • ntfs (rw) support (kernel support only)
  • Forced Fast Charge v1.2a
  • CPU OC up to 1.6GHz
  • Triangle away support
  • dynamic fsync support (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)
  • disabled mali state tracking (AndreiLux)
  • reduce mali utilization sampling timeout (AndreiLux)
  • added SIO scheduler
  • added ROW v4 scheduler
  • black crush fix (AndreiLux/AndiP71)
  • added lulzactiveq CPU governor
  • exynos-mem Exploit fix (AndreiLux)
  • sysfs interface to delay fsearlysuspend (Yank555.lu, base idea Codeworkx)
  • 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 (MD5 85d731d4cc295bdd1a161bd16da74477)

======================================================
This kernel contains the sudden death fix as of v3.0a
and the exynos-mem fix as of v2.8c.
Kernels up to v3.4f will only work on Samsung 4.1.2 firmwares.
Kernels starting from v4.0 will only work on Samsung 4.3 firmwares.
None of the kernels will work on leaked 4.2.x firmwares.

==================================================


----------------------------------------------------------------------------------------------------------
Important : Should I have given wrong credit, please PM me, I'll update asap.
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: 3520
Joined: 11 Mar 2013, 20:51
Has thanked: 924 times
Been thanked: 4608 times

Re: [2013/MAR/03][Update 8][3.0.67] Yank555.lu kernel v3.3

Postby yank555 » 12 Mar 2013, 20:33

Changelog And Download Links For Older Versions (prior to v3.0)

OK, let's get down to business, what's in the kernel, what's the installer let you do and most importantly, where to download the kernel.

Changelog v2.8g

  • updated ramfs to XXELLA firmware (removed recovery flash service from init.rc)
  • reverted preliminary exynos-mem exploit fix
  • added whitelisting exynos-mem exploit fix (credits to AndreiLux and AndiP71)

  • Download link (MD5 985f447d01ce48f3248f048f2caefa51)

PS: To be able to record videos on 4.1.2 ROMs, flash this fix (= green camera fix, so if you already flashed it, no need to flash anything).

Changelog v2.8f

  • added support for XBOX 360 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 (MD5 7a505039f4f06a0e59c2616e2aaf401a)

PS: If you get the green camera bug on 4.1.2 ROMs, flash this fix.

Changelog v2.8e

  • 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 100
      • Fastcharge : enabled, 1000mA USB & AC
      • Soundlevel : speaker +3, stock for headphones
      • Dynamic fsync : enabled
      • CIFS kernel modules : enabled
      • Flash : ask
      • init.d support : yes


  • Download link (MD5 aa8204155a7d359d6d231a5d837d6d02)

Changelog v2.8d


Changelog v2.8c


Changelog v2.8b (never released)

  • updated ramdisk to Samsung 4.1.2 firmware
  • added cifs support (kernel module)
  • 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 !)
  • 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 100
      • Fastcharge : enabled, 1000mA USB & AC
      • Soundlevel : speaker +3, stock for headphones
      • Dynamic fsync : enabled
      • CIFS kernel modules : enabled
      • Flash : ask
      • init.d support : yes

Changelog v2.8a


Changelog v2.8

  • 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 : yes


  • Download link (MD5 925fbc60446e54a322cf7a49cdc9745b)

Changelog v2.7a

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

  • Download link (MD5 4ea9b3f7011cd473e0b923a57371e907)

Changelog v2.7

  • 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 !

  • Download link (MD5 1641b4c8c78b72c87d82a15f5743abc8)

Changelog v2.6


Changelog v2.5


Changelog v2.4c

  • added 'Triangle Away by Chainfire' support [COLOR="Red](NB: If you use int2ext mod, as of this kernel version, you need to flash the version of the mod for "custom kernels")[/COLOR]
  • reverted dynamic cpu_max adjustment introduced on 2.4a (behaviour wasn't intuitive)
  • added dynamic cpufreq_max_limit adjustment according to scaling_max setting (allows 100% respect of user configured limit, while the use of the full frequency range is still available through CPU controlling apps)
  • updated to Aroma 2.56

  • Download link (MD5 59309fa0df9d83f8ebff43f1b0f125f8)

Changelog v2.4b

  • added scaling_available_frequencies sysfs interface

  • Download link (MD5 40939ff66d1338b736df49f5343a14ee)

Changelog v2.4a

  • added dynamic cpu_max adjustment so CPU apps trying to set freq. above max. freq. will not be able to

  • Download link (MD5 ea59839a455e858767d883d0c4e543a0)

Changelog v2.4

  • added asynchronous PPP support in kernel (needed for asjkl)
  • removed PPPoE support in kernel (not needed afterall)
  • limited cpu freq. table to disbale freq. above CPU max to avoid using higher freq. at any time (even few seconds) - This will impede setting freq any higher than chosen in Aroma, even with SetCPU/System Tuner ..., except by changing the value in /sys/power/cpufreq_max_limit !
  • /sys/power/cpufreq_max_limit now set by Aroma script to limit CPU frequency from using more than what user wants (usage up to 1.4 during boot is normal even if lower CPU max. chosen in Aroma)

  • Download link (MD5 32d1ebe063d013c00b1a692fb3d3b84e)

Changelog v2.3


Changelog v2.2a

  • Forced Fast Charge v1.2a : (sorry forgot something :()
    • custom fast charge for usb now possible up to 1000mA/h (as per request by bcky84)

  • Download link (MD5 941e2262201244bfee9ddcda5ca70f0a)

Changelog v2.2

  • added dynamic file sync by faux123 setting in Aroma
  • Forced Fast Charge v1.2 :
    • custom fast charge for ac now possible up to 1500mA/h (as per request by bcky84)
    • added failsafe for custom current that can be disabled so that ANY value up to 2100mA/h is accepted as custom AC / USB current. This is only available manually through the sysfs interface (set /sys/kernel/fast_charge/failsafe to 0 to unlock) and not in Aroma, use at your very own risk and only if you really know what you're doing ! (as per request by bcky84)
  • added PPPoE support in kernel (as per request by asjkl)

  • Download link (MD5 8353034c593a7dfd1a59a3d9674b12b5)

Changelog v2.1


Changelog v2.0

  • rebased on Samsung JB update 6 sources (Linux 3.0.31)
  • updated to kernel.org Linux 3.0.49
  • merged with Yank555.lu v1.7 adding all goodies up to what we have in v1.7 !

  • Download link (MD5 77849b6857bab0f37df06ee2c052d30e)

Changelog v1.7b

  • added swappiness setting in Aroma for virtual memory so you can choose it, for hardswap and for zram as well (hardswap used to set swappiness to 100)
  • the kernel is unchanged still v1.7

  • Download link (MD5 a41e19581f65a133192640a07806b0ec, reuploaded 2393af976207a90020fc2418861bb4e4)

Changelog v1.7a

  • added /system/etc/init.d folder creation if it does not exist (only when selecting init.d support = yes)
  • the kernel is unchanged still v1.7

  • Download link (MD5 262560842b3da3a1a9f46be968a5d15b)

Changelog v1.7

  • updated to kernel.org Linux 3.0.48

    But use with great care, the changes to get past 3.0.39 were quite tricky, so keep your eyes wide open and report anything strange. Thanx !

  • Download link (MD5 b7517f31d90f22b0b80db5761bdefa05)

Changelog v1.6a

  • added option in Aroma for init.d support by kernel/ramdisk
    But use with great care, executing the scripts twice (once by kernel/ramdisk and once by ROM) may be a problem ! So know what you're doing, you have been warned ;)
  • the kernel is unchanged and will still display v1.6, if you have v1.6 already you only need to flash this if you need to add init.d support
  • I reuploaded v1.6a with LMK defaulting to "not set here" as using Medium without swap induces slight lag (if you use swap, you can manually select Medium to get back to the previous default)

  • Download link (MD5 e2b3392d58e401cbf21546e8fda2491a, reuploaded bd255de596ed1051c4cd361b41eeacbb)

Changelog v1.6

  • mdnie: custom settings - Includes hardcore sharpnes fixes, and black gamma curve adjustment for black crush (AndreiLux)
  • used more "conventional" default Aroma settings

  • Download link (MD5 a304370b2d9b4f771b6884ac1847a8ee)

Changelog v1.5a

  • removed busybox binaries, hoping to find all I need in recovery (incompatibilies with TWRP Recovery)
  • the kernel is unchanged and will still display v1.5, if you have v1.5 already no need to flash this

  • Download link (MD5 e2ccfd0b1029f73488f1ec563e336208)

Changelog v1.5

  • added Aroma installer with script generator, allowing to customize the following kernel settings when flashing :


    • CPU maximum frequency (underclocking down to 1.0GHz and overclocking up to 1.6GHz)
    • Consider I/O as CPU load
    • MMC I/O (scheduler & readahead buffer size)
    • Android Low Memory Killer
    • Virtual memory (hardswap / zram)
    • Fast charge

  • Download link (MD5 551ac5fba30597d29cd1cd9a133fe9c0)

Changelog v1.4b

  • reenabled Contiguous Memory Allocation (introduced by Samsung on JB)
  • disabled mali state tracking (AndreiLux)
  • reduce mali utilization sampling timeout (AndreiLux)

  • Download link (MD5 41c15a25441a89f76a145a0f2c21ffd5)

Changelog v1.4a

  • disabled Contiguous Memory Allocation (introduced by Samsung on JB)

    NB: Just a test on my end to compare with and without, will be added
    again in future releases.
    Available user RAM drops back to ICS (779Mb) instead of JB (833Mb)

  • Download link (MD5 b2aca2ed5ae3e625db1d76afc09f66bc)

Changelog v1.4

  • update ramdisk to ARHD 12.0 (mike1986)

  • Download link (MD5 921d7032c92f8a1f3a7d86a7100944f0)

Changelog v1.3b

  • default CPU frq 1.4GHz (max. 1.6MHz) (Yank555.lu)
  • removed zram activation from init.rc (Yank555.lu)

  • Download link (MD5 d3ee1f51e2f8e22cc3b3a1010f663a24)

Changelog v1.3a

  • zram support (Android optimized)

  • Download link (MD5 dd952ae06577cec20db3844449523028)

Changelog v1.3

  • 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)
  • ntfs (rw) support (kernel support only)

  • Download link (MD5 36217e97f72b6033eb5eb9b5c5ba4acc)

Changelog v1.2

  • new dynamic sync control (faux123)

  • Download link (MD5 6078cffb434c20f753e48ea37d7834d9)

Changelog v1.1

  • OC up to 1.6GHz (Yank555.lu)
  • USB forced fast charge (Yank555.lu)

  • Download link (MD5 41ac8f59a76abcb718549266d1935633)

Changelog v1.0.38

  • updated to kernel.org Linux 3.0.38

  • Download link (MD5 17170c7c0b6b858d75df2f76ca0dca62)

Changelog v1.0.35

  • updated to kernel.org Linux 3.0.35

  • Download link (MD5 999a10e51c783a4d79b8ce5d1805ef7e)

Changelog v1.0

  • Samsung JB update 5 sources (Linux 3.0.31)
  • using ARHD 11.0.0 ramdisk (mike1986)
  • swap support
  • /proc/config.gz support
  • optimized for size

  • Download link (MD5 0d3324f9e1629588105e34cbe9b63a5c)
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: 3520
Joined: 11 Mar 2013, 20:51
Has thanked: 924 times
Been thanked: 4608 times

Re: [2013/MAR/03][Update 8][3.0.67] Yank555.lu kernel v3.3

Postby yank555 » 12 Mar 2013, 20:33

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 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 ;)

  • CRT off display delay

    For those who fancy using a CRT off mod, this is a way to tell the kernel to not turn the screen off as quickly, so that there's enough time to display the CRT off animation.

    So if you don't see the animation, or only part of it, increase this. Often, I've been told, 100ms is enough, but sometimes it isn't, so you need to try it out for yourselves. CyanogenMod uses a 500ms daly btw.

  • 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.

  • Fading notification LED

    To stay with CyanogenMod, they use a mod that replaces the notification LED blinking by a fading. If you don't quite get the difference, fading is shown in this youtube video (move forward to 0:30, it's not on an SGS3, but you'll get the picture).

    Since I've been on CM10 for a while, and am back on Sammy ROM in the meantime, I did miss that fancy little mod, so when someone asks to add it, I just did :D

    Only drawback, at least for now, is that stock Sammy apps like SMS, of low battery warning will still blink, they seem to access hardware from userspace there :eek:

  • 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: 3520
Joined: 11 Mar 2013, 20:51
Has thanked: 924 times
Been thanked: 4608 times

Re: [2013/MAR/03][Update 8][3.0.67] Yank555.lu kernel v3.3

Postby yank555 » 12 Mar 2013, 20:33

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 ;)

  • I use int2ext mod and since I flashed this kernel I lost access to my external sdcard ?

    You most likely are coming from using a custom kernel, and thus on [url="http://forum.xda-developers.com/showthread.php?t=1772234"]the int2ext MOD OP[/url] you chose one of the two files of the MOD for custom kernels (depending on the fact if you use exFAT or FAT32).

    Now since this is a close to stock kernel, those scripts will not work, since they assume finding the external card on the wrong device.

    To fix this, you just need to flash the corresponding file of the MOD for stock kernel with init.d support

    And as you have just read above, if you use an exFAT formated card, that will not work with this kernel, I'm afraid.

    As of Yank555.lu v2.4c, you need to use the version for custom kernels, adding support for Triangle Away has made the devices shift.

  • 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: 3520
Joined: 11 Mar 2013, 20:51
Has thanked: 924 times
Been thanked: 4608 times

Re: Απ: [2013/MAR/03][Samsung ROMs] Yank555.lu kernel v3.3

Postby sotmax » 12 Mar 2013, 21:05

Very nice kernel my friend ;)

) ) ) over the air on N4 ( ( (
Be friendly and if you dont know try to learn..
User avatar
sotmax
 
Posts: 12
Joined: 12 Mar 2013, 20:57
Has thanked: 1 time
Been thanked: 36 times

Re: [2013/MAR/09][Samsung ROMs] Yank555.lu kernel v3.3a

Postby Mingo3k » 13 Mar 2013, 07:56

Very glad you still continued your Kernel :)
Downloading now
Mingo3k
 
Posts: 1
Joined: 13 Mar 2013, 02:10
Has thanked: 0 time
Been thanked: 2 times

Re: [2013/MAR/09][Samsung ROMs] Yank555.lu kernel v3.3a

Postby corrsea » 13 Mar 2013, 08:05

Great to be here at the beginning.
Already subscribed as a favourite.
You can't keep a good Kernel down ;)

Sent from my SGS3 using Tapatalk
ROM Sotmax Ultimate V15
Kernel Yank555.lu-V3.3a
corrsea
 
Posts: 43
Joined: 13 Mar 2013, 01:58
Has thanked: 24 times
Been thanked: 18 times

Re: [2013/MAR/09][Samsung ROMs] Yank555.lu kernel v3.3a

Postby yank555 » 13 Mar 2013, 10:58

Honestly, I'm glad to be out of xda, and that unproductive climat of fighting and trolling instead of working together.

This way, the energy I have goes where it belongs, the kernel, not fighting iditos :oops:

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: 3520
Joined: 11 Mar 2013, 20:51
Has thanked: 924 times
Been thanked: 4608 times

Re: [2013/MAR/09][Samsung ROMs] Yank555.lu kernel v3.3a

Postby Kung-Fu-Tse » 13 Mar 2013, 14:50

Yeahaaaaaaaaaaaaaaaaaaa :lol:

Hi my friend Image

extremely beautiful to hear from you and you continue to work for this great kernel Image

works (v3.3a) great on "Omega v43.1 Jelly Bean 4.1.2" :ugeek:
Image
Samsung Galaxy S III GT-I9300 Int.: v3.0.78 (Yank555) (Boeffla), CM10.1 / Stock (+ JKay Deluxe), PhilZ Touch CWM v6.0.3.2 / TWRP 2.5.0.0
Samsung Galaxy S II GT-I9300 Int.
User avatar
Kung-Fu-Tse
 
Posts: 9
Joined: 13 Mar 2013, 14:23
Has thanked: 71 times
Been thanked: 4 times

Next

Return to Kernels

Who is online

Users browsing this forum: No registered users and 1 guest

cron