Notifications out of sync from time to time - LG G Watch

My LG G Watch keep having some out of sync notifications from time to time with my Nexus 5.
For example if I have cleared the Hangouts notification on my phone, it will still show on my phone.
Have you guys ever experienced this? Since to be happening only recently.
I tried factory resetting the watch, still the same.

Using LG G3, I see that, sometimes, notifications stays few seconds, but not more (sync issue?).

Related

[Q] Push notifications and chat delay

Hi!
I have a few very annoying problems I want to get rid of.
The first is that all sorts of push notifications are often (if not always) very delayed. For example, when someone's played Wordfeud and it's my turn it can take up to 20 minutes before the phone alerts me. Same thing with Whatsapp and other apps. I did a factory reset recently and the problem seemed solved but after just a few hours the delays began to appear again. Both with 3G and Wi Fi.
It is the same thing with the built in FB-chat. Sometimes messages are also delayed for up to an hour. Occationally when I enter the Message hub and swipes to Online tab the messages arrives but it's rare. It could at first appear as work when two or maximum three messages arrives but then the conversation just dies and I must go to the Facebook app to view and continue the chat. Also after the factory reset it worked somewhat fine but just like with Push notifications it didn't work long enough... Same here, both over 3G and Wi Fi.
Does anyone have a single clue of what the issue is here?
Is the phone checking for new notifications in a certain pattern, like every 30 minutes?
I'm not completely sure if this is the right forum for this but I'm beginning to be kind of desperate. Notifications on iOS and Android works like a charm and I don't think the Lumia with WP should be behind in this matter.
Extremly thankful for answers.
Regards
Mikael Ivarsson
Nokia Lumia 800
OS version: 7.10.8773.98
Zune: Latest available
its not a problem of software, its a wanted feature of microsoft, wp7 doesnt have any multitastking, so if you turn of wifi and whatsapp is running, wifi is turned off for some minutes and if you turn on screen, wifi connects and whatsapp gets your messages, thats what i realized..
next phone wont be wp. :/ nice OS but the little things like this are annoying
facekill1337 said:
its not a problem of software, its a wanted feature of microsoft, wp7 doesnt have any multitastking, so if you turn of wifi and whatsapp is running, wifi is turned off for some minutes and if you turn on screen, wifi connects and whatsapp gets your messages, thats what i realized..
next phone wont be wp. :/ nice OS but the little things like this are annoying
Click to expand...
Click to collapse
Thanks for the reply!
But that's the strange thing, even if i don't turn off the screen and keep the phone "awake" there are no toast. The push notifications were instant for a few hours after the factory reset so there must be something that is "blocking" push messages. Same thing with the fb-chat. The chat should also work without problems even when the screen is turned off.
Me too are also considering walking out of Microsoft on this one. The OS is very beautiful and everything is so thought through but they still have som work to do.
Yes, background agents run every 30 minutes
thats why i wont buy a wp phone anymore. its really annoying and not SMARTphone like!
But shouldn't push messages be pushed through nearly instant?
it should be popup in the second it arrives
Exactly. Even if the screen is unlocked and wifi 3G is connected and all that it still is a delay.
The problem seem to have solved itself! I don't know what I've done but one morning I woke up and everything worked smoothly. Let's hope the issue doesn't return!
Data connection should be enabled for Push notifications to work. Maybe you went above your data cap or sometimes the 3G reception got lost.
Also, are you sure that app uses Push notifications and not regular Toasts sent by a background agent ?

[Help]Issues after sideloading 1.4 update.

I updated my G watch to 1.4 by sideloading the update which I downloaded from xda thread itself. After the update I'm not getting any incoming call notifications.
Also when I go to Android Wear app-> try out watch notifications, there is no
Option for phone call.
Today I tried installing some wear apps and now even those aren't getting synced on watch, I'm getting rest all the notifications, I tried factory resetting as well.
Any help?
The LG G watch does not have a speaker and so google did not add the calling shortcuts to the g watch or any other android wear device without a speaker. Did you check if it was a problem phone side maybe like uninstalling android wear app?
Well I'm getting the notifications now
Xmaster24 said:
The LG G watch does not have a speaker and so google did not add the calling shortcuts to the g watch or any other android wear device without a speaker. Did you check if it was a problem phone side maybe like uninstalling android wear app?
Click to expand...
Click to collapse
I just tried formating my watch twice i guess, now I'm getting the notification but the
Problem is it's way to laggy , the watch just vibrates and before the caller screen appears the call is already disconnected. Anyone else facing this issue ?

[Bug?] Stratos can't connect to the iOS app, but receives messenger notifications.

I have tried to factory reset the watch many times, and everytime it will fix it, but after a few days, same issue persists.
Sometimes it will receive app notifications, sometimes it can't even do that.
**Right now it shows in my bluetooth settings that the watch is connected(probly why Im getting notifications) . But again, no connection in app**.
Very frustrating as I won't be able to view any of my stats on the app at all.
Anyone else experiencing this?
Since no one replied...
UPDATE:
I gave up on the iOS app, seems like it's just a persisting problem right now.
I managed to not lose any data by enabling the hidden app list, and paired my watch with my Samsung phone instead. So I didn't have to factory reset it.
And the Android app so far is working much better. i.e. Custom watch faces actually shows up in the app.
Make sure you have latest firmware on watch and Amazfit app on phone. Pair them properly or you may have problems with your activity data in the future (see thread about sync FAQ). If you still have issues, re-install Amazfit and enable the "Away alert" in watch Settings, it seems to make connection much more stable for me...

Notifications late or not showing on wifi connection

Hello everyone,
I've been having this issue for several months now where all my social apps like messenger, instagram, whatsapp, flock, gmail and so on won't show notifications when my phone is connected to any type of wifi.
The notifications are late, or they show up when i open the app. Sometimes they repeat themselves even after i checked, like something is blocking them till some point.
I tried SO MANY things to fix this (factory reset, disable device care and any battery saving settings, reinstalled apps,...) and ended up using 4g all the time as the most solid one for the time being.
It's just very frustrating that something as simple is this is not getting fixed for a long time now.
Does anyone have similar issues? Or maybe even a fix for this? I noticed this happening to other people around me using different samsung devices.
I don't know if this is a samsung related issue or something else.
Thanks!

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