Search results

My second mi 11 pro died a couple of days ago after 1 year of use with xiaomi.eu - I flashed it the moment it arrived - first miui 13, then miui 14. The first mi 11 pro died 6 months after I bought and flashed it. The seller replaced it. Now the replacement is dead too and it's already out of...

that didn't work for me

Reportedly they don't have these issues on the chinese ROMs (excluding the legacy AA one).

Adding the Android Auto problems (starting from MIUI 13, WIFI drops for a bit on GSM network changes, which disconnects Android Auto) to the latest deal-breaking notifications issues, the best stable ROM seems to be 12.x.

Cool. Pls, keep us posted should any changes in the behaviour occur. Thanks!

can you confirm that .DEV ROM solves the notifications issue for certain?

Mi 11 Pro, MIUI14 stable (xiaomi.eu). The adb log (logcat) shows a lot of these: 02-22 16:15:23.478 4371 4371 W GCM : broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE flg=0x10000000 pkg=com.google.android.apps.tachyon (has extras) } 02-22...

I guess not.

Same issue on mi 11 pro with miui 14 stable. Notifications appear after hours, or never. They tend to show when the app is opened. It affects all background apps - even google maps started updating its location "once a year". MIUI 14 is kind of messed up in that regard...

same here. something's wrong with that rom. flashing back 3.0.10 leads to "wait until your device is fully rebooted" when trying to start anything. it seems i'll have to do a "factory reset", wiping the data. update: factory reset didn't work - it wouldn't accept my lock screen pin, so had to...

no. just do it Sent from my MI 8 using Tapatalk

works fine dude Sent from my MI 8 using Tapatalk

right. cool. thanks! the fixed rom works fine with FGS on two of my mi8s's too! good stuff guys! Sent from my MI 8 using Tapatalk

mi6x 10.0.3 rom is still there and it's also affected by the FSG issue. Sent from my MI 8 using Tapatalk

you're in a gsm black spot dude. it's normal. Sent from my MI 8 using Tapatalk

Create a backup from inside TWRP first, then try a dirty update. If it doesn't work, wipe data and flash again. Just remember NOT to turn on the full screen mode afterwards.

It's safe, but you could also re-flash 10.1.2 and disable fullscreen mode upon install and then we'll wait for the next update together. :-b

i think it's the same issue like in mi8 Sent from my MI 8 using Tapatalk

wipe, reflash and don't activate full screen mode until they release the fix. Sent from my MI 8 using Tapatalk

I can now surely confirm the fullscreen mode causes the black screen. Unless you're using the screen navigation buttons, do not install this ROM on mi8! I think the mi 6x black screen issue after upgrading from 10.0.2 to 10.0.3 might also be the same bug.