DCT

1:26-cv-00555

Earin Ab v. Skullcandy Inc

Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:26-cv-00555, D. Del., 05/13/2026
  • Venue Allegations: Venue is alleged to be proper in the District of Delaware because Defendant Skullcandy, Inc. is a Delaware corporation and has allegedly committed acts of infringement in the district.
  • Core Dispute: Plaintiff alleges that Defendant's wireless earbud products infringe a patent related to the automated power management and connection logic for true wireless stereo (TWS) earbuds.
  • Technical Context: The technology governs the fundamental user experience of modern TWS earbuds, specifically how they automatically power on, connect to each other, and connect to a host device when removed from a charging case.
  • Key Procedural History: The complaint notes a prior, related patent infringement action between the same parties involving the same patent (Earin AB v. Skullcandy, Inc., No. 24-cv-275-RGA), which may be relevant to the complaint's allegations of willful infringement.

Case Timeline

Date Event
2014-09-05 '120 Patent Priority Date
2015-10-06 Plaintiff Earin launches its M-1 TWS earbuds
2016-07-26 '120 Patent Issue Date
2026-05-13 Complaint Filing Date

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 9,402,120 - "Wireless Earbuds"

  • Patent Identification: U.S. Patent No. 9,402,120, "Wireless Earbuds," issued July 26, 2016.

The Invention Explained

  • Problem Addressed: The patent's background section notes that for wireless earbuds to become popular, key characteristics such as "convenience and user-friendliness, duration between battery chargings, [and] operational reliability" are important '120 Patent, col. 1:20-22 The implicit problem is the need for a seamless and power-efficient method for managing the earbuds' various connection states without requiring constant user intervention.
  • The Patented Solution: The patent describes circuitry with an automated logic sequence for managing an earbud's operational state '120 Patent, col. 1:41-2:4 When an earbud is disconnected from its charger, it automatically enters an "operational mode" by first attempting to establish a "true wireless stereo" (TWS) connection with its partner earbud '120 Patent, col. 10:12-18 If that connection fails, it defaults to a "mono" mode '120 Patent, col. 10:20-24 If the TWS connection succeeds, one earbud is designated the "master" and attempts to reconnect to a known host device (e.g., a smartphone) '120 Patent, col. 10:28-32 This automated sequence, detailed in a flowchart (Fig. 12), is designed to provide a seamless user experience while preserving power.
  • Technical Importance: This type of automated state management-transitioning from charging to TWS pairing to host connection-became a foundational element for the user experience across the TWS earbud industry.

Key Claims at a Glance

  • The complaint asserts at least independent claim 20 '120 Patent, col. 13:58-15:14
  • The essential elements of independent claim 20 include:
    • A wireless earbud with standard components (housing, loudspeaker, battery, circuit board).
    • Circuitry configured for "automatic power preservation."
    • Detecting connection to a charger and entering an "idle mode" where existing connections are disconnected.
    • Detecting disconnection from the charger and entering an "operational mode."
    • In operational mode, first "attempting a true wireless stereo, TWS, reconnection with the second wireless earbud."
    • If the attempt is successful, operating as a TWS receiver; otherwise, operating as a "mono wireless audio receiver."
    • If operating in TWS, determining whether the earbud is a "master" or "slave" device.
    • If it is the master device, "attempting to reconnect with the wireless audio streaming host device."
    • If reconnection to the host device fails, initiating a "pairing procedure" with the host device.
  • The complaint alleges infringement of "one or more claims of the '120 Patent, including at least claim 20," reserving the right to assert other claims '120 Patent, ¶20

III. The Accused Instrumentality

Product Identification

The complaint identifies the "Accused Products" as the Skullcandy Push 540 Open, Method 540 ANC, Dime 360, Smokin' Buds 360, Push Active, and EcoBuds, along with "substantially similar versions" Compl. ¶2 Compl. ¶20 The complaint also references the Push 720 Open when discussing infringing features Compl. ¶25

Functionality and Market Context

The complaint alleges that the Accused Products are wireless earbuds that practice the claimed invention through advertised features such as "multipoint pairing and automatic reconnection" Compl. ¶3 Specific functionalities cited as infringing include "charger-detect, true-wireless-stereo reconnection, solo/mono operation, and host-device pairing" Compl. ¶3 The complaint further points to marketing terms like "Auto On/Connect," "Use Either Bud Solo," and "multipoint pairing" as evidence that the Accused Products perform the claimed logical steps Compl. ¶¶25, 27, 28

No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

'120 Patent Infringement Allegations

Claim Element (from Independent Claim 20) Alleged Infringing Functionality Complaint Citation Patent Citation
an earbud housing; a loudspeaker element; a rechargeable battery; and at least one main printed circuit board having disposed thereon circuitry for wireless radio communication, audio codec and earbud operation control; The Accused Products are wireless earbuds that include advertised drivers (loudspeakers), rechargeable power, Bluetooth connectivity, and control circuitry on a printed circuit board. ¶24 col. 5:36-44
wherein the circuitry is configured for automatic power preservation by: detecting connection of said battery to a charger and in response entering the idle mode, wherein existing connections to a second wireless earbud and to a wireless audio streaming host device will be disconnected; The Accused Products are designed to be placed in a charging case, at which point they allegedly enter an idle or power-preservation state and disconnect existing wireless links. ¶26 col. 10:3-9
and detecting disconnection of said battery from said charger and in response entering the operational mode by: attempting a true wireless stereo, TWS, reconnection with the second wireless earbud; When removed from the charger, the Accused Products allegedly power on and automatically attempt to connect to each other for stereo operation, as reflected by "Auto On/Connect" and "true wireless operation" features. ¶27 col. 10:10-18
if the attempt is successful, operating the wireless earbud as a TWS audio receiver and otherwise operating the wireless earbud as a mono wireless audio receiver; The Accused Products allegedly support both stereo operation and solo-earbud (mono) use, which reflects the claimed fallback to mono operation if a TWS connection is not established. ¶27 col. 10:19-24
if operated as a TWS audio receiver, determining whether the wireless earbud is a master device or a slave device with respect to the second wireless earbud; The complaint alleges that when the Accused Products establish a TWS connection, one earbud acts as the primary or "master" earbud for host communication. ¶28 col. 10:25-27
if the wireless earbud is determined to be a master device, attempting to reconnect with the wireless audio streaming host device and other known wireless audio streaming host devices if applicable; This functionality is allegedly reflected in the products' ability to reconnect to previously paired host devices, advertised as "Auto On/Connect" or "Auto Connect" functionality. ¶28 col. 10:28-32
and if reconnection with the wireless audio streaming host device fails, initiate a pairing procedure with the wireless audio streaming host device and other known wireless audio streaming host devices if applicable. The complaint alleges this is satisfied by features like "Auto On/Connect, Auto Connect, Google Fast Pair, multipoint pairing, and Bluetooth pairing," which initiate pairing when an automatic reconnection to a host device fails. ¶29 col. 10:46-52
  • Identified Points of Contention:
    • Scope Questions: A central question may be whether the general marketing terms cited in the complaint (e.g., "Auto On/Connect") correspond precisely to the specific, ordered, and conditional sequence of logical steps required by claim 20. The defense may argue that its products achieve a similar user-facing result through a technically distinct, non-infringing method.
    • Technical Questions: The complaint's allegations are based on "publicly available information" and "pre-suit investigation" Compl. ¶22 A key question for the court will be what technical evidence Plaintiff can produce to demonstrate that the accused earbuds' firmware executes each step of the claimed process. For example, does the accused "solo-earbud" mode function as a fallback after a failed TWS connection attempt, as the claim requires, or is it initiated by a different trigger?

V. Key Claim Terms for Construction

  • The Term: "attempting a true wireless stereo, TWS, reconnection with the second wireless earbud"

  • Context and Importance: This term defines the first critical action an earbud takes upon being removed from its charger. The definition of "attempting" will be crucial for determining whether the accused products' "auto-connect" features meet this limitation, as it dictates the start of the claimed logical cascade.

  • Intrinsic Evidence for Interpretation:

    • Evidence for a Broader Interpretation: The plain language "attempting" could be argued to encompass any action taken by the earbud to seek a connection with its counterpart, regardless of the specific protocol or duration. The specification states in general terms that "a true wireless stereo, TWS, reconnection... will be attempted" '120 Patent, col. 10:15-18
    • Evidence for a Narrower Interpretation: The patent's flowchart in Figure 12 provides a more structured context for the "attempt." It shows the attempt (126) followed by a check for success (128, 140) and a "reconnection timer" (132). A party could argue that a true "attempt" under the patent must be part of such a timed, conditional process, not just a simple broadcast signal.
  • The Term: "operating the wireless earbud as a mono wireless audio receiver"

  • Context and Importance: This term is critical because it is not merely about using one earbud, but about when and how that mono state is entered. The claim requires it to be a consequence of a failed TWS reconnection attempt. Practitioners may focus on this term because it links the "mono" or "solo" feature to a specific condition precedent.

  • Intrinsic Evidence for Interpretation:

    • Evidence for a Broader Interpretation: A party could argue that any mode in which a single earbud functions as a "mono wireless audio receiver" satisfies this element, as long as it is an alternative to TWS operation.
    • Evidence for a Narrower Interpretation: The claim language states "if the attempt is successful, operating... as a TWS audio receiver and otherwise operating... as a mono wireless audio receiver." The word "otherwise" directly links the mono operation as the alternative outcome to a failed TWS connection attempt. Figure 12 reinforces this, showing the path to "Mono-mode enabled" (144) is taken only if the "TWS connected?" check (140) is "No." This suggests mono operation is not just a selectable feature but a specific fallback state.

VI. Other Allegations

  • Indirect Infringement: The complaint focuses on direct infringement under 35 U.S.C. § 271(a) and does not plead separate counts for indirect infringement Compl. ¶30
  • Willful Infringement: The complaint alleges that Skullcandy's infringement is and has been willful Compl. ¶32 The basis for this allegation is Skullcandy's purported knowledge of the '120 Patent from having been sued previously by Earin on the same patent in a prior case, Earin AB v. Skullcandy, Inc., No. 24-cv-275-RGA (D. Del.) Compl. ¶32 The complaint asserts that despite this notice, Skullcandy continued its conduct and released new infringing products Compl. ¶32

VII. Analyst's Conclusion: Key Questions for the Case

  • A primary issue will be one of functional specificity: do the accused products' "Auto On/Connect" and "Use Either Bud Solo" features perform the precise, ordered, and conditional sequence of operations mandated by claim 20? The case will likely depend on whether Skullcandy's implementation is merely a different path to a similar result or a direct mapping to the patent's specific logical flowchart.
  • A second key question will be evidentiary: can Earin provide detailed technical evidence from reverse engineering or source code analysis that proves the internal firmware of the accused earbuds executes every step of the claimed method, particularly the fallback from a failed TWS connection attempt to mono mode? The dispute may hinge on whether there is a literal, step-for-step correspondence in software logic or a "fundamental mismatch in technical operation."
Loading Complaint