@Aloys many thanks for your work. I published your click file. If you want to change anything on the open store page please ask.

@Aloys said in Publishing updated app from another maintainer:

can we have several publisher for an app on openstore ?

This would be the best solution in my opinion. This way an app can be be maintained by a team.

@Aloys did some great work so I will upload the new version if there is no way to share the openstore account of this app.

@TheVancedGamer Hats off to you! What a magnificant piece of work you have done. Fantastic.

Somehow the installer, besides installing he wrong recovery also fails to 'adb push' on my windows machine.

When flashing the correct recovery and doing the copying manually then after a reboot into the recovery the installation process started.

Tried it again yesterday.

• The installer still installs the old (wrong) recovery.
• After manually flashing the correct recovery (see above) the installer seems to successfully finish. But...
• After rebooting the first time the recovery appears and when rebooting a 2nd time it fails. Only the splash screen is shown and no adb access.

@Lakotaubp
Tried to copy from the commandline but it fails:

adb.exe push "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\rootfs-992a3dd9f3fc67917d3abaa9786a86f7af59c60feabf6495223fc170de802863.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\rootfs-992a3dd9f3fc67917d3abaa9786a86f7af59c60feabf6495223fc170de802863.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\version-14.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\version-14.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\image-signing.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\image-signing.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\image-master.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\image-master.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\ubuntu_command" "/cache/recovery/
C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\rootfs-992a3dd9f...170de802863.tar.xz: 1 file pushed. 12.2 MB/s (463061576 bytes in 36.065s)
C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\rootfs-992a3dd9f...3abaa9786a86f7af59c60feabf6495223fc170de802863.tar.xz.asc: 1 file pushed.
adb: error: failed to copy 'C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz' to '/cache/recovery/device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz': remote write failed: No space left on device
C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99...de81c08ffc3b.tar.xz: 0 files pushed. 14.6 MB/s (63824272 bytes in 4.165s)
adb: error: failed to copy 'C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz.asc' to '/cache/recovery/device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz.asc': couldn't read from device
C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99...35de81c08ffc3b.tar.xz.asc: 0 files pushed. 0.0 MB/s (488 bytes in 0.481s)
adb: error: failed to copy 'C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz' to '/cache/recovery/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz': couldn't read from device
C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\keyring-28992f00...62ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz: 0 files pushed.
adb: error: 617-byte write failed: No error

This is df on my device:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1460812 572 1460240 1% /dev
tmpfs 1460812 0 1460812 0% /mnt
tmpfs 1460812 108 1460704 1% /tmp
tmpfs 1460812 0 1460812 0% /storage
/dev/block/mmcblk0p16 516040 460884 55156 90% /cache
/dev/block/mmcblk0p14 1334432 1284468 49964 97% /system_root
/dev/block/mmcblk0p28 57591248 2244256 55346992 4% /data
/dev/block/mmcblk0p15 5024 4284 740 86% /persist
/dev/block/mmcblk0p1 65488 57424 8064 88% /firmware

@Lakotaubp The recovery file appears to be the same as the one I tried (well WinMerge says so).

Copying the data seems to work the install/update fails.

The first error seems to be:

mount -a mount: '/dev/block/platform/msm_sdcc.1/by-name/system'->'/system': No such file or directory

and indeed adb shell shows:

lrwxr-xr-x 1 root root 19 1970-01-01 00:00 system -> /system_root/system
drwxr-xr-x 2 root root 0 1970-01-01 00:00 system_root

root@A0001:/ # ls -l /system_root/
total 0

-edit-

Aha no this is wrong. mount just complains about non existing links the first real error appears to be make_ext4fs: not found
And indeed it does not. But mkfs.ext4 does exist.

@MrT10001 I tried the halium-9 one. Maybe it should have been one of the other builds of https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fporting%252Fcommunity-ports%252Fjenkins-ci%252Fbacon/ so if you still want to try...

By the way the log now shows (see the pastebin): /sbin/sh: make_ext4fs: not found

@Lakotaubp That is exactly what I did.

@TheVancedGamer

I just tried something. Don't know it is useful information.

I manually installed the recovery and boot images from https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fporting%252Fcommunity-ports%252Fjenkins-ci%252Fbacon/job/halium-9.0/lastSuccessfulBuild/artifact/halium_bacon.tar.xz

And the installer now did not show any error (disabled flashing system partitions) . But it is still not working see https://pastebin.com/Yr9sqy7q

@TheVancedGamer

Also for me it still fails. See https://pastebin.com/Xg4TGKvB

Is it possible to show some version info in the recovery so we can check if the correct one is being flashed?
The log file indicates the installer uses the one from http://cdimage.ubports.com/devices/. Is that the correct one?

Does it work for you?

@magnargj Sorry at the moment I am not very interested in Ubuntu Touch and I am not working on my apps for it. You will have to check the logs on your phone to see what is going wrong.

@abmyii It seems to work well. No errors in the log. (Oneplus One, rc channel, Ultravnc on windows 10).

I ran it with

phablet@ubuntu-phablet:/opt/click.ubuntu.com/mirvncserver.abmyii/1.0.0$ LD_LIBRARY_PATH=lib/arm-linux-gnueabihf/ ./mirvncserver  -m /run/mir_socket --cap-interval 2 -s 432 768

thanks for creating this

@paulmbcufc Did you follow all the steps mentioned here? https://forums.ubports.com/topic/4147/sony-xperia-x-performance-dora-f8131-f8132/2

@UdenGoogle multiple persons have met this issue. Search the forum for 'opo wifi' and you will find some. Some got it working and some did not.

This one seems to had success: https://forums.ubports.com/topic/4225/oneplus-one-bacon-wifi-issue/20

@Nathan123 no idea what can be wrong. All I know is that the only issue I have with wifi on my opo is that sometimes after booting wifi is not available. For the rest it works flawless.

Did you flash anything special before trying ubports? Maybe try to revert to stock modem?

I used the ubports installer many times for my opo. Now it fails consistently. I flashed lineage 16.0 and want to go back to ubports but after the installer does it's magic in fastboot the ubports recovery does not show up in 'adb devices'. normal booting just hangs.

When I reinstall lineage and verify adb is working and in bootloader mode I manually flash the ubports recovery (fastboot flash recovery C:\Users\neil\AppData\Roaming\ubports\bacon\firmware\recovery-bacon.img) and boot into it 'adb devices' remains empty.

Is the adb server still present and working in the recovery image?

I am running the installer on Windows 10 and tried to install both rc as well as stable.

solved: virtualbox was grabbing the device so the host adb (windows) never saw it. The installer now works. Well it is busy doing stuff ...

Hi,

I have renamed my app shoutcast-ubports into shoutcast-ut. This in order to remove any link with the UBports Foundation.

Some time ago there was a general request in the telegram groups to not use the foundations name and a new release seemed like a proper moment for the rename.

The new app is added to the open-store and the old one removed. New github url is https://github.com/wdehoog/shoutcast-ut

Sorry for any inconveniences. (Believe me, mine were bigger then yours.)

@c4pp4 Hi. You tried to revert the commit 8 days ago and it did not help. I also tried to revert it and it did not help me either. Now todays update seems to work and indeed the commit is gone. But I suspect something else has also changed. I am probably wrong and it is of no use anyway since it now works.

@Thatoo I am not one of the devs but please allow me to respond.

You are completely right that contacts sync is very important and that it's current state is bad. However you are wrong in thinking that MIR and Lomiri are geeky and not used by your mum. In fact everybody uses them and without them there is no Ubuntu Touch.

Unfortunately the current state of affairs is that the few devs have to spend all their resources to developping the base system and do not have much left to work on higher layers like contacts sync.

As this is a community project you will have to work on it yourself or wait until somebody else will.

Me I would like to read a book and listen to the music files on my dlna server. As this could not be done I had to start working on my own app and fixing/extending various parts of ubuntu touch (led, gestures, media-hub).

Sorry I cannot help you making you feel better but I hope you can understand why things are as they are now.

Creating a changelog for updates is too much work. But now it is very hard to detect the source of problems and regressions. Is it possible to automatically create a list of versions of installed packages for each update? (Or does such a list already exist?) And then have them available for a while so we can compare them and look for possible candidates to investigate.