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, 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 with each other. 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 (and whose urgency to make them work together is greater than mine) 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.
Same exact problem here with my Nexus 4; rooted, stock ROM, no problem paring with Bluetooth, but unable to connect. I just noticed this today when I was trying to connect to my OBD2 device. This has worked since I bought the phone a year ago. I only use one app, and not very often, so I can't pinpoint the exact time the problem started, but I am pretty sure it would be in the time-frame of the 4.4.3 or 4.4.4 update. I also tried rebooting, re-pairing the hardware with the phone, enabling and disabling Bluetooth, etc..
pjc123 said:
Same exact problem here with my Nexus 4; rooted, stock ROM, no problem paring with Bluetooth, but unable to connect. I just noticed this today when I was trying to connect to my OBD2 device. This has worked since I bought the phone a year ago. I only use one app, and not very often, so I can't pinpoint the exact time the problem started, but I am pretty sure it would be in the time-frame of the 4.4.3 or 4.4.4 update. I also tried rebooting, re-pairing the hardware with the phone, enabling and disabling Bluetooth, etc..
Click to expand...
Click to collapse
Thanks for the commentary, pjc123. At least someone said something.
I restored one of my Nexus devices to stock 4.4.3, then 4.4.4. Didn't change anything. Maybe I need to take a couple of them back to 4.4.2 or earlier and see what happens. But AFAIK, my friend who has the same problem hasn't ever even updated to those versions of the OS. And it worked fine for him, doing these Bluetooth connections on no less than a weekly basis for a year.
Google's tech support, fwiw, told me that the first thing I needed to do was to update to 4.4.4. Not that I took that as anything other than their reading off a script.
Please let me know if you ever figure anything out with this. I'll report here if I do, too.
Well, as it turns out it was my fault for not checking the Xprivacy security settings; I am brand new to that app. After wasting a good part of the day, I discovered that the Torque app for my OBD2 reader needs both "Identification (device)" and "Network(addresses)" permissions for the Bluetooth device to show up within the app so it can be connected to. Once I gave those permissions it was back to working OK again.
pjc123 said:
Well, as it turns out it was my fault for not checking the Xprivacy security settings; I am brand new to that app. After wasting a good part of the day, I discovered that the Torque app for my OBD2 reader needs both "Identification (device)" and "Network(addresses)" permissions for the Bluetooth device to show up within the app so it can be connected to. Once I gave those permissions it was back to working OK again.
Click to expand...
Click to collapse
Interesting. I temporarily turned XPrivacy off just for that purpose. The app that's failing for me wasn't being protected, anyway, but it doesn't matter. I can't even get to that point, because the devices don't connect, even though they're paired. Furthermore, only one of my devices even has XPrivacy installed. I can't get any two of my, or my friend's, Nexus devices to connect, even though they're all paired. And they all used to.
I'm waking up this thread again to see if anyone has any ideas. I just can't connect two Bluetooth devices anymore by using the list of Bluetooth devices in settings on a Nexus device. This prevents an app that's dependent on that from working.
I CAN connect two devices via Bluetooth using ES File Explorer and see the contents of the other device and make file transfers. But the Bluetooth icon remains unlit and the connection isn't made in the settings. Maybe it's a different aspect of Bluetooth. When I close the connection with ES File Explorer, the toast says that the OBEX connection has been discontinued.
Why would I be able to connect two Nexus devices regularly for a year, then not be able to anymore?
I've tried to get Google support on this. Unlike some companies who provide inept support, even laughably so, Google just blows off the notion altogether.
Some months later...
This problem remains unresolved. I've now tested this on multiple devices (about ten of them) running various different versions of Android. I just tried it today with another, a stock, factory state N4 trying to connect to a stock, factory state N7 (2012). I wiped the devices, reinstalled the OS and then tried to pair and connect as the very first act on the clean systems once I got past the initiation routine.. I even loaded a few different versions of Android from distant past (4.2) to present. I CAN NOT connect two paired Android devices using Bluetooth, even if they're successfully paired and Bluetooth is turned on for both devices. All these devices connect fine with things like external speakers and cars. I've shown this to Google employees, some of whom have tried it on their own devices. Nobody succeeds.
As mentioned earlier in the thread, this used to work every time on every set of paired devices, regardless of the Android version.
What could possibly be going on here?
I struggled with this for awhile today. Same symptom: the devices can pair, but will quickly go from "Conecting..." to "not connected". I eventually stumbled on the solution: one device must have internet tethering enabled. This setting is in the "Tethering & portable hotspot" section, not in the bluetooth settings. This will enable the two devices to connect, and it will also enable the second device to use the "Internet access" feature in the bluetooth configuration for its connection with the first device. Hope that helps!
I am coming from a long history of HTC use and so I apologise if this question has an obvious answer.
Previously, if I wanted to connect to my bluetooth in the car (previously paired with), I would just hit the bluetooth button in quick settings to turn it on and that was it, just like connecting to wifi.
If I do this on my S7E, I then get another screen popping up that tells me my device is visible to others and lists previously paired devices for me to select from, and then I have push the back button to leave that screen?
Is there a simpler way as I used to do on my HTC?
cheers
C.
PS - I am sure this will be the first of a number of questions as I get used to TouchWiz and Marshmallow......Sorry.....
crazyC said:
Previously, if I wanted to connect to my bluetooth in the car (previously paired with), I would just hit the bluetooth button in quick settings to turn it on and that was it, just like connecting to wifi.
Click to expand...
Click to collapse
Have you ever *paired* your new phone with your car?
I've only had two cars with BT in them, but in both cases the car and phone had to be paired before they would work together.
Once that was done then it would work as you expect.
Specifics of getting your *car* into pairing mode I can't help with, but once you do that you should be able to select it while scanning from the phone (as you've seen already the phone will list devices it finds) and you can finish walking through the pairing.
C0derbear said:
Have you ever *paired* your new phone with your car?
I've only had two cars with BT in them, but in both cases the car and phone had to be paired before they would work together.
Once that was done then it would work as you expect.
Specifics of getting your *car* into pairing mode I can't help with, but once you do that you should be able to select it while scanning from the phone (as you've seen already the phone will list devices it finds) and you can finish walking through the pairing.
Click to expand...
Click to collapse
Oh yes, it was paired with the bluetooth fine (its actually a visor BT device, not the car itself), and when I turn on the BT it shows up on the list of previously paired devices)
Don't have to make it a trusted device for it to auto-pair?
Why turn Bluetooth off at all?
Just leave it on.
Regards,
Dave
Sent from my Nexus 6P using Tapatalk
neezy13 said:
Don't have to make it a trusted device for it to auto-pair?
Click to expand...
Click to collapse
Nope, just had to be paired.
Trusted Device brings in the Smart Lock stuff, which enables the option of having your phone NOT authenticate you (pattern/pin/finger/passwd) when connected.
For example, I have my car bluetooth set as a trusted device so that when I'm driving I don't get any identity challenge to use the phone (like for navigation), the screen will just come on as requested.
Smart lock is blocked by my exchange administrator as I get my work emails on my phone.
I turn the Bluetooth on the phone off because I don't turn the one in the car off and it's just outside the house and will stay connected.
Sent from my S7 Edge
I have a retus version on stock ROM (non-Amazon). I have 5-6 BT devices connected (Moto 360 watch on persistent, some headsets, headphones, speakers, car, etc.). They are all different brands (Plantronics, JBL, Taotronics, etc.). Almost every time I use a device and then it off, after awhile when I try to connect another device it won't connect. Then I need to reboot phone before it will connect again. Not every time, but most times. Just turning off the BT on phone and back on used to work sometimes but doesn't now. Anyone else have this problem and any suggested fixes? Thanks.
Has your phone done any updates, security patches etc, used to have to remove all previous Bluetooth items on my samsung, then reboot and add them back, before they would automatically reconnect, could be the same for moto.
Ray
Did anyone find a way to make device not request fingerprint when paired with set BT device as google devices do? I think it is called smart unlock maybe.
I have a problem with pairing Bluetooth components.
In the smartphone we recognize the CarKit immediately and can then be connected via the PIN code smartphone side.
My problem is that I can't connect any other hardware to the CarKit.
Devices such as cash terminal, printer, or headphones are displayed in a list, but cannot be connected to the CarKit.
I despair. because I simply need certain components.
Maybe someone can give me a tip on how to solve the problem.
Have other car systems in operation where this is not a problem.
The Bluetooth hardware we recognized by the K1.
However, no connection can be made.
There is no possibility to enter the pairing code.
Why is this not possible with the K1?
What does reseller suggest when contacted for support
The seller says my devices will not be supported.
However, the devices are listed via BT.
(first photo)
However, there is no way to connect.