View Single Post
Old 09-29-2016, 07:54 AM   #13
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by rmzg View Post
I have no idea as to why none of these individual bits match up: Why does the PHONE version have _1? Why do neither of the filenames contain '10' like the folder does? And so on.
The # was likely changed to _ by some component involved in the copy. Some people think that # is an invalid character so their apps replace it. Exactly which component I cannot say. It did not happen for me when I copied my library using copy/paste as you did.

It is worth noting that MTP is really flaky. I have personally seen it lose files (not show files that are on the device) and create files (show files that are not on the device). I avoid using it like the plague. Usually when I need to do a transfer I use one of the cloud tools, usually dropbox and dropsync. There are tools available like AirDroid that I haven't tried.

The 10 becoming 1 could be calibre shrinking the path component. It does that when it thinks there is a possibility that the name is too long.
Quote:
I've tried copying the folder and file to the phone again in various combinations and I can't get it to reproduce the file name change.

I'll note that in my initial attempt to copy the Calibre Library over, something was *seriously* unhappy with the file named 'metadata.db', any attempt to copy files that included a file named that generated an error message along the lines of "The device has stopped responding or disconnected", so, uh, that's weird. I eventually changed the name of the file to something innocuous, copied it to the phone, then used the phone's file manager to rename it.
Given that the "long transfer" problem is apparently solved, use the wireless device connection. It handles all file operations on the appropriate machine so is not subject to these arbitrary renaming hassles.
chaley is offline   Reply With Quote