yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] barturblits:
Well the fix is basically resetting the super partition and do a manual update the LOS way. Last failed ota i tried the same thing without the reset of super and that did not make it boot.

No only through manual sideloading the update with LOS recovery.

Yup, I never need to flash gapps. All included. But i still have to patch Magisk, normally right after the OTA before the reboot. That worked flawlessly in LOS 18.1.

After this manual update with the reset of super I also had a regular OTA now with success. This time I did not patch magisk before the reboot, just to be safe. Gonna try that next OTA.

I only boot custom recovery through fastboot, I did not install it in the ramdisk.

BTW, did you ever execute this step in the magisk installation documentation:

(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

It says it is optional. It looks like you only need to set some flags or parameters to this partition, nothing is said about what vbmeta.img file. I never did it and never had a problem with Magisk itself. Problem is I have no idea what it does, why it is optional and how you can diagnose if you need it. And if you need to flash this manually after every OTA or if it is a one time only.

Any idea on this?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
last 2 versions do not work for alioth. something changed and broke it.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
It should be working now. Try latest
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
It works now. Thank you!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] McFlypants:
Sometimes when people calling me i have the following number on screen:

(callers number)+(my own number)

or

(callers number)&(my own number)

I can edit it afterwards with an editor i just downloaded, but when the call is incoming, i never know who calls.

This problem didn't occur with miui, so i guess it's a rom problem.

Any possibility to fix?

I'm on german o2 and use volte and vowifi. It only happens for 3 or 4 contacts i have.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] jkim204:
Hello, is it sometimes? Or most of the time? I'm worried about this too..
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] McFlypants:
It's always the same contacts. For some it happens everytime, for some never.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] damonke:
How are the numbers saved compared to the others?

+[countrycode]xxxxx

or maybe 00[cc]xxxxxxx

Maybe it's also what carrier they are on. Maybe try flashing the latest firmware (not rom just firmware) if you haven't. Might be something to do with the carrier's profiles.

Also maybe it's just the phone app? That would make it a lineage problem and nothing to do with this version specifically though.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TitaniumGom:
Not sure what is the exact cause, but there is a workaround.

There is a line [persist.vendor.radio.redir_party_num=1] in /vendor/build.prop, where you need to either delete it or set to 0. (For the record, default in MIUI is 1 actually.)

Some roms comes with this fix. Lineage OS didn't have this problem at first but now we have it. (from my experience, Arrow OS had this change applied already)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duttyend:
Hello all,

For your information, the latest ROM build is working fine for me (and no loss of root or modules in the OTA update process along with Lineage Recovery).

Security patch has been updated to January 2023. The kernel has not been updated to latest version yet (you can follow mainstream releases at www.kernel.org).

Happy new year!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] McFlypants:
I did it ans hope it's alright now. Will See it in a few days, when some of these contacts called me again.

All are saved different. Some with country Code, some without. No pattern
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] denyo81:
Is there a particular reason why you are not accepted into the Telegram group?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Smultie:
Are you talking about yourself?

(If that's the case, I think "Is there a particular reason why I am not accepted into the Telegram group?" is easier to understand)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] McFlypants:
Yesterday I flashed the newest build but went into bootloop. Strangely my other boot slot didn't work, too.

I was able to flash the last working version again und it booted up and now everything is fine, but still an older version.

Were there any major changes in the rom? Maybe magisk or one of it's modules was the problem.

I use Magisk 25.2 with these modules:

- AOSP Mods

- clear Lineage

- Zygisk LSPosed
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] denyo81:
Yes, I like to talk to myself for my life, you know? 😉
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] PsychoRS:
Hi,

Just moved to 19.1 from ArrowOS. ROM is awesome (as always), but I am suffering two minor "bugs". Poco F3 8/256GB EEA (Europe).

1) I usually set the clock to the left side of the status bar. On LOS 19.1, clock is too close to the upper left corner of the screen and doesn't look good. Is anything I can do for adding a little padding/margin on the left side of the status bar?

2) Phone isn't showing "fast charge" when plugged to the OEM adapter (showing it on MIUI and ArrowOS). It always says "slow charging" (or charging slowly, I have my phone set to spanish, I'm not sure of the correct term in english).

No root, just "standard" install (Lineage Recovery, recommended firmware following LOS Alioth wiki, MindtheGapps flashed after LOS flash and a reboot to recovery).

Thanks in advance for your great job.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RCkiller:
The charging slowly is a graphical bug. Mine has never displayed anything else, even with the original charger. The time until full is also way off. However, functionally it is fine, quickcharge works correctly and the battery is full much faster than the prediction shown.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] PsychoRS:
Thanks, so it's only a cosmetical bug. Just installed LOS yesterday and didn't have the chance of checking charging times yet.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] McFlypants:
As you are not rooted (and so no chance for magisk or xposed modules), i don't know for both questions.

But if you'd have magisk, root and xposed, you can try AOSP mods which let's you set the margin of the status bar and also let's you display extended charging information on lockscreen. So you can at least see how fast it charges in numbers.

If you want to try that, you should take AOSP Mods 2.4.1, which is compatible with 12L.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] PsychoRS:
Thanks, just installed Magisk, LSposed and AOSP mods and adjusted the padding, now my status bar clock looks mint.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Sydtek:
Whenever Im taking to someone, I accidentally press random buttons leading to mute/ hold or pressing keypad.. Does our phone has problem with proximity sensor or is my device having a problem? Any possible solution? ( I'm having latest firmware with latest los)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RCkiller:
The phone does not have a proximity sensor, it does an approximation using the microphone and the gyro, which is not ideal and far from the real sensor. Unfortunately, it is a device issue.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Parideboy:
After I tried to update to the latest version I am stuck in a bootloop. I tried to flash the rom again, but I get error code 7. I can still decrypt and access all the data, I'm doing a backup right now. Is there a way to just wipe the system partition leaving the data partition intact?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] denyo81:
They are saving at the wrong end if you ask me. I can not imagine that a renunciation of the proximity sensor brings the big savings? Well, that's probably what the masses do. But on the other hand, this is a well-known problem. From which other models also suffer. Xiaomi has already promised a remedy. But so far, apart from some empty promises, not much has happened...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] McFlypants:
This was my solution, not sure if it's the same problem. Was was able to decrypt in twrp and orangefox when i booted into it.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Parideboy:
Thanks for the reply, I ended up clean flashing the rom and restoring all the data
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] festor:
Does anyone know if upgrading 19.1 > 20 will need a clean flash/data wipe?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
It's always recommended, but you don't have to, at least that's how it was from 18.1 to 19.1.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] McFlypants:
At the moment there are no official builds so if you flash an unofficial build over an official, clean flash is really advised!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] festor:
It's just impatience on my part. I'll have some time this weekend so I was going to try 19.1 (from stock) but I should just hold out for 20.0 stable.

DT2W and haptics don't work on the 20.0 beta (not a dealbreaker for me) but it comes with V13.0.6.0.SKHMIXM firmware so I might have more issues with my EEA phone/firmware. I see that beta > stable also might require a clean flash anyway.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] barturblits:
I accidentally found the answer on the TWRP page. If you google twrp alioth you will get a different landing page for F3 than if you navigate the devices page. On the old page there is nothing about vbmeta but the new page has:

For me this was probably done by LOS at first install.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pedramtt:
hello

should I unlock first and then install payload miui 13.0.3 global

Or first payload miui13.0.3 and then unlock ?

and also when we unlock poco f3 can we lock it again if we install miui official?

thank you please help
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
This is LOS thread not MIUI. Ask in the proper section.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pedramtt:
Install miui 13.0.3.0 global with payload is the first instruction in LOS official website .

that was a simple question senior
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] McFlypants:
I once flashed a lineage update in twrp and wasn't able to boot afterwards. Reflashing the old version in lineage recovery fixed it.

Did this bootloop come from flashing in twrp?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
So, if it's the first instruction, why did you feel the need to ask if you should do it first?

This also is on the official website: "Warning: Before following these instructions please ensure that the device is currently using the firmware version mentioned below". First word in the warning is literaly "Before".
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] goshgrr:
Thank you very much for the project. I had been using 18.1 but decided to finally update. However I need to mention, the information here;

Redirecting…

-is correct for M2012K11AG. That is whats in this thread, but I didn't know to come here specifically. I tried to follow this website;

Xiaomi POCO F3 / Redmi K40 / Mi 11X (alioth) - LineageOS ROMs

Xiaomi POCO F3 / Redmi K40 / Mi 11X (alioth) Official roms Download last nightly build (2023-01-07) (mirror EU).LineageOS 19.1 – [ Android 12.1 (Snow Cone) ] [Recovery file (2023-01-07) (mirror EU)] Previous version (nightly) (2022-04-16) LineageOS 18.1 – [ Android 11.0 (Red Velvet Cake) ]...

lineageosroms.com

-where the information must be outdated, because following it leads to a FASTBOOT loop. There is no mention of vendor_boot.img or MIUI firmware, and there is no link to the lineageos.wiki page with more up to date information. Thankfully being stuck in FASTBOOT allowed me to follow the wiki page here but until then it was a scare. I have no idea how I came to that website before the official wiki guide, it was just in my bookmarks so I goofed up.

Also, could Magisk be added to the instructions? It wasn't hard to figure out by following the GitHub instructions, but I was under the impression I had to flash it through LineageOS recovery, when it only actually works if you boot back into fastboot and flash it through there
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] oirtemed:
https://wiki.lineageos.org/devices/alioth/upgrade

^ I'd suggest reading the upgrade instructions from the official wiki
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
No. This is LOS thread, magisk or any other 3rd party is NOT supported.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] maniacbb:
Is this rom support Aptx codec?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TitaniumGom:
To flash anything you need to unlock first. Even stock rom needs unlock if you are trying fastboot flashing. Locked bootloader = OTA only (via official updater app)

There still is a way to flash things with locked bootloader which is called EDL mode, but for Xiaomi devices it is not really open for public.

If you are going back to stock rom then yes you can lock it again. Just make sure you are on global device (Poco F3) not China thing (K40) since China device + Global stock rom + Locked bootloader means soft brick.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] :
Just to be sure, i need to sideload this at point 6 from this guide right?

Redirecting…

I flashed Gapps, rebooted to system, rebooted back to recovery & flashed #ih8sn.

It flashed successfully but CTS Profile match is failing.

If anyone could just tell me if #ih8sn it's still working or not I would appreciate so I don't clean flash again for nothing.

EDIT 1: I clean flashed anyways. CTS Profile match keeps failing but Netflix (Known app that doesn't work without safetynet) now shows up and installs from PlayStore... Guess it's working?

Also something i noticed is that after using ih8sn the device certified option in PlayStore just vanished xD

EDIT 2: I did a clean install and didn't applied ih8sn, after installing my bank app it triggered the safetynet issue. So i just went to lineage recovery and sideloaded ih8sn, rebooted into system, and now the app works.

So yeah, even that CTS Profile match fails, this fix safetynet.

Also something that I miss on this lineage build it's the lack of change the system color :/ By default it just picks up the wallpaper color... Hope this feature gets in next versions. I like to have it selected to a solid color only.

Thank a lot anyways for this amazing ROM! :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] guest2free:
Actually, I'm experiencing the same problem with ih8sn. All the relevant properties (ro.build.fingerprint, ro.build.version.security_patch, etc.) have the correct values that match ih8sn.conf when queried with adb shell getprop command. However, YASNAC and other older SafetyNet checkers report CTS profile failure. YASNAC displays values that match ROM security patch date and true model.

ih8sn seems to working (at least partially) since advice to relock bootloader no longer appears when ih8sn is installed.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
@althafvly I can confirm that. CTS profile match fails but ih8sn works.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
It's broken after recent changes in safetynet. So far haven't found a workaround (unrooted). Use magisk safetynet fix for now.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Smultie:
What's the link again to view behind-the-scenes Android 13 changes?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pedramtt:
battery standby issue.

last week i installed LOS 19.1 clean with no gapps

fingerprint off-modem off -sensors off- battery saver on -

found 5 percent battery usage within 7 hours.in standby

compare to Los 20 for poco x3 NFC _Surya

after 7 hours no battery change in standby

and compare to also miui 12 for poco F3 deleted all the bloatware , disabled miui optimization_ and no battery issues in standby
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Finnit0:
I have an issue with the updater app. When I klick on install and accept the popup the update app crashes. Any ideas how to fix that?

I use gcam 8.2 greatness with greatness XML unfortunately the narrowest camera does not focus it always hast a blurred picture. Any ideas?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Smultie:
19.1 development looks to be close to zero
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
LineageOS Downloads

download.lineageos.org

I wouldn't say so.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Barracuda77777:
A little truth in there, as there has not been a single commit since Feb 07, no Security patch for Feb yet usually around the tenth. Keep in mind we get all this for free, so thank you to all who contribute to this project.

btw anyone having issues with hotspotting?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] festor:
I'm sure the dev(s) will be focusing on 20. Either way, any comment (pressure) on lack of development is always a bad idea IMO.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Morghoth:
Hi, I have missing options for fingerprint. Search says they are in Gestures menu (Long press and Swipe behaviour). However, when I click on Gestures menu it has no options for fingerprint. I am on nightly 20230114.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
Have a look under "Security"!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Morghoth:
I have looked. There are no "Long press fingerprint" nor "Swipe fingerprint" options in the Security menu.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
What function do you want? Under "Security" you can set fingerprints
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
Long press on fingerprint sensor to unlock phone is the DEFAULT behaviour if you use fingerprints and you can not turn it off. Kind off pointless to be otherwise. Swipe fingerprint does not seem to be supported.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
New firmware is out for EU region: V13.0.11.0.SKHEUXM. So far everything works great.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Smultie:
Any changelog?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] festor:
You post about donating for the wrong reason (I don't believe you btw) hoping that your complaint somehow speeds up the release and you think the maintainer is the "schmuck"? smh

I often wonder if requests for quicker releases are just from trolls trying to get unpaid devs to abandon projects. Nobody could be stupid enough to believe demands from randoms would in any way motivate people who are working for free... surely? Would these requests make you work harder?

The maintainer(s) are currently working on 20 while still maintaining 19.1 with more updates than other ROMs. If you genuinely want a quicker release and not for them to step down, show some patience and maturity.

https://download.lineageos.org/devices/alioth/changes
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
I think the frustration about LOS 20 for alioth comes from the fact that much older phones from Xiaomi (2016-2017) got it already. We should not compare as every phone has a different developer or in some cases there is more than one developer. Also, keep in mind that these people do it for free and in their spare time, so show some respect.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] festor:
I think some people are missing the point. Posting your frustration or complaint will never speed things up. It's far more likely to annoy the maintainer and give them yet another reason to step down.

I don't know if it's correct, but I have seen it mentioned in the Telegram channel that they are waiting for A13 (MIUI14) to be released. The China release is out (K40) and the Global and EEA POCO F3 release is due this month. Maybe it's to fix a technical/firmware issue, maybe it's not even true, but there could be many other factors we don't know about.

Either way, don't post any complaints about not getting your free stuff fast enough, if you actually want to get your free stuff faster.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] knowledge@heart:
Look, the reason for delay is somewhat technical.

The thing is, with lineage, unlike other ROMs, they have to stick with a specific Firmware version.

If LOS 20 is relased for the device now, it will be stuck with the current MIUI 13 firmware for the entirety of LOS 20 lifespan of our device.

Even for LOS 19, you can read in wiki. The recommended firmware is way back from May 2022. Not the latest.

This is to ensure that OTA updates work smoothly and dont break some vital function of the device.

Other ROMs often require updating the firmware too occasionally, but LOS sticks with one version for life of the version.

So in short, it is better to wait for Official MIUI 14 fw to drop rather than having to being stuck with Android 12 firmware on a Android 13 ROM.

Hope this clears up things!

Cheers.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] alfix8:
That doesn't seem to be true.

When LOS 19 was released for alioth, it required 13.0.4.0 (for EEA) IIRC. Now it requires 13.0.6.0. So there was an update of the firmware version under LOS 19.

Scratch that, I misremembered. In August 2022 the wiki still said "use latest Android 12 firmware" without specifying a version, but 13.0.6.0 was the latest version back then.

However, what is the technical reason for sticking with one firmware version? Under LOS 18.1 there was usually only a minimum firmware version specified, but everything above that was fair game. The installation instructions often only specified to use the latest version of the firmware for the correct Android version.

Is it actually a technical restriction or just a lack of time to officially test newer firmwares to confirm they work?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] festor:
You incorrectly claimed that @knowledge@heart posted false info then pivoted into question that they already answered. Not needing to update the firmware as frequently (if at all) and smoother OTA updates is a good enough reason for me. It also explains why devices that are no longer receiving manufacturer updates have 20 already.

I would prefer the maintainer(s) to actually work on development or even take a well-earned break than having to explain their methods to us here. No matter what info was provided, somebody would question and challenge it anyway, just like you did.

It's a catch 22 situation. They have policies and systems in place which create a solid, desirable ROM with great support and updates yet people want them to bypass these policies and systems to speed up the release. I bet those same people are the first to complain if something goes wrong.

Let them cook!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Couchy:
You guys know crDroid is Lineage with some enhancements? I believe you can even dirty flash with it.