[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I installed pulseaudio-modules-bt and it does give some new options for sound output and possibly better sound, but microphone sound quality was still iffy. Recorded sound on Audacity seemed better and was slightly louder (according to the DB meter), but a test call on Microsoft Teams was still muffled and unintelligible. I have ordered a Avantree DG80 dongle (which makes the bluetooth connection externally and appears to linux as usb audio) and will hopefully be able to continue working with that, but I would love to see this problem resolved in pulseaudio. For the record, I am using a Sony WH-1000XM4 headset on PopOS 20.10 running on a System76 Darter Pro. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I can't seem to get the DG80 working correctly under PopOS 20.10. It works great for listening to music (though that worked directly on bluetooth without issues) but I can't seem to get the correct mode for talk. Since you say you have success with it, I will play with it some more before returning it and see if I can get it set up properly. It is probably some kind of configuration thing on my end, but I was hoping it would solve my microphone problems. As it stands, my best option is using the headset with my phone for Teams calls--the sound works perfectly there. If I find the right magic, I'll reply again here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I think the problem was in the headphones. I found I was having trouble on my phone as well. I contacted Sony support and they had me try a soft reset of the headset, which seems to have restored function. I am still getting bad mic sound on bluetooth, but I think it is just the low quality sound on this thread and not the completely muffled sound I was getting before. I will try reconnecting to the DG80 now and see if it is any better. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1110787] Re: VPN tunnel connections are not properly setting MTU values
I am still seeing this problem in 14.10, even installed fresh on a new
laptop. I have found a workaround that takes care of the problem
automatically, though. There is a 1412 mtu hardcoded in /etc/vpnc/vpnc-
script, but that may not be relevant to network manager so I didn't mess
with that script. The NetworkManager man page notes that any scripts
placed in /etc/NetworkManager/dispatcher.d will run when network
connections go up and down, and that they will receive the name of the
interface and the action as parameters to the script. So I placed the
following script in that directory under the name "70vpnMtuCorrection"
(the scripts run in alpha order, and there was already one more there so
I wanted this one to run later...but you can call it anything else you
like and it should still work). The script needs to be owned by root and
executable by all (so use sudo to save it and execute a "chmod a+x" on
the file"). The script determines if the tun0 interface is coming up, if
we have a wlan0 connection, calculates the necessary mtu value, and
resets it if the MTU value needs to be decreased. This seems to be
handling my issue, but I would still prefer to see that it is handled
properly by network manager in the first place. But if you are having
the same problem, this should remove a pesky annoyance like it is doing
for me:
/etc/vpnc/vpnc-script/70vpnMtuCorrection:
#!/bin/bash
TUN0_INTERFACE_NAME="tun0"
WLAN0_INTERFACE_NAME="wlan0"
VPN_UP_ACTION_NAME="vpn-up"
MTU_DIFFERENCE=78
INTERFACE_NAME=${1}
ACTION=${2}
if [ "${INTERFACE_NAME}" != "${TUN0_INTERFACE_NAME}" ]
then
exit 0
fi
if [ "${ACTION}" != "${VPN_UP_ACTION_NAME}"]
then
exit 0
fi
#Make sure we have a current TUN0 entry before we continue.
CURRENT_TUN0_MTU=`sudo ip link list | grep "${TUN0_INTERFACE_NAME}:" | sed -r
"s/.*mtu ([0-9]+).*/\1/"`
if [ "${WLAN_MTU}" == "" }
then
exit 0
fi
#Also make sure we have a current WLAN0 entry
WLAN_MTU=`sudo ip link list | grep "${WLAN0_INTERFACE_NAME}:" | sed -r "s/.*mtu
([0-9]+).*/\1/"`
if [ "${WLAN_MTU}" == "" }
then
exit 0
fi
NEW_TUN0_MTU=$((${WLAN_MTU} - ${MTU_DIFFERENCE}))
if [ ${NEW_TUN0_MTU} >= ${CURRENT_TUN0_MTU} ]
then
exit 0
fi
ip link set ${TUN0_INTERFACE_NAME} mtu ${NEW_TUN0_MTU}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1110787
Title:
VPN tunnel connections are not properly setting MTU values
Status in NetworkManager:
New
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
I regularly connect to a cisco anyconnect vpn using vpnc through the
network manager. I am often at various different location using wifi,
including connecting via wifi to a cellular hotspot. Usually, when
connecting to a WIFI connection the MTU value (on the wifi connection)
is 1500. When connecting to the vpn, the MTU value of the tun0
connection is set automatically and it usually sets itself to
something like 1412. This works with no problem.
When the wifi connection has a lower MTU value (and the cellular
hotspot usually has an MTU of 1430, as do connections in various
coffee shops), the tun0 connection still sets itself to 1412. For
read-intensive operations (e.g. accessing websites and downloading
pages, pulling from a subversion repository) there is no apparent
problem. But when attempting to post to a web page (for instance,
writing a bug report in bugzilla) or commit to a repository over the
VPN, the connection will fail. The MTU value for a VPN connections
seems to want to be 78 less than the MTU value of the connection that
it is working over, and having MTU greater than this causes the upload
failures.
I use the VPN via the network manager (using network-manager-vpnc and
network-manager-vpnc-gnome). I am able to work around the issue by
setting the MTU value of the VPN connection manually from the command
line after connecting with the following command:
sudo ifconfig tun0 mtu 1330
It is tedious to do this each time, but it does allow me to
successfully upload or commit when connected. (I also find that RDP
connections fail much less often when the MTU is set correctly.) I
should note that I pick an MTU value that is 100 less than the MTU
value of the WIFI connection--it should be 78 but I opt for the easier
math and don't really notice the difference.
And for those that don't know, you can find the current MTU value of
your connections by issuing the "ifconfig" command.
If you do not have access to a cellular hotspot or other wifi
connection that has a low MTU value, it is likely you can replicate
this issue by manually setting the primary network connection's MTU
value to 1430 (using the above command) though I have not tried to
replicate it under these conditions.
Ideally, the VPN connection would properly calculate an appropriate
MTU v
[Touch-packages] [Bug 1583821] [NEW] Applications shuffling around on desktops after screen lock
Public bug reported: I use multiple desktops to organize open applications. Also, I am currently using multiple monitors. If I arrange my applications (e.g. Chrome on the laptop screen of desktop one, Geany on the attached monitor on desktop 1, another chrome on the laptop screen of desktop 2, another app on the attached monitor on desktop 2) and then lock the screen, when I unlock all of the applications have moved around. Sometimes they all move to desktop 1, sometimes they are resized and half off the screen. But they are rarely on the same screen and desktop that I left them on. This is new behavior since the latest version upgrade. Previously, applications stayed on the screens where I left them. Some requested info: $ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu3 Candidate: 1:7.7+13ubuntu3 Version table: *** 1:7.7+13ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 19 17:17:20 2016 DistUpgraded: 2016-04-29 20:29:44,172 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978] InstallationDate: Installed on 2014-12-03 (532 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: LENOVO 80H1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-30 (19 days ago) dmi.bios.date: 09/28/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B9CN12WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Edge 15 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Edge 15 dmi.modalias: dmi:bvnLENOVO:bvrB9CN12WW:bd09/28/2014:svnLENOVO:pn80H1:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoEdge15: dmi.product.name: 80H1 dmi.product.version: Lenovo Edge 15 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue May 17 10:15:01 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1103 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1583821 Title: Applications shuffling around on desktops after screen lock Status in xorg package in Ubuntu: New Bug description: I use multiple desktops to organize open applications. Also, I am currently using multiple monitors. If I arrange my applications (e.g. Chrome on the laptop screen of desktop one, Geany on the attached monitor on desktop 1, another chrome on the laptop screen of desktop 2, another app on the attached monitor on desktop 2) and then lock the screen, when I unlock all of the applications have moved around. Sometimes they all move to desktop 1, sometimes they are resized and half off the screen. But they are rarely on the same screen and desktop that I left them on. This is new behavior since the latest version upgrade. Previously, applications stayed on the screens where I left them. Some requested info: $ lsb
