| 4cab16e396f9f5381e14121011d55a7c12e3c317 |
|
06-Apr-2012 |
Tom Taylor <tomtaylor@google.com> |
Empty forward draft not removed
Bug 6222154
A number of problems to fix for this relatively innocent looking bug.
First, the PDU was getting persisted on the UI thread. Second, persisting
a PDU automatically creates a thread, but on the forwarded message side,
the thread id wasn't getting set. Since the thread id was zero, the
working message code didn't think there was any draft to delete.
Change-Id: I3021b864bdf9876eb8c66e4048295516b085406f
/packages/apps/Mms/src/com/android/mms/ui/AsyncDialog.java
|
| 661957caeb3110ae3328a995edd467ceedc07a36 |
|
05-Apr-2012 |
Tom Taylor <tomtaylor@google.com> |
ANR on the Messaging application, when editing the attachment
Bug 5973755
When slideshows are involved, there's the possibility of an ANR because
the slideshow is saved on the UI thread. With this change, the heavy-duty-
disk-writing work is done in a background thread. If the task takes longer
than a half second, a modal progress dialog is displayed. The various
target activities, such as SlideEditorActivity and SlideshowEditActivity,
still read/save the PDU on the UI thread. They should use the PduLoaderManager.
A separate bug has been filed.
Change-Id: I384968d406fe10e192abf1614e3ce0b27f20c93d
/packages/apps/Mms/src/com/android/mms/ui/AsyncDialog.java
|