|
Yes, this is the verbatim log that popped up after I closed the debug version of calibre. All I did was save as and send it to you.
And yes, I'm running a much older version of calibre because I'm resistant to upgrading because it seems that every time I do update anything as I usually loose something vital or run into major glitches. However, if the solution is to upgrade, then that's what needs to be done.
Yes, it is a "real" calibre release, not one from a third party. I just haven't updated it.
Yes, I previously used Marvin on my iOS device before the Marvin/Apple iOS 8.3 incompatibility. I haven't revisited using Marvin on my iOS with my Calibre but that is an option on the table if I can't get the Samsung to cooperate.
Do I need to create another debug log, or is the fact that it's missing those bits of information symptomatic of a problem? I followed the instructions detailed in the FAQ that you linked me to. I opened calibre in debug mode, attempted to connect CC and calibre a total of twice (with my IP and port specified), which both failed, and then I closed calibre (debug), saved the log it generated, and emailed it to you.
Am I just a jinx (my hubby says so!)?
|