summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
author Makoto Onuki <omakoto@google.com> 2021-08-06 14:10:29 -0700
committer Makoto Onuki <omakoto@google.com> 2021-08-06 21:43:31 +0000
commit5031c3a4f63a4a843eefdb49fe5e06ea25a4e482 (patch)
tree7c8c1b0bc63105f2d9f5a67fcd18e69ffdc20c98
parentedb6d7f8a8d597b7c5379196daab6d89e07ace7e (diff)
Clarify how FGS restriction won't apply STICKY FGS restarts
Fix: 195780554 Test: build Change-Id: Ic627a89ac863729d36554070d04c22254747f014
-rw-r--r--core/java/android/app/Service.java7
1 files changed, 7 insertions, 0 deletions
diff --git a/core/java/android/app/Service.java b/core/java/android/app/Service.java
index 7cb1d89aa954..336387204410 100644
--- a/core/java/android/app/Service.java
+++ b/core/java/android/app/Service.java
@@ -387,6 +387,13 @@ public abstract class Service extends ContextWrapper implements ComponentCallbac
* <p>This mode makes sense for things that will be explicitly started
* and stopped to run for arbitrary periods of time, such as a service
* performing background music playback.
+ *
+ * <p>Since Android version {@link Build.VERSION_CODES#S}, apps
+ * targeting {@link Build.VERSION_CODES#S} or above are disallowed
+ * to start a foreground service from the background, but the restriction
+ * doesn't impact <em>restarts</em> of a sticky foreground service. However,
+ * when apps start a sticky foreground service from the background,
+ * the same restriction still applies.
*/
public static final int START_STICKY = 1;