Quote:
Originally Posted by kartu
Two things to note here:
1) Reading cache.xml won't help seeing all books. There is a bug ("limitation") in libuss.so.
2) Whether reading cache.xml is feasible at all, is an open question. On the one hand, one "saves" the time to scan the file system. On the other, what should one do with gazillion books in "books by <whatever>"?
It was reported, that when you have loaded about 1300 books (it might depend on books if course) the ebook slows down:
https://www.mobileread.com/forums/sho...&postcount=282
So far first aim would be "hot loading" books from SD card, without rescan. Then adding the "load cache.xml" support (without it, one won't be able to comfortably work with bookmarks etc). So basically it would be "you have thousands or tens of thousands of books on card, but only those that you actually read in cache.xml" |
1) I don't know what the limitation is, but surely it will help.
2) I'm getting really tired of getting asked this question.
I've been stuffing my reader full of books for a long time, I don't care what has been reported, I've never experienced any type of "slowdown" or "battery life loss" so please let's kill that rumor.
The reason I'm fixated with cache.xml is because all things being equal, if there's no scan of the card, there's no chance of corruption, hence the file manager's dependence on cache.xml for book locations will be unimpeded. I'm completely open to my understanding being flawed, but since there are other ways of generating a good cache file, I thought it was a worthwhile direction.
In a previous post, you mentioned a way of mounting the sd card the linux way. Can you elaborate on how this can be achieved, I saw igorsky's run script.sh method but don't that mean you have to boot off the flash utility? Can it be mounted this way via a change in your code somewhere?
And thanks again for your efforts.