UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Bluetooth findings with OTA-13 (rc)

    Scheduled Pinned Locked Moved Support
    13 Posts 4 Posters 1.0k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • P Offline
        padu
        last edited by

        This post refers to the discussion related to Bluetooth in topic OTA-13 call for testing

        @Moem said in OTA-13 call for testing:

        OTA-13 RC seems to improve OnePlus One carkit telephony compatibility.

        Unfortunately I can't reproduce this (with OpO and Jabra Drive carkit). Still no dice.

        Don't know if that is relevant, but I have

        • the latest firmware on OnePlus One
        • removed all known HFP devices carkit-side (because I did have issues, too)
        • removed the carkit phone-side
        • paired both devices anew

        And then carkit telephony just worked (tested with Volkswagen carkit Composition Media). Will re-run my tests if I find some time and report back.

        Can anyone else confirm OTA-13 carkit telephony improvements?

        1 Reply Last reply Reply Quote 0
        • MoemM Offline
          Moem
          last edited by

          Not yet, but your post gives me new hope. I'll remove the phone from the carkit and vice versa, pair them again and see what happens. The firmware stuff is above my pay grade.

          Is currently using an Op5t
          Also owns an Op1, a BQ E4.5 and an Xperia X, as well as a BQ tablet and a Pinetab2. Please, someone... make it stop.

          P 1 Reply Last reply Reply Quote 0
          • P Offline
            padu @Moem
            last edited by

            @Moem said in Bluetooth findings with OTA-13 (rc):

            The firmware stuff is above my pay grade.

            You can at least check your firmware by typing this on the terminal

            phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems | grep -i rev
                Revision = .4.0.1.c7-00013-M8974AAAAANAZM-1
            

            and compare the result.

            1 Reply Last reply Reply Quote 0
            • flohackF Offline
              flohack
              last edited by

              Bluetooth firmware is loaded from the system image for Bluetooth and has nothing to do with the modem firmware...

              My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

              1 Reply Last reply Reply Quote 0
              • P Offline
                padu
                last edited by

                That is, it is updated automatically as long as new Bluetooth firmware is available?

                flohackF 1 Reply Last reply Reply Quote 0
                • flohackF Offline
                  flohack @padu
                  last edited by

                  @padu No its never updated, as Oneplus does not supply new firmware for an old model πŸ˜‰

                  My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                  1 Reply Last reply Reply Quote 0
                  • flohackF Offline
                    flohack
                    last edited by

                    Also, please bear in mind the problems you are looking for are probably not coming from the firmware: A Bluetooth network card is a thin layer.

                    Our issue is: Old Bluez daemon plus buggy pulseaudio plus a ton of other bugs all over the place. All in middleware and UX-facing software.

                    Its 100% not a BT firmware issue, thats just responsible for sending frames around, and that obviously works.

                    My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                    1 Reply Last reply Reply Quote 0
                    • P Offline
                      padu
                      last edited by padu

                      About the old bluez, I've read @mariogrip having hacked on backporting bluez 5.50. How's that progressing? Might that come before the 18.04/20.04 switch?

                      flohackF 1 Reply Last reply Reply Quote 0
                      • P Offline
                        padu
                        last edited by padu

                        BTW, I'm not looking for problems. πŸ™‚ I just noticed that carkit telephony works with some devices with OTA-13, while people ask for this in other threads [1], [2].

                        1 Reply Last reply Reply Quote 0
                        • flohackF Offline
                          flohack @padu
                          last edited by

                          @padu Its barely moving along, as we were dragged into the Non-Android phones for the last 1.5yrs, And we would need more hands for that to be cleaned up. But as I said, Bluez is only on part of the problem, audio routing for various audio devices incl 4000 non-standardcompliant carkits is done more in other layers, like pulseaudio and telepathy-ofono I think. Its worth a few man months of work probably.

                          My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                          1 Reply Last reply Reply Quote 0
                          • P Offline
                            padu
                            last edited by

                            @Flohack That's an invitation for sponsoring. (Looking at Canonical, for Ubuntu conquering mobile platform certainly raises their market value.)

                            KenedaK 1 Reply Last reply Reply Quote 0
                            • KenedaK Offline
                              Keneda @padu
                              last edited by

                              @padu said in Bluetooth findings with OTA-13 (rc):

                              (Looking at Canonical, for Ubuntu conquering mobile platform certainly raises their market value.)

                              Are you telling that ubports should ask canonical to help them improve the very one phone OS they dumped to the ditch three years ago?

                              2015-2023 : Meizu MX4 ☠️⚰️✝️
                              2023-2024 : Nexus 5 ☠️⚰️✝️
                              2024-***** : FPOS Fairphone 5 waiting UT for freedom πŸ˜‰
                              πŸ‡²πŸ‡«πŸ‡¬πŸ‡§

                              1 Reply Last reply Reply Quote 0
                              • P Offline
                                padu
                                last edited by padu

                                @Keneda Like HP, Canonical have been wimps. Never put the (massive) resources needed into mobile platform and then had to step back. In contrast, a little sponsoring today is peanuts for Canonical (that may focus on enterprise grade features for the otherwise community driven project). About asking Canonical, I think there's no need for that. There's just one UBports foundation out there and Canonical certainly knows where to find them. (But just in case ...)

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post