Guys, today i successfully got root and first of all slightly changed the values in sysmon.cfg. Changed maximum brightness level (255) from first value till next four values, so there`s first five values set on maximum brightness, 255. And then the brightness gradually goes lower and lower till minimum (100) value. I did the same thing on my previous phone, Xperia T, and had no issues with this. What do you think, everyting will be OK with Z ? I don`t play games so much , more often surfing, music, movies. But when the screen is changing brightnes this is so annoying, so i`ve changed this values, but a little bit worry, because the screen is bigger and quad-core processor, so what do you think ?
Well, i guess noone knows exactly answer on this question, and in the meantime i changed the values, and set first 10 values to maximum (255) brightness level, and have no issues with this. Instead i have maximum brightness level of the screen when surfing and listening the music, but in games the screen still makes darker, when the temperature of the phone becomes too high, and in this condition i think the screen is better to be a darker indeed, to not to let the phone become too hot and not to damage it. But in the normal state i think that the screen in maximum brightness won`t damage the device. I hope so
Recently bought mate 10. Compare to my current mate 9, I noticed the mate 10 screen brightness isn't as bright as the mate 9. Wonder why manufacturer decrease the maximum brightness of newer phone.
nickpda said:
Recently bought mate 10. Compare to my current mate 9, I noticed the mate 10 screen brightness isn't as bright as the mate 9. Wonder why manufacturer decrease the maximum brightness of newer phone.
Click to expand...
Click to collapse
Max brightness is reached only when in auto mode+sunlight. Check the gsmareana review. Otherwise indoors the brightness is lower and cannot be manually toggled to reach the max brightness the display is capable off. Personally the brightness is more than enough for me in real usage. I use auto brightness and toggle it to about 50% brightness.
Loving the Mi 8, especially after the 10.1.1 update, however the "auto" brightness Useless. Virtually every time you unlock the phone in low(ish) light its reset to a very low setting. I've had phones from many manufacturers over the last few years and they all seem to have managed to string together a half decent auto-brightness offering.
Does anyone know of this is something they're working on?
I have the same issue
I love everything about the new update but that issue made me hate the update. Anyone with a fix? Appreciate it.
Not sure if the same brightness bug is impacting AOD too, which reacts to light levels but so aggressively at night that it actually turns off.
Auto Brightness on MIUI has always been dodgy as ****. There's workarounds - check out Velis auto brightness - but they're an additional battery drain since the app is constantly running.
I felt like it's not that bad on the MI 8 though.
Cheers
Just giving Lux Lite Dash a go and seems to be doing the trick. You can manually adjust when needed but then commit to memory for the next time a specific lux is reached. I guess over time, like most phones, it will then be customised how you like it.
Will see what battery life is like though...
So far so good. Battery seems to be at the same level with Lux Lite Dash running.
Lux Lite had issues in the end. The max brightness was lower than that of the phone. Switched to Velis which seems to have an option to allow the phones auto (and max brightness) to kick in when there's bright sunlight.
Hello, I have noticed that whenever I remove the charger from the phone after a full charge, the CPU stays idle at 1.04 and 1.06 for big cores instead of 576 and 710. It is fixed after a reboot.
Can anyone else confirm and report back the bug?
10.2.2.26 official global rom.
MysteriousStranger said:
Hello, I have noticed that whenever I remove the charger from the phone after a full charge, the CPU stays idle at 1.04 and 1.06 for big cores instead of 576 and 710. It is fixed after a reboot.
Can anyone else confirm and report back the bug?
10.2.2.26 official global rom.
Click to expand...
Click to collapse
I can confirm that the bug appears ONLY when I use fingerprints for unlock. When I delete all fingerprints, it is gone. (and in addition, still present in 10.2.28 EEA)
MysteriousStranger said:
I can confirm that the bug appears ONLY when I use fingerprints for unlock. When I delete all fingerprints, it is gone. (and in addition, still present in 10.2.28 EEA)
Click to expand...
Click to collapse
This explains why I got better battery hours after I deleted fingerprints! Not that it was bad before, but now it's ridiculously good!
I don’t think this a bug, it probably must be this way in order to wake up screen just by putting the finger on the scanner.
Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.
kingbasescu said:
Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.
Click to expand...
Click to collapse
This summer when I started to get the pocket photos, before the .27 was released (yes I was among the ones that got it before it was redrawn) I deleted the fingerprints to get rid of the pocket activity due to the non-existing pocket mode. As .27/.28 came with pocket mode I started to use fingerprint again but discovered that face unlock that I had been using was far more convenient and suited me better despite the somewhat lower security rating. I don’t use Gpay, and do not keep top secret stuff on my phone so I’m happy being rid of the fingerprint sensor. The sensitive economic things are protected by pin-code anyway.
So it was not battery time that drove me to ditch the fingerprint sensor, that extra battery time just came as added value for me!
kingbasescu said:
Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.
Click to expand...
Click to collapse
If you notice, the CPU frequency increase occurs randomly after a period of time, not as soon as you turn on the phone, which seems like a bug to me. In addition, the frequency does not settle down again, leading to less standby time available. So I don't really understand how an active fingerprint sensor affects the CPU frequency after a while, and not since the boot.
gerhard_wa said:
This explains why I got better battery hours after I deleted fingerprints! Not that it was bad before, but now it's ridiculously good!
I don’t think this a bug, it probably must be this way in order to wake up screen just by putting the finger on the scanner.
Click to expand...
Click to collapse
If that was the way to be, the frequency should be that high even right after booting.
MysteriousStranger said:
If that was the way to be, the frequency should be that high even right after booting.
Click to expand...
Click to collapse
No, that does not have to be true. I can think of some reasons why CPU speed can't slowdown in order to instantly start the scanner, like for example the more services and apps are started the more CPU power is needed to make the scanner snappy enough. So that may explain why right after boot the CPU may be able to enter a lower idle state. It is in fact true that if you turn off the fingerprint reader you will not have the higher speed at idle state at all, I tested this.
Perhaps there will be a new firmware with a somewhat slower response to the fingerprint scanner that allows the CPU to enter the lower idle state to save battery power. Who knows!
I noticed this as well right from the first firmware update I used (EEA). It's been fixed after upgrading to Android Q's beta modified by Xiaomi.eu, but I don't see much, if any, improvements in battery life, while also witnessing a giant storage performance regression. Hella disappointed.
gerhard_wa said:
No, that does not have to be true. I can think of some reasons why CPU speed can't slowdown in order to instantly start the scanner, like for example the more services and apps are started the more CPU power is needed to make the scanner snappy enough. So that may explain why right after boot the CPU may be able to enter a lower idle state. It is in fact true that if you turn off the fingerprint reader you will not have the higher speed at idle state at all, I tested this.
Perhaps there will be a new firmware with a somewhat slower response to the fingerprint scanner that allows the CPU to enter the lower idle state to save battery power. Who knows!
Click to expand...
Click to collapse
I get your point but the fact is that in never goes into these lower frequencies again, even after unlocking the phone and idling with screen on, which is strange. I don't get it, really. Plus, you are not able to see in real tilme what process is hooking up CPU resources, as you could normally do in older android versions by using an app.
Ok, if the frequency never locks in the high range again and the scanner starts just as snappy I guess you are right that it must be a bug.
Skickat från min MI 9 via Tapatalk
I disabled fingerprint auth, but I don't seen any improvements in battery life.
I notice it on mine as well right now, small cores sitting at 1036 MHz and big ones+super one at 1056 MHz. Can't really put my finger on what triggered it as I've been using the FP sensor all this time and I've checked many times and the cores were at normal clocks (576, 710 and 825). I killed all running apps but it still sat like that until I restarted... at least now I can understand why sometimes my overnight consumption goes from 1% up to 5% even though I always close/kill all apps.
kingbasescu said:
I notice it on mine as well right now, small cores sitting at 1036 MHz and big ones+super one at 1056 MHz. Can't really put my finger on what triggered it as I've been using the FP sensor all this time and I've checked many times and the cores were at normal clocks (576, 710 and 825). I killed all running apps but it still sat like that until I restarted... at least now I can understand why sometimes my overnight consumption goes from 1% up to 5% even though I always close/kill all apps.
Click to expand...
Click to collapse
Try rebooting your device and you will see what the actual idle frequencies should be, then monitor it for a day or two! Can't find what triggers it but It's bugged for sure.
apoklyps3 said:
I disabled fingerprint auth, but I don't seen any improvements in battery life.
Click to expand...
Click to collapse
Reboot your phone after disabling it, otherwise the frequencies stay the same
Hi all. Sorry for my bad english.
I buy xiaomi mi 11 in my country.
But this screen brigthnes not high.
I turn of auto brightness, no any intelligent mode.
But on full screen brightness level, my old phone htc u11 and my wife phone s9+(exynos) more brighter than mi 11.
Why? Everyone in youtube, every web site say/write this phone typcal 700 nit, peek 1500 nits"
.
I can't compare with the models you refer, however, comparing to my old Oneplus 5 and my company Samsung A42, the Mi 11 does a good job.
peak (highest) brightness is only reached in Auto brightness mode and when under strong light
Furma said:
peak (highest) brightness is only reached in Auto brightness mode and when under strong light
Click to expand...
Click to collapse
I try too auto mode. And i try under direct sunlight. Not change. Same result.. :/