Related
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
FSRBIKER said:
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
Click to expand...
Click to collapse
Go retrain it once more in a completely silent room. You should be able to hear nothing except air moving (fan, a/c, etc.). Then report back.
FSRBIKER said:
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
Click to expand...
Click to collapse
Biggest thing is keep it at arm's length. Like really, extend your arm to the fullest, and then speak normally. Try it.
natezire71 said:
Go retrain it once more in a completely silent room. You should be able to hear nothing except air moving (fan, a/c, etc.). Then report back.
Click to expand...
Click to collapse
jhnl33 said:
Biggest thing is keep it at arm's length. Like really, extend your arm to the fullest, and then speak normally. Try it.
Click to expand...
Click to collapse
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
FSRBIKER said:
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
Click to expand...
Click to collapse
Good luck! I had the same issue as you in the beginning. I uninstalled updates and reinstalled to try to make sure previous cache and settings were cleared and re-trained at arms length and now it works pretty well!
FSRBIKER said:
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
Click to expand...
Click to collapse
also, make sure you use the same pitch and cadence when saying it. If i want the phone to pick up my voice easier, i can say ok google now when training it in slightly different ways. But then my phone also comes on and thinks im saying it when no one has said anything close to ok google now. If you make sure everything sounds the exact same when saying it, i didn't run into any problems. But i can't wake the phone up when i first wake up in the morning lol. I always try but i apparently sound like death whenever i first wake up.
jayboyyyy said:
also, make sure you use the same pitch and cadence when saying it. If i want the phone to pick up my voice easier, i can say ok google now when training it in slightly different ways. But then my phone also comes on and thinks im saying it when no one has said anything close to ok google now. If you make sure everything sounds the exact same when saying it, i didn't run into any problems. But i can't wake the phone up when i first wake up in the morning lol. I always try but i apparently sound like death whenever i first wake up.
Click to expand...
Click to collapse
I agree, try using the same voice for all three samples. I know that early on people were suggesting you say it with slightly different speed etc but I have found it is best to try to say it the same all three times and let the software in the Moto X handle slightly variations automatically.
Mine wakes up all day sitting on my desk at work. I do talk about Google a lot, but I never say my phrase. It's funny some of the stuff I see it type...
Sent from my XT1060 using Tapatalk
This is an interesting thread for me. I had the Note 3 (hi galaxy) and Nexus 5 (ok google). Both of them would think I was talking to them when I wasn't, and I have almost the opposite problem with the Moto X. I have a hard time to get it to listen. I re-trained, re-trained, re-trained.. My wife's phone works flawlessly. I do love that we train our voices because she uses here touchless control all the time right next to me and my phone has yet to mistake mine for hers.
Maybe I need shorter arms.
OK quick update, I uninstalled the Touchless Control update and retrained my Moto X again in my garage this morning. It's been about 7 hours and it hasn't once yet turned itself on. I streamed music, have been in congested areas with people, a business meeting and it's working perfectly now.
I'm going to wait for 24 hours to make sure it's still working correctly and then install the update to the app.
About ready to scream!
The touchless control on my Moto X Developer Edition is extremely sensitive. Anytime anyone talks in the office that I work in, the dang phone comes on and waits for someone to give it a command. All anyone has to do is say "OK" and it does this even when I don't want it to. I've tried retraining the phone multiple times and it doesn't seem to help me out at all. I'm going to be so glad when the Lollipop update finally rolls out for this phone so I can get retrain this with a different launch phrase that will not be so easy to trigger on my phone. In the meantime, has anyone been able to get the sensitivity adjusted on this phone? If so, how? I'm thinking of going to Cyanogenmod 12.1 until Lollipop rolls out for the XT1060,
Any help that I can get on this would be greatly appreciated.
Cindy
So I've had my G4 for a couple months now, and I've noticed the GPS is literally almost worthless. My location is set to on and high accuracy. My usual routine is to look up the route before I leave my driveway like any normal person. The GPS locks on after a while, and when I start driving is the problem. It either won't update to my moving position (I live in Pittsburgh and T-Mobile's coverage is pretty good) and will frequently freeze. Or it will randomly start locking onto random locations around my area but not on my car. This is incredibly frustrating obviously because I absolutely need my GPS to work. Does this sound like a hardware problem and how do I prove it to T-Mobile to get a replacement device?
With a clear sky, my GPS is amazing. But with heavy cloud cover I cannot get a decent lock.
Seems the AGPS (tower based location) is worse on this than any device before. Even with Wi-Fi on.
Sent from my LG-H811 using Tapatalk
Came here to post the same thing.
For some reason, over the last few weeks, my gps started going bonkers for no reason. It will work just fine for 20 min and then all of a sudden it will keep thinking that I am 70 feet west of where I really am. So if I'm driving south on the highway, it thinks I'm driving parallel to the highway but 70 feet to the right of the highway. So whenever there is another road nearby, Google Maps thinks I'm on that road and tries to reroute me to get back on the highway. If there is no other road nearby, Maps will correct my location to the highway. It is really frustrating because it becomes useless with intersecting roads and constant erroneous rerouting. The arrow keep jumping back and forth and the app is giving me false rerouting instructions non-stop. Not to mention the map keeps rotating around because it gets confused about which direction I'm headed. Super confusing.
Once I reboot the phone, everything goes back to normal and the gps is once again super accurate (until it happens again).
This issue happens every other day or so.
I did update to 10N as well as rooting and putting TWRP on it a months ago (around the same time these issues started). Not sure if the bug was introduced with 10N or if it's related to the root and TWRP (doubt it).
I started really hating this phone as I keep getting lost while driving.
majp89 said:
So I've had my G4 for a couple months now, and I've noticed the GPS is literally almost worthless. My location is set to on and high accuracy. My usual routine is to look up the route before I leave my driveway like any normal person. The GPS locks on after a while, and when I start driving is the problem. It either won't update to my moving position (I live in Pittsburgh and T-Mobile's coverage is pretty good) and will frequently freeze. Or it will randomly start locking onto random locations around my area but not on my car. This is incredibly frustrating obviously because I absolutely need my GPS to work. Does this sound like a hardware problem and how do I prove it to T-Mobile to get a replacement device?
Click to expand...
Click to collapse
Is this the same type of GPS issue on Samsung flagships? Those require opening up the phone and lifting up the GPS leaf pins.
Sent from my SM-G386T using Tapatalk
aptalca said:
Came here to post the same thing.
For some reason, over the last few weeks, my gps started going bonkers for no reason. It will work just fine for 20 min and then all of a sudden it will keep thinking that I am 70 feet west of where I really am. So if I'm driving south on the highway, it thinks I'm driving parallel to the highway but 70 feet to the right of the highway. So whenever there is another road nearby, Google Maps thinks I'm on that road and tries to reroute me to get back on the highway. If there is no other road nearby, Maps will correct my location to the highway. It is really frustrating because it becomes useless with intersecting roads and constant erroneous rerouting. The arrow keep jumping back and forth and the app is giving me false rerouting instructions non-stop. Not to mention the map keeps rotating around because it gets confused about which direction I'm headed. Super confusing.
Once I reboot the phone, everything goes back to normal and the gps is once again super accurate (until it happens again).
This issue happens every other day or so.
I did update to 10N as well as rooting and putting TWRP on it a months ago (around the same time these issues started). Not sure if the bug was introduced with 10N or if it's related to the root and TWRP (doubt it).
I started really hating this phone as I keep getting lost while driving.
Click to expand...
Click to collapse
Have you tried using Device Only mode? I noticed that once I did that accuracy went to 100% while driving.
I think it's a software issue that shows up when the phone is not using the GPS and instead relying on WiFi and Cell for location.
Joe USer said:
Have you tried using Device Only mode? I noticed that once I did that accuracy went to 100% while driving.
I think it's a software issue that shows up when the phone is not using the GPS and instead relying on WiFi and Cell for location.
Click to expand...
Click to collapse
You know, you might be onto something about the assisted gps part (cell and wifi)
Shortly after I posted the message, I started using this app called GPS Status & Toolbox. It has a feature of clearing and updating the assistance data (A-GPS) which it can automatically do once a day. Since I started using it, I haven't had the issue.
It's possible that there is a software glitch regarding cell and wifi assist
Los Angeles got hit by El Nino pretty hard with thick clouds for about a week but didn't have any issues with my navigation. I use TomTom go, Google map, waze, and MS Here depends on my mood but all were accurate. I haven't done anything to my phone except turning off WiFi assistance for GPS, you think that has anything to do with it? I think it was called WiFi scanning under advanced WiFi setting.
I find the LG G4 gps to be one of the best among the phones I have used. I have had Note3, Note4 before... those had horrendous gps performance issue.
I keep trying different faces, but some seem to work correctly at first but then get stuck & stop updating. I had one running that I thought worked great & then today it said it was cloudy/rainy & 56° out even well after it got warm & sunny.
~John
re: weather info.
jmorton10 said:
I keep trying different faces, but some seem to work correctly at first but then get stuck & stop updating. I had one running that I thought worked great & then today it said it was cloudy/rainy & 56° out even well after it got warm & sunny.
~John
Click to expand...
Click to collapse
Good question!
I have the same problem too.
Also when I click on the weather on the watch face it
displays different results than what the weather app
displays on the watch face itself.
I must have tried 25 different weather apps for android wear
and so far not one of them were any where near accurate
enough for me to actually use any of them.
Good luck, have a great day!
Also when I click on the weather on the watch face it
displays different results than what the weather app
displays on the watch face itself.
Exactly. I'm giving up on watch face weather for now
~John
I've been using this watchface since I got the watch in november:
https://play.google.com/store/apps/details?id=mobi.byss.instaweather.watchface
I'm in Finland and I've been happy with the weather data, it's not 100% accurate, but accurate enough for daily use.
Most watch faces I've tried have been really weak in showing accurate weather data from smaller countries.
yearly subscription?? Eer, no thanks.
I would gladly pay a one time fee for a good app, but this is ridiculous.
~John
I have been trying a face I made with WeatherTime & so far today it has worked fine.
That means absolutely nothing however, as some of the other faces seemed to work in the beginning but then simply stop updating no matter what the settings are.
~John
My guess is that it's related to connectivity issues between the watch and phone. My watch and phone constantly disconnect from each other. At 4pm today for example, it was still showing the temp for 9am. Jeeze!
weather time seems to work pretty well for me (way better than anything else I've tried) So far, it always seems to me within a few degrees of what my phone is reading & is at least useable.
~John
I know this thread is a bit old, but I use a WatchMaker face. While WatchMaker (search on the Play Store) requires you to purchase a license to put watch faces on your watch, it is totally worth it. You get to make your own faces and use other peoples faces. Look up "facerepo" for a site that has tons of watch faces. To get accurate weather, you have to go into the app's settings on your phone, and configure the weather settings to update every half hour.
I'm sticking with weather time. It works perfectly 99% of the time.
It got stuck once on the temp, but in the phone app you can click force weather refresh & then it's fine again. I do have my phone (galaxy S8 Plus) set to update every 30 minutes.
~John
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
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.