I posted this is another forum, but I feel like its more appropriate here.
It was brought to my attention that some of the new WM6 cooked roms seem to have some updated a2dp drivers that finally fix the quality issue that causes static and hissing with certain headsets (in my case, an i.tech R35).
Many who had switched to the Widcomm stack for better quality now say that they no longer need it. However, I can't seem to figure out how this was fixed...
I'd like to try and apply it to other devices that don't have these cooked roms available, but suffer from poor A2DP sound quality, such as the Tornado.
I'm wondering, does anyone here know anything about this? I'm trying to figure out if there are new a2dp drivers, or maybe someone developed their own fixed codec and applied it? Or perhaps someone has just found the perfect balance of registry settings?
If you know anything about this, please share! Any help would be appreciated, 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?
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...
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.
So when connecting to my main car I get no phone but media does play. Other cars it's 50/50 if I get whole phone or just media.
While researching I found that oplus3t had this issues with certain ROMs and sometime made a flashable zip that changed the bt stack. Was wondering if that existed for the axon7. I know it worked with my car with stock, hate stock though.
I don't know about a different Bluetooth stack, but I've tried every ROM on this forum. The only one that has fully functional BT for me is NucleaROM.