Uggh.. Might have to stop wearing this thing because I cannot figure this out. Everyday, it seems like my Gear will randomly stop giving notifications. Everything is setup correctly and the check boxes are marked and everything. If I toggle bluetooth or reset the gear, the notification comes right through. Ive tried completely resetting the Gear and even doing a factory reset on my Note 3. No luck.
Any ideas on what could cause this? Im all stock.
I have this same problem. I've read other places that if your phone screen is on when the notification arrives, it won't send it to your phone. But even if that is true, it still seems inconsistent at times. It is frustrating...
thewisteron said:
I have this same problem. I've read other places that if your phone screen is on when the notification arrives, it won't send it to your phone. But even if that is true, it still seems inconsistent at times. It is frustrating...
Click to expand...
Click to collapse
Yup. If the phone screen is on the notification wont come through. When you turn the screen off, the notification should come through on the watch. That makes sense.
But you said, it's frustrating when it flat out misses notifications..
Yea, noticed I was missing some Gmail notifications today and rebooted the gear and all started working properly again. Makes no sense.
Yep, this is happeing to mine as well. My watch will be quite for a while and ill pick up my phone and boom, i have 3 texts and an email and my watch did nothing. screen was off and the icon that says gear is connected is there as well.
yeah started noticing this after Gear Manager updated itself to the white version (1.7)
This happened to me few times, but I've made a habit by disconnecting and reconnecting it to gear manager on every morning when I start to wear it.
Related
Last night I was at home and noticed my wifi wasn't on, so I used the quick settings in the shade to toggle it. After a few seconds, wifi connected, and some unknown app took focus and closed repeatedly. After a few moments, it stopped and all was well.
I thought it was strange, so I turned wifi back off and the same thing happened. I rebooted, tried again, and got the same result. I was trying to think of a way to see what was happening, so I tried using the Screen Record function in Gravity Box, which didn't help much, because it happens so fast, and no info is displayed, just a black window that goes away quickly.
I then turned on the CPU usage in Developer Options to see if anything consistently came to the top when toggling. I saw a few apps each time Plume (Twitter), and Maildroid (email) were two of them. Both of these apps behave differently on wifi and 3G/4G (push vs. pull), so thought -maybe- it could be something with that. I uninstalled both of those, rebooted and tried again, getting the same result.
I recorded the screen when this was happening with the CPU usage displayed, and was wondering if anyone has any ideas? I don't really want to uninstall and reinstall EVERY app on my phone, so I was hoping someone may have seen this before or see something I'm missing when watching it happen.
Video: https://copy.com/8L6VTsqcdbUjVTz
Thanks for any input anyone can offer!
Do you check virus from your phone ?
I am also having this, seems to be due to 4.4.2 OTA, which I continue to delay as I am rooted.
Mine doens't only happen with wifi change, but also just randomly when using hangouts, keyboard stays out but hangouts min -> maxes quickly. I have tried freezing the update apps but it apparently didn't do anything as I was still asked to update earlier.
Only hangouts? I have that app disabled.in the app settings.
I can't say for sure that being on 4.4.2 fixed it, but I am on 4.4.2 now and it is not happening anymore.
I unlocked my bootloader and did the 4.4.2 SBF, unlocked and rooted. I installed probably 99% of the same apps (only ditched 1-2 that I never used anymore) and I am not having the flashing issue anymore.
Hard to tell for certain if the pending OTA was the cause, but it may have been.
Okay folks, I wonder if anyone out there can help... My One is randomly vibrating once, with no notification, and I can't figure out why.
Other threads point to similar issues but not the same problem I have. I've been troubleshooting a lot, but can't narrow it down much. What I know so far:
Appears random. Not a particular time, battery level etc
No notifications appear in the bar. It can happen even when I'm looking at the phone and there is no visual indicator.
I have a Pebble watch, so most notifications can and do come through to the watch - no notifications on it when the vibrate happens.
It also doesn't seem to be any kind of dropped Bluetooth connection with my Pebble, as the Pebble doesn't notify of a lost connection like it normally would.
I have also read threads for other HTC phones where it pointed to nfc being switched on. While I do usually leave NFC on, the vibrate still happens even when I disabled NFC
.
I was holding off until Vodafone decide to release the Sense 6 update, but I'm not holding my breath there...
Is there anything that I could investigate? I was trying to avoid rooting or modding the phone for as long possible, but would be prepared to do it. However, I don't really fancy going down that road if the problem will still be there.
Suggestions appreciated!
paulgildea said:
Okay folks, I wonder if anyone out there can help... My One is randomly vibrating once, with no notification, and I can't figure out why.
Other threads point to similar issues but not the same problem I have. I've been troubleshooting a lot, but can't narrow it down much. What I know so far:
Appears random. Not a particular time, battery level etc
No notifications appear in the bar. It can happen even when I'm looking at the phone and there is no visual indicator.
I have a Pebble watch, so most notifications can and do come through to the watch - no notifications on it when the vibrate happens.
It also doesn't seem to be any kind of dropped Bluetooth connection with my Pebble, as the Pebble doesn't notify of a lost connection like it normally would.
I have also read threads for other HTC phones where it pointed to nfc being switched on. While I do usually leave NFC on, the vibrate still happens even when I disabled NFC
.
I was holding off until Vodafone decide to release the Sense 6 update, but I'm not holding my breath there...
Is there anything that I could investigate? I was trying to avoid rooting or modding the phone for as long possible, but would be prepared to do it. However, I don't really fancy going down that road if the problem will still be there.
Suggestions appreciated!
Click to expand...
Click to collapse
If your phone is not modified in any way, the best thing to do is take it to service
Can't think of a good sig
I'm no longer getting vibrations on my wrist with my Gear Live. I haven't touched anything, but they just stopped. The motor does work however, I've tested it using the Phone Finder app. I've tried resetting the device, restarting the device, and making sure that it's not on mute. I can't seem to find settings for this anywhere; could someone help me out?
Edit: I love how as soon as I post this, vibration starts working again..
Could it be that certain apps aren't getting the thing to vibrate, but others are? Anyone else getting vibration notifications with Textra?
I swear vibration didn't work every time. It's so faint though that even when it does, I don't notice it
Sent from my GT-I9505 using XDA Premium 4 mobile app
DrawnToLife said:
I'm no longer getting vibrations on my wrist with my Gear Live. I haven't touched anything, but they just stopped. The motor does work however, I've tested it using the Phone Finder app. I've tried resetting the device, restarting the device, and making sure that it's not on mute. I can't seem to find settings for this anywhere; could someone help me out?
Edit: I love how as soon as I post this, vibration starts working again..
Could it be that certain apps aren't getting the thing to vibrate, but others are? Anyone else getting vibration notifications with Textra?
Click to expand...
Click to collapse
Do you get Textra to work without. Contact + ?
Watch not vibrating for text messages
I noticed my Gear Live wasn't vibrating for text messages. It seemed random whether or not it vibrated for text messages. It vibrated normally for all other notifications. I have now discovered (and I believe and hope it's a software issue) that my watch will vibrate every time for incoming texts if and only if my phone is set to silent or ring mode. If the phone is set to vibrate, my watch will not vibrate for incoming texts. My Phone is a Samsung Galaxy S4 on the Verizon network running Android 4.4.2. I have tried rebooting, powering down andback on, and even a factory reset all resulting in no change of behavior. Is this similar to what you were experiencing? Anyone else experiencing this?
Text message vibration not working
I also noticed I'm not getting a vibration for text messages. Not sure why, I've had the watch for a week now and this just started a day or so ago. I've also restarted and reset to factory settings with no luck. If anyone knows of the issue, please post. Thanks!
UPDATE
MikeyFlo727 said:
I also noticed I'm not getting a vibration for text messages. Not sure why, I've had the watch for a week now and this just started a day or so ago. I've also restarted and reset to factory settings with no luck. If anyone knows of the issue, please post. Thanks!
Click to expand...
Click to collapse
Not sure if it's a permanent fix or not, but I actually shut my phone down completely (Samsung GS4) and turned it back on. I did a couple test text messages and the watch is picking up the messages and vibrating again. Again, this could just be a band-aid but it did seem to work.
Let me preface this by saying that after changing this setting and 20 hours later with multiple separations of phone and watch, I have yet to miss a notification and battery life is much much better. My specific problems were: Watch would randomly stop receiving notifications. I would realize this after a few hours go by without any notifications and pull my phone out and see what I've missed. This would happen despite the Wear app showing 'connected' status. Another issue I had was giving a voice command and after a few seconds the watch would return a 'disconnected'message, again the Wear app showed connected. All of this under known working network connections, whether Wi-Fi or cellular. I was also experiencing what I feel is short battery life at about 14 hours per day. I've had and used the watch for two weeks now and have restarted it many many times.
The following is the ONLY thing I have changed since the major improvement in performance. I don't have the depth of knowledge to prove or describe why this worked for me, and maybe it wasn't the cause, but I (knock wood) have a perfectly operating watch now with the battery life indicating about 2 days remaining at noon today.
Go to Settings> Bluetooth> and select the settings icon on your connected device. Then select 'connection access' and choose 'automatic'. Mine defaulted to 'always ask'.. I'm guessing this caused a hangup with the connection between Wear app and watch leading to my problems.
Edit: I'll add that my phone is an LG G2 on 4.4.2 , rooted and running xdabbeb's Rom.
Edit 2: I reset my watch, synced the watch via the Wear app on phone and NOT the Bluetooth screen and now I'm running strong after two days. Made sure automatic was checked as well.
Bugger
I don't have that option in my bluetooth settings
I don't have any problems with mine so far but just checked my settings and it was on always ask.
Could anyone confirm what it should be set as? I have changed mine to automatic anyways.
Thanks for the heads up.
Phil
Not seeing that option in Android 5.0.1 on my HTC One GE. But I have not been having any of the issues mentioned in the OP.
Sent from my Nexus 10 using Tapatalk
Here is a pic of the screen where you make selection. Always Ask is NOT what you want, which is what is pictured. Select Automatic. Sounds like this isn't available on Android 5.0 from what I see in responses so far.
I don't think I saw this option on any of the ROMs I ran, but there may be devices out there that have it and default to it, and this one would really break wear connectivity - so it may help someone someday.
I'm on 5.0, lg g3 and have both options.
Although i havnt had a problem with always ask and only switched it to automatic tonight.
Judging from the description, it will work as long as the watch stays connected, but a reconnect from the watch side would ask for confirmation (and could be possibly even silently denied under some circumstances).
Phone -> Watch = no problem
Watch -> Phone = problem
and it's possible (and likely) there are more connections going on than just the primary one, and if the connection is flaky there might be a dead one and a new one from either side...
you could just have been lucky, so far
My issues returned last night. I left my watch at home and went to dinner and out with friends, came back home after several hours. I left the watch in theater mode while I was out and over night. I woke up this morning, put watch on and realized the battery had tanked overnight and I was no longer receiving notifications, again, wear app showing connected. I looked at the battery graph for the watch and it is totally flat while I was out last night and appears to tank fast as soon as I got home and my phone was in proximity to the watch again. It's like it is constantly trying to handshake with the phone or something. The only thing that fixes this problem is a reboot of the Watch itself. I still think the connection setting was helpful because I have yet to see battery life like that or a solid link for that long. I would love to know what exactly is going on here. Bad hardware?
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
That's what I have also since I own the watch.
Stbrightman said:
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
Click to expand...
Click to collapse
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
mic18u said:
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
Click to expand...
Click to collapse
Nope, shows also when out of the box so without android debugging.
Just a normal operation notification
I just discovered another possible contributor to connectivity issues: I just tried to use my watch to voice dial and after multiple attempts I got the disconnected message. I took my phone out and Wear app says connected and I had full 4G signal. My phone is set with a pattern lock. After unlocking it and checking the above mentioned, I tried the watch again and it worked. Could locking your phone have something to do with these problems?
I bought the Watch R a week or so ago and I've been trying to work out why the Google Now notifications are so unreliable.
At first, I thought it was just me - I never really embraced Google Now and actually had it turned off on my phone (Galaxy S6 Edge). A few days ago I turned it on, configured it and was expecting to see the odd card popup on my watch every now and then but I've had zip.
So, I thought I'd test the notifications on the watch, from the Android Wear app, but the only notification that works all the time is the phone call. Most of the other notifications just don't pop up on screen and the only way I see them is to swipe the face from above and then they're there. Is this normal behaviour? I thought that notifications were supposed to popup on the screen, like on my phone!
I've reset the phone a couple of times in desparation but it's made no difference. I've unpaired the watch from the phone and re-paired it after forgetting the device. No difference. Removed all the custom watch faces and used only the once that came with the watch and once again, no difference.
I do get notified of text messages and emails with no problem, but nothing from Google Now.
Can anyone please suggest anything?
I have the s6 and I don't receive any notifications except the test phone call. I believe it to be a samsung problem with it killing the wear app from running in the background. watch worked fine with my other phones.
It's ridiculous, my s6 / gwr doing the same thing. Reboot both and things work for a little while, then gradually peters away to nothing. Except for sometimes I'll tap the watch for the time, and some random google now cards will be there, which I dismissed days before! Swipe them away but the same few keep coming back! As for the weather reports, well they've not worked for over a month now. And all this without me touching any settings whatsoever. I've exempted the android wear app from battery optimisation in the s6 too, incase they were that dense they'd overlooked that core app, but doesn't seem to have sorted it. Seems every time these companies update stuff they break it, and don't care about fixing it.!