Hey Everyone.
I have had this issue for about 5 days now, I started out on CM 12.1 when I started to notice random black screens which required a reboot. Prior to this it has been fine for a few months.
Since then, I have tried a new ROM each day, CM 13, SLIM, RR and Mokee.
All seem to start out fine, restore apps from playstore / settings, phone performance is good.
The next day however is when the issues seem to arise, Sluggish behavior and random black screens which require reboot.
Has anyone else seen such behavior? Im a bit stuck, starting to think there is an issue with the phone.
Thoughts? Suggestions?
Thanks.
did u use ambient display?
try to disable it
faizauthar12 said:
did u use ambient display?
try to disable it
Click to expand...
Click to collapse
Everything under display is disabled except "Adaptive Brightness"
Fastboot flash and then try your desired rom
Related
I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
akaja24 said:
I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
Click to expand...
Click to collapse
Are you completely stock? Any custom kernel? Any rom?
Usually it's a kernel issue - tearing, but it's only present on custom kernels (never came across on the stock cm11 kernel). You might wanna try a different kernel though, if you're comfortable with that.
I have the same issue on my stock rom with stock kernel. the only thing i have changed was the developer options. i changed the screen animation time.
mupper said:
I have the same issue on my stock rom with stock kernel. the only thing i have changed was the developer options. i changed the screen animation time.
Click to expand...
Click to collapse
Was it working before those changes?
edit:
Perhaps this might help?
http://forum.xda-developers.com/oneplus-one/general/ghost-touches-flickering-graphics-t2900756
akaja24 said:
I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
Click to expand...
Click to collapse
I had exact same issue during recording a video yesterday night !! I am latest mahdi and latest franco...
Funny thing is it went away once i exited the camera... what rom and kernel are u using ?
I've been having the same issue too. I don't have a solution for you, though. I haven't been able to find much about it.
Same issue here, stock all the way, only been since latest update. The update didn't flash properly, it gave an error stating it couldn't be located but i went through the files and it was there and then upgraded OK
I had the same problem. Selecting "Force GPU Rendering" in developer options cured it.
i have stock everything. i'm not rooted.
a reboot fixes the problem temporarily. shoot, all the issues i've ran into with this phone thus far (like the GPS not locking on) is fixed by a reboot. i know a reboot is good to do every now-and-again regardless, but having to do it constantly to fix issues is the sign of a failing device and is very annoying; it shouldn't be something you have to do with a brand new device.
i am facing this too randomly. Am on rooted 38R with Franco kernel. Rebooting is a temp cure but it will frustrating to keep doing it.
This happened to me after getting 38R. Fortunately it hasn't been back since a hard reboot. It would show up on Youtube & when dragging down the notifications area.
I had this today on PAC ROM. When I unlock phone and lock ring animation dots flash up made lines come across screen not sure what it was or why. Just rebooted phone. Back to normal. But trying out vanir later tonight try something abit different.
Also experiencing this here.
Stock ROM, clean 38R install.
Stock kernel.
Rooted, with a few xposed modules.
Started a day or two ago. Haven't found a way to recreate it. When it does happen, a reboot remedies it, but only temporarily.
I will attempt to screenrec it the next time.
I find it interesting that I only see mentions of this starting recently.
Same problem for me since the last update. Restarting the Phone solves the problem for some times. Maybe a driver issue?
Glad to see that it is not a hardware issue.
Same here
Same here, mahdi-2.8-bacon-20141001 ROM, enabled "Force GPU rendering" in Developer options, let's see if this comes back!
I have the same problem on latest cm nightly with stock kernel. And dev options works sometimes but it resets on reboot and my phone reboots randomly all the time. I'm starting to hate this device
Sent from my A0001 using Tapatalk
I also have the same issue on Stock 38R update + franco kernel r27
It happens after the latest kernel update, before I never had this lines.
Lucky for me I don't have any reboots now but I fear that will come to pass as well.
Got the same problem with Mahdi Rom 2.8 - 20141016
Will be solved in Franco Kernel r28,he just confirmed this on his kernel thread.
Sent from my OnePlus One using XDA Free mobile app
same issue here. i have to reboot. its happened on stock and AK kernel. will try enabling force gpu rendering and see if it comes back
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. 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.
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
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
pesche80 said:
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
pesche80 said:
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. 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.
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
Click to expand...
Click to collapse
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Click to expand...
Click to collapse
Thanks!
I'm going to consider a new display... but not a new gf
pesche80 said:
Thanks!
I'm going to consider a new display... but not a new gf
Click to expand...
Click to collapse
Don't forget to invite me to your wedding.
Hi guys,
I'm running OOS Stable Pie on my OnePlus 6. I know I'm also running Magisk and a custom kernel (blu spark) but I don't know why it would have to do with my issue. It also happenned to me with Radioactive kernel.
So basically, randomly, when I wake up the screen, I can tell the screen tones have changed and when I go to settings, I can see that "srgb" is selected, however, if I select "default", then the colors don't change, and then if I select "srgb" again, then the colors go back to what I picked earlier, before turning on the screen.
It happenned to me a few times now, and I think it always happens after waking up the screen. I don't think it happens while the screen is on.
I didn't change any display settings in kernel apps such as Kernel Adiutor.
Am i the only one affected by this bug? Is this known? Is there a fix that should come?
Thanks for your help.
Up
same here
both OOS and HOS 9.0
xxal said:
same here
both OOS and HOS 9.0
Click to expand...
Click to collapse
Thanks for reporting the same bug. it's kind of reassuring that I'm not the only one affected. So we can hope for a fix for next update! It really makes my eyes bleeding back to default settings
Did you guys ever noticed phone randomly switching screen to saturated mode?... Happens randomly, kind of often.
While in settings it will still show you're on sRGB or natural, but actual calibration jumps to what looks is AMOLED white gamut. Switching it back to your preferred mode fixes things for some time until the next random switch.
I'm not sure if this is rom related or not, seems like I had this problem on multiple OBs and stables on Android 10, with different kernels.
Currently on OB12 + xXx + arter kernel and this issue is present.
I guess I'm the only one having this problem... one every OOS beta and latest stable with stock kernel, screen calibration literally jumps to wide gamut after locking/unlocking the screen.
Ice Bear has experienced this issue ever since upgrading to OOS 10 and it's been this way since the first version of OOS 10. Screen calibration was fine on OOS 9.
I noticed the switch happens when you receive a call almost 90% of the time. I had this problem since 10.0.0 and on beta as well. I provided system logs to help OnePlus teams to track this bug down and since then, I switched to vivid and did not bother much. Currently I don't know if it still exists, what's your build?
Just downloaded the Beta 2 OTA from google's site: https://developer.android.com/preview/download-ota#
Go get it!! Already downloaded and installed on my P4XL. Checking it out now.
Yup just downloaded and flashed and have root still??
Currently on it! Improvement in animation in some places, better landscape to portrait transition.
Missing clock option from themes
Music player now looks better, I think no more an experimental feature.
Final api released good for developers.
Recently screen tweaked a bit no share option anymore.
Yet to find other changes
---------- Post added 09-07-2020 at 12:25 AM ---------- Previous post was 08-07-2020 at 11:47 PM ----------
Restart button vanished from power menu! Great
Updating my Taimen now. About to be in a meeting so I need my Coral working, do will update later.
From Coral, with Tapatalk
Problems I have noticed are
The screen flickers a lot especially when using dark theme and a dark themed app.
I'm also missing new media controls.
Anyone got these problems?
does the navigation bar still remain on the home screen even on beta 2?
Flickering here too
Rotten Ross said:
Problems I have noticed are
The screen flickers a lot especially when using dark theme and a dark themed app.
I'm also missing new media controls.
Anyone got these problems?
Click to expand...
Click to collapse
I have the flicker issue too, media controls are there though.
I've noticed there's no longer the option to force 90hz now either in developer settings which I presume would resolve the flicker issue.
CodeFox said:
I have the flicker issue too, media controls are there though.
I've noticed there's no longer the option to force 90hz now either in developer settings which I presume would resolve the flicker issue.
Click to expand...
Click to collapse
Just done a quick test and turned brightness up above 70%ish the flickering stops or just isn't noticeable.
Flicking is so annoying.. is there any fix?
Maybe custom kernel? I can't watch on this stroboscope
Anyone got Magisk working on the new beta? The canary build that was reported working on beta 1 isn't booting for me. (I never tried beta 1 myself.)
Here is my experience...
1) The flickering screen is annoying
2) I had no problems rooting via Magisk
2a) After rooting my Messages app stopped receiving messages but I was able to send them without issue
2b) I could not update apps from the Google Play store. It would just say "Downloading" but nothing would happen
2c) The Google weather widget on the home screen would not show the weather nor would it take me to Google weather when I clicked it. It seemed disabled.
I have since re-flashed the latest Beta but didn't root. All of the above issues, aside from the screen flickering, have been resolved,
Lots of flickering
Terrible flickering...
The flickering exists also at Beta 1 but only at very low brightness (environment and system brightness). Now screen flickering regardless of environment and system brightness (except at extreme high system brightness...) as long as background is not totally black.
Flickering sucks! OMG! No media controls here but do have force 90hz option still
Hopefully the flickering issues can be fixed with a 2.5 patch or maybe play services/kernel update ??
tardis_42 said:
Anyone got Magisk working on the new beta? The canary build that was reported working on beta 1 isn't booting for me. (I never tried beta 1 myself.)
Click to expand...
Click to collapse
I have tried a few ways no luck yet.
As for other people the flicking screen I have it in this beta . I had it before Beta too, It's the 60hz - 90hz refresh rate. Sucks to say but if you disable it fixes the problem.
I don't see the flickering on my device. Yes to using dark mode, force dark mode, enabling 90 Hzv display (no more force), and playing a couple games at well as watching videos, reading news...
It never shows. Or else I am not recognizing it - and I'm pretty sure I know what flickering means, so....
I do use figure mode to automatically pause most of my games and SoS I don't normally use at work during work hours, so maybe that is why?
Or else something else I might have done?
From Coral, with Tapatalk
I thought mine wasn't doing it to until just now. In dark room and looking at chrome settings while using dark mode. The grey background flickers like crazy... On a positive note at least it's safe to to back to Android 10 July without face unlock breaking
Anyone who is missing the new media controls, found any way to get them to work yet?