Database Develop

[Q] I9000M and Voodoo or OCLF lag fix

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.

[Q] Reinstall Voodoo

Hi
Galaxy S, Froyo, Voodoo kernel:
I'm thinking about disabling Voodoo to try OCLF and see if it is faster. Therefor I wonder a few things.
Does OCLF work with the Voodoo kernel installed?
I understand I just create the file/folder voodoo/disable_lagfix to disable the Voodoo lagfix, but how do I get it back if I don't like the OCLF? Just remove the file/folder and reboot, or is it more complicated then that?
And lastly: Any thoughts on which is better? OCLF or Voodoo? My Galaxy S isn't superfast with the Voodoo, thats for sure.
Thanks

Decided to try.
Downloaded the remove voodoo-app, and disabled it with success. Back to RFS.
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.
Help!

Can't someone please help me!

Just put voodoo back on in my opinion.
But if you MUST try it you might have to put a stock kernel on. Isn't there some oclf option that refers to that playlogos file or whatever it is?
Sent from my GT-I9000 using XDA App

[Q] Lag fix removal and upgrading to 2.2.1

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

[Q] How to Re-Root a *Half* Rooted Captivate

I seem to have a recurring problem with my root on the FireFly 2.8 rom, though it may have been present on Serendipity and I never noticed.
My problem is this: Before I flashed FireFly, I used Odin to revert to stock 2.1, master cleared, and then rooted using the One Click Galaxy S root, which worked fine. I was able to flash the rom using CWM and Titanium Backup as well as other apps that require root said they had proper permissions.
At some point, I do not know where, I lost my root. Now, when I try to use Titanium Backup or Firefly fixes, the app tells me Root access FAILED.
I have superuser as well as the current busybox. Can anyone help me with possibly telling me how to enable my root or how to reroot if necessary?
I have tried z4root but it never does anything anymore.
And when I try to use the One Click Root again I can not click "reinstall packages" because I am taken to CWM instead of regular recovery.
Any help would be appreciated, thank you.

You probably converted system to ext4. Go back into Recovery and go to the features of whatever kernel u are using and reapply root.
Sent from my Captivate running Continuum 4.0 with Onix 2.0.5.

I was neveraware you had to reroot after converting the system to EXT4. Worked like a charm though! Thanks for your help.

#1 in CWM "reinstall packages" is the 2nd option down! called "apply update.zip" (kinda makes sense doesnt it?)
#2 if you have CWM you can root without one click root.
boot to CWM recovery> Clockwork Features > root + install superuser
adv

Edit: Nevermind, looks like someone already solved your problem while I was typing my BS out.

skrallbro said:
I was neveraware you had to reroot after converting the system to EXT4. Worked like a charm though! Thanks for your help.
Click to expand...
Click to collapse
You don't normally have to....

I has this same problem with FireFly 2.8. I never had that issue with older versions of FF. But, as mentioned, if you reapply root in CWM, it works again.
I love the FF themes, and stability, but I may go back to FF 2.6. FF 2.7 had charging death for me, and FF 2.8 I have issues with keep the lights on. That's how I found my root issue. Now, with the root fixed, keep the lights on seems to disable itself after a while. Definately after every reboot it turns back off. I never had this issue before with cog, perception, or any of the earlier FFs.
Sent from my SAMSUNG-SGH-I897 using XDA App

Your rom probably came with a kernel that implemented lagfix upon first boot. It happens if you manually apply lagfix as well and re-rooting in CWM works like a charm all the time.

Elisha said:
Your rom probably came with a kernel that implemented lagfix upon first boot. It happens if you manually apply lagfix as well and re-rooting in CWM works like a charm all the time.
Click to expand...
Click to collapse
All the FireFly versions I have used have the lagfix optional, and applied through CWM, but 2.8 is the first one that applying the lagfix affected the root of the ROM. I also didn't have this issue with Cognition or Perception, both of which apply the lagfix on first boot.
So the kernel is the issue, not the ROM? A different kernel may fix this?
Sent from my SAMSUNG-SGH-I897 using XDA App

quarlow said:
So the kernel is the issue, not the ROM? A different kernel may fix this?
Click to expand...
Click to collapse
Yes and no. losing root from converting system to ext4 or back to rfs, can happen with any kernel, and for the charge death that was the onix kernel in those versions. The keep the lights on, does that kernel have bln options in cwm? I use sp voodoo do idk.

i have never lost root converting my system
but i havent converted it in over a month. Just leave it EXT4 when i upgrade/change roms.
havent had any problems not converting it so i dont bother. (except going to stock)
but when i used to convert back and fourth every flash out of fear... NEVER LOST ROOT

I've only lost root converting on Continuum but never on FireFly or Apex so not sure if it is kernel or rom.
Sent from my GT-I9000

studacris said:
The keep the lights on, does that kernel have bln options in cwm? I use sp voodoo do idk.
Click to expand...
Click to collapse
Yes FF 2.8 has bln options in CWM. I have issues with bln active or disabled (in FF 2.8). I have not tried managing the bln with the app from the market, would that make a difference (vs managing bln in CWM)?
Sent from my SAMSUNG-SGH-I897 using XDA App

LagFix Doesn't work? Can't Flash

Ok, so I have a stock 2.2 FW and I have really bad lag, especially with text messages. So I installed the OCLF from the market, installed the exttools, rooted the phone and did the lagfix v2. It didn't fix the lag. I still had the same exact problems as before. So others suggested using a ext4 kernal. However, my phone can't get into recovery or download mode. I have a phone I find out that will eventually have the shutdown problem. So I decided I would just trade the phone in.
However..the OCLF that has an unroot option..doesn't work for 2.2. So can't do this till I unroot. I thought about using the ADB Tools, but without a 2nd way to get into recovery/download, I didn't want to risk this.
Is there a different market app that can unroot since ryzes doesn't work? Also..any reason why the lag fixes wouldn't work at all? I mean..i get a text message..entire phone freezes for a good minute..recieve 2 back to back..yeah stuck for a while. Also..since I uninstalled the lagfix and ext tools..however..now I can't download any apps with error of insufficient space...I have 9 gigs free.
Anyone else have these sort of problems?
Appreciate the help, thanks!

Uninstalling the "lagfix" does not convert the file system back to rfs it is still in ext2, which is really antiquated btw, that is why you are getting the insufficient space error.
I'm pretty sure Super one click will un root you, it isn't an app, its a pc based program so you would plug your phone in via usb and unroot.

So how do you covert back? I UN did lag fix undid root undid ext tools but still have space problem.
I will try super oneclick. Was hoping to do through phone so could exchange today. The lag is really awful and making phone not able to unstall apps or save pictures wasnt good fix anyway :/.Curious as to why lag fix didn't work though.
Sent from my SAMSUNG-SGH-I897 using XDA App

that "lagfix" is super old. ext2 as compared to ext4 which is the current filesystem for "lagfix", that And the stock rom is pretty crappy also. and only goes up to android 2.2.

So think they would replace phone that is rooted if its in the O'Neil range of power problems?
Sent from my SAMSUNG-SGH-I897 using XDA App