To get back to the OP's problem: So it was probably the Amazon update kicking in, thinking it would be a good moment since the "normal" reading framework was idle. Good that it recovered *despite* the reset, which probably happened when it was already runnning...
|