#Xiaomi POCO F5/Redmi Note 12 Turbo [Archive]
57610 messages · Page 58 of 58 (latest)
Let's see
My reported fingerprint problem was when I turned on the private space
yesss, same case
fingerprint issue fixed?
Hotspot not working on new build
Don't know because i have frp sensor so i never faced this problem
any issues if i don't flash on both slots?
mine working fine
Are you sure?
Turns out I just need to reflash the same build
It might be because I flashed while my hotspot is turned on. Reflashing fixed it
Yeah, 100% sure. Can't toggle it even in settings but all good now
Was about to download the new one lol
wifi has the issue too
are you already flashed into both slots?
just did
Why is download speed so slow for April 11 update
as I messed up flashing ended up with cannot boot to recovery the only way is to flash the stock rom and start fresh rip files
Booted. Shazam audio search? Can't find in setting
install the app
can it find songs?
I've tried and found songs with shazam
ok thanks!
auto brightness fine?
fingerprint unlock delay issue?
It doesn't work at all for me
Which disabled all apps that needs a fingerprint to login
ill test everything just need to dl the zip file
ill check
Testing it in different light
also test for ducking when unlock pls
works for me
thanks, i can post as OTA later
In ducking brightness go to low level after unlock it rises to sutible level
Other wise work fine
thanks!
autobrightness works better now and shazam works
Fingerprint sensor doesn't recognize your finger when you try to register?
try to cleanflash
or double flash
Fingerprint works for me
ahh shee long time no see
did some widgets got removed?
like?
helloo
ye just got back trying the rom again lol
Idk
It's been gone long, due to google app update. If you remove the google app updates, the weather widget will show again.
its been there in my end since the last latest update
hmm
alright thanks for the insight, i remember that i updated the google app
thanks ❤️
Just try to remove the update and check if it shows again or not
yup its present after uninstalling the update of google app
u best ❤️
No worries 😊
New OTA is out!
Sourceforge files have been updated!
FIRMWARE NO LONGER NEEDS ANY UPDATING, NOW INCLUDED IN THE ROM
RECOMMENDED TO FLASH ROM TO BOTH SLOTS VIA RECOVERY TO AVOID WEIRD BUGS LIKE DOLBY MISSING
All audio issues should be fixed, now bar returns, ksu zip updated with latest kernel changes
I see evox community build have 233 krnl. No issue with guddix sensor
we won't use outdated stuff anymore
now following Arian/cupid devs stuff
Ohh . Understand
#1209524619313156096 message
This is right for new build?
Pixeldrain?
So it means that this new build still have issues with goodix FP sensor? Then I'll wait till it is solved because that issue is really annoying.
yes
no
Posted
This one?
New build with hos 2 firmware can i use Old module?
Which is the link for the updated KSU?
same in sourceforge
what module?
Do u have any guide?
For hide keyboard space and black baar at bottom
I don't use that module my guy.
HyperOs2 is already pre packed with the rom
so no need to flash fw
hm ok
Hi, can i use OFRP-R11.1_7_RECOVERY-Beta for flashing the latest build?
While double flashing, do I have to change the slot from recovery? Or just flash? Can you tell me the process please?
Alright Ill do a guide for double flashing
flash rom > change slot > reboot recovery > reflash rom > reboot to system
And if I clean flash, do I need to format the device two times after flashing in two slots?
In this case scenario lets say you are currently in SLOT A:
- Reboot Recovery
- Wipe Cache/Dalvik
- Wipe Cache
- Flash Rom
- Reboot System
Since you started with SLOT A the rom will automatically flash to the inactive SLIT which is SLOT B and once you reboot into the device it will automatically boot into SLOT B.
Since you are in now in SLOT B just redo the following steps:
- Reboot Recovery
- Wipe Cache/Dalvik
- Wipe Cache
- Flash Rom
- Reboot System
Just like I said the rom will flash to the inactive SLOT which is SLOT A. Now once you reboot into the Device you are now in SLOT A. This will ensure you that the rom boots fine for both slots with no problem. Now you just performed double flash.
@frosty moon @woeful lava
Or just do this but sometimes this fails idk why, it could be due to the recovery (ofox).
And what about this?
no
just format once
Okay. Thank you
I'm able to get rid of the nav bar. But is there a way to make the apps full screen?
reading seems to be your weakness
oh okay
still can enter fastboot? why not flashing vendor_boot, dtbo and boot?
mb bro
I disabled it I forgot the package name
Bro how to check we are on which slot ?
Via Recovery
Ok In recovery...
Ok thanks bro
You can also check on which active slot you are in via DevCheck or just remember what slot you used after flashing.
co.aospa.dolby.xiaomi
Hey Guys, max auto-brightness is lower (darker) than max manual. Is it only me? EvoX from 11.4.
thanks dev
Yep Can 😅 bro I am also already back to Evo x rom after flashing stock rom
Audio problem related that I found on the latest 15/04 build (dirty flashed) :
Audio clipping/distortion on speakers and wired headphone at high/max volume with or without Dolby.
There's no notification sound on bluetooth headphone even though I already set the notification sound to max and not in silent mode.
The good thing are there's no more audio leaking to speakers and the media volume will be lowered when notification sound played using bluetooth headphone.
Thanks for the audio update, Joey.
My main speaker ain't working
current build date 11th april

reflash again
reflash again
yes, I already flashed on both slot
hmmm of thats the case then please provide logs
okayn!
just a little help how do we flash on both slots?😃
here's the log
read back a little
alright lets wait for Joey to analyze the problem
it never fucking ends with this device
cant even build for k20 pro or mi 11 without poco f5 always asking for attention
cursed device ngl
Some users are curse for this device 🤣
why are you even following this topic
Some drama a while ago
so now you get tagged each here tag and you're gonna answer like a jackass
fucking unfollow if you dont have an F5
Oh I'm sorry I wanted to follow some drama
Calm down
this is the drama im following
Wrong drama 😭
ts isn't even drama
Crazy
they could be scared flashing test build for boobloop potential ig
on my pixel 6 bootloop happened.
All I did was rollback to 10.3
idk why tbf
others devices worked
Please, pin this message
i dont even encounter the distortion wtf
Me neither
I did gave feedback earlier, nothing on my end
hi
Idk if I encounterd it, it could be from the video itself idk its a 1 time thing so I didn't bother to check.
best option
I'm everywhere
I checked it again with music full blast with dolby on, nothing wrong
Same
Dude probably got too much audio enhancer module or smth it breaks audio
i swear some people just trying to sabotage at this point
Auto brightness works better after unlocking but it's limited comparing it to manual
Is it intended?
you can flash that if u can't enter recovery, ur file will be safe
ye I swear wipe data before flashing is mandatory
it never works without it for me
I think the autobrightness limit is because of Ximi
I saw a YouTuber video also complaining about the same on hos
JOEY the people that we are really enjoy and grateful of your work we support you , there a lot of disrespectul and ungrateful people..that thinks that everything is life for free and your time is very valuable..
Really big thank you for the hard f*cking work. It's a godsend to have the evox team
Can anyone try the same as this?
.
Or it's just HBM
Yeah thanks for the work (even tho I dont have the device, thanks for owning evox)
i will try the new one..
Here's the video regarding the distortion I mentioned before. Sorry for making you upset because of my report. But since I am always listening to music with this phone everyday, I instantly noticed the distortion.
Are you using gain on the equalizer or smth?
To be turned off it sounds already too loud
turn all sound related stuff off on poweramp
or turn off dvc
damn it was a hassle to install this last build , after many bootloops for no reason flashing twrp then back to ofox finally booted. let's test it now
No, I never use dvc or eq. All turned off
Pls try the autobrightness limit compared to manual
No, I never use dvc or eq. All turned off
I don't know but it's already too loud,it has the same volume as my device with dolby
And without its like 25% less volume
I even never turned on Dolby since I hate the sound it makes.
well, i turned dvc and eq off and never used dolby and it sounds fine
nahh its not about the report you made, users typically reports only during ota releases and not during test builds
Lemme try
To be fair Im now sticking to OTAs since I can't risk a errors since I'm using the device for work
Change slot then reboot recovery, try reflash rom,if still same try reboot system, if u can bootup updated via ota updater. it also happen to me yesterday
If anyone has the autobrightness "issue" feel free to @me
It's very minor bug but I want to know if it's only me
I don't use autobrightness but as a trial I checked and didn't realize much of a difference compared to manual
Yh it's like a 5% more on manual (100%) than on auto (100%)
It could be HBM turning on but I don't know,maybe Joey knows about the implementation
Dead wifi after single flashing. (flashed again and it came back)
It's because only a few people flash test builds and they are like flashing different roms all day. But us "normal" users wait for the final build and then flash. And we use it as a daily driver that's why we see those issues
Pls test auto vs manual brightness limit
99% reachable on auto it seems
Best is take some rest, Hyde and I can handle
Yh that's what I noticed too
But yeah it does get noticeably dimmer (100% manual is brighter)
Seems that 100% auto = 87% manual
For the latest update
If we use OTA, does it flash rom on both slots automatically. Or we need to flash the rom manually using orangefox
+1
most likely auto reaches up to 500nits and manual slider up to 1000nits , yes when it is on autobrightness max it is dimmer but since I don't use auto at all it's fine for me
Maybe it can be implemented so auto reaches full brightness
it's due to brightness changes in trees
they matched with hyperos values
i'll just let it be
better to flash rom on both slots , for me when I flash on only 1 slot after restart it was keep flashing on homescreen only after flashing both slots it becomes normal
when I click that settings fs
Pls consider it for future updates, nonetheless latest build is awesome,ty for the bug corrections
If anyone has problem consider going clean
Oh my Orange Fox is finally working when flashing 0415 build
What did they change? It just don't work before
it's always working
hi i cant get into my recovery, it always get into fastboot mode. how can i boot to recovery without losing any data?
Just flashrecovery again, it should work
If not flash the whole stock fastboot pack with miflash or with the script
evox recovery from xda?
Orange Fox
how to? i forget the command
fastboot flash recovery /path/to/recovery.img
doesnt work. i get into fastboot again
not "fastboot flash recovery_ab (recovery.img)" ?
Yeah it has been like this since A14
Both should work
try "fastboot flash recovery_ab recovery.img
same
Then you need to get the fastboot pack, tell me if you don't know where
i cant even boot into system
tell me pls
what did you do?
Do it on your computer than, you need your computer anyway
downloaded new update going to flash in the recovery, but it get into fastboot
@undone flaxhttps://xiaomirom.com/download/redmi-note-12-turbo-poco-f5-marble-stable-OS1.0.18.0.UMRMIXM/#global-fastboot
你正在看的是 红米 Note 12 Turbo / POCO F5(代号 marble)的 稳定版 刷机包,ROM 版本为 OS1.0.18.0.UMRMIXM。刷机前,请确保机型准确无误。您可以在 Fastboot 模式下通过命令 fastboot getvar product 来查看型号。 …
you flash the rom then in it boot to fastboot? or you flash the recovery?
i was going to go to recovery to flash the new update, but it never did
then how?
extract it, find the flash_all.bat(not the one with lock or keep_data), run the script and let it cook (assuming you are on windows?)
you boot in to recovery but it boot to fastboot?
yess
yes im on windows. no need any software like miflash?
You can just use the scipt, but i recommend you download a miflash if possible,
what's this? flash stock?
Yes, stock system
so there no rescues beside reflash stock?
No other way that i know
and all he did was reboot to recovery? that scary
it might be due to wrong firmware check pinned comment for the recommended firmware versions
once you install the latest firmare you have to install old one manually using cmd
aren't the firmware included?
Wait if the firmware is included now, so incase of clean flash do we need to flash it or not
Also so all different regions how that works?
yes but it's possible that you might have issue with it
you can flash firmware manually to go back to old version
Why would i go to the old version?
in case the included one doesn't work
now i remember. he might downloaded the OFRP from here which is only possible flash in recovery not fastboot
you can install it in fastboot just download the IMG file instead of zip
https://github.com/Ctapchuk/android_device_xiaomi_marble-OFRP/releases/download/2025-02-15/OFRP-R11.1_7_RECOVERY-Beta-marble.img
guys the ksu-next to root the 1504 build is the one that appears in sourceforge with 13-04 date?
or with this latest build there is a new one
i mean the one in telegram sorry. the one with only 42mb
ok
how?
have you tried the module to hide the navbar with latest build? is it works?
Yes working
great i'm going to flash the latest one...hope everything works ok
All custom recoveries come in the format of an IMG file (some are released as a flashable ZIP, like OrangeFox, but there's still an IMG inside).
However, installation method will differ, depending on where the recovery ramdisk resides on your device specifically.
Failing to install the custom...
That's fine my guy.
thankss broo.. you help me out of fastboot
Your point is valid my guy and I get it , the solution I could think is instead of a weekly update we should have 3 weeks per update.
First Week - Initial Testing
Second Week - Final Testing
Third Week - Optimizing All bugs that can be fixed
Then release OTA and all bugs that are caught after OTA will be address on the following update. This will ensure testers to have a valid time to test things out and provide enough logs for Joey to check and fix.
Congrat, and sorry I provided the less optimal instructions
i jus remembered i did fastboot boot recovery.img lol
the instructions tell how to get out of those things.. tysm
i flashed the latest one for me my FP GOODIX works flawlesly! dolby or without dolby sounds perfect, with speaker and with bluetooth earphones..seems everything very smooth..thanks joey again and again and the rest of the team
the only thing i can't flash is the ksu next , it appears me corrupt file, i downloaded 3 times..anyone could give me the file please?
Alright lets hope and see if Joey agrees with this.
its on sourceforge
Yes i dowloaded from sourceforge i'm going to try once again
I have this error
Can't determine the active slot
Initial impressions about the last build(Apr15):
- Sound increased when listening with headphones significantly which is cool
- WhatsApp bug is still there. During call through earpiece or headphones no issue , listening voice messages with headphones no issue but listening voice messages through earpiece always need to push volume button once otherwise it is silent
you came from dirty flash right?
Fingerprint seems fine so far I hope it will not bug out like in Apr7 build suddenly
@azure furnace yes flash on both slots and everything works perfect
try flashing on the other slot
I don't how to do that , i have to change the boot slot in recovery?
i honestly didnt notice it until this message
now im bothered
its really hard to hear tho
Biometrics doesn't work
Guys is this normal?
yes
okayy thanks
if you are using aosp keybox its normal if not then its not
yeah I am
then that should be fine
I dirty flashed every test build till today when released and I flashed today's build too and everything works without any bugs. thanks joey..👏
I try in the other slot and it's the same... Should i try to flash it with fastboot in both slots?
Did you boot into the system already or not?
Yes
Yeap never happened to me
the one that is on sourceforge the 230 from the 13-04 date
i didn't see the 233
the build from today have 230
223 i meant
sorry
can i use an older one? from the build?
not sure since i didnt test it myself
or just use magisk
its weird that the zip file isnt flashing in your end
nope
Guys whats happening latest build works fine na?
Few users saying wifi not working this not working that not working
Should i normally flash latest build? Or waht
works well in my end
Ok lemme clean flash it
Btw just flash rom thats it na?
No need any fw or flash in both slot etc etc
yup yup
Newest HyperOs2 FW is already included but some are required to do 2 flashes
Um 😅
WIFI works fine in my end
Ok bro
Ok 2 flashes in case bootloops right?
Yes, Only issues based on users are distortion on high volume in some cases and fingerprint issue in private space and the usual could be related for not clean flashing the rom or dual flash back then.
Mine too godix fp 😂😂
Ok will dual flash it for safer side
Ok bro lemme flash it
Do you think if i flash it with fastboot could be work?
hmmm not sure exactly since you cant flash zip files via fastboot
only adb
Right
Fastboob = IMG
ADB = ZIP
can someone please give me the link for orfox and twrp
OFOX is in pinned
TWRP is in Sourceforge
and you can get them both in sourceforge
List of relevant recovery in one place
Thank you!
Noticed a weird bug, game sounds are not playing over bluetooth headphones
Tried every possible methods, and umm logcat for audio pipeline/server looks just fine
Since everything is working just when game is played (i personally tested brawl and codm) and no sound over earphones
Codecs - sbc/aac/ldac tried on all
send logs
Hmm it was whole system log, ill probably file for an audio log as it won't catch personal stuff
Meantime will try some more workarounds
Very understandable no worries.
How to check
it's this right?
@foggy tinsel
bro has both
wtf
actually it is correct
lucky bastard has FPC
we no frends sar 
It's diff per phone?
yes
Ohh
Blutooth headphones working in latest build?
shiiiiii @lyric dagger got sad, dw we friends 🤝
Hmm tried workarounds, no luck sadly maybe bluetooth issue on my end or probably fw thing
Only games sound is not working in headphones
Bluetooth right?
Me as well
@azure furnace hmm
Any solution other apps like youtube n music apps fine no problem there
alright, send logs whenever you're free
No everything fine just games
Same
Yes
I bet if someone else confirms this would save me 2hours lol
Fetching audio logs is painful
I want joey to have some rest for now as well, this is manageable with 3.5mm though
Some of them don't have it 😔
Are you Indian btw?
Ha
Fw issue hoga probably
Ha
he is going to rest for a few days due to issues we currently have awhile back
Main bhi wahi soch rha tha ke indian fw flash karke dekhna chahiye kya
That's good, I want him to as he didnt sleep that much merging april patches
Maybe it purposely shows both?
Nasa latest build?
facts finally a user who understandsssss :'>
Hos v2 indian nahi aya abhi tk
u get a plus points in my book
Fellow builder haha, its painful job
ako? yes
When I see bugs, I understand how my users be to me.
Its hectic
Yes no audio in bgmi also with realme buds
Fir ya to wait karo ya previous build pr jao ?
Wireless 3?
Same
hmmm alright seems like everyone is affected, try to fetch logs whenever possible at least this will help Joey in the following days.
3.5mm se manage nahi to old, but rescue party maybe aa sakta hai
Same mera bhi, white variant
Wired hai hi nahi bhai
Thank you confirmation ke liye, saved me almost hours to debug
Main enco use kr ra
Revert
Waha fw flash karna padega kya
Afaik, there hasn't been a global release for the F5 with HOS 2.0 yet, it's still in the beta testing phase. Only the China variant has it so far
new build have display saturation feature added or not?
Can anybody try " disable a2dp hw offload "?

Tricky question, 11th ko 5.10.230 kernel got hos2 compatible update.
But not to risk bootloop, use 1.0.15.0
Only issue games audio?
Ok thanks
Pati distortion daw pag max volume
Kala ko meron ako kanina pero Wala ata
Maybe on specific audios
only 1 person who is affected by this
@stable gust on bt?
can you confirm @neon topaz
Not here though
Yes
Hmm...
Try toggling sbc/aac/ldac if there
Here's the video
happens on speakers too based on his statements
Chat i recived update through system updater should I update??
Is fingerprint works ? Or any other issues?
Should I update or wait for stable update
Yep, not working
he sent logs too
Enabled and disabled
🤝👊
For this I have a complicated fix
Fp works and issues so far is Bluetooth when gaming thats all for now.
Requires flashing module hifi by reiryuki and force 16bit mode on speaker and it will fix it
I had this issue, when I enabled 32bit on speaker
Should I update through updater is that ok because I am from India and hyper os v2 is not available in India
Ha all ok
Ok thanks for confirming I will update ASAP
Because I literally tried of that navigation bar issue 😭😭
Keep in mind bluetooth user ke liye game sound is not audible via earphones/headphones
Just advising beforehand taaki you can make a choice
I have question. New build with hos2 firmware. I think about revert back to 5th March build. Flashing recommended fw is ok or i need to flsh fast boot rom first
I also have realme bus wireless 3 I will manage that game sound but youtube an all sounds are coming na ??
Last build is just fine, but that old build will bootloop
All ok just games (precautions de raha bas)
I'm not go for dirty. I will clean flsh.
To avoid flooding of reports, @azure furnace sorry for tag can you make an guide* for users that still havent updated
It's ok brother for games I will manage for few days for fix but for that I am really tried of that navigation issue that why I want to badly update
Its fine to ping me anytime dw, what guide?
All fine go ahead
Umm, users that are into gaming just a heads-up bluetooth audio for gaming wont be there
This will prevent further reports, surely too many reports get overwhelming and joey needs rest soo
Just a friendly guide
hmmm
As we have reports already furthermore will be a lot
yah we could do that but i aint an expert in audio, you could do the guide and ill pin it instead
that is true but only 1 person sent the logs but sure we could do an alternative route for now
I thought there was also an issue with wired?
Nothing such, just a heads-up for gamers
if you only use tws/earbuds/neckbands or any bluetooth related hardware to listen audio queues while gaming, then kindly make sure that you have a back-up 3.5mm headset/earphones. As this update has some issue with audio playback (only for games) via bluetooth devices, audio from youtube/any app is just fine, only affected are games
No issues
Reverted to previous now sound working
I wonder why it's only for games
.15
I think hos 2 ke issues
umm where's the guide to patch it tho
Yes maybe
Cuz beta
The patch is only for that speaker distortion sadly this is just a heads-up
Which violily had
Or that user idk
hmmm lemmi see might as well include it
At this point Ill believe anything as no clue lol
just drop it here and ill compile it
Clean or dirty
Sure, this is only for users that are facing distortion on speaker
- flash this mod
- paste this file in main directory of internal storage
optionals.prop
Reboot
Dirty
Some references if that helps
https://t.me/ryukinotes/53
All credits to Reiryuki and ZackPtg5 and respective devs for their hardwork, I take none
Message directly modules/optional prop - #1209524619313156096 message
Text inside optional.prop (as per my testing)
if you listen to FLAC or 32bit records use the below,
speaker.bit=16
sample.rate=96```
*Experimental (no issues except direct volume control in some music apps like poweramp)
```hires.pcm=1
hires.float=1
speaker.bit=16
sample.rate=48```
If you want github - https://github.com/reiryuki/Hi-Res-Audio-Enabler-Magisk-Module
Hi-Res Audio Enabler Troubleshootings
-
You can check via logcat and search bitwidth and play music to confirm is your ROM supported or not. If you see 24 bitwidth or 32 bitwidth and no any resetting to 16 bitwidth, that means your ROM is supported, otherwise it's not supported.
-
To check is your ROM already applied 24 or 32 bit width, run ...
bett imma compile
Joey is tired
Please just use the written optional.prop
Anything other might bootloop or worse (dont change values)
Thats user issue
Sadly, mr. Tejas hasn't updated the Evo-X launcher for QPR2 yet
Joey is back?
Typing...
Just a heads-up for gamers who are using the latest OTA release.
If you only use tws/earbuds/neckbands or any bluetooth related hardware to listen audio queues while gaming, then kindly make sure that you have a back-up 3.5mm headset/earphones. As this update has some issue with audio playback (only for games) via bluetooth devices, audio from youtube/any app is just fine, only affected are games.
Lastly for those users that are experiencing Speaker Distortion or while using headphones/earphones on high volume levels you can use [this](#1209524619313156096 message) to fix it temporarily.
Use this as a [reference](#1209524619313156096 message).
Take Note:
Please just use the written
optional.propanything other might bootloop or worse (dont change values).
Credits to @neon topaz .
Nice I added all links and relevance
Those who facing issues with new build it is recommended to clean flash to avoid breakage issues are coming mostly to those guys only who dirty flashed it.
@neon topaz he clean flsh and game sound working for him in blutooth earphone
For me game audio fine
No issue i m facing
Ill have to try it this weekend
Update if worked
But the guide is only for speaker distortion btw
If I'm clean flashing btw, do I still need to flash on both slots
You can, but usually not needed since you already did
Bluetooth?
Yes
I have not experienced it since
- I don't have bt earphones.
- My Wired Earphones are currently broken.
Hmmmmm
Did you flash twice @neon topaz ?
I flashed twice
Well I did following -
- flashed a/b
- reset the neckband
- reset bt settings
- disable all mods (ksu)
- disabled jdsp just in case
- then tried to spoof props with hi-fi
Nothing worked
facts
might aswell pin it for now
Do u clean flash everytime hyde
nope
I rarely do a clean flash unless something breaks that I cant fix.
Okay
Anyways custom rom community's moto
Clean flash after every QPR
because google likes to trouble us users
Yeah
Xiaomi POCO F5/Redmi Note 12 Turbo [Archive]
thats good to hear in your end but idk with other users though
Hm strange to me also
kek archived
Mostly guys either dirty flashed
this channel goes bye bye soon
ei hyde finally i could i flashed the rom once again (3 times) and i could flash ksunext..and finally it works..😏
