I have a Cubot One, using the G800_CUBOT_D1_V0.8_20140124_MJK firmware (4.2.1) - it was previously on the 0.6 firmware and had the same issue.
What I have experienced is that when connecting to a device with Bluetooth - in this case a Sony SW2, but have also tried Bluetooth headsets - it has problems pairing.
The phone sees the BT device as an available device, and when I select it, it starts the pairing process. Initially it seems to be ok and successfully pairs for 2-5 seconds, the the device is relisted as an available device, but not connected. I have had success twice. The first time was immediately after rooted my phone, and this was ok for several days, even rebooting my phone and the watch didn't seem to cause the issue again, but then it randomly stopped working. I was unable to connect until flashing with the 0.8 ROM. At this point is was again working for about 24 hours - even better than before - until I switched the watch off. Since then I have been unsuccessful in pairing again.
Interestingly, when I try to pair with my Galaxy Tab 2 I have the same problem, UNLESS I initiate the connection with the tablet, then it is fine.
I know that there were problems with the Bluetooth stack on 4.2.1 when it first came out, and it may be related to that, but can anyone offer suggestions as to what else I can try?
I've been dealing with connection issue on my Asus Zenwatch 2 since updating it 2.0. Sometimes when I try to use Google Assistant it comes up with error saying "Can't reach Google at the moment." When this happens the watch will show Bluetooth is disconnected in the connectivity settings, however my phone shows it's still connected and I still receive notifications as usually. The only thing I can't do is use voice features. Now when I'm connected to Wifi works perfectly fine, it just happens mainly on a mobile data/Bluetooth connection. If I reboot my phone and watch the issue will correct itself for a while.
Things I've tried:
-Factory resetting at least 5 times.
-Wiping the cache through recovery mode.
-Factory resetting my phone.
My devices and builds
Phone - ZTE Blade X Max (Z983) - Android 7.1.1
Build Z983V1.5.19
Watch - Asus Zenwatch 2 - Android 7.1.1
Build NWD1.170706.001
I apologized if this isn't the place to post this here. I'm new here!
Just not sure if it's man issue on the watch or phone side. Any insight is greatly appreciated! Thanks.
I've had similar issues when music is playing. If I use my watch to pause the music, then voice commands start working again. Try playing/pausing music with your watch, then try using voice commands again.
I don't mean to revive a dead thread, but I too am having the exact same problem as OP
/me too.
Me too, Ticwatch E, so recent watch.
Hi all,
maybe this will help you. I have had the same issue. But it's solved now:
https://support.google.com/androidwear/thread/41855
I have a Galaxy Tab A 10.1 with stock Oreo. Not rooted (yet ) and probably going to put a custom ROM in soon.
I just bought an Innuevo Bluetooth keyboard (older - BT 3.0) and was able to pair it almost immediately. It worked fine, but when I went to use it again (after turning the keyboard off to save power), it wouldn't pair. I unpaired the keyboard on the tablet, and unfortunately the tablet's BT no longer detects the keyboard at all.
Have tried everything troubleshooting-wise: clear cache, reset network settings, off/on/scan a million times, different BT connection app... nothing. It simply doesn't see it.
My Windows 10 laptop was able to detect the keyboard and start the pairing, but crappy Windows 10 keep aborting the pair procedure (e.g., typing in the code) early. Then the keyboard also disappeared from the laptop's BT radar. (Event log has lot of BT low-power warnings in it so I'm thinking it's Windows being Windows.) The keyboard briefly appeared on the detection list but then disappeared after several unsuccessful pair attempts.
Any idea if there's a way I can totally nuke the BT (other than a factor reset) to see if it'll detect it again? Also wondering if using Lineage or a other AOSP/non-TW ROM would help.
Thank you!!!
Usually in my car this happens but every once in a while to any Bluetooth device. I'll try to connect and unable to pair repeatedly happens. I unpair and repair and the problem is usually solved.
Is there any idea on what can be done to make this easier? Clearing data and cache doesn't really seem to help either & I am looking for a permanent solution
My p6 will see most some of my Bluetooth devices (laptop, tablet, TV, earbuds) . It pairs with the earbuds, but everything else it will try and pair, usually does not. If and when hen it does pair, that pairing is dropped dropped within 5 secs. Cleared BT cache, rebooted. No joy. It will show no paired devices.
Network reset.
Clear system cache.
Hard reboot.
Do not factory reset; find to root cause as it will likely reoccur otherwise, eventually.
It may be a 3rd party app, try in safe mode.
Try rolling back associated apks to their factory load versions if updated.
Double check permissions and settings.
blackhawk said:
Network reset.
Clear system cache.
Hard reboot.
Do not factory reset; find to root cause as it will likely reoccur otherwise, eventually.
It may be a 3rd party app, try in safe mode.
Try rolling back associated apks to their factory load versions if updated.
Double check permissions and settings.
Click to expand...
Click to collapse
Thanks. Tried everything but the "roll back " . It will remain paired with ear buds and car, but laptop, desktop,tablet and phone all disconnect immediately
Tool Belt said:
Thanks. Tried everything but the "roll back " . It will remain paired with ear buds and car, but laptop, desktop,tablet and phone all disconnect immediately
Click to expand...
Click to collapse
You play with bt settings in Developer options?
Is power management active? This doesn't fit power management's profile for erratic behavior but maybe it got "smarter".
Played with BT in developer. I will give power a try, but I don't understand why the buds and car are seemingly 0k. I haven't the chance to be in the car for an extended period.
Tool Belt said:
Played with BT in developer. I will give power a try, but I don't understand why the buds and car are seemingly 0k. I haven't the chance to be in the car for an extended period.
Click to expand...
Click to collapse
Think about the clues.
Are the other devices configured properly?
Check Event Viewer in Windows for error messages, it might tell you why this is happening.
Try some Google searches for similar issues, it can be other devices and OS versions. Many issues span both. With a newer device this strategy works many times.
To see if power management is active Developer options>standby apps, all buckets should show as active, otherwise power management is running. It can't be disabled here though.
Power checks out. I tried to send a file from the tablet. Phone showed the attachment, file failed. Was able to send a file to tablet using "nearby device"
Tool Belt said:
Power checks out. I tried to send a file from the tablet. Phone showed the attachment, file failed. Was able to send a file to tablet using "nearby device"
Click to expand...
Click to collapse
Do it to the PC and see what error messages Event Viewer shows.
Sent file from lap top to P6. P6 paired and accepted. Closed send window on LT and P6 dropped connection. Sent another file and did not click finish on LT and P6 remains connected and LT acts as trusted device for Smart Lock. The purpose here is not having to get frustrated with the FP sensor while at home. Using Trusted Location enables an area with nearly a half mile radius
It's not just bluetooth, it has to do with the Wifi+Bluetooth implementation. You can reliably crash System Settings after a factory reset if you type a wifi password wrong on the same network more than once, or if you attempt to connect to the same network with an incorrect password too many times. Attached "proof" (not really proof but). Once it crashes it'll restart setup but won't let you continue past Network Setup.
I could not get my Android Wear watch (Fossil Gen4) to connect. It was seen once and tried to but the bluetooth stack crashed. Even after a reboot, settings reset, forgot the device, and factory reset the watch it would not work.
My Pixel buds connected via fast pair and "worked", but the phone refused to identify them as Pixel Buds and I could not use the dedicated settings app. Same thing with my Galaxy Buds Live, the Samsung Wearable app would not find the buds even when connected.
MichRT said:
It's not just bluetooth, it has to do with the Wifi+Bluetooth implementation. You can reliably crash System Settings after a factory reset if you type a wifi password wrong on the same network more than once, or if you attempt to connect to the same network with an incorrect password too many times. Attached "proof" (not really proof but). Once it crashes it'll restart setup but won't let you continue past Network Setup.
I could not get my Android Wear watch (Fossil Gen4) to connect. It was seen once and tried to but the bluetooth stack crashed. Even after a reboot, settings reset, forgot the device, and factory reset the watch it would not work.
My Pixel buds connected via fast pair and "worked", but the phone refused to identify them as Pixel Buds and I could not use the dedicated settings app. Same thing with my Galaxy Buds Live, the Samsung Wearable app would not find the buds even when connected.
Click to expand...
Click to collapse
This sounds similar to my problems. Try and contact support (took 50 minutes for a call back) and get it into their system.
Tool Belt said:
This sounds similar to my problems. Try and contact support (took 50 minutes for a call back) and get it into their system.
Click to expand...
Click to collapse
I'm sorry you're dealing with it I've since factory reset the device and haven't tried crashing anything, so things seem to be working so far. I have an RMA P6 on the way already due to terrible screen tint issues on my phone. Took over 3hrs (1hr waiting for chat to be available, 1hr in line on chat, 1hr on chat)
I may try a reset when I am bored. Gr8 you have a new one coming