Call notification issue of Amazfit Verge on Samsung S8+ (Temporarily Solution)
I think maybe I know the problem of call notification of Verge, but I would like to hear more from other person who have this issue before I contact the Amazfit Support.
Samsung S8+: Android 9, update to newest software (2019-NOV-8).
Amazfit Software: update to newest software (2019-NOV-8).
Verge Firmware: 3.2.6.0, US Version.
My Amazfit watches (Pace, Verge, GTR) actually disable all the features because I only need the “Call Notification” function.
Testing procedure:
1. Unpair the Verge (This will cause the Verge factory reset).
2. Use Amazfit software to scan the barcode and activate the Verge.
3. On Verge, swipe left and choose Phone, swipe left 3 times. You will see a "Bluetooth Phone" option.
4. On Samsung S8+, Setting -> Connection -> Bluetooth, You will see all the bluetooth devices.
5. My Pace, Verge and AND GTR have Bluetooth profile, the Verge connect as a headset. Except the Verge, Pace and GTR work fine. This means my S8+ Bluetooth and Amazfit software are OK.
6. The “Amazfit-23F5”is my Verge, tap the DEVICE SETTING icon, You will see the a Call option.
7. If you try to enable the "Calls" option, after swipe the bar, the setting goes back to disable automatically.
8. The only way to enable this option, you need to use Verge (Step 3). You swipe the “Bluetooth phone” bar to off then on again. You will found the Calls setting on S8+ become Enable. This means actually this function control by Verge.
9. Now you can make a call, the Verge will notify there is an incoming call, hang up the call by Verge then call again. The Verge didn’t receive anything (sometime the screen will on, but no vibration, no sound).
10. Go back the check the Step 6 on S8+, you will found the “Calls’ become disable after first call. This cause the notification will not work anymore.
11. So I re-enable the Bluetooth Phone Setting every time after I received a call, this is a “Temporarily Solution” but It worked.
I test with this procedure for 3 times and get the same result !
The communication path should be Verge <-> Amazfit software <-> S8+. So I am not sure why the Calls setting become disable automatically, both of software and firmware may cause this. The call notification didn’t send by s8+ all because the Calls setting was disable.
Please leave your comment and test result, thanks !
Yep, I came to the same exact conclusion. I even factory reset my Verge with the same exact outcome.
What's weirder is the second time I tested a call, it worked fine, but the third call is when the answer phone notification on watch got cleared immediately.
EDIT- I'm using an S10 so I wonder if it's a Samsung issue...
The same problem
I have the same problem. My phone is Samsung A40. I came to the same solution, like you. And after that I've found your post. But I don't know, what to do. I didn't have this problem before. But I don't remember if it was before changing my phone or software.
So I exchanged the watch for a brand new one and the same issue is still there. I don't understand why more people aren't complaining about this.
I also having same issue with my note 10, can't enable the call function
Sent from my SM-N970F using Tapatalk
same problem, samsung S9+ and the test works fine but does not pair with the samsung. whats the easiest way of contacting the support? or has someone found a way by now?
estrre said:
same problem, samsung S9+ and the test works fine but does not pair with the samsung. whats the easiest way of contacting the support? or has someone found a way by now?
Click to expand...
Click to collapse
update: guess what, the support is just some random screenshots, don´t even look at the info you provided (told me to update to the latest version when my version # was already in the ticket). waiting to see if any one of you fine folk can find a workaround
estrre said:
update: guess what, the support is just some random screenshots, don´t even look at the info you provided (told me to update to the latest version when my version # was already in the ticket). waiting to see if any one of you fine folk can find a workaround
Click to expand...
Click to collapse
Yeah, support is just sending me a new one (will be my third now).
Related
Hi,
yesterday i received my Amazfit Verge.
I could not test it completely before an upgrade to OS 3.2.0.7 (I was running 3.2.0.5) came in.
I tested this watch on 2 phones (samsung s9 plus and a Motorola G4 plus).
Before testing I did a reset of the watch.
Both show the same problem, when testing the warnings the incoming call warning does not work.
When a call comes in the warning also does not work on the watch, all other warnings work.
Is this a problem with the watch or is it a software glitch in 3.2.0.7 and how to solve this?
Do you have latest version of Amazfit app installed on phone with all permissions granted? If yes, try adding the phone/contacts/favorites to the notification settings in the app.
deboopi2 said:
Is this a problem with the watch or is it a software glitch in 3.2.0.7 and how to solve this?
Click to expand...
Click to collapse
Interesting - I just checked it with my Verge on 3.2.0.7. The first time I tried, it took relatively long - about 10 secconds - before I received the notification on my watch. The seccond time it came right away.
Have you tried to let it ring a little longer?
I'm running on release 2.6.7
Phone/contacts/favorites are hidden by the smart filter, they should not get selected.
I selected them anyway but the result is exactly the same
I've been waiting for 20 seconds now and I still do not have a notification on the watch.
I have exact same problem. Notification works only when I enable BT call function on watches.
I have the same problem, incoming calls are not visible. Samsung Galaxy S8 Android 9.
same problem here with a Samsung S10.....anyone solved it???
deboopi2 said:
Hi,
yesterday i received my Amazfit Verge.
I could not test it completely before an upgrade to OS 3.2.0.7 (I was running 3.2.0.5) came in.
I tested this watch on 2 phones (samsung s9 plus and a Motorola G4 plus).
Before testing I did a reset of the watch.
Both show the same problem, when testing the warnings the incoming call warning does not work.
When a call comes in the warning also does not work on the watch, all other warnings work.
Is this a problem with the watch or is it a software glitch in 3.2.0.7 and how to solve this?
Click to expand...
Click to collapse
Did you marked in Watch App, notification section call/phone? Do you getting all others notifications like message, calendar and ect.? In 3rd screenshot https://play.google.com/store/apps/details?id=com.huami.watch.hmwatchmanager you can see notification area. Here you must add all apps from yours phone from which you want to get notifications. If will not help, try reset factory settings of watch. For me working everything fine. Also, if in watch you will not see caller name, need to give permission of that (in smartphone). By the way i hope you understand that watch with smartphone must be connected via bluetooth?
P.S. I got 3 updates, now i got latest where was integrated Alexa (working in US only). With all software versions which i had and have working all notifications very well, included call. I guest you will not added it in Watch App notification section that. I have not Xiaomi brand smartphone too. Brand of smartphone havn't any effect in getting notifications I hope But maybe China manufactor don't like Samsung, so... you can chat with Amazfit support us.amazfit.com. But i'm really don't want to believe that this is true. Maybe something bad is with Samsung smartphones, cos this problem have a lot of people here
I had a Xiaomi Mi9 before and all worked very well!!
Now that i switched to a S10 with all the same settings that i had before, the notifications (whatsapp, telegram, gmail..ecc..) are perfect BUT if someone calls me the Verge vibrate for a second, the screen lights up and...stop!! no name, not even number calling.....when the call attempt ends it also notify me the missing call....!! I am pretty sure this problem is connected to samsung phones with pie but i really hope there is a way to fix it because i would hate to sell my Verge.....
agv83 said:
I had a Xiaomi Mi9 before and all worked very well!!
Now that i switched to a S10 with all the same settings that i had before, the notifications (whatsapp, telegram, gmail..ecc..) are perfect BUT if someone calls me the Verge vibrate for a second, the screen lights up and...stop!! no name, not even number calling.....when the call attempt ends it also notify me the missing call....!! I am pretty sure this problem is connected to samsung phones with pie but i really hope there is a way to fix it because i would hate to sell my Verge.....
Click to expand...
Click to collapse
I starting to think that this is not Verge problem, but problem is with Samsung smartphones, even newest models. I have none Xiaomi smartphone and it's working fine. It's not Samsung too. So i advise you to chat with Samsung support too, but ofcourse try to talk with Amazfit support us.amazfit.com (it's US, but only this support have live chat) if will be closed chat, try en.amazfit.com via mail support, but keep in mind today is saturday, so answer via mail or chat will be opened only from monday. It can be that these models working with each other with this problem
Answer from Amazfit Support:
Amazfit Support (Amazfit)
May 12, 23:02 PDT
Hi Milan,
Thank you for contacting Amazfit Customer Support. We apologize if the product caused you any inconvenience!
Could you please let us know where did you purchase your watch? Please kindly attempt the following steps:
1. On the home screen of the Amazfit Watch App tap Me in the lower right hand corner tap Setting tap Notifications setting tap the toggle switch to enable Push notifications tap App notification setting and select app in the list to enable or disable the specific notifications.
2. Make sure Not push, phone’s screen is ON is turned off.
3. Check if you enabled the Silent mode on the watch. If you enabled silent mode, you can't receive any notifications at all.
4. Make sure your phone notification bar is functioning. Please note that alerts will only appear on watch if they pop up on phone.
5. Open Amazfit Watch APP MeSettingSystem PermissionsAccess notificationstoggle on Amazfit Watch if it’s off. If it’s on, turn it off and on, reboot your phone, restart App and try again.
6.Open Amazfit Watch APPMeSettingSystem PermissionsAutostart tap Background operation permission setting to add Amazfit
Watch APP to the white list of background operation permission.
7. Open Amazfit Watch App Me Setting System Permissions Read contacts to allow Amazfit watch app to read your contacts in settings or the security app on your phone.
If the issue persists, please send us all the pictures and show us how you enabled the permissions. Then submit a feedback from the watch and Amazfit Watch App. Also send us the Amazfit ID to help us locate the issue.
Sincerely,
Seven
Amazfit Support
everything is checked and there is no incoming call anyway
yeah same preset answer they give to anyone.......
i also have all checked but the problem persists!!
I think it's standard form of answer to costumer. So consultants doing just copy - paste process from base of information. I think company request to do that from theirs workers, so don't be suprised. By the way i got some too about battery, but it's better to get answer like this one if don't get it at all, i had some examples when i did not got answers at all or answers into my questions
Any idea how to fix it?
zapas17 said:
Any idea how to fix it?
Click to expand...
Click to collapse
Try to do factory reset of watch. I tried several times and after last reset i could hear caller when i answered to ring. But i need to check again that. By the way i did some reset of watch without restore of my data. So maybe this can help you.
No helps. I think it's problem new software for verge.
Still happens on my new Note 10 too, damn it! Coming from Note8 I havent experienced this before.
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...
Hello all, new user here.
I just got Amazfit Verge, I'm using it with iPhone XR and I have a problem, the watch has constant reconnect issues, when for example I'll go out of phone range, it won't reconnect (or reconnect only one device as there are two devices visible in bluetooth menu, one for calling and contacts and one for notifications it seems). I've removed and forgot the device that is for calling and now it reconnects like 70% of time which is still no good. I didn't find any info about that in google but maybe someone has faced similar issue and found a fix or has a clue if any custom rom fixes that?
I like the watch a lot but that problem is realy annoying.
i have same problem with my verge and iphone 7. i did factory reset both devices and nothing changed. after that i synced the watch with old an android phone s3 mini and the watch perfectly worked. i think there is a problem with iOS
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.