yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] adelskrev:
I would also like no know that, have the same as you JM1, i have

PDA:I9000XWjM2

PHONE:I9000XXjM1

CSC:I9000NEEjM1

Will it work on mine? Regards Jörgen
[Galaxy S I9000 Android Development] dkcldark:
It should work in theory but haven't tried it. So you could find it out if it's working!
[Galaxy S I9000 Android Development] RyanZA:
It cannot be the same - the source was released ages ago, and samsung has changed the kernel from JF* to JM*

So.. someone go get them to release the changes please!

Plus, the actual drivers - that are labeled in the source as 'GPL release version' - do seem to behave differently to the ones in the samsung stock kernel.

So I think we don't have the same sources. It is very very hard to check though, or at least, I don't know how. :)
[Galaxy S I9000 Android Development] bub181:
I totally agree. They released the source months ago and I'm sure they have made changes since then. Unfortunately they seem to be very busy developing and pushing out froyo so I don't think releasing updated source code is a high priority for them.
[Galaxy S I9000 Android Development] FadeFx:
sounds possible, but have to set up virtual machine with linux to do so...

also i have to say that i am also not used to such blackbelt stuff, so could be i come back with some questions in the next days... will start tomorrow.
[Galaxy S I9000 Android Development] bilboa1:
actually it's the rom version number

leaked sources aren't samsung releases so they don't "have" to release sources because "they didnt release it" (arguably it's a cheap lie, most of the roms are unlisted available for public download on their servers. unlisted, but distributed - but ok)

but JM1 is official release i think and stuff like battery life works fine, so the source is supposed to be the same

ps: what i dislike with big companies: they would kill you litteraly if you stole their IP (intellectual property) and ask millions of damage. But when it comes for them to respect "the people's" IP, aka no big company behind, they very often barely care enough.. what a world we're living in ;))
[Galaxy S I9000 Android Development] magote:
Looks nice, but I'm going to wait for a version integrated with BackLightNotification :)
[Galaxy S I9000 Android Development] hacksome:
I applied the ext4 one. Quadrant is 804!. Without any lagfix it was 915. Anything wrong.
[Galaxy S I9000 Android Development] RyanZA:
Not possible with this method, it uses the stock kernel.
[Galaxy S I9000 Android Development] dkcldark:
Yeah something must be wrong.. Check if there is a disable lagfix folder in Voodoo folder.
[Galaxy S I9000 Android Development] andars05:
So can I use this on the Captivate by deleting redbend_ua and zImage (and then resigning it)? This is assuming that I am using unhelpful's kernel.
[Galaxy S I9000 Android Development] AV1985:
I have a major problem with this lagfix.

Because of it, my internal memory shows about 10mb free and most of my applications are missing I guess because of lack of space!

Help?!
[Galaxy S I9000 Android Development] dkcldark:
Not for this time.. See what i've changed in the kernel
[Galaxy S I9000 Android Development] dkcldark:
Was there enough space before you started applying this lagfix?
[Galaxy S I9000 Android Development] AV1985:
Note that I had the original voodoo lagfix installed first and used the disable folder method to uninstall it first.

I've tried the same method with this lagfix and it won't go away!

I am using HVJH1 ROM which is 2.1 Eclair, thought it'd work.

I'm just download JM8, any suggestions on how to install cleanly?

And more importantly, fix my memory issue!
[Galaxy S I9000 Android Development] kindaichi24:
same here having memory issue problem.

UPDATE: I FOUND OUT THAT I DIDNT DELETE THE "DISABLE LAGFIX" FOLDER AFTER I DISABLED , THUS I DELETE AND REINSTALL THE UPDATE.ZIP AND NOW THE MEMORY IS BACK.
[Galaxy S I9000 Android Development] Archer13:
You should have enough free space on /sdcard (internal SD) before installing lagfix. This space is used for temporary backup of /data partition during filesystem conversion. If not - conversion process failed somewhere and you will end with ~200Mb /data partition.

"Enough free space" - at least same size as /data partition used size. It's zipped during conversion, but better to have some reserve.

Good luck! :)
[Galaxy S I9000 Android Development] dkcldark:
Seems like the journey from voodoo.beta4 from this lagfix has some trouble... Ill sort this out very soon. Sorry about that guys!
[Galaxy S I9000 Android Development] ufuuu:
At first, I read whole thread and comments like "faster than voodoo" sound exciting :)

I think I couldn't understand about "stock kernel" :confused: I mean, why voodoo lagfix is a custom kernel and yours is stock? (talking about ext4)

And what's the difference between original Voodoo-beta4-GT-I9000-update.zip on voodoo webpage and update_voodoo_ext4_i9000.zip on this thread?

Thanks for your work
[Galaxy S I9000 Android Development] tristecire:
oc 1.2 ghz kernel nilfs2 ?

Hi, and thanks dkcldark, nice work, i like to play !

But there's something i can't understand :

My phone runs 1.2 ghz after flashing your last nilfs2 update.zip

( was on jm8, voodoo B4 with raspdeep oc kernel before )

Nowhere you say anything about oc, so i doubt flashing the update was efficient.

Now kernel says 2.29 jw@jw ubuntu #3

Is it the signature of your nilfs2 kernel ?

Thanks

Edit : I missed to flash your update.zip on reboot.

So, i'm on ext4 and raspdeep oc again.

Sorry. re doing it all ...
[Galaxy S I9000 Android Development] dkcldark:
That's because I didn't compile this kernel but just modified an existing stock JM8 kernel. And this makes some differences. I'm not saying that this must be better than the original voodoo :D. The reason why I'm releasing this is because some people want to use stock kernels.
[Galaxy S I9000 Android Development] dkcldark:
No, that is not mine. There must be wrong with it. Mine says se-s603, which samsung made
[Galaxy S I9000 Android Development] tristecire:
I missed some step

My bad, and sorry.

I've edited my post.

Doing it all again.
[Galaxy S I9000 Android Development] BlockbusterF:
Removed OCLF v2 to try this one out. Works very well till now.
[Galaxy S I9000 Android Development] dkcldark:
It's okay! :D please tell me if it goes wrong
[Galaxy S I9000 Android Development] ufuuu:
So, are you saying no battery drain paranoids should be in this lagfix, since it uses stock JM8 kernel/drivers, etc.. That sounds what I'm looking for :D
[Galaxy S I9000 Android Development] andars05:
I have a request. Could it be possible to integrate this with the reoriented kernel for the Captivate found here:

http://xdaforums.com/showthread.php?t=780732

I would attempt to do it myself, but I'm not nearly knowledgable enough (though I'm always up for learning).
[Galaxy S I9000 Android Development] dkcldark:
No problem. But just wondered that that kernel doesn't seem to be a stock kernel and it wouldn't have any merit integrating this scripts since they are basically minimalised voodoo! The kernel you are showing me does have voodoo as well : )
[Galaxy S I9000 Android Development] eX1337:
Pros and cons on ext4 / nilfs2?

I can apply this on voodoo-beta4, right?
[Galaxy S I9000 Android Development] razedd:
I also may found a bug. At 5-10 minutes or so, 8mb of data is written on the 2gb of internal memory. I am using the nilfs lagfix and I'm coming from a Voodoo kernel(I've disabled the lagfix,then flashed the JM8 kernel and then applied the update.zip)
[Galaxy S I9000 Android Development] andars05:
I didn't notice that it was updated recently. It didn't have voodoo originally :P.
[Galaxy S I9000 Android Development] adrianmak:
How do I use it on my ZSJQ4 stock kernel ?
[Galaxy S I9000 Android Development] joecisd:
thanks for your work

it's really smooth

but i've experienced memory drain

1 min before, there's over 150mb available memory

but suddently, there's only around 50mb available memory

(i've already use task panel to kill the apps)

any hints for this issue?
[Galaxy S I9000 Android Development] ed10000:
I have a problem with the space too. When I installed it, there was 1.53GB free space. This morning, there was 0.97GB free. Now, there's 803MB. How have you configured the Garbage Collector or whatever?..
[Galaxy S I9000 Android Development] Laum:
NILFS2 WILL use all of your free space and after that it starts deleting/writing over the old snapshots. So free space reading will be wrong with it.
[Galaxy S I9000 Android Development] TDO:
Than how can you determine the real free space?
[Galaxy S I9000 Android Development] hacksome:
How is your Quadrant Scores ?!
[Galaxy S I9000 Android Development] Archer13:
~1250 on nilfs2
[Galaxy S I9000 Android Development] dupel:
Well, the main question is - how will it behave once it starts remiving logs.

Anyway, has anyone sucessfully disabled the fix and gone back too voodoo?
[Galaxy S I9000 Android Development] adrianmak:
There are four attachment files which one should I flash ?
[Galaxy S I9000 Android Development] Mopral:
Same issue for me...

Had to reboot my phone...
[Galaxy S I9000 Android Development] StoneRoses:
I'm on JM8 with "Voodoo lag-fix only 3.0".

I'm not sure about what do I need to do to use NILFS2 lag fix?

Method A.

1. disable voodoo lag fix, reboot

2. apply NILFS2 update.zip

Method B.

1. disable voodoo lag fix, reboot

2. flash stock JM8_stock.tar using Odin

3. apply NILFS2 update.zip

Do I need to reflash stock kernel? or NILFS2 update.zip already include JM8 stock kernel?

I ask this question because I don't have Windows machine for Odin flash at the moment.

Thanks for this fix.
[Galaxy S I9000 Android Development] dupel:
I think that after a day of use voodoo = this one. But voodoo does not make logs (which in the end probably will slow down out phones).

Did anyone try the ext4 kernel from here?
[Galaxy S I9000 Android Development] mdalacu:
Hi, where can i find JM8_stock.tar? Is it zImage from CODE_I9000XWJM8.tar.md5. If yes, how can i flash only this with ODIN (without loosing everything) ?
[Galaxy S I9000 Android Development] StoneRoses:
File is on the opening post.

One question about how to disable lagfix.

On Voodoo webpage it said create file or folder name “disable lagfix” in /sdcard/Voodoo

But for this lag fix, dkcldark said create “disable-lagfix” (with hyphen).

Why don't use the same filename?
[Galaxy S I9000 Android Development] crazzym:
It will work either way.
[Galaxy S I9000 Android Development] TweetyPeety:
i flashed my SGS yesterday with NILFS2 and it runs so fast, no Lag, nothing it is really smooth due to the fact that NILFS2 works way better with small files as ext4.

but I got the same problem as many of us with the free space. I think due to the fact that it takes snapshots of itself every minute/second my free space drowns down. I can even click every 30 seconds on Settings / SD Card and see that again 10MB are gone.

can you disable this snapshots because I would love to stay on with NILFS2 and don't wanna go back to ext4.
[Galaxy S I9000 Android Development] Deathlike:
So that means sooner or later we'll start receiving that android message saying our phone's memory is full?
[Galaxy S I9000 Android Development] ashwinds:
Yeah - have the same doubt ... and if anyone has an idea on the battery drain in making snapshots? To me, from what I read, it looks like nilfs2 seems to be doing something all the time :)
[Galaxy S I9000 Android Development] hacksome:
As an experiment, I tried the NILFS fix on a fresh NEW-JM1 ROM. Working butter smooth till now. Quadrant is around ~1400.
[Galaxy S I9000 Android Development] galaxykeks:
seems like that yes...

maybe there can be set a max of snapshots which r stored?

to edit the interval would be great too...
[Galaxy S I9000 Android Development] mekwall:
Hmm... I found this: http://piotr.gabryjeluk.pl/dev:ssd-fses-benchmark-results

I know it's old (and that it's using Bonnie++ to benchmark), but should still be quite accurate. I just hope we'll get the source for 2.2 so we can test this out with Btrfs!

About NILFS2, I'm not yet convinced. I've read alot of posts on different forums where users are having trouble with NILFS2. Fsck not working properly and other bugs. I'm not sure it's stable enough to be used for the SGS.
[Galaxy S I9000 Android Development] ed10000:
I second that - could you disable the snapshot feature completely?
[Galaxy S I9000 Android Development] NeidRider:
+1: disable the snapshot functionality, or enable some max-generations option or something.
[Galaxy S I9000 Android Development] dkcldark:
The garbage collector works as it is supposed to do. Memory wouldn't be full up unless you keep installing and removing the NFS:shift 20time at once. You can have a look at /system/etc/nilfs_cleanerd.conf
[Galaxy S I9000 Android Development] TweetyPeety:
yeah but the problem is that it makes all the time snapshots and that uses battery power and the intern sd which isn't the best, or ?
[Galaxy S I9000 Android Development] spline1:
Yeah we dont need the snapshot functionality :-)

It draws battery and the memory is in 30 minutes from 1100 MB to 600 MB of free and then again to 1000 MB free.

and again and again and again
[Galaxy S I9000 Android Development] distortedloop:
Why don't you ask them for the source code to be released...? :D If they say "no", you've got a point, if they say "yes", question can be answered.

edit: the you in the above paragraph is intended to be the generic you, not you as an individual.

You beat me to the "leaked" vs "official" point. ;)

Also, isn't a large company allowed a "reasonable" time to release the source. I've seen arguments that for a company like Samsung "months" is "reasonable".

With the build dates on most of these leaked things being only a few weeks old, I think you'd have a difficult to defend legal position that Samsung's violating the GPL by not releasing the source on a three week old kernel that was never publicly/officially leaked.

PS. - you got a handy link to the public download servers?
[Galaxy S I9000 Android Development] distortedloop:
So a bunch of people are asking for snapshots to be turned off...

Isn't that the only form of protection against corruption that NILFS provides?

Are we going to devolve into the journaling/non-journaling debate all over again, only this time instead of ext2 vs ext4 it's NILFS-snapshotting vs NILFS-non-snapshotting?

We geeks are never happy, are we? :D
[Galaxy S I9000 Android Development] dupel:
Im no linux guru, but i dont think you can even switch it off. Its kind of whole point of this fs =)
[Galaxy S I9000 Android Development] ed10000:
I disabled the lagfix. How do I flash back the stock JM8 kernel provided in the first post? Fire it up as a PDA on Odin, with NO PIT file selected?

Edit: After removing the .zip from the filename, of course.
[Galaxy S I9000 Android Development] TweetyPeety:
is NILFS2 so corrupted that it needs every seconds a snapshot and every half an hour it kills the cpu usage to 100% for a some seconds ?
[Galaxy S I9000 Android Development] shivankit:
Why don`t we just use YAFFS2

I do not understand why is samsung trying to be smart and using the RFS file system instead of the more popular YAFFS2 system. Can we have a fix that uses the YAFFS2 file system instead of this ****ty RFS system. I think that will unlock the real potential of the phone.
[Galaxy S I9000 Android Development] CazeW:
It's been discussed at least a hundred times already. Try searching. But I'll summarize the result of those for you: Won't work.
[Galaxy S I9000 Android Development] ed10000:
I undid the NILFS2 lagfix, flashed back stock JM8 kernel, and it now reports 19.02MB free.
[Galaxy S I9000 Android Development] dupel:
format data in recovery menu. Did the same (though before flashing)
[Galaxy S I9000 Android Development] kalpik:
Same thing happened wth me for the NILFS version on JM8 (Tayutama rom).
[Galaxy S I9000 Android Development] bratfink:
@OP

Using the same method you have already adopted to recompiling these kernels i have two questions..

1. Doesnt this mean that you technically can use the kernel form JPH and apply your method to make an ext4/NILFS2 lagfix seeing as you dont need the source code?

2. Can you also create an Ext2 version aswell :D?
[Galaxy S I9000 Android Development] dupel:
What im interested in is, why no one tried to impement Btrfs?

It might not be very fineshed, but it is chosen by MeeGo. And despite my love for android meego is the future.
[Galaxy S I9000 Android Development] RyanZA:
I doubt that...

Why? MeeGo is jointly run by Intel. Mobile computing is all about ARM. MeeGo is just Intel's way of trying to get their x86s onto phones somehow. It's not going to work out unless Intel go with ARM - and why would they?

So don't go off talking about the future like it's a definite. :)
[Galaxy S I9000 Android Development] ed10000:
What's the point? I wanted to keep all my apps and date :(. Reflashed JM8.

I had Doc's ROM. Seems there's a problem with custom mods currently. I was able to undo the lagfix successfully on JM8 with no custom ROMs, but the free space went from ~600MB to 19.02MB after the process. Flashing stock JM8 ROM didn't seem to help. Ended up reflashing JM8 entirely.
[Galaxy S I9000 Android Development] dupel:
Emm, n9 which was leaked and releaked that reportedly will launch somewhere in january and runs on arm? Nokia N900 which is avaliable for a year already and is basically MeeGo (you can even download meego on it). Its all arm based.

MeeGo is already (not yet released seriously) but adapted, promised to use by most car manafacturers, device producers, providers, nokia and intel, etc.

And its actually much-much better than android for the simple reason that it does not need any dalvik, etc. Its pure native linux. And if you read coverage and comments by major gadget sites - everyone agrees that meego is the future.

And not to mention that it is expected that intels platform (moon-something) will be faster, better, more economical than arm based.

So yeah, I know what Im talking about.
[Galaxy S I9000 Android Development] distortedloop:
I have no idea if it's that corrupted, but obviously whoever designed it thinks it has the potential to be if it goes to those extremes that are being complained about here (filling up all available space with snapshots, freezing the system) in an effort to prevent data-loss. Either that or it's been poorly implemented. :confused:

That wasn't my point, anyways. It seems like every lag-fix thread devolves into a debate over which filesystem to use; whether it's ext2 vs ext4 or nilfs2 vs ext4, or whatever. One thread to discuss the filesystem religious wars would be nice, leaving the actual fixes published clear of that debate, and more about the fix itself.

To your original question, if your question is based on your experience with this fix, and those are typical results, it sounds very muck like the complaints with other methods (occasional lag/freezes).
[Galaxy S I9000 Android Development] lycosme:
doesn't support 2.2?:(
[Galaxy S I9000 Android Development] mdalacu:
Hi, i am using JM8 with standard Voodoo Beta4 lagfix applied. Can i use directly update_voodoo_i9000_ext4.zip (update.zip) or i should disable the lagfix first?

Thank you!
[Galaxy S I9000 Android Development] RyanZA:
We shall see! If MeeGo isn't sitting at 50% marketshare in 5 years time, I'll come ask you why! :D

The debate over which filesystem to use is kind of important to lag fixes though... I mean the whole point of these lag fixes is changing the filesystem. If we didn't care what filesystem it used, why would the lagfix even matter?!

And nah, these lag/freezes occur right on schedule, and you can watch the nilfs doing the GC when it happens. Doesn't happen often in regular use though. It's just a property of nilfs. :) Increased data reliability through constant backups instead of using journals. It's a different approach to filesystems, and not necessarily worse.

As with early java though, the GC isn't well optimized yet. As with java though, there is no reason the GC can't be optimized to work almost as well as native, while retaining all the cool benefits. :) It's probably the future of filesystems, eventually... (but I don't think it's usable on a phone yet! The big freezes happen at random times (can happen during a phone call, etc) ....
[Galaxy S I9000 Android Development] NeidRider:
I just installed the latest nilfs2-update.zip from yesterday over the existing one, and *BOOM*, all my apps & co are gone...

Any idead what could have caused this? It just sucks...
[Galaxy S I9000 Android Development] benfish:
I had the same problem. :mad:
[Galaxy S I9000 Android Development] mdalacu:
Anyone? :confused:
[Galaxy S I9000 Android Development] kalpik:
Disable lagfix first.
[Galaxy S I9000 Android Development] NeidRider:
I also see some other strange behaviour; formatting DATA doesn't delete everything, e.g. SMS are kept. And the phone doesn't feel as fast anymore.

That's it for me... After some more fiddling around, I couldn't get the phone up to speed anymore and got inexplicable behaviour, so I'm back to Voodoo 3.0 with ext4. Will keep an eye on this project for sure, but at the current state it's just not stable enough for daily use, IMHO.
[Galaxy S I9000 Android Development] cyq1857:
hi,

how can i remove nilfs completely?

there is something wrong with my phone after install nilfs

thank u!
[Galaxy S I9000 Android Development] Mopral:
I use this a little and remove it

Now I have strange issues:

-Wipe data does not work properly from recovery mode

-when I use wipe data from recovery mode, I have first "format_root_device: /dev/block/mmcblk0p2Formating CACHE:..." (do not know if it is normal or not...)

-SGS tools does not work properly anymore (do not know if it is related...)

I try to reflash firmware with Odin (with repartition check) but I still have these issues...
[Galaxy S I9000 Android Development] dupel:
Proper way to remove:

1) create /sdcard/voodoo/disable-lagfix file. I use root explorer.

2) reboot. When rebooted phone will most likely not boot. It will either stay in boot screen for a VERY long time, or stay long time and turn off screen (so only menu buttons light up). In anyway give atleast 30 min for it to work like this (use charger).

3) Using vol up + pwr +home buttons wipe /data and reboot. Not sure if phone will work again or not, but wait here a long time too, just to let it convert everything.

4) Go into download mode and flash stock kernel.

4a) alternativly you might try the original voodoo kernel, as it is has more clever ways of dealing with strange /data types. I recomend it as step 5, not instead of step 4.

It should work (pretty much what I did). If it doesn't - try reflashing your phone completely (without repartition). And as always I do not blame me work bricked phones (though its next to impossible to brick it) and volcano eruptions =)
[Galaxy S I9000 Android Development] cyq1857:
i have another question after install nilfs.

i cannot copy or edit file in /system by root explorer....

is there any solution?

thx
[Galaxy S I9000 Android Development] ed10000:
Are you sure it is in R/W mode and not R/O? Look at the top left in Root Explorer.
[Galaxy S I9000 Android Development] cyq1857:
yeah,i notice that ,i use R/W mode and cannot copy any file to /system .
[Galaxy S I9000 Android Development] dkcldark:
Switch on the r/w button when you are in the root directory
[Galaxy S I9000 Android Development] _JKay_:
I have Voodoo lagfix 3.0 installed on JM8

Whenever I removed the 'disable-lagfix' the lagfix gets installed again!

Can I remove the lagfix completly without loosing my data (without the need to reflash the phone)?

What happends if I try to install this update.zip with the 'disable-lagfix' folder still present?
[Galaxy S I9000 Android Development] kindaichi24:
i follow the instruction on ur 1st post as i used ur previous ext 4 kernel and now my phone just stuck at a black screen after i disable the lag fix. how to solve this???