Firmware 3.18.0 discussion

[Nick_1964]

Originally Posted by IanD

Feeling a bit dim here ... can someone explain what full screen reading mode is please? I don't see any obvious setting in the GUI.

I have a Glo HD with stock 3.15.0, and no patches currently - just wondering if it's finally time to upgrade.

If you use: FullScreenReading=true in the config file, you get another option in the gui to enable or disable full screen, in that modus there is no footer and header visible anymore.. but if there is a full refresh now intruduced,that will be visible at every pageturn and your battery will be empty much sooner. (I think that is the consequence because I didn't updated yet.. I always wait to see if there are new bugs.. pardon me, I always wait to see which new bugs are introduced with a new firmware.. this maybe doesn't count as a bug because fullscreen isn't a documented feature..)

[GeoffR]

Can anyone who uses the FullScreenReading feature setting confirm whether the refresh bug affects devices other than Glo and Aura?

[jackie_w]

Originally Posted by GeoffR

Can anyone who uses the FullScreenReading feature setting confirm whether the refresh bug affects devices other than Glo and Aura?

I don't normally use FullScreenReading but I have updated my spare AuraHD with v3.18.0. I can confirm that enabling FullScreenReading makes the device refresh every page turn. Disabling FullScreenReading starts refreshing correctly again, as per the settings.

[dordale]

Originally Posted by Nick_1964

If you use: FullScreenReading=true in the config file, you get another option in the gui to enable or disable full screen, in that modus there is no footer and header visible anymore.. but if there is a full refresh now intruduced,that will be visible at every pageturn and your battery will be empty much sooner.

I'm sure refreshing every page turn will have an affect on battery usage, but I don't think the effect would be that significant. I change my refresh options quite frequently and quite a bit of the time I have it set to refresh every page--simply to have clearer text on the page. I personally don't notice a difference in how long the battery charge lasts.

On the other hand, I can understand how this would be annoying to people who what to use the FullScreenReading setting and really don't like seeing the refresh.

[Jarrett]

Things are feeling more responsive in 3.18 and there's less ghosting where it used to be common

[PeterT]

I will admit I fail to understand why people insist on enabling the buggy / unsupported / unfinished FullScreenReading mode.

[davidfor]

Here are the details posted to the beta list by Kobo.

Release is for: Kobo Touch, Kobo Glo, Kobo Aura HD, Kobo Aura, Kobo Aura H2O, Kobo Glo HD, Kobo Touch 2.0

Changes include:

• Sort Bookstore search results by price, rating, title, and date
• See how many books are in each subcategory
• After a sync that finds and applies an update, the regular sync is completed after update
• Ghosting improvements
• % read updates correctly on the sleep screen
• Previously, saved Bookstore searches would not appear if Wifi was disconnected
• Previously, 'Downloading' of book/article progress could get stuck in the header

And for the Kobo Desktop:

• New option in Reading Settings for Double page view.

I have bumped the firmware version supported by calibre. This will be in the next release.

[GeoffR]

Originally Posted by PeterT

I will admit I fail to understand why people insist on enabling the buggy / unsupported / unfinished FullScreenReading mode.

Because it is a great feature that makes reading KePubs bearable. I have used it for a long time and found it to work 100% perfectly for ePubs and (with the help of some patches to fix two bugs that only affect KePubs) almost perfectly for KePubs.

Hopefully there is a fix soon, but if not then I will have to decide either to downgrade to 3.17.3, or just stick to reading ePubs as there is another way to patch that gives a usable almost-full-screen mode for ePubs.

[JSWolf]

Originally Posted by PeterT

I will admit I fail to understand why people insist on enabling the buggy / unsupported / unfinished FullScreenReading mode.

What I don't get is why people say there are bugs in FullScreenreading mode and complain about them. It's an unfinished/unsupported/unofficial feature. So if it doesn't work, it doesn't work and it's not a bug that it doesn't work properly.

[PeterT]

Originally Posted by JSWolf

What I don't get is why people say there are bugs in FullScreenreading mode and complain about them. It's an unfinished/unsupported/unofficial feature. So if it doesn't work, it doesn't work and it's not a bug that it doesn't work properly.

Exactly

[Lynx-lynx]

I use full screen reading mode on my H2O without any probs whatsoever. I only read Calibre cleaned, side loaded, epubs.

[GeoffR]

Originally Posted by Lynx-lynx

I use full screen reading mode on my H2O without any probs whatsoever. I only read Calibre cleaned, side loaded, epubs.

Are you using this firmware version 3.18.0? If so: have you tried turning pages after putting the device to sleep and waking it again without leaving the book? And what do you have your page refresh rate set to?

[Lynx-lynx]

Geoff I'm still on 3.17.3, page refresh after 3 pages.

I don't use any other modifications apart from full screen reading.

[GeoffR]

Originally Posted by JSWolf

What I don't get is why people say there are bugs in FullScreenreading mode and complain about them. It's an unfinished/unsupported/unofficial feature. So if it doesn't work, it doesn't work and it's not a bug that it doesn't work properly.

Here are some other things that are not officially supported by Kobo:

* Using the built-in web browser
* Sideloading KePubs
* Using Calibre to sideload (and much more)
* Installing third-party software
* Patching the firmware

How many people here don't depend on at least one of those things to make their reading experience better?

[GeoffR]

Originally Posted by Lynx-lynx

Geoff I'm still on 3.17.3, page refresh after 3 pages.

I don't use any other modifications apart from full screen reading.

Okay sorry, I thought you meant you were using 3.18.0 and didn't see any problems, in which case I hoped to fighure out what you were doing differently.