[Android Central Question]

I've created a sound in a .wav file I want as my notification. Plays fine on my laptop. But after uploading it to the device through Bluetooth, moving it into the Notifications folder and then changing the settings it plays some other notification sound, as if what I select is actually pointing to one of the default sound files.

I've tried it three times naming it three different things and keep getting the same result. Help!

[B. Diddy]

Welcome to Android Central! Which phone? When you select that custom tone in your Settings>Sounds menu, does it play a sample for you, and if so, is it the correct sample?

[drewturney]

It's a Samsung Galaxy S7 Edge. I upload the file and use File manager to put it in the Notifications folder. Then when I go to Mesages>Settings>Notifications>General notifications or New Messages and select the file I uploaded it plays one of the generic/default tones.

[B. Diddy]

Is the /Notifications directory on Internal Storage or the SD card?

[drewturney]

This is in the internal storage - haven't installed an SD card yet

[B. Diddy]

Try wiping the cache partition: https://support.t-mobile.com/docs/DOC-28028

[drewturney]

That's done, re-uploaded the sound file, moved into 'Notifications' folder, same problem.

[B. Diddy]

Is there any way to convert the file into mp3, or create it that way? wav should work, but I'm just wondering if there's something weird with the file format.

[drewturney]

That worked! You're a genius, thank you so much. The other weird effect was that when I went to the settings screen in notifications to select a new one, the current notification selected was a number, not the name of the file. That didn't happen this time, so seems it was a file format issue. Thanks a lot again.

[B. Diddy]

Great! I wonder if Android dropped wav support recently? I was under the impression you could use mp3, wav, or ogg files for notifications. Or maybe it's a Samsung thing?