My Galaxy S21 Ultra received an update on 4/10. I noticed, after receiving that update, that my phone was vibrating for all notifications and also when I turned the screen off. Digging around a little I realized that the option in Settings/Sounds and Vibration/Notification Vibration Pattern/ no longer shows "none" as an optional vibration pattern. (I believe I must have had set "none" as my Notification Vibration Pattern before this update, either manually, or perhaps by default. I don't remember doing it.)
The result of this is that there is no way to prevent the phone from vibrating on EVERY notification, since a pattern other than "none" must be set.
I also believe that this vibrating continues for at least some notifications even when the phone is in "Do Not Disturb" mode.
I can't imagine I am the only person experiencing this.
I have reported this to Samsung. Assuming others are experiencing this, it would be great if you could note that here, and also let Samsung technical support know, so that they can get this fixed.
Thanks!
Nope, your not alone. Was hoping someone would have already posted a fix. Dont understand why updates seem so hard to do these days,.................
have you checked in the app notification settings?
press and hold the app > i button > notifications > check each notification option and maybe disable the vibrate if you don't want it to vibrate?
and you have submitted an error report on samsung members app? or the community?
Post Nine said:
have you checked in the app notification settings?
press and hold the app > i button > notifications > check each notification option and maybe disable the vibrate if you don't want it to vibrate?
Click to expand...
Click to collapse
I just checked several apps. The apps all have different notification options, but none of the apps I checked had a specific notification option for vibrate.
Post Nine said:
and you have submitted an error report on samsung members app? or the community?
Click to expand...
Click to collapse
I did both.
I made a post very similar to my initial post here on the Samsung forums. And as I said in my initial post here, I did report it to Samsung. It was just the first level tech support and while the rep was very polite, and assured me that it would be corrected in a coming patch, she also said she had not heard about it before. So I took that basically as lip-service, and am not holding my breath. That's part of the reason I suggested that others also report it, as I'm guessing the more people that report the problem, the greater the likelihood that it will get resolved.
Post Nine said:
have you checked in the app notification settings?
press and hold the app > i button > notifications > check each notification option and maybe disable the vibrate if you don't want it to vibrate?
Click to expand...
Click to collapse
Literally the first thing I tried, no cigar
Andyw2100 said:
I just checked several apps. The apps all have different notification options, but none of the apps I checked had a specific notification option for vibrate.
I did both.
I made a post very similar to my initial post here on the Samsung forums. And as I said in my initial post here, I did report it to Samsung. It was just the first level tech support and while the rep was very polite, and assured me that it would be corrected in a coming patch, she also said she had not heard about it before. So I took that basically as lip-service, and am not holding my breath. That's part of the reason I suggested that others also report it, as I'm guessing the more people that report the problem, the greater the likelihood that it will get resolved.
Click to expand...
Click to collapse
ok so i meant the samsung members app where you can submit an error report and it sends errors directly to samsung so they can take a look at the issue. this is not the live chat with the tech support.
Post Nine said:
ok so i meant the samsung members app where you can submit an error report and it sends errors directly to samsung so they can take a look at the issue. this is not the live chat with the tech support.
Click to expand...
Click to collapse
I said I posted in Samsung Forums, but it was through the Samsung Members App on my phone. Sorry if I had the terminology wrong.
Andyw2100 said:
My Galaxy S21 Ultra received an update on 4/10. I noticed, after receiving that update, that my phone was vibrating for all notifications and also when I turned the screen off. Digging around a little I realized that the option in Settings/Sounds and Vibration/Notification Vibration Pattern/ no longer shows "none" as an optional vibration pattern. (I believe I must have had set "none" as my Notification Vibration Pattern before this update, either manually, or perhaps by default. I don't remember doing it.)
The result of this is that there is no way to prevent the phone from vibrating on EVERY notification, since a pattern other than "none" must be set.
I also believe that this vibrating continues for at least some notifications even when the phone is in "Do Not Disturb" mode.
I can't imagine I am the only person experiencing this.
I have reported this to Samsung. Assuming others are experiencing this, it would be great if you could note that here, and also let Samsung technical support know, so that they can get this fixed.
Thanks!
Click to expand...
Click to collapse
I only had the phone for a week and forced the April update as soon as it was available in Canada. Noticed the same idiotic removal of "None" in vibration pattern options.
Literally the first phone where I can't remove vibrations.
One solution might be to reduce the "Vibration intensity" for notifications to zero... but it's a sh!tty workaround.
Ipse_Tase said:
I only had the phone for a week and forced the April update as soon as it was available in Canada. Noticed the same idiotic removal of "None" in vibration pattern options.
Literally the first phone where I can't remove vibrations.
One solution might be to reduce the "Vibration intensity" for notifications to zero... but it's a sh!tty workaround.
Click to expand...
Click to collapse
I hadn't thought of changing the vibration intensity to zero. I just did that and there were actually options to set the vibration intensity separately for incoming calls, touch interactions, and NOTIFICATIONS! I don't know if those options were always there or not, but if not perhaps that is why the "none" vibration pattern was removed. (I'm not suggesting that was actually a good idea.) In any case, I think setting the notifications vibration intensity to zero, while leaving the others as they were, is actually a good work-around for me. Thanks!
Cheers for tip, will give it a try
Andyw2100 said:
I hadn't thought of changing the vibration intensity to zero. I just did that and there were actually options to set the vibration intensity separately for incoming calls, touch interactions, and NOTIFICATIONS! I don't know if those options were always there or not, but if not perhaps that is why the "none" vibration pattern was removed. (I'm not suggesting that was actually a good idea.) In any case, I think setting the notifications vibration intensity to zero, while leaving the others as they were, is actually a good work-around for me. Thanks!
Click to expand...
Click to collapse
I did a quick Google search, and the option to select different vibration intensity levels for the three different selections is not new. So that in no way explains the missing vibration option "none."
Related
Hi everyone
Re-posting this from the general section (posted on there by mistake, was still half asleep lol, sorry)
Just got the xperia z yesterday (after my previous lg 4x was stolen... grrr... may the thief get permanent bursting hemorroids...) and I noticed a weird thing.
The mute/vibrate/sound toggle in the notification bar does not seem to work, and the same goes for the one in the popup shown by pressing the power button for a couple seconds.
Details: the mute or vibrate icon appears on the notification bar, but if I check the volumes in settings, they're still all on, and if I receive a call or get a notification or whatever, the phone actually rings despite the supposedly muted state.
All this doesn't happen if I "manually" turn the volume off with the volume buttons or via settings: in that case the vibrate icon appears and the phone actually does not ring.
Has anyone experienced anything similar?
All good here dude. Hope you get it fixed. Have you tried turning phone off and on again? That usualy fixes small.glitches.
Sent from my C6603 using xda app-developers app
steve17harris said:
All good here dude. Hope you get it fixed. Have you tried turning phone off and on again? That usualy fixes small.glitches.
Click to expand...
Click to collapse
Yep, already tried that of course, as well as uninstalling the one widget I have that interacts with volumes, just to be sure it was not some weird conflict (and of course it wasn't)
Not a biggie actually, as I can turn it down manually or by said widget, but I hope I'll figure it out anyway if only for the sake of understanding the source of the issue
Yep I understand that. Annoys me when I cant get something working lile its ment to.
Sent from my C6603 using xda app-developers app
I have a problem with the toggle in the notification bar and the power off menu. System settings show me notifications and ringtones are off, but the phone still has audible, unmuted notification sounds. Really annoying.
robogo1982 said:
I have a problem with the toggle in the notification bar and the power off menu. System settings show me notifications and ringtones are off, but the phone still has audible, unmuted notification sounds. Really annoying.
Click to expand...
Click to collapse
Yep, that's the same exact issue I'm having
I guess we have to wait for a software update.
robogo1982 said:
I guess we have to wait for a software update.
Click to expand...
Click to collapse
I guess as much...
Actually, I could try a factory reset just to be sure, but I admit I'm kind of too lazy to set my stuff up again from scratch only to try and fix that small glitch
Vostradamus said:
I guess as much...
Actually, I could try a factory reset just to be sure, but I admit I'm kind of too lazy to set my stuff up again from scratch only to try and fix that small glitch
Click to expand...
Click to collapse
Well, I was thinking the same, but now that we got root... :laugh:
robogo1982 said:
Well, I was thinking the same, but now that we got root... :laugh:
Click to expand...
Click to collapse
Heard about it, but haven't read the whole thing yet (yep, still being lazy)
Jokes apart, I was planning to leave it 100% stock for at least a little while to see how the battery behaves without even the slightest piece of modding (got the phone only last friday, today has been the first real "field test" for the battery and so far I'm pretty positively impressed)
Well I have already removes/frozen a bucketload of apps happy bunny, I am. Now I only need to figure out which app does what so I don't kill something and make my phone less usable.
robogo1982 said:
Well I have already removes/frozen a bucketload of apps happy bunny, I am. Now I only need to figure out which app does what so I don't kill something and make my phone less usable.
Click to expand...
Click to collapse
lol I removed a few apps too, but luckily for me they were uninstallable without root or anything.
I also disabled a few more through the stock apps management, for the time being it's sufficient for my taste
Same irritating automatic toggling action going on
Vostradamus said:
Hi everyone
Re-posting this from the general section (posted on there by mistake, was still half asleep lol, sorry)
Just got the xperia z yesterday (after my previous lg 4x was stolen... grrr... may the thief get permanent bursting hemorroids...) and I noticed a weird thing.
The mute/vibrate/sound toggle in the notification bar does not seem to work, and the same goes for the one in the popup shown by pressing the power button for a couple seconds.
Details: the mute or vibrate icon appears on the notification bar, but if I check the volumes in settings, they're still all on, and if I receive a call or get a notification or whatever, the phone actually rings despite the supposedly muted state.
All this doesn't happen if I "manually" turn the volume off with the volume buttons or via settings: in that case the vibrate icon appears and the phone actually does not ring.
Has anyone experienced anything similar?
Click to expand...
Click to collapse
Yes, having the same problem as well with mine. But it has been the same problem since I had ICS on my Xperia Arc S, then Xperia V and now this when I use the toggle in the notification bar or any other toggle aside from toggling it manually via setting. Very irritating since it has never and probably will never be fixed due to the fact that it's a cross-model issue. Chances are, those who say they don't have this problem already has it but don't know it yet or will get it eventually. Sony needs to iron this out once and for all
Moto X, 4.2.2 stock, rooted
When receiving a an email, message, or whatever (e.g., Gmail, snapchat, kakaotalk, google voice), the active notification appears as normal (vibrate/sound + screen display), but then the phone repeatedly displays the notification until it's unlocked. I do want the initial notification, but just the one. After the initial notification, further notif. only display the screen (no sound/vibrate).
When there isn't a notification, it doesn't display the clock over and over again as if I'm picking it up, so it's not like it's being moved around or something.
It did not used to do this, but I'm not sure exactly what setting/app/whatever would have caused this.
'Active notifications' has an option to disable certain apps or turn off completely, but there are no 'repeat' or 'lockscreen' settings located there, or in individual apps.
When I googled/searched for the issue (key words: active, notifications, repeat, stop, android, alert), I found these related posts, which seem to describe what I'm experiencing (albeit on different phones). Edit: ah, I can't post links yet, if you would like to look at them, please google the parts-of-the-url below
s4-active-message-notification-doesnt-stop-coming-up-lock-screen
android-kit-kat-moto-x-repeated-notifications-for-the-same-email
Has anyone else had this problem? What settings, if any, can I check for to disable these unwanted (repeated) notifications or how else might I go about it?
This isn't a bug or an issue, it's a feature. It's something called "breathing" notifications.
Every so often, the phone will give you the notification again just to be sure you saw it the first time. There is no way to remove or alter this feature through Active Display's settings.
If you are looking for an equivalent to Active Display, a good one (and the only one I know of) is DynamicNotifications by GreatBytes.
Have you tried swiping the notification to the side? That should dismiss it.
Sent from my XT1053 using Tapatalk
It seemed to me it wasn't normal behavior, as I don't remember it happening when I first got the device, but if you say it's intended, I'll go with that.
DarkWolffe: you say "every so often". The notifications are appearing every 5 seconds or so. Is this inline with what your own experience? If I can't change that interval from the native settings, might the app you linked be able to? It seems that DynamicNotifications is made for devices that don't already have Active Notifications. (perhaps I'm supposed to disable AN and only use DN?) Thank you for the link, though, I'll check it out.
scottjb: Ah, I figured that out sometime after making this post, but thank you for that tip. It's useful when I may actually see the phone, but when I'm away from the phone or sleeping, for example, I'd prefer it not to behave that way. I realize it's an AMOLED screen, so the battery really shouldn't be affected too much, but it doesn't feel right to have it turn on over and over again so often.
Knowing they're called "breathing notifications" has allowed me to better search for related topics. It seems that turning the phone over or putting it in a pocket will stop the breathing. I'd still prefer if I could change the interval somehow, but I'm satisfied to have figured most of how it works out.
The interval of the notifications seems to change over time. When you first get a text message etc it seems to flash the notifications more often, after some time I believe it slows down a little. You can have the feature disabled at night, my ringer is silent from midnight to 9 am and my active notifications are disabled from 1 to 7 am. When disabled at night it only stops it from displaying on its own, if you move the phone it will still display the clock and any notifications.
LG Pulse with KitKat 4.4.2 same issue
I don't have a Moto X, I have the LG Pulse from Virgin Mobile Custom. My notifications do that, too! I have KitKat 4.4.2. I have never experienced this and I certainly would NOT make it a default nor intended action. Mine start out at the first notification + sounds, then 10 seconds later, 15 seconds later, 20 sec, 25 sec, etc. It is very annoying and there is no option in the system settings nor individual app settings to stop that behavior. I may just have to turn off notification sounds as this is ridiculous.
You can try setting the "sleep at night" option, and adjust the time to be on all the time (1am to 12am).
I believe this setting is supposed to suppress the breathing notifications. Though, it won't stop it from showing if you move the phone around... I know this cause my phone charges on my bed at night and when I roll around, it triggers AD, even though I have sleep mode on.
Hope it helps!
tapa'd on my moto x
Damn Tapatalk, won't let me edit..
tapa'd on my moto x
The sound is 4 progressively higher notes on a xylophone-like wooden or bamboo instrument. Usually plays on unlock, but also randomly throughout the day and night. My default notification sound is silence, so this might be tied to an app or the OS (MM 6.1). I just don't know what it is - other than loud and inconvenient. Any Ideas? This is driving me crazy and waking my wife at night. Thanks.
its an app, 100000%. now your job is to find out which one.
Hi and thanks for the confirmation Simms22. :good: I know. Kinda obvious.
I have gone through settings and turned off most radios thinking it could be tied to an app through BT, GPS, NFC, etc.; a successful connection or location fix. I have also gone through the various apps and checked their notification sound settings too. No dice. Whats worse is that I have gone through all my ringtones and notification sounds and can't find it.
It seems to be tied to the Google Now cards notifications, but if it is, I can't find it. I don't really want to turn those off but I guess that's next. Grrrr.
simms22 said:
its an app, 100000%. now your job is to find out which one.
Click to expand...
Click to collapse
ManagementCritic said:
Hi and thanks for the confirmation Simms22. :good: I know. Kinda obvious.
I have gone through settings and turned off most radios thinking it could be tied to an app through BT, GPS, NFC, etc.; a successful connection or location fix. I have also gone through the various apps and checked their notification sound settings too. No dice. Whats worse is that I have gone through all my ringtones and notification sounds and can't find it.
It seems to be tied to the Google Now cards notifications, but if it is, I can't find it. I don't really want to turn those off but I guess that's next. Grrrr.
Click to expand...
Click to collapse
id still be guessing, but google doesnt have a xylophone-like wooden or bamboo instrument sound on the nexus 6, so i know its not a default sound.
Thanks for the info. Hope I described the sound well enough. I'm mostly deaf in one ear and can't hear out of the other. Misspent youth and all that.
I know the notifications and ringtones I've added. That leaves apps that have brought their own sounds with their install. So it's back to the haystack.
I think I'll let it percolate in the sub-conscience for a while. Besides, I'm way behind on a personal Tasker project. Thanks again. I'll update later with what I find out.
simms22 said:
id still be guessing, but google doesnt have a xylophone-like wooden or bamboo instrument sound on the nexus 6, so i know its not a default sound.
Click to expand...
Click to collapse
ManagementCritic said:
Thanks for the info. Hope I described the sound well enough. I'm mostly deaf in one ear and can't hear out of the other. Misspent youth and all that.
I know the notifications and ringtones I've added. That leaves apps that have brought their own sounds with their install. So it's back to the haystack.
I think I'll let it percolate in the sub-conscience for a while. Besides, I'm way behind on a personal Tasker project. Thanks again. I'll update later with what I find out.
Click to expand...
Click to collapse
you can enable safe mode. that way you can check if its an app. long press the power button until you get the power off option. then long press on the power off until the safe mode option pops up. if that notification doesn't go off, then its an app. as on safe mode, all apps are disabled.
Flash another ROM. This happened to me on PureNex and when I switched to Chroma it went away.
Sometimes it actually happens once in a while. I'll hear the annoying "do dieu do doo" sound
Sent from my Nexus 6 using Tapatalk
I also have this problem. Has anybody found out the cause?
It started a few months ago and I ignored it, but now it is really annoying.
I put my phone into safe mode and it still happens. I assume this means it must be a preloaded app?
I installed a notification history app and nothing is listed when it happens!
Any help would be greatly appreciated!
I'm sure its something everyone has experienced, they hear their phone go off and check and nothing is there.
It happens to me every now and then, but It feels like its happening more frequently. Today I left my phone in another room and herd it go off twice but when I went to go check it was cleared. I know I herd it for sure, it was my Metal Gear ! Sound as well as my Ring Doorbell Sound.
Is there some kind of Notification Logger? Even if they are cleared.
To be honest, I have never had any issue as you describe
I had something similar, but some notifications would disappear after about 5 minutes or so. I had to turn off app power monitor in order for my notifications to stay. Although, I never had an issue with them disappearing instantly. I know also weather updates can make sounds, so that can also possibly be it. At the time before I found out about the app power monitor problem, I had installed an app called notisave and it would save every notification I would receive. Hope this helps.
I had similar, i downloaded an app called Notification History and it would show them, it was one weird app that did it but i don't recall exactly why or how.
there is also a phone setting that says "show most recent notifications only" make sure that's not on
I once disabled google assist or whatever it's called and it helped. After a few updates I abled it again. Seems some of their updates does this.
This isn't very easy to describe, but I've noticed this "bug" for a while. I managed to workaround it by not updating the Phone app (as it appears the bug was introduced with the 24th Feb 2021 update for the Phone app). However, with the April (whole phone) software update, it's forced the Phone app to also update to a newer version which has this bug.
I'd be grateful if someone could see if they can reproduce this bug as follows:
-Ensure you are using the built-in Samsung Phone app as default
-Ensure the version of your Phone app is at least "12.1.10.28" (my current version is "12.1.10.41")
-Ensure your phone is off charger
-Ensure your phone is in standby for at least 1 minute (and ensure it's not being woken up during this period due to receiving messages or other notifications)
-Call the phone, and don't pick-up. Once the phone is "ringing", you can hang up
-Observe that no missed call notification is shown on the AOD or the lockscreen - this is the bug
-Wake the phone and get to the homescreen - you'll now see the missed call notification pop up at the top. If you put the phone back in standby, you'll also now notice the notification on AOD and the lockscreen
I can reproduce this bug following a factory reset, and also in Safe mode. Therefore, I'm thinking this should be a universal bug, but I'm hoping at least one other person can reproduce this. I've tried searching in other forums/threads but no one seems to be reporting this. I'd have thought this would be extremely widespread and many would have noticed this by now, hence why I'm posting to ask. Thanks in advance to anyone who tries to reproduce this.
Couple of observations/clarifications from the original post:
-If the phone isn't in standby for at least around 1 minute, then all works fine and the missed call notification shows up on AOD and lockscreen
-If the phone is charging, there is also no issue
-Phone app with older version numbers to above have no issue
-As described in the original post, navigating to the homescreen following a missed call appears to "trigger" the notification to display
Given all the above, it makes me wonder if something is putting the "Missed call" notification mechanism to "sleep". I suspect the only hope is for the Phone app to update to correct this bug.
i tick all the above boxes and i can confirm there is no missed call icon on the AOD, there is only a missed call notification on the notification bar
matty100147 said:
i tick all the above boxes and i can confirm there is no missed call icon on the AOD, there is only a missed call notification on the notification bar
Click to expand...
Click to collapse
Thanks for trying and confirming the issue for AOD! Can you also confirm it doesn't show up on the lockscreen?
Yes, once you enter into the phone and on the homescreen, the missed call notification shows up on the notification bar (as if entering the homescreen is required to trigger the notification). From there (as long as you don't clear the notification), the notification then displays as it should everywhere else (including on the AOD and lockscreen).
By the way, can you please report the exact version number of your Phone app?
By the way, I managed to get someone else on Android Central forums to reproduce this, and he's using a Snapdragon US version. So it's almost certainly a universal bug.