Hi guys, I'll try to describe this problem as best I can. I've tried to take a video of this but it doesn't quite work.
Basically about 80% of the screen occasionally starts flickering. It could be a screen refresh issue or a backlight issue or something physically wrong with the screen. The top 20% is absolutely fine!
I've tried flashing different ROMs, Kernels, Radios, used different governors, set force GPU render and set Disable HW overlays.
None of these things work, whilst some appear to fix the problem its over ever temporary. Sometimes increasing the brightness fixes it but not every time.
The flicker has a slight yellowish colour to it too.
I've disassembled the phone and checked the screen connector ribbon etc and all seemed fine.
Has anyone heard or experienced this themselves? Please help!!!
My last option is to do a factory reset and start all over again. Or buy a new screen for £35...
Thanks
Can no one help meh???
Related
Hello,
I had some problems with the camera button on my cingular 2125 but I managed to fix it just by cleaning it with wd40. Unfortunately a couple of days after the issue with the button was fixed I notice that I was not getting any image from the camera sensor - just black screen.
The same time I was playing with the rom updates and now I am not sure if that might be a hardware or software issue. Currently I am on WM6 perfect english v6 and it works perfect except the fact that I am not getting any image form the camera sensor.
When I turn the camera app on it shows the loading icon for a split of a second as usual but then no image but a black screen. I can actually see the camera image area boundary because if has a different shade of black that the background black but thats it. When I turn the COOL EFFECT picture actually goes blue. Playing with brightness and other settings does not help.
Anyone can tell if it is most likely a fried sensor issue or some driver malfunction.
I think its a driver issue.
I've had the same issue with my phone. If I click on the menu and choose the Reset Brightness option the camera goes back to normal, but anytime I try adjust the brighness settings it goes to black and I have to reset the brightness again. Not sure what the problem is.
I tried with every possible setting in the camera app menu but nothing works. Also when making a video it records the sound but not the image.
I guess since there is not that many people with a similar problem I assume a fried camera sensor or some other hardware issue. I am trying to get a new camera on ebay but no luck yet.
Does anyone know if the camera for 2125/spv c600 can be taken from some other model.
The one from the magician looks very similar except the shorter data tape:
http://cgi.ebay.co.uk/Y206-Int-Came...oryZ3728QQrdZ1QQssPageNameZWD1VQQcmdZViewItem
Hi all
Recently started having this issue with my screen - haven't dropped it or anything either. On lighter colored backgrounds there are faint to pretty moderate horizontal lines flickering on the screen. The lines aren't colored or in one specific spot on the screen. It's hard to explain but it is similar to older projection tvs where there are those faint lines(static like) in the background.
I took a screenshot but it doesn't show the lines. I had been using Android Revolution HD 6.1 (great rom btw!!) and I've tried other roms since this began happening (thinking it was the rom) but to no avail. I'm currently running CM7.1.
Things I've tried:
changing roms
turning screen brightness up
turning on automatic brightness
turning down/off various animation settings
turning on light sensor filter in cm7 settings (helps a little)
If anyone can help it'd be greatly appreciated! Thanks for reading!
I would try unrooting, installing ruu from HTC website and see if problem is still there. If it is then you will be back to stock and can claim your warranty. If problem is gone then just reroot. This is a problem I have not read anywhere though so it is probably a hardware malfunction and would need to be warrantied.
Not a bad idea! I'll give it a shot and share the results once complete.
Installed stock RUU - screen lines still present so probably a screen hardware issue. Going to take it into the store tomorrow and see what they can do
Please help. I think my GPU is failing. I have green dots when I turn the phone on, then screen is always shaking, moving upwards and the colours are not displayed correctly. See photos here: imgur[dot]com/a/aMDz0 . The problem with the colours appeared before in the last 2 weeks but I always fixed it by rebooting. Since this morning, it became much worse.
I made a screencast but on the video file everything is displayed perfectly.
Please tell me what seems to be the problem and what solution might I find to solve it. The phone is almost unusable now.
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.
I have reading the forum and tried contacting 1+7 also but they just say switch off nfc and so on but till today (1 month since I bought it ) I still have the problem . while making a call it goes on hold or connects another call or something or the other happens and the other person gets irritated as if I am doing on purpose. I am still unable to solve this will changing rom be the solution or can someone please help I am fed up with this instrument
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
will try out can you advice reset sensors apps
jonsat said:
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
Click to expand...
Click to collapse
will try out can you advice reset sensors apps
Issue is back again after 9.5.9 update.
IEESH said:
will try out can you advice reset sensors apps
Click to expand...
Click to collapse
Search for "Proximity sensor reset" or similar names. Usually apps like that needs root privileges, btw.
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Superguy said:
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Click to expand...
Click to collapse
Disabling double tap to wake resolved my screen wakeup during calls issue...
UPG to 9.5.10 Plz - Issue has disappeared again.
ram4ufriends said:
Disabling double tap to wake resolved my screen wakeup during calls issue...
Click to expand...
Click to collapse
I'll try that, but I don't think I have that enabled. I disabled NFC for the other tap issues and that helped some.
I really wish there was a screen calibration tool. Samsung curved screens have none of these issues.
Do you have a dirty screen protector?
This is a known bug with the proximity sensor, although, actually, I believe the root cause is something else.
Screen does go black, which indicates the proximity sensor is working and recognizes your face is near... But input is still allowed (meaning it does not lock it).
As a result, during a call your face/ear will press whatever is underneath and trigger random actions.
I believe (I hope?) that OnePlus is aware of this issue and they issue a fix.
I think it was briefly fixed for 9.5.9 and then reverted on 9.5.10 since it introduced other issues.
Quality control has been a bit subpar on the OnePlus 7 Pro builds when compared to my previous OnePlus phones...