Check the Nougat version code in the supported way

chrome/android/java/src/org/chromium/chrome/browser/notifications/NotificationPlatformBridge.java

Index: chrome/android/java/src/org/chromium/chrome/browser/notifications/NotificationPlatformBridge.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/notifications/NotificationPlatformBridge.java b/chrome/android/java/src/org/chromium/chrome/browser/notifications/NotificationPlatformBridge.java
index 182ab94789f45830328023481f83f58f5b1334c6..0ca20263b419fef302c1a463aacb1ab55325fcd1 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/notifications/NotificationPlatformBridge.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/notifications/NotificationPlatformBridge.java
@@ -633,7 +633,7 @@ public class NotificationPlatformBridge {
         if (commandLine.hasSwitch(ChromeSwitches.DISABLE_WEB_NOTIFICATION_CUSTOM_LAYOUTS)) {
             return false;
         }
-        if (Build.VERSION.CODENAME.equals("N") || Build.VERSION.SDK_INT > Build.VERSION_CODES.M) {
+        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) {

[johnme, 2016/11/28 13:54:06]

This will fail to detect devices stuck on early N developer preview builds[1].
For past versions of Android that was only a few Googlers, but N had a public
developer preview, so there might be a few actual users on such builds. Is there
a benefit to moving to this shorter form?

[1]:
https://commonsware.com/blog/2016/03/17/backwards-compatibility-n-developer-p...

             return false;
         }
         if (hasImage) {