Nextpvr Shield TV Oreo Update Tuner Lost

[007GTCS]

I am getting the error "Nextpvr Tuner Client Lost" after new oreo update on the nvidia shield tv. It will play live tv for about a minute then give the error. All of my other devices (fire Tvs and Computers) are working fine. I have done a full reset and new kodi install on the shield and it has not changed. It does it both over wifi and ethernet. Here is the link to my log for Kodi when this started occurring. Attached is my most current log for NextPVR

https://paste.kodi.tv/ajelicacoq

[mvallevand]

Is the time ok on your Shield? the Kodi log doesn't match the NextPVR logs.

Also if you turn off timeshift does it work ok?

Martin

[007GTCS]

Is the time ok on your Shield? the Kodi log doesn't match the NextPVR logs.

Also if you turn off timeshift does it work ok?

Martin

The kodi log and the npvr log were taken at different times. But I downgraded to Shield tv os 6.3 and it works fine. It’s something with kodi and the Oreo shield os upgrade (version 7). Never tried without timeshifting.

[bertmagin]

I tried without time shift and Kodi 17.6, NextPVR 4.2.2, and Oreo works. With time shift I lose Tuner (Ceton InfiniTV6) randomnly.

[mrdally204]

Reporting that I am seeing the same issue here as well. I am using Kodi 17.6 on a Shield TV with Oreo installed. The program plays for a short period of time and then I receiver the tuner lost error message on screen. I have not tried disabling time shift yet, but will do so when I get home. Attached are my NextPVR logs if that helps any

https://dl.orangedox.com/Suts8Q

[mrdally204]

We are not the only ones experiencing this issue. There is a forum post on Kodi that has a few users experiencing it as well. I shared the "disable time shift" work around with them to help in the meantime.

EDIT:
lol. I just noticed the user names on the Kodi forum are very similar to the ones in this post...

[bloftin]

If anyone is still interested in this thread, I fixed my problem by mapping a drive to the server from the Shield box. Then I changed the timeshift directory in NextPVR to the shared drive instead of the default C:\Users\Public\Videos and everything is smooth as butter.

[mvallevand]

If anyone is still interested in this thread, I fixed my problem by mapping a drive to the server from the Shield box. Then I changed the timeshift directory in NextPVR to the shared drive instead of the default C:\Users\Public\Videos and everything is smooth as butter.

That makes no sense unless your C drive is incredibly slow or virus scanning is getting in the way, since the NextPVR has to write and read that file over the network and then the client has to stream it back. The client won't try to play the local file using the PVR addon.

Martin

[bloftin]

I've had the problem since I bought the shield 2 weeks ago. I had a heck of a time mapping a drive, but finally succeeded. And of course now it updated to support SMB 3 today. Anyway, with the pain in the ass it was to get the share mapped, I figured it must be some permission based issue and switched the directory to the shared directory(just to be clear the network share is on the NEXTPvr machine) and like I said it has been working flawlessly all day. I was getting the lost tuner error until this morning. And no, the drive is a 120gb Samsung SSD on the C: and mirrored WD Blue for the share.

[mvallevand]

I feel the main reason the "lost tuner" timeshift bug has been so hard to fix is that it is very hard to duplicate.

Martin