MobileRead Forums - View Single Post

NiLuJe · 07-01-2018, 02:51 PM

@7hir7een: Yeah, that's what I understood, too.

That vaaaaguely made sense, but another possibility might be that it's tied to something that we're SIGSTOP'ping....

And just to double-check: that wasn't a "no framework" startup, was it? Because that's essentially broken on FW 5.x

.

So, another quick experiment:

While KOReader is running, but before doing the hexdump experiment again, run

Code:

killall -cont awesome

, then the hexdump thing again

.

(You'll probably get bits of the default UI seeping through, that's to be expected. Run killall -stop awesome & trigger a full screen update (f.g., closing the top menu) to get things back in order).

07-01-2018, 02:51 PM	#40
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@7hir7een: Yeah, that's what I understood, too. That vaaaaguely made sense, but another possibility might be that it's tied to something that we're SIGSTOP'ping.... And just to double-check: that wasn't a "no framework" startup, was it? Because that's essentially broken on FW 5.x . So, another quick experiment: While KOReader is running, but before doing the hexdump experiment again, run Code: killall -cont awesome , then the hexdump thing again . (You'll probably get bits of the default UI seeping through, that's to be expected. Run killall -stop awesome & trigger a full screen update (f.g., closing the top menu) to get things back in order).