View Single Post
Old 10-03-2016, 11:12 AM   #228
nasser
Evangelist
nasser ought to be getting tired of karma fortunes by now.nasser ought to be getting tired of karma fortunes by now.nasser ought to be getting tired of karma fortunes by now.nasser ought to be getting tired of karma fortunes by now.nasser ought to be getting tired of karma fortunes by now.nasser ought to be getting tired of karma fortunes by now.nasser ought to be getting tired of karma fortunes by now.nasser ought to be getting tired of karma fortunes by now.nasser ought to be getting tired of karma fortunes by now.nasser ought to be getting tired of karma fortunes by now.nasser ought to be getting tired of karma fortunes by now.
 
nasser's Avatar
 
Posts: 477
Karma: 445678
Join Date: Feb 2010
Device: Too many..
Quote:
Originally Posted by knc1 View Post
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:
  1. Start through search bar shortcut (;kt) - portrait mode: no lag, landscape mode: lag present
  2. Start from Kindle explorer - portrait mode: no lag, landscape mode: lag present
  3. 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.
nasser is offline   Reply With Quote