FOD does not work because it is not 100% bright - Redmi K20 / Xiaomi Mi 9T Questions & Answers

Hi everyone,
I have been trying a few ROMs, 12.1 to 13, but with none of them the fingerprint sensor works correctly. I can register a new finger all right, but then, when it is time to unlock the phone, the circle illuminating the finger is just not bright enough. It seems to be limited by the global brightness of the display, and in fact if I pump it up to maximum, then the FOD does unlock the device, but with the brightness on automatic no way.
I think there might be something wrong with the firmware, but I flagged latest EU and also latest global but the issue remains...
Any ideas?
Thanks in advance

Related

AOD Dim after update

Hey i received an update for the Always On Display (update number 1.1.22)
after i updated the app i noticed that the AOD is much dimmer in some places than it was before
also i noticed that my girlfriend's s7 AOD is much brighter than mine in the same areas (they were the same before the update)
is there a way to undo the update? (was update through galaxy apps)
Thanks in advance
As far as I know, the AOD dimming is introduced in APD1 and later firmware updates. What is your firmware version ?
Yep, they pretty much ruined the entire feature. Its now too dim to see in anything but outside in full sunlight. Indoors its pretty much just a black screen now. Been a month, they still havent fixed it.
The update is to solve screen burning, this is why is dimmer now.
Cheers.
No, it never burned in since it was always moving. Now it is so dim that i cant even see it, rendering the entire feature useless.
It must be a bug, it cant possible be intended.
Dunno if you tried it but I noticed my AOD accomodates with the lighting condition in the room but im often sitting in the corner where I face the light so when I turn it off I face it to the light so the AOD would be bright. weird habit for now huh hahahah
Still annoys me to hell that they basically took one of the best features of the phone and essentially ruined it (so dark its unreadable indoors, if you dont have a ceiling light shining straight on the sensor). Just by a single little forced software update. Why couldnt they just provide a simple brightness slider in the AOD settings?
Third party AOD apps exist that allow complete brightness control, but sadly none of them run with the samsung AOD "tech" so they all keep the phone hot and running as if fully awake, draining battery more than just the pixels being lit do.
just done the update this morning and I didn't notice difference in the brightness of the AOD. it remained the same. are you sure your dim situation is not caused by some setting, which was reset after the update ? For example, It happened to the fingerprint lock setting in my phone, which become corrupted, unusable after the update. I need to delete the previously saved fingerprint and add a new one again for it to work.
100% certain it was the update. I literally can barely see the AOD indoors anymore. Before the update it was always very bright and vibrant.
Baleur said:
No, it never burned in since it was always moving. Now it is so dim that i cant even see it, rendering the entire feature useless.
It must be a bug, it cant possible be intended.
Click to expand...
Click to collapse
How often does your clock move on your screen, because mine stays stationary unless I turn the screen on and it turn it off again, then it'll change to a different position.

Screen flicker workaround

Hi everyone
I want to share a workaround to all of us who owns a defective S5
Symptom: You unlock your phone and it doesn't show anything. Actually, the phone is working. Capacitive buttons light up and you may heard some activity in the phone
Your phone has a defective screen. There are a lot S5 which have this problem, according to several forums. After several tries, unlock and lock over and over, the screen light up and you are able to use your phone. The problem is when you receive a call and you want to know who is calling you, the screen doesn't illuminate and you won’t be able to know who is.
Here's a workaround which makes your powerful S5 usable and take out from your drawer.
Solution:
The more effective way to fix it is: change defective screen! But sometimes it could cost as much as a new phone, or simply you can't afford it, and it's better to change your phone instead, and you put your S5 in a drawer.
The technical explanation of this problem is: Screen doesn't receive enough electrical current at low brightness levels (maybe the flex is defective, get old, etc)
Most probably the wake up problem exist together with screen flicker at low brightness levels
The wake up problem rises up more in dark environment, when light sensor make low bright screen
The lock screen light up screen, with a dim effect: when you lock the phone, it slowly turn screen off, and when you unlock, it make and effect of dim screen.
When you are is in dark environment, the effect is very slow, preventing the screen illuminate because the technical problem explained before.
When you are in very light environment, you lock screen and sensor light make the screen very brilliant and chances are you defective phone wakes up correctly.
We can use an app which give us complete control over brightness subsystem. I use an app called Velis AutoBrightness:
Once installed from Play Store, it shows a Setting Wizard. Follow the instructions. Below are some notes
• 1/7: Welcome Screen
• 2/7: How bright... Most probably is your phone always have flicker in low brightness. Choose "AMOLED" or "AMOLED bright". By the way choosing any one of those cure always minimum brightness failure!
• 3/7: Choose High sensitivity
• 4/7: On, if you want additional brightness when charging. Irrelevant for this thead. Choose your favorite setting
• 5/7: Same of 4/7
• 6/7: Choose enable: That enable the app
• 7/7: Some additional notes: Press Done
Now important settings: go to Menu > Settings > General: Settings Mode > Advanced
Service Activation settings:
• Disable system handler > ON: When you use Power saving mode, you surely noted screen flicker, which is very annoying, and make unusable power saving mode. By set this ON: Android doesn't set screen too dim; instead Velis have a minimum of brightness set by Wizard 2/7. (Surely you find out that you avoid screen flicker, by setting autobrightness off and slider in 8-10%)
Sensors settings:
• Screen-on sensor value override: Set this value to 30000. Read below this post if you want technical explanation of this setting
After you establish these settings, you'll be able to unlock your phone all the time!
This is the trick: When you unlock your phone, you'll note that the screen is very bright (because Screen-on to 30000) and quickly adjust to the environment light. The failure is that electrical current to screen is defective, and when exterior light is dark, the screen make a dim effect and doesn't light up.
Note to Marshmallow users:
• This app make use of Screen overlay permisions: And marshmallow is very restrict with this kind of app. This is specially true when you are installing an app. All you have to do is deactivate the app in notification screen: press "OFF" button, adjust system brightness upper enough to not flicker the screen, install your app, and activate Velis Autobrightness again
• Because of Doze mode, wake up from this mode may avoid your screen light up, the first time you use your phone. Let 10-15 seconds your phone wake up, lock again, and unlock again, and velis will make its work!
I hope this post make your smartphone usable. I barely apply this trick to two phones, but I think this is a good workaround!
I used this app & the flickering is still available
What worked for me is downgrading the firmware on my g900f all the way back to Android 4.0. My phone came with version 5.0 and I noticed the problem only after I kept installing samsung's system updates. Will report if the problem starts up again but I'm running rooted and running nougat just fine so I don't see a reason to keep upgrading the firmware.
Edit: nevermind, this didn't work
Reyse said:
The technical explanation of this problem is: Screen doesn't receive enough electrical current at low brightness levels (maybe the flex is defective, get old, etc)
Click to expand...
Click to collapse
Does anyone know for sure if it's the flex cable or some capacitors? I notice only the lower half of my screen flickers.. I bet there's a simple electrical fix for it instead of replacing the whoooole display
fbs said:
Does anyone know for sure if it's the flex cable or some capacitors? I notice only the lower half of my screen flickers.. I bet there's a simple electrical fix for it instead of replacing the whoooole display
Click to expand...
Click to collapse
Hello,
Have you change jour battery? If it s old it could cause some issues...
But try to buy a genuine one, I think that your battery must be old now.
Bye
cedouic said:
Hello,
Have you change jour battery? If it s old it could cause some issues...
But try to buy a genuine one, I think that your battery must be old now.
Bye
Click to expand...
Click to collapse
it doesn't make any sense. the lower half of the screen flickers in green even on charger
fbs said:
it doesn't make any sense. the lower half of the screen flickers in green even on charger
Click to expand...
Click to collapse
I noticed that screen only flickers at low brightness when using Boeffla kernel for LOS14 and others based on it.
No issue for the same device with LOS or Stock based kernels.
zlazaar said:
I noticed that screen only flickers at low brightness when using Boeffla kernel for LOS14 and others based on it.
No issue for the same device with LOS or Stock based kernels.
Click to expand...
Click to collapse
you're wrong
I was using los16 with stock kernel for months with flicker everyday
fbs said:
you're wrong
I was using los16 with stock kernel for months with flicker everyday
Click to expand...
Click to collapse
+1 to that , i even went back to stock and the screen flicker appeared and such issues are well known already with samsung amoled panels back in 2014-even some panels from 2018 . So def not kernel related.
I was using los 15.1 and this problem got worse. The phone was barely usable as mentioned by the op. In my case, the screen would start flickering below 60%. Then I switched back to stock marshmallow. I noticed that 100% brightness in los 15.1 is actually only about 70% in the stock rom.
I have been using the phone at 80% brightness for some weeks now and the problem has significantly reduced. But not completely gone, it's much much better. Also, you might want to avoid using dark wallpapers.

Screen Flikering Issue with auto brightness sensor on Zenfone Max Pro M1 6gb

Has anyone noticed Display keeps flickering when auto brightness is on. Even if phone is kept at a fixed position & same amount of light is exposed to the sensor it still keeps flickering. I mean if I'm watching movie it automatically dems or increases the brightness. please confirm how many user experiencing this problem! as per i know it was not resolved from 301 to till 331 update. is it manufacturing defect particularly with specific variant ?
I wouldn't call it it a flicker. More like the auto-brightness feature is so badly programmed that it doesn't transition from dim to bright and vice versa in a smooth, gradual or dynamic manner, like in older and cheaper phones.
My eyes get a shock every few seconds, trying to adjust to the sudden jumps in screen brightness. It's a real pain.
And yes, the issue has persisted through all the OTA updates without any sign of improvement.
Instead of addressing this most basic and "glaring" issue, Asus seems to be intent on introducing bloatware and EIS for the phone and announce it like it's the second coming.
The latest update was supposed to bring with it, system optimization but I don't see any form of basic optimization, let alone calibration, with the screwy display.
I can only guess at Asus' sense of priorities. Or if they're actually blind and/or stupid.
May be it was true that autobrightness was programmed badly manner it was not transist smoothly from dim to bright. But afterall we are facing it at serious level and uptill now asus has not solved yet. I just want to confirm that How many user experiencing screen flicker issue after enabling auto brightness or it was particularly manufacturing defect with specific varient.
its an autobrightness calibration issue,software update will fix it in future,lets hope so
Hello everybody! I found a bug: brightness is flickering even when "auto brightness" ("adaptive brightness") is disabled. Brightness can encrease for few seconds and then decrease to previous level. I read in some reviews that max pro m1 has adaptive brightness which changes depending on content on the screen. I tried to change a lot of display settings, developer settings, i tried to adjust CABC (Content Adaptive Brightness Control) through Nova Launcher (but later I read that CABC controls only autobrightness), and even hard reset. I flashed custom ROMs but it didn't help. Only Lux Dash app helps avoid this bug. But it is not very comfort to use it and I think there must be desicion on firmware level. Did anybody has this problem and any solution? May be somebody has this issue and found custom ROM without flickering brightness?
Sorry for my English, it's not my first language. And thank you for answers!

Fingerprint scanner issues when using Oled Saver

I am very sensitive to PWM. Since there is no Dc Mimming on our phone, I have to use different applications from the Play Store to eliminate screen flicker. They use a black translucent overlay to control the brightness of the screen. On MIUI, this works fine, I have not encountered any problems with this. But on custom firmware when using these applications, the fingerprint scanner does not work. You cannot even add a fingerprint. I am so assuming that on MIUI, all overlays are removed from the screen during fingerprint scanning and the reading mode is turned off due to which unlocking is successful, this is not provided for custom firmware. I hope that the developers will see it and fix it. Thanks!

Mi 9T Ambient Display brightness issues

Hi all, i own two Xiaomi mi 9T and i'm seeing that ambient display on two mi 9t behaves in two distinct and separate ways. Both smartphones have Android 9 miui 11.0.3 no root, both have the automatic display brightness disabled but the ambient display in the first smartphone, with a glass film applied on the display, greatly lowers the brightness of the ambient display (to the point that you do not they see the notifications) and then raise it in case of very strong light. On the other smartphone, however, where there is no glass film applied on the display, the brightness of the ambient display is always at the maximum (I also tried in the dark, same result). Can you please give me some pointers on how to fix it? Thanks so much.
Brightness slider working?
What values are in *#*#6484#*#* > "light sensor"?
sirliam said:
Hi all, i own two Xiaomi mi 9T and i'm seeing that ambient display on two mi 9t behaves in two distinct and separate ways. Both smartphones have Android 9 miui 11.0.3 no root, both have the automatic display brightness disabled but the ambient display in the first smartphone, with a glass film applied on the display, greatly lowers the brightness of the ambient display (to the point that you do not they see the notifications) and then raise it in case of very strong light. On the other smartphone, however, where there is no glass film applied on the display, the brightness of the ambient display is always at the maximum (I also tried in the dark, same result). Can you please give me some pointers on how to fix it? Thanks so much.
Click to expand...
Click to collapse
Take a look here:
https://forum.xda-developers.com/mi-9t/themes/adaptive-brightness-bug-solution-t4043847
I had the same problem and I solved it but you need to modify a file in /persist folder.
This can be done only with a custom recovery or with a file manager with root access.
If you don't want to root your phone you can unlock bootloader (data will be lost), boot official TWRP, go to file manager, copy that file to PC, edit it and put it back to the original location. After this you can relock bootloader if you want to.
SzczufFun said:
Brightness slider working?
What values are in *#*#6484#*#* > "light sensor"?
Click to expand...
Click to collapse
Hi, the first result is of the smartphone with the glass film is: backlight 105 - DAC 157,327271 luxes.
the second is of the one without the film: backlight 470 - DAC 267,922717 luxes
data captured at the same time, same room and same light (artificial)
Could you help me?
sipollo said:
Take a look here:
https://forum.xda-developers.com/mi-9t/themes/adaptive-brightness-bug-solution-t4043847
I had the same problem and I solved it but you need to modify a file in /persist folder.
This can be done only with a custom recovery or with a file manager with root access.
If you don't want to root your phone you can unlock bootloader (data will be lost), boot official TWRP, go to file manager, copy that file to PC, edit it and put it back to the original location. After this you can relock bootloader if you want to.
Click to expand...
Click to collapse
Hi, thanks a lot but they are two new smartphone, less than 2 weeks life, at the moment I don't want to unlock the bootloader ... anyway thanks!
Your sensor readings are correct then, so it's not a problem with it.
.
The best way to fix this in your case will be Factory Reset or Fresh ROM Flash via MiSuite .
SzczufFun said:
Your sensor readings are correct then, so it's not a problem with it.
.
The best way to fix this in your case will be Factory Reset or Fresh ROM Flash via MiSuite .
Click to expand...
Click to collapse
So it's normal to have two such different results at the same time?
If screen film may cause some anomalies to the sensors, why not?
The most acurate results you will get if you rip off screen film, and mesure light intensity without any extra screen protectors.

Categories

Resources