Argh! Widevine stopped working on my ARM device!

Note: Currently older ARM widevine versions are still working so the below isn't yet required

Who is affected?

Anyone using am ARM Linux device who plays back Widevine DRM content
Either via Kodi Add-ons or Chrome browser

Affects: LibreELEC, CoreELEC, Xbian, OSMC, Raspberry Pi OS & others
Android is not affected

See below on the status of the various OS's

LibreELEC 9.2.X (Kodi 18)

  1. Navigate to Kodi Settings > LibreELEC > Updates
  2. Set Automatic Updates to manual
  3. Set Update Channel to LibreELEC-9.2
  4. Select Available Versions then select 9.2.8
  5. Select Yes to update
  6. It will download the update, install it and reboot
  7. You can change Automatic Updates back to auto (optional)
  8. Once completed - see "Update Widevine" section below

LibreELEC 10.X (Kodi 19)

  1. Update to LibreELEC 10 Beta5 (June 27th, 2021) or higher
  2. Once installed - see "Update Widevine" section below

CoreELEC 19.X (Kodi 19)

  1. Update to CoreELEC 19.2-Matrix_rc2 (June 6th, 2021) or higher
  2. Once installed - see "Update Widevine" section below.

CoreELEC 9.2.X (Kodi 18)

OSMC (Kodi 19)

Raspberry Pi OS

In progress...

Xbian

In progress...

OSMC (Kodi 18)


Update Widevine

If you have an updated OS from above that supports the latest Widevine,
you now need to install the latest Widevine module

  1. Navigate to Add-ons > My Add-ons > Services > Slyguy Common
  2. Select it then select Configure
  3. Now select Playback > Install Widevine CDM
  4. Yes to any prompts and then select 4.10.2209.0
  5. Select Yes on the warning as you are now using a supported OS
  6. You should now be ready to go!


What happened?

As you can see above, Google removed support for any Widevine versions below 4.10.2252.0
on ChromeOS on May 31st 2021. Our current working version is 4.10.1679.0

Why does ChromeOS affect me on Linux?

Google does not (yet) provide an ARM build of the Widevine binary.
Therefore everyone has been using a Widevine binary pulled from an ARM ChromeOS image.
Which worked great... until now.

Why not just pull 4.10.2252.0 from latest ChromeOS image?

They have!

However, Google has made changes to it that don't allow the current method to open it.
In short - it has been compiled to use some specific "stuff" related to ChromeOS.

Some smart users have figured out this "stuff" and have found how to make the OS's work with it.

What can I do to help my OS?

  1. Please don't post on every forum / git repo saying "X is broken"
  2. Wait patiently

Discussion

Support