The app I'm working on has recently experienced some issues where a Roku device has an incorrect time and it causes big problems in the time-based app.
We've seen Rokus with time far in the past and also Rokus with time a few hours in the future. In either case, the app won't work correctly since it looks for content "on now" and doesn't find the right data.
To address this I'm considering two possibilities:
1) Detect that the Roku device time is off by some minimum (say 10 minutes) and instead of launching the app, throw a warning on screen to tell the user their device time is off and they should try rebooting their Roku,
2) Have the app calculate the difference between the device time and the actual time as given by our APIs and use that difference as a global time offset so that the app can run normally.
In trying to test these cases, I've been having difficulty recreating the problem. This leads me to wonder if the time server issue was corrected in firmware 7.1 (by "time server issue," I mean device defaulting to the software build time in cases when the time server isn't reached). http://forums.roku.com/viewtopic.php?f=34&t=92391#p519096
1) Was the time server issue addressed in fw 7.1?
2) Is there a way to force the device time to be incorrect so that I can test the potential resolutions?