Thread: Firmware 4.31.19086
View Single Post
Old 02-13-2022, 09:49 PM   #319
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 Calenorn View Post
I wonder if they care enough about side loading to bother. Barnes and Noble clearly didn't.
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.
davidfor is offline   Reply With Quote