Firmwares 4.39.23027 and 4.38.23038

[ghira]

Originally Posted by DNSB

If you have developer mode enabled, that will happen. If you tap on the battery icon, you will see the eReader power level, the PowerCover power level and the cilix power level even if you don't have a PowerCover or a styus.

I do not have devmode enabled as far as I know. But I'll check and disable it if it's on.

It only displays this from time to time. Which seems a bit odd.

[ghira]

Originally Posted by mathil

You should check that the collections on your Kobo correspond to those present on your Kobo account. If there's a difference syncing will hang. I had the same issue for years until I deleted all of the collections manually on my Kobo and my Kobo account (using the app). I synced and then everything worked properly. If you use Calibre recreating your collections afterwards is very easy.

I very very rarely use Calibre to edit files with serious problems. Less than once a year?

I do not use it to copy things to the Kobo. I didn't even know my Kobo account knew about collections. I'll check that. Thanks. Well what do you know? I had never noticed that. Collections look the same as far as I've checked but I have a lot to go.

[hatuluang]

Hi,
I want to inform as titled said some patches from 4.38.21908 didn't work on 4.38.23038 as follows:

src/libnickel.so.1.0.0.yaml:
    Customize ComfortLight settings: yes
    Don't uppercase header/footer text: yes
    Don't uppercase header/footer text and change page number text: yes
src/nickel.yaml:
    Increase size of kepub chapter progress chart: yes

I ran kobopatch.bat one by one to the four patches and it didn't work. The other patches I used worked fine. I use Clara 2E.
So I will wait the release of kobopatch 4.38.23038 and patches my device.

Attached the log.txt

[ZodWallop]

Originally Posted by jkrzok

Is it as simple as following the instructions in the latest patch thread while ignoring version numbers?

I seem to remember you had to manually update the version number in some files. But it has been so long since I have done it, I don't remember where.

[xyclonei]

Originally Posted by ZodWallop

I seem to remember you had to manually update the version number in some files. But it has been so long since I have done it, I don't remember where.

What I did was to update the firmware versions mentioned in the kobopatch.yaml file from the previous patch version.

On a separate note, I see that whiletrying to create an FTP connection, it no longer accepts root as username and *blank* as password.

Does anyone know why this might be and what the updated credentials are?

EDIT: It seems the username and password are now admin and admin.

[ZodWallop]

Originally Posted by xyclonei

What I did was to update the firmware versions mentioned in the kobopatch.yaml file from the previous patch version.

Tried that and it did work. I haven't applied the patch .tgz to my Kobo yet.

It did have an issue with the 'Set KePub hyphenation' patch.

[Phil_C]

The "Remove line from bottom tab bar" patch has no effect on the Clara BW. I used the new offset of 866 found on github, which allows the patch file to be created with no errors. But when the patch is applied, the line remains on the Home screen.

Not a big deal. Just FYI.

[rcentros]

Originally Posted by DNSB

Changes:
Updated certs

Does this mean if I want my devices to connect to Kobo I'll have to update to this new firmware?

[pdurrant]

Originally Posted by Mik3

Прошу помочь найти образ на SD-карте kobo glo libros n613,
(Или оригинальную прошивку)

Google translate:

Please help me find the image on the kobo glo libros n613 SD card,
(Or original firmware)

[KomadoriRobin]

So. I just had the chance to test wether or not I'd get a database corruption simply by adding some books via Calibre. I'm sad to say I got a database corruption on my second connection. I ejected the device safely.

Actually, I've about had it right now. I'm so tired of this bug. I'll probably sell my Kobo Libra Colour and get a BOOX Go Color 7.

[DNSB]

Did you eject it from within calibre? if you are running Windows, did you use the eject option when right-clicking on the drive icon in Explorer or did you use the USB icon (Safely Remove Hardware and Eject Media) in the system tray? The eject from the system tray USB icon has multiple issues and, IMHO, does not constitute a safely eject.

[KomadoriRobin]

Originally Posted by DNSB

Did you eject it from within calibre? if you are running Windows, did you use the eject option when right-clicking on the drive icon in Explorer or did you use the USB icon (Safely Remove Hardware and Eject Media) in the system tray? The eject from the system tray USB icon has multiple issues and, IMHO, does not constitute a safely eject.

I ejected it from Calibre. I'm on a Mac, if that makes a difference.

[KomadoriRobin]

Okey. One more try. This is the steps I've done this time.

A full reset of my Kobo
Transfered my books again
Reinstalled Nickelmenu
Excluded my Kobo from the Spotlight search on my Mac. I've had this recurring issue where the Kobo didn't get ejected due to it being used. Turns out Spotlight indexed it, which prevented it from being ejected. Since excluding it, I've not had this issue.

As of right now, it seems to be working without issues. I've ejected and connected it a bunch of times without issues. I'll do some more testing and get back with an update.

EDIT: And there it is again. "CorruptError: database disk image is malformed".

[DNSB]

Are you ejecting the Kobo from within calibre (eject this device or using SmartEject) or by dragging the disk icon to the Trash?

Edit: Are you waiting for the Kobo to exit the Connected and charging screen before unplugging the USB cable?

[ghira]

Originally Posted by DNSB

Edit: Are you waiting for the Kobo to exit the Connected and charging screen before unplugging the USB cable?

Does that happen? I think I waited for that once, gave up, and have never given it serious thought since.