Search results

DId you buy the Chinese (or in some cases Indian) model rather than the Global model? If not, then play with your region settings.

It probably doesn't work -- just like Google backups in general doesn't work for a lot of folks on .EU

Yep, been working great for almost two weeks. Just had to leave the default version installed to retain maps compatibility with Android Auto. The compass issue never affected the latter. Out of curiosity I flashed Lineage20 last night and maps works properly with that on the F3.

Because you have the wrong version of the recovery installed for the android version you're coming from -- and yes it's because it didn't ask for a password and it didn't decrypt the data partition.

You can find firmware blobs which are flashable through TWRP here: https://xiaomifirmwareupdater.com/ Generally it's unnecessary, but in the worst case you can just flash the respective version for the rom version you're running, back.

Check the bands with Network Signal Guru then to make sure they're actually enabled. If not then try flashing the global firmware on top of the .EU rom. If neither works then you'll have to contact Xiaomi to get them to fix it in their rom. Then it will trickle down to the .EU rom eventually...

Because Chinese versions and global versions of some of their phones support different bands genius...

No. Once Xiaomi discontinues weekly dev support for a device, then weekly builds here stop too.

Something else was running in the background during your disabled test because it makes zero sense that using a feature that creates more reads and writes to the nand flash would actually increase a nand flash read and write benchmark performance. Logic dictates that your test is a fluke/invalid.

How long have you tested it for? It makes sense since it uses its own built in version of GMS. I'll test it for a day or two to make sure it doesn't suffer the same issue as the play store version (If play services data is cleared, the play store version will work properly for me for about a...

That doesn't work on either of my F3s. Clearing map data or play services data is the only thing that does.

Nope.

It's fine on my two. Better than the final weekly.

Everything is fine here on two F3 phones. Battery life improved on the two F3 phones I have, but everything else is the same. Compass still doesn't work in Google Maps without clearing app data or play services data every time -- but all builds since early January for this device have been like...

Yes. You have to type out that entire command from the command line. Your TWRP image likely isn't TWRP.img either. It'll be whatever the file name is of the relevant recovery you downloaded separately. Go read the how to flash a custom recovery thread in the Q&A section.

Yes.

Cards still can't be added. Likely not just a server side issue. Google Play says the device is certified but YASNAC fails. Getting the same error from the OP. Rooted with Magisk 26.1 and I've tried with and without the denylist, with and without Shamiko etc.

Oh yeah I forgot about that app. I used that with my Mi Band 4 and my old phone before my buddy gave me his Galaxy Watch. Now I just use the Mi Band at work so I haven't needed the directions etc. Thanks for reminding me it could do that.

Weird..I have never seen my Mi Band 5 in the Bluetooth devices list yet it syncs properly with Zepp Life and notifications etc all work on it.

I don't have either of those issues on my pair of F3s.