yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Saber:
Sorry guys, build v029 came with the incomplete changes to zzmoove tunables. Please be aware that the afs_threshold tunables will not work properly yet and a few other zzmoove tunables are also broken. Please wait for the next build for fixes.

regards, gsstudios

Build v030 is released. Sorry for the inconvenience

[MENTION=6128498]ajrajr155[/MENTION], I'm testing interactive as we speak.

Next build will have interactive CPU governor added back. The governor is from a more stable source than the previously modified one found in early dorimanx 8.xx kernels that used to cause SODs. Now most issues are fix and the governor is now reliable again. More tests will need to be done before I release build v031.
[Galaxy S II Android Development] Saber:
Build v031 has been released! This build readds the interactive CPU governor that was missing from this kernel due to previous instability issues. It's all fine now and has been very stable with more than 12+ hours of uptime without SODs. Battery life and performance is good with interactive, and scales very efficiently.

regards, gsstudios.

Also, I noticed some people are still on build v024, please update to the latest version to get all of the improvements done on this kernel.

I Also noticed that some people are using different governors on the kernel. Any suggestions on the default CPU governor? Personally I still think HYPER is the default for a good reason, because it is very reliable.
[Galaxy S II Android Development] souler456:
Is interactive governor tunable on Stweaks? Or should I use Kernel Adiutor on it?

:D :) ;) :good:
[Galaxy S II Android Development] Saber:
You can use either app. However, I recommend using stweaks so there is less conflict with the kernel scripts and the kernel tuning apps. In stweaks, interactive is at the bottom of the CPU governor list and can only be set as the awake governor.

regards, gsstudios.
[Galaxy S II Android Development] ajrajr155:
We can't change interactive values in stweaks... We can choose interactive but we can't tune it to faster or slower scaling..

I'm using init.d script to tune interactive
[Galaxy S II Android Development] Saber:
My bad. I thought you guys meant that you couldn't set interactive. Yes, I haven't added tunables or variable tuning yet in stweaks for interactive. Hopefully by next build, I will be able to add it. [MENTION=5075251]souler456[/MENTION], in this case, use kernel adiutor for now.

Regards, gsstudios

I'll take a break from kernel development (Probably about 1 months) . All of the problems trying to merge the new interactive governor with the old is giving me a headache, and is too hard to work with with the hybrid kernel that we have.
[Galaxy S II Android Development] Saber:
It was a tough job but I added interactive tunables to stweaks. The reason why it was difficult was because interactive kept playing up when I tuned the govs, giving SODs and freezing for some odd reason. It's all fine now so the build should be ready by tomorrow after some more testing is done. zzmoove tunables will also be added in the next build too, after discovering my silly mistakes from last time.
[Galaxy S II Android Development] OlMightyG:
thanks for your work!!

since I am not using interactive or zzmoove, is there a reason to upgrade from v30? any other fixes?
[Galaxy S II Android Development] Saber:
Just interative governor that was added. Stay on the current build if you think it is working fine.
[Galaxy S II Android Development] Saber:
can't release today since I'm still getting SODs with the latest version. I think it is because all of the kernel mess I've created trying to get the tunables correct. I will have to start from scratch to solve these problems (now that I've got more experience).

regards, gsstudios

Update: I think I can confirm that the issue is with interactive CPU gov tunables in stweaks. The cortex script found in this kernel has some issues changing interactive variables, but works fine with all other ones. It changes the values, but gives SODs when screen is off.

Update 2: I won't be able to release a build with interactive tunables, there is no way to tune it but manually or via init.d scripts (or other apps). Otherwise the kernel is too unstable to use. However, I'm releasing build v032 with zzmoove tunable fixes. TRIM and NON-TRIM builds have been released.
[Galaxy S II Android Development] Saber:
[MENTION=5075251]souler456[/MENTION] and [MENTION=6128498]ajrajr155[/MENTION]. How are you guys finding the stability when tuning interactive gov via different app or via scripts?

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

Will you add odemandqplus grovenor ?
[Galaxy S II Android Development] ajrajr155:
Extract the zip and put files in init.d folder and change permission to 555

*I'm not using it right now so its not 100% but it should work fine
[Galaxy S II Android Development] Saber:
Thanks, but I was asking about the stability.

Regards, gsstudios
[Galaxy S II Android Development] ajrajr155:
Sorry didn't get the question right

Are you asking if interactive is stable?

If yes it was pretty stable for me no SOD or freezes
[Galaxy S II Android Development] Saber:
Are you talking about ondemandplus? I will have to see as it wouldn't natively work on our device.
[Galaxy S II Android Development] MikiGry:
[MENTION=5811506]gsstudios[/MENTION]

On my old galaxy s adavnce we used to have 2 ondemand grovenors.

Odemand and odemandq

I my opinion odemandq was much more optimaliseited for bettery live and perfornance.

Why ondemand(q)plus wont natively work on our device ?
[Galaxy S II Android Development] Saber:
Build v033 has been released. This build comes with lionheart CPU gov from [MENTION=4354573]chhapil[/MENTION]'s source. Not much testing has been done but it seemed stable when I was testing it.

regards, gsstudios
[Galaxy S II Android Development] souler456:
Can you please tell me what terminal commands should I use to adjust the mxt_224 touch. I want to change the values of them without entering Stweak, since Stweak is kinda really slow to open...

Edit: I also cannot edit build.prop, mainly, the dalvik.vm.heapsize and related stuff... Modifying ro.sf.lcd.density is fine.

:D :) ;) :good:
[Galaxy S II Android Development] Sziklián:
Is it possible to set touchmove sensitivity (vitalij value) with this kernel?
[Galaxy S II Android Development] j1gga84:
For me the sensitivity is good but while device is on charger (original Samsung - tested several diverse original chargers) it is a bit difficult to "hold" a position.

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy S II Android Development] Sziklián:
I mean you have to move screen 8 pixels, until it detects movement. This app can test it: https://play.google.com/store/apps/details?id=com.tegrak.touchmove

If it was 0, the screen could detect movement by moving just 1 pixel on the screen. If it is 8, you must move 8 pixels on screen, while the screen does not detect move, and when decects it, the content on the screen will move 8 pixels suddenly, not one by one.

In older Dorimanx kernels, there was an option in Stweaks to set this value to 0, but unfortunately it has been removed.
[Galaxy S II Android Development] Saber:
It would be nice if you could give the specific version when it was able to be adjusted, otherwise I won't know what version to revert to.

regards, gsstudios
[Galaxy S II Android Development] Sziklián:
It is fully working on Dorimanx 7.46 and Siyah v6.0b5, I know that Dorimanx 8.33/9.33 supports it too but couldn't find a working download link.
[Galaxy S II Android Development] Saber:
hey guys, as you may or may have not noticed, it seems that the recent changes in the last few builds has caused some instability issues for some people. I will start by reverting lionheart governor, then reverting the bugged interactive governor that still doesn't stable enough to my likings.

Please revert to v031 or earlier if you have issues with latest builds.

regards, gsstudios
[Galaxy S II Android Development] souler456:
Can you fix the unmodifiable build.prop bug? :confused:

:D :) ;) :good:
[Galaxy S II Android Development] Saber:
I probably can't do much about that. Is it caused by the kernel?

regards, gsstudios
[Galaxy S II Android Development] j1gga84:
I think the unchangeable build.prop it is related to SuperSU

I had problems with 2.50 on my tablet, with 2.52 it works again :good:

regards
[Galaxy S II Android Development] souler456:
Yes. I tried switching to Apolo, and now I can modify heapsize through setprop and add new lines. On Dori latest, I can't.

Tried SuperSU 2.46, and b2.49, no luck. I also don't think SuperSU is the issue here, since I'm on b2.49 now, but changed the Kernel to Apolo, and now editing it is fine.

:D :) ;) :good:
[Galaxy S II Android Development] Saber:
It could be because of the cortexbrain script. Try disabling it temporarily and edit it. BTW, DorimanX 10.45 v034 is out ;)

Changelog
[Galaxy S II Android Development] souler456:
Right ahead of you. I already disabled cortexbrain process, disabled cron, and disabled ALL tweaks coming from Stweaks. I only modified CPU governor & tunables, I/O, and GPU tweaks. I activated BLNWW, using S2W, disabled root installation at root, and disabled logcat.

Did you tried modifying build.prop's heapsize on your own, sir? Or even at least, add an extra line.

:D :) ;) :good:
[Galaxy S II Android Development] psydex:
Why did you remove Lionheart? I'm using v33 with lionheart [MENTION=4691858]1.3[/MENTION]ghz and have no issues
[Galaxy S II Android Development] Saber:
I found that after tuning certain variables in the kernel, especially variables that are CPU related, the kernel will sometimes give SODs. I personally find it mostly stable for normal use, but under constant stress, it becomes noticeable that that kernel becomes less stable.
[Galaxy S II Android Development] Saber:
DorimanX 10.45 v035 is up. I have updated UBER toolchain to the latest and done some additional fixes to the kernel.

regards, gsstudios
[Galaxy S II Android Development] Saber:
Next build will have some changes done to io schedulers, mostly just to improve stability and efficiency. I have reverted I/O scheduler updates so it doesn't put too much stress on our devices storage chip and tuned the fifo batch variable for SIO and Deadline. This should increase throughput at the cost of a bit more latency, but the good thing is that the storage chip doesn't have to work too hard after these changes.

Most importantly, this change will also see improvements to the external sd card speeds as the io scheduler (for external sd card) is set to deadline by default, so tuning deadline means better performance ;)

Build will be uploaded when more testing has been completed.

Regards, gsstudios

Update: DorimanX 10.45 v036 is up! Happy Flashing! :)
[Galaxy S II Android Development] Saber:
Good news touch screen sensitivity tuners (thanks [MENTION=4851689]Sziklián[/MENTION] for speaking up for this issue). I have found the related commits to MOVHYSTI, or more commonly known as the touchmove sensitivity value or vitalij value of the touch screen.

Original post

Original post 2

Related commit 1

Related commit 2

I also discovered that the settings in stweaks was removed because there was no specific file that could tune the MOVHYSTI value anymore, meaning that only developers would be able to tune the values.

Let me know if you want this feature back on DorimanX kernel, and if there is enough people, I will consider putting this variable back again ;) I will make special builds with movhysti value set to 0, gamers and people who constantly need to scroll will benefit from this.

One last thing, for old users of siyah kernel or dorimanx, did you guys like it when the MOVHYSTI value was set to 5 or 7, as I might consider to tweak default values in my kernel.

regards, gsstudios

Update: You know what, screw the whole response system. I'm uploading it anyway ;)

Special DorimanX build with tweaked MOVHYSTI/TOUCHMOVE/VITALIJ VALUE

https://www.androidfilehost.com/?w=files&flid=42468

I have confirmed that the tweak is working as I have provided a screenshot below

Update: I have established a new thread regarding the special kernel.
[Galaxy S II Android Development] Sziklián:
Thank you! I couldn't test yet because using 4.2 now. So could you add this to JB versions too?
[Galaxy S II Android Development] Saber:
Yes I will when I have time. It seems that some people can't tell the difference when touchmove is tune or not, for me it seems pretty similar too.
[Galaxy S II Android Development] Saber:
DorimanX 10.45 v037 is out. This build is built with the latest UBER toolchain (20151031 build) for the latest optimizations and fixes.

regards, gsstudios
[Galaxy S II Android Development] psbt:
I've been using v36 with SlimSaber for the last few days and it's pretty great, except for one little problem, every time I install an app from Play Store which will auto install inself on my sd card, I get the "Couldn't install on USB Storage or SD card" error. Those which install on internal sd card is fine.
[Galaxy S II Android Development] Saber:
Probably something wrong with app2sd, which I've never used before. IMO, installing apps onto external sd is never a good idea, increasing data partition on internal storage is a much better option.
[Galaxy S II Android Development] souler456:
I also have this issue, but I suspect the ROM rather than kernel, since as of now, I use Apolo on it, and I encounter such problems same as yours. I noticed this behavior on APKs which has "installLocation=2" (prefer external) on installation and has 40mb or more size... Even though I still have 1GB free space, the app still won't install...

:D :) ;) :good:
[Galaxy S II Android Development] psbt:
Yeah, I use my external sd mostly for music and books, still got a lot of space on internal storage. But every once in a while, an app will prefer external to internal, and that's when I've encountered this problem.

Strange, I switched to Apolo and install those apps with such problems just fine.
[Galaxy S II Android Development] souler456:
Well, for me it isn't. Although I flashed Dori first, then Kernel-wiped, and flashed Apolo. Maybe there are "remains" of the bugs, I guess?

Can't full wipe and flash SlimROM and Apolo directly to test, since I need my phone to keep running for the whole week.

:D :) ;) :good:
[Galaxy S II Android Development] psbt:
Well, I just tested it and it seems fine enough. My apps still install just fine. Let's see if flashing Dori now will cause problem or not.

On a side note, I can't seem to get BLN to work, and tried both Apolo and Dori. What is your settings? Is there any other backlight options that I have to disable?
[Galaxy S II Android Development] souler456:
BLN work both on Apolo and Dori. You just have to "re-toggle" them in ApoloConfigurator/STweaks on every boot.

Yes, it's painstakingly irritating, but it's quite worth it on the long run... :good:

:D :) ;) :good:
[Galaxy S II Android Development] psbt:
Apolo or Dori, I just can't get BLN to work :(.
[Galaxy S II Android Development] Wolfey7:
Maybe it's a confict between STweaks and Settings/Advanced Settings/Device/Screen/Enable keys backlight?
[Galaxy S II Android Development] psbt:
And it seems I can't find the combination that will make it work :rolleyes:.
[Galaxy S II Android Development] Saber:
Next build will be built by UBER toolchain and Linaro toolchain. I just wanted to make more variations for people who perfer a toolchain over the other. Please note that it will be just for the next build, future releases will still be only built by UBER, but I might make Linaro builds from time to time.

regards, gsstudios.
[Galaxy S II Android Development] Skyline:
What about LP builds?? Also Same for LP??
[Galaxy S II Android Development] Saber:
I will do the same for LP builds.
[Galaxy S II Android Development] _Atom_:
So which tool chain Is the best for a good battery life ?
[Galaxy S II Android Development] :
I've found the linaro builds to be better for battery, but uber seems to be smoother
[Galaxy S II Android Development] Saber:
They are pretty similar in terms of battery life, but I prefer UBER since it is smoother and more up to date.

Update: Linaro builds are up. I have organised folders for each kernel branch, UBER and Linaro builds are now kept separate from each other.
[Galaxy S II Android Development] Saber:
Ok, done a bit of research. Will add colors feature back sometime tomorrow (or weekend). It will be an test release just in case something goes wrong (issues such as colors not changing, weird colours etc.) If all works fine, will promote build to a beta.
[Galaxy S II Android Development] nhmanas:
What about fusebug fix. Is it included? And what is the selinux status of this kernel (disabled is better for me)?

Waiting for the next release
[Galaxy S II Android Development] Noctis Lucis Caelum:
Fusebug, yes. First post confirms it

Selinux is disabled like in the official.

[MENTION=5811506]gsstudios[/MENTION], any chance of a non trim version with the TCP Algorithms.
[Galaxy S II Android Development] Saber:
I'll see if I have space left on my build environment, that way I can try to make a build with no trim just for people who can't use trim on their phone.

You guys want Westwood as default TCP algorithm? Tested it for a while now and seems very promising.
[Galaxy S II Android Development] Nick_Knight:
[MENTION=5811506]gsstudios[/MENTION] I flashed today your v007 build on my girlfriend's phone. She is running on SlimSaber and have a 128 gb Micro-SD inside ntfs formated and was fine with the last 1044v008. Now after starting it no longer exists and in the recovery they can no longer even mount. Are you an idea?
[Galaxy S II Android Development] Saber:
That's weird, I never remember changing anything with the sd card mounting. Is the issue still there when you flash back to cybernetus' build?
[Galaxy S II Android Development] nhmanas:
And I have to ask this. If you flash trimmed kernel (just flash) it runs like a any other kernel. But things could be dirty if you run fstrim script or make factory reset... So in this theory I think everyone can use Trimmed kernel but if they have infected emmc they can't use fstrim or factory reset. Correct me if I'm wrong
[Galaxy S II Android Development] Nick_Knight:
Just flash the kernel of cybernetus has not solved the problem. I flash backup and everything was okay again.
[Galaxy S II Android Development] DaveKing:
Did you try to install Paragon NTFS & HFS+. Normally it solves the system load to that partition. I know DorimanX kernel support ntfs and other type of format.

By the way, I have problems with wifi while testing kk with this kernel. Does Modem xxms4 work well with this kernel? Thanks gsstudios.
[Galaxy S II Android Development] :
From what I have read about trim and the superbrick bug, even "insane" chips should be safe(and have been since Samsung patched their later kernels ie after 4.0.4). As long as those patches(which I think would have been done ever since the first original dorimanx kernels) and these(which I'm sure [MENTION=5811506]gsstudios[/MENTION] would have done) have been implemented into this kernel. [MENTION=4141005]Lanchon[/MENTION] has more info over on his trim kernel thread
[Galaxy S II Android Development] Saber:
TRIM disabled kernel uploaded. It includes all TCP algorithm changes and etc.
[Galaxy S II Android Development] Saber:
I can't get this feature working since it relies on a specific file in mdnie folder. Reverting dorimanx's commit is easy, fixing the issue, a bit complicated for me. Also, I need more reports on TCP algorithms. What's your favorite TCP algorithm? Should I make Westwood to default?
[Galaxy S II Android Development] kostelo:
Westwood makes indeed my connection feel faster even in high loads. Sorry for not providing any screenshots. I think it should be default.

Sent from my GT-I9100
[Galaxy S II Android Development] DaveKing:
Sorry gsstudios. But do you have any problem with me? You didn't answer to any question made by me for days. Now I have a WiFi problem and no reply to that neither... I don't have any problem with anyone in this forum, but in any forum the feedback is a good manner between people. Thanks again by your work gsstudios, cause it have been greatly to our phone. Sorry but I installed KK just to try your work...and have this prob...and no phone working well. Understand please.
[Galaxy S II Android Development] Saber:
Sorry, just busy recovering after the exams :o With the problem with the wifi, did this happen with the dorimanx builds by cybernetus? I know this sounds a little repetitive, but that's because I did nothing to modify wifi or storage settings. Maybe next time, could have a little patience :)
[Galaxy S II Android Development] Saber:
Also, TCP algorithms fixed now. Westwood is now the default TCP algorithm for now on. Enjoy :good:
[Galaxy S II Android Development] DaveKing:
OK. Sorry,didn't realize. I installed the v007 version in first post. It's just the WiFi prob. I will try other modems and reply here any advancements. Sorry for any inconvenient. Good luck in exams! ;) thanks
[Galaxy S II Android Development] the.gangster:
Just found this thread .

Good to see that work on DorimanX Kernel continues again.

Although I am still lucky with the latest b3-build of stelistcristi's personal build.

I haven't figured out all differences to your new one, yet, except for the obvious ones, but I'll keep an eye on this thread and will very likely give it a try, soon.

Thanks for spending time on developing and good luck.
[Galaxy S II Android Development] kostelo:
@gsstudios Is it possible to have ext4 support in dorimanx for internal/sdcard? Is it hard to implement this? :fingers-crossed::confused:
[Galaxy S II Android Development] morTimar:
Cydia Substrate + RootCloakPlus - is this working for someone?

Hi all,

I am using Apolo 7.2 beta kernel for SlimKat latest stable release for my i9100.

After I installed this kernel after a HawkerCore kernel wipe I was not able to hide root for Maas360 using RootCloakPlus (extension to Cydia Substrate).

Even reinstall all of the 3 apps in recommended order did not help.

I went back to Apolo kernel and got it working.

Any ideas what to do?

Or is this kernel not supporting Cydia Substrate + RootCloakPlus?

Thank you very much.

bye morT
[Galaxy S II Android Development] Ham1do:
Hi .. I'm on slimkat & the only reason I dropped The powerfull dorimanx kernel is this essential app for me

https://play.google.com/store/apps/...store&pcampaignid=APPU_1_O8pIVq67OMjkUpK8utAN

It contains over 1 GB of database & works well on stock/apolo/Gustavo kernels

On dorimanx : Error

Android.database.sqlite.SQliteDiskIOException

Disk I/O Error ( code 3594 )

Is this related for ext4 kernel support or what ?
[Galaxy S II Android Development] Saber:
I think this could be because of the hacked sqlite on dorimanx Kernel. Not too sure if it would be related on the file system.

Regards, gsstudios
[Galaxy S II Android Development] Saber:
What recommended apps did it recommend? I have a feeling this is because of some problem with busybox, or at least something related to it.

Regards, gsstudios
[Galaxy S II Android Development] Saber:
DorimanX 10.45 v038 is out! I have merged some updates for net (ipv4) and TCP cubic, to ensure greater network speeds and stability. We are about 1 - 2 releases away until I release Linux 3.15.0 stable kernel, as I need to fix all stuff during the merging stage (depending on how well it goes, I might release early or might not even release it at all).

regards, gsstudios

Update: Linaro builds are out! v038 will be the last build built with UBER toolchain. All future builds will be compiled with Linaro 4.9.
[Galaxy S II Android Development] chhapil:
Any specific steps are you following to merge the upstream changes?
[Galaxy S II Android Development] Saber:
DorimanX 10.45 v039 is out. I have been testing it for a while and it is very stable. This build brings missing changes that was meant to be in v038, and additional fixes to kernel files.

regards, gsstudios