Ubuntu 18.04 and bluetooth speaker JBL Charge 3











up vote
6
down vote

favorite
5












I upgraded to the new 18.04 version of ubuntu, coming from the latest 17. release. In both versions I have the same problem using my JBL Charge 3 bluetooth speaker. The sound is lagging and is being interrupted in uneven sequences, sometimes sounding OK for two seconds, then being interrupted in bursts.



I have tried disconnecting, re-connecting, switching HSP/HFP and A2DP Sink on and off, also "forgetting" the device and reconfiguring it.



My kernel (dmesg) says (repeatedly):



[ 5903.702600] input: FC:A8:9A:9B:81:E9 as /devices/virtual/input/input23
[ 5917.523365] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5933.525358] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5949.523345] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5965.524317] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5981.524464] Bluetooth: hci0: last event is not cmd complete (0x0f)


I have also tried this workaround without success.










share|improve this question






















  • have same one. I also can reproduce it on 17.10. [ 2165.605629] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 2170.010235] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4746.012661] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4762.012971] Bluetooth: hci0: setting interface failed (19) [ 4764.412328] Bluetooth: hci0: command 0xfc05 tx timeout [ 4764.412348] Bluetooth: hci0: Reading Intel version information failed (-110) bluetooth 548864 16 btrtl,btintel,bnep,btbcm,rfcomm,ath3k,btusb ecdh_generic 24576 1 bluetooth
    – Grigoriev Nick
    May 10 at 9:31















up vote
6
down vote

favorite
5












I upgraded to the new 18.04 version of ubuntu, coming from the latest 17. release. In both versions I have the same problem using my JBL Charge 3 bluetooth speaker. The sound is lagging and is being interrupted in uneven sequences, sometimes sounding OK for two seconds, then being interrupted in bursts.



I have tried disconnecting, re-connecting, switching HSP/HFP and A2DP Sink on and off, also "forgetting" the device and reconfiguring it.



My kernel (dmesg) says (repeatedly):



[ 5903.702600] input: FC:A8:9A:9B:81:E9 as /devices/virtual/input/input23
[ 5917.523365] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5933.525358] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5949.523345] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5965.524317] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5981.524464] Bluetooth: hci0: last event is not cmd complete (0x0f)


I have also tried this workaround without success.










share|improve this question






















  • have same one. I also can reproduce it on 17.10. [ 2165.605629] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 2170.010235] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4746.012661] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4762.012971] Bluetooth: hci0: setting interface failed (19) [ 4764.412328] Bluetooth: hci0: command 0xfc05 tx timeout [ 4764.412348] Bluetooth: hci0: Reading Intel version information failed (-110) bluetooth 548864 16 btrtl,btintel,bnep,btbcm,rfcomm,ath3k,btusb ecdh_generic 24576 1 bluetooth
    – Grigoriev Nick
    May 10 at 9:31













up vote
6
down vote

favorite
5









up vote
6
down vote

favorite
5






5





I upgraded to the new 18.04 version of ubuntu, coming from the latest 17. release. In both versions I have the same problem using my JBL Charge 3 bluetooth speaker. The sound is lagging and is being interrupted in uneven sequences, sometimes sounding OK for two seconds, then being interrupted in bursts.



I have tried disconnecting, re-connecting, switching HSP/HFP and A2DP Sink on and off, also "forgetting" the device and reconfiguring it.



My kernel (dmesg) says (repeatedly):



[ 5903.702600] input: FC:A8:9A:9B:81:E9 as /devices/virtual/input/input23
[ 5917.523365] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5933.525358] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5949.523345] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5965.524317] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5981.524464] Bluetooth: hci0: last event is not cmd complete (0x0f)


I have also tried this workaround without success.










share|improve this question













I upgraded to the new 18.04 version of ubuntu, coming from the latest 17. release. In both versions I have the same problem using my JBL Charge 3 bluetooth speaker. The sound is lagging and is being interrupted in uneven sequences, sometimes sounding OK for two seconds, then being interrupted in bursts.



I have tried disconnecting, re-connecting, switching HSP/HFP and A2DP Sink on and off, also "forgetting" the device and reconfiguring it.



My kernel (dmesg) says (repeatedly):



[ 5903.702600] input: FC:A8:9A:9B:81:E9 as /devices/virtual/input/input23
[ 5917.523365] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5933.525358] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5949.523345] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5965.524317] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 5981.524464] Bluetooth: hci0: last event is not cmd complete (0x0f)


I have also tried this workaround without success.







sound bluetooth






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Apr 28 at 13:43









chrisk

312




312












  • have same one. I also can reproduce it on 17.10. [ 2165.605629] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 2170.010235] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4746.012661] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4762.012971] Bluetooth: hci0: setting interface failed (19) [ 4764.412328] Bluetooth: hci0: command 0xfc05 tx timeout [ 4764.412348] Bluetooth: hci0: Reading Intel version information failed (-110) bluetooth 548864 16 btrtl,btintel,bnep,btbcm,rfcomm,ath3k,btusb ecdh_generic 24576 1 bluetooth
    – Grigoriev Nick
    May 10 at 9:31


















  • have same one. I also can reproduce it on 17.10. [ 2165.605629] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 2170.010235] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4746.012661] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4762.012971] Bluetooth: hci0: setting interface failed (19) [ 4764.412328] Bluetooth: hci0: command 0xfc05 tx timeout [ 4764.412348] Bluetooth: hci0: Reading Intel version information failed (-110) bluetooth 548864 16 btrtl,btintel,bnep,btbcm,rfcomm,ath3k,btusb ecdh_generic 24576 1 bluetooth
    – Grigoriev Nick
    May 10 at 9:31
















have same one. I also can reproduce it on 17.10. [ 2165.605629] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 2170.010235] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4746.012661] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4762.012971] Bluetooth: hci0: setting interface failed (19) [ 4764.412328] Bluetooth: hci0: command 0xfc05 tx timeout [ 4764.412348] Bluetooth: hci0: Reading Intel version information failed (-110) bluetooth 548864 16 btrtl,btintel,bnep,btbcm,rfcomm,ath3k,btusb ecdh_generic 24576 1 bluetooth
– Grigoriev Nick
May 10 at 9:31




have same one. I also can reproduce it on 17.10. [ 2165.605629] Bluetooth: hci0: SCO packet for unknown connection handle 0 [ 2170.010235] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4746.012661] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 4762.012971] Bluetooth: hci0: setting interface failed (19) [ 4764.412328] Bluetooth: hci0: command 0xfc05 tx timeout [ 4764.412348] Bluetooth: hci0: Reading Intel version information failed (-110) bluetooth 548864 16 btrtl,btintel,bnep,btbcm,rfcomm,ath3k,btusb ecdh_generic 24576 1 bluetooth
– Grigoriev Nick
May 10 at 9:31










2 Answers
2






active

oldest

votes

















up vote
0
down vote













I have this speaker and Intel integrated bluetooth. I think it's just bad controller, because I had issues with other devices before. The only thing you can do is to locate your speaker as close to your pc/laptop as possible, on distances more than 2 meters it won't work reliably. The other thing to consider if you are on 18.04 and using intel's bluetooth is updating firmware from here https://unix.stackexchange.com/questions/257270/get-rid-of-no-caching-mode-page-found-message-during-boot and installing fresh version of bluez from this PPA https://launchpad.net/~bluetooth/+archive/ubuntu/bluez.
It might not be the cause of your particular problem, but you definitely will see this bug later if you will get your speaker to work.






share|improve this answer




























    up vote
    0
    down vote













    The sound is distorted as long as the "bluetooth setting" windows is open and searching. Closing the windows clears the sound and stops the messages in the dmesg.



    Blueman (alternative bluetooth manager) shows the same behavior while searching for devices, but the default bluetooth manager is constantly searching when open.



    It would be interesting to discover if this affects only JBL speakers, and if it is a problem of some bluetooth controllers only (mine is a Intel 3165).






    share|improve this answer





















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      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',
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      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
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1029233%2fubuntu-18-04-and-bluetooth-speaker-jbl-charge-3%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      0
      down vote













      I have this speaker and Intel integrated bluetooth. I think it's just bad controller, because I had issues with other devices before. The only thing you can do is to locate your speaker as close to your pc/laptop as possible, on distances more than 2 meters it won't work reliably. The other thing to consider if you are on 18.04 and using intel's bluetooth is updating firmware from here https://unix.stackexchange.com/questions/257270/get-rid-of-no-caching-mode-page-found-message-during-boot and installing fresh version of bluez from this PPA https://launchpad.net/~bluetooth/+archive/ubuntu/bluez.
      It might not be the cause of your particular problem, but you definitely will see this bug later if you will get your speaker to work.






      share|improve this answer

























        up vote
        0
        down vote













        I have this speaker and Intel integrated bluetooth. I think it's just bad controller, because I had issues with other devices before. The only thing you can do is to locate your speaker as close to your pc/laptop as possible, on distances more than 2 meters it won't work reliably. The other thing to consider if you are on 18.04 and using intel's bluetooth is updating firmware from here https://unix.stackexchange.com/questions/257270/get-rid-of-no-caching-mode-page-found-message-during-boot and installing fresh version of bluez from this PPA https://launchpad.net/~bluetooth/+archive/ubuntu/bluez.
        It might not be the cause of your particular problem, but you definitely will see this bug later if you will get your speaker to work.






        share|improve this answer























          up vote
          0
          down vote










          up vote
          0
          down vote









          I have this speaker and Intel integrated bluetooth. I think it's just bad controller, because I had issues with other devices before. The only thing you can do is to locate your speaker as close to your pc/laptop as possible, on distances more than 2 meters it won't work reliably. The other thing to consider if you are on 18.04 and using intel's bluetooth is updating firmware from here https://unix.stackexchange.com/questions/257270/get-rid-of-no-caching-mode-page-found-message-during-boot and installing fresh version of bluez from this PPA https://launchpad.net/~bluetooth/+archive/ubuntu/bluez.
          It might not be the cause of your particular problem, but you definitely will see this bug later if you will get your speaker to work.






          share|improve this answer












          I have this speaker and Intel integrated bluetooth. I think it's just bad controller, because I had issues with other devices before. The only thing you can do is to locate your speaker as close to your pc/laptop as possible, on distances more than 2 meters it won't work reliably. The other thing to consider if you are on 18.04 and using intel's bluetooth is updating firmware from here https://unix.stackexchange.com/questions/257270/get-rid-of-no-caching-mode-page-found-message-during-boot and installing fresh version of bluez from this PPA https://launchpad.net/~bluetooth/+archive/ubuntu/bluez.
          It might not be the cause of your particular problem, but you definitely will see this bug later if you will get your speaker to work.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered May 14 at 13:53









          monte

          11




          11
























              up vote
              0
              down vote













              The sound is distorted as long as the "bluetooth setting" windows is open and searching. Closing the windows clears the sound and stops the messages in the dmesg.



              Blueman (alternative bluetooth manager) shows the same behavior while searching for devices, but the default bluetooth manager is constantly searching when open.



              It would be interesting to discover if this affects only JBL speakers, and if it is a problem of some bluetooth controllers only (mine is a Intel 3165).






              share|improve this answer

























                up vote
                0
                down vote













                The sound is distorted as long as the "bluetooth setting" windows is open and searching. Closing the windows clears the sound and stops the messages in the dmesg.



                Blueman (alternative bluetooth manager) shows the same behavior while searching for devices, but the default bluetooth manager is constantly searching when open.



                It would be interesting to discover if this affects only JBL speakers, and if it is a problem of some bluetooth controllers only (mine is a Intel 3165).






                share|improve this answer























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  The sound is distorted as long as the "bluetooth setting" windows is open and searching. Closing the windows clears the sound and stops the messages in the dmesg.



                  Blueman (alternative bluetooth manager) shows the same behavior while searching for devices, but the default bluetooth manager is constantly searching when open.



                  It would be interesting to discover if this affects only JBL speakers, and if it is a problem of some bluetooth controllers only (mine is a Intel 3165).






                  share|improve this answer












                  The sound is distorted as long as the "bluetooth setting" windows is open and searching. Closing the windows clears the sound and stops the messages in the dmesg.



                  Blueman (alternative bluetooth manager) shows the same behavior while searching for devices, but the default bluetooth manager is constantly searching when open.



                  It would be interesting to discover if this affects only JBL speakers, and if it is a problem of some bluetooth controllers only (mine is a Intel 3165).







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 26 at 9:36









                  Thomas

                  65




                  65






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • 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.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • 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.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1029233%2fubuntu-18-04-and-bluetooth-speaker-jbl-charge-3%23new-answer', 'question_page');
                      }
                      );

                      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







                      Popular posts from this blog

                      Mont Emei

                      Province de Neuquén

                      Journaliste