Firmware 4.31.19086

[sh3nl0ng16]

Originally Posted by Quoth

I said that, but it was the 4.30.x FW, not the 4.31.x FW. After reading here I cancelled the OTA offering of 4.31.x Then recently I went back to last Elipsa FW before 4.30.x, which is 4.28.17925

Hi Quoth,

I use Kobo Elipsa too, and I am having some minor issues such as delay pencil writing or freeze when highlight. My firmware is 4.31.19086 right now, and can you help me clarify that your kobo elipsa (with fw 4.28.17925) works without any problems? Do you need to do something for improving the reading experience or writing (patch or add some code line, etc...)?

Thank you for reading my question.

[JSWolf]

Originally Posted by DaveLessnau

Well, after reverting the firmware, my Forma checked for updates and asked if I wanted to upgrade the firmware. I said Not Now (or whatever) and the prompt went away. I connected the Forma to the computer to look around, and when I disconnected, it updated itself to the newest firmware all by itself. Hopefully, that won't have done anything bad. I see an earlier post here by JSWolf saying:



But, I can't find that file. Could someone point me to it?

EDIT: It looks like that file is part of the firmware patches from here:

https://github.com/pgaskin/kobopatch-patches/tree/v74

I'm going to have to do some more research.

https://www.mobileread.com/forums/sh...d.php?t=342717

That's the URL for the thread on the patches for 4.30.

[davidfor]

Originally Posted by DaveLessnau

I renamed the old BookReader.sqlite and reverted the firmware. After the reboot, I signed into Overdrive without problem and it created a new BookReader.sqlite. That one is also 7 hours in the future (I was wrong when I said 6 hours). I'm guessing it's time-stamped for UTC, which is 7 hours ahead of me. KoboReader.sqlite is also time-stamped 7 hours ahead.

Yes, you are running into timezone issues and how the two different OSes involved and the file system handle them.

Also, the new BookReader.sqlite is only 15 KB in size. The old one I renamed was 45 MB in size (3000 times bigger). The old one was just about the same size as the KoboReader.sqlite file. I wonder if they're somehow getting mixed up.

My belief is that somehow the contents of the database in KoboReader.sqlite are being written to the BookReader.sqlite file. I have no idea how, why or when, and have no way to prove it. I'm not sure if it is a real issue. I did think it was related to some syncing issues I was having on one of my devices, but, I am not sure now. When I see this, I remove the BookReader.sqlite file. If I see an issue afterwards, I do a repair and that seems to fix things.

[davidfor]

Originally Posted by DaveLessnau

Well, after reverting the firmware, my Forma checked for updates and asked if I wanted to upgrade the firmware. I said Not Now (or whatever) and the prompt went away. I connected the Forma to the computer to look around, and when I disconnected, it updated itself to the newest firmware all by itself.

For the record, that is working as designed. The prompt is after the firmware has been downloaded. It doesn't remove the files and they get installed at the next opportunity. Which is either another sync, or after connecting to the PC. If you want to prevent the upgrade, you can remove the update files when connected.

[enuddleyarbl]

It's odd that a repair will fix a newly-generated BookReader.sqlite file, but not fix one that's actually gone bad. At the very least, I'd think the repair process would see that the file is bad and just replace it on its own if it couldn't fix it with some minor edits.

[davidfor]

Originally Posted by DaveLessnau

It's odd that a repair will fix a newly-generated BookReader.sqlite file, but not fix one that's actually gone bad. At the very least, I'd think the repair process would see that the file is bad and just replace it on its own if it couldn't fix it with some minor edits.

I don't think it is odd at all. If it was easy to do that check, then that check should be done for the main database. And we don't know what is wrong with the file. It could be that the contents of the main database has been added to BookReader.sqlite but what should be in there is still there and valid. Or invalid in a way that appears to be valid. And when it is recreated, it will have default values which will probably trigger whatever is needed to populate the database correctly.

And I just opened a "bad" copy of BookReader.sqlite with a binary editor. Most of it is nulls. From that, it is could be just the file has been reallocated as a larger file and no bad data has been written to it. The size of the used part of the file appears to be about what I would expect it to be.

[koboread]

https://github.com/pgaskin/NickelMenu/issues/121

[koboread]

Already solved，Please delete this item, THS

Originally Posted by koboread

https://github.com/pgaskin/NickelMenu/issues/121

[enuddleyarbl]

I connected the wife's Forma to sideload a book from Calibre today and it promptly corrupted her BookReader.sqlite file. Unfortunately, she has several books checked out via Overdrive. I chose deleting the BookReader.sqlite over resetting the whole device and once signed back in to Overdrive, her books were expired on the Kobo. Even though she still had them checked out on the library, she couldn't re-download them to the device. So, she had to download them to ADE and sideload them over to the Forma. Needless to say, she's not happy and, thus, I'm not happy.

Isn't Rakuten late in getting another firmware out? I thought they released new versions about every 2 months. A replacement for this firmware would be really nice.

[compurandom]

Originally Posted by DaveLessnau

I connected the wife's Forma to sideload a book from Calibre today and it promptly corrupted her BookReader.sqlite file. Unfortunately, she has several books checked out via Overdrive. I chose deleting the BookReader.sqlite over resetting the whole device and once signed back in to Overdrive, her books were expired on the Kobo.

Last time that happened to me, I logged out of the kobo and logged back in and then I was able to sign into overdrive. (And then backed up the BookReader.sqlite file!!)

[enuddleyarbl]

Originally Posted by compurandom

Last time that happened to me, I logged out of the kobo and logged back in and then I was able to sign into overdrive. (And then backed up the BookReader.sqlite file!!)

I've pretty much given up on those non-destructive means of recovery. This loss of Overdrive has happened to us quite a bit. Not once has rebooting or repairing our accounts fixed anything. In this case, after reconnecting her Forma to my computer, I could see that the BookReader.sqlite file was about the same size as the KoboReader.sqlite file. So, to minimize the pain, I just deleted it. Sideloading her Overdrive books via ADE is still a lot easier/faster than sideloading all our books from Calibre (all told, the latter takes about an hour). Of course, even better would be if, upon logging in, Overdrive checked the actual account that it's logging into and recovered itself to that state. But, of course, that doesn't happen.

[JohhnyMix]

I got a H20 v2 and mine has some slight freezes so im hoping for a update soon to fix all this because i dont want to revert back for now.

[JSWolf]

Originally Posted by DaveLessnau

I connected the wife's Forma to sideload a book from Calibre today and it promptly corrupted her BookReader.sqlite file. Unfortunately, she has several books checked out via Overdrive. I chose deleting the BookReader.sqlite over resetting the whole device and once signed back in to Overdrive, her books were expired on the Kobo. Even though she still had them checked out on the library, she couldn't re-download them to the device. So, she had to download them to ADE and sideload them over to the Forma. Needless to say, she's not happy and, thus, I'm not happy.

Isn't Rakuten late in getting another firmware out? I thought they released new versions about every 2 months. A replacement for this firmware would be really nice.

The only thing you can do is go back to 4.30 and patch it to not allow WiFi firmware updates. If you don't want to patch, then you'll have to keep WiFi off and do not sync or use Pocket.

[sherman]

Sigh, just had DB corruption on my Mum's Libra after adding some books.

Thankfully, I seem to have managed to get it back into a workable state by using sqlite3's ".recover" command, which basically recreates the database. As far as I can tell, it's basically a more advanced form of ".dump".

YMMV as to what data is actually lost, so I'd probably use it as a last resort if you want to try and keep your DB instead of signing out to recreate the DB from scratch.

I really hope Kobo manages to find and fix these issues for the next FW version.

[JSWolf]

Originally Posted by sherman

Sigh, just had DB corruption on my Mum's Libra after adding some books.

Thankfully, I seem to have managed to get it back into a workable state by using sqlite3's ".recover" command, which basically recreates the database. As far as I can tell, it's basically a more advanced form of ".dump".

YMMV as to what data is actually lost, so I'd probably use it as a last resort if you want to try and keep your DB instead of signing out to recreate the DB from scratch.

I really hope Kobo manages to find and fix these issues for the next FW version.

You should go back to 4.30 on your mom's Libra 2 and if you or she syncs, apply the patch to stop WiFi firmware updates.