Related
Hey guys. Im having a problem with the proximity sensor on my sensation 4g. It was working fine when i bought it. It shut the screen off while calling, but now it does not. I thought that maybe rooting it would fix the problem by getting a custom rom, but i would like some input before i go rom exploring on this phone. I assume its a software issue because i havnt dropped the phone or anything along that line. Any Help would be highly appreciated. I also am looking for the dialer codes that would lead you into a test mode to test the functions on the device. If anyone knows of a code, I would appreciate to learn what it is. thank you for your help.
Make sure Proximity sensor is enabled in Settings > Call Settings > Additional Settings.
thank for your reply. I checked the settings and the only thing that shows up is Caller Id settings and Call waiting. Oh and i downloaded a market app that would show me all the sensors that work on my phone, and the light and proximity sensors both come up with an unknown error. Could it be something from the gingerbread update?
Did anyone figure this out? I have the same problem and its getting pretty annoying.
Me too...:-(
Hello,
I am having the same problem. Earlier, I thought that it was a ROM issue, however, after changing multiple ROMs, it seems to be firmware issue.
On my sensation, I found out that it is related to the back light for the soft keys (home, menu, back and search).
I can get it to work if I turn on pocket mode in Settings > Sound and then restart (once or twice). It will work until next restart.
I have installed AndroSensor from market and it shows one of the 3 messages
Proximity Sensor: Waiting for Event
Proximity Sensor: Unknown Error.
Proximity Sensor: 3.5in
Also, I am getting exceptional battery life which makes me wonder whether phone uses both the cores or if anything else is wrong with the phone.
I am using Energy ROM (3rd Oct).
Any feedback?
Thanks,
Baiju
baijunagori said:
Hello,
I am having the same problem. Earlier, I thought that it was a ROM issue, however, after changing multiple ROMs, it seems to be firmware issue.
On my sensation, I found out that it is related to the back light for the soft keys (home, menu, back and search).
I can get it to work if I turn on pocket mode in Settings > Sound and then restart (once or twice). It will work until next restart.
I have installed AndroSensor from market and it shows one of the 3 messages
Proximity Sensor: Waiting for Event
Proximity Sensor: Unknown Error.
Proximity Sensor: 3.5in
Also, I am getting exceptional battery life which makes me wonder whether phone uses both the cores or if anything else is wrong with the phone.
I am using Energy ROM (3rd Oct).
Any feedback?
Thanks,
Baiju
Click to expand...
Click to collapse
This is interesting b/c I just noticed I have the same problem, too. I do not check the pocket mode because I want to save some battery life. I did get the proximity sensor working during calls "sometimes". And it's really hard to define this "sometimes" b/c I cannot identify the pattern or reproduce the scenario.
My solution to this issue is that If it's not working, I recharge the battery until full, do a reboot, maybe reboot twice, and it is "sometimes" "fixed" by itself. In my case, after doing that, the proximity will work for a while (again, it's hard to determine how long), and just stopping working all the sudden.
I hope there is a easier fix, maybe a app, that would reset the proximity so we can apply it when the sensor does not work.
Hi I just realized the cause, it's because the battery % mod from UOT kitchen. I removed it and everything is fine now. Apparently the UOT kitchen's setting has problem.
I have 2 sensation 4g. One doesn't have any problem with Energy ROM. For the other phone, I went back to Factory settings and reinstalled original TMobile ROM. I still have problem with that one. I have contacted t-mobile and asked for a replacement. It is something with the hardware I suppose.
Baiju
hello
I got the exact same problem and i do many rom/kernel change to figure out this problem but i just can't .
Yungyeh could you explain more how do you solve it ? thks
toowave said:
hello
I got the exact same problem and i do many rom/kernel change to figure out this problem but i just can't .
Yungyeh could you explain more how do you solve it ? thks
Click to expand...
Click to collapse
I guess nothing fancy.
As I've known so far, there are several causes, which can be divided into two categories: Hardware and software .
If your device came with this issue, with a stock rom installed, maybe applied some updates, then you shouldn't wait to call the (HTC/T-mobile?) customer service. Have a exchange or replacement is the only way to correct the hardware issue.
If it's a software issue, i.e. it worked before with a stock rom, but now it fails sometimes after flashing a custom rom, you may go with the following solutions.
Situation One: If the custom rom is fresh installed, charge your device until battery full, stay in charge mode for another 1 - 2 hours, complete power off and on at least twice (three times maybe, make sure the "fastboot" in the power settings is off). Do not install any mod until your rom settles for a few hours. Sometimes the sensor does not work will simply because the cache goes wrong. If after waiting for a few hours and the problem still persists, you may want to check your custom rom's instruction and make sure you've followed every steps.
Situation Two: If the proximity sensor does not work all the sudden, especially after doing a reboot, you should first clear your data for phone app (or any other apps that use the proximity sensor), and then boot into recovery to clear all your cache. After wiping your cache, you have to do what situation 1 instructed because your device is just like a fresh installed one.
Situation Three: If your proximity sensor fails to work after applying a mod, especially some mods cooked from the UOT kitchen, revert back to your previous backup. DO NOT APPLY THAT MOD ANYMORE!!! Try some other mods that work for you and that is friendly to your proximity sensor. This situation also applies to if your flash an inappropriate kernel. Revert back to your previous backup is the only solution.
If none of the situations described above works for you, then I am out of clue. Changing to other custom rom or kernel usually does not work. You may try that but I doubt it will resolve this issue. It may be just your bad luck that the proximity sensor of your device goes to its end. I sincerely hope it not the case.
my sensors are not working!!
accelerometer
gyroscope
light
magnetic field
orientation
proximity
All not working...
Was using HyperSensation-CM7.1-v0.8, then decided to update the kernel, faux newer one, then lost the ability to rotate the phone..
So, did a manual wipe, then super wipe, restored my backup, and still no sensors,
wiped again and tried a diffrent rom nothing changed,
wiped again tried arhd 3.6.7 with stock kernel and faux kernel,
tried cm7 with the kernel it comes with or the newer one and still nothing...
at what level does the software talk to these sensors, is there a 100%way to wipe the phone and start over? i have never had any issue like this before!
Would reverting back to the original rom via fastboot help at all versus what i have done?
if someone has any ideas pm me, its a little bit easier then catching a response here since this is the most popular rom in the world lol, but ill still be reading
I'm having the same probpem. I don't really mess around with Roms or anything and I have 2 sensation 4g that do the same thing. And I believe is an htc problem.
having the same iseu with proximity and light sensor.
Do you have an solution yet ?
yungyeh said:
Hi I just realized the cause, it's because the battery % mod from UOT kitchen. I removed it and everything is fine now. Apparently the UOT kitchen's setting has problem.
Click to expand...
Click to collapse
I`m having the same problem with both proximity and light sensors.They work occasionally but not for to long.Have you found a solution for this?
It's April of 2012 and I have found NO answers or fixes!!!!!!!!!!
Same sensor problem on my sensation.
If I reboot the phone in a dark room, booth sensors are working (I don't know if it's correct when the proximity sensor shows only 3,5 or 0 inches, but it works)
When I go to a lighted room, the proximity sensor stops to work and the light sensor needs more time to measure the illumination.
If I reboot the phone into lighted room, the sensors didn't work.
It is possible to simulate a "dark room" by covering the sensors with a finger ;-)
It is not easy to decide if the error is located into software or the sensors are "overloaded". For finding out a solution I have ordered new flex main board which should contain booth sensors. Hope it helps ^^
schand99 said:
Same sensor problem on my sensation.
If I reboot the phone in a dark room, booth sensors are working (I don't know if it's correct when the proximity sensor shows only 3,5 or 0 inches, but it works)
When I go to a lighted room, the proximity sensor stops to work and the light sensor needs more time to measure the illumination.
If I reboot the phone into lighted room, the sensors didn't work.
It is possible to simulate a "dark room" by covering the sensors with a finger ;-)
It is not easy to decide if the error is located into software or the sensors are "overloaded". For finding out a solution I have ordered new flex main board which should contain booth sensors. Hope it helps ^^
Click to expand...
Click to collapse
@schand99: The Flex/Main Board actually isn't the problem. It is an HTC software/hardware related problem. I have 2 Sensation's here now, one is rooted and unlocked entirely and the Proximity and Ambient Light Sensors and the Capacative Backlights on the touchpad DO NOT WORK. FYI, the touchpad lights work in cooperation of the Ambient Light Sensors: If there is any light under 90.0 Luxes (this is how the sensor measures light) the backlights will come on. If there is anything over 90.0 Luxes, the backlights will stay off. This is based on the fact that you need light in a totally dark environment, or you do not need light as you can see the touchpad and it is not that dark.
It is DEFINITELY not a hardware issue as there are some temporary fixes that will bring them back to life, but usually after a reboot, they are both dead again.
I am curious if your new flex/main cable would do the trick or not. I have tested the sensors chipsets independently and they work fine, there is just something that block their functionality on a software end.
mariosaraylian said:
It is DEFINITELY not a hardware issue as there are some temporary fixes that will bring them back to life, but usually after a reboot, they are both dead again.
I am curious if your new flex/main cable would do the trick or not. I have tested the sensors chipsets independently and they work fine, there is just something that block their functionality on a software end.
Click to expand...
Click to collapse
My report about main flex board changing:
After changing the board booth sensors are working fine. I have tested the functionality of the sensors also on different ROM's like stock rom, OrDroid and CoinDroid. No problem until now. It makes not a difference anymore if I power on the phone into dark room or on a sunny place.
BUT!
I don't recommend to do this by yourself. It is verry difficult to do this work !!
It is my profession to do this kind of work.
AND
to change the board was the right method for fixing the sensor-problem on my HTC Sensation. I had to unlock the hboot 1.27.xx by using the "beer drinking" method. So perhaps I have damaged the sensors by doing this...
schand99 said:
My report about main flex board changing:
After changing the board booth sensors are working fine. I have tested the functionality of the sensors also on different ROM's like stock rom, OrDroid and CoinDroid. No problem until now. It makes not a difference anymore if I power on the phone into dark room or on a sunny place.
BUT!
I don't recommend to do this by yourself. It is verry difficult to do this work !!
It is my profession to do this kind of work.
AND
to change the board was the right method for fixing the sensor-problem on my HTC Sensation. I had to unlock the hboot 1.27.xx by using the "beer drinking" method. So perhaps I have damaged the sensors by doing this...
Click to expand...
Click to collapse
@schand99: That's very strange that it could be the SAME hardware problem for all of these people that are complaining about this issue. I wonder if is some sort of production issue they have. The strange part is that it is not just for the lot of hardware issued for the USA only, it is also in other parts of the world also.
I did a hardware exchange with mine at the TMOUS store and the "new" one I have now is working fine thank God.
I told them that the TMOUS ICS RUU OTA upgrade broke the sensors LOL!
Thanks for your feedback!
Guys!
Do you experience proximity sensor issues while answering calls on OP7P?
For me while I'm on calls. The display comes on and gets disturbed and get pressed by my ears all the time.
Also any idea of where the proximity sensor is located on OP7P?
Thanks ?
Yes, I'm having the same issues. While I'm on calls I often activate the notifications pulldown. It would be nice to know how to fix this.
If you pull down the notification shade, the sensor is located just above the fifth icon on the first row. IE behind the screen.
If you pull the shade all the way down it is above and between the third and fourth icons. Easiest way to describe it. Put your thumb over that area with auto brightness on to watch the slider move.
Annoying while on a call that the screen comes on.
I'm experiencing the exact same issue with the caller app.
I also tried to make a flip cover to turn screen on or off with a proximity sensor detection app and it didn't work either.
I search a little in engineer mode (*#808#) and found that there is multiple proximity sensor, the IR sensor work quite well but it doesn't seem to be the default one.
The default one seems to be the ultrasonic sensor which works really bad.
There is also a "TP" proximity sensor which seems to be a near field detection which seems to work if I move my hand near the screen.
The sad thing is that in dedicated app to use or test proximity sensor (and in antutu or else) only one proximity sensor is listed (The ultrasonic one I guess) so you cannot switch to use the one which is working well.
Isn't this in the wrong place? Shouldn't it be in the Questions and Answers section?
Mods?
Probably just here looking for a mod to improve the situation
Actually I was going to open a new thread in Q&A when I found this one with the same subject and problem.
Do you think I need to open a new thread?
Is any of you experiencing the same issue as I described in my answer?
did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people
I tried to with no luck but as I explain in my first message the IR sensor is only used when screen is off (that's why it could help with double tap to wake)
But when screen is on another or couple another sensors are used and you can't calibrate them.
I think ultrasonic sensor is used when screen is on.
Do someone tested proximity sensor with any app on the play store? (Like proximity sensor test)
Put it on a table and check if it's working, mine is absolutely not. If I hold it like I was about to phone it works a little but it's not impressive.
Since I got 9.5.7 (EU version) earlier this evening screen turn off when I make a call.
I'm having this issue since 9.5.8... It's very annoying and I'm really disappointed, I often turn on airplane mode during a call... I tried to calibrate but it doesn't work.
I'm very very frustrated
schmeggy929 said:
did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people
Click to expand...
Click to collapse
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8
dallasnights said:
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8
Click to expand...
Click to collapse
This...
I've been having issues with phone calls but more so with pocket issues.. When I had the 6t pocket mode kept the phone neutral but this phone doesn't seem to have an accurate prox sensor.. Is there a way to activate a pocket mode?
Sent from my [device_name] using XDA-Developers Legacy app
Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
pinzarualex said:
Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.
Click to expand...
Click to collapse
Let us know if it's going to fix the issue wiping and resetting everything please!!!
Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
But I have had this issue since release.. Do you a link to this information? If that's the case maybe someone can look into the firmware and see if it's minor tweak that can fix it?
Sent from my [device_name] using XDA-Developers Legacy app
Jack_Sparrow_ said:
Let us know if it's going to fix the issue wiping and resetting everything please!!!
Click to expand...
Click to collapse
Of course it didn't fix anything...
Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app
j0hnee said:
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have reported this to Funk wizard on the OOS support thread and he said he cannot reproduce it anymore on the latest test build, so... We have to wait for next firmware release and see if that is indeed the case
My Pixel 3's proximity sensor reads 0cm after android 10 update(using Sensors Multitool), and double tap to wake and lift to wake not working.
I've search on the internet and I read the post of "FIXED - Android 10 - Sensors Bug". and also tried using proximity sensor reset or calibrate app, but all seem not working.
In my case, all other sensors works perfectly(Active Edge,Ambient Light Sensor, Auto-brightness, Accelerometer, Auto-rotation), but proximity sensor have reading of 0cm all the time. Which make the screen black when having a phone call. And double tap/lift to wake is not working(although my accelerometer is working according to sensors multitool).
I don't have screen protector, and this problem happened just after i first updated it to android 10. so i think it might be just a software problem.
I had the october update already, but it is not fixed.
And this is a phone that never oem unlocked or rooted, no trwp installed ever, so it might be a different problem rather than that FIXED one.
I live in a country that I could not send the phone back for repairing or replacement, and i have to use adb sideload to install every ota
(and most of time when I switch my camera to frontfacing camera, it will buzz and vibrate, but when i switch back to rare and back to front, it can be fixed. this is another small issue, but it happened before this update already, maybe i just need to mention it)
Any idea what might cause this and how can I fix them?
Thanks.
https://forum.xda-developers.com/showthread.php?t=3967525&p=80233629
TonikJDK said:
https://forum.xda-developers.com/showthread.php?t=3967525&p=80233629
Click to expand...
Click to collapse
i read this already and my issue is not the same one as mentioned...
in that issue, all sensors are dead, but not in my case.
my device is never unlocked or rooted, no twrp installed, so maybe nothing has right to write the persist?
and if it is the same one, it should be fixed in october patch, but mine is not FIXED at all.
zhangcx93 said:
i read this already and my issue is not the same one as mentioned...
in that issue, all sensors are dead, but not in my case.
my device is never unlocked or rooted, no twrp installed, so maybe nothing has right to write the persist?
and if it is the same one, it should be fixed in october patch, but mine is not FIXED at all.
Click to expand...
Click to collapse
I factory reset my device yesterday and it fixed a lot of errors I was getting. Have you tried factory reset?
Be sure the phone has backed up to the google drive
I have a problem with the fingerprint sensor.. Since I switched to miui 11 with android 10 the sensor worked at times. It works for a day or two, then the menu disappears from the settings and i can no longer use it.
I try tu update vendor partition, wipe data, format data, reinstall new rom with all wipes, reinstall stock rom with Mi FlashTool, any solution works..When i wipe all, it works for a while and than, suddenly, doesn't work anymore!!
I have Mix 2S, i'm sure that is not an hardware problem..
Replace fingerprint sensor
I don't know why you say that you're sure that it's not a hardware problem, but to me, it sounds like the sensor is broken. I suffered this issue in my own Mi Mix 2s and it was caused because the "cable" of the sensor was folded (it's not really a cable, it's more like a flat plastic connector) and it worked one day and not the next. I finally decided to fix it by myself, looking for a youtube video about disassembling the phone and with these tools and the replacement sensor it was pretty easy (and quite cheap, frankly). I hope it helps!
Kaliotto said:
I don't know why you say that you're sure that it's not a hardware problem, but to me, it sounds like the sensor is broken. I suffered this issue in my own Mi Mix 2s and it was caused because the "cable" of the sensor was folded (it's not really a cable, it's more like a flat plastic connector) and it worked one day and not the next. I finally decided to fix it by myself, looking for a youtube video about disassembling the phone and with these tools and the replacement sensor it was pretty easy (and quite cheap, frankly). I hope it helps!
Click to expand...
Click to collapse
I had the same problem. Mi mix 2s had a problematic/bad assembly line.
I have exactly the same issue. After Android 10 update the fingerprint sensor works for a while. After one day I recognized that the fingerprint sensor is not working anymore. And there are no options or settings in the system settings anymore. So I assume a software problem.
Jörg Krug said:
I have exactly the same issue. After Android 10 update the fingerprint sensor works for a while. After one day I recognized that the fingerprint sensor is not working anymore. And there are no options or settings in the system settings anymore. So I assume a software problem.
Click to expand...
Click to collapse
This problem is very boring!!! Have you try a solution, or a temporary fix???
No, I have no idea how to fix. Seems we have to wait till the next update from Xiaomi, which hopefully will fix the problem. It is really boring.
Jörg Krug said:
I have exactly the same issue. After Android 10 update the fingerprint sensor works for a while. After one day I recognized that the fingerprint sensor is not working anymore. And there are no options or settings in the system settings anymore. So I assume a software problem.
Click to expand...
Click to collapse
Your assumption is wrong... these options will not show up if the system can't find the fingerprint sensor... Had the same problem and it turned out to be a hardware fault, exactly like mentioned by Kaliotto. You can do a simple test via CIT (tap multiple times on kernel-version). You will find a fingerprint sensor check in there. If it does not find the sensor, it is broken, simple as that. Replacing the sensor is really no voodoo, did it in a timeframe of 30 minutes myself and it was really the first time I ever opened a smartphone. And the parts are really cheap.
cdfs said:
Your assumption is wrong... these options will not show up if the system can't find the fingerprint sensor... Had the same problem and it turned out to be a hardware fault, exactly like mentioned by Kaliotto. You can do a simple test via CIT (tap multiple times on kernel-version). You will find a fingerprint sensor check in there. If it does not find the sensor, it is broken, simple as that. Replacing the sensor is really no voodoo, did it in a timeframe of 30 minutes myself and it was really the first time I ever opened a smartphone. And the parts are really cheap.
Click to expand...
Click to collapse
I read on differents sites a lot of people who had problems with fingerprint sensor after upgrading to miui 11 with android 10..i don't think that all of us had hardware problem at the same time of the upgrading, it's very strange...
so, to avoid any doubt, i'm searching a new fingerprint sensor..the site suggested in the second posts seems to have problems with payment, any times i try to buy with paypal o credit card, the payment was refused..so i'm searching another reliable site..
I solved the problem. In my case it was defenitely a software bug. I tried to run the fingerprint test at CIT and the phone reminded me that the phone is protected by a PIN and can not enroll fingerprint information. So I switched of the PIN protection and the fingerprint test runs positive. Since that time, the fingerprint options in the setting was back again and I was able to setup the fingerprint sensor as usually.
So I thing the deactivation of PIN protection was the solution to get the fingerprint sensor working again.
Jörg Krug said:
I solved the problem. In my case it was defenitely a software bug. I tried to run the fingerprint test at CIT and the phone reminded me that the phone is protected by a PIN and can not enroll fingerprint information. So I switched of the PIN protection and the fingerprint test runs positive. Since that time, the fingerprint options in the setting was back again and I was able to setup the fingerprint sensor as usually.
So I thing the deactivation of PIN protection was the solution to get the fingerprint sensor working again.
Click to expand...
Click to collapse
So, you only disabled pin in the lockscreen (and set swipe method to unlock the phone)??
I tried now disabling pin and restarted the phone, but no options in the settings menu
Can you give me more details? Thanks
Update! After one day of use, I have to say, that the fingerprint sensor still does not work proper. After a while the fingerprint sensor stops working again. I played around with the settings, disabled the PIN protection and start the phone several times and than the fingerprint sensor was working again for a while. There is still something wrong. Also the CIT test sometimes pass and sometimes fail. Maybe it is hardware failure after all.
What I did: I disabled the password (PIN) protection, means no protection at all. After that I was able to run the fingerprint sensor test at CIT ( as cdfs wrote). This test was pass and the settings to configure the fingerprint sensor appears again in the system settings and the sensor worked for a while.
Since this procedure the function of the sensor is not consistent and I can not definitely say what to do to get it works. In the meantime I think that all the described workaround just works by accident.
NEWS: i changed stock kernel with two modded kernel (Twisted v22 && LawRun9.0_60hz) and fingerprint start to works again!!!
So, my idea was real: it's a software problem!!!!
Try it yourself and give me your feedback
Hi,
I had also the issue that the fingerprint sensor was not recognized. I replaced it.
Then the option was there again but it doesn't read any fingerprints.
The CIT test fails by the last step "Pixel open test"
Then I got a second new fingerprint sensor and replaced it again.
The test fails again in the last step!
These are the CIT messages:
Autotest: Testing
SPI test: Success
Reset pin test: Success
Interrupt pin test: Sucess
Pixel open test: FAIL
So I would say it is a Software Issue
Hello,
so I at the end found some users, having exactly that problem!
I bought a new sensor and changed it. Pixel Opem Test failed.
I bought another sensor with the same result: Pixel Open Test failed.
Is there a usefull solution?
Mi Mix 2s MiUi 12 xioami.eu
fefuzzo said:
NEWS: i changed stock kernel with two modded kernel (Twisted v22 && LawRun9.0_60hz) and fingerprint start to works again!!!
So, my idea was real: it's a software problem!!!!
Click to expand...
Click to collapse
I had a try with twisted kernel V28.
Unfortunately it dind't solve the problem for me
meeven said:
Hi,
I had also the issue that the fingerprint sensor was not recognized. I replaced it.
Then the option was there again but it doesn't read any fingerprints.
The CIT test fails by the last step "Pixel open test"
Then I got a second new fingerprint sensor and replaced it again.
The test fails again in the last step!
These are the CIT messages:
Autotest: Testing
SPI test: Success
Reset pin test: Success
Interrupt pin test: Sucess
Pixel open test: FAIL
So I would say it is a Software Issue
Click to expand...
Click to collapse
Hello currently I am using mi note 9 pro but I am having fingerprint issue there is fingerprint option missing I am not able to mange fingerprints. Plz somebody help me
I have an issue on Samsung A515U
I already did factory data reset and upgraded to Android 11, nothing works.
I'm searching for firmware of Android 9 for this model and haven't found it yet.
Can anyone help me pls
Hello!
You can check the Samsung Fingerprint Sensor with Samsung Phone Code.
Just dial (like typing in a phone number) the Samsung Sensor Code: *#0*#
Then tap on Sensor, where you can check Samsung Accelerometer Sensor, Gyroscope Sensor, DL Magnetic Sensor, and Fingerprint Sensor.
In the Fingerprint section, Tap on “Normal Scan” and see which tests it passes and which one fails.
This is just an information, you can't repair or change anything.
Your plan to downgrade to an older android version is NOT a good idea.
They made very important changes (filesystem, security, framework structure....) in the newer versions. You might brick your phone and can't use it anymore.
To improve your fingerprint take a look at this postings Speed up fingerprint
Good luck!
Thanx for answering
I've already done what you mentioned and didn't work. I checked the sensor dialing that code and it seems to be good
Same issue here... did you get yours fixed yet?
same here, I do factory reset but no fix.
why this happen ?
solution: I went to a service store and they replace the sensor.
The test reports that the sensor is ok (all tests show as PASS), but I still get the "Fingerprint sensor calibration needed" message.
How can I calibrate the sensor? Where can I find the procedure?
dornfinger4 said:
Hello!
You can check the Samsung Fingerprint Sensor with Samsung Phone Code.
Just dial (like typing in a phone number) the Samsung Sensor Code: *#0*#
Then tap on Sensor, where you can check Samsung Accelerometer Sensor, Gyroscope Sensor, DL Magnetic Sensor, and Fingerprint Sensor.
In the Fingerprint section, Tap on “Normal Scan” and see which tests it passes and which one fails.
This is just an information, you can't repair or change anything.
Your plan to downgrade to an older android version is NOT a good idea.
They made very important changes (filesystem, security, framework structure....) in the newer versions. You might brick your phone and can't use it anymore.
To improve your fingerprint take a look at this postings Speed up fingerprint
Good luck!
Click to expand...
Click to collapse
yossidme said:
The test reports that the sensor is ok (all tests show as PASS), but I still get the "Fingerprint sensor calibration needed" message.
How can I calibrate the sensor? Where can I find the procedure?
Click to expand...
Click to collapse
Well this looks like a problem faced by most Samsung users after updating their phones. There is no exact way to fix this since Samsung is yet to release a fix to this issue.
But you can try this:
Change your lock, to swipe to unlock, which will delete your fingerprint data. Then set up your fingerprint lock again, rescanning your fingerprints like you did the first time you set your lock screen options.
I had/have the same issue after installing a backup of one A51 to another A51.
All runs fine, but the fingerprint.
Doing a factory reset -> fingerprint is OK and working.
Using the copy on the "wrong" phone -> fingerprint is NOT working
So it's no hardware issue, but I have not found a solution yet
Try to reflash the whole system with Odin and get the software from samfw