Thread: Aura HD Kobo Aura HD
View Single Post
Old 05-01-2013, 10:58 PM   #633
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by ilovejedd View Post
I've found that usually, the problem is with the file system format rather than the extra capacity. I've got a tablet that throws a "corrupted SD card" error with 64GB exFAT and several that throw the same error with 64GB FAT32. Since I'm guessing the microSD card slot on the Aura is easily accessible, no, 64GB support isn't absolutely necessary. It would have just been more convenient (less swapping required). I carry a credit card sized case which holds up to 8 cards in my wallet. It's currently populated with 4*64GB and 4*32GB cards (~360GiB) which stores a mix of manga, music and videos (mostly manga) and that's only a subset of my collection (have a 12TB file server at home). Yeah, I won't be able to read/listen/watch through 360GiB of content in 1 month but I like having a large selection on hand.
As you mention swapping SD cards, I think I'll add an explanation of what happens when you put an SD card in a Kobo ereader.

When you insert an SD card, the device processes all the books on it and adds them to the internal database. This is used for the library. This is the same as when a book is sideloaded to the main memory.

When the card is ejected, the device does nothing except it will no longer list the books that are on the card in the library.

If you put the card back in, the card is checked for changes. Books that have been deleted are removed from the database. New books are processed and added to the database. Books that have been changed, are removed from the database and then added as new books. As far as I can tell, the file size is what is used to determine if a book has been changed.

What the above means is that if you eject and replace an SD card, it is reasonable fast. But, if you eject it and put a different one in, all books on the first card are removed from the database and all books from the new card are added. That can take some time if the card has a lot of books. If the cards share contents, such as you copied the books from one card to another and added more books, it should treat it as the same card and only process the differences. But, I haven't tried this.

As I mentioned changed books on the SD card, changes are handled differently for the main memory. If the book changes, it is completely removed from the device. The book is deleted and all entries in the database removed. Again, the change seems to be based on file size. If you use calibre to send a changed book to the device, calibre will update the file size in the database to prevent the book from being removed.

The above is based on experimentation with my Touch and Glo over all the different firmware versions. The above is what the current state seems to be. As the firmware is common between the devices, I expect the Aura HD to work in the same way.
davidfor is offline   Reply With Quote