Develop Bugs

[Q] Touch stops working for some letters

Hi folks,
I'm not sure what's up with my phone. I have CM10 beta on it and since earlier today the D button on the keyboard is completely unusable. Also, I have a hard touch hitting R. I have tried touching the same area in other apps and it seems to work fine. Maybe there's a tool out there I could use to confirm this?
I had this happen before on an earlier build of CM10. When it happened before (and as of now), rebooting doesn't fix it. Last time I gave up and just upgraded my CM10 ROM, and it has been working ever since (around a month or so).
Today, the touch screen experienced some "glitches". What I mean is, I took it out to use it and it seemed like it was detecting touch/drag events in various spots, and I had to put it to sleep to get it working again.
I have no idea where to start with diagnosing this. It doesn't seem to be a hardware issue, since re-flashing before fixed it. Any ideas?

Go back to stock, if you have the same problem then it will probably be hardware issues.
Sent from my One V using xda premium

[Q] Touchscreen gone mad @lockscreen

Hi!
Have anyone notised this problem with Z1C?
I received my Z1C 4 days ago and this has happened once every day. It seems to appear when trying to unlock the phone and all of a sudden it goes mad and nothing seems to happen when touching the screen. Otherwise the device seems to work fine. But do you guys think this is a software issue that can be fixed at next update or do you think I need to RMA?
regards.

This looks like a software issue to me... Try to factory reset your device and if it still persist reflash it with PC Companion it should fix the issue. A hardware defect can't make a phone like that don't worry
DXarz said:
Hi!
Have anyone notised this problem with Z1C?
I received my Z1C 4 days ago and this has happened once every day. It seems to appear when trying to unlock the phone and all of a sudden it goes mad and nothing seems to happen when touching the screen. Otherwise the device seems to work fine. But do you guys think this is a software issue that can be fixed at next update or do you think I need to RMA?
regards.
Click to expand...
Click to collapse

did it do that right out the box? or did you install anything that could have messed with that?

RevokOne said:
did it do that right out the box? or did you install anything that could have messed with that?
Click to expand...
Click to collapse
I cannot se anykind of app that I installed that would mess up the device like that? Ive installed about 15 apps and mostly "stand alone" apps like skype, sofascore and MX player. The app that closest could affect the UI is then maybe Nova launcher (got the prime verision) but I dont think it would mess up the lockscreen like that? (Or atleast it havent on any of my other devices, always felt solid and worked perfect)

It's not always about apps you installed though... There could be data files from system apps that got corrupted and caused the issue.

Do you have glove mode on at all? The screen is very sensitive, it could be some conductive dirt on the screen. I tested my Z1C in the shower, a drop of water rolling down the screen is enough to open the notification area or scroll a website in chrome.

Did you see this?
http://forum.xda-developers.com/showthread.php?t=2643078
I think this is a hardware issue.
This happens more often if you use some sort of flip case (I had roxfit).
Now I have only a screen protector with hardcase i have still lockscreen ghost touches but less.
To fix it just clean the display with cloths or something you prefer.
DXarz said:
Hi!
Have anyone notised this problem with Z1C?
I received my Z1C 4 days ago and this has happened once every day. It seems to appear when trying to unlock the phone and all of a sudden it goes mad and nothing seems to happen when touching the screen. Otherwise the device seems to work fine. But do you guys think this is a software issue that can be fixed at next update or do you think I need to RMA?
regards.
Click to expand...
Click to collapse

Okay, this is starting to be interesting. I actually did a factory reset three days ago and now this phenomenon haven't happened since before the reset. Though I must admit that Im not sure if I noticed the problem before mounting the Muvit Easy Folio case since I got the case the day after I got the phone. Unfortunately I have not had time to reinstall all apps that I had before the factory reset so for now my phone is not really comparable with the device it was three days ago. After the weekend I will probably know more since I will have had more time testing and installing all the former apps (then I can uncheck that variable). I hope its not the case since I have not found any other case that's lime and also cover the screen, though It also looks like a possible troublemaker (according to delimanyak23 and the thread)
time will show, I'll be back when Ive done some more research

This happened to me but in homescreen. I just turned off the screen. Wipe the screen with my tshirt for 2-3 secs and viola problem gone. Weird but it works
Sent from my D5503 using Tapatalk

My wife also has that issue. Her phone was factory reset but still the same and as it was seen by the shop who sold it to us, the phone will be replaced today. We will see if it happens with the new phone.
Nb : glove mode is off, no screen-protection used, a protectiln case is used but i don't know what model it is. I'll you the update after trsting the new phone.
Sent from my GT-I9506 using xda app-developers app

Crazy Touch Screen Not Responding Bugs with my G3

So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up...
Edit: This is a confirmed fix for me.
If you face the same issue, try:
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot

I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag).
Sent from my Nexus 5 using Tapatalk

@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.

deedscreen said:
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
Click to expand...
Click to collapse
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2

Epix4G said:
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Totally agree with @Epix4G on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh).
Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc.
If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).

^^^^ - Will take that into consideration.
This may be a possible fix for now, can't yet confirm
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
It may or may not help
EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.

Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.

@deedscreen
I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot.
ic_fw_version info
SYnaptics 5.5
PanelType 1
version: v1.22
IC_product_id[PLG313]
Touch IC : s3528(family_id = 1, fw_rev = 1)
What version is your firmware? Also, did you find out about the fix from somewhere?

I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue.
I have (RAW) touch screen firmware version: 30 05 51 96

Same problem, but not only on lock screen
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now.
But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version.
After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again!
I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.

This is happening when the screen is on right? Or is the screen turning off and then not turning I again?

You need to keep Knock feature on, someone already said this. That's why your screen is freezing.

Daum Ex said:
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Click to expand...
Click to collapse
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug

icon71 said:
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
Click to expand...
Click to collapse
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...

Daum Ex said:
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Click to expand...
Click to collapse
Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like:
- this is a normal behaviour and can happen (!!)
- don't put your phone in the front pocket
- use the quick circle case to prevent...
- disable knock on (which is at least not possible over a standard setting, but only via the hidden menu).
I wrote back:
- that for me, this is not a normal behaviour
- that 90% of male users are wearing the phone in the front pocket
- that I don't like to buy a case only to prevent a bug of a premium telephone and
- finally, that they please could tell me, where and how to disable knock on
I am curious about their answer...

Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least.
Next time i purchase an Android phone i'm going with Nexus line...

icon71 said:
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem...
Click to expand...
Click to collapse
So what happened? How is it doing now?

Hey everyone, I just wanted to report my results of this touchscreen bug.
Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it.
I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER!
The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen.
I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL.
I hope this helps someone here.

Knock
If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away.
I think LG really has to deal with this issue.

Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855.
First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck.
I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard?
I really don't know what to do! Appreciate any comments or suggestions!!!
Thanks in advance!

[Q] Touchscreen problem

Hi everyone,
TL;DR: I have an issue with the touchscreen of my Find 7 qhd (x9076), while on any other ROM than stock it my touchscreen glitches or something.
After installing a custom Rom, like PA, Dirty unicorns, CM, Nameless or any other available for this device (I believe I've tried all of them). The device works just like it should, nothing wrong with the touchscreen. But after like half a day, it starts to 'glitch'. Sensitivity is very low, when I press here it detects a press somewhere else.
I've got a temporary solution which is wiping the cache in recovery, then it works for a short period of time, but then it starts gliching again..
On stock rom the issue doesn't exists, but I realy do want to use a custom one.
Is anyone experiencing the same issue? Or maybe someone who has a solution?
Thanks in advance!
P.s every install is a full wipe, tried multiple recoveries, non-unified

I've read that the touchscreen fixes implemented by Oppo only work on ColorOS even though ROM makers have already implemented the fixes into the Roms. I'm not sure why, though

farenteria said:
I've read that the touchscreen fixes implemented by Oppo only work on ColorOS even though ROM makers have already implemented the fixes into the Roms. I'm not sure why, though
Click to expand...
Click to collapse
Hmm that's unfortunate, but it seems to me that I am one of a few people having trouble with this? Why don't other x9076 users have this problem?

B-vb said:
Hmm that's unfortunate, but it seems to me that I am one of a few people having trouble with this? Why don't other x9076 users have this problem?
Click to expand...
Click to collapse
Not sure. I personally have never had that problem

I want to bump this thread, i have this problem aswell and still it isnt fixed. anyone has a idea what to do about it ?

B-vb said:
Hi everyone,
TL;DR: I have an issue with the touchscreen of my Find 7 qhd (x9076), while on any other ROM than stock it my touchscreen glitches or something.
After installing a custom Rom, like PA, Dirty unicorns, CM, Nameless or any other available for this device (I believe I've tried all of them). The device works just like it should, nothing wrong with the touchscreen. But after like half a day, it starts to 'glitch'. Sensitivity is very low, when I press here it detects a press somewhere else.
I've got a temporary solution which is wiping the cache in recovery, then it works for a short period of time, but then it starts gliching again..
On stock rom the issue doesn't exists, but I realy do want to use a custom one.
Is anyone experiencing the same issue? Or maybe someone who has a solution?
Thanks in advance!
P.s every install is a full wipe, tried multiple recoveries, non-unified
Click to expand...
Click to collapse
Try to flash back stock recovery then flash COS 1.20 in systembase, then upgrade to COS 1.25, Then upgrade to 2.0 or above. Then flash custom recovery and rom again. This is the step you will not have problem in custom Rom. I am 100% sure.
Sent from my X9070 using XDA Free mobile app

I have the same problem, and I'm running Stock OS.
v2.1.4i Beta
This is how I bought the phone, interesting that it reads Beta...

I've updated to the latest firmware and still having touch screen sensitivity issues.
Someone has got too have some advise.... Oppoooooo.....

TouchScreen Auto Test - FAIL
I did the TouchScreen Auto Test and showed FAIL. Has anyone else shown this error?

Hi, I am having exactly same touch screen problem with custom roms, have tried both Omni and crDroid.
Is there a solution for this? I didn't have this problem in COS before.

What's the auto test?
I‘m on COS 2.1.5I and sensitivity works ok so far. I did have auto brightness problems but xposed and gravitybox has helped me adjust a lot of that out. Now it doesn‘t over dim in low light.

Auto test in COS is ok, I only had this problem in custom Roms, COS worked smoothly,so I reckon it's could be driver issue in custom Rom, maybe there are new fix for some panels are not included in custom Rom.

I never had any problems with touchscreen on find 7 until now. I have been extremely satisfied with this device until now. I have the find 7 9076.
There is a lengthy discussion of this touchscreen problem on the oppo forums.
My opinion is, it has nothing to do with the rom or firmware. It is a physical problem caused by heat. Once overheated, the digitizer gets somehow damaged.
I left my phone on a table in direct sunlight for hours while working on my lawnmower. I noticed it got very hot to touch. Ever since then my touchscreen has problems where there were no problems for 2 years prior. Dead spots, phantom touches and behaves sluggish in certain spots. Upper screen in portrait.
I tried wiping and reinstalling. Nothing works to fix this.
I even tried sealing it in a ziplock bag and freezing it. This actually works but its only temporary. The digitizer got damaged from heat. There is no "software" fix.
The only solution I can see is to physically replace the digitizer. This is a difficult thing to do but can be done.
I am considering replacing replacing the entire screen along with the digitizer as this is much easier but the problem is getting the high res replacement. Most after market screens are not equal to oppo's. The cost of OEM is too high.
Shame because this problem makes me now shy away from oppo devices.

Okay,
I opened up the phone.
Set to try and pry off/seperate the digitizer and replace with new one.
Decided to try something first.
Unplugged the digitizer and held power button (to release any stored up energy in the phone). Resnapped in digitizer cable to connector.
Reassembled the phone.
Put battery back in. Rebooted.
Sure enough, its all working. The full touchscreen is working with no dead spots or glitches.
For how long? Who knows?
Keeping this thing out of the heat.

Display wakeup issues after screen replacement

Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?

gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
You most likely got a bad part. OEM like One plus and xioami are known for using something called product binning. Which means their parts have a higher failure rate then other oems. They also dont make extra parts really so what you got was most likely just a generic screen like you can buy at any shop in China.
Nothing you can really do about it except try a different screen but to be honest I would get a different device and this time dont skip on the price. You get what you pay for and when a good device is cheap there is always a reason. (why do you think most of the owners and mods of XDA run Iphones as their daily drivers and leave android for a hobby)

gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
As an experiment, try stock OOS and see whether the issue goes away.

i too have this problem cant find any solution anywhere been trying for about a week now arrggghh

ireaper4592 said:
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
Click to expand...
Click to collapse
tnsmani said:
As an experiment, try stock OOS and see whether the issue goes away.
Click to expand...
Click to collapse
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!

gt-kingz said:
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
Click to expand...
Click to collapse
Thanks for the confirmation. The cheaper screens seem to have an issue which is not faced by the costlier ones. I have found while roaming the threads that sometimes flashing OOS helps. May be a driver issue.

My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.

Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.

csabatoro said:
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
Click to expand...
Click to collapse
Did you try OOS?
OEM screen is not cheap (atleast compared to what is offerred online).
May be you are better off with what you have since you have found a work around. Who knows what you will get next time?

Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up

skymera said:
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Click to expand...
Click to collapse
How much plz?

Shreeram02 said:
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
Click to expand...
Click to collapse
Thank you also for confirming that on OOS there is no issue. Looks like the cheaper of the online replacements have this issue while the costlier ones don't.

Funniest thing is I have a slim ROM backup on 7.1. and that works fine so like what the f--- any ideas people?

gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
Yes, I have the same issue and I wanted to revert back to Stock OOS, but I just tried Caesium latest kernel, and the display wakeup issue seems to have gone. I'm using Havoc OS 2.3 based on Android Pie.

Guys the latest mad kernal reborn it wakes up all the time
At least for my screen
It used to be worse on all the other kernals

Finally found a solution
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...

Mohammed Raihan said:
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Click to expand...
Click to collapse
post link to one u have plz

Mail me i have that file..
[email protected]
There is issue while sending here

Mohammed Raihan said:
[email protected]
There is issue while sending here
Click to expand...
Click to collapse
got anyway working fine cheers dude

Even i have the same problem as mentioned above..even i changed my oneplus 3 display
I always prefer custom roms..but screen wakeup issue had made my phone worse...then i tried oos 5.0.8 and it works like a charm...yeah i know its very old android version but no other option though...
Others who have same problem and have no issues going back to oos oreo then go for it...your problem is solved..
---------- Post added at 01:47 PM ---------- Previous post was at 01:43 PM ----------
ireaper4592 said:
got anyway working fine cheers dude
Click to expand...
Click to collapse
Is this kernel working for you!??