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?
Related
When I use the A2DP in wm5/6 I tray all versions BT stack~but no one could work,so I chose 2003se,IT's best for BT A2DP.
Why Helmi Do not fix that?Dose this really hard?
Yes, it's that hard to fix that. The only way we could get wm5/wm6 working flawless on BA is if we had the source code for the drivers and the testing/debug equipment.
If you know someone that works at HTC you could ask them to look for the BA devkit and sourcecodes on the storage rom... hehehe
Mine didn't skip with WM5 and did not skip when I first flashed WM6. Now it does. When I was messing around trying to connect to bluetooth devices (I couldn't connect properly), it stopped skipping for a while. I don't know if this gives any clues.
rambo6 said:
Mine didn't skip with WM5 and did not skip when I first flashed WM6. Now it does. When I was messing around trying to connect to bluetooth devices (I couldn't connect properly), it stopped skipping for a while. I don't know if this gives any clues.
Click to expand...
Click to collapse
I know a way to prevented this bug,but not prefectly.
Use regedit tool,open to find software\widcom\plugin\av
add 3 dwords
Linespeed 320 (10+)
Blocks 16 or 32
Subbands 16
You will see the music quality is prefect
but the skipping frequency is above normal~
When using the asus p535,this way will surly improve the quality~and it no skipping,so I thing it must be the bug from the System~
Use win2003 have no such foolish bug.Now I set my pc back up my pda every time connected it with PC~Store the phone book in simcard~
I have no choice
Toxi,
Thanks. I couldn't add the Dword settings which you suggested because I had no Widcom file. So I loaded Helmi's 1.7 Broadcom BT driver. (Always wanted to try it. The Broadcom BT drivers alway better. Immediately after installing, my BA played music better alone and with my BT headsets. Adding the Hemi 1.7 BT cab, added the Widcom file which allowed me to add the Dword registry changes. The music sounds almost perfect.
I tested the BA with these three BT Stereo Headsets: Motorola S9 headsets; Chinese Copy Motorola BT820; and I-Phono RX450. The Motorola S9 works (It didn't at all with the MS WM6 BT Drivers). The S9 would only work if it's 12 to 18" from the BA. That's unacceptable. The BT820 chinese knockoffs skipped as usual (the skip some with every device cause they're knockoffs). The I-Phono worked perfectly with crisp clear sound and no skipping. I can also get further away from the BA but certainly not more than 3 feet without trouble.
In conclusion: Helmis Broadcom 1.7 cab worked to fix the sound problems completely with and without using the headsets. The newer headsets such as the S9 don't work all that well with the BA.
I hope this is helpful for others not satisfied with the music quality of the BA running WM6.
I wish HTC would make a Blue Angle II.
Has anyone taken a look at the differences between the A2DP drivers in WM6 versus WM5??
I'm thinking about rolling my device back to WM5 because it responded faster on my device (Titan), but the only feature that I really need WM6 for is the A2DP quality.
Some of you may recall that WM5 had awful hissing noises and distortion using certain A2DP headsets (while others were fine). The final release of WM6 dramatically enhanced the sound quality, and now you can't even tell its wireless.
So, I've poked around a bit, but I can't seem to figure out what exactly needs to be changed to bring whatever was fixed in WM6 into WM5.
does anyone have any suggestions or helpful insight?
I think someone here has actually extracted the A2DP files from WM6, but it was back when the beta was leaked. The beta version didn't have the fixed A2DP. Although, its possible that the extracted files weren't able to fix the problem in the first place...
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.
So, I have searched all over these forums, and cannot find a difinitive answer or solution. I have problems with A2DP when connecting w/ the BT in my car, since installing a 2.1 ROM (currently DC 2.09.01). When connected, the music plays about twice as fast as it should, then slows down, then speeds up again. Conversley, Android 1.5 worked fine. There has been a lot of talk of BT issues, but it doesn't appear there are any solutions. Am I correct, or has someone found a solution? THanks.
ZenEXP works if you dont mind switching.
I have had those problems occasionally with all 2.1 ROMs I have tried. Usually, if I pause and then unpause it solves the problem. Sometimes I have to do it more than once.
I'm currently running ZenEXP and I've had the problem a few times, but it has been significantly less than with other ROMs. However, AVRCP hasn't been working with ZenEXP, whereas it has worked on other 2.1 ROMs, such as DC.
So, with the unrooted stock Sprint 2.1 software, A2DP works?
The Darchdroid ROM actually fixes this problem! I had the exact same problem as you with playing audio in my 2010 Mazda 3 and Darchstar's ROM fixed it for me, it's the only ROM I have found so far that fixes the bluetooth
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
Click to expand...
Click to collapse
Turn off/disconnect headset while playing music fixes studdering for me in settings under bluetooth for the connected device. Disconnect the ' phone' while playing. Haven't really tested this on anything but my kenwood head unit.
-------------------------------------
Sent via the XDA Tapatalk App
here's a reply I received from HTC support:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Bluetooth Stack?
So is it possible for one of the developers on this site to rewrite the bluetooth stack or copy the old one from 1.5 that worked?
I have a Panasonic TH12 bluetooth home phone that worked fine before 2.1. I recently bought an AT&T bluetooth phone and it does the same thing. Will pair but not connect.
aschlect said:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Click to expand...
Click to collapse
I have to call BS on this. (Not on the post, on the reply)
Why would any company not support legacy hardware as simple as Bluetooth. Especially since most devices aren't even Bluetooth v3/v4 standard yet. And Bluetooth 2.1 is 1. Not very old and 2. What 90% of Bluetooth device still manufactured are! and its been around since 2006!
I honestly can't believe a company is going to just say "Oh its to old" instead of fixing their crap. as far as I know v3/v4 is fully backwards compatible to 2.1 because they include "Classic Bluetooth" protocols!
Not to mention I doubt the hardware in our phone is even capable of v4 stuff. I'll have to do some more research on what BT chip is in the phone. Utter BS.
Either Phillip or HTC is a moron.
CDMA Hero Specs for BT:
Supported Profiles: HSP 1.1, HFP 1.5, A2DP, AVRC, (OPP, PBA)
version 2.0+EDR / possibly upgradeable to 2.1+EDR, plus OPP and PBA profiles
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Kcarpenter said:
<snip>
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Click to expand...
Click to collapse
Yeah, I just bought a BT USB adapter so I could exchange files and synch and stuff. I got it to work ONE time and all it did was pass 200 of my contacts to my phone from my PC. Like it was just waiting to upchuck on me. After that, nothing.
There's three hours of my life and $8.99 I'll never get back.
Bluetooth is pretty much the #1 complaint that users have been posting on the Sprint Community Forums (here's the HTC Hero section). Nearly all of those complaints say that Bluetooth now doesn't work at all or just plain sucks on the stock 2.1 Sprint/HTC release. Which probably also means that any ROM here based on 2.1 stock will also suck it up bad with Bluetooth compatibility. Known problem, no one has done anything about it yet. It sounds like AOSP ROMs don't have this issue, so at least that's good.
All,
Does anybody have any fixes regarding the sound quality when using Bluetooth A2DP protocol? I use my Evo to mate with a Bluetooth receiver so I can listen to Rhapsody over my home stereo. The sound quality is flat. The high frequencies are not present. It sounds like a bad quality MP3. I know that its the A2DP causing the quality issue as directly connection (through 3.5 jack) is awsome.
The Apple 3GS A2DP sound quality was awsome. I am not sure why the Evo is not sounding good. Any help would be most appreciated.
Thanks,
Lance
use the cyanogen rom--this uses a bitpool of 53 giving you the best bluetooth quality possible. the stock/sprint/htc bluetooth drivers are set for a bitpool of 32
Is there any other ROM that has the bit pool set to 53?
Lance
Nope all Sense roms use HTC's ****ty low bitpool setting. This is why I'm running CM as well it's the only rom I can A2DP to my Sony Head unit and get good audio. I attempted to contact HTC about this issue here's the juicy details
Here's my initial question
I have terrible static when streaming music over A2DP on my HTC EVO to my sony mex-bt2800 car radio. If I use CyanogenMod 6.0 which uses a open source bluetooth stack my A2DP is crystal clear to my radio. I have used logcat to look at whats going on I dont know if its a bitrate problem or a bitpool problem or if my radio isn't in your acoustic database.
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
Here's the response I received
Although the android software has been updated to be more compatible with Bluetooth headsets and car kits. Most of the time a Bluetooth manufacturer will have a list on there website stating devices they have found compatible, but this is not always the case. From the information on your issue it seems that your device is simply not fully compatible. The only thing we would be able to recommend would be to try another headset.
Then my response back
I would like an Engineer to read my question if possible since I don't think you fully grasp what I'm saying here. First My EVO's Bluetooth A2DP WORKS 100% clearly when using a Open Source ROM which implements Bluez Bluetooth stack http://www.bluez.org/
When I run your Sense UI ROM the Stock ROM you release which uses your own proprietary Bluetooth Stack I get static in the background so you cant really say its my phone now can you? Its your implementation that's not working properly. I'm not about to try every car stereo till I find one that works with the EVO when I know my stereo can work perfectly with my phone when using a properly coded open source Bluetooth stack.
Here is some extra info from a logcat that shows how your Bluetooth makes a connection through A2DP and what I believe is too low of a bitrate or bitpool setting
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
PLEASE DON'T GIVE ME A ANSWER THAT YOU JUST READ FROM A SCRIPT. I would like a true response from someone who understands and can grasp my question fully like an engineer or a developer, when you give me a generic response of oh your Bluetooth headset isn't compatible keep buying new ones till you find one that works, that really makes me upset since you didn't even read my question it's a car stereo and there not cheap.
I await your educated answer.
And there final bull**** reply
We apologies for any inconvenience you may be experiencing. We will document your concern for review in development of our upcoming devices and future software updates. The situation is still an incompatibility with our device and your car kit weather on software or a hardware level. Unfortunately at this we have no further information beyond what has already been provided.
P_Dub_S said:
Nope all Sense roms use HTC's ****ty low bitpool setting. This is why I'm running CM as well it's the only rom I can A2DP to my Sony Head unit and get good audio. I attempted to contact HTC about this issue here's the juicy details
Here's my initial question
I have terrible static when streaming music over A2DP on my HTC EVO to my sony mex-bt2800 car radio. If I use CyanogenMod 6.0 which uses a open source bluetooth stack my A2DP is crystal clear to my radio. I have used logcat to look at whats going on I dont know if its a bitrate problem or a bitpool problem or if my radio isn't in your acoustic database.
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
Here's the response I received
Although the android software has been updated to be more compatible with Bluetooth headsets and car kits. Most of the time a Bluetooth manufacturer will have a list on there website stating devices they have found compatible, but this is not always the case. From the information on your issue it seems that your device is simply not fully compatible. The only thing we would be able to recommend would be to try another headset.
Then my response back
I would like an Engineer to read my question if possible since I don't think you fully grasp what I'm saying here. First My EVO's Bluetooth A2DP WORKS 100% clearly when using a Open Source ROM which implements Bluez Bluetooth stack http://www.bluez.org/
When I run your Sense UI ROM the Stock ROM you release which uses your own proprietary Bluetooth Stack I get static in the background so you cant really say its my phone now can you? Its your implementation that's not working properly. I'm not about to try every car stereo till I find one that works with the EVO when I know my stereo can work perfectly with my phone when using a properly coded open source Bluetooth stack.
Here is some extra info from a logcat that shows how your Bluetooth makes a connection through A2DP and what I believe is too low of a bitrate or bitpool setting
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
PLEASE DON'T GIVE ME A ANSWER THAT YOU JUST READ FROM A SCRIPT. I would like a true response from someone who understands and can grasp my question fully like an engineer or a developer, when you give me a generic response of oh your Bluetooth headset isn't compatible keep buying new ones till you find one that works, that really makes me upset since you didn't even read my question it's a car stereo and there not cheap.
I await your educated answer.
And there final bull**** reply
We apologies for any inconvenience you may be experiencing. We will document your concern for review in development of our upcoming devices and future software updates. The situation is still an incompatibility with our device and your car kit weather on software or a hardware level. Unfortunately at this we have no further information beyond what has already been provided.
Click to expand...
Click to collapse
Well I commend you for trying. This is something that makes me want to tear my hair out so I would love to see this resolved as well.
good on ya mate.
anyone know how to get another bluetooth stack on stock rooted 2.2?
I asked Flipz a while ago but I don't think he's looking into it. I also asked Netarchy he said he would look into it sometime but that i shouldn't hold my breath since he hadn't even looked at the code yet. HTC has released the source for their Bluez implementation so all we need is a dev willing to look into adjusting the bitpool setting.
This is a HUGE problem. I am flashing CM6 right now. HTC I am very disappointed with you..
The cyanogen rom also has great dsp equalizer
CyanogenMod will also make you a tropical island than transform your EVO into a jet plane and take you there ;-)
But in all seriousness, yeah, CM6 has BT fixed. One of my friends nagged Cyanogen about it last month, and he patched it right away.
I wish somebody could help us by increasing the bitpool on the Bluetooth driver. The Evo would be so much more enjoyable (for me at least) if the sound quality was better thru A2DP.
lancer123 said:
Is there any other ROM that has the bit pool set to 53?
Lance
Click to expand...
Click to collapse
It would be nice if there can be a patch of some sort...
Just an update today I got a call from HTC customer service since i gave a poor review of my experience on a survey they sent me. Talked in great detail about our problem with the Bluetooth stack told him about the bitpool setting how its 53 on CM and 35 on there roms. So hopefully on the next update well get a fix for the Stock Sense UI rom.
^^LMAO!!! dont blv the hype
I read that the CM6 ROM has this issue fixed. I have also read reports that the ROM email client doesn't support word wrapping (which I really do need). Can anybody confirm this?
Also,
Can anybody in ROM land please create a patch or an update to their ROM which increases the Bitpool to 53? I understand that the Bluetooth driver code has been released.
Thanks
bump............
any roms address this yet?
greenail said:
any roms address this yet?
Click to expand...
Click to collapse
maybe:
* Added DSP Manager (Digital Signal Processing) to boost audio and equalize sound for Headset, Phone Speaker and Bluetooth devices.
wont let me post links, but you know what to do:
forum.xda-developers.com/showthread.php?t=793471
I am using the latest OTA, rooted, along with the latest pandora and the bt audio quality is much better. I have the motorola t605.
With the initial 2.2 update bt quality sucked but now it's better.
Sent from my PC36100 using XDA App
mchlwvr614 said:
I am using the latest OTA, rooted, along with the latest pandora and the bt audio quality is much better. I have the motorola t605.
With the initial 2.2 update bt quality sucked but now it's better.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That was a streaming issue, not a bitpool issue.
The BT audio was a lot better on my TP2 when I updated the registry bitpool to 48 from 32.
I wish they would fix it.