Thread: Kobo future firmware feature request thread
View Single Post
Old 02-27-2013, 10:39 PM   #470
Rev. Bob
Wizard
Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.
 
Rev. Bob's Avatar
 
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
Quote:
Originally Posted by davidfor View Post
I haven't seen enough of a delay between 3 and 4 to make me concerned. And if 2 happens, I know that 4 will happen so I wait.

The problem with that is the only reason a scan won't happen is if the device doesn't see the card. And if it doesn't see the card at all, how can it tell you that it isn't doing the scan? I have had circumstances where the scan didn't happen, but the device put up a prompt saying there was a problem with the card.
Conversely, if the device doesn't see the card, how does the user tell the difference between "step 4 is coming, so hang on and wait while I check the card for changes" and "I don't see that there's a card to scan, so there is no step 4"? I have had both the "significant 3-4 delay" and "no card seen" problems, and only rarely have I seen the "bad card" message.

Quote:
Originally Posted by davidfor
All that is surprising. I've spent a lot of time looking at the database after just about any operation. I haven't done the checks with 2.4.0, but with the previous few firmware versions, the database was kept clean. But, records for the SD card stay there until the books are removed. Ejecting the card and inserting it again should not change the database. But ejecting and inserting a new card will remove all the books from the first card and add all the books from the second card. The same happens if you eject the card, delete a few books and add different ones. And I have never found duplicates for a book unless the file name or path of the book changed.
Next time I get a chance, I'll hook my reader up, look at the database to determine number of lines, and then try (a) replacing a book on the card through the USB cable, (b) replacing the same book through the power-off-eject-card process, and (c, d) deleting the book through the device and then adding it back through each of the above methods. At no point in these tests will I engage either wifi sync or desktop software sync, to shut out all external factors.

If the database is behaving correctly, all five versions of the database should contain the same number of lines, right?

Quote:
Originally Posted by davidfor
For the main memory, what happens depends on the firmware. With the current firmware, if you replace a book (exact same name and path), if the file size changes, the device removes the book completely during the processing. Then you have to add the book again. That means it is treated as brand new book.
That's consistent with my experience, as far back as I remember.

Quote:
Originally Posted by davidfor
This is a defence mechanism on Kobo's part. It doesn't know what changed, so it doesn't know if it is safe to accept.
I can understand that, at least up to a point. I would certainly prefer to see the device do something like "if the assigned unique identifier is the same as the old version, transfer the shelving and progress data over to the new version, because it's the same book."
Rev. Bob is offline   Reply With Quote