Firmware 4.31.19086

[gtriever]

Originally Posted by Sirtel

Obviously there are bugs in the latest firmware...

Yep. All my device issues have disappeared after rolling back to 4.30.18838.

[ownedbycats]

Did a test myself:

1. Connected the device to Calibre and used KTE to send a book not already on device.
2. Disconnected and waited for import to finish.
3. Powered down the device, and turned it back on.
4. Tested that reading position was being saved. (It was.)
5. Re-connected the device.

No scan&fix prompt!

[icallaci]

Originally Posted by ownedbycats

Did a test myself:

1. Connected the device to Calibre and used KTE to send a book not already on device.
2. Disconnected and waited for import to finish.
3. Powered down the device, and turned it back on.
4. Tested that reading position was being saved. (It was.)
5. Re-connected the device.

No scan&fix prompt!

Thanks for confirming it works for you too. I hope Kobo fixes this soon.

[agugu]

Originally Posted by gtriever

Yep. All my device issues have disappeared after rolling back to 4.30.18838.

need a factory reset??or just roll back by dropping the 4.30 file to .kobo and reboot???

[Deobulakenyo]

Originally Posted by agugu

need a factory reset??or just roll back by dropping the 4.30 file to .kobo and reboot???

you can just do the second one

[ownedbycats]

Originally Posted by agugu

need a factory reset??or just roll back by dropping the 4.30 file to .kobo and reboot???

Dropping 4.30 files in and rebooting will work. Avoid sync (or disable wifi entirely if you don't need it) or it'll try to upgrade you again.

[gtriever]

Originally Posted by agugu

need a factory reset??or just roll back by dropping the 4.30 file to .kobo and reboot???

Just extract the zip file to the .kobo folder and eject the device. It'll automatically reboot and install. Make sure wifi and automatic sync are turned off on the reader so it doesn't try to update again.

And, the next connect to Calibre will tell you a new firmware version is available and ask if you want to install it. Obviously the answer is 'no'.

[JSWolf]

Originally Posted by gtriever

Just extract the zip file to the .kobo folder and eject the device. It'll automatically reboot and install. Make sure wifi and automatic sync are turned off on the reader so it doesn't try to update again.

And, the next connect to Calibre will tell you a new firmware version is available and ask if you want to install it. Obviously the answer is 'no'.

That's not correct. You want to extract the entire contents of the firmware ZIP file to the .kobo directory. That way if there were any changes to the OS (Linux) they will be reversed.

As to connecting to Calibre after backing down the firmware, Calibre does not tell you there is a new firmware unless you select to have Kobo Utilities check for a newer firmware or have it set to check daily. Most do not Kobo Utilties set to check for newer firmware daily.

[rashkae]

I have just made a very interesting observation about firmware 4.31 that I think can explain the issues people have been reporting. I connected my Kobo to my Linux computer and navigated to the .kobo folder very soon thereafter in my desktop file browser. I saw some temporary sqlite files appear in the file list, then disappear without my doing anything. My only conclusion here, the Kobo had not finished unmounting the user partition before allowing the computer to mount it.

Edit: That might not be the whole story, hoiwever. I can see the same thing happening after revering to 4.30,, but at least now I don't have to re-boot the kobo for the database to update properly again.

Edit 2: I had Calibre open. That was responsible for creating then deleting the temp files as part of it'sscanning books on device. Sorry for the noise.

[frostschutz]

Originally Posted by rashkae

My only conclusion here, the Kobo had not finished unmounting the user partition before allowing the computer to mount it.

It's possible, it happened before.

Kobo uses lazy umounting, and "lazy" means it's not unmounted at all while still in use.

The result is filesystem inconsistency and perhaps includes Windows complaining about the filesystem.

I had a mod to detect this condition ( https://www.mobileread.com/forums/sh...d.php?t=263674 to display a happy or sad smiley face depending on umount status ) and try to detect the cause what is preventing the umount, but of course it's old and unmaintained and probably won't work, for current devices.

Back then it was the KEPUB Reader that prevented umount if you connected while reading the book, it was fine if you connected USB from the home menu.

Of course any addon can also block it, if it has anything in /mnt/onboard open.

[Koboder]

Hi everyone.
I have noticed this on two devices Kobo Libra 2.
After the update ver. 4.31.19086, if I turn off the device with Wi-Fi off, it will freeze during startup.
To restart it I have to connect it to the PC and hold the power botton.
If I turn it off with the Wi-Fi on, the device is working properly.

I also tried the reset. It works fine but I don't have to start the sync or it will download the update again and the problem shows up again.

Does anyone have the same problem or know how to fix it?

[Sirtel]

The only fix at the moment is downgrading to 4.30 and keeping sync/wifi off until Kobo releases the official fix.

[ownedbycats]

Originally Posted by rashkae

I have just made a very interesting observation about firmware 4.31 that I think can explain the issues people have been reporting. I connected my Kobo to my Linux computer and navigated to the .kobo folder very soon thereafter in my desktop file browser. I saw some temporary sqlite files appear in the file list, then disappear without my doing anything. My only conclusion here, the Kobo had not finished unmounting the user partition before allowing the computer to mount it.

Edit: That might not be the whole story, hoiwever. I can see the same thing happening after revering to 4.30,, but at least now I don't have to re-boot the kobo for the database to update properly again.

Edit 2: I had Calibre open. That was responsible for creating then deleting the temp files as part of it'sscanning books on device. Sorry for the noise.

Originally Posted by frostschutz

It's possible, it happened before.

Kobo uses lazy umounting, and "lazy" means it's not unmounted at all while still in use.

The result is filesystem inconsistency and perhaps includes Windows complaining about the filesystem.

I had a mod to detect this condition ( https://www.mobileread.com/forums/sh...d.php?t=263674 to display a happy or sad smiley face depending on umount status ) and try to detect the cause what is preventing the umount, but of course it's old and unmaintained and probably won't work, for current devices.

Back then it was the KEPUB Reader that prevented umount if you connected while reading the book, it was fine if you connected USB from the home menu.

Of course any addon can also block it, if it has anything in /mnt/onboard open.

I wonder if that could also explain the database instability I had? If the database wasn't properly closed, I could see how that might result in it getting malformed (or at the very least data loss).

Fortunately for me, I've not had any issues since I started doing a reboot after loading new books.

[WormGod]

Originally Posted by davidfor

And I tend to read epubs on the Clara HD but kepubs on the Libra H2O. The only epubs that end up on the Libra H2O are ones for testing something.

A little off-topic, but curious - is there a reason why you use epubs on the Clara but kepubs on the Libra H2O?

[davidfor]

Originally Posted by WormGod

A little off-topic, but curious - is there a reason why you use epubs on the Clara but kepubs on the Libra H2O?

It was sort of accidental. I was testing a problem and removed all sideloaded books from the Libra H2O to prove it wasn't related to them. For a while, I was reading purchased books on the Libra H2O and sideloaded books on the Clara HD. When I started sideloading on the Libra H2O again, I went with kepubs to avoid the font scaling issues between epubs and kepubs.

The other part of it is that I am not great fan of the 6.8"/7" size. I tried an Aura H2O before and didn't find the extra screen size made up for the extra bulk. The same goes for the Libra H2O. But, I like the buttons. So, I end up splitting my reading between the two. But, I have, much to my surprise, find the 8" screens to be good. I am deciding about a Sage at the moment. I got one last year and it is in my wife's hands. I was expecting to use her Sage for while, but, there is some screen damage and that is making it unusable.