@lsitongia, as far as I understand, "Type C" only defines physical shape of a USB port. Inside it could be USB 2.0 or USB 3 or USB 3 + DisplayPort alt mode. Most mid-range phones only have plain USB 2.0/3.0 , and so video output is not supported.

Do you know, is that because it's the lower-cost version of the phone?

I think it definitely helps to reduce manufacturing costs. In case of Pixel devices the absence of physical video out ports also help advertising chromecast devices, I believe . Considering all the things I wouldn't count on support for video output over USB Type-C port on a phone by default, unless it is explicitly advertised in device specs.

@lsitongia Video output won't work because Pixel 3a doesn't support DisplayPort alt mode over USB. Other ports on the dock might work though (if Pixel supports USB OTG).

@kugiigi thank you for the feedback!
For some reason Seabass can't execute libertine-launch on Nexus 5, although libertine-launch works fine from Terminal. The problem could be somewhere in between seabass, pyotherside, libertine-launch python script and proot (used by libertine-launch), but unfortunately for now i don't know what exactly goes wrong.

Thanks everyone for trying the beta!

So far it seems that creating and building projects doesn't work on Nexus 5 or (maybe) on a subset of devices including Nexus 5. Unfortunately, I don't have a Nexus 5 so I can't investigate the issue further.

I can tell though that the issue doesn't depend on architecture (arm64/armhf) or OTA-version, but seems to be more device-specific.
To summarize: at least Nexus 5 seems to be in a list of devices that doesn't support seabass+clickable for now (which is a pity because it's one of a few devices that support connecting external displays). Poco F1 and Xperia X seems to work fine.

So, if you've tried the beta on any device other then Nexus 5 and creating projects from within the Seabass doesn't work, I'd be grateful for any information about your device!

@kugiigi said in Feedback for the Seabass:

Then I tried manually installing clickable in the container via the settings app.

Hm, I've just realized that installing clickable using apt-get probably won't work, because Seabass tries to launch clickable using python3.6 while clickable installed with apt relies on python3.5.

It should be possible to install required version with libertine-launch -i seabass2-build python3.6 -m pip install --user --upgrade git+https://gitlab.com/clickable/clickable.git@subcommands-reduced

@joel thank you for your work!

I'm using Ubuntu Touch on Poco as my daily driver and with the latest update to the halium-boot it seems really stable and won't even discharge anymore! Really, today is fifth day since i've charged it and it still has 35% of battery remaining.

@kugiigi hm, that's ok, it's just a warning. Actual script output should follow that line. What's strange is that there is nothing else in the output...

@kugiigi thank you very much for trying the build!

Oh, didnt know UT is already available for that phone.

UT works pretty well on F1 aside from a few stability issues, even fingerprint sensor works

I still get the error at the end. It says that clickable is not found.

Hm, I think I need to improve logging here
If you have some time, could you please try "Update build container" button on the Settings page in Seabass? It will run a script to install the required version of "clickable"!

@kugiigi thank you! It's Poco F1

@kugiigi thank you for the feedback!

This one has a compressed prebuilt container so container creation is really fast.

Thank you! I'm thinking about such option because creating a container from scratch seems too unstable and requires too much time even on snapdragon 845. I'd better not imagine how long it would take for example on BQ e4.5

And I like the way OnTheRoad solves the problem.

And then I get some errors around the part when clickable is being installed

Hm, I think it might had been broken for some time. v0.11.2 (currently in the store) should've solved container creation issues by upgrading python to v3.6.

Hi everyone!

It's almost Christmas time, New Year is coming, and it means holidays and maybe some spare time for developers to create new awesome apps for UBports... and that's where the Seabass might come in handy

The next release is going to provide an ability to create new apps for UBports from within the Seabass. Hopefully that means building apps right on your phone/tablet more easily.

So if you happen to have a use case for a mobile/convergent dev environment to build UBports apps and you have a device that supports Libertine, I'd be grateful for your suggestions and feedback!

For now there is a beta version available for testing.
It has a new menu entry called "New project..." in the file list:

It leads to the project settings page:

Here you can specify all the options supported by Clickable and create a new app.

There are a few limitations for now:

• Libertine support is required
• Creating a Libertine container (during the first run of clickable) might take a while
• Seabass now uses a pre-release version of clickable that might have a few breaking changes
• it's only possible to create new projects inside ~/Documents and ~/Downloads directories (and any nested directories)

Click package is available on Github: v1.0.0-beta-1

@danqo6 logviewer from the open store should work for getting logs

@danqo6 does the app works for you when running from the app grid?

@danqo6 thank you! I can reproduce the issue on Pocophone with GSI. For me the same happens when trying to run other apps that use qmlscene from terminal (I tried it with uNav). But running the applications from the app grid works fine.

Just a guess, but maybe the app grid provides environment variables, that are required but missing when trying to run qmlscene from terminal?

@joel Thank you very much! Works great!

@TotalSonic said in Xiaomi Poco F1 (Beryllium):

What is the current status for camera, camera flash/zoom, torch, and video encoding/decoding for the F1?

Camera works, recording videos works, flash works, torch works. Haven't tried playing local video files other than taken with camera, but youtube in Morph works.

I haven't tried to run desktop applications from Libertine, so have no experience here.
For command line apps libertine-container-manager exec and libertine-launch commands works for me.

Have you tried running ubuntu-app-launch <CONTAINER_ID>_<desktop_file_name>_0.0 command (from the docs)?

@xinyiman said in Problem with libertine:

Why?

python3-libertine-lxd package is, I believe, required to create LXD containers and it's not installed by default. As for why it's not installed -- I don't know. We need someone more knowledgeable here

How resolve?

libertine-container-manager create -i myapp -t chroot will create a chroot container

A few notes on v0.5.0:

• Container creation fails constantly for me because of mismatching package versions in the xenial repos.
  How to fix: update to v0.5.1
• Seabass can't delete the container in case of initialization errors
  How to fix: delete the container manually using System Settings app
• And in case you've managed to create a container, desktop applications from the seabass2-build container are visible in the app grid.
  How to fix: libertine-container-manager exec -i seabass2-build -c "bash -c 'rm /usr/share/applications/*.desktop'"

The issues should be fixed in v0.5.1

v0.5 is up and it has support for building projects using Clickable.

The feature is very experimental and somewhat limited for now and (although I've tested it as much as I could) there should be bugs. To build a project you need to open a corresponding clickable.json file and click the "Build" button:

When starting a build process for the first time a new chroot Libertine container with ID seabass2-build will be created.
So the first thing required to build packages with the Seabass for now is... patience :-D.
Because creating a chroot container might take a while. About 30min was usually enough for my Xperia X during testing, but the experience for sure may vary depending on your device and Internet connection. The app should also be active (not sleeping) while the container is being created. The good thing is that you only need to create container once.

If for some reason the container creation failed, Seabass will try to delete the container, so that the next time you run Build it could try to create container once again.
And if for some reason the deletion wasn't successful, libertine-container-manager is here to help: libertine-container-manager destroy -i seabass2-build. You could also use this command if anything goes wrong with the container

There are also a few limitations:

• Project files should be located inside ~/Downloads or ~/Documents directories. Not really a strict requirement, just these directories are automatically mounted to Libertine containers. Alternatively you could create additional bind mounts using libertine-container-manager or maybe even System Settings application.
• clickable.json file should be named 'clickable.json'. Because the "Build" button is only visible for "clickable.json" files.

QML, HTML, C++ and Python clickable templates are supported for the first release (Go and Rust require additional packages that are not installed in seabass2-build by default). By "supported" I mean I've tested building "HelloWorld" applications using these templates

Please let me know if there are missing packages in the container required to build your favorite application!
Your feedback is very appreciated!

Thank you for your thoughts on the Icon!

@Giiba said in Feedback for the Seabass:

A tangential though related feature request would be two things

Thank you! Content Hub for the Seabass is definitely on my todo. It'll take a few releases before Content Hub is implemented though:

• v0.5 release will feature building packages with Clickable
• v0.6 will probably contain ability to delete files (seems to be the only blocker left before Content Hub integration)
• and then v0.7 will probably contain Content Hub integration.

Well, at least this is what I think for now