Amazfit Bip S Lite Notification Issues - Amazfit
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.
Related
Cloud Sync
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
[Bug?] Stratos can't connect to the iOS app, but receives messenger notifications.
I have tried to factory reset the watch many times, and everytime it will fix it, but after a few days, same issue persists. Sometimes it will receive app notifications, sometimes it can't even do that. **Right now it shows in my bluetooth settings that the watch is connected(probly why Im getting notifications) . But again, no connection in app**. Very frustrating as I won't be able to view any of my stats on the app at all. Anyone else experiencing this?
Since no one replied... UPDATE: I gave up on the iOS app, seems like it's just a persisting problem right now. I managed to not lose any data by enabling the hidden app list, and paired my watch with my Samsung phone instead. So I didn't have to factory reset it. And the Android app so far is working much better. i.e. Custom watch faces actually shows up in the app.
Make sure you have latest firmware on watch and Amazfit app on phone. Pair them properly or you may have problems with your activity data in the future (see thread about sync FAQ). If you still have issues, re-install Amazfit and enable the "Away alert" in watch Settings, it seems to make connection much more stable for me...
Verge - can't accept calls on watch
Since I've tried everything i could to solve this issue, searched all forum/reddit/google for 14 hours, I'm asking for help here as a last resort. Symptoms: When i receive a phone call i tap on green to accept, the watch act as everything is fine (jumps to in call screen, starts to count...etc) but actually the phone doesn't accept it, just keeps ringing. If i accept the call afterwards on the phone itself, everything works fine watch acts as a BT headset automatically. Remarks: Disabling+Enabling "bluetooth phone function" on the watch solves the problem temporaly, probably until next notification/sync. -Amazfit Verge 3.2.2.0 3.2.3.0 -HTC U Ultra (tried with both stock Android 8.0 and LineageOS 9.0) -Amazfit Watch (2.7.0.1) app permissions are enabled (call logs, camera, contacts, location, storage, telephone) -Android Battery optimisation disabled for: Amazfit Watch, Amazmod, Bluetooth, Call management, Contacts, Phone, Phone services -Amazfit Watch/Amazmod notification: As battery opt. above, but i've even tried it with adding everything (including all system apps) -Enabled: Android settings/Google/Vocie/Allow Bluetooth request with device locked -Tried it with and without Amazmod -Watch factory reset, apps reinstall are done Update: I did more testing, and the answer call does work if I wait at least 4-5 seconds before tapping the accept button. It is probably an issue of both sides: the phone needs some time to accept the watch as a BT headphone, while the watch does not have any check/redundancy for accepting call during this phase.
DraX8 said: Since I've tried everything i could to solve this issue, searched all forum/reddit/google for 14 hours, I'm asking for help here as a last resort. Symptoms: When i receive a phone call i tap on green to accept, the watch act as everything is fine (jumps to in call screen, starts to count...etc) but actually the phone doesn't accept it, just keeps ringing. If i accept the call afterwards on the phone itself, everything works fine watch acts as a BT headset automatically. Remarks: Disabling+Enabling "bluetooth phone function" on the watch solves the problem temporaly, probably until next notification/sync. -Amazfit Verge 3.2.2.0 -HTC U Ultra (tried with both stock Android 8.0 and LineageOS 9.0) -Amazfit Watch (2.7.0.1) app permissions are enabled (call logs, camera, contacts, location, storage, telephone) -Android Battery optimisation disabled for: Amazfit Watch, Amazmod, Bluetooth, Call management, Contacts, Phone, Phone services -Amazfit Watch/Amazmod notification: As battery opt. above, but i've even tried it with adding everything (including all system apps) -Enabled: Android settings/Google/Vocie/Allow Bluetooth request with device locked -Tried it with and without Amazmod -Watch factory reset, apps reinstall are done Click to expand... Click to collapse Maybe problem that you using a lot of unofficial apps, software and ect.? By the way for me working fine, i'm with stock ROM, today got new update 3.2.3.0 where was fixed some bugs
xdauser2019 said: Maybe problem that you using a lot of unofficial apps, software and ect.? By the way for me working fine, i'm with stock ROM, today got new update 3.2.3.0 where was fixed some bugs Click to expand... Click to collapse Thank you for your reply/suggestion. I tried it with clean watch+phone, no changes at all. New update did not helped either. Meanwhile i got some testing time with it, and found out i have to wait before i accept a call. After 5-6 vibrations on the watch i can accept the call with success, i would guess this bug is due to the phone needs some time to set the device as bluetooth headphone. Probably the watch SW does not have any checks is it done already, also no redundancy for answering a call (sending the OK signal a few times for example, if that is possible).
make sure that in the bluetooth, you have the voice profile enabled for the watch connection
1immortal said: make sure that in the bluetooth, you have the voice profile enabled for the watch connection Click to expand... Click to collapse Thank you for the suggestion, it was enabled already. Meanwhile i could do some testing, updated the OP also as: I did more testing, and the answer call does work if I wait at least 4-5 seconds before tapping the accept button. It is probably an issue of both sides: the phone needs some time to accept the watch as a BT headphone, while the watch does not have any check/redundancy for accepting call during this phase. Click to expand... Click to collapse Do you think it is possible to solve this issue with Amazmod? Implementing some kind of redundancy or check for the phone watch app?
DraX8 said: Thank you for your reply/suggestion. I tried it with clean watch+phone, no changes at all. New update did not helped either. Meanwhile i got some testing time with it, and found out i have to wait before i accept a call. After 5-6 vibrations on the watch i can accept the call with success, i would guess this bug is due to the phone needs some time to set the device as bluetooth headphone. Probably the watch SW does not have any checks is it done already, also no redundancy for answering a call (sending the OK signal a few times for example, if that is possible). Click to expand... Click to collapse I recommend you to test without any amazmod and ect., problem can be with 3rd parties software, apps. If you still have problem when you using everything from manufactors: stock rom on smartphone/smartwatch and everything is updated, i recommend you to connect with Amazfit support https://en.amazfit.com/support.html or https://us.amazfit.com/contact (this is US support, but they taking advice for all costumers, keep patience checking, often is disconnected). I don't have this porblem, coz if say honest i don't talk right now over watch. But maybe need to test someday too. By the way for me need to wait a little bit too when watch will be vibrate after ring smartphone, it's all, if i'm not wrong, problem of Amazfit watches. With other manufactor i did not had this problem. But if say honest time between ring and vibrate is about 1-2 second in my situation
xdauser2019 said: I recommend you to test without any amazmod and ect., problem can be with 3rd parties software, apps. If you still have problem when you using everything from manufactors: stock rom on smartphone/smartwatch and everything is updated, i recommend you to connect with Amazfit support https://en.amazfit.com/support.html or https://us.amazfit.com/contact (this is US support, but they taking advice for all costumers, keep patience checking, often is disconnected). I don't have this porblem, coz if say honest i don't talk right now over watch. But maybe need to test someday too. By the way for me need to wait a little bit too when watch will be vibrate after ring smartphone, it's all, if i'm not wrong, problem of Amazfit watches. With other manufactor i did not had this problem. But if say honest time between ring and vibrate is about 1-2 second in my situation Click to expand... Click to collapse I did, factory reset on both watch and phone stock rom (then LineageOS 9.0 on phone), the same issue. Wrote to official support also today, no reply yet thou. I also have a second of lag when the watch starts to ring, but i have to wait over that a few seconds to be able to really answer the call. It is usable now with waiting 4-5 seconds, i just have to not forget it and answer the call too fast...
Stratos BT disconnect not recognized by watch
My Stratos does not recognize when I disable BT on my phone. On the Watchface is no information and even in the settings screen(swipe down) the watch shows it is connected. I am on international 2.3.10.5. I am using Amazmod and GreatFit Watchface. I would like to know by checking the Watchface if the watch is connected. Any suggestions? Thanks a lot.
What phone model and OS? I have seen this happening with some Android phones... Do you still get notifications on watch or it shows as connected but no data come through?
Strange This is super strange! I checked what you proposed and I have never expected to actually receive notification on my watch with BT on the phone turned off. But I do! So the behaviour of the watch is correct because it is not disconnected. I am using Nexus 5X with Lineage 15.1 (Android 8.1)
It seems some phones keep BLE on despite the main BT is off... Check phone settings, it may be related to Google using BT to scan nearby devices for location, etc.
Problem with zepp
I' ve just recently bought redmi note 9 pro. My amazfit watch is t-rex. Since then every time I turn on my redmi , I have to enable gps, in order to connect the t-rex with zepp app, otherwise it doesn't connect. The message that appears is in the screenshot
Same with Amazfit Bip Had same issue with my Amazfit Bip initially when the app was released. After about a dozen connects it now allows me to sync with bluetooth only however the initial sync only loads steps counts, I have to close app fully and reload to get it to sync any sleep data. Weird!
I simply uninstalled the app. It has become pretty useless.
DarthJabba9 said: I simply uninstalled the app. It has become pretty useless. Click to expand... Click to collapse But if I do this I wont be able to connect my t-rex with the phone any more.
SACS73 said: But if I do this I wont be able to connect my t-rex with the phone any more. Click to expand... Click to collapse True. For me, it was nothing lost, because nothing I did (other than uninstalling it and then installing it again - every time) would make it connect. It was working perfectly fine before it became zepp.