Thread: Aura H2O Syncing Progress between KoboAura and Android via Calibre?
View Single Post
Old 04-22-2016, 02:47 AM   #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 Ken Maltby View Post
Actually, I've posted a great many times that KOReader does nothing to limit your use of the Kobo stock software (Nickel). The two are both available. So it's not exactly a matter of "switching over", you can easily have some ebooks that you read with the stock software and others that you read with KOReader. You can even use some of the KOReader features like OPDS catalog support to provide ebooks for reading in Nickel.
How does it get the books into the database? Is it updating the database or triggering the book processing? Or waiting for the next time you disconnect to a PC?
Quote:
Despite the nature of some of the posting here, the two (and Sergey's Coolreader port) work well together, for the most part.

There is the issue of Nickel's use and dependence on an SQLite data base. Although not required, I think it only prudent to have files that I will be reading exclusively in other than Nickel, inside a "hidden folder structure" (Hidden from nickel's processing). If both were accessing the same file, it seems possible that Nickel or KOReader could do something to the file that the other has a problem with.
I have no idea bout KOReader, but nickel does not in any way change a book on the device. The books are put into place by someone sideloading. They stay there unchanged including timestamps and permission. The only exception is if you delete the book using nickel. Then the file will be removed as well.
Quote:
There is no problem with having two copies of an ebook file, one in a hidden folder and another open to Nickel's processing. (Of course you will probably want to hide any ebook files from Nickel, that are in any of the many formats that Nickel can't handle. For instance I have a lot of .pdb ebooks.)
No, that doesn't matter. Nickel only looks at files with an extension that it understands. Anything else will be ignored. I don't know what happens if the extension doesn't match the contents. Current firmware will probably stop book processing with it.

And nickel doesn't care if you have multiple copies of a book in the same format that it can be seen. The book is identified in the database using the file path. But, if the two copies have identical metadata, there will be no way to tell them apart.
davidfor is offline   Reply With Quote