History log of /frameworks/base/telephony/java/android/telephony/SmsMessage.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
141da403c0ad2d06b8f55e737ddf5d9e2b64c536 02-Nov-2011 bi4004.lee <bi4004.lee@samsung.com> Fix exception when sending multi-page SMS with Turkish characters.

- Precondition: config_sms_enabled_single_shift_tables is configured as
1 (Turkish) in frameworks/base/core/res/res/values/config.xml

- Cause: There is no consideration for National Language Shift Tables in
SmsMessage::fragmentText function.

- Solution: The header length is calculated properly according to
National Language Shift Table

- modified to add test cases and fix calculation bug (jhamby@google.com)

Bug: 5553544
Change-Id: I9eaefbbd6b3d75f8c41cbf9d0cb03a701cfa1cb3
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
b7945cae5ad0feaad09378d0db77f2b3105e5235 22-Sep-2011 Jake Hamby <jhamby@google.com> Enable support for multiple SMSDispatchers in CDMALTEPhone.

Refactor framework to support multiple SMSDispatcher objects on
dual-mode devices that require support for both 3GPP and 3GPP2
format SMS messages. Each dispatcher registers to receive events for
the appropriate message format.

Note: All applications which handle incoming SMS messages by processing the
SMS_RECEIVED_ACTION broadcast intent MUST pass the "format" extra from the intent
into the new createPdu() method in android.telephony.SmsMessage that takes an
extra format parameter. This is required in order to correctly decode the PDU on
devices which require support for both 3GPP and 3GPP2 formats at the same time,
such as CDMA/LTE devices and GSM/CDMA world phones.

- moved code to manage device storage events from SMSDispatcher to a
new class, SmsStorageMonitor, which is shared among all dispatchers.

- moved code to monitor per-application outgoing SMS usage from
SMSDispatcher.SmsCounter to a new class, SmsUsageMonitor, which
is shared among all dispatchers.

- fixed a bug that prevented CDMALTEPhone from setting the MCC/MNC
operator numeric value in the telephony provider from the UICC,
as GSMPhone does, when the SIM records have loaded.

Change-Id: I2789ac07b6ca2948138bca7f75481f9b31514f20
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
ee60f3fb1b4e61ac8027293a658ba710e36d36b6 11-May-2011 Jake Hamby <jhamby@google.com> resolved conflicts for merge of 18cc814c to honeycomb-plus-aosp

Change-Id: I2b569ada3baec2dc486296623063bc2b504c5e96
b49a73dfc4c9817bba1f227e9330555acdf9b56f 16-Mar-2011 Jake Hamby <jhamby@google.com> Enable support for SMS national language shift tables.

Add support for encoding and decoding SMS 7 bit user data using the
national language shift tables defined in 3GPP TS 23.038 (GSM/UMTS only),
including the new tables added in Release 9 for Indic languages.

Decoding is always supported, but encoding is only enabled for the
specific language tables added to the new integer array resources
"config_sms_enabled_single_shift_tables" and
"config_sms_enabled_locking_shift_tables" defined in
frameworks/base/core/res/res/values/config.xml. The default empty arrays
should be overridden in an OEM overlay for the specific nationalities where
SMS national language shift table encoding is allowed/mandated (e.g. Turkey).
GsmAlphabet.countGsmSeptets() will try to find the most efficient encoding
among all combinations of enabled locking shift and single shift tables.
If no 7 bit encoding is possible, 16 bit UCS-2 encoding will be used.

This change also fixes a bug in the decoder: when an escape septet
is followed by a septet with no entry in the extension (single shift)
table, TS 23.038 Table 6.2.1.1 states that the MS shall display
the character in the main GSM 7 bit default alphabet table, or the
active national language locking shift table. Previously, we were
decoding this sequence as a space character. Two consecutive escape
septets will continue to decode as a space character, according to
Note 1 of table 6.2.1.1.

Change-Id: I4dab3f0ffe39f3df2064ed93c9c05f26e274d18b
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
1938e314e34fb11ec5398716dfe9704cea66e31e 02-Feb-2011 Wink Saville <wink@google.com> Have SmsMessage use getCurrentPhoneType

Although our first tablet doesn't support SMS messages there are testing
scenarios where they can be used. To preserve proper behavior now that
getPhoneType can return PHONE_TYPE_NONE use getCurrentPhoneType.

bug: 3198435
Change-Id: I48ef294f563351c66971b4e89e6dcb3326b0ae92
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
b55df4471ed55a0e91dee79304f3b1209ffa4b35 05-Aug-2010 Sang-il, Lee <gendoh@google.com> Support MBCS characters in contacts and SMS messages that are stored in SIM cards.

Change-Id: I0438c5748a47512fc2a0e4b89ac85e30e3f5c6de
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
145ff609de3206b585819ef974fab20cdc2d9f5e 16-Apr-2010 Jake Hamby <jhamby@google.com> Spelling corrections and other minor cosmetic cleanups.

- Fixed a bunch of typos in comments (plus a few variable names)
- Removed unused import lines from telephony classes
- Added @Override attribute to overriding methods
- Made SmsMessage.PduParser inner class private & deleted unused constructor
- Added type specifiers to declarations of ArrayList and HashMap
- SimulatedCommands.getRegistrationState() had an ArrayIndexOutOfBoundsException
trying to write to index 14 of a 14-element array. I removed the
out-of-bounds assignment.

Change-Id: I054b5156aa64ab6639028d5b45a7e688b2deee08
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
633dfb6da6d70cb369797b42df4bf046fdb3a07f 19-Mar-2010 Jake Hamby <jhamby@google.com> Fix some typos and logging of calls to CDMA methods.

Fixed some comment typos and cleaned up logging of unexpected calls to
CDMA-specific methods on a non-CDMA device.

Change-Id: Ia6e5fba765122cbf3186fd9fecca7a3931a76dcc
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
72fac6778119e42f39e00f5b7e36b7500893f45c 22-Oct-2009 Tom Taylor <tomtaylor@google.com> Handle bad SIM message

When trying to view the saved sms messages on my SIM, I ran into a null ref.
With this fix, we don't try and wrap a null message, but just skip it.
This is part one of three fixes for BC-triaged bug 2205782.

Change-Id: Ie7105dae7e3134b98681deabcc14f5db555902f3
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
1f952a178db86559ff4bab79c4a9b5fae18096bf 25-Aug-2009 Tammo Spalink <tammo@google.com> Move SMS pdu creation fully into the central Phone process.

Previously pdu creation was haphazardly done sometimes by the app and
sometimes centrally by the phone process -- specifically the phone
process did creation for multipart texts. This change gets rid of the
previous IPC interface for sending raw pdus to SMSDispatch in the
phone process, and instead makes everything work like multipart
messages worked before, namely the structured data is passed and pdu
encoding done centrally.

The motivation for this was the need to ensure that CDMA message id
numbers were strictly monotonic, including across reboots, which
necessitated central state in the form of a system property, which
could in turn only be modified by the phone process.

Hence, this (in part) addresses issue: http://buganizer/issue?id=2075760

Change-Id: I94ca207b6e657c465e8472534704db8646ee277c
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
95434bfaee62161ce02012c6424f0c0c8fffccb5 28-Aug-2009 Tammo Spalink <tammo@google.com> Allow fragmentText to be called for singleton CDMA messages.

Corrects for previous partner changes, addressing issue:

http://buganizer/issue?id=2063332

Change-Id: I49e564d81c5db3e92a6bad973f21a02a7302875d
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
0da3bdb476086db02a1076780676b21e239c79d6 28-Jul-2009 Jaikumar Ganesh <jaikumar@google.com> Fix public API caused due to CDMA changes.
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
5e5b8c45dbb87be5468821ed298747ab065d73a6 27-Jul-2009 Tammo Spalink <tammo@google.com> Fix swapped gsm/cdma function dispatch, and 7bit text fragmentation.
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
fc78f358cb1d1cee99758bcd6ef998a122ef27c9 11-Jun-2009 Tammo Spalink <tammo@google.com> for cdma concatenated (long) messages, replace ascii7bit with gsm7bit encoding
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
a94945d3a1cf23caf33759eb1de84195d3fcb37b 03-Jun-2009 Tammo Spalink <tammo@google.com> make sms calculateLength radio-independent
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
641bb3d8dfd72f57356d39ef00256d6077c9e235 27-May-2009 Tammo Spalink <tammo@google.com> expose (but still hide) sms user data headers

addresses bug http://b/issue?id=1751571
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
64c499113a758cf80cddfd4d0183f944a1a6645a 05-May-2009 Tammo Spalink <tammo@google.com> SmsHeader rewrite, in preparation for migration to public API.

See http://b/issue?id=1751571

Changes the semantics of SmsHeader from containing only opaque data
to exposing occurs-once frequently-used fields together with a list
of opaque fields. Also changes the coding to and from byte array to
be symmetrical, whereas previous encoding had an extra length field.

Cdma SmsMessage -- cleanup of code paths along with adjustments to
match the new header semantics, which should address at least some
of the issues with concatenated messages. See http://b/issue?id=1809759
/frameworks/base/telephony/java/android/telephony/SmsMessage.java
767a662ecde33c3979bf02b793d392aca0403162 02-Apr-2009 Wink Saville <> AI 144185: Integrate cdma into the main code base.

Automated import of CL 144185
/frameworks/base/telephony/java/android/telephony/SmsMessage.java