I replaced the digitizer in my Desire, and now the proximity sensor reports 0.0 cm at all times. As a result, the screen goes black during calls and will not come back on. As part of the digitizer replacement, I used 2mm transparent tape to attach the digitizer to the chassis, and I'm sure there is some of that tape over the proximity sensor. Obviously, I don't want to pull the digitizer back out.
Am I screwed? Or is there something I can do short of disabling the proximity sensor? TIA!
My proximity sensor is also broken. It took me several days to find out how to completely disable it. Put the attached script in the /system/etc/init.d/ forlder (copy paste the code in a text file) and chmod/chown it properly. After a reboot the proximity sensor will be disabled (you will have to switch the screen off manually during calls of course)
Code:
#!/system/bin/sh
#
chmod 0000 /dev/cm3602
chmod 000 /dev/cm3602
aleksei87 said:
My proximity sensor is also broken. It took me several days to find out how to completely disable it. Put the attached script in the /system/etc/init.d/ forlder (copy paste the code in a text file) and chmod/chown it properly. After a reboot the proximity sensor will be disabled (you will have to switch the screen off manually during calls of course)
Code:
#!/system/bin/sh
#
chmod 0000 /dev/cm3602
chmod 000 /dev/cm3602
Click to expand...
Click to collapse
what will be the name of this text file? Sorry i am a noob
You've left the rubber out that sits round the proximity sensor.
It looks like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Put that back and it will sort your problem. I did the same thing recently.
It looks like this when it's fitted
Actually, what happened was when I installed the new digitizer, I used a transparent, 2mm tape from 3M designed specifically for this purpose, and did not leave a gap in the tape for the proximity sensor. I thought that it would be okay because the tape is transparent, but I was wrong. I was able to fix it without removing the screen by lifting up the camera PCB, removing the plastic lens that goes in front of the proximity sensor, and using a small flat-blade screwdriver to gently remove the tape obscuring the hole. Now it's working perfectly.
lolomolo said:
what will be the name of this text file? Sorry i am a noob
Click to expand...
Click to collapse
Arbitrary name. I've called it "99userinit" for example
temporary fix
I have rooted HTC explorer and am running cynogen mod time in it.
Once I tried to calibrate sensor by downloadding an application from playtime called "Rezound proximity calibrator"
I tried to launch the application but it gave error [application has been stopped something like that...]
Then I rebooted the device then my sensor got fixed
But uninstalling the application broke the proximity again...
I'm just sharing my experience to know what exactly the problem is and get a permanent fix inshallah.
Related
Greetings,
I just bought an htc desire. I do however have BIG problem.
As soon as i call someone, the screen goes dark (read it is normal) but, i CANNOT get out of the dark screen, i cannot hang up or unlock the phone, the unlock key does nothing, nor does any other key.
Whats happening?
maybe youre holding one of your fingers over the proximity sensor left to the phone output, or your proximity sensor may suffer hardware faults
the second option really does not sound too good, for a NEW phone
is there no way to disable the sleep option on call???
I don't think there is, that is a needed function. Otherwise, you would do many things with your face over the screen.
Still, my sensor works normal. If I cover it (hand, ear or whatever at the earphone), the display goes off and locks, if I uncover it the display is on and active. And I can do this many times.
i installed "show sensors" and for the proximiti sensor (cm3602) it says reading 0.0 and accuracy high, the number NEVER changes :/
I don't think that anyone from the forums can help you, it's obviously hardware problem. Why you don't just take it to HTC for repairment/replacement?
Btw, show sensors for my proximity sensor say 1.0 when I don't touch it, and 0.0 when I place a finger on the earphone. It's too obvious that your proximity sensor is off.
looks like i have no choise, im gonna have to bring it back in and wait it comes back from support, gonna be without phone for a while :'(
jhaquo said:
i installed "show sensors" and for the proximiti sensor (cm3602) it says reading 0.0 and accuracy high, the number NEVER changes :/
Click to expand...
Click to collapse
Do you have a case or an "invisible" shield covering the sensor?
Regards,
Dave
sadly, no, its out of the box. i dont even know where is the sensor tough
It's on the left side of the earphone
Aproximate position, not sure about the exact position.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jhaquo said:
i installed "show sensors" and for the proximiti sensor (cm3602) it says reading 0.0 and accuracy high, the number NEVER changes :/
Click to expand...
Click to collapse
It should read 1.0 unless the sensor is covered (moving an object over the sensor changes its value to 0), so it appears that you have a faulty device
is the support of htc any good? will i have to wait long to get my baby back? anyone knows?
I called HTC belgium this morning. They made a ticket and said ill receive an email that i have to print and give to the delivery guy tomorow with the phone, between 8 and 12 am.
Now the funny part is, I STILL DID NOT RECEIVE THE DAMN EMAIL.
I called 3 or 4 times, send 4 messages via their ticket system, gave 3 different email adresses to be sure. And i STILL DO NOT HAVE IT, its been like SEVEN damn hours...
They are one hour out of closing, and there is no way ill get it tomorow before the delivery guy comes.
I'm about to go berserk right now, is it always like that with them?
Hey,
i had the same problem that i noticed after root... have you rooted or installed different rom?? Also i send it to repair what they did was updated the rom to the newest one and and restored contacts of the sensor.... but it might be only the rom if you had flashed it. If not then you have to send it to repair or exchange it.
i did not flash it nor root it
jhaquo said:
i did not flash it nor root it
Click to expand...
Click to collapse
Then its a hardware problem, maybe loose connection from the sensor, in that case either repair or exchange
I feel sorry for you... I was without the phone for about 2 weeks for exactly same issue
I researched about causes of phone unable to turn on after a call and saw a DHD thread about it. I tried reflashing the ftf file but after a call, the screen was unable to turn back on, therefore i think it is the proximity sensor's problem. Is there an app like http://forum.xda-developers.com/showthread.php?t=951858 to calibrate proximity sensor? o_o
Any help? After every call i have to pull out my battery and on my phone ..
I'm going through the same problem with my xperia play but I realized that if you place the unit directly in the sunlight it works, I tried a lot about some application to adjust it but it only works in some unit (not xperia) he asks for one kernel file that we do not possess even in custom kernel like DOOMkernel.
I saw this information on the sony page:
(i cannot post links, just look in google for "Sensor HAL for Xperia™ phones available as open source")
I located the file Sharp_gp2.c that has the attributes that I want to change, I imagine that if I change some values like "power" or "resolution" I have some positive results but I do not know where to put this file in xperia play, I think that i can make a zip file and do a fastboot but not sure what the correct path.
If someone Knows, please tell us.
(Obs: I bought the proximity sensor part on ebay and i'll change it by my self, it costs 9 dollars and will arrive in 30 days, if this solve the problem i'll post the result here)
Hey dude, i solved my problem with proximity sensor, the piece that i order still not arrived but i disassembled my xperia play and i removed the piece (proximity sensor) an put it again and is ok now.
It looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see how to disassembly your phone on Youtube, i think the problem was a kind of Conductivity failure on the big conector as in the image.
Proximity sensor replacement
cezeoh said:
Hey dude, i solved my problem with proximity sensor, the piece that i order still not arrived but i disassembled my xperia play and i removed the piece (proximity sensor) an put it again and is ok now.
It looks like this:
You can see how to disassembly your phone on Youtube, i think the problem was a kind of Conductivity failure on the big conector as in the image.
Click to expand...
Click to collapse
Where did you find the part? Mine is doing the same thing but, I prefer to keep all parts intact so I believe I should order one. Also does the part come with the tools?
E
Hi,
Stock Android - Not Rooted 5.1.1
I am attaching two images here. I am pretty sure it's not a hardware problem since my other sensors are working so I would like to figure out which apps are blocking these sensors and how to fix.
A quick reboot is a temporary fix.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk
Pretty sure that this is a hardware issue. Two of the most common issue of this tablet is auto-rotate and touch screen. I experienced the auto-rotate issue a week or two ago wherein placing the tablet on a flat surface face down and pushing the "N" and "S" letters at the back and doing a reboot temporarily fixed the auto-rotate issue. Which if I may say only worked for a few hours.
It came to a point that the reboot and pushing the letters no longer worked. This is the time where I searched and found a hardware workaround: https://www.youtube.com/watch?v=LLCAeBe2hVU this is if you're willing and have the guts to open up your tablet. It seems that the wires connecting the accelerometer/gyroscope and touchscreen "loosens" over time. I've applied the fix a week ago and no longer experience the auto-rotate issue.
Obviously It's still best to send your tablet for repairs if you still have warranty.
chickentuna said:
Pretty sure that this is a hardware issue. Two of the most common issue of this tablet is auto-rotate and touch screen. I experienced the auto-rotate issue a week or two ago wherein placing the tablet on a flat surface face down and pushing the "N" and "S" letters at the back and doing a reboot temporarily fixed the auto-rotate issue. Which if I may say only worked for a few hours.
It came to a point that the reboot and pushing the letters no longer worked. This is the time where I searched and found a hardware workaround: https://www.youtube.com/watch?v=LLCAeBe2hVU this is if you're willing and have the guts to open up your tablet. It seems that the wires connecting the accelerometer/gyroscope and touchscreen "loosens" over time. I've applied the fix a week ago and no longer experience the auto-rotate issue.
Obviously It's still best to send your tablet for repairs if you still have warranty.
Click to expand...
Click to collapse
I had already applied that fix so was ambient sensor working. Earlier none of the sensors use to work. But now since removing my magnetic case it seems to work fine for today. Will see how long does it last!
Sent from my Nexus 7 using Tapatalk
Actually disabling automatic brightness and removing magnetic cover has seemed to solve the issue. I am using Velis Auto Brightness and since then the auto rotate has never ever stopped.
Sent from my Nexus 7 using Tapatalk
Whenever my screen turns off, I could see (Not visible to naked eye but can see though other cameras) a sensor near to front camera is continously flashing in pink. Which sensor is this and will it consume my battery. I have the latest oxygen os version
Do you have proximity wake turned on?
cohaolain said:
Do you have proximity wake turned on?
Click to expand...
Click to collapse
No. Proximity wake is not ON
The sensor you are referencing is the proximity sensor. I also confirm being to "see" it using the camera from another phone without proximity wake being activated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe the new pocket mode checks constantly if the sensor is covered instead of checking after you touch the fingerprint sensor. Would possibly save time?
cohaolain said:
Maybe the new pocket mode checks constantly if the sensor is covered instead of checking after you touch the fingerprint sensor. Would possibly save time?
Click to expand...
Click to collapse
Will this have an effect on battery.
Was this check present in oxygen os verson older than 3.2.2. Also why the proximity sensor is visible only on camera and not to human eye.
You can see it in dark. It's because of pocket mode when it's in your pocket it helps to disable fingerprint sensor.
I'm more concerned about the sensor that its always active it might get damaged?
Prince Chandela said:
You can see it in dark. It's because of pocket mode when it's in your pocket it helps to disable fingerprint sensor.
I'm more concerned about the sensor that its always active it might get damaged?
Click to expand...
Click to collapse
I would like to know the MTBF on that proximity sensor if it is constantly active...
Sent via mobile...
Adarzh said:
Will this have an effect on battery.
Was this check present in oxygen os verson older than 3.2.2. Also why the proximity sensor is visible only on camera and not to human eye.
Click to expand...
Click to collapse
I can't check if the proximity sensor did the same thing on previous versions cause I'm running CM13 at the moment. But the pocket mode is a new implementation that users had been asking for a lot before the update.
The proximity sensor is only visible on cameras because it emits infrared light, which can't be seen by the naked eye. Cameras on the other hand do see this light (unless the camera has an IR filter, which many higher-end webcams do) but represent it on a display that only emits light on the visible part of the spectrum, hence we can see it.
The proximity sensor is made to use infrared light so that
A) it's not an annoyance to people using it, they don't see it blinking when the screen is off to check if it's in a pocket etc.
and B) so it works in all light conditions
---------- Post added at 06:28 PM ---------- Previous post was at 06:25 PM ----------
The effect on battery would be minimal, if any at all. Proximity sensors have become much more efficient than they used to be. They've also gotten better at being "invisible". For example, my old phone (a Vodafone Smart Ultra 6) had a proximity sensor that emitted infrared light, but very sloppily, hence emitted some light in the visible spectrum too, so you could see if it was turned on in the dark, which was really annoying. Not to mention a bug in its software that meant it sometimes got stuck on randomly and had to be rebooted to fix it, and that didn't even always work
Hi everyone. I recently bought a Xiaomi Mi Max 3, my first Xiaomi phone. It got approximately 3 major updates and is now running MIUI Global 10.3.2.0 Stable. The other day I tried taking a photo of my phone and noticed a white dot next to the front facing camera. I tried to take another photo and noticed a constantly blinking light from the same spot. It's not the notification light, that's on the left side and is noticeable with the naked eye. This one however is on the right side (next to the camera) and is not visible to the naked eye.
Upon further research I found out that it might be what I initially thought it was; the proximity sensor. However from previous experience with my Samsung Galaxy S5 I've seen that the proximity sensor is only on during phone calls or if air gestures was on. But on my Mi Max 3 it's always on. The moment I turn the phone on it starts lighting up. I don't have auto brightness/face unlock on, and also tried to turn the proximity sensor off in call settings. But no luck. It even lights up when the screen is locked/off. I don't know if there's any settings causing this, but I tried turning almost everything proximity related off (pocket mode etc.) I have seen that other Xiaomi users have been having this issue too. I tried CIT and the proximity sensor seems to be working (0 to 5cm) but fails to calibrate.
So I had a few questions
1) Is this normal? Is it normal for the proximity sensor to be always on? I highly doubt it
2) Any way to fix this?
3) Will it consume a significant amount of battery power?
*If this really is an issue and not normal, I hope it'll get fixed with a software update because I don't think it's a hardware issue. I've read that people were having similar issues after update here
I don't know if the problem existed before the updates; noticed the light recently only!
Thanks
Attachment:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}