From f7e9cf4fb48ea80cbc5088204ac3f898109623f7 Mon Sep 17 00:00:00 2001 From: Svet Ganov Date: Wed, 13 May 2015 10:40:31 -0700 Subject: Access mock location is no longer a runtime permission - framework 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: I19e3f9dc7c7de82eab46b30fec1abfbca54a0e59 --- docs/html/training/location/location-testing.jd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/html/training') diff --git a/docs/html/training/location/location-testing.jd b/docs/html/training/location/location-testing.jd index 5021fc0..8f73d51 100644 --- a/docs/html/training/location/location-testing.jd +++ b/docs/html/training/location/location-testing.jd @@ -79,7 +79,7 @@ trainingnavtop=true

Turn On Mock Mode

To send mock locations to Location Services in mock mode, a test app must request the permission - {@link android.Manifest.permission#ACCESS_MOCK_LOCATION}. In addition, you must enable mock + android.Manifest.permission#ACCESS_MOCK_LOCATION. In addition, you must enable mock locations on the test device using the option Enable mock locations. To learn how to enable mock locations on the device, see Setting up a Device for Development. -- cgit v1.1