Raspberry Pi 3 bluetooth stops working after a while
I use it to connect to a speaker (as a pulseaudio sink)
dmesg | grep Blue shows the following:
[ 14.034501] Bluetooth: Core ver 2.22
[ 14.034587] Bluetooth: HCI device and connection manager initialized
[ 14.034609] Bluetooth: HCI socket layer initialized
[ 14.034622] Bluetooth: L2CAP socket layer initialized
[ 14.034654] Bluetooth: SCO socket layer initialized
[ 14.048959] Bluetooth: HCI UART driver ver 2.3
[ 14.048974] Bluetooth: HCI UART protocol H4 registered
[ 14.048980] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 14.049211] Bluetooth: HCI UART protocol Broadcom registered
[ 14.324295] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.324304] Bluetooth: BNEP filters: protocol multicast
[ 14.324318] Bluetooth: BNEP socket layer initialized
[ 14.400493] Bluetooth: RFCOMM TTY layer initialized
[ 14.400517] Bluetooth: RFCOMM socket layer initialized
[ 14.400544] Bluetooth: RFCOMM ver 1.11
[ 1615.270230] Bluetooth: hci0 hardware error 0x00
[ 1619.500366] Bluetooth: hci0 command 0x1003 tx timeout
[ 1621.580373] Bluetooth: hci0 command 0x1001 tx timeout
[ 1623.660382] Bluetooth: hci0 command 0x1009 tx timeout
[ 1627.980418] Bluetooth: hci0 hardware error 0x00
[ 1630.060437] Bluetooth: hci0 command 0x1003 tx timeout
[ 1632.140793] Bluetooth: hci0 command 0x1001 tx timeout
[ 1634.220438] Bluetooth: hci0 command 0x1009 tx timeout
[ 1717.420690] Bluetooth: hci0 command 0x1003 tx timeout
[ 1719.500695] Bluetooth: hci0 command 0x1001 tx timeout
[ 1721.580697] Bluetooth: hci0 command 0x1009 tx timeout
[ 1728.940700] Bluetooth: hci0 command 0x1003 tx timeout
[ 1731.020745] Bluetooth: hci0 command 0x1001 tx timeout
[ 1733.100711] Bluetooth: hci0 command 0x1009 tx timeout
[ 1766.060724] Bluetooth: hci0 command 0x1003 tx timeout
[ 1768.140730] Bluetooth: hci0 command 0x1001 tx timeout
[ 1770.220721] Bluetooth: hci0 command 0x1009 tx timeout
[ 1830.140659] Bluetooth: hci0 command 0x1003 tx timeout
[ 1832.220708] Bluetooth: hci0 command 0x1001 tx timeout
[ 1834.300655] Bluetooth: hci0 command 0x1009 tx timeout
systemctl status bluetooth shows:
Jan 13 21:46:10 picroft bluetoothd[7820]: Excluding (cli) sap
Jan 13 21:46:10 picroft bluetoothd[7820]: Bluetooth management interface 1.14 initialized
Jan 13 21:46:10 picroft bluetoothd[7820]: Failed to obtain handles for "Service Changed" characteristic
Jan 13 21:46:10 picroft bluetoothd[7820]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource
Jan 13 21:46:10 picroft bluetoothd[7820]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink
Jan 13 21:46:12 picroft bluetoothd[7820]: Loading LTKs timed out for hci0
Jan 13 21:46:20 picroft bluetoothd[7820]: Failed to set mode: Failed (0x03)
Jan 13 21:46:31 picroft bluetoothd[7820]: Failed to set mode: Failed (0x03)
Jan 13 21:53:30 picroft bluetoothd[7820]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource
Jan 13 21:53:30 picroft bluetoothd[7820]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSink
I really don't know whats causing this, but a reboot fixes it.
Does anyone know whats the cause / how to fix it?
raspberry-pi pulseaudio bluetooth
New contributor
Tobias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I use it to connect to a speaker (as a pulseaudio sink)
dmesg | grep Blue shows the following:
[ 14.034501] Bluetooth: Core ver 2.22
[ 14.034587] Bluetooth: HCI device and connection manager initialized
[ 14.034609] Bluetooth: HCI socket layer initialized
[ 14.034622] Bluetooth: L2CAP socket layer initialized
[ 14.034654] Bluetooth: SCO socket layer initialized
[ 14.048959] Bluetooth: HCI UART driver ver 2.3
[ 14.048974] Bluetooth: HCI UART protocol H4 registered
[ 14.048980] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 14.049211] Bluetooth: HCI UART protocol Broadcom registered
[ 14.324295] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.324304] Bluetooth: BNEP filters: protocol multicast
[ 14.324318] Bluetooth: BNEP socket layer initialized
[ 14.400493] Bluetooth: RFCOMM TTY layer initialized
[ 14.400517] Bluetooth: RFCOMM socket layer initialized
[ 14.400544] Bluetooth: RFCOMM ver 1.11
[ 1615.270230] Bluetooth: hci0 hardware error 0x00
[ 1619.500366] Bluetooth: hci0 command 0x1003 tx timeout
[ 1621.580373] Bluetooth: hci0 command 0x1001 tx timeout
[ 1623.660382] Bluetooth: hci0 command 0x1009 tx timeout
[ 1627.980418] Bluetooth: hci0 hardware error 0x00
[ 1630.060437] Bluetooth: hci0 command 0x1003 tx timeout
[ 1632.140793] Bluetooth: hci0 command 0x1001 tx timeout
[ 1634.220438] Bluetooth: hci0 command 0x1009 tx timeout
[ 1717.420690] Bluetooth: hci0 command 0x1003 tx timeout
[ 1719.500695] Bluetooth: hci0 command 0x1001 tx timeout
[ 1721.580697] Bluetooth: hci0 command 0x1009 tx timeout
[ 1728.940700] Bluetooth: hci0 command 0x1003 tx timeout
[ 1731.020745] Bluetooth: hci0 command 0x1001 tx timeout
[ 1733.100711] Bluetooth: hci0 command 0x1009 tx timeout
[ 1766.060724] Bluetooth: hci0 command 0x1003 tx timeout
[ 1768.140730] Bluetooth: hci0 command 0x1001 tx timeout
[ 1770.220721] Bluetooth: hci0 command 0x1009 tx timeout
[ 1830.140659] Bluetooth: hci0 command 0x1003 tx timeout
[ 1832.220708] Bluetooth: hci0 command 0x1001 tx timeout
[ 1834.300655] Bluetooth: hci0 command 0x1009 tx timeout
systemctl status bluetooth shows:
Jan 13 21:46:10 picroft bluetoothd[7820]: Excluding (cli) sap
Jan 13 21:46:10 picroft bluetoothd[7820]: Bluetooth management interface 1.14 initialized
Jan 13 21:46:10 picroft bluetoothd[7820]: Failed to obtain handles for "Service Changed" characteristic
Jan 13 21:46:10 picroft bluetoothd[7820]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource
Jan 13 21:46:10 picroft bluetoothd[7820]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink
Jan 13 21:46:12 picroft bluetoothd[7820]: Loading LTKs timed out for hci0
Jan 13 21:46:20 picroft bluetoothd[7820]: Failed to set mode: Failed (0x03)
Jan 13 21:46:31 picroft bluetoothd[7820]: Failed to set mode: Failed (0x03)
Jan 13 21:53:30 picroft bluetoothd[7820]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource
Jan 13 21:53:30 picroft bluetoothd[7820]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSink
I really don't know whats causing this, but a reboot fixes it.
Does anyone know whats the cause / how to fix it?
raspberry-pi pulseaudio bluetooth
New contributor
Tobias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
On unrelated hardware I had interferences between wifi and bluetooth (which have overlapping freqs in the 2.4GHz): audio failed sometimes after i could see wifi renegociating. Are you also using wifi?
– A.B
Jan 14 at 20:21
Yes I am. I am gonna try a wired connection and see if that fixes it.
– Tobias
Jan 14 at 20:24
add a comment |
I use it to connect to a speaker (as a pulseaudio sink)
dmesg | grep Blue shows the following:
[ 14.034501] Bluetooth: Core ver 2.22
[ 14.034587] Bluetooth: HCI device and connection manager initialized
[ 14.034609] Bluetooth: HCI socket layer initialized
[ 14.034622] Bluetooth: L2CAP socket layer initialized
[ 14.034654] Bluetooth: SCO socket layer initialized
[ 14.048959] Bluetooth: HCI UART driver ver 2.3
[ 14.048974] Bluetooth: HCI UART protocol H4 registered
[ 14.048980] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 14.049211] Bluetooth: HCI UART protocol Broadcom registered
[ 14.324295] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.324304] Bluetooth: BNEP filters: protocol multicast
[ 14.324318] Bluetooth: BNEP socket layer initialized
[ 14.400493] Bluetooth: RFCOMM TTY layer initialized
[ 14.400517] Bluetooth: RFCOMM socket layer initialized
[ 14.400544] Bluetooth: RFCOMM ver 1.11
[ 1615.270230] Bluetooth: hci0 hardware error 0x00
[ 1619.500366] Bluetooth: hci0 command 0x1003 tx timeout
[ 1621.580373] Bluetooth: hci0 command 0x1001 tx timeout
[ 1623.660382] Bluetooth: hci0 command 0x1009 tx timeout
[ 1627.980418] Bluetooth: hci0 hardware error 0x00
[ 1630.060437] Bluetooth: hci0 command 0x1003 tx timeout
[ 1632.140793] Bluetooth: hci0 command 0x1001 tx timeout
[ 1634.220438] Bluetooth: hci0 command 0x1009 tx timeout
[ 1717.420690] Bluetooth: hci0 command 0x1003 tx timeout
[ 1719.500695] Bluetooth: hci0 command 0x1001 tx timeout
[ 1721.580697] Bluetooth: hci0 command 0x1009 tx timeout
[ 1728.940700] Bluetooth: hci0 command 0x1003 tx timeout
[ 1731.020745] Bluetooth: hci0 command 0x1001 tx timeout
[ 1733.100711] Bluetooth: hci0 command 0x1009 tx timeout
[ 1766.060724] Bluetooth: hci0 command 0x1003 tx timeout
[ 1768.140730] Bluetooth: hci0 command 0x1001 tx timeout
[ 1770.220721] Bluetooth: hci0 command 0x1009 tx timeout
[ 1830.140659] Bluetooth: hci0 command 0x1003 tx timeout
[ 1832.220708] Bluetooth: hci0 command 0x1001 tx timeout
[ 1834.300655] Bluetooth: hci0 command 0x1009 tx timeout
systemctl status bluetooth shows:
Jan 13 21:46:10 picroft bluetoothd[7820]: Excluding (cli) sap
Jan 13 21:46:10 picroft bluetoothd[7820]: Bluetooth management interface 1.14 initialized
Jan 13 21:46:10 picroft bluetoothd[7820]: Failed to obtain handles for "Service Changed" characteristic
Jan 13 21:46:10 picroft bluetoothd[7820]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource
Jan 13 21:46:10 picroft bluetoothd[7820]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink
Jan 13 21:46:12 picroft bluetoothd[7820]: Loading LTKs timed out for hci0
Jan 13 21:46:20 picroft bluetoothd[7820]: Failed to set mode: Failed (0x03)
Jan 13 21:46:31 picroft bluetoothd[7820]: Failed to set mode: Failed (0x03)
Jan 13 21:53:30 picroft bluetoothd[7820]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource
Jan 13 21:53:30 picroft bluetoothd[7820]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSink
I really don't know whats causing this, but a reboot fixes it.
Does anyone know whats the cause / how to fix it?
raspberry-pi pulseaudio bluetooth
New contributor
Tobias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I use it to connect to a speaker (as a pulseaudio sink)
dmesg | grep Blue shows the following:
[ 14.034501] Bluetooth: Core ver 2.22
[ 14.034587] Bluetooth: HCI device and connection manager initialized
[ 14.034609] Bluetooth: HCI socket layer initialized
[ 14.034622] Bluetooth: L2CAP socket layer initialized
[ 14.034654] Bluetooth: SCO socket layer initialized
[ 14.048959] Bluetooth: HCI UART driver ver 2.3
[ 14.048974] Bluetooth: HCI UART protocol H4 registered
[ 14.048980] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 14.049211] Bluetooth: HCI UART protocol Broadcom registered
[ 14.324295] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.324304] Bluetooth: BNEP filters: protocol multicast
[ 14.324318] Bluetooth: BNEP socket layer initialized
[ 14.400493] Bluetooth: RFCOMM TTY layer initialized
[ 14.400517] Bluetooth: RFCOMM socket layer initialized
[ 14.400544] Bluetooth: RFCOMM ver 1.11
[ 1615.270230] Bluetooth: hci0 hardware error 0x00
[ 1619.500366] Bluetooth: hci0 command 0x1003 tx timeout
[ 1621.580373] Bluetooth: hci0 command 0x1001 tx timeout
[ 1623.660382] Bluetooth: hci0 command 0x1009 tx timeout
[ 1627.980418] Bluetooth: hci0 hardware error 0x00
[ 1630.060437] Bluetooth: hci0 command 0x1003 tx timeout
[ 1632.140793] Bluetooth: hci0 command 0x1001 tx timeout
[ 1634.220438] Bluetooth: hci0 command 0x1009 tx timeout
[ 1717.420690] Bluetooth: hci0 command 0x1003 tx timeout
[ 1719.500695] Bluetooth: hci0 command 0x1001 tx timeout
[ 1721.580697] Bluetooth: hci0 command 0x1009 tx timeout
[ 1728.940700] Bluetooth: hci0 command 0x1003 tx timeout
[ 1731.020745] Bluetooth: hci0 command 0x1001 tx timeout
[ 1733.100711] Bluetooth: hci0 command 0x1009 tx timeout
[ 1766.060724] Bluetooth: hci0 command 0x1003 tx timeout
[ 1768.140730] Bluetooth: hci0 command 0x1001 tx timeout
[ 1770.220721] Bluetooth: hci0 command 0x1009 tx timeout
[ 1830.140659] Bluetooth: hci0 command 0x1003 tx timeout
[ 1832.220708] Bluetooth: hci0 command 0x1001 tx timeout
[ 1834.300655] Bluetooth: hci0 command 0x1009 tx timeout
systemctl status bluetooth shows:
Jan 13 21:46:10 picroft bluetoothd[7820]: Excluding (cli) sap
Jan 13 21:46:10 picroft bluetoothd[7820]: Bluetooth management interface 1.14 initialized
Jan 13 21:46:10 picroft bluetoothd[7820]: Failed to obtain handles for "Service Changed" characteristic
Jan 13 21:46:10 picroft bluetoothd[7820]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource
Jan 13 21:46:10 picroft bluetoothd[7820]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink
Jan 13 21:46:12 picroft bluetoothd[7820]: Loading LTKs timed out for hci0
Jan 13 21:46:20 picroft bluetoothd[7820]: Failed to set mode: Failed (0x03)
Jan 13 21:46:31 picroft bluetoothd[7820]: Failed to set mode: Failed (0x03)
Jan 13 21:53:30 picroft bluetoothd[7820]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource
Jan 13 21:53:30 picroft bluetoothd[7820]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSink
I really don't know whats causing this, but a reboot fixes it.
Does anyone know whats the cause / how to fix it?
raspberry-pi pulseaudio bluetooth
raspberry-pi pulseaudio bluetooth
New contributor
Tobias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Tobias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Tobias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 14 at 20:13
TobiasTobias
61
61
New contributor
Tobias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Tobias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Tobias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
On unrelated hardware I had interferences between wifi and bluetooth (which have overlapping freqs in the 2.4GHz): audio failed sometimes after i could see wifi renegociating. Are you also using wifi?
– A.B
Jan 14 at 20:21
Yes I am. I am gonna try a wired connection and see if that fixes it.
– Tobias
Jan 14 at 20:24
add a comment |
On unrelated hardware I had interferences between wifi and bluetooth (which have overlapping freqs in the 2.4GHz): audio failed sometimes after i could see wifi renegociating. Are you also using wifi?
– A.B
Jan 14 at 20:21
Yes I am. I am gonna try a wired connection and see if that fixes it.
– Tobias
Jan 14 at 20:24
On unrelated hardware I had interferences between wifi and bluetooth (which have overlapping freqs in the 2.4GHz): audio failed sometimes after i could see wifi renegociating. Are you also using wifi?
– A.B
Jan 14 at 20:21
On unrelated hardware I had interferences between wifi and bluetooth (which have overlapping freqs in the 2.4GHz): audio failed sometimes after i could see wifi renegociating. Are you also using wifi?
– A.B
Jan 14 at 20:21
Yes I am. I am gonna try a wired connection and see if that fixes it.
– Tobias
Jan 14 at 20:24
Yes I am. I am gonna try a wired connection and see if that fixes it.
– Tobias
Jan 14 at 20:24
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Tobias is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494486%2fraspberry-pi-3-bluetooth-stops-working-after-a-while%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Tobias is a new contributor. Be nice, and check out our Code of Conduct.
Tobias is a new contributor. Be nice, and check out our Code of Conduct.
Tobias is a new contributor. Be nice, and check out our Code of Conduct.
Tobias is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494486%2fraspberry-pi-3-bluetooth-stops-working-after-a-while%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
On unrelated hardware I had interferences between wifi and bluetooth (which have overlapping freqs in the 2.4GHz): audio failed sometimes after i could see wifi renegociating. Are you also using wifi?
– A.B
Jan 14 at 20:21
Yes I am. I am gonna try a wired connection and see if that fixes it.
– Tobias
Jan 14 at 20:24