yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] henriquesb:
OCLF on top of JFS works very well so far! :)

Currently getting amazing performance using an ext2 loop with binds (a la OCLF 2.2) on top of JFS, for /data only.

By amazing I mean scrolling almost 100% fluid while doing a full Touchdown sync over wireless, or MP3 player changing tracks in the background and almost no interruption while racing on Asphalt 5!

ext2 loop on top of ext4 was much worse, and normal ext4 partition was not as fast with Touchdown (and other applications that store in database, like JuicePlotter, more info on RyanZA's thread on fsync ).

On Quadrant I got 994 on ext4/ext2 and 997 with jfs/ext2. The numbers don't express at all how fast the phone feels now ;)

Tested removing the battery and did not change the language back or timezone as usually commented about JFS, because all happens in the ext2 loop.
[Galaxy S I9000 Android Development] kamirza:
Lagfix procedure

Please advise. In kernel 10 with JPO v9.

Can we apply lag fix anytime or only after installing new ROM? If yes then when it gives optios; which one should we pick; like backup or backup and restore etc?

Thanks
[Galaxy S I9000 Android Development] Goldie:
Anytime, backup and restore.
[Galaxy S I9000 Android Development] sztupy:
You can aply lagfix any time. Backup and restore will restore your data after lagfix, so you won't lose your data. Any other choice will result in losing all your data (but you will have a backup from them if choosing the "only backup" option).
[Galaxy S I9000 Android Development] mathieumeuh:
Supercurio did convert /system in voodoo 5. Do you plan to work with him? I think you two are at the origin of big improvements on Sgs!

Sent from Galaxy S i9000
[Galaxy S I9000 Android Development] sztupy:
We're on separate paths, and are thinkig very differently about things. This doesn't mean features from voodoo won't appear in ultk or in some ultk variant. (I don't think supercurio would add ultk features to voodoo anytime however).
[Galaxy S I9000 Android Development] kamirza:
Hi Sztupy

I applied the lag fix e4 noj for Doc rom JPO v9. Things seemed ok except gallary which showed quadrupilation of all photos. This was disturbing. I had chosen backup and restore so I went back and it showed 'system could not be backed up'. Now I have disabled lagfix and installed the rom and all anew. I want to have lagfix but anything I should do before to not spoil the gallary? This happened once when I went from v7.0.1 to 7.0.2 as well. please advise. Thanks.
[Galaxy S I9000 Android Development] Qazz~:
Ive noticed that the backup ulf makes when choosing lagfix options isn't automatically deleted. Thats normal right?

And why is it still based on JPM kernel, aren't there a lot of newer, possibly better kernels to base on?

Just a question...
[Galaxy S I9000 Android Development] zurchpet:
JPM kernel source was released by Samsung. The other ones not.
[Galaxy S I9000 Android Development] eitama:
ULF is great,

But I find it disturbing that you are using Voodoo/OCLF terms when they are infact NOT the work of supercurio and Razya. I'd suggest you change it.

Cheers!
[Galaxy S I9000 Android Development] jeebspawnshop:
Who the hell are you, the Word Police?

And since you're being narc, it's RyanZA, not Razya.

Go home.
[Galaxy S I9000 Android Development] supercurio:
In fact I've asked sztupy to remove the Voodoo name from his software since about a week.

And I'm re-iterating my request now.
[Galaxy S I9000 Android Development] eitama:
LOL, jeebspawnshop, take your stupid name, shove it, and shut your hole.

I wasn't talking to you, next time you express yourself, do it politely, same as I did.
[Galaxy S I9000 Android Development] brujoand:
Aye

Aye, happy troopers. No need to be shouting. :)

You were a litle harsh when you expressed your self eitama. But I think we all agree with you that aspecially now that voodoo is so much more then one ext4 partition it will be only confusing for ULF to use this naming convention. And I think we also agree that the SGS-scene is pretty confusing for a newcomer anyways, ;)

That said, Im also a big fan of the work thats going on here, keep it up! :D
[Galaxy S I9000 Android Development] jeebspawnshop:
Ooh, there's no need to stop being a lady!

Relax.

Now calmly go tell the rest of your Word Police friends about how you've been mistreated.

There, all better.
[Galaxy S I9000 Android Development] eitama:
Your contempt towards other people's work is where the "mistreating"'s at.

And don't worry, i'm relaxed, always have been.
[Galaxy S I9000 Android Development] dakine:
Been using JFS Advanced for a couple weeks now and it's been really good. I'm a little lost on if I should worry about this /system corruption reported in several threads.
[Galaxy S I9000 Android Development] EarlZ:
I've encountered a "MD5 Mistach" error on one of my current back ups, any known cause behind this ?
[Galaxy S I9000 Android Development] saphirrot:
i want to tell ya about a bug i think i´ve found :

since i was using your lagfix my phone is speeding away. but, when i shutdown my phone and go to sleep while it charging, the display is showing that the phone is charging but the display sometimes turn on and suddenly goes off.... and that procedure repeats every night every 3 minutes.... after the night i noticed that it starts itself in the Recovery Menu and it wants to take a new config ! i havent choose a new config .....

**** my ****ty english, iam sorry for it....
[Galaxy S I9000 Android Development] dupel:
ALways wondered why people swith off their phone? It is designed to be on always, as a phone and as smartphone.
[Galaxy S I9000 Android Development] gicgi:
you are kidding, dont you?

@saphirrot,

you can switch to airplane mode at night by long pressing power button and choosing the airplane mode at night. in the morning do the same thing, disable the airplane mode. no need to shot down the phone at all.

and yeah, its probably a bug.
[Galaxy S I9000 Android Development] saphirrot:
Man cmon, best bull**** i´ve heard :D I think you dont got the right phone, go get one without an Power Button ;D

@gicgi : Thank you, good idea.

I just to have this little bug fixed, nothing else. GREAT LAGFIX BTW !!!
[Galaxy S I9000 Android Development] sztupy:
You ask to change something inside something that was already released. I'm ultimately sorry I can't turn back time. Btw. Twitter is not an appropriate place to ask other people to do something.
[Galaxy S I9000 Android Development] supercurio:
I see that you're aware that i asked you on twitter.

It means you simply chose to ignored my request.

Now that you're once more aware of my request, please remove the Voodoo name from the version you distribute actually from your github:

https://github.com/sztupy/universal_lagfix_kernel_initramfs

This distribution don't concern previous release but current and future. I see no change here.
[Galaxy S I9000 Android Development] sztupy:
Github is meant to be social, so you can always modify stuff and issue a pull request (like for example neldar did with BLN). This is actually the preferred way of doing changes in github. This is actually something I asked you before, but you seemed to chose to ignore that.
[Galaxy S I9000 Android Development] supercurio:
You know, it's your software, it's you're responsibility.

I don't want to fork your project so i can make a 2 lines commit, i don't get the point.

And frankly, i don't understand at all the game you play, nor appreciate it.

Too hard for you to respect another project request?

What is that, messing with me or extreme laziness ?
[Galaxy S I9000 Android Development] supercurio:
I think you won't learn anything telling you that you never asked any permission before using the Voodoo name in your software.

It wasn't a problem for me as long as i didn't understood that it was creating a lot of confusion for using, because most of them assumed that it was Voodoo lagfix inside your software.

And as consequence, that your software just made Voodoo lagfix obsolete.

Also, the /system corruption issue, that you still refuse to fix decided me to ask you to remove the Voodoo name from any of your software.

Again, i think it's totally insane you keep such a terrible bug in your software, and refuse to correct it. It's causing a lot of problem to other developers and users.

I totally don't get it nor the attitude you show today.
[Galaxy S I9000 Android Development] supercurio:
If you really want to be "social", stop ignoring my requests.
[Galaxy S I9000 Android Development] dupel:
I wonder why RyanZ	doesn't complain here. Maybe cos he isn't jealous?
[Galaxy S I9000 Android Development] sztupy:
First, the FAQ clearly states why I chose the names for the schemes. You didn't write anything at the time this project was more actively developed, when I could have changed it easily.

Second, this "branch" of ultk is not actively developed as you can already see, as the last official release was about two months ago. The main branch is now "maintained" by hardcore (as it's usually his kernel that people are using), who has already fixed the /system issue (the easy, backward-incomatible way).

The next version will contain the fix, but it has to contain it in a way that makes the version compatible with older releases. This means I have to create the /system conversion part, which was not avialable in previous releases, so fixing this issue is not actually something that can be done in a few steps.

Third, your attitude was not better than mine. It's okay that you say my project has done something bad in a public way (although you could have asked me to investigate the issue too), but after that you started also making false claims (like "it also corrupts /efs") without actually doing some minor research that shows you that these are actually not true. I don't think this is the preferred way of telling the other party of their mistakes (you can send PMs, mails, or start chating. imho these are the preferred way of asking someone to do something in the OS software-development world). I'm usually a calm guy, but I became a bit pissed about how you communicated the things about my project (mainly the false claims).

In conclusion: Please, don't tell me that my attitude is bad. IMHO it's not worse than yours, so I think this discussion can be actually be closed.

(ps: the next version will contain both the /system fix AND will have all references to "voodoo" removed. I might also remove the "OCLF" name too. If you'd like to, then some of my other projects I'll release soon will check whether they are running on a Voodoo rom, and refuse to run, in order to not break things. But only if you insist on this.)
[Galaxy S I9000 Android Development] supercurio:
Ok finally an real answer after more than 1 month you ignore my messages.

Thank you.

Yep.

I hoped you would also fix it in your code because a lot of other developer base their kernels/ramdisks on the software you released or on the git code.

As a result, there is no single day on IRC when I don't have to deal with such a corruption issue.

This is why despite the bug publication it can continue to spread so easily.

And why it deserves a fix in your repo IMO.

It would not mean you continue do develop, it, I understood you decided to change of focus.

Just that it's not a harmless bug and that it deserves to be fixed with a quick note explaining the issue.

I can help you write the description and a HOWTO if you want.

Unfortunately it seems there is no real fix to this problem.

I guess you thought something like that:

- mount ro with always "no check=no"

- then convert to RFS with check=no or another filesystem

It will work for some user but a lot of them used their /system mounted both way.

As a result, there are missing files in both mount options.

It's a deduction made from reading rfs fixer log files from several user, who had missing df binary/symlink even when mounted without check=no. If you find a smarter detection method, that's cool.

When you say "next version", it's a version you're working on without publishing source yet, or by hardcore?

All my apologizes about how I had to come up publicly with revealing crudely the /system RFS corruption bug.

As I already told, the only reason was that you ignored at this time since several weeks all my messages (twitter, xda private messages).

Without any response from you, I could not wait eternally.

Sorry It must have been not pleasant for you and it wasn't my goal at all.

Wasn't pleasant all all for me because I've been accused of a lot of things because of of a bug report.

If you answered and corrected the bug, I'm sure the story would have been very different.

About /efs, it was a twitter message, written as a question and promptly corrected less than 30 minutes ago after verification.

I'm not here to judge anybody of course. I spoke about attitude because I didn't understood your acts. Now I understand better thanks to your explanations, even if I don't agree with some of your choices.

Ya, someone told me hardcore removed the Voodoo name very shortly after I asked you on twitter.

He was also very helpful during the /system corruption crisis, I'm glad he was here with courage to deal with the situation.

There is no Voodoo ROM.

No need to create any artificial incompatibility damageable to the user.

PS: I hope we will keep a better communication like today.
[Galaxy S I9000 Android Development] gicgi:
if its not voodoo, dont call it voodoo

maybe its that simple.

what if i leave papers like "dupel did it" in the crime scene, would u be jealous?
[Galaxy S I9000 Android Development] ragin:
@sztupy,

Hi,

I am trying to put together a specialized ROM meant for architects so that they may start using their SGS as a ready to use tool for their daily work.

I loved your concept of afterburner. Actually a similarly named extension exists in 3dsmax software that we architects use to make presentations of our projects.

Can you help me integrate it into this ROM of mine? Lot of people will find it handy.

Thanks a lot.
[Galaxy S I9000 Android Development] dupel:
O_O

:eek:
[Galaxy S I9000 Android Development] ragin:
http://xdaforums.com/showthread.php?t=864278

???

10 chars...
[Galaxy S I9000 Android Development] sztupy:
A new kind of an "afterburner" style app will be released hopefully tomorrow. Let's get back to this topic then.
[Galaxy S I9000 Android Development] ragin:
Ok, thanks.
[Galaxy S I9000 Android Development] mrwookie6379:
Back on topic then is there an update in the works Sztupy and any idea on ETA? No matter what others I try I eventully keep coming back to your kernal. That can only be good. :)
[Galaxy S I9000 Android Development] anXy:
How do i use the zImage file when i want to flash with Odin? °_°
[Galaxy S I9000 Android Development] gicgi:
looks like we wont be needing any lagfix with froyo 2.2.1
[Galaxy S I9000 Android Development] wcg707:
Its shouldn't be called lagfix now, but filesystem fix.
[Galaxy S I9000 Android Development] rewtnull:
First of all, I want to say thank you very much for this kernel which is my favourite one so far for the sgs. :)

I've noticed that upon using this kernel together with Doc's and Darky's JPX roms, wifi seems to get borked, connecting to AP always leads to immediate disconnect. Could anyone confirm this?
[Galaxy S I9000 Android Development] sztupy:
Development continues here: http://xdaforums.com/showthread.php?t=881837
[Galaxy S I9000 Android Development] ragin:
You should probably announce something like this on the Title. This post will get lost quite soon.
[Galaxy S I9000 Android Development] Gh0stw4lk3r:
installed the overkill option without binds on JP6 with voodoo previously enabled(disabled right now ofcourse), everything went fine and the phone is lagfree at the moment.
[Galaxy S I9000 Android Development] FadeFx:
ah, ok... didnt eaven know what was the problem with this, just knew it does not install some update.zip...
[Galaxy S I9000 Android Development] dagrim1:
Can I simply 'disable' the binds afterwards?

I used the advanced option but didn't disable binds, and of course I immediately got notes that the database was full or someting. Uninstalled some apps, so working now, but would like to completely disbale it.
[Galaxy S I9000 Android Development] Tayutama:
Sounds great and haven't tested it myself yet.

But i got one request... included init.d support :(

It would be nice if you could use the same version as Unhelpful is using
[Galaxy S I9000 Android Development] sztupy:
You can always switch between the lagfix schemes, it will simply convert the files the next reboot.
[Galaxy S I9000 Android Development] sztupy:
Could you drop me a link to that?
[Galaxy S I9000 Android Development] marcedli:
Hi!

I've installed on JPM/JP6 multi, then applied lagfix /advanced without any problems/errors.

The galaxy flies as hell, tried "angry birds" to download/install from market as market-test, everything went ok, no errors.

Thanx Sztupy!

P.s. Csak azon gondolkodom, mi lehet a munkád, ha ennyi időd van ilyen alapos fejlesztésekre:)
[Galaxy S I9000 Android Development] _JKay_:
Im using the Extended option and according to TaskManager my Personal data is at 56.64MB/119MB and has been there for a day now. Everything seems to be running just great! NO FCs!

Regards,

JKay
[Galaxy S I9000 Android Development] Tayutama:
Here is the link to his latest github version: http://github.com/Unhelpful/linux-galaxy/tree/unhelpful-v1.7

The init.d is under: usr/initrd_files/sbin/init.d or one of the other 2 called initrd_files_(something)
[Galaxy S I9000 Android Development] stuclark:
My phone got stuck on backing up EFS and couldn't be persuaded past this point, no matter what I did.

Flashed back to a different kernel and my apps and data were still present.

... want to give this a go, but will wait for the EFS backup to get fixed first.
[Galaxy S I9000 Android Development] Unrealwolf:
Is there any analog of No-RFS Advanced for JM9 Eclair?
[Galaxy S I9000 Android Development] cHarOn99:
i think it depends on how many you install :), i have 90 apps/games on it, with Bind Option enabled at installing the apps i think i was getting the full Personal Data after isnatlling the 40 Apps/Games, anyway now i use Advanced Option without Bind and now no issues anymore.
[Galaxy S I9000 Android Development] ykkfive:
hey sztupy, u've did what i wanted to do already (much more actually)....

btw, seems we've the same ideas like recovery2e->cwm->other updates, but the different is, u made it compatible to other fixes as well and it's available for the whole world
[Galaxy S I9000 Android Development] woeds:
Hi sztupy

Would be be willing to include the Backlight Notification Mod in this rom? Sources can be found here
[Galaxy S I9000 Android Development] ashwinds:
+1 to this request. It'd really be useful.
[Galaxy S I9000 Android Development] sztupy:
Argh. why couldn't the guy just upload the _modified_ sources to github instead of the whole kernel without changelog...
[Galaxy S I9000 Android Development] sztupy:
The pre-dbdata and data mount scripts won't work with my rom, as they are mounted pre-init. Other than this they should work.
[Galaxy S I9000 Android Development] woeds:
Maybe he'll give them to you if you ask nicely? :P ;)
[Galaxy S I9000 Android Development] INeedYourHelp:
Thanks for clarifying. Have you taken a look at the start-up tweaks?

http://xdaforums.com/showpost.php?p=8708125&postcount=1
[Galaxy S I9000 Android Development] wertzuiop123:
so what is the fastest of the options? :D

and can i patch the kernel over tayutama's rom-kernel (CF)? i think there should be no problem
[Galaxy S I9000 Android Development] ed10000:
Awesome! Charging the battery (1%) right now, will definitely give this a go later tonight! :)

What exactly are "binds" though (sorry, a total n00b here!)? :confused: I see that there's an option to disable it in order to fix the low memory issues, but what exactly are the advantages of having it enabled? Does it boost I/O performance somehow (and if so, how?)?

P.S. - sztupy, you must be a ninja or something. Deadly attacks out of the blue, perfect execution with superb style! All the while remaining the cool silent type. ;) :D
[Galaxy S I9000 Android Development] DvTonder:
Anyone tried this on JPA sucessfully? - there is a post earlier of someone having a probelm but not sure if he was the exception rather than the rule.
[Galaxy S I9000 Android Development] sztupy:
Bind means that you have the /data/data directory mounted at the /dbdata actually. This has the advantage that /data/data is used frequently, but /dbdata is faster (it's on a faster chip). The disadvantage is that /data is a 2GB partition, while /dbdata has only 128MB
[Galaxy S I9000 Android Development] avary:
i applied this on jpa, except for a warning about not being able to back up sd_ext, my phone is working fine, faster than previous lagfix(oclf) .. im very happy.:cool:
[Galaxy S I9000 Android Development] RolluS:
Hi!

Great work!

I've had an issue with lagfixer though...

- First time, i've benn using advanced mode and disabling bind, lagfixer was looping.

- Pulling the battery and booting in recovery, lagfixer loop twice and then recovery was loaded

- enabling bind and lagfixer loaded once and phone boot normally, but dbdata/ were quickly full..

binding isn't a bad idea, if using a very superlite rom...

Finally, I use ext4 everywere with no ext2loop and no binding..

Thanks again for the great work ;)
[Galaxy S I9000 Android Development] atinm:
Awesome! I cannot wait to get my hands on the Captivate kernel so I can do this!
[Galaxy S I9000 Android Development] fatpound:
+1
[Galaxy S I9000 Android Development] sztupy:
The MoviNAND device samsung uses is not really designed to be used with yaffs. It can be tried however, but results might be worse.
[Galaxy S I9000 Android Development] spline1:
It stuck with me for backup efs erst. after reboot it went away. now runs faster and a little better than voodoo only
[Galaxy S I9000 Android Development] dwillMUFC:
This happens to me also and has been noted. But when you reboot what happens? does it go back into recovery to do a nandroid backup? because thats what mine does and then gets stuck at EFS again ?

thanks

Dan
[Galaxy S I9000 Android Development] [Ramad]:
I have tried it today...it's too good to be an alpha release.

I can see that there is some bugs that need to be worked out, but I think that this will be very good, and even better when jfs is included, which will reduce power consumption used by the device.

Very good work indeed. :)
[Galaxy S I9000 Android Development] sztupy:
V0.2

Version 0.2 released.

Changelog:

- efs is not backed up automatically during lagfixing (but it's still backed up during ordinary backups)

- added jfs support and some more lagfix schemes using jfs

- added backlightnotification support, with the option to turn it on and off

- added startup script tweaks support, with options to turn them on and off

- removed ext2 support for the base mounts (might be put back into later)

- bind now only binds /data/data (should use less space)

- some minor bugfixes relating

Updating from 0.1 to 0.2:

- if using binds, before updating turn them off, update and you can turn them back on if desired.
[Galaxy S I9000 Android Development] ashwinds:
Thanks for including BLN! jfs seems interesting too.
[Galaxy S I9000 Android Development] cHarOn99:
amazing thanks for 0.2 but i have to agree calling that alpha is a big understatement :P, i am ok if you call it 1.0 RC2 or something hahaha, thanks for this great kernel
[Galaxy S I9000 Android Development] ashwinds:
+1 on the alpha tag. To bundle this much AND have so few issues reported is pretty laudable.
[Galaxy S I9000 Android Development] efegue:
RFS is alfa, not this :)
[Galaxy S I9000 Android Development] ashwinds:
jfs

sztupy - what are your initial impressions on jfs? does it match ext4/ext2 on performance?
[Galaxy S I9000 Android Development] mathieumeuh:
Seems very nice :)

I'll test your kernel tomorrow :)
[Galaxy S I9000 Android Development] musznik:
omg, I love this kernel! good job sztupy ;] :eek::eek::eek::eek: