Quote:
Originally Posted by PeterT
Have you at least opened a support ticket with Kobo? Just because some people DO come here from Kobo does not mean that this problem is entered into their problem management systems.
|
No, I haven't, and I don't plan too. You can flame me for that if you want, but the point I'm trying to make is that for something so fundamental as the file system and database getting corrupted - I SHOULDN"T HAVE TO!!!
This is a simple $130 device that is intended for one thing only, reading books, *reliably*. It's not a tablet or a full blown computer that's being taxed to do many complicated things.
I have several MP3 players in the same price range that similarly do one thing only - play music. And *not one* of these devices has *ever* had its file system or database corrupted to the point that it loses everything and requires a reset. It just wouldn't be accepted, but for some reason, Kobo thinks this is OK for their piece of shat ereader.
This is just bloody ridiculous. And people shouldn't have to file support tickets for a fundamental major failure like this.
Kobo should recall *ALL* of the devices, figure out what they're doing, fix it, and then start selling ebook readers.
Not the other way around, frustrating people who paid good money by making them act as guinea pigs while they learn how to program file systems and databases that every other manufacturer learned years ago.
Simple as that.
The REAL Joe