Hi All!
I just made my first custom ROM:
It based on stock 2.2 JPF: only modification is rooting and converting to ext2 data system and cache partitions.
Flash it after flashing full stock JPF (My ROM don't contain bootloader, modem etc, so you must first flash stock JPF)
DON'T wipe after reboot, it will format you data and cache partitions back to RFS. I don't changed recovery binary, so please don't wipe if you want ext
ROM works OK for both rfs and ext2, so it will work, but no point to use my ROM with rfs
Any feedback is appreciated.
Update:
My JPM ROM converted to ext4
Stock firmware, only changes are rooted, busybox, fugutweak, (removed Layar and thinkfree for space, ext4 left less space for users ;( )
quadrant score is 470
Used apollo5801 kernel with modified initramfs to allow ext4 ext2 and rfs FS on all partitions, it use possibility to have data2sd
As for me, use ext4 for /system is has no much sense. Better use ext2 for /system and /cache, wile using ext4 for /data
/system normally is R/O, /cache has no vital information, so it better to use it with ext2 for performance
URL for ROMs:
My JPF ext2 ROM: http://www.multiupload.com/KQBT92RM0U
My JPM ext4 ROM: sorry, link removed, it has issue with WIFi
Interested in it. Give a detailed list of steps, please.
mumbozver said:
Hi All!
I just made my first custom ROM: sorry, I have no posts yet, and can't attach
It based on stock 2.2 JPF: only modification is rooting and converting to ext2 data system and cache partitions.
Flash it after flashing full stock JPF (My ROM don't contain bootloader, modem etc, so you must first flash stock JPF)
DON'T wipe after reboot, it will format you data and cache partitions back to RFS. I don't changed recovery binary, so please don't wipe if you want ext
ROM works OK for both rfs and ext2, so it will work, but no point to use my ROM with rfs
Any feedback is appreciated.
Click to expand...
Click to collapse
Hello,
I am interested in your ext2 ROM.
It's not quite clear for me how to flash it. I mean this: "DON'T wipe after reboot". Do you mean I should not do a factory reset? What about factory reset right after flashing stock JPF?
Would you write a detailed list of steps?
Thank you.
szabof1 said:
Would you write a detailed list of steps?
Click to expand...
Click to collapse
My ROM is kind of POC, it's not customized or so, main goal is try ext2 instead of rfs
1 - Flash stock JPF firmware.
2. - After flashing stock JPF you may do "wipe data/factory reset", or don't do factory reset.
3. - Flash my ROM.
4. - After reboot don't do "wipe data/factory reset" or "wipe cache partition", just choose "reboot system now"
If you do all right, you will get system data and cache partitions in ext2, only efs partition will stay in rfs.
mumbozver said:
Hi All!
I just made my first custom ROM: sorry, I have no posts yet, and can't attach
It based on stock 2.2 JPF: only modification is rooting and converting to ext2 data system and cache partitions.
Flash it after flashing full stock JPF (My ROM don't contain bootloader, modem etc, so you must first flash stock JPF)
DON'T wipe after reboot, it will format you data and cache partitions back to RFS. I don't changed recovery binary, so please don't wipe if you want ext
ROM works OK for both rfs and ext2, so it will work, but no point to use my ROM with rfs
Any feedback is appreciated.
Click to expand...
Click to collapse
hello. you converted the partitions /system /data and /cache to .ext2.
With a factory reset, the partitions will be converted back to .rfs?
kyrillos13 said:
hello. you converted the partitions /system /data and /cache to .ext2.
With a factory reset, the partitions will be converted back to .rfs?
Click to expand...
Click to collapse
Hello
system partition in any case will stay in ext2
"wipe data/factory reset' will reformat data and cache partition to rfs
"wipe cache partition" will reformat cache partition to rfs
Because of this don't do factory reset if you want test ext2 for data or cache partitions
P.S. looks like we need tweaked/custom recovery, if you know any - send me a link, pls
does it is working
I flashed your ROM
Hello,
I flashed your ext2 ROM just now.
Everything seems to be OK.
mount shows:
"/dev/block/stl6 /system ext2 rw,relatime,errors=continue 0 0
/dev/block/stl7 /data ext2 rw,nosuid,nodev,relatime,errors=continue 0 0
/dev/block/stl8 /cache ext2 rw,nosuid,nodev,relatime,errors=continue 0 0"
It is rooted and has busybox installed by default! Thanks.
Stock JPF upgraded by your ext2 ROM still workes well.
I also use Link2SD with 2nd (ext2) SD card partition for selected programs.
Is ext3 file system supported on SG3?
If yes, is it possible to convert /system, /data and /cache partitions to ext3 instead of ext2?
szabof1 said:
Is ext3 file system supported on SG3?
If yes, is it possible to convert /system, /data and /cache partitions to ext3 instead of ext2?
Click to expand...
Click to collapse
it isnt possible. When sammy release froyo kernel sources we will convert the partitions to ext4...
I do not know ext4. Why is ext4 better than rfs? What is the performance difference between ext2, ext4 and rfs?
szabof1 said:
I do not know ext4. Why is ext4 better than rfs? What is the performance difference between ext2, ext4 and rfs?
Click to expand...
Click to collapse
From my ext2 ROM: overall performance index by Quadrant increased from 325 to 520 after converting from rfs to ext2
ext4 is must be faster than ext2, but it uses more CPU, so need to get real user experience.
hi mumbozver,
what do you think about deodexing? does it make sence make ROM deodexed if this ROM is converted to ext2? i have heard some thoughts deodexed rom is not faster than non-deodexed... the higher performance is reached by ext2, not deodexing. is it true?
anly11 said:
hi mumbozver,
what do you think about deodexing? does it make sence make ROM deodexed if this ROM is converted to ext2? i have heard some thoughts deodexed rom is not faster than non-deodexed... the higher performance is reached by ext2, not deodexing. is it true?
Click to expand...
Click to collapse
Deodexing is increase first boot time after flashing and decrease available space in /data partition, but increase space in /system (you will get half of space, that you are wasting in /data. In deodexed ROM you need to store odexed "classes.dex" in /data/dalvik-cache and zipped deodexed "classes.dex: inside *.apk or *.jar files on /system).
So you will get lesser overall free space in you phone and slower first boot. Thats all about deodexing performance.
Main reason to get deodexed ROM is ability to change themes, and possibly put in /system some program of user choice, so programs will survive factory reset. But in my ROM factory reset will convert /data and /cache partitions back to rfs, so deodexing in my point is not needed.
i have flashed your rom, everything seems to be ok. quadrant score: over 500
mumbozver said:
Deodexing is increase first boot time after flashing and decrease available space in /data partition, but increase space in /system (you will get half of space, that you are wasting in /data. In deodexed ROM you need to store odexed "classes.dex" in /data/dalvik-cache and zipped deodexed "classes.dex: inside *.apk or *.jar files on /system).
So you will get lesser overall free space in you phone and slower first boot. Thats all about deodexing performance.
Main reason to get deodexed ROM is ability to change themes, and possibly put in /system some program of user choice, so programs will survive factory reset. But in my ROM factory reset will convert /data and /cache partitions back to rfs, so deodexing in my point is not needed.
Click to expand...
Click to collapse
Thanks for the ROM.... Just a question of how long the battery lasts...? Is it over a day...
Vishnu N S said:
Thanks for the ROM.... Just a question of how long the battery lasts...? Is it over a day...
Click to expand...
Click to collapse
It depend of usage pattern.
I use it lightly, just few minutes of call per day, but always on Wi-Fi or 3G connection, skype chats and email checks.
After Gallery3d removal it run something about 2 days.
mumbozver
I don't understand.
Yesterday was your explanation about deodexing.
Now i can't see this one
Why?
Is this a "postmoderating"?
Add.
Sorry.
It's very strange. I see it again!
kyrillos13 said:
it isnt possible. When sammy release froyo kernel sources we will convert the partitions to ext4...
Click to expand...
Click to collapse
Now we have sources
I did quick test for ext4 enabled kernel from here: http://forum.xda-developers.com/showthread.php?t=978823
Just flashed zImage to my ROM. everything looks OK for now, so I will make ext4 ROM in few days, probably based on JPL.
There seems to be a lot of confusion or pr people aren't being clear enough. At the moment there's one build found here http://forum.xda-developers.com/showpost.php?p=65193930&postcount=1302 that has F2FS as an option to change to. But I recall there being a problem with the /cache partition too small for F2FS to work, and if you look into F2FS's internal operation a bit, if /cache isn't F2FS then it's pointless.
So I'm asking, is there any TWRP build that supports formatting system/cache/data partitions as F2FS? Is there a way to fix whatever the problem is with /cache unable to be formatted to F2FS? The error I get when I try to format with F2FS is this:
Code:
mkfs.f2fs -t 0 /dev/block/mmcblk0p38 process ended with error: 255
Unable to WIpe Cache
Error changing file system.
Do we need ROM/kernel makers to specifically make their projects with F2FS support? What is the technical issue with getting /cache formatted as F2FS?
bobbarker2 said:
There seems to be a lot of confusion or pr people aren't being clear enough. At the moment there's one build found here http://forum.xda-developers.com/showpost.php?p=65193930&postcount=1302 that has F2FS as an option to change to. But I recall there being a problem with the /cache partition too small for F2FS to work, and if you look into F2FS's internal operation a bit, if /cache isn't F2FS then it's pointless.
So I'm asking, is there any TWRP build that supports formatting system/cache/data partitions as F2FS? Is there a way to fix whatever the problem is with /cache unable to be formatted to F2FS? The error I get when I try to format with F2FS is this:
Code:
mkfs.f2fs -t 0 /dev/block/mmcblk0p38 process ended with error: 255
Unable to WIpe Cache
Error changing file system.
Do we need ROM/kernel makers to specifically make their projects with F2FS support? What is the technical issue with getting /cache formatted as F2FS?
Click to expand...
Click to collapse
Old post, but F2FS requires a minimum of 100 MB to be used on a drive. Ours is 99 MB.
I converted cache and data f2fs but system not change f2fs.How can I do it ? ( Sorry my bad english )
Ottoman61 said:
I converted cache and data f2fs but system not change f2fs.How can I do it ? ( Sorry my bad english )
Click to expand...
Click to collapse
You can't. At least not without a proper OS support.
LineageOS supports F2FS only on cache and data partitions.
F2FS should only improve write speeds (debatable, I haven't done any benchmarking), and since /system is read-only it doesn't really make much sense.
IMO it's not really worth the hassle, even for /data or /cache.
Electry said:
You can't. At least not without a proper OS support.
LineageOS supports F2FS only on cache and data partitions.
F2FS should only improve write speeds (debatable, I haven't done any benchmarking), and since /system is read-only it doesn't really make much sense.
IMO it's not really worth the hassle, even for /data or /cache.
Click to expand...
Click to collapse
I understand.Thank you so much @Electry
i'm on latest open beta 7(8.1) on my oneplus 5. i just unlocked the bootloader and flashed the bluespark twrp then i tried to change the system partition file system as f2fs. it showing done but on next line it showing an error as failed to mount '/system'(no such device). i tried official twrp also and facing the same error. it changed to f2fs but after booting it was again changed to ext4(checked with diskinfo)
then i can't able to mount the system also
Please help to solve this error and to change the file system as f2fs.
i can't able to boot into system on ob7 with twrp. but can be booted with stock recovery. please help me thanks in advance.
Ragavendran 007 said:
i'm on latest open beta 7(8.1) on my oneplus 5. i just unlocked the bootloader and flashed the bluespark twrp then i tried to change the system partition file system as f2fs. it showing done but on next line it showing an error as failed to mount '/system'(no such device). i tried official twrp also and facing the same error. it changed to f2fs but after booting it was again changed to ext4(checked with diskinfo)
then i can't able to mount the system also
Please help to solve this error and to change the file system as f2fs.
i can't able to boot into system on ob7 with twrp. but can be booted with stock recovery. please help me thanks in advance.
Click to expand...
Click to collapse
You have to format data and then change system partition to ext4 and now you can flash the rom again.
Aarju said:
You have to format data and then change system partition to ext4 and now you can flash the rom again.
Click to expand...
Click to collapse
I formatted the data . Then only I tried to change the file system as f2fs. .. I want to change the filesystem as f2fs
Ragavendran 007 said:
I formatted the data . Then only I tried to change the file system as f2fs. .. I want to change the filesystem as f2fs
Click to expand...
Click to collapse
Ext4 is better than f2fs and also you have to first format again and then clean flash is required.
Aarju said:
Ext4 is better than f2fs and also you have to first format again and then clean flash is required.
Click to expand...
Click to collapse
F2fs has better writing speed. Then I may help to install the apps faster.. right?
https://medium.com/thecyberfibre/f2fs-versus-ext4-our-take-on-the-ongoing-battle-c0324f46d040
Ragavendran 007 said:
F2fs has better writing speed. Then I may help to install the apps faster.. right?
Click to expand...
Click to collapse
While faster, you may find yourself with compatibility issues in regard to your preferred ROM, etc.
Sticking with ext4 (for now) is simply the better option at the moment because it ensures that your reliability and compatibility. Also, there are apparently some issues with f2fs when it comes to device encryption.
Therefore: just wait. Maybe in the future f2fs will be the better option. As for now: I don't think that with an OP5 you need to worry about the installation time of apps taking too long.
I've unlocked my new MI9T to install xiaomi.eu rom.
First of all, after unlock, i've installed the official TWRP and i've formatted (not wiped) the DATA partition.
I've noticed that TWRP logged that it was formatting the DATA partition with mkfs.f2fs ...... really strange...
So, i've rebooted to TWRP and changed the DATA partition type to EXT4 and formatted it... after a reboot i've tried to format it again and it was formatted again in F2FS (like F2FS was the default selection).
So i've tried to switch to OrangeFox recovery (i suspected a bug in TWRP)... but the same behaviour...seems that F2FS is the default partition type for my DATA partition.
I've installed the xiaomi.eu (the kernel in this rom is the official one, and i dont think that it supports F2FS) and the rom boot ok, without problems.
I've tried also to force ext4 on DATA, but with this partition type the rom never boot (it remains on the android bootanimation).
So right now, i see a f2fs partition type on my data partition, with original kernel.
I've tried also to change the cache partition to f2fs (by default this partition is formatted in ext4) but in this way, the rom boots, but i can't see the cache partition, seems that effectively the kernel can't mount the cache partition.
so i've unpacked the official miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM_5001481fbb_10.0 rom, and i've found that in the vendor partition, under (vendor)/etc/fstab.qcom there is this entry for DATA partition:
Code:
/dev/block/bootdevice/by-name/userdata /data [B]f2fs [/B]noatime,nosuid,nodev,nodiscard,fsync_mode=nobarrier,reserve_root=32768,resgid=1065 wait,check,fileencryption=ice,wrappedkey,quota,reservedsize=128M,latemount
So, this phone uses by default a F2FS partition type for DATA????
gulp79 said:
...so i've unpacked the official miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM_5001481fbb_10.0 rom, and i've found that in the vendor partition, under (vendor)/etc/fstab.qcom there is this entry for DATA partition:
So, this phone uses by default a F2FS partition type for DATA????
Click to expand...
Click to collapse
Yes - stock QFJEUXM 11.0.4, never formatted (or wiped) Data, see screenshot from /vendor/etc/fstab.qcom