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.
Related
Hi Guys: I have got the Widcomm Phone edition stack working on my unit.
It seems to be fine but I have not fully tested all aspects of the software - so if any little bits don't work, let me know...
You need to install the official widcomm 1-4-1-59 version
Then you can upgrade it using the cab file I have made.
The 1.4.1.59 version file I got from the following topic
http://forum.xda-developers.com/viewtopic.php?p=57550#57550
thanks go to mamaich for the file.
the upgrade file consistes of the PE edition files and the required registry entries.
Let me know how you all go on with it - but I am not really a hacker so any serious probs I will not be able to fix...
if anyone else can improve on the installation be my guest
any news about which profiles it support that ms or the old one dont support ?
I hope unintall won't mess up my volume as in case of original bluetoothgps.cab
I can't garauntee it works perfectly, so I suggest everyone make a backup of their system before use.
has anyone tested any BT headset with this new stack?
I've got it installed and it all seems to work well exept for the handsfree/headset profile, I have set up my headset ok it is discovered and bonds fine but when I try to connect from the xda2 the connection fails after "waiting for device" for some time. tried with a motorola hs 810 and a neovoice usb, same with both. Anyone got any ideas?
BT headset
I have a 6315 and an XDA 2, I haven't tried the BT Stack on the XDA 2 yet but I found when I bondeded my HBH-30 to my 6315 once it made the connection my BT Headset shut off for some reson. This caused the bonding to fail, but as soon as I turned my headset back on (while it was trying to discover services) it completed the process and worked on my 6315. I'm not sure if this will be the same, but it's worth a shot.
Brandon
Test results
Hi fellows
Here is little bit of my testing of this new BT Stack, which we all awaiting for..
Proc…
1. Installed as per instructions 1.59 without any problem. During installation was prom to override .dll files – agreed to do that. For good or for bad – will see later.
2. Installed .cab file provided by icarusbop (big thanks to him for doing this) without any problem. Screen shots will be attached below.
3. Reset it as requested upon installation and got Widcomm BT working instead of MS BT..
4. Paired it with my BlueTrek G2 within 3 seconds (which took usually 10 sec with MS BT)
5. BT recognized G2 as device with Headset/Hands-Free profiles and asked to use as default… I said yes…
Here comes Cons part ;(
1. Unfortunately even after paring – my I-Mate can not get connected with G2 (see screen shot)
2. As you can see in another screen shot – there is Hands Free menu – it can not be accessed, or can be accessed ONLY while connection is established.
3. AND the last L … So, this new BT is not working now… I decided to go back to MS BT… SURPISE!!! I am getting message that BT HARDWARE IS NOT INSTALL ON THIS UNIT…. L Assumption - .dll files were overwritten (see Proc 1)
Here is my 2 cents in this jorney… I am hoping that described problems can be fixed and we can make it working (without doing hard reset on my device )
Paul
thanks guys! for testing hands-free/headset profile. by now everything seems to work fine with this new stack except for hands-free/headset profile.
New comments to my testing
1. I tried what NeoCole recommended - didn't work for me
2. As soon as new BT is OFF - MS BT is working fine .....uf
LETS FIX THE HEADSET PART PLEASE
I posted this is another thread - but in case someone does not read that thread . . . it is relevant here as well.
If the intent of this is to get voice dialing without touching the device, that is by only pressing a button on the headset to initiate a voice-dial program to make the call, there is no evidence this works with this BT stack either.
I have been reading other forums with people who have the H6315 already (mine is in the mail to me now) and none of them have been able to make this work. Nor is there any mention of this capability in any of the literature and/or documentation for this device. It seems that if this was a feature of this phone, it would be prominently displayed!
Voice Command
Okay.. on my 6315 I press the headset button, it beeps, sound and voice is now transfered to the headset. I do this before I initate voice command. Now all I do is press a button that activates Voice Command on the PPC and walla, I'm speaking and listening through my BT Headset. This is a huge step forward from using the MS Stack, and I feel that since the Phone Edition of the Widcomm is 1.0.0 I'm sure that they'll associate a hardware button with the headset button in future releases. Anyhow.. I think that the functionality of the Widcomm BT Stack is well worth the work. The XDA 2 would be a lot better device if the BT Stack worked 100% of the time and was fully compatibile.
I also have not got it working.
the Hp 6315 is well know to still require a hardware button press (not on the headset) to activate voice command. They can still not do with any nokia or SE phone can do easily.
Surur
VoiceCommand
That would be correct... One press of the HW Button does it all on a Regular phone.
The 6315 has brought it closer to allow you to interact with programs using your BT Headset, but yes you must still activate the programs on your handset before you can use them with your headset.
So.. to sum it up...
1. You can't interact with Voice Command using MS BT Stack on an XDA 2
2. You can interact with Voice Command using Widcomm Stack on 6315, but you have to activate the headset first, then start VoiceCommand on the PPC by using the HW Button.
Hopefully through this thread we'll be able to give the XDA 2 the same functionality as the 6315.
And maybe if Widcomm provides an update to allow the headset to activate a HW button, we'll be to the one step solution.
I do not want my comments to be read as stating that this is not a worthwile endeavor. I simply meant to make sure that someone does not go to the trouble of installing this new stack (particularly those who might be considered novices) with the mistaken impression that by doing so they will have that "one step" voice dialing solution.
This is by all means a worthwile endeavor, but it is merely a step down the road . . . not the final destination.
Y'all are doing good work - keep on blazing that trail!
hm.. I would think that it is more of MS Voice Dial functionality than BT - to recognize signal sent from headset as request for voice dialing.
When MS released first version of Voice Dialing they did not expect new functionality to have BT headset with hands-free profile connected to the device.
paired with my Jabra 250 = ok
connected to my Jabra 250 = failed
No luck with Moto headset
Eveything else seem to be working. No problems with detecting and working with BT access point
rehman said:
I hope unintall won't mess up my volume as in case of original bluetoothgps.cab
Click to expand...
Click to collapse
Hi Rehman,
i tried to install and uninstall, for the very first time i didn't have to get a Hard-Reset done. the volume didn't disappear. so i believe trying it wont be a harm, but yet i would recommend to get a full Backup first.
Trying to figure this out
Okay, I looked through the whole registry. I can't find anything out of the ordinary. Only thing I can think of is the sound driver. Does anyone know what DLL that is? I bet it's a different version.
If someone that knows more about which DLL does what. Let's get all the DLL's that could pertain to Sound and Phone and compair the 6315 DLL's with the ones on the XDA2.
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.
I'm a Desktop .Net developer with NO bluetooth experience and only a bit of low-level networking experience so I'm speaking from limited knowledge, but not complete ignorance.
I use my phone as an A2DP source and AVRCP client for quite a few devices (Jabra JX20 Pura, Jabra BT3030, Windows Vista, various BT speaker systems) and Alpine BT300) around my house, garage, car, and on the go. They all work wonderfully (some have better range than others, some better sound), but using any of them presents a couple common issues.
Some devices (like my car), constantly seek out the last paired device until they connect, while most of the other require a connection to be initiated from the phone. The phone doesn't care which is around or has the best signal, just which one successfully connects first.
I'd like an app that could have profiles setup which would let me control certain variables OR at a more basic function (see below):
Bluetooth Profile
Device Priority
Minimum Strength (to be used when more than one device has the same priority)
That would be my ultimate goal, but in the meantime I'd be happy with something as simple as a command line app that could be bound to a key or shortcut which would try to connect to a predefined list of BT MACs for a given profile and stop when the first one connects successfully. Variations on this might allow a connection attempt to a specific device instead of a list. This way I could have StartMenu or Today shortcuts.
The point here is largely to have to avoid nagivigating all the menus needed to initiate an A2DP connection, but I'm sure there are MANY other uses people would find.
If someone could point me in the right direction (I'm researching already of course) to the namespace(s) and or class(es) in .Net 2 or newer which would allow me to enumerate and/or initiate connections, this may be something I could bring to the community (assuming it doesn't already exist, and I have asked MANY times).
I've created a poll also to see what kind of interest is out there for this software and how much support I might receive.
I've been knocking an app up to suit my own personal A2DP needs... and a lot of yours by the look of things ;-) Things it does:
Kinetic scrolling finger friendly list of A2DP devices known to your phone (tap to select then tap again to attempt connection).
Toolbar buttons indicating active A2DP connection status (tap to disconnect active connection).
Bluetooth devices applet shortcut.
Switch bluetooth on (a good few of my devices need the phone to be discoverable so the app forces the phone to be discoverable at all times *blush*).
Switch bluetooth off.
Shortcut to program launcher list (automatically displays this list when you initiate a connection to a selected device... and there's items to display in the list of course).
Command line access (via secondary exe) allowing you to attempt connection (to a named , the last connected or first found device) and disconnect an active A2DP connection. I've only really tested the named device connection but the other 2 modes *should* work
QVGA / VGA and orientation aware.
I've been wanting to work towards getting it up on XDA... but time constraints (and a baby on the way ) have gotten in the way and it's unlikely I'll have the time to do it for a good while. I'd be happy to pass on the code to someone willing to take it further if that's any use. It's written (very quickly!) in VB.net BTW.
It uses a few bits and bobs from other people though:
A2DPToggle's "a2dp.exe" to handle initiating a connection.
Icons from lord only knows where I found them.
The kinetic list code found on here (http://forum.xda-developers.com/showthread.php?t=333124&highlight=klist). IIRC, I used the gingercat updated version and tweaked it to my own needs. There's many a kludge I've put in to the code to get things working quick-smart (D-Pad navigation mainly).
InTheHand 32feet.NET libraries (http://inthehand.com/content/32feet.aspx). These work with MS Bluetooth stack only.
So permission from the respective folks above would be needed before releasing it into the wild I guess.
Here's a screeny
Hey great tool! When I click a device will it auto connect or only open the BT Explorer and will it work with Broadcom BT Stack? Thanks
Oops, meant to say it's been developed for the MS bluetooth stack only. Sorry about that.
When you attempt to connect to a device it first checks the device is reachable and only then attempts to initiate an A2DP connection.
Northernmost said:
I've been knocking an app up to suit my own personal A2DP needs... and a lot of yours by the look of things ;-) Things it does:
Click to expand...
Click to collapse
Absolutely. I can get around in VB.Net and C# just fine. If you don't want to publish the code publicly, PM me your email address and I'll invite you to my Sharepoint site (easiest way I know to share files and manage communique), otherwise attach here.
It sounds like you've already covered 99% of what I was looking for, but I'd be more than happy to do what I can to more the idea forward, even taking suggestions from others in this thread.
About the BT stack, I'm running a Vogue with a ROM cooked in PPCKitchen, how do I determine which stack I'm running and can that be changed?
rainabba said:
About the BT stack, I'm running a Vogue with a ROM cooked in PPCKitchen, how do I determine which stack I'm running and can that be changed?
Click to expand...
Click to collapse
I've no idea what stack Vogues come with but the MS stack device list looks like the attachment below. If yours looks the same it's the MS one. I guess the Vogue forum should have any info on swapping stacks if it's possible.
Sounds like I found the correct people to answer my question about BT. Is there a way / how can I: enable my Mogul 6800 phone to transmit the sound that would normally go through the speaker to my BT headset in order to listen to streaming audio from the net using Kinoma Play which goes out and picks up all sorts of "radio programs" , i.e. not using a direct URL. I am also not able to listen to audio files from the Audio Recorder through anything except the speaker, even not through a head phone. Do I need to download a program or set up my phone differently. I currently have Titan WM6.1 Build 20755 GPS kitchen from PPC Geeks. Thanks so much for your help.
jminor4326 said:
Sounds like I found the correct people to answer my question about BT. Is there a way / how can I: enable my Mogul 6800 phone to transmit the sound that would normally go through the speaker to my BT headset in order to listen to streaming audio from the net using Kinoma Play which goes out and picks up all sorts of "radio programs" , i.e. not using a direct URL. I am also not able to listen to audio files from the Audio Recorder through anything except the speaker, even not through a head phone. Do I need to download a program or set up my phone differently. I currently have Titan WM6.1 Build 20755 GPS kitchen from PPC Geeks. Thanks so much for your help.
Click to expand...
Click to collapse
You need an A2DP capable device (high quality), connected, THEN start your audio program OR use a program called Audio Gateway with a basic Bluetooth headset (low quality audio).
thank you very much.
Northernmost, how about that source code? If you want to pass it along less privately than a post here, PM me and I'll provide a solution (source control, WSS, etc.)
Sent you a PM the other day. Let's go the private way for now.
So I've had this issue since the first Eris leaked ROMs. Basically, any 2.1 ROMs I've tried, INCLUDING what I'm running now, DC 2.07.2
When I turn on bluetooth, and then try to pair my headset, I get a popup saying:
Code:
To pair with "Motoroal H270",
confirm that it is showing the
passkey: 001328.
{Pair} {Don't pair}
The numbers that show up for the passkey are always different, but always 6 digits. I'm assuming the phone is not registering the correct profile for my headset.
Of course, it never pairs.
In 1.5 ROMs I simply entered 0000 as the passkey, but I do not get that option.
I've searched, but with limited keywords to search for... let's just say the hundreds of posts are a little difficult to filter through.
Is that an older Motorola Bluetooth?
I've paired the Motorola H720 with the leaked Eris. Smooth like butter. All I did was enter "0000." Worked fine. Try another bluetooth device, possibly one of more recent vintage. (Don't know how old a model your 270? is.)
I have not had any problems with my Clarion car stereo or my plantronics headset. In my car, in fact, the 2.1's have worked better than stock, since my car stereo picks up the phone and streams the audio automatically every time I get into the car without having to delete and re-pair (as I had to do with stock).
Pete
I have had no luck pairing my phone and any of my cars with any ROM based on 2.1. It pairs, but will not stay connected. Phone says "paired but not connected"; car says "paired, connected; then disconnected"; then endless loops of connected/disconnected. Sucks!
The sad thing is it seems most of these amazing ROM cookers do not use BlueTooth so it is not something they worry about. I bet this is what is holding up releasing the official Sprint update.
I too have tried searching through endless posts about bluetooth and 2.1. All I can come up with is there are some libraries missing from the 2.1 BlueZ; or something to that effect.
I love Damage's 2.0.7.2 ROM! But I have to go back to stock since driving and talking on the phone without a handsfree device is now illegal here in El Paso, TX.
I don't have a car or stereo bluetooth device to pair against. Just tried pairing my bluetooth with the new 2.0.2v2? Alysious ROM. Took 2 sec and nearly totally automatic. Amazing.
My issue with all 2.1 roms is that I can pair, dial and audio stream all day. I just cant talk as no sound or mic. I reflash back to 1.5 and all works well. BT in the car is now useless. sigh
2.1 paired fine, but its a crappy connection on 2.1, on 1.5 i had a better connection
finally used my BT last night with my phone ...worked like a champ! everything was clear to me....i don't have no sound probs and haven't used any of the fixes...
I pair with my bluetooth headset most of the time without problem. I do occasionally have to turn on and off my headset and the bluetooth on the phone to get it to reconnect. Thankfully, it only happens occasionally.....
Maybe I'm just one of the lucky ones (this time) but I have been streaming audio from my hero to the car stereo while while using google navigtion, which politely talks over the music, and have not had any problems. I'll get an occasional skip in the music (probably during downloads of map data), but nothing worth complaining about.
Pete
poor_red_neck said:
So I've had this issue since the first Eris leaked ROMs. Basically, any 2.1 ROMs I've tried, INCLUDING what I'm running now, DC 2.07.2
When I turn on bluetooth, and then try to pair my headset, I get a popup saying:
Code:
To pair with "Motoroal H270",
confirm that it is showing the
passkey: 001328.
{Pair} {Don't pair}
The numbers that show up for the passkey are always different, but always 6 digits. I'm assuming the phone is not registering the correct profile for my headset.
Of course, it never pairs.
In 1.5 ROMs I simply entered 0000 as the passkey, but I do not get that option.
I've searched, but with limited keywords to search for... let's just say the hundreds of posts are a little difficult to filter through.
Click to expand...
Click to collapse
Guys, sorry to revive an old post but I am having this exact same issue as the OP. If anyone has found a fix, please post. Thanks.
Looking at FroYo they have updated some Bluez stuff (what makes out BT work) maybe it will be better when we get that.
Hopefully...
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.