#StackBounty: #windows-7 #audio #bluetooth #speakers Not able to receive sound from my laptop unless wearing earphones

Bounty: 50

I don’t know what has happened to my Windows 7, but I am not able to hear any volume until I wear earphones. The hearing device is Speaker. Another thing is that when I don’t wear earphones and open anything like YouTube then it shows like this

enter image description here

If I am not wrong this means that the sound is getting produced, but I am not able to hear it still. I have to wear an earphone to hear any sound from the laptop however the earphone is little damaged now, so I wanted to hear sound from the speaker only. The speaker of my computer is in-built. I have set the voice too at good level that I can hear.

enter image description here

So as you can see the amount of sound coming has been set high by me. Another thing is that like when I wear earphones and choose the sound giving speaker as Speakers/HP the sound can be heard without earphone too but sometimes the sound is loud sometimes mere however this voice is doesn’t come now as my earphone are damaged. I don’t want to buy a new earphone as already many earphones have been damaged by me. Maybe there might be some small mistake by me like once I was getting disturbed because of text cursor scrolling me down but then I realized that I had turned on the caret browsing so similarly maybe there might be a small mistake here too.

enter image description here

As you can see these all are speakers of my computer and I am not able to hear any until I wear a well working earphone. I also tried running the troubleshoot but it showed that there is no error the device is working fine. I tried uninstalling and then again installing the drivers but in vain.

enter image description here

These are the speakers device present in my device manager. And from the first image you can see that my sound is not muted.

enter image description here

enter image description here

Even I have tried also tried updating my BIOS system but in vain. So please can anyone help me resolve this problem? Let me specify you that this is some software problem according to me because if speakers weren’t working then how would wearing working earphones made the speaker work but as soon as you plug off the earphones the speakers don’t work. Pls don’t suggest to buy me a speaker like These as I frequently take my laptop from one place to another so working with carrying speakers from one place to another would be quite difficult for me. Plus using external speakers at work doesn’t seem a good idea. My laptop also gets connected to a Bluetooth but Bluetooth doesn’t give any voice however the Bluetooth gives voice with other laptops and devices. So pls suggest me how to resolve this software issues? Or do you still think it is a hardware issue? I know this is a duplicate question like Not able to receive sound from my laptop unless wearing earphone but in that no one was answering and having less number of reputation I could not risk my reputation by starting bounties so that is why I asked a duplicate question. Apologies for grammar mistakes


Get this bounty!!!

#StackBounty: #20.04 #sound #kubuntu #bluetooth #pulseaudio Stop application/pulse audio changing Bluetooth Profile when joining a call

Bounty: 50

I have a pair of bluetooth headphones, and a separate microphone, so I have the headphones set to use the "High Fidelity Playback (A2DP Sink)" Profile, so the audio quality isn’t trash. When, however, I join calls on some conference software, such as Microsoft Teams, the profile is automatically changed from A2DP Sink to HSP/HFP, causing the quality to turn into as if I’m using a mobile phone from the 1980’s.

I also, at the same time, wanted to stop application’s audio being muted when I join a call, and I discovered a solution to that in the question How to stop gnome from muting my music? I assume, therefore, there is likely a similar setting in Pulse Audio to stop it changing the profile when I join a call, but of searchfu hasn’t yielded any results and the linked blog in the above answer is a dead link. Does anyone know which I need to (un)comment or amend to stop it changing the profile? As I am using a separate microphone, then changing the profile makes no sense, as the headphone’s inbuilt mic shouldn’t be being used.

More odd is that if I join to call, change all the settings back (including the input volume as for some reason it resets that too) and then rejoin the call it doesn’t change the settings again; it is only the first time I join a call that boot cycle. Also, odd again, when I turn the headphones on for the first time in a boot cycle, they will connect using A2DP sink, and will continue to do so if I power them off and on. If, however, I join a call (which results in the profile change), and then later, after fixing the settings, power the headphones off, and then on again later they will connect using HSP/HFP even though they were using A2DP Sink when powered off here. This suggests it’s not Teams that’s changing the profile but likely PulseAudio.

Does anyone know how I can stop PulseAudio making automatic choices on what profile to use when I join a call for a Bluetooth device?


Get this bounty!!!

#StackBounty: #20.04 #bluetooth Bluetooth not finding any device.20.04

Bounty: 50

Hello

I have Ubuntu 20.04 and my bluetooth works but doesnt find any device and also not visible to any other device. I have installed blueman.Yeah and please, please don’t give me link to other questions on this site because they don’t work.(I have disabled the bluetooth device from Windows) and checked rf kill list and also enabled bluetooth from bios.

Output of command :- service bluetooth status

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2021-01-21 11:18:56 IST; 2h 39min ago
       Docs: man:bluetoothd(8)
   Main PID: 5147 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4514)
     Memory: 2.1M
     CGroup: /system.slice/bluetooth.service
             └─5147 /usr/lib/bluetooth/bluetoothd

Jan 21 11:18:56 Piyush-X55C bluetoothd[5147]: Bluetooth daemon 5.53
Jan 21 11:18:56 Piyush-X55C systemd[1]: Started Bluetooth service.
Jan 21 11:18:56 Piyush-X55C bluetoothd[5147]: Starting SDP server
Jan 21 11:18:56 Piyush-X55C bluetoothd[5147]: Bluetooth management interface 1.17 initialized
Jan 21 11:19:00 Piyush-X55C bluetoothd[5147]: Endpoint registered: sender=:1.66 path=/MediaEndpoint/A2DPSink/sbc
Jan 21 11:19:00 Piyush-X55C bluetoothd[5147]: Endpoint registered: sender=:1.66 path=/MediaEndpoint/A2DPSource/sbc
Jan 21 13:48:16 Piyush-X55C bluetoothd[5147]: Endpoint unregistered: sender=:1.66 path=/MediaEndpoint/A2DPSink/sbc
Jan 21 13:48:16 Piyush-X55C bluetoothd[5147]: Endpoint unregistered: sender=:1.66 path=/MediaEndpoint/A2DPSource/sbc
Jan 21 13:48:17 Piyush-X55C bluetoothd[5147]: Endpoint registered: sender=:1.155 path=/MediaEndpoint/A2DPSink/sbc
Jan 21 13:48:17 Piyush-X55C bluetoothd[5147]: Endpoint registered: sender=:1.155 path=/MediaEndpoint/A2DPSource/sbc

Output of sudo btmgmt info:-

Index list with 1 item
hci0:   Primary controller
    addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x000000
    supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys 
    current settings: powered bondable ssp br/edr 
    name Piyush-X55C
    short name 

Output of :- sudo btmgmt find
Unable to start discovery. status 0x0c (Not Supported)

When I tried to start discovery by using command :- bluetoothctl
the output is :-

Agent registered
[bluetooth]# scan on
[bluetooth]# discoverable on
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# discoverable on
Changing discoverable on succeeded
Failed to set discoverable on: org.freedesktop.DBus.Error.NoReply
[bluetooth]# 


Get this bounty!!!

#StackBounty: #20.04 #bluetooth #bluez Bluetooth error in Ubuntu 20.04

Bounty: 50

Hello
I am trying to make my adapter discoverable but it displays me this:- after bluetoothctl

[bluetooth]# scan on
[bluetooth]# discoverable on
Changing discoverable on succeeded
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# 

Output of command :- lspci -knn | grep Net -A3; lsusb

02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290]
    Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055]
    Kernel driver in use: rt2800pci
    Kernel modules: rt2800pci
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Get this bounty!!!

#StackBounty: #drivers #20.04 #bluetooth Bluetooth not working with Ralink RT3290 In Ubuntu 20.04

Bounty: 50

I have Ubuntu 20.04 and my Bluetooth (RT3290) was not working so I reinstalled its driver using GDEBI package installer. After I tried command sudo modprobe rtbth it started working but it does not do anything, no device is visible and also my laptop is not also visible to any device.

When I try service bluetooth status it displays me this

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2021-01-18 18:39:32 IST; 40s ago
       Docs: man:bluetoothd(8)
   Main PID: 15857 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4514)
     Memory: 2.1M
     CGroup: /system.slice/bluetooth.service
             └─15857 /usr/lib/bluetooth/bluetoothd

Jan 18 18:39:32 Piyush-X55C systemd[1]: Starting Bluetooth service...
Jan 18 18:39:32 Piyush-X55C bluetoothd[15857]: Bluetooth daemon 5.53
Jan 18 18:39:32 Piyush-X55C systemd[1]: Started Bluetooth service.
Jan 18 18:39:32 Piyush-X55C bluetoothd[15857]: Starting SDP server
Jan 18 18:39:32 Piyush-X55C bluetoothd[15857]: Bluetooth management interface 1.17 initialized
Jan 18 18:39:35 Piyush-X55C bluetoothd[15857]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSink/sbc
Jan 18 18:39:35 Piyush-X55C bluetoothd[15857]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSource/sbc

Output of rfkill list

0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

Now the bluetooth is started but not finding any device and also visible to any other device.

Output of sudo btmgmt info

Index list with 1 item
hci0:   Primary controller
    addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x000000
    supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys 
    current settings: bondable ssp br/edr 
    name Piyush-X55C
    short name 


Get this bounty!!!

#StackBounty: #bluetooth #bluez RE: Modifying bluetooth scan parameters via btmgmt

Bounty: 100

I have the same problem of @Hias about this topic:
https://unix.stackexchange.com/questions/420978

The more interesting answer is:
"modify bluetooth kernel module, set any discoveryFilter using Bluez (i.e.: RSSI -127)."

The answer is not clear to me.
Where is the "bluetooth kernel module"?
That is, what is the directory?

In the output of this command:

sudo btmgmt --index 1 find

Between "hci1 type 7 discovering on" and "hci1 type 7 discovering off" there is a time of 11 seconds (I counted in mind).
How to change this time?

If –timer parameter is 5 for example, i must wait other six second to execute the command, otherwise it gives me the output of busy: 5+6=11


Get this bounty!!!

#StackBounty: #drivers #20.04 #bluetooth Bluetooth In Ubuntu 20.04

Bounty: 50

Hello

I have Ubuntu 20.04 and my bluetooth (RT3290) was not working so I reinstalled its driver using GDEBI package installer.After I tried command sudo modprobe rtbth it started working but it does not does anything no device is visible in it and also my laptop is not also visible to any device.Also when I try service bluetooth status it displays me this

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2021-01-18 18:39:32 IST; 40s ago
       Docs: man:bluetoothd(8)
   Main PID: 15857 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4514)
     Memory: 2.1M
     CGroup: /system.slice/bluetooth.service
             └─15857 /usr/lib/bluetooth/bluetoothd

Jan 18 18:39:32 Piyush-X55C systemd[1]: Starting Bluetooth service...
Jan 18 18:39:32 Piyush-X55C bluetoothd[15857]: Bluetooth daemon 5.53
Jan 18 18:39:32 Piyush-X55C systemd[1]: Started Bluetooth service.
Jan 18 18:39:32 Piyush-X55C bluetoothd[15857]: Starting SDP server
Jan 18 18:39:32 Piyush-X55C bluetoothd[15857]: Bluetooth management interface 1.17 initialized
Jan 18 18:39:35 Piyush-X55C bluetoothd[15857]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSink/sbc
Jan 18 18:39:35 Piyush-X55C bluetoothd[15857]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSource/sbc

Output of rfkill list

0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

Now the bluetooth is started but not finding any device and also visible to any other device.

Output of sudo btmgmt info

Index list with 1 item
hci0:   Primary controller
    addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x000000
    supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys 
    current settings: bondable ssp br/edr 
    name Piyush-X55C
    short name 


Get this bounty!!!

#StackBounty: #18.04 #bluetooth #bluez Bluetooth service fails and freezes after some time in Ubuntu 18.04

Bounty: 100

Recently bluetooth is giving a lot of problems in 18.04.5 LTS (I have the latest update), specially when I awake the laptop (I have no TLP installed). I updated bluez and nothing changed. Bluetooth can’t connect and does not seem to power on, even after restarting the service.

I find these errors on red when I check the status of bluetooth after restart:

Version mismatch for sixaxis
Loading LTKs timed out for hci0
Failed to set mode: Failed (0x03)

I also get Failed to set power on: org.bluez.Error.Failed when I try to power on on bluetoothctl

Log

$ sudo service bluetooth restart
$ sudo service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2021-01-10 14:12:22 CET; 18s ago
     Docs: man:bluetoothd(8)
 Main PID: 13873 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─13873 /usr/lib/bluetooth/bluetoothd

Jan 10 14:12:22 toshiba systemd[1]: Starting Bluetooth service...
Jan 10 14:12:22 toshiba bluetoothd[13873]: Bluetooth daemon 5.50
Jan 10 14:12:22 toshiba systemd[1]: Started Bluetooth service.
Jan 10 14:12:22 toshiba bluetoothd[13873]: Starting SDP server
Jan 10 14:12:22 toshiba bluetoothd[13873]: Version mismatch for sixaxis
Jan 10 14:12:22 toshiba bluetoothd[13873]: Bluetooth management interface 1.14 initialized
Jan 10 14:12:22 toshiba bluetoothd[13873]: Endpoint registered: sender=:1.91 path=/MediaEndpoint/A2DPSource
Jan 10 14:12:22 toshiba bluetoothd[13873]: Endpoint registered: sender=:1.91 path=/MediaEndpoint/A2DPSink
Jan 10 14:12:24 toshiba bluetoothd[13873]: Loading LTKs timed out for hci0
Jan 10 14:12:32 toshiba bluetoothd[13873]: Failed to set mode: Failed (0x03)


$ sudo bluetoothctl
Agent registered
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Failed
*-usb:0
  description: Bluetooth wireless interface
  vendor: Intel Corp.
  physical id: 2
  bus info: usb@1:1.2
  version: 0.01
  capabilities: bluetooth usb-2.00
  configuration: driver=btusb maxpower=100mA speed=12Mbit/s

Note

To make it work again, I need to reboot.

This is really annoying because I’m using it for a bluetooth keyboard, and every time it fails to connect I have to switch to the laptop internal keyboard.


Get this bounty!!!

#StackBounty: #arch-linux #kde #bluetooth #plasma Bluetooth speaker not connecting on on Arch Linux / KDE Plasma

Bounty: 100

I’m running Arch Linux with KDE Plasma. When I try to connect to a wireless Bluetooth speaker through the KDE Plasma GUI, it fails.

Here’s the step-by-step I go thru in screenshots. I click "add device," then click the button that says the "PIN" matches. Note, since it’s a Bluetooth speaker, there is no PIN. So it doesn’t matter if I click "PIN matches" or the other option, the next screen says the setup has failed.

When I boot into Windows 10, it can connect to the speaker. My smart phone also connects to the speaker.

enter image description here

enter image description here

enter image description here

enter image description here


Get this bounty!!!

#StackBounty: #ubuntu #linux-mint #usb #bluetooth #power-management Prevent bluetooth keyboard from sleeping

Bounty: 50

After a few minutes of inactivity (10mn?), my keyboard go to sleep. I have to press a key, then, wait 5 long seconds before I can use it again…

First, some technical details :

  • Linux Mint 20 ulyana – Cinnamon (Ubuntu 20.04)
  • TP-Link UB400
  • Bluetooth USB dongle Microsoft Surface Ergonomic Keyboard

enter image description here
enter image description here

I paired the keyboard using bluetoothctl. This is the only way I found to enter passkey, since blueman-mananger didn’t ask for a passkey.

What I tried:

  • 1 – Checking the bios (motherboard: Asus H87-PLUS C2) for usb power management options. I found nothing
  • 2 – grub setting. Nothing changed.

commands:

sudo sed -i 's/GRUB_CMDLINE_LINUX_DEFAULT="[a-z ]*/& usbcore.autosuspend=-1/' /etc/default/grub    
sudo update-grub2    
reboot
cat /sys/module/usbcore/parameters/autosuspend
-1
  • 3 – Looking for power management in parameters. Found nothing.
    enter image description here
    enter image description here

  • 4 – Editing /etc/bluetooth/main.cfg. Still nothing.

config + reboot:

AutoEnable=true
FastConnectable=true

Any other ideas? Bluetooth options? USB options? Keyboard options? Maybe some kind of nondisturbing script + cron to keep it alive?

(I know "Mint is not Linux", but I hope you guys are more open minded compared to the askubuntu Stack Exchange community 🙂 )

EDIT:
I connected a bluetooth headphone. It looks like only the keyboard is falling asleep. The headphone is kept awake.
I cannot manually connect the keyboard from blueman manager (right clic + connect) when it’s sleeping, but I can connect the headphone.


Get this bounty!!!