[Motorola Droid 4] Septfox:
Yea, I saw the comments. It's neat that a fix for us also helped those few who carry around BT keyboards.

Here're some things I tried, and the fun things that happened as a result

Copying a ringtone from the SD card folder, copying it back. This made it show up (figured it would because of the forced media refresh), but still didn't work properly (changes in Ring volume still played the default system sound)

Copying a ringtone - Rasalas - to my computer, checked for extra metadata. Nothing but the Loop flag. Edited it a bit, sent it to the SD card. Result was the same as above

Corrected permissions on the above ringtone to 644; no change

Changed the permissions on the SD ringtones folder to match those on the system's folder. This caused the preview when changing volume to stop working completely

I decided to reboot to fix the preview. The boot back up was very long. Once booted, System and Play Services both came up as not responding. The phone ran like complete garbage for about 5 minutes, then seemed to settle down. CoolTool - I have this up constantly now, out of curiosity - displayed android.process.media and sdcard as the heaviest users of the CPU during this. Fair enough, media scanning on boot and all, it just doesn't generally run so terribly while it's doing it.

Next, I went to the Play store to poke around at some CM12 themes. At this point, I started having trouble. During and for a minute or so after each install, "loop98" - something I haven't noticed popping up until now - started capping the CPU out and making the store run quite poorly.

Downloaded three themes, backed out, opened up the theme chooser. Hit the button to apply a theme: once again, loop98 capped the CPU out, to the point of making the phone completely unresponsive for several minutes. The only way I could tell that it wasn't hardlocked was that CoolTool was occasionally refreshing. It did eventually apply, however, and the phone once again calmed down. Backed out, tried applying another theme, and once again, loop98.

At this point I was pretty sick of this crap, and pulled the battery. Booted back up perfectly fine, can apply themes fine, phone is running alright. However, I'm now noticing loop98 occasionally popping up as the primary CPU user. So it's nice that I've apparently touched on a bug somewhere and created an ongoing problem.

Fake edit: while writing further down in the post, I picked up my phone to check something. Took its sweet time waking, unlocked it, instant soft-freeze with loop98 and system_server taking turns trying to burn the CPU up. Awesome. Have since rebooted, renamed the ringtones folder to something else, rebooted again, and the problem seems to have cleared up.

So, uh, I guess the moral of the story is...don't try things. Ever. That's all : \

Maybe it's OOM settings that are set a bit too aggressively, prompting garbage collection that cleans out the list's thumbnails, which then need to be created again --- causing a huge delay before it pops. Or not, I have no idea how the recent apps list does its thing.

Following writing the above, I had the idea of forcing a low-memory condition by opening several pages in UC Browser. Managed to get available memory down in the red, tried to pop Recent Apps: it came up in a second. So much for that theory.

Putting ringtones directly into the system folder has been common practice for me since 2.2...it just makes sense to me that they be where they can most readily be accessed. And indeed, it was perfectly fine prior to 5.0 so long as the file permissions were set right.

That said, I wouldn't recommend trying it again. I was messing with it in an earlier build and managed to get the phone to not recognize anything in there, even after removing the extras I had placed, necessitating a reflash.

I've had my wifi drop like this exactly once. There didn't seem to be any reason for it, I wasn't doing anything special at the time, it just...randomly dropped and forgot the network.

CoolTool seems to work adequately, and as I wrote above, can display CPU utilization and the process currently using the most, among other things. Like MekaByte posted, though, it unfortunately doesn't display I/O, which would be helpful.

Try flashing joojoobee's modified kernel posted further up in the thread, it removes the 600/800mhz steps, seems to help a bit.

Whew. That was a post and a half.