Hi,
I've noticed an issue recently with my SGS3 (I747M). The flicker that I am referring to is not the more common hardware overlays issue, but rather only occurs, or is noticeable, on a white background. What happens is the screen will flicker colors; it's not that the entire screen will display one color and change to another and another rapidly, but rather it seems random pixels on the screen will flicker in waves...almost a 'shimmering' effect. So far, it seems to happen not immediately after reboot, but later on as I use my device. I was hoping this was a software issue, but so far it seems to be more likely a hardware issue.
From googling, I have found that this issue is not limited to myself (http://www.howardforums.com/showthread.php/1772504-Samsung-Galaxy-S3-Praise-and-Problems), that being said, I couldn't find anyone else here on XDA that has this issue. Have any of you experienced it? and if so, what did you do? return under warranty perhaps?
Thanks in advance.
mk_ln said:
Hi,
I've noticed an issue recently with my SGS3 (I747M). The flicker that I am referring to is not the more common hardware overlays issue, but rather only occurs, or is noticeable, on a white background. What happens is the screen will flicker colors; it's not that the entire screen will display one color and change to another and another rapidly, but rather it seems random pixels on the screen will flicker in waves...almost a 'shimmering' effect. So far, it seems to happen not immediately after reboot, but later on as I use my device. I was hoping this was a software issue, but so far it seems to be more likely a hardware issue.
From googling, I have found that this issue is not limited to myself (http://www.howardforums.com/showthread.php/1772504-Samsung-Galaxy-S3-Praise-and-Problems), that being said, I couldn't find anyone else here on XDA that has this issue. Have any of you experienced it? and if so, what did you do? return under warranty perhaps?
Thanks in advance.
Click to expand...
Click to collapse
It might be a digitizer problem, digitizers are hard to replace but, I think zedomax has a way to change it.
Just go on galaxys3root.com-- this might help http://galaxys3root.com/galaxy-s3-root/how-to-replace-broken-lcd-screen-on-galaxy-s3/
thanks for the reply, but would a malfunctioning digitizer actually cause the screen to shimmer as it does? I would think it might be a digitizer problem if the screen wasn't recognizing my inputs properly, but I think this is a different issue which, to me, seems to be not related to the digitizer.
thanks though!
any other possible ideas/solutions?
I have had that issue. It would do the same thing and then lock up because I would try and hit the home button. The. It would do a full reboot. Weirdest thing I have ever had happen to a phone. I tried different than roms and stock and didn't do a dang thing. Returned it to att.
Sent from my SGH-I747 using xda app-developers app
I suppose if it actually does get to that point where it renders the phone as unusable as in your case, I'll probably do the same...though since it's outside the 14 days I have with my provider (Rogers), I think I might have to go through with a warranty replacement through Samsung.
Thanks for the reply
update:
It seems it was either the ROM or Kernel that caused the issue (last few versions of task's AOKP). After flashing a different ROM (bacon version of Roger's JB), the issue seems to be resolved *knock on wood*.
Related
Hi,
sometimes the touchscreen of my defy stops working (but the phone is not frozen)
and the only way to fix it is to lock/unlock the screen...
does anyone have the same problem (and can help me)?
thanks
P.S
i've had the problem both with stock rom (2.2) and with cyanogenmod rc 1.5
When this happens, do the 4 buttons below your display still give you haptic feedback (little vibration) or do they react not at all?
Also, does this only happen when there's the normal launcher/standby screen active or when there's an other app active too ?
Did you undervolt ?
Edit: Also, this seems to be a hardware problem which seems to be well known in a certain German android forum but I cannot find much about it in here. In short, the digitizer unit seems to be broken for some people and locking/unlocking helps because it disconnects and connects power for the digitizer. The people there fixed the problem by replacing the digitizer (which isn't easy at all!).
It would be nice to have someone from XDA who had this problem before too, to confirm this problem!
First of all, thank you for the answer
When I have the problem, 4 buttons stop working too.
It usually happens after a period of stand-by, i don't undervolt or have some other application running than the launcher (ADWlauncher).
I bought the phone one week ago, if it is an HW problem, i can't repair it by myself...
I'd recommend to wait and see whether xda has other suggestions for you and if not, just check the Motorola hotline and ask whether they know something and if they do change it for free.
Also, what you describe fits perfectly to what I've read elsewhere (don't know whether I'm allowed to post a link here or if it were useful at all because it is in German). So it sounds like your digitizer could really be defect.
ok, even if i hope to solve the problem by myself...
News: They've changed the touch screen, but the problem is still present...
Can it be a sw problem??
Keep sending it back, they will replace it in the end.
Sent from my MB525 using Tapatalk
the whole phone?
Yes, the whole phone. They have two year warranties, but don't put up or make do, you should have a phone that works right
Sent from my MB525 using Tapatalk
I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.
I wonder when it happens ,are you charging?
nameite said:
I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.
Click to expand...
Click to collapse
What nightly version are you using?
The problem happens even if i'm not charging...
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.
KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium
Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.
Any news? Was it the battery issue?
Hey guys,
I know that the screens on these phones are turning out to be junk, but I'm looking for some opinions on whether my particular issue (which I don't think has been brought up here before) is a hardware problem, or if it just looks like a software bug.
I've attached a picture of the glitch, which appears as two lines of random pixels that flicker between pink and green. I've circled in red the pixels that were doing it at the time (it only seems to happen with darker colours). The picture is GTA3, but I know that it also happens in the music app and when flicking between sense themes (although it's harder to reproduce in those apps). Oddly I've played Spirit HD too, but that doesn't cause it.
So what do you guys reckon, is it more likely a hardware issue or is this something that a driver update could fix, and is anyone else having this problem?
Thanks
Apparently the attachment didn't work, so here's a link: img713. imageshack.us/img713/7762/phonebug.jpg (remove space after the first dot)
enough with this FUD the screens are not junk, in fact they are amazing and made iphone owners shivers
the software has a glitch causing all sort of graphical corruption ie not the screen, glitches that goes away are software, glitches appearing in the same place in all phones are software, glitches that never manifest in certain apps are also a sign of software issue
software is no problem, no one updates their phones faster than HTC
end
hamdir said:
enough with this FUD the screens are not junk, in fact they are amazing and made iphone owners shivers
the software has a glitch cause all sort of graphical corruption ie not the screen
end
Click to expand...
Click to collapse
OK fair enough, but given the amount of people complaining about screen flex issues and the like, surely I can be forgiven for thinking otherwise?
I raised the topic because this doesn't seem like the "software issues" that everyone is talking about though (the ones with flickering status bar etc).
Thanks for your input
I have had no issue for 4 days and noe all of a sudden I'm getting a red box outline all the way around the screen when selecting options in some menus very random
Sent from my HTC One X using xda premium
root, install a custom rom, problems solved.
combat goofwing said:
I have had no issue for 4 days and noe all of a sudden I'm getting a red box outline all the way around the screen when selecting options in some menus very random
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
A red box around the whole screen? I think that's caused by the keyboard. I never experienced this on my phone because i use swype but i see it very often if i use the emulator. try a different keyboard. perhaps this fixes your issue.
mikep1993 said:
A red box around the whole screen? I think that's caused by the keyboard. I never experienced this on my phone because i use swype but i see it very often if i use the emulator. try a different keyboard. perhaps this fixes your issue.
Click to expand...
Click to collapse
i think that's a debug option in developer settings...indicates whenever menu speed is above a certain threshold afaik...i might be wrong though.
disable "Strict mode", reboot, wipe cache & dalvik for the hell of it...
Hi!
In my Galaxy Nexus, a line of pixels on the top of the screen isn't normal.
http://i.imgur.com/sd9WGXJ.png
Just see by yourselves... The line at the top of the sreen (left side when landscape mode) isn't coloured normally. Is it a screen issue or software issue? I am using coloured softkeys that I modded with metamorph but I've never noticed this problem for 3 months of softkeys modification, just now...
If it is a hardware problem I'll send it do warranty, but I need to be sure that is worth of it
Seems like a hardware problem. The app you asked about doesn't seem like it'll fix it, but worth giving it a shot.
no it doesn't fix... what kind of "pixel disease" it is?
warranty covers that?
http://forum.xda-developers.com/showthread.php?t=1394358
Thanks, I've posted my problem there also
Hi Guys!~
Hope all is well !!
... recently I came across my rooted android 11 Pixel 3XL got a screen flashes with bright home screen background during the screen turning off and entering ambient display mode.
I try my best to find a solution but haven't found one yet.
I have tried to reflash to stock, also doesn't fix the problems.
... the only solution I found at this moment is to get android 12 beta which the transition animation from turning off the screen to the wake up of ambient display is totally different and I still prefer to stay with rooted android 11.
Your browser is not able to display this video.
Sounds like a hardware failure, display or mobo.
blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.
haritvii said:
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.
Click to expand...
Click to collapse
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.
blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse
blackhawk said:
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.
Click to expand...
Click to collapse
Thank you so much, now I got a great reason to get a new Pixel 6 then
haritvii said:
Thank you so much, now I got a great reason to get a new Pixel 6 then
Click to expand...
Click to collapse
I could be wrong... and even if it is hardware that doesn't mean a work around doesn't exist to make it usable.
Play with it, Androids wuv attention