This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1907891 - Lenovo T14 (Intel CPU) audio BT headset mic issues
Summary: Lenovo T14 (Intel CPU) audio BT headset mic issues
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pulseaudio
Version: 8.3
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: 8.0
Assignee: Wim Taymans
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-15 13:15 UTC by jloscar
Modified: 2024-01-10 04:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-11 17:39:46 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
Lenovo T14 on RHEL 8.3 (17.11 MB, application/x-xz)
2020-12-15 13:15 UTC, jloscar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-3054 0 None Migrated None 2023-09-11 17:38:26 UTC

Description jloscar 2020-12-15 13:15:04 UTC 
Created attachment 1739332 [details]
Lenovo T14 on RHEL 8.3

Description of problem:
Lenovo T-14 (Intel CPU) with RHEL 8.3 has bluetooth headset problems

- Sometimes the headset works in headset mode while sometimes it is just a headphone (no microphone)
- device is reported as connected but not available in the audio settings

How reproducible:
Frequently

Steps to Reproduce:

1. There are two audio profiles for the this headset to choose from, "High Fidelity Playback" and "Headset Head Unit". In both cases the speakers work but there is no microphone for the  "Headset Head Unit" profile. There is the internal microphone of T14 available

2. After suspend/resume the BT headset is not reconnected. It needs to be paired manually.

Actual results:
No Mic option 

Expected results:
Have the Mic available to use  

Additional info:
Attaching an SOSReport
Comment 1 jloscar 2021-01-28 01:37:08 UTC 
It's been over a month and I have seen no movement on this ticket.

If there additional data or information needed to help move this forward, please let me know.

-Joshua
Comment 2 jloscar 2021-06-05 00:17:38 UTC 
Is there any new update on this?

Is there better support coming to linux bluetooth stack because things are switching to pipewire?

Is there additional information that you need?


-Joshua
Comment 4 jloscar 2021-07-28 00:39:44 UTC 
The customer is also having bluetooth issues with Lenovo T14 with Ryzen7 Pro and RHEL8.4

I am attaching it to this same BZ.

-Joshua
Comment 5 jloscar 2021-10-19 14:01:27 UTC 
It's been over 3 month and I have seen no movement on this ticket.

If there additional data or information needed to help move this forward, please let me know.

-Joshua
Comment 6 jloscar 2021-11-09 11:17:03 UTC 
We are another month in, and I am going to now ask if there is a status update.

My Customer will be trying RHEL 9 Beta aswell, so I'll ask them to test this on current RHEL 8.5 and RHEL 9, and I'll upload the sosreports.

This is a pain point for my customer, and I'd appreciate an update to let them know the status.

-Joshua
Comment 7 jloscar 2022-03-01 00:43:45 UTC 
I haven't heard anything back on this case.

I have had the customer try again on RHEL 8.5, 
and it still has the same issue.

Uploading latest SOSReport.

Is there any additional info that you need?
Comment 8 jloscar 2022-03-01 00:44:15 UTC 
I haven't heard anything back on this case.

I have had the customer try again on RHEL 8.5, 
and it still has the same issue.

Uploading latest SOSReport.

Is there any additional info that you need?
Comment 9 Wim Taymans 2022-03-01 12:43:19 UTC 
This needs more debugging.

In general, bluetooth device support depends on the right adapter, adapter firmware, kernel version, kernel tweaks, bluez version and tweaks, audio server tweaks, device firmware and device hardware and 
also any combination of those.

The best option to make this work is to try to upgrade to the latest versions of the kernel and bluez.

You could also try to clear the BlueZ cache: Delete all files and directories under /var/lib/bluetooth/ and systemctl restart bluetooth. This forgets all devices and you need to pair devices again.

Alternatively, a log of the bluetooth traffic could reveal the problem: 

1. power off all devices
2. run sudo btmon >log in a terminal
3. Connect device
4. Do the problematic operation
5. Ctrl-C btmon.
6. attach the log file here.
Comment 10 jloscar 2022-05-05 16:57:53 UTC 
Hello Wim,

I had the customer test and they reported back:


1. When switching from HSP to A2DP the audio quality remains bad.
2. After suspend/resume the BT headset was reconnected automatically, this has failed in the past. Before suspend i switched from HSP to A2DP without audio quality improvement but after resume the audio quality was great. But as soon as i switched to HSP and A2DP the quality was bad again.


I am also attaching the 2 log files you asked for.

-Joshua
Comment 13 jloscar 2022-05-10 14:16:34 UTC 
Do we have a status update on this case?

-Joshua
Comment 14 jloscar 2022-05-17 13:19:52 UTC 
I had the customer grab the log files you asked for and I've uploaded them to the BZ as a private attachment.

Do we have a status update on this case?

-Joshua
Comment 15 jloscar 2022-05-24 18:32:16 UTC 
Hello Wim,

Did the 2 logs files have the data you needed?

Do you have additional data that needs to be gathered?

Do we have any status update?

-Joshua
Comment 19 gopal krishna tiwari 2022-06-15 12:56:29 UTC 
jloscar,

Wondering if you can check with latest RHEL-8.6 kernel (No change for RHEL-8.7) and bluez-5.63 (latest version for RHEL-8.7) where we have fixed issue related to headset suspend and resume ?

It would be great if you can capture the btmon and bluez logs for the same as well 

How to bluez logs ? 

~~~

enable debugging by adding a -d after

ExecStart=/usr/libexec/bluetooth/bluetoothd

in /usr/lib/systemd/system/bluetooth.service

Save, then:

$ systemctl daemon-reload
$ systemctl restart bluetooth


Now you get your information in /var/log/syslog
or 
journalctl --unit=bluetooth -f

~~~~

2) Run btmon in different terminal and try to suspend and resume. 

Thanks
Gopal
Comment 24 gopal krishna tiwari 2022-08-03 13:03:23 UTC 
(In reply to jloscar from comment #22)
> Created attachment 1894006 [details]
> New SOSReport Lenovo T495 with RHEL8.6.
> 
> Customer Uploaded new SOSReport.
> 
> d120807:Desktop$ uname -r
> 4.18.0-372.9.1.el8.x86_64
> d120807:Desktop$ rpm -qa | grep bluez
> bluez-obexd-5.56-3.el8.x86_64
> bluez-libs-5.56-3.el8.x86_64
> bluez-5.56-3.el8.x86_64
> 
> Customer don' t see any improvement.
> 
> There is no reconnect on resume and in headset mode it is still mono and the
> sound is distorted. 
> 
> Customer enabled bluethooth debugging before testing.
> 
> If more info is needed please let me know

Hi Jloscar, 

Wondering if the bluez updated version for 8.7 is being verified as mentioned in comment #20? 

We need bluez logs as mentioned in comment #19. I can try and check from bluez/bt kernel side. Sos report doesn't capture bluez debug logs unless specified.   

let me know if you see any concern in capturing the data or issue with package ?

Thanks
Gopal
Comment 27 jloscar 2022-12-13 14:42:39 UTC 
I had the customer try on RHEL 8.7 and the issues is still there.

I've attached the file above.

This case has been open for 2 years,
Please advise on how we can move forward.

-Joshua
Comment 30 gopal krishna tiwari 2022-12-20 06:29:59 UTC 
Just to summarize the issue, please correct me, suspend/resume is working ? . I think we have problem with audio quality here from HSP to A2dp ?.

Looking at the problem we are hitting some sync issues. Wondering if possible can we try once after performing following

~~~
Before suspend i switched from HSP to A2DP without audio quality improvement but after resume the audio quality was great. But as soon as i switched to HSP and A2DP the quality was bad again.

~~~

Restart pulseaudio ?. It will help in understanding if its the bluez or pulseaudio is having issue. This is more of sync issue. 

Another please also share/capture the bluez logs in parallel.  

Thanks
Gopal
Comment 34 RHEL Program Management 2023-09-11 17:32:44 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 35 RHEL Program Management 2023-09-11 17:39:46 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 36 Red Hat Bugzilla 2024-01-10 04:25:04 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.