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.

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

Using Ford Sync with MyTouch 4G Genius Button

A friend of mine has been nursing an old BlackBerry 8700G for many years now. Last week he decided to put it out to pasture and picked up a MyTouch 4G (due, in part, to my glowing review of the device).
He's not happy.
Some of his issues are the usual complaints which can be handled with a quick tutorial and a few tweaks here and there.
The real problem, though, is integration with Microsoft Sync in his 2009 Ford Escape.
The aged BlackBerry worked pretty much as expected with Sync but the MT4G does not. Making and receiving phone calls seems to work just fine but the SMS messaging features of Sync do not appear to be compatible with the MT4G.
This shouldn't matter, though, right? The "Genius Button" lets you send and receive SMS messages via voice control. Unfortunately, while he and I had both assumed that the Sync system would let him access all of the voice control features of the Genius Button (including full voice-control of SMS messages), we were mistaken. Sync doesn't seem to provide any mechanism for triggering a phone's built-in voice recognition system, thereby rendering the Genius Button features completely useless.
Now, I've never used Sync myself so I'm holding out hope that there is some kind of trick or software update that will get his setup working the way he wants it to work. Anybody know something about this that I don't or is he pretty much screwed?

Shouldn't have bought a Ford...
Sorry had to say it

I have SYNC in my 2010 Mustang, and to my knowledge it doesn't have the ability to forward a call button command to the phone like most Bluetooth headsets do. SYNC is more of a "command center" rather than a glorified BT headset in a car stereo, so it pulls in data and info from a variety of sources and you use the voice and button commands to access and control it. You would likely have to tell the car "Bluetooth Streaming" and have the phone playback information for you (unfortunately, the microphone won't forward anything so the handsfree profile will just tie that up).
If he's really, totally, and COMPLETELY hung up on that and still wants Android, I've read on the SYNC forums that the DROID, DROID 2, and DROID X all support SMS transmission through SYNC, including reading and replying. Of course, this might be mitigated by Gingerbread since it's supposed to be getting a new BT stack from what I've read. You know, or not.

Please post questions in the Q&A section.

Question, do they actually have Sync working correctly with their devices? I have a MT4G and am trying to sync with my 2010 Ford F-150. The phone book starts to download and then quits half way through and then the bluetooth causes the phone to freeze up and gets completely screwy. My Vibrant and HD7 do great....the MT4G not so much.

cmerrifield said:
Question, do they actually have Sync working correctly with their devices? I have a MT4G and am trying to sync with my 2010 Ford F-150. The phone book starts to download and then quits half way through and then the bluetooth causes the phone to freeze up and gets completely screwy. My Vibrant and HD7 do great....the MT4G not so much.
Click to expand...
Click to collapse
Mine works fine. My G2 would act strange with my Mustang until I figured out I had to disable WiFi before getting in the car. I'm not sure if it's just WiFi, or the WiFi calling app hanging or resetting the radio, but after doing that my SYNC system would download the phonebook and stay connected the whole time. My mT4G doesn't require this.
Edit: Just thought of this, but I'm using WiFi N at 5GHz at home now with the mT4G, whereas I was on 2.4GHz with my G2 and had the issues. Normally you get different radios for different frequencies, so I wonder if that's the case here.

N4 bluetooth won't sync with car

Hey all,
Recently got my n4 and am currently running cm10 nightlies on it, but today I picked up our new car (Hyundai i30 premium) which has bluetooth built into the audio system and I can't get my n4 to sync with it properly. My partners Desire HD syncs no problems and all her contacts phone book everything shows up fine. My n4 wouldn't even sync originally then I just kept retrying and eventually it synced but nothing really works, music won't play through the speakers (the audio system just sits there waiting for music and nothing happens) my phonebook etc don't show up (after me allowing them permission) I can't even make calls.
I have heard that the n4 has some bluetooth problems but nothing this bad, anyone have any suggestions that I can try? Happy to go to another ROM if that will help??
Thanks,
Hosh

this build has serious BT issues. i can't even find a mouse that works. wait and see what the 4.2.2 update brings.

I own a Hyundai Elantra GT which is the US version of the i30 - I didn't seem to experience any issues when I paired it this morning, but I"ll double check when I get out of work this afternoon that the contact sync is working. I am, however, on the stock rom.

I own a 4 day old Dodge Journey and it pairs with no issue to Uconnect.
Try a different rom?
If thats not it, then its your hardware.

The new bluetooth stack in Android 4.2 is causing a lot of issues. Personally, I don't have any problems connecting to UConnect (Jeep Grand Cherokee) or my SmartMini (bluetooth music streaming).
I am waiting on delivery for my MetaWatch, there have been complaints that 4.2 isn't connecting well with it but I guess we'll see. CM10.1 users don't seem to have as many problems. I'm running Xylon w/ Franco r53.

I had the same problem with Chevrolet captiva until I have installed custom ROM and is working perfect now.I have tried every custom ROM and is OK with all.

I have this problem but there is a way around it (for me anyway).
Download Bluetooth file transfer from the market.
Delete the connections with your car. Both on the phone and your car.
Open Bluetooth file transfer. Select the Bluetooth screen.
Make a connection. The default android Bluetooth will ask for a password. Don't enter it. Instead go to your recent apps and select Bluetooth file transfer. Put the password in the request screen the app supplies.
Bluetooth file transfer should pair the devices and make a connection.
Once done. Kill Bluetooth file transfer as you won't be able to exit.
You can then uninstall Bluetooth file transfer if you want (although I tend to keep it for when I change ROMs or have to do a factory reset etc).
Hope this works for you
Sent from my Nexus 4 using xda premium

Hey all,
Sorry for the late reply, been away for the weekend. Thanks for all the advice, tried them all and no luck. Will try out a mates n4 tomorrow and see if he has any luck syncing with the car, if he does might just flash roms again.

after flashing a new rom, I had problems pairing w/bluetooth and connecting w/wi-fi. I fixed the problem by restoring my system settings w/titanium backup thanks to someone's suggestion.

Seems the only thing that worked for me is when it asks to sync my phonebook I have to say no, if I say yes it seems to freeze the whole thing. Makes me think if I click yes I might just need to give it 10-15 mins to sync, might try that tomorrow. But for the moment at least it's half working!