Hello @ready-go . The current image is built for the Pi 3 only because the kernel is built for that Pi only. The Pi 4 image can be built, but nothing would be displayed because of missing support for some gpu functions in the version of Mir ( the display server ) currently used in UT. When we will reach the 20.04 base in Ubuntu Touch and upgrade Mir a functioning image could be released

How supported is the official 7" screen? The gestures to exit programs and bring up the launcher don't seem to work. The control center can be brought up though. overall, the system is much faster and smoother than I was expecting. Even if the gesture issues aren't resolved, I'm definitely going to try to make this system work out, since Android is slow.

@pulsar33 Thanks. I had no idea such a thing existed.

@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.

@Aury88 : some news about #371 distribution Starting as usual, terminal display is correct but graphical display is garbage as previously. I'm connected to a 4k Samsung TV (3840x2160) with a standard HDMI wire. I've not tested in 1920x1080 but previous tests have shown no difference with a Full HD monitor. So, after some time and automatic reboot, I've seen the same grey lines on white page screen, with some pixels blinking. Fortunately, the PrintScreen function has captured a 4k snapshot of the display and it is correct as you can see below (I've reduced the image size for forum convenience). So it is definitely a problem of bad parameters in the frame buffer (correct) to video output (garbage) process (I don't know the code breakdown). Good evening Pulsar33 [image: 1599935082376-screenshot20200912-ut371.png]

@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.

With some help from the RPi Telegram group (https://t.me/UBports_pi) between clicks and keyboard tab and enter I was able to get the "Next" button to be activated and am now past this timezone dialog. There were also issues with the touchscreen edge swipes not beind detected that I posted to the "Support" category as they may be broader than the RPi.

It took long but here we are: https://gitlab.com/ubports/community-ports/pinephone

Apologies for resurecting an old thread, but I was just wondering if anyone had made any headway with getting UT on a Pi?

@adams said in Widevine: As @dobey says, distributing a copy of widevine seems problematic, but strangely debian appear to have a package doing just that. I doubt Debian is actually distributing widevine. I don't see any available package for it on Ubuntu 18.04 at least. At most, it's probably in the non-free repository, and is simply a download and extract script, similar to how the flashplugin-installer package works, which downloads the official tarball from Adobe, unpacks into a temporary directory, then copies the plug-in to the destination location. It probably also only does this on x86 for widevine, which likely doesn't require downloading a 2GB ChromeOS recovery, and then extracting from there.

@aury88 That's true, my mistake. I read a time ago that there are deb based images for raspi 2 + 3. Maybe they call it different - can't find the name of the project.

@advocatux well, if this is the same, then yes. If click package is working

@jonius Ok! I only need a respberryPi, the PiPhone kit and to learn programming/porting x.D

@jonius Ok let me explain with a screenshot - this one is from the old boot layout, where android system is inside ubuntu.img and system.img is a hardlink to ubuntu.img, so please forgive the sizes of the files. This WILL change with Halium): partition BOOT: Contains initrd system with kernel and the usual initrd helpers [image: 1528024153388-5187ab83-cd25-4f04-85c8-4557a2dd807c-grafik.png] partition DATA: ext4 formatted, contains: on /data: ubuntu.img is the read-only root filesystem system.img contains the Android LXC container. This will not be needed at all for Raspberry folder user-data: Contains all user data from the home dir folder system-data:Contains system settings like WiFi, network, future printing, etc. So, if you manage to boot the raspberry image, your bootloader basically needs to follow the steps of https://github.com/ubports/ubports-boot and its initrd workflow. Specifically, see this init: https://github.com/ubports/ubports-boot/blob/master/initramfs/init BR

Thanks @alan_g for your feedback. Very appreciated.