Quote:
Originally Posted by cybmole
KF HDX.
if I've previously disconnected from content server, and let tablet sleep...
Then when I wake the tablet, launch CC & try to connect the 1st try always ( I think - very small sample size) thinks a while & says nope , cant find a content server.
But 2nd try (always - but with same reservations) works immediately, on the same settings. maybe it has a too aggressive time-out ? ( or it could be that my wifi is still initialising but I don't think that is the case )
if you want me to look more deeply, please advise. otherwise I'm happy to poke it twice! I'm only using CC about once per week.
if you want logs, you'll need to tell me where to find them!
|
Have you entered an IP address or URL into CC's settings, or are you using "automatic"? If the latter, then not only must wifi finish initializing on your tablet, calibre must "wake up" on your computer. CC will wait 5 seconds for calibre to respond. In addition, because CC is using a "broadcast" to send its message, the networking subsystem makes no guarantee that the message will actually be delivered.
The best way for me to see what is happening is to have a CC debug log. The log will tell me what CC tried to do and what success it had at the various stages. To send a debug log, go to CC's settings, scroll to the bottom, and choose "Send a debug log to MultiPie" (I am assuming that your tablet knows about your email accounts). You will see two destinations, one at multipie and one at charles dot haleys etc. Erase the multipie address; my son needn't get involved. If you want to look at the log then it is at Android/data/com.multipie.calibreandroid/files/calibre.companion.debug.log.txt.
Quote:
|
If I leave your CC connected it resumes fine after a KF sleep. but there';s no wat to delete a local copy of a book while connected to the server ? ( so I am disconnecting just to do that )
|
I assume that you mean connected to the content server? Regardless of which connection, you are right, but for different reasons. You can't delete books when connected as a wireless device because there is no way to tell the connected calibre that the device book list has changed.
You can't delete books when connected to the content server because it never occurred to us that someone would want to do that. If we add it then we would need to deal with the ambiguity of local delete vs calibre-side delete (which in fact we can't do). A simple "Delete" menu item wouldn't tell the user on which side the delete would happen, which isn't good because it is destructive.
I assume that the issue of deleting while connected to the content server arises because you are using CC only as a transport. Grouping, sorting, etc are of no interest to you because you do all of that in the kobo app. This is probably an edge use case, and I am not sure whether it is good to add options/complexity to accommodate it.