Is anyone else having this issue? The device fails to receive notifications from Gmail, Twitter, Snapchat, etc. until I turn on the screen and unlock the phone. I'm currently connected to Wifi. There's a lot of crap apps that I disabled, so maybe that could be the culprit? Perhaps I disabled a necessary one on accident? Maybe there's a bloatware app that's disabling my Wifi? I haven't changed any Wifi settings and I don't see any noticeable culprit in the settings menu. Either way, here's the list of my disabled apps.
ATT FamilyMap
ATT Hot Spots
ATT Live
ATT Locker
ATT Mail
ATTMobile Locate
ATT Navigator
ATT Ready2Go
ATT Smart Wifi
BlurbCheckout
Caller Name ID
Device Help
Drive Mode
Facebook
Famingo
Flipboard
GALAXY Apps
Games
Google Play Books
Google+
Hancom Office 2014
HP Print Service Plugin
Keeper
Live weather
Lookout
Milk
Mobile TV
PEN.UP
Samsung Account
Samsung Billing
Samsung Galaxy
Samsung GALAXY Apps Widget
Smart Remote
Uber
Wallet (ISIS)
YP
Any help would be appreciated, thanks!
When you say not receiving, is it not notifying you until you wake it up, or is the notification icon there, it just doesn't play a sound?
chadderbox said:
When you say not receiving, is it not notifying you until you wake it up, or is the notification icon there, it just doesn't play a sound?
Click to expand...
Click to collapse
It's legitimately not receiving any notifications after until I wake it up.
I give up.
I've tried everything at this point. I reset the phone twice. I monitored it on both Wifi and Cellular data. I monitored as many stock apps as I could. Something is stopping the damn phone from receiving data while it's asleep and I have no clue what the hell it is. I've scoured the settings menu countless times as well. Seeing how there's no replies, I'm just assuming that I'm the only person with this issue. I might have to just exchange the phone because I'm starting to believe that it's a hardware problem. Doesn't seem like it really, but damn this is annoying.
seoulstyle said:
I've tried everything at this point. I reset the phone twice. I monitored it on both Wifi and Cellular data. I monitored as many stock apps as I could. Something is stopping the damn phone from receiving data while it's asleep and I have no clue what the hell it is. I've scoured the settings menu countless times as well. Seeing how there's no replies, I'm just assuming that I'm the only person with this issue. I might have to just exchange the phone because I'm starting to believe that it's a hardware problem. Doesn't seem like it really, but damn this is annoying.
Click to expand...
Click to collapse
Have the same problem. Chatted with 2 people at Samsung, both useless.
The first person told me that "you will receive only notifications for text messages and call logs on the lock screen". I told her there should be a tiny icon near carrier name...
The 2nd person suggested I contact AT&T.
Like to know if anyone has more info regarding this issue.
possible solution
I have experienced same issue particularly with hangouts for me. From the brief searching I did about this I found it seems a common issue with Android lately and also saw an app suggested called pnf--push notification fixer. I have tried it and seems to do the trick. Something you may find helpful. Root and non root versions in play store.
Google was down this morning. Hangouts, and gmail wetter effected. It should be back up and working now. You may have also experienced they Google Play Services crashing.
Sent from my SHIELD Tablet using XDA Free mobile app
Been having some issues with android wear and my nexus since MM came out. got a different set of problems with N. originally had a bluetooth issue with MM, N seems to have fixed that. I now no longer receive texts or emails on my watch. I sometimes get a vibrate but nothing will show up on screen. I still get navigation and google now reminders. Ive also noticed the messenger app is missing on the watch; it used to be there. i can still send out texts fine via the watch but no receiving. I also don't see any calls come on screen most of the time. If I do see a call Ive already missed it when the watch starts.
Nexus 5X - N Beta 3
Huawei Watch - 6.0.1
Factory reset watch, factory reset phone, re-paired watch to phone. redownloaded apps, turned off doze for blutooth share and other blutooth processes, turned doze for phone app, sms app, android wear, contacts, call management, device manager, mms service, phone service, phone and messaging storage.
Hi all!
I do not recieve any Messages on my Huawei Watch (neither WhatsApp, nor SMS or Telegram) from my HTC One M7 (rooted). Calendar notifications and phone calls are working without any problems.
I realized that problem since i did a full wipe and reinstalled VipeOne 9.0 ROM.
This steps also did not help and i did a reset and new pairing multiple times without any success.
Could there be any settings which are set wrong?
How can i detect and solve this problem to get my notifications back?
Because i do not know if the problem is Android or Android Wear related or has something to do with the Huawei Watch or ViperOne ROM, i did a post in this Forum...
Thank you for helping in advance,
Florian
it could be related to this sort of thing http://forum.xda-developers.com/huawei-watch/general/bad-battery-life-read-factory-reset-t3474948
go to apkmirror.com and download the latest version of Google Play Services for your phone then double reboot phone and watch twice (could take a day for Google play services on watch AND phone to sync their versions)
since you wiped your rom I'd bet your version of Google Play Services is out of sync with what's on the watch (probably would fix itself after a week off trickling the updates)
pablo71 said:
it could be related to this sort of thing http://forum.xda-developers.com/huawei-watch/general/bad-battery-life-read-factory-reset-t3474948
go to apkmirror.com and download the latest version of Google Play Services for your phone then double reboot phone and watch twice (could take a day for Google play services on watch AND phone to sync their versions)
since you wiped your rom I'd bet your version of Google Play Services is out of sync with what's on the watch (probably would fix itself after a week off trickling the updates)
Click to expand...
Click to collapse
Hi pablo71,
thank you for your answer.
I downloaded the newest Google Play Services apk from apkmirror.com, installed it and restartet Watch and Phone multiple times.
But after over 24h there is still the same problem...
What can i do? Reset the phone another time or sync Google Play Services manually or something else?
htcdesire-hd said:
Hi pablo71,
thank you for your answer.
I downloaded the newest Google Play Services apk from apkmirror.com, installed it and restartet Watch and Phone multiple times.
But after over 24h there is still the same problem...
What can i do? Reset the phone another time or sync Google Play Services manually or something else?
Click to expand...
Click to collapse
my apologies for late reply ... I don't know what could be done, but if your watch was rooted I'd say to install the app Advanced Settings, then open it ON THE WATCH and go to Apps > System > Google Play Services > CLEAR DATA ... THEN go to Android Wear on the phone and FORGET THE WATCH ... THEN Reboot the watch, open Advanced Settings on watch go to Bluetooth > check the Discovery Mode Box and RE-PAIR the watch with Android Wear .. when I have the problem 'that sounds like what you're describing' this procedure fixes it for me.
sorry you're having problems with your watch .. if it's because of data-cross-contamination between different versions of Google Play Services updates that is causing this then I hope Google takes some action and stops doing this ... non-functioning watches does NOT make people want to buy smartwatches
pablo71 said:
my apologies for late reply ... I don't know what could be done, but if your watch was rooted I'd say to install the app Advanced Settings, then open it ON THE WATCH and go to Apps > System > Google Play Services > CLEAR DATA ... THEN go to Android Wear on the phone and FORGET THE WATCH ... THEN Reboot the watch, open Advanced Settings on watch go to Bluetooth > check the Discovery Mode Box and RE-PAIR the watch with Android Wear .. when I have the problem 'that sounds like what you're describing' this procedure fixes it for me.
sorry you're having problems with your watch .. if it's because of data-cross-contamination between different versions of Google Play Services updates that is causing this then I hope Google takes some action and stops doing this ... non-functioning watches does NOT make people want to buy smartwatches
Click to expand...
Click to collapse
No Problem!
Today i unlocked my Watch and installed Advanced Settings. Then i deleted the data from Google Play Services and did a Reset and tried everything you described, but untill now no messages arrived on the watch... Could there be something else wrong or settings on my phone?
The Google Play Service Version on the phone and on the watch are nearly the same (10.0.84) but the number after the bracket are different (238-... on phone and 530-... on watch)...
Thank you, yes its very annoying having a Smartwatch which isn't recieving any messages ... hope it can be fixed, but because its only software related it should be viable.
htcdesire-hd said:
No Problem!
Today i unlocked my Watch and installed Advanced Settings. Then i deleted the data from Google Play Services and did a Reset and tried everything you described, but untill now no messages arrived on the watch... Could there be something else wrong or settings on my phone?
The Google Play Service Version on the phone and on the watch are nearly the same (10.0.84) but the number after the bracket are different (238-... on phone and 530-... on watch)...
Thank you, yes its very annoying having a Smartwatch which isn't recieving any messages ... hope it can be fixed, but because its only software related it should be viable.
Click to expand...
Click to collapse
wow that would drive me crazy .. all I can think of would be to try the earlier version of Android Wear on the phone you used to have ... apkmirror would have it .. wow good luck I hope it gets fixed
I tried to install an older version of Android Wear but it did not help.
So i don't know what to do anymore...
Solved!
I just got the solution for my problem!!
It was a very stupid mistake: Android Wear was not set as device administrator... There was even a notification on my Wear app,
but i didn't recognized it because normally there is a notification to activate locations and it looks exactly the same
htcdesire-hd said:
I just got the solution for my problem!!
It was a very stupid mistake: Android Wear was not set as device administrator... There was even a notification on my Wear app,
but i didn't recognized it because normally there is a notification to activate locations and it looks exactly the same
Click to expand...
Click to collapse
How did you check to make sure that it was? I too am having a similar problem where my SMS notifications would sometimes take over 2 minutes to get to my watch.
rimz808 said:
How did you check to make sure that it was? I too am having a similar problem where my SMS notifications would sometimes take over 2 minutes to get to my watch.
Click to expand...
Click to collapse
Because all system related notifications arrived on my watch without any problems and all notifications of third party apps didn't, it could only be Phone related...
You have an other problem, because the SMS notification is system related.
Do you sync via cloud (wifi) or via Bluetooth?
Did you try to reset your watch or reinstall the wear app (and delete app data)?
^good to know!
htcdesire-hd said:
Because all system related notifications arrived on my watch without any problems and all notifications of third party apps didn't, it could only be Phone related...
You have an other problem, because the SMS notification is system related.
Do you sync via cloud (wifi) or via Bluetooth?
Did you try to reset your watch or reinstall the wear app (and delete app data)?
Click to expand...
Click to collapse
I meant how did you check to see that Android Wear was set as device Admin? I looked in my device admin and did not see Android Wear in the list.
But I did do a reset of my watch and re-paired, and that seem to have fixed the notifications delayed.
rimz808 said:
I meant how did you check to see that Android Wear was set as device Admin? I looked in my device admin and did not see Android Wear in the list.
But I did do a reset of my watch and re-paired, and that seem to have fixed the notifications delayed.
Click to expand...
Click to collapse
Sorry it was not the device admin query, but the notification access query (Preferences -> Apps -> Settings -> something like "Special access" -> Notification access).
Good to hear, that your problem is also resolved!
Not resolved. Same problem. Notification would arrive much later than on phone, and even calls are now not going to my watch. I performed another watch factory reset again, but why am I having to keep doing this?
I have a Huawei watch with a Huawei Mate 9. I would expect both to work seamlessly together. I had no problems when my watch was synced with my Axon ZTE 7.
So this is what I believe is causing the problem. When the phone and watch gets out of range (walking away from my desk without my phone), for some reason the phone and watch does not ask to be paired. It looks as though they are both still connected. With my Axon 7, whenever both got out of range and wanted to connect again, I would get a notification asking if I wanted to pair the watch with my phone. I would then accept. In this case, with the Mate 9, I do not get that pairing notification and I believe that is why i do not get notifications to my watch after it has lost its connection. I had to manually unpair the watch from my phone, then pair it up again.
Any insights?
rimz808 said:
So this is what I believe is causing the problem. When the phone and watch gets out of range (walking away from my desk without my phone), for some reason the phone and watch does not ask to be paired. It looks as though they are both still connected. With my Axon 7, whenever both got out of range and wanted to connect again, I would get a notification asking if I wanted to pair the watch with my phone. I would then accept. In this case, with the Mate 9, I do not get that pairing notification and I believe that is why i do not get notifications to my watch after it has lost its connection. I had to manually unpair the watch from my phone, then pair it up again.
Any insights?
Click to expand...
Click to collapse
I do also have a Huawei Mate 9 and i dont have any problems... I did never get a re-pair notification (on my HTC One M7 also). It re-paired automatically when i was in range!
htcdesire-hd said:
I do also have a Huawei Mate 9 and i dont have any problems... I did never get a re-pair notification (on my HTC One M7 also). It re-paired automatically when i was in range!
Click to expand...
Click to collapse
And your notifications come to your watch the same time it comes to your phone? Just to clarify, mine does automatically re-pair when it gets in range again, but I was thinking that maybe somehow it doesn't fully re-pair, which was the cause of my delayed/missed notifications? So I wanted to manually re-pair to make sure it did.
Still trying to figure out when my notifications sometime shows up, and sometime does not. Baffled.
The messages arrive about 1-2s later (i disabled vibration on my phone) and since i set Wear for special access everything works without problems, like before...
If i understand right, your notifications arrive after a couple of seconds or sometimes they do not arrive? Is there a coherence when they arrive and when not? (for example always when you re-pair it don't work and when it's constantly paired it works, but delayed?)
And are you syncing with Bluetooth or Wifi (cloud)?
htcdesire-hd said:
The messages arrive about 1-2s later (i disabled vibration on my phone) and since i set Wear for special access everything works without problems, like before...
If i understand right, your notifications arrive after a couple of seconds or sometimes they do not arrive? Is there a coherence when they arrive and when not? (for example always when you re-pair it don't work and when it's constantly paired it works, but delayed?)
And are you syncing with Bluetooth or Wifi (cloud)?
Click to expand...
Click to collapse
I am going to keep monitoring and see if I notice any patterns to when I do receive notifications instantly, and when I do not. Yes, sometimes my notifications, i.e SMS, or my CNN notifications, I will hear that it arrive on my phone, but then look at my watch and do not see the notifications. Sometimes, it would eventually go on my watch a few minutes afterwards.
When I re-paired it, I did notice that my notifications appeared instantly. I did not try to walk away from my phone and come back to have it re-paired automatically. I can try that today and see what happens. I just turned on wi-fi sync yesterday. But would i still be getting text SMS through wi-fi?
When you say that you set Wear for special access, where about did you check that?
Yes, try to find out what commonly happens when it does not work...
I haven't been trying wifi sync but i think all notifications should work like using bluetooth.
htcdesire-hd said:
Sorry it was not the device admin query, but the notification access query (Preferences -> Apps -> Settings -> something like "Special access" -> Notification access).
Click to expand...
Click to collapse
I adore the new keyboard functionality of 2.0, but in general my watch has been behaving poorly since the update. I have it paired to a Huawei mediapad m3 8.4 (cellular version)
At all times, notifications seem to come through in a timely fashion. But anything that requires an Internet connection (specifically Google Assistant, voice replies to notifications, and weather) are hit or miss. Half the time they work just fine. Other times they don't.
I've factory reset the watch since the update, with no improvement. Again, at all times notifications come through. But sometimes, anything that requires voice dictation or data fails. At these times, I go into the Android wear app, and it says connected. I can see and even reply to notifications with the keyboard, but if I try to use voice, or the assistant, or query for a weather update, it will tell me disconnected, or couldn't reach Google. Play store updates on watch apps are the same problem.
When I go into the watch settings while observing this bad behavior, under Bluetooth settings, it shows my phones Bluetooth ID, and says disconnected. When it's working properly, it says connected. But in BOTH cases it properly receives notifications, so just the Internet sharing to the watch from the phone seems at issue.
I've done everything short of factory resetting my phone, which I'd rather not do, including clearing data from Google app and clearing data /Uninstalling /reinstalling Android wear on the phone. Does anyone have further suggestions?
Screenshots for reference
https://flic.kr/p/UCzYGL
Weather app
https://flic.kr/p/TpK7s1
https://flic.kr/p/TsD85r
https://flic.kr/p/TpKcvY
Edit: just on a whim, I decided to try Shazam on the watch while assistant, weather, and voice were not working. Even in the "disconnected" state, it could properly identify music. Baffling. Though if Shazam on wear just records the audio, sends it to the phone, and that does the identification, I suppose this follows logic. Still sort of feel like it's specific to Google though.
Hi, I can't connect my buds+ or my car Bluetooth to my phone when I receive a Facebook messenger, never faced it with any other phone I have
Do you mean you can't hear audio from Messenger via bluetooth? If so, FB Messenger was like this on my last phone too (Mate 20 Pro), so it's an app issue, not the phone
jonboi said:
Do you mean you can't hear audio from Messenger via bluetooth? If so, FB Messenger was like this on my last phone too (Mate 20 Pro), so it's an app issue, not the phone
Click to expand...
Click to collapse
No, in the sound settings, I select Bluetooth and it connects for 1 second and then revert back to the internal mice , never had this before