Hi everyone always received great answer here but still very new at this. My problem is with the Att galaxy note 4 (currently brand new and still stock). When using with all properly enabled "OK google" wake up command only works intermittetanly. Work fine all day yesterday....I wake up today and it is gone again. Works fine always if using google now launcher....but would rather it work with all launchers as they each have desired features. Any Ideas? Sorry if the subject has been brought tip before but I could not find it.
I gather many people are having connection issues with their Android Wear devices.
Is this just a Note 3 issue?
Has anyone managed to get a stable connection using Lollipop?
Yes, my Note 3 with Lollipop (tested many ROMs, even the Note 4 ports) has this issue, and it's not only with Android Wear, but with several other Bluetooth LE devices. I've heard mixed explanations: some say it's something with Lollipop itself, affecting many phones (unless the manufacturer added patches to solve the issue), and Google solved it with Lollipop 5.1; others say it's something only with Samsung's Lollipop ROMs. The latter may be true, as @civato apparently solved the issue tweaking the kernel.
Some people say their phones don't have this issue, but I suspect it's because they haven't put their BTLE devices under the failing scenarios. I have a very easy test case:
1) Pair your Android Wear watch with your phone, using the Android Wear app. Make sure the watch is communicating with the phone.
2) Create a situation where your watch loses connection with your phone (e.g. walk away with the watch, put it in a Faraday cage etc.). But make sure it stays that way for some time, say 10-30 minutes (sometimes it happens as soon as it's out of range).
3) Notice that even though the watch is disconnected (the "no cloud" icon is shown), the Android Wear app on the phone will show it as "connected". Now even if you bring the watch close to the phone again, it will not reconnect automatically.
The same thing happens with other BTLE devices. Other symptoms include frequently disconnects / reconnects, even when the device is in range.
Mine has paired but refuses to connect now. I'll try Civ kernel.
Is there a Lollipop Civ kernel lol
Some problem here with my Sony Smartwatch. The new XEO Update don't fix the Bluetooth problems complete. Is any fix released to fix the Bluetooth Connection problems?
I had all sorts of problems on both the leaked Lollipop and the official Lollipop. It was driving me insane with its constant disconnections/reconnections and then just disconnecting until Bluetooth was cycled. It made the watch useless!!!
I then tried Dark Lords N4 port (v1.5). Boom! All working perfectly. No more issues at all and reconnects if i move out of range seamlessly.
Same problem, Note 3 XEO with Sony SW3. So maybe for now there is only way - root with knox 0x1 and N4 port ROM...
Had a few issues after getting Lollipop but nothing compared to the issues I got when Android Wear updated (on Friday I think it was).
My Moto 360 just wasn't wanting to connect, tried rebooting phone, then the watch, but didn't help. In the end I factory rest my watch and its been fine since.
Vince
Yep, bluetooth all over the shop...Headset and Moto 360.
I also have a lot of problems with Sony SW3 and Note 3. Not only I have inconstant BT connection, but also weird management of incoming phone calls: watch notifies phone calls that appear on the teleohone only 3 or 4 seconds later (that's a huge time).
Anaother issue: I have also tried to decline a phone call with the Smartwatch but the telephone went on ringing.
Inviato dal mio SM-N9005 utilizzando Tapatalk
Also posted this on the LG G Watch R forum (the watch I own ):
Since the last Wear update (5.1.1) I noticed that the 'Ok Google" command is less responsive.
Sometimes I have to say it three times before it is recognized, I also stumbled on this thread:
https://www.reddit.com/r/AndroidWear/comments/3784f5/anyone_else_notice_ok_google_less_responsive/ so it seems others are also experiencing this.
Before the 5.1.1 update it was almost always working the first time. Maybe they lowered the sensitivity cause of false positives. Does anybody else experience the same?
Would be nice to have an option to adjust the sensitivity.
Hi,
I have actually been having this problem for roughly 1 year on multiple devices from lollipop to marshmallow. I have a LG G watch R and this issue started happening around the same time i started using my galaxy note 4 on lollipop. It has persisted through to a Galaxy S6 edge plus and now my S7 edge on stock and custom roms.
So the Issue is when ever i install android wear all my notifications sounds disappear after i use my watch for voice commands to make a call or send a sms. My ringtone still works but all sms and application sounds do not. I reboot my phone and sounds come back until i use my voice commands on my watch. Also if i uninstall android wear all sounds are restored and all is perfect again.
I contacted google support and they said they are going to try and help me to correct this problem with android wear, after 45 min they transferred me to LG without telling me and LG was like well what do you want us to do call Samsung.
Has anyone else experienced anything like this or maybe knows of a fix?
Anyways thanks for reading.
Hello all, I have a Huawei Watch which works perfectly with my LG G5.
Now I try a new phone (Mi Max - Helium with official global rom) and I am getting all kinds of issues.
First, the DND - Silent mode toggles are crossed.
I select "silent" on the phone and it triggers Do not disturb on the watch. Result: I cannot receive vibrations only (as the phone will vibrate but the watch will not due to the DND activated).
Second, I am using the google messenger app: that app does not notify me when messages arrive on the phone (I mean it notifies on the phone but not on the watch). Also, the calendar notifications are not passed on either...
Quite disappointing - as with the LG G5 all worked so well...
I tried the "silence phone while wearing watch" feature: that does not do anything either. The phone will ring even when that is "on"
Is there any fix, any ideas?
Its miui, nothing works well with it.... its modified so much many standard android apps dont work with it, basically whenver I get a miui based xiaomi phone the first thing I do is install CYanagenmod/Lineage OS onto it ASAP. Basically anything out of China with android on it is totally screwed in some way or another or most China apps track users behind the scenes for the Chinese government due to them making it legally mandatory to track users to particular phones if you company is based in China