CastagnaIT / plugin.video.netflix

InputStream based Netflix plugin for Kodi
MIT License
1.91k stars 259 forks source link

Shield v8.0.0 (Pie) killed Kodi Netflix #152

Closed beardie79 closed 4 years ago

beardie79 commented 5 years ago

I'm submitting a ...

General information

Pie update on shield killed Kodi Netflix

Addon version used

14.6

Description

Tried re-install no joy. Stalls on loading.

Steps to Reproduce

Upgrade Shield to v8

Context (Environment)

Installation

Operating System

wintuxx commented 5 years ago

Hi, i got the same problem, but it is not a issue from netflix addon. it is an issue from inputstream i think.

https://github.com/peak3d/inputstream.adaptive/issues/293

HDGuy commented 5 years ago

Hi, i got the same problem, but it is not a issue from netflix addon. it is an issue from inputstream i think.

peak3d/inputstream.adaptive#293

The Amazon Inputstream addon still works for me after the Shield 8.0 update but like everyone else the Netflix addon no longer works.

Smeulf commented 5 years ago

killed

Stalls on loading

no longer works

That's not a very large description of the problem. Any error message? How does it behave? How is it broken?

Please can someone install "DRM Info" and tell us what is Windevine CDM Security Level?

Can you provide debug logs with no extra component logged for now?

What's your setup regarding VP9 and HEVC?

Help us so we can help you. Without logs and proper description of the issue, there's no way we can understand the problem!

HDGuy commented 5 years ago

I'm surprised you guys don't have a Shield, as it's probably one of the most used platforms for Kodi.

In any event:

Widevine CDM Security Level- L1

As far as VP9 and HEVC I've tried it every possible combination. Enabled and disabled, same result.

For some reason for 4k content I only get 720x480p, even if I set it to manual I only have the 480p stream available (DD+ w/Atmos still works). For all other content (1080p and lower) it just buffers endlessly. Worked perfectly fine on Oreo before the Pie upgrade.

I will provide a log later.

xnappo commented 5 years ago

I think this is everyone with Shield and 8.0 starting at post 1399 here: https://forum.kodi.tv/showthread.php?tid=329767&page=94

I also tried every combination of settings, playback just results in endless starting playback symbol (skin dependent). If I set playback steam to manual, the very lowest setting does play(480p). Amazon plugin still works fine.

Log: https://pastebin.com/uCTBGbaE

Smeulf commented 5 years ago

@xnappo did you try to play a Netflix video on that log? I can't see any call to the play method...

xnappo commented 5 years ago

I thought the same thing :) I will try again.

wintuxx commented 5 years ago

Hi, i got the same problem, but it is not a issue from netflix addon. it is an issue from inputstream i think.

peak3d/inputstream.adaptive#293

@Smeulf please look in my log I posted in the link above.

I have tried everything, but nothing let kodi play the Netflix video stream.

Smeulf commented 5 years ago

@wintuxx is it the log where the busy wheel stays on screen?

In the issue you opened at InputStream, you're referring to hardware acceleration.

Is it OMXPlayer and MMAL ? If so, can you please try disabling OMXPlayer and keep MMAL only?

Also in Kodi settings, player, it seems you have the refresh rate adjustment enabled (I may read the log wrong). Can you try to disable it?

There's no obvious error in the log, so for now pretty hard to tell where the problem is :/

Smeulf commented 5 years ago

Also @wintuxx, did you try disabling HEVC profiles? Enable VP9?

/!\ do not enable both HEVC and VP9 the same time.

Dnkhatri commented 5 years ago

Also @wintuxx, did you try disabling HEVC profiles? Enable VP9?

/!\ do not enable both HEVC and VP9 the same time.

Shield does not support vp9 ver2 hardware acceleration so that didn't work even before the update

Smeulf commented 5 years ago

And what about H264?

xnappo commented 5 years ago

If I understand the question, I do not have H265 enabled, so should be H264.

wintuxx commented 5 years ago

@wintuxx is it the log where the busy wheel stays on screen?

In the issue you opened at InputStream, you're referring to hardware acceleration.

Is it OMXPlayer and MMAL ? If so, can you please try disabling OMXPlayer and keep MMAL only?

Also in Kodi settings, player, it seems you have the refresh rate adjustment enabled (I may read the log wrong). Can you try to disable it?

There's no obvious error in the log, so for now pretty hard to tell where the problem is :/

yes

i will provide later new logs ... i will try all above options once with a single log for every option.

wintuxx commented 5 years ago

@Smeulf

Kodi 18.3 fresh install kodi.log no settings changed (netflix question 4K: no, because I have only a 1080p TV)

In Kodi 18.3 there are no OMX and MMAL option in the player settings. Only MediaCodece(Surface) and MediaCodec . They both were active.

if i open a netflix video the busy wheel stays on screen.

Smeulf commented 5 years ago

@wintuxx in your fresh install, you have VP9 enabled, I think it can explain the "ERROR: CDVDVideoCodecAndroidMediaCodec::AddData error(-10000)" message.

wintuxx commented 5 years ago

okay. i have a look. wait i post its log without any other changes than disable vp9

Smeulf commented 5 years ago

@wintuxx no problem :) Thanks for helping and trying for me.

wintuxx commented 5 years ago

it is also in my interest to know why the netflix addon does not work on my shieldtv here the log only VP9 deactivated but no video and the busy wheel stays

Smeulf commented 5 years ago

Ok, I hate that error, 'cause for now I can't understand where it come from.

Can you please try: (don't post logs unless the "ERROR: CDVDVideoCodecAndroidMediaCodec::AddData error(-10000)" has disapear please)

If it still don't works, I'd like you to try with Kodi 18.1. Disable Kodi auto update in the PlayStore, and install this APK: http://mirrors.kodi.tv/releases/android/arm64-v8a/kodi-18.1-Leia-arm64-v8a.apk (hopefully it's the right one), same tests with MediaCodecs, all enabled, only one by one, and none.

Can someone lend me a Shield box ? :D kidding but would be so usefull...

wintuxx commented 5 years ago

VP9 in netflix settings disabled Enable only MediaCodece(Surface) no video, no sound Enable only MediaCodec no video, no sound Disable both MediaCodecs no video, but sound

wintuxx commented 5 years ago

a fresh install with 18.1 no changes

Smeulf commented 5 years ago

For the record, the error looks very similar to this one https://github.com/CastagnaIT/plugin.video.netflix/issues/98 where we concluded a firmware issue was the root cause.

Doesn't mean we won't eventually find a way to make it work.

robofunk commented 5 years ago

I'm tempted to do a factory reset because that seems to have solved people's issues with the Official Netflix app and the Android Pie, but I can live without this add-on in the meantime.

Smeulf commented 5 years ago

@wintuxx @xnappo can you both please try with a trailer? Use context menu on a popular tv show and select 'trailers'.

I'll explain why later ^^

Smeulf commented 5 years ago

@robofunk I was about to ask someone to do a factory reset. If you try, please keep us posted. But I fear it won't solve the issue... Worth a try, if you don't have much to loose.

M2k80 commented 5 years ago

maybe a logcat can help to see what happens... i would give one, but actually on my shield when try to play a vid on netflix complete kodi is crashing. this began since i tried the some different setting in the netflix app, before it was like it discribed above here

wintuxx commented 5 years ago

The Trailers are running. Tried different series

xnappo commented 5 years ago

@Smeulf Will try trailers when home - but agree seems the same as #98 - I get the same no video with audio playing seen there with both mediacoders are disabled.

Smeulf commented 5 years ago

The Trailers are running.

That makes me think it's a decrypting issue then... Trailers are not DRM protected ^^

So either we don't pass the correct arguments to InputStream, or InputStream is not working correctly here.

wintuxx commented 5 years ago

The Trailers are running.

That makes me think it's a decrypting issue then... Trailers are not DRM protected ^^

So either we don't pass the correct arguments to InputStream, or InputStream is not working correctly here.

That was my first thought too. Because everything works before the Shield-Update.

M2k80 commented 5 years ago

i just reseted my netflix addon, it now says esn is l3 and i can only play sd content lol (NFANDROID2-PRV-T-L3-NVIDIASHIELD=ANDROID=TV) i checked on settings. this is not my correct esn, i will try now to set it manually

edit: some series work with sd, and another one get this like discribed here

Smeulf commented 5 years ago

i just reseted my netflix addon, it now says esn is l3

Can you confirm with the app 'DRM Info' from the playstore? Section "Windevine CMD"/"Security Level"

M2k80 commented 5 years ago

with drm info i have l1. with local netflix app it works with 4k the key in the netflix kodi app is complete different to this one which is shown in the android settings. https://photos.app.goo.gl/WGEKjWEvoMSQGZcH9

Smeulf commented 5 years ago

@M2k80 what if you replace the ESN in the settings.xml file with the one from the app?

M2k80 commented 5 years ago

i try no to replace it completely. only change to this NFANDROID2-PRV-SHIELDANDROIDTV-NVIDISHIELD=ANDROID=TV was not working. just entering the complete string. report in 2 minutes

M2k80 commented 5 years ago

no sorry, complete esn dont work too.

Smeulf commented 5 years ago

no sorry, complete esn dont work too.

Thanks for trying!

M2k80 commented 5 years ago

but i have a logcat now. and i just showed which resolutions are available, they are only SD but should 4k

Smeulf commented 5 years ago

and i just showed which resolutions are available, they are only SD but should 4k

Logs please?

M2k80 commented 5 years ago

https://paste.ubuntu.com/p/bXtbhc7h3f/ this is the logcat - it begin when pressed play on the episode.

i think @peak3d is needed to fix this

xnappo commented 5 years ago

Anything to be learned from Amazon - which is still working?

M2k80 commented 5 years ago

i am also wondering, why the plugin now detects wedivine L3 on the shield by default. on old firmware the automatic detection was fine

Smeulf commented 5 years ago

As far as we can see (thanks @lrusak) there's some changes in the cryptography under Android Pie. https://developer.android.com/about/versions/pie/android-9.0-changes-all

Might be related, or not... Anyway, I assume both add-ons are not working the exact same way so it's logic they don't behave the same.

Maybe it's just some data we're not handling correctly and we pass wrong to InputStream, I don't know yet.

Question: can you rollback to a previous firmware version? Android Oreo maybe?

If yes, I'd be very interested with something:

On Android O, play a movie, then grab the "manifest.json" file in the addon data folder, and post it. On Android P, play the exact same movie, on the exact same box, grab the "manifest.json" file and post it too.

I'd like to compare both...

xnappo commented 5 years ago

Is it okay if it is two different Shields? I have one I did not let update yet..

xnappo commented 5 years ago

Assuming different Shield are okay.

O: https://pastebin.com/pjhN1QFh P: https://pastebin.com/BcTQF4Js

HDGuy commented 5 years ago

I have 2 Shields, a 2015 and 2017, same problem on both with Pie update.

Damnit, this build is having problems with the Logfile uploader. Let me try and figure out what's going on.

Smeulf commented 5 years ago

@xnappo that is ok, not exactly what I wanted but no problem.

The manifest seems to be correct on P too. So an issue on that part seems to be excluded.

Thanks.

Smeulf commented 5 years ago

@HDGuy can you resubmit your logs and fix the link? I can't get them. Thanks.

Smeulf commented 5 years ago

@xnappo

I have one I did not let update yet..

Please do not update it ^^ it might be usefull for some test...