Database Develop

[APP] One Click Lag Fix APK

Hello,
I take no credit for this at all. I saw it on the I900 post. and it works on vibrant. It gets rid of the sleep->awake lag.
NOTE: YOU MUST DO THE UNLAGFIX. DO NOT RUN THIS IF YOU HAVE NOT!
http://forum.xda-developers.com/showthread.php?t=760571
Author: RyanZA
Donation Link for him: https://www.paypal.com/cgi-bin/websc...if:NonHosted

what do you mean unlag fix..
:O .. and has anyone tried this on the captivate?
what are the requirements to run this app?

darkamikaze said:
what do you mean unlag fix..
:O .. and has anyone tried this on the captivate?
what are the requirements to run this app?
Click to expand...
Click to collapse
I helped RyanZA test this when he was still developing it. This is the 1.0 version of the lagfix, not the newer version, but it's great for people who aren't comfortable installing 2-3 or one of the update.zip versions

coolbeans, so I should be set on installing this apk because I've never tried applying any form of lagfix before, right?

This works great on the captivate. All un-lagfix is is simply removing the lag fix.

Great to hear I'll try this or when I'm back from school or.. I'll download it from school woo
i897 @ xdaApp

OCLF
Ok so after hours on end of deciding what to do about the lag issues I decided to go with the OCLF 1.0. Man did I make a good choice. I was barely at 900. I am now hitting 2100+. My firmware is stock version 2.1-update1. The baseband is I897UCJF6. My phone has lightning speed now it is truly amazing. For anyone debating on whether or not to do it I say go for it.

pardon my ignorance...but this one focuses on the sleep to wake lag?
This would be fantastic, it annoys me to no end that when I hit the power button I have to wait for it to respond...

is this required to root my phone?
Im sorry i'm a noob.

or need micro sd?

If I run this, will it erase any of my personal stuff?

jel7 said:
If I run this, will it erase any of my personal stuff?
Click to expand...
Click to collapse
No, it will not

unlag fix?
what is the link to the unlag fix so i can do this

Works great. Asphalt loads so quick now.

I ran this last evening, and at first boot there was a massive delay of the boot screen running, it stayed on the "AT&T World Phone" screen while all of the boot audio ran. Then the screen switched to the "3G" and "Galaxy S" screens. Rebooted a second time and it's back to normal. I ran Quadrant and found went from a 885 before to a 2160 after. The I/O is running thru 3X faster than it did before the lag fix, the 2D and 3D FPS didn't seem to have changed at all. In normal use, I do see the Music player opens noticeably faster.
Nice work, VERY simple to use.
Thanks for the hard work on this one

Seems to be stuck in between lag fix and undo lag fix
Hi,
I have a captivate that I bought from Rogers.
I rooted the phone, then I applied the lag fix using OCLF lag fix.
I decided to undo the lag fix in preparation of the rogers froyo release...
It seems that the undo succeeded (no obvious errors anyways)
When I went back to the OCFL app, the oneclicklagfix v2.2+ and v1+ are unavailble in red, when I "You already appear to have another lag fix installed! (/system/bin/playlogos1 less than 5KB)"
I did a restore boot animation to restore the playlogos1 file... but nothing changed.
the undo lag fixes (2.2+ and 1) are also unavailable
I tried Uninstalling ext2 tools (option available) I got this error:
Remove EXT2 Tools failed with error:Couldn't remove library libext2_blkid.so:rm:can't remove'/system/lib/libext2_blkd.so':Read -only file system.
I've checked the internal phone storage available space: 1.69 GB.
Can someone please help? Did the lag fix undo work? is it safe to upgrade to froyo with this issue (once it is release from Rogers that is)
Thanks

My girl has that on her Vibrant and she is always saying your phone is faster and better then mine.I'm running voodoo on P8

kam777 said:
Hi,
I have a captivate that I bought from Rogers.
I rooted the phone, then I applied the lag fix using OCLF lag fix.
I decided to undo the lag fix in preparation of the rogers froyo release...
It seems that the undo succeeded (no obvious errors anyways)
When I went back to the OCFL app, the oneclicklagfix v2.2+ and v1+ are unavailble in red, when I "You already appear to have another lag fix installed! (/system/bin/playlogos1 less than 5KB)"
I did a restore boot animation to restore the playlogos1 file... but nothing changed.
the undo lag fixes (2.2+ and 1) are also unavailable
I tried Uninstalling ext2 tools (option available) I got this error:
Remove EXT2 Tools failed with error:Couldn't remove library libext2_blkid.so:rm:can't remove'/system/lib/libext2_blkd.so':Read -only file system.
I've checked the internal phone storage available space: 1.69 GB.
Can someone please help? Did the lag fix undo work? is it safe to upgrade to froyo with this issue (once it is release from Rogers that is)
Thanks
Click to expand...
Click to collapse
Looks like it removed parts, but not all. I'd be hesitant to do the upgrade. Back up your apps, and use Odin(the full odin, not the AT&T one click) to flash the stock firmware. It'll wipe any remnants of the lagfix off.

i897 OCLF install help ..pls
So I downloaded oclf.2.3.0.apk. Installed EXT2 Tools, however, I get an error msg when I try to run either the OneClickLagfix V2.2+ or OneClickLagFix V1+ (which one should I be using anyway?).
"You do no have a /system/bin/playlogos1//system/bin/ playlogo file!"
I try to run Restore Boot Animation and get:
"Restore Boot Animation failed with erro: ....No such file or directory"
Please help or point me in the right direction. Thx!
BTW I'm on Froyo Cognition V2.4.1

I installed OCLF, installed EXT2 Tools, then look at my screen1st pic)OCLF2.2 is unavailable! After I click on it, i get the "no space in data folder" error(pic 2). The 3rd pic shows the space available. So what do I do? I need that fix badly!

[Q] Bell i9000 compatible firmware

Hi, I was just wanting to clarify what firmwares are safe to use on the Bell i9000.
I previously screwed up my phone because I flashed JPC and it corrupted my internal memory.
I was hopping to clear up what can be flashed on the Bell version of the i9000 and what can't me.
So far this is what I know.
Good:
JP2
JP3
BOJI
HVJHI
GJH2
JM2
JM4
XWJM5
JM7
JM8
UGJH2
1.20Ghz Kernel
Bad:
JPC
JPH
(possibly caused by One click lagfix)
To keep 850mhz radio
Modem: http://www.mediafire.com/?qic38waf8px13mz
CSC: http://www.mediafire.com/?7ow6p25nhzle5jo

JPC worked fine on my Bell Vibrant. Any of the international firmwares will work without any issues short of the issues inherent in the firmware already.

That was my understanding as well, but many people and all of the seem to have Bell Vibrants are getting corrupt sd cards from JPC, which basically bricks the phone.

My Bell Vibrant was Bricked no idea why ? because i didn't root or use a custom ROM so Bell [email protected]#$%# me over. Dammit 500 $ paper weight.
Now i gotta wait 3 to 6 weeks unless someone knows how to unbrick one without the 3 button recovery mode ?
Anyone ideas ? lol

Fuzz21 said:
My Bell Vibrant was Bricked no idea why ? because i didn't root or use a custom ROM so Bell [email protected]#$%# me over. Dammit 500 $ paper weight.
Now i gotta wait 3 to 6 weeks unless someone knows how to unbrick one without the 3 button recovery mode ?
Anyone ideas ? lol
Click to expand...
Click to collapse
No exactly what this thread is about sorry.

I also have a brick sent back to Bell/Samsung for repairs due to JPC.
I'm pretty sure any other firmware is fine. I had the HK JP2 installed without issue. Other than that I just stuck with the UGJH2 as it's nearly as new as any of the international firmwares and runs smooth, even without a lagfix.

mafiaboy01 said:
Hi, I was just wanting to clarify what firmwares are safe to use on the Bell i9000.
I previously screwed up my phone because I flashed JPC and it corrupted my internal memory.
I was hopping to clear up what can be flashed on the Bell version of the i9000 and what can't me.
So far this is what I know.
Good:
HK JP2
JP3
UGJH2
Bad:
JPC
JPH
Click to expand...
Click to collapse
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.

jentech said:
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
Click to expand...
Click to collapse
For me and some others JPC did it :S

jentech said:
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
Click to expand...
Click to collapse
JPC ran like garbage on mine but no major issues aside from the lag, JPH though has been a champ for me thus far.
Sent from my GT-I9000 using XDA App

we need to pin down as to what caused these SDCARD errors so we can all avoid that.
I'm thinking maybe repartitioning with the wrong pit file might cause something like this ?
I'm using JPC on my I9000m now, working nicely (some lag here and there, but nothing AutoKiller can't take care of), and since I saw the post about the SDCARD error on one of the i9000m, am a bit hesitant to flash JPH.
Problem is, if it does get bricked, its basically paper weight because am in the US and doubt Bell or Samsung US/Canada would be willing to help.

I also would like to find out what is causing the problems, it has to be an issue with only some of the Bell ones because there are people running these frimwares with no issues.

mafiaboy01 said:
I also would like to find out what is causing the problems, it has to be an issue with only some of the Bell ones because there are people running these frimwares with no issues.
Click to expand...
Click to collapse
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?

madmack said:
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
Click to expand...
Click to collapse
JPC messed mine with no lagfix installed. This has been ruled out in several threads on xda.
Sent from my I7500 using XDA App

it is also highly likely that us bell users are flashing with bell modem so that we can keep 850 out of the box and is root of the sdcard corruption.
for some reason i remember having nexus one that every firmware and mod always strongly warned that froyo modem is required as well as flushing dalwik cache right after upgrading from éclair.
and here most of us are doing just that using jh2 with froyo.
well as for me i know i wont be upgrading to froyo as long as this thing with sdcard keeps happening as my 30 days was up on sept 9 so no more DOA and even if under warranty still not willing to be without the phone for more than a month.

madmack said:
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
Click to expand...
Click to collapse
I lag fixed mine but as others have said it doesn't seem to be the cause.
Though I did seem to find a progressive decay in the phone until it finally shut off and never started. It wasn't all of a sudden.

mafiaboy01 said:
I lag fixed mine but as others have said it doesn't seem to be the cause.
Though I did seem to find a progressive decay in the phone until it finally shut off and never started. It wasn't all of a sudden.
Click to expand...
Click to collapse
Which lag fix ? if you used OCLF, did you allocate the entire internal memory to it ?

madmack said:
Which lag fix ? if you used OCLF, did you allocate the entire internal memory to it ?
Click to expand...
Click to collapse
Yes I did use OCLF, I only allocated the default so something like 800mb.
Sent from my GT-I9000M using XDA App

All the ones bricked, were you also having issues with the 3 button recovery? Trying to see if there is any connection there.

I'm reading around regarding this error, and it seems some guys with other phones and the same error got things running back by using Parted. You basically boot into recovery, push Parted to the bin folder, and then repartition/format that failed block: mmcblk0p1
I'm not sure what the file system currently is on that block, but the guys I got this info from were formatting it to ext2. I think if we modify it to match the filesystem that our ROMs require, then we're good. It's a long shot though, and if anybody has a bricked phone with them now, they could give it a go before sending it back for repair.

I used kies yesterday and upgraded to UGJH2, don't remember what it was before, whatever was factory loaded but now I am having all sorts of problems that I did not before.
GPS is way out of wack. Phone freezes. Signal disappears. Right now it's running smoothly but all day it was going retarded.
I give it a bit, if it doesn't sort itself out by the time froyo rolls I'll be flashing this sucka.
Thanks for the heads on good roms.

[Q] Freeze on Boot Movie. I-9000M, "M" Disappears

I have a Stock 2.1 Samsung Galaxy S I9000M from Bell and suddenly I noticed it would not boot anymore. It shows the model number, then the "M" would disappear and go on with the boot movie (for a good 5 min) then just blank out and freeze.
I had the Voodoo lag fix applied to it but it has been working fine until today.
What should I try doing on it?
Thanks!!

knightdaemon said:
I have a Stock 2.1 Samsung Galaxy S I9000M from Bell and suddenly I noticed it would not boot anymore. It shows the model number, then the "M" would disappear and go on with the boot movie (for a good 5 min) then just blank out and freeze.
I had the Voodoo lag fix applied to it but it has been working fine until today.
What should I try doing on it?
Thanks!!
Click to expand...
Click to collapse
That is strange. From what I read here in the fourms, the symptom of the missing "M" is related to flshing an international firmware but you say your device is stock... Is that correct?
I would start by removing the voodoo lag fix and then doing a factory reset. If that does not work then you may be one of the unlucky people (mostly us here in Canada with the i9000M) whos internal sd card has failed after applying the lagfix.
If anyone else has any info to share or if Im incorrect then please let me know.

Yes, the device is stock (updated through unhacked Kies) + Voodoo.
SO I have disabled Voodoo and then performed a reset in recovery mode. Then another reset through the phone's normal interface.
Currently restoring everything through Titanium then reapplying Voodoo.

knightdaemon said:
Yes, the device is stock (updated through unhacked Kies) + Voodoo.
SO I have disabled Voodoo and then performed a reset in recovery mode. Then another reset through the phone's normal interface.
Currently restoring everything through Titanium then reapplying Voodoo.
Click to expand...
Click to collapse
The other thing to keep in mind is that the voodoo lag fix actualy flashes a "non stock" kernel to your device so again... It MAY be the voodoo fix that is causing the "M' to disappear as it is compiled on an "international" kernel.
Perhaps if you NEED a lagfix you should use oe that does not modify the kernel itself but be warned... It seems that the lagfixes contribute to the internal sd card deaths that I previously mentioned.
PS... I thought Titanium coul only be used on a rooted device? Are you rooted? If so then your device is NOT "stock".

It would make sense for the "M".
Yes, I'm rooted, I thought root doesn't redefined stock

knightdaemon said:
Yes, the device is stock (updated through unhacked Kies) + Voodoo.
Click to expand...
Click to collapse
Wait, "updated through unhacked Kies"? Is it on JH2 eclair, or on some froyo variant? If the m disappears, it sounds like you used the reg hack on kies to update to an i9000 version of froyo

It is JH2, I bought the first batch of Samsung Galaxy S in Canada, it had another version beforehand. I do not have froyo yet, waiting on the official version.

knightdaemon said:
It is JH2, I bought the first batch of Samsung Galaxy S in Canada, it had another version beforehand. I do not have froyo yet, waiting on the official version.
Click to expand...
Click to collapse
Ah, ok, I understand now. I have no idea. I've only seen the m disappear when you run a i9000 firmware

[Q] Zroot4 app - will it work for bell i9000m ?

I have a Bell i9000m
I want to root it
I downloaded that z4mod - app
can anyone confirm if it works for the i9000m ?

Works like a CHARM!!! When you run it for the first time you may see that it does nothing for like the first 15 mins to 1/2 hour. If this happens to you just perform a reboot or pull your battery, start the app again and it will root in like 30 seconds...
Make sure you have z4root and NOT z4mod as the mod app is a new type of lagfix and NOT the root app...

yiannisthegreek said:
Works like a CHARM!!! When you run it for the first time you may see that it does nothing for like the first 15 mins to 1/2 hour. If this happens to you just perform a reboot or pull your battery, start the app again and it will root in like 30 seconds...
Make sure you have z4root and NOT z4mod as the mod app is a new type of lagfix and NOT the root app...
Click to expand...
Click to collapse
does z4mod lagfix work ?
after I root, should I lag fix ?
I am on stock android. Froyo i heard is coming next month. I am curious - will I have to remove lagfix/root before update? Will I lose my apps/contacts when I update to froyo ???

I used the z4mod to root it and it works amazingly. For the lag fix i used the One click lag fix and that worked amazing for me. And the one click lag fix is really easy to remove so i don't have any problems when i flash roms to my phone.
For your backups you should be using Titanuim backup for everything, so if you do lose it its easy to get back. And for your contacts just back them up using Kies, it will take a few seconds

might as well install DOC's i9000m froyo which already have z4mod included

Funkadelick said:
does z4mod lagfix work ?
after I root, should I lag fix ?
I am on stock android. Froyo i heard is coming next month. I am curious - will I have to remove lagfix/root before update? Will I lose my apps/contacts when I update to froyo ???
Click to expand...
Click to collapse
I am scared to try any lagfix for fear of my internal SD card going "bye bye" so I really dont know about it...
I was also curious about Doc's ROM as well but I have seen a few people with corrupt internal SD cards after flashing even through Clockwork Mod so I have not tried it yet... STUPID I9000M's!!!

[Q] Re-lagging even after OCLF

I am using galaxy S i9000 (international). I have stock 2.1, upgraded to 2.2 (kies), Z4root, and OCLF. Initially OCLF was just mind blowing....but after 1 month things are lagging horribly (its even worse than 2.1) My questions are:
1. Does installing apps on the SD card cause lagging even after OCLF (I am thinking like that as before installing OCLF i had to move all the apps from the SD card to the Internal storage)
2. Is there a possibility of a bug causing random crashes, which i am experiencing
3. Ultimately will removing the OCLF and reapplying it solve the lag issue ( has any one done that?
Please help
Will change the ROM as last resort (but dont want to at the moment)
p.s= my friends with iphones are really bugging me due to my phones random crashes, lags...
Its question of pride people

Get rid of OCLF completely.
It used to be good but is just outdated nowadays.
Revert the Lagfix in OCLF, then get rid of it.
Flash SpeedMod Kernel and enable EXT4 + Startup Tweaks.

xero2002 said:
Get rid of OCLF completely.
It used to be good but is just outdated nowadays.
Revert the Lagfix in OCLF, then get rid of it.
Flash SpeedMod Kernel and enable EXT4 + Startup Tweaks.
Click to expand...
Click to collapse
I would also look into flashing a 2.2.1 ROM as well. XWJS7 is the newest one at the moment.
Do some reading about flashing with Odin3. Do some research and read some tutorials posted on the forums.
Here's a good place to start... http://forum.xda-developers.com/showthread.php?t=723596