Quote:
Originally Posted by davidfor
It can't be. Firmware version 4.32.19501 has been out for less than two weeks. As you said it happens "Every few weeks", that means it is impossible for the symptoms you describe to be attributable to that firmware version. But, it does sound like behaviour that was happening with the 4.31 release. If it started in late January, that is probably the case. The updates in 4.32.19501 should fix those issues. Give it some time to see if it happens again.
|
Presuming it’s a corrupt database from 4.31, wouldn’t the issue persist in 4.32 until the database was remade? Since OP can “fix” the issue by loading a single book which then reveals all the books already on the device?