📎 AI Summary:
The thread discusses the issue of a notebook automatically disabling its built-in microphone when a headset earphone is plugged in, preventing the use of both together. The original poster asks if this behavior is normal and if there's a way to enable the microphone despite the presence of the headset. A respondent explains that the system typically treats the earphone and microphone as a combined device, and that using different hardware or drivers might affect this behavior. The overall sentiment suggests this is a common hardware or driver limitation rather than a bug.

pstein

Extraordinary Member
Joined
Mar 20, 2010
Messages
454
Thread Author #1
As you know many (new) notebook have built- in speakers and a built-in microphone.
In addition they offer plugins für a separate headset (with microphone as well).

Now assume the user plugs in only one cable (=the one for listening) of the headset into the notebook
but leave the other cable (=the one for the damaged microphone) out.

The user wants to use the combination headset earphone + notebook microphone.

Unfortunately this seems NOT to work.

As soon as the earphone headset cable is pluged in the notebook microphone is automatically disabled.

Is this correct?

Is there a trick to enable the built-in microphone anyway?

Peter
 

Solution
The computer has no way to know that your mic and earphones are both mounted on the same headband. They should be independent. A simple way to check is find some earphones or speakers that you can plug in and see if you get the same problem. The only thing I could see causing that by design is if you are using a headset with its own device driver, and that driver decides that your headset is connected based on the earphone jack.

Fixer1234

Senior Member
Joined
Aug 3, 2012
Messages
481
The computer has no way to know that your mic and earphones are both mounted on the same headband. They should be independent. A simple way to check is find some earphones or speakers that you can plug in and see if you get the same problem. The only thing I could see causing that by design is if you are using a headset with its own device driver, and that driver decides that your headset is connected based on the earphone jack.
 

Solution