Finally had a "real" issue..

[Frisco]

..screen blanking when attempting to input from the number pad during a call.

The screen would go blank so quickly that I did not even have time to input one digit. It was behaving as if I'd kept the phone at my ear instead of holding it down in front of me so that I could use the keypad to continue in the menu of the place I'd called.

I am not sure if I've cured it or not; I did a live battery pull about an hour ago and have made several calls without the glitch happening.

I'd like to know if anybody else with an Eris on 1.5 has had this problem, and if so, if you've found a reason and/or solution. Did a battery pull do the trick? At another site a factory reset was suggested, which is something I'd rather avoid unless absolutely necessary.

 

[smacky]

Yeah, I have that issue. I think it's the proximity sensor fudging up a bit. I usually just hit the Send button to bring the screen back to life and do it that way. But I also don't find myself usually needing to input numbers during a call. Those damn machines.

 

[Jmtegra]

Ive had issue in 1.5 and 2.1 as well. I got to the point where if i know i have to input anything during a call i would just leave the phone on speaker.

 

[jayjay1122]

..screen blanking when attempting to input from the number pad during a call.

The screen would go blank so quickly that I did not even have time to input one digit. It was behaving as if I'd kept the phone at my ear instead of holding it down in front of me so that I could use the keypad to continue in the menu of the place I'd called.

I am not sure if I've cured it or not; I did a live battery pull about an hour ago and have made several calls without the glitch happening.

I'd like to know if anybody else with an Eris on 1.5 has had this problem, and if so, if you've found a reason and/or solution. Did a battery pull do the trick? At another site a factory reset was suggested, which is something I'd rather avoid unless absolutely necessary.

Frisco, I had the issue when I was on 1.5 because the screen protector I was using seemed to interfere with the proximity sensor. I removed it the same day I flashed to 2.1 and it has not happened since so I am 99% sure it was the screen protector.

 

[Frisco]

Frisco, I had the issue when I was on 1.5 because the screen protector I was using seemed to interfere with the proximity sensor. I removed it the same day I flashed to 2.1 and it has not happened since so I am 99% sure it was the screen protector.

Thanks for that, but no screen protector is being used on my device.

I am thinking that Smacky hit it with the wiggy proximity sensor.. I'm just wondering why it changed behaviors three months into using the phone and also why the battery pull fixed it (or seems to have fixed it.. so far).

 

[jayjay1122]

Thanks for that, but no screen protector is being used on my device.

I am thinking that Smacky hit it with the wiggy proximity sensor.. I'm just wondering why it changed behaviors three months into using the phone and also why the battery pull fixed it (or seems to have fixed it.. so far).

no worries!

 

[metzy75]

I have had this issue as well in 1.5, 2.1 v2,3. My question is where is the proximity sensor located??

 

[Frisco]

I have had this issue as well in 1.5, 2.1 v2,3. My question is where is the proximity sensor located??

It is on the far upper left as the front faces you.

 

[SoCal64]

Only time I have experienced that was trying to have a skin on the phone. The hole for the sensor wasn't big enough.

Other than that I haven't had a problem.

 

[Demache]

I have had this issue as well in 1.5, 2.1 v2,3. My question is where is the proximity sensor located??

To the left of the earpiece. Make sure that it isn't covered at all. Its very sensitive.

 

[smacky]

Clean fingerprints off of it.

My MBP won't let the keyboard illuminate at all if it senses adequate sunlight. Dunno why it does this, but it does. It uses the camera. When you cover up the camera lens, regardless of the time of day or whatever, the keyboard illuminates. Here's where it gets funky.

If I'm wearing a polo, which is usually a darker color, it will not turn on like normal. If, however, I'm wearing a bright orange Auburn shirt or my white undershirt on, it will turn on.

My theory, as silly as it might be, is your clothing and whether the sensor is sensing your dark shirt instead of the sunlight around. Or...just something dark in the room in general. It associates the darker color with being blocked from sunlight with it being on the side of your face. When it senses light, it'll go on.

Have you dropped your Eris? Even if you haven't, the sensor may be a bit knocked up out of place. Yes. I said knocked up.

 

[xScorch Muffinx]

I used to have this, then I did a hard reset(becuase of other problems that the phone was having) and it seemed to fix this problem. Then, I upgraded and still had no issues.

 

[Frisco]

Well, I was able to duplicate the problem; you're right. I put a smudge (dish sink water, just a dab) in the area of the sensor, made a call to the airport and voila: screen black when trying to input from the number pad.

Battery pull didn't fix it, it was my habit of wiping the device down right before powering it up.

 

[smacky]

Well, I was able to duplicate the problem; you're right. I put a smudge (dish sink water, just a dab) in the area of the sensor, made a call to the airport and voila: screen black when trying to input from the number pad.

Battery pull didn't fix it, it was my habit of wiping the device down right before powering it up.

I love when I'm right. Inflated ego, FTW.

 

[s10onn2o]

what i do on the sensor is just a quick "swipe" over it most of the time it works.

 

[Frisco]

what i do on the sensor is just a quick "swipe" over it most of the time it works.

I am now resigned to acquiring that habit; that really does pan out to be the problem I was having.. I believe that it just cropped up lately as the weather warmed up a bit where I live and there might be a slight, rather appealing I'm sure, glow to me this time of year outdoors which is sloughing off onto the phone as I make calls.

 

[Trident]

I have removed/ edited some posts. Please keep this thread on topic or it will be closed.

 

[jreed2560]

hmmmm....interesting.....I have always found pressing the volume rocker can bring the screen back up as well. with one of the MRs that came out weren't you able to hit the power button to bring up the screen when it goes blank? Its hit and miss now, sometimes it will, sometimes it ends the call.

 

[s10onn2o]

I have removed/ edited some posts. Please keep this thread on topic or it will be closed.

Wont be nothing new

 

[Frisco]

hmmmm....interesting.....I have always found pressing the volume rocker can bring the screen back up as well. with one of the MRs that came out weren't you able to hit the power button to bring up the screen when it goes blank? Its hit and miss now, sometimes it will, sometimes it ends the call.

I was doing the button-pushing thing, to no avail; the screen remained black.

In my case it really was the sensor up there near the top, just to the left of the ear-piece, getting obscured just enough for the device to think it was still near my head. Wiping it off quickly does the trick for me.

 

[hallstevenson]

what i do on the sensor is just a quick "swipe" over it most of the time it works.

My wife told me she occasionally has to "wave" her hand in front of the sensor.

 

[s10onn2o]

Yea i have also notice that in different lighting it will act up to i got a buddy working with me right now on a rom he looking to see if theres a setting to change around to maybe fix it.