Amazfit Bip - notifications after reconnection - Amazfit

Hello,
I'm testing Amazfit Bip since yesterday. To receive notifications I'm using Notify & Fitness for Amazfit. It works fine, but problem appears after reconnecting the watch. I mean - Amazfit losts the connection (for example if it's too far from the phone), somebody calls / sends a message, then Amazfit receives the connection back with the phone and shows no new notification. When it's connected again I don't get notifications for messages/calls received when connection was lost. The same is with Mi Fit application. Do you have any idea how to solve it?

The same here.
What firmware is on your watch?

Mr.kabas said:
The same here.
What firmware is on your watch?
Click to expand...
Click to collapse
V0.1.1.36

Only using third party apps, mostly paid ones. Some can detect that you lost connection and send the notification once the watch is connected. For instance, Notify & Fitness on PlasyStore.

you can try alert bridge on playstore, which is also free. Is not customizable as notify o similar apps (which however need to be paid), but if you don't pretend too much on notifications side, it does what you're looking for. give it a try

Related

phone connected indicator (amazfit pace)

Is there a way to show on watches, that my phone is connected/ disconnected from mobile via bluethooth ?
It whould be nice to know i will not receive notification, because i am too far from my mobile. It could be one of indicators on watch face too.
Try AmazMod + GreatFit watchface (you need to install both on watch, and AmazMod on phone too), it will be included in the next release.

Verge OS 3.2.0.7 incoming call warning

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.

Amazfit GTR issues

Beside the well known GPS issue, the GTR have other limitations that are bothering me.
1. When I receive a call, a can only deny or silent, but cannot accept, even when i have a bluetooth fone on.
2. The Whatsapp notifications are fine, whith whatsapp logo on. But othe apps notifications come with genneric and ugly "app" logo.
I also have Amazfit Verge and things are working perfectly fine.
I only use the Amazfit App.
So, anyone knows how to fix or improve this things?
Thanks!

Bad bluetooth connection with Amazfit and Bip/Bip S

I've been using an Amazfit Bip together with the Mi Fit app for a long time without any problems. The Bip hardly ever lost connection to the phone. Then I bought an Amazfit Bip S and as the Mi Fit app does not support it, I had to use the Amazfit app. I recognized that the Bip S permanently lost bluetooth connection to the phone, no matter what settings I changed. So I thought it would be a problem of the Bip S and bought a normal Bip again. But same problem... if the phone does not lie directly on the table, most of the time Bip has no bluetooth connection. Even if the phone is in its case on my belt, the Bip loses connection.
So it must have something to do with the Amazfit app, I guess. Somewhere I read that if you uninstall and reinstall it, Bluetooth connection problems may be gone. But if I uninstall the app, I lose all data, so before I do that I try to investigate what could be the problem.
The phone is a Blackview BV9700 Pro. I already cleared all data and cache of the Bluetooth app. I restarted the phone. I turned Bluetooth off and on again. I turned the option for a permanent notification in the Amazfit app on and off, makes no difference.
Can anyone confirm that the Amazfit app has a bad Bluetooth connection compared to the Mi Fit app? Could the problem be caused because both apps were installed at the same time at the beginning? I had Mi Fit installed, installed Amazfit and because the Bip was recognized by both apps I uninstalled Mi Fit and kept only Amazfit.
In case my english sounds strange from time to time: I'm from Germany
Homer J. S. said:
I've been using an Amazfit Bip together with the Mi Fit app for a long time without any problems. The Bip hardly ever lost connection to the phone. Then I bought an Amazfit Bip S and as the Mi Fit app does not support it, I had to use the Amazfit app. I recognized that the Bip S permanently lost bluetooth connection to the phone, no matter what settings I changed. So I thought it would be a problem of the Bip S and bought a normal Bip again. But same problem... if the phone does not lie directly on the table, most of the time Bip has no bluetooth connection. Even if the phone is in its case on my belt, the Bip loses connection.
So it must have something to do with the Amazfit app, I guess. Somewhere I read that if you uninstall and reinstall it, Bluetooth connection problems may be gone. But if I uninstall the app, I lose all data, so before I do that I try to investigate what could be the problem.
The phone is a Blackview BV9700 Pro. I already cleared all data and cache of the Bluetooth app. I restarted the phone. I turned Bluetooth off and on again. I turned the option for a permanent notification in the Amazfit app on and off, makes no difference.
Can anyone confirm that the Amazfit app has a bad Bluetooth connection compared to the Mi Fit app? Could the problem be caused because both apps were installed at the same time at the beginning? I had Mi Fit installed, installed Amazfit and because the Bip was recognized by both apps I uninstalled Mi Fit and kept only Amazfit.
In case my english sounds strange from time to time: I'm from Germany
Click to expand...
Click to collapse
Hello,
Few things:
- I would recommend you to use only one App, AmazFit or MiFit at a time. I guess AMazFit is preferable depending on the watch you have. Unpair from one app and uninstall the app you don't want to use
- if you uninstall and reinstall the Amazfit or MiFit app with same credentials, Mi account or with mail/phone number, you should recover your data saved and you won't loose all your history. Maybe the one from the current day, I think. I jumped from MiFit to Amzfit with same account with no problem, recovering data for many years
- concerning the bluetooth, not sure what OS your are using, iOS or Android. You could check in the Amazfit or Mi Fit app properties if the OS is not using "battery saver" functions. Sometimes, by default, the battery saving is in "restricted mode" which can affect connections like wifi/bluetooth to save power. Try to see if you have this battery saving function ON and set to "no restrictions" - at least this is what I do on my Android phone.
Tzar92 said:
Hello,
Few things:
- I would recommend you to use only one App, AmazFit or MiFit at a time. I guess AMazFit is preferable depending on the watch you have. Unpair from one app and uninstall the app you don't want to use
Click to expand...
Click to collapse
Yeah - as I wrote I uninstalled Mi Fit and only use Amazfit now.
- if you uninstall and reinstall the Amazfit or MiFit app with same credentials, Mi account or with mail/phone number, you should recover your data saved and you won't loose all your history. Maybe the one from the current day, I think. I jumped from MiFit to Amzfit with same account with no problem, recovering data for many years
Click to expand...
Click to collapse
Hm, now as you said it... the Amazfit app also loaded the data from the Mi account.
- concerning the bluetooth, not sure what OS your are using, iOS or Android. You could check in the Amazfit or Mi Fit app properties if the OS is not using "battery saver" functions. Sometimes, by default, the battery saving is in "restricted mode" which can affect connections like wifi/bluetooth to save power. Try to see if you have this battery saving function ON and set to "no restrictions" - at least this is what I do on my Android phone.
Click to expand...
Click to collapse
The phone uses Android 9. The Amazfit app is not restricted by any battery saving modes as I put it on "Not optimized" just like the Mi Fit app before.

Amazfit Bip S Lite Notification Issues

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.

Categories

Resources