There are two things: 1. The incorrect named "Droid source primary" element which is something we could easily fix from pulseaudio by just adding a better description for the source.
2. The null input should be never listed as its useless for the user and just used internally to allow proper routing for Bluetooth audio devices. Whoever (I suspect webbrowser-app) lists the devices here needs to filter that device out. There are a number of different hings for the source element we can use for that Source #3 State: SUSPENDED Name: source.fake.sco Description: Null Input Driver: module-null-source.c Sample Specification: s16le 1ch 8000Hz Channel Map: mono Owner Module: 8 Mute: no Volume: mono: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: n/a Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Null Input" device.class = "abstract" device.icon_name = "audio-input-microphone" Formats: pcm ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560068 Title: Settings report incorrect Microphone device names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1560068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs