I just got a bluetooth headset and am trying to set it up with my computer so I can just it with ichat. The headset is a Tekkeon eztalker mini and I am running os 10.4.2. when i try to set up the device in the bluetooth prefs I get this error "Failed to set up the headset. Headsets are not supported on your Bluetooth hardware." Has anyone else gotten the error or know what it means?
Launch it from Applications > Utilities > Bluetooth Updater
Apply it to your adapter (takes very long).
Start the Apple Bluetooth Assistant and select Headset. Do not use anything else!
Make your headset Bluetooth visible. Look up the manual of your headset how to do that.
Now select the headset in System Preferences > Sound.
In most cases step 3 is missed. You have to start the installed updater yourself (do not ask me why). Step 4 fails if your Bluetooth USB adapter is not supported by Apple and you have to go for a D-Link DBT-120 USB adapter.
I'm also trying to pair my tekkeon mini headset with my computer for Skype.
I downloaded the firmware, and when I launch the application, and click update it says: "This Bluetooth device is not supported. This computer does not have an Apple Bluetooth module installed. It cannot be updated by this application."
I've seen your solution to this problem - which seems so widespread that it's amazing Apple won't/ doesn't deal with it - but it's unclear to me whther your solution requires a D-Link adapter, as you say in the post above. I can't believe that this can be true for Powerbooks with Bluetooth installed.
The problem I have, which hundreds of others seem to have, is that my Bluetooth headset - Logitech Mobile Freedom - pairs perfectly, even works in the beginning, but then loses connection, or connects for a second or two.
Now I've tried your solution a number of times, even trashing the Bluetooth preference file and reinstalling the update as you suggest, but it tells me, as it tells others, that it won't update because there is no supported Bluetooth module. Which is nuts.
I cannot believe that recent Powerbooks that have Bluetooth installed need external USB adapters. There must be another solution, a solution that hundreds of frustrated Mac users should be given by Apple.
No, for headset support you need either a Apple Bluetooth module or if not present a Bluetooth USB adapter, preferably a D-Link DBT-120.
Your problem is a Mac OS X v10.4 issue. I never had that myself but I doing most of my work in Mac OS X v10.3 still. Your mentioned problem is common and I have no solution for that one, except complain to Apple or try the various fixes here in the forum.
You say I need either a Bluetooth module or a D-Link adapter. But I have a recent Powerbook which has Bluetooth installed. The headset is recognised and pairs and even worked for a brief time but now disconnects within seconds. So I must have a Bluetooth module installed on my recent Powerbook, no? So why does the installer say I need one when I have one?
I'm answering this because, obviously, I have a problem, but also because the solution you have offered many times on this forum is clearly NOT a solution for many people. And I think you should make this clear. That for your solution to work you need an external D-Link adapter. Also, your solution does not appear to work with 10.4, you say, or, apparently, with recent Powerbooks that have Bluetooth modules. Your advice is gratefully recieved, but you need to be more specific about what kinds of hardware and software it will work on.
And if you don't know, you should make that clear before offering such specific advice. Thanks.
My advice fits all configurations:
– Mac OS X v10.3.2 - v10.4.3
– internal Bluetooth and Bluetooth USB adapter.
The problem is, you face a different problem. My advice is for all who cannot pair their headset at all or being more precise cannot link a Bluetooth headset with the Sound Preferences. Your problem is totally different. You face a bug in Mac OS X v10.4 related to Bluetooth headsets. Please see the forum for (several partial) solutions for this problem.
We talk about two different problems here. Cannot solve all problems on world with one advice, can I?
That is now much clearer, to me and I hope other people. I am not asking that you solve my problem - which is obviously a problem for 100s of other people too. It's just that I wasted a lot of time trying to apply the solution suggested by you when you now say that that solution does not apply to my problem.
I think in the future it would be much better, when you offer your solution, that you make it clear that it only works for those "who cannot pair their headset at all or being more precise cannot link a Bluetooth headset with the Sound Preferences", as you say in your most recent response. It would have saved me - and I'm sure others - a lot of wasted time.
In the meantime, does anybody have a solution to the problem that I and 100s of other appear to have?
The headset pairs, is discoverable, even works briefly, but then either does not connect or disconnects after a second or so. I have seen, on this forum, a fix which involves going into terminal mode, but the fix does not seem easily comprehensible to me.
Search this forum. There are several steps which solve it for some time or go back to Mac OS X v10.3.9. I think an Apple Bluetooth Software update is required. Let's see what v10.4.4 brings. Have you tried v10.4.3?
Is there a solution for the "cannot link Bluetooth headset with the Sound Preferences"?
I followed the advice. My BT firmware is up-to-date. I even tried it again to make sure, and the installer tells me it can't install because its already updated.
I can pair my headset - but it does not show up as an option in iChat microphone selection.
Ok, this is interesting. My headset pairs, connects, then drops. If I open my sound prefs and select the headset, it boots and I have sound. As long as I do not close that dialog (this trick from another thread), the headset remains active.
Clearly you need to have activity to the device to keep it on line - makes sense, to save power, though it apparently has "failed". The device bounces back in to try to cennect, then out again.
Fun part: if I open Skype and dial someone, the headset kicks in. So for the moment I am treating it as "on demand", though it is a little unnerving. Certainly don't like this pop-in-pop-out behavior. Maybe a bit of config I haven't read yet, or an OS bug.
A Traud mentioned some "force visible" feature of some headsets. While his posts are frequently incomplete, and I would not be very happy with him as my Helpdesk Attendant (sorry, Traud, but take a good look at what you're dishing out: what's with this Bluetooth Updater that is supposed to be run even if you are on new systems? Sorry, baby, strike two), still it is worth looking into, perhaps the headset is "proactive" and maintains its own connection?
I had a high-end motorola which I believe had this ability. I traded it in for this Plantronics Voyager 510, which is uncomfortable and can't do this nifty trick - maybe I'll switch back.
ok, more experience, so perhaps more help: apparently, if you are able to pair to the device to begin with, and make the sound in and out your headset, anything going to that pipe will wake the headset. makes sense. I just fiddled with Adium's sound setting, and even that fiddling woke the device. I also launched iTunes for the fun of it, and no issue.
Also, when the computer releases the headset, it is made available to other devices - such as my RAZR. When I click into voice dial names, it activates theheadset as well; I am also able to voice dial from the headset and designed.
so... maybe everything is working well for some of us, who thought the thing was bollixed up?
But of course! that annoying behavior of popping in and then popping out again is due to the systems sounds that occur now and then... like a system "Stop" or "Error" sound. They trigger the headset, because I have system sounds set in/out to the headset.
The key here is to leave system sounds on your speakers, and them configure each specific software to take in/out from your headset.
In my case:
- I paired Bluetooth with the headset., and it appears in the list.
- I went to Sound Preferences, and made sure my SYSTEM sounds remained at whatever default I wished, in this case laptop mic and speakers
- I went to Skype Prefs, found Audio, and explicitly defined in/out to be my Bluetooth Headset (which appeared in the list)
- Adium does not support audio chat at present, so there are no settings for - I use Adium since I have multiple IM accounts, across MSN AIM YAHOO ICQ platforms...
- iChat doeds support audio, but wasn't able to find the audio in/out settings... it did kick my audio out on once or twice. I don't use the program, so you'll have to figure that one out 🙂
Pardon? Do not understand anything you want to tell us. There is no
force visibility trick. Again, you miss the initial point of this topic – perhaps if you do not see all posts in this topic, please unfold all of them. There are two issues with Bluetooth headsets around:
1. Get to pair with a headset.
2. Get to keep a connection to a headset.
The symptoms of issue 1 are either no
headset option within the Apple Bluetooth Assistent (Mac OS X v10.3) or a message telling you, your hardware would not support headsets (Mac OS X v10.4).
The symptoms of issue 2 are frequently dropped connections and problems to create a new connection (in Mac OS X v10.4). I never experienced this myself (in Mac OS X v10.4) and I cannot and have not provide any further help on this one except to go for Mac OS X v10.3 which is more stable when it comes to Bluetooth headsets.
