Development [ROM][11.0][UNOFFICIAL] [DISCONTINUED] Lineage OS 18.1 for Redmi Note 10 (mojito / sunny)

[Zirila]

I made a backup with twrp from data partition before.
If I flashed Lineage, can I resore data with twrp or can this break something? Or does Lineage not start then?

if you make a backup of MIUI data partition, you can't restore this to a LOS data partition, these are 2 different ROMs.
even backup up and restoring data partition of only LOS is tricky. you can find infos about that in the TWRP thread.

 

[Subhan.]

regarding the alarm clock, i quote something from the AOSP FBE documentation:



FBE and Direct Boot isn't that new in 2021, but it seems like it is actually the problem with the alarm clock in this LineageOS version.
Probably, the alarm-clock app isn't Direct Boot aware or is not available in Device Encrypted (DE) storage, and therefor can't ring the alarm upon boot until the user would enter the credentials to unlock the userspace and data.

@Subhan. maybe you can take a look at this if you find the time, I guess this would work if it gets rolled out correctly, but you probably know more about the options than me

Ok so I def will look into it and if I find a fix i will def add it but it wont be included in this update instead the one after this update
For the next build, there are some optimizations, partition size for flashing gapps, microg or the recovery related zips, aptx etc

 

[Zirila]

Ok so I def will look into it and if I find a fix i will def add it but it wont be included in this update instead the one after this update
For the next build, there are some optimizations, partition size for flashing gapps, microg or the recovery related zips, aptx etc

I'm excited for anything that improves the situation
do you plan to provide a flashable microg zip for spoofing and flashing the apps?
i think the most wanted features currently are working methods for troubleless upgrading and a video recording fix.

 

[Subhan.]

I'm excited for anything that improves the situation
do you plan to provide a flashable microg zip for spoofing and flashing the apps?
i think the most wanted features currently are working methods for troubleless upgrading and a video recording fix.

1)(This update) This time I will make sure the dirty flash works I will do a dirty flash myself first from the last release(but with Los recovery)
2)(Next Update) I have an idea but that might take some time(a dev suggested me to add anx in Los but I want to keep los as simple as possible)
So will check if any part or libs from anx can solve the video recording and will only add that

(No eta)I will try to check the micrgo spoofer too but well that might take time

 

[Zirila]

1)(This update) This time I will make sure the dirty flash works I will do a dirty flash myself first from the last release(but with Los recovery)
2)(Next Update) I have an idea but that might take some time(a dev suggested me to add anx in Los but I want to keep los as simple as possible)
So will check if any part or libs from anx can solve the video recording and will only add that

(No eta)I will try to check the micrgo spoofer too but well that might take time

alright!
I'd currently upgrade using TWRP or fastboot flash, but if it works with LOS recovery it should work with TWRP too (i hope). otherwise, flashing LOS recovery isn't that much of a deal either.

hm I think, it would still be better to provide a real clean vanilla image of lineageos and try to provide everything else as additional, flashable (magisks) .zips. some people might not trust the xiaomi proprietary camera libs if they were integrated into the vanilla image. that way users could decide between clean ROM and working camera. Though, I still expect the camera to work out of the box after some firmware upgrades in the future and that all this isn't necessary anmore.

if lineageos goes official anytime in the future, lineage.microg.org would automate the spoofing process without anyone needing to do extra stuff, that would be really cool too. as long as it's unofficial we can spoof it ourself with haystack and maybe provide a .zip for magisk for each update.

 

[nierewa]

I flashed LineageOS with the Fastboot scribt.
Now the recevery isn't TWRP anymore but PE Recovery.

Can I reflash TWRP like explained in Teamwin tread

 

[Zirila]

you always need to reflash any 3rd party recovery (like TWRP) after flashing ROMs. First fastboot.exe boot twrp.img, then install it to ramdisk. why is that so? read this once to understand:

How A/B Partitions and Seamless Updates Affect Custom Development on XDA

You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?

www.xda-developers.com

 

[nierewa]

Ok. Now I'm happy

 

[Subhan.]

Changelog (21/07/21):
• Dropped gapps variant
• Switched to User builds
• Increased system partition's size
• Included TWRP 3.5.2
• Set props for Rounded Gboard(If you install Gboard)
• Setup required props for userspace LMKD
• Switched Skia rendering backend to Vulkan
• Enabled force triple frame buffers
• Added bluetooth aptX blobs from redfin

 

[Zirila]

Changelog (21/07/21):
• Dropped gapps variant
• Switched to User builds
• Increased system partition's size
• Included TWRP 3.5.2
• Set props for Rounded Gboard(If you install Gboard)
• Setup required props for userspace LMKD
• Switched Skia rendering backend to Vulkan
• Enabled force triple frame buffers
• Added bluetooth aptX blobs from redfin

reporting back after upgrading to this version.

I had LOS version of June installed along with TWRP 3.5.1 (both on A slot) and after excessive backups I tried upgrading by dirty-flashing to this LOS version of July.

Now I know from previous attempts, that LOS Recovery seems to be working better than TWRP for upgrades, my first step was therefor flashing LOS Recovery, overwriting TWRP.
I first thought I might try MPK99 custom ROM fastboot flash install script, but by the date trying, it was already abandoned due to (unknown?) technical difficulties. So I stick with recovery installation method.

I upgraded via LOS-Recovery and that worked just fine. I rebooted to recovery again, and it started up TWRP as it is part of LOS-rom.zip this time (I would still prefer LOS-recovery getting shipped with the ROM for real vanilla, though)
After rebooting to system, the first start finalizes the installation, and this is the -first time ever- that an upgrade successfully installed itself from previous Slot A to Slot B without troubles. After first ROM start and a reboot to TWRP all errors shown right after the upgrade in tWRP were gone. Fine!

Luckily, this time, the old magisk signature spoofing module from previous LOS version still works without needing to run haystack again, so actually everything seems to be working out of the box after upgrading and all apps and data is still there and working.

So far so good!


Now, a few things I noticed:

- USB-Debugging is still activating everytime after booting, despite disabling it in the dev-options (rebooting while connected to PC with usb cable -> automatically always establishes usb-debugging connection)
I'm not entirely sure if this is supposed to be fixed in this version by switching to "user builds". Or maybe it's a settings issue when upgrading from previous lineageOS version? maybe you can tell me.

- quick panel icons are still lined up by 2 rows instead of 3 rows in previous versions and some original LOS icons seem to be missing. (again, I'm not sure if this was supposed to be fixed in this version, or whether my older settings overwrite any changes made)

- I've got a phone with 64GB internal memory. On previous and latest version, System (all Slot A+B) takes already 19GB of space, leaving only 45GB free space for internal storage.
Is this supposed to be normal, how many space does your system take and how many space do you have available as free storage (excluding external sd cards)? It looks a bit much for me..

- camera bug still exists but I didn't expect otherwise. I also did not test any of the new kernels yet, but I think they won't change anything yet.

if I found something else I'll post more.

Thanks so far for the updates

 

[MPK99]

reporting back after upgrading to this version.

I had LOS version of June installed along with TWRP 3.5.1 (both on A slot) and after excessive backups I tried upgrading by dirty-flashing to this LOS version of July.

Now I know from previous attempts, that LOS Recovery seems to be working better than TWRP for upgrades, my first step was therefor flashing LOS Recovery, overwriting TWRP.
I first thought I might try MPK99 custom ROM fastboot flash install script, but by the date trying, it was already abandoned due to (unknown?) technical difficulties. So I stick with recovery installation method.

I upgraded via LOS-Recovery and that worked just fine. I rebooted to recovery again, and it started up TWRP as it is part of LOS-rom.zip this time (I would still prefer LOS-recovery getting shipped with the ROM for real vanilla, though)
After rebooting to system, the first start finalizes the installation, and this is the -first time ever- that an upgrade successfully installed itself from previous Slot A to Slot B without troubles. After first ROM start and a reboot to TWRP all errors shown right after the upgrade in tWRP were gone. Fine!

Luckily, this time, the old magisk signature spoofing module from previous LOS version still works without needing to run haystack again, so actually everything seems to be working out of the box after upgrading and all apps and data is still there and working.

So far so good!


Now, a few things I noticed:

- USB-Debugging is still activating everytime after booting, despite disabling it in the dev-options (rebooting while connected to PC with usb cable -> automatically always establishes usb-debugging connection)
I'm not entirely sure if this is supposed to be fixed in this version by switching to "user builds". Or maybe it's a settings issue when upgrading from previous lineageOS version? maybe you can tell me.

- quick panel icons are still lined up by 2 rows instead of 3 rows in previous versions and some original LOS icons seem to be missing. (again, I'm not sure if this was supposed to be fixed in this version, or whether my older settings overwrite any changes made)

- I've got a phone with 64GB internal memory. On previous and latest version, System (all Slot A+B) takes already 19GB of space, leaving only 45GB free space for internal storage.
Is this supposed to be normal, how many space does your system take and how many space do you have available as free storage (excluding external sd cards)? It looks a bit much for me..

- camera bug still exists but I didn't expect otherwise. I also did not test any of the new kernels yet, but I think they won't change anything yet.

if I found something else I'll post more.

Thanks so far for the updates

Do you fond to use telegram ?
If so, you can contact us (literally all the devs) as we're available there 24x7 interacting with community users in runtime.

Here's the Redmi Note 10 Community
If you have any queries, tag us there & we'll reply to you instantly.

 

[Zirila]

Do you fond to use telegram ?
If so, you can contact us (literally all the devs) as we're available there 24x7 interacting with community users in runtime.

Here's the Redmi Note 10 Community
If you have any queries, tag us there & we'll reply to you instantly.

I'd join but sorry I'm not using telegram, I intentionally don't use any messengers that are tied to phone numbers. Maybe if you have a matrix channel/bridge. Or anything similar.

 

[pnplusplus]

Thanks for the rom. Can you add 3 swipe screenshot?

 

[Zirila]

been a few days on this updated LOS version now, and one thing really stands out.
battery performance was great before, but this version is phenomenal regarding battery life.
I'm on my 3rd day with average usage without charging and still have 50% battery left.
before I had 40-50% battery after 2 days. so it seems like something (vulkan switch?) is really pushing the battery life in this update.
coming from an old phone that only lasted for half a day, this is mind blowing.

 

[Subhan.]

reporting back after upgrading to this version.

I had LOS version of June installed along with TWRP 3.5.1 (both on A slot) and after excessive backups I tried upgrading by dirty-flashing to this LOS version of July.

Now I know from previous attempts, that LOS Recovery seems to be working better than TWRP for upgrades, my first step was therefor flashing LOS Recovery, overwriting TWRP.
I first thought I might try MPK99 custom ROM fastboot flash install script, but by the date trying, it was already abandoned due to (unknown?) technical difficulties. So I stick with recovery installation method.

I upgraded via LOS-Recovery and that worked just fine. I rebooted to recovery again, and it started up TWRP as it is part of LOS-rom.zip this time (I would still prefer LOS-recovery getting shipped with the ROM for real vanilla, though)
After rebooting to system, the first start finalizes the installation, and this is the -first time ever- that an upgrade successfully installed itself from previous Slot A to Slot B without troubles. After first ROM start and a reboot to TWRP all errors shown right after the upgrade in tWRP were gone. Fine!

Luckily, this time, the old magisk signature spoofing module from previous LOS version still works without needing to run haystack again, so actually everything seems to be working out of the box after upgrading and all apps and data is still there and working.

So far so good!


Now, a few things I noticed:

- USB-Debugging is still activating everytime after booting, despite disabling it in the dev-options (rebooting while connected to PC with usb cable -> automatically always establishes usb-debugging connection)
I'm not entirely sure if this is supposed to be fixed in this version by switching to "user builds". Or maybe it's a settings issue when upgrading from previous lineageOS version? maybe you can tell me.

- quick panel icons are still lined up by 2 rows instead of 3 rows in previous versions and some original LOS icons seem to be missing. (again, I'm not sure if this was supposed to be fixed in this version, or whether my older settings overwrite any changes made)

- I've got a phone with 64GB internal memory. On previous and latest version, System (all Slot A+B) takes already 19GB of space, leaving only 45GB free space for internal storage.
Is this supposed to be normal, how many space does your system take and how many space do you have available as free storage (excluding external sd cards)? It looks a bit much for me..

- camera bug still exists but I didn't expect otherwise. I also did not test any of the new kernels yet, but I think they won't change anything yet.

if I found something else I'll post more.

Thanks so far for the updates

Welll about the usb debugging bug it only goes away with clean flash
I dirty flashed and clean flashed a no. of times to test and it went away only in clean flash

I kinda forgot about the qs panel....
Will try to fix in the next update

Afaik all custom roms on rn10 take about 19-20 gb in system

Well I will try to work on cam bug There is some other cam related background stuff that I have to work on too

 

[Angenios]

I'm a newbie and I don't understand one thing: when I install this custom ROM, root access is already enabled? If yes, how do I install universal fix?
Thank you for your time.

 

[Subhan.]

I'm a newbie and I don't understand one thing: when I install this custom ROM, root access is already enabled? If yes, how do I install universal fix?
Thank you for your time.

Nope, You'll have to root it with magisk yourself and then flash universal magisk there

 

[Angenios]

Nope, You'll have to root it with magisk yourself and then flash universal magisk there

And in order to install Magisk I only need to install it through TWRP, right? If yes, in what order do you suggest?
1. Install TWRP -> 2. LineageOS -> 3. GApps -> 4. Magisk -> 5. universal fix
Is it correct?
Thank you for your answer.

 

[Zirila]

Welll about the usb debugging bug it only goes away with clean flash
I dirty flashed and clean flashed a no. of times to test and it went away only in clean flash

I kinda forgot about the qs panel....
Will try to fix in the next update

Afaik all custom roms on rn10 take about 19-20 gb in system

Well I will try to work on cam bug There is some other cam related background stuff that I have to work on too

Ah, too bad about the clean flash and usb debugging.
Well, then I'll have to do a clean flash at some point in the future, I don't know when I'll try that yet. Big ups to you for testing and finding that out.

phew, 20gb system is pretty much, but if this is the new normal, well, it's what it's like...

no prob about the qs and cam bug, still happy about every feature and security update that you can bring up to the table!

 

[Subhan.]

reporting back after upgrading to this version.

I had LOS version of June installed along with TWRP 3.5.1 (both on A slot) and after excessive backups I tried upgrading by dirty-flashing to this LOS version of July.

Now I know from previous attempts, that LOS Recovery seems to be working better than TWRP for upgrades, my first step was therefor flashing LOS Recovery, overwriting TWRP.
I first thought I might try MPK99 custom ROM fastboot flash install script, but by the date trying, it was already abandoned due to (unknown?) technical difficulties. So I stick with recovery installation method.

I upgraded via LOS-Recovery and that worked just fine. I rebooted to recovery again, and it started up TWRP as it is part of LOS-rom.zip this time (I would still prefer LOS-recovery getting shipped with the ROM for real vanilla, though)
After rebooting to system, the first start finalizes the installation, and this is the -first time ever- that an upgrade successfully installed itself from previous Slot A to Slot B without troubles. After first ROM start and a reboot to TWRP all errors shown right after the upgrade in tWRP were gone. Fine!

Luckily, this time, the old magisk signature spoofing module from previous LOS version still works without needing to run haystack again, so actually everything seems to be working out of the box after upgrading and all apps and data is still there and working.

So far so good!


Now, a few things I noticed:

- USB-Debugging is still activating everytime after booting, despite disabling it in the dev-options (rebooting while connected to PC with usb cable -> automatically always establishes usb-debugging connection)
I'm not entirely sure if this is supposed to be fixed in this version by switching to "user builds". Or maybe it's a settings issue when upgrading from previous lineageOS version? maybe you can tell me.

- quick panel icons are still lined up by 2 rows instead of 3 rows in previous versions and some original LOS icons seem to be missing. (again, I'm not sure if this was supposed to be fixed in this version, or whether my older settings overwrite any changes made)

- I've got a phone with 64GB internal memory. On previous and latest version, System (all Slot A+B) takes already 19GB of space, leaving only 45GB free space for internal storage.
Is this supposed to be normal, how many space does your system take and how many space do you have available as free storage (excluding external sd cards)? It looks a bit much for me..

- camera bug still exists but I didn't expect otherwise. I also did not test any of the new kernels yet, but I think they won't change anything yet.

if I found something else I'll post more.

Thanks so far for the updates

Well so about the built in twrp
Well first I wasnt able to compile user builds(Lineage doesnt have user builds officially)
With some changes I was able to compile but then wasnt able to boot to recovery so then I had two option either to go with userdebug builds or user builds with twrp
And well then I decided to go with user builds and builtin twrp