There's an uncaught exception that is wrecking havoc (or, less dramatically, semi-randomly causing the dreaded Force Close dialog) among many Paperdroid installations. It seems to affect some G1s as well as many Droids; unfortunately my data on the matter is scarce.
In an effort to solve the mystery, I published Paperdroid 1.0.2 - which, besides a minor bug fix, didn't have any new features but for an attempt in getting these errors properly logged.
Now, after some days in which I had unrelated events to take care of, it is clear that the attempt failed miseramente - I'm getting exactly nothing.


However the priority is still to solve this bug; I'll try to fix the reporting issue and, it is hoped, will push an update tomorrow.
Anyway, if you are experiencing random crashes (or, on Paperdroid 1.0.2, probably the Application Not Responding dialog) and you know how to get a logcat, by all means send me the stacktrace (this requires 1.0.1, however). The
future of the universe
solution to this bug is in your hands!
But - do not despair. I'm confident I'll get to solve this thing soon, thanks to the efforts of the many people trying to help me out (I can't thank you guys enough) - then I'll be finally full-on putting new features in Paperdroid and, especially, Paperdroid Pro.