Q: FaceTime making strange clicking sound since OS X 10.10

The bottom line is with a lot of experimentation, I believe the issue is with the Bluetooth/wireless cards in 2011 MBPs.  Continuity is expecting BT 4.0 and current BT/Wifi cards.  Even though Handoff and instant hotspot rely on BT 4.0 and phone calls and SMS use wifi only, the Yosemite code has an issue handling FaceTime and the wifi continuity features with older hardware.  Apple either needs to find the root cause and patch the software so pre-BT 4.0 MBPros can still use FaceTime and phone calls with no issues or we all need to upgrade to current hardware. 

The Coreadudio process is messed up for non-BT 4.0 hardware.  I have traced all the issues to this process.  Whether SLEEP mode affects it or not, plugging in headphones, using BT headphones, or the internal speakers all have issues when you mix and match these devices and try to use them on the same machine.  FaceTime, the SOUND process in SYSTEM PREFERENCES, and the coreaudio process all get borked requiring a re-boot of the system.  I have even had issues with BT and Google Hangouts.  Apple needs to either get this straightened out or just come clean and make a firm stand that to use ALL continuity features without issue you need BT 4.0 hardware. Period.

FaceTime audio issue is caused by the headphone jack.   Whenever this is used and then you try to use either internal speakers or BT headphones, the audio issues occur.

Can we get a poll from the users on this post experiencing issues with FaceTime having popping and clicking noises when you try to make a call either with FaceTime or via Continuity with your iPhone:

How many of you were using the headphone jack prior to the issue occurring and then had it happen after the headphones were removed?  I have tested it many times and everything works fine until I use the headphone jack and then the popping and cracking audio issues return.  I have to do a complete re-boot to restore the FaceTime audio to normal.

I have never used headphones and I have this issue every now and then. Often on Macbook to Macbook and sometimes on Macbook to iPad.

Prior to 10.10 I never used the audio jack or BT.  After the upgrade is when the popping/crackling started every time I tried using FaceTime or Google Hangout.  Interestingly Skype continues to work fine. 

Based on a suggestion I read, I plugged in external speakers (and headphones) and the sound clears up.  If I unplug the popping/crackling comes back until I plug the speakers back in.  It's a pain, but I video chat a lot and this is a fix around that works for me.

I've updated to 10.10.1 and the issue still exists.

N3vn wrote:

 

FaceTime audio issue is caused by the headphone jack.   Whenever this is used and then you try to use either internal speakers or BT headphones, the audio issues occur.

 

Can we get a poll from the users on this post experiencing issues with FaceTime having popping and clicking noises when you try to make a call either with FaceTime or via Continuity with your iPhone:

What is your rationale for this conclusion, that the headphone jack is the reason for FaceTime sound failure? How have you tested this root cause?
I will also point out that I have not been using headphone jack when this issue has occurred, so I cannot agree that the headphone jack is the root cause of the popping.

Your suggestion to create a poll here in not recommended. I do not want to receive notifications for each and every new "poll result" that everyone will be sending to this forum thread. If people are mindless enough to start posting your "poll answers", I will be forced to stop following this thread.

I second JanRL's comment in all respects.

JanRL,

I spent over an hour testing it on my MBP yesterday.  I also spent over an hour with an Apple technician via remote log-in to my system 2 days ago.  From both testing scenarios, I was able to consistently reproduce the problem by either using the headphone jack or allowing the MBP to go into SLEEP mode on its own or by closing the clamshell.  This information has been shared and documented with Apple to hopefully help them find the root cause and provide a fix.

My intention is not to create extra update traffic for you or other users via this post.  I think you would agree this is a very frustrating issue for many people as evidenced by this post and several others on this subject.  My intent was to try to identify if other people were also either using the headphone jack or putting the computer to sleep on its own or with closing the lid to see if indeed this seems to be the common scenario(s) initiating the problem.   The majority of the responses on this thread have merely confirmed there is some audio issue with FaceTime in Yosemite but have offered no possible cause or way to avoid it other than doing a complete system re-boot.  I am merely trying to identify what may actually trigger the issue so people will know what to do to avoid the problem until Apple issues a fix.

I'm about to give up on Yosemite and go back to Mavericks.  On top of the FaceTime issue that Apple is apparently not going to fix, both my computers randomly become unresponsive for various reasons causing me to use a Force Reboot.

It's ironic.  The two reasons I decided to try Apple computers in the first place, is because of FaceTime and operating system stability.  Apparently Apple doesn't consider those two things to be priorities anymore.  These days, I see less and less reason to stick with OS X over Microsoft. 

Some of the posts on this very long string are obviously by hard core users with vast knowledge and experience with computers, and Mac products in particular.  Rather than do PRAM resets (admission: I had to look up PRAM ... "duh", after I relieved my ignorance) and all that other troubleshooting I've read about, I'm going to trust Apple to make it work how it should.  They've earned some "benefit of the doubt" here, as well as time.  I realize that's relative for everyone.  After years of frustration with Windows, which I still get at work, it'll have to get much worse before I abandon Apple.

Linux, anyone?

That said...  and I understand everyone's frustration, since updating to Yosemite, my MBP (purchased late 2010) has slowed, which, ironically, reminds me of my PC days.  However, referring to the problem that kicked off this thread, the last two times I used FT it worked fine - the only thing I did, which I always do, is shut down after use.

Haven't encountered a Force Reboot situation... yet.  Hope I do not.

It'll have to get much worse before I go back to Windows products.

-Greg.

I was in touch with AppleCare about this very same issue. The senior advisor had me collect some data (capture?) and submit it. I was supposed to get a phone call back with an update, never happened. I've more/less given up on FaceTime since this started, and now using Skype almost full-time. I've had no issues with audio/video with Skype in Yosemite, only with FaceTime.

As for Apple, I think they are lost and not as focused on user experience AND quality as they used to be. The User Experience is garbage if he/she cannot use the software to begin with.

The best fix for this issue was posted a couple of months back - open iTunes and mute it.  That ended the feedback issue until Apple can figure out to upgrade their software to do the same thing - apparently they're tying Facetime/iTunes in together and the speaker just don't like that

First off...  That "fix" does NOT work.

Secondly, Apple released a Beta version of Yosemite to over a million beta testers.  A workaround shouldn't be required in the first place.

Once Yosemite left the Beta stage, it should work as advertised.  Microsoft has to address countless thousands of vendors building a multitude of PCs.  Apple controls both the hardware and software.  They have NO EXCUSE for turning out an operating system that doesn't work.

Apple is too focused on making political statements and fashion accessories these days to make a reliable operating system.  Yosemite is a JOKE!

It worked just fine for me so to say that it doesn't work at all is your opinion; as is the rest of your post. If you're not contributing towards helping the situation why bother posting?

Your "fix" does NOT work and it shouldn't be necessary in the first place.  As for my posting, if you don't like what I post, move to another thread.  I'm simply stating the facts.  A new operating system SHOULD NOT break existing features.  One should expect a new operating system to work at least as well as previous versions.  People like you probably don't care that Apple turning out inferior products, but I do.  I will continue to post as I choose.

Same problem.  Early 2011 MBP 15" after upgrading to 10.10.