Alternative bluetooth drivers anywhere??
I have been trying for some time now (as have many, many people here) to get a BT Headset/Audio Gateway profile to work satisfactorily as a speakerphone through my CarPC using Widcomm 3.X and 4.X. There are a few critical problems folks have encountered that have been scattered throughout various threads here:
(1) excessive noise, sounds like 'skipping' of the audio -- as yet unexplained (?)
(2) auto answer issues ('mostly' solved with Widcomm 3.X as opposed to 1.4.X)
(3) huge processor load when connected via headset profile to the phone, causing Centrafuse (and any other app) to slow down substantially when attempting to pass the phone audio to the PC
(4) anything else I missed?
I have a SE T637 with IOGear GBU311 BT, Via M10000 512MB, XP SP2, Widcomm drivers.
(1) and (3) are related: turns out it is the driver itself that is causing the excessive load -- btwdins.exe and services.exe hog about 30-50% of my CPU when the Headset profile is connected. (2) has been addressed but the verdict seems to be that the Widcomm SDK is cost prohibitive, such that Zorro needs $1500 in order to develop this functionality for PhoneControl.
My test system for software installations is an IBM T41p. Needless to say, this can handle everything simultaneously with no problems: BT Headset connection, PhoneControl serial port connection, audio playback, GPS, XM, blah, blah. What's funny is that task manager reports very little load (<5%) on the processor when doing all of these things. Is my P4 2.0 GHz really that much better than the processor in the M10000? More importantly, given the low bandwidth of the BT audio connection I seriously doubt the BT stack needs to hog the PC that much to make the Headset connection happen.
Conclusion: Widcomm drivers don't cut it, at least not with my current config. XP SP2 doesn't offer a Headset profile. But the VoIP world really wants to use BT for calls using existing wireless handsets, ala Vonage (see http://communications.siemens.com/cd...iption,00.html or http://www.calls-calls.com/shop/product.cgi/CFSE1/3/) .
I'm hoping someone using an M10000 has found drivers -- Widcomm or otherwise -- that can make the Headset connection happen without the 'audio skipping', or maybe there is some simple XP tweak. Since most of us only need a single serial port, Headset/Audio Gateway connection, and maybe OBEX are there any other simpler drivers out there?? I think Longhorn will have the Headset profile and will *possibly* be more efficient, anyone beta tested it yet? Any ideas please!!