Wrong kernel on Redmi 9 (codename lancelot)
-
Hi guys.. New here. I flashed Ubports on my lancelot (24.04-1.0 Stable) a few hours ago and I noticed that sim 2 wasn't being detected. Last time I flashed ubports (focal) a few months ago both sims were being detected.
So I went digging around and saw that the running kernel is 4.14.355-openela-merlin, which I don't think is the correct one- I correctly selected lancelot while installing. I used the ubports installer in windows 10.
Under imei only one imei is listed, the other one just has 'none' -
@Keli
I don't think any UT port currently supports two SIM cards.
The Android version prior to installing UT is 11 (here is the link https://github.com/ubuntu-touch-redmi-mt6768/lancelotfw/blob/main/README.md).
The device has to be unlocked.
After that the installer assume all the work.
-
@Vlad-Nirky If I remember correctly, UT supported two sim cards on lancelot, just that you couldn't use the second sim card for mobile data like it says on the devices page. But you could make and receive calls using both sim cards.
Also, merlin is not lancelot. -
Below are two screenshots taken months apart. One while using UT on focal and one that I took yesterday. Look at the network indicators. One shows two while the other one shows one.
-
@Keli
OK.
I've amended my reply.
And which kernel version was running when this screenshot was taken?
Do you think it's a regression?
https://gitlab.com/ubports/porting/community-ports/android11/xiaomi-redmi-9/kernel-xiaomi-mt6768https://gitlab.com/ubports/porting/community-ports/android11/xiaomi-redmi-9/kernel-xiaomi-mt6768
You may report an issue on one of these.
Was the screenshot taken in Noble?
-
@Vlad-Nirky I don't think it's a regression. I'm not sure how the UT images are baked or how the install process is done by the installer. But it's obvious that I have a Redmi Note 9 kernel instead of a Redmi 9 one.
Maybe there was a mixup and somehow the install script is being instructed to flash a wrong kernel image.
In android lingo, flashing the correct boot.img in fastboot would have fixed the issue.
I guess it's upon the device maintainer to answer these maybes. -
@Vlad-Nirky I don't know which kernel version I was running back then. But I know that both sim cards were being detected and noble was still in beta at the time.
When noble was announced I decided to give UT touch another go and here we are. -
@Keli I have lancelot with the same kernel, both sim cards are detected for me
I am on 24.04-1./x daily but not the latest, could try on the latest daily?
-
@Fuseteam thanks for the suggestion. Let me look into it.
-
I downloaded a daily build update and installed it, the update was successful.
Sim 2 wasn't being detected nonetheless. So I decided to switch the sim cards. Sim 1 wasn't being detected. Hmm..
I decided to test the problematic sim card on another phone - also a lancelot running stock android, it worked there.
I decided to use an old sim card on my lancelot to see if it would be detected. It was.
The problematic sim card was working just fine before switching to UT from Android.
Anyway, it seems like UT doesn't like this sim card. Has anyone encounter this issue before? Is there a reason why UT would fail to detect a working sim card?
Below are some screen grabs highlighting the above issue.
-
@Keli
To complete the test the non working SIM should be inserted in another phone running Android, to see if it is still OK. -
@Vlad-Nirky I did test the non working sim card (the one that can't be detected) on another phone, also a lancelot but running MIUI. It works there. The old sim card that was decommissioned doesn't work in the sense that it can't register to its network and that's why it says 'unknown' as you can see from the screen grab - but at least it can still be detected by the phone.
The working one that I would like to use fails to be detected on both slots hence the 'No Sim' error message. -
@Keli
Is there a mix regarding VoLTE?
One that has it and one that doesn't?
Can your other phone hold two SIM cards?
If so, it would be interesting to know if they can work together. -
@Vlad-Nirky No it isnt a VOLTE issue and yes both sims are VOLTE capable and both work well together. I haven't tested VOLTE under UT on either sims though. But VOLTE is problematic even on stock Android for lancelot in my country.
-
I had to reinstall Android unfortunately
Both Sims are working. Will give UT another go sometime in the near future.
Thanks everyone. -
I gave it another try, it's all good now.
-
@Keli
Hello.
Right after reinstalling? -
@Vlad-Nirky Yes it worked after reinstalling.
-
When I say reinstalling, that's just putting it mildly.
Let me post this in the hope that someone might find it useful.
A couple of months ago I tested UT using the normal install procedure (Stock vendor, A11) vs an edge case procedure (OSS vendor, A13) and found out that UT worked roughly the same in both instances.
Since then, using OSS vendor has been my preferred method of getting UT on my lancelot -I'm the edge case, testing the untested.
With this method, I can easily test feature availability/issues between firmware versions (I cannot access the call waiting setting under firmware v12.5.6.0 but can with v12.5.4.0 for example), easily move between Android and UT etc.
So here's how I move from UT to OSS Android for example:- Reboot the device into fastboot (The one with an orange text)
- Run
fastboot flash recovery recovery.img - Run
fastboot flash boot boot.img - Run
fastboot flash dtbo dtbo.img - Run
fastboot flash vbmeta vbmeta.img - Run
fastboot wipe-super unsparse_super_empty.img - Run
fastboot reboot recovery - Run
adb sideload lineage.lancelot.ziponce the device reboots into lineage's recovery.
I run these commands under linux and this workflow has never failed me.
I use an unofficial lineage 20 zip for lancelot which has all these files inside the archive.
To go back to UT, I just put the device in fastboot mode and run the ubports installer.
-
@Keli
Thank you for sharing your knowledge.
Very interesting...
And what LineageOS ROM are you using exactly?
