@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
I just noticed in fastboot the device name is 'bengal' and not 'billie'. Is this normal or do I have the wrong device maybe ?
I just noticed in fastboot the device name is 'bengal' and not 'billie'. Is this normal or do I have the wrong device maybe ?
@Kamil Yes, I think this is what i am experiencing. Just tested Nord N100 and Pixel 3A on testufo.com. The 3A holds 60 fps pretty well while the N100 is constantly dropping from the mid 50s to as low as mid 20s.
@MrT10001 Yes restarted a couple of times with no change. I not sure if laggy is the correct term but it's not smooth when scrolling like my Pixel 3A. I might do a fresh install and see if it changes.
I just installed ut on a Nord N100 and everything works but it's very 'laggy' compared to my Pixel 3a. Opening the app drawer or scrolling for example. Does anyone else notice this or did I mess up the install ?
@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