Dekko's just an email client, right? New mail notification is a server feature. For me, I have an imap watcher which watches for new mail using the IDLE extension and pushes an XMPP message:
https://vsta.org/andy/pickup/xmpp_mail.py
and I have a web interface to XMPP so I can read from a browser anywhere:
https://github.com/vandys/webXMPP

The final part is a daemon running on my phone, and its counterpart on that webXMPP server. When my phone's active, it just does a popup notification with sound. When the phone's off, it also gets the LED's blinking. They turn back off when you unlock the phone. The server remembers the client, and as soon as new messages arrive, it does a notification push.

I guess I'm telling you that I don't see how an email client gives you push notifications. The best it can do is try to run in the background and poll an imap account. But Touch SIGSTOP's apps as soon as they lose focus (delta that UI tweak utility) which will fight you, and it's a waste of battery and data anyway. imap IDLE really isn't a great fit for a mobile platform.

It seems that there is such a package

https://launchpad.net/unity-voice

although this stopped being shipped after 15.10. Not sure why 😕

In any case I plan to have a look at it at some time.

@UKPhil thanks , yea you right. was a missunderstanding than.

Update...

During my trip, I had to switch back to my old phone due to a bug in the Python3 notification2 library. _closed_callback() was using an "nid" which wasn't in the notifications_registry any more. I coded some defensive logic and logging, and will see what's going on.

But with that workaround, I have been able to daily drive my Nexus 5 for the second day now. I'm able to keep real time notifications with one 150 byte packet sent and received every 2.5 minutes. It lives fine behind NAT, and also seems fine with the transition from Wifi to mobile data and back.

@hans1977se
Maybe it worked for me, because I used a Raspberry Pi with Ubuntu Mate. I'm not quite sure how the user and sudoers group management works there.

I'm pretty sure that by using a "fully prepared" working system, this error does not occur.

Ubuntu/Canonical colors are Ubuntu orange and Canonical aubergine. None of this colors has any role in the latest Canonical designs. None of this colors as well is present in the UI I think apart of Ubuntu logo button and Ubuntu Store icon. It may be present also in some apps that hasn't been updated for a long time.

I think that we retain the orange Ubuntu logo and Ubuntu wallpapers as long as the Ubuntu Touch name is kept. If the decision to change it is made or we are forced to do this, then the new branding for the OS should be created, consisting of new name, new logo and colors for it.

@UniSuperBox, last night I was going to post a study [0] OpenSource.com has published yesterday on 18 open source translation tools to localize your project but I saw in the telegram group that weblate is the winner already.

I don't have an special predilection for any tool.

Anyway here's the link just in case is interesting for someone.

[0] https://opensource.com/article/17/6/open-source-localization-tools

The issue has been filed, link for reference:
https://github.com/ubports/ubports-touch/issues/128

I have raised this in Github Github defect

@Flohack, OP3T comes with OxygenOS which is based in Android 6.x or Android 7.x depending version.

https://en.wikipedia.org/wiki/OxygenOS

This is not a feature, my Bq E5 also lost notifications at around the end of May. It looks like something cancels the registration of your Ubuntu One account in the Canonical notifications push server, and your device looses the notifications.

A workaround that has been reported to work is to delete completely your Ubuntu One account, create a new one, and register again Telegram with the new Ubuntu One account. Just creating a new account and registering Telegram again, without deleting the old account, has not worked for me (I cannot erase my old account since it is my Launchpad account and I have a lot of history there).

Now I have moved my daily device to a Nexus 5 and I have recovered Telegram notifications with my old account.

In any case who knows how long we are going to have Telegram notifications, as soon as Canonical decides to close the push server they will be gone for good. There is some discussion on how to implement a sustainable notification system (maintaining a push server seems out of the possibilities of UBports) here in the forums and in github.

@Flohack This command needs to be run on your mobile device, so first login into your device via ssh.

We have the general steps that an image goes through on this wiki page, but we do not have step-by-step instructions for setting it up yourself.

Thanks for that pointer, applying it to my Hammerhead tree did permit a build. What would have been my "hands on" Nexus 5 is busy with some highly interesting notification experiments, but I'll see if my built images boot RSN.

Hi,
since a young developer provided a Lineage OS 13.0 version for BQ Aquarius E4.5 maybe one could use this as a base to get a newer kernel?
I am not exactly sure what kernel version and what else is needed to get 16.04 working on Krillin but any insight in the requirements for porting to 16.04 would be heartily appreciated.

Here is the link to the Lineage OS porting guide:
http://www.cyanogenmods.org/forums/topic/lineage-os-13-aquaris-e4-5-krillin-marshmallow-rom/
Here are the links to the Github repository of the developer:
https://github.com/Pablito2020/android_kernel_bq_krillin
https://github.com/Pablito2020/android_device_bq_krillin

I am currently switching my Krillin from the Canonical to the UBPorts image, but if it helps I can also try out the LineageOS version.

When I read the title of this post, I started to get concerned. Was something going on, that I was not aware of, was the tablet going? Thankfully the answer to that is no. For me, the os on the tablet is the main thing. That being because it is all I use now, but to lose the os/support would be out of the question 