First of all, I really like my galaxy watch 5 pro. I often take my LTE version when I go running, connected to my Galaxy buds live. There are certain issues I have, which drive me bananas:
When it passes a marker (for example, every mile), it breaks up the music, briefly. Usually only for the first one or two markers. And then it reappears later, sometimes. Definitely an intermittent issue. It's like, it pauses and tries to figure out what it is supposed to do: the watch is like 'Do I pause,? do I stop the music? Do I act like there's a major blast of Wi-Fi in the area news connection?' it's like it has a conflict going on inside it.
Secondly even when I've got it on do not disturb, if someone phones me or there are certain kinds of messages that go to my phone, they still forward!! The worst is if somebody calls me, it stops the music! And it's almost impossible to stop the call while running! And I can't restart the music without really fiddling around with the watch, and that is really difficult to do without losing your pace.
It's not a great running watch in my opinion. Samsung needs to fix some things here.
Am I the only one? Maybe it's my watch.
ekerbuddyeker said:
First of all, I really like my galaxy watch 5 pro. I often take my LTE version when I go running, connected to my Galaxy buds live. There are certain issues I have, which drive me bananas:
When it passes a marker (for example, every mile), it breaks up the music, briefly. Usually only for the first one or two markers. And then it reappears later, sometimes. Definitely an intermittent issue. It's like, it pauses and tries to figure out what it is supposed to do: the watch is like 'Do I pause,? do I stop the music? Do I act like there's a major blast of Wi-Fi in the area news connection?' it's like it has a conflict going on inside it.
Secondly even when I've got it on do not disturb, if someone phones me or there are certain kinds of messages that go to my phone, they still forward!! The worst is if somebody calls me, it stops the music! And it's almost impossible to stop the call while running! And I can't restart the music without really fiddling around with the watch, and that is really difficult to do without losing your pace.
It's not a great running watch in my opinion. Samsung needs to fix some things here.
Am I the only one? Maybe it's my watch.
Click to expand...
Click to collapse
A possible reason for the break in the music could be that you are switching between cell towers and there is possibly a gap in the signals, happens to me sometimes when driving down motorways. or maybe there is a setting somewhere to inform you when you reach these markers and its briefly trying to silently play another sound idk dont own the watch so cant really say what the problem is except for some general things it could be.
Secondly bugs bugs and more bugs, dislike them a lot myself lol
What fitness app are you using? I don't wear earbuds when running but Strava seems to work really well. A good fitness app will allow you to customize notifications. Maybe consider disabling wireless data when running.
It drives me bananas. I went on a run today. As it starts telling me my lap info, the music cuts out, the voice is a bit broken up, and then, when I'm in an area with trees, it must confuse the gps which makes the watch decide that I have 'lapped', and it starts giving me new lap times every 5 seconds!!! Makes it impossible to use with earbuds. MYne it is the combination of everything going on, and I admit it's a lot, data, voice ready, music to Bluetooth, gps, Samsung health app running etc... But they sell this as a WORKING solution, and it so often doesn't work properly (for me).
ekerbuddyeker said:
It drives me bananas. I went on a run today. As it starts telling me my lap info, the music cuts out, the voice is a bit broken up, and then, when I'm in an area with trees, it must confuse the gps which makes the watch decide that I have 'lapped', and it starts giving me new lap times every 5 seconds!!! Makes it impossible to use with earbuds. MYne it is the combination of everything going on, and I admit it's a lot, data, voice ready, music to Bluetooth, gps, Samsung health app running etc... But they sell this as a WORKING solution, and it so often doesn't work properly (for me).
Click to expand...
Click to collapse
I just went for a 2 mile walk while listening to earbuds through the watch and Samsung Health was monitoring it and it worked perfectly.
Ok, I may have solved the issue. Will be testing it soon. I switched from Samsung to Google text so speech engine.
Related
I have owned pretty much every Galaxy phone so far and though I've loved each one, there's a few completely annoying issues that I end up having solve through a custom ROM, launcher, a developer script, or something along those lines. I thought for once with the Note 4 I would be able to for once keep everything stock besides having it rooted but it looks like I was wrong.
The issue I'm having right now is driving me through the wall. My phone answers phone calls AUTOMATICALLY ON ITS OWN when connected to BLUETOOTH.
It happens consistently, the exact same way, every single time. When I'm connected in my car it answers after exactly 2 rings (2 seconds). It is getting ridiculous and sometimes I just want to toss the phone out of the window while I'm driving down the freeway. Its extremely annoying to have your phone answer a call that you absolutely no intention of answering, ESPECIALLY WHEN I'M DRIVING. I'm tremendously busier in the past year and don't have time to sit and tinker like I used to or I'm sure I would've either solved this or gotten a new phone by now.
I already made sure auto-answer is OFF: Settings > Call > Call Accessories > Automatic answering [Box is not checked]
THIS IS DEFINITELY AN ISSUE WITH THE PHONE BECAUSE IT HAPPENS ON ALL 3 OF MY CARS & 2 OTHER CARS I'VE TRIED.
Please, if anyone knows how to fix this issue or anything about this completely ridiculous issue, please share.
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?
I bought the Watch R a week or so ago and I've been trying to work out why the Google Now notifications are so unreliable.
At first, I thought it was just me - I never really embraced Google Now and actually had it turned off on my phone (Galaxy S6 Edge). A few days ago I turned it on, configured it and was expecting to see the odd card popup on my watch every now and then but I've had zip.
So, I thought I'd test the notifications on the watch, from the Android Wear app, but the only notification that works all the time is the phone call. Most of the other notifications just don't pop up on screen and the only way I see them is to swipe the face from above and then they're there. Is this normal behaviour? I thought that notifications were supposed to popup on the screen, like on my phone!
I've reset the phone a couple of times in desparation but it's made no difference. I've unpaired the watch from the phone and re-paired it after forgetting the device. No difference. Removed all the custom watch faces and used only the once that came with the watch and once again, no difference.
I do get notified of text messages and emails with no problem, but nothing from Google Now.
Can anyone please suggest anything?
I have the s6 and I don't receive any notifications except the test phone call. I believe it to be a samsung problem with it killing the wear app from running in the background. watch worked fine with my other phones.
It's ridiculous, my s6 / gwr doing the same thing. Reboot both and things work for a little while, then gradually peters away to nothing. Except for sometimes I'll tap the watch for the time, and some random google now cards will be there, which I dismissed days before! Swipe them away but the same few keep coming back! As for the weather reports, well they've not worked for over a month now. And all this without me touching any settings whatsoever. I've exempted the android wear app from battery optimisation in the s6 too, incase they were that dense they'd overlooked that core app, but doesn't seem to have sorted it. Seems every time these companies update stuff they break it, and don't care about fixing it.!
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
Have you tried doing a reset?
When I got mine, it upgraded straight away so I thought "great", it's a clean watch, there can't be anything wrong with it.
Nope..
Apps didn't work.
Battery life was rubbish.
Did a reset when i got a new phone.
Apps worked without issue.
Battery takes me from 5am through to 9pm with 40% left at least, LTE is off but aod is on.
Yes - reset the watch to factory when I deleted the app, pairing etc - went totally to step 0 across the board, short of formatting over the phone itself. But I did one more reset after that last night and charged it all night. So far this morning (wrote most of my note locally last night, posted this morning) I'm holding up pretty well. Nothing running on the watch - bone stock with phone shut off and Ok Google off. 2.5 hours @ 91%. Fingers crossed that this was a fluke. But in my experience today is probably the fluke LOL.
wig said:
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
Click to expand...
Click to collapse
Sorry to bump an old thread how is your usage the last few months? I'm confused between buying this and the huawei watch 2.
Thank you @wig
Sent from my Sony Xperia XZ1 using XDA Labs
No worries. The LGWS has been pretty decent. It seems to me that its bluetooth radio gets confused. For example, when I'm in my car, sometimes the watch disconnects or the car bluetooth disconnects. When I'm in my home office where the WIFI router is, the watch seems to disconnect as well. Beyond these weird edge cases, it stays connected and just works. The disconnecting isn't really bothering me as much as the fact that when it does, it tries to connect over WIFI and drains the battery pretty quickly. I've kind of learned to live with it and the hardware in this watch is better than the HW2. That being said, my experience with connectivity was much better with the HW2. Not sure how it's going now for those who have it. Android Wear has updated both the IOS app and the core OS and apps numerous times since I posted this. So for all I know, HW2 is doing the same thing these days. It does appear Google is trying.
As for the LGWS - go to ebay, find yourself a new one that's super cheap. I ended up getting mine for around $170 which made it a no brainer. One of these days I'll throw a SIM in it just to try it, but have bigger fish to fry at the moment.
Best of luck.
P.S. I just saw you have an android phone - so your mileage may vary and in fact will probably be MUCH better. I'm on iPhone which is 90% of the issue.
wig said:
No worries. The LGWS has been pretty decent. It seems to me that its bluetooth radio gets confused. For example, when I'm in my car, sometimes the watch disconnects or the car bluetooth disconnects. When I'm in my home office where the WIFI router is, the watch seems to disconnect as well. Beyond these weird edge cases, it stays connected and just works. The disconnecting isn't really bothering me as much as the fact that when it does, it tries to connect over WIFI and drains the battery pretty quickly. I've kind of learned to live with it and the hardware in this watch is better than the HW2. That being said, my experience with connectivity was much better with the HW2. Not sure how it's going now for those who have it. Android Wear has updated both the IOS app and the core OS and apps numerous times since I posted this. So for all I know, HW2 is doing the same thing these days. It does appear Google is trying.
As for the LGWS - go to ebay, find yourself a new one that's super cheap. I ended up getting mine for around $170 which made it a no brainer. One of these days I'll throw a SIM in it just to try it, but have bigger fish to fry at the moment.
Best of luck.
P.S. I just saw you have an android phone - so your mileage may vary and in fact will probably be MUCH better. I'm on iPhone which is 90% of the issue.
Click to expand...
Click to collapse
Thank you so much for your reply I think you have sold me the watch. Now I can continue my search to try and find one. Seems at $170 that's definitely a bargain let me know if your wanting to sell ?
Sent from my Sony Xperia XZ1 using XDA Labs
Well, this seems to be a common issue that Asus support knows nothing about. I have learned that Asus support is worthless, but I will leave that rant for another post. Anyway, I am having the same issue that many other people seem to have, but I haven't been able to find a solution for it. I have a 6P, latest Android Wear on the phone, latest Android Wear on the watch, and it usually takes 15-30 seconds for the watch to "ring" when I get a phone call. Additional details below.
Here is, in detail, what I have noticed. If I have used the watch recently (sorry, can't provide an accurate, or even estimate time fraim) it seems to work fine, however if it hasn't been used in a while, it can take 15-30 seconds for the watch to notify me of an incoming call. I am used to my pebble, where notifications that take 2 seconds are VERY long delays, usually its instant with the pebble. This also appears to be an issue when an alarm goes off. Alarm, as in set an alarm in the clock app, it takes forever to get the notification on my watch. As far as phone calls, it also seems as though if I answer the phone before the watch starts ringing, the watch can start ringing after I have answered the phone, and am talking on the phone, and the watch won't shut up until the call has ended.
I assume there is a simple fox for this, but I can't find it anywhere. For details, the watch is running 2.8.0.182823779 (Latest at the time of writing) the phone is running 8.0.0 rooted, android wear 2.9.0.185084575.gms (Latest at time of writing)
Practically begging for help here, thanks in advance.
I assume you are using stock AW 2. Everyone of us has had problems with the speed of the watch. The snapdragon 1200 seems to be to slow and old for AW 2. But if you try the ROM available here in the forum made by @janjan , it get's a little bit better.
You have to disable ZenWatch Manager on the watch and uninstall on your phone.
The Zenwatch manager actually processes lots of data before notifying the watch. Hence the lag.