Firmware 4.32.19501

[ownedbycats]

Originally Posted by MGlitch

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

Now I'm curious as your thought process: could one of the servers have sent out a glitched copy of the firmware?

[icanhardlyread]

Alright, here I go again - somehow, the forum is eating my posts. My apologies if they all show up at once.

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?

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 (shows up in affiliate.conf), and I live in Germany.

[MGlitch]

Originally Posted by icanhardlyread

Alright, here I go again - somehow, the forum is eating my posts. My apologies if they all show up at once.



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 (shows up in affiliate.conf), and I live in Germany.

Yeah something was going on with the forum I kept seeing a new post but it never showed up.

So you can get to 4.31 safely which is good. I know someone else had to apply the 4.32 update twice to get it to stick, and I had a weird experience where I could have sworn my Libra 2 was on 4.31 but after updating to what I thought was 4.32 showed as 4.31. I didn’t pay attention to the notes, but I didn’t have the features of 4.32 until a second update.

It’s interesting that in every case it’s the Libra 2.

Best I can suggest for now is to try manually updating again. Hopefully that gets you to 4.32.

[Deobulakenyo]

Originally Posted by davidfor

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?

Aside form taking longer to boot, i experienced my libra 2 hanging last night. screen and buttons don't respond while frontlight is on.

Then screen turns off light, but BG image became the book cover, light flashing slowly. Pressing power button doesn't do anything.

I remembered some posts here saying that happened to them and connecting to PC resolves the issue. I do not have a PC where I was so i just connected the Libra 2 to a powerbank, then pressed the button and it turned on on my reading screen (not homescreen)

This is the first time i experienced my device hanging while yirned on. The problems in reboots i considered hanging also but not while using the device.

For the record, There really is no reason to reboot and turn off the device, but probably the reason it seems i am the only one experiencing this is because i have to restart my device often because nanoclock kept on disappering on me every after disconnecting from calibre. To make it reappear, i had to restart my device (often multiple times of restarts for it to reappear). If not for that, i would't be able to document these restart/reboot problems. and i often initiate restarts and power off using nickelmenu (so as not to abuse the power button)

I am in the Philippines and my affiliate is Kobo

[JSWolf]

Originally Posted by Terisa de morgan

Just a question. Has anybody of you seen their reader taking much more time to update than usual?

When I installed 4.32, it did take longer to end up at the home screen.

[JSWolf]

Originally Posted by codychan

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

Where you will find that if you side load, eventually, you will end up with s corrupt database due to bugs in 4.31. Either go back to 4.30 and apply the patch to prevent WiFi firmware updates or go to 4.32 and just ignore the issue.

[codychan]

Originally Posted by JSWolf

Where you will find that if you side load, eventually, you will end up with s corrupt database due to bugs in 4.31. Either go back to 4.30 and apply the patch to prevent WiFi firmware updates or go to 4.32 and just ignore the issue.

corrupt database? Already happened over 10 times in multiple firmwares in more than 3 years of using Kobo Forma, I always have backups when I connect it to my PC using Calibre, so sad to say that I already got used to it.

prevent WiFi firmware updates, already did, always use firmware zip file and then apply patches.

[ownedbycats]

Originally Posted by codychan

corrupt database? Already happened over 10 times in multiple firmwares in more than 3 years of using Kobo Forma, I always have backups when I connect it to my PC using Calibre, so sad to say that I already got used to it.

prevent WiFi firmware updates, already did, always use firmware zip file and then apply patches.

4.31 had a bug that made it more likely to occur -- I got a corrupt db three times in a week, and it does get rather annoying to restore the backups. So if you sideload and need to downgrade, 4.30 is more stable.

[codychan]

Originally Posted by ownedbycats

4.31 had a bug that made it more likely to occur -- I got a corrupt db three times in a week, and it does get rather annoying to restore the backups. So if you sideload and need to downgrade, 4.30 is more stable.

Thanks, the frequency of corrupting db for me is not that high, pretty normal frequency.

And Firmware 4.31.19086 adds feature matters to me. So I'll use it instead.

[icanhardlyread]

Originally Posted by MGlitch

Yeah something was going on with the forum I kept seeing a new post but it never showed up.

So you can get to 4.31 safely which is good. I know someone else had to apply the 4.32 update twice to get it to stick, and I had a weird experience where I could have sworn my Libra 2 was on 4.31 but after updating to what I thought was 4.32 showed as 4.31. I didn’t pay attention to the notes, but I didn’t have the features of 4.32 until a second update.

It’s interesting that in every case it’s the Libra 2.

Best I can suggest for now is to try manually updating again. Hopefully that gets you to 4.32.

Thanks for the help, but unfortunately, I've now tried updating manually 3 times in a row, and the Kobo tries updating OTA basically anytime it syncs; 4.32 just won't stick.

While I'm new to Kobo, I'm not a stranger to Linux - are there maybe any logs I could access on the device to try and locate the exact point of failure?

[icanhardlyread]

Obviously, I could just stay on 4.30 and be mostly happy, but since I have issues, I keep poking and prodding the thing.

So far, I've discovered that the only update that will work from 4.30 is a manual update to 4.31; any OTA update will fail. This makes me think that something might already be going wrong during the 4.30 update after all - as if that leaves the firmware partition in a bad state.

Are Kobo FW updates incremental, or should I be able to go straight from 4.28 to 4.32 if I did it manually? I'm asking because I've noticed that setup via the Kobo app always seems to go from 4.28 to 4.30.

[Quoth]

I went from 4.28.x to 4.32.x direct, manually, on the Elipsa.

[MGlitch]

Originally Posted by ownedbycats

Now I'm curious as your thought process: could one of the servers have sent out a glitched copy of the firmware?

I’d be surprised if this was the case. So far we have three countries where we have users with the issue, Germany, the Philippines, and the USA. I’ve not checked my Libra 2s affiliate but I doubt even that is the common link. I’ve got several generations of devices and the only one that might have had issues with 4.32 was the Libra 2, which is the device others are having issues with.

[Katsunami]

Originally Posted by Quoth

I went from 4.28.x to 4.32.x direct, manually, on the Elipsa.

Got you beat there... my reader was on an even older firmware. I went fron 4.20.x directly to 4.31 and to 4.32 just after the patches were released, a few days later...

[JSWolf]

Originally Posted by Quoth

I went from 4.28.x to 4.32.x direct, manually, on the Elipsa.

I went from 4.30 to 4.32 and I had no problems doing so manually. I've also applied patches.