MacBooks Experiencing Bluetooth Problems
flowolf writes in with news that Apple seems to be having difficulty getting to grips with a Bluetooth problem on MacBooks. Bluetooth goes unavailable intermittently from what users are assuming is a hardware problem, and while it's out the machines won't stay in sleep mode. Complaints started last spring on the Apple forum, which is still quite active. Many people have had to send their MacBooks for repair more than once without a satisfactory resolution.
I recently moved, and found some troubling differences in Bluetooth performance. At the old place, my bluetooth keyboard and mouse worked quite solidly: smooth responsive mouse motion and I could type full speed without problems. The range was quite good with no deterioration at 5ft. At the new place, the mouse often jitters or sloshes as I move it, and if I type quickly, once in a while it will receive the keystrokes in a different order. (At first I felt it was just an occasional transpose mistake on my part, but every once in a while, a whole word will be received *mostly* backwards.) There's a noticeable improvement/degradation effect if I simply move a Coke can around on my desk, even if I keep the mouse within about 2ft of the Mac. The mouse is so bad I switched to an older radio-based wireless mouse instead.
I'm guessing from other cases mentioned on the web that Bluetooth gets stuck trying to resend packets if there's interference killing some packets. I imagine this sort of jitter and resend loop can be a big problem if it happens in a sleep mode.
[
Complaints started last spring on the Apple forum, which is still quite active.
Oh don't worry, we're working on erasing those complaints.
- Apple's Support Team
The real problem is the total lack of communication from anyone on Apple's side to these kinds of problems. Bluetooth problems have been an ongoing issue since I started using Tiger (10.4.4), with everything from the aforementioned "Bluetooth unavailable", to problems with using DUN via Bluetooth (dial up too often via DUN and it just mysteriously dies), to issues where Bluetooth PAN simply disables itself. Now after a good 2 years this kind of stuff gets really tiring but no one at Apple says a word which adds an extra layer of frustration to the whole process. Are they even aware of the problems from their aluminium tower?
Now compare that with Microsoft who also had Bluetooth problems with their phones, and you can actually get some kind of interactivity with the developers. Your end users might end up being a bit nasty to you on the forum, but it's far less than the ill-feelings your brand generates if you just clam up.
I haven't been terribly impressed with bluetooth. I bought a (rather expensive) bluetooth mouse for my Acer laptop, and I keep experiencing random disconnects in Windows with it. Not in Kubuntu, though. The mouse works perfectly in Linux.
And evidently the XP Bluetooth stack is some third party thing you can uninstall and reinstall, because I had to reinstall it to even get it to do anything.
And it seems that most phones have very few bluetooth features beyond headsets. Like you can't upload and download photos without some crappy phone tools software if you have a Motorola.
Has anyone found bluetooth to be reliable for them? Any success stories?
Anecdotally, I have a MacBook and the Bluetooth has always worked fine, but I realize that anecdotal evidence isn't worth much.
For the very same reason, I'm not sure if this is a story if the only evidence to support it is a thread or threads on Apple's discussion pages. You hear this all the time: "Hundreds of people are posting to the forums about this problem, but [whatever company, Apple in this example] refused to acknowledge that it's a major problem!" Well, here's the thing, if the company sells millions of computers and a hundred people are having a problem... in fact, let's say that the posters on the forum represent only a small percentage of people that are having the problem, so, it's a few thousand units that have the problem, it's still statistically small, even if it looks like a major issue on the forum and feels like a major issue if it happens to you.
It's not that it's not important or that Apple shouldn't fix it, it's just that it's not a news story, IMO.
Posting this to Slashdot with no other links about the story seems like somebody's just looking for an excuse to write a negative Apple story, but maybe that's just my tinfoil hat talking.
I'm just sayin'.