With the 2.2 OTA coming should we expect it to use RFS or EXT4? My gut feeling is that it would be RFS, but I honestly don't know Sh!t.
RFS
The phone came with RFS and Samsung does not support ext4 on the epic. Leaked builds have been RFS only until devs here modded them to support ext4.
/thread
More likely RFS
Someone please correct me if I am wrong but 2.2 is still rfs I think ext4 doent come till gingerbread.
Sent from my SPH-D700 using XDA App
Yes Gingerbread uses EXT4.
2.2 is still RFS.
RFS until the devs cook up the good stuff for us
Sent from my SPH-D700 using XDA App
Actually the gb13 source comes with files for ext2, 3, and 4 support... so all are possible. But as said, it will come rfs, and need to be modded for those.
I never want to go back to Rfs after usi g ext4. So much faster.
To the devs, does Gingerbread support RFS? If it's only EXT4 I see problems in updating...
It will be RFs..and prob Gingerbread will be RFS..cause RFS is a file system made by samsung..and thats what they use..
As for support..I'm not 100% sure but neither 2.1 nor 2.2 support RFS either..samsung just made it so...
but doesnt samsung run yaffs on the nexus s?
EB13 kernel source compiles rfs support and NOT EXT4 support...but we should be able to compile ext4 support in...but no by default it is not ext4 so you can count on OTA being RFS
adamw1101 said:
but doesnt samsung run yaffs on the nexus s?
Click to expand...
Click to collapse
Nope, ext4.
adamw1101 said:
but doesnt samsung run yaffs on the nexus s?
Click to expand...
Click to collapse
Ok 2 things..
1) Google made the request on the Nexus S, and my guess is Google made the call on the partitions...
2) Samsung's OneNAND by Default comes with RFS, in the Nexus S they use Sandisk's NAND...
Haven't people mostly had issues with EXT4 to the point where the difference between the 2 were minuscule or nothing? Maybe I'm off b/c 2.2/3 is different but it seems to me that a lot of people switched to EXT4 in the dev section only to switch back to RFS due to bugginess and no improvement over RFS...
pipskicks said:
Haven't people mostly had issues with EXT4 to the point where the difference between the 2 were minuscule or nothing? Maybe I'm off b/c 2.2/3 is different but it seems to me that a lot of people switched to EXT4 in the dev section only to switch back to RFS due to bugginess and no improvement over RFS...
Click to expand...
Click to collapse
I'm on ext4 right now but I can't say I really noticed much of a speed difference when I switched. Well probably go back to stock RFS when the update is out.
Related
Guys many people are fond of Supercurios voodoo and Hardcores Kernels...lets discuss and make it easy for people to choose from the best....
one man's poison is another man's medicine..
wellll i have tested the latest hardcore's k10i wid ext4all lagfix and its very good...no lag...and i m very fond of supercurios voodoo too..i had tested his test version and it ws fast too but i think it just lacked in the battery usage..i think so...bt i have not tested his latest stable version yet....lets c wat others have to say...
So me, Voodoo Final is much better than the RC. Not sure about K10i. I heard its good too.
Both are excellent Kernels. What I m personnaly doing is putting the voodoo first so that all partitions including /System get converted to Ext4 then put Hardcorer's K10i over it. this way I get the best out of both (hardcore doesn't convert /system and you have to ignore the conversion request when you first start your phone following Hardcore's kernel flash)
bouzoubaa said:
Both are excellent Kernels. What I m personnaly doing is putting the voodoo first so that all partitions including /System get converted to Ext4 then put Hardcorer's K10i over it. this way I get the best out of both (hardcore doesn't convert /system and you have to ignore the conversion request when you first start your phone following Hardcore's kernel flash)
Click to expand...
Click to collapse
Wow I'm not sure about that but why not...
This does not belong here! And please, this is like comparing apples to oranges. Each one has its strong points.
Sent from my GT-I9000 using Tapatalk
g00ndu said:
This does not belong here! And please, this is like comparing apples to oranges. Each one has its strong points.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Exactly.
Please move this thread to the Q and A section.
bouzoubaa said:
Both are excellent Kernels. What I m personnaly doing is putting the voodoo first so that all partitions including /System get converted to Ext4 then put Hardcorer's K10i over it. this way I get the best out of both (hardcore doesn't convert /system and you have to ignore the conversion request when you first start your phone following Hardcore's kernel flash)
Click to expand...
Click to collapse
Is it better now with the K10i over the stable voodoo conversion? Because i thought i'll be brave and try that too although it's very smooth even with the voodookernel..
Sent from my GT-I9000 using Tapatalk
bouzoubaa said:
Both are excellent Kernels. What I m personnaly doing is putting the voodoo first so that all partitions including /System get converted to Ext4 then put Hardcorer's K10i over it. this way I get the best out of both (hardcore doesn't convert /system and you have to ignore the conversion request when you first start your phone following Hardcore's kernel flash)
Click to expand...
Click to collapse
Hardcore does not convert /system? Anyone knows why?
g00ndu said:
This does not belong here! And please, this is like comparing apples to oranges. Each one has its strong points.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
as i said in d post...i like both the kernels... bt its just to help people to select their kernel in a better way...no objection to any of d developer...
If you got the ULK ext4 with ext2 mounts and unbounded you will get high scores in quadrant..
but currently i would say voodoo kernel is better and more safe.. /sytem is converted to ext4
IMO, I agree in saying, this topic is not something that should belong here
I've read somewhere , using idle for 9 hours , 0 % battery drain with new K10i 256Hz, if it's real, it's ****ing awesome... i got 5% battery drain on 7 hours on Wifi ON just try today on my C.M. 6.1 and i'm happy the same
ale0crysis said:
I've read somewhere , using idle for 9 hours , 0 % battery drain with new K10i 256Hz, if it's real, it's ****ing awesome
Click to expand...
Click to collapse
Sounds really nice!
But didn't know that Hardcore doesn't convert /system. I think i will also try flashing voodoo first and then hardcore over voodoo...
OT: @ale0crysis: from your signature: "32 GigaByte Class 10 Sandisk"? Never heard of a 32GB Class microSD. Do you have the exact model?
I was on JPU with Voodoo but had problems with Skype calls. Voice was not clear lagging and can't hear each other even with WIFI.
On the other hand I was using JPO with Speedmod kernel, Skype was awesome, working increadibly..
But I am not sure whether it was kernel or ROM release affecting..
hello fellas
this was as pm for supercurio mentioned i cant send him one and cant answer/make a topic in the dev sektion so i decided to make a new topic in the general sektion if someone could give him the info ive got if he didnt knowed that, that would be nice
so the info ive got for you is:
a friend of mine got the nexus s (i9023) and i compared my sgs and the nexus s with the android system info tool cause i would like to know why its that bit better
1st thing i saw was that the 2 phones have exactly the same processor and gpu the only thing is that the nexus s got a few more sensors
so why its faster
at this point i looked at the mountpoints and what amazing surprise the whole nexus s runs on ext4 even the system, data, dbdata etc.
so my thoughts are that it could be worth to have a look at the nexus s sources cause of the same hardware of the phones i think that the missing features can be found there
im not a coder but im a linux enthosiast and more hardware interrested but i thought this could be usefull for making ext4 work on the sgs
so with the best regards
yours
sputnicyes
Sent from my GT-I9000 using Tapatalk
Ext 4 Does work on the SGS, its called a lagfix, and anybody running a custom ROM / Kernel is probably using Ext 4.
unless i have misunderstood your post ???
sputnicyes said:
hello fellas
this was as pm for supercurio mentioned i cant send him one and cant answer/make a topic in the dev sektion so i decided to make a new topic in the general sektion if someone could give him the info ive got if he didnt knowed that, that would be nice
so the info ive got for you is:
a friend of mine got the nexus s (i9023) and i compared my sgs and the nexus s with the android system info tool cause i would like to know why its that bit better
1st thing i saw was that the 2 phones have exactly the same processor and gpu the only thing is that the nexus s got a few more sensors
so why its faster
at this point i looked at the mountpoints and what amazing surprise the whole nexus s runs on ext4 even the system, data, dbdata etc.
so my thoughts are that it could be worth to have a look at the nexus s sources cause of the same hardware of the phones i think that the missing features can be found there
im not a coder but im a linux enthosiast and more hardware interrested but i thought this could be usefull for making ext4 work on the sgs
so with the best regards
yours
sputnicyes
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I do not mean to be rude but you are approximately one year late with this idea of yours.
As far as I can tell the OP may have had one of three goals in mind when they put this post up:
1) The OP is saying that Ext4 would be a viable option for the file system on the SGS: Yes, this was discovered and almost universally implemented on custom ROMs and kernels here. In fact, searching for the term Ext4 in the i9000 forums brings up more than 250 threads where Ext4 is a keyword. The OP may even find some of them instructive.
2) The OP is saying that devs may be able to learn a new way to implement Ext4 on the i9000 by studying the file structure of the Nexus S: I would doubt that. The file system is the file system no matter the hardware it is mounted on, besides which everyone has already made very clear that as far as Android implementation the Nexus S and the SGS line are pretty much identical.
3) The OP was trying to illustrate WHY Supercurio doesn't accept random PMs: Mission accomplished.
lol i knowed that my sgs runs on that lagfix
but there are missing features in 2.3.3 and it seems that the the nexus s (also running 2.3.3 and the same processor) has that missing features implemented in the kernel
or im wrong what supercurio writes in his post about the ext4 lagfix on 2.3.3 for the sgs
Sent from my GT-I9000 using Tapatalk
Try any Custom Kernel, Speedmod, Voodoo Stable, DamianGTO, Dark Core & many more. All have the option to convert all partitions to ext4.
Or you can try Darky, Docs, Juwe's or any other Custom Rom, The Kernels included with all custom roms usually support conversion to ext 4.
And yes ext4 on SGS make it Super fast. I use it personally & really like the fast response of ext4 compared to RFS.
Just try it. If you are on stock Rom I would suggest to try a custom kernel from Development Section of this forum to see how it feels. Search for any of the kernels i mentioned & follow the installation instructions there.
so let me get clear
supercurio writes here:
[KERNEL] Hacked Lagfix/Ext4 Samsung Galaxy S Gingerbread - JVB
that there are missing features in the kernel of 2.3.3 jvb
my thoughts are that these missing features can be found in the nexus s kernel sources cause it runs also an 2.3.3 release of android
Galaxy S is not as fast as NS because of bad samsung coding and bad framework implementation. Try CM7 on SGS and see it is as fast.
I now use with samsung s gingerbread - jfs filesystem and I can see it s faster than ext4 but still not cm7 fast (which has ext4).
Sent from my GT-I9000 using XDA Premium App
Hello gents/ladies, I recently decided to change things up a bit, and flashed from CM 7.0.3 to Darkside Sense v3.0.0. As part of installing the new ROM, the file system was changed from Ext3 to Ext4. I have decided to go back to CM7, this Sense 3.5 Rom is just to buggy and laggy for me.
My question is, not knowing a whole lot about the difference in the two file systems, do I need to convert back to an Ext3 filesystem to run CM7, and if so, how do I safely go about doing this? I have searched around the forums, but have not found a definitive guide on how to do this, if it is necessary.
Thanks in advance for helping a n00b out
xRogerxC said:
Hello gents/ladies, I recently decided to change things up a bit, and flashed from CM 7.0.3 to Darkside Sense v3.0.0. As part of installing the new ROM, the file system was changed from Ext3 to Ext4. I have decided to go back to CM7, this Sense 3.5 Rom is just to buggy and laggy for me.
My question is, not knowing a whole lot about the difference in the two file systems, do I need to convert back to an Ext3 filesystem to run CM7, and if so, how do I safely go about doing this? I have searched around the forums, but have not found a definitive guide on how to do this, if it is necessary.
Thanks in advance for helping a n00b out
Click to expand...
Click to collapse
i'm pretty sure CM7 has an ext4 filesystem...
saranhai said:
i'm pretty sure CM7 has an ext4 filesystem...
Click to expand...
Click to collapse
That's definitely what I'm trying to figure out, still searching.
Note: More searching reveals that Gingerbread ROM's use an Ext4 filesystem? If this is the case, then originally installing CM7 on my phone would have already been an Ext4 filesystem?? If so, I don't know why I was thinking it was converted by installing the Sense 3.5 ROM.
OK so I am running the newest version of cyanogenmod 7 on my samsung vibrant witch is based on android 2.3.7 and I want a voodoo lagfix kernel compatible with cyanogenmod 7 does any one know if someone is working on this or it there is one alredy out that i could use.
Moped_Ryder has a bunch of Gingerbread kernels here. There is also a chart that shows if it supports Voodoo and if you need to remap the keys or not.
I think you need to understand what voodoo lagfix is. Search and read.
Sent from samsung Vibrant
You DO NOT voodoo lagfix on CM7. It won't work anyway. Also, there are no voodoo lagfix kernels for CM7, only voodoo color/voodoo sound.
Sent from my Sensation using Tapatalk 2
geoffcorey said:
You DO NOT voodoo lagfix on CM7. It won't work anyway. Also, there are no voodoo lagfix kernels for CM7, only voodoo color/voodoo sound.
Click to expand...
Click to collapse
This. The whole point in voodoo is to replace the RFS file system that Samsung used with Ext4. Because Cyanogenmod doesn't use RFS the Voodoo lagfix won't do anything like geoffcorey said.
My .02
Samsung Froyo and Gingerbread ROMs use a file system called RFS. basically it sucks. Voodoo lagfix (note not sound/color) is a procedure that changes the stock Samsung RFS file system to ext4. Note is does NOT change the partition setup of the ROM, just the file system.
That is why you can jump from Froyo to Ginger and back (if all kernels support Voodoo) without Odin.
CM7 / ICS and others use a file system called YAFFS - not RFS or ext4. YAFFS requires a totally different partition setup. This is why once you go to CM7/9 or ICE you cant go back to Froyo or GB without Odin with repartition checked.
Some of us are old school and remember OCLF...but that is another story.
Ayo folks , i tried to tweak a bit some kernel options and discovered that our device LOVES low readaheads .
So i pushed the internal memory readahead to 96kb (under this there is no improvement) with kernel toolbox and there : magic , the device gets snappier , benchs get significant improvement but overall performance explodes: latency got from 70ms (stock no modification) to 29MS!!
You can try yourself :
Scheduler : ROW
Internal card readahead : 96 or 64kb
Entropy read: 128
Entropy write : 1024
antutu always goes over 80k for me, so nothing new here, and as far as IO speeds go, yours are rather slow with that setup.
BFQ w default 1024kB
entropy @ 1024/2048
so no real gains imo. seems slower tbh
its just benchs in the end. generally miui is less snappy and will always be, once cm gets properly fixed up ull see some real gains
sikica133 said:
antutu always goes over 80k for me, so nothing new here, and as far as IO speeds go, yours are rather slow with that setup.
BFQ w default 1024kB
entropy @ 1024/2048
so no real gains imo. seems slower tbh
its just benchs in the end. generally miui is less snappy and will always be, once cm gets properly fixed up ull see some real gains
Click to expand...
Click to collapse
Oh wow didn't realize that cm was that slower than miui but still it looked like stock cm values were a bottleneck
i believe shantosh didnt really tinker with kernel settings much, prolly been too busy with fixing every little thing, so some tweaks might actually give a decent boost on cm. in the end, pure cm kernels are usually too restrictive. custom built one is what we need
sikica133 said:
antutu always goes over 80k for me, so nothing new here, and as far as IO speeds go, yours are rather slow with that setup.
BFQ w default 1024kB
entropy @ 1024/2048
so no real gains imo. seems slower tbh
its just benchs in the end. generally miui is less snappy and will always be, once cm gets properly fixed up ull see some real gains
Click to expand...
Click to collapse
Mine was different:
FIOPS @ 1536
Entropy @ 512/1024
Sent from my Redmi Note 3 using XDA Labs
aaz03 said:
Ayo folks , i tried to tweak a bit some kernel options and discovered that our device LOVES low readaheads .
So i pushed the internal memory readahead to 96kb (under this there is no improvement) with kernel toolbox and there : magic , the device gets snappier , benchs get significant improvement but overall performance explodes: latency got from 70ms (stock no modification) to 29MS!!
You can try yourself :
Scheduler : ROW
Internal card readahead : 96 or 64kb
Entropy read: 128
Entropy write : 1024
Click to expand...
Click to collapse
Can you give us link to app that is able to do so?
New cm has f2fs support. Not sure if this is applicable or not?
simplyme2908 said:
New cm has f2fs support. Not sure if this is applicable or not?
Click to expand...
Click to collapse
I've flashed latest build (by TheStrix) and converted /cache & /data to F2FS.
The bad thing is there are no TWRP with F2FS support available for our device. Those TWRP only can convert to F2FS, but cannot mount it afterwards. When I need to flash something I should adb sideload the package, it's not convenient but; I really prefer F2FS than EXT4 because I can feel it runs faster when copying something from device to PC via MTP and vice-versa, on EXT4 it was slow.
MOVZX said:
I've flashed latest build (by TheStrix) and converted /cache & /data to F2FS.
The bad thing is there are no TWRP with F2FS support available for our device. Those TWRP only can convert to F2FS, but cannot mount it afterwards. When I need to flash something I should adb sideload the package, it's not convenient but; I really prefer F2FS than EXT4 because I can feel it runs faster when copying something from device to PC via MTP and vice-versa, on EXT4 it was slow.
Click to expand...
Click to collapse
Thestrix is making a new twrp now.
simplyme2908 said:
Thestrix is making a new twrp now.
Click to expand...
Click to collapse
@vibhu0009 is the maintainer I guess as stated on: https://twrp.me/devices/xiaomiredminote3.html
But Unofficial one will do...
Relax, new update will be coming soon with F2FS support
MOVZX said:
@vibhu0009 is the maintainer I guess as stated on: https://twrp.me/devices/xiaomiredminote3.html
But Unofficial one will do...
Click to expand...
Click to collapse
In case you need a f2fs twrp. Change /data and /cache to f2fs
Note: this will wipe your ad card.
https://www.androidfilehost.com/?fid=24591000424943818
simplyme2908 said:
In case you need a f2fs twrp. Change /data and /cache to f2fs
Note: this will wipe your ad card.
https://www.androidfilehost.com/?fid=24591000424943818
Click to expand...
Click to collapse
I've been using F2FS since the 1st Strix build with F2FS support. The problem is no TWRP with F2FS support currently. But fortunately today I browse TheStrix AFH folder and found unofficial TWRP made by him which support F2FS.
MOVZX said:
I've been using F2FS since the 1st Strix build with F2FS support. The problem is no TWRP with F2FS support currently. But fortunately today I browse TheStrix AFH folder and found unofficial TWRP made by him which support F2FS.
Click to expand...
Click to collapse
That is the link is sent you now
simplyme2908 said:
That is the link is sent you now
Click to expand...
Click to collapse
I modify the kernel ramdisk (of CM13 TheStrix Build) so that /cache & /data are mounted with nobarrier option. And I'm happy with it, fast & stable. Easy to notice the difference from using EXT4, MTP transfer with F2FS runs slightly faster.