1

I have been using Samsung Galaxy s4 stock firmware up until now. Yesterday I switched to AOKP 4.4.4 (18/10/2014 build) and I've noticed that none of my old ringtones work (12 unrelated ringtones). I tried converting some of them to ogg, mp3 and wav formats with audacity. Whatever i do, they do not appear in ringtone list when moved to system/media/audio/ringtones. They cannot be selected with ES explorer - I get "Wrong file type, please select again" message. If I select them with root explorer the ringtone is set to "None".

Some mp3 files in my music library work, but not the ringtones.

I assume it has something to do with ringtone format, however, I have got no idea where to start looking.

Is there any setting I could change or an app I could change / install to add the compatibility? Is there any particular app responsible for sound playback in android?

EDIT: I am running AOKP on Samsung Galaxy S4.

EDIT2: I recently installed latest official firmware. During instalation I tried resetting to phone default firmware and ringtones worked. Now that I am on new official firmware, old ringtones do not work again. Also, On the new FW I used official ringtone selection tool (that creates a ringtone file). The ringtone created works in ringtone selector list, but cannot be added to list if removed from the list or if moved.

This leads me to believe problem is with some update all newer firmwares (including AOKP) have.

No real answer to this question, I am forced to use a 3rd party app to use my old ringtones.

Improve this question
1

3 Answers 3

Reset to default
1

In my OnePlus 2 running OxygenOS 2.2 (Android 5.1.1) the problem was solved by removing .nomedia in the root of the SD card, copying the audio folder from the media folder to the root of the SD, and then moving it back to the media folder. Don't ask me why but it worked again.

Improve this answer
1
  • Uh.....I can't believe something like that worked, but it did.
    – Zero
    Commented Jan 29, 2016 at 20:34
2

It's weird that your ringtones are still incompatible after conversion to the Ogg Vorbis format, because it (as you probably already know) is what Android's native ringtones come in.

Since you mentioned that you put your files in /system/media/audio/ringtones, it is worth a try to check and set the permissions of your files. It's as easy as

chmod 0644 /system/media/audio/ringtones/*

in a terminal emulator or through ADB.

If you want, you can also put your ringtone files in /sdcard/media/ringtones and do a reboot. You should be able to see, preview, and set your ringtones in Settings. (This works with regular MP3 files, as I've tested months before.)

P.S. Since you also said you've tried using Audacity, it's worth noting that Android doesn't repeat custom ringtones when they stop playing (as is the expected behaviour with call ringtones) unless you include a tag named ANDROID_LOOP set to true in the ringtone's metadata.

Improve this answer
1
  • No it's not permissions, originally, I saved the ringtones to SD card and made sure that permissions are set after it failed the first time.
    – Zero
    Commented Oct 27, 2014 at 5:36
-2

I dont know why it works, but re-namimg a file from *.mp3 to *.wav makes the file work as a ringtone.

If you then rename it back to *.mp3, it still works.

No idea why.

Improve this answer
1
  • Renaming .mp3 to .wav worked for me! Thanks for advice
    – Aleks Shindje
    Commented Feb 22, 2021 at 14:05

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .