Skip to content
Related Articles

Related Articles

Improve Article
Save Article
Like Article

Notifications in Android Oreo (8+)

  • Last Updated : 17 Jul, 2018

Android Oreo has brought in a ton of changes. This also includes the way in which a user issue notifications in an app. In this article, we will discuss the changes required to be made in the notification department.

Following things are to be kept in mind while issuing notifications:

  1. Designing a Notification Channel
  2. Importance of each notification channel
  3. Notification ID (different from channel id) should not be set to zero.

Before going forward, make sure this line is added in the build.gradle (Module: app) dependencies:

implementation ''

Let’s start with making a notification channel. The method below creates a notification channel:

@RequiresApi(api = Build.VERSION_CODES.O)
void makeNotificationChannel(String id, String name, int importance)
    NotificationChannel channel = new NotificationChannel(id, name, importance);
    channel.setShowBadge(true); // set false to disable badges, Oreo exclusive
    NotificationManager notificationManager =
    assert notificationManager != null;

Let’s see what this method does in detail.

  1. The method accepts String id, String name, int importance..
    • String id: This is the id with which you issue a notification in the notification channel. You use this exact id for multiple notifications in the same channel.
    • String name: This is the name of the channel visible when someone taps navigates to Settings -> Apps & Notifications -> [your_app_name] -> App notifications.
    • int importance: This is the importance level of the channel. The levels are as follows:
      1. NotificationManager.IMPORTANCE_MIN – shows only in notification shade, no sound or peek.
      2. NotificationManager.IMPORTANCE_LOW – shows everywhere, doesn’t make sound, doesn’t peek.
      3. NotificationManager.IMPORTANCE_DEFAULT – shows everywhere, makes sound but doesn’t peek.
      4. NotificationManager.IMPORTANCE_HIGH – shows everywhere, makes sound and peeks (visual interruption).
      5. NotificationManager.IMPORTANCE_MAX – this importance level is usually not used. Works similar to IMPORTANCE_HIGH.

        Often the IMPORTANCE_DEFAULT parameter is preferred but this produces the notification sound that can be annoying. To silence, add the following line in the makeNotificationChannel() method, just before the last line.

        channel.setSound(null, null);
  2. The method then creates the channel with the parameters.
  3. The setShowBadge(true) makes the notification available by the Oreo notification dot feature.
  4. Finally, the notification channel is created by the createNotificationChannel() method of NotificationManager.

    Now let us issue a notification. We will use NotificationCompat for backwards compatibility.

    void issueNotification()
        // make the channel. The method has been discussed before.
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
            makeNotificationChannel("CHANNEL_1", "Example channel", NotificationManager.IMPORTANCE_DEFAULT);
        // the check ensures that the channel will only be made
        // if the device is running Android 8+
        NotificationCompat.Builder notification =
                    new NotificationCompat.Builder(this, "CHANNEL_1");
        // the second parameter is the channel id.
        // it should be the same as passed to the makeNotificationChannel() method
            .setSmallIcon(R.mipmap.ic_launcher) // can use any other icon
            .setContentText("This is an Oreo notification!")
            .setNumber(3); // this shows a number in the notification dots
        NotificationManager notificationManager =
        assert notificationManager != null;
        // it is better to not use 0 as notification id, so used 1.

    The execution proceeds in this way:

    • First, the above method initially creates a notification channel with id = “CHANNEL_1” and the name “Example channel”. The id isn’t visible anywhere but the name can be viewed by opening the “App notifications” option of the App Info page.

    • Then a NotificationCompat.Builder object is made specifying the context and id as “CHANNEL_1”. A different channel id can be mentioned provided it is made with the makeNotificationChannel() method.
      The rest is self-explanatory. The setNumber() method shows a number in the notification dot of the app.

    • Finally, the notification id (here 1) is better to not set 0 as in cases where the notification is used for a Foreground service, it will fail to display if the id is 0. On executing the issueNotification() method, we get the following notification:

    Attention reader! Don’t stop learning now. Get hold of all the important Java Foundation and Collections concepts with the Fundamentals of Java and Java Collections Course at a student-friendly price and become industry ready. To complete your preparation from learning a language to DS Algo and many more,  please refer Complete Interview Preparation Course.

    My Personal Notes arrow_drop_up
Recommended Articles
Page :

Start Your Coding Journey Now!