Hi jezek,
Please also note this link related to your topic.
In particular, it states:
The verification of the conformity of combinations of radio equipment and software by the radio equipment itself should not be misused to prevent the use of the equipment with software from independent suppliers.
End of quote.
Greetings
Mario
@rdfrs thats because apparmor rules (waiting for fix to trickle down to stable releases ask @Fuseteam he knows about this better then me)
confinment is mostly done, not a priority though because it will not raise security as much as you think only make it clearer to you the user what i am doing on you're phone, which granted is a very good reason and is why im working on it. (there is a branch with confinement implemented im just waiting until it won't break the app to use)
@lduboeuf Thanks a lot for the suggestions. That's interesting to hear that the nuntium restart command should be the same as rebooting. It happened often enough that I feel confident saying a reboot didn't happen.
Now that I've heard your idea about booting I wonder if the trigger that would cause the issue was reboots all along. I'd be disappointed with myself for not making that connection, but it's definitely possible.
I don't have this issue anymore, it occurred both on a previous phone (Oneplus 5T) and with a different cell provider (not sure which change fixed it), but I'll try swapping my SIM into that broken old phone and see if I can reproduce it just to see.
As ever, thanks so much for your work on MMS and for the help!
@owd200
Having the same Issue, so I searched through this Forum and found this: https://forums.ubports.com/post/69548
"To enter fastboot I had to
sudo reboot -f bootloader
in the UT terminal"
This worked fine for me, hope it helps.
@JayH
Yes, that is where I am stuck. I need to know what exactly is missing to complete the build. It's my first port, and I'm new to this. The port does reference other code via clone statements, so I have to look at that too. There are no comments that I am finding that tells me what does what. It will take me a while to figure out what each thing does and what goes where and when. I'm comparing other ports and reading some documentation, but it will be slow going on my own unfortunately.
@Simmonz Interesting. Have you tried contacting our Volla mates in their forum? There should be a more straightforward way of doing that. One of the benefits of such phones is that, since they have total control of the drivers, one can unlock the bootloader and lock it again after installing UT. Cheers.
@wally Bienvenue , as stated , newbie to phone and UT,
ok ,checking 3G is showing receiving and making a call, i guess you are right !! it does switch from L to 3G here too , so , learning here .
@stanwood I also live in Switzerland
I've got Fairphone 4 running 24.04-1.0 Beta 2 and my carrier is Yallo.
4G VoLTE is turned on but is unfortunately not working.
In the Ubuntu Touch Docs ( https://docs.ubports.com/en/latest/userguide/dailyuse/volte.html) one of the requrements is „Ubuntu Touch contains a VoLTE configuration for your carrier.„
Does anybody know how to create such a configuration?
@Simmonz I have moved your topic so that it is more clear to everyone what device you have. That was relevant for your question, but you did not specify it at the start.
@smoore100 You may have to look at installing the minimum Android version requirement before going to UT. You can check with the Volla guys which one is required before upgrading to UT. Cheers.
@stanwood said in Call for testing: Ubuntu Touch 20.04 OTA-10:
So, how will the update be rolled out to users on the stable channel? (OTA-9). Will they first receive the update to 20.04 OTA-10, then immediately afterwards the update to 24.04-1.0? Or will they have the choice between the 20.04 OTA update and the 24.04-1.0 update?
I must admit that I myself am a bit lost in all this
20.04 OTA-9 users will first receive 20.04 OTA-10 as an usual update. After that, they'll be offered an upgrade to 24.04-1.0. Users can choose whether to upgrade or not.
I'll try to make this more clear in our release announcement blog.
