Galaxy A5 2017 (A520) Proximity sensor not working after upgrade to Nougat 7.0

Sep 6, 2017
7
0
0
Problem:
Hello, I have updated my Galaxy A5 2017 to the newest software Nougat 7.0 that was released yesterday. Since then I am having problems with the proximity sensor. The screen does not turn off during calls.
What I have tried:
I have dialed *#0*# and selected Sensor. The Proximity sensor shows 0.0 even when I cover it. ADC number vary from 23-35 and when I cover the sensor it is 255. Restarting my phone solves the problem but just for some time and not always. On restarted phone the proximity sensor shows 1.0
 
Thank you B. Daddy for your reply. Yesterday I made Factory data reset and until today everything was working properly, but this morning again the sensor is not responding.
I followed your instruction and entered the Recovery mode, I got message "E:failed to find /misc partition" but the wipe cache was successful.
For now the sensor is back on, but we will see for how long. For any changes I will make sure to update this thread.
 
I entered the safe mode and used my phone almost all day like that, but the same problem appears again after couple of hours. Then I restarted the device and the sensor works again for some time. So we are back to square one :(
Do you think it's good idea to downgrade the software back to marshmallow? I think I can do this without rooting my phone if I am correct.
 
Problem:
Hello, I have updated my Galaxy A5 2017 to the newest software Nougat 7.0 that was released yesterday. Since then I am having problems with the proximity sensor. The screen does not turn off during calls.
What I have tried:
I have dialed *#0*# and selected Sensor. The Proximity sensor shows 0.0 even when I cover it. ADC number vary from 23-35 and when I cover the sensor it is 255. Restarting my phone solves the problem but just for some time and not always. On restarted phone the proximity sensor shows 1.0


I have the same exact problem on my A5(2017), tried everything like B.Diddy said, no success
 
The last thing that I have tried was to go to Settings -> Apps -> Show system apps and uninstall the updates from all of the stock apps. But no luck there either
 
You guys have no idea how greatful I'm that someone else is having the exact same issue as me.
I was literally ready to reinstall the Marshmallow software back. I already download everything I need to do it and then I decided: "let me do one last search about it...", and I found this post lol.
I also already tried everything listed here in the replies and didn't work. I have the A5 2017 A520F model, and this issue is annoying me. It started when I update to the Nougat firmware. I was wondering if someone else has had the same problem. I hope we can found a fix for it soon, or at least that Samsung release a update with a fix.
 
I the weekend i had no problem, thought the issue was gone.
But it all came back yesterday. In my case it sems that when i use the bt connection for the car kit the problem reapears
Any ideas?
 
I the weekend i had no problem, thought the issue was gone.
But it all came back yesterday. In my case it sems that when i use the bt connection for the car kit the problem reapears
Any ideas?

Hey!

I have this issue in my A5 (2017) [SM-A520F/DS] and I solved it with this folliwing steps:

1) Factory Reset (Setting>General>Restore>Factory Default)
2) Hard Reset (from boot menu)
3) Clear cache data (from boot menu)
4) Start phone without Samsung Cloud backup
 
As I mentioned before, nothing worked for me and I hope that with the next update this will be fixed. I have found alternative way to solve this problem. Please note that this is not permanent fix:
Go to Settings -> Accessibility -> Answering and ending calls -> End calls -> Press Power key to end calls
Make sure that this option is turned OFF, so that when you call someone or receive call press the Power button to lock your screen.
 
Hello everyone,
I have great news regarding the proximity sensor issue. I have received a new update on the 7.0 software. Hope you will get this update soon and be done with this problem. For 3 days now I have been using my device and I have not encountered the issue.
Many thanks to all of you guys and especially to B. Diddy for the fast replies.
 
got tired of waiting for a fix so I rolled back to original ROM android 6.0.1. Now all works as it should.
 
Ok the good news are that inside the next months we are getting android 8.0 and that will solve the issue. Now because nothing works I'll probably send it to Samsung for service. Hope you'll find a solution.
 

Trending Posts

Forum statistics

Threads
954,116
Messages
6,960,637
Members
3,162,925
Latest member
montesjony0611