Firmware 4.38.21908

[maddz]

I'm trying to dowload and install the new firmware, but am getting this error via Calibre:

HTTP Error 403: Forbidden

Traceback (most recent call last):
File "calibre/gui2/device.py", line 104, in run
File "calibre_plugins.koboutilities.jobs", line 123, in do_check_firmware_update
resp = urlopen(update_data["UpgradeURL"])
File "urllib/request.py", line 216, in urlopen
File "urllib/request.py", line 525, in open
File "urllib/request.py", line 634, in http_response
File "urllib/request.py", line 563, in error
File "urllib/request.py", line 496, in _call_chain
File "urllib/request.py", line 643, in http_error_default
urllib.error.HTTPError: HTTP Error 403: Forbidden

Not sure if this a Kobo or a Calibre issue...

[DNSB]

Originally Posted by maddz

I'm trying to dowload and install the new firmware, but am getting this error via Calibre:

Spoiler:

HTTP Error 403: Forbidden

Traceback (most recent call last):
File "calibre/gui2/device.py", line 104, in run
File "calibre_plugins.koboutilities.jobs", line 123, in do_check_firmware_update
resp = urlopen(update_data["UpgradeURL"])
File "urllib/request.py", line 216, in urlopen
File "urllib/request.py", line 525, in open
File "urllib/request.py", line 634, in http_response
File "urllib/request.py", line 563, in error
File "urllib/request.py", line 496, in _call_chain
File "urllib/request.py", line 643, in http_error_default
urllib.error.HTTPError: HTTP Error 403: Forbidden

Not sure if this a Kobo or a Calibre issue...

This is an issue with changes that Kobo made in the download URLs for firmware. Use Patrick Gaskin's Kobo Firmware Downloads to download the firmware instead.

[Amon_Re]

Does anyone know when the database corruption first started? It happened again and I'm growing tired of it.

[jospalau]

Originally Posted by Amon_Re

Does anyone know when the database corruption first started? It happened again and I'm growing tired of it.

This solved it for me but don't do it
[FeatureSettings]
ExcludeSyncFolders=.*

I decided to use KOReader exclusively a few weeks ago. In any case I never used the stock reader

Sent from my 22081212UG using Tapatalk

[ownedbycats]

Originally Posted by Amon_Re

Does anyone know when the database corruption first started? It happened again and I'm growing tired of it.

It occurred in early 2022 (4.31), but got fixed at some point. I think the reports of it reoccuring were 4.34-36 or somewhere along there.

[Aleron Ives]

Both 4.34 and 4.35 seem to be unaffected. 4.36 was only for the Elipsa 2E, so 4.37 and 4.38 seem to be the culprits.

[JSWolf]

Originally Posted by Aleron Ives

Both 4.34 and 4.35 seem to be unaffected. 4.36 was only for the Elipsa 2E, so 4.37 and 4.38 seem to be the culprits.

4.38 here on my Libra 2 and not a single database corruption nor the need to reboot. I go to the home screen and then plug the Kobo intot he computer.

[ownedbycats]

It's less likely to happen when connecting from the home screen. I've only seen it when either connecting from within a kepub or connecting immediately after importing multiple new books.

[JSWolf]

Originally Posted by ownedbycats

It's less likely to happen when connecting from the home screen. I've only seen it when either connecting from within a kepub or connecting immediately after importing multiple new books.

Does it happen if you connect to the USB using NickelMenu so you can update the metadata? I've not had it happen doing this to update the metadata.

[ownedbycats]

Originally Posted by JSWolf

Does it happen if you connect to the USB using KOReader so you can update the metadata? I've not had it happen doing this to update the metadata.

I'd be surprised if it does, because I don't even use KOReader.

[Haggis70]

I'm having a bit of a strange, annoying, and slightly absurd problem. I've had many Kobo readers over the years, and currently have a Sage. This problem started in one of the recent firmware updates. I do not have any mods or patches, and have tried a factory reset. I've also tried different books and file types (EPUB, KEPUB). (Edit: did some testing, this started happening with v4.37.21533. v4.35.20400 seems fine.)

The problem is that when I hold my finger on the screen for an extended period of time (~2-5 minutes), the Kobo crashes and reboots. This also causes the Kobo to lose track of any pages I read during that session.

Why am I holding my finger on the screen for 5 minutes, you ask? Well, reading helps me fall asleep, so I often doze off holding the Kobo. I don't care if it reboots, but losing my place is getting annoying.

I can 100% recreate this problem with my Sage, but not with my wife's Clara 2E.

Anyone else notice this? Is there any fix or workaround, such as forcing the Kobo to record the current position after every page?

[Aleron Ives]

If it's a firmware bug introduced in 4.37, the only current solution would be to roll back to 4.35 and hope Kobo fixes it in 4.39.

[Cootey]

Originally Posted by Cootey

Shutting off WiFi’s a great suggestion. I’ll implement that right away.

I don’t use calibre to manage my collections, so I do not believe I’ve run into that particular bug. (Interesting thread, though! )

Something’s off. That’s for sure. I just noticed it was completely dead and the battery bank connected to it was half drained. That’s enough energy to charge two iPads.

Wi-Fi was clearly the culprit. I charged to 100%, turned Wi-Fi off, and my Elipsa 1 has not crashed or had its battery drained since October 19. That’s two weeks, and I still have a 89% charge.

I purchase a lot of books, as well as use Kobo Plus and Overdrive, so syncing with Kobo’s servers and not depleting my battery is something I expect my Kobo ereaders to do. These last two firmware releases haven’t been so cooperative.

I’m going to backup my DB, then do a soft factory reset. That fixed Wi-Fi sync loop issues in the past. Obviously, that’s destructive to stats, so I’ll try to recreate whatever I can. Unlike my past Kobos, I can’t pop out a micro SD card from the Elipsa to make a full backup in order to restore it if things go awry.

Can you think of anything else I could do to isolate this issue? I’m curious to know why having a PDF or Notebook open would cause battery draining while Wi-Fi is turned on.

[JSWolf]

Originally Posted by ownedbycats

I'd be surprised if it does, because I don't even use KOReader.

My mistake. I meant NickelMenu. Do you use NickelMenu to connect to USB a second time to update the metadata without unplugging the USB cable?

[ownedbycats]

Originally Posted by JSWolf

My mistake. I meant NickelMenu. Do you use NickelMenu to connect to USB a second time to update the metadata without unplugging the USB cable?

Yes. My usual method is to plug in the cable, autoconnect to PC, let Calibre send the books. Then I disconnect and wait for the "importing..." screen to disappear and main menu to reappear then use NickelMenu to re-connect.

Unfortunately, I found that re-connecting immediately after the import process is more likely to result in "drive has an error" and subsequent database corruptions. (It doesn't happen when overwriting existing books--think fanfiction updates--only when the 'importing' screen pops up.)

So instead I just use NickelMenu to trigger a reboot, this ensures that the database is closed. If the USB is plugged in, it'll autoconnect to Calibre after startup.