Not responding processes in Actvity Monitor: callservicesd, coreaudiod, com.apple.geod, identityservicesd, and icloud helper

Also see whether the Flash Player is up to date

Nisalm, That's hopeful about the yosemite update. My flash is up to date. But there is def something I do during normal operations before this service stops responding. I'm keeping activity mon open and trying to watch it as I open, use and close things through the day. I'll post again if I can get a reasonably conclusive cause and effect.

Hi mi_lo, no I haven't try a clean installation, I can do it cause i have an external disk and a time machine's backup. Maybe i try but I don't have much problems with those services except that the mac is blocked for a minute few seconds after start and sometimes itunes is stopped too for 30 sec. It's boring but I can wait for the next upgrade/fix. Last thing... i have an end 2009 Imac 21", thanks for answered!

Checked.... no digidesign plugin but I have Hear plugin, a little app for audio control..maybe i have to try to uninstall it...but surely it's a yosemite problem!!!!!

Hi Cubelibre,

That might be the one causing the issue.

Go to Utilities>Audio Midi Setup and see whether there is anything below "Built-In Output". In my case, it was DigiDesign Core Audio.

checked again but i don't have any digidesign file on my mac....thanks but I think that the problem may be another audio app installed....i'll try to unistall those apps and see what happen

I saw the same problem occur in my system as well after a clean install and formatting of my HD.

the system runs smooth and the way it should except for these couple of files that start "not responding".

seems to be unhurtful to the system and doesn't raise any high cpu percentages.

its got something to do with location services

heres a link i found - you have to translate the japanese using google translator but at least it proves it's a known bug

http://www.atsuhiro-me.net/apple/mac-os-x/geod

Check This Link Out - it might be a fix, I'm gonna try it

http://apple.stackexchange.com/questions/155326/location-services-not-working-in -os-x-10-10-yosemite

this fix worked for a few days but I just checked the activity monitor and its stuck at "not responding" again.

nisalm,

I've been reading the discussion on this issue and I was curious... I don't have the Digidesign CoreAudio.plugin but I do have AirPlay.driver, AppleAVBAudio.driver, BluetoothAudioPlugin.driver and iSightAudio.driver. Are these files supposed to be in "HAL"?

Thanks in advance! (:

Hi Jenn,

You just have to delete the Digidesign CoreAudio.plugin (not the HAL folder) 🙂

Hey Nisalm

I've got Protools installed and have tried to find the digidesign CoreAudio.plugin in the HAL folder but it's not there. The only plugin i have in there is Avid Coreaudio.plugin, is it the same thing?

Hi mate,

Currently Pro Tools is not compatible with OS X Yosemite. You'd better uninstall the application and see how it goes. However, I don't think that Avid Core Audio plugin is the issue but I'm not sure, to be honest.

OK so I took it upon myself to do some research because I was not getting the response I required quick enough. I personally have protools on my computer. So I followed the instructions on going to the library and updating the plug ins.

go to your computer

go to library

go to audio

go to plug-ins

go to HAL

see what kind of Plug-In you have, mine was DigiDesign

remove plug-in and reinstall

This stopped my issue with the coreaudiod, callservicesd, & identityservicesd. I have not seen these stop responding in the past 3 days.

However I am still having some issues with slow response going between functions on my computer. Which I do not understand because I have 45GB open on my hard drive. But it is no where near as bad as it was before. Over the next week or so I will be removing a lot of pictures, video and music onto external hard drives. Cleaning my desktop, and getting rid of programs I don't use.

I hope this helps because it was really frustrating for me.

I found the avid.coreaudio.plugin was the culprit. Moved to trash, renamed it (just in case), then rebooted...so far all good.