3 ms·
His comment doesn't seem to amount to anything. His contention is that the files are still there in AOSP git tree when the key point was that those are "TESTS"
by blinkingled 16y ago
His comment doesn't seem to amount to anything. His contention is that the files are still there in AOSP git tree when the key point was that those are "TESTS" which means they are likely not "shipped" with Android and so the assumed impact if any is not anywhere near as dire as the original Engadget post or Folrian's own blog post made it out to be.
EDIT: Ryan Paul's take - http://arstechnica.com/open-source/news/2011/01/new-alleged-evidence-of-android-infringement-isnt-a-smoking-gun.ars http://arstechnica.com/open-source/news/2011/01/new-alleged-... . He confirms that the files in question are non-shipping ones.
- moondowner 16y agoRyan's post is good, he explains things more thoroughly. Very important: "It's not clear how the zip file got included in the AOSP, but it's obvious that it wasn't intended to be there and isn't actually used by Android in any capacity."