Ext4 on galaxy tab?
- Thread starter mikenicee
- Start date
From what I read koushes clockworkmod recovery converts your system to ext4. But I think its for vzw. I tried with my tmo tab and I could of sworn I stood at rfs. Not sure. But would love to see a voodoo kernal
Sent from my GT-P1000 using Tapatalk
Sent from my GT-P1000 using Tapatalk
read this if you want to learn about ext4.
http://en.wikipedia.org/wiki/Ext4
are you sure you hacked it or you used a voodoo kernal?
http://en.wikipedia.org/wiki/Ext4
are you sure you hacked it or you used a voodoo kernal?
Last edited:
Oh, I agree, but it's difficult to put show qualitative benefits of ext4 vs. rfs.
Well why did samsung ditch rfs to ext4 for the nexus s?
Sent from my GT-P1000 using Tapatalk
Because it was not Samsung who was coding for the Nexus S! Nexus S has nothing to do with Samsung it is all done by Google! Only the hardware and its warrenty is related to Samsung. All firmwares/ROMs and Kernals will be released by Google and google only! This is why it is call a true google phone!
Ext4 file system make read/write operations at least twice faster compare to RFS. It allows for file size exceeding 2GB as well. Besides it has journaling capabilty.
All this greatly reduces lags and glitches especially for video and when switching tasks that involves read/write operations.
My experience with ext4 on Vibrant is very positive.
RFS is fat16 or fat32 with a journal.
It is also proprietary to Samsung and no source code for it is released, so it is not very good for AOSP release. And in everyone's experience it performs like ****.
The RFS stack (probably storage.ko) also contains sector remapping/wear levelling module that implements stl on top of bml. So while it is easy to switch to extX on top of stl its gonna be much harder to implement it on top of raw mtd flash for .35 kernel on tab. The flash chip in Nexus S most likely has wear levelling built in. But on Tab it is done on software.
It is also proprietary to Samsung and no source code for it is released, so it is not very good for AOSP release. And in everyone's experience it performs like ****.
The RFS stack (probably storage.ko) also contains sector remapping/wear levelling module that implements stl on top of bml. So while it is easy to switch to extX on top of stl its gonna be much harder to implement it on top of raw mtd flash for .35 kernel on tab. The flash chip in Nexus S most likely has wear levelling built in. But on Tab it is done on software.
That is not always true. The problem is that quadrant can be "tricked" into a higher score (EXT2, EXT3). However, ext4 is a true "lag fix" and thus the performance gain is real. There is a "real world" gain after converting to EXT4. The problem as I understand it with the Tabs right now is that we don't know if it is actually working. Give it time and we will see the same progress as we see in the Galaxy S phone.....
Similar threads
