JUMP TO SOLUTION Solved

Original topic:

Notification Sound/Vibration For Apps Not Working.

(Topic created: 05-17-2025 07:38 PM)
659 Views
Jezreel
Asteroid
Options
Galaxy S21
Is it just me or is the galaxy S21 Series notification sound & vibration for apps not working since the One UI7 update? Because mine is not working for some reason. I restarted it about three times it's not working i've diagnosed it with the members app, says everything is fine, all sensors are working. Is anyone else having the same issue? Can anyone help me?

1 Solution


Accepted Solutions
Solution
Jezreel
Asteroid
Options
Galaxy S21
Thank you for the help. Fortunately, I didn't have to do all those steps. It seemed to be a temporary software issue it fixed by itself.

View solution in context

6 Replies
LongHiker
Galactic Samsung Care Ambassador
Options
Galaxy S21
Is your volume off or at to zero?
0 Likes
Reply
Jezreel
Asteroid
Options
Galaxy S21
All my volumes are at 100
0 Likes
Reply
LongHiker
Galactic Samsung Care Ambassador
Options
Galaxy S21
Do you have Do Not Disturb enabled?
0 Likes
Reply
Jezreel
Asteroid
Options
Galaxy S21
No
0 Likes
Reply
LongHiker
Galactic Samsung Care Ambassador
Options
Galaxy S21

@Jezreel Did you wipe the device cache partition after the update? I recommend that you do this after every device update. It wipes out incompatible or outdated cache information which might be incompatible after the update. It does not erase any user data nor applications.

To wipe the device cache partition:

1. Power off your device.
2. Power up while holding down the Volume up key and the Side key until the Samsung logo appears. 
3. An Android recovery menu will appear.
4. Use the Volume down key to scroll down to Wipe cache partition.
5. Click the side key to select it.
6. Use the Volume down key to scroll down to Yes. 
7. Click the side key to select it. The Cache will be wiped almost instantaneously. 
8. Click the side key to select "Reboot system now" 

Solution
Jezreel
Asteroid
Options
Galaxy S21
Thank you for the help. Fortunately, I didn't have to do all those steps. It seemed to be a temporary software issue it fixed by itself.