yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] DocRambone:
Good news :)

The pro is back ...
[Galaxy S I9000 Android Development] dupel:
Yahoo!

10 char
[Galaxy S I9000 Android Development] jeebspawnshop:
^^ Probably not.

And YAY! for the new version ;) sztupy's kernel may have the least number of fancy additions, but somehow I just feel it's the only one I can trust.
[Galaxy S I9000 Android Development] dereknas:
Any sneak-peak as to what is coming :)
[Galaxy S I9000 Android Development] dupel:
Least? Its definitely the most! Other guys (with very big respect to hardcore et al) just took everything together and made it run smoother.
[Galaxy S I9000 Android Development] jeebspawnshop:
Ah, fair enough ;) I agree with you. What I meant is all the fancy things like Voodoo color & sound fixes, UV and OC, etc.

I'm sure sztupy will put all that jazz in some day, but only when he's sure it's working 101% :P
[Galaxy S I9000 Android Development] FadeFx:
As sztupy already stated multiple times, he will only implement features that can be made optional, means easy to disable and are known to work, no alpha state stuff so, but always a reliable kernel.

I guess change in v0.4 will be (eventually with others) fully working jfs, with no problems like timezone and language reset. This bug is hiding well, so i guess (again) that this is the cause for sztupy's absence, spending more time in research and less in answering the same forum questions over and over again.

Nice greets to all

and thumbsup to sztupy

FadeFx
[Galaxy S I9000 Android Development] corgar:
a little spoiler of the new features?
[Galaxy S I9000 Android Development] Hawk:
Can anyone explain what the difference is between this lagfix and hardcore's Speedmod?
[Galaxy S I9000 Android Development] FadeFx:
hardcores SpeedMod has this included plus some extra tricks at kernel compilation to achieve more smoothnes and better battery life. however i am not sure if SpeedMod Kernel is as stable as this one.
[Galaxy S I9000 Android Development] oswade:
WOW! JFS advanced is so much faster than pure voodoo (on JP6 here). Launcherpro app menu loads almost instantly on first open :)

This has saved me from updating from JP6 (Which has been quite laggy, but I prefer to wait a while than be a compulsive flasher lol).

Thanks x1000
[Galaxy S I9000 Android Development] redbull320:
maybe with voodoos color and soundfix *-* ?

it would bee sooo nice :)
[Galaxy S I9000 Android Development] Fihlvein:
sztupy, is there going to be changes in JFS system?

I would like to convert to JFS today, but I don't want to do it yet if something will change in the next few days.
[Galaxy S I9000 Android Development] mschwa1:
Can somebody please provide a tun.ko for this kernel.

I used VPN wird 2.6.32.9 - but since i switched to this lag fix it stopped working.

Reflashing to the previous kernel didn't help either.

Old: I9000XXJPM-2.6.32.9root@sep-42 #1

New: I9000XXJPM-2.6.32.9sztup@ubuntu #138

There has to be something different...
[Galaxy S I9000 Android Development] EscaflownPL:
I'm realy looking forward to install the upcomming version of sztupy's awesome, imho best working, Kernel on my SGS.

The only thing I hope he will update his Kernel to, is to base it on the new JPA/JPO Kernels. Concerning the other changes/upgrades he is going to implement in his Kernel, honestly I don't want to know them now, because I'm looking forward to this "WoW"-moment I had when I installed his Kernel for the first time. Something tells me this time the wow will be a bit larger :D

greetings from Germany, Esc.
[Galaxy S I9000 Android Development] corgar:
waiting for new version and how to flash to your new kernel from speedmod kernel? need some kind of data wipe?
[Galaxy S I9000 Android Development] Polarfuchs:
What is the difference between ext4 and JFS?

I already consulted Wikipedia on this, but there you get only facts like max. file size comparison etc.
[Galaxy S I9000 Android Development] sztupy:
tun.ko should be compiled inside the kernel
[Galaxy S I9000 Android Development] sztupy:
The bad part is that most of the features of ULTK is dependent on recompiling the kernel, so using JPA/JPO as a base is not that easy.

This doesn't mean there won't be ULTK versions that actually use stock kernels, but I can't promiss that the next version will be one of them (it might, this depends on how much time I'll have). One thing is sure, that there will be multiple separate versions: a stable one which will be mostly the same as 0.4 with some fixes, and probably an experimental one, with a lot of fresh stuff, that needs to be widely tested.
[Galaxy S I9000 Android Development] corgar:
any news about release?
[Galaxy S I9000 Android Development] jeebspawnshop:
Shh shh shh! Don't rush genius :P
[Galaxy S I9000 Android Development] Kel Ghu:
Can you make the lagfix convert /system too?

Will we get ext2-only as an option? It can be useful for /cache, no?

Thank you for this awesome kernel!
[Galaxy S I9000 Android Development] Bec07:
How about the JFS timezone bug?
[Galaxy S I9000 Android Development] mschwa1:
I can confirm that VPN status is Connected on my FritzBox.

However: when i type lsmod the tun.ko is not shown.

I still can not connect to any devices on my homenetwork - which i could before.

Any ideas?
[Galaxy S I9000 Android Development] Polarfuchs:
Any suggestions on which to choose?

ext4 vs. JFS
[Galaxy S I9000 Android Development] xan:
I would like to make a suggestion, can we have per partition backup/recovery?

Its kinda pointless to backup/recover all partitions when we change /dbdata only.

It came to my mind because:

I woke up this morning, because phone vibrated once... Like it does when it turns off.

It ate ~10% overnight (data on, sync on).

I plugged the charger, turned it on -> recovery pops in, configs differ.

My scheme was:

/data = ext4

/dbdata = jfs

/cache = ext4

Now the /dbdata was reverted to rfs, so I've lost whole /dbdata partiton.

(fortunately I had backup from last night)

I dont know if it is 'jfs's fault' or 'dbdata' fault.
[Galaxy S I9000 Android Development] BumsNudlFuX:
JFS is da cool ****. try it!
[Galaxy S I9000 Android Development] AnnihilatorSC:
Thanks for your hard work.

Running all ext4... noticed additional battery drain but so far so good.

Would very much like to try using ext2 instead.
[Galaxy S I9000 Android Development] Peacemanibk:
Does someone of you has the app "Smartkeyboardpro" installed? I have noticed that with all the word suggestions and dictionaries enabled, this app lags horrible with a stock JM2. My guess is that it reads a lot for finding the suggestions. With the voodoo lagfix its much better but there is still sometimes a lag from 1s.

Has someone experience how this is on Froyo with the different types of file systems? Would be very interested if thus lag disappears fully when using JFS.
[Galaxy S I9000 Android Development] jeebspawnshop:
I have it, and it works just fine 99% of the times. Only very rarely does it have a slight bit of weird delay when I start writing really fast in some places, but that's about it.

Only reason this isn't off-topic is cuz I use sztupy's ULK in all-JFS mode ;)
[Galaxy S I9000 Android Development] Kel Ghu:
Apparently, Nikodemus' Kernel doesn't have that problem. And weirdly, I don't have that problem with ULFK anymore either since I flashed Hardcore's Speedmod kernel.
[Galaxy S I9000 Android Development] kmrdeva:
I have stock JPM with hardcore's speedmod kernel now. Still facing timezone reset post-boot issue if I go with jfs. I was on the super-optimized kernel before that and I still faced the issue.

Also, yesterday I helped a friend flash his new SGS (i.e. no apps, no data) to stock JPO with speedmod kernel. Using jfs for lagfix still caused timezone resets to GMT+0.

Back on ext4 for all 3 partitions, with speedmod, for now.
[Galaxy S I9000 Android Development] _JKay_:
How come that you need to recompile the kernel? Is it the e2fsprogs for ext4 support? Cant you just use the ones compiled in jpm and copy them to system from data or sdcard?
[Galaxy S I9000 Android Development] sztupy:
ext4 support, jfs support, BLN support, memory config changes (in ultk based modded kernels) and there are space issues too. I didn't really found too much changes between an original and a recompiled kernel either.
[Galaxy S I9000 Android Development] Kel Ghu:
I set my time on automatic (network-provided), so that problem doesn't come up in my case. Though, language does reset to my SIM card default on reboot, which is german and very annoying... I can live with it though, but not without JFS. In my experience, JFS gives a substantial boost in battery life. Far superior to RFS and Ext4. No doubt about this. I can't wait for the bugs to be addressed. We'll see in the next release if sztupy updates the JFS lagfix to Nikodemus' standard.
[Galaxy S I9000 Android Development] neldar:
I have build a sub-build of Universal-lagfix:

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)

BacklightNotification v2.2 with Universal-lagfix v0.3 FIXED for odin/heimdall (md5: 32e19fc8ba5614057c9c17266cf76bbe)

BacklightNotification v2.2 with Universal-lagfix v0.3 FIXED update.zip (md5: 03b74a2f36bbe5c4af40479d0171f563)

This releases are fixed (/system is mounted with check=no).

What is the difference to Universal-lagfix v0.3 by sztupy?

This package is 100% compatible with the BacklightNotification settings app.

No special steps required, only install this kernel and you are done.

Edit: BLN is still disabled by default,

you need to activate BLN

by BacklightNotification settings app OR by cwm recovery.

Source:

Initramfs

recovery

kernel

(notice: upcoming universal-lagfix version by sztupy will also include all the compatibility changes)

Edit:

Does this mod drain the battery?

No, that issue has already been fixed in the eclair build (in v0.9.8rc3).

Measurements showed, that an ongoing BLN increases battery consumption by 0,18% per hour. The average battery consumption without BLN is 1,04% per hour, so an ongoing BLN results in an overall battery consumption of 1,22% per hour. And by the way: ongoing NoLed results in an overall battery consumption of more than 2,5% per hour. Please see the Q&A "How much does this modification affect battery life?".
[Galaxy S I9000 Android Development] sztupy:
Thanks for putting these up!
[Galaxy S I9000 Android Development] gicgi:
just a couple requests for next version:

-would you please put a blank option at the top of the recovery mode, so that nothing will be selected while keeping "volume up+home+power) pressed.

-would u please let people change settings in recovery mode without being have to backup system?

-would you please add "delete backup, save backups to sdcard/phone" options in

recovery mode?

-i want to change button usages. for example, using home button as power switch or, using power button as home etc... can it be done via kernel?

-why dont you sell your wonderful work to samsung?
[Galaxy S I9000 Android Development] Schrotty35:
Which one i need it for Froyo 2.2?
[Galaxy S I9000 Android Development] sztupy:
either one. The first one is for flashing via odin, the second one is to flash via CWM or 2e recovery
[Galaxy S I9000 Android Development] peachpuff:
sztupy: will you be adding any more partitions to the lagfix, such as /system and /efs?
[Galaxy S I9000 Android Development] Schrotty35:
Ok thank you. Can i use it with Froyo JPO or need a other Kernel? If I install this, I must then make a wipe?
[Galaxy S I9000 Android Development] kendragon:
I have a question, if I go in recovery mode and I install voodoo lagfix How can I remove it? is there an option in recovery mode menù to remove lagfix?
[Galaxy S I9000 Android Development] Kockowan:
GalaxyS is rooted by CF-Root-1.2, Rom Manager and 2e-ClockWorkMod-Recovery from Market are installed on Froyo-JPO.

Root doesn't matter, but what is about the Rom Manager/CMW?

Must Rom Manager/CWM be removed before flashing this kernel?

Thx....
[Galaxy S I9000 Android Development] _JKay_:
Did a speed test of /system folder where I cpio all files to null. RFS gave me 12 - 13 Mb/s and JFS gave me 25 - 28 Mb/s!!!
[Galaxy S I9000 Android Development] corgar:
news about 0.4 release?
[Galaxy S I9000 Android Development] deli_gt:
Hi sztupy why don't you make ext2 available as non loop device.

It's faster than jfs and same as ext4 but consumes less battery.
[Galaxy S I9000 Android Development] sztupy:
The autodetection between ext4 and ext2 was not working, that's why I removed this feature from 0.3. Don't worry, it will be back.
[Galaxy S I9000 Android Development] knak2k1:
sztupy for president \o/
[Galaxy S I9000 Android Development] kmrdeva:
Can't wait, really. Am very keen to try 'voodoo'-like ext2 - all partitions on native /ext2 instead of loop would be really sweet..
[Galaxy S I9000 Android Development] Adevem:
i'm currently on speedmod(the latest) and if i'm not wrong, it's based on your ULFK! big kudos to you. :D

was playing around with overkill ext4 without binds earlier today. currently trying out overkill JFS without binds now.

hope i won't have funny issues as some has reported ;p

great job!
[Galaxy S I9000 Android Development] elivagar:
succesfully on italian offical RSjp5. thank you!
[Galaxy S I9000 Android Development] deli_gt:
And would it be possible to convert other partitions also ex System etc...
[Galaxy S I9000 Android Development] hardcore:
@sztupy:

IMPORTANT! I just found that fsck was not checking the filesystems properly (most of the time) at boot. I'm not sure if it happens with all ULFK 0.3 variants, but it definitely happens on my SpeedMod kernel.

I checked the /res/pre-init.log, and I saw lines like:

Trying to mount /dev/block/stl10 to /res/odbdata

Run a filesystem check on it

DBDATA: clean, 674/32896 files, 9239/32896 blocks (check deferred; on battery)

So it looks like fsck is not checking the filesystems when running on battery (and sometimes even plugged in).

I guess this is only a problem if the user is using an ext4 lagfix scheme. Not sure if it affects jfs, but in my case I noticed it with ext4.

I tried one fix for this:

I created and copied a file called e2fsck.conf to /etc/e2fsck.conf

The file should contain:

[options]

defer_check_on_battery = false

But it didn't seem to work. I still got that check deferred; on battery error.

Then I just modified all the fsck commands in the pre-init.sh to include the -f parameter. That worked.

I wonder how much of a problem it really is.
[Galaxy S I9000 Android Development] sztupy:
Thanks for the info. The severity of the problem depends on whether the check is also deferred if without a check the filesystem woudln't mount. If the checks wouldn't run in these case then this is actaully a major problem. (as the system won't boot up properly). On the other side the -f flag might slow down the boot process because it wuld always check, even if it has no sense. It's still better to stay on the safer side though.
[Galaxy S I9000 Android Development] deteego:
I have an issue, when applying the "No-RFS Standard: /data is rfs+ext2, all other partitions are ext4" along with Darky's Mod, it gets stuck on "creating /data".

Using the "No-RFS Advanced: all partitions are ext4" works without problems.

Should I just use the OCLF through the APP on the market (and would this be any different?)

Any ideas why this is happening?

(Darky's mod is located here http://xdaforums.com/showthread.php?t=814091) and it uses SpeedMod
[Galaxy S I9000 Android Development] mkdr:
I updated my kernel, I came from VooDoo and I have a JPM build, with the universal lagfix kernel. All went well, I converted successfully via backup & restore to 3xjfs. But shortly after using I noticed that my system language was reset and USB debugging was also enabled, I changed the language to English and disabled USB debugging, all seemed well. But after a reboot some time later, it was set back again. I tried to change it again, it works, but after a reboot the settings are gone again. How can that be, and can I fix it without flashing my whole rom? :/
[Galaxy S I9000 Android Development] elivagar:
Hi ... thanks for the work!

I posted just upside that everything was ok on italian froyo official

I used the option everything in ext4 with backup and restore

my firmware : baseband JPP and FW revision RSJP5

Everything was ok but day after on boot all the software crashed (first launcher pro and was impossible to go on....every single application crashed one after another. I reboot again but was the same and i decided to reflash the orignal firmware and kernel

DID you have any notice about waht happende? (may be to others?)

thanks in advance , I 'll try again
[Galaxy S I9000 Android Development] [Ramad]:
To my understanding, USB debugging should be ON by default in this kernel and is not a bug.

Other bugs only appears when using JFS and has been discussed earlier in this thread, they are all related to jfs utils that is developed by nikademus.

Unfortunately, nikademus refuses these bugs' relation to jfs utils so don't expect a fix soon.

An easy fix is to use ext2 or ext4 on this kernel by reverting back to rfs (Disable Lagfix) and then converting to ext2 or ext4.
[Galaxy S I9000 Android Development] mkdr:
Thank you very much for the infos. So USB debugging is enabled by kernel after each reboot. But why is my language reset too after each reboot (I want to use English as system language but it is set back to German after each reboot, that just happenes now with the new kernel, it never happened before), is it because of those jfs bugs? And what does that do also to my system or can do I maybe have not noticed yet? You spoke about other bugs regarding to jfs, so using jfs is unsave? I thought I read somewhere jfs is much saver to use than for example ext4, because you can get data losses with ext4.

And what does that quote mean? So ext2 is the best option, but it is not availabe atm in 0.3? Im really confused now what I should do :(
[Galaxy S I9000 Android Development] jeebspawnshop:
JFS works fine, but it has some bugs in it (like the ones you mentioned). It is also not safer than ext4, if you want to put it in those terms, because they both work sort of the same way (journaling).

Also, sztupy's kernel does not yet support ext2 natively - for mounts - but he said he would include it in 0.4 (I think...).

And before you ask, ext2 is PLENTY safe to use once it is implemented, and it doesn't have any bugs like JFS. And ext4 uses too much battery.
[Galaxy S I9000 Android Development] [Ramad]:
USB debugging should be on and that is because Clockwork is using it, this is not a bug as I understood earlier in this thread.

-Time reset

-Language reset

-"Clear Data" seems not to take effect under "Manage applications" in Settings

These are bugs related to jfs-utils and not JFS, jfs-utils is the program that converts the file system on SGS from RFS to JFS.

JFS is a very reliable and trusted filesystem, please search the net for more information.
[Galaxy S I9000 Android Development] Peacemanibk:
One question since i have just read a couple of articles about journaling file systems and ssd's: would it be possible to include a lagfix scheme using ext4 without journaling? This maybe provide better performance then ext2 because of the additional features of ext4 (block access as far as i understood). Any opinion about this idea from the experts?
[Galaxy S I9000 Android Development] mkdr:
So you say I should stay with 3 x JFS, because ext4 uses too much battery, ext2 is same like JFS when it comes to performance but not yet native implemented by kernel. But JFS somehow has those three major bugs, timezone reset, language reset, and the clear data option not working. But how can that be, I mean, how can the file system affect something like these software implemented things like language or timezone? Arent those just settings saved somewhere like any other setting which are working. Why not those two? That does not make sense actually. Timezone is not that important because it will be set to the right time after reboot by GSM signal, but language is somehow bothering me :/
[Galaxy S I9000 Android Development] [Ramad]:
Settings such as time and language are saved on a partition which is /dbdata, I have investigated JFS lagfixes for some time now and I can only see that /dbdata might not be mounted/un-mounted properly, that is all what I can tell, the rest is up to the developers, I only count myself as a tester.
[Galaxy S I9000 Android Development] x86-Dark:
Any update in program? :D
[Galaxy S I9000 Android Development] CrashHD:
So which option actually ends up being the fastest / best?
[Galaxy S I9000 Android Development] sztupy:
I'm working on it when have the appropriate time.
[Galaxy S I9000 Android Development] sztupy:
That depends on a lot of things. ext4 advanced is probably the most stable.
[Galaxy S I9000 Android Development] defconoi:
running a few i/o tests with quadrant advanced comparing ext4 advanced and jfs advanced, jfs is getting 2900-3400 i/o scores when ext4 is getting 2100's. So for anyone asking JFS is the fastest. Run some i/o tests and see for yourself :)

also read online that jfs's cpu usage is lower than all other filesystems that we use, so it should extend battery life and reduce lag in our devices
[Galaxy S I9000 Android Development] cortx:
Hello;

I've a probleme with my phone and I need to do an Hard reset.

I should back to BUJG2 with "Clear Storage" in recovery menu

So First I should remove the lagfix, the root option and back to the original kernel.

***

By memory, with the new recovery mode there is an option to remove the lagfix. I've chosen the No-RFS Advanced (format in ext4), is that enough ?

For root, I didn't saw the option to remove, How can i do ?

For kernel, is OK if I put the firmware with ODIN, (The entire firmware BUJG2 is available into the thread of this forum)

***

How could I proceed please ?
[Galaxy S I9000 Android Development] [Ramad]:
I think that you can still use 512.pit to flash any firmware so far.

I understand that this is a one package update rom, if you install JM8 with 512.pit with re-partition then I think that you can flash any one package froyo just by flashing as PDA, granted that you might get some errors in recovery when flashing to JM8 but it can be fixed by a factory reset/wipe cache.
[Galaxy S I9000 Android Development] hardcore:
That was what we thought. But for the DXJPA firmware we must use the 513 PIT because the 513 PIT has the biggest /system partition and apparently DXJPA needs it. If you try it with any other PIT, the phone just won't boot - it'll get stuck at the first Galaxy S screen.
[Galaxy S I9000 Android Development] [Ramad]:
How big is the factoryfs.rfs?
[Galaxy S I9000 Android Development] hardcore:
Its only 267288576 bytes but the CSC copies a lot of stuff into /system. The cache.rfs and dbdata.rfs are quite big, and I think it does a one-shot copying into /system after the flash.
[Galaxy S I9000 Android Development] [Ramad]:
I have just tried flashing using 512 pit on Heimdall which allows to flash separate files, I can conclude that it's the factoryfs.rfs that does not allow the phone to boot, flashed with/without dbdata and with an empty dbdata, replaced kernel, param.lfs...etc. but no boot on 512.
[Galaxy S I9000 Android Development] sztupy:
The problem is that the 0.3 can't format /dbdata as RFS. If using a lagfix scheme that also converts /dbdata (to ext4 or jfs, it doesn't matter), it will work. Switching to RFS won't however. Afaik in the 0.4_pre version I already fixed it (or not, I don't remember. The git version should contain the fix though).
[Galaxy S I9000 Android Development] mapas:
i think it is just a matter of compiling the kernel using the compiler optimization flags... it should affect all versions.
[Galaxy S I9000 Android Development] newter55:
I want to test this but not sure about trying it on my captivate..anyone want to provide some advice? Not much new coming out over there so I came to lurk around here and couldn't help but read about this.