Currently Being ModeratedAug 23, 2011 6:26 PM (in response to Ryan Homer)
yup, i had this problem too. i have a new 2.2ghz macbook pro and while at a coffee shop, i noticed my battery draining very quickly, and a look at activity monitor showed that BTServer was running away with high-cpu utilization. i killed off the process and didn't notice any loss of functionality.
not sure what it was supposed to do with so much freaking cpu cycles!!!
is this for bluetooth? i dont even have bluetooth on. im not happy about this having to be something i'd need to keep a eye on when i'm trying to maximize my battery life.
Currently Being ModeratedAug 23, 2011 6:30 PM (in response to timmysf)
okay, follow up here - looks like BTServer is launched when I have the ipad simulator running when doing xcode work. quitting the simulator will also end the process.
might be a necessary service for the ipad simulator, but whoa.. lets take it easy on the cpu, mmkay?
Currently Being ModeratedAug 24, 2011 11:51 AM (in response to timmysf)
I'm having this same probem myself on a new MacBook Air running 10.7.1. I'm a developer as well, so that makes sense if it has something to do with the iOS Simulator. Hopefully Apple will update the software soon to fix this problem. In the meantime, I've just been using Activity Monitor to quit the BTServer process. My fan slows down right away when I do.
Currently Being ModeratedAug 25, 2011 2:07 AM (in response to Ryan Homer)
I also noticed this issue a short while ago. But with a slight difference from what some of the guys above wrote – iPad simulator was already shut down almost 6 hours ago, and since then the MacBook has been sleeping until now.
Currently Being ModeratedAug 25, 2011 5:17 AM (in response to ThePablick)
I don't think it has anything to do with Lion. I'm having the exact same problem under Snow Leopard 10.6.8
I think it is something in recent betas of iOS5.
I'm a developer too, and this problem only appears when I leave the iOS simulator open (if unused).
Currently Being ModeratedAug 25, 2011 2:56 PM (in response to Ryan Homer)
Just confirming I have this issue, too. And that killing BTServer works.
I have noticed this since installing Xcode 4.2 w/iOS 5 beta 6. It has occurred on a MacBook Pro running Snow Leopard and a MacBook Air running Lion, so it seems OS-independant. Also, the iOS simulator is not necessarily running at the time of high CPU usage, but has been launched since rebooting. Sometimes, simply relaunching the simulator does the trick.
Cool down, little Air, coooool down.
Currently Being ModeratedSep 2, 2011 10:48 PM (in response to Ryan Homer)
I recently noticed the same issue, and a lot of the supporting details match - dev working a late build (aug 2011) xcode 4.2, running iOS simulator. BTServer doesn't always start going crazy, but on my 2010 macbook air it will occasionally start taking up 150-170% cpu in activity monitor, and I'd kill the process to good effect.
Tried quitting iOS simulator and that does the trick as well. I just wish there was a way I'd get notification that it's going crazy sooner than waiting for the fan to start ramping up and the battery draining.
Currently Being ModeratedSep 12, 2011 4:29 PM (in response to Ryan Homer)
Just had this problem, and I have indeed launched the iPad simulator since rebooting my machine. I was doing some coding work in the morning, went to lunch and had some meetings, came back to find my machine running at 97º C (!!) and the fans both raring away at 6,000 RPM. Killing btserver in the Activity Monitor quickly brought things back down to normal.
I'm on 10.7.1 and Xcode Developer Preview 4.2 Beta 7.
Currently Being ModeratedOct 10, 2011 8:09 AM (in response to Ryan Homer)
Same problem here: high CPU load caused by the BTServer process even in Xcode 4.2 GM on Snow Leopard.
The problem seems to always appear when waking up a MacBook from sleep with the Simulator left running.
Currently Being ModeratedOct 14, 2011 6:17 AM (in response to Ryan Homer)
Me too with XCode 4.2/iOS5 release. Ironically makes iOS developing on the move - i.e. on a Macbook Pro using battery power - very inconvenient. Battery life is ridiculously small when the simulator is running now. Plus fan comes on within seconds in any situation.