You set a custom ringtone. It works. Then one day your phone rings and — there it is again, the default tone you thought you'd replaced weeks ago. Did Android reset it? Did an update undo your setting? Or did you imagine the whole thing?
Probably none of those. What feels like "my ringtone keeps changing back" is usually one of five much more boring explanations, and they all look identical from the outside. The trick is figuring out which one you have before you start changing settings at random. Because changing five settings at once and having the problem "go away" teaches you nothing — and it usually comes back.
First: identify which call is actually affected
An incoming mobile call, a call from one saved contact, and a call inside an app can all use different sound controls. Before changing several settings at once, run one clean experiment: ask a second phone to call your number twice — once from a saved contact, and once from another number that isn't in your contacts.
Then note two things separately. Did the Phone ringtone setting itself change, or did the phone merely play a different sound? That distinction prevents a long list of random fixes. If the setting still shows your custom tone but a certain call played something else, the setting didn't reset — something overrode it for that call. If the setting itself reverted to the default, that's a different problem entirely.
1. Confirm the selected audio file still exists
Open the phone's Files app and play the MP3 from local storage. If the downloaded file was moved, deleted, or stored in a temporary location, select it again from a stable folder. A ringtone setting that points at a file that no longer exists will quietly fall back to the default — and from your side, it looks exactly like Android "resetting" your choice.
On Pixel, Google's sound settings documentation explicitly describes using the Ringtones folder for MP3 files transferred from a computer. On Galaxy, Samsung's ringtone guide shows the add-file control in the sound picker. Either way, the principle is the same: put the file somewhere permanent, then point the setting at it.
If the file no longer plays, download it again from its original page, then set it as the phone ringtone and run a test call. Keep only media you have the right to use. And this time, leave the file where you put it — moving ringtones around after setting them is the single most common cause of this whole problem.
2. Check contact-specific overrides
If only one person's calls sound different, open that contact's ringtone setting. A saved per-contact choice can override the general phone ringtone, and it will keep doing so no matter how many times you change the default. Google documents this in its Pixel help page, and our per-contact ringtone guide walks through the distinction.
This is also the explanation when "my ringtone changed back" turns out to be "my mum's calls play the old tone." Your default is fine. Mum has her own tone, set months ago and long forgotten. Check the contact, not the system setting.
3. Separate volume and sound mode from file selection
A ringtone can remain selected while Ring & notification volume is low or the phone is set to vibrate or mute. In that case the phone isn't playing the wrong sound — it's playing your sound too quietly to notice, or not playing it at all, and your brain fills in the gap with "it must have reset."
Change the sound mode and test a call. Check Bluetooth or another connected output if the sound seems to come from the wrong device — a ringtone playing through a forgotten Bluetooth speaker in another room sounds a lot like a ringtone that isn't playing. A silent phone is not proof that Android reset the selected file.
4. Check the calling app
WhatsApp and some other calling apps have their own notification or call sound settings. If regular cellular calls use your choice but an app call does not, inspect that app's settings. Samsung calls this distinction out in its ringtone troubleshooting. Avoid changing the system ringtone to fix an app-only symptom — you'll break the calls that were working to fix the one that wasn't.
This one catches people out because the calls look the same. An incoming WhatsApp call fills the screen like a normal call, but it's governed by WhatsApp's sound settings, not your system ringtone. If WhatsApp calls always play the same tone regardless of your system setting, that's expected behaviour, not a reset.
5. Re-select once, then test properly
Choose a built-in tone temporarily and save it. Return to your desired local MP3, save, and test with a real incoming call. The round trip — away from your custom tone and back — forces the setting to re-save cleanly, which clears up cases where the selection was half-stored or pointing at a stale file reference.
If the setting still changes after a restart, stop guessing and gather facts. Write down the phone model, Android version, exact file path, and whether it affects every caller or just some. Those details make manufacturer support actually useful. "My ringtone resets" gets you a generic checklist. "Galaxy S24, One UI 6.1, MP3 in Internal storage/Ringtones, reverts after every restart, affects all callers" gets you a real answer.
Do not factory-reset your device for an unconfirmed ringtone issue. A factory reset is a day of restoring backups, re-logging into everything, and re-setting up the phone — all for a problem that is almost always a moved file or a contact override. It's the last resort, not the first one.
Where to look next
If the file never appears in the picker, follow downloaded ringtone not showing. If the selected sound exists but calls remain silent, use Android ringtone not working. This guide is a diagnostic sequence; it does not claim one cause applies to every Android device.