Since these days several people are having problems with the nightmode (for nickel), I mention some details (as far as they concern KSM users). I have nothing new to say, but it may help some people nonetheless.
The nightmode hack has an initalization routine that does not work when a certain line of a certain file (rcS) changes. Since some firmware updates make changes to the rcS file, the initialization routine can stop working and someone has to modify the script. Up to now this happend at least twice. With KSM, however, the nightmode hack does not rely on this installation routine; actually the installation routine did never work with KSM.
In KSM you have instead to select in (KSM home) "configure," in the section [nickel], nickelpreload="/root/screenInv.so."
There are several methods to switch nightmode on and off; not all are available on all models and with all versions of the nightmode hack.
- On devices that have a hardware home button or a hardware frontlight button, you can toggle nightmode with those buttons.
- You can toggle also with the help of fmon. KSM has this build in. Therefore you can toggle by opening toggle_nightmode.png.
- With one version (some versions?) of nightmode you can use the light slider to toggle nightmode on and off. We are told that this does not work on Aura One. But I do not know for sure.
- You can edit the nightmode configuration file to switch nightmode on or off. Instead of using a text editor for doing this, you can do it via the KSM configuration editor. You start the configuration tool by selecting "tools" > "nickel diverse.msh" > "edit nightmode conf.sh." There, you have to select in the section [state], invertActive=yes; or invertAcitve=no, depending on the case. It is not very convenient, but in some cases perhaps easier than to connect the device to a PC and edit the file there.