Screen, keypad light and vibration
Control the screen brightness, keypad light and vibration through the interfaces below. Check support status and your phone page before using a control; their availability and visible results depend on the phone.
Display
Section titled “Display”The display has a fixed native size, listed on the selected phone page. RGB565 images use two bytes per pixel and packed rows. The display does not scale or rotate images; prepare their size and orientation before using the image tools.
The graphical session uses Wayland. Applications that present frames directly use the DRM display interface and need the graphical session stopped. The phone pages state the limits of each phone’s visible image results.
Screen brightness
Section titled “Screen brightness”Brightness uses a scale from 0 to 10; 0 switches the backlight off. The default level is 7. The graphical session restores its saved brightness when available. Read and change the level in a shell on the phone:
fplinux-brightness getfplinux-brightness set 4To change it with the keypad, use Settings → Display → Brightness in the phone interface. The optional direct-display Brightness control application uses the same service.
The brightness service keeps the level during the current boot. Settings saves its selection with the other session settings; those files survive power-off only on a persistent system root. The numbers are settings, not percentages or light measurements, and the same number can look different on different phones.
Restarting the brightness service during the same boot preserves the selected level. Automatic screen-brightness control is not provided.
An application can change the brightness temporarily while it uses the screen. fplinux-brightness get keeps reporting your level, and a level you set meanwhile takes effect when the application finishes.
Switching off the backlight leaves the display running. After wake or display enable, the backlight stays off until the first frame is ready.
Keypad light
Section titled “Keypad light”On phones with automatic keypad lighting, the light turns on when you press a key and turns off about five seconds after the last key press. Input from a connected keyboard counts too. Check keypad-light support for your phone: manual lighting and automatic lighting from physical keys can have different support states. Most phones expose on/off control; the phone page lists any different brightness range.
On phones with automatic lighting, first disable its trigger:
echo none > /sys/class/leds/:kbd_backlight/triggerSwitch the light on at its maximum level or off:
cat /sys/class/leds/:kbd_backlight/max_brightness > /sys/class/leds/:kbd_backlight/brightnessecho 0 > /sys/class/leds/:kbd_backlight/brightnessA light switched on this way stays on until you switch it off. On phones with automatic lighting, restore its trigger with:
echo input-events > /sys/class/leds/:kbd_backlight/triggerVibration
Section titled “Vibration”There is no command to make the phone vibrate; applications such as ARMADA use it. Vibration is either on or off, with no adjustable strength, and each vibration stops automatically after about five seconds at most.
The phone page states whether vibration uses a motor or the speaker and whether it is supported. Speaker-based vibration plays a low tone and has additional conditions:
- vibration needs device data prepared from the same phone; without it, the phone does not vibrate;
- a single continuous vibration lasts at most about three seconds;
- headphone sound, including FM radio, is muted while the phone vibrates and for about a second afterwards; speaker sound keeps playing;
- a running recording picks up the vibration tone.
Developers can find the programming interface in Device interfaces.