yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Zilch25:
Things to check:

Make sure you are in debug mode

If you *are* in debug mode, make sure you don't have your SDCards mounted for copying files to your computer via USB (You can toggle this from your notification pulldown).

Make sure when you start this your phone is unlocked and that you're giving it permission to run
[Galaxy S I9000 Android Development] s2k:
Actually it was quite funny. Why do people try to do things to their phone when they don't have the faintest idea what they're doing? Please try to read this forum first before trying to screw up your phone.

But: your phone is not rooted, that's your problem. And no I am not going to tell how, find it on this forum how to, you'll learn a lot reading it.
[Galaxy S I9000 Android Development] Tayutama:
and ofcourse have a rooted phone :)
[Galaxy S I9000 Android Development] RyanZA:
All of this is already in the first post though. It's all very clear imo. I don't think repeating it over and over is the right way to go.

Mostly importantly though: if something goes wrong and he manages to get this to install, he won't be able to fix it. This is bad! Much worse than not using the lag fix at all. I'm comfortable with people using the lag fix if they can restore to a backup, or reflash their device if everything goes wrong. But if they can't do this, or don't know someone who can do this, then I INSIST that they do not get within 1km radius of my fix, or ANY lag fix. :D

The occasional pauses are better than having to send your device back for repairs (imo anyway). I don't believe it is possible for this type of lag fix to ever be completely problem free. (Please prove me wrong! :D )

EDIT: If you follow the procedure properly from a stock rom and do manage to have your device not boot, I'd really like to know more about it! What firmware, what mods, everything!
[Galaxy S I9000 Android Development] Zilch25:
In my defense.... he did claim it was rooted :o
[Galaxy S I9000 Android Development] mohnishism:
I had mounted my sdcard..i have rooted my fone

thanks zlich,s2k nd tayutama...ur replies very morehelpful dan ryanza's were...

but i do appreciate da guy a lot..

nd yes it was funny...
[Galaxy S I9000 Android Development] frankencat:
Flashing 2.2 lagfix now. Getting lots of FC errors on the phone and apps are popping up randomly and phone is completely locked up. Script still seems to be running though. We'll see.... :)

Edit: Seems to have worked. 2152 on Quadrant.
[Galaxy S I9000 Android Development] Narcissus85:
@RyanZA

which firmware are u using at the moment?

I'm with JM2 ... do u suggest something better?

thanks

ivan
[Galaxy S I9000 Android Development] RyanZA:
Yeah, this is by design. :D

It is bulldozing over your apps with a 1.5GB sledgehammer. It makes a copy before hand though, so it should be fine. :D
[Galaxy S I9000 Android Development] RyanZA:
I'm on I9000JPJG8 - it works the best for me. Pretty similar to JM2 though.
[Galaxy S I9000 Android Development] frankencat:
Seems smoother than v1.
[Galaxy S I9000 Android Development] RyanZA:
Whyyy can't you read the first post? :)

Anyway good to know you got it working, sorry for taking your head off! That question, or something almost like it, gets asked every ~3 pages though. And the answer is in the first post!
[Galaxy S I9000 Android Development] Narcissus85:
thanks for the answer...i'm looking on samsung-firmware.webs.com for the JG8 and i see that is not a EU firmware

can i flash it on my european device?

(sorry for the OT)
[Galaxy S I9000 Android Development] kgk888:
Can I ask, are you running Eclair (2.1) or Froyo (2.2)? And which firmware?

Best I could muster with Froyo (2.2) / Firmware JP2 was 1836 in Quadrant.

EDIT: Nevermind I see your sig now, and it's Eclair. Which firmware though? I"m anxious to see how this performs on Eclair and with the stock launcher stripped and replaced with something not laggy like LauncherPro
[Galaxy S I9000 Android Development] frankencat:
Wow! Really flying now! Thanks and let us know when you need to test some more. :)
[Galaxy S I9000 Android Development] RyanZA:
It's an AFRICAN firmware actually - middle eastern. I have it on my UK imported SGS though, and it works fine. (Since there is zero hardware difference with the middle eastern and European galaxy s.) Before any lag fix is applied, it was definitely the smoothest firmware. After lagfix, most firmwares are smooth enough that you can't tell the difference. IMO anyway!
[Galaxy S I9000 Android Development] mohnishism:
yes i finally managed to do it...nd its awsome..thanks ryanza..if nything goes wrong i can always flash da firmware again..i do noe how to use dat...
[Galaxy S I9000 Android Development] Narcissus85:
eheh thanks! edited my post about the "american" mistake too late :p

thanks again i'm gonna try that now... :)
[Galaxy S I9000 Android Development] bahamutkung:
sos! when i install this version. it make lower score then 1.0 (22xx -> 17xx)

and when i uninstall it. result is infinity loop of reboot. :(

now i'm shock and don't know what to do.
[Galaxy S I9000 Android Development] frankencat:
I am running the stock ROM for US T-Mobile Vibrant. I actually got a little bit higher Quadrant score with v1 but the phone feels faster and smoother with v2.2. Maybe due to the dbdata move?
[Galaxy S I9000 Android Development] galaxydog:
Tayutama: Do your update uses latest 2.2 version from ryanzx?
[Galaxy S I9000 Android Development] IDtheTarget:
Which way did you test it? Tayutama's upgrade.zip, or Ryan's instructions at the beginning of the thread?

Thanks!

Now if only Tayutama would let me know about whether his upgrade.zip is compatible with the root method I used, found here:

http://xdaforums.com/showthread.php?t=723479
[Galaxy S I9000 Android Development] kgk888:
Oh, sorry to confuse. I meant which phone firmware you were running. But if it's a US firmware I guess it doesn't apply to me anyway (Europe)

I did the OneClickFix v2.2 with Froyo firmware JP2 and got 1836 in Quadrant. The Touchwiz interface is still crap (in my opinion anyway) and needs to be gutted and replaced with something that has smoother animations.

I'm going to flash a good Eclair ROM (JG2, JM2 or JM5 probably), apply lagfix v2.2 and then try to gut TouchWiz and try LauncherPro (which apparently doesn't work on Froyo yet). I suspect it will really eliminate any trace of animation lag until we get the official Froyo release for the Galaxy S.
[Galaxy S I9000 Android Development] RyanZA:
Could be the dbdata, could also be the real mounts instead of symlinks. In v1, when the phone went to fetch a file, it would have to first fetch a symlink and work out what to do, and then only fetch the file. Now it can pick it up normally. I'm still not entirely sure what dbdata is used for - but what I do know, is that anything inside /dbdata (on EXT2 now) is very very fast! Unfortunately, only 100MB of space in there. :(

BTW, I have updated Post 2 : Frequently Asked Questions. If anybody has any question they see coming up a lot that they want added there... shout! :)
[Galaxy S I9000 Android Development] Tayutama:
Not yet... (But tbh it's almost the same.. Only difference between the current update.zip and RyanZA's 2.2 is update.zip uses 1.6GB for space and RyanZA's 1.5GB, and he runs /dbdata/databases from /dbdata where i run it from /data

But working on a update that runs dbdata/databases from /dbdata and fixes the problems that people have with paid apps.

(And maybe with added ext3 support but not sure if ill put that one in.)
[Galaxy S I9000 Android Development] RyanZA:
With JPJG8 and this lag fix, I'm really not seeing any lag. You might just be more sensitive to lag than I am though! It's worth a try if you have the time though.
[Galaxy S I9000 Android Development] Tayutama:
Umm no idea tbh can see there is one file in that zip that i don't have in mine.

Also mine installs busybox 1.17.1, latest su and Superuser 2.3.1

RyanZA: Small problem... it won't mount /dbdata/dabases on boot :( but it was mounted before the reboot :(
[Galaxy S I9000 Android Development] fish1ng:
i followed the instructions, however after rebooting my phone i get the notification "Database storage is getting low"

Is this normal or did i do something wrong? everything looks normal for me..

thanks
[Galaxy S I9000 Android Development] Gr8gorilla:
the paid apps/google maps fix would be really nice. It seems I get FC whenever opening anything related to maps.....
[Galaxy S I9000 Android Development] alerems:
Hey, why there is only 435 mb free space for apps? (i9000)
[Galaxy S I9000 Android Development] Tayutama:
Ok RyanZA get to work since you make me work more :(

LagFix.sh

Top of file:
LOOPBACK_1=/dev/loop0
LOOPBACK_2=/dev/loop1
LOOPBACK_3=/dev/loop2
IMAGE_FILE_DATA=/data/image.ex2
IMAGE_FILE_SDCARD=/sdcard/image.ex2
IMAGE_FILE_DBDATA=/dbdata/linux.ex2
MOUNTPOINT=/data/data-ext2
DBDATA_DIR=/dbdata/databases
TEMP_DIR=/data/sddata
BACKUP_DIR=/data
DISK_SDCARD=/dev/block/mmcblk0p1
DISK_DATA=/dev/block/mmcblk0p2

Bottom with the dbdata part:
echo "Copying /dbdata/databases to mountpoint...";
busybox cp -rp /dbdata/databases $TEMP_DIR;

echo "Creating 100MB $IMAGE_FILE_DBDATA";
if [ ! -e $IMAGE_FILE_DBDATA ]; then
busybox dd if=/dev/zero of=$IMAGE_FILE_DBDATA bs=1M count=0 seek=100;
else
echo "Skipping. Image already exists.";
fi;

echo "Setting up loopback with image file.";
busybox losetup $LOOPBACK_3 $IMAGE_FILE_DBDATA;

echo "Formatting image through loopback.";
mkfs.ext2 -b 4096 -m 0 $LOOPBACK_3;

echo "Creating mountpoint for files.";
if [ ! -d $DBDATA_DIR ]; then
mkdir -p $DBDATA_DIR;
else
echo "Skipping. Mountpoint already exists.";
fi;

echo "Mounting device";
mount -t ext2 -o noatime,nodiratime,errors=continue $LOOPBACK_3 $DBDATA_DIR;
for i in databases; do
echo "Copying $i to mountpoint...";
busybox cp -rp $TEMP_DIR/$i $DBDATA_DIR;
done;

Userinit.sh

Top:
LOOPBACK_1=/dev/loop0
LOOPBACK_2=/dev/loop1
IMAGE_FILE_DATA=/data/image.ex2
IMAGE_FILE_DBDATA=/dbdata/image.ex2
MOUNTPOINT=/data/data-ext2
DBDATA_DIR=/dbdata/databases
REMOVE_FIX=/data/image.unfix
BACKUP_DIR=/data/bak

if [ -e $IMAGE_FILE_DATA ]; then
busybox mknod $LOOPBACK_1 b 7 0;
busybox mknod $LOOPBACK_2 b 7 1;
busybox losetup $LOOPBACK_1 $IMAGE_FILE_DATA;
busybox losetup $LOOPBACK_2 $IMAGE_FILE_DBDATA;
busybox mkdir -p $MOUNTPOINT;
busybox mkdir -p $DBDATA_DIR;
e2fsck -p $LOOPBACK_1;
e2fsck -p $LOOPBACK_2;
mount -t ext2 -o noatime,nodiratime,errors=continue $LOOPBACK_1 $MOUNTPOINT;
mount -t ext2 -o noatime,nodiratime,errors=continue $LOOPBACK_2 $DBDATA_DIR;

# mount the mountpoint
for i in app app-private data system dalvik-cache; do
mount -o bind $MOUNTPOINT/$i /data/$i;
done;
fi;

It mounts all EXCEPT /dbdata/dababases
[Galaxy S I9000 Android Development] IDtheTarget:
Hm..so if I run your lagfix update.zip, do I run the risk of bricking my phone (yes, I know that I always run that risk, but the AMOUNT of risk is relative), or should it just overwrite the stuff put there by the other method?

I apologize for being a pain, it's just that I'm so SICK and TIRED of this frickin' LAG. It makes the phone unusable at times...
[Galaxy S I9000 Android Development] kgk888:
Well JPJG8 is Android 2.1 (Eclair) though. I imagine it's a little more polished than JP2, which is Android 2.2 (Froyo), seeing as Froyo isn't technically in the wild yet for Galaxy S.

I will try the JG8 firmware though, as it should work just fine for Europe.

I am pretty sensitive to lag though, but almost all the lag that I notice is from the TouchWiz interface, which I find to be horrendous. I have an HTC Desire sitting here rooted with OpenDesire 3.0.5 on it and it seems a little snappier going from home to application list and back, but in applications like Google Earth the Galaxy S (with JP2/Froyo and v2.2 lagfix) is a little bit quicker.
[Galaxy S I9000 Android Development] Muaddib69:
Ryan or anybody, may I ask you to confirm that the files to delete after uninstall v1 (those you said that were not deleted by unlagfixme.bat v1) are just this 3 you mention in the code of v2???

** This can be crucial for anyone -like me- wanting to clear not deleted backups of v1, and not wanting to install V2, YET.

Thanks in advance.
[Galaxy S I9000 Android Development] frankencat:
Another one for the FAQ.

Noobs. :rolleyes:
[Galaxy S I9000 Android Development] ruskprick:
Did the fix on jp2.Phone stuck at logo,randomly vibrating. V1 was fine,this one is not.:mad:
[Galaxy S I9000 Android Development] RyanZA:
Do it like this, it works for me:

busybox mknod $LOOPBACK_1 b 7 1;

busybox mknod $LOOPBACK_2 b 7 2;

There is something special about b 7 0, some sort of 'all loopback' option. Beats me. :D
[Galaxy S I9000 Android Development] kgk888:
I had the same issue with Tayutama's version and JP2.

Try Ryan's One Click Lag Fix v2.2 in the OP. It worked fine for me with JP2.

You will obviously need to reflash JP2 with Odin though.
[Galaxy S I9000 Android Development] RyanZA:
2-2 will delete the old .bak files when you install it. You can delete them manually to be sure though! Those are the files.
[Galaxy S I9000 Android Development] RyanZA:
You had some sort of lag fix already running when you tried to install this... so it couldn't make the loopback mount. Any ideas what it might have been?
[Galaxy S I9000 Android Development] RyanZA:
It can't actually brick your phone, you can always flash on a new firmware. If you CAN'T flash on a new firmware, STEP AWAY FROM THE LAGFIX, for your own good. :)
[Galaxy S I9000 Android Development] CrazySmile:
Workt perfectly for me, Thanks!
[Galaxy S I9000 Android Development] Tayutama:
Look at the attached image :) that is with:

busybox mknod $LOOPBACK_1 b 7 0;

busybox mknod $LOOPBACK_2 b 7 0;

Like i wrote in the post with the zips i have only tested the eclair version on jm1.

Will test the new one i'm making on JP2 later when it's done...

EDIT:

busybox mknod $LOOPBACK_1 b 7 1;

busybox mknod $LOOPBACK_2 b 7 2;

only mounts what is in /data not /dbdata... *cry*
[Galaxy S I9000 Android Development] Muaddib69:
Thx Ryan, but I dont want to install v2 at the moment!, just delete those forgotten bak files, that's why I insist asking u what are the exactly bak's to delete... (sorry for my insistence)

And thanks again
[Galaxy S I9000 Android Development] RyanZA:
JP3 will always have lag until you turn off JIT. This is because the JIT on JP3 is sadly broken. It is meant to precompile and store raw machine code for the java bytecode it will run. However, JP3's JIT seems to not be caching the machine code it makes, and all kinds of other weird bugs. It's just broken. Try turn it off if you can. :D
[Galaxy S I9000 Android Development] jkcheng122:
I ran the BETA 2 but did do a unlagfix before running the new one. Prior to that I did another method that had some codes posted I'm still trying to locate the thread.
[Galaxy S I9000 Android Development] IDtheTarget:
I haven't tried to learn how to flash my phone, because I *gasp* actually like the interface that came with the phone, and also want to ensure that when Samsung releases the official Froyo, I'll be able to install it. The other reason is that my wife has a phone also, and I have to support hers from a distance (I'm away from home a LOT for the next two years), and if I have a custom ROM and she doesn't, it makes it that much harder.

I'd be willing to attempt it, however, if I could somehow backup the original ROM in my phone so that i could revert to it at need.

Of course, I'd be amazed if Samsung isn't monitoring this thread and incorporating your fixes into the Froyo release...
[Galaxy S I9000 Android Development] RyanZA:
No problem, happy to help. :)

The 3 .bak files you listed were the exact ones!

I don't really understand.. is it giving an error or something?

Yeah.. you had some weird stuff hanging around that caused the 2-2 fix to fail. It needs the /dev/loop0 interface, and you were already using it for something else. You'd need to clear out that other lag fix first. It is probably hanging around in /system/playlogos1
[Galaxy S I9000 Android Development] jkcheng122:
Found the other thread: http://xdaforums.com/showthread.php?t=727279

I'm going to do the undo there and then run the unlagfixme and re-run lagfixme.bat.
[Galaxy S I9000 Android Development] Tayutama:
no idea can't see what it does at boot.

need to use adb logcat > logcat.txt then :(

made a minor edit to my lagfix.sh so trying that out first
[Galaxy S I9000 Android Development] RyanZA:
I hope so! :D

As far as flashing your firmware, there are tons of guides on it. It seems to be completely safe.

That's weird. I'll try install those and try track down what they're doing. It is probably related the maps issue some people are getting:

08-12 23:14:31.562: ERROR/Database(3493): sqlite3_open_v2("/dbdata/databases/com.google.android.apps.maps/LayerInfo", &handle, 6, NULL) failed. err=14 ..

Also strange. It seems that some of the files in /dbdata/databases aren't making it through - randomly.
[Galaxy S I9000 Android Development] rugbycaps:
A question please!

applied lagfix 2.2 sucessfully. Still get the low storage message and a red sd card image on the left side of the notification bar. Is this working correctly?
[Galaxy S I9000 Android Development] RyanZA:
I found your problem Tayu

echo "Copying /dbdata/databases to mountpoint...";
busybox cp -rp /dbdata/databases $TEMP_DIR;

echo "Creating 100MB $IMAGE_FILE_DBDATA";
if [ ! -e $IMAGE_FILE_DBDATA ]; then
busybox dd if=/dev/zero of=$IMAGE_FILE_DBDATA bs=1M count=0 seek=100;
else
echo "Skipping. Image already exists.";
fi;

You copied the databases out, but you didn't delete the originals before making the image file. So you can't mount /dbdata/databases, cause of either no space, or cause it already has data in it. :D
[Galaxy S I9000 Android Development] RyanZA:
Not likely... You must have some strange stuff hanging around in /data

Any chance you could use ADB like this:

adb shell
su
ls -l /data

and post the results?
[Galaxy S I9000 Android Development] Tayutama:
is that your last offer? :D

echo "Copying /dbdata/databases to mountpoint...";
busybox cp -rp /dbdata/databases $TEMP_DIR;

echo "Creating 100MB $IMAGE_FILE_DBDATA";
if [ ! -e $IMAGE_FILE_DBDATA ]; then
busybox dd if=/dev/zero of=$IMAGE_FILE_DBDATA bs=1M count=0 seek=100;
else
echo "Skipping. Image already exists.";
fi;

echo "Setting up loopback with image file.";
busybox losetup $LOOPBACK_2 $IMAGE_FILE_DBDATA;

echo "Formatting image through loopback.";
mkfs.ext2 -b 4096 -m 0 $LOOPBACK_2;

echo "Creating mountpoint for files.";
if [ ! -d $DBDATA_DIR ]; then
mkdir -p $DBDATA_DIR;
else
echo "Skipping. Mountpoint already exists.";
fi;

echo "Mounting device";
mount -t ext2 -o noatime,nodiratime,errors=continue $LOOPBACK_2 $DBDATA_DIR;
for i in databases; do
echo "Copying $i to mountpoint...";
busybox cp -rp $TEMP_DIR/$i $DBDATA_DIR;
done;

echo "Now setting up reboot support";
echo "Installing userinit script...";
if [ ! -e /system/bin/playlogosnow ]; then
busybox mv /system/bin/playlogos1 /system/bin/playlogosnow;
busybox cp /sdcard/sl4a/resources/playlogos1 /system/bin/playlogos1;
busybox chmod 755 /system/bin/playlogos1;
else
echo "Skipping playlogos1. File already exists.";
fi;

if [ ! -e /system/bin/userinit.sh ]; then
busybox cp /sdcard/sl4a/resources/userinit.sh /system/bin/userinit.sh;
busybox chmod 755 /system/bin/userinit.sh;
else
echo "Skipping userinit.sh. File already exists.";
fi;

echo "Cleaning Up..."
umount $TEMP_DIR;
busybox losetup -d $LOOPBACK_3;
busybox rm $IMAGE_FILE_SDCARD;

echo "Rebooting now to clear up any outstanding file links.";
reboot

Right before reboot if i did #reboot so it didn't reboot and then did this in adb shell: df -h then /dbdata/databases was mounted like i should be.

But ill try the other one
[Galaxy S I9000 Android Development] rugbycaps:
thank you for the reply :)

Im sorry I have completely how to or what is adb shell sorry /cry.

And yes I do have some data from FIFA10 in the folder!

but nevermind that! thankyou RyanZA for the hard work!

so can i please ask another question

When the official FROYO firmware comes out, can i just go ahead and upgrade my firmware through Kies?? or do i need to do anything else like running the unlagfix on the device first?
[Galaxy S I9000 Android Development] RyanZA:
There is something very very strange about /dbdata ;)

Just playing around it with ls -l c*, ls -l co*, and files don't follow any proper pattern.

I'm thinking it is NOT a good idea to include this folder in a lag fix. :)
[Galaxy S I9000 Android Development] bub181:
Thanks again Ryan for your hard work! It's great that we now have fsck checking of the EXT2 partition. I have one question, will fsck automatically fix errors if it finds them? I noticed that you haven't passed any parameters to do that explicitly.
[Galaxy S I9000 Android Development] MAMBO04:
right, just did it, took longer than usual but i'm glad about the error checks :) it's awesome, working really well atm! Here is my QScore: 2136

running this on JM5 SamSet 1.9c, i had the previous version applied but got rid of it and applied this

cheers! great work!
[Galaxy S I9000 Android Development] makamiso:
You say only for people who value their data so im assuming this wipes all of your data unlike your original lag fix?
[Galaxy S I9000 Android Development] vytman:
Just a question, the 1.7GB of application data available is only for the 8GB version or for the 16GB as well? Shouldn´t we have more space with 16GB version?
[Galaxy S I9000 Android Development] E_man5112:
Well, it's installing on my captivate, so I'll tell you how it goes :D
[Galaxy S I9000 Android Development] MAMBO04:
Oh and i have 199MB free now from 1.7G's ahah :)
[Galaxy S I9000 Android Development] Tayutama:
First whine RyanZA :)

I get Invalid Attachment specified. If you followed a valid link, please notify the administrator when i try to download it... GET TO IT ;)

Ill be making update.zip versions of this as soon as i can download it... also i might make it abit smaller then 1.7GB so we don't get the warning about low on space.
[Galaxy S I9000 Android Development] hcarrega:
memory low in sdcard
[Galaxy S I9000 Android Development] RyanZA:
No, it doesn't wipe your data. I goes to horrible lengths to try to keep it intact. :D

I say it's only for people who don't value their data, because its still in testing and may have bugs that will wipe your data out!
[Galaxy S I9000 Android Development] RyanZA:
The Invalid Attachment was because I just removed it and put up version 2-1 that removes old .bak files. This is where the warning for low space is coming from. You should have over 200mb free normally.

Everyone, if you previously had V1 installed, you need to download V2-1, and not used V2 !
[Galaxy S I9000 Android Development] MAMBO04:
Well 99% of us on here are not bothered about our data cause we keep on re-flashing every second and trying lag fixes. So not a problem i think cause we all keep backups ;)
[Galaxy S I9000 Android Development] clubtech:
There were a few .bak directories left /data.

I deleted them all and now internal storage is showing about 193MB and he market and widgets are working again.
[Galaxy S I9000 Android Development] RyanZA:
V2-1 will hopefully fix this. V1 left behind old .bak files. :(
[Galaxy S I9000 Android Development] RyanZA:
It's that easy? Awesome. :D

Everyone with the low disk space error who has used V2 and not V2-1 - go into /data and remove the old .bak files manually!
[Galaxy S I9000 Android Development] MAJED.y:
:rolleyes: Thank you for your hard work RyanZA,

will try now your new patch.

:eek:

already the unlagfixme running! :D

i should go and get something to drink. :rolleyes:
[Galaxy S I9000 Android Development] makamiso:
I understand this is off topic but could someone refer me to a thread that gives the basics of making backups just incase something goes wrong? Cheers everyone :)
[Galaxy S I9000 Android Development] Tayutama:
Next time make it easier for me to edit into an update.zip damnit :(