Hello guys,
I am trying to continue the work of the previous porter for this devices and bring focal to miatoll devices. I will post here if I have any progress. So far I am setting up the enviroment needed to build and getting familiar with what needs to be done.
I do not have problem that you ping me. i simply dont understand why you pinged me thats why I ask.
I will try to explain simply how it works. Vendors which manufacture android phones, put their proprietary drivers and i vendor partition on the Flash memory of the device. We call this proprietary drivers "vendor blobs". Halium based OS as UT , Droidian and etc, use Halium as abstraction layer between the OS and the vendor blobs. What developers which work on halium do is reverse engineer how Android setup the vendor blobs and implement that in the halium project, then third party OSes (as UT , Droidian) use halium in order to provide different functionalities as telephony,wifi,camera,flashlight and etc.
If you want to gain deeper understanding on how exactly that is done and how halium works i would suggest to read the documentation.
In terms of VoLTE the IMS implementation is not standartized so the different vendors implement IMS functionality in different way in the vendor blobs. What we are trying to do now is reverse engineer how exactly Android communicate with the different vendor IMS drivers in order to setup the IMS functionality."
For telephony UT and other halium based OSes use ofono. Ofono have few different ways to communicate with the vendor blobs in order to provide telephony. The most recent method for achieving this is through binder (Android IPC). So ofono uses binder calls in order to communicate with the vendor cellular module. So what we are working on is understanding what binder IPC calls does Android do in order to setup the IMS for the different vendor blobs and implement that IPC calls in ofono. Sailfish OS already made IMS ofono extension for qcom based devices but this extension is proprietary and not open source.
As you can see from the explanation above the problem with VoLTE is not OS specific, but the problem is that the VoLTE vendor implementation is not standartized and for the different vendors a lot of tracing has to be done in order to understand how exactly android setup VoLTE and replicate that setup procedure in ofono for the different vendors.
Hope that brings some clarity on the subject.
Small update: I managed to build successfully the focal branch of the miatoll devices(YAYYY). Later on today i will try to boot it on my phone and see how it goes. I will post an update when i have more information to share.
Hi all, I got involved with UT from about a month and I love the project. I am electronics engineer and I am interested in helping as much as I can with development of UT , because I support the projects idea and vision.
I am currently maintaining focal port for miatoll devices, but I wish to get more into system development and plan to do another port too.
Thank you all who are working and supporting UT and making it real.
Update: We got focal running, most of the stuff work so far, i will perform a bit more testing and then i will upload it so everyone else can test it too. I guess a couple more days and it will be up for everyone.
The problem with windows is that when the phone goes into fastbootD the windows does not recognize it and you have to set up the driver from the device manager, then the windows will recognize the device and the UT installer will continue.
I am glad that you managed to install it from Linux and hope you enjoy.
Hello guys,
Small update . There is RC channel available now for miatoll devices, also when focal OTA-3 comes out there will be a stable channel too.
Have a great day/night.
Hello friend and welcome to he UT community! I hope you enjoy your stay here!
Redmi Note 9 pro devices are named miatoll and there are 4 separate devices which share that name, but have different codename:
This are the miatoll devices which are currently supported and maintained by the Redmi note 9 pro (RN9P) UT port.
Redmi note 9 pro 5g is a different device with different codename and its not currently supported by UT.
Hope this information clears up a bit the supported devices. If you decide to buy a miatoll device for UT please make sure it is one of the mentioned above and if you have any trouble with UT for this devices please let me know.
Best of luck and have a great day!
Hello @Kamikaze
We have some progress on VoLTE and I hope I would be able to share more details soon.
Another very nice community member made a telegram group for people which wish to follow the progress of the miatoll devises and help with testing or development. Here is the link if someone wants to join us and help.
Update: I am happy to tell you guys that the last know issue was resolved. I made a MR request to the webpage to update it to support focal and that it's no longer unmaintained device. Also we are working on the config for the installer and waiting the backend for OTA updates.
It turned out to be kind of port specific, but yes it can occur on other devices with a bit older kernel as miatoll was. The fix is quite easy.
The Xperia port had the same issue as miatoll and it turned out to be the same kernel problem even that both devices use different kernel versions.
This is the source of the issue. If in the kernel the
oom_adj
oom_score_adj
Files are with read only permissions 400 the problem will most probably occur. Because lomiri-app-launch spawns SUID helper when it cannot set the scores in this files by it self and the spawn is done by forking so the freezes occured because of the forking.
The problem with lomiri-app-launch is that it spawns a process for each thread to adjust the score which is not very good and in some applications as chrome this is a lot of processes and forks which copy pages and that's slow, but by making lomiri-app-launch able to set the scores by it self then it does not need to spawn SUID helper so no forks no freezes.
Hope I managed to explain it clearly enought.
If you need more information you can contact me in telegram.
Hello again Dear Friend,
Thank you very much for your worm words , it is really nice to meet nice people like you!
@pe3noATo2DOTpl said in Redmin Note 9 Pro doubt - Fake/Virtual 8GB of RAM?:
30). By the way, could you maybe share some YT links to the films where the UT @ Redmi Note 9 Pro are presented, please ?
As an UT Ambassador I would have a Great Help/Tool to promote our Great Phone System, as I really want to share the best of what I/we have
Unfortunately I do not have any UT videos on redmi note 9 pro, but there should be plenty videos on how UT works on different phones on Youtube.
Here a link which summarize very well the focal OTA3 update.
https://www.youtube.com/watch?v=0pRgF2aslW4
Here a nice video which explains the vision of UBports
https://www.youtube.com/watch?v=1sPtRdZlEu4
Here a link of the Redmi Note 9 Pro device page, which summarizes what works currently on this UT port.
https://devices.ubuntu-touch.io/device/joyeuse
Please let me know if you need any help and best of luck!
Hello ,
I would like to ask in which parts/features/modules of UT development, developers are most needed?
Thank you again for this amazing project.
Thank you for the info. I managed to build the stable version of miatoll port today . And from tomorrow I will start working on focal. I will try droidian too since I am also interested more in having closer desktop feeling on my phone , but I also want to try to maintain miatoll for UT too. I believe with focal and libertine containers we can have good desktop feeling on UT too
@Enrico13011978 Why do you need newer android version ?
The UT Focal port is ready and can be installed from the installer. Make sure to choose the 20.04/devel channel if you wish to test Focal and if you find bugs please report them in https://t.me/ut_miatoll
Have a great day/night
i will be more than happy to help in the development of VoLTE support in UT, if i can. So if someone is working or is planning to work on that , contact me if you want to split the development effort.
image url)
Hello guys the installer was fixed and now you can install focal on miatoll devices. Please make sure to check the "Partitioning" check box if you install focal for first time or the installation will fail.
If you are using Xenial you CANNOT update to focal from OTA you need to do it from installer, but just uncheck the wipe option , but KEEP the partitioning button checked
there is a known issue with the flashlight (currently working on it) and there are some freezes when you switch between apps.
Have a good day/night