Related
I couldn't get watchon app working so I tried installing a similar app from the play store called gravity. It basically turns your watch on and off based on the positioning and motion of the watch. I can get it to work, the problem I'm having is that no matter what settings I try, I can't get it quite perfect. A lot of times the watch ends up turning on when I don't want it to, and turns off when I don't want it to. I've tried playing around with all the settings but can't seem to get it just right. I was wondering if anybody else has any experience with this app and what the optimal settings were?
flimmyflam said:
I couldn't get watchon app working so I tried installing a similar app from the play store called gravity. It basically turns your watch on and off based on the positioning and motion of the watch. I can get it to work, the problem I'm having is that no matter what settings I try, I can't get it quite perfect. A lot of times the watch ends up turning on when I don't want it to, and turns off when I don't want it to. I've tried playing around with all the settings but can't seem to get it just right. I was wondering if anybody else has any experience with this app and what the optimal settings were?
Click to expand...
Click to collapse
I haven't tried that particular app, but found Shake in the Play Store, which can be configured to launch OClock when the TS is shaken. It isn't perfect either, as sometimes there is a couple seconds delay before launching the clock, and also the setting to Run as Service sometimes gets turned off. I got around the last part by using Tasker to run Shake at boot, which seems to then turn the Service on.
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.
I've only had my watch 16 hours or so (7 of which I was asleep), and I like it, and plan to develop apps for it..... but I have the following issues:
Updated (9 Jul)
Take a note voice command just sends me an email, instead of using something like Google Keep
The screen dims for a second before screen turns off (or goes to clock) - if I do OK Google during this time it ignores it
Set a Timer voice command does not work - options set an alarm menu
No music controls when I use default music player, or RocketPlayer Solved my Wear Music Controller
When doing a voice search, it often says Disconnected. 6 times so far, one time I had to restart watch before it could reconnect.
Dictating a longish email will eventually fail, even though it recognized loads of the words.
Step count often not updated on homescreen widget, despite it showing a higher number in the actual watch app
Dismissing a google now card (weather for example), you can't get it back if you did it by mistake
Navigation started from watch sits on Calulating route... if music playing on phone with screen locked.
Screen stays on while charging (reported by dunjamon) Solved by Slumber
I have it paired with HTC One S with Liberty S4 MAX custom ROM.
Anyone else have these issues (what device do you have it paired with)? Or know how to fix/work around them?
I have 4 and 7 8 D:
Number 1 confused me for a while. I searched everything on my phone before I realised that it had just emailed me. With number 7, I've turned off the step count...yet it still tells me my total of 0.
Also, is with the screen always on settings set to no, when you put it on charge the screen stays on. It's a nightmare at night, I have to turn it off and then boot it back up in the morning. There needs to be some kind of sleep mode or setting to allow the screen to be off while charging.
I've had 3 and 5
5 is a bit annoying. I'm hoping a restart means it won't recur as I go thru the day...
dunjamon said:
Number 1 confused me for a while. I searched everything on my phone before I realised that it had just emailed me. With number 7, I've turned off the step count...yet it still tells me my total of 0.
Also, is with the screen always on settings set to no, when you put it on charge the screen stays on. It's a nightmare at night, I have to turn it off and then boot it back up in the morning. There needs to be some kind of sleep mode or setting to allow the screen to be off while charging.
Click to expand...
Click to collapse
There is. Enable developer settings and set if the screen show stay on or not during charging
biggiephat said:
There is. Enable developer settings and set if the screen show stay on or not during charging
Click to expand...
Click to collapse
I didn't know about these developer options: Tapping build version several times works, same as a phone. The "Stay awake when charging" option is disabled by default however. I've only recently enabled the "always keep screen on" mode, so will be interesting to see what happens when charging tonight...
Regarding 1) It has started working! I installed Evernote for Android Wear from play store, also Baby Time and Draw Watch. I also resycn'ed all apps using the option in the Android Wear companion app.
Next time I did "take a note", it asked if I wanted to complete Action using Keep or Evernote, so I chose Keep. I also can see Keep in the list of apps on watch (before it wasn't there). The note was stored in Keep. Still works after uninstalling Evernote.
Regarding 4) I installed Music (Remix) Trial from play store, and Pause, Prev, Next actions are now on my watch. Unfortunately, the buttons do nothing. Not sure if this is an issue with my particular phone or what... Anyone else tried this app?
biggiephat said:
There is. Enable developer settings and set if the screen show stay on or not during charging
Click to expand...
Click to collapse
I've already disabled the stay awake while charging option. Unless it needs to be activated and then the watch itself to be set to not be always on. Will have another play tonight.
I've also noticed Keep show up in the apps now after another update. Will test out another note and see where it goes.
Got none of these problems with my watch. Fix for 8: If eg you swiped away the weather just say "ok google, what's the weather". after it told you the card should be back. this works for me, also with others like world clock, steps etc.
Just tried the screen off while charging and it doesn't work. The only way I can get the screen to turn off is to put it on charge and then on my phone set the screen to go off.
I actually have none of these issues...
barkside said:
Regarding 1) It has started working! I installed Evernote for Android Wear from play store, also Baby Time and Draw Watch. I also resycn'ed all apps using the option in the Android Wear companion app.
Next time I did "take a note", it asked if I wanted to complete Action using Keep or Evernote, so I chose Keep. I also can see Keep in the list of apps on watch (before it wasn't there). The note was stored in Keep. Still works after uninstalling Evernote.
Regarding 4) I installed Music (Remix) Trial from play store, and Pause, Prev, Next actions are now on my watch. Unfortunately, the buttons do nothing. Not sure if this is an issue with my particular phone or what... Anyone else tried this app?
Click to expand...
Click to collapse
i have the same problem with my music controls (nexus5 android L preview)
drsouly said:
i have the same problem with my music controls (nexus5 android L preview)
Click to expand...
Click to collapse
Music controls working fine, paired with Nexus 5 Android 4.4.4 Stock.
alistairs1 said:
Music controls working fine, paired with Nexus 5 Android 4.4.4 Stock.
Click to expand...
Click to collapse
I hope it isn't the case where everything will only work flawlessly with the latest Nexus devices. Have Google tested Wear with anything older?
I suppose it would make good business sense to encourage peeps to fork out for a Nexus 5 after spending money on a Wear watch...
Another issue I'm seeing is starting a Navigation from the watch won't work if I have music playing on my phone (phone lockscreen has music player UI). It just sits there on Calculating route... I'll add this to my list (and others from other peeps)
barkside said:
I've only had my watch 16 hours or so (7 of which I was asleep), and I like it, and plan to develop apps for it..... but I have the following issues:
Updated (9 Jul)
Take a note voice command just sends me an email, instead of using something like Google Keep
The screen dims for a second before screen turns off (or goes to clock) - if I do OK Google during this time it ignores it
Set a Timer voice command does not work - options set an alarm menu
No music controls when I use default music player, or RocketPlayer
When doing a voice search, it often says Disconnected. 6 times so far, one time I had to restart watch before it could reconnect.
Dictating a longish email will eventually fail, even though it recognized loads of the words.
Step count often not updated on homescreen widget, despite it showing a higher number in the actual watch app
Dismissing a google now card (weather for example), you can't get it back if you did it by mistake
Navigation started from watch sits on Calulating route... if music playing on phone with screen locked.
Screen stays on while charging (reported by dunjamon)
I have it paired with HTC One S with Liberty S4 v9 custom ROM.
Anyone else have these issues (what device do you have it paired with)? Or know how to fix/work around them?
Click to expand...
Click to collapse
Number 4, music control, works well with Pandora. I like that I can start Pandora by voice, but there's no way to shut it down the same way.
Number 8, the disappearing cards was giving me hell on stocks. To resolve, I opened a browser on my workstation, Googled "quote xom" or whatever stock, and then the stocks card reappeared. I suspect a simple "Ok, Google...quote XOM" might do the same thing.
None of these issues. Nexus 5 Stock 4.4.4. You are also using a custom ROM so.....
Sent from my Nexus 5 using XDA Free mobile app
No 3. Timer kicks straight into Alarm picker. Timer does work when you get to Google screen, swipe up and manually select it. But that's not a solution. I'm on stock 4.3.
Having the control issue with google play music and youtube when connected to chromecast he buttons wouldn't work and with youtube wven tho there was nothing playing the buttons were still on the watch and couldn't be dismissed
also having the connection issues if i take the watch out of the reach of the phone the app won't reconnect unless i go into the app myself to do it even then the watch says it's not connected when using ok google
EDIT: Happened again this time can't get the Ok Google working at all
Anybody else having issues where raising your arm to activate "Ok Google"isn't working consistently? We've got 2 watches in the house, and I've worn both. Same issue. Seems like if you don't use it for awhile, the arm motion won't wake the watch back up.
Sent from my HTC One_M8 using Tapatalk
I'm having some of the same issues. I've had a few smart watches to compare.
-My Gear 2 worked way better as far as waking up when raising my arm. The LG G is difficult to wake by raising my arm.
-Bluetooth doesn't connect automatically when I get back in range of my phone. The other smart watches have done this that I have owned so not sure why this issue exists.
-There's no way to set the screen timeout. This thing times out very quick. Personally, I have no problem charging my batt every night so I would like to take advantage of the 30 or so % that is left on the watch each night by increasing the screen time out, vibration duration etc.
-I have a difficult time getting cards back after deleting even if I search for the stock, weather, etc. again.
-No way to reply to text messages.
I'll add more as they hit me.
Has anybody got Cloud Sync to work?
I want notifications to go to my watch without a bluetooth connection.
I can connect the watch to wifi but I can't get any updates from my watch.
I have the same problem. I am using a Note 4.
I already did a reset without a result .
The asus support could not help me.
It seems that not many owners tries to use this feature. Would be interesting if any zwatch 2 works with wifi.
I know mine does not respond to 'OK Google' when I am out of BT range, even if it says it is connected to WiFi. I do seem to be able to get notifications though, and I have always been able to execute Tasker Tasks from Wear Tasker.
But Android Wear docs say "OK Google" should work. I have seen similar reports from others using different watches so I am guessin this is just some typical broken Google goodness we'll have to wait for them to straighten out.
I used to have tons of sync issues with my Zenwatch (both first, second gen), and this trick solved all my issues - have no idea how and why, but it worked:
Just let my Zenwatch battery go empty, did not charge it for 4-5 days, than recharging. It connected my phone (mate 7) again normally, and all syncs (in my case weather, notifications, step counts) worked fine again - permanently. NO idea how it works (emptying cache watch?), but it worked for me.
All other suggestions of forums (re-installing, reconnecting): not..
Jus my 2c
After a bit of research and some common sense troubleshooting, I have my watch working as expected on my local Wi-Fi network.
I read something somewhere that Wear has had some issues on higher Wi-Fi channels. I also downloaded WiFi Analyzer to check used channels in my area. All APs were in the neighborhood of ch 6-11.
I forced my router to ch 1 and bingo. Phone is now upstairs at the other end of the house and everything is working great, including 'OK Google' (knock on wood).
My ZW 2 has a working wifi connection (2.4Ghz Port1). I know that because google maps on the watch is working even when the phone is switched off.
My problem ist, that no notification appears on the phone and no "ok google" command works, when phone and watch are only connected via wifi and bluetooth is switched off.
The asus support told me, that i am the only person with this problem who contacted them.
Seems to be a problem with my galaxy note 4.
I will give it a try with a xperia z3 compact the next days.
I can´t believe this is a hardware problem.
roboterente
Hello all, I updated my iPhone to iOS 16 beta and my notifications are not working at all. I know there was a fix coming as an update for the Zepp app which I did (7.1.5) but I am still not able to get anything from my phone into my watch. Notifications, calls, nothing at all. I tried submitting a ticket to support but got no response.
Any help is appreciated, thanks.
Exactly the same problem here. iOS 16 (not beta) and Zepp 7.1.5 (was on Zepp 7.0.3 and it was the same). I have an old Bip in my desk drawer that I tried to activate instead of my Bip S Lite and it actually did receive notifications, until it very soon didn't anymore.
It also seems the watch disconnects itself from Bluetooth from time to time and won't reconnect until I open the Zepp app and do a sync.
I have a watch face that indicates if BT is connected or not, so that's how I know when it's disconnected.
So same problem on both Bip and Bip S Lite. And it seems those aren't the only models affected. There are reports coming from here and there.
Don MC said:
Exactly the same problem here. iOS 16 and Zepp 7.1.5 (was on Zepp 7.0.3 and it was the same). I have an old Bip in my desk drawer that I tried to activate instead of my Bip S Lite and it actually did receive notifications, until it very soon didn't anymore.
It also seems the watch disconnects itself from Bluetooth from time to time and won't reconnect until I open the Zepp app and do a sync.
So same problem on both Bip and Bip S Lite. And it seems those aren't the only models affected. There are reports coming from here and there.
Click to expand...
Click to collapse
Same thing is happening with the Bluetooth too. It gets disconnected and it does not reconnect at all.
Yeah I have seen reports from other watch users and some of them have already been able to fix it but I have tried everything so far with no success.
I have also tried factory resetting the watch(es), forgetting the Bluetooth bindings and uninstalling/reinstalling the Zepp app many times, but to no avail.
EDIT: Have now submiitted 3 reports via the Feedback function in the app. Each one more detailed than the previous.
The latest one:
Watch not receiving notifications and constantly disconnecting from BT.
iOS16, Zepp 7.0.3 and 7.1.5
-Problems started with iOS 16, I think.
-Notifications for Phone calls, WhatsApp, Gmail and SMS. None of them work.
-Watch keeps disconnecting from BT and will not reconnect until I open the Zepp app and do a sync.
-Will not reconnect BT automatically after being out of range.
-I have tried every setting in the App itself and in the phone's settings.
-I tried my old Bip watch and it did show a notification, but only once. Then it too stopped receiving them.
-I have factory resetted both watches many times and uninstalled/reinstalled the Zepp app a couple of times.
-Have made the phone forget the Bluetooth binding many times.
Don MC said:
I have also tried factory resetting the watch(es), forgetting the Bluetooth bindings and uninstalling/reinstalling the Zepp app many times, but to no avail.
EDIT: Have now submiitted 3 reports via the Feedback function in the app. Each one more detailed than the previous.
The latest one:
Watch not receiving notifications and constantly disconnecting from BT.
iOS16, Zepp 7.0.3 and 7.1.5
-Problems started with iOS 16, I think.
-Notifications for Phone calls, WhatsApp, Gmail and SMS. None of them work.
-Watch keeps disconnecting from BT and will not reconnect until I open the Zepp app and do a sync.
-Will not reconnect BT automatically after being out of range.
-I have tried every setting in the App itself and in the phone's settings.
-I tried my old Bip watch and it did show a notification, but only once. Then it too stopped receiving them.
-I have factory resetted both watches many times and uninstalled/reinstalled the Zepp app a couple of times.
-Have made the phone forget the Bluetooth binding many times.
Click to expand...
Click to collapse
I have also done all that and nothing has worked.
Mine started on iOS 16 beta before 16.1 like the update before it and it broke. First time I updated to the beta it was working fine but then the one right before 16.1 that’s where everything started.
Got an update to the Zepp app on my iPhone yesterday (v. 7.1.6) but it doesn't seem to have made any difference. Still no notifications.
I'm beginning to think the problems have something to do with how iOS16 handles Bluetooth connections. The bug is either in iOS16 or in the watch Firmware (although other Amazfit models are affected too).
I base my asumptions on the fact that the watch has trouble reconnecting to BT after being out of range or after it's been restarted. If I restart the phone, however, the watch usually gets connected.
So if it is the phone that initiates the connection, it usually works. But if the watch itself tries to connect, then it doesn't work.
But then again, the notifications do not work even if I keep the Bluetooth window open on my phone and the watch is 100% connected when a message arrives. Strange.
There is also something weird when I make the iPhone forget the BT pairing to the watch. It usually immediately rediscovers the watch and tries to pair again. This happens even if the watch is set to NOT be discoverable.
Just got another Zepp update in the App Store. 7.1.7.
Still no cigar.
There will be no more Huami watches in this household.
Don MC said:
I'm beginning to think the problems have something to do with how iOS16 handles Bluetooth connections. The bug is either in iOS16 or in the watch Firmware (although other Amazfit models are affected too).
I base my asumptions on the fact that the watch has trouble reconnecting to BT after being out of range or after it's been restarted. If I restart the phone, however, the watch usually gets connected.
So if it is the phone that initiates the connection, it usually works. But if the watch itself tries to connect, then it doesn't work.
But then again, the notifications do not work even if I keep the Bluetooth window open on my phone and the watch is 100% connected when a message arrives. Strange.
There is also something weird when I make the iPhone forget the BT pairing to the watch. It usually immediately rediscovers the watch and tries to pair again. This happens even if the watch is set to NOT be discoverable.
Click to expand...
Click to collapse
My apologies for my absence, I am not getting any notifications and honestly lost hope on this. I understand that this is something that might take time but 3 updates later, no real resolution or acknowledgment of what is actually happening.
I also believe that this issue has to do with the connection that the app has with the iOS16 beta since it started after an update. I got beta going, and everything was going smoothly, received an update and everything went south after that with no success or real connection whatsoever.
I just updated the app to 7.1.7 as you did and still the same, the only difference is that it seems the connection is more stable as it has not been disconnected yet and still shows connected without any issues.
I have not encountered the situation you are experiencing in that even if you unpair the watch the phone forces the connection again.
Indeed, I think this will be my last Huami watch. My wife is dying to update to iOS16 but I have warned her multiple times not to since it will break the connection.
Right now I just feel I have a regular watch that I have to charge in order to see the time...
It’s not the iOS beta. I was on the official 16.0 to 16.0.2 and the problem was there. Jumped on the 16.1 beta to try to solve it, but no luck there either.
Threw my Amazfit in my desk drawer and bought myself a Withings Scanwatch.
I finally am able to receive my iMessages on my Amazfit GTR4. On the Notifications in iPhone, go to Messages, and make sure in the Lock Screen Appearance-->Show Previews-> When Unlocked. Mine had changed to Never, as soon as I changed that and synced the Zepp app, now my messages are going through to my watch! Just thought I'd share what worked for me.
Seems that the Zepp app version 7.2.1 has fixed the notifications on my watch. They took their time, I might say.
...aaand then I updated my phone to iOS 16.1.1 and the watch (Bip S Lite) stopped notifying again.
EDIT: My Amazfit Bip on the other hand seems to be notifying just fine. Think I'll be using that one for now.
It definitely seems like the Bluetooth on my Bip S Lite is broken somehow. It won't automatically reconnect after it's been out of range/disconnected. I have to manually open the app to connect it again. And still no notifications.
I've contacted both the seller of the watch and Amazfit. Let's see if they have anything to say about it. I'm using the old Bip for now.
Dusted off my old Bip S Lite and paired it to my phone (or rather reactivated it, since I never did unpair it). To my surprise, it updated its firmware (to 2.1.1.86). Will try it and see if the notification issue is gone.