Quote:
Originally Posted by Readirect
The problem with Amazon's approach to indexing is that books -- especially sideloaded books -- can get stuck if the indexing fails, causing the device to continue cranking away without end. Since the Kindle OS provides no way to find the offending book, that's a big problem for large libraries.
|
That’s why it’s sensible to load your books in batches and wait for each batch to finish indexing before loading the next. Genuinely “stuck” indexing is very, very rare these days, though. I didn’t have it happen at all while loading 9000+ books onto my KO2, nor for years previously with several other generations of Kindle.
Quote:
|
A better approach, if you don't need every word indexed, is to disable indexing. Do that by connecting the device to a pc then find the Search Indexes folder, delete it and replace it with a text file of the same name. The device will still show your books as unindexed but it won't attempt to index them.
|
That then means that you can’t search books, a facility I find indispensable.
Quote:
|
Or, you *could* just use a Kobo Aura One which doesn't have an issue with indexing. Plus, Kobo allows Calibre to automatically set up collections without jailbreaking the device. With a large library of sideloaded books, that's a tremendous advantage.
|
But the Kobo doesn’t offer the ability to search your entire library. The Kindle’s the only reader (AFAIK) which offers that capability.