Related
Has anyone got NFC to work?
You have an option of choosing NFC secuity chip by choosing kne of the sim slots
But it does not read any nfc tags
M
I'll admit I had a time trying to get nfc to work. Just sending a picture to my wife (who also has the Mate 8), was a task. I finally got it to work when we took our cases off.
dpagoh said:
I'll admit I had a time trying to get nfc to work. Just sending a picture to my wife (who also has the Mate 8), was a task. I finally got it to work when we took our cases off.
Click to expand...
Click to collapse
First i read "clothes" then "cases" ... :laugh:
lol, it just needed a little LUV baby!
have you found the solution? mine also not working and been trying to reset as well... this is a nightmare!
I had my NFC work as mobile payment. It works smoothly.
AL10 reflashed to L29
NFC doesnt work, i try to read card, on oher phone works
kangvip b170
On my AL10 NFC works. I transferred a video I had taken to a friends Samsung phone through NFC and it worked fine. I was running KangVIP B168 at the time but NFC should work on stock as well.
jbmc83 said:
it just needed a little LUV baby!
Click to expand...
Click to collapse
what you mean ? or just laughing ?
i dont try took case off yet (it is not metal) and very hard do it
Its a very strange but after i took of case ... it works. I put phone back in case and ... work again... In other apps works too... In same app that dont work earlier... Nothing other changes - only on off NFC button, try to send photo via NFC ... May be first launch was hard ? I start thinking thats needed to receive next level in Hogwarts
AL10 KangVIP 170 4/64
dpagoh said:
I'll admit I had a time trying to get nfc to work. Just sending a picture to my wife (who also has the Mate 8), was a task. I finally got it to work when we took our cases off.
Click to expand...
Click to collapse
I tried this with another Mate 8, made the 2 Mate 8 "kiss" close to where the camera is. The other phone recognized a tag which it could not read (My Mate 8). That was L29C185B560. I just updated mine to L29C636B563... I tried to NFC with a Windows Phone. No luck.
Pretty pissed now!
I also have a problem with NFC on my Mate 8.
Current firmware L29C636B563, previous firmware tested on L29C636B321 (and maybe L29C636B330)
First off, I was testing this with an LG Washer / Dryer with the "Tag On" logo. The LG Application could not detect the NFC so I will assume the problem is with the phone? Where exactly is this NFC strip they are talking about? No, even after updating to L29C636B563 Nougat OTA Push Update, my Mate 8 will still not work with LG Tag On.
So, I got curious as to whether or not NFC was working to begin with. I live in Canada. It is a very *backwards* country and NFC applications are few and not mainstream. Apple Pay just got introduced... and Android Pay is not even available for download... so... I never really had any use of NFC at all.
Anyway, I have another Mate 8 (not mine). It recently got an OTA push, L29C185B560. At that time, my Mate 8 was still at L29C636B321.
We tried Android Beam... I guess the instruction was to bring the phone close together (in this case - back to back) and both phones will detect each other... then you can tap content to the other phone...
Well... the L29C185B560 (let's call this C185 for short) made a sound and it picked up a tag, but that tag was empty... ?? My phone, the L29C636B321 (let's call this C636 for short) did not do anything at all... it just stared and stared in outerspace....
I also tried to "Share" and then pick "Huawei Beam" and of course, nothing happened between the 2 phones....
I was suddenly discouraged... eeeks! No NFC? I thought this phone was the *super* phone... time to shop for another phone.
Just last week, my C636 got its first OTA update... uhm... only after downloading Firmware Finder... maybe it did something to the settings to correct it...
So, it got updated to C636B330 first, then 2 days later, C636B563 arrived. Yay... Nougat! What bugs are there?
Just 2 days ago, I tried to Beam with a Samsung Galaxy S4. No luck there...
So just this weekend, I tried Beam again... first, just putting the phone together... no luck.
Then, I thought... uhm... so this time, I put the phones together, back to back and then picked a photo on my phone, "Share" and "Huawei Beam".... surprise, surprise... I heard a tone.... I angled my head and saw that my phone recognized a device and I tapped and I guess the other phone, the C185 didn't need to accept the beam, it was already downloading the photo...
So I tried the LG Tag On again... no luck...
Then. I got home and downloaded apps to read my chip enabled Canadian passport (inside and outside the covers) and my Paypass enabled credit card... No... none of the apps detected anything.
To my understanding NFC will "communicate" once detected. No further action. In the experience with Huawei Beam... it seems that an "action" has to be triggered for NFC to activate? Maybe I am wrong and have been wrong all this time?
So, does "reading" an NFC tag also require an action?
What else is broken?
I found some documentation on Huawei Mate 8 NFC. Maybe someone with more experience will be able to explain this occurrence way better? Give us more insight and get it working?
I just bought 10 NFC Tag stickers on eBay, let's see late on if the phone actually reads it....
Thank you for this. I had sworn my NFC was dead, then I took the extra step you mentioned of trying to send a picture using Beam, and that appears to have woken the NFC chip up. I can't believe it's working fine now.
Cheers!
childoftheworld said:
I also have a problem with NFC on my Mate 8.
Current firmware L29C636B563, previous firmware tested on L29C636B321 (and maybe L29C636B330)
First off, I was testing this with an LG Washer / Dryer with the "Tag On" logo. The LG Application could not detect the NFC so I will assume the problem is with the phone? Where exactly is this NFC strip they are talking about? No, even after updating to L29C636B563 Nougat OTA Push Update, my Mate 8 will still not work with LG Tag On.
So, I got curious as to whether or not NFC was working to begin with. I live in Canada. It is a very *backwards* country and NFC applications are few and not mainstream. Apple Pay just got introduced... and Android Pay is not even available for download... so... I never really had any use of NFC at all.
Anyway, I have another Mate 8 (not mine). It recently got an OTA push, L29C185B560. At that time, my Mate 8 was still at L29C636B321.
We tried Android Beam... I guess the instruction was to bring the phone close together (in this case - back to back) and both phones will detect each other... then you can tap content to the other phone...
Well... the L29C185B560 (let's call this C185 for short) made a sound and it picked up a tag, but that tag was empty... ?? My phone, the L29C636B321 (let's call this C636 for short) did not do anything at all... it just stared and stared in outerspace....
I also tried to "Share" and then pick "Huawei Beam" and of course, nothing happened between the 2 phones....
I was suddenly discouraged... eeeks! No NFC? I thought this phone was the *super* phone... time to shop for another phone.
Just last week, my C636 got its first OTA update... uhm... only after downloading Firmware Finder... maybe it did something to the settings to correct it...
So, it got updated to C636B330 first, then 2 days later, C636B563 arrived. Yay... Nougat! What bugs are there?
Just 2 days ago, I tried to Beam with a Samsung Galaxy S4. No luck there...
So just this weekend, I tried Beam again... first, just putting the phone together... no luck.
Then, I thought... uhm... so this time, I put the phones together, back to back and then picked a photo on my phone, "Share" and "Huawei Beam".... surprise, surprise... I heard a tone.... I angled my head and saw that my phone recognized a device and I tapped and I guess the other phone, the C185 didn't need to accept the beam, it was already downloading the photo...
So I tried the LG Tag On again... no luck...
Then. I got home and downloaded apps to read my chip enabled Canadian passport (inside and outside the covers) and my Paypass enabled credit card... No... none of the apps detected anything.
To my understanding NFC will "communicate" once detected. No further action. In the experience with Huawei Beam... it seems that an "action" has to be triggered for NFC to activate? Maybe I am wrong and have been wrong all this time?
So, does "reading" an NFC tag also require an action?
What else is broken?
I found some documentation on Huawei Mate 8 NFC. Maybe someone with more experience will be able to explain this occurrence way better? Give us more insight and get it working?
I just bought 10 NFC Tag stickers on eBay, let's see late on if the phone actually reads it....
Click to expand...
Click to collapse
Actually, never mind. It's dead again. I have no idea what I did to make it work for a short while,
but now it won't read my cards anymore. (sigh)
r0bgar said:
Thank you for this. I had sworn my NFC was dead, then I took the extra step you mentioned of trying to send a picture using Beam, and that appears to have woken the NFC chip up. I can't believe it's working fine now.
Cheers!
Click to expand...
Click to collapse
Repair
Same case but i have found the reason.
The nfc antenna is embedded in to top side of back cover.
It's connected not with flex cable, but with spring contacts
2 screws on bottom
open carefully (fingerprint scanner on cover is connected with flexible cable)
adjust spring contacts
clean contacts and contact pads on cover with alcohol or ...
that's all
now it works
Hi,
Coming from a Moto Z and before that a 6P.
Ok... I didn't intend to hate this phone but... Why are notifications broken? Why dont PocketCasts playback controls work?
I know this is "1 aspect" but to me notifications are vital and i simply don't understand this phone.
- i receive a notification and screen lights up (i set that per app)
- but then I unlock phone
- notifications still in notification shade. I lock device.
- they are no longer on lock screen
Why?
That's not how any other device i have owned worked?
And lock screen music playback is... A disaster?
I consider this phone basically unusable... Yet reviews never mentioned this. Am I alone?
I agree with you, mostly. I'm coming from a Nexus 6P (and many Nexi before that since the One), so I'm used to the plain Vanilla and love it. I was able to rectify some of the notification issues by enabling banner and lockscreen notifications from the Settings >> Notification & Status Bar >> Notification Management area. It doesn't fix everything, and at times (especially the beginning) it was very frustrating. I have it for 5 days now and am at a point where I think it's usable and am waiting for LineageOS to come out with a vanilla-ish version.
http://lineagerom.com/huawei-mate-9-lineage-nougat-update/
The battery is what drew me to the phone and it doesn't disappoint. I can get about 24 hours and that impresses me.
Thanks, have that set for important apps. Feels like a massive part of Android (notifications) are basically missing. Rest is good/ok/great but.... Just feels like madness that this is acceptable in 2017.
yup, hw software sux. end of. waiting for stock-ed customs
Just you
Sent from my MHA-L29 using Tapatalk
Yea, that's what ended up being the deal breaker for me. I absolutely loved everything else with the phone, but notifications are the baseline of what a phone should be (at least to me), and this phone failed at that miserably. Not being able to reply to a text without unlocking the phone is a no go for 2017. I also kept hearing how battery life was amazing...I never really saw that either considering the size of the battery and a 1080p screen. I've got a Moto Z Play and I can tell you that this is truly amazing battery life. I'm now sitting at 53% with 4:39 sot and been off charger since 9:45a...It's now 1a the following morning. Not putting down Mate 9, as I really did like the rest of the phone...So much so that I'm on here looking to see if they have come out with an update for the glaring problem you guys are discussing. It looks as they Huawei doesn't even acknowledge the issue, so not counting on a fix. Oh well
Sent from my XT1635-02 using Tapatalk
I'm really surprised Huawei get a free pass on this. I read about 10 reviews, saw lots of YouTube videos and I had no idea how this phone handles notifications. I simply don't believe that someone coming from "normal" Android versions wouldn't find this different enough to warrant a huge rant?
Very frustrating. I like so many aspects of this device but the basic things are terrible. Madness.
for lock screen music playback -
settings> then uptop type in notifications> notifications panal> notification managment. then find the app you want to allow on the lockscreen. hope that helps.
Spot on! I'm 700 USD in on this phone. Only thing going for it on my side is the battery (so far) and dual sim as I travel a lot.
The rest is just unacceptable... At the very best. Likely the first and the last Huawei I'll own.
It's not just software that is bad for notifications. The hardware is poor too. The LED is tiny and almost invisible. The vibration is very weak so you can't feel it in your pocket.
This is a great phone underneath, but the little things really spoil it.
Huawei had a great opportunity to take business off Samsung, but they have blown it.
This has put me off Huawei. I'll be trading in the Mate for a Note 8. Or perhaps I won't wait for that. The S8+ is looking good.
Coming from a Nexus 6, the software has it's issues, but overall I like my Mate 9 so much more. Thought I would be missing the stock Android in a daily basis, but I seem to be very happy with my new phone.
-ErrorFile- said:
Coming from a Nexus 6, the software has it's issues, but overall I like my Mate 9 so much more. Thought I would be missing the stock Android in a daily basis, but I seem to be very happy with my new phone.
Click to expand...
Click to collapse
Coming from the disastrous year of Samsungs (s7 Active, s7 Edge, Note 7) Im loving the mate 9. Getting 10 hours of screen on time, notifications havent been an issue at all (Ive had to unlock the phone to reply to a text on every single phone Ive used including iPhone). I prefer the lockscreen stay clean and the led flash when I have something unread. Out of all the phones Ive used this past year, this is the only one Ive kept. Ive got a Moto Z Force sitting on my table thats for sale and once its gone all Ill have left is my iPhone 6s plus and the Mate 9.
wingzfan said:
Coming from the disastrous year of Samsungs (s7 Active, s7 Edge, Note 7) Im loving the mate 9. Getting 10 hours fo screen on time, notifications havent been an issue at all (Ive had to unlock the phone to reply to a text on very single phone Ive used including iPhone). I prefer the lockscreen stay clean and the led flash when I have something unread. Out of all the phones Ive used this past year, this is the only one Ive kept. Ive got a Moto Z Force sitting on my table thats for sale and once its gone all Ill have left is my iPhone 6s plus and the Mate 9.
Click to expand...
Click to collapse
Do you find the LED bright enough and the vibration strong enough? If so I have a different phone to yours
RR-99 said:
Do you find the LED bright enough and the vibration strong enough? If so I have a different phone to yours
Click to expand...
Click to collapse
I have no issues with the brightness of the led at all, in fact I prefer it to the absurd brightness of the s7 series. My phone is primarily on a desk or table and I havent missied any notifications at all. Also my volume is always on so I hear my phone go off and never really pay attention to the vibration of it but I would say its right on par with my iPhone. Another thing is I use Textra and always have so Ive got the vibration set to "multiple short" and if the phone is for some reason on silent I still hear the vibration when a notification comes in. Honestly I have no complaints about anything with this phone especially now that Ive been able to change out the emojis without root (hate android emojis).
coming from a pixel
i really like the mate 9, the software could do with abit more though.
if it was pure vanilla, this phone would be the end all.
RR-99 said:
Do you find the LED bright enough and the vibration strong enough? If so I have a different phone to yours
Click to expand...
Click to collapse
I use an app called Flash notificationn 2. basically on any missed notifications it keeps flashing the camera and lights up the screen( set every min or so). it works very well. coming from a note 4 i was also tossed. I do love this phone and at 599.00 seems a steal. does it have shortcomings , ya it does. but so does every phone. price to price with the s8+ or note 8 rumored at close to a grand makes this phone a steal. especially considering the list of shortcomings the galaxys 8 will have.
https://play.google.com/store/apps/details?id=com.manzy.flashnotification2&hl=en
admorris said:
Not being able to reply to a text without unlocking the phone is a no go for 2017.
Click to expand...
Click to collapse
That seems like an odd issue to me. All it takes to unlock the phone is touching a sensor. Unless the complaint is about doing it while sitting flat on a surface, then I agree the sensor placement isn't optimal. But if replying to a text without unlocking the phone is important, that's easily solved with a 3rd party text app, like Textra.
I also haven't noticed the issues with notifications in my usage that others have had. But I do agree the notification LED could be brighter, and the vibration stronger.
tommy281 said:
for lock screen music playback -
settings> then uptop type in notifications> notifications panal> notification managment. then find the app you want to allow on the lockscreen. hope that helps.
Click to expand...
Click to collapse
This just doesn't work reliably. Spotify works 60% of the time maybe but PocketCasts about 5%. Totally rubbish.
Really mixed bag of opinions here.
I'm almost wondering if there are multiple software versions showing different behaviour?
The 2 notifications issues i have are :
1. Music playback controls. Dreadful. Seems like some apps whitelisted but even those don't work 100% of the time. PocketCasts (even latest version from 2 days ago) works basically never, meaning i need to unlock phone to pause. A total joke.
2. Notifications. Lock screen shows them once and once only. As soon as i unlock, all notifications are not shown again on lock screen, unlike normal Android.
For those that "don't have issue with the notifications"... Do you see what i see?
tommy281 said:
for lock screen music playback -
settings> then uptop type in notifications> notifications panal> notification managment. then find the app you want to allow on the lockscreen. hope that helps.
Click to expand...
Click to collapse
That doesn't fix the issue...It's a known problem.
Sent from my XT1635-02 using Tapatalk
---------- Post added at 05:41 PM ---------- Previous post was at 05:36 PM ----------
RealEvil said:
Really mixed bag of opinions here.
I'm almost wondering if there are multiple software versions showing different behaviour?
The 2 notifications issues i have are :
1. Music playback controls. Dreadful. Seems like some apps whitelisted but even those don't work 100% of the time. PocketCasts (even latest version from 2 days ago) works basically never, meaning i need to unlock phone to pause. A total joke.
2. Notifications. Lock screen shows them once and once only. As soon as i unlock, all notifications are not shown again on lock screen, unlike normal Android.
For those that "don't have issue with the notifications"... Do you see what i see?
Click to expand...
Click to collapse
I think what you have are two types of people on here...Not two software versions. You have people that have given up on the phone and people who are justifying their purchase...lol
Sent from my XT1635-02 using Tapatalk
Since I got the phone, while in pocket, I reject/answer 80% of the calls. I was under the effect of "yay nexus is back, google finally gave us a cheapster" so didn't really got bothered. But days are passing by and it's getting quite annoying, so to the point, could anybody tell me why this phone wakes up the screen on incoming calls when the proximity sensor is covered (ie. in pocket?) (if it's "normal" to do so, then why?). Proxi switch is fine, it triggers during calls and shows activity on sensor testing apps and whatnot. Default calls screen and whatsapp incoming calls, (heck I can unlock the phone with the fingerprint reader in my pocket without taking it out, now explain that.) ... Cherry on top the "slide to answer" thingy is vertical, so yeah there is the problem (while sliding it out from the pocket, it answers or rejects the call). I'm considering throwing it out lol it's so annoying lately. Android 9 was the same? (I had 3 android one phones to fill the superexpensive 3 generation pixel gap) Was I living under a rock? Can anyone try it? Thanks for the helpful inputs in advance.
strapabiro said:
Since I got the phone, while in pocket, I reject/answer 80% of the calls. I was under the effect of "yay nexus is back, google finally gave us a cheapster" so didn't really got bothered. But days are passing by and it's getting quite annoying, so to the point, could anybody tell me why this phone wakes up the screen on incoming calls when the proximity sensor is covered (ie. in pocket?) (if it's "normal" to do so, then why?). Proxi switch is fine, it triggers during calls and shows activity on sensor testing apps and whatnot. Default calls screen and whatsapp incoming calls, (heck I can unlock the phone with the fingerprint reader in my pocket without taking it out, now explain that.) ... Cherry on top the "slide to answer" thingy is vertical, so yeah there is the problem (while sliding it out from the pocket, it answers or rejects the call). I'm considering throwing it out lol it's so annoying lately. Android 9 was the same? (I had 3 android one phones to fill the superexpensive 3 generation pixel gap) Was I living under a rock? Can anyone try it? Thanks for the helpful inputs in advance.
Click to expand...
Click to collapse
There is no pocket mode on stock firmware. If you'd like to add one you can use Edxposed and the dark tricks module.
Sent from my Google Pixel 3a XL using XDA Labs
As hard as I'm trying, I start to see it's nearly impossible to be completely satisfied with the stock android experience. I gave up rooting, flashing, modding long time ago. Ain't got time for that. This leaves one choice, a sad but with time will get used to it.
strapabiro said:
As hard as I'm trying, I start to see it's nearly impossible to be completely satisfied with the stock android experience. I gave up rooting, flashing, modding long time ago. Ain't got time for that. This leaves one choice, a sad but with time will get used to it.
Click to expand...
Click to collapse
Do all 3a do this? I am looking into buying one but don't want to deal with something like that. This is exactly the reason I decided not to buy Galaxy S10e - just try to Google "S10 proximity sensor". It was never officially acknowledged/fixed by Samsung and over the time people just seem to "get used to it" and stop talking about it.
I don't know mate, that's why I asked others to try it please, it's really getting on my nerves and funny thing is, these kind of problems are a hit or miss on warranty claims ... doesn't even worth to try ... and I don't want to take this to reddit either because it'll only get downvoted to a lower than hell level by biased fanboys not to mention the google product forums with the "platinum product experts" and their generic "try this and try that" answers.
So yeah I'm angry.
strapabiro said:
I don't know mate, that's why I asked others to try it please, it's really getting on my nerves and funny thing is, these kind of problems are a hit or miss on warranty claims ... doesn't even worth to try ... and I don't want to take this to reddit either because it'll only get downvoted to a lower than hell level by biased fanboys not to mention the google product forums with the "platinum product experts" and their generic "try this and try that" answers.
So yeah I'm angry.
Click to expand...
Click to collapse
I never had issues, but probably I don't understand the issue yet, so I have a question: how do you know screen is waking up in pocket? For sure it's waking up if you move the device, i.e. take is off the table or turn it around. Are you sure screen switches on in the pocket and not while you are taking it out?
AndDiSa said:
I never had issues, but probably I don't understand the issue yet, so I have a question: how do you know screen is waking up in pocket? For sure it's waking up if you move the device, i.e. take is off the table or turn it around. Are you sure screen switches on in the pocket and not while you are taking it out?
Click to expand...
Click to collapse
You can test by trying to unlock the device while covering the proximity sensor.
Without any mods it'll unlock.
But like that's the main benefit to a Google phone running stock firmware. It's a perfect base for mods.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
You can test by trying to unlock the device while covering the proximity sensor.
Without any mods it'll unlock.
But like that's the main benefit to a Google phone running stock firmware. It's a perfect base for mods.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
This ... Or cover like 80% of the screen, leave only a small bar uncovered on the lower part of the phone (usbc port side) and ask someone to call you. You'll see on the remaining uncovered part that the screen woke up which is hilarious. Honestly at this point I don't understand how a feature like this can be overlooked by r&d.
Sadly modding is no option for me, for safety and other reasons.
There is another thread about this in the 3a xl section, hope it doesn't count as duplicate.
strapabiro said:
Sadly modding is no option for me, for safety and other reasons.
Click to expand...
Click to collapse
What reasons? This is a Google phone. You're allowed to unlock the bootloader and flash modified software without breaking warrantee.
If you have issues, it's easy to just flash the factory image back to completely stock and relock the bootloader.
Sent from my Google Pixel 3a XL using XDA Labs
@strapabiro,
Have you tried this app?
Skittles9823 said:
What reasons? This is a Google phone. You're allowed to unlock the bootloader and flash modified software without breaking warrantee.
If you have issues, it's easy to just flash the factory image back to completely stock and relock the bootloader.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
You're shifting the subject, but the short answer is, imagine I never had an apple product in my life but I rather buy an iphone than start doing that But that's me and that's another topic like I said, thanks though.
strapabiro said:
You're shifting the subject, but the short answer is, imagine I never had an apple product in my life but I rather buy an iphone than start doing that But that's me and that's another topic like I said, thanks though.
Click to expand...
Click to collapse
Fair argument.
Sent from my Google Pixel 3a XL using XDA Labs
Today I had my phone in my coat pocket at an appointment for about an hour hanging on a coat rack not even being touched. When I came back to, the screen was on, on the lock screen, and if was pretty warm with battery down a good 25 percent. I'm wondering if what you're talking about here has something to do with this? I was confused why or what was going on with it. No unusual apps were in memory in developer settings.
kc6wke said:
@strapabiro,
Have you tried this app?
Click to expand...
Click to collapse
I have found this "feature" annoying as well on my 3a XL. However I tired the app that you suggested and it seems to work fine. Thanks for providing a decent solution to the OPs question.
Hello,
I’m using the Xperia 5 since this Wednesday (for two days).
My overall experience with phone is mostly good (for most parts of using even perfect). Unfortunately, these nice words do not apply for the fingerprint sensor.
It usually takes 2-5 tries to unlock the phone, sometimes I can’t even open the phone with the fingerprint scanner at all. (The error messages are: Not recognized; could not process fingerprint, please try again. Sometimes it says something with "partial fingerprint").
I tried rebooting recalibrating the fingerprint with the wizard then rebooting again. Nothing seems to help. I know this doesn’t have to be eventually a defect or something. Fyi, my thumb is not moist or oily, same thing applies for the reader. Maybe my thumb is just too wide, I don’t know.
What’s your overall experience?
Jakub
Same experience. Worst fingerprint reader I've used.
Same here, IMHO the worst fingerprint sensor I've ever used on a device.
googam said:
Hello,
I’m using the Xperia 5 since this Wednesday (for two days).
My overall experience with phone is mostly good (for most parts of using even perfect). Unfortunately, these nice words do not apply for the fingerprint sensor.
It usually takes 2-5 tries to unlock the phone, sometimes I can’t even open the phone with the fingerprint scanner at all. (The error messages are: Not recognized; could not process fingerprint, please try again. Sometimes it says something with "partial fingerprint").
I tried rebooting recalibrating the fingerprint with the wizard then rebooting again. Nothing seems to help. I know this doesn’t have to be eventually a defect or something. Fyi, my thumb is not moist or oily, same thing applies for the reader. Maybe my thumb is just too wide, I don’t know.
What’s your overall experience?
Jakub
Click to expand...
Click to collapse
I got it working but putting my finger along the side of it and not by using the thumb having the finger pointing out from the phone.
Mine works almost every time now.
But it is indeed not the best scanner.
Sent from my [device_name] using XDA-Developers Legacy app
japkoslav said:
Same here, IMHO the worst fingerprint sensor I've ever used on a device.
Click to expand...
Click to collapse
So, you didn't use Z5 series. That was the worst fingerprint sensor. Fingerprint sensor didn't work more than it worked. This one on 5 is better but not good. Sometimes it doesn't work at all.
I have the same issue as well, as do many others evident from Sony Forums however the FPS works fine Banking apps, website logins etc
tomo100brt said:
So, you didn't use Z5 series. That was the worst fingerprint sensor. Fingerprint sensor didn't work more than it worked. This one on 5 is better but not good. Sometimes it doesn't work at all.
Click to expand...
Click to collapse
I didn't use a Sony phone with fingerprint sensor before
I am kinda used to finger print sensor being 99,99% accurate and reliable (iPad, Meizu, Nokia, LG, Samsung, Asus, Xiaomi etc.) so that's why I am surprised it can implemented so poorly. :silly:
Honestly after 2 weeks with this phone, I'm beginning to question whether it has a fingerprint scanner at all. Feel like I may as well just remove my fingerprints and forget it exists.
Tricky547 said:
Honestly after 2 weeks with this phone, I'm beginning to question whether it has a fingerprint scanner at all. Feel like I may as well just remove my fingerprints and forget it exists.
Click to expand...
Click to collapse
I sold mine last week, of same reasons. Useless fp, might as well be non existent.
I had to retrain myself with how to use the finger print scanner. With other phones, I'm used to using the tip of my finger, but that doesn't work with this scanner. As HellRoot describes above, I now lay the flat part of my finger against the scanner so that my finger is parallel to the phone (not pointing at an angle). Now I can get it to work very reliably.
thsieh said:
I had to retrain myself with how to use the finger print scanner. With other phones, I'm used to using the tip of my finger, but that doesn't work with this scanner. As HellRoot describes above, I now lay the flat part of my finger against the scanner so that my finger is parallel to the phone (not pointing at an angle). Now I can get it to work very reliably.
Click to expand...
Click to collapse
Sadly not working for me at all.
Not to mention I encountered "flip case" bug when the phone is refusing to accept touch screen input to take a call.
This "Sony experience" is much more frustrating than I ever expected and that comes from a guy that used LG V30 for 2 years.
If they do not fix software issues with Android 10 update, I will seriously give it to my mom or wife and buy a propper phone.
My FP sensor worked perfectly for two weeks, I did not get a single "Partial FP detected" and was wondering what's with the bad press.
Then, gradually over the course of a day, it's started playing up. Now I'm in line with everyone else, frustrating experience at less than 20% hit rate. Android 9 or 10 doesn't seem to make a difference, tried factory resetting etc.
Checking the Service Menu (*#*#7378423#*#* from the Dialler --> Service Tests --> Fingerprint Test) returns the following:
Fingerprint Sensor Status:
Sensor not OK
Sensor HWID:
0x0603
I can't seem to find more information on this error code, contacting Sony has returned the typical "Are you running the latest software?" and "Have you tried restarting your device?"
vlad_kfv said:
My FP sensor worked perfectly for two weeks, I did not get a single "Partial FP detected" and was wondering what's with the bad press.
Then, gradually over the course of a day, it's started playing up. Now I'm in line with everyone else, frustrating experience at less than 20% hit rate. Android 9 or 10 doesn't seem to make a difference, tried factory resetting etc.
Checking the Service Menu (*#*#7378423#*#* from the Dialler --> Service Tests --> Fingerprint Test) returns the following:
Fingerprint Sensor Status:
Sensor not OK
Sensor HWID:
0x0603
I can't seem to find more information on this error code, contacting Sony has returned the typical "Are you running the latest software?" and "Have you tried restarting your device?"
Click to expand...
Click to collapse
Right you are! Mine says the same. Has this been posted on the Sony forums?
vlad_kfv said:
My FP sensor worked perfectly for two weeks, I did not get a single "Partial FP detected" and was wondering what's with the bad press.
Then, gradually over the course of a day, it's started playing up. Now I'm in line with everyone else, frustrating experience at less than 20% hit rate. Android 9 or 10 doesn't seem to make a difference, tried factory resetting etc.
Checking the Service Menu (*#*#7378423#*#* from the Dialler --> Service Tests --> Fingerprint Test) returns the following:
Fingerprint Sensor Status:
Sensor not OK
Sensor HWID:
0x0603
I can't seem to find more information on this error code, contacting Sony has returned the typical "Are you running the latest software?" and "Have you tried restarting your device?"
Click to expand...
Click to collapse
I just got mine yesterday, pretty much everything work perfectly except for the fingerprint, and mine also show the same Service Tests info as yours.
When I scan my finger, it usually register only at certain angle, and usually only at my 2nd press on the scanner, which is quite frustrating
I really wonder if this is a software bug or hardware problem so I can have the store replace a new one.
thatguy222 said:
Right you are! Mine says the same. Has this been posted on the Sony forums?
Click to expand...
Click to collapse
Thanks, that's a good point :highfive:
I just raised it on the Xperia Support Forum, fingers crossed it gets enough traction for Sony to look into it!
japkoslav said:
I will seriously give it to my mom or wife and buy a propper phone.
Click to expand...
Click to collapse
You must be hating your mom and wife with a passion
yekollu said:
You must be hating your mom and wife with a passion
Click to expand...
Click to collapse
Thank you It made my day.
But seriously they do not mind to use not so reliable devices. Xperia 5 is still an upgrade for Xiaomi Note 4 or Asus M1 Pro user.
palkia171993 said:
I just got mine yesterday, pretty much everything work perfectly except for the fingerprint, and mine also show the same Service Tests info as yours.
When I scan my finger, it usually register only at certain angle, and usually only at my 2nd press on the scanner, which is quite frustrating
I really wonder if this is a software bug or hardware problem so I can have the store replace a new one.
Click to expand...
Click to collapse
It appears to be Software. I have issues only with unlocking the screen. The Banking apps seem to work fine (for now)
yekollu said:
It appears to be Software. I have issues only with unlocking the screen. The Banking apps seem to work fine (for now)
Click to expand...
Click to collapse
That's good to hear. I suspect so too because the service tests show everything was fine when I first bought the phone (it was running Pie at the time) and I started upgrading to Q soon afterward. And it was the 2nd day after I upgraded to Q that I notice the service test "Not OK" info.
Hope it can be fixed in the near future update and off topic: hope that update will also include patch for third party launcher to work with Q's Gesture (my most annoyed thing about Q)
Edit: After a few days using it, I realize it recognize the finger really well at certain angles. It never scans well with full finger but almost never miss when I use my finger tip or side. So I guess I can live with it for now. But still hope for improvement soon.
Well, other Xperias like XZ2, XZ3, XZP just got updated to 10 recently. And, all I've seen so far are complaints about 2 things: no swipe gesture (because the stock launcher hasn't been updated, which is rather stupid) and fingerprint on those devices all become less responsive. It took many times pressing to work, which sounds just like our problem.
So I guess this is a software based problem from Sony's side. Maybe some bad fingerprint driver I guess. Anyway, hope Sony is aware of this and get it fix soon with December security update (also hope for third party launcher patch too)
My fingerprint reader keeps disabling. I have to turn phone off and back on (reboot is not enough). However then all the apos detect a Biometrics change and I have to reenable fingerprint login for each app.
Even when it works the reader is super sensitive and keeps telling me I've had too many attempts before i pick up the phone.
While I do get the too many attempts thing I haven't had the fingerprint reader disable on my phone
For me its working just perfectly.
It works perfectly for me as well. I have found that using a case helps a lot with false reading attempts.
I also use a slim case and I'm having a very positive experience with the fingerprint reader.
Coming from a Pixel 2 XL with a reader at the back, it took me a few days to get used to thumb based unlock.
But now, I find it much more reliable than the Pixel 2 XL reader, where fingers moisture was a real pain.
Same hands (different finger being used on the 5ii and it works almost 100% of the time (and quick too).
Stock ROM and launcher.
arturiu said:
I also use a slim case and I'm having a very positive experience with the fingerprint reader.
Coming from a Pixel 2 XL with a reader at the back, it took me a few days to get used to thumb based unlock.
But now, I find it much more reliable than the Pixel 2 XL reader, where fingers moisture was a real pain.
Same hands (different finger being used on the 5ii and it works almost 100% of the time (and quick too).
Stock ROM and launcher.
Click to expand...
Click to collapse
What case are you using?
also my fingerprint sensor is absolutely flawless I haven't had any issues or anything that has caused me to be concerned or despised the fingerprint sensor. maybe I'm lucky or maybe I just knew how to set the fingerprint up properly I don't know but my experience with it has been positive
thepersona said:
What case are you using?
Click to expand...
Click to collapse
https://www.amazon.co.uk/GEEMEE-Waterproof-Anti-Scratch-Protective-Transparent/dp/B08H5931YQ
arturiu said:
https://www.amazon.co.uk/GEEMEE-Waterproof-Anti-Scratch-Protective-Transparent/dp/B08H5931YQ
Click to expand...
Click to collapse
Damn it doesn't appear that that case is available in Canada or even the US. Oh well hopefully more cases turn up when the device releases in the US
Try adding the same finger a few times. I haven't had any problems since I did that.
Do you also have this issue, that while calling, you accidentally click on the fingerprint sensor and so activate the screen while it is 'at your ear' and so you 'click' on several options and so on? It happens a lot, I have accidentally adjusted with my ear the brightness or paused the call etc. Very annoying!
I struggled a bit at first to have my fingerprint recognized when trying to unlock, often ending up typing my pin instead.
I noticed a huge improvement by sliding my thumb upwards on the sensor, instead of just pressing it still. Now works almost all the times.
November update might have improved the situation as well.
Not sure if it's something to do with a recent update but my reader is not recognising my fingerprints very well at all now. Anyone seen problems?
The other potential issue is that I've been doing a lot of DIY lately and probably worn away some of the detail on my finger ends .
wazzaworld said:
Not sure if it's something to do with a recent update but my reader is not recognising my fingerprints very well at all now. Anyone seen problems?
The other potential issue is that I've been doing a lot of DIY lately and probably worn away some of the detail on my finger ends .
Click to expand...
Click to collapse
Mine still on 58.0.A.22.21 as it's US variant but recently I am also facing issues with fingerprint scanner if the phone is in (deep?) sleep mode. Earlier it used to be just touch and go but now had to press it or try multiple time to unlock it.
Not sure what's the issue here?
No problems with my FPR. Occasionally it requires a couple of tries but that's true of every single phone on the market.
Mine seems to be working well. I am coming from a P30 Pro with the underscreen sensor, and I had a few Xperias before that. This is by far the fastest Android fingerprint sensor I've used. it seems to instantly recognize everything. It's probably on par with my pre-face ID iPhones, but i don't have one of those anymore to compare it.
I ended up disabling the fingerprint reader completely. Never works from first try when I need it, but somehow easily unlocks when I actually don't need it, as in when just holding it, putting down or in pocket. Also all those buttons on the same side is a really poor design choice, specially power right under volume. Btw, is there a way to disable the assistant button?
hovikg said:
I ended up disabling the fingerprint reader completely. Never works from first try when I need it, but somehow easily unlocks when I actually don't need it, as in when just holding it, putting down or in pocket. Also all those buttons on the same side is a really poor design choice, specially power right under volume. Btw, is there a way to disable the assistant button?
Click to expand...
Click to collapse
Everything I have read, says there's no way to disable it. I'm very surprised I have yet to activate accidentally. But, that might be because the button covers on my case are kind of stiff.
hovikg said:
Never works from first try when I need it, but somehow easily unlocks when I actually don't need it, as in when just holding it, putting down or in pocket.
Click to expand...
Click to collapse
I get the exact same behavior. Very frustrating. Totally disappointed with the fingerprint scanner.
hovikg said:
Btw, is there a way to disable the assistant button?
Click to expand...
Click to collapse
You can disable the assistant app. But if course this is only a solution if you don't use the Google assistant at all.
My favorite fingerprint reader was the Pixel 3 with the reader on the back of the phone. My least favorite has been the under-screen readers on my Huaweis. The reason is less accuracy and fingerprints.
I've had my Xperia 5 ii for a day, and have been on it a lot, and the fingerprint reader has been excellent. My problem is finding it and not dropping the phone while I look.