Database Info

Not happy with my Raphael

I am sorry to say, but I am not happy with my new phone !
Some serious problems with it.
1. sometimes when I push the powerbutton nothing hapens, and actualy I can see the phone is fuctioning (round button is flashing for new mail). After a few seconds I get the "famous" grey screen. Reboot is the only option.
2. sometimes I wake up and the phone has boot (I guess) somewhere in the night, because I have to give my accescode for the sim.
3. the "broken glass" isue is a problem and happens twice now
Think these are not small problems for a "Pro" phone.
Right now I don't have a riable and solid phone, and I think a pro phone should be that way .
Hope this things are fixed soon.

I wonder if this is a difference in roms or if you should return your touch pro. I've beating the hell out of my phone software wise to see how it will run and i haven't had a single problem yet. I haven't been charging it via the wall charger so maybe that has something to do with it but i doubt it.

Send it back! At least try that once, if you get the same problem again then either you are very unlucky, or there is a problem with all batches. I haven't had either of those problems once and got the phone the day it came out.
I only see one or two people complaining about these issues.
Steve

steveoidm said:
Send it back! At least try that once, if you get the same problem again then either you are very unlucky, or there is a problem with all batches. I haven't had either of those problems once and got the phone the day it came out.
I only see one or two people complaining about these issues.
Steve
Click to expand...
Click to collapse
I am thinking about it, to send it back. But I still hope it is a rom problem, like Bxsteeze said. Flashing another rom could help. Soon that is possible I will try.
If it doesn't help I send it back.(forgive my my English )

TBH i would do it the other way around. If flashing the ROM doesn't help because of a hardware fault and you have flashed another ROM, chances are you may not get the replacement you want.
especially as Olinex haven't finished the SPL Downgrader yet.....

DONT send it back ffs!!
We have just got HardSPL for the thing so you can actually try any ROM you wish, surely its worth the little hassle trying that first?!

I had the same "broken glass" like screen issue only once also when sitting overnight, but it wasn´t charging at all.
I have several other issue´s but it think it´s ROM related, and if it´s not i´m gonna send mine back aswel.

I've had issues 2 and 3 happen to me.
A couple of times now when trying to wake the device from an overnight charge in the morning I get no response, device locked. Soft reset and all is well.
Regarding the broken glass thing, that's definitely a software issue. Its TF3D having a spaz. If you disable it and then re-enable it, all is well.
Check out the issues thread here:
http://forum.xda-developers.com/showthread.php?t=418150
and here:
http://forum.xda-developers.com/showthread.php?t=420700

Hey if anyone doesn't want their Raphael. You could give it to me.

hardSPL ? Let the party begin

Problems
Hi,
Four problems i found so far.
First the broken glass effect. When the phone is ringing and i turn it on his screen the ringing stops and the 3dflo breaks. Or the screen turns grey.
Problem 2 After it restarts i get an device.exe issue.
Problem 3 volume of normal calling is very low. In a noisy room it is hard to understand the caller.
Problem 4 During a call several hick-ups. Also when the signal strength is max.
For know. It is a nice smartphone but some things need improvement.

Can I remind people there is an issues thread here:
http://forum.xda-developers.com/showthread.php?t=418150
I know a couple of pages got a bit OT about touch sensitive buttons etc but its back on track now. Log your issues in there guys so we can try and help each other better.

Syphon Filter said:
Can I remind people there is an issues thread here:
http://forum.xda-developers.com/showthread.php?t=418150
I know a couple of pages got a bit OT about touch sensitive buttons etc but its back on track now. Log your issues in there guys so we can try and help each other better.
Click to expand...
Click to collapse
And dont forget to add the info to the wiki.

My Touch Pro has had the 'wake up' problem (either refuses to without soft reset or shows me frizzed up screen), has frozen on me during basic setup (following a hard reset) and has given me several spontaneous resets.
It also keeps forgetting my wi-fi network exists.
I feel safe in saying that I have a faulty one, so I'm asking for a replacement.

[Q] No tablet display but HDMI works.

Hi,
Yesterday (08/02/2013) I updated my tf700t, everything seemed to be fine after it rebooted, I was playing a game, the battery was low, and it turned off abruptly. I assumed it automatically shutdown because of the battery, so I put it in the dock and plugged in the charger. Several hours later I tried turning it on and nothing. I held down the power button for 8 seconds felt the double vibration, but no display. I tried various combinations of docked/undocked, power cord plugged in, holding the power button for 30-60 sec. etc. but nothing.
Out of curiosity I connected the HDMI to my computer monitor and sure enough, it was there, I could unlock it and everything seems to be functioning fine, just no display. The digitizer seems to work fine, although guessing where things are at is pretty tough.
I think I tried the cold boot, volume up/down (I tried both) plus power, and it didn't make a difference.
In order to do the update I had to flush the DMC Client and CMClient data and cache, I had been getting errors from DMC Client crashing.
Also I'm not certain this is update related, as the tablet had been acting wierd, which is why I did the update. I would press the power button to turn the screen on and nothing would happen, so I'd hold it down longer and the tablet would reboot and finally the screen would come on, or it would come on a few seconds after I pressed the button. I was getting a lot of reboots etc... I thought the update might resolve this.
I'm not sure if the problem is hardware, firmware, or software related.
I'm wondering if when I flushed the DMC and CM Client cache, maybe I deleted the drivers for the display or something?
My options seem to be:
1.) Factory reset by feeling around the digitizer while connected to HDMI
2.) Factory reset via the pinhole
3.) Install new (old) firmware via usb/computer. (the device is recognized by Windows 7 so I think this is doable.)
4.) Send it off to Asus. (would this be free?)
So my questions are:
1.) is there something else I should try?
2.) what order should I do the above in?
*Note: I'd like to save my data somehow.
*Edit: I forgot to mention I was on 4.2.1, no root or anything. Also I bought this in July of '12 so I'm pretty sure it is out of warranty. Any idea how much it might cost to send it off? Perhaps I could replace the LCD myself? I replaced the digitizer/screen on an ipod touch, although I'm sure this LCD is much more expensive and much harder to replace. This is turning into a nightmare. So much for trying to keep my data, now I hoping to keep this from becomming a paperweight.
Thanks.

A bloke at work had this issue. He let it rundown and left it for 3 days. It worked fine again after that.

zpyatt said:
I'm not sure if the problem is hardware, firmware, or software related.
Click to expand...
Click to collapse
If you don't even see the boot logo, it cannot be software related.

Thanks for the replies.
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.

zpyatt said:
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.

_that said:
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
Click to expand...
Click to collapse
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.

zpyatt said:
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
Click to expand...
Click to collapse
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....

sbdags said:
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
Click to expand...
Click to collapse
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.

zpyatt said:
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
Click to expand...
Click to collapse
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.

Having the same problem
I am having almost the same problem, except that the tablet screen works when the wall charger is plugged in. THe HDMI display and the digitizer work fine. It is just the tablet's screen dispaly when the charger is unplugged.
sbdags said:
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Click to expand...
Click to collapse

So I didn't have any luck letting it run all the way down.
I contacted customer support, the warranty is only 1 year, but fortunately for this there is an extra 3 months, so I just managed to squeak by, although I'm keeping my fingers crossed.

same problem as you both
i have d same problem well until last week the screen displays when conne ted to wall charger now its all blank but iy works via hdmi, digitizer works fine but all blank, this tf201, does anyone know if i change d whole display it will work?
i already bought the tf701
any suggestions is welcomed and did you get youra to work?

zpyatt said:
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL.
Click to expand...
Click to collapse
I have not seen people mentioning VHDL and verilog for a while, hahaha... It sounds like you are a low level or physical layer programmer. Any way, a firmware is in general a low level program that communicating with the hardware and the software or high level program ( level 7).. If you will, a firmware is a management levels (level 2 and 3). A VHDL is a level 1 which generates a 0's and 1's or mapping the transistors in the FPGA chip for example.... Oh well, it is just my definition...
zpyatt said:
I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
If you can get the output from the HDMI port, it is more likely you have a hardware problems. I think that the problems are your display related hardware. If you really want to troubleshoot your issues, you can look on the mother board to locate all the electrolytic caps and check to see any abnormal signs of those capacitors. Those caps are the one that will blew up first before any others parts go....Good luck...:fingers-crossed:

Phone is hard to unlock...bug or feature?

My N5 was recently replaced (last month on warranty yay) because of screen failure. The replacement I first got had to go back to Google as well because of uneven backlight. The second one I got is a little bit better (still not as good as the first tho), so I decided to keep it. However it turns out that these 2 more recent units they shipped to me don't unlock unless the proximity sensor has nothing on top. I mean it's enough that you hover you hand (even a few inches away) on it while you push the power button and the phone won't turn on. I understand that this can be a cool "feature" because you'll never unlock your phone in the pocket by mistake and all that, but the weird thing is that my previous unit never did that. FYI I'm on CM11 right now, stock software was gone by the first 5 minutes I opened the box, so I don't even know whether it's a CM feature or just a phone feature from the 403K rev. Anyone else owning a 403K that does this? Please forgive me if this is a dumb question but this "feature" annoys me so I'd love to know whether it can be disabled or something.

I use a custom rom so maybe its hard to tell, but I can completely cover my sensor and still unlock. Proximity is not supposed to be in use for screen unless on a call.

That's interesting. I'm still not sure about contacting Google over this, I can live with it, having to ask for two replacements in a month has been annoying enough already, setting your phone up every time is a pain. Anybody using CM can relate maybe?

vnvman said:
That's interesting. I'm still not sure about contacting Google over this, I can live with it, having to ask for two replacements in a month has been annoying enough already, setting your phone up every time is a pain. Anybody using CM can relate maybe?
Click to expand...
Click to collapse
One thing you can do is set it back to stock and see if it happens. If you're rooted now you can just take a nandroid so you won't really lose anything by testing.

Yeah I may try that on Sunday if I have some spare time, will report back.

vnvman said:
My N5 was recently replaced (last month on warranty yay) because of screen failure. The replacement I first got had to go back to Google as well because of uneven backlight. The second one I got is a little bit better (still not as good as the first tho), so I decided to keep it. However it turns out that these 2 more recent units they shipped to me don't unlock unless the proximity sensor has nothing on top. I mean it's enough that you hover you hand (even a few inches away) on it while you push the power button and the phone won't turn on. I understand that this can be a cool "feature" because you'll never unlock your phone in the pocket by mistake and all that, but the weird thing is that my previous unit never did that. FYI I'm on CM11 right now, stock software was gone by the first 5 minutes I opened the box, so I don't even know whether it's a CM feature or just a phone feature from the 403K rev. Anyone else owning a 403K that does this? Please forgive me if this is a dumb question but this "feature" annoys me so I'd love to know whether it can be disabled or something.
Click to expand...
Click to collapse
rootSU said:
I use a custom rom so maybe its hard to tell, but I can completely cover my sensor and still unlock. Proximity is not supposed to be in use for screen unless on a call.
Click to expand...
Click to collapse
It is a CM11 feature/annoyance.
Added in CM11 M9:
- Proximity Wake-Up support – prevent accidental wake-up of device by checking to see if proximity sensor is blocked (eg. Device is in a bag or pocket).
As of CM11 M10, M11, or some Nightly after M9 (I don't follow CM too closely, I use my own self-built ROM), that option is disabled by default in the Settings. If you're flashing an old build, or restoring a backup, it'll still be enabled as it was previously enabled by default (until all the idiots who can't read the post right above theirs/search spammed the hell out of the CM11 threads with complaints lol!).

Thanks sooo much for your post. Yeah it's gotten pretty hard to find useful info in the CM thread nowadays, in fact I didn't even bother posting there. I'm running M10 with a fresh install, but I guess that setting was restored when I logged into my CM account or something. I searched the options with the "wake-up" key word and it showed right away. Sorry for being so dumb, I tried searching for "proximity" before but it showed no results so I figured it wasn't in the options. Thanks again.

vnvman said:
Thanks sooo much for your post. Yeah it's gotten pretty hard to find useful info in the CM thread nowadays, in fact I didn't even bother posting there. I'm running M10 with a fresh install, but I guess that setting was restored when I logged into my CM account or something. I searched the options with the "wake-up" key word and it showed right away. Sorry for being so dumb, I tried searching for "proximity" before but it showed no results so I figured it wasn't in the options. Thanks again.
Click to expand...
Click to collapse
The CM Account was probably it.

Messed-Up Display

Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.

Saad S. said:
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Click to expand...
Click to collapse
Has this happened after you flashed a rom or.. ??

semirr said:
Has this happened after you flashed a rom or.. ??
Click to expand...
Click to collapse
Yes after I flashed the rom but not directly after. But after a good 1 month.

Saad S. said:
Yes after I flashed the rom but not directly after. But after a good 1 month.
Click to expand...
Click to collapse
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.

semirr said:
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
Click to expand...
Click to collapse
Is it possible that a driver update could fix this, if so then how?

Saad S. said:
Is it possible that a driver update could fix this, if so then how?
Click to expand...
Click to collapse
Hmm i dont think that a driver could be the problem. And if it is i dont know how you could fix it Google it

I hate to be the bringer of bad news - but your screen is toast. Fortunately you can replace the touch and display components all at once.
http://www.amazon.com/Skiliwah-Digitizer-Assembly-Google-nexus5/dp/B00HN0U168
Here is what you need to perform the repairs - and here are the procedures for disassembly.
https://www.ifixit.com/Teardown/Disassembling+Nexus+5+Display+Teardown+-+liquid+damage/32410
Trust me, it's not that difficult. Unfortunately, it's a bit pricey ($60 for the screen and digitizer), nevertheless much cheaper than a new device or sending your device in for repairs.

Rma

Problem Solved
The screen isn't toast, neither is the digitizer. I have 2 of these phones. The parts which cause problems like this are the main board and the ribbon with the USB connector on it, which also attaches the screen & digitizer to the main board. One was showing lines exactly like this, & also no touch. I put a replacement main board in. Works great now. The other, wouldn't even turn on. I put the main board from the first phone in the second one, it still wouldn't turn on. I replaced the ribbon cable, it turns on and perfectly replicates the issue from the first phone. So now, I have one fully functioning LG Nexus 5, and another which turns on with the same problem as yours. This is good, I started out with 2 of them that were useless to me. So, it appears that your display and touch issues are caused solely by a bad main board. A replacement main board costs somewhere around $75. After swapping stuff around, I have 2 bad main boards, 1 bad USB ribbon & 1 working phone of 2. Not bad, not bad at all.

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.