Pixel 3 screen flash - Google Pixel 3 Questions & Answers

Didn't see this posted here yet, but forgive me if I missed it.
Trying to find out if anyone has seen or heard of any acknowledgement from Google regarding this. My new Pixel 3 (Verizon; non XL) since day 1 has had an annoying issue with the screen flashing when ambient screen engages. I have my settings with alwayson set to off, and new notifications set to on. If the screen is asleep and I get a text or any notification, the ambient screen wakes and will initially make the entire screen flash white very quickly.
I do not get a flash of the screen in any other scenario when the phones on, it only seems to be when the screens totally asleep and the ambient screen wakes. I can unlock the phone or hit the power button to fully wake the phone to my home screen with no flashing. Its not every single time, but its very often. I do notice sometimes when it doesn't flash the whole screen, the time or text on the ambient display will be at full brightness when it first wakes for a split second and then will go to the dim text Im used to seeing.
Replaced the phone through Verizon. Got another brand new one with the same exact problem. This one even flashes on reboot occasionally just before the white "Google" screen pops up. Google had me send them a bug report this time and are supposed to be having their dev team look at it.
WHY.

Mine did it once
Sent from my Pixel 3 using Tapatalk

I've also now noticed mine will flash in Instagram when I "like" something lol. Just the picture flashes within the app itself in that case, not the whole screen. Such a weird thing, that may have something to do with the app on the new pixel? I don't even know anymore.

I just saw the white flash. It was only for a few ms but it looked like a full brightness white flash on the whole screen. I had just set my phone down and I think the AOD was coming on.
Weird.

Yeah I have a feeling this is happening on way more devices than we're reading about. I hope it's addressed. Sometimes my notification audio cuts out real quick too. Hoping it's just all memory related.

I have this weird kind of screen flickering on my device as soon as I use the fingerprint area to turn the phone on. It is very faint and fast but its like static lines for half a second when the screen comes on??

Archangel said:
I have this weird kind of screen flickering on my device as soon as I use the fingerprint area to turn the phone on. It is very faint and fast but its like static lines for half a second when the screen comes on??
Click to expand...
Click to collapse
Strange, I haven't had any issues like that using the fingerprint reader or just hitting the power button. Mine are all directly related to ambient screen waking.

My Pixel 3 is doing the same thing when I unlock it. Flashes like taking a selfie... I have even looked for the selfie to no avail.
It does not do this regularly, very random.

edster00 said:
My Pixel 3 is doing the same thing when I unlock it. Flashes like taking a selfie... I have even looked for the selfie to no avail.
It does not do this regularly, very random.
Click to expand...
Click to collapse
Same here. Sometimes when I tap the screen to wake it up, it flashes. Just did it a minute ago before I wrote this.
Sent from my Pixel 3 using Tapatalk

I just charged the Pixel face down; during the charge I picked it up to check the progress and I got the screen flash ~2X out of 10.

edster00 said:
I just charged the Pixel face down; during the charge I picked it up to check the progress and I got the screen flash ~2X out of 10.
Click to expand...
Click to collapse
Report it to Google. I feel like it's something they're aware of (I hope) but support certainly isn't saying so if they are.

I saw a post on Android Police about bug trackers and read in some of the comments that people were having problem with screen flashing. Some of them said it was related to the always on display. Mine was flashing like white static lines. But it was only for half a second when you turn on the screen and it didnt happen every time, it was random. I turned off the AOD and it never happened again. Kinda sucks cause I like AOD. But that tells me it is a software problems and not hardware.

I turned off AOD too, for 1 day; the next day I turned AOD back on. I have not had a screen flash since (a few days now).

edster00 said:
I turned off AOD too, for 1 day; the next day I turned AOD back on. I have not had a screen flash since (a few days now).
Click to expand...
Click to collapse
Try rebooting. I bet it's still happening you just may not be noticing. I've had my AOD off for a while and as soon as I turn the new notifications option it comes back. Not every time but still often.

I'm having the same issue, doesn't happen all the time but I can reproduce it usually by unlocking the device, locking it then when ambient display comes on, unlock it and the screen flashes/flickers. I've only managed to do it with ambient screen set to always on.
I've RMA'd this morning so I'll report back when the new phone comes.

I hope you RMA's for other reasons too because it is likely that you will get a phone with the same flickering problem. I think it is a software issue esp since it goes away after we turn off AOD.
steslatt said:
I'm having the same issue, doesn't happen all the time but I can reproduce it usually by unlocking the device, locking it then when ambient display comes on, unlock it and the screen flashes/flickers. I've only managed to do it with ambient screen set to always on.
I've RMA'd this morning so I'll report back when the new phone comes.
Click to expand...
Click to collapse

Archangel said:
I hope you RMA's for other reasons too because it is likely that you will get a phone with the same flickering problem. I think it is a software issue esp since it goes away after we turn off AOD.
Click to expand...
Click to collapse
I just find it strange that people are having the flicker in different scenarios, like mine is only when ambient is set to always on but other people are having the issue when it's set to double tap etc. Anyway I guess I'll see when the new phone comes.
Sent from my Pixel 3 using Tapatalk

Yeah let us know please once you get the new phone. It seems like it is hit or miss with people so you might get lucky and avoid it.
steslatt said:
I just find it strange that people are having the flicker in different scenarios, like mine is only when ambient is set to always on but other people are having the issue when it's set to double tap etc. Anyway I guess I'll see when the new phone comes.
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse

Quick update. My new phone arrived this morning and I've managed to get the screen to flash once so far where as my old one would do it 8 times out of 10. I feel like this is a poor display hardware problem rather than software.

I believe or rather am hoping that because it only happens when you turn on AOD that it is a software issue and not a hardware one. The only way something will be done is enough people complain on a bug tracker.
steslatt said:
Quick update. My new phone arrived this morning and I've managed to get the screen to flash once so far where as my old one would do it 8 times out of 10. I feel like this is a poor display hardware problem rather than software.
Click to expand...
Click to collapse

Related

Turn off Fully Charged notification

I hate that notification because I use my phone for my alarm and it lights up in the middle of the night. Has anybody figured out a way to turn that notification off? I have looked and not found anything on the phone or in the forums.
If you can't find a way to suppress the notification, do what I do...turn the phone over. If you don't have the Body Glove case that lifts the screen off the furniture and are concerned about scratches, put it on a paper towel or similar item to protect it. I use a wash cloth.
would also like to know how to turn that stupid notification off - software based and not using a towel though
I don't know much yet but I was digging around in root explorer and if you go to /system/media there are a bunch of .qmg files for battery related stuff, and two of them are named chargingwarning.qmg and Disconnected.qmg. Could one of these be the file for the fully charged notification?
rockr09 said:
I don't know much yet but I was digging around in root explorer and if you go to /system/media there are a bunch of .qmg files for battery related stuff, and two of them are named chargingwarning.qmg and Disconnected.qmg. Could one of these be the file for the fully charged notification?
Click to expand...
Click to collapse
Probably not because the notifications are all text, and QMGs are the 3d files used at boot-up. Most likely those animations are used in the battery meter that is displayed when the phone is off (turn your phone off and plug it in).
This won't help with the light, but the sound can be fixed.
http://forum.xda-developers.com/showthread.php?t=737147
seriously? we are all STILL dealing with this? has anyone found a solution to prevent this notification from popping up?
GarciaM25 said:
seriously? we are all STILL dealing with this? has anyone found a solution to prevent this notification from popping up?
Click to expand...
Click to collapse
It is confirmed fix in the 2.2 release - at least the JI6 build we are all playing with. They moved it to the notification bar.
Bumpage!
Been a lurker but just recently got my Captivate. Great forum here! Looking forward to contribute as well.
Well my issue with the "Fully Charged" battery notification is the display will stay on for the entire night. When I wake up in the morning, I see the phone's display on with the notification. Is this normal? I think this was happening just recently but I can't remember. Shouldn't the display turn off after the set amount time of inactivity? Thanks.
Nevermind, I figured it out. Within the development settings, the option to never allow the phone to sleep while plugged into the usb was checked. I wonder why that was checked.
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok, I THOUGH disabling that option would put the display to sleep when the notification comes on but it doesn't. =(
Is this normal behavior? The screen stays lit after the notification is on? The only reason why i'm concern is if I'm plugging it in night after night and it's on that particular screen for hours at a time, there might be some burn in issues.
dawei213 said:
Ok, I THOUGH disabling that option would put the display to sleep when the notification comes on but it doesn't. =(
Is this normal behavior? The screen stays lit after the notification is on? The only reason why i'm concern is if I'm plugging it in night after night and it's on that particular screen for hours at a time, there might be some burn in issues.
Click to expand...
Click to collapse
Not likely. It's not a rear projection tv or a CRT monitor. Burn-in problems died with those.
miztaken1312 said:
Not likely. It's not a rear projection tv or a CRT monitor. Burn-in problems died with those.
Click to expand...
Click to collapse
Guess you haven't seen some of the demo Captivate at your local AT&T stores. Seeing the burned in images on those beautiful SAMOLED screen just kills a little bit of me.
In any case, so it's normal for the screen to take on after the message notification comes on?
dawei213 said:
Guess you haven't seen some of the demo Captivate at your local AT&T stores. Seeing the burned in images on those beautiful SAMOLED screen just kills a little bit of me.
In any case, so it's normal for the screen to take on after the message notification comes on?
Click to expand...
Click to collapse
None of the models I saw had burn-in at all. I got my phone on August 30th of this year. The phone had been on the shelves since July. But I would imagine it's normal for the screen to come on.
I got my phone only three weeks ago, so the phone sitting on display has probably been there a long time. And yeah, samoled screen can get burned in. well guess I'll have to charge it during the day time for now until I can figure out a way to disable the pop up.
Oh my worry is that the screen might be in the on state with the same image for hours while I sleep. That's something I can't leave to chance.
Sent from my SAMSUNG-SGH-I897 using XDA App
dawei213 said:
I got my phone only three weeks ago, so the phone sitting on display has probably been there a long time. And yeah, samoled screen can get burned in. well guess I'll have to charge it during the day time for now until I can figure out a way to disable the pop up.
Oh my worry is that the screen might be in the on state with the same image for hours while I sleep. That's something I can't leave to chance.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
As long as you're not using a Samsung Dock or have the Stay Awake option checked off in settings, it won't stay on. I watch my phone every night. It usually finishes charging long before I ever go to sleep (case in point, it's 3:11am, and the phone was done around 1am) and the screen always times out and turns itself off. It doesn't come back on either.
miztaken1312 said:
As long as you're not using a Samsung Dock or have the Stay Awake option checked off in settings, it won't stay on. I watch my phone every night. It usually finishes charging long before I ever go to sleep (case in point, it's 3:11am, and the phone was done around 1am) and the screen always times out and turns itself off. It doesn't come back on either.
Click to expand...
Click to collapse
Ok, yeah that's what I figured. Thanks for confirming it for me. I do have that option "not checked". Something might be preventing it to fall back asleep.
Is there any log within the file system which might keep track of system events? I might have to do a little digging around.
Thanks for your input.
dawei213 said:
Ok, yeah that's what I figured. Thanks for confirming it for me. I do have that option "not checked". Something might be preventing it to fall back asleep.
Is there any log within the file system which might keep track of system events? I might have to do a little digging around.
Thanks for your input.
Click to expand...
Click to collapse
I don't believe there's any logs, but you might have some luck installing logcat from the market and checking that after one night
Sent from my Captivate
Charged notification PROBLEM SOLVED !
PROBLEM SOLVED ! NO COST !
I saw this suggestion in another forum and it WORKS, so I'm passing it on !
Set the global notifications to SILENT.
Set the notification on Gmail to any ringtone, NOT DEFAULT.
Set the notification on messaging to any ringtone, NOT DEFAULT.
You'll still have a tone when you 1st plug the phone in to the charger, but NO tone when it's fully charged.
Where are these settings? I can't find them any where.

Can software really fix a stuck pixel?

I just got a replacement Nexus 5 which is fine except for 1 stuck green pixel just about at the centre of the screen. It's a bit annoying. I don't know if they would send me a new phone over this or if it's worth the hassle.
There are a number of apps that claim to fix stuck pixels by cycling through colours. I've tried a few for a few minutes. People in the comments have said running it overnight fixed their stuck pixels.
Does this really work? What's the principle that would allow a stuck pixel to become unstuck?
If I want to try this should the screen be set to maximum brightness or not? I'm a little concerned that leaving the phone plugged in with the screen on at max brightness may cause damage to the phone or screen due to overheating. Is this something I should be worried about?
Thanks.
tmagritte said:
I just got a replacement Nexus 5 which is fine except for 1 stuck green pixel just about at the centre of the screen. It's a bit annoying. I don't know if they would send me a new phone over this or if it's worth the hassle.
There are a number of apps that claim to fix stuck pixels by cycling through colours. I've tried a few for a few minutes. People in the comments have said running it overnight fixed their stuck pixels.
Does this really work? What's the principle that would allow a stuck pixel to become unstuck?
If I want to try this should the screen be set to maximum brightness or not? I'm a little concerned that leaving the phone plugged in with the screen on at max brightness may cause damage to the phone or screen due to overheating. Is this something I should be worried about?
Thanks.
Click to expand...
Click to collapse
Usualy its hardware (screen itself) related so software cannot fix that.
No. In answer to your question
Sent from my Nexus 5 using Tapatalk
So what's going on with people who claim it's worked for them?
In any case, I think I'll call Google and see if I can get another replacement. Maybe third time will be the charm...
Because it can work.
Think of each pixel as 3 switches.
One red. One blue. B one green.
In your case one pixel has the green switch stuck on.
These apps are designed to force the switches to keep turning on and off.
Sometimes you can get lucky and the switch will eventually free itself after so many tries.
Sometimes it will not work no matter what.
These apps just try to get it unstuck.
Sometimes it works. Sometimes it doesn't
Sent from my Nexus 5 using xda app-developers app

Phone face down, rings, screen black...

If I have my phone face down on a counter when it rings, when I pick it up the screen is black. Not off, as I see some light, but basically dark.
I cannot see who is calling...can't get it to display.
This actually happens a lot other times. Just now, for example, I just picked it up, and turned it on with finger print. I placed it face down, and picked back up immediately...screen black.
If I happen to have it on and brush the screen across my side, it will go black.
The ringing is the realy annoying one.
Any suggestions? I'm thinking it has to do with something about the proximity sensor sensing the screen against something...but it should let it come on when it's not against something.
Is noone else having this problem? Every time my phone rings, it turns on but stays black. I never know who's calling unless I answer.
I don't know what to do with it. Very annoying.
Hoping someone has a suggestion.
You could disable auto dimming on your phone. Use Lux from Play store instead.
Planet X said:
You could disable auto dimming on your phone. Use Lux from Play store instead.
Click to expand...
Click to collapse
Do you mean Auto Brightness? If so, that is not the problem. I have it disabled and am using an app for brightness control...not automatic.
I cannot find anything in settings about 'auto dimming'.
Thanks for the suggestion though...
You're right. I mean Auto Brightness, it does Auto Dimming too . B.t.w. I don't have this issue.
Planet X said:
You're right. I mean Auto Brightness, it does Auto Dimming too . B.t.w. I don't have this issue.
Click to expand...
Click to collapse
I'm beginning to think I am the only one.
Another symptom which I am thinking is related. Sometimes when I touch my finger to the fingerprint button to wake the phone, it comes on with that dark screen for just a moment. It feels like the phone is busy, overloaded, or just slow. It will then come fully on. Also seems like maybe it is just in deep sleep and slow to wake up. If I turn it off and back on, it is instant.
I check memory and it always has just under 1.5 GB free.
I don't know what to think, but it is very annoying. I thought about chalking Huawei support, but I'm sureo they'd just say to hard reset.
I do have a lot of apps on the phone, but with that much free memory I wouldn't think that should be a problem.
Another interesting thing related to screen dark: I can have the setting for display to not turn off if no actdivity to 10 minutes, and it still goes off after less than a minute. (Going off is different from the topic of this thread where it is near black/dark, but not off).
I discovered this while trying to use Huawei backup. Thinking of doing a Factory Reset. Instructions say to not lock the screen, so I'm trying to keep screen on w/o my having to hold the phone the entire backup.
This overall topic is making me pretty unhappy with the phone, which I had thought was perfection when I started with it.
sigh...
I finally called Huwaei technical support this morning. They apparently know about this problem, and want me to send the phone back for repair. They expect me to be without a phone for two weeks while this is going on.
It speaks to the reason to not buy phones away from carriers, as anytime I had a problem with my Samsung, they would send out a replacement and then I would send back my old one and I would not have to be without a phone.
Pretty poor .
AN update In case anyone is following this for some reason...
Getting ready to send the phone in, I did another factory reset. I had got to wondering if maybe Gravity Box had been part of my problem. May be the case...not sure. But for now i'm not having the problem. I changed some of the settings on it when I reinstalled. I cancelled the return.
I've had the odd time when the screen is on, but not properly backlit. You can just about make out the screen, but then the backlight seems to rectify itself. It isn't just the Mate 9, but the P10 and probably other phones. Doubtful a hardware issue I'd have thought - rather a software glitch.
The P10 just got an update earlier this week (yet still with April security patches) but my Mate 9 hasn't had an update in months.

P30 fingerprint picture showing up often

When my P30 is placed on the table (I don't notice when in my pocket, duh ) it lights up the "Place finger here" in the bottom.
Does anyone have an idea why that happens?
It's not like the table is moving or anything to trigger a read, so why is it showing?
Could it result in burn-in?
I have same problem, it could result in burning, but i have no idea why it shows up
It is annoying! I've turned it off in favor of a PIN to prevent burn-in
I wrote and email to Huawei and the replied rhat IT shouldnt result in burn-in.
And if I didn't want to risk it, I could turnering it off.
Not really a valid answer...
ZigmaDK said:
I wrote and email to Huawei and the replied rhat IT shouldnt result in burn-in.
And if I didn't want to risk it, I could turnering it off.
Not really a valid answer...
Click to expand...
Click to collapse
I'm surprised their IT is not aware of the latest OTA from last night, which is version 9.1.0.124(C431E3R2P2) and fixed the problem. The annoying fingerprint symbol no longer randomly appears but only if I move my phone (and in the pocket it would not show as the proximity sensor prevents that from happening, which I have tested).
ifonuser78 said:
I'm surprised their IT is not aware of the latest OTA from last night, which is version 9.1.0.124(C431E3R2P2) and fixed the problem. The annoying fingerprint symbol no longer randomly appears but only if I move my phone (and in the pocket it would not show as the proximity sensor prevents that from happening, which I have tested).
Click to expand...
Click to collapse
That didn't solve it for me. It still shows up.
I still use the screen protector that was on the phone when I bought it. Did you remove yours?
ZigmaDK said:
That didn't solve it for me. It still shows up.
Click to expand...
Click to collapse
What's the interval like?
ZigmaDK said:
I still use the screen protector that was on the phone when I bought it. Did you remove yours?
Click to expand...
Click to collapse
I've kept it on. Normally I'm not the kind of guy who uses one, but this was placed on very well I still find the screen to be excellent, it does not bother me. Have you immediately pulled yours off or can you describe a before/after experience?
ifonuser78 said:
What's the interval like?
I've kept it on. Normally I'm not the kind of guy who uses one, but this was placed on very well I still find the screen to be excellent, it does not bother me. Have you immediately pulled yours off or can you describe a before/after experience?
Click to expand...
Click to collapse
I just tested at my desk and it came up 9 times in a minute.
I still have the protector on. Never removed it as it is placed nicely.
ZigmaDK said:
I just tested at my desk and it came up 9 times in a minute.
I still have the protector on. Never removed it as it is placed nicely.
Click to expand...
Click to collapse
I have version 9.1.0.124(C431E3R2P2) and this problem is solved. Fingerprint symbol shows up only when i move the phone.
I have 9.1.0.124(C431E4R2P2) and the symbol sporadically lights up for me as well
matjazzzz said:
I have version 9.1.0.124(C431E3R2P2) and this problem is solved. Fingerprint symbol shows up only when i move the phone.
Click to expand...
Click to collapse
Is that the standard P30 you have on .124? My P30 is on .113.
I have this issue too, the symbol shows up several times a minute. I have seen others mention elsewhere that this could well be a hardware issue?
I'd just assumed this was a software issue but if it is hardware then it may be time to return it?
arsenal74 said:
Is that the standard P30 you have on .124? My P30 is on .113.
I have this issue too, the symbol shows up several times a minute. I have seen others mention elsewhere that this could well be a hardware issue?
I'd just assumed this was a software issue but if it is hardware then it may be time to return it?
Click to expand...
Click to collapse
Yes, it's standard version... After I bought it (first day), phone was updated with this version ...
After I switch off the phone (and put it on the table), symbol shows up for a few seconds, then disappear until I move the phone ..
Maybe you should try first with .124 version .. ?
Hi
My p30 is on 115 update and still has the same problem
Anyone try without or with a different screen protector?
I have found some kind of solution, but by some reason it does not work all the time. Settings- Smart assistance- Shortcuts & gestures - wake screen - Double-tap screen to wake. Activate that option and reboot the device.
But as I can see, that light might be used as some kind of notification light since it blinks when there is something, like e-mail, message and other things that need attention. When there is no internet connection it is not blinking until you move it.
All of the above are just my personal observations and I don't insist that they are 100% correct.
Having this act as a notification indicator isn't a bad theory, although the frequency of it appearing seems wrong for that kind of use.
Personally, I'm bummed at the lack of notification light, something I had been relying on for years with all my previous phones. I might end up taking advantage of the OLED screen and just make it keep the screen on instead.
My phone updated from 111 to 121 today (I guess we have different build numbers in North America), I still see it flashing from time to time while it sits on my desk.
Update: I tried with a tempered glass screen protector and now it doesn't show up unannounced anymore.
I think it is an issue with sensitivity of the screen.

Question Screen Flicker During Unlock

Every time I unlock my screen, whether it's with the fingerprint or pattern, the screen will flicker for half a second. Super annoying because it's a bright white flash.
It's not face unlock assistive lighting, as I've ensured that is turned off.
I've also tried every display setting possible, toggling things like vision comfort, comfort tone, refresh rates, display calibrations, changing wallpaper, and so on.
Really hoping this isn't a hardware issue because I'm also noticing my touches don't register all the time, unless I'm pressing the screen slightly harder. Not sure if it's my screen protector but I am left a bit concerned.
Any ideas? I've Googled this a bit and I've noticed others have the same issue but on OnePlus 6 devices for the most part, not the 9 series. If anyone has run into this before and knows a fix, I'd love to hear it, thanks!
That's how the fingerprint works. It increases the screen brightness to the max usually. It's the flaw of using that kind of fingerprint rather than sonic like Samsung. Believe it takes a picture of your fingerprint and compares vs ultrasonic gets a 3D image, the difference is in speed too, optical is faster, but ultrasonic technically more secure and does not rely on lightning conditions. I personally prefer the hardware on the back kind over both.
zymphad said:
That's how the fingerprint works. It increases the screen brightness to the max usually. It's the flaw of using that kind of fingerprint rather than sonic like Samsung. I personally prefer the hardware on the back kind.
Click to expand...
Click to collapse
I don't remember it being this prominent on my previous OnePlus devices, though. My 8 Pro did not flicker as aggressively as this one does. It's enough for me to clearly notice it, even in brighter areas; this is why I've been left with a bit more concern than usual.
Not to mention this occurs even if I use my pattern to unlock.
Not sure. Mine does the same but doesn't bother me in the least bit. If it happened at other times other than unlock would be different story.
zymphad said:
Not sure. Mine does the same but doesn't bother me in the least bit. If it happened at other times other than unlock would be different story.
Click to expand...
Click to collapse
Any chance you could try and make a video of it happening on your device? I just want to see if it's the same thing as mine. That way, I'll have a better idea of this being a defect or normal behaviour.
I know, it's kind a big ask so no rush! If you ever have time. I can do the same if anyone needs to see what I am talking about exactly.
Update:
I've noticed the issue occurs only if the lock screen is showing. If ambient display is on and the fingerprint icon shows at the bottom then the device will unlock without flickering. The fact that it's happening only when the screen is on at the lock screen, is what's making me feel like maybe it's not a hardware problem. Very odd issue...
Another update,
After doing more Googling I came to the conclusion that it's a hardware issue over software. I tried to factory reset and the issue was still present.
I couldn't update the software on the phone though. It kept telling me that there was an installation problem. I'm guessing that's because I had previously used a rooted EU boot img and a factory reset through the phone settings isn't enough to get rid of that. I'm hoping the repair center won't fault me for sending the device back with an unlocked bootloader. Doesn't seem like OnePlus would do that anyway, given how open they are with the modding community.
Once I receive the replacement of test to see if the issue was still there and will update this thread.
rickysidhu_ said:
Another update,
After doing more Googling I came to the conclusion that it's a hardware issue over software. I tried to factory reset and the issue was still present.
I couldn't update the software on the phone though. It kept telling me that there was an installation problem. I'm guessing that's because I had previously used a rooted EU boot img and a factory reset through the phone settings isn't enough to get rid of that. I'm hoping the repair center won't fault me for sending the device back with an unlocked bootloader. Doesn't seem like OnePlus would do that anyway, given how open they are with the modding community.
Once I receive the replacement of test to see if the issue was still there and will update this thread.
Click to expand...
Click to collapse
One time I sent them bricked device and they still accepted the return. Returning unlocked bootloader phone shouldn't be a problem.
What made you think it was hardware since I see other people have the same thing. Hell I had it too. I don't seem to have that problem after updating to latest firmware. Seems to be software to me.
Hope it gets fixed. I saw a thread for it on OnePlus community forum, so hopefully OnePlus knows.
rickysidhu_ said:
I'm hoping the repair center won't fault me for sending the device back with an unlocked bootloader. Doesn't seem like OnePlus would do that anyway, given how open they are with the modding community.
Click to expand...
Click to collapse
When I sent the phone away for trade in there was no mention of rooting or bootloader unlock. Just wipe it.of your info and data.
zymphad said:
What made you think it was hardware since I see other people have the same thing. Hell I had it too. I don't seem to have that problem after updating to latest firmware. Seems to be software to me.
Hope it gets fixed. I saw a thread for it on OnePlus community forum, so hopefully OnePlus knows.
Click to expand...
Click to collapse
Thinking it's hardware because my 8 Pro doesn't literally cause a white flash of the entire screen, it would just up the brightness which is normal.
And I was also noticing my touches only registered on more firm presses. Made me think it could have been a bad display panel.
Didn't want to take any chances especially while inside the 15 day return/replacement window.
rickysidhu_ said:
Thinking it's hardware because my 8 Pro doesn't literally cause a white flash of the entire screen, it would just up the brightness which is normal.
And I was also noticing my touches only registered on more firm presses. Made me think it could have been a bad display panel.
Didn't want to take any chances especially while inside the 15 day return/replacement window.
Click to expand...
Click to collapse
Yeah good plan.
It absolutely does NOT do that on mine. Only the fingerprint area gets bright, not the entire screen.
NotTheGiant said:
It absolutely does NOT do that on mine. Only the fingerprint area gets bright, not the entire screen.
Click to expand...
Click to collapse
+1 on the 9Pro
According to the OnePlus support section of the site, the progress shows as "Inspected". I assume the next step is shipping out a replacement. Hopefully it's soon, will post an update on the new unit.
Thanks for letting me know you guys aren't experiencing the issue, makes me feel good about my decision of sending it back. Almost didn't do it because I didn't want to come back to this Pixel 5 after being spoiled by that 9's screen size lol.
Got the replacement today, after some testing it seems like this unit has no issues! There is a clear difference between this one and my original. There was a blinding white flash even when using my pattern to unlock. Same thing when double tapping the lock screen to put the device to sleep.
This has no white flashes so definitely seems like a hardware issue. Finally, I can start enjoying this thing!
rickysidhu_ said:
Got the replacement today, after some testing it seems like this unit has no issues! There is a clear difference between this one and my original. There was a blinding white flash even when using my pattern to unlock. Same thing when double tapping the lock screen to put the device to sleep.
This has no white flashes so definitely seems like a hardware issue. Finally, I can start enjoying this thing!
Click to expand...
Click to collapse
Awesome, glad you got a good one! They didn't make you wait too long...
rickysidhu_ said:
Got the replacement today, after some testing it seems like this unit has no issues! There is a clear difference between this one and my original. There was a blinding white flash even when using my pattern to unlock. Same thing when double tapping the lock screen to put the device to sleep.
This has no white flashes so definitely seems like a hardware issue. Finally, I can start enjoying this thing!
Click to expand...
Click to collapse
How bro it can be a hardware issue.. it's only happens on low brightness when you unlock the phone right?I am also facing the same issue but it is not there where I unboxed the phone and used it for 1day after receiving update to os 11.2.7.7only this problem starts to me..so how can it be a hardware issue
Bodhidharman said:
How bro it can be a hardware issue.. it's only happens on low brightness when you unlock the phone right?I am also facing the same issue but it is not there where I unboxed the phone and used it for 1day after receiving update to os 11.2.7.7only this problem starts to me..so how can it be a hardware issue
Click to expand...
Click to collapse
No it happened on any brightness. It was just more noticeable in low brightness and reading through the same issue on OP forums, others were confirming it is hardware related as a complete factory reset isn't able to resolve the issue. If it was software related, a complete restore would have/should have fixed it. Your issue might be different from what I was experiencing.

Categories

Resources