Database Users

EVO won't stay "asleep"

My phone died today and when I got home to charge it, I noticed that after pressing the sleep/power button, the screen turns off and then about a second later comes back on. It does this regardless of if it's plugged in or not. I took it into Sprint and they're going to give me a new one when they get their paws on some. Right now I'm just looking for ANY possible work around to the problem.
I've done a factory reset, added a pattern/code, and installed NO LOCK but nothing can keep the screen from coming back on after pushing the power button...
(I also had another problem with the phone, the camera has a HOT PINK tinge about 85% opacity. I can go without the camera for a few weeks until the new one gets here but any help with that is very welcome)
~ ACE

are you running a rom ?

freddyamazin said:
are you running a rom ?
Click to expand...
Click to collapse
Everything is stock.

Mine had a similar problem when I was on 2.1 I would charge the phone overnight and at some point in time the phone would turn the screen on and not turn back off. Or sometimes it would sitting on my desk and just randomly turn the screen on. After I upgraded to 2.2 it stopped. I never could figure out what was causing it to wake.

Are you using ChoiceDialer+? There is a known bug where the screen will not shut off after making a call with ChoiceDialer, though a reboot does fix it.

[Q] Black screen while in call

Hello,
i'm having troubles with the last OTA 2.05.405.2 update on a stock unbranded, sim-free HTC legend.
The weird thing is my screen going black when calling to my voicemail and not being able to get back to a normal screen. So I cannot interact with the phone anymore.
I get the same problem with other phonecalls too but when the other side hangs up, my screen comes back normal.
I suspected an incompatible app so i reset my phone to factory settings, but this didn't help.
My next step was to download the RUU_Legend_HTC_WWE_2.03.405.3_Radio_47.39.35.09_7. 08.35.21_release_130330_signed ROM from the internet and make myself a goldcard. The process of "updating" (downgrading in fact) goes well until i get an errorcode "140" "Bootloader problem"
Is there a way to replace the bootloader to a previous one? How do I proceed?
Tnx

Men, use search... There is a good thread about downgrading.
Sent from my HTC Legend using XDA App

Black screen while in call -- proximity sensor broke?
OK, I managed to downgrade my phone succesfully to 2.03 official rom.
My black screen problem still exists. Apparently, my light sensor is not sensitive enough.
When in call, the screen goes black, even if I don't hold it to my ear.
When I put the sensor under a bright light, the screen goes on again. So there must be a wrong setting or just a fysical problem.
Does anyone else have this problem (only when in call)

I have the same problem but the screen turns back on when I shake the phone.

I called HTC service today.
the problem could be software or hardware, for software related problems, a hard reset (factory settings) should resolve the problem.
In my case, i had to send it back for repair.

I hope you unrooted before you gave it in for repair. Or did you flash an unrooted ROM when you downgraded?

I flashed a stock rom 2.03.405.4 from shipped-roms.com.
My previous Rom was 2.05.405.3 via on OTA update.
I suppose there is no problem with that.
Tnx for the attention.
Sent from my HTC Legend using XDA App

Like in2ition, when I move the handset away from my ear while on a call the screen comes backs, but I'm guessing yours didn't. It's most likely a power saving 'feature' as while you are on the phone you are probably not going to be looking at the screen.
Were any other features not working on the phone? Games like Teeter etc?
Anyway, hope it comes back fixed.

Well this adventure is getting out of hand.
I sent the phone back to HTC and they claim the failing light sensor is not covered by the warranty because they have seen some scratches on the cover, not on the screen!
So they send me a repair note of 225€!!!
Be aware that HTC is trying to get out of their responsability when sending back you device.
I'm trying to escalate with HTC but so far (after six weeks) no luck, the call center is holding back the answer...

Viskoze, I seem to have the exact same issue. I am very grateful that you shared your experience; thanks to that I know that returning the phone as high chances of being an expensive move (my legend has scratches too) and I seem to have found a workaround (putting the phone under a bright light doesn't work and wouldn't be as easy):
sliding my finger from left to right above the screen brings the phone back to life.
Even if there is a hardware pb (the light sensor), the fact that pressing the standby button doesn't bring the phone back to life is definitely a bug to me. Hopefully they fix that in a future release.
I will try to remember to update this thread if this workaround doesn't prove to work well, but so far it works 100% of the time.

Light sensor

There is one on the G2, right?
The reason I ask is I'm pretty sure if there is, mine is broken, or something. Problem is, when talking on the phone, I am consistently either inadvertently putting it on hold, or muting the phone as it touches my face when held up to my ear.
Anyone else have similar problems?

yeaa there is i have had that happen on my tp2 so many times as well

digital_exhaust said:
There is one on the G2, right?
The reason I ask is I'm pretty sure if there is, mine is broken, or something. Problem is, when talking on the phone, I am consistently either inadvertently putting it on hold, or muting the phone as it touches my face when held up to my ear.
Anyone else have similar problems?
Click to expand...
Click to collapse
It has a light sensor and proximity sensor. Mine works perfectly. Whenever I'm on a phone call the screen turns off every time. Next time try setting your phone down while you're on a call and placing your hand over the top portion of the phone. Screen should turn off completely when you get within a few inches of it.

Bishybob said:
It has a light sensor and proximity sensor. <snip> Screen should turn off completely when you get within a few inches of it.
Click to expand...
Click to collapse
Thanks, that's exactly what I needed to know. Mine does not. The screen does turn off once the time out interval passes, but until that time it stays on, and the hold/mute problem occurs.
Now let's see what I can get done warranty wise.
Thanks for the replies.....

When making a call, my screen only goes dark when the phone is in a vertical position and then you put your hand over the sensors, otherwise if its on a table or laying flat the screen stays on while making a call.

tony597fitter said:
When making a call, my screen only goes dark when the phone is in a vertical position and then you put your hand over the sensors, otherwise if its on a table or laying flat the screen stays on while making a call.
Click to expand...
Click to collapse
Really? Mine turns off no matter what position it is in. Flat on the table or vertical/horizontal. Maybe it helps to say I'm post-OTA with no root.
Sent from my T-Mobile G2 using XDA App

Bishybob said:
Really? Mine turns off no matter what position it is in. Flat on the table or vertical/horizontal. Maybe it helps to say I'm post-OTA with no root.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Im post OTA and rooted with CM6.1RC2.
Ill try my wifes phone thats post ota only when she gets home.
I did notice that since I put CM6.1 on my phone, the in call features work WAY better.

I have noticed this but only when using the speakerphone button...when I have tried to bring it to my cheek without getting out of speaker, i have put calls on hold and also hung up on them......
I got to see if coming from speaker to headset also has issues...

Just got off the phone with customer service. They are going to warranty it. They didn't say it was a known problem, but I was told by one rep that its not the first time they have seen this problem.
Sent from my T-Mobile G2 using XDA App

digital_exhaust said:
Just got off the phone with customer service. They are going to warranty it. They didn't say it was a known problem, but I was told by one rep that its not the first time they have seen this problem.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Sounds good. Hopefully the replacement doesn't have any problems. But it seems like they are starting to get their stuff together and sending out some good phones recently.
P.S.
Have you tried a factory reset to fix the prob?

Bishybob said:
Have you tried a factory reset to fix the prob?
Click to expand...
Click to collapse
I did. No go.
And on that note, and this might make me sound like an idiot, but since the reset, no matter what I do or how hard I try, Angry Birds refuses to install.
Weird, huh?

EI22 issues during calls

Unfortunately I cannot search since there isn't a search forum button at the moment, so I am just going to throw out this topic/question and see if i can get some insight.
I am running the deodexed EI22 with nubernal (no rom's just rooted) and every time i am on a call the screen will turn back on randomly. And when it does of course my face is mashing buttons and usually hangs up or puts the person on hold or something. My only way around it is if i notice it light up to pull it away from my face wait a second and then pull it back in. Then it will turn off but it will light back up eventually. This is EXTREMELY annoying and problematic.
Is anyone else experiencing this issue?

goblue30093 said:
Unfortunately I cannot search since there isn't a search forum button at the moment, so I am just going to throw out this topic/question and see if i can get some insight.
I am running the deodexed EI22 with nubernal (no rom's just rooted) and every time i am on a call the screen will turn back on randomly. And when it does of course my face is mashing buttons and usually hangs up or puts the person on hold or something. My only way around it is if i notice it light up to pull it away from my face wait a second and then pull it back in. Then it will turn off but it will light back up eventually. This is EXTREMELY annoying and problematic.
Is anyone else experiencing this issue?
Click to expand...
Click to collapse
Are you sure the proximity sensor isn't being accidently uncovered?

positive, its up against my ear. I'm not using it any different than i have for the year that i've owned it.

goblue30093 said:
positive, its up against my ear. I'm not using it any different than i have for the year that i've owned it.
Click to expand...
Click to collapse
no clue then. I always talk on speaker so after the call is connected, I hit the power button to turn off the screen. Never had it come back on.

I noticed my screen come on a few times as well when I'm on a call. Then I move the phone a little and it goes back off. Almost seems like the proximity sensor's sensitivity has radically changed with GB. Never did this on Froyo.

well i'm glad i'm not the only one lol. However this has got to be fixed. I need to take my phone back to best buy anyways cause my bezel has cracked severely. Hopefully they give me a new phone preloaded with Gingerbread and maybe it won't do it on the new one. We shall see. IF BB screws me on the new phone i will be reflashing mine to stock and see how that goes before moving on to the latest Urban Rom.

Problems ending calls

Hey everyone. I'm having a problem with my phone where when in a call, the screen will stay black, and I can't turn the screen back on to end the call, use the number pad, or anything. Once the screen goes black, that's it. I have to do a battery pull to get the phone to function properly again. This has been going on since I got the device a few weeks ago. I don't think it has anything to do with the ROMs I'm flashing, I have had this problem with stock, cm7, nightly's, RCMix 3D, and absolution. This is a real pain in the ass, and I hope you guys can shed some light on this issue. Thanks in advance.

Not to state the obvious, but if you have this kind of problem with multiple ROM's the problem is probably hardware.
Though I can't for the life of me imagine what hardware that would be. Whatever circuit physically powers on the screen obviously works enough to get it to start on boot.
You could try disabling the automatic screen off feature during calls. Just bypass the problem by keeping the phone on. It's not a great solution because a 60 minute phone call will really sap your battery. But it might be a good temp solution until a real fix is found.
Did you try a full factory reset, rather than just a flash to a stock ROM? There might be some glitch in the software that a ROM flash doesn't cover.

Skipjacks said:
Not to state the obvious, but if you have this kind of problem with multiple ROM's the problem is probably hardware.
Though I can't for the life of me imagine what hardware that would be. Whatever circuit physically powers on the screen obviously works enough to get it to start on boot.
You could try disabling the automatic screen off feature during calls. Just bypass the problem by keeping the phone on. It's not a great solution because a 60 minute phone call will really sap your battery. But it might be a good temp solution until a real fix is found.
Did you try a full factory reset, rather than just a flash to a stock ROM? There might be some glitch in the software that a ROM flash doesn't cover.
Click to expand...
Click to collapse
I had this problem with full stock and s-on. The problem continued even after downgrading the radio and rooting with s-off and multiple ROM flashes. I wouldn't know what hardware it would be either. I don't really talk much, so your suggestion will work until I figure something else out. Thanks man.
Edit: I just tried keeping the screen on, no dice. As soon as I dial out, the screen turns off completely and none of the buttons work. I also tried the trackball hangup option, but no good.
Sent from my HTC Glacier using xda premium

i think the problem is the proximity sensor. it could be misplaced and covered by the front glass.
download sensor test on market to find out.

mniroy said:
i think the problem is the proximity sensor. it could be misplaced and covered by the front glass.
download sensor test on market to find out.
Click to expand...
Click to collapse
Downloaded and ran the app. All the sensors appear to be working, except the proximity sensor. It just reads 0.
Edit: I ran the test again, and when I first start it, the "0:" line for the proximity reads 9. As soon as I move my hand close to the screen, it will drop to 0 and stay there.
Sent from my HTC Glacier using xda premium

Well that certainly seems to be the issue.
I can't remember how to do it, but I'm almost certain there's a setting to disable to proximity sensor during calls. Sorry I've never actually used that setting so I have no recollection of where it is.
For all I know it might be the "screen on during calls" setting I refereed to originally.
I knew it was hardware though!
Also, I saw this app. I don't think it was designed to do what you want, but I think it ultimate does it. It was made so that you could answer the phone with a swipe. But in order to make sure the screen is on to be swiped, it disables the proximity sensor.
https://market.android.com/details?...wsMSwyLDEsImNvbS5pdHNtZTR1Y3ouc2NyZWVub2ZmIl0.

Skipjacks said:
I can't remember how to do it, but I'm almost certain there's a setting to disable to proximity sensor during calls. Sorry I've never actually used that setting so I have no recollection of where it is.
Click to expand...
Click to collapse
if youre a fan of miui, there is an option to disable in settings. def sounds like the proximity sensor is the culprit. have a screen protector or case thats interfering with it?

Dan_Brutal said:
Downloaded and ran the app. All the sensors appear to be working, except the proximity sensor. It just reads 0.
Edit: I ran the test again, and when I first start it, the "0:" line for the proximity reads 9. As soon as I move my hand close to the screen, it will drop to 0 and stay there.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
so your proximity messed up. the solution is easy, just remap your end call to hard button.
like this for example:
Code:
key 116 ENDCALL WAKE_DROPPED

mniroy said:
so your proximity messed up. the solution is easy, just remap your end call to hard button.
like this for example:
Code:
key 116 ENDCALL WAKE_DROPPED
Click to expand...
Click to collapse
If the screen is not coming back on even after the other person has hung up, this will not work. Its worth giving it a shot tho
Sent from my HTC Glacier using Tapatalk

mrmako777 said:
If the screen is not coming back on even after the other person has hung up, this will not work. Its worth giving it a shot tho
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
of course, but if that so, the problem must not be the proximity sensor isnt it.

mniroy said:
of course, but if that so, the problem must not be the proximity sensor isnt it.
Click to expand...
Click to collapse
um, yeah, it still could be the sensor

I had this issue without a screen protector or case. Do you think if I flash back to stock with s-on, HTC would warranty it?
Sent from my HTC myTouch 4G using xda premium

Dan_Brutal said:
I had this issue without a screen protector or case. Do you think if I flash back to stock with s-on, HTC would warranty it?
Sent from my HTC myTouch 4G using xda premium
Click to expand...
Click to collapse
i would think so if youre still under the warranty period, which is i think a year.