3846 Views 7 Replies Latest reply: Feb 28, 2007 10:02 AM by David Fritzinger
I've been having the same problem over the last week - the 'squiggle' appears then disappears after a reset, then reappears again after 20mins - 1hr. It even appears to cut out mid way through a sync cycle.
Also, the Bluetooth icon disappears from the Preferences pane whenever this happens and only reappears again after a successful reset.
I have a suspicion it's probably a hardware fault.
Any ideas anyone?
i have the same problem on both my C2D MBP and my sisters C2D MB, sometimes the bluetooth hardware is just lost by the computer and isnt found again for a while, usually takes a retart or two. I notice it most when traveling, perhaps bumps (while the laptops are closed and asleep) cause them to forget they have bluetooth? Or worse, bumps cause the bluetooth connectors to become dodgy? How odd. This could be a nasty little issue.
Any one else has simmilar problems?
MBP C2D 2.33GHz Mac OS X (10.4.8) 160GB 2GB APX/BT/DVD-RW
this happens to my CD MBP as well this week.
the Bluetooth became "unavailable" and was not even found in the "system preference->hardware".
after resetting the PRAM and rebooting for few times, it came back.
Can anyone explain what th eproblem is?
MacBook Pro Intel Core Duo 2.0Ghz Mac OS X (10.4.8)
[UPDATE] after over an hour on the phone with Apple Support, they have concluded to a hardware failure and asked me to drop it at the nearest Apple Center for repair.
I noticed an increased fan activity too while doing just nothing. Fans were running at 6000rpm+ and the computer was getting hotter by the minute.
I'll post an update when I collect my MBP after repair - hopefully sometime over the next 10 days.
MacBook Pro C2D 15" Mac OS X (10.4.8)
I've seen similar problems. After my MBP (CD-1.83) has been on for a while, I notice that, on opening, it will show the screen for a second, and then the screen will turn blue for a moment before showing my normal screen. This is in addition to the bluetooth suddenly becoming unavailable. So far, a restart has solved this problem, but it is worrying (I must say that I haven't thought that much about it, since I don't use the bluetooth). Anyone know what is going on?