Related
Hi,
Don't know where to post my question... But... The vr apps on my note 3 always lean to the left. So when I'm playing a vr story or a Rollercoaster...at the end I'm always looking left of almost behind me. Tried calibrating the sensors but did not work. Some apps have a calibration option with the cardboard magnet. But yeah it's pretty annoying... Someone knows what this could be? I'm on Android 4.4.2...
liobeir said:
Hi,
Don't know where to post my question... But... The vr apps on my note 3 always lean to the left. So when I'm playing a vr story or a Rollercoaster...at the end I'm always looking left of almost behind me. Tried calibrating the sensors but did not work. Some apps have a calibration option with the cardboard magnet. But yeah it's pretty annoying... Someone knows what this could be? I'm on Android 4.4.2...
Click to expand...
Click to collapse
This forum is Gear centric, but common issues some are having with non Gear devices are drift and orientation issues. Most apps have a reset for orientation for this reason. Depending on your phone, this could be better or worse. Depends on the sensor design and set-up. This is all I know on the issues since will really be indigenous to your specific phone, VR headset, software and set-up. Too many variables to have a clue here.
You can try putting your phone on a flat surface while the app is on, leave for at least 5-10 sec. If that doesn't work calibrate you gyro/accelerometer sensors in HwModuleTest, dial *#0*# .
liobeir said:
Hi,
Don't know where to post my question... But... The vr apps on my note 3 always lean to the left. So when I'm playing a vr story or a Rollercoaster...at the end I'm always looking left of almost behind me. Tried calibrating the sensors but did not work. Some apps have a calibration option with the cardboard magnet. But yeah it's pretty annoying... Someone knows what this could be? I'm on Android 4.4.2...
Click to expand...
Click to collapse
Day 3 with my S10+ and after two days where the fingerprint sensor worked "reasonably well", today it refused to unlock, no matter in which angle, which one of my 3 registered fingers and no matter how much pressure (or almost no pressure) I applied. Only device restart solved the problem.
And yes, I have all the latest updates (at least the Day One that tmobile released...)
Is anyone else experiencing the same?
gilbnx said:
Day 3 with my S10+ and after two days where the fingerprint sensor worked "reasonably well", today it refused to unlock, no matter in which angle, which one of my 3 registered fingers and no matter how much pressure (or almost no pressure) I applied. Only device restart solved the problem.
And yes, I have all the latest updates (at least the Day One that tmobile released...)
Is anyone else experiencing the same?
Click to expand...
Click to collapse
Mine is acting up as well. When I first got it, it worked great and now I can barely get it to unlock
Edit: forgot to say my wife is also having troubles with fingerprint as well
sparky2029 said:
Mine is acting up as well. When I first got it, it worked great and now I can barely get it to unlock
Edit: forgot to say my wife is also having troubles with fingerprint as well
Click to expand...
Click to collapse
Same here. My Note 9 fingerprint reader was far superior. Has anyone tried removing the pre-installed screen protector? I wonder if it would help. I may try it and/or return the phone for a different model. Frustrating
Sent from my SM-G975U using Tapatalk
Also, have you gotten the FP reader update yet? I know unlocked AT&T models got it last night. Definitely helps.
mine working fine stock screen protector all updates done. received @6 March and its exynos indian variant S10+ G975F
Sent from my SM-G975F
Working fine here. Have exynos version. It initially didn't work for one of my thumb. I deleted it and again register it using every angle. Its working fine after that. Maybe Samsung released it too early without testing much.
Sent from my SM-G973F using Tapatalk
Received my galaxy s10 on March 6th. I was super excited but my excitement fizzled down after testing fingerprint scanner. That thing just would not work. It worked like 20 percent of the time. Some times I would try 5 times in a row and it would fall all the time. I had registered two thumbs twice but that didn't help. I went through a lot of threads on XDA and other forums and gathered all the suggestions. Figured out some of the things that worked for me.
Here is what you need to do to make it at least 80-90 percent reliable.
1. Upgrade to ASBA version of the firmware. I am not sure which region you are from but Samsung just released a firmware update which was about 440 MB. This should already help a ton.
2. After you upgrade, go to settings and search for "touch sensitivity". Go to the setting and turn it on. This will increase touch sensitivity of the display. It may use a bit more battery but I have not noticed any difference.
3. Now remove all your fingerprints. Click add finger. This time, when scanning finger do following.
A. Start with the middle of your thumb. Not the edge of the thumb. The part that is about half cm inside. Press that portion and don't do much of a sideway motion till you reach about 80 percent. Now use the edge of the thumb and try to move the edge a bit to reach 100 percent.
B. Add the same finger again. This time start with edge and try to get to 80 percent without much motion. Then use middle of thumb to reach 100 percent.
C. Do the same for other thumb. Also don't register your thumb in vertical position. Just register the way you would hold a phone and try to scan your thumb. Close to horizontal may be at 5-10 degree.
You may be required to press a bit hard while registering your finger but this is not needed to unlock the phone.
3. Now turn off the screen and try to unlock the device without turning on the screen. I know it is a bit hard. Just go with the feeling and press gently with middle of the thumb where you think the scanner is. Note that this is not capacitive scanner that you just touch and done. Put your thumb with a gentle press and leave it there for may be 1 second.
4. Screen should come on and phone should unlock. If it didn't work then turn off the screen and then tap it once to start always on display. This will show you the scanner on screen. Just gently press and hold for 1 second.
I have noticed that the scanner does not work when the finger is super dry. But I think after the update it has gotten better. I had initiated a return for this device and was planning to just get an iPhone. But after the upgrade I decided to keep it and trade in my galaxy note 8.
This is really worrying me. I don't want the gimmick / novelty instead of reliability
Mine is perfect. Installed the update and removed the screen protector it came with and fitted an aftermarket one my local phone shop sold. I get a failed attempt maybe 2 times a day because I haven't had my finger on the right spot
Initially I had the same issue , things I have done which resolved the issue
1 Most important, update the software version. Recent version has fingerprint issue fix.
2 Enable touch sensitivity from settings
3 Add same finger twice , i prefer to add my thumb finger in horizontal position same way you hold your phone
The only trick people miss out is they do not cover the entire sensor while unlocking...just a small adjustment and the fps is as fast and reliable as any in the market.
I initially had his problem trying with part of the sensor covered and i thought it was horrible.
Infact if you cover the sensor wholly you dont need the touch sensitivity turned on as well. I have it mine switched off.
---------- Post added at 05:57 AM ---------- Previous post was at 05:54 AM ----------
Another tip that worked for me is...while registering the fingerprint, hold the phone as you would while you unlock the device and scan the same position of the finger with minimal movement until it flashes 80%.
rtarv321 said:
Same here. My Note 9 fingerprint reader was far superior. Has anyone tried removing the pre-installed screen protector? I wonder if it would help. I may try it and/or return the phone for a different model. Frustrating
Sent from my SM-G975U using Tapatalk
Click to expand...
Click to collapse
I took that crappy screen protector off the second it came out of the box. Only had it 24 hours and it's working so far, but time will tell...
Fingerprint sensor gone
Hi, I'm new here
After I restore factory default of my S10, because it was consuming battery too fast, the fingerprint sensor stop work.
At the samsung's members app I did the interactive check of the sensor and said it is ok.
The phone and apps are update.
I try everything to restore the sensor but had no success. Does anybody knows what could be, and if it is a software problem and how to restore?
Thank you
Hey, got a question for those that exercise, or work out using their Galaxy Watch 3. Specifically, walking, but also running, treadmills,etc.
Do you see a dropping of your heart rate data at random times during your activity? Heart rate data appears perfect during the day, but will drop randomly during a walk, or treadmill activity.* This has happened both times I've tried the activities, I've only had the watch 3 days.
Anyone found a fix?
Can't speak for running, but for brisk walking the heart rate monitoring has been very good and consistent for me (within 1-2 of a chest strap monitor average after an hour).
It needs to be snug, not tight (it should not be able to slide around on your wrist in any direction). And should be above the orbital bone on your wrist.
Beretta143 said:
Hey, got a question for those that exercise, or work out using their Galaxy Watch 3. Specifically, walking, but also running, treadmills,etc.
Do you see a dropping of your heart rate data at random times during your activity? Heart rate data appears perfect during the day, but will drop randomly during a walk, or treadmill activity.* This has happened both times I've tried the activities, I've only had the watch 3 days.
Anyone found a fix?
Click to expand...
Click to collapse
I have the same problem when in cycling mode :/ At first i thought it was related to tightness of the strap or placement, but no matter how tight or loose it is, it drops, and seems to come back by random seconds or minutes after i notice it has gone.... Seems to only be in exercise mode, as i've never caught it doing it otherwise (i have continuous monitoring enabled)
In any case, the heart sensor really stops working at times during physical activities, especially running. And even at times during the day in a normal situation it stops working.
In any case I did not have this kind of problem with my Galaxy watch active 2.
I hope there will be an update soon.
To elaborate: This happened again for me today, and i took off the watch and could see the green sensor light still going.... tried to clean it and put it back on, but no success.... after ~10 minutes more on my bike, it "magically" started registering HR again.... Very weird.... Hope it is SW and not HW related though
At times I have the same problem with the heart sensor. In any case, it's very frustrating for a watch that calls itself sports / Fitness.
Well i found out that if i move the watch on my wrist during ECG, it ends with "Atrial fibrillation" and the curve looks like garbage
If i have the watch tight on the wrist, it ends sinusal and regular, clean...
So i'd guess that the drops might come from the watch not being secured enough on the wrist. Just tighten it very well before walk/run.
mafy31 said:
Well i found out that if i move the watch on my wrist during ECG, it ends with "Atrial fibrillation" and the curve looks like garbage
If i have the watch tight on the wrist, it ends sinusal and regular, clean...
So i'd guess that the drops might come from the watch not being secured enough on the wrist. Just tighten it very well before walk/run.
Click to expand...
Click to collapse
That was my first thought as well. But it behaves the same way when tightened everywhere from "comfortably loose" to "i think i cut off blood circulation to my hand" :/
early firmware issues perhaps? did you reboot the watch (pressing the bottom button until you see "rebooting" on the display)?
if you experienced better results from older galaxy watches then give the firmware some time to mature.
i use my elliptical daily and whilst i don't like to have a watch on my arm , i left it on to test the auto exercise feature. it picked up i was using an elliptical and the stats/vitals all looked in line with what i expected -- so no dropouts in hr. ive the lte version.
If it's not firmware (and probably not - mine was great out of the box), then it's a hardware issue (wasn't there a clear film on the back of the watch - did you remove that?).
I have not tested running, but brisk walking, riding an exercise bike, and sleeping and all other times of the day the heart rate is spot on for me. It definitely doesn't "drop" and stop reading. If anything, it would just spit out an inaccurate reading for a bit during strenuous exercise.
Epedemic said:
That was my first thought as well. But it behaves the same way when tightened everywhere from "comfortably loose" to "i think i cut off blood circulation to my hand" :/
Click to expand...
Click to collapse
hi exactly the same i tightened the strap of the watch to have traces of it. And always inconsistencies with the heart sensor while running. In any case looking forward to having the next update.
marctronixx said:
early firmware issues perhaps? did you reboot the watch (pressing the bottom button until you see "rebooting" on the display)?
if you experienced better results from older galaxy watches then give the firmware some time to mature.
i use my elliptical daily and whilst i don't like to have a watch on my arm , i left it on to test the auto exercise feature. it picked up i was using an elliptical and the stats/vitals all looked in line with what i expected -- so no dropouts in hr. ive the lte version.
Click to expand...
Click to collapse
How long did you have it track your workout? It seems the problem usually first starts after x minutes, and from there on it seems (to me) completely random when it starts working again (during the workout). I think i will try to see if i can spot it doing it, stop the workout mode, and see if it does HR instantly in "non-workout-mode"... I encourage others to try this too to gather some data.
*edit*: Reboot have been tried to no effect right before workout, but not during (which also kinda defeats the point), and there is no film on the watch.
Looking around, i found this thead about a similar problem one of the older watches: https://us.community.samsung.com/t5/Galaxy-Watch/Galaxy-watch-heart-rate-sensor/td-p/389847/page/7
Going to try out some of the things: 1st: turning off diagnostics. Will keep you in the loop. *edit*: Nope didn't work.
Next: Turning off always on NR monitoring. *edit*: Nope!
Third: Turning off sensor permits for power saving. *edit*: Nope, also didn't work.
Epedemic said:
How long did you have it track your workout? It seems the problem usually first starts after x minutes, and from there on it seems (to me) completely random when it starts working again (during the workout). I think i will try to see if i can spot it doing it, stop the workout mode, and see if it does HR instantly in "non-workout-mode"... I encourage others to try this too to gather some data.
*edit*: Reboot have been tried to no effect right before workout, but not during (which also kinda defeats the point), and there is no film on the watch.
Click to expand...
Click to collapse
I run errands and I always have the problems. The heart rate sensor stops at times .... And when it resumes it completely wrong. With very random measurements.
Beretta143 said:
I run errands and I always have the problems. The heart rate sensor stops at times .... And when it resumes it completely wrong. With very random measurements.
Click to expand...
Click to collapse
My readings seems fine, once it, randomly, resumes. (Eg 140-160 when biking at a fast but not furious (hehe) pace)
Compared to the apple watch it's very finicky. I have to tighten the watch band ridiculously in order to get HR and ECG.
I think the Apple watch is a better overall product.
Update incoming: https://doc.samsungmobile.com/SM-R855F/TGY/doc.html Hope this is what we're looking for.... (Not out in NEE region yet though)
Epedemic said:
Update incoming: https://doc.samsungmobile.com/SM-R855F/TGY/doc.html Hope this is what we're looking for.... (Not out in NEE region yet though)
Click to expand...
Click to collapse
Very good news.
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
andrewd71 said:
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
Click to expand...
Click to collapse
I was having the same issue when I had the edge notification app installed that makes the screen light up around the camera when you get a notification.
Uninstalled and no issues since
Tap to wake not working for me
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
andrewd71 said:
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
Click to expand...
Click to collapse
Do you have any notification or edge lighting apps installed?
Mdizzle1 said:
Do you have any notification or edge lighting apps installed?
Click to expand...
Click to collapse
No, I've not installed any apps like that.
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
andrewd71 said:
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
Click to expand...
Click to collapse
Not using a case. It's sporadic. Tap to wake works fine for a while and then stops. The issue during calls is constant. Not major issues just niggles.
Not noticed any bugs with ambient display, but it has used 20 percent battery in 21hrs.
Seems a bit high to me, have just turned it off, not worth a 5th of my battery.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
RockStar2005 said:
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
Click to expand...
Click to collapse
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
czm said:
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
Click to expand...
Click to collapse
Yeah. Seems like more and more people are noticing and like me reporting these various issues to Google. So hopefully the next batch will include fixes for all this stuff.
I have same two problem with AOD, touch to wake up and screen off/on when calling.
DOMIN_ said:
I have same two problem with AOD, touch to wake up and screen off/on when calling.
Click to expand...
Click to collapse
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
RockStar2005 said:
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
Click to expand...
Click to collapse
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
czm said:
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
Click to expand...
Click to collapse
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Morpherios said:
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
Click to expand...
Click to collapse
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
RockStar2005 said:
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
Click to expand...
Click to collapse
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Morpherios said:
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Click to expand...
Click to collapse
Hey Morpherios,
Ok.............downloaded that app and tried it out several times. It passed some of the time, but then I'd try it again a few minutes later and it would fail on both tests. Ughh!!
You think even though it passed a few times I still need to replace it?
The success rate hit of the finger print scanner is much lower with the lock screen than with the screen saver. While with the screen saver it is effective and quick , it more often than not that with the lockscreen the fingerprint identification is rejected.
Any ideas? solutions? I already deleted and printed new finger print few times already.
I find that it's total garbage. It works about 10% of the time and I've redone adding my prints over and over. I've tried most of the steps others have and find that it doesn't help. Someone said to do a factory reset and no I'm not going to do that. I just don't use it anymore and will probably get rid of this phone soon. I want to use SD cards again and have more memory as 512 is just not enough. The reader on the Note 9 was so much better.
Not sure what you guys are doing or not doing, but my print reads all the time whether screen is on or off. Get use to where the sensor is also make sure you don't have dry hands
No complaints here. Work 99 out of 100 times on both screens
Can't complain either, working perfect here and very fast, too... Btw with stock screen protector, if that matters....
Sonin66 said:
Not sure what you guys are doing or not doing, but my print reads all the time whether screen is on or off. Get use to where the sensor is also make sure you don't have dry hands
Click to expand...
Click to collapse
I am doing all of the above , just when AOD is active the success rate is vey bad , when normal screen saver is on , the success rate is much better.
Tnx
I was having no issues before a screen protector.. now I don't even use it because I can never get my finger print to read.
dnoam said:
I am doing all of the above , just when AOD is active the success rate is vey bad , when normal screen saver is on , the success rate is much better.
Tnx
Click to expand...
Click to collapse
Screensaver, AOD, screen off.. Success is 99/100
Are you using a screen protector/shield?
I have learnt I need to press harder. I used to have a Pixel 2 XL FPR on the back which was really sensitive. Using a phone with FPR under-screen was new for me, you do need to be firmer when pressing your finger down and after training myself for a few days I don't have any issue with unlocking now. I have fitted two S21Ultras (mine and friends)with the White Dome tempered glass and that has not impacted us either.
Sonin66 said:
Not sure what you guys are doing or not doing, but my print reads all the time whether screen is on or off. Get use to where the sensor is also make sure you don't have dry hands
Click to expand...
Click to collapse
It's hard to miss where the sensor is as it's pointed out on the screen when using it. As for dried hands that too seems not to matter.
Folks I'm guessing you think you're being helpful when you say that you're not having a problem with your phone as a response to someone who is have a problem. To me that's like me taking my car to a mechanic and telling them my car isn't working properly and them telling me that their car is working just fine. I worked for many years as a computer consultant at a major university in upstate NY and never once did I respond in this fashion because it's pointless.
But he was wondering if his phone was faulty..you being an analyst should realise that if most of the replies are positive that in itself helps him
Tony966 said:
Folks I'm guessing you think you're being helpful when you say that you're not having a problem with your phone as a response to someone who is have a problem. To me that's like me taking my car to a mechanic and telling them my car isn't working properly and them telling me that their car is working just fine. I worked for many years as a computer consultant at a major university in upstate NY and never once did I respond in this fashion because it's pointless.
Click to expand...
Click to collapse
Im guessing you think we can solve a problem thats either a defect or user error.
oh wait. guess we can just close the thread then.
joancolmenares said:
Screensaver, AOD, screen off.. Success is 99/100
Are you using a screen protector/shield?
Click to expand...
Click to collapse
Hi.
No , as it was unpacked from the box.
This has started to be an issue on my a.o.d.
Was ok but I changed the icon and it seems to be hit and miss now.
I just double tap the screen and bypass it
mattlcfc said:
This has started to be an issue on my a.o.d.
Was ok but I changed the icon and it seems to be hit and miss now.
I just double tap the screen and bypass it
Click to expand...
Click to collapse
My Icons also changed , so that might be the issue.
Problems solved.The cause of very low hit rate of the fingerprint scanner on AOD in lock screen was new icons i dowloaded from Galaxy store.When i installed the original , no more missed prints
No complaints here. But it completely works