Related
Does anyone know of a way to remove the proximity sensor drivers or shut it off completely my screen just goes black during a call and i need to use the keypad during calls i have tried all the proximity apps on market and it has no effect, have tried calibration etc odin firmware updates to the point i killed my phone just got it back from repair and was told it needs a new chip to rectify the problem.
I have spent weeks going through forums for a solution and i know on my brothers sgs 2 it has a setting in the menu to turn it off.
This seems to be a common problem with no resolve so im looking for someone to resolve this problem and make alot of people happy.
We all no As these phones age this will be more and more common.
Techies get ur teeth into this or even software writers make An app n earn some cash,
This would b a great ego booster for someone to say i solved that when no one in the world could.
Thanks...........looney
Sent from my GT-I9000 using XDA App
Mh? Why not pressing the home button during call.
Screen is enabled then...
Anyway MIUI got this option to switch it off.
Don't know if this setting is available in Stock ROMs.
screen should go back on when you move your head out of the ~5cm sensor radious. if it is not happening there are two possibilities:
- something wrong with firmware -> reflash phone with pure unrooted samsung firmware and check if problem persist
- someting is wrong with proximity sensor -> use warranty and send it to service center with proper description of the problem
Thanks for the replys the home button won't work as the proxy is up the spout had it checked the chip is blown, when u press the home key won't work as the phone is trying to find the proxy then eventualy it will crash and force close.
No software update will do it as its a hardware fault unless it turns it off so will have a look at the one you suggested.
There is def a stock version but i fear it is only on the s2 to turn blank screen off il check my bro's firmware, till then keep the suggestions coming in thanks....
Sent from my GT-I9000 using XDA App
Here is a possible solution. Check the + 3.7 volts at this point, if there is no tension, then feed it thither with a jumper
SADист said:
Here is a possible solution. Check the + 3.7 volts at this point, if there is no tension, then feed it thither with a jumper
Click to expand...
Click to collapse
Thanks for the tip. Where can i get 3.7 V from? (which part of the MB)? Is there a way of hardware disabling the sensor? the software testers report 0.7 mA leakage on a sensor (which is faulty anyways)
lusjash said:
Thanks for the tip. Where can i get 3.7 V from? (which part of the MB)?
Click to expand...
Click to collapse
You can do this:
Hi All,
My proximity sensor isn't triggering during calls (Possilbly at all?) causing me to accidentally put people on hold.
(very annoying! at least make a tone so I know I hit the button)
Is there a switch for that?
What's weird is that I don't see a HW test for the proximity sensor in the diagnostics screen (tapping on kernel version)
Edit -> settings -> system apps -> phone -> incoming call settings -> proximity sensor is ON.
Can someone whose proximity sensor is working download a sensors test app like https://play.google.com/store/apps/details?id=com.wered.sensorsmultitool&hl=en
and tell me if that detects your proximity sensor distance correctly? (or whatever app you want, just tell me which one).
- Frank
Go to Settings - About phone and tap 5 times on Kernel tab. You will get into test menu. There you can to test and calibrate proximity sensor.
sergmarin said:
Go to Settings - About phone and tap 5 times on Kernel tab. You will get into test menu. There you can to test and calibrate proximity sensor.
Click to expand...
Click to collapse
I don't see it. What is the test called?
What Rom are you running? I'm on 8.0.10.0
See pictures below. Test menu works on any firmware.
sergmarin said:
See pictures below. Test menu works on any firmware.
Click to expand...
Click to collapse
Well,that's damned odd.
My proximity sensor item is missing.
https://drive.google.com/open?id=0B6qmkujf4DlWVVFWVXBxTkJoRTA
xx
ChodTheWacko said:
Well,that's damned odd.
My proximity sensor item is missing.
https://drive.google.com/open?id=0B6qmkujf4DlWVVFWVXBxTkJoRTA
Click to expand...
Click to collapse
Just looked at mine and I have prox sensor as number 9. Sounds like you may need to flash an updated build.
I updated to developer rom and proximity appeared and was working.
I then re-updated to stable rom (8.0.12.0 i.e latest) and it dissapeared again!
ChodTheWacko said:
I updated to developer rom and proximity appeared and was working.
I then re-updated to stable rom (8.0.12.0 i.e latest) and it dissapeared again!
Click to expand...
Click to collapse
You already have the answer you're looking for. Guess the sensor is broken in the stable build. In this case, you may have to wait for the next stable release or use an alternate ROM.
ChodTheWacko said:
I updated to developer rom and proximity appeared and was working.
I then re-updated to stable rom (8.0.12.0 i.e latest) and it dissapeared again!
Click to expand...
Click to collapse
Confirm proximity sensor missing in 8.0.12.0
Unfortunately, it is also missing in 8.2.1.0 stable
On Chinese 8.2.3.0 and the settings are missing from the CIT list also ... with that said I don't depend on it anyways lol. Just checking things.
for some thick case the proximity sensors might have problem... need to reboot phone with case on to "register" the case thickness...
hi mi mix fans , I came through lot of applications,proximity sensor tests, procedures, secret codes etc . to get solution for "screen off during call and not on automatically" but i found the real solution in this is .. remove back cover which almost users use . , tpu transparent also and see whether it work during call ..yes,finally got solution. check yourself all test works properly and screen on during call when device is away from ear..if not ?? pls consider to clean sensor ..
Wanted to test it. I can see the test, but not sure how to test it. I still don't.
So I tried to the front microphone test to learn how to use these tests...
But it scared the s**! out of me. It's such a haunting noise! Is that normal?!
I'm on global stable, CIT proximity option doesn't show too. I think my sensor is bugged by my cover since when the device isn't covered the sensor works fine.
jaekry said:
Wanted to test it. I can see the test, but not sure how to test it. I still don't.
So I tried to the front microphone test to learn how to use these tests...
But it scared the s**! out of me. It's such a haunting noise! Is that normal?!
Click to expand...
Click to collapse
Yes, such an annoying noise.
i have same problem i just updated phone after proximity sensor not work why xiaomi not try before update this f*cking fw.
What I observed is after resetting when I tested it I came to know that sensors sensi
What I observed is after resetting when I tested it I came to know that sensors sensitivity distance increase up to an inch but starts dropping again as I move object in front of sensor 8 to 10 times and is reduce to 1 cm finally which is very less if you hold mobile in left hand ear but it works on right hand ear as proximity sensor is placed left of mobiles front side.I think it is a software problem which xiaomi should look in to.Sensor keeps on calibrating till it reduces distance to 1cm from nearly 1 inch that is 3 cms.This is very shameful for xiaomi that after so many years of experience they have not yet resolved this for Mi A1.
My proximity sensor also isn't working. I've tried to do this test we find on kernel tab, but I couldn't test it, it shows no options for me to calibrate or sth. Help me please!!
Same issue here. Phone just turns black, when I am calling people - difficulties to restart the display afterwards. Using Lineageos 16 - no chance to tab the kernel there. Dialing * # * # 64663 # * # * shows no results. Wandering, if this is a hardware or a software issue.
Have you checked or compared your compass against older or other devices?
My new Note9 compass is about 10° off (counter clock wise), a problem my old samsung devices did not have. Note 8 and S8+ for example are all around +-2°.
I can easily notice this in google maps, because if I turn on the function which turns the display view according to the direction you are looking, its always off.
How exact is your Note9 compass compared to Note8 (or other devices)?
TML1504 said:
Have you checked or compared your compass against older or other devices?
My new Note9 compass is about 10° off (counter clock wise), a problem my old samsung devices did not have. Note 8 and S8+ for example are all around +-2°.
I can easily notice this in google maps, because if I turn on the function which turns the display view according to the direction you are looking, its always off.
How exact is your Note9 compass compared to Note8 (or other devices)?
Click to expand...
Click to collapse
Let me know what app to use, I can check it against my wife's note 8 if you like.
Sent from my SM-N960U1 using Tapatalk
Limeybastard said:
Let me know what app to use, I can check it against my wife's note 8 if you like.
Sent from my SM-N960U1 using Tapatalk
Click to expand...
Click to collapse
I use GPS Status & Toolbox from EclipSim since years... Nice program!!
Besides the comparison to Note8, is your Note9 accurate?
Another issue is that my Note9 looses it's Compass Calibration frequently. You can check this also with GPS Toolbox (there is a point for compass calibration) or the service menu (*#0*# in the dialer, the sensors, if it shows a blue "3" besides the compass it is calibrated).
Inside the service menu, can you please also test the function "grip sensor"? On my device it "detects" only when I touch the bottom of my device, it triggers even when my finger is a few mm away from the bottom. Does your device the same?
Thank you!!
Sent from my [device_name] using XDA-Developers Legacy app
TML1504 said:
I use GPS Status & Toolbox from EclipSim since years... Nice program!!
Besides the comparison to Note8, is your Note9 accurate?
Another issue is that my Note9 looses it's Compass Calibration frequently. You can check this also with GPS Toolbox (there is a point for compass calibration) or the service menu (*#0*# in the dialer, the sensors, if it shows a blue "3" besides the compass it is calibrated).
Inside the service menu, can you please also test the function "grip sensor"? On my device it "detects" only when I touch the bottom of my device, it triggers even when my finger is a few mm away from the bottom. Does your device the same?
Thank you!!
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'll do this after I finish my grave yard shift.
Sent from my SM-N960U1 using Tapatalk
The grip sensor behaves similar to yours. If I place my hand near the USB charger socket it will engage without touching it.
In respect to the service menu, I chose sensors test and looked under magnetic . I didn't see a blue "3". I did see a round black circle with a red line inside of it?
Sent from my SM-N960U1 using Tapatalk
Limeybastard said:
The grip sensor behaves similar to yours. If I place my hand near the USB charger socket it will engage without touching it.
In respect to the service menu, I chose sensors test and looked under magnetic . I didn't see a blue "3". I did see a round black circle with a red line inside of it?
Sent from my SM-N960U1 using Tapatalk
Click to expand...
Click to collapse
Thank you!! I have been at a local store today and all of the devices there show similar behavior with the touch sensor.
The redine tells you that your compass is not calibrated, a calibrated one would have a blue line with a "3" beneath it.
Calibrate your compass while at this screen (make the "8-pattern" with the phone in the air and rotate it along all 3 axis until you have the 3 and a blue line).
Then, you can check two things: how long does the phone stays calibrated (normally it should for a long time, until next reboot or even more), and if the heading it shows is right.
For me it's constantly off at about 10 degrees, and it jumps weirdly around.
Also, after 1-2h my calibration is gone and I would have to recalibrate...
On my Note 8 this was much better!
What do other Note 9 users say, how is your compass accuracy or calibration persisting?
Sent from my [device_name] using XDA-Developers Legacy app
TML1504 said:
Thank you!! I have been at a local store today and all of the devices there show similar behavior with the touch sensor.
The redine tells you that your compass is not calibrated, a calibrated one would have a blue line with a "3" beneath it.
Calibrate your compass while at this screen (make the "8-pattern" with the phone in the air and rotate it along all 3 axis until you have the 3 and a blue line).
Then, you can check two things: how long does the phone stays calibrated (normally it should for a long time, until next reboot or even more), and if the heading it shows is right.
For me it's constantly off at about 10 degrees, and it jumps weirdly around.
Also, after 1-2h my calibration is gone and I would have to recalibrate...
On my Note 8 this was much better!
What do other Note 9 users say, how is your compass accuracy or calibration persisting?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've been trying the figure 8 and rotating my phone to get calibration under the test menu to no avail . Tried for minutes.
Sent from my SM-N960U1 using Tapatalk
Limeybastard said:
I've been trying the figure 8 and rotating my phone to get calibration under the test menu to no avail . Tried for minutes.
Sent from my SM-N960U1 using Tapatalk
Click to expand...
Click to collapse
So you want to say that you don't get any calibration at all? Because this works for me every time. My. problem is that the compass is off even if calibrated, and that the calibration does not stay very long until I would again have to calibrate...
It could be that you have to make really weird movements for the calibration to work, you can also try a restart!
If you get never ever any calibration then I would suggest you to swap your device, or hope that it is a software error.
I'm also unsure if I should swap because of this, or if it could be fixed with an update in the future.
For that it would be really helpful to know if there are users out there, whom Note 9 compass works flawless... The its most probably NOT software/firmware related, and we would have to exchange devices...
So please @All, let us know how well your compass works!!
Sent from my [device_name] using XDA-Developers Legacy app
TML1504 said:
So you want to say that you don't get any calibration at all? Because this works for me every time. My. problem is that the compass is off even if calibrated, and that the calibration does not stay very long until I would again have to calibrate...
It could be that you have to make really weird movements for the calibration to work, you can also try a restart!
If you get never ever any calibration then I would suggest you to swap your device, or hope that it is a software error.
I'm also unsure if I should swap because of this, or if it could be fixed with an update in the future.
For that it would be really helpful to know if there are users out there, whom Note 9 compass works flawless... The its most probably NOT software/firmware related, and we would have to exchange devices...
So please @All, let us know how well your compass works!!
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ok got it calibrated after a another few mins and also turning phone upside down and doing the figure of 8. Did the same to wife's note 8 and placed them next to each other. Once calibrated, they both show slightly different lines on the graphic service menu , where the 3 is. My note 9 for example line was straight and the note was slightly at a approx 10 degree angle to the left.
https://photos.app.goo.gl/QhZUtpH6xEo9Ar9NA
Sent from my SM-N960U1 using Tapatalk
Hello guys, asus rog phone doesnt activate 2nd led flash. I think it only for lighting armor case. Is there any way to activate it without the case?
vimalcv said:
Hello guys, asus rog phone doesnt activate 2nd led flash. I think it only for lighting armor case. Is there any way to activate it without the case?
Click to expand...
Click to collapse
Not that I know of, like you say, it's only for official case
reg66 said:
Not that I know of, like you say, it's only for official case
Click to expand...
Click to collapse
I hope xda devolopers try to figure it out
Second light you see is not a flash light, it's a RGB light. For the lighting armor case, this light turns on to make writing and logo on back of case light up in different colours. So yeah mobile has only 1 flash light.
Doesn't the case have an NFC chip in it that activates the light? I've never dealt with NFC, but would it be possible to mimic that chip data with a stand alone chip that you can use to trick the phone?
Mr_Mooncatt said:
Doesn't the case have an NFC chip in it that activates the light? I've never dealt with NFC, but would it be possible to mimic that chip data with a stand alone chip that you can use to trick the phone?
Click to expand...
Click to collapse
Yeah, I'm theory, but it would only be an rgb led, not a flash...
reg66 said:
Yeah, I'm theory, but it would only be an rgb led, not a flash...
Click to expand...
Click to collapse
Good point. Use it for mood lighting! Lol
reg66 said:
Yeah, I'm theory, but it would only be an rgb led, not a flash...
Click to expand...
Click to collapse
RGB can make white flash (just combine all red green and blue).. hence can be used for mood lighting, party strobing, camera flash etc
Anyone able to fine any solutions for the 2nd rgb light to work without the case?
vimalcv said:
Hello guys, asus rog phone doesnt activate 2nd led flash. I think it only for lighting armor case. Is there any way to activate it without the case?
Click to expand...
Click to collapse
I found it currently it was quite evil design and almost undetectable till someone give me free rog phone 2 to open and investigate .u need a very weak n small mgnet bar (enough to keep a small needle hanging), and nfc chip just to trigger for awhile (hardware ver)
Another option u can try , set your aura light mode on
then go std calculator dial .012345+=
Then go menu test rgb ( software version) ihope someone can create a consol to activate hidden rog item including the extra usb c port too
Pum0nss said:
I found it currently it was quite evil design and almost undetectable till someone give me free rog phone 2 to open and investigate .u need a very weak n small mgnet bar (enough to keep a small needle hanging), and nfc chip just to trigger for awhile (hardware ver)
Another option u can try , set your aura light mode on
then go std calculator dial .012345+=
Then go menu test rgb ( software version) ihope someone can create a consol to activate hidden rog item including the extra usb c port too
Click to expand...
Click to collapse
It worked after put on Aura Sync light in Armoury Crate, with .12345+= in Calculator App and select single test, Aura and Bump Red LED Test, Aura and Bump Blue LED Test and Aura and Bump Gren LED Test.
We need to figure out a way to make use of this LED outside of the test menu.
Reverse engineer SMMI test app maybe?
I exported java resources from SMMI Testing app and found the parts responsible for the Aura bump test. I am too amateur to understand the code and its dependencies. Can anyone help build an app to do this externally and in more controlled way from these resources?
I hope there is some solution for this soon! Having a RGB light on phone can give a very unique lighting conditions for photography which I would love to test
Nkz=- said:
I hope there is some solution for this soon! Having a RGB light on phone can give a very unique lighting conditions for photography which I would love to test
Click to expand...
Click to collapse
This app uses root access to let you control the ASUS ROG Phone II's RGB logo
Looking for a way to customize the illumination pattern of the RGB logo on the ASUS ROG Phone II? Check this rooted app out!
www.xda-developers.com
Works on stock. Requires root tho.
Another option (I think) could be asking someone with the lightning case to clone the NFC chip, post the data here and You could make Your own NFC chip - might also work.
Pum0nss said:
I found it currently it was quite evil design and almost undetectable till someone give me free rog phone 2 to open and investigate .u need a very weak n small mgnet bar (enough to keep a small needle hanging), and nfc chip just to trigger for awhile (hardware ver)
Another option u can try , set your aura light mode on
then go std calculator dial .012345+=
Then go menu test rgb ( software version) ihope someone can create a consol to activate hidden rog item including the extra usb c port too
Click to expand...
Click to collapse
Hey, can you share data to write to a custom NFC chip so that i can mimic as if the case is on? I'll arrange a magnet. If I can just mimic the NFC case, I'll be able to control the RGB LED!
4869_aptx said:
Hey, can you share data to write to a custom NFC chip so that i can mimic as if the case is on? I'll arrange a magnet. If I can just mimic the NFC case, I'll be able to control the RGB LED!
Click to expand...
Click to collapse
Surely it's easier to flash twrp and root, then install the custom RGB app, no? I can walk you through the process if you're not sure how to...
To enable and disable your Asus Rog phone 3 led flash (WITHOUT ROOT AND OR COMPUTER) you will need the following applications and settings to be on.
YOU MUST ALSO BE ON ANDROID 11+, ANDROID 10 NEEDS USB DEBUGGING FOR SHIZUKU AS THERES NO WIRELESS DEBUGGING IN ANDROID 10 FOR ASUS ROG PHONE 3.
Apps:
Shizuku (https://shizuku.rikka.app/)
aShell (https://gitlab.com/sunilpaulmathew/ashell)
Settings you need on to do this:
System lighting must be set up and enabled
Developer options must be on and you must enable:
USB Debugging
Wireless Debugging
Step 1: After you have done the prep, start Shizuku's pairing service and type your pairing code found inside wireless debugging into the notification Shizuku sends.
Step 2: Start Shizuku service and grant permission to aShell inside Shizuku.
Step 3: Open aShell and type "setprop vendor.asus.aura.CSCmode 1"
And just like that, you now have your secondary flashlight enabling when you enable system lighting and it disabling when you disable system lighting. Furthermore it does persist outside of apps after stopping Shizuku service and disabling both wireless debugging and usb debugging, however I do not know if it persists when your phone restarts or boots up again. And. This is a rootless method that is easy to do.
Now to disable the led flash you repeat step 1 and 2 but now instead of typing "setprop vendor.asus.aura.CSCmode 1" you instead type "setprop vendor.asus.aura.CSCmode 0" inside of aShell. Simple as that. Now it's off. Enjoy your custom lighting.
Everything after this line is just me explaining how I found you can enable this feature
Just now when I discovered my Asus Rog phone 3 even had a working led flash using smmi test I was fairly maddened that I couldn't get control over it because you need a specific case to unlock it, just seems unfair to pay for a feature that's locked behind a paywall.
And as such I took it upon myself to find a method without root using ADB to unlock this feature and I found it.
The way I even managed to find how the led can be turned on or off is by using any apk viewer/editor and selecting the smmi test system app and viewing its contents inside assets/[ASUS-I003DD]-config.xml and at line 46 I noticed this:
<TEST_ITEM Disable="0" ErrorCode="2186" Name="Aura_Bump_RedLED_Test" Param="getprop vendor.asus.aura.CSCmode;setprop vendor.asus.aura.CSCmode ;1" AutoTest="0" />
"setprop vendor.asus.aura.CSCmode ;1", and it looked an awful lot like a adb command you would use to set a system property, considering the led turns on when you run the test I knew it was correlated to that adb command that it sends.
By using Shizuku "https://shizuku.rikka.app/"
And "aShell" https://gitlab.com/sunilpaulmathew/ashell
Aswell as wireless debugging I now had a adb app that I can use to get system access to parts I otherwise couldn't get, I ran the following command inside aShell "getprop" which shows me all the system properties and I saw once again. "vendor.asus.aura.CSCmode"
Using what I understood about smmi test's command I ran "setprop vendor.asus.aura.CSCmode 1" and low and behold, the second led flash started to work. It's synced to the Asus logo at the back that glows, if the Asus logo glows red, the flashlight will be red, so on and so forth. Furthermore, you can control the brightness of this light so that's even better and it's quite bright at max. Better yet, you don't need root, thus making it much simpler to get and still pass safetynet, whilst enabling a otherwise disabled feature. I haven't tested if it disables itself after restart BUT it does stay for the whole time you use your phone, to disable the second led, just type "setprop vendor.asus.aura.CSCmode 0" and now it's off.
I replaced the Mi 9T Pro amoled display with a new original one, but the fingerprint doesn't work. The fingerprint sensor is still working, the problem is related to the calibration. I tried using the "Activity launcher" app to calibrate the sensor, I chose "In display fingerprint" then "SPMT", but this process failed when it asked to "Calibrate, put the FLESH CHART then click next" with error "0x14 the number of bad pixel is abnormal".
I know that "FLESH FLAT" means that I need to use a mirror on the fingerprint, but what does "FLESH CHART" mean?
Thank you
Here some screenshots and the difference between the two displays: https://drive.google.com/folderview?id=1lJ0_T0kMW3kOl-2Piy8vC9VUv2cUhLeG
Hello , There are issues with the miui 12 update. Is your screen really 100% original?
sacha2506 said:
Hello , There are issues with the miui 12 update. Is your screen really 100% original?
Click to expand...
Click to collapse
I think that it's the original one, here a link https://drive.google.com/folderview?id=1lJ0_T0kMW3kOl-2Piy8vC9VUv2cUhLeG to a photo gallery with the photo comparison between the two displays.
There is an official procedure to perform the fingerprint calibration?
Thank you
according to your photos it is not the original screen but an adaptable one. the reference is not the same look carefully ...
sorry I don't know the procedure ...
sacha2506 said:
according to your photos it is not the original screen but an adaptable one. the reference is not the same look carefully ...
sorry I don't know the procedure ...
Click to expand...
Click to collapse
Thank you for your reply. I bought this spare parts on eBay. It was described as original AMOLED
About the reference, do you mean the code that is in the bottom of the screen on the gray tape?
At this point I will try to change it again... There is a shop where I can buy original spare parts? I know that this one is a good shop https://dragon-tt.com/Products.aspx?gid=95 but you need to wait some days for the shipment because they ship from China.
Thank you
I think that of your link is good however I do not know the difference between the beginning of the serial number JA and JC or JB ... Anyone know the difference or is it just a year or a place of production?
sacha2506 said:
I think that of your link is good however I do not know the difference between the beginning of the serial number JA and JC or JB ... Anyone know the difference or is it just a year or a place of production?
Click to expand...
Click to collapse
I think that I will buy a new one on dragon-tt.
Do you think that ask to the reseller for the beginning of the serial number it's important?
Thank you
Yes Il think ...
sacha2506 said:
Yes Il think ...
Click to expand...
Click to collapse
Dragon-tt give me this reply:
This item is 100% original new.
It recognize the fingerprint .
You can not start calibration process ,because you have no tool.
Only xiaomi have the tool to calibrate the finger print.
Our screen comes with JA.
I think it is not a problem.
Click to expand...
Click to collapse
it still seems weird to me. but if so then Xiaomi should be able to fix the problem with an update.
Have you tried to factory reseting the device?
Please let me know
Grazma said:
Dragon-tt give me this reply:
Click to expand...
Click to collapse
I see that there are some topics with reports of the same problem, that is: difficulties with the fingerprint scanner after replacing the broken screen of an MI 9T / K20D [PRO].
A summary of the situation:
Until MIUI 11, the MI 9T / K20D [PRO] worked normally even when their screen was replaced by non-original screens with only 5 multitouch points, sometimes described as "tft" or "oled", including the fingerprint scanner.
Most of the screens available on internet sellers are of these types, and vendors often insist that they are original. The easiest way is to check the number of multitouch points, if it is not 10, it is not original.
After upgrading to MIUI 12, the fingerprint scanner of the MI 9T / K20D [PRO] equipped with these screens no longer works, restarting the device whenever trying to register a fingerprint. This is not a calibration problem.
The only solution found so far is to replace the non-original screen with an "AMOLED" screen, with 10 multitouch points, which is either original or at least has characteristics similar enough to the original to work.
This topic has a good explanation on that subject https://forum.xda-developers.com/k20-pro/help/miui-12-fingerprint-unlock-defective-t4122135
I hope it helps
As Thoriq said, have you tried factory resetting it? i had the same problem when i replaced the screen on my cepheus with a bad quality one and that fixed it
[Solved]
rodrimax10 said:
As Thoriq said, have you tried factory resetting it? i had the same problem when i replaced the screen on my cepheus with a bad quality one and that fixed it
Click to expand...
Click to collapse
Hi guys, after reading the last update in this thread, I tryed to install a clean Global ROM on my Mi 9T Pro, and it works, but due to the cheap quality of the new AMOLED, the recognition works 1 time on 8.
I followed this guide step by step, and if you open this link from a smartphone, turn on the "Desktop Mode" otherwise you will see a blank page: https://c.mi.com/oc/miuidownload/detail?guide=2 - to follow the guide you need a Windows PC -.
If you need to unlock the device, first you will need to turn on the "Developer options", go into the "Mi Unlock status" menu, and bind the Xiaomi Account with the unlocker. Of course, you will need the Xiaomi Account password.
Ater the unlock, according to the guide that I linked before, the device will reboot, but sometimes it stops on the coloured "MIUI" logo. So after 5 minutes without any change, I turned off the device pressing the power button, and then it rebooted correctly. After the first reboot, it asked me to add again the Xiaomi Account password, because the device was already paired with an account. At this point it booted, and I turned off the device before selecting the system language, and I continued to follow the linked guide from the STEP 3.
The nice thing is that the fingerprint works again, unfortunately the bad quality of the display cannot be fixed without replacing it again.
Thank you for your help guys.
Grazma said:
[Solved]
Hi guys, after reading the last update in this thread, I tryed to install a clean Global ROM on my Mi 9T Pro, and it works, but due to the cheap quality of the new AMOLED, the recognition works 1 time on 8.
I followed this guide step by step, and if you open this link from a smartphone, turn on the "Desktop Mode" otherwise you will see a blank page: https://c.mi.com/oc/miuidownload/detail?guide=2 - to follow the guide you need a Windows PC -.
If you need to unlock the device, first you will need to turn on the "Developer options", go into the "Mi Unlock status" menu, and bind the Xiaomi Account with the unlocker. Of course, you will need the Xiaomi Account password.
Ater the unlock, according to the guide that I linked before, the device will reboot, but sometimes it stops on the coloured "MIUI" logo. So after 5 minutes without any change, I turned off the device pressing the power button, and then it rebooted correctly. After the first reboot, it asked me to add again the Xiaomi Account password, because the device was already paired with an account. At this point it booted, and I turned off the device before selecting the system language, and I continued to follow the linked guide from the STEP 3.
The nice thing is that the fingerprint works again, unfortunately the bad quality of the display cannot be fixed without replacing it again.
Thank you for your help guys.
Click to expand...
Click to collapse
DEAR SIR I HAVE THE SAME PROBLEM AND FOLLOWED your procedure but no result.
I bought an AMOLED screen manufactured by Samsung, complete with frame, supports 10 touch points, with color quality and contrast very similar to the original screen of my Mi 9T. At first it is a good display, the seller has guaranteed that it is of Original / OEM quality. Here is the link to the part I bought: https://www.aliexpress.com/item/4000156095854.html
The only problem is that biometric recognition does not work on MIUI 12! The sensor registers my fingerprint but the phone does not unlock with it. I've tried to downgrade to MIUI 11 and it didn't work either. Any solution?
same situation but the one I got is branded OLED instead of an AMOLED one. I wish there's a way to calibrate the fingerprint as I registered the same finger thrice for accuracy but it still doesn't detect properly.
ClockUpEx said:
same situation but the one I got is branded OLED instead of an AMOLED one. I wish there's a way to calibrate the fingerprint as I registered the same finger thrice for accuracy but it still doesn't detect properly.
Click to expand...
Click to collapse
You can try to follow what I have done here. But, if you didn't bought the original spare part, you will probably be unable to use the fingerprint scanner due to the bad quality of the display.
It worked either you replaced original (10 or 5 finger touch support) Theres a tricky way to make it done.
Xda user from iran n india successfull fod