Wednesday, January 9

... with my kindle. You see, at some point last year I went to New Zealand and encountered many many days of superiorly shitty weather. At some point during the trip, I also acquired, among many other things, a library of about 1000 ebooks, which I then immediately put on my Kindle Keyboard. To be fair, I would probably not read most of the books as they tend to be in the "love-vampire-books?-well,-here's-a-thousand-of-them" variety.

And then the battery on my Kindle started to act up. I would charge it and then it would discharge to 75% within hours and then to 50% within a day, and to about 10% within two days, even if I did not read anything at all. Not connecting it with the addition of books, I first thought that there was a problem with the firmware. And when it wasn't that, I thought that the time had come for a new kindle. What better time than the beginning of February (HINT HINT HINT) for such a thing to happen? Endless conversations with San about which Kindle model is better, and after finally deciding on one ...

... I googled the issue. That is when I realized that maybe Amazon hired some of our students to write software for the Kindle. Here's what the interwebs had to say:Also, keep in mind than from time to time, the framework likes to mess around with the index files, even if nothing's changed in the content, and the more books you have, the more CPU it'll eat. (That's kinda true as a whole too, since it'll churn a bit on the index file every time it wakes up from sleep, too).
I went all crazy with this new piece of information and removed all but two books (Perdido Street Station and Mountaineering, the Freedom of the hills, if you must). No change in battery charge in the past two days. All iz well!!