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

@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.

Hello everyone,

I'm Matej from Slovakia, I'm 37 years old. For few year I've used UT on bqE5 maintained by Canonical. Recently I've bought new phone FP2 and I've installed UT by Ubports. I'm familiar with linux (10 years no other OS) and I'm using Ubuntu on all my devices. I've a degree in cybernetics and I think I'm slight above average in reading/writing code. I'm familiar with C++ (I hate it), Pascal/Delphi (this was long time ago), PHP (along with html/css/js for work), SQL (for work), Matlab (long time ago for school) and Go/Golang (my current favourite). I've tried other programing languages (Python, Haskel, Java, ...), but I'm just above beginer level in them.

I'm willing to do some help with Ubuntu Touch, so be patient with me and I'm looking forward to make UT better with you.

PS: I speak Slovak, English and German and I'm currently learning Japanese (fresh beginer).

@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?

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:/# 

I overcame my touch difficulties after screen break with usb keyboard some time ago.

@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.

I had this idea, that I presented in github issue:

I think, the touch area should dynamically expand to the left, until the last item of the possible menu. If there's no menu, the touch area is the whole notification bar.

Is this dynamic behavior possible? Where should I start (repo & how to), if I want to experiment on this idea?

@hummlbach Thank you, that's the issue I have been (unsuccessfully) looking for. Will continue there.

@3arn0wl I too think, that menus at the top of the window are better. In Unity7 was a switch somewhere in preferences, where you could choose if the menu is on the top of screen or window. I think that's the goal we should reach/hope for.

Hello, I have encountered some inconsistency in indicator pull down behavior after rc channel upgraded to new Unity8 (which happened after rc update to version 63).

Before I could pull down the indicator even by swiping down from empty space (left from most left indicator icon = notification icon). Indicator was pulled down with notification tab opened.

Now I can't pull down the indicator from blank space. I have to start the swipe exactly on the icon, to pull down the indicator.

I have tried to search forums & github issues, but found no mentions about this. So I write here first.

Q1: Does anybody experience this behavior after update?

Q2: Is this a regression, or intended behavior?

EDIT: solved in rc/ver. 70)

@Luksus Wow, that worked. You are a savior. Thank you.

@TobsEnd No, this issue was not always on my FP2. After I bought the phone in summer 2018 an immediately installed Ubports touch and video recording and playing was not a problem for about a year. Then suddenly I noticed, that video playback in gallery and media player is not working, even for videos I played a week ago. I thought, that it is some update issue, so I waited some time and then I started this thread.

Q: How do I test if this is a hardware issue? The only way, that comes to my mind is to install android and test video playback, but how do I know it's usind HW decoding instead of SW, if the video plays?

Hellou. Today I have tried to reinstall ubports, to see if something changed for video playback. I have installed android back using fairphone 2 android manual install technique. After android was working, I used ubports installer to install ubports touch 16.04/rc (version 63). Everything went smooth and I have latest OS from rc channel. But I still can't play videos on FP2 using gallery or media player.

Q1: Are there any Fairphone 2 owners, who are using Ubuntu touch OS and can't play videos, as I do? Or you have a FP2 and can shoot and play videos without any problem?

Q2: I didn't choose the wipe user data during install. Can the user data affect video playback and cause some problems?

I have succeed to make adaptive style transfer work in libertine container. I mean only the style transfer part, not the learning part (which I haven't tried, maybe that can work too).

There was one caveat though. It consumed too much memory and crashed/restarted unity on my FP2, when ran from terminal on the phone, so it couldn't finish. But if runned through ssh connection, the unity crash/restart did not affect the process, so it succeed.

I have browsed through morph-browser code, especially the parts, were environment variable or command line arguments processing occurs and I could not find any part, that changes the zoom factor from outside app. I'm afraid, there is currently no way to change zoom factor at webapp start (maybe I overlooked something and I'm wrong).

However, it can be implemented. The fastest way is to implement it yourself & then send an pull request. Or, if you are not confident in your current skills, fill a bug report an wait.