rldunn
03-19-2003, 07:53 AM
OK, this has happened to me twice now, so I wanted to share here. After moving apps into Flash that required Flash to be compacted, I've had issues with alarms for apps moved to Flash not going off; instead, the device freezes and requires a soft reset.
For example, I had Clock+ in flash, which is my alarm clock. Last night I moved some OTHER apps to and from Flash, and as part of the process, Flash compacted. This morning, my alarm didn't go off and my Clie froze. This doesn't happen everytime Flash gets compacted; I've only noticed it once before with DiddleBug.
So does this mean that alarm apps shouldn't go in Flash? No, I wouldn't say so, but you should be aware of the issue. Once we get our systems stable where we're not adding to Flash, it shouldn't be an issue. But when you do move apps, you might want to make a point of going to your Flash alarm apps and run them once after the move, which should take care of the problem. I believe what's going on is that the alarm DB loses it's link to the actual app if it gets moved to a different spot in Flash during the compacting process.
For example, I had Clock+ in flash, which is my alarm clock. Last night I moved some OTHER apps to and from Flash, and as part of the process, Flash compacted. This morning, my alarm didn't go off and my Clie froze. This doesn't happen everytime Flash gets compacted; I've only noticed it once before with DiddleBug.
So does this mean that alarm apps shouldn't go in Flash? No, I wouldn't say so, but you should be aware of the issue. Once we get our systems stable where we're not adding to Flash, it shouldn't be an issue. But when you do move apps, you might want to make a point of going to your Flash alarm apps and run them once after the move, which should take care of the problem. I believe what's going on is that the alarm DB loses it's link to the actual app if it gets moved to a different spot in Flash during the compacting process.