I'm an electronics engineer. I am mostly interested in embedded systems, low-level software development, digital signal processing , digital and analog circuit design, Real Time OS, Linux. My object is to be creative and innovative in the field of embedded system design. Currently working on Focal port for miatoll devices
if you wish to support my work please consider a small donation, thank you.
https://www.paypal.com/donate/?hosted_button_id=LJ4Q4DYM2LGB8
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.
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.
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.
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.
Well then try starting it your self. Nobody can force someone to start a port.
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
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
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
@nibzy26 yes that is the right procedure and Mi unlock tool is the right too for unlocking your device.
@muskist on what phone did you discovered this and which channel do you use for OTA.
Hello I am the maintainer of that port. You just need to download the stock android 10 firmware and flash it then install UT.
In order to do that you need to unlock your bootloader. The instructions on how to do that are at the bottom of that page.
https://devices.ubuntu-touch.io/device/joyeuse
You will see how to install section and there are links to the android 10 stock firmware and how to unlock your bootloader if you need help you can join our telegram group and we will help you
Good luck!
@muskist Thank you for that catch, just wanted to add a small note the Logs should be cleared on reboot if devel mode is not enabled.
@DPITTI thank you very much for the info.
Just to add a bit more clarification.
You need the official ROM because of the Vendor Specific Propitiatory Code or the vendor blobs as we call it , This blobs are located in the vendor partition of your device and are installed with the official ROM , UT cannot take this blobs and distribute them because this violates some license (Not very familiar what exactly) so thats why they need to be preinstalled on your device and thats done by the Official ROM (because they are distributed with it), when you flash UT on your device it does NOT delete this vendor partition (vendor blobs) but instead Halium is using it in order to make UT communicate with the hardware. Hope thats clarifies to you why you need Stock ROM installed on the device before installing UT.
@nibzy26 you dont need Lineage OS if you have official kernel avaliable. Some times its harder to find the manufacturers kernel so in that cases if the device has Lineage OS port it's kernel can be used instead. In your case thats not needed because you have official kernel from Xiaomi.
The other case which you might need to turn to Lineage OS is as specified previously, if you Don't have the right official ROM , then you can use Lineage OS ROM, but in your case thats not needed either, so you are safe to ignore Lineage OS at this point
Edit: also in the documentation there are 3 porting methods . The method which you should use is the Standalone kernel method , which is also the simplest way (Yayy)
I am glad that i could help a bit. Xiaomi has official repo in github with kernels for their devices
https://github.com/MiCode/Xiaomi_Kernel_OpenSource
There you can find the official kernel source for your device.
Looks like there are 2 versions of Redmi Note 10 you have to select the right one based on the device code name.
Redmi note 10 5g (camellia) with MT chipset
Redmi note 10 (mojito) with QCOM chipset
If i can help you with something else , let me know here or in telegram
Best of luck!
Lineage OS does not use halium gsi as far as I know , it uses android gsi, because it is an android based os. Halium is HAL between the vendor specific blobs and Linux based OS as Ubuntu touch.
When new android comes up talented developers create halium port for the corresponding android version. Currently halium 13 is in development and not stable yet for use for any ports. In order to make a port of android device to UT or similar Linux OS you need the android kernel from the device manufacturer (Xiaomi in your case), a halium gsi and ramdisk for the corresponding android version and the UT rootfs. All of this is explained in the porting guide so I would advice you again to read it.
If the device which you wish to port UT to has only android 13 stock ROM , that means that it is based on android 13 gsi ,so it needs halium 13 port in order to be able to communicate with the hardware (vendor blobs in the vendor partition ). There is a possibility if you device has Lineage OS port for older android version to use that and use older halium version, but if it does not then you would need to wait for halium 13 to come up or join the effort in developing it.
Good luck!