Firmware 4.31.19086

[compurandom]

Originally Posted by icallaci

I'm pretty sure this is a new issue with 4.31 firmware

I'm not saying this isn't an issue with 4.31, I'm saying it is *worse* with 4.31, but the problem was there before, it just happened less.

Smells like a race condition or something to me. It would make sense if something was preventing kobo from unmounting the partition before it gave it to USB. But it doesn't happen every time before 4.31.

[Lykke]

I upgraded a Libra 2 and since then have had constant problems with getting it to boot. It will only boot if I connect it to a powered-on computer. Sometimes that does not work either. Factory reset did not help. So I only put it to sleep now, but for some reason it powered itself off and I had to spend 30+ min (before my morning coffee!!) to get it to work. What, is this not a professional product? Is Kobo not the second or so biggest ereader producer? This is completely unacceptable. I have never opted in for beta updates. That I will have to roll back to the previous firmware because Kobo messed up is just laughable. I will definitely be writing to them after I calm myself a bit. Sorry for the rant.

[JSWolf]

I am surprised that Kobo has not rolled back or come out with another firmware.

[jospalau]

I am in version 4.31.19086

NickelMenu broke after updating. I reinstalled it and I am not experiencing any problem. I have read a couple of books with KOReader since then.

I experienced problems with KOReader end of last year but not now.

Sent from my CPH2021 using Tapatalk

[ownedbycats]

Originally Posted by JSWolf

I am surprised that Kobo has not rolled back or come out with another firmware.

Is Kobo even known to make emergency hotfixes?

[ownedbycats]

Originally Posted by compurandom

Smells like a race condition or something to me. It would make sense if something was preventing kobo from unmounting the partition before it gave it to USB. But it doesn't happen every time before 4.31.

Before 4.31, my scan&fix errors were only under one very specific condition (deleting a book from the device using Calibre and then re-connecting). Now I'm getting them a lot more, usually tied to the import process.

I wonder if the import process might be leaving more things open than just the filesystem? If somehow the database is left in a weird state after the import process, I could see how that could result in corruption.

[MGlitch]

Originally Posted by ownedbycats

Is Kobo even known to make emergency hotfixes?

They’ve released firmware updates quickly and pulled problematic firmware from being distributed before.

For what it’s worth I had to manually update my Libra 2 yesterday. Not sure what the affiliate is set to.

[JSWolf]

Answer given by MGlitch.

[DNSB]

Originally Posted by ownedbycats

Is Kobo even known to make emergency hotfixes?

Kobo has released a firmware version to fix a showstopper bug in a previous firmware release. OTOH, the first step was to disable the buggy firmware from being used for an OTA update.

[Calenorn]

I wonder if they care enough about side loading to bother. Barnes and Noble clearly didn't.

[ownedbycats]

Also, another observation of 4.31 that I'd noticed but had to do a few tests to confirm:

When connecting, a session that gives me the scan&fix prompt causes the screen to take just a tiny bit longer to switch to the 'connected and charging' screen; there's actually a noticeable flicker from white to dark-gray to black while it's doing that. This doesn't happen on a session that connects properly.

Unfortunately I don't know if that tells us anything more.

[MGlitch]

So I’ve tried reading back a bit to find the triggers for the issues folks are having on 4.31 and I haven’t seen anything concrete aside from importing seems to maybe cause database corruption.

Yet I’ve had zero issues with my Libra 2 which I upgraded to 4.31 yesterday just before importing a large number of books kepub and cbz on to it via Calibre on a Mac. It’s not having issues remembering my place, it’s not crashing randomly, it doesn’t freeze if I shut it off with WiFi off then start it up.

[agugu]

Originally Posted by MGlitch

So I’ve tried reading back a bit to find the triggers for the issues folks are having on 4.31 and I haven’t seen anything concrete aside from importing seems to maybe cause database corruption.

Yet I’ve had zero issues with my Libra 2 which I upgraded to 4.31 yesterday just before importing a large number of books kepub and cbz on to it via Calibre on a Mac. It’s not having issues remembering my place, it’s not crashing randomly, it doesn’t freeze if I shut it off with WiFi off then start it up.

When did kobo fix the lastest version？？Was that updated on pgaskin.net??

[ownedbycats]

Originally Posted by MGlitch

So I’ve tried reading back a bit to find the triggers for the issues folks are having on 4.31 and I haven’t seen anything concrete aside from importing seems to maybe cause database corruption.

Yet I’ve had zero issues with my Libra 2 which I upgraded to 4.31 yesterday just before importing a large number of books kepub and cbz on to it via Calibre on a Mac. It’s not having issues remembering my place, it’s not crashing randomly, it doesn’t freeze if I shut it off with WiFi off then start it up.

I'd be curious to see what devices the malfunctions are happening most on, as I'm wondering if it could be limited to certain firmware versions -- Libra H2O is mark7 and Libra 2 is mark9 if I'm remembering right.

[MGlitch]

Originally Posted by agugu

When did kobo fix the lastest version？？Was that updated on pgaskin.net??

I never said they fixed it, 4.31 is the latest firmware version available, I just didn’t list the full version as we’ve not had multiple 4.31 firmware releases.

That said in the past Kobo have released new firmware in as little as 24hrs if I recall correctly. Certainly there were some rapid fire releases when the Sage and Libra came out as well as way back when the Forma released. The Forma actually had a fairly annoying and big bug related to the unlock screen and using a code to unlock. I forget the specifics, but I remember getting a decent amount of updates right after each other.

As to firmware releases between device launches I’m fairly sure I remember it happening before where a firmware introduced a bug so they pulled it from distribution and later released a new version without the bug.

But I would second ownedbycats in trying to narrow this down. They’re right about the Libra 2 being a Mark 9, and I’m pretty sure about the Libra H2O being Mark 7.

I can’t say for sure if my Sage, Forma, or Aura H2O have issues as I’ve not used the latter two since before 4.31, and the Sage I’ve not imported anything on to since before 4.31.

I will say occasionally the buttons don’t work but paging forward or backwards by touch resolves the issue and it happens very infrequently.