yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] [DT]:
Oh holy ****...

[edit]

OK, do I get a pass since we were up all night drinking tequila and I'm _supposed_ to be on vacation? :D

It's always the simplest things. Amazing, thanks so much. I guess I was thinking I "uninstalled" but I really just converted the FS and swapped back the other kernel (and the directory was just sitting there).

This did seem to have an extra step, when it rebooted the first time, it came back to Recovery, showed 'Installing Multi-CSC', I let it sit, and just chose the reboot option from the Rec Menu, got a regular start (media scanning was extremely fast), everything seems _super_quick_ again.

DT owes jhernand1102 a [good] beer. :)
[Captivate Android Development] a.n:
Before I flash Beta 4, I want to make sure I'm good-to-go.

1. The only lag fix I've ever used is from the OCLF app in the Market.

2. When I open the app there is no available option to undo any lag fix listed, as if I'm not using one.

3. If I choose "Remove EXT2 Tools" a message pops up letting me know "You appear to have a lag fix installed!.../system/bin/playlogos1"

So, I'm just a little unsure if flashing the Beta 4 update.zip will cause me any issue at this point. A little insight, please?

*I fixed this by using "Restore Boot Animation." Beta 4 installed successfully if anyone was where I was at.
[Captivate Android Development] cfili:
Anyone with the voodoo kernel installed able to successfully install the OTA update? I've tried twice and it failed both times for me.
[Captivate Android Development] [DT]:
I would definitely clear out any existing lagfix (that changes the f/s and/or modifies startup files and/or the kernel). I thought there was a PC app you could run that would do all of the uninstall semi-automated[?]

I don't know if you read my post(s) above, but I tried with the filesystem converted back to EFS and with the original kernel put back, both cases (and a couple of tries each time) I got to the 50% mark and the 'update failed' message. Nothing appears to be done, no issues, etc.

At this point I'd rather have the infinitely better performance vs. a questionable GPS fix. I'm confident, if the GPS is actually tweaked, that one of the smart folks on this forum will provide it as a update that can be flashed via recover or ROM Manager.
[Captivate Android Development] jslee1020:
so what would v1.9 improve over v1.8??

Would it result in better performance??
[Captivate Android Development] atinm:
It doesn't work - for anyone who has basically even touched their phone . . . anything but straight stock from the store seems to fail. Wait for others to build ROMs from this - designgears' Cogition is already building on top of the OTA update with captivate voodoo lagfix 3.0 v1.9 that I released at the top of this thread.
[Captivate Android Development] atinm:
No, I put in the changelog that it is really only an internal change in how I process init.d scripts. More applicable to ppl who build ROMs that use init.d scripts than users. It is essentially v1.8 other than that but I would prefer if ppl used v1.9 if they're coming new or coming from stock.
[Captivate Android Development] DJNgoma:
How long does it take to uninstall Voodoo? I've staring at my phone screen for the last 10 mins with the AT&T after it said Converting ext4 to RFS...

EDIT: Nevermind, it seems like it has finished. Never knew it would take this long haha.
[Captivate Android Development] lexudv:
I flashed my phone to the newest JH7 with OTA update ROM (http://xdaforums.com/showthread.php?t=790080) and everything is working! I want to apply a lagfix and this one looks good.

Can I apply this Voodoo lagfix or is it not compatible with the updated ROM?
[Captivate Android Development] rajendra82:
Running voodoo on the OTA JH7 ROM it right now. No issues. Quadrant 1730.
[Captivate Android Development] lexudv:
That's weird, after I applied the Voodoo lagfix, my GPS no longer works. GPS Status shows 0/5 fixed satellites. I've been restarting the phone with no luck! Has anyone had the same issue?

Note: I had applied the new JH7 with OTA update ROM (http://xdaforums.com/showthread.php?t=790080) before doing this.
[Captivate Android Development] xtremekilla09:
That is awesome. I can hardly wait.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] graveheart_82:
so finally did the 1.9 update and it worked beautifully, got the confirmation "conversion successful". Phone rebooted and the Quad score was 1799. Phone was snappy as expected.

Once done, I saw the thread about JH7 and being impatient I am, I run to get the OTA Update w/o unrooting, removing the lag fix or flashing back to JF6 stock. As noticed by others it failed at 50% but after that, when I logged back in the phone, Rom Manager (RM) FC'ed on me. I tried the update again and RM FC'ed on me again. Giving up on it for time being, I for some reason I ran the Fix Permission in RM and I saw the lag come back and now my Quad Score is 1618. Can someone explained why this is the case? I understand that Quad test is not simulating real world experience but I did notice the lag before I re-ran Quad score so its not just numbers in my head.

To get the speed back up again, would it be better to disable lag-fix and reinstall 1.9?

Thanks!
[Captivate Android Development] atinm:
I actually don't know what state your phone was left in - if the update installed a new kernel, and/or you had disable-lagfix, you would see lag.
[Captivate Android Development] graveheart_82:
I did not disable lag-fix while updating to OTA JH7. The phone still says its at JF6 with Voodoo 1.9 kernel so I was curious why the diff in Quad score num's. I dont know if it started converting partially and messed w/ the lag fix during that?

I guess I will just flash back to JF6 stock w/ ODIN, run the JH7 update thru RM and run 1.9. I'll see if my brother gets any luck w/ GPS once he updates to see if its worth jumping to OTA JH7.

Can I disable lag-fix and run 1.9 again on JF6 just to get a clean install again? Will it cause any issues since I'm not reverting back to the stock Kernel completely or will I have to ODIN back to stock then run 1.9?

Thanks again!
[Captivate Android Development] ghost77:
Hi i flashed latest VooDoo 1.9 , had no lagfixes prior to this , all works great speed . Except one thing.

Once i connect USB cable to PC and select Mass Storage , i get Red Triangle on my phone , and windows throw up scandisk warning. Disk "I" is my Internal phone SD.

Think it was unrelated , i let windows fix it ,it didn't find any problems , i then rebooted phone, and no more red triangle.
[Captivate Android Development] jwood55812:
Sweeeet! Can't wait!
[Captivate Android Development] provoked:
Correct me if I am wrong but the red triangle looks exactly like debug mode and the.kernel might have it on.by default.
[Captivate Android Development] :
Red triangle that was epic xD, thats just the default notification icon,in this case it means usb debugging is turned on, and the device is telling you wether to mount or not the sd card.

rafyvitto
[Captivate Android Development] ghost77:
I am guessing it somehow turned on by itself i keep it off :p
[Captivate Android Development] shadow65781:
mine did this 3 0r 4 times then I lost all usb connectivity and the red triangle is debug
[Captivate Android Development] alphadog00:
Is Voodoo going to get re-written for JH7 kernel?

EDIT - looks like the kernel is the same - so no worries.
[Captivate Android Development] ragpaoa:
Actually, I believe the JF6 and the JH7 kernels may be a bit different. I'm no expert, but I'm basing it on the audio quality from the Phone, audio jack, and bluetooth.

I was able to flash JH7 successfully using the OTA. This was because I have a stock, unmodified JF6 that I have been using for over a month. I noticed that the audio quality of the bluetooth (I have a good bluetooth stereo headset) had better bass response and was clearer overall with the new JH7. Also, the audio jack quality has improved a bit in terms of background noise. I also have a pair of hi-end Sennheisers that I use to test. Lastly, the phone audio no longer crackles at higher volumes.

However, after I flashed the Voodoo lagfix 3.0 after the JH7 updated, I got back the same audio 'problems' I had with the stock JF6.

I flashed again back the to JH7 (via a backup I made), the audio was all good again. Most people won't notice the difference, but since I am an audiophile, I can distinguish with a good set of headphones.

Please, for my own edification, can you make kernel based on the JH7 kernel? Unless someone out there can prove there is no differences between the 2 kernels.

I do want to say, thank you antinm for all your hard work!

Thanks
[Captivate Android Development] rajendra82:
When Samsung releases the source code for the JH7 kernel, I am sure that the voodoo lagfix can be ported to it in almost no time.
[Captivate Android Development] Pmac25:
What is this I hear about a Beta 5 of Voodoo with Clockwork support? Oh please do tell I am sure we all would love to have details. :D
[Captivate Android Development] atinm:
Samsung hasn't released the source code for the latest kernel that they shipped with the JH7 modem and so we can't do it, yet. Hopefully they're release it and then it'll be easy enough to add Voodoo to it. Though with Froyo supposedly coming soon too, maybe they'll just release the kernel source that they ship with Froyo and it'll contain these audio fixes as well. Once they do, adding Voodoo is no biggie.
[Captivate Android Development] TheTodFather:
+1 for voodoo COLOR fix, it has come a long way and has been ironed out.
[Captivate Android Development] Delwyn:
Everytime I flash this update.zip, it somehow disables my MobileAP? Any thoughts?
[Captivate Android Development] atinm:
MobileAP doesn't come with my kernel - it is installed by something else, and I think it requires an init.d script. Maybe the init.d script it comes with wasn't using the latest init.d method but now every voodoo version for Captivate supports the same (mine, Unhelpful's and even the reorient) so hopefully you will not be seeing this again.

-Atin
[Captivate Android Development] atinm:
Just posted a new version of my kernel that also supports backlight notification. Also, added an optional kernel that can go on top that enables HSUPA using the I9000 modem but bluetooth mic does not work with that.
[Captivate Android Development] InsaneJester17:
Woa, looks very cool! Is there a way to flash just the backlight part onto captivate?
[Captivate Android Development] atinm:
If you are already running my previous Captivate kernels with Voodoo, this is a minimal change and you can just flash over it. But it is a new kernel plus a different file in /system/lib/hw so you do need to run the update.zip to have everything work. Backlight is not a separate thing.
[Captivate Android Development] InsaneJester17:
Ah IC, will it hurt anything if I'm using Cognition 2.1.5 with optional HUSPA kernel?
[Captivate Android Development] ranova:
What does backlight notification mean? similar to noLED or does it light up the bottom buttons?
[Captivate Android Development] atinm:
Bottom buttons. http://xdaforums.com/showthread.php?t=772672
[Captivate Android Development] atinm:
I *think* those are my kernels so it should just work. You will first have to use the update.zip I linked to update the kernel to the voodoo+bln, and then flash the Voodoo+BLN+HSUPA kernel linked above via ROM Manager to get your HSUPA back.
[Captivate Android Development] sstrawsb:
..in a robot voice... "this may take a few minutes.. Step One"

Thats awesome! This is my first kernel flash so I was pretty intrigued by the talking robot women. Everything seems to be going good so far! Thanks for the very basic instructions, made it easy for a noob like me to figure out.. "Step Two!" Go Robot go!

Thanks again
[Captivate Android Development] mindfrost82:
Since you seem to be one of the few Captivate kernel gurus we have here, I was wondering if its possible to do an audio tweak like they have on the Nexus One.

I know it was at the kernel level and it basically tweaked the audio level so the earpiece was a little louder than stock. If I'm in a noisy place, the stock audio level on the Captivate is too low for me.
[Captivate Android Development] sstrawsb:
I agree. I do find the ear speaker volume a tad low. Especially with my body glove case, I tend to find my ear mashed to the screen in a death grip.
[Captivate Android Development] Mattwp103:
I see you've figured out how to manipulate the lights. Would it be possible to have them stay lit while the screen is on?
[Captivate Android Development] daraj:
+1 on the audio level tweak. Its too low
[Captivate Android Development] IStern:
awesome, thanks atinm!

upgrade to jh7 through kies mini, applied 1.10 and hsupa, and now my phone is super fast and has a working gps!!

Now how do I get rid of this stupid device management reminder to apply the OTA update...
[Captivate Android Development] kamots:
Man I think I pulled a noob. I installed the new voodoo kernel with m lagfx file still in the voodoo folder. Dumb huh? Phone seems to be a bit "off" now. Still works and got n the 1700 with quadrant, but have a hard time keeping 3g. Mostly edge. Don't know if its related. I deleted the disable lagfix folder and reflashed voodoo.thinking I'm gonna Odin back to stock and wait for the next version of cog. Phone just doesn't seem as fast as it was with 1.9 voodoo kernel. Am digging the new xda app though!
[Captivate Android Development] atinm:
It shouldn't matter if you leave the lagfix file in there if you're just upgrading to v1.10 kernel from my previous kernel via the update.zip file attached. v1.9 and v1.10 are basically the same, with just the backlights added. Cognition is just going to go to v1.10 next too - but if you go back to stock via Odin and then install the v1.9 kernel via Cognition, then update.zip to v1.10 from here - you should be fine.
[Captivate Android Development] atinm:
Since I am in the audio world right now due to bluetooth issues with HSUPA, I'll take a look to see if I can do this. No promises.
[Captivate Android Development] TMC_Sherpa:
I'm working on it as fast as I can :) unfortunately things are pretty messy in there, lots of wm8994_write(codec, BLAH, YUCK) commands. And by Yuck I mean binary or.

val = wm8994_read(codec, WM8994_POWER_MANAGEMENT_2);

val &= ~(WM8994_TSHUT_ENA_MASK | WM8994_TSHUT_OPDIS_MASK | WM8994_OPCLK_ENA_MASK | WM8994_MIXINL_ENA_MASK | WM8994_MIXINR_ENA_MASK | WM8994_IN2L_ENA_MASK | WM8994_IN2R_ENA_MASK);

wm8994_write(codec, WM8994_POWER_MANAGEMENT_2, val);

for example.

A1026 should be in bypass mode

void wm8994_set_voicecall_bluetooth(struct snd_soc_codec *codec)

{

if(a1026_mode_status != BYPASSMODE)

{

A1026SetFeature(BYPASSMODE); // set the configure for A1026 to bypass //hdlnc_ldj_0416_A1026

a1026_mode_status = BYPASSMODE;

}

for bluetooth so I'm guessing its one of the codec commands that's screwing things up like an audio route is not getting set up correctly or something. The stock wm8994_aries.c file only changes WM8994_POWER_MANAGEMENT_1, 4 and 6 while wm8994_kepler.c changes 1-6 when it enters that code block. The headers contain all the constants but that doesn't help much because I don't know what any of them do :P Without any documentation for the chip it's all a shot in the dark at the moment.

Interestingly most if not all of the not "dealing with phone calls" code is the same between the files.

wm8994_record_bluetooth() and wm8994_set_playback_bluetooth() for instance are identical.

Sherpa
[Captivate Android Development] thumper_1151:
Thanks for all the hard work guys! We should send a petition to Samsung to pay all of you that are working hard to fix the problems on this amazing piece of hardware since they obviously aren't working to hard on it!!
[Captivate Android Development] Krynn!:
Thanks for the update!

Just one little detail... Is there anything we have to do to enable the backlight notification? In reading neldar's Q&A post, it says that SMS should be on by default, and calls can be enabled with one of two apps. I'm not seeing any notifications for SMS, nor for calls (tested with both recommended apps, rebooting after configuring each just to be sure).

Just for reference, I'm running JH7 OTA + Voodoo Lagfix 3.0 v1.10 + MobileAP + Circle Battery %.
[Captivate Android Development] atinm:
I think it "just works". Make sure you phone is actually in sleep mode (display off) - that's when you'll see the backlight come on on email and sms at least. Haven't tried calls yet.
[Captivate Android Development] atinm:
BYPASSMODE is a pain in the ass and nothing works if we set that. I've given up on that and just compile without A1026 enabled for HSUPA mode with I9000 modem since that modem won't work with the chip enabled anyway. I also modified the sound/soc/codecs/Makefile and wm8994_aries.c to pull in what I need from wm8994_kepler.c for bluetooth and other power management stuff. Bluetooth mic is still not working and can't figure out why and I've been playing with POWER_MANAGEMENT_6 as that seems the most likely culprit. But no luck yet. Take a look at my git repo for linux-captivate and you'll see the config for i897_hsupa_defconfig and how I build that.
[Captivate Android Development] Krynn!:
Yeah, that's kind of what I thought too... Unfortunately, it doesn't seem to be working. Phone is sleeping, SMS comes in and wakes it up, I don't touch it at all, and when it goes back to sleep, everything's off. Just to be sure, I let it sit for 5 minutes and nothing came on.

I'm more than willing to experiment if there's anything you'd like me to try...
[Captivate Android Development] killer_siller:
Installed over the top of a fresh Cognition install. No backlight notification.

For what it's worth I'd run an i9000 kernel prior to this, and had backlight notification working. Unfortunately that kernel seemed to suck a lot of battery :(
[Captivate Android Development] jhernand1102:
How do I enable Mobile AP on this...
[Captivate Android Development] DOAlaboratories:
Yeah, none for me either...

Sent from my Cappy using mental telepathy powers.
[Captivate Android Development] Krynn!:
First, be somewhat comfortable working as root in adb shell....

Second, backup!!!! You probably won't need it, but it can't hurt!

Third, follow these steps:

1) install atinm's voodoo kernel

2) create a file called S99_mobile_ap_service containing the following:

#!/system/bin/sh

/system/bin/wlp2pservice </dev/null 1>/dev/null 2>&1 &​

3) create a directory (if you don't already have it) called /system/etc/init.d/

4) copy S99_mobile_ap_service to /system/etc/init.d/

5) run the following from a root prompt:

chmod 755 /system/etc/init.d/S99_mobile_ap_service​

6) download signed-mobileap.captivate-I897UCJF6.zip

7) install signed-mobileap.captivate-I897UCJF6.zip using clockwork
[Captivate Android Development] Krad:
The new kernel with notification lights is killing my battery!
[Captivate Android Development] Krynn!:
Are you seeing any notification lights?

I'm not, but my battery seems to be holding up as good as ever...
[Captivate Android Development] atinm:
Don't know what to tell you guys - the change is minimal, only affect backlights and is enabled for email and sms by default. How did you install? Did you use my update.zip?

-Atin
[Captivate Android Development] posthold:
My lights are working...
[Captivate Android Development] Krad:
Yes lights were working and never shutting off
[Captivate Android Development] Krynn!:
Yup. Installed using clockwork.

Now... before testing SMS or e-mail, I tried installing both of the call notification apps ("Missed Call for Android 2.x" and "Easy reminder", and yes, only one of them at a time). I don't know if they may have left something in the system that might hose SMS notifications or not, but I guess anything's possible?
[Captivate Android Development] techmik67:
Noticed a small thing.... when using stock earphones,, for any purpose, the button on them only works 1 time..... then it is disabled til you unplug and replug it.
[Captivate Android Development] atinm:
Installing via clockwork will not work for backlights. You have to use the update.zip method because it needs to install an updated lights.default.so file also.
[Captivate Android Development] atinm:
With or without HSUPA? HSUPA is still somewhat flaky - consider it in testing and thanks for the bug report. I'll try to see what I can do about it.
[Captivate Android Development] atinm:
They should shut off after you actually handle the notification by turning the phone on, going into whatever is alerting you. That's how it is supposed to work - it doesn't come on and go off.
[Captivate Android Development] techmik67:
Sorry, should've specified..... with HSUPA.
[Captivate Android Development] pricej636:
Works awesome here, did the update.zip method on top of cognition. Thanks!
[Captivate Android Development] jhernand1102:
Thanks..Just one more question...should I use notepad to create the file and save it as a .txt file?
[Captivate Android Development] Krynn!:
No, that'll end up saving the file in MSDOS format, with both a carriage return and a line feed at the end of each line. Better to use something like Notepad++ and save the file in UNIX mode.
[Captivate Android Development] Krynn!:
Just out of curiosity...

Does anyone who installed either of the call notification apps have the backlight notification working?
[Captivate Android Development] jhernand1102:
Ok thanks..
[Captivate Android Development] atinm:
What is the exact sequence of things you tried - my stock phones just do mute when I hold it, and unmute when I let go, is that all they're supposed to do? :)
[Captivate Android Development] atinm:
Would like you to try installing i897_hsupa_v1.10.zip using Rom Manager - just on top of what you have and see if your stock headphone button works now. Mine seems to mute/unmute fine now, hopefully I fixed yours too.
[Captivate Android Development] techmik67:
That is the one I installed, following your instructions right after you uploaded. That is the only thing I noticed..... if you want, I can try tomorrow to install over the top and test. Can't test audio tonight in case something goes wrong. Roommate sleeping =)

edit: 1st install was stock, wasn't it. Will flash rom manager in am.
[Captivate Android Development] WickedStyx:
Thanks! This is working great so far.
[Captivate Android Development] alphadog00:
If I am already rooted and have the SuperCircle battery do I have to flash back to stock first? Has anyone installed with this existing combo?

Thanks for any advice.
[Captivate Android Development] harshkey:
I just installed this on my captivate and its constantly showing force close pop-ups while booting. It is not booting up to the home-screen. I tried installing twice with no success. Any suggestions?? does this work on stock att rom??
[Captivate Android Development] mcbooth:
Installed fine on my Captivate. Quadrant of 1710, brilliant performance. Thanks!
[Captivate Android Development] InsaneJester17:
Flashed this on JH7 that already had unleash the beast, no lag fix and fightspit's circle mod. Works very well! This used it's own battery indicator mod but I just flashed fightspit's back over it.

Thank you!
[Captivate Android Development] alphadog00:
Thanks! Hopefully this will get rid of the lag when deleting emails in the stock app.
[Captivate Android Development] Hydrocharged:
I currently have my phone rooted with a trillion apps installed and everything, do I need to do anything special so that I won't lose everything? Or can I just flash this straight from the update.zip? I want to make sure I have absolutely no problems. I'm still running jf6. And I already have a lag fix installed.
[Captivate Android Development] mesasone:
Please take the garbage to the curb and stop attacking other users. If you have an issue, take it up over PM. Let's keep this thread on track to the subject of the Voodoo lagfix and not petty squables.