yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Saber:
The problem shouldn't be caused by hotplug method, it has been stable for a long time on our kernel. Just in-case you didn't know, Auto hotplug will set the hotplug method to intelliplug for all govs except Nightmare, Darkness and zzmoove.

IMO, I think it was the OOM management that needs to be fixed on our kernel, but I don't have much time to investigate it anymore (hence the no longer updated status in the OP)

gsstudios
[Galaxy S II Android Development] Skyline:
Yes i saw status in OP

Thanks, I understood it now. I didn't know this before.:D
[Galaxy S II Android Development] LeBourrin:
For me, no more launcher force close since I installed beta31, 7 days ago :good:

- Beta 29 and CPU gov "on demand" = Launcher FC

- Beta 31 and CPU gov "on demand" = no more Launcher FC

Others sTWeaks options are default (except BLN)
[Galaxy S II Android Development] ahmadabumaizer:
After i falsh this kernel i reboot and after the kernels boot animation finishes the screen goes black and nothing happens after that
[Galaxy S II Android Development] Saber:
What ROM are you using? Did you try wiping cache partition after flashing the kernel? Reflash kernel and see if it works, otherwise you can reflash ROM and try again.

gsstudios
[Galaxy S II Android Development] Saber:
I will see if I can push out a build tomorrow with all of the changes I've tested. Don't want to keep things in the testing list when they already should be available for everyone to use ;) Will be the last build for LP, I'm already back on KK as I don't plan to continue updating for a while.

gsstudios
[Galaxy S II Android Development] wdevil12:
it's good to know that we will get another awesome update.. but why you're back to KK?:) I re-read it 3 times more to make use if it's not MM :D
[Galaxy S II Android Development] kulitom:
[MENTION=5811506]gsstudios[/MENTION] any chance to fix launcher FC in next build?
[Galaxy S II Android Development] Saber:
DorimanX 11.0 b032 has been released.

This will be the last build for DorimanX kernel as I will now be away from kernel development. Sadly, this means we won't see MM kernels from me as I don't have time to work on the kernel anymore. Please look at the changelog for the list of changes in this build. I have tested all changes and it is working fine.

gsstudios
[Galaxy S II Android Development] MikiGry:
[MENTION=5811506]gsstudios[/MENTION]

That is sad. Anyway. Thank you very much for your all affors you have put into XDA. You resurected DorimaX kernel for AOSP 4.x , 4.4.4 and 5.1.1 roms. You answered a lot of questions. Never skipped a single one. I dont want to press the thank button , becuse it will look wirdly (You quiting the development and me thanking for that[emoji14])

Anyway. I am running v31 on Makox CM 12.1 and i have a ... bug ? After i booted the device kernel was woring , but the supersu was missing , but built in CM root managent seem to work fine with STweaks. Even better. It takes 4 seconds to load STweaks. The only annoying thing is , that sth. keeps using root acces , and as a result i cant get rid of # sign on statusbar.

And with v31 one day after instlling that i have been expiring almost constant Trebuchet FCs and freezes (ondemand bug). After instaling Nova and swithing to Zzmove/fiops (awake) and sleepy/sio (sleep) launches FCs seem to be gone.
[Galaxy S II Android Development] j1gga84:
Very sorry to hear that there will be no Dorimanx for MM, I was hoping till now.. :(

Anyway, many thanks for your work for our S2, it was a good time but every time comes to it's end.

I guess you will get another device and that is the reason why you stop development.

regards
[Galaxy S II Android Development] Saber:
Try build b032. Right now, I'm not experiencing any FCs on the latest build. Still too early to confirm.

gsstudios.
[Galaxy S II Android Development] wdevil12:
I cant even post what I'm feeling right now. But.. nothing is invariable.. I understand that.. I love your work. Thank you [MENTION=5811506]gsstudios[/MENTION]
[Galaxy S II Android Development] Saber:
I have tested my latest build for almost 24 hours now and I haven't encountered a single FC. I have opened and closed apps that use heaps of RAM, open and closed system apps. For now, I can say that FCs have been solved :) Please note that I'm testing on Trebuchet (CM launcher), however it should also be fine on nova launcher and etc.

gsstudios
[Galaxy S II Android Development] prazola:
[MENTION=5811506]gsstudios[/MENTION] ...I'm crying so hard. :((((((((

I hope the best for you, thx for your work <3
[Galaxy S II Android Development] LeBourrin:
I'm sad too.

But I thank you for all the hard work you did to port DorimanX to Lollipop :good:
[Galaxy S II Android Development] davidcie:
I encountered a weird thing, maybe someone will be able explain. Device was lagging a lot after half a day of usage to the point of being unusable (unresponsive keyboard, text messaging app taking 30s to open, etc). Having experienced similar behaviour with ZRAM with other kernels, I disabled it it STweaks and things seem to have improved by about 50% and phone is now usable but still very laggy compared to OMNI 4.4.4.

What does surprise me thou is how no matter how many apps I run, I still see only half of RAM being utilized (see screenshot). Is this normal? Is this even true, ie. should I believe the system gauge? Is it possible that OOM manager is going crazy here or that perhaps OOM killer is leaving some space for ZRAM despite it being turned off?

Basically, can anyone guess what is going on here? :)

(Linaro b032 on latest CM12.1 nightly of 20160203, all settings at default values aside from ZRAM off an

IO set to sioplus.)
[Galaxy S II Android Development] Saber:
OOM does have a habit of closing background apps that are not used very aggressively when you check this (I always see a bit of lag checking with stock OOM manager before seeing that there is a noticeable increase of free RAM). However in Diskinfo, it will show me if there is less RAM available and doesn't free up RAM randomly. In other words, OOM is still quite aggressive and there is no problem with having this amount of free RAM unless you start getting FCs.

gsstudios
[Galaxy S II Android Development] davidcie:
Thanks for your reply. Indeed, DiskInfo seems to present a lot more accurate information than the system chart!

I was pondering upon OOM behaviour because I suspected it might be the cause of my problems but from what you are saying it may not: I get no FCs at all, just general lagginess. You can see what I mean on video here. It takes ~20s for Maps to open, over a minute for Drive and Sheets, 10s for Messenger (the text message app, not Facebook Messenger), 6s for the Phone app... This is very different to my previous KitKat experience. I do not mean it in a complaining way, just wondering if this is what everybody else is experiencing and hoping that: (1) it is not and (2) there is some setting I got wrong that might sit at the root of the problem.

(All partitions have been TRIM-med and phone rebooted a few minutes prior to recording. Things get a lot worse after a few hours of general use.)
[Galaxy S II Android Development] Saber:
Those delays seem way too long compared to anything I've seen. Because I've only experienced freezing once in a while and afterwards, everything is back to normal. What stweaks settings are you using? Try running default profile with no ZRAM if you haven't done so. Can you provide any logs?

gsstudios
[Galaxy S II Android Development] davidcie:
Thanks again! Inspired by your hint I loaded a power efficient profile in STweaks, rebooted, loaded the default profile and rebooted. Did all this just in case some kernel settings were messed up from the kernel + Kernel Adiutor combo I used prior to DorimanX. This seems to have improved things considerably! It has only been a few hours thou, will report again in a few days if this cured my lag problems once and for all.
[Galaxy S II Android Development] davidcie:
Sad to say but little improvement. For the first few hours the phone behaves normally, quite snappy, apps do open quickly. But at some point it seems to succomb to sudden memory pressure and falls flat on its face — from there on opening most apps takes forever, UI is very laggy, phone not responding to home/power button presses for as many as 10 seconds and generally barely usable. Manually closing apps does help but only a reboot really brings it back to life.

Default STweaks profile tested with ZRAM both on (300MB) and off. The default CM12.1 kernel suffers from the very same problem on this device; as wife run out of patience it will be going back to KitKat days over the weekend :)
[Galaxy S II Android Development] Odran:
Does this kernel works on CM13?
[Galaxy S II Android Development] Saber:
No. It doesn't work on CM13.

gsstudios
[Galaxy S II Android Development] mordan:
Hey, awesome people! Just wanted to say thank you for keeping this phone alive for us, for such a long time :) You rock!
[Galaxy S II Android Development] aaronfiji:
Is there a Marshmallow 6.x.x kernel coming soon? That would be amazing :D
[Galaxy S II Android Development] j1gga84:
No, I fear we will never see a MM Dorimanx for our S2..

That would be amazing in combination with CM13.0 by Markox89 but I think we have to run stock kernel from now on or remain on CM12.1, which is not the worst idea because CM13.0 is not yet running good at all on the S2..

On the one hand it would be interesting to know why gsstudios stopped kernel development in general - not only for S2 - but on the other hand I can understand it, especially for the S2 because it is an old device and developers move on to newer devices..

regards
[Galaxy S II Android Development] wdevil12:
Finally DU-M is released. So migrating from cm12.1+dori to unicorns 10.1+arnab's custom kernel is the best choice for me. After testing, reading reviews, changelogs, bugs I didn't like cm13 at all.
[Galaxy S II Android Development] LeBourrin:
I still have Trebuchet launcher crashes with last DorimanX beta.

I've found the solution by changing "Background process limit" in the "Developers options". I set it to "4 process max" and now my S2 is flying.
[Galaxy S II Android Development] Saber:
I will be resuming this investigation sometime soon once I have finished some of my uni work. There is a build in the works ;) (Probably won't be released this week or week after because I am quite busy nowadays)

gsstudios
[Galaxy S II Android Development] lightmandn:
This night i take this kernel sources from github and compiled it with llatest commits. Phone began work is much better, but i had turn on aggressive lmk and reserve on boosted. Keep it up gsstudios !
[Galaxy S II Android Development] Saber:
Thanks for the feedback. I tried downloading my repo this morning but the connection to github was so slow (200kB/s max, where I would use to get at least 3 times faster back in the days).

Pretty sure it isn't a problem with my internet :)

gsstudios
[Galaxy S II Android Development] Saber:
My build environment is all set up now :)

Repo has been downloaded completely and now ready to make new builds (I haven't done any testing yet, so more changes will come later). I will go back to LP ROM soon.

gsstudios
[Galaxy S II Android Development] arnab:
Hey josh tell me one thing did u disable selinix and tried in cm13 ???
[Galaxy S II Android Development] Saber:
Selinux is disabled when I tried to boot into CM13 (when using CM13 kernel). Wasn't booting and no boot animation.

gsstudios.
[Galaxy S II Android Development] mco2015:
I had alot of FC's. I limited to 4 processes like leBourrin suggested. It improved, but still get 5+ FC per day.. :(
[Galaxy S II Android Development] Saber:
I'm testing one of my recent test builds and it seems fine for now. I'll give it more time before concluding.

gsstudios
[Galaxy S II Android Development] LeBourrin:
Yes, this trick does not 100% fix the trebuchet crash. I have one from time to time. It may depend of the apps you use.

I've just got a crash this morning just after a screen wake up. I've looked at the logcat but there is no usefull informations. Anyway, this is not a memory problem because I had 300 MB free when it crash.
[Galaxy S II Android Development] j1gga84:
So do you consider to bring DorimanX to CM13 one day? :fingers-crossed:

regards
[Galaxy S II Android Development] Saber:
Yes, it is on my to-do list. Not soon because I need to fix the problems in lollipop first before leaving lollipop development.

gsstudios
[Galaxy S II Android Development] arnab:
Lol josh.. I know if u leave smthing halfway it keeps eating u alive inside. :laugh:
[Galaxy S II Android Development] Saber:
Build b033 has been released.

Yes, as you may have already known, I have continued development on the lollipop branch. :highfive:

As for MM, it's on my to do list as explained in a previous post. I'll fix the current problems in lollipop first then I will move on.

This build has no major changes. However, it does contain some important changes.

I have reverted back to aggressive LMK profiles, reverted VM changes and pulled few updates from CM. Overall, my phone feels smoother than the previous build.

Also, if your stweaks profile doesn't reset, just be sure to reset it manually in recovery.

Happy flashing, gsstudios ;)
[Galaxy S II Android Development] Saber:
If you are still getting launcher FCs, and if you are using nova launcher, you can enable a setting called aggressive desktop. See if this setting helps.

gsstudios
[Galaxy S II Android Development] lightmandn:
Hi gsstudios. I noticed that when you reach a certain amount of memory device starts to slow down. At this kernel - about 180 megabytes. In stock - 50. I understand that begins recording on the drive? Is there an option expands the amount of memory used as stock?
[Galaxy S II Android Development] Saber:
Are you talking about free space? It could be due to memory leaks that I haven't found yet in the kernel or zram or LMK as the kernel is struggling to keep up with the demands of the user.

gsstudios
[Galaxy S II Android Development] lightmandn:
Yes, about free ram space. If the free memory is less than 180 megabytes - the device slows down. On stock - 50mb or low. ZRAM is not affects on this situation.
[Galaxy S II Android Development] Saber:
It would be as I said before. The kernel memory management still needs to be improved, and right now kernel is struggling. Hopefully in future updates I will be able to find the root cause.

gsstudios
[Galaxy S II Android Development] lightmandn:
We are pleased to join the testing
[Galaxy S II Android Development] Saber:
Starting from next build, we will have UBER 6.0 experimental builds. There is a small performance difference between UBER 5.3 and UBER6.0. I'm still testing the stability and battery life of the new toolchain.

gsstudios ;)
[Galaxy S II Android Development] LeBourrin:
A crash log for you

I've installed beta 33 last night and I'm heavily using my phone in order to reproduce Trebuchet crash. I don't modified the Process limit in developer options. All is good, no crash.

But this morning Trebuchet get a crash while I was using Chrome et memory was very low (under the 180 MB).

This time catlog have messages that may be useful for you gsstudios. Crash appends after 11:17.

Notes:

- I have many skipped frames because of low memory

- You will see many GMS Authentication errors in my catlog. It's not linked to crash. I was activation double auth on my Google account.
[Galaxy S II Android Development] mco2015:
Exactly the same as LeBourrin.

Installed 33b, and only 1 FC this morning. Trebuchet.

Do you reccomend NOVA launcher?

This version has lower framerate sometimes, but much more stable I agree.
[Galaxy S II Android Development] Saber:
I get no FCs with nova launcher when aggressive desktop is enabled. It keeps the launcher refreshed in memory and hence prevents this heap corruption from happening.

Still investigating the root cause.

gsstudios
[Galaxy S II Android Development] Saber:
Build b034 has been released.

The main highlights of this build is the inclusion of new UBER 6.0 builds. There is a small improvement over UBER 5.3, battery life is about the same. Although it is experimental, it has been as stable as UBER 5.3.

Other changes include changing the default I/O scheduler to ZEN and reverting lowmemreserve ratio values.

Happy flashing, gsstudios :)
[Galaxy S II Android Development] Saber:
Thanks for the log.

I'm testing a commit for LMK that should prevent a kernel crash from happening when RAM is running low. Fingers-crossed this helps with the issue :)

gsstudios
[Galaxy S II Android Development] marcimix:
Is possible that recognition voice: "OK google" is worst than official kernel from CM12.1? I have this feeling.
[Galaxy S II Android Development] Saber:
Alright, tested the LMK commit that I pushed last night and it seems that launcher FCs are gone. Launcher process is killed properly by LMK and no more kernel freeze :) Still need more testing but so far it looks good :)

gsstudios
[Galaxy S II Android Development] Saber:
Build b035 is out!

This build contains exciting new changes. I have updated stweaks with material design thanks to [MENTION=5798657]Skyline[/MENTION]. LMK will now kill system and protected (root) apps and services to prevent kernel crash. Before, kernel would crash if LMK couldn't kill these protected/system apps, so now it should be all good. I have also noticed that the kernel is more responsive under heavier loads compared to previous builds. Kernel testers please see if this helps with Launcher FCs, because I haven't had a FC for a while now. If you get more random FCs, let me know :)

Various security and stability fixes were pulled from CM13 kernel.

Happy flashing, gsstudios :)
[Galaxy S II Android Development] LeBourrin:
Wow gsstudios, that's incredible! Three things:

- System is more faster to free RAM when needed. (Before that, free RAM stay low for several tens of seconds)

- System is more responsive when RAM is under 180 MB

- For now I was not able to crash Trebuchet. One time I see it quick restart (when wallpaper is black and reappear)

Good job! :good:

I continue to test it and I tell you if I have FC.

PS: Nice new STweak
[Galaxy S II Android Development] Saber:
How are you guys liking material design in Stweaks? Personally, Stweaks looked very dated before I updated it. Now it looks great :)

gsstudios
[Galaxy S II Android Development] LeBourrin:
I like it, it's modern. But it would be better if tabs were not black. It's too much contrasted with the white below. A gray or a color would be sweeter.
[Galaxy S II Android Development] :
So far v035 is great, no problems and running smooth. Could be "stable" for me.

Running with cm-12.1-20160406-UNOFFICIAL-i9100 by [MENTION=5302855]CNBLACK[/MENTION]

Yeah I like it. It suits LP/MM style a lot more; the old style was more KK
[Galaxy S II Android Development] Gent':
Can you please bring this kernel to Cm13
[Galaxy S II Android Development] Saber:
Its on my to do list.

gsstudios
[Galaxy S II Android Development] Muhammadsoli:
Hello gsstudios. Sorry for offtop. I wanted to ask a question: I saw a Galaxy S in your devise list, so i have a korean one. And i was wondering whether it is possible to convert the shw m110s to the international one as i did with my shw m250s?
[Galaxy S II Android Development] psychoid:
Where to find the aggressive desktop?im on b35 [emoji54]
[Galaxy S II Android Development] prazola:
Is an stweak reset required for b35?
[Galaxy S II Android Development] LeBourrin:
So I continued to try to cause Trebuchet FC and I have none. After 24H it's stable. Are other testers have the same result?

[MENTION=5322909]prazola[/MENTION] personnaly I do a stweak reset before every Dorimanx updates
[Galaxy S II Android Development] Saber:
I managed to cause a few FCs yesterday, although they didn't appear anymore when I tried forcing it to. :confused:

I will promote build b035 status to stable.

gsstudios
[Galaxy S II Android Development] :
I have tested and had a soft reboot while charging overnight(once), but no FC's or any other instability.
[Galaxy S II Android Development] mco2015:
I've had a few FC, but with faster recovery.

However, overall, i find the system slower in response, and many times i get blank or black screens (waiting on apps), much more often than on previous builds.

This was my first UBER try. I will instal Linaro 035 and see what happens.
[Galaxy S II Android Development] :
Change the I/O to CFQ or Deadline.. For me they are more responsive and stable. App Loading times are also considerably Faster. :p
[Galaxy S II Android Development] semcem:
Thank you very much for this great kernel,

Just a quick question and demand, why not supporting VPN networks? is it possible to get vpn support on this kernel?
[Galaxy S II Android Development] Saber:
I don't know for sure but our kernel's WiFi module is not working on LP. It is either this or some other problem with the WiFi driver in the kernel.

gsstudios
[Galaxy S II Android Development] Saber:
Build b036 is out!

I have tested this build with the optimizations found in [MENTION=4354573]chhapil[/MENTION]'s JB kernel since this morning and it has been running very smoothly. In fact, this is the smoothest release so far because we were missing these optimizations in previous builds ever since this kernel was updated past linux kernel 3.12. Battery life has still been pretty good and performance is slightly better on all builds. Kernel testers please let me know if this build introduces any problems so I can solve them quickly.

The default I/O scheduler was changed back to CFQ.

Happy Flashing, gsstudios ;)

OT: Screenshots updated
[Galaxy S II Android Development] mco2015:
After 3 days of Linaro 035 use, i've had slower phone, a few FC and many slows, many. only use apps like Google Calendar, Whatsapp, Telegram and 2 games: Boom Beach and Clash Royale.

Previous builds were faster, but more FC's..

Do you recommend 036 Linaro or Uber with Resurection Remix ROM?

It's really hard to decide.

But I will try 036 for a few days and report back.

PS: Im not idiot, but I searched and I really can't find how to post logcats here.. I would like to help with that. Any1 can link me or explain me how to logcat i9100? Thanks
[Galaxy S II Android Development] Saber:
Try the uber 6.0 or 5.3 builds. The performance difference over previous builds is more noticable than the already optimised linaro toolchain builds.
[Galaxy S II Android Development] arnab:
Look Josh every time toolchain can't bring u optimization however much u try...why don't u try to add f2fs...it has auto discard feature...Blv me it makes a huge performance difference. Recent linaro versions do not have a9 specific..so I never moved from 4.9...and while Uber is better..if your kernel has multicore power scheduler...or schd_mc...it's better to stick with linaro with the a9 variant.
[Galaxy S II Android Development] Jack122:
I need cm 13 Version.
[Galaxy S II Android Development] LeBourrin:
With Linaro beta 35 my phone is slow when memory is low. So I suppose this is what appens to you. Monitor your free RAM with Cool Tool app.

But unlike you, i don't have FC with beta 35. I switched to beta 36 Uber which is just as stable, currently.
[Galaxy S II Android Development] Saber:
B037 will be released later this week. I've been busy in the past few days and was unable to make many changes to the kernel. So it will just be a small update :)

gsstudios
[Galaxy S II Android Development] mco2015:
Well, i changed to beta uber 036, and i still get alot of trebuchet crashes and blank screens (loading apps for 10+ secs). memory when FC is always 350+ free.

I used hawkercore to kernel wipe, and hawkercache wipe.

I thank you for your work.. but really dont' know what else i can do. And i'm sorry i don't know how to logcat.

When you release 37 I'm going to try reinstall whole ROM.