View Single Post
Old 11-02-2021, 09:28 PM   #6
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 Claude_C View Post
Thanks, I tried all that.

My only guess is that Kobo Touch (Extended or not) is not compatible with the new 4.30.x firmware.

Really a bummer when you just received your new toy.
As I have just answered you post in the 4.30.18838 firmware thread, it is working with no problems here. This includes on my Sage. With both the built-in KoboTouch driver and the KoboTouchExtended driver.

Nearly every time this doesn't work, it is due to configuration. If you are confident it is correct, then please run calibre in debug mode, connect the device and let the jobs run. Then close calibre and post the debug log for me to look at.

And for the record, all the function in the KoboTouchExtended driver except for the kepub related stuff comes from the built-in KoboTouch driver. If it works in one place, it will work in the other. But, the configuration is separate. A common problem is that someone has changed from one driver to the other, but, have not updated the configuration when doing so.
davidfor is offline   Reply With Quote