AT&T Fuze screen issue - bottom menu-area of screen is flickering almost constantly
(Forgive me for the length of this post. I am just trying to provide as much information as possible! If anyone has encountered this same or similar issue, your help is greatly appreciated).
I need help! (professional and otherwise) ...with my AT&T Fuze (rebranded Touch Pro).
I am developing a game for Windows Mobile called Scrobble (http://forum.xda-developers.com/showthread.php?p=3206316&posted=1), and I left it running overnight.
My screen is set to turn off after 1 minute, and my device set to sleep after 5 minutes when plugged in to external power.
I had the Fuze plugged into wall outlet power to recharge. I left it lying, like I always do, face down on a black soft-leather CD case (so the glowing charging light doesn't bother me).
I left it alone for the 7.5 or so hours I was asleep. When I woke up in the morning and picked it up, the screen was on. It usually is not on, and I don't think I pressed the button to activate the screen.
When I looked at the screen, the Scrobble program was still running, and the bottom menu portion of the screen was flickering. Scrobble has two menu buttons at the bottom -- "Turn" and "Game" -- with a SIP keyboard icon in between them (same as nearly all WM apps).
In any other program, or the Today screen, the menu portion of the screen flickers (the brightness constantly and rapidly fluctuates consistently... like a fluorescent light that is on its last leg).
I did a full power off and power on, and during the "world phone" screen and the the AT&T 3G "power up" animation, the flicker was -not- there. But as soon the Windows Mobile loading/splash screen appeared, the flicker returned, in the exact same spot.
And I can see the ghost "Turn -- [SIP] -- Game" menu in the flicker. But I don't think it's burnt into the display, because it's not there during the first two loading/splash screens.
Currently I have the battery completely removed from the device and will leave it out for a while. If that doesn't work I will do a hard reset.
Any help would be greatly appreciated!! (This device is about 2 months old -- does HTC provide any support for it directly?).
Fixed
Phew! My screen flicker issue is no more.
I'm not sure if it's because I took the battery out and let it sit and think about what it had done for ~22 hours, or if it's because it just went away after a while (with the battery out for 22hrs). But either way, my Fuze is back to normal!
So if anyone leaves theirs on overnight and wakes up in the morning to a flickering ghost of a menu at the bottom, my suggestion is to fully reboot it, then take the battery out and leave it out overnight!
(It's kind of nice going a full day without any phone calls!!).
good for you.. you dont need a new phone giving you damage issues already... glad to hear that its gone
Thanks you for this post. I am going through the same thing with my ATT Fuze. This time it is Tomtom that I left running overnight with the screen turning on and off. I can add that the flicker and ghost is there the second the phone powers on. I have already hard reset and took the battery out for a few mins, but the flickering still there. Now I will take the battery out for several hours and hopefully it will be normal again.
I had a similar issue this week. I was using the phone all day, getting emails and phone calls, no problems. I get home and go to charge my phone and it doesn't appear to be charging. I flip on the screen and the whole screen is flickering on and off like it's not getting enough power. I charged the device over night, hard reset, pulled battery for 24 hours and still it won't go away. I just got the device thru amazon so I already reordered a replacement.
I've never left my screen on for hours at a time and I sometimes run into that same issue. The bottom of the screen flickers, and I can see a ghost image of my left and right soft keys when doing things that pull up a dark grey or black screen, like adjusting the volume. I usually try a few soft resets, and if that doesn't work I turn it off and take the battery out for a while. From what I am reading it seems to be correlated with extended periods of screen usage, but my screen has rarely been kept on for more than 30 minutes at a time.
Not to beat a dead horse or anything, but I was just having the same problem with my Fuze: the bottom quarter of the screen was flickering, but without the ghosting you spoke of. Out of curiosity, I went into my "Power Settings" menu, and for some reason the "auto adjust backlight" was unchecked, and the brightness settings were maxed out. I checked "auto adjust backlight" and the flickering stopped. Not sure why, but thought I'd add it to the thread.
kart_racer3 said:
Not to beat a dead horse or anything, but I was just having the same problem with my Fuze: the bottom quarter of the screen was flickering, but without the ghosting you spoke of. Out of curiosity, I went into my "Power Settings" menu, and for some reason the "auto adjust backlight" was unchecked, and the brightness settings were maxed out. I checked "auto adjust backlight" and the flickering stopped. Not sure why, but thought I'd add it to the thread.
Click to expand...
Click to collapse
Yeah I did notice that it's only really noticeable when the screen is set to max brightness. Setting it on auto adjust cleared it up for me also.
proj3ktpat said:
Yeah I did notice that it's only really noticeable when the screen is set to max brightness. Setting it on auto adjust cleared it up for me also.
Click to expand...
Click to collapse
thx guys...helped me out too...
Just sent my unit in for repair (under warrenty) due to the screen flicker issue, lets see what happens when it comes back.
I just started to experience the flicker today. Has be somewhat concerned. The device is only two weeks old.
However, it seems to have stopped by itself while I was searching the forums for an answer. If it returns, I'll try the 'remove battery' method and see if that helps.
Also, I love Scrobble! Shame it doesn't work on QVGA displays. Or, at least, didn't on my Wizard...
Related thread
Hey guys there's a thread with the same exact issue and a screenshot on the first post.
http://forum.xda-developers.com/showthread.php?t=535099
Seems to be something related to the Hardware 3D Acceleration driver for Windows Mobile, I get this problem only once 3d has been activated.
If Sense/TF3D is turned off, I never see this problem. It only comes up once a game or Sense has been launched.
I can also boot into Android without 3D activated and not have this problem, but if I run Sense then go into Android I get the flicker from a Windows Mobile screen while in Android.
protwitness: That doesn't seem to be the case (for me, at least.) I don't run TF3D and it still happens. I can't really discern what the trigger is, but I have a feeling it has something to do with the screen brightness auto adjustment. (Sometimes, I'll turn my phone on when it's dark and it jumps to full day-light brightness for some reason.)
I've adjusted to it and it doesn't really bother me any more.
I got nexus s (i9020T) recently and found the touch screen unresponsive sometimes. I've already tried several launchers(adw, lancherpro, go launcher ex), and it seems not launcher's problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
Later I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally.
I'm confused by the strange behavior, anyone experienced similar issue?
more info from test,
I connect my phone with adb, and tried to "cat /dev/input/event0"
The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I don't know kernel very well, so I cannot find the source code Any help please?
FYI. we are not alone.
http://code.google.com/p/android/issues/detail?id=13853
I got this problem too whenever my phone is in my pocket facing inward.
I have tried to open the calculator to see which part of the screen having problem. Mine is usually the "8" and "5" location unresponsive if my phone stayed in my pocket facing inwards for a certain period of time.
The problem will goes off after couple of mins when i can feel that the phone is cooler than my body temp.
I knew this happens to the Dell Streak as well.
I've had an odd problem with my 820 almost since getting. I'm hoping one of you geniuses have some advice.
When I turn it on it works perfectly, sometimes for hours. Then the screen goes blank, and then random pixels begin to appear, starting at the top of the screen. Outdoors rather than random pixels the screen goes almost totally green. Strangely, if part of the screen is obscured the green only covers rhe exposed area.
Pressing the on button repeatedly usually brings back the lock screen and reset (on+down) fixes the problem for another few hours.
By the way, eventhough I can't see the screen the touch sensor works. For instance I can hold theon button and then swipe downwards to turn off the phone. I can also answer and hang up using earphones.
My daughter who purchased the phone said it worked fine until the amber update. I had hoped the black update would fix the problem but no change. I found some posts from people with the same problem who sent the phone in to be fixed and got it back in the same condition. I really don't want to go through the hassle unless I expect to get it back fixed. I'd rather try fixing it myself.
My question is whether this is a firmware problem an whether it is likely that re-installing the stock black rom would do any more than the ota install that occurred automatically did (or didn't do).
Any ideas?
Nobody?
By the way it seems to happen only, or mostly when in standby.
I installed an app that displays a clock and doesn't allow the phone to go into standby mode,
and the problem doesn't appear to occur (unless I forget to leave the app on top).
I would set the phone to standby = "never" but the option isn't available on my phone, though
I understand that there are those with the standby = "never" option.
Any idea if I can set standby = "never" with keyboard commands, perhaps?
I've got an intermittent problem - sometimes when I wake the phone up, the touch screen doesn't work. It happens when I wake it up with the power button, when someone calls, or when an alarm wakes up the screen. That means when the problem happens, I can't answer the call, or turn off the alarm (sometimes locking the screen and waking it up immediately works).
It doesn't seem to be affected by whether or not the phone is or has been charging, whether it's been in my pocket or the temperature of the device. I've not been able to discern a pattern at all. Once the phone is unlocked and the touchscreen is working though, it works perfectly. The problem never returns while I'm using it, only if I lock it, and only sometimes.
If I leave the screen on while touch is unresponsive, I can tell when it is responsive to touch again by a line that quickly flashes along the top edge of the screen. At that point, the screen operates entirely normally.
In what may be a related item, when I'm on a call, sometimes the proximity sensor doesn't work properly and the screen turns back on and starts working. I get off the call and find my phone in a different app.
Does the Nexus 5 use the proximity sensor while the screen is off as a way to weed out unintended touches while the phone is in a pocket?
I'm going to try and store it face up over the next couple of weeks and see if the problem continues, but I was hoping that someone might have some insight.
About the phone:
I cracked the screen over the summer and had it replaced, but I didn't have any issues with it at all until I installed Lollipop. 5.0.1 hasn't made a difference
I use an older Samsung Note 4 with the latest stock OS allowed for it. I have had an issue since day one that I can't seem to find a solution.
I want to be able to disable the screen from turning on, unless I hit one of the physical buttons (typically Home or Right side button). The reason is that notifications and other background processes keep lighting up the screen. Sometimes, the screen will just stay on and not timeout. Also, if the phone is in my pocket, it senses my body and starts interacting as though its my fingers. I am only aware of this once the phone heats up and then all my icons are messed up. The biggest problem is the battery drain from all this. Setting the timeout short does not really help and is kinda annoying itself.
I have not been able to find a setting or app than can suppress this. All of my searches just turn up the opposite solution to keep the screen active constantly.
Is it possible to disable the screen until an actual physical button is pressed? If so, what is the solution? New OS, new phone, app?
Thanks.