View Single Post
Old 10-08-2019, 10:59 PM   #1684
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,204
Karma: 169936284
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Leonatus View Post
Yes, this is what I want to do the plugin, and:

This is not what I would like to do.

What has been the intention for my report is, basically, that 0nce that I upgraded the reader manually, the plugin seems to not be able to recognize which firmware version is actually on the device; hence the offer to download and install a "new" firmware. In previous upgrades, I relied on the plugin to do that for me, and afterwards, it recognized the actual version.

So I wanted to know if there is something irregular.
I suspect that you were seeing the warning that the database version on your Kobo was newer than the version that the KoboTouch/KoboTouchExtended drivers were expecting. This is nothing to do with downloading new firmware but rather a warning that the database structure in the newer firmware may not be supported by your current version of calibre.
DNSB is online now