Firmware 4.32.19501

[Deobulakenyo]

Originally Posted by ZodWallop

That's how Kobo Nickel has always looked.

I've attached an image from an eight year old review of the Mini and the Glo showing Kobo Nickel. Looks the same.

(It also shows that Facebook owes Neal Stephenson some money for 'Metaverse')

I wish i had taken a screenshot of the nickel font before i updated. It was definitely different on my device on previous fw.

[Skydog]

Originally Posted by jackie_w

... and if you want to also see a couple of FontForge screenshots for more detail, here is the original MR post on which the wiki entry was based.

As always, thank you, jackie_w, for your never-ending assistance and contributions. I am forever greatful to you and all those here on MR that share their wisdom and expertise.

[Cootey]

Originally Posted by davidfor

The only plugin that I know of for word counts is the Count Pages plugin. That is "ancient", but is also completely up to date…

Honestly? Based on the "discussions" about page and word count, a random number generator is probably as good a way as any. Otherwise, it's basically do it yourself, or the Count Pages plugin.

LOL I'm not sure RNG is the way forward for me.

By "ancient" I meant that the links I found discussing that plug-in were five years old or older. I'm glad to hear the project is up to date. I just assume anything that old usually isn't. Not sure why newer posts didn't come up in the search.

At any rate, I'll look forward to the Calibre update. I wasn't aware Kobo had extended that type of data, but then I've been away from this site for some time.


Sent from my iPad using Tapatalk Pro

[BookCat]

Originally Posted by Deobulakenyo

I wish i had taken a screenshot of the nickel font before i updated. It was definitely different on my device on previous fw.

Are you sure you weren't seeing the Publisher Font before? That looks a bit like Times New Roman.

[Deobulakenyo]

Originally Posted by BookCat

Are you sure you weren't seeing the Publisher Font before? That looks a bit like Times New Roman.

No. I even posted in our local fb group that I love the Kobo Nickel font. And that is why after udating, i set my currently reading book to nickel font, and i was surprised.

[MGlitch]

I’ve now looked on my two Formas, one on 4.31 the other on 4.32, my Sage and Libra 2, both on 4.32, and my Kobo H2O which somehow is running 4.30 I suppose I must have synced it for some reason after that update though I can’t imagine why as I’ve not used it for reading in quite some time now.

Kobo Nickel appears the same on each device in each firmware. Granted it’s only the last three firmware releases, but I’d have thought we’d have seen someone mentioning this amid 4.30s release, 4.31s release, or the rollbacks to 4.30.

It appears as a slab serif font, I can’t say for 100% sure how much the line spacing has changed as some of these devices are patched some aren’t, and for the ones that are I can’t for sure say if I used line 10 or 24 patches and if I did which one. Though this wouldn’t affect the font to the point it didn’t look like Times New Roman, nor do I apply any patches that would try to switch out Kobo Nickel (or any preinstalled font), and the non patched devices are the same as the patched ones for Kobo Nickels overall appearance.

I mean I suppose I could try rolling back the Kobo H2O to its stock firmware (pretty sure we already had Kobo Nickel back then) to really put this to the test. But I think I’ll hold off unless we get some more complaints that Kobo Nickel has changed.

[Deobulakenyo]

It seems my device is weird. even with nanoclock that keeps disappearing everytime i eject my device from calibre and needs multiple reboots for it to appear again.

[MGlitch]

Originally Posted by Deobulakenyo

It seems my device is weird. even with nanoclock that keeps disappearing everytime i eject my device from calibre and needs multiple reboots for it to appear again.

You may want to consider doing a manual factory reset, though I wouldn't do it over the Kobo Nickel issue.

I tried going back to 3.7.0 (the oldest firmware I think was ever available), and while I can import books opening them crashed the Aura h2o (not surprising as downgrading like I did is very not supported or suggested).

I did get it to open a book using 4.20.14601 from February 2020 and Kobo Nickel still showed up as the same slab serif typeface that I see on 4.30, 4.31, and 4.32.

[Deobulakenyo]

Originally Posted by MGlitch

You may want to consider doing a manual factory reset, though I wouldn't do it over the Kobo Nickel issue.

I tried going back to 3.7.0 (the oldest firmware I think was ever available), and while I can import books opening them crashed the Aura h2o (not surprising as downgrading like I did is very not supported or suggested).

I did get it to open a book using 4.20.14601 from February 2020 and Kobo Nickel still showed up as the same slab serif typeface that I see on 4.30, 4.31, and 4.32.

I did manual reset a few times already. The last one was when i updated to the latest fw. I just need help how to debug and generate log for nanoclock so i can send it the dev. I don't know how to.

[DNSB]

Originally Posted by Deobulakenyo

I did manual reset a few times already. The last one was when i updated to the latest fw. I just need help how to debug and generate log for nanoclock so i can send it the dev. I don't know how to.

Did you do a real factory reset (either from Settings => Device information => Developer options or using the manual factory reset (see: Manual reset your Kobo Sage, Kobo Libra 2, Kobo Forma or Kobo Libra H2O? The factory reset from the Device information menu is not a full factory reset.

As for the debug setting for nanoclock? Take a look at the nanoclock.ini file. change debug to true. Possiblly set the dump_log option to true as well.

;
; To debug, set to true
;; NOTE: Everything is sent to the syslog, to look specifically for nanoclock entries, run
;;       logread | grep '\(nanoclock\|nanoclock\.sh\)\[[[:digit:]]\+\]'
;; NOTE: Alternatively, you can find a NickelMenu config that will dump it in .adds/nanoclock/nanoclock.log
;;       over here: https://github.com/NiLuJe/NanoClock/blob/master/config/nm_nanoclock
;
debug=false

;
; If this is enabled, the current log will be dumped to .adds/nanoclock/nanoclock.log
; every time this config file is reloaded.
; This is a poor man's hack to get at the logs when you truly have no other way...
;
dump_log=false

You can add the following lines to your NickelMenu config file as well.

# Dump NanoClock's log to a file, because Dev mode log dumps are now encrypted :/.
menu_item : main : NanoClock Log : cmd_spawn : quiet : /usr/local/NanoClock/bin/nanoclock-logdump.sh
  chain_success : dbg_toast : Dumped NanoClock log in .adds/nanoclock/nanoclock.log
  chain_failure : dbg_toast : Failed to dump NanoClock log!

This information was lifted from NiLuJe's github page for nanoclock. Check the items in the config folder.

[DNSB]

Why do duplicate messages happen at random?

[Deobulakenyo]

Originally Posted by DNSB

Did you do a real factory reset (either from Settings => Device information => Developer options or using the manual factory reset (see: Manual reset your Kobo Sage, Kobo Libra 2, Kobo Forma or Kobo Libra H2O? The factory reset from the Device information menu is not a full factory reset.

As for the debug setting for nanoclock? Take a look at the nanoclock.ini file. change debug to true. Possiblly set the dump_log option to true as well.

;
; To debug, set to true
;; NOTE: Everything is sent to the syslog, to look specifically for nanoclock entries, run
;;       logread | grep '\(nanoclock\|nanoclock\.sh\)\[[[:digit:]]\+\]'
;; NOTE: Alternatively, you can find a NickelMenu config that will dump it in .adds/nanoclock/nanoclock.log
;;       over here: https://github.com/NiLuJe/NanoClock/blob/master/config/nm_nanoclock
;
debug=false

;
; If this is enabled, the current log will be dumped to .adds/nanoclock/nanoclock.log
; every time this config file is reloaded.
; This is a poor man's hack to get at the logs when you truly have no other way...
;
dump_log=false

You can add the following lines to your NickelMenu config file as well.

# Dump NanoClock's log to a file, because Dev mode log dumps are now encrypted :/.
menu_item : main : NanoClock Log : cmd_spawn : quiet : /usr/local/NanoClock/bin/nanoclock-logdump.sh
  chain_success : dbg_toast : Dumped NanoClock log in .adds/nanoclock/nanoclock.log
  chain_failure : dbg_toast : Failed to dump NanoClock log!

This information was lifted from NiLuJe's github page for nanoclock. Check the items in the config folder.

Thanks for the instruction on debugging. I followed the nanoclock log instruction before but all i get is the log that nanoclock started. But i will do it again and share the log.

For the nickelmenu, what does it do? Do i rnable it via nickelmenu and then disable it after?

As for the reset. I did manual reset by holding the volume up button while pressing the power button and waited until the screen flashed and reset the device to factory setting. Rolled back the fw as well after. Then i turned the device on and it updated via wifi to 4.30. I updated it again via wifi to 4.31. then i manually updated to 4.32 as the latest fw is not yet available in my location.

[DNSB]

Originally Posted by Deobulakenyo

Thanks for the instruction on debugging. I followed the nanoclock log instruction before but all i get is the log that nanoclock started. But i will do it again and share the log.

For the nickelmenu, what does it do? Do i enable it via nickelmenu and then disable it after?

Once you have enabled the debug setting, the NickelMenu entry is a simple way to dump the nanoclock log file to a human readable file in a known location. It runs, tries to dump the nanoclock entries and lets you know if the process succeeded or failed. It replaces having to get shell access to your Kobo and then running:

logread | grep '\(nanoclock\|nanoclock\.sh\)\[[[:digit:]]\+\]'

It also saves you from having to play with the dump-log setting.

Hmmm... bring up NickelMenu and tap a button or make a telnet connection, login and run the command. I know which I would prefer for ease of use.

Originally Posted by Deobulakenyo

As for the reset. I did manual reset by holding the volume up button while pressing the power button and waited until the screen flashed and reset the device to factory setting. Rolled back the fw as well after. Then i turned the device on and it updated via wifi to 4.30. I updated it again via wifi to 4.31. then i manually updated to 4.32 as the latest fw is not yet available in my location.

The FW version is the key to telling if it was a true factory reset. If you did the factory reset and the firmware was the same version as prior to the factory reset, it was the half-assed factory reset. If the firmware reverted to the factory version, it's the full factory reset.

[davidfor]

Originally Posted by DNSB

The FW version is the key to telling if it was a true factory reset. If you did the factory reset and the firmware was the same version as prior to the factory reset, it was the half-assed factory reset. If the firmware reverted to the factory version, it's the full factory reset.

Not quite. For some reason, the Libra 2 will update to 4.30 from any earlier firmware. Once the device is on 4.30, the next check will get 4.32. Someone at Kobo mentioned this, but didn't say why.

[Deobulakenyo]

Originally Posted by davidfor

Not quite. For some reason, the Libra 2 will update to 4.30 from any earlier firmware. Once the device is on 4.30, the next check will get 4.32. Someone at Kobo mentioned this, but didn't say why.

I can confirm this. After the manual reset. The libra 2 after connecting to wifi during the initial setup will update to 4.30. then syncing it again and/or checking for updates will download the available update. In my case it was 4.31 as the 4.32 is not yet rolled out in my area. Thus i had to manually update to 4.32