This is a place to coordinate developers working on dekko2. (It is not the place to discuss individual bugs)

In the good old days we had dekko and it mostly worked ok. At some point a rewrite as dekko2 was deemed necessary. The rewrite was started but not completely finished. In addition the platform has moved on beneath dekko (xenial). Time has gone by and development rate of dekko has dropped.

As of today, there is no working dekko for xenial UT.

Over the last couple weeks I see here and there on various UT telegram channels messages pop up about various people trying to work on dekko. Some wrestling with the build system. Somewhere a test build showed up. Some critical bugs were mentioned (settings, system load). Workarounds and some fixes too. I think it's time to coordinate efforts. So we don't independently solve the same problems multiple times, but instead move forward faster.

So all you dekko2 hackers, speak up below with whatever you do / did on dekko2. What you need help with.

Let's make it happen!

PS: This is not an attempt to hijack the project from the current maintainer @DanChapman . Personally, I think the best future for email on UT would be a Dan maintained dekko2 with a small community of developers cooperating. Dan seems to be on a hiatus right now. Let's see what the future brings.

PPS: If you are not actively developing on dekko, then help us stay focussed by not going off topic here! Maybe you really want to encourage people to work on dekko. Or maybe you are very frustrated because you really need an email client. Well, yes, we know. We all are. Feel free to up (or down) vote posts. Or maybe you want to report an issue or suggest a feature. Then use the bug tracker. Or you just have a question. Then start a new thread or go here https://forums.ubports.com/topic/1750/dekko-0-1-6-beta2-released/1

I almost don't dare to ask, but .... Qt update?

It is our pleasure to announce the release of Dekko2 for Xenial

You find it in the open-store on your device and at https://open-store.io/dekko2.dekkan

Yes there are still bugs. We know, but it should definitely be good enough to allow you to read and write your emails from UT.

Try it out and feel free to praise or curse us below. Let us know what you think.

Bugtracker is over here: https://gitlab.com/dekkan/dekko/issues
Source code: https://gitlab.com/dekkan/dekko
Dev thread: https://forums.ubports.com/topic/1477/dekko2-developer-community-thread

PS: Yes, patches are welcome

Pick one (any) convergent user story and make it a perfect experience out of the box.

For example: I receive an email from a coworker asking me to work on some spreadsheet. Dock phone and work desktop style, listening to music on my headphones. Realise I miss some info. Text another person with a question. Receive a phone call interupting me. Take the phone out of the dock and talk while I walk to the coffee shop. End the call and finish the spreadsheet on the phone/tablet interface in the coffee shop. Email the file back.

All those features are kinda there, but there are a bunch of usability features that kill this (and similar) workflows. I would suggest you draft a story like this, then test it and prioritise any bugs you run into. Docking ain't reliable - fix this. Email app closes and interrupts my drafting when switching to browser /spreadsheet - fix that. Out of the box UI scaling for localc doesn't allow me to work efficiently on a tablet display - fix it.

No need to make everything perfect, but pick one story and maybe one device and make that one really shine. If it ain't the "mobile office work" above it could be the visual artist - now you need to make sure that krita works perfectly on the tablet - does taht require better touch input in xmir well then this is your top prio feature. Or maybe its wayland on mir. The user is not gonna care as long as the workflow is awesome.

Pick a story that is achievable, but sets ubports apart from ios/android. Getting krita to run is too hard - what about preparing, adjusting and giving a presentation from the phone including live pdf annotation xournal style.

Make sure to produce a release video that shows off! Focus on the added value for the user instead of the technical feature of how you adjusted the dpi for Xmir or whatever.

I'm trying to get Halium running on the Nexus 7 2013 gsm variant "deb".

I've made a few steps already. Most notably: Plasma Mobile starts!

I'm keeping (and updating while I progress) the summary below, so that:

• I don't forget what steps I took
• Others can help to improve this
• Others can use this as inspiration for their ports

Setup sources

• Follow the Porting Guide for halium-7.1 here https://docs.halium.org
• lineageos kernel sources: https://github.com/LineageOS/android_kernel_google_msm
• my local_manifest: https://gist.github.com/doniks/7ee302c7792450761332d8f8712f29f6
• binaries : https://developers.google.com/android/nexus/drivers MOB30X
• my repo with all kernel changes: https://github.com/doniks/android_kernel_google_msm

Kernel image

config

source build/envsetup.sh 
add_lunch_combo lineage_deb-userdebug
lunch lineage_deb-userdebug

• kernel config: kernel/google/msm/arch/arm/configs/lineageos_flo_defconfig
• Primary source to check for wrong configs: https://github.com/lbt/mer-kernel-check
• my kernel config: https://gist.github.com/doniks/7406a87e5f15e1eab5a64aa90ad8f633
• other config checkers for reference:
  • CONFIG=out/target/product/deb/obj/KERNEL_OBJ/.config lxc-checkconfig
  • https://github.com/janimo/phablet-porting-scripts/blob/master/kernel/check-config

patches

• https://gist.github.com/doniks/75d16dda43d241feb79b721bab6c4940

• https://gist.github.com/doniks/44faf86a23f7467b80744f033fb08100

• add cgroup_disable=memory to the HYBRIS_BOOTIMG_COMMANDLINE in halium/hybris-boot/Android.mk (this fixes some problem with systemd/cgroups, can't remember what exactly )

common porting errors

• Halium Porting Error Knowledge Base
  https://gist.github.com/doniks/2ac14a1bb6750165bf782f62139c8aab#file-gistfile1-txt-L61
• Reference of older kernel versions http://elixir.free-electrons.com/linux/v2.6.39.4/source
• [https://public.etherpad-mozilla.org/p/r.0aae797a3bd13b4cd923b82fe29a2f47](Sailfish HADK FAQ)

test and debug

• Follow steps here http://docs.halium.org/en/latest/porting/debug-build/
• if you want to force init into telnet, add kernel parameter bootmode=debug:

fastboot -c "$(abootimg -i hybris-boot.img | sed -ne '/cmdline/s/. cmdline . //p' ) bootmode=debug" boot hybris-boot.img

Android image

cd halium
mka systemimage
ls -l out/target/product/deb/system.img

Rootfs

Halium rootfs

get it

• https://docs.halium.org/en/latest/porting/install-build/reference-rootfs.html

install it

• to install the rootfs you need working adb. I use this twrp recovery: https://eu.dl.twrp.me/deb/twrp-3.0.2-0-deb.img.html (had some problems with 3.1.1-0)
• boot into twrp recovery

git clone https://github.com/Halium/halium-scripts
./halium-scripts/halium-install halium-rootfs-20170630-151006.tar.gz halium/out/target/product/deb/system.img 

• The device should reboot and get to the point where it announces usb networking:

lsusb -vd 0fce: | grep -i serial
  iSerial                 3 GNU/Linux Device on usb0 10.15.19.82

• reboot into twrp recovery to set the root password

adb shell
cd /data
mkdir mnt
mount rootfs.img mnt/
chroot mnt /bin/bash 
export PATH=/sbin:/bin:/usr/sbin:/usr/bin:$PATH
passwd

connect to it

• reboot the device and wait for usb networking to come up as above
• configure usb network on your desktop in a similar way as above for telnet, but now for ssh

sudo ip address add 10.15.19.1 dev enp0s20f0u7 
sudo ip route add 10.15.19.82 dev enp0s20f0u7

• login via ssh

ssh root@10.15.19.82 

• fix path variable

echo $PATH
/usr/bin:/bin
export PATH=/usr/sbin:/sbin:$PATH
echo 'export PATH=/usr/sbin:/sbin:$PATH' >> /root/.bashrc

what works

• test_lights makes the led breathe
• EGL_PLATFORM=hwcomposer test_hwcomposer shows rotating spiral! I need echo 200 > /sys/class/leds/lcd-backlight/brightness to turn up the display brightness, so I can actually see the spiral
• wifi: http://docs.halium.org/en/latest/porting/debug-build/wifi.html

nmcli d # no wlan0
echo 1 > /dev/wcnss_wlan 
echo sta > /sys/module/wlan/parameters/fwpath 
nmcli d # shows wlan0
nmcli dev wifi # list wifis 
nmcli dev wifi connect <SOMEOPENWIFI>
# or
# sudo nmcli device wifi connect <SOMEENCRYPTEDWIFI> password <PASSWORD>
ping -c 2 8.8.8.8
ping -c 2 debian.org
# install some missing packages
apt update
apt install openssh-client bash-completion command-not-found binutils nano

• buttons: evtest /dev/input/event5
• touchscreen: evtest /dev/input/event0
• adb:
  • TWRP
  • chroot into rootfs
  • systemctl enable adb
• test_egl_config : https://gist.github.com/doniks/4e9ea8a8f5aaf1968c2e42846b5a9158

what doesn't work

• test_audio nothing to hear

ACDB init open file failed
[ACDB Init]->File is not found on the system
[ACDB Init]->ACDB init success!

• test_camera

library "libcamera_compat_layer.so" not found
Segmentation fault

• test_egl segfaults
• test_glesv2 segfault
• test_gps, honestly I don't know whether that output below constitutes success of failure ... since I can't recognise any coordinates, I think it failed. I've waited 5 minutes or so. There are more *** tracking lines but no coordinates

*** setup signal handler
*** get gps interface
*** device info
 id = gps
 name = loc_api GPS Module
 author = Qualcomm USA, Inc.
*** init gps interface
*** set capabilities
capability is 00000007
 ** Creating thread: 'Loc_hal_worker' (start=0xb69f23b5, arg=0x1d02080)
 ** After thread_create: 'Loc_hal_worker', error=0 (start=0xb69f23b5, arg=0x1d02080)
 **** Thread wrapper start (start=0xb69f23b5, arg=0x1d02080) ****
*** setting positioning mode
*** start gps track
*** gps tracking started
*** tracking.... 

• test_input

library "libis_compat_layer.so" not found
Segmentation fault

• test_media, get a video from http://bbb3d.renderfarming.net/download.html

wget http://download.blender.org/peach/bigbuckbunny_movies/big_buck_bunny_480p_surround-fix.avi
wget http://distribution.bbb3d.renderfarming.net/video/mp4/bbb_sunflower_1080p_60fps_normal.mp4
scp bbb_sunflower_1080p_60fps_normal.mp4 root@10.15.19.82:
ssh root@10.15.19.82
test_media bbb_sunflower_1080p_60fps_normal.mp4
library "libmedia_compat_layer.so" not found
Segmentation fault

• test_nfc

Starting test_nfc.
Finding NFC hardware module.
test_nfc: test_nfc.c:156: testNfc: Assertion `hwModule != NULL' failed.
Aborted

• test_recorder

Test application for video recording using the camera
Recording start with volume up button. And stops with volume down.
The result is stored to /root/test_video.avi

library "libcamera_compat_layer.so" not found
Segmentation fault

• test_sensors

library "/system/lib/hw/sensors.oem.so" not found
libsensor_add_waiting_client adding cb 0
Hardware module ID: sensors
Hardware module Name: Qualcomm Sensors Module
Hardware module Author: Qualcomm Inc.
Hardware module API version: 0x1
Hardware HAL API version: 0x100
Poll device version: 0x1000001
API VERSION 0.1 (legacy): 0x1
API VERSION 0.1: 0x65537
API VERSION 1.0: 0x16777217
API VERSION 1.1: 0x16842753
API VERSION 1.2: 0x16908289
API VERSION 1.3: 0x16973825
API VERSION 1.4: 0x17039361
libsensor_add_waiting_client adding cb 1
Got 0 sensors

• test_wifi 1 says :

Cannot load driver (err -1)

not supported

• test_vibrator , segfaults, but anyway the N7 doesn't have a haptic motor to vibrate

Segmentation fault

UBports rootfs

Tried the rootfs from here: http://cdimage.ubports.com/rootfs/ but it doesn't do too much for me:

• screen stays on the Google logo
• no usb iSerial messages
• no usb network interface seems to come up
• last_kmsg shows that systemd does take over http://paste.ubuntu.com/25419054/ however,
• it complains that "systemd[1]: Failed to start LXC Android Config and Container Initialization."
• no adb interface comes up, even though in TWRP/chroot I see that android-tools-adbd.service is enabled

Plasma mobile rootfs

git clone https://github.com/bhush9/rootfs-builder bhush9-rootfs-builder
cd bhush9-rootfs-builder
# follow the instructions in README to patch lb_chroot_live-packages
sudo ./build.sh
# waaaaait
# install it

The reboot takes about a minute. Then you'll hear an audible greeting and afterwards you are greeted by the plasma mobile login screen. You can login and play around a bit. Not much to do though. No network connection and it's not possible to ssh in.

Reboot back into TWRP and chroot.

1. To be able to use the ssh server, you need to generate ssh server keys: dpkg-reconfigure openssh-server
2. Preferably enable password less login :

adb shell mkdir /home/phablet/.ssh
adb push ~/.ssh/id.pub /home/phablet/.ssh/authorized_keys
// todo : some chmod/chown needed?

1. reboot, setup usbnet and then reboot and login as ssh phablet@10.15.19.82
2. Alternatively, you can set the passwords, but I don't do this because it seems to actually break the graphical login:

passwd 
passwd: Authentication token manipulation error
passwd: password unchanged
# fix passwd
apt remove libnss-extrausers
pam-auth-update 
# select everything but extrausers
passwd # set root password 
passwd phablet # set user password

Debian

Haven't tried yet.
https://archive.org/download/halium-debian-rootfs/
https://github.com/JBBgameich/rootfs-builder/tree/debian

Arch

https://github.com/Halium/rootfs-builder/tree/archlinux
https://github.com/mickybart/rootfs-builder/tree/archlinux
Haven't tried yet. I'm not very familiar with arch.

What's next?

• Get ubports to run
• Get PM to run on halium-boot
• Check out LuneOS
• Check out SailfishOS
• Build a .zip file, only makes sense if some OS is remotely usable, PM is close but still not there
• get lxc-attach to work
• patch out the noise dmesg logging of the battery

Any tips or feedback appreciated!

Oh and of course, the elephant in the room: How's 16.04 coming along?

Tell me. How awesome is it to work on one "real" recent Linux kernel for the Pine Phone instead of a dozen incompatible and weird and ancient Android hacks?

How big is your head- and heartache after seeing the responses to your thread: Want To Develop UT And Need A Device?

Enjoy your real lives guys. Well deserved. And thanks for the continuous updates!

@3arn0wl said in PinePhone:

is it right to assume that the PinePhone, being a Linux phone, won't need Libertine to run Xorg apps?

No. It is "more" of a Linux phone than others that run some (old, forked) version of the Linux kernel in the sense that it runs a recent upstream version of the Linux kernel.

Everything that happens on top of the kernel is up to the distro you run. In the case of Ubuntu Touch, it will be Mir and Libertine. If you run Plasma, Lune, Postmarket, something else it will be whatever that distro provides

@Toadtoad said in Navigating (enabling developer mode) with broken screen (oneplus 3t):

@doniks
ls -l /system

total 88
drwxr-xr-x   2 root root 4096 2020-06-26 06:53 android
drwxr-xr-x   2 root root 4096 2017-01-10 21:46 bin
drwxr-xr-x   2 root root 4096 2016-04-12 20:14 boot
lrwxrwxrwx   1 root root   14 2020-06-26 06:53 cache -> /android/cache
lrwxrwxrwx   1 root root   13 2020-06-26 06:53 data -> /android/data
drwxr-xr-x   3 root root 4096 2020-06-26 05:28 debian
drwxr-xr-x   4 root root 4096 2020-06-26 05:24 dev
drwxr-xr-x 110 root root 4096 1973-06-18 14:58 etc
lrwxrwxrwx   1 root root   16 2020-06-26 06:53 factory -> /android/factory
lrwxrwxrwx   1 root root   17 2020-06-26 06:53 firmware -> /android/firmware
drwxr-xr-x   3 root root 4096 2020-06-26 05:32 home
drwxr-xr-x  19 root root 4096 2020-06-26 05:28 lib
drwx------   2 root root 4096 1970-01-01 00:00 lost+found
drwxr-xr-x   2 root root 4096 2020-06-26 05:23 media
drwxr-xr-x   2 root root 4096 2020-06-26 05:23 mnt
lrwxrwxrwx   1 root root   12 2020-06-26 06:53 odm -> /android/odm
drwxr-xr-x   3 root root 4096 2020-06-26 05:31 opt
lrwxrwxrwx   1 root root   16 2020-06-26 06:53 persist -> /android/persist
drwxr-xr-x   2 root root 4096 2016-04-12 20:14 proc
drwx------   2 root root 4096 2020-06-26 05:32 root
drwxr-xr-x   8 root root 4096 2020-06-26 05:31 run
drwxr-xr-x   2 root root 4096 2020-06-26 05:32 sbin
drwxr-xr-x   2 root root 4096 2020-06-26 05:23 srv
drwxr-xr-x   2 root root 4096 2016-02-05 09:48 sys
lrwxrwxrwx   1 root root   15 2020-06-26 06:53 system -> /android/system
drwxrwxrwt   2 root root 4096 2020-06-26 05:32 tmp
drwxr-xr-x   2 root root 4096 2020-06-26 06:53 userdata
drwxr-xr-x  10 root root 4096 2020-06-26 05:23 usr
drwxr-xr-x  11 109  113  4096 2020-06-25 12:57 var
lrwxrwxrwx   1 root root   22 2020-06-26 06:53 vendor -> /android/system/vendor

Now, this looks like UT! I am so surprised.

Should I reinstall UBPorts?

No, no need. Seems you were correct earlier! Just double check that there is a home/phablet folder in there then it is 100% that this is UT. Then find the passwd executable. It has to be in any of bin sbin usr/bin usr/sbin I'm sure. Then chroot /system and change phablet's password using that passwd that you just found.

PS: Could you do me a favor? It's not really relevant for your passwd/ssh question, but it would help me understand how this halium port is put together. Can you paste ls -l /system/var/lib/lxc/android (or without the leading /system if you are inside the chroot)

@Toadtoad thanks for the clear post!

The first step of the guide you linked involves the following the command: mount /data/rootfs.img /a, which outputs that rootfs.img does not exist.

oh. uhh. I am really surprised. You are positive that UT is installed right? Maybe things are not working as I thought they are Can you show ls -l /system?

There is a thread about the oneplus 3t in the porting - devices section. People there should know how to chroot in

@Toadtoad said in Navigating (enabling developer mode) with broken screen (oneplus 3t):

@doniks I booted into TWRP. Opened up the adb shell and did the following:

yeah that doesn't sound right. up front please add pwd and ls -l before you mount, otherwise it's kinda hard to know from the distance what actually gets mounted where

twrp mount system
chroot system

the more I think about it, I think ALL halium ports use an image file and not the system partition. it looks like you are mounting the partition.

please show ls -l / inside the chroot, then we can be sure

PATH=$PATH:PATH

not sure, what you are trying to achieve here ... I don't think it does what you think it does ... I think you are adding the literal string ":PATH" to the end of the $PATH environment variable which doesn't make much sense.

However, since you are not using export I also think it does not affect the lines following, so it is (luckily/unluckily) immaterial

passwd phablet

And I got /bin/sh: 3: passwd: not found

Since it doesn't seem like I'll set up adb or ssh, any suggestions to run headlessly on my phone? Thanks.

You're jumping to conclusions.

Please do (I'm just typing from memory, so be careful when copy/pasting and give us relevant output to help you)

ls -l / 
cat /etc/fstab
mount 
mount /data 
ls -l /data 

then please see here how to chroot into a halium rootfs http://docs.halium.org/en/latest/porting/debug-build/logging-in.html?highlight=chroot#logging-in

and again, just to make sure we are on the same page, please ls -l / once inside the rootfs

@Toadtoad said in Navigating (enabling developer mode) with broken screen (oneplus 3t):

I chrooted in TWRP, but passwd was not in the /system/bin directory.

Can you paste exact steps you took and output? passwd should be there. If you are looking at a folder called '/system/bin' then you are looking at the wrong place. I don't think such a folder exists INSIDE the UBports system image/partition (not sure which one the OP3t has.., so again, please post steps verbatim!). It should be in a "normal" Linux location, something like /bin /sbin /usr/bin /usr/sbin don't have a device in front of me.

And while I'm sure you should be able to get passwd working, I'm not sure UBports is the best system for a "headless" (broken screen) system. It is designed for touch input. With Halium it should be possible to put other systems on it as well ... I'm a bit out of the loop, but at some point there was a debian version and for sure there is plasma mobile, which may or may not work easier in headless style.

for the password, I think you should be able to boot twrp, connect with adb, mount the system, chroot into it and then passwd phablet.

for ssh, maybe some of this stuff helps: https://gitlab.com/ubports/community-ports/pinephone/-/issues/104#note_360710771

this should be the steps to get ssh https://gitlab.com/ubports/community-ports/pinephone/-/issues/104

@TartanSpartan said in Concerning Libertine and it's status within the Ubuntu Touch OS:

with a switch from Xmir to Xwayland among other improvements will return all applications within the Libertine container to full functionality.

Well, it's not like Xwayland is a silver bullet that will guarantee that there are no bugs and give you an awesome user experience right out of the gate

I could do this soon, easily enough, yep. For the reasons you suggest. Albeit I do think many of the developers do understand what the issues are, given their comments about them on Git.

Awesome! You know, sometimes developers disappear and others show up. It's a community and not a life sentence.

@dobey said in OTG Ethernet:

@doniks said in OTG Ethernet:

In order to fix that one would firstly require the ability to compile a new kernel, but the kernel sources for this device are not publicly available, so might be the e4.5 is a no-go.

Yes they are. They must be, otherwise UT would not run on it. It's at https://github.com/ubports/kernel_krillin

ohhh. i didnt know! i thought bq provided a binary kernel. now I see not only krillin, also arale, vegatahd, bq m 10 and turbo kernel sources are there. do we also have sources for the android layer for these devices?

I'm not sure, but it might require a driver that's not present on the bq e4.5 .

In order to fix that one would firstly require the ability to compile a new kernel, but the kernel sources for this device are not publicly available, so might be the e4.5 is a no-go.

On other devices that originally came with Android where the sources are available, it would be conceivable that the driver can be enabled with a recompiled kernel. But if the driver is not yet present in a working state in those sources (since Android manufacturers didn't care about enabling (not breaking) this driver), then you would be looking at a non-trivial task of enabling/backporting the driver.

On the pinephone your chances should be much higher to get this working since it is using a recent, almost-upstream kernel. But just to not to skip any bit of my half knowledge: on the brave heart edition of the pine phone there is some hardware issue related to OTG, which may or may not affect the ability to drive an OTG Ethernet adapter (see two forum posts in pine64 forum)

@TartanSpartan I think it might be worthwile to have Videos of this difference in UX. I mean the X+1 menu story. A video of the device (not a screencapture) might make it clear for (new) developers what was once possible vs today. I never had a M10 and I can't really picture in my mind what you are describing. I understand that its hard to translate menus into a touch interface without writing a new UI. It might help to have that documented