I'm far away from saying that there is no bug in Dekko2, but if finding below is a bug in Dekko2 or a new bug/feature/behavior in the OS is unclear. The high CPU utilization of dekkod is a result of reading from time to time again through one of its database files /home/phablet/.cache/dekko2.dekkoproject/database/qmailstore.db (39 MByte in size) with tons of llseek(2) and read(2) syscalls: [pid 22511] _llseek(9, 20623360, [20623360], SEEK_SET) = 0 [pid 22511] read(9, "\r\0\0\0\1\1o\0\1o\1\27\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024 [pid 22511] _llseek(9, 20625408, [20625408], SEEK_SET) = 0 [pid 22511] read(9, "\r\0\0\0\1\1v\0\1v\2\214\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024 [pid 22511] _llseek(9, 22777856, [22777856], SEEK_SET) = 0 [pid 22511] read(9, "\r\0\0\0\1\1s\0\1s\2\214\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024 [pid 22511] _llseek(9, 20626432, [20626432], SEEK_SET) = 0 [pid 22511] read(9, ^C"\r\0\0\0\1\1s\0\1s\2\225\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024 ... In it log file it says about this: [22511] May 13 07:24:41 [Debug] Action completed 96684008800466 result success [22511] May 13 07:26:39 [Warning] Would not determine server/action completing [22511] May 13 07:26:39 [Warning] Would not determine server/action completing [22511] May 13 07:26:40 [Debug] Running action ExportUpdatesRequest 96684008800468 [22511] May 13 07:26:40 [Debug] Running action ExportUpdatesRequest 96684008800469 [22511] May 13 07:26:41 [Warning] Unable to process malformed message removal record for account 4 [22511] May 13 07:26:41 [Warning] Unable to process malformed message removal record for account 4 [22511] May 13 07:26:41 [Warning] Unable to process malformed message removal record for account 4 [22511] May 13 07:26:41 [Warning] Unable to process malformed message removal record for account 4 [22511] May 13 07:26:41 [Warning] Unable to process malformed message removal record for account 4 .... I think it's time to remove the Dekko2 installation completely and start again from scratch. The PITA is that there is no way to keep the configuration, one must configure all by hand from scratch. This is really a bug in Dekko2.

On meizu 5 pro plus, the media player gives the same error after upgrading to OTA-9 No meizu 5 pro plus, o media player dá o mesmo erro depois da atualização para o OTA-9 https://github.com/ubports/ubuntu-touch/issues/1140

@Stefano updated the latest version of tools. it's worked well.

@dtarrant These are the options offered by File Manager for opening an image file. Image Viewer is top row, third from left with daisy/magnifier icon. A picture is worth a thousands words!

I have so much respect for the core devs. I can see how much work they have done on the camera on Nexus. It is quite obvious that some of the manpower / brainpower is allocated on improving camera capabilities of the promoted devices. One of the things I appreciate the most about UT mobile OS is that it comes with CLI which enables me to connect to my Raspberry Pi wirelessly and control it. Not 100% sure if iPhones or Androids have an app for this but on UT it comes by default.

@maxinova2001 Thanks for the tips.. I appreciate all help..

adb shell tail -f /var/log/syslog

@advocatux Ok. As i haven't the knowledge to know if it is an old or a new issue, i have reported it. https://github.com/ubports/morph-browser/issues/183

@dln949 If the screen is bowed, it must be that the battery has died and increased on size i'm afraid, i had the same recently on a macbook for which the keyboard started sticking out and the the trackpad was not responsive anymore

Disregard, I found a solution. In /usr/share/unity8/Shell.qml ln:468 width: parent.width > units.gu(60) ? units.gu(40) : parent.width increasing '60' to '70' did the trick

The linked demo looks cool. Just one request to whoever is going to prepare similar videos: Please, do not open a CLI in a UX demo! (Or more generally, when targetting non-developer audience.).

@guru said in Dekko 2 account settings: @gdegrez said in Dekko 2 account settings: Incomming: Server name: pod51010.outlook.com ok Username: username@company.com ok Port: (443 ?) 993 Security: SSL/TLS ? Force encryption (SSL/TLS) Authentication PLAIN Outgoing Server name: pod51010.outlook.com ok Username: username@company.com ok Port: 587 ok Security: SSL/TLS Encryption: Use encryption (STARTTLS) Authentication: LOGIN Autheticate from server capabilities: ok Allow untrusted certificates: ok HIH The same config works in my BQ M10FHD with the old Dekko.

@advocatux Here is the script i use fyi: #! /bin/bash sudo mount -o remount,rw / sudo apt-get update sudo apt-get install --only-upgrade syncthing sudo mount -o remount,ro /

@alan_g said in xev like tool to see key_press (...) events: They'll be on github or gitlab (UBports are migrating projects from one to the other). I suspect you are misunderstanding me: OSK is not the solution you asked for, but it is the only process that does anything even vaguely like what you want. So, if you figure out how it is able to do that, you might be able to use that knowledge to create something new to remap input. No, I didn't misunderstood you. I wanted to look into OSK to see which key-events are arriving there and what is assembled of them to route it to the apps. I suggest that writing a new terminal app (or enhancing the existing one) with the ability to remap input would be far simpler. Focus on the terminal-app could be done only when the events are arriving in it on a low level. In addition would mean that any other app could not be see the key-events which are possible with a BT keyboard. In the past I expanded already the mapping for the terminal app with json files like: { "name" : "mutt Keys", "short_name" : "mutt", "buttons": [ { "main_action" : { "type": "key", "text" : "ESC", "key" : "Escape" } }, ... Maybe a first step would be add some logging in the terminal-app to understand what chars are arriving there from a BT keyboard (not only from the OSK).

Hi @zlamalp, I have to tell you that my solution is not really working. Indeed, when I gave you my answer, I've forgotten that I had changed the way I create the /sbin/sogosync file. In fact, after the creation by running the original script, I modified this file manually in console mode : sudo mount / -o remount,rw sudo vi /sbin/sogosync Then I edited the file in order to fit with the following lines : export DISPLAY=:0.0 && export DBUS_SESSION_BUS_ADDRESS="$(ps -u phablet e | grep -Eo 'dbus-daemon.*address=unix:abstract=/tmp/dbus-[A-Za-z0-9]{10}' | tail -c35)" && /usr/bin/syncevolution data_base_name Note : in the above line data_base_name is to be replace by the name of your database. Then at each execution by cron daemon, the string DBUS_SESSION_BUS_ADDRESS is evaluated. It would be nice if the original script would be able to put this line in the file itself but I'm not an expert in shell programming so I've no solution to propose.

Nevermind, my data seems to be working now without it.