...Are we talking about Messages app, like for sms texting? Or a different app altogether?

I don't want to hijack this thread but i am having an issue that kind of relates to this one (involves messaging app, multiple duplicate notifications and a lomiri/window manager crash),
difference here is that the crash doesn't happen as i'm operating the messaging app, but at a "random" point in time afterwards
so i'm tagging along

Hi, Can someone help me out?

device: Pixel 3a
OS: 20.04 r667 (20-09-2023)

issue: after setting up my nextcloud account the calendar app does fetch and list the available calendars, but doesn't seem to sync events to or from Nextcloud.
The sync process does take about 10 minutes to complete but shows little for it

i tried:

• tweaking the URL setting up te account. the initial one is the only one that accepts and is also the one that works fine with Ghostcloud and Ubsync app. so my guess is the URL and credentials are correct.
• showing and hiding calendars in the app. no effect
• wiping folders in .local .cache and .config to varying degrees, even resorting to completely deleting the evolution folders and the syncevolution folders. the result is that the calendar app again correctly fetches the calendars, but doesn't sync the events
• creating an event in a listed calendar on the phone. the event shows up, indicating that the calendars are indeed visible but empty.
• syncing that event to Nextcloud. the locally created event does not show up in nextcloud

is there anything else i can try?
i'm not afraid to fetch logs or files and use the CLI but i'd need instructions

/ETA

ive tried more things:

• delete everything, add generic CALDAV account, with a generic CALDAV URL from my server, sync: same result. calendars are listed, but empty
• delete everything, add generic CALDAV account, with a MACOS CALDAV URL from my server, sync: same result. calendars are listed but empty
• added a google account. this one DOES show up! (but is not what i want lol)

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

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

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

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

@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

@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

@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

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

@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

I'm gonna +1 this

device: Pixel 3a
OS: Ubuntu 16.04 (2022-W39)
Channel: RC

connecting my Pebble Time Steel always was a bit iffy through System Settings, but using bluetoothctl in terminal gave me more control but still fails at connecting:

$ bluetoothctl
$ discoverable on
$ scan on
$ agent off
$ agent NoInputNoOutput (this to make sure no verification code is asked. the watch doesn't expect one)

--wait until you see your device pop up in the scan list --

$ trust [device mac]
$ pair [device mac]

--pairing should pop up a confirmation on the pebble. press top right button to confirm. terminal reports success--
so far so good, but then the last command gives trouble:

$ connect [device mac]

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

before the update, the pebble, once paired, had no trouble connecting and reconnecting. i could walk out of range of my phone and back in range and it would just pick up again.

Other devices (BT mouse, car's integrated hands-free set, windows laptop) seem to have no trouble.

/edit:

I realize all the devices i tested have one thing in common: they are all much newer than the Pebble smartwatch.
Could it be that an old protocol or some such was removed from the bluetooth stack, causing older devices to fail?

Hi, has anyone tried to install anbox on a bq M10 HD yet?

i have , but anbox-tool is telling me i need to flash the kernel, but i did that?!

i followed instructions from here: https://docs.ubports.com/en/latest/userguide/dailyuse/anbox.html

might there be some step missing? or is the anbox-boot-cooler.img not functional?

@doniks

it went from EVERYthing in the same xsession (and 1 xsession per window) to EVERYthing in a new window (don't know if it's multiple windows per xsession or worse, every gui item getting it's own xsession now)

i suspect xmir recently became aware of new windows, but either

1. still lacks the abilty to classify, or
2. has support for window classes but is not getting the proper instructions?

thinking about it, if every gui item gets it's own xsession, xmir is not wrong to give it a new window, so
3. xmir has support for window classes, probably gets the right instructions too, but only receives new xsessions == new window

how does Mir itself handle it? (don't have a mir session to play with on my pc)
/Edit:
Fun fact: i just tried with libreoffice on wayland and on Xorg: Wayland doesn't allow floating toolbars! i have to dock it somewhere, where on Xorg, i can have floating toolbars. the floating toolbar even shows on the panel as a separate window (tooltips and menus don't though)

@doniks judging by how hot my FP2 can get, and FP2's are mostly found in northwestern Europe, do we have correlation?

@killerbee indeed, so it's not depending on a specific toolkit (XUL, GTK3, QT, whatever libreoffice uses), but has to do with window classes not being recognized or not properly dealt with. which is a window manager thing.

Rodney told me on telegram that the problem might go away when we move from xmir to xwayland, but no idea on ETA on that

Hi, I can’t imagine no one has noticed this yet but couldn’t find anything about it yet. Feel free to merge/move this to where it belongs

Ever since updating to 16.04/devel, once libertine started working again, it works differently from how it was in 15.04.

It used to open everything an app did in the same window. Even new apps started by an app, like when you launch gedit from terminal. This was cumbersome, but the new situation is the other extreme: everything, tooltips, drop down menus, right-click menus, dialogue boxes, everything opens in a new window. Some middle road must be able to be achieved?

See also the github issue I made for it. https://github.com/ubports/libertine/issues/10

Does anyone have this problem too, and is there any way to fix it? Is this an xmir/mir/Xorg thing?

Hey Florian, thanks for the heads-up!

I followed the instructions on a windows 7 pc (don't think that matters, but there you go ) and a Fairphone 2 running UT 15.04 devel r280

flashing went smooth, phone is up and running. i will keep an eye on stability.

i have been experiencing signal loss (take it out of my pocket, see an X on the signal indicator, unlock the phone, indicator jumps to at least a little signal. seems as though being in my pocket is enough to lose signal?) would this patch help with that too? lets wait and see...

The dualboot part is working as far as i can see. The problem is the image for nexus 10. it is broken, and even though it still churns out versions, it just does not get fixed. Somehow nobody wants to try and fix this. Fine, maybe it's just too broken to bother, but then at least be honest and remove that 90% functionality from the website.

At least you gave a means to dualboot a device with an ubports image, which is something. Thanks for your effort.

Yougo