yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Exahope:
Much appreciated Sam for the response.

I am not sure what is the technical restraint here, but the easiest workaround I can think of is aligning it to the right since there are usually less indicators there. In the end enabling it is still optional for whomever prefers looks over functionality.

Thanks again for the great work!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] bhupatib:
Sadly I have the same issue with 2-3% per hour drain but an ok 5.5hour SOT.

Clean install 10/2 build, gapps pico, 5g disabled, always on bluetooth band+headset, no root, 5-6 apps installed and all of them in "battery restriction" mode.

I think even the stock ROM had high standby drain but I didn't monitor properly as I can't stand MIUI and switched to LOS as soon as the stupid BL lockout period got over!

Will try the latest MIUI.EU to see if it's any better...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ale82to:
hello everyone can please someone confirm if the double tap screen to wake is working for lineage unfortunately it's not working on many poco F3 room, thank you very much!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
It works for me
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] aaaa12345:
Running lineageos 18.1 with 12.5.2 firmware. I would like to update to 12.5.4, can i flash the incremental update via twrp while on lineageos, or do i need to flash the whole phone with miui and then install lineageos again?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rotblaag:
Hello People

i installed this rom

my phone now has the lineageOS recovery and Pico Opengapps

i would like to install Magisk too

i have read through this whole thread and still am a bit confused

i can rename magisk.apk to magisk.zip and then simply flash it?

"adb flash magisk.zip" ?

and the magiskmanager i already installed is not needed?

what about using slot a or b? what is that about?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] aaaa12345:
put the phone in recovery mode and choose update> side load. rename the file magisk.zip and use the command: adb sideload magisk.zip
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Paffi:
@Sahil_Sonar Thank you very much for this rom for this great mobile phone.

I am new to the f3 with los and i have the same Problem. We both have the german f3? Whats with the others who have the Problem?

I receive an incoming call, when I pick up the call I do not hear the person who is calling me. She does to me, but I to her not. I have to activate the speaker of the phone and then if I hear that person and if I then return to normal sound mode, I can already hear him.

If I call someone everthing is fine.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rotblaag:
e:footer is wrong

E: Signature verification failed

eror 21

seems something is not right..
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Veiranx:
Are you able to sideload the .apk file instead of the .zip?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rotblaag:
Of course i did not try that since that was not the instruction
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Veiranx:
Give it a try and let us know how it goes! (That is, 'adb sideload (magisk).apk')
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Paffi:
Why you do this?

Magisk how to:

Installation

The Magic Mask for Android

topjohnwu.github.io

says

Custom Recovery​

Extract the boot img from the lineage os rom.

How to:

Extract Android OTA Payload.bin File using Payload Dumper Tool

Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other important partition images.

www.thecustomdroid.com
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] aaaa12345:
When the error message appears select yes and continue the installation.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rotblaag:
thanks!!!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] thelegendaryharold:
I'm still getting random restarts especially when my phone s in motion on a car for at least 30 minutes, what could be causing the issue?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Veiranx:
Are you in North America? I've heard that it's the modem crashing and causing the phone to reset. Seems to only happen here (NA) and with AOSP-based ROMs like Lineage.

Give the Immensity Kernel a try to see if that helps.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
Make sure everyone is running this firmware :

- For all POCO F3 variants use Global (V12.5.4.0.RKHMIXM) or newer firmware.

- For MI 11X India (V12.5.5.0.RKHINXM) or newer firmware.

- For Redmi K40 China (V12.5.6.0.RKHCNXM) or newer firmware.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] bhupatib:
Is there a way to confirm whether we are on the latest firmware? Silly question perhaps but even after flashing the latest one, I see 12.5.3.0 in device info

View attachment 5436545
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] thelegendaryharold:
Make sure everyone is running this firmware :

- For all POCO F3 variants use Global (V12.5.4.0.RKHMIXM) or newer firmware.

- For MI 11X India (V12.5.5.0.RKHINXM) or newer firmware.

- For Redmi K40 China (V12.5.6.0.RKHCNXM) or newer firmware.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
Thats fingerprint prop, set in alioth lineageos build. Not your firmware version.

Miui 12.5.5.0 baseband (aliothin) : MPSS.HI.2.0.c7-00266-0908_1454_4260f48f7c
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] thelegendaryharold:
How do I know which firmware I'm running?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] thelegendaryharold:
How do I flash the kernel?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] bhupatib:
At this point, it seems the only way to know is by comparing the "Baseband" value.

For aliothin/Mi 11x with 12.5.5.0 firmware, the baseband is MPSS.HI.2.0.c7-00266-0908_1454_4260f48f7c, as confirmed by @althafvly (same as mine which means the firmware update was successful for me).

For F3 and K40 users, maybe someone can share the latest baseband string value.

But anyway, as long as you don't get an error while flashing the firmware in recovery, it seems to do the job....just no intuitive way to confirm!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] thelegendaryharold:
Thanks! I haven't encountered any errors updating so hopefully that means I don't have to worry about the firmware.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Veiranx:
Go to that thread; they should have instructions there.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kalamaius:
Can anyone tell me wich is the correct baseband value of stable global V12.5.4.0.RKHMIXM? The MPSS.HI etc... value for Poco F3 Alioth
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] damonke:
F3 here, coming from 12.5.6 EEA firmware

MPSS.HI.2.0.c7-00266-0829_1858_1e40c925ae

Interesting, this baseband is older than yours if 08/29 is a date.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] jkccl9:
im on lineage microg and im now having the call problem reported by others where i cant hear the other person speaking until i toggle loudspeaker.

was on 10/1 build, calls working fine. i updated to latest firmware and then sideloaded the 10/15 build, cleared cache and rebooted/rooted.

i had a call yesterday and it didnt work. tested it today and called myself with a second phone too. dont get enough calls to be bothered by this.

is there an auto loudspeaker when away from ear in the settings cant find one? would probably bypass the bug until you figure the root cause.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] fre42:
Thank you for this excellent ROM. It runs flawlessly!

Only the proximity sensor does not seem to work.

The display always stays on for me.

Various proximity test tools always show 5cm distance even when you put your hand on the sensor.

Has anyone been able to test this successfully yet?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] damonke:
It works for me in calls... mostly. Try to pretend to put the phone to your ear and see if the readout changes.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] thelegendaryharold:
Is anyone experiencing frequent crashes when connected to mobile data here in NA? It's been happening since I installed LOS, wondering if developers are aware of the modem crash issue and whether an update will be pushed to fix it. Thanks in advance!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] fre42:
No, unfortunately the proximity sensor does not work for me even with the most current LOS 18.1 build.

Even if I put the phone on the ear while talking. The display gets darker due to covering the light sensor, but it is not switched off.

I had the same problem with the stock MIUI firmware the device was shipped with, but after the most recent MIUI update it worked. Therefore I know that the sensor works on my device.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] damonke:
I just tried cpu info from f-droid to get sensor readouts, and it is quite finnicky. Putting my hand over it doesn't work, holding it to your face makes it hard to read the screen. Now if you hold your hand in the air (vertically as if it's the side of a head) and move the top of the phone towards it, you can get it to change. At least for me that works. The sensor only works in combination with moving it towards your head it seems, I dunno it's weird but I guess it stops it from false positives. Try playing around with it.

By the way, people say the sensor is ultrasonic, so maybe it doesn't work well for hair... But maybe it's superior to IR for dark skin... There's really no single type of sensor that is perfect for every situation.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] thelegendaryharold:
Is it possible to have dark mode on the screen when a call is being made? I turned on system-wide dark mode but this screen still displays green.

By the way if anyone's in North America and experiencing modem crashes and hard reboots, setting the preferred network type in settings to 3G/WDCMA mitigates the problem for me.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] fre42:
Thanks, @damonke! I've found that the speakers at the top are used for the ultrasonic signal. My problem was my cover which had only 6 small holes at the top frame where the speakers are placed. By enlarging these holes the ultrasonic sensor now works as expected. And you are right, the sensor only works when you hold the phone vertically.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] damonke:
I just flashed the china 12.5.14 firmware and it has this same baseband.

Weirdly though, despite not remembering flashing any firmware myself, the baseband has changed somewhere from 2-3 weeks ago when I had the baseband with '0829' in it to one with '0705' in it... Are some of these firmware files sometimes included in lineage updates?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ran94:
Wanted to know if tap to unlock (not click) with fingerprint is working in this ROM. can someone confirm? Thanks
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] clayteau:
@althafvly latest build with commits related to audio routing broke audio output from 3.5mm jack usb adapter.

https://review.lineageos.org/c/LineageOS/android_device_xiaomi_alioth/+/318289/
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] alfix8:
Can confirm this bug. When plugging in the headphones with the USB jack, sound continues to play from the phone speakers instead of the headphones.

Audio input through the headset microphone also doesn't work anymore.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mingwiki:
yes i need it badly can't wait
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Veiranx:
Are you guys updated to the most recent firmware? That fixed a lot of the problems I experienced with Arrow OS.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mingwiki:
the bug is found in the lastest version of lineage, older ones worked ok, arrowos is built based on lineage I think.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Veiranx:
It might be that the new version requires the updated firmware.

https://xdaforums.com/t/firmware-poco-f3-xiaomi-mi-11x-redmi-k40-alioth-auto-updated.4253091/

I'd recommend taking the one that applies to you (mine was Global) and sideloading it in recovery.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ale82to:
hello everyone I ve desperate need of help I really love pure lineage OS but unluckily other deeply modified room I M not able to hide /get rid of navigation bar(since I use xposed edge) , I've tried the Magisk module immersive gesture but it's not working can please someone help me.

thank you for the help
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Veiranx:
I've heard that crDroid ROM allows for non-root-based hiding of the navigation bar. It's a built in function. Consider giving that a try!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mingwiki:
I just tried, it doesnt work. am pretty sure now, It's a bug caused by 10.30 updates from lineage build.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ale82to:
hopefully I edited framework res myself and I succeeded in getting rid of nav bar
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ale82to:
does anyone know how to force enable the network traffic in status bar.

I do know is disabled because of minor graphical issue but I do know how to edit system ui to adjust padding (I ve already done it in my old mi 10 with lineage as well).

but with this lineage build for poco F3 I don't know how to enable network traffic in the firs place.

is there any adb custom setting command.

I tried su -c settings put system status_bar_show_net_traffic 1 without success, thanks for the help
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] clayteau:
Yep my firmware is updated to v12.5.5.0.RKHINXM. Usb audio is broken currently on 10/30 build.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
Although I installed the firmware via sideload without an error message, I only see an old version here.

the command was "adb sideload xxxx.zip"

Am I doing something wrong? Perhaps here is the error with the call Problems?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] rimrekizoki:
how can i get rid of the annoying black navigation bar?

i can't properly type because of it lol
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] linuxnoobbbb:
There's a magisk module called "Immersive Gestural Navigation Bar" - however I haven't tried it out, because such black bar doesn't disturb me in any way actually...

(Also I'm using gesture navigation instead of virtual navigation buttons, this can be configured in system settings -> system -> gestures -> system navigation)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] linuxnoobbbb:
Alipay fingerprint authentication isn't working - but there seems to be a confirmed (and simple?) working solution.

"setprop persist.vendor.sys.fp.vendor fpc" seems to be fix it: https://gitlab.com/LineageOS/issues/android/-/issues/4089
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] damonke:
Hi, I just updated to the latest version and while at least audio is working (I heard there were problems last week), the headset buttons are still wrongly mapped?

These are the keycodes I get with keytest.apk

189 up

79 middle

190 down

The up button seems to click on the first thing on the screen and the down button seems to function like a back button or something. Middle button works as expected. This has been an issue for a while for me, can others confirm? Maybe it's just my specific headset, but I don't think so. It worked on miui AFAIK.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] sburry:
How quick is it to open gcam, autofocus, and take a good picture? Say if your kid or cat or dog is doing something funny and you have to be fast. Is the quick snap experience on LOS + gcam good?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ale82to:
for anyone like me that was struggling to get network traffic in status bar, after two full long day I discovered that manually adding values as shown in the screnshot and then setting correct permission for setting.db(system, system, 660)will allow us to have network traffic in status bar.

file to edit :

/data/user_de/0/org.lineageos.lineagesettings/databases

screnshot :

IMG-20211108-WA0000.jpg

IMG-20211108-WA0000.jpg

drive.google.com
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ale82to:
does anyone noticed that enabling double tap to wake (without aod) often very often wakes the phone in the pocket.

the problem is that proximity sensor when screen is off is not working, covering it and double tapping still wakes the phone.

if I enable aod proximity sensor instead is working as expected :

if covered and I perform I double tap screen is not waking up.

any suggestion?

thanks
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Exahope:
Been looking for this one for a while. What app you used to modify the values. Also, is the changes persistent.

Much appreciated!!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ale82to:
just use any sql editor and don't forget to set right permission for the file (i user mixplorer /sql editor)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] vander13:
Anyone got Magisk working?

Iexport the boot.img, patched and flashed by fastboot, all successful. Still nothing, app keeps showing "installed N/A" :(

EDIT: since the nightly 20211113, streaming finds my TV and works flawlessly :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Exahope:
Much appreciated, I did mange to activate it, but it 's under the notch. Any luck patching that?

I found several patches in Github for devices with similar issue, not sure why it's not applied for this device though.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Exahope:
I just flashed magisk.apk in fastboot and all is fine.. I even update my lineageos without losing magisk root.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ale82to:
actually it's super easy to fix I did not understand why the developer of the room did not do it in the first place.

having said that u must edit, decompile system ui with apktool and edit status_bar.xml (screenshot : https://drive.google.com/file/d/12IvbMgbbfgLH1vF-N-waD4XwR2LRWvDN/view) under layout and add padding right.

but before doing this u must patch android and disable signature verification otherwise system is not gonna band also replacing system ui is not that intuitive (I got several bootloop before finding right way:u must use mixplorer open at syyemu ui app folder execute command cp path to modded system ui / /system_ext/priv-app/SystemUI/SystemUI.apk)

it s overwhelming and I strongly suggest to take a twrp backup before succeeding I got several bootloop myself.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Exahope:
TBH, was planning to do that since I've read some guides, but it's too much hustle for me since I need the phone to be functional all the time and it seems I am gonna lose the luxury of OTA updates if i did that (not sure about this part tho).

So I am gonna wait for a bit for it, hopefully the rom devs do the copy pasting from GitHub asap :P

Thanks man for the help, really much appreciated!!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
With today's update, the problem seems to have been resolved.

I will continue to do tests tomorrow, currently it works.

Otherwise, can one of you who also had this bug find out whether the bug is gone?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] vander13:
I had to uninstall the APK and reinstall by ADB, than it worked.

Now I run into another problem. I tried SnoopSnitch an it seems beside root it also needs a kernel function (DIAG_CHAR) that's not available. Any idea how to achieve this?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] anggatelorendog:
how to gesture screen capture ?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Exahope:
checking their page they stated the following.

Unsupported. Devices with custom ROM such as CyanogenMod which lacks the Qualcomm DIAG kernel driver (DIAG_CHAR)

So i guess nothing can be done here, unless there is some kind of dirty workaround.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
Which option would you prefer in LineageOS?

1- 60,90 and 120Hz list for refresh rate (default right now)

does not change refresh rate depending on content. refresh rate will be

set to a constant value

2- 60-120Hz smooth display (changing refresh rate depending on content)

this one requires some sacrifice,

- Need to remove 90Hz. its not color calibrated properly so using with smooth display will give flicker when switching between 60-90-120Hz.

- Theres was a flickering when switching between 60-120 in low brightness. In order to avoid that we had set 60-120 auto switch only above 40% brightness. below 40% it will be 60Hz or 120Hz ,depending on smooth display on or off.

QA:

1. Why does it flicker in the first place?

ans: The display uses different gamma curves for different refresh rates. It's hard for panel vendor to tune the curves to have exact same brightness for different refresh rate. So flicker could be observed at switch time. The issue is worse at the gamma lower end. In addition, human eyes are more sensitive to the flicker at darker environment. To prevent flicker, we only support higher refresh rates if the display brightness is above a threshold. And the darker environment could have higher threshold. source

2. Why we need to remove 90Hz ?

ans: Display gamma curves are entirely different compared to 60 and 120 even in low/high brightness. Xiaomi doesn't use it properly in miui builds, only 60-120Hz officially available, 90Hz is hidden from normal user, can only activate this via command line or some hacks. i have only seen 90Hz used in recents menu in miui.You guys might have noticed a color shift in this menu.

EDIT: There won't be any changes regarding this. Will continue using current one.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] metalspider:
been using my new 5G connection with usb tether but in lineage it seems to go down to H+ pretty fast,in xiaomi eu and in the stock global firmware there's an option in battery saver called "5G battery saver". disabling it helped me stay on 5g for longer but i was also suspecting my cell carrier want too happy even though i paid for a big data plan.

in lineage i could force back to 5g in the preferred networks setting but i need hspa/3.5g for phone calls since volte is not enabled on my carrier.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] damonke:
For me personally, sacrificing 90Hz (which might be a nice balance between battery and smoothness) is not worth it if this 'hacky' implementation of adaptive refreshrate won't work below 40%, which I think is at least half of my usage of the phone. Actually, the brighter the environment, the less I'd care about this stuff probably (like, I would be using google maps quickly or taking a quick picture).

Then again, this is just some of my thoughts, I don't currently use any high refreshrates. In theory an automatic mode would sound attractive too though. Am I correct in assuming this would switch to 60 in case you're looking at something static? Because then maybe you just get the best of both worlds and I kind of feel that that might be a more useful option than 90 constant... if it works well that is. Does MIUI have the same thing under 40% btw?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AudioSculpt:
LOS means freedom: so, why not booth?

Anyway i personally prefer the first set-up.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] :
Hi everyone, POCO F3 (LATAM) user here sharing my experience.

In order to install the ROM, I followed these steps:

- Updated device to MIUI 12.5.4 (lastest OTA recieved at least here).

- Unlocked bootloader.

- Flashed Lineage OS using LOS temporary recovery, by ADB side-loading the package.

- Flashed OpenGapps Micro (the only one that fitted system partition).

Issues so far after a week of usage:

- Random reboots while the phone is inside my pocket or inside my car while using maps. For this one I tried changing some live display settings (read about it in comments) and so far I had no more reboots.

Questions:

- I've read that a 12.5.4 based firmware is required for this ROM. Looking into this guide, i read:

So it's not entirely clear if this ROM actually has the drivers it requires or not and wether people should do the update. Can anyone clarify?

Thanks for the ROM to all the developers.

edit 19 Nov 2021: crashes are still happening while driving (phone connected to a car with BT).