yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] kamots:
you rock zilch! thank you:D so how hard is it to crate this file on the sd card?:o its simple as a file manager create new folder named disable lag fix in the voodo folder? i assume that the voodoo folder is automatically created when you install this right? bad things happen when I assume things though lol:p
[Captivate Android Development] Zilch25:
Nah if you're getting 1400-1700 scores the fix is applied. It's EXT4 and it's actually ya know... doing something other than testing an artificial buffer in quadrant, so don't expect the quad score to be as high... the real life improvements should speak for themselves though
[Captivate Android Development] Zilch25:
I do what I can!

As for the voodoo folder, it's created as soon as you apply the kernel initially, and creating the disable-lagfix file is as easy as creating it with any file manager. I used root explorer to add it. Once you reboot the soothing voice of creepy robot lady will inform you of what's going on.

Remember after removing the fix, as soon as you remove or rename that disable-lagfix file it will reinstall on next reboot!
[Captivate Android Development] Hellerox:
What happrns if I already had one click lag fix by RianZa and installed this over that one? Everything seems fine so far
[Captivate Android Development] Smallsmx3:
So it can lay dormant in the phones sd.... creepy... not really. So to get rid of it forever wed have to delete the file from sd?
[Captivate Android Development] Zilch25:
It shouldn't have worked right unless you removed the previous lagfix... then again you might just have an EXT2 file living on top of the EXT4 partition O_o
[Captivate Android Development] warri:
Agreed, once OC/UV arrives it will be the ALL POWERFUL KERNEL

I'm not going to lie here. I am super impressed by the improvement and stability of this fix. I installed from Fresh Clean Stock JF6->JH7->Voodoo, then used TIBU and let me just say, TIBU Ran 10X Faster then normally. Installing Apps at lightning speed!

I have not had 1 FC or 1 Random Reboot, or anything. Extremely Surprised, and excited. Keep up the good work, and some donations will be coming your way !
[Captivate Android Development] KaLiBLeeK:
I wakeup, and see an announcement about Voodoo for Captivate on Twitter...AFTER I had already made my coffee run.

This is turning into a most excellent Thursday. Haha.
[Captivate Android Development] Hellerox:
What happens if I apply this fix over One click fix by Ryanza?
[Captivate Android Development] warri:
It will break, remove lag-fix first
[Captivate Android Development] Zilch25:
In order to get rid of it you actually have to use the disable-lagfix method, otherwise it will still leave remnants on your NAND that will prevent future installs of the lagfix kernel.

If you have already botched this up, placing the disable-lagfix file into the voodoo folder WILL botch up your current install, but it will also fix the problem for future installs- so you're never truly screwed
[Captivate Android Development] iamamp3pimp:
i left some things out i suppose..lol

Having a couple FC issues with Root explorer so im running fix permissions and waking from a reboot now.

Still FC on root explorer. Restored it with TIBU and it works.

:)
[Captivate Android Development] Hellerox:
What happens if I apply this fix over one click fix by ryanza? I forgot to remove it
[Captivate Android Development] iamamp3pimp:
that must be the case then as i ran the ext2 patch awhile ago and never undid it.

when i tried using sl4a it rebooted quickly and seemingly no changes were made.

so far so good though.
[Captivate Android Development] Zilch25:
... well, now you have an EXT2 file installed on your new EXT4 partition- you could try to remove it after the fact and it might work, though you're in uncharted territory here.

You could also use the lagfix removal method that I typed up before using the disable-lagfix file in the voodoo folder, THEN removing ryanza's fix, THEN remove the disable-lagfix file which will reapply the kernel lagfix
[Captivate Android Development] atinm:
Color is not enabled - that is part of the kernel and I didn't port that over to the Captivate because I wanted to leave this clean of everything.

-Atin
[Captivate Android Development] kamots:
this was my next question. lol how to get rid of it permanently is need be lol
[Captivate Android Development] Zilch25:
Hey Atin, one thing I've noticed- it's subtle but I'm not sure what could be causing it- at least when running Quadrant I'm seeing dips in FPS that weren't usually there with previous kernels- not sure what to make of it, and I'm not sure if it makes any difference but it's there
[Captivate Android Development] b0bfath3r:
This is awesome. I have never seen my phone fly like it is now. Thanks for your hard work atinm and supercurio!
[Captivate Android Development] atinm:
I did the OP at 2:45am my time - it wasn't the highest priority for me, putting up a working .zip for people to use was and I'm sorry I didn't stay awake longer. Anyone who has trouble with my only fixing the SRE turds I left over from my development build in the first update.zip within 6 hours, please accept my apologies and if possible, never use anything I build again. Thanks.
[Captivate Android Development] gtg465x:
Clean is good. Not really digging unhelpful's oc/uv kernel right now. Too many people seem to be having problems with the latest versions and I could never play certain games without freezing at 1.2GHz. I'm sure unhelpful's kernel will be great eventually, but I don't think it's there yet.
[Captivate Android Development] KaLiBLeeK:
So some issues I had with my installation of JH7/SRE 1.3.1c over the weekend seemed to have reared their head; couldn't get past the AT&T screen after using SL4A to remove the old lagfix.

One-Clicking JF6 right now, then doing everything else and installing this mofo. Thanks a ton for porting this over atinm; I haven't even tried this out yet, but I will be using stuff you build in the future. Haha.
[Captivate Android Development] ranova:
I've never used init'd for anything, how do you enable mobileAP with this lagfix?
[Captivate Android Development] Zilch25:
You may not have, but that's the method SRE has used to enable it since... forever. So if you had another method of enabling it you might have to go back to that
[Captivate Android Development] Smallsmx3:
So does rom manager work with this yet? I know i read in the voodoo thread that a backup couldn't be made with this fix enabled
[Captivate Android Development] ranova:
I'm not currently using SRE (too lazy atm to flash to stock) and just using designgear's standalone MobileAP package, which I thought had actually flashed your kernel.

My current speedhack is the NAND hack (the old one limited to 130mb of app space), so if I revert that hack and update with this, will everything work dandy with mobileAP?

I'm on the stock JF6.
[Captivate Android Development] Zilch25:
Chances are the reason his mobile AP package works is *because* it flashes the kernel. Flashing the kernel to Unhelpfuls kernel adds init.d support which in turn enables the MobileAP feature... you can verify this by browsing to:

/system/etc/init.d and seeing if theres any files in there (You'll need root of course)

And yes you'll have to revert the NAND hack, but your MobileAP will still be shot until the version of this kernel with init.d is released
[Captivate Android Development] ranova:
yep, you're correct (as usual :))

I have S_mobile_ap_service in /system/etc/init.d

I guess I can still execute mobile ap manually each time by running /system/wlp2pservice

Has anyone tried this on the stock JF6 firmware?
[Captivate Android Development] designgears:
Ditto, no init.d, no MobileAP, no sideloading, etc...
[Captivate Android Development] atinm:
Did you even do a checksum before you made that comment? And relax - it isn't like you were not credited on the first release (gone now).
[Captivate Android Development] mircury:
Thanks for your incredible work and getting it to us end users as quick as possible! I think you, supercurio, DG and all the contributers of fixes and code for our phones are incredibly talented people. Keep up the good work.

Donate to these people!
[Captivate Android Development] atinm:
No - right now you cannot flash Unhelpful's OC kernel yet because it will overwrite the initialization and it doesn't support EXT4. But I am forked from Unhelpful's kernel and the next item of business is to incorporate his latest work into my build as well. This includes the init.d work for allowing sideloading, mobile-ap etc.
[Captivate Android Development] atinm:
Yes, Odin will put you back to stock though the EXT4 is left on there. Cleaner way is for you to get to the internal sdcard and put a file named disable-lagfix (empty or whatever, doesn't matter) in the Voodoo directory and reboot. It will convert the filesystem back to Samsung's (R)etarded (F)ile (S)ystem.
[Captivate Android Development] atinm:
No color fixes from Voodoo. This is as vanilla as I could get it.
[Captivate Android Development] designgears:
wow...

adding a single space to the end will change the checksum

like editing the ui_print to something else..

all of my init.d scripts are there

unhelpfuls kernel is still there

the script used to flash was changed to point to a different directory with a different kernel

the update-script is identical besides the header

shall I keep going?

looks like your new release is just the kernel... so, thank your for removing SRE
[Captivate Android Development] atinm:
To get rid of all traces of it, you would have to reflash to stock. Otherwise the kernel init will always look for the disable-lagfix file and if not present, it will convert your /data to EXT4.
[Captivate Android Development] designgears:
No longer contains sre

Thank You. Bye now.
[Captivate Android Development] atinm:
It does not - supercurio is working on it and I am not spending any time on that. If you want to do it, disable-lagfix to go back to RFS first.
[Captivate Android Development] jslee1020:
to clear up a few points on this... I read a few pages... I think it was zilch who said it... that previous lag fixes will not be removed by odin 1 click?

Is that correct? Was he referring only to ext4 lagfixes or ext2 lagfixes as well?

I was under the assumption that odin 1 click reverted everything back to stock (i.e. OC/UV/ext2 lagfixes?)
[Captivate Android Development] Kaik541:
DG, I mean, maybe he ripped the update process and stuff from yours, but isn't that just a sign of how stable your work is? aren't you overreacting just a little? this kernel could lead to amazing things and he's clearly interested in collaboration since he's working off of Unhelpful's base. he even credited you originally, but you're kind of blowing up over it. do we really want/need to drive developers AWAY from working on the captivate?

clearly it was an accident, he even mentioned this on more than one occasion. we all make mistakes late at night (you've uploaded your personal versions of SRE on more than one occasion because of late hours), so maybe cut him some slack and see he's trying to move on to just the kernel?

edit: ok, I see you've caught up and have accepted the mistake, sorry for the complaining
[Captivate Android Development] atinm:
Which will be tonight if I can stay awake after having stayed awake 3 nights in a row! Thanks Zilch25 for all the support you are doing for this - I'm too tired to really think straight right now.
[Captivate Android Development] supercurio:
Hey atinm, you did well, don't bother with the this crazy SRE story :)

Congrats bro.

Following the pretty good reports so far, we will publish it soon to http://project-voodoo.org/ i think, and target a much wider audience which wont be obsessed but just happy with the great working solution.
[Captivate Android Development] Kaik541:
I'm worried about what will happen to this phone's support community if Zilch were to leave or (heaven forbid) get a different phone. I can't pick up the slack there, I'm way too lazy =P
[Captivate Android Development] Zilch25:
If you have previous NON voodoo lagfixes the one clicks will remove them. If you reflash with the voodoo version installed it will leave traces behind, though you'll still get a functioning install.

Most of the problems (at least judging from previous version of voodoo) that you'll encounter will occur when you try to reinstall voodoo again since it doesn't fully remove the EXT4 stuff it created initially. There could be more to this, but it's good practice to disable-lagfix before every firmware/rom/whatever flash. At least until a UI that does it for you is created :)
[Captivate Android Development] atinm:
Like I said - it was late, I left the build in that state because I wanted to get it out to people and so I credited you for the damned scripts even though I knew I'd be taking the stuff out after I woke up because the whole goal was to create a clean install.

-Atin

p.s. The fact that the script was pointing to a different kernel made you think that I was still using the kernel you include and it gave you all that bile you had to spew - wow.

I'm sorry. Really.
[Captivate Android Development] Zilch25:
Anytime :) I've been following this since it was just a peep from supercurio in the bounty thread- so I'm about as well-versed as a non-dev can be! This has been a long time coming and the work certainly does justify community support
[Captivate Android Development] designgears:
Had he just PM'd me and been like, HEY I WANNA USE THIS!!

I would have been happy to let him, hint hint...
[Captivate Android Development] Zilch25:
Nah, I'm too cheap and lazy to upgrade my phone- at least until my contract is up :D

I should put a donate link up and hold myself hostage!
[Captivate Android Development] atinm:
Thanks! :)
[Captivate Android Development] kamots:
lol right on . Thank you I will try this when I get home. my concern though is if i had to get rid of it for some reason it i reboot it, will itpop up again even if i delete the disable lag fix file? I may have mis understood.:D i think i am confused if i delete the disable lagfix folder on the sd card and re boot it re install the lagfix?
[Captivate Android Development] vinunleaded182:
I spoke too soon with v1.0

Sleeping death is still there when I woke up this morning. I cant turn it back on now. It look like they sold me a bad copy or the OC kernel made some permanent damage. Time to call Warranty
[Captivate Android Development] atinm:
Thanks. I'm sorry I was pissed in my early responses - I have slept less than 6 hours over the last three days working on this to try to incorporate the init.d changes and incorporating voodoo into the init script.
[Captivate Android Development] Kaik541:
well all I'm going to say is your work is fantastic and I look forward to much more of this. once you get init.d working cleanly, this will be the kernel to follow. Unhelpful has made some fantastic headway with customizing/optimizing our kernel, and seeing it combined with voodoo is like a dream come true
[Captivate Android Development] KaLiBLeeK:
This thread is making me feel awkward; haha. I love designgears' work. After using this Voodoo for a few minutes, I love atinm's work. It's like watching my parents fight or something...

*runs to a corner and sobs*

Anywho, Voodoo is running great. Did the 1-click JF6, then Odin'd JH7, then cleared both caches, installed SRE, then installed Voodoo. I was going to log into the IRC channel for voodoo and give some feedback...but the convo was all about hippos licking crocodiles and lolcats, so I left. Haha.
[Captivate Android Development] Phaze13:
Ditto, I'm getting mid 30fps in the 3D where I used to get in the mid 50fps.
[Captivate Android Development] Zilch25:
I FINISHED THE ORANGE JUICE, ITS ALL MY FAULT! *sobs, cuts self*
[Captivate Android Development] bsinc1962:
Selecting Captivate when loading ROM manger did not work, but by selecting i9000 I was able to get it to load into clockwork, then I was able to do a nandroid backup after loading this. I had to do it through the ROM manger app and not through a normal boot into recovery.
[Captivate Android Development] KaLiBLeeK:
"Mommy, why is Daddy sleeping on the couch again? And he smells funny."

I think this is bringing back bad memories. Time to change the topic.

So, ummm...yeah.
[Captivate Android Development] shep211:
Can we get a version that works with jm8?
[Captivate Android Development] Zilch25:
This one should... technically. Though the issues that persist using I9000 firmwares with Captivate kernels would be there.
[Captivate Android Development] kamots:
ok disregard my confusion i read and saw the answer im clear now. lol funny what u learn when u read and not skim. thi thread is movin! lol:D
[Captivate Android Development] atinm:
I haven't done anything to the video - like I said, this is as close to stock as I could get it using Samsung's source. Do you have the same issue with Unhelpful's kernel?
[Captivate Android Development] Zilch25:
Prior revisions (before he added the voltage control stuff) I never had any dips, though I can't say for certain if the newer kernel builds introduced a bug like that. Perhaps someone who's still running a non-voodoo handset could give this one a whirl.
[Captivate Android Development] shep211:
It fails when it looks for I897 and returns I9000.

getprop("ro.product.device") == SGH-I897
[Captivate Android Development] Zilch25:
Ohhh maybe because of the redbend package- might need to extract the zImage and repackage it, then flash through Odin.

There's also the option of using the I9000 version of the fix- though you'd lose external SD, you'd be able to gain HSUPA by flashing a JG8 or JH2 (the I9000 JH2) modem as a consolation prize!
[Captivate Android Development] atinm:
I barely know what JM8 is - I guess I could stop checking for what device this is running on and so let an I9000 through but I am not sure what that would do! And I am not going to try to support various different configurations because I'd rather work on incorporating the changes I need for myself and I haven't yet tried anything but stock firmware because I haven't felt the need yet. I've basically been breaking my phone daily while working on the kernel so flashing anything is just a pain as I'd be putting it back to stock in a few minutes anyway after I kill it! :D
[Captivate Android Development] warri:
Wireless Tether App is also not working, Thats about the only thing i have found...

Not sure if its the kernel or just the app...

Hopefully when you incorporate init.d we can get mobileap in and working !
[Captivate Android Development] warri:
Well im running on JH7 with no problems , except wireless tehter, so its not jus the Stock JF6 Frimware :)
[Captivate Android Development] atinm:
It won't until I have pulled in the init.d changes - I think it also uses the same init.d stuff though can't say for certain.
[Captivate Android Development] rajendra82:
Any details on voodoo leaving traces of ext4 behind? Is this because of upgrading between voodoo betas without doing disable-lagfix first, or is this happening despite doing disable-lagfix because of a voodoo bug?
[Captivate Android Development] Hellerox:
Is it normal that my Quadrant score (1600+) is lower than it is with other lag fix options?
[Captivate Android Development] Kaik541:
yes, this is a much more realistic result. the other lagfixes use an artificial buffer that "tricks" quadrant. this version also is a native filesystem as opposed to a loopback device and unmounts properly.
[Captivate Android Development] shep211:
That would be great if you could remove the checks for I897. You should not have to do anything else to support I9000 roms. What I am doing is loading I9000 rom then installing captivate kernel. I like the I9000 roms a lot better the the captivate ones.
[Captivate Android Development] rsx19:
do we need to reflash stock before* doing voodoo?
[Captivate Android Development] Kaik541:
a few people have said they've successfully flashed over SRE, but you'll lose the MobileAP ability because it doesn't support init.d and you'll also lose any overclock/undervolt
[Captivate Android Development] androidftwin:
has anyones phone randomly shut off after flashing this?

I flashed this last night and when i woke up the phone was off.. im starting to think all this flashing has messed up my phone
[Captivate Android Development] boomerod:
Keep it clean; Great work

I agree with yo, the kernel is nice... sent him a PM, SRE is there, he even notes it in his GIT

its not that kernel[/QUOTE]

I'm not using this guy's stuff yet cause I'm not sure it's worth the time. Having said that, it seems, from what I've read so far, he did put in some hard work and did give you (DG) credit. I'm not defending him cause I don't follow this stuff close enough to know all the details...but here is what I do know:

DG, you do awesome work and are clearly passionate about this stuff. I appreciate the hell out of your work and even donated $5 to you yesterday after I saw the SRE 1.3 re-posted and then working on my phone with JH7. You are clearly a bright person...stay above the fray/take the high road whenever you can cause I think I can speak for most when I say: We appreciate you a great deal.

Now, I'm so tired of waiting I can hardly stand it...I want to just drop Capitivate and AT&T and get me an EVO. Geez!! Come on Samsung and release the friggin Froyo so we can use are friggin bluetooth voice commands!!:p
[Captivate Android Development] vinunleaded182:
yep my phone wont turn on now. I just called Warranty and they are sending a replacement
[Captivate Android Development] atinm:
I'll do it tonight as part of the init.d changes once I get home from work.

-Atin
[Captivate Android Development] atinm:
Given that this really is as close to stock as I could make it, I can't figure why this would be. Did you try to reflash using the Odin one-click? That usually sets our phone back to stock at least.
[Captivate Android Development] vinunleaded182:
nope. Theres some posibilities

1. I couldve gotten a bad unit from AT&T

2. Previous SRE flash with OC made some permanent damage (that was when I started getting sleeping death and is why i switched to this one). Now it is permanent death

3. Bad quality control from Samsung?
[Captivate Android Development] -=HOLLYW00D=-:
Thank you atinm!
[Captivate Android Development] iamamp3pimp:
ouch.

damn
[Captivate Android Development] darkamikaze:
Glad to see things for cleared up looking forward to more updates on this

Xdapp @captivate
[Captivate Android Development] androidftwin:
did you call ATT warranty or samsung?
[EVO 4G General] Drewmungus:
Is there a way to lock the phone in landscape mode? I use fresh and am running launcher pro. I'd like a way to lock it in too only landscape mode.
[HD2 General] oshizzle1991:
I need to sell this asap
[HD2 General] Lizzo:
u wanna sell asap, and i wanna buy asap :D will u ship to trinidad?
[HD2 General] oshizzle1991:
unfortunatly, no =/ shipping will be a *****, i can ship to anywhere in america though... sorry man
[HD2 General] Lizzo:
nooooooooooooooooooooooooooooooooooooooooooooooo :(
[HD2 General] wacky.banana:
Closing this. If you want to sell this on XDA it must be posted in Marketplace and MUST comply with Marketplace rules which this thread does not.

WB
[Galaxy S I9000 General] markwil:
Hi,

the clock component has got a nasty bug:

1. Set alarm to now + a few minutes

2. Wait for screen to turn off

3. Press home button to look at the current time

4. Let screen go off again

5. THE ALARM DOES NOT SOUND!!

This could cause major chaos - luckily for me I just woke up half an hour later than was planned - I didn´t have to catch a plane or anything thankfully.

Phone is not rooted etc. original out of the box with a few extra apps and widgets installed.

Info. (from Android System Info. App):

1. Build: 2.1-update 1

2. Release codename: REL

3. Running Launcher Pro

Anybody else noticed this?

Cheers,

Mark