[Guide] OnePlus 3 custom Tasker shell commands - OnePlus 3 Guides, News, & Discussion

*This requires root!*
So i was tweaking around with Tasker and I came across this tutorial online: http://www.notenoughtech.com/tasker/tasker-run-shell-commands
I decided to use the 3 commands he uses to make a list of shell commands that we can use. Basically this will allow you to change settings that are only found in Oxygen os and thus you can't normally change within Tasker. (I recommend you check out the page and try some things for yourself. There are more settings like these. The ones below are just the ones I thought would be most useful.)
Some examples of what you could use this for: A better power saving mode that disables all gestures and backlighting. Or automatically lock the hardware buttons when watching a show or movie, etc. This is not a guide for Tasker. If you don't know how Tasker works then I recommend you go watch some tutorials on YouTube. It definitely has a learning curve, but it is 100% worth it.
To add the shell script in Tasker:
create a task>'+' button>Code>Run Shell>enter the command line
Make sure you select the 'use root' checkbox, otherwise this will not work!
I've tested all of the commands below (on Oxygen os 4.0.3), however I'm not responsible for any damage that might occur to your phone.
Lock hw buttons
(You don't get the notification to re-enable the buttons. To do so you have to toggle the quick tile. Keep this in mind!)
On: settings put system oem_acc_key_lock_mode 4
Off: settings put system oem_acc_key_lock_mode 0
[Choose any percentage. If you go to battery settings and then tap 'Turn on automatically', it will set the value to 0. (So if you want to keep your settings, don't do this.)]
Auto enable battery saver at XX%: settings put global low_power_trigger_level XX
Capacitive button backlight
On: settings put system buttons_brightness 1
Off: settings put system buttons_brightness 0
Seconds in the clock
On: settings put secure clock_seconds 1
Off: settings put secure clock_seconds 0
Advanced reboot
On: settings put secure advanced_reboot 1
Off: settings put secure advanced_reboot 0
Double click power for camera
On: settings put secure
camera_double_tap_power_gesture_disabled 0
Off: settings put secure camera_double_tap_power_gesture_disabled 1
[For the button commands you can set it to multiple values (0-10). Below is a list of what the values mean. Replace the 'X' in the command line by the number of your choosing.]
0=No Action
1=Open/Close Menu
2=Recents
3=Search Assistant
4=Turn Off Screen
5=Open Camera
6=Voice Search
7=Open Last Used App
8=Open Shelf
9=Open/Close Notification Center
10=Open/Close Split Screen
Button Commands:
Long press home: settings put system key_home_long_press_action X
Double tap home: settings put system key_home_double_tap_action X
Long press Recents: settings put system key_app_switch_long_press_action X
Double tap Recents: settings put system key_app_switch_double_tap_action X
Long press back: settings put system key_back_long_press_action X
Double tap back: settings put system key_back_double_tap_action X
Screen on Gestures
Flip to mute
On: settings put system
oem_acc_sensor_rotate_silent 1
Off: settings put system
oem_acc_sensor_rotate_silent 0
3 Finger screenshot
On: settings put system
oem_acc_sensor_three_finger 1
Off: settings put system oem_acc_sensor_three_finger 0
[The screen off gestures work a little different. Every gesture has a certain number (written below). You have to add up the values of the gestures you want to have enabled. So everything enabled is 128+64+1+30=223 and nothing enabled is 0+0+0+0=0. Replace the 'XXX' in the command by the value you get.]
Double tap to wake=128
Open camera=64
Toggle flashlight=1
Music control=30
Screen off gesture: settings put system oem_acc_blackscreen_gestrue_enable XXX
I've tested these on Oxygen os 4.0.3. I'm not sure if they work on other versions/on the OnePlus 3t. I believe that the 'seconds in clock' and the 'lock hw buttons' weren't available before. So I doubt that those will work on marshmallow versions of Oxygen os (aside from maybe the marshmallow open beta). The others should be fine.

Related

Atomatically enable data when screen is off periodically (enormous battery save)

Hey, I've been tinkering for a few days with Tasker (begginer here) and I finally managed to do what I wanted when I installed it, that is turning WiFi or mobile data on for a few seconds every few minutes when the screen is off. I tested the battery drain with this task and after a full charge on my Huawei P9 lite, I managed to obtain 48 hours of battery life with 10 hours of usage.
Before anything else, this profile only works with Nougat. Marshmallow apparently doesn't allow apps to wake the device when it enters doze, even If I excluded Tasker and all the other apps I needed from doze. Nougat has a softer doze and it works great.
So, before you start, there are several requirements:
1. Tasker
2. Secure Settings plugin (for gps disabling and other stuff) - optionally
3. Taskkill (for killing processes when you turn the display off) - optionally
3. A rooted Nougat running phone
If you don't know how to root Nougat, there are several tutorials out there. Here's a small one for Huawei P9 Lite(mine runs on VNS-L21C432B370):
1. Revolution Recovery
2. Elite Kernel v5.1
3. PHH's Superuser
4. Adb and Fastboot drivers
5. Bootloader unlock code from huawei site (Tutorial)
6. USB drivers for your phone (just install HiSuite)
How to root Huawei P9 Lite Nougat:
- install adb and faastboot drivers
- use one of the methods to reboot to bootloader (i just reboot the phone with usb connected and hold volume down key)
- shift+right click where you have downloaded the recovery image, click "Open command window here" and type: fastboot oem unlock *insert bootloader unlock code here* and press enter
- after you unlocked your bootloader, from the same command window type: fastboot flash recovery revo_recovery.img
- reboot phone to recovery and install EliteKernel, after that wipe cache
- install PHH's Superuser from playstore and give Tasker, Secure Settings and Taskkill root permisions
Now for the Tasker profiles, small description:
Basically there are three profiles, one activates when the display is off, one after you unlock the display, and the third one does the magic. All the links are below.
Display Off profile with the Locked task does several things after you turn off the display:
- Sets variable LCD to 0 (you will se why in a minute)
- Sets Auto-Sync to off
- Turns off GPS (via Secure Settings plugin)
- several Taskkill actions (you can disable those if you want)
Display On profile with the WiFi On task does:
- Sets variable LCD to 1
- Turns on WiFi
- Waits 10 seconds
- If WiFi isn't connected turns of Mobile Data
- Turns on Auto-Sync
On-Off profile with Do task does the following every 2 minutes (change the value if you want or even set the hours between you want it active)
- If LCD~0 then
- Turn on WiFI
- Turn on Auto-Sync
- Waits 10 seconds
- If WiFi isn't connected then
- Turn on mobile data
- Wait 10 seconds
- Turn Wifi, Mobile Data and Auto-Sync off
Now go to Settings->Battery->Close apps after screen lock and allow Tasker, Secure Settings and maybe Superuser to run after you turn the screen off.
After that go to Settings->Apps press on the Settings icon on the bottom, go to Special Access->Ignore battery optimisation, press on the small arrow and select All apps, find Tasker, Secure Settinsg and maybe Superuser and allow them to stay active after doze.
You can customize the profile and add as many tasks as you like or play with the timers but I recommend not to alter the conditions for the profiles because some things won't work. This works 100%. Also, when I was researching, I found out you can monitor network usage and restrict the task from running if you have downloads in progress. I haven't implemented that, feel free to do the research and post the results.
And that's it. After this, enable all profiles and profit. Like I said, my average battery life is 48 hours and as long as nobody sends me important notifications that can't wait 2 minutes until I receive them, it's the best battery save trick I know.
Tasker profiles&tasks
Extract the archive and paste the files wherever. After that long press the Profiles and Tasks tabs in Tasker and import the XML files.
Let me know if it works for you.
Cheers.
Hey man, I'm going to tell you right now, this was a great post. The content was ok, but your style, your step by step instructions WITH reasons... remarkable.
Keep it up and you will be the tasker man, just based on your dedication.
Now if I may tweak your content?
Adding wait actions inside tasks is a battery destroyer and is bad taskering in general. Plus doing checks, waiting, checking etc... just hard to debug, hard to enjoy when you're leaving battery juice you could be saving.
Set a time context DO profile that runs every.... switch to variable . And the variable...name it something like %synccheck
Then on your screen off profile, set %synccheck to %TIMES+360 (the current time in secs, plus 5 min) this only runs on screen off.
Create a SCREEN ON profile, set %synccheck to %TIMES+120 (the current time in secs, plus 2 min) this only runs on screen on. SO 2 MIN IF SCREEN ON. 5 MIN IF SCREEN OFF.
(NOTE: I WOULDN'T put too much effort into checking whether on data or Wi-Fi. Under Wi-Fi settings, just disable "keep wifi on during sleep " and that lets the system handle disabling and reenabling when the screen comes on.
(Build a tasker task that enables Wi-Fi based on location and disables on it when you leave the Wi-Fi area...)
he current time is %synccheck. Since the current time can never be null, it will never run if the variable was cleared
Since in this example, it's set 5 min from now, the timing profile will run. The timing profile is the one that enables auto sync and whatever else you want to at a given time.
So there's no checking at all. If we clear the variable %synccheck then the profile never runs. The profile is only enabling auto sync and disabling on the exit task.
Hey, thanks for the reply. I am aware that my tasker knowledge is limited. I will take your tips into consideration and update my guide.
Cheers!

Changing Display Mode (Galaxy S8+ Adaptive/AMOLED Photo) when launching an app?

I have a Galaxy S8+. I use AMOLED Photo display mode, mostly because when I tweak a photo in Instagram, Snapseed,or Lightroom, I like it to be a fairly accurate representation on my phone's display, as the default Adaptive mode is oversaturated. But at other times, the Adaptive mode can look rather nice.
So what I'd like to do is when I launch something like Instagram or Snapseed, is to have Tasker switch the display mode to AMOLED Photo, and change back to Adaptive when I close the app.
It's a basic setting. Settings > Display > Display Mode > and you choose from one of 4 options with a radio button for each.
I tried using AutoInput, by using it to open display settings, then clicking display mode, then clicking AMOLED Photo. This is clunky, and slow, and the settings windows show on screen. And I then have to dismiss the settings window. Is there a way I can toggle that specific setting directly using some kind of plugin, without having to simulate all the key presses? Or have it change behind the scenes, not actually on screen?
Perhaps a shell command would work, if it has a specific system shell command? Is there a way to determine or interrogate if there is any kind of shell command?
Thanks!
the_scotsman said:
I have a Galaxy S8+. I use AMOLED Photo display mode, mostly because when I tweak a photo in Instagram, Snapseed,or Lightroom, I like it to be a fairly accurate representation on my phone's display, as the default Adaptive mode is oversaturated. But at other times, the Adaptive mode can look rather nice.
So what I'd like to do is when I launch something like Instagram or Snapseed, is to have Tasker switch the display mode to AMOLED Photo, and change back to Adaptive when I close the app.
It's a basic setting. Settings > Display > Display Mode > and you choose from one of 4 options with a radio button for each.
I tried using AutoInput, by using it to open display settings, then clicking display mode, then clicking AMOLED Photo. This is clunky, and slow, and the settings windows show on screen. And I then have to dismiss the settings window. Is there a way I can toggle that specific setting directly using some kind of plugin, without having to simulate all the key presses? Or have it change behind the scenes, not actually on screen?
Perhaps a shell command would work, if it has a specific system shell command? Is there a way to determine or interrogate if there is any kind of shell command?
Thanks!
Click to expand...
Click to collapse
I dont know about plugins, but you can check if there is a setting or intent regarding the display mode.
Run the following commands in terminal to see if there is a setting regarding display mode.
Code:
[B][COLOR="Blue"]# You can also write something like: settings list system > tasker.txt[/COLOR][/B]
settings list system
settings list global
settings list secure
[/HIDE]
You can change the settings which youve got from previous commands by using those commands:
Code:
[B][COLOR="Blue"]# Get the value/status of a setting[/COLOR][/B]
settings get global name_of_setting — returns status of setting (such as 1 = enabled, 0 = disabled)
[B][COLOR="Blue"]# Change the value/status of a setting[/COLOR][/B]
settings put global name_of_setting 0 — disables setting
settings put global name_of_setting 1 — enables setting
settings put system ...
settings put secure ...
[/HIDE]
You can also check if there is any intent for display mode in Settings.apk by using Manifest Viewer which shows the AndroidManifest.xml of every apk (where the intents are defined or something).
If there is a setting for display mode or if there is a intent, then its quite easy to set up a Tasker profile to achieve what you want.
You can also try to ask on Reddit ( /r/tasker ) since there are some people with good knowledge and /r/tasker is more popular than here on xda.
Thanks for your reply. You were on the right track. I had also asked on the Tasker Reddit.
But I need root to do what I want, and I'm not prepared to lose the warranty on my S8+ just yet.
Thanks anyway

[Guide][OOS][Root][Tasker] Disable visual annoyances during night

Hello guys, i'm no tasker expert, but i'll try to share my setup in order to turn off automatically notification (pulse) led, charging led and new notification wake up screen (under ambiant display) using tasker.
Requirements:
OOS (most custom roms have these things natively, and commands may differ from rom to rom)
Root
tasker
If you're new to tasker and need more step by step guide to create a task, there are plenty of tutorials and videos for that :good:.
First thing to understand is that there are multiple commands, you can choose to merge all the ones to disable lights into one task, and all the ones to enable lights back into another task, that's the easier way, but you can choose to make individual tasks that will be called one by one in another "main task", that's up to you, but the second choice will ask some extra work.
All the tasks will be created the same way, so i'll just help you with the first, then simply redo the things with the other commands.
Let's start with charging led, I named it LightsOff but you can name any task like you want.
Go to thet tasks tab, hit the "+" in the lower right, then name your task (LightsOff ?), then hit again the "+", type shell in the search field and select the "run shell", then, you'll need to type the different commands to be ran, one by line, so it meens after each command, hit "enter"
Once you're done, don't forget to tick the root checkbox.
For example, to turn the charging led Off you'll need the following commands:
Code:
settings put system battery_light_full_color 00
settings put system battery_light_medium_color 00
settings put system battery_light_low_color 00
There are other commands to turn it off, but for some reason, turn it back on will require a reboot, so to avoid that, i simply changed the colors to black, so it's not really turned off, but black (which is, for us, exactly the same).
You'll find all the commands at the end of the post, if you want to merge all commands (recommanded) into one task, go there and just add them to the task before saving it.
Save the task.
Now let's make the task that will get your charging led back to normal (or whatever suits you).
It's almost a copy and paste as the only changes are the name of the task (LightsOn ?) and the values for the colors.
Commands to type:
Code:
settings put system battery_light_full_color 16711936
settings put system battery_light_medium_color 16842752
settings put system battery_light_low_color 16842752
Save the task (root ticked obviously).
These are the default values, you can try other values if you like, that's what i've done, i like dimmed lights for charging, so mines are
Code:
settings put system battery_light_full_color 4096
settings put system battery_light_medium_color 8126464
settings put system battery_light_low_color 8126464
Before you ask, i could not find how find the correct number for a wanted color, i just tried many and wrote down ones i could keep, if you have an idea let's share it
So, now, here are the other commands that you can choose to merge to the first task or just create more tasks for each.
Wake up screen on new notification (you can find it under the ambiant display menu)
Warning: not same command as before, this setting is stored in the secure settings, not the system settings
Disable:
Code:
settings put secure notification_wake_enabled 0
Enable:
Code:
settings put secure notification_wake_enabled 1
And for the pulsing notification light.
Disable:
Code:
settings put system notification_light_pulse 0
Enable:
Code:
settings put system notification_light_pulse 1
You can merge all the commands in one single task for enable and another for disable if you want, that will be easier to setup.
Now all you have to do is create a new profile for night based on time of the day that will trigger the lights off.
Go to profiles tab, hit the "+" then "time" and choose the hours that suits you.
then select the task you want to run (the one that will turn off everything), after that, long click on the selected tak and select "add exit task"
then select the task that will turn all back on.
If you merged all the commands you're done, if not, you'll need to crete two tasks that will group the different tasks you want, i don't thinks it's worth the extra work but for knowledge purpose here's what you have to do.
Go to Tasks Tab, hit "+", give a name, hit "+" type "perform" in the search field and then select "perform task", hit the magnifying glass (the search icon, sorry english isn't my native language) then select the task you want, repeat this for each task you want to add to the "main" task.
Do the same for the "exiting" task.
This way is better as you can add extra tasks like going to airplane mode or mute sounds or whatever you want, but i i told before, it's much more work.
Hope this will help some stock (or xXx :good users, if you have questions, i'll try to answer, but as i said earlier, i'm really no expert with tasker, but if i could manage to do it, you too !
Have a nice day XDA !

Themes / Apps / Mods [App] Fix of buggy proximity sensor - Locking screen from being pressed during phone call

Note: app compatible with any phone with 1080x2400 screen or lower. Probably higher too, try it. Also it's impossible to make such block when talking in messengers (more precisely, it's difficult). App won't work without gapps, rare case.
Instead of classic reliable optical sensor we have sucky ultrasonic one.
Sometimes it does not turn off the screen while phone call and something is pressed with ear or cheek up to dropping call.
Popular workaround is app "Call Proximity Sensor Fix" which automatically turns off the screen. Or you can press the power button immediately after the answer.
But IMHO this is inconvenient because if you need to look at something on the screen it will not turn on by itself which is so familiar.
My simple application makes screen insensitive to taps. And unlike analogs soft buttons and status bar are blocked too (but not gestures).
On screen will be translucent button that disables lock if you need to use the phone:
– Long tap on button - unlock (button will turn green)
– Short tap when unlocked - lock again
– Long tap when unlocked - remove button at all so as not to interfere with e.g. for entering text
When second call comes in screen will automatically unlock so you can easily answer or hang up. Then it blocks again.
When manually launching the application there will be a question whether to enable 4 seconds delay for an outgoing call. So you able to choose SIM card.
Made by powerful Tasker, the project was exported as standalone application via App Factory. Implemented via scenes with new full-screen blocking type.
Location of button adapted for default AOSP / Google Dialer. It can be misplaced for third-party dialers and / or interface scale. It's impossible to cover all possible variants. So if it really bothers you, install Tasker and project below. Then change coordinates of the buttons.
Installation
Follow manual carefully, otherwise nothing will work.
Application is safe and doesn't have internet access.
1. Download APK below this post
2. Install it via file manager and launch
3. Answer the question about delay, decision can be changed later by launching app again
4. Open Settings > Apps & Notifications > In-Call Screen Lock
5. In "Notifications" turn off them all completely, otherwise they will be annoy you
6. In "Permissions" enable everything: Contacts, Call List and Phone
7. MIUI: right there in application settings enable "Autostart"
8. MIUI: and in "Background" select "No restrictions"
9. Custom: Settings > Apps & Notifications > Advanced > Special app access > Battery optimization > All apps > In-Call Screen Lock > Don't optimize
10. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
11. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
12. Settings > [MIUI: Advanced settings] > Accessibility > In-Call Screen Lock > enable "Use In-Call Screen Lock"
If you using Tasker
1. Download ZIP archive below this post
2. Extract file from it to phone/Tasker/projects
3. Tap on "House" icon at the bottom > Import Project > In-Call_Screen_Lock
4. If you don't need a delay on an outgoing call: delete / disable action #3 ("Wait") from the "In-Call Lock Start" task
5. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > Tasker > Allow display over other apps
6. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > Tasker > Allow display over other apps
7. Settings > [MIUI: Advanced settings] > Accessibility > Tasker > enable "Use Tasker"
UPD: files updated, fixed small bug.
does this affect battery life
shakeelbirmani said:
does this affect battery life
Click to expand...
Click to collapse
No.
Tested now on my RN10-pro... works just fine! Thank you!
Tested without gapps and it didn't work. I use the standard phone app from Arrow OS. I do all settings from your instruction.
There was no 4 seconds query of the sim card. The and no lock screen button.
Social_Work said:
Tested without gapps and it didn't work.
Click to expand...
Click to collapse
Unfortunately, APK's exported by Tasker always have dependencies from GMS no matter actions it should perform. Sorry, I can't fix that.
I reinstal Arrow with Gapps and Install tasker. IT works great! Thx a lot! Now ist this Phone uesable.
Great application. Tested it via Tasker and works. Thank you so much!
Small question, if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again. How do I get the button back then?
Note: sensors are automatically calibrated and sometimes this creates a problem.
To cleanup and recalibrate the sensors, all you need to do is this:
Bash:
# dd if=/dev/block/by-name/persistbak of=/dev/block/by-name/persist conv=notrunc
For me that solved everything on official MIUI V13.0.12.0 (and previously on V12.5.9.0).
Amazfit User said:
if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again
Click to expand...
Click to collapse
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
Zibri said:
sensors are automatically calibrated and sometimes this creates a problem
Click to expand...
Click to collapse
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
Thanks for the information. Tested it and ticking the block overlay + fixes the issue. I guess it's because even though I'm able to tap the icon and other call icons the phone is still locked. I guess the overlay + makes sure that the lock off scene is still visible on the "lock" screen. I'm on Samsung One UI 4.1 with the native Google dialer.
Thanks for the help.
Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
ultrasonic sensor can be even manually calibrated and the calibration is indeed stored and used.
Also: the ultrasonic sensor works in software, relying also on the position and angle of the phone.
If that measurement fails or is inaccurate, everything is ruined.
Trust me: try to do a fastboot flash of V13.0.12.0 then reset that partition as I said.
Then you can tell me if it improves or not.
For me now it works perfect both in DUO both in the stock dialer and messenger.
You can find the latest stock firmwares here:
Codes and study of the Redmi Note 10 PRO (SWEET) and some findings
code name 76937 com.miui.powerkeeper.cloudcontrol.CloudUpdateReceiver 8437625 com.miui.powerkeeper.thermalconfig.ThermalConfigReceiver 37263 com.miui.powerkeeper.ui.framerate.FrameRateSecretCodeReceiver 2877...
forum.xda-developers.com

AOD off task when face down

Can somebody help me with a task to turn off aod when face down or in pocket on a samsung s21 FE?
Thanks!
Not bullet proof but you can give it a try...........
creat a new task > custom setting > system > aod_mode > value 0
create a new profile > find sensor or gesture > find face down
add the above task to the profile.
** you can reverse aod on I believe is using value 1
eeeemc said:
Not bullet proof but you can give it a try...........
creat a new task > custom setting > system > aod_mode > value 0
create a new profile > find sensor or gesture > find face down
add the above task to the profile.
** you can reverse aod on I believe is using value 1
Click to expand...
Click to collapse
Sadly it doesn't work.
But thanks
last resort ............
same as previous nmethod but change aod_mode to:
aod_tap_to_show_mode
use value 0
Actually I'm on Samsung A71 and using such methods
Mrawy said:
Sadly it doesn't work.
But thanks
Click to expand...
Click to collapse
eeeemc said:
last resort ............
same as previous nmethod but change aod_mode to:
aod_tap_to_show_mode
use value 0
Actually I'm on Samsung A71 and using such methods
Click to expand...
Click to collapse
It doen't work, maybe I need to give tasker some permissions trough adb?
Mrawy said:
It doen't work, maybe I need to give tasker some permissions trough adb?
Click to expand...
Click to collapse
I'm not sure if extra permission is required as not in my case.
May be try below experimental task if it works so that it proofs tasker custom settings is available on your device :
custom settings > system > blue_light_filter > value 1
This turn on Samsung's reading mode and if you manually hit play button from within tasker after you create this blue light test task , then you check from the dropdown tilt to see if the blue light icon is on or not.
if it is on , means custom setting is availble on your device without extra permission.
if this is the case , use custom setting to use the 'FIND' button step-by-step go to AOD on/off menu and set it. ( hope you know custom setting has 'FIND' function to manually choose the require action in your case is to find the AOD )
On Huawei P30 Pro, to disable AOD make task like a photos in attachment.
To use this task You Need use ADB DEBUGGING and Tasker Permissions app or adb command. Read more:
https://tasker.joaoapps.com/userguide/en/help/ah_secure_setting_grant.html
I toggle my AOD on my Samsung device. It's just as the first reply said.
custom setting > system > aod_mode > value 0 to turn it off, and 1 to turn it on.
To test the adb setting on your device, just create a simple task that toggles AOD. EG when you are connected to wifi, set it off, or somethign else you can use to easily test.
If that works (which it should), then it's the sensor part that has the issue.

Categories

Resources