I downloaded the leaked froyo firmware to my captivate hoping it would solve a lot of the issues of lag but it still lags a lot like it's a phone from 2006. I downloaded the Ryan ZA one click lag fix and it still lags. I wanted to put voodoo on it but I have froyo and I don't think it will allow me to do it...what the heck is the problem and why is there so much hacking I have to do to get it to run smooth. The HTC Aria runs blazingly fast and quick from what I read and this Super Phone Galaxy S runs slower than a Hero? If anybody has an answer I'd like to know or if someone can offer some suggestions on how to improve this. It's pretty annoying.
Ok, My Captivate lags a lot...this isn't normal
- Thread starter crossover37
- Start date
Its called RFS... call up samsung and complain to them about it...
so many problems with this
a) wrong section, Q&A or general please
b) notice that word "leaked" in what you said? it means this isn't OFFICIAL, which means it likely ISN'T the final release, so it's bound to have at least some bugs.
c) ryanza lagfix is placebo and awful and doesn't work at all (on top of that, ext2 is a bad choice)
d) if you understood how/where the lag was coming from, you'd know why voodoo is "necessary" on 2.1
e) the aria is built EXTREMELY different from the captivate, it's like comparing the iphone to the nokia n8... yes they're both android, but they're built different which leads to complications
f) voodoo is not yet available for 2.2 because we don't have source code for 2.2 (again, if you knew how voodoo worked, you'd know why it wasn't instant)... we can hack it in with initramfs, and there are people working on it... but it isn't top priority
g) and shockingly a SMALLER piece of hardware with a SMALLER resolution made by a company known for making quality android phones runs smoother? shocker. honestly.
h) if you actually had any other real world interactions with other android phones, you'd know the lag is occasional but not unusual (hell I've seen just as bad or worse on the droid x before)
i) I suggest you read, read, read, search, read, read, and think before you make posts like the above (why on earth you thought this belongs in development is beyond me)
/rant
a) wrong section, Q&A or general please
b) notice that word "leaked" in what you said? it means this isn't OFFICIAL, which means it likely ISN'T the final release, so it's bound to have at least some bugs.
c) ryanza lagfix is placebo and awful and doesn't work at all (on top of that, ext2 is a bad choice)
d) if you understood how/where the lag was coming from, you'd know why voodoo is "necessary" on 2.1
e) the aria is built EXTREMELY different from the captivate, it's like comparing the iphone to the nokia n8... yes they're both android, but they're built different which leads to complications
f) voodoo is not yet available for 2.2 because we don't have source code for 2.2 (again, if you knew how voodoo worked, you'd know why it wasn't instant)... we can hack it in with initramfs, and there are people working on it... but it isn't top priority
g) and shockingly a SMALLER piece of hardware with a SMALLER resolution made by a company known for making quality android phones runs smoother? shocker. honestly.
h) if you actually had any other real world interactions with other android phones, you'd know the lag is occasional but not unusual (hell I've seen just as bad or worse on the droid x before)
i) I suggest you read, read, read, search, read, read, and think before you make posts like the above (why on earth you thought this belongs in development is beyond me)
/rant
There are two kinds of lag. I/O lag is caused by the delays in accessing data stored on your phone in some partition. This is largely due to the use of RFS by Samsung, and the voodoo lag fix gets rid of most of that. Unfortunately there is no voodoo on Captivate leaked Froyo yet, as the source code has not yet been released by Samsung. The OCLF type fixes will help some by masking this lag when the amount of data being written and read is small. When a large amount of data is involved, these fixes will lag, as they still sit on top of RFS.
There is a second kind of lag due to memory shortage. This will hit you after the phone has been on for a while. This is similar to the paging seen on Windows, where the data has to be fetched from the hard disk. This type of lag is best fixed by installing a memory management application. The one I use is called Autokiller. Despite its name, it is not a task killer. What it does is make sure that a certain amount of RAM is always free. I use the strict profile, and my phone can go days without having to be rebooted.
There is a second kind of lag due to memory shortage. This will hit you after the phone has been on for a while. This is similar to the paging seen on Windows, where the data has to be fetched from the hard disk. This type of lag is best fixed by installing a memory management application. The one I use is called Autokiller. Despite its name, it is not a task killer. What it does is make sure that a certain amount of RAM is always free. I use the strict profile, and my phone can go days without having to be rebooted.
troll. go get an aria then^^
save a galaxy s for a person who can truly appreciate it.
save a galaxy s for a person who can truly appreciate it.
by accident I posted this in the development area, I didn't realize until after the fact, my bad.
So do you think I should put my phone back to 2.1 on my phone and apply voodoo? My phone lags quite a bit, it's bad.
I'll try out that app you suggested, thanks.
So do you think I should put my phone back to 2.1 on my phone and apply voodoo? My phone lags quite a bit, it's bad.
I'll try out that app you suggested, thanks.
Look at the z4mod post in this forum. It works on 2.2
http://forum.xda-developers.com/showthread.php?t=811902
There is a pre-release version out for froyo but I doubt it will provide more benefits than issues at this point.
the "pre-release" version you're talking about is for the i9000... and guess what, the i9000 has source code, we do not
I had the same issue when I installed the leaked 2.2.
I did a master reset, flashed back to stock, master reset again, flashed to 2.2 cognition. Now I don't know if the second master reset was necessary, but my phone is faster than ever. Very few problems, in fact... less problem than the 2.2 leak.
I did a master reset, flashed back to stock, master reset again, flashed to 2.2 cognition. Now I don't know if the second master reset was necessary, but my phone is faster than ever. Very few problems, in fact... less problem than the 2.2 leak.
Just flash to cog 2.1.6/2.1.7. I have absolutely no lag at all. Though even at stock my phone wasnt crazy laggy like your claiming your phone is.
Free RAM is wasted RAM.
And task killers, etc. are a great way to rape your battery life.
Autokiller is NOT a task killer. It changes the memory management profile that defines when the apps are closed. This is a combination of the amount of free RAM and the type of app and the state it is in. I also disagree that free RAM is wasted RAM. If you are trying to open a webpage and the amount of RAM is low, the system has to decide to close something else to free the space you need. If the profile of what to close is inefficient, you will frequently run into low memory situations, when the system has to continue to close some apps to free up the memory, and you will see lag as the system works it out for you. What makes you think that the profile that Samsung chose to determine when to close an app is necessarily the best one?
Last edited:
New posts
-
Paranoid Android Ruby Alpha 1 - Mi A3
- Latest: hektor2hektor2
-
problem with latency on samsung tablets
- Latest: N1NJATH3ORY
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone