I run UT on a OnePlus 3 (stable channel). I have installed waydoird using:

$ sudo ubports-qa install xenial_-_android9_-_wayland
$ wget -O - https://github.com/Anbox-halium/anbox-halium/raw/lineage-17.1/scripts/install.sh | bash

Afterwards, I tried to run it using:

$ sudo /home/anbox/run-container.sh

This fails after:

modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/3.18.31-halium-gac6f57d5/modules.dep.bin'
modprobe: FATAL: Module binder_linux not found in directory /lib/modules/3.18.31-halium-gac6f57d5
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/3.18.31-halium-gac6f57d5/modules.dep.bin'
modprobe: FATAL: Module ashmem_linux not found in directory /lib/modules/3.18.31-halium-gac6f57d5
mount: unknown filesystem type 'binder'
ERROR: Binder and ashmem nodes not found!

After this nothing happens for a second or two, then the screen goes black and the phone becomes unresponsive except for the power button, which allows me to reboot the phone.

Since apt doesn't work on UT, how do I install the required modules?

@MrT10001 That's great to hear. I really hoped there wasn't some technical problem in UT preventing this. I'll look into it then.

@gpatel-fr Right, thanks!

I'm new at clickable as well as CMakeList.txt, so if this is documented, please point me there, but my build fails after:

Errors
------
 - lint:control_architecture_valid_contents
	found binaries for architecture 'all': src/Providers/charset_normalizer/md.cpython-38-x86_64-linux-gnu.so, src/Providers/charset_normalizer/md__mypyc.cpython-38-x86_64-linux-gnu.so
/home/diederick/projecten/Code/clickable-projects/potkast/build/all/app/potkast.thefoggiest.dev_1.0.0_all.click: FAIL

even after if succesfully build the package. This doesn't happen when I do clickable dekstop

In my CMakeList.txt I have (if this is related):

add_custom_target(install_deps ALL
    COMMENT "Installing feedparser and requests dependencies"
    COMMAND pip3 install -U --target install/src/Providers/ feedparser requests
)

I got this example from an existing project, Afvaller, but that one builds without problem.

Any help greatly appreciated!

@oldbutndy I honestly never looked in what is making Jellyfin see my TV as something it can cast to, while it specifically mentions Google Cast to be unsupported, but it works, without any other dongles hanging out of its HDMI ports.

@arubislander said in What is quality level of external wireless display mode on Nord N10 5G:

@RapidRotator said in What is quality level of external wireless display mode on Nord N10 5G:

I can cast Jellyfin to my Panasonic TV with does 1080p with perfect quality from my N10.

Do you have a Jellyfin client running on your TV as well? In that case it is not comparable.

No, my TV has not a Jellyfin client. I cast it to my TV from my phone.

@oldbutndy Hey, unsure why you need unlock codes from OnePlus (maybe my situation was different) but I unlocked mine with this: https://www.getdroidtips.com/unlock-relock-bootloader-onepus-nord-n10-n100/

Anyway, I don't have a Miracast, but I can cast Jellyfin to my Panasonic TV with does 1080p with perfect quality from my N10.

Does this help?

@flohack Atm it's quite busy because of the year-end with my kids (school, music performances, etc.), but between Christmas and new year I can remount the needed directories writeable and see if I can install and configure mmcli and geoclue to see if I can get those working on UT

@projectmoon Thanks, you're completely right. It works now.

@MrT10001 That's great to hear. I really hoped there wasn't some technical problem in UT preventing this. I'll look into it then.

I have an open source Bangle.js smart watch with assisted GPS. On a PostmarketOS phone I use geoclue with:

[wifi]:
enable=true
url=https://beacondb.net/v1/geolocate

in the settings to get fast WiFi-enabled GPS. So hence my question: why is badly perfoming GPS mentioned as a caveat with every phone, while this is perfectly possible to do in Linux?

Is it simply that nobody had the time yet?

@projectmoon Waydroid came installed with UT. I just had to do a waydroid init in the terminal and I could start it. MicroG was not there, so I grabbed a file called microg-services-0-3-1-4-240913-hw.apk from what looked like a trustworthy site and did an adb install from the terminal