Just got a Robin to replace a N5X that was killed while on vacation in MX. The bluetooth pairs just fine the first time to all four of the bluetooth devices I routinely use. Despite them now being listed in 'Paired Devices' none of them will automatically connect to the Robin. Each acts as if its the initial pairing again, asking to be included as a trusted source, and the device being connected to requiring a confirmation on the pairing. And even then getting them connected again has about a 50% success ration (if that). The N5X never had issues automatically connecting to the same four devices. Is this a known bug and is there any work around?
***UPDATE***
Well, nothing I've tried could make bluetooth work properly on stock 7.1.1. Deleting all paired devices, factory reset, you name it. Fed up, I decided to flash Omni Rom and now bluetooth works as well or better than any device I've owned. As such, it's definitely a software issue with stock 7.1.1.
Related
Situation:
I'm using a Xlink bluetooth gateway in my house to connect my phone with and I also have a Mazda CX-5 with integrated Bluetooth system with the latest update from TomTom and Mazda. In the Mazda, I use the Bluetooth mainly for the phone, but occasionally use it to stream audio.
Phone:
T-Mobile samsung S2 x SGH-T989D with ICS 4.0.4 (Rogers leak)
Issues:
At first (With official Gingerbread)... everything was working fine. Both device paired and all functionality worked.
Then, applied official ICS update from Kies software ICS 4.0.3 and Bluetooth issues started. I first paired my Xlink device. So far it worked. Then tried to pair my Mazda, everything was really slow but managed to have it work. Turn the car off, get back in the house and the phone is now able to pair with my Xlink device, but cannot connect as a phone audio. Even if I go manually in the Bluetooth menu and try to activate the Phone audio it wont work. Only way to have it work again is to unpaired the Mazda and reboot.
After reboot, the phone works great in the house with my Xlink device. Going back to my car and try to pair my Mazda. Same issue. The phone does pair with the Mazda, but I'm unable to make a call since the phone cannot activate the Phone audio.
Look online and have tried the ICS 4.0.4 (Rogers leak) and same issue with Bluetooth.
The only way my devices works perfectly is when I only pair with one device at a time. There is something happening when you pair more than one device, even if not both device are turned on or in range.
Anybody got the same issue or a fix to that?
Thank you and sorry if my post is a little long... but that issue is the only thing that make me not enjoy my phone.
I'm working with a Nexus 7 (2013) and a Nexus 4. I've had both devices for quite awhile, the 4 for well over a year and the 7 for a year. Both are rooted and using stock ROMs. The 7 is still on 4.4.3 and the 4 on 4.4.4.
I have the two devices Bluetooth paired and sometimes connect them. For the most part, over the last year, there have been no problems doing that. Once in awhile, they won't connect, but if I reboot, they will. Now, all of a sudden, I can't get them to connect under any circumstances. They're paired. But they won't connect. They both connect to an external Bluetooth speaker and the phone connects to my car bluetooth. That happens with 100% reliability. But these devices just won't connect. And I need them to for certain work related purposes.
What could have happened?
I've unpaired and repaired them a few times. I've rebooted both devices. Potentially competing Bluetooth devices (like my car and the speaker I mentioned) are turned off. The devices aren't connected to any other Bluetooth devices.
Strangely, someone I work with who's doing the same sort of thing with the same exact devices as I am is having the exact same problems.
What could be going on? Please let me know if you have any ideas.
Thanks.
I am unable to connect to any of the bluetooth devices I previously used with my Samsung Galaxy S3. I have a stock, unrooted 5X and I am updated to the latest software. The devices can still be connected to on other devices, including an iPhone 5S. Does anyone know what the issue might be? I have tried toggling the bluetooth and restarting the phone multiple times. It usually does not even detect the bluetooth devices. I think something may be wrong with the phone's bluetooth.
Hey guys,
since I bought my bluetooth headphones (Wearhaus Arc), which are actually pretty cool, I have lots of troubles with them.
When I paired my phone (HTC One M8 running latest official stock unbranded Android 6.0) with the headphones the first time, everything was great.
While using them from day to day I was faced with connection issues. That means, that both my phone and headphones are on, but it takes (almost everytime) a couple of tries to connect them. Even if I tap in the saved devices on the headphone, the connect could not be established. Turning off and on the headphones and bluetooth on my phone was the only way to fix it.
If I finally had a connection, everything was fine. In a few very rare cases, the connection worked at the first go.
Some weeks ago, a new firmware for the headphones was released, so I wanted to install them. During the update process, the updater (Android app) said, that the verifcation failed and the firmware cound no be updated. Same behaviour with the Windows 10 app. Even with another phone it did not work. Seems like, something is wrong with the headphones.
So I contacted the support again (first time they gave me the advice to use the Windows 10 app to update firmware) and told me, that I have to return it for repair. The gave me a return label etc. and I sent it back.
After waiting a few weeks I finally got it back. With zest I turned them on, but the joy was marred, because my phone did not recognize them.
Before sending them back, I unpaired the headphones in order to start over with the new ones. Maybe this was the mistake...
I did some pairing testing with other phones (HTC Sensation, BlackBerry Q10, HTC HD2), which found the headphones immediately and worked fine. So my guess is, that only my M8 has a problem with them.
Pairing, unpairing and "repairing" (pairing again) between my M8 and the other mentioned phones worked well, so there cannot be an general bluetooth issue.
After doing a factory reset on my M8 I'm a step futher, because now the phone sees the headphones (somethimes), but it isn't able to establish a connection. In case I see it, I tap on the available devices, the phone tries to connect, but a second later I get the message: "unable to pair. Make sure your devices are on and discoverable, and then try pairing again". Rebooting the phone does not work. I also cleared the data and cache of the bluetooth share app and performed a network reset like described here: http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-bluetooth-wont-android-6-0-t3340279
My question to guys is, what can I do, to get the headphones to work?
Is it possible, that on the phone is still a piece of information left about the former connection, which refuses any new connection?
Is there a file on the phone, which stores the bluetooth connections? if yes, maybe deleting or editing the file could help?
Thank you in advance!
@@RON
Anyone an idea?
Sent from my HTC One_M8 using Tapatalk
Ever since installing the September update I have had troubles with Bluetooth connecting and staying connected to my Galaxy Watch 3 and my hearing aids. Everything worked flawlessly until that installation. Is this a known issue or has anyone else observed this?
Quite the opposite for me, this update has made my phone more reliable to Bluetooth connections.
My BT headphones disconnect all the time. I think my Fitbit does too
With A13, the Bluetooth stack used by Android was changed. I saw some issues early on (problems pairing, needing to forget and repair, pairings simply disappearing), but after redoing some pairings, things seem to be getting better. Still some odd stuff, like impossible options enabled (like "Input Device" and "Contact Sharing" on speakers without that capability).
It's obviously a work in progress.
As mentioned above by Mike, I did also do a fresh start no restore for Android 13 since I thought I was having issues with other things that was really annoying me with android 13 after upgrading to that, all the problems that caused me to fresh start were still present but almost all of these have gone after Sept update