Are your Roku channels not working? Find troubleshooting tips for adding/removing channels, logging in, authentication, activation, playback issues, and more.
Tested with 3800 crazy close to router.
Below, see signal after crashing with less drops/retry of inbound data transmit. Yesterday I had TX/RX flipped. TX is transmitted by SiriusXM server to customer node. Retries are usually zero for Sling in comparison. No glitches at 5 GHz but lots at 2.4 GHz. Signal strength (SNR) would jump around and peak at 34 sometimes. If I could see either of these two screens while running XM, some data might pop out.
Performance indications on main screen. Temp before picture taken was 112 C and graph color was red vs orange. Shutdown was abrupt on this test. CPU Speed was 1000 MHz before I could take the picture so device had not normalized from this stress test. 3800 normally runs hotter than 3930 or 3900 but not above boiling point of water.
This test proved that too strong a signal did not prevent the behavior but shortened the time to crash.
Moved router back down below floor since this test showed strong signal was too much of a good thing. First re-test ran 3 hours and I didn't use the right remote. Repeat and crashed at 3 hours. Post crash had 104 C and 33% retries so I am back to condition before close router test.
There is some network/router option that is being exploited by new XM code that consumes all the bandwidth of the network and the CPU power. I would suspect such high utilization would shorten life of electrical components when operated out of normal range. My printer is the only device on same router as XM device and printer goes off line now when it did not before May 16, I suspect router is broadcasting on all channels and knocking out any other devices. Printer is on different channel than XM device. There should be no contention.
Next steps are to analyze router configuration changes that still provide proper security. It could be that other users reporting this bug are timing out because router is not perfectly set up or up to date. I found some notes on multicasting that matched the retry symptoms but don't believe that is exactly the same root cause. If I change something and device runs cooler without crashing or locking. I do not think the locking is related to this performance overload unless part of memory is corrupted and XM code just goes around some code if data is not addressable. If I can watch traffic on the router due to 3800, I might see it doing something crazy and have better search terms for Dr Google.
If Roku device crashes after 20 minutes, is it hot to the touch? From home screen, hit home 5 times, then FF, down arrow, Rewind, down arrow, FF key. Platform screen will show temperature. If your signal is green and factory reset was done, time before crash should be closer to 30 minutes. Network contention has to be minimized or crash time will be quick. With zero contention, elapsed time to crash will be in hours. Detail screen will lock at 1 hour.
There could be more than 1 root cause. However, I think it is most likely some network issue where new XM code is dependent on a system requirement that is undocumented. XM probably doesn't even know the dependency since the part of the cause may be deep within some vendor controlled runtime library. This new dependency could be found if XM source code compared the pre/post versions. Compares have been part of the standard software methodology forever.
My solution to this issue.
- Count the number of ROKU devices you own that you listen to SiriusXM on.
- Goto "https://www.walmart.com/ip/onn-Android-TV-2K-FHD-Streaming-Stick-with-Remote-Control-Power-Adapter/... and purchase one per device.
- Call SiriusXM @ 1-866-304-7474 and request a $20 bill credit for each ONN device you purchased.
- Enjoy hassle free listening as well as screen casting from your Android devices.
If SiriusXM can't fix the application then perhaps buying customers new hardware will motivate them. 🙂
~kidkrash
