Develop Bugs

[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.

[Q] lag cm12 flo black screen of death

Well ATM its working.. But lately the lag on my device makes it stutter so bad it freezes up then slowly comes back. Then sometimes the screen goes black and my device won't do anything.. The screen doesn't come back on. I have to hold the power button and sometimes volume buttons together to get it to restart to be usable.
I have only experienced this on 5.0.x roms 4.4.4 never did this
Ideas? Suggestions? Thanks
Sent from my Nexus 7 using XDA Free mobile app

I've never had those issues on any lollipop ROMs (at least not for this device).
Personally I'm not a big fan of CM, have you tried any other ROMs and/or kernels? Have you flashed a custom kernel or adjusted any kernel settings that could be causing this? Are you using any mods (like Xposed)?
I'd suggest trying out some other ROMs (possibly even just rooted stock) and starting out with a clean flash, with no mods/kernel changes initially, and see if you still have the issue.

PrizmaticSmoke said:
I've never had those issues on any lollipop ROMs (at least not for this device).
Personally I'm not a big fan of CM, have you tried any other ROMs and/or kernels? Have you flashed a custom kernel or adjusted any kernel settings that could be causing this? Are you using any mods (like Xposed)?
I'd suggest trying out some other ROMs (possibly even just rooted stock) and starting out with a clean flash, with no mods/kernel changes initially, and see if you still have the issue.
Click to expand...
Click to collapse
I'll give that a try.. I haven't done anything to it because upgraded the bootloader to like 4.04 and installed CM12 on it. It ran so good till like a week or so ago and now its just trash. A case with a magnet for sleep mode wouldn't have anything to do with this would it? But first things first, I'll try a simple 5.0.2 rom and see what happens.
Thanks

My device freezes in a black screen

Hey all!
This is happening to me for 2 months now, I was running official 12.1CM and now official 13CM
I tried to also use some stock based rom but im pretty sure it happened there too.
Whats happening to me is that randomly throughout the day my phone's screen turns black and I cant reboot it by any home button combination, only by getting out the battery.
When this happens the phone just totally freezes and I cant get it to respond or make a sound.
I don't think that the phone dies because sometimes when its freezes I can still see the notification led blinking.
Does anyone know why this might happen? or where can i copy some logs that might help you guys figure it out?
Thanks in advance!

sounds like you have the sleep of death issue? Personally I haven't been on CM roms much on my G3 so I haven't really encountered this issue but on my previous phone I've encountered this a few times on CM.
EDIT: Though it shouldn't happen on stock are you sure it happens on stock as well?

I have this issue as well using the Exodus rom. I never had it while using a stock rom, so I think this is a cyanogenmod issue (Exodus is a CM based rom in 5.1).

I have the exact same issue with my vs985. Seems to happen the most when viewing any sort of video, but I have had it happen at other times as well. Pretty dang annoying, probably 3-4 times a day. Using CM 13.0-20151217-nightly-vs985 but it started when I first flashed CM. Never had the issue on stock rooted rom.

Random reboots OOS 4.0.x

Hi,
I'm experiencing random reboots since I've upgraded to OOS 4.0.x (I've had them since 4.0.0, but I've got them too on 4.0.1). My friend has the same issue. I think its weird that I find very little about this issue. I think it happens the most when switching from LTE/4G/Mobile to WiFi and vice-versa. I can not say that the reboots only occur when switching.
OnePlus support suggested me to do a clean flash of the rom. (Isn't that the same as a factory reset? I did not have tampered with my phone.. Everything is stock. (ROM / Kernel..) Even the device is not rooted and the bootloader is still locked..
Are there other people who have this issue?

Nexoez said:
Hi,
I'm experiencing random reboots since I've upgraded to OOS 4.0.x (I've had them since 4.0.0, but I've got them too on 4.0.1). My friend has the same issue. I think its weird that I find very little about this issue. I think it happens the most when switching from LTE/4G/Mobile to WiFi and vice-versa. I can not say that the reboots only occur when switching.
OnePlus support suggested me to do a clean flash of the rom. (Isn't that the same as a factory reset? I did not have tampered with my phone.. Everything is stock. (ROM / Kernel..) Even the device is not rooted and the bootloader is still locked..
Are there other people who have this issue?
Click to expand...
Click to collapse
I have been experiencing the same situation with you. Sometimes during charging, sometimes just randomly.
Your suspect with network/wifi switch could be right as my network quality is quite bad and it jumps around quite frantically. I did clean flash but still issue persists

creezalird said:
I have been experiencing the same situation with you. Sometimes during charging, sometimes just randomly.
Your suspect with network/wifi switch could be right as my network quality is quite bad and it jumps around quite frantically. I did clean flash but still issue persists
Click to expand...
Click to collapse
I see you are using Resurrection Remix with a custom kernel?

Nexoez said:
I see you are using Resurrection Remix with a custom kernel?
Click to expand...
Click to collapse
Not anymore, that was old signature. I have no time to update it [emoji14]
Sent from my ONEPLUS A3003 using Tapatalk

Working fine on my end but I'm using the Chinese A3000. Might be only affecting A3003 and US A3000.

Nope, I got a Chinese one too and i have really got issues with that random reboots, because my alarms dont work anymore after a reboot.

I'm on Open Beta 10 and have the same issue, on a clean flash. See screenshot attached. Not sure what's going on. Phone was plugged in each time but one.

Collegue of mine has the same issue, (also OnePlus3), other friend of mine has also the same rebooting issue. (OnePlus3).
It's weird that I don't find as much information on the internet regarding it..

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!??