yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] silveraero:
Why do people want to use 60Hz? As I experienced, the battery usage with 120Hz screen is OK for me. I usually get 9 hours and sometimes up to 12 hours with browsing, reading, gaming, youtube, facebook ... Of course with wifi only. I guess there should be no reason to use the 60Hz mode.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CrazyRoux:
What do you mean underlying issue? Can you explain to me?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CrazyRoux:
I didn't care about 120hz at all. I prefer battery backup. And i play mobile legend but it doesn't support 120fps.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] silveraero:
I guess 2 days usage with average 10 hours screen on is not enough for you. If you play games and they are not supported 120hz, well that's ok.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Fuechslein:
The phone never goes down to 60Hz even when you set it in settings. It's seems locked on 120Hz. Turning on battery saver is just a band-aid solution.

When you are reading something for example or watching at a picture or literally anything where the screen is static, you do not need 120 refreshes per second. It doesn't give you any better visual quality, it's just unnecessary battery usage. Btw, stock MIUI ROM adjusts refreshrate dynamically, even when you set it to 120Hz.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
That's not quite true. With Google Maps I only have 60Hz!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Sahil_Sonar:
camera and incall ui too xD
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Sahil_Sonar:
You can enable a battery saver. Anyways will look into it soon
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] MrPhilo:
Will there be two options like in some other ROMs? Max and minimun hz? Or will it remain has one hz option only
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] billy_overheat:
Weird, I rooted the phone and it seems like I've lost 120hz. Does anyone experience this
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] fonzserge18:
Anybody using this ROM also playing CODM? Can i ask for the experience nor can i ask for the screenshot of codm on the start menu. Thanks
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
I have a problem with the Google Dialer that I cannot hear the caller when I call. Only after hanging up and calling again do I hear the person. But I am always heard.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] aaaa12345:
NGcam 8.1 version 1.3

About NGCam 8.1

NGCam 8.1 changelog

ngcam.xyz

Use the config attached to enjoy all three cameras.

Credit for the xml:

Telegram User: @Fuzailkhanazmi

Published here:

NGCam | XML

NGCam | Google Camera modification	▫️Channel: @ngcamchat	▫️Chat: @ngcamchat	▫️Donate: telegra.ph/Donations-06-08	Share XML - @ngcam_contact_bot	Use #pinned and hashtags

t.me
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] danashcroft:
Getting issues with location based apps like Google maps and uber. Tried using a reset GPS app but no success
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Sahil_Sonar:
This happens on some specific gapps
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] danashcroft:
Which gapps is best, tried opengapps and mindthegapps
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
I took the Pico version of Open GApps and everything works.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] danashcroft:
Fixed this issue with a fresh install and using Niki gapps core
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
OpenGApps is the only one officially supported by lineageos and updated constantly. I recommend the pico package
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
That's not true, see link.

Redirecting…
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] vanjimber:
Hi there. Doesn't work incoming call ringer

sound when bluetooth headphones connected, just silence in bt headphones and even on phone. With wired headphones works fine.

Just clean install + opengapps pico without any mods. Can somebody check?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] danashcroft:
Nearly there with this, know the official stance on safetynet but is there any way of passing it? Tried everything including the magisk modules
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] vanjimber:
Try to install magisk module MagiskHide Props Config and follow

https://xdaforums.com/t/rom-official-alioth-aliothin-11-lineageos-18-1.4313085/post-85451291
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] danashcroft:
Perfect worked! Well gpay isn't working but I'll figure it out
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
How is that not true? It is supported officialy and it gets constant updates. MindTheGapps is suported officialy but curent version is from april. How is that not true?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] keyoke87:
Install magisk, and use magisk hide with magisk hide props
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
That is not true. MindTheGapps is officially supported, see my link.

It doesn't matter when the last version is, you wrote that OpenGApps is the only version that is officially supported.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
You have reading issues. Only one officialy supported AND updated constantly. Try to read the whole sentence before making statements.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
Looks like tomorrow's build will fix the 'stuck at 120hz all time' issue.

https://review.lineageos.org/c/LineageOS/android_device_xiaomi_alioth/+/314738/
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] danashcroft:
Got an issue, every time I make a call or doesn't show the screen to hang up, mute etc end up having to restart the phone to hang up!

Fixed this, turns out the phone app wasn't set to default app for calls, doing this brought back the call screen when making calls
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Seb_Lz:
Has anyone managed to get voice match (hey google) feature working ? The option is greyed out in Google => Voice settings for me.

My install: clean LOS -> NikGapps-core -> Magisk 23 -> MagiskHide Props Config -> install google & google assistant from playstore -> install NikGapps Velvet addon.

Also, trying to install NikGapps Full gives an error about missing storage space.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
Maybe you should ask in the nikgapps or the magisk thread because neither is supported by LOS.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Seb_Lz:
I'm totally fine using another gapps, I was just describing what my current setup was in case it would have an influence on voice match. If someone else managed to have voice match working on this LOS rom, I'd be interested to know what his setup is (which gapps, which settings).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Jayelar:
Idle drain is terrible in current build. Slept at 80%, woke up at 25% battery. AOD is on.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CHGICEMAN:
That is very bad for you indeed! Take a look which app sucks the battery. I lost about 5% battery over night, which is also high but still works.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] vanjimber:
Installed version 18.1-20210814. Sound of incoming call ringer does not work when bluetooth headphones are connected. Silence in the headphones and on the phone. Clean install + opengapps pico.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ajsmsg78:
Whenever this happens I just take the velvet folder I saved and move it into system/priv-app. Then voice match will work. If it's missing in system it won't work even if you installed it from the Play Store. Here's a link to it if you need it.

https://drive.google.com/folderview?id=1eDPr5MPglqlkrFmGGaTbu763ixeCVH85
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] billy_overheat:
Deleted.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Fuechslein:
Seems like the refresh rate issue is still not fully solved. The selection of min refresh rate in the settings is now respected, but is applied as permanent refresh rate.

I could successfully build my own LoS build and reverted the changes from https://review.lineageos.org/c/LineageOS/android_device_xiaomi_alioth/+/314738 and https://review.lineageos.org/c/LineageOS/android_device_xiaomi_alioth/+/314463 but commented out

ro.surface_flinger.use_content_detection_for_refresh_rate=true

Dynamic refresh rate is properly working:

- goes to minimum refresh rate defined in settings when there is a static image and no touch input

- goes to 120Hz when something onscreen is refreshed

- goes to 120Hz when touch input is registered

- goes to 120Hz when device is woken up

Setting minimum refresh rate to 120Hz translates to permanent 120Hz like this.

Pretty much all that is needed in my eyes now, would be a setting for maximum refresh rate which then applies to Settings.System.PEAK_REFRESH_RATE so we could set the maximum frame rate instead of the hardcoded 120Hz. (Removing minimum refresh rate setting altogether and replacing it with maximum refresh rate instead would make it closest to how it works in stock miui)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] bricky23:
Same here. If my smart watch didn't vibrate, I wouldn't even know that someone was calling.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Doronmak:
Great ROM, there's a face unlock module?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Seb_Lz:
Thanks for your tip. I managed to get it working simply by uninstalling google update, then clearing data of google and assistant apps. Once it was working, I could update google again and it kept working.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rstment ^m^:
But stock miui refresh rate is horrendous... Whole reason why I'm now looking to go with aosp....

Don't advocate for refresh rate dropping after only few seconds of not touching the screen - you cannot even imagine how horrible it is when the game is dropping frames unless you're constantly touching the screen. Those drops from 120 fps to 60 fps cause immense jerks in performance... Just look at how going from 120 fps to 90 fps in recent apps feels jittery as fucck. Going 120 fps to 60 fps is just a murderous amount of performance jerk.

Honestly I have no idea how the adaptive display works in lineage now but as long as you can force it on 120 fps I'll be happy. Current implementation of "adaptive refresh rate" is ridiculous. It's not adaptive at all , all it does is force other apps to use lower refresh rate... Untill display can truly adapt in the means of rendering at 60 , 59 , 58 , 57 Hz depending on how much fps the game or app is rendering at I don't wanna see any of this. All of these refresh rate switches are so barbaric that I'd rather just use 120hz all the time

I can't believe there are people out there forcing themselves to use 60/90 fps for the sake of 10/20 mins longer battery if even that...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] 21071992:
Same. I want 120Hz all the time and don't care about little battery saved when using lower than 120Hz. After using 120Hz, 60Hz feels very laggy and slow and annoying, watching video does not consume much power so I don't feel any different if refresh rate reduce to 60Hz or stay at 120Hz when watching video.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ewertonbruno:
I installed the last update and since then I have problems using the EggNS app. When accessing the settings, trying to access F3 folders (in this case to find games etc) and with the proper authorization to access directories, the app lock and close, which was not happening in first version of LineageOS, where all apps were working and accessing folders normally. Any solution?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rstment ^m^:
Flash everything all over again following the procedure , when you are done flashing everything excepts gapps go back to main menu and reboot to boot loader. Type in fastboot boot in your cmd and drag and drop twrp by nebrassy into cmd. Hit enter and phone boots into twrp , there go to advanced and apply update via adb , then just type in cmd adb sideload drag and drop whatever gapps you want ( I used open gapps ) and it shouldn't complain at all about insufficient space
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rstment ^m^:
Overall great ROM but there is touch polling issues... I'm moving to something else until it gets fixed. If you move your finger fast you might not notice it but if you place your finger on the screen and slowly and consistently try scrolling down you notice that scrolling stutters , it's full with micro stops and jerks.... ( I did this "feel" test on this XDA page with brave browser installed. It's hard to spot elsewhere... I was having doubts because of this very thing at first thinking maybe xda webpage is **** but after seeing touch polling at 340hz via adb and feeling bit off overall but can't quite point it out how on everything else while moving around phone , keyboard I'm convinced ) That's something arrow OS dev noticed and fixed literally days after releasing his touch poll increase toggle inside settings , if you guys are following their train of thoughts look into what they fixed because touch ain't alright at all.

OS feels smooth as **** it's a real shame...

Recovery is broken as well , is not able to install gapps after flashing ROM. I had to reboot into twrp to install gapps because it keeps reporting insufficient space even on the pico gapps...

And let's not forget jagged edges around the notch and all around display edges !!! This shet really needs to go....

Hopefully within a couple updates this stuff gets fixed :\ One can dream.

I did adb shell get event -r -t -l and it reports touch refresh rate as 340hz and around that. With it hitting 360hz very very rarely and as a peak... On arrow with quantic kernel it reports usually around 380hz with peaks going into insane ranges ( Those peaks usually don't matter as it happens when touch is too short and it over reports it as something as insane and 500-2000 hz touch polling ) I didn't bother to calculate avg touch polling as it doesn't even matter what it says it is when touch feels really bad... While I'm here might as well try Quantic Kernel and see if it fixes touch if not I'm out...

After Quantic : touch feels less jittery but still feels like it's not quite there.... Adb shell command from above reports much better touch polling at 360hz some relative minimum and peaks hanging around 370/380hz just like what I would expect.

But performance is somehow worse... I use GPU mark to test GPU performance and its way below what this device can do. On stock arrow score is 1.85 mil , on stock lineage it's 1.71 mil , on arrow with Quantic it goes up to 2.15mil , on lineage with Quantic it drops below 1.71 mil =\

Overall I had relatively low expectations for Quantic , it offers worse touch feeling than arrow stock but is still better than lineage is stock so if some of you are stuck on lineage might as well try Quantic I guess...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] MrPhilo:
This does not make sense for people who watch videos. 120hz is not needed for them, not everything revolves around playing games.

Either way the dev has made changes to the hz system yesterday anyways which should show up on next update.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rstment ^m^:
Nah man , even when app renders at 60 fps it does feel smoother to have the display refresh at 120hz... If you have time do read up on it , there should be studies online saying that higher display refresh rate is always welcome even when apps render at lower fps - you get those frames to show up sooner iirc. Either way I moved on from this ROM so I don't wanna argue
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] MrPhilo:
Please stop spouting incorrect information. A 24/30/60fps video will not look smoother on a 120hz compared to a 60hz. This has been proven countless time and is placebo effect coming from the users. There is a reason why MEMC exist to make it look smoother at higher refresh rates.

I have been in the hz game long before mobile devices came with high hz. Heck I have a 360hz and 240hz (OC'ed to 260hz) monitor right now and I can tell the difference easily when I see different hz.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rstment ^m^:
Lmao memsc is completely different topic. Literally first response you get by googling explains why higher refresh rate is always favourable and definitely not placebo :

It'll feel less laggy than it does on a 60Hz monitor because the image will scan out four times as quickly top to bottom. On a 60Hz monitor, the bottom part of the image is drawn nearly 16ms after the top part. On a 240Hz monitor that difference is only about 4ms. Even though a game might be producing frames at a rate much slower than 240 FPS, the 240Hz display will still get that information to your eyes more quickly.

Linus tech tips did multiple videos on this same thing , I hardly remember most of the stuff there but this exact thing I sent you above was heavily discussed along side advice to ALWAYS disable vsync or such variants.

If you haven't already go and read up on it lmao. I think I'd rather trust the words of someone like Linus than random on the internet claiming he's " in the high hz game " :sneaky:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] MrPhilo:
This is getting off-topic now for Lineage.

But you're comparing 'gaming' to 'watching videos' - this is two seperate uses. I am comparing videos being played on 60hz than at 120hz. Of course playings games will be better at 60fps on 120hz. So do some fact checks before trying to go of topic.

For someone whose been on Blurbuster forum for a good few years and researching monitors and overclock potential, I would assume I would know a things. Also Linus video is about higher refresh rates for GAMES not video.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rstment ^m^:
It's kinda the same thing no... While video might be able to be paced in some way that new frames are timed not a single app on your phone is fixed fps all the time. That YouTube app while it might not play videos at 120fps does render rest of the ui at 120 fps... That includes scrolling , opening pages , and basic navigation around. If the adaptive refresh rate was able to detect 60fps video playback and ONLY limit display to 60hz in videos that are able to dictate screen accordingly when the next frames will be coming with 0.1ms or such latency switching that you can't even notice then I would have no problems with it doing that. But rest of the ui does not act like video , it acts just like any other game would act. Random fps based on how strong the CPU/GPU performs. Completely unable to be paced with display and much unpleasant on 60 hz display refresh rate... My reasoning on this might be completely wrong but I can tell with 100℅ certainty I saw real world difference between 60fps game lobby at 60hz display refresh rate and 120hz - We all come from the ****ing miui , if you were more observant there you would have noticed as well
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] MrPhilo:
No it's not the same thing. Please provide me any link than a placebo effect from yourself

Or make a post on Blur buster forum so I can watch how they tear you apart from even suggesting that.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] faiztarmizm:
I can't transfer file between my phone and my computer. The computer just not recognize file transfer. Is it just me? Where did I do wrong? Thankss
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] alefmm:
Is this ROM was built like this below?

I mean as production to avoid this tags [userdebug] switching that for [user] tag?

Reached that is necessary to avoid some apps that detect system modifications.

Spoiler content hidden.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] linuxnoobbbb:
I installed LOS 18.1 20210814 with Nebrassy's TWRP.

I cannot 'fastboot boot' or 'fastboot flash boot' LineageOS recovery, the former gave me this error:

Sending 'boot.img' (196608 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed

...and the later gave me this error:

fastboot: error: boot partition is smaller than boot image

However after installing LOS successfully with TWRP, I can hold VOLUP key to enter LOS recovery.

Besides, OpenGapps nano failed to install, with error messages like "error code 70"/"insufficient system partition space". Thankfully OpenGapps pico had no problem.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] @rmE:
Can someone guide which gapps will work? I was able to boot up without gapps but with gapps it always gave me bootloop.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] billy_overheat:
Miflash to stock

Flame or nik basic
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rstment ^m^:
I posted above... You can try going back to main menu after flashing rom and advanced > reboot to recovery. Then try flashing gapps via adb sideload. Reboot may fix the insufficient space error.

If it doesn't you have to wipe data , flash ROM again and go to advanced , reboot to bootloader. Phone enters fastboot mode , download twrp by nebrassy and flash it via

cmd : fastboot boot +enterTWRPpathhere

Once phone is in twrp you flash gapps via adb sideload and it should work - I installed opengapps pico , you might be able to install nano as well via twrp but I personally only tested pico
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] litetaker:
Hi all, not sure if it is okay to ask a question here, but I am considering to buy this phone and put a custom ROM on it. I wanted to know if the experience/performance with a custom ROM is smooth and snappy. I got feedback from one user already that it is quite bad with custom ROMs and not really very smooth. Wondering if this is the general consensus or if others had better experiences.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] linuxnoobbbb:
After installing Android Accessibility Suite & enabling Select to Speak, the volume control panel always shows the gray accessibility volume slider instead of media/call volume sliders. Not a big problem since I can still click to expand the volume control panel, however I think it's better to be fixed.

Also, I think volume keys should affect ringtone/notification volume (instead of media volume) by default when there's no media playing - currently it seems that volume keys always affect media volume instead of ringtone/notification, even if there doesn't seem to be any media playing at all (except that there's an ongoing phone call, volume keys affect call volume by default in that case)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] rehankumar:
Can someone confirm if carrier aggregation is working for them on this ROM?

Can't seem to get it working on either airtel or jio whereas it seems to work fine on MIUI
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] vanjimber:
Can you tell me, in the new version (lineage-18.1-20210821) fixed the problem where sound of the incoming call does not work when Bluetooth headphones are connected?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] iminnow:
R angle jagged edge
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Senaxo:
Can someone help me here, I installed this Rom and started it so far, but I have a problem that the "Google Contacts" do not synchronize. I hope someone can help me?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mnbpt:
Did you install gapps? If so, which?

Are you saying that you have Google's Contacts app installed and your Google account setup and your contacts aren't synchronizing, or are you using Lineage's Contacts app instead?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] iminnow:
Open google play services address book permissions
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rajdeep Madasu:
Does latest version has inbuilt network meter ??
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Senaxo:
Yes, I have installed these "FlameGApps-11.0-basic" gaps here. So I use the existing "Google Phone" app, which was installed and I set up the Google account, but still my contacts cannot be synchronized. I don't use this Lineage contact app at all, but it is available.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Fuechslein:
No because it would be blocked by the camera cutout.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] fonzserge18:
hows codm works? like the eu rom?