Database Develop

MI9 Fingerprint CPU Frequency bug

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

Constant 120fps refresh rate ?

Greetings all,
The phone doesn't run 120fps all the time like for instance during the usage of google chrome, etc. You can check this by heading over to https://www.testufo.com/
On my OnePlus 7 Pro, we can enable constant 90fps via adb.
Was wondering if anyone has figured out a way to get get it working on our Rog Phone 2 ?
Cheers.

Won't this drain the battery?

JazonX said:
Won't this drain the battery?
Click to expand...
Click to collapse
No it doesn't, no noticeable drain on the OnePlus 7 pro.

Is it because the phone has variable framerate to save battery? Or because the display isn't capable of keeping 120hz?

Yes the same here.. Only after switching on the 120 hz in the topbar menu I have 120 hz also in the browser. I hope they will fix this.

el4nimal said:
Is it because the phone has variable framerate to save battery? Or because the display isn't capable of keeping 120hz?
Click to expand...
Click to collapse
Guess its a bug because when you activate it from the quick settings you get 120 fps all around. On my oneplus 7 pro, by default , on chrome and other apps it switches back to 60fps too but you can activate system wide 90fps via adb
geffect said:
Yes the same here.. Only after switching on the 120 hz in the topbar menu I have 120 hz also in the browser. I hope they will fix this.
Click to expand...
Click to collapse
yea, hope they get it fixed soon, sometimes after reboot it goes back to 60 or when you open and close the app. Whats the use of having 120fps if you only get to use it on the homescreen and asus's stock browser lol.

Hi, I'm thinking of getting the Asus rog 2 ultimate edition when it becomes available soon. And I would like to know if the 120 hz force mode could be activated like one plus 7 pro.
Since I had the oneplus 7 pro I had the 90hz force mode and I can't use any device without feeling the choppy effects of the 60hz. Be it iPhone or note 10 plus. And I hope someone has managed to find a way to activate 120hz ask the time.

I think it is a bug of Chrome Stable.
You can use 120hz continuously with Chrome Beta and Dev version.

You can choose, via settings, the screen mode: 60Hz, 90Hz, 120Hz. If you have 60Hz (default choice), of course the browser will run at 60Hz, no wonder about that. And, of course, the screen will drain less battery.
From the settings, you can choose to run ALWAYS at 120Hz. In some BATTERY test, tho, they showed how 120Hz ALWAYS will drain more battery. So, they suggested to use 120Hz mode only with X-Mode, so you can use it for games.
But, if you wanna use it ALWAYS, so even when you surf on the web via browser, you can activate 120Hz mode from Video Settings, in order to be Always on 120Hz.

Sorry for the noob-ish question, but is there any significant difference between a 90hz panel and a 120hz panel? I know that it's a leap from a 60hz to a 90hz panel, just wanted to know if there was any noticeable difference between the 90hz and 120hz.

dudeperfect said:
Sorry for the noob-ish question, but is there any significant difference between a 90hz panel and a 120hz panel? I know that it's a leap from a 60hz to a 90hz panel, just wanted to know if there was any noticeable difference between the 90hz and 120hz.
Click to expand...
Click to collapse
Not much difference, but if I am going to keep it on 90hz then what is the point of getting the device over the ROG or 1+7. Also the battery saving isn't much you will probably get 30 mins ~ 1 H SOT vs a 60hrz constant refresh rate if I recall correctly. Any way it comes down to the type of device usage.
I will advise to try different settings and stick with the one that suites you. Personally I like to keep it at 120hz unless I am short on battery.

Rashad83 said:
Not much difference, but if I am going to keep it on 90hz then what is the point of getting the device over the ROG or 1+7.
Click to expand...
Click to collapse
Plenty. Heck, I'd take this at 60Hz vs the 1+7 (or most any phone, for that matter), because there's plenty to love about the phone. Aside from the lack of U.S. support, of course...

Question Fhd+ vs WQHD+

Hi all, I have been thinking lately about moving to WQHD resolution instead of the FHD that I'm already on. Can someone please share the battery impact and the actual screen sharpness? I have always maintained that the smaller the screen the more difficult it is to discern the actual difference between FHD and WQHD. Surely, the difference is day and night on larger screen sizes i.e. 50 inches and above. Is it really the case on our screens too? I'm on adaptive refresh rate and plan to keep it as is.

amirage said:
Hi all, I have been thinking lately about moving to WQHD resolution instead of the FHD that I'm already on. Can someone please share the battery impact and the actual screen sharpness? I have always maintained that the smaller the screen the more difficult it is to discern the actual difference between FHD and WQHD. Surely, the difference is day and night on larger screen sizes i.e. 50 inches and above. Is it really the case on our screens too? I'm on adaptive refresh rate and plan to keep it as is.
Click to expand...
Click to collapse
Not much of a difference in battery , may be like 30 mins of less SOT.
Gpu takes a bit of more load , and thus the overall graphics might be like 5-10% slow .
Thats my opinion, might be different for others

The difference is nearly imperceptible, wouldn't worry too much about both WQHD+ and adaptive refresh rate

Buying a phone at this price but not using the highest possible resolution is quite useless

why cant you just TRY IT YOURSELF?

sesnut said:
why cant you just TRY IT YOURSELF?
Click to expand...
Click to collapse
You could NOT have used the CAPS and I would have still understood your point!

amirage said:
Hi all, I have been thinking lately about moving to WQHD resolution instead of the FHD that I'm already on. Can someone please share the battery impact and the actual screen sharpness? I have always maintained that the smaller the screen the more difficult it is to discern the actual difference between FHD and WQHD. Surely, the difference is day and night on larger screen sizes i.e. 50 inches and above. Is it really the case on our screens too? I'm on adaptive refresh rate and plan to keep it as is.
Click to expand...
Click to collapse
Hi.
I tried both WQHD+ and FHD+ with adaptive refresh rate on for a few days each - but I couldn't discern any significant differnce in battery life with day to day usage. I'm not saying there wasn't any... common sense dictates that there must be some, but I wansn't able to appreciate it.
I was very hard pressed to tell the differnce between the two resolutions on my screen as well. When I went down to HD+, I could immediately detect the drop in quality. But between FHD and WQHD I couldn't tell initially. Over time, i leatnt to discern the differnce up close (really close) becasue I knew what to look for - but the difference was not very big. So I tested it out on my family members, and not a single person could tell the difference with confidence (none are tech nerds) - all they said is "Wow! nice screen, what do you want me to look for? Looks the same as before..."
But this was all done in the first 2 weeks since I bought the phone, so usage was erratic and frenzied. I hadn't settled into a regular routine with the phone, it being all new and shiny - installing and uninstalling new apps, tinkering around etc - so i don't think I can honestly testify as to the battery life difference between FHD and WQHD.
But I can definitely tell that my eyes found it very difficult to tell the difference in quality, even today. So I just kept it on FHD+ and forgot about it till I came across your post. Maybe it's time to try out the experiment again with a more settled down phone... as I sit here typing this on WQHD resolution, trying to imagine if the FHD+ looked any different 15 minutes ago.

amirage said:
Hi all, I have been thinking lately about moving to WQHD resolution instead of the FHD that I'm already on. Can someone please share the battery impact and the actual screen sharpness? I have always maintained that the smaller the screen the more difficult it is to discern the actual difference between FHD and WQHD. Surely, the difference is day and night on larger screen sizes i.e. 50 inches and above. Is it really the case on our screens too? I'm on adaptive refresh rate and plan to keep it as is.
Click to expand...
Click to collapse
I tried it and didn't see much difference so keeping it at wqhd and adaptive.
Same with 4g and 5g in my area.
Everything is on adaptive. 5g and wqhd.
Go on and use it. That's why you paid for the phone, if you don't use the feature s what's the point?

Just use the best possible resolution. No point getting a phone like this and turn things off is how i look at it.

70% of the time, on my phone: I'm just messaging/calling or using the browser to view text-based content with a few images here and there.
30% of the time: HD Video, photos, camera, video-calls, etc.
So, I do this:
(1) Remove Animations (under Accessibility or just use Finder/search to locate it) -- because I don't need
(2) Force Dark in Developer Options (goes away after a reboot, so just reactivate this).
(3) Keep the phone in 720p60fps, full-temperature Comfort Shield, Power Saving mode, AOD off, Limit CPU to 70%, Decrease brightness by 10%, etc.
(4) Use a Bixby Routine to go into and come out of this low-quality mode as desired.
(5) I have all deviceidle and other power saving settings turned off.

nixnixnixnix4 said:
70% of the time, on my phone: I'm just messaging/calling or using the browser to view text-based content with a few images here and there.
30% of the time: HD Video, photos, camera, video-calls, etc.
So, I do this:
(1) Remove Animations (under Accessibility or just use Finder/search to locate it) -- because I don't need
(2) Force Dark in Developer Options (goes away after a reboot, so just reactivate this).
(3) Keep the phone in 720p60fps, full-temperature Comfort Shield, Power Saving mode, AOD off, Limit CPU to 70%, Decrease brightness by 10%, etc.
(4) Use a Bixby Routine to go into and come out of this low-quality mode as desired.
(5) I have all deviceidle and other power saving settings turned off.
Click to expand...
Click to collapse
Now your phone will always stay dark on reboot. You're welcome.

Question Dynamic Refresh Rate?

Hi! I am on xiaomi.eu miui 12.5.9. Is there any way possible to set the refresh rate to 60hz when it idles for a moment?
Some custom rom has this feature (e.g. project elixir, aex etc) where you can set the minimum refresh rate is 60hz and maximum at 120hz, when the phone idles the display automatically drops down to 60hz. It is a great battery-saving feature, so I was wondering is there any way to do this in MIUI?

a safe haven said:
Hi! I am on xiaomi.eu miui 12.5.9. Is there any way possible to set the refresh rate to 60hz when it idles for a moment?
Some custom rom has this feature (e.g. project elixir, aex etc) where you can set the minimum refresh rate is 60hz and maximum at 120hz, when the phone idles the display automatically drops down to 60hz. It is a great battery-saving feature, so I was wondering is there any way to do this in MIUI?
Click to expand...
Click to collapse
I thought the refresh rate already dynamic? Try set it to 120hz and turn on refresh rate from developer option... You will find the display rate fluctuate between 30,60,120...

Nazri786 said:
I thought the refresh rate already dynamic? Try set it to 120hz and turn on refresh rate from developer option... You will find the display rate fluctuate between 30,60,120...
Click to expand...
Click to collapse
Nope it doesnt, it always stays at 120hz.

a safe haven said:
Nope it doesnt, it always stays at 120hz.
Click to expand...
Click to collapse
Sorry, unaware this is redmi note 10 forum... On poco x3 it had that dynamic refresh rate..

a safe haven said:
Nope it doesnt, it always stays at 120hz.
Click to expand...
Click to collapse
It must show other options as well.

does realme gt master edition support dynamic refresh rate? can we get that feature via an ota update?

Hello, from my experience using custom ROM, Redmi Note 10 pro screen doesn't fancy enough for using variable refresh rate. When setting to 60 Hz - 120 Hz, The display always stay in 120 Hz if it register touch not depends the content we see like other phone. And drop to 60 Hz in +/- 1 seconds after last touch input

Question How To Fix ? OnePlus 10 Pro Refresh Rate Stays 120Hz Always

Hi Everyone,
Can i anyone help OnePlus 10 Pro Always Stays 120Hz Never Went Down Even Static Wallpaper , It shows only 120hz and my battery draining faster
if i turn on normal mode ie 60hz then reducing but video 60hz fine , after static photo also 60hz

jack_ssl said:
Hi Everyone,
Can i anyone help OnePlus 10 Pro Always Stays 120Hz Never Went Down Even Static Wallpaper , It shows only 120hz and my battery draining faster
if i turn on normal mode ie 60hz then reducing but video 60hz fine , after static photo also 60hz
Click to expand...
Click to collapse
There's already a thread I've answered to this.. You need to search more buddy

dladz said:
There's already a thread I've answered to this.. You need to search more buddy
Click to expand...
Click to collapse
i cant find it thats why i asked in this forum , please help me to find it

jack_ssl said:
Hi Everyone,
Can i anyone help OnePlus 10 Pro Always Stays 120Hz Never Went Down Even Static Wallpaper , It shows only 120hz and my battery draining faster
if i turn on normal mode ie 60hz then reducing but video 60hz fine , after static photo also 60hz
Click to expand...
Click to collapse
Does it stay locked at 120hz even with high brightness?

@ashrr oneplus 10 pro battery drain issue how to fix it . i am using oxygen os

ashrr said:
Does it stay locked at 120hz even with high brightness?
Click to expand...
Click to collapse
@ashrr i tested now , in high brightness frame rate dropping into 1hz. y in low or little medium brightness it stays locked at 120hz

dladz said:
There's already a thread I've answered to this.. You need to search more buddy
Click to expand...
Click to collapse
Can you share the link of the thread?

jack_ssl said:
@ashrr i tested now , in high brightness frame rate dropping into 1hz. y in low or little medium brightness it stays locked at 120hz
Click to expand...
Click to collapse
That's normal then, at higher brightness the screen will drop all the way down to 1hz to save battery but at lower brightness it will stay at 120hz or drop to 60hz in some apps.

faryal said:
Can you share the link of the thread?
Click to expand...
Click to collapse
Here you go

Maybe AutoHz in store

ashrr said:
That's normal then, at higher brightness the screen will drop all the way down to 1hz to save battery but at lower brightness it will stay at 120hz or drop to 60hz in some apps.
Click to expand...
Click to collapse
it's not normal, it should be variable even at medium and low brightness.