Ringtone Corruption Workaround (21501)
Hey all. Apologies if this is a known workaround, but I thought I would post what I found.
I was unable to find the root of the corruption issues, but using Total Commander, I realized that the only files that were affected were compressed files (.wma and .mp3).
I then copied all the compressed system sound files (several are .wav's already) and used winamp to convert them into .wav files. I then copied the new files back into /Windows.
Now even though the files have different extensions, Sounds and Notifications seems to pick whichever one it feels like if the rest of the filename is the same. So make sure the filename of the .wav files is a bit different (I added a "-1", e.g. Alarm1-1.wav). Now in Sounds and Notifications, ensure that all sounds chosen are .wav versions of the files. This may also be necessary for Alarms, although for me, the ONLY files that even show up are the .wav files (both original and added).
For ringtones, you may need to copy the default windows ringtones into a My Ringtones folder.
For custom ringtones, you will also need to convert to uncompressed wav audio, but you can delete the original compressed version to avoid duplicates in S&N. If you have full .mp3's I HIGHLY recommend trimming them before trying to convert to .wav and transferring them back. WAV files can be quite large.
Note, you can't delete the compressed system sound files since they are classified as part of the ROM. So in Souds and Notifications, you will still have the "corruptable" files, but so long as all the files chosen are the .wav variety, you should be okay.
I have tested this on PPCKitchen build 21501 for a couple of days. So far so good.
Default sound files are attached below. Extract to /Windows (may need to move default ringtone files to My Ringtones)
Last edited by qbunnie; 05-21-2009 at 09:50 AM.
Reason: Attached uncompressed system sound files
|