Ubuntu touch: freedom, privacy and data sovereignty in your hands

@mardy The output of command:

phablet@ubuntu-phablet:~$ sudo ls -l /dev/fm* /dev/radio*
ls: cannot access '/dev/fm*': No such file or directory
crw-rw----+ 1 system system 81, 18 Apr 14  1971 /dev/radio0
phablet@ubuntu-phablet:~$ 

Btw:

phablet@ubuntu-phablet:~$ sudo zless /proc/config.gz | grep -iE 'V4L2'
CONFIG_VIDEO_V4L2_SUBDEV_API=y
CONFIG_VIDEO_V4L2=y
CONFIG_MSM_VIDC_V4L2=y
CONFIG_MSM_V4L2_VIDEO_OVERLAY_DEVICE=y
# CONFIG_MSM_BA_V4L2 is not set
phablet@ubuntu-phablet:~$

@mardy I tried on my BQ U Plus (I'm the official porter, even though the device is not officially in the list).
Error:

phablet@ubuntu-phablet:~$ fm-radio-client.py 
1) Quit
2) Open tuner
Choose an action: 2
Traceback (most recent call last):
  File "/usr/bin/fm-radio-client.py", line 226, in pick_action
    command.action()
  File "/usr/bin/fm-radio-client.py", line 156, in open_tuner
    tuner_path = service.open_tuner()
  File "/usr/bin/fm-radio-client.py", line 26, in open_tuner
    return self.__service.OpenTuner()
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: com.lomiri.FMRadioService.Error.ResourceError: Radio backend not available

I checked what CONFIGs are enabled in the kernel:

phablet@ubuntu-phablet:~$ sudo zless /proc/config.gz | grep -iE 'RADIO|FM'
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_SCRIPT=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_HAMRADIO is not set
# CONFIG_BTFM_SLIM is not set
# CONFIG_BRCMFMAC is not set
CONFIG_MEDIA_RADIO_SUPPORT=y
CONFIG_RADIO_ADAPTERS=y
# CONFIG_RADIO_SI470X is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_RADIO_SHARK is not set
# CONFIG_RADIO_SHARK2 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_RADIO_SAA7706H is not set
# CONFIG_RADIO_TEF6862 is not set
# CONFIG_RADIO_WL1273 is not set
# Texas Instruments WL128x FM driver (ST based)
# CONFIG_RADIO_WL128X is not set
CONFIG_RADIO_IRIS=y
CONFIG_RADIO_IRIS_TRANSPORT=y
CONFIG_RADIO_SILABS=y
CONFIG_MMC_SDHCI_PLTFM=y
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_FMC is not set
# CONFIG_QFMT_V1 is not set
# CONFIG_QFMT_V2 is not set
phablet@ubuntu-phablet:~$

CONFIG_RADIO_IRIS is the module, but it seems to have some issue.
The rootfs.img I actually use is a stable one with some months old. Might it be useful to test with more recent version of edge one for armh?
Btw, the installation of the 3 debs went fine.

@z4tab Sorry for the issues, but if you really want to test it, please, could you use the guide: https://forums.ubports.com/topic/4351/porting-ubuntu-touch-ubports-to-karin-sony-xperia-z4-tablet-sgp771-and-karin_windy-sony-xperia-z4-tablet-sgp712?_=1630513955780

@applee Yep, I needed to create configuration patch to add tenshi into the installer-config version 2 and I already had committed to the backend administrators (1 month ago).
If you want to test them, I will provide it to you, but if the backend administrator has not yet prepared the infrastructure for tenshi, they won't be useful

@applee I requested to include it a long time ago, considering it is almost fully working, but camera+video and MTD/RNDIS for configfs. The other minor issue is that if you plug the jack in to listen to the music, sound output is router to headset and speakers.

@matte0 Thanks for your interest: unfortunately I (the porter) am not able to fix issue of camera/video alone. It depends on some standard package. On top of that, the other missing thing is MTD/RNDIS, as the ability to see storage from pc.
Apart from it, it is fully working, including anbox where you can install apk from android

@metty fastboot flash boot halium-install.img for kernel, while for rootfs.img and system.img you need halium-install tool. It automatically install both of them in the /data partition

@metty did you choose the right images? first try to boot from datapart, putting system.img and rootfs.img over there and flashing the halium-boot.img
Then you can pass to the next step, I mean to boot from system partition

@metty hello, what is your difficulty in executing these instruction?
Let me resume:

• you need to unlock your device, I suppose you had already done to have LOS up and running
• you need to install TWRP, by sudo fastboot flash recovery twrp.img
• you then need to install the OS, executing: ./halium-install -v -p ut ~/Downloads/ubuntu-touch-hybris-xenial-edge-arm64-rootfs(1).tar.gz ../system.img
• reboot the device to bootloader and flash the kernel: fastboot flash boot halium-boot.img
  I recommend at the first time to choose the halium-boot.img which boots from /data
  Then reboot and it should start to work

@z4tab actually I never performed these preparatory steps, so I can't help you out. My suggestion is to unlock bootloader and install twrp, then from there (recovery mode) try to activate adb sideload from twrp menu on device and on pc's terminal execute adb sideload name_of_binaries.zip.
If you want to risk to go directly on installing UT, first try to install it on datapart (the /data partition) with halium-install. Remember to use the proper halium-boot.img.
When you will be more familiarised with UT and recovery also in systempart (/system partition).

@zapfel There is a great work done for pioneer by Heng Ye and @TheKit in the following repo: kirin (Sony Xperia 10), mermaid (Sony Xperia 10 Plus), pioneer (Sony Xperia XA2).
I'd need to queue my device up in this repo.

@branja6 I guess it is. Is it the same model with 2 sims? Somewhere in the web, i saw the difference for each model. If it is a discovery, no problem at all. I oly built kernel (halium-boot.img ) and vendorimage (vendor.img), then I installed ubports-GSI-rootfs and it worked.
But I need to do it better, enhancing TheKit's work to make it officially supported

@BigB you need to comment out telephony-ext in your device.mk in device/sony/your_device_name.
Also all the services in vendor/sony/your_device_name in the file *.mk (at the end of the fike)

@markus228 I'm starting from today: my device is discovery (h3213), Xperia XA2 Ultra. It will be used halium-9

@basti you used the wrong file with the halium-install: the command needs to be feeded by the rootfs.tar.gz (you did it correct) then by system.img. At this point, it won't fail.
So far, you need to reboot in bootloader, and from pc execute fastboot flash boot halium-boot_h870_datapart.img (that you will download from the very first post).
Your halium-boot won't let you boot correctly because it is thought to bootsttap from systempart to be OTA compliant, while halium-boot install rootfs and system in datapart
Anyway, the 3rd line of the very first post, suggest to join a telegram chanbel that i created today

@basti Did you install your device with halium-install? I just updated the instruction at the very beginning.
Halium-install usually installs rootfs.img and system.img in datapart, so you need to flash the image, as described above.
Please, inform me if you still have problem booting.
Take it easy, you can recover your old system (previous UT or Android, or LineageOS), whenever you want.

@basti this is more likely due to adb, rather than to halium-install, the last command must be executed when the device is in recovery mode. Not in bootloader one

@Invy @basti No, it must be arm64, otherwise it won't work at all

@Invy I need to upload new kernel configuration with HCIUART and HCIUART_H4, otherwise it won't work at all. I will ping as soon as I did it. Or I can add my halium-boot (botstrapping from systempart, as requested by OTA compatibility, or not) to be downloaded and tested.