Firmware 3.19.5613 discussion - Page 8

DNSB · 12-09-2015, 05:57 PM

Quote:

Originally Posted by GeoffR

There are no trace logs. The Glo doesn't crash though, so I wouldn't expect any.

The Kobo Tsukushi Mincho is an extremely large font, 15MB, so it could be that lack of memory is an issue on older devices but not newer ones. I also have a lot of other fonts sideloaded, no problems with any of them, but none are anywhere near as large as Kobo Tsukushi Mincho.

I've used Microsoft's Arial Unicode font (~22MB) on my Kobos from the Glo onward and haven't noticed any issues connected with the size of the font file.

Lynx-lynx · 12-09-2015, 06:12 PM

Quote:

Originally Posted by Ripplinger

I'm also very privacy conscious, but I didn't mind signing up for an account when I got my first Kobo, it was a very very minor annoyance. But there's no personal details, no billing info, absolutely nothing but the email address, so I don't understand why some are so against it, especially when Kindles require linking to Amazon accounts.

Since you also buy from Kobo and I can understand you not wanting the hassle of double books, but why not just create a 2nd Kobo account for the reader only with a different email address, one you never make a purchase from. That would solve the problem of the double book downloads and end the hassle of trying to keep the reader unregistered.

Like you, I only purchase my books through my PC and sideload all books. Nothing is so urgent I need to download it to my reader right then and there.

Quote:

Originally Posted by delph

That's an excellent idea, and I don't know why I didn't think of it myself. I have my own domain and generate standalone email addresses for other reasons (also not privacy related). There's no reason not to do so for this as well. Thanks for the suggestion!

Yes, that's exactly what I've been doing for several years now. My device email account is not used for purchasing kobo ebooks. I call it my 'dummy account'.

I only ever side load Calibre cleaned ebooks and I've not encountered any problems at all. (And I don't use the device wifi, I don't turn it on so to speak.)

Also, I manually change the firmware version updates, so that's not an issue either.

For some folk a dummy account is not the solution because they want to use kepub formatted ebooks because, for example, they prefer the format or they want to collect stats etc.

Lynx-lynx · 12-09-2015, 06:16 PM

Quote:

Originally Posted by the.Mtn.Man

My Kobo Aura is filled with over 600 free and public domain books, and the only time I use the sync feature is when I want to download a new firmware.

If you don't want to sync to download an updated firmware then you can manually update. (That's what I do.)

I don't have a need to sync my device at all because on the odd occasion that I get a kepub formatted ebook, rather than an epub formatted ebook, obok converts it for me as part of the Calibre cleanup and then I sideload it.

davidfor · 12-09-2015, 06:48 PM

Quote:

Originally Posted by GeoffR

There are no trace logs. The Glo doesn't crash though, so I wouldn't expect any.

The trace logs can be produced when a component crashes but the rest of the device keeps going.

Quote:

The Kobo Tsukushi Mincho is an extremely large font, 15MB, so it could be that lack of memory is an issue on older devices but not newer ones. I also have a lot of other fonts sideloaded, no problems with any of them, but none are anywhere near as large as Kobo Tsukushi Mincho.

Memory is a good theory. The Touch and Glo have 256MB vs the 512MB in the later devices.

davidfor · 12-09-2015, 07:02 PM

Quote:

Originally Posted by GeoffR

No, at least not normally. But there are some cases where a setting scale changes, and then the old settings get translated to the new scale during the upgrade.

For example, in firmware 3.12.1 there were 40 font size settings ranging from 12 to 90 and including size 25. Then in 3.13.1 the scale was increased to 48 sizes ranging from 12 to 150 for the HD devices, but although the spacing of the new scale as more uniform overall, it didn't include a size 25. So if you had a book set to font size 25 I think it would have been changed during upgrade, to 24 or 26.

With this firmware version, if you had any books set to use Gothic or Ryumin fonts then their settings will be changed to use the replacement Kobo UD Kakugo and Kobo Tsukushi Mincho fonts instead.

No, the font settings aren't changed during the upgrade. If it was set to 25, 25 will continue to be used until you make a change. You could always go in and change the settings in the config file or database and choose other options [insert ad for Kobo Utilities plugin] and they would be used.

I'm not so sure about the actual fonts. Again, they don't change the settings, but I don't know what happens when you open a book. It could change to whatever is the default, or it could use the matching replacement font. But, whichever it does, happens when you open the book.

GeoffR · 12-09-2015, 07:32 PM

Quote:

Originally Posted by davidfor

I'm not so sure about the actual fonts. Again, they don't change the settings, but I don't know what happens when you open a book. It could change to whatever is the default, or it could use the matching replacement font. But, whichever it does, happens when you open the book.

The current firmware has a funcion

Code:

Migration125_ReplaceMorisawaFontsSettings::migrate(Device const&, QSqlDatabase&)

which executes this SQL

Code:

UPDATE content_settings SET ReadingFontFamily='%1' WHERE ReadingFontFamily='%2';

There is another one that executes

Code:

UPDATE content_settings SET ReadingFontFamily='OpenDyslexic' WHERE ReadingFontFamily='Dyslexie';

from back when the Dyslexie font was removed. I think these must be done sometime during the upgrade process.

The font sizes though might be done when the book is next opened, as you say, and I guess there is nothing to prevent it continuing to use a size that is no longer available on the font size slider.

Fbone · 12-09-2015, 07:45 PM

Thank you. I am still using 3.15 but have adjusted the boldness of several fonts and didn't want to redo them so I've avoided updating.

GeoffR · 12-09-2015, 08:03 PM

Quote:

Originally Posted by Fbone

Thank you. I am still using 3.15 but have adjusted the boldness of several fonts and didn't want to redo them so I've avoided updating.

I don't think the weight/sharpness settings are saved seperately for each book, there is just one setting for each font stored as plain text in the [Reading] section of the ".kobo/Kobo/Kobo eReader.conf" file, so if you make a backup of that file it would be easy enough to restore them after a factory reset, or if you get a new device.

JSWolf · 12-09-2015, 08:05 PM

Quote:

Originally Posted by Terisa de morgan

@delph, I purchase a lot of books at Kobo... but never at the email address I've registered my Kobo. I'm not interested in synchronizing the books.

That is a good idea to create a second account that doesn't have any eBooks with it.

tayseidel · 12-09-2015, 08:40 PM

JSWolf, would you say that the page turns in epubs are as fast as with kepubs in the new 3.19 firmware?

davidfor · 12-09-2015, 09:03 PM

Quote:

Originally Posted by GeoffR

The current firmware has a funcion

Code:

Migration125_ReplaceMorisawaFontsSettings::migrate(Device const&, QSqlDatabase&)

which executes this SQL

Code:

UPDATE content_settings SET ReadingFontFamily='%1' WHERE ReadingFontFamily='%2';

There is another one that executes

Code:

UPDATE content_settings SET ReadingFontFamily='OpenDyslexic' WHERE ReadingFontFamily='Dyslexie';

from back when the Dyslexie font was removed. I think these must be done sometime during the upgrade process.

I stand corrected. The "Migration125_..." methods should be run when migrating the database to DBversion 125. I'm sure I saw a reference to Gothic or Ryumin in one of my databases after it reached 125. But, that might be an issue with the beta firmware versions if the above code wasn't in the firmware that did the rest of the migration.

Quote:

The font sizes though might be done when the book is next opened, as you say, and I guess there is nothing to prevent it continuing to use a size that is no longer available on the font size slider.

That's correct. The sizes are just points, so if the font and renderer can handle it, it works. I took advantage of this with the Glo at some point as the best size for me was one of the missing numbers.

LuQQ · 12-09-2015, 11:18 PM

Quote:

Originally Posted by davidfor

Gothic and Ryumin fonts replace with "Kobo Tsukushi Mincho" and "Kobo UD Kakugo". As far as I can tell, they are identical. The change was something to do with changing their font supplier.[*]Devices will sleep when plugged in. There were some other sleep timing

Do you konw these two fonts's font-family ？

davidfor · 12-10-2015, 01:12 AM

Quote:

Originally Posted by LuQQ

Do you konw these two fonts's font-family ？

For "Kobo Tsukushi Mincho" it is "KBJ-TsukuMin Pr6N RB" and for "Kobo UD Kakugo" it is "KBJ-UDKakugo Pr6N M". Or at least that is what is written to the config file and database when these are selected.

GERGE · 12-10-2015, 02:34 AM

Quote:

Originally Posted by GeoffR

There are no trace logs. The Glo doesn't crash though, so I wouldn't expect any.

The Kobo Tsukushi Mincho is an extremely large font, 15MB, so it could be that lack of memory is an issue on older devices but not newer ones. I also have a lot of other fonts sideloaded, no problems with any of them, but none are anywhere near as large as Kobo Tsukushi Mincho.

There is a simple way to test it. I just installed Kaiti. It only comes in regular and bold but has a total size of 70MB.

It completely broke Kobo Glo. I could open the books but no glyphs showed up after selecting the type, only an empty page. Nothing in the logs too.

Nick_1964 · 12-10-2015, 05:42 AM

I think the font must be removed or the update must cancel, on my wife's normal Glo the Kobo Tsukushi Mincho destroys the whole lay out, books are stopping,the device hangs so I needed the reset button.
Now "here" on this forum we know how to revert (I put her back to 3.17.3) but how many customers in the "open field" are there that can't do this.
I think it is the best that Kobo stops the automatic update progress until this stupid font is removed or a lot of customers are going back to the shop with it.
On My Kobo HD there are no real problems with it.

12-10-2015, 05:42 AM	#120
Nick_1964 Bookworm Posts: 975 Karma: 768585 Join Date: Aug 2010 Location: Netherlands Device: Sony prs-650, Kobo Glo HD (2x), Kobo Glo	I think the font must be removed or the update must cancel, on my wife's normal Glo the Kobo Tsukushi Mincho destroys the whole lay out, books are stopping,the device hangs so I needed the reset button. Now "here" on this forum we know how to revert (I put her back to 3.17.3) but how many customers in the "open field" are there that can't do this. I think it is the best that Kobo stops the automatic update progress until this stupid font is removed or a lot of customers are going back to the shop with it. On My Kobo HD there are no real problems with it. Last edited by Nick_1964; 12-10-2015 at 05:45 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Firmware 3.18.0 discussion	GeoffR	Kobo Reader	335	10-14-2016 01:56 PM
Firmware 3.17.3 Discussion	PeterT	Kobo Reader	258	09-16-2015 09:13 AM
Firmware 3.16.0 Discussion	davidfor	Kobo Reader	240	08-14-2015 12:52 PM
Firmware 3.16.10 Discussion	murg	Kobo Reader	35	08-12-2015 02:08 PM
New Firmware (1.4) Discussion	Stinger	Kobo Reader	103	07-22-2010 12:02 PM

12-09-2015, 07:45 PM	#112
Fbone Is that a sandwich? Posts: 8,318 Karma: 103930826 Join Date: Jun 2010 Device: Nook Glowlight Plus	Thank you. I am still using 3.15 but have adjusted the boldness of several fonts and didn't want to redo them so I've avoided updating.

12-09-2015, 08:40 PM	#115
tayseidel Zealot Posts: 146 Karma: 189664 Join Date: Feb 2009 Device: Glo HD, Aura H20, PRS-T1	JSWolf, would you say that the page turns in epubs are as fast as with kepubs in the new 3.19 firmware?