Ticket #1421 (closed enhancement: wontfix)

Opened 7 years ago

Last modified 4 years ago

Verify that audio applications close the audio device when idle.

Reported by: jg Owned by: cjb
Priority: high Milestone: Future Release
Component: tinderbox Version:
Keywords: power Cc:
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description (last modified by rsmith) (diff)

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.

Change History

in reply to: ↑ description   Changed 7 years ago by rsmith

  • verified unset
  • description modified (diff)

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.

in reply to: ↑ description   Changed 7 years ago by rsmith

  • description modified (diff)

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.

  Changed 7 years ago by jg

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

  Changed 7 years ago by kimquirk

  • milestone changed from BTest-4 to Trial-2

Moving to next software release, Trial-2.

  Changed 7 years ago by jg

  • cc rsmith removed

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.

  Changed 7 years ago by jg

  • component changed from distro to tinderbox

  Changed 7 years ago by jg

  • milestone changed from Trial-2 to Trial-3

  Changed 7 years ago by jg

  • milestone changed from Untriaged to V1.1

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

  Changed 4 years ago by cjl

  • next_action set to never set

Is there any point in keeping tinderbox bugs open?

  Changed 4 years ago by cjb

  • status changed from new to closed
  • resolution set to wontfix

No, thanks.

Note: See TracTickets for help on using tickets.