yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] MikiGry:
Ehh. This is the end of KitKat and Dori running on my device. After nearly 3 monts of usage SII refuses to work GPU >330 Mhz

When i set this and run benchark , i will get sod.

Now it is even worst. I try some profiles for STweaks profile thread , and seconds after fresoring them i was getting SOD + data corrupion (needed to reflash ROM + GAPPS + Dori to boot into system again).

I wonder , why my SII now refuses to

work with GPU 400Mhz (400Mhz GPU --> 1350mV).
[Galaxy S II Android Development] Saber:
Your device must be getting old. :( That's what happens to a lot of S2s. Sometimes it can reach a certain overclock or undervolt, but over time it degrades.

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

Thats sad ;(

At least i can still use extereme UV on CPU (825mV - 100-300Mhz)

Edit. My CPU got olso "used"

No more UV possible. -25mV is max ! -50 and freeze. Mebay after some time my device will "resurrect" :P
[Galaxy S II Android Development] ultravy:
The worst : get an sod over the night and no alarm to wake you up to go at work :D! i will give a try with no UV or 0,25 mv decrease! i allways used the voltages posted few pages back with no problems (sod&data coruption). Forgot to mention that now i used [MENTION=5651185]GreekDragon[/MENTION] build with same uv , and kernel has now 1,4 ghz and editable voltage table! Dont uv 1,4 ghz below 1,3 v or 1,275 - you will get a freeze even after reboot , no matter how fast your are , i was able to get in performance menu and then BAM freeeeze!!! the only way was to flash from recovery an older verion of slimsaber kernel , limited freq to 800 ghz and flash the orginal kernel back or entire rom(dirty flash)!
[Galaxy S II Android Development] MikiGry:
[MENTION=5811506]gsstudios[/MENTION]

There seems to be something wrong with dolloweing grovs.

- Darkness

- Nightmare

- NeoX

- Intelidemand

With most of them i am getting sods , and i am not anable to reboot phone again (need to wipe STweaks profile via recovery)
[Galaxy S II Android Development] Saber:
Thanks, will investigate when I have time. Won't be able to make a new build for KK because I already removed it from my machine.

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

I know. But i think Lolipop verison is olso affected.
[Galaxy S II Android Development] Saber:
Well I tested those governors on Lollipop and they work fine. No SODs or any form of crashing.

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

I think im going to move to Lolipop until your Dori v12(...) builds will arrive. If you will be on kitkat , plese test them (i am gestting sods)
[Galaxy S II Android Development] Marios145:
I've been using 10.50v004 for 10 days it's super-stable, no crashes or freezes so far no performance issues either, thanks gsstudios
[Galaxy S II Android Development] morTimar:
STweak changes do not survive reboot after update to 10.50v004

Hi all,

I updated to 10.50v004 but all my STweaks changes do not survive a reboot.

Any ideas on that?

Thank you very much.

updated from 10.45v004 as follows:

- reseted STweaks profiles

- did a Kernel Wipe with Hawker Kernel Wipe 1.04

- flashed kernel
[Galaxy S II Android Development] Saber:
[MENTION=2397363]morTimar[/MENTION]

^^

Well that's the reason, no need for hawker kernel wipe. Just dirty flash over existing build and your settings would have been still there.

gsstudios
[Galaxy S II Android Development] morTimar:
Ok, good to know.

I understood that there are new features and that was the reason why I assumed it would be useful to get rid of all old stuff.

And because of that I was not expecting to keep my settings. Those are super simple that I could do it again quickly.

So you say no need but that does not mean it was completely wrong, correct?

What I do not understand, why the changes I do now are gone after a reboot.

It is like you would do a reset but also not for all of the settings I just saw.

'Memory' settings for 'OOM Level Screen On/Off' stay the same and as far I can tell 'USB mass storage mode' as well.

Any other settings do not survive.

Why is that?

Thank you very much.

bye morT
[Galaxy S II Android Development] Saber:
I assume you reset stweaks profiles in StanTRC recovery, am I correct?

There could be some sort of corruption happening on your end. The obvious choice would be to do a clean flash to remove the problem completely. What 'simple' changes have you been doing on the latest build? Does it occur on a particular change or happens everytime?

gsstudios
[Galaxy S II Android Development] morTimar:
Correct, I reset stweaks profiles in recovery, did the HawkerKernelWipe and flashed the new kernel

Since then I try to setup the stweaks profile the way I like it. I do not change something at the kernel build (no programming) just in case that was your question.

Changes I do:

- govenors: both to 'pegasus'

- 'Memory': OOM Level Screen On=aggressive; ... Off=medium; Low Mem Reserve=boosted; ZRAM=150+20%

- GPU: 5th stage=400MHz

- Screen: MIN_BL=40; MIN_GAMMA=0; MAX_GAMMA=22; Gamma Shift=-5

- BLN: LED voltage lvl=2750 mV

- OTHER: USB mass storage mode= force mass ...; Auto mount=disabled; battery usb charge=600mA

- TWEAKS: Android Logger control=disabled

Those are my changes but except the ones I posted earlier all others are gone.

Even with 'Push CPU tuning to GOV Core'

I was hoping I do not have to do a clean install.

WORKAROUND/SOLUTION which worked for me:

- reset profile this time in stweaks app

- in recovery installed old kernel 10.45(004)

- rebooted and did my setup in stweaks app and rebooted to see if the settings survive > positive

- in recovery flashed the 10.50(004) kernel

- settings still there and also changes there survived a reboot

Thank you very much.

bye morT
[Galaxy S II Android Development] BLscHaWK:
[MENTION=5811506]gsstudios[/MENTION] I flashed this kernel, everythings fine, but I can't use my bluetooth gamepad. Matching my phone but buttons doesn't work. What should I do?
[Galaxy S II Android Development] Saber:
Hey guys,

a new build has been uploaded to afh and github. This build has many changes synced from LP kernel (even though it is EOL).

This should definitely be the final build since I have retired from development from all dorimanx branches and kernel development in general (I am busy with life).

The reason for this build to be released was because the past few changes really didn't meet my expectations, so I decided to make a build full of changes :)

gsstudios

Edit: Spelling mistakes with zips have been fixed. All zips have been reuploaded. :)
[Galaxy S II Android Development] j1gga84:
[MENTION=5811506]gsstudios[/MENTION]

Many thanks for the update.

Sorry to hear that you stopped kernel development in general.

Do you think this is a final decision or will you probably start developing one day again?

Weather for Galaxy S2 or another device?

Everybody was hoping that Dormanx will come to MM because no other kernel beside stock is left but I can also understand your decision.

For me it is not that important because the S2 is only my backup device and I switched to S5 one year ago ;)

Wish you all the best for the future.

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy S II Android Development] Saber:
Build v006 is out!

I have tested the changes for about 2 days now and it has been very stable.

Many changes have been synced from LP kernel. A lot of missing changes were synced because I forgot to do them in the last build.

Happy flashing, gsstudios ;)
[Galaxy S II Android Development] davidcie:
You are amazing, thank you for still supporting KitKat! For many of us (or our loved ones!) LP / MM ROMs are simply not stable or performant enough for daily drivers; your kernel is the only thing that keeps these phones away from the dreaded Drawer of Death :)
[Galaxy S II Android Development] xn0live:
hi all

is here onyone whi have a kitkat rom with this kernel?

which rom are u have and how ist stability and batter ylife better then jelly bean?
[Galaxy S II Android Development] Saber:
DorimanX 10.50 v007 has been released!

While I was daily driving my kernel on Kitkat, I noticed that I have forgot a really important change in the way the kernel trims the data partition. It turns out that the issue has existed on all existing builds and would affect the performance of the device. Basically the kernel would trim whenever there are free data blocks in the partition (online trimming), but android versions 4.3+ have automatic trimming while phone is charging so it isn't required.

While I had the chance to fix this problem, I had the freedom of syncing most of the changes from my MM kernel. This kernel will have all of the changes from MM kernel, except those that are MM specific (e.g. Selinux, other fixes). See the changelogs for some of the changes I've done. There were more things I changed that you will have to look for yourself on my github.

This should be the last build as I don't think there are any major bugs that are left on this kernel.

Happy Flashing! - gsstudios
[Galaxy S II Android Development] profyler:
Sorry for stupid question, but Im using Lanchon cyanogenmod kk ROM. Can I flash the non trimm kernel on it?
[Galaxy S II Android Development] Saber:
Yes you can, but you should be using TRIM kernel even if you are brickbug affected.

gsstudios
[Galaxy S II Android Development] profyler:
Ah Ok, i thought trim kernel needed some other stuff to work. Do I loose the cyanogenmod splash boot animation? I like that animation :p
[Galaxy S II Android Development] Saber:
No, you keep your ROM's boot animation. Dori kernel has an additional kernel splash screen before you see ROM boot animation.

As for TRIM, you can use an app like Trimmer on the Google play store to use the trim feature.

gsstudios
[Galaxy S II Android Development] profyler:
Is there a way to remove Dori's splash screen?
[Galaxy S II Android Development] ssanjy:
Go to s tweaks and in the last tab or so there's option to disable the dorimanx welcome boot screen.. Need to untick the option
[Galaxy S II Android Development] tiuro:
[MENTION=5811506]Saber[/MENTION] Thank you for keeping DorimanX kernel and the the old S2 alive! ;)

I got 2 pieces of S2 in family (one is a gaming backup phone for kids, and the other ones is mother in law ;) )

With one S2 all went fine, but with another I got stuck in Dorimanx logo. I tried many things but with no success. Of course I tried clean install after format data and wipes (TWRP) and/or after factory reset in CWM. Even with Hawker Paul Kernel Wipe Script is the same.

Both phones are on SlimSaber 4.4.4 from [MENTION=5651185]GreekDragon[/MENTION] 20160519 (the last one)

I'm using SuperSu 2.79 SR1, Kernel 10.50v007 Linaro or Uber, last opengapps...

Do you have any idea how can I solve this problem?
[Galaxy S II Android Development] Ham1do:
I suggest you to flash the rom , flash gapps, flash kernel and reboot without wiping cache .

The kernel contains its own SuperSu so no need to flash it again
[Galaxy S II Android Development] Saber:
Hi,

I suggest doing the flashing in these steps if you didn't do so:

- Format system

- Factory reset

- Flash Slimsaber

- Flash Gapps

- Flash DorimanX kernel

- Reboot

Ensure that your partition layouts have normal sized preload. Make sure you are using 1GBSystem4GBData layout or 1GBSystem3GBData layout or Stock.

Saber
[Galaxy S II Android Development] tiuro:
Thank you. It doesn't work :/

Working S2 has a 1GB System and 4GB Data. Not working S2 had 0,5GB System and 2GB so I assume it was stock. But I changed it. I used Repit script from Lanchon configured this way lanchon-repit-20160923-system=1G-data=4G-sdcard=max-preload=min+wipe-i9100.

Still the same. Stucked at DorimanX logo. Now I have a TWRP 3.0.2-1 IsoRec

I'm thinking that DorimanX kernel is the most developed for KK. And the SlimSaber is the best ROM for S2. Maybe it's time to give a second chance for LP or MM Slim for this device. (last time I was trying about 2 yeras ago). .

For now I'm on Lanchon last Trimm kernel for CM11, is comparable with DorminX in terms of performance?
[Galaxy S II Android Development] Saber:
Have you tried wiping the preload and cache? How about flashing my kernel in ODIN? Try using an older build of Slimsaber or Dori kernel. I'm running out of ideas :)

I don't know how comparable lanchon kernel is to Dori kernel, but it seems to be that this kernel along with Slimsaber gives the best combination.

Saber ;)
[Galaxy S II Android Development] tiuro:
Maybe it's because modded preload size, but probably no. Yesterday it was a stock size :/ Now my preload it's 7MB and additional formatting didn't help.

All of partitions on both phones are ext4

Next things before I resign ;) will be an older SlimSaber ROM and/or older Kernels, maybe 10.50 v005 and I will try kernel in Odin, but I need to convert to tar first.

Is there any way to create log on booting?

Thank you!
[Galaxy S II Android Development] TriboDoP:
I suppose you do know the kernel guide by Saber how to convert zip to tar.

In this are also some premade tar kernels ready for download.
[Galaxy S II Android Development] tiuro:
Yes, but I had some problems and described them in a thread.

Premade kernels are pretty outdated
[Galaxy S II Android Development] the.gangster:
[MENTION=5283601]tiuro[/MENTION]

Are you sure, that all your partitions on both phones are ext4?

As far as I remember (and it's still listed in #4), the DorimanX-builds don't even support ext4 on internal/external SDcards.
[Galaxy S II Android Development] Saber:
See:

https://github.com/gsstudios/Dorimanx-SG2-I9100-Kernel/issues/2

Realex-fire and I have tested ext4 on our devices a while ago and ext4 is mounting properly, but I don't think I announced the findings :)

Please note that we tested on the MM branch kernel (so if broken in older branches, fixes may be able to be ported).

Saber :)
[Galaxy S II Android Development] tiuro:
[MENTION=6560258]the.gangster[/MENTION] you were right! I ignored checking internal/external and they are vfat! at NOT working S2.

I'm at work I got only NOT working phone with me. So I'm gonna check it in the other in the evening I doubt if this changes anything...
[Galaxy S II Android Development] the.gangster:
[MENTION=5283601]tiuro[/MENTION]

As vFat is the default I wouldn't expect this to be the reason, too.

I already expected that, as otherwise your repit-command line should have thrown an error. You could still use it once more, with a +wipe parameter for each partition. This would ensure you start with clean partitions and it runs much faster anyway.
[Galaxy S II Android Development] tiuro:
[MENTION=6560258]the.gangster[/MENTION]

I used lanchon-repit-20160923-system=1G+wipe-data=4G+wipe-sdcard=max+wipe-preload=min+wipe-i9100

So wipes were made for for system, data, sd card (internal), preload

Preload has 7MB

Still no luck
[Galaxy S II Android Development] TriboDoP:
Hi [MENTION=5283601]tiuro[/MENTION]

After all your efforts - could this not be a sign to update to cm14/aicp N/RR N ..... ;););)
[Galaxy S II Android Development] the.gangster:
[MENTION=5283601]tiuro[/MENTION]

Does it boot with the ROM's default kernel at least or didn't you try that at all?
[Galaxy S II Android Development] tiuro:
[MENTION=6560258]the.gangster[/MENTION]

Yes it does. It doesn't boot only with DorimanX (checked v005, v006, v007)

After attempts I'm restoring SlimSaber 05192016 (GreekDragon) with Lanchon CM11 trim kernel

Probably I will stay with it or will try wit LP or MM or Nougat ;) But first I will try older SlimSaber builds and kernel flashed from Odin (but I need tar)

Edit: last fusionjack bulid and kernel via Odin the same... lol
[Galaxy S II Android Development] Saber:
:highfive:New kernel build is up!:highfive:

This build contains security fixes including the DirtyCOW exploit patch.

Here are the changes:

DorimanX 10.50 v008 (STABLE)
- Security updates from LineageOS (formerly Cyanogenmod) kernel source
- Change default I/O scheduler to ZEN - CFQ better for hard disks, ZEN is good for flash storage
- Remove UKSM - The kernel needs to be more in-line with the linux kernel
- Remove toggle for Software CRCs and disable by default - Tested safe by other devs so why not?
- Remove power saving workqueues control - Had little to no effect
- Remove Powersave and Performance governors - I don't keep garbage :)

Some important info:

- I won't be testing these changes at all as I believe that nothing should break with these security patches and because I don't use this device as a daily driver anymore

- I will only build Linaro builds as I don't have time to build UBER builds and because I think I should build the kernel with the toolchain that I think is best

Happy flashing :)

Saber
[Galaxy S II Android Development] Lownita:
Hi everyone, today I took my time to repit my good old S2 (lanchon-repit-20160923-system=1G+wipe-data=4G+wipe-sdcard=max+wipe-preload=min+wipe-i9100.zip) and install TWRP, Slimsaber ROM (latest from fusionjack) and today's release of Dorimanx kernel. First boot went smoothly, I just updated SuperSU app, clicked yes to update SU binaries and rebooted the phone. Suddenly, the screen was stuck on the Dorimanx splash screen and didn't boot further. I longpressed the power button to reboot, this time the phone booted up again. After a while though, the browser popped up with a logfile and told me, that errors in partitions would have been detected. I am pretty clueless if I did something wrong or what I should do now. Any advise would be highly appreciated :)
[Galaxy S II Android Development] Saber:
You may have encountered a corruption in one of your partitions. In stweaks, you need to enable fix partitions then reboot.

I don't know why DorimanX encounters weird corruption issues (/dev/data partition at least for me) but usually the only thing that is affected is the boot process (sometimes multiple reboots, freezing on dori kernel logo).

Saber ;)
[Galaxy S II Android Development] ultravy:
It happened to me several times, and SOD's if i let the phone charge over night with no UV/OV. Open Stweaks, look for fix data partition!
[Galaxy S II Android Development] Saber:
:highfive:New kernel build is up!:highfive:

Last maintenance update from me :) Just more security updates and minor changes throughout the kernel.

Here are the changes:

DorimanX 10.50 v009 (STABLE)
- Additional security updates from LineageOS kernel source
- Force Deadline to be used as the default scheduler while not in OS
- Updated stweaks descriptions from previous commits
- Re-enabled Software CRCs. DorimanX kernel does experience corruption issues so it is better to keep this enabled.

Some important info:

- I won't be testing these changes at all as I believe that nothing should break with these security patches and because I don't use this device as a daily driver anymore

- I will only build Linaro builds as I don't have time to build UBER builds and because I think I should build the kernel with the toolchain that I think is best

Happy flashing :)

Saber
[Galaxy S II Android Development] Ham1do:
:eek::eek::eek:

I have tested Dorimanx 10.50 v009 for a while on SlimSaber by GreekDragon ( 20160519 build ) it's really stable , except that CF Lumen by Chainfire does not want to work in root mod while it work perfectly on stock kernel :confused:
[Galaxy S II Android Development] Saber:
Hi,

Can you please describe the problem? Is CF Lumen unable to change the display colour? Does the problem still occur when you switch between CF Lumen driver modes (compatibility, performance, hybrid)?
[Galaxy S II Android Development] Ham1do:
I can change the display colour only on non-root mod ( less quality )
[Galaxy S II Android Development] Saber:
Can you please provide a logcat when you try to force CF Lumen to enable when in root mode. I will see if I can find the cause of this issue.

My guess is that there is something conflicting with the CF Lumen service/driver which could be kernel related.

Thanks.
[Galaxy S II Android Development] Ham1do:
I'm currently on stock kernel i will try to provide a logcat when I switch to Dorimanx kernel again .

Thank you
[Galaxy S II Android Development] Ham1do:
Is it not related to Selinux disabled in this kernel while it is in permissive on stock !

I hope this log files can help . Thanks [MENTION=5811506]Saber[/MENTION]
[Galaxy S II Android Development] Saber:
Unfortunately, I was unable to see the main cause of this issue. Don't think this is selinux related as having it disabled shouldn't cause issues with apps, only having it enabled will cause issues.

Have a quick look at the logcat, there are a lot of exceptions given from the app but they are unclear (resource missing??? Maybe try removing xposed framework). dmesg doesn't show any issues so kernel is not denying any permissions.
[Galaxy S II Android Development] marcimix:
I can not turn on the WiFi after flash your kernel

lolcat:
[Galaxy S II Android Development] DaveKing:
Well, after trying many other modems with no changes in wifi behaving, I tried the chmod 0777 to data/misc/wifi/wpa_supplicant (it had permission just for the system) and the result: nothing. -_- I think it must be an incompatibility between my i9100 fabrication version wifi modem and the kernel drivers. Maybe it needs a especific wifi drivers to work well, and with the last versions of dorimanX doesn't work. Don't know for real. But I had this problem for a long time in JB and had to flash a fix in recovery to put the wifi working again, I don't recall what kernel was, if was dorimanX or other... But I'll stay with LP for now...it has many incompabilities, but just with applications. Well, it's a matter of time the apps work better with ART.

gsstudios, in my humility opinion, you should focus in LP and not in KK for many reasons. The ROMS in LP are in Stable status for now, and need a good kernel like dorimanX for better performance and with unlocked features. And you would have many supporters in this. Of course I understand you have the exams and you have to make them priority to your life. But in this project, try to see the pool you made, and if you need any help you will get it, cause the future is LP not KK. ;) For my phone I tried KK and got wifi probs, in LP this maybe wouldn't be a prob.

Cheers mate! ;) And good luck again!

ps: my i9100 in fact has 4 years, it was one of the first models of the i9100 international. I'm so proud of my baby (lol), it looks new! ;) sooo, many changes could had been made until it was descontinued in "parts".
[Galaxy S II Android Development] Saber:
You'll notice the difference once you play around with the tcp algorithms and io schedulers :) My builds have most of stelistcristi's changes (excluding wifi driver updates), except my builds have more features. I've been making more changes to stweaks profiles to make them faster, before they were really unopimized.
[Galaxy S II Android Development] Noctis Lucis Caelum:
[MENTION=2432329]DaveKing[/MENTION]

Your Wi-Fi issues reminded me of the same problem I had when using dorimanx by Cybernetus, basically the gapps were breaking my Wi-Fi, I fixed this by using slim mini gapps.
[Galaxy S II Android Development] DaveKing:
Thanks [MENTION=6273571]NoctisBlade[/MENTION]. Never heard of that, but gapps are the problems to many things, including in LP. I installed LP for now and the differences are too many, and the ROM itself it's so sweet, the UI, the colors. When we come back to KK it's like coming back to Medieval Age. :D But will try that. It seems a good work in there with the Schedulers IO and overall ROM optimizations by gsstudios, and would be a shame not to try at the least.

Thanks for the help Cybernetus.
[Galaxy S II Android Development] Saber:
Nice, I'll add this to the troubleshooting guide.

Right now, I'm trying to add back some good governors like lulzactive and revert zzmanx to zzmoove, but the compiler has been spitting out errors which is a pain in the neck. I should hopefully fix this by next week.