Channels & viewing

[daz1138]

After the OS 11 Update (11.0.0 build 4168-CR) on my Roku Express 4K+ (3941RW) every few minutes the CW app crashes and drops me back to the Roku Home Screen. I’ve run all updates, rebooted the Roku, removed and readded the app. 

After deleting and readding the app I restarted the program from the beginning and it crashed at the EXACT same point. I went to my Roku TV (OS 10.5.0 build 4210-94) and watched the same program from the beginning and did not have any crashes. 

The crash is 3 minutes into this weeks Flash episode and it seems like the crashes are every 3 minutes although I did not time each one  

CW app version 2.2 build 29 on both Roku devices 

I don’t know if this is related but on OS 11 - Amazon Prime Video (ver: 12.3 build 2021122417) gives me an HDMI cable error when I try to play video from there. Netflix is fine, YouTube is fine. 

[daz1138]

After rebooting a few times, the HDMI cable issue seems to have resolved itself, for now. This must have something to do with OS 11 as I never had this issue with the device before and this only happened in the Amazon Prime Video app. 

[RokuDanny-R]

@daz1138 

Thanks for the post.

How are you powering the Roku device? Is the device plugged into the TV USB port or is it plugged into a wall outlet?

With more detailed information, we will be able to investigate further.

Thanks,
Danny

[daz1138]

The device is connected to the TV via USB. It has been connected this way for almost a year and this is the first issue I have had with this device. 

[RokuDanny-R]

 @daz1138 

Thanks for the post.

Have you tried connecting your Roku device directly to a power outlet? Please be aware that sometimes the TV does not provided enough power to the Roku device, which would explain what you are experiencing.

Keep us posted what you find out.

Thanks,
Danny

[daz1138 · Accepted solution]

It appears the CW app issue was CW. The app on all my Rokus (OS 11 and 10.5) had problems this weekend. It looks like OS 11 was more sensitive to the initial issue but as it got worse the app would not even launch on any of my devices. It appears to have corrected itself so it must have been a backend issue. Thank You.