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.
Related
Hi!
I am not getting any notifications pushed to my G Watch any more.
Usually, the watch vibrates and shows a notification card when e.g. I receive a new mail (K-9) or a new Threema message. However, it has stopped now. I still see new messages on my mobile, but my watch just seems to ignore them completely.
The watch is connected to the mobile (there is no crossed out "cloud" symbol on the display) and I also still receive calendar schedules on my watch.
I have browsed through all the settings, but I cannot find anything that seems to be configured wrong.
Any ideas?
Thanks!
shredzone said:
Hi!
I am not getting any notifications pushed to my G Watch any more.
Usually, the watch vibrates and shows a notification card when e.g. I receive a new mail (K-9) or a new Threema message. However, it has stopped now. I still see new messages on my mobile, but my watch just seems to ignore them completely.
The watch is connected to the mobile (there is no crossed out "cloud" symbol on the display) and I also still receive calendar schedules on my watch.
I have browsed through all the settings, but I cannot find anything that seems to be configured wrong.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Did you mute the watch on accident? Swipe down from the top of the screen on the watch and if you see a bell with a line through it the watch is muted which means no notifications will be shown or buzzed.
mapatton82 said:
Did you mute the watch on accident? Swipe down from the top of the screen on the watch and if you see a bell with a line through it the watch is muted which means no notifications will be shown or buzzed.
Click to expand...
Click to collapse
I have already checked that the watch is unmuted. It also does vibrate, e.g. on incoming calls.
It's just that notifications from the notification bar do not appear on the watch any more. I also checked the "Security" - "Notification Access" (roughly translated from German, I hope you know what I mean) configuration on the mobile and verified that the "Android Wear" app is enabled.
shredzone said:
I have already checked that the watch is unmuted. It also does vibrate, e.g. on incoming calls.
It's just that notifications from the notification bar do not appear on the watch any more. I also checked the "Security" - "Notification Access" (roughly translated from German, I hope you know what I mean) configuration on the mobile and verified that the "Android Wear" app is enabled.
Click to expand...
Click to collapse
Repair with blutooth.... Restart it...and last reset.
Sent from my LG-D850 using XDA Free mobile app
blaker13 said:
Repair with blutooth.... Restart it...and last reset.
Click to expand...
Click to collapse
I removed the bluetooth pairing, deinstalled all Wear related apps, made a factory reset on the watch, started from the very beginning. And still... No notifications.
I hate my G Watch... :crying:
I feel like an idiot... :silly: I have tried everything on my watch. However, after restarting my Nexus 5, notifications are shown on the watch again.
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
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...
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).
Hi,
Every once in a while I get the message 'connection failed, update to the latest app to synchronize data'. I click the message away and I get back to my watchface, only my screen stays always on after getting this message. I always have to reboot...
I did already a factory reset, but didn't helped. I have a custom watchface, could that be the problem ? Or is it something else ? Anybody ?
Does it happen when you have default watch face?
iyengar said:
Does it happen when you have default watch face?
Click to expand...
Click to collapse
That I have to test...but don't want to have the standard facewatch anyway...
I did test it. Have occasionally the message on all tried watchfaces...I use the zepp app in combination with notify and fitness. Any one a solution ?
Maybe downgrade firmware and then update again to latest firmware? This sometimes fixes bugs..
I have the exact same problem with the Amazfit GTS . I have the same combination (Zepp app + Notify and fitness) and every few hours (or even more frequently) I get the same message and the screen stays on until I notice. Even if I press the screen for the message to go away the screen stays on until I also press the physical button.
Also besides that, the battery drain is awful. I used to get around 20-22 days of battery (with Amazfit app and Notify and fitness and everything enabled, even continuous heart rate) and now with the exact same settings i 5-6 days.. I can only get 1 day more if I disable things.
Problems started back in late August, early September when the Amazfit app changed to Zepp app but I am not sure if this is a fault of Zepp app or a problem between notify and fitness and the new Zepp app.
I have tried to do a factory reset to the watch, to delete zepp app and add it again etc etc but nothing changed. I have the default watchface and never used a custom one.
If someone finds a solution please inform us.
Just curious if anyone found a solution. I am having the same problem with connection failed, update to the latest version and I am on the latest version of notify app. Please help, thanks.
Without notify installed I have no problem.
By the way.....
I am on Android 11 with OnePlus nord