Ubuntu Touch is no longer supported.
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Won't Fix
--
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
** Tags added: pulse-touch
--
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.
** Changed in: oxide
Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
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:
Additionally, the device names should be localized, as they are user-
facing strings.
--
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
@David: Not sure, but you can take a look at
$ pactl list sources
That lists all properties pulse reports for the source devices. However
from the Android side (that is where we're reading the list of available
devices from) we only get 'primary' as the name of the source and not
further informat
Oxide is responsible for listing the audio capture devices. See
https://bazaar.launchpad.net/~oxide-
developers/oxide/oxide.trunk/view/head:/qt/core/api/oxideqmediacapturedevices.cc#L163
for implementation details.
Chromium exposes the following attributes for each device:
- id (string)
- name
@morphis: Is there a better API to call to get the list of "user"
visible audio inputs instead? or a well-known filter to apply to get
those. I image most apps will want that list, whereas system level
components will be the only one interested in the full extent list.
--
You received this bug no
** Package changed: webbrowser-app (Ubuntu) => oxide
--
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 thi
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 rout
10 matches
Mail list logo
