Database Info

Screen going black

I've tried various different ROM images (including the excellent Dr.Gonzo), and I have this problem with all of them.
When I'm using the phone either with the keyboard in or out, the screen just switches off randomly. If I wait a few seconds (possibly the backlight timer length), then it comes back. Mostly... Othertimes I have to wait a lot longer, but it does always come back.
A reboot sometimes fixes it, but not always - does anything survive a reboot or battery removal?
Anybody else seen anything like this? I have seen a lot of threads about the screen staying on, but not off.
Of course, it could be a hardware fault, but because it's intermittent, it's hard to prove.
Mike

same problem

If you shake the phone can you re-produce this problem? I've never not heard of this being affected by software - you might also want to ensure you're not overclocking it.
Nothing is removed when you do a battery removal or reboot, ensure your connections are all tight and make sure the SIM pins are all making contact and the SIM door closes, apart from that it sounds like a possible bad LCD ribbon.

Shaking it doesn't reproduce the problem.
Once the phone has started doing this, it happens everytime you press a key.
Seems more like a memory leak to me since it always seems to happen after a while of web browsing/email use.

So actually, it looks like it might be a hardware fault.
I think it happens when the device gets warm. After a few minutes with the screen on, keyboard lit up, wifi on, the phone gets pretty warm and that's when the screen seems to go black. Leave to cool and all returns to normal.
Mike

Same issue here, but the screen does not acually go black/blank it just seems that the screen backlight does not turn back on from a standby like state, the phone itself functions but just not able to see whats going on on the screen.
(keyboard lights work fine and come on when expected)
Not sure about the heat theory as it happens (to me) most often right after a call, anything over 30-50 seconds and the backlight problem occurs, when it decides to work again is a matter of luck.
As said before because it's intermittent, it's very hard to prove.
Has anyone who has had this issue, fixed it with a hard reset ?
Very strange ... but also getting very annoying now!

i got the same thing. took it back to warranty and they said nothing's wrong with the phone but i still get this.

I experience the same problems.. it happens pretty random, but every time when you hit a key. I have set all timers to never but the problem is still there.
Running Gonzo 1.1 at the moment, upgraded from guava.. but that didn't solve the problem.
It is getting so annoying now that I am about to throw the s710 in the dustbin

I have had the same problem!
I have turn it back to my provider and no problem now.

i have the same problem with my VOX
apparently, i can still receive phone calls, and do whatever i want with the phone,
but the screen just stays black, its like if you have unplugged your monitor
since i dont have a htc center in my town or anywhere else nearby.
does anyone know a way on how to open the phone, change what need to be changed and correct the problem? im all up for testing if that would resolve this annoying problem :s
cheers everyone

there is a dismantling manual somewhere in this forum. search.
i don't think taking it apart would help you because this is not a physical fault that you can locate.
and i learned that mcel is the retail seller of vox in mozambique. they should be able to help you with service. else just send a mail to htc support and they will guide you.

yes, mcel are the retail sellers, but i tried to go there, and there are no specialists on htc's there,
the thing is, i didnt bought my htc from them, so i can't go there and change for another one
but tks anyway

no problem
but do try to contact htc support by email. they might suggest a way.

I'm having exactly the same weird problem and I think I found some pattern when it occurs. Well, the thing is that in the bright day or in a room with lots of light it works just fine. In the darker conditions… well… not so fine. It seems to me that this screen blackout happens whenever the keyboard light is on and screen changes to full brightness (in the dark, because of the light sensor). In the daylight, keyboard light doesn't turn itself on, so s710 works. I don't know much but this definitely isn't some bad contact problem. Maybe some battery problem, but I doubt it since I can receive phone call in this condition. This started to happen after I flashed this Windows Mobile 6.1 ROM from HTC (I have original S710). Flashing Dr.Gonzo's later on didn't bring any luck either. I believe that some power control SW is the main culprit. I've read that many people mention some Tornado Power Control app. Does anybody know can this application be permanently disabled or removed?

are you trying to say that by desabling the light sensor, the problem might go away?
i would also like to know if it possible to have the baklight on the lowest possible brightness forever, because it seems, on a low brightness the problem might go away

petlof32 said:
I'm having exactly the same weird problem and I think I found some pattern when it occurs. Well, the thing is that in the bright day or in a room with lots of light it works just fine. In the darker conditions… well… not so fine. It seems to me that this screen blackout happens whenever the keyboard light is on and screen changes to full brightness (in the dark, because of the light sensor). In the daylight, keyboard light doesn't turn itself on, so s710 works. I don't know much but this definitely isn't some bad contact problem. Maybe some battery problem, but I doubt it since I can receive phone call in this condition. This started to happen after I flashed this Windows Mobile 6.1 ROM from HTC (I have original S710). Flashing Dr.Gonzo's later on didn't bring any luck either. I believe that some power control SW is the main culprit. I've read that many people mention some Tornado Power Control app. Does anybody know can this application be permanently disabled or removed?
Click to expand...
Click to collapse
I also have this problem with the lightsensor turned off. And also at (as it seems) random moments.

well, even with the light sensor turned off, the problem persisted.
i got my phone to a repair shop of htc's, and they figured out the problem
my phone is now 100% thankfully, the repair man told that the problem was because of bad or malfunctioned circuits, he exchanged them with new ones, and the problem went away,
dont know wich circuits exactly, and he didnt want to tell me, but i suggest anyone having the same problem to try and do the same
probably its a hardware malfunction with these VOX,
its possible since so many times before i've heard about malfunctioned pieces coming out in large quantities for sale.
anyways, cheers everyone, and good luck Portugal in EURO!

I have the same problem. I just noticed that it usually happens when the phone is warm, so if you need to do something on my phone just... take some ice from fridge and put it on back of your mobile. I cant see any more solutions.
Please someone help us!

Update. Problem Solved
Just thought I'd update this thread I started.
I sent the phone back to my dealer (Grapevine in Poole,UK).
A week later, I got a brand new one back from the HTC repair centre.
So far, so good. Looks like the problem's solved.
Mike

Sam problem here,
i called with HTC and they sent them to there repair centre.

About the screen (bottom part)

Okay so I've had the HTC Fuze for 3-4 days now and 1 thing that i noticed is in the screen, by the bottom (where the touchflo is) the screen is like "blinking".
It's hard to explain, but if you get closer to the screen you see like its moving and shaking but when you look at any other spot its not.
Is this normal or my device could have a problem?
Oh and sometimes when i use the keyboard and the screen rotates, the "right side" which is the bottom (keeps blinking) sometimes has the letters of the menu before i rotated the phone, so it has like letters with opacity there as if OVER the screen.
Any of you have this problem? Or is it just me?
What can I do? My device is still in warranty but its a really small problem, it just bothers me the screen like that.
Thank you.
PS. Ill post a video if you want to see more clearly.

not normal

I agree this is not normal. Reflash your ROM.

xlinkx said:
I agree this is not normal. Reflash your ROM.
Click to expand...
Click to collapse
I've never done this before. But i wanted to take all the A&T stuff of my phone and make it faster. What ROM would you recommend me?

There's other threads about this on these boards. It's a hardware issue with the Fuze, and yes, it is normal. I've gone through 4 Fuze's, all of them were sent back on warranty, because of this exact problem. I just seen a thread not too long ago about it and someone mentioned that it was a hardware problem but I really don't remember his/her explanation of it.

PryorDaniel said:
There's other threads about this on these boards. It's a hardware issue with the Fuze, and yes, it is normal. I've gone through 4 Fuze's, all of them were sent back on warranty, because of this exact problem. I just seen a thread not too long ago about it and someone mentioned that it was a hardware problem but I really don't remember his/her explanation of it.
Click to expand...
Click to collapse
Oh so should I send mines back or just keep it?
It doesn't bother me at all, i mean, i could live with it, but sometimes i think it would be better if it didnt do that.
It just happens when my device is hot. I mean, when you use WIFI the phone gets warmer and thats when the screen starts doing that, when i turn it off and let it rest it works fine again, and sometimes when i put it in standby mode and then back to normal it comes with the blinking thing and sometimes not.

Like I said, I've gone through 4 and still have the problem. My advice, either switch the TF3D look so it's not as noticable in portrait or just switch a totally new ROM with a new TF3D look. It's still going to happen but you'll notice it less. Even on this new Fuze it's still happening. I'm using EnergyROM Mercury right now, and while I still have the problem, it's nowhere near as obvious as before.
Another thing I've noticed that seems to help a bit from time to time is to turn off the screen and plug the charger in. Weird, but it fixes it sometimes. As you also noticed, it only happens when the device is hot. A prime time for it to happen is when you hang up a call.

PryorDaniel said:
Like I said, I've gone through 4 and still have the problem. My advice, either switch the TF3D look so it's not as noticable in portrait or just switch a totally new ROM with a new TF3D look. It's still going to happen but you'll notice it less. Even on this new Fuze it's still happening. I'm using EnergyROM Mercury right now, and while I still have the problem, it's nowhere near as obvious as before.
Another thing I've noticed that seems to help a bit from time to time is to turn off the screen and plug the charger in. Weird, but it fixes it sometimes. As you also noticed, it only happens when the device is hot. A prime time for it to happen is when you hang up a call.
Click to expand...
Click to collapse
Thanks a lot for this information!!
Ill just keep my device and live with it.
I'm flashing to a new room soon, ill see which one i'd like.
Thanks again.

Problem with the proximity sensor, please help

Hi all, I have a weird problem with the proximity sensor in my HTC Titan. I got a new Titan about a week ago, to which I immediately installed HSPL and Dynamics rom. After I did all the tweaks and installs I like, I noticed that every time I dial a phone call the screen goes off and stays that way until the number I called answers. If the number does not pick up, only thing I can do is remove the battery basically to hang the call up. I noticed that removing the back cover slightly affects the issue and its easier to get the screen back on (by pressing the power button), but still removing it does not solve the problem. With a handsfree I can actually stop the call as it has an accessible end call button.
I tried flashing another custom rom and also a stock rom, both had the same issue. So, I took the device for warranty repair. I got it back today from HTC, with a note saying that software has been updated and problem has been fixed. I tried the device and surely it was working. Well I can’t live without an fully unlocked device and against my better judgment flashed a custom rom again… And surprise surprice the problem appeared back.
Im thinking here that could I adjust the proximity sensor from the registry, if its somehow too sensitive or something. Strange part naturally is that other people with same rom are not experiencing this behavior, so it is device specific problem. Also I don’t think I can take the device back again and say yeah I was flashing some custom roms on it and lost whatever you did with it.
There a Proximity folder at HKLM and I tried changing some values there but no affect at all. It probably would be better to have someone who understands about the values little try to take a look.
Thanks a lot!

It's a hardware problem. I got the same issue after 2 months of use. I sent to repair but they wanted to charge me to do that, so I haven't fixed it but I still can get the screen back by pressing and rubbing my finger on top of the sensor.

But when I got it back from repair today it was working. I made few phone calls and it was working totally like normal.

you are not alone
Loco5150 said:
But when I got it back from repair today it was working. I made few phone calls and it was working totally like normal.
Click to expand...
Click to collapse
I can tell you that you are not the only one with this problem, it happened the same to me. I'm still unsure if the problem is hardware or software, but I think it's software because it happened just after I install Dynamics_2.0_Titan. I really wish that someone will bring a good solution for it.

Nexus 5 water damage - screen's all black - motherboard related?

Hello guys,**
Well few days ago I accidentally dropped my Nexus 5 in a glass of water for just 1 sec. So I immediately switched it off and wait a bit to let dry then restarted it, and all seemed to work fine. But just some days later and up to now the phone boots up all fine as usual to the lock screen, and from there I can pull down the notification bar (and navigate through it, activate/deactivate wifi, etc..) but when I unlock it to get to the home screen it becomes all back and nothing appears on the screen even though the phone is still on.*
It's really confusing and weird. When I call the phone it rings (so no signal or sound problem) but I can't still access the screen to take the call as it's all back and unresponsive.
Following some suggestions I disassembled the phone and cleaned it dry but same results again! So now I think the problem is somehow related to the motherboard, coz as you might notice on some of the pictures attached, it seems that some plastic parts have melt down to cover other smaller parts. Anyway guys,*I'm just wondering if some of you guys had experienced something like that and if you were luckier*to find a solution or any directives that could help. Or you even think that's a motherboard problem like, do you know any ways to fix that o buy a new one somewhere??
PLEASE!!

Sorry apparently, I can't publish links until I get like 10 posts or plus..
But anyway guys, I'd really appreciate your help.

Why did you power it on and short circuit it on purpose for??

Bump

@SekouCheikh

Maybe it's a coincidence that you dropped it in water and this happened a few days later. Once in a blue moon mine does something similar to this (although not usually as start up only after lots of use), but I think it's related to an app or xposed. I only notice it after installing a bunch of crap again. Maybe try a factory reset (do it though the computer) just to see if it is somehow not hardware related? That's what I would try first.

Help please

Ttt

Wait... Are you seriously posting from 2 different accounts??
<...>
First, simply try to factory reset or flash a new rom. There is not enough evidence to be sure it's a hardware problem, it could just as well be a coincidence that it started happening just now.

-SmOgER said:
Wait... Are you seriously posting from 2 different accounts??
<...>
First, simply try to factory reset or flash a new rom. There is not enough evidence to be sure it's a hardware problem, it could just as well be a coincidence that it started happening just now.
Click to expand...
Click to collapse
No, I just like to help

Help Op solve the problem please

Ttt

SOD (sleep of death)

I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?

60puc said:
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
Click to expand...
Click to collapse
This has happened to me before.What I simply did was replace the display.

Mr.Ak said:
This has happened to me before.What I simply did was replace the display.
Click to expand...
Click to collapse
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.

60puc said:
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
Click to expand...
Click to collapse
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.

Mr.Ak said:
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Click to expand...
Click to collapse
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.

60puc said:
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
Click to expand...
Click to collapse
As I already said,the same issue happened to me after I changed my display.I asked for replacement and replaced that damaged display,boom! I don't know what's so hard in it for you to understand.

Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.

60puc said:
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
Click to expand...
Click to collapse
Aliexpress?

Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.

60puc said:
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
Click to expand...
Click to collapse
Get ready with a lot of proofs tho'!

to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?

Gab_echelon said:
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Click to expand...
Click to collapse
See previous page,I've already explained what is the cause of the issue.

I just finished replacing my screen, been waiting for my broken antenna cable and volume button flex to arrive. Everything works except the damn SOD i never had with my old screen. Tried turning off the proximity sensor check and still a no go. The screen turns on fine initially and trying to wake it instantly works all the time, but if I leave it off for any longer than 5 sec probably it won't respond to anything - power button, volume button, double tap and plugging in the usb cable connected to a power source.
Does this sound more like a governor issue? The rom installed is lineageOS (just updated to 10-30 release). Looking up my purchase log to open a dispute...
tested it again, repeated lock/unlocks puts it into the SOD state, doesn't even take 2 sec to do it...
oh wow, it does this even in the twrp recovery. I have wiped cache and dalvik cache just for the hell of it but doubt that was the real cause...

Gab_echelon said:
works everything but not touch
Click to expand...
Click to collapse
we've got a reverse situation. touch, buttons, sounds, modem works, but not screen (if you lock/unlock it 10-20 times it can raise again without reboot.
Buratei said:
it does this even in the twrp recovery.
Click to expand...
Click to collapse
i've got the first SOD in twrp mode. it doesn't matter, but at first - no troubles were with that. and now it works so so at home. and if i use it outdoor it becomes very often, but at home it seems that it works ok, just only seems, because if i want - i can do some manipulations (use camera, lock/unlock it etc) and the SOD appears again. but custom os executes SOD more frequently. i think it can be real overvoltage, like people says.
there are many posts here and everyone advices not effective solutions (flash stock, modem, fw ...) at first it helped me, but now i know there is no way, i can just try but ...
long time ago i owned an old tablet iconbit matrix - it has just the similar issue. it boots, but if you go to a sleep mode - it didn't wake up every time. it lights works ok inside, but no image. i had two displays and if i used one in a custom rom it worked ok, but not another one. stock rom works ok with every display. the solution was a display driver, like at windows OS.
cause of developers bugs, it was a little different (not stock-based) and some revisions of display works ok, others aren't.
so, i think it can be fixed, but the solution for me - change a display like the first reply says. Ali seller read this topic and posted me this in a few days after i started this topic:
Your dispute has been processed and the money will back to you in 7~10 working days.
so could you give us a positive feedback, please?
Best regards.
so, i'll order another one, no trouble, i hope this will help me to enjoy my oneplus.

60puc said:
so could you give us a positive feedback, please?
Best regards.
Click to expand...
Click to collapse
They always ask for positive feedback in exchange for refund/replacement.Bastards,aren't they? @evronetwork
For the sake of other people that'll read your feedback and make their decisions upon it,don't do it! Just complain this bribery to aliexpress staff ffs!

well I wish I bought from aliepxress... I bought mine from ebay to pinch some pennies, and because I was waiting on other replacement parts (which were only needed due to damage occurred during a screen replacement op) to ge here I am way over the protection period. aw shiiiiit, I guess you live and learn
gotta tell you though, the screen is a bit wacky in other ways too. the capacitive buttons do light up but not completely (kinda dark in the corners) and the colors look a bit off. hopefully the seller would honor the refund/return request...
EDIT: whoa... kinda hard to believe, but I messed around with battery profile just for the hell of it and by some pure luck discovered that the "performance" profile (second one from the far right) works just fine and wakes the screen every time. The "balanced" profile and everything below that gives me an insta-death. go figure!
EDIT2: guess I spoke too soon. it sure as hell looked like fixed, but it came back after a while. maybe it is just more sporadic than I thought...

No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg

60puc said:
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
Click to expand...
Click to collapse
What happened to getting a new display?

I use this one, because it works ok, but only at home. As a home tablet. At the street it fails every time.
I can reboot it if it doesn't wake up. But it wakes up often, so i don't want to order new one now. I want to check my mainboard to be sure, that it is dispaly problem

a bit late, but thought I should update on the situation... all working fine after a (yet another) LCD replacement. Much better color balance to boot, points to QC problems at the supplier's end. If I ever have to do this again, I am definitely going to inspect the new LCD as soon as I receive I receive it.