yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Saber:
Doesn't happen here. Maybe wiping will be your solution.

Also, did you undervolt? Remove any adjustments and try using the default values. Reset stweaks profiles.

gsstudios
[Galaxy S II Android Development] DualJoe:
Will try that.

Is there no fix for mdnie sharpening in stweaks? I think i can see it does change colors at startup (during stweaks profile appliance). I can set it manually in adb shell with 'echo 8 > blahblah/scenario' but persistent change by stweaks would be much better.
[Galaxy S II Android Development] Saber:
Yep, so you also want to change screen mode on stweaks. Will see if I can add it for the next build.

gsstudios.
[Galaxy S II Android Development] Saber:
DorimanX 11.0 b025 has been released.

There has been lots of updates to zram in this build. [MENTION=4354573]chhapil[/MENTION] has been working hard to get lz4 working on zram, whereas I've been updating zram and other parts of the kernel to make zram even faster and more stable. I can confirm that with this build, lz4 will be used as the default algorithm which can be seen in /sys/block/zram0/comp_algorithm.

I have also changed the default scheduler to CFQ for all profiles. The move from SIO to CFQ was because Lollipop needs more I/O performance to multitask, so simpler schedulers don't cut for our old device. Our device is using a slow storage chip compared to modern/newer phones which can run simpler scheduler effortlessly. Before people ask for recommendations, currently, only CFQ, BFQ or ZEN should be used with our kernel. Other schedulers will work fine but they are a bit too slow for lollipop. From this change, people will experience less lags and stability will be improved.

This will also be the last time we will see NON-TRIM and UBER 4.9 builds. Everyone should be on TRIM builds regardless if you're affected by brickbug or not, and UBER 4.9 is just an extra build for me to do. There are reasons why we should still keep them, but I feel that they are just not important and add more time for me to make builds.

You may also think that Marshmallow kernels are just around the corner, well that's depending on the development on CM13. I will start work soon after betas have been released, but I will be working to bring support while we are still waiting.

One last thing, screen mdnie support for DorimanX will be postponed to later builds because I want to release this build with zram updates.

Enjoy the update! - gsstudios
[Galaxy S II Android Development] makix13:
gsstudios you are a Master, great development and effort, and great idea left non-trim kernels under the sea[emoji6] [emoji106] .

Only one thing, it's support ext4, I know you have many other important things, but I think this will be great for this amazing kernel.

All my respect to you[emoji122] [emoji122] [emoji122]

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Android Development] souler456:
I'm sure you're on a CM12.1-based ROM, right? Can you try booting the ROM "without" Dori Kernel, then test if it'll soft reboot again? :confused:

This is still a mystery to me, since this is the reason why I can't use a CM12.1 ROMs here (and ofc, the Dori Kernel). Tried everthing, from the Official one, to RR. Still the same. Soft reboots. Pisses me off...

:D :) ;) :good:
[Galaxy S II Android Development] DualJoe:
That's probably a different problem. I had it working for months already. It's somehow a dirty update problem. Maybe i should restore the backup on b10 StanTRC instead of b24 recovery. I'm going for TWRP anyway but for now i have to deal with it somehow or start from scratch.
[Galaxy S II Android Development] fabiodelaplazia:
Hello, to spend a trim just take the trim version, and launch the application trimmer?
[Galaxy S II Android Development] Noctis Lucis Caelum:
Yeah just grab the trim kernel and the trimmer app.

Launch the app and choose the partition you want to trim, then press trim.

Should take a couple of seconds depending on the size of different partition.
[Galaxy S II Android Development] fabiodelaplazia:
OK thanks ;)
[Galaxy S II Android Development] LeBourrin:
I've installed beta 25 and I restarted 4 times my phone in order to test my boot problems.

No more STweaks and SU rebuild, and no more semi boot-loop. Don't know what's happened before. I'm happy that the problem is gone (maybe a cache bug?)

One thing: I noted that installing beta25 reseted my wallpaper. Is it a usual behavior?
[Galaxy S II Android Development] Jack122:
sorry that i ask here. i replaced my usb controller. but i broke the volume keys. it is softbricked at the moment. how do i get into recovery now? dorimanx 22 i only get to the dorimanx boot logo and there it is stuck.

tried adb. it only recognizes the device when the screen is off. i attached a pic of adb. adb doesnt do anything after the command.
[Galaxy S II Android Development] Saber:
A USB jig could be what you need. Then you will be able to get into download mode. Flash a the last working kernel on your phone and you should get into your OS.

gsstudios
[Galaxy S II Android Development] Saber:
No, this is the first report of wallpaper being reset by kernel flash.

I think this is more to do with the rom rather than the kernel as this used to happen to be occasionally on slimsaber 4.4.4 (cache clearing, etc). Except that this happens on restarts, and not flashes.

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

Can confirm "wlalpaper reset" on latest SlimSaber + first 10.50 Trim Linaro DorimanX .
[Galaxy S II Android Development] DualJoe:
I have freshly installed MarkoX and kernel b25. Deepsleep is bad here (~10% in some hours). Logcat is flooded with this entries:

02-02 08:17:17.415 I/auditd (5674): Starting up
02-02 08:17:17.418 E/auditd (5674): Failed on audit_set_pid with error: Protocol not supported
02-02 08:17:17.418 I/auditd (5674): Exiting
02-02 08:19:16.371 W/art (4771): Long monitor contention event with owner method=void com.android.server.power.PowerManagerService.releaseWakeLockInternal(android.os.IBinder, int) from PowerManagerService.java:921 waiters=0 for 802ms

The ART errors just came somewhat later but the auditd are spread everywhere. As the kernel has SELinux disabled auditd service (in init.rc) should be better disabled as well.
[Galaxy S II Android Development] atuser:
@gsstudios

It takes too long to display the caller ID :(

Is this a Kernel related issue?:confused:

-------------------

ROM: Euphoria

Kernel: DorimanX (Kernel_Dorimanx-V11.0b025-[16-21]-[01-02]-LP-SGII-GSSTUDIOS-UBER-5.3-TRIM-signed.zip)
[Galaxy S II Android Development] TreckeR:
The caller ID takes longer time here too. With the default kernel I did not have this problem.
[Galaxy S II Android Development] buddy1234567:
Am I correct that this does not work on slimLP?
[Galaxy S II Android Development] Sun90:
Since Slim LP is based on AOSP, It should wrk , But u can take a bkp of the current setup before proceeding
[Galaxy S II Android Development] Troubadour666:
not sure because now we have a new release, and "non-trim" , the 1rst to try on SlimpLp if you want to test.
[Galaxy S II Android Development] Noctis Lucis Caelum:
It won't work at moment on Slim or Omni, only CM12.1 based rom.
[Galaxy S II Android Development] Resync:
Kernel doesn't work with 0703 nightly can't mount internal nor external sd.

Both are ext4

Also can you please make a tar for next build it's quite annoying otherwise with the new cm recovery.
[Galaxy S II Android Development] kostelo:
EXT4 filesystem on internal/external storage was never supported in DorimanX kernels and probably will never be. So this is not a bug you are reporting.

The kernel itself works like a charm in latest nightly for me.
[Galaxy S II Android Development] Cidxx:
First of all, thanks to gsstudios for its work!

I'd like to switch to LP and need to repartition /system as well; does this kernel is suitable to perform that operation, or, as adviced by the same gsstudios in previous guide on repartitioning, is still suffering of formatting problems and hence is preferable gustavo's?

Thanks,

Cid
[Galaxy S II Android Development] Resync:
Yeah but why not ext4 is awesome!

Would be nice to get that support if it is not too much work.
[Galaxy S II Android Development] kostelo:
I so much agree with you but I think it's not that easy to be implemented unfortunately. Who knows, maybe one day.

Sent from my GT-I9100
[Galaxy S II Android Development] Resync:
What Filesystems are supported?
[Galaxy S II Android Development] Heroeagle:
didn,t worked with mokee unofficial ends with a bootloop even it,s cm based

thanks
[Galaxy S II Android Development] Nick_Knight:
Open the mount storage menu, select format sdcard0, everything is available there, the kernel can handle then you formated in the recovery. Especially when you format Micro-SD ntfs with PC the kernel can't handle.
[Galaxy S II Android Development] AF_624:
[MENTION=5811506]gsstudios[/MENTION]

Please rename the kernel to LP kernel instead JB kernel like it sais in 'about phone'

Thanks to your work, i m using your kernel for a while and with intensive usage and it seems very stable...
[Galaxy S II Android Development] ettore88:
Hi guys!!!Please could you tell me anything more about difference between TRIM and NON TRIM?THX in advance!!!
[Galaxy S II Android Development] GreekDragon:
There is a bottom here in xda called Search. Use it. It won't harm you.
[Galaxy S II Android Development] Nick_Knight:
With TRIM when you want can use App Lagfix or terminal/adb command for trim system and data partition. I don't know why people ask for a non TRIM. [MENTION=5811506]gsstudios[/MENTION] I don't know what is wrong in second build, but simcard not detected in first official CM also in Carbon. I am back to build 1 all fine.

Thanks for holding our oldie S2 on special DorimanX. I like your hard work also for KK. Especially thanks [MENTION=6159291]Lysergic Acid[/MENTION]

Regards Nick_Knight
[Galaxy S II Android Development] Noctis Lucis Caelum:
Reading the Trim thread, you would know why some people ask for the non trim version.. with all the different issues affecting the emmc, some folks like being safe.
[Galaxy S II Android Development] kulitom:
Why viper4android don't work on this kernel?
[Galaxy S II Android Development] ssanjy:
I had it working in the initial version of the kernel... Haven't used the new version so can't say about it....But in my view it should work....Reinstall and check...
[Galaxy S II Android Development] Nightshadow931:
Make sure SELinux is permissive, v4a won't work if it is set to enforcing.

Sent from my GT-I9100
[Galaxy S II Android Development] DualJoe:
The root folder (ramdisk parent) should be read-only when system has been booted up. Some apps spam their data there if for some reason they cannot write into their personal data folder. Never seen that before but here they do.

Anyone know a solution for widgets not loading properly with 3rd party launcher? Seems to be a common problem on Android 5 but maybe someone knows better. I already tried to put GO Launcher into /system/app but that doesn't help. Widgets come up black and when pressing on them a popup is asking to grant access to the launcher to place widgets. On next boot up they are gone again.
[Galaxy S II Android Development] Saber:
The caller ID delay happen's to me also. I guess it is something related to the kernel. Using the Linaro build right now and I guess they are more or less the same.

gsstudios
[Galaxy S II Android Development] Saber:
I actually saw the logs being flooded with auditd entries as well. Yes it is related to selinux being disabled, will see if I can disable auditd.

As for deepsleep, I'm getting 3-4%/hr draining which was roughly the same for me on stock CM kernel.

gsstudios

Edit: Auditd service will be disabled in next build.
[Galaxy S II Android Development] DualJoe:
I've temporarily disabled it with init.d. Will let it settle for some time.

The loop is to force r/o rootfs. Apps are writing there and i don't like that.

#!/system/bin/sh

# Debug
# exec &> /data/initd.txt

nice -10 /system/bin/sshd
stop auditd

# (sleep 90;echo 8 > /sys/class/mdnie/mdnie/scenario) &

(
for i in `seq 1 60`; do
if [[ "$(mount |grep -E 'rootfs.*rw,')" ]]; then
echo "remount rootfs ro"
mount -o remount,ro /
echo $?
else
sleep 2
fi
echo loopcount $i
done
) &
[Galaxy S II Android Development] Skyline:
[MENTION=5811506]gsstudios[/MENTION]

As of now there are lots of improvements from last few(not actually few) builds which are pretty stable but I am facing 2 minor issues and I always perform clean flash

1.Launcher force closes

2.When my battery gets down from 1% to 0% phone freezes instead of automatically switched off and display stays on

I observing this from long time before reporting here but this happens every time. Don't know if anyone else is facing the same

Thanks
[Galaxy S II Android Development] arnab:
Josh if ur pushing regular updates why dont u add otaupdater app in ur kernel like I did. u can provide all changelogs all together in one go.
[Galaxy S II Android Development] Saber:
Seems interesting, will see what I can do ;)

Edit: I'll add OTA support in b027. For now I want to release b026 with important changes first :)

OT: I've fixed the Low latency audio issue (sound driver crash sound) we've been experiencing in some games for the next build.
[Galaxy S II Android Development] Saber:
DorimanX 11.0 b026 has been released.

The most important inclusion to this kernel is the low latency audio fix thanks to [MENTION=4293606]DualJoe[/MENTION]. If you don't know what the issue is, it occurs on certain games using newer unity engine versions. DorimanX kernel doesn't support it and/or has issues with low latency audio. So what I've done is I made the kernel delete the low latency xml file from the ROM on boot. As far as I know, deleting low latency audio support will not bring any issues to any dorimanX kernel since low latency audio doesn't work anyway, but if you require it at some point, reflash your current rom and use a different kernel! I don't know if I can bring proper support in the future but that is how it stands as of today. Please note that I've only tested this on CM12.1 official nightlies, but it should also work on other ROMs too.

I have also disabled auditd service where before, it has been seen flooding logs making it difficult of users to debug problems with apps and etc.

Other changes include many updates to the kernel's workqueue driver for a more efficient and stable operation and updates to tcp_yeah.

Enjoy this kernel! - gsstudios
[Galaxy S II Android Development] arnab:
I reported this guy. apparently he is spamming in all threads. Plz report him.
[Galaxy S II Android Development] Saber:
Reported just a moment ago. Now lets wait for mods to come in ;)
[Galaxy S II Android Development] Saber:
[MENTION=4293606]DualJoe[/MENTION]

Maybe your phone doesn't like DorimanX kernel :confused:

Sometimes battery drop happens to me to, but not all of the time.

AFAIK, bootloader or modem will have no impact on this (Sometimes it will, but rarely these days). Either hardware issue or something in the kernel that is causing you issues.

gsstudios
[Galaxy S II Android Development] Saber:
1. I've experienced this before. Seems to occur less when using stock launcher and on Linaro build.

2. Battery issue existed for quite a while now. I think a similar bug I've noticed was when I'm charging a really flat battery on a s2 with dorimanx kernel. It flickers and sometimes doesn't want to charge at all :confused: So maybe something is keeping it from charging/discharging/switching off properly.
[Galaxy S II Android Development] DualJoe:
Probably needs more testing to make sure but I think i found the culprit. Somehow i must have accidentally copied my untouched AFWall custom script to the phone that includes DNS redirection. That doesn't work with DorimanX indeed (if i reckon correctly dorimanx once even confirmed that) but i wasn't aware it was on the phone (and causes such side effects).

Just in case.. dont' try this on DorimanX (but feel free to use on working kernels):

Active DNS server can be checked on https://www.dnsleaktest.com.

$IPTABLES -t nat -D OUTPUT -p tcp --dport 53 -j DNAT --to-destination 208.67.222.222:53 || true
$IPTABLES -t nat -D OUTPUT -p udp --dport 53 -j DNAT --to-destination 208.67.222.222:53 || true
$IPTABLES -t nat -I OUTPUT -p tcp --dport 53 -j DNAT --to-destination 208.67.222.222:53 || true
$IPTABLES -t nat -I OUTPUT -p udp --dport 53 -j DNAT --to-destination 208.67.222.222:53 || true
[Galaxy S II Android Development] DroidNforcer:
[MENTION=4293606]DualJoe[/MENTION] [MENTION=5811506]gsstudios[/MENTION]

I can confirm the issue with the battery drop. I generally drops about

%40, when is 80 something, if the device is rebooted afeter some heavy usage or rebooted 2 or 3 times, it hapens. And sometimes it tries to recover the percentaje. My guess is that it has to do with the way LP manage the battery metter calculation, I thinks its different that from KK.

I could get working the transparent proxying on orbot, by adding the proxy setting to the wifi settings, I guess that with normal 2g/3g must work too, but i dont generally use a sim card in this phone.

The proxy settings are localhost or 127.0.0.1, port 8118, also check config on orbot about transparent proxying.

By setting on AFWall+ only orbot to network access. All aplications trafic is sent to tor. But this way you cant deny trafic to an specific app you would not want it to acces internet, every app has connectivity, so this is not ideal.

Orwall still doesnt work, even this way.

I havent yet tested the vpn this way, but I suspect it could work.

One suggestion, I dont know if this is kernel or rom related, but it would be good to the battery if on first boot, the screen is not set to maximum brightness. Some times it takes 10 minuts or more after a flash, reseted cache and the like. Having the phone working on maximum proccessor power plus maximum screen power, could contribute to the battery problems, plus an unnecesary early wear for people like us, who flash frequently.

Request: If an admin see this, please delete this acount, I've already sent a message to Mike, but to no avail. Thanks :D
[Galaxy S II Android Development] Skyline:
+1 for sudden drops in battery % after reboots

Edit: Not a big issue for me just reported Here if there chance to fix that's all :p
[Galaxy S II Android Development] souler456:
Hey guys... Isn't the battery drop issue already known on our device as our fuel gauge goes crazy when we attempt to do a hard reboot? Even I experience this on JB... It's nothing new...

BTW, A classic workaround for this is plug the charger in and reboot...

:D :) ;) :good:
[Galaxy S II Android Development] DualJoe:
Maybe it's an fsync issue on shutdown (cpu reset) so that caches don't get flushed properly and we end up with a corrupt battery stat file on next boot. We could try 'sync;sleep 1;sync' somewhere as shutdown script or as init 'on property' (Zygote down or something). Just a wild guess though.

[MENTION=5811506]gsstudios[/MENTION]:

Now i know why i've seen weird stuff in rootfs. To quote the init.rc:

The whole rootfs itself is world writable (777). That's not a good idea indeed. It should be 775.

:)
[Galaxy S II Android Development] Saber:
Good news guys, while I was working on bringing Marshmallow support, I found a fix to the screen off battery charging animation issue. Now it doesn't disappear forever!

Will be included in next build :)

gsstudios

Edit: Now it's not working :( So it was only working on first kernel install, probably permission related...
[Galaxy S II Android Development] Skyline:
Migrated to cm13 and missing Dori a lot. Hope it will come soon.

Thank You gsstudios
[Galaxy S II Android Development] Saber:
I'm still merging CM13 changes into the kernel, so it's a WIP ;)

gsstudios
[Galaxy S II Android Development] Skyline:
So, I am reverting back to LP. When there is new Dori builds(including 1st build) for MM will go back again to MM :D
[Galaxy S II Android Development] Saber:
While I was on MM, I noticed how smooth it was. I investigated and found that the OOM management is more aggressive than LP's profiles, so I synced them to my LP kernel. Also, you guys may/may have not noticed that the default, medium and low OOM profiles were the same, well that's all changed for the next build :)

gsstudios
[Galaxy S II Android Development] Skyline:
cm13 is damn smooth but currently not better than cm12.1 + dori as we all know that is the 1st nightly but hope it wiil become more stable in future.

I didn't noticed OOM profiles changes coz i keep it as it is.

Thanks

I am out of thanks today :silly:
[Galaxy S II Android Development] j1gga84:
I just wanted to ask you about the missing smootheness I know from KK times..

I like your work in continuing dorimanx kernel very much, no doubt :good:

But I must say, I miss the smootheness of good old KK times, CM11 from Markox89 with Dorimanx was flying, now, on CM12.1 by Markox89 with Dorimanx I have big problems with larger apps such as Facebook.

Yesterday I updated facebook in playstore but this update took 10 (!) minutes, 2 times the phone reboots out of nothing..

Also it take a long time in opening apps, especially larger apps and I don't know why.. I have installed around 150 apps but this was never a problem under KK or JB, even CM12.1 with stock kernel is running smoother and I think it is (hopefully) only one or some wrong settings in stweaks so I have attached my profile as a text file, would be great if you could have a look and give me some good tipps :good:

thanks & regards
[Galaxy S II Android Development] Saber:
[MENTION=4699854]j1gga84[/MENTION]

It seems you are still using my old profile.

Next build will have these OOM profiles refreshed again for better performance.

Change OOM profile for screen on to aggressive, screen off to default, dirty_background_ratio to 5. Over clock to 1.3GHz if desired. This should make heavy apps lag/freeze less.

Linaro build may be slightly better at heavy apps.

gsstudios
[Galaxy S II Android Development] prazola:
Ban this guy please.
[Galaxy S II Android Development] arnab:
Wtf again..i once reported him. As he did same in my post.
[Galaxy S II Android Development] wdevil12:
[MENTION=414800]arnab[/MENTION] [MENTION=5811506]gsstudios[/MENTION] TWRP 3 is out! we're all waiting its isorec version to flash over dori:)
[Galaxy S II Android Development] arnab:
Ya ..its just a version upgrade. Il give the ramdisk once I compile latest twrp soon enuf.
[Galaxy S II Android Development] Saber:
DorimanX 11.0 b027 has been released.

I have been working on Android Marshmallow for a few days now, however I was also working on Lollipop as well.

LMK/OOM profiles have been updated again to better match Android Marshmallow values and DorimanX LG G2 kernel. I have tested this build for a while now and it has been very smooth. As explained in an earlier post, earlier builds had the same values for default and medium. Low was basically the same as well but with the difference of the cost variables. Now each profile is different and will have a more noticeable change to performance.

UBER 5.3 toolchain was updated and all hotplug config was moved to the new HOTPLUG tab in stweaks.

Enjoy the update! - gsstudios
[Galaxy S II Android Development] makix13:
Oh man! You're our hero, incredible work, [emoji122] [emoji122] keep pushing S2 to the infinite and beyond [emoji2] .

Only a wish, support ext4 soon [emoji6]

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Android Development] prazola:
One question, can dorimanx mount ext2 or ext3 sdcard? What's the actual list of fs fully working?
[Galaxy S II Android Development] crash.1:
Thank you for great work!

Do you consider add support for f2fs to your kernel? On ace2 and note2 it was working flawlessly
[Galaxy S II Android Development] Saber:
Nope. F2FS does have it's advantages, but in this current stage, I don't see it as something worth doing.

gsstudios