I use Newsblur on an Android e-ink e-reader (Boyue T62+) that has physical scroll buttons. These buttons are highly preferable to dragging the screen, because of e-ink’s low refresh rate and responsiveness.
But the scrolling buttons don’t work in the Newsblur app on my device. Instead, they try to navigate the apps menus.
It’s hard to tell on a device not built for multimedia, but my impression is these aren’t volume buttons - I think they may be actual scroll buttons. No volume dialogs appear when I use them, Pandora ignores them, and Firefox uses them to scroll.
Hmm, if we can figure out what keys those buttons correspond to, it should be easy enough to support them. Can you run the following and let us know the codes for those two keys?
No, if I tap in the story body, then press the scroll keys, selects the hamburger menu button. Subsequent presses don’t actually do anything to that button (no presses, no further menu navigation).
Key codes: 92 is scroll up/left, 93 is down/right. Android docs say they map to KEYCODE_PAGE_UP / KEYCODE_PAGE_DOWN
Just a quick update on this: I have played with scrolling via pgup/pgdn keys, and while it “sort of” works, Android makes it somewhat tricky. Since those are hardware keys, using them flips the app into keyboard / non-touch mode, for which we don’t yet have great support. For instance, trying to do keyboard scrolling of the story makes it jump up and down in somewhat unpredictable increments depending on story content (images, text, etc).
I’ll see if I can crack a simple way to make the app keep scrolling via normal rules after using the buttons, but if I can’t do that in a simple way, this might have to wait until we address better keyboard support. (https://github.com/samuelclay/NewsBlur/issues/837)