How to upload file to Kindle Scribe?

[xxyzz]

I want to upload a file to path like `documents/book_name.sdr/LanguageLayer.en.asin.kll` and I'm using this code:

def upload_file_to_kindle_mtp(driver: Any, source_path: Path, dest_path: Path) -> None:
    storage = driver.filesystem_cache.storage(driver._main_id)
    parent = driver.ensure_parent(storage, dest_path.parts)
    with source_path.open("rb") as f:
        driver.put_file(parent, dest_path.parts[-1], f, source_path.stat().st_size)
    source_path.unlink()

the code works on Android device but can't upload files to scribe. Could someone point out why my code doesn't work?

Original code on GitHub: https://github.com/xxyzz/WordDumb/bl...e.py#L276-L284

[kovidgoyal]

The scribe is an MTP device. I dont know of any reason it would work with an android mtp device and not the scribe.

[j.p.s]

I thought the scribe is a linux device.

[Quoth]

Scribe is MTP and technically MTP is not do if the device is Android. It's a protocol MS developed for the Zune (from 2006 and Windows CE 6 embedded). I think up to Android 3 Google used Mass Storage and it's from 4.0 in 2011 that Android switched to MTP.

Perhaps Kovid meant MTP just like an Android device?

In 2011, it became the standard method to transfer files to and from Android.
MTP is part of the "Windows Media" framework and thus closely related to Windows Media Player. Versions of the Microsoft Windows operating system from Windows XP SP2 support MTP. Windows XP requires Windows Media Player 10 or higher;[3] later Windows versions have built-in support. Microsoft has made an MTP Porting Kit available for older versions of Windows, back to Windows 98.

—Wikipedia https://en.wikipedia.org/wiki/Media_Transfer_Protocol

[DNSB]

Originally Posted by j.p.s

I thought the scribe is a linux device.

A Scribe may be running a Linux OS but the USB connection was changed from USB mass storage to MTP in the last firmware update.

[j.p.s]

Originally Posted by DNSB

A Scribe may be running a Linux OS but the USB connection was changed from USB mass storage to MTP in the last firmware update.

That doesn't make it an android device.

[Quoth]

Originally Posted by j.p.s

That doesn't make it an android device.

True, though means it behaves like Android since 4.x

[j.p.s]

Mischaracterizing a device can lead to confusion and other problems.

[DNSB]

Originally Posted by DNSB

A Scribe may be running a Linux OS but the USB connection was changed from USB mass storage to MTP in the last firmware update.

Originally Posted by j.p.s

That doesn't make it an android device.

Might I be so bold as to point that that I stated the Scribe as running a Linux OS? You don't need to be running Android for an MTP connection considering that the first time I ran into MTP was a Microsoft Zune music player back in 2008. This was a few years before 2011 when Android adopted MTP.

[xxyzz]

Could this have anything to do with the `@same_thread` decorator in the Windows MTP driver? But I don't find any `ThreadingViolation` exceptions in user posted logs.

[kovidgoyal]

My point was if its working for non-scribe mtp devices it should work the same for scribe they are identical as far as the mtp code is concerned. As for threading yes that's definitely a concern to upload a file you should relaly be submitting a job to the gui device manager rather than talking to the driver directly.

[xxyzz]

I tested the code on Linux not Windows and the Linux MTP driver don't have this thread checking code, I guess this could be the culprit.

[DNSB]

Originally Posted by xxyzz

I tested the code on Linux not Windows and the Linux MTP driver don't have this thread checking code, I guess this could be the culprit.

One thing to remember is that unlike Windows, Linux and MacOS only allow a single connection to an MTP device. That seems to have bitten quite a few users of those OS when using an MTP device.

[xxyzz]

That's not a problem, the code only runs if calibre could connect to the device.

[Quoth]

I have to stop (not kill as it will respawn) gvfs-mtp-volume-monitor on Linux Mint with Mate before I plug-in an MTP device. Setting MTP to not automount only seems to work (mostly) on Cinnamon, not Mate. Using "unmount" at GUI only works for some MTP devices, others won't communicate without cable re-plugged, which of course remounts it as a filesystem.