Firmware 4.32.19501

[Deobulakenyo]

Originally Posted by davidfor

The driver will update the metadata on the device when the device is next connected. What is update depends on what has changed in the library. But, as I stated in post immediately under the one you quoted, this will not happen as calibre will need another update.

Okay thank you. I am beginning to understand this little by little. Thank you for your patience

[dagrim1]

Are notebooks screwed up for anyone else?

I actually don't use them, no pen, but I had a test-notebook in the notebook section which wouldn't open. Could remove and create a new one, which took way to long to show, but then was missing some UI elements of the navigation bar and all so I couldn't return to the home screen anymore. Also, couldn't open the newly created notebook either.

A reboot allowed me to return to the home screen but going into notebooks and opening the test notebook messed things up again.

Not too bothered because as mentioned, I don't actually use them, but still...

[Stevex]

Originally Posted by Sirtel

That's not my experience. Both my Sage and Libra 2 have updated normally.

Ditto for me, that‘s definitely not normal behaviour (multiple reboots)

Been on the new firmware for a week now, no hangs yet, but I would say it needs a good month to be sure.

[Sirtel]

Originally Posted by davidfor

In a discussion in the KoboTouchExtended driver thread, I discovered that one of the changes I had expected in firmware 4.32.19501 is not in it. This means that the version of the database I was using for testing is higher than that in the released firmware. I was expecting the database version to be 169, but, it is apparently 168. And that means that the test in the driver to see if the bookstats can be set in the database will fail. And the stats will not be set. Which explains why few people have seen them.

I have fixed this in the code and checked it in. Unfortunately, it will only be available when the next release of calibre is made.

It is possible to update the database version in the database. This will let the function work, but, it could cause issues when the next firmware is released. If you do this, you should undo it before the next release.

Thank you for your work on this. I'm going to wait for the next release.

[Deobulakenyo]

Originally Posted by Stevex

Ditto for me, that‘s definitely not normal behaviour (multiple reboots)

Been on the new firmware for a week now, no hangs yet, but I would say it needs a good month to be sure.

I factory reset again (holding button up while pressing power button), it factory reset to old fw but it updated automatically to 4.30.

Without using any mod and patches (nickelmenu, nanoclock), i rebooted many times while in 4.30, and no problems in reboots. Device rebooted fast and no problems.

After this I synced again and an update was found (now it is 4.32, last week 4.31 was still the latest update in my region), so i downloaded the update, and it rebooted to update. 3 times it cycled and flashed going back and forth from 3 dots to white flashing screen, then rebooted to 4.32 homescreen.

I turned off the device rebooted again to test. and the reboot cycled again and took multiple 3 dots screen going back and forth with two screen flashes (3 dots, white screen flashes, 3 dots, white screen flashes, 3 dots, white screen flashes, 3 dots, then rebooting to homescreen.

I did it again and it was fine, fast boot.

I did it again and it was the problematic boot again.

I did it again and it was fine, fast boot.

I did it again and it was fine, fast boot.

I did it again and it was the problematic boot again.

I tried it one last time and it boots problematic again.

I am now factory resetting to see if this problems will manifest in 4.30 fw.

i had a horrible time dealing with 4.31 and now 4.32.

[MGlitch]

Originally Posted by Deobulakenyo

I factory reset again (holding button up while pressing power button), it factory reset to old fw but it updated automatically to 4.30.

Without using any mod and patches (nickelmenu, nanoclock), i rebooted many times while in 4.30, and no problems in reboots. Device rebooted fast and no problems.

After this I synced again and an update was found (now it is 4.32, last week 4.31 was still the latest update in my region), so i downloaded the update, and it rebooted to update. 3 times it cycled and flashed going back and forth from 3 dots to white flashing screen, then rebooted to 4.32 homescreen.

I turned off the device rebooted again to test. and the reboot cycled again and took multiple 3 dots screen going back and forth with two screen flashes (3 dots, white screen flashes, 3 dots, white screen flashes, 3 dots, white screen flashes, 3 dots, then rebooting to homescreen.

I did it again and it was fine, fast boot.

I did it again and it was the problematic boot again.

I did it again and it was fine, fast boot.

I did it again and it was fine, fast boot.

I did it again and it was the problematic boot again.

I tried it one last time and it boots problematic again.

I am now factory resetting to see if this problems will manifest in 4.30 fw.

i had a horrible time dealing with 4.31 and now 4.32.

Given all the peculiarities of your Libra 2, I think you’d be best served trying to convince Kobo to replace it for you. I know you’ve said it eventually gets to the Home Screen but something is clearly going wrong on a regular enough basis that you’re very aware of it.

I don’t think it’s a software fault in your case since it’s persisted through two or three firmware releases and presented with symptoms that even those who had consistent issues with 4.31 did not see.

And it’s better to try now as near to your purchase as possible, Kobo would be more inclined to believe you aren’t trying to pull a fast one on them just to get a new device.

I would suggest being persistent, tell whoever you talk with at Kobo that you’ve gone through many factory resets and the problem persists. Because it does actually persist even if you get a few good reboots back to back you’re still getting bad ones as well.

[davidfor]

Originally Posted by Deobulakenyo

I factory reset again (holding button up while pressing power button), it factory reset to old fw but it updated automatically to 4.30.

Without using any mod and patches (nickelmenu, nanoclock), i rebooted many times while in 4.30, and no problems in reboots. Device rebooted fast and no problems.

After this I synced again and an update was found (now it is 4.32, last week 4.31 was still the latest update in my region), so i downloaded the update, and it rebooted to update. 3 times it cycled and flashed going back and forth from 3 dots to white flashing screen, then rebooted to 4.32 homescreen.

I turned off the device rebooted again to test. and the reboot cycled again and took multiple 3 dots screen going back and forth with two screen flashes (3 dots, white screen flashes, 3 dots, white screen flashes, 3 dots, white screen flashes, 3 dots, then rebooting to homescreen.

I did it again and it was fine, fast boot.

I did it again and it was the problematic boot again.

I did it again and it was fine, fast boot.

I did it again and it was fine, fast boot.

I did it again and it was the problematic boot again.

I tried it one last time and it boots problematic again.

I am now factory resetting to see if this problems will manifest in 4.30 fw.

i had a horrible time dealing with 4.31 and now 4.32.

What is the horrible time you are having dealing with 4.32? Is it just that it takes longer to boot? And that it's boot pattern is different than in 4.30? Or is it just that the boot pattern isn't always the same? I honestly can't tell you if the boot pattern has changed, because I hardly ever see it. I mainly see it when the device is updating firmware, and then I expect it to take longer. I don't shutdown the device, because there is no reason to.

Are you having any actual problems using 4.32 when it is running?

[ownedbycats]

Originally Posted by davidfor

In a discussion in the KoboTouchExtended driver thread, I discovered that one of the changes I had expected in firmware 4.32.19501 is not in it. This means that the version of the database I was using for testing is higher than that in the released firmware. I was expecting the database version to be 169, but, it is apparently 168. And that means that the test in the driver to see if the bookstats can be set in the database will fail. And the stats will not be set. Which explains why few people have seen them.

I have fixed this in the code and checked it in. Unfortunately, it will only be available when the next release of calibre is made.

It is possible to update the database version in the database. This will let the function work, but, it could cause issues when the next firmware is released. If you do this, you should undo it before the next release.

Are the changes in source yet? If so, I'll just switch over to running from source.

[jackie_w]

Originally Posted by codychan

There is something wrong with the font in this version of firmware, some characters in one of my customized dictionary can not be displayed, it is OK in previous firmware, rollbacked.

It sounds like you have been using a patch to set a customised font for the dictionary pop-ups. The problem is described in the designated 4.32 kobopatch thread. If you need to post more about this problem you should do it in that thread, not this one.

Originally Posted by codychan

And another issue is, I use a font specifically for some part in my ebook(in css), but new firmware won't use it, it uses the default font instead.

Similarly, you'll find more info in this post in the kobopatch thread.

[PeterT]

Originally Posted by ownedbycats

Are the changes in source yet? If so, I'll just switch over to running from source.

Yep

Sent from my Pixel 4a using Tapatalk

[sherman]

Originally Posted by sherman

So, just had another thought about the webkitTextRendering, it could potentially be used to perform CSS injection in the body tag.

I mean, the relevant bit is

text-rendering: %3;

Where %3 is a string.

So, what's stopping something like

webkitTextRendering=optimizeLegibility;font-family:sans-serif;text-align:center

from working?

Note, I haven't tested anything, but I don't see a reason why it wouldn't work.

Thinking more about this, I don't see a reason why you couldn't also set CSS for more tags and elements too, so long as the final result is valid CSS. Eg:

webkitTextRendering=optimizeLegibility;} p {text-align: center

Note, this idea relies on the fact that the text-rendering: %3; is at the end of the block of CSS.

[codychan]

Thanks for you information, didn't notice that.

Originally Posted by jackie_w

It sounds like you have been using a patch to set a customised font for the dictionary pop-ups. The problem is described in the designated 4.32 kobopatch thread. If you need to post more about this problem you should do it in that thread, not this one.

Moved to: https://www.mobileread.com/forums/sh...7&postcount=45

Originally Posted by jackie_w

Similarly, you'll find more info in this post in the kobopatch thread.

Moved to: https://www.mobileread.com/forums/sh...5&postcount=43

Well, it turns out there is nothing I can do about it. Move back to firmware v4.31.19086

[icanhardlyread]

Deobulakenyo apparently isn't the only one is running into issues with 4.32...

My Libra 2 has been running absolutely fine on 4.30, but now that I wanted to update to 4.32, it has been behaving quite oddly. When it's on 4.30, it detects that an update is available, downloads it and then asks whether to update immediately or update later. Either way, something about the update seems to go wrong - after a couple of 'three-dot screens', it boots back up and is still on 4.30. However, it won't connect to a PC via USB again, and nothing short of a factory reset will get it to do that again. Which doesn't stop it from happily announcing that an update is available, however...

I'm wondering - what are the odds of both of our devices having the same defect that only shows up in one specific update (since 4.28 -> 4.30 goes without a hitch)? Could it maybe be have something to do with affiliate or regional things rather than a hardware fault?

[MGlitch]

Originally Posted by icanhardlyread

Deobulakenyo apparently isn't the only one is running into issues with 4.32...

My Libra 2 has been running absolutely fine on 4.30, but now that I wanted to update to 4.32, it has been behaving quite oddly. When it's on 4.30, it detects that an update is available, downloads it and then asks whether to update immediately or update later. Either way, something about the update seems to go wrong - after a couple of 'three-dot screens', it boots back up and is still on 4.30. However, it won't connect to a PC via USB again, and nothing short of a factory reset will get it to do that again. Which doesn't stop it from happily announcing that an update is available, however...

I'm wondering - what are the odds of both of our devices having the same defect that only shows up in one specific update (since 4.28 -> 4.30 goes without a hitch)? Could it maybe be have something to do with affiliate or regional things rather than a hardware fault?

What happens if you manually update to 4.31 or 4.32 instead of doing an OTA update?

You can grab the firmware updates from https://pgaskin.net/KoboStuff/kobofirmware.html just scroll to Libra 2. You’ll need to select older firmware to get 4.31.

Assuming that doesn’t work what affiliate is your Kobo set to? And if you’re comfortable saying what country are you in?

[icanhardlyread]

Originally Posted by MGlitch

What happens if you manually update to 4.31 or 4.32 instead of doing an OTA update?

You can grab the firmware updates from https://pgaskin.net/KoboStuff/kobofirmware.html just scroll to Libra 2. You’ll need to select older firmware to get 4.31.

Assuming that doesn’t work what affiliate is your Kobo set to? And if you’re comfortable saying what country are you in?

First of all, for some reason my post just disappeared after editing, so if it reappears all of a sudden, I'm sorry for the double posting.

Incidentally, I was actually trying what you suggested before I saw your post. A full factory reset shows that updating from 4.28 to 4.30 goes without issues - as does a manual update to 4.31. But going from 4.31 to 4.32 results in a non-update. Interestingly enough, I do seem to get the 4.32 patch notes after the reboot - but the device info shows that I'm actually still on 4.31.

My affiliate is Kobo (according to affiliate.conf), and I live in Germany.