yashsingh1/xdaforums huggingface dataset:
[Elephone P8000] Stefan Gündhör:
dt2w stopped working at some point after 1-2 days of uptime for me as well.

Scratching sensor did not help, but rebooting fixed it.

In my case it might be related to the pocket mode being stuck, because I carried the phone around a lot in the past 2 days.
[Elephone P8000] skeleton1911:
Yep. Disable pocket mod will fix it.

If not. Also Disable dynamic fsync.

Tip: In most cases a reapply in vtools settings will fix dt2w too
[Elephone P8000] Stefan Gündhör:
Not in my case, but I will try without pocket mode now and even if the problem persists, I can live with it, for me this feature is nice to have but not essential and a reboot will fix it anyway.
[Elephone P8000] BlueFlame4:
So to everyone who doesn't know it yet: I'm currently selling my P8000 because I'd like to have a Qualcomm powered device for now to port CyanogenMod onto. I hope Stefan will continue and enhance this kernel or create his own fork :) Thank you all for being part of this awesome community! I'll stop by now and then but won't actively develop for this device anymore.

Cheers!

Jan
[Elephone P8000] MTIH1992:
But wont you miss the glorious battery? ;)

In all seriousness, thank you for your work on the kernel, you've made hundreds of people very happy and really made this device reach its potential. Hope you enjoy the new toy, but you never know...you might be back ;)
[Elephone P8000] BlueFlame4:
Happy to hear :) Well, maybe I'll build some versions blindly some day, who knows ;)
[Elephone P8000] BlueFlame4:
I just uploaded a 1.6.2 version which features a security patch for the keychain vulnerability recently discovered. See: http://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-0728

It's attached in OP - can someone test it?
[Elephone P8000] miqcea3:
Sorry for OT, but do you already know which device it will be? :o
[Elephone P8000] BlueFlame4:
I already bought an Elephone Trunk and am very pleased. Great build quality and a Snapdragon SoC :) And there are also kernel sources, hooray! Once I got it up running CM 13, I'll buy a Xiaomi Redmi 3 because I like to have a toy to play with :D
[Elephone P8000] jknarf:
With the ****ed up bootloader?

http://www.chinamobilemag.de/news/xiaomi-redmi-note-3-warnung-vor-dem-flashen-und-kauf.html

I really hate Tapatalk and miss ff. rest in peace my ol friend...
[Elephone P8000] BlueFlame4:
Yes, I heard about that problem... . IF I buy a Redmi 3, I won't have those problems that the author describes because the Redmi 3 is unlike the Redmi Note 3 Qualcomm-powered. So no hassle with SPFT there. Still I need to get my bootloader unlocked somehow but I'll go for the Trunk for now anyways ;)
[Elephone P8000] Cusciify:
Hi, i can't flash the img for flyme rom. Every time i flash the kernel i got stuck in a bootloop and i have to reflash the rom.

Have anyone have the same trouble or can help me?
[Elephone P8000] BlueFlame4:
From now on I'll help Stefan with his kernel, so this thread will be closed. It's the best for everyone if we work together than having two different kernel branches ;) Just pushed battery fixes Stefan will soon include in his guestekernel.
[Elephone P8000] :
Thread reopened per OP request! :good:
[Elephone P8000] BlueFlame4:
visi0nary's kernel is back! Version 2.0 features major improvements! Check first post for the changelog :)

Enjoy!
[Elephone P8000] :
I'm looking for some patches for gov interactive although i see it hard to merge into mtk kernel
[Elephone P8000] Mcuteangel:
Both two version 2 files are 8core?
[Elephone P8000] sgspluss:
DT2W means still activ even if its disabled from rom side?

Gesendet von meinem p8000
[Elephone P8000] walter79:
Hotplug settings:

found here: /kernel/elephone/p8000/drivers/misc/mediatek/mach/mt6735/include/mach/mt_hotplug_strategy_internal.h

#define HPS_TASK_PRIORITY (MAX_RT_PRIO - 3)
#define HPS_TIMER_INTERVAL_MS (100)

#define MAX_CPU_UP_TIMES (10)
#define MAX_CPU_DOWN_TIMES (100)
#define MAX_TLP_TIMES (10)
//cpu capability of big / little = 1.7, aka 170, 170 - 100 = 70
#define CPU_DMIPS_BIG_LITTLE_DIFF (70)

/*
* CONFIG - runtime
* Execute time interval : 100 ms
*/
#define DEF_CPU_UP_THRESHOLD (95)
#define DEF_CPU_UP_TIMES (2)
#define DEF_CPU_DOWN_THRESHOLD (85)
#define DEF_CPU_DOWN_TIMES (8)
#define DEF_TLP_TIMES (1)

#define EN_CPU_INPUT_BOOST (1)
#define DEF_CPU_INPUT_BOOST_CPU_NUM (2)

#define EN_CPU_RUSH_BOOST (1)
#define DEF_CPU_RUSH_BOOST_THRESHOLD (98)
#define DEF_CPU_RUSH_BOOST_TIMES (1)

#define EN_HPS_LOG (1)
#define EN_ISR_LOG (0)

/*
* EARLY SYSPEND CONFIG - runtime
* Execute time interval : 400 ms
*/
#define DEF_ES_CPU_UP_THRESHOLD (95)
#define DEF_ES_CPU_UP_TIMES (1)
#define DEF_ES_CPU_DOWN_THRESHOLD (85)
#define DEF_ES_CPU_DOWN_TIMES (2)

Found this: /kernel/elephone/p8000/drivers/misc/mediatek/mach/mt6735/mt_hotplug_strategy_main.c

//In order to fast screen on, power on extra little CPU to serve system resume.
little_cpu_num_resume = 4;

We can use this settings device runs very well but need some improvment for cpu govornor setting:

little_cpu_num_resume = 1;

#define EN_CPU_INPUT_BOOST (0)

#define EN_CPU_RUSH_BOOST (0)
[Elephone P8000] :
[MENTION=3784300]BlueFlame4[/MENTION] Can you change readahead 512 > 128
[Elephone P8000] :
Antutu-Points:

visionary V2.0-8cores 40971 points

visionary V2.0-4cores 38882 points

scafroglia93 8cores 40928 points
[Elephone P8000] alfredxyz:
for me with both versions of v.2 kernel the display wakes up randomly and I could not disable DT2W in display settings
[Elephone P8000] sgspluss:
Should be related to this change in kernel https://github.com/visi0nary/androi...mmit/f75cc7fbdacce6989c7768933879e43d445498c4

Maybe [MENTION=3784300]BlueFlame4[/MENTION] can take a look into this again...

Gesendet von meinem p8000
[Elephone P8000] Emileh:
Hey [MENTION=3784300]BlueFlame4[/MENTION] do you plan on building a kernel for the 2016 version? :)

Would be great and I see you have the source on git.

Thank you for your hard work!
[Elephone P8000] BlueFlame4:
You're right. Thanks!

W/System.err( 699): java.io.IOException: write failed: EPIPE (Broken pipe)
W/System.err( 699):	at libcore.io.IoBridge.write(IoBridge.java:502)
W/System.err( 699):	at java.io.FileOutputStream.write(FileOutputStream.java:186)
W/System.err( 699):	at java.io.OutputStream.write(OutputStream.java:82)
W/System.err( 699):	at java.io.DataOutputStream.writeBytes(DataOutputStream.java:156)
W/System.err( 699):	at org.cyanogenmod.hardware.TapToWake.setEnabled(TapToWake.java:71)
W/System.err( 699):	at org.cyanogenmod.platform.internal.CMHardwareService$LegacyCMHardware.set(CMHardwareService.java:184)
W/System.err( 699):	at org.cyanogenmod.platform.internal.CMHardwareService$1.set(CMHardwareService.java:405)
W/System.err( 699):	at cyanogenmod.hardware.ICMHardwareService$Stub.onTransact(ICMHardwareService.java:71)
W/System.err( 699):	at android.os.Binder.execTransact(Binder.java:446)
W/System.err( 699): Caused by: android.system.ErrnoException: write failed: EPIPE (Broken pipe)
W/System.err( 699):	at libcore.io.Posix.writeBytes(Native Method)
W/System.err( 699):	at libcore.io.Posix.write(Posix.java:258)
W/System.err( 699):	at libcore.io.BlockGuardOs.write(BlockGuardOs.java:313)
W/System.err( 699):	at libcore.io.IoBridge.write(IoBridge.java:497)

Oddly enough this doesn't make sense but I will look into it later.

For now we have 2.1 which features an improved hotplug algorithm by [MENTION=382340]walter79[/MENTION]. All 8 cores are "available" again but they are plugged in much lazier than before. Enjoy!
[Elephone P8000] BlueFlame4:
I don't own the device so I guess someone who does should do this :)
[Elephone P8000] :
Guys, it's very difficult apply the latest Interactive Gov patch
[Elephone P8000] mauro2112:
Hello everyone this is band b P8000 with stock rom + 2.1 kernel version

View attachment 3865828

Thanks!!

Antutu benchmark: 40818
[Elephone P8000] :
Waiting for revision
[Elephone P8000] :
Until this is fixed and deactivated you can use Kernel Auditor app to switch it off permanently.
[Elephone P8000] :
Improvements with Arm64 Energy Patch ?
[Elephone P8000] charliepie:
Thanks for the recent developments with your kernel, is this good for Eragon rom as well or just CM? Presently using 3.10.103 think that's guestekernel...2.4.1
[Elephone P8000] valascus:
Guestekernel 2.4.1 is not updated, so, it uses 3.10.102.
[Elephone P8000] Mcuteangel:
Latest kernel have fast battery drain
[Elephone P8000] :
Sometimes battery drain are generated by system app
[Elephone P8000] :
Test kernel with massive update:

- Gpu

- Networking

- Kill LogSpam

- Tons of Arm Patch

Keep me updated please

My Source:

https://github.com/scafroglia93/android_kernel_elephone_p8000
[Elephone P8000] Moyster:
I'm gonna cherry-pick that and see how it goes, I love your work mate <3

edit: I had some of these networking changes already, I think you need

"CONFIG_INET_DIAG_DESTROY=y"

in your defconfig to take advantage of it ;)

edit 2:

same goes for the new fiops sched

IOSCHED_FIOPS

(DEFAULT_FIOPS)
[Elephone P8000] :
You have installed my test kernel ?
[Elephone P8000] Moyster:
More or less : https://github.com/Moyster/android_kernel_m2note/commits/lp-5.1

I mostly used visi0nary's repository to patch my way up and ended up cherry-picking most of the commits :)

You can check (for instance schedulers) :

# cat /sys/block/mmcblk0/queue/scheduler

noop deadline cfq [zen] sioplus

fiops is not enabled nor built inside ;)

edit:

enable it :

https://github.com/Moyster/android_kernel_m2note/commit/0644760e0f9d6f24e884324ff2f3304ccac0a1c8

and it spawns :

# cat /sys/block/mmcblk0/queue/scheduler

noop deadline cfq [zen] sioplus fiops

PS: don't mind the few schedulers I don't have compared to you
[Elephone P8000] jknarf:
I installed the kernel around twelve hours ago.

I did not make any benchmarks but it feels very fast snappy. Battery consumption seems to be good.

Great job.:)
[Elephone P8000] boka18:
5 hours of usage, got 96% battery. wow
[Elephone P8000] :
Another Test Kernel with massive update:

-Scheduler Improvements (Blk-throttle, blkcg, cgroup)

-Sched Update

-Build with latest UberTC 4.9.4
[Elephone P8000] anibalcezar:
[MENTION=2357893]scafroglia93[/MENTION] sorry to ask but this kernel works on Eragon?
[Elephone P8000] charliepie:
I'm on Eragon 9.9 as well, I might try flashing your test kernel with flashify to see if it works;)

*Edit* NO, doesn't work with Eragon - I ended up having to dirty flash 9.9 again as the phone would only boot to recovery, even wiping cache & dalvik twice was futile. Tried to flash guestekernel on top but no luck with that either so I wouldn't recommend you try this test kernel with Eragon rom.
[Elephone P8000] :
This kernel is CM Based so, it's work only with CM and derivates
[Elephone P8000] micbanand:
Thanks will use it and se.

seems fine for this short time. But no Init.t support.

is there a reason all these p8000 kernels ****s that up so often?
[Elephone P8000] :
Make it your kernel man!
[Elephone P8000] Jonny:
Init.d support is in the ramdisk (init.rc file to be specific). The ramdisk forms half of the boot.img file, the other half is the kernel. What you flashed was a raw boot.img containing a ramdisk as well which doesn't seem to have init.d support.

A nice easy solution to this is for the kernel to be provided in a flashable zip that uses unpackbootimg and mkbootimg to keep the original ramdisk and only update the kernel.
[Elephone P8000] Moyster:
ramdisk and init.rc files are not "init.d", it's an initramfs, which init the kernel in order for it to boot..

init.d helps setting services/scripts on boot as it's loaded after the hw init, during the boot process.

So I wouldn't recommend unpacking the kernel from one ramdisk to another as it's the best way to create bugs and instabilities, either add init.d support to the kernel project from OP*, either start a "fork" ;)
[Elephone P8000] sgspluss:
[MENTION=2357893]scafroglia93[/MENTION] would it be possible to set dt2w off in kernel, as it was few updates ago? Since it was activated you can not control it over rom just over kernel editor would be a bit anoying.

Gesendet von meinem p8000
[Elephone P8000] Jonny:
You add in the init.d script support in init.rc though and no using unpackbootimg and mkbootimg does not create instability and/or bugs.

Init.d script support is not a kernel thing. I've been making ROM's for 4 odd years now and it never has been a kernel thing.
[Elephone P8000] Moyster:
I might have not been clear, but adding a hook inside the boot.img initramfs to call on busybox in order for it to parse /etc/init.d/ is not having init.d inside the boot.img :) I guess we say the same things in the end.

And I never said init.d scrit was a kernel thing, it's a kernel that is mainly aiming CM, therefore the init.rc files that comes with it are better to be in sync with OP release better than creating a "freak" boot.img using a scripted update.zip to repack the kernel.

All it takes it to add a simple hook in OP's boot.img.

Greetings
[Elephone P8000] Jonny:
That little snippet implies you thought init.d support was in the kernel. Hence my reply.

The CM ROM should also flash the boot.img file so if users wanted to just update the kernel I think having a zip that repacks it is a very tidy - it also means 2 boot.img files don't have to be maintained.

But to each their own ;)
[Elephone P8000] boka18:
[MENTION=3784300]BlueFlame4[/MENTION] can u upload the latest kernel u used on CM12.1?
[Elephone P8000] Moyster:
If you downloaded the latest rom, just use the boot.img you can find inside :)
[Elephone P8000] BlueFlame4:
Not exactly. Stock ROM won't boot it because of ramdisk changes. Even the kernel itself won't boot because I removed a lot of unneeded MTK bull**** in cm kernel.
[Elephone P8000] sgspluss:
[MENTION=3784300]BlueFlame4[/MENTION] would it be possible to revert this commit? https://github.com/visi0nary/androi...mmit/f75cc7fbdacce6989c7768933879e43d445498c4 its annoying to use an extra app to disable dt2w since without set this to "y" you can handle it on rom side.

This holds me to old kernel... Would nice if its possible.

Gesendet von meinem p8000
[Elephone P8000] walter79:
Will test it tomorrow.
[Elephone P8000] sgspluss:
Would be nice to get this [MENTION=382340]walter79[/MENTION] thanks for hearing me ?

Gesendet von meinem p8000
[Elephone P8000] alandur:
I've disabled it in the settings of my cm12.1, without any additional app. In my mind the 2.0 kernel I think had this discribed issue, sie am I wrong?

Gesendet von iPhone mit Tapatalk
[Elephone P8000] walter79:
Reverting this commit disable d2tw. You can t enable it with cm setting
[Elephone P8000] boka18:
just want to say that this kernel is working with the latest Eragon (v10)
[Elephone P8000] valascus:
Of course it's working...

From Eragon's 10 Changelog:
[Elephone P8000] boka18:
iys gueste kernel. visionary is v2.1
[Elephone P8000] valascus:
Oh... So.. skeleton made a mistake.
[Elephone P8000] pjella:
[MENTION=5942840]boka18[/MENTION] - Could you please check if possible and update if encryption working with visionary v2.1 kernel on Eragon v10.0? Many thanks.
[Elephone P8000] valascus:
Of course not.

It's not a kernel related bug.
[Elephone P8000] BlueFlame4:
Version 2.2 is attached to OP. Changelog is too huge to post, sorry. TLDR loads of improvements ;)
[Elephone P8000] -Tiz-:
Will this kernel be automatically integrated into the next CM OTA or do I have to separately flash it? Thanks.
[Elephone P8000] sgspluss:
Reverting this commit would bring it back to standart that you can manage it in rom without second app.

Have test it today on myself, flashed new v2.2 kernel and it force dt2w always on even if i disable it in rom it would be always on. Then installed kernel adiutor and disable dw2t in this app, now it force it to stay always off even if i try to set it on in rom. I thought ok lets try older kernel without this change means tried v2.0.0 and tada it works as it has to, can set it off and on in rom without problems with forcing.

Maybe you [MENTION=382340]walter79[/MENTION] and [MENTION=3784300]BlueFlame4[/MENTION] can take again an eye on this.

Gesendet von meinem p8000
[Elephone P8000] walter79:
https://github.com/visi0nary/androi...mmit/2746fd76156e70951d01a44a86c92e3015ee1cd1

Use fixed libslos.so
[Elephone P8000] BlueFlame4:
There is no difference anymore between visi0nary's kernel and CM kernel.

Thanks for the hint with DT2W btw! [MENTION=4920940]sgspluss[/MENTION]
[Elephone P8000] sgspluss:
No prob [MENTION=3784300]BlueFlame4[/MENTION] hope to see an fixed version soon ;)

Gesendet von meinem p8000
[Elephone P8000] Damoedge:
Hi Blue, which version of this kernel did you lock Selinux to enforcing??

So I can install the kernel below that so I can switch between enforcing or permissive when needed

Thanks

D.
[Elephone P8000] duffi200000:
hi guys, can you help to port this kernel for elephone m2
[Elephone P8000] Snul9:
visi0nary's 2.2 or guestekrnl 2.4.1? Which is better?
[Elephone P8000] Fourteenth:
Is it possible to explain how do you change the kernel? I mean what tools do you use and what steps is needed to make a custom kernel.
[Elephone P8000] BlueFlame4:
How far have you come?

IIRC 2.1 was the last version that allowed permissive. Still you should avoid setting SELinux to permissive if it's not absolutely neccessary :)

I don't understand the question, can you elaborate a bit more?
[Elephone P8000] lokitoo92:
hola buenas yo tengo la nexus 2.6 con kernel gueskrnl 2.4.1 podria flasear el de visionary sin ningun problema
[Elephone P8000] Snul9:
Yes, without problem.
[Elephone P8000] gabri84sv:
Hi guys, does it works on lineageos 13? thanx
[Elephone P8000] Bradco:
Yes you can, but flash with rash flash tool on playstore, it's more simple, if you want :)

.
[Elephone P8000] peptonib:
Sounds nice... Could you share with us a "how to"...? :fingers-crossed:
[Elephone P8000] jott_st:
Yes, that's probably because when thermal throttling kicks in, it scales down one step, which is 1.3 GHz instead of 1.17 GHz.

I guess both solutions aren't the cleanest, but oh well :D. No, I neither have the time, nor the experience for ROM Development. Besides, I'm pretty happy with debloated stock and Xposed. :)

Do you know if the GPU runs [MENTION=1601421]600[/MENTION] MHz? Otherwise a similar approach in _mt_gpufreq_get_dvfs_table_type() would probably overclock the gpu.

Sure: Check out BlueFlame4's Repo (it's in the OP), revert the last commit and add "return CPU_LEVEL_0;" in drivers/misc/mediatek/mach/mt6735/mt_cpufreq.c, line 861. Build the kernel. Done :).

I can upload a working image when I get home, but I'm pretty sure BlueFlame4 will have it implemented by then ;).
[Elephone P8000] BlueFlame4:
I haven't checked GPU frequencies yet or rather can't find any link that outputs the current frequency. Looks like Mediatek is using a non standard approach there again. Did you find a way?

Right, haha ;) Changelog and MD5 in OP :)
[Elephone P8000] Stevethegreat:
Just one suggestion if I may: I think it would be best if you were to give a link to original (stock) kernel on your first post so that it would be easy to revert if anyone ever feel the need.

As it stands, one has to dig the flash-tools files to find the image. It's not that hard, but it would be easier if we had a link of the kernel alone on the first post.

BTW thanks for taking the time to look into this device.
[Elephone P8000] BlueFlame4:
Good idea, thanks! Attached stock kernel in OP. Also thanks for your kind words :) CM starts to become boring at the moment because I'm the only one digging around there, so words like these are more than appreciated!
[Elephone P8000] jott_st:
They're definitly using a non standard approach :( I didn't find a way yet.

But could anyone give me the Antutu 3D Score real quick? Preferably from a cool/long-term idling phone?
[Elephone P8000] DrStuhl:
Here are my results. Seems like 0.7 is slightly better than the Stock Rom for me.

Stock:

0.7:

Note: If you are surprised about the time: I've been testing 0.7 first, then reflashed to Stock Kernel.

3D Score slightly decreased, but that might be the testing variance?

btw: Thank you BlueFlame4 for your releases :):good:
[Elephone P8000] Nikolaosf:
Very small difference.... Hmmmmm

---------- Post added at 04:39 PM ---------- Previous post was at 04:33 PM ----------

[IMG="P6000 Pro Geek"]http://s13.postimg.org/jtx888hrb/IMG_20151017_124410.jpg[/IMG]

Stock 1.3 ghz p6000 pro....dont know if it proves anything
[Elephone P8000] jott_st:
Thanks!

Yes, I'm getting these variances,too. I'm guessing thermal throttling kicks in pretty quickly.

So I played around a little with frequencies and it looks like overclocking the GPU is not as easy. I'm pretty sure the device is running [MENTION=1601421]600[/MENTION]Mhz and setting a higher frequency doesn't seem to work. :crying:
[Elephone P8000] Stevethegreat:
I don't think it is . It's the same kind of variance that you're going to get with or without the overlock. I'm starting to think that the overlock does not stick like it happens to the rest of Mediatek devices (it says "1.5Ghz" but the CPU is running 1.3Ghz actually).

Unfortunately it seems to need deeper digging, Mediatek made sure that over-clocking would be very hard and I think to this day nobody has achieved over-clocking Mediatek devices. MT6753 seems to fall in this category. It's rather unfortunate that I do not have my P8000 currently to run more thorough tests of my own, but either the OC does not stick, or it instantly throttles when it recognizes the high volts.

Whatever's the case the device does not seem to be overlocked from where I'm standing.

Mediatek MT6752 runs at 1.7 Ghz and gets a geekbench 3 score in the high 3000s (almost 4000), MT6753 gets a score in the high 2000s, so I'd expect a score in mid 3000s if the overlock was to stick.
[Elephone P8000] stefano91av:
Why have i only 29700 with kernel 0.7 in antutu?
[Elephone P8000] pitrus-:
Because it's a synthetic benchmark and doesn't really mean a sh*t. Also you should be aware that this is really exciting experimentation as there are no known methods on how to do overclocking on mediatek SoC:s. Be glad someone is actually trying, I am and would be helping if my HP Proliant server were up and running right now, still setting it up.
[Elephone P8000] ShootistUK:
I got my highest antutu bencmark of 34,658 using 0.7
[Elephone P8000] BlueFlame4:
I also thought about that. Will try to go ridiculously low tomorrow and see if the device begins to lag. If it does, the freqs are real ;) Thanks for your feedback!

OP updated, I just added Doubletap2Wake, yay! :) Good night people :D
[Elephone P8000] skeleton1911:
Hey mate.

We have a little sos.!

Related to the new 20151014 base.

There elephone changed the internal storage from data/media/0 to data/media.

That means recovery and also kernel are not able to find the storage anymore..

Look into newest kernel (init.ssd_nomuser.rc and no ssd.rc anymore).

It will be possible after the update to use app2sd. But that method (and part now) is full of risk.. Of losing data etc...

I personally do not understand elephone..

(Let's go via pm, if you want)

Gesendet von meinem Elephone P8000 mit Tapatalk
[Elephone P8000] jott_st:
Actually it's more of an "unlocking" than overclocking. The SoC supports 1.5 GHz, but they are using an efuse or something like that to determine if the cpu should run at 1.3 or 1.5Ghz. This check is removed from the sourcecode.

If you compare the benchmark scores, you have to consider that they usually not just test the cpu. But if you compare the stock antutu CPU integer scores by themselfs for example, it shows approx. the 13% increase of the overclocking (Stock: 5286, I tested around 6000). So I think it sticks, but the device also heats up pretty quickly so that it gets throttled again.
[Elephone P8000] BlueFlame4:
I have to update the ramdisk to make the kernel work with the latest release, but unfortunately I don't have time now. Will do so asap. Surprisingly there is no mention in the changelog from Elephone, is there?

PMs are a good idea btw ;)