Hello, I updated my Moto 360 to the new version which enables wifi support and I have a weird problem, when I disconnect my phone bluetooth and wifi and enable wifi on moto 360 I notice that I don't get notifications for mails, facebook messages, tweets etc also voice commands won't work, but I can browse webpages with android wear internet browser.
Am I missing something ?
Isn't the whole idea of wifi support to be able to use the watch autonomously ?
If not by Bluetooth, your watch must still be on the same network as your phone to get notifications from your phone. You need to turn WiFi on your phone back on.
Hey RoyJ thanks for your reply, I see so the phone gets a notifications then pushes it to the watch via wifi, that's a shame, let's hope in a future update where the device would function autonomously without a phone.
Noticed the same thing. What I have found is that Bluetooth needs to be on regardless of whether the watch is connected to the phone or not. It is as if it is a switch to tell the android wear app whether or not to forward notifications. I can personally confirm that you do not need to be on the same WiFi network. I had my paired phone in my car at work with WiFi off and my phone connected to a hotspot I created with another phone and received all the notifications on my watch.
Sent from my LG-VS985 using Tapatalk
Also from what I read, voice commands might not work on WiFi, just notifications.
I've set this up according to Google's support page and can confirm that my Moto 360 connects to WiFi when out of range of the phone. However, it still remains disconnected from the phone, even though both phone and watch are using the same WiFi. The little cloud symbol with the line through it never disappears and none of the connected features work. As soon as I move back into range of the phone it switches back to bluetooth and reconnects again. So the switching to WiFi part is working OK, it just fails to communicate with the phone over WiFi. It's a Nexus 6, if that's relevant.
Any ideas?
EDIT: Never mind, it appears to be because the phone is using IPv6 but the watch only supports IPv4, oddly. If I force the phone to use IPv4 it works.
mijkz said:
EDIT: Never mind, it appears to be because the phone is using IPv6 but the watch only supports IPv4, oddly. If I force the phone to use IPv4 it works.
Click to expand...
Click to collapse
Really? Isn't IPv4 kicking the bucket officially real soon like?
I can't get this working either. I have no idea why the phone's bluetooth or IPv6 should make any difference at all for this feature. It's supposed to use the cloud, and as long as the phone and watch have a connection to the internet then it should work.......right?
Unfortunately it's the sort of feature that I will disable unless it is truly reliable. And so far I can't even get it to work at all, so it's only reliable in it's ability to connect to a wifi network and drain the battery.
aperry said:
I can't get this working either. I have no idea why the phone's bluetooth or IPv6 should make any difference at all for this feature. It's supposed to use the cloud, and as long as the phone and watch have a connection to the internet then it should work.......right?
Click to expand...
Click to collapse
No, that is NOT how it works. Your watch is a slave to your phone regardless of the WiFi feature; WiFi just gives you a longer leash. I'ts HIGHLY unlikely that the current iteration of Android Wear will allow you to "leave home without your phone" as someone suggested above. It's just not how it was designed, nor how Google envisions it. If that's what you want, you're best looking outside of Android Wear and into some of the fringe wearables that actually act as mobile devices.
thebobmannh said:
No, that is NOT how it works. Your watch is a slave to your phone regardless of the WiFi feature; WiFi just gives you a longer leash. I'ts HIGHLY unlikely that the current iteration of Android Wear will allow you to "leave home without your phone" as someone suggested above. It's just not how it was designed, nor how Google envisions it. If that's what you want, you're best looking outside of Android Wear and into some of the fringe wearables that actually act as mobile devices.
Click to expand...
Click to collapse
But Google's own descriptions of the Android Wear wifi feature states this:
If your watch has Wi-Fi, your watch can automatically connect to saved Wi-Fi networks when it loses the Bluetooth connection with your phone. This lets your watch and phone to automatically stay synced at any distance over the Internet. That way you can get notifications and use voice search on your watch throughout your home and work when you leave your phone in a different room.
Click to expand...
Click to collapse
Operative words being "This lets your watch and phone stay synced at any distance over the internet". Are you telling me that "any distance over the internet" actually means "only as far as your local wifi network covers"?
It also states "Could Sync" must be turned on for wifi to work. Why would I need a feature called "Cloud Sync" if it's not designed to sync over the cloud?
aperry said:
But Google's own descriptions of the Android Wear wifi feature states this:
Operative words being "This lets your watch and phone stay synced at any distance over the internet". Are you telling me that "any distance over the internet" actually means "only as far as your local wifi network covers"?
It also states "Could Sync" must be turned on for wifi to work. Why would I need a feature called "Cloud Sync" if it's not designed to sync over the cloud?
Click to expand...
Click to collapse
Imagine you could connect to many WiFi locations as long as you already connected and saved those WiFi locations. But a WiFi only tablet can't connect at all times, how can you expect your watch to?
Here's what I have found:
My setup: Nexus 6 with Moto 360 5.1.1
On WiFi (same network) - BT off, I can receive texts, reply to texts, send texts. Once I turn off the WiFi on my phone, I no longer get notifications because the phone no longer knows where the phone is to send the notifications to. I think that makes sense. As others have said, the watch is always slave to the phone, however it is connected - WiFi or BT. But I do think that it was not designed to be independent of the phone, so you can't simply leave your phone at home and go out and expect to have notifications even if the watch is connected on WiFi.
mohcho said:
Here's what I have found:
My setup: Nexus 6 with Moto 360 5.1.1
On WiFi (same network) - BT off, I can receive texts, reply to texts, send texts. Once I turn off the WiFi on my phone, I no longer get notifications because the phone no longer knows where the phone is to send the notifications to. I think that makes sense. As others have said, the watch is always slave to the phone, however it is connected - WiFi or BT. But I do think that it was not designed to be independent of the phone, so you can't simply leave your phone at home and go out and expect to have notifications even if the watch is connected on WiFi.
Click to expand...
Click to collapse
I don't understand why "slave" would require the watch and phone to be on the same network. If the data is synced via the Cloud then the watch can still operate as a slave, meaning it will receive but not generate notifications.
Furthermore, it still doesn't explain why Google states that this wifi feature allows us to "stay synced at any distance over the internet", and why they state that the wifi feature requires the Cloud Sync feature to be enabled. if Cloud Sync is not meant to sync notifications over the cloud, then what exactly IS being sync'd over the cloud?
When you set up the watch, you have to pair it via BT using the phone. That authenticates the watch hardware with your account on your phone. If the phone and watch are not on the same network, how would your watch authenticate against your account? It's not like there's any account login option for the watch itself, hence it slaved to your phone on the same WiFi network. Since the watch has no real input options other than voice and swiping, there's no way to authenticate your watch to your account. I think it's wise that they set it up this way, albeit, a bit confusing how they worded the WiFi capabilities.
mohcho said:
When you set up the watch, you have to pair it via BT using the phone. That authenticates the watch hardware with your account on your phone. If the phone and watch are not on the same network, how would your watch authenticate against your account? It's not like there's any account login option for the watch itself, hence it slaved to your phone on the same WiFi network. Since the watch has no real input options other than voice and swiping, there's no way to authenticate your watch to your account. I think it's wise that they set it up this way, albeit, a bit confusing how they worded the WiFi capabilities.
Click to expand...
Click to collapse
Ok, putting aside the confusing language in Google's own description (that no one can explain), let me simplify my question: What is Cloud Sync?
Btw, authentication could be taken care of with a token. That would be generated by the Cloud and sent to the phone when the Cloud Sync feature is first enabled, and would be sent to the watch initially via BT and then used to authenticate the watch to the Cloud whenever needed. Token would be invalidated by the Cloud if/when Cloud Sync is disabled on the phone (for example, if the watch is stolen). This is roughly how I expected it to work. If somehow the watch and phone need to be on the same wifi network then this feature is 90% useless IMO, and Google's description is very misleading.
I stand corrected. I think it does work the way you suggest, but not 100%.
I connected my watch to my other phone's hotspot and am able to send/receive texts and emails to my watch. I turned off WiFi on my phone as well as the BT. It takes a while for it to connect and I assume authenticate using a token.
After a while though, like just now, I received a text on my watch but couldn't reply to it, the watching saying "Sorry that didn't work, try again".
mohcho said:
I stand corrected. I think it does work the way you suggest, but not 100%.
I connected my watch to my other phone's hotspot and am able to send/receive texts and emails to my watch. I turned off WiFi on my phone as well as the BT. It takes a while for it to connect and I assume authenticate using a token.
After a while though, like just now, I received a text on my watch but couldn't reply to it, the watching saying "Sorry that didn't work, try again".
Click to expand...
Click to collapse
Cool, thanks for testing this. Now if I can get my own watch to work then I'll be happy
By the way, the diagram at the bottom of this page seems to confirm that the watch should be able to sync notification data with the Cloud without any direct connectivity to the phone:
http://developer.android.com/training/wearables/data-layer/index.html
JeffMD said:
Really? Isn't IPv4 kicking the bucket officially real soon like?
Click to expand...
Click to collapse
The moto 360 doesn't support ipv6 that's for sure. But really that's a non issue, as far as them shutting down ipv4 it won't be for a long time. At least longer than the life cycle of the moto 360 anyways. The Ipv6 adoption is only more prevalent in the U. S. for the most part.
Also as far as a phone using ipv6 only I'm sure Google has some sort of protocol like NAT64 boxes in order for ipv6 to talk to ipv4 so it shouldn't matter if your phone is using ipv6 (but of course I could be wrong about that I'm just making that assumption they do have some sort of protocol to handle that)
jgeorge15 said:
The moto 360 doesn't support ipv6 that's for sure. But really that's a non issue, as far as them shutting down ipv4 it won't be for a long time. At least longer than the life cycle of the moto 360 anyways. The Ipv6 adoption is only more prevalent in the U. S. for the most part.
Also as far as a phone using ipv6 only I'm sure Google has some sort of protocol like NAT64 boxes in order for ipv6 to talk to ipv4 so it shouldn't matter if your phone is using ipv6 (but of course I could be wrong about that I'm just making that assumption they do have some sort of protocol to handle that)
Click to expand...
Click to collapse
I am pretty sure that the phone and watch do not talk to each other directly over wifi so this IPv4-IPV6 mismatch should be a non-issue provided each one of them can reach the internet.
aperry said:
I am pretty sure that the phone and watch do not talk to each other directly over wifi so this IPv4-IPV6 mismatch should be a non-issue provided each one of them can reach the internet.
Click to expand...
Click to collapse
Yes absolutely true. I meant to word the second paragraph in my statement in a way in which I meant suppose ipv4 was shut down in the near future I'm sure Google has someway to communicate with legacy devices so notifications could still be pushed to the watch. Hope that clarifies things.
I have had this watch just about a week, after multiple resets, checking settings, I still cannot get the watch to connect to the internet via wi-fi without my phone. It will say it's connected to the network within the settings screen, but be unable to perform any tasks such as ok google commands, etc.
I just spoke to Huawei, and they said you cannot connect to the internet without your phone being paired via bluetooth. Is that correct?
yes, the wifi connection is only used to connect to your phone via the internet/wlan (cloudsync), but it can't do anything without it.
OK, so I've got a VERY strange one for y'all.
First off, I had this problem on Nougat. That's what prompted me to follow instruction on here and upgrade to Oreo and try. Yeah, that failed too.
So right now I have no problems at all connecting to any Wi-Fi router at home, my friends, in-laws, etc. Even when we go to restaurants and connect, like Bob Evans, Denny's, etc. where it asks you to accept the terms of service.. no problems.. at all!!
The problem I have is on the plane. I fly 4-6 planes a week and the free Wi-Fi I have with T-Mobile has been a godsend in keeping up with work while in the air. Obviously, it's happening on every plane I fly. I can connect to the SSID, but do not get an IP address. I even bothered the guy sitting next to me once to disable his iPhone and let me connect using the IP addressing that his phone had to try. Nothing. I can ping the gateway, but not the DNS server. SO I resolved the URL for the login page to an IP and threw that in Chrome to try to pull it up. Still nothing. It's so infuriating!! I can open plenty of apps that shows the IP address that whatever router I'm connected to gives me, but for some reason I do not get one when connecting to GoGo. I've tried a different browser (firefox, opera and the Samsung browser). I've tried an incognito window to remove and possible cashed issues. I've tried forcing Google's DNS and OpenDNS, still nothing.
So, the next step.. try a different phone. Yup, works great. It's not an account issue. It's almost like my MAC address is blocked by all the routers on every plane?! That can't be. I carry this Moto Z2 Force and also my iPhone. Problem is, I wanted to try to connect my laptop via Bluetooth to my Z2 Force once it's connected to the GoGo Wi-Fi to get my laptop online, but I can't even get an IP to be able to connect to the router. You can't do that with an iPhone. If you can... a penny for your thoughts
What's worse, is I've contacted GoGo Wi-Fi's tech support chat. They are determined to tell me there's something wrong with the phone.
Can someone please help me figure this out? I used to work in an IT department for the state government, and I should be able to keep up with whatever you ask.
Thanks a TON in advance!!
Some specifics:
Moto Z2 Force (T-Mobile)
Rooted with Magisk (but had the issue when it was bone stock on Nougat)
Android 8.0.0
Baseband M8998TMO_20207.117.02.41R NUS
Kernel 4.4.78-perf-g6174029
Build OCX27
SSID of the affected network - gogoinflight
I'm flying 3 hops tomorrow and I can get you as much detail as you'd like, I just need to know what.
nothing!?