Originally Posted by mankokoma

sorry 4 no reply yet. too much other things to do...
gonna test it when I can afford spending some hours on it.
but you mean to do the zcat command after having installed your kernel? coz then I will already know 4 sure.

sent from the desert with xda app

yes ofcourse after installing the kernel, all it does is check the config to see if ext4 is enabled or not

Tried your kernel, changed the app2sd script in a way, that it theoretically should act like my hybrid-data2sd settings....
So I did NOT change the data-partition from ext4 to ext2 and after flashing your kernel it did not boot (stucked in first Samsung logo, no adb possible - waited for about 10 minutes...) - CWM was possible, but no adb shell there, means couldn't check the zcat. So I assume, that it does not handle ext4...
It was not possible to change the kernel back to G3mod with update.zip - had to flash via ODIN.
For further experiments I still find no time now - just wanted to report the first steps...

Originally Posted by mankokoma

Tried your kernel, changed the app2sd script in a way, that it theoretically should act like my hybrid-data2sd settings....
So I did NOT change the data-partition from ext4 to ext2 and after flashing your kernel it did not boot (stucked in first Samsung logo, no adb possible - waited for about 10 minutes...) - CWM was possible, but no adb shell there, means couldn't check the zcat. So I assume, that it does not handle ext4...
It was not possible to change the kernel back to G3mod with update.zip - had to flash via ODIN.
For further experiments I still find no time now - just wanted to report the first steps...

Thanks for confirming that it doesnt support ext4 yet, and as you were using data2sd, data couldnt be mounted and thus the bootloop

Originally Posted by cdesai

Thanks for confirming that it doesnt support ext4 yet, and as you were using data2sd, data couldnt be mounted and thus the bootloop

Misunderstanding? I used Kyrillos' APP2SD-v2 in /etc/init.d and changed few things - not data2sd from g3mod....
Do you think it's not possible to handle that also?
Okay, of course I would have to change all to ext2 what I did not. Thought that this is the only problem (for now ).

Originally Posted by mankokoma

Misunderstanding? I used Kyrillos' APP2SD-v2 in /etc/init.d and changed few things - not data2sd from g3mod....
Do you think it's not possible to handle that also?
Okay, of course I would have to change all to ext2 what I did not. Thought that this is the only problem (for now ).

Dont confuse me!

see, you had an ext4 partiton on ur sd, and were using an app(or data)2sd script

And as my kernel runs init.d scripts, but doesnt support ext4, the script tries to move those folders to mmcblk0p2, which isnt mounted due to it being ext4

Convert to ext2, and it'll work (or rfs if you want xD)

no confusion! the point is that stl7 /data is also ext4... so the problem with the sd-partition is behind that

sent from the desert with xda app

Originally Posted by mankokoma

no confusion! the point is that stl7 /data is also ext4... so the problem with the sd-partition is behind that

sent from the desert with xda app

Just rfs partitions are mounted!