Hi there,
We're developing a hardware project at University that captures audio and send it out through BT A2DP profile to be analysed. It already works fine with wireless headsets and our next step is connecting it to an Android device.
The AOSP is currently implementing the "sink role" of A2DP profile in Bluedroid stack, but as far as I know it is still on lab. However, it seems that the discontinued BlueZ BT stack partially implements this role in Lollipop versions.
Hence, my question is: do you know any 5.x ROM for Nexus 4 that swaps BT stack to be BlueZ? We haven't either enough time nor knowledge to build our own custom ROM.
Any further help would be really appreciated :highfive:
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...
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.
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?
I figured I should come to you guys after accidentially trashing my bluetooth whilst trying to fix my A2DP no output problem in an unofficial WM6 ROM build.
I just need to do a little research here. Are problems with stereo headset compatibility common, even in the latest builds of WM6 ROMs? Is there a registry setting I should be aware of, or a port number I can check?
Or, heck, a way to check if the drivers are actually running?
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.