I wonder why both of mine work?! There are other issues with networking for sure. I cannot do ipp (works on the GS290/volla). I cannot connect to qmllive from the SDK. So, off I go to debug another issue.
EDIT: just tried with the GS5 again and when wifi is OFF and cellular on, hotspot works really well. Just spent a hour trying different things with it as the hotspot. Was even relatively snappy! On the otherhand, can’t print with it via wifi and seaprint 
Did anyone with a rephone make a backup of the ROM/vendor images? I, sadly, neglected to do so. Looking for the vendor binary blobs for the camera.
Sorry, no, I always start making backups, when I have a for me suitable system. In my tests with the Hostspot directly after flashing, the experience WHEN I was able to established a working connection, was as well stable and snappy.
Sorry, no, I didn’t know it was possible
Just to get a ‘clean slate’ on the rephone, I’m going through VollaOS first and testing all functions. So far, good news:
)
Lesson learned, never touch multi-boot into VollaOS unless you want to be stuck with a bootloader you don’t want. Hmmmm. Anyone know how to get rid of the boot image selector!?
Does this help?:
Sadly not relevant to this device, though I could probably screw about with twrp for a while. But I don’t have the time for that.
Maybe asking on Volla or ubports forum helps.
I’ll go low level I guess. No worries, it just changes some ‘default’ advice I used to give or at least means a warning for what not to do.
EDIT: well, the simple solution is to remove the SD card. I also used the UT install just to see what the state was since it’s at 20 now. But, removing the SD card got me booting SFOS again.
EDIT: Sadly, video recording is still broken.
News from my side regarding network. After the reflash I’m now more or less constantly on interface wlan0. My Ip is now shown on the developer site in settings. The WLan Icon is now most of the time stable.
…And Sailfish connect works now. Not very good compared to my other devices, but it seems so far reliable. I have to set the IPs of the devices I want to connect. So no autorecognition. And I have to be patient. It takes up to two minutes until the devices show up and are getting connected. Connection quality is sometimes as well somewhat flaky, but anyway. It works at least.
I hope you get the network issues debugged. I have moved SIM Card and SD to the rephone again. 
Ok, that’s cool! I did the old, flash Ubuntu Touch routine. Tested Video and Hotspot there. Both worked almost as well as under VollaOS. Then, after removing the SD card, SFOS booted again. But video is still borked. @piggz I believe it is on the SFOS end, not that I’m expecting you to account for all the vars.
EDIT: to be clear, to get out of my not being able to boot SFOS I did:
i flashed volla os on my gs5…
but sailfish or ubuntu dont boot up
from sd card:-(
- All WLans show up three times and I’m not sure if it makes differences which one I choose
The first time I have flashed Sailfish (so it was still using the installed Android’s 11 version ), the 3 WLAN behaviour didn’t strike me, so I think that every WLan was showed up only once.
Unfortunatly, I had to reflash my phone, so I have flashed VollaOS and then Sailfish and now I can see the 3 WLan behaviour.
Do you think that the behaviour could be different depending on the Android’s version that was flashed juste before ?
That’s possible. I haven’t looked after the network, when I first installed SF. I installed it the first time as well over the original Android 11. Anyway, there were so many problems, that I flashed Volla OS and from there I flashed SF. So maybe this is a direction in which @poetaster and @piggz could investigate. But I’m not the expert on this this side.
And wrong again. As @piggz mentioned far above, the Volla22/GS5/ and rephone only support FHD (1920x1080) video. SOO, you need to choose using Advanced Camera from @piggz and set the resolution. Then the camera videos are correctly recorded and viewable. Sigh.
Sometimed its so easy. especially when you are solving problems which doesn’t exist. 
Yup, classic, since I had a vague memory of a note in this very thread as I was flashing for the third time. Ah, well. At least I now know that the 20 version of UT works quite well. Maybe it’ll move me to finally port some apps to UT!
After re-flashing my GS5 (prepared with the Volla image as recommended by @poetaster) I had the same problem as you, that “Systemdaten” filled up quickly.
So I did a factory reset in recovery and flashed again.
I don’t know if it was like that from the beginning, but now it’s like in your screenshot: all the partitions add up to about 64 GB instead of 128, as the GS5 should have.
Did I oversee something in the previous 507 posts here in the thread or are the remaining 64GB just missing?
No, I don’t think, that you have overseen something. I haven’t seen an explanation why there has been left just half of the size for the running system. Anyway I accepted that, because together with my SD-Card for me it’s enough space.
My guess is, that some stuff is needed for recovery system and android blobs. if you look at the partition layout, you see, that all the space is there but used for different things:
[root@Phone22 home]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 448,4M 1 loop /android/apex/com.android.art
/android/apex/com.android.runtime
/android
/android/system
/var/lib/lxc/android/rootfs
loop1 7:8 0 392,9M 1 loop /android/vendor
loop2 7:16 0 58,6G 0 loop
└─home_encrypted 253:1 0 58,6G 0 crypt /home
nbd0 43:0 0 0B 0 disk
nbd1 43:32 0 0B 0 disk
nbd2 43:64 0 0B 0 disk
nbd3 43:96 0 0B 0 disk
nbd4 43:128 0 0B 0 disk
nbd5 43:160 0 0B 0 disk
nbd6 43:192 0 0B 0 disk
nbd7 43:224 0 0B 0 disk
mmcblk0 179:0 0 116,5G 0 disk
├─mmcblk0p1 179:1 0 3M 0 part
├─mmcblk0p2 179:2 0 512K 0 part
├─mmcblk0p3 179:3 0 512K 0 part
├─mmcblk0p4 179:4 0 20M 0 part
├─mmcblk0p5 179:5 0 1M 0 part
├─mmcblk0p6 179:6 0 8M 0 part
├─mmcblk0p7 179:7 0 8M 0 part
├─mmcblk0p8 179:8 0 8M 0 part
├─mmcblk0p9 179:9 0 8M 0 part
├─mmcblk0p10 179:10 0 8M 0 part
├─mmcblk0p11 179:11 0 8M 0 part
├─mmcblk0p12 179:12 0 22,6M 0 part /metadata
├─mmcblk0p13 179:13 0 32M 0 part
├─mmcblk0p14 179:14 0 32M 0 part /mnt/vendor/nvcfg
├─mmcblk0p15 179:15 0 64M 0 part /mnt/vendor/nvdata
├─mmcblk0p16 179:16 0 48M 0 part /mnt/vendor/persist
├─mmcblk0p17 179:17 0 8M 0 part /mnt/vendor/protect_f
├─mmcblk0p18 179:18 0 8,4M 0 part /mnt/vendor/protect_s
├─mmcblk0p19 179:19 0 8M 1 part
├─mmcblk0p20 179:20 0 128M 1 part
├─mmcblk0p21 179:21 0 1M 1 part
├─mmcblk0p22 179:22 0 6M 1 part
├─mmcblk0p23 179:23 0 1M 1 part
├─mmcblk0p24 179:24 0 16M 1 part
├─mmcblk0p25 179:25 0 2M 1 part
├─mmcblk0p26 179:26 0 32M 1 part
├─mmcblk0p27 179:27 0 64M 1 part
├─mmcblk0p28 179:28 0 8M 1 part
├─mmcblk0p29 179:29 0 6M 1 part
├─mmcblk0p30 179:30 0 2M 1 part
├─mmcblk0p31 179:31 0 26M 1 part
├─mmcblk0p32 259:0 0 64M 1 part
├─mmcblk0p33 259:1 0 12M 1 part
├─mmcblk0p34 259:2 0 128M 0 part
├─mmcblk0p35 259:3 0 1M 0 part
├─mmcblk0p36 259:4 0 6M 0 part
├─mmcblk0p37 259:5 0 1M 0 part
├─mmcblk0p38 259:6 0 16M 0 part
├─mmcblk0p39 259:7 0 2M 0 part
├─mmcblk0p40 259:8 0 32M 0 part
├─mmcblk0p41 259:9 0 64M 0 part
├─mmcblk0p42 259:10 0 8M 0 part
├─mmcblk0p43 259:11 0 6M 0 part
├─mmcblk0p44 259:12 0 8G 0 part
│ └─system_a 253:0 0 7,8G 0 dm /android/vendor/bin/vndservicemanager
│ /android/vendor/etc/init/mtkrild.rc
│ /android/vendor/etc/vintf/manifest/manifest.xml
│ /
├─mmcblk0p45 259:13 0 107,5G 0 part /android/cache
│ /android/data
│ /userdata
├─mmcblk0p46 259:14 0 43M 0 part
└─mmcblk0p47 259:15 0 16M 0 part
mmcblk0boot0 179:32 0 4M 1 disk
mmcblk0boot1 179:64 0 4M 1 disk
mmcblk0rpmb 179:96 0 16M 0 disk
mmcblk1 179:128 0 119,1G 0 disk
└─mmcblk1p1 179:129 0 119,1G 0 part /run/media/defaultuser/86f16387-82ae-48ab-9b14-c834d4c286e8
zram0 254:0 0 3G 0 disk [SWAP]
nbd8 43:256 0 0B 0 disk
nbd9 43:288 0 0B 0 disk
nbd10 43:320 0 0B 0 disk
nbd11 43:352 0 0B 0 disk
nbd12 43:384 0 0B 0 disk
nbd13 43:416 0 0B 0 disk
nbd14 43:448 0 0B 0 disk
nbd15 43:480 0 0B 0 disk
If you are looking at mmcblk0p44 and mmcblk0p45 These should be the relevant partitions. So there is all together 128GB (119 GiB) space. 8GB mmcblk0p44 is for root partition. The rest mmcblk0p44 is for
In /userdata there is the container for the encrypted home partition (home.img).
Why it has just the given size, I don’t know. Maybe it has to do with the encryption, so there is always enough cache. In the end you have to ask @piggz or someone who is fitter with all this stuff. I’m just a user.
A very knowledgeable user though thanks to which I now know I haven’t missed anything obvious.
Thanks!