[Kernel] Devil [4.3/4.2.2/4.1.2]- Linux 3.0.101 - Linaro 4.8.2 - Dualboot - 24/10

[DerTeufel1980]

This Kernel is based off the sources of AndreiLux Perseus Kernel (alpha35).
If you consider to thank me, please also consider to thank him http://xdaforums.com/showthread.php?t=1927852

This kernel supports only Samsung 4.1.2 and Aosp based roms up to Android 4.3.1
Android 4.3.x roms need to be installed as primary for now!

Features (changes compared to Perseus):
- compiled with linaro gcc 4.8.2
- updated Linux Kernel base to 3.0.101
-zram, zsmalloc and lowmemorykiller updated from 3.9
- 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
- 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#head-1c3e71416a9fdc2f59c1c251a97963f165302b6e
- improve memcopy/memmove
- Using Voodoo Sound
- mdnie: toggling mdnie negative effect with home button (Gokhanmoral)
- Reverted LED Control
- ExFat support (thx to samsung for opensourcing the driver)

/* if your rom is based off PAC, Bam, Fusion, ... *\
/* Generic framework "framework-2.jar" introduced *\
/* (teamed up with Yank555, Googy, AndiP, Psndna, Temasek), *\
/* this is to get rid of proprietory framework naming conventions *\
/* and come up with an aligned approach between rom and kernel devs. *\
/* For now, specific framework for Pac Man remains added, *\
/* but for a grace period only. *\
/* Those will be removed with the first update after November 10th. *\
/* So please do pass this message along to your favorite ROM devs, *\
/* we will stop supporting additional frameworks with specific ROM names. *\​

Kernel app http://xdaforums.com/showthread.php?p=41346443#post41346443

How to post bugs:
http://xdaforums.com/showthread.php?t=1520508

Dualboot Faq:
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:
dualboot menu.
in this menu you can:
* create the secondary system partition (needed to be run once, if you want to install a second rom)

Install-zip menu:
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. Then just select your backup, and restore it to secondary filesystem.
  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 spaces in the filename!,
  then just go to install zip. you'll notice 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 zip to secondary fs, does not modify the zip.

Additional information:

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

Many Thanks to:
- RichMD
- Gokhanmoral
- Andreilux
- DAGr8
- simone201
- ptmr3
- Stratosk
- RolloS
- kasper_h
- Philz (for his recovery source, although i had to implement my own touch)
- all the others mentioned in the changelogs

 

[DerTeufel1980]

Changelog:
24.10.2013
+ backport interacctive governor from googles linux 3.4 kernel source + enabled it
+ updated zzmove cpu governor
+ cpufreq: Save and restore min and max frequencies.
+ cpufreq: Save user policy min/max instead of policy min/max during hotplug
+ cpufreq: Only apply driver limits for scaling_min/max_freq writes
+ linux 3.0.101 (last update)

22.10.2013
+ revert: zram: use zram->lock to protect zram_free_page() in swap free notify path
+ added support for latest cm nightlies
+ some cleanup by removing non used code

20.10.2013
+ linux 3.0.100
+ added support for pac rom
+ reverted some autohotplug related commits which aren't useful if there are only governors with own hotplug logic
+ reverted cpu oc from 2000 to 1800 (stability testing in connection to undervolting)
+ zram: use zram->lock to protect zram_free_page() in swap free notify path (thx to stsdema28 for suggeting this patch)

09.10.2013
+ linux 3.0.99
+ some patches to improve general swap performance (especially zram)
+ minor update to block kernel subsystem (io schedulers)

03.10.2013
+ linux 3.0.98
+ fixed zram kernel crashes
+ fixed triangle away (thx ckh469)
+ memcopy improvement (also thx to ckh469)

30.09.2013
+ linux 3.0.97
+ added additional sysfs for controling vibration on 4.2.2 roms by using device settings or devil tools
+ zram: re-added code for using multiple cores for (de)compression, which should be significantly faster now
+ zram: upstreamed to linux 3.12
+ zcache: fix booting by syncing code with faux123
+ re-enabled cleancache
+ block/io-schedulers: big update to row and cfq scheduler from linux 3.4 (thx to andreilux for squashing the commits)
+ fixed adb root options after data wipe
+ added options to turn of hardwarekeys backlight on screen touch, thx to yank555-lu (for now, this isn't added to deviltools, please see below for the sysfs path/command)

this doesn't affect samsung roms!
* /sys/class/sec/sec_touchkey/touch_led_handling (rw)
*
* 0 - handled by ROM (newer CM10.2, default)
* 1 - handled by kernel (older CM10.2)
*
* /sys/class/sec/sec_touchkey/touch_led_on_screen_touch (rw)
*
* 0 - hardware keys backlight only lights up if h/w keys are used
* 1 - hardware keys backlight lights up if h/w keys are used or screen is touched (default)

27.09.2013
- updated linux to latest 3.0.96
- Revert "wakelock: use single threaded workqueueus" (supposed to fix android os bug)
- compiled using linaro 4.8.2 gcc
- surprise (many thanks to umberto1978 for this)

18.08.2013
- added exfat support
- linux 3.0.91

10.08.2013
- fixed sysfs of led control to be readable/writable by deviltools
- re fixed mtp/ums and adb root

09.08.2013
- backported zram_for_android from linux 3.4 (i9500) and enabled it again
- updated zram to latest official version (linux 3.11
- updated android binder driver
- added led control by yank555-lu

05.08.2013
- linux 3.0.89
- re-added selinux
- disabled uksm (cam failure on i9300)
- updated/backported zsmalloc, zram and lowmemorykiller from 3.9 (disabled zcache and zram_for_android because of this)
- fixed a bug in ashem driver, caused by samsung, which could lead to deadlocks
- mmc: fix the workqueue overload battery waste (thx to aagit)
- fixed adb root
- fixed mtp/ums issues after wipe

02.08.2013
- Reverted selinux
- better implementation of 4.3 support.

31.07.2013
- updated to linux 3.0.88
- added andreilux's abb control
- updated and activated zram (thx to yank555), zcache, cleancache and frontswap (most probably not very important on note2)
- enabled uksm by default (http://www.phoronix.com/scan.php?page=news_item&px=MTEzMTI)
- added experimental support for android 4.3 (only i9300 for now)
- reduced wifi wakelocks a little bit more

25.0.7.2013
- cpufreq: zzmoove governor 0.6 (thx to zanezam)
- include most of touchwake 1.1 changes. thanks to yank555-lu
- bcmdhd: update back to version used by andreilux. …
big thx to xda forum member gondsman: http://xdaforums.com/member.php?u=3740419 (this should drastically reduce wifi wakelocks)

24.07.2013
- reverted compiler option "optimze_for_size" to fix cam on aosp roms

23.07.2013
- reverted wifi driver to cm version, to fix wifi tethering, additional disabled multicast in suspend for power savings

22.07.2013
- linux 3.0.86
- disable touchwake during call
- se linux support
- wifi driver from andreilux sammy kernel (should reduce wakelocks)


27.06.2013
- linux 3.0.83
- reverted JRcu
- dyn fsync updates from faux123
- two upstream fixes to row i/o scheduler
- added latest cm changes (UMS: f_mass_storage: Added cdrom option to UMS-lun-devices, Samsung i9300 Update 10)

12.06.2013
- linux 3.0.81
- 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)

29.05.2013
- 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

15.05.2013

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)

12.05.2013
- 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

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

27.04.2013
- updated block to linux 3.3
- updated row i/o scheduler to linux 3.4
- added fiops v2 i/o schedler

25.04.2013
- 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

- Andreilux:
* mdnie-control: Digital brightness control
* s6e8aa0: Allow manual brightness to 300 candela
* ARM: decompressor: Enable unaligned memory access for v6 and above


19.04.2013:
- 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 ...

 

[nfsmw_gr]

more to come ...

OMG!
Loved this on the i9000!
It's awesome to see it on the i9300 too!
I've got two questions though...

1)Trickster mod configures everything right now or some things are not configurable?Thanks for the STweaks support too!

2)You mention this is based on perseus...that means that screen calibration is available on devil kernel too right?is it configurable too like on perseus?

Many thanks man! :highfive:

EDIT:
Flashed right now and my questions were both answered.Sorry to spam,but i was on a stable setup and didn't want to ruin it.
This kernel feels fast and smooth!
It rocks man,simply awesome!

EDIT 2:I just finished going through advanced configuration and oc/uv it.
Also i run some benchmarks,everything's good.
No bugs or anything so far too.
Could i make just one wish please?
Don't use the same audio engine perseus uses,it's a bit buggy(atleast for me) and doesn't have many more features than the one used in siyah...plus the latter one runs fine,so keep the one you're using now please.

 

[squirtsy]

Doesn't seem to boot on mcbytes rom without a wipe

Sent from my GT-I9300 using xda premium

 

[nfsmw_gr]

Doesn't seem to boot on mcbytes rom without a wipe

Sent from my GT-I9300 using xda premium

It works fine on ultima v12,i see no reason why wouldn't this work on mcbyte rom...?both are sammy based.
try to flash again mate!

 

[LovelyDay]

Not boot

Report

ARHD 25.0 using Devil Kernel Not boot

kernel Flashing before /data/.perseus delete and wipe cache and Dalvik Cahce

But Not boot

 

[proxuser]

Works fine with grisza monster beam 8.0
Installed with cwm without wipe anything
Sent from my GT-I9300 using xda premium

 

[ghul21]

Hi Dominik

Finally we have u here only thing i'm missing is the sign of the kernel in settings ,see screenshot. And one more, mybe some sharpness tweaks. Or i just miss this in settings thank u for your work :thumbup:

Edit:

Big bug. Using the camera make reboot every time. Trying on two roms, both aosp. With previous kernel no problem

Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2

 

[DerTeufel1980]

Hi Dominik

Finally we have u here only thing i'm missing is the sign of the kernel in settings ,see screenshot. And one more, mybe some sharpness tweaks. Or i just miss this in settings thank u for your work :thumbup:

Edit:

Big bug. Using the camera make reboot every time. Trying on two roms, both aosp. With previous kernel no problem

Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2

Can you please send me the last_kmsg after device booted up again.

Gesendet von meinem GT-N7105 mit Tapatalk 2

 

[Leicxan]

i flashed this kernel,but it doesn't support exfat..

Sent from my GT-I9300 using xda premium

 

[davtse]

Can you please send me the last_kmsg after device booted up again.

Gesendet von meinem GT-N7105 mit Tapatalk 2

Hope this helps. It also crashes when running benchmark applications like antutu benchmark

 

[funeralcrows]

+1 on sticking to Siyah's sound mod. Everything else is just buggy and doesn't really give any better sound.

 

[DerTeufel1980]

updated the op with a new kernel.

- added support for exfat (as long as it is working, it is fine for me. i am not going to miss improvements to keep compatibility to a propietary driver)
- higherd the mem reservation of fimc driver, to hopefully prevent camera crashes

 

[MuertoKo]

updated the op with a new kernel.

- added support for exfat (as long as it is working, it is fine for me. i am not going to miss improvements to keep compatibility to a propietary driver)
- higherd the mem reservation of fimc driver, to hopefully prevent camera crashes

Good to know the "i am not going to miss improvements to keep compatibility to a propietary driver", you might already be aware of this or maybe I missunderstood it some time ago, but I think Andrei ported his kernel to Linux 3.4 (or 3.3??) and added a new i/o scheduler some time ago, but had to revert it back to recover ExFat compatibility... maybe worth cheking!

 

[scheichuwe]

updated the op with a new kernel.

- added support for exfat (as long as it is working, it is fine for me. i am not going to miss improvements to keep compatibility to a propietary driver)
- higherd the mem reservation of fimc driver, to hopefully prevent camera crashes

Camera still crashes.

 

[davtse]

Camera still crashing, and when I try to flash back to my old kernel it bootloops. Flashing back to your kernel allows it to start up again. This is with cache/davik cache wipes.

 

[MuertoKo]

Camera still crashes.

Camera still crashing, and when I try to flash back to my old kernel it bootloops. Flashing back to your kernel allows it to start up again. This is with cache/davik cache wipes.

Please say if you are using CM or Sammy bases if posible (even with a last_ksmg is more than enough), just to let users as well as dev where are the posible bugs and trigger them to solve them with more logs

 

[davtse]

Please say if you are using CM or Sammy bases if posible (even with a last_ksmg is more than enough), just to let users as well as dev where are the posible bugs and trigger them to solve them with more logs

Erm.. I did upload a last kmsg if you notice.
Anyway, on AOSP slimbean rom

 

[scheichuwe]

Please say if you are using CM or Sammy bases if posible (even with a last_ksmg is more than enough), just to let users as well as dev where are the posible bugs and trigger them to solve them with more logs

I already did, but on another Forum. Sorry for this.
Here you are:
stock EMC3
https://www.dropbox.com/s/rc0fdeuueq86wts/last_kmsg.txt.zip

 

[nfsmw_gr]

Hmm..weird things about the camera...
It works fine on my S3 on Ultima v12.