Windows Mobile 6.5 Status LED Standards

During the release of Windows Mobile 6.5, Microsoft instituted defined hardware specifications under its chassis requirements to unify the user experience across various original equipment manufacturers (OEMs). A key component of these hardware requirements was the standardization of status and notification Light Emitting Diodes (LEDs). This article covers the standardized LED states for battery charging, critical power warnings, missed event notifications, and wireless connectivity defined across compliant Windows Mobile 6.5 hardware.

Power and Charging Status LEDs

Microsoft's hardware design guidelines required clear, real-time visual feedback regarding power delivery and battery health. These indicators were typically handled by a dedicated power LED or a multi-color primary LED:

  • Solid Amber or Red: Indicates that the device is connected to an external power source (via AC adapter or USB) and is actively charging.
  • Solid Green: Indicates that the battery has reached full charge capacity while remaining connected to an external power source.
  • Flashing Amber or Red: Signals a battery fault, such as an over-temperature state or an invalid battery pack.
  • Intermittent Flashing Red (on battery power): Warns the user that the battery level has dropped below the critical threshold (typically below 5% to 10% capacity) and requires immediate charging.

Notification and Event LEDs

To ensure users were alerted to incoming or pending events without turning on the display, Windows Mobile 6.5 utilized standardized notification triggers tied to the operating system's internal Notification Manager.

  • Flashing Green: Indicates pending, unread notifications. Standard system events that trigger this state include missed telephone calls, unread SMS/MMS messages, pending voicemail, unread email messages, and active calendar reminders.
  • Priority Escalation: The platform required notification LEDs to yield to critical power states; if a device had a low-battery condition while a missed message was pending, the low-battery warning took priority or combined into an alternating flash pattern depending on the physical LED configuration (dual-color vs. single-color).

Wireless Connectivity LEDs

While often integrated into the main notification light or split into a dedicated auxiliary LED, connectivity indicators followed specific signaling patterns:

  • Flashing or Pulsing Blue: Signifies an active Bluetooth connection, a device in pairing/discovery mode, or data transfer over a personal area network (PAN).
  • Solid Blue (select hardware): Indicated an active, paired headset or hands-free profile connection in use.

Software and Driver Implementation

Standardization was enforced through the Windows Embedded CE driver layer, specifically the Notification LED (NLED) driver architecture. Hardware vendors were required to map physical LED capabilities to standard Windows Mobile API structures:

  • NLedDriverGetDeviceInfo: Exposed the hardware capabilities (such as cycle times, flash rates, and available colors) to the OS.
  • NLedDriverSetDevice: Allowed system services to toggle blinking rates, steady-on states, and color assignments based on defined system priority tables.

Through these hardware requirements and low-level driver standards, Windows Mobile 6.5 established a consistent visual language across third-party devices from manufacturers such as HTC, Samsung, and HP.