Develop Bugs

[App] NOT-VERY-INTERESTING Bar

Standard Disclaimer: I am in no way responsible for your device ,marriage, or social life, so don't come crying to me when something happens to one or all of them. You assume all responsibility and risk.
THIS APP IS BETA:
This is a simple app I made for the A100 semi- based off the popular HideBar app by Pieter Pareit. What this app does is allow you to use the capacitive Home Button on the device (A100) to toggle the Notification Bar on/off.
HOW TO SET UP​
Download the two files in the folder
Take the "gpio-keys.kl" file and move it to "/system/usr/keylayout" (make sure to make a backup of the old one before pasting)
Make sure permissions are set to RWXRWXRWX or at LEAST RW-R--R--
Now Install the downloaded APK like normal.
FILES CAN BE FOUND HERE
HOW TO USE​The gpio-keys file basically changes the home button to act as a search button (which this beta app uses) so to use the toggle, just LONG PRESS the search button and select the toggle. The first time it will ask for root permissions. I do recommend setting it as the default app. There is no app icon.
TO DO: This app is in beta, so I need you guys to let me know any bugs you find! Besides that I plan to bypass the need to use a search button.
THANKS TOO: dima_tr for, Pieter Pareit for his HideBar App , sanixk for his tutorial on how to remap hardware keys , crossix for his continued development on this device ,aznmode for letting us all know about HideBar originally , and Acer for a great tablet

Just in case
Sent from my Acer A100 using XDA Premium

What I get no thanks for initially posting the hidebar app? lol. Jk I dont think I was the first one to. Anyway, thanks for this. Will try it out when I get home!

aznmode said:
What I get no thanks for initially posting the hidebar app? lol. Jk I dont think I was the first one to. Anyway, thanks for this. Will try it out when I get home!
Click to expand...
Click to collapse
You actually were the first to post about it xD (at least that I saw) so definitely added your name.
Let me know how it works for you
Sent from my EVO 4G

I can't seem to get this working on my A10. I put the gpio-keys.kl file where it belongs. I installed the apk. Permissions are correct. I may be wrong but seems that the gpio-keys.kl from the download is identical to the one in my "/system/usr/keylayout"
this is the one I downloaded
key 136 SEARCH WAKE_DROPPED
key 139 MENU WAKE
key 102 HOME
key 158 BACK WAKE_DROPPED
key 116 POWER WAKE
key 115 VOLUME_UP WAKE_DROPPED
key 114 VOLUME_DOWN WAKE_DROPPED
this one is my backup copy from "/system/usr/keylayout"
key 136 SEARCH WAKE_DROPPED
key 139 MENU WAKE
key 102 HOME
key 158 BACK WAKE_DROPPED
key 116 POWER WAKE
key 115 VOLUME_UP WAKE_DROPPED
key 114 VOLUME_DOWN WAKE_DROPPED
am i missing something?

You have to change
key 102 HOME
to
key 102 SEARCH

simoneser said:
You have to change
key 102 HOME
to
key 102 SEARCH
Click to expand...
Click to collapse
Yes that is correct I thought I changed it to make it easier I apologize ill fix that.
Thanks simoneser
EDIT:I reuploaded the gpio-keys.kl file. Should work fine now, I apologize.
Sent from my EVO 4G

got it working
I like it so far. I'm going to check it out for a while. Thanks!

Good job! it works great. There is a typo in gpio-keys.kl though, an `s` is the first char.

eww245 said:
Good job! it works great. There is a typo in gpio-keys.kl though, an `s` is the first char.
Click to expand...
Click to collapse
Thanks for letting me know, I reuploaded a fixed version. =)
Hopefully in the next couple weeks ill have a version that doesn't need an extra gpio-keys file and just uses the home button, but that looks like it takes looking into the binding and not just android.intents so with a busy life don't hold me on the time frame

Thanks allot for making the app. Any known issues we should watch out for or things we should avoid doing with it enabled etc?

I did find an issue with using this. I was watching a video in Netflix with my taskbar hidden and the home button worked as a search button only. The long press would not work. I had no way to exit the program without restarting my tab. Any way to fix this? I'm sure there are other apps that would have this issue as well.
Sent from my A500 using xda premium

NoSudo said:
Thanks allot for making the app. Any known issues we should watch out for or things we should avoid doing with it enabled etc?
Click to expand...
Click to collapse
Well the only issue is that at the moment this does call for the search button so any app that doesn't have a need for it won't be able to launch the app.
As for the problem above (cant multiqoute on tapatalk) that's a weird issue , but it seems like it goes along with what I said above and their is no workaround until I make the app use the home button as a "home button"
Sent from my EVO 4G

will you continue to work on this to make it more functional?
thanks for the hard work put in it anyway

nunoruf said:
will you continue to work on this to make it more functional?
thanks for the hard work put in it anyway
Click to expand...
Click to collapse
Oh wow, I almost forgot about this (not in the A100 threads much)
But I suppose it's possible. I'm not very sure about ICS compatibility, but I'll take another look at this soon
Sent from my EVO 3D using Tapatalk 2

Yes, it would be amazing if you could find the time to update this to be ICS compatible!

Yes please make this ics compatible
Sent from my A100 using Tapatalk 2

Any progress on this purty please?

I don't have a comp right now so I can't work on this. Eventually though
Sent from my PG86100 using Tapatalk 2

yes ..
yes...
+1 for ICS compatibility !

Change circle button

Is there a way to make the circle button not to be recognized as the back button on an jelly bean rom ?
Particularly on emulators like n64oid where the back button toggles a bar, it's really annoying
I tried modifying the keylayout but it completely bugged up several other keys
Any help here ?
Thanks in advance...

I would also like to know.
Gingerbread and ICS instructions too if possible.

you need to edit a keymap file , not sure where it is on jb
Sent from my R800i using Tapatalk 2

even when u edit the keymap, not every app will detect it properly..., and u risking mess up other key, this is never ending bug story with un-official (non beta) ICS & JB Rom..

I TRIED modifying the keylayout files, but it messed so much other keys that I abandonned, perhaps I did it incorectly ?
It messed up the home key and most of the keypad, just for changing 305 to BUTTON_B
EDIT : fixed it : found a mirror of a fix, and it worked flawlessly thanks for the help anyway

DarkVarano said:
I TRIED modifying the keylayout files, but it messed so much other keys that I abandonned, perhaps I did it incorectly ?
It messed up the home key and most of the keypad, just for changing 305 to BUTTON_B
EDIT : fixed it : found a mirror of a fix, and it worked flawlessly thanks for the help anyway
Click to expand...
Click to collapse
Please share!

Why dont people share!?

ermacwins said:
Why dont people share!?
Click to expand...
Click to collapse
Its already been shared. But it doesnt fix the circle button issue for certain applications that require the sony framework.

chery2k said:
Its already been shared. But it doesnt fix the circle button issue for certain applications that require the sony framework.
Click to expand...
Click to collapse
Where is this fix? because my circle button is fine now but the select button now acts as back. What needs to be changed? I will ask some of the Nexus 4 devs to make the neccessary changes.

ermacwins said:
Where is this fix? because my circle button is fine now but the select button now acts as back. What needs to be changed? I will ask some of the Nexus 4 devs to make the neccessary changes.
Click to expand...
Click to collapse
Post #1 requires you to make changes to your build prop. Note this doesn't fix circle button 100% correctly.
http://forum.xda-developers.com/showthread.php?t=1862722

chery2k said:
Post #1 requires you to make changes to your build prop. Note this doesn't fix circle button 100% correctly.
http://forum.xda-developers.com/showthread.php?t=1862722
Click to expand...
Click to collapse
Thanks, but I think I have sussed it shortly after my last post without any build prop editing. though when I save the profile in sixaxis it doesnt show the profile in the app but there is an output file on the sdcard. I will post the details later. Dev was very helpful

[Q] How do I enable softkeys on the American Zenfone 2 4GB RAM model?

I've tried editing every build prop file in the system folder and it fails to add software buttons.

TR88 said:
I've tried editing every build prop file in the system folder and it fails to add software buttons.
Click to expand...
Click to collapse
There are definitely apps on the Play Store that can superimpose softkeys on the screen at the bottom, if you really don't like the capacitive ones.

cmendonc2 said:
There are definitely apps on the Play Store that can superimpose softkeys on the screen at the bottom, if you really don't like the capacitive ones.
Click to expand...
Click to collapse
Funny enough I installed a softkeys app for rooted devices off the play store and it put my phone in a bootloop...looks like I'm going to have to flash the factory firmware.

TR88 said:
Funny enough I installed a softkeys app for rooted devices off the play store and it put my phone in a bootloop...looks like I'm going to have to flash the factory firmware.
Click to expand...
Click to collapse
The one that makes the softkeys floating at the bottom?

cmendonc2 said:
The one that makes the softkeys floating at the bottom?
Click to expand...
Click to collapse
I believe it edited the build prop so it was navigation buttons, not superimposed.
The reason I was trying to get the navigation buttons back by the way was because the capacitive stopped working.

TR88 said:
I believe it edited the build prop so it was navigation buttons, not superimposed.
The reason I was trying to get the navigation buttons back by the way was because the capacitive stopped working.
Click to expand...
Click to collapse
It might be bootlooping because if you try to enable a feature (in the build prop) that isn't on the device (the actual system files), it can't boot up correctly.

cmendonc2 said:
It might be bootlooping because if you try to enable a feature (in the build prop) that isn't on the device (the actual system files), it can't boot up correctly.
Click to expand...
Click to collapse
That's most likely the case, I was just getting frustrated and installed the app without thinking, oh well.
I just want the navigation bar because, at least from my experience, most apps that superimpose the buttons are never the same. They won't appear at boot, interfere with the keyboard, and require a gesture to make them appear.

Doesnt gravity box have an option? Never tried it though.. just saying it might work.

i saw someone doing this but cant remeber where. Look in the develompent forum or in Google+ asus zenui beta development

I've been using this app for the last two years. I can highly recommend it.
http://forum.xda-developers.com/showthread.php?t=2270198

Install LP xposed, and LP gravity box, go to "navigation bar tweaks" and tick "master switch" "enable navigation bar" and soft reboot done =]

You have to edit the correct build.prop in /system/ that corresponds to your Zenfone 2 model.
If you have the same model as me (WW/64GB/4GB RAM/2.3GHz), you need to edit build.ze551.dual.2p3GHz.prop
If you look through my posting history, you'll see me offer a link to a guide on doing it, link also includes info on disabling the capacitive buttons. On mobile so can't look through myself. Cheers.

You could use one hand mode until you find a working one.
Sent from my ASUS_Z00AD using XDA Free mobile app

Use Pie Control from the market

rlaw said:
You have to edit the correct build.prop in /system/ that corresponds to your Zenfone 2 model.
If you have the same model as me (WW/64GB/4GB RAM/2.3GHz), you need to edit build.ze551.dual.2p3GHz.prop
If you look through my posting history, you'll see me offer a link to a guide on doing it, link also includes info on disabling the capacitive buttons. On mobile so can't look through myself. Cheers.
Click to expand...
Click to collapse
Yeah I actually found your thread prior to making this, but despite editing that specific modeled build prop, I did not see any results. It always deleted the line of code after I saved changes.
Sent from my T-Mobile LG G4 using Tapatalk

TR88 said:
Yeah I actually found your thread prior to making this, but despite editing that specific modeled build prop, I did not see any results. It always deleted the line of code after I saved changes.
Sent from my T-Mobile LG G4 using Tapatalk
Click to expand...
Click to collapse
Strange it worked for me perfectly.

How do I disable hardware keys / Cyanogen12 [5.1.1]

So the hardware keys on Samsung tablets really annoy me. For over a year I've had to deal with randomly getting knocked out of my e-reader, comic book reader, web browser, etc. just by accidentally sliding my palm against them. What a terrible design. I had originally rooted this tablet in order to try to enable on-screen nav and disable hardware keys. I could never get that working. The instructions surrounding build.props simply didn't work with Samsung's stock firmware.
So I finally go around to installing TeamWin, wiping and installing a CyanogenMod Nightly
cm_chagallwifi-userdebug 5.1.1 LMY49J 11fa7f9ea1
I was able to enable onscreen navigation using the following command
Code:
settings put secure dev_force_show_navbar 1
That works perfectly. However, I still can't disable my physical keys. Most of the instructions I've read say to mount /system as writeable and then comment out the MENU, BACK and HOME key codes from /system/usr/keylayout/Geneic.kl. I've commented out keycodes 127 (Menu), 158 (back)and 172 (home), yet after a reboot, my hardware keys are still enabled.
I also found a noSoftkeyBacklight.zip file that is intended to disable the backlights. I looked in the zip before installing it (which you should always do!) and it just creates an init script that attempts to echo a 0 to /sys/class/leds/button-backlight/brightness (which doesn't even exist on this version of CyanogenMod12).
I look in the /sys/class/leds directory to see if there were any other files that may control the switch backlights, but couldn't find anything except a ton of annoying recursive symbolic links.
Anyway, how do I disable the physical keys on this thing? It shouldn't be this freakin difficult!!!

djsumdog said:
So the hardware keys on Samsung tablets really annoy me. For over a year I've had to deal with randomly getting knocked out of my e-reader, comic book reader, web browser, etc. just by accidentally sliding my palm against them. What a terrible design. I had originally rooted this tablet in order to try to enable on-screen nav and disable hardware keys. I could never get that working. The instructions surrounding build.props simply didn't work with Samsung's stock firmware.
So I finally go around to installing TeamWin, wiping and installing a CyanogenMod Nightly
cm_chagallwifi-userdebug 5.1.1 LMY49J 11fa7f9ea1
I was able to enable onscreen navigation using the following command
Code:
settings put secure dev_force_show_navbar 1
That works perfectly. However, I still can't disable my physical keys. Most of the instructions I've read say to mount /system as writeable and then comment out the MENU, BACK and HOME key codes from /system/usr/keylayout/Geneic.kl. I've commented out keycodes 127 (Menu), 158 (back)and 172 (home), yet after a reboot, my hardware keys are still enabled.
I also found a noSoftkeyBacklight.zip file that is intended to disable the backlights. I looked in the zip before installing it (which you should always do!) and it just creates an init script that attempts to echo a 0 to /sys/class/leds/button-backlight/brightness (which doesn't even exist on this version of CyanogenMod12).
I look in the /sys/class/leds directory to see if there were any other files that may control the switch backlights, but couldn't find anything except a ton of annoying recursive symbolic links.
Anyway, how do I disable the physical keys on this thing? It shouldn't be this freakin difficult!!!
Click to expand...
Click to collapse
Only klimtwifi/klimtlte have a method currently to disable the hardware keys, chagallwifi/chagalllte use a different button driver.

deadman96385 said:
Only klimtwifi/klimtlte have a method currently to disable the hardware keys, chagallwifi/chagalllte use a different button driver.
Click to expand...
Click to collapse
Is this for the current firmware?
I have in the past disabled the hardware keys on the t805 and enabled soft keys on a stock, but custom rom, but not sure if this was kitkat or lollipop.

deadman96385 said:
Only klimtwifi/klimtlte have a method currently to disable the hardware keys, chagallwifi/chagalllte use a different button driver.
Click to expand...
Click to collapse
So the current CyanogenMod builds for this tablet have no support to disable hardware keys? Do other roms? I don't see an official MUMI rom? What about the unofficial CM13 roms?
How's the new Cyanogenmod hardware driver work? There's no way to disable hardware keys at all in it? ... I'm kinda sick of dealing with this. This is way more painful than it ever should have been. I should sell this and get something that doesn't have hardware keys.

djsumdog said:
So the current CyanogenMod builds for this tablet have no support to disable hardware keys? Do other roms? I don't see an official MUMI rom? What about the unofficial CM13 roms?
How's the new Cyanogenmod hardware driver work? There's no way to disable hardware keys at all in it? ... I'm kinda sick of dealing with this. This is way more painful than it ever should have been. I should sell this and get something that doesn't have hardware keys.
Click to expand...
Click to collapse
It is samsungs fault nothing to do with cyanogenmod, its a in kernel driver that is diffrent from klimtwifi

Just tested this on a stock XXU1BOG2 rom and disabling hardware keys works fine.
Commenting out 127, 158 and 172 in system/usr/keylayout/generic.kl
Isnt the key file in cm called something different sec_touchscreen.kl or something or other?

ashyx said:
Isnt the key file in cm called something different sec_touchscreen.kl or something or other?
Click to expand...
Click to collapse
Yes! That's did it! The sec_touchscreen.kl contained only two entries for the app switcher and back button. I commented those out and now the keys are disabled. I also found that disabling the backlights can be done easily in the settings too. Thanks!
deadman96385 said:
Only klimtwifi/klimtlte have a method currently to disable the hardware keys, chagallwifi/chagalllte use a different button driver.
Click to expand...
Click to collapse
Turns out you are incorrect. The hardware keys can be disabled on the chagallwifi!

djsumdog said:
Yes! That's did it! The sec_touchscreen.kl contained only two entries for the app switcher and back button. I commented those out and now the keys are disabled. I also found that disabling the backlights can be done easily in the settings too. Thanks!
Turns out you are incorrect. The hardware keys can be disabled on the chagallwifi!
Click to expand...
Click to collapse
That is a way of doing it manually, i was talking about the in kernel method of doing it that lets you change it over a sysfs.

Swap recent and back keys and kill the lights on both buttons.

Having used Samsung's before and other devices, I've become accustomed to the back button being on the right.
I was hesitant about changing this as it would mean that you'll have a back symbol on the left and recent's on the right, even though they've switched, which would look a bit crap to be honest.
Anyway, disabling the backlight's will make it look a lot better whilst you have your buttons swapped
To do this you'll need to be rooted, that's it.
Flashable Zip Method
Here are some zips for flashing via recovery should you not want to edit these files yourself.
ButtonSwapLights0% - Swaps back & recents, kills button backlight
ButtonsDefaultLights0% - Default button order, kills button backlight
ButtonsDefaultLights50% - Default button order, backlight brightness 50%
ButtonsDefaultLights100% - back to normal
Manual Method
Download a text editor capable of altering system files, i personally used QuickEdit which is free in the play store.
Once that's installed
To disable the back light go here with a text editor.
/sys/class/leds/button-backlight/max_brightness change the number in here which will be 255 to 0.
This will switch off the lights immediately.
If you'd like to swap out the buttons so that back is recent and recent is back,.
Go to cypress-cap-sensor.kl which is in
system/user/keylayout/cypress-cap-sensor.kl
and find then simply reverse the text from the following two lines (there's only two in the file anyway)
key 158 BACK VIRTUAL
key 580 APP_SWITCH VIRTUAL
to
key 158 APP_SWITCH VIRTUAL
key 580 BACK VIRTUAL
Reboot the device and the keys will be switched
Enjoy
Thanks to @LeeDroid for putting me onto the location of the recents and back button file. :good:
Another big thanks to @Chronzy for making these zips, very much appreciated :good:
Update : These same zips work with Nougat on both cm and sense based roms.. Can be flashed at the same time of a Rom.

Outstanding job dladz. This is exactly what I was looking for, and so easy in your instructions. Thank you.
Off topic;
What about a lower haptic vibration ? Stock this phone vibrates like a wild rattlesnake in my hand, about to bite me. I thought most phones have a setting to adjust the vibration ? My Galaxy Note 5 does, as well as my LG G5 did and OnePlus One.
I am running LeeDroid ROM and he has specific settings for power abd haptic feedback, but even down to 1 it's still pretty powerful, just too strong for my tastes. I like to feel a slight vibration, nothing much. Is that possible ?

Is there a way to swap the Nav / software keys that some ROM's enable ?

Zorachus said:
Is there a way to swap the Nav / software keys that some ROM's enable ?
Click to expand...
Click to collapse
I'd say there is, but haven't looked into it mate.

Zorachus said:
Outstanding job dladz. This is exactly what I was looking for, and so easy in your instructions. Thank you.
Off topic;
What about a lower haptic vibration ? Stock this phone vibrates like a wild rattlesnake in my hand, about to bite me. I thought most phones have a setting to adjust the vibration ? My Galaxy Note 5 does, as well as my LG G5 did and OnePlus One.
I am running LeeDroid ROM and he has specific settings for power abd haptic feedback, but even down to 1 it's still pretty powerful, just too strong for my tastes. I like to feel a slight vibration, nothing much. Is that possible ?
Click to expand...
Click to collapse
There should be a file which you can edit to make haptic feedback alter, I've never looked into it mate.
Personally I switch feedback off. I don't need it.
Google: marshmallow haptic feedback how to change system
Also mate,, use the thanks button [emoji106] [emoji16]

When i tested the htc 10 i was shocked how the vibration intensity felt.. just like a cheap phone. Sometimes, I cannot understand htc.

DSF said:
When i tested the htc 10 i was shocked how the vibration intensity felt.. just like a cheap phone. Sometimes, I cannot understand htc.
Click to expand...
Click to collapse
Custom kernels + app allow that to be adjusted. I turned mine way down, and it feels a lot better now.

DSF said:
When i tested the htc 10 i was shocked how the vibration intensity felt.. just like a cheap phone. Sometimes, I cannot understand htc.
Click to expand...
Click to collapse
Please. This and haptic feedback has nothing to do with this thread.. If you'd like to speak about this, then please, take it elsewhere.

You can use init.d script to prevent brightness changing on every reboot, i.e
"#! /system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/max_brightness"
Create a file in /system/etc/init.d and paste the above lines (without quotes), and give 755 permission, itll set to 0 before boot Everytime
If on stock rom dont have init.d support then use superSu's su.d, place same file to /system/su.d folder
Sent from my Redmi Note 3 using Tapatalk

Adarsh1998 said:
You can use init.d script to prevent brightness changing on every reboot, i.e
"#! /system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/max_brightness"
Create a file in /system/etc/init.d and paste the above lines (without quotes), and give 755 permission, itll set to 0 before boot Everytime
If on stock rom dont have init.d support then use superSu's su.d, place same file to /system/su.d folder
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Cheers mate, will give it a whirl

Was looking all over the web for this.
Thank you, great job.

dladz said:
Cheers mate, will give it a whirl
Click to expand...
Click to collapse
If you want, i can make automated flashable zip to disable and enable the hardware keys, just upload Cypress-cap-sensor.kl here
Sent from my Redmi Note 3 using Tapatalk

FIFATG said:
Was looking all over the web for this.
Thank you, great job.
Click to expand...
Click to collapse
You're welcome

Adarsh1998 said:
If you want, i can make automated flashable zip to disable and enable the hardware keys, just upload Cypress-cap-sensor.kl here
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
That'd be brilliant, thank you, appreciate that.
Primarily it's the lights coming back on, i tried to lock down the permissions but they're reset on each boot, it isn't the end of the world but it's annoying if you reboot a lot.

Made the init.d file, just seeing if it works.
Will upload once i'm in work.
EDIT: Nah didn't work mate.
Permissions in root explorer are 4 places and not 3.
so 755 comes out like 0755

dladz said:
Made the init.d file, just seeing if it works.
Will upload once i'm in work.
EDIT: Nah didn't work mate.
Permissions in root explorer are 4 places and not 3.
so 755 comes out like 0755
Click to expand...
Click to collapse
You might need to place it in su.d?

This is awesome, thanks!
Quick question regarding the init.d script - I'm currently on the stock rom, rooted with Supersu, but don't have a system/su.d directory. Should this already have existed? I can't create it either due to read only file system.

dladz said:
Made the init.d file, just seeing if it works.
Will upload once i'm in work.
EDIT: Nah didn't work mate.
Permissions in root explorer are 4 places and not 3.
so 755 comes out like 0755
Click to expand...
Click to collapse
@Adarsh1998 thanks for your tip, exactly what this mod needed.
Got it to work in system/etc/init.d, had to enable all permissions: read, write, & exec for all 3 user groups: owner root, group root, and global.... 0777.
It's survived 2 reboots now and the lights are staying off. I might try to scale back the permissions one by one... don't know if there is any danger to leaving all off those permissions enabled.
Thank you both for the info, this is something I wanted to do since I bought the phone (on other devices as well) because i'm used to the Samsung (also older HTC) setup. The no lights looks so slick and the button swap feels perfect. Thanks again!

Chronzy said:
@Adarsh1998 thanks for your tip, exactly what this mod needed.
Got it to work in system/etc/init.d, had to enable all permissions: read, write, & exec for all 3 user groups: owner root, group root, and global.... 0777.
It's survived 2 reboots now and the lights are staying off. I might try to scale back the permissions one by one... don't know if there is any danger to leaving all off those permissions enabled.
Thank you both for the info, this is something I wanted to do since I bought the phone (on other devices as well) because i'm used to the Samsung (also older HTC) setup. The no lights looks so slick and the button swap feels perfect. Thanks again!
Click to expand...
Click to collapse
Thank you.
Flashable zip on the way, thanks to @Adarsh1998 Good times

Adarsh1998 said:
You can use init.d script to prevent brightness changing on every reboot, i.e
"#! /system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/max_brightness"
Create a file in /system/etc/init.d and paste the above lines (without quotes), and give 755 permission, itll set to 0 before boot Everytime
If on stock rom dont have init.d support then use superSu's su.d, place same file to /system/su.d folder
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
This worked perfectly. Thanks!