Thread: Workarounds for a Lux 4 with broken screen?
View Single Post
Old 01-31-2024, 05:36 AM   #6
wold
Zealot
wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.
 
Posts: 137
Karma: 87012
Join Date: Apr 2021
Device: Lux 5, Libra 2, PRS-T2N
Quote:
Originally Posted by rkomar View Post
You probably have some key press linked to taking a screenshot. If so, there is no need to write your own app for that.
Good suggestion. There's no default screenshot key set on my Lux5 (6.7), and for 5.x it seems the same, also judging from the config.
One could configure a screenshot key manually (adding `@KA_scrn` to a `gkey`) except the config is protected by a magic number checksum... but copying from a working reader might just work

Still, for unrooted devices this would require (re)connection to view the screenshots, i.e. one can't navigate, so rooting is desired.

As for an app, it likely requires calling 2-3 SDK functions at minimum, from SSH or crontab. One issue there is trashing the disk with too many writes (->memory partition).

There is some practical use to this for me, and (hidden in the dear diary stuff) also the thought exercise of accessing a reader with a broken screen.
wold is offline   Reply With Quote