At risk of stating the obvious but yet unvoiced question:
Why are things which worked properly now broken? The Roku has not suddenly tightened its h.264 playback requirements causing "Loading please wait" nor did received signal quality needed to make uninterrupted playback suddenly require changing antenna signal attenuation.
An obvious answer is programming mistakes introduced in the Tablo 2.2.6. firmware.
Things which worked fine before the update should NOT send users off to re-examine their antennas, routers, etc.
The programmers should be asked to carefully look at what was changed, and why, and how..... And their changes should be critically reviewed by OTHER people whose fresh eyes and ego-less reviews find and eliminate bugs.
Far too many wasted hours of user grief, endless typing, and amateur speculations created by new firmware bugs which are the root cause of these problems.
If 5% of the firmware is new code, this is where the corrective action needs to be focused and applied.
All the other effort to explain why previously working code no longer works is, IMHO, a big waste of time.
The loading issue and the inability to connect remotely issue suddenly appeared in 2.2.6., and the Fast Forward reboot started in April right when Tablo
and Roku coincidentally updated their respective firmware. How about either providing a method to downgrade / revert or, better yet, assign people to really concentrate exclusively on fixing these bugs?
As much as I appreciate the value of users trying to find workarounds, I am really hoping that root causes will be revealed by looking at the obvious - what has CHANGED WITHIN THE UPDATE which previously worked properly.