[Q] What file systems do phones use? - General Questions and Answers

Hello, samsung phones (at least i9000) uses RFS (or something like that) as default partitions which causes the lag, and you can convert to EXT4 to make it faster.
What partitions do other phones like HTC use? EXT4 by default?

YAFFS2 or EXT4 are the ones officially supported by Android I believe. Samsung however added RFS, and some ROM developers add other filesystems such as UBIFS

Neleor said:
YAFFS2 or EXT4 are the ones officially supported by Android I believe. Samsung however added RFS, and some ROM developers add other filesystems such as UBIFS
Click to expand...
Click to collapse
What does HTC sensation use by default? Just wondering because a friend is saying its ext4 but i thought that wasn't a default.

Please use the Q&A Forum for questions Thanks
Moving to Q&A

Related

[Q] Samsung Behold II & ext4 support

Does anyone know if the Behold II supports ext4 partitions? I know that BH_Man's roms support ext3 (which I currently use for apps2sd). Nu11u5 came out with a rooted kernel based on the 1.6 OTA update; however, it doesn't support apps2sd. I was thinking of upgrading my ext3 apps2sd partition to ext4 but I wanted to make sure that it will work first. I tried contacting BH_Man, but he hasn't responded yet.
Since no one has responded, I thought I would add what I found out about ext4 support in the Behold II [BH2]. According to the source code, It seems that the BH2's kernel does indeed have support for ext4; however, I was unable to verify that Samsung actually compiled their kernel with ext4 support.
Back in the old day, before Cyanogen and Amon_Ra's recovery, to upgrade an ext3 partition to ext4, this was all that was needed:
Code:
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -fpDC0 /dev/block/mmcblk0p2
When I ran those commands in recovery mode via adb, tune2fs refused to run because of a missing mtab file (meaning tune2fs couldn't verify that mmcblk0p2 was mounted or not). I could be that I needed to use a newer version of tune2fs (but I'm too lazy to compile it myself). Whatever I tried, tune2fs wouldn't run. I actually had to use Acronis Disk Director to upgrade from ext2 to ext3 as I ran into the same problem before btw. I decided to give up and just use ext3 for app2sd. It works well and the slow down isn't really noticeable. Plus I like the added bonus of the journal.
The moral of the story: When buying a phone, make sure there is an actively developed ROM for it (like Cyanogenmod). Otherwise, forget about hacking it.

[Q] How to convert to ext2?

Is there any recovery or script for Desire S that can convert filesystem type to ext2?
Standard CWM 5.x does not have any convert option, 4EXT which I installed moment ago only converts to ext4 (pointless...).
You can use Linux commands in adb shell. Google the one you need.
Edit: this should do
If you do not have the binaries (e.g. commands) download the package from here, post 7, point 2. In the same post there is a description how to transfer them to the phone
why you what to downgrade to ext2
Who told ext4 is upgrade to ext2? Higher number does not mean better. Agree, ext4 originates from ext2, but these are just another file system types with different purpose.
And I think ext4 is an overkill because I just don't need journaling on... mobile phone.

[Q] nexus s fstrim on /cache /system partition

Hello,
i am using lagfix on my nexus s. But by default , only /data partition is selected for trim command.
Can i check /system and trim it also safely without bricking or any other issues?
secondly.. the /cache partition is disabled altogether.. and i get a prompt that the /cache partition isnt supported due to hardware or due to the limitations of the kernel on the device. So my query.. whats the limititation? the h/w or the default cm10 kernel? is there a kernel that i can use so as to get trim to run on /cache partition? is it possible..
please share your opinion.
my nexus s seems to start lagging a lot . i want to bring it back to life.. any proven suggestions would be appreciated.
Thanks so much XDA community.

[Q] How to determine if the rom is F2FS or ext4

I am looking to figure out how to know if a rom is F2FS or ext4?
I see people are talking about the rom is ext4 or F2FS. I'm a flash happy person and would like to not flash wrong.
pctechdroid said:
I am looking to figure out how to know if a rom is F2FS or ext4?
I see people are talking about the rom is ext4 or F2FS. I'm a flash happy person and would like to not flash wrong.
Click to expand...
Click to collapse
In most cases it is ext4 by default. If it is F2FS compatible, it should be explicitly written in the OP. If you still can't figure it out, just ask
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!

For Moto Maxx/DROID TURBO, What is the best filesystem, ext4 or f2fs?

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 Moto Maxx/DROID TURBO, 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 Moto Maxx/DROID TURBO owners (XT1225, XT1250, XT1254)
I like to know your opinions about the ext4 and f2fs filesystems for Moto Maxx/DROID TURBO
In case of necessity, I post it also in DROID TURBO sub-forum
No one replied here?
lat94084 said:
No one replied here?
Click to expand...
Click to collapse
This was very hotly debated three years ago, in late 2014 and early 2015 -- mostly dealing with the XT1225. You can probably dig up old threads over in the Droid Turbo forum where it was discussed. (We were all in one forum back then. It was the "All Quark" forum.) The forums were split in September 2015, but some of the threads never got moved. Droid Turbo finally got bootloader unlock in November 2015, thanks to Sunshine, but by then the topic was no longer being discussed.
There was some reason why the topic was dropped and everyone just went with the default system. Maybe didn't work well with TWRP backups or something about encrypting? Also, there was false low storage warnings. I don't remember. I just remember it was too much hassle so everyone didn't bother.
ChazzMatt said:
This was very hotly debated three years ago, in late 2014 and early 2015 -- mostly dealing with the XT1225. You can probably dig up old threads over in the Droid Turbo forum where it was discussed. (We were all in one forum back then. It was the "All Quark" forum.) The forums were split in September 2015, but some of the threads never got moved. Droid Turbo finally got bootloader unlock in November 2015, thanks to Sunshine, but by then the topic was no longer being discussed.
There was some reason why the topic was dropped and everyone just went with the default system. Maybe didn't work well with TWRP backups or something about encrypting? Also, there was false low storage warnings. I don't remember. I just remember it was too much hassle so everyone didn't bother.
Click to expand...
Click to collapse
The DROID TURBO I own have unlocked bootloader thanks to Sunshine (is a little expensive, but is worth it), I asking about ext4 or f2fs as filesystem for /data partition, the DROID TURBO Stock ROM is the /data partition formatted as f2fs, but the majority of Android devices the /data partition is formatted as ext4 and some questions and comparation between both filesystems for /data partition
Three questions: ¿The /data partition of your phone is formatted now as ext4 or f2fs?, ¿The encryption is working on both filesystems or only one (ext4 or f2fs)? and ¿Your phone is in the Stock ROM formatted the /data partition as ext4 or f2fs?
I published this in DROID TURBO forum, but no one replied here.
lat94084 said:
The DROID TURBO I own have unlocked bootloader thanks to Sunshine (is a little expensive, but is worth it), I asking about ext4 or f2fs as filesystem for /data partition, the DROID TURBO Stock ROM is the /data partition formatted as f2fs, but the majority of Android devices the /data partition is formatted as ext4 and some questions and comparation between both filesystems for /data partition
Three questions: ¿The /data partition of your phone is formatted now as ext4 or f2fs?, ¿The encryption is working on both filesystems or only one (ext4 or f2fs)? and ¿Your phone is in the Stock ROM formatted the /data partition as ext4 or f2fs?
I published this in DROID TURBO forum, but no one replied here.
Click to expand...
Click to collapse
I don't use encryption on mine or my wife's phone. My phone is formatted however TWRP formatted it. @bhb27 our official TWRP dev and who maintains two popular ROMs recommends f2fs.
[RECOVERY][OFFICIAL TWRP 3.1.1][For all Quark][Moto Maxx/Turbo and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=62363432&postcount=2
[QUOTE @bhb27]The format of data partition is different, in 4.4.4 is ext4 and 5.x.x is f2fs.
I have restore more then 100 times in my test, in some i end-up in a "bad/bug ROM" and it happens when flash 4.4.4 over 5.0.2 or vice versa, in the most bad one the device lost response of the touch screen even in the recovery, the bug was simply resolved by restoring to stock via fastboot using files from a stock XML rom. In others bug's android boot after boot i try to unlock to use and it reset, and stay in that loop, boot try to unlock reset, i try to wipe everything but system and did not work, in all those case partition format of data was wrong.
TWRP will backup the partition exactly how it is, If the backup is EXT4 and the Data partition of the device is f2fs TWRP will restore the data and will not change the format.
That may cause a problem, so when restoring to a different OS version advanced wipe the partition and change the format.
To do that click Wipe>advanced Wipe> select Data> click on Repair or change File System>change File System>
For Kitkat android 4.4.4 choose EXT4
For lollipop android 5.x.x choose F2FS
____________
This will not affect custom ROM, but i recommend to use f2fs.[/QUOTE]
In conclusion /data formatted as f2fs is better for Moto Maxx/DROID TURBO than ext4. I asking because only some Android devices use /data partition as f2fs because the majority is formatted as ext4. In Nougat custom ROM'S is f2fs better? And ChazzMatt your phone is formatted the /data partition as f2fs or ext4?

Categories

Resources