I support mickeys RFC, because I think, that this usage makes sense and it especially is what everybody that ever used a smartphone would expect.<br>Blue for bluetooth (standard on many many devices with BT) and wifi - I'd suggest slowly blinking for bluetooth (as this might be used heavy for headset users and so on - slow saves power), fast(er) blinking for wifi (maybe in combination with displaying activity by flashing slower or faster), constant on for both.<br>
Same for power - only reasonable position - glowing while charging, blinking on low-battery (somehow ironic to suck it down even more, but will be a useful indicator).<br>I also like the idea of the d-bus-events for the aux-led. So this led can be used for indicating every thing we want, might it be messages (mail, sms, im) in default mode, or other things by an running application that overrides it (cellmonitor on cell change e.g.).<br>
Of course we're talking about default settings here, there surely will be a gui to control it all.<br><br>@Werner: do you know - or can you figure out - how many GTA02v5 will leave the factory and reach the customers?<br>
And how will it be possible to find out what revision it is without powering it on?<br><br><div class="gmail_quote">On Thu, Apr 17, 2008 at 10:00 AM, Andy Powell <<a href="mailto:openmoko@automated.it">openmoko@automated.it</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Thursday 17 April 2008 02:02, Shawn Rutledge wrote:<br>
> On Wed, Apr 16, 2008 at 4:42 PM, Werner Almesberger <<a href="mailto:werner@openmoko.org">werner@openmoko.org</a>><br>
wrote:<br>
> > Right now, we could only leave them permanently on, which comes with a<br>
> > hefty electricity bill, particularly on GTA02v5 (each LED burns about<br>
> > 150mW). In GTA02v6, this should come down to about 25mW, maybe less.<br>
><br>
> But GTA02v5 is not going to ship is it?<br>
><br>
> > If all we're really interested in is whether some wireless is active,<br>
> > perhaps it should just be blink = wlan || bt; People can get the<br>
> > details from the LCM.<br>
><br>
> Or just use it to indicate that an actual data transfer is occurring<br>
> (like some ethernet LEDs).<br>
><br>
> If security is implemented correctly, and power drain is also within<br>
> typical specs, it's normal for Bluetooth to be left turned on and<br>
> discoverable all the time. (The BT SIG encourages this, but some<br>
> phone mfgs have overreacted because of past security problems, so they<br>
> have the default short timeouts for being discoverable, and in some<br>
> cases BT is actually off by default when the phone powers up, etc. Of<br>
<br>
</div><snip><br>
<br>
My preference is that BT is off by default, but what I prefer doesn't matter.<br>
What should be happening is the device should be restoring the state it was<br>
last in when powered up. So bt/wifi etc will just to what they were doing<br>
last.<br>
<font color="#888888"><br>
<br>
--<br>
<br>
Andy / ScaredyCat<br>
<br>
</font></blockquote></div><br>