-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection refused for BLE_ATH-M50xBT #47
Comments
I'm not sure what's the reason. Disconnect your device first, then run the script again while disconnected. This works for some devices. |
did you try to rerun the script @Vrizkag? like in executing the same command twice?
|
Got the same problem using different device, let me know if you rather have a separate issue for this 876964 headset. ( 876964 is this headset model name 🤷 )
With the headset connected (script exits in less than 1s, it returns this error every time I run it):
With the headset disconnected
|
+1 The command journalctl -f -o cat /usr/bin/gnome-shell prints out:
|
I have the same issue with my headset, I'm on Ubuntu 20.04.2 |
I have the same issue on Ubuntu (5.4.0-89-generic #100-Ubuntu SMP) with a Bowers & Wilkins headphone. Battery level is reported correctly after a reboot, but after the first suspend I get the same behaviour ("Errno 111") as described above. Oh, and I found these lines repeated over and over in /var/log/syslog: So, actually the battery level is correctly reported by the device. Perhaps the deprecate warning is not correctly interpreted by |
I can confirm that after a restart, battery status is reported correctly |
bluetooth_battery 00:0A:45:0B:5C:5C
00:0A:45:0B:5C:5C is offline [Errno 111] Connection refused
Then i tried this:
bluetooth_battery 00:0A:45:0B:5C:5C.1
00:0A:45:0B:5C:5C is offline [Errno 16] Device or resource busy
Before that, I went into
bluetoothctl
to get the correct addressThe text was updated successfully, but these errors were encountered: