Related
all notification are working except for call.
when my phone (Xperia Z2) receives call, watch didn't show a thing, just shows the clock.
any idea how to solve this issue?
I tried restart n factory reset but still can't solve
anyone can help?
The watch won't show anything if it's in the cinema mode and a phone comes in.
Sent from my LG-H815 using XDA Free mobile app
Are you receiving a call using default phone, this should work, or with third party app like WhatsApp or Hangouts? These don't ring, very annoying...
yes, by default phone
but if the other party end the call, it did shows missed call
funny thing is I connect the watch to my redmi 2, worked flawlessly
What watch apps do you have installed?
Few years later... topic digging !
Here's a fix I found, for the future people who will find this topic :
To fix the incoming call popup window not showing on your watch :
Go to settings (on your phone) / apps / Android Wear / Permissions / Phone !
Should work now.
Is anyone else having a delay in phone notification? By the time my watch starts vibrating to notify me of a phonecall I have already missed the call on my phone. That's irritating. One of the reasons I got the watch was to let me know when my phone starts ringing. My emails and texts seem to be notifying me just fine. It's just the phone notification.
Ideas?
I have only a small delay like 0,5s. So I think this is not normal. Are you connected by bluetooth or maybe by wifi?
I'm connected by BT. Like i mentioned all of my other notifications are working just fine. It's just the phone notification. I wiped my watch and reloaded everything so i am waiting to see if that fixed anything.
zumstin said:
I'm connected by BT. Like i mentioned all of my other notifications are working just fine. It's just the phone notification. I wiped my watch and reloaded everything so i am waiting to see if that fixed anything.
Click to expand...
Click to collapse
Update: It did not work. Sigh...
zumstin said:
Is anyone else having a delay in phone notification? By the time my watch starts vibrating to notify me of a phonecall I have already missed the call on my phone. That's irritating. One of the reasons I got the watch was to let me know when my phone starts ringing. My emails and texts seem to be notifying me just fine. It's just the phone notification.
Ideas?
Click to expand...
Click to collapse
I have this at times, though not always. I also get it where after I answer the call it continues to vibrate on my watch. hangouts messages do take a few seconds to push to the watch though. that said, this behavior has been consistent with my zenwatch, smartwatch 3 and my hwatch so I think it's just inherent in the platform
kellybrf said:
I have this at times, though not always. I also get it where after I answer the call it continues to vibrate on my watch. hangouts messages do take a few seconds to push to the watch though. that said, this behavior has been consistent with my zenwatch, smartwatch 3 and my hwatch so I think it's just inherent in the platform
Click to expand...
Click to collapse
Same here.
I just tested a call and it was about .5 to 1.0 seconds which is considered very good by my taste. But I did notice SMS and Hangouts does take a few seconds.
Maybe they set the priority like that on purpose.
Same problem for me...
zumstin said:
Is anyone else having a delay in phone notification? By the time my watch starts vibrating to notify me of a phonecall I have already missed the call on my phone. That's irritating. One of the reasons I got the watch was to let me know when my phone starts ringing. My emails and texts seem to be notifying me just fine. It's just the phone notification.
Ideas?
Click to expand...
Click to collapse
I am experiencing the same exact problem with my Nexus 6P - no amount of resetting seems to have fixed the problem. This has been extremely frustrating.
Anyone else figure this out without having to warranty the watch. Mine is a good 3 seconds behind with a Nexus 6. The call can go to voicemail before the watch vibrates.
uniqueflips said:
Anyone else figure this out without having to warranty the watch. Mine is a good 3 seconds behind with a Nexus 6. The call can go to voicemail before the watch vibrates.
Click to expand...
Click to collapse
I'm hoping with the new update to Wear announced today that it will fix the delay. Hoping....
uniqueflips said:
Anyone else figure this out without having to warranty the watch. Mine is a good 3 seconds behind with a Nexus 6. The call can go to voicemail before the watch vibrates.
Click to expand...
Click to collapse
it has nothing to do with the watch, I've got a sw3 as well that behaves the same with my 6p. previously I had a zenwatch, and it had the same delay with my n6 and later the 6p
I believe it's the android wear app itself. If you can find the AW 1.3 apk from apkmirror or the like, you should see a difference. Hopefully the new OS update will help alleviate the issue.
Same here with HW Watch Active. Phone get instant Message since Doze Settings on Marshmallow were edited, Watch still delayed...
I am having problems as well. Sometimes I would get notifications on my watch, other times the notifications would be delayed. I just tried and I am not even getting calls to my watch. I had to perform a factory restart twice now in order to get it to work. Why is that? I have a Huawei watch sync with a Huawei Mate 9. I would figure they both should work seamlessly.
any advice would be appreciated
rimz808 said:
I am having problems as well. Sometimes I would get notifications on my watch, other times the notifications would be delayed. I just tried and I am not even getting calls to my watch. I had to perform a factory restart twice now in order to get it to work. Why is that? I have a Huawei watch sync with a Huawei Mate 9. I would figure they both should work seamlessly.
any advice would be appreciated
Click to expand...
Click to collapse
Did you find a solution? I am experiencing the same issue, the incoming calls are not working and I also cant therefore receive calls directly on the watch. I am using an updated Huawei Watch with the HTC One M8, which is also updated to Android 6.0, with the latest version of Android Wear.
Cheers
Badelhas said:
Did you find a solution? I am experiencing the same issue, the incoming calls are not working and I also cant therefore receive calls directly on the watch. I am using an updated Huawei Watch with the HTC One M8, which is also updated to Android 6.0, with the latest version of Android Wear.
Cheers
Click to expand...
Click to collapse
The incoming calls seem to have fixed itself. However, what really solved the issue was that I had to make sure, on my Huawei phone, Android wear was set to close after the screen lock. I made sure that Android wear was always running in the background. Not sure if there is a similar setting on the HTC One M8, but making sure android wear was not in any power saving mode solved the problem for me.
Hope it help,
rimz808 said:
The incoming calls seem to have fixed itself. However, what really solved the issue was that I had to make sure, on my Huawei phone, Android wear was set to close after the screen lock. I made sure that Android wear was always running in the background. Not sure if there is a similar setting on the HTC One M8, but making sure android wear was not in any power saving mode solved the problem for me.
Hope it help,
Click to expand...
Click to collapse
I fixed the issue with a "wipe partition cache" procedure. Thanks
I'm using Samsung Galaxy S6 paired with Huwei watch. The notifications for all apps (messenger, whatsapp, inbox, etc.) do not show up on the watch. Only calls show up on the watch. The voice command (ok google) works also fine. So the connection is good and stable. None of the apps are blocked. If I do factory reset everything works fine, but only for a couple of days. Then I have the same problem again. Does somebody know what is going wrong and what I can do to fix it? Thanks in advance!
Do you have an app installed, that interferes with notifications, e.g. "Do not disturb"-apps, that enable and disable notifications under certain conditions?
This behavior is not a common problem (at least none of which I've heard of or experiencing myself), so I assume it has something to do with configuration/apps on your phone.
Another thought: Maybe you are using an app that causes a problem with the notification system on the watch (e.g. due to a software bug). So maybe this app somehow breaks the notification queue after it is received by the watch.
Maybe this app will notify only every couple of days and after it does you're not signaled any further notifications.
So just think of the apps you have installed. Which apps are not very common and do not notify every day? Block the notification to the watch of this app(s) and see if the problem still occurs.
I am using only the build in "do not disturb" function at night. Other than that no apps have a do not disturb function enabled. I will try to block various apps as you proposed. I'll start with clean master. There is a function on Samsung Galaxy S6 that allows to switch on notification access for various apps. It was off for huawei wear but on for andorid wear. Although I'm not using huawei wear this might have caused the problem. I have switched it on! Let's see if it helps! Thanks!
I can switch back to my S6 if you cant find out. Just post and let me know. I havent used it in a while.
Thanks guys, but I figured it out. Allowing huawei wear to access the notifications solved the issue!
How did you do? I mean how can I allow Huawei Wear to access notifications?
Thank you, I have the same problem...
scrissi said:
How did you do? I mean how can I allow Huawei Wear to access notifications?
Thank you, I have the same problem...
Click to expand...
Click to collapse
You have to allow the Notification from the phone. I think it varies depending on your Android version. For me it's Settings- Notifications- Notification Access- then allow whatever you want to get i.e. Android Wear, Huawei Wear, etc.
So, I've sideloaded Android Wear 1.4 to my Huawei Watch and it's been working well so far!
In my phone's bluetooth settings, I've configured it to "use the watch for phone audio", so that I can answer calls through the watch.
Today, however, I noticed something annoying: when I use my phone to make calls, the proximity sensor is no longer activated (the screen remains on during the phone call). Did anyone notice the same problem? Any workarounds?
I'm not sure this is relevant, but my phone is an HTC One M8 running Android 6.0 (Google Play Edition).
Thanks!
tiagobt said:
So, I've sideloaded Android Wear 1.4 to my Huawei Watch and it's been working well so far!
In my phone's bluetooth settings, I've configured it to "use the watch for phone audio", so that I can answer calls through the watch.
Today, however, I noticed something annoying: when I use my phone to make calls, the proximity sensor is no longer activated (the screen remains on during the phone call). Did anyone notice the same problem? Any workarounds?
I'm not sure this is relevant, but my phone is an HTC One M8 running Android 6.0 (Google Play Edition).
Thanks!
Click to expand...
Click to collapse
Same here, except that I'm on a Moto X Pure 2015.
What I've just ended up doing is after dialing/answering a call, I press the power button to turn the screen off, and turn it back on to end it.
The same here. Another alternative is to manually choose "Earpiece" within in-call screen. This activates prox sensor again.
This should be considered a bug and I believe Google will make necessary adjustments in the Dialer app in this regard.
Thanks for the help, guys! The workarounds you provided do work. However, the bug is still very annoying. I've reported the bug in the AOSP issue tracker:
https://code.google.com/p/android/issues/detail?id=202776
tiagobt said:
Thanks for the help, guys! The workarounds you provided do work. However, the bug is still very annoying. I've reported the bug in the AOSP issue tracker:
https://code.google.com/p/android/issues/detail?id=202776
Click to expand...
Click to collapse
Thanks for taking care of creating an issue. I added my vote and comment.
Just voted as well...Nexus6P
This issue does not seem to present in my Samsung Galaxy S6 ... the proximity sensor works as intended during phone calls from phone.
The phone screen does not dim when the call is actually running on the watch , however the proximity sensor works as expected and dims the screens if the call is placed from the phone or transferred back to the phone from the watch......Perhaps this issue is Device specific or present in the stock versions of Android OS
Most likely related to Google's Dialer app and InCallUI app
Samsung delivers its own modified Dialer so it is possible they took care of that issue themselves.
Added new comment. Quoting.
Issue seems to be fixed after updating my Nexus 5X to MHC19J. Well, almost. Handset earpiece is forced as soon as call is connected resulting in proximity sensor being active, which is OK for handling incoming calls. Issue is with outgoing calls as when dialing, I have to wait for call to be connected before proximity sensor kicks in. Proximity sensor should kick in as soon as dialing starts, before call is connected.
Click to expand...
Click to collapse
nomad032 said:
This issue does not seem to present in my Samsung Galaxy S6 ... the proximity sensor works as intended during phone calls from phone.
Click to expand...
Click to collapse
Works also fine for my Samsung Note 4.
tiagobt said:
So, I've sideloaded Android Wear 1.4 to my Huawei Watch and it's been working well so far!
In my phone's bluetooth settings, I've configured it to "use the watch for phone audio", so that I can answer calls through the watch.
Today, however, I noticed something annoying: when I use my phone to make calls, the proximity sensor is no longer activated (the screen remains on during the phone call). Did anyone notice the same problem? Any workarounds?
I'm not sure this is relevant, but my phone is an HTC One M8 running Android 6.0 (Google Play Edition).
Thanks!
Click to expand...
Click to collapse
Same here! Huawei watch and Droid Maxx 2 running Marshmallow. I thought it was Android Wear until I stumbled upon this post. This so negatively impacts the user experience that I'm considering returning the watch.
For the last week or so I've noticed that when I get a text, I get the preview pop up of the text, and then it disappears - along with the notification of the text. It will either disappear immediately or soon after. Sometimes if I have multiple text notifications - and I touch one - the rest will disappear. It also removes the 'unread' badge count on my Nova Launcher bar. This has never happened before, and I'm unsure what could be happening now to cause it. I normally use Textra, but I switched to Android Messages to see if it was an app error but the same thing continued.
I was aware of the Oreo issue where text messages weren't being received, but I'm definitely receiving them. I'm on a Pixel 2 XL now, but this was happening with my Pixel XL last week also. I've tried turning off the battery optimization in case it was acting funky, but that hasn't changed anything. Any ideas?
I am having the same issue. I'm on a Verizon Pixel 2 XL. I get a text, the notification starts to play and then cuts off, not showing an unread notification. I'm getting the text, if I go into Textra it shows the new message, its just marked as read.
Coincidentally, I'm also having an occasional issue where my screen won't wake up and I have to reboot the phone to get the screen to turn back on. Haven't seen anyone having that issue yet either.
I have noticed the same thing on my Nexus 6. I haven't noticed an update to the messages app that corresponds to when this started, but the android wear app updated around the same time, so I was curious if it had something to do with that.
---------- Post added at 09:02 AM ---------- Previous post was at 08:48 AM ----------
I just uninstalled the wear app and my notifications don't disappear any more. Unfortunately, I can't use my watch now
Messages notifications are disappearing on my Pixel 2 (non-XL) also. Sometimes they disappear so quickly that I don't even get the partial sound, just a short vibration from the phone.
I also have a Wear device. Haven't tried removing the Wear app, because all other notifications are working correctly, and I depend on them much more than the occasional text I receive these days.
I'm getting this on my Galaxy S8 as well; I was finally able to track this back to the Android Wear app, but as I haven't told it to silence notifications on my phone when connected to my watch, I'm not sure exactly what is causing this bug...
Sent from my Galaxy S8 using XDA Labs
benmeroff said:
I'm getting this on my Galaxy S8 as well; I was finally able to track this back to the Android Wear app, but as I haven't told it to silence notifications on my phone when connected to my watch, I'm not sure exactly what is causing this bug...
Sent from my Galaxy S8 using XDA Labs
Click to expand...
Click to collapse
I just noticed that I'm having this problem as well after a few people asked me why I hadn't responded to their texts. I'm sure this used to work fine. Maybe it was broken in a recent update of messages?
Good catch tracking it to Wear. I have figured out the following:
If the watch is on, the text notification gets "eaten up" by the watch and does not show on the phone
If the watch is off, the notification does remain on the phone
If the watch is on but I set it to ignore the "Messages" app notifications, the message shows on the phone
This is pretty annoying as I do like getting notifications on the watch, but of course I don't want them to disappear from the phone. It seems like for the moment, I have to choose between one device or the other.
I opened a bug report at https://issuetracker.google.com/issues/70808796
So I actually think I may have figured out what's happening on my end but still don't know exactly why... I had AT&T NumberSync enabled for my LG Watch Urbane 2nd Edition, and after disabling that all my text notifications persist like they used to; basically my watch now functions tethered to my phone through a traditional Android Wear connection and will only get notifications once "passed on" from my phone, versus catching the texts via the AT&T network directly with NumberSync.
Sent from my Galaxy S8 using XDA Labs
I have the issue on Nexus 6 and Android wear also. Any solutions to keep both going?
In the Wear app on the phone check to see if "Silence phone while wearing watch" is enabled.
benmeroff said:
So I actually think I may have figured out what's happening on my end but still don't know exactly why... I had AT&T NumberSync enabled for my LG Watch Urbane 2nd Edition, and after disabling that all my text notifications persist like they used to; basically my watch now functions tethered to my phone through a traditional Android Wear connection and will only get notifications once "passed on" from my phone, versus catching the texts via the AT&T network directly with NumberSync.
Sent from my Galaxy S8 using XDA Labs
Click to expand...
Click to collapse
You are a genius! Thanks. This solved my problem (although I think the underlying issue might be different since you are on AT&T).
The winning combo for me (I'm using T-Mobile with "DIGITS with Paired Data") is:
On the watch, settings --> connectivity --> cellular --> advanced --> watch shares number with phone --> calls: on, text messages: off
On the watch, settings --> apps & notifications --> app notifications --> show all --> messages --> off
Since TMo already handles having the watch SIM share my main SIM's number on the network side, there's no need to tell the watch about this. I've confirmed that the following work:
Incoming texts appear (and stay in the notifications) on the phone and watch
I can reply to texts from either device and the "from" number is correct (my main number)
I do not get duplicate notifications on the watch (the watch's messages app's notifications are disabled)
I can place a call from the watch and the correct "from" number appears on caller ID
I can receive a call placed to my main number on either the phone or the watch