Thread: Glo Firmware 2.1.5
View Single Post
Old 10-18-2012, 06:47 PM   #47
murg
No Comment
murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.
 
Posts: 3,240
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
Quote:
Originally Posted by MDK View Post
Kobo is checking to make sure each device gets the appropriate upgrade package when needed. If the user (you) can't wait and goes willy-nilly then its the user's responsibility for whatever damage that causes.
Sorry, but if you guys aren't even doing the very basic checks involved in determining that the firmware is for the right device. This is a design defect and probably a manufacturing defect as well.

You are operating in an international arena, the consumer protection laws are different in every country. I'm sure that at least one of these countries will find that the design of the firmware update management is a defect. And imagine the PR disaster if your devices are found to have a defective design. People (and by this I mean the press) doesn't really distinguish between firmware and hardware.

Nothing a user does on the user accessible side of the Kobo should result in a broken device. Needing-to-be factory reset is barely acceptable, but broken is completely unacceptable.

If someone goes playing around on the internal side of the device, then they are on their own.

There was also no warning from Kobo that this behaviour would lead to a broken device. There is a big difference between 'incompatible' and 'broken'.
murg is offline   Reply With Quote