MobileRead Forums - View Single Post

davidfor · 02-21-2018, 10:28 PM

I just did a couple of quick tests here, and it seems to be working. But, I haven't run the restore just now. I reset up my Aura H2O just before Christmas, and that included copy about 50 in progress books onto the device and then restoring the reading positions. I haven't reopened some of them since then. Opening a few of these now, worked OK except for one book (and I know why it didn't).

One thing I do suggest, is restarting the device before opening the books. The reason for this is that the plugin updates the database on the device directly, but the device can work on cached data. I occasionally find that the update to the database isn't seen because it doesn't get reread before it is displayed or used. Restarting the device will mean the database will be reloaded and the latest values used. In my case, the device has definitely been restarted since the restore was done.

Another reason for this to fail is if the book on one device doesn't match the book on the other device. A simple reason would be if you were reading an epub on one, but used kepub on the other. The two formats use different methods for storing the reading locations and they are not compatible. The restore function doesn't attempt to validate the restored reading position makes sense for the version of the book currently on the device.

Other than that, I would need to see some more details. Run calibre in debug mode, restore the reading position for a few books and post the debug log. Then check if any of the books open to the correct place. I should be able to see from the logs if the reading position is being restored in the way I expect it to be.

02-21-2018, 10:28 PM	#1464
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	I just did a couple of quick tests here, and it seems to be working. But, I haven't run the restore just now. I reset up my Aura H2O just before Christmas, and that included copy about 50 in progress books onto the device and then restoring the reading positions. I haven't reopened some of them since then. Opening a few of these now, worked OK except for one book (and I know why it didn't). One thing I do suggest, is restarting the device before opening the books. The reason for this is that the plugin updates the database on the device directly, but the device can work on cached data. I occasionally find that the update to the database isn't seen because it doesn't get reread before it is displayed or used. Restarting the device will mean the database will be reloaded and the latest values used. In my case, the device has definitely been restarted since the restore was done. Another reason for this to fail is if the book on one device doesn't match the book on the other device. A simple reason would be if you were reading an epub on one, but used kepub on the other. The two formats use different methods for storing the reading locations and they are not compatible. The restore function doesn't attempt to validate the restored reading position makes sense for the version of the book currently on the device. Other than that, I would need to see some more details. Run calibre in debug mode, restore the reading position for a few books and post the debug log. Then check if any of the books open to the correct place. I should be able to see from the logs if the reading position is being restored in the way I expect it to be.