Access mock location is no longer a runtime permission - settings

The access mock location is no longer a runtime permission. It is a
signature protected one that apps cannot get but the fact they request
it means they want to inject location into the system. Now the user
gets to choose the current mock location app in developer options from
the apps that request the mock location permission. The access to mock
location is no longer guarded by the permisson but from a new app op
which is off by default and the settiings UI sets it to enabled only
for the currently selected mock location app.

bug:21078873

Change-Id: I6555179ecf0cc37d9bb857e9dfb3b04c091ea612
This commit is contained in:
Svet Ganov
2015-05-13 10:39:35 -07:00
committed by Svetoslav
parent 0c3d8f1c0f
commit 02e65a181a
4 changed files with 156 additions and 24 deletions

View File

@@ -3540,10 +3540,14 @@
<string name="select_logd_size_title">Logger buffer sizes</string>
<!-- UI debug setting: limit size of Android logger buffers [CHAR LIMIT=59] -->
<string name="select_logd_size_dialog_title">Select Logger sizes per log buffer</string>
<!-- Setting Checkbox title whether to allow mock locations -->
<string name="allow_mock_location">Allow mock locations</string>
<!-- setting Checkbox summary whether to allow mock locations -->
<string name="allow_mock_location_summary">Allow mock locations</string>
<!-- UI debug setting: select current app to mock location [CHAR LIMIT=50] -->
<string name="mock_location_app">Select mock location app</string>
<!-- UI debug setting: no mock location app has been set [CHAR LIMIT=50] -->
<string name="mock_location_app_not_set">No mock location app set</string>
<!-- UI debug setting: mock location app has been set [CHAR LIMIT=50] -->
<string name="mock_location_app_set">Mock location app: <xliff:g id="app_name">%1$s</xliff:g></string>
<!-- Setting Checkbox title whether to enable view attribute inspection -->
<string name="debug_view_attributes">Enable view attribute inspection</string>
<!-- Title of warning dialog about the implications of enabling USB debugging -->