Develop Bugs

Gesture Control (root)

I'm developing application that allows you to control tablet with gestures. Root access is needed. Currently it allows to execute following gestures: Back, Home, Show/Hide status bar
Try it out and let me know what you think. What other features or actions would be helpful?
All differences from other devices fixed. Please visit main thread.
http://forum.xda-developers.com/showthread.php?t=1535740

This sounds quite awesome. Does this potentially work on all HC tablets, or just the A100 and A500?

This does not work properly. It always says "Root failed" even when I grant it Superuser permissions. The only fully working feature is the "hide status bar" option. This app still seems to have potential though.

willverduzco said:
This sounds quite awesome. Does this potentially work on all HC tablets, or just the A100 and A500?
Click to expand...
Click to collapse
Potentially it works on all tablets, I just need a little bit of information. It even works on my SGS2 phone when I build it with decreased SDK requirements.
Could anyone test version (updated) from first post and send me logcat?

StupidIdea said:
Could anyone test version (updated) from first post and send me logcat?
Click to expand...
Click to collapse
Tested - It still does not work properly. Logcat attached.

Thanks, that explains the problem. I don't recognize multitouch properly on this device. Could you execute
from shell
su -c "getevent"
or from adb that would be
adb shell su -c "getevent"
make a few multitouch and send me output.

Added single touch option. Multitouch gestures not supported on this device at the moment.
Can anyone confirm that singletouch gestures are working on A100?

StupidIdea said:
Added single touch option. Multitouch gestures not supported on this device at the moment.
Can anyone confirm that singletouch gestures are working on A100?
Click to expand...
Click to collapse
I'll give it a try .
EDIT: Single touch gestures work perfectly .
StupidIdea said:
What other features or actions would be helpful?
Click to expand...
Click to collapse
You could add a gesture to disable the backlight (turn off screen). You could also add gestures to open certain apps (like browser, etc.) and possibly make them configurable.

Theonew said:
I'll give it a try .
EDIT: Single touch gestures work perfectly .
Click to expand...
Click to collapse
Good. Still need to investigate where multi touch disappeared.
Could you execute
from shell
su -c "getevent"
or from adb that would be
adb shell su -c "getevent"
make a few multitouch and send me output.

New version
1.2.1
- Added check for USB Debugging
Still want to need information in order to fix multitouch. See post above.

StupidIdea said:
Good. Still need to investigate where multi touch disappeared.
Could you execute
from shell
su -c "getevent"
or from adb that would be
adb shell su -c "getevent"
make a few multitouch and send me output.
Click to expand...
Click to collapse
StupidIdea said:
Still want to need information in order to fix multitouch. See post above.
Click to expand...
Click to collapse
Log attached . Hope the format isn't too new for you .

Thanks, I fixed it. Updated first post. Can you confirm, that multitouch works now?

good job
Any chance at getting touch to wake to work with this app
Sent from my HTC EVO 3D using XDA

StupidIdea said:
Change log:
1.2.2
- Fixed multitouch on A100 (and probably similar devices) - Thanks to Theonew
Click to expand...
Click to collapse
StupidIdea said:
Thanks, I fixed it. Updated first post. Can you confirm, that multitouch works now?
Click to expand...
Click to collapse
It works perfectly now. Great job, great app, and no problem for my help .

Theonew said:
It works perfectly now. Great job, great app, and no problem for my help .
Click to expand...
Click to collapse
Great app! Wonderful developer with whom to work. Kept in touch and fixed all the issues as promised. I hope he writes more apps.

Thanks everyone for help. I published update to market.
All differences are fixed now, so further discussion moving to the main thread:
http://forum.xda-developers.com/showthread.php?t=1535740"]http://forum.xda-developers.com/showthread.php?t=1535740[/URL]

[FIX] Capacitive buttons NOT lighting up on AOKP with Auto-brightness off

This is a dirty fix. I have an idea for a better fix but I am unable to implement it.
These are scripts to be run with Script Manager.
Code:
led_on script:
#!/system/bin/sh
print 80 > /sys/class/leds/button-backlight-portrait/brightness
print 80 > /sys/class/leds/button-backlight-landscape/brightness
led_off script:
#!/system/bin/sh
print 0 > /sys/class/leds/button-backlight-portrait/brightness
print 0 > /sys/class/leds/button-backlight-landscape/brightness
The value can be set from 0 to 255. I chose 80 as it is good enough and also due to a known issue, as explained below.
Obviously enable root browsing in SManager and run this as root. You can also run led_on at boot if needed. This is a fix when not using auto-brightness.
This will cause the capacitive buttons to ALWAYS be on, even when the screen is off. A simple idea is to check the status of the screen and then appropriately modify that file. But this means a service running in the background and is probably wasteful on resources. But if someone can help me out or have ideas, go ahead and do so. But once done, please lemme know as I am trying to learn.
Lemme know of other issues!
Cheers!

litetaker said:
This is a dirty fix. I have an idea for a better fix but I am unable to implement it.
These are scripts to be run with Script Manager.
Code:
led_on script:
#!/system/bin/sh
print 50 > /sys/class/leds/button-backlight-portrait/brightness
led_off script:
#!/system/bin/sh
print 0 > /sys/class/leds/button-backlight-portrait/brightness
The value can be set from 0 to 255. I chose 50 as it is good enough and also due to a known issue, as explained below.
Obviously enable root browsing in SManager and run this as root. You can also run led_on at boot if needed. This is a fix when not using auto-brightness.
This will cause the capacitive buttons to ALWAYS be on, even when the screen is off. A simple idea is to check the status of the screen and then appropriately modify that file. But this means a service running in the background and is probably wasteful on resources. But if someone can help me out or have ideas, go ahead and do so. But once done, please lemme know as I am trying to learn.
Lemme know of other issues!
Cheers!
Click to expand...
Click to collapse
Awesome work. I'm not feeling so well tonight or I would look into it bro.
Sent from my Incredible 2 using xda premium

litetaker said:
This is a dirty fix. I have an idea for a better fix but I am unable to implement it.
These are scripts to be run with Script Manager.
Code:
led_on script:
#!/system/bin/sh
print 50 > /sys/class/leds/button-backlight-portrait/brightness
led_off script:
#!/system/bin/sh
print 0 > /sys/class/leds/button-backlight-portrait/brightness
The value can be set from 0 to 255. I chose 50 as it is good enough and also due to a known issue, as explained below.
Obviously enable root browsing in SManager and run this as root. You can also run led_on at boot if needed. This is a fix when not using auto-brightness.
This will cause the capacitive buttons to ALWAYS be on, even when the screen is off. A simple idea is to check the status of the screen and then appropriately modify that file. But this means a service running in the background and is probably wasteful on resources. But if someone can help me out or have ideas, go ahead and do so. But once done, please lemme know as I am trying to learn.
Lemme know of other issues!
Cheers!
Click to expand...
Click to collapse
I see you have something for lights in portrait. Maybe also write it for landscape as the lights always go out in landscape.
Sent from my Incredible 2 using xda premium

knipp21 said:
I see you have something for lights in portrait. Maybe also write it for landscape as the lights always go out in landscape.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Did that. This fix is a very hackey one! I wish I could make a more clean one later...

[RESOLVED][IDEA/REQUEST] Backlight button light up notification

See first post, page 3 for an solution
-------------------------------
Dear XDA,
I've searched for this kinda app but couldn't find it so i decided to make a thread about it.
Anyway, i was wondering if it's possible to make the backlight of the buttons light up when there is some kind of notification as the led in the One X is kinda useless imo.(dirt gets into the tiny holes)
If it IS possible, does someone want to take the effort to try and make such an application/mod?
I'll be eager and happy to test it and my thanks will be beyond eternity
Thanks in advance,
Joran

+1
Good idea, but I do think there could be any hardware limitations to make this work....
anyways, sounds great if it could be possible! :good:

I wrote an app called "Capacitive Button Brightness" which lets you control the brightness of the capacitive buttons backlight on the HTC One X: http://forum.xda-developers.com/showthread.php?t=2033973. Someone pointed this thread out to me so I thought I'd chime in with an idea.
I have not tested this (in fact I don't have a device to test it on!) but you might be able to flash the backlight of the capacitive buttons by running the following command from a root terminal:
Code:
echo 1 > /sys/class/leds/button-backlight/blink
If that doesn't work, take a look at the list of files in /sys/class/leds/button-backlight and see if perhaps I got the name of the file wrong. There should be one in there with "blink" in its name.
If this does indeed flash the capacitive button backlight then you could write a simple script in "Tasker" to blink the capacitive button backlight every time that a message is received.
User Vcek reported doing something very similar with Tasker, and I'd recommend to contact him if you have further questions. See http://forum.xda-developers.com/showthread.php?p=35266420#post35266420 and http://forum.xda-developers.com/showthread.php?p=35276999#post35276999

denversc said:
I wrote an app called "Capacitive Button Brightness" which lets you control the brightness of the capacitive buttons backlight on the HTC One X: http://forum.xda-developers.com/showthread.php?t=2033973. Someone pointed this thread out to me so I thought I'd chime in with an idea.
I have not tested this (in fact I don't have a device to test it on!) but you might be able to flash the backlight of the capacitive buttons by running the following command from a root terminal:
Code:
echo 1 > /sys/class/leds/button-backlight/blink
If that doesn't work, take a look at the list of files in /sys/class/leds/button-backlight and see if perhaps I got the name of the file wrong. There should be one in there with "blink" in its name.
If this does indeed flash the capacitive button backlight then you could write a simple script in "Tasker" to blink the capacitive button backlight every time that a message is received.
User Vcek reported doing something very similar with Tasker, and I'd recommend to contact him if you have further questions. See http://forum.xda-developers.com/showthread.php?p=35266420#post35266420 and http://forum.xda-developers.com/showthread.php?p=35276999#post35276999
Click to expand...
Click to collapse
i tried your app but all it does is either off or it's on.
Thanks for the input for this idea:good:, but i'm kinda low skilled (read no skill) in the technical side of the phone.
so i hope someone can try this?
edit: nvm, don't got terminal on this rom yet.

jorank said:
i tried your app but all it does is either off or it's on.
Thanks for the input for this idea:good:, but i'm kinda low skilled (read no skill) in the technical side of the phone.
so i hope someone can try this?
edit: nvm, don't got terminal on this rom yet.
Click to expand...
Click to collapse
You're right, my app won't address the feature you are looking for.
If you want a terminal, you can install "Android Terminal Emulator" from the Play store: https://play.google.com/store/apps/details?id=jackpal.androidterm. You will need to be rooted though.
If you want to test out the "echo" command in the previous post, you will need to run "su" in the terminal before running the "echo" command.

denversc said:
You're right, my app won't address the feature you are looking for.
If you want a terminal, you can install "Android Terminal Emulator" from the Play store: https://play.google.com/store/apps/details?id=jackpal.androidterm. You will need to be rooted though.
If you want to test out the "echo" command in the previous post, you will need to run "su" in the terminal before running the "echo" command.
Click to expand...
Click to collapse
tried the command and i confirm it works

jorank said:
tried the command and i confirm it works
Click to expand...
Click to collapse
Sweet. Now you can use an app like tasker to run that command every time you receive a message. Can anyone help with this?

denversc said:
Sweet. Now you can use an app like tasker to run that command every time you receive a message. Can anyone help with this?
Click to expand...
Click to collapse
I try to create a tasker profile with this. Does someone know a command to stop the blinking?

staffordniko said:
I try to create a tasker profile with this. Does someone know a command to stop the blinking?
Click to expand...
Click to collapse
Same command that is used to enable exept with echo 0.
Sent from my HTC One X

Got it done, how can i post a tasker script here?

Omg guys stop discussing aokp has this feature called button back light notification
Thread can be closes and don't forget to hit the thanks button
Gesendet von meinem HTC One X mit Tapatalk 2

howdid said:
Omg guys stop discussing aokp has this feature called button back light notification
Thread can be closes and don't forget to hit the thanks button
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
and what if i don't want aokp but sense?
think twice please.

Okay so i've installed tasker but i can't find out how to set the appropriate settings for this event.
Anyone did it already?

Did anyone find a solution?

not really, tried tasker but that didn't get me any luck.
so i hope anyone else does

Profile: blink (2)
Event: Notification [ Owner Application:WhatsApp Title:* ]
Enter: blink (3)
A1: Run Shell [ Command:echo 1 > /sys/class/leds/button-backlight/blink Timeout (Seconds):0 Use Rootn Store Result In: ]
A2: Wait [ MS:0 Seconds:4 Minutes:0 Hours:0 Days:0 ]
A3: Run Shell [ Command:echo 0 > /sys/class/leds/button-backlight/blink Timeout (Seconds):0 Use Rootn Store Result In: ]

Did anyone test the battery usage for this?
@staffordniko: You could use a trigger for "screen on" to stop the blinking.

I can confirm that it works. It should be cool to blink one button at a time!
Sent from my EndeavorU using xda app-developers app

A mod like this would be nice!
I'll follow this thread!

I'm trying to export a app with this settings with "Tasker app factory", but no luck so far. Maybe someone know how to do this right? Getting a "package installer stopped" error.
Sent from my HTC One X using xda premium

TouchControl and Tasker

For anyone trying to integrate TouchControl into Tasker as per the instructions in this thread, the syntax has apparently changed with the newest version of the program.
As such:
echo disable > /proc/ponury/status no longer works and should now be echo enabled 0 > /proc/touch_control/<<gesture>>
And:
echo enable > /proc/ponury/status now becomes echo enabled 1 > /proc/touch_control/<<gesture>>
Note that <<gesture>> needs to be replaced with either g_doubletap2wake, g_slide2unlock, g_slide2media_next, g_slide2wake or g_touch2wake, depending on which gesture you want to enable/disable.
I can't seem to find a post anywhere in the thread reflecting these changes so figured I would try to save anyone else trying to accomplish what I was some time and frustration.
As I only have a couple posts I can't post to the Dev section of the forum so perhaps someone could either copy/paste it in the post or maybe link back to this thread. Feel free to verify the above if you need to before linking but it works for me perfectly.
Thanks!

If I have multiple gestures enabled, do I need to disable all of them for this to work?
---------- Post added 10th September 2013 at 12:43 AM ---------- Previous post was 9th September 2013 at 11:53 PM ----------
dave__ said:
If I have multiple gestures enabled, do I need to disable all of them for this to work?
Click to expand...
Click to collapse
Played around with it a bit more tonight and it works by just having each echo statement on a seperate line in the shell command, like so:
echo enabled 0 > /proc/touch_control/g_slide2wake
echo enabled 0 > /proc/touch_control/g_slide2lock

You can still completely enable/disable Touch Control the old school way without enabling/disabling each individual gesture
echo enable > /proc/touch_control/controller
or
echo disable > /proc/touch_control/controller

Is this working for anybody? I've tried tons of different variations with no success.
Run Shell -> Command: Echo enable 0 > /proc/touch_control/controller
This does not work. I also check marked the "use root" box. Any suggestions?

thanks
i will try it

I got it to work
Here is the correct syntax:
echo disable > /proc/touch_control/controller
Change disable to enable as your exit task or as a "not call any" task.
This will switch touch control entirely off/on. It will remember your settings when it is re-enabled.
Thanks to @evo5ive for pointing me in the right direction with this.

dvorak67 said:
Here is the correct syntax:
echo disable > /proc/touch_control/controller
Change disable to enable as your exit task or as a "not call any" task.
This will switch touch control entirely off/on. It will remember your settings when it is re-enabled.
Thanks to @evo5ive for pointing me in the right direction with this.
Click to expand...
Click to collapse
http://postimg.org/image/pzm78p9n7/
Can you tell me why this isn't working? I'm losing my mind over it! :crying:

Nephilim-Giant said:
http://postimg.org/image/pzm78p9n7/
Can you tell me why this isn't working? I'm losing my mind over it! :crying:
Click to expand...
Click to collapse
You are using the Touch Control app, correct? Not s2w, which many kernels have implemented?
This is what I did on my Nexii 4 and 5 to successfully disable the Touch Control app. Note that you will have to completely close and reopen Touch Control to see this work (swipe it out of your recent app list). I will see if I can export this as an app to share and will update this post.
Can you verify that the file: "/proc/touch_control/controller" exists? Proc is located at the root level, so you'll need a root file explorer like ES if you don't have one already.

dvorak67 said:
You are using the Touch Control app, correct? Not s2w, which many kernels have implemented?
This is what I did on my Nexii 4 and 5 to successfully disable the Touch Control app. Note that you will have to completely close and reopen Touch Control to see this work (swipe it out of your recent app list). I will see if I can export this as an app to share and will update this post.
Can you verify that the file: "/proc/touch_control/controller" exists? Proc is located at the root level, so you'll need a root file explorer like ES if you don't have one already.
Click to expand...
Click to collapse
I'm using Touch Control app. Not s2w of any kernels (never even downloaded one).
I'm running 4.4 kitkat on Nexus 5. I do see the "/proc/touch_control/controller", along with "g_doubletap2wake" and three others.
I posted an image on my previous post, is that the correct implementation? Otherwise, I'm quite stumped .
I'm extremely grateful for the time you are taking to help me out, I appreciate it!

Nephilim-Giant said:
I'm using Touch Control app. Not s2w of any kernels (never even downloaded one).
I'm running 4.4 kitkat on Nexus 5. I do see the "/proc/touch_control/controller", along with "g_doubletap2wake" and three others.
I posted an image on my previous post, is that the correct implementation? Otherwise, I'm quite stumped .
I'm extremely grateful for the time you are taking to help me out, I appreciate it!
Click to expand...
Click to collapse
I'm sorry, I don't know what the problem is for you here. It works for me, and you seem to have it set up the same way. The only thing I can think to try is to check your trigger states in Tasker.

Hey dvorak, I setup my scripts like you did a couple above and it looks like they are working (disables and enables when I hit "play" in tasker to test them). I made two profiles, one for Call Any and another for Orientation Face Down and put them as enter/exit tasks. I haven't had a chance to try the call profile, but when I flip the phone face down and slide it still wakes up. I tried to nudge it to edge of the table to ensure it is flat and it still is enabled. Any advice?
Thanks!

Dude ! Thank you ! I couldn't stand my phone to do whatever in my pocket while I'm biking !!

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!