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.
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
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.
Hi there,
I'm experiencing massive issues with the Nexus 5 of my wife. Everything is basically broken
It started 2 days ago, the phone start rebooting without reason and heating a lot. Applications sometimes hang for a long time, or the screen stays black with only the notification bar displayed.
Wifi is never able to connect, even though the welcome screen is able to display available wifi. On the welcome screen after a fresh flash, nothing happen when I enter the WIFI password and try to connect. Only the "ignore" button is available, as if I have done nothing.
LTE connectivity seems to work, but I have removed the SIM card for further testing, so it's hard to say.
Parameters screen sometimes works, sometimes won't. Battery consumption screen never works.
The phone is never able to shutdown properly, it hangs forever on the shutdown loading circle; I always have to hard-reboot.
I changed the battery (I had a spare one ordered few days before the problem occurs just to see if it improves the battery life), with no luck.
When I opened the phone to change the battery, it is clear the heat come from the CPU.
I tried (I wiped everything each time in between):
- factory reset
- flash a stock rom from Google website (MMB29K)
- flash latest Cyanogenmod rom (ZNH0EAO2NM)
I have the same issues with any of those 3 roms. I captured some logs while running MMB29K and ZNH0EAO2NM:
Stock (MMB29K) logs: https://drive.google.com/open?id=0B-CDc3nzF3e3M28tM2xjTmJKa28
Cyanogenmod (ZNH0EAO2NM) logs: https://drive.google.com/open?id=0B-CDc3nzF3e3TVUtTmExZDBLUms
The only state where the phone is stable is when TWRP is booted, which is not so useful...
I'm thinking of a hardware issue, but is there anything else I can try? What do you think?
Thanks a lot!
Nobody?
I said the same thing in another post. The fact that flashing different ROMs with the same issues kinda point to hardware problem. I'd guess something fried on the motherboard and it's causing weird behavior. Funny thing, the other post also reported wifi not connecting issues, so I'm thinking there is something that breaks in older Nexus 5 phones that cause wifi issues along with other random reboot problems.
This is my first time installing custom ROM's on my otherwise stock Sprint Motorola photon 4G LTE. After successfully flashing CM13 (2016_08_20 snapshot release), I tried to make a call, and upon hitting "call" from the dialer, the screen goes black and stays that way. The only recourse is to hold down power button long enough to reboot. While the screen is black, there is no sound from the ear piece (i.e. it does not appear that the call is connected). Finally, while the screen is black, the phone does exhibit some reactions: it vibrates sometimes if I hit the power button, in other words, the device is still 'on" until I have to reboot it.
After this happened, I gave up on CM13 and flashed CM-12 (the latest snapshot release, from 2015) , and experienced the same behavior.
The call apparently was completed, because the other party received a missed call. However, there was no sound on my end (although there was side-tone, when I breathed on it)
I googled for about an hour, and saw examples of the same behavior on other devices claiming to be related to the proximity sensor (though in those cases, there apparently was audio in the ear piece-- ie. the call completed, and was in progress while the screen was black). This behavior was not observed a few minutes before under stock ROM in the same device (so doubt it's a strictly hardware issue, so doubt I need to open the device and clean the sensor, per some of the suggestions out there).
I suspect the answer is very basic, because I found no similar threads searching XDA.
Please let me know any ideas. I did not do anything about updating my baseband version from stock before flashing the CM ROMs., but don't know if I have to I'm a noob at custom Rom's and just remembered that you had to worry about the baseband / radio version back on the HTC Evo 8 years ago, which was my last time flashing. Again, the ROM itself worked fine-- wifi and 3G/LTE connectivity was a success.
Let me know any ideas.
thanks
After restoring to stock, dialing worked again on the phone, but the behavior on the device was different from two other photons I tested next to it.
In the stock ROM, the call connected, but the screen turned off immediately upon hitting "call" (even when the phone was on the desk). You could get the screen back (in stock only) by hitting the power button.
In my other two photons, the black screen does not kick-in immediately. So it does appear it could be something having to do with the proximity sensor (i.e. it's always engaged). I don't have the skills to confirm. I am writing-off this phone for now, and have a different device (so not a high-priority thread at this point), but let me know if anyone has any ideas. Thx.
There's a way to validate if the prox sensor is working - zDeviceTest in the Play Store will test all of the hardware, and it will also show the metrics each piece of hardware is receiving - the prox sensor being fairly simple, it just identifies if an object is "near" or "far".
I always recommend making sure everything works in the stock ROM before flashing anything custom - as you need to validate everything works before making tweaks.
My advice is the same as arrrghhhs. (This name really looks like it was typed with a Photon Q with some characters repeated by the device >.>)
I noticed that my proximity sensor sometimes "stuck" to near (I use some different app [SatStat] so it shows 3 cm or 100 cm instead of near/far). Winking a little above the sensor helps sometimes. But your problem sounds like a defect.
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?