yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] IStern:
just flashed 1.4 over 1.3...now I get no sound at all 8)

Edit:

/system/etc/ does not contain an "asound.conf"
[Captivate Android Development] Purpleness:
Ditto. Were we supposed to uninstall first?
[Captivate Android Development] atinm:
Well, looks like 1.4 just deletes a good file too. I am removing that. Ideally you could just go to 1.3 from stock - it should work then. You would have to go from stock until I figure out how to fix this.
[Captivate Android Development] IStern:
can you post the good asound.conf? I assume I can just stick it in /system/etc and it'll be fine until I reboot right? I'll flash stock to 1.3 when I get home
[Captivate Android Development] mesasone:
I can't get on 3G or EDGE. I don't know exactly what is causing it as I flashed to JH7 and installed Voodoo at the same time - previously had been using JH2. Not using SRE though.

Also not getting audio through the headphones as others have mentioned which is a huge deal for me since I listen podcasts and music on my Captivate at work. I hope we can sort this out promptly.

EDIT: Sorry, just got home and work was still making my way through the new posts. I usually try to keep up with revelant threads on my phone through out the day, but of course my data isn't working ATM so... glad to see this is fixed now. Now just to figure out what borked my data.

SECOND EDIT: Alright, looks like I got my data working again as well. At some point my APN settings were wiped. Doubt it's related to Voodoo, if anybody else to doing a big upgrade (flashing to a newer build - JH7 f.ex) - check your APN settings if your data stops working.
[Captivate Android Development] Zilch25:
Okay, try this asound.conf file... Just ripped it out of JF6... I also leaned you can upload to multiupload through the stock browser lol

http://www.multiupload.com/TTZ7U03YMH
[Captivate Android Development] atinm:
Here is v1.5: captivate-voodoo-beta4-v1.5.zip. It is only meant for cleaning up the mess that v1.2 and v1.4 made. If you went straight to 1.3 from stock, then you do not need it. I will also put up 1.6 which for people who are installing voodoo for the first time or are coming from stock.
[Captivate Android Development] Purpleness:
Thanks! Sound restored with 1.5.
[Captivate Android Development] IStern:
All good, thanks atinm.

Should we go from 1.5 to 1.6 when you release it?
[Captivate Android Development] mesasone:
Atinm buddy, you might want to rethink your iteration scheme - at this rate you're going to hit 2.0 before the night is finished!
[Captivate Android Development] atinm:
Just hit 1.6! Hopefully I'm done!
[Captivate Android Development] Spleisher:
Can confirm sound is back for me too as of 1.5. Thanks!
[Captivate Android Development] atinm:
Ok, just posted captivate-voodoo-beta4-v1.6.zip. It is just a clean install if you have never installed v1.2 or below nor installed v1.4 or are coming to Voodoo fresh.

But if you have installed v1.2 or below, or v1.4 you need captivate-voodoo-beta4-v1.5.zip to clean up the mess I made. Sorry about that.

-Atin
[Captivate Android Development] rajendra82:
I think the asound.conf file packed with 1.5 still the buggy JH7 one. I did not actally install 1.5, but pulled out the file and put it in /system/etc/. On the next reboot the sound from the speakers was back, but headphones were mute. So I put in a known JF6 file from my archives, which I think would be the same as Zilch's upload. Now sound is back from both the speakers and the headphones. I guess we need a 1.5a. The buggy one is dated February 28, 2008, while the good one is dated June 19, 2010.
[Captivate Android Development] Divinedark:
My headphones that I ran my initial failed tests on work like a champ with the 1.5->1.6 update.
[Captivate Android Development] Pmac25:
ok just flashed 1.5 and sound is back. flashing 1.6 right now to get current. :D

Atinm,

Thanks for all the hard work and the late nights man this rocks.
[Captivate Android Development] IStern:
no problems going from 1.5 to 1.6.

appreciate your hard work atinm!
[Captivate Android Development] atinm:
Hmm, shoot. I pulled it off my phone, but it wasn't stock at the time . . . I guess there has to be a 1.5a!
[Captivate Android Development] kamots:
Damn. ! 0k i juststarted fresh with odin one click, re rooted, deleted voodoo update.zip from internal sd, downloaded rom manager nand back up of utb..... Fail. Restart phone, delete voodo folder with disable lagfix, nand restore utb through rom manager.... Success. Sign into xda and now see like 5 versions of voodo have. Ome out since i restored. Which version do i need. 1.5 or 1.6? As far as i can tell there ae no traces of voodoo on my phone, but i might not know. Where to look.
[Captivate Android Development] vinunleaded182:
Do I need to root before applying this or it already comes with Superuser?
[Captivate Android Development] Divinedark:
Shoot... Okay. Out of curiosity, what was buggy with the other file? My headphones seem to work just fine.

If I went from 1.2->1.5->1.6, please let me know how to go about installing this one.
[Captivate Android Development] atinm:
Can you check now captivate-voodoo-beta4-1.5a.zip - I pulled the asound.conf off stock phone (Odin OneClick).

Thanks,

-Atin
[Captivate Android Development] atinm:
If you are coming from stock, you just need the latest highest numbered version.
[Captivate Android Development] atinm:
It does not come with superuser but is an update.zip file, so you don't need root to install it. You will not have superuser after installing it either.
[Captivate Android Development] atinm:
I would say install 1.5a and then install 1.6 anyway . . . sorry. The asound.conf file that is used to configure how your mic, headphones etc work is not the stock one in v1.5 and v1.5a has the stock one from JF6.
[Captivate Android Development] IStern:
ls -l /system/etc/asound.conf on 1.5a shows aug 1 2008

is that the correct version?

i went from 1.5 to 1.6 and now 1.5a

Edit:

just ran a diff on the asound.conf from 1.5->1.6->1.5a->1.6 and the asound.conf posted by zilch, exactly the same
[Captivate Android Development] contentryder:
i'm having a battery drain issue like the rest of the people with beta4 lagfix... =\ before i wake up at 6am for work til 7pm and still have about 70% with little use. now i'm getting 30% with little use! but overall phone is zippy!
[Captivate Android Development] Divinedark:
You might check your battery meter to see what's eating up your battery. For them it was the Android OS. It also made the handset hot.

I've been watching mine and with 1.2 I was off charger at 9:00pm. It's now 7:00pm the following day and I'm sitting at 62% with moderate use. Pretty much what I was getting previously, if not a bit above average. I dropped 9% from 1:00pm to 7:00pm with phone calls, flashing and rebooting 4 times, running two full quadrant benchmarks, and texting. Just trying to keep a log. My battery meter shows the screen(by a large margin), then phone calls, then quadrant being my primary battery eaters.
[Captivate Android Development] g0dzilla32:
sound works for me after this... for future info can I just flash on top??? I disabled lagfix.. then run update.zip... then delete disable lagfix folder.. then reboot...

EDIT: Headphones that is.. sound always worked :-)
[Captivate Android Development] LuckyX2:
So can anyone else not make phone calls with this?

I flashed to stock then sre v1.3.1c then voodoo kernel v1.2 on top of that and when I make phone calls, the other person can't hear anything except some garbled static...

I updated to v1.5a and then v1.6 and still having the same problem.

Thanks
[Captivate Android Development] Zilch25:
Are you running the stock modem files? This phenomena only occurs (normally) when using a non-AT&T modem on a stock kernel.
[Captivate Android Development] LuckyX2:
When you say modem files, is that the same thing as baseband? If so, yeah, I'm on JF6.

I flashed to stock with odin, then sre 1.3.1 and then voodoo 1.2. Nothing else was done modification wise after that. I never (knowingly) modified any modem files.
[Captivate Android Development] kamots:
Ok im screwed i think. . And confused. I used odin to flash to stock with odin, re rooted, did nand restore of unleash the beast intalled voodoo 1.6 via. Comp to internal sd card.( could download directly using eugenes hybrid rom) . Anyway utb with voodoo 1.6 is unbearably laggy. Reboited, did nit fix. Attempted to do disabke lag fix in voodoo folder and it wont let me. Usind explorer from market ( free on not root explorer ( cant buy apps)anyway says read only. What file manager should i use. I cant use odin again cause i didnt disable the lagfix. I think i messed up when i deleted the voodoo update zip of internal sd card, and replacednit with clockwork zip. Can i recover from this? Can i reflash 1.6 voodoo to get the zip on internal sd card after i remove clockwork zip. Soooo mad.
[Captivate Android Development] Zilch25:
Yup, that's what I'm talking about... very strange. If your baseband still reads JF6 then you're still at stock, which should work just fine. There might be something else amiss on your device- not saying it isnt somehow voodoo related, but it's more than likely a voodoo fluke if anything.

Is this a really fresh install or have you been piling things on over time? (As in you started at like SRE version 1.0 and upgraded gradually over time to 1.3.1) If you aren't terribly averted to it, for testing purposes, could you maybe revert the lagfix, then reflash a stock kernel and see if your normal phone functions return?
[Captivate Android Development] Zilch25:
Sure you can recover from this, as long as your phone can still mount the SD cards to your computer (You know, how you drag and drop the zip files into your /sdcard). Just mount the drives, open up the one for the internal SD, go to the voodoo folder, create a text file called "disable-lagfix.txt", then just use the built file explorer on your phone to remove the file extension (or do it through windows if you have file extensions turned on).

Reboot, it'll remove the fix

Though I'm not entirely sure what went wrong... removing the voodoo zip file shouldn't do a thing since it already unloaded everything it needed, and never really references the file again

Edit: You might also try using the free version of Astro File manager if the freebie Root Explorer is being *****y
[Captivate Android Development] IStern:
You're the one, or should be the one anyway, that created the voodoo update.zip file on /sdcard. If you can adb in to create the update.zip file, then you should be able to create the disable-lagfix file to get rid of voodoo, or copy over 1.6 and adb reboot recovery.
[Captivate Android Development] K-mart Shopper:
Voodoo 1.6 works great, thanks for the quick headphone fix.

I can report my phone works exactly as it should, only faster and with more features now. At the rate my phone was draining the first half of today, I would've had ~50 hours with light usage - that's great. I'm running JH7 with MobileAP, for those interested.
[Captivate Android Development] LuckyX2:
Yep, fresh install right to sre 1.3.1 and then voodoo 1.2 all in a row within a time-span of 15 minutes or so.

I'll try a stock kernel and report back.

Also, I now know it's definitely not the modem because voice recorder doesn't work either. It's something wrong with the mic.
[Captivate Android Development] alphadog00:
you can also create a floder called disable-lagfix in the voodoo folder - it is a bit easier then removing extensions, but if you are doing it from the pc - it is just a drive letter and windows exporer will let you create a new txt file, then rename without the extension or, as i said, just create a folder.

from the voodoo project:

* Create a file or folder named “disable lagfix” in a a directory named “Voodoo” in your internal SD card.

* Reboot
[Captivate Android Development] jslee1020:
just wanted to comment OP... I like how you keep the download links for previous versions. Never know what people want, you know?

Anyway.. I fresh installed through odin 1click, rooted, tibu to erase all AT&T bloatware and then applied voodoo 1.6

Great work!

BTW... I'm not experiencing any of the above problems (headphone problems... call problems.. etc...) I guess just make sure that you don't overlap too many mods
[Captivate Android Development] ranova:
because it was fixed way back in voodoo 1.3
[Captivate Android Development] kamots:
Again you rock zilch! i am learning alot from you and i appreciate it. I have already installed astro and was able to do the disable lag fix folder in the voodoo file. I have not restarted to rsf because after 3 reboots, it seems to be getting faster. Maybe its just me. I will give it until tomorrow, and if if doesnt seem to be as good as The hybrid rom then i will do this process again. The only. Thing concerning me is my internal storage has gone from 12.34 to 12.00 for no reason. I f i do the master clear with odin one click, will that give me my 13 gb back?or will it bork the phone?
[Captivate Android Development] Zilch25:
The internal storage shouldn't have changed O_o but keep in mind that the Voodoo fix will *stay* uninstalled until you remove the disable-lagfix file :) I'm glad to help, feel free to hit me up whenever you have questions, PM if it's something offtopic since I don't like derailing threads!
[Captivate Android Development] Circazero:
I have JH7 with voodoo 1.0.

Would you guys say it's better to run 1.5a voodoo and then 1.6.

Or

Just disable voodoo > flash to stock JF6 > then voodoo 1.6?
[Captivate Android Development] Zilch25:
I'm always an advocate of a clean flash. And right now I'm a little too inebriated to follow the upgrade path :) So yeah I'd say, disable, flash, install whatever ROMs you want and then apply the new voodoo.
[Captivate Android Development] nathon.fuller:
And this is what i would expect from this phone! well done guys!
[Captivate Android Development] Circazero:
Thanks! That's what I was thinking of doing. If I disable voodoo. Then use the Odin 1click to stock JF6 will that give me a complete, like "out of the box" captivate system? Last time I tried Odin master clear it just hanged.
[Captivate Android Development] Zilch25:
Yup, that it will.

The only benefit of a master clear is that it will wipe your /sdcard area too, and you probably dont want to do that... but if you do- go ahead and enable USB debugging and try master clear while the phone is booted ;) that'll do it.

Just remove the fix, use the one click to reflash, dont bother with master clear, then remove the disable-lagfix file, reflash the voodoo kernel and reboot and you'll be back to snappy voodoo speeds
[Captivate Android Development] Circazero:
Since SRE Removes all the crapware and enables sideloading and stuff (I don't care about OC/UV) would it be safe to flash SRE to do it's thing then run voodoo on top?

Thanks for all your answers :)
[Captivate Android Development] Zilch25:
Yup, if you flash one of the 1.X releases of SRE you should be completely fine flashing the Voodoo kernel afterwards :D By doing so you should be able to keep MobileAP and all that fun stuff... only thing you'll lose is OC (Since this kernel doesn't support the extra step)
[Captivate Android Development] smokestack76:
How long have you ran this zilch? I got it when it first came out. Then your. Update flash. First one for odin u posted. since then i see my space shrinking and shrinking? Kinda strange. May just be me. And like i said no reflashez since then...
[Captivate Android Development] smokestack76:
Oh and since then a few reboots throw me into safemode. I gotta catch back up on here. Just too tired tonight :-P
[Captivate Android Development] Zilch25:
TBH right now I'm not running it because I'm testing some other stuff... I ran it back when it was for I9000, I ran the 1.1 version for a day though without any issues. This isnt just typical app install stuff is it? Also you haven't thrown in any ROMs or anything have you? Your space shouldn't be gradually shrinking O_o

You might want to just clean house and load up the new versions of the fix... theres no reason why the little Odin package should have caused any issue, but just to confirm I didn't have a hand in it... lol
[Captivate Android Development] smokestack76:
No im off fresh jh3 flash. I have system monitor going now. Could be cache catching up with me. Not a big factor space wise. Just more than normal. And the reboots never happend before. Im kinda thinkin it may be a app since i have no lag fix either.
[Captivate Android Development] smokestack76:
Ahh no problem. Like i said may just be me. I didnt do master clear im sure. Still have junk on sd. No biggie. Im going to sleep on it lol. Just thought maybe you still had it going.
[Captivate Android Development] Zilch25:
Yeah that's definitely a little bit on the odd side.

This may be a stupid question... but did you disable GPS logging? It has a tendency to fill up the NAND within a number of days...
[Captivate Android Development] smokestack76:
Im sure it is just me. My cpu is going non stop lol. Something i did didnt play well. Time to stat fresh in the am.
[Captivate Android Development] Zilch25:
Check your jupiter.xml file... if gps logging is on that would 100% explain why your storage is filling...
[Captivate Android Development] smokestack76:
And noooo i sure didnt lmao. One time i dont use sre lmao
[Captivate Android Development] Zilch25:
DAMN I'm good :D
[Captivate Android Development] smokestack76:
Yeah thanks fer the reminder lol. Killed cpu usage alot too even with gps shut off. Nice n00b moment. Thanks man lol? Guess i better get to bed.
[Captivate Android Development] Zilch25:
Hahaha it happens to us all, I wouldn't of thought of it if you hadnt mentioned "fresh JH3". Make sure you clean out that log folder to reclaim your lost space after you kill that logging entry :D
[Captivate Android Development] LuckyX2:
Well never mind my posts I guess. My phone's mic must be broken. I flashed back to stock and still having the same problems...
[Captivate Android Development] Zilch25:
That's really bizarre... completely blank 1 click restore with master clear type restore? Are you hearing other sounds on your phone or is it just people on the other end that cant hear you?
[Captivate Android Development] thedon809:
I did this and I get a slight lag when dragging and dropping apps or when putting an app on the home screen from the app drawer. It didn't do this when I had the original ext2 fix.
[Captivate Android Development] LuckyX2:
Didn't master clear, I'll do that now before I tear down the phone and/or return it.

I can hear everything fine on the phone, it's just that the mic isn't picking up sound. Voice recorder only records static and people calling me/people I call can only hear static.
[Captivate Android Development] Zilch25:
Hmmm... well that rules out asound.conf issues. That's what normally happens with incompatible basebands (like I said before). But you've done a complete reflash which should have reverted absolutely everything... lagfix included. That really only leaves a defective mic as far as I can tell. I guess I should be relieved it's not an issue with the kernel =P

I hope your replacement has button combos!
[Captivate Android Development] The Bishop:
here's an odd one. went back to stock (JF6) went up to JH7 then applied SRE but no lagfix and then this one. Wouldn't come up, so I decided to go back to stock again ... load into download mode and Odin sees the phone and says firmware start but doesn't actually do anything that I can see ... ?
[Captivate Android Development] Zilch25:
How did you go about trying to install the kernel? Using the update package through regular recovery menu? Where-about did it fail?

If it *did* apply you should be sure to remove it... however if you never heard the robot lady talk it probably didn't install.

If Odin is hung up it either indicates the phone was plugged in before Odin started, the USB port isn't talking right, Drivers need to be reinstalled, Kies is running, or Satan himself hates your phone
[Captivate Android Development] vinunleaded182:
One request: can u make note of the forum page everytime you release a new version
[Captivate Android Development] The Bishop:
Well, everything ran fine, except for the SRE thing, and the instructions there said to rerun if it didn't do everything, which I did, and it did come up with that 2nd screen for install that I had not seen before. Rebooted, the AT&T logo and then the Samsung logo came up and then ... nada. The 4 buttons on bottom light up and that's all.

So I just rebooted my computer, the phone has the evil pc -/- phone thing when I turn it on so I just go directly to the downloading. I do that by holding the vol+/vol- and then plugging in the USB cable. I then fire up odin, unplug the usb and replug it in, and odin sees it on com6 like normal. I've tried just about every combo that I can think of from there:

with and without repartition

with and without pit file

with JF6 and tried JH7 just for grins

odin gets to the point where it says "DO NOT TURN OFF TARGET" but I don't see it doing anything, nor do I see the blue status line on the phone either.

That's where i'm at. I also tried the one-click odin and it did the same (unless it doesn't do the blue status line, I can't remember).

SRE was the point that killed it, but I'm wondering if it was this lagfix + SRE failing and then me re-running it that hosed it up. Is there a way that I can wipe the internal sd in case there's something there that's hosing it?
[Captivate Android Development] vinunleaded182:
Have you tried this on a different computer?
[Captivate Android Development] The Bishop:
I have not, but my wife's captivate just let me flash to JF6 so I'm pretty sure it's the phone :/
[Captivate Android Development] The Bishop:
and just like that after trying the same thing 6 times in a row, the 7th worked. literally just did the same pit file, repartition and stock JF6 and there it goes.

maybe reflashing my wifes got odin to 'like' me again? that's all that I did differently.

That's the last time that I'll be using SRE.
[Captivate Android Development] Zilch25:
The problem is that when you use the two volume buttons + USB trick Odin has to be open first, otherwise it'll hang shortly after the point where it bricks your phone =P

Try it that way

Close Odin

Unplug Phone

Yank battery

Open Odin

Insert battery

Hold buttons

Plug in USB

Flash

Profit

Edit: Glad you got it working, but I still maintain it was probably because you did it out of order! Odin is *****y!
[Captivate Android Development] vinunleaded182:
Try swapping batteries and flash your phone again
[Captivate Android Development] The Bishop:
Thanks guys -- I knew that I had not gotten it to a 'doom' point, just had to figure out the right combo. Will remember the odin thingy too (battery swap was what I was about to do based on the post above me :) )
[Captivate Android Development] Zilch25:
Always remember:

If manually getting download mode (without USB), open Odin before you plug the phone in

If using the twin vol button method open Odin FIRST before attaching the phone to USB

And may all your flashes be fruitful!
[Captivate Android Development] madjsp:
Where is that file you were talking about? I've gone through half this thread.
[Captivate Android Development] Zilch25:
Check the other thread... I reuploaded it =P
[Captivate Android Development] domin8:
sorry this may have been answered in this thread (ive skipped around) but what is the benefit of this over the tayutama lagfix? Thats what i'm running now with quadrant scores of 2219.

whats the appeal of this one? thanks
[Captivate Android Development] Zilch25:
The Tayutama lagfix is running in a gigantic EXT2 bubble living on top of the stock RFS file system... this situation is rather precarious and potentially volatile. The Voodoo lagfix completely takes the RFS file system out of the equation and replaces the stock file system with EXT4, which while not scoring as high in Quadrant SHOULD yield even better real world performance than the EXT2 lagfixes
[Captivate Android Development] domin8:
oh ok i like the sound of this then :) now to figure out how to remove my lagfix :/