Some questions about widevine

[Franco Palombo]

After trying to install Netflix on my android x86 setup, I got so disappointed when I discovered that for us, android x86 users, there is no HD DRM protected content to watch. I wasn't able to belive this, so I started researching a bit. I've found out that some people found a way arround using Google Chrome, or Microsoft edge, and using the web version of Netflix. I've got no luck on doing that. It seems like the version that I've installed of android x86, makes google chrome, unable to install the corresponding plugin to play DRM content. After hours of looking on the web, entering the same websites again, and again, and again, to see if I was able to find another solution, I gave up. I even tried searching "HD MOD NETFLIX FOR NON L1 DEVICES", but no solutions worked given the status of android x86.

With my last bit of hope, I decided to search in how to get L1 certification to play HD DRM protected content, and, I think that I've found something. Idk if its going to work, besides the fault from android x86 devs (completely understandable if you guys cannot/don't want to do this) or simply not meeting the requirements to get a widevine certification. What I've fount (that really surprised me), is that, to get a widevine certification, there are no needs to pay anything to anyone. As I was reading through this article, most OEMs, don't add widevine, not because the lack of money/lowering the price of the product, it's basically, because a lack of time caused by the delay while creating the product, and not having enough time to pass all widevine tests. That last sentence, made me belive that L1 certification could be a thing in android x86, so, then, on the same article, it explains what are the requirements to have a L1 certification:

1-Having a TEE (Trusted Execution Environment)

2-All content (cryptography) being processed in the TEE

The first point, scared me a bit, and I thought that it might be a hard thing to do, but, I don't think it's impossible. As it says in the article, most mobile phones with ARM CORTEX-A architecture, have this TEE implemented on the cpu design. I don't know if desktop cpus have something similar, but, there migth be a way to implement it (isn't it?) Anyway, i would like to know others opinion, because im not a developer, and i dont know all things that have to be done to achieve different things.

Regards

[Daniel Cheung]

Have you tried an older version of Netflix from APKMirror? I had to use 4.16 and side loaded into my tablet for it to get around the rooted status. It seems like it's running at 1080p 30FPS. My device won't support a higher resolution because Intel HD driver isn't that developed.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/5474c19f-c544-41b8-9b6b-147d150f06bbn%40googlegroups.com.

[Franco Palombo]

Im actually using 4.16.4 build 200217, and using the Netflix test patterns, i can see that it wont go up than 480p30. Can you send me your apk file (if you still have it), so i can test it? Maybe i did something wrong. btw, im not interested in reproducing contentin higher quality than 1080p, because where i plan to leave this pc, is on a 1080p ultrathin TV, so, its ok

[Daniel Cheung]

The APK is 25MB so not sure if it will attach correctly. You can look for it on APKMirror for this version:

com.netflix.mediaclient_4.16.0_build_15120-15120_minAPI19(armeabi-v7a)(nodpi)_apkmirror.com

Since it's an ARM version, make sure your native bridge is turned on.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/8c1c7a0b-9a13-45ac-aa0f-460524ab417fn%40googlegroups.com.

[Michael Goffioul]

Android-x86 cannot get Widevine/L1 certification, because that level of encryption is bound to the hardware. Android-x86 is a software-only distribution. Also android-x86 does not include codecs that would support a full secure media path. 

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/8c1c7a0b-9a13-45ac-aa0f-460524ab417fn%40googlegroups.com.

[Franco Palombo]

Well, it seems like android x86 is a no-go for what i want to do. Also, using the apk that BrokenE39 said that he had at 1080p, dosent seems to work. I can still only play content up to 480p only

very sad :(

[Christian]

4.13.3 works for me, anything else (higher) not.

[BrokenE39]

Hmm I reinstalled 9r2 and 4.16 stop working, it would constantly try to update itself, fails and crash. Tried 4.13.0 as well and the same problem happens. Disabling root doesn't have an impact on the problem. Anyone manage to get around this? Or we are completely locked out of Netflix since Android X86 doesn't support widevine?

[Jon West]

Use this version, it might not be what you're looking for, but it works for me https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-7-64-0-build-19-34976-release/netflix-7-64-0-build-19-34976-android-apk-download/

[Michael Goffioul]

I think the main point here was to get 1080p, which you can only access with Widevine/L1, hence not possible on android-x86. Otherwise Netflix is working fine with Widevine/L3.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/855d0428-6234-4798-8b0a-f2c90012c9cdn%40googlegroups.com.

[Daniel Cheung]

Interesting that even Youtube is now stuck at 720p. I don't recall having this issue when I was running 9.0 R2 back in June. I was running 7.1 between July and Oct but want to try using GRALLOC=gbm to fix the wake & crash issue. Wondering if GRALLOC is the root cause. I'll have to test since even the APK Jon suggested is not working.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CAB-99Lu7wGXyc09D4tUk8bGviWPTvLiecNrFkW3Xdt4bt5Pk_Q%40mail.gmail.com.

[Daniel Cheung]

Nope. GRALLOC got nothing to do with the problem I'm seeing. The APK Jon suggested basically says my device is not compatible. And YouTube is giving me 720p because the video is only available in 60 fps format. Other videos in 1080p 30fps work just fine.

[Michael Goffioul]

Do you have functional widevine support in your build? E.g. one way to check (which I use) is the DRM Info app (https://www.apkmirror.com/apk/android-fung/drm-info-2/drm-info-2-1-1-7-201102-release/). If this does not report widevine support, Netflix is not gonna work.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CAFgJqCcCTBAc-wZEZ5j64n-De0bD3%3DKsU5wx5dMTmHQpT_thxg%40mail.gmail.com.

[Jon West]

Are you adding widevine to your config? https://github.com/BlissRoms-x86/android_vendor_google_chromeos-x86 is what I'm using to include it in my builds. Only L3, but better than nothing ;) 

[Daniel Cheung]

I haven't had the chance to double check. There's a possibility that I removed it not knowing what it was to reduce the ROM size. Need time to sync the 9.1 R2 repo and make edits to BT and WiFi modules.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/0ae26454-7e55-4610-9c02-ba632417e34fn%40googlegroups.com.

[BrokenE39]

OK, I was under the impression that it's part of Android X86 source code. That explains why I couldn't find it when I'm looking at the kernel configuration GUI. I then did a search in my old Android 7 source folder and found com.google.widevine.software.drm in OpenGAPPS source files that I checked out. However, it only exists for framework 19, 24, and 25. Since Android 7 = 24, that explains why it was working in my Android 7 install a few weeks ago. I'm going to try copying it to framework 28 (Android 9) and then build a new image.

[Daniel Cheung]

Well not sure if I tested correctly with copying the widevine jar file in OpenGAPPS since I was using the 480 min dpi version (my tablet is 240 dpi). But using the Bliss OS widevine source code + no dpi version of Netflix 7.64, I manage to log into Netflix and start a video. Thanks for pointing me in the right direction Jon.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/2432c2e3-062f-41a6-ac31-1522cbcdd49dn%40googlegroups.com.