Terminal emulator for Touch (and Paperwhite?) - Page 16

nasser · 10-03-2016, 09:54 AM

Quote:

Originally Posted by baf

Thanks for testing!

I got rid of visible resizing on kt, I don't have pw, so I will leave it as is for now.
Config entry for rotation is orientation = U with possible choices of U, L or R.

v2.2 working OK on PW3 and KT3.
Config entry for orientation also works on PW1, PW3, KT3.
Visible resizing not seen in KT3, but still present in PW3. Seems to be a Paperwhite specific issue?

knc1 · 10-03-2016, 10:16 AM

Sounds like the display controller is being started earlier on the paper white devices.
Perhaps to have it running before the front light controller starts.

The sequence is probably too fast for the human eye -

but does the resizing happen before the front light comes on?

Maybe a more practical suggestion:
Is there any difference in the start-up scripts (sequence or content) used between the KT3 and the PW3?

nasser · 10-03-2016, 11:12 AM

Quote:

Originally Posted by knc1

Sounds like the display controller is being started earlier on the paper white devices.
Perhaps to have it running before the front light controller starts.

The sequence is probably too fast for the human eye -

but does the resizing happen before the front light comes on?

Maybe a more practical suggestion:
Is there any difference in the start-up scripts (sequence or content) used between the KT3 and the PW3?

On PW1, I used the frontlight toggle hack to turn off the frontlight. Then started kterm. The resizing lag is still there.
The startup script (kterm.sh) is the same for all kindles. No separate scripts.
On PW1, however, there is no lag sometimes. I tried the following combinations to start kterm:

Start through search bar shortcut (;kt) - portrait mode: no lag, landscape mode: lag present
Start from Kindle explorer - portrait mode: no lag, landscape mode: lag present
Start through KUAL - portrait mode: lag present, landscape mode: lag present

Should also add that my PW1 is quite low on free storage (< 200 MB)... Don't know if that would make any difference.

knc1 · 10-03-2016, 11:45 AM

Thanks for that testing, for the #3 case, try this:

Current (json):

Code:

{
	"items": [
		{"name": "kterm", "priority": 1, "action": "bin/kterm.sh"}
	]
}

Try:

Code:

{
	"items": [
		{"name": "kterm", "priority": 1, "action": "exec", "params": "./bin/kterm.sh"}
	]
}

At least on a PW-1, that should give a quicker start-up from KUAL.
(less process over-head to chain to the next executable)

Edit:
Which KUAL is that? The Document or the Booklet?

Notes:
They can both be installed at the same time.
They use the same part of the extension tree and files.
The Booklet will run on all touchscreen devices (K5 and up).
The Booklet **should** have less overhead. For example, the Kindle's main page is a Booklet.

baf · 10-03-2016, 11:52 AM

Quote:

Originally Posted by nasser

v2.2 working OK on PW3 and KT3.
Config entry for orientation also works on PW1, PW3, KT3.
Visible resizing not seen in KT3, but still present in PW3. Seems to be a Paperwhite specific issue?

It is probably related to slow eink refreshing. Now I noticed that it is more visible when starting from kual. It is not so important, I probably could hide the widget while building layout. Maybe if I have more time some day…

I have put the images through filter that sharpened it and also I managed to decrease sizes. Please test on bigger resolution devices. On KT it looks ok.

nasser · 10-03-2016, 11:58 AM

@knc1
Tried your suggestion (different menu.json) on PW1... No change in behaviour. Lag still present for both orientations. In fact seems more for landscape mode.

nasser · 10-03-2016, 01:09 PM

Quote:

Originally Posted by baf

It is probably related to slow eink refreshing. Now I noticed that it is more visible when starting from kual. It is not so important, I probably could hide the widget while building layout. Maybe if I have more time some day…

I have put the images through filter that sharpened it and also I managed to decrease sizes. Please test on bigger resolution devices. On KT it looks ok.

Slow eink refreshing? Is that a sign of an ageing or worn out kindle?

New image sets load OK on all three types of kindles. And substantial file size reduction too. Thanks, baf!

knc1 · 10-03-2016, 01:29 PM

Quote:

Originally Posted by nasser

@knc1
Tried your suggestion (different menu.json) on PW1... No change in behaviour. Lag still present for both orientations. In fact seems more for landscape mode.

Good.
Confirms baf's suspicion that what you see is a result of the screen refresh rate.

I.E: Application starts with the same delay or LESS to let you see more of the screen refresh.

The PW-1 has the older i.MX50 series cpu/SoC - the newer devices have the i.MX6 cpu/SoC.
And the newer i.MX6 SoC includes an enhanced performance e-ink controller.

All of those differences should go away when someone delays the 'widget show' until after the drawing is complete.

I wrote 'someone' because this is probably in his public repository, anyone can submit a patch, we don't have to wait for baf to do it himself.

baf · 10-03-2016, 02:18 PM

Quote:

Originally Posted by nasser

Slow eink refreshing? Is that a sign of an ageing or worn out kindle?

I would say it is just a sign of an eink screen

Quote:

Originally Posted by nasser

New image sets load OK on all three types of kindles. And substantial file size reduction too. Thanks, baf!

Great. I will package new set then.

baf · 10-03-2016, 02:22 PM

Quote:

Originally Posted by knc1

Good.
Confirms baf's suspicion that what you see is a result of the screen refresh rate.

I.E: Application starts with the same delay or LESS to let you see more of the screen refresh.

The PW-1 has the older i.MX50 series cpu/SoC - the newer devices have the i.MX6 cpu/SoC.
And the newer i.MX6 SoC includes an enhanced performance e-ink controller.

All of those differences should go away when someone delays the 'widget show' until after the drawing is complete.

I wrote 'someone' because this is probably in his public repository, anyone can submit a patch, we don't have to wait for baf to do it himself.

Thanks for the explanation!
Contributions most welcome!

baf · 10-03-2016, 04:43 PM

Quote:

Originally Posted by nasser

baf has included a logic in the kterm.sh file which checks the resolution of the kindle and selects the appropriate layout files. But this has to be updated for the 300 ppi kindles. And also, of course, all the 3 sets of image files need to be available.

Could you check that this command will get dpi on all the platforms. On KT it does.

Code:

cat /var/log/Xorg.0.log | grep DPI | sed -n 's/.*(\([0-9]\+\), [0-9]\+).*/\1/p'

Or maybe there is a better way to get dpi from command line?
Previously I used xwininfo, but I would prefer to have screen dpi, not dimensions.

nasser · 10-03-2016, 10:24 PM

Quote:

Originally Posted by baf

Could you check that this command will get dpi on all the platforms. On KT it does.

Code:

cat /var/log/Xorg.0.log | grep DPI | sed -n 's/.*(\([0-9]\+\), [0-9]\+).*/\1/p'

On PW1, got result as 211
Will check on the others later..

JimmyR · 10-03-2016, 11:24 PM

On K5: 167

encol · 10-04-2016, 02:58 AM

Quote:

Originally Posted by baf

Could you check that this command will get dpi on all the platforms. On KT it does.

Code:

cat /var/log/Xorg.0.log | grep DPI | sed -n 's/.*(\([0-9]\+\), [0-9]\+).*/\1/p'

On my PW3 i get:

Code:

baf · 10-04-2016, 05:52 AM

Thank you all for help!

I have uploaded new release to github. The keyboard layouts should now be properly chosen according to screen resolution.

10-03-2016, 11:45 AM	#229
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Thanks for that testing, for the #3 case, try this: Current (json): Code: { "items": [ {"name": "kterm", "priority": 1, "action": "bin/kterm.sh"} ] } Try: Code: { "items": [ {"name": "kterm", "priority": 1, "action": "exec", "params": "./bin/kterm.sh"} ] } At least on a PW-1, that should give a quicker start-up from KUAL. (less process over-head to chain to the next executable) Edit: Which KUAL is that? The Document or the Booklet? Notes: They can both be installed at the same time. They use the same part of the extension tree and files. The Booklet will run on all touchscreen devices (K5 and up). The Booklet should have less overhead. For example, the Kindle's main page is a Booklet. Last edited by knc1; 10-03-2016 at 12:01 PM.

10-04-2016, 05:52 AM	#240
baf Evangelist Posts: 405 Karma: 2330752 Join Date: May 2012 Device: kt	kterm 2.2 Thank you all for help! I have uploaded new release to github. The keyboard layouts should now be properly chosen according to screen resolution.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
One more terminal emulator for kindle.	Matan	Kindle Developer's Corner	160	07-15-2025 12:43 AM
PRS-T1 Terminal Emulator in rupor-minimal	jcromero	Sony Reader Dev Corner	2	09-26-2012 02:07 PM
Anybody working on terminal for Kindle Touch?	markatlnk	Kindle Developer's Corner	3	06-02-2012 10:07 AM
Development Terminal Emulator oddity	twichy	enTourage Archive	5	05-01-2011 11:51 AM
DR800 rxvt (terminal emulator) for DR800	GregorRichards	iRex	13	01-04-2011 06:56 AM

10-03-2016, 10:16 AM	#227
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Sounds like the display controller is being started earlier on the paper white devices. Perhaps to have it running before the front light controller starts. The sequence is probably too fast for the human eye - but does the resizing happen before the front light comes on? Maybe a more practical suggestion: Is there any difference in the start-up scripts (sequence or content) used between the KT3 and the PW3?

10-03-2016, 11:58 AM	#231
nasser Evangelist Posts: 475 Karma: 445678 Join Date: Feb 2010 Device: Too many..	@knc1 Tried your suggestion (different menu.json) on PW1... No change in behaviour. Lag still present for both orientations. In fact seems more for landscape mode.

10-03-2016, 11:24 PM	#238
JimmyR ɴₐɴ Posts: 421 Karma: 2507940 Join Date: Jun 2011 Location: 37.2N 93.3W Device: KV PW4 PW3 PW2	On K5: 167

Advert

Advert