Firmware 4.31.19086

[Stevex]

Seriously WHEN are Kobo going to release a fixed firmware. Sorry just letting my frustration out here, it's now the third time I had to recreate everything.

[JSWolf]

Originally Posted by Stevex

Seriously WHEN are Kobo going to release a fixed firmware. Sorry just letting my frustration out here, it's now the third time I had to recreate everything.

Just go back to 4.30 and if you sync or use Pocket, apply the patch to block WiFi firmware updates.

https://pgaskin.net/KoboStuff/kobofirmware.html

You can find 4.30 for your Kobo at the bottom under Versions.

[rcentros]

Originally Posted by Stevex

Seriously WHEN are Kobo going to release a fixed firmware. Sorry just letting my frustration out here, it's now the third time I had to recreate everything.

It's weird, isn't it? For a quite a while it seemed like there was a new Kobo firmware release every other week — but now, when they have a version with issues, they've stuck with it for over two months.

[enuddleyarbl]

The worrisome thing is that according to the list of Forma firmware versions at:

https://pgaskin.net/KoboStuff/kobofirmware.html

they released 6 versions in 2018, 8 in 2019, 10 in 2020, but then only 3 in 2021 and the 1 version so far this year. On one hand, fewer releases could be a sign of code maturity. On the other hand..., well it could a worrisome thing.

[ownedbycats]

Originally Posted by rcentros

It's weird, isn't it? For a quite a while it seemed like there was a new Kobo firmware release every other week — but now, when they have a version with issues, they've stuck with it for over two months.

I'm just assuming that they're having issues identifying and fixing the issue -- tho it raises the questions of why they don't just revert to the stable 4.30 code.

[tschucha]

Originally Posted by ownedbycats

I'm just assuming that they're having issues identifying and fixing the issue -- tho it raises the questions of why they don't just revert to the stable 4.30 code.

If they reverted to the 4.30 code and then just added the SideLoad option I'd be a very happy camper.

[Rand Brittain]

Had some kind of database wackiness on the Elipsa last night, probably the database corruption mentioned above. I did a factory reset and that fixed it, thankfully.

I'll probably just avoid loading any more books on it until a new firmware comes out.

[JSWolf]

Originally Posted by Rand Brittain

Had some kind of database wackiness on the Elipsa last night, probably the database corruption mentioned above. I did a factory reset and that fixed it, thankfully.

I'll probably just avoid loading any more books on it until a new firmware comes out.

Just read the thread and go back to 4.30. Patch it to prevent WiFi updates if you sync or use Pocket. Problem solved until a new firmware comes out.

[compurandom]

Originally Posted by JSWolf

Just read the thread and go back to 4.30. Patch it to prevent WiFi updates if you sync or use Pocket. Problem solved until a new firmware comes out.

I've been running '31 since my device autoupdated. Database damage 3x. Repaired itself without my help once (reboot), lost it once, and recovered from backup once.

I see no point in downgrading to '30, just keep backups.

[JSWolf]

Originally Posted by compurandom

I've been running '31 since my device autoupdated. Database damage 3x. Repaired itself without my help once (reboot), lost it once, and recovered from backup once.

I see no point in downgrading to '30, just keep backups.

So you don't mind having to correct the database and lose data such as the reading position? I don't understand why you would want to stay with such a buggy firmware.

[ownedbycats]

Originally Posted by JSWolf

So you don't mind having to correct the database and lose data such as the reading position? I don't understand why you would want to stay with such a buggy firmware.

Seeing as the issue is usually triggered by re-connecting too quickly after ejecting + importing, chances are the last good backup will have your current reading positions.

In any case, it's easy to put back reading positions if you have Kobo Utilities store it to a column.

[compurandom]

Originally Posted by JSWolf

So you don't mind having to correct the database and lose data such as the reading position? I don't understand why you would want to stay with such a buggy firmware.

You mean, don't I mind having to restore the reading position from calibre after restoring the database? It would be nice if there was an easy way to automate that, but frequently it's only 2-3 books that need their position restored anyway. Sometimes it's faster to do it by hand than wait for the search to find the ones that need to be restored.

[Stevex]

Originally Posted by JSWolf

Just go back to 4.30 and if you sync or use Pocket, apply the patch to block WiFi firmware updates.

https://pgaskin.net/KoboStuff/kobofirmware.html

You can find 4.30 for your Kobo at the bottom under Versions.

I really like 4.31 and the sideloading, I don’t want to revert, I just want it to work. Each time I put it back on, and btw I keep wifi off, I optimistically think it won’t happen again.

[rashkae]

Originally Posted by Stevex

I really like 4.31 and the sideloading, I don’t want to revert, I just want it to work. Each time I put it back on, and btw I keep wifi off, I optimistically think it won’t happen again.

From my testing, you should be ok if you power off and reboot the Kobo before connecting to PC. Do not open any books (or open any other dialogue) prior to connecting the USB.

There has been one person who reported database corruption after doing this, but I am not convinced it was not from a cause other than the 4.31 file system unmounting bug.

[Stevex]

@rashkae OK I’ll try to stick to that, thanks