yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] INeedYourHelp:
Well I know some people do not want these "optimizations", so I think maybe create two versions, one with it and one without it.
[Galaxy S I9000 Android Development] mapas:
I don't see why we should NOT have them... they don't cost anything, or cause any problems :D
[Galaxy S I9000 Android Development] franklin01:
Should ask to RyanZa he made an app to flash kernel from update.zip so it could be possible to include an option to flash another kernel but dunno if sztuppy modification is usable with another kernel until he add the changes...

So we need laststufo's info about optimizing kernel, RyanZa for the flash, and sztuppy to add changes and include it.

But IMO, I dont think laststufo kernel is compatible with lagfix since it is already optimized...

(or we just need to re-compile sztuppy kernel using laststufo params)
[Galaxy S I9000 Android Development] kanemari:
this might have been answered somewhere else, but ill ask anyway because it seems like an obvious candidate that no one has paid attention to...

how come no one wants to use yaffs2 for the main filesystem? the init.rc has all the original mounts as yaffs2 which samsung changed to rfs, which would point to someone (probably google) thinking yaffs2 was the best option before capitalism took over. the htc desire, which in my opinion has one of the most lag free smooth UI experiences uses yaffs2 as well. its 'yet another flash file system' so its obviously optimised for flash drives.

why are we sticking with file systems that were developed for hard disks?
[Galaxy S I9000 Android Development] avary:
is this compatible with jpa ?

edit : i took the risk and applied No-RFS Extended option(with bind turned off) on jpa(with failed z4mod on top of it :D), got one note saying "INFO WRONG , could not mount sd_ext , sd_ext bakcup may not be supported on this device , skipping sd_ext backup"(something like that).

phone rebooted normal. will restore my back up from titanium now, may take long time.
[Galaxy S I9000 Android Development] maxidrom:
Gyus, who installed advanced and extreme, what is the performance after restoring all your applications? I found previously with OCLF and others on JPA, that everithing fine but when I restored all my 100+ apps booting time became 3-4 minutes, while Quadrant shows 1800-1900. I solved this only by moving most of apps to SD.
[Galaxy S I9000 Android Development] ashwinds:
Thank you!

Got a chance to try this on Doc Rambone's ROM - and i must say its very good work. CWM as the default recovery is priceless, so is the ability to backup (tested) and restore (not tested) ext4 partitions! I tried the Advanced option and must say that with regard to feel, its slick but not significantly compared to my voodoo experience. Its early days yet (< 30 min) though :)

Thanks again for the wonderful work!
[Galaxy S I9000 Android Development] Disgustipated:
Love this. Will be watching the progress closely.
[Galaxy S I9000 Android Development] Darkyy:
Great to see such a progress!

Thank you ;)

When the time comes, I could integrate this in my Steel Edition ROM, if you want.
[Galaxy S I9000 Android Development] dwillMUFC:
Any news on the backing up of efs folder bug? I think it may be when the phone automatically creates a nv_data.bak.... Etc. There is a conflict there, maybe even if there was an option to not back up the efs folder. Then that could be a short term option.

Dan
[Galaxy S I9000 Android Development] sztupy:
it's already using those compiler flags except for -O3 (it still uses -O2, that's considered safer)
[Galaxy S I9000 Android Development] sztupy:
It must be a read bug that the phone can't read something from the efs folder. The short term option is viable will add it soon.
[Galaxy S I9000 Android Development] spline1:
me is always this message: E: INFO is Wrongcould not mount sd-ext. sd-ext backup may not be supported on this device. skipping backup of sd-ext

and the process starts from the beginning.

I'm not in recovery mode
[Galaxy S I9000 Android Development] dwillMUFC:
Okay thankyou very much, i know because of alpha there probably will be bugs.

Thanks

Dan
[Galaxy S I9000 Android Development] woeds:
For an early alpha version, the entire recovery process looks extreme detailed and polished :) great job
[Galaxy S I9000 Android Development] ashwinds:
Would it be possible to port neldar's BLN fix in this kernel?
[Galaxy S I9000 Android Development] FadeFx:
sztupy, did you also work over the install routine for update.zip files in clockwork, which is not working propperly with many update.zip in stock clockworkmod?
[Galaxy S I9000 Android Development] sztupy:
If the update.zip was applied to the /cache directory beforehand, the init will use the old 2e recovery.

I'm going to add an option to CWM that will switch back to 2e if it's needed for an update.
[Galaxy S I9000 Android Development] sztupy:
filesize doesn't matter as it doesn't contain a complete dump, they simply cut out the end, where it's only a bunch of zeros anyway. The header of the filesystem is intact however and it contains the size of the fs, which is (it seems) larger than the avialable space on an 512 pit.
[Galaxy S I9000 Android Development] efegue:
sztupy are u planning a new release of ULF or something else? :)
[Galaxy S I9000 Android Development] sztupy:
Something else. ULTK related though (=ULTK will be based on it).
[Galaxy S I9000 Android Development] Reflxxx:
Great lagfix.. all ext4

Just one question, why can't it convert the stl9 (system) partition?

Sent from my GT-I9000
[Galaxy S I9000 Android Development] Telanis:
System is read-only. Writes are slow, reads are not, so there's no point.
[Galaxy S I9000 Android Development] xcreatir:
does the current version allow ext2 everywhere without any loop backs?
[Galaxy S I9000 Android Development] CommanderROR:
Sadly, even version 0.4 pre does to offer any real ext2 features. It is what I want most at the moment, but apparently there are still issues. Maybe it will be in the final 0.4 release, or it might arrive even later. I just hope it wont be too long...

I would also be interested in trying ext4 without journals, but I do not know how hard that would be to implement.
[Galaxy S I9000 Android Development] dupel:
Look at hardcores threads, he has it explained.
[Galaxy S I9000 Android Development] hardcore:
I might look into implementing ext2 or ext4 no-journal on ulfk too. For now ext4 should be a good alternative for u. I find jfs too unstable without any real benefits.
[Galaxy S I9000 Android Development] CommanderROR:
Hey hardcore,

I actually prefer jfs, but the bugs worried me a bit. Ext4i is Ok, but the journaling eats too much processor and battery time. Do you have any ETA for an initial ext2 or ext4 without journals support in your speedmod kernel? I am very happy with the k8 version, but I am considering going back to z4mod so that I can get ext2 back which seemed to work best amongst all the Filesystems I tried so far...
[Galaxy S I9000 Android Development] hardcore:
No timeframe for that yet. But we may have bigger fish to fry now... at least trying to make the current stuff really stable.
[Galaxy S I9000 Android Development] hardcore:
@sztupy: What do u think of supercurio's findings about the mount options for /system?

http://twitter.com/#!/supercurio

" as far as I know, ULF always use corrupting mount options for /system, on every lagfix configuration: http://bit.ly/bq2oXg "

It looks easy enough to add the -o check=no to it. But the question will be, can we fix any corruption that may have occurred? No fsck for rfs?
[Galaxy S I9000 Android Development] drhonk:
I'm curious about this as well.
[Galaxy S I9000 Android Development] sztupy:
1. I don't know how severe this corruption is. Except from supercurio I didn't heard any problems about this.

2. the only real corruption I've found is when an rfs partition gets mounted as vfat (and mount -t auto will always mount an rfs parition as vfat).

3. there is no fsck.rfs, as it's included in samsung's init script (it gets exdecuted on the line exec apply_disk_policy)

4. samsung mounts /system as ro,check=no and after that it WRITES to the /system partition (wtf?)

From this, and if this corruption thing is actually true, I think that there are some strange things happening in the "exec apply_disk_policy" part, and that's where the corruption (might) happen. Or it can also be, that /system never gets checked on my setting as it's not actually mounted as "ro". (If _not_ mounting a filesystem as "ro,check=no" will corrupt it, then rfs is probably more flawed than anything else in the universe), or it can be that fsck.rfs gets run, but it corrupts /system as it's not mounted ro (fscking a device while it's mounted rw is bad for health). I don't know, never encountered this problem (mainly because I stick with ULTK).

If using the mount option ro,check=no solves this issue then only one question is remaining: WHY DOES SAMSUNG'S init.rc WRITE TO /system IF IT'S MOUNTED ro? (My script remounts /system ro after init has run, and not before running init, so init.rc can do it's modifying in /system)
[Galaxy S I9000 Android Development] AnnihilatorSC:
The drawback is the mockup of USB mass storage. When one disables USB debugging manually, USB mass storage stops working. One has to switch to another USB connection type and then back again to get it to work.

I see how debugging could be very useful in Recovery, but having it auto-enabled in base mode doesn't bring any benefits - only the aforementioned drawback. Therefore, I vote killing it for base mode.
[Galaxy S I9000 Android Development] sztupy:
you can use usb debugging and mass storage side by side. The problem is if you want to use other kinds of usb connection modes, like media storage or kies.

Noted the report though
[Galaxy S I9000 Android Development] kenkiller:
Is it me or is supercurio needlessly sarcastic/rude about ULF?

Just check out his thread regarding the corruption issue. Every chance he has, he pours scorn on ULF and tries to get people to flash to his Voodoo snapshot.

Maybe sztupy should do some fixes to shut his mouth once and for all.
[Galaxy S I9000 Android Development] Bara2:
Actually I think the fuzz they're making about this bug is too much...

Of course, it is a bug and it is a good thing that supercurio developed a fix. But as anybody who is on ULTK at the moment is most likely to stay there I see no real problem for most of us.

I agree that sztupy should include a fix in his next version.

Until then I mainly wonder why this so called corruption occurs... there was another thread yesterday night in which there were several possible explanations. AFAIK nobody could actually explain the problems to full extent. So let's just wait and see. I am currently happy with my YA-OK which is also based on sztupy's great work. Would love to see a pure EXT2 solution 'tho :-)
[Galaxy S I9000 Android Development] jeebspawnshop:
I used to think supercurio was a decent guy, with his dev work being good and him being generally nice in his posts.

But a fews days ago, he flipped out and posted a reply to RyanZA's technical explanation of the RFS problems - but his reply was straight-up rude. In fact, he was just an @$$hole, saying that RyanZA was just BS'ing, and so on.

So now he starts pouring his crazy-juice on ULK, and sensationalizing the whole bug like it was Ebola for the SGS! And his suggested fix is flashing to Voodoo...?

Amazing how quickly he managed to lose all my respect. What a prick.

sztupy is nobody's fool, and I know he'll resolve this bug in his next version, and that's that.

Thanks for the hard work and kind replies, sztupy ;) I use a kernel based on ULK, so I really appreciate it.
[Galaxy S I9000 Android Development] kalpik:
Please, lets be civil.. No need to pour gas in the fire :)
[Galaxy S I9000 Android Development] supercurio:
Sorry if you read my messages like that, it's not my goal.

But i must admit I used the names "system corruption" on twitter to get noticed and because this is true.

Why ?

Because sztupy was ignoring my bug report (still is).

He also ignored all my messages for several weeks, for no reason. No idea why. Before that i was very happy we even spent hours to speak on IRC, this was very cool.

I'm a nice guy but also a bit intransigent, don't be so surprised :) that's who I am.
[Galaxy S I9000 Android Development] WiwiPouPou:
That's why you're making a good job !
[Galaxy S I9000 Android Development] spline1:
yea, please give us ext4 without Journaling.

I'm so happy with writeback and no ordered
[Galaxy S I9000 Android Development] webstar_s:
How is performance of no rfs advanced ext4 compared to voodoo?
[Galaxy S I9000 Android Development] dupel:
I lol'd =)))

10char
[Galaxy S I9000 Android Development] webstar_s:
Good thing you lol'd, i thought i've lost my sense of humour.

# Voodoo: /data is ext4, all others are kept at rfs

# No-RFS Advanced: all partitions are ext4

There obviously are some differences. Being the new linux/android user, i don't know if there could be any performance gain if all partitions are ext4, hence why i asked the question.
[Galaxy S I9000 Android Development] dupel:
Voodoo - all partition except efs are ext4. So yeah, I still lol =)
[Galaxy S I9000 Android Development] webstar_s:
Do you have a problem reading what's written or is there something i'm missing? It clearly say that only DATA IS EXT4, and all others are KEPT AT RFS.

# Voodoo: /data is ext4, all others are kept at rfs

# No-RFS Advanced: all partitions are ext4
[Galaxy S I9000 Android Development] supercurio:
Hi.

This changed now for Voodoo, which converts /dbdata /data /cache and /system to Ext4.

Maybe time to remove the Voodoo name from Universal Lagfix.

No-RFS advanced in ULF is /dbdata /data /cache in Ext4, /system in RFS.
[Galaxy S I9000 Android Development] webstar_s:
Well, you see, i was asking specifically for this kernel, that quote i used is just showing that. Otherwise i wouldn't ask in this thread. The reason i asked here is because i'm currently using this kernel, and voodoo lagfix which was already in it, and since it was already called that i didn't feel a need to call it by another name. So, obviously this was all a misunderstaning, and thanks for clearing that up.

I'll just ask again, is no-rfs advanced ext4 actually offering better performance then the "voodoo lagfix" which only converts data to ext4? That was supposed to be the original question, so that no one would confuse "voodoo lagfix" in this kernel to original voodoo lagfix by supercurio.
[Galaxy S I9000 Android Development] st4rk:
Try it and see.. :D:p:rolleyes:
[Galaxy S I9000 Android Development] Reflxxx:
Hi,

I noticed that hardcore used version 0.4 ULF but I dont see it posted over here..

What are the changes?

Thanks
[Galaxy S I9000 Android Development] [Ramad]:
Don't worry, some members just using time jumping from thread to thread telling others that they are wrong and dumb :)

You know that a post that just include "lol" do count as a post...go figure how some members can have 800+ posts :D

Should 'EXT' in EXT2 be removed because EXT4 includes that ?
[Galaxy S I9000 Android Development] Reflxxx:
Can you please put in the option to convert stl9 (system) to EXT4.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] dupel:
I assume your talking about me. Firstly its not very polite. Secondly when a person cant even distinguish if he is talking about voodoo from curio, voodoo from this kernel and just do a research (curio released new version of voodoo, what, week and a half ago?) than what do I do?
[Galaxy S I9000 Android Development] [Ramad]:
You mean this is being polite:
[Galaxy S I9000 Android Development] dupel:
Not very polite, but what do you answer to question "is ext4 faster than ext4?"
[Galaxy S I9000 Android Development] SamHaLeKe:
Indeed gentlemen, what a day, what a day. Time to get some rest...

Mark: SAMSUNG

Name: Galaxy S

Model: GT-i9000

Product code: i9000HKAXEN

Firmware: Google android 2.2 (Froyo)

PDA: i9000XWJPA

Phone: i9000XXJPP

CSC: i9000XENJP2

Custom ROM: DocRambone Froyo XWJPA v7.6.2 + medium package

Theme: AOSP Lockscreen + Extended PowerMenu + CircleBatteryMod C

Kernel: Hardcore SpeedMod K9 HZ=300

Sent directly from the above using XDA App
[Galaxy S I9000 Android Development] webstar_s:
First of all, my question wasn't formulated like that. Now, i don't remember being rude in any of my posts, so there was no need for arrogant, primitive behaviour. Since i was using this kernel i asked only about lagfix schemes this kernel offers, if i wanted to talk about real voodoo lagfix, i would ask a question in a thread about it. Even after i quoted what is written in the first post of this thread, you were still "loling" and still thinking i was asking about the supercurio's voodoo lagfix. I know there's only one voodoo lagfix, but this lagfix scheme i was talking about was called after earlier releases of voodoo, and it looks like it kept its name so far. No point in continuing about this anymore.

@Ramad: It definitely seems that way, but you can't blame them. Narrow-minded people unlimitedly believe in their conclusions, no matter what you tell them.
[Galaxy S I9000 Android Development] [Ramad]:
I'm not going to make this long, but I recall you bashing members for not reading previous posts, well, I guess that this is your turn this time.

webstar_s was asking about the very first post in this thread, I mean post 1 by sztupy:

So please...If you like to help other members then try to remember your first days here at XDA.

As the old Danish saying: There is no stupid question, only the answer can be stupid.
[Galaxy S I9000 Android Development] neldar:
I have fixed the bug in my sub-build of ULF, /system is now mount with check=no.

But:

ATTENTION: If you are upgrading from an unfixed ULF 0.3 read this:

[REF] Details about /system RFS corruption and HOWTO correct it (fix included)

And you might want to apply the repair-kernel from that thread, before you go to this post: BacklightNotification v2.2 with Universal-lagfix v0.3 FIXED

and upgrade to the fixed BLN release.
[Galaxy S I9000 Android Development] sztupy:
Thank you for this update!
[Galaxy S I9000 Android Development] russell.nash:
How about including /system conversion to ext4/jfs ?

Since we all saw that rfs has a lot more fundamental flaws than ever thought, how about completely kicking it and adding /system to the list of partitions being able to convert to ext or jfs during lagfix?
[Galaxy S I9000 Android Development] dupel:
There are lagfixes that doit (voodoo and jfs). However, rfs (in noatime - in tweaks in sppedmode kernel, or you cah do it yourself) is pretty fast on read. So it doesnt show any improvement.
[Galaxy S I9000 Android Development] russell.nash:
I am not talking about speed improvement, I am talking about code improvement. Not using proven-to-be-broken code should be fundamentally obvious to anyone related with programming devices. I would suggest the very same even if rfs was a lot faster than ext.

If you know your car is broken in some manner, wouldn't you repair it even if it still drives as fast as before?

From another point of view: you cannot argue for something based on a single attribute which is only of equal quality than the one of a possible replacement if the replacement is proven-good whereas the current solution is proven-bad.
[Galaxy S I9000 Android Development] sztupy:
and the goodbye rfs rom with ultk also does away with rfs. (uses ext2 on /system).
[Galaxy S I9000 Android Development] dupel:
Well, good point.

Heh, forgot about that =)
[Galaxy S I9000 Android Development] russell.nash:
Your idea doing a "Universal lagfix" was to incorporate all lagfix ideas in one patch, not? That's why one might think that system-to-ext can find a place in your patchset...

Let me quote the OP from your goodbye rfs:

"This is only a showcase on how a ROM (mostly) without RFS(*) would work.

(*): this is only marketing bull****. The /efs partition still uses rfs in this rom.

"

Basically, I am not looking for a showcase. Why not complete the issue once and for all (even for /efs)? If ULK contains everything-to-ext it will not take long before a patch combining ULK and BLN will be done, which is pretty much what a phone in productive use needs...
[Galaxy S I9000 Android Development] russell.nash:
There is yet another problem with the speed-comparison. We found that during comparing reiserfs and ext3 performance. reiserfs was pretty much equal r/w performance, sometimes even faster. But it turned out that ext3 uses a lot less cpu power. In fact when we switched some boxes from reiserfs to ext3 the cpu usage dropped to 1/10. So if you compare some fs against ext you should watch cpu usage, too. Being on a mobile device that might make some sense as the ext caching strategies are a lot better than fat-derivatives'.
[Galaxy S I9000 Android Development] russell.nash:
Let me show you why you have some need for cleanup in this matter:

Someone from goodbye-thread:

"Thanks!!!!! but i have 2.5.1.5 version and i don't see ulf option, I'll search for another one. Also this Rom doesn't have Universal lagfixed Kernel"

Now you:

"This rom is pre-lagfixed, so you can't actually de-lagfix it easily. You can flash ULTK on top of this ROM, and use ULTK's lagfix options, to disable the lagfix."

My thought: ok, and how does he de-lagfix /system if ULTK cannot handle /system?

And then - as expected:

"I am stuck in recovery mode! each time I reboot.. recovery.

When I disable Lagfix:

Clockword Recovery V2,5,1,0 lagfix edition

E: could not open lagfig.conf

When I restore a nandroid: FAIL:

can't mount /system/!

My phone just died!

"

Well, he really could not de-lagfix /system, I was right...
[Galaxy S I9000 Android Development] Verplrke:
Indeed it is, will have to switch to another lagfix then...
[Galaxy S I9000 Android Development] sztupy:
converting /efs will never be done by me (and i don't think anyone else would do that), that's for sure. /efs is a crucial part of the phone, which can not be reset by re-flashing the rom. nikademus's lagfix solves this by creating a backup of that folder and never mounting it again, but keeping that as RFS. I like this idea, so I might implement this particular solution in a next release.

As for the /system issue, converting /system is more harder than converting the other three as the backup/restore process might need files from /system to work. This can be solved too, but it was not in ultk 0.3 or 0.4.git (which basically means every other kernel based on ultk too), and I still need to figure out how it can be done optimally.
[Galaxy S I9000 Android Development] Kel Ghu:
To all JFS users, just use RFS or Ext4 for /dbdata. You will not hear of the JFS bug. :P
[Galaxy S I9000 Android Development] Kel Ghu:
sztupy,

Why can't one use simultaneously on different FS?

I'd love to have:

data = jfs + ext2

cache = jfs + ext2

dbdata = rfs + ext2

but the kernel reports lots of errors when doing that.
[Galaxy S I9000 Android Development] Schrotty35:
Whene comes 0.4?
[Galaxy S I9000 Android Development] russell.nash:
Thanks for keeping it in mind. It would be great if you solved that somehow.
[Galaxy S I9000 Android Development] Und3rtaker:
sorry in advance for noob question:

what does "overkill" stands for? does it somehow shortens hardware's life in long term??
[Galaxy S I9000 Android Development] mengsuan:
Apparently the timezone bug is still there. I have just tried.