Question New Pixel-User and small big - Google Pixel 6

Good evening, I have been the owner of a Pixel 6 for about a week. Now I have noticed a small graphics error in this regard. When selecting a message (for example on Discord) small white pixels appear on the display. For understanding I also attach a short video where you can see the pixels. This is not only on Discord. I also notice it on Telegram for example....
The bug bothers me a lot as a perfectionist. Is there any way to fix this bug?
I would also be happy to receive any other tips about my Pixel 6. I have already loaded a custom kernel, which I am very happy with. But the error was also present before loading the kernel. As I said before, I'm happy to take tips and tricks here as well. For example, I was also advised against a custom ROM. Is that really useless or can I get more experience and performance out through another Rom?

Took me a while to spot it. I might be wrong, but I believe that's a feature, not a bug. It's similar to the animation that appears when you plug in the charger and in some other places around the OS.

gnite6 said:
Took me a while to spot it. I might be wrong, but I believe that's a feature, not a bug. It's similar to the animation that appears when you plug in the charger and in some other places around the OS.
Click to expand...
Click to collapse
Your guess can be right.
I hate this "feature", haha.

Animation or the pointer circle?

Animation. Look carefully and you'll see the Pixel wave radiating out from the spot where his finger touched.
OP, this is normal, though I can understand why you might not like it.

Strephon Alkhalikoi said:
Animation. Look carefully and you'll see the Pixel wave radiating out from the spot where his finger touched.
OP, this is normal, though I can understand why you might not like it.
Click to expand...
Click to collapse
Yeah... though so. It's everywhere lol

Related

[Q] Menu button flashing issue

Hi to everyone in this forum. I've recently received as a present a new toshiba folio 100, but, since I'm experiencing an annoying menu button flashing, I've thought of it as a software problem so I upgraded the folio using the foliomod1.3c and applied the rotate patch and also the 1.3c fix patch. The menu still flash with no apparent logic. I've tried to kill all applications running and it's still there. It seem to come up and down at random. I ask to all in this forum: do you believe it's a hardware issue or is a software issue? Because if it's a hardware issue I'm going to try to have a new folio from toshiba. I'm overall very pleased with the work that Dexter made to make the folio an usable machine but this flashing is driving me crazy. I use the folio basically as a portable scientific pdf reader so I need to concentrate on what I read and this flashing is really annoying. I would like very much to thank you all in this forum in advance for all the suggestion/help you could provide.
use my "foliobuttons" app
teknoraver said:
use my "foliobuttons" app
Click to expand...
Click to collapse
I have a request that serve All those who suffer MENU crazy button .
Is it possible to prepare application you can setting ON/OFF the MENU button
Most of the time useless button.
sometimes button jump after 10 minutes, sometimes after an hour
Usually I fix the problem by changing the settings with FolioButtons 1.1.
If you could add to FolioButtons on/off operation for menu Buttons was the best.
Hi teknoraver,
Can you add enabled/disabled menu button in foliobuttons application ?
flashing on...
teknoraver said:
use my "foliobuttons" app
Click to expand...
Click to collapse
I am pretty desperate about this issue, because none of the methods seem to help...
Right now the buttons work opposite- Menu button flashes mad and none of the other 3 responds...dont know how it happened
Just a thought- while the folio is booting up the menu button ALREADY flashes! I have zero understanding in there but isn't it a process that loads / starts early in the line?
I appreciate everyone's effort trying to solve this bug as it makes this handy tool a useless pile of crap.
I was wondering how many folio users are suffering of this crazy buttons madness.
Mine was crazy from the very beginning; I sent it back for repair and toshiba only did a firmware restore... Nothing changed at all!
It makes my folio almost unusable!
bye bye crazy buttons
After two weeks of testing and a complete breakdown of my folio100, I finally find the problem or just crazy buttons and freezing of the screen.
I drag a thickness in the screen in the bottom right corner of the screen to isolate the audio connector and it works better than a miracle again.
The only downside is that the screen comes out slightly from the slot but nothing really bad.
The thickness I put slightly too big or-1.4 mm I'll Demount next week to put a finer and I'll try to take pictures in passing.
Note however that the loss of waranty is innevitable.
Sorry for my bad english ;-)
I think it's a hardware issue and even a build quality issue.
If i hold my folio at the side of the buttons, i get the flashing buttons problem (even the foliobuttons app will not help), if i hold it at the other side, i've got no problems at all.
Do you have an animated background? Because I saw that some people had this issue with an animated background...
Hi Mshr73, nice first post indeed
Could you post some pictures of what you did?
Mshr73 said:
After two weeks of testing and a complete breakdown of my folio100, I finally find the problem or just crazy buttons and freezing of the screen.
I drag a thickness in the screen in the bottom right corner of the screen to isolate the audio connector and it works better than a miracle again.
The only downside is that the screen comes out slightly from the slot but nothing really bad.
The thickness I put slightly too big or-1.4 mm I'll Demount next week to put a finer and I'll try to take pictures in passing.
Note however that the loss of waranty is innevitable.
Sorry for my bad english ;-)
Click to expand...
Click to collapse
seems to get better...
I really don’t want to be too quick on this, but Dexter’s 1.4 seems to bring relief to this issue - for 2 days I have been running this mod the menu button stopped flashing!!
Any similar impressions on this?
vietnamibalzsam said:
I really don’t want to be too quick on this, but Dexter’s 1.4 seems to bring relief to this issue - for 2 days I have been running this mod the menu button stopped flashing!!
Any similar impressions on this?
Click to expand...
Click to collapse
No way pal, I guess I'm in the opposite situation. It still happens to me, and sometimes I think it even got worse... well, I can always look at crazy keys as a "special feature" that no other tablet will have!!!
I just tested without thickness under the screen, with foliomod 1.4 and after a few hours I again the problem of crazy buttons.
Mshr73 said:
After two weeks of testing and a complete breakdown of my folio100, I finally find the problem or just crazy buttons and freezing of the screen.
I drag a thickness in the screen in the bottom right corner of the screen to isolate the audio connector and it works better than a miracle again.
The only downside is that the screen comes out slightly from the slot but nothing really bad.
The thickness I put slightly too big or-1.4 mm I'll Demount next week to put a finer and I'll try to take pictures in passing.
Note however that the loss of waranty is innevitable.
Sorry for my bad english ;-)
Click to expand...
Click to collapse
Well, I just finished dismantling e reassembling my Folio. Following your hint, I cut a piece of paper and put it between the audio connector and the back of the screen (yes, it was metal vs metal). I'll see whether it's gonna work or not. Crossing fingers for now.
Not that I'm so confident in leaving a piece of paper stuck right where the DC input is .
BTW, did you try with a smaller thickness? Even if this is the problem, I'm wondering whether a piece of paper would be enough or not.
thyself can someone. post pictures of before and after details?
we will be much appreciated
i didn't have the crazy buttons issue this far in 2 weeks, just my home butten needs to be pressed harder. I'm pretty sure it's hardware related, i read often that users experience it when changing from an warm room to a colder one, or in regions where its verry humid(some circuit closes maybe...). so Mshr73 is on the right way as far as i can tell.
Dexter's 1.4
^Sbk79^ said:
No way pal, I guess I'm in the opposite situation. It still happens to me, and sometimes I think it even got worse... well, I can always look at crazy keys as a "special feature" that no other tablet will have!!!
Click to expand...
Click to collapse
Really sorry mate, I hope it will solved this for others too...
Anyhow, it is so disturbing, that I was already considering to send the tablet back to Toshiba...
I'll try to do this weekend if I do not have too many customers. I post the result Monday.
Mshr73 said:
I'll try to do this weekend if I do not have too many customers. I post the result Monday.
Click to expand...
Click to collapse
I'm looking forward to your pictures, too... because my trial simply didn't work.
I tried with both a single piece of paper and then with 2 pieces wrapped in tape. I put these spacers between the back of the display and DC/audio connector.
In both cases, the crazy keys phenomenon started to happen after 15-20 minutes of usage.
In most cases, it starts to show when I unlock the device. As soon as I unlock it, home and menu buttons light up with no apparent reason and go crazy for 10-30 seconds.
Then, I even tried to loosen just a little the screws (I read, somewhere in the forum, of a guy who said that he solved his crazy keys and screen lag problems this way). I mean, all screws are now locked but not too tight. Well, I have to say that I don't have any screen lag anymore (I even removed the piece of paper, from the battery area, which used to solve the issue before) but crazy keys still happen. I'm going slightly mad
^Sbk79^ said:
I'm looking forward to your pictures, too... because my trial simply didn't work.
I tried with both a single piece of paper and then with 2 pieces wrapped in tape. I put these spacers between the back of the display and DC/audio connector.
In both cases, the crazy keys phenomenon started to happen after 15-20 minutes of usage.
In most cases, it starts to show when I unlock the device. As soon as I unlock it, home and menu buttons light up with no apparent reason and go crazy for 10-30 seconds.
Then, I even tried to loosen just a little the screws (I read, somewhere in the forum, of a guy who said that he solved his crazy keys and screen lag problems this way). I mean, all screws are now locked but not too tight. Well, I have to say that I don't have any screen lag anymore (I even removed the piece of paper, from the battery area, which used to solve the issue before) but crazy keys still happen. I'm going slightly mad
Click to expand...
Click to collapse
Well ... with a piece of paper the problem Come back.
I handed a piece of cardboard and the problem disappears.
I think that to raise the screen to solve them but I'm still not 100% sure.

SMOLED burn in problems?

Is anyone else worried about the burn in problems like the original moled had? My vibrant had it bad... Please don't tell me its not an issue with the original sgs screens, type in google and you will see a lot of complaints on this topic, and my screen is burn in galore. Just wondering if this new screen will suffer from similar problems or if samsung recognized and corrected this issue?
Sent from my SGH-T959
I have burn in on my nexus one right now. Status bar is burnt in, and the keyboard is burnt in. Yes the galaxy s2 will likely do it too.
RogerPodacter said:
I have burn in on my nexus one right now. Status bar is burnt in, and the keyboard is burnt in. Yes the galaxy s2 will likely do it too.
Click to expand...
Click to collapse
Wow, really? I got my Desire (AMOLED) for more than a year now and I can't notice anything.
Zero burn-in after a year's heavy use of my SGS1 - just leave the no activity timeout to 5 minutes or less and you'll be fine.
cTrox said:
Wow, really? I got my Desire (AMOLED) for more than a year now and I can't notice anything.
Click to expand...
Click to collapse
I had burn in after the first month of my nexus. About all people have it, you just haven't noticed it yet.
I see two possibilities here. Some people notice it more, some people based on their usage suffer from it more. I got the N1 when it released for AT&T, dont remember when exactly that was, somewhat more than a year? I'm just now getting to where I notice some burn in but it seems slight to me, not an issue now. Dont know which way I fall in my first observation but I can say that given enough time I think that most people will notice some burn in, how much time, I dont know. I suppose the bottom line is how how much time you spend with a device and will you move on before you get to where burn in becomes an issue to you with your usage. Thats a tough question to answer.
Nine times out of ten burn in on a mobile would be from the status bar. So if you're worried just download and use Go Launcher and set the slide up gesture to hide and show it.
That's interesting people with lcd displays have burn in as well... Well my status bar is permanently there, half the icons on my desktop are also burnt in, had my vibrant since it first came out, its set to 30 sec timeout and auto bright. So do amoled displays just have it worse or is it about the same?
Sent from my SGH-T959

Weird Flicker when turning on the screen?

Hi everyone!, I'm having this really odd issue with my S2. I've only had it about a week now and this could have been happening all along though I didn't notice it.
Basically If the screen is off and I hit the power button is has this really slight flicker as the screen comes on. It's almost like a single line down the screen right before the wallpaper appears. It's also right-justified on the screen and always in the same spot.
Has anyone else had this issue? It can be reproduced by simply hitting the power button to shut the screen off then hitting it again to turn it on.
Thanks!
Edit: Also the screen doesn't always fade on. 3/5 times it will just "instant-on" where I'll hit the power button and it will instantly show the lock screen tile instead of "fading" into it. Does this happen to anyone else or does it ALWAYS fade in?
I'm probably just being paranoid but I'd rather replace the phone quickly to avoid actually sending it to manufacturer.
Thanks again!
You should take a video of it so we can see if it is normal. I don't see what you describe, and not sure the phone is supposed to "fade in" to the lock screen. Mine is always instant on.
I once flashed to Litening ROM and it had that flicker (lightning style) as a feature I guess, is it the same problem OP stated?
Regards.
Saw it once two days ago, vertically on the extreme left of the screen. Haven't seen it since, but it was very rapid - blink-and-you'll-miss-it job. Can't say it worries me. On Revolution FWIW.
B3311 said:
Saw it once two days ago, vertically on the extreme left of the screen. Haven't seen it since, but it was very rapid - blink-and-you'll-miss-it job. Can't say it worries me. On Revolution FWIW.
Click to expand...
Click to collapse
sorry I can't take a video since this is the only device that I own that is capable of taking video.
anyway, yeah - it's really quick. And it's vertically down the screen. I kind of assumed that it was the backlight turning on but I'm pretty certain that happens on the sides right?
Right now it's 10:00 and this issue happens right where the "1" is on the clock at the top of the screen. So starting from that 1 all the way to the bottom.
Again it's REALLY fast - but it's noticeable, I'd have no problem showing it to someone in front of me. It just looks like a single line about the same width as the "1" as well. It almost seems like the one tiny line is showing before the rest of the screen, like if the screen were a "loading process" that line would be the first thing to appear before the rest gets backlit.
Not sure if it matters but it's the model I9100M from Virgin, just incase they are made differently somehow.
This phone has no backlight. The LED's are all individually lit.
Ryne said:
sorry I can't take a video since this is the only device that I own that is capable of taking video.
anyway, yeah - it's really quick. And it's vertically down the screen. I kind of assumed that it was the backlight turning on but I'm pretty certain that happens on the sides right?
Right now it's 10:00 and this issue happens right where the "1" is on the clock at the top of the screen. So starting from that 1 all the way to the bottom.
Again it's REALLY fast - but it's noticeable, I'd have no problem showing it to someone in front of me. It just looks like a single line about the same width as the "1" as well. It almost seems like the one tiny line is showing before the rest of the screen, like if the screen were a "loading process" that line would be the first thing to appear before the rest gets backlit.
Not sure if it matters but it's the model I9100M from Virgin, just incase they are made differently somehow.
Click to expand...
Click to collapse
Hmm, not the same problem as me - certainly nothing to do with the time here - it was in the afternoon when it happened with me, and my lockscreen clock's in 12 hour format. Clock's also at the bottom of my screen.
Been trying to reproduce it, and can't.
B3311 said:
Hmm, not the same problem as me - certainly nothing to do with the time here - it was in the afternoon when it happened with me, and my lockscreen clock's in 12 hour format. Clock's also at the bottom of my screen.
Been trying to reproduce it, and can't.
Click to expand...
Click to collapse
No no, I wasn't saying that the clock had anything to do with it, I was just trying to describe where the line appears on screen. I was also talking about the clock that appears at the very top, not the one on the lock screen. If I just continually tap the power button on and off I can see the "line" appear every time exactly in that spot.
It's pretty noticeable, unless you have the phone away from you - so if you don't see it then it probably isn't happening.
Does anyone think I should return this and get another? I don't really want to run into issues later and have to send to manufacturer. Is this problem big enough that I could get it replaced without issue?
Thank's for the replies!
Sorry, misunderstood. Definitely not my problem, I have no clock in the status bar.
If it happens every time, I'd probably return it if I was you - could be the precursor of something more serious.
Hi again, Thanks for the replies. I realized today that the issue is really only noticeable if you're in a dark room. Even in a semi-lit room it's almost unnoticeable which is probably why I hadnt seen it thus far.
If anyone wouldn't mind flicking the lights off and taking a look I'd appreciate it. If not I'll just return it.
thanks again forum!
I experience it too (at least I think we are talking about the same thing)..it's like it's stuttering and lagging after being in standby. So the first time it renders the lockscreen, the first few frames seem to be rendered at a different pace. If you turn the screen on after a good break, it'll likely do it, but after a few times in a row it instantly shows the screen.
Perhaps it relates to how big the wallpaper for the lockscreen is. I'm not sure, but I've had some huge 2mb pictures set as wallpapers for the lockscreen, and afterwards I think I decided to select a smaller image. I don't know if it was just a placebo effect, but anyways..it still does it with my current picture. I don't really care. You could try a different lockscreen from android market and see if it helps, but I think every SII suffers from this.
I have this exact issue too and it really annoys me! I also bought the phone from Virgin if that is relevant. It's a white streak on the left of the screen for me and only happens every so often. So what's the prognosis? A software fault? Hopefully fixed in a subsequent firmware update? Or a hardware fault worth repairing?

Nook tablet remotely hacked?

My nook tablet was opening apps like Facebook and google search and typing unusual letters in the search and status boxes. Anyone seen anything like this? It honestly seemed like the device was being controlled remotely. I wasn't even touching the device and it was trying to type letters. My device has been rooted for about two weeks. I've not seen anything like this until tonight.
What was your battery charge? There are reports of the touchscreen acting weird when the battery is low.
yea, sounds more like a glitch in the touch screen. this happened on my phone. I would warranty it. Make sure you unroot first
It sounds like a defective unit... I have a Droid X that does the same thing; started happening about a month or two out of warranty. I've factory reset / SBF'd it a million times and it still happens, rooted or not.
For me, it seems to happen more frequently when the screen is dirty (but also happens when perfectly clean), and especially bad if I am wearing clothing that generates static electricity (fleece and other synthetics). Makes me wonder if the screen isn't grounded properly.. the phone has a lot more flex in the chasis than it should and sometimes flexing it in just the right way will make the problem stop.
Thanks
Thanks much for the replies. The battery was very low and I was sitting in a chair that could generate static electricity. Also noticed little bits of dog hair caught between the case and the screen. Not sure I'm going to return the unit just yet. It could have been a fluke. The only time I've seen a machine act like that is when someone controls a server at work remotely. It was really strange and seemed like a program was attempting to type on its own.
One other caveat is that I had installed Aurora on the tablet earlier in the night. It's a browser by Mozilla in development. It was running really sweet so I don't think that had anything to do with it. I did notice that the tablet was locking up on a couple pages and really sluggish for a bit while using the default browser. It then responded fine until the ghost took over.
One other question if anyone is still listening: if this happened to you did the keyboard come up? It didn't appear when the letters were being typed in my case.
I was thinking a cover and possibly a shield may be in order. I've got a year, so it if happens again even one time I'm going to return the unit- after unrooting of course.
My Nook Color will do this as well when it has been zapped by static electricity and when there are a bunch of finger prints all over the screen (usually when the finger oil gets built up around the edges of the screen it starts).
A good wipe down with a microfiber cloth (with the screen off) fixes it for me. Granted this is Nook Color and not my Nook Touch we're talking about, but I figure the behavior could be similar.
Good luck!
Merrell
Weird, I could swear there was a thread about this, but now I can't find it for the life of me.
Anyway, it's a known issue- no need to panic and return the NT.
When the battery gets critically low, sometimes the NT will seem to have a mind of it's own and everything you describe starts happening. Apps open themselves, random text types itself, touchscreen completely unresponsive, etc.
I've seen exactly the same thing, and also at first wondered if it was a remote hack. Then I noticed the pattern that it's only during extreme power lows.
Just recharge to at least a minimal level and there's no problem.
zaptoons said:
Weird, I could swear there was a thread about this, but now I can't find it for the life of me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1431091
Ah. I knew I posted there, but thread is strangely missing from my 'find all posts..' results.
macrossmerrell said:
My Nook Color will do this as well when it has been zapped by static electricity and when there are a bunch of finger prints all over the screen (usually when the finger oil gets built up around the edges of the screen it starts).
A good wipe down with a microfiber cloth (with the screen off) fixes it for me. Granted this is Nook Color and not my Nook Touch we're talking about, but I figure the behavior could be similar.
Good luck!
Merrell
Click to expand...
Click to collapse
Same thing happens to me but I only switch the screen off and on and then it goes away.
As has been mentioned, charge it, clean the screen, wash your hands. This should take care of the "autogibberish". As far as opening software... do you mean that it is opening foreground applications? Or that software will just load in the background? If the latter, this is NORMAL behavior of Android -- it will load software into memory so that it is instantly available when you try to run the software. If the former, probably related to the dirty screen.
I do NOT believe that this is a hardware defect. It rather is a side-effect of a LARGE touch surface. The bigger the touch surface, the more likely it is to be subject to random static charges.
Whoops didn't realize how this thread was!

Repeated burn-in issues.

Hello, recently i sent my phone to warranty because of serious screen burn in issues, they replaced my sceen, which had more light bleeding issues, but i wouldnt mind that, as the burn-ins were gone, but to my surprise, yesterday after about 3hrs of constant on screen texting in whatsapp, the burn-in started appearing on the new screen, i am seriously pissed off, i really like this phone overall with the features it offers and so on, but the quality control... Wtf LG.. I now have bought a phone which i should just send for warranty repairs after a period of time?
Just wanted to share my experience with you, i still have a gpad 8.3 thats is still rolling on the latest 7.1.1 and has no quality issues and a robust metal build whatsoever, but this is just annoying...
Im sorry to hear about your issues with g5. Its a great device, whats wrong with your screen? Light bleeding whad do this mean?
Gmobilize said:
...Just wanted to share my experience with you,..
Click to expand...
Click to collapse
If you want to do something for us, try to use the search engine first until you start a new thread!
There are a lot of threads around here which has described screen ghosting on LG devices!!!
See here:
1.) (English) ->https://forum.xda-developers.com/lg-g5/help/lg-g5-screen-ghosting-burn-problem-t3545769
2.) (German) ->http://www.android-hilfe.de/thema/displayflecken-nach-langem-aktiv-sein.790992/page-3
3.) (English) ->https://forum.xda-developers.com/lg-g5/how-to/panel-vs-panel-series-t3480270
4.) (English) ->https://forum.xda-developers.com/tmobile-lg-v10/help/ghost-images-screen-image-retention-t3395732
5.) (English) ->https://forum.xda-developers.com/g4/help/screen-ghosting-lg-g4-t3451879
YOU are not alone!
non-toxic said:
If you want to do something for us, try to use the search engine first until you start a new thread!
There are a lot of threads around here which has described screen ghosting on LG devices!!!
See here:
1.) (English) ->https://forum.xda-developers.com/lg-g5/help/lg-g5-screen-ghosting-burn-problem-t3545769
2.) (German) ->http://www.android-hilfe.de/thema/displayflecken-nach-langem-aktiv-sein.790992/page-3
3.) (English) ->https://forum.xda-developers.com/lg-g5/how-to/panel-vs-panel-series-t3480270
4.) (English) ->https://forum.xda-developers.com/tmobile-lg-v10/help/ghost-images-screen-image-retention-t3395732
5.) (English) ->https://forum.xda-developers.com/g4/help/screen-ghosting-lg-g4-t3451879
YOU are not alone!
Click to expand...
Click to collapse
Dont you think i am aware of this? How does it help me? I have wrote ot in threads before and i write it again, this one was about the same thing happening even after warranty repair, and the cause is a faulty panel, i am sharing my warranty experience, i dont really understand why would you post these links? How is this helpful?
i think it would be interesting for all of us to know the period when it started to happen for the first time and then when exactly after the replacement?
I for myself got the screen replaced about 2 month ago having the screen burn issue as well. Phone IME starts with 604. Since the replacement no issue for me so far..but i am not so sure if it the problem is solved with that and the screen burn in starts again after a while again......
Gmobilize said:
Dont you think i am aware of this? How does it help me? I have wrote ot in threads before and i write it again, this one was about the same thing happening even after warranty repair, and the cause is a faulty panel, i am sharing my warranty experience, i dont really understand why would you post these links? How is this helpful?
Click to expand...
Click to collapse
aking007 said:
i think it would be interesting for all of us to know the period when it started to happen for the first time and then when exactly after the replacement?
I for myself got the screen replaced about 2 month ago having the screen burn issue as well. Phone IME starts with 604. Since the replacement no issue for me so far..but i am not so sure if it the problem is solved with that and the screen burn in starts again after a while again......
Click to expand...
Click to collapse
Its indeed interesting as it really seems to not appear at the beginning, and once it shows up it starts to get more noticable over time, for example as i said, it occured after heavy using whats app for about 3hrs most of the time with auto brightness sometimes hitting the highest levels, right now i can notice the burn in, but its not at levels where it would become disturbing, ill see how it goes, if it progresses and so on..
Gmobilize said:
Dont you think i am aware of this?
Click to expand...
Click to collapse
No, it was not visible for me reading your post, that you have get all informations about LG display issue.
Gmobilize said:
i don't really understand why would you post these links
Click to expand...
Click to collapse
i want to be sure, that you can see, that this is no individual case!
Gmobilize said:
How is this helpful?
Click to expand...
Click to collapse
If you had read all of my linked threads, you should know...
...many people has this problem with different LG devices...
... it was recognized at LG G5 phones produced between march and jun. 2016 (see serial number starting with 604 up to 606)...
... there seems to be a new display without ghosting but with a little more power consumption recognized since serial number 609...
... it makes no difference witch country code your device was! all displays could be affected!
...that some users have installed "sFilter BlueLight" app to prevent this issue!
...as some users reports,it is not granted, that this issue never returns on changed displays because it seems to be a general fault...
Maybe that all this informations does not help to solve YOUR problem, but this is a forum for questions and answers ant i thought, that this informations could be helpful to know. But as it looks like,it seems that this will be for other users only!
So if you feel disturbed of me, feel free to set me to first position in top of your ignore list!
and at least: see my signature at 3.!
non-toxic said:
No, it was not visible for me reading your post, that you have get all informations about LG display issue.
i want to be sure, that you can see, that this is no individual case!
WITH
If you had read all of my linked threads, you should know...
...many people has this problem with different LG devices...
... it was recognized at LG G5 phones produced between march and Jjund 2016 (see serial number starting with 604 up to 606)...
... there seems to be a new display without ghosting but with a little more power consumption recognized since serial number 609...
... it makes no difference witch country code your device was! all displays could be affected!
...that some users have installed "sFilter BlueLight" app to prevent this issue!
Maybe that all this informations does not help to solve YOUR problem, but this is a forum for questions and answers ant i thought, that this informations could be helpful to know. Maybe only for other ons only!
So if you feel disturbed of me, feel free to set me to first position in top of your ignore list!
Click to expand...
Click to collapse
Sorry, but to me the reply seemed non-friendly, as it would be addressed to a rookie user, who hasnt done his research, maybe im wrong about your post...
But overall, yes i have seen all those threads, and unfortunatley, as i have mentioned in some other LCD display threads, the app could basically be a temp fix for the issue, when its not at a disturbing level, as its a cause of a faulty panel.
At this point where my panel has been already replaced, i cant really keep track of its model.
Gmobilize said:
Sorry, but to me the reply seemed non-friendly, as it would be addressed to a rookie user, who hasnt done his research, maybe im wrong about your post...
But overall, yes i have seen all those threads, and unfortunatley, as i have mentioned in some other LCD display threads, the app could basically be a temp fix for the issue, when its not at a disturbing level, as its a cause of a faulty panel.
At this point where my panel has been already replaced, i cant really keep track of its model.
Click to expand...
Click to collapse
Okay so lets go through this together.
A burn-in only happens with amoleds as this is permanent. We have LCD panels so we have image retention which is non-permanent.
A LCD is a liquid crystal display. Means you have a certain state of the crystals. When you apply a voltage the crystals rearrange themselves and block light. This is why we need a background illumination. Anyway once you use it for a longer period with a semi-static or a static picture (like whatsapp typing bar, google maps info boxes, keyboards etc) the crystals start to shift in their relaxed form towards another state. Blue light is due to its short wavelength energy consuming -> high voltage applied -> faster image retention.
That's why blue light filters do work to some extent. (With cf lumen and root you can adjust to use less blue instead of having an overlay draining additional energy)
This liquid crystal thingie is dependent on a lot of different parameters, that's why some get it faster and some slower. My 1,5k$ thinkpad has the same issue with the navigation bar being a persisting image after 10h+ of browsing.
TLR
So this is actually not a warranty issue. LG also returned phones unrepaired as this is the negative side of a lcd and considered standard behaviour. Go for an AMOLED the next time as they can't suffer from this, but once you have image burn-in you will never get rid of it. So doesn't really make a difference.
https://en.wikipedia.org/wiki/Image_persistence (helpful for that burn in issue which a lot of people seem to get wrong)
Cheers
lolmensch said:
Okay so lets go through this together.
A burn-in only happens with amoleds as this is permanent. We have LCD panels so we have image retention which is non-permanent.
A LCD is a liquid crystal display. Means you have a certain state of the crystals. When you apply a voltage the crystals rearrange themselves and block light. This is why we need a background illumination. Anyway once you use it for a longer period with a semi-static or a static picture (like whatsapp typing bar, google maps info boxes, keyboards etc) the crystals start to shift in their relaxed form towards another state. Blue light is due to its short wavelength energy consuming -> high voltage applied -> faster image retention.
That's why blue light filters do work to some extent. (With cf lumen and root you can adjust to use less blue instead of having an overlay draining additional energy)
This liquid crystal thingie is dependent on a lot of different parameters, that's why some get it faster and some slower. My 1,5k$ thinkpad has the same issue with the navigation bar being a persisting image after 10h+ of browsing.
TLR
So this is actually not a warranty issue. LG also returned phones unrepaired as this is the negative side of a lcd and considered standard behaviour. Go for an AMOLED the next time as they can't suffer from this, but once you have image burn-in you will never get rid of it. So doesn't really make a difference.
https://en.wikipedia.org/wiki/Image_persistence (helpful for that burn in issue which a lot of people seem to get wrong)
Cheers
Click to expand...
Click to collapse
Thanks for the interesting article on LCD artifacts, however, i wanted to say some things:
As my for my first panel, that got replaced, image retention was pretty hard, as when the phone got warmer, it became really disturbing and barely usable as the keyboard and status bar started to ghost on grey background apps such as xda, the only way was to let it cool down and wait till everything disappears, as soon as i started using my phone a bit longer, the problem resurfaced very quick. So it clearly wasnt a normal reaction. Just to add, no CF.lumen like apps were able to help back then.
My current replaced panel is showing only minor signs of this, it becomes more apparent on longer usage times with the same elements and the ghosting is barely visible with not so intense usage, so i hope that this wont eventually get stronger as before. As it would seem to be a natural usage reaction, i still consider this an issue however, cause none of my previous LCD phone had anything like it, not even my LG Gpad 8.3. So im gonna try to apply warranty again if needed, as repair services seem to be pretty helpful in my country at least, as long as they have spare panels in stock.
And about amoled, i think ill pass that for a while, i have seen enough samsung demo units in stores have serious homescreen burn-ins.
With LG G5 the quality really seems to be an issue, yes there maybe lucky people with good units and so, but overall it is pretty disappointing, as feature and hardware wise i really love this device.
lol
I see the so called expert stopped responding like a retard. I had the same problem I just lgup and flashed stock all over again about 4 times and it started to show improvements. As of now I got rid of the burnt images on my lcd

Categories

Resources