Related
While the development is still in its infancy here,
lets post here a bunch of do it yourself tweaks.
Feel free to post any rom tweaks you know of.
In the file /system/etc/init.qcom.post_boot.sh , find the section
case "$target" in
"msm8960" | jaguar* | M2* | m2* )
Click to expand...
Click to collapse
then modify the following value:
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
Click to expand...
Click to collapse
This will improve the touchscreen responsiveness.
Add the following line at the end of the msm8960 section:
echo 1024 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
Click to expand...
Click to collapse
This will speed up loading of apps somewhat.
Reboot for changes to take effect.
In the same file you can have it run every init.d file if you don't have init.d support.
Sent from my SPH-D700 using Tapatalk 2
governor tweaks
if on the on-demand governer i recommend you change the sampling rate to 70,000, it improves the devices scaling performance i.e if your device is sitting for a sec. and you touch the screen it should jump to a higher frequency to perform the action faster at the cost of a little bit higher battery consumption but a minuscule amount. And of course please all use the noop i/o scheduler it really does improve responsivness of the phone by alot.
I will aslo be uploading a sys ctl.conf tweak to greatly improve our battery life my og epic increased by 3 hours because of this it is a cwm flashable but for those who dont feel like using it you can always use a root explorer and copy and paste or adb push it. i will post when i know it works
file is migrating to new host this is the link you have to take it apart and either copy and paste or adb push, the install script is giving me trouble will post back when i get around to fixing it unless some brave soul would like to fix it for me idc its all about you guys so if you wanna beat me to it be my guest
and remember always make a nandroid
I would also like to say i did not create this and i have absolutly no idea who did this mod has been circulating around xda's htc forums,android central, and droid forums as far as im concerned the maker of this mod is untraceable.
V6supercharger makes a world of a difference in the memory management section and no ram is waisted it is devoted to the cache for our devices its a pain to set up because we are on odex stock devices ice is a bitc* that way haha.
I found this thread here with several build.prop tweaks... He claims they work on all devices. I am an Android newbie so I can not verify that information.
http://forum.xda-developers.com/showthread.php?t=1639104
matrixzone5 said:
if on the on-demand governer i recommend you change the sampling rate to 70,000, it improves the devices scaling performance i.e if your device is sitting for a sec. and you touch the screen it should jump to a higher frequency to perform the action faster at the cost of a little bit higher battery consumption but a minuscule amount. And of course please all use the noop i/o scheduler it really does improve responsivness of the phone by alot.
I will aslo be uploading a sys ctl.conf tweak to greatly improve our battery life my og epic increased by 3 hours because of this it is a cwm flashable but for those who dont feel like using it you can always use a root explorer and copy and paste or adb push it. i will post when i know it works
Remove this is the link you have to take it apart and either copy and paste or adb push, the install script is giving me trouble will post back when i get around to fixing it unless some brave soul would like to fix it for me idc its all about you guys so if you wanna beat me to it be my guest
and remember always make a nandroid
I would also like to say i did not create this and i have absolutly no idea who did this mod has been circulating around xda's htc forums,android central, and droid forums as far as im concerned the maker of this mod is untraceable.
Click to expand...
Click to collapse
Gotta ask you to remove your link. Third-party downloads that require signing in/up are prohibited.
I'm sorry about that bro I understand its totally annoying I forgot u gotta sign up now for 4shared ill upload it to media fire the second I get a chance
Note to mod* remove if you can please
Sent from my SPH-L710 using XDA
Doesn't build.prop cover most do-it-yourself tweaks?
Yes but there's still ur susctl .conf file u can play with if u go to sustem/etc I believe there is a file u can edit to boost the Max speaker volune
I personally love ofinding new little tweaks to apply and edit in android I love poking and prodding around just to find out what does what whether removing this and replacing it with *,that will benefit perform
Sent from my SPH-L710 using XDA
Terminal emulator cmd
getprop til.MSL Works for getting your msl # to change the settings for faster 3g in ##DATA# menu under the multimedia tab.
If you know what I mean.
Sent from my PB GS3 using XDA
Tewlman252 said:
Terminal emulator cmd
getprop til.MSL Works for getting your msl # to change the settings for faster 3g in ##DATA# menu under the multimedia tab.
If you know what I mean.
Sent from my PB GS3 using XDA
Click to expand...
Click to collapse
I've tried this both with
Code:
getprop til.MSL
&
Code:
getprop ril.MSL
and can't get it to display the MSL, any ideas?
And yes I entered "su" prior to typing the cmd, I actually have terminal setup to do that automatically.
Sent from my SPH-L710 using Tapatalk 2
Strange, it worked for me the first time but now no luck.
Sent from my SPH-L710 using XDA
Tewlman252 said:
Strange, it worked for me the first time but now no luck.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
That's weird, hmmph.
Sent from my Transformer TF101 using Tapatalk 2
carhauler1969 said:
I've tried this both with
Code:
getprop til.MSL
&
Code:
getprop ril.MSL
and can't get it to display the MSL, any ideas?
And yes I entered "su" prior to typing the cmd, I actually have terminal setup to do that automatically.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
What app are you using to control ur su binary? Super user?
And did you try typing just get prop and scrolling through
Sent from my GT-I9100 using xda app-developers app I recommend using supersu by chain fire for super user on ics
Tewlman252 said:
Terminal emulator cmd
getprop til.MSL Works for getting your msl # to change the settings for faster 3g in ##DATA# menu under the multimedia tab.
If you know what I mean.
Sent from my PB GS3 using XDA
Click to expand...
Click to collapse
Can you clarify this? Thanks
Courtesy of our own Qbking77
http://www.youtube.com/watch?v=RQRZ2Z_IQkY&feature=youtube_gdata_player
This is how I got it to work the first time on my GS3 from Sprint but subsequent tries have failed. Not sure if it's just a one time thing or not.
Needless to say, now that I have my MSL, I don't need to get it again unless I switch devices.
Sent from my SPH-L710 using XDA
Another tip to save battery is enable power saving mode. It automatically scales back the cpu governor to a max speed of 1.026 ghz. Unless you're gaming, this should be fine for day to day usage.
I have tested this with cpu spy and no frills cpu control.
Sent from my SPH-L710 using XDA
nabbed said:
While the development is still in its infancy here,
lets post here a bunch of do it yourself tweaks.
Feel free to post any rom tweaks you know of.
In the file /system/etc/init.qcom.post_boot.sh , find the section
then modify the following value:
This will improve the touchscreen responsiveness.
Add the following line at the end of the msm8960 section:
This will speed up loading of apps somewhat.
Reboot for changes to take effect.
Click to expand...
Click to collapse
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
this part showed a 90 in my script. i just want to verify that the instruction is to change the 90 to an 80. or is the instruction to alter it how i wish, and the 80 is just what you picked?
stretchwookie said:
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
this part showed a 90 in my script. i just want to verify that the instruction is to change the 90 to an 80. or is the instruction to alter it how i wish, and the 80 is just what you picked?
Click to expand...
Click to collapse
Its alot easier if you used an app like setcpu and go to governed setting ans change the up thresh hold to 80 remember the lower the number the higher the performance at the cost of Max battery life but never set it to 100 it freezes really badly. 99 is even a stretch u shudnt need to go over 95
Sent from my SPH-L710 using xda app-developers app
I see a few people asking about this and I found this app that works on my HTC One X.
Screen Filter:
https://play.google.com/store/apps/details?id=com.haxor&hl=en
If you just want to switch the lights off, set the filter to 100% then un-tick the enable softkey back light. It works great when watching videos or using it as a nightstand clock.
Hope their wasn't a thread about his. I did a few searches and couldn't find anything, hope this helps a few people.
Does it save the preference after reboot? I use Adjbrightness and after rebooting I have to load the app up again.
Sent from my HTC One X using xda app-developers app
I will have a look but I think you have to reopen it.
Sent from my HTC One X using xda app-developers app
I had a test now and it doesn't start on boot. But when you start the app after a boot it then knows what your last settings were. Hope that helps.
Sent from my HTC One X using xda app-developers app
K, when I have the time I was thinking of writing my own app that does this.
Sent from my HTC One X using xda app-developers app
If u put the app (screenfilter) in some autostart program it will work fine, if u dont wanna enable it manually.
This text was generated by a HoX device, in symbiosis with thoughts from someone else
ououououo said:
If u put the app (screenfilter) in some autostart program it will work fine, if u dont wanna enable it manually.
This text was generated by a HoX device, in symbiosis with thoughts from someone else
Click to expand...
Click to collapse
That is a great idea, I was wondering if there was an app like that I will have a look and see how well that works. But it's really nice to disable those lights, gives the phone a really neat appearance.
Roars21 said:
That is a great idea, I was wondering if there was an app like that I will have a look and see how well that works. But it's really nice to disable those lights, gives the phone a really neat appearance.
Click to expand...
Click to collapse
I did this on my previous device (xperia u, to get rid of the annoying LED-bar )
NOTE:
*** If you accidentally make your screen go BLACK ***
1. Pull your battery
2. Uninstall the app to reset your bad brightness setting
3. Reinstall the app and use it normally again"
Click to expand...
Click to collapse
I am kinda worried about this happening on my HOX...the fist step is already too much trouble to go through.
jimmy2027 said:
I am kinda worried about this happening on my HOX...the fist step is already too much trouble to go through.
Click to expand...
Click to collapse
Don't worry if you hold down the power button for a couple seconds it simulates a battery pull. Then when you start up, provided you don't have it on a autostart app you can then go in and change the settings. Also if you do set the brightness too low it gives you 10 seconds to approve it or it will just revert your settings. If that makes sense.
Make a new file, call it 99KeyOff.sh and put this in it:
#!/system/bin/sh
# ========================================
# init.d script for key light off. ONE X.
#BACKFROMTHE[/QUOTE]STORM
# ========================================
#disable Key Backlight
echo begin set Key Backlight - KB
echo KB - set permissions rw
chmod 0666 /sys/class/leds/button-backlight/brightness
echo KB - set Key Backlight 0
echo "0" > /sys/class/leds/button-backlight/brightness
echo KB - set permissions ro
chmod 0444 /sys/class/leds/button-backlight/brightness
echo KB - done!
Put it in the init.d folder or run it manually in a terminal emulator or script manager.
Unfortunately that doesn't work on the Maximus ROM. I think it's because the rootfs mounts read only. I tried adding a remount line to the top but nothing happened.
Sent from my HTC One X using xda app-developers app
My keyboard backlight trigger stopped working so i have no backlight when the keyboard is opened.
I was hoping to write a script to toggle the backlight using a spare hardware key on the keyboard (368, that silly search/browser key below the enter key).
I have written 2 scripts to turn it on and off which were really simple (and work :victory but a toggle script looks a lot harder.
OFF
Code:
#!/system/bin/sh
echo "0">/sys/class/leds/keyboard-backlight/brightness
ON
Code:
#!/system/bin/sh
echo "255">/sys/class/leds/keyboard-backlight/brightness
Can anyone help me with this, i suspect it would be pretty simple for someone familiar with scripts.
DId i mention i know nothing about writing scripts...
Code:
#!/system/bin/sh
state=`cat /sys/class/leds/keyboard-backlight/brightness`
if [ "$state" == 0 ]; then
echo "255" > /sys/class/leds/keyboard-backlight/brightness
else
echo "0" > /sys/class/leds/keyboard-backlight/brightness
fi
Thanks ameer but it doesn't seem to work, it will turn the backlight on but will not turn it off again.
Tironsteel said:
Thanks ameer but it doesn't seem to work, it will turn the backlight on but will not turn it off again.
Click to expand...
Click to collapse
Did your previous script turn it off?
ameer1234567890 said:
Did your previous script turn it off?
Click to expand...
Click to collapse
Yes it did.
I tried running the Toggle script after the backlight was already on as well and it still didnt turn it off. Only way to turn it off is to run the OFF script.
Tironsteel said:
Yes it did.
I tried running the Toggle script after the backlight was already on as well and it still didnt turn it off. Only way to turn it off is to run the OFF script.
Click to expand...
Click to collapse
How did you run the scripts?
ameer1234567890 said:
How did you run the scripts?
Click to expand...
Click to collapse
Script Manager - SManager app
Also tried it in terminal to no avail.
Surprisingly, it works perfectly on my Xperia Pro.
ameer1234567890 said:
Surprisingly, it works perfectly on my Xperia Pro.
Click to expand...
Click to collapse
Well I suppose that's good news...
Ill try a different rom and see if that makes a difference
Thanks for your help ameer
Tironsteel said:
My keyboard backlight trigger stopped working so i have no backlight when the keyboard is opened.
I was hoping to write a script to toggle the backlight using a spare hardware key on the keyboard (368, that silly search/browser key below the enter key).
I have written 2 scripts to turn it on and off which were really simple (and work :victory but a toggle script looks a lot harder.
OFF
Code:
#!/system/bin/sh
echo "0">/sys/class/leds/keyboard-backlight/brightness
ON
Code:
#!/system/bin/sh
echo "255">/sys/class/leds/keyboard-backlight/brightness
Can anyone help me with this, i suspect it would be pretty simple for someone familiar with scripts.
DId i mention i know nothing about writing scripts...
Click to expand...
Click to collapse
Hi,
How can I execute that script with the hardware key (search/browser)?
Thanks in advance
Any news about that ?
Yyyeeeah...
I wish there was more news, but I guess not...
How hard could it really be (for you awesome people who know how to do everything)?
I mean, I run the same (almost) ROM on both my xmp and xp, yet on xp there's no HW-keyboard backlight when clearly on xmp it's no problem.
I know the phone is outdated now to say the least, but seeing as how there's such a dedicated group of users who prefer to have a hardware keyboard, shouldn't there be at least one programmer willing to put a few hrs in?
Please, please, pretty please, please with ice cream and cherries ontop-- uuuh AND WHIPPED CREAM TOO! yum... -what was I talking about...?
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 !!
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!