crazylinker: Disable on Android N+

This reverts commit 774b2fbf and
describes new evidence in comments.

Bug: 980304
Change-Id: I20f3e7abdcade1cafa2b5d85bad4aa215e6ff1cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695557
Commit-Queue: Egor Pasko <pasko@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676392}

base/android/java/src/org/chromium/base/library_loader/LibraryLoader.java

@@ -140,6 +140,20 @@ public class LibraryLoader {
      * libraries instead.
      */
     public static boolean useCrazyLinker() {
+        // A non-monochrome APK (such as ChromePublic.apk) can be installed on N+ in these
+        // circumstances:
+        // * installing APK manually
+        // * after OTA from M to N
+        // * side-installing Chrome (possibly from another release channel)
+        // * Play Store bugs leading to incorrect APK flavor being installed
+        // * installing other Chromium-based browsers
+        //
+        // For Chrome builds regularly shipped to users on N+, the system linker (or the Android
+        // Framework) provides the necessary functionality to load without crazylinker. The
+        // crazylinker is risky to auto-enable on newer Android releases, as it may interfere with
+        // regular library loading. See http://crbug.com/980304 as example.
+        if (Build.VERSION.SDK_INT >= VERSION_CODES.N) return false;
+
         // The auto-generated NativeLibraries.sUseLinker variable will be true if the
         // build has not explicitly disabled Linker features.
         return NativeLibraries.sUseLinker;