Hi There.
I am using the mini which has the BT 1.2 while my headset (BTH778) has 1.1 version.
Most people complain about hearing me with noises and a bit metalic as well - could that be the issue? if yes, is there a solution?
Thanks,
Udi
Supposedly the MS Stack 1.2 is backwards compatible, but I also wonder about the 1.2 profile.
My Audi has 1.0 or 1.1, not really sure. The Blue Angel worked with my cars BT, but the JAM 1.2 cannot even partner.
The Maigician not being able to partner with your Audi has nothing to do with 1.1 vs 1.2. It is a matter of the MS stack not supporting the "handsfree" profile as required by the Audi. (Or if it is the "headset" profile that is not supported, can't remember).
Makes sense.
Hope someone can figure out how to replace the MS Stack with the newer Broadcom Satck.
Or rather, let us hope that Microsoft provides an updated stack with support for a few more profiles. Apart from the lack of profiles the MS stack seems to do the job pretty well.
I wouldn't count on MS to provide much. They never provided an profiles since 2003 for the MDA II Device, which had the MS Stack, albeit 1.1.
Related
Surfing the web, I noticed that Widcomm just launched a new BT development kit for the PPC/Phone Edition (That's the one we have!).
You can find information here:
http://www.widcomm.com/Products/bluetooth_comm_software_btce.asp
This is what they got to say about it:
NEW!
BT-PPC/Phone Edition leverages current BTW-CE/PPC features and includes the following profiles (GAP, SDP, SPP, GOEP, OPP, FTP, SYNC, DUN, HSP, HFP & PAN).
Key features of this product:
Addition of WAN connectivity features
Implement cellular connectivity
Manage audio traffic routing to headset
Display radio signal strength (RSSI) on screen
Implement power management scheme (enable WAN connectivity while PPC is off/sleep)
Initial release OMAP platform
I am extremely interested to know if anyone knows where to find an installable app for our XDA's. The fact that they say that an initial release is only for the OMAP platform worries me slightly, because I think that only the orginal XDA was based on that.
Best regards,
Bastian
I do not believe Widcomm sells directly to end users. They sell to OEM's to include in their product. The product can't be just installed. It has to be tailored for each device individually by the OEM. So, HTC would have to package the software into one of their ROM updates. However, since licenses for the Widcomm BT stack cost money, I wouldn't hold my breath expecting HTC to foot the bill to give us a good BT software stack. I don't know for sure, but its a reasonable guess.
Besides, the Widcomm BT stack has been around for a while. There wasn't a specific PPCPE as there appears to be now, but the current version would have worked as well as the Microsoft stack that HTC uses now. If they didn't get Widcomm then, I wouldn't expect them to add it now. May for the XDA III
Hope....
Let's hope that HTC will do this in the future, because the current BT implementation sucks.
-Bastian
I think this isthe one for the new iAPQ h6300... As of the manual h6300 has the same BT Manager of other iPAQ devices but with some additional headset Profile, nothing about Handsfree Profile till now...
if this has been posted, apologies in advance and appreciate it if the thread link can be posted. if not...
been doing some browsing as i'm considering what ppc to buy in place of my ol'trusty xda2 running on wm2005. saw a lot of units, there's the atom, prophet, the upcoming muse, etc...
would like to ask about bluetooth. if a set has a built-in version 1.2 for bt; does this automatically mean it supports a2dp (for bt stereo)? read articles which seem to say that 1.2 does support a2dp...and read some articles which were downright confusing.
or would this fall under version 2.0?
cheers
did some more browsing and came upon this...looks like i answered my own question
"Unfortunantly the version of bluetooth that is installed into the 650 handset is 1.1 and this does not support data transfer of music through bluetooth. You would need version 1.2 to do this. Quote from palmone data sheet; A2DP (Advanced Audio Distribution: playing music wirelessly. This is Bluetooth 1.2, and the Treo 650 smartphone is Bluetooth 1.1)"
but feel free to correct me anytime
cheers
BlueAngel has BT 1.1, but has A2DP profile.
BlueAngel a2dp profile
I have a Blue Anggel (siemens sx66) but it doesnt seem to have the a2dp profile, i have recently upgraded the btooth stack and am on:
1.0.0 build 3900
to me this reads that i seem to have downgraded it? shouldnt it be at least 1.2.0 build xxxx?
im trying to find a different stack now, i want my music....
thanks...
Fact:
Microsoft's A2DP implementation in WM5 is incompatible with certain headsets.
Certain headsets, such as many Nokia and Logitech ones, sound incredible (as good as wired headphones), whereas others, like i.tech or Jabra, don't.
This has been a subject of much confusion to WM enthusiasts, since these headsets sound great when paired with other devices, however when used with a WM device, a high pitched ringing/hissing and slight distortion is heard when certain frequencies of sound are played.
Some Pocket PC users have temporarily solved their problem by porting the Widcomm Bluetooth stack over from the Dell Axim series, however it is generally buggy and not available for all devices.
Fact:
Windows Mobile 6 Beta was released, and had even worse A2DP than WM5
When the beta/demo roms starting floating around, many of us who experience the problem had a glimpse of hope that maybe it would be fixed.
But alas, the A2DP support had many people re-flashing back to WM5. It was even worse.
Fact:
THE FINAL RELEASE OF WM6 SUPPOSEDLY FIXED THE QUALITY BUGS OF A2DP!
There is a write up about this here:
http://forum.xda-developers.com/showthread.php?t=310438
Basically, the new devices shipping with WM6 seem to be more compatible with a wider variety of headsets than its predecessors.
Headsets with the static, popping, hissing, etc... finally sound good even with the Microsoft bluetooth stack.
Some of the new cooked Roms are starting to use this new A2DP support as well.
Problem:
WM5 still sounds bad with A2DP!
Those of us who don't have WM6 upgrades available, or don't want cooked roms or beta versions, are stuck with the poor A2DP of WM5.
Solution:
SOMEONE NEEDS TO MAKE A NEW A2DP PATCH using the WM6 drivers!
Remember when someone first made the A2DP support for Tornado available in WM5? If your device didn't have A2DP to begin with, all you needed was AKU2, and this patch would install the signed drivers and make the appropiate registry edits and like magic we all had A2DP (albeit crummy with some headsets)!
Over time, other patches were made, some using AKU 3.5 and other later releases that promised the possibility of better sound. But all of them failed.
What we need now, is for someone who has an official WM6 device (or someone who has access to a decent cooked ROM with the new A2DP support) to help make a NEW patch for those of us who need it!
Anyone out there willing to help?
Is it possible and if so, can any of the chef's here cook a ROM which includes the Microsoft bluetooth stack over the Widcomm one??
Cheers
+1
I know each has it's merits and problems, but I'm having more problems with the WIDCOMM stack than I did with the MS one on the HD, so I'd like to see this in a cooked ROM as well...
Agree. A good idea.
+1
I really hope this can be done... chefs, please help us out!
It cant be done easily. The bluetooth chips in these phones (TP2, HD2, etc) dont work with the microsoft BT stack because the drivers supplied by HTC, don't work with it. They're designed to only interface with the widcomm stack and software :/ God knows I hate the widcomm stack on my TP2 as well, especially the crappy quality of the A2DP protocol, but unless some very bright mind comes along that can hack/rewrite a driver to work with the MS stack.. we're out of luck :/
NRGZ28 said:
It cant be done easily. The bluetooth chips in these phones (TP2, HD2, etc) dont work with the microsoft BT stack because the drivers supplied by HTC, don't work with it. They're designed to only interface with the widcomm stack and software :/ God knows I hate the widcomm stack on my TP2 as well, especially the crappy quality of the A2DP protocol, but unless some very bright mind comes along that can hack/rewrite a driver to work with the MS stack.. we're out of luck :/
Click to expand...
Click to collapse
Thanks....and bugger
NRGZ28 said:
It cant be done easily. The bluetooth chips in these phones (TP2, HD2, etc) dont work with the microsoft BT stack because the drivers supplied by HTC, don't work with it. They're designed to only interface with the widcomm stack and software :/ God knows I hate the widcomm stack on my TP2 as well, especially the crappy quality of the A2DP protocol, but unless some very bright mind comes along that can hack/rewrite a driver to work with the MS stack.. we're out of luck :/
Click to expand...
Click to collapse
Thanks for the explaination NRG. You managed to get MSVC to play nice with your Energy ROM for the TP2... was that because of a updated or perhaps an older Widcomm stack?... MSVC not playing nice with my BT headset HD2 is killing me. I use it all the time when driving... Your TP2 ROM and perhaps another were the only ones that worked at all with MSVC
I emailed HTC to voice my "opinion" of the Widcomm stack... not that I expect anything to change
Thats very dissapointing to hear!
It´s very important for me to dial contacts using my bluetooth headset SE HBH-PK740 !
Hi there,
I have a Sony Ericsson HBH-DS980 and it can access the addressbook/last calls without any problem on HD2. Is there any chance you might have missed the permission screen before first access attempt?
Also compared to Cruise, Diamond and HD (all bt tweaks applied) HD2 seems to have the best quality stereo output out of the box with these headphones. The bass is great and there is no background noise at all.
I friend of mine uses TP2 with Sony Ericsson HBH-DS220 and the stereo audio quality is also superior to MS stack both on WM and Vista/Win7.
I think it would make sense to open an thread to highlight incompatible BT hardware so that at least users planning to buy new ones will get the right headphones.
sproxy said:
Hi there,
I have a Sony Ericsson HBH-DS980 and it can access the addressbook/last calls without any problem on HD2. Is there any chance you might have missed the permission screen before first access attempt?
Also compared to Cruise, Diamond and HD (all bt tweaks applied) HD2 seems to have the best quality stereo output out of the box with these headphones. The bass is great and there is no background noise at all.
I friend of mine uses TP2 with Sony Ericsson HBH-DS220 and the stereo audio quality is also superior to MS stack both on WM and Vista/Win7.
I think it would make sense to open an thread to highlight incompatible BT hardware so that at least users planning to buy new ones will get the right headphones.
Click to expand...
Click to collapse
PLEASE explain us how you access adressbook?Voicedial?
I have SonyEricsson HBH-PV740 and Motorola HT820 and no way to dial adressbook.
I can dial last number by touching headset button twice but there´s no way to dial any person from adressbook without holding HD2 in my hands.
Hi there,
I have paired the device as usual. Then two profiles were selected by default. (stereo audio and handsfree).
1 Connect to your bluetooth device. You will see the services (image 1)
2 Select your device and then press properties button on the bottom left. (image 2)
3 Check the box where it says "Connections authorised"
If you dont perform step 3, next time the headset tries to access addressbook, you will see a promt on your phone and you will need to allow it. If you miss this screen, the functionality will not work.
When you press addresbook button or call history button on your headest, you will see that a new service is added to the list of services (image 4) named Phone Book Access. This will only show when you are accessing the addressbook or call history.
I can see both the names and numbers on the screen of the BT headset.
Also, in ms stack I would only see a number for the incoming calls on my headphones. Now I can see the name as well. So this was another improvement of the new BT stack.
Regading voice dialling, since I have a small screen on my headphones(980), did not need it. I think MS voice command would do the job well. The only issue I remember from previous WM devices was you needed to get the right DLL associated so that you could trigger it with the dial button on the headphones.
These theads might be a good starting point regarding MS voice Command
http://forum.xda-developers.com/showthread.php?t=304224
http://forum.xda-developers.com/showthread.php?t=281977
you might find more up to date resources if you searh the forums deeper.
Hi there,
is there anyone know why the bluetooth was downgrade from 2.1 in WM6.1 to 1.9.3 in WM6.5 in T-Mobile TP2? Any way to upgrade it back to 2.1?
I have a Sony Ericsson HBH-IS800 headset that requires Bluetooth2.0+ in order to use the volume control on TP2. There is no volume control on the headset.
Thanks.
Anyone can confirm that the supposedly present PBAP protocol is working ?
Altough my X2 is working generally better than expected, the my Alpine Car stereo is not able to show the phone's contacts.
That Car stereo was able to show the contacts with almost any phone I tried in the last couple of years.
Notably the samsung i780, the Xperia X1, the imate 8502 (which is a Mobinnova product), all the sonyericsson featurephones (k800, w995, G705, etc...).
So, is that protocol truly present (as stated on the bt cpl), and there is some compatibility issue, or is simply missing ?
Can you share your experience ?
I have no problems with the RBAP protocol on my Parrot MKi9000.
Maybe there's a problem with you Stereo.
Cheers.
Jolo_ said:
I have no problems with the RBAP protocol on my Parrot MKi9000.
Maybe there's a problem with you Stereo.
Cheers.
Click to expand...
Click to collapse
Thanks for the info.
Maybe wm 6.5.x has changed something on the protocol so the radio won't recognize it.
I'll try to flash the radio with the latest firmware to see if the problem is solved.
I haven't upgraded the FW, since it worked W/O a single problem, with any device I tried (excluding the N900 that was released w/o PBAP support).
Ok, updated the car stereo's firmware (not so easy task) to the latest revision, the caller ID is still unsent, and the phonebook unavailable from the radio's display.
The compatibility list of this FW is huge
http://italy.alpine-europe.com/file...ion3.60/CC_CDE_103BT_CDE_113BT_ver3_60_IT.pdf
So I'm still convinced that something is wrong on the X2 itself or on the windows version installed.
I have the same problem, my car can access the phone book on other phones, but not on the X2.
Anyone know what to do?
svert said:
I have the same problem, my car can access the phone book on other phones, but not on the X2.
Anyone know what to do?
Click to expand...
Click to collapse
I have the X2 and a JVC KD-NX5000 car stereo (outboard/integrated BT attachment). The X1 worked fairly flawlessly over BT (with gtrab's custom firmware).
Although I have not figured-out how to get MS Voice Cmd on the X2 to initiate calls from the JVC, the following software cured the Phonebook problem:
http://www.jetwaremobile.com/
They offer a free 30-day demo, and it's only $15 for the registered version. There's a command on the menu where (once you are paired with your BT radio), you 'force-feed' the contacts over to the radio. Worked like a charm for me. And, it's actually a bit preferable to the 'phone handles it' method. On the X1, it took the phonebook on its own, but it would update only under unknown/unexpected circumstances. With JetMobile, I believe you can re-send/overlay the contacts whenever you'd like.
(Note: This is using X2 and the May MR2 firmware release with the Saturn theme.)