Add documentation for SECRET_CODE_ACTION according to API review

process.

 * Document who can send and who can receive the broadcast. What are the security restrictions?
   The implication here is that there should be some. What are the wake-up semantics?
 * Document who can receive SECRET_CODE action and under what circumstances,
   and what permissions are needed to receive and send it.

Bug: 73751267, 73392896
Test: Basic telephony sanity
Change-Id: I1b6138c9ddf4cb3d84d8b652e18d4e57f410ee4d
This commit is contained in:
Cassie
2018-02-22 09:58:33 -08:00
parent 18f8500e32
commit 5b97cf1395

View File

@@ -1102,10 +1102,15 @@ public final class Telephony {
"android.provider.Telephony.MMS_DOWNLOADED";
/**
* Broadcast Action: A debug code has been entered in the dialer. These "secret codes"
* are used to activate developer menus by dialing certain codes. And they are of the
* form {@code *#*#<code>#*#*}. The intent will have the data URI:
* {@code android_secret_code://<code>}.
* Broadcast Action: A debug code has been entered in the dialer. This intent is
* broadcast by the system and OEM telephony apps may need to receive these broadcasts.
* These "secret codes" are used to activate developer menus by dialing certain codes.
* And they are of the form {@code *#*#<code>#*#*}. The intent will have the data
* URI: {@code android_secret_code://<code>}. It is possible that a manifest
* receiver would be woken up even if it is not currently running.
*
* <p>Requires {@code android.Manifest.permission#CONTROL_INCALL_EXPERIENCE} to
* send and receive.</p>
*/
@SdkConstant(SdkConstantType.BROADCAST_INTENT_ACTION)
public static final String SECRET_CODE_ACTION =