Odd behavior from Libra 2

[foosion]

Two strange things from my Libra 2

1) Occasionally when I push the page turn button nothing will happen. I'll wait a bit, then push it again and it will skip forward two pages. I'm waiting much longer than it should take to go to the next page.

2) While the device was charging from a normal USB-C charger the screen went blank and three dots appeared, blinking in order. I unplugged and it went back to the usual sleeping screen. Wifi is off. This only happened once.

???

[foosion]

1) It did it again. I pressed the page turn button and nothing happened. I waited 30 seconds to make sure I wasn't double clicking, then clicked again and the reader skipped forward two pages. This was at a chapter boundary.

Anyone else or any idea why this is happening?

[PeterT]

Over the years I've experienced that or similar missed button presses many times in a range of devices.

I've found the Libra Colour has been far better in this regard though

Sent from my Pixel 7a using Tapatalk

[Sirtel]

I don't have this problem with my Libra 2, but it happens occasionally on my Sage.

[foosion]

Originally Posted by PeterT

Over the years I've experienced that or similar missed button presses many times in a range of devices.

I can understand a device not recognizing a button press; it's turning two pages forward on the next button press that seems odd to me.

[Sirtel]

Originally Posted by foosion

I can understand a device not recognizing a button press; it's turning two pages forward on the next button press that seems odd to me.

Seems to be the usual lazy quality control from Kobo. It happens with my Sage, but has never happened with any Kindle I've had (tbh, it also never happened with either my Libra 1 or Libra 2).

[foosion]

Sounds as if it's not unheard of and that there's nothing to do about it.

[Quoth]

Originally Posted by foosion

I can understand a device not recognizing a button press; it's turning two pages forward on the next button press that seems odd to me.

No, that happens on Sage, and less often on the Libra2 and not at all on the original Libra. Something to do with over-aggressive "sleep".
Unlike all non-eink systems, an eink ereader achieves long battery run time by sleeping as the page is bistable. The page will display practically forever if disconnected or battery suddenly unplugged.

Maybe a future firmware will fix it. I kept my old Libra for audio narration as it has 100% reliable page turning. My Libra 2 and Sage do not have reliable page turns.

[Quoth]

Originally Posted by Sirtel

Seems to be the usual lazy quality control from Kobo. It happens with my Sage, but has never happened with any Kindle I've had (tbh, it also never happened with either my Libra 1 or Libra 2).

Most of the Kindles with page turn are very old. Only the Oasis 3 is current?

I did have an Oasis 2 for a while, but forget if the page turn was reliable. The Kindles have loads of other issues.

[Aleron Ives]

Originally Posted by foosion

This was at a chapter boundary.

How long are the chapters? This happens to me when a book is poorly formatted into giant sections that are hundreds of screens long. If the next "chapter" is huge, then turning the page takes a very long time, and it may appear as if the page turn was not registered, but in fact the Libra is just struggling to load the next massive XHTML file.

In this case, the solution is to edit the book to break it into smaller files.

[Sirtel]

Originally Posted by Quoth

Most of the Kindles with page turn are very old. Only the Oasis 3 is current?

I did have an Oasis 2 for a while, but forget if the page turn was reliable. The Kindles have loads of other issues.

The Oasis 3 has been discontinued. It was released in 2019. Before that, I had the Oasis 2 (2017), Oasis 1 (2016), Voyage (2014) and older nontouch Kindles. No button issues with any of them that I can recall.

Kindles have their own issues, true, and I no longer use them (because I like the Kobo UI better), but at least when I still used them (more than 3 years ago now), they tended to have fewer bugs than Kobos. That may have changed by now, no idea. My Libra 1 (2019) was also relatively bug-free, but the Sage and the Libra 2 certainly are not. I do love my Kobos, but Kobo quality control sure has very little to recommend it.

[foosion]

Originally Posted by Aleron Ives

How long are the chapters? This happens to me when a book is poorly formatted into giant sections that are hundreds of screens long. If the next "chapter" is huge, then turning the page takes a very long time, and it may appear as if the page turn was not registered, but in fact the Libra is just struggling to load the next massive XHTML file.

In this case, the solution is to edit the book to break it into smaller files.

I was wondering about that. I'd have thought 30 seconds would be enough time, but the next time it happens I'll wait longer and check the size of the following chapter.

I don't remember the size for this time. The largest file so far is about 30kb.

[John F]

Not registering a tap and then advancing two pages used to happen to me on my previous Kobos. I haven't noticed it on my Clara 2E.

[DNSB]

The explanation I got for this is that especially on the Sage with it's very aggressive power management, after a certain delay, the ereader goes to a deep sleep mode. The first key press wakes the ereader up but it will take a while before the ereader is awake enough to process the key press. At that point, I had usually lost patience and hit the key again. So now the second key press is queued up and gets processed as well.

[Sirtel]

Originally Posted by DNSB

The explanation I got for this is that especially on the Sage with it's very aggressive power management, after a certain delay, the ereader goes to a deep sleep mode. The first key press wakes the ereader up but it will take a while before the ereader is awake enough to process the key press. At that point, I had usually lost patience and hit the key again. So now the second key press is queued up and gets processed as well.

While this might be true, it doesn't explain why some devices behave this way and others don't - for example, my Libra 2 doesn't do it, but the OP's Libra does. I'm no speed reader, so differences in reading speed are probably not the cause in this case.

AFAIK basically all Sages do it, but with other Kobo models it doesn't seem to be so absolute.