@downeaster59:
Orientation being wonky in no framework mode doesn't suprise me, because there's some shenanigans involving the framework needed to figure out the Oasis's original rotation
.
As for the rest, it vaguely looks like either the orientation is badly detected, or the touch input device (which would send touch events in the "wrong" place, which could easily lead to the kind of behavior you're seeing).
What's strange is that we should specifically be doing things to avoid this kind of issue, because it happened for the original Oasis, because of a subtle difference between the 3G variant and the others
.
See
post #30 for instructions on how to enable debug mode.
My best guess is that this specific variant has a weird HW quirk, so if debug mode doesn't help figure things out, I'm afraid I'll need some of the same kind of info I asked @7hir7een for, and that requires USBNet/SSH, unfortunately
.
@JSWolf: That kind of remark in a post with a subforum moderator AND KOReader developper active took some kind of guts. I won't bother adressing this further, since it's just been done perfectly.
(To add insult to injury, @downeaster59 specifically asked if we should continue in this thread in his original answer, so, yeaaaaaah, your overzealousness is duly noted, but thanks, we're good
.).