Search results

This also happens on other devices and it is not because of a damaged part. I can confirm it because I changed the display for a friend (mi 9t pro) and fingerprint sensor only worked with old miui 11 roms. Probably xiaomi implemented some sort of check like apple does. sorry for being off...

Thats odd. maybe others know more. Yes mine also says default but it works as a German keyboard ( correct symbols and everything )

I did it the same way as you described. In my screenshot you can see the layout is shown under keyboard's name. it should also remember it after the device is reconnected.

Asking this again as it got overlooked. Is the swipe to switch between control center and notification panel a xiaomi.eu feature? if it is, it would be great to make it optional as it makes smart home tiles unusable.

3.5.1_10 is twrp's version (teamwin will increment it) but Manuel has his own version number for his builds (v1.2) so this one is version 3.5.1_10_v1.2

Is there any way to disable the swipe gesture when in control center? the one where swiping to left or right switches between notifications and control center. If you have any smart devices in control center and want to change their brightness for example, it switches to notifications instead...

it's the recovery posted earlier (#102) named MBTWRP and solved the encryption problem when using pin code for CMI.

That must be specific to UMI, I do not experience that with CMI. Did you try the 3.5.0 TWRP? does it have the same problem when flashed as 3.4.2b?

It is the same file please stop posting the same comment again and again. we get that you want to "promote" your thread. I am confirming for everyone else who read this thread that the files infact have the same checksum: 90381326bae874f405e264baff6ba12a MBTWRP_12.2.5_CMI.img...

It is the same recovery as the one linked by Superwitschi

So, the guy posted this a couple of weeks ago: "Redmi K30i5G version, Xiaomi 10Pro, Xiaomi 10 self-esteem version, Redmi K30S, Xiaomi 9Pro5G Android 11 TWRP3.5.0 automatic decryption 2021.2.2 emergency update, support the latest internal beta development version to decrypt data!" At least that...

Thanks for the info. Since i discovered that such a group exists i'm trying to register on qq. It's a joy to use google translate and screenshot every page lol /s

apparently they have a group in QQ (probably something like chinese telegram) and the files are shared there.

This is not the same issue with last week's build. Do you by any chance use a dns like 1.1.1.1? or vpn or something that blocks that url? If I'm not mistaken that is the URL used for redirecting to public wifi logins. google has also a similar one.

If I remember correctly it's a problem with specifically this device (poco f2 pro) at least from my encounters on this forum. Mi 10 pro passes Safetynet just by hiding magisk

This is actually not a good idea if you are really flashing a firmware with anti roleback protection! Those lines basically ensure that you don't flash such firmware if it's number is lower than the current one. They do the following: 1. Check firmware files for an anti roleback version and set...

oh now i get it, you mean the video after it's slowed down is 10 second. Yeah the same thing on 10 pro. That's my guess as I cannot think of any other reason why it does that. Maybe someone with more technical knowledge can clear that up. But no matter the reason, it's still really...

wait, 10 seconds?! mi 10 pro only records 3 second videos and only the last second is 960fps -_- If I have to guess, the limitation is probably that the storage cannot handle that amount of data written to it, so they probably cache it in ram and write it afterwards. I would love to have a 10...

What is the problem? The line you marked means if the variable is not defined set it to 0. also there is a check for it just 4 lines after that. For example the following: echo setting variable to 0 set CUR=0 if [%CUR%] EQU [] set CUR=2 echo %CUR% echo removing the variable set CUR= if [%CUR%]...

Some general questions to narrow down the problem: Do you both updated your phones at the same time? Did the problems start right after the update? Does it go away if you install the last known good ROM you had before the update? After that you can know if it's a hardware or software issue.