Related
Hey guys. Im having a problem with the proximity sensor on my sensation 4g. It was working fine when i bought it. It shut the screen off while calling, but now it does not. I thought that maybe rooting it would fix the problem by getting a custom rom, but i would like some input before i go rom exploring on this phone. I assume its a software issue because i havnt dropped the phone or anything along that line. Any Help would be highly appreciated. I also am looking for the dialer codes that would lead you into a test mode to test the functions on the device. If anyone knows of a code, I would appreciate to learn what it is. thank you for your help.
Make sure Proximity sensor is enabled in Settings > Call Settings > Additional Settings.
thank for your reply. I checked the settings and the only thing that shows up is Caller Id settings and Call waiting. Oh and i downloaded a market app that would show me all the sensors that work on my phone, and the light and proximity sensors both come up with an unknown error. Could it be something from the gingerbread update?
Did anyone figure this out? I have the same problem and its getting pretty annoying.
Me too...:-(
Hello,
I am having the same problem. Earlier, I thought that it was a ROM issue, however, after changing multiple ROMs, it seems to be firmware issue.
On my sensation, I found out that it is related to the back light for the soft keys (home, menu, back and search).
I can get it to work if I turn on pocket mode in Settings > Sound and then restart (once or twice). It will work until next restart.
I have installed AndroSensor from market and it shows one of the 3 messages
Proximity Sensor: Waiting for Event
Proximity Sensor: Unknown Error.
Proximity Sensor: 3.5in
Also, I am getting exceptional battery life which makes me wonder whether phone uses both the cores or if anything else is wrong with the phone.
I am using Energy ROM (3rd Oct).
Any feedback?
Thanks,
Baiju
baijunagori said:
Hello,
I am having the same problem. Earlier, I thought that it was a ROM issue, however, after changing multiple ROMs, it seems to be firmware issue.
On my sensation, I found out that it is related to the back light for the soft keys (home, menu, back and search).
I can get it to work if I turn on pocket mode in Settings > Sound and then restart (once or twice). It will work until next restart.
I have installed AndroSensor from market and it shows one of the 3 messages
Proximity Sensor: Waiting for Event
Proximity Sensor: Unknown Error.
Proximity Sensor: 3.5in
Also, I am getting exceptional battery life which makes me wonder whether phone uses both the cores or if anything else is wrong with the phone.
I am using Energy ROM (3rd Oct).
Any feedback?
Thanks,
Baiju
Click to expand...
Click to collapse
This is interesting b/c I just noticed I have the same problem, too. I do not check the pocket mode because I want to save some battery life. I did get the proximity sensor working during calls "sometimes". And it's really hard to define this "sometimes" b/c I cannot identify the pattern or reproduce the scenario.
My solution to this issue is that If it's not working, I recharge the battery until full, do a reboot, maybe reboot twice, and it is "sometimes" "fixed" by itself. In my case, after doing that, the proximity will work for a while (again, it's hard to determine how long), and just stopping working all the sudden.
I hope there is a easier fix, maybe a app, that would reset the proximity so we can apply it when the sensor does not work.
Hi I just realized the cause, it's because the battery % mod from UOT kitchen. I removed it and everything is fine now. Apparently the UOT kitchen's setting has problem.
I have 2 sensation 4g. One doesn't have any problem with Energy ROM. For the other phone, I went back to Factory settings and reinstalled original TMobile ROM. I still have problem with that one. I have contacted t-mobile and asked for a replacement. It is something with the hardware I suppose.
Baiju
hello
I got the exact same problem and i do many rom/kernel change to figure out this problem but i just can't .
Yungyeh could you explain more how do you solve it ? thks
toowave said:
hello
I got the exact same problem and i do many rom/kernel change to figure out this problem but i just can't .
Yungyeh could you explain more how do you solve it ? thks
Click to expand...
Click to collapse
I guess nothing fancy.
As I've known so far, there are several causes, which can be divided into two categories: Hardware and software .
If your device came with this issue, with a stock rom installed, maybe applied some updates, then you shouldn't wait to call the (HTC/T-mobile?) customer service. Have a exchange or replacement is the only way to correct the hardware issue.
If it's a software issue, i.e. it worked before with a stock rom, but now it fails sometimes after flashing a custom rom, you may go with the following solutions.
Situation One: If the custom rom is fresh installed, charge your device until battery full, stay in charge mode for another 1 - 2 hours, complete power off and on at least twice (three times maybe, make sure the "fastboot" in the power settings is off). Do not install any mod until your rom settles for a few hours. Sometimes the sensor does not work will simply because the cache goes wrong. If after waiting for a few hours and the problem still persists, you may want to check your custom rom's instruction and make sure you've followed every steps.
Situation Two: If the proximity sensor does not work all the sudden, especially after doing a reboot, you should first clear your data for phone app (or any other apps that use the proximity sensor), and then boot into recovery to clear all your cache. After wiping your cache, you have to do what situation 1 instructed because your device is just like a fresh installed one.
Situation Three: If your proximity sensor fails to work after applying a mod, especially some mods cooked from the UOT kitchen, revert back to your previous backup. DO NOT APPLY THAT MOD ANYMORE!!! Try some other mods that work for you and that is friendly to your proximity sensor. This situation also applies to if your flash an inappropriate kernel. Revert back to your previous backup is the only solution.
If none of the situations described above works for you, then I am out of clue. Changing to other custom rom or kernel usually does not work. You may try that but I doubt it will resolve this issue. It may be just your bad luck that the proximity sensor of your device goes to its end. I sincerely hope it not the case.
my sensors are not working!!
accelerometer
gyroscope
light
magnetic field
orientation
proximity
All not working...
Was using HyperSensation-CM7.1-v0.8, then decided to update the kernel, faux newer one, then lost the ability to rotate the phone..
So, did a manual wipe, then super wipe, restored my backup, and still no sensors,
wiped again and tried a diffrent rom nothing changed,
wiped again tried arhd 3.6.7 with stock kernel and faux kernel,
tried cm7 with the kernel it comes with or the newer one and still nothing...
at what level does the software talk to these sensors, is there a 100%way to wipe the phone and start over? i have never had any issue like this before!
Would reverting back to the original rom via fastboot help at all versus what i have done?
if someone has any ideas pm me, its a little bit easier then catching a response here since this is the most popular rom in the world lol, but ill still be reading
I'm having the same probpem. I don't really mess around with Roms or anything and I have 2 sensation 4g that do the same thing. And I believe is an htc problem.
having the same iseu with proximity and light sensor.
Do you have an solution yet ?
yungyeh said:
Hi I just realized the cause, it's because the battery % mod from UOT kitchen. I removed it and everything is fine now. Apparently the UOT kitchen's setting has problem.
Click to expand...
Click to collapse
I`m having the same problem with both proximity and light sensors.They work occasionally but not for to long.Have you found a solution for this?
It's April of 2012 and I have found NO answers or fixes!!!!!!!!!!
Same sensor problem on my sensation.
If I reboot the phone in a dark room, booth sensors are working (I don't know if it's correct when the proximity sensor shows only 3,5 or 0 inches, but it works)
When I go to a lighted room, the proximity sensor stops to work and the light sensor needs more time to measure the illumination.
If I reboot the phone into lighted room, the sensors didn't work.
It is possible to simulate a "dark room" by covering the sensors with a finger ;-)
It is not easy to decide if the error is located into software or the sensors are "overloaded". For finding out a solution I have ordered new flex main board which should contain booth sensors. Hope it helps ^^
schand99 said:
Same sensor problem on my sensation.
If I reboot the phone in a dark room, booth sensors are working (I don't know if it's correct when the proximity sensor shows only 3,5 or 0 inches, but it works)
When I go to a lighted room, the proximity sensor stops to work and the light sensor needs more time to measure the illumination.
If I reboot the phone into lighted room, the sensors didn't work.
It is possible to simulate a "dark room" by covering the sensors with a finger ;-)
It is not easy to decide if the error is located into software or the sensors are "overloaded". For finding out a solution I have ordered new flex main board which should contain booth sensors. Hope it helps ^^
Click to expand...
Click to collapse
@schand99: The Flex/Main Board actually isn't the problem. It is an HTC software/hardware related problem. I have 2 Sensation's here now, one is rooted and unlocked entirely and the Proximity and Ambient Light Sensors and the Capacative Backlights on the touchpad DO NOT WORK. FYI, the touchpad lights work in cooperation of the Ambient Light Sensors: If there is any light under 90.0 Luxes (this is how the sensor measures light) the backlights will come on. If there is anything over 90.0 Luxes, the backlights will stay off. This is based on the fact that you need light in a totally dark environment, or you do not need light as you can see the touchpad and it is not that dark.
It is DEFINITELY not a hardware issue as there are some temporary fixes that will bring them back to life, but usually after a reboot, they are both dead again.
I am curious if your new flex/main cable would do the trick or not. I have tested the sensors chipsets independently and they work fine, there is just something that block their functionality on a software end.
mariosaraylian said:
It is DEFINITELY not a hardware issue as there are some temporary fixes that will bring them back to life, but usually after a reboot, they are both dead again.
I am curious if your new flex/main cable would do the trick or not. I have tested the sensors chipsets independently and they work fine, there is just something that block their functionality on a software end.
Click to expand...
Click to collapse
My report about main flex board changing:
After changing the board booth sensors are working fine. I have tested the functionality of the sensors also on different ROM's like stock rom, OrDroid and CoinDroid. No problem until now. It makes not a difference anymore if I power on the phone into dark room or on a sunny place.
BUT!
I don't recommend to do this by yourself. It is verry difficult to do this work !!
It is my profession to do this kind of work.
AND
to change the board was the right method for fixing the sensor-problem on my HTC Sensation. I had to unlock the hboot 1.27.xx by using the "beer drinking" method. So perhaps I have damaged the sensors by doing this...
schand99 said:
My report about main flex board changing:
After changing the board booth sensors are working fine. I have tested the functionality of the sensors also on different ROM's like stock rom, OrDroid and CoinDroid. No problem until now. It makes not a difference anymore if I power on the phone into dark room or on a sunny place.
BUT!
I don't recommend to do this by yourself. It is verry difficult to do this work !!
It is my profession to do this kind of work.
AND
to change the board was the right method for fixing the sensor-problem on my HTC Sensation. I had to unlock the hboot 1.27.xx by using the "beer drinking" method. So perhaps I have damaged the sensors by doing this...
Click to expand...
Click to collapse
@schand99: That's very strange that it could be the SAME hardware problem for all of these people that are complaining about this issue. I wonder if is some sort of production issue they have. The strange part is that it is not just for the lot of hardware issued for the USA only, it is also in other parts of the world also.
I did a hardware exchange with mine at the TMOUS store and the "new" one I have now is working fine thank God.
I told them that the TMOUS ICS RUU OTA upgrade broke the sensors LOL!
Thanks for your feedback!
My nexus s' proximity sensors have stopped working. I am rooted and running aokpcb rom, I'm wondering if this is a hardware problem or something with the rom? The screen won't turn off when answering / making a call when the phone is brought up to my ear. I also tried using the app prox pro, and that wouldn't work either. If anyone knows a fix or what the problem is, that would be great.
Backup your current ROM , wipe and install a Stock ROM.
Issue solved --> Rom Issue
Issue unsolved --> hardware issue
Thank you for your response. I tried your suggestion, and the problem wasnt fixed with wiping and installing a stock rom. But, with experimentation, I installed the app "Prox Pro" and whenever I would turn it on, it would execute the command that was specified for when the phone was "flat". So, when realising this, I am assuming that my phone developed some sort of calibration problem with the sensors. All in all, I am wondering if there is a way that I can re-calibrate my proximity sensor so that they work properly. Thank you.
Could that just be the default for the phone if it's not getting a reading?
I don't think its the default. The sensors always worked fine up until sometime last week.
I meant a default if there is no signal or an error, which is what it currently looks like.
Oh, okay, ya that could be it. Do you have any idea how to change it? I also realised that the light sensor isn't working either, when on auto brightness, the screen will always be dim, no matter how bright it is outside. If you, or anyone else has a solution, I will open up my phone and check to see if there are any connection issues or something like that .
Hi all, I just noticed that my auto rotate isn't working anymore. I was using a custom rom, but reverted back to stock just to make sure everything would be alright, but it still isn't working on my stock rom. I downloaded "Phone Tester" from the app store, and when I check to see if it's working, it says that my device has no accelerator, compass, light sensor, etc...
What's going on here? It was working fine a couple of days ago.
Edit, when I go to the Phone Tester app, it says that I don't have:
- Accelerometer
- Compass
- Magnetic Field Sensor
- Proximity Sensor
- Light Sensor
- Gyroscope
- Pressure Sensor
- Humidity Sensor
bump
Having your same issue. It worked once when I flashed a new rom but then I rebooted and it stopped working. I went back to stock but that didn't help either.
neriamarillo said:
Having your same issue. It worked once when I flashed a new rom but then I rebooted and it stopped working. I went back to stock but that didn't help either.
Click to expand...
Click to collapse
If you flashed the factory image and it's still not working then it's most likely a hardware issue.
I remember soon after the N5 was launched there was a barometer app that was crashing all of the sensors. Maybe this is still an issue?
El Daddy said:
I remember soon after the N5 was launched there was a barometer app that was crashing all of the sensors. Maybe this is still an issue?
Click to expand...
Click to collapse
I have barometer installed and working since day 1 I bought the phone.. I would assume the OP problem is an isolated issue that somehow crashed all the sensors.
Most possibility is factory hardware defect.. or .. somehow the phone was at affected by strong magnatic/radiation field area that caused those sensors broken.
Having the same issue.
So I figured something out today. I flashed the stock image for 4.4, (not 4.4.2 like i had previously), and everything works perfectly fine! Now if I take the OTA for 4.4.2 it stops working once again. So now I have no idea what to do lol since I know its not necessarily a hardware issue but more of a software issue. Another thing is while on 4.4.2 if I open GPS Status & Toolbox app to check the GPS or sensors the phone soft reboots but the app never opens.
This is definitively a software issue somewhere. Its been working perfectly fine all day on stock 4.4
I will try and see if I can find what's changing or getting updated when you do the update to 4.4.2.
I have tried every single ROM on this Forum for Moto G 2015 Osprey 1GB version. However I am having same issue on evry ROM . Often I recieve a call my screen goes blank and I am not able to answer the call . Also when dialling out my screen goes blank after pressing dial . As a result I am not able to put teh call to loud speaker or use any other in call options . Can some please help me how to fix the issue . (I know work around to use Power Button to end calls and Volume to answer calls however that doe snot suite me as I ended up answering few calls which i did not wanted while mobiel in my pocket ).
Things I have done so far
I have tried this with both a screen protectoron and now have taken screen protector off . Issue still there
I have a a backup of orignal Motoroal ROM and this issue does not happen on orignal ROM
I have installed Nano gapps to make sure I have unough RAM free issue still there
I have tried most of the ROM 7.1.1 and even 6.0.1 all ROMS including Cynogen mod+ Lineage 13 and 14, ressurection remix, AOPS . Experience, Slim, AOKP, Cosmic , AOSP extended and list goes on and on but issue is still; there
Is there any specific reason for this issue ?
Is this to do with RAM, Sensor or custom ROMS issue ?
Is teher any way to turn teh sensor off which turn screen off whiel in a call and when i take mobile near my face (I am thinking if sensor incorrectly so wanst to check if turning thsi off makes any difference )
Can anyone please help
So your proximity sensor is acting up... are you on current baseband and firmware? I would suggest flashing the latest factory image completely via fastboot, verify operation of the proximity sensor, then flash your ROM again. A backup and restore in TWRP of stock is not sufficient to update firmware.
acejavelin said:
So your proximity sensor is acting up... are you on current baseband and firmware? I would suggest flashing the latest factory image completely via fastboot, verify operation of the proximity sensor, then flash your ROM again. A backup and restore in TWRP of stock is not sufficient to update firmware.
Click to expand...
Click to collapse
Thanks acejavelin you are always helpfull. I know how to flash Stock Formware however How can I verify operation of the proximity sensor?
I have found a copy of orignal firmware under XDA thread however I am not sure whether it is up to date firmware or not . How can I confirm if this is up to date firmware ?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Retail UK (1GB) - XT1541_OSPREY_RETGB_6.0.1_MPI24.107-55-2_cid7
Can you please help on this bit
chungomungo1 said:
Thanks acejavelin you are always helpfull. I know how to flash Stock Formware however How can I verify operation of the proximity sensor?
I have found a copy of orignal firmware under XDA thread however I am not sure whether it is up to date firmware or not . How can I confirm if this is up to date firmware ?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Retail UK (1GB) - XT1541_OSPREY_RETGB_6.0.1_MPI24.107-55-2_cid7
Can you please help on this bit
Click to expand...
Click to collapse
Just take the newest one there... Best you can do.
As far as testing the proximity sensor, make some calls and have someone call you... You can try a sensor tester app like https://play.google.com/store/apps/details?id=com.mtorres.phonetester too
Brilliant , Thanks alot . will try that
FACING EXACTLY SAME PROBLEM ON XT1550
I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.
abhishekturumella said:
FACING EXACTLY SAME PROBLEM ON XT1550
I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.
Click to expand...
Click to collapse
There is only one fix. find where is proximity sensor, usually it is on the top near front camera . when ever screen goes blank dry your thumb and clean screen with teh thumb where proximity sensor and screen will wake up .
Also you need to keep you pockets extra clean. It is better if you can hoover inside them as most of the time I noticed there was a little dirt always on my screen when screen went blank. I am noit sure if my mobiel screen has gone very catchy to dirt after 1 year use
I intially though iut was due to custom ROMS and I have gone back to stock ROM and recieved two motorola security updated still issue is there so this is not because of the ROM .
Try this
Goto settings and search default from the search button then select phone app and set the default app.
Just saw this and thought I'd try Phone Tester. covered or uncovered, my proximity det always said Far. I tested phone by making a call and then covering it and the screen immediately went black. I would suggest that some screen protectors might interfere a bit but you've already taken that into account. Note where it is (on my xt1540 top just right of ear speaker) and make sure surface is clean. Otherwise just may be defective.
EDIT: if you feel it's "defective" You might consider replacing the screen/digitizer in hopes that that would fix it and it's not a motherboard issue.
Facing same issue
My stock rom on moto G3 2015 was working fine. Yesterday i rooted and installed tesla when this issue started. Frustrated i tried ASOP Extended and here too same issue.
It's not the issue of the sensor since Stock rom was fine till 2 days ago.
Have tried Phone notificaion settings as well.
Any updates on this or else i may have to reinstall Stock ROM
Hi, it appears that recently the gravity sensor in my Nexus 5 stopped working.
At least it is what it seems by using sensor testing apps. And this makes it impossible for the phone to get its orientation (compass is not working).
Screen rotation is still working fine though.
Here is what happened exactly: not long ago I was using Google Maps, but the phone was a bit sluggish so I decided to reboot it.
After rebooting I opened Google Maps again and immediately noticed that the orientation indicator was missing (the blue "beam"), while it was present before the reboot. But I didn't care about it, and just thought that the compass needed re-calibration.
After a few days the orientation indicator was still missing, and the phone never asked me to re-calibrate, as it used to do before instead.
Then one day I launched Google Sky Map, and noticed that the view does not rotate automatically.
So I fired up a sensor test app I had installed (asd.vector.sensor), and no data is displayed for the Gravity sensor. Also orientation is not displayed and the info says that the gravity sensor is used to compute orientation, too.
Other sensors are ok, and as I already wrote screen rotation still works great.
Any clues about this issue? Did anyone ever experience this?
I'm afraid a system restore would not help...
I'm using Resurrection Remix ROM, Android 6.0.1.
Thanks.
If the problem exists on a stock ROM, it could be a hardware fault.
audit13 said:
If the problem exists on a stock ROM, it could be a hardware fault.
Click to expand...
Click to collapse
Ok yes, but I still do not know if it exists on a stock ROM.
Taking it the other way around... Do you think there is real possibility that it is a software fault?
I mean: did it ever occur to anyone? Is there really any hope that resetting my phone to stock will fix this?
I HATE having to reset my phone...
Thank you.
I stopped using custom roms a while ago because of minor problems that would suddenly appear.
I don't think there is a way to really tell if it is software or hardware unless you reset or use a stock ROM.
audit13 said:
I stopped using custom roms a while ago because of minor problems that would suddenly appear..
Click to expand...
Click to collapse
Well, that's a little hope at least.
I will need to find some time to re-stock my Nexus and try.
Thanks .
Ok, I restored the phone to stock and all sensors work again now!
Thanks audit13 for pushing me in that direction .
That's great that it was a software bug in the custom ROM.
Now you get to hunt for a custom ROM that works with a minimal or zero number of issues