[Verizon Droid Incredible 2] RegnierD:
A couple observations that I've noticed:

1 I have definitely had widgets freeze up and just stop working. Either Force Stopping Trebuchet or opening Trebuchet Setting and then backing out usually helps, but, sometimes, I have to re-add the widget.

2. Is GPS still a little wonky? When I enabled mine for the first necessary time on ICS today, it locked me in North Carolina for about twenty mnutes, and I'm in Worthington, OH. O.o Rebooting with GPS on seems to have fixed it.

3. A BIG note on the rom setup (and keep in mind this has been done with 4ext Touch Recovery): I've noticed (after flashing this thing so many times) that if you have all your partitions formatted as ext4 (I.E., coming from a rom like MikRunny where it's set up like that), all of your partitions will remain as ext4. When flashing from an ext3 rom (based off stock, most other roms, etc) it formats the system partition as ext4, but leaves data and cache in ext3.

The difference in speed between then two is very apparent for me and, believe it or not, the ext4/system ext3/data and ext3/cache setup is the most responsive. I even went into 4ext Touch Recovery to manually switch back and forth between data+cache as ext3/4 several times to confirm this, and I can tell the difference every time. Just a heads up for people that may be experiencing issues: check how your partitions are set up.

Also, for anyone that is interested, I pinpointed the root (haha) of my issues the past week-ish: My phone forgot it was S-Off somehow. Everythong was still rooted (because I was flashing rooted roms) and the bootloader functions still worked like S-Off (like fastboot recovery flashing), but roms couldn't actually make those same system level changes that were important. I figured this out when I went to update my SU binary through the SU app in this rom, and it said I wasn't S-Off. I tried several other roms and got the same error.

Now, this happens sometimes when you OC too high and your phone gets hot and locks up, which it did, once, about a week and a half ago (this happened to me multiple times on my OG DInc, which wouldn't OC past 1.08 mhz :P). Unfortunately, the only way to fix this for us (because of how Revolutionary unlocks and then overrides bootloader writing through fastboot/hboot) is to RUU back to Froyo (if anybody even knows what that is anymore, lol) via PG32IMG.zip, then run SuperOneClick to gain root, follow a string of ADB commands to flash the original 0.97.0000_336906 hboot, then RUU back to 2.3.3 via PG32IMG.zip, and then run Revolutionary again to get S-Off. The difficult thing about this, is that all the guides for this have links hosted by MultiUpload, and all the mirrors have gone dark. So, you have to extract that hboot .nb0 file from the Froyo RUU .zip. Sound confusing enough? Lol

The point being, this is why OC-ing is dangerous, and why we (I) need to be careful when doing so. I got lucky, and was able to fix the rather minimal corruption, but I (or some other unfortunate SuperUser carelessly playing with the processor) may not be so lucky next time if something goes wrong again because of playing too much with OC. I learned my lesson, that's for damn sure. XD LOL

Just a PSA, for other people that may run into issues like this down the road.