Apps are suspended when in the background on UT so you can't trigger notifications in this state
Lol. Recently I tried to play music in the background and now I understand why it didn't work. That's a pity.
Are there currently any known plans on implementing those background services you're talking about?
2
Оkay, I'll check it out, thank you.
otherwise most clients would need to poll their servers
Well I don't think they'll actually have to poll it since stuff like real-time messengers is mostly websocket-based nowadays.
So, your push server is not something that app developers are forced to use in order to be able to send notifications, right? That is, can I write a Telegram client that will not depend on your notification server (while still being able to use notifications ofc)?
I just... don't understand how some things work.
Looks like this is the most relevant place for such questions here on the forum.
Push notifications.
If I understand it correctly, a notification has to go through the UBports push notifications server along with the token identifying the device that notification should be delivered to. Why so complicated? When I run kdialog --title "Hello world" --passivepopup "Foo bar" on my desktop, I don't need to obtain any token and send it back and forth, so why is it impossible for an app to just send some notification event directly to mir socket or something like that?
Gui apps running inside libertine containers.
Well, they perform veeery poor, at least on (my) Nexus 5. Is that OK? Will it get better if I attach an external monitor, or is it because of xmir?
By the way, as far as I know, xmir is abandoned, but mir is wayland-compatible now, so why even use xmir instead of xwayland which is still supported, or even use wayland directly where possible?
Well, I'm running 16.04 stable on asus-flo and willing to get anbox to work. I googled, and this guide from the official ubports documentation is what I have found.
According to the guide, however, nexus 7 is not supported. Time to forget about anbox?
But interesting fact - I have it installed out of the box! Here's the related apt output:
NOTE: apt purge anbox attempts to remove not only anbox-related stuff, but also ubuntu-touch*. Seems like one of them is a dependency of another?
The only problem is that, I can't find any systemd services related to anbox, hence not able to run it. All attempts to run anbox commands without systemd expectedly fail.
So, what is it? Is the guide outdated? Or perhaps there's something wrong with my ubuntu installation? Because if it's really not supported - why is it even installed? Help pls guys