Obsolete
Status Update
Comments
to...@fud.no <to...@fud.no> #2
The log messages are related to a technique used in Android 4.2 to reduce accidental presses on the main navigation keys while typing. This "dead zone" should not, however, be active when touching the navigation keys in general, only during a short window after you've interacted with the rest of the screen. And the dead zone does not extend all the way to the bottom of the screen; it's worth trying to touch the navigation keys all the way at the bottom of the visible screen area to see if that still works.
I wonder if you might be having a hardware issue; a defect with your touchscreen that is causing stray motion events elsewhere on the display, invoking this DeadZone feature to prevent touching the navigation buttons. This could potentially be confirmed by turning on Pointer Location (in the Developer settings) and looking for stray touches elsewhere on-screen.
I wonder if you might be having a hardware issue; a defect with your touchscreen that is causing stray motion events elsewhere on the display, invoking this DeadZone feature to prevent touching the navigation buttons. This could potentially be confirmed by turning on Pointer Location (in the Developer settings) and looking for stray touches elsewhere on-screen.
lo...@google.com <lo...@google.com> #3
I turned on Pointer Location and I am not seeing stray touches. To me it looks as if the touch indicator cuts off halfway through the bottom buttons as I drag my finger down. I see the touch indicator only on the top half of the button I am touching. It does seem like a hardware defect where only that small portion of the screen is not responding to touches.
to...@fud.no <to...@fud.no> #4
Hmm, yeah, that does sound like the touch panel is not responding on that edge of the screen.
I'd be interested to know if you can touch the screen in that area when there's something else there; that is, rotate the phone into upside-down landscape (so that the navigation buttons are up by the earpiece) and see if you can interact with the system (or generate Pointer Location traces) in that area. For that matter, I'd be curious if you can operate the navigation buttons when they're at the other end of the display, too.
I'd be interested to know if you can touch the screen in that area when there's something else there; that is, rotate the phone into upside-down landscape (so that the navigation buttons are up by the earpiece) and see if you can interact with the system (or generate Pointer Location traces) in that area. For that matter, I'd be curious if you can operate the navigation buttons when they're at the other end of the display, too.
to...@fud.no <to...@fud.no> #5
i have the same problem, is there any way to fix it?
to...@fud.no <to...@fud.no> #6
Sorry for the long response time. I ended up RMAing the device.
lo...@google.com <lo...@google.com> #7
Same problem here. The developer visualisation shows that the bottom 1 cm of the device (in portrait mode) is not accessible to the touch screen. In landscape mode, the soft buttons are out of this dead area and still work.
Google telephone support had no problem sending a replacement device.
Also, I didn't measure this before factory resetting the device, but I think the dead area has gotten bigger. Originally ~0.5cm, cutting through the soft buttons, but is now noticeably above them.
Most likely the root cause is hardware.
Google telephone support had no problem sending a replacement device.
Also, I didn't measure this before factory resetting the device, but I think the dead area has gotten bigger. Originally ~0.5cm, cutting through the soft buttons, but is now noticeably above them.
Most likely the root cause is hardware.
lo...@google.com <lo...@google.com> #8
Hi, here with the same problem, but I don't think is a hardware problem, because when I rotate the phone and tried to use this area of the screen, the touch work perfectly fine, for example, scrolling a webpage.
to...@fud.no <to...@fud.no> #9
[Comment deleted]
lo...@google.com <lo...@google.com> #10
Dead area on screen where soft buttons are in portrait mode. When phone is rotated the dead area is the same group of pixels ie when rotated clockwise the dead area is the left edge in landscape. Debugging the touches shows no touch is recorded at all. The touch trace cuts out. Started suddenly after 5 months. Full reset with no restore of preferences did not fix.
tu...@student.jyu.fi <tu...@student.jyu.fi> #11
so is there a solution to it ? anyone found a solution ?
uw...@gmail.com <uw...@gmail.com> #12
Returned device under warranty. Accepted by Google.
da...@gmail.com <da...@gmail.com> #13
Was there a solution to this issue? or I need get a replacement?
My keys stopped working all of sudden. But it doesn't look like a hardware issue since in chrome I can still scroll in that area once I put the phone in landscape mode.
BTW. I work for Qualcomm and I did some work on this phone. So if anyone at Google would like to get the device for debugging than I would be happy to help. I'm also located in Silicon Valley.
My keys stopped working all of sudden. But it doesn't look like a hardware issue since in chrome I can still scroll in that area once I put the phone in landscape mode.
BTW. I work for Qualcomm and I did some work on this phone. So if anyone at Google would like to get the device for debugging than I would be happy to help. I'm also located in Silicon Valley.
da...@gmail.com <da...@gmail.com> #14
Well my soft buttons stopped working too, but I'm in Lebanon, they're not working at all, under any condition. What should I do?
uw...@gmail.com <uw...@gmail.com> #15
Same Problem here!
uw...@gmail.com <uw...@gmail.com> #16
Factory reset/wipe as well as flashing the phone with a factory image did not lead to solving the problem .. contacted customer support and am getting a replacement ..
uw...@gmail.com <uw...@gmail.com> #17
Well any way to solve that? It happens to me today. I'm able to operate my phone because in have cm ROM and pie controls
uw...@gmail.com <uw...@gmail.com> #18
Same problem here. A technician told me that the problem is the touchscreen, but it doesn't sound right because the edge of the sreen works when the touchkeys are rotated.
da...@gmail.com <da...@gmail.com> #19
Guys, IT'S JUST BROKEN - YOU WILL NEED TO RETURN IT.
uw...@gmail.com <uw...@gmail.com> #20
@pedro do the soft keys work on CM Rom? If they don't work on CM rom than surely this is a hardware issue.
I have had time to factory reset the device and ask for replacement. Need to take full back so will likely do this over this weekend. If it doesn't help than I'll ask for replacement.
I have had time to factory reset the device and ask for replacement. Need to take full back so will likely do this over this weekend. If it doesn't help than I'll ask for replacement.
cs...@gmail.com <cs...@gmail.com> #21
Sometimes it works, a sometimes not. Sometime the screen freezes and I have to turn off the screen. I brought my nexus from amazon you think that seller accept the return?? This weekend I will try like @hardik says and if that doesn't work in will try to return it
da...@gmail.com <da...@gmail.com> #22
I am facing the same issue(softkeys not working).. Ul said it needs to be replaced, but the problem is dat I had bought the phone from US, but now im in India.. Can i replace it from here?
po...@gmail.com <po...@gmail.com> #23
why don't you ask google, who can give you the correct answer, rather than people like us?
uw...@gmail.com <uw...@gmail.com> #24
@22 and..calvin.it Try going to http://support.google.com/nexus/ as they are the best people to help you.
lo...@google.com <lo...@google.com> #25
I went to this site but cud not find a place where i can post my query.. http://support.google.com/nexus/ .. Can ne1 tell me how to file for replacement or where to file it? I hav tried emailing, but they just revert via automated mails wich redirect to useless sites.. How did ul replace the phone?
po...@gmail.com <po...@gmail.com> #26
Im experiencing the same issue. Had my phone for about 3 weeks.
The softkeys are unresponsive, however if i open a webpage and flip the phone so they ocupy the other side of the screen then they work fine.
The issue seems to be intermittent. Ive just recharged my phone and the issue has gone again.
There doesnt seem to be any conclusions on whats causing the issue in this forum or suggestions of a solution to it yet. Anyone got any ideas or is it really only solvable with returning the phone for a replacement?
Thanks.
Dave
The softkeys are unresponsive, however if i open a webpage and flip the phone so they ocupy the other side of the screen then they work fine.
The issue seems to be intermittent. Ive just recharged my phone and the issue has gone again.
There doesnt seem to be any conclusions on whats causing the issue in this forum or suggestions of a solution to it yet. Anyone got any ideas or is it really only solvable with returning the phone for a replacement?
Thanks.
Dave
th...@gmail.com <th...@gmail.com> #27
Update: its not intermittent any more :o(
Worth noting that if anyone is really stuck and cant change the phone on warranty then there are some apps available to offer a work around the issue. try searching for taskbar or softkeys.
Ive added 'taskbar switcher' which gets me back to the home page via the notifications bar, but my phone is new so its going back for a replacement.
Dave
Worth noting that if anyone is really stuck and cant change the phone on warranty then there are some apps available to offer a work around the issue. try searching for taskbar or softkeys.
Ive added 'taskbar switcher' which gets me back to the home page via the notifications bar, but my phone is new so its going back for a replacement.
Dave
lo...@google.com <lo...@google.com> #28
Interesting that while those keys don't work in Portrait, the area of the screen on which the Softkeys located is scrollable in landscape. Clockwise rotation to horizontal is the only way to have the soft keys work though.. Would suggest it's a software issue?
uw...@gmail.com <uw...@gmail.com> #29
My Nexus 4 phone has the same issue. I bought this phone from US, 4 months before. But now i am in India so how will i get fix my phone?, please help me.
ch...@gmail.com <ch...@gmail.com> #30
I have bought a Nexus 4 from US 4 months ago and i am in India.
My Nexus 4 was working good and suddenly since 4 days Softkeys (Back, Home, etc.)are not responding even i have tried rebooting and restoring factory setting. I need a solution for this issue.
My Nexus 4 was working good and suddenly since 4 days Softkeys (Back, Home, etc.)are not responding even i have tried rebooting and restoring factory setting. I need a solution for this issue.
ja...@gmail.com <ja...@gmail.com> #31
I have been having problems with my Nexus 4 as well. I bought it in India on 22nd June and it started giving me problems from 18th July...not even a month of peace!
First I started facing some phantom touches in the softkeys. I cleaned it once and it reduced the frequency of phantom touches. After some time it stopped on itself.
After phantom touches stopped the softkeys were back to normal but just for some time.
Later the soft keys became unresponsive in portrait mode. If I tilted to landscape mode towards right which shifted the softkeys towards the top of the phone(Where camera is), the softkeys worked in new location AND the the bottom of the screen where softkeys are placed in portrait mode was ALSO responsive to touch.
Then again after some time, that part of screen (where softkeys are in portrait mode) became completely unresponsive to touch. I enabled show touch and could observe that the lines break as soon as it enters the bottom of the screen where softkeys are in both portrait mode and landscape mode.
So I thought I should get a replacement as it is under warranty.
Thought of going to the LG service center(LG retails Nexus 4 in India) it next day.
Next morning however, the softkeys were working!!! BUT, again for sometime, then I again saw phantom touches, followed by unresponsive softkeys followed by normal functioning. The problem is that if I take it to service center and the keys are working normally they might not give me a replacement straightaway. So I am planning to take a video of it when phantom touches or unresponsive softkeys happen next time.
On the actual problem itself, I am still not sure that it is a hardware or software problem. Could be that the digitizer is acting weird. But then, how will it resolve itself after going completely dead in that area?
It could be a firmware issue as well and looks more likely to me. I dont want to root and try custom firmware or custom ROMs as long as the phone is in warranty. But I have a feeling that this problem is going to come in the replacement phone as well as some point of time. :(
Really disappointed with Google/LG. These kind of issues should not occur in a flagship phone and next time I am planning to go back to Samsung for a phone that is thoroughly QCd or may even try my hand at the next iPhone!
First I started facing some phantom touches in the softkeys. I cleaned it once and it reduced the frequency of phantom touches. After some time it stopped on itself.
After phantom touches stopped the softkeys were back to normal but just for some time.
Later the soft keys became unresponsive in portrait mode. If I tilted to landscape mode towards right which shifted the softkeys towards the top of the phone(Where camera is), the softkeys worked in new location AND the the bottom of the screen where softkeys are placed in portrait mode was ALSO responsive to touch.
Then again after some time, that part of screen (where softkeys are in portrait mode) became completely unresponsive to touch. I enabled show touch and could observe that the lines break as soon as it enters the bottom of the screen where softkeys are in both portrait mode and landscape mode.
So I thought I should get a replacement as it is under warranty.
Thought of going to the LG service center(LG retails Nexus 4 in India) it next day.
Next morning however, the softkeys were working!!! BUT, again for sometime, then I again saw phantom touches, followed by unresponsive softkeys followed by normal functioning. The problem is that if I take it to service center and the keys are working normally they might not give me a replacement straightaway. So I am planning to take a video of it when phantom touches or unresponsive softkeys happen next time.
On the actual problem itself, I am still not sure that it is a hardware or software problem. Could be that the digitizer is acting weird. But then, how will it resolve itself after going completely dead in that area?
It could be a firmware issue as well and looks more likely to me. I dont want to root and try custom firmware or custom ROMs as long as the phone is in warranty. But I have a feeling that this problem is going to come in the replacement phone as well as some point of time. :(
Really disappointed with Google/LG. These kind of issues should not occur in a flagship phone and next time I am planning to go back to Samsung for a phone that is thoroughly QCd or may even try my hand at the next iPhone!
mi...@gmail.com <mi...@gmail.com> #32
To add to my comment above: I have tried hard resetting it once last night, and it did not resolve the problem at least last night. But it was working this morning as I mentioned earlier again to start giving me trouble before coming back to normal.
ja...@gmail.com <ja...@gmail.com> #33
Took it to the LG service center and they replaced the digitizer and seems to work so far. It is still in warranty (only one month old phone!) so didnt cost me anything.
But I am worried now, I am going to Australia for a few months in a few weeks, and if this problem comes again while I am there then I will have to shell out nearly AUD150 to get it fixed because the warranty wont be applicable there.
But I am worried now, I am going to Australia for a few months in a few weeks, and if this problem comes again while I am there then I will have to shell out nearly AUD150 to get it fixed because the warranty wont be applicable there.
ja...@gmail.com <ja...@gmail.com> #34
So, the same problem with my Nexus 4. I tried with pointer location (developer optioon) and it shown that the bottom of screen (softkey's position in portrait mode) was not responsive with touch. The same in landscape mode (plz see attach file).
I bought my phone non-officially in a store at my country - Vietnam (the phone made in Korea) so I think i cannt send it back to receive a replacement. The only thing I want to do is fix it (I'm sure that's hardware trouble), so anyone can help me, Please !!!
I bought my phone non-officially in a store at my country - Vietnam (the phone made in Korea) so I think i cannt send it back to receive a replacement. The only thing I want to do is fix it (I'm sure that's hardware trouble), so anyone can help me, Please !!!
de...@gmail.com <de...@gmail.com> #35
To the person above: You will need to get the Display+Digitizer assembly replace at any local LG/Google store. When you say you have bought it un-officially what does it mean? If you have a proper bill of the sale from a store within Vietnam you may still be covered by warranty. I would recommend going to the service center with whatever bill you have to check for warranty. If it is covered then you dont have to pay anything.
However, if that is not the case, and your phone is not covered by warranty, then you will need to pay for the part cost + labour for replacing the Display+Digitizer assembly which will cost somewhere between USD 100-150.
Good luck!
However, if that is not the case, and your phone is not covered by warranty, then you will need to pay for the part cost + labour for replacing the Display+Digitizer assembly which will cost somewhere between USD 100-150.
Good luck!
lo...@google.com <lo...@google.com> #36
I agree to most parts with an addition.
Recently many a times the back button in chrome doesn't work. After we minimize the apps and then start again it works.
BTW back arrow button from menu always works.
Addition the keyboard doesn't pop up sometime in the text boxes (even in chrome).
Galaxy nexus GWR66Y
Recently many a times the back button in chrome doesn't work. After we minimize the apps and then start again it works.
BTW back arrow button from menu always works.
Addition the keyboard doesn't pop up sometime in the text boxes (even in chrome).
Galaxy nexus GWR66Y
ge...@gmail.com <ge...@gmail.com> #37
exactly same issue. It appears when I have upgraded to android 4.3
en...@google.com <en...@google.com>
ad...@gmail.com <ad...@gmail.com> #38
After reverting back to Android 4.2.2 (JDQ39) factory image, I am still plagued by the same issue. Also it may be worth noting that I had the same issue while in recovery mode using twrp recovery. I still can not use the soft buttons. Using developer options on 4.2.2 show that the touch sensor stops working within the edges of the soft button bounds, but fails to detect touch on the button itself. Attached are screenshots and a catlog of "V/DeadZone" results when trying to hit the soft buttons.
br...@gmail.com <br...@gmail.com> #39
I believe this issue to be a hardware malfunction of the digitizer because re-imaging all device partitions did not solve anything, so I performed the steps outlined below:
According to LG Live Chat consultant that messaged me, all LGE960 devices purchased in the United States are under a 1 year warranty provided by google, and that I must contact google 1-855-83-NEXUS (63987).
After calling, the google consultant stated that, since I admitted to have dropped my phone once I am outside of the bounds of the 1 year warranty provided by google. Even though this damage is not in any way hindering the screen's performance because it is on the back near the speaker. So I called LG where upon I have shipped it back to the address given to me with the RMA # provided. The device may fall within the manufacturer's 1 year warranty, and this must be determined by LG technicians so I await their verdict.
Hope this information helps anyone who looks for it.
According to LG Live Chat consultant that messaged me, all LGE960 devices purchased in the United States are under a 1 year warranty provided by google, and that I must contact google 1-855-83-NEXUS (63987).
After calling, the google consultant stated that, since I admitted to have dropped my phone once I am outside of the bounds of the 1 year warranty provided by google. Even though this damage is not in any way hindering the screen's performance because it is on the back near the speaker. So I called LG where upon I have shipped it back to the address given to me with the RMA # provided. The device may fall within the manufacturer's 1 year warranty, and this must be determined by LG technicians so I await their verdict.
Hope this information helps anyone who looks for it.
lo...@gmail.com <lo...@gmail.com> #40
I have the same problem with my Nexus 4.
I installed Button Savior and added the buttons on the right side of the screen until a solution will be found.
I installed Button Savior and added the buttons on the right side of the screen until a solution will be found.
ab...@gmail.com <ab...@gmail.com> #41
I too face this issue for the past few weeks. I am using this phone since June 2013 and this problem cropped up after a few weeks of upgrading to Android 4.3. Will rolling back to an earlier version solve this? (I read elsewhere that it works). Or is it worth waiting for 4.4 upgrade?
da...@gmail.com <da...@gmail.com> #42
I sent my phone back to lg since Google told me it was out of warranty.
They gave me a new phone.
If you look at my previous post... Revert back to 4.2 solved nothing.
They gave me a new phone.
If you look at my previous post... Revert back to 4.2 solved nothing.
br...@gmail.com <br...@gmail.com> #43
@paresh, the problem with my phone is that I got it as a gift from a relative in the US. I am in India. So not sure about how to go for a replacement.
id...@gmail.com <id...@gmail.com> #44
Any hope to have this fixed updating to KitKat?
kw...@gmail.com <kw...@gmail.com> #45
AFAIK, this is a hardware issue and cannot be fixed with a software update.
I successfully replaced my phone (in the US) through warranty.
I successfully replaced my phone (in the US) through warranty.
rc...@gmail.com <rc...@gmail.com> #46
I'm now on kitkat ... Same issue
Description
It appears that Android starts ignoring these shortly after connecting to the network. This causes it to loose IPv6 connectivity after some time, the exact time depends on how long the lifetimes in the RA are set to.
I'm reproducing this easily using a Samsung Galaxy Nexus running stock Android 4.0.2. The router on the wireless network is a Linux host running Quagga, with the following configuration:
interface wireless
ipv6 nd prefix 2001:db8::/64 60 40
ipv6 nd ra-interval 10
ipv6 nd ra-lifetime 30
ipv6 nd router-preference high
no ipv6 nd suppress-ra
This causes it to transmit RAs every 10 second, with a default router lifetime of 30 seconds, and the IPv6 address valid/preferred lifetimes are 120/90 seconds.
After connecting the phone to the network, I can monitor the timers counting in "adb shell" with the following command:
$ while sleep 1; do ip -6 address list dev wlan0; ip -6 route list dev wlan0; done
Immediaetly after connecting to the network, the default route are listed with expires 29-30 seconds, and the inet6 addresses are listed with a valid_lft of 59-60 seconds, and a preferred_lft of 39-40 seconds, all as expected. I have not yet seen the device failing to act on the intitial (solicited) RA recived immediately after connecting.
However, as time goes by, the lifetimes are eventually dropping to zero. First the default route expires (at this point internet connectivity is lost), then the preferred_lft timer expires (and the addresses gets marked "deprecated"), and finally the valid_lft timer expires, and the addresses are removed completely.
It does not ignore *all* unsolicited RAs, so occasionally it will successfully reset the timers, re-add the default route if it had expired already, and un-deprecate/re-add the addresses if the preferred_lft/valid_lft had expired.
Since the unsolicited RAs are transmitted every 10 seconds, the timers should never drop to less then 10 seconds below the starting point (assuming no packet loss in the air).
I have reproduced the problem on two different wireless networks using two different router implementations, so I find it unlikely that this is a network issue. Also, while reproducing it I can ping the link-local address of the device without any packet loss, so it is also unlikely that signal quality is the problem.
One thing I've found interesting is that if I also ping the all-nodes multicast address (ff02::1) or the phone's solicited-node multicast address (ff02::1:<last 24 bits of the link-local address>) from the router, the phone replies only *very* sporadically. This leads me to believe that the issue is not specific to ICMPv6 Router Advertisements, but all (IPv6) multicast traffic.