Quote:
Originally Posted by tychothecat
I'm not interested in using the GUI to interact with my device - I just want to use an android app (Calibre Sync in my case) to discover the server, navigate and download books.
|
The wireless device connection protocol contains no ability to navigate in the library. It is "push" only, sending metadata to the device for books already there and sending new books that calibre says to send (GUI, news, reading list, smart eject, etc).
The content server connection provides navigation capability.
Quote:
|
I can do this when firing the server up as a GUI instance, after enabling with wireless device connection element (again noting that I don't need to use ANY element of the GUI. No need to push to the device, etc.)
|
As I said above, the wireless device connection provides no navigation ability (I know because I wrote it), so I don't understand what you are doing. My suspicion is that you are using the content server without realizing it. If calibre sync cannot connect to the content server without also being connected to the wireless driver then you are out of luck.
Quote:
|
I know that this question has come up multiple times in the past few years, but is this something that can now be considered, please?
|
The calibre device subsystem is embedded in calibre's GUI, so no, starting the wireless device driver as a headless service won't happen. You can of course run the calibre GUI on a headless server using xvfb, but I suspect that would be a lot of trouble for almost no benefit.