diff options
| author | 2017-07-31 14:22:04 -0700 | |
|---|---|---|
| committer | 2017-07-31 14:25:39 -0700 | |
| commit | 6e5bd3f9f805cc074248a86160b9ea340e10be14 (patch) | |
| tree | f517d47a0ee54702ff6caded62b7075b55fc0835 | |
| parent | 3072aa76c9ee475bdc76d16987855a7b7feffff6 (diff) | |
Add documentation for MIN notification interaction with fg services.
Don't do this, you won't get what you want.
Test: built
Change-Id: I57ae93ced2b9ad563197c00ad8d94f7b492dff0c
| -rw-r--r-- | core/java/android/app/NotificationManager.java | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/core/java/android/app/NotificationManager.java b/core/java/android/app/NotificationManager.java index 885817231175..34343e9e106a 100644 --- a/core/java/android/app/NotificationManager.java +++ b/core/java/android/app/NotificationManager.java @@ -204,7 +204,12 @@ public class NotificationManager { public static final int IMPORTANCE_NONE = 0; /** - * Min notification importance: only shows in the shade, below the fold. + * Min notification importance: only shows in the shade, below the fold. This should + * not be used with {@link Service#startForeground(int, Notification) Service.startForeground} + * since a foreground service is supposed to be something the user cares about so it does + * not make semantic sense to mark its notification as minimum importance. If you do this + * as of Android version {@link android.os.Build.VERSION_CODES#O}, the system will show + * a higher-priority notification about your app running in the background. */ public static final int IMPORTANCE_MIN = 1; |