@lduboeuf
No logs unfortunately.
I was surprised too but according to the BBC website (UK national news) - " The alerts will work on all 4G and 5G phone networks and on devices with the following software:
iPhones running iOS 14.5 or later
phones and tablets running Android 11 or later
Older "non-smart" phones will be unable to receive the alerts, and nor will devices that are turned off or on aeroplane mode. "
@sb I'm just starting with QML too so don't take anything i say as a good idea! but in the documentation it seems contentComponents width and height should be set to the parent Page width and height NOT BottomEdge.
I was still getting the same problems after changing this so I tried setting the contentComponent to a Rectangle and nesting the PageStack inside. After this, myStackPage.height no longer resets to 0.
Hope this might help
@moodroid thanks so much, that worked. I did not realize there were multiple lines i had to edit.
Could some kind soul show how to add 'MOZ_USE_XINPUT2=1' to the desktop file? I have tried adding at the start, end and in between 'firefox' and '%u' in Exec. All this does is open firefox at the url 'MOZ_USE_XINPUT2=1'. Is this even the right place to add it ?
If you could explain it like you would to a small child or a dog, as that is clearly my level of knowledge with this sort of thing : )
My Pixel 3a has always done this. On Xenial, the screen would go off/black then back on showing whatever app was open until a hard reboot. On Focal it is exactly as the OP described with the ubuntu loading screen. This can happen any time, not just when using the messaging app, it even happens when the phone is sitting on my desk not being used. I always assumed this was some specific issue with my device. I ran 'top' after this mornings crash but i have no idea what I'm looking for.
@lduboeuf
No logs unfortunately.
I was surprised too but according to the BBC website (UK national news) - " The alerts will work on all 4G and 5G phone networks and on devices with the following software:
iPhones running iOS 14.5 or later
phones and tablets running Android 11 or later
Older "non-smart" phones will be unable to receive the alerts, and nor will devices that are turned off or on aeroplane mode. "
On P3a no emergency notification but I didn't realize I had to be on dev, my bad. In the UK it is only 4g/5g that receive the broadcast and in my networks forum a poster said only android 11 and above would work. Would that have an impact on Ubuntu Touch devices ?
@sb I'm just starting with QML too so don't take anything i say as a good idea! but in the documentation it seems contentComponents width and height should be set to the parent Page width and height NOT BottomEdge.
I was still getting the same problems after changing this so I tried setting the contentComponent to a Rectangle and nesting the PageStack inside. After this, myStackPage.height no longer resets to 0.
Hope this might help
@rik
I may be a bit late but just got a pixel 3a working with UT. I am in the UK and CAN send / receive SMS and MMS with the wifi on.
Just an update, I could not find any info on android 9 breaking the sensors anywhere. Whatever the issue is, it must only affect a small number of phones.
Got another pixel 3a, flashed 9, sensors work! Installed Ubuntu Touch and sensors work! UT looks amazing on this phone and I have not had to charge it in 24 hours! Still have to test everything out such as MMS.
As for the original phone, as it works on 11, I gave it to a family member who needed a new android phone.
Man, Ubuntu Touch is getting expensive 
@rocket2nfinity
Thanks for the explanation. I took your advice and found that the February 2021 update fixes my sensor problems. The release notes contain "Fix for issue preventing certain sensor detection on startup".
I guess UT will never run on this phone 
but at least it's fully working on android.
Thanks @rik and @rocket2nfinity for your help.
@rik
I don't think anyone here in Ubuntu Touch land needs to worry about this sensor bug. The first fix for affected phones was to roll back to android 9, then all sensors would return. So anybody flashing android 9 should be okay... except me who is back at square 1.
For what it's worth, MOST of the affected phones previously had custom rom's. The main issue being twrp log files corrupting the persist partition. ( twrp no longer uses this partition )
Does anybody know why we have to flash android 9, would installing Ubuntu Touch while on android 11 be a bad idea ?