LED patterns
codemonkey (Talk | contribs) (→LEDsToMap) |
codemonkey (Talk | contribs) (→N900) |
||
| Line 14: | Line 14: | ||
PatternName=Priority;ScreenOn;Timeout;LEDsToMap;Engine1Pattern;Engine2Pattern | PatternName=Priority;ScreenOn;Timeout;LEDsToMap;Engine1Pattern;Engine2Pattern | ||
| - | === Priority === | + | === Pattern Format === |
| + | |||
| + | ==== Priority ==== | ||
0-255, 0 is highest, 255 is lowest. | 0-255, 0 is highest, 255 is lowest. | ||
| Line 21: | Line 23: | ||
A common example of this is where the n900 is on charge, the battery is full (starting PatternBatteryFull with a priority of 40), and an SMS message is received (PatternCommunicationSMS with a priority of 30). On receipt of the SMS, the LED begins to display the flashing blue led of an SMS. Once that SMS has been dismissed, the green LED of the full battery notification is again displayed. | A common example of this is where the n900 is on charge, the battery is full (starting PatternBatteryFull with a priority of 40), and an SMS message is received (PatternCommunicationSMS with a priority of 30). On receipt of the SMS, the LED begins to display the flashing blue led of an SMS. Once that SMS has been dismissed, the green LED of the full battery notification is again displayed. | ||
| - | === ScreenOn === | + | ==== ScreenOn ==== |
* 0: only show pattern when the display is off | * 0: only show pattern when the display is off | ||
* 1: show pattern even when the display is on | * 1: show pattern even when the display is on | ||
| Line 29: | Line 31: | ||
* 5: always show pattern, even if LED disabled | * 5: always show pattern, even if LED disabled | ||
| - | === TimeOut === | + | ==== TimeOut ==== |
This is the time-out of the LED pattern in seconds. 0 for infinite, i.e. until the notification is dismissed. | This is the time-out of the LED pattern in seconds. 0 for infinite, i.e. until the notification is dismissed. | ||
If this is set to 20, the pattern will display for 20 seconds, and then stop. | If this is set to 20, the pattern will display for 20 seconds, and then stop. | ||
| - | === LEDsToMap === | + | ==== LEDsToMap ==== |
There are two engines that can be used to make custom LED patterns.<ref name="engines">Actually there are three, but the third engine is used exclusively for the keyboard LED.</ref> | There are two engines that can be used to make custom LED patterns.<ref name="engines">Actually there are three, but the third engine is used exclusively for the keyboard LED.</ref> | ||
Revision as of 11:55, 8 January 2010
(UNDER CONSTRUCTION)
Contents |
N800
The N800 has a single-colour (blue) LED behind the dpad.
N810
The N810 has an RGB LED.
N900
The patterns in the /etc/mce/mce.ini are broken down as follows:
PatternName=Priority;ScreenOn;Timeout;LEDsToMap;Engine1Pattern;Engine2Pattern
Pattern Format
Priority
0-255, 0 is highest, 255 is lowest.
Since currently only a single pattern at a time can be displayed, this is important to assign importance to the led patterns. Although only a single LED pattern can be displayed at a time, multiple patterns may be active at any one time, the pattern with the highest priority being displayed.
A common example of this is where the n900 is on charge, the battery is full (starting PatternBatteryFull with a priority of 40), and an SMS message is received (PatternCommunicationSMS with a priority of 30). On receipt of the SMS, the LED begins to display the flashing blue led of an SMS. Once that SMS has been dismissed, the green LED of the full battery notification is again displayed.
ScreenOn
- 0: only show pattern when the display is off
- 1: show pattern even when the display is on
- 2: only show pattern when the display is off, including acting dead
- 3: show pattern even when the display is on, including acting dead
- 4: only show pattern if the display is off, or if in acting dead
- 5: always show pattern, even if LED disabled
TimeOut
This is the time-out of the LED pattern in seconds. 0 for infinite, i.e. until the notification is dismissed.
If this is set to 20, the pattern will display for 20 seconds, and then stop.
LEDsToMap
There are two engines that can be used to make custom LED patterns.[1]
r, g, or b maps the corresponding LED to Engine 1.
R, G, or B maps the corresponding LED to Engine 2.
For example, "rG" maps the red LED to Engine 1, and the green LED to Engine 2.
You should avoid mapping the same LED to both engines.
Lysti Format Engine Patterns
- Engine 1 pattern in Lysti format (16 commands at most)
- Engine 2 pattern in Lysti format (16 commands at most)
- 0000 -- Jump to the start of the pattern for the channel
- 40xx -- Set channel brightness
- 9d80 -- Refresh Mux (use as first command in every pattern!)
- xxyy -- Increment/decrement
- xx determines the speed;
- 02-3f -- short step time (granularity 0.49ms)
- 42-7f -- long step time (granularity 15.6ms)
- If xx is even, increment
- If xx is odd, decrement
- yy determines the increment/decrement steps
- 00-ff -- in/decrement steps
- Use 0 steps to create pauses
- Two consecutive increment/decrement sequences are needed
- to cover the entire range from 0-255
- c000 -- End pattern execution
- e002 -- Send engine 1 trigger
- e004 -- Send engine 2 trigger
- e008 -- Send engine 3 trigger <used by key backlight!>
- e080 -- Wait for engine 1 trigger
- e100 -- Wait for engine 2 trigger
- e200 -- Wait for engine 3 trigger <used by key backlight!>
Cite error:
<ref> tags exist, but no <references/> tag was found