Am I right there there still is no 220.127.116.11 available for D-Link USB Bluetooth adapter? :-(
Anyone found a version of 18.104.22.168 that might work with the D-Link and/or know how to crack that license-thing? It is totally rediculous that they protect these drivers and keep some from getting them.
The main reason I am looking for the new drivers is to be able to use my Jabra BT200 as a headset with my D-Link dongle.
You don't need 1.4.*.* to use a Jabra BT headset with a dongle.
1.3.*.* supports this fine - certainly does with my TDK USB dongle.
Not much use anyway as a PC headset - mono with a crap audio response. Great for a mobile phone but not for any better quality audio.
Better to get a proper stero headset if you can afford it.
P.S. manufacturers protect their ported and tested (at their expense) code because cheapskates try to buy cheap hardware then rip off the work that they haven't funded. If there is no financial benefit in porting new firmware then why should they do it?
IMO, I have to agree with you that 1.4 does not provide any improved audio functionality over 1.3*. If you want the "headset profile", 1.3* is sufficient.
Testing under 22.214.171.124 & 126.96.36.199 gives the same results as 1.3*:
1. mono quality,
2. inadequate handling of voice stream from mic to pc while voice is simultaneously streaming from pc to headset, and
3. transmission break-up during high CPU.
As in earlier testing of 1.3*, I've returned to using a "wired" stereo headset/mic in order to enjoy a "normal" environment.
The chipset in the BT headset (designed for the sole purpose of voice to mobile) seems to also present a limiting factor.
I'll try to find the link to an article that I recently came across that broke down the components in a SE HBH-60 headset which amounted to about $5 to $10 USD in materials (not very sophisticated!!).
Chris Chris Chris, you of all should be aware of the Audio Speed problem have many have experienced. I can say that it did not work correctly (speed was played back very fast and VOIP sound would be extremely noicy)
With 188.8.131.52 it finally works. Before it was unusable and only made it possible to listen to audio on the headset. Now it can be used with VOIP.
I have not experienced the high CPU usage problem. Have not tried using it with e.g. games yet where that might be experienced.
I am getting confused again over version numbers of ports/stacks.
I was assuming that the 1.4 referred to the version of the Bluetooth spec., and that the numbers after 1.4 were specific to an individual software supplier i.e. TDK would have different serial numbers from e.g. Belkin or D-Link.
This was based on the assumption that different teams were porting diferent stacks.
So does e.g. 184.108.40.206 cover all ports, does it cover all different manufacturers using e.g. Widcomm, or are all numbers different?
LittleGrayCat, it seems that 220.127.116.11 was sent out to all manufacturers. DLINK released it first, and I've got a beta from TDK. However, TDK did not release this version, and continued working, testing, fixing bugs. Apparently they're working on 18.104.22.168 (same as a couple of other manufacturers).
So, for me it looks like all companies have access to the same version, they adapt to their requirements, and some will release sooner, others will release later - as I said depending on how their testing goes, if something is missing and they prefer to delay than having users with problems, etc...
In my opinion the way the drivers are handled is totally ridiculous.
To my knowledge the hardware in the different CSR BT-units is completely identical and use the same drivers. Its a load of boloney that the companies do their own testing and modifications. In my opinion all they do is adapt the material to their product names and useless security/copy protection.
There is a reason why (for example) the MSI driver is so cheap compared to the other units. They clearly arent spending any time/money on developing new versions of the drivers. You cant really complain that WidComm want to make a profit from selling their BT stack. Afterall the drivers that run the actual devices are only a small part of the whole BT stack.
[Chris Chris Chris, you of all should be aware of the Audio Speed problem have many have experienced. I can say that it did not work correctly (speed was played back very fast and VOIP sound would be extremely noicy)]
Sorry, maybe you're getting confused re: my earlier comments to LittleGreyCat. They're simply a general feedback on PC - headset quality of use and the version number required for use. Version 1.3* was the release which first offered the headset profile. My comments and observations have remained consistent in that no real audio improvements have been observed in subsequent releases.
As you'll note, many users are confused regarding versioning, etc. and many become confused in the need to jump to later releases, say 1.4 when all this release provided was HID support.
I guess I'm missing something with the audio problem in 22.214.171.124. I've never had any problems (outside of the quality, CPU, etc.) in using with MSN Messenger, NetMeeting, Net2Phone, etc. None of these apps. require the recording and playback for "realtime" use.
The audio speed problem occurs when recording and then listening to playback in XP only?? Correct??
Are you saying that voice speed in the realtime audio stream is also increased? Because I'm not having this problem.
Let's ensure we're identifying specific problems/issues for the benefit of others. ;)
I had done the same action as IBM Thinkpad that I had thrown away with my TDK BT, IBM had released 126.96.36.199 for their Thinkpad notebooks with BMDC (from ActionTec) which is very good in reception and compatibility with my Logitech BT Mouse and SONY Ericsson T610.
For TDK, I got a lot of errors and problems even in 188.8.131.52.
Also, I had seen 80% of manufacturers had released their Widcomm software except Boardcom chipset manufacturers and TDK! However, when I used 184.108.40.206 (w/ modifications) for Broadcom chipset, it is 100% working except Audio profile. While in TDK, it did not work good.
That's the reason why TDK BT suddenly disappeared in Hong Kong and Singapore although it was very common in 2002.
As you had seen, TDK had 1.4.2 software since May, but TDK never launched for public for 6 months, which is unbelievable to me!