yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] frankencat:
IS there any way to uninstall Voodoo? I just installed and it doesn't seem like Voodoo is working on my phone so I would like to go back to the plain ol' JAC OC UV kernel without Voodoo. Thanks :)
[Vibrant Android Development] zephiK:
How do you know if it isn't working? Go into Terminal Emulator and type in mount

Does /dev/block/mmcblk0p4 show up there?

But if you really want to remove it... go into /sdcard/Voodoo and make a file named disable-lagfix (no extensions).
[Vibrant Android Development] frankencat:
Nope. I see /dev/block/mmcblk0p2 and /dev/block/mmcblk0p3 but not /dev/block/mmcblk0p4. Also I am gettin low Quadrant and Linpacks. Quadrants look like stock 840's and Linpacks in the 8's. Phone is very laggy. :(
[Vibrant Android Development] daddysays:
If you do not notice a color issue I would not recommend the Color Fix one. It broke my color at the highest brightness. It cast a Yellowish tint across everything on the home screens (everything else seemed the same, including pictures) but all I did was just flash the other one, and everything was fine.
[Vibrant Android Development] adm1jtg:
I am running this kernel with voodoo and OC'd to 1200 and just had a 30 min phone call... phone didn't even get warm.
[Vibrant Android Development] demo23019:
I dont have this problem
[Vibrant Android Development] IDtheTarget:
I had a problem getting bionix's ROM with voodoo to work, because I had installed and uninstalled another lag-fix.

To fix it and get it working, I had to go to this thread (bionix ROM) http://xdaforums.com/showthread.php?t=782027

and had to go through the steps entitled: "Did You Flash Something Before Disabling Voodoo? Then This Fix is For You."

Basically, it involves completely wiping the phone and re-installing a stock ROM. Once I did that and then reinstalled and re-flashed Rom Manager, I was able to re-flash bionix' rom with voodoo, and it works great!

I know that you're trying to get this kernel working, not bionix' rom, and that those steps may not work for you (I'm not an expert at this by any means), but that's what got me working.

Good luck!
[Vibrant Android Development] frankencat:
Did the "disable lagfix" and now my Linpacks are back to 9.7-9.8 range. My phone is lagging today though. Maybe I am just used to running it with the RyanZa lagfix. Hmmm......
[Vibrant Android Development] frankencat:
I had already ODIN'd back to stock and then did KK's kernel, then JAC's then this one with Voodoo.
[Vibrant Android Development] demo23019:
.......ignore
[Vibrant Android Development] angryPirate12:
I had an issue flashing the new OC/UV/Voodoo/CF kernel overtop his original Voodoo beta4 kernel. It refused to format the partition to ext4. But i found a solution, quite simple solution at that

in either Clockwork or Stock:

1) Wipe cache

Then flash your kernel*, was as simple as that for me.

*If you have voodoo already be sure 'disable-lagfix' file is created in the appropriate location before attempting
[Vibrant Android Development] IDtheTarget:
I had tried RyanZA's, and another one (can't remember his name), and they were both faster than the quadrant scores I'm getting with bionix 1.3 with voodoo. However, RyanZA's is using a loopback virtual drive and there have been many people (myself included) who found that those methods were a bit buggy and lead to data corruption and eventual crashing.

I understand that voodoo, while perhaps a bit slower, actually has an ext4 partition and is therefore supposed to be much more stable. I guess I'll find out, as my record with the loopback lag fixes was about a week before dying a horrible, gruesome death... ;)
[Vibrant Android Development] daddysays:
I wouldn't say they are straight up fake. If you notice a marked improvement in responsiveness (like myself and many others have) then it is doing what it is supposed to. The reason that the quadrant jumps so high is because of the I/O fix, which is a slight oversight on sammys part. I personally like having a higher quadrant score than my friend with an original droid, running 2.2 with a 15 linpack. Makes me feel like less of a sucker for buying this phone.
[Vibrant Android Development] daddysays:
I always wipe cache and delvik before any flash. After all it cannot hurt and seems to keep you from having problems all around.
[Vibrant Android Development] Greenarcher707:
Can i just flash this over the JAC OC/UV + Voodoo Kernel? or do i need to disable it first? - Never mind, i'll disable it anyway just to be on the safe side.
[Vibrant Android Development] demo23019:
Yea i removed that. Allot of people like lagfix and i dont want to sound like an ass.

And i wasn't saying lagfix's are fake, i said the 20k quadrant scores are.

And TBH i haven't tried the "real lag fix" voodoo so maybe i should try that before judging.

But just with stock ROM and jac kernel its very fast and i get up to 9.8 linpack i get same results with bionx 1.3 and with jac kernel and its just a s snappy and responsive...im just starting to come to that conclusion that lagfix isn't really necessary anymore
[Vibrant Android Development] ultra spikey:
Flashed the Voodoo and got faster Quadrant scores, but doesn't "feel" any faster than before. I will probably leave it on though and see how it effects the battery.
[Vibrant Android Development] rk0:
Any way to go back to regular kernel without factory resetting phone using odin? I think my phone can't handle it.

Edit: Nvm.
[Vibrant Android Development] freekyfrogy:
Running on the new OC/UV/CF Voodoo kernel, and it is amazing! I'm using setcpu to clock it at 600/1000 conservative, and my phone is like butter! With my short time using it, I have also noticed an awesome increase in battery life as well! I also love everything the colorfix does, especially allowing me to turn the brightness WAAAAAY down ^_^ Thanks so much JAC, you have really helped to make this phone useable despite all of sammy's blunders :)
[Vibrant Android Development] IDtheTarget:
I don't really put much stock in the quadrant scores, but I've noticed a HUGE difference in Aldiko. One of the main uses I have for any smart-phone is reading eBooks. Before the lag-fix, it would literally take over two minutes for Aldiko to load an epub novel. Now it's just a few seconds.

That right there is worth all of the trouble of implementing the lagfix.
[Vibrant Android Development] deez1234:
Ok I have a couple questions. I flashed this kernel over Bionix 1.3 and decided to check my quadrant score, which ended up being only about 900 or something similar. I made the decision to disable Voodoo and just go with the lagfix that is provided with Bionix (the original lagfix). I ran another benchmark and my quadrant score was around 2400. This was more of what I was looking for but I do not like the ext2 lagfixes due too a couple reasons. (Can't use CacheMate, less app space...etc) If I want to re-enable Voodoo, how would I go about doing so while also getting rid of my currently installed lagfix, and possibly reflashing JAC's updated kernel..? Hopefully this makes sense and I'm not throwing this thread in the wrong direction. Thanks for any input!
[Vibrant Android Development] speedysilwady:
wow this thing flies!!! but has anyone noticed any poor touch response when you wake the phone, wakeup lag? touch works fine after like a second after wakeup, its only before..i know its a minor gripe but im just wondering, because the previous betas didnt have this issue

P.S. Linda's voice changing pitches sure is kinda creepy =P
[Vibrant Android Development] holysmokesbatty:
With the latest Voodoo w/ OC/UV/CF the auto brightness adjusts WAY too low. At least, with mine.

Luckily Samsung added the wicked trick of sliding the note bar left and right to adjust brightness manually when you have auto turned off, which is awesome.

Not sure if this is happening to anybody else, but if it is, and it bugs you too, that seems like a decent temp fix. :D
[Vibrant Android Development] zimphishmonger:
Thanks a lot for the numerous versions of the kernel, there is a config for everyone :D

I personally was excited for the colorfix but after applying it, I noticed that at 100% my screen was way too redish for my preference. I kniw each screen is unique in the way it will look, but was wondering what everyone else is experiencing? Does the colorfix look better? Too much red, green, or blue?

Thanks!
[Vibrant Android Development] kennyp987:
I got the same thing. ..the thing is...im not one of those people who had the blueish tint at low brightness i think that could have something to do with it...im gonna flash the one without the colorfix

Vibrant - Bionix 1.3 - adb lag fix
[Vibrant Android Development] zimphishmonger:
its a feature of the colorfix. curio discovered that the screen brightness could be taken down a lot lower
[Vibrant Android Development] zimphishmonger:
Ive noticed this JUST SLIGHTLY, but not enough to make it a major issue, imo
[Vibrant Android Development] :
just a quick question. I had the leaked JI4 rom on my phone when i tried to flash this with ODIN. and now..umm... phone won't boot past the "S" screen. the screen just goes black and sits there. does this only work with the original stock rom?

EDIT: after reflashing like 6 times the os finally came up. kinda weird. disregard post.
[Vibrant Android Development] chadti99:
Wow, the colorfix makes the screen look so much better! Much more natural color reproduction, can't wait to have this update in the other brightness settings. I'm also anxious to try out the new sharpness settings, any word on when those will be public?
[Vibrant Android Development] angryPirate12:
i noticed this too, it jumps back and forth a lot, and i'm in a severely dim light room.

I am having color issues as well, when the brightness is cranked up the home screen turns redish, and at low levels its blueish. Now with the brightness cranked up, when I launch the Web browser and other various apps, the color turns blueish. Whenever I hold the home button to bring up app switcher with the brightness up and the browser open (blueish) the screen switch's back to being redish until i close the app switcher then its back to blue in the browser.
[Vibrant Android Development] s0niqu3:
Lol, exactly my experience, my screen never seemed overly cool/blue before, and with the colorfix version of the kernel its WAY too warm for my preference too, so much so that blacks look reddish/sepia tinted, and that's too harsh for me. I also don't really notice a difference in sharpness and clarity of fonts between colorfix and regular voodoo kernels. Just goes to show that there's a pretty wide range of manufacturing variance in these OLED panels.

Anyway, I tried taking screenshots to post, one at full brightness and one at zero brightness, but neither show the tint, and in fact they look 100% identical, lol. My guess is that ddms (my preferred method of taking screenshots) must draw screenshots from the pixel color and layout information in the apps, etc., and ignore the actual device brightness/color/rendering settings. I'm guessing this is fairly universal among screen capture applications too, and it would explain why the demonstration images on the voodoo website were all simulated.

Oh well, still exceptionally happy with the OC/UV + voodoo kernel for now, cheers JAC on an amazing job, and thanks Curio and everyone else that helped make this kernel a reality.
[Vibrant Android Development] kennyp987:
Anyone notice better data signal and speed with this kernel? I have. :-)

Vibrant - Bionix 1.3 - JAC's Xmod kernel- adb lag fix
[Vibrant Android Development] zimphishmonger:
You explained it much better than I did. It is way too warm, so much it skews other colors. Hopefully we'll see variants of mod with different settings. No reason why it couldn't be tuned by the user :-)
[Vibrant Android Development] Generic112:
I have a question regarding flashing this kernel. I have bionix 1.3 with kingklick's kernel, can I simply flash this kernel over my current set up? Also, how can one tell if their Vibrant is capable of using Voodoo b4? Should I just try it, and if it doesn't work, my vibrant can't use it?
[Vibrant Android Development] justanothercrowd:
Yes the ColorFix is still in beta and the FULL color changes are only present at 100% brightness. This is the reason I offer my Kernel with ALL options possible, because it may not be for everyone at this point. But I did want to give people the opportunity to experience what has been done so far...and it also shows how much control we can have via software over the SAMOLED screen ;)

The ultra "low" light setting is intentional. The Colorfix may not be for everyone at this point but it will continue to be fine tuned :) Again that is why there is versions with and without it and there will continue to be. Options are what is it is all about and I won't restrict anyone to one or the other.

For a FULL description of the Colorfix please visit http://project-voodoo.org/color

MY battery life on the other hand has been outstanding. I hope you are seeing the same results. I will continue to tweak the OC/UV settings but we are already pretty low in comparison to other UV kernels.

Enjoy!
[Vibrant Android Development] joshthewaster:
That would be cool. I'm hesitant to try the colorfix as I'm very happy with my screen and haven't noticed any tints so I don't want to "correct" anything.

But due to this it's tempting. I almost always use the phone indoors and have no need for the screen to be as bright as it is even on the lowest settings. That on top of the fact that my battery usage is 65% due to the screen makes me want this even more.

With this kernal I'm seeing a pretty good jump in battery life when the screen isn't on (like it barely drops at all) but again anything to help out the life is good by me.
[Vibrant Android Development] thiscashbox:
Hey, I would also like to know if there is a possible way to tell if your Vibrant can handle the Voodoo fix.

Also if it can handle the UV and the OC to 1.2, I get random lockups when I set the clock speed to 1.2.

Thank you in advance for any input.
[Vibrant Android Development] Relikk356:
I started to get a lot of force closes after I installed setcpu. It ran great at first, but after long periods of no use system files would fc. First thought was my cpu couldt take it. So I started monitoring my cpu speed. The fastest it got was 1029. Seeing that it's 45nm it should for sure do 30htz more. So I assumed it was a setcpu problem. Uninstalled used the script on OP page and its been fine ever since.

Update.

LP score is higher now at 9.88.
[Vibrant Android Development] justanothercrowd:
First in either Terminal or ADB shell

cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size

Then take the output of that and multiply it by 512. If it comes out to "16005464064" Then beta4 will work for you. If you end up with a value of "16441671680" then you have the 416MB larger NAND chip and will need to wait untill beta5.

This has been updated in the OP to keep people from having issues.
[Vibrant Android Development] Generic112:
Thank you very much. I can use voodoo b4, so I'll be flashing that kernel when I get home. Again, thank you for the quick assistance.
[Vibrant Android Development] w_bovine:
Now THAT'S what I call very specific and useful information. Big thanks for this...it explains why I had no success with Voodoo before and just saved me from trying to install it moments ago. Fine work going on here. :)
[Vibrant Android Development] joshthewaster:
No kidding. Thanks JAC. found I can run beta 4 so I think I will give it a go.
[Vibrant Android Development] w_bovine:
Ah yes...I know what CacheMate is for! :)
[Vibrant Android Development] geoffcorey:
What is Colorfix that's being incorporated into this kernel and what does it do?

Sorry, i haven't been following too much of the kernel development.
[Vibrant Android Development] joshthewaster:
http://project-voodoo.org/color
[Vibrant Android Development] geoffcorey:
thank you very much.
[Vibrant Android Development] redwolf313k:
This kernel really shows you the potential of the super amoled screen works great.
[Vibrant Android Development] epakrat75:
Thanks so much! This confirmed what I already suspected. Originally, I thought I had done something wrong but when news of beta 5 hit, this was the logical conclusion.
[Vibrant Android Development] geoffcorey:
if i flashed this kernel but didn't do anything for OC, would i still notice speed and battery improvements?
[Vibrant Android Development] joshthewaster:
I certainly have. My battery hardly moves when the screen is off so it's lasting much longer than it was before. I had mine OC'd for a bit but just didn't need that but even without it everything seems much smoother.

I'm restoring a backup right now as something went wrong with the install of the version with colorfix. Not sure if it worked but I'll find out soon. I'm really interested to see what it does.

Edit: SO the kernal obviously flashed even if something else went screwy, my screen was dim as hell. I like that I can get it even lower except that it seems to jump from the stock low to the new low, there isn't a range of in between values.
[Vibrant Android Development] frankencat:
I had a some performance issues with this after a couple of days - lots of lag in certain apps like facebook and dolphin, my gmail stopped sending outgoing emails - so I am going back to stock ROM + lagfix. That seemed to work the best for me.
[Vibrant Android Development] IDtheTarget:
I got 16441671680, but I loaded Bionix' rom with Voodoo last night. Do I need to remove it?
[Vibrant Android Development] msimpkins14:
I'm liking this kernel for the most part , but do have a question. Is anyone else having "my location" issues? I can't get any fix whatsoever unless enabling GPS and its affecting performance of some apps... Am I alone on this? I've redownloaded and am still having same problem...
[Vibrant Android Development] codester3388:
I'm trying to figure out if this is a hardware or software problem. I didn't have my phone stock for very long (30 mins) before it was rooted and had a custom ROM and kernel on it. But ever since I started installing these mods, every once in a while after I lock the screen or after it goes out by itself.... it won't turn back on or the buttons won't respond to any presses so I have to pull the battery and its fine. Has anybody else had this problem? This is one of those $.01 Vibrants from Amazon a month ago.
[Vibrant Android Development] frankencat:
Yes. That is one of the issues I am having.

I just ODIN'd back to stock and am restoring my last nandriod backup. I think I will give King's another try or maybe stick with the stock ROM + lagfix. That seemed to work best for me.
[Vibrant Android Development] Reyland:
when i'm in a dark room the screen brightnes decrease i think is supposed to be the other way? Or not?
[Vibrant Android Development] codester3388:
My problem is it was doing this in the Vibrant9 ROM, Bionix1.2 and 1.3, and now the new FTwiz ROM. And had the OCV4 kernel, KK kernel, and now this kernel and all of them seem to do that.
[Vibrant Android Development] mikey98277:
If your using Setcpu that could be the issue, if you have it set with the wrong options it will cause the issue you are describing.
[Vibrant Android Development] codester3388:
I have SetCPU. I use the autodetect and keep it on conservative and it still does it if I'm at 1200MHz or 1000Mhz.
[Vibrant Android Development] MINUS Stl:
What's your min set at? Too low and it'll cause that. I keep mine at 400 min and don't have any problems. Others may be able to go lower, but I'm not sure.
[Vibrant Android Development] w_bovine:
You have your minimum at 400? No extra battery drain? I knew not to go below 200, but never thought about setting it higher.
[Vibrant Android Development] demo23019:
what happens when set lower than 200?

mine is at default 100mhz and seems ok
[Vibrant Android Development] w_bovine:
I've read about crashes and lag when set below 200.
[Vibrant Android Development] demo23019:
thanks, yea i haven't had issues yet but if do ill bump to 200
[Vibrant Android Development] msimpkins14:
Multiple tests and my phone still can't obtain a cellular triangulation for my location without gps. Any clues as to why developer? I really appreciate your work but never had this problem before.
[Vibrant Android Development] matt_stang:
Is there supposed to be a noticeable difference with the color fix?

EDIT: Wow, never mind. There is a huge difference
[Vibrant Android Development] MINUS Stl:
You know, I don't think I've tried 200. I've done 100 a few times and it always ended with me having to reboot. Going to see how 200 treats me.
[Vibrant Android Development] heatx:
Epic with the voodoo lag fix. Smooth as butter.

Thanks for this!
[Vibrant Android Development] w_bovine:
It turned your Vibrant into an Epic? Good Lord man! :eek:
[Vibrant Android Development] GTOJim:
How does one go about flashing it back????? :)
[Vibrant Android Development] scrizz:
i wonder if the colorfix can be had separately.

I'm on a 2.2 ROM so.....

:(
[Vibrant Android Development] d33dvb:
What's tge colorfix?
[Vibrant Android Development] Relikk356:
My min was set at 100 and explains the problem I posted below.
[Vibrant Android Development] w_bovine:
Doesn't look to be a separate download for anyone yet.

http://project-voodoo.org/download
[Vibrant Android Development] kboater:
so im running just the kernel. what are the best/recommended settings for set cpu, or how do I check to see what Mhz im currently running at?

I currently have cpu governor set to conservative and auto refresh checked. my max is set at 1200 and min at 400. with set cpu open, the number at the top left above scaling conservative, is that the speed im currently running?

also, the set cpu widget gives me current temperature, what temps should i be looking for? just want to make sure i can keep an eye on overheating

thanks
[Vibrant Android Development] w_bovine:
People seem to be using 200-400 for the minimum and of course 1200 as max. I'm trying it out with 400 minimum right now.

I read somewhere that you want to use Conservative scaling for the Vibrant...fine by me. Now that I think of it I think it says that on the app's Market page.

SetCPU should tell you in big bold number what the current speed it. It will of course fluctuate depending on what the phone is doing. Not sure if there's a widget that might tell the same thing.

I've never had a temperature problem to date. I've seen it as high as 109° and there seems to be no ill effect. Normally I'd guess it's in the low 90's.

Have you made any profiles in SetCPU? Might be worth looking into. I've got a few set, one for throttling down if the temperature gets too high.
[Vibrant Android Development] Bronk93:
Just installed the color fix version....The whites are def brighter, what I did notice is the color difference while playing Homerun Battle 3D. The images do not appear to be as sharp and there is def a warm color tone to it, not sure if I like it or not but everything else is beautiful.
[Vibrant Android Development] kboater:
thanks for the response. this is my first time using set cpu on vibrant. I was using it on mt3g. i was never very successful in creating my own profiles. any tips?

btw, with everything stock, my linpack was avg 8.1 and quadrant about 880

now just running oc/uv kernel (no voodoo) my linpack avg is 9.73 and 950 quadrant

thanks for all the help and thanks JAC
[Vibrant Android Development] w_bovine:
No tips really, as I'm just getting used to it myself. So far so good though. I do know you can set priority levels for the profiles. I have the temperature profile set at a higher priority than the screen off profile, for instance.

I haven't benchmarked the phone...I'll probably just skip doing that or else I might make myself a bit crazy. :D

I'll be trying Voodoo when Beta5 comes out. I'm running Bionix, and it sounds like 1.4 should be out in a few days. I'm hoping I don't have to run ODIN and get back to stock to get Voodoo to work, but that remains to be seen.
[Vibrant Android Development] kboater:
ive yet to learn how to use odin. You have to use odin to flash Bionix rom right?