Navigation buttons with an inactive touch pad at the bottom of the screen

[ze7zez]

Navigation buttons work very well in ROMs, for Nexus 4 with an inactive touch pad at the bottom of the screen:

AICP - mirror
AOKP
AOSiP
AOSP
AOSPExtended
Chroma
Carbon - Use this trick.
Colt
Cosmic
crDroid
Dirty Unicorns
Krexus
MoKee
NeXus4ever
Nitrogen
OwnROM
Pixel Dust
Pure Nexus
Resurrection Remix
Tesla
Validus
Zephyr


Partial solution for ROMs.
@mkrmec pointed out this solution and should simply use it.
[WIP][FIX]Dead navbar workarounds and fixes

1. Enable android debugging in ROM.
2. Connect N4 to PC and check "always allow from this computer" on N4 screen and OK
3. On PC, run commands:

adb shell
wm overscan 0,0,0,90

From now on, the navigation buttons also work after restart. :victory:


Navigation buttons work very well in TWRP, for Nexus 4 with an inactive touch pad at the bottom of the screen:

TWRP 3.2.1.0 by sudokamikaze
TWRP 3.0.2.0 by vocoderism
TWRP multirom 3.0.2.0 by KreAch3R
TWRP multirom 3.0.0.0 by Tassadar

Developers and Contributors @BadGuy, @czepeq, @dragos281993, @Mr.MEX, @nitin.chobhe, @spezi77, @zaclimon, @xyyx!

(Sorry if I omitted someone who would like and could help in the case.)

We are before the next release of TWRP.

How You are applying fix or a way that allows the use of non-responsive buttons in the navigation bar in the ROM listed below, you are working on?
Can you use this property from your ROM to in a similar way could activate the navbar in TWRP?

If so, please notify the @dess_troy and TeamWin crew.

The problem of handling navigation bar does not apply to all copies of the Nexus 4.
Until recently, no ROM on the Nexus 4 did not give the possibility to use the navigation buttons on the equipment, which was susceptible to the problem.
From October 2016 arrives However, there are ROMs, in which it is possible to use the navigation buttons.

Examples of links to information describing the problem:

nexus-4-navfix
Dead navbar workarounds and fixes
How to fix Nexus 4 unresponsive soft navigation menu buttons
Google search

 

[spezi77]

First

I am not so familiar with the TWRP source code, and whether there is any common point in fixing it. However, here is the fix for frameworks_base which works around the "deadzone": https://github.com/nexus4ever/andro...mmit/a70409b5dbc663205adf8da5215765ee04accab4

I am looking forward to see what the other devs think, before notifying dees-troy and his crew..

Cheers!

 

[zaclimon]

As Spezi pointed out, the commit is included in the framework part of the rom. Now there is two things to consider from TWRP:

1. The code is in C++ which differs from java so a backport might be needed.
2. Since I don't know the source code as well of TWRP, we might need to check how the touchscreen events are handled and perhaps add a condition for the Nexus 4.

From what I see, TWRP has the same problem as the roms without the patch correct?

Sent from my Pixel using XDA Labs

 

[ze7zez]

From what I see, TWRP has the same problem as the roms without the patch correct?

That's right. In TWRP buttons they are not responsive.

 

[ze7zez]

@Tasssadar or @KreAch3R, could you comment?
(Tasssadar was active very long time ago)
Do you know well the code and/or principles of operation to assess the chances of realization in some way navigation bar fix in TWRP?

 

[KreAch3R]

Hello,

Well I don't know how I was drawn into this conversation, but thank you for thinking that mentioning me will help.

Unfortunately, besides the fact that I know about this weird bug since at least marshmallow (you can add Krexus at the list of supported ROMs), as @zaclimon said, the patch is on Java so I don't think picking it on TWRP will be applicable.

Chances are (and that's only my humble guess) that this will need to be re-written completely for whatever driver TWRP uses to control touch input, and given the age of the device and its declining health (even though we all love mako ), I don't think anyone capable enough will spend the time to do it (except the TWRP team of course).

I would suggest that a custom theme with the navigation bar pivoted above the buggy area would be the best and easier compromise.

 

[ze7zez]

Success, but why?

I would suggest that a custom theme with the navigation bar pivoted above the buggy area would be the best and easier compromise.

I checked your TWRP 3.0.2.0 on AFH.
In my buttons navigation function properly if I touch more than 2/3 of the height of the navigation bar.
Even better works in TWRP_multirom_mako_20160714_UNOFFICIALr2.img than in TWRP_multirom_mako_20160714_UNOFFICIAL.img.
@vocoderism, your Unofficial TWRP Mako 3.0.2.0 EXT4/F2FS/NTFS also works correctly. It's great!

Friends, tell me how you did it?

 

[ze7zez]

Source Code: https://github.com/TeamWin

android_device_lge_mako is very old. If there were this fix, the official version of TWRP would long ago have worked well.

I do not know of a place where they come from your source patches, so I do not have to send information to @Dees_Troy.
@KreAch3R and @vocoderism!
Do you you report to TeamWin crew, the solution can be used in the next official version?

 

[KreAch3R]

@KreAch3R and @vocoderism!
Do you you report to TeamWin crew, the solution can be used in the next official version?

No I don't, I have worked with twrp multirom independently.

If you already have found working TWRP recoveries, why are we still looking for it?

 

[ze7zez]

No I don't, I have worked with twrp multirom independently.

If you already have found working TWRP recoveries, why are we still looking for it?

Creation DeadZone may arise in each Nexus 4.
DeadZone Fix eliminates the problem.

I do not know why some developers and contributors do not apply it in the ROMs.
I understand that fixes are not there to repair the equipment.
But if it is a simple fix, why it could not be used in all devices?

I think the fix could be included in the basic source TWRP.

Can you give the source of the above mentioned versions of your TWRP that you prepared?

 

[KreAch3R]

Creation DeadZone may arise in each Nexus 4.
DeadZone Fix eliminates the problem.

I do not know why some developers and contributors do not apply it in the ROMs.
I understand that fixes are not there to repair the equipment.
But if it is a simple fix, why it could not be used in all devices?

I think the fix could be included in the basic source TWRP.

Can you give the source of the above mentioned versions of your TWRP that you prepared?

If I remember correctly, I never actually got to finish my mako work. I didn't remember if it even booted. But for both builds (mako and hammerhead), the source is here anyway: https://github.com/kremultirom

 

[ze7zez]

new TWRP

@sudokamikaze created the topic Unofficial TWRP Mako 3.1.1-0 EXT4 / F2FS and here we have the latest version of TWRP in which navigation buttons work.

Thanks so much @sudokamikaze!

 

[ze7zez]

I added to the first post a solution for ROMs.

 

[mkrmec]

Developers and Contributors @BadGuy, @czepeq, @dragos281993, @Mr.MEX, @nitin.chobhe, @spezi77, @zaclimon, @xyyx!

(Sorry if I omitted someone who would like and could help in the case.)

We are before the next release of TWRP.

How You are applying fix or a way that allows the use of non-responsive buttons in the navigation bar in the ROM listed below, you are working on?
Can you use this property from your ROM to in a similar way could activate the navbar in TWRP?

If so, please notify the @dess_troy and TeamWin crew.

The problem of handling navigation bar does not apply to all copies of the Nexus 4.
Until recently, no ROM on the Nexus 4 did not give the possibility to use the navigation buttons on the equipment, which was susceptible to the problem.
From October 2016 arrives However, there are ROMs, in which it is possible to use the navigation buttons.

I checked and I can confirm that the navigation buttons work very well in the ROM for Nexus 4:

AICP
AOKP
AOSP
AOSPExtended
Chroma
Carbon - Use this trick.
Cosmic
crDroid
Dirty Unicorns
Krexus
MoKee
NeXus4ever
Nitrogen
Pixel Dust
Pure Nexus
Resurrection Remix
Tesla
Validus
Zephyr


Solution for ROMs.
@mkrmec pointed out this solution and should simply use it.
[WIP][FIX]Dead navbar workarounds and fixes

1. Enable android debugging in ROM.
2. Connect N4 to PC and check "always allow from this computer" on N4 screen and OK
3. On PC, run commands:

adb shell
wm overscan 0,0,0,90

From now on, the navigation buttons also work after restart. :victory:




Examples of links to information describing the problem:

nexus-4-navfix
Dead navbar workarounds and fixes
How to fix Nexus 4 unresponsive soft navigation menu buttons
Google search

I connected to the phone from another phone vid app adb shell and entered wm overscan 0,0,0,15 that was enough for the phone navbar start working and that all that screen space was wasted.

 

[ze7zez]

I connected to the phone from another phone vid app adb shell and entered wm overscan 0,0,0,15 that was enough for the phone navbar start working and that all that screen space was wasted.

Reducing the screen is not painful.
It is painful to buy and replace a digitizer.

It is possible to use the Button Savior or PIE application and disable the navigation buttons if there is a setting in the ROM.

This topic, however, concerns the operation of navigation buttons in the recovery mode.
I hope that @sudokamikaze will deal with bugs and we will be able to use fully functional TWRP and navigation buttons.

 

[sudokamikaze]

Reducing the screen is not painful.
It is painful to buy and replace a digitizer.

It is possible to use the Button Savior or PIE application and disable the navigation buttons if there is a setting in the ROM.

This topic, however, concerns the operation of navigation buttons in the recovery mode.
I hope that @sudokamikaze will deal with bugs and we will be able to use fully functional TWRP and navigation buttons.

I tried many times of recompiling, but still don't find solution


BTW, bugs are fixed

 

[paolocorpo]

Partial solution for ROMs.
@mkrmec pointed out this solution and should simply use it.
[WIP][FIX]Dead navbar workarounds and fixes

1. Enable android debugging in ROM.
2. Connect N4 to PC and check "always allow from this computer" on N4 screen and OK
3. On PC, run commands:

adb shell
wm overscan 0,0,0,90

From now on, the navigation buttons also work after restart. :victory:

This workaround worked well for my N4
Thanks a lot
Paolo

 

[d_g_m_2000]

hello, i'm gonna give a try.. before send it to change a display... thanks in advance for this tutorial