Firmware 4.38.21908

[compurandom]

Originally Posted by franklekens

So I'll have to spend a day again sifting through a near 3000 book library to find what I want to put on it.

I've done this enough times that I have a work around for that.

I use reading list to sync books to the device. When I want to add a book, I add it to a reading list that adds a tag to the book and syncs everything on the list on next connect and clears the list.

I have another reading list that is sync'ed from what is on the device, and sets the flag, so everything on the device gets the flag set eventually.

I have saved searches that give me lists of books that are suppose to be on the device but are not (in case I finish a book and delete it, now I can go mark the book as done and clear the on device tag).

It is possible to soft reset the device and have it rebuild the database without needing to re-sideload all the books (just delete the database), but even if the side loaded books get wiped, I can just select the ones with the tag and schedule them to be sync'ed again. Or weed out the list before I do that. Or send them in small batches over a couple of days when it is convenient...

[anacreon]

Originally Posted by compurandom

I've done this enough times that I have a work around for that.

I use reading list to sync books to the device. When I want to add a book, I add it to a reading list that adds a tag to the book and syncs everything on the list on next connect and clears the list.

I have another reading list that is sync'ed from what is on the device, and sets the flag, so everything on the device gets the flag set eventually.

I have saved searches that give me lists of books that are suppose to be on the device but are not (in case I finish a book and delete it, now I can go mark the book as done and clear the on device tag).

It is possible to soft reset the device and have it rebuild the database without needing to re-sideload all the books (just delete the database), but even if the side loaded books get wiped, I can just select the ones with the tag and schedule them to be sync'ed again. Or weed out the list before I do that. Or send them in small batches over a couple of days when it is convenient...

I prefer to use virtual libraries for that. I have presently 5: Archive, Libra 2, Sage, Elipsa, and one for the cousin whose reader I administer.

[Sirtel]

I use a custom column for the books that I send to my devices. A saved search shows only the books belonging to this column. When a device is connected, I click on the saved search and sort by on_device, so I can see at a glance which books are not yet sent.

[Artemide]

Reading your comments prevents me to update this year.
4.35 version works well, with patch and nickel menu. I really wonder that after 5/6 releases firmware could be still so buggy.
Sometimes my Libra 2 freezes and it needs to make a reboot, but it happens very rarely and this thing occurs with a lot of devices (pc, smartphones etc).
Maybe you could consider to make a downgrade of firmware.

[Sirtel]

Originally Posted by Artemide

Reading your comments prevents me to update this year.
4.35 version works well, with patch and nickel menu. I really wonder that after 5/6 releases firmware could be still so buggy.
Sometimes my Libra 2 freezes and it needs to make a reboot, but it happens very rarely and this thing occurs with a lot of devices (pc, smartphones etc).
Maybe you could consider to make a downgrade of firmware.

I still use 4.34 on both of my Kobos. Reading about all the bugs in later firmwares has made me reluctant to update, especially as there is really nothing in later versions I absolutely want.

[DNSB]

Also for what it is worth, the issue with database corruption does not seem connected to not safely ejecting your ereader. The extra database files that are visible during an error connect very strongly suggest that the issue is during the shutdown of the file system on the exposed partition prior to the connect to your PC.

[JSWolf]

@Artemide, explain exactly what you are doing. We both have a Libra 2 and you have problems I don't.

[DNSB]

Originally Posted by JSWolf

@Artemide, explain exactly what you are doing. We both have a Libra 2 and you have problems I don't.

Jon, one thing to remember is that you are much like me in being slightly[*] paranoid about cleaning up your ePubs before sending them to your Kobo. I have seen, on several occasions, issues where ePubs which made epubcheck barf also caused issues with Kobo ereaders. The worst part is that most of these ePubs were commercial products so I can't even say avoid ePubs from dubious sites with a straight face.

* I chose slightly though for me, it might have been better to say very.

[JSWolf]

Originally Posted by DNSB

Jon, one thing to remember is that you are much like me in being slightly[*] paranoid about cleaning up your ePubs before sending them to your Kobo. I have seen, on several occasions, issues where ePubs which made epubcheck barf also caused issues with Kobo ereaders. The worst part is that most of these ePubs were commercial products so I can't even say avoid ePubs from dubious sites with a straight face.

* I chose slightly though for me, it might have been better to say very.

Not paranoid. But yes, I do clean up my ePub and make sure there are no errors. I have checked some retail ePub with epubcheck and I have found errors.

Maybe the solution is to check all ePub before they are sent to a Kobo and if they don't pass, fix the errors.

[Sirtel]

Originally Posted by JSWolf

Not paranoid. But yes, I do clean up my ePub and make sure there are no errors. I have checked some retail ePub with epubcheck and I have found errors.

Maybe the solution is to check all ePub before they are sent to a Kobo and if they don't pass, fix the errors.

I'm not going to bother; I buy far too many books to add that to my workload. I don't even have epubcheck installed.

As Artemide said, it happens seldom enough that I can live with it.

[JSWolf]

Originally Posted by Sirtel

I'm not going to bother; I buy far too many books to add that to my workload. I don't even have epubcheck installed.

As Artemide said, it happens seldom enough that I can live with it.

To me it happens not at all. Most books are OK. But occasionally there are ones with errors. I have no idea how they slip past epubcheck unless it's due to an older epubcheck version a newer version.

[Sirtel]

Originally Posted by JSWolf

To me it happens not at all. Most books are OK. But occasionally there are ones with errors. I have no idea how they slip past epubcheck unless it's due to an older epubcheck version a newer version.

I've come across a couple of books in need of fixing errors. The calibre editor fixed them just fine. Most books don't need it. As basically every book has some errors, but very few cause any issues on my Kobos, I don't waste my time error-checking everything; if I have an issue, I'll fix it when it happens.

[Artemide]

Originally Posted by JSWolf

@Artemide, explain exactly what you are doing. We both have a Libra 2 and you have problems I don't.

Originally Posted by DNSB

Jon, one thing to remember is that you are much like me in being slightly[*] paranoid about cleaning up your ePubs before sending them to your Kobo. I have seen, on several occasions, issues where ePubs which made epubcheck barf also caused issues with Kobo ereaders. The worst part is that most of these ePubs were commercial products so I can't even say avoid ePubs from dubious sites with a straight face.
* I chose slightly though for me, it might have been better to say very.

I do nothing, every 2 or 3 mounths it needs to reboot Libra 2, but for me it's normal.
I don't check or modifie ebooks with Calibre before sending to the Libra 2, just use nickel for wireless transfer.

[JSWolf]

Originally Posted by Artemide

I do nothing, every 2 or 3 mounths it needs to reboot Libra 2, but for me it's normal.
I don't check or modifie ebooks with Calibre before sending to the Libra 2, just use nickel for wireless transfer.

That could be were the problem lays. It could be an ePub with errors that the parser doesn't understand.

[geek1011]

Originally Posted by DNSB

Jon, one thing to remember is that you are much like me in being slightly[*] paranoid about cleaning up your ePubs before sending them to your Kobo. I have seen, on several occasions, issues where ePubs which made epubcheck barf also caused issues with Kobo ereaders.

If that's paranoid, I must be neurotic since I don't just clean my ePubs—I also rewrite the entire OPF document with good metadata (usually based on GoodReads and/or OverDrive).

The worst part is that most of these ePubs were commercial products so I can't even say avoid ePubs from dubious sites with a straight face.

Eh... the ones from dubious sites are often slightly better since they've been processed with Calibre. OTOH, that in itself could be considered worse in some ways.