Internal Mic Fix?

[dcz]

@niceguy

how are the chances that a wired headset (like the one that came with the phone) will work?

I believe someone on the team is investigating this right now.

[guru]

@guru

@Loki

Once installed the app will be available from the main app view (after selecting to show all apps) under the name “PulseAudio Volume Control”. After launching the app, it’s quite straight forward…

1. Choose the “Input Devices” tab
2. Unlink the Left/Right gain controls to give independent control of each
3. Disable top internal mic by setting “Front Left” gain to 0%

See below image for visual guide…

I’ve configured exactly this and I can even see moving the audio level bar below the sliders following the noise, but when I call some other phone, for example my other mobile, only silence is sent to the other device. Why?

At the end, I moved away the existing (and perhaps) messed-up configuration with

mv ~/.config/pulse ~/.config/pulse.broken

rebooted, which created a new ~/.config/pulse clean configuration, run again the above steps 1. … 3. and audio in calls worked fine again. It’s a pity that the configuration is stored in some binary files:

$ ls ~/.config/pulse 
9b43caf3619f49f8ba467ec270970f44-card-database.tdb
9b43caf3619f49f8ba467ec270970f44-default-sink
9b43caf3619f49f8ba467ec270970f44-default-source
9b43caf3619f49f8ba467ec270970f44-device-volumes.tdb
9b43caf3619f49f8ba467ec270970f44-stream-volumes.tdb
cookie

so we can’t find out with just diff what the problem was.

[irvinewade]

@guru

so we can’t find out with just diff what the problem was

python3
import tdb
t = tdb.open('9b43caf3619f49f8ba467ec270970f44-stream-volumes.tdb')
print(list(t.keys()))

or

sudo apt install tdb-tools
tdbdump 9b43caf3619f49f8ba467ec270970f44-stream-volumes.tdb

[guru]

tdbdump 9b43caf3619f49f8ba467ec270970f44-card-database.tdb
{
key(29) = "alsa_card.platform-sound-wwan"
data(59) = "B\04NL\00\00\00\02tanalog-input\00r\00\00\00\00\00\00\00\00Ntanalog-output\00r\00\00\00\00\00\00\00\00NNN"
}
{
key(24) = "alsa_card.platform-sound"
data(132) = "B\04NL\00\00\00\05t[Out] Headphones\00r\00\00\00\00\00\00\00\00Nt[Out] Speaker\00r\00\00\00\00\00\00\00\00Nt[Out] Handset\00r\00\00\00\00\00\00\00\00Nt[In] Headset\00r\00\00\00\00\00\00\00\00Nt[In] Mic\00r\00\00\00\00\00\00\00\00NNN"
}

hmmmm???

[Loki]

@guru

At the end, I moved away the existing (and perhaps) messed-up configuration with

mv ~/.config/pulse ~/.config/pulse.broken

Although we did identify a couple of user config settings related to the actual modem that were set at non-default values there was clearly one or more others that remained a little more elusive causing the issue to remain.

I would have preferred to pinpoint the actual user config setting(s) responsible, but, nuking the config and having pulseaudio rebuild the user config from scratch was a quick and simple fix.

[guru]

@Loki

I would have preferred to pinpoint the actual user config setting(s) responsible, but, nuking the config and having pulseaudio rebuild the user config from scratch was a quick and simple fix.

I haven’t removed the broken config, it’s still there…

[Loki]

I’d imagine that much if not all of the config settings and values in the config files will also available via pactl and pacmd.

For example, pactl list without any further arguments will dump a lot of info on the loaded modules, sources, sinks and streams in a readable format. If you dumped that output to a file for both the working and broken configs that may give you something to work with.

[irvinewade]

@guru

hmmmm???

Yes. I don’t know either.

However, if you were to take that output, probably format it up a bit better, then you could at least diff to get an idea of what changed even if you can’t interpret the values exactly.