yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] ashwinds:
JM6

On XFJM6 too and deployed the update - SU works with almost all apps I've tried with - e.g. Titanium Backup, Market Enabler. When I launch Check_Space I dont see an alert from SU. The script returns no values.
[Galaxy S I9000 Android Development] EarlZ:
Could you post the actual update.zip that your using, probably the one on the thread had some changes thats not compatible wit JM6
[Galaxy S I9000 Android Development] ashwinds:
update.zip

Attaching the update.zip that I have deployed.

Couple more notes:

1) Ryan's OCLF Checkspace script gets SU and executes fine.

2) I am not even sure this is firmware related. I havent tried these versions recently, but I never could get Tayutama's ver 2+ scripts to run (was on JG4 then). Ver 1 would execute real smooth.
[Galaxy S I9000 Android Development] EarlZ:
That update.zip is quite large.. Lagfix inlucded ?

Im not sure why its not working for me with JM6, maybe i borked my phone ?
[Galaxy S I9000 Android Development] Tayutama:
The update.zip he posted is the same that is in the OP aka 2.3.3

Got no idea why mine won't work on your phone though :(
[Galaxy S I9000 Android Development] EarlZ:
It works on all other firmware aside the XFJM6, tried it already altho I get a FC error on the first time I run the SU app and permission asking is done over a dozen times in certain apps.. could this be phone related defect ?
[Galaxy S I9000 Android Development] kgk888:
It says yours works on JM1. Does that include the new JM1 rev.3?

Just checking since it wasn't explicitly listed in the OP
[Galaxy S I9000 Android Development] FadeFx:
tayutama can you give some more details on the apn-conf.xml you use in your first post, is it the monster apn list from cyanogen mod?
[Galaxy S I9000 Android Development] Tayutama:
The JM1 that is in the OP is not rev.3, also those are just what firmware I have tested it on.

No idea, though i didn't get it from his builds. Got this one from SamSet
[Galaxy S I9000 Android Development] Toss3:
Running rev.3 and it works fine. :)
[Galaxy S I9000 Android Development] timn2bama:
ok when froyo 2.2 comes out will we have to uninstall this lagfix before upgrading?
[Galaxy S I9000 Android Development] zimphishmonger:
Does anyone know if this is working for the TMobile Vibrant variant of the Galaxy S?
[Galaxy S I9000 Android Development] Tayutama:
Nobody knows for sure what the Froyo update will do but most likely it will wipe all from the phone including the lagfix

I think i saw someone post he got it working on Vibrant but i'm not sure about that... You might wanna see through the thread for it.
[Galaxy S I9000 Android Development] Bec07:
Does not work on latest Froyo release.:(
[Galaxy S I9000 Android Development] Tayutama:
It does since i'm using it myself on JPC :)

Though you need to flash it in recovery mode when you have flashed another kernel for when you root JPC... Then you can flash this update.zip
[Galaxy S I9000 Android Development] The_Chrome_Coyote:
Running and enjoying. :)
[Galaxy S I9000 Android Development] cryolithic:
Up and running on

I9000UGJH2

2213 Quadrant score :)

One question: Why use the internal phone (/data) storage rather than the internal SD card?

picasaweb.

google.

com/lh/photo/_N4d2WlyWIrFmyfTkpQEdEZmB3eV_um9YF91ufjM_aw?feat=directlink
[Galaxy S I9000 Android Development] LeDiable:
Rooted & Installed.....Quadrant went upto 1817 from 993 :P

Man what a change!!!
[Galaxy S I9000 Android Development] Tayutama:
Because if we use the internal sdcard (/sdcard) then you won't be able to mount it on a computer since your phone will do mass force close then
[Galaxy S I9000 Android Development] tranms:
I don't think the ext4 lagfix works on captivate with stock firmware I897UCJF6.

I tried using update2.3.3.zip and after reboot the phone hung on the galaxy s screen. I deleted all user and cache data and got it to boot but then was in a FC loop. From there I could put my phone in debug, use droid explorer, and grab my clockwork recovery update.zip to place on my internal sdcard.

Does SL4A have a log so I can see where in the script my phone might have errored out?

It seems you're the only developer offering a EXT4 lagfix. Problem is even if it works with Captivate JH2 or JH3, I don't want to revert from the stock firmware because of reports of 3G band connectivity issues (not being able to connect unless reboot).
[Galaxy S I9000 Android Development] Toss3:
Does ext4 work on the new kernel?

Edit: Apparently not. :)
[Galaxy S I9000 Android Development] Tayutama:
Sadly not... lacking the module files for the new kernel to enable that... how i just wish they would integrate ext4 into the kernel :(
[Galaxy S I9000 Android Development] Tayutama:
Sadly i can't test it on the captivate firmwares as i got a I9000 myself.

Zilch... get to work ;)
[Galaxy S I9000 Android Development] streakpt:
Seems i can't install quadrant from market, i have eris market fix, ryanza 1.6 app lag fix and JPC rom.
[Galaxy S I9000 Android Development] TheRob44:
Epic 4G?

I'm going to pick up the Epic 4G this afternoon. I'd like to get this rooted with the lagfix in one go. I know this thread isn't specific to the 4G, but has anyone tried this on it yet?

Thanks,

-Rob
[Galaxy S I9000 Android Development] timn2bama:
Went from lag 4 to lag 2 from 1700 to 2200!
[Galaxy S I9000 Android Development] timn2bama:
Ok stupid question what does check space do? Does it recover lost space in lag 2?
[Galaxy S I9000 Android Development] Tayutama:
Nah it's just a script to tell you how much space there is left inside the ext* file
[Galaxy S I9000 Android Development] E9rendil:
Hello

I have an error message when I flash:

E: Failed to verify signature whole-file

E: Signature verification failed

Installation Aborded

My SGS is root, JPC

Ideas?
[Galaxy S I9000 Android Development] Uppsala9496:
The ext4 works on I897UCJF6.

Follow the instructions. After it auto reboots, let it run the media scan cycle. Once it finally finishes, you need to restart your phone again. Power down, then power up. It will take a bit to power back up.

My quadrant score went from 898 to the high 1900's. Just ran it after a 3rd power down and it is at 1699.

EDIT: Just to clarify. Follow the instructions. The phone will auto reboot after the SL4A ext4 script is run. You need to manually power down again. After your second reboot, you will notice the phone is much faster. The second reboot will take a long time (as did the first auto reboot).

I used Kies to drag and drop the update.zip (renamed) to the internal SD card. I renamed my current update.zip temporarily.
[Galaxy S I9000 Android Development] Phaze13:
I can verify it takes next to forever on the first autoboot during the flashing S. So long I was worried also. Just let it finish 10-15min. A second restart/boot is recommended as noted above. Yes I'm using stock

JF6, applied Ext4 after 2nd restart.
[Galaxy S I9000 Android Development] Fedburin:
Running an ext-4 with OC4 kernel on a Vibrant...

Can I install this fix over the top of the previous External Ext-4 lag fix without issue? Are there advantages to this lagfix over the standard external Ext-4 lagfix?
[Galaxy S I9000 Android Development] Tayutama:
You can't use update.zip's with JP3 and JPC...

Ill see about making an bat file to copy over the content of the zip file

Added link to this post in the OP :)

If you mean that you already are running the external lag fix then you need to remove that first before this one can be applied.
[Desire Themes and Apps] syklitengutt:
Anyone know of any backup prog that installs progs without me pressing install and close for every single app installed like I have to with titanium backup?
[Desire Themes and Apps] maxomus:
You gotta get the donate version of titanium backup to get the 1 click restore, I believe my backup pro does it as well if its still around.

Sent from my phone.
[Desire Themes and Apps] ephumuris:
My Backup Pro does the job a treat for me and is still being updated.
[Desire Themes and Apps] syklitengutt:
thnx. titanium donate fixed.
[Captivate Android Development] rajendra82:
How about the kernel based lag fix that you can use with an external card? Is that method no longer recommended?
[Captivate Android Development] Smallsmx3:
I'm assuming design is incorporating this into super duper user infinite? I really like how fluid things are on my cappy since running the last lag fix. Thanks for all the good work
[Captivate Android Development] Zilch25:
You can still run that one if you're satisfied with it :) Though I've found this to be a bit faster due to the buffering.

The other side of this is that it can function with a stock kernel with no flashing required but it *does* use your internal storage- so if you're afraid of that then keep on truckin with the external method
[Captivate Android Development] Zilch25:
He's well aware of it! He was actually testing the new version without any of us knowing it- sly devil :D
[Captivate Android Development] designgears:
shhhhhhh ;)
[Captivate Android Development] Zilch25:
:o

By the by, if you didn't notice theres a 2.3.1 out that reverts SL4A to r0 to fix the FCs :D
[Captivate Android Development] Tayutama:
he is already using sl4a r0 already... ;)

this should learn me not to update to a new version and then release something without testing it... :D
[Captivate Android Development] Zilch25:
Shhh don't let them hear you, it may besmirch your reputation.

FIX IT FIX IT FIX IT

:D
[Captivate Android Development] ponack:
Our Devs are so fun. :)
[Captivate Android Development] Circazero:
So I just flashed a JH3 using Odin and everything is great.

So I download Tayutama's 2.3.1 lagfix. Flashed it successfully.

But when I try to run SL4A and Run the LagFix_Ext2.sh I get an error:

"The application SL4A has stopped unexpectedly. and i have to force close it. :(

Any suggestions?
[Captivate Android Development] Zilch25:
Yeah we're actually working on that one right now... it was working fine yesterday but somewhere along the line some of the refinements managed to mess things up.

I'm on a fresh JH3 right now trying to figure it out too!
[Captivate Android Development] Tayutama:
Trying to figure out why it makes that error atm... We didn't have that error yesterday so it's kinda weird
[Captivate Android Development] Zilch25:
It's bizarre... really bizarre.

I've tried both versions of SL4A, and I've tried some scripts from yesterdays test version and they're both giving the same errors- I even installed spare parts and the development tools that you removed between yesterday and today
[Captivate Android Development] Tayutama:
Tbh i got no idea what is going on...
[Captivate Android Development] Zilch25:
Just for the hell of it I'm going to take the version from yesterday afternoon (2ish my time) and replace the scripts with the ones in the new version and see if it runs.

Performing it from a full wipe
[Captivate Android Development] bleeman:
Compatiible?

I am running the stock JF6...am I good to go on this lag fix?
[Captivate Android Development] Tayutama:
Sitting looking through a logcat... found something interesting... it errors out because it can't find library com_googlecode_android_scripting_Exec...

and weird part is that that library is included in the apk
[Captivate Android Development] Zilch25:
As soon as we get this bug ironed out you will be, give us a little more time :)
[Captivate Android Development] Zilch25:
That *is* weird... is it a permissions issue maybe?
[Captivate Android Development] Zilch25:
Oh that part is easy :)

Go to your command prompt:

adb shell

Now unlock your screen so you can see the homescreen

back in the command prompt type:

su

Look at your screen and approve the popup :) Once you get the # in the command line you have root! (You can lock your screen again at this point)
[Captivate Android Development] phishie:
Oh d'oh! Thanks!
[Captivate Android Development] phishie:
So that worked great, I just have one question.

In the advice I got for moving the hosts file from /sdcard to / it was suggested to use:

"busybox mv /sdcard/hosts /system/etc/"

Why "busybox mv" rather than "mv"?
[Captivate Android Development] Zilch25:
Well the difference is:

busybox cp = copy

busybox mv = move

As for why you put the busybox in front- sometimes some of the commands aren't linked right and will only work with busybox in front of it

By using copy you create a copy of the hosts file while leaving the original hosts file on your /sdcard area, if you use mv it creates the file in /system/etc but deletes the original file from /sdcard

I use mv for most things myself, but only because it reduces clutter on the sdcard :D
[Captivate Android Development] phishie:
Gotcha, thanks.

I only asked because I used mv fine to rename my existing hosts file and wasn't sure if I needed the "busybox" to move the new hosts file.
[Captivate Android Development] skins30:
anybody else have a huge battery drain and the phone gets really hot? it did speed up but the battery is getting wasted
[Captivate Android Development] Zilch25:
Can't say that I have... I'm running this AND an OC kernel and I haven't had any issues. Hell my phone was last plugged in last night at around 1AM, it's 3:52PM now and I'm at 76% battery.
[Captivate Android Development] Kagoshema:
i swore i wouldnt try any more lag fixes after i messed up the other ones and had to nandroid

but....

idk the market lag drives me nuts
[Captivate Android Development] Zilch25:
They're pretty addictive, but hey, it beats huffing glue :D
[Captivate Android Development] schtuka:
I had the same epiphany
[Captivate Android Development] Clienterror:
My favorite sharpie flavor is grape.
[Captivate Android Development] Tayutama:
Gotta love trying to fix scripts and then i get a boot loop when applying the update.zip... gah
[Captivate Android Development] Zilch25:
Well dg just pulled the script out of his SRE... so this thread is probably going to get a lot more busy in the next couple hours D:
[Captivate Android Development] Tayutama:
saw that... atm i'm trying to see if i can integrate Gscript better then sl4a :) but also got a few bug fixes in them like removing stuff that wasn't used but gave errors for a few people
[Captivate Android Development] Fortune090:
Yeah... Doing/undoing the ext2 fix always ends up with the same thing. ext4 functions perfectly fine for me though.
[Captivate Android Development] Tayutama:
Got no idea why there would be problems with ext2 but i'm testing a new update.zip atm that has a few changes in it compared to 2.3.2... 1 change in the ext2 which *MIGHT* help
[Captivate Android Development] Fortune090:
Hmmm... I'll definitely be testing it out! :D

I just see more improvement in speed with ext2... Might just be delusional, but it's just what I see, haha.
[Captivate Android Development] Tayutama:
well new version is up... do note that i could change my font with ext2
[Captivate Android Development] Zilch25:
Hmm I suppose I should give this one a shot then eh? Did you change anything big?
[Captivate Android Development] Tayutama:
well only 1 version now... it removes old root and installs a new one, so there should be less problems with that... it also removes any old sl4a folders on /sdcard and any old sl4a apps..

Btw it's sl4a_r1 it's using now and i have had np so far..

also included a new hosts that doesn't block localhost like the last one...

And ofc cleaned up the scripts to remove whatever lines i didn't use so there should be less problems that way around also
[Captivate Android Development] Zilch25:
Awesome! I'm about to give it a test... you'll be hearing from me if it doesn't work! :D
[Captivate Android Development] Zilch25:
The new fix worked brilliantly :) Now to try fonts...

Edit: Fonts in EXT2 still say disparaging things about my mother and spit in my face
[Captivate Android Development] Tayutama:
Weird since it worked for me on ext2...
[Captivate Android Development] Zilch25:
It's never worked for me on EXT2, but I've got the special Captivate... well, me and Clienterror :D
[Captivate Android Development] Tayutama:
Hehe you two and your Captivate... <3 I9000 ;)

Anyway off to bed since i'm going out with the family later today... they gather here in 6 hours or so... *cry* and ill proberly be back 8-10 hours later so around 8pm-10pm GMT+1
[Captivate Android Development] Zilch25:
Okay, I'll try to fight off the problems till you come back :D Have fun with the fam...
[Captivate Android Development] ominously:
If I ran the ext2 script, what can I do to change to ext4 ?
[Captivate Android Development] Zilch25:
You'd have to use the remove fix script that came with the one you initially installed. If you used the update.zip method you should still be able to find it in your app drawer in the application "SL4A".

Now keep in mind if you're rolling back from a version more than a couple days old theres a very real possibility it will fail to uninstall so make sure you're backed up!
[Captivate Android Development] ominously:
Nah, I'll be using the same SL4A I installed with the update.zip, I just want to change it to ext4.

Thanks Zilch, <3<3
[Captivate Android Development] Kagoshema:
2 things before i try this

1: does the ext4 work on jf6?

2: does anyone know what % more r/w's ext4 uses compared to ext2? cuz i know it can shorten memory life but i havent seen any examples of how much
[Captivate Android Development] Zilch25:
1. Yes it does

2. EXT2 won't do any extra writing to your device because it doesn't journal at all... EXT4 will write whenever you have any sort of disk operation.

Modern flash memory has wear leveling though, so while it's doing more work the work is spread out all over the device and doesn't abuse any single block more than another- in short chances are you'll replace your device before EXT4 can kill it. You might also want to view it as a temporary fix until Samsung gets their act together :)
[Captivate Android Development] Kagoshema:
k, thanks :)

but is there like any sort of scale or something for strain on ram or flash memory?
[Captivate Android Development] Zilch25:
Not really... we're just a bunch of basement hackers- most of this is based on speculation and armchair math :)

If you're worried about wear just go with EXT2, there's no reported cases of it corrupting on anyone to date. Just keep a decent backup and you'll be prepared for the worst (having to reflash)
[Captivate Android Development] ZooCow:
Reporting in from a Captivate JF6. Its working great.

Went from ~800 to 1897 in Quadrant, but, more importantly, its noticeably faster. Thanks again for all of your hard work!
[Captivate Android Development] Clienterror:
To be honest I'm not sure anyone knows how much the stock writes, so it could be more or less. But normal ssd memory can be written to for like 3 years 24/7 before its expected to fail. So in reality its more like 9 or more with normal use probably. And to put that into perspective if you kept your phone from 9 years ago it would probably be a nokia candy bar phone (I miss all the cheap face plates)
[Captivate Android Development] sfernandez:
Just did this on STOCK Captivate JF6. Its working great.

Went from ~895 to 2145 in Quadrant, and is a faster.

THANK YOU :D
[Captivate Android Development] jimtastic:
installed ext2 (with that one click apk.. convenient) over sre1.2.1 on JF6 and i'm getting a 2347 on quadrant. absurd.
[Captivate Android Development] Smallsmx3:
Small issue. I had the sre installed yesterday. (the last one before the lash fix was removed) everything went fine with no issues except for the OC not exe. So today I flashed over the sre with the new one. OC was working but when I rebooted from the update the lagfix was gone and not working. I downloaded the lagfix applied it with no issues except when I looked at my internal memory it only had 825 mb instead of the. 1.25 gb it had after applying all the other lag fixes. Any ideas?
[Captivate Android Development] Smallsmx3:
nevermind. im assuming that 1gb was used instead of the 512 thats been used on the other lagfixes.
[Captivate Android Development] Zilch25:
That's sort of right, this version of the lagfix does some things differently-

It creates an EXT file (type of your choosing) of around 800MB, all of your system data and application data is moved into this file. The remaining space on your NAND is left for the larger part of the application (the apk files) and those live harmlessly in the normal RFS space. So you can look at your remaining space as the amount of space you have left to install apps- but do keep in mind that data from each app (a relatively small quantity) will still go to live inside the EXT file, so if you want to check space remaining inside the EXT file you can use the option from within SL4A :)
[Captivate Android Development] itpromike:
So if I'm using SRE I can't use the "Tayutama's Update.zip method (recommended)" lag fix and I need to wait for designgears to update things or has someone who has SRE done this successfully?
[Captivate Android Development] Zilch25:
designgears has since then removed the lag fix from SRE since people were having issues with the baked in version of it. There's no reason why the new and improved versions shouldn't work on SRE though, if you do come across any bugs with it though please give a report. With the amount of people that use SRE it would certainly be worthwhile to figure out what went wrong :)
[Captivate Android Development] itpromike:
Well I'm using the version of SRE that DID have the lagfix baked in... What should I theoretically do? Do I need to somehow uninstall it (I don't even know how to do that LOL)? Or can I just go ahead and install this lagfix or do I need to redo SRE without the lag fix baked in and THEN install this new one? I'm guessing if I do a titanium backup I should be safe anyway so which would be the best method to try seeing as I can get all my apps back if something goes wrong...?
[Captivate Android Development] Zilch25:
Hmmm well if you have the version with pre-baked lag fix but the lag fix isn't applied you should be able to just plop in this update.zip, install it through system recovery (NOT ROM MANAGER), and it should remove the old, replace with the new, and you should be able to run it from the SL4A application.

If you had the previous lag fix method running I'd recommend a reflash, or at the very least make sure you back up everything before trying to revert it!

Hell, back up everything anyway!
[Captivate Android Development] itpromike:
Ok let me make sure I got this right... reflash to the new SRE then use the "Tayutama's Update.zip method (recommended)" and everything should theoretically be ok. Now when you say don't use ROM manager you just mean don't flash through it right? I can still go in ROM manager and use the boot into recovery mode though right? Or do I have to go into recovery mode manually?
[Captivate Android Development] Zilch25:
Yes, use rom manager for backup purposes, but don't use it to apply the update.zip for the lag fix :)

Not a whole lot of people have given any reports of how the new lag fix works with the new SRE, so it's *possible* (though not probable) that something could interfere, so please let me know how it goes. If there's a bug I'd love to get to the bottom of it :)
[Captivate Android Development] itpromike:
OK great thanks for the help mate. When I click the 'Boot into clock work recovery mod" from ROM manager, and it reboots into recovery, I'm then completely out of ROM manager right? I mean it's not some special ROM manager recovery mode it put's me in right? It's the same as If I rebooted and held the power and volume buttons correct? Sorry for all the questions mate, just making sure I understand everything fully.
[Captivate Android Development] Smallsmx3:
I have both new versions of the lagfix and sre and both are playing nice. Everything is stable and really fast. My concern is with OC enabled will there be extra drain on the battery? Prob the wrong thread for this? Now only if xda could update there app so it doesn't FC all the time......