Firmware 4.35.20400

[MGlitch]

Originally Posted by jospalau

But was Ok in previous versions regarding the buttons?

Sent from my CPH2021 using Tapatalk

Quoth and I (and others) have reported issues with previous firmware versions and the sage buttons occasionally ceasing to work. So if he’s saying it’s ok in this firmware version it’s probably been fixed. He mentioned earlier he’d read a good bit without issue.

[Sirtel]

Originally Posted by MGlitch

Quoth and I (and others) have reported issues with previous firmware versions and the sage buttons occasionally ceasing to work. So if he’s saying it’s ok in this firmware version it’s probably been fixed. He mentioned earlier he’d read a good bit without issue.

It's gotten considerably better since the beginning. I'm still on 4.34 and I don't feel like bothering with 4.35 as things stand now. The button issue doesn't crop up that often, compared to when I bought my Sage a year ago.

[Quoth]

Originally Posted by MGlitch

Quoth and I (and others) have reported issues with previous firmware versions and the sage buttons occasionally ceasing to work. So if he’s saying it’s ok in this firmware version it’s probably been fixed. He mentioned earlier he’d read a good bit without issue.

Hmm. Buttons stopped working twice today. Sleep/wake fixes it, though using button sometimes it sleeps without sleep screen.

[NiLuJe]

Entering standby at full clock speeds (which is totally an idea I didn't steal from the Kindle's custom hibernation behavior, no siree ;p) appears to have fixed the dropped-input-after-PM issue on the Sage on my end, FWIW. (And also shaves 25% off the resume time, which is what I was originally after. It working around weird kernel issues was just icing on the cake).

(i.e., this is fixed in current KOReader releases).

[DrChiper]

After updating, I had a couple of times a kind of freeze (unresponsive touch screen) right after resuming from sleep mode to start reading. Reentering sleep mode or reset fixed this.
Further, I also did have seen this same freeze after connecting to my PC via the usb-c for charging.
No big issue, but rather annoying.

[mbovenka]

Originally Posted by Quoth

Hmm. Buttons stopped working twice today. Sleep/wake fixes it, though using button sometimes it sleeps without sleep screen.

Using the touch screen fixes it too.

[jospalau]

Originally Posted by mbovenka

Using the touch screen fixes it too.

So, not fixed... 😩

Sent from my CPH2021 using Tapatalk

[mbovenka]

Originally Posted by jospalau

So, not fixed... 😩

Alas, no.

[MGlitch]

Originally Posted by jospalau

So, not fixed... 😩

Sent from my CPH2021 using Tapatalk

But a seemingly huge step toward fixing, twice after a few days of reading is a drastic improvement over what has been the case in previous firmware releases.

[Onemack]

Probably an exaggeration, but after I updated everything went fine for a few days until I sideloaded three books, now I get the message which I fail to comprehend.

Can anyone of you geniuses out there explain what it means and what do I do??


Quote "calibre, version 6.9.0
WARNING: Failed: Kobo database version unsupported - See details

Your Kobo is running an updated firmware/database version. As calibre does not know about this updated firmware, database editing is disabled, to prevent corruption. You can still send books to your Kobo with calibre, but deleting books and managing collections is disabled. If you are willing to experiment and know how to reset your Kobo to Factory defaults, you can override this check by right clicking the device icon in calibre and selecting "Configure this device" and then the "Attempt to support newer firmware" option. Doing so may require you to perform a Factory reset of your Kobo.

Discussion of any new Kobo firmware can be found in the Kobo forum at MobileRead. This is at https://www.mobileread.com/forums/fo...play.php?f=223.

Device database version: 171.
Device firmware version: 4.35.20400" unquote.

Perhaps I should ignore it and hope for the best, Anyhow the three books seem OK but what happens after I've read them I dread to think?

Cheers

[Aleron Ives]

It means that your version of Calibre was released before firmware 4.35, so just in case Kobo made changes to the database format since 4.34, Calibre has entered read-only mode to avoid accidentally corrupting the database. Since Kobo probably did not make any major changes in 4.35, you can probably ignore the error. If you're feeling paranoid, you can update Calibre once a new version that supports 4.35 is released.

[DNSB]

Originally Posted by Onemack

Can anyone of you geniuses out there explain what it means and what do I do??

Perhaps I should ignore it and hope for the best, Anyhow the three books seem OK but what happens after I've read them I dread to think?

Cheers

For what it is worth, you can safely check the Attempt to support newer firmware version checkbox.

[Onemack]

Originally Posted by Aleron Ives

It means that your version of Calibre was released before firmware 4.35, so just in case Kobo made changes to the database format since 4.34, Calibre has entered read-only mode to avoid accidentally corrupting the database....

Thanks for that response, now I understand, although why they didn't put it as succinctly as you have beats me. More words leads to more confusion.

[JSWolf]

Originally Posted by Onemack

Thanks for that response, now I understand, although why they didn't put it as succinctly as you have beats me. More words leads to more confusion.

It's so you come to the forum to find out if the database is compatible.

[mzel]

Originally Posted by DNSB

From my notes, here are the items I saw for this release:

• ----
  
• Fix issue where the OverDrive page (Discover > OverDrive tab) was stuck on "Please wait..." state
  

Many of the changes are oriented towards the Sage/Elipsa.

Mine is stuck on "Please wait". I am on Forma. Should I roll back to 4.34?