Related
You must have ROOT to complete this process. I have been having issues with my light and proxy sensor ever since I had gone S-Off on the phone.. well tonight i decided to do some research and see if I could figure it out. I love having S2W and DT2W but without the pocket protection, you tend to turn the screen on alot when you dont want to, well some how the calibration gets changed.
there are two apps on the Play Store to help get you set up
the first will be your testing app, its called - Android Sensor Box
and the second is called - Rezound Prox Sensor Calibration
when i used the Android Sensor Box, my light sensor would never go over 40 luxes and drop to 10 luxes when I covered the sensor. and my prox sensor always said "NEAR" and would never change
Now go to the Prox Sensor Calibration app, my stock settings were 16 low and 24 high (I think), after playing around with it, I found a great sweet spot set at 40 low and 60 high, but feel free to play and see how it works for you. when done, click on "Set on Boot" and reboot the phone.
When my phone rebooted, I went back to the Sensor Box app and just under normal light conditions my light sensor was at 160 luxes and as i slowly covered the sensor it gradually went down. then i checked my prox sensor and it worked perfectly and would change from "NEAR" to "FAR" after my hand moved farther then 2 inches away. and this fixed my S2W function with working pocket protection.
I hope my frustration will help someone else out with the same issues
I just got the phone last week and it’s always had a screen protector on it. I know many have issues with the proximity sensor covered but I don’t get how the phone should work. All my other phones turn off the display as you put the phone to your ear and on again if you move it away to look at something or end the call. The Nexus 6 just stays on until the screen time out and then I have to tap the power button to get the screen back.
I installed a proximity sensor app (Proximity Sensor Finder) and it seems to work fine though I don’t know what the readings would be without the screen protector covering it. It shows 5.000305cm until my hand gets within two inches or so and it jumps to 0. The app says some sensors are discrete so seems ok and the readings are very consistent and fast. So why is the screen not turning off?
Also, the Ambient display setting says it will turn on the display when you pick up the phone or get notifications. Never worked. ???
Bad phone, software or setting?
Thanks.
P.S. Why in God’s name are the volume buttons and to a lesser extent, the power button, dead center of the phone? I hit them every flipping time I pick it up. Is there a way to disable the volume buttons when the screen is off?
Tanquen said:
I just got the phone last week and it’s always had a screen protector on it. I know many have issues with it covered but I don’t get how the phone should work. All my other phones turn off the display as you put the phone to your ear and on again if you move it away to look at something or end the call. The Nexus 6 just stays on until the screen time out and then I have to tap the power button to get the screen back.
I installed a proximity sensor app (Proximity Sensor Finder) and it seems to work fine though I don’t know what the readings would be without the screen protector covering it. It shows 5.000305cm until my hand gets within inches or so and jumps to 0. The app says some sensors are discrete so seems ok and the readings are very consistent and fast. So why is the screen not turning off?
Also, the Ambient display setting says it will turn on the display when you pick up the phone or get notifications. Never worked. ???
Bad phone, software or setting?
Thanks.
Click to expand...
Click to collapse
my suggestion would be to take your screen protector off. when you pull away from thd phone, the screen should pop on, but it not doung that for you. over the past 8 months or so, ive been reading about this same issue. and its always fixed by raking off the screen protector. im fuessing that your screen protector is covering one of your sensors.
Understood but:
"I installed a proximity sensor app (Proximity Sensor Finder) and it seems to work fine though I don’t know what the readings would be without the screen protector covering it. It shows 5.000305cm until my hand gets within two inches or so and it jumps to 0. The app says some sensors are discrete so seems ok and the readings are very consistent and fast. So why is the screen not turning off?"
Can someone without a screen protector on chime in with naked sensor readings?
Tanquen said:
Understood but:
"I installed a proximity sensor app (Proximity Sensor Finder) and it seems to work fine though I don’t know what the readings would be without the screen protector covering it. It shows 5.000305cm until my hand gets within two inches or so and it jumps to 0. The app says some sensors are discrete so seems ok and the readings are very consistent and fast. So why is the screen not turning off?"
Can someone without a screen protector on chime in with naked sensor readings?
Click to expand...
Click to collapse
Readings the same.
Tanquen said:
Understood but:
"I installed a proximity sensor app (Proximity Sensor Finder) and it seems to work fine though I don’t know what the readings would be without the screen protector covering it. It shows 5.000305cm until my hand gets within two inches or so and it jumps to 0. The app says some sensors are discrete so seems ok and the readings are very consistent and fast. So why is the screen not turning off?"
Can someone without a screen protector on chime in with naked sensor readings?
Click to expand...
Click to collapse
your phone has its own proximity sensor thats being blocked by your screen protector, probably. im telling you that of the very many that have been reporting thus issue, have no more issue when they remove the screen protector. its worth a try, isnt it?
simms22 said:
your phone has its own proximity sensor thats being blocked by your screen protector, probably. im telling you that of the very many that have been reporting thus issue, have no more issue when they remove the screen protector. its worth a try, isnt it?
Click to expand...
Click to collapse
His screen is staying on tho. Usually with screen protector it stays off.
prdog1 said:
His screen is staying on tho. Usually with screen protector it stays off.
Click to expand...
Click to collapse
for most ppl it stays off, a few that ive read stay on non stop.
for example.. if it doesnt "see" your face get close, it wont turn off the screen.
simms22 said:
for most ppl it stays off, a few that ive read stay on non stop.
Click to expand...
Click to collapse
Kewl. He needs to make sure ambient display is on in display settings. Also the buttons are in middle of phone so you can reach them holding phone normally.
simms22 said:
... its worth a try, isnt it?
Click to expand...
Click to collapse
Yea, but the protector would not be usable afterwards and it was really hard to get it on clean and lined up and the sensor readings are the same. I thought the folks that had problems had stuck or sporadic readings.
simms22 said:
for most ppl it stays off, a few that ive read stay on non stop.
for example.. if it doesnt "see" your face get close, it wont turn off the screen.
Click to expand...
Click to collapse
Mine can be toggled on and off with the power button, never gets stuck. It just acts like the proximity sensor mode during a call never activates. It only powers off after the normal screen timeout if you are still on the phone. The sensor does see me and sets the value the zero.
prdog1 said:
Kewl. He needs to make sure ambient display is on in display settings. Also the buttons are in middle of phone so you can reach them holding phone normally.
Click to expand...
Click to collapse
It’s on, even tried toggling it.
The buttons should be higher. I understand you can’t reach the power button on larger phones if on top of the phone but putting the volume at the center of gravity is crazy. It’s actually noticeably difficult to hold the phone without it dipping when grabbing it lower and that’s after training myself to grab it lower. I still forget and grab it in the middle like any brick sized object. I'm old, hands weak.
I have read here, somewhere, that the proximity sensor does not have a variable output. It's either off or on, so to speak.
Larzzzz82 said:
I have read here, somewhere, that the proximity sensor does not have a variable output. It's either off or on, so to speak.
Click to expand...
Click to collapse
Probably yes but everyone who had a screen protector without a sensor cut out had to change it for one with a sensor cut out.
This is step 1. Even if this isn't the cause, it will cause problems later.
You say not variable. Sure on or off. That said, a protector can limit how close the "close" reference can be identified at.
Step 2 is a factory reset.
Unfortunately, can't troubleshooting without doing these steps.
Larzzzz82 said:
I have read here, somewhere, that the proximity sensor does not have a variable output. It's either off or on, so to speak.
Click to expand...
Click to collapse
That is my understanding also and someone posted above that they have the same readings from the sensor without a screen protector. They did not say but I’m assuming their phone works as it should when on a call. Again: "I installed a proximity sensor app (Proximity Sensor Finder) and it seems to work fine though I don’t know what the readings would be without the screen protector covering it. It shows 5.000305cm until my hand gets within two inches or so and it jumps to 0. The app says some sensors are discrete so seems ok and the readings are very consistent and fast. So why is the screen not turning off?"
danarama said:
Probably yes but everyone who had a screen protector without a sensor cut out had to change it for one with a sensor cut out.
This is step 1. Even if this isn't the cause, it will cause problems later.
You say not variable. Sure on or off. That said, a protector can limit how close the "close" reference can be identified at.
Step 2 is a factory reset.
Unfortunately, can't troubleshooting without doing these steps.
Click to expand...
Click to collapse
I know, I know. I’ve read that many have had issues with screen protectors but I thought the folks that checked saw that the proximity sensor readings were also bad. Mine seem to be just what the phone would want to see.
I will take it off at some point and I guess I’ll be the first to verify that even if you use an app to monitor the proximity sensor readings and they look normal the protector can still cause an issue or it is something else.
I did find that the Ambient display will not work without screen lock turned on.
Tanquen said:
I did find that the Ambient display will not work without screen lock turned on.
Click to expand...
Click to collapse
True, because it needs a lock screen to display it.
The screen worked as it should randomly the other day. Only on the one call. I pulled the phone away to look at something and it turned the screen on. Put it to my ear and what do you know, it turned the screen off. Not worked again so far and I ran the sensor app right after the call and it showed just what it always has, zero. Anything close to the phone you get a zero every time, right away. The phone app just ignores the zero reading.
I use the phone as navigation in the car, so I never hold it to my ear. I did not have a SIM in it for a year, now I put one back in order to also use it for hands-free talking. Issue is the famous black screen when starting or accepting a call.
I have rooted it, installed Xposed and enabled modules CallScreenFix and Sensor Disabler. In Sensor Disabler, I have tried to things with the same result: hard lock the Proximity sensors shown to maximum distance or also disabling them.
AIDA64 shows as expected either proximity 5.0 or no sensor at all (info: before installing Xposed it was 0.0 constantly).
However, the screen still turns off when a call is in progress. I would not even care that much, but I cannot enabled speakerphone to use it for hands-free talking.
Any further ideas? At the very minimum any phone /dialer apps where I can pick up and call directly in speakerphone mode?
As mentioned above, I have the phone rooted. So anything goes
Cheers,
Daniel.
I would try without Xposed first. Xposed is very much a hack, and you never know what it actually does.
Do you have a screen protector that covers the sensor?
runekock said:
Do you have a screen protector that covers the sensor?
Click to expand...
Click to collapse
No, I never used any of that. Without Xposed, the sensor always shows 0.0 on AIDA64. With Xposed, I can choose between 5.0 and not having a sensor at all. None of that has an effect. I'd very much like to find a non-hacked solution of course. However, since it's my secondary device, I'd also be ok with half a hack...
nexus 6 proximity sensor fix
In my case it was the protective glass, when it was removed it worked again. I saw in a video that the sensor may be "released" or something. I can not publish external links, but on YouTube you find videos showing possible solutions when writing nexus 6 proximity sensor fix... Sorry for my English, use a translator.
I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?
I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.
jdock said:
I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.
Click to expand...
Click to collapse
Thanks mate, appreciate your feedback. Proximity sensor works fine on my phone during calls. Can't think of any reason why Samsung would intend it this way...
Proximity sensor issue here as well
I have the same problem. I put phone into test mode and it was bad compared to my wife's s9 search proximity sensor s20fe on YouTube and see others with issue
There is no fix. This is apparently the way AOD works now. I can't remember if it started with the S10s or S20s.
uggies said:
I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?
Click to expand...
Click to collapse
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
No problems with Verizon S20 FE 5G UW
Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
I just purchased the Samsung S20 FE 5G UW (how about we shorten this to FE UW?) with all updates AND a glass screen protector and have no touch/proximity issues.
FYI I bought it at the Costco kiosk for a few dollars less per month, no activation charges and a 90 day return policy.
the Galaxy S20 FE (5G) has no physiscal proximity sensor.
Insted it uses a combination of the front camera, touch screen and gyroscope.
I have tested the proximity issues, luckily for me there were ok...turn green. The only thing that drive me crazy is the touch screen issues which never been fixed even after updates. Oh well at least its better than before.
Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
Mate great information here, really appreciate this.
Tested the Proximity sensor using *#0*#, I agree with your analysis. The proximity must be using electric reaction to detect if my ears are touching it or not. Covering it with a book does not trigger a proximity sensor... This explain why my screen keeps waking up in the pocket.
As much as this is annoying, there appears to be no way out Just have to let the phone face outside rather than my legs.
I also have the same issue, while on a phone call, the phone's screen goes on and off constantly and I can see the notification bar moving. Very annoying.
This is a terrible design by Samsung. The punch hole usually goes in the "Empty" part of the ear, so the screen stays mostly on.
I might just return the phone because of this issue, I don't see it getting fixed by a software update.
I have the exact opposite issue with the proximity sensor on my Samsung S20 plus running Android 10 - i.e. it works well by turning the screen off when my ear/cheek/face is very close to the proximity sensor during phone calls; whereas, when the phone's screen is locked and turned off, the proximity sensor is turned off as well. Control by hardware? Software/firmware? Don't know?! To turn the screen on without using the Power hardware button, I had to enable the "Double Tap" feature in Settings.
On earlier/other Android mobile devices - Samsung included - the proximity sensor is always on - whether the screen is on, off, or currently locked. When it's always on, you can be innovative and build a widget, for instance, to turn the screen on by "waving" your hand above the proximity sensor to interrupt the laser. I suspect new(er) Samsung mobile devices like S20 and Note20 variants might be using a "virtual" proximity sensor setup/combo for controlling the device's screen - and that really sucks!
To test if the proximity sensor is always activated on Samsung S20 and Note20 variants, I type *#77692# - which displayed a hardware screen to test proximity and light sensors. Note: if you type *#0*#, the proximity and light sensor options are absent from the hardware test screen.
Has anyone found any method - via codes even - to permanently turn on the proximity sensor, even when the screen is locked and turned off?
I searched through AOSP framework vanilla codes and couldn't see anything out of the ordinary regarding control of the proximity sensor. Samsung might be doing something dubious with their firmwares/hardwares though - well, at least, the S20 and Note20 variants are having issues with the proximity sensor setup.
P.S: Not sure if you guys are aware, but Samsung mobile devices with odd designation tends to be more problematic than their even-designated counterparts, like screen's burn-ins/shadows on Samsung S3 devices, light sensor fluctuation (which affects screen brightness control) on Samsung S5s, and now proximity problems with the S20s and Note20. Samsung S20 variants are in fact "S11" variants renamed. So the trend continues with Samsung always stuffing up their odd-designated device releases.
Hi All,
I am using Nokia 7 plus for past 2 years. Andorid 10 with Nov security patch. Recently, my proximity sensor stopped working and I am not able to use phone any more (due to black screen during calls). I even root my phone and installed edxposed framework for disabling proximity sensor but no luck. Even sensor disabler not working for me. Any suggestions would be much helpful as I want to use this phone badly
I have same problem (stop working after lcd replace), try more solution, but at end i find one "working"... In Developer options enable QuckSettingsDeveloperTiles/SensorOff, this add Sensor tile to top pulldown QuckSettings menu, before call must you manually enable it, after call disable (because sensor off disable all sensors and also camera ;-)
k3dar7 said:
I have same problem (stop working after lcd replace), try more solution, but at end i find one "working"... In Developer options enable QuckSettingsDeveloperTiles/SensorOff, this add Sensor tile to top pulldown QuckSettings menu, before call must you manually enable it, after call disable (because sensor off disable all sensors and also camera ;-)
Click to expand...
Click to collapse
Yeah, I have been using it. Problematic when attending calls in Skype which wont work unless you switch again. Thanks anyway
In my experience, proximity sensors don't stop working, they just work all the time! Often there's a small rubber gasket which separates the UV LED from the sensor. Can be lost when replacing a screen - I did this myself on a Moto G. Screen would go black in a call and couldn't be unlocked. I found the gasket on the floor, replaced it and this fixed the problem. Replaced the screen on a Nokia 7 Plus recently, same problem. I couldn't find a missing gasket this time, but glued a small piece of rubber between sensor and LED and this fixed the issue. Had to experiment with the size of the rubber piece to get it working properly. I think some of the UV light bounces off the back of the screen and is picked up by the sensor , if this piece is missing. My $0.02 worth...
Guys, I am frustrated with proximity sensor of my Nokia 7 Plus, as soon as I call, screen goes black.
I could stop it by enabling Developer Mode and disabling sensors, but this disables all sensors not proximity, and my camera stopped working.
Can I just remove it from mother board? any way to disable only proximity sensor?
Thanks in advance.
MrNams said:
Guys, I am frustrated with proximity sensor of my Nokia 7 Plus, as soon as I call, screen goes black.
I could stop it by enabling Developer Mode and disabling sensors, but this disables all sensors not proximity, and my camera stopped working.
Can I just remove it from mother board? any way to disable only proximity sensor?
Thanks in advance.
Click to expand...
Click to collapse
If you've had the screen replaced, I think the rubber gasket separating the IR LED and sensor has been lost. Seems to be a common cause of this kind of problem. Cheers
Gastrocnemius said:
If you've had the screen replaced, I think the rubber gasket separating the IR LED and sensor has been lost. Seems to be a common cause of this kind of problem. Cheers
Click to expand...
Click to collapse
Many thanks for quick reply.
Yes, I replaced screen. I don't remember about rubber gasket, but now i have to open scree and fix it.
Can we just remove proximity sensor from board? What functions get affected?
MrNams said:
Many thanks for quick reply.
Yes, I replaced screen. I don't remember about rubber gasket, but now i have to open scree and fix it.
Can we just remove proximity sensor from board? What functions get affected?
Click to expand...
Click to collapse
I guess just the screen turning off during a call. But removing it may damage some other component, I guess. I also wonder if the screen stays off or on permanently if the sensor is removed. If you're taking the screen off anyway you could just try my fix of glueing a small piece of plastic or rubber between the sender and receiver, has worked for me and is still working. But this is just my opinion, all the best in whatever you decide to do. Cheers
Gastrocnemius said:
If you've had the screen replaced, I think the rubber gasket separating the IR LED and sensor has been lost. Seems to be a common cause of this kind of problem. Cheers
Click to expand...
Click to collapse
Yes, I replaced screen. I don't remember about rubber gasket, but now i have to open scree and fix it.
Can we just remove proximity sensor from board? What functions get affected?
Gastrocnemius said:
I guess just the screen turning off during a call. But removing it may damage some other component, I guess. I also wonder if the screen stays off or on permanently if the sensor is removed. If you're taking the screen off anyway you could just try my fix of glueing a small piece of plastic or rubber between the sender and receiver, has worked for me and is still working. But this is just my opinion, all the best in whatever you decide to do. Cheers
Click to expand...
Click to collapse
Ok Thanks, I shall try it.
One more question
Is there a way to disable only proximity sensor through OS/App? This will save my effort to remove it from board and possible damage to board.
Am working on another 7 Plus which has the gasket fitted to the proximity sensor and took some pictures so y'all can see what I'm talking about. First picture is of the gasket, second is the sensor without the gasket. Cheers
Just checked in to this forum for give Gastrocnemius a big "Thank you"!
We have a Nokia 7 Plus with the "normal" USB connection issue.
Send to repair to an independent repair station (so not Nokia), who offered a good price.
When it came back it looked fine, charging and fast charging was possible, we have been happy.
Until the first call... Black screen with dialing.
A short search showed: many problems after an update, looked like software related issue with no solution.
Shortly after the new USB connection was faulty again.
So the phone went into a drawer and replaced with a new Nokia.
Now my old Redmi 4 is too old and some for me important apps will not work with the "old" android.
I remembered the Nokia 7 plus and started to repair the USB board, also as a trial if i can handle mobile phone repairs for myself. Well, cheap USB board found, change successful... not! Broke the Display (stayed black after assembly, board from display got hot, probably cable broken).
Ok next step, new display, screen works and and charging repaired on first view.
Function check: black screen during call. Tried several proximity fix tools without success.
The app Phone Check clearly identifies as proximity sensor as "close" / near, no change.
The change to far came only when the display was way to the side. So, the sensor is working, but the function close far is not working.
After weeks I discovered this fred! Gasket? Which gasket! There is no gasket! Check with several videos on YT, yes, gasket identified!
So I tried the mentioned fix rubber band but was not able to get it working.
Then I looked for a gasket online and found one available for the Nokia 2 / TA 1007 on EBAY for a couple of Euros and ordered it for giving it a try.
I just assembled the gasket.... the 7 plus no works like new!
So I'm assuming that during the first USB-board change the gasket got lost and the check by the repair company was only performed for the charging and no more checks for the rest or they didn't care (ASUMING!)
Long story short:
If the gasket is missing you can use the one from the TA-1007!
It does look a little bit different than the above gasket but mine worked. No further assembly from the phone is required, just slip it over the sensor (make sure that the big hole is left, seen as microphone is up and sensor is up left [don't know how to describe better]).
Thanks again for the hind to the missing gasket.
Best regards from Munich,
Thorsten
(typos corrected)
Blackboie said:
Just checked in to this forum for give Gastrocnemius a big "Thank you"!
We have a Nokia 7 Plus with the "normal" USB connection issue.
Send to repair to an idependent repair station (so not Nokia), who offered a good price.
When it came back it looked fine, charging and fast charing was possible, we have been happy.
Until the first call... Black screen with dialing.
A short search showed: many problems after an update, looked like softwrae related issue with no sollution.
Shortly after the new USB connection was faulty again.
So the phone went into a drawer and replaced with a new Nokia.
Now my old redmi 4 is to old and some important apps wil not work with the "old" android.
I remembered the Nokia 7 plus and started to repair the USB board, also as a trial if i can handle mobile phone repairs for myself. Well, cheap USB board found, change sucsessful... not! Broke the Display (stayed black after assembly, board from display got hot, probably cable broken).
Ok next step, new display, yes, phone and charging repaired.
Funktion check: black screen during call. Tried proximity fix tools without sucess.
The app Phone Check clearly identifies as proximity sensor as "close" / near, no change.
The change to far came when the display was way to the side. So the sensor is working, but the function close far is not working.
After weeks I discovered this fred! Gasket? Which gasket! There is no gasket! Check with several videos on YT, yes, gasket identified!
So I tried the mentioned fix rubber band but was not able to get it working.
Than I looked for a gasket online and found one available for the Nokia 2 / TA 1007 on EBAY for a couple of Euros and orderet it for giving it a try.
I just assembled the gasket.... the 7 plus no works like new!
So I'm assuming that during the first USB-board change the gasket got lost and the check by the repair company was only performed for the charging and no more checks for the rest or they didn't care (ASUMING!)
Long story short:
If the gasket is missing you can use the one from the TA-1007!
It does look a little bit different than the above gasket but mine worked. No further assembly from the phone is required, just slip it over the sensor (make sure that the big hole is left, seen as microphone is up and sensor is up left [don't know how to discribe better]).
Thanks again for the hind to the missing gasket.
Best regards from Munich,
Thorsten
Click to expand...
Click to collapse
Glad to hear it worked for you Thorsten!