Firmware 4.31.19086

[Sirtel]

Originally Posted by mathil

Has anybody experienced occasionally freezing with the latest update? I wasn't doing anything special to make that happen either - once I was reading normally and then the page wouldn't turn; another time it hung up inside the My Books menu; both times I hadn't interacted with the device for a short amount of time (no more than 1 minute, or the time it takes to read a page). Holding the power button to turn it off worked, but the screen didn't refresh until I turned the reader back up again.

I have a Libra 2 with patches installed. I also ran a database check with the KoboUtilities plugin and it went well (the reader also doesn't have any other issue that is usually related to corrupted database).

I have experienced occasional freezing with the 4.30 firmware. Haven't updated yet because of font issues, and if it doesn't fix the freezing issue, there will be no point to updating at all.

I also have patches installed, but nothing else, no NickelMenu, no KoReader etc.

[RobertJSawyer]

Originally Posted by mathil

Has anybody experienced occasionally freezing with the latest update?

Yes, I have. I also have a Libra 2. I haven't yet been able to discern any pattern to it, but I have noticed that sometimes when I think the device is frozen if I just let it sit for a couple of minutes, it unfreezes itself (without any reboot). Nickel Menu and patches installed; I use a sideloaded font mostly (Noto Sans); I exclusively read Kepubs.

[Skydog]

Originally Posted by Sirtel

I have experienced occasional freezing with the 4.30 firmware. Haven't updated yet because of font issues, and if it doesn't fix the freezing issue, there will be no point to updating at all.

I also have patches installed, but nothing else, no NickelMenu, no KoReader etc.

I too experience the occasional freezing with 4.30. Some patches are installed, no NM or KoReader.

[JSWolf]

When your Libra 2 freezes with 4.30, what is it you are doing?

[Deobulakenyo]

Originally Posted by JSWolf

You did not have to factory reset to go back to 4.30.

Yes but i decided to do it to have a clean install and to try it out

[mbovenka]

With this firmware, when I select a word in a Dutch book, it claims I don't have a Dutch-English translation dictionary installed. Which is correct, but I do have a single language Dutch dictionary. I run my Sage in English, which is probably the reason it thinks I need a translation dictionary, but previous firmware didn't do this; it just picked the Dutch dictionary. I can select the Dutch dictionary and that works afterwards (because it remembers the last choice).

Anyone else seeing this?

[black]

Hi Mbovenka,

I'm reading a Dutch book right now and have installed a Dutch dictionary.
I can select that dictionary and have the correct word explained. No problems whatsoever using firmware 4.31.19086 on my Sage.

[Poppaea]

Originally Posted by JSWolf

When your Libra 2 freezes with 4.30, what is it you are doing?

Nothing special. Just using it and it freezes. Like looking up a word, going through the library. As long as I am just reading, it seems to do fine. And I upgraded it from the 4.30 it came with because of the freezes and am on 4.31.19086 right now on a Libra 2.

Thank God I am used to Kobo having wonky firmware to go with their new readers. This is why I don't buy them as soon as they come out anymore. Though I'd thought they'd have it sorted for the Libra 2 by now.

[ownedbycats]

Has anybody had database instability issues with 4.31? As described in this thread I had issues with bookmarks not saving, disk i/o errors, and malformed databases.

I've reverted back to 4.30 for now and will see how that goes.

[windirt]

I have a Libra 2 upgraded to 4.31, nanoclock and nickel menu installed before. It has occurred several times freezing in a short period of time.

Then I did a factory reset and re-upgrade to 4.31 again. without any patch and additional software installed. It has not FREEZE for a week.

[icallaci]

Originally Posted by ownedbycats

Has anybody had database instability issues with 4.31? As described in this thread I had issues with bookmarks not saving, disk i/o errors, and malformed databases.

I've reverted back to 4.30 for now and will see how that goes.

Yes, and it was getting worse, although even before 4.31 I was having a problem with duplicate books in my Calibre library. I always put my current read into a temporary Calibre library so that I can fix typos, formatting problems, etc. as I read. When I finish the book, I reimport the fixed version back into my permanent Calibre library. Something must have changed the way books were saved, because a book titled (for example) "This Is the Title" would be saved to disk as "This Is the Title: And This is the Subtitle," even though I had "polished" the ebook to update the metadata. So when I reimported the ebook back into my permanent library, it wasn't recognized as a duplicate and was instead added as a new book with the longer title. Anyway, after I installed firmware 4.31 on my Elipsa, I started experiencing database errors, disk i/o errors, and other fun things. I suspect the two things are related somehow, but I decided to go back to square one. I even created a new Calibre library and copied all the ebooks from the old library into the new one, hoping to standardize the way metadata was displayed and saved. Then I reset my Elipsa, and reinstalled and reimported everything from the newly created Calibre library. It seems to be working now. But it's only been 3 days, so I'm still hesitant to say it's fixed.

[Sirtel]

Originally Posted by windirt

I have a Libra 2 upgraded to 4.31, nanoclock and nickel menu installed before. It has occurred several times freezing in a short period of time.

Then I did a factory reset and re-upgrade to 4.31 again. without any patch and additional software installed. It has not FREEZE for a week.

It seems like a patch could cause the freezing. Unfortunately I absolutely don't want to use my Libra 2 without patching and I have too many enabled to check them all.

[icallaci]

Well, I got the dreaded "scan and fix" error when I connect my Elipsa to the computer this morning, but I ignored it and everything seemed to be ok until I ejected the reader. My Elipsa rebooted itself, but at least it didn't want me to start from scratch and reinstall everything. So, something is definitely wrong, but the "database malformed" error didn't occur, so I consider that progress.

[davidfor]

Originally Posted by icallaci

Yes, and it was getting worse, although even before 4.31 I was having a problem with duplicate books in my Calibre library. I always put my current read into a temporary Calibre library so that I can fix typos, formatting problems, etc. as I read. When I finish the book, I reimport the fixed version back into my permanent Calibre library. Something must have changed the way books were saved, because a book titled (for example) "This Is the Title" would be saved to disk as "This Is the Title: And This is the Subtitle," even though I had "polished" the ebook to update the metadata. So when I reimported the ebook back into my permanent library, it wasn't recognized as a duplicate and was instead added as a new book with the longer title.

None of that has anything to do with the device. It is all happening in calibre. If you are getting that title when you do a "Save to disk" (though while you said "saved to disk", I suspect you are either talking about the "Send to device" or what calibre uses internally) then either that is what the title in the library is, or, you have a template that sets the file name as that (for the save-to-disk and send-to-device).

Anyway, after I installed firmware 4.31 on my Elipsa, I started experiencing database errors, disk i/o errors, and other fun things. I suspect the two things are related somehow, but I decided to go back to square one. I even created a new Calibre library and copied all the ebooks from the old library into the new one, hoping to standardize the way metadata was displayed and saved.

I don't quite understand how that would have worked. Calibre displays the metadata as it displays the metadata. Unless you were removing custom columns when doing this.

Then I reset my Elipsa, and reinstalled and reimported everything from the newly created Calibre library. It seems to be working now. But it's only been 3 days, so I'm still hesitant to say it's fixed.

As to the issues on the device, I am seeing more occurrences of Windows reporting the filesystem is dirty. But, nowhere near as many as before Kobo updated dosfstools in 4.23 (I think that was the version). I usually do the scan and have not had an issue whether I do or don't. And I haven't had any corrupt databases.

[ownedbycats]

The weird issue with my scan & fix ones is that the notification tends to disappear before I can actually click on it. So I couldn't actually run the suggested scan & fix. A manual chkdsk always came up clean.