Nice update again. Thanks for adding the suggestions I had.
There's been a few times when the app would force close. Each time it happened, it would be while an image is loading after you clicked on it. It happen a few times in the previous release. Though on v1.0-rc2, I've only had it happen once so far. Can't seem to reproduce it though. The image that made it force close would load fine after reopening the application again. I checked the log file with alogcat and this seemed to be the error for the force close. Some of it at least:
I/ActivityManager( 163): Displayed us.donmai.danbooru.danbo/.activity.SinglePostActivity: +126ms
D/dalvikvm(11009): GC_EXTERNAL_ALLOC freed 80K, 49% free 4151K/8007K, external 13492K/15284K, paused 98ms
E/dalvikvm-heap(11009): 25599364-byte external allocation too large for this process.
D/dalvikvm(11009): GC_FOR_MALLOC freed 0K, 49% free 4151K/8007K, external 13492K/15284K, paused 45ms
E/GraphicsJNI(11009): VM won't let us allocate 25599364 bytes
D/skia (11009): --- decoder->decode returned false
W/dalvikvm(11009): threadid=12: thread exiting with uncaught exception (group=0x40175560)
E/WindowManager(11009): Activity us.donmai.danbooru.danbo.activity.SinglePostActivity has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@4083bad0 that was originally added here
E/WindowManager(11009): android.view.WindowLeaked: Activity us.donmai.danbooru.danbo.activity.SinglePostActivity has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@4083bad0 that was originally added here
Don't know if this is helpful or not. I can send you the rest of the log file if you want as well. Let me know.
