Database Info

Touch In Call Screen not working on the HD2

I tried to install this great piece of soft, Touch In Call Screen Tweak, because I am not totally satisfied with the way the HD2 manages the backlight during a phone call.
http://forum.xda-developers.com/showthread.php?t=488991
Sadly, for some reasons it seems that Touch In Call Screen Tweak does not work on the HD2.
Did someone try? Any idea to make it work?
thanks...

Sorry but in what way are you not happy with the way the HD2 handles the screen during a call?
Surely what Touch In Call Screen Tweak tries to emulate using the G-Sensor etc. the proximity sensor does effortlessly on the HD2. I really don't see what you would want to install Touch In Call Screen Tweak. Unless I am missing something?

richardirv said:
Sorry but in what way are you not happy with the way the HD2 handles the screen during a call?
Surely what Touch In Call Screen Tweak tries to emulate using the G-Sensor etc. the proximity sensor does effortlessly on the HD2. I really don't see what you would want to install Touch In Call Screen Tweak. Unless I am missing something?
Click to expand...
Click to collapse
Richard,
Because I think that Touch In Call screen is far more efficient:
- The HD2 only uses the proximity sensor, whatever the position of the device,
- Touch In Call Screen combines the proximity sensor AND the G-sensor.
I am using my HD2 a lot, and sometimes during the phone call I touch the screen and enter in the Menu by mistake. The HD2 system does not work all the time.

arturobandini said:
Richard,
Because I think that Touch In Call screen is far more efficient:
- The HD2 only uses the proximity sensor, whatever the position of the device,
- Touch In Call Screen combines the proximity sensor AND the G-sensor.
Click to expand...
Click to collapse
I have not experienced any issues yet with the proximity sensor and knocking menu buttons.
I also didn't realise the software could use the proximity sensor as I thought it was designed around devices like the Diamond & HD which don't have proximity sensors.
I find that If the phone is away from my ear then I would ussually want the screen on. Not sure how it handles the screen when using speaker phone though.

Touch Incall screen tweak doesn't use proximity sensor, it uses the g-sensor and the light sensor to emulate what a real proximity sensor does.
I haven't used it on HD2 but previously I've found it difficult to set up because of confusing wording in program settings. So I wouldyousuggest that you try to fiddle with them a little more.
On a side note, while TICST is just an attempt to emulate the real sensor in HD2, it has an option to keep screen off while using headset, which is something I'm badly missing now...

Hi, anybody knows how to change the settings of incall screen off on HD2? My HD2 don´t dim the screen while i cover the proximity sensor during a call.
Is there any menu or registry setting?

Touch screen stays on during call (phone by ear)
I have the same problem: my touch screen stays on during a call when I have the phone by my ear. I have this since I upgraded to the official HTC 1.66 rom. Anyone experiencing this as well? Any solutions? Help would be appreciated...

Hi. Same here. My screen stays on as well. Did someone got a solution?

jan227 said:
I have the same problem: my touch screen stays on during a call when I have the phone by my ear. I have this since I upgraded to the official HTC 1.66 rom. Anyone experiencing this as well? Any solutions? Help would be appreciated...
Click to expand...
Click to collapse
Same issue here with the 1.66. Got around this by flashing to a cooked rom,

nosh10 said:
Same issue here with the 1.66. Got around this by flashing to a cooked rom,
Click to expand...
Click to collapse
nosh10, that's interesting. Which cooked ROM did you flash, and did it solve the problem of the screen in call? Besides that, does the ROM work well, or does it cause other problems?
I have the same problem as everybody else here, using stock ROM 1.66. Screen doesn't turn off reliably in call (sometimes yes, other no), leading to push buttons, hang up call, accidental conference call with Australia, China, and US .

See :
http://forum.xda-developers.com/showthread.php?p=9463284#post9463284

[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!

Sony proximity sensor bug?

Hi guys, I have a issue with proximity sensor, it happend from 4.4.2 and now i'm in 4.4.4 and still facing with it.
At the first time I think that is my app problem, so I don't care at all. But today, I found it (maybe to late) happend with all thing include call and the test in hidden menu.
This is the way how I made it:
1. cover the proximity sensor
2. start the call
-> screen go off
3. un-cover the proximity sensor
-> screen not turn on even the call ended. All thing you can do is press Power button twice
If this only happend with call, ok, I can accept it like a feature.
But when I try reproduce the issue in *#*#7378423#*#* - Service tests - Proximity Swich test, the result show that the proximity sensor cannotchange state and always "Detected".
So idk the problem is my phone or sony firmware, anyone can confirm that? I did some searching but can't find anything.
Thank you.

i think the problem is in proximity sensor because as u say it happend in 4.4.2 and 4.4.4, and i've use both firmware and i dont face any problem like that, and u can check if u have ur screen guard on ur proximity sensor, because it happens with me once i put my screen guard on proximity sensor thinking nothing will be wrong because screen guard is transparent but that my proximity sensor becomes like what u say, always detect, check it

It's not the problem of sensor, this problem is in firmware. I am facing the same problem and my frd too.

ChetanLokhande said:
It's not the problem of sensor, this problem is in firmware. I am facing the same problem and my frd too.
Click to expand...
Click to collapse
i never face this problem,
which kernel you are using, i am using vinays nitrogen kernel, does this problem occur on stock ?

Dialer Screen going blank on incoming calls and also when dialling out : please help

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

Proximity Sensor Issue

Hello there!
I have the problem since I put matte screen protector on my phone. Everytime I call/answering call screen goes black. Maybe it needs calibrating proximity sensor or something like, but I don't know how.
I would be very grateful if you could suggest me some way to fix this problem.
Thanks

Some screen protectors just mess with the proximity sensor, remove them and verify the sensors operation... If it fixes the problem, contact the manufacturer/retailer and request a refund, a screen protector designed for the device should not interfere with any sensor's operations.
There is no way to calibrate the sensor I am aware of.

Sensors Test app by Ettore Zaffaroni is a handy tool to check proximity sensor and others. It detects 3 levels of proximity, less than 1 cm, between 1 and 3 cm, beyond 3 cm on Moto G 3th. The proximity sensor on this model is right between the ear speaker and the front facing camera.

Thank you both for the answer.
The protector I'm using currently is custom cut (cause there was no other option for my phone in my region). It covers sensor and hence the problem comes. When putting on I didn't think there would form this kind of obstacle. The Clear one that I had purchased from amazon and used before was cut nicely and didn't cover sensor.
Lately I was searching some tools for calibrating and came up with an app named Proximity sensor restore/repair by Mobile Direction. As it says it only repairs the software problem not hardware. I gave it a try and for now sensor works. Though, I don't know if it will be permanent solution.
Alternative is to cut there too where proximity sensor is located, cause I don't want to remove the protector yet.

Oh no ! here it comes again! I had a long standing issue on Moto G Osprey with screen going blank when making or receiving a call . WIth AospExtended ROM 26/09 version it was resolved . In mean time I spent 1 year tried to resolve teh issue by installing stock motoroal firmwayre, proximity sensor disabling via exposed module, proximity sensor caliberation etc and nothing worked . But with 26/09 build thsi was resolved and my screen was working on 90% of calls and on 10 % dialler or call accepting option was not apearing but status bar was visible where on Andropid Nougat roms and Marshmellow Roms it was 90% of calls were made received with blank screen and then rubbing over sensor to wake up screen .
After the Alpha build 30/09 this has came back again . I have checked again on 26/09 build and issue is not there . Can anyone suggest why I am having this issue with new build or what changes been made into new build which can cause this issue ? I understand only few people have this issue and even on Lenovo forums there is no solution to it

Proximity sensor Complete solution 101%
I have also same problem and All osprey custom ROM last update has this problem.
But guys u can use cypheros 4.1.2 there is no problem with proximity sensor it's same stable as AEX 4.6
get.cypheros.co