Develop Bugs

HELP! Phone doesn't wake up

My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!

rossle12 said:
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
Click to expand...
Click to collapse
Stock ROM or custom? Any overclocking?
The phone powers up if you soft reset, correct?

Well, I found out it was a small problem with the rom.
It was a custom rom, and I just installed a different one and it works flawlessly.
With the other one, the light sensor did not work either.
Also, I dropped my phone the other day, and a really small spring fell out.
And the back plain on my screen is loose and opens up easily..

Which ROM?

I hate to hijack this thread but i am having the exact same problem. Basically when i put my phone to sleep its hit or mess as to if it will wake. It seems to have started when i flashed Energy ROM. It was terrible after that, so I switched back to the stock ROM available from the HTC website and all seemed well at first. Now its back to hit or miss.
I cant really rule out a hardware issue such as a broken sensor or something because I'm not sure how the mechanics of it work. When i push the power button on top the phone wakes but not the screen I know this because the 4 lights on the bottom light up and the keyboard as well. I can hit the button repeatedly but it doesnt help. At other times it works flawlessly, but usually does not.
Can anyone give me a suggestion as to what it could be, or a way to rule out a hardware issue?

Exactly my problem!
It was perfectly fine for the first day or so before it started crapping out again..
Can someone please help us with this problem?
It's mind consuming and it's making me worry.
Until TP3 is out, I won't get a new phone ):

Well, the problem is discussed in great detail on the internet, but no one can give a definitive answer. ..
I've been a touch pro 2 user for exactly 3 days... My new HD2 from T-Mobile is in the mail... This is a un acceptable flaw with no real solutiion... Good Luck TP2 users....

Good luck to you.
I've had mine for over two years and it was flawless
Just one recent drop determined everything
Although I Must say, it was one hell of a durable phone

Yea, dont get me wrong. I really like the phone. Thats why I'm getting the HD2. Great OS and big beautiful screen. I'm gonna miss the slide out keyboard but I think thats what breaks these phones.
I'm excited that there's the possibility of running Windows Mobile 7 on it.

rossle12 said:
Can someone please help us with this problem?
Click to expand...
Click to collapse
I'd like to try to help. But you never answered my question of what ROM you are on (and which one you tried previously).

I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now

djowen6565 said:
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
Click to expand...
Click to collapse
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.

HELP: Same problem Phone not waking up
Hi saw this thread and was wondering if anyone can help me.
I have an HTC Touch Pro 2 for some month now...
Using the following details:
OS Version: 5.2.21887 (21887.5.0.86)
ROM Version: 2.07..401.1 (80303) WWE
ROM date: 02/04/10
Radio ver: 4.49.25.91
stock ROM basically...
THe issue is that the phone doesn't wake or when using it just freezes/hangs.
Not much software/apps installed... and memory is good as well.
I just don't know what's going on...
Help please.
Thanks

rossle12 said:
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
Click to expand...
Click to collapse
I'd agree with the notion that its likely hardware related. I've flashed maybe 10 different builds of Energy over the last 7 months or so, and never once had and issue with the SOD (sleep of death) that I can recall. A bad flash can sometimes happen. But since you flashed another reputable ROM (Jackos), that somewhat eliminates the possibility that a bad flash is the culprit.
You can start from scratch, by running Task29 to format the ROM area of the phone's memory, and reflash the ROM. But this would be just to eliminate the possibility of a bad ROM flash. My gut says that you won't see any different results.
Running the phone "clean" for a while (to see if you still have the SOD) without any software installed or any other modifications will eliminate the possibility that any software or mods are responsible for the issue.

are you sure its hardware related? because my phone started doing this yesterday too...I had an energy rom from october, and it was really buggy. I am only able to keep my phone from sleeping when it is plugged in to some power, so i flashed the newest energy rom and still having the same problem...wont wake up from sleep
EDIT:
I dont see how this can be hardware related because everytime i soft-reset, the screen works again. this problem only happens when the device goes to sleep...

Any overclocking?
As I already mentioned, I never had any SODs on Energy that I can recall, except when using OCT (OverClocking Tool).

I have done no overclocking...I just flashed the newest energy rom like 15min ago...is there anything else I can do or check? it looks like the phone works still, just no backlight...

After flashing the ROM, maybe try running it "clean" for a day or two, don't install any software or do any mods, reg edits, etc. If you still have problems with the phone waking up with a new ROM, and no other software or other mods, than it may indicate a hardware problem.
And be sure to run Task29 before you flash the new ROM, if you don't already do that.

You guys should read the following thread:
http://forum.xda-developers.com/showthread.php?t=648134
You're not the only ones (by any means) with the SOD issue. But it isn't at all clear what causes the issue. Lots of different theories in that thread about various software or ROMs, with no clear solution.
Lots of conflicting info, but some comments on the thread suggest (as I mentioned) that Task29 may help (certainly can't hurt).
moto2000 said:
are you sure its hardware related?
Click to expand...
Click to collapse
Nope, definitely not sure, especially after reading the thread linked above. But as I suggested before, Task 29, try a different ROM, and run it clean with no software or mods, and start eliminating the variables.

[Q] Touchscreen stops working

Hi,
sometimes the touchscreen of my defy stops working (but the phone is not frozen)
and the only way to fix it is to lock/unlock the screen...
does anyone have the same problem (and can help me)?
thanks
P.S
i've had the problem both with stock rom (2.2) and with cyanogenmod rc 1.5

When this happens, do the 4 buttons below your display still give you haptic feedback (little vibration) or do they react not at all?
Also, does this only happen when there's the normal launcher/standby screen active or when there's an other app active too ?
Did you undervolt ?
Edit: Also, this seems to be a hardware problem which seems to be well known in a certain German android forum but I cannot find much about it in here. In short, the digitizer unit seems to be broken for some people and locking/unlocking helps because it disconnects and connects power for the digitizer. The people there fixed the problem by replacing the digitizer (which isn't easy at all!).
It would be nice to have someone from XDA who had this problem before too, to confirm this problem!

First of all, thank you for the answer
When I have the problem, 4 buttons stop working too.
It usually happens after a period of stand-by, i don't undervolt or have some other application running than the launcher (ADWlauncher).
I bought the phone one week ago, if it is an HW problem, i can't repair it by myself...

I'd recommend to wait and see whether xda has other suggestions for you and if not, just check the Motorola hotline and ask whether they know something and if they do change it for free.
Also, what you describe fits perfectly to what I've read elsewhere (don't know whether I'm allowed to post a link here or if it were useful at all because it is in German). So it sounds like your digitizer could really be defect.

ok, even if i hope to solve the problem by myself...

News: They've changed the touch screen, but the problem is still present...
Can it be a sw problem??

Keep sending it back, they will replace it in the end.
Sent from my MB525 using Tapatalk

the whole phone?

Yes, the whole phone. They have two year warranties, but don't put up or make do, you should have a phone that works right
Sent from my MB525 using Tapatalk

I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.

I wonder when it happens ,are you charging?

nameite said:
I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.
Click to expand...
Click to collapse
What nightly version are you using?
The problem happens even if i'm not charging...

Phantom or Ghost Touch Screen LG Optimus G

Few days earlier I started to notice this problem after 5 months of use of my device. My screen starts rapidly shaking left to right and front touch panel stop working, it happen when I freshly open an apps. To temporarily fixed it, I have to press power button to turn off the screen. Is it a hardware or software problem?

Did you flashed any rom or kernel?
Do you use trickster?
Some people sayed that uninstalling trickster solved their ghost touches on the keyboard (may not work in your case).
I had a similar problem and was because of a kernel.
If you had modified anything try to use stock for a while and see if the problem persist
Enviado do meu Optimus G através de Tapatalk

Stock, I guess I should wait for official kitkat. Dont have time thinkering my fone atm.

I was ghosts touches on my screen. One was pressed on all sides. To fix it I had to turn off and turn on the screen. I decided to change the touchscreen and the problem was fixed. Now it works ok.
Sorry my english.
Enviado desde mi LG-E975 mediante Tapatalk

where do you get you're replacement touchscreen? any online site that offer spare parts?

yawako said:
where do you get you're replacement touchscreen? any online site that offer spare parts?
Click to expand...
Click to collapse
I bought it on ebay. Screen+touch+ frame. This option:
http://pages.ebay.com/link/?nav=item.view&id=111278902215
But You can buy other options.
1. Touch + screen+ frame (medium dificult)
2. Touch + screen without frame (best option)
3. Only touch screen. (very dificult option)
Many people have told me that the best option is 2, without frame to not be taking off parts that are originally attached to the frame.
You can see totorials on youtube

Ghost Touch now keeps rapidly pulsing at the buttom edge of my screen (portrait) my phone is sometimes uncontrollable. I never thought this kind of newer high end device gets broken so easily under short period of time. I never experienced this from my good old Galaxy Y, Xperia mini and X8 that I accidentally deep under water even now still working in mint condition. So sad with LG products. I was planning to buy LG G Pad but because of this I probably get Nexus 7 instead.
Im going to sell this for $155
Reflash it again with stock firmware twice, problem still persist
Its now a hardware issue

Touch screen seems deteriorating overtime. At first Ghost Touch, then on the next day a dead touch portion just above the home screen panel where the ghost touch first occurred rapidly moving back and then after few days a ghost touch appeared again just below in the middle of the screen (portrait) then after an hour probably about 1.5mm size thickness dead touch. Now a I have 2 horizontal dead touch portion of my screen and probably more to come if I keep using it.

Few days ago i'v got first phaton/ghost touch problem. I used Omni 4.4.4 so
- reflash to clean OmniRom (try few kernels) - the same
- flash to Android L Preview - the same
.....
fu***
Install - ARTMod ROM so 99,9%of stock - and as for now all its ok.
Strange.
Update:
One day and zero problems.

htomasz said:
Few days ago i'v got first phaton/ghost touch problem. I used Omni 4.4.4 so
- reflash to clean OmniRom (try few kernels) - the same
- flash to Android L Preview - the same
.....
fu***
Install - ARTMod ROM so 99,9%of stock - and as for now all its ok.
Strange.
Update:
One day and zero problems.
Click to expand...
Click to collapse
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!

dashcsn said:
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!
Click to expand...
Click to collapse
On this ROM 0 phantom/ghost touch
http://forum.xda-developers.com/optimus-g-intl/development/rom-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342

OK, this is freakin' weird...
I have been running KitKat on my F180S pretty much from the time it got released (different versions: full stock, VDT, Sling...). Yesterday, out of the blue, my digitizer started getting crazy with ghost touches in the upper portion of the screen (around the strip where Q-slide apps usually are in the notification shade, or the clock area on a weather widget where most people have it). This made the phone 100% unusable, as it was constantly registering touches. Rebooted to recovery to do a factory reset, and the problem was persistent in the recovery, too (I am using PhilZ Touch). So, at that point it looked like a hardware issue to me. To clear my consciousness, I opened the phone, disconnected the digitizer, cleaned the connectors, plugged it in again. No dice. Still, I thought about reflashing a full stock KDZ, just for the heck of it (no root, no custom recovery, locked BL). Here is what happened:
1. F180S V30c KitKat - same problem.
2. F180S V30b KitKat (downgraded a notch) - same problem.
3. F180S V20n Jelly Bean - everything is working fine, no ghost touches. Huh?!?
4. Rooted V20n, unlocked BL (Mako method) and flashed CWM using FreeGee - no problem, everything is still OK.
5. Flashed my favourite JB ROM - no problem, everything is still OK.
So, the phone is now running on rooted JB, with unlocked BL and CWM recovery, with no touchscreen problems whatsoever. I may try going to KK again at some point, but will just leave it for now, as I need a stable working phone.
WTF??? I am just scratching my head, trying to understand where the issue came from. It appears to be directly related to KitKat, since eliminating unlocked BL and custom recovery didn't solve the issue, but going back to JB (either full stock, or unlocked BL with CWM) totally cured it. The most bizarre thing is that it started out of nowhere, as I didn't do anything to my phone recently, apart from installing some apps here and there...

kt-Froggy said:
OK, this is freakin' weird...
I have been running KitKat on my F180S pretty much from the time it got released (different versions: full stock, VDT, Sling...). Yesterday, out of the blue, my digitizer started getting crazy with ghost touches in the upper portion of the screen (around the strip where Q-slide apps usually are in the notification shade, or the clock area on a weather widget where most people have it). This made the phone 100% unusable, as it was constantly registering touches. Rebooted to recovery to do a factory reset, and the problem was persistent in the recovery, too (I am using PhilZ Touch). So, at that point it looked like a hardware issue to me. To clear my consciousness, I opened the phone, disconnected the digitizer, cleaned the connectors, plugged it in again. No dice. Still, I thought about reflashing a full stock KDZ, just for the heck of it (no root, no custom recovery, locked BL). Here is what happened:
1. F180S V30c KitKat - same problem.
2. F180S V30b KitKat (downgraded a notch) - same problem.
3. F180S V20n Jelly Bean - everything is working fine, no ghost touches. Huh?!?
4. Rooted V20n, unlocked BL (Mako method) and flashed CWM using FreeGee - no problem, everything is still OK.
5. Flashed my favourite JB ROM - no problem, everything is still OK.
So, the phone is now running on rooted JB, with unlocked BL and CWM recovery, with no touchscreen problems whatsoever. I may try going to KK again at some point, but will just leave it for now, as I need a stable working phone.
WTF??? I am just scratching my head, trying to understand where the issue came from. It appears to be directly related to KitKat, since eliminating unlocked BL and custom recovery didn't solve the issue, but going back to JB (either full stock, or unlocked BL with CWM) totally cured it. The most bizarre thing is that it started out of nowhere, as I didn't do anything to my phone recently, apart from installing some apps here and there...
Click to expand...
Click to collapse
Kinda like my situation.
I have the sprint version of the phone,in every kitkat GEE ROM I have ghost touches, but not in Gproj kitkat ROMs neither in stock or JB.
some weird sh*t is happening here lol

FcoEnrique said:
Kinda like my situation.
I have the sprint version of the phone,in every kitkat GEE ROM I have ghost touches, but not in Gproj kitkat ROMs neither in stock or JB.
some weird sh*t is happening here lol
Click to expand...
Click to collapse
Yeah... But at least in your case the problem seems to be consistent. I was using my phone without any issues, and then it just crapped out for no apparent reason. Nothing changed, same ROM that was working fine before...

kt-Froggy said:
Yeah... But at least in your case the problem seems to be consistent. I was using my phone without any issues, and then it just crapped out for no apparent reason. Nothing changed, same ROM that was working fine before...
Click to expand...
Click to collapse
It started the same way for me.

....
The same thing happened to me. Are you guys familiar with Sky Vega phones? I had a Vega Iron before and also it began having ghost touch issues after upgrading to kitkat. I was frustrated, i also flashed any custom rom i could search and no luck at all. I just sold it recently! and i heard this ghost touch issue is also a common on Nexus 4.

dashcsn said:
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!
Click to expand...
Click to collapse
http://forum.xda-developers.com/optimus-g-intl/development/rom-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342

Hello everybody,
I have the same problem with my LG - ghost touch and dead zones on the display. First installed the ROM from this link - http://forum.xda-developers.com/opti...te-10-t2811342 , but the issue still exist.
Then change the display with a new one. Dead zones vanished but ghost touch doesn't. Tried some other ROMs even the original stock ROM.
When I installed the new display the ghost touch is mostly when I use Facebook Messenger.
What can I do in this situation?

[PROBLEM] - Fingerprint sensor not working

Hi guys, I'm currently on AEX 4.6, everything is running smoothly but all of the sudden my fingerprints sensor is not working as well as the slide options. The actual button works. It clicks so I'm managing to use the phone normally but no u-touch function. I've already tried different roms and nothing seems to work. Has anyone experienced a similar problem? I'm afraid it's a hardware problem.

I'm glad to say that I found the solution for this problem on another thread. The sensor driver might have had an issue, so installing it again will solve the malfunction. After all it wasn't a real hardware problem. Just download the file I'm sending and restart your phone so it'll come back to life again :laugh:
Here's the link:
dropbox. com/s/0gqvvfzae4exi12/sensor.zip?dl=0
PS: it didn't work at first with me. So I sort of gave up then I tried another time and it worked.

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