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 on Infiniti/Nissan

Has anyone had any problems pairing their X1 with any Nissan or Inifniti cars? There seem to be some mumblings on the web about their cars and WM6 devices and I've had no luck getting it to work on my '08 G35. Thanks.

bluetooth pairing
i just checked the aproved phone list for your g35 and the x1 is not aproved by infiniti. only certain phones will link to our cars others will not

I have an 08 G35 and have no prob. pairing it with my car. How are you pairing this up with the car?

it also depend if you both have navagation or not

elee888 said:
I have an 08 G35 and have no prob. pairing it with my car. How are you pairing this up with the car?
Click to expand...
Click to collapse
I don't have the navigation so I just click the phone button, tell it I want to pair a new device, and have my X1 start searching. At least now I know it can be done. Thanks for the reply

Well... I do have the navigation. So maybe the pairing process is a little different. But it should work though, it even allows me to download the whole phonebook into the car. Something my other phones in the past did not allow me.

baashha said:
Managed to solve this now.
Of course both Merc & SE didn't have any good solutions.... so had to continue googling & XDA-ing... This is what I did:
i.) Jetware, as I posted earlier has been removed.
ii.) I still had the SAP Profile addition downloaded from one of the forums in XDA on.
iii.) Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys\COD
the default is 5898764 (Decimal) which is "Telephone (Smartphone)" which you would think would work. Changed to 5374476 (Decimal) which is a normal phone.
iv.) Restarted the phone.
v.) Started the pairing process from the car - failed as per before.
vi.) Started the pairing from the phone, and they work!!
Now, they pair automatically as how they would before....
Ram
Click to expand...
Click to collapse
this is how i got mine working with my pioneer deck.
here's the link to the SAP Profile he was talking about.
http://forum.xda-developers.com/showpost.php?p=997872&postcount=166
hope this works for you.

which PIoneer do you have?
I have the DEH-P5900IB and a BT adapter, and i can't get my X1 connect.
All my previous phones worked fine.
it looks like the X1 won't let me pair without passcode, and the radio says Error.
Do you mind explaining exactly how you did it?
Thanks

i have the DEH-790BT.
what i did was after i changed what i mentioned above, then i set my deck to be able to be noticed by other bluetooth devices, then added it through my X1. After I added it through my phone it said successfully connected on my deck and the phone displayed it connected as wireless stereo and hands free. now the only weird thing was it was trying to connect as both the wireless stereo and hands free which seemed to mess with the deck, so I had to turn off my ignition and turn my car back on for it to actually recognize the connection fully. oh and the passcode if you connect through the deck to phone like I did it should be default '0000' but i would check your manual just to be safe, and if your connecting through your phone to the deck (which i haven't tested so I don't know if it works) you can pick your own passcode, which i suggest just making 0000 or nothing.

I have a problem also with my HTC Touch HD (Blackstone)
I can pair with my Nissan Qashqai carkit but soun dis very bad, and the caller on the otherside doesn;t hear anything.
Strangly, but try, when during a call i switch from carkit to phone and back (using the options in my carkit/buttons on stearing wheel) everything is fine!
Checking the internet learned me that this is related to the bluetooth stack (or settings) in WM6.1 (and 6.5 also)
So does anybody have any idea how to solve this, maybe by registry changes or maybe by even "downgrading" the Bluetoorh stack to 6.0 or maybe even 5.x.
Maybe it is also possible to replace the complete MS stack for an other stack?

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

Bluetooth issues

I have 3 main devices that I pair to my phone via bluetooth: watch/lg tone/car
The watch stays paired with no issues, but the watch is having issues swapping from the lg tones to the car and vice versa.
Anyone found a remedy for this?
As of now, I have to go into the bluetooth settings of the one I don't want to use and deselect media/phone, then go to the other and select media/phone. And even sometimes this takes multiple times to work.
My previous phone (gs7) had no issues swapping from the two.

Hi,
Did you get a solution ? I face the same problem and can't find any solution...

Just to clarify, when you are in your car and want to connect to it, the headphones are turned off, correct?

Having similar issues... Every time I try to connect to my car (stock Subaru WRX), I have to manually connect and it takes several attempts before it connects. Once it connects it usually doesn't drop though. Very frustrating...
Another poster resorted to getting a whole new head unit: https://forum.xda-developers.com/oneplus-5/help/sony-xav-ax100-bluetooth-issues-t3634940

ArkAngel06 said:
Just to clarify, when you are in your car and want to connect to it, the headphones are turned off, correct?
Click to expand...
Click to collapse
It's not in my car but with the bluetooth device of my motorcycle helmet. The reference is ncom bluetooth kit 3. I have to connect it manually and it takes several attempts before it connects. Sometimes it doesn't connect at all....

I have 2 headset Plantronics Backbeat Pro and Plantronics Backbeat Fit. They both work flawlessly
My Huawei Watch also works.
But my Nokia 616 Car kit wont connect at all.
And my motorcycle hemlet bluetooth kit, Cardo scala rider PACKTALK, connects, but the audio is slowed down to about 80 percent?

Same thing here.
I have been facing problems with a Sony SBH52 Headset and with my Opel Corsa E, stock infotainment system.
It gives me a hard time connecting but when it does it's stable.
I had the same with my gen 1 Moto 360 but after a factory reset to the watch and a reboot it's stable.
Sent from my ONEPLUS A5000 using Tapatalk

yubimusubi said:
Having similar issues... Every time I try to connect to my car (stock Subaru WRX), I have to manually connect and it takes several attempts before it connects. Once it connects it usually doesn't drop though. Very frustrating...
Another poster resorted to getting a whole new head unit: https://forum.xda-developers.com/oneplus-5/help/sony-xav-ax100-bluetooth-issues-t3634940
Click to expand...
Click to collapse
I had the same issue with my TSX. I did some research and cleared the cache. Worked like a charm afterwards. Did not have the issue one week since doing that

suizdude said:
I had the same issue with my TSX. I did some research and cleared the cache. Worked like a charm afterwards. Did not have the issue one week since doing that
Click to expand...
Click to collapse
Ahem, I seem to be unable to find bluetooth in my app settings. Can you please give me a hint?
It's been driving me crazy these days with my SBH-52 and I want to try this too.
Thanks!
P.S.
I'll also give it a shot with a plantronics pro headset I have to see if it does the same.

Bluetooth profiles implementations, even though they passed certification, are not always made equal! So don't end up pulling your hair if a certain BT device doesn't play nice with another.
Just as an example... Head Unit X had big issues with the initial contacts sync, right after pairing with Samsung phones (already known to sometimes play around some other standards). It would only work after several reconnects. After several weeks of debugging (poor development guys) and reproduction test (poor testing guys) it was concluded that it is a phone issue caused by some wrong timing delays in the process of exchanging information between the HU and the phone. Samsung was informed and the ticket was internally closed.

I have similar problem with Bluetooth Earbuds. Phone simple doesn't "see" the Earbuds. But strange - it can see other Bluetooth devices and other devices can see Earbuds.
I'm sure this is a OnePlus 5 software problem.
Version OxygenOS 4.5.10

i have somhow issue as urs, i have Bluetooth pad lock and android watch, it sometimes connected and sometimes not, i do believe its software issue, im on 4.5.11

Yes, it is strange. After some restarts and on/offs connection suddenly appears