View Single Post
Old 03-03-2022, 02:59 AM   #23
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by ZodWallop View Post
Not exactly the best PR for Kobo.

I'm really surprised they haven't quickly pushed out a patched 4.31 or a quick replacement of same.
Why? I mean, is it a problem that affects a significant number of their users? Probably not, or there would be something. It is an issue for people here because they sideload. But, the average user doesn't. They are using the devices the way that Kobo hopes they will (reading books purchased from Kobo and downloaded to the device). These users are not going to see a problem like this. And, as you are worried about the PR for Kobo, rushing out a fix for a problem that does not affect most users is also "Not exactly the best PR".

And of course to fix a problem, it means you know what is causing it, which means you have to be able to reproduce it. And honestly, it isn't consistently reproducible. I know I can't do it. And that's after spending several hours chatting with a Kobo engineer while I connecting and connecting my devices to my laptop. That was at least 20 times and I think I had the prompt to check the drive once in that period. And I did not have a single corrupted database. I have seen a most of the issues mentioned, but, not at a time I could do anything to debug it, or know what it was that might have caused it.
davidfor is offline   Reply With Quote