Related
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.
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.
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.
I have the Nexus 7 with 3G running the latest Android 4.2 stock/rooted. I've been trying to connect my Motorola Bluetooth Android Keyboard and it pairs fine, shows it's connected but nothing works...no typing, home button...nothing. I tried it on my VZN Galaxy Nexus running Jellybelly 10.2 (also Android 4.2) and it also isn't working. I did some research and saw that 4.2 might have broken bluetooth connections? Is this true? Is there a work-a-round or do we just have to wait for Google to send the update?
Thanks
Should work fine. I've got a Nexus 7, Jelly Bean 4.2, rooted, Motorola Android Bluetooth keyboard and mouse.
All paired and working no problems. Try switching off the keyboard and then reconnecting again.
kilowatt.xda said:
Should work fine. I've got a Nexus 7, Jelly Bean 4.2, rooted, Motorola Android Bluetooth keyboard and mouse.
All paired and working no problems. Try switching off the keyboard and then reconnecting again.
Click to expand...
Click to collapse
I did that about 20 times...still nothing...I tried changing batteries but they were from my tv remote...I'll try again tomorrow with brand new batteries...I just can't figure it out...frustrating...unless the keyboard itself is faulty? It used to work on my iPad about 4 months ago...
Well I tried new batteries and no go...it wouldn't work on my iPad either so it's not 4.2. Plus my Bluetooth mouse worked just fine. I just ordered a new keyboard from eBay so we'll see how that goes
Sent by an Android Guy using an iPad...
The Bluetooth stack was replaced in 4.2 to a new, standard conforming one from Broadcom. This is a good thing - long term.
Devices that were dependent on the BlueZ stack will have problems.
rmm200 said:
The Bluetooth stack was replaced in 4.2 to a new, standard conforming one from Broadcom. This is a good thing - long term.
Devices that were dependent on the BlueZ stack will have problems.
Click to expand...
Click to collapse
Thank you! I hope my new keyboard will work now! Lol
Sent by an Android Guy using an iPad...
Hey,
I own a T330NU. I bought a Bluetooth Keyboard to use with it. Everything was fine for a month, and then all of a sudden, the keyboard started being "unable to communicate" with Bluetooth. I unpaired it, tried to pair it again and it still didn't work. I NEEDED to use my keyboard, so I did a reset and restore and it worked fine after that. Until another month later, when the same thing happened. This time, a reset didn't help.
I'm able to connect the keyboard to other devices, such as my Macbook and iPhone. I'm able to connect my tablet to other Bluetooth devices, like an audio speaker and my boyfriend's T330NU. I'm also unable to connect my keyboard to my boyfriend's T330NU.
I tried rooting my tablet to see if it would help. It did not. I deleted the Bluedroid folder. That did not help. I tried turning my tablet on and off. That didn't help. I tried most of the Bluetooth keyboard apps on the Play marketplace, that did not help.
There aren't any custom ROMS for the T330NU, so I feel like I'm screwed. I NEED to be able to use a keyboard with my tablet. I'm waiting for the Stock ROM to download and MAY try that. But c'mon! I'm also going to try out an Apple Bluetooth Keyboard tomorrow, but if it doesn't work, I may pull out my hair. AGH! Any ideas?
hi,
from your post;
I'm also unable to connect my keyboard to my boyfriend's T330NU.
------------------
suggests the problem is the keyboard not the tab.
as far as i know bluetooth devices need batteries, perhaps that's the issue?
m
You were right! Weird! Battery fixed it!