You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's an as-of-yet unknown condition in the Badge that causes the RUN menu to mysteriously not appear.
Guessing: This may have something to do with a previous problem noted with the testing firmware; it would sometimes report a valid EEPROM chip as being invalid.
[from an email]
I powered up my badge and while it was searching for a network the menu screen showed the searching message and the CANCEL menu item. I selected CANCEL and there was no RUN menu available. The next three times I tried, I noticed that the searching message had a RUN menu item (not CANCEL) and selecting cancel still let me scroll to and select run.
So it appears that the EEPROM check isn't working all the time. I suspect it's related or similar to the EEPROM check issue we had with the initial tester code. Ideas?
... tried again and it happened again. CANCEL appears on searching menu. This time I didn't choose to cancel and instead waited it out, then only the SEARCH option was available. Can't RUN. Rebooted and upon next Searching WiFi, same issue... CANCEL (no RUN). I cancelled, rebooted, same problem... rebooted, same problem... cancelled, searched, cancelled, then rebooted... this time the RUN option appeared while searching for network.
... powered down, powered up, RUN shows up, rebooted, CANCEL (no RUN) shows up. Hmm... could it be something to do with the reboot feature? (double-tab of power button)
The text was updated successfully, but these errors were encountered:
There's an as-of-yet unknown condition in the Badge that causes the RUN menu to mysteriously not appear.
Guessing: This may have something to do with a previous problem noted with the testing firmware; it would sometimes report a valid EEPROM chip as being invalid.
[from an email]
The text was updated successfully, but these errors were encountered: