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.
Related
So, I've had my Gear S now for about a week, and LOVE it. The connection stuff has me a bit confused though. I have it paired with an AT&T Note 4. There are a few things I have questions about...
If I reboot the phone, the watch will only connect to Gear Manager remotely. Shouldn't it connect to Bluetooth first? I have to go into Gear Manager and disconnect the remote connection, then it will reconnect via Bluetooth.
Under what circumstances does the phone forward calls/sms to the watch? For example, on purpose, I left my phone at home one day, and went out for a drive. Calls and SMS that were made came from the watch's number. I can't say about the receiving end because I didn't receive anything LOL.
Sometimes, if I go out of Bluetooth range at home, the home wifi will kick in, but repeatedly get a message on the watch that the forwarding function failed.
I'm definitely keeping this baby, but just need a little help in understanding it fully.
diehardbattery said:
So, I've had my Gear S now for about a week, and LOVE it. The connection stuff has me a bit confused though. I have it paired with an AT&T Note 4. There are a few things I have questions about...
If I reboot the phone, the watch will only connect to Gear Manager remotely. Shouldn't it connect to Bluetooth first? I have to go into Gear Manager and disconnect the remote connection, then it will reconnect via Bluetooth.
Under what circumstances does the phone forward calls/sms to the watch? For example, on purpose, I left my phone at home one day, and went out for a drive. Calls and SMS that were made came from the watch's number. I can't say about the receiving end because I didn't receive anything LOL.
Sometimes, if I go out of Bluetooth range at home, the home wifi will kick in, but repeatedly get a message on the watch that the forwarding function failed.
I'm definitely keeping this baby, but just need a little help in understanding it fully.
Click to expand...
Click to collapse
With my S5 initially, Remote Connection would kick in after a few minutes out of Bluetooth range. But, when I was back in Bluetooth range, I would have to do what you are doing to drop RC. I had a Gear 2 Neo prior to Gear S, don't know if that was any issue. .I did a factory rest on S5 ( to get rid of root and some other things) , and now watch connects and disconnects to RC by itself and rather quickly. BTW, when in RC, all texts and calls to S5 do come to Gear S. If I were in your shoes, I might try to reinstall Gear on phone before wiping phone. IF you do wipe phone, Gear S will be reset during the pairing process, so you may want to back up your Gear S data prior.
Op. Under settings-connections-mobile network, do you have it set to auto connect? On the phone side of things for Bluetooth settings, gear s contented to phone audio?
jerrycycle said:
Op. Under settings-connections-mobile network, do you have it set to auto connect? On the phone side of things for Bluetooth settings, gear s contented to phone audio?
Click to expand...
Click to collapse
Yeah, all that was set, but I ended up wiping both the phone and the watch and everything seems fine now... Still loving the watch... wondering how they'll make the next one better..
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.
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).
Hello I got problem with amazfit stratos 3. I cant pair it with any phone. Its probably becouse I accidentialy factory reset it while airplane mode. It seems like bluetooth is not working after reset becouse still in airplane mode. Now I have no access to settings to turn off airplane mode becouse watch restarted in pairing mode. Is there any option to anyway enter settings in pairing mode? Or what should I do?
malycinek said:
Hello I got problem with amazfit stratos 3. I cant pair it with any phone. Its probably becouse I accidentialy factory reset it while airplane mode. It seems like bluetooth is not working after reset becouse still in airplane mode. Now I have no access to settings to turn off airplane mode becouse watch restarted in pairing mode. Is there any option to anyway enter settings in pairing mode? Or what should I do?
Click to expand...
Click to collapse
I know few people with bluetooth issues on the watch. I've faced some problems to connect the watch to the app.
You can try:
Make sure you don't have the watch still paired in Amazfit app, if so, just unpair it from the app.
Remove the watch from Bluetooth paired devices.
Disable bluetooth on phone, force close Amazfit app and clean cache of the app.
Reboot into Ultra mode:
Code:
adb reboot mcu
and then go back to Smart mode.
Use AeX Amazfit mod app, since I'm using this app, bluetooth connection has improve in my case: https://portal.mi-room.ru/files/aex-amazfit-mod/
If nothing of this works, claim for your warranty.
Thank you, but nothing helped. Ill contact support. If anyone else have any idea how to solve this problem please reply. Btw, checked bluetooth status by adb, it says its off sadly
malycinek said:
Thank you, but nothing helped. Ill contact support. If anyone else have any idea how to solve this problem please reply. Btw, checked bluetooth status by adb, it says its off sadly
Click to expand...
Click to collapse
If you use:
Code:
[COLOR="Blue"]adb shell dumpsys bluetooth_manager[/COLOR]
You will get:
Code:
enabled: false
state: 10
address: D8:80:3C:3B:71:F3
name: Watch
Bluetooth Service not connected
Even if BT is correctly connected so is not 100% trustable.
But yes, it's better to contact them.
If you want to do some other test, you can install PaceOn, which has WiFi/BT toggles and try to enable BT.
Before installing the apk, bypass the QR screen with:
Code:
[COLOR="blue"]adb shell pm hide com.huami.watch.setupwizard[/COLOR]
install the app, and play around with BT toggle.
If you want to launch the QR again:
Code:
[COLOR="blue"]adb shell pm unhide com.huami.watch.setupwizard
adb shell am start -n com.huami.watch.setupwizard/.InitPairQRActivity[/COLOR]
Sadly still nothing. Updated firmware by OTA to 4.2.4.0, no results. Also tried to play with bluetooth. Nothing happend.
If anyone still need information how to pair. It worked somehow, after few days off becouse of battery gone. Battery went to 0, then watch shutdowned. After power on, there is information your watch need alteast 5% battery to pair. If you click on it, pairing QR appears for a moment, then i scanned it before dissapeared and it worked.
Hello all,
Sorry for the offtipic post.
I am new at running and looking to get a sports watch to track my runs along with little smart features like showing notifications and controlling music from my phone.
I have short listed two watches according to my needs. Amazfit stratos 3, price 299 SGD or Garmin Vivoactive 3 element, price 267 SGD.
I need accurate GPS and HR along with less buggy software on watch and app.
Need help in deciding one of these two.
I have same problem.
It can pair only in ultra mode.
What should I do?
try to turn on GPS on the phone. for me was only option it paired.
For some time music controller doesn't work. Has anyone the same problem?
Hello all. I will continue here with my issue.
I have amazfit Stratos 3 (rom version 4.2.8.0)
I used the mobile phone HUAWEI MATE 9. No issue with the pairing in the past.
I bought a new mobile phone, ONE PLUS 9, and the issue started.
I had no issue with the old phone; the watch was always connected only with Bluetooth, without location on. The connection was stable without any problem.
I bought a new mobile phone, moved the APP ZEPP, and paired the watch. It worked, but it was not stable. The connection was dropping. I changed the phone's battery customisation for the app, so the app was always on, but nothing changed. Then I upgraded the firmware to 4.2.8.0.
Long story short, I have an issue with both phones from the firmware upgrade.
I can pair the watch with the old phone, and the connection is stable until the first time that watch loose connection with the phone. Then I cannot pair it anymore, and I need to factory reset the watch to pair it again over and over again. The connection with the new mobile phone does not work anymore.
I mostly used watch for 24/7 notification. And this is getting annoying to me.
What can I do? I appreciate your help.
UPDATE 1: with several attempts, I manage to pair the new phone with Stratos 3. BT and location on. IS location necessary that is on, because it draining my battery. On the previous phone, my location was off and the watch connected without issue.
UPDATE 2: The connection was paired for cca 2-3 hours. But in the last 30 minutes, somehow the connection was lost and I cannot pair it again.
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.