Chromecast has been one of those smaller hardware products that have brought about a meaningful experience upgrade. The first Chromecast solved the pain point of clunky TV software interfaces, making it easier to locate content on your handy smartphone and then play it on your big-screen TV. However, a Court in the US has ruled that Google has infringed upon patents with its Chromecast products and that it should pay $338.7 million in damages because of it.

A Western District of Texas jury has ruled that Google has violated three patents held by a company called Touchstream Technologies, as reported by ArsTechnica. The complaint points to several Chromecast products, including the Chromecast Ultra, the Chromecast with Google TV, and other Chromecast-integrated products.

The first patent application in this complaint was filed in April 2011. The three patents relate to “a system for presenting and controlling content on a display device.”

Further, the complaint claims that Touchstream met with Google in December 2011 but was told that the tech giant wasn’t interested in partnering with it in February 2012. For reference, the first generation Google Chromecast was released in 2013. The latest Chromecast with Google TV (HD) was launched in September 2022, while the 4K variant was launched earlier in September 2020.

Chromecast with Google TV HD box 2 Google opposed the complaint, arguing that the patents are “hardly foundational and do not cover every method of selecting content on a personal device and watching it on another screen.” Further, the Chromecast is said to differ in technologies detailed in Touchstream’s patents.

The jury agreed with Touchstream’s allegations and ordered the company to pay $338.7 million in damages for its patent violations.

Google intends to appeal this decision, as mentioned by their spokesperson in their statement to ArsTechnica.

  • chinpokomon@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I selected “was” simply because I don’t have enough understanding of the current situation to argue it from that standpoint.

    In many ways, Chromecast is superior. Removing the rendering task from the tablet or phone, and letting the receiver manage that, it’s significantly better than making the mobile device decompress the source stream and then decompress it for a Miracast receiver. The only real advantage Miracast has in this is that it doesn’t need to receive firmware updates to keep it up to date with newer protocols. With Miracast being built in to TVs, and possibly implemented in an ASIC, it should be a universal fallback. With Android 4.2 it was a built in protocol to AOSP. What I didn’t know was that it was actually stripped back out with Android 6. I thought dropping support was specific to Google devices only.

    What really needs to be implemented is a non-proprietary extension to Miracast which goes back to the early Chromecast days when it was based on the DIAL protocol. It’s incredible that we have to deal with so many proprietary standards from Airplay and Chromecast, and then also support the wifi alliance standard for Miracast.

    • dustyData@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      They have different objectives honestly. Miracast was supposed to stream frames exclusively. Chromecast hands datastreams to the target device who then has to do the heavy lifting, sometimes even fetching the source itself. Entirely different use cases and tech stacks. I would like to show my PC screen on the living room. I can’t do that without paying either Google or Valve (still Google), despite the fact it is not technically difficult or complex with contemporary technology to stream raw frame buffers to a screen. But that’s patent trolling and monopolies. They will sap all the fun out of tech for those extra pennies.

      • chinpokomon@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        They are different as you and I have both described, but when the sink device can support different streams, it has a significant advantage, because it automatically can support sinking frames from the broadcasting device and it removes the overhead of decompressing and then recompressing with practically assured data loss. It is yet another example of how patents, especially software patents, work against the original intent of the patent process.