Verify that audio applications close the audio device when idle.

[jg]

If the audio device is open, it will consume some amount of power.

We need to audit, preferably in the tinderbox if possible, that applications are actually closing the audio device when idle.

Any offending applications should have bugs filed against them.

R396 and R379 can be used by tinderbox2 to measure the current draw of the AD1888 and the audio amp.

[rsmith]

Replying to jg:

If the audio device is open, it will consume some amount of power. We need to audit, preferably in the tinderbox if possible, that applications are actually closing the audio device when idle. Any offending applications should have bugs filed against them.

[rsmith]

Replying to jg:

If the audio device is open, it will consume some amount of power. We need to audit, preferably in the tinderbox if possible, that applications are actually closing the audio device when idle. Any offending applications should have bugs filed against them. R396 and R379 can be used by tinderbox2 to measure the current draw of the AD1888 an the audio amp.

[jg]

How is the audio amplifier controlled? That is outboard of the AD1888, IIRC.

[kimquirk]

Moving to next software release, Trial-2.

[jg]

Note that in a sugar environment, most of the time you can know whether or not you are the preferred activity by the normal X visibility notification mechanisms.

Those should be used in preference to sugar mechanism where possible. This limits the dependencies to sugar to where it is actually needed.

[jg]

We think this is mostly temporarily resolved in Trial-3. Getting tests into Tinderbox is worthwhile.

[cjl]

Is there any point in keeping tinderbox bugs open?

[cjb]

No, thanks.