Amazfit Verge connection problems on iOS 13.1.3 - Amazfit

Anyone noticed Bluetooth issues resulting in problems with sync and notifications when iOS updated to 13.1.2 and still not fixed with 13.1.3
I performed a network reset on the phone (iPhone 8s) and it was better only for a day
Have to constantly off/on Bluetooth and sometimes reboot the phone.
Have already tried factory reset watch and re pairing
Sent from my iPhone using Tapatalk

Related

Cloud Sync

Has anybody got Cloud Sync to work?
I want notifications to go to my watch without a bluetooth connection.
I can connect the watch to wifi but I can't get any updates from my watch.
I have the same problem. I am using a Note 4.
I already did a reset without a result .
The asus support could not help me.
It seems that not many owners tries to use this feature. Would be interesting if any zwatch 2 works with wifi.
I know mine does not respond to 'OK Google' when I am out of BT range, even if it says it is connected to WiFi. I do seem to be able to get notifications though, and I have always been able to execute Tasker Tasks from Wear Tasker.
But Android Wear docs say "OK Google" should work. I have seen similar reports from others using different watches so I am guessin this is just some typical broken Google goodness we'll have to wait for them to straighten out.
I used to have tons of sync issues with my Zenwatch (both first, second gen), and this trick solved all my issues - have no idea how and why, but it worked:
Just let my Zenwatch battery go empty, did not charge it for 4-5 days, than recharging. It connected my phone (mate 7) again normally, and all syncs (in my case weather, notifications, step counts) worked fine again - permanently. NO idea how it works (emptying cache watch?), but it worked for me.
All other suggestions of forums (re-installing, reconnecting): not..
Jus my 2c
After a bit of research and some common sense troubleshooting, I have my watch working as expected on my local Wi-Fi network.
I read something somewhere that Wear has had some issues on higher Wi-Fi channels. I also downloaded WiFi Analyzer to check used channels in my area. All APs were in the neighborhood of ch 6-11.
I forced my router to ch 1 and bingo. Phone is now upstairs at the other end of the house and everything is working great, including 'OK Google' (knock on wood).
My ZW 2 has a working wifi connection (2.4Ghz Port1). I know that because google maps on the watch is working even when the phone is switched off.
My problem ist, that no notification appears on the phone and no "ok google" command works, when phone and watch are only connected via wifi and bluetooth is switched off.
The asus support told me, that i am the only person with this problem who contacted them.
Seems to be a problem with my galaxy note 4.
I will give it a try with a xperia z3 compact the next days.
I can´t believe this is a hardware problem.
roboterente

Moto Z Android 7.0 Nougat issues

I have a Moto Z Force (Droid), and got the OTA update for Nougat about a week ago (build NCL25.86-11). Since the update, I've had a lot of problems:
* Wifi issues: Right now my phone can't see any of the 10 or so access points near my house.
* Bluetooth Audio issues: Frequent skips listening to audio over bluetooth (every several minutes)
* Background Sync issues: Hangouts no longer syncs in the background, and Facebook seems to have occasional syncing issues. I get no Hangouts notifications at all (until I open the app), and my Facebook notifications are sometimes missing or delayed.
I think I may be having battery life issues with my Incipio battery Moto Mod, but I'm not sure about that.
Also, I can't remember if I tried this before the Nougat update, but when I'm using bluetooth and use voice commands to play music, all further bluetooth media plays back at extremely low (nearly inaudible) volume, even with bluetooth volume turned all the way to max, and I have to disconnect and reconnect to bluetooth to get normal volume on anything again.
I've tried multiple reboots, and a cache wipe. I'm pretty close to doing a factory reset, but was wondering if anyone else is experiencing these issues.
I am definitely seeing the Bluetooth audio skip - I downloaded my album off google play and had the same effect (verifies it isnt data connection). Skips and stutters on all audio - Pandora, Google Play, etc...
I have noticed WiFi issues - drops connection and comes back up
also getting zero notifications on apps.
Another issue I am seeing is the screen locking and becoming unresponsive - couple threads I have seen suggest this is caused by certain apps - so I am having to boot in safe mode and turn them on one at a time - friggin painstaking.
Definitely starting to miss my Note 5
By now I've no 7, but did you try to do a factory reset? I had similar problems with LG devices when upgrading vom 5 to 6. A factory reset resolved them completely. No fun to so so but ...
I've only experienced the Bluetooth issues. They went away after a reboot though.
Sent from my XT1650 using Tapatalk
I have absolutely no Bluetooth, cannot see or be seen by any other device. I'm exchanging it tomorrow.
Looks like my Wifi issue is not a Moto Z specific issue - it's happening exactly as described in this Nexus/Nougat forum post:
Code:
https://productforums.google.com/forum/#!topic/nexus/Qbeb7ZP0wOw
Perform a factory reset, then see where you are. Factory resets aren't as bad as the "old" days. You can pick your backup image date from the Google Welcome menu screens as you set the phone back up. If you use Nova launcher, import your saved desktop back up.
I've had the Bluetooth Audio skips as well. I also cannot use my camera about 75% of the time. It gives me the Camera error, Please restart the Camera app. I did a FDR and issues are still present.
Sent from my XT1650 using Tapatalk
wifi is slow used to get 218 megs down now only 136 down
I can add an other Bluetoorh issue. When I'm listening to podcasts while the phone is connected to the audio system of my car and I get interrupted by a phone call (which is also routed to the audio system of my car) after the call ends audio play back resumes for about half a second and the stops. I've to start it manually on the phone to resume. The podcast app (https://play.google.com/store/apps/details?id=com.bambuna.podcastaddict) is in paused state.
I'm definitely seeing WiFi drops and battery drain and heat issues with my Tumi battery mod. Also seeing screen freezes requiring a power button reset. Am getting very close to factory resetting.
I'm having problems going from WiFi to data. If I boot up the phone, it establishes a data connection. After Wifi is turned on, data permanently turns off and can't be reconnected without restarting the phone.
Note that I am using the phone overseas with a domestic (Japanese) sim card. Just last week however, I was using a Moto Z Droid Play and had no problems whatsoever. The standard Moto Z Droid has more Lte bands as well, so this shouldn't be happening.
I'm assuming it's a problem with WiFi to Lte handover related to Nougat?
TokyoGuy said:
I'm having problems going from WiFi to data. If I boot up the phone, it establishes a data connection. After Wifi is turned on, data permanently turns off and can't be reconnected without restarting the phone.
Note that I am using the phone overseas with a domestic (Japanese) sim card. Just last week however, I was using a Moto Z Droid Play and had no problems whatsoever. The standard Moto Z Droid has more Lte bands as well, so this shouldn't be happening.
I'm assuming it's a problem with WiFi to Lte handover related to Nougat?
Click to expand...
Click to collapse
Rather than restarting, toggle airplane mode.
Sent from my XT1650 using Tapatalk
PiousInquisitor said:
Rather than restarting, toggle airplane mode.
Actually that doesn't work. I tried it numerous times, along with disabling mobile data and then enabling it. I'm going to wipe the phone tonight and do a fresh start to see if that solves the problem.
Click to expand...
Click to collapse
Fix for wrong default APN Settings for O2 on Android 7.0 Nougat
After Upgrade to Android 7.0 mobile data did not work on german O2 Network.
After some research i found the right APN Option:
MVNO-Type have to be changed from IMSI auf „Keine“
Source: Giga.de - Android 5.0 Lollipop-Bugs & Probleme: Lautlosmodus, WLAN, Videowiedergabe & mehr [Ãœbersicht]
After that change another apn appeared called "O2 Internet", selecting it and LTE started to work as expected.
Hope that's help someone.
And here I was thinking this was the smoothest update on any Android phone I've received. I have no issues at all, didn't factory reset either. I also listen to podcast all the time over bluetooth, and never once did it skip. Maybe it's google music issues?
Also battery life has gotten much better.
Bluetooth disconnected issues for me via car Bluetooth since update.
any one having problems with sound cutting out on the phone only way to get sound back is by rebooting ?????????
I think the issues I'm seeing are due to overheating. Seems to happen after the battery pack charging kicks in at 80%. Anyone else notice this?
For the BT skipping/noise, turn off BT and turn it back on. That fixes it for me.
Don't know what's triggering it, though.

Constantly asks for pairing after BT disconnect

Something seems to be wrong since the AW2 update. Any time I go out of range and lose the BT connection, the watch asks to be re-paired with my phone. I need to approve the pairing code on the phone and watch to reconnect. I'm using an Axon 7 running Nougat 7.1.1. I've tried uninstalling Wear, forgetting BT pairing, clearing cache, etc. Anyone have any ideas???
Welcome to the club ^^ You can only minimize the problem by disabling audio to smartphone in the Connection settings of the watch
I have the same problem.
Does anyone know any solution to this?
I would assume this has to be a phone issue, not a watch issue, as I don't have this problem. If mine goes out of range, I'll get the no connection icon, but restarting the watch usually fixes it.

Amazfit Verge with IOS issue

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

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