For what it's worth, this still at least looks like it's mostly code from test frameworks, which doesn't necessarily even run on an Android device itself. So it could likely be dropped from the source distributions without compromising the functionality of any device. (Distributing it would still have been infringement --- but a lot more easily remedied than it might have been otherwise.)

Specifically, if we look at the PDFs from the original source here:

  http://fosspatents.blogspot.com/2011/01/new-evidence-supports-oracles-case.html

six of the seven Android files are in subpackages of "org.apache.harmony.security.tests". The Android version of Mueller's example number six, strangely, has no package declaration at all, but the name of the class (PolicyNodeImpl) at least is the same as one that has been identified as unit test code the last time it came up in this connection.

(BTW, the "org.apache.harmony" package prefix doesn't necessarily mean that the ASF ever distributed the particular file in question; that PolicyNodeImpl.java file was distributed by Google with an Apache Harmony package declaration, but had never been distributed by the ASF itself.)

There are a lot of problems which the engineer in me wants to code around that should really, really be solved by throwing money at it. Often, a trivial amount of money.

I once did several hours of work trying to optimize my use of Redis to avoid having to upgrade my VPS (I was nearing the limits of the physical memory at 1.5 GB). I even asked Thomas for advice on how to decrease memory usage. His reply: "How much to the next tier?" "$30 a month." "Why are we having this conversation?" And, of course, he was right.

Another reason is that it's written by a guy who has studied this company for years, interviewed Schmidt eleven times and links to his own Google book in the body of the article.

Freelance tech journalism, this ain't.