Bug 12985 - Audible hiss using headphone jack
: Audible hiss using headphone jack
Status: VERIFIED WONTFIX
Product: SB Radio
Classification: Unclassified
Component: Audio
: Include FW version in comment
: PC Windows XP
: P4 normal (vote)
: 7.4.0
Assigned To: Caleb Crome
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-22 14:20 UTC by Mickey Gee
Modified: 2009-10-14 09:02 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mickey Gee 2009-07-22 14:20:36 UTC
When music is not playing or paused, a loud hiss is heard on the headphone output jack. Tried with 3 different headphones with same result.


Using firmware r6749.
Comment 1 Caleb Crome 2009-07-22 14:21:47 UTC
Is this more or less than with Boom?  Fab4?
Comment 2 Mickey Gee 2009-07-22 14:28:24 UTC
It's LOT more than Fab4 and Boom. I have a PB1. Let me check if it's only my unit.
Comment 3 Mickey Gee 2009-07-22 15:49:44 UTC
Tried it out on a PB2 unit. No audible hiss.
Comment 4 Caleb Crome 2009-07-22 16:36:42 UTC
Ahhhhhh, I forogt about this one.  This isn't so invalid after all.

The PB1 units had HPLCOM tied to HPRCOM, and if the dac was configured wrong, it would do this (and draw a ton of current).

Richard, did you just do something with HPLCOM and HPRCOM configuration?

-Caleb
Comment 5 Richard Titmuss 2009-07-27 01:09:52 UTC
Reset priority before triage.
Comment 6 Richard Titmuss 2009-07-27 01:39:31 UTC
Yes, to fix the headphone pop on power on. Do we need to make that dependent on the hw revision? When can we retire the PB1's?
Comment 7 Caleb Crome 2009-07-27 07:23:22 UTC
Hmm, that's strange.  the 'COM' signals should just be disabled all together.  You're saying you need them turned on to reduce the pop?
Comment 8 Richard Titmuss 2009-07-28 04:25:41 UTC
What should the register settings be, and I'll verify they are set correctly for the PB1 boards. The COM are disconnected on PB2 and onwards so should not matter, right?
Comment 9 Caleb Crome 2009-07-28 22:24:21 UTC
This only affects PB1 units.
Comment 10 Ben Klaas 2009-08-26 07:50:19 UTC
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Comment 11 Caleb Crome 2009-10-14 09:02:21 UTC
wontfix because we're going to discontinue pb1 units anyway.