Phone is hard to unlock...bug or feature? - Nexus 5 Q&A, Help & Troubleshooting

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.

Related

Strange Backlight occurence...

Has anyone had this happen to the GS4G? It used to happen occasionally, but now it's often. After every call that's ended, my backlight resets itself back to the dimmest setting. I even set it to the automatic setting & it still does it & I have to manually go back in each time to brighten the screen. I realize there is a sensor that blacks the screen out when talking on it, but that's not the case. The phone is stock, & unrooted. Could this be the sensor gone bad?
96traxx said:
Has anyone had this happen to the GS4G? It used to happen occasionally, but now it's often. After every call that's ended, my backlight resets itself back to the dimmest setting. I even set it to the automatic setting & it still does it & I have to manually go back in each time to brighten the screen. I realize there is a sensor that blacks the screen out when talking on it, but that's not the case. The phone is stock, & unrooted. Could this be the sensor gone bad?
Click to expand...
Click to collapse
well for starters...fyi, the super amoled screen doesnt have a backlight...thats what makes it able to accomplish the deep blacks..just so you know
but, silly question, have you tried rebooting?
Pardon the wrong choice of word "backlight", I was just trying to make the question as simple as possible. Also, I rebooted several times since this has been going on to no avail. It's been a going on for about a month.
96traxx said:
Pardon the wrong choice of word "backlight", I was just trying to make the question as simple as possible. Also, I rebooted several times since this has been going on to no avail. It's been a going on for about a month.
Click to expand...
Click to collapse
gotcha,
the only thing I can think of is a faulty sensor, a possible hard reset, or your holding the status bar and dragging your finger across the top of the screen, which is a gooseegg way to adjust the backlight if you have the auto brightness turned off.
Yeah, I was just had a chat with T-MO & they said they had to replace 5 since these came out & it was out of the batch that had the FEB. sticker on the box. They assumed it was the sensor, but no real confirmation from the techs. But they had me place the phone face up & call my VM with the speaker on, then flip it over face down during the call & then back over then end the call, guess what?, same thing. So they're going to send me one out. I guess i'll tinker around with this G2x for the time being, I tell ya, i'm gonna miss the superamoled, lol, talk about a BIG difference. thanks man

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.

Touch screen problem

Hi guys,
i'm having an issue with my HTC u11, basically when i'm using the phone randomly the swipe down screen (when you swipe the screen down from top to bottom to get the notifications) comes down.
For example if while i am writing a message then drop down screen will come down when i'm typing, i then have to swipe up and continue and again.
it happens more or less all the time and is quite annoying.
any ideas?
its okay, issue resolved. NOVA Setting had gesture switched on. Swipe down for notification menu, this was the issue. lol
PLease close the thread.
Thanks
killa_byte said:
its okay, issue resolved. NOVA Setting had gesture switched on. Swipe down for notification menu, this was the issue. lol
PLease close the thread.
Thanks
Click to expand...
Click to collapse
Well i had the same issue. Was driving me mad! Thanks for the info.
I don't use nova and I have been experiencing this same problem so now what?
Sent from my SM-G955U using XDA-Developers Legacy app
Yeah i though the Nova setting had solved it but it seems to be back again for me, although not as frequent.
I also experience the keyboard collapsing randomly too. Anyone get that?
Hi guys, thought nova got rid bit guess not. I still get the issue. Would this be a software issue or do I have a fault with my hardware?
Any tests I can do?
I reported my issues to HTC and they replied with the following :
To test the function of the touch screen please follow the below steps
1- Dial *#*#3424#*#* > the press accept.
2- From the options, mark Line drawing test > then press run.
3- Then start drawing on the screen to check if there are parts that do not respond
The screen does not have any dead or unresponsive spots tho and the test passes without any issues.
Does anyone experience the keyboard collapses also?
I might do a full reset soon to see if that helps any. If not i will be getting back in touch with HTC.
Did all this as well, and all the tests that I've ran pass just fine. I've also done a hard reset and it didn't make any difference. I do notice that after a soft reset that it takes a while for it to happen again. It's annoying as hell so I will be monitoring this thread. Whatever you find out from htc please update this thread so we can figure out what the hell is going on.
Sent from my SM-G955U using XDA-Developers Legacy app
I also done the test and it was a pass.
I'm certain it's something to do with the software of htc. The UI has to have something wrong with it. Mind you it hasn't done it to me today yet and I'm nearly at the end of the day.
Has everyone got a case? Can't be case interference?
killa_byte said:
I also done the test and it was a pass.
I'm certain it's something to do with the software of htc. The UI has to have something wrong with it. Mind you it hasn't done it to me today yet and I'm nearly at the end of the day.
Has everyone got a case? Can't be case interference?
Click to expand...
Click to collapse
I turned off edge sense, I removed my screen protector and removed the case. It still does it when it's ready.
themuffinman said:
I turned off edge sense, I removed my screen protector and removed the case. It still does it when it's ready.
Click to expand...
Click to collapse
Exactly same issue here. Very very annoying. As a HTC fanboy I'm quite dissapointed. Phone less than 2 months old. I actually spoke to HTC today, they said they would have to book it in for a repair... Takes up-to 10 business days... I said this is not acceptable! Waiting for a email back.
I have emailed HTC back advising them that others are reporting the issue so unlikely that it's a single handset issue.
Awaiting their reply. No doubt it will be along the same lines that @dobknobby got and have to go through the 10 day repair process.
Will update when I get a reply.
I have had the same problem, and I have done the a lot of the same steps;
I tried several different screen protectors, thinking that was causing the issue. I have had no screen protector on for the last week, and yep it still happens.
Shut off edge sense, still happened.
Tested the touch screen, and everything passed.
Last night I noticed that it seemed to be related to the pressure I was putting on the screen, if I pressed down harder on the screen and slide my finger left or right or up the notification bar would come down. Did some more testing and for awhile I was able to reproduce it about 50% of the time. I rebooted the phone into safe mode (hold power button down and then press and hold the power off option for about 5 seconds it will ask if you want to reboot into safe mode). In Safe mode I could not reproduce it, Safe mode disables ALL third party apps.
WARNING: when I rebooted my phone to go back to "normal" all of my widgets and groupings were not on the screens, had to re add them.
After doing all this testing last night, I have not seen the notification come down, but like someone said it seems to get worse the longer the phone is running before reboot.
I was going to do a hard reset, today but that sounds like that may not help.
Not sure if this is software, but with the testing I did last night it seem to work fine in safe mode. However I have wondered if it is something with the screen, like is flexing enough for the sensors at the top to react to the pressure/flex.
Well keep testing and report back.
I'm also having some issues with the touch screen, but it mainly happens with the keyboard. I like to swipe to type, but lately I've noticed that it gets really jumpy, causing thing errors.
At first i thought it was touchpal so i installed Gboard. Problem still occurs.
I also removed my screen protector and tried did the touchscreen test.
---------- Post added at 07:30 PM ---------- Previous post was at 07:08 PM ----------
I ran the line drawing test a bunch of times and yes, i now do see that mine fails to draw a continuous line on occasion. It only happens in the keyboard (squeezable?) area though.
I'm worried now that edge sense is damaging the touchscreen.
OK, i have ordered HTC u11 this morning from amazon, but i guess i will cancel my order. Had many problems with htc phones in the past. Saw many reviews and thought that this one is perfect with no flaws... Ahh..... Already ordered some accessories for my new device... It's really a shame to read this kind of threads. Hope you guys will find a solution and hope that this won't be a hardware issue.
djbutter said:
I'm also having some issues with the touch screen, but it mainly happens with the keyboard. I like to swipe to type, but lately I've noticed that it gets really jumpy, causing thing errors.
At first i thought it was touchpal so i installed Gboard. Problem still occurs.
I also removed my screen protector and tried did the touchscreen test.
---------- Post added at 07:30 PM ---------- Previous post was at 07:08 PM ----------
I ran the line drawing test a bunch of times and yes, i now do see that mine fails to draw a continuous line on occasion. It only happens in the keyboard (squeezable?) area though.
I'm worried now that edge sense is damaging the touchscreen.
Click to expand...
Click to collapse
Does your keyboard collapse when you are typing? That happens with me. Really frustrating when you are typing quite fast then the keyboard just disappears. Then you end up tapping a link or something that was behind the keyboard. You then need to go back to the page you were on and start typing all over again.
Are you running app killers? Stop boost+ auto. Apps updating from gplay can cause you to be kicked out of the keyboard, it can also pause/stop YouTube vids.
The edge sense system is 2 sensors stuck to the inside of the edge of the device, along the aluminium strips, they shouldn't interfere with the screen at any time.
Sweaty hands and greasy screen can cause the screen to misread your touches and gestures.
Running low on internal memory (sdcard) can cause all sorts of issues. Make sure you ALWAYS have a couple of Gb free.
Try to replicate the problem in test mode.
Beamed in by telepathy
shivadow said:
Are you running app killers? Stop boost+ auto. Apps updating from gplay can cause you to be kicked out of the keyboard, it can also pause/stop YouTube vids.
The edge sense system is 2 sensors stuck to the inside of the edge of the device, along the aluminium strips, they shouldn't interfere with the screen at any time.
Sweaty hands and greasy screen can cause the screen to misread your touches and gestures.
Running low on internal memory (sdcard) can cause all sorts of issues. Make sure you ALWAYS have a couple of Gb free.
Try to replicate the problem in test mode.
Beamed in by telepathy
Click to expand...
Click to collapse
Personally I made sure to address all your points when trying to figure out what is going on. So none of this applies to me.
scotia_rfc said:
Does your keyboard collapse when you are typing? That happens with me. Really frustrating when you are typing quite fast then the keyboard just disappears. Then you end up tapping a link or something that was behind the keyboard. You then need to go back to the page you were on and start typing all over again.
Click to expand...
Click to collapse
It doesn't collapse for me, but i do occasionally have the notification shade pulled down.
dobknobby said:
Exactly same issue here. Very very annoying. As a HTC fanboy I'm quite dissapointed. Phone less than 2 months old. I actually spoke to HTC today, they said they would have to book it in for a repair... Takes up-to 10 business days... I said this is not acceptable! Waiting for a email back.
Click to expand...
Click to collapse
Same here, only I was told 7 to 15 business days. Offered to give c card to have a replacement shipped, but that is no longer an option with HTC.
So when I washed my M9, I was without a device for 2 days, but now that their phone is crap, it's going to be 3-4 weeks.
Unhappy....

SOD (sleep of death)

I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
60puc said:
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
Click to expand...
Click to collapse
This has happened to me before.What I simply did was replace the display.
Mr.Ak said:
This has happened to me before.What I simply did was replace the display.
Click to expand...
Click to collapse
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
60puc said:
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
Click to expand...
Click to collapse
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Mr.Ak said:
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Click to expand...
Click to collapse
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
60puc said:
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
Click to expand...
Click to collapse
As I already said,the same issue happened to me after I changed my display.I asked for replacement and replaced that damaged display,boom! I don't know what's so hard in it for you to understand.
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
60puc said:
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
Click to expand...
Click to collapse
Aliexpress?
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
60puc said:
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
Click to expand...
Click to collapse
Get ready with a lot of proofs tho'!
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Gab_echelon said:
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Click to expand...
Click to collapse
See previous page,I've already explained what is the cause of the issue.
I just finished replacing my screen, been waiting for my broken antenna cable and volume button flex to arrive. Everything works except the damn SOD i never had with my old screen. Tried turning off the proximity sensor check and still a no go. The screen turns on fine initially and trying to wake it instantly works all the time, but if I leave it off for any longer than 5 sec probably it won't respond to anything - power button, volume button, double tap and plugging in the usb cable connected to a power source.
Does this sound more like a governor issue? The rom installed is lineageOS (just updated to 10-30 release). Looking up my purchase log to open a dispute...
tested it again, repeated lock/unlocks puts it into the SOD state, doesn't even take 2 sec to do it...
oh wow, it does this even in the twrp recovery. I have wiped cache and dalvik cache just for the hell of it but doubt that was the real cause...
Gab_echelon said:
works everything but not touch
Click to expand...
Click to collapse
we've got a reverse situation. touch, buttons, sounds, modem works, but not screen (if you lock/unlock it 10-20 times it can raise again without reboot.
Buratei said:
it does this even in the twrp recovery.
Click to expand...
Click to collapse
i've got the first SOD in twrp mode. it doesn't matter, but at first - no troubles were with that. and now it works so so at home. and if i use it outdoor it becomes very often, but at home it seems that it works ok, just only seems, because if i want - i can do some manipulations (use camera, lock/unlock it etc) and the SOD appears again. but custom os executes SOD more frequently. i think it can be real overvoltage, like people says.
there are many posts here and everyone advices not effective solutions (flash stock, modem, fw ...) at first it helped me, but now i know there is no way, i can just try but ...
long time ago i owned an old tablet iconbit matrix - it has just the similar issue. it boots, but if you go to a sleep mode - it didn't wake up every time. it lights works ok inside, but no image. i had two displays and if i used one in a custom rom it worked ok, but not another one. stock rom works ok with every display. the solution was a display driver, like at windows OS.
cause of developers bugs, it was a little different (not stock-based) and some revisions of display works ok, others aren't.
so, i think it can be fixed, but the solution for me - change a display like the first reply says. Ali seller read this topic and posted me this in a few days after i started this topic:
Your dispute has been processed and the money will back to you in 7~10 working days.
so could you give us a positive feedback, please?
Best regards.
so, i'll order another one, no trouble, i hope this will help me to enjoy my oneplus.
60puc said:
so could you give us a positive feedback, please?
Best regards.
Click to expand...
Click to collapse
They always ask for positive feedback in exchange for refund/replacement.Bastards,aren't they? @evronetwork
For the sake of other people that'll read your feedback and make their decisions upon it,don't do it! Just complain this bribery to aliexpress staff ffs!
well I wish I bought from aliepxress... I bought mine from ebay to pinch some pennies, and because I was waiting on other replacement parts (which were only needed due to damage occurred during a screen replacement op) to ge here I am way over the protection period. aw shiiiiit, I guess you live and learn
gotta tell you though, the screen is a bit wacky in other ways too. the capacitive buttons do light up but not completely (kinda dark in the corners) and the colors look a bit off. hopefully the seller would honor the refund/return request...
EDIT: whoa... kinda hard to believe, but I messed around with battery profile just for the hell of it and by some pure luck discovered that the "performance" profile (second one from the far right) works just fine and wakes the screen every time. The "balanced" profile and everything below that gives me an insta-death. go figure!
EDIT2: guess I spoke too soon. it sure as hell looked like fixed, but it came back after a while. maybe it is just more sporadic than I thought...
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
60puc said:
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
Click to expand...
Click to collapse
What happened to getting a new display?
I use this one, because it works ok, but only at home. As a home tablet. At the street it fails every time.
I can reboot it if it doesn't wake up. But it wakes up often, so i don't want to order new one now. I want to check my mainboard to be sure, that it is dispaly problem
a bit late, but thought I should update on the situation... all working fine after a (yet another) LCD replacement. Much better color balance to boot, points to QC problems at the supplier's end. If I ever have to do this again, I am definitely going to inspect the new LCD as soon as I receive I receive it.

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