Jump to content
Melde dich an, um diesem Inhalt zu folgen  

Galaxy Nexus - ZenSERIES [JB][Linaro] **Entwicklung eingestellt**

Recommended Posts





Build Infos

  • 3.0.52 is the latest from Google source with upstream merges from 3.2/3.4/3.5
  • Built from 4.7gcc Linaro HighSpeed ToolChain
  • 384/1230Mhz CPU - InteractiveX/Deadline Default
  • 384MHz GPU clock speed

Verfügbare Takte

  • Overclocking/Undervolting/Overvolting
  • 192MHz/230MHz
  • 384MHz (default)
  • 576/729MHz/1036MHz
  • 1230MHz (default)
  • 1305MHz/1420MHz/1536MHz
  • 1612MHz/1766/1804MHz

verfügbare Governors

  • InteactiveX (Default)
  • Interactive/Pegasusq
  • Ondemand/Intellidemand
  • Performance/SalvagedZen
  • Conservative/Userspace
  • Powersave/Lazy

verfügbare Schedulers

  • Deadline (Default)
  • SIO/Noop
  • Cfq/Bfq

zusätzliche Features

  • Color Contrast Control
  • Vibration/Sound/Temp/Fsync/Color Control, BL Extender Support
  • Cpufreq tweaks (ondemand sleep/wake logic -> interactive faster+ more
  • Aggressive Scaling, Interactive, InteractiveX, Ondemand tweaks
  • Some MM/cpu scheduler sysctl tweaks, increased max readahead
  • Userspace undervolting support
  • v3.1-ck2 (all except for BFS and BFS related)
  • Compass fix for toroplus
  • Built with some basic optimizations, auto vectorization flags, neon instrinsics
  • +softfp, mtune=cortex-a9.
  • Several pmap PM cleanups/updates Several smartreflex cleanups/updates
  • Smartreflex disabled on 1420+ frequencies for stricter voltages



Android 4.1.x

















Android 4.2.x















Entwickler: androiddeveloperalliance (https://androiddeveloperalliance.org/)

Original Kernel Thread: https://forum.xda-developers.com/showthread.php?t=1958143

bearbeitet von freedroid

Diesen Beitrag teilen

Link zum Beitrag



- v3.0.58

- More sysctl tweaks.

- Misc. fixes (anarkia/imoseyon)

- Interactive+ZenX upstream updates

- ZenX updated from v2.1-v2.2 (re-worked a lot of hotplugging handling in the timer, other improvements.

- see https://github.com/AndroidDeveloperAlliance/ZenKernel_TUNA/commit/32e1f3ff8b62a4214949295d639bc6b5c852079d for details)


- Rebased the tree for sanity and to fix a bunch of slop bugs.

- Several cleanups and misc. fixes.

- Added ROW I/O scheduler and made it default.

- Updated ZenX to v2.1 (code improvements, infinite CPU support)

- More block layer updates

- Sysctl tweaks

- Some more wifi updates


- Updated to v3.0.57

- Some arm v7 updates

- Multiple interactive governor updates

- Zen I/O scheduler bug fix in add_request

- WiFi bcmdhd: merge in a couple wakelock fixes

- Cleaned up zip template and scripts.

- Replaced 192MHz and 230Mhz with 218.88MHz frequency.

- ZenX v2:

- Complete Rewrite

- Hot(un)plug logic is now determined on the per-CPU timers.

- Hot(un)plug logic performance improvement is substantial over ZenX v1.

- Eliminated racy calling of the hotplug workqueue.

- Support up to 8 CPUs (unplug_load_cpu3 replaced with unplug_load_cpumore, which is for CPUs 3-7)

- Actual cpu_up and cpu_down work is performed in separate workqueues that play mostly dumb (does exactly what the timer tells them to do)

- Removed insert_delay and unplug_delay

- Implemented hot_remove_sampling_periods and hot_add_sampling_periods.

- Now if average CPU load after hot_add_sampling_periods is > unplug_delay_cpu{#} the CPU will be removed. 20 sampling periods should be about a ~400 millisecond delay before adding a CPU.

- Now if average CPU load after hot_remove_sampling_periods is <= unplug_delay_cpu{#} the CPU will be removed. 20 sampling periods should be about a ~400 millisecond delay before removing a CPU.

- Use a longer-term load calculation for hot(un)plugging.

- ZenX will tune certain values on suspend for power savings and revert them on wake (go_hispeed_load, timer_rate, hot_add/remove_sampling_periods).

- ZenX sends a boost pulse on device wakeup (target higher frequency for a short time/80ms default)


- ZenX SoD Hotfix

- Multiple misc. wifi fixes

- Some other misc. fixes, a couple scheduler fixes backported to v3.0 by faux

- Some more adjustments to the lower-end voltages/margins. One of the mid-higher range voltage steps was wrong

- Several improvements in the kernel config.

- Fix some scripting issues, typo in sysctl.conf, don't rely on the sysctl binary to set sysctl values*

- Many roms don't have it, helps with permissions for min/max/governor, and other misc*

- Deprecated zeneractive

- Added ZenX (zeneractive v2)

- Fixed rare SoD (phone alive & accessible, but perm. suspended state) bug that was present on zeneractive

- The hackiness of total_below/above_unplug_time arrays got the axe. Now we actually set and use the data set on each CPU as we should have all along.

- Ditto last_time_above/below_unplug_time

- We now calculate the average load across _all_ ONLINE CPUs instead of using the potentially incorrect current CPU load

- On device wakeup, all cores are forced to wake up

- XXX Quirk! If you are on pegasusq/hotplug/ZenX and you change governor to a non-X gov including*

- Ondemand/interactive/intellidemand/performance/adaptive/conservative* _while your second core is OFF_, it will never re-enable itself

- This only applies if you change your governor while the core is removed

- Workaround: I added a helper script, so, as root, you can just run "set_core_online" to manually re-up your CPU (you only have to do this once)

- This is a pretty rare case, and if your governor is set on boot - this won't affect you anyway!


- Updated to v3.0.56 upstream

- SoD work, Adjusted SR margins and voltages

- Replaced glados' color control with the CM/voodoo color control port

- Re-added some SR updates that were lost in v12

- Added some misc. updates/some from android-3.4

- Interactive upstream updates

- Decreased 512MHz GPU voltage slightly

- Zeneractive: upstream updates, also added tracing, boost, and boostpulse

- Zeneractive: Re-introduce set_speed_mutex*

- Prevents hotplugging from occuring while frequency scaling occurs*


- Updated to v3.0.55

- Rebased the whole kernel tree to clean up

- Updated bcmdhd+ipv4 with some upstream fixes/wakelock related

- Disabled merging on deadline and no-op

- Added in some more TCP congestion schedulers (cubic still default)

- Some misc. updates - More SoD Actions taken

- Replaced interactiveX with "Zeneractive." (documentation: https://pastebin.com/UrkEke8k)

 - Interactive-based governor with "live" CPU hot plugging.

 - Behavior on Zeneractive with Great Battery:

 - If CPU load is <= unplug_load[cpu] for a given CPU for time = unplug_delay, that CPU will be removed (if online)

 - If CPU load is > unplug_load[cpu] for a given CPU for time = insert_delay, that CPU will be inserted (if offline)

 - Tunables: unplug_load_cpu1 (default: 25%), unplug_load_cpu2 (default: 60%), unplug_load_cpu3 

- Zeneractive (default : 75%), unplug_delay (default: 5s), insert_delay (default: 30ms)


- Reverted some DSS+OPP & SR adjustments (May fix SoD some users are experiencing)

- Raised default screen_off_freq to 729.6MHz

- Added 512MHz GPU clock setting (512 in progress for some users)

- Available GPU options are 307/384/512 (384 still default)

- Re-did ondemandX (suspend/wake code + CPU hot plugging)

- Added adaptiveX governor, adaptive with suspend/wake code + CPU hot plugging

- Added intellidemandX governor, intellidemand with suspend/wake code + CPU hot plugging

- New list of governors with early suspend/wake/hotplugging*

- InteractiveX, pegasusq, adaptiveX, ondemandX, intellidemandX

- 4.0/4.1 kernels will progress maybe another few builds for stability                                                   


- Hotfixes for Maximum Stability

- Two Versions 

- ZenSERIES 4.1 

- ZenSERIES 4.2 

- Fixed PGM support

- New Adaptive Governor by Samsung

- Fixed Tethering & WEP by reverting back to 3.0 wifi drivers

- NEW modified version of imoseyons sysfs for GPU UC/OC @307/384*

- GPU OC changes live using TricksterMOD to clock GPU's* - 512 will show but Currently Inactive

- Reverted to the latest Interactive/InteractiveX with the proper scaling fixes

- Fixed apps setting min/max frequencies sticking upon reboot for some users

- ZenSERIES 4.1 Fil Updated Build Changelog:

- All of v9/v10 major changes below are included - Exeption is different bluetooth drivers

- Enjoy!


- Updated to v3.0.53 Latest Upstream Google Source

- Added in some additional omap-specific fixes

- Pulled in the core block layer from axboe/linux-block.git up to 3.3. Includes the following:

  - https://git.kernel.org/?p=linux/kernel/git/axboe/linux-block.git;a=shortlog;h=refs/heads/for-3.1/core

  - https://git.kernel.org/?p=linux/kernel/git/axboe/linux-block.git;a=shortlog;h=refs/heads/for-3.1/drivers

  - https://git.kernel.org/?p=linux/kernel/git/axboe/linux-block.git;a=shortlog;h=refs/heads/for-3.2/core

  - https://git.kernel.org/?p=linux/kernel/git/axboe/linux-block.git;a=shortlog;h=refs/heads/for-3.3/core

- Updated BFQ to for-3.3 version to reflect it

- SOD issues should now be fixed

- Added FIOPS v2 I/O scheduler

- Added logic to cpufreq_set_policy so it only sets policies with a valid min/max frequency*

- Vs any min/max frequency within the range*

- Adjusted Ondemand/OndemandX/Intellidemand/Pegasusq settings

- Updated wifi drivers to 3.4 ones

- Enabled frontswap and cleancache

- Added script to apply some fstab tweaks to current roms ramdisk (mount with noatime+disable barriers)

- Applied zRam updates

- Added ZRAM_FOR_ANDROID (Optimizes zram for android, adds bits to zram+lowmemorykiller)


- Two Versions 

- Final ZenSERIES 4.1 build 

- Ongoing support for ZenSERIES 4.2

- Updated Base to 3.0.52 Latest Upstream Google Source

- Fixed deep sleep on 4.2 ROMS

- More core build optimizations

- Updates from the android-3.0 tree

- More conservative default cache_pressure


- Now should be Compatible with 4.0/4.1/4.2 ROMS

- Merged in latest 4.2 Source tuna+omap updates

- Revert to using stock ramdisk for capability

- Pegasusq tweaks, some suggestions from EniGmA1987

- Set CPU_DOWN_FREQ to cpu frequency policy minimum on pegausq

- Set sysctl values via script, overrides anything set by ROMS Ramdisk initially

- To remove, rm /system/bin/set_zen_sysctl and /system/etc/init.d/99ZenKernel

- Deep Sleeping was more ROM Related vs Kernel - v7 has worked on our end

- Fixed Zram & CPU Sticking


- Added a New Custom Ramdisk Rewritten with Zen settings

- Ramdisk originally pulled and modified from leanKernel 

- Sysctl settings won't be overridden by rom's default ramdisk now

- This should fix any lag/idle slowdowns that were minutely present

- Modified CPU scheduler settings

- Modified sysctl settings for the "Zen-Tune" branch settings

- Now matches what is set by the ramdisk just for easier reference

- More upstream lowmemorykiller updates

- Updated Interactive & InteractiveX using latest upstream from android common

- Added Brand New 4.2 Ramdisk by Google's Kernel Source *Testing Phase*


- Rebased Entire Kernel - Cleaned up all code in source

- More sysctl tweaks, min_free_kbytes is now at ~4Mb by default

- Added OndemandX Governor

- Added ZRAM Support

- Fixed OC issues for some users by enabling trim quirks

- Updated lowmemorykiller to latest from ~3.6

- Updated OPP driver to latest from ~3.6

- Adjusted intellidemand default settings to match our ondemand ones

- Some omap DSS fixes

- Reduced android logger ram usage (dorimanx)

- More accurate nohz load accounting (dorimanx)

- More tweaks by default 

- Dirty_expired_centisecs -> 200, vm_dirty_background_ratio - >

- 60, sched_nr_latency -> 10, sched_min_granularity -> 

- .4msec, sched_latency -> 3ms


- Breaking Ground *Serious Kernel Power*

- Built with a more vanilla crosstool-built gcc 4.7.2 instead of Linaro* 

- Should solve affected Chrome users & any remaining boot issues*

- Fixed 384MHz Maximum GPU Frequency 

- Updated to v3.0.51

- Adjusted CFLAGS

- Raised default vfs_cache_pressure from 20->30

- Re-added some incidentally removed PM updates

- Lowered fifo_batch to 1 on deadline/SIO/zen/V(R) as it may be most desirable for flash memory

- Set cpu transition latency back to 30ms

- Slightly increased voltages for 1.4-1.7~GHz frequencies

- Proprotional rate reduction for TCP

- Westwood as default TCP congestion scheduler

- Thalamus' updated target residencies

- Zen I/O scheduler is now default

- A couple cleanups to Zen I/O

- Adjusted default lowmemorykiller minfree, for min ~80Mb. 

- 2048/3072/6144/15360/17920/20480


-Added cleaner.sh script to zip template & runs in the updater-script 

-Thoroughly cleans any & all remaining kernel scripts

-Should fix issues for users who can't boot the kernel

-Added Zen Info sysfs interface for future usage

- Latest Upstream v3.0.50

- Added back in screenoff_maxfrequency support*

- *Defaults to 576MHz - Should solve wakelocks/wake issues

- Removed rev_penalty even though it's the main feature of VR 

- Also removed logic based on choosing request *

- *Depending on head because our phones don't have spinning hard drives.

- Added +10mV to 192/230Mhz frequencies

- Reverted some memory patches that were problematic

- Added "Zen" I/O scheduler.

 * Based primarily off of no-op, but also VR. Very similar to SIO.

 * Primarily FCFS, dispatches back-inserted, deadlines ensure fairness between requests.

 * Synchronous requests chosen over asynchronous ones

 * Even simpler than the "Simple I/O scheduler"

bearbeitet von freedroid

Diesen Beitrag teilen

Link zum Beitrag


ich hatte den Kernel vor ein paar Tagen mal am laufen. War nicht sonderlich zufrieden. Hatte auch zwei unfreiwillige Reboots, was sonst fast noch nie bei mir vorkam.

Diesen Beitrag teilen

Link zum Beitrag

Ich hab ihn seit letzter Woche mit einem Neuflash von rasbean drauf. Läuft bei mit super.

Deshalb dachte ich, ich will den der Community nicht vorenthalten ;)

Diesen Beitrag teilen

Link zum Beitrag

Vielleicht teste ich nochmal eine neue Version :-)

Welche Vergleiche kannst du zum Trinity ziehen?

Diesen Beitrag teilen

Link zum Beitrag

Bei mir läuft der wirklich gut. Mir kommt es so vor, als ob er sogar einen Tick flotter läuft als der Trinity A67.

Diesen Beitrag teilen

Link zum Beitrag

Update auf ZenSeries v3.1 erschienen

Download siehe Post #1

Changelog siehe Post #2

Diesen Beitrag teilen

Link zum Beitrag

Falls es jemand interessiert hier mal ein paar Einstellungen für den Kernel, die bei mir super sind.

Eingestellt mit Trinity Toolbox


Min. Takt: 384 MHz

Max Takt: 1230 MHz

Governor: pegasusq

Scheduler: Deadline


Kontrast: -10

Farb Multiplikatoren: Rot 140, Grün 140, Blau 195

Diesen Beitrag teilen

Link zum Beitrag

Hab ähnlich eingestellt. Schauen wir mal was der Kernel leistet.

Diesen Beitrag teilen

Link zum Beitrag

Hab ihn mir auch gestern Abend draufgemacht und bin eigentlich sehr zufrieden.

Mit dem Pegasusq-Governor bin ich schon immer gut gefahren. Das ist der vom SIII oder?

Diesen Beitrag teilen

Link zum Beitrag

Ja genau. Der pegasusq wurde vom S3 übernommen.

Diesen Beitrag teilen

Link zum Beitrag

Update auf ZenSeries v4.0 erschienen

Download siehe Post #1

Changelog siehe Post #2

Diesen Beitrag teilen

Link zum Beitrag

Nutzt du schon die neueste Version? :-)

Gesendet von meinem Nexus 7

Diesen Beitrag teilen

Link zum Beitrag

Ja hab die gleich nach erscheinen geflasht. Läuft insgesamt gut. Ich musste jedoch den Scheduler von ZEN auf SIO umstellen. Beim ZEN hatte ich gelegentlich ein leichtes Ruckeln beim öffnen von Apps.

Diesen Beitrag teilen

Link zum Beitrag

Update auf ZenSeries v6.0 erschienen

Download siehe Post #1

Changelog siehe Post #2

Diesen Beitrag teilen

Link zum Beitrag

Auch schon für 4.2 verwendbar. Ging sehr flott :-)

Diesen Beitrag teilen

Link zum Beitrag

Update auf ZenSeries v7.0 erschienen

Download siehe Post #1

Changelog siehe Post #2

Diesen Beitrag teilen

Link zum Beitrag

Please sign in to comment

You will be able to leave a comment after signing in

Jetzt anmelden
Melde dich an, um diesem Inhalt zu folgen  

  • Neu erstellen...

Wichtige Information

Bitte beachten Sie folgende Informationen: Nutzungsbedingungen und Impressum & Datenschutzerklärung. Wir haben Cookies auf deinem Gerät platziert, um die Bedienung dieser Website zu verbessern. Du kannst deine Cookie-Einstellungen anpassen, andernfalls gehen wir davon aus, dass Du damit einverstanden bist.