Bugzilla – Bug 12816
Tracking Bug - euthanize PB1
Last modified: 2016-11-27 21:02:29 UTC
Tracking bug to plan the recall of PB1 units
Richard won't be doing the recalling, I think. :)
no...but he wanted to come up with the mechanism for killing the PB1 & PB2 units
When this is implemented can we display appropriate messaging saying how and why the unit is bricked? Something like: "Pre-production unit locked. This is a pre-production device and is not supported by Logitech. (PB1)" This should apply to bug 12817 too. (do we need 2 bugs on this?)
I like that idea Dan Yes, 2 bugs because we may delay implementation of this code on PB2
Important note: please please do not retire PB1 units prior to August 21. I had to take all PB1s to the new agent training happening this week and next and I can't have then all suddenly die. A thousand thanks!
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
== Auto-comment from SVN commit #7440 to the jive repo by richard == == https://svn.slimdevices.com/jive?view=revision&revision=7440 == Bug #12816 Bug #12817 Splash screen warning added to beta hardware.
Options added to the code to warn and euthanize beta hardware. Currently PB1/PB2 will now display a five second warning on boot. Earlier PA hardware is euthanized. The messages displayed are: Beta Hardware This is a pre-production unit, hardware revision %s.\n\nSome features may not work. Beta Hardware This is a pre-production unit, hardware revision %s.\n\nThis unit is no longer supported, please return to Logitech. Mickey let me know if the text needs changing, or when the firmware should discontinue support of the older units (eg once most have been recalled).
== Auto-comment from SVN commit #7442 to the jive repo by richard == == https://svn.slimdevices.com/jive?view=revision&revision=7442 == Bug #12816 Bug #12817 Dont nag for hardware rev 3. Show message for a little big longer.
No plan to kill off PB1 units for initial release. From Richard: "...for 7.4 pb1/pb2 should not become worse, but we won't fix things that are broken." May still do so later. Moving target out to review for next release.
I don't know what the original intent of this bug was, but I am hoping it solves a Support issue where PB1 or PB2 units show up on eBay at some point after release. Mickey-- what is your criteria for review? If we are not disabling PB1s (& PB2s) at 7.4 launch, then when would we? I vote we nuke 'em at or shortly after launch.
Please don't euthanize the early revisions until all us outside beta testers have received newer (production?) units. I'm still testing, commenting, and filing bugs. Waking up on Tuesday to find my PB1 bricked wouldn't help anybody. eBay: it would be good for someone to post a note in the Radio forums about how to identify an early unit. It's been common to suggest buyers of used SB1/SB2 style players ask eBay sellers for label pics to determine what player it is. Thank you.
Changing priorities due to management guidance.
Moving lower-priority bugs to next target
Please check with Mickey, but I believe all the PB1s have been returned to Logitech now, so the poison pill to brick any stragglers should be reconsidered. Also I didn't bookmark the ticket, and now cannot find it, but I thought there was an enhancement ticket in bugzilla for some kernel(?) optimizations that had been put on hold because they were incompatible with PB1 Babies. Maybe I'm thinking of optimizations for Touch/fab4? Anyway, I expect Felix and Richard would recall if there are any performance-robbing bits in the current Radio firmware that exist only because there were still PB1s in the field. If so, those should be fixed to improve the UX for everybody. Thanks.