Hello,
Normally I turn off the watch at night.
Earch morning, when I turn on, the watch date/hour isn't correct, and remains incorrect until the watch connects with the phone.
This is normal? Isn't a real watch?
Previously to the Urbane I have own a LG Watch (the square model) and I don't remember this issue.
Thanks
i saw this issue after last week I wonder if there was an update that caused it...i connected my phone and the time was fine after
darhoade said:
i saw this issue after last week I wonder if there was an update that caused it...i connected my phone and the time was fine after
Click to expand...
Click to collapse
Mine is also working fine after synced with the phone, but is a annoying issue, that I don't have suffered in none of my previous devices
None of the LG watch keep time/date after power off.
I have an G and R watch and when power ON it display 1:00 (or 2:00 with DST) and January 1, 1970
Not usable if you have not a phone connected.
dersie said:
None of the LG watch keep time/date after power off.
I have an G and R watch and when power ON it display 1:00 (or 2:00 with DST) and January 1, 1970
Not usable if you have not a phone connected.
Click to expand...
Click to collapse
Possibly my fault.
I doesn't remember that issue from my previous LG G Watch.
Thanks!
bartito said:
Hello,
Normally I turn off the watch at night.
Earch morning, when I turn on, the watch date/hour isn't correct, and remains incorrect until the watch connects with the phone.
This is normal? Isn't a real watch?
Previously to the Urbane I have own a LG Watch (the square model) and I don't remember this issue.
Thanks
Click to expand...
Click to collapse
When you keep any stock watchface, watch will ask you for the required timezone, swipe left to select your city/timezone. Just set your time zone and the date and time will be automatically set and you will not face the issue again.
Related
Hi all,
in the last two days, my G Watch R is turning off randomly.
Sometimes I look at it, and it is off.
I must hold the button to turn it on again.
Does anyone know how to fix it?
Have I to bring it to service?
My software version is 4.4w.2 build knx01r
Thanks
Guiduz
guiduz said:
Hi all,
in the last two days, my G Watch R is turning off randomly.
Sometimes I look at it, and it is off.
I must hold the button to turn it on again.
Does anyone know how to fix it?
Have I to bring it to service?
My software version is 4.4w.2 build knx01r
Thanks
Guiduz
Click to expand...
Click to collapse
Please Help!
Look at the battery gauge, it seem the only reason for watch turn off and stay off.
Battery is not empty, today i saw a lot of random turning off.
Factory reset of the watch and use without install any apps (uninstall watch apps/watchface from phone before).
It reset again -> RMA
How have you solved the problem?
guiduz said:
Hi all,
in the last two days, my G Watch R is turning off randomly.
Sometimes I look at it, and it is off.
I must hold the button to turn it on again.
Does anyone know how to fix it?
Have I to bring it to service?
My software version is 4.4w.2 build knx01r
Thanks
Guiduz
Click to expand...
Click to collapse
I have same random power off issues.
This fixed my problem for Note 3 only.
He updated the bluetooth drivers in his kernel.
Watch never disconnecting now.
http://forum.xda-developers.com/showthread.php?p=57821255
[ROM+KERNEL][9005][5.0_TW_OA5] Flex_Lollipop Rev2.1 +LP_Xplorer_Rev1.5 [26/2/2015]
Sent from my SM-N9005 using XDA Free mobile app
Let me preface this by saying that after changing this setting and 20 hours later with multiple separations of phone and watch, I have yet to miss a notification and battery life is much much better. My specific problems were: Watch would randomly stop receiving notifications. I would realize this after a few hours go by without any notifications and pull my phone out and see what I've missed. This would happen despite the Wear app showing 'connected' status. Another issue I had was giving a voice command and after a few seconds the watch would return a 'disconnected'message, again the Wear app showed connected. All of this under known working network connections, whether Wi-Fi or cellular. I was also experiencing what I feel is short battery life at about 14 hours per day. I've had and used the watch for two weeks now and have restarted it many many times.
The following is the ONLY thing I have changed since the major improvement in performance. I don't have the depth of knowledge to prove or describe why this worked for me, and maybe it wasn't the cause, but I (knock wood) have a perfectly operating watch now with the battery life indicating about 2 days remaining at noon today.
Go to Settings> Bluetooth> and select the settings icon on your connected device. Then select 'connection access' and choose 'automatic'. Mine defaulted to 'always ask'.. I'm guessing this caused a hangup with the connection between Wear app and watch leading to my problems.
Edit: I'll add that my phone is an LG G2 on 4.4.2 , rooted and running xdabbeb's Rom.
Edit 2: I reset my watch, synced the watch via the Wear app on phone and NOT the Bluetooth screen and now I'm running strong after two days. Made sure automatic was checked as well.
Bugger
I don't have that option in my bluetooth settings
I don't have any problems with mine so far but just checked my settings and it was on always ask.
Could anyone confirm what it should be set as? I have changed mine to automatic anyways.
Thanks for the heads up.
Phil
Not seeing that option in Android 5.0.1 on my HTC One GE. But I have not been having any of the issues mentioned in the OP.
Sent from my Nexus 10 using Tapatalk
Here is a pic of the screen where you make selection. Always Ask is NOT what you want, which is what is pictured. Select Automatic. Sounds like this isn't available on Android 5.0 from what I see in responses so far.
I don't think I saw this option on any of the ROMs I ran, but there may be devices out there that have it and default to it, and this one would really break wear connectivity - so it may help someone someday.
I'm on 5.0, lg g3 and have both options.
Although i havnt had a problem with always ask and only switched it to automatic tonight.
Judging from the description, it will work as long as the watch stays connected, but a reconnect from the watch side would ask for confirmation (and could be possibly even silently denied under some circumstances).
Phone -> Watch = no problem
Watch -> Phone = problem
and it's possible (and likely) there are more connections going on than just the primary one, and if the connection is flaky there might be a dead one and a new one from either side...
you could just have been lucky, so far
My issues returned last night. I left my watch at home and went to dinner and out with friends, came back home after several hours. I left the watch in theater mode while I was out and over night. I woke up this morning, put watch on and realized the battery had tanked overnight and I was no longer receiving notifications, again, wear app showing connected. I looked at the battery graph for the watch and it is totally flat while I was out last night and appears to tank fast as soon as I got home and my phone was in proximity to the watch again. It's like it is constantly trying to handshake with the phone or something. The only thing that fixes this problem is a reboot of the Watch itself. I still think the connection setting was helpful because I have yet to see battery life like that or a solid link for that long. I would love to know what exactly is going on here. Bad hardware?
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
That's what I have also since I own the watch.
Stbrightman said:
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
Click to expand...
Click to collapse
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
mic18u said:
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
Click to expand...
Click to collapse
Nope, shows also when out of the box so without android debugging.
Just a normal operation notification
I just discovered another possible contributor to connectivity issues: I just tried to use my watch to voice dial and after multiple attempts I got the disconnected message. I took my phone out and Wear app says connected and I had full 4G signal. My phone is set with a pattern lock. After unlocking it and checking the above mentioned, I tried the watch again and it worked. Could locking your phone have something to do with these problems?
I 've had the Urbane for three weeks now, and I'm pretty pleased* with the watch except for a major problem:
I keep seeing that "cloud with a line through it" icon on top of the watch face way to often.
I'm actually looking at it right now - I'm at work, my Urbane is on my left wrist, and my phone is on the desk 20 centimeters away.
Since I haven't heard many others complaining about this, I'm suspecting the problem to be on the phone side - this is a "China phone", an Elephone P3000S (64bit, 3GB RAM) that I bought quickly as a cheap, but (on paper) good spec'd replacement for my broken Sony Z1 Compact.
But nevertheless, I thought I'd asked here if anyone else are experiencing the same?
I've factory reset the watch, I often reboot it, I reboot the phone even more often, and most of the time connection is re-established but lasts only for maybe 15 minutes up to several hours. I have disabled wifi on the watch to see if that improves things - initially I thought maybe it did (as long as I kept the phone nearby, of course), but after a while it seems it's not the case.
Anyone have any other tips? ...Before I replace the phone?
Thanks,
Christopher
*: of course I would prefer a brighter screen (when needed, i.e. outdoors), light sensor, better battery capacity, ...
Try to find out what Bluetooth version the phone has.
grenness said:
I 've had the Urbane for three weeks now, and I'm pretty pleased* with the watch except for a major problem:
I keep seeing that "cloud with a line through it" icon on top of the watch face way to often.
I'm actually looking at it right now - I'm at work, my Urbane is on my left wrist, and my phone is on the desk 20 centimeters away.
Since I haven't heard many others complaining about this, I'm suspecting the problem to be on the phone side - this is a "China phone", an Elephone P3000S (64bit, 3GB RAM) that I bought quickly as a cheap, but (on paper) good spec'd replacement for my broken Sony Z1 Compact.
But nevertheless, I thought I'd asked here if anyone else are experiencing the same?
I've factory reset the watch, I often reboot it, I reboot the phone even more often, and most of the time connection is re-established but lasts only for maybe 15 minutes up to several hours. I have disabled wifi on the watch to see if that improves things - initially I thought maybe it did (as long as I kept the phone nearby, of course), but after a while it seems it's not the case.
Anyone have any other tips? ...Before I replace the phone?
Thanks,
Christopher
*: of course I would prefer a brighter screen (when needed, i.e. outdoors), light sensor, better battery capacity, ...
Click to expand...
Click to collapse
ranf said:
Try to find out what Bluetooth version the phone has.
Click to expand...
Click to collapse
Guys,
Having the same problem as well..... I'm using a Nexus 6 with Bluetooth 4.1 which is also not so far away from my watch all the time..... Really don't know what's going on....
I don't have an Urbane watch (yet) but ran into this issue myself....I downgraded Android Wear on my phone back to 1..0.5 to fix my problem. To get the apk I am using now, see the link below. Before that, my watch would constantly disconnect from the phone for no reason. Best of luck to you all! The Urbane is the BEST looking smart watch out there IMO!
http://www.apkmirror.com/apk/google...roid-wear-1-0-5-1724356-android-apk-download/
Pietje_1985 said:
Guys,
Having the same problem as well..... I'm using a Nexus 6 with Bluetooth 4.1 which is also not so far away from my watch all the time..... Really don't know what's going on....
Click to expand...
Click to collapse
Same here. N6 running CM12.1. Bluetooth works perfectly with car, around home, other devices. I've tried every setting I can think of. Glad to hear I'm not the only one.
Have you tried enabling/disabling the wireless syncing option? I had similar initial issues, had to factory reset and I disabled Wireless Syncing (and deleted the cloud data).
I then setup the phone again and didn't enable wireless sync for a few hours so I knew the phone was setup and working only using Bluetooth.
I knew something was wrong as once the wireless Sync was disabled and the cloud info deleted, my watch said it had lost connection to the phone and I had to factory reset it (even through Bluetooth was enabled still).
I am having significantly more instances of Bluetooth disconnections on this watch that I did with the Moto 360. This especially occurs in my car while driving. I'd bet that the watch disconnects every 10 minutes or so in the car.
Same here ... I have an LG G3 running Lollipop with an LG Watch Urbane running v5.1.1 This is to replce my LG Watch R but these connectivity issues every 10 seconds is highly frustrating ... Looking forward to a permanent fix on this thread ...
I'm starting to see the same thing, no issue while both are on WiFi, but without WiFi my watch is constantly disconnecting. Normally rebooting the watch seems to fix the issue, but really hope this gets fixed soon.
If I get away from my phone watch disconnects, thats normal. But when I get close to phone again, it doesn't connect automatically, or connects too late. Is that normal? This is so annoying.
well im all good not had that at all i get about 25 foot then loose bt soon as im back in 25 foot im good
i have a edge
I have an SGS6 Edge and it is slow connecting. I've found it will connect instantly if I turn BT off and back on.
Has anyone tried using phones wifi terhering instead of bt connection? Maybe that extends the connection distance?
Seems like my problems are solved for the most part. Doesn't disconnect that often anymore. Could be because of recent update to Android 5.1.1 on my Nexus 6 and I factory resetted my urbane! Lookin' good now!!
How about you guys?
I have a Nexus 6P, and the disconnecting with my Urbane is beyond annoying. I'm starting to think that, despite the looks of the Urbane, the watch itself is a pile of poo.
Same issue here. Phone and watch constantly disconnect. If I walk 10 feet from my phone, it disconnects and doesn't reconnect when I come back within range of the bluetooth.
Pleased to report, though, that I went into Settings>Apps>Android Wear and cleared the cache and the phone has been reconnection pretty well. I have the LG V10 and the G3 before that and have found that you have the clear the cache on bluetooth connections every once in a while, and then things start to work smooth again.
Hope this helps someone out there.
I have been having the same problem since I got my new Nexus 6P. On my old phone, an Asus Zenfone 2, I would hardly ever lose connection. I might drop connection once a day. With my new phone, its about once an hour if I'm lucky. I just did a factory reset of both the phone and watch this evening, and so far it seems to have helped but I'm not going to call it fixed yet until I make a whole day without losing connection.
For what its worth, there are tons of people who are saying the BT on the N6P is boned, as well as a ton of people saying the same thing about the Urbane.
I have a Samsung Galaxy S6 and have both Bluetooth and Wifi connected to my LG Urbane however:-
If I go away from phone - within my own house AND well within Wifi range - it LOSES connections to BOTH Bluetooth and Wifi. (Bluetooth I can understand but how come it is losing connection to Wifi)?
Anyone got any answers please?
Hi guys, hope somebody will help me. I have an Urbane, and a Nexus 5X, both upgraded to the last versions of Wear and Marshmallow. The thing is, I can't make a daily wake up alarm to work. Every night I put both the watch and the phone on plane mode; and the watch's screen off. Both have the same alarm set: 7am from Monday to Friday, but only the phone's works. I've made a factory reset of the Urbane, and nothing has changed. I don't know what else I can do. Any thoughts?
Hello,
Am i alone with this problem ?
How to fix it ? -> https://youtu.be/txf2krXf2xs
Redo the link... I'm getting video not found
dadoc04 said:
Redo the link... I'm getting video not found
Click to expand...
Click to collapse
could you try again please ?
Wow... Don't think I've seen that 1 before... Mine won't even rotate into that other position
Hmmmmm
dadoc04 said:
Wow... Don't think I've seen that 1 before... Mine won't even rotate into that other position
Hmmmmm
Click to expand...
Click to collapse
i have tried 2 resets data factory without change
Never had that problem, only rotates when docked and charging.
That was unexpected, haven't seen the behavior with mine and this is the first I've read of it. Time for an exchange?
krabman said:
That was unexpected, haven't seen the behavior with mine and this is the first I've read of it. Time for an exchange?
Click to expand...
Click to collapse
i have bougth it on US Play Store from France...............
waiting for Play Store french, but it's not available for the moment..
Resolved !
yesterday i released my Pixel with Android O preview 2, and after i did a reset data factory on my LG Sport watch, i was wearing it during the firts start ans the screen do not turn anymore !
great, its a bug if you keep the watch on the charging dock at the first start (tryed 3 times...) the screen always turns after...
I had the same issue in the beginning, did the same thing as you did ^^
I've found the reason :
Eatch time I started the watch for the first time, it was on his charger dock...
The Last time I did it, the issue was not. ?