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 ?
Related
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.
Hi!
I am not getting any notifications pushed to my G Watch any more.
Usually, the watch vibrates and shows a notification card when e.g. I receive a new mail (K-9) or a new Threema message. However, it has stopped now. I still see new messages on my mobile, but my watch just seems to ignore them completely.
The watch is connected to the mobile (there is no crossed out "cloud" symbol on the display) and I also still receive calendar schedules on my watch.
I have browsed through all the settings, but I cannot find anything that seems to be configured wrong.
Any ideas?
Thanks!
shredzone said:
Hi!
I am not getting any notifications pushed to my G Watch any more.
Usually, the watch vibrates and shows a notification card when e.g. I receive a new mail (K-9) or a new Threema message. However, it has stopped now. I still see new messages on my mobile, but my watch just seems to ignore them completely.
The watch is connected to the mobile (there is no crossed out "cloud" symbol on the display) and I also still receive calendar schedules on my watch.
I have browsed through all the settings, but I cannot find anything that seems to be configured wrong.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Did you mute the watch on accident? Swipe down from the top of the screen on the watch and if you see a bell with a line through it the watch is muted which means no notifications will be shown or buzzed.
mapatton82 said:
Did you mute the watch on accident? Swipe down from the top of the screen on the watch and if you see a bell with a line through it the watch is muted which means no notifications will be shown or buzzed.
Click to expand...
Click to collapse
I have already checked that the watch is unmuted. It also does vibrate, e.g. on incoming calls.
It's just that notifications from the notification bar do not appear on the watch any more. I also checked the "Security" - "Notification Access" (roughly translated from German, I hope you know what I mean) configuration on the mobile and verified that the "Android Wear" app is enabled.
shredzone said:
I have already checked that the watch is unmuted. It also does vibrate, e.g. on incoming calls.
It's just that notifications from the notification bar do not appear on the watch any more. I also checked the "Security" - "Notification Access" (roughly translated from German, I hope you know what I mean) configuration on the mobile and verified that the "Android Wear" app is enabled.
Click to expand...
Click to collapse
Repair with blutooth.... Restart it...and last reset.
Sent from my LG-D850 using XDA Free mobile app
blaker13 said:
Repair with blutooth.... Restart it...and last reset.
Click to expand...
Click to collapse
I removed the bluetooth pairing, deinstalled all Wear related apps, made a factory reset on the watch, started from the very beginning. And still... No notifications.
I hate my G Watch... :crying:
I feel like an idiot... :silly: I have tried everything on my watch. However, after restarting my Nexus 5, notifications are shown on the watch again.
I have my watch connected to my LG G3 (marshmallow) and can receive notifications from pretty much everything, however I do not get a notification on who is calling. I get a voicemail notification and missed call notification, but is it possible to get a notification on who is actively calling my phone on my watch? I installed LG Call for Android Wear app, but I can't figure out what that app even did. Any suggestions? Thanks!
When you installed Android Wear and paired your smartwatch on Marshmallow, did you grant it access to contacts? Looks like a permission issue.
LG Call app doesn't work with G Watch (W100), it's supposed to start calls using the watch (dial), you can use other apps to do the same.
PS: be aware that if you unpair your watch you will need to reset it and sync from the beginning.
lfom said:
When you installed Android Wear and paired your smartwatch on Marshmallow, did you grant it access to contacts? Looks like a permission issue.
LG Call app doesn't work with G Watch (W100), it's supposed to start calls using the watch (dial), you can use other apps to do the same.
PS: be aware that you unpair your watch you will need to reset it and sync from the beginning.
Click to expand...
Click to collapse
Thanks! I unpaired and started over...it works now! It brings much more functionality to the watch!
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...
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.