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?
Related
Hello everyone,
I've been having quite an interesting issue on my NS4G. I'm currently running the latest available CM7 nightlies/gapps, as well with Pete Alfonso's kernel. The underlying system in the phone (radio/etc) is all running the current latest available from Sprint as well.
Now the issue in question, I've been having an issue that seems to be occurring more and more frequently on my phone. Now because I am already running a custom ROM and not just stock, this makes me unsure if the issue is coming from the software, or if there is an actual hardware issue with my phone.
Occasionally (I would say as infrequently as once every 2 days or so) when I unlock my phone with the power button, for a split second after the CRT animation I see my phones screen as all green (with a hint of purple), almost the color you associate artifacting with. Now I am not overclocked, but I am running this custom kernel. But the thing is, I'm not 100% on this, but If I remember correctly I do remember seeing this issue on other kernels as well before (I've been running Pete's for some time now).
I also occasionally experience issues with lets say finishing up a phone call, and my phone may lock up with that green screen w/ purple, and then CM7 will automatically reboot the phone for me. I've also experienced my phone rebooting into "Safe Mode".
Essentially what I am wondering is if anyone can shed some light, are these just software bugs that I am running into that other users are experiencing as well, or is this an issue with my phone?
Thanks everyone!
boktai1000 said:
Hello everyone,
I've been having quite an interesting issue on my NS4G. I'm currently running the latest available CM7 nightlies/gapps, as well with Pete Alfonso's kernel. The underlying system in the phone (radio/etc) is all running the current latest available from Sprint as well.
Now the issue in question, I've been having an issue that seems to be occurring more and more frequently on my phone. Now because I am already running a custom ROM and not just stock, this makes me unsure if the issue is coming from the software, or if there is an actual hardware issue with my phone.
Occasionally (I would say as infrequently as once every 2 days or so) when I unlock my phone with the power button, for a split second after the CRT animation I see my phones screen as all green (with a hint of purple), almost the color you associate artifacting with. Now I am not overclocked, but I am running this custom kernel. But the thing is, I'm not 100% on this, but If I remember correctly I do remember seeing this issue on other kernels as well before (I've been running Pete's for some time now).
I also occasionally experience issues with lets say finishing up a phone call, and my phone may lock up with that green screen w/ purple, and then CM7 will automatically reboot the phone for me. I've also experienced my phone rebooting into "Safe Mode".
Essentially what I am wondering is if anyone can shed some light, are these just software bugs that I am running into that other users are experiencing as well, or is this an issue with my phone?
Thanks everyone!
Click to expand...
Click to collapse
go to the main settings, cyanogenmod settings, display.. turn on the screen off animation. then go back to cyanogenmod settings, lockscreen, delay and timeout, turn both screen timeout delay and screen turned off delay to immediately. that should fix the green screen.
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
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
Hey all! I recently updated from Android 10 to Android 11 OOS 11.0.2.2 and I have a strange issue I didn't have before. On grey/blue backgrounds, the screen dims and changes color a little bit after not touching it for 4-5 seconds. I already submitted a bug report but I just wanted to see if others are having this issue. I do have a T Mobile device that's been converted to global, but again this issue wasn't present before. I can't report as to whether the issue happened on OOS updates previous because I just updated and got 11.0.2.2. I've also linked a short video here showing the issue. If you guys have any input at all, it's appreciated!
I may be having a similar issue. I am trying to view your video to see if it is the same problem. I have noticed that my color turns warm, as if the blue light filter was activated. It normally happens when I am trying to type in a field. In most situations, it happens when there is a lot of white being displayed.
I did not pay attention to the browser that I was using. It may be a Chrome issue, but that is only if we are experiencing the same thing.
Ok, so we are talking about two different things. But, your dim is very subtle, at lease as far as the camera is concerned. Does mine do the same thing? No idea. I probably never noticed.
However, are you using Adaptive Brightness or manual brightness? In my experience, OOS 11 came with a LOT of bugs. I've been getting screen orientation problems as of late, and it would lock my screen sideways depending on what I am doing. I do not use auto rotate, and I am certain that I didn't press the rotation button in the bottom right corner. Even if it showed up, it shouldn't have, as I was using my phone in portrait mode every time that bug showed up.
TL;DR: OOS 11 - YMMV.
AarSyl said:
Ok, so we are talking about two different things. But, your dim is very subtle, at lease as far as the camera is concerned. Does mine do the same thing? No idea. I probably never noticed.
However, are you using Adaptive Brightness or manual brightness? In my experience, OOS 11 came with a LOT of bugs. I've been getting screen orientation problems as of late, and it would lock my screen sideways depending on what I am doing. I do not use auto rotate, and I am certain that I didn't press the rotation button in the bottom right corner. Even if it showed up, it shouldn't have, as I was using my phone in portrait mode every time that bug showed up.
TL;DR: OOS 11 - YMMV.
Click to expand...
Click to collapse
So I have the same thing with the screen going super warm on white backgrounds too, primarily on web browsers. With the other issue it only happens with the brightness between 30-70% or so and the screen gets darker and the gamut seems to get a tad cooler but I've chalked these up to separate issues. No phone is without faults but it seems like Oneplus releases software without testing it at all.
Edit: I noticed the yellowing on Chrome, and nowhere else on the phone. Samsung internet does have the same issue
Yes, I have a slew of issues with Android 11. My problem is the fact that I like it a lot more than A10 w/OOS, sooo....I have no option but to tolerate them for the moment.