Related
Hey guys,
I've bought a slightly used myTouch 4G off of Craigslist to replace my Vibrant.
I've rooted and modded the MT4G and I'm currently running CM 7.2 RC0. I followed the step-by-step directions from the CM Wiki.
I've found what I think is a problematic proximity sensor reading. Every time I place or receive a phone call, the screen blanks out. The only way I've found to bring the device back, is to wait for the phone call to disconnect and then receive another incoming call. This _usually_ will reactivate the display. As long as I don't answer that phone call, the display will remain active.
I downloaded a proximity sensor app off of the market and according to the app the proximity sensor is engaged 100% of the time (which explains the behavior a little bit). But I don't know whether or not to trust this app.
I've tried tinkering with every proximity setting I can find, both in the phone's settings and in the extra settings that CM ships with.
Edit: I'm sorry for not mentioning it earlier, but I have done a bit of research on the proximity sensor. I don't think there's any kind of screen protector that might be obscuring the sensor.
What are the chances that the phone's proximity sensor is damaged? Is there any way to spoof that value and override what the sensor is repeating back to the OS?
Does anyone have any helpful suggestions?
For what it's worth, here's some information from About Phone:
Android Version: 2.3.7
Baseband Version: 12.28b.60.140eU_26.03.02.26_M
Kernel Version: 2.6.35.14-cyanogenmod-g295e82f [email protected] #1
Mod Version: CyanogenMod-7.2.0-RC0-glacier-KANG
Build Number: GWK74
Thanks in advance for taking a look
Are you using a case? My wife bought a cheap case that covered the prox sensor and it behaved exactly how you said.
Edit: I found an app in the market called Hardware Disabler. It scans your device for drivers and disables whatever you select. The problem is it only gives you the driver's name, not what it works for. If you can identify the driver (perhaps a knowledgable dev could help) you could kill that baby on startup.
Sent from my HTC Glacier using XDA App
Yeah, sorry I didn't mention it before. I've got nothing that I can think of that would be interfering with the proximity sensor on the front of the phone; no screen protector, no little case. Nothing at all.
Tonight I've been monkeying around with a few different things, just to see if I got better/different results:
Tried a couple of the different/newer radios from the radios post in the dev forum.
Wiped cache and Davlik partition
Reset phone back to factory defaults.
Flashed back to one of the T-Mobile Froyo ROMs.
None of these helped, but on a lark. I decided to go ahead and shine a big flash light at the phone while I was running the Proximity Sensor Finder application. If I shined the light directly on the proximity sensor, then the proximity sensor would intermittently blink on/off.
It doesn't really help me all that much, but it looks like I definitely have a flaky/bad proximity sensor.
In order to help people down the road who might have the same problem, here's some things I'm going to try:
Deny permissions to the device's file in the /dev directory
Try and use an app like Tasker to disable the sensor.
May flash MIUI, it sounds like it has an option to permanently disable the proximity sensor.
An app on the market called Proximity Screen Off
I'll keep the thread up-to-date with what I wound up doing. It's a bit of a bummer, I got this phone to last me until my contract expires with T-Mobile in a few months. But it was hopefully going to be a definite upgrade over the Vibrant. It's a little aggravating that I'm going to spend the next few months heating the side of my face when I'm on the phone and/or accidentally hanging up on people when on the phone
Last reply to my own thread, I promise. The MIUI's disable proximity sensor setting worked great, although I wasn't really crazy about the look & feel of MIUI (this isn't a dig on the ROM, just a personal preference).
We wound up using a Hex Editor to edit the file /system/lib/hw/sensors.glacier.so, we searched for "cm3602" (the proximity sensor) and changed it to "xxxxxx".
The one downside is the phone doesn't turn off when you hold it up to your face, but that's certainly better than a phone who's display likes to power off when placing/receiving phone calls.
Thanks for comments mines also have this issue too.
Sent from my HTC Glacier using XDA App
Nice thread Neckhole. I'm glad you followed up on this and let us know what did and did not work for you. Thanks. I really hate it when people figure something out and never post it. Ha.
Sent from my HTC Glacier using XDA App
estallings15 said:
Nice thread Neckhole. I'm glad you followed up on this and let us know what did and did not work for you. Thanks. I really hate it when people figure something out and never post it. Ha.
Me too lol
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
I'm glad what I found out has helped you guys too, I posted a blog about it too after a few people found it to be helpful.
MyTouch 4G: Don't Stand So Close to Me
Just a quick update, I've been re-flashing different ROMs and had to re-make this change. Which helped me spot some typos in my blog post (woops) and I took the time to write something more close to step-by-step instructions. Hope this is more helpful:
http://blog.brianmoses.net/2012/01/mytouch-4g-dont-stand-so-close-to-me.html
Get ADB Functioning on your desktop computer.
Download and install a Hex Editor
Use ADB to pull down the file sensors.glacier.so (adb pull /system/lib/hw/sensors.glacier.so)
Open sensors.glacier.so in your Hex Editor
Search for the text "cm3602" (no double-quotes) and save your changes. Please note, case sensitivity is important. If you're paranoid, it's good to check that the file size is exactly the same as it was before your edit.
Re-mount the /System folder as read-write using an ADB Shell (mount -o remount,rw /dev/block/mmcblk0p25 /system)
Open up a new command window and use ADB to push your edited file (adb push sensors.glacier.so /system/lib/hw/sensors.glacier.so)
Reboot your phone.
For whatever it's worth, I flashed my first ICS ROM a week or two ago. I totally forgot about my defective Proximity Sensor.
I thought people might like to know that the same steps I used to disable the proximity sensor previously still works in ICS.
thank you thank you thank you for this thread, i have the exact same problem i couldnt answer calls cause i use gv and i cant call where i have to press a number aftewards!
so glad it still works for ics. thank you again! posted this problem in a few forums no one could help
I have a doubt
You said : Search for the text "cm3602" (no double-quotes) and save your changes
what changes should I save? since all I've done is search for a text.
tripi24 said:
You said : Search for the text "cm3602" (no double-quotes) and save your changes
what changes should I save? since all I've done is search for a text.
Click to expand...
Click to collapse
Change cm3602 with xxxxxx
Thanks for this post. It has been a big help. I was having the same issues.
Did this work for anyone else? It did not for my phone. The phone goes black and can't access the dial pad.
I have the exact same problem after recently i replaced my broken digitizer touch screen & LCD.
I just realized that during the call , when the display goes totally black , if i push the UP-LEFT corner of the screen of my phone (just beside the proximity sensor) , the screen comes back again.
That's because the "adhesive" i used under the lcd screen , is more thicker than the original adhesive.
So the sensor is ok , the distant between the "touch & LCD " and the sensor is the problem.
Oh je baby pussyy
Shaggadelic baby
albi159 said:
Oh je baby pussyy
Shaggadelic baby
Click to expand...
Click to collapse
What?
Solved
Well i again diss-assembled the whole phone , and replace the thick adhesive under the Lcd & touch with proper one.
and problem solved as i guessed it's not from the Proximity sensor . no more dark screen
Hi all
I accidentally dropped my Nexus 7 (32GB, WiFi) and the screen not longer rotates. All the autorotate settings are correct. I checked GPS Status and all the readings are out. I also got SensorTester and the orientation sensors are definitely out of whack. So, I'm guessing the sensors got disrupted in the fall. I tried recalibrating using both apps with no luck.
I've seen threads about doing a hard reset, but I'm not sure how that would work, particularly since I suspect it's a hardware problem. Unless the sensors are somehow software dependent? Is there something I can do to fix this, or would I have to send it in for repairs?
I'm running stock 4.2.2
Thanks!
swoatt said:
Hi all
I accidentally dropped my Nexus 7 (32GB, WiFi) and the screen not longer rotates. All the autorotate settings are correct. I checked GPS Status and all the readings are out. I also got SensorTester and the orientation sensors are definitely out of whack. So, I'm guessing the sensors got disrupted in the fall. I tried recalibrating using both apps with no luck.
I've seen threads about doing a hard reset, but I'm not sure how that would work, particularly since I suspect it's a hardware problem. Unless the sensors are somehow software dependent? Is there something I can do to fix this, or would I have to send it in for repairs?
I'm running stock 4.2.2
Thanks!
Click to expand...
Click to collapse
You broke the sensor but just be glad that's all you broke. You could have easily broken the screen.
I've looked but can't seem to find a replacement for the sensor. But you'd probably need to be very handy with tiny soldering jobs to fix it even if you could find the part.
Are you known with rooting etc?
If so there are some ways to flash the stock ROM
I would not say its broken immediately, because when I dropped my iPod touch the iOS just went crazy and didn't boot anymore, but all was fixed after a reset...
Sent from my Nexus 7 using xda premium
lewmur said:
You broke the sensor but just be glad that's all you broke. You could have easily broken the screen.
Click to expand...
Click to collapse
I know! I hadn't realised the N7s were so prone to screen shattering and dislodged digitisers before I started looking for solutions to my problem. I'll be a lot more careful from now on lol. Fortunately everything else is working, although the GPS stopped working for a while.
sdelange99 said:
Are you known with rooting etc?
If so there are some ways to flash the stock ROM
Click to expand...
Click to collapse
I've been toying around with the idea of rooting it for a while now. Haven't really had any need/want to. Until now. I'll give it a try when I have the chance.
Thanks for the advice
Whenever I make, receive or even check my balance(which had absolutely nothing to do with the sensor), after the call is over proximity sensor still works! :crying:
Gets pretty annoying some time Later, can't work, play games, watch movies just somehow hand comes in front of it and then Sensor detects it and black out the entire screen!
Please if someone knows anything about it, I desperately need their help! Thanks. :good:
Might sound silly, but have you enabled all your Samsung Air/Gesture commands etc? -- also Smart stay/Pause?
If so, disable them.
radicalisto said:
Might sound silly, but have you enabled all your Samsung Air/Gesture commands etc? -- also Smart stay/Pause?
If so, disable them.
Click to expand...
Click to collapse
I absolutely never enable them they're off since I got my phone but the sensor still continues to annoy me!
What should I do to stop it?
there are a few thread for proximity sensors problems... search and you will find some useful information.
but in short, there is probably some dust in front of the proximity sensor.
a temporary fix is to blow some air in the earpiece... but the problem will eventually come back.
I do this once a month.
The other thing you can do is disassemble your phone, clean the proximity sensor lens, maybe add some kind of protection to protect it from dust... and reassemble everything.
zadigre said:
there are a few thread for proximity sensors problems... search and you will find some useful information.
but in short, there is probably some dust in front of the proximity sensor.
a temporary fix is to blow some air in the earpiece... but the problem will eventually come back.
I do this once a month.
The other thing you can do is disassemble your phone, clean the proximity sensor lens, maybe add some kind of protection to protect it from dust... and reassemble everything.
Click to expand...
Click to collapse
But how to disassemble the phone it must be a risky business!
sambhavmathur said:
But how to disassemble the phone it must be a risky business!
Click to expand...
Click to collapse
If you have the tools, is not very difficult...
http://forum.xda-developers.com/showthread.php?t=2488031
Sent from my SM-N900 with Tapatalk
sambhavmathur said:
Whenever I make, receive or even check my balance(which had absolutely nothing to do with the sensor), after the call is over proximity sensor still works! :crying:
Gets pretty annoying some time Later, can't work, play games, watch movies just somehow hand comes in front of it and then Sensor detects it and black out the entire screen!
Please if someone knows anything about it, I desperately need their help! Thanks. :good:
Click to expand...
Click to collapse
Try going to Settings>General>Application manager>All>Phone and clearing data.
If that doesn't help, try doing a factory reset.
Failing that, try availing warranty, or if you are Knox 0x1, try another ROM.
zadigre said:
there are a few thread for proximity sensors problems... search and you will find some useful information.
but in short, there is probably some dust in front of the proximity sensor.
a temporary fix is to blow some air in the earpiece... but the problem will eventually come back.
I do this once a month.
The other thing you can do is disassemble your phone, clean the proximity sensor lens, maybe add some kind of protection to protect it from dust... and reassemble everything.
Click to expand...
Click to collapse
His problem seems to be a software issue and not a hardware one.
FeralFire said:
Try going to Settings>General>Application manager>All>Phone and clearing data.
If that doesn't help, try doing a factory reset.
Failing that, try availing warranty, or if you are Knox 0x1, try another ROM.
His problem seems to be a software issue and not a hardware one.
Click to expand...
Click to collapse
I had the exact same problem with my device... and the problem is hardware (dust in front of the proximity sensor)...
I tried everything, including a factory reset, and the only thing that fix it (for now) is to blow some air in the earpiece.
Next step will be to disassemble and clean the sensor manually
A New Development
Before when I call or receive a call from anybody the proximity sensor still worked and turned the screen off even after the call, but now my phone is acting even more weird!
After the call the headphone jack is also not working!
Desperately need assistance guys, pls help!
Hello,a week ago my proximity sensor started making bizarre things.The screen stayed black after calls etc etc. I went to Samsung in Greece and they changed the sensor.I had the phone back after 4 days...4 difficult days because I am in love with my phone but now everything is working fine. I saw a lot of threads in forums about proximity sensor problems on this phone...too bad!
alexpsilos said:
Hello,a week ago my proximity sensor started making bizarre things.The screen stayed black after calls etc etc. I went to Samsung in Greece and they changed the sensor.I had the phone back after 4 days...4 difficult days because I am in love with my phone but now everything is working fine. I saw a lot of threads in forums about proximity sensor problems on this phone...too bad!
Click to expand...
Click to collapse
But I can't send my phone to Samsung because I rooted it and that triggered Knox warranty so I probably need some other way!
If anybody knows anything please help!
http://forum.xda-developers.com/showpost.php?p=50740216&postcount=4
Well, you could just disable the proximity sensor and turn the screen off manually by pressing power.
Phone --> Call Settings --> Turn off screen during calls.
Not ideal, but at least you can still use your phone.
sambhavmathur said:
But I can't send my phone to Samsung because I rooted it and that triggered Knox warranty so I probably need some other way!
If anybody knows anything please help!
Click to expand...
Click to collapse
mwerkz said:
http://forum.xda-developers.com/showpost.php?p=50740216&postcount=4
Click to expand...
Click to collapse
Try what he says! if this do not work then, or you have to pay to get your phone fixed or find a way to fix it yourself (buying a new proximity sensor and changing it through the help of videos).The second option will be a pain in the *** and I would never try it as I am not sure if it could go well.
Absolutly same problem i gotta
my proximity senzor is still little red Everything works fine. Like test or calls but is still slightly red. When i restart phone is black but after first call is slightly red and turn black only after restart.. but works fine. Any solution?
Ok so basically I love the g2, but here is my problem, bare with me on this haha, BTW its completely stock n everything as its my 1st Android phone so didn't want to mess with it. So basically I broke my phone screen in January, bought new screen, followed a YouTube tutorial, replaced LCD+touchscreen, no issues super happy, had the odd issue where if I woke screen, would only be on for a second n then go back to sleep, but then upgraded to KitKat through computer software update, still nothing wrong, upgrade fixed the issue with the knock to wake, and then my worst day, smashed the screen again! On good Friday, ok I thought I'll just replace screen again, so I did, but when I put new screen on and tested it, all was well, until I made a phone call, the instant moment I press green call button, screen goes blank and won't come on no matter what, power button don't bring it back on or end the call, but I can hear the other person and they can hear me, had to turn phone completely n back on to be able to use it again, so I though hmmm dodgey screen, but just to be sure it wasn't the phone I put damaged screen back on, and the issue didn't appear, stayed lit up while in my hand, went off next to my ear, back on whole in hand, so I took it to local phone repair shop because I couldn't be bothered going through the hasstle getting refunds etc, they replaced screen, I went and tested it before paying them, guess what, same problem, so what exactly is going on? Has KitKat made the phone not work with a new screen other than the one I upgraded it with? I'm seriously confused and need some bodies help urgently my model is an unlocked lg g2 d802 16gb now I turned it on last week before I took it to be repaired, and it says I have software updates but I didn't bother installing them, is there a chance these could be related to my issue and possibly fix them? Its driving me nuts tbh
Chris
Hey Chris. It seems like your proximity sensor is messed up. I think the new screen you got yourself is worse quality or your damaged the proximity sensor when installing the screen.
Edit:
Please go into your phone app (where you call people) and type the following
3845#*802#
Then go into: HW Device Test and then ALC proximity test. Try testing your proximity sensor with your hand. It should change from far to near when your hand is about 2 inches from your phone. The proximity sensor is located next to the camera.
Sent from my LG-D802 using XDA Premium 4 mobile app
Ok thank you I will try that, I also thought a damaged sensor but when I put damaged screen back on after having the issue with my new screen it worked just fine, no blank screen when making a call, I retested it before I left it at phone repair shop, still was fine, then picked it up with a new screen and issue came back, I don't get why its been like this, I'm thinking bad quality screen and maybe try scratching the sensor area of the new screen to allow more light in? It may be to dark for it, what exactly do I do if it works fine when using that code, try another screen?
Chris
I doubt it will work when you use that method. It's just to make sure that it's the proximity sensor that's the problem and not some loose connection. And yes, a new screen would be your best bet.
Sent from my LG-D802 using XDA Premium 4 mobile app
Ok I won't try that method then lol, what if it doesn't work when I use that code, as I said I didn't have the issue with the damaged screen which I tested after having the issue with the replacement screen I'd purchased, so how do I know its not just the screen not allowing the sensor to see? Is there anyway I can reset the sensor to relearn maybe?
Chris
If you follow my steps, nothing bad will happen. It's just a way of troubleshooting the proximity sensor. I still think you should do it.
Sent from my LG-D802 using XDA Premium 4 mobile app
Ok I've spoken to phone repair shop and they agree it worth a try to see if its the screen or not, I'll let you know on Saturday after I've been and tested it
Chris
I just had this exact same issue.Turns out the inside of the screen was just dirty. I opened it up and took a q-tip to the inside of the screen and it worked perfectly after that. Also check the readings of the light sensor, as it is right next to the proximity sensor, if the screen is the problem it will likely have low readings as well.
Great I'm glad somebody else has encountered this issue, its been driving me nuts lol ok so I dial in the code that's been mentioned and what are the labels in the menu for the proximity and light sensors? I'm thinking its just a crap screen as the broken 1 worked fine after I put it back on after testing new screen, and I reckon the screen the repair shop has used is also ****e quality, but I just want to cancel it all out as I don't have the phone to hand to inspect as they still have it lol is there a picture somebody can post up to show what to not cover when replacing the screen and applying adhesive tape etc? Just so I can show them to make sure they have done it all properly.
Chris
Ok so just to update the problem, I went to the phone shop today, did the test, it was showing near all the time, but the light sensor reading was quite high, 166 or something, but I then tried squeezing the screen, index finger on back and thumb on front, gently squeezed it, and proximity sensor started showing far, and near as I moved my hand over it, but after few seconds, went back to showing near constantly, so I think its the screen not been seated, told the shop to take screen off, give it a good clean and reseat it. This sound good to you guys?
Chris
Anyone?
Bump! I'm only wanting a little extra advice so I don't end up paying more money out for another screen when it could possibly be proximity sensor? I think it was just the screen not seated properly, anybody have an idea or something else to either assure my choice or point me in another direction?
Chris
Hi all,
Im at a loss here, I dont know how to move forward with this problem so im asking for help lol XD.
I just gave my nexus 4 to my gf ( just got my opo last week). The phone was running cyanogen mod 11 ( some nightly version between m6 and m7).
So when my phone came in the mail, I dropped her sim in my nexus 4 (witch was working perfectly) and after making a phone call with it, she tells me she thinks the phone app is broken or something...
So I have a look at it and this is what its doing now. When I call someone, as soon as you click call the screen goes black. To bring back the screen you need to click twice on the sleep/wake button on the side ( kinda like if you were closing the phone and re-opening it) just for the screen to show again but none of the buttons work. Well none of the phone app buttons work, I can still click back/home/previous app buttons or slide down the top menu just fine. just cant click any of the number keys, hang up, hit speaker phone or anything related to the phone app. So in order to hang up I have to click home and then use the drop down menu and click hang up under the phone notification.
Before droping her sim card in the phone I did a standard wipe/factory reset on the phone just to give her a clean platform. So since that was already done I've tried updating to a stable ( M9 in this case) release, problem is still there, so I tried to wipe dalvik, cache and done a data wipe/factory reset from the CWM recovery and flashed a fresh cm 11 M9 with gapps and I still have the problem.
Im at a loss at where to begin looking for a fix for this situation, I've looked on the xda and cm forums and ran plenty of google searches for this problem but im coming up empty ...
any help would be greatly appreciated,
regards
Chris
Edit: omg screen protector was interfering with the proximity sensor... Is this a common problem with nexus 4 or could this provblem still be related to my hardware/software ?
(I've never used a screen protector before).
R3druMz said:
Edit: omg screen protector was interfering with the proximity sensor... Is this a common problem with nexus 4 or could this provblem still be related to my hardware/software ?
(I've never used a screen protector before).
Click to expand...
Click to collapse
If the screen protector isn't applied carefully, it might interfere easily with the sensors. If you want to check, then download a sensor tester from the play store, and use it to see if the sensor is working without any protector over it.
abaaaabbbb63 said:
If the screen protector isn't applied carefully, it might interfere easily with the sensors. If you want to check, then download a sensor tester from the play store, and use it to see if the sensor is working without any protector over it.
Click to expand...
Click to collapse
haha thanks for your reply, I've been trying to solve this issue for a week, been looking on the cm nightly and stable forums and here on xda trough all the posts that sounded closely related to my problem and didn't find anything... as soon as I post a questions 3 minutes later I found the problem.
To test it, I simply peeled the screen protector off and held it there while I made a call and it worked perfectly !! Then I cut out the part that goes over the prox sensor and its perfect again ( looks like crap but works ). Still gonna download that sensor tester ( curiosity XD).
P.S: totally unrelated to this post, I've been reading some of your "how to" posts here on xda, just wanted to say thanks for all the info you have put out there XD.
R3druMz said:
P.S: totally unrelated to this post, I've been reading some of your "how to" posts here on xda, just wanted to say thanks for all the info you have put out there XD.
Click to expand...
Click to collapse
Hehe No problem
This happened with my co-worker's Nexus 4 (which is now my Nexus 4). She had been complaining about this for like a month, until I actually saw her screen, and that the corner of her screen protector had flapped loose and had a bunch of crud built up underneath it. It was a forehead smacker for me when I realized how obvious the cause/solution was. Not so obvious when I took possession and replaced the screen and had the same problem.