View Single Post
Old 06-17-2016, 06:36 PM   #47
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by knc1 View Post
Probably the all too common "off by one" programing error.
Ah yes, the classic "Obi-Wan" error.

I tried telling it to set the frontlight brightness to "-1", but no jailbreak resulted from that. Just an error message.

I did not have a room dark enough for visual testing at the time I posted this discovery. It looked "off" to me, and besides, after setting it to zero with lipc-set-prop, reading it back with lipc-get-prop showed that it was indeed zero. Why would kindle software lie to us?

Though it makes sense that its behavior mimics the brightness slider, which is probably just a GUI layer over this very same lipc command.

Whereas the corresponding /sys file is a kernel driver interface, which gives us a closer connection to "bare metal" reality and a greater degree of control (where zero is indeed off, and 999 is max brightness).

Last edited by geekmaster; 06-17-2016 at 09:42 PM.
geekmaster is offline   Reply With Quote