| 7a063cb79843369325645ce059ec0f4676e0ca83 |
|
25-Oct-2011 |
Tom Taylor <tomtaylor@google.com> |
Turn off database log dumps
Bug 5512341
If we run into a recipient inconsistency while sending, log it but don't
dump the user's database into the log. Use a direct method when printing
out the db. The nice LogTag functions use format and if any of the strings
have format characters, this causes a crash.
Change-Id: I597c1b7ac72b346b3b8b3b05843132c243c6fd6d
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| b736686638eca62aa89cb15184711ef38413cb3e |
|
28-Sep-2011 |
Tom Taylor <tomtaylor@google.com> |
SMS messages being delivered to wrong contact
Bug 5319828
Last ditch escape hatch at detecting an sms being sent to a wrong
contact. From what we've seen of a database where sending to the wrong
contact had taken place, the in-memory Conversation cache had the
correct threadId, but the wrong recipient. With this change, we do
two checks to verify that the recipients for a particular thread match
the recipients associated with the thread in the database.
Change-Id: I8f7c194243e6da093461c1aaae4119f05390582d
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| 9935944b16d3651f5e95a67a1884f0a14acf1d6c |
|
20-Sep-2011 |
Tom Taylor <tomtaylor@google.com> |
Need to turn off warning dialog in Factory ROM build
Bug 5343269
Change-Id: I0e71d73a950837821908fa3dbdd324ea4dfbe83e
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| a0bda6a838d0c9bff996aa39d4f9750faa00adda |
|
12-Sep-2011 |
Tom Taylor <tomtaylor@google.com> |
Add some debug code for double send
On reboot, one particular user reports that an old message gets resent.
Add debug logging code to print out when a message gets sent and when
the successful send confirmation comes back (where we move the message
from the outbox to the sent box). This code also gets triggered by
onBootCompleted, where the bug seems to manifest itself. Bug 5172594
Change-Id: Ic42fa877418c438a83186e249463566358a3e825
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| b3217a6ddcd9455968de7078bfbc0a901b4ff705 |
|
16-Aug-2011 |
Tom Taylor <tomtaylor@google.com> |
Merge debugging messages and tools to master
Merge the newly added debugging messages and database dump tools from
gingerbread into master. Bug 5133439
Change-Id: I191960a79c7dc60f7e5f731ab952f06c5c9383c4
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| 0856dec418d9838e09b1609439279e248355e0c4 |
|
16-Aug-2011 |
Tom Taylor <tomtaylor@google.com> |
Turn off send sms debugging
Add a simple debug function at the choke point so the next time
the telephony layer reports an error from the RIL, we'll print out
the error. Bug 5164371
Change-Id: Idb4b588e3e956248f429311361795b49ec2c9b70
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| c33ee154b6fd872439fd24a073f947339bbe4d22 |
|
11-Aug-2011 |
Tom Taylor <tomtaylor@google.com> |
Add debug log code for message not sent
Turning on for a day or two to capture some log info.
Bug 5144439
Change-Id: Icbbf8a4a0e485fb1ed49d7977220e7258b886a14
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| 72ab3ecfa3556866ee51b822f8ce5b1f2f117545 |
|
05-Jan-2011 |
Tom Taylor <tomtaylor@google.com> |
Merge changes from gingerbread
Manually merge some of the gingerbread changes that didn't get auto-merged
back into master.
Change-Id: Ibfea8d1317f16717e5cb3f2ea1ec6c16a9ab9b83
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| 63e1e43eba8a1c47bf6895055046bc126e70c38b |
|
05-Jan-2011 |
Wei Huang <weih@google.com> |
am 048de832: am 94263ffe: bug #3057952: remove and turn off verbose logging done for this bug.
* commit '048de8327650c65e9e0df591f13a9d4870528fd8':
bug #3057952: remove and turn off verbose logging done for this bug.
|
| 94263ffe93fedcbd2ce3a8fffe44e36a3b0acebd |
|
05-Jan-2011 |
Wei Huang <weih@google.com> |
bug #3057952: remove and turn off verbose logging done for this bug.
Change-Id: I85c14abfccb35d3d4f9c80cba14642f5cb2fb1fc
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| 9337760339d7d3a1cace8a2acfc2df7e50219a89 |
|
03-Jan-2011 |
Wei Huang <weih@google.com> |
Merge commit 'f9466d4b' into manualmerge
Conflicts:
src/com/android/mms/data/WorkingMessage.java
src/com/android/mms/ui/ComposeMessageActivity.java
Change-Id: If66a2c8d1573c09fc47b94c56915c916720a607c
|
| 858d59e9f4b0839ee014e52e0744ea910d9830ff |
|
03-Jan-2011 |
Wei Huang <weih@google.com> |
bug #3057952: add bunch more debugging info to catch this bug.
Change-Id: I3ea9bd19adcf177697536cc56ab079957f863463
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| 56ee740f49cde993ef8de79c30b4da7c14dc76ad |
|
23-Oct-2010 |
Jason Chen <jasonchen@google.com> |
resolved conflicts for merge of 77dc8fc2 to master
Change-Id: I11ea6cc31d316f200ac1ea3bec8247176fd5ff28
|
| 8543b9ffab4a6fba08af8ece77573c7ec5dc6974 |
|
23-Oct-2010 |
Tom Taylor <tomtaylor@google.com> |
Turn off messaging app's SEVERE_WARNING
Bug 3062274
Change-Id: I100914f4f31bf74c2cc79e784f38cd0fc33143d1
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| 4d72768e5f149a6bcd40604d1e2741795cc86ebf |
|
18-Oct-2010 |
Tom Taylor <tomtaylor@google.com> |
Prepare for turning off extensive logging
Bug 3062274
Change-Id: I02dbc06b6502d8f50ba7bb2dca367623364adc40
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| b6e4518a7b3740e48fd03f3803cc8696f15bbcc7 |
|
05-Oct-2010 |
Tom Taylor <tomtaylor@google.com> |
Add debugging code
Add a number of tests to try and track down the situation that causes
a message to be sent to the wrong recipient. Bug 3057952
Change-Id: I2da3e91dcb039e87c3222e48026b859d1644793e
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| 09a75ac1d3710e60dbe78ead3dee6863ffb380ca |
|
08-Apr-2010 |
Wei Huang <weih@google.com> |
bug #2438230: more logging for Conversation and Recipient cache.
- add more logging to try to catch the mismatching contact/thread bug.
- add selective checking to make sure thread id and recipients are not compromised.
Change-Id: I038dca4f7b32bf822ef68e344c7a6eaf8990e328
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| d62ef06699b3ca5048c5642bd50300e9a2eb04a1 |
|
23-Sep-2009 |
Tom Taylor <tomtaylor@google.com> |
Fix draft bug
Fix a special case of working on a draft and then getting a new intent for that same
draft. Recognize we've got the same conversation rather than trying to save the draft
and reload the same draft. Add more logging to Conversation and WorkingMessage and move
the common logging code into LogTag.
Change-Id: I1388967f3f2e7520e08730036243f958574a6001
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| 32a1dcecca6ed0881431555a4218d0282814326c |
|
27-Aug-2009 |
Wink Saville <wink@google.com> |
temporary fix for bug 1892808. If the SMS address is a short code addr, don't feed it to PhoneNumberUtils.compare() as that doesn't handle short phone numbers.
- if the SMS address is shorter than 6 digits, just do a straight string comparison now. SMS short codes don't usually have the separater characters like "(.- ", or the prefix '+'.
- when updating the contact cache, don't spin up one thread per contact. Do all the contacts update in a single thread.
- add a unit test for comparing SMS phone numbers and short codes. Disabled ConversationaListTest, it seems to get stuck for a long long time.
Change-Id: I9fca4734c235466671ff72d144842bbbb0d7dda9
/packages/apps/Mms/src/com/android/mms/LogTag.java
|
| 812391ad832f3fdac054ad3a50af563da16e99b5 |
|
25-Aug-2009 |
Wei Huang <weih@google.com> |
Add onNewIntent() to ComposeMessageActivity, and add the launchmode="singleTop" to AndroidManifest.xml. Just specifying the intent flag Intent.FLAG_ACTIVITY_SINGLE_TOP doesn't make the activity single top.
(cc: Dianne only for the activity launch mode flags in AndroidManifest.xml)
- the singletop launch mode is needed for the case when we receive a new message notification for the same contact that's on CMA already. If CMA has a MMS draft on screen (but not saved to db yet), not going thru. onNewIntent() would cause the following bad sequence.
- onCreate() would load any draft saved in db, but in this case there isn't draft saved in db yet because we only save draft in CMA.onStop(). So loadDraft() would load the empty draft.
- onStop() on the old CMA activity would now save the in-memory MMS draft to db.
- the new CMA lost the MMS draft that's there before clicking on the notification. But resulting db has the MMS draft, which is now orphaned and not associated with the conversation. From here on out, entering and exiting the CMA for this conversation would not see the MMS draft, but it's there in the part table in db. VERY BAD!
so with onNewIntent(), we can check if the new intent's recipient is the same as the old one, and skip the whole shenanigan.
- add debug logging for draft cache. Changed the log tag for draft cache to "Mms:draft", and CMA to "Mms:compose".
- guard against null cursor returned from Contacts query. Contacts is very flaky right now, and I am getting a null cursor from it all the time.
- reorg logging. Add new LogTag class. Log MMS app logs using "Mms:app" and transaction logs using "Mms:transaction".
Change-Id: I5e12c87ab378ff9b6ff326e136598f64bd423129
/packages/apps/Mms/src/com/android/mms/LogTag.java
|