| d64419030e1fec1e751695dab3bd7236e2fb0214 |
|
02-Aug-2012 |
Roger Chen <cxr514033970@gmail.com> |
Clean and format all imported packages
Change-Id: I2e45f5ba1d56b9b17314a8b0f4c0fc1a5d8fc4d9
Signed-off-by: Roger Chen <cxr514033970@gmail.com>
/packages/apps/Mms/src/com/android/mms/transaction/SmsSingleRecipientSender.java
|
| 758276fd1342cb573f9fb6bcff7ce427b2f411d0 |
|
20-Jan-2012 |
Tom Taylor <tomtaylor@google.com> |
[Crespo-S] Message not able to be sent to a Korean number with a plus code in front (i.e. +82...)
Bug 5800721
Remove separators from numbers before passing them to the SmsManager.
For numbers like "+8211-111-1111", Sprint will send back an SMS saying
the destination is invalid. By removing the separators ("-"), the number
sends fine.
Change-Id: I890a5c25063288e0527a468b65bcc26b00b57892
/packages/apps/Mms/src/com/android/mms/transaction/SmsSingleRecipientSender.java
|
| e3c2e38196432b2858f67b269feef4cc067773c2 |
|
29-Nov-2011 |
Tom Taylor <tomtaylor@google.com> |
maguro] Modification for Buganizer issue No. 5509903
- Description: When sending multi-pages SMS, delivery report is received several times.
- Solution: In order to receive just one delivery report, PendingIntent for
MessageStatusReceiver is added to deliveryIntents if it is the last page.
Merged from master
Change-Id: Idd7217c2432f71baddaa33c58ddd4e7c2c5446a5
/packages/apps/Mms/src/com/android/mms/transaction/SmsSingleRecipientSender.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/transaction/SmsSingleRecipientSender.java
|
| 0d2c0042be90f42635e3bc301f2a2e37460e6344 |
|
12-Aug-2011 |
Tom Taylor <tomtaylor@google.com> |
Add more debug log code for message not sent
Turning on for a day or two to capture some log info. Now printing out
the error code returned in the intent from the SmsManager. Bug 5144439
Change-Id: I687b030810dfff9d42a47f8908a8173fa43af8e9
/packages/apps/Mms/src/com/android/mms/transaction/SmsSingleRecipientSender.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/transaction/SmsSingleRecipientSender.java
|
| 3234c38f1f1cc34324edaab2b2308ab2fffd08dc |
|
26-Jul-2010 |
Banavathu, Srinivas Naik <snb@codeaurora.org> |
Mms: Fix for sending long SMS to multiple recipients
When a long SMS is sent to multiple recipients, it is sent only to the first
recipient. MMS app checks extra EXTRA_MESSAGE_SENT_SEND_NEXT for true before
sending SMS to other recipients. Since same pending intent is used for all
fragments, this is never true. Fixed this issue by using differnet pending
intent for last fragment with extra EXTRA_MESSAGE_SENT_SEND_NEXT set to true.
Change-Id: I9f61274e0f20698544090419a85e0e6b8daff3e0
/packages/apps/Mms/src/com/android/mms/transaction/SmsSingleRecipientSender.java
|
| f7e8281a223af6228e6399055a6197a1edd9bc3a |
|
09-Mar-2010 |
Tom Taylor <tomtaylor@google.com> |
Remove mms-common
Get rid of the mms-common library and move the mms files back into the
framework where they originally came from.
Change-Id: I8ce2b0a2a3cfc6b7da13ce0e791173c09dd8f0f5
/packages/apps/Mms/src/com/android/mms/transaction/SmsSingleRecipientSender.java
|
| 4020be563f457ed2251b43928f14770246c886a2 |
|
11-Feb-2010 |
Tom Taylor <tomtaylor@google.com> |
Fix double display of outgoing messages
Prior to this fix, sending an SMS message would put the message
in the SMS table marked as pending. As the message was pulled off the queue
to be sent, a duplicate message was added to the SMS table and marked
as "outbox". Then the pending message was deleted out of the same table.
Meanwhile, the UI responded to these DB changes and momentarily flashed
two copies of the outgoing message in the ComposeMessageActivity. With
this change, we only keep a single copy of the message in the SMS table and
simple change the column value from pending to outbox. The result is a
lot less DB churn and a much smoother UI when sending an SMS. Tested with
short SMS messages and long, multi-part messages.
Change-Id: Iaad4f7a9732d79786b50aa19428f51bfec002d4a
/packages/apps/Mms/src/com/android/mms/transaction/SmsSingleRecipientSender.java
|
| fd644551e8506266aad2b76463b51b44154ed62f |
|
29-Jan-2010 |
Tom Taylor <tomtaylor@google.com> |
Update refs now that MMS is removed
Move MMS to mms-common library. Update imports.
Change-Id: I28fa24a68c27977eba58cb62f2667596d3abe2c4
/packages/apps/Mms/src/com/android/mms/transaction/SmsSingleRecipientSender.java
|
| 52b0fc717011d84dd25c1e88998eaae97c8161a8 |
|
13-Jan-2010 |
Bai Tao <michaelbai@google.com> |
Sending message one by one
/packages/apps/Mms/src/com/android/mms/transaction/SmsSingleRecipientSender.java
|