| 87d14a1756f2ff4abdc107de35d06739245a606e |
|
15-Nov-2011 |
Jake Hamby <jhamby@google.com> |
Fix 3GPP SMS send failure for 7-bit national language tables.
Fix a NullPointerException when sending a single-part SMS containing
characters in one of the enabled national language tables.
Also added a few log messages for several error cases to help with
debugging any future problems in the SMS dispatcher.
Bug: 5553544
Change-Id: I61c1cbe297b2e222027f0db7c833df6a03c2974a
/frameworks/base/telephony/java/com/android/internal/telephony/SmsHeader.java
|
| 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/com/android/internal/telephony/SmsHeader.java
|
| 550885d158f5371cb207228eb1b7fb06aac32ea3 |
|
22-May-2009 |
Tammo Spalink <tammo@google.com> |
added SmsMessage ConcatRef parsing validation
addresses bugs:
http://b/issue?id=1870607
http://b/issue?id=1688238
and prior perforce commit:
http://s9/?change_num=136189
/frameworks/base/telephony/java/com/android/internal/telephony/SmsHeader.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/com/android/internal/telephony/SmsHeader.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/com/android/internal/telephony/SmsHeader.java
|