KOA2 KOReader on KOA2: Possible yet?

[NiLuJe]

Huh, if anything, I'd have expected the 3G variants to be the more finicky ones... .

@downeaster59: I'll merge a few minor things to workaround a few of the fonts issues later today, I doubt it'll solve anything, but it can't hurt. I'll give you a heads up when it's up, and we'll try running in debug mode, to see if anything else pops up in the logs that way...

EDIT: Out in 1755 .

[downeaster59]

Originally Posted by NiLuJe

Huh, if anything, I'd have expected the 3G variants to be the more finicky ones... .

@downeaster59: I'll merge a few minor things to workaround a few of the fonts issues later today, I doubt it'll solve anything, but it can't hurt. I'll give you a heads up when it's up, and we'll try running in debug mode, to see if anything else pops up in the logs that way...

EDIT: Out in 1755 .

Well, my device is surely finicky!

When I start KOReader in "no framework" mode, it seems to run as expected - with the exception that, when I open a book, it first appears upside down. I need to tilt my KOA2 just a bit for the book to flip to the correct orientation.

When I start KOReader in "normal" mode", I come to the file browser. No matter what I select - or try to select - it takes me one level "up" in the file system. When it can't go any further "up", it freezes. I can pull up the top or bottom menus, but tapping anything has no effect. The only way out is to reboot.

How would I run this in debug mode?

If I'm the only one experiencing these problems, this might not be worth your while, as I have other ways to read ePubs and the like. But if others are finding the same issues, then this could help them as well. Thanks!

PS - I have installed 1755...

[JSWolf]

This thread belongs in the KOReader forum as it's about KOReader.

[downeaster59]

Hi, Jon,

In response, here is a quote from the OP of the Kindle-KOReader thread in the KOReader forum. The OP is here:

"Please address any Kindle-specific questions (e.g. device integration, getting KOReader to run, anything where it matters that you are using a Kindle and not a Kobo/Pocketbook/Android) in the Kindle Developer's Corner."

I would argue that this thread does belong here, based on this quote.

[NiLuJe]

@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 .).

[downeaster59]

@NiLuJe: Thanks for the link for debug mode. I'll get to that at some point today and post the results.

Well, if it comes to USBNet, it'll give me a reason to learn something about it in the process. Aaaaannnddd, it may prove useful in other ways as well! All good.

I can go over your exchange with @7hir7een and get a sense of what is involved.

Thanks again.

[NiLuJe]

@downeaster59: I guess I can also put the bits I need in a custom KUAL extension and ask you to install & use that, and send me some files it'll create instead .

I think I did something of the sort already at one point of the KOA2 stuff, so I should have a skeleton ready to go .

[NiLuJe]

@downeaster59: Here goes for the KUAL approach .

Unpack at the root like any other KUAL extension, click it once, and send me the KOA2_NiLuJe_test.txt ile it'll have dumped (at the root, again).

EDIT: Oops, fixed it.

[downeaster59]

Originally Posted by NiLuJe

@downeaster59: Here goes for the KUAL approach .

Unpack at the root like any other KUAL extension, click it once, and send me the KOA2_NiLuJe_test.txt ile it'll have dumped (at the root, again).

I may be doing something wrong, because I can't find that txt file:

I've unpacked this at the root. I go to KUAL in my KOA2. Under the "Helper" heading, I see "Test KOA2 Stuff". I click that, and then see "Done" appear at the bottom of the display.

Then, when I search for that txt file, I cannot find it! Have I missed something?

[NiLuJe]

@downeaster59: No, you haven't, I indeed did something wrong, lemme double check .

[NiLuJe]

Yep, another stupid typo .

I updated the attachment in the earlier post, this time it should behave properly .

[downeaster59]

Originally Posted by NiLuJe

Yep, another stupid typo .

I updated the attachment in the earlier post, this time it should behave properly .

That did it!

[NiLuJe]

@downeaster59: Quick question: was is it actually upside down when you were in KUAL?

[downeaster59]

Originally Posted by NiLuJe

@downeaster59: Quick question: was is it actually upside down when you were in KUAL?

I usually use the KOA2 with the physical buttons on the left. That may be "upside down" - I'm not sure!

[NiLuJe]

@downeaster59: Yep, that's what I meant .

That's good news, that means it may just be a case of me handling rotation terribly badly .

EDIT: Well the rotation code makes my brain hurt. >_<".

Can you try launching in normal mode, with the device upright (i.e., portrait, buttons on the right)?