This really has nothing to do with Java (the language, library or tooling) other than Google not wanting to use Java ME for obivious reasons (licencing and lacking features).
So Google sees Java SE as the only choice, but Java SE contains too much library code without use to their platform (Windowing toolkits for example). But cutting that out from their Java SE implementation and creating a subset of the Java API means they can't use Sun/Oracles JDK and they can't call it Java. So they go with Apache Harmony (which isn't officially Java, since they haven't been able to run the Technology Compatibility Kit (TCK) as Apache doesn't want to pay money, nor is based on OpenJDK).
Now the next thing Google needs to replace is the JVM for both technical (optimize for embedded hardware) and to not be a Java platform. Enter the Dalvik VM which runs its own bytecode and is not based on Hotspot.
The result, Java ME is dead by Google's hands, Sun got pissed but didn't want to cause havok to the Java community and didn't do anything, despite losing their cash cow. Oracle doesn't really care about that and chooses to sue, but Google obviously have tried very hard to publicly state that Android + Dalvik isn't Java, so Oracle can't really do anything there. The only thing left to do is patent infringement for the patents they got on techniques in the JVM, which means that it's not limited to a Java VM. Sure they could say Google only did this to get around paying money to use the JVM and Java platform but still use Java the language (which the obviously did).