MobileRead Forums - View Single Post

maraskan_user · 04-16-2021, 05:49 PM

Something might possibly be up with Calibre's mtp driver...

I'm using Calibre v5.15 on a Win10 PC and connect to my Android devices via USB.
(Regional formats and system codepage of the PC are set to german, in case it makes any difference. Win10 and all Android devices' firmwares are up to date.)

I'm connecting my Android devices via USB for calibre's 'send to device' function. I had problems with all three them not showing the Date in Device View for quite some time, an issue that was discussed in the forums before with the conclusion that it's probably firmware related.

Today I checked more closely what happens with the files' timestamps as shown by windows 10's file browser when interacting with them via Calibre.
I thing that came up with: Files that start out with having both a "Modified" and a "Created" time showing in the file browser will actually lose this timestamp when I send the file over again from Calibre. The file gets overwritten, but now no timestamps are shown anymore in windows's file browser. Refreshing or changing directories does not bring them back for that file. On the other hand, disconnecting and reconnecting USB and looking at the file again in the file browser, it will show timestamps for both "Modified" and "Created" - but both are the same. Maybe either the Android device itself or the file browsers in this case fixes missing/damaged timestamps by using the timestamp of the containing folder? Not sure.

On the other hand, if I use the file browser to copy an epub to the Android device, the overwritten file will not lose its timestamps - only when copied by calibre. Copying by the file browser it retains the "Modified" timestamp from the windows 10 host while the "Created" timestamp is set the copy time. Reconnecting USB as expected does not change these timestamps.
This shows that it's possible to write and later read both timestamps - at least the file browser does it.

Looking at these results, I wonder if Calibre's mtp driver somehow writes corrupted or invalid timestamps to the Android device. (It might additionally also read invalid data, since Calibre doesn't show real dates in it's device view date column even for files I have manually replaced and checked to have correct dates through file manager before starting calibre...)

So...

- Can anybody confirm these observations?

- Does anybody with the same hardware/software not have the described issues when sending from calibre?

- Does anbody know a fix?

04-16-2021, 05:49 PM	#1
maraskan_user Member Posts: 12 Karma: 10 Join Date: Dec 2020 Location: Germany Device: Boox Nova 3, Galaxy Tab S6, Samsung M21	Android via USB file times Something might possibly be up with Calibre's mtp driver... I'm using Calibre v5.15 on a Win10 PC and connect to my Android devices via USB. (Regional formats and system codepage of the PC are set to german, in case it makes any difference. Win10 and all Android devices' firmwares are up to date.) I'm connecting my Android devices via USB for calibre's 'send to device' function. I had problems with all three them not showing the Date in Device View for quite some time, an issue that was discussed in the forums before with the conclusion that it's probably firmware related. Today I checked more closely what happens with the files' timestamps as shown by windows 10's file browser when interacting with them via Calibre. I thing that came up with: Files that start out with having both a "Modified" and a "Created" time showing in the file browser will actually lose this timestamp when I send the file over again from Calibre. The file gets overwritten, but now no timestamps are shown anymore in windows's file browser. Refreshing or changing directories does not bring them back for that file. On the other hand, disconnecting and reconnecting USB and looking at the file again in the file browser, it will show timestamps for both "Modified" and "Created" - but both are the same. Maybe either the Android device itself or the file browsers in this case fixes missing/damaged timestamps by using the timestamp of the containing folder? Not sure. On the other hand, if I use the file browser to copy an epub to the Android device, the overwritten file will not lose its timestamps - only when copied by calibre. Copying by the file browser it retains the "Modified" timestamp from the windows 10 host while the "Created" timestamp is set the copy time. Reconnecting USB as expected does not change these timestamps. This shows that it's possible to write and later read both timestamps - at least the file browser does it. Looking at these results, I wonder if Calibre's mtp driver somehow writes corrupted or invalid timestamps to the Android device. (It might additionally also read invalid data, since Calibre doesn't show real dates in it's device view date column even for files I have manually replaced and checked to have correct dates through file manager before starting calibre...) So... - Can anybody confirm these observations? - Does anybody with the same hardware/software not have the described issues when sending from calibre? - Does anbody know a fix?