yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] the_ozyrys:
OK, I will refrain from trying to understand how filesystem type affects sound file reading. ;)

Actually, I have 154MB of free space on /system; wanna buy some? :D
[Galaxy S I9000 Android Development] DamianGto:
no its strange.

well if you have a custom.Rom you can have alot free space.

**DamianGTO Steam kernel. 350MB Ram. 500HZ. ext2/jfs . js3 base**
[Galaxy S I9000 Android Development] renaud:
Actually, this is not a filesystem problem, it's in the way samsung checks for media files. I still haven't understood what is the real cause behind that.
[Galaxy S I9000 Android Development] renaud:
I would really like to understand why some devices give problems and others not. I would also suspect some differences in the ROMs.

For those who have the UID problem, could you send me the location of the packages.xml file.

adb shell
find / -name packages.xml

And I would also like to see /fugumod.log

adb pull /fugumod.log .

Thank you
[Galaxy S I9000 Android Development] renaud:
0.36 is out, it tries to solves the UID problem which occurs on some ROMs/devices
[Galaxy S I9000 Android Development] the_ozyrys:
For me it's in /dbdata/system.

As for log file, I'll try to find time to flash FuguMod once again today.
[Galaxy S I9000 Android Development] renaud:
l found a bug in the permission fixing. I am working on it.
[Galaxy S I9000 Android Development] renaud:
0.37 is out, this is purely a bugfix to definitely solve the UID problem. Expect longer boot times.
[Galaxy S I9000 Android Development] Daneshm90:
That it does.

Use to have uid problems and was never able to give jfs a shot (on any kernel)

But now im a happy jfs user :)

i9000M
[Galaxy S I9000 Android Development] matticala:
I know you will hate me for this but... Just flashed 0.37 and waited for boot/fs-convertion and the first message after the welcoming fugu was a "UID inconsistency".

Rebooted in recovery, checked "fix permitions" and rebooted again. Same UID warning.

I still believe it's a problem with jfsutils. Same thing happened when i first flashed Darky's 9.2 with speedmod and JFS, after I had wiped data all went smooth.
[Galaxy S I9000 Android Development] renaud:
I don't hate you :)

You should not fix permissions in cwm, rebooting should be enough and even safer. Try rebooting normally first, I found bugs in cm permissions fix
[Galaxy S I9000 Android Development] matticala:
Nothing happened :(

EDIT: Could it be referred to apps on SD card instead of internal memory?

EDIT2: Moved all apps from sd to internal and rebooted, still getting UID inconsistency :S
[Galaxy S I9000 Android Development] renaud:
Can you give me some logs? /fugumod.log

Thanks
[Galaxy S I9000 Android Development] matticala:
Attached ;)

It seems all regular anyway, it tries to fix anything wrong.

/mnt/asec/ is app2sd storage, I wonder if that's the problem. It is perhaps better not to have external sd / app2sd on when enablig lagfixes/partition convertions
[Galaxy S I9000 Android Development] renaud:
Well, the SD apps don't get fixed, but this is normal. So if you still get UID errors with 0.37, it's either caused by apps on the SD (which can be solved by putting them on /data and rebooting) or corruption in system apps, which is almost impossible if fugumod converted the filesystems itself.

How did you convert to jfs? using steam or whatever jfs enabled kernel?

Also, how did you flash darky rom? from DOC or another rom? with or without wipe?

When trying 0.37 version, I did random chown, chmod against /data applications and it got corrected after a reboot.
[Galaxy S I9000 Android Development] matticala:
I made a full Odin flash from stock JS5, then flashed speedmod kernel from odin ad uploaded Darky's 9.2 on internal SD. From Recovery I did install the custom zip and rebooted.

Darky's converts filesystems to Ext4, so i rebooted again in recovery and disabled lagfixes... after that, with all rfs, i installed your kernel :)

I'll do a wipe in the end

UPDATE: Reboot in recovery -> mount data -> wipe data -> wipe cache -> reboot -> Still UID inconsistent! Now this is weird, it actually didn't wipe it at all!
[Galaxy S I9000 Android Development] renaud:
Could you do

adb root
adb shell
/sbin/fix_permissions

while the system is running and send me the screen output?
[Galaxy S I9000 Android Development] matticala:
Wiped already, i'm going to put your kernel on stock JS5 ROM. If corruption happens again I'll send you that output
[Galaxy S I9000 Android Development] renaud:
I feel that what you are experiencing is a double install of some program, both in system and in data. Apart from the popup, when you are clicking on "I am feeling lucky", does the system work globally, or only some random apps are not working?
[Galaxy S I9000 Android Development] matticala:
Ok, this is what I did this time, step-by-step:

Flashed FULL JS3 with re-partition enabled -> reboot

Flashed FuguMod 0.37 with Odin -> reboot

Waited for Fugu to convert partitions -> NO UID problems.

(at this point i noticed it reverted system language back to dutch, discarding my previous set to italian)

then:

Rebooted in recovery and installed Doc's 9.6 with SpeedMod kernel

Rebooted again in recovery to check partitions, since flashing a ROM formats system. At this point I'm on SpeedMod. It cannot detect what filesystem it is on. It can flag system for a repartition, but once i checked "disable lagfix" recovery stuck -> battery pull

Reboot in download mode to flash FuguMod again -> reboot

System loaded with UIDs inconsistency and no Home Screen (Doc's 9.6 bug?)

Again:

Reboot in recovery

Install zip from SD card -> Darky's 9.2 ED

Installation failed with error: copy_dir PACKAGE:system SYSTEM:

Installation aborted

It looks like there is some kind of taint on system partition when installing a ROM over Fugu. To update, it is needed either the rom hasn't a different kernel or it shouldn't format system (at this point I don't know how the rom formats system).
[Galaxy S I9000 Android Development] Arise:
Why would you write a Speedmod kernel if it does not works with JFS filesystem?
[Galaxy S I9000 Android Development] DamianGto:
you can't blame fugumod for your lack of reading skill.

speedmod don't support jfs file system.

if you had read you should know that.

you should have put fugumod kernel in that rom and used that.

**DamianGTO Steam kernel. 350MB Ram. 500HZ. all ext2. Steam Rom. Js5**
[Galaxy S I9000 Android Development] renaud:
I think the best would be to put FuguMod in an update.zip instead of the cooked one.

To be honest, when I flash ROMs, I do it in recovery with a root shell:

http://www.llorien.org/samsung_galaxys/doc_update-script.txt
[Galaxy S I9000 Android Development] matticala:
SpeedMod DOES support JFS. Anyway it comes bundled with any custom ROM you flash, I cannot avoid it; or better, I could remove the kernel from the ROM, but I should then modify scripts included and re-hash the package
[Galaxy S I9000 Android Development] matticala:
I'm not blaming him of course! I'm trying to figure out, with him, why the system taint happens when it shouldn't and why it didn't get fixed.

For istance, it came out with app2sd...

If I gave nikademus the feeling I'm blaming him I'll excuse right now, it wasn't my intention. Sorry.
[Galaxy S I9000 Android Development] DamianGto:
well then he just put that in. he did not support it before.

**DamianGTO Steam kernel. 350MB Ram. 500HZ. all ext2. Steam Rom. Js5**
[Galaxy S I9000 Android Development] renaud:
It's not in current features as far as I can read. I think speedmod used to support jfs in the past, but does not anymore (not 100% sure tough).
[Galaxy S I9000 Android Development] matticala:
It's in the advanced convertion options. I used to have:

System: Ext4 (only option available)

Data: JFS

Cache: ext4nj

dbdata: JFS
[Galaxy S I9000 Android Development] renaud:
Only steam kernel has proven to be fully jfs compliant and compatible yet.
[Galaxy S I9000 Android Development] renaud:
0.38 is out with some improvements on read speed and a change to give more chances to flush pages to disk.
[Galaxy S I9000 Android Development] x86-Dark:
This kernel is symply awesome! IMO the speed is better than Speedmod K13A (with all tweaks/lagfix) and no problem so far!

Thx man!
[Galaxy S I9000 Android Development] renaud:
Thank you
[Galaxy S I9000 Android Development] ragin:
Not anymore, speedmod doesn't have an option of JFS at all in advanced options.
[Galaxy S I9000 Android Development] Freexter:
Im on speedmod k13a and i have jfs for data/cache/dbdata

i converted filesystem in k13a
[Galaxy S I9000 Android Development] x86-Dark:
Hi guys!

I want to update my Doc's Rom JS3 9.1.4 with the latest JS5 9.6.6 without wiping everything.

Can i replace the zImage inside the Doc's rom CWM package(docsrom.zip/updates) with the FuguMod inside your Odin package(zImage-current.tar)?

Because i am with your kernel atm, and i dont want do all the steps for convert/reconvert/flash/wipe (jfs>stock rom>cwm kernel>flash new rom>flash jfs kernel). It will take too much time.

thx
[Galaxy S I9000 Android Development] renaud:
This hasn't been tested but it should work
[Galaxy S I9000 Android Development] Freexter:
i tried your kernel with insanity 0.5.3 but it was stuck on bootscreen.i know it can take a while to convert filessystems but i saw the bootscreen for about 40 minutes.what could be the problem?
[Galaxy S I9000 Android Development] Xacky:
Already tried a factory reset? Thats the first advice when in a bootloop
[Galaxy S I9000 Android Development] franksames:
I tried your Kernel with Darky's 9.3 beta and work without problem.

I tried also to revert back by use of Steam kernel, as well no problem at all.

And than revert to Speed Mod kernel, also no problem.

Now I'm back to your Kernel and will test it for some days, as I like the idea of JFS system. Great work.
[Galaxy S I9000 Android Development] Freexter:
after reflashing js3 and then insanity.i tried it again and it works.so cool :)
[Galaxy S I9000 Android Development] x86-Dark:
It worked without problems! :D

So if you want to update your first post with a little guide that explains how to replace zImage between rom's and kernel's packages , i think a lot of user might find it very useful! ;D

bye!
[Galaxy S I9000 Android Development] scheichuwe:
I'm having problems to get this kernel working...

What I did:

I was on Doc's JS3 (I don't remember version, 9.x) with Speedmod 13B-Kernel.

I disabled lagfix so all partitions were on rfs again.

Flashed FuguMod 0.38 using Odin -> nice fish (for about 25 minutes). Canceled.

Then I flashed a fresh JS3 using Odin, did a factory reset (rebooted, all worked fine) and flashed FuguMod -> the fish again (I waited 40 minutes!)

So, what am I doing wrong? :)

I have no apps installed (->factory reset) and about 3,5 GB free space on my internal sdcard.
[Galaxy S I9000 Android Development] [Ramad]:
Your device is not partitioned as 512.pit but as 803.pit or 513.pit right?
[Galaxy S I9000 Android Development] scheichuwe:
No, last time I clicked re-partition, I used 512.pit...

But anyway, I'll try that once again.
[Galaxy S I9000 Android Development] renaud:
I found another bug in the permission fixer. This is due to the way samsung "improved" speed in 2.2.1.

It is currently being worked on.
[Galaxy S I9000 Android Development] renaud:
0.39 is out

It is highly recommended that you upgrade to this version if you ran any previous ones. It should fix the application preferences lost issues some people may have seen.
[Galaxy S I9000 Android Development] franksames:
Just saw this. It should no problem with partitioned PIT 803.

I use always partition PIT803 and do not have any problem
[Galaxy S I9000 Android Development] renaud:
0.40 is out with a little bit more voltage for the CPU to help solve lower quality hardware issues

I/O scheduler is now again deadline to keep more write consistency
[Galaxy S I9000 Android Development] ragin:
Hi again.

I now have Stock Deodexed JS5 with SpeedMod k13c. Do you see any problem if I flash this over? Thanks.
[Galaxy S I9000 Android Development] renaud:
It should work, however some people reported failures after having installed speedmod.
[Galaxy S I9000 Android Development] ragin:
Just flashed your FUGU & am seeing a Bright Red Fish, report back later.
[Galaxy S I9000 Android Development] ragin:
How long do I have to wait?
[Galaxy S I9000 Android Development] renaud:
I depends on the number of apps you have, if it's a custom rom, etc. It may take 10 min.

If it fails, please flash a full clean ROM, flash fugumod, then use cwm no wipe to install the theme/rom you want.

Fugumod is available on romkitchen beta.
[Galaxy S I9000 Android Development] ragin:
I have 180+ apps & thanks for helping me along, I now see flashing S logo as I type.
[Galaxy S I9000 Android Development] ragin:
And look what I have!!! A foreign language that I can't make out. ROFL.

PS : How do I begin to use this phone nikademus? :D

PS2 : Clicked on some hunches & have English now. Don't tell me you have set wierd tones for different notifications. I am about to go to sleep beside my wife now. :D
[Galaxy S I9000 Android Development] renaud:
Well, if it's the stock XWJS5 that is on samfirmware, it' probably dutch, please read first post to see how you can force language.
[Galaxy S I9000 Android Development] ragin:
Ok, I change the language & the time. Now when I restart my phone, both are not saved.
[Galaxy S I9000 Android Development] renaud:
Did you read the first post as I suggested?
[Galaxy S I9000 Android Development] ragin:
Yep, read it. Now what would be the correct settings for India? Can you help me?
[Galaxy S I9000 Android Development] renaud:
I would say:

persist.sys.timezone=Asia/Kolkata

persist.sys.language=en

persist.sys.country=IN

See: http://en.wikipedia.org/wiki/List_of_zoneinfo_timezones
[Galaxy S I9000 Android Development] ragin:
/system/default.prop contains

ro.com.google.clientidbase=android-samsung
[Galaxy S I9000 Android Development] renaud:
Strange, it should contain a little bit more, but anyway, all you need to do is append the locale data to the file.
[Galaxy S I9000 Android Development] Prasad:
How do I disable the lagfix and convert filesystem back to RFS, so that I can safely switch to another kernel? :)
[Galaxy S I9000 Android Development] DamianGto:
Flash steam kernel. :-)

**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
[Galaxy S I9000 Android Development] Prasad:
Will do :) thanks!
[Galaxy S I9000 Android Development] renaud:
0.41 is out, it implements compcache (also known as ramzswap)

note that you will _not_ see /dev/ramzswap0 if you log in with adb, but it is used nonetheless.
[Galaxy S I9000 Android Development] renaud:
0.42 is out to update BLN, so you can now get blinking but it's not enabled by default, you need the BLN app to enable blinking.
[Galaxy S I9000 Android Development] renaud:
This kernel can now also be flashed with DOC ROM in http://romkitchen.org thanks to Stefunel
[Galaxy S I9000 Android Development] x86-Dark:
Wonderful news! :D
[Galaxy S I9000 Android Development] renaud:
1.0 is finally out
[Galaxy S I9000 Android Development] ragin:
congratulations on going GOLD.
[Galaxy S I9000 Android Development] DamianGto:
Congratulations on your version 1.

**DamianGTO Ultimate kernel.1200MHZ. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
[Galaxy S I9000 Android Development] ragin:
Long time ago, you went from 0.9 to 0.10, I remember asking you if you had done a numbering mistake, you said NO, this kernel still needs development. I love the way you have committed to the development of this kernel & finally is able to post a 1.0.

PS : Thanks for taking my small suggestions along the way, Naming your ROM, Cross-Kernel compatibility, CWM in recovery etc.,
[Galaxy S I9000 Android Development] fake01:
Any way to flash to another rom.

I tried flashing this using custom rom from Docs Rom Kitchen, however it's stuffed up my phone. It got stuck on a red blower fish for over 30 minutes. Restarted the phone and reflashed and it went through however all I get is a blank screen that keeps vibrating.

I also keep getting a message E:Can't open /cache/recovery/log in recovery mode.

So I would like to switch back to speed mod, anyone know how I could do this, as I can no longer get access to the SD card to swap over the files.
[Galaxy S I9000 Android Development] renaud:
1.1 is out with new smaller jfsutils binaries and new busybox 1.18.3 which is also smaller. Kernel is now 5.2Mb instead of 5.4Mb.
[Galaxy S I9000 Android Development] renaud:
Did you remove all the lagfixes before applying the kernel? It looks like your system is corrupted.
[Galaxy S I9000 Android Development] fake01:
I had no lag fixes active upon applying this kernal. I was using RFS. As I have 2.2.1 firmware I didn't bother with using EXT4 as there was little improvement.

I deleted everything on the phone and did a wipe/factory reset as I usually do.
[Galaxy S I9000 Android Development] renaud:
Since you used romkitchen, did you use a wipe rom or a non wipe one?
[Galaxy S I9000 Android Development] Mothatt:
Sweet kernel, thanks for all your hard work on this :)
[Galaxy S I9000 Android Development] fake01:
XWJS5 v9.6.6 WIPE
[Galaxy S I9000 Android Development] fackamato:
Compcache? I didn't know that Android used swap. Does the kernel make use of compcache as well, or is it just support added for it?
[Galaxy S I9000 Android Development] renaud:
Well, as written on the first post, you should really use a non wipe ROM. I will ask Stefunel to put it on the romkitchen too.
[Galaxy S I9000 Android Development] renaud:
The kernel create one compcache device which it uses. This is the only one used. Unfortunately, due to the init by samsung, you don't see the actual device in /dev unless you do a mknod before. Samsung init seems to wipe /dev and recreate what it knows, but the device is initialized before the /dev entry is removed and it works even if you don't see it.
[Galaxy S I9000 Android Development] renaud:
Great, I will have a look
[Galaxy S I9000 Android Development] renaud:
I will probably look at this, this is a little bit more complicated with jfs tough.
[Galaxy S I9000 Android Development] sztupy:
I already included JFS support in the ULTK. People usually complain that using jfs the timezone settings resets after each reboot and that you can't clear the application data using Settings/Applications. Strange that these things don't appear if using ext4 or rfs.
[Galaxy S I9000 Android Development] zenkinz:
not sure about the app data problem, but I never have problem with timezone setting, I use auto time (based on network value) though.

also, I tried jfs and ext4, it looks like jfs will have some stuttering intermittently, ext4 seems to be smoother and I don't notice too much diff in battery (just to correlate to the cpu usage).

might just go back to ext4 ..
[Galaxy S I9000 Android Development] renaud:
I am running voodoo lagfix with ext4 this WE, and it seems to drain battery more than jfs does. Also benchmarks seem more constant with ext4 than with jfs, but it's hard to tell as I do use my phone as a normal user, not just to run benchmarks.

The biggest problem with jfs being its write journal when you have time, which seems to give problems on the SGS with it's crazy policy of not unmounting properly on shutdown. This does not really make a problem if you use the lagfix script, but it does if you run it natively from the init.rc.
[Galaxy S I9000 Android Development] renaud:
I made (but not tested yet) reiser4 modules, so for people who want it, they can try it at http://llorien.org/samsung_galaxys/jpm/reiser4
[Galaxy S I9000 Android Development] ed10000:
Why isn't it a problem when using the lagfix script? It still doesn't unmount properly on shut down right?
[Galaxy S I9000 Android Development] renaud:
Since it overmounts /data,the behavior may be very different.
[Galaxy S I9000 Android Development] Arise:
Some people (me included) would like to try things on an external SD card, not the internal memory.

Two reasons for this:

-maybe an external card can provide superior speed over the internal memory (if the card speed is not bottlenecked by the hardware interface).

-flash memory wear, I would rather kill my external SD card rather my whole phone. :P

Voodoo is a great lag-fixer targeted at masses, but for few people that don't mind keeping the external sd card always in the slot this mod would be a nice try.

BTW, I have great hopes related to this "jfs mod lagfix". Using it or some parts of it, with a proper OC/UV froyo kernel I hope to break through 3k (yeah, three) barrier in Quadrant.
[Galaxy S I9000 Android Development] renaud:
The biggest problem is that I only have a class2 SD, so if someone could try with a class10, that would really be great.
[Galaxy S I9000 Android Development] spoidar:
Almost certainly with a class 10.

Except the internal flash has hardware wear levelling, unlike your external SD.

Apparently people testing JFS with sztupy's (awesome) kernel have found it to be a less consistent performer than EXT4 due to the delayed journal writes, which flog the storage from time to time...
[Galaxy S I9000 Android Development] sztupy:
This is the main point on using a HDD filesystem instead of a flash based one.
[Galaxy S I9000 Android Development] renaud:
Now, very honestly, I have been running systems out of flash cards with an ufs filesystem on them and with system logging enabled and I haven't got more problems than with spinning hdd systems. In fact I even had less problems than with spinning hdds. I think wear is clearly overstated, you will have replaced your system way before your flash card is worn out.
[Galaxy S I9000 Android Development] exadeci:
And what is the main reason for not using Yaffs or Logfs ? Both flash File System ?? (Yaffs being google choice)
[Galaxy S I9000 Android Development] spoidar:
YAFFS requires a raw flash device, but on the Galaxy S the storage is presented via an SD (block device) interface, so it's not possible.
[Galaxy S I9000 Android Development] sztupy:
Yaffs is actually not that fast, so it's usage would be kinda useless here.
[Galaxy S I9000 Android Development] renaud:
I updated my page, now all kernel modules there are about 10% of the size of what they were.
[Galaxy S I9000 Android Development] Arise:
So far there is no evidence that embeded hardware wear-level is activated and working for the internal memory.

I'm not saying that RFS is any good for wear leveling or there is some hardware algorithm that takes care on the internal sd cards.

Until proved I would say is the best to make experiments (like benchmarks) on external storage.

I don't believe that there is any true class 10 micro SD available on the market, but for pure numbers we can always try some normal SD cards. Class 10 or class 6 from Sandisk, featured as a 30MB/s sustained write speed would be great to find out if there is any bottleneck.

I've seen that some people got impressive speeds on the G1 unit using some fast Sandisk microSD cards, but I got no ideea the controller on Galaxy S is capable for.
[Galaxy S I9000 Android Development] dupel:
Emmm, it is proven many months ago?
[Galaxy S I9000 Android Development] sztupy:
1. It's included in the specification of the hardware

2. You can check that there is actually less space avialable for the stl devices than for the bml devices, the extra space is used for the wear level data, and you can also see that data distribution is equal.

3. If you modify the bml data directly you'll lose the stl devices until a next re-partition

4. Wear leveling is only active for /system, /efs, /data, /dbdata and /cache (no wear leveling for the bootloader, kernel, modem driver, etc.)
[Galaxy S I9000 Android Development] Arise:
Not always the latest version of busybox is the best.

I've found out that some new versions miss important parameters like wget or tar with zip compression.
[Galaxy S I9000 Android Development] fake01:
I see, any way I can get my phone back in order to give it another go?
[Galaxy S I9000 Android Development] renaud:
I do compile my own, I don't take a precompiled one. This one has wget and tar with gz and bz2. It also has a working "less".