@jhayar0719 Which command are you running? It appears that SDL2 isn't being detected / used, and thus no window is being created.

Also, do you happen to be using focal? I'm not sure if there are additional steps required for that.

@mateo_salta Sorry for the late reply - I check my messages infrequently.

@graphik_ I successfully built this on my device, but I don't think moonlight has Mir support, so it doesn't work for me. If you have a Wayland device I can describe the steps required to build and test it yourself.

I believe the limitation stems from libva which doesn't appear to have Mir support (https://github.com/moonlight-stream/moonlight-qt/blob/51b5f8046f1864e36cfa6efefbe2de71ef98ca92/app/streaming/video/ffmpeg-renderers/vaapi.h#L18-L31).

@applee Ah, makes sense. A bit of a shame though... Are there any "distros" that use the GPU for Pinephone?

@kugiigi Hmm, I guess it has very little HW acceleration to speak of... Does it even have a GPU at all?

@keneda Wow, my OPO gets destroyed in the particle test...

@povoq I'm not sure - it isn't my app (@pavelprosto any idea?). I also know that SDL2 apps don't work on Pinephone regardless of there is a click produced or not unfortunately...

I asked users to post the results their devices get on the Godot 3D Test app by @pavelprosto (https://open-store.io/app/godot3dtest.pavelprosto). Here are the results. Feel free to join in and add yours to this thread.

abmyii - OPO

Emanuele-Sorce - BQ E5

CiberSheep - Meizu MX4 (Arale)

Fuseteam - BQ E5 2nd Edition

@povoq Ah, right. My OPO has an Adreno too, apparently, albeit Adreno 330 whereas OP3 has an Adreno 530.

@kugiigi Thanks for such thorough testing! What is adreno?

@kugiigi Could be that not changing the version means it hasn't updated.

@kugiigi Also does your phone happen to have the /vendor/lib/egl/libGLESv2S3D_adreno.so library? I don't on mine, and I'm wondering if the presence of it on the OnePlus 3 causes the issue (very far-fetched TBH...).

@kugiigi Hmm, they should be different. I've added things to the logging commands since the release.

@kugiigi Thanks for testing! It could be that for sure, but it's a very weird issue...

Could you please test this click and see if a window is created?
https://gitlab.com/abmyii/gigalomania/-/jobs/1304649142/artifacts/raw/build/aarch64-linux-gnu/app/gigalomania.abmyii_1.0.1.1_arm64.click

Also, could you please send the logfile (~/.config/gigalomania.abmyii/log.txt`) after running the above click?

https://open-store.io/app/gigalomania.abmyii

I have been trying to debug an issue (https://gitlab.com/abmyii/gigalomania/-/issues/1) for Gigalomania crashing on a OnePlus 3 device, and I was wondering if the issue is common to all OnePlus 3(T) devices or not. if anyone could test it that would be very helpful.

@povoq Perhaps one of these?
https://forum.xda-developers.com/t/treble-gsi-ubuntu-touch-for-oneplus-3-3t.4123989/
https://forums.ubports.com/topic/4481/halium9-gsi-oneplus-3-t/24

@flohack I have had the NetworkManager problem for a while - since ~202012 IIRC (can't remember the exact version - sorry), but the SSH and cellular problems are new.

@flohack Hello! I tried this on my OPO and on the whole it works great, but I did run into a few hitches:

• NetworkManager and SSH don't start on boot anymore, so I had to add the following to /etc/rc.local:

/etc/init.d/network-manager start
service ssh restart

• My phone defaults to 2G only (saves battery) option for the cellular Connection Type, which results in me getting no cellular and Denied until I change it to the 2G/3G/4G option. I'm not sure how to force it to use 2G/3G/4G by default, so I guess I will have to set it manually on every boot which is a bit inconvenient.

@mariogrip I heard the mirbacklight script will be removed from devel. I use it in MirVNCServer, so what alternative methods can I use once it has been removed?

For input to work on Nexus 5 (hammerhead), a udev rule has to be added using the following instructions:

• Make the rootfs rw using the Ubuntu Touch Tweak Tool (UTTT)
• Run this command on the device/over SSH:

echo 'ACTION=="add", KERNEL=="uinput", OWNER="system", GROUP="bluetooth", MODE="0660"' | sudo tee /lib/udev/rules.d/70-android_additional.rules

• Reboot device

This fix has to be applied only once. It will become redundant after OTA-17 is released, as there is an open PR to fix it (https://github.com/ubports/android_device_lge_hammerhead/pull/30).

@kugiigi If you are up for it, you can just manually download all the required libs until it works - there shouldn't be too many more TBH. The process is a bit finicky, but doable. I can explain how to, if you are interested.

Unfortunately I don't have an arm64 device, else I would have tried it myself.