Bugzilla – Bug 5896
If anything goes wrong during creation of main menu items, remote is unusable and not obviously upgradeable
Last modified: 2009-09-08 09:19:25 UTC
I checked in a couple of things this week that exposed a couple of bugs. Both of these bugs (can't use jive.ui.Window:setTitleWidget() in SlimBrowser, SetupWallpaper settings written/read in bad form) caused a Lua crash while creating the main menu. An accompanying problem with this was that, when this error occurred, the HW becomes unusable. Luckily for the beta field units, a combination of a) reboot with + key held down to wipe settings and/or b) reboot with volUp key held down to boot to previous version could get the user into a state to update to a newer, fixed firmware. I don't have a solution for this, but it would be nice if in these situations the remote could still be updated with new firmware. Otherwise at some point there is going to be a situation in the field where a firmware update causes this issue and we end up with a support crisis.
This harkens back to the request I made earlier to let the user back out to some default home menu. Add this to the fact that if the server goes away, we also can get stuck on a blank screen.
Richard asks if there are specific cases in the future we should open new bugs for them.