Quote:
Originally Posted by Sirtel
They all do, in my experience.
|
Only MTP and Network USB gadgets don't lock the screen. The iRiver Cover Story, Binatone Android 3, Sony PRS, older Nook eink, all Kindle eink except Scribe (it's MTP), all eInk Kobo all lock the screen.
The database corruption issue on some Kobo FW versions is complex.
I've not had such happen for a long time, even though I manage five Kobos (4 models) regularly and the two Sage models very often. I have used maybe 7 models of Kobo and only saw it a few times. The current issue can be due to the database not being closed before USB connects, that's a FW issue. Obviously disconnecting the cable while something is ongoing can also cause an issue.
The symptoms of corruption vary.
Amazon sync messes up collections if you have a PW3 and DXG on the same account. I've seen database corruption a few times on Kindles, nothing to do with USB.
Originally MS introduced MTP as an extension to PTP for DRM on the Zune.
Google switched Android from Mass Storage USB to MTP with Android 4.x and the reason may have been security.
Above 32G there is another reason. The Kindle Scribe is the only Kindle currently with a more than 32G option (the 64G model). More than 32G on an SD Card partition really needs exFAT rather than FAT32. Mass Storage mode is usually FAT32 because it's the only format everything supports that has longer paths and filenames. MTP and Network USB (reMarkable and some gadgets) allow any arbitrary file system on the 'gadget' as the MTP or TCP/IP are protocols for data transfer/communication, not file access. Windows has a driver layer that uses MTP and emulates a filesystem for the OS, so more than one process can connect (because they developed MTP), though I think originally only Windows Media Player connected to transfer (a bit like iTunes for an iPod). Mac and Linux are limited to one process, so if it's 'mounted' for Finder or a File manager, then no other application can connect direct. On Linux Mint with Mate Desktop (not with Cinnamon) I might have to stop (not kill) the gvfs-mtp-volume-monitor. With some MTP devices unmounting will allow calibre to connect, others can't, so gvfs-mtp-volume-monitor has to be stopped before connecting the cable.