Current RC has bad bluetooth on Op5t

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.

Moem

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

it works on stable and does not on Rc

That is exactly the case.

Yougo

@flohack

Here's the log for dev:
pebbledumpdev-summary.pdf
pebbledumpdev.pdf
pebbledumpdev.log
bluetoothctl terminal output

and here's the log for stable:
pebbledumpstable-summary.pdf
pebpledumpstable.pdf
bluetoothctl terminal output

stable connected fabulously , from what i could see, rc and dev failed in the exact same way...

Moem

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

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

I've tried and tried to get Focal running on the Xperia X but I always end up with a non-booting device. Installation seems to finish, the device reboots and try to install updates, this fails and the phone will then only boot to recovery.
So I still can't try the BT on Focal.

flohack

Whole Bluetooth changes will be reverted. This will delay that OTA further, unfortunately, as we need a new RC...

Yougo

@flohack

Thanks for your update.
Good news for Pebblers I guess, but yikes thats a setback... sorry to hear that.

I just installed my Pixel 3a (stable) OTA-24 and the BT connection with my Pebble survived. Is that because of the delay, or was OTA-24 safe anyway?

is it usefull to get a new log on OTA-24?

arubislander

@yougo OTA-24 contains the same bluetooth stack as OTA-23. That was the object of the decision to revert.