I the banner. Also kudos to everyone who participated and made this possible.

@krogoth I like @dobey 's answer. Cause it's not a simple 'no'. It is accompanied by some hints, how you can try to approach the problem, if you want to solve it. Keep going @dobey , excellent work.

@hummlbach Ok. I've decided. I'm ready to maintain the messaging app, if there isn't anybody else. I think I can read/write code, but I'm not familiar with the workflow of maintaining an app on UT. So what do I need to do/know for starters?

Hello there.

I made a pull request, to be able to build messaging-app with clickable tool. This can be usefull for develpoing and testing purposes. And who knows, maybe sometimes all apps come as clickable (snap, ...) packages and can be uninstalled to make UT more flexible.

I'm writing this, to bring a little bit of attention to the PR, to do some testing, if it can be accepted. Feel free to ask any questions.

@dtarrant I played with clickable and webapps few weeks ago .... this is the result: memrise webapp

After looking to my history, these were my steps to init, build & deploy to phone:
on notebook with Ubuntu MATE 18.04

1. install & setup clickable & docker

   sudo add-apt-repository ppa:bhdouglass/clickable
   sudo apt update
   sudo apt install clickable docker
   

2. go to your project dir & create project via clickable (project folder will be created)

   cd ~/projects/ubports/webapps/
   clickable init
   

3. after app creation was successful, you should see an dir created in your current dir with the name of the project you typed in clickable initialization. Enter the project dir

4. try to run (I've figured out, you have to use sudo to run docker)

   sudo clickable -e
   

5. edit files, play, debug, etc ...

6. to deploy to phone, there is a .click package (like appname.developername_1.0.0_all.click) in build folder in your project dir. If not use step 4. or build with

   sudo clickable --output .
   

   this produces a .click package in current dir & tries to copy it to your phone via adb.

on the Ubuntu Touch phone
0) upload .click package to your phone somehow, if not uploaded yet

1. install uploaded .click package via Ubuntu Twaek (or some other way)
2. have fun

So I found out it is possible to select messages in thread fo mass operations. But not as expected. Instead long-hold anywhere on message line, you have to long-hold on left (or right) edge of screen, or somewhere between 2 adjacent message bubbles. It is not every time, but 1 out of 5 attempts is successful, and select mode is turned on.

It is only on my fp2, or are you experiencing the same behavior on your phones too?

@Ghostrider said in Ubports with a jbl go speaker:

@advocatux I tried your suggestion, I've a terminal return : no space on /var/cache/apt/archives

This is normal for FP2, since last 2 or 3 OTAs. You can try to free some space using these commands extracted fom another post:

$ sudo mount -o rw,remount /
$ sudo rm -r /var/cache/apt
$ sudo tune2fs -m 0 /dev/loop0

If previous commands can't free enough space for /var/cache/apt/archives, you can temporary mount-bind the folder to somewhere else with more space, as described in this post:

$ sudo mkdir -p /userdata/system-data/var/cache/apt/archives
$ sudo mount -o bind /userdata/system-data/var/cache/apt/archives /var/cache/apt/archives/

After this you can try the @advocatux suggestion and it should work without free space problems. Maybe you will have more luck.

I tried the sudo ubports-qa install xenial_-_new-bluez, but it didn't finish and got stuck on bluetooth restarting. After rebooting, as I wrote in previous post, no improvement was observed. And because of the freezing on bluetooth restart, I couldn't revert things back with sudo ubports-qa remove xenial_-_new-bluez, so full image reinstall was needed. Has anyone more luck with this, as I had?

You can bind /var/cache/apt/archives temporary, using mount -o bind command.

# create dir in userdata space 
$ sudo mkdir -p /userdata/system-data/var/cache/apt/archives
# mount - bind
$ sudo mount -o bind /userdata/system-data/var/cache/apt/archives /var/cache/apt/archives/

Now your /var/cache/apt/archives has more space until reboot.

@advocatux said in Ubports with a jbl go speaker:

@Ghostrider there's a new bluetooth version for testing. If you know what you're doing and you are comfortable tinkering, you can give it a try. Run sudo ubports-qa install xenial_-_new-bluez. If after doing that your device gets stuck (because it's trying to restart bluetooth) you just need to reboot your device.

That new version works way better than the old one btw

I'm an FP2 & JBL GO user too and I can't use the speaker with Ubuntu Touch too. I've tried your advice and use new bluetooth version, but the outcome is the same. You connect to speaker, speaker beeps, that it is connected, but no music is allowed to play in music app, and you can't disconnect the speaker, or shut down bluetooth. You have to restart device.

However my other JBL Clip 2 speaker works with UT. And both, with the JBL GO speaker, are working with my Ubunu Mate 18.04 laptop.

@futurecn said in How to keep my python running in the container properly while the screen is locked?(N7 2013 flo):

I tried apt install screen on ubport and apt can't run.

You need to install screen into your libertine container.

$ libertine-container-manager install-package -p screen

Then you can run a screen session.

$ libertine-container-manager exec -c "screen"

NOTE: first time I got access permission error for /var/run/screen. You can fix this by logging into container and change permissions.

$ libertine-container-manager exec -c "/bin/bash"
root@ubuntu-phablet:/# chmod 777 /var/run/screen/
root@ubuntu-phablet:/# exit

After this, I was able to run a screen instance, deattach, bu no reattach success after libertine container was exited and run again.

# enter container, run screen and deattach
$ libertine-container-manager exec -c "/bin/bash"
root@ubuntu-phablet:/# screen -ls
No Sockets found in /var/run/screen/S-root.

root@ubuntu-phablet:/# screen -dmS worker
root@ubuntu-phablet:/# screen -ls
There is a screen on:
	30070.worker	(15.02.2019 17:57:40)	(Detached)
1 Socket in /var/run/screen/S-root.

# worker is in deattached state, reattach
root@ubuntu-phablet:/# screen -r worker

# Now I'm succesfully attaced to worker, using "ctrl-a d" to deatach again
[detached from 30530.worker]
root@ubuntu-phablet:/# screen -ls
There is a screen on:
	30530.worker	(15.02.2019 18:00:38)	(Detached)
1 Socket in /var/run/screen/S-root.

# exit container and reenter again
root@ubuntu-phablet:/# exit
 libertine-container-manager exec -c "/bin/bash"
root@ubuntu-phablet:/# screen -ls
There is a screen on:
	30530.worker	(15.02.2019 18:00:37)	(Detached)
1 Socket in /var/run/screen/S-root.
root@ubuntu-phablet:/# screen -r worker

Error: Cannot find master process to attach to!
root@ubuntu-phablet:/# 

@Luksus said in Fairphone 2 (FP2):

Since Fairphone managed to run Android 9 on the FP2, would it be possible to create a Halium 9 Port with this GSI thing?
https://www.fairphone.com/en/2020/06/18/fairphone-2-gets-android-9/

I've asked the same question on fairphone forum. The answer is:

No, because of
Halium version 9 is basically for phones released with android 8 or later, in other words devices with vendor partition.
The FP2 does not have a vendor partition.

Nice
There are some bugs. Most of the clickable commands in text are missing a space. Specifically clickablecreate, clickabledesktop and clickableupdate.

@dobey said in Compass in Device Checklist:

@jezek said in Compass in Device Checklist:
Abstraction on what level are you talking about?

In qtubuntu-sensors.

Thank you for reminding me. I forgot, there is already an issue opened on this.

@dobey said in Compass in Device Checklist:

Compass was never a requirement for core functionality of the system to work, so nobody ever implemented the abstraction for it.

Oh I see, thanks for clarifying. Another two questions.

Abstraction on what level are you talking about? The android LXC container does not handle the compass or the libhybris or the plaform API (reference image).

Is the fingerprint sensor the same case as the compass sensor? Or there was already some work done?

@dobey said in Compass in Device Checklist:

@jezek said in Compass in Device Checklist:

Hmm, you say that on some devices the compass works

No.

Having proper sensor support doesn't work on any device with UT currently (well, except maybe on pinephone) at the moment.

I don't understand your answer. Accelerometer or proximity sensors are sensors too and are working (in a way, that they can be used in ubports apps). What is the difference between compass sensor and them?

@dobey said in Xompass not working:

Compass sensor is not implemented on UT currently. Xompass only works on specific devices, due to the way it tries to read hardware.

Hmm, you say that on some devices the compass works. So it should be in the Device Checklist.

Another argument for adding compass to list could be, that Sensors: Fingerprint reader (among some other items) is currently not supported too and is in the checklist. It also would be a good remainder, that it is something, that sometimes needs to be done. Or am I wrong?

@cliffcoggin said in Xompass not working:

If you are real old school all you should need is a paper map and a magnetic needle in a glass case. (Which incidentally I still have and use.) Nevertheless I am happy to have GPS mapping and navigation in addition.

I carry an analog compass always in backpack (along with other useful stuff). But sometimes when I need really quick to know here north is, it's always hiding buried under other (in this situation unuseful) stuff. During my android times the phone was quicker.

Yes, GPS navigation is grat to have. I'm grateful for that. But I also think compass is good to have too, so I'm just trying to raise some awareness, so it is not forgotten.

@cliffcoggin said in Xompass not working:

...Oh well, it wasn't essential.

My personal opinion is, that compass (mgnetometer) is more essential than... let's say GPS. If I had to choose between them, I would choose compass. But maybe I'm just weird. Or just old-school?

Hello, there is a Device Checklist file, which hast to be used as template for reporting what's working and not working for some device port.

I think that Sensors: Compass is missing in the list. Or is compass sensor not supported by UT?

Note: I already filled an issue.

@cliffcoggin said in Space bar/key in search:

the rubber edged case I bought prevents swiping from any edge. Damn. I'll have to get something else.

I think, un UTTT, you can adjust the swipe area. Maybe it helps.