Feedback for the Seabass
-
@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.
-
@mikhael Oh wow, which UT device has 845?
I'll be installing the beta version and try creating a container again and let you know
-
-
@mikhael Oh, didnt know UT is already available for that phone. I though fxtec pro1 x is supposed to be the most powerful UT device
I tried creating container again and luckily, it only took less than an hour this time. Maybe the server is happy today
However, I still get the error at the end. It says that clickable is not found. Then I tried manually installing clickable in the container via the settings app. After I've done that, building an app just shows a blank build 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"! -
@mikhael I tried that but I get an error.
proot warning: can't chdir("/opt/click......." in the guest rootfs: No such file or directory proot info: default working directory is now "/" -
@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...
-
@mikhael Yes, nothing else after that.
-
@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-getprobably 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 -
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!
-
@mikhael Oh that's sad. I tried your command and the build output just stayed blank. Before the command, it just says that clickable wasn't found and environment variable wasn't set.
-
@kugiigi thank you for the feedback!
For some reason Seabass can't executelibertine-launchon Nexus 5, althoughlibertine-launchworks fine from Terminal. The problem could be somewhere in between seabass, pyotherside,libertine-launchpython script andproot(used bylibertine-launch), but unfortunately for now i don't know what exactly goes wrong.
