6d2c0e5ee2f717d4a5c00df08aca21c76eea8278 |
|
23-Jun-2015 |
Svetoslav Ganov <svetoslavganov@google.com> |
Remove not needed contacts related permissions. This reverts commit ed5ff51b2ca7c051e2719dfc8a8a083e6208848e. Change-Id: If2407e4e474a438d95e1b7ad1aa6f441bb3ace08
/frameworks/base/docs/html/guide/topics/providers/contacts-provider.jd
|
ed5ff51b2ca7c051e2719dfc8a8a083e6208848e |
|
23-Jun-2015 |
Bart Sears <bsears@google.com> |
Revert "Remove not needed contacts related perissions." Broke the build, reverting. This reverts commit a2991da0d671adf511ccb884cf25bf1241303f92. Change-Id: I2bdfa70fbd8a6c03e48426f85eeb63896762d5da
/frameworks/base/docs/html/guide/topics/providers/contacts-provider.jd
|
a2991da0d671adf511ccb884cf25bf1241303f92 |
|
22-Jun-2015 |
Svet Ganov <svetoslavganov@google.com> |
Remove not needed contacts related perissions. Removing the read/write profile/social stream permissions as they are not needed anymore. These permissions are for accessing data nested in the conacts provider which is already guaded by the read/write contacts runtime permissions. The removed permissions would be in the contacts group which means they would not provide more protection compated to read/write contacts. Also removing the permissions voids the need for app op support for legacy apps. Removed deprecated APIs for social streams as these were deprecated and will go away in the next release. We want apps targeting M to not be able to compile if still suing these APIs to help with migration. Change-Id: I26ed9055847af7f92c78eb0f4ac8f9f1aa616fcd
/frameworks/base/docs/html/guide/topics/providers/contacts-provider.jd
|
50e990c64fa23ce94efa76b9e72df7f8ec3cee6a |
|
22-Jun-2012 |
Scott Main <smain@google.com> |
Massive clobber of all HTML files in developer docs for new site design Change-Id: Idc55a0b368c1d2c1e7d4999601b739dd57f08eb3
/frameworks/base/docs/html/guide/topics/providers/contacts-provider.jd
|