Check for truly new version

[cpy82]

That might be a stupid question, but is there perhaps a possibility that the Inputstream Helper could check whether a new version of libwidevinecdm.so is actually available?

As noted in the #615 (comment), for example, this is the current latest version of libwidevinecdm.so, but it's already several years old. This means that the same version is being installed repeatedly on a regular basis.

Or is there no way to check this in advance, but only after it has been installed?

Thank you!

[mediaminister]

As far as I know this cannot be easily implemented for libwidevinecdm.so on ARM devices because the Widevine CDM version number for ARM devices is not published by a known Google API. The Widevine CDM is only available inside a zipped Chrome OS recovery image and must be extracted first to read the version number.

Currently, InputStreamHelper reads the Chrome OS recovery version info from a Google API (recovery.json) and notifies the user when a new Chrome OS version is available. But the Widevine CDM version number is only checked after extraction.

You can set the update frequency from 31 days to 90 days in InputStreamHelper settings to limit these notifications.

If these unnecessary reinstallations bother you, would it help to add a setting to completely disable update notifications for ARM devices?

[cpy82]

As far as I know this cannot be easily implemented for libwidevinecdm.so on ARM devices because the Widevine CDM version number for ARM devices is not published by a known Google API. The Widevine CDM is only available inside a zipped Chrome OS recovery image and must be extracted first to read the version number.

Currently, InputStreamHelper reads the Chrome OS recovery version info from a Google API (recovery.json) and notifies the user when a new Chrome OS version is available. But the Widevine CDM version number is only checked after extraction.

Thanks for the reply! I already suspected something like that.

You can set the update frequency from 31 days to 90 days in InputStreamHelper settings to limit these notifications.

Yes, that's right! Good idea!

If these unnecessary reinstallations bother you, would it help to add a setting to completely disable update notifications for ARM devices?

Maybe this could be interesting for someone else, but personally, I don't need it implemented. I don't think completely disabling it is a sustainable long-term solution, especially if a new version should appear at some point.

Maybe at some point, some way will emerge to actually check the current version and determine whether a newer one is available, or the update process could be aborted earlier once it's clear that no newer version exists—although the download and extraction are probably going to take up the most time anyway.