Features (changes compared to Perseus):
- updated Linux Kernel base to 3.0.81
- DevilQ cpu governor (default)
- block updated from Linux 3.3 (better i/o performance)
- row i/o scheduler updated from Linux 3.4
- fiops v2 i/o scheduler
- working for Aosp and Sammy at once (Big thx to Gokhanmoral for making this possible)
- Portet Ezekeel's Touchwake Feature (from nexus s)
- Oc up to 2 Ghz
- using Joe RCU
- Backport from Linux 3.5 smp driver parts
- Cm Wifi driver (from D2 Linux 3.4 kernel)
- possibility to set high/low power mode for wifi when screen is off
- LulzactiveQ cpu governor (from siyahkernel, thx again to Gokhanmoral)
- Hotplug Cpu Governor
- Proportional Rate Reduction for TCP http://kernelnewbies.org/Linux_3.2#h...7963f165302b6e
- improve memcopy/memmove
- Using Voodoo Sound
- mdnie: toggling mdnie negative effect with home button (Gokhanmoral)
- Reverted LED Control
For more detailed instructions, please take a look at this thread from RichMd (thank you for it): Dualboot Faq thread
Important: if you want to use this kernel for dualboot, i highly recommend flashing my recovery as well.
General information about the recovery:
- the recovery does not mount /cache, /system or /data by default. if you want to perform any file modifications to either of your roms (wiping data, create/restore nandroid, fixing permissions,...), you have to use the dualboot menu before.
in this menu you can:
* create the secondary system partition (needed to be run once, if you want to install a second rom)
* enable mounting of primary filesystem
* enable mounting of secondary filesystem
if you have enabled the mounting of one of the filesystems, all the actions mentioned above are performed to the filesystem you selected. this filesystem stays the active one, unless you reboot to recovery, or you select the other one.
you'll notice there is a new menu, where to select what you want to flash.
if you select kernel, rom or recovery, the zip gets installed as it is.
if you select zipt to pri./sec. filesystem, it is selfexplanary
if you select rom to secondary fs, the zip gets modified to install to the sec. fs. IF YOU WANT TO INSTALL IT TO PRIMARY FS LATER SOME TIME, YOU NEED TO REDOWNLOAD THE FILE!
if you select rom to primary filesystem, it gets installed there, and you can use the same zip later again.
How to install a second rom:
make sure you have already created ssecondary system partition! if not, go to dualboot menu and create it now (this may take some minutes)
The savest way is the way by using nandroids: if you don't have a nandroid already, create one now. Go to dualboot menu, enable mounting of primary fs (look above for details), go to nandroid menu and make your nandroid.
go back to dualboot menu, enable mounting of secondary fs, then go to nandroid menu, and restore your backup.
you now should already be able to boot into primary or secondary rom (which are both the same now).
now you can install any other rom as primary.
if you want to install a new rom directly as secondary, make sure there are no spqaces in the filename!,
then just go to install zip. you'll notuice there's a new menu at some point.
in this menu you can select where you want to install, and what type of file it is.
if you choose rom to sec. fs, your zip files itself gets modified to be installed to secondary fs. this may take a minute, because the files needs to get zipped again. Imporant: this file is permanently modified. if you think you need it later again, you should redownload it, because the modified one would always install as secondary.
installing a rom as primary, a zip to primary or secondary fs, does not modify the zip.
roms coming with an aroma installer are hard to handle, as every dev can place own commands into it. It's impossible for me, to take care of every possibility. Because of this, it should be the best method, to flash a rom with aroma installer as primary one (and then move it to secondary, by using the nandroid method, if you want it to be secondary).
- linux 3.0.81
- fixed internal storage on 4.2.2 secondary roms
- reverted cpufreq driver back to "default", to try fixing being stuck at max. freq for some users
- merged update9 changes from cm team
- wifi changes which hopefully reduce wakeup time
- built nfs as module (was built-in before)
- update to linux 3.0.80
- reverted a commit from 3.0.79 which caused the cpu to be stuck at max. freq
- fix touchwake/proximity sensor for i9300
- cpufreq: fix handling of offline cpus
- dynamic fsync: fixes from faux123, to prevent data loss, in case of kernel panic/unexpected shutdown
- CPU hotplug, writeback: Don't call writeback_set_ratelimit() too often during hotplug (from francisco franco)
- freezer: allow tasks to be frozen faster (1ms if possible, instead of 10 ms)
- freezer: skip waking up tasks with PF_FREEZER_SKIP set, to make suspend/resume more efficient
- t0ltecdma: fixed sprint compatibility
important: please uncheck in deviltools to apply settings on boot! gpu voltage changes would cause the device to freeze on startup!
- reverted gpu voltage to be displayed as before (this fixes incompatibility with trickstermod or other apps)
- DevilQ: turn/keep second core online on screen touch
- add PM_SUSPEND_FREEZE powerr state (if used, it does save little less power, but PM_SUSPEND_FREEZE has less resume latency
•Erik Gilling - sync: don't log wait timeouts when timeout = 0
•Ørjan Eide - sync: Fix race condition between merge and signal
•Erik Gilling - sync: add Documentation/sync.txt
•Erik Gilling - sync: add tracepoint support
•Erik Gilling - sync: refactor sync debug printing
•Erik Gilling - sync: use proper barriers when waiting indefinitely
•Erik Gilling - sync: update new fence status with sync_fence_signal_pt
•Erik Gilling - sync: protect unlocked access to fence status
•Erik Gilling - sync: dump sync state of fence errors
•Erik Gilling - sync: improve timeout dumps
•Erik Gilling - sync: use correct signed type when handling SYNC_IOC_WAIT
•Erik Gilling - sync: dump sync state to console on timeout
•Erik Gilling - sync: clean up compiler warnings
•Erik Gilling - sync: fix erase-o in sync_fence_wait
•Erik Gilling - sync: change wait timeout to mirror poll semantics
•Rebecca Schultz Zavin - sync: Fix error paths
•Erik Gilling - sync: add reference counting to timelines
•Erik Gilling - sync: add internal refcounting to fences
•Erik Gilling - sync: optimize fence merges
•Erik Gilling - sync: reorder sync_fence_release
•Erik Gilling - sync: export sync API symbols
•Erik Gilling - sync: allow async waits to be canceled
- ext4: prevent kernel panic in case of uninitialized jinode
- mutex: dynamically disable mutex spinning at high load Date Thu, 4 Ap… … (faux123)
- mutex: restrict mutex spinning to only one task per mutex … (Waiman Long)
- mutex: Make more scalable by doing less atomic operations … (Waiman Long)
- hrtimer: Prevent enqueue of hrtimer on dead CPU When switching the hr… … (franciscofranco)
- hrtimer: Consider preemption when migrating hrtimer cpu_bases When sw… … (franciscofranco)
- fs/buffer.c: remove redundant initialization in alloc_page_buffers() … … (clouds-yan)
- time: cast ->raw_interval to u64 to avoid shift overflow We fixed a b… … (faux123)
- vmscan: comment too_many_isolated() Comment "Why it's doing so" rathe… … (Wu Fengguang)
- mm/vmscan.c: avoid possible deadlock caused by too_many_isolated() Ne… … (Wu Fengguang)
- input: evdev: Move wake_lock_destroy call … (halaszk)
- wakelock: use single threaded workqueueus … (halaszk)
- linux 3.0.78
- added own cpu governor, DevilQ (based off lulzactiveq by gokhanmoral)
- improved touchwake (acting like swipe2wake now, if delay is set to 0, to prevent false wake ups)
- pegasusq: readd some of andreilux's changes
- gpu: allow oc up to 800 mhz
- added option to disable touch boost
- updated wifi driver from s4 (commit by cm team)
- disabled swap, zram and cleancache
- linux 3.0.75
- fixed cam preview on note2 lte
- new tunables for pegasusq:
* early_demand: to enable this functionality (disabled by default). ( echo 1 > sys/devices/system/cpu/cpufreq/pegasusq/early_demand, to enable it. 0 disables it)
* grad_up_threshold: over this gradient of load we will increase
frequency immediately. ( echo xx > sys/devices/system/cpu/cpufreq/pegasusq/grad_up_threshold, to set value. xx has to be betwenn 11 and 100, default 50)
- updated block to linux 3.3
- updated row i/o scheduler to linux 3.4
- added fiops v2 i/o schedler
- readded gokhanmorals sammy/aosp mod more cleanly
- lulzactiveq: small fixes
- cpufreq_pegasusq.c: revert to stock
- Enabled AIO support
- improved aio: Asynchronous I/O latency to a solid-state disk greatly increased between the 2.6.32 and 3.0 kernels. By removing the plug from do_io_submit(), we observed a 34% improvement in the I/O latency.
- added zzmoove governor
* mdnie-control: Digital brightness control
* s6e8aa0: Allow manual brightness to 300 candela
* ARM: decompressor: Enable unaligned memory access for v6 and above
- Fixed patch: "LOAD_FREQ (4.61 s) avoids loadavg Moire (thx to Klaus Ripke)", many thx to AndreiLux for pointing and fixing this
- Added Franciscofranco's Touch Boost Control (input boost frq., when screen touched can be set with trickster mod app), including the additions from simone201, but fixed to not beeing stuck at high freq.
- removed LCDFreq scaling mechanism (using touch boost instead)
- fixed charging while device off
- applied a bluetooth patch from cm (might help with bt issues some users were reporting)
more to come ...
hints and fixes:
- if your pc does not recognize your phone, please try this method, until i know what is causing this behaviour:
Originally Posted by pnxsinned
Is it possible this kernel tries to detect the voltage input on the device and based on that he turns on MTP yes or not? I made through apex -- Activities -- Settings -- USB to PC --> And enabled it manual there. Now it works fine.
Would you like to know one of the things that really annoys me on a daily basis? Tough, … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?