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!
Related
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
Hi,
Just a little trick for those who want the "capacitive" buttons always on (maybe not very battery friendly but...) Remember someone asked this a few weeks ago somewhere...
Obviously you need root and init.d support... You can also edit directly the brightness file in /sys/class/leds/button-backlight/brightness but the modification will not survive after a reboot so you need to use an init.d script to load the modified value at each boot.
Put the init.d script below in /system/etc/init.d set the permissions to rwxrwxrwx, reboot, done
Here's the script: http://www.multiupload.nl/SMQWQQVBTJ
If you want to return back to stock: rename the init.d script with the .back extension or delete it.
If you want to set the "capacitive" buttons always off you need to edit the value, open the init.d script with notepad++ (on PC) or with a file explorer directly on your phone and set the value to "0" instead of "255", save, reboot, done.
Hoping that it will be useful,
Won't be using but thanks anyways, one question though, when do the HTC one buttons come on and off normally? They seem to have no specific interval
Sent from my HTC One using xda app-developers app
Hi,
No worries , it works with the ambiant light so with the sensor (light->off / night->on), even if the auto brightness is on or off the capacitive buttons vary in brightness so this part is independant...
After that I'm not a dev, the only solution I found is to modifie the value by the user in one file. Maybe it's set in the framework, or kernel? i don't realy know. The auto brightness values can be changed with a modified framework-res.apk, maybe it's the same thing for the capacitive buttons . In any case I have not the knowledge and skills for this part about the "automatic" dimming...
Capacitive button in Play works well and less cumbersome. Am using it with Pie. Automatic dimming would be cool though Thanks for looking into this.
Sent from my HTC One using Tapatalk 2
Stea1thmode said:
Capacitive button in Play works well and less cumbersome. Am using it with Pie. Automatic dimming would be cool though Thanks for looking into this.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Hi,
Sorry but I don't know what you mean... or you mean a kind of greater "light graduation", not on or off like stock, at least it looks like this for me (for example some values like 0 / 100 / 200 / 255), depending of the ambient light?
Like I said, for this I have not the knowledge, maybe a dev can take a look . In any case I don't think you will see a big difference between 100 and 255 for example...
And in the path /sys/class/leds/button-backlight/ there is nothing related to the graduation, it's in the framework stuff I think...
Stea1thmode said:
Capacitive button in Play works well and less cumbersome. Am using it with Pie. Automatic dimming would be cool though Thanks for looking into this.
Click to expand...
Click to collapse
This app now officially supports the HTC One in the latest beta version. I'm the developer of the app and I'd love to hear feedback from HTC One owners to know if it really works (since I don't have a device of my own to test on). See this thread: http://forum.xda-developers.com/showthread.php?t=2402153. Thanks!
denversc said:
This app now officially supports the HTC One in the latest beta version. I'm the developer of the app and I'd love to hear feedback from HTC One owners to know if it really works (since I don't have a device of my own to test on). See this thread: http://forum.xda-developers.com/showthread.php?t=2402153. Thanks!
Click to expand...
Click to collapse
Thanks I've just tested it. It has 3 settings right? Seems to be working well. It would be cool though to have an auto brightness feature.
Sent from my HTC One using Tapatalk 4 Beta
Stea1thmode said:
Thanks I've just tested it. It has 3 settings right? Seems to be working well. It would be cool though to have an auto brightness feature.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
That would be pretty cool.
Sent from my HTC One
Stea1thmode said:
Thanks I've just tested it. It has 3 settings right? Seems to be working well. It would be cool though to have an auto brightness feature.
Click to expand...
Click to collapse
Yep, it has 3 settings. Thanks for the idea about auto-brightness. You are definitely not the first person to pose that idea!
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...?
Please note the same information used to develop the app is in the guide for free... the app just makes it easier
You can find the app here
CALIBRATION REQUIRES ROOT... PLEASE GO GET ROOT ON YOUR PHONE AND THEN COME BACK.
Oh and BTW... I cannot be held responsible for anything that happens to your phone.... EVER!
use "adb shell" or a terminal emulator to get a terminal prompt and run the following commands
Step 1. - Save old calibration value (Optional)
Code:
su
mkdir /sdcard/S4data/
cat /efs/prox_cal >> /sdcard/S4data/prox_cal
Step 2. - Edit calibration value and update permissions
Grab the current value with everything clear of the proximity sensor.
Code:
cat /sys/devices/virtual/sensors/proximity_sensor/state
The value on mine was between 45 and 55. If you a lot higher then there might be something wrong with your phone. I used 150 for my value. You can use whatever you want but 150 is working great for me.
Convert your calibration value to hex (The windows calculator works great for this... use programmer mode). Put your calibration value in place of the 96 in the command below.
Code:
su
echo -en $'\x96' > /efs/prox_cal
chown system:system /efs/prox_cal
chmod 644 /efs/prox_cal
sync
Now reboot and your proximity sensor should be working.
Big thanks to greaty for his post here
Does this app remove dirt/lint from your proximity sensor?
Pp.
Sent from my Touchwiz device that never forgets gapps and everything works the way its supposed to.
I took my phone all the way apart and cleaned the sensor and it still had the issue. It seems that the sensor reads about 50 all the time and that is where they have the trip point set. This guide and the app just move that trip point.
Sent from my GT-I9505G using XDA Free mobile app
This saved my phone! Thank you!
Sent from my SGH-M919 using Xparent Red Tapatalk 2
Armandopjr said:
This saved my phone! Thank you!
Sent from my SGH-M919 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Glad it worked for you!
dagentooboy said:
I took my phone all the way apart and cleaned the sensor and it still had the issue. It seems that the sensor reads about 50 all the time and that is where they have the trip point set. This guide and the app just move that trip point.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
because you dont know how to clean... i had 46 all the time and now i have 11-12 for month or two and it is not increasing anymore because i shielded it with silicone/rubber and no more dust come inside - thats the only permanent way to fix this.
I dont think its for CM11 also
FYI, this file (/efs/prox_cal) does not exist in Google Edition S4.
fincan said:
FYI, this file (/efs/prox_cal) does not exist in Google Edition S4.
Click to expand...
Click to collapse
I believe it's only in TouchWiz roms.
Cleaning the dirt out of the sensor is the only long term solution to fix it. But even then it's not permanent. It will eventually get dirty again.
This guide solve my problem.
I noticed about the problem when flashed AOSP based Rom. So, thinked it was a rom bug.
Then, flashed stock again and find the issue was still there.
After trying whit compressed air, and nothing changes, rooted my phone (again) and follow this guide, and proximity sensor is working again.
Thanks.
it was driving me nuts! this worked and thanks so much!
djdivan said:
This guide solve my problem.
I noticed about the problem when flashed AOSP based Rom. So, thinked it was a rom bug.
Then, flashed stock again and find the issue was still there.
After trying whit compressed air, and nothing changes, rooted my phone (again) and follow this guide, and proximity sensor is working again.
Thanks.
Click to expand...
Click to collapse
I am glad it worked for you. I have heard that this is a huge issue for the S4. Not sure about other models.
Manual method worked perfectly fine. You SAVED my LIFE! Tons of thanks from the Philippines!
You're awesome! Been using this phone without a proper sensor for almost a year!
Skipjacks said:
I believe it's only in TouchWiz roms.
Cleaning the dirt out of the sensor is the only long term solution to fix it. But even then it's not permanent. It will eventually get dirty again.
Click to expand...
Click to collapse
I'm using an AOSP ROM (http://forum.xda-developers.com/showthread.php?t=2643031) and worked for me.
But the point of my post (and I have the Verizon edition BTW) is to say THANK YOU! I got to the point where every time I made a phone call I knew almost certainly my screen wouldn't turn on and even half the time hitting the home button wouldn't do the trick. I know the issue is my otter box defender series, which never caused this problem until about a month or two ago. But I need the otter box and this fixed my problem... Thank you thank you! No more random voice mails from me because my screen won't turn on haha
Edit: For those on AOSP, if you type the value in the calculator, swipe left and hit HEX, it will give you the hexadecimal value you need
Ever since I flashed any custom ROM on my tmo S4, the proximity sensor hasn't worked right. Screen would never wake after a call ended, even the app I use to keep the screen off in my pocket (Gravity Screen, pretty cool app) wasn't working. I used the little app referenced in the OP, and it all works again! Thanks! :good: :highfive: :victory:
fincan said:
FYI, this file (/efs/prox_cal) does not exist in Google Edition S4.
Click to expand...
Click to collapse
Previously I wrote that that file and value does not exist in S4 GPE (Google Play Edition), but just for the heck of it I gave it a shot and created the file, and what do you know, it works. Since you saved my sanity and also my phone from being smashed with a hammer, I purchased the app to show my support. Thank you dagentooboy.
Thank you so much you saved my life!!!!!
Thank you! i bought the app & in about 1-2 min it was fixed! im on 5.0.1 awesome!!
Wow, following this steps help solved my problems, Thank you~!!
Contrary to what OnePlus have said, the code for the Always on Ambient Display is in the first beta of Oxygen OS 11. All you have to do is enable the feature, which is disabled in the "OPFeatures" framework. This is very simple, and can be done in two lines in a root terminal (ie. do "su" first):
Code:
setprop sys.aod.debug_support_always_on 1
pkill systemui
After you have done this, the option to enable it will appear in Settings > Display > Ambient Display > Always on ambient display.
This doesn't survive a reboot, but you can have Magisk do it on boot for you. Only the first line is required for this (since SystemUI won't have started yet), simply drop the .sh file from the attached zip into /data/adb/service.d, set its permissions to rwxr-xr-x (chmod 755) and reboot. Please note that the zip is not flashable and cannot be used as a Magisk module. Something as simple and temporary as this (hopefully anyway, OnePlus have said this feature will come later) doesn't need a full blown Magisk module.
DanGLES3 said:
Do you mind if I make a Magisk module for this? Should be easier for users to install
Click to expand...
Click to collapse
You can, but Magisk isn't really built for modules to do tiny things like this. One liners are what service.d scripts are for.
Quinny899 said:
You can, but Magisk isn't really built for modules to do tiny things like this. One liners are what service.d scripts are for.
Click to expand...
Click to collapse
I'm aware of that, i just think users would be more comfortable installing a module than moving files, i just like making things easy for people ya know
About Service.d/Post-fs-data imo it would be cool if Magisk had a built in interface to manage/install scripts as Magisk is great for boot scripts but offers no straightforward method of installing/managing them other than making modules or manually moving files
DanGLES3 said:
I'm aware of that, i just think users would be more comfortable installing a module than moving files, i just like making things easy for people ya know
About Service.d/Post-fs-data imo it would be cool if Magisk had a built in interface to manage/install scripts as Magisk is great for boot scripts but offers no straightforward method of installing/managing them other than making modules or manually moving files
Click to expand...
Click to collapse
Agreed, maybe it'll come with the often-teased Xposed style injections one day
DanGLES3 said:
I'm aware of that, i just think users would be more comfortable installing a module than moving files, i just like making things easy for people ya know
About Service.d/Post-fs-data imo it would be cool if Magisk had a built in interface to manage/install scripts as Magisk is great for boot scripts but offers no straightforward method of installing/managing them other than making modules or manually moving files
Click to expand...
Click to collapse
Thank you!
Thank you guys for this.
Thank you very much for this.
Is there any shortcut for notification bar for fast on/off ?
And can I use Taskrer sehell command to Toggle AOD on/off (for example when "do not disturbe mode is on" or when I put phone to pocket). Something like options that existed in Exposed AOD Mod?
ontwykende said:
Thank you very much for this.
Is there any shortcut for notification bar for fast on/off ?
And can I use Taskrer sehell command to Toggle AOD on/off (for example when "do not disturbe mode is on" or when I put phone to pocket). Something like options that existed in Exposed AOD Mod?
Click to expand...
Click to collapse
It turns off automatically when it's in your pocket, but for DnD you probably would need to find the setting that controls it and toggle that
Is it a glitch or something but all I did was update my oneplus7t to is 11 and ambient on was already there I didn't need to use magisk
Is there no risk of burn in?
For some reason this doesn't work for me. It just restarts the SystemUI and the option still force closes when I go to it in the settings, just as before.
Nah mine works as intended I dunno honestly that's what I'm tryna figure out is magisk needed for certain versions of the 7t because I can go into settings and extra the only thing I noticed that does not function as should is the ambient light
DanGLES3 said:
I'm aware of that, i just think users would be more comfortable installing a module than moving files, i just like making things easy for people ya know
About Service.d/Post-fs-data imo it would be cool if Magisk had a built in interface to manage/install scripts as Magisk is great for boot scripts but offers no straightforward method of installing/managing them other than making modules or manually moving files
Click to expand...
Click to collapse
Thanks a bunch! Much much easier.
donjamal said:
Is there no risk of burn in?
Click to expand...
Click to collapse
No. It"s have burn in protection. This is bilt in AOD... This mod just bring hiden option in Settings (off, scheduled, all day) and it's work excellent.
MyDaugghterskeeper1429 said:
Nah mine works as intended I dunno honestly that's what I'm tryna figure out is magisk needed for certain versions of the 7t because I can go into settings and extra the only thing I noticed that does not function as should is the ambient light
Click to expand...
Click to collapse
I am on international version O2_BETA_01 and in my case I needed to unveil "when to show" option in display-ambient display, by using shell command /script from here.
I still didn't find out how to turn it on/off from tasker... only to use shell command from first post?
is there any other shell command just to turn AOD on/off and not to hide options from display/settings ?
ontwykende said:
I still didn't find out how to turn it on/off from tasker... only to use shell command from first post?
is there any other shell command just to turn AOD on/off and not to hide options from display/settings ?
Click to expand...
Click to collapse
Your right it does work excellent made a script from FKM to trigger both upon reboot. Thank
With FKM script manager you don't need to use a terminal you can run right from that app
lil_kujo said:
Your right it does work excellent made a script from FKM to trigger both upon reboot. Thank
With FKM script manager you don't need to use a terminal you can run right from that app
Click to expand...
Click to collapse
what I would like is to turn the AOD on or off with the shell command from Tasker ... For example, the AOD can only be ON when I have a new notification OR it can be completely Off when the "Do not disturb mode" is on (I already have task to turn Do not disturbe mode ih house (wifi zone) during night).
Thank you @Quinny899 for this work that allows us to have AOD.
After following the installation process, I have no problem.
AOD works very well.
I programmed it from 6:45am to 10:30pm and it disconnects when I switch to DND mode at night.
ontwykende said:
I am on international version O2_BETA_01 and in my case I needed to unveil "when to show" option in display-ambient display, by using shell command /script from here.
Click to expand...
Click to collapse
Ahhhh I see now I don't have that " when to show " option