[Discussion] Face Recognition doesn't work after Android 10 update - Samsung Galaxy A7 (2018) Guides, News, & Discussio

As the title says, face recognition doesn't work (model SM-A750FN) after updating to Android Q. Front camera works fine, but when you are on the lock screen or trying to register your face again it asks for a reboot, which does not fix this issue.
Probably a factory reset would make it work again, but I don't want to try it — because of laziness. Or maybe a new update would fix it. I am wondering if I am the only one experiencing this issue.
My firmware belongs to the Spain (PHE) provider.

Not recommended to upgrade from 9 to 10 because 10 is buggy.

I had the same problem but i solve it by factory reseting a7 2018 and face recognition work great after reseting it.

Related

Honor 8 gyro or accelerometer bug?

Hi,
i've noticed a very boring bug, sometimes the screen rotation won't work untill i reboot the phone; after reboot it's all fine untill the bug appear again.
Had it in B360 and also now in B131 (i've done a rollback).
Hard reset/cache clean already done and nothing changed, any advice? It's a known bug?
I did not have this bug on Android 6 but since update to Android 7 I too have this. Like yourself a reboot corrects this bug for a time.
I have reported this to Huawei Honor via feedback and email.
Their reply was this is a feature of the OS..
Yeah for real my reply was not nice let's just say until I emailed a reply with the problems once again.. Just goes to show they don't read the full details laid out when reporting issues..
You should just send them an email with your problem via email from within the HiCare app (Service > Feedback>email)
Same issue here. I bought my Honor 8 last week, and now my accelerator is only working for few minutes after reboot. Firmware is B131. Is this an software or hardware issue?
I have the same problem (smartphone is 2 weeks old, FRD-L19, B360).
Sometimes it occurs daily. Sometimes not for some days.
This is really strange. I did a hard reset and for now it is working again.
But you can try this:
Delete cache of compass app (in system settings) and start app again. I assume that you have to re-calibrate the compass now. Do so and make sure that calibration is successful (i.e. turning the phone in every direction)
Does this fix your issue? I assume that somehow the accelerometer/gyro is also dependent from a correctly working magnetometer.
Edit: After some days I figured out that also a hard reset is not the solution. I updated on B380 now and have no issues so far. Let's see...
Edit nr. 2: issue also occured with B380. Seems to be a software issue deep in the system. Hopefully Honor will fix this issue in the future
Probably isn't just a software bug, Honor service replied me that it could be an hardware problem came out with Nougat Update, they told me that i could have sent them the device to let investigate the problem, but i made a refund and bought another phone.
Which phone did you buy?
I don't think that this is a hardware issue as I have had this problem with Android 6 as well. Nothing is working for me yet. Will wait for my 3rd device and this will definitively be my last one...
Fozzy90 said:
Which phone did you buy?
I don't think that this is a hardware issue as I have had this problem with Android 6 as well. Nothing is working for me yet. Will wait for my 3rd device and this will definitively be my last one...
Click to expand...
Click to collapse
I switched to the dark side.... I bought an iPhone
Other thread :
https://forum.xda-developers.com/honor-8/help/auto-screen-rotation-bug-t3531119
If anyone found a solution...
Klasputnikov said:
Hi,
i've noticed a very boring bug, sometimes the screen rotation won't work untill i reboot the phone; after reboot it's all fine untill the bug appear again.
Had it in B360 and also now in B131 (i've done a rollback).
Hard reset/cache clean already done and nothing changed, any advice? It's a known bug?
Click to expand...
Click to collapse
Same here. It's definitely some software-related issue. Factory-resetting the phone solves that issue until the next system update is installed. A reboot only helps for some hours (not even days for me). I guess there's something wrong with the calibration data and that exact part is restored to it's initial state when you do a factory reset.
Found out that I have the same issue
I just found out that my gyroscope isn't working properly, for instance while using Google Cardboard app or if I'm trying to watch YouTube in cardboard mode. The strange thing with this issue is that it works perfectly fine if I'm enjoying a 360° vr photo in chrome/opera
I don't really want to downgrade my phone to previous Android version since I don't want to lose all my data...
I have realized that if I have installed "Huawei Health" app, accelerometer seems to work without freezing.
Can someone try and confirm this?
panel1 said:
I have realized that if I have installed "Huawei Health" app, accelerometer seems to work without freezing.
Can someone try and confirm this?
Click to expand...
Click to collapse
Yes its working thanks for the tip

GPS not detecting satellite

So I bought this phone a month ago, and I just noticed that it wont use waze properly or g maps for that matter. Then upon checking Phone tester, to my surprise it doesn't detect any satellites. Is there a fix for this?
I also tried other apps and look, it doesnt detect satellite
Hi there,
I'm having the same problem. At first I thought it was Google Map apps but I've tried other navigation apps as sygic, tomtom and waze, all with the same problem. When I install the GPS apps I can see the the phone is unable to lock the GPS signal. I've send the phone back to the service center and what they did was a software update (though I think what they did just hard reset the phone) but the problem still occurred. I've done the hard reset myself numerous time but no difference whatsoever.
Is this a random problem to the P20 model or is it region based problem? I've read somewhere not all the P20 is having this issue. Could this be related to Android Oreo (8.1) itself? Currently I'm on version EML-L29 8.1.0.132 (C636patch01). Mine was purchased from Maxis Malaysia. I've been thinking either to install custom firmware, downgrade to Nougat or rebrand to other region but am not sure whether it will solve the problem. Anybody else with the same problem and is there a fix for this?
I have the same problem. Tried to install other apps, did a hard reset as well... But problem still exist.
I also had the same problem, I performed a hard reset and nothing happened, I returned where I bought and they sent me a new one, it is now working correctly
send it back to Huawei service centre. I just had mine fixed. Changed motherboard, with new IMEI. 2 weeks phone. it sucks to be honest. hopefully nothing goes wrong after this. #fingercrossed

Oppo Find X2 Pro and Freestyle Libre

For my diabetes I use the Freestyle Libre system to measure my glucose levels. It works using NFC, it should work using NFC. Sadly it only works a few times out of every 10 times I try. Sometimes the Oppo reads my glucose levels with no problem but usually it is just a miss and miss scenario.
Sometimes turning NFC off and on resolves the issue, sometimes powering the Oppo off completely resolves the issue, but several times the seemingly only option was to do a factory reset , reinstalling everything again, whereafter it works a few days, when the same problem reappears again.
As you can imagine, not something that makes me happy. Anyone out here who recognizes these NFC problems, and has a solution, or a way to make it work more reliable. Every other NFC operations seem to work okay, but this one is really bugging me, especially as it is important with regards to my wellbeing. i am using a fully updated Oppo Find X2 Pro.
On my previous phone, a Samsung S9+, i had no issues at all.
I'm so glad someone else also has this issue!
I was about to start a similar thread.
I have a lot of issues scanning my libre and it hardly ever works!
Can anyone help locate the exact location of the NFC sensor. I have watched Jerry rigs everything teardown but he did not mention where exactly it is located.
If someone could give me the exact grid number from this grid I've created I'd be very grateful!
CheopsChefren said:
For my diabetes I use the Freestyle Libre system to measure my glucose levels. It works using NFC, it should work using NFC. Sadly it only works a few times out of every 10 times I try. Sometimes the Oppo reads my glucose levels with no problem but usually it is just a miss and miss scenario.
Sometimes turning NFC off and on resolves the issue, sometimes powering the Oppo off completely resolves the issue, but several times the seemingly only option was to do a factory reset , reinstalling everything again, whereafter it works a few days, when the same problem reappears again.
As you can imagine, not something that makes me happy. Anyone out here who recognizes these NFC problems, and has a solution, or a way to make it work more reliable. Every other NFC operations seem to work okay, but this one is really bugging me, especially as it is important with regards to my wellbeing. i am using a fully updated Oppo Find X2 Pro.
On my previous phone, a Samsung S9+, i had no issues at all.
Click to expand...
Click to collapse
Is this issue still present on Android 11 for you? My issue still persists even on a factory reset
Have you found solution. I have the Same problem with OPPO reno 4 z
I have bought an Oppo Find X3 Lite this weekend. Same issue. Anybody has a solution already for the above? I imagined only NFC would be enough but why is it that the Oppo phone does not connect with the scanner? Any idea anybody?
I got the Android 11 update for Oppo Reno 10x Zoom, and my Freestyle Libre 2 Sensors stopped working with the phone. When I try to scan, the NFC service hangs and NFC will not work anymore untill phone restart.
Oppo told me it is a known problem and they will try to fix it in a new firmware update. God knows when.
THANX A LOT, OPPO! Now I have to carry around the ****ty Freestyle reader all the time!
Hi Everyone. I had this issue and called ABBOT. Got a fix which now works. In your phone settings go to the libre link app and clear the cache data. Restart your phone and voila it works!

Xz3 - 52.1.A.0.672 RU version

Xperia XZ3 (H9493) - 52.1.A.0.672 - RU version
Notification seek bar bug - STILL!!! – If I’m playing media through chrome, soundcloud or another app, the notification seek bar does not work in most situations. This has been a bug since the initial Android 10 roll out and I’m still shocked that we’re still going through this.
Swipe up from the lock screen – I’ve noticed this since the update from Android 9 to 10. It used to be a quick flick of the thumb where I could go from the notifications on the lock screen to the security pattern. Now since the A10 update, I can’t do that anymore. It is a longer swipe, more exaggerated swipe to get to the security options. It was easier with 1 hand before and it needs to go back to whatever it was in Android 9
Camera – Still gives error unknown error. It’s MUCH EASIER to fix than the first and second android 10 releases but it still shouldn’t be like this. It’s at the point where I don’t know if it’s an actual software or hardware problem. And with everything that’s going on, I probably won’t be able to confirm for the next 6 months. I'll probably end up wasting$200 fixing the hardware, that was really a software issue all along.
Fingerprint – Good, I believe either at or close to Android 9 speed
Battery – Good
Networking issues – I believe better than the last update. It seems good so far so
No idea why the software version has to be in the notification quick settings. That doesn’t need to be there. It’s out of place/doesn't add value by being there
I am so frustrated by Sony. They’re taking steps to fix this but damn you should have been on the ball. I do a clean install each update because I don't trust Sony to do this correctly.
This phone is like the Renault Formula 1 team. It's a great product and each update is a step further but holy **** you all should have been a lot farther along by now. Now Mclaren (One Plus) is starting to pass you.
Edit: I forgot to add this earlier. I found a bug by random. In dark mode, About phone -> Emergency Information, the notification bar text is black. So you've got a dark screen with black text.
I still have not received an air update on my H9493. my software version is still 532.
Wa1ker_ru said:
I still have not received an air update on my H9493. my software version is still 532.
Click to expand...
Click to collapse
I too haven't received an update since December on my xz3 h9493 my version is 532
kaderzaim said:
I too haven't received an update since December on my xz3 h9493 my version is 532
Click to expand...
Click to collapse
In the morning I received an update with the numbers 618
Wa1ker_ru said:
In the morning I received an update with the numbers 618
Click to expand...
Click to collapse
I too received it this morning and I'm still waiting for the 672
supervf1s said:
Xperia XZ3 (H9493) - 52.1.A.0.672 - RU version
Notification seek bar bug - STILL!!! – If I’m playing media through chrome, soundcloud or another app, the notification seek bar does not work in most situations. This has been a bug since the initial Android 10 roll out and I’m still shocked that we’re still going through this.
Swipe up from the lock screen – I’ve noticed this since the update from Android 9 to 10. It used to be a quick flick of the thumb where I could go from the notifications on the lock screen to the security pattern. Now since the A10 update, I can’t do that anymore. It is a longer swipe, more exaggerated swipe to get to the security options. It was easier with 1 hand before and it needs to go back to whatever it was in Android 9
Camera – Still gives error unknown error. It’s MUCH EASIER to fix than the first and second android 10 releases but it still shouldn’t be like this. It’s at the point where I don’t know if it’s an actual software or hardware problem. And with everything that’s going on, I probably won’t be able to confirm for the next 6 months. I'll probably end up wasting$200 fixing the hardware, that was really a software issue all along.
Fingerprint – Good, I believe either at or close to Android 9 speed
Battery – Good
Networking issues – I believe better than the last update. It seems good so far so
No idea why the software version has to be in the notification quick settings. That doesn’t need to be there. It’s out of place/doesn't add value by being there
I am so frustrated by Sony. They’re taking steps to fix this but damn you should have been on the ball. I do a clean install each update because I don't trust Sony to do this correctly.
This phone is like the Renault Formula 1 team. It's a great product and each update is a step further but holy **** you all should have been a lot farther along by now. Now Mclaren (One Plus) is starting to pass you.
Edit: I forgot to add this earlier. I found a bug by random. In dark mode, About phone -> Emergency Information, the notification bar text is black. So you've got a dark screen with black text.
Click to expand...
Click to collapse
Same here like a attached photo
Camera unknown error most of the time
Very sometime good again .but I can't
find anyway to slove that problem.I tried to clear cached clear data forced stop disabled
and restart still have that unknown error
After that I flashed stock ftf 10.0
again with full wiped and then repair software with PC suited also wasting time
Please give me any ideas guys thz
PS Xz3 H9493 .618
kokokmt said:
Same here like a attached photo
Camera unknown error most of the time
Very sometime good again .but I can't
find anyway to slove that problem.I tried to clear cached clear data forced stop disabled
and restart still have that unknown error
After that I flashed stock ftf 10.0
again with full wiped and then repair software with PC suited also wasting time
Please give me any ideas guys thz
PS Xz3 H9493 .618
Click to expand...
Click to collapse
It's possible it's a hardware problem. It happens to me too but it was worse with the initial A10 update. My understanding is if you squeeze beside the camera when turning the phone, it can solve the issue. This is because it's a possible loose ribbon.
The initial A10 release was terrible so flash up to .672 and it may fix the problem (if it's a software issue)
supervf1s said:
It's possible it's a hardware problem. It happens to me too but it was worse with the initial A10 update. My understanding is if you squeeze beside the camera when turning the phone, it can solve the issue. This is because it's a possible loose ribbon.
The initial A10 release was terrible so flash up to .672 and it may fix the problem (if it's a software issue)
Click to expand...
Click to collapse
I really appreciated your reply I'm so confused that problem is hardware or not.Coz I got back my camera very sometime but after few days
It happened again ??? and also I found
another user reported that bugs at Sony'
Discussion and any other places when they upgraded to A10.Another problem is
My device is H9394 Dual So latest ver
Of A10 is .618 . Ver 672 is not yet for my
Region thz
PS Now I tried to downgraded android 9
If Downgrade is fix this problem I will
let you know
kokokmt said:
I really appreciated your reply I'm so confused that problem is hardware or not.Coz I got back my camera very sometime but after few days
It happened again and also I found
another user reported that bugs at Sony'
Discussion and any other places when they upgraded to A10.Another problem is
My device is H9394 Dual So latest ver
Of A10 is .618 . Ver 672 is not yet for my
Region thz
PS Now I tried to downgraded android 9
If Downgrade is fix this problem I will
let you know
Click to expand...
Click to collapse
Hey I am also facing this problem on my xz3 dual. Failed to restart the camera is consistently occuring in the past few weeks but restarting the phone worked then. But now its been almost 2 days, camera app says unknown error, I tried everything mentioned above but still unable to resolve the issue. Kindly let me know if downgrading the firmware resolves the issue.
Thank you
Camera unknown error issue
Splinter07 said:
Hey I am also facing this problem on my xz3 dual. Failed to restart the camera is consistently occuring in the past few weeks but restarting the phone worked then. But now its been almost 2 days, camera app says unknown error, I tried everything mentioned above but still unable to resolve the issue. Kindly let me know if downgrading the firmware resolves the issue.
Thank you
Click to expand...
Click to collapse
Of course
I am waiting to downgrade 9
But it was delay coz of covid 19
I can not go to any service center.
Because I can't downgrade it myself .
I hope that problem is software issue .
After downgrade to android 9
That problem can fix or not I will
let you know
Thank you
It is not a software problem for my device
Splinter07 said:
Hey I am also facing this problem on my xz3 dual. Failed to restart the camera is consistently occuring in the past few weeks but restarting the phone worked then. But now its been almost 2 days, camera app says unknown error, I tried everything mentioned above but still unable to resolve the issue. Kindly let me know if downgrading the firmware resolves the issue.
Thank you
Click to expand...
Click to collapse
Today I downgrade my Xz3 H9493 to android
9 but my camera didn't get back.So I decided
to check hardware.that is really sad.
Coz I have to take out all water proof
Seal from my back cover .After that I found
my Camera connector is loose.That's why
occurring unknowm error and after
2 or 3 days is good again.At last that is
not a software error at all.
I got error while enabling tethering
Anyone else?
I'm having signal issues. Dropping connection all the time. Latest firmware hurt this badly.
Same SIM on a Samsung A30S on android 9 works fine.
Hello guys. I need your help finding 52.1.A.0.618 for H9436

Question Fingerprint enrollment failed after display replacement

Please help, this is driving me nuts. here's briefly what's going on:
- Bought a Rog Pone 5s with a broken display. Found a 6 months old dead Rog Phone 5 - motherboard died of overheating. Quick disassembly-assembly and had a nice working phone.. but...
- I'm facing an issue with the fingerprint - Fingerprint enrollment failed immidiately after i try to register one. This is happening on Android 11. On Android 12 the fingerprint registration process starts, but the phone deasn't register my fingerprint no matter how i try.
- i found the calibration procedure video here on XDA, ordered the tool (still haven't received it) and downloaded the app. The app installs under both Android 11 and 12, and i tried to two pieces of paper - at least to try to get the fingerprint working until i get my tool. But nothing happens, calibation procedure passes and fingerprint is still not registered at all - the phone doesn't even try to read it.
- i double-checked all connections and flex cables inside the phone - all seems fine. I also tried some apps which are supposed to test the fingerprint - one of them directly shuts down with an error, anotherone reports fingerprint sensor is in use. Built-in test accessible through .12345+= says test is passed.
- do i need to be on a specific firmware to be able to correctly calibrate the sensor? if yes how can i downgrade to this firmware from the latest Android 11? i'm able to successfully downgrade fom 12 to 11 using Asus's "special" firmware for downgrade, but i don't know how to downgrade to an earlier Android 11.
- i saw that other phone brands/models are having similar issues with fingerprint sensor. are there any general instrustions on how to fix this? is calibration the only method?

Categories

Resources