Hello,
in Germany, last night clocks were adjusted at 3:00am to 2:00am due to dayliht saving. My Android phone switched the time instantly, my Amazfit BIP ignored it, even at 11 am, the time was still faulty, syncing with the Mi Fit app didn't help. The only thing that helped was to unbind and rebind the BIP to the phone
This is really a pitty, I wonder how often at all the BIP does syncronize at all, and why the people developing this piece of software are so ignorant not to implement the most obvious use-cases.
Any tips and hints how the time sync behaviour can be improved? Thanks!
Turn off and then on the Bluetooth. That's all. Works every time. I travel a lot and that's what I do to sync the time when I change timezones.
Sent from my Huawei P9 using Tapatalk Pro
A lot Xiaomi/Amazfit Products (Miband, Bip, Cor etc) has to connect one time to mifit after time change to get the right time again! I use mifit since a few years now and i‘ve never a problem with the time change!
I tried reconnecting bluetooth as well as syncing in the MiFit App, both did not help. Only unpairing and repairing solved the issue Even if these two did work, it is a shame that things like that do not work automatically out of the box...
Hello, i have same issue. Just turn off and on your bip and it solve the problem.
Restart the phone
I had same issue today and restarting the phone connected to my BIP solved the issue instantly. Hope it helps!!
4 years later and my brand new Amazfit Band 7 ignores daylight saving even after a full shutdown. Disappointing indeed because (almost) all my devices, clocks, watches use either DCF or NTP to avoid this issue in the first place.
Hey guys,
I have a problem with sync function on a amazfit Verge, I can sync without any problems but 10 minutes later the watch disconects from the phone, I tried uninstalling the app, restarting the phone, watch and keeps happening.
Im using a mate 20 btw, never had any problems with a GTR and previously I used the verge with an iphone 7 without issues
thx for any info and your time
Hello. The last 5 days, the name of the income call doesn't appear in my t-rex screen. I made factory reset of the watch and it got fixed . The day after, the problem returned. So I realized that every time I synchronize the watchface it get fixed for one day and the day after the problem returns.
SACS73 said:
Hello. The last 5 days, the name of the income call doesn't appear in my t-rex screen. I made factory reset of the watch and it got fixed . The day after, the problem returned. So I realized that every time I synchronize the watchface it get fixed for one day and the day after the problem returns.
Click to expand...
Click to collapse
Prevent Zeep from being killed on your device and keep BT connection, everything should work
In the spring this year there were no problems at all. But now it's very unreliable.
Yesterday I pulled down the Zepp view a dozen times and finally it synced my last workout... but without GPS data! I know there was GPS data because I can see it on the watch itself.
Today I could not sync my last workout at all. Previously the Activities menu on the watch said there are a few items unsynced, but now it does not have this message. It's as if it was synced but I don't have data in Zepp.
When I pull down the Zepp view, sometimes it shows no errors, sometimes says "Device sync failed". But it shows battery level correctly and also it is able to ping the watch through Find watch function (the watch vibrates). Occasionally Zepp does the AGPS update of the watch, and the update also sometimes takes multiple tries to complete.
What I have tried these days:
restarting Zepp
restarting Bluetooth and location of the phone
restarting Amazfit
restarting the phone
force-closing Zepp
cleaning Zepp cache
unpairing and repairing Amazfit (had to repeat pairing twice - it failed during the last step when preparing the device)
Watch
Amazfit GTS
Firmware version v0.1.2.05
Phone
Nokia 8.1 Android 11
Zepp
7.0.2-play
Now after having written this, I restarted Zepp once more, and suddenly it synced automatically, loaded the stuck workout with all the GPS data and also did AGPS update. But when I do pull down, it again says "Device sync failed".
Why it's so unstable now? Is the watch dying? Is Zepp glitching? Is it some Android update at fault?
I'm having the same issue. Did you ever find a solution?
Exactly the same issue. Same steps were tried also. Have reported this issue through app. No response. Atleast, it is not me alone. Thanks for sharing this issue.
Hi everyone. I found a solution.
Removed all the cache data and also app data in Android app settings for Zepp.
Then uninstalled Zepp completely.
Then reinstalled Zepp from Google Play.
Then reset Amazfit to factory settings.
Then paired Amazfit to Zepp.
Now it seems to be working again without a hitch for two months.
I suspect, the local database was somehow out-of-sync beyond repair and that's what was messing Zepp and it failed when saving data. So, most likely cleaning all the app data was the main thing, and maybe it would work just fine without reinstalling. At first, I was reluctant to clean the app data because I was afraid I would lose all of my workout history, but fortunately, the app was able to reload it from the server. Of course, I lost all the workout data that was on Amazfit itself.
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.