| 9e271688595d0281fe73acb16eb70925be9cf9b5 |
|
02-Aug-2016 |
Amit Mahajan <amitmahajan@google.com> |
Bind to service only after USER_UNLOCKED.
WapPushOverSms which starts before USER_UNLOCKED binds to
WapPushManager. However the service is not direct boot aware so
the bind fails.
Bug: 30007288
Change-Id: Ia436045c1538b89ec25049accff3c4ded69cfa92
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 98dabb4505f072a7997ded2a1db47748f5032485 |
|
05-Feb-2016 |
Amit Mahajan <amitmahajan@google.com> |
Unit test for WapPushOverSms
am: 60a81bdb47
* commit '60a81bdb47cf64972c8edf5b0c51e8059765e5a0':
Unit test for WapPushOverSms
|
| 60a81bdb47cf64972c8edf5b0c51e8059765e5a0 |
|
28-Jan-2016 |
Amit Mahajan <amitmahajan@google.com> |
Unit test for WapPushOverSms
Bug: 25691379
Change-Id: I26eebb8711c9369c5ab85e740254a86483125bf5
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 722b1b5403842bf0595ba8c11e7f01fdb9844518 |
|
04-Feb-2016 |
Abhijith Shastry <ashastry@google.com> |
Catch all PDU parsing errors so that the phone process does not crash on invalid PDU's.
BUG: 26918719
Change-Id: I6286d17b2e2bd9f6fd0cb18d0cfd217f1055eacf
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 72f7fc997b09204bf01ccaac34ac4b9bd91d954b |
|
27-Jan-2016 |
Ji Yang <yangji@google.com> |
Check wap push type before showing new message notification
Bug: 26232405
Change-Id: Id8dc622dd058856c70d20de0fe879711c3048a04
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| ba51280f53e677ac527b11bd9a5dfa819740f70a |
|
22-Jan-2016 |
Abhijith Shastry <ashastry@google.com> |
Block SMS, and MMS from blocked numbers.
BUG: 26682753
Change-Id: I464c04466d3a936d2d611cbaf791490340a9f515
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 1a87ab3d7170d618f048c4f5af8c7504a587aaa5 |
|
10-Dec-2015 |
Jack Yu <jackyu@google.com> |
Merge from master
Change-Id: Ifbd86600111d2c444031ff608fab62fb2ee4b236
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| ba798021d26fc3690a16a2c9b4f41f44a1122b49 |
|
13-Oct-2015 |
Amit Mahajan <amitmahajan@google.com> |
Require receivers of WAP_PUSH_RECEIVED to have MMS/WAP_PUSH permission
Earlier the permission was RECEIVE_SMS which was incorrect.
Bug: 24806190
Change-Id: I6805c7ccb2e5b30bfdf4914014de94db7b841539
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 65bd5856a33708f3b690dcb7703b7ce5acfd66e0 |
|
04-Sep-2015 |
Xiaohui Chen <xiaohuic@google.com> |
Cleanup USER_OWNER in telephony
Bug: 19913735
Bug: 23795305
Change-Id: Id52c4558c56d1006b975f27f65e061a623978b8f
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 25ba0c3660ef78bbdaf2f4db7b3e7a833c377ccb |
|
22-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #22612630: Ensure SMS/Call delivery during Doze
Place apps on whitelist when delivering SMS, like MMS.
Change-Id: Ied719152e84ba88cb2c224ed1669cb12c1412ee7
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 932f590aadc3cfac86cc3972db5eb7013f94780d |
|
14-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #21626564: MMS should be receivied while Dozing
Uses new APIs to put apps on the whitelist as needed.
Change-Id: I24bf0c00f2a7dca64590e7fc0dd6ec036e9bd2bf
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 032e0398ba2770edd52c543482afbae6f92ff29b |
|
17-Nov-2014 |
Ye Wen <ywen@google.com> |
PduParser MSIM support (2/4)
PduParser needs to know if Content-Disposition part header is supported
for a specific carrier. Originally this is loaded directly from system
resource in PduParser. This won't work for multi-SIM, which requires
getting that config based on carrier. This change adds parameter to
indicate if this header is supported and requires caller to provider the
config.
b/18371228
Change-Id: I2394dbb9551280037ad52e6983e35fa1f26d86ca
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 9dbb6ad72f064bde732111fe40ded4543b34295e |
|
12-Nov-2014 |
Ye Wen <ywen@google.com> |
Addressing API review issues for SmsManager (1/3)
b/18356155
Change-Id: I6202861943fe578a1edadf65de60df5bd77dae51
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 299dad50409e907993fa96c7401d4f10c58018b1 |
|
11-Nov-2014 |
Wink Saville <wink@google.com> |
Update SubscriptionManager API as per API council.
bug: 17575308
Change-Id: Ib39a60e4f75981a466e9d606ec627756efad018d
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| b237a11044ed842d2865ff8c8716befb06b6ca25 |
|
25-Oct-2014 |
Wink Saville <wink@google.com> |
Change subId to int from long
Change-Id: Idae6335e63e7b1e4e714bc17e71b1a4705e38474
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 6a5ef38e6ae3d3a3ad90ae180388fe85de0495a2 |
|
08-Sep-2014 |
Wink Saville <wink@google.com> |
Change suffix UsingSubId to ForSubscriber.
Bug: 17255752
Change-Id: Ifd522888b5aaae111f642d1e35bd1bb939e539d4
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 917cd56bf468b599ae1aca56773d18ee4a5d4df8 |
|
03-Sep-2014 |
Tom Taylor <tomtaylor@google.com> |
Change SmsManager.getSmsManagerForSubId to getSmsManagerUsingSubId
Bug 17371475
The agreed upon convention for SubId methods is xxxUsingSubId.
Change-Id: I3df09c5225f4331abe65868aded844a1334208c7
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 038b5c11030741f103c15741db74068ce099cb53 |
|
02-Sep-2014 |
Shri Borde <shri@google.com> |
MessagingConfigurationManager and SmsManager api changes
Bug 17243357: MessagingConfigurationManager is replaced with
SmsManager.getCarrierConfigValues
Remove the newly added SmsManager APIs taking a subId parameter. We now
create SmsManagers per requested subId.
Change-Id: Ifa95802b6f723c4986197a2b7d6fcbc43f4e0792
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 1dd55df4bcba73c42f724477284df2bd0edd4ff5 |
|
26-Aug-2014 |
Tom Taylor <tomtaylor@google.com> |
Complete MSIM support in MmsService
Bug 16681645
Use the subId to get the correct mms_config parameter.
Change-Id: Ie43d0979a5b5185c3c22bd171b9676a98b916e70
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| a2ce002a0327f0deb079cc6acad1c493e6ded442 |
|
05-Aug-2014 |
Amith Yamasani <yamasani@google.com> |
Make SmsApplication handle multiple users
Assume that there's one default app per user. Apps should be able
to register as the default app for even secondary users.
Read and write to the correct settings db.
Deliver DELIVER broadcast to primary user.
Deliver RECEIVED broadcast to all permitted and currently
running users.
Bug: 16681533
Change-Id: I08cf5318f267a8c55ac427ac2c3573b4319b5193
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| f1aeeb51f2c62420012122e0ccc75b3940c570e4 |
|
15-Jul-2014 |
Ye Wen <ywen@google.com> |
Messaging auto persist switch (2/4)
b/14095333
Change-Id: I9dccdadd72d951d86f83cb7adea9b2f09fad08ce
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| b29851580bba4a13ddbf7a534d8b09295eb2c60f |
|
10-Jul-2014 |
Ye Wen <ywen@google.com> |
New SMS and MMS APIs and semantics (2/4)
1. Rest of the new SMS and MMS APIs
2. Auto persisting MMS WAP Push
3. Partial multi-sim support
4. New SMS/MMS database columns: archived and creator
5. Record message creator
6. Mms config access APIs
b/14095333
Change-Id: Idb0ab75384b2c949f1a6ebe8f1c33e90a06a4d9b
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| cafda9904d2804959d51697cdc63a185e687cb98 |
|
12-Jul-2014 |
Colin Cross <ccross@google.com> |
Revert "New SMS and MMS APIs and semantics (2/4)"
This reverts commit c5f9236283882b8e08390ac52e5b1fab2d3bc2fb.
Change-Id: I9585dabfc31611e68718859ea509b8f52535d9b5
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| c5f9236283882b8e08390ac52e5b1fab2d3bc2fb |
|
10-Jul-2014 |
Ye Wen <ywen@google.com> |
New SMS and MMS APIs and semantics (2/4)
1. Rest of the new SMS and MMS APIs
2. Auto persisting MMS WAP Push
3. Partial multi-sim support
4. New SMS/MMS database columns: archived and creator
5. Record message creator
6. Mms config access APIs
b/14095333
Change-Id: I9a4261753a803f520933b643c0bac708ab9f40a9
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| a8467dd0c524787104b1ccdddc5e8af10ba729ed |
|
13-Jun-2014 |
Wink Saville <wink@google.com> |
Merge kwd to master
Change-Id: Idb607c0aa32f80fe4fe1539aedea7a221e9e7f04
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 023346cf9050c146a36eedd14886d0e9a679dc49 |
|
03-Dec-2013 |
Jake Hamby <jhamby@google.com> |
Fix OOBE crash/DoS after receiving 0-byte WAP push.
Add a try/catch block around the code in WapPushOverSms.dispatchWapPdu(),
so we don't get into a reboot trap on receiving weirdly formed messages.
Only catch ArrayIndexOutOfBoundsException, which is difficult to
prevent inside dispatchWapPdu() for 0-byte PDUs or other unusual
contents. The caller should probably catch any unhandled exceptions of other types and log them with stack traces.
Bug: 11967705
Change-Id: Iabfec68d2564dd438d45c80cdba877bf19fa0397
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 13fa971b6c6eab1578f4732c8de6fa2ba3b57ce6 |
|
29-Aug-2013 |
Sungmin Choi <sungmin.choi@lge.com> |
wappush: Use valid index for pdu including garbages
For some operators, pdu has garbages. As a result, device does not receive
MMS or operator some requests.
To fix it, re-index pdu to use valid index for operators.
Bug: 10492745
Change-Id: Ic7262f7369403bd060d94c5da0e09f18c96ff3db
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 5c3b6658d82f3af57161d5a34385dd95ea0f1abb |
|
16-Sep-2013 |
David Braun <dabraun@google.com> |
Implement new method for handling SMS/MMS on the platform
Multi project change:
The changes in this project implement the actual change in the SMS related
intent behavior (defining and using the new events).
Bug: 10449618
Change-Id: Ia707ed561d89428db78203a2ed54504d867a3e43
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 16d259bfedada60d6b772ee0c640df58830527df |
|
06-Aug-2013 |
Wink Saville <wink@google.com> |
When disposing only unbind if actually bound.
Change-Id: Icef7f050088d648fdf60f9a1ed690af46deb36e0
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 7d3118aa708e4d02bf65514ab3feda10cd05a619 |
|
05-Aug-2013 |
Dianne Hackborn <hackbod@google.com> |
Stop using implicit intents with bindService().
The behavior of this case is not defined.
Change-Id: I6e858190d7b0c3b8976a1657de81a682cd989eee
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 0d4bcdf379842af4b6304809156971e926f374f0 |
|
18-Mar-2013 |
Jake Hamby <jhamby@google.com> |
Refactor inbound (MT) SMS handling into new handler classes.
Moved all MT SMS handling to separate StateMachine classes, which
save all incoming PDUs in the SmsProvider "raw" table, previously
used only for storing PDUs of concatenated messages. Then we ACK the
message, before starting the ordered broadcast as usual. If a receiver
of the broadcast sets the status to failure, we ignore it, but in the
future we could provide a mechanism to redeliver the broadcast.
New classes are (without com.android.internal.telephony prefix):
- CellBroadcastHandler
- InboundSmsHandler
- InboundSmsTracker
- SmsBroadcastUndelivered
- WakeLockStateMachine
- cdma.CdmaInboundSmsHandler
- cdma.CdmaServiceCategoryProgramHandler
- gsm.GsmCellBroadcastHandler
- gsm.GsmInboundSmsHandler
This fixes a bug in the SMS dispatcher. Previously we delivered
incoming SM's as ordered broadcasts and then sent an acknowledgment
to the SMSC after the broadcast completed. It was possible for the
ordered broadcast to take over 20 seconds to complete, causing SMS
retransmissions because we didn't ACK quickly enough. Also, a
broadcast receiver could set the result code to failure (the AOSP
MMS app never does this), causing us to negatively acknowledge the
SMS, potentially leading to many retries and a backlog on the SMSC.
The reason for saving all PDUs in the raw table before ACKing is so
InboundSmsHandler can handle the failure case of a device crash or
power failure in between ACKing the message and the delivery of the
ordered broadcast to receivers. This is handled when the Phone class
starts, creating a new thread to run SmsBroadcastUndelivered.
This Runnable scans the raw table once, finding all complete
PDUs and sending IncomingSmsTrackers to the state machine to
broadcast them again to receivers. In the worst case, a message might
be added twice to the MMS inbox, but it won't be lost.
However, due to the current MMS app implementation, which immediately
acknowledges the ordered broadcast before starting a new Service to
process the message, there is a very short window of time when a
message could potentially be lost, if the MMS app or device crashed
after the ordered broadcast returns and the message is deleted from
the raw table, but before the MMS service has added the message to
its own tables. To fix this will probably require API changes.
Another improvement from this change: SmsBroadcastUndelivered also
deletes PDUs for incomplete multipart messages that are older than
30 days. We've never garbage collected this table in the past, so
it's possible for a phone to accumulate a number of old PDUs in the
raw table if not all components arrived successfully.
The wake lock handling is also improved in this version, as we now
acquire a wakelock when the state machine leaves the Idle state,
releasing it 3 seconds after returning to the idle state, instead
of the previous 5-second timeout. If a new SMS arrives while a
broadcast is being delivered, we add it to the raw table and ACK the
new PDU immediately, then send the InboundSmsTracker as a message to
handle when the previous broadcast completes.
In order to keep track of whether a PDU is in 3GPP or 3GPP2 format,
the destination port column of the raw table is extended with three
flags: 3GPP format, 3GPP2 format, and no destination port present.
Because the destination port is a 16-bit value in both 3GPP and
3GPP2, the upper bits of the destination port can be used for flags.
This saves us from having to modify the SMS provider to update the
DB version and to add extra columns to keep track of these flags.
Bug: 7099232
Change-Id: Ibbc01ccb83320f4b6112fe3dd31355eb6f570b67
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| cbaa45bbf2cab852b6c9c3a887e9f803d4e857ea |
|
23-Feb-2013 |
Wink Saville <wink@google.com> |
Clean up
- Add @Overrides where needed.
- Update javadoc comments
- Remove extra semi-colons
- Rename DataConnection.java to DataConnectionBase.java
- Rename GsmDataConnection.java to DataConnection.java
- Add defaults to switch statements
- Remove/fix most "if (false)" statements. Fixed by using a CONSTANT
- Fix hidden variables by hoisting to base class or renaming
- Tweak some debug output
Change-Id: If38de2fdeaacafbf40cdfd7f84dc5c52030ba2a3
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 7fce994eb223105829becb6c26e3af7a9739752c |
|
05-Feb-2013 |
Dianne Hackborn <hackbod@google.com> |
Add new app ops for sending/receiving SMS messages.
There are a variety of new app ops for various kind of
SMS operations: reading, writing, sending, receiving, on
ICC card, MMS, etc. These are instrumented in the telephony
framework; the controls for access to these features are
rolled up to either sending or receiving SMS.
Change-Id: Ie18b09d77fac555aaa169eb6fdfba44dd8078976
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 072d5d580041046968dbc335c5d4418f344d2b39 |
|
22-Nov-2012 |
Maunik Shah <mshah@codeaurora.org> |
Fixes Binder Buffer leak after crashing com.android.smspush process
After many crashes of com.android.smspush process under low memory
condition, binder buffer used to get overflow as there is a leak
in buffer.
This fix restricts the leak in binder buffer by unbinding it upon
com.android.smspush process crash.
Change-Id: I0b5cd4ef282ec9f12693337001c084ce60db4555
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| d720945f2be5ea5fe0faf67e67d9ea0e184eba67 |
|
01-Aug-2012 |
Alex Yakavenka <ayakav@codeaurora.org> |
Telephony: Move uicc classes into uicc package
Reduce constructor visibility to package where
possible
Dependent Changes:
I3b718b9aea1f21c7906c8243b4ca0db6af495a08
I80204a2f3dc57cac875abeab390bb9db7a636ff7
Ib9c19e8b157dc7ec74eb14baca5bd3b5caf08c47
Change-Id: Ib4f43374c041cb5eaf2e3883e5ea28b2eb2c9a69
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| ded9c0af7fa49504c047275ed34c2d3b22bf0c3a |
|
07-Dec-2012 |
Wink Saville <wink@google.com> |
Use Rlog
Change-Id: Ie013f51215de8380b8de74161b6056b010711cfd
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|
| 0825495a331bb44df395a0cdb79fab85e68db5d5 |
|
12-Jul-2012 |
Wink Saville <wink@google.com> |
Create telephony-common
telephony-common was created by moving some of
frameworks/base/telephony
to:
frameworks/opt/telephony
Change-Id: I32cbb5eec1fa239c1587e055c8f7ef4fc48fb62c
/frameworks/opt/telephony/src/java/com/android/internal/telephony/WapPushOverSms.java
|