I configured now and restarted dekkod as: phablet@ubuntu-phablet:~$ cat ~/.config/dekko2.dekkoproject/dekkod.conf [FileLog] Enabled=1 Path=/home/phablet/dekkod.log [LogCategories] IMAP=0 Messaging=0 POP=0 SMTP=1 [StdStreamLog] Enabled=0 [Syslog] Enabled=0 phablet@ubuntu-phablet:~$ restart dekkod dekkod start/running, process 26955 The resulting log is very good and I'm familiar with such SMTP logs from sendmail and other MUA: [24252] Feb 02 12:39:16 [Debug] Running action TransmitMessagesRequest 107185203838979 [24252] Feb 02 12:39:16 [Debug] SMTP : newConnection [24252] Feb 02 12:39:16 [Debug] SMTP : Open SMTP connection [24252] Feb 02 12:39:16 [Debug] SMTP : RECV: "220 ms-10.1blu.de ESMTP Exim 4.86_2 Ubuntu Sat, 02 Feb 2019 12:39:15 +0100" [24252] Feb 02 12:39:16 [Debug] SMTP : SEND: "EHLO [127.0.0.1]" [24252] Feb 02 12:39:16 [Debug] SMTP : RECV: "250-ms-10.1blu.de Hello ppp-88-217-102-34.dynamic.mnet-online.de [88.217.102.34]" [24252] Feb 02 12:39:16 [Debug] SMTP : RECV: "250-SIZE 104857600" ... Now I have just to wait and catch the next send resulting in Drafts ...

@krille said in missing xmpp and a very slow install in libertine: In my opinion XMPP is not suitable to replace a messenger like Telegram or Matrix on mobile... mhmm as @dobey already said...

@guru I would for now carry on with that thread as only the name space has changed for the app. Development carries on the same. Lets keep it all together for now.

@kugiigi I don't think it does. There are desktop actions defined in the morph-browser.desktop file, but they are nevertheless not shown.

@jelkner I would rather have you working with us on the problem if you like. It might be some insights for you in how UT works, and for us an opportunity to recruit a new community contributor Would you mind bringing one of the OPOs back to Android, to see whats the MAC address there? We definitely need to find out where Android gets it from. Also for Bluetooth, see this bug: https://github.com/ubports/ubuntu-touch/issues/955

Thanks a lot for your answers!!! Rg LOTR

@lakotaubp Thank you for tips, I finally got it to come back on. After trying a bunch of things, what ended up working was plugging it in to my computer at work, I left it plugged in for a few hours, hit the power button and it showed the battery icon, almost fell out of my chair, held the button and it fired right up. Not sure why, but it's on and working again so I'm happy.

Ah! Okay. That makes sense then, @mic_ !

The negative tone starts at your post title ("a sad story") and then continues. What it's "a clear picture" for you, maybe other people see it just as a grumbling because you're using some adjectives that are not really necessary to describe a technical problem. Anyway, it's way better to fill an issue, that's true.

For example, Logitech M535 works fine: https://www.logitech.com/de-de/product/bluetooth-mouse-m535?crid=7

If anything else fail, try to install with good old '' ubuntu-device-flash '' tool. It worked for me as a last stance, when everything else would just not work.

@cj_c Pleased to hear it. We have a good helpful community here.

@dobey this is also what I saw on the OpenStore !

I use Rudi timmers gmail app and it works well in Xenial. regards....

@dobey hi ! this is what behavior I also expect ! I will try it soon. thanks!

I think it's time to debug and nail this down. I found the file /etc/init/wpasupplicant.conf which spawns the WPA daemon as: exec /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant I will mount the /root in this test device writeable and change the line to: exec /sbin/wpa_supplicant -dd -u -f /var/log/wpa_supplicant.log -O /run/wpa_supplicant to gather the debugging output in a file. Update: It's not necessary to mount /root writable. The proc init starts and re spawns that proc when it dies. With a bit of luck you can fire up these three lines from a shell script and get your version of WPA up before init can restart its own: #!/bin/sh pkill -9 -f '/sbin/wpa_supplicant.*' wpa_supplicant -dd -u -f /var/log/wpa_supplicant.log -B -O /run/wpa_supplicant exit The lines in the log files look promising...

I can confirm that setting up a DavMail in server mode & using it as a caldav gateway to exchange works fine I've tried it on an f-droid only version of Android without Exchange provider Only tried caldav but no doubt the other gateways DavMail provides would work too If it works on android, no reason why it wouldn't work for UBPorts It'd be nice to have it on-device though, maybe DavMail could be repackaged in some way to provide the required Dav gateways to Exchange I know it's java based though, so might be too heavy to run in the background on a mobile device But it's a thought