yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] RovG:
[MENTION=4663860]Computoncio[/MENTION]

From the following link: http://www.spinics.net/lists/linux-ext4/msg10413.html

"Running "e2fsck -y" vs. "e2fsck -p" will sometimes do "bad" things because the "-y" forces it to continue on no matter what. It looks like there was some serious filesystem corruption beyond the 8TB boundary, and the inode table for at one or more groups (depending on how many of the "SEVERE DATA LOSS POSSIBLE" messages were printed) is completely lost. ".

Please consider using the the e2fsck -p before e2fsck -fyc in your check partition script. Also could you consider adding e2fsck - V >> $ FILE at the beginning so that we can see what versions of e2fsck people out there have.

Lastly, I don't think that there is any benefit of the -c option in e2fsck -fyc on nand devices as bad block management is handled by the memory controller iirc.

Please check your pm. Tks
[Galaxy S II Android Development] Gamer015:
hot boots still happens occasionally, I don't know why. oh well, it's ageing now. currently on comp's 10.43 v107

Sent from my GT-I9100
[Galaxy S II Android Development] cybernetus:
Kit kat Bug

It will be solved on 4.4.3
[Galaxy S II Android Development] m1trand1r:
if we will get it at all....

How's your S-2 ?.....working fine?...

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] Spaulding89:
I hope we get 4.4.3. I need it [emoji12]

V108 runs stable smooth fast awesome since flashing. No hot reboots, SoDs or other Bad things [emoji106][emoji106][emoji122][emoji122][emoji12][emoji13]
[Galaxy S II Android Development] j1gga84:
I have the same, mostly when I quit an app, whatsapp for example..

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] Klaus20:
I have got the same problem. After reboot I just get the error message.

I do not know now what I should do because apart from the error message I see nothing.

Should I switch to an earlier version, if so, which one??

Regards Klaus
[Galaxy S II Android Development] cybernetus:
Yes

I'm on v105 and no problems :)

---------- Post added at 03:36 PM ---------- Previous post was at 03:34 PM ----------

I'm on v105.

I have the same error on v106/7/8
[Galaxy S II Android Development] stoneh:
Me too，hot reboots. v108 flashed~
[Galaxy S II Android Development] Misk77:
107 work fine but 108 doesn't reboot

Skickat från min GT-I9505 via Tapatalk
[Galaxy S II Android Development] cybernetus:
Forking the dorimanx repo :)

I will made a personal build for me without the changes :)

It's more safe for my beloved phone lol
[Galaxy S II Android Development] TheImpossibleEnemy:
a little Q

Can fixing partitions/memory blocks process somehow be related to files appearing in sdcard0/LOST.DIR folder after boot?Sometimes they differs greatly in size,like 32kb or 24mb.
[Galaxy S II Android Development] Computoncio:
It can related or it maybe be only bad deletions of files by apps.

I'm uploading v109 i have added [MENTION=4177034]RovG[/MENTION] suggestions to add -p flag before -yfv and removed -c flag also.

I have also updated e2fsck and tune2fs.static binaries.

Have done also some cosmetic in log-errors.html,binaries version are now printed in log and if you choose "fix partitions in every boot" like it was before the browser popup, the log-errors.html will be created but it will not open in browser, this way you can see better the corrupt partitions.

[MENTION=1670821]cybernetus[/MENTION] it's good that you have you phone back [emoji106] but I'm sure your trouble has nothing to do with my changes, the core is the same i only tuned and make exfat support possible, when using vfat/fat32 the code is the same.

I'm thinking on setting "Fix partitions on every boot" as default in stweaks, like it was before, what do you think?

Build v109 for all branches

Kernel_Dorimanx-V8.43v109-Comp-[01-48]-[27-04]-JB-SGII-PWR-CORE.zip MD5: 992595a1a0ccc02a63eb916f18a5c3a1

Kernel_Dorimanx-V9.43v109-Comp-mv2-[01-23]-[27-04]-JB-SGII-PWR-CORE.zip MD5: 7d5876b02bbd83bd6e01d09875847db5

Kernel_Dorimanx-V10.43v109-Comp-mv3-[00-58]-[27-04]-JB-SGII-PWR-CORE.zip MD5: fe29f3225907cee25927aba6142b6696

Commits:

Kernel V8: All binaries below needed for now to support exfat file system and fixing the partitions

Kernel V9-mv2: All binaries below needed for now to support exfat file system and fixing the partitions

Kernel V10-mv3: All binaries below needed for now to support exfat file system and fixing the partitions

initramfs: Support for exfat added to kernel, now waiting for roms devs;)

I will not change this two commits (kernel and initramfs) it is working good, so if you have cherry-picked it please reset and cherry-pick again. From now on, i swear, i will only add commits :angel:

If no issues appears in the next days i will send a pull request to [MENTION=2376110]dorimanx[/MENTION] to see if he want to merge now or wait till a rom dev add exfat or ext4 support for sdcard0 ;)

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v109-mv3

1st ROM : SlimSaber 4.4.2 Maliv3 by fusionjack build of 20140416 (Online)

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:
[Galaxy S II Android Development] TheImpossibleEnemy:
Just to be clear,does "fix partitions on every boot" to work requires "Cron" to be up and running?
[Galaxy S II Android Development] sien1996:
Latest v109 running well, seems good. Thanks computoncio :)
[Galaxy S II Android Development] sharp87:
All 10.43 v8, v9 and v10 running good [emoji106][emoji106][emoji5]
[Galaxy S II Android Development] Spaulding89:
10.43V109 boots fine on latest Slimsaber and runs very nice. Good Work [MENTION=4663860]Computoncio[/MENTION]
[Galaxy S II Android Development] m1trand1r:
Boot is super slow on my side with 109[emoji37][emoji37][emoji24]

143secs whereas on v107 it took 80-90 secs max......and android needs ages to load widgets and stuff on 109.....else it's running fine with one hotboot right after flash....lol....

Beam-ed through your pineal gland via//Android 4.4.2.:p//

---------- Post added at 11:59 AM ---------- Previous post was at 11:53 AM ----------

No.....it'll work without CRON enabled.....[emoji106]

and [MENTION=4663860]Computoncio[/MENTION] I have enabled fix partitions at boot everytime still I got hotboot on 109.....why?....Bloody Google?

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] Spaulding89:
[MENTION=3763274]rkoby13[/MENTION] thats freaky [emoji21][emoji20] on my side V109 boots faster as V107-108 but only a few seconds. And i dont have any hot reboot. Do i have a magic S2? [emoji56]
[Galaxy S II Android Development] sien1996:
Same here dude, I don't really go and measure my boot timings but v109 is good. Really no issues so far. Maybe we have magical S-2's :p
[Galaxy S II Android Development] ccerrillo:
root lost

Hi guys, i have a problem and i can't find how to solve it

I installed [ROM][4.4.2][04/16] SlimSaber - i9100 [SlimKat Unofficial Builds], and that rom is rooted, then i installed Dorimanx V10.43v108, and then after a reboot the screen goes black after dorimanx splash, so i reflased slimsaber and then dorimanx again because slimsaber rewrite the recovery to TWRP, after a reboot all starts well, but i lost root. I tried to do a factory wipe, cache wipe, dalvik wipe, reflash slimsaber, reflash dorimanx i tried the new 109 version, but nothing solves the problem.

What can i do to get root again?

Note that stweaks app is missing too
[Galaxy S II Android Development] jgcaap:
There migt be something messy for sure... But the issue is with Gustavo kernel works fine no freezes or sods. I miss this kernel configuration features and by giving that awnser for sure wont help on discovering whats wrong.. :) i AM going to havê a small vacation soon and ill try see when i get a SOD and get a log :p
[Galaxy S II Android Development] pSyCh¤_O_O:
What do you mean by: and by giving that answer?

Next time i will just not try to help you out AT ALL.

Is a non-existent answer a better answer? Coz thats what youre getting from me from now on [emoji6]

Edit. And just dont post next time you have trouble. Its your problem not kernel problem and im tired of seeing you complain all the time. Youre the only one with problems so its USER PROBLEM.

Use stock kernel or gustavos.
[Galaxy S II Android Development] Computoncio:
Go to setting => developer options => root access and enable root access.

If you install twrp stweaks gets removed, after you have root you can just flash dorimanx again and root will remains.

Your issue is you are using su from rom and not su from supersu.

Just follow the steps above and you you will have root again.

I too have hot-reboots but in logs it shows rom issues and not kernel issues, sometimes it's dalvik issues other times if the same bug of installing or removing apks ;)

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v109-mv3

1st ROM : SlimSaber 4.4.2 Maliv3 by fusionjack build of 20140416 (Online)

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:
[Galaxy S II Android Development] ccerrillo:
Enable root access in developper options has no effect, still without root

But i regained root, reflashing slimsaber, NOT flashing AIO gapps and flashing v100, i will try to isolate the problem and then come back again
[Galaxy S II Android Development] Computoncio:
Did you choose appand adb option?

Slimsaber thread has a lot of post from users without root issues too.

Dorimanx kernel used to force supersu apk and binary, but now if it finds a su binary it doesn't replace it, because if you install a new version of the binary it would be replaced by the version of the kernel on boot.

You could use the old root kit zip with supersu, it always works ;)

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v109-mv3

1st ROM : SlimSaber 4.4.2 Maliv3 by fusionjack build of 20140416 (Online)

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:
[Galaxy S II Android Development] ccerrillo:
I'm very confused :confused:, because before i did a factory wipe, flashed slimsaber, gapps and dorimanx and then rebooted and the root wasn't enabled and stweak and supersu wasn't installed

but now i don't know how i get it, this is what i did:

1. reflased slimsaber and checked that root is enabled

2. Install your dorimanx kernel v109 an checked that supersu and stweak are installed and i get root

3. Install slim AIO gapps

After that root is still enabled and stweak and supersu still installed

Thanks [MENTION=4663860]Computoncio[/MENTION] :victory::good::good:
[Galaxy S II Android Development] cybernetus:
I believe this is a good thing :)
[Galaxy S II Android Development] TheImpossibleEnemy:
+1

me too:good:

v109 works without issues btw:highfive:
[Galaxy S II Android Development] RovG:
[MENTION=5074262]StanTRC[/MENTION], Phil3579 found an old bug in CWM recovery sources.

http://xdaforums.com/showthread.php?p=52219977
[Galaxy S II Android Development] himsin:
Hello guys, I am trying dorimanx kernel after quite a long time. Last night I flashed 10.43 v109 (with kernel wipe), but when I rebooted my phone was very laggy and screen freezing. I could not open stweaks at all and was facing frequent other apps FCs. Can anyone let me kn0ow what am I doing wrong. Also when I tried to flash gustavo's kernel, I got status 7 error. I am on latest slimsaber if that matters.
[Galaxy S II Android Development] jgcaap:
Dear friend, i'm not here to judge on your behavior, perhaps my unpracticed English makes things harder to understand. I'll try to transmit my idea in another way...

In my opinion you are not helping, when you say it's my fault (or its users fault). Do you know how many times i formatted from 0 only this year because of this kernel? If i say that was around 40 times, would be a few. I've been having a frustrating experience with this new version of kernel of the BETA edition.

I was contacted by Computocio, which he helped me and created a new version of kernel (The FS), not for sure what does, but since the version 107 (or was the 106?), the boot loop issue was gone. I was pretty happy for that, because i am sure my phone, beside being old, has everything working fine.

I know that 99 % of the time is user fault, but i am tired to see people say exactly same thing for months, for an issue wich has been here also for months for many users, and many users were ignored because the members that use this kernel where 90% of them happy and 10 % having SODs (and the thesis used from many people was still, it's users fault). Since around november (not sure!), i've been having alot of issues, and after some months, only one person, was kind enought to believe that perhaps there was something different, and that was Computocio, which i am grateful and happy that he tried something different. And he solved the bootloop issue.

Now about the SODs, for months, i still say is something related how memory is configurated on the kernel. Why? Because on some apps, there is more lags compared to other kernels (there is something different, try use Gustavo kernel, or even stock kernel, using SwiftKey on different messaging apps, and use Dorimanx kernel, you'll see Dorimanx is less fluid. Why ? i do not know, but i know that i get SODs. I use the phone most for work and it's frustrating not to have things working as we need, but more frustrating, is people not wanting to give the benifit of a doubt that might be something wrong. Please sir, understand it.

I know you learned that speech from many Devs, the answer of, use stock and goodbye, this is not for noobs. And i ask you, here, in wich way is that an answer to give to anyone. But this, i'm not saying just to you, but to everyone.

I'm sorry if i sound arrogant or something, it never was my intention to offend you or anyone. I admire you here on xda, been very active and helpfull.

I hope i can clear things a bit with this post.

Again I remember, when I report, my intention is always to improve, not destroy anyone's work. Dorimanx had already my support (with small amounts ok, but is what i can give), and for over one year I've been giving some suggestions to improve Dorimanx kernel, as i tested alot of stuff to improve users experience. I do not believe i am something which does not know what i am doing, but at least i know i can be wrong.

Thank you.
[Galaxy S II Android Development] StanTRC:
I believe there are a lot of bugs. I have found two.
[Galaxy S II Android Development] ccerrillo:
Maybe you could try to wipe cache and dalvik, then reflash slimsaber again and then dorimanx v109, i have this combination and all works smooth and fine :D
[Galaxy S II Android Development] RovG:
Well [MENTION=5074262]StanTRC[/MENTION], whatever you are doing, you are doing a great job. Thank you for all that you do for us. Your recovery is the first that I notice that I can use to format a partition and then do an e2fsck that results in no errors.

BTW, have you seen my previous post http://xdaforums.com/showthread.php?p=52073712 regarding Philz touch recovery?
[Galaxy S II Android Development] StanTRC:
Thx! I'll try to build touch recovery later.
[Galaxy S II Android Development] RovG:
[MENTION=2376110]dorimanx[/MENTION], [MENTION=4663860]Computoncio[/MENTION], [MENTION=1670821]cybernetus[/MENTION] & [MENTION=5074262]StanTRC[/MENTION].

Running stock XWLSZ (JB 4.1.2), I can successfully execute the FSTRIM binary e.g. /system/xbin/fstrim -v /data but with this kernel I cannot. See output in screenshot below. Consequently, I also suspect that the discard option http://xdaforums.com/showthread.php?p=44524165on the mounted file systems does not work. We also don't seem to be mounting with discard option anymore (see attachment: mounts.txt). I don't know if this is contributing to the partition errors of "multiply claimed inode" & orphaned inode issue and would like to eliminate this as the cause.

Please can you also confirm if we have the Samsung recommended fixes http://xdaforums.com/showthread.php?p=52009519 for the eMMC issues or not, as some of the other workarounds have other side effects. E.g. mmc_cap_erase = 0 results in not being able to format the internal SD card from within the ROM. http://xdaforums.com/showthread.php?p=44467287

Please can you add support for FSTRIM into the kernel & recovery. You can use the binary from here to test: http://xdaforums.com/showthread.php?t=2534471

I am hoping thereafter to be able to run fstrim for each partition as a cron job say every 48 hours.
[Galaxy S II Android Development] pSyCh¤_O_O:
That goes to show this kernel is not for everyone.

I only answered your question of why do i think problem was on cybernetus side. And like i said....no problems on my side on same ROM+kernel so afaik its not kernels fault hence i suggested you to nuke the hell out of your phone. Thats all.

Did you do what i suggested?

-Use romnuke script

-Select default profile from inside recovery

-Dont install any of your usual apps and then test. If no sod you know its something youre installing afterwards.

Im pretty sure theres something youre doing wrong and because ive not had any problems in quite some time now. I use my phone every day. I dont have a secret kernel and im keeping quiet about it. Its the same kernel everyone is using and youre the only one with problems always. That...or your phone doesnt like dorimanx kernel. But it would be strange that youre phone is the only one not Dori compatible.

Kernel might not be perfect and it might need some changes but it definetly doesnt sod.

Good luck
[Galaxy S II Android Development] jgcaap:
I'll test again on weekend :)
[Galaxy S II Android Development] Computoncio:
I will see what i can do,i will check why discard option is not enable on mount, it was on, don´t now why it's off now, i can add the http://wiki.cyanogenmod.org/w/EMMC_Bugs patching and the FSTRIM replace in kernel but no eta, i'm without time this week :(

Only next weekend i will have time to do it, or sooner ;)

Great finding [MENTION=4177034]RovG[/MENTION] :good::highfive: that's what we need to make Dorimanx kernel even more stable and solid
[Galaxy S II Android Development] jgcaap:
i've formated today everything, internal sdcard etc.

After flashing the kernel:

how can i fix this?
[Galaxy S II Android Development] jgcaap:
while searching on the web for a fix i found out this page: http://xdaforums.com/showthread.php?t=2104326 and i remembered that i use the trim process on android 4.1.2 with philz kernel. But after flashing dorimanx it didnt work. After testing this app with kit kat 4.4 i noticed it doesnt work, according to the app, could be because of the kernel. Have anyone thought on making this compatible with our kernel? Perhaps could help sort some problems we might been having. Thanks
[Galaxy S II Android Development] smokerman:
im using Kernel_Dorimanx-V8.43v109-Comp-[01-48]-[27-04]-JB-SGII-PWR-CORE

with neat rom 5.9 JB and its running amazing..:D

but i have to say for KK roms i still use apollo regular with no problems at all..i might give a try with this kernel..wich version do you guys recommend (more stable at least) for Carbon rom for example? im still new here so any advice will be great.:)

ps: in wich roms we have to use maliv3 version?
[Galaxy S II Android Development] Fülesbagoly:
I have a problem with the V.109-dirnmaxal.

Boot after receiving this message:

https://www.dropbox.com/sc/uemheom3awi7jka/LPFA2LInet

https://www.dropbox.com/sc/gy652e14xn5jeg8/Wr0PlQnqUn

https://www.dropbox.com/sc/3xrk8w9epydtati/uNyuVB2Y_X

Is this file system errors, or V.109's bug?

What should I do?

Anyway, it works well.
[Galaxy S II Android Development] RovG:
Open STweaks, select tab called "OTHER", under "FS","FIX FILE SYSTEM ON BOOT", tap "FIX DATA ON or OFF button once and then reboot.
[Galaxy S II Android Development] Fülesbagoly:
Me to do the same thing? (Open STweaks, select tab called "OTHER", under "FS","FIX FILE SYSTEM ON BOOT", tap "FIX DATA ON or OFF button once and then reboot.)
[Galaxy S II Android Development] RovG:
Yes but do backups first using Titanium Backup and Nandroid.
[Galaxy S II Android Development] ccerrillo:
[MENTION=3930547]himsin[/MENTION] did you solve the issue?
[Galaxy S II Android Development] Fülesbagoly:
Thanks!
[Galaxy S II Android Development] himsin:
Tried dirty flashing rom and then kernel again but no luck, same problem. I think I should try a full wipe once (its been a while since I full wiped), but can do that only in weekend, so right now waiting for weekend to give it a one more try.
[Galaxy S II Android Development] jgcaap:
And alo psycho thank you for your help. Ill try look foward to test this better. For now it seems stable.

Computoncio have you had the opportunity to check the trim script? Thanks :)
[Galaxy S II Android Development] jgcaap:
Anyway to test if worked?
[Galaxy S II Android Development] RovG:
Reboot & then look at the log files named log-* in root i.e. "/". E.g. log-data. If it hasn't then repeat the process I gave you.
[Galaxy S II Android Development] StanTRC:
news

Hi!

Good news. [MENTION=4663860]Computoncio[/MENTION], [MENTION=1670821]cybernetus[/MENTION], I have pushed net updates

https://github.com/StanTRC/Dorimanx-SG2-I9100-Kernel/tree/net-merge

and fix for "/dev/__properties__" error

https://github.com/StanTRC/initramfs3

And bad news. It's not for V8 branch. Bluetooth is broken because of outdated proprietary blobs in the Summy ROMs.
[Galaxy S II Android Development] RovG:
[emoji24] wish sammy would just stop being so deceitful and meet its open source responsibilities.

---------- Post added at 08:41 AM ---------- Previous post was at 08:40 AM ----------

Some old but good info on TRIM: http://www.anandtech.com/show/7185/android-43-update-brings-trim-to-all-nexus-devices
[Galaxy S II Android Development] Computoncio:
Thanks StanTRC [emoji106], good job, i will see if i can build when i arrive at work.

I already added the mount options like it was in dorimanx post, is the old days ;)

The patch for the emmc firmware i must find a kernel with it because in dorimanx the file is different and i don't want to mess with thinks i don't understand :P

I can get fstrim to work, i will see what i can do in kernel side, and see if slimsaber has ftrim support.

Good work mate. That's what we need [emoji106]

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v110-mv3

1st ROM : SlimSaber 4.4.2 Maliv3 by fusionjack build of 20140416 (Online)

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:
[Galaxy S II Android Development] RovG:
Great! Thanks [MENTION=4663860]Computoncio[/MENTION].

Perhaps CM, Omni Rom or Gustavo's kernel may have it. Hoping maybe master [MENTION=2376110]dorimanx[/MENTION] may help us out here[emoji16]

Since support for trim was introduced by Google since Android 4.3. I AM assuming any 4.3 based kernel should have support for it.

---------- Post added at 02:46 PM ---------- Previous post was at 02:13 PM ----------

I agree with you 100% because there is always the possibility of creating super bricks especially with devices susceptible to the wear leveller bug.

We must proceed cautiously.