Kobo Firmware 3.11.0

[JSWolf]

Originally Posted by davidfor

And I even asked Kobo about this in case it was a mistake.

Can you please ask Kobo why they don't allow us to use the font adjustments with sideloaded fonts? Thanks.

[icallaci]

Originally Posted by GeoffR

I'm having a slightly different but perhaps related issue with 3.11.0 on my Glo: I haven't noticed any ghosting from the sleep screen, but the text on the page it shows after waking from sleep is very light. If I turn the page forward and then back the text returns to normal darkness, even without a refresh.

I think you're right that it might be related. It's possible I'm seeing a combination of light text on the current screen combined with ghosting of the sleep screen. As I turn pages, the ghosting fades (or maybe the text gets darker), but it doesn't completely go away until I get a page refresh. I'll have to try a different book to see if this particular cover's light and dark areas exacerbate the ghosting issue.

[PeterT]

@JSWolf: We can ask but the chances of getting a reply from them is next to zero. There was a time we had a far more open / productive discussion with Kobo during beta's, but for some time now it's been a very quiet experience.

[camelriders]

May have been discussed here, not sure, but I have not read all of this thread so excuse me if this already been discussed.

Is there going to be a patch to tweak this firmware release?

I don't remember who, but someone released a patch for 3.8.0, which allowed us to tweak margins, etc.

Thanks.

[PeterT]

Originally Posted by camelriders

May have been discussed here, not sure, but I have not read all of this thread so excuse me if this already been discussed.

Is there going to be a patch to tweak this firmware release?

I don't remember who, but someone released a patch for 3.8.0, which allowed us to tweak margins, etc.

Thanks.

See Instructions for patching firmware 3.11.0

[camelriders]

Originally Posted by PeterT

See Instructions for patching firmware 3.11.0

Thank you.
Much appreciated!

[davidfor]

Originally Posted by JSWolf

Can you please ask Kobo why they don't allow us to use the font adjustments with sideloaded fonts? Thanks.

As PeterT said, discussion on the list is not as free as it used to be. But, I do remember this being asked. The problem is that they can't trust the sideloaded fonts. If there is a problem with the font and things go wrong, it affects the user experience and Kobo will be blamed.

Is it a cop-out? Probably. But, if they have tested a few fonts and found problems with them, then they can justify it.

[Jellby]

Originally Posted by JSWolf

Can you please ask Kobo why they don't allow us to use the font adjustments with sideloaded fonts? Thanks.

In my not very exhaustive experience with 3.5.0, the font adjustments with sideloaded fonts work in the preview window (with the patch), but not always in the book. Disabling the option is easier than fixing the bug

[MGlitch]

Originally Posted by Jellby

In my not very exhaustive experience with 3.5.0, the font adjustments with sideloaded fonts work in the preview window (with the patch), but not always in the book. Disabling the option is easier than fixing the bug

Seemed to work well in 3.8.0 with the patch, though I didn't test a ton of fonts.

[sbwtxj]

Under 3.11.0 , KBmenu is nor run, original version is for FW3.4.1.

[Anak]

Originally Posted by davidfor

The problem is that they can't trust the sideloaded fonts. If there is a problem with the font and things go wrong, it affects the user experience and Kobo will be blamed.

Is it a cop-out? Probably. But, if they have tested a few fonts and found problems with them, then they can justify it.

I agree Kobo might get blamed if 'tweaking' of sideloaded fonts don't work and therefore I understand that this feature is disabled by default for sideloaded fonts.
On the otherhand it is unbelievable (at least to me) that quite a few fonts which are supplied and embedded by Kobo don't work as intended. I.e. no italics, bold etc. Or other features that contain (easy to spot) bugs.

I work at an auditing firm. I've learned the hard way that if you are resonsible for a report or section of a report you have to check and recheck everything before you hand it over to someone else to review. Stupid errors, errors of ignorance (you should have asked someone who does know) or errors of ineptitude (here: when you made a mistake while you do know how not to make or how to avoid that mistake. If you had checked your own tasks thouroughly you should have spotted it and fixed it.)
These kind of errors which are easy to spot (if you had checked your tasks) would always result in a rant by a senior manager of several minutes regardless how futile the mistake you made really was. Next time you certainly tried hard not to make that (kind of) mistake(s) anymore. It you kept making them you certainly would loose your job ('maybe you should leave') or temp contracts were not renewed. I've seen many collegues leave this way.
The only 'mistakes' that are allowed are mistakes 'above your paygrade'. Or some senior manager changed his/her mind and wanted a different solution for a problem (but the solution you worked on should still be free of easy to spot errors).

Ergo: I except 'real life' errors or bugs that are not easy to spot. I.e. a spontanious reboot of a device. I can't except those easy to spot errors or bugs. I.e. cut off characters because the text doesn't fit within the available space. Or the font bug I mentioned above.

[Ashfall]

Originally Posted by icallaci

Is there a setting in 3.11.0 that will refresh the current page upon waking from sleep? When my Aura HD wakes, the ghost image of the front cover is so noticeable that it interferes with the text on the page. This didn't happen with 3.8.0. I'd prefer a refresh on waking rather than setting my page refresh to 1. Any way to do this?

I'm having this problem and have found that when I use the sleep switch, the screen does a full refresh both going to sleep and waking up. But when I use the sleep cover, it does a full refresh when going to sleep, but NO REFRESH when waking up, leading to ghosting. This behavior is new to 3.11 it seems. Maybe related to the new light delay feature.

For now my workaround is just to use the switch to sleep/wake again, causing a full refresh.

[adamslast]

I recently bought a kobo aura 6". It's fw is 3.1.0 and it does'nt update automaticly. Still on 3.1.0. How can i update it to new fw, 3.11.0 ? Or do you recommend do not update because of the changes? btw are there some tweaks for 3.1.0 especially for buttom margin? searched on forum but no result.
edit: I did it succesfully.

[JSWolf]

Originally Posted by davidfor

As PeterT said, discussion on the list is not as free as it used to be. But, I do remember this being asked. The problem is that they can't trust the sideloaded fonts. If there is a problem with the font and things go wrong, it affects the user experience and Kobo will be blamed.

Is it a cop-out? Probably. But, if they have tested a few fonts and found problems with them, then they can justify it.

I can see how that could be a problem. I found a nice looking free font (forget the name) and I tried to tweak it in a good font editing program and because of the poor way it was designed, some of the letter/characters did not come out properly. But can't Kobo put it in the beta section with a note that it's not guaranteed to work with all fonts?

[icallaci]

Originally Posted by Ashfall

I'm having this problem and have found that when I use the sleep switch, the screen does a full refresh both going to sleep and waking up. But when I use the sleep cover, it does a full refresh when going to sleep, but NO REFRESH when waking up, leading to ghosting. This behavior is new to 3.11 it seems. Maybe related to the new light delay feature.

For now my workaround is just to use the switch to sleep/wake again, causing a full refresh.

Aha! Thank you for that insight. I am indeed using the sleep cover, rather than the switch. It's just odd because ghosting has never really bothered me, but the ghosting I get now is terrible. Thank you.