Firmware 4.31.19086

[Skydog]

Originally Posted by ownedbycats

Ok. Downgraded to 4.30 and then applied the patch. Ran a few manual syncs to check and it didn't prompt me to upgrade. I think this'll work.

The patch does not eliminate the prompt. At some point you will see a popup announcing an update but with an option to "skip."

[Rid]

Originally Posted by JSWolf

In the file libnickel.so.1.0.0.yaml you want to change no to yes for...

Block WiFi firmware upgrade:
  - Enabled: no

Great timing for me, I thought you could do this but could not find the post

[meeera]

Originally Posted by Skydog

There is a patch that will prevent that.

I'm aware; I've been using the kobo patches for years. This particular patch comes with some pretty significant warnings, so I did not have it installed at the time.

[JSWolf]

Originally Posted by compurandom

I'm convinced that this has been a problem for a long time, but it was harder to trigger, and in '31, it triggers about 1 time in 3 instead of 1 time in 10 or 20.

Did you have a KePub on screen when you plugged in your Kobo? Given what's being said about 4.31, if there is a problem with 4.30, maybe it's to do with KePub.

[JSWolf]

Originally Posted by meeera

I'm aware; I've been using the kobo patches for years. This particular patch comes with some pretty significant warnings, so I did not have it installed at the time.

Others have been using it and I've not read of any problems with it.

[ownedbycats]

Here was the exact warning in the patch files:

      WARNING! THIS IS A DANGEROUS PATCH! READ THE INFORMATION BELOW CAREFULLY!

      THIS PATCH IS UNTESTED, as there is no way to be sure it still works until
      the next firmware version is released. If it works then the firmware will
      not be upgraded during a WiFi sync, but you will still be able to upgrade
      manually or by syncing with the Kobo desktop.

      THIS PATCH COULD RESULT IN A BOOT LOOP when signing out of your Kobo account
      (Settings > Accounts > Sign out) or when invoking a factory reset from the
      device information menu (Settings > Device information > Factory reset).
      REMOVE THIS PATCH BEFORE USING EITHER OF THOSE OPTIONS.
      A factory reset invoked using the hardware methods (such as holding down the
      light button while switching on) should not be affected.

Hopefully I will not have to do either of those in the near future.

[ownedbycats]

Originally Posted by JSWolf

Did you have a KePub on screen when you plugged in your Kobo? Given what's being said about 4.31, if there is a problem with 4.30, maybe it's to do with KePub.

Here is what frostschutz said:

Originally Posted by frostschutz

Umount always fails when you connect within KEPUB (nickel does not release KEPUB filehandle), and sometimes fails when you connect from Home menu (nickel does not release KoboReader.sqlite filehandle).

It makes sense that sqlite being forcibly dismounted while it is being written to would cause db corruption.

[JSWolf]

Originally Posted by ownedbycats

Here is what frostschutz said:

I'm talking 4.30 and not 4.31.

[ownedbycats]

oops, I misread.

[ZodWallop]

Originally Posted by JSWolf

Did you have a KePub on screen when you plugged in your Kobo? Given what's being said about 4.31, if there is a problem with 4.30, maybe it's to do with KePub.

I'm fairly certain on previous firmware versions I connected to Calibre while I had a kepub open. I know that I never went out of my way to go back to the home screen before connecting.

[Skydog]

Originally Posted by ownedbycats

Here was the exact warning in the patch files:

      WARNING! THIS IS A DANGEROUS PATCH! READ THE INFORMATION BELOW CAREFULLY!

      THIS PATCH IS UNTESTED, as there is no way to be sure it still works until
      the next firmware version is released. If it works then the firmware will
      not be upgraded during a WiFi sync, but you will still be able to upgrade
      manually or by syncing with the Kobo desktop.

      THIS PATCH COULD RESULT IN A BOOT LOOP when signing out of your Kobo account
      (Settings > Accounts > Sign out) or when invoking a factory reset from the
      device information menu (Settings > Device information > Factory reset).
      REMOVE THIS PATCH BEFORE USING EITHER OF THOSE OPTIONS.
      A factory reset invoked using the hardware methods (such as holding down the
      light button while switching on) should not be affected.

Hopefully I will not have to do either of those in the near future.

Ahh, you have the full block. There are two patches available, IIRC. The one I was referencing will occasionally offer an update message but user has the option to select either "skip" or "download." No warning disclaimer is associated with this patch (and it works as advertised).

[Skydog]

Originally Posted by meeera

I'm aware; I've been using the kobo patches for years. This particular patch comes with some pretty significant warnings, so I did not have it installed at the time.

There are two. The one I referenced to @ownedbycats is not the same.

[ownedbycats]

I didn't see the other patch, but I only skimmed through the libnickel file.

[Quoth]

The 4.31.19086 too buggy on Elipsa
The 4.30.18838 also is too buggy: Stylus battery sometimes doesn't register. BT on sometimes doesn't turn on BT, but tapping BT toggle always turns on WiFi. An Advanced Notebook hung ereader & all cotent was deleted.

I've gone back to 4.28.17925, which while having BT as a beta feature, works better than 4.31.19086 or 4.30.18838

Checking https://pgaskin.net/KoboStuff/kobofirmware.html and the Kobo forum here for any newer version than 4.31.19086 that fixes bugs.

But on all versions the Elipsa seems only just worth the money as a 10.3" ereader with a separate ewriter notepad with handwriting to text & buggy undocumented shape/equation editing. Finger selection with touch key or BT keyboard text input is the only really useful annotation, just like a Libra 2 (or earlier Kobo with no BT). The stylus annotation only good to copy back visual PDFs, no use for workflow proof edit as no real text.

[rashkae]

Edit: Everything I said here was wrong.