Issue with Nvidia Shield 2019 - Kodi Feezing/Exiting Videos over SMB
#1
Hi Guys,

Just upgraded my Shield 2017 box to the 2019 version expecting improvement, but looks like I am running into issues which may or may not be Kodi! Did a full install of Kodi and applied all the skin and changes I wanted etc to find that playback on all files failed within 3-10 mins. When I say failed, the video pauses for 20-30 secs, before turning black screen for another 10-20 secs then exiting to the main menu. All my files are stored on a hard drive connected to my router shared via SMB protocol. This worked fine and dandy on the 2017 version of the Shield but not sure if it is a Kodi setting I haven't configured.

I have tried a full reset of the box and a basic install of Kodi and get the same results. I've tried to limit the config I have done (with audio passthrough etc). Some videos are so bad that they freexe within the seconds!

I think that this is the log you need to help diagnose: Kodi Log

In that log, I start a video (ignore what I watch, I was with the wife!), it plays for a few seconds. Then I play again and it plays for a while, freezes and then picks back up again in 20 secs. Then a few mins later it freezes and exits.

Any pointers or anything else I can give you guys to help? (using Google play Kodi 18.5 version of Kodi and only the Artic Zepher 2 Skin installed, nothing else). Shield Pro 2019 passing through to a Samsung NW950 Soundbar.

Many thanks!
Reply
#2
Quote:2019-12-31 02:23:11.291 T:24642   ERROR: CCurlFile::Open failed with code 404 for https://api.thetvdb.com/series/253463/actors:
2019-12-31 02:23:11.291 T:24642   ERROR: Run: Unable to parse web site
2019-12-31 02:23:23.960 T:24642   ERROR: GetDirectory - Error getting
2019-12-31 02:23:45.101 T:24642   ERROR: CCurlFile::Open failed with code 404 for https://api.thetvdb.com/series/80349/ima...seasonwide:
2019-12-31 02:23:45.101 T:24642   ERROR: Run: Unable to parse web site
2019-12-31 02:24:02.035 T:24642   ERROR: CCurlFile::Open failed with code 404 for https://api.thetvdb.com/series/80349/ima...seasonwide:
2019-12-31 02:24:02.035 T:24642   ERROR: Run: Unable to parse web site
2019-12-31 02:24:02.084 T:24642   ERROR: GetDirectory - Error getting
2019-12-31 02:26:20.211 T:24717   ERROR: Previous line repeats 7 times.
2019-12-31 02:26:20.212 T:24717  NOTICE: CVideoPlayerAudio:Tonguerocess - stream stalled
2019-12-31 02:28:12.349 T:24522 WARNING: ActiveAE - large audio sync error: -111081.362740

There are other problems in your log. One that your entire network connection breaks? Can you ping the Shield while this issue happens?

And all this converges to:

Quote:2019-12-31 02:49:17.835 T:25389   ERROR: Read - Error( -1, 110, Connection timed out )

While this happens does Internet-Access on other machines still work?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#3
(2019-12-31, 11:14)fritsch Wrote:
Quote:2019-12-31 02:23:11.291 T:24642   ERROR: CCurlFile::Open failed with code 404 for https://api.thetvdb.com/series/253463/actors:
2019-12-31 02:23:11.291 T:24642   ERROR: Run: Unable to parse web site
2019-12-31 02:23:23.960 T:24642   ERROR: GetDirectory - Error getting
2019-12-31 02:23:45.101 T:24642   ERROR: CCurlFile::Open failed with code 404 for https://api.thetvdb.com/series/80349/ima...seasonwide:
2019-12-31 02:23:45.101 T:24642   ERROR: Run: Unable to parse web site
2019-12-31 02:24:02.035 T:24642   ERROR: CCurlFile::Open failed with code 404 for https://api.thetvdb.com/series/80349/ima...seasonwide:
2019-12-31 02:24:02.035 T:24642   ERROR: Run: Unable to parse web site
2019-12-31 02:24:02.084 T:24642   ERROR: GetDirectory - Error getting
2019-12-31 02:26:20.211 T:24717   ERROR: Previous line repeats 7 times.
2019-12-31 02:26:20.212 T:24717  NOTICE: CVideoPlayerAudio:Tonguerocess - stream stalled
2019-12-31 02:28:12.349 T:24522 WARNING: ActiveAE - large audio sync error: -111081.362740

There are other problems in your log. One that your entire network connection breaks? Can you ping the Shield while this issue happens?

And all this converges to:
Quote:2019-12-31 02:49:17.835 T:25389   ERROR: Read - Error( -1, 110, Connection timed out )

While this happens does Internet-Access on other machines still work? 

While I haven't been able to replicate those errors during playback issues (which impacts all videos), I did have a constant ping going on during the last few hours of testing with no packet drops at all between 1) my laptop to the shield device and my laptop, 2) my laptop and router and c) my laptop and google. Further testing has shown this may not be a Kodi issue as VLC has the same issue with all video files - which implies something with the new Shield 2019 device. I'll post on the Nvidia forums to seek advice, but if there is anything else that anyone else has experienced that might help, I would love some advice!
Reply
#4
Please check your local network again. Some routers (especially cheap ones) have a sever issue if "some hundred connections" are opened .. You don't bittorrent next to that, do you?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#5
(2019-12-31, 13:24)fritsch Wrote: Please check your local network again. Some routers (especially cheap ones) have a sever issue if "some hundred connections" are opened .. You don't bittorrent next to that, do you?

Nope - no torrenting for me. It's literally 4 devices on the network at the moment, my shield, TV, Laptop and router. Just joined my 2017 device and second TV and they are working perfectly - I am sure it has to be a new setting on the Shield/Android OS level - perhaps a change in SMB. Thanks for the suggestion and advice though
Reply
#6
SMB change I agree,

but the 404 you get when connecting to the Internet, is definitely something else! Also see above log. For me it seems the shield has issues connecting to your network.

Use your Laptop and ping the shield device please and check if that one stays alive.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#7
(2019-12-31, 13:33)fritsch Wrote: SMB change I agree,

but the 404 you get when connecting to the Internet, is definitely something else! Also see above log. For me it seems the shield has issues connecting to your network.

Use your Laptop and ping the shield device please and check if that one stays alive.

It may not be SMB as expected - was able to host media on the router via the uPnP protocol and the same issue occurs. From the start of the video to the point where it froze (approx. 15 secs) I had a constant ping going without any packet drops. Let me check the logs after doing another test, see if the 404 error is constant or was just a one off. I'll post my results..

I also plan to try and host an SMB share from my laptop to see if that works, to limit if it an issue between the router/shield.

Many thanks
Reply
#8
Basics first, please. Do you say the ping kept working _after_ the issue appeared?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#9
(2019-12-31, 19:10)fritsch Wrote: Basics first, please. Do you say the ping kept working _after_ the issue appeared?

Sorry - yes there was a constant ping from prior the issue continuing through the freeze and beyond the video file closing down. I have not seen any dropped packets from before starting the video beyond the video closing.
Reply
#10
(2019-12-31, 19:10)fritsch Wrote: Basics first, please. Do you say the ping kept working _after_ the issue appeared?

So I have done some further testing and although the previous test showed no dropped packets that I saw during a ping. I am now seeing one dropped ping packet about 3-5 seconds prior to the video crashing (assuming that is the buffer keeping it going) - this has happened for the last 10 tests and pretty much ties in with the timing of the message "2019-12-31 20:09:02.914 T:9104  NOTICE: CVideoPlayerAudio:Tonguerocess - stream stalled, 2019-12-31 20:09:24.603 T:9090   ERROR: Read - Error( -1, 110, Connection timed out )".

So something not right with the network configuration?
Reply
#11
What's your network topography? How are things connected?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#12
(2019-12-31, 23:06)fritsch Wrote: What's your network topography? How are things connected?

5ghz TP-Link VR2800 router with connected USB drive(s) serving the Shield TV wireless 5ghz band with IPv4 (Same setup with my 2017 Shield Device) device Smile
Reply
#13
(2019-12-31, 23:06)fritsch Wrote: What's your network topography? How are things connected?

Just to give an update - an SMB share from another device (laptop) works fine and no packets dropped at any time, over Wi-Fi too. 

So it is definitely a shield to router issue - not related to SMB specifically or Kodi. Any other suggestions is appreciated but I will also try and engage some help from the Shield community!
Reply
#14
(2019-12-31, 23:06)fritsch Wrote: What's your network topography? How are things connected?

Sorry to bombard with replies, just wanted to share the lastest findings. It looks like it could be a Kodi issue, or at least some part of Kodi. Based on a suggestion from the Shield community, I installed MrMC which looks like a stripped down version of Kodi. All videos are playing perfectly fine, tested 4 so far without a single freeze (I cannot get 1 to work in Kodi).

Not sure if this give us any clue as to where to look within Kodi based on MrMC is working?
Reply
#15
MrMC uses a different SMB implementation.

I still don't get your 404 internet access errors, cause they are SMB unrelated.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply

Logout Mark Read Team Forum Stats Members Help
Issue with Nvidia Shield 2019 - Kodi Feezing/Exiting Videos over SMB0