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!
Related
I was wondering if anyone else is having issues with bluetooth on their Archos 101. I can't tell if perhaps my hardware is flaky, or if its a software issue.
Basically, bluetooth seems to work sporadically. Sometimes it pairs like it should, other times it is a fight just to get it to pair with my phone, laptop or bluetooth keyboard. Often times I have to reboot just to get it to pair and it seems to really struggle if both bluetooth AND wifi are enabled.
I'm running the stock current ROM and outside of the android market APK and some basic apps, I haven't done anything wacky or weird to it.
I guess I'm just looking for some validation and/or confirmation and/or possible fixes if any.
Sorry, i have experienced no issues with bluetooth apart from forgetting to switch it on
I have had some issues as well. Paired a set of Motorola S9 bluetooth stereo headphones. They pair and connect fine, but the audio is choppy. It will sound fine for 15-20 seconds and then it will skip, go silent, bring back audio, etc. Tried playing same audio through unit speakers and no problems. I also have an Archos 70 tablet and have no problems with the same headset. Both have been updated with the Froy 2.2. Starting to think it might be a hardware issue with the 101. Anyone have any other thoughts?
Never had it working
I always get paired but not connected. Never have been able to get it to work.
The same problem. Pair, but not connect!
I've never found problem about bluetooth (Archos 101 - firmware version 2.1.08)
Pair & connect with DELL BH200 (Bluetooth Headset) - work fine.
Pair & connect with DELL BT Travel Mouse - work fine.
i'm getting major issues on my new replacement 101. did you ever sort your issues? i'm using latest fw.
its really hit or miss (mostly miss) whether it actually see's any BT devices when it scans. yet wifi works fine 100%
I experiment something very similar with my 101, this both on standard Android and Urukdroid 0.7 or 1.0 :
- very difficult (multiple tries have to be done) to get successfull peering.
- with BT enabled phones
- with BT GPS (G-Sat BT-368i, wich is given in forums to work well on our gen8 devices)
- for the GPS (which is the BT device that interest me) : impossible to have it working directly from GoogleMap, I got some success with "Bluetooth Gps Provider" appli from Market). This device is never shown as connected from the BT Parameters.
Could it be a hardware problem, that is do I have to return the tablet to archos ?
Thanks for your experience feeling about the fiability of the BT on 101 tablet.
It generally works fine for me, but a couple days ago it got stuck, and it would not allow to send me files to other devices until I rebooted the Archos. The same day I was also using bluetooth headphones and the wifi network together, and I had audio stutter problems. It seems that wifi has a negative effect over bluetooth stability.
It works for me... though
Bluetooth is not working on my Archos 101.
When I try "scan for devices" it shows 1 or 2 devices, while my HTC HD2 shows about 5. When I click again on "scan for devices" - sometimes it is howing different device, sometime shows bloothooth adress only.
Evan my HTC can see Archos, it cannot pair with it. Archos never see my HTC.
Zalek
Same here
I can pair with my phone (htc desire hd) but cant connect.
I need my phone connected for gps.
Nobody has a solution ?
No solution ?
Thanks
BT has some issues for me too with an A43.
BT+wifi means i either can't get a proper internet connection, or BT devices disconnect.
quite annoying, because i want to be able to use my BT mouse with the internet browser.
and my jabra halo headset connects in dumb mode (no media/volume controls) most of the time.
which is annoying, because it means my headset is stuck on the volume i last used.
Hi Lara and other fellows! For me, after all sort of tries, the solution comes with full reinitialization. Plug the unit to AC outlet, backup all your data, go to settings, repair and formatting and full reini. It seems that when we update firmware the things go a little crazy with the bt side. Good luck!
Think I've sorted out bluetooth problems
I also have had real problems with the bluetooth on Archos 101 - pairing but not connecting, causing "Location & Security" to crash when I attempted to open it (in settings). I updated the firmware to 2.4.19 and then rebooted - still the same problems, so I did a full initialization and hey presto all problems seem to have vanished ! A pain because I've now got to re-download all the apps I had before but at least the tablet is working as it is supposed to.
Hope this helps others.
luiznaufel said:
Hi Lara and other fellows! For me, after all sort of tries, the solution comes with full reinitialization. Plug the unit to AC outlet, backup all your data, go to settings, repair and formatting and full reini. It seems that when we update firmware the things go a little crazy with the bt side. Good luck!
Click to expand...
Click to collapse
Hello
How can I backup all my data?
Thks
Followed your instruction however it is not work for me. I am running the last patch (2.4.19)
Thanks
luiznaufel said:
Hi Lara and other fellows! For me, after all sort of tries, the solution comes with full reinitialization. Plug the unit to AC outlet, backup all your data, go to settings, repair and formatting and full reini. It seems that when we update firmware the things go a little crazy with the bt side. Good luck!
Click to expand...
Click to collapse
It is not working for me.....
Archos 101 Bluetooth Problem - Known issue?
I'm having the same problems. I contacted Archos support and they told me to do a full reinitialization. This did not resolve the issue.
When scanning for bluetooth devices, nothing shows up until the 5th or so attempt.
The mac address of the discovered device is shown instead of the device name.
When attempting to connect it fails several times, then it pairs but says "paired but not connected."
When I finally connect the audio stutters. It's extremely choppy... useless.
If the bluetooth is left on, the 101 will eventually freeze when the screen sleeps and cannot be woken up by pressing the power button. The green light stays on when this happens. Pressing the button a few times or holding it in reboots the 101.
After reading all the posts I've come to the conclusion that Archos likely knows about this issue.
Archos, if you're reading this, for the sake of your customers, please admit this is a known issue and let us know if it's fixable and when a possible fix may be available.
I encourage everyone to open a ticket with Archos support.
If you purchased your 101 used and it's been registered by the previous owner, you can register it and the registration will be instantly transferred to you.
Create a support account at archos.com
After you create an account you can add products to your account and submit tickets for them.
Firmware: 2.4.81
Board ver: A101IT-V5
OMAP ver: ES1.2
Boot ver: Unknown / 4.04.000000
My bluetooth device: Jensen WTB210. Works fine with several other android devices.
Hello all.
I am having some bluetooth connectivity problem with my moto g 4 US xt1625 Retus channel (non amazon version) stock everything.
Basically the connection to my smartwatch is unstable and keeps dropping on and off.
Normally I would be blaming the smartwatch for this BUT it connects absolutely perfectly to my moto G2 (cyanogenmod 14) without any hint of misbehavior
I've already tried;
Forgetting and re-pairing device (also rebooting phone before repairing)
Factory resetting watch
clearing app data and cache of system bluetooth apps ("bluetooth share" and "bluetooth MIDI")
Disabling 4G (sometimes interferes apparently)
Disabling wifi
Running phone in safe mode.
*edit - also tried disabling power optimisation for both system bluetooth apps AND the watch companion app
I also reconnected my smartwatch to my old moto G 2 after trying all these things and it still works perfectly.
Old moto G2 had blutooth 4.0 LE and this moto G4 has bluetooth 4.2 LE which would offer no comparability issues.
Has anyone had any similar problems with their bluetooth?
Thanks in advance
I think my next move will be to root, and start removing G apps that could be interfering with the bluetooth connection
hotdog18882 said:
I think my next move will be to root, and start removing G apps that could be interfering with the bluetooth connection
Click to expand...
Click to collapse
I have had a problem with my Fitbit connecting that didn't happen on my G2 or G3. I keep my cordless home phone connected with no problem though. What I have to do is forget the Fitbit in my bluetooth devices and it connects fine. If it's even showing up in the bluetooth devices it won't connect. That seems strange that it will only connect that way but others have reported the same thing. Maybe try and see if it connects after you forget it in the bluetooth settings and it's not even showing up.
Sent using XDA-Developers Mobile App
Tel864 said:
I have had a problem with my Fitbit connecting that didn't happen on my G2 or G3. I keep my cordless home phone connected with no problem though. What I have to do is forget the Fitbit in my bluetooth devices and it connects fine. If it's even showing up in the bluetooth devices it won't connect. That seems strange that it will only connect that way but others have reported the same thing. Maybe try and see if it connects after you forget it in the bluetooth settings and it's not even showing up.
Sent using XDA-Developers Mobile App
Click to expand...
Click to collapse
OK maybe you're on to something.
If I connect to the watch using the companion app, then enter bluetooth settings and "forget" the device..... It still appears to be connected
But a few seconds later, it automatically pairs and re-appears in the "paired devices" list.
Is there a way to prevent re-connect?
Actually, after "forgetting" it several times, It's staying connected and has done for a 15 minutes now.
I'll report back if and when it disconnects.
Cheers
Ok so the watch disconnected a couple of times in a few hours. (this is a huge improvement from before)
Each time, "forgetting" the watch in bluetooth settings caused an automatic re-pair and return to good connection.
Maybe I can use "tasker" or similar app to automate this unpair upon disconnect?
Cheers
hotdog18882 said:
Ok so the watch disconnected a couple of times in a few hours. (this is a huge improvement from before)
Each time, "forgetting" the watch in bluetooth settings caused an automatic re-pair and return to good connection.
Maybe I can use "tasker" or similar app to automate this unpair upon disconnect?
Cheers
Click to expand...
Click to collapse
Yeah, it's strange that it works that way. I think it's the device not compatible with that version Bluetooth. My Fitbit doesn't try to reconnect once I forget it unless I make it pair then it will actually work sometimes and sometimes it doesn't when paired. It always works if I don't pair it at all. Have you tried clicking on the gear besides your watch in more settings once it connects and unchecking what ever connectons it shows in the check boxes?
Tel864 said:
Yeah, it's strange that it works that way. I think it's the device not compatible with that version Bluetooth. My Fitbit doesn't try to reconnect once I forget it unless I make it pair then it will actually work sometimes and sometimes it doesn't when paired. It always works if I don't pair it at all. Have you tried clicking on the gear besides your watch in more settings once it connects and unchecking what ever connectons it shows in the check boxes?
Click to expand...
Click to collapse
If i click the gear next to the watch in the bluetooth settings, the only options i have are to rename the device, or to forget it
I have no checkboxes or anything like thar.
Do you have advanced bluetooth settings installed or something???
hotdog18882 said:
If i click the gear next to the watch in the bluetooth settings, the only options i have are to rename the device, or to forget it
I have no checkboxes or anything like thar.
Do you have advanced bluetooth settings installed or something???
Click to expand...
Click to collapse
Some of my devices have check boxes for contacts, audio, etc. but not all. I thought maybe that would be something to look at.
Sent using XDA-Developers Mobile App
Ok, its still messing around. I'm going to install the Temasek unofficial cyanogenmod 13 and see if that is an immediate fix, or if the additional options offers a fix.
Cheers
update;
after ugrading moto g4 to android nougat (7.0.1) I no longer have any issues with bluetooth connectivity.
6.0.1 was to blame!
my phone is updated to stock Nougat also and still having bluetooth issues staying connected to my car (2012 ford fusion with mysync) I will be keeping an eye on this thread.
vrm4 said:
my phone is updated to stock Nougat also and still having bluetooth issues staying connected to my car (2012 ford fusion with mysync) I will be keeping an eye on this thread.
Click to expand...
Click to collapse
I seldom connect my phone to mysync but my wife does. She also keeps her G4 connected to the Panasonic home phone system while home. I've noticed that since the update to Nougat mysync is very slow to connect on her phone. The Panasonic cordless phone seems to connect fine. Mysync will usually connect although she has to drive for 10 or 15 minutes before it does occasionally and other times it connects instantly. One time I had to delete her phone in the car and add it back. I wondered if it was a problem of it not disconnecting from the Panasonic, but that shouldn't be past the end of the driveway. Then again it may be just a rip in the space time continum. ?
Sent from my SM-T530NU using Tapatalk
I got a new MOTO 4G Play to replace and older Samsung. I like it except for one thing. I have to unpair ("forget") the device and then cycle the radio on and off a couple times and then turn on the adapter and then pair and connect to get it to work. I have to do this each time.
I've contacted that adapter mfg and moto they both point to each other. They even said a new pone won't likely fix the problem. No one is actually interested in solving the problem. I'm sure there are plenty of others in the same situation. The adapter mfg says it is a problem with moto phones.
Are there any bluetooth radio hacks or other versions. I don't know what radio I have or how to find out. I'd rather not go with a complete custom ROM at this time.
Any suggestions on what the problem could be, how to fix, how to address compatibility problems when both mfgs say the other is causing the problem. Is there somewhere to officially complain about BT compatibility issues? Is BT an industry standard or a specific company that licenses it?
It seems like I should have some recourse here, but, so far I've spent a lot of time going in circles dealing with level 1 support people who only fill in forms or read off lists as well as time and money spent on phone calls, being put on hold, etc.
While Bluetooth is an industry standard, there are different versions (3.0, 4.0, 4.1, etc.) which transmit data in different ways. There are other standards as well, such as A2DP. But for all of this to work, both devices need to be able to detect each others' Bluetooth MAC and store it long term. If one device forgets it has that knowledge, then it won't recognize the others' BTMAC at all.
Changing to a ROM isn't going to fix this (Lineage is notorious for killing BT when you change from cellular to WiFi, and to this day it still isn't completely fixed). What I recommend is going into Apps, looking for Bluetooth Share, and clearing its data. Then try re-pairing to the device.
I tried clearing the data as you suggested as well as during a hard reset and that doesn't work.
I do have a sequence of steps that works pretty consistently, but, I have to do it interactively. I'm wondering if I could just write a script to do these steps. Some of them like the pairing and the connection take a little time and may need some timing steps. Ideally it could access a signal when the connection is made or not made etc. I could just set it in motion and go about putting on the seatbelt, starting the car, etc while it is working.
I have no idea what commands the different things I interact with use. It involves forgetting the connection, cycling airplane mode on and off, pairing and then after they are paired connecting. Any ideas?
Some people on the Moto forums suggest disabling Bluetooth Scanning. It seems to work for some people; others report no change in their connection after turning it off.
I'm running LineageOS, and as the previous reply stated, my Bluetooth restarts when changing between WiFi and cell data. I tried Bluetooth scanning on and off, and neither seemed to fix the Bluetooth restarts.
Hello to everyone.
From when i bought it the op8pro has some problem with the bluetooth. Is like if the device can connect to one device only. I have a fossil 5 gen, one fiesta mk8 with android auto and the bluetooth headset but is like if the bluetooth has some problem to connect to two or one devices. For example every time my car doesnt connect to the phone automatically and today when i was to the gym my headset doesnt connect automatically too. My previous note 10 pro was able to connect without any problem... Someone has some problem with the bluetooth? Thanks
I have another problem. Every time that i enter in my car the device is connect to android auto but if i want to play an audio from whatsapp i have to tap a lot of time on the play botton.!!!???why
I see this same issue, I'd say 80-90% of the time (the other 10-20%, it "just works", which is truly odd, given the protocol).
For example, I use some bone-conducting open-air headphones, while cycling (long time road cyclist), and sometimes I want to connect my Garmin Edge 1030, to download a route, when I'm out.
Good luck, even upon returning, I'm often sitting in the garage, trying 20+ times (after shutting my headphones off, even), to try and download my ride-data, for the day. Sometimes it requires rebooting both devices, flushing the Bluetooth app-cache, and the Garmin app-cache, and then it'll work, that's perhaps 40% of the time.
For another 40%, it will NOT connect, what-so-ever, across multiple reboots and app-cache flushes, period (I tend to give up at around the 20+ attempt mark, depending).
The last 20%, it works, perfectly, as you'd expect, and as my OP7 Pro did, I can't recall a single BT connectivity issue, with it, either solo (Garmin) or with headphones concurrently.
I've filed bugs with OP (along with NUMEROUS other radio bugs, like the fact you can't connect to a 5G-mobile signal, if you're connected to a WiFi signal, on the INO2025 model, bug filed, trace-logs submitted, including pointing out log-lines where the radio(s) fail).
Unfortunately, with the Bluetooth issues, it will not repro, if I use the OP debug-mode, which is how they want to receive logs (and how I've submitted many bugs, previously), so I'm at a loss, short of finding a hardware Bluetooth debug module (I used to work on h/w and s/w boundary driver stuff, so I've used a h/w BT debugger before, but not for some years, and have no access to one, currently).
OP seems to just ignore the bugs, at that point, when I can't provide the logs, they pretty much abandon the bug-thread, so I'm not sure how they're going to get some of these resolved (I've noted that the debug-mode seems to introduce some latency, or similar, that prevents repro, no response to that, what-so-ever).
I have reset the radio-stack, a couple of times, and did one full factory-reset (shortly after getting the phone, about 1 month back now), with no real change in results, for reference.
I feel like I'm back in the late-90's, when Bluetooth was super-flaky. on most devices, in the 1.x and 2.x days.
Not exactly a "flagship phone experience", or even a decent budget phone Bluetooth experience, for this day and age...
I'm open to ideas on how to debug further, I'm really more of a storage and display guy, and memory-management, in terms of the bulk of my dev/debug skills, communication protocols were something I did on the fringe, of sorts, when they overlapped, or similar.
I have an Atoto S8, and this is my first Android powered head unit (coming from their linux-based F7, which was more of an appliance UI instead of a smart OS). I love the extra functionality it gives me, running apps and video players directly on the unit. But Bluetooth support is wonky.
My wife and I share the car, and ever since swapping to the Android powered unit, it only reconnects to whoever drove last. So if I drive the car all the time, its fine. But when my wife drives, she says bluetooth isn't working, so I have to go into settings on the BT app (BT1 as they call it) and see the three phones listed as paired (my old phone, my new phone and my wife's phone), and click on hers. Wait a bit, and then she is good to go. But then next time I drive, I realize my phone isn't connecting now, so I have to go do it again. Which means she's going to complain next time that her phone isn't working again.
I've installed a few bluetooth powered head units before, and even the Android Auto supporting F7 before this one, worked as expected: If the last device isn't available, try to connect to another recent paired one. It seems to just get stuck on the last one for some reason. Is this a limitation of how bluetooth works on these units?
have you solved this issue
i am finding it very frustrating
i thought i would solve it using the app "automate"
this would star a sequence of checks and sytematic attempted connections
but, oddly enough you cant automate the triggering o fthe flow
so it would only start if actioned
Yes, or rather THEY solved it.
Reach out to customer support. There is an update to the Bluetooth module that makes this work the way I described.
I got an A6pf in my other car and had them make an update for that one too. Much happier now.