I own a Motorola DROID TURBO (XT1254) with unlocked bootloader and the Stock ROM /data and /cache partitions are in f2fs filesystem and /system is in ext4 filesystem and I have some doubts and questions:
1. Some Custom ROM's like LineageOS on this device can be installed with /data and /cache partitions formatted in ext4 and f2fs, In your daily Stock or Custom ROM in which filesystem are formated the /data, /cache and /system partitions?
2. I read that the f2fs filesystem are used by Motorola on Stock ROM's due to notable higher write speeds (this helped to the Nexus 7 2012 owners, because has eMMC bug) but has more chances of data corruption (in some devices exists the garbage collection problem), and ext4 is more reliable for data and has higher read speeds. What are you experience with ex4 and f2fs filesystems on Android? and in DROID TURBO/Moto Maxx, which is better for you?
3. Apart for Motorola, Samsung create the f2fs filesystem but not use it in their devices, Huawei uses f2fs filesystem since Android 7.0 Nougat/EMUI 5.0, OnePlus tried it on OnePlus 3/3T, but in OnePlus 5/5T switched back to ext4. Google says "F2FS isn’t supported for the internal storage as it doesn’t support inline hardware encryption", and Android 7.0 Nougat and higher supports Direct Boot and file-based encryption but only in ext4 filesystem. A website says that the Motorola Moto Z (an other Motorola device) are faster than Google Pixel (XL?), because the Moto Z uses f2fs filesystem.
4. It would be good to share the used filesystem in your phone and in which ROM uses this filesystem.
Note: Can you check partitions filesystem with Diskinfo app or TWRP in Wipe> Choose partition> Repair or change filesystem
This information and questions apply for all DROID TURBO/Moto Maxx owners (XT1225, XT1250, XT1254)
I like to know your opinions about the ext4 and f2fs filesystems for DROID Turbo/Moto Maxx
In case of necessity, I post it also in Moto Maxx sub-forum
No one replied here?
Related
I've been playing around with the CM-mod/S7 and can sucessfully make it boot with all ext4 partitions.
Backround information:
Parititions and formatting
Partitions are the basic unit of storage on my devices with storage (think C: D: E: if you use windows)
The standard layout of android devices:
A /cache partition
A /data partition
A /system partition
Other hidden partitions (this part isnt relevent to us)
The common filesystem formats for recent android devices are EXT 3 and 4 (4 being the newer obviously)
The S7's default partitions:
stock 3xx: (ie froyo)
/cache: ext3(?)
/data: ext3(?)
/system: ext2
stock 5xx: (ie honeycomb)
/cache: ext3
/data: ext3
/system: ext4
my ext4 mod:
/cache: ext4
/data: ext4
/system: ext4
All other devices that launched with HC installed use all ext4 partitions.
But the S7 didnt launch with HC, it launched with froyo.
Dell couldnt upgrade /data to ext4 without wiping user data.
They could upgrade system, since they wipe it on install anyway.
Cache they didnt for the outside chance a user had actual important data in it.
My proposal
What I propose is a modified version of CM9-mod with /cache and /data formatted as ext4 partitions.
I've already got a working version, the main issue is that:
I dont know what the difference is. I've ran quadrant with ext4 and again with ext4, and there's very little difference.
Since quadrant has an I/O and database benchmark (and they run on /data), at least it shows that there's only 1% change in scores.
Would anyone actually be interested in using an ext4 mod?
There are some downsides (depending on how you view it):
ext3 and ext4 nandroids arnt compatable
You will need to do a fac reset on first install (as it reformats)
You will need seperate versions of CM9-mod and CWM
This space for rent
A simple modification of the boot.img to change init.streak7.rc mount points to ext4, easy as pie.
Yea that's what I did, along with a CWM recovery.fstab mod.
But like I said I havnt really noticed any changes in quad, and it's using /data for it's tests
As soon as I get wifi up and working on cm10, going to see if there is any benefit to switching
Sent from my Nexus 7 using Tapatalk 2
I can test it tomorrow.
Sent from my PG86100 using xda app-developers app
People around i9300 kernel developement backported F2FS and managed to boot modified omnirom.
Should I bring this stuff to upstream?
GR0S said:
People around i9300 kernel developement backported F2FS and managed to boot modified omnirom.
Should I bring this stuff to upstream?
Click to expand...
Click to collapse
f2fs for external SD cards: Sure
f2fs for /data - Not until the next Android revision, you can put all the infrastructure there, but changing from ext4 to f2fs would require wiping /data
Entropy512 said:
f2fs for external SD cards: Sure
f2fs for /data - Not until the next Android revision, you can put all the infrastructure there, but changing from ext4 to f2fs would require wiping /data
Click to expand...
Click to collapse
Wiping is okay.
We can try f2fs on /system, it gets formatted each time anyway. I know it won't give us massive performance boost, but it will be nice start point for now.
Why we can't use f2fs on /data?
Moto X has it already.
PS: can I use debian's arm binaries in recovery? Specifically f2fs tools.
GR0S said:
Wiping is okay.
We can try f2fs on /system, it gets formatted each time anyway. I know it won't give us massive performance boost, but it will be nice start point for now.
Why we can't use f2fs on /data?
Moto X has it already.
PS: can I use debian's arm binaries in recovery? Specifically f2fs tools.
Click to expand...
Click to collapse
Because /data is currently ext4 on the device you specified initially, and you can't change filesystems without wiping. Making users wipe at this point in the 4.4 cycle is NOT OK.
Not much if any benefit of f2fs on /system - Moto G doesn't even use f2fs for /system (it does for /data)
Entropy512 said:
Because /data is currently ext4 on the device you specified initially, and you can't change filesystems without wiping. Making users wipe at this point in the 4.4 cycle is NOT OK.
Not much if any benefit of f2fs on /system - Moto G doesn't even use f2fs for /system (it does for /data)
Click to expand...
Click to collapse
Anythng else? Will it work as intended if I will just patch kernel, patch device, format.
I remember Dees_Troy mentioned /data/media trickery may not work.
Hello guys, i've a question, I did a fatory reset on my phone and lost all my data, I did a lot of research and was able to create a img file will all my data using some adb commands, but now I'm stuck because the motox 2014 uses f2fs filesystem and not ext4.
I need to convert a .bin image that is in f2fs to ext4 without loosing it's content, any of you have any idea how to so it?
The forensic tool FTK Imager does not read f2fs filesystem.
Thanks
Guys I'm new here and I do not know much about roms or recovery modes and it's functions. I have a question for you. Some of the roms support f2fs filesystem but whenever I try to install them on my device, it flash roms by using ext4 function. I have never be able to flash them by using f2fs. For example Los 13, Los 14.1, RR roms have f2fs filesystem support. I convert my system and cache to f2fs from ext4 but it doesnt work at all. It installs the roms by using ext4 always. How can I flash them with f2fs filesystem. I have heard that f2fs is faster than ext4 therefore I want try it
Follow these steps:
novafusion.pl/tutorials/how-to-use-f2fs-s3-mini/
danilisilva7 said:
Follow these steps:
novafusion.pl/tutorials/how-to-use-f2fs-s3-mini/
Click to expand...
Click to collapse
I have tried that but whenever I try to install a rom with a filesystem formatted as f2fs, it converts it to ext4 at the beginning of the installation. Can I convert my filesystem after installing a rom? For example after the installation of LineageOs 14, can I convert my filesystem as f2fs? Does it harm my phone?
Hi, wouldn't it be sufficient to switch to a custom kernel with f2fs driver to be able to run MIUI with a f2fs file system? It is even possible? With LineageOS you still cannot use f2fs on the /system partition (maybe in the initial ramdisk there is no f2fs driver ?) but at least /data and /cache partition, also on MIUI. Is there a way to do that?
I'm trying without success, installed a custom kernel which claims to have f2fs support, formatted the cache partition in f2fs to do some testing, typed the 'df' command in the linux shell but no cache partition is displayed.
Using f2fs on the /system isn't a good idea to begin with, the /system is a read only partition so you wouldn't benefit from anything that f2fs gives.