yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Arise:
System UIDs Inconsistent / I'm Feeling Lucky

Tried to install 0.12 oc over a stock JPA and it took some long time until finished everything. (I took a bath during this time).

When I came back, everything was ok, I tried a quadrant (about 1450 points, kinda low) then I checked the space and had something like 200MB free (I forgot that I downloaded all maps for Sysgic Aura last night, so I attempted the reconversion with some free space missing on SD card).

Anyway...

I tried a reboot and when it finished ... lots of FCs over FCs.

Screenshot attached.

df -h returned this (before this command I did a rm -r on /cache, so deleted some stuff there):

Filesystem Size Used Available Use% Mounted on
tmpfs 171.3M 0 171.3M 0% /dev
tmpfs 171.3M 0 171.3M 0% /mnt/asec
/dev/block/stl9 275.8M 255.1M 20.7M 92% /system
/dev/block/mmcblk0p2 1.9G 303.3M 1.6G 16% /data
/dev/block/stl10 127.3M 8.0M 119.3M 6% /dbdata
/dev/block/stl11 30.0M 152.0K 29.9M 0% /cache
/dev/block/vold/179:1
5.8G 5.5G 242.4M 96% /mnt/sdcard
/dev/block/vold/179:9
31.9M 31.9M 2.0K 100% /mnt/sdcard/external_sd
/dev/block/vold/179:9
31.9M 31.9M 2.0K 100% /mnt/secure/asec

mount gives me this:

rootfs on / type rootfs (ro,relatime)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl9 on /system type jfs (ro,noatime,nodiratime,iocharset=utf8)
/dev/block/mmcblk0p2 on /data type jfs (rw,nosuid,nodev,noatime,nodiratime,iocharset=utf8)
/dev/block/stl10 on /dbdata type jfs (rw,nosuid,nodev,noatime,nodiratime,iocharset=utf8)
/dev/block/stl11 on /cache type jfs (rw,nosuid,nodev,noatime,nodiratime,iocharset=utf8)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
[Galaxy S I9000 Android Development] [Ramad]:
A 2e recovery only wipes /data and /cache on Eclair , you can even do a factory reset on Froyo while having 2e recovery and you will not loose any thing and no setting will be reset.

2e does not touch /dbdata where all of your setting are stored when using froyo. Technically you are only wiping /cache on Froyo, if /data should be wiped then /dbdata should be wiped.
[Galaxy S I9000 Android Development] ragin:
Thanks for answering, I actually DID wipe ALL. Including Cache. See my step by step report in my earlier posts.
[Galaxy S I9000 Android Development] [Ramad]:
If you have a 2e recovery on standard Froyo then try to do a factory reset from phone or recovery, you will see that only /cache and /data are wiped.
[Galaxy S I9000 Android Development] ragin:
Yea, after 50 minutes or so, I first pulled the battery, went into recovery. started saying changing CSC which I hadn't initiated. Again pulled the battery, tried to wipe cache. Got stuck for a further 35 minutes or so. Went into recovery, flashed Docs 8.0.1 back, Again got stuck. Went into recovery, wiped /data factory reset. phone booted with everything intact.
[Galaxy S I9000 Android Development] ragin:
when now I run mount command on my phone, it says relevant partitions are jfs.
[Galaxy S I9000 Android Development] ragin:
& to set things right, the phone again resets to GMT. An annoyance really.
[Galaxy S I9000 Android Development] ragin:
@ nikademus,

http://xdaforums.com/showthread.php?t=845337&page=6

Are these arguements relevent?
[Galaxy S I9000 Android Development] Arise:
Just noticed I'm also on GMT time.

--------------

Later edit: After I've placed my SIM card in the phone seems that I got back on my timezone (GMT+2).
[Galaxy S I9000 Android Development] Freexter:
how is it with the feeling of the phone, snappy?fast?lags?batterylife?

thanks for the answers
[Galaxy S I9000 Android Development] Arise:
I have some sort of question in my mind.

So, to revert back (escape from nikademus JFS kernel :D) one must flash a new rom. At least that is written on the first page.

I saw that on z4mod website there are a couple of scripts to reconvert partitions back to RFS.

http://www.sgscompilebox.dreamhosters.com/downloads.html

Could those scripts work in this case, with a z4mod enabled kernel flashed on bml7 just before this?
[Galaxy S I9000 Android Development] renaud:
This script won't work as is as it only supports ext filesystems. I assume the kernel only supports ext too. It may work after some modifications and with a kernel that supports jfs, like the one from sztupy.
[Galaxy S I9000 Android Development] ragin:
I think its time to make this kernel a bit more easy. If you can add support for applying & disabling this fix on the fly, maybe with a modified CWM, a lot of people would try this out I feel. In this present form, its quite a hassle to remove this fix & go to stock state. Involves a lot of restoring after reflashing a fresh ROM & all that.
[Galaxy S I9000 Android Development] ragin:
@ nikademus,

Do you remove the sim card when you install the ROM & your kernel? I dont, is that why I am having the time issues?
[Galaxy S I9000 Android Development] ragin:
Hi again,

I flashed stock JPO. removed the sim. Flashed your kernel. It booted ok, NO sound in boot animation, time again reset to GMT. Shut down, went into recovery, shows 2e, again -- Applying Multi-CSC... & stuck.
[Galaxy S I9000 Android Development] ragin:
I tried to do a wipe data/factory reset in that state, says,

-- Wiping DATA:...

Formatting CACHE:...

Data wipe complete.

E:Can't mount /dev/block/stl11

(No such device)

E:Can't mount /dev/block/stl11

(No such device)
[Galaxy S I9000 Android Development] renaud:
I don't remove the SIM, but I don't flash through Odin either, I use Heimdall.

The removal of the boot sound is a feature, not a bug, this sound is utterly annoying.

I am still researching the timezone issue.

I am still working a little bit on recovery.
[Galaxy S I9000 Android Development] ragin:
Thanks for all the efforts. I still want to have a workable JFS. :)
[Galaxy S I9000 Android Development] renaud:
Very honestly, for me it is perfectly workable. As I said, I never use recovery and there are simple fixes for the timezone, language reset.
[Galaxy S I9000 Android Development] Arise:
Hi there.

The phone is again in a non usable state.

I was using your kernel 0.12 with the 1.12GHz OC/UV.

Last night I've decided to let my phone charge, battery was at 30%. After I plugged the phone into the wall charger I saw that I could not turn it on!

Removed the battery, let it boot again, everything ok, then I put it again on charge and saw it freeze again!

WTF!

Again, I removed the battery, put it back, let it charge then I switched on the phone. I realy wanted it to charge, I realized there was a problem with charging it while being turned on so I thought about let it start charging off then switch it back on.

So the phone started for the 3rd time, spent some more time on the glowing S, after that the hell started again.

The same "System UIDs Inconsistent" with the I feel lucky button then lot's of FCs over FCs, and as you can see from the picture the phone was in a new fresh state, On screen keyboard settings on the background.

Also, the time was 22:57, but in reality it was 00:57, my phone timezone was back on GMT and it should have been on GMT+2.

So, I could say that the phone on JFS is not that stable as it should, maybe those hard time freezes (not sure the cause, maybe overclocking/undervolting, but never had problems charging with the raspdeep kernel, even when I was using the 1.2GHz kernel) crash something on the JFS hence the "lost UIDs" and the force closes and the time reset.

My conclusion: JFS is stable as long as it doesn't run into troubles, when this happens it goes utterly wrong!

I have my sim card in another phone, the galaxy s is going to stay some time in this state until I can figure out more about this problem, so if you want logs or something feel free to ask!
[Galaxy S I9000 Android Development] renaud:
0.14 is out, it does not clear dalvik cache anymore, so it may be more compatible with DOC rom.
[Galaxy S I9000 Android Development] Arise:
Do you guys still have the file '/data/system/packages.xml' ?

I took a look into /data/system/ and packages.xml is missing from there...

So, I thought I should look for my missing packages.xml file:

# find / -name 'packages.xml'

/dbdata/system/packages.xml

After this I symlinked /dbdata/system/packages.xml -> /data/system/packages.xml

and run sztupy/cyanogen fix_permissions.sh (to run this script is looking into /data folder not /dbdata)

Script from here:

https://github.com/sztupy/android_bootable_recovery/raw/froyo/utilities/fix_permissions

All the permissions with problems seems to have increased with 1 point, so the script is reverting back, like:

Changing user ownership for: /data/data/com.picplz.rangefinder/cache/webviewCache/0bf4a986 from '10125' to '10124'

and

some problems cause system was not mounter rw. After mounting /system rw, run the script again:

Processing (65 of 233): com.sec.android.app.twlauncher...
Changing user ownership for: /system/app/TouchWiz30Launcher.apk from '1000' to ' 0'
Changing group ownership for: /system/app/TouchWiz30Launcher.apk from '1015' to '0'
Changing permissions for: /system/app/TouchWiz30Launcher.apk from 'rwxrwxr-x' to 'rw-r--r--' (644)

and... this ***** still won't work.

In the lolcat I can see

I/PackageManager( 2587): This is first froyo booting for your device, "packages.xml" migration is needed
I/PackageManager( 2587): *packages.xml migration start
D/dalvikvm( 2587): GC_FOR_MALLOC freed 5620 objects / 234520 bytes in 36ms
E/PackageManager( 2587): Error during "packages.xml" migration
W/System.err( 2587): java.io.FileNotFoundException: /data/system/packages.xml (No such file or directory)
W/System.err( 2587):	at org.apache.harmony.luni.platform.OSFileSystem.openImpl(Native Method)
W/System.err( 2587):	at org.apache.harmony.luni.platform.OSFileSystem.open(OSFileSystem.java:152)
W/System.err( 2587):	at java.io.FileInputStream.<init>(FileInputStream.java:82)
W/System.err( 2587):	at com.android.server.PackageManagerService$Settings.<init>(PackageManagerService.java:7960)
W/System.err( 2587):	at com.android.server.PackageManagerService.<init>(PackageManagerService.java:718)
W/System.err( 2587):	at com.android.server.PackageManagerService.main(PackageManagerService.java:675)
W/System.err( 2587):	at com.android.server.ServerThread.run(SystemServer.java:130)
[Galaxy S I9000 Android Development] renaud:
Thanks for the log, I corrected 2 mistakes in fat.format. The new version will be included in 0.15. This is probably why clearing data didn't work in recovery mode.
[Galaxy S I9000 Android Development] spippo:
Come on guys, we have so trust in you all to find a good balance of file system stable and faster for our galaxy s
[Galaxy S I9000 Android Development] renaud:
I would say that jfs is probably the best native filesystem for this device. Low CPU consumption and very good speed.

Although, indeed, I should probably ask z4ziggy to make the update available through z4mod.
[Galaxy S I9000 Android Development] Rawat:
I've noticed that new users can edit their posts, and put in links from there.
[Galaxy S I9000 Android Development] renaud:
I tried this already, it depends probably if you have enough posts.
[Galaxy S I9000 Android Development] Ibanez33:
I have some people edit their post and put the link in the reason for editing I'm not sure if thats what he meant....

Saying that your not that far off the magic number... (well thats if it twelve):)

Edit as below...

!

\/
[Galaxy S I9000 Android Development] renaud:
I sent z4ziggy a PM, let's see how he reacts :)
[Galaxy S I9000 Android Development] CazeW:
That, or like supercurio said you could port Voodoo to use JFS. But I'm happy with either way. :D
[Galaxy S I9000 Android Development] lokhor:
I'm willing to try a JFS version of Voodoo.. after someone else tests it first haha
[Galaxy S I9000 Android Development] huxflux2003:
Enough with the lagfixes guys! Voodoo is almost out and its good. Not to mention that JP6 does not need a lagfix anyway. Spend your time to improve something else. Everyone seems to be working on a lagfix these days. Newsflash: its not July any more! RFS is fixed!
[Galaxy S I9000 Android Development] xvarthx:
I knew it! i said to go for JFS near 1 month ago... the less cpu usage part makes me feel better with my battery life :)
[Galaxy S I9000 Android Development] dcarr622:
We are far from done. Since we can only convert /data, there is still lots of lag while using the phone compared to any other high end device.

The file system is still the biggest problem with the performance of the phone. After that, it's a pathetic browser and poor ram management. I'm praying that CyanogenMod can fix that.
[Galaxy S I9000 Android Development] renaud:
Does JP6 really performs better than JPM filesystem wise?

Also, security wise, RFS is probably not the best FS you would run.
[Galaxy S I9000 Android Development] lokhor:
JP6 does not perform well after installing a lot of apps it is nearly unusable. Voodoo Lagfix is virtually mandatory if you use 100+ apps. RFS is still a pos.
[Galaxy S I9000 Android Development] RyanZA:
Not true, security wise RFS is very good. With full journals stored along side each file, and the sync on close behavior, RFS is probably the safest filesystem I've seen. Gives up a lot of performance for it's structure (two files on FAT32 for every logical file) and far too many fsyncs, but this does give a lot of data security.

As far as JFS goes, it seems a perfect fit for the SGS.
[Galaxy S I9000 Android Development] renaud:
I was talking about permissions security :)
[Galaxy S I9000 Android Development] huxflux2003:
I just wish people worked on other improvements. JP6 with 70 apps here running smooth. And there is also voodoo, just in case... I think some people are becoming dogmatic about RFS. Also there is the issue with nand wear. Samsung suggests RFS for their NAND chips and to be honest I trust them (more than a random guy in a forum at least). No offence, I really admire the work you are doing. I just want you to consider the fact that maybe you are working on a problem that is already solved. Ate you sure that Jp6 is so terribly laggy ?
[Galaxy S I9000 Android Development] dupel:
Installed JPM an it is SO slow with 150 apps, its not even funny.
[Galaxy S I9000 Android Development] renaud:
Well, that's my first mod attempt, but when I get everything right with JFS, you can expect a fully customized build. I am heading towards a fully optimized version which would be flash and forget.

BTW, my mod doesn't wear the internal SD as it uses the external one.
[Galaxy S I9000 Android Development] dupel:
internal sd has hardware level wear protection, so its not a ptoblem.

Maybe you could really do a "voodoo" but only with your fs? I think a lot people would be interested in it.
[Galaxy S I9000 Android Development] renaud:
I am almost done with a first attempt at a kernel mod for it. Direct Odin flash.
[Galaxy S I9000 Android Development] Arise:
ok, flashed your 0.14 (I guess this one is not OC) to get rid of the problems.

Then I copied your corrected version of fat.format in /sbin and rebooted the phone.

I guess I was a bit naive that would work, it seems the old file is again back there. :D

I assume this comes from initramfs at boot and is created each time, so this is the reason why my replacement is not there.

So I have to wait... for your kernel release. :D
[Galaxy S I9000 Android Development] renaud:
Indeed, it's in the initramfs, so that will not do anything.

I have uploaded a corrected fat.format version called zImage.0.15-test for you to test
[Galaxy S I9000 Android Development] Arise:
I had to find a linux to run tar to make the file a .tar file. :D I use odin.

The phone is still in a non-working state. I have lots of FCs, but don't know what to say.

I'll update the post with a logcat in a few minutes.
[Galaxy S I9000 Android Development] renaud:
Well, those FC are most likely the results of a database corruption. The change I made here was only to allow factory reset from recovery.
[Galaxy S I9000 Android Development] Arise:
already tried that, can't wipe/reset in recovery.

Can't mount /dev/block/stl11

btw, if you look into the logs most problems are related to sqlite db access that fails on read-write and then on read only because the file is not there.

I checked some files like:

/dbdata/databases/com.android.providers.contacts/contacts2.db
/dbdata/databases/com.google.android.gsf/gls.db

and those files are missing from their folder. Could this be the result of crashed JFS filesystem or something related to some "don't know how" factory reset?
[Galaxy S I9000 Android Development] Arise:
Ok got bored of the damn FCs. What was really annoying was the permanent vibration occuring each time a new FC spawned.

So... to put an end I did a "rm -r /dbdata/", flashed back the 0.13 version and restored from backup.

Tried to trash it back by setting the Undervolting options back, but it just started charging as it should and no freeze.

Don't know. I'll check it again when phone will reach 50% and 30% battery.

out.
[Galaxy S I9000 Android Development] Allnuts:
The way to be able to wipe/reset is to flash a stock firmware and when the phone boots up /dev/block/stl11 mounted and the phone boots to 3e. Then do wipe/reset/format sd. Then boot up, shutdown, and do a wipe/reset/format sd in 2e. Reboot, pull the battery and flash the stock fw again. Boots up and shutdown and then flash jfs 0.14 or the newest one.
[Galaxy S I9000 Android Development] Arise:
@Nikademus:

Last night did something stupid.

Issues a rm command over the /data folder. In theory that was ok, in practice it seems that this also erased the symlinked /efs folder, so... :D No worries, I had /efs backups. :D

Is it possible to move the efs folder somewhere else in the next versions of the kernel?

I'm not very sure, but I think that some recovery loaders seems to offer the option to wipe the full /data folder, so for future compatibility/git branch joins with those projects moving the symlinked efs folder could be a good choice.
[Galaxy S I9000 Android Development] renaud:
Reformatting the real /efs to jfs is probably not a very good idea. So it has to sit in /data (the largest one), or dbdata or cache.

Anyway, with my kernel, you will not be able to delete efs easily as it's only a copy.
[Galaxy S I9000 Android Development] Arise:
I know /dev/block/stl3 is not mounted, I'm only saying that /data is subject to wiping. :D

Then maybe you can test to see if /data/efs exists, and if not, mount stl3, restore efs in /data then umount back stl3.
[Galaxy S I9000 Android Development] renaud:
That's a good idea, but first boot, rfs modules will be loaded then (which seems acceptable).
[Galaxy S I9000 Android Development] renaud:
0.15 is out with some bugfixes and some security improvements
[Galaxy S I9000 Android Development] super_sonic:
I'll try your new kernel soon: I like jfs but without cwm/recovery nor rfs back, it takes a long time to test others kernels or to test your kernel when using another one.

But thanks for your work.
[Galaxy S I9000 Android Development] renaud:
RFS back is not really a good idea. Some mods are modifying the system in depth, and then you get more and more waste on the system, and thus after some time, you really never test something clean, so you tell "kernel X is bad because it does not work for me, and I had to reflash".

If you want to really test something, you should always use a sane base.
[Galaxy S I9000 Android Development] super_sonic:
Thanks for your answer: today, it's like that I test new kernel with a fresh new stock install before... But after too, I reinstall stock kernel... It's take a long time! What about cwm?
[Galaxy S I9000 Android Development] jsen:
Thanks for this.

Using it with Doc's BUJP8 v9 rom.

Was from ext4 (YA-OK) and decided to give this a try.
[Galaxy S I9000 Android Development] x86-Dark:
I want to try this kernel, but i've intalled the K9 SpeedMod, can i flash this over the K9 kernel?

thx
[Galaxy S I9000 Android Development] renaud:
As long as all lagfixes are disabled before installing, it should be safe.
[Galaxy S I9000 Android Development] Arise:
Hi there. Just found a stupid bug.

Tried to download for a couple of days from market and failed. Today just took a look into the logs and saw the error:

DownloadManager | download aborted - not enough free space in internal storage

tried a df -h, had plenty of space on all partitions.

Then it hit me. There is no /cache partition mounted!

I'm running your latest oc-kernel. Upgrading to your latest kernel should fix the problem for good?

BTW, 0.16 is not there yet...
[Galaxy S I9000 Android Development] Arise:
Just flashed 0.15 and I still don't have a /cache partition mounted...
[Galaxy S I9000 Android Development] Arise:
cat /jfsmod.log

processing started: 11/27/2010 22.41.47
The current device is: /dev/block/stl11

The superblock does not describe a correct jfs file system.

If device /dev/block/stl11 is valid and contains a jfs file system,
then both the primary and secondary superblocks are corrupt
and cannot be repaired, and fsck cannot continue.

Otherwise, make sure the entered device /dev/block/stl11 is correct.

/sbin/jfs_fsck version 1.1.14, 06-Apr-2009
[Galaxy S I9000 Android Development] renaud:
This is strange. Try to do "mkfs_jfs /dev/block/stl11" as root. And then shutdown and restart the phone.
[Galaxy S I9000 Android Development] Arise:
Hi there. Too late, lost my patience.

It was strange. I tried all night to fix it, but got no ideea how to fix it, so in the end I've reflashed a new firmware with Odin. Kinda gave up... :(

I think I was a bit in a rush when I said this is a bug in your kernel, don't know what to say exactly, maybe I was missing the /stl11 partition before applying your kernel.

I tried universal kernel to have access to CWM recovery and try to delete/erase the /stl11 and in vain.

So, in conclusion /stl11 was something undefined in my system, a device that was not properly defined and this was the problem. Like I said don't know if this is related to your kernel...

I tried mounting:

mount -t jfs -o rw,noatime,nodiratime,iocharset=utf8 /dev/block/stl11 /cache

mount -t rfs -o nosuid,nodev,check=no /dev/block/stl11 /cache

and both commands failed.

I had the /cache folder in the root, but /stl11 was not mounted to it. Also tried to mount root in rw and create a new /cache2 folder but also couldn't mount to it.

So... Odin with repartition solved the problems.

Forgot the most important detail:

Before repartion I've tried to fix it with Odin writing only the cache.rfs file. And Odin said everything was ok, but again I couldn't mount. And tried to write a zImage (universal) and cache.rfs and Odin again told me everything went ok, but when I went in clockwork recovery/e2 recovery I wasn't able to umount/clear cache partition.
[Galaxy S I9000 Android Development] Freexter:
just installed it on a fresh JPO

working good

only thing is all that **** thats is coming with samsung nobody needs

so i guess it would be the best to pack this kernel in a clean up ROM

but good work thanks
[Galaxy S I9000 Android Development] Arise:
You can always remove samsung apps by hand.

Forgot to report/confirm, the kernel works fine on jp7.