Future Button and LED software spec

Andy Powell openmoko at automated.it
Thu Apr 17 10:00:46 CEST 2008

On Thursday 17 April 2008 02:02, Shawn Rutledge wrote:
> On Wed, Apr 16, 2008 at 4:42 PM, Werner Almesberger <werner at openmoko.org> 
> >  Right now, we could only leave them permanently on, which comes with a
> >  hefty electricity bill, particularly on GTA02v5 (each LED burns about
> >  150mW). In GTA02v6, this should come down to about 25mW, maybe less.
> But  GTA02v5 is not going to ship is it?
> >  If all we're really interested in is whether some wireless is active,
> >  perhaps it should just be  blink = wlan || bt;  People can get the
> >  details from the LCM.
> Or just use it to indicate that an actual data transfer is occurring
> (like some ethernet LEDs).
> If security is implemented correctly, and power drain is also within
> typical specs, it's normal for Bluetooth to be left turned on and
> discoverable all the time.  (The BT SIG encourages this, but some
> phone mfgs have overreacted because of past security problems, so they
> have the default short timeouts for being discoverable, and in some
> cases BT is actually off by default when the phone powers up, etc.  Of


My preference is that BT is off by default, but what I prefer doesn't matter. 
What should be happening is the device should be restoring the state it was 
last in when powered up. So bt/wifi etc will just to what they were doing 


Andy / ScaredyCat

More information about the openmoko-devel mailing list