[Kernel] Devil2-2.3.2 [4.4.x, 4.3.x] - f2fs Filesystem - Dualboot - 02/01
- Thread starter DerTeufel1980
- Start date
So it flashes the screen pink when scrolling the screen for example ?
That means that it has working HWCcongratulations!!!!
But that is really strange
as for the sources
this is samsung and will stay the way it is, closed sourced.
and even sony has some crap in this aspect, like when you unlock the bootloader, you lose all the features like "X-loud" and X-Reality
so this is more or less the same attitude....
Anyways, nice to know that Devil3.4_0.5.3 kernel is still up to date, although it wasn't updated recently
unfortunately, after 2hours of standby and opening alot of apps (70apps, since i configure each apps). i was plagued by Lollipop's 5.0.2 inherent memory problems, my phone suddenly comes to a crawl and hangs. mind you this is S3 (E210S) with 2GB memory. So in the end i went back with Temasek CM11+Devil Kernel and call it a day..:good: no more hangs. CM12 is really at its infancy, maybe i'll make a switch after a couple of months or maybe a year maybe at that time it's mature as its older brother CM11 hehe
Open a shell, for example adb shell via adb or terminal emulator app.
Then type: dumpsys SurfaceFlinger
You should see lots of debug stuff and then you should see the current layers, e.g. notification drawer, wallpaper..
At the beginning of each line you will see HWC, GLES or something else I forgot. This will tell you what is being used for which layer. Repeat the dumpsys command several times, since the responsible device for drawing layers will change often.
Then type: dumpsys SurfaceFlinger
You should see lots of debug stuff and then you should see the current layers, e.g. notification drawer, wallpaper..
At the beginning of each line you will see HWC, GLES or something else I forgot. This will tell you what is being used for which layer. Repeat the dumpsys command several times, since the responsible device for drawing layers will change often.
Dual Boot Lollipop and KK
Seeing as how another person got a LL rom to boot with a modified devil kernel, I thought I would try just the unmodified one.
Didn't boot (nor did I expect it to).
However I am dual-booting LL and KK:
I installed a 4.4 rom (Archi 3.02) normally, saved nandroid, and restored to 2nd rom.
Then wipe, and install CM12 into primary. When I want to boot second rom, I boot recovery as normal, flash devil, and reboot secondary.
To go back to 1st, flash appropriate LL kernel, and then reboot primary.
Flashing kernels is very fast, so this only takes a few seconds longer than the regular way of switching, and lets you have LL and KK.
Just thought I'd leave a note in case others want to try out LL without giving up the stability of their regular rom.
Seeing as how another person got a LL rom to boot with a modified devil kernel, I thought I would try just the unmodified one.
Didn't boot (nor did I expect it to).
However I am dual-booting LL and KK:
I installed a 4.4 rom (Archi 3.02) normally, saved nandroid, and restored to 2nd rom.
Then wipe, and install CM12 into primary. When I want to boot second rom, I boot recovery as normal, flash devil, and reboot secondary.
To go back to 1st, flash appropriate LL kernel, and then reboot primary.
Flashing kernels is very fast, so this only takes a few seconds longer than the regular way of switching, and lets you have LL and KK.
Just thought I'd leave a note in case others want to try out LL without giving up the stability of their regular rom.
Hi @DerTeufel1980
Is this kenel working with i9305?
If not can you please provide a kernel for i9305 with dual boot! like this awesome ketnel
Thanks
Is this kenel working with i9305?
If not can you please provide a kernel for i9305 with dual boot! like this awesome ketnel
Thanks
@DerTeufel1980
Are you still working on multirom for the i9300??
Sent from my GT-I9300 using XDA Premium 4 mobile app
Are you still working on multirom for the i9300??
Sent from my GT-I9300 using XDA Premium 4 mobile app
Previously I have reported about some strange situation with the battery on this kernel.
I continued the investigation and even bought a brand new battery from Samsung.
And it looks like something is really wrong with at least Soft Voltage setting.
1. The problem with @Quick charging@ and short discharging time is still present with new battery. Soft Voltage = 4.3V as original.
2. When tweaked Soft Voltage to 4.25V to improve battery life a little I can observe the real situation is getting worse. When the battery is "charged full" and disconnected the real level drops immediately to about 97%. When the level shows 30-35% the phone is powered down and when I connect it again to charger it shows 0%!
@DerTeufel1980 - any comments on this? What is Hard Voltage - there is no setting for it (but original Perseus had), maybe it is not correct?
I continued the investigation and even bought a brand new battery from Samsung.
And it looks like something is really wrong with at least Soft Voltage setting.
1. The problem with @Quick charging@ and short discharging time is still present with new battery. Soft Voltage = 4.3V as original.
2. When tweaked Soft Voltage to 4.25V to improve battery life a little I can observe the real situation is getting worse. When the battery is "charged full" and disconnected the real level drops immediately to about 97%. When the level shows 30-35% the phone is powered down and when I connect it again to charger it shows 0%!
@DerTeufel1980 - any comments on this? What is Hard Voltage - there is no setting for it (but original Perseus had), maybe it is not correct?
I think the development for this kernel has died...
Sent from my GT-I9300 using XDA Free mobile app
@DerTeufel1980 I wish you would surprise us with a newer version of the kernel mate, miss your kernel
I believe I have issues because of this feature: now I can install only Devil and arter's kernels - stock one and all others including Boeffla leads to stuck at Samsung logo (no animation - it comes later, only logo) during the boot.
Is there any way to restore mali libs to stock ones? Unfortunately I have no backup, but I believe I can extract corresponding libs from original ROM and flash them in /system/libs via recovery.
But I need to know which libs were replaced.
I've expected restoring /system/libs/egl from stock ROM via recovery will help - but it doesn't.
Last edited:
pleaseDevil3.4_0.5.3-i9300-DUAL-20141009.zip
sorry , this kernel support android 4.3 samsung s3 based stock roms ?
thank you!
Last edited:
"This kernel only supports roms of android version 4.3.x (sammy and aosp) and 4.4.x!"
Well in the OP it says the above. Do a nandroid backup then flash whatever kernel you like
Sent from my GT-I9300 using XDA Free mobile app
Well in the OP it says the above. Do a nandroid backup then flash whatever kernel you like
Sent from my GT-I9300 using XDA Free mobile app
Yes , I know that Devil2-2.3.2 [4.4.x, 4.3.x] support 4.3 sammy based stock roms , ... but I dont know if Devil3.4_0.5.3-i9300-DUAL-20141009.zip , also support 4.3 based stock roms.
thank you
Last edited:
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
146
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 only supports roms of android version 4.3.x (sammy and aosp) and 4.4.x!
You can dualboot any of those roms
if you were using this kernel on aosp based roms, and want to use another kernel, you need to reflash the rom, of course without any wipe, it's just to restore modified files
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 changelogs56here is the new recovery now. with this, and the 2.4.7 kernel from previous page, you are able to format and use f2fs instead of ext4. below a guide by a user in my note2 thread:
here some additional info about the changes to kernel and recovery:
what's new:
kernel:
- added new f2fs filesystem support (supposed to be up to 2 times faster than ext4), backported from linux 3.13
- introduce the BFQ-v6r2 I/O sched for 3.3
- block, bfq: add Early Queue Merge (EQM) to BFQ-v6r2 for 3.3.0
- enable CGROUP_BFQIO by default
- backport SLUB (memory allocator, very important) from Linux 3.8
Big thanks to arter97 at this point. He sent me the initial f2fs patches, fixed building of bfq io scheduler, as well as had ported slub to 3.3 already.
- updated block subsystem (io schedulers) to Linux 3.4
- afsync: replace fput() with fput_light() accordingly
- cfg80211: Fix memory leak
- mm: implement WasActive page flag (for improving cleancache)
- fix triangle away
- usb: fix 'adb root'
recovery:
- complete rework of recovery ui (primary and secondary rom need to be selected once in dualboot menu)
if you can't access dualboot menu, please boot primary or secondary rom with the new kernel once
- resized secondary system image to 1.9 gb
- possibility to flash roms to secondary without modifying the zip (you HAVE TO CHOOSE ROM). if this fails, select use workaround (this is the old method) next time
- added support to format and mount f2fs formated partitions (/system, /data and /cache)
- if you format data to f2fs (this gives the maximum prformance, you have to select primary rom in dualboot menu, then the option will be in mounts and storage: format /data, /data/media and secondary (please backup before, this wipes your internal sdcard as well))
I'll update the op, once i get confirmed f2fs is working well for you
This has been the work of almost one month every evening.
Please consider a small donation to show me your appreciation (and i can show my family that i am not just wasting my time).
latest kernel can be found here:
http://xdaforums.com/showpost.php?p=51148539&postcount=180453as quoted above, i am leaving home today again, but not without uploading the new kernel for you as well34Changelog:
02.01.2014:
+ merged mk9 source drop
+ fixed usb connection
+ fixed execution of some init.d scripts
+ changed calculation of next freq in pegasusq (based off a commit by stratosk to ondemand governor, which giot merged into linux 3.11)
+ reverted Sec Oom Killer (maybe causeing some random reboots)
+ switched to latest linaro toolchain (4.8.3 of 12/2013)
26.12.2013:
+ fixed video recording on aosp roms
25.12.2013:
+ cleanly merged update13 (thx to yank555-lu), my previous merge was messed up
+ addded async fsync by htc (ported by faux123)
24.12.2013:
+ merged samsung update13
+ switched back to O2 compiling mode (smaller kernel image, maybe better stability)
+ hardware keys backlight options working for samsung roms as well now
+ re-added oc up to 2 ghz (for those whos device can handle this, mostly added for note2)
+ re-added devil kernel boot logo
+ updated adbd binary to get rid of countless errors in logcat
12.12.2013 part2:
+ samsung 4.3 roms: added new additional mountpoint for external sdcard ( /extSdCard)
+ aosp 4.4.x roms: export path of external storage, needed by some apis
12.12.2013:
+ merged samsung update for note2 (contains fixes for memory management, mali driver, lowmem killer option SEC_OOM_KILLER, new modem driver, ...)
+ backported cpu boost driver
+ improve swap per google's suggestionCode:When certain bursty and important events take place, it might take a while for the current cpufreq governor to notice the new load and react to it. That would result in poor user experience. To alleviate this, the cpu-boost driver boosts the frequency of a CPU for a short duration to maintain good user experience while the governor catches up. Specifically, this commit deals with ensuring that when "important" tasks migrate from a fast CPU to a slow CPU, the frequency of the slow CPU is boosted to be at least as high as the fast CPU for a short duration. Since this driver enforces the boost by hooking into standard cpufreq ADJUST notifiers, it has several advantages: - More portable across kernel versions where the cpufreq internals might have been rewritten. - Governor agnostic and hence works with multiple governors like conservative, ondemand, interactive, etc. - Does not affect the sampling period/logic of existing governors. - Can have the boost period adjusted independent of governor sampling period.
+ enabled SEC_OOM_KILLER:
+ switched to zswap (backported from linux 3.13) + vnswap instead of zramCode:This enables 'Android-Style oom-killer' The way to select victim by oom-killer provided by linux kernel is totally different from android policy. Hence, it makes more sense that we select the oom victim as android does when LMK is invoked.
03.12.2013:
+ gpu control: voltages are applied as deltas internally (no noticable change for users, this just was needed for the second change below)
+ gpu control: if gpu freq. gets changed by user, only reset its matching voltage, all other voltages stay untouched.
29.11.2013 part 2:
+ fixed apllying of custom gpu voltage
+ removed intellyplug driver (wasn't working properly, consumed much battery, made boot up take longer and it was unstable)
29.11.2013:
+ fixed: secondary rom no longer stuck at max freq.
+ gpu control: automatically set voltages according to changend freq (ported from yank555-lu), you can apply your own voltages after you have changed all freq (changing a freq, causes the voltages to be reset again)
26.11.2013:
+ added sepreate initramfs for cm11 and omni
+ recovery: fixed wiping of secondary filesystem
25.11.2013:
+ added support for omnirom, including dualboot
24.11.2013:
+ partial updated mali driver from SEA update 1 (this also fixes a typo in original implementation)
+ properly applied dualsound engine support, boeffla and scoobidoo (unlike other devs, this implementation only allows one sound mod to be active at a time. if you switch on boeffla (in boeffla app for example), scoobidoo gets disabled automatically. if you turn on scoobydoo in deviltools (new option), boeffla gets disabled automatically)
22.11.2013:
+ fixed hardware keys backlight settings and added more options to Deviltools
+ small fixes to gpu interface, compatible to new Deviltools
+ switched to latest boeffla sound engine
+ small mdnie related corrections
22.11.2013:
+ added gpu control, needs to be set manually for now.
+ ARM: SMP: use a timing out completion for cpu hotplug
+ init.d support for sammy 4.3
+ dualboot support for all supported roms (i couldnt try this. be careful!)
20.11.2013:
+ fixed loosing baseband on aosp roms
+ added support for cm11
+ some code cleanup
+ reverted SEA update 1 (seems to be faster without...)
19.11.2013:
+ merged SEA update 1
+ some small code fixes and cleanups
+ updated wifi driver from note3
+ sammy4.3 initramfs: disabled creation of 300mb zram (yank555-lu)
+ aosp 4.3 initramfs: reverted back to previous ones
16.11.2013:
+ fixed and readded mdnie control
+ fixed kernel version been displayed under "about phone"
...more to come31I am in hospital currently and before I moved to a new home. But I didn't sell my Note and I'll start development again as soon as possible
Gesendet von meinem JY-G4 mit Tapatalk
