yashsingh1/xdaforums huggingface dataset:
[Vibrant General] 2sh0rt:
So i searched the forums and didnt find a definate answer, maybe i didnt search the correct terms or something, idk. My question is, if you have a larger nand and voodoo DOESNT install, do you still need to run "disable-lagfix" when flashing a backup or another rom?
[Vibrant General] SkOrPn:
No i do not believe so, BUT, I would still put that file into the voodoo folder anyway. There is no harm in doing so. When you get the other rom installed and setup how you like, then you can remove it. Voodoo can be enabled and disabled at will simply by removing/replacing the "disable-lagfix" file into the voodoo folder. Its just as easy as that really...

Hope that helps.
[Vibrant General] Daddy_617:
I Really think you don't need to since your file system is still rfs,
[Vibrant General] 2sh0rt:
how do you totally remove voodoo? if i flash back to the last backup i have BEFORE installing bio1.7 voodoo will voodoo still be there or will it be gone?
[Vibrant General] Daddy_617:
I think you would need to put the disable-lagfix file/folder in the voodoo folder. Then reboot wait until it's done, then flash a kernal that isn't voodoo.After that then restore your back up. For some reason, I thought my back up was fine, but when I take the disable-lagfix file out, it would reinstall voodoo again when I boot. It might just be me, but I don't think nandroid back-ups restore the kernal. I could be wrong...
[Vibrant General] SkOrPn:
+1

Yes you need to put that disable-lagfix file into the voodoo folder on the sdcard. Reboot, it will tell you voodoo is being disabled/transformed back into rfs, once finished you can then proceed with your normal flashing routine.
[Vibrant General] Orwell83:
Linda's beautiful voice!!!

I'm a long time lurker, but I've never had anything constructive to say so I've silently read, and slowly learned how to make my phone more awesome. I'm happy to say that I followed these directions exactly and voodoo finally enabled. What a great find! Thanks!
[Vibrant General] SkOrPn:
Glad to hear another happy voodoo user, and yet more proof that beta4 works on all vibrants including larger nand variants.

Your welcome Orwell
[Vibrant General] BruceElliott:
I just did this on my confirmed large NAND phone and it works. I will let you know if I encounter any stability issues.

Quadrant 1798 before restoring apps.

Quadrant 1820 after restoring apps.

Quadrant 1690 mounted to PC

Thanks!
[Vibrant General] rogerchew:
hmmm....the eugene froyo rom flashed to error, exactly how you mentioned, but trying to flash back to stock JFD, this one is not working...odin just sits

EDIT:

Tried 2 more times, finally flashed. now i hear linda setting up voodoo!!

Confirmed working with larger NAND!! Thanks whiskey team!
[Vibrant General] SkOrPn:
Try Odin 1.3 instead, if you have not already...

http://xdaforums.com/showthread.php?t=790026
[Vibrant General] Master™:
Thanks to everyone who has confirmed this working!
[Vibrant General] Dougefresh91:
When I flashed bionix 1.7 w/voodoo it didn't work. Error log ect. Anyway since it didn't install I didn't bother to disable when I flashed 1.7 w/o voodoo. Everything turned out fine. Just an fyi since someone was asking earlier. Though adding the disable txt file couldn't hurt either I'm sure.

I'm gonna try this fix you posted, but probably not until the weekend. I just flashed 1.7 and don't really feel like going through the whole process again yet. Plus work calls and all that. Looking forward to it though and I'll report back the results.
[Vibrant General] Master™:
1.8 is almost out. So you should do it then :)
[Vibrant General] phonepersonality:
I did this earlier today.

What I SHOULD have been doing was overseeing my project, but whatever :)

It works perfectly.

z

I'm actually just testing out the "disable_lagfix" zip file in preparation for 1.8.
[Vibrant General] SkOrPn:
Isn't that supposed to be a dash - and NOT a _ underscore? example: disable-lagfix

Ive always used the dash...
[Vibrant General] Master™:
Yeah.. Its a dash
[Vibrant General] smashpunks:
wooops wrong thread
[Vibrant General] Dougefresh91:
Jeez, I can't keep up. I went from 1.4 to 1.7 mostly because it happened so fast. Definitely puts Samsung to shame.
[Vibrant General] knicks235:
ok im going to start this sucker now but before i start what is the best method to save my stuff? also im on bionix 1.8 do i need to do anything before this?
[Vibrant General] SkOrPn:
Use Titanium Backup to back everything up, it might cost but theres no app more important. IF you are wanting to try voodoo but it is not working for you, NO you do not need to do anything special. Just install the windows drivers and Odin 1.3 and follow that guide. Once you got your phone back to stock make sure you have everything ready to re-root your phone and then download Rom Manager, flash clockwork recovery, then just put bionix 1.8 with voodoo on the /sdcard, and boot into clockwork recovery and flash away... The initial start up will take slightly longer than normal because a bionic female voice called Linda has to turn your data partition into an ext4 partition, or something like that.

After that just setup your phone how you like, sign into google and start up the Market so you can download Titanium Backup again. Then download Rom Manager again, do a quick Fix Permissions, reboot, and then go into Titanium and it will see the backup it made. You can batch restore all "Missing apps with data", reboot and enjoy your new phone...

You might want to turn off phone and fully charge it to 100% and then go into recovery again and wipe battery stats. Enjoy and good luck.
[Vibrant General] Dougefresh91:
Fix permissions you say? I've only flashed 1.4 and 1.7 so far but I have yet to do that yet. Did't realize it was necessary; good to know.

But with that said I'm about to try out this fix. AppAlarm Pro isn't working in 1.7 and it's driving me nuts/making me late for work. I'm not blaming the ROM, but something's not right.
[Vibrant General] SkOrPn:
lol, yeah I use mine for alarms also. Fix permissions is just a "just in case procedure" to make sure everything runs smoothly, its a it doesnt hurt kind of thing. I find that lots of times I get very weird use out of TB, but fixing permissions first has always cleared it up for me, so its now second nature for me to make sure I do that before running Titanium. In fact I do a fix permissions before and after a titanium restore. Its just me...

Hope everything went well with your update to 1.8 and voodoo...
[Vibrant General] knicks235:
thanks for the info guys, i love this aspect of phones!
[Vibrant General] mk262:
removed question to questions forum
[Vibrant General] Dougefresh91:
I loaded 1.8 smoothly, but I can't access ODIN right now because I'm on a Mac. Apparently I didn't read very carefully because I didn't realize that the process was through ODIN. I'm thinking weekend project at this point. If this doesn't smooth things out for me I think I'll try a stock kernel because my phone has been acting weird since I starting flashing different ROMs.
[Vibrant General] justanothercrowd:
A warning should be put in the OP that this will wipe your SIMS partition.

The only way to get it back is to flash an original T-Mobile MBR.

This hack works because your phone now gets detected as an International 16GB version which we already found had the 2 diff size NAND's,

Just a warning that users should know. The 2.2 init is what overwrites the MBR and causes you to lose the SIMS game.

Voodoo will be up tonight with REAL support for Vibrant users that dont want to lose their 3rd partition for the SIMS game.
[Vibrant General] oka1:
Excellent

Thank you for the clear explanation Very well done !
[Vibrant General] Paging Dr B:
good to know JAC. I ran this procedure a few weeks back and it allowed me to finally use voodoo, but i've since flashed a stock t-mo rom via odin, then bionix again (non voodoo). After that I got a hold of the sims apk but it doesnt install properly. So my question is where should I be placing the sims game?
[Vibrant General] SkOrPn:
Awesome news, yeah JAC sent me a PM telling me how this works and how the Froyo flash was tricking voodoo into working. Hopefully now with the new voodoo we wont need this fix....

w00t :D

EDIT: Glad JAC chimed in with an explanation, lol....
[Vibrant General] rogerchew:
can't wait for new voodoo!!
[Vibrant General] SkOrPn:
probably no better than old voodoo, lol. Its JAC's kernel I cant wait for as they run so darn good on my Vibrant.... voodoo beta5 should just be another ext4 implementation I would think.
[Vibrant General] BlackVision:
Did the voodoo lag fix (Beta 5) for larger nand chip come out?
[Vibrant General] jmao:
Couldn't wait for the voodoo beta 5. Im glad this was out! Really wanted to use the master rom 1.1!! Thank you!
[Vibrant General] rogerchew:
i guess i mean, want voodoo that doesn't wipe my data cause i have a large ****.
[Vibrant General] supercurio:
Hello!

Beta5 is ready?

I didn't knew that ^^

http://twitter.com/#!/supercurio/status/27384512373 ;)
[Vibrant General] BlackVision:
Beta 5 didn't come out and I think Beta 5 is only for Froyo users now. So all those including me with the larger NAND chip will be **** out of luck unless we go for Froyo which I assume supercurio will incorporate the NAND chip issue.

I don't know, maybe I am mistaken.
[Vibrant General] rogerchew:
i think you are right on that, in terms of what's going on with beta5 for vibrants, i have no clue what the information is, neither does curio.
[Vibrant General] BlackVision:
the links for the stock 2.1 vibrant file is no longer working. is it ok just to flash from froyo a (can I install rom manager) nandroid of the stock that I made when i first got my phone?
[Vibrant General] floepie:
I love the work, but I don't understand what happened to that wonderful color fix that was talked about almost a month ago now. It was supposed to cover changes to white balance across all levels of brightness, not simply at full brightness. But, most of the talk now centers around sound enhancements. I would have thought each major fix (color, sound, etc.) to be wrapped up into their own update, or even a few updates. But, again, voodoo lag fix has really allowed me to decide to stick with this Galaxy S phone, so cheers to the dev.
[Vibrant General] The K-Zoo Kid:
Wait I'm confused.. If I can't enable voodoo, does the only way to get it working involve wiping everything?
[Vibrant General] epakrat75:
LOL. :rolleyes: Until Beta 5 comes out, yes. Did you not read the 1st post in this thread? :eek:
[Vibrant General] The K-Zoo Kid:
I did, and from what I could understand, beta5 should have come out awhile ago.
[Vibrant General] Orwell83:
Sad post

Earlier I said that I got voodoo working on my larger NAND chip vibrant, but I spoke too soon. I heard Linda say conversion complete but my phone never booted past the Galaxy S screen from bionix 1.8. I've flashed other roms since then so I assume voodoo isn't enabled (haven't figured out adb yet), but I've never had luck with any of the oc/uv kernals or lagfixes. Has anyone else not been able to make this fix work or had trouble with oc/uv kernals in general?
[Vibrant General] frankencat:
Any update on this?
[Vibrant General] rogerchew:
the information in the original post is slightly inaccurate. The OP should change it and mention it is not coming anytime soon.

But there is work being done to get voodoo on any kernel which is quite interesting. worth checking out.

http://xdaforums.com/showthread.php?t=797672
[Vibrant General] floepie:
Did JAC tell you this?

I'm not sure what's going on with this whole Voodoo thing, as it seems Vibrant 2.1 users have suddenly been abandoned with no word from the devs. Great work so far and love what they have done, but if only they could just tell us that they have moved on to strictly supporting 2.2.
[Vibrant General] rogerchew:
supercurio actually told me this, as i had a short chat with him on his irc and he was completely unaware a beta5 was even remotely available soon. he then proceeded to come on here and make his post.

http://xdaforums.com/showpost.php?p=8627579&postcount=48
[Vibrant General] floepie:
Right, but I was under the impression the "fix" for those with the larger NAND chip would arrive some time ago, so that the Vibrant port of beta4 would work for everyone with a Vibrant. Beta5 is a different animal entirely.
[Vibrant General] jeffsgalaxys:
That was my understanding as well. It looks as though the wait will be a little longer but hopefully a stable 2.2 rom will come out soon and we'll be basking in official voodoo glory. (bionix 2.0 maybe?) ;)

No voodoo = boohoo

:(
[Vibrant General] SkOrPn:
I think JAC said he would be releasing a new kernel for Eclair that will include the new beta5 voodoo fix as well.
[Vibrant General] SamsungVibrant:
what do you mean your vibrant has the larger NAND chip? some came with small ones?
[Vibrant General] SkOrPn:
Yes, your NAND is either "16005464064" or "16441671680" bytes in size. Follow the procedure below to figure out what size yours is.

http://xdaforums.com/showpost.php?p=8322865&postcount=131
[Vibrant General] gunks:
Any idea when we will be seeing Voodoo beta 5? I know we're not supposed to ask for ETAs, I figure someone may have a bit of info. <-- Larger NAND :mad:
[Vibrant General] mr2t32:
i guess this is the one time where larger is not always better? LOL... I'm bored at work.
[Vibrant General] M5devil:
Yeah.... and I was scratching my head what's going on with the Q scores. My Vibrant also has a larger NAND chip, I will try the method posted earlier in this thread. But what exactly does this mean? do larger NAND chips phones perform better or what? What was the size of the other NAND chip and why the change?
[Vibrant General] M5devil:
Very strange I followed the procedures to the T.... and after flashing back to stock all went well... except that I can't use ADB, it just won't find the device.

I odined again to the froyo, although this time it didn't show the error message on the recovery screen. At this point I tested adb reboot and it did reboot fine. I then flashed back to stock again and it passed well in odin, phone loads fine... but I can't root because adb doesn't work. I tried the OCLF from the market and it throws the error: "root device recovery 2e failed with error"

What did I do wrong? Ohh I flashed first step from Bionix 1.91... is that the problem? If yes, I redid it again already from stock the 2nd time, and still same ****.... :confused:

UPDATE:

Finally got it going flashed Fusion 1.1 and the OCUV Voodoo 1.1, so far so good Quadrant score = 1775, so it must be working with the larger NAND chip!!
[Vibrant General] johndoe411:
I am currently using Bionix 1.9/voodoo. Needless to say the lagfix is not working for my Vibrant. Can I ODIN straight to 'Froyo that does not brick' first?

The instruction on that page says I must be on a stock Vibrant ROM before flashing the 'Froyo that does not brick' rom. Does that mean I first have to ODIN back to stock JFD ROM, then 'Froyo that does not brick' ROM?
[EVO 4G Q&A, Help & Troubleshooting] twigums:
I know there are quite a few threads on setCPU BUT this is my first time using and i was wondering for my rom, kernel, and phone usage what you guys think is best to save battery but still be snappy when the screen is on.

My phone setup:

2.2 Android

2.15.00.09.01 Baseband

King CFS 10 kernel

Evervolv v0.2.1 rom

pri 1.77_003

PRL 60670

I have the phone on wifi about 90% of the time because some of my reading says it saves battery. I use my phone for browsing facebook and a few forums, send a few hundred texts a day, talk on the phone maybe 10 times a week ( im a college student), regularly on email. NOW with that said how would YOU set up the set cpu for battery life but no lag while operating.
[EVO 4G Q&A, Help & Troubleshooting] wmdunn:
You need to update your PRL ...
[EVO 4G Q&A, Help & Troubleshooting] Aerodynamix:
I always leave my main profile at 245 mhz min and 998 mhz max (ondemand mode). Then, of course, you'll want a screen off profile, and as far as that goes, I've heard that 128 and 245 draw the same voltage, so I have mine set to 128 min, 245 max (powersave mode). Other than that I just have some low battery profiles and a temp one. I don't really get any lag with this setup, but I've heard some people do. If that's the case, and I'm only talking about lag when first turning on, just up the 245 to 384 or something and I'd make it ondemand.
[EVO 4G Q&A, Help & Troubleshooting] twigums:
do i need to check set on boot under the scaling option
[EVO 4G Q&A, Help & Troubleshooting] grouse130:
No. I would leave it unchecked. This has been known to cause some issues.
[EVO 4G Q&A, Help & Troubleshooting] quocamole:
what kind of issues are you talking about? i've only heard and practice leaving it off when experimenting with overclocking (since it can put you in a boot loop). once you find a stable overclock speed, you can check it to start on boot so that you don't have to open setcpu every time you reboot if you decide to run it at that speed.

on-demand is a little less laggy (barely noticeable to me) but may consume more juice than conservative.

most kernels will step down to 245 when the screen is off so creating a profile to do that is redundant. you can verify this with the app android system info under the system tab > cpu.

having said that, i don't use setcpu unless i'm benchmarking and want to overclock.

kings #6 bfs kernel is awesome for battery life (default is conservative governor). it's what i use. give it a go when you've gotten a good feel on how kings #10 cfs is working out for you.
[EVO 4G Q&A, Help & Troubleshooting] ms79723:
Here's what I would hit up..

set it to conservative. Conservative starts your phone at your minimum clock speed and works its way up, as opposed to on demand which starts at the highest and works its way down.

then for advanced i have sampling rate at 50000

Up threshold at 95% <- that's saying that when the workload hits 98%, crank up the processing speed

Down threshold at 70% <- when the load hits 70% turn it down

That stuff right there is agressive as hell, and when I say agressive, i mean...you probably won't ever hit your max frequency unless you are seriously doing some heavy lifting. The settings there are what I use to save up battery, you can get through a day easy with everything on (GPS, Wifi, sync, 3g, the works) and with your current usage, since its similar to mine (except that i also run beejive, skype and twitter at refresh rate of 5min).
[EVO 4G Q&A, Help & Troubleshooting] Aerodynamix:
Yeah I think you've probably just seen that on some custom kernel pages. They only say not to do that because if you're testing battery life with say...HAVS, it could interfere w/o you realizing it. Set on boot just means you don't have to turn setCPU on everytime you reboot your phone.
[EVO 4G Q&A, Help & Troubleshooting] justinewing80:
just go set a profile on minimal mhz and on powersave mode if kerenal allows if not just use ondemand
[EVO 4G Q&A, Help & Troubleshooting] tonyz2897:
My problem with the "Set on Boot" option is if you accidentally fat finger the slider past your stable clock with it checked, you're looking at boot loops and possibly having to restore from a backup to sort it out. SetCPU really needs the "Set on Boot" option grayed out and a "Lock Settings" option that must be checked before "Set on Boot" becomes accessible (unchecking "Lock Settings" would also uncheck "Set on Boot").

Another option would be a user defined field for max stable clock in the advanced settings that would limit the slider on the main tab. Either one should eliminate accidental boot loops.
[Droid Incredible Q&A, Help & Troubleshooting] TrailBlazer31:
I Rooted a buddies DINC (SLCD) over the weekend using Unrevoked 3.1. The device is rooted (verified in ADB), and applications such as Root Explorer, and Drocap 2 work.

Here enters the problem. When I opened up Titanium backup it said "Could not find root". My next step was to hit the Problems button. As soon as Busybox updates there is an endless stream of root permission requests. Once you click allow about 20 times, they will stop. After you re open Titanium and click menu>Batch>Backup, again with the endless Superuser permission. I clicked allow at least 30 times by the time the backup reached 3 percent completion.

I figured maybe a quick fix permissions via ROM Manager might help. This time rom manager continued to error out.

NEXT, I figured I would install Busybox via the Busybox app on the market. I downloaded the stable version, Incredible rebooted, and once booted, I tried Ti Backup again......failed.

Next solution was to ADB push Busybox to the DINC in recovery. I got it to install, and even verified its existence with root explorer. I placed it in /System/xbin.

This fixed ROM manager, and I was able to fix permissions HOWEVER Titanium backup still CONSTANTLY asks for superuser permissions.

Also the last thing I can even think of adding to this is that I noticed that some of the root apps seem to ask for permission a little more than I am used to on my DINC. The logs are quite large.

Really have no idea why his is such a pain compared to mine. Again, like I said, he has a 2.2 stock rooted SLCD Incredible.

Any help would be appreciated.
[Droid Incredible Q&A, Help & Troubleshooting] Deltaechoe:
Look at the permissions that you have set in the superuser app, if that's alright try updating or reinstalling superuser. If that doesn't work, try reinstalling titanium. If that doesn't work try cleearing your Dalvik Cache in clockwork. And if that doesn't work reinstall your rom i guess.
[Droid Incredible Q&A, Help & Troubleshooting] TrailBlazer31:
Only thing I havnt tried is wiping Dalvik. He wants to try flashing his first ROM without loosing all of his apps. But that may have to happen.
[Droid Incredible Q&A, Help & Troubleshooting] Pons:
Also, I know it's generally obvious, but make sure Remember or Always Allow is checked. And reinstalling Superuser fixes most of these problems.
[Droid Incredible Q&A, Help & Troubleshooting] TrailBlazer31:
Wish it was all that easy. I have tried all of this lol. Titanium does not find busybix, so I doubt it is an SU issue. All the other root apps I have come across work. Like I said, I pushed Busybox, and it is now in system/xbin, but Ti still does not find it.
[Droid Incredible Q&A, Help & Troubleshooting] Frostik:
Similar issue

Hi, I have similar problem on Desire. I tried all as you and also no luck. I am going back to previous version where it worked.
[Wildfire General] axq:
Is there a patched market for the new Version 2007 yet?

Greetz, axq.
[Wildfire General] bluedragon1982:
Anyone with the new cracked market (v2007) please, i cant update installed apps like rom manager :(
[Wildfire General] axq:
Same here. Would really appreciate it when someone could patch the new market.
[G2 and Desire Z General] ChaosXIII:
While im in a call on my G2 randomly the call will end or it will get muted or it will go on speaker phone. It seems like there is a proximity sensor or a light sensor in the upper left of the phone and randomly it freaks out mid call and turns on the screen and my cheek hits some of the touch buttons. It is very annoying. Randomly ill be in a conversation with my girlfriend and it will hang up -_-. maybe when we get root access or more api access to that sensor we can turn it down or something like that. Anyone else having a similar problem?
[G2 and Desire Z General] jashsu:
This is a common problem with smartphones that use proximity sensors. Whether or not you get this problem depends on how you hold your phone to your head and possibly whether you have long hair (there is some argument about that). Some phones also do have more problems than others, suggesting it might be related to programming of the proximity sensitivity/hysteresis.