• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Stage 1 Speed Fix for Captivate (Vibrant, Galaxy S)

With all the threads about available memory and all, I was curios if that wuould make any difference.

I started out with running the test after my phone had been running 2-3 hours, and had a lot of apps open in the background:

58 MB free memory, lots of apps loaded, score 813
Closed a bunch of stuff, 170 MB free memory, Score 825

Not much difference there.

Not sure if I will mess with the fix, given the restrictions.

d8aaf69b.png


I find it interesting how close the graphs shows it to the SGS with 2.2
 
No, that's the Galaxy S with <2.2 which means less than 2.2

So, your scores are right on for a Galaxy S running 2.1 (Not sure why they just don't say 2.1 instead of <2.2)
 
I am seeing Quadrant scores approaching 1000 now and if the other fix is ever released that allows us to put application data on our Class 4 microSD cards, we will see speeds close to 1700.
Click to expand...

So... Question. You say a class 4 card should get incredible speeds, but would it be worth it to invest in a class 6 card? At that point, what would the limitation be, the phone or the card?
 
Yea this works and this works well. I'm not going to run a benchmark though because I'm far more concerned with real world performance. My Captivate flies! Its like I have an entirely different phone.
 
To those concerned about hitting the App memory limit and seeing a bunch of Force Close issues, below is the command that you can run to determine how much data your apps are taking (assuming you are rooted and have busybox):

Code: 
adb shell
su
busybox du -h /data

at the bottom of the output you will see something like 26.0M /data/data this is the total amount of space your apps data is taking up, in my case it's only 26Mb so I think I will run this and see the difference
 
Is there a way to 100 percent tell if my phone is stage one or if i sucesfully un did it. I tried undoing it and it just did wierd thing, all apps still there but my backround changed and the data saved within the apps were erased trying to undo stage 1. for example my custom handcent is back to stock.
 
I went ahead and gave this a go tonight. My initial quadrant score, before doing anything to the phone at all was around an 840. After a few tweaks, such as removing the ATT Bloatware, I was up around 870. After doing the stage 1 speed fix I am scoring considerably higher, and beyond that, the phone is running noticeably better.

screenshot.png
 
Thank you! Thank you! Thank you!

I was about to return my Cappy tomorrow for an exchange it was so laggy it was getting extremely annoying. My score was 867 prior to the fix and now I am rocking a 962.

Life is so much better now. My exchange email now instantly shows instead of waiting 3-8 seconds for the message body to appear. All my apps insta-load. This is what I expected this phone to be.
 
So these relatively small increases in score really lead to such huge real-world perceptions/experiences in speed increases? I wouldn't think that increases <100 would be so significant/noticeable.
 
sremick said:
So these relatively small increases in score really lead to such huge real-world perceptions/experiences in speed increases? I wouldn't think that increases <100 would be so significant/noticeable.
Click to expand...


Yes, my phone is flying. Makes a huge difference.
 
sremick said:
So these relatively small increases in score really lead to such huge real-world perceptions/experiences in speed increases? I wouldn't think that increases <100 would be so significant/noticeable.
Click to expand...
In theory, an increase of 100 isn't that much. The thing is that the galaxy s phones have an actual I/O glitch and this fix is a workaround. If anyone had quadrant pro and could run the custom benchmark, the I/O benchmark, they would see that the performance is probably multiple times better. The full benchmark isnt just testing the I/O glitch that causes the lag, but all aspects of the phone's speed so the increase isn't by much.

Look at these benchmarks by androidandme. Scroll down to the I/O test. See how far behind the droid x the captivate is? I'm sure after this fix, if someone ran the I/O test that it would be on par with the droid x....multiple times faster
What is the fastest Android phone? – Android and Me

Idk what the difference is between the fix you guys are doing and others, but people here are getting quadrant scores of 1200-1400.
UPDATED : Real fix for the "stalling/lagging" problem - Android @ MoDaCo

I'm getting my captivate today :-D so I'll probably give this fix a try as long as it doesn't require any rooting....I haven't looked through the instructions tho. Don't wanna void my warranty fixing a glitch on a glitchy phone that the manufacturer should be the one fixing in the first place. Something tells me that with the lag and gps issues, a total recall should still be on the table for samsung. I think both the gps and lag fix are both just work arounds so noone really knows if its actually a hardware or software issue right now except samsung.
 
if you read other posts you'll actually see that the ridiculously high scores on the droid x are false scores.i don't remember the technical reason but I'm sure its somewhere on this thread or on the xda thread. Once we get android 2.2 the I/O scores should increase significantly.
 
mttfrog13 said:
I'm getting my captivate today :-D so I'll probably give this fix a try as long as it doesn't require any rooting....I haven't looked through the instructions tho. Don't wanna void my warranty fixing a glitch on a glitchy phone that the manufacturer should be the one fixing in the first place.
Click to expand...

That's the thing: my understanding of this "fix" is that it not only requires rooting, but also rearranges data in a way that imposes new limits which can cause problems. You're right: while the speed benefits might be real, I don't want to introduce a new series of issues as a result... and such an intrusive fix shouldn't even be necessary in the first place.

Someone can feel free to correct me if I'm wrong... but I think there's "fine print" on this that needs to be emphasized.
 
if you undo this you have a folder left named /dbdata/data
code used to remove
adb shell
su
busybox cp -rp /dbdata/data /data/data.tmp
rm -r /data/data
mv /data/data.tmp /data/data
reboot

If you uninstall a program it doesnt remove the data in the /dbdata/data if you undo this do you still need to keep that folder /dbdata/data since you have everything now back on /data/data

UPDATE:
I did a factory reset and then rooted checked with root explorer and /dbdata/data is not there anymore so it shouldnt be needed however, it's not mentioned in the steps, so be careful if you revert back, there seems to be a folder not needed anymore but I'm not 100% positive..however after a factory reset it is GONE!! So i would go out on a limb and say it can be safely removed but who knows when you create it and point the software to read from there instead, it might still read some from there and bust your #$@@ up!! So I just reverted did a factory reset and mine is normal now!!
 
Android_J said:
Froyo will allow us to move apps to the externa SD right? I really wish they would've just used 16GB NAND modules. Cheapskates.
Click to expand...

Do we have any specs around what size NAND they did use? The phone shows 1.67GB internal memory free and 13.7 GB internal SD card free. It seems unlike we got 2GB of NAND and 14GB SD.

Could the problem just be a partition issue? Even so, why is there a 130MB limit in NAND when I have so much free memory?
 
You must log in or register to reply here.
Back
Top Bottom