Quote:
Originally Posted by MGlitch
To be more specific, more users reporting it more frequently. Rather than a handful (who didn't intentionally try and trigger this) reporting more frequently.
The bug is def. there, it's just curious that we've seen fairly little noise about it. I'm sure it's been mentioned, but could Windows scanning the partition be part of the issue? That would at least explain why multiple thousands of books getting imported to my Libra 2 the other day didn't make it bat an eye, nor did ejecting while in a kepub, as I'm doing it all on a Mac.
|
When I got my Libra 2, I imported a couple of hundred books in one go. I didn't send all my books at once because I then was still sorting them manually into collections on the reader, which takes time. Then the next couple hundred and so on, until I had about a thousand books on it.
I can't say with confidence it went worse with each batch, because I neither did keep a close eye on it nor did I write anything down, so this is just my memory of how things happened. But the crashing while still indexing, books not showing up until the reader was connected again (without re-sending them) to be visible on the reader, the warning message, all this happened more and more. So factory reset the whole reader back twice and went through the whole thing once again after the first reset with the same occurrences and results. After the second reset, I changed to 4.30 and have not encountered any of this.
I can't give any numbers or help with the codes, so I know this is clealy only anecdotal, but I still hope this helps.
My guess is if you were to add a more books to it and keep on doing so, it would trigger this for you too.
ETA All my books are kepub