yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] sl8125:
Busybox df -h

I have done formated my sd card with 900mb of Fat32 and 1gb of ext4. After installing into the phone, i wanted to check if the sc card is mounted correctly. however, when i run the command "busybox df -h" I see everything accept the following line.

/dev/block/mmcblk1p2 957.4M 123.1M 785.6M 14% /disk

Did I not partitioned my sd card correctly? I used Paragon Hard Disk Manager V.10 to partitioned the sd card. I can't seem to have the sd card show up.

Any ideas why? would appreciated if you can let me know.
[Galaxy S I9000 Android Development] Darkstriker:
You either partitioned incorrectly or you didn't properly apply the kernel from post 1.
[Galaxy S I9000 Android Development] brisandroid:
I currently have JG5 and am running the lag fix all with no problems.

What I'm wondering is, if I want to update to JM1, do I need to re-apply the lag-fix afterwards, or can I just reflash?
[Galaxy S I9000 Android Development] T0N3Z:
i have done everythingggg......like literally everything!!!!

and still caant get this fix to work!!!

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

and thats it!
[Galaxy S I9000 Android Development] sl8125:
I have not applied the kernal yet. I am assuming you need to have this done in order for you to see it on the adb screen. Sorry still little knew to this. Thnx for your help.

Applied the Kernal. It rebooted just like how it said it would. but still can not see disk. Please see below. Maybe i didn't format the sd card correctly. Is the phone going to be okay til i make the change on the card. Cause my adaptor is at work. can't get to it tonight. Shucks!.

# busybox df -h

busybox df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 162.8M 0 162.8M 0% /dev

df: /mnt/.lfs: Function not implemented

tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals

/dev/block/stl9 275.8M 226.0M 49.8M 82% /system

/dev/block/mmcblk0p2 1.9G 195.9M 1.7G 10% /data

/dev/block/stl10 127.2M 10.4M 116.8M 8% /dbdata

/dev/block/stl11 30.1M 1.5M 28.5M 5% /cache

/dev/block/stl3 5.9M 4.0M 1.9M 68% /efs

/dev/block//vold/179:1

13.4G 144.7M 13.3G 1% /sdcard
[Galaxy S I9000 Android Development] lenrek:
After you had made the partition, did you format the partition?

Do not format the SD card with your phone! It would wipe out the partition you had created.
[Galaxy S I9000 Android Development] lenrek:
I think the partition in the external SD card is not properly formatted.

The phone should be fine, but since you did not create the filesystem and copy the /data/data to /disk/data, you won't be benefited of the speed improvement.
[Galaxy S I9000 Android Development] lenrek:
The steps should be:

1) Start Odin

2) Start SGS in recovery mode

3) Connect the USB cable.

Do not connect the USB cable before you start Odin or before you had set SGS in recovery mode.
[Galaxy S I9000 Android Development] sl8125:
okay another step i missed. i must of read the thread couple of times but still missing steps. Sorry guys but i do appreciate your help.

So i need to reformat the FAT32 partition correct. How about the EXT4 partition. What page was this info at? Such a NOOB.

I don't have a SGS i9000. I don't see anyone at captivate forum reall post a good thread as of yet. i am hoping that i can get this done and hopefully i could make a thread for our guys too. KEKE. I don't want only u guys to have fun. We are getting jealous how you guys show up with these benchmark scores going through the roof. LOL. Thanks for your patiences.
[Galaxy S I9000 Android Development] sl8125:
Originally Posted by T0N3Z

i have done everythingggg......like literally everything!!!!

and still caant get this fix to work!!!

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

and thats it!

I think i have an idea what he is not doing. He might of not inserted the PIT file. I was in the same shoes. I waited and waited and waited and chit didn't happened. Try inserting the Kernal file in the PDA section and the odin.PIT file on the PIT section. I used the one ending 2. Of course i haven't successfully completed the process but. I was where you are now.
[Galaxy S I9000 Android Development] lenrek:
Someone did a summary of the steps here:

http://hemorrdroids.net/?p=637

By the way, from what I had read so far, it seems those who are having problem after they format the filesystem are using partition > 2gb for ext3/4. So, partition it < 2gb. Mine is just 1gb.
[Galaxy S I9000 Android Development] sl8125:
These are my properties of each drive from Paragon Hard Disk Manager. I formatted each drive. Still my phone is not detecting the disk drive. It won't even show up in the Setting-USB Setting. It just won't detected at all.

Volume letter:(I:)

Volume label:NEW VOLUME

Type:Primary

File system:FAT32

Sectors per boot:38

Sectors per cluster:8

Serial number:B425-8600

Partition ID:0x0B FAT32

Volume size:902 MB

Partition size:902 MB

Used space:1.7 MB

Free space:900.2 MB

Active:No

Hidden:No

Volume letter:(*)

Volume label:NEW VOLUME

Type:Primary

File system:Linux Ext4

Sectors per cluster:8

Serial number:1665-61E3-686A-A368-3A13-8C46-1A46-B6BC

Partition ID:0x83 Linux Native

Volume size:1011.9 MB

Partition size:1011.9 MB

Used space:33.1 MB

Free space:978.7 MB

Active:No

Hidden:No
[Galaxy S I9000 Android Development] sl8125:
double post.
[Galaxy S I9000 Android Development] lenrek:
Run the following command:

prompt> adb shell dmesg > dmesg.log

Use your word processor and open dmesg.log. Search for EXT4. Check if there is any warning/error messages.

For mine, since is working fine, I would see:

<6>[ 5.797591] EXT4-fs: barriers enabled
<6>[ 9.307081] kjournald2 starting: pid 2160, dev mmcblk1p2:8, commit interval 5 seconds
<4>[ 9.313501] EXT4-fs warning: maximal mount count reached, running e2fsck is recommended
[B]<6>[ 9.818035] EXT4 FS on mmcblk1p2, internal journal on mmcblk1p2:8[/B]
<6>[ 9.822665] EXT4-fs: delayed allocation enabled
<6>[ 9.827167] EXT4-fs: file extents enabled
<6>[ 9.831355] EXT4-fs: mballoc enabled
<7>[ 9.834721] ext4_orphan_cleanup: deleting unreferenced inode 549
<6>[ 9.834814] EXT4-fs: mmcblk1p2: 1 orphan inode deleted
<6>[ 9.839837] EXT4-fs: recovery complete.
<6>[ 10.412590] EXT4-fs: mounted filesystem mmcblk1p2 with ordered data mode

You can safely ignore the warning of maximal mount count reached.

By the way, did you flash the correct kernel image?
[Galaxy S I9000 Android Development] sl8125:
Just opened up the command prompt. got in the SDK. type in adb shell dmesg > dmesg.log. it kept repeating shell dmesg. Sorry. be patient with me. Noob. so typed in adb shelll dmesg and all sorts of chit came up but not the what you posted above.

so i redownloaded the kernal. it was the same kernal. check the phone the kernal now shows "2.6.29 root@ubunto #1".

When i start my phone, "removed external card" appears. It will not even detect in phone mode nor usb mode when i connect to cpu. However, take the card out and then use in the thumb drive adaptor it detects. is there something with the phone. now. when i partition the drives and install the first time, the phone as to format the external drive but i did not format on the phone since it formats all drives in FAT32. Arghh... So frustrating.
[Galaxy S I9000 Android Development] lenrek:
Hmm... Strange...

Can you do this:

prompt> adb shell

$ su -

# busybox fdisk -l /dev/block/mmcblk1

I am using a 16gb card with 1gb for EXT4:

# busybox fdisk -l /dev/block/mmcblk1

Disk /dev/block/mmcblk1: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 1812 14554858+ b Win95 FAT32
/dev/block/mmcblk1p2 1813 1936 996030 83 Linux

If you did not get anything out from here, I suspect, maybe you did not insert the card correctly.
[Galaxy S I9000 Android Development] sl8125:
fdisk: can't open. no such file /dev/block/mmcblk1

the phone is not detecting the external card. as soon as it boots removed external sd card message come up.
[Galaxy S I9000 Android Development] lenrek:
Strange, even with the partition not formatted, the SD card should be detected by OS.

For your case, I think you did not insert the card properly.
[Galaxy S I9000 Android Development] T0N3Z:
tried both still stuck on file analysis

this is really pissing the hell out of me!
[Galaxy S I9000 Android Development] lenrek:
What were the steps you took to flash the kernel? Remember, it must be in the following order:

1) Start Odin

2) Power off SGS, start in Recovery Mode.

3) Connect the USB cable. Do not connect the USB cable before complete (1) and (2)

4) Flash the kernel, by using PIT and kernel file.
[Galaxy S I9000 Android Development] T0N3Z:
i promise you id did that....what else could i be doing wrong.....i had this same problem with this: http://xdaforums.com/showthread.php?p=7308446# so i forgot about it, but this i kand of can't

.....does my captivate have to be rooted or su? or busybox?
[Galaxy S I9000 Android Development] T0N3Z:
is id suppose to 0?

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..
[Galaxy S I9000 Android Development] lenrek:
Not sure, as I did not notice it. However, I did face the same problem you have there. The solution is to follow the steps exactly.

Beyond this, I really don't know what else I can help you.
[Galaxy S I9000 Android Development] T0N3Z:
i am doing it from windows 7 x64...does that make a difference?
[Galaxy S I9000 Android Development] dahool2008:
tested your fix after reboot-and have no luck also.

when i have my phone charged-i make a frehs firmware update to jg3 and then make the test again-maybe i can reproduce the bug again.
[Galaxy S I9000 Android Development] dahool2008:
So made now a clean now firmware update to jg3.

get the same error.

so my think is- that the partition of the sdcard amkes the problem.

so that we can find the problem....can you please axplain with witch software and how you make the partition. i made it with gparted on linux debian.

this i get after fresh install (install your kernel and busybox)

/dev: 166828K total, 0K used, 166828K available (block size 4096)

/mnt/.lfs: Function not implemented

/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)

/system: 282432K total, 257132K used, 25300K available (block size 4096)

/disk: 2712240K total, 141804K used, 2570436K available (block size 4096)

/data: 1963904K total, 29504K used, 1934400K available (block size 16384)

/dbdata: 129728K total, 1292K used, 128436K available (block size 4096)

/cache: 30784K total, 12K used, 30772K available (block size 4096)

/efs: 6064K total, 4103K used, 1961K available (block size 1024)

/sdcard: 6060544K total, 2174880K used, 3885664K available (block size 32768)

/sdcard/sd: 12893888K total, 101432K used, 12792456K available (block size 8192)

i get from the beginning the same market error. also when i make a copy of media to /disk and make remove on /system and hardlink
[Galaxy S I9000 Android Development] raspdeep:
quick way to test is to move /data/data/com.android.vending out back to the rfs partition and try..
[Galaxy S I9000 Android Development] dahool2008:
ok made now not move - i cp and make the hardlink to sdcard for media. get the same error.

@ raspdeep can you explain please how.... cause /data/data is now a hardlink to /disk.
[Galaxy S I9000 Android Development] mimocan:
I made the partition with paragon disk manager for windows. But it should also work with gparted as you have already moved /data into there.

this is my partition layout and I have no problems to move data around:

Filesystem Size Used Available Use% Mounted on

tmpfs 162.9M 0 162.9M 0% /dev

df: /mnt/.lfs: Function not implemented

tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals

/dev/block/stl9 275.8M 214.7M 61.1M 78% /system

/dev/block/mmcblk1p2 1.0G 129.2M 859.4M 13% /disk

/dev/block/mmcblk0p2 1.9G 315.2M 1.6G 16% /data

/dev/block/stl10 127.2M 3.3M 123.8M 3% /dbdata

/dev/block/stl11 30.1M 1.5M 28.5M 5% /cache

/dev/block/stl3 5.9M 4.0M 1.9M 68% /efs
[Galaxy S I9000 Android Development] bommel0815:
there was a post over at MoDaCo I think where a member stated that he visited Samsung Belgium. They where a bit surprised about the problem, and after a while confirmed that Samsung will definitely fix this in a Firware upgrade.

make of that what you will :)
[Galaxy S I9000 Android Development] raspdeep:
if you kept the old data in /data/data.bak, then this should work

rm -r /disk/data/com.android.vending

ln -s /data/data.bak/com.android.vending /disk/data/com.android.vending

kill market before you do this..

actually, this is not a solution, its only meant for a test to see if the problem actually lies with com.android.vending in /disk

also, can u post your "mount" ?
[Galaxy S I9000 Android Development] dahool2008:
will test it...

mount:

rootfs / rootfs ro 0 0

tmpfs /dev tmpfs rw,mode=755 0 0

devpts /dev/pts devpts rw,mode=600 0 0

proc /proc proc rw 0 0

sysfs /sys sysfs rw 0 0

/dev/block/stl6 /mnt/.lfs j4fs rw 0 0

tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0

none /dev/cpuctl cgroup rw,cpu 0 0

/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block/mmcblk1p2 /disk ext3 rw,noatime,nodiratime,errors=continue,data=order

ed 0 0

/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc

harset=utf8 0 0

/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha

rset=utf8 0 0

/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar

set=utf8 0 0

/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset

=utf8 0 0

/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=

1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s

hortname=mixed,utf8,errors=remount-ro 0 0

/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,g

id=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-

1,shortname=mixed,utf8,errors=remount-ro 0 0

//Edit

Okay made with the link. It makes the same error with the market.
[Galaxy S I9000 Android Development] raspdeep:
so market was working fine before you move the link?

clear market cache, uninstall update?
[Galaxy S I9000 Android Development] dahool2008:
OK used a other sdcard. Problem is gone.

So this fix was okay-problem was my 16gb sdcard.

now everythin went fine.

great fix
[Galaxy S I9000 Android Development] mimocan:
I am glad that you made it work dahool!!
[Galaxy S I9000 Android Development] poolcin:
OK, what if i apply this patch and remove my SD card from a phone. What then? Will my system crash/be unstable? Or will it just affect few apps installed?
[Galaxy S I9000 Android Development] mimocan:
what if you apply a patch and remove the harddisk from your PC? will your system crash/ be unstable?

yes it won't start.

The only time I will remove my sdcard will be the moment that I will put this phone on ebay or marktplaats (NL). This won't happen any time soon.
[Galaxy S I9000 Android Development] oxylos:
Do you have make new Kernel when Samsung release new firmware?
[Galaxy S I9000 Android Development] mimocan:
I will definitely try out the new kernel when Samsung releases. But it won't happen until they push the update for froyo.

This kernel is based on 2.6.29, and original samsung source. The next kernel update will be probably 2.6.32 together with froyo.
[Galaxy S I9000 Android Development] poolcin:
So, I won't be able to connect my phone to PC and copy some file as well. Am I right?
[Galaxy S I9000 Android Development] mimocan:
no that's not right. Your PC won't recognize this partition anyway so all copying will be done to the fat32 partition.
[Galaxy S I9000 Android Development] Itsme87:
Any possibility of making a video tutorial for this :rolleyes: ?

Seams like a great solution but since I didn't understand the guide entirely I don't dare to try the fix.
[Galaxy S I9000 Android Development] dahool2008:
OK i can now reproduce the problem with running out of space in market. It always comes when the sd card ist 16gb (anyway testet more 16gb sd). maybe it's also a problem if the ext3 is more then 1,2 gb-will test this
[Galaxy S I9000 Android Development] mimocan:
This really should not matter as mine is also 16gb.

Anyway I really appreciate your efforts and testing.
[Galaxy S I9000 Android Development] lenrek:
Hmm... Is Odin 64 bit compatible?? Do you have 32bit XP or Vista?
[Galaxy S I9000 Android Development] T0N3Z:
NOPE just this one
[Galaxy S I9000 Android Development] Fekke:
Ok. So its alot of pages!

So im asking: What Ext do you prefer? Ext3 or Ext4? Im on to doing this but i dont realy know what one that i should make...

Quick reply please
[Galaxy S I9000 Android Development] K3yMaster:
Go for ext4. Its faster.
[Galaxy S I9000 Android Development] lenrek:
My vote for EXT4 as well.
[Galaxy S I9000 Android Development] Fekke:
Ok. But i have hered that it is less stabel? But you maby not have seen any problem with it? Is there any other things that i need to do when i applu the fix?

My phone is rooted and that stuff
[Galaxy S I9000 Android Development] K3yMaster:
ext4 is stable enough. ext3 is just more widespread that's all.

Just follow the guidelines in first post, and you should be ok.
[Galaxy S I9000 Android Development] iammichel:
So I'm finally finished reading through 39 pages of comments, so I should be able to safely state that whatever issues I might address are probably not discussed (properly) before...

I would like to post a few notes and questions, and it would be nice to see comments on these since they argue issues that I ran into and did not see discussed (in understandable language) so far.

- After tackling the lagging issue, is there a quick and easy way to determine that everything went right and the phone does indeed use the external memory? I have seen solutions on how to check this with terminal commands, but I was wondering whether there's a 'newbie friendly' way.

- There is an ongoing discussion on Quadrant scores. So far it appears that scores of +/- 1750 are the highest, but it is not very clear what users can/should do to fully optimize their Galaxys. It seems that the ext4 fix combined with the XWJG5 f/w produces best results, but I would like to see some more suggestions on how to reach 'optimal' performance.

I am using XWJG3 (too many messages that XWJG5 is instable) with the ext3 fix and task killer on aggressive mode and have Quadrant scores of +/- 1400.
[Galaxy S I9000 Android Development] Fekke:
I formated 1 gb ext4 with paragon. And the rest as fat32.

but i where wondering if im goin to format ext4 with an Letter-name or not?

i did format it with an letter-name.

Made all that needed to do.

And when i go into settings->SD-card and phonememory i cant see the ext4 partition...

do i need to reinstall the rom, make the ext4 partition again without an letter-name and then make the steps?
[Galaxy S I9000 Android Development] sl8125:
Its not recovery mode. its suppose to be in download mode. there is a difference. Maybe thats why..... check again a retry. easiest way to get to download mode.

adb reboot download

hope this works.
[Galaxy S I9000 Android Development] lenrek:
You would not see this partition. Is normal.
[Galaxy S I9000 Android Development] lenrek:
Oops... You are right, is downloading mode. My mistake.

Did you manage to solve your problem?
[Galaxy S I9000 Android Development] sl8125:
For the love of GOD. NO ;(

Okay. This is what i came up with.

The kernel seems to be installed okay. I checked the setting

The sd card is working functionally. I had both partition formatted after creating new FAT32/Ext4.

I installed fresh sd card on the phone. no detections.

Today, i factory hard reset. Wipe all info on the phone. the kernel installed is still there. however, i did notice the g-sensor is now working properly with the new kernel. after installing the kernel, it must of whacked the g-sensor, the orientation was off. BUT still no detections of external SD card. LOL. WTF MANG!

Final conclusion. After kernel installation, the phone has now somehow deactivated the external sd drive.

Okay my new question. Using ADB, is there a way to check if the driver for external sd card has been affected somehow during the installation of the ext4 kernel. I am talking out of my azz here. I don't know much so please understand. Maybe its just my phone. Please note its a CAPTIVATE. AT&T version.

Edit: Okay I went flashed my phone back to the originla rom with original kernel. Everything is back to the original format.

I inserted the sd card back in the phone. and CHIT original rom detects the sd card only showing my FAT32 storage.

For you those of you trying to use the EXT4 method with Captivate, the EXT4 kernel install will somehow detach the external sd card driver and will not mount correctly. Okay maybe EXT3 will I don't know. Gonna try it out now and let you guys know.
[Galaxy S I9000 Android Development] T0N3Z:
dude r u god? lol

finally something works

......however its been on <ID:0/005> DO NOT TURN OFF TARGET!! for like a good 5 minutes.....how long will it stay like this?
[Galaxy S I9000 Android Development] sl8125:
something is not working right if you are still at this stage. I just pull off the usb off and restart everything. cpu and phone and start all over. it really only takes 10 seconds. it should never take more then that. make sure your phone is in download mode. the big yellow triangle with exclamation in the middle and it says it is in download mode, do not power off! message should appear. then you plug the usb in. add the tar file and hit start.

i know what your going through i went through it. ext4 method didn't work for me. gonna try out ext 3 method now.

LOL. a noob giving direction to noob.
[Galaxy S I9000 Android Development] mazsuper:
Thanks Quadrant score 1700

flashed to XWjG5, rooted, followed your instructions, cool

feels good will test for a week, only got my gs 4 days ago :)
[Galaxy S I9000 Android Development] trinikartel:
yeaaaaaaa this really works well. I have a class 6 8GB in my 16GB SGS. Did the EXT4 fix and my quadrant score went from 922 (on JM2) to 1682. Definitely see the difference in app launch times

Thank you!!!
[Galaxy S I9000 Android Development] sl8125:
I noticed your on At&t network. Are you using Captivate? or Int'l version i9000?

I tried many times but when i installed the kernel, the phone will not mount the external sd card. Please tell me u don't have a captivate. plz... if you do, why do GOD hate me.
[Galaxy S I9000 Android Development] T0N3Z:
lol thats how we do it.....noobs united lol
[Galaxy S I9000 Android Development] trinikartel:
LOL...I'm actually using the i9000 (I should put that as my signature actually). It was pretty straight forward for me. I flashed earlier this morning with the new JM2 firmware, made sure i had the latest busybox installed and followed the instructions as stated on page 1. Only difference is I used the terminal app on the phone to enter the commands rather than adb.

I used Paragon to create the 2 partitions (6.5GB fat32 and 1GB ext4) on my microSD externally before putting it in the phone if that makes some sort of difference
[Galaxy S I9000 Android Development] Kil:
Sorry if i missed this, i tried to find an answer, but couldn't find it in this thread.

You say you won't loose any personal data or settings.

But isn't it better to delete and re-install all my apps after i've done this fix?

Or am i being the biggest noob out here with this question? let me know.. :p
[Galaxy S I9000 Android Development] japanfred:
Just done this on JM2, blisteringly fast now.

1459 in Quadrant.