Database Info

[Q] Sensation 4g proximity sensor problem

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!

[HELP] Proximity Sensor problem

I was earlier on cm11s and everything worked fine. Then I manually flashed the cyanogen os 12 ota using stock recovery. Since then the proximity sensor becomes active during incoming calls even if I dont answer the call. During incoming call if the sensor gets covered, the screen goes off. After that I flashed the latest ota with 'OK Oneplus' and the problem was still there. So today I flashed Euphoria Rom (5.1) thinking that this may solve it but the problem still persists. Can anyone tell me the solution to this?
Thanks!

.::[email protected]::. said:
I was earlier on cm11s and everything worked fine. Then I manually flashed the cyanogen os 12 ota using stock recovery. Since then the proximity sensor becomes active during incoming calls even if I dont answer the call. During incoming call if the sensor gets covered, the screen goes off. After that I flashed the latest ota with 'OK Oneplus' and the problem was still there. So today I flashed Euphoria Rom (5.1) thinking that this may solve it but the problem still persists. Can anyone tell me the solution to this?
Thanks!
Click to expand...
Click to collapse
This is only normal!
The goal of this is to not interfere with the screen while the phone is against your face.

néonaloj said:
This is only normal!
The goal of this is to not interfere with the screen while the phone is against your face.
Click to expand...
Click to collapse
But usually the proximity sensor becomes active after accepting the incoming call. But in this case it happens ever if I don't accept it.
This never happened in cm11s

.::[email protected]::. said:
But usually the proximity sensor becomes active after accepting the incoming call. But in this case it happens ever if I don't accept it.
This never happened in cm11s
Click to expand...
Click to collapse
there is a flashback zip file but i don't know where, you can search it up in the forum using the search tool or to disable the sensor from the settings (personally i disabled it)

Does anyone have a fix for this issue. Its extremely annoying that I have to wait for sensor to check if its clear before answering a call. Usually a 2 second delay on incoming call.

Proximity sensor turns screen off for incoming calls

So, I have stumbled across this weird issue since January wherein if the proximity sensor is covered during an incoming call, the screen will remain off. What's weird is that this only happens on CM based ROMs and not on AOSP based ROMs. Of course, all full wipes and clean flashes. I have also tried flashing all the Marshmallow compatible modems available but none solved my issue. I'm using TWRP 2.8.6.0 to flash the zips.
CM based ROMs that I have tried so far;
1. Resurrection Remix M
2. Bliss ROM (both official and unofficial)
3. Marsh CM13
The older builds (December and early January) did not have this problem but of late, every CM based ROM activates the proximity sensor for an incoming call. The reason I'm posting this here is because no one else seems to have this problem and it's not specific to any one ROM.
On AOSP ROMs, everything works fine (no matter what modem I use). I have tried Darkobas ROM and I'm currently on CandySix where I don't have any issues with the proximity sensor.
Any idea why this could be happening? I miss all the customization on CM ROMs and I'm not a huge fan of Layers, so help would be appreciated.
Cheers!

This is the exact bug description:
1. when on a call, cover the proximity sensor >> screen turns off
2. while covering the sensor doubletap the screen (this is the reason for this issue!)
3. uncover the sensor >> screen stays off
The problem is that the doubletap is registered as a power button press and therefore the screen stays off.
It only happens if you accidentally touch the screen with your face, which is likely to occur on a phonecall.
I've already mentioned this in a commit and they said they know about this issue.
The needed commit needs to be ported from cm12.1.
So I guess we can only wait...

Thanks for your response, mate. But CM seems to have fixed this issue because I just flashed the 02/03 CM13 nightly and the proximity sensor works just as it should during an incoming call; no issues there.
I'm going to try flashing another ROM on top of this.

AcmE85 said:
This is the exact bug description:
1. when on a call, cover the proximity sensor >> screen turns off
2. while covering the sensor doubletap the screen (this is the reason for this issue!)
3. uncover the sensor >> screen stays off
The problem is that the doubletap is registered as a power button press and therefore the screen stays off.
It only happens if you accidentally touch the screen with your face, which is likely to occur on a phonecall.
I've already mentioned this in a commit and they said they know about this issue.
The needed commit needs to be ported from cm12.1.
So I guess we can only wait...
Click to expand...
Click to collapse
I just went through your post again and it seems that you misunderstood my issue.
Apart from the issue that you mentioned, the proximity sensor is turning off the screen even before I have answered an incoming call. So, for example, I get a call when the phone is in my pocket. When I take it out, it takes a while for the screen to turn on which is frustrating. If I don't answer the call, the screen should remain on for as long as the phone rings, irrespective of whether the proximity sensor is covered or not. But, in my case, if the proximity sensor is covered when the phone is ringing, the screen turns off. Am I being clear now?
So, after a few intense sessions of flashing different ROMs, it seems that the official CM13 nightly and CandySix are the only ROMs where the proximity sensor is not broken for incoming calls. I guess I'll be sticking with CandySix for the foreseeable future.
But I'd really appreciate if someone can identify why this is happening with all other ROMs and not with official CM13 and CandySix.

girishb said:
I just went through your post again and it seems that you misunderstood my issue.
Apart from the issue that you mentioned, the proximity sensor is turning off the screen even before I have answered an incoming call. So, for example, I get a call when the phone is in my pocket. When I take it out, it takes a while for the screen to turn on which is frustrating. If I don't answer the call, the screen should remain on for as long as the phone rings, irrespective of whether the proximity sensor is covered or not. But, in my case, if the proximity sensor is covered when the phone is ringing, the screen turns off. Am I being clear now?
So, after a few intense sessions of flashing different ROMs, it seems that the official CM13 nightly and CandySix are the only ROMs where the proximity sensor is not broken for incoming calls. I guess I'll be sticking with CandySix for the foreseeable future.
But I'd really appreciate if someone can identify why this is happening with all other ROMs and not with official CM13 and CandySix.
Click to expand...
Click to collapse
actually i think u messed up a bit mate dont mention calling ! something like screen OFF when i recieve a call from someone even when not answered or something like this ! and now getting back to your query i flash RR and CM13 by jgcaap right now just for checking ur issue and i dont have this i kept the phone on the table , called from my other phone and covered the proximity sensor with my hand ! screen was still ON .. and i should mention my RR build is a bit old ! i have been using jgcaap cm 13 from many days ! so

Well, there was only so much I could put in the title. I think my OP explains the issue clearly.
Also, can you try the latest version of RR or Bliss ROM? Because as I said, I wasn't having this issue on the older builds. I also don't have this issue on the official CM13 nightly or CandySix. I just want to find out what's causing this issue on my phone with other ROMs.

@girishb
Ok I see. The way you put it, I thought cm based roms includes stock cm13.
Regardless. The commit which fixed the proximity sensor with screen off has been merged on 02/20.
When did the other cm based roms get their last update?

AcmE85 said:
@girishb
Ok I see. The way you put it, I thought cm based roms includes stock cm13.
Regardless. The commit which fixed the proximity sensor with screen off has been merged on 02/20.
When did the other cm based roms get their last update?
Click to expand...
Click to collapse
but still that issue of phone getting locked furing call persists right ? i mean during call i get this lock sounds sometimes and i need to double tap agn to disconnect the call ! anyways im sure there is a more recent build after 20/2 for rr ! anyawys i should check and get back on taht

thepico said:
but still that issue of phone getting locked furing call persists right ? i mean during call i get this lock sounds sometimes and i need to double tap agn to disconnect the call ! anyways im sure there is a more recent build after 20/2 for rr ! anyawys i should check and get back on taht
Click to expand...
Click to collapse
Im on RR 24 and i can still see this issue. Lets see wht RR Mod comments on that.

Uh, I'm pretty sure that's a different issue. What you guys are facing is basically the screen getting locked when a call is going on, which should not happen. This issue is consistent across all ROMs that I have tried, even AOSP ones. So I don't think that's a CM issue.
My original issue is slightly different. During an incoming call, the screen should remain on for as long as the phone rings, right? If I choose to answer the call, that's when the proximity sensor should kick in and turn off the screen as I move the phone to my ear. However, in my case, if the proximity sensor is covered during an incoming call, it keeps the screen off so I can't see who's calling unless the sensor is uncovered. This should not happen. I hope this explains the issue properly.

girishb said:
Uh, I'm pretty sure that's a different issue. What you guys are facing is basically the screen getting locked when a call is going on, which should not happen. This issue is consistent across all ROMs that I have tried, even AOSP ones. So I don't think that's a CM issue.
My original issue is slightly different. During an incoming call, the screen should remain on for as long as the phone rings, right? If I choose to answer the call, that's when the proximity sensor should kick in and turn off the screen as I move the phone to my ear. However, in my case, if the proximity sensor is covered during an incoming call, it keeps the screen off so I can't see who's calling unless the sensor is uncovered. This should not happen. I hope this explains the issue properly.
Click to expand...
Click to collapse
What firmware are you on? Most proximity sensor issues are due to incompatible/old firmware.

YoshiShaPow said:
What firmware are you on? Most proximity sensor issues are due to incompatible/old firmware.
Click to expand...
Click to collapse
I have tried all modems from this topic (other than the h2os and oxygen one). I have also tried clean flashing the latest CM13 nightly before clean flashing any ROM. I also tried dirty flashing a ROM over the CM13 nightly with no luck. I used TWRP 2.8.6.0 for all of this.
What I can't seem to figure out is why I don't have these issues on the official CM13 nightly build or on CandySix ROM. All other ROMs that I have tried have this issue. If it's a firmware related issue, then shouldn't I be having this problem on all ROMs?

Any solution for this problem coz its really annoying.

I'm having the exact same problem with my phone running CyanogenOS 13.1.2-ZNH2KAS3P0-bacon. The screen doesn't turn on automatically if the proximity sensor is blocked in the beginning of the incoming call or alarm.
If someone finds a solution, please reply to my post

With CM12 or CM13, screen goes black when making calls and is stuck there

This is my first time installing custom ROM's on my otherwise stock Sprint Motorola photon 4G LTE. After successfully flashing CM13 (2016_08_20 snapshot release), I tried to make a call, and upon hitting "call" from the dialer, the screen goes black and stays that way. The only recourse is to hold down power button long enough to reboot. While the screen is black, there is no sound from the ear piece (i.e. it does not appear that the call is connected). Finally, while the screen is black, the phone does exhibit some reactions: it vibrates sometimes if I hit the power button, in other words, the device is still 'on" until I have to reboot it.
After this happened, I gave up on CM13 and flashed CM-12 (the latest snapshot release, from 2015) , and experienced the same behavior.
The call apparently was completed, because the other party received a missed call. However, there was no sound on my end (although there was side-tone, when I breathed on it)
I googled for about an hour, and saw examples of the same behavior on other devices claiming to be related to the proximity sensor (though in those cases, there apparently was audio in the ear piece-- ie. the call completed, and was in progress while the screen was black). This behavior was not observed a few minutes before under stock ROM in the same device (so doubt it's a strictly hardware issue, so doubt I need to open the device and clean the sensor, per some of the suggestions out there).
I suspect the answer is very basic, because I found no similar threads searching XDA.
Please let me know any ideas. I did not do anything about updating my baseband version from stock before flashing the CM ROMs., but don't know if I have to I'm a noob at custom Rom's and just remembered that you had to worry about the baseband / radio version back on the HTC Evo 8 years ago, which was my last time flashing. Again, the ROM itself worked fine-- wifi and 3G/LTE connectivity was a success.
Let me know any ideas.
thanks

After restoring to stock, dialing worked again on the phone, but the behavior on the device was different from two other photons I tested next to it.
In the stock ROM, the call connected, but the screen turned off immediately upon hitting "call" (even when the phone was on the desk). You could get the screen back (in stock only) by hitting the power button.
In my other two photons, the black screen does not kick-in immediately. So it does appear it could be something having to do with the proximity sensor (i.e. it's always engaged). I don't have the skills to confirm. I am writing-off this phone for now, and have a different device (so not a high-priority thread at this point), but let me know if anyone has any ideas. Thx.

There's a way to validate if the prox sensor is working - zDeviceTest in the Play Store will test all of the hardware, and it will also show the metrics each piece of hardware is receiving - the prox sensor being fairly simple, it just identifies if an object is "near" or "far".
I always recommend making sure everything works in the stock ROM before flashing anything custom - as you need to validate everything works before making tweaks.

My advice is the same as arrrghhhs. (This name really looks like it was typed with a Photon Q with some characters repeated by the device >.>)
I noticed that my proximity sensor sometimes "stuck" to near (I use some different app [SatStat] so it shows 3 cm or 100 cm instead of near/far). Winking a little above the sensor helps sometimes. But your problem sounds like a defect.

Screen turns off immediately after dialing/answering a call

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:
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
Your device is a Moto X (1st generation/2013 )? A quick Google search would tell you this is a Proximity Sensor issue, it is device specific whether anything can be done or not, so you might want to check your device's group.

acejavelin said:
Your device is a Moto X (1st generation/2013 )? A quick Google search would tell you this is a Proximity Sensor issue, it is device specific whether anything can be done or not, so you might want to check your device's group.
Click to expand...
Click to collapse
No bro. Mine is a moto g3 xt1550. Searched the forum later yday and found that it is calibrating proximity sensor issue. Will try doing that and check. Thank you for the response

abhishekturumella said:
No bro. Mine is a moto g3 xt1550. Searched the forum later yday and found that it is calibrating proximity sensor issue. Will try doing that and check. Thank you for the response
Click to expand...
Click to collapse
Sorry, you must have typo'd earlier, you clearly said XT1055 which is a valid Moto device. Anyway, sounds like you're on the right track.

acejavelin said:
Sorry, you must have typo'd earlier, you clearly said XT1055 which is a valid Moto device. Anyway, sounds like you're on the right track.
Click to expand...
Click to collapse
Oops. Sorry. It was a typo. Mine is motog3 xt 1550.

abhishekturumella said:
Oops. Sorry. It was a typo. Mine is motog3 xt 1550.
Click to expand...
Click to collapse
please let me know if you can some how fix this issue. I have same issue ands I did proximity caliberatiin as well and it did not resolve my issue

chungomungo1 said:
please let me know if you can some how fix this issue. I have same issue ands I did proximity caliberatiin as well and it did not resolve my issue
Click to expand...
Click to collapse
I too did proximity sensor calibration but it worked only for few times. But the only solution that's working is whenever screen goes blank I rub with my finger on proximity sensor area for 3-4 times as if like cleaning it. Immediately the screen lights up. This is the solution am doing since past few times and its working consistently.

abhishekturumella said:
I too did proximity sensor calibration but it worked only for few times. But the only solution that's working is whenever screen goes blank I rub with my finger on proximity sensor area for 3-4 times as if like cleaning it. Immediately the screen lights up. This is the solution am doing since past few times and its working consistently.
Click to expand...
Click to collapse
Thanks

Can we disable the proximity sensor ???

Mohammed Siamwala said:
Can we disable the proximity sensor ???
Click to expand...
Click to collapse
Yes u can disable the proximity sensor.....
Procedure:
1. The device need to be rooted
2. Install the xposed module
3. After installing search for sensor Disabler apk in xposed module
4. Install sensor Disabler and open the app and select the proximity sensor.
5. Select the value of proximity sensor to Maximum level and save it
6. Do the reboot
This whole procedure will disable ur proximity sensor ie ur screen will no go blank on any call.
Note : Xposed installer for nougat ROM is in development phase ...
Do it ur own risk I'm not responsible for any harm.
All the best :good::laugh:

abhi8939 said:
Yes u can disable the proximity sensor.....
Procedure:
1. The device need to be rooted
2. Install the xposed module
3. After installing search for sensor Disabler apk in xposed module
4. Install sensor Disabler and open the app and select the proximity sensor.
5. Select the value of proximity sensor to Maximum level and save it
6. Do the reboot
This whole procedure will disable ur proximity sensor ie ur screen will no go blank on any call.
Note : Xposed installer for nougat ROM is in development phase ...
Do it ur own risk I'm not responsible for any harm.
All the best :good::laugh:
Click to expand...
Click to collapse
Thanks for your help !!
But will need to wait as I'm using Nougat ROM :laugh:
Any disabling method for 7.1.1 ???

Mohammed Siamwala said:
Thanks for your help !!
But will need to wait as I'm using Nougat ROM :laugh:
Any disabling method for 7.1.1 ???
Click to expand...
Click to collapse
To my knowledge it is not there... U can Google it bro
As I'm also facing this problem...
Some info about xposed....
Xposed is not compatible with Nougat, the truth is it may never be a viable option again due to security changes in Android. The developers have said that Xposed is on it's last legs, the changes in Android and the security are becoming impossible to work around. Remember last year at this time, the developers of Xposed had mostly given up and thrown in the towel and said Xposed was dead with Marshmallow, but they got lucky and found a work around just before completely giving up. They have not as yet found such a exploit to make it work, and if they do it will only be temporary as the next version of Android will probably close it again. They may get it to work with Nougat, or maybe not, either way best bet is to learn to live without it, because it will be gone before too long.

abhishekturumella said:
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
hi buddy i have a solution for this hope this will be helpful............
i have flashed the cm 12.1 yesterday on my moto g3 and since yesterday i didn't faced the problem of screen going off on call .....
this conclude that rom is somewhere responsible for screen off during call on some phones( my opinion )
you can try this if u want:fingers-crossed:

This will help you mate
github.com/Alberto97/proprietary_vendor_motorola/blob/cm-14.1/osprey/proprietary/lib/hw/sensors.msm8916.so?raw=true
Paste this in system>lib>hw>
And change the permission to rw- r-- r--