Kobo Sage page buttons flaky

[Sirtel]

Originally Posted by NiLuJe

Duplicating the offending gesture works immediately (and the kernel is woken up by the missed input).

Not in Nickel. Touching the screen wakes the buttons up. I don't have KOReader installed on my Sage, so cannot test how it works there.

[BiliBug]

Originally Posted by Sirtel

Not in Nickel. Touching the screen wakes the buttons up. I don't have KOReader installed on my Sage, so cannot test how it works there.

My experience mimics that of NiLuJe in both Nickel and KOReader. I have screen tap gestures disabled in Nickel, necessitating a swipe to turn pages, which I never do. I only use the buttons. If there is no response, a second press turns the page.

As an aside, I’ve noticed far fewer occurrences of button unresponsiveness when using KOReader.

[Sirtel]

Originally Posted by BiliBug

My experience mimics that of NiLuJe in both Nickel and KOReader. I have screen tap gestures disabled in Nickel, necessitating a swipe to turn pages, which I never do. I only use the buttons. If there is no response, a second press turns the page.

As an aside, I’ve noticed far fewer occurrences of button unresponsiveness when using KOReader.

Funny, that. I can press ten times and the buttons still don't respond. When I touch the screen, they wake and start to respond.

If the second press worked, I wouldn't be as annoyed by this issue. But it doesn't in my case.

[Quoth]

Originally Posted by Sirtel

No, it's not that. When they don't respond, they don't respond until you touch the screen, no matter how many times or how hard you press the button.

I agree. But if I don't pause in my reading it seems OK. I've found best to close the cover if being distracted by someone/something.

[mbovenka]

Originally Posted by Sirtel

Funny, that. I can press ten times and the buttons still don't respond. When I touch the screen, they wake and start to respond.

Yep, that's how it works for me too. If the button press doesn't work the first time, follow-up presses won't work either until I either use the touch screen or put the device to sleep and wake it up again.

[NiLuJe]

That's an interesting difference in behavior (I mean, in a technical sense. In practice it sounds way worse xD). I'm curious whether the subsequent input reports actually make it to userland and it's just the QPA being confused, or if they never actually hit userland and/or are mangled in a different manner than what I'm seeing on my devices (both of which are early batches, FWIW).

[Sirtel]

Originally Posted by NiLuJe

...(both of which are early batches, FWIW).

My Sage is one of the earliest ones as well.

[mezzanine]

Originally Posted by Sirtel

No, it's not that. When they don't respond, they don't respond until you touch the screen, no matter how many times or how hard you press the button.

Mine will "wake up" after an unsuccessful button press; the following press always seems to work. Weird that different people are experiencing different symptoms with the same hardware likely also on identical firmware. I checked and my model is 778.

[HLS]

Originally Posted by geekraver

Hi all

I have a new Kobo Sage. I find about 20% of the time when I press the next page button the page doesn't turn. I'm wondering if this is a common issue or if the unit I bought is defective and I should get a replacement. Thoughts?

I just bought the Sage. I experienced page button issue and screen freeze but its not bad to where I would want to return the device. I am sure they will get an update to address it eventually

[HLS]

Originally Posted by Sirtel

Funny, that. I can press ten times and the buttons still don't respond. When I touch the screen, they wake and start to respond.

If the second press worked, I wouldn't be as annoyed by this issue. But it doesn't in my case.

I have the opposite. The screen will not respond but pushing the button will unlock it

[mezzanine]

Originally Posted by Sirtel

Funny, that. I can press ten times and the buttons still don't respond. When I touch the screen, they wake and start to respond.

If the second press worked, I wouldn't be as annoyed by this issue. But it doesn't in my case.

Observed this on my device this morning, which also jogged my memory for having previously experienced it. The missed page turn presses are more frequent, but having both buttons frozen is egregious.

They're also aware of this at Kobo according to a redditor who is particularly unhappy about this problem and who escalated it up the chain.

[Cactus Chef]

Originally Posted by mezzanine

My new theory is that most of the dead button presses are simply a result of not pressing hard/long enough. My tendency is to apply the minimum pressure to compress the button, but that doesn't work with these buttons. They don't pick up light presses that seemingly should be effective.

Nah. At least not in my experience. If that were the case, then every light press would fail. But what I observe is that either:

1. the first light press fails, and then the second light press works
2. a "heavy"/long press works, and then a light press works

So that, to me, lends more credence to the "wake-up" theory, because the light press seems to work fine once the device is awake.

I once spent some time with a stopwatch trying to figure out exactly how long it would take between turning the page and the device going into standby mode such that the next button press would fail. I could never get a fully consistent pattern--it seemed to be somewhere between 40 seconds and 1 minute, but even that wasn't totally consistent.

The only conclusion I came to was that the amount of time until standby mode was however long it took me to read a page.

[Quoth]

The buttons are "Tact" mechanical switches. It's purely the amount of depression, not how hard or soft. The length of time the switch is closed may sometimes be relevant.

So it has to be a SW issue.

[NiLuJe]

@Cactus Chef: It's ~5s of idle time, FWIW . (That implies no wifi/bt, no power source).

Which means the issue is *NOT* systematic (thankfully for us, possibly not thankfully for the poor sod at NTX who gets saddled with debugging this, if any...) .

[Quoth]

Originally Posted by NiLuJe

@Cactus Chef: It's ~5s of idle time, FWIW . (That implies no wifi/bt, no power source).

Which means the issue is *NOT* systematic (thankfully for us, possibly not thankfully for the poor sod at NTX who gets saddled with debugging this, if any...) .

[You mean not randomish?] Misread prior post

I look forward to better FW for buttons and Advanced Notebooks. Meanwhile I'm on 4.32.x and flip cover closed if I stop reading and it's fine!