When using a kernel with s2w on my Nexus 5 (With any version of CyanogenMod or stock) turning on the screen will cause my device to register taps usually on the lower half of the screen even though nothing is touching it. I've been able to reproduce this with Franco kernel and ElementalX so far, on multiple devices. These phantom touches happen about 80% of the time when unlocking the device either by sweeping across the display or just using the power button. This makes s2w unusable as I can't deal with my phone randomly launching apps or tapping things in whatever app I have open every time i turn it on. Ihave done so much googling and searching through these forums and I can't find anyone with a similar problem. I even RMA'd my device because there was literally nobody else I saw with this issue so I thought it must be a device problem, but my new one does the same thing, What can I be doing wrong?
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.
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.
After installing Lollipop, everything became unbearably slow. I've tried flashing multiple ROMs, both Lollipop and Kitkat, but everything remains so slow: the actual boot-up process and the ROM itself. Does anybody have any ideas about what can be done about this? In fastboot I see hammerhead D820(H) 32GB; HW version rev_11; Bootloader version HHZ12d, Baseband M8974A-2.0.50.2.22. Lock state is unlocked. Any suggestions will be highly appreciated!
Wipe cache and see if that helps and disable Chrome's integration into the app switcher. Also get rid of Facebook and FB Messenger.
Sent from my Nexus 5 using XDA Free mobile app
Instead of Lollypop try some LSD
Thanks. But it is that slow even before any of these apps are loaded (e.g. after I do a factory reset and flash a new rom). Is it possible that Lollipop did sthg to the hardware? If so, how could I find out? Just to give you an idea about how slow exactly it is: when I am typing 5 letters at normal speed, it takes until the fifth letter before the first letter actually displays on the screen. I should also note that when the screen goes off, I can no longer get it on again without a reboot...
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
sdspieg said:
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
Click to expand...
Click to collapse
Probably the replacement screen has been reconnected poorly. There's nothing you can do on software side, for me, it's more like a hardware problem.
Hello!
My oneplus one is having this issue for a while now, When I plug it in and lock the device, there is a 60~70% chance that the display stays on but its just blank, I have to unlock it and lock it again to fix it.
Recently this also started happening when it was not charging and the screen would often stay on causing massive battery drain :/
This happens on every single rom all the way from CM11S up to CM13 and also oxygen os,...
Does anyone know what the problem is?
Thanks,
Noahvt
I have the same problem since I can remember, also looking for an answer.
I have a similar issue. Sometimes the screen stays on, but is dimmed. A simple double press of the power button resolves it (turn on full, turn off screen) but its mildly irritating. I have only noticed it since being on sultanxdas cm12 ROM. I had an issue with a notification LED app not working since a recent ROM update so uninstalled it. Maybe the issue was related to that app as I cant remember the issue occurring since I uninstalled it a few days ago.
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.