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

    Current RC has bad bluetooth on Op5t

    Scheduled Pinned Locked Moved Oneplus 5/5T
    bluetoothsmartwatchstable channelrelease channeloneplus 5t
    31 Posts 5 Posters 5.3k Views 4 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.
      • MoemM Offline
        Moem @Yougo
        last edited by Moem

        @yougo said in Current RC has bad bluetooth on Op5t:

        --it connects... for about three seconds and then drops off.--

        Yes! Exactly the same issue I was having on RC. Now, back on stable, it's fine.

        Could it be that an old protocol or some such was removed from the bluetooth stack, causing older devices to fail?

        πŸ€”

        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.

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

          Well we upgraded Bluez stack to 5.53 -- that might be the reason. We would need some more debug infos here. Unfortunately I will not hold off the OTA for this now, we are 2 months late and need to ship what we have. And we alread have issues with contacts, as soon as they are solved we put this into stable.

          We can investigate the issue in parallel.

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

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

            @flohack said in Current RC has bad bluetooth on Op5t:

            Unfortunately I will not hold off the OTA for this now, we are 2 months late and need to ship what we have.

            Fair enough! Maybe someone should send you a Pebble to make things easier to debug? :smiling_face_with_halo:
            I do know that they use BT 4.0.

            I'm no good at providing debug info, maybe @Yougo can help here. But first things first. It's not that urgent... I'll just stay on OTA23 for a while.

            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.

            Y 1 Reply Last reply Reply Quote 0
            • Y Offline
              Yougo @Moem
              last edited by

              @moem @Flohack

              sure, i'll stay on rc or maybe move to dev to help test or dig up logs that may be of interest, as long as my phone keeps working. i just got a 'project' of sorts today that needs me to be on call for the coming week (given your stated schedule that shouldn't be problem πŸ˜‰)

              just lemme know if i can help

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

                @yougo You may want to run btmon trace during the pairing and connect, and log that to a file. It can then be inspected with Wireshark

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

                Y 2 Replies Last reply Reply Quote 0
                • Y Offline
                  Yougo @flohack
                  last edited by Yougo

                  @flohack
                  pebbledump.log

                  pastebin of terminal output(as far as i could scroll back and copy)
                  i hope you can make sense of this?
                  the device is 'Pebble Time 3247, B0:B4:48:A3:32:47'. there's also a 'Pebble Time LE 3247' but that's a (useless) limited mode that should be ignored.

                  1 Reply Last reply Reply Quote 0
                  • Y Offline
                    Yougo @flohack
                    last edited by

                    @flohack

                    Did you have a chance to look at it?
                    I've gone and tried wireshark.
                    i have no idea what i'm doing lol, but i managed to print out a packet list (both summary and all written out, one packet per page) of what i think are two complete cycles of finding, trusting, pairing, connecting and sadly disconnecting the Pebble.

                    i hope it helps

                    pebbledump summary.pdf
                    pebbledump.pdf

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

                      @yougo I wouldn't be surprised if this is not on the agenda as long as OTA24 isn't finished. And understandably so. Let's try and have a little patience. :relieved_face:

                      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.

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

                        @moem Honestly I do not see what we can do other than to roll back to old Bluez, and disappointing the owners that tested already devices that work now, but never did before with UT. If this is what we should do, then we do it. But unless it breaks on all devices the benefits would outweigh the negative impacts

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

                        MoemM Y 2 Replies Last reply Reply Quote 0
                        • MoemM Offline
                          Moem @flohack
                          last edited by Moem

                          @flohack said in Current RC has bad bluetooth on Op5t:

                          If this is what we should do, then we do it.

                          Well, that seems like it would make a lot of folks unhappy. No one wants that.
                          Maybe I'll have to say goodbye to my Pebbles then. :crying_face:

                          Would it be doable in cases like mine to roll my installation of UT back to the old Bluez BT stack? I mean, using old Bluez on OTA24+? If I can find someone who know what they're doing, of course.
                          My guess is: probably not...

                          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.

                          Y klhK 2 Replies Last reply Reply Quote 0
                          • Y Offline
                            Yougo @flohack
                            last edited by

                            @flohack

                            that is sad news for the few UT+pebble users. but understandibly if it's great news for a lot of new devices then i see where the priorities are, and rightfully so.

                            at least we learned something. thanks for your time πŸ™‚

                            1 Reply Last reply Reply Quote 1
                            • Y Offline
                              Yougo @Moem
                              last edited by Yougo

                              @moem
                              from what little i understand, i think a specific filesystem overlay would do what we want, provide a cusom bluez stack on one device while leaving the image for that port intact.

                              someone would need to create that overlay and maintain it, for every affected port, test it against new OTA's and adapt it accordingly, and the user would need to implement the overlay in their device after every OTA manually.

                              oofπŸ˜“

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

                                @yougo said in Current RC has bad bluetooth on Op5t:

                                someone would need to create that overlay and maintain it, for every affected port, test it against new OTA's and adapt it accordingly, and the user would need to implement the overlay in their device after every OTA manually.

                                Yeah, that sounds like a lot of work... and work that requires a specific skill set. If someone feels up for it, I would gladly send them a Pebble!

                                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.

                                1 Reply Last reply Reply Quote 0
                                • klhK Offline
                                  klh
                                  last edited by klh

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • klhK Offline
                                    klh @Moem
                                    last edited by

                                    @moem I see you have an Xperia X (forum signature) - can you install 20.04 on it and check if the watch connects there? Not sure if the issue is visible without the app, but if not I can try and build it for 20.04.

                                    I think the easiest is to install with the installer, checking "show hidden system-image channels" in the options and selecting 20.04 devel. Beware ofc that this is not end-user ready and a lot of things are missing.

                                    MoemM 2 Replies Last reply Reply Quote 0
                                    • MoemM Offline
                                      Moem @klh
                                      last edited by Moem

                                      @klh said in Current RC has bad bluetooth on Op5t:

                                      have an Xperia X (forum signature) - can you install 20.04 on it and check if the watch connects there?

                                      I tried that a few days ago, but it wouldn't boot. Should I try again?

                                      Not sure if the issue is visible without the app

                                      Yes, the watch should be able to connect, app or no app. The app is just for managing the watch, things like adding watchfaces and so on.

                                      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.

                                      klhK 1 Reply Last reply Reply Quote 0
                                      • klhK Offline
                                        klh @Moem
                                        last edited by

                                        @moem hmm, did you do a clean install with wipe and bootstrap? It's an older device, there were some kernel changes needed for 20.04 to work so might be safer with these options.

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

                                          @klh said in Current RC has bad bluetooth on Op5t:

                                          hmm, did you do a clean install with wipe and bootstrap?

                                          I believe so, but just in case, I will try again tomorrow.

                                          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.

                                          1 Reply Last reply Reply Quote 1
                                          • klhK Offline
                                            klh
                                            last edited by klh

                                            Oh, also @Yougo I see you have a Pixel 3a and that definitely has working 20.04, so you could also check (ofc only if this is not your only device, I can't repeat enough that 20.04 is not ready for general use ;p)

                                            Y 1 Reply Last reply Reply Quote 0
                                            • Y Offline
                                              Yougo @klh
                                              last edited by Yougo

                                              @klh sorry, life happened and i lost track of this thread. my pixel 3a is my main device so while i can switch channels between stable/rc and dev, 20.04 may be a bridge too far πŸ˜…

                                              @Flohack i did switch it to dev now. is that of any use for testing and logging bluetootctl?

                                              i also have a bq aquarius M10 HD but its dev channel is apparently stuck on 30.06.2022 and i dont suppose it has a 20.04 channel as it is a legacy device?
                                              i have a One Plus One with a broken screen, can't be operated...
                                              then i have a Fairphone 2. is that of any help at all?

                                              (what a sad bunch if i put it like that, huh?πŸ˜₯)

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