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.
Hello. Previously i had the lollipop 5.0.1 gpe , wich use the file system ext4 but now i am running the stock motorola lollipop 5.0.2, and remains the file system ext4 (motorola stock rom support both ext4 and f2fs). I know the advantages of use f2fs and i want to convert from ext4 to f2fs . Since i have a otg pen drive, it is possible to do a nandroid backup to backup everything, than change the file system and then restore all? In this way everythong will work without troubles and the phone will be the same as was? Thanks in advance
Hi all! I'm running CM13 Snapshot, with ElementalX. As now I formatted /data and /cache in F2FS. Would it be worth to also format /system in F2FS, since is mostly read-only?
Well you simply can't, every ROM installation will re-format /system to ext4 automatically. And even if you could, you probably can't notice any improvements on the Nexus 5. The Nexus 5 still has pretty powerful hardware which can handle almost everything without any problems so I wonder why you would want to have /system formatted to F2FS. In my experience things never really got that much better with the /cache and /data formatted to F2FS, only benchmarks scores got a bit higher. In my opinion F2FS is pretty useless on this device. Could be helpful for lower end ones.
Thanks for the answer! I must say i jumped on the f2fs train without doing any benchmarks, and also going from KK to LP long time ago, so I couldn't do a proprer comparison. Also I didn't think about the rom installation process reformatting...well than my question is pretty useless
Short answer, no. From what I've read, F2FS has slightly better write speeds than ext4 and slightly worse read speed. On a partition that you write often to, such as data and cache, it could be beneficial because of the better write speed. But on the system partition, it would even cause performance drop since it's read-only.
No.
The system partition is mounted mostly with ro permissions anyway.
Write operations are few and rare.
Finally, f2fs seems to have more overhead (allocates more space) which might be an issue for devices with small-ish system partitions.
I'm currently on AOSPExtended ROM(7.1.1) with it's stock kernel. I recently heard about f2fs system which is more faster and has increased life span of flash storage than current ext4 system.
Now I want to know whether this ROM and kernel are f2fs compatible, and how can I change my partitions to f2fs in detail without loosing my current data.
Thank you.
in previous iterations of android, only data partition was allowed to be in F2FS format (by default data partition is in F2FS format unless you have a GPE device). all the rest should be in ext4. some kernels allow cache to be in F2FS thats all. you can format some partitions to F2FS via TWRP recovery. however if any F2FS partition is unsupported you will endup in a bootloop.
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?