Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "Clarifying docs for USE_EXACT_ALARM" into tm-dev

Browse Source
This commit is contained in:
TreeHugger Robot
2022-03-23 21:26:59 +00:00
committed by Android (Google) Code Review
parent d7b3be3e0b b56ceea6f4
commit 5c687a5145
1 changed files with 29 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
core/res/AndroidManifest.xml
View File

@@ -4445,21 +4445,41 @@
For more details, see <a For more details, see <a
href="{@docRoot}about/versions/12/behavior-changes-12#exact-alarm-permission"> href="{@docRoot}about/versions/12/behavior-changes-12#exact-alarm-permission">
Exact alarm permission</a>. Exact alarm permission</a>.
<p>Apps who hold this permission and target API level 31 or above, always stay in the <p>Apps need to target API {@link android.os.Build.VERSION_CODES#S} or above to be able to
request this permission. Note that apps targeting lower API levels do not need this
permission to use exact alarm APIs.
<p>Apps that hold this permission, always stay in the
{@link android.app.usage.UsageStatsManager#STANDBY_BUCKET_WORKING_SET WORKING_SET} or {@link android.app.usage.UsageStatsManager#STANDBY_BUCKET_WORKING_SET WORKING_SET} or
lower standby bucket. lower standby bucket.
Applications targeting API level 30 or below do not need this permission to use <p>If your app relies on exact alarms for core functionality, it can instead request
exact alarm APIs. {@link android.Manifest.permission#USE_EXACT_ALARM} once it targets API
{@link android.os.Build.VERSION_CODES#TIRAMISU}. All apps using exact alarms for secondary
features (which should still be user facing) should continue using this permission.
--> -->
<permission android:name="android.permission.SCHEDULE_EXACT_ALARM" <permission android:name="android.permission.SCHEDULE_EXACT_ALARM"
android:protectionLevel="normal|appop"/> android:protectionLevel="normal|appop"/>
<!-- Allows apps to use exact alarms just like with SCHEDULE_EXACT_ALARM but without needing <!-- Allows apps to use exact alarms just like with {@link
to request this permission from the user. android.Manifest.permission#SCHEDULE_EXACT_ALARM} but without needing to request this
<p><b>This is only for apps that rely on exact alarms for their core functionality.</b> permission from the user.
App stores may enforce policies to audit and review the use of this permission. Any app that <p><b> This is only intended for use by apps that rely on exact alarms for their core
requests this but is found to not require exact alarms for its primary function may be functionality.</b> You should continue using {@code SCHEDULE_EXACT_ALARM} if your app needs
removed from the app store. exact alarms for a secondary feature that users may or may not use within your app.
<p> Keep in mind that this is a powerful permission and app stores may enforce policies to
audit and review the use of this permission. Such audits may involve removal from the app
store if the app is found to be misusing this permission.
<p> Apps need to target API {@link android.os.Build.VERSION_CODES#TIRAMISU} or above to be
able to request this permission. Note that only one of {@code USE_EXACT_ALARM} or
{@code SCHEDULE_EXACT_ALARM} should be requested on a device. If your app is already using
{@code SCHEDULE_EXACT_ALARM} on older SDKs but need {@code USE_EXACT_ALARM} on SDK 33 and
above, then {@code SCHEDULE_EXACT_ALARM} should be declared with a max-sdk attribute, like:
<pre>
&lt;uses-permission android:name="android.permission.SCHEDULE_EXACT_ALARM"
&Tab; android:maxSdkVersion="32" /&gt;
</pre>
<p>Apps that hold this permission, always stay in the
{@link android.app.usage.UsageStatsManager#STANDBY_BUCKET_WORKING_SET WORKING_SET} or
lower standby bucket.
--> -->
<permission android:name="android.permission.USE_EXACT_ALARM" <permission android:name="android.permission.USE_EXACT_ALARM"
android:protectionLevel="normal"/> android:protectionLevel="normal"/>