Phone: Samsung Fascinate
ROM: MIUI 1.7.29
Problem: Just after completing a phone call, I pull my phone away from my face and attempt to press the "End Call" button. The problem is that the screen will still be black. It's somehow not detecting that the phone has been pulled away from my face apparently. When I press the power button in hopes of waking up the screen, nothing happens. I think the reason that is, is because pressing the power button during a call, may actually be muting the call.
In any case, when this occurs, I have to wait for the person on the other line to hang up their phone. My screen will then wake up and show that my call has been ended.
I did some research online and found some options to toggle:
Settings > Programs > Call Settings >
There you will find "Enable proximity sensor", wich I have set to on, and also "Enforce proximity sensor". That switch was set to on, and so I changed it to OFF. Even so, my problem still exist.
Does anyone know what "Enforce proximity sensor" even means, and what does it do precisely?
Any other suggestions?
Thanks!
I don't have any suggestions, but I am experiencing the same issue on CM7, build #10.
I am using MIUI 1.7.28 and experiencing your EXACT problems. I have tried turning them off and on again, rebooting, but it still doesn't work.
This is frustrating, any ideas?
from what I've read none of the sensors work that great on the GB ROMs yet, and won't until fascinate specific source is available.
Wow! Yes this is a known issue with all of the GB roms except for any bassed off of the EC09 leak.
EC09 has been known to eat SD cards! [just a warning]
Low call volume and proximity sensor are the two BIGGEST known issues!
Related
Over the past week or so I have noticed the backlight on my Atrix acting strange during calls. Sometimes it will not shut off when placed next to my head(I can see the screen out of the corner of my eye) or it will not light up when taken away from my head(to key in a selection on a menu). Sometimes it also shuts the backlight off as soon as the call is placed and I have to press the power button to "wake it up" so that I can make a selection.
The only other thing that I noticed just a little bit ago is - while in a call the LED next to the earpiece appears to be glowing red(dim - like the Terminator's eye right before it got crushed ).
I haven't added any apps in the last two weeks and there haven't been any major updates to speak of.
The phone is basically stock. I did root it so I could use titanium backup and barnacle.
Build: OLYFRU4 1.8.3
Kernel: 2.6.32.9-00007
baseband: n_01.77.15p
android version: 2.2.2
sys ver: 4.1.83.nb860.att.en.us
Has anyone else had a similar problem? More importantly, has anyone else resolved a similar problem?
Thank you in advance for any assistance provided.
Interesting.. I have similar problems, and I've heard this is a known problem with the Gingerbread update (which you haven't done it seems). I've personally noticed that this happens after I use bluetooth and making calls and stuff with BT devices. Do you do anything like that?
I do use a bluetooth headset but haven't noticed any problems when using it.
Shortly after making this thread I checked for any OTA updates and there was the gingerbread update available. I went ahead and performed the update and the problem still exists.
I also believe that my terminology was different and that is why I didn't have success when searching. I have found several threads describing the problem as dealing with the proximity sensor instead of the light sensor. I have not found a definite solution though yet - I'm contemplating a factory reset.
So I went ahead and did the big wipe and still have the same issue. I've read over the other "proximity issue" threads which all involve editing the value in build.prop.
The problem with this is, mine seems to have problems both ways. I've had it blank the screen right after pressing "dial" and then I've also had it not blank the screen at all(allowing it to cheek dial). The other weird thing I mentioned in my first post, is the sensor LED( to the right of the ear slot) is glowing red when there is an active call. I don't recall seeing it do that before.
I'm really tempted to have an insurance claim really soon.
71chevellejohn said:
So I went ahead and did the big wipe and still have the same issue. I've read over the other "proximity issue" threads which all involve editing the value in build.prop.
The problem with this is, mine seems to have problems both ways. I've had it blank the screen right after pressing "dial" and then I've also had it not blank the screen at all(allowing it to cheek dial). The other weird thing I mentioned in my first post, is the sensor LED( to the right of the ear slot) is glowing red when there is an active call. I don't recall seeing it do that before.
I'm really tempted to have an insurance claim really soon.
Click to expand...
Click to collapse
Unfortunately, it sounds like your proximity sensor (or logic board in general) may be going haywire - meaning a hardware problem not a software problem (I'm guessing that since, as you said, it's happening both ways)...
In my sig there is a app called Build.prop editor. You can use this to change the proximity timing and distance. the little red light you see is the infrared sensor that tells the screen to shut off.
In the build.prop edit mot.proximity.delay=200
and edit mot.proximity.distance=30
should fix screen not turning off issue.
Once again link in my sig for build.prop app( must be rooted)
You can try other values that fit you, doesnt have to be 200 and 30
Hi,
I am having issues with ending calls. After I speak with someone and I remove my photon away from my ear, the screen refuses to turn on. The calls stays connected. The only way to end the call is to pull the battery. This happens randomly and frequently almost half the calls.
The entire phone is unresponsive, even the power or volume buttons do nothing. The screen remains off. I guess this has to do something with the proximity sensor.
One thing I have observed is it happens a lot (much more than half) if I get to voicemail or any IVRS system.
I am on beta 0.4.2.1 of joker's. Is anyone facing the same issues? I have had this issue long, pre-beta 0.3
Looking for suggestions and fixes if anyone has one.
- Harakiri
Harakiri1298 said:
Hi,
I am having issues with ending calls. After I speak with someone and I remove my photon away from my ear, the screen refuses to turn on. The calls stays connected. The only way to end the call is to pull the battery. This happens randomly and frequently almost half the calls.
The entire phone is unresponsive, even the power or volume buttons do nothing. The screen remains off. I guess this has to do something with the proximity sensor.
One thing I have observed is it happens a lot (much more than half) if I get to voicemail or any IVRS system.
I am on beta 0.4.2.1 of joker's. Is anyone facing the same issues? I have had this issue long, pre-beta 0.3
Looking for suggestions and fixes if anyone has one.
- Harakiri
Click to expand...
Click to collapse
I did not experience this issue running 0.4.2.1. First thing I would do is download ScreenOn from the Market and set it to keep the screen on when using the dailer/call function.
Not sure what is actually causing this on your particular device though.
second day and already have many problems:
1. ringtone turned off vibration only. still have ringtone with incoming calls
2. making calls screen turned off once near ear. moving away from ear doesn't turn on the screen. try any button nothing works. have to turn off power to cut
3. smart stay isn't smart. screen still turned black even with bright environment
Am I unluckily with a faulty phone or they are known bugs? thanks
Not to sure mate
I have had NONE! of the problems that you have had, although i have had a few problems e.g. the turn to mute media stopped working and things like that, all i had to do was a restore and it is fine now, i was speaking to the people at the carphone warhouse (phone shop in the uk) they said they have only had 1 return since launch and that was because the screen wasnt big enough and they went for the note, i have also always found that samsung is happy to help you if you have a problem with your phone just give them a ring.
1: you need to explain exactly what you changed.
2: It's supposed to go off near ear because uses proximity sensor to save battery turning screen off.
3: Smartstay just doesn't work as well as it should do.
My HTC One Max's screen often comes on during calls. Then the touch screen reads my face's contact with the screen and acts according to what it thinks I selected. I have ended up several menu layers into apps that opened because of this. But worse, I have frequently had my calls mute - so the person I am talking to can no longer hear me.
I have had my HTC One Max less than a month, and it has had to be replaced twice, once because the 3G radio didn't work, and the second time because of this issue. Well, the current replacement has the same issue too. I used Android Sensor Box to test the functioning of the proximity sensor, which should be what controls this function. It appears to work, but my experience tells me that it stops working a few minutes into a call.
Your ideas and suggestions are welcome. I love the phone, but this is a problem I can't live with.
Is anyone else experiencing this issue?
My suggestion is to always press the power button during calls that way the phone only comes back on if you hit the power button again... The reason it comes on now during calls because your ear / side of your head covers and uncovers the sensors at the top of your phone so to eliminate that just turn the screen off by pressing the power button it work 100% for me, my wife had the same problem until I told her to start doing that.. Lmk if that works!!
Sent from my HTC6600LVW using Tapatalk
Hi, my mother has the Nokia 7.2 phone and few days ago it began to go to black screen when on a call. It on all the time, and you can't start the screen unless when the call is ended. I see that many has this error, but I couldn't fix the error permanently with any of there advise.
The only thing that seems to work, is going into developer mode, enable "USB-debugging" and "turn sensors off". Then from the top drawer I can turn off sensors. Now the phone doesn't go into black screen when on a call.
But the problem it, that it shouldn't be necessary to do this step, and it will turn off all other sensors also.
My plan is to take it to a service center as it many still be under warranty, but I don't want them to just say "Not hardware failure, wait for an software update" and then I have to pay for basically nothing.
So my question is, can I somehow test the proximity sensor and perhaps others, so I can be sure that it's a hardware or software error?