Hello everybody!
I recently bought an Amazfit Stratos 3 to replace my amazing Stratos 2, since it's battery died after 2 years. And although my almost immediate regret (the 2 was pretty much indestructible, the 3 already has marks with just one week), there is a annoying connection issue: every so often it simply disconnects from my Poco F1! My phone is also not on stock ROM but it was only when it arrived, so I'm excluding that as an possible cause. I've had that issue on the latest stock ROM and also on the Paceficator ROM from Saratoga. It gets me mad since what is the use on a smartwatch that, randomly, disconnects from my phone? Any other Stratos 3 users with this issue? Or is just mine and should I get it to warranty? Just for reference, with the Stratos 2 it was almost shocking how far I could get from the phone without losing connection, let alone being near to it and with the Stratos 3 I find myself with my phone on my pocket and with the smartwatch disconnected!
Thank you all for your help!
Try to configure zepp to not going to sleep
winni21 said:
Try to configure zepp to not going to sleep
Click to expand...
Click to collapse
I'm sorry, I'm not getting what you want to say.
Hello,
I notice almost the same. There is of course the option on the watch to get notified when it disconnects from the phone but I also see that "find phone feature" is not working good anymore. Sometimes, I'm in line on sight at 2-3m from the phone, and the "find phone" option is not successfull. Watch is saying "Not connected to App, unable to find phone". So definietly, the watch is loosing the connection with the phone/Zepp app.
To answer Winni21, Zepp is in "no restriction" in battery saving. Is this what you mean by "configure Zepp not to go to sleep"? It is true that if Zeep goes to sleep, "find phone" and bluetooth migh disconnect quickly. Please, clarify what you mean "not going to sleep" if possible
Tzar92 said:
Hello,
I notice almost the same. There is of course the option on the watch to get notified when it disconnects from the phone but I also see that "find phone feature" is not working good anymore. Sometimes, I'm in line on sight at 2-3m from the phone, and the "find phone" option is not successfull. Watch is saying "Not connected to App, unable to find phone". So definietly, the watch is loosing the connection with the phone/Zepp app.
To answer Winni21, Zepp is in "no restriction" in battery saving. Is this what you mean by "configure Zepp not to go to sleep"? It is true that if Zeep goes to sleep, "find phone" and bluetooth migh disconnect quickly. Please, clarify what you mean "not going to sleep" if possible
Click to expand...
Click to collapse
Hi! I've used both options on Zepp's battery options, with no sucess. But I do notice that if I turn on location with the GPS the connection is almost instant! But I'm not willing to have location on all the time...
I have started getting the same connection issues. I didn't have this problem before or at least I didn't notice. Enabling the anti-lost phone feature reveals the watch is constantly loosing connection.
In my case I noticed the problem via the notifications (started to come with a delay and very often repeated) Seems like when the watch looses connection (or when it reconnects) old notifications are displayed.
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.
Just bought the second gen moto 360. Whenever i turn off bluetooth from my phone it doesnt immediately show on my watch that phome has been disconnected. I have also installed the find your phone app which tells you that phone is out of range when it loses bluetooth connectivity. The notification or vibration for disconnect usually come to the watch after a minute or two. Is there any problem with the watch?
nklrwt said:
Just bought the second gen moto 360. Whenever i turn off bluetooth from my phone it doesnt immediately show on my watch that phome has been disconnected. I have also installed the find your phone app which tells you that phone is out of range when it loses bluetooth connectivity. The notification or vibration for disconnect usually come to the watch after a minute or two. Is there any problem with the watch?
Click to expand...
Click to collapse
Nah, no problem with the watch, it dose the same on mine.
There is due to this some kind of "power saving" feature either on the watch itself or in Android Wear app, that's why it doesn't show the disconnected sign on the watch immediatly nor the vibration alert sent by whatever apps similar to "Find your phone" app (I've tested quite a few)
What I found is that, if you turn on your watch's screen from either ambiant mode or non-ambiant mode (black screen) to normal mode, the disconnected sign would show up as well as the disconnected vibration alert within seconds, otherwise, it could take minutes...
It is kinda annoying if we wanna use those apps to alert us whenever we've left our phone behind or it's being stolen since it does not make any vibrations UNLESS we manually wake the watch face up
This kind of alert should really have been built into the Android Wear app's settings in the first place along with the vibration strength/duration settings (few 3rd party apps can do that pretty well), because a lot of us often find the watch's vibration is weak (well, actually, not that weak but too short), we know the purpose is to preserve the battery's life, but I bet a lot of us would prefer to not miss notifications rather than having a few extra hours of battery life...
Hi, i have a new Amazfit 2 Stratos with official international firmware US FW (2.3.2.7) and noticed cases where the battery would rapidly drain within hours, for example I would go to sleep with 60% battery and 6-7 hours later it would be on 5%...
I then noticed that if i reset the device, the rapid battery drain would stop, for example i noticed a rapid drain of 10 % an hour, so i reset the device and it stopped draining the battery...
Which made me think there is a stuck process or some firmware issue that keeps draining the battery, and I now reset my device every morning which makes it lasts days.
Anyone else noticing battery drain issues?
Having the same issue. What watch face are you using? I'm trying to narrow down the issue.
I've noticed the same after converting from Chinese to US. I'm thinking it might be caused by WiFi (or something using it) as it didn't start happening until I added my network.
...
try to install Task Manager and you can kill some processes which are maybe draining your battery. I use it as i have plenty of apps there.
I found the cause - the data sync. Each time you access the app on your phone, it syncs the data.
When you disable the wifi/data connection on your cell and access the app (while watch is paired), it tries to sync and fails. Problem is that it seems to be stuck in a loop until data connection is available and by then the battery depletes rapidly.
Solution - don't access the app while there is no connection in your phone to wifi/data.
Not sure if this is the only case when the watch syncs data - it might be syncing it automatically each day at a specific time - will post more info if i find out.
I also don't know if this bug is caused by the new firmware or not because i received the watch only last week and immediately updated to the new version based on the notification in the app.
It seems there is also a difference in battery use when using different watch faces. For example, I've observed that a watch face with no temperature will consume less battery than with a watch face with a temperature reading.
Anyone with similar experience?
I've bought an Amazfit Pace that sufered from same issue, te battery starts to drain all the way down in a couple of hours, so i returned it and decided to buy the Stratos, and guess what?
I have exact the same issue.
Tryed some things and i think the cause is related with smartphone bluetooth, in my case OnePlus 5T bluetooth.
If i desconnect smartphone bluethoot it stops draining, if i put it on again it starts draining again, if restart smartphone it stays good until it happen again next day or so.
Problem with battery discharge Amazfit 2
Hi, I also have a battery discharge problem. The watch battery will start to discharge quickly when I turn on the amazfit application on my phone. When the phone is restarted and I do not go to the Amazfit application, the watch connects everything works and the flashlight is ok, I turn on the application amazfit and the torch goes down. Tonight I put the plane on the phone and plugged in only the bluetooth and my watch was discharged in the morning. The red bar at the bottom of the amazfit app only appears when I'm not connected to the internet, I'm connected all the time. I have amazfit 2 China, recorded by Rom 2.0.14.0, Amazfit Watch 3.0.0 and HUAWEI Mate 10 lite
So it has exactly the same bug as the first one... (and I have it on my wrist). Well time to go back to regular (but expensive for nothing) watches
You may want to check this post/thread:
https://forum.xda-developers.com/sm...ain-issues-t3636166/post76189539#post76189539
Basically what usually cause these problems are wither data sync issues or a problem with Bluetooth/WiFi.
paulomodesto said:
I've bought an Amazfit Pace that sufered from same issue, te battery starts to drain all the way down in a couple of hours, so i returned it and decided to buy the Stratos, and guess what?
I have exact the same issue.
Tryed some things and i think the cause is related with smartphone bluetooth, in my case OnePlus 5T bluetooth.
If i desconnect smartphone bluethoot it stops draining, if i put it on again it starts draining again, if restart smartphone it stays good until it happen again next day or so.
Click to expand...
Click to collapse
I noticed the same issue with my pace on my OP5 after à phone update. Tried to reset, pair un pair still the same.
Issue was removed after oxygenos 5.1.0 but immediately back after last oxos 5.1.1
To move on I paires the watch to my xiaomi mi5 on global stable rom Android 7, all is fine.
Seems many phones are bt broken with oreo.
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
I think too, that this is some sync related issue. If I check the watch data in the Amazfit app, then the watch starts to drain with 2-3% per hour. However if I exit the app and turn off Bluetooth on the phone till the notification icon and the watch show disconnected and then turn back BT to get the watch connected again, the battery consumption goes back to normal.
Opening the app again starts the battery drain issue again.
I wrote it already in another thread here, I own an Amazfit Pace, of course with battery drain issues. So I tested a bit. When the phoneapp is syncing it shows an information field at the bottom, this field becomes green when finished. But a few seconds later another datasync is made, not shown in the app but indicated by network speedmeter in androids statusbar. I think weather is syncing there but if you aren't aware of this and close the phoneapp before this second sync is finished, the watch runs into battery drain.
Since I wait 10 seconds after the app shows the green sync complete field I never had drain issues again.
amazfit watch app
I have the opposite problem. My phone battery drains like crazy. I have the Stratos for 2 days /int. version/. It works great, battery life is excellent. I suspect the Amazfit Watch App /Android/ is the culprit. I have to charge my phone 2-3 times daily??!
I think my Stratos worked fine until I activated the 'continuous HR' feature (and switched it off again). Before that, it would easily last for 5 days on a full charge. But I also get these fast drains now.
I restarted the watch a couple of times, let's see if this did it.
I've had the same issue a while ago (also after testing the continuous HR feature), and there I really had to reset the watch and reboot 3 times to get it back to normal again.
nickyzweb said:
I have the opposite problem. My phone battery drains like crazy. I have the Stratos for 2 days /int. version/. It works great, battery life is excellent. I suspect the Amazfit Watch App /Android/ is the culprit. I have to charge my phone 2-3 times daily??!
Click to expand...
Click to collapse
Something is breaking the Bluetooth connection between phone and watch, the most common cases are WiFi interferences (test with phone in Airplane mode and only BT on and see if battery usage is OK on phone) or corrupted data when syncing to the cloud (open Amazfit app and check if syncing is OK - you should see a green bar at the bottom -, you may need to unpair - it will delete all data on watch - then pair again and answer NO when it asks to restore old data).
Indeed seems bt is corrupted. When draining occurs, even if I switch off the bt from the phone, the icon on the watch says it is still connected. Again for me this does not occur on nougat, only when pairing with oreo device.
lfom said:
Something is breaking the Bluetooth connection between phone and watch, the most common cases are WiFi interferences (test with phone in Airplane mode and only BT on and see if battery usage is OK on phone) or corrupted data when syncing to the cloud (open Amazfit app and check if syncing is OK - you should see a green bar at the bottom -, you may need to unpair - it will delete all data on watch - then pair again and answer NO when it asks to restore old data).
Click to expand...
Click to collapse
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
I also have battery drain problem. Every setting is swithed off, no connection to the phone but in activity mode (cycling) I get 1h 30m of battery life.
Mihakol said:
I also have battery drain problem. Every setting is swithed off, no connection to the phone but in activity mode (cycling) I get 1h 30m of battery life.
Click to expand...
Click to collapse
Did you find a solution or did you send back the watch ?
so until how do not know what is the culprit?
mine one can last one day......
Hi. the tittle says it all.. i just bought this watch and i find it a pretty good watch, everything works fine but i cannot activate phone calls. When i try to switch it on, the phone ask for pairing with bluetooth ( when its already paired and conected) Its this normal ? If not, there is some workaround or fix ?
iPhone Xs
iOS 14.3
Thanks you for your help
Jotze0 said:
Hi. the tittle says it all.. i just bought this watch and i find it a pretty good watch, everything works fine but i cannot activate phone calls. When i try to switch it on, the phone ask for pairing with bluetooth ( when its already paired and conected) Its this normal ? If not, there is some workaround or fix ?
iPhone Xs
iOS 14.3
Thanks you for your help
Click to expand...
Click to collapse
I have exactly the same problem, with my Sony Xperia 10 III (Android 11) phone.
I had an Amazfit Bip, which is a great watch. I was undecided between a GTS 2 mini and this watch. I paid €80 more specifically to get the phone function, and I can't turn it on.
Amszfit seems to have zero support, other than an FAQ.
Jotze0 said:
Hi. the tittle says it all.. i just bought this watch and i find it a pretty good watch, everything works fine but i cannot activate phone calls. When i try to switch it on, the phone ask for pairing with bluetooth ( when its already paired and conected) Its this normal ? If not, there is some workaround or fix ?
iPhone Xs
iOS 14.3
Thanks you for your help
Click to expand...
Click to collapse
I have managed to solve this problem, but I don't really understand how it worked.
My GTS 2 was connected to my phone (Android 11) and I assumed there was a Bluetooth connection. However this phone function couldn't be activated because Zepp said there was no associated device.
I turned off Bluetooth and attempted to reactivate it manually. On my phone, the watch wasn't visible. I rebooted both the watch and the phone, but no luck. However, I realized that the phone was finding my old Amszfit Bio, which I had disassociated. I turned off the Amazfit Bip and tried again. I ended up having to reboot phone and watch once more, but now I am able to activate the phone function.
I can also respond to phone calls and it works well.
I hope this is helpful. You can try the above, and if it doesn't work, light a candle. I must say that Zepp is really inadequate for this watch. It was barely acceptable for the Bip, but falls far short for the complexity of the GTS 2.
What I really don't understand is that there was a Bluetooth connection, activated by QR code when I set up the phone, that allowed the watch to synchronise data with the phone, and which managed to send notifications, but was not functional for activating phone calls, unless a connection was made manually using the phone's Bluetooth settings.
Second method work for me. you need to tap pair on watch too at same time during pairing.
Start the Zepp app and go to "Profile > Amazfit GTS 2 > App settings". On the Phone page, turn on "Call on watch", then pair the watch and your phone through Bluetooth as instructed. Or you can try second mothed.
1. On your phone, go to Settings, then select "Bluetooth" to turn on the Bluetooth, and set the phone to be discoverable. On the watch, go to App list > Settings > Network and connections > Bluetooth. Ensure the Bluetooth is turned on.
2. Find the watch in the search results for available devices on your phone, and tap to pair them. Or, find your phone in the Bluetooth search results on the watch, and tap to pair the devices.
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.