Related
Hey guys,
I am going crazy here, searching forums did not help me at all.
The lower section of the screen keeps flicking, and not always, what do i mean by flicking, its like the screen at the lower section keeps doing like a strange low refresh rate, and has an old imprint of some old menus. Happens especially when there is the color of gray.
Made a screenshot of the phone, no problems, there, so its not a software rendering problem, might be a drivers problem though, or a defec tin the screen itself.
Frequency is high but not always, and am unable to determine when does that happen exactly. going crazy here, is this a defect? or all touch pro's have this?
Exact explanation summary:
1CM from the bottom of the LCD sometimes flickers as if that 1CM is having an extremely low refresh rate. Mostly happens when there is light gray, but not necessarily, and a soft reset for the phone does not remove it. It happens on random!
Hey,
Yeah it happens to me too! You don't need to do a soft reset, it actually fades away if you watch it closely! I don't know what it is either, and yes it is random as you have stated! I initially thought it was an application I installed as it only started happening after that, so I did a full hard reset and its still happening! Not sure what or how, but hoping next firmware version stops it!
Cheers,
mpls-te
As it happens, that's exactly why I've logged on here today! Any ideas whta the cause might be?
OK, good to see that others have this, so am not alone here, experts here, any ideas? other touch pro users, can you please leave your statements?
I hope its a driver issue.
But from what i noticed, its like, the screen is OFF, as in blank and no back light, but somehow, the application working on the screen before you turned off the device is somehow printing something on the LCD, something that we don't see, and when we actually start the phone and its back light, that OFF LINE imprint pops on screen. Something like that.
Its completely illogical, but dunno, can't find any sense here and am going crazy
Same thing happened to me and a few others as well.
See my thread here.
What rom is everyone using?
I've noticed a similar issue with mine, except rather than something software it seems like it's the backlight for the bottom 1cm of the screen flickering slightly. I don't see any weird pixels or inappropriate screen information, just a dimming/high speed flickering of the backlight in that same regionas yours. It comes and goes. Sometimes weeks without it, then maybe 3 times in a day for a minute or two at a time. Everything else works fine and whatever screen I go to displays fine.
I'm assuming it's a hardware problem with the LED(s) that light up the bottom portion of the screen, and I'm going to use it as an excuse to get a warranty replacement somewhere near the end of the warranty when the phone's getting a little old and worn.
maxh said:
I've noticed a similar issue with mine, except rather than something software it seems like it's the backlight for the bottom 1cm of the screen flickering slightly. I don't see any weird pixels or inappropriate screen information, just a dimming/high speed flickering of the backlight in that same regionas yours. It comes and goes. Sometimes weeks without it, then maybe 3 times in a day for a minute or two at a time. Everything else works fine and whatever screen I go to displays fine.
I'm assuming it's a hardware problem with the LED(s) that light up the bottom portion of the screen, and I'm going to use it as an excuse to get a warranty replacement somewhere near the end of the warranty when the phone's getting a little old and worn.
Click to expand...
Click to collapse
Lool, evil, lets just hope that this problem DOES occur when you go to their shop for your replacement
Good idea though, might do the same thing except that i have to travel abroad to where i got the phone from to actually get the warranty working. Don't forget to re-enable stock SPL and stock ROM
It happens frequently enough I'll be able to get it on video just in case they need proof, but typically they just exchange by mail.
I just posted in another thread about this issue. I have run into the same thing a few times. The bottom portion of the screen flickers, and when i do things that have a dark gray or black screen I can see a ghost image of the left and right soft keys from my TFL3D home screen. It seems to be most noticeable when the screen brightness is set to max. To get it to go away I usually do a few soft resets, and then, if needed, i will turn off the phone and take the battery out for a while. I have never tried waiting it out to see if it will just go away on its own.
proj3ktpat said:
I just posted in another thread about this issue. I have run into the same thing a few times. The bottom portion of the screen flickers, and when i do things that have a dark gray or black screen I can see a ghost image of the left and right soft keys from my TFL3D home screen. It seems to be most noticeable when the screen brightness is set to max. To get it to go away I usually do a few soft resets, and then, if needed, i will turn off the phone and take the battery out for a while. I have never tried waiting it out to see if it will just go away on its own.
Click to expand...
Click to collapse
I see that everyone posting in this thread,that has their signature filled in, is using the Energy ROM. I find that very interesting.
i am having the same problems, sometimes touchflo3d will flicker at the bottom, near the edges. I also get text that can be read through other screens. Like on pocketshield i can see the left and right softkey words still at the bottom. its so odd !
P.S im on energyrom
I'm on NATF v2.2, not an energy rom. But then again, mine looks more like a hardware issue, as I've never seen any ghost images of text or softkeys, just flickering.
can somebody post screens?
maybe the same problem here...
hardreset, other roms > problem still there:-(
Same problem here and I am using stock rom!
here are 3 screens of my xda diamond pro, using latest official o2 rom and newest romeOS eng
hope you can see this prob?! same like yours?
climber1872000 said:
I see that everyone posting in this thread,that has their signature filled in, is using the Energy ROM. I find that very interesting.
Click to expand...
Click to collapse
Well, i doubt EnergyROM has anything to do with that problem, since my Stock ROMz had same problem, never got fixed with any updates HTC used to release. MAYBE some Cooked ROMs out there have this solved, if any, please let us know And my problem is nothing close to screenshots above :S
mj084 said:
here are 3 screens of my xda diamond pro, using latest official o2 rom and newest romeOS eng
...
hope you can see this prob?! same like yours?
Click to expand...
Click to collapse
Dude, those photos are awful, after seeing them am happy with my phone flickering, its nothing close to this.
You see, in your photos, all three of em, you some kind of shadow effect, where text of a button for example has that same text beneath it 3x6mm, that is not my case at all.
My case is as follows, IF i am on the home screen for example all looks ok, except that the bottom 1CM of the screen is flickering. If i go to another window, either a total black one or any other screen, i would still see a ghost of the old home screen, for example, and only at the bottom 1CM.
Will post photos once i get my cam back. Cheers
similar issue
my issue is kinda similar, instead of getting the bottom 1cm or so discoloration or stuck pixels, I get streaks of red or blue on my screen. I have had this happen on each version of NATF I have tried, but don't remember it happening on the stock version (which I am tempted to try again to see if that's the issue).
Could this be a driver issue?
mind is even worse than all you guys, the touch screnn dose not response, and i have the energy rom on it, before it goes wrong. it just suddenly dose not response, than i send it to HTC, they ask for 425.00 for fix.... I will just send this to Asia and get some one to fix it.
But I hope before i send it out, some one can help me here.... anyway can fix it easy!!!!
Hi all, i have the same problem, here's another topic about it
http://forum.xda-developers.com/showthread.php?t=447891&page=2
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.
I have read this forum and many other internet sites until mys eyes cross!
I have Sprint HTC Touch Pro2 running winmo 6.5. duelboot android.
I have flashed many times and the problem isnt fixing itself.
Its like when my backlight goes to sleep I cant wake it up. I can still here the
phone ring and answer it.. just cant see anything after it has gone to sleep.
In Android i dont have this problem..
Anyone know where the registry is to do some editing??
Your help would be so APPRECIATED!!
Thanks in Advance.. Tammy
Tp2 Zombie
I Have the same issue. I Recently tried to flash back to 6.5, and somehow it all went wrong and i got the white screen of death. i could get to the boot loader(tri color) screen but it would just go right back to that White back ground with Green letters 'htc'. Now I finally found the post that helped getting to that tricolor screen then loading rom. IT WORKED! then i tried the sleep/ pwr button and sure enough it STILL WON'T WAKE!!!! Seems like the only answer is to break down and get the droidX. but i need windows for a 3rd party program i use....so i might just stick to the lil slide fone i have as a back up...
I just leave the light on 30% if Im expecting any txts or calls, when Im not I just turn the light out I can still hear incoming calls and if I hear a couple txt I pull the battery and stick it back in so that I can see the screen again.. its all I can do for now.
Im amazed with so many smart folks here I havent had anyone offer any fix's yet??
I have been hoping for easy registry fix.
Good Luck and please let me know if you get any help with yours??
yes, its becoming a problem. pulling out the battery to get the screen is more damage than good
I'm not sure if it's lag or what, but my phone screen won't come on. I think it's a ribbon that was disconnected or something though. For about a few hours if I were to press power to see the lock screen, all I saw where a bunch of rainbow static. Then I powered my phone on and off because nothing would work and now it's jut black! Does anyone know what's wrong? I can't boot into clockwork so I don't think it's a rom problem. Does anyone know the problem or have any idea to fix? Anyone I should ask specifically?
maybe water? even having my phone in the bathroom while i take a shower cause me that
It's not water, I never bring my phone close to place with water :/
can you boot into the screen where there are 3 droids with the skateboards? (i not sure whats the name)
I think I can boot and my phone still works, because it still rings when someone calls and it still vibrates when someone text it, but I just can't pick up or reply (because the screen won't come on). I should be able to boot into that thing, but I can't anything :/
well bro sorry i cant help you :/ maybe it could be the screen,the ribons or somethings loose. did it fell?
aznangel1408 said:
I think I can boot and my phone still works, because it still rings when someone calls and it still vibrates when someone text it, but I just can't pick up or reply (because the screen won't come on). I should be able to boot into that thing, but I can't anything :/
Click to expand...
Click to collapse
Seems like either broken ribbon that connects the screen to the "motherboard', or dead screen itself. That's exactly how 1 of my phones died (it was too complicated to disassemble and fix it myself)
But once I had similar problem with my TP2, the screen first become unresponsive to any touch, and then it went just black after restart (and every next restart). However all keys did work.
Hard reset somewhat helped, the screen actually came back, but it was still stuck on setting up Windows Mobile (if you know WinMo: the part where you calibrate touchscreen), apparently "touch" part of the screen didn't work.
I thought it is ribbon or screen assembly, but since all the keys worked I flashed another ROM and what do you know: all problems went away. It worked fine for as long as I had it. I never figured out what caused it/was the problem.
koete said:
well bro sorry i cant help you :/ maybe it could be the screen,the ribons or somethings loose. did it fell?
Click to expand...
Click to collapse
MT4GS said:
Seems like either broken ribbon that connects the screen to the "motherboard', or dead screen itself. That's exactly how 1 of my phones died (it was too complicated to disassemble and fix it myself)
Click to expand...
Click to collapse
Yea I think that's the problem here. I think I'm just going to borrow a friends mt4gs to use and navigate recovery and do a back up and just buy a new one and restore. Thanks for all the help guys
Hi. I have been running pacman v22.0.1 for quite some time now and I could quite easily make and receive calls with no problems, the rom was fast and battery life was great. But quite recently, I received a call and answered it spoke but when it came to ending it, I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that. But I switched to another rom then wiped everything and flashed pacman again but still had the same problem. Is there anybody who is facing the same problem or has a solution? I have tried on 4 different 4.2 roms now and have experienced the same problem with all.
Just uploaded a very, very long log cat if you are a dev or have knowledge of logs, please read!
Problem solved, it was my screen protector which was covering my proximity sensor and jelly beans behaviour with the proximity sensor caused it to stay off. When buying a screen protector always make sure it has a hole or gap of some sort for the proximity sensor. The bug in the log cat was something else which was fixed by a build.prop tweak.
My radio is 3831.19.00.110
ifti786 said:
I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that.
Click to expand...
Click to collapse
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
paulie-uk said:
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
Click to expand...
Click to collapse
That could just be it: the reason for my problem is my impatience! Still need to check though...
No, that didn't fix it. I think it might have something to do with my proximity sensor because on vipersaga, it used to turn the screen on when I moved my phone from my ear but now it doesn't so I have to press the power button.
Also have the same problem on jelly bean fire
Sent from my HTC Desire S
Please help because I really want Jelly Bean 4.2 but at the current moment, it looks like my desire s is incapable of running it!
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
sanilii said:
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
Click to expand...
Click to collapse
Wipe all partitions except sd card AMD done this on pacman v22.0.1, JellyFireBean, JellyTime, flinny cm10.1 and AOKP redefined. I have just flashed a new radio and will check if that fixed it
Flashing a new radio did not fix the problem please somebody help!
ifti786 said:
Flashing a new radio did not fix the problem please somebody help!
Click to expand...
Click to collapse
I've got the same problem. My screen won't turn on after I move the phone away from my head after a call, altho I can turn it on with the powerbutton somehow. Happens on all JB ROMs for me aswell.
I tried Proximity Sensor Finder app from play store and it says 9cm when theres nothing infront of the sensor, then goes to 0cm when there is something, but doesn't go back to 9cm when the sensor is free again. It only goes back to 0cm when I restart the app.
I don't know whats the problem, but I think its software related.
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
NVardan said:
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
Click to expand...
Click to collapse
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
ifti786 said:
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
Click to expand...
Click to collapse
Maybe you should upload the logcat in the PACman thread.
Ok will do that now
Sent from my HTC Desire S
NVardan said:
Maybe you should upload the logcat in the PACman thread.
Click to expand...
Click to collapse
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
ifti786 said:
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
Click to expand...
Click to collapse
Unfortunately I am NOT a developer so I can't help you.
You must copy-paste your logcat in a .txt file and upload it in the PACman thread.
Sent from my Desire S using Tapatalk 2
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Right, I've just had a look through the logcat and i've found a bug. I'm going to try some build.prop tweaks and see what the results are. I will let you know but please bear in mind that it might take some time as I am having some very important exams coming up so I'm going to be revising in most of my free time.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Do you have a screen protector on your phone by any chance?