Related
Hi there,
someone has problems that the touchscreen is not responding?
Have CM11 - current nightly, Fournace kernel 1.0.2 and OPO lockscreen flashed ....,Only the lower right corner is responsive to inputs.
I had the problems also 2 times with the CM11S-ROM.
Has anyone else this problem?
Sun_Dancer said:
Hi there,
someone has problems that the touchscreen is not responding?
Have CM11 - current nightly, Fournace kernel 1.0.2 and OPO lockscreen flashed ....,Only the lower right corner is responsive to inputs.
I had the problems also 2 times with the CM11S-ROM.
Has anyone else this problem?
Click to expand...
Click to collapse
I have the same problem. It's intermittent and goes away after a while but it comes back often enough to make my device unusable when needed. I literally can't answer calls or log into my device because of this. Is no one else having this problem? The issue persists into recovery so it might be hardware.
Franco r13 has new touch drivers implemented. Try it.
OP you say it as if your screen is never responsive, only in the bottom of the screen. That sounds like a RMA.
I will look into Franco r13 tonight. In the meantime, here is how my problem happens:
- Most of the time touch screen is working as expected
- Sometimes the touch screen becomes unresponsive to many areas on the screen, but some small areas still work
- When the above issue occurs, it is only temporary. If I let the phone sit for a few minutes it usually comes back.
- Restarting does not fix the problem, and the problem persists into recovery mode (I forget which recovery I have, but it has touch screen input)
- The problem started with phone being 100% stock, although only after the OTA update a few days ago
notten said:
I will look into Franco r13 tonight. In the meantime, here is how my problem happens:
- Most of the time touch screen is working as expected
- Sometimes the touch screen becomes unresponsive to many areas on the screen, but some small areas still work
- When the above issue occurs, it is only temporary. If I let the phone sit for a few minutes it usually comes back.
- Restarting does not fix the problem, and the problem persists into recovery mode (I forget which recovery I have, but it has touch screen input)
- The problem started with phone being 100% stock, although only after the OTA update a few days ago
Click to expand...
Click to collapse
Yeah, try Franco then. Mine feels better now. It wasn't too responsive before either.
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
i tried 4 or 5 roms lollipop but this issue seem happen with cm12 . Can anybody confirm ?
The issue is the navigation buttons does not turn off after screen turned off (you can check by turn on screen then turn off right immediately , the light still there)
hoangtu2410 said:
i tried 4 or 5 roms lollipop but this issue seem happen with cm12 . Can anybody confirm ?
The issue is the navigation buttons does not turn off after screen turned off (you can check by turn on screen then turn off right immediately , the light still there)
Click to expand...
Click to collapse
i am using AK.068.OPO.SKULL.CM12 Kernal with LiquidSmooth nightly, and this problem seems to be fixed most of the time. - still happens once a while. but much much better now.
I had this with older temasek but v3.3 seems to have it fixed now
Sent From Lollipopified Bacon Goodness!
Hi Everyone,
I am facing this issue sometimes. The display becomes as below (you can see in the screenshot attached). I am on stock ROM and stock Kernel. Have anyone faced the similar issue? Is it a hardware issue ?
jollz04 said:
Hi Everyone,
I am facing this issue sometimes. The display becomes as below (you can see in the screenshot attached). I am on stock ROM and stock Kernel. Have anyone faced the similar issue? Is it a hardware issue ?
Click to expand...
Click to collapse
It's a hardware issue if YOU can see it but it isn't visible in screenshots.
In this case, as it is visible with a screenshot, it's a software bug. Nothing major here, just some random artifacts.
This is known as screen tearing effect and i am assuminh you are on 5.0 lollipop. This issue was mainly seen in 5.0 .. Update to latest 5.1 ..
sent from Bacon (OnePlus One)
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.