Search results

The one you linked is the one I am currently using. Really stable.

Same here (I am Italian). 1) Yes 2) Yes 3) Honestly it works great with stable build (10.0.3.0), while the dev branch is still too young (based on Pie).

I have already done that. But, as I wrote above, my suspect is that my proximity sensor never worked well ("unstable" is not the proper word) and now I need assistance as it completely stopped working.

This is simply not true. You have to format data if you move to a rom with excrypted data (for example, stock one) to a rom without encryption (for example, xiaomi.eu). When you update the weekly version of xiaomi.eu there is no need to format data. Still format data has been suggested when...

I think I have an hardware issue with my ultrasonic proximity sensor. But I am not sure since it worked inconsistently since the very early days I owned my device. I guess I would need to send the phone for assistance but I would like to know your experience with the ultrasonic proximity sensor.

I do not really understand. Nevertheless there is one rule: since Xiaomi.eu roms are not encrypted while stock roms are encrypted, when moving from stock to Xiaomi.eu or the vice versa, you need to format data (not just wipe).

Use Mi Flash tool and restore the fastboot version.

Done! Now I am No. 19 who confirmed the issue. Thank you.

I wrote "workaround" and not "solution" on purpose. By the way, which is the confirmation button?

The ultrasound proximity sensor is definitely less efficient than the ones we were confortable with. Still I have a couple of tips in order to make the call experience less annoying. First, try to calibrate the proximity sensor by entering the proper menu under settings \ device \ all specs and...

For MiMix2S users: would you suggest upgrading from 8.7.19 or it would be adivisable to skip this week's version and wait for the major bugs in gallery and file manager to be fixed? In other words: is there anyone who flashed the current version and does not have the relevant bugs? Thank you in...

If coming from official beta, then the rom is encrypted. So, in order to successfully flash xiaomi.eu rom, which is not encrypted, you have to remove encryption first by a "format data" (wipe is not sufficient) in the recovery. I had the same issue before understanding what was blocking me...

The problem is rom version Rom is MIUI 10 Global 8.7.19 Beta. The only TWRP working with that version is unofficial TWRP v7. You can find it on XDA: https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922

The .IMG file should be in the same directory of the file fastboot.exe (if you are using Windows).

The command "fastboot flash recovery NAME_OF_THE_RECOVERY.img" is correct. Obviously you have to give the command from the directory where the recovery .IMG is stored and change the name if needed. I would suggest to rename the recovery in "recovery.img" and just give the command "fastboot flash...

Are you sure you have also activated OEM unlock in developer settings?

Mi Mix 2S with Magisk 16.6. No problem here.

Mi Mix 2S is NOT currently (while I am writing) listed in the available roms. Did you flash the one for Mi Mix 2 instead??

Stock global (MIUI 9.5) updated and rooted with Magisk 16.4. I will give a try to xiaomi.eu. Thank you for your appreciated advice.

I am sure it is not a matter of permissions, since I have an identical issue with other apps (for esample, AdAware does not work, as it cannot write in /system/etc and update the hosts). Anyway, I am using the latest version from Play Store.