Hey there. I've followed all the necessary steps when it comes to setting up the Gear Fit with my Nexus 5. There are no issues pairing, all is well in that regard, however, the date and time on the Gear Fit are way off. It's stuck in November and tells me my birthday in the 80s is in the future when setting up my profile. No matter how often I pair, unpair, reset, whatever, the correct time settings won't push to the watch. Are there any fixes for this? Or should I abandon hope of using it with the Nexus 5 and return it?
Related
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
mickmel said:
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
Click to expand...
Click to collapse
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
EDIT:
PS. It is worth noting that the watch does NOT display the disconnect icon when this happens (usually if you walk out of range you get a little cloud with a line through it)
Azarin said:
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
Click to expand...
Click to collapse
I'm not getting extended disconnects; just failing to answer questions about half the time. If it fails, I can try again and it often works.
mickmel said:
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
Click to expand...
Click to collapse
I just got my LG G Watch and paired it with my stock Moto X running 4.4. It paired no problem but I would say 95% of the time I get a disconnected message when doing a voice search. It is pretty infuriating.
Notifications still seem to come through and I still get served cards but voice search fails almost all the time. When I initially went from Wifi to 4g it worked for one search and then back to disconnected. It doesn't seem to be a phone problem since people on here are using a number of different phones. This is a bug that needs to get fixed ASAP by Google.
I am disappointed but hopeful they can get this quickly fixed.
I'm experiencing the exact same thing on my Gear Live. Its paired with stock S5. I just tried for like 5 minutes to get it to save a note and it would think for a while and then just disconnect.
mosi76 said:
I just got my LG G Watch and paired it with my stock Moto X running 4.4. It paired no problem but I would say 95% of the time I get a disconnected message when doing a voice search. It is pretty infuriating.
Notifications still seem to come through and I still get served cards but voice search fails almost all the time. When I initially went from Wifi to 4g it worked for one search and then back to disconnected. It doesn't seem to be a phone problem since people on here are using a number of different phones. This is a bug that needs to get fixed ASAP by Google.
I am disappointed but hopeful they can get this quickly fixed.
Click to expand...
Click to collapse
This is exactly everything I've noticed as well.. Seems to have gotten waaaaay worse after yesterday's update
Azarin said:
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
EDIT:
PS. It is worth noting that the watch does NOT display the disconnect icon when this happens (usually if you walk out of range you get a little cloud with a line through it)
Click to expand...
Click to collapse
Happens to me, too. Completely random though. Repairing the watch fixes it, but it is indeed annoying. We will have to wait for Google to fix this together with all the other bugs.
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
iHelp101 said:
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
Click to expand...
Click to collapse
Thanks, I'll give it a shot.
What about trying to reply using voice within a received Hangout or email? I'm always getting an error "Can't reach Google at the moment". Am I the only one? But if I select a default reply from the available list, I can reply with no problems...
iHelp101 said:
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
Click to expand...
Click to collapse
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
barkside said:
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
Click to expand...
Click to collapse
I found it only improves it a little, but it's not a full fix. Sometimes my watch works the whole day without connection problems and then suddenly multiple times in a short period of time.
I've read that the gear live has the same problem, so I guess it's android wear wide. Hopefully google is going to bring out an update soon which fixes all the annoying bugs.
barkside said:
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
Click to expand...
Click to collapse
Like stated by the previous post this is a simple fix. The only one that can truly fix the issue is Google. I have used this for a week and not had any issues relating to bluetooth disconnecting. One issue I noticed was Google Search sometimes breaks after using it multiple times in a short amount of time. I usually have to just force stop Google Search every 3 days also.
This has always been an issue I had even before Android Wear. If I used Google Now too much I couldn't get the "Okay Google" command to work. It seems this also happen when using wear too much. A simple force stop fixed it, but it is annoying when you want it to just work. Another thing I noticed was custom roms are having issues with Android Wear in my case.
Every time I use a custom rom on my Nexus 5 and try to use my LG G Watch I have constant disconnects and Google Search issues. Maybe Android Wear isn't playing nice with custom roms, but after using rooted stock for the last week I am experience very few issues compared to when using different custom roms. I noticed whenever I used a custom rom I got the "Connected, running sync loop". I have no idea if this causes the constant disconnects, but on stock with the simple "Connected" I have no issues.
I started out with the same problem using a Gear Live with a Sony Xperia Z1 Compact. The thing that fixed it for me was turning off battery saving mode on the phone - called stamina on the Xperia - that was turning off BT to save power. Now I rarely see the disconnected message.
Anyone found a solution to this problem?
My lg g watch also disconnects 90% of the time from my note 4. Anything from ok google to search or ser a reminder or or or
SIlvRav said:
Anyone found a solution to this problem?
My lg g watch also disconnects 90% of the time from my note 4. Anything from ok google to search or ser a reminder or or or
Click to expand...
Click to collapse
I have found this issue for Android Wear for my LG G watch R and Galaxy Note 3. If I use watchmaker, I have it set to vibrate twice upon disconnect and vibrate once upon connect. It is constantly disconnecting and immediately reconnecting (2 vibrations, followed immediately by a single vibration). This is extremely annoying and I see the same problem stated in the beginning, the voice search is constantly disconnected or cannot reach the server.
Cheers,
B.D.
So, I've had my Gear S now for about a week, and LOVE it. The connection stuff has me a bit confused though. I have it paired with an AT&T Note 4. There are a few things I have questions about...
If I reboot the phone, the watch will only connect to Gear Manager remotely. Shouldn't it connect to Bluetooth first? I have to go into Gear Manager and disconnect the remote connection, then it will reconnect via Bluetooth.
Under what circumstances does the phone forward calls/sms to the watch? For example, on purpose, I left my phone at home one day, and went out for a drive. Calls and SMS that were made came from the watch's number. I can't say about the receiving end because I didn't receive anything LOL.
Sometimes, if I go out of Bluetooth range at home, the home wifi will kick in, but repeatedly get a message on the watch that the forwarding function failed.
I'm definitely keeping this baby, but just need a little help in understanding it fully.
diehardbattery said:
So, I've had my Gear S now for about a week, and LOVE it. The connection stuff has me a bit confused though. I have it paired with an AT&T Note 4. There are a few things I have questions about...
If I reboot the phone, the watch will only connect to Gear Manager remotely. Shouldn't it connect to Bluetooth first? I have to go into Gear Manager and disconnect the remote connection, then it will reconnect via Bluetooth.
Under what circumstances does the phone forward calls/sms to the watch? For example, on purpose, I left my phone at home one day, and went out for a drive. Calls and SMS that were made came from the watch's number. I can't say about the receiving end because I didn't receive anything LOL.
Sometimes, if I go out of Bluetooth range at home, the home wifi will kick in, but repeatedly get a message on the watch that the forwarding function failed.
I'm definitely keeping this baby, but just need a little help in understanding it fully.
Click to expand...
Click to collapse
With my S5 initially, Remote Connection would kick in after a few minutes out of Bluetooth range. But, when I was back in Bluetooth range, I would have to do what you are doing to drop RC. I had a Gear 2 Neo prior to Gear S, don't know if that was any issue. .I did a factory rest on S5 ( to get rid of root and some other things) , and now watch connects and disconnects to RC by itself and rather quickly. BTW, when in RC, all texts and calls to S5 do come to Gear S. If I were in your shoes, I might try to reinstall Gear on phone before wiping phone. IF you do wipe phone, Gear S will be reset during the pairing process, so you may want to back up your Gear S data prior.
Op. Under settings-connections-mobile network, do you have it set to auto connect? On the phone side of things for Bluetooth settings, gear s contented to phone audio?
jerrycycle said:
Op. Under settings-connections-mobile network, do you have it set to auto connect? On the phone side of things for Bluetooth settings, gear s contented to phone audio?
Click to expand...
Click to collapse
Yeah, all that was set, but I ended up wiping both the phone and the watch and everything seems fine now... Still loving the watch... wondering how they'll make the next one better..
hi!
i cant talk about heart rates or sport related issues, i havent got the time to use the watch in work outs yet (if i ever get the time).
main reason i got mine was due to having access to messages and alerts without the need to reach the phone (and it aint that good, i can only read last message from apps).
mine was chinese, then flashed the stratOS rom and, now, international rom.
since i got the international rom, and updated to last version, ive noticed a few things, most of them, lagging.
- taps on the watch screen are now less responsive, needing a certain level of pressure (but it may be some impression due to lagging, see bellow);
- some icons dont react right away when tapped. some dont react at all (you can see the icon visual feedback but the watch dont perform the command);
- phone-to-watch distance reminder now lags to the point of going away from the phone and coming back and, then, receiving the warning im far away from the phone;
- phone-to-watch distance reminder now alert im far away from the phone when im not (i suspect the blutooth strength has been reduced, im receiving this alert a lot when the phone is on my backpack, on my back).
anyone else experiencing these? or any other issue?
ill use this chance to inform: if youre getting the health center being unable to sync problem (forgot the proper warning words), this helps:
it probably started happening after you rebooted the watch and already have a profile set on the amazfit app. watch format for weight, height and distances are probably back to default and now differ from the ones you changed in your profile.
go back to your profile and also on your watch and recheck all the formats. when theyre the same, phone and watch should be able to sync health data again.
Note that the F° displayed on the watch comes from the weather app on the amazfit app. go there to change F° to C° on your watch.
Hi All.
I recently got an Amazfit Stratos and I am having a horrible time trying to gps track my outdoor cycle.
I have tried twice, and both times, the GPS just either:
*Intermittently records data
or
*stops recording gps data altogether.
Basic questions?
Urban areas and Woods... same issue
Urban areas are residential.. no high tall building
Weather was good on both occasions
Yes I am waiting for GPS lock
Heart rate and time measurement continue flawlessly (shows data for the entire ride). It's just GPS tracking that is totally weird.
P.S. It's not "drifting" or inaccurate.. it seems to only switch on the gps sporadically... recording "every now and then"...
No errors or issues reported during the activity.
Latest Firmware (Although last nights a new firmware popped up, haven't tried the activity with last night's firmware.)
Both previous activities was on latest firmware at the time. (Yesterday and the day before)
And the REAL issue for me really, is that my wife's Pace records perfectly on the exact same routes where my Stratos just can't get anything usable going...
I have logged "feedback" request with logs using the app, but have not had any response other than, thanks.. we may use your feedback in the future...
From my own conclusions, the gps works.. because when it tracks... the location where it tracks is accurate.. it just doesn't track constantly. See my attached screenshot of my last ride. (Where my wife and her Amazfit pace tracked perfectly)
Any Ideas?
Cant add the image due to post count... How do I add it to this post?
Have you tried factory reset of the watch? Procedure is to unpair it from the app, it will reset itself, start fresh clean and ask for a pairing.
After pairing it will load last 7 days of your work, while all other old data will remain in the app, on your Mi account cloud. What you will have to add separately are only the 3rd party watchfaces, if you have installed them before.
Strongly suggest you try this first, it takes 5 minutes of your time, and you will lose no data.
image
https://ibb.co/rcJXcyx
Thanks Nidza. I will surely try this. I have not yet as the watch is brand new. Upon receiving it It upgraded firmware 3 times from out of the box, and then I started using it.
I will give it a try, surely cant hurt.
Well what do you know. That factory reset seems to have done the trick!
Thanks!
Some points worth noting:
from the factory settings, a few watch settings did not pull through from the sync back to the app after factory reset.
Time format: My previous time format was 24h (Doubt that makes a difference)
Auto Sync: After factory reset, auto sync is off (I had it "on" before). Can't say if this actually causes any bugs to pop up? Maybe the watch tried to sync which interfered with gps functions? I used it yesterday with auto sync off and it worked well. I will investigate if auto sync on causes the GPS issue again.
Thanks again.
Hi guys, is it normal, that my Stratos's Gps show me the speed to much delayed. I checked it with my car, and the gps gets to the same speed as my phone's one, but maybe 10 seconds later. By skiing it can mean worse maximum speed measurement. It is like that with all the Amazefit Startos watches or I have a wrong one? Thanks for the answers!
It's not the same sampling frequency for a car as it is for a walking man. Watch gps do not need to detect non-human speeds, so there is a lower sampling. (Slower).
Same issue again FW version 4.2.8.0:
stops recording gps data altogether after a few minutes.
I've reset and unpaired the clock twice but the issue remains.
Any advice?
Hi, so I had my Samsung Gear Fit 2 for a while and it was working fine used it with a few different phones. Right now, I'm using it with Xiaomi Mi8. Before, there wasn't any problems, but now, it started acting up. Whenever I start a run or a cycle session, it doesn't track how much I run/cycle or how fast. I tried factory resetting it, but that didn't help. Gear Plugin on my phone has location permissions. The watch is out of warranty, so that's not an option.