Skip to main content
Question Protected by CommunityBot
added 214 characters in body
Source Link
Joshua Fox
  • 151
  • 1
  • 1
  • 6

On my Nexus 4 (Lollpop), the nav keys no longer respond when it is in portrait mode, and the q key no longer responds when it is in landscape mode. Here is the bug report. This has been discussed at the Google Group, and Grigoriy Kraynov has brilliantly put together an unofficial fix, but it requires rooting the Android. (Correction: Maybe not rooting it, but definitely some dangerous digging around in the OS's innards.)

There are also occasionally ghost presses. (I configured my phone to show a white dot when there is a press, and sometimes there are a lot of them all together, usually in this malfunctioning area, without my pressing the screen.)

It's been called a hardware bug in the digitizer, but pretty clearly isit looks to me like it's in the software layer -- since Kraynov's fix works, and since that part of the screen has no other problems.why would one particular rectangle stop working?

Can anyone suggest a simpler way to fix this? It's hard to believe that Google would allow such a significant software bug to go unfixed.

My workaround is to install the Button Savior Non Root app and an autorotator app (to enable 4-way rotate in every app). This workaround is more or less OK.

On my Nexus 4 (Lollpop), the nav keys no longer respond when it is in portrait mode, and the q key no longer responds when it is in landscape mode. Here is the bug report. This has been discussed at the Google Group, and Grigoriy Kraynov has brilliantly put together an unofficial fix, but it requires rooting the Android. (Correction: Maybe not rooting it, but definitely some dangerous digging around in the OS's innards.)

It's been called a hardware bug, but pretty clearly is in the software layer -- since Kraynov's fix works, and since that part of the screen has no other problems.

Can anyone suggest a simpler way to fix this? It's hard to believe that Google would allow such a significant software bug to go unfixed.

On my Nexus 4 (Lollpop), the nav keys no longer respond when it is in portrait mode, and the q key no longer responds when it is in landscape mode. Here is the bug report. This has been discussed at the Google Group, and Grigoriy Kraynov has brilliantly put together an unofficial fix, but it requires rooting the Android. (Correction: Maybe not rooting it, but definitely some dangerous digging around in the OS's innards.)

There are also occasionally ghost presses. (I configured my phone to show a white dot when there is a press, and sometimes there are a lot of them all together, usually in this malfunctioning area, without my pressing the screen.)

It's been called a hardware bug in the digitizer, but it looks to me like it's in the software layer -- why would one particular rectangle stop working?

Can anyone suggest a simpler way to fix this? It's hard to believe that Google would allow such a significant bug to go unfixed.

My workaround is to install the Button Savior Non Root app and an autorotator app (to enable 4-way rotate in every app). This workaround is more or less OK.

edited body
Source Link
Joshua Fox
  • 151
  • 1
  • 1
  • 6

On my Nexus 4 (Lollpop), the nav keys no longer respond when it is in portrait mode, and the q key no longer responds when it is in landscape mode. Here is the bug report. This has been discussed at the Google Group, and aGrigoriy Kraynov has brilliantly put together an unofficial fix has been put together by Grigoriy Kraynov--, but it requires rooting the Android. (Correction: Maybe not rooting it, but definitely some dangerous digging around in the OS's innards.)

It's been called a hardware bug, but pretty clearly is in the hardwaresoftware layer -- since Kraynov's fix works, and since that part of the screen has no other problems.

Can anyone suggest a simpler way to fix this? It's hard to believe that Google would allow such a significant software bug to go unfixed.

On my Nexus 4 (Lollpop), the nav keys no longer respond when it is in portrait mode, and the q key no longer responds when it is in landscape mode. Here is the bug report. This has been discussed at the Google Group, and a fix has been put together by Grigoriy Kraynov-- but it requires rooting the Android.

It's been called a hardware bug, but pretty clearly is in the hardware layer -- since Kraynov's fix works, and since that part of the screen has no other problems.

Can anyone suggest a simpler way to fix this? It's hard to believe that Google would allow such a significant software bug to go unfixed.

On my Nexus 4 (Lollpop), the nav keys no longer respond when it is in portrait mode, and the q key no longer responds when it is in landscape mode. Here is the bug report. This has been discussed at the Google Group, and Grigoriy Kraynov has brilliantly put together an unofficial fix, but it requires rooting the Android. (Correction: Maybe not rooting it, but definitely some dangerous digging around in the OS's innards.)

It's been called a hardware bug, but pretty clearly is in the software layer -- since Kraynov's fix works, and since that part of the screen has no other problems.

Can anyone suggest a simpler way to fix this? It's hard to believe that Google would allow such a significant software bug to go unfixed.

added 176 characters in body
Source Link
Joshua Fox
  • 151
  • 1
  • 1
  • 6

On my Nexus 4 (Lollpop), the nav keys no longer respond when it is in portrait mode, and the q key no longer responds when it is in landscape mode. Here is the bug report. This has been discussed at the Google Group, and a fix has been put together by Grigoriy Kraynov-- but it requires rooting the Android.

It's been called a hardware bug, but pretty clearly is in the hardware layer -- since Kraynov's fix works, and since that part of the screen has no other problems.

Can anyone suggest a simpler way to fix this? It's hard to believe that Google would allow such a significant software bug to go unfixed.

On my Nexus 4 (Lollpop), the nav keys no longer respond when it is in portrait mode, and the q key no longer responds when it is in landscape mode. Here is the bug report. This has been discussed at the Google Group, and a fix has been put together by Grigoriy Kraynov-- but it requires rooting the Android.

Can anyone suggest a simpler way to fix this? It's hard to believe that Google would allow such a significant bug to go unfixed.

On my Nexus 4 (Lollpop), the nav keys no longer respond when it is in portrait mode, and the q key no longer responds when it is in landscape mode. Here is the bug report. This has been discussed at the Google Group, and a fix has been put together by Grigoriy Kraynov-- but it requires rooting the Android.

It's been called a hardware bug, but pretty clearly is in the hardware layer -- since Kraynov's fix works, and since that part of the screen has no other problems.

Can anyone suggest a simpler way to fix this? It's hard to believe that Google would allow such a significant software bug to go unfixed.

Source Link
Joshua Fox
  • 151
  • 1
  • 1
  • 6
Loading