Related
So a friend of mine bought me a TuneLink (for Android) for my birthday. I've been running CM7 Nightlies for quite a long time, and I'm currently using N93. The tunelink is great for the car, if it worked.
I've worked back and forth with support from NewPotato, the makers of the tunelink, and they are stumped. They have sent me multiple devices, thinking it was maybe a hardware issue, but nothing seems to work. At first, the device will pair and connect, and music will start playing, but after about 10 minutes, my phone becomes very slow and will eventually reboot itself. After this, the phone will connect but not pair to the tunelink. No matter what I do after the reboot, the phone refuses its connection.
I also have a Jabra Clipper that works perfectly all the time, without problems, and I haven't seen anyone else complain about the CM7 Bluetooth stack.
Anyone else witnessing any problems with any bluetooth device while running CM7?
bump bump bump
Using 7.1-RC1 on an Incredible:
Also having issues with the TuneLink. Worked perfectly on stock ROM, when I switched to CM7 the device will work for about 5 minutes before the BT signal fades out and then I pick up nothing but interference when I play audio. Eventually the device just disconnects from the phone. Then the Bluetooth radio will not reconnect unless I pull the device and then let it sit for awhile.
This is a deal-breaking issue for me now that my iPod Touch is broken. I have to be able to listen to my podcasts in the car. I really don't want to go back to stock.
I should also add that my Bluetooth headphones work just fine with CM7.
Bluetooth appears to be broken on my Galaxy Nexus I can discover other bluetooth devices fine, and they can discover the Nexus, and pairing appears to be successful from either direction. But as soon as I try to connect/transfer a file immediately I get a notification on the Nexus saying 'connection unsuccessful', 'transfer cancelled by user' (when I didn't cancel anything!) etc.
I've tried this with three different devices (my old HTC Desire, my wife's HTC Legend and my MacBook Pro) with the same results on all three.
Has anyone else run into similar problems, or does this sound like I've got a faulty unit and should send it back? Is there anything I can do to troubleshoot this any further? (I've not rooted the phone and its running the stock Android 4 ROM).
I wish I had an answer; just got my Galaxy Nexus yesterday; it won't pair with any of my bluetooth(s) -- they were all working fine in my Droid so I know how to pair. Any suggestions? Help!! Thanks
After further investigation, it seems it's just outgoing connections that don't work on mine. I can transfer files from other devices to the GN fine, just can't transfer from the GN to any other devices. Haven't tried connecting to a headset or anything like that as I don't have one.
I asked an acquaintance who also owns a GN to test it out on theirs and they experienced exactly the same thing - everything works ok except for outgoing connections/transfers.
I'm wondering if its a software bug if that's the case. If it were hardware related you'd have thought the whole bluetooth thing would be broken.
FWIW: I have been able to pair and connect via bluetooth with my car, with no problem. Downloaded my phonebook to my car via bluetooth as well.
Bt phonebook pairing
I'm having BT issues as well with my G-Nex on Verizon. Will connect/pair with my car, works for making/receiving phone call audio, but will not synch the contact list. Thus, cannot use voice dial in my car (Nissan).
Have searched all over the internet, no real answers. Tried to disable the existing bluetooth PBAPservice as suggested somewhere else - no dice, and it just restarts itself anyway. I've seen some suggestion about rooting the phone and replacing the PBAPservice which may be my next step. Hate to root a phone this new when I may end up returning it if I can't make this work ... sorta a deal breaker for me.
Anyone have any suggestions? Could my phone just be defective? Seems like there are a number of BT issues around, but I can't find anything "official" acknowledging the issue(s) ..
Thanks ...
I'm having a problem with my new GNex bluetooth as well. I'm using a Blackberry Stereo Gateway (an A2DP adapter) in my car and it -does- work, but only after I toggle bluetooth off and back on again. That's kinda annoying.
Previously I had been using an Incredible and it was working fine.
Having problems with Bluetooth as well. I have a BlueFusion unit installed in my car. Worked perfectly fine with my Droid X. Every time I got in the car, it just connected and calls and music both played over the stereo fine. Got my Galaxy Nexus paired and it worked great. However, whenever I get back in the car and the Galaxy Nexus reconnects, the audio does not work. It says it's connected, it plays with no audio coming out of the phone or the car speakers though. Tried re-pairing, no go. Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
DoubleVision81 said:
...Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
Click to expand...
Click to collapse
Okay, I don't feel so bad now. Ouch.
---------- Post added at 02:07 AM ---------- Previous post was at 02:04 AM ----------
cam30era said:
FWIW: I have been able to pair and connect via bluetooth with my car, with no problem. Downloaded my phonebook to my car via bluetooth as well.
Click to expand...
Click to collapse
Does A2DP work properly? And what sort of bluetooth device are you pairing with?
Same here, sending files works, receiving doesn't. Pairing with my bt headset also works fine....
Sent from my Galaxy Nexus using XDA App
mattots said:
Bluetooth appears to be broken on my Galaxy Nexus I can discover other bluetooth devices fine, and they can discover the Nexus, and pairing appears to be successful from either direction. But as soon as I try to connect/transfer a file immediately I get a notification on the Nexus saying 'connection unsuccessful', 'transfer cancelled by user' (when I didn't cancel anything!) etc.
I've tried this with three different devices (my old HTC Desire, my wife's HTC Legend and my MacBook Pro) with the same results on all three.
Has anyone else run into similar problems, or does this sound like I've got a faulty unit and should send it back? Is there anything I can do to troubleshoot this any further? (I've not rooted the phone and its running the stock Android 4 ROM).
Click to expand...
Click to collapse
I had this problem when I fist boot the Nexus and after the first boot of the update to 4.0.1. Reboot the phone, re-pairing the devices and everything is fine since then.
Sent from my GT-P7300
I can't even get my Nexus to pair with my car (Kufatec FISCON unit for Volkswagen). Just straight up error "unable to pair" when I try it. :/
And I have a problem as well. I did get it to pair with my PC but I can't send any files from my PC to Nexus (it works fine with Desire).
I have two Nexus (one is my wife's) and both car have Blackberry Bluetooth Gateways in them. In both cases I am seeing the same issue as the OP, the bluetooth will not connect automatically. However if I manually power on the bluetooth on the phone when the gateway is in connecting mode than they will connect. I never had a problem like this with previous phones.
Is there a official way to inform Samsung of this issue?
I'm also having problems with bluetooth on my Galaxy Nexus. I wanted to transfer files via bluetooth from my old Incredible 2 to my new Galaxy Nexus and it just wouldn't work.
Edit: A reboot appears to have fixed the problem.
DoubleVision81 said:
However, whenever I get back in the car and the Galaxy Nexus reconnects, the audio does not work. It says it's connected, it plays with no audio coming out of the phone or the car speakers though. Tried re-pairing, no go. Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
Click to expand...
Click to collapse
I have this same issue exactly - and had this issue after a System Update on my Droid Incredible for a few weeks before I ended up buying the Galaxy Nexus. I had hoped the new phone wouldn't have this issue. Anyways, it also seems to happen when I take a phone call.
Scenario: I'm listening to music over bluetooth to my bluetooth audio enabled headunit in my car. I receive a phone call, and toggle the bluetooth off so I can take the call privately over my phone's earpiece. When the call is finished, I toggle the bluetooth back on and the phone will connect - however the music is playing, but no audio comes through the phone nor the speakers of my car.
I started having this -exact- scenario issue when System Updates started rolling out for Droid Incredible, and they added the options for "Phone Audio" and "Media Audio" under the bluetooth options. Before these System Updates, my Droid Incredible had worked perfectly with bluetooth audio in my car.
Bluetooth Phone and Stereo
SnarfvsMaximvs said:
I'm having a problem with my new GNex bluetooth as well. I'm using a Blackberry Stereo Gateway (an A2DP adapter) in my car and it -does- work, but only after I toggle bluetooth off and back on again. That's kinda annoying.
Previously I had been using an Incredible and it was working fine.
Click to expand...
Click to collapse
I am having similar problems with both my car's BT phone and BT audio.The phone through my car gets terrible static until I stop and start Bluetooth again, which is dangerous on the highway.
I hope it can be fixed with a little software update.
I have the same problem with new nexus galaxy, pairs well with car bluetooth audio, can hear a confirmation beep on car speakers but no luck in the phone. It just stays on paired but not connected. It doesnt allow to remove pairing and redo it untill rebooting the device.
I'm also having issues with the bluetooth audio in my car. I pair okay with my Sony Xplod head unit, then when I turn off the car and reconnect, the GN starts playing music through the internal speaker instead of the car speakers.
I'm having the previously mentioned A2DP issue as well. Everything connects fine but occasionally, no audio is heard via the deck in my car. Phone calls via bluetooth work, just no A2DP audio.
For those having this same problem, you can fix issue by toggling airplane mode on and off. This is quicker than rebooting (which also fixes the issue).
This has to be a bug. I'm running 4.01. Anyone having the same issue with 4.02/4.03?
AdamUpNorth said:
I'm having the previously mentioned A2DP issue as well. Everything connects fine but occasionally, no audio is heard via the deck in my car. Phone calls via bluetooth work, just no A2DP audio.
For those having this same problem, you can fix issue by toggling airplane mode on and off. This is quicker than rebooting (which also fixes the issue).
This has to be a bug. I'm running 4.01. Anyone having the same issue with 4.02/4.03?
Click to expand...
Click to collapse
Yes. I just got mine last night...ran some errands today. Paired fine in my car, can make and receive calls through the car's audio system, but no sound. I'm running 4.02. Tried this with my BT headphones and the same thing happens.
The airplane mode trick works, however. Thanks!
Hopefully this will get fixed rather quickly!
Has anyone encountered issues with connecting with a car bluetooth? My wife phone conntects with no issues.. She can use the cars remotes to make and receive calls.. Mine I have to pick a contact from the phone for it to work, it will not work with the car or my work truck controls.. It seems everytime it ask if my car or truck can access my contacts, I always choose allow, but nothing happens, but it works with the wifes.. This is with the Lollipop update, that we both have...
happened to me I just rebooted my phone and it connected, also check settings for that paired device
Rom-Addict said:
happened to me I just rebooted my phone and it connected, also check settings for that paired device
Click to expand...
Click to collapse
Got one to work, in my truck.. The car it worked for a while, then quit.. I will try it agian to see if it will stcik... Most likely caused by the 5.0 update..
I've noticed a Bluetooth problem that suddenly started in the last week or so. I upgraded to Lollipop when it first hit, and didn't have any problems.
Now, however, after Bluetooth works fine for awhile (I can connect to a Pebble watch, Bluetooth speaker, car Bluetooth, etc) all day long - then all of a sudden it can't connect to ANYTHING. Toggling Bluetooth off\on doesn't fix it.
Restart the phone, then everything works just fine for awhile. Until it doesn't, and I have to restart again.
Anyone else experiencing this pattern?
I've actually had the opposite happen. I have a iSimple bluetooth box in my car. I've never been able to auto connect with either VZW Note2 or 4. The CS rep told me it had to do only with VZW phones and he couldn't help me out. On another forum, another member mentioned he didn't have any issues with his older phone, so I dug out my old HTC Incredible. Sure enough, it would auto connect. Something changed with Lollipop, and now my Note4 will finally auto connect to the iSimple box. I tried using a third party Bluetooth app prior, but it didn't fix the problem.
Finally got the one in the car working as well... Because the wife and I have the same phone, I just simply changed the name of my phone and it works fine..
If your talking about the developer edition one rom update.. YES.. What fixed mine was wiping everything and redoing the one rom lollipop, then twrp, then installing Ricks Rom Lollipop, things have been perfect. I even addressed it in the ricks rom thread the week.
I haven't had any issues connecting devices but since Lollipop, when I am connected to a bluetooth speaker (car, bose, other bluetooth speakers) the audio gets choppy randomly.
I have done some searching and found others (LG g3) who had the exact same issue after updating to Lollipop.
I have tried rebooting, using different music apps, unpairing/pairing, forgetting the device ect and nothing seems to work. Anyone else having this problem after updating to lollipop? Anyone know how to fix it?
OK, so I got everything working on my unit back in November. Bluetooth worked fine and connected with my phone and OBD device (OBDLink LX).
Suddenly within the last couple of weeks, it's stopped connecting. I have tried rebooting the radio, unplugging/replugging my bluetooth OBD, unpairing the phone, repairing, etc... Nothing seems to work for more than a few minutes. Sometimes it will work for one trip, but then the next trip it's back to REFUSING to connect to either bluetooth device. Remember - BOTH worked before, and I didn't change anything.
Since it's happening with both my Phone and my OBD device, it appears like it is a fault in the stereo. I really don't want to do a full factory reset as that would entail many hours sitting in the car wasting gas idling while I reinstall/reconfigure EVERYTHING only to not even be sure it won't do this again.
Anybody have any tips on something I can do to fix this? There does not appear to be any kind of "unpair" option in the bluetooth settings on the radio itself. I'm wondering if there's a way I can manually reset just all of the bluetooth settings - blow them away and start over without resetting the whole device.
This is a pretty big deal - one of the #1 reasons I bought this device was for OBD datalogging. If that feature does not work, I will rip it out of my dashboard and ebay it. PERIOD...
Adcice?
Nobody?
I tried changing the bluetooth device name, changing the PIN and re-pairing my devices. They work intermittently, but 90% of the time won't connect, or if they do, they won't stay connected.
This is turning my radio into an expensive piece of garbage...
lotherius said:
I tried changing the bluetooth device name, changing the PIN and re-pairing my devices. They work intermittently, but 90% of the time won't connect, or if they do, they won't stay connected.
Click to expand...
Click to collapse
Try keeping wifi on all the time (even if not actually connected to any network).
themissionimpossible said:
Try keeping wifi on all the time (even if not actually connected to any network).
Click to expand...
Click to collapse
I do have Wifi on all the time. I have an LTE Hotspot I keep in the glovebox of my car that powers up as soon as the car powers on. So there's 100% wifi coverage for my stereo no matter where I'm at.
I can randomly get it to connect, but it won't stay connected. When I'm in the bluetooth menu, the devices will actually disappear from the paired devices list. Both paired and available will go blank just suddenly as the devices drop off. Then they'll reappear on their own. So it appears to be the bluetooth stack is crashing - but I'm not sure why.
It is a KLD RK3188 unit. Running latest MCU (came preloaded, just bought it in November - I haven't put a new MCU) and recent firmware, which is a stock firmware, not MalaySK (MalaySK doesn't support the digital display below the screen on my unit)...
At this point this unit is trash if I can't keep Bluetooth working more than 10% of the time.
Sent from my OnePlus One.
lotherius said:
I can't keep Bluetooth working more than 10% of the time.
Click to expand...
Click to collapse
Some smartphones might show an incompatibility with the radio's BT stack. To be sure try with another smartphone.
I would see if it pairs reliably with just one device at a time. My phone has issues connecting with the HU if I first connect my BT headset to the phone but works fine if I do it after. Also the construction of these seems to be sub-par and it could be the bt device or antenna in yours was not connectec/mounted well and you hit a pothole and now its not attached/broken/loose. It may be worth opening and looking inside for something that broke off or is loose. Finally, I have had (well still have) my factory settings change randomly and have to go in and reset. There are settings in the for BT module and it may be worth looking to see if yours are correct.
I also have problems with mine but I'm running Marshmallow in my OPO. As soon as i go back to Lollipop (CM 12.1) it works again.
stormlabs said:
I also have problems with mine but I'm running Marshmallow in my OPO. As soon as i go back to Lollipop (CM 12.1) it works again.
Click to expand...
Click to collapse
Turns out I think it's the OPO. Mine has issues even with 12.1. I think it's based on Modem version not firmware version. Your modem may have been changed when you went back to 12.1.
For me changing modem versions is something I really want to avoid. I hunted forever for a modem version that didn't constantly drop WiFi and LTE, finally found one, and I think that's when the Bluetooth issues started. Every time I flash a modem to the OPO it becomes a nightmare. That phone really does not want you messing with the firmware which is not what I expected when I bought it.
For now I'm back on my old Nexus 5. No problems. I may just sell the OPO and never stray from Nexus again.
Sent from my Nexus 7 using Tapatalk
Hmmm.
My OPO doesn't connect to the headset but my chinese BT OBD dongle connects fine and works.
I have the same problem with my unit but phone working.Only obd2 adapter some times not connecting.Have you find any solution?
I have a similar issue with the Pixel XL.
Previous I was on a Nexus 5 Bluetooth worked perfectly every time without fail, could make calls, listen to music and sync address book no issue.
Now since moving to the Pixel XL I have an issue connecting to the head unit. The head unit shows as a connected device, but then flashes green then grey, green, grey showing connected, disconnected... I can still stream music from my phone over Bluetooth, but voice is not achievable.
Like suggested it's likely to be the BT stack in the handset rather than the head unit as works fine with Nexus 5. Highly frustrating and likely no fix unless it can be patched by software update
I'm also having the same problem as you noodlemctwoodle on a Nexus 6P with 7.1 developer preview.
I've un-enrolled from the beta program this morning, waiting for the ota to come down, as soon as it does will re-test and let you know if it's working, as I suspect it is a problem with the bluetooth stack in 7.1
MTCD MLT (Xtrons TD618AS) Bluetooth and OBD Reader
I have had issues with the Bluetooth on the MTCD MLT V1.76_1 (Xtrons TD618AS).
I found a work around which allows me to use the OBD reader successfully. I downloaded an Android Bluetooth App and toggled off the Bluetooth. Once the Bluetooth was toggled off I was able to access the OBD reader by using the "Piston" OBD app. I tapped on the car picture and waited for the app to think about things. Once the app finished thinking I was able to start capturing the live OBD data by pressing the play picture. I am only speculating, but I feel as though perhaps the firmware engineers goofed. This is even the OBD reader that Xtrons promoted as compatible with the TD618AS stereo I bought with it at the same time. Not to mention that I continually lose FM radio even though the stereo was professionally installed and no wires were cut. I was very excited, and now only depressed.
mr.hackerly said:
I have had issues with the Bluetooth on the MTCD MLT V1.76_1 (Xtrons TD618AS).
I found a work around which allows me to use the OBD reader successfully. I downloaded an Android Bluetooth App and toggled off the Bluetooth.
Click to expand...
Click to collapse
Which Bluetooth app did you download?
Hi guys,
I own a Ford Mondeo (Fusion) built in 2007 and have a problem using my 5t with it's bluetooth hands free.
It works fine, gets recognized, phonebook is in sync.
Problem is it seems to loose connection when dialling very often, but not always. I dial the number, my radio mutes and brings up one ringtone and then all of a sudden it unmutes, plays music again and the phone continues dialling anyway, as if no bluetooth would be active. Normally this happens once or twice and then works the third time around.
Havent found a couse for this issue, it worked flawlessly with all predecessors.
Any ideas on that?
I am running Open Beta 9 on Oreo 8.1.0 but it also was the case on stock 8.0.0. Cant remember how it was under Nougat, tho.
i Have a 2010 mondeo and i have the same issues.. it does work if i dial the number from my actual phone, but scrolling though on the car stereo and dialing a number doesnt always work.
I'm sure its an issue with the car and not the phone.
Well, I think it's solved....and it seems OP did the trick. A few days ago I installed the OTA update onto Open Beta 10 and havent had the error once since then. So maybe this might be worth a try for you as well....
Anyway, I dont think its the car coz all the other devices before the 5 t worked from the off.
Lets hope it now stays that way.