Current RC has bad bluetooth on Op5t

Yougo

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.

Yougo

@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

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.

Flohack

@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

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.

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

Yougo

@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

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

Moem

@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!

klh

This post is deleted!

klh

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

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.

klh

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

Moem

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

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)

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?)

Flohack

Sorry to say but I hav eno clue where to begin with debugging this... bluetoothctl does not seem the right place I guess. btmon could be tried it can produce files with packet traces that can be openend in Wireshark.

Yougo

@flohack i already did the btmon+wireshark thing for RC channel. the output is gibberish to me so it would be great if someone with more skills could look at it.
https://forums.ubports.com/post/67758

My latest question was if the same btmon+wireshark output for dev and/or stable would be useful to generate. if so i'll happily do that.

Flohack

@yougo if it works on stable and does not on Rc then yes, 2 traces could be helpful. Depending on which layer the problem actually is. Also a debug log of the Bluez daemon might be needed.