Thread: Touch Kobo Touch Firmware 2.0
View Single Post
Old 07-15-2012, 02:39 AM   #370
guma
Connoisseur
guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.
 
Posts: 93
Karma: 473808
Join Date: Jul 2012
Device: kobo touch
Quote:
Originally Posted by ltr View Post
No, it's not a device hardware issue. It's the multitude of different ways people use the device with respect to kepub, epub, sideloaded books, calibre, special plug-ins, hacked firmware, etc, etc.

This open system (that Kobo generously allows) is problematic when releasing firmware updates. They simply can't account for all the variations.

ltr
Forget about hacked firmware and plugins (for which kobo is not responsible) and the situation does not appear that complex at all. What remains are a few ebook formats and sideloaded vs. kobo loaded books. (Note that 'sideloading' books is not a hack but part of the core functionality.) Assuming that there are no hardware variations in between devices the only potential factor introducing some complexity is the update history of individual devices. And if this makes a difference to the outcome of updating the device it is due to bad programming anyway.

Fact is that Kobo's beta testing obviously missed quite a few bugs that are easy to spot and perfectly reproducable (for instance: displaying wrong covers in sleep mode and the way dictionaries are offered) and, from what I read here, quite a number of fatal bugs (readers bricked after applying the update). There is simply no excuse for such a failure to properly test a forced update in a commercial product.
guma is offline   Reply With Quote