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.
Related
Hello all!
Recently I've purchased the Swann DVR8-1425 security system.
I've been able to connect it to my home network successfully. I can remote view the cameras through my T999L (no root, completely stock) on WiFi through the SwannView app, but as soon as I put it into mobile data, it shows me a message of not being able to contact the server. I'm assuming if I were at someone elses house on their WiFi, it would be the same result. Same issue on my Dad's S2, rooted, running Infamous 3.0 in the T989 forums.
I've messed with most, if not all the settings I can possibly use with trial and error. When it comes down to it, obviously there's only the one setting that works with my WiFi (the given IP address from the DVR and a server port given: 9000) and it won't connect with mobile data whatsoever (2g, 4g, or LTE). I've tried using HTTP port 85 instead of the 9000, a preferred DNS server in place of the IP address, turning on and off UpNp (not really sure what that does). Absolutely nothing. Server connection fail each time when using mobile data.
I've disabled the firewall in hopes of it working, but I've had no luck. Haven't reset the router, assuming I just unplug and replug but other than that, I'm out of ideas. Not sure what else I can work on besides the firewall, if that even does anything.
The Swann software installed on my Mac does work, but haven't had a chance to test it somewhere other than my home network. It could work, but I wouldn't know at this point. Just more concentrated on the mobile data issue.
My knowledge is small when it comes to this networking stuff. Connecting to a WiFi hotspot is about as easy as it gets for me lol. I just got lucky with trial and error for setting it up with the home network. Just wondering if anyone has experience with this or ideas that may come to mind. At the worst, I won't be able to remote view anywhere other than using my wifi, but it will still record at least.
Thanks in advance!
MyanRagahis said:
The Swann software installed on my Mac does work, but haven't had a chance to test it somewhere other than my home network. It could work, but I wouldn't know at this point. Just more concentrated on the mobile data issue.
Click to expand...
Click to collapse
^^^^^
Seems to me you should test the remote connection elsewhere before you start troubleshooting a problem thst may not even exist. If its not configured correctly to do what you want, its not going to work across the internet which would include the mobile data.
Make sure you can access what you want remotely, then test over mobile data. Unless I read that wrong it doesn't sound to me like you've done this. You can test the mobile data connection all you want, but if its not working remotely by any other means you will be wasting your time. (Unless you got lucky and configured it correctly, but as you said, youre not very experienced with this).
Until you verify it does work remotely, there's no reason to assume its your phone or T-Mobile that is the problem.
Tbh, I'd assume first it was a router config on your side. (Unplugging it doesn't reset its settings, and even if it did it may not be configured as needed by default.)
You'd probably find better support by going to the equipment website and router website.
Sorry I don't have the answer your looking for, but hopefully ill get you in the right direction.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
^^^^^
Seems to me you should test the remote connection elsewhere before you start troubleshooting a problem thst may not even exist. If its not configured correctly to do what you want, its not going to work across the internet which would include the mobile data.
Make sure you can access what you want remotely, then test over mobile data. Unless I read that wrong it doesn't sound to me like you've done this. You can test the mobile data connection all you want, but if its not working remotely by any other means you will be wasting your time. (Unless you got lucky and configured it correctly, but as you said, youre not very experienced with this).
Until you verify it does work remotely, there's no reason to assume its your phone or T-Mobile that is the problem.
Tbh, I'd assume first it was a router config on your side. (Unplugging it doesn't reset its settings, and even if it did it may not be configured as needed by default.)
You'd probably find better support by going to the equipment website and router website.
Sorry I don't have the answer your looking for, but hopefully ill get you in the right direction.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
After read this earlier, I facepalmed myself and went to go test this out. Drove over to Starbucks a few minutes ago, connected to their wifi through my phone and it didn't connect Hmm...definitely a router setting then. The dvr itself is connected to the router by an ethernet cable. Just a matter of figuring out how to configuring the router settings. Thanks!
Try bluestacks
Hey. I came across this page looking for a solution to a similar problem. My new swann system connects fine with my phone on Orange but wouldn't connect to my partners identical phone on Vodafone via mobile Internet. Both worked on wifi. I solved by asking Google for my ip address, then going onto the swannview link app, under my device is a button to edit, on the edit page where it has p2p if you tap the line it gives you another option to connect with ip, then enter your ip where it says host. Save details with icon in top right and log in. This solved my issue, hope it helps anyone with the same issue.
MyanRagahis said:
Hello all!
Recently I've purchased the Swann DVR8-1425 security system.
I've been able to connect it to my home network successfully. I can remote view the cameras through my T999L (no root, completely stock) on WiFi through the SwannView app, but as soon as I put it into mobile data, it shows me a message of not being able to contact the server. I'm assuming if I were at someone elses house on their WiFi, it would be the same result. Same issue on my Dad's S2, rooted, running Infamous 3.0 in the T989 forums.
I've messed with most, if not all the settings I can possibly use with trial and error. When it comes down to it, obviously there's only the one setting that works with my WiFi (the given IP address from the DVR and a server port given: 9000) and it won't connect with mobile data whatsoever (2g, 4g, or LTE). I've tried using HTTP port 85 instead of the 9000, a preferred DNS server in place of the IP address, turning on and off UpNp (not really sure what that does). Absolutely nothing. Server connection fail each time when using mobile data.
I've disabled the firewall in hopes of it working, but I've had no luck. Haven't reset the router, assuming I just unplug and replug but other than that, I'm out of ideas. Not sure what else I can work on besides the firewall, if that even does anything.
The Swann software installed on my Mac does work, but haven't had a chance to test it somewhere other than my home network. It could work, but I wouldn't know at this point. Just more concentrated on the mobile data issue.
My knowledge is small when it comes to this networking stuff. Connecting to a WiFi hotspot is about as easy as it gets for me lol. I just got lucky with trial and error for setting it up with the home network. Just wondering if anyone has experience with this or ideas that may come to mind. At the worst, I won't be able to remote view anywhere other than using my wifi, but it will still record at least.
Thanks in advance!
Click to expand...
Click to collapse
Fix
Hello..
I am also using Lorex wireless security camera for my home but till now I am not facing any issue because all configuration is performed by experts. But I have two fixes for your issue.
Either contact with Lorex Support Team for help or follow steps:
Check with your mobile data service provider to confirm if they allow streaming of constant information over their network.
Configure a lower substream video resolution in your DVR / NVR settings to reduce mobile data usage and increase your connection speed.
If you cannot connect to your cameras using an LTE or IPv6 connection, switch to a 3G connection.
If you are using a device ID through your mobile plan, set up a Dynamic Domain Name System (DDNS) to eliminate the need to pass through the Stratus / FLIR Cloud servers.
Hope it helps!
I am finding many instances where I am getting the cloud icon when I am at home. My watch has both of my access points set up. Sometimes I will get the cloud and I will be 10 feet away from an access point and within line of site while my phone is sitting even less than that from another access point and also in line of sight, and when I check the phone it is connected to wifi.
I thought being on the same LAN was supposed to be functionally equivalent to having a Bluetooth connection.
I have also noticed that the watch does not seem to automatically connect to wifi when it loses the BT connection even though I have it set to automatic in the settings.
I am not going to carry my phone all over the house like a goofball so that the watch works. Wifi capability was one of the things I was waiting for for this very reason. It makes the watch WAY more useful...but it actually has to work properly.
brizey said:
I am finding many instances where I am getting the cloud icon when I am at home. My watch has both of my access points set up. Sometimes I will get the cloud and I will be 10 feet away from an access point and within line of site while my phone is sitting even less than that from another access point and also in line of sight, and when I check the phone it is connected to wifi.
Click to expand...
Click to collapse
I thought being on the same LAN was supposed to be functionally equivalent to having a Bluetooth connection.
Have experienced the same. However, it may not be the watch problem and may be the Google cloud ☁ service.
vvveith said:
I thought being on the same LAN was supposed to be functionally equivalent to having a Bluetooth connection.
Have experienced the same. However, it may not be the watch problem and may be the Google cloud service.
Click to expand...
Click to collapse
Experiencing the same thing more and more often.
My phone (N6) is connected to either wifi or 4G; my watch connects to wif's as well. Nonetheless when disconnected from bluetooth it disconects completely (The Cloud thingy).
Why? I must be doing something wrong, Android Wear is new to me.
Hi
If I understand correctly the wifi will only work if the phone is close by
I read elsewhere that other smart watches will connect directly to wifi
even if the phone is not on
can someone please clarify & will this option come with future updates ?
Thanks
The phone needs to be only in a close range if you're connected by Bluetooth. If you're connected to a WiFi network, the phone just needs an internet connection and can be on the other side of the world.
foo said:
The phone needs to be only in a close range if you're connected by Bluetooth. If you're connected to a WiFi network, the phone just needs an internet connection and can be on the other side of the world.
Click to expand...
Click to collapse
Thanks Foo
But it doesn't seem to be the case with mine
If I am at home or at work it will connect easily with the Wifi but only if the phone is there
without the phone its saying disconnected , maybe I am missing something
I did a test recently with mine. I left my paired smartphone (Smartphone_A) far out of range of my watch (>100m within a company building). The watch signaled that it is disconnected as it was only connected by Bluetooth before. The smartphone itself was only connected to a 3G network (no WiFi active).
I used a second smartphone (Smartphone_B, obviously not paired with the watch) and activated the mobile hotspot on it. I connected the watch to the mobile hotspot using WiFi and was able to connect to my paired smartphone:
Code:
Watch<---WiFi<--->Smartphone_B<--------->3G mobile data<--------->Smartphone_A
<--------------------receive notifications-------------------------->
I was really surprised that this worked, but it did, so I'm pretty sure, that they do not have to be both connected to the same WiFi or be within a close range.
The question is, why is it not working for you. How do you check, that you are connected to the WiFi?
foo said:
I did a test recently with mine. I left my paired smartphone (Smartphone_A) far out of range of my watch (>100m within a company building). The watch signaled that it is disconnected as it was only connected by Bluetooth before. The smartphone itself was only connected to a 3G network (no WiFi active).
I used a second smartphone (Smartphone_B, obviously not paired with the watch) and activated the mobile hotspot on it. I connected the watch to the mobile hotspot using WiFi and was able to connect to my paired smartphone:
Code:
Watch<---WiFi<--->Smartphone_B<--------->3G mobile data<--------->Smartphone_A
<--------------------receive notifications-------------------------->
I was really surprised that this worked, but it did, so I'm pretty sure, that they do not have to be both connected to the same WiFi or be within a close range.
The question is, why is it not working for you. How do you check, that you are connected to the WiFi?
Click to expand...
Click to collapse
Strange
with my phone on no problems it shows my house & work network on the watch & connects showing the correct SSID
with phone off I tested it 2 ways 1 clicked on google app (disconnected ) 2 Settings- About -Connection (disconnected )
Brgds
I see the problem, I also may have misunderstood the actual problem.
The status (Google app/about) which you are referring to shows if you're connected to your watch. If your phone is off, the watch can't connect to the phone. Even if the watch is connected to your WiFi, the watch will not go directly to the internet, but will use the WiFi connection to connect to your phone (cloudsync).
You can check the WiFi connection in the WiFi setting. See if the watch was assigned an IP address, if there is one, then you're connected to the WiFi.
I think you expected that the watch can directly connect to the internet and use things like Google now directly. but this is not possible.
foo said:
I see the problem, I also may have misunderstood the actual problem.
The status (Google app/about) which you are referring to shows if you're connected to your watch. If your phone is off, the watch can't connect to the phone. Even if the watch is connected to your WiFi, the watch will not go directly to the internet, but will use the WiFi connection to connect to your phone (cloudsync).
You can check the WiFi connection in the WiFi setting. See if the watch was assigned an IP address, if there is one, then you're connected to the WiFi.
I think you expected that the watch can directly connect to the internet and use things like Google now directly. but this is not possible.
Click to expand...
Click to collapse
Yes
I checked a few things, my phone was on & the google app works, turn phone off & the google app says disconnected
in wifi settings even with phone off it says obtaining IP then connects so I thought it would connect to google app
so if I understand correctly it wont connect directly to internet but the phone (cloudsync) even if the phone is on or off
Thanks for taking the time to clarify
tclough said:
so if I understand correctly it wont connect directly to internet
Click to expand...
Click to collapse
correct
tclough said:
but the phone (cloudsync) even if the phone is on or off
Click to expand...
Click to collapse
it will connect to the phone by cloudsync only if the phone is on.
foo said:
correct
it will connect to the phone by cloudsync only if the phone is on.
Click to expand...
Click to collapse
Thanks
all seems a bit pointless to have a wifi connection but cant really use it do anything
maybe some apps or updates in the future that will utilize the wifi option ??
Thx
I guess wifi is just helpful if you get out of range of the Bluetooth connection.
At home I often get out of range of the Bluetooth connection so the watch connects to my wifi and reconnects to my watch via cloudsync as long as I stay out of Bluetooth range.
When the watch gets back in reach it connects via Bluetooth again, because this is much better for battery life.
So wifi is only there to increase range but unfortunately not for standalone functionality. I also have a Youtube client and a webbrowser on my watch (just for fun, not really useful). Both apps also need the watch and will not use a direct wifi connection to load videos/websites from the Internet.
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!?
Had my galaxy watch about a month now. I have set wifi to auto but I find it resets itself to off. I then set wifi to on and then it still turns off. Any ideas on what is going on? I may have to contact Samsung and I dread doing so.
WiFi shall only be used if the watch loses the connection to your phone. It is only used for the remote connection feature, where the Bluetooth connection between watch and phone is lost afaik
Gesendet von meinem SM-G965F mit Tapatalk
It is set to turn on when I lose BT connection. It can't turn on because the watch has turned wifi completely off
I have my WiFi set to automatic and that works just as expected. Connects to WiFi when Bluetooth connection drops.
Gesendet von meinem SM-G965F mit Tapatalk
I had that problem and I've only gotten my watch for a couple of days. I just turned on wifi to auto when the watch was connected to bluetooth and it just kept going that way for the time being.
Update: I've seen that the WiFi turns itaelf off again after some time. I'm pretty curious to know what causes that.
Have had my watch five days now and have experienced the problem of not being able to reconnect to Wi-Fi..
Define a Wi-Fi connection to be used 'Auto' (when out of reach of BT). But next time the watch is out of BT-reach it is stuck in 'Connecting ...' ( seen in the status of Wi-Fi).
Have reported this as an issue ( I'm in Denmark) and got the answer: Try to 'Reset' - otherwise wait for an update.
My software version is: R815FXXU1BRHB
Maybe it is a router problem. In German forums some dudes have problems with fritz Box router. It does connect only once to the router.
I also noticed that. Probably watch tries to save battery life. It turns on again when you start to do something. Personally I find out as good feature. No drawback.
bagmanone said:
I also noticed that. Probably watch tries to save battery life. It turns on again when you start to do something. Personally I find out as good feature. No drawback.
Click to expand...
Click to collapse
It is not because there are three options Wi-Fi (off), Wi-Fi (on) and Wi-Fi (auto). The later should (re)connect to Wi-Fi when out of reach of BT (the first two are manual). But the reconnect is never completed, stays in "Connecting ...".
What do you mean by "It turns on again when you start to do something."? My watch does not for the above reason (connection is never completed).
Doing manual Wi-Fi connection to same Wi-Fi works fine. When out of reach of BT to mobile it is connected to 4G network.
pkylle said:
It is not because there are three options Wi-Fi (off), Wi-Fi (on) and Wi-Fi (auto). The later should (re)connect to Wi-Fi when out of reach of BT (the first two are manual). But the reconnect is never completed, stays in "Connecting ...".
What do you mean by "It turns on again when you start to do something."? My watch does not for the above reason (connection is never completed).
Doing manual Wi-Fi connection to same Wi-Fi works fine. When out of reach of BT to mobile it is connected to 4G network.
Click to expand...
Click to collapse
I use option Always On. For the option watch turn off Wifi when it is not used at all. Watch turns Wifi on when I start to use watch. It is only my observation. I don't know is that indented behave for GW.
bagmanone said:
I use option Always On. For the option watch turn off Wifi when it is not used at all. Watch turns Wifi on when I start to use watch. It is only my observation. I don't know is that indented behave for GW.
Click to expand...
Click to collapse
Have you tried the Wi-Fi (auto)?
pkylle said:
Have you tried the Wi-Fi (auto)?
Click to expand...
Click to collapse
Not really, I usually need Wifi to connect the internet.
bagmanone said:
Not really, I usually need Wifi to connect the internet.
Click to expand...
Click to collapse
The watch will connect to the internet using BT to the mobile if within range.
pkylle said:
It is not because there are three options Wi-Fi (off), Wi-Fi (on) and Wi-Fi (auto). The later should (re)connect to Wi-Fi when out of reach of BT (the first two are manual). But the reconnect is never completed, stays in "Connecting ...".
What do you mean by "It turns on again when you start to do something."? My watch does not for the above reason (connection is never completed).
Doing manual Wi-Fi connection to same Wi-Fi works fine. When out of reach of BT to mobile it is connected to 4G network.
Click to expand...
Click to collapse
The sync Wi-Fi profiles setting seems to cause the the watch forgets the Wi-Fi password. This shows up as with that "connecting..." state. Try to remove that sync option from the wear app on phone and see if that helps.
I would like to use the Wi-Fi (auto) setting, but for some reason the watch changes that back to Wi-Fi (off) by itself. No idea how to make the watch to remember the setting.
miloytyn said:
The sync Wi-Fi profiles setting seems to cause the the watch forgets the Wi-Fi password. This shows up as with that "connecting..." state. Try to remove that sync option from the wear app on phone and see if that helps.
Click to expand...
Click to collapse
Wow! That did it but this shows there clearly is an error in the sync. option. Did someone report that to Samsung?
Thanks.
miloytyn said:
The sync Wi-Fi profiles setting seems to cause the the watch forgets the Wi-Fi password. This shows up as with that "connecting..." state. No idea how to make the watch to remember the setting.
Click to expand...
Click to collapse
Just bought this watch today. I have the same problem
Disablem "syncing" in connection setting on phone app cures the pproblem
Same issue here.
Just bought the watch and set it on Always on wifi but noticed that it disconnects after some time and then refuses to connect to the same SSID. It either says, authentication error, cannot connect to ...., or doesn't say anything.
Restarting the watch fixes it temporarily.
Keeping it on Auto, does not change from bluetooth to wifi when out of range.
Sync profiles is on. I will try with it off.
Did anyone figure the solution to the issue?
I am facing the same issue