[ONE Q&A, Help & Troubleshooting] pesche80:
Hello everybody,

I've got a problem with a Oneplus One.

First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. :p So I'm quite used to replace the display on this device.

Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.

Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).

I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.

A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!

An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.

As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.

Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.

I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.

I also tried to install different original factory images.

cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip

and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.

I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.

I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.

I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.

Unfortunately I've got no luck.

Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.

So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.

I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?

thanks!

p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.

:confused:

I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...

Maybe there is a problem with permissions or the flash memory?

p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX