@roger64: No worries
.
Yeah, we don't support USBMS either on the Kobo (because unlike on Kindle, the stock system is pretty monolithic, and since we kill it, we "lose" any low-level stuff it might have done for us).
While it's true that, on Kindle, since the stock is system is *extremely* modular, we try to take advantage of that. It's not always as easy as we'd like, but it allows us to leverage a few of its low-level capabilities (of particular interest, this ensures a rock-solid suspend support, since it's the system's
).
I'm still quite interested in how your device behaved and what your interpretation of what was happening was, because it's always interesting to put oneself in a user's shoes. I've been messing/fighting with this particular bit of the system for so long that I have a very specific PoV on it
.
And as to why it's never come up until now: err, beats me, we've known that USBMS was a terrible idea for quite a while, I vaguely remember discussions about how we could go about handling it as far back as during the kpdfviewer days. Since KOReader, I can only blame myself for completely forgetting about this, since I'm the main maintainer of the Kindle startup script, and my devices spend roughly 99.99% of their time in USBNet mode -_-".