I just installed AOKP Unofficial 4.2.2 from this thread.
If I simply make a call, the proximity sensor functions as expected and near perfectly (I think there's slightly too much lag between removing the phone from one's ear and the screen coming back on... but not unbearable). With the keypad shown, I've found the behavior to be quite unpredictable. On my first call with the new ROM, I called my company voicemail and between inputting my password and cradling the phone, I could hear a bunch of key presses occurring. It ended up disconnecting the call. This is quite reproducible for me.
I'd like to know if this is a reproducible issue, intended function, and/or bug (which I will report if others can verify).
Method:
- Dial a number
- Set phone on table
- Put hand in viscinity of top of the phone
- Observe screen turning off and on as you move your hand over the sensor and then away
- Pull up keypad
- Repeat hand test and observe that the screen is not predictable
In trying this several ways, there's either a lag in detecting proximity, or it's just flaky. I actually find it really hard to reproduce consistently. Sometimes it actually will turn off (I can see peripherally that if I put it to my ear), however if cradling (with phone still well within what I could call "proximity" to my face/ear), it will dial numbers. In putting my hand in various positions over the phone, sometimes it turns off, sometimes not. With the keypad hidden, it turns off reliably 100% of the time.
The biggest difference I can reproduce is that if you put a single finger over the full width of the top of the phone (over the HTC logo -- the sensor is just to the left of the logo), it will reliably turn off the screen without the number pad, but not with it. I get that the sensor probably needs to account that one's fingers will be pushing on the screen to enter numbers, but something directly over the sensor (simulating an ear pressed to it) should turn it off even with the number pad shown, I would think.
Thanks for any suggestions of if you'd like any further information.
----------
ETA: S-off, unlocked bootloader, AOKP: aokp_jewel_unofficial_Mar-12-13, baseband 1.12.11.1210, Android 4.2.2.
Related
I have got the problem that sensors turn out my screen after calls start (incoming/outgoing) and it does not activate again when I want to end the call.
I have realized that after a call is started and the phone is moved (e.g. after typing a number, dialling and then move the phone to your ear) that this (or actually any movement) locks the screen.
I have realized that the movement actually activates the 'dial pad' (just as you would press the icon on the screen during a call) but somehow also fully de-activates the screen. You can get the screen activated again only by sliding the hardware keypad out. Then you can press 'x' on the screen to get back to the normal call screen (and then end the call normally).
I have got the 2nd SK17 now and it has got the same issue regardless which firmware I use (branded 4.0.A.2.335 from vodafone, 4.0.A.2.335 Generic or 4.0.2.A.0.58 Generic).
Anyone else got this issue and has got a solution.
Same here. its because of the light sensors.
http://forum.xda-developers.com/showpost.php?p=18404603&postcount=6
heres a guide to turn it off
Thanks for the quick response. Much appreciated.
However, I am afraid this does not resolve the issue. When applying as described in the guide the screen is de-activated straight after answering a call (without moving the device) and even when sliding the hardware keyboard out and pressing 'x' on the screen (to return to normal call screen) and then close the hardware keyboard again the screen is de-activated straight.
Ending calls now is only possible when the hardware keyboard is slided out.
Before applying as described in the guide at least the screen returned to be active after sliding keypad out, pressing 'x' and sliding keypad back in (and then not moving the device).
Therefore I have reverted back to what is was before for the time being.
Any other thoughts, hints, help.
----------
UPDATE 2011/11/27:
I have got my SK17 exchanged again (got the 3rd one now) and on this one it does not occur respectively call screen and sensors work perfect. Finally SE or vodafone seem to fix it on newly produced devices.
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
mrcash101 said:
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
Click to expand...
Click to collapse
Probably that or a bad flash, just reflash, see if it solves the issue.
Most likely it's something simple, like an issue with your proximity sensor. I know there was an app that could calibrate that but I forgot what the app was.
Stock Rom - Black screen while phoning
There is a similar problem on my wife's phone with a stock rom (not rooted Amaze from T-Mobile). When making or accepting a call, the screen will instantly go off even without leaning the phone against anything and won't turn on unless the power button is pressed. Sometimes the screen would turn on by itself after a while after the other phone was hanged.
I've downloaded AndroSensor app: the proximity value does't change even when touching the area near the earpiece. It keeps showing ( 0.5mA ) 3.5 in.
I've found a thread which is there since april 2012 and describes quite a similar problem.
okay.. i just the original post date for this thread.. please don't bring back threads that are 6 month's old which issues might have been solved already since no ones been posting in it for 6 months...
(anyways) this is what i was gonna say
on my current s3 when my phone is placed to my ear it cuts off the display.. and if you pass your hand anywhere near the sensor's to the top near the camera it cuts off the display.. maybe there's a feature like that enabled on the stock rom also.. or you could possible check with the system settings to see "screen" on/off settings in display or power saving mode.. or something...
Thanks for the answer. I didn't notice that the thread was that old. I think I will keep up a newer one. But the current issue isn't likely to have been solved.
The problem doesn't seem to be triggered by wrong sensor measures (because the screen will go off even after disabling the sensor) nor does it depend on the rom version (same thing on the CM10).
Resolved:
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
This phone has never been modified, no custom ROMS, never rooted, using the latest OS from AT&T ...
And today, for whatever reason, when making originating a phone call, and once I've hit "dial" ... the phone screen goes completely black except for the status bar at the top (the one you can swipe down). I'm saying that whereas usually, after hitting "dial" and as the phone dials, you can actually see a screen full of information (hang up botton, number/name of who your dialing, etc.) ... in this case and now, there is just a black screen.
Though there is a black screen (other than the status bar at top), I can still hear the phone ring and even have a conversation should somebody answer. But when the call is over (the person on the other end has to end the connection because I have no screen interface to do such), the screen remains blank (other than the status bar at top) and none of the bottom, permanent keys are operative either ("home" / "back" / settings / etc.). To get back to the home screen, I have to pop the battery and re insert it and re start the phone. But even then, it's acting weird: when booting, at the "Reimagine Possilbe" screen (I think that's what it says) it hangs there for about 45 seconds (usually only about 5 when functioning correctly) and will eventually end up at the home screen.
But if I originate a call, the cycle repeats.
I've completely reset the phone to factory defaults at least three times, formatted the USB storage and the whole nine yards but it remains glitched as described above.
...
So... has anyone seen/heard of this?
I'm thinking of just warrantying the phone as it's only about 5 months and I figure AT&T should have no issue as it's such a replicable problem and it certainly doesn't seem to be software related as it's completely stock and multiple factory resets have not worked but wanted to put a line out here first to see if anyone else has experienced this.
Thanks in advance for any information.
Best,
Joel.
I think the network is fugazi right now, as I had issues with the phone, and read about another user having same troubles. I'd give it a little time.
rangercaptain said:
I think the network is fugazi right now, as I had issues with the phone, and read about another user having same troubles. I'd give it a little time.
Click to expand...
Click to collapse
I sure hope so. Even though I've reset the phone (which sucks) ... I'd prefer that over having to go to the store and all...
Odd that a network problem could cause such, though ....
Thanks for the word ...
Best.
.joel
Just a llittle update ...
I changed the "Proximity Sensor" to OFF and now the normal iin-call screen appears but it never goes away, which can be problematic.
In general, I've always had the proximity sensor set to ON as this allows the in-call screen to blank after a few seconds (complete blank with no status bar at top) and then reappear when I remove the phone from my ear.
But when I re enable the proximity sensor, now ... the screen blanks immediately (excepting the status bar at the top) and never comes back ... even after my call recipient ends the call ...
I'm just gonna warranty at at the local service center; at this point (two days now with all my friends AT&T phones working fine) I'm pretty sure something is glitched with the internal sensor that manages the proximity settings ...
Thank God for warranty.
Proximity sensor is supposed to turn the screen off when held to your face, though I have yet to see it do that. On my phone the proximity sensor turns off the display every time I make a call or play a voice mail. This is really annoying, I almost hold the phone to my face, I have headphones, and sometimes I have to do a battery pull to end a call, and forgot about accessing other information on the phone while on a call.
I have found a patch that works with limited success by use of a startup script which resets the sensor, but it's not reliable. I understand that this is a bug in cm10,and I am running pacman based on cm10.2
Does anyone know of any other solutions? Like can I just turn it off? My old phone had no proximity sensor and accidental button presses were rare.
Kryxan said:
Proximity sensor is supposed to turn the screen off when held to your face, though I have yet to see it do that. On my phone the proximity sensor turns off the display every time I make a call or play a voice mail. This is really annoying, I almost hold the phone to my face, I have headphones, and sometimes I have to do a battery pull to end a call, and forgot about accessing other information on the phone while on a call.
I have found a patch that works with limited success by use of a startup script which resets the sensor, but it's not reliable. I understand that this is a bug in cm10,and I am running pacman based on cm10.2
Does anyone know of any other solutions? Like can I just turn it off? My old phone had no proximity sensor and accidental button presses were rare.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator&hl=en
It works. Mine is set to 100 on top and 0 on the bottom. I don't know what both of them do, but those values work for me. Haven't touched the app since first use, it sets on boot automatically.
thank you. i will benefit from this greatly
Coming from a OP5 with a separate fingerprint sensor (rather than under display), I'm used to being able to unlock the phone just by placing a finger on the sensor - even when the display is off.
On the 10T, the sensor only seems to work with the display is on, so I need to jiggle the phone a bit too wake it and then present my finger.
I found a setting 'fast unlock' which reads like the sensor is always active however I can't see any difference and pressing when the screen is off does nothing.
Anyone seen this / know how to get it working?
(For context, this is mostly an issue when I leave the phone on the desk and want to check something without moving the phone. If I pick it up then it wakes up and sensor works as expected)