The Reading Joy & Delight Thread

[DNSB]

Originally Posted by John F

Kobos are so much better. Plug it in, transfer your books, unplug it... corrupted database.

Not quite right, John F. Plug it in when the database was not properly closed and get the database corrupted message. No need to transfer books or unplug it.

OTOH, since I backup the database once per day, the times that this has caused me any issues are nonexistent. If you don't backup your database, you get to sign out and sign in which does not remove sideloaded content which will be re-imported as part of the sign in.

Rather unlike my Kindle Paperwhite 10th gen. which on Saturday when I connected it to WiFi for the first time since before Christmas decided to wipe my sideloaded content. Not that it matters much since most of that sideloaded content was from books that I was formatting/editing for others but for others, it might be just a touch more important.

Another difference is that Kobo is aware of the issue and admits that it is an issue that will (hopefully) be fixed in the next firmware release. In contrast, Amazon does not seem to see wiping sideloaded content as an issue, probably since, for the most part, that involves content not purchased from Amazon.

[ownedbycats]

Originally Posted by John F

Kobos are so much better. Plug it in, transfer your books, unplug it... corrupted database.

Making sure you're on the home screen before connecting should be sufficient to prevent most db corruptions, for what it matters.

[Sirtel]

Originally Posted by ownedbycats

That's an awfully strange joy.

On the topic, pretty much a lot of posts I've read indicate that the Kindle is so sideload-unfriendly (covers going missing, for example) that I wonder why anybody even uses them.

I'm guessing most Kindle users don't sideload or if they do, they use Send-to-Kindle, not USB.

I've read posts here about users not even knowing how to sideload to a Kindle.

If you play by Amazon rules, Kindles are no worse than anything else. The trouble starts when you want to do something they don't want you to do.

[John F]

Originally Posted by DNSB

Not quite right, John F. Plug it in when the database was not properly closed and get the database corrupted message. No need to transfer books or unplug it.

OTOH, since I backup the database once per day, the times that this has caused me any issues are nonexistent. If you don't backup your database, you get to sign out and sign in which does not remove sideloaded content which will be re-imported as part of the sign in.

Rather unlike my Kindle Paperwhite 10th gen. which on Saturday when I connected it to WiFi for the first time since before Christmas decided to wipe my sideloaded content. Not that it matters much since most of that sideloaded content was from books that I was formatting/editing for others but for others, it might be just a touch more important.

To me, the point is that they both (Kobo and Kindle) have their problems. Why bring it up in a "Joy of Reading" thread?

Another difference is that Kobo is aware of the issue and admits that it is an issue that will (hopefully) be fixed in the next firmware release. In contrast, Amazon does not seem to see wiping sideloaded content as an issue, probably since, for the most part, that involves content not purchased from Amazon.

Just curious, but how do you know that Kobo and Amazon are aware/not aware of the problems and their plans for fixing/not fixing them?

[John F]

Originally Posted by DNSB

Not quite right, John F. Plug it in when the database was not properly closed and get the database corrupted message. No need to transfer books or unplug it.

OTOH, since I backup the database once per day, the times that this has caused me any issues are nonexistent. If you don't backup your database, you get to sign out and sign in which does not remove sideloaded content which will be re-imported as part of the sign in.

Rather unlike my Kindle Paperwhite 10th gen. which on Saturday when I connected it to WiFi for the first time since before Christmas decided to wipe my sideloaded content. Not that it matters much since most of that sideloaded content was from books that I was formatting/editing for others but for others, it might be just a touch more important.

...

So to me, Amazon seems to be the better choice for side loading, as I wouldn't be turning on WIFI. Those Kobos are so unjoyful.

[Sirtel]

Originally Posted by John F

To me, the point is that they both (Kobo and Kindle) have their problems.

That's certainly true. I had very few problems with my Kindles (they were almost always offline and that was before the current issue with deleting content), whereas I've had some bugs with my Kobos. So, based on my personal experience, I'd say Kobos are buggier than Kindles. I still prefer Kobos, though (customization and Calibre integration are the main reasons). But both have given me lots of joy and delight.

[icallaci]

Originally Posted by ownedbycats

Making sure you're on the home screen before connecting should be sufficient to prevent most db corruptions, for what it matters.

This does not work in my case. I always return to the home screen before connecting, yet I was receiving db corruption errors often. The only thing that
prevents db corruption for me is turning off the reader, then turning it back on before connecting.

[Renate]

I find this question of corruption really interesting, but that doesn't make it joy.
I've started a new thread here and I'd be very interested to learn something.

[JSWolf]

Originally Posted by John F

Kobos are so much better. Plug it in, transfer your books, unplug it... corrupted database.

Nope. Not here with my Libra 2. I don't get a corrupted database. It just works. I make sure I go to the home screen before plugging in. No problems at all.

[John F]

Originally Posted by JSWolf

Nope. Not here with my Libra 2. I don't get a corrupted database. It just works. I make sure I go to the home screen before plugging in. No problems at all.

See post 127.

[ZodWallop]

Originally Posted by John F

Kobos are so much better. Plug it in, transfer your books, unplug it... corrupted database.

No, no, no. Everyone knows avoiding a corrupted database is as simple as:

1. Make sure you are running not the most recent firmware, but the one from two firmwares ago.
2. Exit any book you are reading.
3. Power the Kobo off then on.
4. Consult your horoscope to see if today is a good day for sideloading.
5. Stand on your left foot while plugging the Kobo in.
6. Sideload your books.
7. Eject your Kobo using Calibre, but NOT using your system's eject (or is it eject using your system's eject, but not Calibre??)
8. Pray a Rosary while the Kobo imports the sideloaded content.

I do that when I sideload and I've only had a corrupted database twice.

[j.p.s]

^ B F Skinner is rolling in his coffin laughing his butt off.

[DNSB]

Originally Posted by John F

Just curious, but how do you know that Kobo and Amazon are aware/not aware of the problems and their plans for fixing/not fixing them?

Easy enough.

For Kobo, I reported the issue to Kobo and got a response back from them.

For Amazon? I made a WEG based on previous Amazon responses to reported issues. As in the issue has been reported and no response, not even the traditional "thanks for reporting this issue".

[John F]

Originally Posted by DNSB

Easy enough.

For Kobo, I reported the issue to Kobo and got a response back from them.

For Amazon? I made a WEG based on previous Amazon responses to reported issues. As in the issue has been reported and no response, not even the traditional "thanks for reporting this issue".

Could you share Kobo's response?

[JSWolf]

Originally Posted by j.p.s

^ B F Skinner is rolling in his coffin laughing his butt off.