Quote:
Originally Posted by davidfor
They definitely do. But, the issue is reproducing the problem. For example, the "always needs to scan" problem is not consistent for me. One night I had it twenty times in a row on my Clara HD and Libra H2O with epubs, but never with a kepub. Whereas someone here has reported it happens with every kepub they sideload. I went to repeat the tests the next day as I thought of something to get more information, and it didn't happen at all on Libra H2O. I did exactly the same thing and didn't have any problems.
While I am seeing some of the issues being reported, I am just not seeing them as often as others are. The scan prompt is happening more often than with previous firmware, but, it isn't happening every time. I have had the issue with the reading status not updating once. But, I suspect that was because it was one of the few times where I sideloaded a book and started reading it immediately. I have had a couple of corrupt databases on my Libra H2O, though the second one was probably me making a mistake when restoring the backup.
All that means is that the cause is not clear. And when trying to debug it, you have to catch it a problem to see what is happening. If the problem doesn't happen consistently, you have to be lucky to catch it. And this has problems debugging it as it is related to what happens when you connect to a PC and at that time, WiFi is shutdown and hence you can't use telnet to debug.
|
I am WAY out of my depth here, but is it possible that sometimes a process is still running when the device is ejected? If so, would it be logical to suspect that a newly occurring error it is related to the newly added (note-taking) firmware?
The reason I left NOOK for Kobo was that the Glowlight 3 seemed to recopy all sideloaded books anytime I added even one new book. This was a SLOW process, and had the annoying side effect of removing the sideloaded books from any user created shelves on the device. My Windows 8 machine would display "safe to remove" message when that clearly was NOT true for the Glowlight3.
The point is, a note-taking device would have to update the notes on EVERY book, wouldn't it? The larger the library, the longer this would take. Might be interesting to see if the problems occur more often on bulkier libraries.
I found this article interesting:
https://www.hellotech.com/blog/reall...ect-usb-drives
Particularly this bit:
"However, even if the USB is not in active use, there is still a danger of corrupting the files. Most operating systems use a caching process. This means that the data is not written immediately onto the USB drive. Some of this information could still be stored on your computer’s RAM.
When you perform a copy command, the computer (depending on the operating system) might perform a series of requests. This can lengthen the process of transferring data from the computer to the USB. This is especially true when you are handling a large amount of data or files."
Suggests that the problem might depend on the operating system, no?
Well, this is just me being a layperson trying to learn about the topic. Am I barking up the right tree?