Related
Please mention all the common issues found in this device (both Hardware and Software level)
So far I have gathered one issue mainly
- The USB/SD Card flap gets loosen or does not properly close.
Some units may have excessive gap between the glass and the frame, either top or bottom.
in_core said:
- The USB/SD Card flap gets loosen or does not properly close.
Click to expand...
Click to collapse
Because of this mine is on the way back to Vodafone [emoji22]
Mine has a dead pixel. But these arent common issues unless a lot of people complain about them tbh.
Servaas said:
Mine has a dead pixel. But these arent common issues unless a lot of people complain about them tbh.
Click to expand...
Click to collapse
Was the dead pixel noticeable from the very first day?
Ive got two things where im not sure if that are real Problems or just a question of settings.
First one is that voice from the other part is not really loud, even on the highest setting, during a phone call.
The other one is the battery time. I dont get such high results like 2 days from the tests on different websites. I only got one day with moderate usage.
in_core said:
Was the dead pixel noticeable from the very first day?
Click to expand...
Click to collapse
No second day, first day I probably didnt notice. Nor do I now to be honest... was hesitating about sending it back but ehh... its so much hassle and like I said I can hardly tell its dead.
I have returned mine to o2 within the initial cooling off period, there's too many problems to risk sorry. I loved the spec and design too
Did you experience any problems or did you just bottle it? I've had mine for a week or so with no problems at all.
qbert456 said:
I have returned mine to o2 within the initial cooling off period, there's too many problems to risk sorry. I loved the spec and design too
Click to expand...
Click to collapse
I'd assume that more than 90% of units have no major issues. The misleading thing is that, in communities like these, people with faulty units are far more represented than people who are satisfied.
Honestly, I didn't really use it,it kept all the plastic films on etc. It's not that I'm not going to get one if it proves reliable more that I'm quite unlucky with phones generally!
I will keep looking in here tho and will likely getting a red/orange one again in a few weeks....
qbert456 said:
Honestly, I didn't really use it,it kept all the plastic films on etc. It's not that I'm not going to get one if it proves reliable more that I'm quite unlucky with phones generally!
I will keep looking in here tho and will likely getting a red/orange one again in a few weeks....
Click to expand...
Click to collapse
I suggest you just get a silicone cover or something, to protect it. A wrist lanyard also helps a lot. And to increase your chance of getting a Z3C from a more recent production batch, you can keep an eye on a web shop and order a Z3C after the stock runs out and is restocked.
Camera Button
Is the Z3c hardware camera button designed to require a fairly lengthy press to activate? I'm guessing that maybe it's a design built in to perhaps avoid accidental pocket presses, but I'm not sure.
Just a quick tap does not activate it on mine, but it works fine with a slightly longer press.
Poojo said:
Is the Z3c hardware camera button designed to require a fairly lengthy press to activate? I'm guessing that maybe it's a design built in to perhaps avoid accidental pocket presses, but I'm not sure.
Just a quick tap does not activate it on mine, but it works fine with a slightly longer press.
Click to expand...
Click to collapse
Mine too, also there seems to be a 2-step press for it, as on a regular camera (half hold down to focus). Half pressing doesn't start it.
Have had to mess with settings to turn off the quick launch which was set to launch and capture as I have so many pics of either a finger or blackness!
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
impact1991 said:
Ive got two things where im not sure if that are real Problems or just a question of settings.
First one is that voice from the other part is not really loud, even on the highest setting, during a phone call.
The other one is the battery time. I dont get such high results like 2 days from the tests on different websites. I only got one day with moderate usage.
Click to expand...
Click to collapse
On mine the sound is pretty loud through the mic, so much so that I thought the loudspeaker was on! Conversely though the actual loudspeaker doesn't seem that loud! Go figure!
For the battery I think you would only get 2 days with the Stamina settings active. I manage to get down to about 25% on a full day of regular usage (in office etc). The Stamina / Ultra stamina modes seem to just disable pretty much everything on the phone. OK if you need to keep it powered on but no good for regular usage. I've ended up turning stamina mode on and then re-enabling Wifi, seems to improve life quite a bit for the times I have been hammering it!
degraaff said:
I'd assume that more than 90% of units have no major issues. The misleading thing is that, in communities like these, people with faulty units are far more represented than people who are satisfied.
Click to expand...
Click to collapse
Always been the case since the Treo days, lol. People will look and see all these problems, but they are random people, that really only for the most part show up here to resolve "issues". While it is a great thing for folks looking for corrections, it does appear bad on the surface if you don't really understand the dynamic at play on boards like these.
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
Poojo said:
Is the Z3c hardware camera button designed to require a fairly lengthy press to activate? I'm guessing that maybe it's a design built in to perhaps avoid accidental pocket presses, but I'm not sure.
Just a quick tap does not activate it on mine, but it works fine with a slightly longer press.
Click to expand...
Click to collapse
Yes. Your button is behaving normally.
I'm currently on my third unit within 7 days. My Internet connection seems to hang about 2 or 3 times a day, and until I try to use the Internet Is don't realise. After then restarting my phone, I get a flood of whatsapps, emails and fb alerts. It's getting really old really quickly,to the point where I just want rid of the phone.
jbhkhc said:
I'm currently on my third unit within 7 days. My Internet connection seems to hang about 2 or 3 times a day, and until I try to use the Internet Is don't realise. After then restarting my phone, I get a flood of whatsapps, emails and fb alerts. It's getting really old really quickly,to the point where I just want rid of the phone.
Click to expand...
Click to collapse
I've only had that once, last Fri however it is a bit weird, here's how mine manifested itself:
- Work most of the day in an office, good wifi connection. Don't use the phone much but see that it is working OK, getting emails, fb updates etc. Can browse the internet via Chrome
- Left the office and try to do a search. Using Google search from the home screen the results showed up very quickly but then when I tried to open any of those links in chrome it would just say no network or something similar. Tried shutting down chrome, clearing cache and data but made no difference.
The weird thing here is that the 4g / mobile data connection WAS working, but the issue was with Chrome.
I'm still stock, not likely to change that but since Chrome is now an intrinsic part of the Xperia build how do you uninstall / reinstall? Or do I end up installing another browser?
Chrome has done this to me on Z3 Compact and a few times on my previous Xperia ZR. Just close the browser from the multi-app right button by flicking it to the side, then try again. If it gets too tedious, install another browser.
Hi, any one have the same issue as me?
My Z3C black out after 2nd week of use then could not power on. Brought to service center and the person claim that it is software issue.. Took back the phone after they reformatted, then after 12hrs use, same problem again.. Then they change 1-1 for me.. but after another week of use, same issue on the 2nd phone!
who have the same issue as me? what should i do next? i cant be bringing the phone in to service center every week..
hello,
I think it's the same pb for me... "Z3 Compact" bought the 28.09.2014. The phone is turned off itself in the middle of the day in my pocket. The battery level was approx. 75% => Black screen, not even light on the charger...:S The Sony support told me to send them with charger and usb cable. I am waiting for news... approx. 10 days...
I've had my Note9 (Tmo) since release, so about 2 weeks now. Usually a quick tap of my finger on the fingerprint scanner and the phone immediately jumps to life and I'm on the home screen. But today it's acting erratically. Now it takes like 5 or 6 presses for it to register, and that's only after I turn the phone on first (it won't skip sleep and go directly to the home screen anymore).
I tried a rebooting, recreating my prints, as well as making sure the scanner is wiped perfectly clean, and that worked... But only for a little while, the issue has come right back.
Anyone else seeing similar issues?
Do other sensors work as expected?
On my previous Note8, when sensors stop working due to hardware fault, the fingerprints also did not work.
BTW I have not experienced the same issue on my Note9 yet.
Are you using a theme? If so that could be the issue. Uninstall theme and try fingerprint again.
Wash your hands.
I also have this issue, it's pretty annoying. On the lockscreen, the phone says "fingerprint-sensor not responding, try again later", and that's it. Tried wiping cache from the recovery menu, nothing.
Try typing *#0*# into the dialer and go to sensors test, should be able to determine if your finger print reader is faulty or not there.
Try cleaning the fingerprint scanner or using a wet wipe on your finger. As the lack of moisture is probably what is causing this issue. It happened to me a few times in HK.
I have the same issue.
My scanner is now telling my "fingerprint wet." But my fingers aren't wet, and I wiped the scanner down several times. Like the OP says, it works for 1 or 2 swipes, then won't recognize my fingerprint.
I'm having the same issue with my Note9. In my case, the problem happens ONLY if I had my phone in my pocket more than 1 minute, the fingerprint sensor just won't work, it's not like it doesn't recognize it, it's dead. I have to wait about 10 seconds putting my finger on the sensor 'til it works. I have tried everything. I'm pretty sure it's something in the software related to the phone being in my pocket (not because the phone's been idle), because when I go to bed and put my phone on the table, the next morning I just grab my phone and immediately the fingerprint sensor takes me to my home screen, no problem.
Namuna said:
I've had my Note9 (Tmo) since release, so about 2 weeks now. Usually a quick tap of my finger on the fingerprint scanner and the phone immediately jumps to life and I'm on the home screen. But today it's acting erratically. Now it takes like 5 or 6 presses for it to register, and that's only after I turn the phone on first (it won't skip sleep and go directly to the home screen anymore).
I tried a rebooting, recreating my prints, as well as making sure the scanner is wiped perfectly clean, and that worked... But only for a little while, the issue has come right back.
Anyone else seeing similar issues?
Click to expand...
Click to collapse
Do you guys have solution to this I been having this issue for a month or so now and i think it is getting worse.
Hi guys, be brave and call Samsung. The phone is under warranty.
They will collect it and drop it off for free, after repairing it and putting your phone back to water and dust resistant.
It took me about 10 days all together, if not less.
florin_stann said:
Hi guys, be brave and call Samsung. The phone is under warranty.
They will collect it and drop it off for free, after repairing it and putting your phone back to water and dust resistant.
It took me about 10 days all together, if not less.
Click to expand...
Click to collapse
I've had samsung repair experienced before my Galaxy s8+ it took them about 5 business days turn around repair it was just software issue.. But with this fingerprint if it's just software glitch or setting i rather do that first but if not I might have do warranty claim.. it always take 2-3 tap for me to work on the fingerprint this is way way slower than my S9+.. Did you have fingerprint issue?
It is definitely not software. Days i have spent uninstalling apps and themes and testing and then resettimg it all and so on and so forth!
It seemed at the beginning that a factory reset is enough, but next day it would start again.
It finally gave up and i have called Samsung, as i do not buy insurrance for my phones and they sorted me out.
I knew it was not software when i have booted the Note into safe mode and it behaved just the same.
skyethur said:
I've had samsung repair experienced before my Galaxy s8+ it took them about 5 business days turn around repair it was just software issue.. But with this fingerprint if it's just software glitch or setting i rather do that first but if not I might have do warranty claim.. it always take 2-3 tap for me to work on the fingerprint this is way way slower than my S9+.. Did you have fingerprint issue?
Click to expand...
Click to collapse
Sorry, forgot to quote you in my reply above.
Anyway, now after the repair, the Note responds diferently, it unlocks fast as hell using the fingerprint.
Try erasing all your fingerprints and re-registering them all over again. As sometimes your fingerprint settings maybe corrupted by a OS update.
florin_stann said:
It is definitely not software. Days i have spent uninstalling apps and themes and testing and then resettimg it all and so on and so forth!
It seemed at the beginning that a factory reset is enough, but next day it would start again.
It finally gave up and i have called Samsung, as i do not buy insurrance for my phones and they sorted me out.
I knew it was not software when i have booted the Note into safe mode and it behaved just the same.
Click to expand...
Click to collapse
Mine isn't like that. Fingerprint sensor works once the device is already in use but once in sleep mode for awhile it will take 2-3 taps for it to unlock and it doesnt happen all the time so My issue is sensor sensitivity and it seems to me that the sensor is not getting any power once in sleep mode to save battery that's why it is less sensitive that's just my opinion. But I already made a ticket to samsung and unfortunately the repair center which I dont trust at all the uBreakifix do not have the sensor in stock. So I may have to call in to ship out my phone.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
iceepyon said:
Try erasing all your fingerprints and re-registering them all over again. As sometimes your fingerprint settings maybe corrupted by a OS update.
Click to expand...
Click to collapse
I have already re-register my finger about 20 times but seems to happen over and over.
note 9 fingerprint issues
Namuna said:
I've had my Note9 (Tmo) since release, so about 2 weeks now. Usually a quick tap of my finger on the fingerprint scanner and the phone immediately jumps to life and I'm on the home screen. But today it's acting erratically. Now it takes like 5 or 6 presses for it to register, and that's only after I turn the phone on first (it won't skip sleep and go directly to the home screen anymore).
I tried a rebooting, recreating my prints, as well as making sure the scanner is wiped perfectly clean, and that worked... But only for a little while, the issue has come right back.
Anyone else seeing similar issues?
Click to expand...
Click to collapse
i am and i wish i knew how to fix it
*#0*# sensor test says that the RESET test has failed. I'm getting random reboots while not using the device.
willhemmens said:
Try typing *#0*# into the dialer and go to sensors test, should be able to determine if your finger print reader is faulty or not there.
Click to expand...
Click to collapse
The test shows RESET: Failed. Everything else is a PASS. It must be a hardware problem. I am getting random reboots while on standby when the fingerprint sensor is turned on.
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
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?
After a few days with the Pixel 7, sadly, I decided to return it.
The biggest reason is the fingerprint reader just didn't work right. 3 out of 4 finger presses don't work. I don't know if it's just a faulty phone that I got, but I got tired of redoing the fingerprint scans.
I have Pixel 6 and the fingerprint reader works very reliably.
The Face Unlock works but I found a bug that if the face unlock is enabled, then for all of the 3rd party apps that use biometric login, the fingerprint unlock stops working and these apps don't support the face unlock.
I had a terrible time getting mine registered and working. I have dry fingers and after moisturizing a little, the enrollment went in one go and the fingerprint works as fast as any other phone.
I have no idea how I got it fixed but I was having the same issue as you. I disabled verity and verification to flash custom kernel (wiped phone after verity) and after that the FP reader is working with 100% accuracy. It was night and day for me.
The fingerprint reader seems to be worse on the Pixel 7 than it was on my Pixel 6. It's fast but has a much higher failure rate.
Has anyone seen a difference with the animation speeds changed in developer options?
My son has my old pixel 6 and the fingerprint reader is working great.
{Mod edit: Quoted post has been deleted}
I tried it in any way I could think of. Dry, wet, sanitized with alcohol, greasy, dirty, you name it. Did not work.
feligoni said:
I have no idea how I got it fixed but I was having the same issue as you. I disabled verity and verification to flash custom kernel (wiped phone after verity) and after that the FP reader is working with 100% accuracy. It was night and day for me.
Click to expand...
Click to collapse
If I pay $600 for the phone and have to do ADB "contortions" to get the FP scanner to work, then I don't need the phone like that.
A "cheap" inlocked Chinese POCO phone with under screen FP reader works 100% of the time without disabling dm-verity.
Wow I find my Pixel 7 to be much better on the FP scanner than my P6 was, I even added a screen protector after enrolling my prints. I also now use the face unlock and have no issues with Apps that use the FP biometric option. This phone is way better than my P6.
xela19115 said:
If I pay $600 for the phone and have to do ADB "contortions" to get the FP scanner to work, then I don't need the phone like that.
A "cheap" inlocked Chinese POCO phone with under screen FP reader works 100% of the time without disabling dm-verity.
Click to expand...
Click to collapse
Agree - I'm fairly familiar with Xiaomi phones and their FP readers are pretty reliable. I'm surprised how poorly my Pixel 7's reader is. In this day and age, we shouldn't have to compromise on what's supposed to be a stable technology after paying $600.
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
xela19115 said:
After a few days with the Pixel 7, sadly, I decided to return it.
The biggest reason is the fingerprint reader just didn't work right. 3 out of 4 finger presses don't work. I don't know if it's just a faulty phone that I got, but I got tired of redoing the fingerprint scans.
I have Pixel 6 and the fingerprint reader works very reliably.
The Face Unlock works but I found a bug that if the face unlock is enabled, then for all of the 3rd party apps that use biometric login, the fingerprint unlock stops working and these apps don't support the face unlock.
Click to expand...
Click to collapse
Really? I have not had that problem - any conflict between face unline and Finger for Biometric apps. Face unlock is outstanding. Fingerprint reader is meh, ok, sometimes
a1b2c3d4444 said:
Agree - I'm fairly familiar with Xiaomi phones and their FP readers are pretty reliable. I'm surprised how poorly my Pixel 7's reader is. In this day and age, we shouldn't have to compromise on what's supposed to be a stable technology after paying $600.
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
Click to expand...
Click to collapse
I have noticed that same thing on my 7 Pro although for me it's more like an hour+ where it gets bad... It will be fine all day then I set my phone down for awhile, pick it up later, and it will instantly fail all three times and then start working again after my PIN goes in. Very strange. Probably can be fixed with software.
No problems here, had the phone for a week now. I don't think I've had any failed reads, maybe one or two. Very reliable and fast, perfect combo with the face scanner.
Mine was failing like crazy. Tried everything. Took it back and exchanged for a new one and the new one is working great. Definitely some faulty hardware out there
a1b2c3d4444 said:
Agree - I'm fairly familiar with Xiaomi phones and their FP readers are pretty reliable. I'm surprised how poorly my Pixel 7's reader is. In this day and age, we shouldn't have to compromise on what's supposed to be a stable technology after paying $600.
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
Click to expand...
Click to collapse
similarly
Mine works flawlessly every time. The only thing I don't like is using it at night, and not covering it with my entire finger. When it scans, it's so freakin' bright! LOL
My 7 Pro's sensor worked great, my regular 7's is just plain awful. And I know about the dry hands issue, I've been preaching that people moisturize their hands since under-display sensors came out.
At the first time with my pixel 7 the i had your same issue, fp wasnt working 9 time on 10 but then, after registered it again correctly (reading the on screen instruction while do it) is started to work flawlessly every time. Now it is always unlocking the phone, with more light or in the dark (at night for example) and with low or high brightness.
a1b2c3d4444 said:
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
Click to expand...
Click to collapse
This was the case with my P7 too. But since past few days, it started to work like 10/10. I haven't noticed any failure since yesterday. Never changed the fingerprint data too.
Update!
I returned the phone. I waited until I got the refund, took a train ride to NYC, and went to Google's Chelsea store. I bought a new Pixel 7 128 GB, traded my Pixel 6, and spend about 2 hours setting up everything in the store. Another advantage of going to the store is that I don't have to pay $600 + tax immediately and then wait 2-3 weeks for a $490 trade-in credit. They take the trade-in and I paid the difference.
If the fingerprint scanner on the new phone would have given me the same issues, I would have at least dealt with it in the store.
And it did start giving me issues initially, but then I asked for assistance and they (store tech support) admitted that Pixel 7's have fingerprint reader problems. He changed the sensitivity setting on the phone and it works (for now).
So clearly I had a bad, faulty phone before. Now, with a phone that I got over the weekend, everything works.
xela19115 said:
Update!
I returned the phone. I waited until I got the refund, took a train ride to NYC, and went to Google's Chelsea store. I bought a new Pixel 7 128 GB, traded my Pixel 6, and spend about 2 hours setting up everything in the store. Another advantage of going to the store is that I don't have to pay $600 + tax immediately and then wait 2-3 weeks for a $490 trade-in credit. They take the trade-in and I paid the difference.
If the fingerprint scanner on the new phone would have given me the same issues, I would have at least dealt with it in the store.
And it did start giving me issues initially, but then I asked for assistance and they (store tech support) admitted that Pixel 7's have fingerprint reader problems. He changed the sensitivity setting on the phone and it works (for now).
So clearly I had a bad, faulty phone before. Now, with a phone that I got over the weekend, everything works.
Click to expand...
Click to collapse
which sensitivity setting ?
The scanner is bad, that's all. The crucial thing to make it usable is the right inital scan, if it records your fingers flawlesly it will work (but not the way we expect, only in an acceptable way).
There is no sensitivity setting, he probably mean the display setting.