Mysterious Android codebase commit
This diff is more explicit about what's going on:https://android.googlesource.com/platform/libcore.git/+/aab9...    Change dependency from libart -> libopenjdkjvm.

There are also diffs adding lambda support, tweaking various classes for compatibility with applications that use reflection to access internal capabilities, and fixing lots OpenJDK compatibility bugs.Android still needs to run dex bytecode somehow, so there are two possibilities for how N will work.Option one is that Android stick with ART and replaces Harmony with OpenJDK: from a technical perspective, that wouldn't be the end of the world, especially since the Harmony implementation is rather inefficient.Option two is that Google ports Hotspot to run on Android and, then has PackageManager convert dex bytecode back to Java bytecode on device. That would be awful, since ART is built for low-end devices and, well, Hotspot isn't.In favor of option one is that Google is still developing ART. In favor of option two is Oracle being Satan incarnate.I also wouldn't be surprised if Oracle has compelled Google to simply ship a copy of Hotspot, allowing developers to ship "authentic Java" APKs instead of dex-bytecode ones, with the two environments running in parallel, with two different zygotes.