| e3070ede55652bb00618eadfac9daee64320569f |
|
18-Mar-2017 |
Jack Yu <jackyu@google.com> |
Added ETWS primary message default message support
ETWS primary message does not contain messagy body. We used
to use hardcoded "ETWS" as the body, which is not easy for
end users to understand what happened. Added the built-in
default messages provided by Japanese government guideline
for earthquake, Tsunami, test, and other channels support to
enhance the user experience.
Test: manual
bug: 33595007
Change-Id: I53659298d8ce3b3ba5c751c14c1b36e76d6dc562
/frameworks/base/telephony/java/com/android/internal/telephony/gsm/GsmSmsCbMessage.java
|
| 4980bf4aff8d49ac4e05444a6ef40ea1536f1afb |
|
14-Feb-2017 |
Dan Willemsen <dwillemsen@google.com> |
Merge branch 'stage-telephony-refactor' into master
Bug: 33644781
Change-Id: If571e3ad9432035811714e3a92d9dfff39311c61
/frameworks/base/telephony/java/com/android/internal/telephony/gsm/GsmSmsCbMessage.java
|
| a639b311e93ad14d9ee5c2b2c215ed2d86c32d2a |
|
10-Jul-2012 |
Wink Saville <wink@google.com> |
Create telephony-common and mms-common
These have been created to reduce the size and complexity
of frameworks/base.
mms-common was created by moving all of
frameworks/base/core/java/com/google/android/mms
to:
frameworks/opt/mms
telephony-common was created by moving some of
frameworks/base/telephony
to:
frameworks/opt/telephony
Change-Id: If6cb3c6ff952767fc10210f923dc0e4b343cd4ad
/frameworks/base/telephony/java/com/android/internal/telephony/gsm/GsmSmsCbMessage.java
|
| 3e3c3f80a90b156ff500076f8655647dfb317acf |
|
06-Feb-2012 |
Jake Hamby <jhamby@google.com> |
Add support for CMAS warning notifications over CDMA.
Refactor SMS Cell Broadcast support to enable receiving CMAS warning
notifications over CDMA. The CellBroadcastReceiver app must also be
updated with the corresponding change. All cell broadcasts are now
delivered as a Parcelable SmsCbMessage object in the "message" extra
of the SMS_CB_RECEIVED_ACTION or SMS_EMERGENCY_CB_RECEIVED_ACTION,
instead of as a GSM/UMTS "pdu" byte array.
Existing functionality for ETWS and CMAS alerts over GSM/UMTS continues
to be supported using the new radio-technology independent SmsCbMessage
and related objects. Test cases are added to verify that valid and
invalid broadcast data is handled appropriately.
Unit testing discovered a bug in the BitwiseOutputStream utility class
used by the added test cases. When the BitwiseOutputStream object must be
expanded (in the private possExpand() method), the mEnd field is not
updated to the new array size. This causes a new array to be allocated
on every new write, and for all data beyond the original array allocation
to be replaced with zeroes. Fixed by adding a line to possExpand() to
update mEnd. Added a test case to BitwiseStreamsTest to verify the fix.
Besides the test cases, BitwiseOutputStream is only used by BearerData in
two places, both of which allocate a sufficient initial buffer. So the
bug in BitwiseOutputStream is not critical to fix for normal operation,
but should be fixed so that the test cases using it function correctly.
Bug: 5856308
Change-Id: I201ecbf11607fd200aaae3cbb32561efabf65672
/frameworks/base/telephony/java/com/android/internal/telephony/gsm/GsmSmsCbMessage.java
|
| efba344b5a7b20e400daf5f41b2fbd688337f789 |
|
29-Feb-2012 |
Jake Hamby <jhamby@google.com> |
Revert "Add support for CMAS warning notifications over CDMA." I'll submit again when the app change is ready.
This reverts commit 0c49f03a0429b5c0c4a619256f7bca86a4997ae8
/frameworks/base/telephony/java/com/android/internal/telephony/gsm/GsmSmsCbMessage.java
|
| 0c49f03a0429b5c0c4a619256f7bca86a4997ae8 |
|
06-Feb-2012 |
Jake Hamby <jhamby@google.com> |
Add support for CMAS warning notifications over CDMA.
Refactor SMS Cell Broadcast support to enable receiving CMAS warning
notifications over CDMA. The CellBroadcastReceiver app must also be
updated with the corresponding change. All cell broadcasts are now
delivered as a Parcelable SmsCbMessage object in the "message" extra
of the SMS_CB_RECEIVED_ACTION or SMS_EMERGENCY_CB_RECEIVED_ACTION,
instead of as a GSM/UMTS "pdu" byte array.
Existing functionality for ETWS and CMAS alerts over GSM/UMTS continues
to be supported using the new radio-technology independent SmsCbMessage
and related objects. Test cases are added to verify that valid and
invalid broadcast data is handled appropriately.
Unit testing discovered a bug in the BitwiseOutputStream utility class
used by the added test cases. When the BitwiseOutputStream object must be
expanded (in the private possExpand() method), the mEnd field is not
updated to the new array size. This causes a new array to be allocated
on every new write, and for all data beyond the original array allocation
to be replaced with zeroes. Fixed by adding a line to possExpand() to
update mEnd. Added a test case to BitwiseStreamsTest to verify the fix.
Besides the test cases, BitwiseOutputStream is only used by BearerData in
two places, both of which allocate a sufficient initial buffer. So the
bug in BitwiseOutputStream is not critical to fix for normal operation,
but should be fixed so that the test cases using it function correctly.
Bug: 5856308
Change-Id: Ie3e6af747976ce9b8a3e71e76fec71709cf86545
/frameworks/base/telephony/java/com/android/internal/telephony/gsm/GsmSmsCbMessage.java
|