Hi,
I bought a motorola milestone and i did not changed the software, but yesterday the problems started. When i make a call, i can hear the call but the screen dont cames again and the phone stays unusable with a black screen, i cant turn off the call or even turn off my phone. Any one can explain how to fix it or there is no way?
joaelvas said:
Hi,
I bought a motorola milestone and i did not changed the software, but yesterday the problems started. When i make a call, i can hear the call but the screen dont cames again and the phone stays unusable with a black screen, i cant turn off the call or even turn off my phone. Any one can explain how to fix it or there is no way?
Click to expand...
Click to collapse
that's not a problem, when you call goes out not to touch the screen with the ear, is a proximity system and really get away from the phone and lights.
elpelas said:
that's not a problem, when you call goes out not to touch the screen with the ear, is a proximity system and really get away from the phone and lights.
Click to expand...
Click to collapse
My friend i know that but the problem start when i press the call buttom, the sreen goes and never came back even if i put it on a table...
joaelvas said:
My friend i know that but the problem start when i press the call buttom, the sreen goes and never came back even if i put it on a table...
Click to expand...
Click to collapse
I have the same problem. Sometimes my milestone has black screen after call and doesnt answer for 30 sec.
I have the newst stock rom.
Any solution?
terpsych
joaelvas said:
My friend i know that but the problem start when i press the call buttom, the sreen goes and never came back even if i put it on a table...
Click to expand...
Click to collapse
is it under warranty? if it is, u know wat to do!
sorry to revive this thread, but I have the same problem. The problem is only when I'm outside with direct solar light. Inside a room it works well.
I'll try not to touch the screen next time, then post the results here
Already happened to other users, it's an HW problem, warranty repair is the best viable option.
How a small rubber could cause deadlocks...
Hi guys!
The Solutor said:
Already happened to other users, it's an HW problem, warranty repair is the best viable option.
Click to expand...
Click to collapse
Basically you're right. The deadlock is caused by the proximity sensor.
There are two possibilities:
1. some circuit could be broken (quite no chance to fix)
2. small grommet inside the display is missing (might be easy to fix)
On my device the little rubber grommet was missing....
Here's what happens inside:
The Milestone uses very comfortable proximity sensor to detect the reflecting light by the users cheek during telephone calls.
This sensor is using an external IR-LED to work properly and to increase sensitivity.
To prevent internal reflection inside the housing there's a small rubber grommet placed between the IR-LED and the sensor.
If this part is missing the internal reflection could cause phantom detection and leads to a deadlock if a call is initated.
@joaelvas: You might check if your device has already been opened.
There should be some sticker on one of the torx-screws at the backside of the case. If the sticker is broken, then your device had already been opened by someone. AFAIK, no warranty in this case.
Anyway you might try to give it to the service
If you're not scared, open the case yourself...
Please be very careful with the damn flex cables... you might ripp them apart so easily.
See here for some instructions how to open the case:
http://www.ifixit.com/Guide/Repair/Installing-Motorola-Droid-Front-Panel/2958/1
Although it's for the droid, it's the same for milestone.
Good luck,
scholbert
It's work!!
wow.... amazing, it solved my problem.... thank you so much Bro, u r PRO!!!!
scholbert said:
Hi guys!
Basically you're right. The deadlock is caused by the proximity sensor.
There are two possibilities:
1. some circuit could be broken (quite no chance to fix)
2. small grommet inside the display is missing (might be easy to fix)
On my device the little rubber grommet was missing....
Here's what happens inside:
The Milestone uses very comfortable proximity sensor to detect the reflecting light by the users cheek during telephone calls.
This sensor is using an external IR-LED to work properly and to increase sensitivity.
To prevent internal reflection inside the housing there's a small rubber grommet placed between the IR-LED and the sensor.
If this part is missing the internal reflection could cause phantom detection and leads to a deadlock if a call is initated.
@joaelvas: You might check if your device has already been opened.
There should be some sticker on one of the torx-screws at the backside of the case. If the sticker is broken, then your device had already been opened by someone. AFAIK, no warranty in this case.
Anyway you might try to give it to the service
If you're not scared, open the case yourself...
Please be very careful with the damn flex cables... you might ripp them apart so easily.
See here for some instructions how to open the case:
http://www.ifixit.com/Guide/Repair/Installing-Motorola-Droid-Front-Panel/2958/1
Although it's for the droid, it's the same for milestone.
Good luck,
scholbert
Click to expand...
Click to collapse
wow, thanks for the tip about the rubber... I was get really annoyed at this cel phone After I replaced the touchscreen.. it would get stuck in calls for a long time. Now a placed a new piece of spounge tape in the back of the sensor and the metal plate in the back of the screen is pressing it hard enough now to block all the side light, it's working as it should.
Thanks.!
my stone,too .
so have to replace the touch screen?it's expensive,
any else??anybody help us!pls!i lov my stone!
scholbert said:
Hi guys!
Basically you're right. The deadlock is caused by the proximity sensor.
There are two possibilities:
1. some circuit could be broken (quite no chance to fix)
2. small grommet inside the display is missing (might be easy to fix)
On my device the little rubber grommet was missing....
Here's what happens inside:
The Milestone uses very comfortable proximity sensor to detect the reflecting light by the users cheek during telephone calls.
This sensor is using an external IR-LED to work properly and to increase sensitivity.
To prevent internal reflection inside the housing there's a small rubber grommet placed between the IR-LED and the sensor.
If this part is missing the internal reflection could cause phantom detection and leads to a deadlock if a call is initated.
@joaelvas: You might check if your device has already been opened.
There should be some sticker on one of the torx-screws at the backside of the case. If the sticker is broken, then your device had already been opened by someone. AFAIK, no warranty in this case.
Anyway you might try to give it to the service
If you're not scared, open the case yourself...
Please be very careful with the damn flex cables... you might ripp them apart so easily.
See here for some instructions how to open the case:
http://www.ifixit.com/Guide/Repair/Installing-Motorola-Droid-Front-Panel/2958/1
Although it's for the droid, it's the same for milestone.
Good luck,
scholbert
Click to expand...
Click to collapse
Is it possible to get that grommet in India?
Even the official service center don't have that
Related
Hey
A friend of mine called me yesterday if I wanna buy his broken X1 (it felt down :/) and repair it, because I'm the man for such jobs
Do you think it's only the LCD-flex-cable or another repairable damage?
I think I can get that device for 2-3 days and then decide if I buy it...
Some ideas? Is there any chance to repair it?
Thanx, Carbon
yes, probably even a loose connector on flex cable
Hello,
I am quite certain it is an easy problem, i have seen many x1 phones with just a minor loose connector which causes the screen not to respond.
The best way to check it if it really is just the screen/flex cable is to turn it on, and check if the side lights flash in all colors.
If that works the phone should work normally. (even if the screen doesn't work)
After opening:
Re-insert all the cables in the screen flex cable and check if it works..
if that doesn't work then replace the flex cable.
If the screen works:
Then check out the screen if it has any crack's or black spots.
In that case you will have to replace the screen/touch screen also.
Generally, if there is no physical damage to the LCD itself and the phone buzzes on startup with all appropriate sounds - replace the flex. Flashing lights are attached to the flex and are positioned ABOVE the LCD on flex connection, therefore will not light up if the flex is damaged and neither will the upper keypad and other less obvious things.
The flex replacement is not minor, just be aware of that. Bad falls are also the reason for main PCB damage, in which case there will be nothing you can do.
Thank you so much
It was a "very short" call by this friend, but when i take the device, I want a precise report what happened...
atm I don't now if the sidelights show reaction, but I will report
I'm afraid of a real PCB damage...
In flex problem side lights will not light up, as i mentioned, they are positioned above the Lcd connection, so if the main flex connection ribbon is damaged, as is most often the case, all of the upper level functions will be gone, but you will get a startup with buzz and sounds present.
I got it
And LEDs are flashing and you can start it complete normally, but you see nothing... i'm going to open it and check the Flexcable
Carbon386 said:
I got it
And LEDs are flashing and you can start it complete normally, but you see nothing... i'm going to open it and check the Flexcable
Click to expand...
Click to collapse
Best of luck.
Hey Everyone!
I am new to this site so pl bear with me if I am posting some wrong thing.
Got MOTO X Verizon running on HSPA in INDIA. Everything seemed to work good.
Suddenly after 3 days of normal use (no dropping, no dumping, no water damage), screen started to garble at uneven intervals.
With all the pain to search for the problem all over the internet I at last (i think) solved the problem.
For this I had disassembled the screen and motherboard and just pressed the golden sticker (above the inter-connecting cable on the back of the screen)
Screen works fine now, but I guess I screwed up the proximity sensor mounted on the motherboard (seemingly irreplaceable.)
When calling the screen goes black etc...( i know this issue has been cited many times...mine is different I believe)
This was working when i got the phone (waving my hand always used to start the active display).
I checked my settings for Active display, got numerous apps for the the proximity sensor testing. [ Phone Tester shows proximity FAR and does not change that value whatever i do; "Proximity Sensor Finder" shows 3.0 cm last value and does not change ever either]
Then I tried everything from the rubber gasket installation to a hard reset, factory reset and what not.(thanks to tonnes of websites and people helping all over the world)
NO LUCK!
I also noticed that the LED beside the sensor used to blink which has actually stopped. LIGHT sensor and all others are working nicely.
This is where my issue lies :silly: : " Has anyone got this type of problem? Has the golden sticker on the right top corner on the back of the screen anything to do with the RED LED of the proximity? I tried all dialers, all possible ways to bypass the Proximity but invain. I am not wishing to root this phone and I am not good with coding either. Can this be a software issue? (running 4.4.4).Is there a calibrator out there to rejuvenate my proximity?
PLEASE HELP!!
For the time being I am using bluetooth headsets (where the screen remains open).
In Kitkat?
V Limaye said:
Hey Everyone!
I am new to this site so pl bear with me if I am posting some wrong thing.
Got MOTO X Verizon running on HSPA in INDIA. Everything seemed to work good.
Suddenly after 3 days of normal use (no dropping, no dumping, no water damage), screen started to garble at uneven intervals.
With all the pain to search for the problem all over the internet I at last (i think) solved the problem.
For this I had disassembled the screen and motherboard and just pressed the golden sticker (above the inter-connecting cable on the back of the screen)
Screen works fine now, but I guess I screwed up the proximity sensor mounted on the motherboard (seemingly irreplaceable.)
When calling the screen goes black etc...( i know this issue has been cited many times...mine is different I believe)
This was working when i got the phone (waving my hand always used to start the active display).
I checked my settings for Active display, got numerous apps for the the proximity sensor testing. [ Phone Tester shows proximity FAR and does not change that value whatever i do; "Proximity Sensor Finder" shows 3.0 cm last value and does not change ever either]
Then I tried everything from the rubber gasket installation to a hard reset, factory reset and what not.(thanks to tonnes of websites and people helping all over the world)
NO LUCK!
I also noticed that the LED beside the sensor used to blink which has actually stopped. LIGHT sensor and all others are working nicely.
This is where my issue lies :silly: : " Has anyone got this type of problem? Has the golden sticker on the right top corner on the back of the screen anything to do with the RED LED of the proximity? I tried all dialers, all possible ways to bypass the Proximity but invain. I am not wishing to root this phone and I am not good with coding either. Can this be a software issue? (running 4.4.4).Is there a calibrator out there to rejuvenate my proximity?
PLEASE HELP!!
For the time being I am using bluetooth headsets (where the screen remains open).
Click to expand...
Click to collapse
(waving my hand always used to start the active display).
This feature is gone with Lollipop though...
And I read you're on kitkat, but really there was a LED blinking there???
I own an xt1060. There is an LED there, but its always been less than useless for me. It never turns on. Ever. Not for calls (missed or otherwise), notifications, or charging. I've often wondered why it's there.
I can make it work in Cyanogenmod. Any stock ROM renders it useless.
when you said you checked gasket are you referring to the tinny black rectangle gasket around the led and prox censer? when i first starting working on the x i had smiler issue, the little gasket fell off and i did not notice it
hugh a said:
when you said you checked gasket are you referring to the tinny black rectangle gasket around the led and prox censer? when i first starting working on the x i had smiler issue, the little gasket fell off and i did not notice it
Click to expand...
Click to collapse
Exactly the same small thing I m taking about.. God knows I dropped it or not... But when I opened it for the 4th tym... I noticed was not there.. Then I did not get it anywhere in sale and so replaced it with a small white rubber piece with 2 similarly cut holes. No luck. Where did u get it from?
BTW I believe it will make the proximity work only if the led on its left side blinks. That works like a transmitter and receive I guess.
My led won't even flash for once..
I plead to all the genius developers to device an app for proximity bypass.
V Limaye said:
Exactly the same small thing I m taking about.. God knows I dropped it or not... But when I opened it for the 4th tym... I noticed was not there.. Then I did not get it anywhere in sale and so replaced it with a small white rubber piece with 2 similarly cut holes. No luck. Where did u get it from?
BTW I believe it will make the proximity work only if the led on its left side blinks. That works like a transmitter and receive I guess.
My led won't even flash for once..
I plead to all the genius developers to device an app for proximity bypass.
Click to expand...
Click to collapse
it must be there to function properly, it fits very snug around both, seals off all light, i had the exact same issue you described, i have extra, pm me
hugh a said:
it must be there to function properly, it fits very snug around both, seals off all light, i had the exact same issue you described, i have extra, pm me
Click to expand...
Click to collapse
I did replace it with a white rubber gasket almost cut into same pattern after an exhaustive search on internet for its replacement. And I am still stuck.
Also what I believe is that if the LED does not transmit at all, How is it going to help any way?
>>Sorry I am new to XDA could not find the option to PM you.
Thanks
V Limaye said:
I did replace it with a white rubber gasket almost cut into same pattern after an exhaustive search on internet for its replacement. And I am still stuck.
Also what I believe is that if the LED does not transmit at all, How is it going to help any way?
>>Sorry I am new to XDA could not find the option to PM you.
Thanks
Click to expand...
Click to collapse
You seem to not understand that even you have cut a replacement gasket, it may look perfect to you, but it can easily block the proximity and that's about it.
You should try with original one, then start pulling off conclusions if the sensors are defective or not.
Why don't you run a dry test without the gasket?
V Limaye said:
I did replace it with a white rubber gasket almost cut into same pattern after an exhaustive search on internet for its replacement. And I am still stuck.
Also what I believe is that if the LED does not transmit at all, How is it going to help any way?
>>Sorry I am new to XDA could not find the option to PM you.
Thanks
Click to expand...
Click to collapse
click on my profile pic and you will see send message, you must have the gasket, if you dont that is you issue for sure been working on these sense they came out, you can not make the gasket, pm me
liveroy said:
You seem to not understand that even you have cut a replacement gasket, it may look perfect to you, but it can easily block the proximity and that's about it.
You should try with original one, then start pulling off conclusions if the sensors are defective or not.
Why don't you run a dry test without the gasket?
Click to expand...
Click to collapse
"Dry test?" can you please elaborate this?
BTW I had tried using without the gasket too. Same values on the tester apps.
If sensor is working each time the value should change at least a bit when open to light without gasket.
V Limaye said:
"Dry test?" can you please elaborate this?
BTW I had tried using without the gasket too. Same values on the tester apps.
If sensor is working each time the value should change at least a bit when open to light without gasket.
Click to expand...
Click to collapse
By dry test I meant to test it without putting the display/frame over the board and test it that way. If it's not defective you should get proper readings off it.
Hey all
After reading this forum for ages I took the plunge on a Z1, and am not disappointed!
I had one question, if anyone is able to help.
The hardware buttons light up with a nice white LED.
However, the one on the left (select open apps) is much, much brighter than the one on the right (back).
In fact, it's almost as if the right hand one doesn't work at all.
Is this the same as everyone else's phone, or does mine have a defect?
Many thanks to anyone that can compare theirs.
Uri
P.S: I have the grey one with the black front, which may make this more noticeable.
Uri
someoneelse999 said:
Hey all
After reading this forum for ages I took the plunge on a Z1, and am not disappointed!
I had one question, if anyone is able to help.
The hardware buttons light up with a nice white LED.
However, the one on the left (select open apps) is much, much brighter than the one on the right (back).
In fact, it's almost as if the right hand one doesn't work at all.
Is this the same as everyone else's phone, or does mine have a defect?
Many thanks to anyone that can compare theirs.
Uri
Click to expand...
Click to collapse
Is a hardware issue, I think.
My 2 buttons has the same light intensity and is a good intensity.
In my previous prone, a OnePlus One, I have suffered this issue: the back button had a lower light intensity compared to the other buttons.
bartito said:
Is a hardware issue, I think.
My 2 buttons has the same light intensity and is a good intensity.
In my previous prone, a OnePlus One, I have suffered this issue: the back button had a lower light intensity compared to the other buttons.
Click to expand...
Click to collapse
Thanks very much for the quick reply
To be honest, everything else about the phone is perfect (screen, fingerprint scanner, buttons don't wobble, etc), so for the first time in my life I might just live with "almost-perfect".
I had too many issues with iPhones and am worried if I swap it out, then the replacement will have some other defect like screen bleed, etc, etc.
Uri
someoneelse999 said:
Thanks very much for the quick reply
To be honest, everything else about the phone is perfect (screen, fingerprint scanner, buttons don't wobble, etc), so for the first time in my life I might just live with "almost-perfect".
I had too many issues with iPhones and am worried if I swap it out, then the replacement will have some other defect like screen bleed, etc, etc.
Uri
Click to expand...
Click to collapse
If you can live with this issue: Don't return it!
I also haven't returned my OPO. Is a small detect I think
Easy to fix
I had this issue too, but it is easy to fix. When you open your phone backcover, you only have to remove the speaker and reposition the led. The led is loose in a cable and so you can reposition it until the buttons have the same intensity and fix it with some glue.
On my phone the intensity is now exactly the same and i only needed half an hour for it.
When you remove the backcover warm it up a bit and use a sucker to avoid scratches in the frame.
Well I can confirm that I have the same issue on my white Zuk! But it's not very noticeable so i'm keeping it like it is!
microdoof said:
I had this issue too, but it is easy to fix. When you open your phone backcover, you only have to remove the speaker and reposition the led. The led is loose in a cable and so you can reposition it until the buttons have the same intensity and fix it with some glue.
On my phone the intensity is now exactly the same and i only needed half an hour for it.
When you remove the backcover warm it up a bit and use a sucker to avoid scratches in the frame.
Click to expand...
Click to collapse
Don't seems too easy to remove the Zuk Z1 backcover if you don't are McGiver
bartito said:
Don't seems too easy to remove the Zuk Z1 backcover if you don't are McGiver
Click to expand...
Click to collapse
Wasn't very hard to remove, i didn't brake any clips. Use a sucker and as soon as you see a little gap, use a plastic pick or your fingernails to gently pull up the backcover.
After i opened it i removed the tape from the phone and the backcover. After the work is done you can simply close the Backcover without tape or something. I didn't use tape and had no gaps afterwards.
microdoof said:
Wasn't very hard to remove, i didn't brake any clips. Use a sucker and as soon as you see a little gap, use a plastic pick or your fingernails to gently pull up the backcover.
After i opened it i removed the tape from the phone and the backcover. After the work is done you can simply close the Backcover without tape or something. I didn't use tape and had no gaps afterwards.
Click to expand...
Click to collapse
I just tried that; broke some pins immediately, they seem to be of very soft plastic... So i would recommend others not to do it
othe01 said:
I just tried that; broke some pins immediately, they seem to be of very soft plastic... So i would recommend others not to do it
Click to expand...
Click to collapse
I supposed...
microdoof said:
Wasn't very hard to remove, i didn't brake any clips. Use a sucker and as soon as you see a little gap, use a plastic pick or your fingernails to gently pull up the backcover.
After i opened it i removed the tape from the phone and the backcover. After the work is done you can simply close the Backcover without tape or something. I didn't use tape and had no gaps afterwards.
Click to expand...
Click to collapse
Hi guys, even I have noticed the same, the back button light is dimmer than task button. Can somebody suggest if I should get it replaced?
aniketsabarad said:
Hi guys, even I have noticed the same, the back button light is dimmer than task button. Can somebody suggest if I should get it replaced?
Click to expand...
Click to collapse
Same for me. back button light intensity is very low compared to menu button. Its not a big issue. My friend also having same issue. you may get same problem in that replacement unit also. So,better keep as it is.
@arunpkrt and @aniketsabarad If you don't mind there is also an option inside the Zuk Z1 lights configuration to switch off this little ugly menu LED and back LED. The function itself stays active and the touch area is large enough to hit the sensitive zone blinded easily .
arunpkrt said:
Same for me. back button light intensity is very low compared to menu button. Its not a big issue. My friend also having same issue. you may get same problem in that replacement unit also. So,better keep as it is.
Click to expand...
Click to collapse
You guys are right. I faced this problem initially. The phone was perfect, I set it up nicely and was using it. But after a day or two this back button led issue started frustrating me. I applied for a replacement and was surprised to see that even the replacement unit had same issue. So really no point getting it replaced. If it really bothers, you can take the risk to open up the back case as other members suggested.
I also have the same issue but its not important because im using onscreen keyboard.
Overall is perfect but one thing is missing. We still dont have marshmallow to enjoy before Android N release.
Edit: Happy 500th post to me! God Bless!
I don't have the issue, but if ever I had it, it won't matter as I disabled the hardware buttons once I started using mine. 5.5" is too much of a screen and the 3 on screen buttons don't take up that much space. I am much worried about pressing the hard home button because I read from some users that it failed after 2 or three months of using the phone. I only use it for finger print. No need to press it. Double tap to wake, double tap to sleep. No hard buttons to wear.
bluestricker_21 said:
I also have the same issue but its not important because im using onscreen keyboard.
Overall is perfect but one thing is missing. We still dont have marshmallow to enjoy before Android N release.
Edit: Happy 500th post to me! God Bless!
Click to expand...
Click to collapse
Mine has the same problem, if I where you I would just keep it that way and don't go to all the trouble to send it back.
You can also Disable the lights thats what I did
Changed phone screen , so after that screen coes black when i call and cant do ****, i think sensor is kinda buggued. When i take screen off and move finger, 5cm far from sensor it works, but when i move my finger in 2 cm far from sensor it wont work. I have no clue , hard ware of software problem.
Find proximity windows on new touch screen and paint it with black marker from inside. If it doesn't help scrape all painting from this small window to make it completely transparent and then again paint it without leaving any spot transparent. Permanent marker You can clean with some alcohol, don't use any solvent cause it can damage rest of digitizer paint.
Some year ago I had whole part like this, 15 or more screens where I had to scrape this window from painting and again paint it with black marker because factory paint was to dark and light couldn't come in. But in Your case before You scrape it first paint it cause Your can be too bright and if it doesn't help then scrape and paint.
Antoonio said:
Changed phone screen , so after that screen coes black when i call and cant do ****, i think sensor is kinda buggued. When i take screen off and move finger, 5cm far from sensor it works, but when i move my finger in 2 cm far from sensor it wont work. I have no clue , hard ware of software problem.
Click to expand...
Click to collapse
Well the best thing to do, is first determine whether the problem is a Software or a Hardware problem.
1) Factory Reset the device, if the problem persists, flash the firmware of your device via Flashtool ( BACK UP YOUR DATA FIRST ).
If the problem with the sensor still exists...
It's most likely a hardware issue and the best course of action would be to send it to Sony and hope it is covered by warranty, either way it won't be expensive to replace compared to a broken digitizer or something.
Revontheus said:
Well the best thing to do, is first determine whether the problem is a Software or a Hardware problem.
1) Factory Reset the device, if the problem persists, flash the firmware of your device via Flashtool ( BACK UP YOUR DATA FIRST ).
If the problem with the sensor still exists...
It's most likely a hardware issue and the best course of action would be to send it to Sony and hope it is covered by warranty, either way it won't be expensive to replace compared to a broken digitizer or something.
Click to expand...
Click to collapse
He changed screen, this phone is no more under warranty.
Painted it black, scratched it off and it worked, thanks a lot
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!