I also agree with some that while the new ROM work is probably cool and much appreciated (as is the old ROM work!); however, I've have put a LOT of time and effort into setting my phone up the way I like it and if this ringer problem would get resolved, I'd be pretty frak'n happy (for now
![Smile](http://forum.ppcgeeks.com/images/smilies/icon_smile.gif)
).
Ok, I'm going to
attempt to sum up the ringer issue.
Please make corrections/comments!
Possible causes:
- BT related: Negatory -- several have stated they don't use BT at all.
- TouchLockPro: No -- same reason.
- ROM: Yes -- Doesn't ever happen with stock ROM (unless a custom ROM wasn't properly "purged"), only modified ROMs
- wma: Yes -- only happens with wma files?. .wav's never cause a problem. When the problem ocurrs, the Sound app defaults back to sound #1 which is .wav. The 1st 8 default files are .wav
- TF3D or WM Dialer: Unknown, but using WM Dialer seems to get rid of a 3 sec ring delay, which is kind of a ringer related bug. I'm using TF3D Dialer.
- ActiveSync: Possibly -- I seem to have the problem shortly after disconnecting from AS. Not sure if it's when I unplug, or if I get a call (or sms) while it's updating or what. Still trying to make it happen intentionally.
Fixes:
- Soft reset fixes it every time. No other fix has been observed when trying to use default sounds in default location: .wma's in \Windows\Rings
- Convert active .wma's to .wav's. Recomnended to leave them in \Windows\Rings for proper function while connected to ActiveSync.
Other:
- I've read of possible conflict playing Sounds because of a file association issue with a media player. That is, the player is associated (or not associated, not sure which way causes an issue) with .wma's and somehow screws up the notifcation app or something.