com.apple.geod process is not responding

I Don't believe that us the problem- I have ZERO notifications set...

You know something, that is an excellent point you have there. Extensions...

My Safari only has 3 extensions installed they are:

• My eBay Manager
• 1Password
• Ghostery

Now those last two are ones that I don't know how I ever got along without them. 1Password is in the App store and is the absolute best password manager you'll ever find. But Ghostery is an awesome App. It will block cookies as well as plugins and advertisements. The two biggest benefits I've seen have been much, MUCH faster load times of web pages (it works with Safari, Chrome, and Firefox), as well as stops those annoying autoplay videos. As a default, I have 3 trackers enabled: Omniture (Required by Apple), Facebook Connect, and Twitter Button. Those are really the big 3 that I need for about 99% of the websites that I visit. Some certain shopping sites won't show prices/items unless some special trackers are enabled (probably to prevent price checking bots from scanning them as well as to track consumer browsing habits). If need be, you can temporarily pause some trackers if you need them. Like the vimeo player, though YouTube is unaffected as it's HTML5.

Give that a try to both speed your computer up, as well as to try and see if perhaps it's tracking cookies and animated advertisements that might be triggering Location Services. In any case though, it does greatly speed up your browser. For me, Safari is indeed significantly faster than Chrome. Especially when it comes to loading Flash animations.

First time I've added anything here, but I do come to these very helpful forums frequently in search of answers. This particular issue is worth a comment.

If I understand this correctly, there is an issue with Yosemite (one of many) that many of us have, nobody really has a handle on what causes it or what effect it is truly having, there are 6 pages of comments and yet, there really doesn't seem to be an answer. I've read through all of this and still have the issue after trying what I feel are the most likely solutions. One thing I haven't noticed is that not many folks mention actually forwarding this problem to Apple.

I know that Apple monitors these forums, but there is nothing like direct customer input to spur the great and wonderful to action. I also understand that this problem is likely on the list of Yosemite fixes, but apparently it isn't to high, I suggest that in this case, the most effective way to get the problem addressed for everyone experiencing this to report it directly to Apple. After all, how do we truly know if this is affecting performance or not?

Just my two cents. You know the adage - squeaky wheel, oil ... And yes, I'll be calling Apple Care today. I'm also working with an Apple Senior Tech on another issue involving Yosemite and I'll be mentioning this to him.

Well now either you did not read all of the pages, or you failed to comprehend what you've read.

1. Numerous people have reported they have spoken with AppleCare on the phone for this issue, and have spoken with a live person when reporting said issue.
2. At least two of us have successfully submitted separate Bug Reports to Apple regarding this issue through their appropriate channels.
3. Working together we have developed a workaround for said issue in terms of both terminating the process itself, as well as identifying the triggers of said process to avoid it from starting at all. This includes, but is not limited to trigger applications as well as how the Yosemite 10.10.2 update has also affected this issue.
4. We obviously know that this is affecting performance due not merely to the number of posts in this thread alone (as there are others), but from what the posts including my own have described.
5. The squeaky wheel does not always get oiled. But Apple apparently has either updated their code, or done something else to help resolve this issue somewhat. Even then the worst symptoms are being seen with vintage machines and older equipment. That I can attest to as between 10.10.2's new behaviors with the com.apple.geod process and the installation of a new SSD that replaced a HDD that was over 7 years old (way, WAY past it's useful age), the problem has rectified itself to even my satisfaction. There is a reason that all equipment becomes obsolete.
6. Not only do we here not work for Apple, auditing processes and debugging code is not our job. We merely put the time in to help both other users and Apple if they come through and read this, the Bug Reports, and AppleCare calls.

Again your words deriding us are both insulting as well as the direct result of you not reading/comprehending this thread. Perhaps thought it is in order to discredit our private time and work that we have all submitted so you can somehow ride in after the battle to claim a victory for yourself.

You are a very sensitive person. I wasn't deriding anyone ... just suggesting. In fact, your email was far more derisive than anything I wrote ... that much I do comprehend. Sorry, but I didn't notice a large number of folks interacting with Apple Care. Also, a "work around" is nice but doesn't address the core issue. Claim a victory for myself? Are you nuts?

Sorry if I hurt you feelings.

Go off in the corner and have yourself a good cry. Also, don't respond ... I won't be back. Life is too short for this aggravation.

Don't worry about what DMCVegas says. When I read his posts, it sounds like a "I-know-it-all" type of guy along with praising how good of a job the Apple engineers are doing. He might be on to something, but I don't think it's an easy solution that applies everywhere. If it was really that easy such as running a script once in a while, Apple would have fixed this stupid bug already.

His workaround along with others probably worked for a while until some other process triggers the com.apple.geod process.

My workaround was to completely stop using Safari (use Chrome instead), iPhoto, and disable all location services. My workaround also probably worked well until something else triggers it again, but I hadn't used it more than couple weeks in that state so I don't know.

I agree with you, users have to report to Apple to get some attention on this problem. I tried to report it once, but then I was greeted to a pay-for-support type of Apple Care screen since my Late 2013 rMBP is out of warranty. I was like, what? Really? Then I read from others that I have to use another route for bug reports but I haven't spent the time to find out how. After couple weeks of frustration and uncertainty of the stableness of the OS, I just went back to another clean install of 10.9.5 and everything is working perfect so far. No stupid com.apple.geod process, and no attempt on iDevice experience integration stuff. Only problem I see in 10.9.5 right now is the wallpaper changes back to default wallpaper when I reboot. It is annoying to have a bug, but I don't reboot often and it's much better than the bugs in Yosemite so I'll live with it.

Good luck with getting Apple's attention. I'll eventually install Yosemite, but not in the near future.

DMCVegas has done a lot of testing to see what causes this issue. I have as well but still no solution. I have reported this to Apple but like many other issues with Yosemite they are slow to address and never really admit to most. I have reverted back to Mavericks until such time I see this and other issues addressed.

In my case the issue resulted from the problem with my Mac's serial number. After upgrade to Yosemite serial number was in state "UNKNOWN" (in the window "About This Mac").

I had problems with iCloud synchronization and I noticed also issue with "com. apple.geod". When I realised that the problem is with serial number or rather its lack, I started to search for a solution. I found how to set the serial number on that blog (http://rogersm.net/icloud-problems-mountain-lion-serial-number). After setting valid serial number all problems disappeared... I don't know why the serial number was lost during upgrade. This is probably Apple's fault... ;-).

So my advice is to check if you have valid serial number and in case of its lack, you can:

a) Go to Apple service and ask to set the valid serial number

b) Use procedure from the blog (on your own responsibility)

Hope this can help.

Br,

Robert

No issue with my serial number but not responding continues.

It looks like the annoying geod not responding problem is fixed in 10.10.3 - at least, it has not shown since upgrading to the public beta. Hopefully it stays so.

Fixed it for a few boots, but now is back to not working again 😕 Why would this be such a major issue with Yosemite, when it worked just fine with Mavericks, and for several years before.

Is this with 10.10.3?

Yes.

But I disabled and re-enabled Location Services. This seems to have solved it for now at least!

I've read this thread with great interest. I am trying your suggestions, hoping they may solve my problem. My problem may not be the same as yours, but I will share regardless.

Since I installed Yosemite in the fall, I had random crashes (unexpected shutdown/restarts). Just 2-3. I let them go. After the latest Yosemite update in February, my iMac crashed every day in a row for five days. Usually starts with "iCloud can't connect..." window that pops up on my desktop. Not long after that, sometimes within a day, the unexpected shutdowns/restarts occur. I've contacted Apple as well. I've documented every single AppleCare call. I even took my iMac in to the Genius Bar and let them troubleshoot and clean reinstall Yosemite. I've sent in crash reports. I have jumped through hoops, resetting PRAM, SMC, and a zillion other suggestions senior AppleCare advisors have made via Terminal...blah, blah, blah, and as I said clean install of Yosemite, yet nothing solves the unexpected shutdowns/restarts. Sometimes they occur while I am working at the iMac, while other times they occur when it has not had any human activity for four days.

I've been an Apple person since 1984, and this is the first time I've ever wanted to toss one of my Macs to the curb. Thanks for letting me vent. I share your frustration.

I just upgraded from an late 2009 iMac to a new 27" with 5K display - love it. HOWEVER, I have had EXACTLY the same problem you are having and it began as soon as I migrated my system over from the old Mac. I've been in touch with AppleCare but they don't seem to have a handle on it either. Time for another call and I'll use your post as supportive documentation.