yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Saber:
For fully working fs:

- Vfat

- FAT32

For semi/partial working fs:

- NTFS

- Exfat

Not working:

- Ext4

- I guess Ext3 and Ext2 are not working as well, but usually people use ext4 instead

In other words, use fat32 or vfat for most stable experience. All other fs is known not to work so well with this kernel.

gsstudios
[Galaxy S II Android Development] y0.o!:
Top work buddy, keep it up!
[Galaxy S II Android Development] y0.o!:
When are you doing TWRP recovery?
[Galaxy S II Android Development] Saber:
As in including it with the kernel? Probably won't happen since this will remove dual boot functionality that has been included in DorimanX kernel since early days. Just flash TWRP isorec over this kernel and you have TWRP :)

gsstudios
[Galaxy S II Android Development] Jack122:
did that. because the dorimanx kernel always repartitions system parrtition when formating. im looking forward for cm 13 kernel. wont update to cm 13 until i have your kernel for it.
[Galaxy S II Android Development] Saber:
Important information to kernel users

I have been investigating the cortexbrain-script for our kernel and found that after tuning the vfs_cache_pressure value prevents the script from running when screen is on. (I confirmed this via adb catlog). While it is obvious in the code (only found out now :o ), this can bring serious performance issues. Although the variable is not available to tune in stweaks, it is still available in apps like kernel adiutor. The ability to tune this parameter was introduced a while ago, while it sounded good back then, and although a warning was given when first introduced, the script needs to be changed in order to allow the kernel to work properly.

A problem with modifying the script to allow vfs_cache_pressure tuning is that our device doesn't have proper notifiers to tell the kernel script that the phone has waken up, so we are still relying on this vm value that changes automatically on screen state.

As for which versions are affected, here is a list of builds that are affected by this 'bug':

As for builds that are not affected:

If you haven't tuned this parameter, there is nothing to worry about. No app or ROM will have this value changed, this bug is only caused when modified by the user. However if you have tuned this, please revert the value back to 60 to restore proper kernel functionality.

Next build will have this tunable locked to prevent any future issues.

gsstudios
[Galaxy S II Android Development] Saber:
Build b028 is up!

This build includes removing the ability to modify vfs_cache_pressure as it is used by the cortexbrain script. I have synced vfs_cache_pressure values with DorimanX LG G2 values to increase performance by freeing more ram, but reducing a bit of battery life. A few updates from the CM13 kernel was merged in this build as well. I have tested for many hours now and it is very stable.

As for the status for CM13 kernel, not much progress has been made. I haven't had time to debug problems yet, but now I will give LP a rest so I can concentrate on CM13.

Enjoy the build! - gsstudios

Update: As a push for everyone using 'stable' builds, I have marked b028 as stable. All changes since b020 has been pretty stable on the kernel, so I see no problem in doing this.
[Galaxy S II Android Development] Saber:
One other thing that I have been testing is intelliactive. Interactive was unstable on our kernel especially when you tune it in stweaks or even manually. Intelliactive however doesn't seem to have the same problem as interactive, it doesn't cause SODs and scales frequencies efficiently.

If all my tests find that the governor is stable, I will include it in the next build.

gsstudios
[Galaxy S II Android Development] patriot16:
anybody know relase date of kernle for CM13? approximately
[Galaxy S II Android Development] OllieW:
Already answered!
[Galaxy S II Android Development] Saber:
Important information for DorimanX users

Another discovery was found when I was looking through the kernel files. Once again it is to do with the kernel's script, but this time it's for CRON (auto task scheduler for optimization).

With the already known bug in zipalign, I have discovered that in the performance profiles, the zipalign task would have automatically run. This is bad for lollipop as it will remove all app simlinks in the /data/app folder. This behavior is caused from the incompatibility between zipalign and ART, where this task was only designed for Dalvik! As described by droidnforcer, wiping caches seems to recreate these simlinks and allows apps to work as they should. This problem only affects Android Lollipop as ART has been selected as the default runtime.

This buggy feature will be removed in the next build.

gsstudios
[Galaxy S II Android Development] stefano91av:
Hi [MENTION=5811506]gsstudios[/MENTION], The Speed ​​Mod is compatible with the changes resulting from various Stweaks profiles? :)

Besides these 2 screenshots are the results of the latest version of the kernel with your performance profile against the smooth kernel of the CM12.1 12.02.15 compiled by Markos .

For a lot of benefits in multicore :(

is only my problem ?
[Galaxy S II Android Development] patriot16:
i have one question, when the kernel for 6.0 will come out will it be compatible with IsoRec TWRP recovery with that i mean could i use TWRP recovery instead of kernels CWM recovery.
[Galaxy S II Android Development] Noctis Lucis Caelum:
DorimanX Kernel has been patched so it will be IsoRec ready.
[Galaxy S II Android Development] Saber:
Have you tried Linaro 4.9 build? This is what I get with latest unreleased build :)

Still not great meaning more work will need to be done :)
[Galaxy S II Android Development] prazola:
Actually the best on geekbench are pegasuq and zzmove.
[Galaxy S II Android Development] makix13:
Hi [MENTION=5811506]gsstudios[/MENTION],

Just a little question. It's seems, as [MENTION=414800]arnab[/MENTION] said in Isorec thread, now it's included f2fs support in our S2 (http://review.cyanogenmod.org/#/c/132900/) .

Could be possible to be included in a near future?

It's only to know your opinion, I know you have a lot of other things in your mind, but I think it's a good point to booster a little bit more our little boy [emoji6]

Thanks in advance

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Android Development] Saber:
Possible. We'll see when this gets merged into CM13 nightlies.

gsstudios
[Galaxy S II Android Development] makix13:
Many thanks for your quick answer and great work [emoji106]

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Android Development] arnab:
First I will have to make a new twrp with f2fs support. Then only u can format.
[Galaxy S II Android Development] Saber:
Next build will be delayed for some time. I think I have corrupted my build machine or my current setup on my phone. Whenever I make a new build, I get SODs. I will have to redownload my own kernel sources which may take a while. Was planning to change a few things for the next build but didn't turn out right, now I'm stuck in a tricky situation :) Hopefully this will be eventually resolved in the next few days (or maybe earlier).

gsstudios
[Galaxy S II Android Development] makix13:
don't worry and thanks for the info [emoji106]

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Android Development] chhapil:
I also had this same issue some days back, best way is to to create new vm machine and just mount old vm as HDD and copy the code again. I had spent many days to resolve this kind of issue.
[Galaxy S II Android Development] stefano91av:
I accidentally updated busybox through the app, from version 1.22 to 1.24.1. Now is there no written the stweaks. I cleaned the cache and Dalvik cache but no change. How can I fix?
[Galaxy S II Android Development] Skyline:
1.Uninstall "busybox 1.24.1" from Busybox

2.Reboot Device

3.Again install it in /system/xbin

See if it works. Same thing happened with me yesterday but now my busybox is resetted to inbuilt one i.e 1.22 automatically don't know how. But all my stweaks settings are gone
[Galaxy S II Android Development] stefano91av:
How should I do ? Can you give me a link to download :)
[Galaxy S II Android Development] Skyline:
I m talking about the path that we select in Busybox App to install busybox 1.24.1 binaries
[Galaxy S II Android Development] stefano91av:
Already it is installed in / system / xbin .

Now I uninstalled the 1:24 and I have to reboot the 1:22 , but Stweaks makes the same mistake .

I advice you to install the 1.24 again at this point ? but in / system / xbin unfortunately does not work ...
[Galaxy S II Android Development] Skyline:
I tried it multiple times and then got success. Try to reflash kernel or dirty flash rom thats all i can say now
[Galaxy S II Android Development] Saber:
SODs have been fixed for next build. Will add the changes that were previously thought to be the cause of the issues when it was actually CPU governor changes that were the main culprits.

gsstudios
[Galaxy S II Android Development] Skyline:
So Intelliactive is there or not??:confused:
[Galaxy S II Android Development] Saber:
I'm delaying the release of intelliactive as I want to get some important fixes out.

gsstudios

Edit: Although it is stable, I'm not convinced that it is a well working governor on this kernel. Seems too aggressive IMO. Anyway, will release it later as said.
[Galaxy S II Android Development] Skyline:
No problem. Thanks for reply
[Galaxy S II Android Development] chhapil:
This issue has been recurring, but there is no specific pattern for it. I faced this issue when I was trying to alucard governor and others. Phone dosnt give SOD as long as its not asleep. (screen on or connected vi USB or charger) I tried looking into logs but nothing fruitful. This led me to enable pstore but pstore doesnt seems to work on JB (Its missing something in init.rc and ramdisk args)

I guess now this issue has come on LP as well, makes it noteworthy.
[Galaxy S II Android Development] Saber:
build b029 is out!

I have solved all SOD issues that have delayed the release, however this meant that we won't see HYPER updates or intelliactive until future updates.

This release contains mostly bug fixes and performance enhancements, including the removal of the buggy zipalign and fix-permissions functions from stweaks and CRON. OOM values now properly restore on each wakeup and I have updated CFQ for more performance. A few other minor changes were also merged into the kernel. As you can see, I have been working to push out a stable release ;)

Enjoy the update! - gsstudios
[Galaxy S II Android Development] Jack122:
i tried cm 13 for 4 days i will go back to cm 12 for now. thx for the update.
[Galaxy S II Android Development] Dr AM:
Might get back to LL just for DorimanX :)

A quick question , Is there a way to reduce graphics on a specific game ?

I play Dungean Hunters 5 and on DorimanX kernel graphics becomes too high that causes the game to lag and after investigating I found that the graphics in this game changes by how much RAM on our device , as on DorimanX we have +800 mb and on stock kernels -800 ,, in +800 the graphics becomes better and that causes some lags on it

Sent from my GT-I9100
[Galaxy S II Android Development] j1gga84:
[MENTION=5811506]gsstudios[/MENTION]

many thanks for the update and your continuous work :good:

May I ask if you also plan to build MM kernel with Linux 3.15 ?

I think this is very outdated if you see here:

https://www.kernel.org/

Or do you plan to build new kernels based on official CM kernel like Apolo or gustavo_s kernel back in the days?

I think the kernel would run much better with a linux version that matches to the system, what do you think?

I know that it was a big project of dorimanx to upgrade kernel to 3.14/3.15 but times goes on and I don't know if this gives such a big performance boost. Under KK gustavo_s or Apolo kernel ran much smoother on my S2 than Dorimanx BUT dorimanx has the better customisations.

regards
[Galaxy S II Android Development] Jack122:
4.5-rc4 ****ing go dude :)
[Galaxy S II Android Development] prazola:
On one side, from 4.5 android support is easier than before, but I think that it need a lot of work to be optimized for GS2. gsstudios is still fixing 3.15 features, so I prefer to wait and let him reach his best on this 3.15.
[Galaxy S II Android Development] Saber:
Linux kernel updates are not very important for our kernel. Unlike many other kernels on XDA, we are running a hybrid kernel, parts from Linux kernel 3.0.x, 3.15.0 and all other versions as well. To upstream to 4.x will be very unlikely. We will just end up in a mess with more things breaking from all of the changes. IMO, upstreaming the kernel version will bring no significant performance improvements. It is better if we just backport features from newer kernel versions which will allow us to keep the already stable kernel that we have and enjoy some new features. This is what dorimanx has done in the g2, keep stable version of kernel, back port new features from newer Linux kernel. It just works a lot better than having to upstream the whole kernel version.

I won't be building other kernels.

gsstudios
[Galaxy S II Android Development] j1gga84:
I don't know what's wrong on my side..

I am using latest b029 Dorimanx Linaro in combination with latest CM12.1 by Markox89 and when I reboot the device it takes ages.. What could be the reason for that? :confused:

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

Home Launcher force closes happens with ondemand. Currently I am using zzmoove with zanezam battery plus profile since 2 days and don't face any force closes.

So I think something wrong with ondemand governor :rolleyes:

Edit: Attached another log
[Galaxy S II Android Development] Saber:
Was this after initial kernel install or rebooting in general? Using latest CM12.1 from Markox as well and reboot takes the normal amount of time. Maybe you have to use kernel cleaning script, or reflash ROM.

gsstudios.
[Galaxy S II Android Development] Saber:
I'll need to confirm this. If this is the case, ondemand based govs (e.g. HYPER, pegasusQ, etc) will have same problem as well. I get launcher crashes using HYPER.

gsstudios

Update: While I was investigating, I noticed that zzmoove was using alucard as the hotplug driver. I forced alucard hotplug for HYPER and all seems good for now. No crashes. I tested on intelliplug. A few minutes after switching between apps, I get launcher FCs. More investigation will be done but for now this is an pretty interesting finding.
[Galaxy S II Android Development] stefano91av:
Wanting to have the " default " profile is recommended to prolong the battery use ZZMoove ? And if so, what way ?
[Galaxy S II Android Development] Skyline:
Select CPU-Tunning(Awake) Tab in STweaks and scroll down till the end and again scroll up a little from there you can choose profiles.:good:
[Galaxy S II Android Development] Skyline:
:good:

You are pretty much faster:silly:

I was trying the same before a minute and you already done with it
[Galaxy S II Android Development] stefano91av:
thank you :)

And " default CPU governor ," have I to change in zzmoove ?

---------- Post added at 13:19 ---------- Previous post was at 13:05 ----------

Hi [MENTION=5811506]gsstudios[/MENTION] :)

I'm doing some tests with your latest kernel .

To optimize battery life I have followed and applied the advice from here .

The user [MENTION=5867207]v7[/MENTION] has checked my stats after 6 hours at off screen with your kernel the default profile.

He told me that there are two possible errors :

http://xdaforums.com/showpost.php?p=65404239&postcount=7966

Can you check it out ? Thank you :)
[Galaxy S II Android Development] Skyline:
Of course you have to change it first then select your appropriate profile and press 'push CPU tunning to GOV core'
[Galaxy S II Android Development] Saber:
Yes, will check it out later today. Will see if I can do anything.

gsstudios
[Galaxy S II Android Development] Saber:
Just updating on the launcher FC issue.

While before I thought that the FCs were occuring because of the hotplug method, I can not prove that it is the root cause of the problem. I have tried both intelliplug and alucard and FCs are still occuring. The thing is that it is not occurring often enough to provide me some logs on what is really happening. If you guys have any logs (logcat, dmseg, last_kmsg are all fine), this will greatly help me with coming up with a solution.

Thanks, gsstudios
[Galaxy S II Android Development] iistoryahi:
i miss this kernel tweaks :(

Is there a chance for MM ?
[Galaxy S II Android Development] Saber:
Not yet, about to release one more build for LP (now this one will be the last one for now), then I will only work on MM. No more LP builds for a while until MM kernel comes out.

gsstudios
[Galaxy S II Android Development] Saber:
[MENTION=5945732]stefano91av[/MENTION]

What modem are you on? If you don't have XXMS4, try flashing it or a modem that is at least newer than what you have. Those are modem/ril wakelocks and sometimes some older modems don't play so well with kernels.

gsstudios
[Galaxy S II Android Development] Saber:
build b030 is out!

I'll keep this short. SIO was updated to SIOplus, I've merged lots of updates to zzmoove, MDNIE support was added to stweaks, a few other minor changes to the kernel. MM kernel work will start now, LP kernel will take a break.

Enjoy the update! - gsstudios

P.S: I will still be investigating the Launcher FC issues.
[Galaxy S II Android Development] iistoryahi:
wow , your the best [MENTION=5811506]gsstudios[/MENTION]
[Galaxy S II Android Development] stefano91av:
it is I9100TDVOE1.

I have a i9100t... But use perfectly cm12.1 for i9100 :)

Inviato dal mio Elephone P8000 utilizzando Tapatalk
[Galaxy S II Android Development] stefano91av:
Forgive me if I write things not related to your thread , but I have a big problem .

Simply put , when you reinstall the rom 12.1 weekly doing before the usual 3 wipe and then installing your kernel , I find that this procedure is not me completely format your phone.

In fact I had installed the Dolby Mod with Viper4Android before reinstalling the rom 12.1 .

On restart always I haunt me .

I make 3 wipe through the recovery to attach with your kernel ...

you help me , please ? Thank you.
[Galaxy S II Android Development] Saber:
build b031 is out!

It was necessary for me to release this build as I thought that I shouldn't leave a WIP function to users. I have added a MDNIE override toggle and moved the MDNIE tuning into a proper script. MDNIE tuning from previous build was still a WIP, this time it is a proper solution. If your settings don't apply, make sure to re-enable override and make changes to settings again. HYPER governor was updated thanks to realex-fire. Now time to concentrate on MM kernel. :)

Enjoy the build! - gsstudios :)
[Galaxy S II Android Development] Saber:
Is this in StanTRC recovery or Isorec recovery?

gsstudios
[Galaxy S II Android Development] Noctis Lucis Caelum:
And here I was about to post about MDNIE not sticking after a reboot on beta 30, then you release beta 31.

Top star [MENTION=5811506]gsstudios[/MENTION], thanks for the update.
[Galaxy S II Android Development] wdevil12:
im on minimal os (aosp based/lightweight/all tweaks/more control than cm) and am missing dorimanx features a lot. I just fed up debloating cm stuff after every nightly/weekly and some cant even be removed. I hope one day dorimanx supports aosp too(( bye custom kernels for now((
[Galaxy S II Android Development] tandonald:
[MENTION=5811506]gsstudios[/MENTION] Good Day... May I request for for the next Dorimax to work for MoKee Marshmallow.. It does not work when I am MoKee Lollipop.... But it work from when I am on CM 12.1... it just that is shows a disabled SELinux.... MoKee is a wonderful ROM for SII but It is missing a wonderful KERNEL maybe you can work forit.. pretty please.... thank you!!
[Galaxy S II Android Development] Traace:
I'm pretty new to the i9100 world, so excuse me if this was already discussed.

While running Dorimanx i always get a error-log html which says my data is corruped.

- Tried to fix it with "Data fix On Off" but the system ain't boot afterwards

- Then i formated system, data, the sdcard and cache over TWRP and flashing the Rom again. After a successful boot the html error log says my data is corruped again.

The Error log shows stuff with ext2 and that his Superblocks are corrupted, but all my partitions are in ext4 expect the sdcard .

If i try to trimming it, the System hangs for a few seconds, crashing and rebooting afterwards.

However, when i try to trim with the "Trim Kernel" around here at xda, it works without any problem.

Any thoughts on this?

Sidenote: My eMMC is a VYL00M Fw:0x19 Date: 06/2011
[Galaxy S II Android Development] stefano91av:
Excuse me , but I only realized the mistake now .

In practice with your CWM as well as the usual 3 wipes I had to be " format system . "

Now all ok . clean and agile system with your kernel .

Thanks for version 31 this morning .

Have a nice Sunday. :)
[Galaxy S II Android Development] psychoid:
Anyone has problem connecting with vpn apps?
[Galaxy S II Android Development] Noctis Lucis Caelum:
It's known issue.
[Galaxy S II Android Development] adri_360:
What is the best governor for games? or in general the best configuration

Enviado desde mi GT-I9100 mediante Tapatalk
[Galaxy S II Android Development] Skyline:
Hyper is damn stable using it since last released update looks Great for performance and battery with io scheduler CFQ

Also undervolted CPU and set max frequency set to 1.3 GHz
[Galaxy S II Android Development] LeBourrin:
I've a BLN question.

With kitkat, STweaks was keeping buttons lights on after I power on and off the screen when I not delete the notification. (Thanks to Timeout=Always On, i think so)

With Lollipop, BLN are shutdown after screen power on then off.

Do you know how to keep BLN lights on after screen power on because I want to use an app that wake up screen at notifications.
[Galaxy S II Android Development] wdevil12:
once you have acknowledged about a notification by unlocking/pressing the power, lollipop doesnt keep lights on. About the app, lights aren't needed to use notifying apps. Try ambient display xposed module. its working great with proximity sensor
[Galaxy S II Android Development] wdevil12:
[MENTION=5811506]gsstudios[/MENTION] you may surely remove launcher fc from bug list. Its somehow fixed in b31. I have been using nova dorimanx ( upgrading from beta 8 or 9) for months and I have experienced nova fc expect 2 versions ( the first one was beta 26 or 28 and the second is this beta 31)

cheers!
[Galaxy S II Android Development] Saber:
Launcher FCs still occurred for me when using CM launcher. It is very random and hard to reproduce.

gsstudios
[Galaxy S II Android Development] Skyline:
Frequency of fc's is get increased when i changed hotplug to auto. While using Intelliplug its negligible. Don't know about alucard as i m using intelliplug since last release.

Forgot to say I am on Hyper and CFQ
[Galaxy S II Android Development] Lanchon:
hi! could you please clarify what you mean by that? are you talking about the kernel image self-extract? are you saying that the lzop decompressor is too big to fit in the kernel partition alongside the compressed kernel? thanks!
[Galaxy S II Android Development] Saber:
Yes, I'm talking about the whole kernel image. The ramdisk will be wayyy too large for the s2 which will stop the phone from booting. I think it was around 100MB for the limit for our ramdisk size (correct me if I'm wrong).

gsstudios