Firmware 4.31.19086

[davidfor]

Originally Posted by JSWolf

4.31 is the only Kobo firmware (since I've had my H2O) that needs to be rebooted after being installed.

Why do you think it needs to be rebooted after the firmware was installed?

Having asked that, there have been plenty of times that people have found a reboot was needed after an update. A lot of people have noticed issues after the update. I think battery life and sleep issues were the most common problem. Rebooting the device was the way to solve these issues.

And for the record, as someone with quite a few Kobo devices, none of them needed to be rebooted after the upgrade to 4.31.19086.

[JSWolf]

Originally Posted by davidfor

Why do you think it needs to be rebooted after the firmware was installed?

Having asked that, there have been plenty of times that people have found a reboot was needed after an update. A lot of people have noticed issues after the update. I think battery life and sleep issues were the most common problem. Rebooting the device was the way to solve these issues.

And for the record, as someone with quite a few Kobo devices, none of them needed to be rebooted after the upgrade to 4.31.19086.

Ownedbycats said that the Elipsa needed to be rebooted. I cannot confirm or deny.

[davidfor]

Originally Posted by JSWolf

Ownedbycats said that the Elipsa needed to be rebooted. I cannot confirm or deny.

Where? @ownedbycats said they needed to reboot to fix a problem with the device remembering reading positions. Which sometimes happens after connecting to the PC. You actually replied to @ownedbycats post about this with:

Originally Posted by JSWolf

4.31 is the only Kobo firmware (since I've had my H2O) that needs to be rebooted after being installed.

So you, not @ownedbycats are the one that is making the claim that the device must be rebooted after updating to 4.31.

As far as I can see, the only other time this was mentioned was when @Quoth's said they needed to reboot to because bluetooth wouldn't enable. As I haven't seen anyone else make a similar statement, I think it falls into my statement that sometime people have issues and rebooting helped to fix them.

And I should say, I don't think it is a bad idea to reboot a device or computer after applying updates. I have tended to do that on my Windows machines as it puts the computer into a known good state. I have done it for the ereaders in the past, but, have not been doing it recently.

[compurandom]

Originally Posted by ownedbycats

Not upon installation. After ejecting from the computer, sometimes the reading position stops saving. Rebooting fixes it.

If Davidfor is correct, it's technically not the reboot that fixes it, but the automatic filesystem repair that occurs during the reboot.

The implication here is that '31 is doing something wrong during the nickel->usb->nickel transition of the filesystem and corrupting it, and it needs a fsck to repair it. With luck, the damage is minor, and doesn't involve the database (or at least, not both databases).

@Davidfor: any chance we could get kobo extended / kobo utils to add the BookReader database to its backup list?

[Rid]

Originally Posted by compurandom

@Davidfor: any chance we could get kobo extended / kobo utils to add the BookReader database to its backup list?

I would like that too. If it would actually work or not is another story, but I think it is worth a shot.

So tired of Overdrive issues.

[rashkae]

Originally Posted by compurandom

If Davidfor is correct, it's technically not the reboot that fixes it, but the automatic filesystem repair that occurs during the reboot.

The implication here is that '31 is doing something wrong during the nickel->usb->nickel transition of the filesystem and corrupting it, and it needs a fsck to repair it. With luck, the damage is minor, and doesn't involve the database (or at least, not both databases).

I don't think so.. I've been able to reliably reproduce this behaviour when the only filesystem error that fsck can see/fix is the dirty bit.

I suspect that the database process gets stuck when the kobo switches to USB mode, (and hence, why the filesystem does not unmount cleanly in those times.) When the USB disconnects, the Kobo resumes, but no new data is getting recorded to the database.

[JSWolf]

Originally Posted by compurandom

@Davidfor: any chance we could get kobo extended / kobo utils to add the BookReader database to its backup list?

The problem with that is that the BookReader database is encrypted and there's no way to know if you are backing up a corrupt database or not.

[Quoth]

Originally Posted by JSWolf

Ownedbycats said that the Elipsa needed to be rebooted. I cannot confirm or deny.

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

[compurandom]

Originally Posted by rashkae

When the USB disconnects, the Kobo resumes, but no new data is getting recorded to the database.

That's a different failure mode. It would be interesting to see if reconnecting the USB and ejecting would fix it, or if a filesystem check from the host in between would fix it, or if a reboot is really required.

[ownedbycats]

Originally Posted by JSWolf

Ownedbycats said that the Elipsa needed to be rebooted. I cannot confirm or deny.

Originally Posted by davidfor

Where? @ownedbycats said they needed to reboot to fix a problem with the device remembering reading positions. Which sometimes happens after connecting to the PC.

I don't even have an Elipsa!

[davidfor]

Originally Posted by compurandom

If Davidfor is correct, it's technically not the reboot that fixes it, but the automatic filesystem repair that occurs during the reboot.

The implication here is that '31 is doing something wrong during the nickel->usb->nickel transition of the filesystem and corrupting it, and it needs a fsck to repair it. With luck, the damage is minor, and doesn't involve the database (or at least, not both databases).

@Davidfor: any chance we could get kobo extended / kobo utils to add the BookReader database to its backup list?

That's a good idea. I'll update it soon.

[enuddleyarbl]

Originally Posted by davidfor

That's a good idea. I'll update it soon.

I guess I should have read these latest messages more closely. I just assumed that file was in my database backups. Oops. Just two days ago, I had reset my Forma back to defaults and set it all back up (Overdrive refusing to log in). Today, I connected it to my computer for the first time since then. I didn't think to back up that BookReader.sqlite file. Upon telling Calibre to disconnect, the Forma rebooted. After coming back up, it had forgotten the network. After signing back in, it had forgotten my Overdrive login and refused to log in again. Connecting to Kobo and checking the device database again shows it as being fine. The BookReader.sqlite file is only about 45 MB in size, but, oddly, is dated about 6 hours from now (in the future).

I'm going to delete BookReader.sqlite and see how that goes. Then, I'm going to revert my firmware following Quoth's instructions.

[Calenorn]

6 hours in the future? Perhaps the device also forgot your time zone.

[enuddleyarbl]

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.

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.

[enuddleyarbl]

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:

In the file libnickel.so.1.0.0.yaml you want to change no to yes for...
Code:
Block WiFi firmware upgrade:
- Enabled: no

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.