Database Users

Bluetooth and HTC touch problems

Does anyone else have a problem with their Bluetooth and HTC touch? I have tried 2 motorola and a LG BT headset and no one can hear me, but I can hear them. I tried pairing and repairing. I deleted it and added it as a new device. I have even tried the BT with another phone and it works with that phone with no problems, so I know it's my phone. I even tried a hard reset. Does anyone have a solutoin to this problem? I have the latest ROM update from HTC's website for a Bell HTC touch. My motorola headset was working fine, but I think after the latest Bell ROM update it stopped. Does anyone else have this problem or can anyone suggest a solution? thanks. paul.

my jawbone did this but my plantanics 510 fine

My jawbone works fine but there's a problem using hands free connection with my '05 range rover. The phone and the truck connect but then the connection is dropped. My buddy has a motorola razor and his phone works great w/my truck. It appears to be my phone that's the problem. Any suggestions on this?
Thanks so much.

jarmijo said:
My jawbone works fine but there's a problem using hands free connection with my '05 range rover. The phone and the truck connect but then the connection is dropped. My buddy has a motorola razor and his phone works great w/my truck. It appears to be my phone that's the problem. Any suggestions on this?
Thanks so much.
Click to expand...
Click to collapse
This thread is 7 months old...
What ROM are you running?

I am running the NFSFAN 6.5 rom V11 and have he same issue with a motorola BT headset.

edit: i just noticed that the initial question was about a newer ROM update and bluetooth, but ill leave my initial reply here, cuz i often look for solution in old posts, so if this can help anybody :
NFSFAN 6.5 rom V11 and bluetooth
i dunno, but my bluetooth stuff somehow works with the 6.1 update, if you cant find any working solution within an hour, id suggest using a "well tried and tested" ROM version, like the 6.1
i stopped picking the "latest and greatest" in cars, devices, apps, or O.S. for the last two years, and been living a whole lot happier since.
about my 6.1 bell mobility ROM and bluetooth :
i like to tweak my weapons alot, my htc touch has a 6.1 ROM update, and i use bluetooth everyday, and it KINDA works well, enough for me anyway...
listening to mp3 and flv everyday on the transit,
then switching at work on the audio dongle adaptor on the pc,
using an pair of sonorix bsh-100 ( foldable stereo headset + optional plug-in mike)
to me the thruth is that bluetooth is a ****ty technology, i love it, and it's well taught,
but the developpers quickly code ****ty interfaces to it.
my settings all work from htc touch to dongle, but i often have to connect the touch to the headset like up to 3 times, where it tells me its connected, but isnt, when i hear the beep, it means it actually IS.
same at work, connect sometimes once, twice, even four, it eventually connects.
it's isnt button wear off or bad contact, its just the code is ****.
i rented a SUV that had bluetooth, tried connecting my phone, worked first time, a week later we rented the same SUV model, and for the whole trip i wasnt able to connect at all... back at the rental we tested the SUV with the clerck htc touch ( nice coincidence ) it worked right away.
i want to add here that whenever i try to connect through bluetooth, it usually works the first time.
my point is, bluetooth creators did a fine innovative job, but werent supported by developpers.
test your bluetooth phone alot with friends owning bluetooth accessories, youll detect behaviors after a while, and will learn to know its "demons" !
a bluetooth everyday user

V13 seemed to fix the issue
Just upgraded to V13, seems like BT works a lot better.
A bit on my history with BY, I just upgraded from a motorola V710, had a Moto Q for a few months too. Never had any issues with BT using the same Motorola BT earpiece, and varouis others through the last 5 years or so. Always worked like a champ, this was my first experience with BT issues.

Rom that will sync with panasonic kx-th1212b

I've come to find out I'm not the only person that has a panasonic kx-th1212b telephone in my home. I use this to link my cell with the house phones after work. I just recently rooted my phone and put on the vanilla new sprint leak modified by damage to keep root access. This rom paired but did not connect to my phone. I'm going to try fresh 2.1.1 today when i get home but I am assuming this is the same issue since its based of the newest sprint leak. Has anyone found a good rom that will allow for hands free bluetooth pairing?

Does it pair as a regular blue tooth headset or does it do something above and beyond that. I haven't had luck with the new leak gettin ANYTHING to connect, everything just about pairs, but nothing connects.

as far as i know it pairs just like a bluetooth headset. Obviously it can make calls and answer the phone. It says it paired correctly, but it never connects.

I know it doesnt help with the panasonic, but I have the Vtech and it synchs flawlessly with my hero

waltkap said:
I know it doesnt help with the panasonic, but I have the Vtech and it synchs flawlessly with my hero
Click to expand...
Click to collapse
and what rom are you using?

the only rom i got to sync with my bluetooth system built in my car is aloysius and the new fresh toast and fresh rom if that helps with anything.

Well, now that the leak is the same as the official rom i guess my bluetooth will never work on this phone again. I just restored my nandroid backup to go back to stock 1.5 and my phone will connect to my phone no problems. I guess that the 2.1 release is what is killing my connection to my bluetooth phone. great work htc. I'm going to write to them and sprint about my issue. glad i didnt use the official 2.1 because then i would never be able to use my home phone again.

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.

[Q] EVO 4G + Ford SYNC/MyTouch: Poor Bluetooth

Hey All,
I have been scouring the web in hopes of answers and can find none. Evidently I'm not the only EVO owner in this boat either. I own a 2011 Ford Explorer with Sync & MyFord Touch (Fully updated). I pair the phone to the car it makes the connection fine. Begins the setup and sometimes will even connect and be recognized for a bit. But then the phone drops the bluetooth headset part of the connection. It appears (but I can't confirm) that Bluetooth streaming audio is still connected. There was a blissful 3 day window where it all just worked. Then it went to hell...... I saw one post where it said to switch the Bluetooth name back to "PC36100" and that didn't help. I saw another that said use a 4 digit pairing code and that didn't help either.
Its worth noting that I'm running Myn's Warm 2.2 rls5 with the stock & fully updated HTC kernel. So here's what I'm hoping to figure out:
*Have you had this issue with ANY car?
*Have you had this issue with Ford SYNC/MyFord Touch
*Aside from unpairing & repairing were you able to get around it?
*Is there a Kernel with a better bluetooth stack I should try?
Thanks for any help, many thanks will be given!

Unfortunately, the HTC bluetooth is totally worthless. I have a 2010 Ford Focus with Sync and it would connect and sometimes work for awhile, but people on the other line always complained of poor quality. And it wouldn't even connect all the time either. Lots of deleting and readding the phone.
Couple weeks ago I switch to CM7. Since CM has a bluetooth stack they built themselves and actually implemented correctly, I haven't had any problems pairing my phone. I can make calls, stream music, gps, etc and it is all fine. Always connects too. What is nice also is the audio will automatically stop if Google Navigation is giving directions or if someone calls. When I shut my car off and open the door, the audio stops and when I get back in it automatically starts again where it left off.
Basically if you want to use your Evo with a Ford Sync system, you'll need to run a version of CM.

Arg. I'm still waiting on my Explorer
On my 08 Explorer with Sync and Myn's RLS4, all is good. I turn BT off and make sure it is on before I turn the key. I stream audio constantly, and talk a bit. I literally just got around to putting on RLS5 today, haven't driven yet.
I partially agree with teamgreen02. It's HTC, not Ford. Does texting work with CM7? That would push me over the edge (or Explorer, pun intended)

It seems that there are a bunch of phones that have issues maintaining connectivity with the latest Sync system. I had to re-pair a BlackBerry to an '11 Explorer this afternoon. There is a backwards pairing procedure that may help rectify your issue. If you try searching for your phone from the vehicle instead of searching for sync from your phone, it has, in my experience, minimised connection drops, especially on the latest versions of Sync...
Btw, I am like the only tech at my dealership who really understands how to even pair phones to Sync, let alone diagnose the concerns our customers have described. There is also a system compatibility chart that we reference to determine if a particular device has been tested and verified to work with certain features of Sync. Last I checked (the October 2010 update) the Evo still wasn't certified compatible/tested...
Sent from my PC36100 using XDA App

Does anyone have any updates on this? My wife's Sync is working fine with her Evo but the sound quality sucks when she calls. Her phone isn't rooted.
I did update the Sync software from v1 to 1.1 (She has a 2008 Ford Edge Limited) but need to do further updates to the system since there are updates available.

Here is my experience/.02.
My wife drives a 2011 Ford Edge with sync....she has a stock Evo4g. When she bought the car 2 months ago, bluetooth seemed to work fine...now she is having the exact same issues everyone else is having. The bluetooth connects/disconnects and just plain doesn't work. I attempted to fix it and.....no. If i unpair from both the car/phone then retry to connect them, it connects for a second and when it tries to send the phonebook from the phone to the car, the connection dies. The phone still displays that bluetooth audio (not phone) is connected.
I then tried my Evo 4g (CM7) on her car...no problems whatsoever. Sync'd and connected fine...phonebook transferred over in about 5 seconds and everything worked great.
To note, my Evo 4g also works perfectly on my 2011 Infiniti G37...
So I think my example further proves that HTC's bluetooth software is likely the causative agent and is likely junk....root or die i guess =p
hope this helps someone

I rooted and installed MIUI and dont have any problems yet with sync.
Although,
I was looking looking to pull the bluetooth stack of the droid X which has the MAP bluetooth profile, that will allow ford sync to read and write text messages for you.
any ideas on how to do this? Or where to find in in the droid X?

2010 Ford Focus here, works fine for me. Using Fresh 3.5.1.

The bluetooth stack should all be dependent on what kernel you are using on your rom, so if you already have it rooted, try to change kernels and see how it improves...
as far as the MAP profile, i found this thread in the Q&A section, and it also recommends pulling the MAP profile (for text messessaging) from the motorola droid kernels.
I wish i knew how to do this.
I was hoping for someone to be able to do this for us
EDIT: I also found this thread:
http://forum.xda-developers.com/showthread.php?t=741332
its trying to get the MAP profile into the nexus one...
they found the new bluez stack had the MAP profile included:
http://code.google.com/p/google-summer-of-code-2010-bluez/updates/list

I have not used sync in a long time in my 2010 escape, but I'm wondering if the text message function works as well. Any word on this?
Sent from my PC36100 using XDA Premium App

lawmangrant said:
I have not used sync in a long time in my 2010 escape, but I'm wondering if the text message function works as well. Any word on this?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
No, the text messaging does not work for the unrooted Evo and it doesn't work for a rooted Evo under Myn's Warm TwoPointTwo RL5.

I Just had a 2011 Explorer limited for the past week as a rental and it worked fine for me (music & calls). I know this does not help much hope you get it going.

i had my EVO running fresh 3.5 and worked great in my Escape, i just switched to twopointtwo ROM and now here i am looking for a solution, not sure if its the rom or the kernel since i switched both..

alexdogg said:
i had my EVO running fresh 3.5 and worked great in my Escape, i just switched to twopointtwo ROM and now here i am looking for a solution, not sure if its the rom or the kernel since i switched both..
Click to expand...
Click to collapse
got it working for a day but its disconnected again, im going to explain what i did hoping someone with more knowledge can help us SYNC users to connect bluetooth
used fresh EVO 3.5 for a while and worked great, then i got bored and changed rom to myn's warm 2.2 with the kernel included and bluetooth started disconnecting after 30 seconds or so...
i tried
ms79723's SBC for Netarchy's CFS More Aggressive 4.1.9.1 Kernel (v7)
Ziggy471 Warm TwoPointTwo RLS4 Kernel
they didnt work either... so heres the funny thing..
i wiped and reflashed a fresh version of the same rom (Myn´s warm 2.2), this time i didnt restore anything, no apps, no contacts, anything, left it clean.. then i paired it up and voila.. it worked for a long time in my ESCAPE, so i thought it was working and restored all my apps and data.. and to my frustration... its disconnecting again.
so does this have to do with the kernel or with some apps or what.

has anyone figured out how to get sync working with blue tooth messaging.

marcw2 said:
has anyone figured out how to get sync working with blue tooth messaging.
Click to expand...
Click to collapse
I don't think the android kernels have the message access protocol that is needed for this to work.
Sent from my HTC Evo 4G

2010 Ford Focus. Bluetooth sucked with stock ROM and warm, dropped connection all the time. Works great with CM7. Definitely an issue on the phone side and not the car in my case.
I am also wondering if we can somehow get the text messaging working. I don't think its officially supported on any Sprint phones.

2010 Moutaineer here - never had a problem with Bluetooth on rooted stock EVO ROM.
Listen to music all the time - even the "call-transfer" functionality works fine when I enter the vehicle while talking on the phone.
Only thing is - I wish the damned thing would auto-synch for media-audio on Aux1 instead of me having to select the source all the time - anyone know how to do this?

2010 Lincoln with mytouch/sync and rooted with stock rom. No problems at all. Sometimes it gets a little static sound but I just turn my Bluetooth off then back on.
Sent from my PC36100 using XDA App

Think the problem lies with the Sense BT stack.

[Q] Question about issues with bluetooth in EC07

Good morning fellow forum member. I've recently begun having some significant bluetooth connectivity issues with my continuum and Ford Sync system in my 2011 Fiesta. Now, before you start ranting about your loath for microsoft or Ford please hear me out. In theory, the Sync system, combined with bluetooth technology, is a great way to go hands free. It also allows for the coordination of the system and Pandora & Stitcher Radio on an Android phone.
Anyway, lately my bluetooth connection to my car has been causing FCs on my phone. They are the type of FCs that cause the "long-short-short-short" haptic feedback but doesn't throw a pop-up message describing the cause of the FC. So, when the feedback occurs the phone will sometimes lock up but it always disconnects the bluetooth. I don't use bluetooth in any other fashion so I can't be positive that it's not an issue with the car's bluettoth system.
With all of that said, is there an inherent issue with the bluetooth system on our phone? If so, is there a fix for this? I'm currently running the EC07-clean_new ROM. This was installed over the SCH-I400-EC07-FROYO-REL-PRODUCTION ROM. My broadband version iss:i400.0.6v.EC06, Kernel 2.6.32.9 and build SCH-I400.EC07.
Any help that you brilliant folks could offer would be much appreciated.
Thanks,
Ray

I run bluetooth constantly (it's the only way I talk on my phone, driving or not.) I've never run into this issue. Have you recently downloaded any new apps? I found that there are some apps that simply don't play well with our phones. Especially radio based apps (I.E. the issues a lot of us were having with gps based apps, or gps losing it's lock, after a while. Wireless tether 3.06 beta completely screwed my phone up... etc). The only other thing I could suggest is to drop your phone from the sync, and reconnect it... I do this with all my bluetooth devices at least twice a week as a matter of course. And if you want to experiment to see if it's sync or your phone, assuming you have bluetooth stack on your computer, you could connect it to your phone. Other than that, maybe find a friend that has bluetooth and connect it?

Thanks for the suggestions. The most recent app I have installed that uses a radio is the new Stitcher, though I have been having some issues with "My Tracks" FCing but I think that is another issue. Anyway, prior to your reply I found an app on the market called "bluetooth fix repair" It's free and I gave it a shot. I've also deleted the phone from my car's list and repaired them. So far so good. I have a bluetooth stereo headset I'll have to try. I probably have too many apps to begin with. I'll see about deleting some of the ones I don't really need.
Thanks again,
Ray

Reborn627 said:
Thanks for the suggestions. The most recent app I have installed that uses a radio is the new Stitcher, though I have been having some issues with "My Tracks" FCing but I think that is another issue. Anyway, prior to your reply I found an app on the market called "bluetooth fix repair" It's free and I gave it a shot. I've also deleted the phone from my car's list and repaired them. So far so good. I have a bluetooth stereo headset I'll have to try. I probably have too many apps to begin with. I'll see about deleting some of the ones I don't really need.
Thanks again,
Ray
Click to expand...
Click to collapse
I think you should be good with rourine disconnect/reconnect. Asfor too many apps, the only thing rhat matters there is storage space. Android wint let you run "too many" at once. Itll delete from ram as needed. I was just saying that certain apps dont seem to play well with others. But that is an android issue, not your phone in particular.
I'm not here for a long time. I'm here for a good time. To hell with the red wine. Pour me some moonshine. - King George

I'm totally stumped here. Yesterday I decided to reflash my phone. I figured any issues might be ironed out. It must be an app issue, although it is going to be a PIA to uninstall then reinstall each app and test the BT after each app install. I thought that it might be the trailblazer101 car cradle, desk cradle or the sticher apps that were giving me the problem but that doesn't seem to be the case. Maybe I'll try replacing the BT files with the ones from eclair to see if I end up with the same trouble. Any idea if that might cause more problems? Are the BT files android version specific?
Peace
EDIT: I've not swapped the BT files from eclair but I did spend an hour or so listening to Stitcher radio via a bluetooth headset. It doesn't seem to be a BT issue. More likely an issue with the connection to the Sync system itself. Connecting via bluetooth is no problem in the car. It's not until I attempt to engage a function other than the phone that an issue occurs. I may try to reflash the EC07-clean ROM and see if there was something with the EC07-Clean_new version that I've been running for the last few weeks.

OK, the BT issue seems to be corrected. I flashed adrenalyn's EC07-clean ROM and that seemed to do it. Something must have gotten corrupted. So, issue resolved...i guess.