Kobo Firmware 4.12.12111

[Uschiekid]

I have taken photos of it, and when you look at the photo which the document is not zoomed, you can see the 6 lines of text that are missing when zoomed, despite the box showing the top left corner is what is being displayed.

[NiLuJe]

@FrustratedReader:

If you care more about highlighting than the quick turn gimmick (I do ), it can be disabled with a hidden setting: disableQuickTurn=true in the Reading section.

WiFi being finicky, yeah, but to be fair, it seems to behave a whole lot better than before on 4.12.

The IR grid not waking up is indeed a very old bug on the H2O . I can concur that it's simply the IR grid not waking up, and not the device freezing, because I had to implement a workaround in KOReader to *always* manually wake the IR grid up on resume.
That said, I haven't encountered it in quite a while in Nickel, on my end. But the potential for it to happen is definitely there .

[frostschutz]

Originally Posted by NiLuJe

because I had to implement a workaround in KOReader to *always* manually wake the IR grid up on resume.

Do you have any details for this workaround?

Touch stop working is something I encounter from time to time as well. Sometimes sending to sleep fixes it, sometimes it does not and then I'm forced to power off and reboot. Thankfully it only happens rarely.

[NiLuJe]

@frostschutz: here it is .

i.e.,

echo "a" > /sys/devices/virtual/input/input1/neocmd

I don't rightly recall where I got that from, but I'd say strace'ing nickel (or strings)?

[NiLuJe]

Fun fact: when Nickel fails to sideload a file, you don't need to channel your inner Hercules Poirot to figure out which ones didn't make the cut, nickel will helpfully log that for you!

logread | grep "This epub file is bad"

will do the trick.

So, yeah, you need shell access. .

This may have been there for a while, but I've only ever setup a grand total of *two* Kobo devices, so .

(Yes, I'm a crazy person who stores kepub files in his Calibre library. There's a reason. It even makes some kind of sense! ).

[compurandom]

Originally Posted by FrustratedReader

Bugs in this Firmware on Kobo H2O original:
3) Old bug still not fixed: Turn off & on too quickly (flip sleep cover or press button twice), which can happen by accident and "Touch" is disabled. Sleep for a longer period usually fixes it. Sometimes needs a reset. I'm thinking it's not crashed or frozen as sleep cover/ active page appears and usually closing cover for count of 15 (or button) fixes it.

I tried to report this bug and they told me it was a hardware bug and I needed to return my kobo. It's clearly a firmware bug, but I don't know if the developers know if tech support won't accept it as a bug report.

[Quoth]

I've designed both SW & HW of similar systems. It's the software (firmware).
Also found in this FW:
A line ending in a carriage return, but not new paragraph is impossible to highlight/annotate. You have to start previous paragraph and end on next. Either the Bobbsey Twins at the Seashore or in the Country (from www.gutenberg.org)

A Touch being interpreted as two touchs, so opening "books" using tile instead of menu opens a title, yet the double tap to enlarge an image is nearly impossible. Solution: Don't use the stupid space wasting tile, but Menu. It ought to be possible to use ALL the Home as an MRU list, like older home screen could be configured.

Impossible to highlight/annotate top line in "no header" mode. See earlier footer bug.

Still annoying: Automatic Dialog to reset partially read books not recently accessed as "unread". Why can't that be a user option? Arrogant foisting of a feature as is hardcoding Google as Search, Wikipedia as Reference and Facebook as Social media as well as enforce waste of space of two last items on homescreen not on the H2O when I bought it.

Really you'd think they don't have proper QA/Testing or GUI designers and it was a fresh team of new graduates rather than software that they have worked on for years.
Problem is likely that Marketing is setting the features and priority. They need to test with people that seriously read, that have 1000 books, that do annotation of proofs / proofreading and research. You know people that understand touch GUIs, document management, reading etc.
Amazon is nearly as bad.
Also stop imitating all the worst GUI decisions of Google & MS.

[jackie_w]

Originally Posted by FrustratedReader

A Touch being interpreted as two touchs, so opening "books" using tile instead of menu opens a title

Am I completely misunderstanding your point? I have quite a few Kobos. Most are heavily patched but one currently isn't. On all of them tapping the big 'My Books' tile on the Home page always opens the My Books list. It never opens a book file.

the double tap to enlarge an image is nearly impossible.

It always works for me. I think it's a kepub-only feature.

Impossible to highlight/annotate top line in "no header" mode.

I rarely use highlight or annotate myself but I just tried it in both an epub and a kepub. Seems to work OK in both. Long-press first word, then drag. In general, highlighting seems a bit easier in kepub.

Really you'd think they don't have proper QA/Testing or GUI designers and it was a fresh team of new graduates rather than software that they have worked on for years.

Which company's GUI satisfies all of its customers all of the time?

[ZodWallop]

Originally Posted by Dshine

Does any one experience battery drainage with this update on kobo aura (1st edition)? Mine only last for 3 days since 100% charged.

Okay, I used my Aura over the weekend. Last charge was on Thursday and it was at 100%.

Because of the holidays, I haven't read heavily over the weekend. Fifteen to forty-five minutes a day (including today), front light set at 17%, WiFi off. My Aura is at 93%. So no, no rapid battery drain on my first edition Aura.

Originally Posted by FrustratedReader

Impossible to highlight/annotate top line in "no header" mode

I have only kepubs, both bought and sideloaded, on my Aura H202 and I have no difficulty highlighting on the top line (and bottom line) in Kobo's own "no header" mode

[Quoth]

Originally Posted by jackie_w

1) On all of them tapping the big 'My Books' tile on the Home page always opens the My Books list. It never opens a book file.


2) It always works for me. I think it's a kepub-only feature.


3) I rarely use highlight or annotate myself but I just tried it in both an epub and a kepub. Seems to work OK in both. Long-press first word, then drag. In general, highlighting seems a bit easier in kepub.

1) was fine till this update. A tap is now easily read as two taps, hence a book opening, or item selecting / unselecting (or vice versa).
2) I have no kepubs. It sometimes works. Previously a sort of double touch enlarged the image, though like the double tap it often needed several attempts.
3) I proof annotate books for practice. I also proof my own writing. The last FW was best for annotation, previously sometimes if the highlight ended at a paragraph end, then the annotation wasn't saved. Now it's fine except on top line if header off, bottom line on footer off (so I'll keep those on!). Previously Full page didn't work properly anyway, no doubt why it wasn't on GUI. The end of line bug is something you'd not normally see as normally ebooks use paragraphs. I shall repair the source book as obviously it's a Gutenberg proof error (pressing say shift return or control return instead of return for a newline/paragraph in editing).
Just because some people don't use a feature, doesn't mean it's not important.
I've written text editors and also software for over 30 years. These bugs are typical lack of testing of boundary conditions. First and last lines outside previous area due to new header/footer options. The "newline" without a paragraph tag would be rare in an eBook. At least I suspect that's what's wrong with the Bobbsey twins.
I use four targets for ePubs that are not Kobo, so I have no interest in kepubs.

[John F]

I can highlight the top line with no header.

I have troubles highlighting the bottom line with no footer; I get rapid page turns when I try to tap and hold on a word in the bottom line.

I am using patches.

[NiLuJe]

@John F: See #167 for a workaround to the footer issue (I say workaround, because, of course, it's a trade-off: it kills the QuickTurn feature entirely. Which I have no use for, so it suits my needs perfectly, but YMMV ).

Which means I now have *zero* issue highlighting stuff on the first/last lines, despite *very* minimal margins (11 or 14px, depending on the device).

@FrustratedReader: Couldn't detect anything to note either with the touch input on my H2O, post-update. It's not great, but then it never really was.

[John F]

Originally Posted by NiLuJe

@John F: See #167 for a workaround to the footer issue (I say workaround, because, of course, it's a trade-off: it kills the QuickTurn feature entirely. Which I have no use for, so it suits my needs perfectly, but YMMV ).

...

Thank you NiLuJe! I don't plan on using quickturn, and would prefer reliable dictionary lookup.

[davidfor]

Originally Posted by FrustratedReader

A Touch being interpreted as two touchs, so opening "books" using tile instead of menu opens a title, yet the double tap to enlarge an image is nearly impossible. Solution: Don't use the stupid space wasting tile, but Menu. It ought to be possible to use ALL the Home as an MRU list, like older home screen could be configured.

Originally Posted by FrustratedReader

1) was fine till this update. A tap is now easily read as two taps, hence a book opening, or item selecting / unselecting (or vice versa).

I can't work out what you are doing here. Like @jackie_w, I thought you meant tapping the "My Books" tile on the home screen resulted in a book opening. But, as you mention using a menu instead, I'm not sure what you mean.

And I have opened a book accidentally after tapping the "My Book" tile. But, it has always been the result of a second accidental tap.

2) I have no kepubs. It sometimes works. Previously a sort of double touch enlarged the image, though like the double tap it often needed several attempts.

Well, if you work out how you did it, please tell us. For the rest of us, the double-tap zoom on an image, only works for kepubs. And CBR/CBZ or PDF. But, they are different.