| c0db70e3992184da49eeab9acbedacc04ed4ccf1 |
|
03-Sep-2015 |
Svetoslav <svetoslavganov@google.com> |
Enable WRITE_SMS for telephony provider
WRITE_SMS app op is explicitly granted to some system components
like bluetooh, phone, mms service. It is however no granted to the
telephony provider. The latter is the one storing the SMS data and
should always have the app op enabled. Content providers perform
proxy app op updates (taking a note they perform an operation on
behalf of another app) which requires the proxy package, the provider,
to have the app op allowed.
bug:23017449
Change-Id: Ic0c6865a616b6f3997a64d390699e9fd86c4ae2e
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.java
|
| f4eaa59cc0a6d9b35ae92e52dd1390d60b9e877a |
|
08-Jun-2015 |
Ye Wen <ywen@google.com> |
Check special system apps' signatures when setting up default SMS app
b/21699325
Change-Id: Id24bef961756ac85ad0ccd1728ec311a11996f5b
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.java
|
| 00647e7f55b1e2283a89b2888dbe2e6ad34cce01 |
|
10-Mar-2015 |
Ye Wen <ywen@google.com> |
Restricted view of SMS/MMS providers (1/2)
Added new SmsApplication method to check if a package is default SMS app
b/19348537
Change-Id: I2e2139430744b8d90495b86097e6fdbbe7be6c73
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.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/SmsApplication.java
|
| 6dc23862ef345df2acd3ab36a432292d264d6a73 |
|
28-Jul-2014 |
Ye Wen <ywen@google.com> |
MmsService always has WRITE_SMS AppOps permission (1/2)
Use the same mechanism as phone app to grant MmsService write access to
Sms/Mms providers.
Change-Id: I38a0a67b75a4c3069259ce7284acca295dbd3e28
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.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/SmsApplication.java
|
| ac9c712e8ac929fec2f91f738d85148919ceeebe |
|
29-Dec-2013 |
Dave Daynard <nardholio@gmail.com> |
Allow tablets to send SMS if enabled in device overlays (2/2)
Change-Id: I30299d44eb59e89104b9b0b90be10da2a6ce62ac
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.java
|
| d8fb3ddda34db44297cf4b0f970b01bf58598960 |
|
14-Nov-2013 |
David Braun <dabraun@google.com> |
Do not attempt to configure null preferred activity
On non-phone devices the default SMS app is null. During the set/get paths
we would not try to configure the activity, but during the package update
path we called 'getDefaultSendToApplication" and configured it without
validating that it is non-null. This change adds the null check.
Bug: 11482259 When default SMS app changes we need to update the default app for the SEND intent
Change-Id: I227cfd803fd0667d78918a720b5a6eae9d57ea9d
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.java
|
| 8a4c72815186db4187587d4fc62125540a0e42a8 |
|
12-Nov-2013 |
David Braun <dabraun@google.com> |
Update preferred activity for SMS related SENDTO intents
Updates the preferred SENDTO activity for sms/mms schemes so that the user
will not see an intent disambiguation dialog for SENDTO sms/mms.
- Update preferred activity on set default SMS app
- Update preferred activity on "secure" get default SMS app
- Update preferred activity on package install/uninstall
Bug:11482259 When default SMS app changes we need to update the default app for the SEND intent
Change-Id: Ib2752fe84389f1c50cf2aa5841e75c3913b94e18
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.java
|
| 4931e2c19616ab5985f61f343b231efb33692241 |
|
01-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
problem to send SMS message by bluetooth MAP profile.
Currently SMSDispatcher will add the message to Sms.Sent database
for all non default SMS application.
This won't work for Bluetooth MAP profile.
In the bluetooth MAP spec, at 5.8 PushMessageFunction,
there are a parameter to control how to send the message by Bluetooth MAP.
Transparent:This parameter may be used to indicate to the MSE(phone)
that no copy of the message shall be kept in the 'Sent' folder
after the message was sent. This is especially useful for telematics applications,
e.g., frequent sending of car's speed and position for traffic measurements
(floating car data).
This application parameter is optional. The value of this parameter is "OFF"
(keep messages in 'Sent' folder) and "ON" (don't keep messages in Sent' folder).
If Transparent is "ON", we shouldn't put the message in Sent folder.
SMSDispatcher always put the message in Sms.Sent
which is mapped to the Sent folder in bluetooth MAP.
Prefer to let bluetooth to decide whether put the message in Sms.Sent based
on Transparent parameter value.
bug:11454636
Change-Id: I2e6c8deb5c4ed8bc9a3d90d492f4d4eb7dac7e5c
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.java
|
| 9382b17d503c107b38610b217ba7c93525be206a |
|
30-Oct-2013 |
Zhihai Xu <zhihaixu@google.com> |
add SMS write permission for bluetooth package to support MAP profile.
bug:11415002
Change-Id: I177210e4139560b066ae40f100ca09ea35805359
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.java
|
| c67761d00a25bd095364e3ff4e4cb8e88b2e974c |
|
13-Oct-2013 |
David Braun <dabraun@google.com> |
Make SmsApplication checks more defensive
When SmsApplication::getApplication is called it will check to see if the
configured default SMS app and the phone package have the needed app ops
to work properly. If the call was made from a privilidged caller where
updateIfNeeded == true then the issue will be corrected, if the call was
made from an insecure caller we will return null indicating no default SMS
app which will cause client apps to know that they are not properly set
as the default SMS app. Either way we log an error.
When SmsApplication::setDefaultApplication is called we will ensure that
even if the previous app is no longer enabled or no longer set up as a
valid SMS app, we will still revoke it's OP_WRITE_SMS permission.
Bug: 11071837 Hangouts on KLP lost the WRITE_SMS permission
Change-Id: Ifea39a3d63e4ec3a30a6a1fa5834878dcc9ccfa0
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.java
|
| 29569c31ed24dd8f48be3f898047d4d7b5665052 |
|
05-Oct-2013 |
David Braun <dabraun@google.com> |
Do not allow default SMS application to be set or get on non-phone devices
Bug: 11072894 People app should not launch into default SMS app on tablets
Change-Id: I9cedf3840f46bbc135f535b60659e5527f79a5aa
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.java
|
| 041cfe21bd66c8cb002435e7dc54177db2e927aa |
|
25-Sep-2013 |
David Braun <dabraun@google.com> |
Update the requirements for being an SMS app in KLP
SMS applications need to handle repsond-via-message (for rejecting a phone
call with an SMS message) and SENDTO with the smsto Uri scheme so that
contact applications can direct the user to the right app. This change also
adds permission requirements for the existing intents that SMS apps
implement.
Bug: 10870624 System should direct "SENDTO" intent with "sms" and "mms" schemes to the default SMS app
Bug: 10818880 Telephony needs to direct RESPOND_VIA_MESSAGE intent only to the default SMS app
Change-Id: I373268bb694f155fb08e2864ae86af345a85c4ff
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.java
|
| 9c9341ecba5312a4a5be5f9fee3ffe1b582b65ce |
|
20-Sep-2013 |
David Braun <dabraun@google.com> |
Add config setting for default sms app.
Different devices can have different default SMS apps.
Bug: 10818725 Allow OEM to specify or override a default SMS app (package)
Change-Id: I11c9832d2246677231e6a54cb03eb76650c85c98
/frameworks/opt/telephony/src/java/com/android/internal/telephony/SmsApplication.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/SmsApplication.java
|