Recent content by manzing

Poco F1 : - Touch issues are back - Security and other app keep FC - Battery backup is worse Gone back to 8.12.13 which is the very best version till now.

Best version for Poco, touchscreen is much better than previous builds.

Is this fix suitable for Poco F1 as well?

It wasn't the case when i wrote (see the upload date/time). ;) Thanks @ingbrzy :)

Hi @ingbrzy Do you plan to release latest MIUI 9.2 china stable for Redmi 3S ?

You are wrong. Stable update for R3s is Marshmallow based and brings absolutely nothing new. Obviously, R3S users will NEVER obtain Nougat... So stop being sad, and let R3S users cry instead...

Same issue on my Redmi3S since two weeks, and this week a clock refresh bug in notification bar... i reverted on 7.11.16 -> everything is OK now.

@ingbrzy Are you sure it is fixed ? Xiaomi forum mentionned it in global rom changelog, but not in china changelog...

Redmi 3S : works fairly well, but Mi video keeps crashing, and french translation needs to be updated as some settings menus are in english now. Edit : maybe i updated before the fixed version for Mi video, my mistake.

Hi Yes, flashing remove the root and you have to root your rom again after flashing a new version.

Hi Just checked my phone (in french) and filename syntax is : IMG_YYYYMMDD_HHMMSS.jpg Besides, i can't find this setting in MiuiCamera.apk resources. Can you please confirm you are using rom version 6.11.17, not an old version ?

Only one (6.9.22 or 29 as i can remember) rom version was affected by this bug, it has been solved with the next release and nobody has reported such issue since then.

Yes for me. I bought mine from geekbuying and it was unlocked (it showed unlocked in adb). I flashed official stable using Miflah and it has relocked the bootloader. I had to officially unlock it again to be able to install TWRP and xiaomi.eu roms.

I've read that beta stable has some issues but developer rom are not meant to be buggy (according to en.miui forum). But i guess ingbrzy has good reasons for that. Too bad, the changelog is pretty good.

Just did the same thing : First write for 6828 value is effective but unable to write 6829 value with qualcommtool.exe. When i look for B20 4G network (others operators use it in France, not mine : i try in case i change...) i don't see any. So it seems the change of NV value had no effect...