View Single Post
Old 09-17-2019, 07:51 AM   #49
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
Calibre support

The KoboTouch driver in calibre was updated in version 3.48 to support the Kobo Libra H2O and firmware 3.17.x. Unfortunately, there was a very late change to the database. The database version was bumped after the calibre release. This means that until the next release of calibre, you will need to use the "Attempt to support newer firmware" in the driver.

Other than the need to use the above option, the are no issues with the KoboTouch or KoboTouchExtended driver. There will be an issue with Kobo Utilities plugin fetching the reading status from the device. It will get the percent read and last read timestamp correctly. The problem will be getting the actual reading location. This will be empty. I'll probably fix this over the weekend.

I don't know when the next calibre release will be. The release of 3.48 was to support the Libra H2O while version 4 is being beta tested. I will be checking in the update for the database version tonight. It will probably be included in the next calibre beta for those who want to try it.
davidfor is offline   Reply With Quote