Voodoo Lagfix is actually disabled: next boot enabled

[CobraStyle]

i'm on superclean 2.8 with Voodoo kernel. I'm not 100% sure lagfix is enabled though. a few of the tests seem to indicate it is, but i get the "Voodoo Lagfix is actually disabled: next boot enabled" everytime i look in CW and my quadrant score is around 900 when everyone says it should be 1200 or higher...

Any thoughts on if it is truly enabled or how to enable it if not?

P.S. I don't have the disable-lagfix file in my voodoo folder.

 

[TheSonicEmerald]

Its enabled. The only instance when its diasabled is when it says next boot:diasabled.

—-----------————---------------
Still rocking DJ05 with Voodoo5 Blazed Eclair 1.2ghz with GingerLiberty
------——-———-----—----—------
Sent from XDA Premium App
----------------—-----------------
DungeonDefendersUsername: TheSonicEmerald

 

[GizmoDroid]

Yes, this is just a superficial glitch in the newest CWM.

I'm sure it will be fixed in newer releases.

 

[GizmoDroid]

—-----------————---------------
Still rocking DJ05 with Voodoo5 Blazed Eclair 1.2ghz with GingerLiberty
------——-———-----—----—------
Sent from XDA Premium App
----------------—-----------------
DungeonDefendersUsername: TheSonicEmerald

You have... something going on with your signature. You don't need to put it in the XDA app if you have it on the forum too.

 

[CobraStyle]

Thanks.. Any reason my quadrant score would be this low then?

 

[thande]

I had this problem with the EB16 voodoo kernel. Check the newest SC 2.8 post http://forum.xda-developers.com/showthread.php?t=983395 and grab the EB01 voodoo kernel. Boot and wait for the conversion then reboot and reload the EB16 based kernel if you want. That will properly enable voodoo.

 

[tonu42]

I had this problem with the EB16 voodoo kernel. Check the newest SC 2.8 post http://forum.xda-developers.com/showthread.php?t=983395 and grab the EB01 voodoo kernel. Boot and wait for the conversion then reboot and reload the EB16 based kernel if you want. That will properly enable voodoo.

What this guy said. Worked for me.

GizmoDroid Yes, this is just a superficial glitch in the newest CWM.

I'm sure it will be fixed in newer releases.

He is a moron, talking about newest CWM does not even pertain to the OP.

 

[CobraStyle]

Thanks thande...This solved my issue exactly...

 

[GizmoDroid]

What this guy said. Worked for me.


He is a moron, talking about newest CWM does not even pertain to the OP.

I didn't clarify myself... which apparently has upset tonu42. I'm glad he was here with his wisdom to guide you to clarity.

My post only addressed the graphical glitch in the newest red CWM where on a properly converted system, it will always say:

Voodoo lagfix is actually: disabled
                        next boot: enabled

My post was only meant to verify that, despite the bug in CWM, that you had the correct settings. Whether or not your partitions were converted, I did not address.

My apologies; I started the post then had to leave so I cut myself short without making this apparent. I'm glad you figured it out without me, and I hope that some day, tonu42 can find it in his heart to forgive me.

 

[ivorycruncher]

For those wondering how to determine whether or not the lag fix is enabled, there is a very easy way to tell. Within a terminal emulator app, just type in the command "mount" with no quote marks. That will show you all current mount points in the system. Now, in the first few lines of the output, you will see the mount points for /system, /cache, /dbdata, and /data. Those should each say ext4 after them if the lag fix is enabled. If the lag fix is not enabled, they will say rfs, or something other than ext4. This method will tell you beyond a shadow of a doubt whether your lag fix is enabled or not, regardless of what CWM says.

Sent from XDA Premium on my Super Clean Fascinate

 

[GizmoDroid]

Yes, and for future reference, and learnin', this is the thread to read (has everything we've discussed here and more):

http://forum.xda-developers.com/showthread.php?t=979744