Database Users

What's the problem with Hero based ROM's and BlueTooth?

Hello.
Before you tell me... I already searched the forum and I can see many posts about the problems with BlueTooth in the Hero based ROM's, but none of these posts I read (I could have missed some, of course) say what the problems are exactly, so I don't know if it can be a problem for me or not.
The only things that I need from BT are connection to the Parrot CK3000 handsfree on my car, and to send/receive files over BT. Ocassionally I will use the Magic as a 3G modem, but I can do it through USB if not working through BT.
Are these BT features affected by these BT problems on Hero based ROM's?
Thanks in advance.

Not sure if this applies to all hero roms but in the 'jacxheroskiv' rom the problem is a missing shared object (just a missing file in the filesystem)
http://forum.xda-developers.com/showpost.php?p=4479554&postcount=96

Hi There
At the moment Bluetooth is problematic on all hero roms for the sapphire or otherwise. Audio head sets (wireless headphones) seem to work ok but everything else doesn't. So unfortunately your car kit won't work. (I have the same one, it pairs but the audio is garbled) File sharing on the other hand is a problem for all the androids so far (There is an app on the market that provides the functionality but it's not as elegant as it could be) so don't expect that to work on hero roms. I haven't tried Bluetooth tethering because WiFi tether works so well. Perhaps someone else could comment.
Now for the difficult part...
So far as I can tell a willing developer, correct me if I'm wrong, could make the Bluetooth work if the source code for the hero was made available (should be available in a few months if the recent release of the sapphires source code is anything to go by) There seem to be quite a number of people who need this functionality so I'm sure one of the rom cookers will get to it but unfortunately there is no way to know exactly when. For this reason I've decided to stick to the ion roms for now. In any event, Touchflo/Sense UI will be made officially available for the magics in due course...for a price of course
On another note any support financial or otherwise is greatly appreciated by the developers so if you want to encourage a particular functionality a few bucks and a friendly message will go a long way. Please remember though that the developers do this kind of thing for the love of it and provide no explicit support for their roms. Any and all risk is taken upon yourself but in most cases caveats will have been picked up by someone before hand.
Sorry if I've mentioned some things you already knew but I thought to add some info applicable to other newcomers.
Enjoy hacking!!

Thanks both.
I guess I'll have to use a non-Hero ROM then. As for the BT file transfer, I've seen at least one Cupcake ROM with it enabled and available as an option in the BT menu. I don't know what ROM it was though, I think I saw it in a Youtube video.
P.S.: I noticed that this thread was moved to "Sapphire general", sorry for put it in "development", I did it for it was related to Hero ROM's. Thanks mods for move it.

A2DP works for my Sony Ericsson HBH-DS205 - music streams flawlessly.
However, the call feature does not work - is this another common bluetooth problem with the HEROs?

[Android] Bluetooth support

The purpose of this thread is to track bluetooth support, document problems, fixes, workarounds, etc.
I'd like to get a poll going in this thread. Please post:
1. what bt headset you're using
2. what build you're running
3. short review of sound quality / bt performance
Thanks!
Support
Currently, bluetooth works in 1.5 (Cupcake), 1.6 (Donut), and 2.1 (Eclair). By 'works', that means can be enabled in the wireless settings and see devices. Everything after that is just software, right?
I haven't checked donut hero or eclair hero.
IIRC it does not work in Tattoo... yet. Let's get cracking.
Profiles
Currently only the headset profile is working.

BT worked in Cupcake since early on, so we'll start with...
Donut
All that had to be fixed in donut was a missing service in the init.rc. After that was added, things worked just as they had in cupcake.

Eclair
There were three problems in Eclair -
first (same as donut) the hciattach service was missing from init.rc.
Second, starting with Android 2.0, they switched versions of bluez from 3.3 to 4.x. This meant that what had formerly been called 'hcid' was now called 'bluetoothd' and there was a directory and config file missing from our basefiles. Fortunately, the old 3.3 bluez config worked fine once it was copied into that new directory.
Third, the hciattach binary was looking for a firmware file that didn't exist in the file system. But we got lucky and were able to sub in the older hciattach from previous versions without issue (so far!)

RESERVED for version 2.++

PAN
I've done some research and cobbled together some stuff on a bt pan. It's possible to do in cupcake. I believe donut and eclair are missing the pand binary.
Personally, I was hoping to use a PAN to get internet on my vogue since I'm a cheapo with no data plan. There's a hurdle here because Android runs a connectivity check before it lets you access most internet services. For example, you can start youtube over a pan connection and it will show the first page with thumbnails, but if you try to load a video it will tell you that you're not connected. So we need to figure out where to get the pan added as a 'real' connection.

1. what bt headset you're using: Samsung WEP 410
2. what build you're running: Eclair 2.1 by mssmison, with latest BT update; SD card ext2 norootfs
3. short review of sound quality / bt performance: could not detect my headset in discovery mode, could not pair
1. what bt headset you're using: Samsung WEP 410
2. what build you're running: Donut Heroblend theme by plemen, NAND norootfs
3. short review of sound quality / bt performance: paired flawlessly, both ingoing and outgoing audio working with calls. able to answer calls by pressing headset.
additional: using Plemen's donut from nand, also able to pair with my Macbook. Using Bluetooth file transfer from my vogue, I am able to surf my public macbook folders from my phone. when looking from the mac, though, no services are available on the phone.

Motorola H300
http://www.amazon.com/Motorola-Bluetooth-Headset-2d-H300/dp/B000VMTDOG
This is the earpiece I'm using, and I'm using Plemen's "[Android] Donut AOSP Eclair - Updated 02/01 - No rootfs boot" v252
http://forum.xda-developers.com/showthread.php?t=591104
So far, it's working great. Callers say I sound fine, and I can hear them. Has chugged along through several 1-2 hour conversations. Answering calls using the button on the earpiece works, and incoming and outgoing calls seem to work fine.

Would Blutooth folder from a droid from verizon with eclair 2.01 be of any help to look at???

Typically the people who know what to do with those get them as soon as they're available. I'm not one of them, though - thanks for the offer.

Looking for a start to research more into Bluetooth and A2DP drivers, I have some linux experience and would like to help the community with testing or helping to create stereo bluetooth drivers.
Basically all that is holding me back from using as a daily OS on my vogue. Can anyone point me in the right direction?
Oh I am running 1.6 with motorola s9's, phone will pair and shift music to headphones in stereo, however is extremely laggy and plays a second of music then a second of silence to "catch up".

daganb said:
Looking for a start to research more into Bluetooth and A2DP drivers, I have some linux experience and would like to help the community with testing or helping to create stereo bluetooth drivers.
Basically all that is holding me back from using as a daily OS on my vogue. Can anyone point me in the right direction?
Oh I am running 1.6 with motorola s9's, phone will pair and shift music to headphones in stereo, however is extremely laggy and plays a second of music then a second of silence to "catch up".
Click to expand...
Click to collapse
Go search the kernel thread for 'bluetooth'. IIRC, the big hurdle to A2DP is that only the low-speed serial driver works. That means we're currently capped at 115200 bps. dzo (the kernel god) has made some attempt at backporting the driver from the 2.6.27 kernel but eventually left off in favor of other things. Last I remember he was using haret to dump some info out of Windows Mobile. Like I said, it's all in that thread.

Bluetooth A2DP issues w/ 2.1

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.

Bluetooth Stereo Sound Quality Not 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.

[Q] bluetooth headset profile HSP

I just purchased an A501, rooted it and am running the Alexander III rom, (very nice job on the rom!!!)
I was hoping I would get the bluetooth Headset HSP profile in the new rom but sadly it was not there.
A little research has shown that there is a Bluez driver plugin installed and various bluetooth libraries, my question is can I potentially just replace these libraries with bluez libraries from another rom that has the HSP profile?
I really need to get the bluetooth headset profile working on this A501, and am willing to pay a bounty for help in getting it working

Sorry to say, it doesn't work... as with most other Tablets.
Just using some libs from another ROM isn't going to work either, unless they are extremely similar... and all ROMs similar enough to try such a stunt are almost definitely broken as well.
Sorry, but you'll have to roll your own BT stack if you're desperate enough to try... I'm not gonna.

haag498 said:
Sorry to say, it doesn't work... as with most other Tablets.
Just using some libs from another ROM isn't going to work either, unless they are extremely similar... and all ROMs similar enough to try such a stunt are almost definitely broken as well.
Sorry, but you'll have to roll your own BT stack if you're desperate enough to try... I'm not gonna.
Click to expand...
Click to collapse
Still doing a little research on this. I discovered, in the Bluetooth folder, a couple of files pertaining to what Acer has deemed "black listed", which simply means, certain brands and models are not allowed to work with bluetooth. System/etc/bluetooth/
Also noted, if you modify the files, you need to make changes in a couple of other module files (android_bluetooth_ScoSocket.cpp). The info in the above files tell you where to look.
Not sure why Acer black listed those devices. Legal reasons maybe? Plain incompatibility? Who knows.
My dev skills, are not quite up to modifying .cpp files. Probably enough to muck things up really good Not to mention, I would have no way to test them. But when I get a chance, I'll see what's in them.
Of course most of this pertains to Auto pairing, so might not be of much use. As with the .so files in the Bluez folder, you'll need to de-compile them first to see what's in there.

Also, I saw some bluetooth apps onn the market that some folks had some success with getting HSP. Not the off/on widgets but an app itself. Might want to give them a try and see if you can get the headsets to connect.
Additionally, it seems bluetooth headset problems seems to be across all devices, and not just the a501, but Zoom, Transformer and Thrive as well. Hit and miss with what works. Most issues say the mic doesn't work.

I tried a couple of the apps with no joy on my plantronics earpiece but one of the widgets actually connects...for just 2 seconds...then disconnects...I think the capability is there and you are correct there is some file manipulation that needs to occur...
I have a friend in Egypt that is very good with android bluetooth, he is working on another project right now but when he finishes his current project I will send him these files...he might be able to figure it out ...