administrators group

arubislander

@developerbayman This post is two years old. And the OP hasn't been on the forums in over a year. I doubt they will benefit from any advice now.
I will proceed to lock the thread.

arubislander

@brenno.almeida the source needs to be available if it is an open source app. But as long as it is fully confined it doesn't need to be open source to be published in the store. The 'open' in Open Store originally was because it was also open to unconfined apps, whereas those were not allowed in the Canonical store.

arubislander

@developerbayman it's just an update of an app that I have had in the store for years now.

This is an open ecosystem. User choice is welcomed. If it is a different app, inspired on Syncthing or no, then there's definitely no objection.

Even if it were the same app, then I am in no capacity to object anyhow. But in the latter case I would rather appreciate collaboration rather than having two distinct versions of the same app in the store.

But since this is not even the case with your app, by all means follow your intuition.

arubislander

@Moem so it is!

arubislander

@developerbayman It is never "that simple". If it were, it would already have been done.

arubislander

A new version (2.0.16) of Syncthing has been uploaded to the Open Store. This release follows the upstream release. See here for the release notes.

arubislander

@developerbayman wouldn't it make more sense to use a mainline port or the PDK image as a base for a x86_64 port. Then there would be no Halium bits needing to be removed.

flohack

Hi there,

if you ever want to install an Android-based distro after Ubuntu Touch was installed, you will notice that no sensors work anymore. The root cause was already identified by guys on the Fairphone forum some time ago description is more to the end of the thread, so be patient and read it in full - but here in UT side nobody of course noticed that, as sensors keep working correctly in UT

What happens is that the necessary Android selinux contexts are being somehow removed from the sensor folder in the persist partition. We would need to analyze why this happens, but probably the files are being rewritten from the Android container in UT and as UT does not use selinux, they are set to unlabeled, like so:

./sensors/registry/registry:
total 668
drwxr-xr-x 2 system system u:object_r:vendor_persist_sensors_file:s0  12288 2023-11-21 22:10 .
drwxr-xr-x 3 system system u:object_r:vendor_persist_sensors_file:s0   4096 2023-11-21 22:10 ..
-rw------- 1 system system u:object_r:unlabeled:s0                       78 2023-11-21 22:10 ak0991x_0
-rw------- 1 system system u:object_r:unlabeled:s0                      131 2023-11-21 22:10 ak0991x_0.mag
-rw------- 1 system system u:object_r:unlabeled:s0                      233 2023-11-21 22:10 ak0991x_0.mag.config
-rw------- 1 system system u:object_r:unlabeled:s0                      181 2023-11-21 22:10 ak0991x_0.mag.config_2
-rw------- 1 system system u:object_r:unlabeled:s0                      222 2023-11-21 22:10 ak0991x_0_platform
-rw------- 1 system system u:object_r:unlabeled:s0                      866 2023-11-21 22:10 ak0991x_0_platform.config
-rw------- 1 system system u:object_r:unlabeled:s0                      142 2023-11-21 22:10 ak0991x_0_platform.mag
-rw------- 1 system system u:object_r:unlabeled:s0                      146 2023-11-21 22:10 ak0991x_0_platform.mag.fac_cal
-rw------- 1 system system u:object_r:unlabeled:s0                      204 2023-11-21 22:10 ak0991x_0_platform.mag.fac_cal.bias
-rw------- 1 system system u:object_r:unlabeled:s0                      508 2023-11-21 22:10 ak0991x_0_platform.mag.fac_cal.corr_mat
-rw------- 1 system system u:object_r:unlabeled:s0                      148 2023-11-21 22:10 ak0991x_0_platform.mag.fac_cal_2
-rw------- 1 system system u:object_r:unlabeled:s0                      206 2023-11-21 22:10 ak0991x_0_platform.mag.fac_cal_2.bias
-rw------- 1 system system u:object_r:unlabeled:s0                      510 2023-11-21 22:10 ak0991x_0_platform.mag.fac_cal_2.corr_mat
-rw------- 1 system system u:object_r:unlabeled:s0                      176 2023-11-21 22:10 ak0991x_0_platform.orient
-rw------- 1 system system u:object_r:unlabeled:s0                      622 2023-11-21 22:10 ak0991x_0_platform.placement

Unfortunately the solution to this is, as described in the Fairphone forum thread, a bit cumbersome:

The bootloader needs to be unlocked. If you happen to have all your data already in this Android installation and you have locked the bootloader again, you will loose all your data during this process.
You have to install Magisk. Depending on the Android version this involves patching the boot.img file or creating a custom recovery
With Magisk you can obtain a root shell and the execute the necessary restorecon command

It would be awesome to find out if we can avoid this situation somehow. Unfortunately I just dont have the time for the moment, but I can confirm the fix worked as described over there.

BR Florian

administrators

Posts

Member List