| ab845dee6565a8dfc384186bc8f2e801a2b087e1 |
|
07-Jun-2014 |
Ye Wen <ywen@google.com> |
Use unified log tag for Mms app
Change-Id: Icec182674c008c2b9d01a6010a2aafc8111b2b7e
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 27d7d33be4f9bf3a9d4beac97117ca56c5b37913 |
|
04-Sep-2013 |
Tom Taylor <tomtaylor@google.com> |
am a9713710: Merge "The messaging app needs to look at getMobileDataEnabled" into klp-dev
* commit 'a9713710c474b02d396a68dbd4e98b52e7739f22':
The messaging app needs to look at getMobileDataEnabled
|
| ed022ca79d681650142b1a89dcd76d38603fa9b8 |
|
04-Sep-2013 |
Tom Taylor <tomtaylor@google.com> |
The messaging app needs to look at getMobileDataEnabled
10456183 - Messaging app is deemed responsible for 20-30% of the battery drain
If the user has turned off Mobile network settings->Data enabled, then
it's impossible to download an mms. However, the TransactionService would
keep on trying to get the connection manager to switch to the mms mobile
state, hence the strong grip on the wakelock. With this change, consider
the phone as not connected if data is disabled.
Change-Id: Ie4b359bb3e05472f187d79bf42dbb43f21eb31f3
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 2b0602347baae5c20189cc7f4df5eb04bbf1d801 |
|
15-Aug-2013 |
Jianzheng Zhou <jianzheng.zhou@freescale.com> |
Fix one NPE in Mms app
For tablet we usually declare not support mobile_* networkAttributes but ethernet,
wifi,bt in config.xml. this will trigger this NPE.
Change-Id: I761c8514f5569bef1242f9fddc321c0aed564d9e
Signed-off-by: Jianzheng Zhou <jianzheng.zhou@freescale.com>
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 087ef9de80082cd001e75c15e1f93cc65d50ed27 |
|
19-Mar-2013 |
Roger Chen <cxr514033970@gmail.com> |
Process inactive msgs if Mms app is relaunched
Try to process all pending transations and queued smses
which maybe killed by user, OOM or Mms crashing and so on
after Mms app is (re)launched.
Since for Mms: Mms app only will retry failed transaction(
must be marked as failed) due to network issue or any known
reason, and for sms: Mms app only rely on SmsDispatcher to
retry to send at most 3 times.
Change-Id: Ifc46d1a86bf33342590313c29d6d4c0aff7c739f
Signed-off-by: Roger Chen <cxr514033970@gmail.com>
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| e90d18fb3e32c77a08708f1473331f269a5ee932 |
|
04-Feb-2013 |
Roger Chen <cxr514033970@gmail.com> |
Enhance Mms connectivity tracker workflow
1. Fix Bug 1691499 by a more appoperiate broadcast
and revert 82f5492b211f51e71c7089eb7779384ff03c0d89.
Broadcast CONNECTIVITY_ACTION is more low-frequencyer
and aproprater than ACTION_ANY_DATA_CONNECTION_STATE_CHANGED.
Root cause of Bug# 1691499 is receiving a high-frequencyer
broatcast and not adding a apropriate filter.
2. Reduce useless duration between hanging up and processing Mmes.
Check mms connectivity is available before retried to connect.
3. Using getNetworkInfo instead of the deprecated one
4. Remove useless codes and make ConnectivityBroadcastReceiver
more readable.
Change-Id: I994d3cccead1e43865c42a24e20021321e140686
Signed-off-by: Roger Chen <cxr514033970@gmail.com>
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 5e508afc2cb9a889de49a52d1b6dfe1238fb4630 |
|
31-Jan-2013 |
Tom Taylor <tomtaylor@google.com> |
Merge "Wake up TransactService when MMS data is available"
|
| 7a1b0328f6a6a6b0225f1392507cccff78f3cbd0 |
|
28-Jan-2013 |
Bin Li <libin@marvell.com> |
Wake up TransactService when MMS data is available
In 2G network, mobile data is suspend during voice
call. MMS data will be notified as unavailable.
After voice call is end, It may notify Default data
connection before MMS data connection. When it
notify Default connection, it is unavailable in
MMS networkInfo and TransactionService will not
launch transaction; When it nofity MMS connection,
it is not connected so it will not wake up
Transaction Service.
How to reproduce:
1) Make a voice call in 2G network;
2) Try to send a MMS during voice call;
3) MMS is sending and waiting for data connection;
4) Hang up the voice call;
5) MMS stays in Sending state.
Change-Id: Ia719e8736cc6ccfcd236bceea4cb94f7c4dd94e5
Signed-off-by: Bin Li <libin@marvell.com>
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 356a950de55b4e9c9867ca255bc7291d87b19802 |
|
15-Jan-2013 |
Roger Chen <cxr514033970@gmail.com> |
Continue to transact pending Mms once after boot completed
Change-Id: Id0cc24fdd1eaf985681c12c34303e854a8d83ce2
Signed-off-by: Roger Chen <cxr514033970@gmail.com>
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 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/MmsSystemEventReceiver.java
|
| 09fb57c41102b5e10beb7081f203d5b5ed8fa71e |
|
01-Jul-2012 |
Wink Saville <wink@google.com> |
Use telephony-common and mms-common - DO NOT MERGE
Change-Id: I37581d9f85ed1d10e33370eafcce3260f7a36fa1
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 7b6fe946f2e1020432e3600c8863f72449cd4e68 |
|
16-May-2012 |
Tom Taylor <tomtaylor@google.com> |
Old thumbnail shown
Bug 6490001
DO NOT MERGE
hen a message is deleted, remove the uri from the pdu cache and clear the
thumbnail cache. When a thread is deleted, clear both the pdu and thumbnail
caches.
Change-Id: I361d48fe5430cbf9885656e2fe91ee2f566a25b9
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| c8d727902ff6976c45285a12aab176545a7848bb |
|
28-Feb-2012 |
Todor Kalaydjiev <todor@google.com> |
Play sound at half-volume and don't show notification for new msgs in current thread
bug: 5928707
Change-Id: I6954f8f1700daa7d4bca971f72da55d153ab5d39
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 3b21f6ab04db5936d73e9f53032f1587389380ff |
|
22-Mar-2010 |
Tom Taylor <tomtaylor@google.com> |
Fix DB query on the UI thread
Move a notification query on the UI thread to a worker thread.
Any calls from UI threads (which includes receivers) are made
nonblocking. Calls from non-UI threads (which includes services)
are blocking. Tested various scenarios and checked threads in the
debugger. Bug 2524765 and bug 2533501.
Change-Id: I38213b7202957bdb103058b657be04bfe6b085dc
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.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/MmsSystemEventReceiver.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/MmsSystemEventReceiver.java
|
| 6be18bedb5b87dbbcdb54f37d5a0945bd0f71377 |
|
17-Dec-2009 |
Tom Taylor <tomtaylor@google.com> |
Unbundling work
This is the first step in unbundling the Mms app. Some of the changes include:
- moving some of the Mms code from the framework into the app itself.
- same with emoticons
- remove dependency on internal drawables and add local copy to mms
- some dependencies on various internal classes now moved to android-common library
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.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/transaction/MmsSystemEventReceiver.java
|
| 82f5492b211f51e71c7089eb7779384ff03c0d89 |
|
15-Jun-2009 |
Tom Taylor <tomtaylor@google.com> |
Fix bug 1691499: MMS constantly stopping.
What was happening was MmsSystemEventReceiver was registered for any connection
state changes in the AndroidManifest. On a connection state change, MmsSystemEventReceiver
would startup the TransactionService. The TransactionService would check its queue and if
there wasn't anything to do, would stop itself. Apparently on the MV campus, there exists
a situation that causes the phone to switch between connections, causing the CONNECTION
STATE CHANGED intent to be sent out frequently and hence, lots of starting and stopping of
the TransactionService even when it has nothing to do. With this change, the MmsSystemEventReceiver
no longer registers for that intent in the AndroidManifest. That event receiver is still
needed in the manifest because it registers for boot completed events. Meanwhile, the TransactionService
keeps another MmsSystemEventReceiver. When the TransactionService has a transaction to
process, but there's no connectivity, it enables the MmsSystemEventReceiver to
listen for connectivity changes. Whenever the TransactionService completes its work, it
unregisters the MmsSystemEventReceiver so it no longer responds to connection changes.
I added test code to TransactionService so I could simulate no connection and test that
the MmsSystemEventReceiver registers for connection changes and then appropriately starts
up the TransactionService. I left the test code in place, but it is disabled.
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 5d2d0046ada7b53205e537d8675d32a8785e8d1d |
|
19-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake_rel/...@140373
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 72735c62aba8fd2a9420a0f9f83d22543e3c164f |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 892f2c5bf965b1431ae107b602444a93f4aad4a3 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|
| 8eed706474910ccb978acda03e85d3261037da6e |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/packages/apps/Mms/src/com/android/mms/transaction/MmsSystemEventReceiver.java
|