I agree that it's a pity the way the LED ended up being handled differently on our devices. Vibrate is at least consistent across all the devices, stopping on it's own after a little while. As I understand it, the reason the m500 series LED stops blinking after a little while is that leaving it going would consume too much power. So, I'd expect future non-wireless devices to continue this trend (as they don't have a radio that sucks lots of power, and therefore can afford to use smaller and lighter power sources).
If you override the resources used by the attention manager to specify the LED blinking pattern, you should be able to make the LED stop blinking after a while, just as it does on the m500 series. If the user dismisses all the requests, the attention manager will stop the LED for you, assuming it is still blinking. In short, you should be able to make the LED behave as it does on the m500 series by just overriding some resources. The question of how to detect the device you're running on has come up many times on this forum. I'm not familiar with the techniques, as I work mostly with apps that live in ROM. It should be possible to detect whether you're running on the i705 easily enough, but that's not really what you want to do. You want to know whether the LED will continue to blink indefinitely. This can be determined by getting the values of the resources used to specify the LED blink pattern. I'd verify this by testing it on an m500 series device and an i705 (using POSE), but I think you can read the 'tint' resource with ID 13503 to determine the repeat count. If this is zero, it repeats forever. If it's any other number (eg 3), then it repeats that many times and then stops on it's own. This is how I'd decide whether to use the LED or not. -- Peter Epstein -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
