I installed OCLF on my phone (Froyo JPO) and tried to remove it in order to upgrade to 2.2, I think it didnt remove the lagfix right though, as the option to apply the lag fix, and the one to remove the lag fix is no longer available. (I cant remember if it specifically said it failed or not.)
I saw somewhere on this site that you first have to install some other rom, or to just select something else in ODIN if updating with lag fix still enabled. Also, should I uninstall all apps with root access before unrooting? And can I backup apps with titanium backup in order to restore it if I have to completely wipe my phone?
use quadrant to check your score.. if its more then 1000 the lagfix is still enable.. my advice is to flash only if you are sure that it is disable...
if i am not wrong, OCLF can say the reason why a function is not avaible, maybe your battery is less then 40%
for flashing it is not neccesary to unroot..
Youre right, it does give the reason. When I try to remove it it says that I dont have the lagfix installed, and if I try to add the lag fix, it says that I already have another lag fix enabled, which I dont. Obviously something went wrong somewhere.
Should I just try to flash 2.2.1?
the exact error messages are as follows
when i try to remove lagfix: "You do not app0ear to have a V2 lagfix installed! (free space on /data does not match /dbdata/ext2data)"
When I try to add the fix: "You already appear to have another lag fix installed! (/system/bin/playlogos1 less than 5 kb)"
So you still dont know of the lagfix is enable??.. check your quadrant score.. if this is below 1000, this will mean that the fix is disable, so you can start flashing..
I just assumed it wasn't applied anymore and installed update and it worked. Lucky me I guess haha, thanks for help
Sent from my GT-I9000 using XDA App
Related
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!
Hi,
What would you recommend setting the size of the EXT2 partition in OCLF to? Just got Cog 2.2 running, so... yeah... thanks!
hmm.... I set mine as high as it can go, but then again, I don't have many apps. I kinda have this question myself.. anybody have ideas?
I set it to max also, ~1500mb. I did default 850 or so last time and got low space warnings after restoring my titanium backup
Its weird because I haven't even been able to get it to work... I keep getting errors trying oclf at the default setting. Just out of curiosity, does this need to be installed right after a fresh flash, or does it matter if all my apps are installed already?
Sent from my froyo'd out cappy
beazie0885 said:
Its weird because I haven't even been able to get it to work... I keep getting errors trying oclf at the default setting. Just out of curiosity, does this need to be installed right after a fresh flash, or does it matter if all my apps are installed already?
Sent from my froyo'd out cappy
Click to expand...
Click to collapse
It shouldn't matter. I installed it after I had installed my apps and it worked fine.
i just set 1 GB for EXT2
i tried it this morning and it borked the hell outta my phone. hade to start all over again. one of these days ill learn not to do this stuff until i have time to fix it if something goes wrong
ive read somewhere that it may not work if you have apps installed on your sd card, but it was never confirmed. for me, the lagfix did not work when i installed 2.2, rooted manually, etc. but when i did a fresh install, cog 2.2, and lagfixed before restoring my apps, it went fine
Hi..
Isn't there chances of data corruption with ext2?
vikdmon said:
Hi..
Isn't there chances of data corruption with ext2?
Click to expand...
Click to collapse
I used default setting to enable OCLF 2.1+ and it worked well first day. Today, I couldn't open email with force closes. I disabled it and now email works fine. So there may be some issue here with Cog 2.2 beta - Froyo.
tylerstoehr said:
ive read somewhere that it may not work if you have apps installed on your sd card, but it was never confirmed. for me, the lagfix did not work when i installed 2.2, rooted manually, etc. but when i did a fresh install, cog 2.2, and lagfixed before restoring my apps, it went fine
Click to expand...
Click to collapse
I confirm that. OCLF kept failing on my cell until i started with a fresh install and applied the fix before restoring apps.
In the end I removed it, is not perfectly stable and the phone is already very snappy without it. I'll wait for Voodoo
voodoo is out except it is in beta stages i think stage 3
labbu63 said:
voodoo is out except it is in beta stages i think stage 3
Click to expand...
Click to collapse
Voodoo is not out for Froyo (2.2) Voodoo only works on 2.1
beazie0885 said:
i tried it this morning and it borked the hell outta my phone. hade to start all over again. one of these days ill learn not to do this stuff until i have time to fix it if something goes wrong
Click to expand...
Click to collapse
You are rooted right? The OCLF from the market won't work without root.
Alright guys one more time
RyanZa's lagfix is really really well built and he put a ridiculous amount of checks into it. It will not work when you have restored with TIBU because undoubtedly some of the apps you installed are set to default install on your sd card. That being said you really cant do the lagfix with them installed because they are actually not on a separate sdcard, just a partition of your sd card that your OS is on as well. That means the OCLF cant unmount the card to copy **** off of it and hence the lagfix will fail with a loop0 error. So if you want to do the lagfix and have all you crap on your phone and dont want to start again, go into your applications menu, tap manage, and the sdcard and then delete all your apps off of it that are there(prob only a few if you havent moved more yourself). After you've deleted those apps reboot phone, run OCLF and then get TIBU to restore missing apps.
DONE AND DONE!
P.S. i am that guy you heard it from......i have posted it like 4 times i think.
P.P.S forgive me if i am coming off short, i am in school and pulled an all nighter studying for tests! Dont mean to be
ice3186 said:
RyanZa's lagfix is really really well built and he put a ridiculous amount of checks into it. It will not work when you have restored with TIBU because undoubtedly some of the apps you installed are set to default install on your sd card.
Click to expand...
Click to collapse
It also won't work just because you restored with TiB. If you did a batch backup and had EVERYTHING restored, well that's just really stupid of you. That restore deleted the newer 2.2 services and files with your old 2.1 services and files. If you then proceed to install the OCLF, you're going to get errors and FC's.
You must start off with a freshly installed, rooted JI6 before you go about installing the lagfix. That way you don't have to worry about where any of your applications get installed to, and there's less data for the OCLF to move around coincidentally speeding up the entire process.
I ran OCLF after using the batch restore of my apps with TBu and everything went just fine for me. I guess it was just luck of the draw our something.
I guess so. But so far everyone that's asked me for help has done the batch restore with the old services+files and/or hasn't rooted their device yet.
I did 1023mb (close enough to 1gb) and get around 1800 quadrant scores.
To me it sounds reasonable.
I was reading forums about lag fix.
I wanna install one but it seems like possibility of bricking phone after installing lag fix is higher in I9000M (Bell model) than any other galaxy s models.
Is there reason for it? Can anyone share their experiences?
Also, I read somewhere that JH2 fixes the lag. Is that true?
I was doing benchmark but never got past 950 with quadrant....
I had no problem with OCLF until I did an upgrade of th app trought android market. Then OCLF didn't recognise that I had a lag fix install and I tried the option to repair the fix and it made my phone lag like hell. Then I tried to flash and repartition with odin to wipe this but I surelly made something wrong cause it bricked the phone. I had to buy another one used over kijiji.
Been using OCLF since then and I didn't had any other problem. I even uninstall it completly a few hours ago cause i want to try froyo. I think it's safe but don't try the repair option ever and try to install and uninstall the fix with the same version of the OCLF to avoid recognition problem.
Sent from my GT-I9000M using XDA App
sp991 said:
I had no problem with OCLF until I did an upgrade of th app trought android market. Then OCLF didn't recognise that I had a lag fix install and I tried the option to repair the fix and it made my phone lag like hell. Then I tried to flash and repartition with odin to wipe this but I surelly made something wrong cause it bricked the phone. I had to buy another one used over kijiji.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Sorry i didnt really get how you bricked yours. So were you upgrading any app with lag fix? Do you mean you shouldnt upgrade any app after you installed lag fix? So to upgrade, i should uninstall any app completely then re-install new version?
Thats one downside....
I'm not sure how I bricked my phone but it's related to the re-partition option in odin and me flashing a froyo firmware. I did this with XXJPH and it was after the problem with OCLF.
What I'm sure of, is that OCLF (the app from the market) didn't recognise that my phone had a lagfix and didn't allow me to un-lag fix it. So I tried the option to repair the ext2 tools and it failed. After that the phone was really lagy and a lot of forced close happened. That why I wanted to repartition with an odin flash.
The probleme is that I tried with the only firmware (at the moment) that requires to never use this option. I should have tried to go back to UGJH2.
For OCLF i'm gonna try something. I have an update showing in the market so i'm going to install the lag fix whit my application and then I'll do the update to see if it can still see the lagfix. Maybe it was my fault in the first place. You'll have feedback in 5 min.
Ok I confirm that everything is working fine. See screenshot. I don't know what was the problem I had but it seems to work fine and there is no problem to recognise the lagfix once updated.
Hi, my SGS is now running Froyo, and all apps and settings are restored. I thought that I should reinstall OCLF 2 again to maybe get some more juice from the file system, and after installing from Market and rooting the device everything seemed fine. But during installation of the actual Lagfix, I noticed an error during the "dd" command (unable to mount device, device busy, or something like that). I was offered to send the log to the developers which I did. I tried to run it again, but get the same error message. But this time the device was hanging hard and nothing I did made the error screen go away. So I removed the battery and restarted the phone. Now when I enter the OCLF app, I can only select the "Unroot device". Both "One click lagfix" and "Undo one click lagfix" are red and not selectable.
If I look (with Linda filemanager) in the root filesystem, there are two zero length files, /dbdata and /data, both created at the time that I tried to apply the lagfix. Do I dare to remove these to and see if they are causing the deadlock?
pingvinen said:
Hi, my SGS is now running Froyo, and all apps and settings are restored. I thought that I should reinstall OCLF 2 again to maybe get some more juice from the file system, and after installing from Market and rooting the device everything seemed fine. But during installation of the actual Lagfix, I noticed an error during the "dd" command (unable to mount device, device busy, or something like that). I was offered to send the log to the developers which I did. I tried to run it again, but get the same error message. But this time the device was hanging hard and nothing I did made the error screen go away. So I removed the battery and restarted the phone. Now when I enter the OCLF app, I can only select the "Unroot device". Both "One click lagfix" and "Undo one click lagfix" are red and not selectable.
If I look (with Linda filemanager) in the root filesystem, there are two zero length files, /dbdata and /data, both created at the time that I tried to apply the lagfix. Do I dare to remove these to and see if they are causing the deadlock?
Click to expand...
Click to collapse
Try removing your SD card, and then run the OCLF
If OCLF can't remove the lagfix you'll have to flash a firmware with Odin and repartition you'r internal sdcard at the same time. Just be carefull and chose a firmware that you can use to option to repartition with. Usualy all the 2.1 firmware are compatible with this option.
Then flash back with your desired froyo firmware and try CF root before you start OCLF. OCLF should not be use to root 2.2 device maybe your problem was caused by this but I doubt it.
I used OCLF with XXJPM without any problem but I flashed JPM over a clean 2.1 firmware (fresh flash with repartition option and no apps install).
Did not help. Do/Undo both still red.
I will first find a tool to backup all settings and apps before trying a re-flash. The question now is - is it worth to go through all this just to get OCLF up and running.
pingvinen said:
I will first find a tool to backup all settings and apps before trying a re-flash. The question now is - is it worth to go through all this just to get OCLF up and running.
Click to expand...
Click to collapse
Definitely!! Try Titanium Backup. It can backup all your apps and data attached. Moreover it'll be able to re-install them without prompting you for every apps. You just start the backup before the flashing and start the restore after and let it go by itself. But be carefull to backup only user apps if you go from 2.1 to 2.2 or vice versa as it's gonna cause a lot of force close if you try to backup and restore system apps that are not right for your android version.
I'm running with OCLF and I can assure you that you won't regret. No more black screen before you launch an app. Installation and or uninstallation are almost instant so your update are done faster over the market.
I was trying to disable Voodoo to try OCLF(not happy with speed with Voodoo)
So I downloaded the remove voodoo-app, and disabled it with success. Back to RFS. I'm using Froyo JPA Samsung official.
But when I try to install OCLF I get the message: "You already appear to have another lag fix installed! (/system/bin/playlogos1 les than 5KB)"
I therefor tried the "Restore boot animation"-function, and it says success. But still I get the same message when trying to install OCLF.
I have also tried to manually delete the playlogos1-file, but it seems to be coming back immediately.
Help!
Another case of not reading BEFORE applying stuff to the phone?
Usually to disable Voodoo you create a folder named "disable_lagfix" in your voodoo folder.
Then reboot to get back to RFS.
Talk about not reading??
I have already disabled Voodoo.... The problem is installing OCLF again..
Obviously something is still recognizing it as ENABLED.
That would have been worth a try.
Otherwise do a full reflash.
Mate, if you read the remove voodoo thread, it isn't the most stable app..... i'd contact that threads originator for advice.
Fwiw, I've used them both, now using voodoo with darkys 4.1 rom.
Sent from my GT-I9000 using XDA App
The only way to truly get rid of Voodoo is to reflash to a stock Rom. Even with it disabled it may have some effect on your phone and it definitely doesn't play well with OCLF. I would suggest flashing using Odin and then reinstalling OCLF---that's what I did.
Sent from my GT-I9000 using XDA App
I have a Galaxy S which i rooted and installed a lagfix on. I think it was Ryans OCLF i used for the lagfix.
I want to update to the official Froyo available from T-mobile via kies but having lots of problems getting it to connect (as everyone does). I have backed up contacts etc. I havent bothered backing up apps as i just wrote down the settings i have in each one and will just reinstall them after the upgrade.
What im planning on doing was completely resetting the phone back to factory settings and wiping it altogether so i have a clean phone to do the upgrade.
The problems im expecting or want to know how to avoid is with the root and lagfix i have installed. Will doing a factory reset or other reset (hopefully somebody can tell me another way of resetting) get rid of the root and lagfix or do i need to do something manually before wiping the phone? I know of something about the lagfix creating partitions etc so would a factory reset cancel the lagfix or would it cause all sorts of problems?
How do i go about removing the lagfix and resetting to the standard software that came with the phone? Also i have apps that require root so if i unroot the phone will this cause problems when they try to start or will they just not work and not be an issue?
Im not running any custom roms just the original one that came on the phone.
Sorry for all the questions and a rather long first post but im hoping to do this soon as the phone is running like a bag of smelly brown stuff lol.
Disable the lagfix first and then wipe. Root will not go away but I dont think that would be problem.PS. If I would be you I would just use odin to upgrade, there is plenty of good guides including how to use odin
Undo lagfix before any firmware upgrade .Then factory reset then go to Kies .
Remove lagfix as per the instructions with whatever lagfix you used .
Unroot not a problem its only a user administrative rights fix giving you greater access .
Personally i undo anything i can before an upgrade .
jje
Yes i would definitely undo everything before upgrading its just a question of how i do it.
I used Ryans OneClickLagFix app that was on the market at the time but now it has been altered because it allowed you to root and google didnt like this. I still have the original version i downloaded on the phone so is it just a case of clicking on "remove lagfix" and that will sort it?
Also if the root remains on the phone after i have wiped it, will this cause any problems when i put froyo on it? Is there not a different method or file for rooting froyo to the one i have used on 2.1?
on "remove lagfix" and that will sort it?
Correct .
jje
Also click Remove Ext2 Tools, and the go into the Scheduler changer and return it to CFG and uncheck the tweak buttons, if you messed with any of that.
In which order should i do all of those?
Should i remove the ext2 tools and return cfg settings etc to default before i remove the lagfix or after?
So just a quick update.
Something went totally wrong the other night on its own. This is before i had even thought of upgrading that night. Was sitting on facebook happily playing away when it started force closing within a few seconds of opening. Tried to open the market to reinstall the facebook app and the market force closed in a few seconds. It did this with every app including the email and phone etc. Even the RyansOCLF would forceclose so i couldnt remove the lagfix or unroot etc. All my settings for apps and launcher pro settings had disappeared. Only a couple of icons i had set on the home screen of launcher pro remained but i couldnt use any of them. All my phone logs were there and so were my texts etc but everything else had reset. When i tried to reapply some of my settings and then restart the phone, when i had finished the restart the settings i had reapplyed had defaulted again. Disaster!!
The only thing i could do was run a factory reset from the options menu. I crossed my fingers hoping this wouldnt brick the phone and alas it worked perfectly. Sorted out kies and connected the phone and installed 2.2.1 android. The lagfix had been cleared by the factory reset. I keep wondering if this is why i had so many problems with it taking ages to start up before. Maybe because the lagfix never really worked properly it never fully rebuilt the file system so was removed easily? Although the benchmarks were coming up double the speed of the fastest device on the results so not too sure how it was performing so fast with a duff lagfix...who knows. Anyway got it all up and running and rooted and lagfixed using the voodoo fix. Stuck launcher pro on setup everything. Got the apps i previously purchased reinstalled and restored any apps i wanted from titanium backup. Works like a dream and alot better memory usage aswell.
Thanks for all the help guys but it seems although i didnt follow any of the instructions you all posted (not out of choice...just because the phone physically wouldnt let me) it seemed to get the upgrade done without any problems.