Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
mickmel said:
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
Click to expand...
Click to collapse
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
EDIT:
PS. It is worth noting that the watch does NOT display the disconnect icon when this happens (usually if you walk out of range you get a little cloud with a line through it)
Azarin said:
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
Click to expand...
Click to collapse
I'm not getting extended disconnects; just failing to answer questions about half the time. If it fails, I can try again and it often works.
mickmel said:
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
Click to expand...
Click to collapse
I just got my LG G Watch and paired it with my stock Moto X running 4.4. It paired no problem but I would say 95% of the time I get a disconnected message when doing a voice search. It is pretty infuriating.
Notifications still seem to come through and I still get served cards but voice search fails almost all the time. When I initially went from Wifi to 4g it worked for one search and then back to disconnected. It doesn't seem to be a phone problem since people on here are using a number of different phones. This is a bug that needs to get fixed ASAP by Google.
I am disappointed but hopeful they can get this quickly fixed.
I'm experiencing the exact same thing on my Gear Live. Its paired with stock S5. I just tried for like 5 minutes to get it to save a note and it would think for a while and then just disconnect.
mosi76 said:
I just got my LG G Watch and paired it with my stock Moto X running 4.4. It paired no problem but I would say 95% of the time I get a disconnected message when doing a voice search. It is pretty infuriating.
Notifications still seem to come through and I still get served cards but voice search fails almost all the time. When I initially went from Wifi to 4g it worked for one search and then back to disconnected. It doesn't seem to be a phone problem since people on here are using a number of different phones. This is a bug that needs to get fixed ASAP by Google.
I am disappointed but hopeful they can get this quickly fixed.
Click to expand...
Click to collapse
This is exactly everything I've noticed as well.. Seems to have gotten waaaaay worse after yesterday's update
Azarin said:
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
EDIT:
PS. It is worth noting that the watch does NOT display the disconnect icon when this happens (usually if you walk out of range you get a little cloud with a line through it)
Click to expand...
Click to collapse
Happens to me, too. Completely random though. Repairing the watch fixes it, but it is indeed annoying. We will have to wait for Google to fix this together with all the other bugs.
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
iHelp101 said:
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
Click to expand...
Click to collapse
Thanks, I'll give it a shot.
What about trying to reply using voice within a received Hangout or email? I'm always getting an error "Can't reach Google at the moment". Am I the only one? But if I select a default reply from the available list, I can reply with no problems...
iHelp101 said:
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
Click to expand...
Click to collapse
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
barkside said:
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
Click to expand...
Click to collapse
I found it only improves it a little, but it's not a full fix. Sometimes my watch works the whole day without connection problems and then suddenly multiple times in a short period of time.
I've read that the gear live has the same problem, so I guess it's android wear wide. Hopefully google is going to bring out an update soon which fixes all the annoying bugs.
barkside said:
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
Click to expand...
Click to collapse
Like stated by the previous post this is a simple fix. The only one that can truly fix the issue is Google. I have used this for a week and not had any issues relating to bluetooth disconnecting. One issue I noticed was Google Search sometimes breaks after using it multiple times in a short amount of time. I usually have to just force stop Google Search every 3 days also.
This has always been an issue I had even before Android Wear. If I used Google Now too much I couldn't get the "Okay Google" command to work. It seems this also happen when using wear too much. A simple force stop fixed it, but it is annoying when you want it to just work. Another thing I noticed was custom roms are having issues with Android Wear in my case.
Every time I use a custom rom on my Nexus 5 and try to use my LG G Watch I have constant disconnects and Google Search issues. Maybe Android Wear isn't playing nice with custom roms, but after using rooted stock for the last week I am experience very few issues compared to when using different custom roms. I noticed whenever I used a custom rom I got the "Connected, running sync loop". I have no idea if this causes the constant disconnects, but on stock with the simple "Connected" I have no issues.
I started out with the same problem using a Gear Live with a Sony Xperia Z1 Compact. The thing that fixed it for me was turning off battery saving mode on the phone - called stamina on the Xperia - that was turning off BT to save power. Now I rarely see the disconnected message.
Anyone found a solution to this problem?
My lg g watch also disconnects 90% of the time from my note 4. Anything from ok google to search or ser a reminder or or or
SIlvRav said:
Anyone found a solution to this problem?
My lg g watch also disconnects 90% of the time from my note 4. Anything from ok google to search or ser a reminder or or or
Click to expand...
Click to collapse
I have found this issue for Android Wear for my LG G watch R and Galaxy Note 3. If I use watchmaker, I have it set to vibrate twice upon disconnect and vibrate once upon connect. It is constantly disconnecting and immediately reconnecting (2 vibrations, followed immediately by a single vibration). This is extremely annoying and I see the same problem stated in the beginning, the voice search is constantly disconnected or cannot reach the server.
Cheers,
B.D.
Related
My S4 will not auto-connect to my Subaru Impreza 2013. It requires that I press the connection 4+ times for it to connect, even then it will randomly drop out. I've read where it is mentioned to ensure that the connect with all visible devices is checked (it is), but the way I read the option is that it should be visible to devices it has paired with regardless of whether that box is checked.
Another problem I have had is with navigation. Sometimes it will not reroute or if I leave the navigation app to look at a message, or answer a call it will start to crash the navigation. I have tried killing the app and restarting (super cool if there is traffic...) but it will continue to act oddly for several minutes.
I'm pretty sure the issue is with the S4, I exchanged my old S4 with another and continued to have the same problems, even though my Nexus4 had no issues.
Verizon SCH-I545
android 4.2.2
Any idea? (Sorry if bumps are uncool)
When I start up the omate it goes to the watch face. If I try to go into any launcher with wifi turned on the watch pops and then powers off suddenly. If I put it in airplane mode it will run fine. I can turn bluetooth on and it will continue to run. If I turn on wifi the watch shuts off.
I read another thread where turning off quickboot and then restarting the watch should help wifi/bluetooth behaviors. This did not help me. Has anyone else exprienced this or have a suggestion how to fix it?
My firmware is 20140120
I've had this watch less then 12 hours and can't even make it work well enough to try it out.
You received a defective watch. If you have already opened it, you might see something obvious wrong in the assembly, like maybe a mis-connected antenna, or more likely not.
Getting a replacement for your defective TrueSmart will take some time, if it turns out to be possible at all.
Sent from my Nexus 5 using Tapatalk
So it turns out it isn't wifi it is the Fleksy keyboard. I disabled Fleksy and was able to type in the Wifi password and connect.
Very odd issue for sure.
You mean when Fleksy is enabled, trying to enable WiFi shuts down your watch, but if you disable Fleksy then you can enable WiFi and your watch does shut down ?
I also had a horrible time trying to use Fleksey to enter my password. I gave up and connected a Bluetooth keyboard.
Sent from my Nexus 7 using Tapatalk
trent999 said:
You mean when Fleksy is enabled, trying to enable WiFi shuts down your watch, but if you disable Fleksy then you can enable WiFi and your watch does shut down ?
I also had a horrible time trying to use Fleksey to enter my password. I gave up and connected a Bluetooth keyboard.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That is what I meant.
Upon even further tinkering with Fleksy disabled I've found what I think to be the actual issue....
The speaker crashes the watch.
Fleksy made noise when I tried to type and crashed the watch.
Loaded Google Hangouts, got a message and the watch crashed.
Loaded Pandora, started a music station and the watch crashed
Set an alarm and when it went off the watch crashed.
Has anyone else seen this issue or read about it?
TCommander said:
That is what I meant.
Upon even further tinkering with Fleksy disabled I've found what I think to be the actual issue....
The speaker crashes the watch.
Fleksy made noise when I tried to type and crashed the watch.
Loaded Google Hangouts, got a message and the watch crashed.
Loaded Pandora, started a music station and the watch crashed
Set an alarm and when it went off the watch crashed.
Has anyone else seen this issue or read about it?
Click to expand...
Click to collapse
Sounds like you have a speaker wire grounding. ive tryed everything that you mentioed on my own ts and i can not replicate it.
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've noticed using Waze I'll see GPS go in and out, and occasionally I try to post pictures to Instagram and find out there's no GPS tagging in them. Anyone else seen this?
scottricketts said:
I've noticed using Waze I'll see GPS go in and out, and occasionally I try to post pictures to Instagram and find out there's no GPS tagging in them. Anyone else seen this?
Click to expand...
Click to collapse
YES! Install a GPS Test and you can actually see the amount of Satellites seen go to zero. I can sit in the same place for 5 minutes and it will go from 21 to 0 every 10 - 60 seconds with a clear sky. I am wondering if this is a software or hardware issue. It is noticeable when using Gmaps to navigate, you will see your arrow simply stop when driving down the highway for 5 seconds at a time.
btothec said:
YES! Install a GPS Test and you can actually see the amount of Satellites seen go to zero. I can sit in the same place for 5 minutes and it will go from 21 to 0 every 10 - 60 seconds with a clear sky. I am wondering if this is a software or hardware issue. It is noticeable when using Gmaps to navigate, you will see your arrow simply stop when driving down the highway for 5 seconds at a time.
Click to expand...
Click to collapse
Im sitting at my desk and watching it not get a fix. The location icon in the status bar never goes white, and the GPSTest just sits there not getting a fix. I've tried disabling the low power GPS option in settings with no luck.
btothec said:
YES! Install a GPS Test and you can actually see the amount of Satellites seen go to zero. I can sit in the same place for 5 minutes and it will go from 21 to 0 every 10 - 60 seconds with a clear sky. I am wondering if this is a software or hardware issue. It is noticeable when using Gmaps to navigate, you will see your arrow simply stop when driving down the highway for 5 seconds at a time.
Click to expand...
Click to collapse
Same here I've noticed on my t-mobile version.... Hmm...
---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------
scottricketts said:
Im sitting at my desk and watching it not get a fix. The location icon in the status bar never goes white, and the GPSTest just sits there not getting a fix. I've tried disabling the low power GPS option in settings with no luck.
Click to expand...
Click to collapse
Sometimes indoors GPS has more difficulty. Has it worked there before with other phones?
EDIT:
Worked with my GPS navigation a bit more... definitely see the GPS lose tracking every few minutes. Turned off the iZat, didn't make a difference. Plugged in a power source, thought it might help a little, but nope, GPS lost every once in a while. Bah, just when I thought I had received a problem-free unit
Any more information on this? As of April 1st, my LG G5 seems to be way off on GPS. I noticed it using Runkeeper. I thought maybe it was a Runkeeper issue, but then used MapMyRun and got the same I looked in history and saw that since getting this phone (traded in my G4 for the G5) I had one successfully tracked run, then it all went haywire. Never had a problem with the G4 - so it can't be signal issues (IMO). And since this phone got it right once... that is strange to me.
To give an idea... I ran about 10 miles and it told me 18. When I looked at the runkeeper map it looked like I was running down side streets, into fields, crazy stuff. Like it never got a real lock on my location.
I'm wondering if I need to return this phone??
bdogi said:
Any more information on this? As of April 1st, my LG G5 seems to be way off on GPS. I noticed it using Runkeeper. I thought maybe it was a Runkeeper issue, but then used MapMyRun and got the same I looked in history and saw that since getting this phone (traded in my G4 for the G5) I had one successfully tracked run, then it all went haywire. Never had a problem with the G4 - so it can't be signal issues (IMO). And since this phone got it right once... that is strange to me.
To give an idea... I ran about 10 miles and it told me 18. When I looked at the runkeeper map it looked like I was running down side streets, into fields, crazy stuff. Like it never got a real lock on my location.
I'm wondering if I need to return this phone??
Click to expand...
Click to collapse
I have only used the G5 in the car a few times and it seems to work fine - using google maps, not waze.
I use a couple apps to track biking and they work fine. However, when I use them I use an app called GPS keeper pro to keep the GPS running all the time. It seems to help with apps for fitness. I started using it with the G3 and just kept right on with the G5. You might want to try GPS Keeper for your running apps.
I use GPS only in the location settings. That may help. At least my apps that rely on GPS open much faster with that setting.
Sent from my LGLS992 using XDA Free mobile app
My specific GPS issue was that it would lose lock a minute or so into a perfectly normal navigation lock while using Gmaps. It would relock after several seconds, only to lose lock again. This repeated over and over.
I was using the app GPS Status to monitor this. However, it hasn't surfaced in a few days, so I don't know if there was some rogue app or former setting that was interfering with GPS holding lock. I've hypothesized maybe it was GPS Status itself which was interfering. I uninstalled and reinstalled it, and so far *knock on wood* it hasn't popped up again.
This sounds a bit different from some of the problems listed here. The run tracker not getting a good track might be related to this, if it is never able to consistently keep GPS lock. Try monitoring the GPS satellite lock icon when the app is running. Does it go from lock (white) to not lock (grey)?
Mine is actually grey most of the time but when I'm connected to wifi calling it's constantly white. Weird. This thing needs an update for a few different reasons. Coming from the note 4 I notice differences in the software obviously but somethings seem like they don't quite work right. Example being when I used wifi calling on the note 4 it would grey out the regular signal but on this it's still active with the bars going up and down. I'm pretty sure it should cancel the network out all together but maybe this is just different. I don't know.
Sent from my LGLS992 using XDA Free mobile app
Maybe it's using the wifi connection hotspot to determine your location? So does your GPS really work at all then?
waylo said:
Maybe it's using the wifi connection hotspot to determine your location? So does your GPS really work at all then?
Click to expand...
Click to collapse
Well I do have it set to GPS only in location settings but until I get out and try to use maps I guess I really won't know. It does find me in maps or other weather apps though.
Sent from my LGLS992 using XDA Free mobile app
Well - I got my second LG G5 hoping that would solve the problem. Doesn't seem to be any different
I've tried this so far:
High Accuracy - Was Already Set
Turn off WiFi location
Tried GPS Keeper to keep signal alive
Tried GPS Status Utility - NOTED: Takes a long time to lock and still will start 'searching' for long periods of time.
Tried with no cover on
New phone seems the same I love the LG phone itself, but I can't handle this. I should have returned it for a Samsung. Are there any other tricks I am missing?
bdogi said:
Well - I got my second LG G5 hoping that would solve the problem. Doesn't seem to be any different
I've tried this so far:
High Accuracy - Was Already Set
Turn off WiFi location
Tried GPS Keeper to keep signal alive
Tried GPS Status Utility - NOTED: Takes a long time to lock and still will start 'searching' for long periods of time.
Tried with no cover on
New phone seems the same I love the LG phone itself, but I can't handle this. I should have returned it for a Samsung. Are there any other tricks I am missing?
Click to expand...
Click to collapse
Do you perhaps have greenify on? I have a theory that the aggressive doze may be affecting GPS lock duration.
waylo said:
Do you perhaps have greenify on? I have a theory that the aggressive doze may be affecting GPS lock duration.
Click to expand...
Click to collapse
I don't think I have greenify loaded? I searched in Google Play and it only says 'install', so can't be on my phone.
bdogi said:
I don't think I have greenify loaded? I searched in Google Play and it only says 'install', so can't be on my phone.
Click to expand...
Click to collapse
Correct, you don't have it installed then. Have you tried disabling iZat? It's the low power GPS addition, at the bottom of the GPS settings page.
Also, just to cover all the bases, you are outdoors when you're searching for GPS, right?
I have a stock T-Mobile G5, I've also noticed inconsistent GPS. Acts as if it's stuck. I'll open Google Maps and it'll show my location from 90 minutes ago. Won't update until I turn on airplane and then off again. Once the radios come back up GPS updates. Hoping for an update to fix this ASAP.
waylo said:
Correct, you don't have it installed then. Have you tried disabling iZat? It's the low power GPS addition, at the bottom of the GPS settings page.
Also, just to cover all the bases, you are outdoors when you're searching for GPS, right?
Click to expand...
Click to collapse
The low power GPS is turned off, yes. When I run the test I am running it right next to my window indoors. I run it on my HTC One (not activated) and my LG G5 (activated - new phone). HTC locks immediately (2-5 seconds) with 14/20 satellites, G5 does not lock for at least 3 minutse with anywhere between 18-26 satellites (I gave up after 3 minutes). I tried turning off/on airplane mode like the previous post - didn't change anything for me.
Even though the GPS doesn't show lock on the LG G5, I can get google maps working. It isn't very accurate, though. It sometimes shows me stuck in a location for about 1-2 miles. It also shows me off the roads, typically.
I found a way to replicate the GPS issue! I was having it behaving really intermittently on my car mount (vertically), and then I decided to tilt it horizontal and suddenly it got a lock! I've verified it by GPS test apps and it's super obvious that in a vertical orientation, the GPS doesn't get a proper lock.
Any of you guys wanna validate this?
I'm having this issue as well, sometimes takes a couple minutes or more to obtain initial lock when I get in my car every morning and start Waze (although it guesstimates my location based on last lock / WiFi), plus then it drops out 2-3 times per drive, which is incredibly frustrating and has caused me to miss turns. I lose lock with WiFi both enabled and disabled during my drive
As a couple people already said, I use the T-Mobile G5. I'm curious if all of us experiencing the problem use the T-Mobile version and it might be a carrier ROM issue. My network and GPS settings are how they were out of the box, although now that I know it exists, I'll try disabling IZat low-power location just to see if there's any improvement.
hot_wired13 said:
I found a way to replicate the GPS issue! I was having it behaving really intermittently on my car mount (vertically), and then I decided to tilt it horizontal and suddenly it got a lock! I've verified it by GPS test apps and it's super obvious that in a vertical orientation, the GPS doesn't get a proper lock.
Click to expand...
Click to collapse
My phone is always horizontal in my car dock, with the top of the phone facing left, but I'm still losing GPS lock. Do you use yours horizontally the other way?
I can tilt mine any way I want and it won't lock I ran a test this morning while taking my kids to school. I took out my old HTC One and turned on Runkeeper (running app). Turned Runkeeper on LG G5 (separate Runkeeper account to be sure nothing got screwy). G5 couldn't lock enough to map anything, HTC mapped perfectly to the roads. I then used VZ Navigator (Verizons map system - this was done at Verizon's request). The maps trailed me by about 1/2 to 1/4 mile and showed me about 200 yards off the road. Then - GPS lost. All the while - HTC mapped me out with Runkeeper perfectly mapped to the roads.
Since this is my second LG G5 with GPS issues... I think there is a problem with the phone or maybe the Verizon version of the phone. Sounds like T-Mobile also, though, so could just be some LG software screwing things up.
Either way - I'm probably getting the S7 now. I really like the G5 with the rear fingerprint scanner... but I need a GPS that works out of the box.
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.