Android Lawsuits

Plaintiff. Oracle America, Inc. — which acquired Sun Microsystems and the Java intellectual property in January 2010 and filed suit seven months later.

Theory of liability. Oracle alleged that Android's reimplementation of 37 Java API packages copied roughly 11,500 lines of declaring code plus the structure, sequence, and organization of those packages, infringing Oracle's copyright in the Java platform. Google's defense had two layers: (1) API declarations and SSO are not copyrightable subject matter under 17 U.S.C. § 102(b), and (2) even if they are, Google's use was fair use under 17 U.S.C. § 107.

Procedural milestones. Filed August 12, 2010 in N.D. Cal. (Alsup, J.). First trial 2012: jury found copying but couldn't decide on infringement; Judge Alsup held the APIs uncopyrightable. Federal Circuit reversed in 2014, holding the declarations and SSO copyrightable. Second trial 2016: jury found fair use. Federal Circuit reversed again in 2018. Cert granted by the Supreme Court November 15, 2019. Argument October 7, 2020. Decision April 5, 2021.

The Supreme Court ruling. Justice Breyer, writing for a 6–2 majority (Justice Barrett did not participate), held that Google's copying was fair use as a matter of law. The opinion assumed without deciding that the API declarations were copyrightable, then walked through the four fair-use factors and concluded that the use was transformative, that the SSO was inherently functional, that Google copied only what was necessary to allow programmers to work in a familiar language, and that the market harm was speculative. Justice Thomas's dissent (joined by Justice Alito) argued that the majority effectively gutted copyright protection for declaring code by skipping the copyrightability question. Read the opinion (PDF) on supremecourt.gov.

Why it matters. The ruling is the most-cited US authority on software API copyright in the modern era and is now taught in every IP-law course. Its assumption-not-decision posture on copyrightability means the underlying question is technically still open at the Supreme Court level — but the practical effect was to end a wave of API-copyright assertions that had grown out of the Federal Circuit's 2014 ruling.

Cross-link. See Android Versions → Java API lawsuit for the Android-platform context (the Java-to-Kotlin shift on Android predated the SCOTUS ruling but was accelerated by it). For the Java-side narrative on the same case — the JCP, the Sun–Oracle handoff, and the Supreme Court's fair-use reasoning in context — see the Java Versions page.

Plaintiff. Epic Games — the Fortnite and Unreal Engine developer — following its parallel suit against Apple over the App Store. Filed in N.D. Cal. and consolidated with multidistrict litigation involving state attorneys general (39 states) and a consumer class.

Theory of liability. Epic alleged Google monopolized two markets in violation of Section 2 of the Sherman Act: (1) the market for Android app distribution and (2) the market for in-app payment processing on Android. The case attacked Google's bundled Play Billing requirement, the secret “Project Hug” payments to large developers to keep them on Play, and the technical / contractual barriers to alternative app stores including OEM revenue-share deals and the Google API anti-fragmentation agreements.

Procedural milestones. Filed August 13, 2020, the same day Epic was kicked off Google Play and the Apple App Store for inserting a direct-payment option. Trial began November 6, 2023 before Judge James Donato (N.D. Cal.). Verdict December 11, 2023 — jury found unanimously for Epic on every count. The verdict was striking partly because Epic v. Apple two years earlier had reached largely the opposite conclusion on overlapping theories, despite the two stores being structurally similar; the jury vs. bench-trial difference, the additional Project-Hug evidence, and the Android-specific OEM-deal record all factored into the divergent outcome.

The October 2024 injunction. Judge Donato issued a three-year remedial injunction in October 2024 with two principal Android-ecosystem-changing requirements: Google must permit third-party Android app stores to access the Play Store catalog of apps, and Google must allow distribution of third-party Android app distribution platforms or stores through the Play Store. Google was given eight months to comply with the catalog-sharing and store-distribution requirements. Behavioral remedies on Play Billing, sideloading flows, and OEM revenue-share deals were also included.

Ninth Circuit affirmance (July 31, 2025). The Ninth Circuit affirmed both the verdict and (with minor narrowing) the contours of the remedial injunction. The panel rejected Google's Trinko-based duty-to-deal argument, holding that Trinko addresses the legality of unilateral refusal to deal, not the legality of compelling a defendant already found liable under Section 2 to deal with rivals. Google sought a stay pending Supreme Court review; the Supreme Court denied the stay in October 2025, leaving Google under the active injunction while it pursues cert.

Why it matters. The injunction is the first remedial order in modern US antitrust law that compels a major platform to open its app catalog and store-distribution surface to direct competitors. Its mechanics — catalog access, third-party-store distribution through Play, anti-tying provisions on Play Billing — are being studied as the template for how any remedies regime against an integrated app-store-and-payment monopolist might work, including in the still-pending DOJ search and ad-tech remedies phases.

What to watch next. The Supreme Court cert petition. Google's compliance progress on catalog sharing and store distribution. The interaction with the EU Digital Markets Act's parallel sideloading mandates — which already require similar conduct in Europe and were a public point of comparison during the Ninth Circuit oral argument.

Cross-link. See Android Versions → Epic v. Google verdict for the platform context.

Plaintiffs. The United States Department of Justice plus a coalition of state attorneys general, in two consolidated complaints (DOJ filed October 20, 2020; the multi-state complaint followed in December 2020).

Theory of liability. The complaint alleged that Google maintained a monopoly in general search and search advertising in violation of Section 2 of the Sherman Act through a network of exclusive distribution agreements — the multi-billion-dollar default-search payments to Apple, the agreements with mobile carriers and OEMs that pre-installed Google Search and Chrome, and the Mobile Application Distribution Agreements (MADAs) governing Google Mobile Services on Android. The Android-specific MADA mechanics were a substantial part of the case-in-chief, even though the case isn't headlined as an Android case.

The August 5, 2024 liability ruling. Judge Amit Mehta issued a 277-page opinion finding Google liable for monopolization of two markets: general search services and general search text ads. The opinion specifically held that Google's exclusive default-search agreements with Apple, the major Android OEMs, and the major US wireless carriers were the principal mechanism by which Google maintained the monopoly. Google was held not liable on a separate search-advertising theory, narrowing the scope of remedies to general search.

Remedies trial (April–May 2025) and ruling (September 2, 2025). The remedies phase was a roughly three-week trial in spring 2025. The DOJ asked for, among other things, a forced divestiture of Chrome and structural relief on Android distribution. On September 2, 2025, Judge Mehta denied the divestiture requests — Google would not be required to sell or spin off Chrome, and Android would not be subject to structural relief — but ordered substantial behavioral remedies. The principal restrictions: (1) a six-year prohibition on exclusive distribution contracts for Search, Chrome, Google Assistant, and the Gemini app, and (2) mandatory sharing of Google's search index and certain user-interaction data (excluding ads data) with qualified competitors. The Apple default-search payment was specifically capped — any future agreement must terminate within one year of entry, ending the multi-year default-payment structure. The court explicitly noted that the rapid rise of generative-AI search interfaces (ChatGPT, Perplexity, Gemini app) changed the competitive landscape and reduced the case for structural separation.

Final order (December 5, 2025) and appeals. The remedies were finalized in a final order on December 5, 2025. Google filed its Notice of Appeal on January 16, 2026, targeting the data-sharing mandate and the technical-committee oversight provisions. The DOJ plus a majority-state coalition filed a cross-appeal on February 4, 2026, challenging the rejection of structural remedies including Chrome divestiture and the limits on data-sharing scope. The case is now in the D.C. Circuit on a multi-directional appellate posture with Google arguing the remedies went too far and the federal-state coalition arguing they did not go far enough.

Why it matters. The first US monopolization-liability ruling against a Big Tech platform in a generation, with the appeal positioned to set a multi-year precedent on the scope of remedies courts can impose on a platform monopolist. The Android-specific implications run through the MADA-distribution holding and the six-year exclusive-contract ban on Chrome and Gemini, which together reshape how Google can negotiate Android pre-install and default-app deals.

What to watch next. D.C. Circuit briefing on Google's appeal and the federal-state cross-appeal through 2026. Compliance progress on data-sharing infrastructure. Possible interaction with the EU Digital Markets Act, which already prohibits some of the same default-search and tying conduct in Europe.

Plaintiffs. The Department of Justice and a coalition of eight state attorneys general (Virginia, California, Colorado, Connecticut, New Jersey, New York, Rhode Island, and Tennessee). Filed January 24, 2023 in the U.S. District Court for the Eastern District of Virginia.

Theory of liability. The complaint alleged that Google illegally monopolized the digital advertising-technology “ad stack” through a series of acquisitions (DoubleClick in 2008, AdMeld, AdMob) and through tying its three principal ad-tech products: the publisher ad server (DoubleClick for Publishers / Google Ad Manager), the ad exchange (AdX), and the ad-buying platform (Google Ads / DV360). The complaint described a pattern of Google steering its publisher customers to its own exchange while running parallel auctions that gave AdX a structural advantage, and tying access to AdX to publisher use of Google's ad server.

The April 17, 2025 liability ruling. Judge Leonie Brinkema issued a 115-page opinion finding Google liable for monopolization of (1) the market for open-web display ad exchanges and (2) the market for publisher ad servers, plus illegal tying of those two products. The ruling did not find for the DOJ on the third theory — advertiser ad-buying tools — narrowing the scope of remedies to the publisher and exchange sides of the stack.

Remedies trial (September–October 2025). The remedies phase was a roughly two-week trial that began September 22, 2025 in Alexandria, Virginia. The DOJ asked the court to consider open-sourcing the logic behind Google's publisher ad server and a divestiture of Google's ad exchange (AdX). Google proposed behavioral remedies, including enabling publishers to use ad servers not affiliated with Google to access AdX demand. Judge Brinkema expressed skepticism about the proposed AdX divestiture, raising concerns about timing and feasibility.

Why it matters for Android. The case is structurally about web-display advertising, not Android. The Android connection runs through the integrated bidding and tying conduct identified by the court, since Google's mobile ad-stack on Android (AdMob plus the broader Google Ads infrastructure) sits alongside the open-web stack the case attacked, sharing infrastructure and policies. A structural remedy that breaks up Google's ad exchange would have downstream effects on how mobile-app monetization works on Android.

What to watch next. Judge Brinkema's remedies ruling. Whether the order is structural (AdX divestiture) or purely behavioral. Google's near-certain appeal to the Fourth Circuit. The interaction with related private litigation including a New York federal-court ruling in November 2025 that gave broad preclusive effect to the DOJ liability ruling in a related publisher class action.

Complainants. FairSearch (a coalition including Nokia, Oracle, and Microsoft at the time of complaint), Aptoide, Yandex, plus several other complainants. The Commission opened a formal investigation in April 2015.

Theory of liability. The Commission's Statement of Objections (April 2016) and the final Decision identified four interrelated abuses of Google's dominance in app-store, general-search, and licensable-mobile-OS markets: (1) tying the Play Store to mandatory pre-installation of Google Search and Chrome via the Mobile Application Distribution Agreements (MADAs), (2) anti-fragmentation agreements that forbade OEMs from selling devices running non-Google-approved Android forks, (3) revenue-sharing payments to OEMs and carriers conditioned on exclusive Google-Search pre-installation, and (4) restrictions on Android forks that, the Commission held, foreclosed alternative Android distributions.

The July 18, 2018 decision. The Commission found Google had abused its dominant position from January 2011 onward and imposed a €4.34 billion fine — at the time the largest antitrust fine in EU history. Google was ordered to bring the conduct to an end within 90 days. The behavioral remedies that Google implemented in response are what European Android users still see today: the Choice Screen (a setup-time prompt to choose a default search engine and browser on European Android devices), separate licensing of the Play Store from Search and Chrome, and the end of the OEM revenue-share-conditioned-on-exclusive-pre-install conduct.

General Court partial annulment (September 14, 2022). The General Court (the EU's first-instance court) upheld the substance of the Commission's findings on three of the four abuses, partially annulling the revenue-share-payments theory. The fine was reduced to €4.125 billion to reflect the partial annulment. The judgment is widely read as a strong endorsement of the EU's tying analysis under TFEU Article 102 in digital-platform cases.

Court of Justice ruling (September 10, 2024). The European Court of Justice (the EU's highest court) dismissed Google's appeal on September 10, 2024, upholding the General Court's judgment and the €4.125 billion fine. The case is now res judicata at the EU level.

The Choice Screen. The compliance mechanism Google implemented after the 2018 decision — requiring users to choose a default search engine and browser at device setup — has been amended multiple times in response to ongoing complaints from competitors that the implementation was non-compliant (initially an auction model that disadvantaged small search engines; later restructured after sustained complaints in 2024 to give all qualifying competitors free placement). The Choice Screen as it ships on European Android devices today is the direct lineage from this case.

Why it matters. The most consequential antitrust action against Google's Android distribution practices anywhere in the world, and the source of the only major Android-platform-level conduct remedy that has actually shipped to consumers (the Choice Screen). The 2024 ECJ affirmance closed the European litigation track but the Digital Markets Act (DMA, in force from March 2024) has since taken over as the principal EU regulatory tool against the same conduct.

Cross-link. The Choice Screen is referenced on Android Versions wherever it shaped a release.

Acting agency. The U.S. Department of Commerce's Bureau of Industry and Security (BIS), which administers the Export Administration Regulations (EAR) and the Entity List of foreign parties subject to specific export-license requirements.

Action. On May 15, 2019, President Trump issued Executive Order 13873 declaring a national emergency over information-and-communications-technology supply-chain risks. The next day, May 16, 2019, BIS published a final rule (84 Fed. Reg. 22,961) adding Huawei Technologies and 68 of its non-US affiliates to the Entity List, requiring a license (presumed denied) for any export, re-export, or in-country transfer of items subject to the EAR to Huawei. The practical effect was that US software companies, including Google, could no longer license their proprietary products to Huawei without a specific license.

The Android consequence. Within days, Google confirmed that Huawei would lose access to Google Mobile Services (GMS) — the proprietary layer that includes the Play Store, Google Play Services, Google Maps, Gmail, YouTube, Firebase Cloud Messaging push-notification infrastructure, and the SafetyNet / Play Integrity attestation APIs. Huawei retained access to the Android Open Source Project (AOSP) base, since AOSP is permissively licensed and not subject to export controls, but lost access to everything Google ships on top of AOSP. Huawei phones produced after the cutoff ship with AOSP plus Huawei's own Huawei Mobile Services (HMS) layer instead.

HarmonyOS. Huawei accelerated its long-running internal HarmonyOS project after the entity-list designation. Initially HarmonyOS shipped as a layer atop AOSP on phones (HarmonyOS 2.0 and 3.0), with the same app surface as Android. With HarmonyOS NEXT (general availability 2024), Huawei shipped a fully independent OS that does not run Android apps at all — a complete decoupling from the Android ecosystem on Huawei's flagship devices. Huawei has continued to ship some lower-tier phones on the older AOSP-plus-HMS combination.

Why it's on this page. The Huawei break is not a lawsuit and does not have a court-docket page or a settlement number. But it is the cleanest example of US export-control policy reshaping a consumer-software ecosystem in real time, and the cleanest stress test of the AOSP-vs-Google-Mobile-Services distinction: it is the answer to "what happens to Android phones when Google can't ship its proprietary layer." It also shapes how visitors think about the lawsuits above, since several of them turn on the structural separability of AOSP from GMS — a distinction the Huawei episode made operationally real.

Cross-link. See Android Versions → The Huawei break for the platform context.