Quote:
Originally Posted by mtravellerh
Kindle reads .prc files that you put in the kindle folder and ereader the .pdb files you put in ereader folder. PB reader seems to scan the whole SD-card and displays the books it can read (books in kindle folder are not displayed) Do I have my facts right here?
|
I think so; that is my experience.
Kindle is tidy and keeps everything in the one Kindle folder and doesn't peep if you swap SD cards.
Aldiko just dumps stuff all over the place. FBReader also creates several hidden folders all over.
It looks like the PB Reader launches a process at boot that scans and indexes the entire file system for epubs. I've been manually shutting the process down because it slows down the IQ something fierce and eats up so many CPU cycles other apps and widgets (especially the PB Widget) start getting unresponsive at the OS level and I start getting the alert boxes.
I normally use a 256MB straight SD card for updates on my readers and with that card (with only three sample ebooks on it; one prc, one epub, one pdf) the IQ is fast and smooth. With the "production" 16GB SDHC card, it gets sluggish as the index program gets bogged down trying to index every one of the 30,000 files on the card. (The big card I've been testing with has a copy of the Black Mask folder in it with 25000 epubs.)
Hate to beat a dead horse here, but the eink readers just use the file system
as an ebook database. No indexing, no internal database. No background process is needed and certainly nothing that eats up resources like the IQ Reader's spawn thread. Considering the bookshelf only lets you sort by author, title, or date; just as the eink bookshelf, there doesn't seem to be much payoff to the hungry-thread approach.
I would humbly suggest a rethink.
Or at least a warning if this is a one time thing.
Back to testing.
Hopefully, in a day or two, I can get down to *using*.
