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!
Hey guys,
I'm having some pretty bad bluetooth issues, and my searches haven't really found a solution. When I attempt to connect my phone to my car headunit, my headunit shows it's connected and my phone also shows connected. But the audio still comes out of the phone speaker. After a few minutes it will disconnect and reconnect a few times, sometimes only showing headset connected and not media. Eventually the bluetooth just locks up saying "connecting...". If I turn off bluetooth on my phone, the stereo still shows it is connected to a bluetooth device. I tried to "forget" my device and re-paired, and the process seems fine except the phone never asks if I want to share my phonebook, so I assume something behind the scenes is already broken at that point.
This is a very new problem for me, and my bluetooth was working fine with this headunit for months now using numerous different ROMs from GB to JB. I was on AOKP JB build 1 when this started. I tried a full wipe and reflashed the ROM and still had the problem. I have tested this on about five other ICS and JB ROMs and am currently on CM9.1 and the problem is continuing. I also tried a different phone to make sure the problem wasn't my headunit and the other phone worked as expected.
Has anyone else had this problem, or does anyone have any direction for me to fix this? Thanks!
I have a similar problem with aokp jb, when it wasn't present before. The head unit shows my phone audio connects but the media audio does not connect sometimes. I would have to reboot my phone or fully disconnect my phone from the head unit and pair them again.. no real solution but it is slight work around and to say that you're not alone
Sent from my SGH-T989 using xda app-developers app
Teo032 said:
I have a similar problem with aokp jb, when it wasn't present before. The head unit shows my phone audio connects but the media audio does not connect sometimes. I would have to reboot my phone or fully disconnect my phone from the head unit and pair them again.. no real solution but it is slight work around and to say that you're not alone
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I've had to reboot or re-pair in the past every once in awhile, but neither rebooting or re-pairing is fixing the connection anymore. Anyone else had this problem? Are know if there is some sort of log I can find on my phone that might give some clues to why this is happening?
Problem Solved....
I tried my phone in a different vehicle, with a different headunit. No problems at all. I went through my head unit menus and found an option to clear all bluetooth data. I assume this clears all paired device information from the headunit. Everything works perfect now. Phone pairs fast, stays connected, and all functions are perfect. I hope this helps someone at some point.
Having an issue with no sound emitting from any audio output on the phone, but sound will play through Bluetooth-connected device. No sound from front speaker (phone calls, dial pad), no sound from rear speaker (notifications, ringer, alarm, media) and no sound from wired earpiece/headphones. Seems like it's stuck in Bluetooth/headset mode, but turning off Bluetooth doesn't restore sound. Problem is intermittent, haven't determined pattern to the behavior.
Phone was rooted long ago but kept stock ROM. Flashed Paranoid Android 3.99 RC2 about a month ago, and problem seems to have started shortly thereafter, but not sure if related. Haven't tried to reflash.
Any suggestions? Tried searches, but didn't locate this specific issue.
SGH-T999 (US/T-Mobile Galaxy S3)
Is it a T999 or a T959? And flash back to stock.using Odin. If it still is a problem it's likely hardware related.
Sent from my SGH-T999 using Tapatalk
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
yardsale said:
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
Click to expand...
Click to collapse
Did some more investigating last weekend before flashing ROM (never did the reflash).....seems that often, not always, if I turn off the car ('13 VW) while still connected to phone Bluetooth, the phone's sound quits working (all sound). Rebooting phone and turning off Bluetooth does not restore sound. The only solution I've found is to reconnect to car's Bluetooth, then turn Bluetooth off before shutting down car, and that only works about half the time, but sound is instantly restored. My estimation is that this wouldn't be hardware related, is that a fair assumption?
I also have a Tasker profile set up on phone to disable PIN lock when phone is connected to Bluetooth device (enables Sena Bluetooth headset used with motorcycle helmet to function properly), could that be causing the problem? Anyone else experience this issue?
Please try another Rom. Some of the Custom Roms may not be uptodate with CM Checkins. This issue was reported a bit back. There were CM Code Fixes that may not have been incorporated in that rom.
I am using Slimbean 2.0 (Android 4.3.1) and have seriously tested its bluetooth capabilities.
its also been reported thst msny car manufacturers did not bother to put any time or money into their BT capable systems. they just threw it together so they could add to feature lists.
Lots of peopke have problems with BT in the car, especially on cm roms. but those are notorious for BT issues to begin with.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Thanks for the replies. I flashed to Paranoid Android 3.99.1 RC1 but the problem still exists. I never had this issue with any of our vehicles, until switching to PA from stock ROM. If problem becomes unbearable, may go back to stock. Thanks again.
@yardsale
I should have mentioned in the previously. Please read this post of mine. Yes its a different Rom. However, here primarily the issue is that of hardware antenna of the T999 talking to the Car's antenna. Doc is 100 % correct, the manufacturers do use substandard Antenna. On that thread, someone else reported issues with two '13 VW for themselves and their brother's.
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?