Quote:
Originally Posted by Julez
Thanks for your reply!
Is there no way to cut down the time? I have over 1000+ ebooks on SD card and growing! I don't need it to update the old collections, just the new ones which I am uploading. I wouldn't mind if I had to update the entire collection now and then but I am a pretty voracious reader so go through books quite quickly.
|
The driver isn't updating all the collections, it is updating what has changed since the last connection. But, that means it has to check the current state of the collections. The time taken will also depend on the number of collections and how many books are on them. The more collections, and the more books per collection, the longer it will take.
Having said that, your 1m 30 seems a bit long. For 3200 books and 38 pages of collections, it takes about 30 seconds on my Glo HD. I don't have enough books on my Glo, so I can't say how long it takes. I'll have to do some experiments. And I'll have another look at the code. It was as efficient a I could make it at he time, but, it has been a while.
It might be worthwhile checking and compressing the database. Any problems in the database could slow things down. And the compress will reorganise the database and clean up any unused space. This should improve the performance. My Kobo Utilities plugin has both functions, or you can use an SQLite database manager.
Quote:
I also have an issue with the turning of pages. I have mine set with the top half to turn backwards and the bottom to move forward. It sometimes goes wonky and flips backwards even though it's supposed to move ahead. There have been times it hangs! I normally rectify it by turning it off and then back on. A pop-up box will appear and will say "Something went wrong". Is there a patch for this?
|
Over the years, there have been a lot of complaints about erratic page turns. Some of them are firmware version dependent, some seem to be the device and some seem to be the user. The recent firmware seem to be better in this regard as I haven't heard complaints recently, but 3.19.5761 should be OK. For the device, clean under the bevel, as anything trapped there can affect the IR touch emitters and sensors. And for the user, some people see these problems when they tap, and others when they swipe. I've never seen a good explanation of why.