Does anyone else have this issue? I have a stock Moto X on 4.4.4. I use it at work with a bluetooth LG headset and up until a few weeks ago never, ever had a problem with it. I cant pinpoint when it became to happen, if I had to guess Id say a month or 2 ago, it got to the point where I literally have to keep the phone in my pocket to get a clear bluetooth connection. Now, its to the point I cant even do that. I have to have the phone right in front of me, unobstructed, to get a clear stream. If I walk away from it 2-3 feet it gets terribly scratchy and the audio cuts in and out.
I began to think maybe the headset was going bad. I got out my old Bionic and found I have no issues with the headset. I can walk 30+ feet away with it connected with clear stream. I just bought a car with bluetooth connectivity and also have problems with the bluetooth crashing on the phone, yet my kids phones connect with no problem.
Ive googled the issue and only found a few people that seem to have the same problems. They said it seemed to have happened with the latest update to 4.4.4. My phone shows the last update was August 1. Thats coming up on 3 months ago, that seems a little long ago when the issue first started, but I know Ive been dealing with this for at least 6 weeks. Its possible it has been 3 months.
I have cleared the cache in recovery mode, no help. Short of doing a factory reset I dont know what else to try. One person that had this issue did a factory reset and said it didnt help. So I dont necessarily want to wipe my phone to find out it didnt fix it.
Was hoping the update to 5.0 might fix this, but who knows when thats coming, especially on Verizon.
Any suggestions to this issue?
Reset device or full wipe do not help. Phones not see watch. Please help!!!
Go in parameter to enable ?
Where to look? I can not find.
With the screen on, hold the button in. That will bring up different settings
fr0st420 said:
With the screen on, hold the button in. That will bring up different settings
Click to expand...
Click to collapse
The first paragraph of brightness. The second device. Item no bluetooth. Paragraph device shows "Bluetooth is currently disabled"
Check if Airplane mode is not activated in parameter.
dersie said:
Check if Airplane mode is not activated in parameter.
Click to expand...
Click to collapse
I have the same problem. All started with the HTC One M7 problems with no audio during calls.
Did Full Wipe on the phone, reinstalled, finally got it working but couldn't connect the watch to Android Wear.
Restored Android Watch and data with Titanium but still nothing.
Finally read that you have to reset the watch. Did that and now I'm stuck on the "Install Android wear on your phone" screen.
I've tried connecting to the watch with different phones without any success..none of the phones sees the watch.
If I push the crown I get the settings page with only the following options:
Adjust Brightness
Bluetooth Devices - which shows: Bluetooth is currently disabled)
Always on Screen
Power off
Restart
Reset device
About
no place to check the airplane mode...nothing.. It's like there should be a "switch" to start the bluetooth somewhere..
any ideas greatly appreciated. For the moment I have a nice black thing on my watch which isn't doing anything..
[email protected] screen
If don't works with any phone maybe it is time to RMA ?
dersie said:
If don't works with any phone maybe it is time to RMA ?
Click to expand...
Click to collapse
RMA? What does that stand for?
[email protected]
depeche101 said:
RMA? What does that stand for?
[email protected]
Click to expand...
Click to collapse
I have exactly the same problem. If you frequently press device. Bluetooth is activated for 3-5 minutes. Watch are charged watchfase. That's all. Off. :crying:
RMA Return Merchandise Authorization
Not variant. Ebay shop.
Same Problem
I am having the same problem. Right now my LG G Watch R is useless. I wonder if it was on airplane mode before I factory restore it and that is what is causing the problem.
taastar said:
I have exactly the same problem. If you frequently press device. Bluetooth is activated for 3-5 minutes. Watch are charged watchfase. That's all. Off. :crying:
RMA Return Merchandise Authorization
Not variant. Ebay shop.
Click to expand...
Click to collapse
my case exctly... nice black piece...
The problem of overheating.
Harvesting hours in the refrigerator for 10 minutes.
Gat. Bluetooth works. Has not yet warmed up.
Then off again.
taastar said:
The problem of overheating.
Harvesting hours in the refrigerator for 10 minutes.
Gat. Bluetooth works. Has not yet warmed up.
Then off again.
Click to expand...
Click to collapse
BUMP
Anyone? No ideas whatsoever?
I did try the fridge thing...Worked once so I could pair the phone but didn't even sync.
Tried again with no success.
dep
Well I have an update. I honestly don't know what has changed...but my watch works again. Having the occasional connection lost problem as reported by many in the new 5.0 update in the watch but nothing too serious.
Anyway, reset your watch. Forget the watch in the Android wear app (or delete data and clear cache), but also delete the paired watch from the phones bluetooth menu.( BTW: I deleted all my paired devices in the phones bluetooth menu and then paired the watch first, don't know if this affected or not, if all else fails you can try this also).
Then turn off bluetooth from your phone. Start Android wear app and let it turn on bluetooth. THis way I can pair my phone. Whenever the watch loses connection to the phone and doesn't reconnect toggle bluetooth off and on from the phone and it works again.
Perhaps it's because the watch is already on Lollipop and the phone not yet...
dep
depeche101 said:
Perhaps it's because the watch is already on Lollipop and the phone not yet...
dep
Click to expand...
Click to collapse
I haven't had any issues and my T-Mo G3 is still on Kit-Kat.
Best practice if pairing gets wonky or whatever, is exactly what you did. Clear / Forget all pairings. Turns everything off. Turn phone on, enable BT, run Android Wear, turn on Watch - wait - follow regular steps and everything should be golden.
If it's still not working, try a reset on the Watch - if it's still won't work, RMA or take it back to the place you bought it from.
depeche101 said:
.
Perhaps it's because the watch is already on Lollipop and the phone not yet...
dep
Click to expand...
Click to collapse
I'm on lollipop on both watch and phone and getting constant disconnections
I will say that my rom is a leaked version of lollipop from Samsung on my note 3
But to date since Xmas it's been a joke
To the point that it might be going back if it doesn't get fixed in the next few days
I am going to go back to official kit kat later and see if that helps
I must say before the lollipop update on both watch and phone it worked brilliant not one disconnection when I trialled the watch when it was first delivered.
If it had been like it is now I would have sent it back there and then
I'm just hanging on because I know it did work prior to the updates
So I'm sure it will again
Hi Experts , after the latest update to Android wear, my watch worked almost fine the whole day but then suddenly the display become distorted - have rebooted the watch multiple times but of no avail.
Thou the watch was connected but was useless as i cant see anything. I then unpaired it hoping that a factory reset might fix but that didnt help either. I suspect the display has become faulty or some other hardware error --- your thoughts please?
Image here
https://goo.gl/photos/DLQTs44MzUNus35cA
Regards,
Junaid
I would try to flash the latest firmware image again. If that doesn't work it might be time to claim under warranty.
After the update a few issues have risen. I've attempted to search for solutions for each one, with no avail.
These are issues that never happened before the update, and started right on the next day.
1. Audio apps close when locking the screen.
When I have a podcast running (on beyondpod) and I lock the screen from the off button, the app will either keep running, or close.
I have found a few questions like this on here and other forums, but none with a definative answer.
I've done a few of the suggestion, like cleared the cache. But is there an actual solution to this?
2. Bluetooth turns off/loses connection to my pebble 2. I think these might be connected.
While using a bluetooth headset, there are no issues. However I constantly (should) have my pebble connected to my phone. However, very quickly it loses the connection. It randomly finds the connection again randomly, but it wont stay connected for very long. Sometimes I catch my phone with the bluetooth turned off, however turning it back on wont neccessarily connect it to the pebble. I also tested out with IFTT, and everytime the phone cut the bluetooth connection it woul send me a notification. And it happened multipe times within the hour. Sometimes taking tens of minutes to reconnect, sometimes not reconnecting it at all.
3. Google Timeline (the thing that draws a map of where you've been and how you've traveled)
I used this to follow my cycling and walking, since step counters dont recongnize cycling very well or at all. However since the update the pages are all empty. It just wont recognize my movement at all. I later noticed that the location gathering accesses had been reset, but even after giving them access again there is absolutely nothing saved onto my timelines.
Please, if you have any ideas what is doing this, or any ideas how to fix one, or each of these, leave a reply...
If nothing else I'll have to rollback to Marshmallow... And I've really grown to like the split screen!
hi, having same problem as #3 on my brand new Huawei Mate 10 pro. did you ever solve the issue? thanks
Just wanted to ask if anyone else has this issue. Whenever I look to connect my Bluetooth headphones to the phone, it causes a freeze problem. This only seems to have happened the last couple of times I've tried it. Also, it only seems to happen when I've already turned on the Bluetooth setting on the headphones before I then search for devices on the phone. It gets stuck in some kind of freeze loop. Only way out is to try to hard reset the app. Initially, I panicked cos I can't pull the battery out.