Develop Bugs

[(KERNEL)] A dumb question about EXT4

[(KERNEL)] A dumb question about EXT4
a)Flashed CWM Kernel + EXT4 tools app. Converted system to EXT4.
b)Flashed Speedmod Kernel K15H. Convert RFS to EXT4 via recovery
c)Flashed Talon Dev 0.2.2. Automatic Convert system partition to EXT4.
1)Are there various type of EXT4?
2)Do I need to convert system into EXT4 each time I flashed a kernel?
3)Why each kernel could not recognize the system already EXT4 converted?
How do I verify the system is in EXT4? CWM EXT4 tool could not recognize ETX4 if you flashed with others kernel.
Can someone explain? many thanks

1) Ext4 or Ext4nj (nj stands for non-journalized), using Ext4nj is only for non critical data.
2) No, the new Kernel must try to know if you're already in Ext4, if it doesn't, it's stupid.
3) use the "mount" command in a terminal or via adb, if you see Ext4 in line with /system, /data, etc. etc., you're under Ext4 Lagfix.

No, there is no different kind of ext4. If you flashed stock rom with odin between each kernel transition, know that this reformat the file system to RFS. Ususally, i use chainfire ext4 tool to know if my FS is in ext4. Also, you should not haveto worry about changing FS to ext4 again after changing as you only change the kernel and not the FS. Next time can you post your question in question & answer sub-forum plz.

.Slane. said:
1) Ext4 or Ext4nj (nj stands for non-journalized), using Ext4nj is only for non critical data.
2) No, the new Kernel must try to know if you're already in Ext4, if it doesn't, it's stupid.
3) use the "mount" command in a terminal or via adb, if you see Ext4 in line with /system, /data, etc. etc., you're under Ext4 Lagfix.
Click to expand...
Click to collapse
true that there is journalised and non-journalised, but both can be mount the same way and are seen the same way by the system.

.Slane. said:
1) Ext4 or Ext4nj (nj stands for non-journalized), using Ext4nj is only for non critical data.
2) No, the new Kernel must try to know if you're already in Ext4, if it doesn't, it's stupid.
3) use the "mount" command in a terminal or via adb, if you see Ext4 in line with /system, /data, etc. etc., you're under Ext4 Lagfix.
Click to expand...
Click to collapse
Thanks man. I would strongly agree that each kernel should try to reconize the EXT4. Somehow, this not the case.

chadouming said:
No, there is no different kind of ext4. If you flashed stock rom with odin between each kernel transition, know that this reformat the file system to RFS. Ususally, i use chainfire ext4 tool to know if my FS is in ext4. Also, you should not haveto worry about changing FS to ext4 again after changing as you only change the kernel and not the FS.
Click to expand...
Click to collapse
Hi. As i said. Once you flashed another kernel, chainfire ext4 would not able to identify wheather your system is in Ext4. I'm using custom rom not stock.

Just to add on, frequent converting from/to Ext4 would cause some app to be force close. You have to reinstall the apps. What the hack!

F2FS for stock KK status

For those who don't know what is f2fs, please search in the google.
After long time of testing, researching, etc, I managed to get my stock KK to use f2fs in /system and /cache partition.
But /data partition no matter what flags i tried to edit fstab.qcom to get it to use f2fs, device will get into bootloop.
So now the f2fs is not in its full potential.
I give up to make f2fs work in /data partition in stock KK.....very tired.
LG stock maybe have hardcoded some parameters about /data partition, so f2fs don't work.
This usage of f2fs in /system and /cache in stock KK, required to use my new F2FS kernel(which build-in a modified fstab.qcom and fstab.geefhd) and my new twrp(with the ability to format partition to f2fs).
But i am not sure if i will share them, as the benefits of using f2fs in /system and /cache is so little.
Who will want it actually?
Prerequisite is a device with stock KK with 4.1.2 bootloader.
Wing

mukwing said:
For those who don't know what is f2fs, please search in the google.
After long time of testing, researching, etc, I managed to get my stock KK to use f2fs in /system and /cache partition.
But /data partition no matter what flags i tried to edit fstab.qcom to get it to use f2fs, device will get into bootloop.
So now the f2fs is not in its full potential.
I give up to make f2fs work in /data partition in stock KK.....very tired.
LG stock maybe have hardcoded some parameters about /data partition, so f2fs don't work.
This usage of f2fs in /system and /cache in stock KK, required to use my new F2FS kernel(which build-in a modified fstab.qcom and fstab.geefhd) and my new twrp(with the ability to format partition to f2fs).
But i am not sure if i will share them, as the benefits of using f2fs in /system and /cache is so little.
Who will want it actually?
Prerequisite is a device with stock KK with 4.1.2 bootloader.
Wing
Click to expand...
Click to collapse
Hi,
I was looking around and saw someone mention that TWRP would format /data and skip /data/media could you check on that.
If it works please do tell.
How did you put the 4.1.2 bootloader on a KitKat F240L?
I had that until i got an update from LG OTA and it replaced my CWM with stock bootloader.

Forget about this old post.
I have successfully used f2fs on /system /cache and /data on cm rom with modified kernel and rom.
(I decided not to share it. Because i shift back to stock rom as the benefit of using f2fs is not much on our phone) )
Just not sucessfully use f2fs on stock rom.
For keeping 4.1.2 bootloader on KK, first, flash back to kdz version of 4.1.2(then your bootloader will be 4.1.2), then use flashable zip method to upgrade to KK, thus your 4.1.2 bootloader will not be touched. If using kdz method to upgrade to KK, you will be using KK bootloader, which is troublesome.
Btw, it is no way using f2fs on /data without format the /data/media also, they are on one partition!
Wing

Recovery port with f2fs support

Hey guys,
i thinking about using f2fs on Nokia X
I format /data and /cache as f2fs and changed values in fstab.qcom and its work and it 2x faster than ext4 !
But i have one question, can anyone port recovery like twrp, cwm and philz with f2fs support
because in philz recovery /data and /cache not accessible

Cannot apply f2fs on N7105

Hi all, I tried to search every posts in the thread of wilson3q's unofficial build cm12.1, to see if the rom supports f2fs since I really love this rom. But I only found 1 post asking without answer. So may I ask is this rom supports f2fs for system, cache, and data?
Below were what I have done before but failed.
1. Flash AGNi pureCM kernel and reboot back to TWRP 2.8.7.0
2. Flash zips provided in the thread of AGNi pureCM kernel to turn my N7105's system, data and cache from ext4 into f2fs
3. Flash latest build of wilson3q's unofficial build cm12.1, then wipe cache/davik cache
4. Flash AGNi pureCM kernel again, then wipe cache/davik cache
5. Flash Open Gapps, then wipe cache/davik cache
After all these, I noticed the System partition is back to ext4 again, is this means wilson3q's unofficial build cm12.1 doesn't support f2fs? In addition, the rom loops in CM boot logo if the Data and Cache continue to be f2fs. Everything gets fine again if I change all the partition back to ext4.
Can anyone help?

erictrixis said:
Hi all, I tried to search every posts in the thread of wilson3q's unofficial build cm12.1, to see if the rom supports f2fs since I really love this rom. But I only found 1 post asking without answer. So may I ask is this rom supports f2fs for system, cache, and data?
Below were what I have done before but failed.
1. Flash AGNi pureCM kernel and reboot back to TWRP 2.8.7.0
2. Flash zips provided in the thread of AGNi pureCM kernel to turn my N7105's system, data and cache from ext4 into f2fs
3. Flash latest build of wilson3q's unofficial build cm12.1, then wipe cache/davik cache
4. Flash AGNi pureCM kernel again, then wipe cache/davik cache
5. Flash Open Gapps, then wipe cache/davik cache
After all these, I noticed the System partition is back to ext4 again, is this means wilson3q's unofficial build cm12.1 doesn't support f2fs? In addition, the rom loops in CM boot logo if the Data and Cache continue to be f2fs. Everything gets fine again if I change all the partition back to ext4.
Can anyone help?
Click to expand...
Click to collapse
In TWRP there is a setting to use "rm -f" instead of formatting. If you make sure this is on before flashing the ROM it might work. I remember doing this some years ago.
Installing the ROM usually formats /system as ext4 but that setting just wipes all files (shouldn't be any as you formatted to f2fs) and so keeps the old file system (f2fs) rather than formats the new (ext4).
This worked for me on my N7100 using Agni kernel (had f2fs support). In the end I stopped using f2fs since my phone would have the "sleep of death" so I had to pull the battery. Eventually this lead to massive corruptions of the file system on /data and I lost everything.
I read somewhere that f2fs speed advantage is not that great on read only partitions such as /system.
Anyway, that's my experience, it's up to you what you do now. Hopefully my advice works in your N7105.
Sent from my GT-N7100 using Tapatalk

DarrenNewsgroup said:
In TWRP there is a setting to use "rm -f" instead of formatting. If you make sure this is on before flashing the ROM it might work. I remember doing this some years ago.
Installing the ROM usually formats /system as ext4 but that setting just wipes all files (shouldn't be any as you formatted to f2fs) and so keeps the old file system (f2fs) rather than formats the new (ext4).
This worked for me on my N7100 using Agni kernel (had f2fs support). In the end I stopped using f2fs since my phone would have the "sleep of death" so I had to pull the battery. Eventually this lead to massive corruptions of the file system on /data and I lost everything.
I read somewhere that f2fs speed advantage is not that great on read only partitions such as /system.
Anyway, that's my experience, it's up to you what you do now. Hopefully my advice works in your N7105.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Thank you so much! I will try that when I get back to home!

OxygenOS 4.1.3 and f2fs

Which filesystem is used for /data and /cache by latest OxygenOS (Nougat based)?
If I have formatted these 2 partitions as f2fs do I need to change them to ext4 before flashing latest Oxygen_4.1.3.zip in TWRP?

Just f2fs on data for OOS

rg_gapa said:
Which filesystem is used for /data and /cache by latest OxygenOS (Nougat based)?
If I have formatted these 2 partitions as f2fs do I need to change them to ext4 before flashing latest Oxygen_4.1.3.zip in TWRP?
Click to expand...
Click to collapse
I would stay on ext4 there is no real difference only in really big application. Also don't encrypt your device since it can take up to 10 minutes to boot in TWRP when encrypted on F2fs! Also it is not stable yet.

FYI: Currently I'm using data as f2fs and cache as ext4 - that's how OOS 4 works by default.