Thread: Issue with Calibre 2.69 and Kobo Aura H20 w/ Koreader - device library disappeared!
View Single Post
Old 10-16-2016, 10:21 PM   #8
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Minim View Post
Hello,

I have the same problem as bunglegrind with a Kobo Mini, also using Koreader exclusivly. Disabling KoboTouchDriver and using Connect to folder does work. Still two questions:
  1. Is my interpretation correct, that KoboTouchDriver is useless if I never use nickel?
Pretty much. The driver is assuming the device is being used in a way reasonably close to what Kobo intended. And I cannot think of any of the functions of the driver, beyond the sending books to the device, that would be useful if you are just using Koreader.
Quote:
  1. Is there a way to get the old behaviour of automatically detecting the device? It's not a big problem to click the Connect to folder-button and choose the device, but from an ux perspective, it's a regression.
I haven't tried, but there is also the "User Defined USB" driver. With that, you enter the USB ids for the device in the driver configuration. I don't know if you can use this to define a device that matches one defined in the other device plugins.

If you try it, the vendor id is "0x2237" and the product id for the Mini is "0x4183". I'm not sure about the revision ID, but I think it is either "0x0110" or "0x0326". The rest of it I am not sure about. The tooltip on the fields gives a hint about finding what these values are.
davidfor is offline   Reply With Quote