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/HttpUtils.java
|
0ecc26df09777835cfa8dbfd3c48ca7b7fa7f011 |
|
27-Mar-2012 |
Tom Taylor <tomtaylor@google.com> |
Use the new DRM scheme in MMS Bug 5158047 Change-Id: Id5d0ed03816b70c9f06b98af982cd5afb9af38d5
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
dd374f47c61f4fed8e6702c1f9d3f33ac5b77d02 |
|
15-Sep-2011 |
Tom Taylor <tomtaylor@google.com> |
maguro:mms: Patch for getting MMS from chuncked packets. - Description Orange FR sends MMS as chunked packets. Chunked packets mean that each packet didn't have its own size field within message header. But android allocates buffer for message body by size that is within message header. So, in case of Orange FR, MMS apk cannot get correct message body even though MMS is retreived on device because MMS apk doesn't know the real size of message. - Solution MMS retrieved is kept on http stack as dummy packet. MMS is checked if it is chunked or not before reading body size. If it is chunked, temporary buffer for message body is allocated as maxium size. And then, read the packet and fill that buffer until packet size is -1. (-1 means end of packet) Finaly, copy temporary buffer to MMS body as loaded size. Manually merge this change from yongsuk.kwon@samsung.com from the partner repo to master. Bug 5257517 Change-Id: Ic48259729cc7090b8afdc113ec3c6b47edff0ed9
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
472cecc82e384f0c81d2a7885ade3db702213d82 |
|
18-Aug-2011 |
Tom Taylor <tomtaylor@google.com> |
Unable to send MMS This doesn't fix the bug, but adds debugging that can be turned on without a recompilation to make tracking down this kind of bug easier the next time. Bug 5182797 Change-Id: Ia601afd6868b5dc4db202c849c35d17123ad833b
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
150c4179995cc0a75f934ef194372f9295957ca2 |
|
08-Apr-2011 |
Joe Onorato <joeo@google.com> |
Remove the deprecated things from Config.java. These havent been working since before 1.0. Change-Id: I7b60931012a68116b516acc8af8a7a8fdeab97c3
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
be53d0c18809a324f9f69d8a3c9a408d841eb964 |
|
03-Nov-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
am 4ef1d3e8: am 754b6b13: Merge "Add support for chunked encoding when downloading MMS PDUs" * commit '4ef1d3e87830995cb6973879622fc8aef8572105': Add support for chunked encoding when downloading MMS PDUs
|
208b7834ee01388a5fecacf00a9c1e1b8ffc5240 |
|
06-Oct-2010 |
Matthias Thomae <matthias.thomae@teleca.com> |
Add support for chunked encoding when downloading MMS PDUs Some networks use chunked encoding for MMS delivery, meaning that the content length is not known beforehand. The Android MMS application did not support chunked encoding, so downloading MMS on these networks would simply fail. The change adds chunked encoding functionality by reading data from the stream until EOF, instead of relying on the Content-Length HTTP header.
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
c122ca5ebd2ccac240002425a567718a9577568c |
|
23-Apr-2010 |
Tom Taylor <tomtaylor@google.com> |
Deprecated language codes leaked in HTTP_ACCEPT_LANGUAGE header Some old language codes, such as Hebrew (iw), were inserted in the HTTP_ACCEPT_LANGUAGE header. Fix the problem using the same strategy as in the browser code: replace deprecated language codes with the new ones. Added a unit test that tests for standard behavior and tests one of the deprecated languages. Bug 2600706. Change-Id: I5ac29618c9c7f5cbbafdb24c43367c983647eaa8
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
4d33cdcbb402a87ffeeaddb58237c70c4608c6f5 |
|
25-Feb-2010 |
Dianne Hackborn <hackbod@google.com> |
Update to reflect android-common no longer in framework.
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
9b668cfd54149b24855f2b8034e332b31e02ac73 |
|
18-Feb-2010 |
Tom Taylor <tomtaylor@google.com> |
am 4fda80cf: am 7a17eaed: Add better logging info Merge commit '4fda80cf3bc76bba51948d0260bffa485d0481a6' * commit '4fda80cf3bc76bba51948d0260bffa485d0481a6': Add better logging info
|
7a17eaedae4c54b72f420380ec7129a15442cbbc |
|
18-Feb-2010 |
Tom Taylor <tomtaylor@google.com> |
Add better logging info When trying to track down bug 2447913, chain the original exception and print out the url that we're trying to reach. Change-Id: I9bcb326e77bfdc95ad75eb0ba5c08aa8cc506a28
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
d62a959cf2e7d261e296f82831942a9a99320175 |
|
10-Feb-2010 |
Dan Egnor <egnor@google.com> |
Pass a Context to AndroidHttpClient.newInstance(), enabling persistent SSL session caching.
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
41f895e5147e7115d46a46657356f33b31251504 |
|
11-Dec-2009 |
Paul Westbrook <pwestbro@google.com> |
Changed class paths for classes moved in unbundling effort
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
1b37c93a3b67483ee9b0ad604a2e1e9d8aaa84d9 |
|
01-Dec-2009 |
Wei Huang <weih@google.com> |
bug: change default UA agent string for MMS. - add conditional logging for UAProf url. - if the MMS port isn't set, don't use Log.e() to log it. Change-Id: I9557763d209226eafb5cb3b0b7e4092287f5ef29
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
1a0ec0c1576cab49e02a1dab796ed2be33f0a0a5 |
|
03-Sep-2009 |
Wei Huang <weih@google.com> |
don't crash due to bad contact url. Change-Id: I826ca5e35f917e5afa0d7686b5e1ab4d85858a3b
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.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/HttpUtils.java
|
293000e15498b71a4986d7247e60fe8bdaa05a4b |
|
19-Aug-2009 |
Wei Huang <weih@google.com> |
fix an issue where our http socket timeout (20sec) is too aggressive for connecting to VZW mmsc, which could have up to 48 sec delay responding to a request. Make the MMS config socket timeout of 1 min (configurable by mms_config.xml). Also fix a bug where we write 8k extra of nothingness when saving to sdcard. - add getHttpSocketTimeout() to MmsConfig. Use in HttpUtils when creating a new AndroidHttpClient. - manually integrate a change from open source, fixing a bug where we write up to 8k of empty bytes to the end of the content when saving to sdcard. - also added logs to dump content type. - tweaked the log when we throw a MmsException when we can't get the duration of media content.
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
89e7af1acc0b62f2822ace8df6d56f4c6d37a40f |
|
20-Jun-2009 |
Christian Gustafsson <qmfd78@motorola.com> |
Additional customization options for mms http transport. Modified the MMS http transport and configuration to allow for more settings. This is needed for CDMA carriers. 1. UserAgent needs to be modifiable. Most MMSC on the CDMA side will use the user agent name as the device identification to invoke the right transcoder settings. 2. The tag name for the UAProfUrl is not the same for all carriers. Instead of "x-wap-profile" they might require "Profile". 3. There are additional http parameters required some with the users phone number. For example: x-up-calling-line-id: 15555550000 where 15555550000 would the users telephone number. Since these parameters vary wildly from carrier to carrier the code was written to be flexible. All additional parameters can be added to a single string in the mms_config.xml file. They are separated by '|'. The substitution string for the users phone number is also flexible to avoid a carrier parameter clash. Example: <string name="httpParams">x-up-calling-line-id: UserNumerGoesHere</string> <string name="httpParamsLine1Key">UserNumerGoesHere</string> If the users number happens to be 15555550000 then at runtime a x-up-calling-line-id: 15555550000 would appear in the http transactions with the MMSC. Additional parameters can be added: <string name="httpParams">x-up-calling-line-id:#LINE1#|x-iot-pass-date: 20001122</string> <string name="httpParamsLine1Key">#LINE1#</string> In this case two additional parameters would be added to the http transaction: x-up-calling-line-id: 15555550000 x-iot-pass-date: 20001122
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
86a1cf79bf92dbb2b9d09431379bff6de83c2581 |
|
19-May-2009 |
Tom Taylor <tomtaylor@google.com> |
Fix bug 1635579 - Make build system configure UAProf. Don't rely on GConfig anymore for various settings. Instead, grab them out of mms_config.xml.
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.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/HttpUtils.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/HttpUtils.java
|
0f236f55349f070ac94e12cca963847173393da8 |
|
18-Dec-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Code drop from //branches/cupcake/...@124589
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|
8eed706474910ccb978acda03e85d3261037da6e |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/packages/apps/Mms/src/com/android/mms/transaction/HttpUtils.java
|