Thread: Aura Sideloading issue
View Single Post
Old 10-22-2016, 09:20 AM   #11
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 Garu View Post
But if something goes wrong do I brick the reader or just factory reset and live happily ever after (well, after uploading the books once more, but that's more or less ok)?
The most likely result of "something going wrong" is that the database on the device gets corrupted. The fix for that is to either restore a backup, or do a sign-out on the device.

But, the main reason that would happen is if you unplugged to device at the wrong time. The differences between the Kobo device support in calibre 1.48 and the latest version of calibre is very small. Most of it has been bumping the supported version number with no actual changes needed to the code. Plus adding new devices. The biggest change has been rewriting the configuration handling earlier this year. That had no real affect on the actual interface to the devices, it just makes adding options easier. The next biggest change was triggered by a change in an option used by Kobo for the database. Again, no real change to the interface, I just had to use a different Python library.

Using calibre 1.48 with the Kobo firmware up to 3.19.x is completely safe. I said 4.1 earlier, but I had forgotten about the database change mentioned above. This was introduced with the 3.20.x firmware. It means that the KoboTouch driver in calibre 1.48 cannot read the database. This can be changed easily and is, as far as I can tell, safe.

If you do need get a later device or firmware, then you can still use calibre 1.48. In this case, you disable the KoboTouch driver and use "Connect to folder" device or a User defined device. This will allow you to manage sideloaded books on the device, but you will not see purchased kepubs or have any of the extra functions of the KoboTouch driver.
davidfor is offline   Reply With Quote