After MIUI update 12.5.2 1st Aug, 2021
Problem noticed:
1.Proximity Sensor not working during phone call and also tested during Xiaomi inbuilt CIT test ( Failed to test cover the screen, constantly showing 5.0).
2. Auto Brightness not working properly day to day usage.
I already generated log file and reported to Xiaomi developers. Request to all do the same if you have same issue..
If anyone having same problem type 'yes' in comments....
Abhik Kumar said:
After MIUI update 12.5.2 1st Aug, 2021
Problem noticed:
1.Proximity Sensor not working during phone call and also tested during Xiaomi inbuilt CIT test ( Failed to test cover the screen, constantly showing 5.0).
2. Auto Brightness not working properly day to day usage.
I already generated log file and reported to Xiaomi developers. Request to all do the same if you have same issue..
If anyone having same problem type 'yes' in comments....
Click to expand...
Click to collapse
I found why this problem is happening now it's fixed. Thank you don't mind.
Abhik Kumar said:
I found why this problem is happening now it's fixed. Thank you don't mind.
Click to expand...
Click to collapse
How did you solve it? The problem is with my phone as well.
otuken said:
How did you solve it? The problem is with my phone as well.
Click to expand...
Click to collapse
Let me know first are you using your phone with proper back cover or without any back cover?
Abhik Kumar said:
Let me know first are you using your phone with proper back cover or without any back cover?
Click to expand...
Click to collapse
I use it with the cover that came with the phone.
otuken said:
I use it with the cover that came with the phone.
Click to expand...
Click to collapse
Try to confirm with Xiaomi inbuilt CIT test from kernel version just click on repeatedly 4 times and it will open with new window name with CIT. Then go to point 22 and read and try. After try this I will tell you next.
I have done the proximity test before and applied it. There was no change. I'm currently using it without a case and it seems to be ok.
otuken said:
I have done the proximity test before and applied it. There was no change. I'm currently using it without a case and it seems to be ok.
Click to expand...
Click to collapse
If problem till persist then do a hard reset this will solve your problem. Don't use any default cleaner.
Despite throwing different roms, it did not improve. I guess the sensors are the problem.
otuken said:
Despite throwing different roms, it did not improve. I guess the sensors are the problem.
Click to expand...
Click to collapse
Try to do hard reset. https://www.mi.com/in/service/productfaq/
Source: HardReset.info
First method:
Power off the phone.
Next press and hold Volume Up + Power button.
Then select "wipe data/factory reset" using Volume buttons to scroll options, and Power button to confirm.
Now choose "Yes -- delete all user data".
After that accept operation "reboot system now".
Finito!
It doesn't make sense because a different rom was thrown and it still didn't improve.
Related
Hello everyone. I've just installed few CM11-based roms (MIUI and AOKP) and noticed a strange thing. When I am just locking my phone and trying to unlock it after a while, screen doen's wake up. It just stays black and there is no reaction for power button. I have to reboot my phone by removing battery so that is really annoying. Stock was working fine, i hadn't notice anything like that. Anyone know the solution?
Mardrom said:
Hello everyone. I've just installed few CM11-based roms (MIUI and AOKP) and noticed a strange thing. When I am just locking my phone and trying to unlock it after a while, screen doen's wake up. It just stays black and there is no reaction for power button. I have to reboot my phone by removing battery so that is really annoying. Stock was working fine, i hadn't notice anything like that. Anyone know the solution?
Click to expand...
Click to collapse
Violently press the button over and over. It worked for me.
Sent from my awfully named device.
RedLedLight said:
Violently press the button over and over. It worked for me.
Sent from my awfully named device.
Click to expand...
Click to collapse
I found another solution i think. I just set up minimal CPU freq. over 400mhz and it's working fine. At least under the charger. You have to press it every single time or once and it's working fine then?
E: Without charger the same issue. Not solved.
I have the same problem and I think it has something to do with the proximity sensor.
Sounds interesting. Why do you think so?
Btw. I don't know why but I am happy that I am not alone with this problem.
Because:
Proximity Wake-Up support – prevent accidental wake-up of device by checking to see if proximity sensor is blocked (eg. Device is in a bag or pocket).
Click to expand...
Click to collapse
I think, here is some XPM bug. Just my thought
lookynator said:
Because:
I think, here is some XPM bug. Just my thought
Click to expand...
Click to collapse
What do you think about checking older version of miui then? I mean v4 or something...
Mardrom said:
What do you think about checking older version of miui then? I mean v4 or something...
Click to expand...
Click to collapse
I've never tried.
lookynator said:
I have the same problem and I think it has something to do with the proximity sensor.
Click to expand...
Click to collapse
Hello, I have the same issue on SGS3 with CM11 M11 (M10 too). Have U found some solution for that ?
Dik
PROBLEM
After flashing to AOSP 6 I have problems with waking the screen up.
1. After or during the call
2. After longer sleep
It can take up to a minute to wake up. Usualy around 10-20 seconds after multiple presses (single press can sometimes doesn't wake the phone).
NO PROBLEMS WHEN:
1. I manualy sleep the screen, and press power again after a moment - I can bring it to a wake up state without any problems.
2. If the phone is connected through USB - there is also no problem to instantly bring the wakeup screen.
3. There is also no problem to bring the wakeup screen with adb
Code:
adb shell input keyevent 26
I was expecting it to be some sort of sensor problem, as it persists to other roms, even coming back to 5.1.1 which previously worked flawlessly in this department.
I've tried this: http://forum.xda-developers.com/opt...mpting-to-fix-broken-sensors-mm-e975-t3297566 without any results. I've also tried restoring factory settings.
Any ideas?
ZPZG said:
PROBLEM
I was expecting it to be some sort of sensor problem, as it persists to other roms, even coming back to 5.1.1 which previously worked flawlessly in this department.
Click to expand...
Click to collapse
What does CPU-Z think of your sensor data? it's being represented correctly?
blackbird5308 said:
What does CPU-Z think of your sensor data? it's being represented correctly?
Click to expand...
Click to collapse
The sensor as far as I know is binary, so either something is in proximity or not, and as that it works correctly under any system.
After reverting to stock 4.4.2 the problem does not appear.
Installing AOSP 6 again - the problem returns.
ZPZG said:
The sensor as far as I know is binary, so either something is in proximity or not, and as that it works correctly under any system.
After reverting to stock 4.4.2 the problem does not appear.
Installing AOSP 6 again - the problem returns.
Click to expand...
Click to collapse
well, i don't really know, my proximity sensor has been working well since first time i went 6.0 AOSP, even when no other sensor was working at all
blackbird5308 said:
well, i don't really know, my proximity sensor has been working well since first time i went 6.0 AOSP, even when no other sensor was working at all
Click to expand...
Click to collapse
Honestly I don't know what is the problem, but in every thread concerning wakup issues and E975 the sensors are blamed. The physical sensor is working properly as I am not having any problems running stock 4.4.2.
Hello guys,
I'm facing some weird problems with my phone,
×All installed apps automatically restart or FC for at least once or twice.
×Music player stops when screen goes off.[Solved]
Also I want to ask, it is normal in emui that we can clear a sticky notification because I'm able to clear all notifications including those which are not supposed to be? Is it normal?
I did reset the settings but no luck
Please reply if you know anything about these issues.
Soheir said:
Hello guys,
I'm facing some weird problems with my phone,
×All installed apps automatically restart or FC for at least once or twice.
×Music player stops when screen goes off.
Also I want to ask, it is normal in emui that we can clear a sticky notification because I'm able to clear all notifications including those which are not supposed to be? Is it normal?
I did reset the settings but no luck
Please reply if you know anything about these issues.
Click to expand...
Click to collapse
It is a problem many people including me are facing
Only we have to wait for new updates
Sent from my DUK-L09 using Tapatalk
anil2653 said:
It is a problem many people including me are facing
Only we have to wait for new updates
Click to expand...
Click to collapse
What about sticky notifications? Is it also common?
There is a solution that you need to try:
Go to settings - battery - Click the gear icon on right hand top - UNTICK "close excessively power-intensive apps"
If you are on b183, it is common that apps crash
PalakMi said:
If you are on b183, it is common that apps crash
Click to expand...
Click to collapse
There is a B183? I'm on B140 and it is the latest update for me
There's a b183
Yeah. Me too. Frequent app crashed. Like fb, WhatsApp and the worse is on games like mobile legend during war. I'm and sometimes my whole team dead there when that happens
Tried wiping data?
Soheir said:
Hello guys,
I'm facing some weird problems with my phone,
×All installed apps automatically restart or FC for at least once or twice.
×Music player stops when screen goes off.
Also I want to ask, it is normal in emui that we can clear a sticky notification because I'm able to clear all notifications including those which are not supposed to be? Is it normal?
I did reset the settings but no luck
Please reply if you know anything about these issues.
Click to expand...
Click to collapse
If there's an update, just update your phone
sniperlife:D said:
Tried wiping data?
Click to expand...
Click to collapse
Not doing that yet. Since it's kinda a hassle to setup back the phone
Form last three days I did not face any FC or app restart. I did nothing it automatically fixed.
Soheir said:
Form last three days I did not face any FC or app restart. I did nothing it automatically fixed.
Click to expand...
Click to collapse
That's great.
Can you report back again in 3 days?! Just to see if it gets fixed by time
Soheir said:
Form last three days I did not face any FC or app restart. I did nothing it automatically fixed.
Click to expand...
Click to collapse
Same here. It got solved automatically.
Sent from my Honor 8 pro using Tapatalk
PalakMi said:
That's great.
Can you report back again in 3 days?! Just to see if it gets fixed by time
Click to expand...
Click to collapse
Sure...
K.khiladi said:
Same here. It got solved automatically.
Sent from my Honor 8 pro using Tapatalk
Click to expand...
Click to collapse
Thats strange...without updating or clearing anything problem solved. sometime these softwares are too much to understand.
PalakMi said:
That's great.
Can you report back again in 3 days?! Just to see if it gets fixed by time
Click to expand...
Click to collapse
How it is fixed..i am still facing the issue
Also confirm what built are you using
Sarfraz888 said:
How it is fixed..i am still facing the issue
Also confirm what built are you using
Click to expand...
Click to collapse
It will be fixed with time.
B183
PalakMi said:
It will be fixed with time.
B183
Click to expand...
Click to collapse
Is it impacting all the regions or only specific country/model?
shashank1320 said:
Is it impacting all the regions or only specific country/model?
Click to expand...
Click to collapse
From various feedbacks, almost all regions are affected
after each lock when i turn the screen on with double tap or power button screen is unresponsive for good 3 seconds. This started happening after the latest camera fix update. When if i use aod and use the fingerprint through the aod this doesnt happen. tried reboot and factory reset with fresh install (no backups) tried safe mode. Same thing happens.
S20 plus exynos.
Yup happening to me too (s20+ exynos). For me the time of unresponsiveness is around 1-2 seconds. Happened after the latest update.
Yes, have been facing the same issue since "ATCH" update.
Yeah has been driving me nuts. Same problem.
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Glad to see it's not only my device. Waiting for fix.
I have similar situation
I'ne noticed the same after the last update.
Chris_c81 said:
Yeah has been driving me nuts. Same problem.
Click to expand...
Click to collapse
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
Chris_c81 said:
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Click to expand...
Click to collapse
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
anfederin said:
I have similar situation
Click to expand...
Click to collapse
Mine is Exynos
sjandroiddeveloper said:
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
Click to expand...
Click to collapse
Is there any channel to communicate this bug to Samsung? Anyone know?
Chris_c81 said:
Is there any channel to communicate this bug to Samsung? Anyone know?
Click to expand...
Click to collapse
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
sjandroiddeveloper said:
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
Click to expand...
Click to collapse
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
turn off the battery optimized for apps: com.samsung.android.biometric.
Go to Settings>Apps>Select "Special Access" from three dot menu>Optimise Battery Usage>select All from drop down menu>Search for "com.samsung.android.biometric"> Turn it off and Restart.
Click to expand...
Click to collapse
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Did accordingly as above.
For a moment it felt like the issue is resolved!
But after checking several times I can confirm the issue still exists.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Sent from my SM-G986B using Tapatalk
verynuclear said:
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Click to expand...
Click to collapse
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Virgo_Guy said:
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Click to expand...
Click to collapse
Have you restarted the phone? It didn't work until I restart mine.
Sent from my SM-G986B using Tapatalk
verynuclear said:
Have you restarted the phone? It didn't work until I restart mine.
Click to expand...
Click to collapse
Ofcourse I did. In fact restarted one more time since it didn't resolve after the first restart, post disabling the optimization.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
I did this already and while it feels like fingerprint is faster, unfortunately this is a screen issue. You see if the screen is off and i put the finger in the correct spot it always scans my finger without any lag. The issue is occurs when -
a) I have unlocked the phone using above way, then the screen becomes unresponsive right after unlocking.
b) The screen is off and i either press the power button or double tap to wake, then the screen will be unresponsive and its during this time the fingerprint scanner doesn't scan (because the scanner doesn't know it needs to scan since the touch is unresponsive)
so TL;DR its not a FP scanner issue.
I am quiet sure Samsung is already addressing this issue for next update.
S21fe updated to UI5.
Couple of issues.... Fingerprint reader sometimes doesn't work when phone hasn't been used for some time. When it happens I need to double tap the screen to wake it up and then scan my fingerprint again.
Also "back" gesture (where I swipe up from the right bottom of the screen) sometimes instead of going back brings up the list of background apps.
Both issues very annoying.
Anyone else experienced anything similar?
Try clearing the system cache. Double check all settings. If that flaws things get more complicated...
A factory reset may be needed, but hard to say if it will resolve the issues. Someone will need to try the latter if the former doesn't work. A global reset of settings is a less drastic option but it may not be enough and still take a lot of time.
This is one reason why I spurn upgrades on a platform that's fulfilling its mission. Lol, I'm still using UI 1.5, no glaring issues.
Unfortunately with latter versions an upgrade may resolve flaws in earlier post >1.5 variants. Tough choice once you are on Android 11 as there's no roll back on stock Samsung's for that. I wasn't locked into using 11 on my N10+'s and never will load it. 12 is even worse.
Roll back is an option for you if bootloader wasn't upgraded too. Eventually Samsung will fix it if it's a firmware/software glitch but don't hold your breath for that
blackhawk said:
Try clearing the system cache
Click to expand...
Click to collapse
With each major update, I always clean the system cache from the recovery !
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
That may not be enough if going from 11 to 12, etc.
Rule #1 - if the OS is fast, stable and fulfilling its mission let it be! You have little to gain and a lot to lose. Although there was a big security hole in 12, not sure if it was patched already or if the patch is in what you just install. Oddly that hole isn't in 9-11.
Gookill is a mess...
I have the same problem with fingerprint unlocking. It simply doesn't work (if I press the side button, it works). Some hours ago I wiped the system cache and after that, I didn't notice the described problem. I will see in the next few hours.
Now I changed "Fingerprints -> Show icon when screen is off" to "Tap to show" instead of "On always on display" which was the default after the upgrade to Android 13.
UPDATE: The phone still has the same problem. Sometimes it simply doesn't allow it to unlock with a fingerprint. The screen is locked as hell. Only the side button unlocks it.
If you go to Lock screen>Always On Display>Show always, does that solve your problem? Mine was set to "show for new notifications" only and the fingerprint icon would disapperar after locking it.
Mine was set to "Show for new notifications". As you suggested, I changed it to "Show always" and we will see, how it works. In my opinion, it is better to show display only when something happens. But something changed and problems occurred.
Report: it didn't help. I have found out that the issue appears if the phone is locked for a while and then a notification comes. This is the reason why this problem exists also while using Android Auto. It creates a notification when it connects ... and then the phone can be unlocked with a fingerprint until the side button is pressed. I'm sure this is a bug that didn't exist before the upgrade to Android 13.
no such issues here with the eu version. definitely an upgrade in every way.
After 3 days with Android 13 on snapdragon variant, only two minor issues found here : slow charging (2h20 from 0 to 100, less than 2h before) and an "unauthorized action due to modified device" screen when rebooting, disappearing by touching "OK" button. Don't know what is unauthorized but... well. I was rooted before, now stock unrooted and relocked bootloader. It doesn't seems to lock something, everything I use is working.
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
d0j0m0j0 said:
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
Click to expand...
Click to collapse
The recent update with the December security patch seens to have resolved this issue for me.
Edit: scratch that, still not fixed...
Edit2: turning off lock scrern mods in Galaxy MaxHz seems to help.
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
How does one do that?
xda-eh said:
How does one do that?
Click to expand...
Click to collapse
It's on the boot menu on Samsung's.
blackhawk said:
It's on the boot menu on Samsung's.
Click to expand...
Click to collapse
You're referring to accessing the recovery mode as explained here?
xda-eh said:
You're referring to accessing the recovery mode as explained here?
Click to expand...
Click to collapse
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
blackhawk said:
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
Click to expand...
Click to collapse
The link I provided and the one you did refer to the same thing. Only difference is my link also provides a way to do it via ADB. In any event, thanks for your response.