My idea of my script is
If Google assistant is on screen for more than 15 seconds with no user touches, reduce brightness to 20.
Then, if I touch the screen, restore its brightness
Use a plugin TouchTask, then set a countdown task restarted by screentouch. In the profile use both application and touch event to work the way u want.
Related
Hi!
Is there any way to disable vibration for ALL apps and notifications?
What I'm trying to achieve is to use an automagic-flow to disable vibrate when the phone is placed on a flat surface. I can detect the phone being placed on a flat surface in automagic, but there is no action to disable vibrate. However it's possible to run apps or shortcuts in automagic, so what I need is an app that is able to disable vibrate for all apps and notifactions. Tried a lot of volume profile tools, but no app seems to be able to override the vibrate-settings from e.g. the htc-mail-app.
I could disable vibrate in all the apps and use light flow to vibrate on an incoming notification, but unfortunately light flow can not create profile shortcuts so there's no way to toggle light flow settings with automagic.
Any ideas how to achieve that?
Greetings
MJFox
I've been messing around with this app obsessively for a few days as a possible replacement for the Gear wake-up gesture. The app seems to be great for two things...
1.) Screen turns off immediately as you start to lower your arm instead of the watch having to wait a minimum of 5-7 seconds
2.) Keep Screen ON by Motion option to prevent a screen timeout for as long as you are looking at it.
I've realized however that the "Turn screen on by motion" option uses more energy and is NOT a good replacement for the normal wake-up gesture found in gear settings. The normal wake-up gesture seems to be better optimized for the watch. No matter how many times i've tried to set up Gravity Screen to do the same thing, the angles don't work right and the screen comes on a lot when it shouldn't.
So i've combined the two...using the wake-up gesture of the gear (keeping the "screen on by motion" unchecked in Gravity screen) and utilizing the Screen Off feature and "Keep Screen ON by motion" feature of Gravity Screen. This has worked the best for me.
Here are the settings i use for everthing...
In the Gear settings:
-Set screen timeout to 7 seconds or whatever you prefer (not important if you keep Gravity Screen running all the time)
-Wake-up gesture set to "Last screen viewed".
(I simply turn off Wake-up gesture and pause Gravity Screen before going to bed... Still looking for a way to toggle these actions as a widget without having to go into settings everytime. Possibly tasker could do it? If anybody knows a way please tell me!)
In the Gravity Screen settings from top to bottom:
Pocket Sensor = 90 degrees
Table Sensor = 90 degrees
Keep Screen ON by Motion = checked
Sensitivity set = 100
Booster = checked
Running During Call = checked (your preference)
Notification = checked
Low Priority (hide icon) = checked
Start at boot = checked
(Everything else leave unchecked)
So that's it. Manually turning on/off the screen is always the best battery saver...but if you want to have the automatic wake-up then using either the app or the gear settings by themselves isn't as good on battery as combining the two as I have described. Let me know what you guys think.
Thanks for sharing your findings.
Function/ Purpose:
Skip to next track when the phone is shaken (specially for Google's standard music app, some 3rd party music apps already have this feature built-in)
Requirements:
• Tasker
• Phone with Proximity sensor
Tasker How to:
1. Create a Profile, Select Event, Select Sensor, Select Shake
If a warning about setting preference pops up, press OK2. Input the following in the options for shake:
Axis: Left-Right
Sensitivity: Very Low
Duration: Very Long3. New Task>Give some task name
4. Task>If %MTRACK Set
5. Media> Media Control>Cmd Next
Both simulate media button and label should be unchecked6. Task>End If
Go to Monitor tab in Tasker preferences and set Proximity Sensor as Yes
I mainly use this while driving/ commuting. One of the problems I had initially faced was this profile getting triggered every time I got a notification (email/ SMS/ ...) and my phone vibrated or if the road was bad and bumpy. I experimented with several combinations of Sensitivity and Duration in Step 2 above and these issues are eliminated now.
Want to control your phone remotely? Even if it's locked? Especially if it gets stolen, or just lost? I think this guide is the best way to do it, for now.
Requirements: Poweron schedule and power on alarm (in case of theft and to not notify a thief, i have alarm on silent)
edxposed and xposed edge pro (of which requires magisk and root, duh)
airmirror and airdroid
A lock screen set by pin, password, or even pattern.
Airmirror is used to control your device remotely; it can be used from the web or the app. Airdroid is to be installed and configured on the device you wish to control. I recommend you use systemize (magisk module) to systemize airdroid; it seems to make airdroid more responsive. As for configuring airdroid, please make sure you can actually control your phone first, and that you don't get the popup for screen casting (otherwise you cannot control phone remotely)
Configure the bootup trigger (in more triggers section) in xposed edge pro to turn on wifi/data, which is required to use airdroid/airmirror. Also, i would recommend you to set for the sms recieved trigger action to open airdroid.
Finally, with xposed edge pro, here comes the vital part to unlock your phone wirelessly.
First you must gesture recording; for now set it to record on a volume key. Lock the phone. Call the device. The call will always wake the device up, and as soon as that happens start the gesture recording. Dismiss the call, swipe and enter your code. End the gesture recording. Now go back to more triggers.
For the incoming call ringed trigger, select multi-action. First action is delay, set it to 2500ms. Second action is gesture inject, for the gesture you've just made.
Now, be sure your gesture actually works. Lock the screen and make a call to it. If your gesture succeeds, the call should be dismissed and the code entered. If not, just keep trying until you get it right. If you have the sms recieved trigger to open airdroid, send a text message to open airdroid. From this point on, open airmirror then control your device to do whatever.
airdroid seems to work as long as you have internet connectivity, and even though it has a data cap, using airdroid to control your screen uses very little data. Be sure to test multiple times, and after several reboots for maximum reliability.
If this guide actually gets attention, I will make it more clear, and more steps to be optimal.
A main disadvantage of the OP7P is the lack of AOD and Led. The ambient display is very short, so you never know if you missed call or message.
Some AOD Apps are heavy battery consumers, or disabling face recognition unlock, OPAODmod block chrome, Plus Beat is reasonable solution, though it is not AOD.
gigiion came up with the idea to trigger the Amolad AOD app to run only if notification was missed, using Macrodroid. Here is the way I implemented his idea, using Tasker:
1. Install Always on AMOLED from google play store. Do not enable the service. For OP7P choose One UI theme.
2. Screen condition
In Tasker, make these two profiles:
- Display off > Veriable set %Screen_Locked ~ 1
- Display Unlocked > Veriable set %Screen_Locked ~ 0
In such way the native ambient display will not interrupt the AOD whet it turn the screen on.
3. Main task
If %Screen_Locked ~ 1
Veriable set %Titel1 to %NTITLE
Veriable set %Text1 to %evtprm3
Wait 15 secondes
From Amolad plugin – start amolad display if %Screen_Locked ~ 1
End if
The variables %Title1 and %Text1, can be used to track the situation that the AOD start without any known trigger. Such phenomenon can happened if WhatsApp notify “Searching for messages”.
The 15 sec delay is for the native ambient display. The double condition of Screen_locked, disable AOD if you unlocked display in this period, of just answer a call.
4. Triggers
Make profiles of event/notification, missed call, state/power/power or whatever you like, and assign to the task you just made. Name those profiles – it is necessary for next stage.
5. Toggle profiles
Make “toggle aod profiles” task:
Profile Status missed_call set toggle
Profile Status aod set toggle
etc ……..
if % PENABLED ~ *,aod,* (“aod” is name of one of the trigger profiles)
setup quick setting (number: 1st, Name: toggle aod profiles, status: inactive)
else
setup quick setting (number: 1st, Name: toggle aod profiles, status: active)
end if
I do not understand way the active/inactive are replaced.
6. Assign quick setting button
In Tasker’s main screen upper right corner three dots: Preferences/ Action tab/ quick setting tab.
Then add it in the quick setting editor.
7. Automatic toggle triggers
Clone the task you made in section 5, and change “toggle” to “on” of “off”, then you can make any profile you like to toggle the triggers.
Seems like alot of work when you can just use this mod.
https://forum.xda-developers.com/on...ice-themes-apps--mods/oxygen-aod-mod-t4023587
hallo dare said:
Seems like alot of work when you can just use this mod.
https://forum.xda-developers.com/on...ice-themes-apps--mods/oxygen-aod-mod-t4023587
Click to expand...
Click to collapse
The main reason that I didn't use it, is the long remind interval (min 15 sec) and the short display time. You can miss notifications if you don't looking into the black screen all the time. Any case I found stable AOD to be better, otherwise i could use Plus beat.