Network Connection Issues?

evlarberryman

Well-known member
Jan 11, 2016
231
0
0
Has anyone had problems with the LG Urbane 2nd Edition having issues connecting to the server transitioning (moving) from Bluetooth range, to wifi range, to LTE cellular connection? Specifically, what I am experiencing when I leave my house and my phone is at home on the charger, my watch will show as disconnected and you cannot use "OK Google" or anything that requires a data connection. This will sometimes last 5 to 10 minutes before the cellular feature of the watch kicks and I can again use it for searches, texts, etc.

I have my wifi on auto, cellular on auto, and Bluetooth and GPS are on. I suspect there is a software glitch in android wear talking to the hardware (LG) and the watch recognizing the transition between these forms of connecting. On m Samsung Gear S2, it was very good to know and connect to the cellular network on the watch within 10 - 15 seconds of leaving Bluetooth or wifi.

Has anyone else experienced this? If not, would some of try this out and report back? I want to know if this is limited to my device or if this is a common problem. 've also noticed that even though I turn off wifi, the watch eventually turns it back on automatically at some point.

I hope we are not looking a mojor problem here, but this is annoying.
 
...... i've also noticed that even though I turn off wifi, the watch eventually turns it back on automatically at some point........

I can't speak to the cellular issue yet since I usually leave it off and manually turn it on when I go for runs. If I turn off BT on the phone then manually activate cellular it connects quickly. However, I have noticed that the Wi-Fi does turn on automatically after turning it off. I'm not sure what issues this will cause, but I'm going keep an eye on it to see if it affects the battery.
 
On my original Samsung Gear S, there is 60 second delay after BT disconnects and before cellular data kicks in. This is to avoid unnecessary cell radio on/off (Samsung keeps cell radio off in auto mode) if you briefly loss BT connection to phone. I'm sure AW has the same delay but usually it is with the similar time delay as my Samsung based on my experience with my Nov edition of this watch (usually when I drive half mile out of my house). Not sure about this new version yet. I too only manually turn it on because leaving it on draws too much battery power.
 
I have had some very similar issues with mine. I live in a high rise building so I have to take an elevator to get out, if I leave my phone in my apartment, it won't connect to the cell network until I get outside, so it's a couple minutes of no connectivity. There are times where it just won't connect to the Google servers and shows the cloud with the slash through it even though it shows that I have an LTE connection. Most of the time it works just fine though. If you put it into Airplane mode and then back that usually has fixed the issue for me. Just kind of forces it to reestablish a connection with the cell network. Last resort is doing a restart and see if that gets it to connect.
 
I have had some very similar issues with mine. I live in a high rise building so I have to take an elevator to get out, if I leave my phone in my apartment, it won't connect to the cell network until I get outside, so it's a couple minutes of no connectivity. There are times where it just won't connect to the Google servers and shows the cloud with the slash through it even though it shows that I have an LTE connection. Most of the time it works just fine though. If you put it into Airplane mode and then back that usually has fixed the issue for me. Just kind of forces it to reestablish a connection with the cell network. Last resort is doing a restart and see if that gets it to connect.

Lvmymoto, this is exactly what I am referring to. I wonder if this is a known software/hardware glitch by LG? A bit surprising they would re-release this watch after a recall without being absolutely sure there are not connectivity issues. I remember the reason for the November recall had to do with cellular connectivity issues on the watch. There's a YouTube video online that shows this. It is similar to what we are experiencing though the cloud with the slash always happened on the recalled watch.

Posted via the Android Central App
 
Lvmymoto, this is exactly what I am referring to. I wonder if this is a known software/hardware glitch by LG? A bit surprising they would re-release this watch after a recall without being absolutely sure there are not connectivity issues. I remember the reason for the November recall had to do with cellular connectivity issues on the watch. There's a YouTube video online that shows this. It is similar to what we are experiencing though the cloud with the slash always happened on the recalled watch.

Posted via the Android Central App
LG never statd what the issue was. Do you have a link to that video?
 
Lvmymoto, this is exactly what I am referring to. I wonder if this is a known software/hardware glitch by LG? A bit surprising they would re-release this watch after a recall without being absolutely sure there are not connectivity issues. I remember the reason for the November recall had to do with cellular connectivity issues on the watch. There's a YouTube video online that shows this. It is similar to what we are experiencing though the cloud with the slash always happened on the recalled watch.

Posted via the Android Central App

I have the recalled version of the watch, and I guess I didn't know that part of the recall was the connectivity. I got my watch the day it was released in November and have had virtually no issues with it other than it not connecting all the time. And even that has been very intermittent, it works perfectly 90% of the time. But like I said, it's usually fixed by a restart or switching the network on and off.
 
I haven't had an issue yet from bluetooth to cellular hand off. I mean it's not instantaneous but it's not an issue. I haven't tried from bluetooth to wifi hand off though.
 
Considering we don't have another Android Wear watch with LTE yet to compare it to i would be hesitant to blame it on LG. It could just as easily be a network or software issue. Being an early adopter of a new product line can have this effect. Really can't compare it to the Samsung S2 cause that's Tizen. That's like comparing Windows to a Mac.
 
Maybe he is referring to this one? https://youtu.be/wSlycq8c2TI

Still not exactly clear on the original issue. Once I had an active SIM that had both cell service and data, I never had a problem like this with the original watch.

Yes that is the video. So my connectivity problem seems to be worse, meaning get the watch shows as disconnected anytime it away from the phone. Not good, especially since this was the recall related issue before.

Posted via the Android Central App
 
I've had mine since Novber and have not noticed these issues on mine. However, I only use it untethered to my cell when I go running, so maybe when I tried to call or txt it just happened to work.
 
What carrier watch do you have evlarberryman? I bought the watch from Verizon last Thursday and haven't been able to get a cellular connection on it yet. No technician has been able to figure out what the problem is.
 
yelp the OLED screen failed after a 1000 hrs on some of the watches.

I've always wanted to know the exact cause of the recall. Is the OLED screen testing issue documented anywhere other than the statement LG released after the recall? Their statement didn't provide any details.
 
LG made it very clear that they didn't want to name the component supplier. If it is OLED screen, it will probably be from LG Display . You are probably never going to find the definitive answer to this question.
 
What carrier watch do you have evlarberryman? I bought the watch from Verizon last Thursday and haven't been able to get a cellular connection on it yet. No technician has been able to figure out what the problem is.

I use AT&T. You should check your SIM card status on the settings for your watch and make sure it's active. My issue is the software and hardware detecting when to turn cellar on and off.

Posted via the Android Central App