Ok so this is not the only phone that I can see that is wireless everything but does not support A2DP so you can listen to the mp3 player wirelessly??? I have seen that some have updated other units (MDAIII) to use a BT stack from broadcom and I was wondering if it is possible to do it on the sp5? I am guessing that using the broadcom stack does not require BT 1.2 but I am not sure what stack the sp5 is using and where I would get the updates. I am also reading that most that have done an update have mention static if they move around?? Why then would you need BT if you cannot move?? Is this then the V1.1 causing the problem and why it should be on 1.2?? :?
more info
Ok so I have asked the question about the sp5 & sp5m about A2DP so you can use stereo bluetooth headphones that include player controls and I found some answers.
A2DP only fully works on Bluetooth V1.2 and these units only V1.1. I have seen that some people have installed some third party BT stacks on there BT V1.1 units to get high quality stereo profiles but they do not have player control. Also it may not even be A2DP it may just be a facsimile but more interesting it may be A2DP. When looking at the specs of phones it says Bluetooth V1.1 but does not say which silicon (Chip) is in the unit which is very important because the chips are backwards compatible. Meaning it may be V1.1 but the chip maybe able to run V1.2 because the manufacture just put in V1.1 stack and rom. So we should all be not asking about new stacks and upgrades but first ask which chip is in the units and if it is a V1.2 compatible, then we should start demanding rom and stack upgrades now. As for the chips the V1.2 and more chips have been out for at least 2 years so the manufactures cannot say the release of them postdated their own development date unless they have been hand building the units for the last year and that gave them one year to test.
Well can someone please tell me which or who’s BT chip is in the sp5 and sp5m
Related
Seems to be a lot of problems/issues spread across the forums concerning bluetooth and XDA2/XDA2i in general. :?
Would a specific Bluetooth Forum be an idea, to try and zero in on some of these issues? :idea:
Now that there are an increasing number of BT devices/uses - GPS, headsets, headphones, cameras, laptops, fridges, car setups etc.. it would be good to be able to share info on those uses that actually work well .... and those that don't.
As a starter .....
What is considered the best and most stable BT setup for XDA2 and XDA2i? Does this vary depending on what you are using it for - handsfree, TomTom, or built-in carphone ?
For my own setup, I am using an XDA2i (Bluetooth v1.0.0-3900 by Broadcom) - this works about 75% of the time with my JabraBT250v.
I also have bluetooth factory-fitted by Audi in my car - but as yet it is intermittent when connecting to the XDA2i and will not recognise the SIM addressbook like it is supposed to do.
The car makes the bluetooth link OK, and I can make calls (even using Audi's Voicedial 8) ) but it then drops out/reconnects every four minutes :evil: Very annoying, but suppose it keeps the call costs down :roll: Is this likely to be the car dropping the phone or the phone dropping the car? Any fixes or hints ?
I have a spare XDA2 that I will happily use as a testbed to try and get different Bluetooth versions working - just be patient with me as I'm a novice !
as far as i know then which bluetooth version is supported is in the Hardware and can never be altered
but what you can do is to change bluetooth stack from MS to vidcomm / broadcom
it solves some issues but creates others try doing a search for vidcomm OR broadcom
Hi all,
Sorry for my poor english...
Has anyone had any experience using a HP BT Headphones (FA303A) with non-IPAQ devices?
I looking info if it is compatible with my ACER N311 but not able to find any info about compatibility between the two. Would installing appropriate drivers work?
RE-HP BT Headphones (FA303A) and non-IPAQ devices
Hi...just wanted to drop a line as to what I have found out on this subject.
Your question can only be answered if you know a little more about your device..
1) Which bluetooth stack are you using (Broadcom/Widcom or Microsoft)
2) Does you device support the A2DP function already (should be listed in your bluetooth options)
2a ) If it is not listed in your bluetooth functions, you will need a driver for the Microsoft stack (it is supplied with the headphones)
OR
2b) you will need to find, download and install the Broadcom/widcom bluetooth patch..
In either case (2a or 2b) if you have researched the issue and installed the driver or patch... the High Audio definition should show as a new function in your bluetooth.
If it does you can then "pair" the headphones with your device and test the functionality...
If someone could post the driver for the IPAQ Bluetooth Stereo Headphones, I would be more than happy to test this all and give everyone the results....
Last note: It cold also be that you device can then (if the patch or driver work correctly) pair your device with any other device (i.e. car radio etc. that also supports the A2DP function. This is what I am looking into now but HP is not posting the driver for the headphones so I cannot download or test.. They only offer an update to the drivers ...and this is only for the PPC 55xx model...
If someone can post the drive let me know !!!
Hope this helps you...
RE2-HP BT Headphones (FA303A) and non-IPAQ devices
I have noticed that your device has the Mobile 5 software.
I have read that microsoft and HP are working on a bluetooth upgrade for the A2DP profile... as such, you may want to consult support for your device and ask the question "will there be an update to support A2DP function"?
Till now this upgrade is being discussed on only selected models (not all devices), but from what I gather the devices in question are only the devices with Mobile 5 on them ...
Hope this helps as well
RE-3
Take a look at this link..
http://www.theunwired.net/?itemid=2762#article
:shock:
LnrMra said:
Hi all,
Sorry for my poor english...
Has anyone had any experience using a HP BT Headphones (FA303A) with non-IPAQ devices?
I looking info if it is compatible with my ACER N311 but not able to find any info about compatibility between the two. Would installing appropriate drivers work?
Click to expand...
Click to collapse
if your unit support a2dp: yes
Broadcom: High Quality Audio
MS: Wireless Stereo
the passcode for pairing is 0000
however, it's highly recommended to put reinforcement on the headband to prevent notorious breaking
After much searching and Googling, I'm a bit stumped.
I'm currently running VP3G's 2.0.1h variant of the WM6 ROMs, and A2DP works beautifully. So does CoPilot / MSN Live Search / Google Earth with Bluetooth GPS. But together? Skip goes the audio.
Some playing with the BitPool setting got me more or less audio before the skips. The BlueTooth GPS is the one that comes with the CoPilot bundle, SirfSTAR III, running at 4800 baud. Fairly standard fare. The A2DP headset is the Sony Ericsson HBH-DS970 headphones. Ideally, I'd like to be able to use it for satnav - you've guessed it - via the bluetooth headphones.
I haven't tried installing the Widcomm stack yet, although that's next on my list. It'd just be nice to do it "natively" with the WM6 bluetooth drivers if possible.
Thanks in advance!
The Hermes has a hard enough time just with A2DP, co-existing with a BT GPS receiver will be really pushing the device's capabilities. You can try installing Sleuth255's A2DPFix v1.0 which does a really good job of fixing A2DP issues in general, but I suspect that you may be asking too much from our poor little devices...
John
Well, installing the Widcomm stack solved it hands down - whilst it seemed to use a little more CPU, it worked fine with the bluetooth GPS and the bluetooth audio, with the satnav application broadcasting audio via the headset.
I'll try the A2DP fix, and see if it does any good with the MS stack. Still, at least I've got a way around the problem now!
N2A said:
Well, installing the Widcomm stack solved it hands down - whilst it seemed to use a little more CPU, it worked fine with the bluetooth GPS and the bluetooth audio, with the satnav application broadcasting audio via the headset.
Click to expand...
Click to collapse
Interesting! I have always considered the Widcomm stack to be miles better than the M$ one (even though M$ has made quite some improvement recently), but just never had enough time to really play around with it to get it working on my TyTN. There was an effort started late last year to raise $500 for the first person to release a working version of the stack, but unfortunately it fizzled.
This might be enough to get me to try again. I am going on vacation for two weeks starting Sunday, this would be a good project for a rainy day -- I am going camping, it always rains when you're camping!!
John
Oh, absolutely, it wouldn't be a camping trip if it wasn't pouring down
After playing around with it some more (using the 0.3 version from the thread), it seems a bit flakey, sometimes failing to update properly, but I think that's more down to CoPilot than the stack - MSN Live Search and Google Maps seemed to work just fine when I was listening to my music. Nothing fancy on the music score either, just plain old Windows Media Player. A lower CPU usage program might help the satnav program - I'll try some alternatives shortly.
The A2DP fix made no difference at all, although I suspect that's mainly for the awful MS implementation on WM5. I haven't really noticed all that much difference in sound quality between the two stacks, although some people rave about the Widcomm, but maybe I'm just not as attuned as some people
There's no doubt that the Widcomm stack is better than the MS one, although it's not without it's apparent issues of course. I tend to use the MS one for general usage and the Widcomm if I need to do more than one bluetooth thing at once. Seems to work for now, although I need to put it in more heavy testing.
Both stacks give the odd skip, but I tend to think that may well be down to how much CPU usage I'm pushing out of the poor little thing
The problem with the Widcomm stack being ported properly was that it wasn't really organised all that well. If someone steps up to the podium, I'm pretty certain people will pay for the functionality. It's just finding someone with the skills and time to do it!
Give it a try, although beware of the potential caveats - reading up on the thread is recommended.
I have Verizon's Touch Pro 2 and it appears to have the Widcomm bluetooth stack. I have had a really terrible time using the phone with my bluetooth enabled car stereo (6.1 and 6.5 stock ROMs). From a ton of reading, I think it may be related to the Widcomm bluetooth stack. My questions are:
1. How can I verify which bluetooth stack I actually have?
2. Is it possible to replace it with Microsoft's?
3. If so, where can I get it from?
I'm sure this information is out there somewhere, but it's just so scattered, I can't really find any solid answers. Thanks.
There is not a way to replace the stack yet and none of the others are compatible with the hardware in these devices. Rhodium devices run Widcomm stacks, which are not that good (even on PC...). The new (leaked) T-Mobile rom leak is supposed to have fixes for some of the problems we currently have with this stack. Hopefully, that's true.
I don't know if this is the correct board, but here it goes..
I just bought Nokia BH-111 (http://nokia.ly/ACiqj6) bluetooth stereo headset and I can't pair it with my Omnia 7. Works fine with Nokia 5230 phone, so it's not a problem with the headset. The phone does not even detect the headset, it keeps showing "searching" and nothing happens.
This is what nokia product page says about compatibility:
"All phones, music players and other devices that support Bluetooth v. 2.1 + EDR, Handsfree Profile 1.5 and Headset Profile 1.0"
This microsoft support article ( http://support.microsoft.com/kb/2449475 ) has this to say abozt supported profiles:
Advanced Audio Distribution Profile (A2DP 1.2)
Audio/Video Remote Control Profile (AVRCP 1.3)
Hands Free Profile (HFP 1.5)
Headset Profile (HSP 1.1)
Phone Book Access Profile (PBAP 1.1)
+ v2.1 with EDR
So as you can see, WP supports EVERY one of those profiles and standards. What's the problem than?
Does your Omnia find other devices?
Omnias are notoriously bad for having faulty Bluetooth. My first one stopped working properly. Replacement is fine.
In the Omnia 7 section there are quite a few people who've reported it.
Thanks for the reply.
It seems that the issue is with WIFI and Bluetooth working together. After i turned wifi off, Omnia was able to find the headset. The playback is a little patchy, and rewind/fast forward does not work. Is this a reason enough to ask for a replacement? Does the warranty cover it?
EDIT: sorry i posted here, i thought it was WP software related, plus Omnia boards are almost empty.