Collections Manager

[NiLuJe]

This possibly feels like brokenish Kindlet framework on the PW3, potentially nothing much we can do about it.
I don't think we have anything else that uses the native Menu system to double-check, though, so...

Does any part of the main container feels broken, besides auxiliary stuff like the menu?

[krupped]

Hmm, possibly. If by main container (forgive my lack of knowledge of the terminology, this is my first time messing around with a kindle), you mean the main UI, then yes, occasionally when switching back to it by pressing home some things fail to render, like it's being a little conservative on what portions of the screen it needs to refresh. Kind of reminds me of a misbehaving libxdamage or something. However, everything usable or clickable is always refreshed.

If by main container you instead mean the main UI of the collections manager, most of it doesn't render unless I press as of yet unrendered buttons (forcing it to draw some new books or collections etc). None of the boxes render unless I press the box to select-all, then all the boxes show up ticked. That kind of thing. So in general, it feels pretty broken.

[nasser]

Originally Posted by knc1

By 'feel around' you mean the touch sensitive spot is not aligned with the graphic?

Note that the poster has a PW2 and your using a PW3.
Different screen resolutions, different screen dimensions (in pixels).

knc1,
I think this kind of issue exists in all add-ins/extensions which were originally developed for the earlier 758x1024 resolution. The icons and/or application area look smaller and in some cases are difficult to view or touch.

What I've seen so far with my PW3:
1. Kindle explorer: smaller menu buttons
2. RGB paint: really tiny menu buttons

I expect Aeris' kindle menu will similarly be affected.

A similar issue existed for the original PW1 with extensions written for the earlier 600x800 resolution.

Have to wait till the original developers rewrite them for the higher resolution

[NiLuJe]

@krupped: I meant the main "window" of CM, yeah.

But the fact that you mention noticing this in the base UI is highly surprising, and would make me question the sanity of your specific hardware: the Kindle UI is pretty damn good at not messing up what it does with the eInk screen. I can't recall ever seeing it break down unless I was doing something to make it break ;p.

@nasser: I'm not familiar with CM's UI code, but it was initially laid out to handle a couple of different resolutions properly (600x800 & 758x1024).
Besides the obvious (bitmap icons), and some possible alignment issues for some stuff, it should behave more or less properly?

[knc1]

Originally Posted by krupped

Hmm, possibly. If by main container (forgive my lack of knowledge of the terminology, this is my first time messing around with a kindle), you mean the main UI, then yes, occasionally when switching back to it by pressing home some things fail to render, like it's being a little conservative on what portions of the screen it needs to refresh. Kind of reminds me of a misbehaving libxdamage or something. However, everything usable or clickable is always refreshed.

If by main container you instead mean the main UI of the collections manager, most of it doesn't render unless I press as of yet unrendered buttons (forcing it to draw some new books or collections etc). None of the boxes render unless I press the box to select-all, then all the boxes show up ticked. That kind of thing. So in general, it feels pretty broken.

That sounds to be a far more general problem than just CM.

What are the first six characters of the device's serial number and what firmware version is it running?
(Both to be found in the "Device Info" panel - if you can get it to display).

[krupped]

@NiLuJe: I should note that strange behaviour only really happens in the base UI after exiting CM or koreader (although I can't seem to get it to happen after koreader anymore, perhaps it was only CM). No Amazon provided software seems to mess up on its own in isolation. Is there an easy way for me to take a screenshot to show you guys? Other than a cellphone picture I suppose.

@knc1: G090G1 and 5.8.1 (2974819923) I jailbroke it on Monday following your instructions here: https://www.mobileread.com/forums/sho...d.php?t=275877

[knc1]

Try the 'two corner' touch - simultaneously touch two diagonal corners of the screen.

Did you use the 5.6.1.1 or the 5.7.4 downgrade package?

[krupped]

@knc1: I used 5.7.4, here is a screen of what I see.

[knc1]

Originally Posted by krupped

@knc1: I used 5.7.4, here is a screen of what I see.

That does look broke and we can't blame factory-5.6.1.1 for this one.

Oh, and I suppose that confirms the 'double touch for screenshot' function is still working on that device/firmware (5.8.1) combination.

There are not a lot of users (yet) of CM on your combination of device and firmware.
Which will make learning if a single trouble report is a local problem or something more general with the CM package.

[krupped]

If you know of anything I can try that might get you information I would be happy to try it.

[NiLuJe]

Yuuup, no idea what's going on there, but what @knc1 said ;D.

Can you check if the Booklet version of KUAL renders differently than the Kindlet version? (Besides the fact that the Booklet version hides the menubar).

[krupped]

@NiLuJe: I'm just running it by opening it as a document, I'm not running it through KUAL (that I know of). Could you link me to instructions or some more docs? I'm not quite sure what you mean D:

[knc1]

Originally Posted by krupped

@NiLuJe: I'm just running it by opening it as a document, I'm not running it through KUAL (that I know of). Could you link me to instructions or some more docs? I'm not quite sure what you mean D:

Ah, I sense a disconnect here.

There are three builds of KUAL (all in the same, very recent, v2.7, archive. see sticky area above the thread index).
The one for the keyboard devices (KUAL-KDK-1.0.azw2)
The one for the touchscreen devices (KUAL-KDK-2.0.azw2)

And the newest one, an update_*.bin format package. (Update_KUALBooklet_v2.7_install.bin)
THAT one is the 'booklet' version of KUAL.

You will need to use MrPI to install it.

I think you can have it installed at the same time as the older document version (but you could just remove the document version of KUAL from /documents while testing. All of the /extensions files can remain - they both use the same ones).

[krupped]

Aha! I see now, I was using the KUAL-KDK-2.0.azw2 version. The booklet build seems to render fine as far as I can tell. Here are screens.

[knc1]

I wonder what the PADD thing is.
Perhaps NiLuJe will tell us.

Of note, the 'Booklet' version is the only version supported by the KT3 and KOA devices.

The 'Home screen' which is messed up on your device is also a 'Booklet' -
but ours seems to work (it is Amazon's Booklet that has problems).