Firmware 4.37.21586

[Aleron Ives]

If people have mentioned having problems, that would suggest it is possible to have problems, does it not?

[DNSB]

Originally Posted by petercreasey

Is the current version really a problem for the Forma as people have mentioned upthread?

My old Forma does not seem to have issues with 4.37.21586. However this does not preclude someone else from seeing an issue. Anything from the books on the device to the driver software and chipset of the computer being connected to could potentially cause issues.

[compurandom]

Originally Posted by petercreasey

Is the current version really a problem for the Forma as people have mentioned upthread?

I have a forma and I don't see any version of the firmware this year being any buggier.

[petercreasey]

Thanks, I feel better.

[patrik]

My Forma is getting the "dirty bit" problem when connecting to a Windows machine again... it's been quite many firmwares that's been working fine.

Annoying...

[JSWolf]

Originally Posted by patrik

My Forma is getting the "dirty bit" problem when connecting to a Windows machine again... it's been quite many firmwares that's been working fine.

Annoying...

Are you sue this is not user error?

[patrik]

Yes, 100%.

[ownedbycats]

Originally Posted by JSWolf

Are you sue this is not user error?

If it's an error with .21582, it's 'update the firmware.' If it's an error with .21586, it's suddenly user error.

[DNSB]

Originally Posted by JSWolf

Are you sue this is not user error?

Jon, considering the number of people who have experienced the error and that almost all the reports I've seen mention it's erratic nature, I think user error i.e. not safely ejecting, can be placed as a low probability cause.

[compurandom]

Originally Posted by DNSB

Jon, considering the number of people who have experienced the error and that almost all the reports I've seen mention it's erratic nature, I think user error i.e. not safely ejecting, can be placed as a low probability cause.

I'm sure I am safely ejecting.
I'm not sure I remembered to turn off wifi and make sure it wasnt running a sync when I plugged it in. I think something is still getting stuck in the background occasionally.

I'm also not sure that I don't have hardware failure, like ram that randomly flips bits. Because at least once, my database got corrupted, so I plugged it back in and copied over the previous database backup and ejected and got a blank home screen with no books...and then rebooted and all was fine.

[icallaci]

I've got an Elipsa that was working flawlessly before I stupidly decided to factory reset it and reload my books in an attempt to compact the ever-growing database. I was on 4.37.21586 before I reset it, and I am still on 4.37.21586 now. I reloaded only the books that were already on the reader before the factory reset, so I don't think it's a rogue ebook causing the problem. After the reset, I am experiencing the dirty bit and a corrupted database quite often. I am doing some experiments to try to narrow things down, and will report back if I manage to find a reliable way to duplicate the issue. But I find it very odd that I never had a single problem with the Elipsa until I factory reset it.

[Aleron Ives]

If the problem persists, you could try doing the developer factory reset that also reverts to the launch firmware and essentially erases everything you've done since you got the device.

[icallaci]

Originally Posted by Aleron Ives

If the problem persists, you could try doing the developer factory reset that also reverts to the launch firmware and essentially erases everything you've done since you got the device.

Is that different than the factory reset done through the menu?

Edit: Aha. I found the two different ways to do a factory reset. I will try a few more things to see if I can narrow down what specific actions are causing the dirty bit and corrupted database. If I can't figure it out, I will do a manual reset and start over. Thanks for the tip.

[Haesslich]

21586 is a step up over the previous three versions which locked up much more often than this one. I've only had to factory reset it once so far, versus the every two weeks with some of the previous versions.

I've seen much worse, although none of the version 5.x ones have been superlative.

[icallaci]

I am beginning to think that Calibre is not closing all of the files on the Kobo when I eject using Calibre's menu. Still testing, but as long as I don't open Calibre while the Kobo is connected via USB cable, my Kobo is happy. If I open Calibre and do absolutely nothing but eject immediately, everything looks ok (the Kobo is ejected in Windows Explorer) but the next time I connect, bingo--corrupted database and/or dirty bit set. I will keep testing to see if I can reliably duplicate this. It may take a few days because I want to make sure it's not random, which means I need to try various intervals of connecting via USB with and without Calibre open. I did try closing Calibre after ejecting the Kobo but before removing the USB cable, and still got corruption.

Edit: If I close Calibre while the Kobo is connected, and then use Windows to eject the Kobo, everything seems to work. But, again, I need to do more testing to make sure. I will try using Calibre as I normally do, but I will close Calibre before ejecting my Kobo through Windows to see if I get any corruption.