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.

Bluetooth pairing problems with all 2.1 ROMs.

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...

Bluetooth not working right with Pioneer and Android

I've been using Androind on my HTD for +/- the past month or so, and have yet to have stable bluetooth operation through my Pioneer AVH-3200BT which is enabled for BT phone calls (NOT A2DP). I've been through several builds, and currently am using shu8i's latest shubCRAFT 1.4d (23.08.2010 build). I'm got HPSL3 and Radio 2.12.
I get a lot of forced close app errors with trying to establish BT connection. Sometimes I get further, like the Pioneer can usually pick up my contact list after a few tries... But the worst happens when I try to make a phone call. The system hangs, the sound goes dead, the Pioneer cancels the call, and the HTC HD2 usually crashes back to the home screen. From then, I usually dont have any sound for anything until I reboot the HD2.
In WM6.5 Bluetooth works fine with the Pioneer.
Can anyone help me out with this? I'd be willing to pull some logs / demos / or get more vital information if I knew where to look. I'll be the geinea pig!
Thanks in advance

I'll add plantronics voyager 815 to list. maybe a list of working headsets might help if anyone has one.

my Jabra T3030 doesn't work either. It works great with A2DP and it even rings when i get a call. but it hangs the device if i try to answer and there's no audio in calls.
I tried every build possible

I cannot get my Bluetooth wireless headset to work also ,it works on phone calls but on media ,no sound is transferred ,Ian using Mattc 1.6b with sonyericsson headset ,that works more than perfect on windows
Sent from my HTC HD2 using XDA App

saabguy123 said:
I've been using Androind on my HTD for +/- the past month or so, and have yet to have stable bluetooth operation through my Pioneer AVH-3200BT which is enabled for BT phone calls (NOT A2DP). I've been through several builds, and currently am using shu8i's latest shubCRAFT 1.4d (23.08.2010 build). I'm got HPSL3 and Radio 2.12.
I get a lot of forced close app errors with trying to establish BT connection. Sometimes I get further, like the Pioneer can usually pick up my contact list after a few tries... But the worst happens when I try to make a phone call. The system hangs, the sound goes dead, the Pioneer cancels the call, and the HTC HD2 usually crashes back to the home screen. From then, I usually dont have any sound for anything until I reboot the HD2.
In WM6.5 Bluetooth works fine with the Pioneer.
Can anyone help me out with this? I'd be willing to pull some logs / demos / or get more vital information if I knew where to look. I'll be the geinea pig!
Thanks in advance
Click to expand...
Click to collapse
I got similar problem with my Motorola Headset too, it just keep hanging with the dialer, without bluetooth one, the dialer works flawlessly. Mine is Shubcraft

I think I figured it out... I set the pioneer to accept connections with pin 1234 instead of 0000 and it seems to be working alright now.
Sent from my HTC HD2 using XDA App

precsmo said:
I got similar problem with my Motorola Headset too, it just keep hanging with the dialer, without bluetooth one, the dialer works flawlessly. Mine is Shubcraft
Click to expand...
Click to collapse
I'm also having troubles with my Sony Ericsson MW600. I did get it going with I think ShubCraft 1.4b but now on 1.5 it won't have it...
It pairs fine, works fine with Media - AVRCP controls working, etc.
But the phone app just doesn't like it. I've tried to switch BT on and off whilst in call and most of the time get a force close on the phone app.
My libbluetooth.so files are dated 04/08/2010. Does anyone have later dated .so files I can try? Or earlier ones for that matter!?
Thanks all.

wheeliemonster said:
My libbluetooth.so files are dated 04/08/2010. Does anyone have later dated .so files I can try? Or earlier ones for that matter!?
Thanks all.
Click to expand...
Click to collapse
I've changed libbluetooth.so for this one:
http://code.google.com/p/androidobex/downloads/detail?name=libbluetooth.so
it work's but the hd2 ask for the bluetooth pass every time that connects.

magnus48 said:
I've changed libbluetooth.so for this one:
http://code.google.com/p/androidobex/downloads/detail?name=libbluetooth.so
it work's but the hd2 ask for the bluetooth pass every time that connects.
Click to expand...
Click to collapse
I can't even get the bluetooth radio to turn on using this file...
Not having bluetooth headset is the most frustrating thing. Well its a close second to nearly every android build claiming to have bt working in the OP but it doesn't work!!

bhilgeman said:
I can't even get the bluetooth radio to turn on using this file...
Not having bluetooth headset is the most frustrating thing. Well its a close second to nearly every android build claiming to have bt working in the OP but it doesn't work!!
Click to expand...
Click to collapse
I've tried changing the libbluetooth, libbluetoothd and libbluedroid files time and again with Shubi's build and nothing works.
I had some success today though. I'm currently using Shubi's build but with the michyprima r10 kernel.
I was trying a different kernel earlier - the huanyu OC kernel from here:
http://forum.xda-developers.com/showthread.php?t=777921
This got my BT headset working for calls and A2CP/AVRCP...
PLEASE NOTE: This kernel is in beta still, read the thread!
Unfortunately, it proved to be a little unstable for me, so I've had to go back to michyprima's kernel.
But it does seem that the problem lies in the kernel, rather than the bluetooth libraries.

bhilgeman said:
I can't even get the bluetooth radio to turn on using this file...
Not having bluetooth headset is the most frustrating thing. Well its a close second to nearly every android build claiming to have bt working in the OP but it doesn't work!!
Click to expand...
Click to collapse
A reboot is required after overwriting libbluetooth.so file
With some old android distributions I cant turno on the bluetooth radio, but it was a kernel matter. Maybe updating the kernel solves the problem.
Now I use FroyoStonev2 with this [kernel][.32.9](BFS+BFQ+AXI+OC+UV) build on 09.09.2010(version 0.2)
But every time that reboot the hd2 need to pair with the freehands.
Every time that reconnect it needs to reenter the code.

[Q] Bluetooth issues with Froyo

So I flashed to a froyo ROM over the weekend and have found someone posted a fix for the gps issues, but I'm having BT issues as well. Has anyone else experienced this: I can pair certain BT accessories but not others, and even when paired the devices cannot connect without multiple connection requests.
My specific issue is that I have motorola rockr bt earbuds, and a Jabra car kit, and they both pair with the phone (after a few trys) but neither will automatically connect to the phone once they're turned on. With the earbuds I have to manually try to connect 6 or 7 times in a row before they'll connect, and even then they may only connect with the phone audio only. This wasn't an issue with the stock ROM so I'm assuming its the bt radio library for Froyo thats the problem?
I'm not new to development, but I'm kinda new to development on Android. I've been trying to learn more about the radios and how they're configured within the OS but I haven't found a lot of good documentation on it. I'd be happy to work this out for myself and post any improved radio to the forum but it would be helpful if someone could send me a link to some learning material? If someone has an improved Epic Froyo BT radio to flash that would be helpful as well

yes bluetooth issues as well, but different in that only when i turn bluetooth on it foreclose's. the bluetooth is otherwise not affeceted. only on the initial start up.

I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!

Delta1Fox said:
I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!
Click to expand...
Click to collapse
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.

revjtanton said:
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.
Click to expand...
Click to collapse
I noticed that too with the stock 2.1. However, Bluetooth voice dialing is a feature built into 2.2. I've read that some people having it work great, but other's like myself, are not having it work at all. Oh well. I'll live for now. Hopefully if it isn't fixed beforehand then it'll be fixed with the "official" release. LOL.

now that you mention it, i had this problem too doing some bluetooth file transfers between my buddy and I's phones last night. it struggled to connect multiple times but after the first successful transfer it seemed to stop having problems for a little. I'm moving back to 2.1 until we get some non-beta custom roms for froyo because i use bluetooth and gps everyday. just out of curiosity though, for those who are having problems, which rom and modem are you using?

I put the DI18 modern on there and that has seemed to fix the gps more or less. I think I'm going to go back as well. Maybe I didn't flush data enough times but layar can't find the camera, neither can the bar code scanner...it's close, but Froyo just isn't ready for the Epic yet.
Sent from my SPH-D700 using XDA App

Still having Bluetooth problems with official Froyo release on Epic 4G
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...

I am using the new official Froyo release from Samsung/Sprint. having the same buggy issues I had with the old leaked version.

donkeysauce said:
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...
Click to expand...
Click to collapse
I can confirm these issues still exist in the official release.

I'm having the same problem, but when I use bluetooth in my car, it insists on transmitting sounds to my car's bluetooth, even when I repeatedly uncheck Use for media audio. I don't have an option in my car to disable A2DP. My only complaint with Eclair, other than speed (I'm using Bonsai4All, and previously, Syndicate) was that I was running out of space for software (was using EpicExperience). Sometimes, bluetooth won't connect at all, necessitating a phone reboot, or going into airplane moe and then back out. So I'm gathering that this is across the board, regardless of Froyo build? Syndicate didn't work at all with my car.

ROM that doesn't have Bluetooth audio problems?

I *REALLY* don't want to buy a different phone, but.... I recently swapped out the headunit in my truck from a Clarion to a Kenwood due to phone audio problems with the Clarion. So now the phone over BT with the Kenwood works great but the audio over BT is skipping and breaking up. Seen lots of posts about this being a problem, but no solutions. Sometimes rebooting the phone helps, but not usually. Sometimes forcing Bluetooth Share to close will help, but not usually. I've deleted and re-paired the devices.
I am currently running the stock 6.0 ROM, build 24.49-18, only rooted. The phone says it's up to date.
On to my point... do any of the alternate ROM's seem to have the BT audio issues worked out??

djmasters said:
I *REALLY* don't want to buy a different phone, but.... I recently swapped out the headunit in my truck from a Clarion to a Kenwood due to phone audio problems with the Clarion. So now the phone over BT with the Kenwood works great but the audio over BT is skipping and breaking up. Seen lots of posts about this being a problem, but no solutions. Sometimes rebooting the phone helps, but not usually. Sometimes forcing Bluetooth Share to close will help, but not usually. I've deleted and re-paired the devices.
I am currently running the stock 6.0 ROM, build 24.49-18, only rooted. The phone says it's up to date.
On to my point... do any of the alternate ROM's seem to have the BT audio issues worked out??
Click to expand...
Click to collapse
Answering my own question.....
I ended up trying another ROM, AICP for clark, and so far AVRCP is working fine, it has connected/disconnected several times and has always come back quickly and without any skipping/stuttering. I haven't tried the phone over BT yet. And it's a pretty good ROM beyond that!!!

djmasters said:
Answering my own question.....
I ended up trying another ROM, AICP for clark, and so far AVRCP is working fine, it has connected/disconnected several times and has always come back quickly and without any skipping/stuttering. I haven't tried the phone over BT yet. And it's a pretty good ROM beyond that!!!
Click to expand...
Click to collapse
I was wrong, after a couple of days AICP started doing the same thing. Replaced XT1575 with an HTC 10, I wish the screen was larger but it's a really nice phone!!! And no Bluetooth troubles.

My phone is connected to my car radio any time I'm in the car, and not having this issue. I'm still on 5.1.1 stock but rooted. Headunit is a Alpine CDE-W235BT. I've had it hooked up 5+ hours at a time. No issues with media or phone calls.

Yeah, it works for some but not for others... I think it's more headunit dependent... my Clarion was OK for music but the phone was jacked up. Reverse with my Kenwood, phone OK but audio jacked. Either way, it had to go.....

Factory rom is the only one I can get to work properly with BT in my Mercedes

I haven't tried it on the Moto X Pure, but on the 2nd gen Moto X, Cyanogenmod had infinitely better bluetooth strength than the stock rom, or any other rom I tried. I'm not saying it's the same for the Pure, because they're probably maintained by different people, but worth looking into at least.

Bluetooth usually connects between my Moto X Pure and Mazda3, but there is a 35% chance that when I turn on my car the audio will connect in this really strange manner where tracks skip and the audio sounds horrific. The only solution is to disconnect and reconnect again, which takes another 30 seconds.
Every ROM I have tried on Moto X Pure has had this problem:
Stock, CM13, AICP
It's gotten so annoying that I've decided I am going to sell my Moto X Pure and revert to my Galaxy S4. Never have ANY problems with my old Galaxy.