Hello everyone
I am having Xiaomi MI 11 lite 5G and Galaxy Watch. I am having problem with losing bluetooth connection between them. I searched a lot of forums about this solution but without any luck.
I’ve already tried resetting and reinstalling everything. I’ve set the settings for all three samsung apps to autostart and disabled battery optimization for them, also made an exception in the security memory cleaner app.
But the watch is constantly losing connection. It is interesting that one day he works normally, other day he constantly loses. The loss of a connection becomes more frequent, as if it is getting worse.
When i open galaxy wearable app it says reconnect but nothing happen so i have to close app disable and enable bluetooth and then open app and connect.
I doubt there is a problem with some application because when I disable / enable the bluetooth, watch vibrates again to signal that the connection is lost, although it already has a lost connection icon on the watch.
Does anyone have similar difficulties or a solution to this problem?
Just updated to miui 13 and I also have a gear 3 watch, experienced the same issues but after update haven't found a single disconection, I'm using xiaomi.eu miui 13
Thank you for your reply.
Last week I updatetet to xiaomi.eu miui 13.
Now everything works as it should.
Related
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
I have the Xiaomi Amazfit Stratos watch, which worked well with my old Mi A1. However, since getting the Poco F1 notifications to the watch do not work (unless the app is open in the foreground). In addition, the VW Connect app (also a background app that uses GPS and connects automatically) did not pick up any trips made since using pairing with the new phone....
This made me think it was something to do with the MIUI battery saver settings. Since then I have changed the settings on both these apps to 'No restrictions' and it has made a slight improvement (I would say about 50% of the notifications are making it to the phone now). So I am at a bit of a loss now....
You would assume that a smartwatch made by Xiaomi would work seamlessly with a phone of the same manufacturer.... but it seems not!
Any ideas would be much appreciated.
I had a Ticwatch E before switching to the mix 3 but using it on the mix 3 now I've had so many connectivity issues. Sometimes I'd get notifications and then sometimes the watch would disconnect, just wondering if anyone is using a smart watch that doesn't have these issues or if this is just an issue with the mix 3 and ticwatches.
Thanks
My moto 360 1st gen has also some issues.
Gesendet von meinem MIX 3 mit Tapatalk
I have Huawei Watch GT, no problems at all.
No problems at all here with a Huawei Watch 2 Classic
Amazfit Pace and no problem
Dont know what happens but now All Apps works and the notification grafics are now perfekt again. No more Problems with transpatency
Gesendet von meinem MIX 3 mit Tapatalk
I had some connection issues as well.
I figured out that it only loses connection when I kill all apps and so i tinkered with a few settings:
- disable power-saving for wear OS app
- enable auto start for wear OS
It still loses the connection if you kill all apps but reconnects as soon as you check your watch.
It never loses the connection if I don't kill apps (anymore?).
Hope that helps!
prozac192 said:
I had some connection issues as well.
I figured out that it only loses connection when I kill all apps and so i tinkered with a few settings:
- disable power-saving for wear OS app
- enable auto start for wear OS
It still loses the connection if you kill all apps but reconnects as soon as you check your watch.
It never loses the connection if I don't kill apps (anymore?).
Hope that helps!
Click to expand...
Click to collapse
Open recent apps, long press Wear OS app, and tap on the lock, now, even if you kill all apps, Wear OS won't be killed
Williammmm said:
Open recent apps, long press Wear OS app, and tap on the lock, now, even if you kill all apps, Wear OS won't be killed
Click to expand...
Click to collapse
True, but than you have to open the app in general while it is never actively opened otherwise.
Same thing with automatic started music that gets killed, even when you don't have your player open.
I've got the Galaxy Watch (46mm) and I am able to use it but with a caveat; if you unlock the bootloader you MUST root with Magisk in order to hide the fact that the bootloader is unlocked. Otherwise, the Galaxy Wear app and Samsung Pay with not even open, and you won't be able to connect the Galaxy Watch to your phone. If you keep the bootloader locked and don't want root access, it works normally.
I have a Gear 2 I flashed with Android Wear and it's been working perfectly.
My Watch GT doesn't automatically reconnect after I go out of Bluetooth range.
I've whitelisted all apps from the MIUI battery saver and granted all permissions.
I have also LOCKED the Huawei Health app to stop the system from closing it.
Once Bluetooth has disconnected, The ONLY way to get the watch to reconnect, is by opening Huawei Health or toggling the phone's Bluetooth off & on.
Unsure if it's the Huawei Health app or MIUI that is at fault.
Very frustrating.
Also using a Galaxy Watch (46mm) and it works great for the most part. You do have to root with Magisk to hide the unlocked bootloader (if you unlocked it). Other than that, for some reason I lose notifications on the watch almost every time I reboot the phone or put it in battery saver/extreme battery saver. This has something to do with the way MIUI handles notification access and is very annoying since the only way to fix it is to disconnect the watch from your phone (as in unlink it which wipes the watch NOT just turn off bluetooth), uninstall the Galaxy Wearable app completely, reboot, then re-install the Galaxy Wearable app, reconnect the watch, and restore my backed up data to the watch. It only takes a few minutes now that I know exactly what fixes it but it is really annoying that I avoid using battery saver and rebooting just to not have to deal with uninstalling and reinstalling the watch. If anyone has any better fix for this please let me know lol.
Does anyone use a FitBit? My wife bought a FitBit Versa and it constantly shows and error about the notifications not being available. She has to constantly reboot the phone to get notifications working correctly.
Rockmadeofrock said:
Also using a Galaxy Watch (46mm) and it works great for the most part. You do have to root with Magisk to hide the unlocked bootloader (if you unlocked it). Other than that, for some reason I lose notifications on the watch almost every time I reboot the phone or put it in battery saver/extreme battery saver. This has something to do with the way MIUI handles notification access and is very annoying since the only way to fix it is to disconnect the watch from your phone (as in unlink it which wipes the watch NOT just turn off bluetooth), uninstall the Galaxy Wearable app completely, reboot, then re-install the Galaxy Wearable app, reconnect the watch, and restore my backed up data to the watch. It only takes a few minutes now that I know exactly what fixes it but it is really annoying that I avoid using battery saver and rebooting just to not have to deal with uninstalling and reinstalling the watch. If anyone has any better fix for this please let me know lol.
Click to expand...
Click to collapse
No problem using the Galaxy Watch with unlocked bootloader, not rooted. Using Xiaomi.eu rom.
dunjamon said:
Does anyone use a FitBit? My wife bought a FitBit Versa and it constantly shows and error about the notifications not being available. She has to constantly reboot the phone to get notifications working correctly.
Click to expand...
Click to collapse
I bought the FitBit Versa and had to return it due to notifications never working, even with all battery saving options disabled it just didn't work. Picked up the Galaxy Watch Active instead and that works perfectly, I'd recommend it instead if you still have the option of returning the FitBit. Used it with MIUI at first which worked perfectly after disabling the battery saving features.
I'm now rooted with Pixel Experience, had to download an older version of Samsung Pay to get it to work without detecting root and it's working great on that too.
SamLovesJam said:
I bought the FitBit Versa and had to return it due to notifications never working, even with all battery saving options disabled it just didn't work. Picked up the Galaxy Watch Active instead and that works perfectly, I'd recommend it instead if you still have the option of returning the FitBit. Used it with MIUI at first which worked perfectly after disabling the battery saving features.
I'm now rooted with Pixel Experience, had to download an older version of Samsung Pay to get it to work without detecting root and it's working great on that too.
Click to expand...
Click to collapse
Well, I've been trying to get her to return the watch, but she's looking at other phones instead. Left her to it. Ha!
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
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.