{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My screen is flickering!!
these saples shows how my sm850f has problem with content of screen, this problem dosnt affect the screenshot, and more distingushable in low light
TEST!
please reup your screenshots (only see your thumbnails).
I have exactly the same problem
AT&T Galaxy Alpha Screen Flickering
MOMO1265 said:
My screen is flickering!!
these saples shows how my sm850f has problem with content of screen, this problem dosnt affect the screenshot, and more distingushable in low light
TEST!
Click to expand...
Click to collapse
I have the same problem. I assume it might be a hardware issue, as long as only the lower third of the screen is affected. My screen only starts flickering when on low brightness only (<20%). Also, if I set the brightness the lowest possible setting, the RGB color balance seems to be distorted and shifted to the green (the screen seems 'greenish').
I've had this phone for over a year. The problem manifested a couple months ago, maybe in Oct-Nov 2015 and has been pretty stable since then.
Same problem. Just up your brightness a bit.
shevtsof said:
I have the same problem. I assume it might be a hardware issue, as long as only the lower third of the screen is affected. My screen only starts flickering when on low brightness only (<20%). Also, if I set the brightness the lowest possible setting, the RGB color balance seems to be distorted and shifted to the green (the screen seems 'greenish').
I've had this phone for over a year. The problem manifested a couple months ago, maybe in Oct-Nov 2015 and has been pretty stable since then.
Click to expand...
Click to collapse
How did you solve this problem?
AceyWAR said:
Same problem. Just up your brightness a bit.
Click to expand...
Click to collapse
but continue in dark
Rojikaft said:
please reup your screenshots (only see your thumbnails).
Click to expand...
Click to collapse
fixed
it become worse...
now I have 3 part in my screen that have 3 different light when the screen in AUTO mode in dark or when it's in low set of light...
is the any help?
I experienced the exact same problem, Samsung replaced the screen under warranty in their 24 hour repair service about a week ago. Haven't experienced any problems since repair.
Has anyone figuered out a solution for this problem without replacing the screen?
Is there any help??
Did you tried factory reset?
Neither of doing a factory reset nor reinstalling original frimware helped...it just stops for sometime when i set to manual mode and then set it to the highest level then return it to the lowest level
gtrs36 said:
Did you tried factory reset?
Click to expand...
Click to collapse
no help
even safe mode
Markus263 said:
Neither of doing a factory reset nor reinstalling original frimware helped...it just stops for sometime when i set to manual mode and then set it to the highest level then return it to the lowest level
Click to expand...
Click to collapse
you think it is a hardware problem? if not who can help us??
@MOMO1265 yes it's probably a hardware problem because i used to have epsilROM when i encountered this problem for the first time and i reinstalled the official firmware and it didn't help and i've sent an email to samsung and they couldn't help me all they said is that it's probably because of the custom rom i used to have all they will tell you to do is to replace the screen and it's probably your fault not their ****ty materials fault...maybe if there's an international email to samsung we can send our complaint to,maybe they will be more helpful
Samsung does nothing about it
I have the same problem so sent it back under Samsung warranty and they did nothing. They claimed to have repaired it but the problem is still occurring. Anyone have a fix? Anything would help. Thanks
Possible solution...
I had the same problem, seems like enabling soft-key back light solves the issue. I installed Screen Filter app and now, if I set the filtering to 50% from the app an brightness to 2 on Auto, no flickering happens. The app also helps if you want a dimmer screen than the standard minimum brightness setting can give you.
I hope it helps.
Replaced the screen ...still happening!!
A couple of months ago before my warranty got expired i went to samsung and they changed my screen. intially the problem disappeared but it came back recently and i don't know what to do.
Related
For a while I was doing this almost every call. Now it happens about 50% of the time.
Am I the only one who accidentally disconnects calls with my chin pressing the "End Call" button?
Is there a fix or am I just not used to this phone....?
(I realize that I am opening myself up to some serious smart ass comments)....
Thanks
Clean off the sensor top left of the screen. It automatically turns off the screen when you have the phone at your face. There is also a setting somewhere to control this. Check that it is on.
atwnsw said:
For a while I was doing this almost every call. Now it happens about 50% of the time.
Am I the only one who accidentally disconnects calls with my chin pressing the "End Call" button?
Is there a fix or am I just not used to this phone....?
(I realize that I am opening myself up to some serious smart ass comments)....
Thanks
Click to expand...
Click to collapse
It happens to me all the time, I've cleaned the sensor many times and it doesn't help. I think its just a design flaw from them putting it behind the mesh for the speaker, this is also why you can't see the led unless your looking straight at the phone. Luckily I don't make a lot of calls because this device wasn't designed to be a phone, it seems like that was just a feature that was tacked on in the last minute because of the horrible proximity sensor, bad call clarity/speakers and mic
Download myLock utilities (free at the market) and enable 'In Call Screen Lock'. It wont solve the prox issue, which seems to be a software flaw, but it will prevent accidental screen touches. Also, make sure the 'back button' option is checked, since the phone does not have a camera or nav key.
Sent from my StarTAC
atwnsw said:
For a while I was doing this almost every call. Now it happens about 50% of the time.
Am I the only one who accidentally disconnects calls with my chin pressing the "End Call" button?
Is there a fix or am I just not used to this phone....?
(I realize that I am opening myself up to some serious smart ass comments)....
Thanks
Click to expand...
Click to collapse
Try Settings->Call Settings->Always Use Proximity.
Sometimes orientation can overrule proximity if that's off so holding it between your cheek and shoulder allows the screen to turn on.
I've found that after I connect the call that pressing the power button to turn off the screen prevents all of these issues
Sent from my ADR6400L using Tapatalk
Absolute_Zero said:
Try Settings->Call Settings->Always Use Proximity.
Sometimes orientation can overrule proximity if that's off so holding it between your cheek and shoulder allows the screen to turn on.
Click to expand...
Click to collapse
I went to Menu=>Settings=>Call=> and don't see anything that lists "Always Use Proximity".
Can you please walk me through this again? I must be missing a step.
Please note that I am rooted and using Das Bamf 1.8 Remix which might be the problem for not having this option available....
superchilpil said:
I've found that after I connect the call that pressing the power button to turn off the screen prevents all of these issues
Click to expand...
Click to collapse
The only problem with that is that it comes back on as soon as the sensor no longer senses your face (unless it doesn't senses it when you shut it off or anytime thereafter)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kinda OT but damn I hate it when I accidentally call somebody and the screen keeps turning on and off and I can't freaking end call!! i especially hate it when it's to somebody random. arg... just wanted to get that out there... Small price to pay for a touch phone i guess.
atwnsw said:
I went to Menu=>Settings=>Call=> and don't see anything that lists "Always Use Proximity".
Can you please walk me through this again? I must be missing a step.
Please note that I am rooted and using Das Bamf 1.8 Remix which might be the problem for not having this option available....
Click to expand...
Click to collapse
Yea, sorry...that may have been introduced in GB or just aosp based. I've been on it too long to remember.
PhillyCheez said:
Kinda OT but damn I hate it when I accidentally call somebody and the screen keeps turning on and off and I can't freaking end call!! i especially hate it when it's to somebody random. arg... just wanted to get that out there... Small price to pay for a touch phone i guess.
Click to expand...
Click to collapse
Most touch phones don't have this problem, at least none of the 3 I had other than the tbolt. I think this is because of the horrible proximity sensor placement, they shouldn't have put mesh over it.
eraursls1984 said:
Most touch phones don't have this problem, at least none of the 3 I had other than the tbolt. I think this is because of the horrible proximity sensor placement, they shouldn't have put mesh over it.
Click to expand...
Click to collapse
Ah. Yeah... Happened on my dinc quiet a bit. Maybe an HTC thing?
eraursls1984 said:
I think this is because of the horrible proximity sensor placement, they shouldn't have put mesh over it.
Click to expand...
Click to collapse
Putting a mesh over it is a very bad idea. I suppose that why they didn't do that. The sensor is under the glass, at the very top, in the "check mark" part of the Verizon logo. Dust can get in through the small crack at the top of the screen, and cause problems - a shot of air will clean it out.
mike.s said:
Putting a mesh over it is a very bad idea. I suppose that why they didn't do that. The sensor is under the glass, at the very top, in the "check mark" part of the Verizon logo. Dust can get in through the small crack at the top of the screen, and cause problems - a shot of air will clean it out.
Click to expand...
Click to collapse
Your right, I guess its not a bad design, just poor build quality/parts.
PhillyCheez said:
Ah. Yeah... Happened on my dinc quiet a bit. Maybe an HTC thing?
Click to expand...
Click to collapse
Maybe its the crappy sensor they use, out of two Motorola and two blackberry phones none had this problem (not all were mine, but I use my wife's phone a good bit) this is my first HTC phone and the longer I have the more its looks like it will be the last also
Hi
I have a Korean Galaxy S2 SHW-250K, and I flashed a XXKH3 firmware on it. Used it for a couple of days, then went ahead and installed MoDaCo GR5 firmware on it. Now while exploring the options, I tried to test out that tilt-to-zoom feature in Gallery, but it didn't work so well. In fact, it more or less didn't work at all despite me checking out all the settings. So I went into Gyro and Horizontal calibration, and noticed something strange. The horizontal calibration dot was moving in jitters despite I had a pretty steady hand holding it. So I went into gyro calibration and noticed that this dot was not moving at all.
I then remembered that when I first got the phone, with Korean firmware and all, I calibrated the sensors and I don't remember seeing the dot ever moving as I calibrated it while placing it on a flat surface.
Now I went into the *#0*# menu and ran the tests. The results are like this:
Gyro sensor Display reading while sitting on a flat surface:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The self test apparently cleared:
The compass also doesn't respond to magnetic fields at all, and more or less rotates with the phone. Tested in a couple other Compass apps, and calibrated it by moving in 8 shape and all, but no avail:
Any idea what's wrong with it? Can it be fixed via software, or is it a hardware issue?
What.. no love?
I have the same issue with my s2
the compass is much more jumpy and less accurate than my old HTC hd2
i hope its not a hardware issue.
Im having the same issue guys.
Horizontal calibration works, but the gyro one doesnt- the blue ball doesnt move!!!!
Same here
Sent from my Desire HD using Tapatalk
any solution, I think i have the same issue
Is this a hardware problem?
I have the same problem too. The compass is not working properly. It's turning in the reverse direction. And pointing to incorrect directions.
Is there any config or app to correct this problem?
Same problem on my Galaxy Note... anyone know how to fix this? Should I return my phone?
I just solved a very similar problem on my colleges SGS2 buy removing it from its case with MAGNETIC catches.
Nobody came up with idea it's nothing wrong with it? It is gyroscope, just put phone on something stable and calibrate to get rid of offset in gyro readings. In other word to make phone know to show zero readings when it has no angular velocity (not rotating).
I'm also having a problem with my shw-m250s. I hope someone can find a solution to this problem. It would be nice if someone made a custom rom based on the official m250s rom.
same problem here, with different roms and kernels..
I have also this problem on my GT-I9100G --' the compass is not accurate as well as when I have bought it 2 mouths ago. Maybe it's a hardware issue caused by magnetic fields caused by charging the battery, I'm not sure of that.
My compass problem
Hi.
If your compass doesn't work, check yours cases. I have magnet within my phone case , and matal parts in my phone was magnet too. It's disturb magnetic field and compass was useless.
And my galaxys s 2 gyroscope not working, have solutions?
I have solvet the problem ( for me )
dzid_ said:
Nobody came up with idea it's nothing wrong with it? It is gyroscope, just put phone on something stable and calibrate to get rid of offset in gyro readings. In other word to make phone know to show zero readings when it has no angular velocity (not rotating).
Click to expand...
Click to collapse
So i heaved the same problem ( when playing a racing game the car goes left even if you have tilt the phone to right ) i was using the phone whit Snapdragon v2 when this problem occurred ( i don't know why but in 4.1.2 there is no proper calibration ) and after long research on that stuff i flashed some random 4.0.4 costume ROM (because i can't find stock ICS ) i calibrate it and everything worked like a charm / Then i installed again Snapdragon and everything still works perfect. So try some old ICS or Gingerbread ROM's
checked with sensor kinectis app ..sensor is working ..but the direction it suggests in any app is like captains jack sparrow's compass
Never worked for me
I also have a S2 and the compass never worked.
I downloaded several apks and none worked.
I flashed some roms (latest is cyanogen), and this doesn't help - the compass still doesn't work.
The compass is base in a magnetic sensor, inside the phone, and it doesn't work.
The gps-based compass is, in reality, a compass based in calculations made when you are moving with gps enabled, and it doesn't use the internal magnetic sensor.
That's more than one year i have this s2.
Today, I have found something that can help, bus, as I can't post external links in the forum, do this:
Open youtube.
Add, to the address ( after the .com): /watch?v=Rak2xhnk0qE
Hope this help
Ok heres my problem.
I have an unlocked atrix running on redpill and this morning i noticed that i have a "dead line" across my screen. About 1 inch down on my screen there is about a centimeter space where the touch does not register. So I downloaded a touch test and it sometimes does not register at all and sometimes it registers even when I'm not touching it.
I also checked and the screen is flat across (no dents/cracks etc...).
Do you think that this is a hardware or a software problem?
And any ideas how to fix it?
Thanks!
Try flashing the pds image. There's a thread about that in General.
I cant find that post i've been looking for an hour and a half, can you help me with a link?
sorry...
Also will reflashing my rom help?
Ah, you asked nicely..
http://forum.xda-developers.com/showthread.php?t=1131649
Try flashing another rom, you never know. Doubt it though..
We have the same problem I think. I missed this thread and started a new one.
After installing Faux's 2.0 enhanced kernal on my CM7, I now have a dead region of my touchscreen which is a little above the middle of the screen, 1/4 inch all the way across (horizontally). I verified this by using the touch test app from the market.
It is also very obvious as scrolling is extremely laggy.
I have already tried wiping my phone with fastboot, performing the PDS fix, and then wiping again in recovery and reinstalling CM7.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see the dead space, very frustrating.
I have even tried flashing back to 1.83 using fruitcakes, then downloading the official moto gingerbread update so I am as close to stock as can be other than being unlocked and still no go.
Is this a hardware failure (that others are having too apparently?)
fsturbo15 said:
I have even tried flashing back to 1.83 using fruitcakes, then downloading the official moto gingerbread update so I am as close to stock as can be other than being unlocked and still no go.
Is this a hardware failure (that others are having too apparently?)
Click to expand...
Click to collapse
although the OTA update is essentially the same thing, i would say your last glimpse of hope is using rsd lite to flash a gingerbread sbf. (2.3.4 sbf file, just to clarify)
and if that doesn't work, at least your phone will be in a completely stock state to go in for a warranty replacement?
Just flashed it, i'll check back in later
Sent from my MB860 using XDA App
Well I just felt like a fool.
I did absoloutely nothing from yesterday (when I went back to 100% stock, reset phone) to today.
At 1:30, I did the same test with Touch Test and got the same dead zone. By the time I got to ATT for a warranty exchange, the screen worked flawlessly. Other than turning on airplane mode and having an extremely low battery @ 5% I did nothing in that hour.
I'd rather have the problem come back at this point and get a new phone than it work fine until my warranty ends and i'm stuck with a dud.
My dead spot is a little higher... but same thing.
Can you think of anything that happened to the phone that would damage it like this. My wife plays coin dozer (there is a lot of tapping) and the dead spot is around that area.
And wow that's bad luck. Mine was going on and off (more dead then alive). Did yours die again or is it back to normal?
I just want to figure out if this is a software or a hardware problem.
On another note i just flashed redpill v4 and it hasent happened yet... maybe. I can only hope...
Well, my phone fixing it self was only temporary.
After going home and doing nothing to my phone other than charging it, the dead zone is back.
This is a hardware issue for sure, the digitizers seem to be failing after some time.
Get a replacement.
thanks.
more money into this phone...
fsturbo15 said:
Well, my phone fixing it self was only temporary.
After going home and doing nothing to my phone other than charging it, the dead zone is back.
This is a hardware issue for sure, the digitizers seem to be failing after some time.
Get a replacement.
Click to expand...
Click to collapse
But what about orange's fix?
http://www.motorola.com/staticfiles...4.4.20_Orange_GB_Upgrade_Release_Notes_GB.htm
"Screen Touch Sensitivity | Fixed touch-screen ghosting and phantom touch events."
Your digitizer connector is cracked.
prove it by pushing on the top left above the glass and use touch test and watch the difference. You need a new digitizer it cost $60 and about 30min to an hour of work.
What's the difference should be? One time touchscreen wasn't reacting but only one time. But how could it prove digitiser problem?
Sent from my MB860 using XDA App
gekster said:
What's the difference should be? One time touchscreen wasn't reacting but only one time. But how could it prove digitiser problem?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
because that's where the digitizer connector is, and pushing on the screen there will cause it to move.
when mine cracked, it caused it to double the effected area when I was to push there.
also, I had made a typo in my previous post.
it's the top left, not top right; i apologize.
Milenko2121 said:
because that's where the digitizer connector is, and pushing on the screen there will cause it to move.
when mine cracked, it caused it to double the effected area when I was to push there.
also, I had made a typo in my previous post.
it's the top left, not top right; i apologize.
Click to expand...
Click to collapse
I have from 2 to 5 ghost fingers, which a) moving horizontally toward the edges of dead zone, b) located motionless at the edges of the dead zone. What behaviour of screen should be if I press that point on the healthy phone?
Is it what I need to replace?
http://www.ebay.com/itm/Original-NE...aultDomain_0&hash=item19cb8661c6#ht_756wt_906
Hello all, I have a G-tablet with a stuck volume and power button. I took apart the tablet and saw that the little metal dimples which get pushed down by the plastic button are stuck flat. Is there any way to fix this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How old is the gTablet? Could it still be under warranty?
Sent from my gTablet using Tapatalk.
I bought the tablet off craigslist with the button problem already present.
I managed to get the button working a little. But now it seems to be stuck in APX mode where the screen doesn't turn on or anything but my PC recognizes it in APX mode. It will not start on its own. A little googlefu led me to this forum
http://www.slatedroid.com/topic/221...n-gtab-does-not-turn-on-and-stay-in-apx-mode/
I followed the instructions, but when I get to step 2.1 it boots to tap&tap instead of recovery. If I shut down the tablet and turn it back on it goes right back to APX mode again without me pushing any volume buttons.
I'm new to the gtablet scene so if somebody could point me in the right direction to fix my tablet, it would be greatly appreciated.
Stuck - Disconnect rocker
falcaraz said:
I bought the tablet off craigslist with the button problem already present.
I managed to get the button working a little. But now it seems to be stuck in APX mode where the screen doesn't turn on or anything but my PC recognizes it in APX mode. It will not start on its own. A little googlefu led me to this forum
http://www.slatedroid.com/topic/221...n-gtab-does-not-turn-on-and-stay-in-apx-mode/
I followed the instructions, but when I get to step 2.1 it boots to tap&tap instead of recovery. If I shut down the tablet and turn it back on it goes right back to APX mode again without me pushing any volume buttons.
I'm new to the gtablet scene so if somebody could point me in the right direction to fix my tablet, it would be greatly appreciated.
Click to expand...
Click to collapse
Thinking out loud...have you tried disconnecting the rocker switch @ the connector to make sure the vol (-) contacts isn't still making contact & forcing the tablet into apx? Disconnectng should make it appear that neither Vol - or + is pressed.
As far as repairing the switch...from appearances, the contacts on the switch looks similar to what Atairi joysticks used to use (on a board vs ribbon/flex cable)...the switches would fail when either the plastic coating over the contact wore through causing the disk to move & not make the correct contact or the adhesive tape covering it would let loose causing faulty/randon contact. I used used to remove the adhesive tape & re-cover the switches with similar adhesive plastic to make them work again. Can't tell from your picture if removing the film is might be possible, but if it is, it's something try...especially it the contact is actually stuck down.
Al
G-Tab no longer under warranty
If you did have a warranty you voided it the minute you opened the tablet. Did you check it really good for any type of sticky substance that might have gotten into the keys? It happens and all it takes is one mi-nute drop from a soda or etc etc etc.
Thank for the replies but I am glad to report that I got the Gtab working properly. I fixed the buttons by removing the plastic and pressing down on the inside center of each cap slightly to bend them back into shape. Seems the last owner was a little overzealous when pushing the buttons and completely flattened 2 of them. I covered them with a piece of clear packing tape and all is well so far.
Also fixed my APX mode problem by following djab's awesome instructions.
http://forum.xda-developers.com/showthread.php?t=1167944&highlight=apx+mode
I got my phone two days ago, but I've noticed this from the very beginning. Completely stock with latest OTA (Sprint). I've been collecting screenshots and taking notes to try to find a pattern and to better understand the problem. Check out the 100% screen-shots below. I've added some arrows. Notice that once you see artifacts on a letter, the same artifacts appear on every occurrence of that letter (of the same size/font/etc). For instance, the lowercase letter "r" appears three times in big, white, heading font and all exhibit the exact same artifacts. The "r" in the grey subtext and the "r" in heading ("Wireless") do not. Both "F" characters in the "OFF" button look identical as welll (forgot to put some arrows here).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The problem seems random and affect random letters at random times. The fact that the screenshot sees it means that it is not a problem with the screen. It is actually in the screen buffer. It seems like a font rendering issue, since the artifacts are identical on all occurrences of the character.
Changing fonts doesn't fix it. Changing text size doesn't fix it. I can interact with the screen, and the artifacts remain. But if I change screens (select an option, open/close an app, etc.) then the artifacts change. By change, I mean it may go away but other artifacts may show up. It is not super common, but if I navigate around the options menu (because it has a lot of text), I will probably see it within 15-30 seconds. Some are so minor, that I don't easily notice.
Has anyone else seen these before?!
The attached zip file contains a few more untouched (except for hiding personal info in one) screenshots. I have a lot more screenshots if anyone is interested.
I get them too. Only noticed it in the system menu though.
kronium said:
I get them too. Only noticed it in the system menu though.
Click to expand...
Click to collapse
I rarely see it outside of the system menu, but it might be because there's a lot less text. But it does happen. The second screenshot above showed that it could happen in the homescreen (the alarm widget) and here's one in the "Reddit is Fun" app. All the letter "o" characters in the title bar are messed-up:
Solution??
Did you guys find a solution for this? Have you guys contacted Samsung?
universem2 said:
Did you guys find a solution for this? Have you guys contacted Samsung?
Click to expand...
Click to collapse
Does this mean that you have the same issue too? From the lack of replies to this thread, it seems not many people do or they aren't OCD enough to care. Anyhow, I'm exchanging my phone for another reason (two dead sub pixels and several random reboots) so it will be interesting to see if the new phone behaves the same way.
Well it seems I have this issue as well but what concerns me the most is if this is a hardware defect. If I can flash a drastically different ROM from the stock one and the corrupted fonts do not appear then it is most likely a software issue however at this point I think it is a hardware issue.
Nothing else is wrong with my phone so I would hate to give it back just for this reason and then get a phone that has dead pixels or a screen filled with those black dots people here are tacking about..
Here's mine
Sent from my SPH-L710 using Tapatalk 2
Hayabusa... Your font corruption is on a whole 'nother level!! Could you describe what happened? Is this a regular occurrence?
jacksparr0w said:
Well it seems I have this issue as well but what concerns me the most is if this is a hardware defect. If I can flash a drastically different ROM from the stock one and the corrupted fonts do not appear then it is most likely a software issue however at this point I think it is a hardware issue.
Nothing else is wrong with my phone so I would hate to give it back just for this reason and then get a phone that has dead pixels or a screen filled with those black dots people here are tacking about..
Click to expand...
Click to collapse
Good (?) thing mine has dead pixels and other issues, so I have no problem exchanging mine. If the new one does it too, then it is definitely more wide-spread.
Haha luckily I remember what to click on
It was the first time I seen it lol
Sent from my SPH-L710 using Tapatalk 2
I sincerely doubt this is a hardware issue. Have you guys tried changing from the default font? (settings, display, font style) I haven't noticed anything like this, but I switched to helvetica s on the first day of random customizing, just because I remember reading someone who liked it. Seems nice enough, but I don't have much basis to judge fonts.
bohiti said:
I sincerely doubt this is a hardware issue. Have you guys tried changing from the default font? (settings, display, font style) I haven't noticed anything like this, but I switched to helvetica s on the first day of random customizing, just because I remember reading someone who liked it. Seems nice enough, but I don't have much basis to judge fonts.
Click to expand...
Click to collapse
From my OP above:
ken830 said:
Changing fonts doesn't fix it. Changing text size doesn't fix it.
Click to expand...
Click to collapse
After seeing this issue, I switched to Helvetica and have been using that since.
I have started using the Helvetica font style as well now and I have not noticed the artifact/corruption at all yet however If I do I will be sure to post it in this thread.
Edit: issue still exists but not as prevalent. I noticed it in settings and on the word today in calender. :banghead:
jacksparr0w said:
I have started using the Helvetica font style as well now and I have not noticed the artifact/corruption at all yet however If I do I will be sure to post it in this thread.
Edit: issue still exists but not as prevalent. I noticed it in settings and on the word today in calender. :banghead:
Click to expand...
Click to collapse
I've tried messing with fonts and sizes myself from the very beginning and it did not help. In fact, changing the font was what caused me to look carefully at the text on the screen and that's when I first started to notice the problem.
I've noticed that it comes and goes in waves... Once it happens, it happens a lot and is more severe. Then, it kinda stops, or is so subtle that it's not noticeable.
Here's a bunch more with various fonts and sizes.
I wish there was a way that we could solve this issue without having to take the phone back... I am so surprised that not many users are reporting this issue, maybe they are not noticing it on there galaxy s3.
Here's an update from me. I received my replacement phone last night and have set it up the same way as my first phone. Same apps, same everything. I used it all night last night, and all day today. So far, so good. No font corruption at all. I got the LG2 update this morning, so I have tried both LF9 and LF2 on the new phone. It's still a little too early to call, but I think this phone won't exhibit the font corruption. Just wanted to let you guys know in case you are near the end of your return period and have a chance to get a replacement phone.
On another note, the old phone had two dead subpixels. One red, one green. The new phone has a single dead blue subpixel. Blue is better, and one is better than two. I think I'll just settle. But boy, Samsung AMOLED screens just kinda suck. They feel like big power hogs and they aren't anywhere near bright enough outdoors.
EDIT: Just updated the old phone to LG2 as well and played with it for just a few minutes before I started to notice the messed-up fonts again.
It's been a couple of weeks and my new replacement phone has not shown any font corruption at all. jacksparr0w: You may want to see if T-Mobile can replace yours. Sprint did it, but I used the dead pixels as the reason for my replacement.
T-mobile here and nothing of that sort. My guess would be corrupt font packages.
-Sent from my T999 / T-Mobile Galaxy SIII