SHIELD Issue

Channels Android TV Troubleshooting
#1

So I've been chasing some issues with my Nvidia Shield for a couple of months now, and I noticed with today's update, all of a sudden out of nowhere, it seems stable again.

I know it's just internal tooling, but I'm wondering if that internal tooling involved the way MPEG TS streams are handled. I was having lockups over ethernet and straight up connection resets over Wi-Fi. Both a 2017 and 2019 Shield. This was with Direct Stream, and it was regardless of whether I used hardware, software, or hybrid decoding.

It seemed like both issues were basically the same cause, but I'm just curious if this update possibly changed anything, because all of a sudden, 20 minutes of streaming has turned into over an hour of streaming with no issues. So if any devs are available to possibly comment or add any insight to give me some peace of mind, I would love that and greatly appreciate it.

#2

Sometimes the release notes don't mention everything fixed in the release.

#3

Nope, nothing would have impacted that at all.

#4

I still have more testing to do to be certain, but it seems as though this was my Asus RT-AX88U Pro causing the issue.

Whether it was a defective router or an incompatibility with the Shield, I don't know. But I bought a UniFi Dream Router 7 and so far it's been streaming for nearly an hour and a half over Wi-Fi of all things. And it's been perfectly stable.

So I guess in the end, after all that troubleshooting, it seemed to be the network.

1 Like
#5

Connection reset issues over Wi-Fi are definitely solved by the router but I'm still running into issues where the guide freezes so I'm just going to use the Apple TV it's not even worth troubleshooting the Nvidia Shield anymore it's just clearly not meant to be used with Channels unfortunately.

#7

All that remains as an issue where the app totally freezes when going to the home screen and back in. At the same time if accessibility buttons are enabled you'll get duplicate button presses. Restarting the server unwedges it. Running the server on macOS or Docker seems to cause the issue but Windows doesn't hit the affected code path that is causing these lockups.

#8

I just want to state this is resolved in the latest beta and just to thank everyone at Channels for taking care of this issue for me. I really, really appreciate it. :slightly_smiling_face: