i do it all the time with my redmi note 3 pro before..i'm editing my wlan mac address..Maybe dont do that?
i do it all the time with my redmi note 3 pro before..i'm editing my wlan mac address..Maybe dont do that?
thats because you installed magisk + usf... its faking your device as MI6... uninstall all your mods and reinstall our ROM...
<< update >>
Tried. The "false" value actually just set the auto brightness to a fixed value when it is activated. So, the slider will not move up and down.
However, the "false" value does "cheat" the manual brightness to stick / stayed after deactivating the auto brightness.
It is not the right way but hey, I can now use 30% for manual brightness and set 60% or any higher value when I activated the auto brightness.
Basically, manual brightness level is fixed at 30%. The auto brightness level is now fixed at 60% and when auto brightness is turned off, the manual brightness returned and stick at the preset 30% level.
So, now. I just have 2 brightness levels on my phone....
>> Auto Brightness ON, my brightness is fixed at 60%. (This % can be adjusted to your liking).
>> Auto Brightness OFF, the brightness is fixed at 30%. (This % can be adjusted to your liking).
Temporary fix for the time being using this "cheat code" until MIUI Team fixed the over-aggressiveness of its Auto Brightness mechanism. Haha.
Thanks, buddy...
Isn't that the way Auto Brightness always behaves before the 'new auto brightness' thing ?
In My Kenzo with xiaomi.eu 7.9.14 Android 6, the auto brightness is always like that.
Manual brightness and auto brightness have their own level, and the slider will not move up and down when auto brightness turned on.
I think with that new auto brightness turned off, you are basically back to the old auto brightness style.
This is just like the '<bool name="support_new_silentmode">true</bool>' that turns New Silent Mode on, when you change it to false, MIUI 8 silent style is back.
I keep thinking that the reason Xiaomi developers put an option like this is because the want to keep the codes for these 'old style' in their ROMs (brightness and silent mode), and maybe they don't think people will like it or simply these 'new styles' are not 100% working perfectly....yet.
haha, at least now you have a way to go back to old style until Xiaomi fix the bug.Possible . Strange indeed! I do not know what is in their mind!
haha, at least now you have a way to go back to old style until Xiaomi fix the bug.
See screenshot, its already EN US..
Please change autobrightness so we have some control over the brightness level. It should be autobrightness with possible adjustment, like in the old days. Now its fullauto and it is really bad :/
Please change autobrightness so we have some control over the brightness level. It should be autobrightness with possible adjustment, like in the old days. Now its fullauto and it is really bad :/
Maybe you want to read these links above.That also happens to me on my Mi5
I think people started to losing faith in Xiaomi developers and turned to xiaomi.eu for help hahaComplain that to the official MIUI developer in the official MIUI forum.
Not here in eu rom forum!
7.9.20 is closed beta. Public release (7.9.21) will be on Friday as usual...Is there a 20/9 china rom update for this week?
And you just won a banDon't post bull...it, first go and see for yourself and then post! Next time you will be reported !!!
Hi! I have a Mi 5S, and 2 cores (2,15 GHz) are sleeping of 4. I read about this, but this is not fake information by any third party app, because I can feel the speed difference, that was the reason I checked it. A tried CPU fixes, mpdecision too. Btw it works until I lock the screen for at least 2 minutes. Only reboot turns on the other 2 cores again. But... I'm never in that mood I wanna reboot the device after every screen lock... Do you have any solution, to fix this? Other CPU fix, or anything?
No bug.. That's fine..Hi!
Is this normal or this is a "bug" in the current capricorn/Mi5s build?
The build.prop fingerprint shows 6.0.1 but the capricorn builds are based on real 7.0.
A section from the build.prop:
"ro.build.fingerprint=Xiaomi/capricorn/capricorn:6.0.1/MXB48T/V8.2.4.0.MAGCNDL:user/release-keys
ro.bootimage.build.fingerprint=Xiaomi/capricorn/capricorn:6.0.1/MXB48T/V8.2.4.0.MAGCNDL:user/release-keys
ro.build.description=capricorn-user 6.0.1 MXB48T V8.2.4.0.MAGCNDL release-keys"
I sent a bug report from the Instagram app and it showed (and maybe sent) this ro.build.fingerprint data.
I don't know that the build has the bug or not, but i think the source of the problem is Android 7.0. I tried other ROMs, like global, *******, miuihu, but on 7.0 this problem always appeared. Marshmallow ROMs wokred always well. But I wouldn't like to change, there isn't any problem, just this.Hi!
Is this normal or this is a "bug" in the current capricorn/Mi5s build?
The build.prop fingerprint shows 6.0.1 but the capricorn builds are based on real 7.0.
A section from the build.prop:
"ro.build.fingerprint=Xiaomi/capricorn/capricorn:6.0.1/MXB48T/V8.2.4.0.MAGCNDL:user/release-keys
ro.bootimage.build.fingerprint=Xiaomi/capricorn/capricorn:6.0.1/MXB48T/V8.2.4.0.MAGCNDL:user/release-keys
ro.build.description=capricorn-user 6.0.1 MXB48T V8.2.4.0.MAGCNDL release-keys"
I sent a bug report from the Instagram app and it showed (and maybe sent) this ro.build.fingerprint data.
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation