Hello people,
I had a weird issue the past few nights with my WiFi. Specifically, I turn off all data, wireless and mobile, when going to bed. However, when waking up yesterday and today, my screen was full of notifications, which wouldn't have possibly come through with all toggles off. I thought that maybe it happened because my Android Wear smartwatch was pushing notifications to the phone (it has standalone WiFi connectivity) but it looked weird so I decided to test it.
I switched off WiFi/Data/Bluetooth on the phone and WiFi/Bluetooth on the watch and tried to send myself a messenger message. It came through, even with no apparent connectivity! I could also reply to it (from facebook messenger) although I couldn't browse websites through Chrome. Hmm weird. I tried turning Airplane mode on and off and it seems to have fixed that. I used my default config to test my Wear theory, only Bluetooth on phone and WiFi/Bluetooth on watch, and no messages came through, so the solution was apparently the Airplane mode toggle.
Anyone else experienced something similar?
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.
OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?
I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.
I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification
disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...
Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.
I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.
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?
Hi guys,
I recently changed from a nexus 5 and the phone is super nice. Of course, hardware > software.
In any case, I noticed a starting a few days back that I do not get gmail push notifications as they come.
Meaning, I have to pull to refresh. This also means that I do not get new gmail notifications.
I did some fiddling around with the settings and it wasn't set to notify me for all new mail but even with this on, I don't get timely notifications.
I did further research and noticed that I get my notifications on wifi but not on regular data.
-edit-
I tried it again and now both wifi and data are not reliable. I'm on a hotel wifi connection so I expected this but I wasn't expecting this from the data.
Has anyone heard of the S6edge having possible radio/modem issues? If so, I'm going to go exchange this device for another s6e.
I'm really hoping that it doesn't come to that and that it's a software issue more than hardware.
The thing is, I don't know if anyone knows but the same thing above happens to me with an application called kakao talk (a korean version of whatsapp)
I don't get push notifications and when I open the app I get bombarded with messages.
After opening the app and then closing it, I get updates like normal.
I can't figure this out. Do any one of you have any suggestions?
I don't get notifications for gmail or inbox either, everything is turned on. It was bothering me before but I got used to it . I use kakao religiously but with notifications off..I'll tick then on and see
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
xketch said:
I don't get notifications for gmail or inbox either, everything is turned on. It was bothering me before but I got used to it . I use kakao religiously but with notifications off..I'll tick then on and see
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
I couldn't wait and I just factory reset my phone.
Gmail notifications come as they should without me having to manually refresh the feed.
Yesterday morning I was on wifi and kakao notifications came in time as well, but I forgot to try this on the network and slept after turning it off last night.
This morning I woke up a little earlier than my alarm and noticed no notifications thinking I didn't get any.
However as soon as my alarm rang and I turned it off, notifications started coming.
Am I going insane? The device seems to go into some network sleep mode and will only start connecting once it's literally awaken.
I'm trying to rule out app bug, software bug, but most importantly, if this is a hardware bug.
If this is a hardware issue, I only have about a week to exchange it.
k0p4n said:
I couldn't wait and I just factory reset my phone.
Gmail notifications come as they should without me having to manually refresh the feed.
Yesterday morning I was on wifi and kakao notifications came in time as well, but I forgot to try this on the network and slept after turning it off last night.
This morning I woke up a little earlier than my alarm and noticed no notifications thinking I didn't get any.
However as soon as my alarm rang and I turned it off, notifications started coming.
Am I going insane? The device seems to go into some network sleep mode and will only start connecting once it's literally awaken.
I'm trying to rule out app bug, software bug, but most importantly, if this is a hardware bug.
If this is a hardware issue, I only have about a week to exchange it.
Click to expand...
Click to collapse
Disable and uninstall (updates) google play services. Later on you can re-update google play services. I know this is same as doing a factory reset but it is worth a try. I did the same to fix mine.
k0p4n said:
I couldn't wait and I just factory reset my phone.
Gmail notifications come as they should without me having to manually refresh the feed.
Yesterday morning I was on wifi and kakao notifications came in time as well, but I forgot to try this on the network and slept after turning it off last night.
This morning I woke up a little earlier than my alarm and noticed no notifications thinking I didn't get any.
However as soon as my alarm rang and I turned it off, notifications started coming.
Am I going insane? The device seems to go into some network sleep mode and will only start connecting once it's literally awaken.
I'm trying to rule out app bug, software bug, but most importantly, if this is a hardware bug.
If this is a hardware issue, I only have about a week to exchange it.
Click to expand...
Click to collapse
You are not losing your mind, this is a software bug and others have this issue as well especially with google related products.
So my dad is having issues with his Droid turbo. It just updated to lollipop and since then, his bluetooth disconnects every time the screen shuts off. It doesn't matter what he's connected to. As soon as the screen is off, it's as if his bluetooth wasn't even on. He's got a fitness tracker that he has an sync app for and it's supposed to be a background thing. Won't stay paired to his vehicle either. He's toggled bluetooth on and off, un-paired and re-paired and cleared data and cache under the Bluetooth sharing app. Nothing is working.
Anyone gotta fix or experience this as well?
Most likely it is a power saving program that is installed. Check settings in any battery apps you have installed for anything about bluetooth.
Like PittAussie said, he probably has one of those bull**** battery saving programs installed that's doing it.