Quote:
Originally Posted by NiLuJe
@Ruskie_it: Beg to differ, you really *should* unmount && eject properly, the USB stack is notably crappy on those devices (well, it's much, much better on the PW2 to be fair), and FAT32 is terrible.
|
Yeah well, I tend to forget that this is not just an usb stick but there is another computer at the other end of the cable...
Quote:
|
To get back to the issue at hand, even your 'extremely rarely' should be have been a never.
|
Yeah well, I recall it had happened once or twice months and months ago, but it was occasionally. I did not bother at the time, but it was for sure older version of both the hack, the jb, the firmware... so who knows what happened.
Quote:
|
You could try to pinpoint if it happens with a specific book? When you mention switching books, that shouldn't matter much, except if those are new (queue of images to crunch, hogging the CPU), but even then, at worst you should see the *previous* cover, not a broken one. (Keep in mind that for the 'very briefly' to have an impact here, that's a real very briefly, i.e., something between the 5~15s range).
|
Well, it happened on a period of two days, so the book I was reading were no more than two (probably only one), but the cover is "sane" - otherwise it would never work, and it does usually. However that is one. And what I briefly read where a couple of other books. Yes, very briefly is below 15s range I know.. but in that case I would expect the old cover to show up... And to work ok once I get to the "old" book.
Anyway, now I recall that at least in one occasion, I tested-read an azw converted from a pdf file (which appeared formatted very badly in azw as it was a kids book full of images)... maybe in that case the framework got panicked by a weird cover and gave up even if I lately switched back to the previous book (and cover)?
Quote:
|
That, or they might have been subtle changes in how the framework reacts when its only image in the pool is silently modified (which works in a completley different and slightly broken way on legacy FW, for instance, so, who knows). Not running FW 5.6.1 here, but I've never heard of this happening in cover mode, and have never seen it happen myself on previous FW :/.
|
Hmmm... I don't think that's the case, I am more for the bad "new" cover that crashes the framework. Let me know if there is something I can produce in case the problem happens again to help you sort this out.
Not a major problem anyway. A restart doesn't kill me.