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....
Related
I have moto x with Lollipop. I cannot get the sleep mode to work correctly. I am getting notification sounds at night waking me up. Yes all my settings are set correctly with Downtime and Sleep Mode. Am I missing something? Anyone else experiencing this with Lollipop?
As much as I love Lollipop, as much as I love the Moto X, downtime and priority notifications are a mess. They should've just disabled one or the other... I've been tinkering with mine all day to get it to work with my meetings on my calendar.
Slipperybrain said:
I have moto x with Lollipop. I cannot get the sleep mode to work correctly. I am getting notification sounds at night waking me up. Yes all my settings are set correctly with Downtime and Sleep Mode. Am I missing something? Anyone else experiencing this with Lollipop?
Click to expand...
Click to collapse
Same exact issue as you. Even though in priority mode I have all 3 option turned off (call/texts etc) I still get notification sounds coming through. I have tried every possible combination without success. The new notification system is the perfect example of "fixing" something that wasn't broken to begin with.
My only solution that I've found to work is to use Power Toggles as a widget. It let's you select 4 volume settings and has worked without a hitch. Hopefully the issue just a bug... But I won't hold my breath for a transparent or timely fix.
Give Power Toggles a try, works great!
So here is what I did. I completed a factory reset and it works now, but don't do a factory reset. Here is why it works. I went to the sounds and notifications, app notifications. I have hangouts and Gmail set to priority meaning it will alert me even when it is set to priority mode only and notifications are set to silent. Stupid me for changing that to begin with. Check that area.
Slipperybrain said:
So here is what I did. I completed a factory reset and it works now, but it don't do a factory reset. Here is why it works. I know the sounds and notifications, app notifications, I have hangouts and Gmail set to priority meaning it will alert me even when it is set to priority mode only and notifications are set to silent. Stupid me for changing that to begin with
Click to expand...
Click to collapse
Believe it or not, I double checked those too. They are greyed (unchecked) so I shouldn't still be receiving the notifications. I factory reset may have been what fixed it for you. Speaking generally, it's ridiculous that anyone would have to do that in order to have things work as they should. But I guess you can say there are always some bugs whenever a new update is rolled out - it's frustrating nonetheless.
I'm using Galaxy S6 Active in Korea
Of course, i unlocked, and updated to 5.1.1
(i used 5.0 just few days, i can't remember how long did it maintain)
Now my phone seems to treat the vibrate profile as silent.
text message vibrations is Okay(i'm using google messenger, not basic sms app, not google hangout)
But, Call notification,FB,Gmail....and so on, all of feature which has vibration noti feature do not work now.
Actually i already did device reset once. at that time, i could get vibration notification.
but few days later, back to present state.
i googled, and i got some people who were experienced like me.
but they said various opinions about this problem such as battery saving mode, 5.1.1 updating...etc.
plus no oned replied "i fix it!"
I constantly use the vibrate profile and this is very problematic not having the phone actually vibrate because I am missing notifications a lot now.
Is anyone else having this issue? Does anyone know how to fix this?
plz give me your comment
I read, I think on Android central, that this occurs when power saving mode is on after updating to 5.1.1. This didn't happen on the previous software.
So I just got a GS8. Fantastic phone. The only issue I am noticing is that when the phone enters "Do not Disturb" mode, it does not exit as scheduled. Typically it is set to turn on at 10 PM each night and turn off at 6 AM the next day. (save for the alarm that goes off at 5 AM). The alarm goes off fine. The phone, however, stays in "Do not Disturb" mode well past 6 AM and until I turn it off. Anyone else notice similar behavior? Could this result from the phone being connected to the A/C charger? I ask because when I set "Do not Disturb" to turn on and off at work it does so just fine. At work the phone is not connected to a charger.
I'm blanking on what it was, but I was running an app that was causing this issue. I've looked through my Google play library and just can't recall what it was. Might have had something to do with volume control. Start by removing anything you aren't using. If the problem persists, try removing anything that sounds like it could interact with audio or notifications until you find it. Worst case, factory reset, confirm issue is gone, then add things back until issue recurrs. I'll try again to jog my memory.
rcobourn said:
I'm blanking on what it was, but I was running an app that was causing this issue. I've looked through my Google play library and just can't recall what it was. Might have had something to do with volume control. Start by removing anything you aren't using. If the problem persists, try removing anything that sounds like it could interact with audio or notifications until you find it. Worst case, factory reset, confirm issue is gone, then add things back until issue recurrs. I'll try again to jog my memory.
Click to expand...
Click to collapse
This gets weirder and weirder. So, I am coming from a Mate 9. on that phone I could set multiple Do Not disturb profiles. So I had one set for overnight (10 PM to 6 AM and one set for work hours (7 AM to 3:30 PM). Although the GS8 only allows one profile, it seems to have "remembered" the second profile. I say this because the phone went into "do not disturb" at 7 AM. I am not even sure how that's possible. I did restore apps via the google, but I cannot think of anything else besides what you are recommending. I may have to do a factory data reset as you recommend and set everything up.
anl2304 said:
This gets weirder and weirder. So, I am coming from a Mate 9. on that phone I could set multiple Do Not disturb profiles. So I had one set for overnight (10 PM to 6 AM and one set for work hours (7 AM to 3:30 PM). Although the GS8 only allows one profile, it seems to have "remembered" the second profile. I say this because the phone went into "do not disturb" at 7 AM. I am not even sure how that's possible. I did restore apps via the google, but I cannot think of anything else besides what you are recommending. I may have to do a factory data reset as you recommend and set everything up.
Click to expand...
Click to collapse
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
rcobourn said:
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
Click to expand...
Click to collapse
You know, as long as I have had an android phone and I didn't think to do that. I should have. One issue I need to deal with is whether turning off the built-in Do Not Disturb disables that suspected hidden profile. If so, then I am good to go, if not, then I need to do the factory reset before using an app from the playstore (probably gives me more options than what Samsung allows).
Thanks.
rcobourn said:
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
Click to expand...
Click to collapse
Resetting the device did the trick. rather than restoring apps from the Huawei Mate 9, I started fresh and downloaded apps from the app store. A pain, but it worked. Thanks again.
I have a Pebble Classic smartwatch (I know, old, unsupported, and discontinued) and a Huawei Honor 6X. My Pebble watch is able to pair and receive notifications fine. After some time, it stops receiving notifications. Sometimes after 5 minutes or even an hour. It doesn't re-sync till I disconnect it via the Pebble app (or settings on the watch) and then reconnect it. After that, it begins the process over by staying in sync after some time then stops receiving notifications.
Also, a strange thing I notice is it syncs in the morning when I wake up just fine without having to do anything.
When it stops receiving notifications both devices say they're still paired.
I have tried forgetting the device and then reconnecting. I have checked that my Pebble app isn't in the lock-screen cleanup list for the Huawei management. The Pebble app has Permissions to notifications. I do have the persistent notification within the Pebble app enabled. This happened before the Pebble servers went down and even after switching to Rebble. I do have Google Wear OS installed. Should I try using GadgetBridge?
My brother has the exact same watch with his iOS device and it works flawlessly.
Phone: Huawei Honor 6x Android 7.0
Pebble: v3.12.3
Is there something happening with the phones Bluetooth connection? Is it the Android operating system putting the app into sleep or something. Is it going into power save mode or something? If rooting my phone will provide a fix I am willing to do so.
phcreery said:
I have a Pebble Classic smartwatch (I know, old, unsupported, and discontinued) and a Huawei Honor 6X. My Pebble watch is able to pair and receive notifications fine. After some time, it stops receiving notifications. Sometimes after 5 minutes or even an hour. It doesn't re-sync till I disconnect it via the Pebble app (or settings on the watch) and then reconnect it. After that, it begins the process over by staying in sync after some time then stops receiving notifications.
Also, a strange thing I notice is it syncs in the morning when I wake up just fine without having to do anything.
When it stops receiving notifications both devices say they're still paired.
I have tried forgetting the device and then reconnecting. I have checked that my Pebble app isn't in the lock-screen cleanup list for the Huawei management. The Pebble app has Permissions to notifications. I do have the persistent notification within the Pebble app enabled. This happened before the Pebble servers went down and even after switching to Rebble. I do have Google Wear OS installed. Should I try using GadgetBridge?
My brother has the exact same watch with his iOS device and it works flawlessly.
Phone: Huawei Honor 6x Android 7.0
Pebble: v3.12.3
Is there something happening with the phones Bluetooth connection? Is it the Android operating system putting the app into sleep or something. Is it going into power save mode or something? If rooting my phone will provide a fix I am willing to do so.
Click to expand...
Click to collapse
You can try to exclude the app from androids Power saving. Also gadgetbridge can be tested(I'm using it with my PTS).
I tried gadget bridge and that does the same thing. Also I have it removed from my power management, nothing. I downloaded an app that supposedly keeps the Bluetooth alive. I'll give that a go.
I found a workaround.
I installed an app called BluetoothKeepActive and that seemed to fix the problem. It seems that my presumption was correct. The Bluetooth is going into standby mode or power management mode or something.
phcreery said:
I found a workaround.
I installed an app called BluetoothKeepActive and that seemed to fix the problem. It seems that my presumption was correct. The Bluetooth is going into standby mode or power management mode or something.
Click to expand...
Click to collapse
Seems to be an kernel issue of your phone imo.
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.