Related
Hi,
I have recently encountered a wired problem. Searched for web for similar issues, seen few same issue, but differ a bit.
I recently was surprised that phone stopped ringing or sound an sms alert or any other app alert such as WhatApp.
I tried to change the sound in sound settings for SMS, Whatsapp, Calls and Handcent app. All of which, didn't do any sound at all. When I select another sound within the apps, nothing is played. Some of them, played a standard beep instead.
I realized also that the alarm had a problem. It simply didn't sound at all at morning and therefore I was late to work that day :-(
anyways, I read on the net, few said, remove the battery for few seconds, did so, and helped, but problem comes up again. So I decided not to remove the battery anymore as it is a temp. solution only.
Some said, in Applicatoin settings, Sound Sets, clear data. Did that, and sometimes helps other doesn't. So another temp. solution.
Sometimes when it happens, I keep trying selecting different sounds, open different apps, changing their notification sounds, and suddenly, I can hear something when changing notification sound, then I know it is back again.
Now it has been happening for around 10 days, and didn't figure it out. I might need to do a hard-reset, but prefer not to as I hate installing all the apps (lots) I have installed and doing all the settings again. It takes long time. So I need another solution.
Something is strange, I am almost sure its not a faulty hardware, but maybe an app that interfere with something.
Anybody experienced such thing?
I am one of those people who always has their phone on silent mode only (no vibrate, no sounds, nothing) as I just rely on the LED notification. Over the past couple of weeks I have noticed that when I wake up in the morning my phone is always on loud, noticeable straight away by the little jingle it plays when you unlock the phone. As I never have sounds on, this was instantly noticeable.
After a couple of days I had discovered that at 7:00am every morning my phone would automatically switch itself from being on silent to loud.
I have never ever used the quiet mode scheduling or anything similar with apps or anything else like that so I have no idea where this has come from. I have checked recently downloaded apps and none of them seem to be in the category that would need access to or change sound profiles.
I have a Three UK handset on the latest software 4.4.2 (D80220d-234-20).
To my surprise I can’t really find anything anywhere with people having the same issue so I’m a bit stuck as to what to even try now? Any one got any experience or ideas?
Will make a sort of wild guess as the timing seems right: are you running Google Now? While I do love being able to say "OK Google" from everywhere, it's been causing -- or at least I think it has -- inconsistent issues with my alarm and profile volumes not where I expect it to be and possibly conflicts with some 3rd party apps (Light Flow). For instance, I have sometimes found that a daytime alarm I had set (manually, not via Google Now) didn't go off -- YET when I look at the notification bar, it shows as if I had snoozed it... yet I did not.
Recently, it seems like Light Flow was acting up (I know they had a July 11 update that is being blamed as less than perfect). However, I decided to disable OK Google voice from my launcher (Nova) and from Everywhere activation and everything seems to have returned to normal.
i have the same problem with my phone G pro lite dual after updating my software
This has been happening to me aswell since an update in November. I have never used the silent mode function, it is defibitely turned off, but my phone changes from silent to loud every day at 6am. I have seen numerous posts about it but no resolutions?
at some point of the day i noticed my notification sound no longer working.
I got all the msgs on my notification but with out sound.
turning off and on didnt fix. only the battery pull worked.
it happened like every once a day. some times I have to do battery pull twice a day.
I had this phone for a wk now.
anyone having notification sound issue?
even the turn off screen and on sound muted.
There's a few bugs, nougat is brand new, they'll fix things. My headphone kept buzzing one time until a restart
Its not just you. And I don't think its exactly something to do with Android 7.0
If you look at how your audio menu is when you change the ringer volume, you'll see that when the phone is set to vibrate, it actually MUTES the other two sliders.. it doesn't set them to vibrate. With that in mind, it seems more likely LG has a bug, than Android 7.0 having a bug.
Having this problem as well with my H910 (AT&T). It's very frustrating indeed. What's even worse is that it seems sporadic in nature, sometimes I will get a notification chime, sometimes I won't. As skyedream said, a battery pull is the only way to get consistent notification sounds, if only temporarily.
I think I get this too. Often I pull my phone out of pocket to find I had a text that I never heard.
Sent from my LG-H918 using XDA-Developers mobile app
I had this problem too yesterday where it was just frozen. Did a restart and all seemed ok after. First time that happened.
This happens to me as well. Also, I will get double notification sounds at times. Like an echo. Or, a different sound mixed with my selected sound. A reboot fixes. Have to do it a couple times a day. Very annoying.
No sound for notifications + no web video playback
I also have same issue with notifications. No pattern on what causes this, but a reboot gets rid of this (just for sometime! and the problem is back). I have also noticed apps not working smoothly and unable to play web videos including from Youtube app and Facebook App. Overall, tad disappointed with the software quality on this set.
Phone notification vibrate shuts off all other notification sounds
HikariNoKitsune said:
Its not just you. And I don't think its exactly something to do with Android 7.0
If you look at how your audio menu is when you change the ringer volume, you'll see that when the phone is set to vibrate, it actually MUTES the other two sliders.. it doesn't set them to vibrate. With that in mind, it seems more likely LG has a bug, than Android 7.0 having a bug.
Click to expand...
Click to collapse
Good call, thanks! I also notice that even though I have Sound Settings-Volume-Touch & Feedback sounds Off, I still get haptic feedback vibration on keyboard while typing this reply to you. It goes away when I go into Sound Settings-Vibration Strength, & turn slider off for Vibrate on tap. The Settings software isn't connecting the overall Volume Profile with the Vibrate Strength settings it seems. I don't know enough to know whether this is Android or LG. Under Vibrate Strength you can control notifications too, though haven't yet tested. Hope this helps til it gets fixed.
---------- Post added at 07:40 PM ---------- Previous post was at 07:26 PM ----------
DeesXDA said:
Good call, thanks! I also notice that even though I have Sound Settings-Volume-Touch & Feedback sounds Off, I still get haptic feedback vibration on keyboard while typing this reply to you. It goes away when I go into Sound Settings-Vibration Strength, & turn slider off for Vibrate on tap. The Settings software isn't connecting the overall Volume Profile with the Vibrate Strength settings it seems. I don't know enough to know whether this is Android or LG. Under Vibrate Strength you can control notifications too, though haven't yet tested. Hope this helps til it gets fixed.
Click to expand...
Click to collapse
I just tested texting...even though on quick settings slider notifications for text are grayed out, while call setting show vibrate only, in the full settings menu, under Vibrate Strength, you can slide the vibration strength up...I did this, sent myself a text, and phone vibrated the notification. I think it's messed up that I can't shut my call notification off completely, including nvibrate quickly with volume key or quick settings. Have to go into full settings menu sound & select silent. Please fix this Android/LG.
skyedream said:
at some point of the day i noticed my notification sound no longer working.
I got all the msgs on my notification but with out sound.
turning off and on didnt fix. only the battery pull worked.
it happened like every once a day. some times I have to do battery pull twice a day.
I had this phone for a wk now.
anyone having notification sound issue?
even the turn off screen and on sound muted.
Click to expand...
Click to collapse
Ya, I have the exact same problem... (I have a H990DS)
I can't seem to even fix it with a reboot.
I have emailed LG about the problem - we'll see what they say...
Digitalaks said:
I also have same issue with notifications. No pattern on what causes this, but a reboot gets rid of this (just for sometime! and the problem is back). I have also noticed apps not working smoothly and unable to play web videos including from Youtube app and Facebook App. Overall, tad disappointed with the software quality on this set.
Click to expand...
Click to collapse
I experience the same as you. I usually clear regents and then hit restart and all my notification sounds come back and videos. I'm just wondering, are you using any type of ad blocker? I use the ad block browser and I've noticed that whenever I open my browser, that's when my notifications get muted.
Issue resolved after update
Hi, looks like this issue is resolved with the update I got in January 2017 end. But not sure what caused it to fail in first place. But as of now, all is well after the update. Cheers!
I still have this problem over here on T-Mobile. Very annoying.
Anyone ever find a fix? Having these issues on a new LG V20 US Unlocked connected to Verizon.
Bumping this to see if anyone has found a solution to this. My V10 started muting notifications when the ringer volume was set to vibrate on one of its later updates. I figured it was a glitch in my phone since I didn't see anyone else complaining about it. This was one of the reasons i decided to upgrade to a V20. I was pretty surprised that it did the exact same thing and it's apparently by design. Who in their right mind would think this was a good idea?
I'm not sure of the cause, but I had many calendar reminder alarms fail to sound over several days when I got this V20. I tried different calendar apps and ended up with one called aCalendar. It works OK most of the time, but there is still a serious issue. If ANY other kind of notification happens to sound right when a calendar alarm needs to sound, the calendar will NEVER sound its reminder notification for the alarm. I've had this happen several times with incoming text or social networking message notifications. I hear those, and then the subsequent alarm that should have sounded concurrently is silent. I've had to set 2 reminders for the same important event, spaced 10 minutes apart, to try to reduce the odds of this issue hijacking an important notification. I've not seen this exact problem ever before on any Android device. My US Unlocked V20 is 100% stock. No idea what to do about it. But from what I can glean online, neither LG nor Verizon plan to push any future updates on the V20, so we're stuck.
For contact selecting unique notification tones that actually stopped working
I got this LG v20 and I loved it...still do....but... how do I keep certain text notification tones thst i select to not change back to default?...on its own? Crazy. I use zedge ap to download ringtones n notification tones. Maybe there is an issue there?
@Dkb123,
If you could please add some punctuation to your post, it might be easier to read so someone can understand your problem and help you .
I am using a rooted HTC One m10 with Viper ROM and am having the same problem. Echos notification noises, turns off alarm and notification sounds, and it is beyond annoying. I have already had to reset it twice to try to fix it and nothing has worked. I have no idea what is causing it but when I try to open my alarm app it says it was disabled and could have been caused by a system time change (which didnt happen) or battery saving (where I have it whitelisted). I will try disabling my ad-blocker. I'm not sure how those things could be connected but since it was suggested I will give it a go. I am consulting all of the developers I know about this but so far nobody has an answer. I am kind of starting to freak out because I need my phone to work. I have 3 kids under the age of 6 in school and need to know when someone has to get in touch with me. Before the last reset, I also saw that when my notification was disabled and I went back in to reenable it, it had been switched back to the sound I had selected the time before that. One more note. When I go in to check my notification noises, all of them, my ringer, notifications, and alarm, are all blank for about one half second before they repopulate and then show the correct tones. If it were as simple as it being my ROM someone would have posted it on the thread because it is a pretty big problem to have gone unnoticed. Is it possible we are all running an app or have a shared setting that is causing this to happen to only us. I had to dig pretty hard to find this thread in the first place. It might help if we posted a list of our apps, what do you guys think?
klear6 said:
I am using a rooted HTC One m10 with Viper ROM and am having the same problem. Echos notification noises, turns off alarm and notification sounds, and it is beyond annoying. I have already had to reset it twice to try to fix it and nothing has worked. I have no idea what is causing it but when I try to open my alarm app it says it was disabled and could have been caused by a system time change (which didnt happen) or battery saving (where I have it whitelisted). I will try disabling my ad-blocker. I'm not sure how those things could be connected but since it was suggested I will give it a go. I am consulting all of the developers I know about this but so far nobody has an answer. I am kind of starting to freak out because I need my phone to work. I have 3 kids under the age of 6 in school and need to know when someone has to get in touch with me. Before the last reset, I also saw that when my notification was disabled and I went back in to reenable it, it had been switched back to the sound I had selected the time before that. One more note. When I go in to check my notification noises, all of them, my ringer, notifications, and alarm, are all blank for about one half second before they repopulate and then show the correct tones. If it were as simple as it being my ROM someone would have posted it on the thread because it is a pretty big problem to have gone unnoticed. Is it possible we are all running an app or have a shared setting that is causing this to happen to only us. I had to dig pretty hard to find this thread in the first place. It might help if we posted a list of our apps, what do you guys think?
Click to expand...
Click to collapse
Hi. You posted this in the wrong area. This is for the LG V20. Try searching the HTC One M10 area for a solution. Someone there might be able to help you.
Not sure why but after the last system update the phone will only come out of black screen sleep mode if I use the fingerprint sensor when theres an incoming call.
Any Ideas ?
This happened to me today too.
Hello, me too! Oreo Beta 2
Anyone ?
going_home said:
Anyone ?
Click to expand...
Click to collapse
Not me, I've never experienced this issue since I got the phone from N then updated to OB2, and now OB3.
Sounds like the proximity sensor may have an issue.
Do you have a screen protector or case?
I don't have that issue with a screen protector and Tudia case and B3.
It's a bug in the latest Google Dialer app. I fixed it be deinstalling the new version/updates then clearing cache and data in the dialer app. It's affecting the Pixel2 XL running 8.1 also. Fixed my issue and I won't let it install the newer dialer version from the play store
In Beta 3, I haven't experienced that problem. I did heavily on 7.1.1
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
going_home said:
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
Click to expand...
Click to collapse
happened to me last week too.. it only happened after I locked the phone, 5-10 minutes later incoming call or when unlocking the phone the phone shows back screen only for a few seconds then it went back to normal.
the problem went away after I turned off the bluetooth radio.
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
DrvLikHell said:
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
Click to expand...
Click to collapse
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
I tried two other dialers and it didn't make a difference on my phone. Drupe did work to make the screen show who's calling again, but wow, Drupe has too much.... just, everything. All I want in a dialer is basic functions in a standard format. Drupe is like a carnival of a dialer. I'll keep trying dialers though, since that one did work, maybe another one will too. Thanks for the suggestion.
Yeah, if you just take the Drupe dialer phone icon and put that on your home screen, whenever you select it you'll go right to the normal looking dialer. :good:You may want to try ExDialer. That used to be one I'd use a lot.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Sent from my PH-1 using Tapatalk
rignfool said:
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Click to expand...
Click to collapse
10 million downloads...good enough for me. I've used it for a long time and it's been better for me than the stock dialer. Just my opinion, no one has to use it but it sure beats a black screen when the phone rings.
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Sent from my Pixel 2 XL using Tapatalk
I read about some people being able to fix it by uninstalling dialer updates. Unfortunately, the Essential doesn't have any to uninstall. I'm working around it by using Drupe as my default dialer, but setting the stock dialer as the default app for dialing, if that makes any sense (When an event pops up that requires the dialer, it asks which dialer to use, I selected the stock dialer and told it always use that.) This way incoming calls trigger Drupe, which acts the way it's supposed to on Bluetooth, but I can still use the stock app for making calls and missed calls and such.
bricky23 said:
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Click to expand...
Click to collapse
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Jank4AU said:
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Click to expand...
Click to collapse
My volume buttons always work fine, BT or otherwise. Stock 7.1.1. Your issue could very well be related to OB3. I had a little bit of an issue connecting/reconnecting to some BT devices at first, but not lately, so it must have been fixed in the last few patches.
I've had my Mi A1 for over a year now and have almost always had it on vibrate, so all calls/notifications cause the phone to vibrate, but any media that gets played will be at the volume set for media.
Over the past couple of weeks though, notifications (not sure about calls, don't get many of them) will play the notification sound at the volume set for media. I can only get them to shut off if I mute the media volume. I've tried changing the volume for both media and ringing, and restarting the device, but to no avail. I either have to leave it muted and miss notifications, or leave it unmuted and get a jumpscare each time (it also plays notifications when I'm on a call, and you can imagine the jumpscare I get with my phone at my ear and a sudden loud notification).
I recently started using Bose QC35 ii headphones through Bluetooth with my phone, but I don't think that has anything to do with it because it was working fine with them before.
I've searched Google for this kind of issue but couldn't find anything other than standard instructions on adjusting the volume. Does anyone have any ideas on how to resolve this (without doing a full reset of the phone, hopefully)?
EDIT: this is a stock ROM, I've never flashed anything new on it
freddo63 said:
I've had my Mi A1 for over a year now and have almost always had it on vibrate, so all calls/notifications cause the phone to vibrate, but any media that gets played will be at the volume set for media.
Click to expand...
Click to collapse
So I solved this by going into Settings > Accessibility > Vibration and turning Ring & notification vibration off, restarting, and then on again. I was able to use the Pushy app to send test notifications so that I didn't have to wait for a friend to send me a message or something of the sort. My vibration mode now works as intended (not sure about calls, I don't know how I can test those without having a friend call me), and loud notifications according to the volume set for the ringer.
So as it turns out, today I once again got sound notifications, despite having set my phone to vibrate only. What could be resetting the sound profile like this (note that the ringer volume is still at zero) that the notifications play sound at the media volume? Anyone have any idea on this?
freddo63 said:
So as it turns out, today I once again got sound notifications, despite having set my phone to vibrate only. What could be resetting the sound profile like this (note that the ringer volume is still at zero) that the notifications play sound at the media volume? Anyone have any idea on this?
Click to expand...
Click to collapse
Why not just set them individually, it won't take long, when I first got my A1 I did just this.
Each time I got a notification I just pulled down and pressed the notification and customised it, most I turned off, the rest I either set to vibrate, a custom sound or left as it was.
Calls are easy to take care of, set ring volume to zero and it only vibrates.
For me:
I want a sound when I get a SMS.
I want a custom sound when I get a call.
I want no notification of gmail, (it would be going off constantly)
I only want Vibrate from WhatsApp messages.
Can't think of others but I think everything else is silenced.
If that is no good try "Volume butler" which will add a seperate volume control for notifications, not used it myself but it should do the trick: https://www.guidingtech.com/separate-ringtone-notification-volume-android/
kudos1uk said:
Why not just set them individually, it won't take long, when I first got my A1 I did just this.
Each time I got a notification I just pulled down and pressed the notification and customised it, most I turned off, the rest I either set to vibrate, a custom sound or left as it was.
Calls are easy to take care of, set ring volume to zero and it only vibrates.
If that is no good try "Volume butler" which will add a seperate volume control for notifications, not used it myself but it should do the trick: https://www.guidingtech.com/separate-ringtone-notification-volume-android/
Click to expand...
Click to collapse
The only downside of doing them individually is that I can't turn them all back on with one setting, as on some infrequent occasions I do want to hear them because I be expecting a message and not necessarily feel the phone in my pocket. and it seems I have to wait for the actual notification to come up? (can't seem to find the setting under the standard notifications settings menu).
I'll have a look at Volume butler, but it sure is disappointing that this would break when it was a nice feature to use.
This seems to be a general Android bug with some bluetooth devices: https://www.androidpolice.com/2019/...s-with-duplicate-alerts-and-ignored-settings/
BtB said:
This seems to be a general Android bug with some bluetooth devices: https://www.androidpolice.com/2019/...s-with-duplicate-alerts-and-ignored-settings/
Click to expand...
Click to collapse
Wow, thank you so much! I now at least know it isn't a unique issue for me, and have an idea of what causes it.
freddo63 said:
Wow, thank you so much! I now at least know it isn't a unique issue for me, and have an idea of what causes it.
Click to expand...
Click to collapse
You're welcome, and seems that possibly if you unpair your BT device and reboot, you could get your notifications back to normal, but then you don't have your headset available...
Since the issue started outside of a system update, there is a chance it was introduced by a Google App or Play Services update, in which case hopefully Google will fix it soon since it's affecting a lot the Pixel phones.
BtB said:
You're welcome, and seems that possibly if you unpair your BT device and reboot, you could get your notifications back to normal, but then you don't have your headset available...
Since the issue started outside of a system update, there is a chance it was introduced by a Google App or Play Services update, in which case hopefully Google will fix it soon since it's affecting a lot the Pixel phones.
Click to expand...
Click to collapse
Ah, I forgot to mention that I have a workaround for this that I came across in one of the dicussions somewhere. Inside Settings > Google > Search, Assistant & Voice > Notifications I can turn off notifications for Google completely. I've also turned off Google Assistant under Settings > Google > Search, Assistant & Voice > Google Assistant. I don't remember which of those actually resulted in the behavior not returning, but I'm pretty sure I don't need either, so I'm OK with it for now. (actually, do Google Security notifications come under the Google app or some other one?)
PS: reboot is actually not necessary, it seems force stopping Google Assistant or Google resets the notification settings (but yes, I want my headset hahaha).
Seems it's been fixed by Google: https://www.androidpolice.com/2019/...s-with-duplicate-alerts-and-ignored-settings/
BtB said:
Seems it's been fixed by Google: https://www.androidpolice.com/2019/...s-with-duplicate-alerts-and-ignored-settings/
Click to expand...
Click to collapse
Thanks! I will "just sit tightly" (as it says on the update) :laugh: as I wait for the update.