Quote:
Originally Posted by rjcroy
Yes, I understand that, and its a fair conclusion to take. But I am still curious about the possibility that it is related to filesystem unmounting, because that it still the most obvious mechanism. And there has not been another mechanism proposed, other than that the internal flash memory is corrupt, which I would expect not to be so widespread/common.
I am interested in clarifying details to help isolate the causes.
|
Yep, AFAIC it's a borked fw, as in someone is likely not closing files properly. In the Google dev blogs they ended up writing up an entire section as to how devs should open/close files and dbs and also part of the reason that they are switching to ext4 in newer releases top hopefully, help mitigate some of these problems.
So as long as mine can still read books I'm not going to bother with a factory reset until we get a new fw, as I am certain that this has absolutely nothing to do with connecting/disconnecting to a computer as I have NOT done that in several fw versions now. I download EVERYTHING over WiFi, through the browser plus IIRC when I was xferring stuff I just pulled the uSD and used my nb's builtin card reader.