Thread: Kobo Bug thread
View Single Post
Old 10-03-2016, 06:24 AM   #744
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 Muttly View Post
Don't forget this is an Aura One, and the firmware is extremely buggy.
doubleshift is partly right. No-one else has reported anything like this. Including me. I have run exactly the same firmware on four different devices with no issues with the dictionary (I use the supplied fonts), that makes me wonder what happened on your device.

And this firmware is NOT extremely buggy. It is no worse than any of the previous versions that it follows on from. And I'm reasonably confident there haven't been any recent changes in these two areas.
Quote:
Yesterday I actually suffered a hang whilst reading and had to restart the device.

My experience with the Kobo, so far, make me appreciate just how rock solid the Kindle software is.


ETA: 'Something happened to the file system' is also a pretty damning indictment of the software. (The Bookerly disappearance happened between ending one book and immediately starting another, without the device being connected to another computer or wifi being turned on. Files should not just disappear in those circumstances. And a hardware fault in an SSD would be most unlikely to cause such selective errors).
You didn't say when you lost the files or what happened immediately before. If you had connected to PC and were not careful to eject, of if you forced a restart, then the file system could be dirty and if a scan was triggered, files might not be recovered. Also, you haven't mentioned if you patch the firmware, use KSM or any of the other hacks. If you do, they might be the culprit. And if you are adding your own dictionaries...
davidfor is offline   Reply With Quote