Notification Sounds Keep Reverting to Verizon Tone

Troy Stephens

New member
Mar 25, 2016
1
0
0
I have the Samsung S7 Edge. I keep setting it to a custom notification sound and it will stay that way for a period of time, but eventually it will automatically revert back to the stock Verizon tone. Any ideas on how to fix this?

Except for this issue, I love this phone. The battery is FAR superior to the S6 and the display is terrific.
 
Are the custom tones ones you added to the phone? If so, did you put them on the SD card, or on the phone's storage? I've had the problem you describe when I tried to use sound files that were on the SD card.
 
I have a similar issue on a Galaxy S7. Apps will show the list of sounds available AND I can choose the new stock (Samsung) sound but there is no "OK" button to commit the change. The only way "out" is either the Back button or the Back arrow (in the upper left corner of the page). Apparently, the apps think you are cancelling your change.

I suspect this is a change in Marshmallow because "Settings > Sounds and vibration > Notification sound > Default notification sound" shows the same sound chooser (w/o an "OK" button) but seems to honor your change even using the Back button or Back arrow to close the list of sounds. At least from Settings, the sound choice seems to work like a Mac/iPhone where your change is instantaneous, there is no "CANCEL" option. If you want to cancel your change, you must change it back to the original value. Weird that this doesn't seem to be a widespread design change but is fairly localized.

If this is a Marshmallow change, lots of apps will need to be updated to support it. To date I know Twitter and Today Calendar cannot change notification sounds.
 
I have the Samsung Galaxy S7 (not the Edge) and have the identical problem with the Verizon Message+ app for SMS and MMS. Message+ allows the customization of a notification ringtone in the app itself, but it doesn't stick, and reverts to whatever the system default notification sound is set to after a day or so. I can also cause it to revert immediately by just opening the app's settings (no need to change anything). I think it's a bug in Message+.

My solution is not to use Message+. I've just been using the stock Android messaging app, which gets its notification sound from the system's messaging sound setting (Settings->Sounds and vibration->Notification sound->Messages notifications).

Note that the Message+ app does not revert to the "Messages notifications" sound, but to the "Default notifications" sound. If it used the specific "Messages" sound, it would have been OK. As it is, Message+ unusable for me.
 
I have this problem only when applying a new theme. Every time I change a theme, one of my notification sounds will revert back to default. I have changed themes so much that it has now become routine for me to go into the "sounds and notifications" settings after I apply a new theme. All good after that.
 
Solved - Setting and keeping custom ringtones.
This worked for me and continues to do so.
Make sure tone is saved in ringtones in device storage.
Go to settings/sound and vibration/ringtone.
Select your custom sound.
DO NOT exit anything, do an immediate restart (might have to use about 3 fingers to do so).
Ringtone is saved, also works for message tone, email, whatsapp etc.(though they're saved in
notification sounds. Prior to this they all reverted back to default.
One further note, after restart I noticed that the custom tone is duplicated by the phone
so maybe it adapts my .mp3 file in some way
 
the thread was started with the notification sound problem..and not the set custome sound issue.
THE PROBLEM IS NOT SOLVED
Notification Sounds Keep Reverting to Verizon Tone - Android Forums at AndroidCentral.com
here i think it is discribed pretty well..
it is 2017 and i haven't found any working solution yet..
what i tried was reinsatlling totally..phone and whaatsapp twice..
leaving out the sd card.. no effect..
asking whaatsapp...they are working on it.. so they say..
aplying data sync app..no change
it has to be an comunication error between marsmallow and whaatsapp
HEEEEEELP