I purchased a Nexus 4 8GB on launch day. The device consistently (multiple times per day) would be non-responsive to my touch on the lock screen when I pushed the power button to do a PIN unlock. I had to cycle the power button to get it to respond to my touch.
I called in an RMA the other night, Google overnighted a new phone to me. The same problem occurs, I haven't installed ANY programs. What are the odds it's hardware and not software?
Does nobody else have this problem???
I can replicate it: Turn the screen off, put five fingers on the screen, at the same time push the power button to bring up the unlock screen. My screen will usually not respond, or it delays a response by a couple seconds. It can take a couple attempts to get it to do it.
The only thing I added was the Google News and Weather widget to the main screen.
crazeco said:
I purchased a Nexus 4 8GB on launch day. The device consistently (multiple times per day) would be non-responsive to my touch on the lock screen when I pushed the power button to do a PIN unlock. I had to cycle the power button to get it to respond to my touch.
I called in an RMA the other night, Google overnighted a new phone to me. The same problem occurs, I haven't installed ANY programs. What are the odds it's hardware and not software?
Does nobody else have this problem???
I can replicate it: Turn the screen off, put five fingers on the screen, at the same time push the power button to bring up the unlock screen. My screen will usually not respond, or it delays a response by a couple seconds. It can take a couple attempts to get it to do it.
The only thing I added was the Google News and Weather widget to the main screen.
Click to expand...
Click to collapse
did it hppen will charging???mny facing this problm....with quad core cpu 2 gb ram so smooth it should be...have try install launcher???i watch the video in other web...it so frustating..mayb upgrade/update jelly bean solve the problem..i dont know just guessing...mayb that y it upgradeable...
crazeco said:
I purchased a Nexus 4 8GB on launch day. The device consistently (multiple times per day) would be non-responsive to my touch on the lock screen when I pushed the power button to do a PIN unlock. I had to cycle the power button to get it to respond to my touch.
I called in an RMA the other night, Google overnighted a new phone to me. The same problem occurs, I haven't installed ANY programs. What are the odds it's hardware and not software?
Does nobody else have this problem???
I can replicate it: Turn the screen off, put five fingers on the screen, at the same time push the power button to bring up the unlock screen. My screen will usually not respond, or it delays a response by a couple seconds. It can take a couple attempts to get it to do it.
The only thing I added was the Google News and Weather widget to the main screen.
Click to expand...
Click to collapse
I just tried doing that around 10 times and I couldn't get my screen to not respond. Have you tried flashing a different rom to see if it helps? Switching roms is the best way to pinpoint software or hardware as a culprit.
yoft1 said:
I just tried doing that around 10 times and I couldn't get my screen to not respond. Have you tried flashing a different rom to see if it helps? Switching roms is the best way to pinpoint software or hardware as a culprit.
Click to expand...
Click to collapse
I updated to 4.2.2 ... I can still get it to become non-responsive. Try hitting numbers very quickly after you hit the power button. Make sure all five fingers are on the screen when you hit the power button.
I also have this issue. I press the power button to turn the screen on, and it will be unresponsive until I turn the screen off then turn it on again and all is fine. Sometimes it is just really laggy for 10 seconds, then it returns to normal. I am thinking this may be a bug in the stock kernel, but I'm not sure.
What programs do you have installed and which widgets do you use? Give me a complete list.
How many Google email accounts are added to your phone?
Sent from my Nexus 4 using Tapatalk 2
crazeco said:
What programs do you have installed and which widgets do you use? Give me a complete list.
How many Google email accounts are added to your phone?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I use apex launcher, have the Google now widget and clock, and only one gmail account. I still think it is the stock kernel, I have flashed Franco's kernel this morning, and have yet to encounter the issue. I will report back at the end of today of the results.
I am rooted and have been encountering this in stock 4.2.1 and 4.2.2 and CM 10.1.
Why do you think so few people notice it? Now that I've had it on two separate devices... It has to be software/kernel. Please do update.
Sent from my Nexus 4 using Tapatalk 2
Franco's kernel didn't work. Still have the issue, though less occurring.
---------- Post added at 06:25 PM ---------- Previous post was at 05:59 PM ----------
Okay, so if there is any multi-touch on the screen when it is turned on, it will be unresponsive. The OP says put five fingers on the screen and turn on the screen (while still holding the fingers on the screen). However, the same results can be replicated by only having two fingers and turning on the screen. What this means is, say, if you are holding the phone, and your thumb and finger are on the screen (on the sides, even barely) and turn on the screen, you will get an unresponsive touchscreen.
Multi-touch still works so it isn't a defective touch panel. I don't think this is any hardware issue other than the hardware used in the few affected phones could be of a different revision number, so the kernel isn't working with it the same as the commonly used panel. I could be wrong, but this is just the conclusions I can draw from this.
Is there an official Google thread or report on this issue?
I can confirm it will do it with just two fingers.
Sent from my Nexus 4 using Tapatalk 2
Same thing here. Just don't touch the screen when turning it on.
Sent from my Nexus 4 using xda premium
crazeco said:
Is there an official Google thread or report on this issue?
I can confirm it will do it with just two fingers.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I don't think there is an official Google thread for this issue yet.
crazeco said:
Why do you think so few people notice it? Now that I've had it on two separate devices... It has to be software/kernel. Please do update.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I don't know what to tell you. I've tried it with every number of fingers from 1 to 5 on the screen when I turn it on. I've tried it with and without a PIN. In no way shape or form can I get my screen to lag. I told you before to wipe and try flashing a different rom as that is the most comprehensive way to separate a software issue from a hardware issue. Not updating, but root, wipe, and flash.
Sent from my Nexus 4 using xda premium
yoft1 said:
I don't know what to tell you. I've tried it with every number of fingers from 1 to 5 on the screen when I turn it on. I've tried it with and without a PIN. In no way shape or form can I get my screen to lag. I told you before to wipe and try flashing a different rom as that is the most comprehensive way to separate a software issue from a hardware issue. Not updating, but root, wipe, and flash.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well it's a lot problem that exists for other people in the thread as well. I've had two separate devices, both factory settings with no software installed that do it.
I wish I could try out your device...
Sent from my Nexus 4 using Tapatalk 2
Using Franco's kernel, I have only run into the issue while turning on the screen once, where as I have encountered it many times a day before. I could also be that I know what causes it, so I subconsciously attempt to turn it on with nothing touching the screen, but I don't know.
It seems I have found the issue. I have deleted all lock screen widgets and it seems to fix it. Google, next update please fix this.
Related
is it normal that my touchscreen goes nuts sometimes? I find that sometimes (usually at night or first thing in the morning) my touchscreen on my n1 is inaccurate. I'll touch in the middle of the screen and it will click on something on the bottom of the screen. if I reboot my phone, the phone works great again.
yes its normal, its been posted here that even stock rom will get that problem now and then. Although mine has been random, not at a certain time.
Google is working on a software fix for it, and cyanogen 5053 (for my experience) has cut that problem to a minimum. I think ive experienced that problem 2 times since flashing. So a span of 3 weeks it happend twice. So i say its been pretty good.
And you dont need to reboot, just turn off the screen and turn it back on. Last i had a problem, i did that and it worked.
So as soon google fixes it im sure this board will be flooded with threads about it. And the devs are fast enough to implement it to their ROMS!
Are you holding it differently at those times? You mentioned at night or in the morning. Are you still in bed? I find I sometimes grip the phone is a way that my hand touches the edges of the screen. That throws off the touches and I've noticed it jumping down to a different icon at times. Just make sure your hand doesn't wrap around to the front of the screen.
My nexus one touchscreen will go nuts at times too. Locking the phone and unlocking does fix it though. I'm also 100% positive it has nothing to do with erroneous input from the way I'm holding it.
ya I was making sure that I wasn't holding it weird. hopefully Google makes a fix : )
p.s. thanks for the tip on turning off the screen rather than rebooting the device.
mine does this too but it seems that if I just put it to sleep and wipe it off it's back to normal
Sent from my HTC Dream G1 using the XDA mobile application powered by Tapatalk
Mine too does this w/ cyanogen 5053. sometimes it's so bad that i cannot even unlock the phone. I never noticed it this bad before on stock... but then again i only used stock for about two weeks before i rooted it.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I'm on a non modded phone and I get it every once in a while. Hit the power button and all is well.
It has happened several times caused by various apps such as chrome, play store, dolphin after downloading something. Screen freezes and system eventually resets on it's own. Is anyone else having this problem?
Build: JOP40C
Same here, restarted and frozen 3-4 times in couple of hours.
I was browsing, using apps, dowloading in background, loads of syncing etc - maybe taxing the system causes it? (But i though it should handle it a bit better...)
I had a couple of reboots but no freeze before the firmware update.
After the update it hasn't rebooted but it froze once
Sent from my Galaxy Nexus using xda app-developers app
I've had exactly what you are saying. I had it three times and haven't had it since. Will update if problem persists.
Sent from my SCH-I535 using xda app-developers app
My keeps loosing Wi-Fi and completely shut down every time I turn it off and didn't turn back on in 5 seconds. Making things worse I have to wait several minutes until it allows me to turn it on by pressing power for a 5 seconds. In those few minutes it does not react on power button at all.
Factory reset did not help. Sadly it looks like I have no options other than return it back.
+1 reboots and freezing. Don't really want to return it since its finally rooted and cust recovery. Anyone think waiting for cust Roms will help?
Sent from my Nexus 10 using Tapatalk 2
No need to return the tablet for software issues.... Updates will come quick. That's a Nexus!!!
Sent from my Nexus 10 using XDA Premium HD app
Mine had been randomly restarting after installing some of my apps. I finally narrowed it down to HD Widgets and haven't had a reboot since uninstalling it.
I am not using HD Widgets and I get restarts periodically. What is the most efficient way to submit a bug report to google.
Sent from my Nexus 10 using Tapatalk 2
Just got an RMA for mine for the same issues u guys are experiencing. Wifi disconnecting and chrome freezing and rebooting. Looks like it may not be a hardware issue. Wonder if I should just keep it and wait for an update.
Edit - It was fine before the software update. Probably should ignore it once I get my replacement unit
I am also seeing the reboots happening every 3 to 4 hours like clockwork. I didn't have the device for more than a few minutes before the first update was pushed to it, so I can't say whether or not that was related. I do have HD Widgets installed, so I will pull it off and see if that helps slow the reboots down.
I'm using BootLog Uptime to keep track of the number and frequency of reboots. If this pattern holds, my money is on some kind of memory leak... just thinking from our own development experiences. Given how much higher the resolution is on the N10, I wouldn't count out some graphics heavy apps blowing through their heap much, much faster than on any previous Android device. We'll have to wait and see.
Just called Google and asked for replacement. I hope they aired new updates at the time my replacement arrived.
BTW, I had to initiated factory reset five or six times until it finally clears all data. Never saw Google product so buggy before.
That's a real bummer. Mine doesn't reset or display any of those problems. I have a tiny bit of light bleed in one corner at full brightness and the screen seems to have gotten a little more yellow over time... maybe just the glue drying. If any of you are brave and don't want to return right away, unlock the bootloader and reflash the stock image from google and see if that fixes things. It can help if there was some sort of corruption when you updated.
You may want to wait on that RMA. I had the same trouble with HD widgets installed.
No trouble at all since uninstalling...
dankerton said:
It has happened several times caused by various apps such as chrome, play store, dolphin after downloading something. Screen freezes and system eventually resets on it's own. Is anyone else having this problem?
Build: JOP40C
Click to expand...
Click to collapse
I've never even touched hd widgets and have had two lock ups since I got it on Friday. Both occurred when task switching back to chrome and it was loading a previously viewed web page. Both times I was able to tap the power button to shut off the screen but couldn't wake it up. It eventually reset itself. It boots in like 5 seconds so it's not too terrible to wait for a software update, but I wonder what is causing it?
I think Chrome has some major bugs to be squashed when running on this device....mine has only crashed when browsing. That said, after uninstalling HD widgets, no crashes since...
NiXXeD said:
I've never even touched hd widgets and have had two lock ups since I got it on Friday. Both occurred when task switching back to chrome and it was loading a previously viewed web page. Both times I was able to tap the power button to shut off the screen but couldn't wake it up. It eventually reset itself. It boots in like 5 seconds so it's not too terrible to wait for a software update, but I wonder what is causing it?
Click to expand...
Click to collapse
I'd like to update my results. From last night, just like djflan, I removed HD Widgets and so far, 7 hours later, the crashes are gone. So I have my fingers crossed that I've found my culprit.
Also, I installed the HoloWeb browser and I have found it to be quite a bit quicker and more stable than Chrome. For those of you have issues with Chrome it is worth a few moments to track this app down (here on XDA) and give it a try.
Some of you may not have remembered or gone through the Android 3.x transition, but these kinds of issues were very prevalent during that update as well. Many developers simply don't or can't test on a wide enough range of devices and OS combinations to catch all the issues, or they rely heavily on assumptions or code that "always worked fine" in the past. I think we're seeing the same sorts of behaviors again with 4.2, so it will take a couple of months for it all to shake out.
For now I think I have a stable configuration on the Nexus 10 and I'm sticking with the device. No RMAs will solve issues that are software related in my case.
Removed hd widgets, no crashes yet.
I get the same random reboots and I've never used the fancy widget app. it has happened 3 times already. One I was browsing, another time deleting a widget and the last one when I tried to change the wallpaper. Everytime I had to hold the power button 5-6 seconds until it reboot
Enviado desde mi Nexus 10 usando Tapatalk 2
I spoke to soon earlier... I actually had 2 restarts today. Once while chrome attempted to open a link from tapatalk and another while trying to load one of the free magazines in the play app.
I don't have hd widgets installed either
Sent from my Nexus 10 using Tapatalk 2
My device constantly freezes when I try to unlock it. The lock screen comes up when I push the power button and it's randomly completely non-responsive. I will lock the screen again with the power button and repeat the process and it will then work.
Anyone else having this problem on their Nexus 4?
I've tried disabling lock screen widgets with no help. All I am left to wonder is whether it's from an application I've installed.
If I want to completely reset the phone and remove any fragments of old applications, is doing a factory reset enough to get this done?
crazeco said:
My device constantly freezes when I try to unlock it. The lock screen comes up when I push the power button and it's randomly completely non-responsive. I will lock the screen again with the power button and repeat the process and it will then work.
Anyone else having this problem on their Nexus 4?
I've tried disabling lock screen widgets with no help. All I am left to wonder is whether it's from an application I've installed.
If I want to completely reset the phone and remove any fragments of old applications, is doing a factory reset enough to get this done?
Click to expand...
Click to collapse
Yep , not as much as u though , and never since installing AOKP
drawde40599 said:
Yep , not as much as u though , and never since installing AOKP
Click to expand...
Click to collapse
How often on stock 4.2 did you have the freezing?
crazeco said:
My device constantly freezes when I try to unlock it. The lock screen comes up when I push the power button and it's randomly completely non-responsive. I will lock the screen again with the power button and repeat the process and it will then work.
Anyone else having this problem on their Nexus 4?
I've tried disabling lock screen widgets with no help. All I am left to wonder is whether it's from an application I've installed.
If I want to completely reset the phone and remove any fragments of old applications, is doing a factory reset enough to get this done?
Click to expand...
Click to collapse
Happens to me once every two days.
Sent from my Nexus 4 using xda app-developers app
I had random reboots from lock screen. I wiped and flashed the factory image. I haven't had the issue in the last 3 days.
Sent from my Nexus 4 using Tapatalk 2
8gb Nexus 4 stock
No issues at all.
jasonwc said:
I had random reboots from lock screen. I wiped and flashed the factory image. I haven't had the issue in the last 3 days.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I spoke too soon. My phone just locked up while in a deep sleep overnight. I had to Power + vol down to restart it.
+1 . Mine generally freezes overnight. When I got to unlock my nexus 4 to check the time I find the phone frozen on the lock screen then the phone reboots itself. I did a factory restore, did a factory re-flash, and nothing seems to help. Today I shut off google now to see if that was the issue. Reading through various threads it seems the problem is widespread and across multiple nexus devices including the nexus 7 and galaxy nexus. This gives me some faith that the phone itself maybe fine. Google please fix ASAP. I need my alarm in the morning, not a frozen phone. :crying:
---------- Post added at 12:21 PM ---------- Previous post was at 12:15 PM ----------
Just to add, I did a bug report and called tech support. Nothing I mentioned seemed like news to my tech nor did he have any recommendation other then to RMA. I told him I would give the phone another week to see if anything improves its stability. I still have my Gnex as a backup. I have not noticed any issues with 4.2 on my Gnex but then again it's been in my backpack since my nexus 4 arrived. Perhaps I will leave my Gnex on as we'll to see if I run into any issues with it.
Lock screen freezes once or twice every day, the fix is easy, just press the sleep button again, but its still annoying. 4.2 has pretty bad quality control.
i had the same issue on my old N4. Especially when i got incoming call, lock screen freezes all the time
I will get replacement tho..
crazeco said:
My device constantly freezes when I try to unlock it. The lock screen comes up when I push the power button and it's randomly completely non-responsive. I will lock the screen again with the power button and repeat the process and it will then work.
Anyone else having this problem on their Nexus 4?
I've tried disabling lock screen widgets with no help. All I am left to wonder is whether it's from an application I've installed.
If I want to completely reset the phone and remove any fragments of old applications, is doing a factory reset enough to get this done?
Click to expand...
Click to collapse
I had the same issue. Seemed to be related coming out of the lockscreen after having done some BT music playback. Anyway, I had this "lockscreen widget disable" app installed. Removed it again, and now I have not had any lockups in the last 3 days.
I'm glad to know I'm not alone here. I did a full reset and I still have the problem. I get a lock 4-5 times a day.
I do use bluetooth and google music...
Knowing other people are having this issue really makes me think it's software and not hardware.
i notice that when mine freezes on the lock screen, [i use a pattern], that pressing the power button to turn the screen off then back on solves the problem.
crazeco said:
My device constantly freezes when I try to unlock it. The lock screen comes up when I push the power button and it's randomly completely non-responsive. I will lock the screen again with the power button and repeat the process and it will then work.
Anyone else having this problem on their Nexus 4?
I've tried disabling lock screen widgets with no help. All I am left to wonder is whether it's from an application I've installed.
If I want to completely reset the phone and remove any fragments of old applications, is doing a factory reset enough to get this done?
Click to expand...
Click to collapse
This is the only disappointment for me, having to press the power button a few times in order to unlock this damn phone.
Power to turn screen on, frozen touch, power to turn screen off, power to turn it on again and the it registered touch.
I am surprise not many have this problem.
A friend of mine ordered at the same time as I did, and does not have this problem.
Feels so stupid having to turn the screen on and off a couple of times to get into the homescreen.
Especially when friends asked to play with the phone and the damn thing wont unlock, and I have to explain to them the process of unlocking the phone.
I want to rma, but shoot, might not get a replacement till next year.
unfaix said:
This is the only disappointment for me, having to press the power button a few times in order to unlock this damn phone.
Power to turn screen on, frozen touch, power to turn screen off, power to turn it on again and the it registered touch.
I am surprise not many have this problem.
A friend of mine ordered at the same time as I did, and does not have this problem.
Feels so stupid having to turn the screen on and off a couple of times to get into the homescreen.
Especially when friends asked to play with the phone and the damn thing wont unlock, and I have to explain to them the process of unlocking the phone.
I want to rma, but shoot, might not get a replacement till next year.
Click to expand...
Click to collapse
RMA won't help a software defect, which it is 100%, it's freaking annoying and makes me think google literally makes the phones and never uses it to see if it has any bugs.
Same problem here. So it is hardware related?!
doquentin said:
Same problem here. So it is hardware related?!
Click to expand...
Click to collapse
Any updates on this issue? My lock screen still freezes.
Never had one, probably a rogue app.
You might have 3rd party application on the lock screen that does this?
Sent from my Transformer Pad TF300T using Tapatalk HD
doquentin said:
Same problem here. So it is hardware related?!
Click to expand...
Click to collapse
I think I've had it happen 2 or 3 times so far. I don't think it's hardware related, it seems to be software to me.
I figured out the first time it happened, if I grab and slide up to launch Google Now, it lets me unlock it. So it definitely isn't hardware, as it is registering touches.
Hey folks,
After updating to 4.2.1 on my Nexus 4, I've been noticing lately the following issues:
1) If I am on a call and I want to do something else, I cannot do anything at all even when I press the power button so I can see the screen.
2) If someone calls me, sometimes the screen won't be on and I can't see who's calling and can't answer. Or it'll show up for a few seconds and boom, same thing. Same issue when ending a call.
3) If I am using my phone and after 15 seconds the screen turns off or sleeps, etc and I press the power button to unlock, I can't. All I see is a light colored black blank screen and then when I press the power button again I can finally see the lock screen widgets/lock screen.
So is this a software issue? Or am I the only one? Hardware issue? This is happening after the 4.2.1 update and not prior to it.
Cheers.
I can confirm point 3. only happening since the 4.2.1 update. Screen is black for a few seconds before the lock screen shows up
Sent from my Nexus 4 using Tapatalk 2
DazzaL said:
I can confirm point 3. only happening since the 4.2.1 update. Screen is black for a few seconds before the lock screen shows up
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Hmm. So it is not me then. Heh. Perhaps Google needs to fix this in their 4.2.2 update or whatever heh.
I'm having this issue as well. I'm even thinking about rooting my phone just to see if a custom rom will fix this.
Sent from my Nexus 4 using XDA Premium HD app
i noticed the black screen too i'm going back to 4.2 since i didn't have the December problem
My phone was updated to 4.2.1 earlier this morning and I don't have any of those issues.
Sent from my Nexus 4
Foxy Roxy said:
My phone was updated to 4.2.1 earlier this morning and I don't have any of those issues.
Sent from my Nexus 4
Click to expand...
Click to collapse
I had point 3 only but that's cleared itself now (I was rooted before updating and after hitting restore root in ota root keeper the problem went away). I've tried a few test calls but don't have issue 1 and 2
Sent from my Nexus 4 using Tapatalk 2
Updated 20 minutes ago and now I am repeatedly getting 3. Screen does not reliably come on when pressing the power button. Have not tried calls
Sent from my Nexus 4 using xda app-developers app
I'm curious to know how many of you with this issues are using those plastic screen protectors?
edited: After doing some tests i figured out that my screen protector is the cause. the screen protector is covering the sensor located on the top left side of the phone which causes android to deactivate the screen to save battery like it dose during calls when the phone is held against your ears.
DazzaL said:
I had point 3 only but that's cleared itself now (I was rooted before updating and after hitting restore root in ota root keeper the problem went away). I've tried a few test calls but don't have issue 1 and 2
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I had root before. Then I got the update, but used Voodoo OTA rootkeeper to preserve root before. After I updated, I still had root. Should I hit restore root still even though I have root enabled?
n4user said:
I'm curious to know how many of you with this issues are using those plastic screen protectors?
edited: After doing some tests i figured out that my screen protector is the cause. the screen protector is covering the sensor located on the top left side of the phone which causes android to deactivate the screen to save battery like it dose during calls when the phone is held against your ears.
Click to expand...
Click to collapse
You mean the one that came with the phone or aftermarket ones? If the one that came with the phone, I have not had the problem prior to 4.2.1. So I highly doubt that's the case here, or rather the issue heh.
DazzaL said:
I had point 3 only but that's cleared itself now (I was rooted before updating and after hitting restore root in ota root keeper the problem went away). I've tried a few test calls but don't have issue 1 and 2
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I can confirm that that issues seem to have gone away after rerooting the device.
Armon2 said:
I can confirm that that issues seem to have gone away after rerooting the device.
Click to expand...
Click to collapse
Hmm... So just uninstall SuperSU and reinstall SuperSU?
Edit: I tried using to restore root using Voodoo's OTA Rootkeeper and so far the problem as per #3 on my list (per main post) seems to have subsided.
evaradar said:
Hey folks,
After updating to 4.2.1 on my Nexus 4, I've been noticing lately the following issues:
1) If I am on a call and I want to do something else, I cannot do anything at all even when I press the power button so I can see the screen.
2) If someone calls me, sometimes the screen won't be on and I can't see who's calling and can't answer. Or it'll show up for a few seconds and boom, same thing. Same issue when ending a call.
3) If I am using my phone and after 15 seconds the screen turns off or sleeps, etc and I press the power button to unlock, I can't. All I see is a light colored black blank screen and then when I press the power button again I can finally see the lock screen widgets/lock screen.
So is this a software issue? Or am I the only one? Hardware issue? This is happening after the 4.2.1 update and not prior to it.
Cheers.
Click to expand...
Click to collapse
I got one for my Mom and right out of the box #1 and #2 were happening after initial setup. Doing a restore to factory seemed to fix it, we didn't do the update on either of our phones
I had the same problem, my nexus 4 was still on 4.2
I had installed an aftermarket screen protector. i removed it and the problem went away.
It does sound like that you have a screen protector that is covering your proximity sensor.
Sent from my Nexus 4 using xda premium
Yes. I can confirm the problem is with the screen protector. I had problem 1 and 2 before removing the screen protector.
+1 on the screen protector. I had the #1 and #2 issue. My screen would immediately black out during a call and not come back on unless the person on the other end hung up first (was terrible for leaving voicemail lol). I had an extreme guard protector on and it was effecting the proximity sensor. Glad I searched for this issue because it was starting to tick me off! I guess its time to go back to CM10 since that was not my issue lol.
-1 for screen protector here, unless there's a super-secret one I can't peel off
My proximity sensor is presumably bust, as Elixir 2 and Android Sensor Box both show it reporting "near" and 0.0cm respectively. Anyone else have these issues?
DJGibbon said:
-1 for screen protector here, unless there's a super-secret one I can't peel off
My proximity sensor is presumably bust, as Elixir 2 and Android Sensor Box both show it reporting "near" and 0.0cm respectively. Anyone else have these issues?
Click to expand...
Click to collapse
Same issue here even though I do have a skin on it. But I''ve had a skin on my last 5 android phones and its never triggered the sensor. I'm going to run that sensor box app after I'm off this call and see what it says.
---------- Post added at 08:26 PM ---------- Previous post was at 08:19 PM ----------
I'm emailing bestskinsever about this, mine is showing 0 as well and my other droid for work shows 100.
---------- Post added at 08:31 PM ---------- Previous post was at 08:26 PM ----------
Here is my email to bestskinsever
So I have orderd from you maybe a dozen or so times and love your products/pricing. But I have a concern with the skin for the nexus 4. Since I have put it on it is throwing mu prox sensor off and making it report a 0. My work phone with no skin is showing 100 in Android Sensor Box. So with the nexus every call I make the screen stays black. Maybe the nexus 4's sensor is more picky about skins? Here are some others have the same issue. Let me know what you come up with, because this may be an issue on all the nexus 4's.
PS There is not one spec of dust under my skin near the sensor. I applied the skin with the shower steaming up so no dust would fall on the screen.
http://forum.xda-developers.com/showthread.php?p=35019284#post35019284
http://forums.androidcentral.com/google-nexus-4/227416-another-nexus-4-issue.html
bton said:
Yes. I can confirm the problem is with the screen protector. I had problem 1 and 2 before removing the screen protector.
Click to expand...
Click to collapse
Same here. I cut off the part of the screen protector near the two "dots" on the top-left, and problem 1 and 2 are gone.
I'm having a bit of a weird issue with my new Verizon GS5.
Scenario: I am doing something such as reading a text, decide I'm done and lock the screen, and then a second or two later realize I forget to check something and hit the lock button again to turn it back on. Most of the time when I do this the physical buttons will light up but the screen will stay black, and a few seconds later the physical buttons will turn off. This will happen a few times until finally the screen turns on and I see the lock screen.
I had a similar issue with my Galaxy Nexus (rooted and running Kit Kat) phone prior to the GS5 and figured it was my old hardware- is this some Kit Kat bug?
Thanks for any input
Same issue here. But I can't figure out if it was due to switching to ART or not.
We can wait others reply with this i hope someone will post a tip on this kind of problem.
I switched to art after installing apps and I'm ha ing this issue didn't really play with phone much until after switching to ART. Is anyone having this issue not on ART?
Sent from my SM-G900V using Tapatalk
kameleongt said:
I switched to art after installing apps and I'm ha ing this issue didn't really play with phone much until after switching to ART. Is anyone having this issue not on ART?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Yes this is happening to me running Dalvik.
Happened just now to me. It has happened a few times.
Sent from my SM-G900V using Tapatalk
Had this a time or two. It's like the power button doesn't register or something. Yes I switched to art.
I have found though that if I hold power for a second it pretty much fixes itself without having to do anything crazy like yanking the battery or restarting the phone.
Imo: not a big deal, doesn't seem to happen a lot for me.
Sent from my SM-G900V using xda app-developers app
tehgyb said:
Had this a time or two. It's like the power button doesn't register or something. Yes I switched to art.
I have found though that if I hold power for a second it pretty much fixes itself without having to do anything crazy like yanking the battery or restarting the phone.
Imo: not a big deal, doesn't seem to happen a lot for me.
Sent from my SM-G900V using xda app-developers app
Click to expand...
Click to collapse
Is it kind of bugged?
Lodaserves said:
Is it kind of bugged?
Click to expand...
Click to collapse
This is actually becoming quite an annoyance to me and happens very often. I'm still on Dalvik. Could this be caused by an app?
I feel like half the time I go to use my phone the screen doesn't turn on.
tehgyb said:
Had this a time or two. It's like the power button doesn't register or something. Yes I switched to art.
I have found though that if I hold power for a second it pretty much fixes itself without having to do anything crazy like yanking the battery or restarting the phone.
Imo: not a big deal, doesn't seem to happen a lot for me.
Sent from my SM-G900V using xda app-developers app
Click to expand...
Click to collapse
I'm having the same issue for the past two days; although, I am not switching between apps or anything (only trying to use the phone). No display, but get sound/vibration from buttons and LED lights from soft keys. Unfortunately, both times required me to yank the battery. My S5 is completely stock (not using ART) and have manually reinstalled my apps from old device. Any suggestions?
I am not experiencing this and I have switched to ART...
Lodaserves said:
I think your phone have a problem and others don't have this kind of problem.
Click to expand...
Click to collapse
I hope this isn't the case. Once again I experienced these EXACT same issues with my Galaxy Nexus running 4.4.2. I can't help but think it might be some app causing it since not everyone has it.
I am noticing this every once in a while. But it's mostly right after I shut the screen off after a large processed app or task, and then remember something I forgot to do and try and turn it back on and there is some lag bringing up the screen again.
Black screen when quickly pushing lock
Lodaserves said:
Try to ask the person where you bought it.
Click to expand...
Click to collapse
I was about to return my S5 to Verizon for this very reason. I haven't switched to art and have been having the screen go black on me, you can tell the phone is on because the physical buttons are lit. It seems to happen to me alot when I take the phone off the charger and hit the on button. I will hear the phone rebooting, but not see the boot animation. Thats when I do a battery pull. Holding the button doesn't do it. I also have had a few random reboots. Thats ok...I'm going to try every root method under the sun..gggrrrr..lol
I've started to try to uninstall apps to see if I can narrow down the issue. It still plagues me at least half the time I try to use my phone.
This is happening to me as well. Not as often. I'd say once a day, but I have to pull my battery to restart it. I did 2 factory resets and am now using a new google account as per verizons request and I added apps slowly. I have been fine until I put a second launcher on. I installed the GEL launcher but did not use it just to see if having multiple launchers could cause this glitch. Could it be this? Is everyone else using a different launcher? Also the only time I ever had it happen while messing with the phone was two times while working in light flow. Any one else connected to those two happenings? Trying to narrow down what could be causing this.
Running ART here, I'm not sure if I'm getting this problem, but I have realized some latency from pressing either the home or power button and the screen turning on. Not sure what causes that lag, but it's a good almost full second whereas my S4 would be instant
eagle132 said:
I'm having a bit of a weird issue with my new Verizon GS5.
Scenario: I am doing something such as reading a text, decide I'm done and lock the screen, and then a second or two later realize I forget to check something and hit the lock button again to turn it back on. Most of the time when I do this the physical buttons will light up but the screen will stay black, and a few seconds later the physical buttons will turn off. This will happen a few times until finally the screen turns on and I see the lock screen.
I had a similar issue with my Galaxy Nexus (rooted and running Kit Kat) phone prior to the GS5 and figured it was my old hardware- is this some Kit Kat bug?
Thanks for any input
Click to expand...
Click to collapse
I would assume this is NOT the physical hardware issue, but the software, I heard somewhere that Samsung version of KitKat 4.4.2 is quite buggy and glitchy.
Njzkrish said:
Same issue here. But I can't figure out if it was due to switching to ART or not.
Click to expand...
Click to collapse
I had the issue before and after switching to ART
Anyone have any further ideas yet? I'm not running ART bit I was able to have it happen again when I had Google experience launcher installed. Removed it and it hasn't happened for two days. I'm installing Google launcher again now to see if that was causing the issue.
Anyone else with further developments?