Android Foreground Service Notification Not Showing


Answer :

It's because of Android O bg services restrictions.

So now you need to call startForeground() only for services that were started with startForegroundService() and call it in first 5 seconds after service has been started.

Here is the guide - https://developer.android.com/about/versions/oreo/background#services

Like this:

//Start service: if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {   startForegroundService(new Intent(this, YourService.class)); } else {   startService(new Intent(this, YourService.class)); }

Then create and show notification (with channel as supposed earlier):

private void createAndShowForegroundNotification(Service yourService, int notificationId) {      final NotificationCompat.Builder builder = getNotificationBuilder(yourService,          "com.example.your_app.notification.CHANNEL_ID_FOREGROUND", // Channel id     NotificationManagerCompat.IMPORTANCE_LOW); //Low importance prevent visual appearance for this notification channel on top      builder.setOngoing(true)     .setSmallIcon(R.drawable.small_icon)     .setContentTitle(yourService.getString(R.string.title))     .setContentText(yourService.getString(R.string.content));      Notification notification = builder.build();      yourService.startForeground(notificationId, notification);      if (notificationId != lastShownNotificationId) {           // Cancel previous notification           final NotificationManager nm = (NotificationManager) yourService.getSystemService(Activity.NOTIFICATION_SERVICE);           nm.cancel(lastShownNotificationId);     }     lastShownNotificationId = notificationId; }  public static NotificationCompat.Builder getNotificationBuilder(Context context, String channelId, int importance) {     NotificationCompat.Builder builder;     if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {         prepareChannel(context, channelId, importance);         builder = new NotificationCompat.Builder(context, channelId);     } else {         builder = new NotificationCompat.Builder(context);     }     return builder; }  @TargetApi(26) private static void prepareChannel(Context context, String id, int importance) {     final String appName = context.getString(R.string.app_name);     String description = context.getString(R.string.notifications_channel_description);     final NotificationManager nm = (NotificationManager) context.getSystemService(Activity.NOTIFICATION_SERVICE);      if(nm != null) {         NotificationChannel nChannel = nm.getNotificationChannel(id);          if (nChannel == null) {             nChannel = new NotificationChannel(id, appName, importance);             nChannel.setDescription(description);             nm.createNotificationChannel(nChannel);         }     } }

Remember that your foreground notification will have the same state as your other notifications even if you'll use different channel ids, so it might be hidden as a group with others. Use different groups to avoid it.


The problem was i am using Android O and it requires more information. Here is the successful code for android O.

    mNotifyManager = (NotificationManager) mActivity.getSystemService(Context.NOTIFICATION_SERVICE);     if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) createChannel(mNotifyManager);     mBuilder = new NotificationCompat.Builder(mActivity, "YOUR_TEXT_HERE").setSmallIcon(android.R.drawable.stat_sys_download).setColor             (ContextCompat.getColor(mActivity, R.color.colorNotification)).setContentTitle(YOUR_TITLE_HERE).setContentText(YOUR_DESCRIPTION_HERE);     mNotifyManager.notify(mFile.getId().hashCode(), mBuilder.build());  @TargetApi(26) private void createChannel(NotificationManager notificationManager) {     String name = "FileDownload";     String description = "Notifications for download status";     int importance = NotificationManager.IMPORTANCE_DEFAULT;      NotificationChannel mChannel = new NotificationChannel(name, name, importance);     mChannel.setDescription(description);     mChannel.enableLights(true);     mChannel.setLightColor(Color.BLUE);     notificationManager.createNotificationChannel(mChannel); }

If none of the above worked you should check if your notification id is 0 ... SURPRISE!! it cannot be 0.

Many thanks to @Luka Kama for this post

startForeground(0, notification); // Doesn't work...  startForeground(1, notification); // Works!!!

Comments

Post a Comment

Popular posts from this blog

Chemistry - Bond Angles In NH3 And NCl3

Answer : Solution 1: As Tan Yong Boon stated, it is Bent’s Rule with which we can explain the lower bond angle of \ce N F 3 \ce{NF3} \ce NF 3 when compared to \ce N H 3 \ce{NH3} \ce N H 3 . The rule as stated by Henry Bent: Atomic s character concentrates in orbitals directed towards electropositive substituents. Fluorine is more electronegative that hydrogen, and the \ce N − F \ce{N−F} \ce N − F bond would have greater p character than the \ce N − H \ce{N−H} \ce N − H bond. And more s character leads to large bond angles. Thus, the bond angle is greater in \ce N H 3 \ce{NH3} \ce N H 3 than in \ce N F 3 \ce{NF3} \ce NF 3 . Now, consider \ce N C l 3 \ce{NCl3} \ce NCl 3 . Clearly, \ce C l \ce{Cl} \ce Cl atom islarger in size than the central atom, nitrogen. Hence the higher bond angle here is due to the steric crowding caused by \ce C l \ce{Cl} \ce Cl atoms.(More pronounced than the electrongativity of \ce C l \ce{Cl} \ce Cl atom). They repel eachother and hence b
Read more

Are Regular VACUUM ANALYZE Still Recommended Under 9.1?

Answer : VACUUM is only needed on updated or deleted rows in non-temporary tables. Obviously you're doing lots of INSERTs but it's not obvious from the description that you're also doing lots of UPDATEs or DELETEs. These operations can be tracked with the pg_stat_all_tables view, specifically the n_tup_upd and n_tup_del columns. Also, even more to the point, there is a n_dead_tup column that tells, per table, how much rows need to be vacuumed. (see Monitoring statistics in the doc for functions and views related to statistics gathering). A possible strategy in your case would be to suppress the scheduled VACUUM, keeping an eye on this view and checking on which tables the n_dead_tup is going up significantly. Then apply the aggressive VACUUM to these tables only. This will be a win if there are large tables whose rows never get deleted nor updated and the aggressive VACUUM is really necessary only on smaller tables. But keep running the ANALYZE for the optimiz
Read more

Can Feynman Diagrams Be Used To Represent Any Perturbation Theory?

Answer : Diagram machinery works also for perturbation theory in classical statistical mechanics and classical field theories. Generally, various kinds of diagrams constitute a pictorial way of talking about tensor products and their contractions while hiding the multi-linear algebra from the layman. In the simplest case, vertices (or blobs) represent vectors, matrices, tensors; vertices have ingoing and/or outgoing ports; ingoing ports denote (contravariant) ro indices; outgoing ports denote (covariant) co indices; directed arcs between blobs give a pair of equal indices summed over; different base spaces ⇔ \Leftrightarrow ⇔ different arc types; symmetric tensors ⇔ \Leftrightarrow ⇔ undirected diagrams; no labels are needed for internal lines. In many cases, the directed arcs are decorated (as thin, thick, broken,wavy, curly lines), each decoration indicating the presence of a so-called propagator, a function of its label to use as a weight in the sum, which may beco
Read more