And an even bigger question is: what is the process for managing the introduction of firmware updates? Right now, the process looks a bit chaotic. It appears that there are firmware updates on the "official" website, firmware updates supplied to individuals in Dash Cam Forum to "try" to solve reported problems, and defacto firmware updates in the newer releases of the product.
@VIOFO-Support @viofo As a former software senior product manager, I would like to propose that customers need a single source of "truth." In my observation, it seems like there are too many sources now... the support page on viofo.com, postings of updates from Viofo in specific threads here in DCT, and now by word-of-mouth from newer product users. I would propose that such a single source be a firmware support page that collects and distributes any and all firmware updates that have been made available publicly. This would include "personalized" updates supplied here in DCT as well as the "planned" updates to existing product users, and also the updates that are found to be a part of the newer releases of the hardware.. Such a posting would ideally be accompanied by a brief explanation of what changes are being made, information about whether any or all of the firmware updates are targeted for existing product users... and a recommendation to install or perhaps a warning to existing users not to install, if applicable.
I think the rapid response of
@viofo to the problems and the creation of the rapid firmware updates to address these problems has been great. But creating a single go-to source (for "personalized" as well as "planned" updates) along with the transparency inherent in such a solution would, in my opinion, go a long way towards reducing the confusion that the technically-inclined product owners, such as the people on DCT, have about what's the best way to ensure that the product(s) they own are up to date.