[GUIDE][5.0]How to enable on-screen nav bar and disable hardware capacitive buttons.

Search This thread

deepesh.tickoo

Senior Member
Mar 15, 2011
733
388
New Delhi
INTRODUCTION
This guide is for Ivan's 5.0 Lollipop AOSP ROM but will work with other ROMs as well.

FEATURES
  • Pure AOSP feel.
  • Many people prefer it, including me.
  • Workaround for 'hardware key wakeup' bug.
  • Can use Lollipop features like Screen Pinning easily.
  • Looks cool:D

PREREQUISITES
  • Ivan's Lollipop AOSP ROM.(May work on others too)
  • MI3.(Again may work on others too:p)
  • Root.
  • ES File Explorer.(or any file manager with root access)

INSTRUCTIONS
  • Enabling on-screen nav bar.
    1. Open ES File Explorer and grant su access.
    2. Go to system and open build.prop with ES Note Editor and add this line in the end:
      Code:
      qemu.hw.mainkeys=0
    3. Save build.prop and reboot.
    4. Check if soft keys are enabled.
    5. If enabled successfully, proceed to next section.
  • Disabling hardware capacitive keys.
    1. Go to system/usr/keylayout and open 'atmel-maxtouch.kl' with ES Note Editor.
    2. In the end of that file there will be following three lines:
      Code:
      key 139    MENU    VIRTUAL
      key 102    HOME    VIRTUAL
      key 158    BACK    VIRTUAL
    3. Add a '#' before each line so it would look like this:
      Code:
      #key 139    MENU    VIRTUAL
      #key 102    HOME    VIRTUAL
      #key 158    BACK    VIRTUAL
    4. Save the file and exit.
  • Disabling capacitive key lights.
    1. Download Capacitive Buttons app from Play Store.
    2. Open it and grant su access.
    3. Select the first option i.e no brightness.
    4. Reboot

DONE:cowboy:
 
Last edited:

FcukBloat

Senior Member
Jun 18, 2012
6,283
3,012
working great!! thanks for sharing!! ;)

f2a3708e3962f1412bfc7c18b0fa9d4f.jpg
 
Last edited:

mandarpalshikar

Senior Member
Feb 3, 2008
58
10
Thx for this mate.

I am unable to boot the system after enabling on-screen nav bar by editing build.prop...... Shows starting MI logo and then a blues flash and again restart. It goes into this loop.
As soon as I remove that "qemu.hw.mainkeys=0" from it, system is botting :(
 

deepesh.tickoo

Senior Member
Mar 15, 2011
733
388
New Delhi
Thx for this mate.

I am unable to boot the system after enabling on-screen nav bar by editing build.prop...... Shows starting MI logo and then a blues flash and again restart. It goes into this loop.
As soon as I remove that "qemu.hw.mainkeys=0" from it, system is botting :(
Can you tell me in detail what exactly you did and which file manager you used?
 
  • Like
Reactions: i_c3man

mandarpalshikar

Senior Member
Feb 3, 2008
58
10
Can you tell me in detail what exactly you did and which file manager you used?

Hi,

I used ES File Explorer first to edit on phone and then rebooted. Phone didn't start so then I went into CWM recocry, pulled file by adb on my desktop, removed the line which I had inserted and then pushed file back to system. Gave 644 permission and rebooted. Device worked this time.

Lemme know if there is any other way. One thing I cld try is edit the file on desk and push through ADB. Earlier I had inserted required line with ES Explorer and editor.

Thanks in advanced.

Regards,
Mandar

Sent from my MI 3W using XDA Premium HD app
 

deepesh.tickoo

Senior Member
Mar 15, 2011
733
388
New Delhi
Hi,

I used ES File Explorer first to edit on phone and then rebooted. Phone didn't start so then I went into CWM recocry, pulled file by adb on my desktop, removed the line which I had inserted and then pushed file back to system. Gave 644 permission and rebooted. Device worked this time.

Lemme know if there is any other way. One thing I cld try is edit the file on desk and push through ADB. Earlier I had inserted required line with ES Explorer and editor.

Thanks in advanced.

Regards,
Mandar

Sent from my MI 3W using XDA Premium HD app
Yea do try that and report, I think the ES method is messing with the build.prop permissions somehow!
 
  • Like
Reactions: mandarpalshikar

deepesh.tickoo

Senior Member
Mar 15, 2011
733
388
New Delhi
Same here, I too used ES without any issue, but I have faced certain problems with ES regarding saving system level files i edited and problems with proper permissions in the past.
 
  • Like
Reactions: FcukBloat

deepesh.tickoo

Senior Member
Mar 15, 2011
733
388
New Delhi
I guess the issue was with saving the file. May I know how you saved the edited build.prop file in ES Note Editor?
I would like to know this so that I would update that info in the thread, so that in future users can be more careful.
 

Deslang16

Member
Oct 17, 2014
24
0
It worked great for me! Thank you!
Will there be a way to make the navbar transparant instead of black?
Thanks in advanced!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 23
    INTRODUCTION
    This guide is for Ivan's 5.0 Lollipop AOSP ROM but will work with other ROMs as well.

    FEATURES
    • Pure AOSP feel.
    • Many people prefer it, including me.
    • Workaround for 'hardware key wakeup' bug.
    • Can use Lollipop features like Screen Pinning easily.
    • Looks cool:D

    PREREQUISITES
    • Ivan's Lollipop AOSP ROM.(May work on others too)
    • MI3.(Again may work on others too:p)
    • Root.
    • ES File Explorer.(or any file manager with root access)

    INSTRUCTIONS
    • Enabling on-screen nav bar.
      1. Open ES File Explorer and grant su access.
      2. Go to system and open build.prop with ES Note Editor and add this line in the end:
        Code:
        qemu.hw.mainkeys=0
      3. Save build.prop and reboot.
      4. Check if soft keys are enabled.
      5. If enabled successfully, proceed to next section.
    • Disabling hardware capacitive keys.
      1. Go to system/usr/keylayout and open 'atmel-maxtouch.kl' with ES Note Editor.
      2. In the end of that file there will be following three lines:
        Code:
        key 139    MENU    VIRTUAL
        key 102    HOME    VIRTUAL
        key 158    BACK    VIRTUAL
      3. Add a '#' before each line so it would look like this:
        Code:
        #key 139    MENU    VIRTUAL
        #key 102    HOME    VIRTUAL
        #key 158    BACK    VIRTUAL
      4. Save the file and exit.
    • Disabling capacitive key lights.
      1. Download Capacitive Buttons app from Play Store.
      2. Open it and grant su access.
      3. Select the first option i.e no brightness.
      4. Reboot

    DONE:cowboy:
    1
    Thx for this mate.

    I am unable to boot the system after enabling on-screen nav bar by editing build.prop...... Shows starting MI logo and then a blues flash and again restart. It goes into this loop.
    As soon as I remove that "qemu.hw.mainkeys=0" from it, system is botting :(
    Can you tell me in detail what exactly you did and which file manager you used?
    1
    Hi,

    I used ES File Explorer first to edit on phone and then rebooted. Phone didn't start so then I went into CWM recocry, pulled file by adb on my desktop, removed the line which I had inserted and then pushed file back to system. Gave 644 permission and rebooted. Device worked this time.

    Lemme know if there is any other way. One thing I cld try is edit the file on desk and push through ADB. Earlier I had inserted required line with ES Explorer and editor.

    Thanks in advanced.

    Regards,
    Mandar

    Sent from my MI 3W using XDA Premium HD app
    Yea do try that and report, I think the ES method is messing with the build.prop permissions somehow!
    1
    Same here, I too used ES without any issue, but I have faced certain problems with ES regarding saving system level files i edited and problems with proper permissions in the past.