After inheriting a Droid X on Oct 23rd, rooting it with D3 Easy Root, and installing Droid 2 Bootstrapper, I was able to tie it to the same Google account as my LG Ally (of course it still has its original phone number with Verizon), and as such import access to my Google calendar. I turned off the Ally.
All my 10 daily repeating alarms and several single-instance alarms were working fine.
Then came the last Sunday in October (the traditional DST change date before our past illustrious leader arbitrarily changed it). Since then, I have had NO END of failed alarms, alarms sounding at the WRONG TIME, etc. But mostly just not sounding at ALL.
I've tried everything that worked in the past to fix an issue like this (which has history for me all the way back into the Palm OS). When nothing worked, I started some online sleuthing. Last night's Google of "Android Calendar Alarm Fail" got 1,000,50 returns. The first page leads mostly to the Verizon and Motorola forums, where I read endless accounts of the same nightmare I am experiencing. Everyone seems to feel their problems all began when Motorola released the Gingerbread update. Those who have downgraded back to Froyo claim the problems go away.
So, it does appear that Motorola somehow borked the Droid X calendar notification system with GB.
I am currently seeking some stepwise information on how to take my Droid X back to Froyo. If anyone can help me, please let me know. I am familiar with putting Velocity on the LG Ally, and of course rooting the Droid X as mentioned. Beyond that I don't yet know what to do to make this happen.