Database Develop

Disconnected...

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.

Phone not muted by Android Wear

Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?

finalbillybong said:
Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?
Click to expand...
Click to collapse
I have same problem. It's bug?

finalbillybong said:
Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?
Click to expand...
Click to collapse
Yes. I am facing this problem too! Seems like a compatibility bug with Android Lollipop. Might be due to the implementation of the 'Notification Priorities'.
Hope some updates come up soon to fix them!!

I'm running 5.0.1 on my HTC One M7 GE. The mute works with 5.0.1. It's a "priority" mode setting. Where the phone does not ring, but certain notifications may make a sound if they are priority and could be lowered.

Glad it's not just me then. Hopefully it'll be address in 5.1/5.0.1

Fixed in the latest Android Wear app. Version 1.0.5
Also seems to be OK on Lollipop 5.0.1 on the watch! Yay

Hum ... I still have the problem. Mute seems alright for notifications but not for phone ring.
I have Nexus 5 on 5.0 (LRX21O), Gear Live on 5.0.1 (LWX48P) and Wear App 1.0.5..1630507.
Also, I'm using Wear Aware app for being notified on watch if phone is missing, but starting with Lollipop, I have 5 ou 6 false alert each day.
I was working perfectly with KitKat.
May be it is the Wear aware app. I'll try another one.
Maybe 5.0.1 on phone will fix this when it will be available.
For now, our nexus 5 only have 5.0 (https://developers.google.com/android/nexus/images)

Anybody found a solution for this?
I have a possible work around but need help with tasker.
I set up a profile for when connected by bluetooth so that the ringer is off and vibrate is off but because off lollipop it does not work. Think it's the do not disturb option.
In my phones setting-lg g3- i can create a vibrating pattern that is a split second long and really weak.
What i need help with is how to recreate this in tasker. I.e is there a way of changing vibration strength in tasker and pattern.
If so we will be able to create this work around until a offical option is available.
Merry Christmas
Phil
Update;
Couldn't find a way of doing it through tasker despite asking on the relevant forums and hours messing around. Think tasker needs a few tweaks to allow these options to work on lollipop.
Although i found a app that works. I can set a rule to put my phone on silent but the watch still vibrates and visa versa when not connected.
https://play.google.com/store/apps/details?id=com.fancy01.myprofiles
Hope this helps, I'm going to do a few more rules for Wi-Fi, location etc using this app.
Cheers
Phil

I got the watch for Christmas and I have the same issue. My Gmail is muted, but the phone rings and all the other notifications sound off. I have a Nexus 5 running Lollipop 5.01 with the newest version of Wear and 5.01 on the watch. I'll be monitoring this thread for updates...

Firefyter said:
I got the watch for Christmas and I have the same issue. My Gmail is muted, but the phone rings and all the other notifications sound off. I have a Nexus 5 running Lollipop 5.01 with the newest version of Wear and 5.01 on the watch. I'll be monitoring this thread for updates...
Click to expand...
Click to collapse
The link in my post above yours is to a profile managing app that does what is required. I'm not sure if the free version works as i can't remember but paid one does.
I created a profile that mutes ringtone, no vibrate with a rule that activates the profile when connected to bluetooth device.
It switches notifications on the watch to priority so don't change that as it will make the phone start ringing/vibrate.

Work around that works
I have the same issue. Here what I do.
Android watch is connected and set to mute apps
Tap the volume rocker (for me nexus 6) and you'll see it says muted. For my work day I leave it on all.
Tap the bell icon and the phone will be put on vibrate. It's working great for the moment.
Best work around I have found.

The issues has returned for me on the latest version of the Wear app....

[Q] Gmail push notifications

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.

Lollipop bluetooth

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.

Note 9 started calling self upon Bluetooth pairing?

So here's a wierd one. Have a SM-N960U1 on Android 9. Everything's been fine but as of last Friday every time it pairs with a Bluetooth device (headphones, car, etc.) it starts calling itself? I re-paired all devices, turned BT off and back on, restarted phone, etc., but this behavior persists. Music is also terrible during this time, but realized by accident when I press Device Care widget to optimize phone the BT device announces 'Call Ending', and music again sounds great. However there's no record of any outgoing call in Phone App. I didn't realize what # was being called until I got in my car and saw it was dialing itself, but again, this phantom call does not show up in Recent Calls history? Any ideas?

Ugh... Same
Same man. Just letting you know you're not alone and following for a resolution.

smart lock on?

Removed all trusted devices from smart lock and it still happened.

Did a support Chat with Samsung, they recommended a soft reset (Vol dn + Power, similar to a Battery pull) which solved it temporarily when I turned on Bluetooth but since then the bug continues. No new updates or setup changes I'm aware of before this started happening. They also suggested running in safe mode and disabling Apps one at a time to see if the issue can be isolated (aren't these supposed to 'be' smartphones? Evidently there's no log of what it's doing) Will try that or another Chat session when I get some time again.

Ive been having this issue for a week or so as well. Every time I get in my car, I have to end the call. Its got to be a software update that caused the issue.

I'm thinking now it could be related to Bixby. I don't use it (remapped to google assistant & flashlight on long press using bxActions) but I recall I allowed it to update recently in case it gets better in the future.

Same issue here ... Sprint Note 9 on Pie ... Bluetooth headphones even has issues. I have to make a phone call and end it to be able to control volume from the headset (changing it from in-call audio to media audio).

Yup, those are the symptoms. Bluetooth headphones sound terrible and has no device control until the 'phantom' call that starts on it's own is manually ended.

I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck

ogretech said:
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
Click to expand...
Click to collapse
Awesome tip!
I use Ring Central App for keeping up with work phone messages. A few days ago started the phone in safe mode and had no BT issue, then back in 'un-safe' mode at first it didn't happen but cycling the headphones on and off it did occur again so I was faced with narrowing it down to which App. After reading your post I went into RC Phone settings, Mobile App Settings, Default Launching, and turned off 'Call From Android Dialer' since I don't use that feature and so far no issue!
Thanks for the tip, hopefully this setting change continues to solve this.

Still good after a couple days and weekly auto phone restart (Sat @ 3:00 AM). So nice not to have to end a phantom call that interrupts the stereo after 10 seconds every time I start the car.
Thanks again for the RC Phone tip.

You guys are definitely not alone. I unfortunately do not use the ring central app so I am not sure what is causing it for me...

I'm on the note 10 and have only had this problem pop up recently out of nowhere... I have no idea what could be my problem as I do not have RC Phone installed on my phone

Possible Solution
Hey, I posted a few days ago about having this same problem and not being a user of ring central. I got to thinking and tested this out. The Voxer app was the issue for me. I uninstalled this app and I haven't had any problems since. I am not sure about why the most recent Voxer update caused my phone to start doing this but I hope this helps someone else.

Possible Solution
Some may have tried this. Let me know.
My wife has Honda Hands Free 2016. In the past 30 days it started this same freaky behavior as all of you list.
She has a Samsung s9+.
She also has had Voxer installed on her phone and has had for many years. I will have to check to see if a recent update hit.
But, this is what seems to work for me at this point........
Told Honda Hands Free to completely forget her s9+. Then disabled blue tooth on the s9+.
Turn Entire Honda car off.
Turn Honda back on, told it to connect to my Samsung phone SM-J320A. Verified Honda was connecting properly to my SM-320A with no issues. All good with no freaky behavior. As info Voxer is not installed on my SM-320A.
Turned bluetooth back on s9+ then added the Samsung s9+ back to Honda Hands Free and told it to completely forget my SM-320A.
So far this has stopped the freaky behavior. If it comes back I will update here and then I will try uninstalling Voxer.