I'm writing this on Ubuntu Touch running on a Raspberry Pi 3 using the OSK on the Pi 7" touchscreen.
Thanks for the hard work put in. There are some issues still of course. Something odd with the graphics in Pi 4 windows and a slight overlap on the touch screen making left or right swipes tricky but this feels so much closer to useable than the first image. I don't think it is too far now from a platform that will showcase convergence and perhaps even let us develop apps live. I appreciate this is a side project so the UBports developers can't make it a high priority. Hopefully though the work done will help towards getting other Arm64 non-Android ports running smoothly. As a long term Linux user - trying to help get Unity8 or UBports working on the Pi has been very humbling - I'd no idea how little I knew/know!

Re: Continuation of rpi effort and how to test
There was a mouse hover event bug that has been fixed upstream making selection with mouse and keyboard a vastly better experience - not perfect yet but much more useable. Worth trying again if you found it too frustrating before.
Wifi is now working on the Pi 3 and Pi 4. We are trying to sort out sound and Bluetooth - any help welcome.
Due to the pinephone and other arm64 devices most apps are available and have been updated to work.
One continuing bug seems related to content hub and Apparmor not working. This means that copying files or pictures between apps is not working (and leads to crashes at times).
Another cause of crashes seems to be related to windows on the screen. Try not to move or change size when a window is rendering and windows rendering over other windows can also cause problems.
The Pi has not got much ram so running multiple browser tabs and/or too many apps at once will lead to problems.
https://ubports.com/blog/ubports-blog-1/post/raspberry-pi-266
https://gitlab.com/ubports/community-ports/raspberrypi
https://t.me/UBports_pi

Is there a place where UT progress and dead ends with the Pinephone are being documented? I find there is so much posted in the Pinephone group on Telegram and a lot of it is not UT specific so I don't follow it as much as I should. I'd still like to know more and try to apply it to the Pi.

@thousandtopics as it is already working on the Pi 3 (not working perfectly of course) he should manage to avoid eating a sock this time around.

Way back in the Canonical days I bought a BQ E4.5. When support was dropped some functionality was initially lost but now, under UBports and the community, the development and functionality of Ubuntu Touch and its apps is very much improved. Any thoughts on how far Ubuntu Touch has come in the last 5 years and how much further we may get in the next 5?

I realised that that post may look like I'm claiming some credit and that would be wrong.
Early on I did some blundering about in the dark and kept posting about my inevitable failures to encourage someone who knew what they were doing to help - that is the sum total of my contribution

@Flohack I have now updated the readme in a similar style to the Pinephone one and put in a merge request. Apologies if I've not followed the correct procedure - Gitlab is still new to me.

@advocatux Thanks - oh and apologies for re-opening a too old thread elsewhere

@thousandtopics as it is already working on the Pi 3 (not working perfectly of course) he should manage to avoid eating a sock this time around.

@atle said in Setting static Subnet IP Rpi 3/ latest UBPort:

Ubiqutiti Bullet M2HP(

I hope you got sorted out. Ethernet works with the Pi 3 but the IP address (static or otherwise) comes from whatever router you use and that is where you would set it.

Way back in the Canonical days I bought a BQ E4.5. When support was dropped some functionality was initially lost but now, under UBports and the community, the development and functionality of Ubuntu Touch and its apps is very much improved. Any thoughts on how far Ubuntu Touch has come in the last 5 years and how much further we may get in the next 5?

@gizmochicken I'd like to add a third point to that: will it mean that we will finally have a working display on the Raspberry Pi 4 running Ubuntu Touch? Rather a minority interest question perhaps.

@Jules I have the same issue on the OPO (rc). Everything else seems to work as usual but I can no longer move the map by sliding with my finger. If I attach a mouse then it works fine scrolling as expected whilst holding down the left button and moving the mouse.

@Mark Sound now works (HDMI and audio jack) on recent images with a newer kernel. Apparmor can be made to work by making some kernel changes (copied from similar changes made for the Pinephone) but this is not yet in the downloadable image.

@Pulsar33 Sorry if I misled you. I used the title "Progress on the Pi 3". I'd added in that Wifi is working on the Pi 4 for information but perhaps I could have been clearer. You can access the Pi 4 using SSH (which is why I know the wifi is now working) but the graphics problem still needs someone with a lot more knowledge and skill than I have to fix it. You can log into the Pi 4 in spite of the graphics issue and a screenshot looks fine even if the actual display has all the feedback lines. However if you open an app in a window then do a screenshot the graphics problem can still be seen in the window on the screenshot.

@Flohack I have now updated the readme in a similar style to the Pinephone one and put in a merge request. Apologies if I've not followed the correct procedure - Gitlab is still new to me.

Re: Continuation of rpi effort and how to test
There was a mouse hover event bug that has been fixed upstream making selection with mouse and keyboard a vastly better experience - not perfect yet but much more useable. Worth trying again if you found it too frustrating before.
Wifi is now working on the Pi 3 and Pi 4. We are trying to sort out sound and Bluetooth - any help welcome.
Due to the pinephone and other arm64 devices most apps are available and have been updated to work.
One continuing bug seems related to content hub and Apparmor not working. This means that copying files or pictures between apps is not working (and leads to crashes at times).
Another cause of crashes seems to be related to windows on the screen. Try not to move or change size when a window is rendering and windows rendering over other windows can also cause problems.
The Pi has not got much ram so running multiple browser tabs and/or too many apps at once will lead to problems.
https://ubports.com/blog/ubports-blog-1/post/raspberry-pi-266
https://gitlab.com/ubports/community-ports/raspberrypi
https://t.me/UBports_pi

@Mark Thanks to the Q&A for kindly complimenting my contribution. I try my best to learn and share. From a distance it is hard to know how helpful that is. I'll keep on learning, sharing and appreciating the support I get from the community.
PS I need to make my questions shorter and clearer