yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] ashwinds:
if you are already up for an odin flash, try to change the lagfix to ext4 and see if that resolves it first ;)
[Galaxy S I9000 Android Development] LockeOn:
Hi sztupy!

Your work is great, my phone while using No-RFS Overkill JFS is a total rocket so it is almost all I need but I was wondering if it is possible to include this kernel mod "[REF] reserved memory tests - around 356mb visible" to your universal lagfix kernel?
[Galaxy S I9000 Android Development] dupel:
It is unfinished work. How would you like for your phone to restart every time you plug usb?
[Galaxy S I9000 Android Development] LockeOn:
I meant including it to ULK as soon as it will be more or less stable without any major bugs.
[Galaxy S I9000 Android Development] wsnipex:
external_sd

is there any chance you could include support for formatting the external SD to ext3?

I'm often getting corrupted FS on the external SD card, but I don't think its broken.

I'd like to try ext3(because there is a ext3 driver for windows) and see if this solves the problem.

PS: any news on the USB 2.0 issue? seems with your kernel USB is only running on 1.1 mode.
[Galaxy S I9000 Android Development] sztupy:
I only want to include options that can be turned on and off somehow. The memory mappings are unfortunately fixed during compiling. If it gets safer I might add a few extra MB for the ROM to be a bit smother, but that's all. Btw everything is open source in this project so anyone can build his/her own ULTK kernel image (might post a tutorial soon)

About SO-kernel: all optimizations are turned on, except for -O3, because that increases kernel size, and size is already at the maximum. I still have to decrease the used size of the stuff, so the initramfs could fit into any official kernel, like JPA, or the kernels from othe types, like the Fascinate/Captivate.

About JFS: Yes, it seems using JFS breaks some thing (like the timezone or the inability to remove cache data). Unfortunately the logs tell nothing about why it breaks (the "could not remove cache files" is not a very expressive error message), and it's actually strange that it only breaks if using a specific file system (which it shouldn't as jfs, extx and rfs are all posix compilant). One might try using ext4 for /data and jfs for the other two and see how that combination works.
[Galaxy S I9000 Android Development] LockeOn:
Actually it would be nice to have an option ULTK with extra RAM and ULTK with regular RAM. Anyway I really appreciate your work.
[Galaxy S I9000 Android Development] dupel:
Well, we all understand your point and we all respect you point of view, as its your kernel :D

But might I suggest - right now this kernel seems to be the most complete and fastest thing around. And maybe you could compile (if it doesn't take too much time) a secondary kernel with more permanent changes (voodoo? RAM? -O3? (if its quicker)) too, so to make it @ultimate-super-duper fast kernel@. But only as a side project, so it doesn't take your attention from perfecting this beautiful piece of coding =)

Maybe even try to work with curio, to incorporate voodoo completely ("delegate" this part of work to him). So we don't have a difficult choice of voodoo vs. this. And to avoid fragmentation :cool:
[Galaxy S I9000 Android Development] sztupy:
Formatting the internal or external SD card is a bit more problematic, as a lot of things depend on them, and I think most of them are hardwired to use vfat. You might try formatting it to ext3 on a computer though and see whether it works.

For me (using ext4 advanced) it works in 2.0 mode
[Galaxy S I9000 Android Development] Ettepetje:
You mean better than you get with stock froyo memory settings? :D
[Galaxy S I9000 Android Development] koukos:
Is it possible to add ntfs support for sd?
[Galaxy S I9000 Android Development] sztupy:
For -O3 to be usable I still have to cut down kernel size (after 6.1-6.2MB the snowing will appear which I don't want, and actual size is already 6MB). And personally I had a lot of problems with -O3 kernels on x86, so I'm a bit reluctant to use it on arm either.

On the other side I'm working on a kitchen that can be used to compile your own ULTK kernel, so you can actually chose between the unmodifiable options. It's still work in progess. (I try to make it usable on windows and without cygwin, which is not an easy feat)

Voodoo is a separate project, as it handles the filesystems in a more sofisticated way (I don't know wheter the fact that I'm not updating the partition table is the root cause of some of the issues or not. I don't think it is, but it might). For the other fixes they are actually opensource'd so I can incorporate them, but as I've read they still have some minor issues, so maybe a later time.

I'll announce feature-freeze soon and start testing one of the options (Advanced ext4 with some tweaks) extensively for a week to see how it's long-term performance is.
[Galaxy S I9000 Android Development] sztupy:
for ntfs support one has to add FUSE + NTFS-3G support. Neither of them were ever tryed out on the SGS, although they might work after some hacking.
[Galaxy S I9000 Android Development] ashwinds:
jfs

hmm - will give it a shot and let you know.

Update 1: Tried it and both timezone and clear market is ok now.. will see how the performance is - dont see any difference initially. The battery life on jfs was pretty good - about 89% remaining after over 6.5 hrs - best i've had- though I am sure part of it is due to the AOSP goodies in Doc Rambone's ROM. Will update if i see any quirks.

Update 2: Performance is good... maybe good as i have ever seen - mail, titanium backup are very quick. Leaves just the battery life to check!
[Galaxy S I9000 Android Development] Ettepetje:
Have the 0.3 kernel installed with Advanced JFS and all Tweaks (Misc + BLN) enabled.

Didn't have any problems with Time-zone (still +2), but that could be because I don't have auto-sync Date/Time enabled. I only infrequently enable to sync, to prevent problems with alarm clocks etc. (clock skipped several hours when awoken, in JM2).

This kernel has worked great the past 15 hours!! Installing was also very well done: hot plugable to an existing stock froyo JP6 install, very powerful controls at the hands of the user...

The only things that I still need to do every reboot is apply Minfreemanager and laborously disable the Diamond default headphone equalizer settings. The first might not be really necessary on froyo sgs (?), and with a little luck supercurio will solve the second one.

As a programmer I feel tempted to hunt down such missing parameter adjustments myself. Some could be included in your wonderful modded kernel.
[Galaxy S I9000 Android Development] dakine:
I'm totally amazed by this. Not only is it a lagfix but just about every lagfix available with backup options and a bunch of other cool stuff that I don't even understand :D

I flashed this over chainfire's rooted kernel and applied jfs advanced. It seems that something went wrong though during restore, since it got stuck for a while and then just rebooted. Tons of FC's and a message about something being inconsistent (cmd?) and that I should wipe my system partition. I clicked "I'm feeling lucky" and rebooted the device into recovery and that time it was able to do a proper restore.

Did this happen because I flashed it over a already modified kernel? The phone seems to work fine now and it's nice and snappy. JFS Advanced gets around 1620 on quadrant for those who care.
[Galaxy S I9000 Android Development] Meister_Li:
I am using the normal No-RFS JFS fix for now. It seems to work quite well, all of it, really. The phone runs fast and snappy, the date and time are correct and it actually seems to use much less power than before. Pretty awesome work, thanks a lot! :D

Edit: Oh! Also, BLN is working perfectly! Really cool! :D
[Galaxy S I9000 Android Development] Ettepetje:
No, did the exact same thing. Smooth as a freshly wiped sgs screen.
[Galaxy S I9000 Android Development] MrBusiness:
I did not want to hijack the other thread, so I ask my question here but it is related to that posting:

http://xdaforums.com/showpost.php?p=8775982&postcount=31

Should all people who use your No-RFS Overkill Option delete all samples (Video/Mp3) to make using bounds more viable?

Furthermore due to the fact that you are gaining more knowledge about the partition sizes, you could perhaps give us an approximate value how much apps (measured in MB) we are allowed to use?
[Galaxy S I9000 Android Development] avary:
how about the battery? which lagfix scheme is more battery friendly ?
[Galaxy S I9000 Android Development] FadeFx:
thats easy, its jfs, but you might wait a bit with that since there are some problems with jfs that need to be sorted before it is fully usable. meanwhile you could use ext2/4 and convert to jfs later on...
[Galaxy S I9000 Android Development] bilboa1:
on x86 Os is pretty good
[Galaxy S I9000 Android Development] dakine:
What issues exactly? My market and time work fine, is there something else?
[Galaxy S I9000 Android Development] FadeFx:
if you got those sorted then you are all good...
[Galaxy S I9000 Android Development] spiritofhumanity:
I am using No-RFS Overkill JFS and after 12 hours of just about average usage (wifi, music player, calls) battery is > 90%.
[Galaxy S I9000 Android Development] jurguh87:
flashed the kernel and after that did install zip from sdcard and installed tayutama full rom but got stock at the galaxy s screen(with the white letters)

anyone what the problem is
[Galaxy S I9000 Android Development] artyte:
Some observations

When I first flashed this over a fresh JP6 and using overkill JFS, it was running very smoothly without any problems. But once I started my restore from titanium backup, it restored around 80 applications then told me that my storage is full. FC started coming up, titanium backup couldn't run. I think it is because of the bind.

Then I did a wipe and changed to advanced JFS. Upon boot, everything ran well, until I restored all my 150+ applications when the phone started to run slower than that of my DXJG4.

There was also a problem with the notifications bar. Sometimes, I can't pull it down. GPS problem still remained even with JFS partition (it was supposed to be a bit faster but there was no change). Couldn't find chrometophone application on apps market. Angry birds, skies of glory, neocore, and cestos 2 doesn't show the proper shortcut application upon boot and had to be replaced onto the home screen for it to work.

I don't really care about quadrant at this point but from my experience, it is running slower than my DXJG4 with OCLF.

For those who wanna know the score: Quadrant-1600+

Overall, I'm quite disappointed with the european froyo even with this superior lagfix.
[Galaxy S I9000 Android Development] dakine:
Flashing a full rom doesn't that replace the universal lagfix kernel? Have you tried restoring to factory settings? That's usually what I have to do if I get stuck on that screen.
[Galaxy S I9000 Android Development] dupel:
Tayutama rom has its own custom kernel
[Galaxy S I9000 Android Development] [Ramad]:
The use of ext2/ext4 is more optimized for sgs because they have been used as lagfix on the device for a while, jfs is new to the scene as a lagfix and is yet to be optimized.

In the power consumption department with jfs , 3%-4% of the battery have been used by the device in 9 hours while idling (during the night) and wifi was on.

Changed to ext4 3-3½ hours ago and the usage is 3%.

Ext4 feels smooth and more responsive than jfs and that is expected, I can pretty much say that there is no issue with ext4 advanced. Well done sztupy for a very good work. :)

There is clearly an issue regarding jfs. jfsutils by nikademus needs to be fixed/optimized, but still is good work by nikademus and sztupy.

Waiting for sztupy to start working on YAFFS2, that I think will be a hit :)

Last time I asked about YAFFS2 the answer was that it is not optimized to work on MoviNAND but on raw NAND, but here we are running ext2/ext4/jfs on MoviNAND and non of these filesystems are optimized for NAND but for magnetic-mechanical harddisks, at least YAFFS2 is designed to work with flash.
[Galaxy S I9000 Android Development] RyanZA:
Filesystem should have very little impact on battery. If you're seeing differences in battery use of more than 5%, then it is something else. Filesystem can affect battery though, but the differences are too small to be measured without dedicated equipment. :D
[Galaxy S I9000 Android Development] RyanZA:
While EXT4 and JFS are optimized for spinning disks, EXT2 is much simpler and is really device agnostic. YAFFS2 is only optimized for NAND in the sense that it does wear leveling - the filesystem itself is not that great, or that fast. Don't expect too much from it, or you will be disappointed. :) (YAFFS2 running directly on hardware should be roughly the same speed as EXT/JFS running ontop of STL -- of course, real testing is needed! Hopefully someone can port it. :D)

YAFFS2 not working on MoviNAND also has nothing to do with optimizations, but lack of low level interface -- it can't work on MoviNAND.
[Galaxy S I9000 Android Development] [Ramad]:
I would be looking for ext2 when ultra-speed and and very high response is needed, but what I'm looking for is good response and long battery life, this is pretty much what I am looking for in a smart phone.
[Galaxy S I9000 Android Development] [Ramad]:
I'm still missing a proof of that anyone did try YAFFS2 on MoviNAND and failed. Nobody did try it yet last time I checked. :)
[Galaxy S I9000 Android Development] Bec07:
Ok... not funny...

What I've done:

JM1 + 512 pit + repartition, boot, JP6 + 803 PIT + no repartition, boot, flashed Da kernel 0.3, boot, and quadrant checked the following:

-No-RFS Advanced: all partitions are ext4

-No-RFS Overkill: turns on all options: everything is ext4+ext2 and /data/data is bound to /dbdata

-No-RFS Advanced JFS: all partitions are jfs + wipe all user/sustem/cache data

Full JFS:

Restored ~60 apps with titanium backup

Removed bloatware with Root explorer

Removed youtube and installed it from the market.

Youtube works fine for a while.

A few hours later I try youtube, it crashes, I reboot and the thing I posted on top shows up...

Any questions?

I need answers...

Ok, UID stuff... probably some remniscent youtube files caused the issue. Deleted them, reboot and reinstalled.

I hope that was the issue.
[Galaxy S I9000 Android Development] dakine:
I'll try ext4 on my second phone and see if there really is a difference with jfs.
[Galaxy S I9000 Android Development] Bajo76:
Installed the kernel a half hour ago and it is the best experience so far, used No-RFS Advanced: all partitions are ext4 and BLN.

Cannot tell much about battery drain after just an half hour. Donating right now ;)
[Galaxy S I9000 Android Development] [Ramad]:
Try this:

Flash to JM8 512.pit + repartition.

Flash to JP6 512.pit

no

partition.

Do a factory reset/wipe cache.

Flash the 0.3 kernel and use ext4 advanced.

JFS has some issues now, ext4 is working fine.
[Galaxy S I9000 Android Development] artyte:
will the difference in performance for JFS and EXT4 be distinguishable?
[Galaxy S I9000 Android Development] xtrememorph:
This problem seems familiar to me could be cause by conflict between click work mod versions.

I usually flash with working 2e kernel and install original cwm update.zip than install tayutama.

Finally flash with this multi kernel.
[Galaxy S I9000 Android Development] kekelingling:
it's good job! thanks!
[Galaxy S I9000 Android Development] lmulli:
I'm using Advanced JFS on the full JPM rom and have not any problems whatsoever - market fine, time and date fine, no FC's. Prior to this, I was using Advanced Ext4, and again, no problems whatsoever as above.

Jobs a good un.
[Galaxy S I9000 Android Development] DvTonder:
Just switched from JFS Advanced to EXT4 Advanced and find the phone noticably faster with EXT4.
[Galaxy S I9000 Android Development] dakine:
OK just compared my 2 phones, one with ext4 advanced one with jfs advanced. The phones are setup almost identically apart from that the jfs phone has about 3 times more apps installed. Home screen and widget wise they are identical.

Quick conclusion is that for some reason on my 2 phones JFS is faster. While the quadrant scores are almost the same the JFS phone completed the tests 5 to 8 seconds faster! (i ran it several times) The apptray opened a bit quicker on jfs even though that phone has a lot more apps installed. Same goes for almost every program I opened, in most cases jfs is just a little bit quicker.

I tried this after a fresh reboot just to be sure.

I'll monitor battery use now to see if there is a difference there.
[Galaxy S I9000 Android Development] Bec07:
+1

I got ~1400 with ext 4 (for all & no loop) only and ~1600 with JFS (for all& no loop) in quadrant.

Also the device is extremely responsive!
[Galaxy S I9000 Android Development] artyte:
Just changed to no-rfs advanced ext4. didn't feel any difference from jfs.
[Galaxy S I9000 Android Development] [Ramad]:
It does finish quadrant faster using JFS, if you compare when it does Database writes in I/O then you will notes that JFS does complete it faster.
[Galaxy S I9000 Android Development] artyte:
I just found a terrible bug. The phone turns itself into airplane mode upon receiving a call, and turns back to normal when the call has failed to receive.

~no-rfs advanced ext4
[Galaxy S I9000 Android Development] dupel:
As we discovered in another thread if you dont no a repartition pit file isnt used. So it makes no difference what file you use after that.

I would recommend to original poster of problem to try doc's rom - whole rom with this kernel.
[Galaxy S I9000 Android Development] jurguh87:
so installed tayutama rom rooted and after that flashed the kernel and now i want to apply no rfs advance ext but after do i have to do something with the superuser ot is it all good for use with titanium backup

thanks
[Galaxy S I9000 Android Development] SLX69:
Ended up flashing Voodoo Doctor Edition v2.1 and it's now running smoothly with the Advanced JFS lagfix, go figure :-)
[Galaxy S I9000 Android Development] avary:
thanks all for your feedback about battery usage..

today my full battery drained totally in about 8 hours. half of them i was running wifi and surfing/using market. i don't know if this is normal ? or my battery is fake ?
[Galaxy S I9000 Android Development] artyte:
can someone address my problem if you know the answer? At least tell me whether your's works with receiving calls.
[Galaxy S I9000 Android Development] brnbock:
Would love to see where this goes
[Galaxy S I9000 Android Development] SLX69:
No such problem over here, receiving call with no problem at all.
[Galaxy S I9000 Android Development] laststufo:
Could i use your work to build a super optimized kernel?
[Galaxy S I9000 Android Development] _JKay_:
Work fine for me (Nordic I9000 with JP6 with alpha 0.1 overkill and bind). Might be a combination of things... To help you we need a way to reproduce the problem.
[Galaxy S I9000 Android Development] TheNikkoMan:
Using no-rfs advanced overkill (?), working insanely good! The only thing is that quadrant gives me 1400, despite that the user experience is way better than when I used voodoo and I got 1800.. But this just proves that numbers don't mean anything :D
[Galaxy S I9000 Android Development] titooo7:
I have tested the following lagfixes with 55apps installed and using touchwiz launcher (note the bold letters because I think it use to be the cause of the lag):

* No-RFS Advanced: all partitions are ext4

* No-RFS Advanced JFS: all partitions are jfs

* No-RFS Overkill JFS: turns on all options: everything is jfs+ext2 and /data/data is bound to /dbdata

I didn't feel too much improvement compared to stock kernel and I also didnt notice any difference between the lagfixes mentioned avobe: I still had some small lag when switching on the 6 pages of the app drawer.

No-RFS Advanvced (all ext4) and No-RFS Advanced JFS (all jfs) scored around 1500, while No-RFS Overkill JFS scored around 1700. But I don't care on benchmarks...

I don't know if it's because I didn't reflash the kernel before doing the change to another lagfix (if im not wrong its not necessary) or because I didn't make any wipe when changing from one lagfix to another. Any advice?
[Galaxy S I9000 Android Development] Cotw:
Just flashed 0.3. The timezone issue must be related with JFS, 'cause I switched to No-RFS (ext4) and I don't seem to have any problems so far :)
[Galaxy S I9000 Android Development] TelloBJK:
how do i upgrade on 0.3?

i have installed 0.2 with No-RFS Advanced: all partitions are ext4.

can i flash it over and all settings ( i mean ext4) will be saved?

p.s. nice lagfix and kernel
[Galaxy S I9000 Android Development] sztupy:
Yes, 0.2->0.3 upgrade should be easy
[Galaxy S I9000 Android Development] ivanchin99:
fixed... :)
[Galaxy S I9000 Android Development] Ettepetje:
After reading up on the 'Headphone' topic the equalizer problems are gone in froyo. Hooray! :)
[Galaxy S I9000 Android Development] Tayutama:
Read something interesting on the Fascinate forum.

They made a kernel that supported /data/local/bootanimation.zip ie. custom boot animations...

Could we get this added in v0.4? :D

Sadly he didn't post link to a github or source so can't link it :(
[Galaxy S I9000 Android Development] renaud:
Seems extremely nice. I am not sure it's still useful to develop my own jfs lagfix. I will definitely test on Monday.
[Galaxy S I9000 Android Development] _JKay_:
You might want to try and use LauncherPro, AutoKiller and AutoRunKiller. And maybe also remove the system apps you never use (with SGS Tools).

I use Alpha 0.1 Overkill w. bind. I have LauncherPro w. 60 apps installed and my SGS has no lag whatsoever. Quadrant Advance 1.1.1 says: 2011. IO only it says 784.
[Galaxy S I9000 Android Development] dupel:
I think it is still useful. It is different (on external). Might not be as quick, but still some people will find it useful.
[Galaxy S I9000 Android Development] titooo7:
Thanks for taking your time to answer man ;)

Yeah, I know I probably wouldn't have any lag with ADW, LAuncherPro or specially Froyo stock launcher, but the thing is that I prefer touchwiz to any other launcher...

I just would like to know, is there any body with +50 apps installed and without lags using touchwiz?
[Galaxy S I9000 Android Development] sztupy:
Anything is possible. Those should've been done as the lagfix schemes, so one can choose between different configs.
[Galaxy S I9000 Android Development] cHarOn99:
great then maybe you can add it soon :P ? anyway i will try now first the 0.1 alpha, damn backing up my system takes so long lol
[Galaxy S I9000 Android Development] franklin01:
Tested and working (on multi v3).

This is awesome...

What can be improved?

Extend !

If possible and not too hard/long add some options like:

-Browser fix ( http://xdaforums.com/showthread.php?t=810668 )

-Gps fix epic 4G ( http://xdaforums.com/showthread.php?t=759976 )

-Gps fix gps.conf ( http://xdaforums.com/showthread.php?t=731462)

-Startup script ( http://xdaforums.com/showthread.php?t=813309 )

-Disable unwanted services ( cant remind the post, it was a sh that stop a few services to free up ram)

-App2nand ( http://xdaforums.com/showthread.php?t=756157 reported to fix keyboard lag etc... tested and working but dunno if it can work with other lagfix )

And for the fun:

-Battery mod ( http://xdaforums.com/showthread.php?t=809379 )

-TWLauncher landscape mod ( http://xdaforums.com/showthread.php?t=792817 )

-Eclair keyboard ( http://xdaforums.com/showthread.php?t=796854 )

-All in one pack ( just an option to apply all fix in 1 click )

That's just some ideas and I know this could be hard to do so just think about it...

Anyway thank you very much for your awesom work.
[Galaxy S I9000 Android Development] _JKay_:
Going for the extreme overkill option... anything else would be boring :-)

Alpha means "needs testing"... so we test... bbl..... and thanks!!
[Galaxy S I9000 Android Development] deli_gt:
I have a feeling this is going to be big.

My SGS is snappy as hell.

ADVANCED