LightBlog

mercredi 30 décembre 2020

Some ROG Phone 3 and ZenFone 7 owners are having issues with HD playback in Netflix

Some owners of the ASUS ROG Phone 3 and ZenFone 7/7 Pro have discovered that their devices have lost Widevine L1 status. As a result, they’re unable to play Netflix content in HD.

Users have taken to ASUS’ forums to voice their complaints. Seems the issue has persisted over several weeks now with no signs of going away.

Widevine is a DRM technology used by many streaming services like Netflix and Amazon Prime Video to ensure that these services are being used by devices with unmodified and secure firmware.

Without Widevine L1 status, users are unable to stream videos from Netflix above 540p quality. Unfortunately, due to a bug in the SoC firmware of the ROG Phone 3 and ZenFone 7 (both are powered by the Qualcomm Snapdragon 865), the Widevine DRM level is being downgraded from L1 to L3 for a handful of users. The only way to fix this, according to ASUS, is for the affected users to ship their devices to ASUS so they can re-provision them.

ASUS released a statement regarding the issue:

“Asus is aware of this issue which affect a small number of users and is caused by a bug from our SOC vendor Qualcomm,” ASUS said. “If this has happened we urge you to contact Asus customer service in your region.”

Some users in the forums have stated that after getting their phone fixed, the issue has reared its head again.

“I have this issue happened to me after that service center resolved my issue but the issue happened to me AGAIN today,” user yashpandya295 said in the ASUS forums. “So I have to visit service center again.”

For what it’s worth, we checked our ROG Phone 3 and ZenFone 7 review units and our Widevine level hasn’t been downgraded. To check your own Widevine DRM level, download the DRM Info app.

DRM Info (Free, Google Play) →

The post Some ROG Phone 3 and ZenFone 7 owners are having issues with HD playback in Netflix appeared first on xda-developers.



from xda-developers https://ift.tt/3hsNTch
via IFTTT

Aucun commentaire:

Enregistrer un commentaire