Reduce Brightness on Touch Lux 3

white_gecko · 12-11-2020, 04:19 PM

I initially bought a Pocket Book Touch Lux 2 and later the Touch Lux 3 because it had the possibility to dim its brightness very low which was very comfortable for reading at night.
Recently I did an update to version U626.5.20.1157 which brought nice updates but since this update the lowest setting for the light is very bright.
;-)
Well, I could try to downgrade the system until I end up with the wanted behavior. But since I could not find anything in the change logs of Pocket Book about this, it is hard for me to track down which was the last version that had the "dark mode".

Does anybody know, which version introduced that change?

Does anybody know, which is the setting file to adjust the brightness e.g. using a Terminal like poterm? Or how to do that with the terminal? (In this case I think a script could do the job.)

Do other users experience the same issue? Or is it specific to me?

white_gecko · 12-12-2020, 07:18 AM

I want a bit further and gained root and ssh access to my device (https://www.mobileread.com/forums/sh...d.php?t=325185)

find provided me with the following result:

Code:

~ # find -iname "bright*"
./sys/devices/platform/tps61161_bl/brightness
./sys/devices/platform/leds-sunxi/leds/power_led/brightness

cat gave

Code:

~ # cat ./sys/devices/platform/leds-sunxi/leds/power_led/brightness
1
~ # cat ./sys/devices/platform/tps61161_bl/brightness
33

sending

Code:

echo 0 > ./sys/devices/platform/leds-sunxi/leds/power_led/brightness
echo 1 > ./sys/devices/platform/leds-sunxi/leds/power_led/brightness

switches the power led off and on, as expected

Code:

~ # echo 28 > ./sys/devices/platform/tps61161_bl/brightness

dims the light. When it is dark I have to find the best value. So far it seems as if the reading light turns of at "27", but maybe I just don't see it.

white_gecko · 12-12-2020, 07:36 AM

"28" dims the light to the lowest possible. "27" is off.

I write a small script/app, which unfortunately only works with root access.

Code:

#!/bin/sh
echo 28 | /mnt/secure/su /bin/tee /sys/devices/platform/tps61161_bl/brightness

just put this into a file "brightness.app" in "applications".

Unfortunately the value will be reset when the reader goes to standby and back.

rkomar · 12-12-2020, 11:16 AM

The value set by the UI is probably saved in a configuration file somewhere in /system. On my Colour, /mnt/ext1/system/config/global.cfg has the entry:

FrontLightLastState=37

Perhaps if you update that value, as well, it will be preserved when you come back from standby.

white_gecko · 12-14-2020, 05:52 PM

Thank you for the hint. I also have this line, but changing it with

Code:

sed

did not no the trick. When going to standby and reactivating the reader again the value is set to

Code:

FrontLightLastState=0

by the system.

I guess it is necessary to interfere with the wake up procedure.

(should this thread be moved to the developers corner?)

nhedgehog · 12-15-2020, 12:46 AM

Can you please check if your system is not readonly (copy a book onto the device, switch the device off, restart, check if book is there after restart).

white_gecko · 12-16-2020, 06:12 PM

I have checked it, and no it is not read-only.
How should that relate to the setting issue? The config file is on /mnt/ext1 which is the sd-card. Also the value is set to 0 on suspend already not only reboot.

rkomar · 12-17-2020, 12:09 AM

/mnt/ext1 is part of the internal storage. The SD card you insert yourself is mounted at /mnt/ext2.

The configuration files are saved to the filesystem in /mnt/ext1. On some devices, the internal storage was actually an SD card, as well, and that would go bad for some people and revert to read-only mode. In that mode, no permanent changes to the files were possible. It would look like the files were changed while the device was running, but the changes were only in RAM and wouldn't be saved to storage when the device shut down. So, when you rebooted the device, all the old configuration settings would reappear. Indications of bad storage are configuration changes that revert, books that disappear after being copied to the device or reappear after being deleted, the state of read books (i.e. last page read, font size,...) reverting to the old settings,... When these strange events happen, it is probably because the internal storage has gone bad. So, it's good to check that that isn't the problem before trying to figure out what may be changing a file on reboot.

12-11-2020, 04:19 PM	#1
white_gecko Junior Member Posts: 5 Karma: 10 Join Date: Dec 2020 Device: Pocket Book Touch Lux 3 (626)	Reduce Brightness on Touch Lux 3 I initially bought a Pocket Book Touch Lux 2 and later the Touch Lux 3 because it had the possibility to dim its brightness very low which was very comfortable for reading at night. Recently I did an update to version U626.5.20.1157 which brought nice updates but since this update the lowest setting for the light is very bright. ;-) Well, I could try to downgrade the system until I end up with the wanted behavior. But since I could not find anything in the change logs of Pocket Book about this, it is hard for me to track down which was the last version that had the "dark mode". Does anybody know, which version introduced that change? Does anybody know, which is the setting file to adjust the brightness e.g. using a Terminal like poterm? Or how to do that with the terminal? (In this case I think a script could do the job.) Do other users experience the same issue? Or is it specific to me?

12-12-2020, 07:18 AM	#2
white_gecko Junior Member Posts: 5 Karma: 10 Join Date: Dec 2020 Device: Pocket Book Touch Lux 3 (626)	I want a bit further and gained root and ssh access to my device (https://www.mobileread.com/forums/sh...d.php?t=325185) find provided me with the following result: Code: ~ # find -iname "bright*" ./sys/devices/platform/tps61161_bl/brightness ./sys/devices/platform/leds-sunxi/leds/power_led/brightness cat gave Code: ~ # cat ./sys/devices/platform/leds-sunxi/leds/power_led/brightness 1 ~ # cat ./sys/devices/platform/tps61161_bl/brightness 33 sending Code: echo 0 > ./sys/devices/platform/leds-sunxi/leds/power_led/brightness echo 1 > ./sys/devices/platform/leds-sunxi/leds/power_led/brightness switches the power led off and on, as expected Code: ~ # echo 28 > ./sys/devices/platform/tps61161_bl/brightness dims the light. When it is dark I have to find the best value. So far it seems as if the reading light turns of at "27", but maybe I just don't see it.

12-12-2020, 07:36 AM	#3
white_gecko Junior Member Posts: 5 Karma: 10 Join Date: Dec 2020 Device: Pocket Book Touch Lux 3 (626)	"28" dims the light to the lowest possible. "27" is off. I write a small script/app, which unfortunately only works with root access. Code: #!/bin/sh echo 28 \| /mnt/secure/su /bin/tee /sys/devices/platform/tps61161_bl/brightness just put this into a file "brightness.app" in "applications". Unfortunately the value will be reset when the reader goes to standby and back.

12-14-2020, 05:52 PM	#5
white_gecko Junior Member Posts: 5 Karma: 10 Join Date: Dec 2020 Device: Pocket Book Touch Lux 3 (626)	Thank you for the hint. I also have this line, but changing it with Code: sed did not no the trick. When going to standby and reactivating the reader again the value is set to Code: FrontLightLastState=0 by the system. I guess it is necessary to interfere with the wake up procedure. (should this thread be moved to the developers corner?)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Reduce brightness on all kobo devices / challenge for developers	akorx	Kobo Reader	14	03-09-2019 07:19 AM
Reduce brightness on all kobo devices / challenge for developers	akorx	Kobo Developer's Corner	4	03-04-2019 07:58 PM
Basic Lux or Touch Lux 3?	Manodragon	PocketBook	9	12-19-2017 12:53 AM
Replace brocken PB626 Touch Lux 2 Display with new Touch Lux 3 display	biokomiker	PocketBook Developer's Corner	2	05-10-2017 01:12 AM
Difference between PocketBook Touch Lux 3 and Tea Touch Lux 3?	Shohreh	PocketBook	2	01-19-2016 12:33 PM

12-12-2020, 11:16 AM	#4
rkomar Wizard Posts: 2,987 Karma: 18343081 Join Date: Oct 2010 Location: Sudbury, ON, Canada Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633	The value set by the UI is probably saved in a configuration file somewhere in /system. On my Colour, /mnt/ext1/system/config/global.cfg has the entry: FrontLightLastState=37 Perhaps if you update that value, as well, it will be preserved when you come back from standby.

12-15-2020, 12:46 AM	#6
nhedgehog Guru Posts: 749 Karma: 622656 Join Date: Sep 2013 Device: EnergySistemEreaderPro, Nook STG, Pocketbook 622, Bookeen Cybooks ...	Can you please check if your system is not readonly (copy a book onto the device, switch the device off, restart, check if book is there after restart).

12-16-2020, 06:12 PM	#7
white_gecko Junior Member Posts: 5 Karma: 10 Join Date: Dec 2020 Device: Pocket Book Touch Lux 3 (626)	I have checked it, and no it is not read-only. How should that relate to the setting issue? The config file is on /mnt/ext1 which is the sd-card. Also the value is set to 0 on suspend already not only reboot.

12-17-2020, 12:09 AM	#8
rkomar Wizard Posts: 2,987 Karma: 18343081 Join Date: Oct 2010 Location: Sudbury, ON, Canada Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633	/mnt/ext1 is part of the internal storage. The SD card you insert yourself is mounted at /mnt/ext2. The configuration files are saved to the filesystem in /mnt/ext1. On some devices, the internal storage was actually an SD card, as well, and that would go bad for some people and revert to read-only mode. In that mode, no permanent changes to the files were possible. It would look like the files were changed while the device was running, but the changes were only in RAM and wouldn't be saved to storage when the device shut down. So, when you rebooted the device, all the old configuration settings would reappear. Indications of bad storage are configuration changes that revert, books that disappear after being copied to the device or reappear after being deleted, the state of read books (i.e. last page read, font size,...) reverting to the old settings,... When these strange events happen, it is probably because the internal storage has gone bad. So, it's good to check that that isn't the problem before trying to figure out what may be changing a file on reboot.

Advert

Advert