yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Saber:
The problem definitely started on LP. Updating the kernel to Linux 3.15 didn't cause this issue, but it is likely that some parts of the kernel still needs to be updated (e.g LMK, ZRAM, etc).

gsstudios
[Galaxy S II Android Development] Saber:
Update

We have a working kernel for CM13, but wifi is broken and storages is not working properly.

We will now have a separate kernel for LP and MM because of the selinux requirement in MM.

gsstudios
[Galaxy S II Android Development] arnab:
I can help you with wifi...contact me in pvt
[Galaxy S II Android Development] Saber:
Hi guys,

I forgot to tell everyone that SuperSU was removed from the kernel since the last build. Now root is handled by the OS or from an existing SuperSU installation.

A small update on MM kernel, we have internal storage working again! ;) Wifi problem is still there but we are very close to a fully working kernel.

See the changelog for a sneak-peek of what to expect in next build :)

gsstudios
[Galaxy S II Android Development] silvers01:
hey again, are you not providing anymore of the non-trim version? ..the last non-trim version i saw in androidfilehost is 0b025
[Galaxy S II Android Development] OllieW:
Since TRIM will work on every Galaxy S2 GT-I9100 device without problems (regardless of any known device bugs), it is now enabled by default in CM and in this kernel.
[Galaxy S II Android Development] Saber:
Pretty much what [MENTION=5695282]OllieW[/MENTION] said.

I don't make non-trim builds anymore because everyone should be using TRIM regardless if you are affected by brickbug or not as not trimming could shorten the life of your components.

gsstudios
[Galaxy S II Android Development] Saber:
I am excited to announce DorimanX 12.0 b002, now with CM13 support!!!

We've been working endlessly on this kernel to get it working on CM13 and now we have a working kernel! Many thanks to Realex-fire for helping me.

I have tested this kernel on CM13 for some time now and it has been stable. I still need to test if every feature is working correctly, but so far it is working fine.

If you've installed BLN-MOD, make sure to change the settings back to default and remove synapse otherwise hardware buttons will always stay on until you switch off the screen.

Selinux is now enabled and set to permissive by default. Wifi driver was updated to 1.141.44, let me know if you experience any issues with wifi. VPN has been fixed (tested on MM using Hola VPN and Hotspot Shield).

We haven't forgotten about CM12.1 users, CM12.1 users will also get the benefits of the CM13 changes as well. And yes, this is CM12.1 and CM13 support from the one kernel!

There were many other improvements, too many to list (see changelogs).

Happy flashing! - gsstudios
[Galaxy S II Android Development] haris1976:
first download
[Galaxy S II Android Development] OT-Xtreme:
great news! many tnx
[Galaxy S II Android Development] the.gangster:
Congrats and big thanks to both of you (and all of you who commited) to achieve this big step foreward!!!

And for BLN-MOD users it should also work to disable button backlights completely in the standard menu.

Can't test right now, as my phone is still updating 118 Apps, after flashing latest ROM & GApps, minutes before reading this good news here.
[Galaxy S II Android Development] haris1976:
succes booting
[Galaxy S II Android Development] rubentkato77:
Excuse my question, do I have too flash dori kernel every time I flash a nightly? Regards and thanx [MENTION=5811506]gsstudios[/MENTION]
[Galaxy S II Android Development] nageswarswain:
Sorry for my expectations. Please impliment Dt2w/swipe2wake feature.This will be a show stopper for s2
[Galaxy S II Android Development] haris1976:
are u mean this feature
[Galaxy S II Android Development] Saber:
Yes, you need to flash every time you update to a newer nightly.

gsstudios
[Galaxy S II Android Development] jamu08:
Is the kenel fully ready to flash in RR 6.0.1?? or we have to wait for sometime.keep up the good work. We appreciate your effort.
[Galaxy S II Android Development] nageswarswain:
Yes that feature.can you confirm the double tap to wake also working?you can enable it by kernel auditor app if the kernel supports wake gestures?
[Galaxy S II Android Development] Saber:
Don't know.

I haven't tested on RR. Maybe if someone could test, thanks.

gsstudios
[Galaxy S II Android Development] lightmandn:
RR 5.5.9 LP 5.1.1 : any apps take FC. On MM RR 5.7.0 this problem does not occur. Thank you so wery much for working SuperSu.
[Galaxy S II Android Development] Cyanic Sword:
Was waiting for this update. Thanks to everyone who helped. I guess [MENTION=5811506]gsstudios[/MENTION] lives in the east of Australia (I'm in Perth so we're about 2-3 hours apart). Just a few questions:

Since you have to flash everytime for a new nightly, does it count if you're using CyanDelta? Also, is the cm recovery fixed? It was broken (nothing could be flashed) before.

Can I use the bcmon wifi driver in this kernel?

May I ask how you fixed vpn? I tried Hotspot Shield, Hola VPN, Avast SecureLine and a few others on 11.0 b035 and 12.0 b001. None of them worked except for vpnbook.com's free OpenVPN account through OpenVPN Connect.

Do you know when the cm 13 stable build will come out?

Thanks for your time. I am willing to help out for testing if you need it. And, as always, keep up the good work! :) :good:
[Galaxy S II Android Development] Saber:
1. If there are kernel changes in a specific nightly, then yes. I would still flash the kernel again regardless of what update method used. CM recovery is still dead.

2. I haven't tried for myself, so I don't recommend.

3. I think that our kernel was missing a few important commits in regards to the general net driver. As of a result, the kernel was not able to set up correct VPN routing.

4. If you are talking about the ROM, this has nothing to do with this kernel. If you are talking about stable kernel build, then it may take a while.

Could someone please test whether VPN works. I'm pretty sure it's working on my side (I've only tested on MM btw) but would like to know if it's the same for everyone else.

gsstudios
[Galaxy S II Android Development] :
Just wanted to let everyone know v12.b002 boots fine on AOKP. I'm using the 20160705 build of AOKP and default settings so far. Early signs are slightly more responsive and smooth. Too early to tell about battery and other things. I'll report back in the next few days with more info.

Thanks [MENTION=5811506]gsstudios[/MENTION] and realex-fire. Very much appreciated. :good:

Edit: Only just realised there are uber and linaro builds. I'm using uber
[Galaxy S II Android Development] j1gga84:
But you could also create a script file that prevents the kernel to get overriden by the stock kernel ;)

I know this from Boeffla kernel but I don't know if there is a setting that could be implemented in stweaks!?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S II Android Development] Saber:
It has been confirmed that the Ext4 mounting bug has been fixed

I have tested on CM13 and everything is mounted properly on the latest DorimanX 12.0 b002.

gsstudios
[Galaxy S II Android Development] DJ-Studd:
CM13 and your Kernel are absolutely flying. Thanks!
[Galaxy S II Android Development] Gent':
Will this work on any Cm13 based roms,for example on the XOSP rom that im currently using?
[Galaxy S II Android Development] j1gga84:
Make a backup of your ROM, try and report it back here ;)

Regards

Sent from my SM-T805 using german Tapatalk 4
[Galaxy S II Android Development] Gent':
where to download,cant find the mm version?

---------- Post added at 01:08 PM ---------- Previous post was at 01:04 PM ----------

LINARO OR UBER,which one to use ?
[Galaxy S II Android Development] Saber:
Use the linaro build. There is no need to post in the CM13 thread.

gsstudios
[Galaxy S II Android Development] Gent':
Posted in the kernel thread too,no answer!

---------- Post added at 01:43 PM ---------- Previous post was at 01:26 PM ----------

Tried it it works on the Xosp rom,and i gotta say it runs very well
[Galaxy S II Android Development] GreekDragon:
Anyone flashed the kernel on RR, XOSP and bliss? All works ok?
[Galaxy S II Android Development] lightmandn:
On RR 5..7.0 i haven't problems. All works.
[Galaxy S II Android Development] OT-Xtreme:
works with xosp also
[Galaxy S II Android Development] Gent':
Tried In XOSP and it works.
[Galaxy S II Android Development] ssanjy:
[MENTION=5811506]gsstudios[/MENTION] and team, really great job.... Working in Beanstalk.. Not the latest ROM version though.....

Actually interesting things happened while flashing.... Flashed dorimanx and as a customary wiped dalvik and cache ... Bootlooped .. Waited about half an hour but all in vain.... Again flashed the kernel and tried to boot but still without luck.... So restored boot and system from nandroid after which it booted... While optimisation of the apps I took another chance.... Forced reboot into recovery and flashed dorimanx and rebooted straight away without wipes and amazingly booted but few apps like chrome, XDA labs etc crashed... Again rebooted and then everything is absolutely amazing..... Swipe2Wake, the killer feature missing in stock kernel is working great...

However xposed is not working despite being active... Am on V 85.... The log showed no SELinux in enforcing mode so this might be the problem...

Here's screens of Beanstalk on dorimanx
[Galaxy S II Android Development] Skyline:
[MENTION=5811506]gsstudios[/MENTION]

First of all Thanks to you and Realex-fire for reviving this amazing kernel again And now I think it's time to find & fix some minor issues.

Is there any problem with sysfs file permissions?? coz I have some problems when tried to change cpu governors
[Galaxy S II Android Development] lightmandn:
Whem free ram reduced to ~215mb, device hase strong lags.
[Galaxy S II Android Development] Saber:
I assume you are changing CPU governors with stweaks and not some other app. I am not experiencing this same problem. Please check if you have some other app overriding these settings (if possible).

gsstudios
[Galaxy S II Android Development] ssanjy:
Hey [MENTION=5811506]gsstudios[/MENTION], I again would like to thank you for the ROM... It's only been a while since flashing your kernel but It's feeling very swift and battery friendly in my device and ROM... I've been monitoring the CPU temperature since it used be high on my device, to be precise 60° on an average even on normal use which caused serious battery drain... Now that I've your kernel flashed the temp had dropped to 45°on average in normal use and battery life had improved a lot.. I've not found any problem so far and will report any issues.....

Have a good day
[Galaxy S II Android Development] Skyline:
Ofcourse I am using stweaks but i see the file permissions in /sysfs are different than stock kernel. When i select zzmoove governor with profile 5 and pressed push tunning button but it always show onedemand as governor parameter
[Galaxy S II Android Development] Saber:
Yes, the problem you are describing does sound like problems with permissions. Have you tried reflashing the kernel? Did you update over an existing build? What about resetting stweaks profiles? Is there any more information that you can provide that would be useful (e.g. what ROM you are using, method of flashing. logs are probably not needed).

gsstudios
[Galaxy S II Android Development] Skyline:
I am using official cm13 and flashed latest dori build on stock cm kernel. I will try with clean flash and report here
[Galaxy S II Android Development] KnightElf009:
Can i flash this on aicp rom? clean flash or dirty? thanks
[Galaxy S II Android Development] jamu08:
[MENTION=5760083]gsss[/MENTION]tudios......The comments here are encouraging enough to flash this kernel right way....great work....should we wait sometime more for enhanced MM support particularly for CM13 and RR or all other CM based Rom or should i flash right now?? hahha.....can't wait flashig this kernel...your efforts are really appreciated.:good::good::good:
[Galaxy S II Android Development] Saber:
That's all up to you :)

Right now the kernel functions well and there are no bugs that will affect normal usage of phone.

gsstudios
[Galaxy S II Android Development] mrfrantastic:
Could not get it to boot with latest DU Rom after dirty flash. Got stuck with bootloop.
[Galaxy S II Android Development] jamu08:
The latest MM kernel is Trim based. What is the difference between TRIM and non-TRIM??

---------- Post added at 11:26 AM ---------- Previous post was at 11:13 AM ----------

Which one you used Linaro or uber??
[Galaxy S II Android Development] lightmandn:
Linaro
[Galaxy S II Android Development] IonutGherman:
Will you add Kernel Samepage Merging? I think it will be a good option for this kernel and for our low memory phone. Just a suggestion :)
[Galaxy S II Android Development] Troubadour666:
booted beanstalk .

actualy have system 1.5GB , i used I9100_1.5GB-System_6GB-Data_32MB-Preload_by-the.gangster.pit at the moment i repited my system.

is there a pit file to unlarge preload to 1.5GB, like system partition ?

i want it to test dualboot if the kernel permit it again .

thanks.
[Galaxy S II Android Development] Saber:
I might have a look. I remember it was broken so Dori removed it.

gsstudios
[Galaxy S II Android Development] KnightElf009:
after i flashed the kernel, stweaks said no kernel support. Im on aicp rom marshmallow :D
[Galaxy S II Android Development] Morbidx13:
flashed your kernel earlier but wifi hotspot didn't seem to work. my computer wasn't seeing it so flashed latest CM13 nightly again, wifi hotspot working.

phone is really laggy though, takes an age to open any app
[Galaxy S II Android Development] ssanjy:
Just a query, how did you manage to have selinux to enforcing instead of permissive in kernel.... It changed to permissive in mine
[Galaxy S II Android Development] Troubadour666:
i have "enforcing" by default, without dorimanx and after flashing it, and i didnt test the beanstalk rom any more .

thanks.
[Galaxy S II Android Development] the.gangster:
Wow, I don't think anyone created a PIT file for a 1.5gb preload partition yet.

But as we have REPIT now, there is even no need to create one any more.

If it fails you can post also here.

But it should work with it renamed to as follows:

lanchon-repit-XXXXXXXX-system=1.5-data=6-sdcard=max-preload=1.5-i9100.zip

or

lanchon-repit-XXXXXXXX-system=1.5-data=6-sdcard=max++ext4-preload=1.5-i9100.zip

depending on your internalSD to be default vFAT or ext4 formatted.

Above examples would even preserve all your data if internal sdcard's content still fitted in the new size (~5.5gb).

But read the HowTo! Usually much faster if combined with +wipe and since you were planning to use PIT files you planned a backup already anyway.
[Galaxy S II Android Development] Troubadour666:
thanks, will try later, very later :)

btw, i have prepared :

lanchon-repit-20160415-system=1.5-data=6-sdcard=max++ext4-preload=1.5-i9100.zip

and

lanchon-repit-20160415-system=1.5-data=6-sdcard=max-preload=1.5-i9100.zip

thanks
[Galaxy S II Android Development] jamu08:
I tried to flash this kernal of linaro version by wiping data,system,cache,dalvik cache on RR 6.0.1 isorec twrp 3.0.2-1 but stuck in bootloop. Tried 4 times bit no remedy. Any idea?? I again came back to RR stock kernel.
[Galaxy S II Android Development] haris1976:
why you wiping system ?

just flash kernel and wiping cache & dalvik after that
[Galaxy S II Android Development] Saber:
DorimanX 12.0 b003 has been released.

This build contains mostly bug fixes. There were some minor fixes to selinux. I have fixed mass storage USB mount option in stweaks (tested only on CM13). Root actions and kernel update check was removed from stweaks.

I have added more tweaks to ZRAM to make it run faster on our phone (max_comp_streams=2, force LZ4).

F2FS had many updates from linux mainline kernel. While F2FS is working, I don't recommend using it yet as it lacks the advanced features currently only available on ext4 and vfat (also because it is still a WIP). We will be working on it in future builds.

Lastly, I have disabled panic_on_oops which will help me diagnose any random reboots that may occur.

Happy flashing! - gsstudios ;)
[Galaxy S II Android Development] GreekDragon:
Dope AF
[Galaxy S II Android Development] lightmandn:
gsstudios , Kernel stop work with lp from 002 build. Any app take fc .
[Galaxy S II Android Development] Saber:
Is this still with RR LP? I'll have a look soon.

gsstudios

Edit: Are there any logs I can look at? I need a logcat to see what's going on. Thanks.
[Galaxy S II Android Development] lightmandn:
Can't take screen, because it fc too. Where I can get log? You mean kernel log?
[Galaxy S II Android Development] Saber:
You can use adb to get logs.

Logcat:

adb logcat > logcat.txt

Dmesg:

adb shell su -c dmesg > dmesg.txt
[Galaxy S II Android Development] lightmandn:
When i flash kernel, adb set to off, and app setting don't work too. Maybe you can tell me where in source code i can enable adb, and i make kernel for this?

Upd: after flash 001 and turn off and turn on adb, i can create logcat, but forum cant keem more than 30000 lines

That link to full logcat file

https://yadi.sk/i/LdNU0i04t9uUq
[Galaxy S II Android Development] Saber:
I had a look at the log and it seems that the problem is with the new Mali driver. I don't plan on fixing this issue only because this would require separate builds for older ROMs with this problem, and that becomes time consuming. Sorry but I only plan on supporting mainly Cyanogenmod ROMs.

gsstudios
[Galaxy S II Android Development] lightmandn:
i understand ... can i ask you? which rom will we greatest work on you kernel ?
[Galaxy S II Android Development] Saber:
Hehe :) I base most of my kernel changes to benefit Cyanogenmod ROMs. CM13 seems to run better on my kernel vs. CM12.1.

gsstudios
[Galaxy S II Android Development] lightmandn:
i think with xposed i can extend the CyanogenMod fo me, ok. At now on CM13 stay there problem with memory ( and agressive lmk) ?
[Galaxy S II Android Development] GreekDragon:
Running DorimanX on my Resurrection Remix test build, all works great. However, i had one SOD and that probably is because i did CPU UV.
[Galaxy S II Android Development] ahmadabumaizer:
Why aren't u on your latest build and what build do u recommended me using and so u recommended this kernel this RR marshmallow and so u recommended uber or linaro builds

Love ur work btw
[Galaxy S II Android Development] GreekDragon:
The build i am now is just to test if things works ok, battery etc, before i try dorimanx battery was ok here. I always use linaro. If you want to test the kernel, go ahead. I won't blame you.
[Galaxy S II Android Development] stylemessiah:
confirming that on the latest build 003 the wifi hotspot doesnt work......
[Galaxy S II Android Development] xn0live:
Is here anyone who used MM Rom like resurrection?

Is the kernel stable?
[Galaxy S II Android Development] Odran:
Can i overclock the gpu with this kernel on cm13?
[Galaxy S II Android Development] BenjyTec:
Did you read the first post?
[Galaxy S II Android Development] j1gga84:
it works but after flashing it seems to end up in a bootloop but after 2 reboots it gets over the dorimanx logo and booted fine :good:

regards
[Galaxy S II Android Development] Saber:
I will have a look at this later. Please provide logs.

gsstudios
[Galaxy S II Android Development] lightmandn:
Gsstudios, how i can turn off swap and make kernel without this future? Can you help me?
[Galaxy S II Android Development] Saber:
It's in the memory tab of stweaks. Set swappiness to 0 and you will only use RAM.

gsstudios
[Galaxy S II Android Development] Saber:
DorimanX 12.0 b004 has been released!

There were some exciting changes in this build. We now have advanced support for F2FS mounting, so the kernel script should now properly maintain your F2FS partitions. I have tested F2FS on my /data and /cache partitions and it has been stable so far. You can try it out if you want to experiment with it, otherwise I would still recommend using ext4 anyway. Note: You may get file system error popups on boot. You can safely ignore these as it will only complain about your partitions not being formatted as ext4.

Edit: Next build will fix this issue.

Exfat got updated to the latest DorimanX sources. I have changed the default hotplug method for zzmoove to alucard and disabled zzmoove native hotplug to prevent conflicting hotplugging. Temperature export support was also added to zzmoove to support temperature specific features.

Lastly, mass storage USB mount has been fixed for LP as the previous fix only worked on android marshmallow.

Happy flashing! - gsstudios ;)
[Galaxy S II Android Development] arnab:
Exfat and ntfs fuse wont matter as cm uses non kernel based exfat and ntfs 3g
[Galaxy S II Android Development] stylemessiah:
Here you go, logged the effects of toggling the HotSpot on

Also, after a couple of days use i was starting to get some lag....

cheers gsstudios
[Galaxy S II Android Development] j1gga84:
It seems that Dorimanx has issues with Resurrection Remix 5.7.0 in combination with Xposed :confused:

When I flash RR with Gapps, Dorimanx, SuperSU 2.76 everything is fine but after flashing xposed system wont boot anymore, even after uninstalling xposed and dirty flash of RR, Dori and SuperSU system does not boot anymore and I have to perform a fullwipe..

A user that is running stock kernel with RR has no issues after flashing xposed, system boots up properly :confused:

maybe it has something to do with the selinux state!?

regards
[Galaxy S II Android Development] Saber:
Yes, the kernel is somehow incompatible with xposed. I will investigate this problem soon with realex-fire.

gsstudios
[Galaxy S II Android Development] Saber:
WiFi driver seems to be the problem. I'll see if I can do anything to fix it.

gsstudios.
[Galaxy S II Android Development] Saber:
DorimanX 12.0 b005 has been released!

Wifi hotspot has been fixed. People who use this feature please confirm that it has been fixed.

F2FS partition error boot log has been fixed. Default I/O scheduler has been changed to CFQ.

Happy flashing! - gsstudios
[Galaxy S II Android Development] ahmadabumaizer:
What about xposed?

Love ur work btw
[Galaxy S II Android Development] Saber:
I am looking on it. Hopefully we can fix it soon. :)

gsstudios

Edit: Once again, logs would help greatly in our efforts :)
[Galaxy S II Android Development] jamu08:
I flashed the latest dori Kernal b.004 with xposed v86 installed in latest RR 6.0.1 build. However, I tried cleaning cache/dalvik cache after flashing the kernal but it stuck in the boot. then I tried dirty flash without cleaning cache/dalvik cache n got successeded. Happy flashing [MENTION=5811506]gsstudios[/MENTION].....please improve the battery backup by managing wakelock, alarms and services.....anyways thnx a ton.

---------- Post added at 03:55 AM ---------- Previous post was at 03:51 AM ----------

[MENTION=4699854]j1gga84[/MENTION]...…why SuperSU bro.....isn't it inbuilt in RR? Did u encounter any problem with SuperSU 2.76 and in built SU in the RR?
[Galaxy S II Android Development] ssanjy:
Similar experience in Beanstalk ROM too.....I haven't tried without Xposed but after flashing kernel, if I wipe art and cache then phone botloops... Without wipe boots fine... However it did gave me random reboots.... Since developer has based development mainly on cm13 I guessed other ROMs will have issues and hence I've returned to stock from my backup....
[Galaxy S II Android Development] j1gga84:
Okay but NOT wiping cache/dalvik for running xposed properly can't be the final solution so I will wait until [MENTION=5811506]gsstudios[/MENTION] has looked into this issue :good:

Concerning SuperSU:

I flashed the System-mode SuperSU and I did not have any problems :good: When xposed is fixed I will try it again with normal systemless SuperSU, allthough my system partition is big enough (1GB System, 8 GB Data ;) ).

Regards