Thread: Firmware 4.31.19086
View Single Post
Old 02-12-2022, 08:35 AM   #292
icallaci
Guru
icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.
 
Posts: 819
Karma: 6528026
Join Date: Sep 2012
Device: Kobo Elipsa
Quote:
Originally Posted by compurandom View Post
I'm not convinced the 31 firmware is causing this. I think the bug is older and happens in maybe the last 2-3 versions, maybe just less frequently.
I'm pretty sure this is a new issue with 4.31 firmware. Sideloading even a single book without rebooting causes the problem, every single time, without fail. Also, if I do not reboot after sideloading a book, my reader loses its reading position for books I've already started reading. None of that happened with previous firmware versions. Yes, I did occasionally experience the scan error but I couldn't MAKE it happen (now I can reproduce the error consistently simply by not rebooting the reader after adding a book), and my reader never lost the reading position for books I'd already started reading. Only with 4.31 do these problems occur consistently.
Last edited by icallaci; 02-12-2022 at 08:39 AM.
icallaci is offline   Reply With Quote