@kugiigi Yeah, the dock works on Manjaro phosh for both usb mouse/keyboard and external display, so I know it's not the dock. I messed around with mounting the root filesystem as writable for a bit and apt installing a few things, as initially I was not able to get libertine to work, so I'm going to try flashing a fresh dev image and see if that helps at all.

@flohack I've successfully installed the OS on the Pixel 2. I'm getting a lot of touchscreen problems though, like double or ghost touches. Shutdown seems to really power off the device though.

@franzm You're welcome, I'm glad the gps is working, enjoy your new mobile with Ut. Regards...

@lakotaubp Sorted. The phone was not booting to recovery mode by pressing vol down and power. So tricked it by failing the upgrade from settings which took me to the recovery screen. The installer worked from there with wipe data and reflash partitions not selected. Data intact, now at OTA-23 and happy again Would the 'un-brick' my Volla X route be to go back to the stock software given above (on halium9) and then install the latest OTA from the installer with the 'flash partition' option selected?

@pe3noATo2DOTpl I've had issues to login in google play too. I just use the Aurora Store from FDroid instead. Maybe that works for you too.

@azraelpwnz note that SMS is now 100% reliable in and out. MMS photos work in and out with wifi OFF. Wifi ON is a problem, but broader than the P3a. https://forums.ubports.com/topic/6039/bounty-for-pixel-3a-halium-9-stability/18?_=1630188659271

@luksus So, I checked for updates and it reported software up to date. On investigation I discovered it was on release candidate channel, so I switched to devel channel and it downloaded 532mb of updates. I installed the updates and after a couple of trys, I managed to coax it to boot. Deep joy, it booted into staged mode! So pleased with the result. I am typing this on my Lenovo tab. Thank you so much for working your magic.

@TheVancedGamer Sorry. I somehow mamaged to downvote your post. Fat fingers on a small screen. I have upvoted to remove the downvote

@DPITTI I don't know why you got upset this time, but as I told you you are free to use what ever you want. Using and testing UT is a personal choice and if you are not satisfied with your experience then you can just put another OS. You are welcome to come back and try out UT whenever you want. Have a great day and I hope you find the right OS for your needs.

@cpb I don't think that is feasible. The edge gestures are system gestures. In-app gestures are something the app can do if they want (but it can't be from the left/top/right edges, only the bottom. Changing to what you suggest would be untenable, requiring every app developer to change their apps, and a massive overhaul of the whole system.

@TobsEnd I also have this problem since a few months in devel.

Anyone using this tablet has been able to get decent stylus behavior/functionality?

@Tommy You might look at https://jmp.chat/ I got it for pure XMPP access to SMS/MMS, but later got their SIM and a data plan. They're a MVNO--T-Mobile here--and have a fork of Android Conversations to also do telephone calls (based on WebRTC, apparently). So it might help, though of course I recognize an Android app isn't an immediate solution for UBports! But they do support SIP into telephony for your phone #. https://f-droid.org/en/packages/com.cheogram.android/

@Wendigo said in Sakawochi development thread: But please don't expect anything soon. No pressure

@stropbu Firmwares are not made by ubports, nor canonical in the passed days. OS is what they make and you're talking about

I had Meizu Pro 5 Ubuntu Edition but run into the https://forums.ubports.com/assets/uploads/files/1528013524195-8a15d567-ca4b-44ca-a1ce-84fdb7e0aec7-image.png screen when first trying to update it to Ubports 16.04/stable channel. Somehow now later I managed to flash - with ubuntu-device-flash - from within 16.04 ubuntu installation (actually, 16.04 lxd container with usb vendor specific passthrough). I did that by booting to Ubuntu's recovery installation with power button + volume up - this is where you might need the recovery-turbo.img but I had it flashed already. I verified that from within my lxc container (where I had added lxc config device add CONTAINERNAME meizu usb vendorid=18d1) I was able to see the device with 'adb devices'. Then I ran ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=ubports-touch/15.04/stable - I thought it got stuck after downloads, but actually then it started the "Pushing" phase. And even more to my surprise, it rebooted to flashing phase with Ubuntu prorgress bar going back and forth, and then booted into working Ubports installation! Even though I specified "15.04/stable", it seems it too pointed to 16.04 already, ie OTA-5. The greatest thing was that since I didn't need to specify --bootstrap or --wipe, it was even the same installation I used as my main phone back in the days, so I had all my apps and photos intact.

@thepossessor Thanks for letting me know, and a big welcome back to the Luxembourg timezone