View Single Post
Old 03-02-2020, 06:53 AM   #13
stumped
Wizard
stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.
 
Posts: 3,305
Karma: 10259306
Join Date: May 2016
Device: kobo forma, Kobo Libra, Huawei media Tab, fire HD10, PW3 HDX8.9,
Quote:
Originally Posted by chaley View Post
Two things:
  • There was a regression in the wireless device driver that broke Bonjour (mdns), making one of the two methods CC uses to find calibre not work. I think the regression was a problem if running the Python3 beta. The fix will be in 4.12 (I think).
  • Auto detect works fine for me with a Virgin Media Hub 3. The PC running calibre is connected by cable.
i think we discussed this briefly ~2 years ago. we got as far as works for you, not for me, left it there.
FWIW, I had probably removed bonjour and never let it back.
I'm ok with setting it up manually
I also have the hub 3, previously, I think I had the same issue with the hub 1 but that's going way back...

Ps I have at least 2 other android apps which rely on seeing a server component on my pc and do do the auto detect thing quite well. Ultimate remote is one, foobar2000 controller is another...

Last edited by stumped; 03-02-2020 at 04:06 PM.
stumped is offline   Reply With Quote