Google's Android Appeal Rejected by Supreme Court

Oracle's copyright lawsuit against Google over Android now returns to a lower court.

Thomas Claburn, Editor at Large, Enterprise Mobility

June 29, 2015

4 Min Read
<p align="left">Image: <a href="">Oracle v. Google evidence</a></p>

9 Ways Technology Is Slowly Killing Us All

9 Ways Technology Is Slowly Killing Us All

9 Ways Technology Is Slowly Killing Us All (Click image for larger view and slideshow.)

The US Supreme Court on Monday declined to hear Google's argument to overturn a federal appeals court ruling that Oracle's Java APIs qualify for copyright protection.

The case now returns to a lower court to determine whether Google's use of Oracle's copyrighted APIs can be excused as fair use.

The Supreme Court's rejection of Google's appeal represents a major victory for Oracle, which in 2012 saw its patent claims against Google rejected and its copyright claim invalidated. After the jury in the case deadlocked over whether Google's use of Java in Android qualified as fair use, US District Court Judge William Alsup ruled that Oracle's Java APIs were not protected under copyright law, a decision that echoed a similar finding in a different case by the Court of Justice of the European Union.

But Google's victory did not last. The US Court of Appeals for the Federal Circuit in Washington reversed Alsup's decision in May 2014. And now the Supreme Court has refused to review that ruling.

"Today's Supreme Court decision is a win for innovation and for the technology industry that relies on copyright protection to fuel innovation," said Oracle general counsel Dorian Daley in an emailed statement.

[ Talk nerdy to me. Read 10 Smartphone Apps You Can Talk To. ]

Google did not respond to a request for comment.

A group of intellectual property professors concerned about the case argued in a brief that the Supreme Court should consider Google's appeal to ensure ongoing software innovation. "Unless reversed, [the Federal Appeals Court decision] is likely to have a chilling effect on the willingness of software startup firms and open source developers to create innovative programs that can be executed on incumbent firm platforms," the group argued.

Mike Godwin, general counsel and director of innovation policy for R Street Institute, a free market think tank that has received funding from Google, said in an emailed statement that contrary to the Federal Circuit decision, APIs should not be copyrightable. "APIs are more like functional descriptions, like the recipe for your favorite dish, than they are the kind of creative expression that copyright law is designed to protect," he said.

If Google manages to convince the lower court hearing the case to accept its incorporation of Java APIs in Android as fair use, it will escape unscathed, apart from the cost of the litigation. But interested parties like the Department of Justice have asserted that Google's fair use argument is undermined by its decision to make Android incompatible with the Java platform. Interoperability represents one reason that copyright infringement in software might be allowed as fair use.

Google could settle with Oracle, which presumably would end up with Google paying a significant sum – Oracle initially sought a billion dollars in damages – and negotiating a license from Oracle to continue to use its intellectual property. But it's unlikely Google will give Oracle that kind of leverage over Android unless it has no other options.

Google has already take some steps to distance itself from Oracle going forward. Android's recently introduced ART virtual machine, for example, appears to be an escape from its previous Dalvik virtual machine, which Oracle claimed infringed its patents. Google may have further technical changes prepared, though any such alterations to Android would not address past infringement.

Google's predicament appears to be one of its own making. Florian Mueller, an intellectual property blogger who has worked as a consultant for Oracle, argued that, had Google chosen to release Android under the GPLv2 license that governs Java, it might have had a stronger argument for its use of Oracle's Java APIs. However, by doing so, Google would have ended up with less control over Android's evolution. Instead, Google published Android under the Apache license, for reasons that it explains, such as appeasing device makers who don't want to abide by GPLv2 license requirements. The price for that decision could be significant.

About the Author(s)

Thomas Claburn

Editor at Large, Enterprise Mobility

Thomas Claburn has been writing about business and technology since 1996, for publications such as New Architect, PC Computing, InformationWeek, Salon, Wired, and Ziff Davis Smart Business. Before that, he worked in film and television, having earned a not particularly useful master's degree in film production. He wrote the original treatment for 3DO's Killing Time, a short story that appeared in On Spec, and the screenplay for an independent film called The Hanged Man, which he would later direct. He's the author of a science fiction novel, Reflecting Fires, and a sadly neglected blog, Lot 49. His iPhone game, Blocfall, is available through the iTunes App Store. His wife is a talented jazz singer; he does not sing, which is for the best.

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like

More Insights