yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] alfix8:
Neither. I've also reinstalled the correct firmware multiple times.

Everything I've tried so far (and what althafvly suggested) can be seen in the corresponding bug report: https://gitlab.com/LineageOS/issues/android/-/issues/5951

So far there seems to be no real solution though unfortunately.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
I'm testing now to see if that was actually needed or not. I threw Google Search Box and the Google Assistant activation services into the deny list and cleared the data for the Google Search Box app and the option became available as it should. Taking that stuff back out of the deny list now.

Also the restricted settings for side loaded apps can be bypassed by going to Settings -> App -> Select the sideloaded app and hit the 3 dot menu, then allow restricted settings. That one was new to me since MIUI didn't have it. Everything seems to be working 100% now. Big thanks to the Lineage devs and those in this thread providing feedback.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] @oracle_345:
There's a bug that's been bothering me using this ROM. While I'm charging the lockscreen charge indicator says Charging slowly while in fact the battery is charging on it's normal speed using the factory provided charger. It's been like this for a while. Why does the developers don't address this issue?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Smultie:
Why does it bother you soooo much if you know the device is charging at its normal speed. Devs are volunteers with a life of their own.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
Unplug it and plug it back in again if it bothers you so much. The second time it will show charging rapidly.

The only real bug I've found in this rom is a minor annoyance (and Google's problem really). When I use Hey/Ok Google it'll show the blue "Unlock More Assistant Actions" button permanently above the listening window. The first time it showed up, it ran the wizard correctly and let me enable the feature, but the icon stays and subsequent taps of it just close the intent instead of launching the wizard. Just a minor visual annoyance. So I'd say this rom is in pretty damn good shape.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Lex_Michdeandroid:
Is anyone else experiencing random reboots/complete shutdowns? Started happening 1,5 week ago, I updated to the latest (July 30th) and it still happened...

Phone has been working fine for months, so it's not because of a new install.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Boracho:
Not at all, maybe try to reflash the Firmware.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] @oracle_345:
I've been experiencing this for a month and I've tried what you've said above and also tried recalibrating the battery but it didn't worked.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] @oracle_345:
Well, it's been a month of constant misreading how are you not bothered?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] @oracle_345:
Google services works fine if you used the recommended gapp pack by lineage. Hey, Google works fine on my case.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
I used the recommended mindthegapps and it functions fine -- it just has the visual annoyance of showing the "Unlock more assistant actions" button showing all the time even though the additional actions are already enabled, like I said.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] @oracle_345:
Perhaps you can remove your google account temporarily then clear google play services data, google play store data, and the google app data. Reboot your phone then sign in again. Hope this works...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
Oh no I didn't try that before reporting the issue. /s 🙄

*Looks at my account age and post count* 🤦‍♂️
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] @oracle_345:
Just trying to help. If you assumed my good intention differently it's not my problem anymore.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duttyend:
Just a quick message to report the update from today is working perfectly (on my side) and the phone feels even snappier.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] JevonsDU:
Much appreciated devs' great work, the latest update has fixed file upload issue in Jelly browser!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
I think the final solution would be if developer port 14.0.7.0 firmware and binary blobs, similar to that https://review.lineageos.org/c/LineageOS/android_device_xiaomi_alioth/+/354275

For me 14.0.4.0 was unstable, 14.0.7.0 is rock solid
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
Latest build is rock solid. Good job devs. (I'm also using the 14.0.7.0 global firmware blobs)

You could always just flash the updated binary blobs from xiaomifirmwareupdater or use the factory image and adb or miflash to reset the device back to stock w/o locking the bootloader prior to installing LOS20. That's what I did before updating from MIUI.EU 14. Saves having to update every single firmware file manually from the command line one by one. You could even just temp boot the SKKK twrp to flash the firmware blobs if it doesn't work through LOS recovery -- though don't update the rom itself using TWRP if you have Gapps on an already installed build of LOS20, because it won't back up everything for Mindthegapps if installed that way (as noted in the wiki). I did the initial install using TWRP and it works fine but it was temp booted so LOS recovery still exists in my boot.img partitions for OTA purposes.

Work smarter, not harder.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] JevonsDU:
I am using 14.0.7 , very stable , although the instructions say, need 14.0.4 firmware
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
Unfortunately documentation is something that is usually poorly maintained in a lot of open source projects. It's no different than when twrp.me had incorrect instructions posted (and probably still do) for installing TWRP on a Poco F3, even though I submitted the corrections formatted so that they could copy and paste them to the wiki in place of what was already there. I wonder how many folks ended up in a bootloop as a result and then couldn't figure out why... Testers should maintain documentation; not the devs themselves. The developers already have enough to worry about.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Smultie:
Any factual data to support the claim that 14.0.7 is stabler?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
I've been on 14.0.7.0 global for the past couple of builds and have had zero crashes, reboots, instability problems, bluetooth/wifi/network issues etc. I had issues with B7 connectivity on all firmware blobs prior to this (China/EEA/Global), even on MIUI 13 and 14.

If 14.0.4.0 works fine for you, then there is likely no reason to change, but 14.0.7.0 isn't going to hurt anything either.

Specifically 14.0.7.0 it is what the Wiki recommends for EEA region users anyway. The versions listed were just what was official for the different regions when the wiki was written, and it hasn't been updated in a while.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Smultie:
EEA always needed 14.0.7, right? At least, that's what https://wiki.lineageos.org/devices/alioth/fw_update/variant1 says at this moment.

Guess I've always been running 14.0.7 then.... guess that explains my lack of problems (even since the sudden reboots were fixed)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Lex_Michdeandroid:
I'm on 14.0.7.0. I don't think it's firmware related.

The phone freezes and I can only hold the power button for 10s so it reboots again.

What terminal app are you using to see 'dmesg'? It happened a few times in a row now... I would like to find out why.

-edit- Well, I guess the phone is dead... Doesn't turn on anymore, does absolutely nothing. Pried off the back and disconnected the battery, connected it again, still dead. I guess Xiaomi is not the quality I am looking for, my first and definitely my last Xiaomi. Now I need a long and hard thinking session on how to get my important stuff fixed while I'm 10.000kms from home... Please wish me luck, because I really could use some...

-edit- Found this on Reddit. Man I start to hate this brand with a passion. Of course you're going to get annoyed with me ranting about Xiaomi, but how is this possible?! Are there really so many people with Xiaomi phones that just die? Absolute... rubbish quality brand.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Smultie:
On the topic of 'Hey Google'. Has anyone else been able to get 'Hey Google' working with the screen off?

It has been working for me in the past, but I can't get it working for the last weeks.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
Your mileage may vary with any brand. I had two Redmi Note 5 Pros for 4 years -- the flash memory started going bad on one near the end of that time (it was only a 3gb/32gb model being written over and over), the 4gb/64gb model was fine and is still being used by a friend of mine to this very day over 5 years later. The two Poco F3s I've had for a year and a half have been flawless. Hardware failures can happen with any brand. I have dozens of friends that have had issues with Apple, Samsung and Google phones as well, and I'm sure you do too. Plus they cost multiple times what the main stream Xiaomi models do. 🤷‍♂️
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Lex_Michdeandroid:
You guys enjoy your Xiaomi's, but make sure you do backups a lot. I'm not coming back to Xiaomi, take care and thanks for holding my hand through this experiment. I've learned a lesson, that's also worth something. Xxx
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duttyend:
Buddy, before leaving, it might be worth trying a few last things: try with charger plugged in to discard battery problem/wear, open the device and check the basics (battery connection, burned component, water oxidation, etc.)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Lex_Michdeandroid:
I already disconnected/reconnected the battery (took the phone apart yes) and got 0 reaction from the device. I don't have more tools with me, so I can't dig deeper now.

When I get back home I'll try to find out where fault lies, maybe even find out what board or chip blew, but for now my journey ends. I'm very lucky I brought my 5T and I can have my internet lifeline working again. I'm wandering around Tokyo right now, trying to compensate the loss of pictures and videos...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Held der Arbeit:
Can I flash Gapps with TWRP?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] maniacbb:
Restarts occur with me all the time I had POCO F3 EEA V14.0.7.0.TKHEUXM and

POCO F3 Global V14.0.4.0.TKHMIXM restarts occurred after two days. I have an important question if people who do not have these reboots after typing this command

fastboot getvar all

does it appear to you

in the results what bootloder you have? Or is it always a blank field?

(bootloader) version-baseband: here it is empty
(bootloader) version-bootloader: here it is also empty
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] MikiVanousek:
I can confirm. Flashing 14.0.7 fixed weird issues I had all over the place, Google Maps, mostly.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
Also empty here.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Boracho:
How do you guys recommend to handle backups, so data can be recovered and probably restored on another phone in case of loss or destruction?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Barracuda77777:
I use a syncthing server to backup all my data, downloads, camera and so on, I also schedule app backup nightly to a synced folder, so whatever happens to my phone I never lose a single byte.

have been using this setup for years.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AudioSculpt:
Great Room.

I'm just here to share my experience: i'm using it with HSM Core instead of Google Play Services: i though that was a good idea since i've just bought a Huawei Watch 4 Pro and i was in a good mood to try some sort of "huawei experience".

Anyway everything works fine, except for one thing: Curve.

With the "app gallery" version i should use Curve as a Pyament app (like Google Pay) but every time i try to activate it, it get stuck in a boot animation with the message "we're activating your nfc" (the nfc is activated of course).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Boracho:
I never used this app, but this could be caused by failing safetynet. Use an attestation tool like yasnac to validate your status. Also, you might want to put the app onto the deny list in case your device is rooted.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AudioSculpt:
Hi Boracho,

That's what i thought.

Device wasn't rooted: didn't worked.

Then i installed ih8sn: didn't worked.

Then i rooted: didn't worked either.

Safetynet pass with basic evalutaion.

Installed Play Services: Google Wallet works like a charm but Curve still doesn't work.

Anyway, i've learned something with this experiment: you can easily live without Play Services.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
Deny list may not be enough. I have a few apps that require Shamiko in order to not detect root, and SafetyNetFix-Mod to actually pass safetynet, but I'm not sure the latter will apply to your setup as you're not using the official play services. Worth a try though. (ih8sn didn't work for me when I wasn't rooted either).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AudioSculpt:
Hi mik101,

Before this experiment i was unrooted, with Play Services and modded ih8sn that i've found here and Google Wallet and Pay through NFC works perfectly.

I don't know: i'm start thinking that is related to some HSM Core plugins that Curve needs to work.

When you install HSM Core from App Gallery its just a baseline of service: whenever you install another app that works with HSM, there's a check if HSM Core have all the...let's coll them "dependecies" to work with. If not, HSM Core perform a download of the specific software addon it need to communicate with the app.

My poin is that Curve pay miss something from HSM Core that are specific for Huawei smartphones.

That's pretty absurd from my pov since AppGallery is just an alternative store, not something closed to Huawei devices.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
Edit: ADB/Verify packages was turned off in developer settings. Previous builds -- reflashing it worked without that enabled. I guess now it doesn't. Disabled it again after installing and so far so good. Todays build is a go.

Edit 2: Has anyone tested if Magisk's addon.d script runs after an OTA without doing the post OTA reflash in the Magisk app? I'm going to guess no since we're using Lineage Recovery instead of TWRP, but just curious is anyone has tried.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duttyend:
I cannot confirm. On my side, Magisk remained installed and today's build is working very well.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
Do you do the Post OTA reflash in Magisk Manager or just rely on the addon.d script to leave Magisk installed?

It was weird that it wouldn't stay installed. Usually it works fine. Seems okay now. Build is good for far.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duttyend:
I rely on the addon.d script and everything stays in place perfectly (Magisk, root, modules, GApps)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
Perfect. I'll give that a try next week. I have just been doing the Install to Inactive Slot (After OTA) in Magisk Manager because I kept finding conflicting information from older Lineage versions on whether it was working consistently on A/B devices. It always worked properly on my single slot Redmi Note 5 Pro. I should have switched the F3 to LOS from .EU a lot sooner. It fixed a lot of annoying issues like the Compass in Google Maps, and my Galaxy Watch 3 disconnecting all of the time.

Thanks for confirming that the addon.d script is working.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mik101:
If anyone happens to be on Public Mobile in Canada and have trouble sending MMS messages, the built in APN settings in the rom are incorrect/outdated and seem to have proliferated all over the internet, so most roms have the wrong ones included.

These are correct:

MMS proxy: mmscproxy.mobility.ca

MMS port: 8799

The included ones that didn't work for me:

MMS proxy: 74.49.0.18

MMS port: 80

Other entries are the same, since Koodo and Public are both just Telus MVNOs.

I should have run into that issue long before now, but I rarely use MMS -- and neither should you. :ROFLMAO: Once in a while you'll find someone who doesn't have RCS turned on.

Edit: Yeah they changed the IP again -- that URL used to point to that IP but now it points to their other MMS server (209.202.119.4). So the rom should have the IP address swapped out for the URL so it can be dynamic. Port doesn't really matter, either 80 or 8799 should work, but they seem to recommend the latter on Telus/Koodo/PM support sites.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] liquidRick:
Hello there,

I flash my phone to this firmware POCO F3 EEA - V14.0.7.0.TKHEUXM

Then tried to "fastboot boot twrp-3.7.0_12-0-alioth.img" and it rebooted to the TWRP

But it failed to mount the partitions:

'/system_root' (Invalid argument)

'/vendor' (Invalid argument)

Could anyone give me a tip?

EDIT: I have missed this part:

fastboot flash boot boot.img
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] vaneno:
I don't know, i use the original lineage recovery since 2020 in all devices that i flashed.

I have a question... My f3 with a clean install allways reboot after finish the first start assitent.

When i stay on desk after finish boot, and see the "trust notification" i beguining to configure some thins , like sounds, buttons... Etc and its freeze and reboots. After boot, i can use normally, but i want to check logs or get info, why this produce. Today was reboot without sim, only wifi (a 5g wifi).

My instalation come from stock rom its:

-unlock

-flash boot partition

-flash lineage recovey

-format data

-flash sideload lineageos

-reboot to recovery

-flash nikgapss (t release)

-flash h8 patch

Init the phone.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Soupape50:
Hey guys,

First of all, thank you all so much for the work you're all putting in this community.

I'm encountering the SIM card reboot bug with my new (second hand) F3. After a while, the network disconnects, then the phone restarts, doesn't show any network setting and I need to reboot again for everything to work.

So from what I've read on this forum, the solution is to flash the right firmware before flashing LOS? I'm not new to flashing ROMs, but I don't really understand the concept of flashing a firmware beforehand.

So I need to check if my phone is a Global or EEA version using my IMEI, then flash the right firmware, then reflash LOS (no way of fixing this without losing my data, right?)

So can someone confirm that this famous bug is fixed by doing this, and that it's the correct way of doing it?

Thanks!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] maniacbb:
Uploading the right firmware is key. Simply uploading a firmware will not remove your data from the phone. It's worth doing it with these instructions

https://wiki.lineageos.org/devices/alioth/fw_update/variant1

I personally having downloaded a newer version of Global. The lineageos website recommends V14.0.4.0.TKHMIXM. In my case, the network continued to disappear and reboots occurred. However, after uploading V14.0.7.0.TKHMIXM, everything works very well. No reboots and network outages. You'll have to see what works for you.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] sxaaa:
I have the same problem with 14.0.4.0 global and 14.0.7.0 global (I'm encountering the SIM card reboot bug with my F3. After a while, the network disconnects, then the phone restarts, doesn't show any network setting and I need to reboot again for everything to work.)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Chinmoy_mi_11x:
Jio 5G not supported!

checked NR availability by dailing *#*#4636#*#*

it says NR availibility unknown...

I did have jio 5G in stock ROM MIUI 14

Device: MI 11X
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] garconblair:
Have you tried to change preferred network type in settings? This happened to me after the instal, the preferred netwotk type was set to: LTE, TD-SCDMA , CDMA,... I changed it to : WORLD and the 5G appeared immediately.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duttyend:
You mean 'Global' and not World?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] garconblair:
Yes, you're right. My phone is in Spanish, i have "Mundial" as an option in preferred network type, so I thought that World would be the english word for that.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Chinmoy_mi_11x:
I already changed ROM to miui 14 for the 5G.

Will Re-flash Lineage os To see if it works
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] uradryct:
did you solve it?

Im experience a similar problem with other roms
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] dmahtani:
On LOS19, I am able to turn my two SIMs on and off (disable individually). Is this possible in LOS20?

If someone could let me know, as I don't want to upgrade if this feature has been removed.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Smultie:
Yes, still possible in LOS20
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ran94:
Hi,

I'm running LineageOS Android 11 version. Can I directly install latest Android 13 version directly without Android 12? Are there any files I need for doing it? Thanks for your time :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
Nobody will have tried that. But you can follow the upgrade instructions on LOS and hope that this version jump works without any problems.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] der_Kief:
@All is fast charging working for anyone ?

For me even with the original Poco F3 charger max. 15W is possible.

With MIUI I'm able to charge with 33W.

All measurements were done with a USB mutlimeter.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] vaneno:
I think its working, because i note when i use the standar charger (15w) or the orginal , its more fast with original. But im not sure.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] vaneno:
I have a dude with this rom (and see too with PE). Some times , my screen remains on. I have 30 seconds to turn off, but sometimes (and i don't use especial software) its happen. Its possible to analyze myselft to find the problem? In battery use , i dont find any app drainning. And a lot of times i get 7-8 hours of screen , so , its not drainning problem. (Sorry my english :) )
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] jlynch1982:
I also have issues with reboots on the global 14.0.7.0 firmware. Today a new global firmware 14.0.8.0 (see here) was released, lets see how this one works.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] xolito727:
I have the same issue. Its totally random
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Soupape50:
I also still have the issue (international Poco F3), despite updating from 14.0.4.0 to 14.0.7.0. Will try the new 14.0.8.0 and let you guys know if this fixes it.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] jlynch1982:
Its still the same for me on 14.0.8.0, still suffering from the reboots
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] xolito727:
I only have a reboot once a month and usually happens when i have 2 sim cards.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Boracho:
I'm on 14.0.4 and haven't experienced any reboots at all. Maybe its worth for you trying going back to the officially supported 14.0.4 and upgrade your lineage to the latest version. Maybe the new firmware is introducing different causes for the rebots now, and the original issue was solved in the lineage code in the meanwhile.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] xolito727:
Latest and greatest gang hates your suggestion
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] liquidRick:
I've been using this ROM daily in the last month.It works fine. I experienced a reboot in the first 5 minutes after flashing the ROM, never happened again.

Hope you guys keep improving LineageOS.