Thread: Elipsa New Kobo (N604) [Elipsa - ed.]
View Single Post
Old 06-06-2021, 06:29 AM   #457
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: 47303826
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Calibre support for the Elipsa
For anyone who gets an Elipsa early, I have just checked in the changes for calibre to recognise the Elipsa. This is adding the device ids and other code so that calibre will see it and attempt to use it. This will be in the next calibre release. Or, for anyone that gets an Elipsa before then, you can run calibre from source to test.

But, I don't know the firmware version or database version that will be on the device. This means that calibre will almost definitely display the new firmware warning when an Elipsa is connected. I have been told that there are no changes in the firmware that will affect how calibre sees Kobo ereaders. It should be safe to use the "Attempt to support newer firmware" option in the driver.


Disclaimer: I do not have an Elipsa to test with. The details have come from a reliable source. I have done the best I can to not introduce any errors, but, until someone plugs an Elipsa in while running this code, I can't be completely sure.
davidfor is offline   Reply With Quote