Database Develop

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....

Anyone has Notification vibration problem?

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.

Android stops sending Notifications to Pebble Watch after time.

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.

Car doesn't switch automatically between day and night mode

I drive a 2016 Honda Civic and have enabled the re-designed Android Auto update. The problem is whenever my US Unlocked Galaxy S9 (Snapdragon) is in Dark Mode, Android Auto is forced into dark mode, no matter if it's daytime outside. And when Dark mode is turned off, Android Auto is forced into Day mode, even if it's night time. I've enabled developer options and tried "Phone controlled" and "car controlled" but neither get the desired result. I have the most recent July 2019 patch.
Some say on reddit that this has been fixed for them, but I have no idea why it isn't working for me.
What am I doing wrong?

I have almost the same problem. The difference is that I don't get to force AA in night mode at all. I also tried all options in AA developer settings with no success. I use AA on a Peugeot 3008 with a Galaxy Note 10+ connected and Android 9. Everything worked fine with the Note 8 and Android 8.1 I had before. I have all latest security updates installed on phone (august and september).
Sent from my SM-N975F using Tapatalk

Solution for that ?
- In the Android Auto app, tap the Hamburger menu.
- Tap About.
- Tap About Android Auto header 10 times, until a toast appears thar says "Developer mode enabled". Now you can access developer mode by selecting the overflow menu dots on the top right of the handheld screen.
There is a command for that night/day display
Do a try

rjpaul said:
- In the Android Auto app, tap the Hamburger menu.
- Tap About.
- Tap About Android Auto header 10 times, until a toast appears thar says "Developer mode enabled". Now you can access developer mode by selecting the overflow menu dots on the top right of the handheld screen.
There is a command for that night/day display
Do a try
Click to expand...
Click to collapse
If you would read what the poster wrote you would understand that he already did what you suggest and I also. Nothing helps.
Sent from my SM-N975F using Tapatalk

Probably the problem is Samsung One UI, are you using themes or are you able to use night mode on smartphone?
Try to remove theme and check android auto.

JRFabbi said:
Probably the problem is Samsung One UI, are you using themes or are you able to use night mode on smartphone?
Try to remove theme and check android auto.
Click to expand...
Click to collapse
Yes, indeed, I was using a high contrast theme, but going back to the original theme didn't help. Waze works fine on the phone in night mode with or without AA. Only when I start Waze from the car's infotainment system, it doesn't switch to night mode, even if I switch it manually from the settings. Google maps also does not switch to night mode.
Sent from my SM-N975F using Tapatalk

I've exactely the same problem and it started when my old S8+ updated to One UI, now my S10 have the same problem.
I will try to test without theme to check if it work here.
---------- Post added at 04:21 PM ---------- Previous post was at 04:05 PM ----------
Just checked here, android auto cannot change day-night mode on Samsung One UI.
If I put on night mode Waze and everything on AA is on night-mode and using it if I change to day-mode on One UI settings AA also change to day-mode so the problem is the One UI.

Guys, its known issue wiht Samsung One UI. What you can do is to set it on scheduel mode to sun set/sunrise with default theme, in this way the phone will go into night mode when the sun goes down and swithces automatically the AA into night mode automatically as well as your phone. There is nothing else you can do about it. maybe its possible with a tasker to set the phone to scheudeled night mode when it has connected to car BT, and then put it back into night mode if disconnected (its mabye possible only on S10(e,+) with bixbey routines, but never tried).
Before aug or sept update it was possible to circumvent this issue, by enableing developer mode with default theme, set it on automatic nigh/day and check also display night mode menu to to have the same setting. then you could install a high contrast dark theme and it still worked, changed the AA according the sun/set into night mode but did not change a thing on the phone, but this option has been disabled by samsung.

Question Android auto notifications stopped working once S21 Ultra was updated to Android 12

No notifications pop up when connecting in my car. If I have current notifications on my phone, once I disconnect and reconnect my phone to the car, they'll appear on screen but new notifications won't show.
I saw that some have the same problem as I do, but haven't heard about either a fix or if it's a common problem waiting for a fix.
Any idea ? Thanks