Firmware 3.13.1 (Japan only?)

[rashkae]

Most of the sluggishness I felt cleared up after a reboot. Twas very negligent of me not to think of that first. The Library menu still has a couple seconds delay that feels a little odd.

[JSWolf]

Originally Posted by rashkae

I find my H20 has become much more sluggish and slow to respond in some places since installing 3.13.1. Notable example is tapping the "Library" menu from the home page, (takes a few seconds for the menu to open, and even once the menu is open, takes a few seconds before it's ready for for one of the items to be tapped. If I tap the Books item impatiently while waiting, that tap gets transfered to the next page and opens whatever book happened to be in that spot.) It's impossible to come close to my previous high score in word scramble game. Even if I'm punching out words non stop in a grid, I can't even reach half my old score before the timer runs out. I hardly consider the 'game' of any import, but it's a good example to show how much the interface has slowed with this update.

Page turning remains unimpaired, unless turning the page to a larger image. But I'm not all sure if this is any slower than it was before.

Since my reading is not impacted, I haven't bothered to do a factory reset to return to previous firmware. I don't know what problem was solved with this firmware for Japanese users, but adding the in book reading stats certainly wasn't worth not waiting for a more widely deployed firmware update.

It could be your database might need to be compacted. Use the Kobo Utilities plugin to do this.

[GeoffR]

Originally Posted by rashkae

Most of the sluggishness I felt cleared up after a reboot. Twas very negligent of me not to think of that first. The Library menu still has a couple seconds delay that feels a little odd.

What I have noticed on my Glo is that when I tap "Library", the menu pops up first, and then the button inverts to indicate it has been tapped a little after that. The time for the menu to pop up seems to be just as fast as always, a fraction of a second, but the tap indication is delayed.

[rashkae]

Originally Posted by GeoffR

What I have noticed on my Glo is that when I tap "Library", the menu pops up first, and then the button inverts to indicate it has been tapped a little after that. The time for the menu to pop up seems to be just as fast as always, a fraction of a second, but the tap indication is delayed.

Yes, this is the same as I see with my "now working at correct speed" H20. The interesting point however, is that tapping on the "Books" button before the "Library" button inverts will have no visible effect. If you try tapping again, the second tap gets transfered to the next screen after the Kobo catches up.

The difference is probably less than 2 seconds. It was *much* more noticeable and annoying when everything on my Kobo was slow. Now I only see it because I'm looking for it, and poke at it like a sore tooth. By itself, not even worth mentioning.

I think it's interesting that if I power off and Boot the Kobo fresh, the Library Button is perfectly and immediately responsive. It's only I've been doing other things (reading, browsing books in the library, etc.) that the Library button gets that 1-2 sec response delay.

[arspr]

Hi guys, I think I've discovered a new bug (or at least I don't remember seeing it posted anywhere).

Look at the attached pictures. The problem arises when you long-press on a word in the right border of the screen in order to call dictionary and/or highlight it.

• The right marker is missing
• Dictionary is not called.

But this trouble doesn't appear if:

• The text is not justified. (As example, in the other picture I've posted, I've just enabled left justification in GUI).
• The word has a punctuation mark after it (a comma, a dot, whatever).

I've tested this issue in several kepubs, both sideloaded and original ones from Kobo bookstore.

Could anybody confirm it?

[robko]

Originally Posted by arspr

Hi guys, I think I've discovered a new bug (or at least I don't remember seeing it posted anywhere).

Could anybody confirm it?

Yep, you're right. I'll report it.

[dordale]

Originally Posted by arspr

Hi guys, I think I've discovered a new bug (or at least I don't remember seeing it posted anywhere).

Look at the attached pictures. The problem arises when you long-press on a word in the right border of the screen in order to call dictionary and/or highlight it.

• The right marker is missing
• Dictionary is not called.

But this trouble doesn't appear if:

• The text is not justified. (As example, in the other picture I've posted, I've just enabled left justification in GUI).
• The word has a punctuation mark after it (a comma, a dot, whatever).

I've tested this issue in several kepubs, both sideloaded and original ones from Kobo bookstore.

Could anybody confirm it?

I'm not seeing this on my Aura HD running 3.13.1.

I only have side loaded kePubs with full justification. Long pressing a word on the very right always seems to call up the dictionary correctly for me.

[pickyaxe]

arspr I've also felt this "missing dictionary definition" bug multiple times on H2O 3.13.1, and though I haven't made a note of the conditions the bug appears, I do remember only seeing it on highlighted words that are at the end of a sentence.

[JSWolf]

There is another dictionary bug that I've seen since 3.11.0. You cannot get the definition of a hyphenated word.

[arspr]

Originally Posted by dordale

I'm not seeing this on my Aura HD running 3.13.1.

I only have side loaded kePubs with full justification. Long pressing a word on the very right always seems to call up the dictionary correctly for me.

Could it be also related to margins/padding? Could you check in the epub code if your books have margins in boby, div (if exists) or p?

(I ask for this because I always kill them in my sideloaded books).

[dordale]

Originally Posted by arspr

Could it be also related to margins/padding? Could you check in the epub code if your books have margins in boby, div (if exists) or p?

(I ask for this because I always kill them in my sideloaded books).

I'm not very good at epub coding, so not sure if this will answer your question...checked out the code in one of my books in Calibre's ebook editor. It has references to a stylesheet in the < p > codes that refers to the following:
.calibre21 {
display: block;
text-align: justify;
text-indent: 1em;
margin: 0

Does that answer your question?

[arspr]

Originally Posted by dordale

I'm not very good at epub coding, so not sure if this will answer your question...checked out the code in one of my books in Calibre's ebook editor. It has references to a stylesheet in the < p > codes that refers to the following:
.calibre21 {
display: block;
text-align: justify;
text-indent: 1em;
margin: 0

Does that answer your question?

Yes and no.

That means that that paragraph has no margins. Now please check if the enclosing <body> has margins or not. There's always a <body> which contains the whole chapter/file text. (The paragraph margins are the sum of both).

Also check for a possible @page setting in either of the linked CSS style files. Calibre (as you seem to have a converted eBook) usually inserts one called Pagestyle.css (IIRC) with that setting specifically, (another possible margin to add).

And if there were <div>s enclosing your <p>s, (there usually aren't, but there could be even several nested levels of them), you also have to check their possible margins.

OTOH nearly sure dumb questions. Have you tested several words? Have you tested several books? Are you using kepubs (rather than epubs, I haven't tested with "common" epubs but just with Kobo flavor, and therefore renderer, of them).

[dordale]

arspr--I'm at work right now, so will look at the details of my ePub settings when I get a chance--hopefully this evening.

To answer your other questions--
Yes I have tested several words in the book
I have tested four or five different books
All my books are kePubs on my Kobo Aura HD (converted on the fly from ePubs during transfer from Calibre through the Kobo Touch Extended Driver)
I've used Calibre conversion on all my books (even those starting out as ePubs) to remove fonts, etc.

[dordale]

Originally Posted by arspr

Yes and no.

That means that that paragraph has no margins. Now please check if the enclosing <body> has margins or not. There's always a <body> which contains the whole chapter/file text. (The paragraph margins are the sum of both).

Also check for a possible @page setting in either of the linked CSS style files. Calibre (as you seem to have a converted eBook) usually inserts one called Pagestyle.css (IIRC) with that setting specifically, (another possible margin to add).

And if there were <div>s enclosing your <p>s, (there usually aren't, but there could be even several nested levels of them), you also have to check their possible margins.

Okay--checked my ePub file--all margins in the file seem to be set to zero.

The body tag references the following code in the stylesheet:

.calibre {
display: block;
font-size: 1em;
line-height: 1;
padding-left: 0;
padding-right: 0;
text-align: justify;
margin: 0
}

There is a seperate page_styles.css. The only code contained in this stylesheet is:

@page {
margin-bottom: 0;
margin-top: 0
}

No div tags in this book.

Hope this helps!

[arspr]

Originally Posted by dordale

Okay--checked my ePub file--all margins in the file seem to be set to zero.

[...]

No div tags in this book.

Hope this helps!

Yes, unless there's something more "hidden", (pagetemplate.xptg, or inline styles), that means that you don't have margins so your books are like mine but you cannot replicate the issue.

I would like to test one of your books. Could you post one of them in both original epub and kepub versions extracted from your HD, (with a picture of a place showing your trouble-free word selection)? If you don't have a free book, (example: a Gutenberg project one), then PM me, I promise to delete it when finished. (Remember you cannot post copyrighted material here even for testing purposes).

The strangest thing would be an H2O issue but not an HD one with the same FW version.