Related
This is a feature request.
If I use Spotify or Poweramp, after 10-15 mintues of it playing with the screen off, it will be greenified (even though it is running in the foreground). To get round this I have setup a tasker profile that opens greenify and manually disables autohibernation via run shell (input tap x y) whenever I play music. I am using a S4, GE rom, rooted, Xposed, Greenify boost mode.
I was wondering if it would be possible to have an additional tasker plugin that would enable/disable greenify's autohibernation? Even if the bug above is fixed at some point for my setup, I think it would be a useful feature to have.
Thanks to the developer for such an awesome app!
I have an application closely associated with the system navigation bar. It is very important for me to know whether it is hidden or displayed.
The following code says it can tell whether immersive mode is enabled/off, which hides the navigation bar.
Code:
View decorView = getWindow().getDecorView();
decorView.setOnSystemUiVisibilityChangeListener(new View.OnSystemUiVisibilityChangeListener() {
@Override
public void onSystemUiVisibilityChange(int visibility) {
if ((visibility & View.SYSTEM_UI_FLAG_HIDE_NAVIGATION) == 0) {
Log.d("NavBar", String.valueOf("visible"));
} else {
Log.d("NavBar", String.valueOf("not visible"));
}
}
});
But he can not say if I gestured up from the bottom of the screen to the navigation bar, and after a while she disappeared again.
How do I make it so that I can track the visibility state?
Is there really no solution?
As far as I understand the docs ( https://developer.android.com/reference/android/view/View.html#SYSTEM_UI_FLAG_HIDE_NAVIGATION ), they say that the SYSTEM_UI_FLAG_HIDE_NAVIGATION flag will be cleared as soon as the navigation bar reappears in immersive mode. (Means the "immersive mode" is "closed".) As far as I can see, your approach is ok for immersive mode but not for sticky mode:
Please read carefully the difference between immersive mode (SYSTEM_UI_FLAG_IMMERSIVE) and sticky mode (SYSTEM_UI_FLAG_IMMERSIVE_STICKY). To get full control over the appearance of the navigation bar, you need to use SYSTEM_UI_FLAG_IMMERSIVE and not SYSTEM_UI_FLAG_IMMERSIVE_STICKY. In immersive mode (SYSTEM_UI_FLAG_IMMERSIVE), you have to take care yourself that the navigation bar disappears again after some user interaction (usually running an async task that reenters immersive mode after xxx milliseconds of time). If the behavior is - like you describe it - that the navigation bar disappears again by itself, this indicates that you are using SYSTEM_UI_FLAG_IMMERSIVE_STICKY. In sticky mode, the docs say that flags are not changed at all because in this mode the short appearance of the nagivation bar is not considered a view change.
There are very good examples how this is done on the android dev pages. Read carefully: https://developer.android.com/training/system-ui/immersive.html
Yes, I understand what you are writing about, but in fact it's a little different. I do not put SYSTEM_UI_FLAG in my application, but any other program and even the system. In these all programs the developer can establish how he wants, and I need to know this in order to correctly implement my application.
o you understand what my program is about - here's the video. But there's another problem on video. Just a video so you can see what the application is about.
https://photos.app.goo.gl/riaFIDumxyV2cTWx1
Now I instead of decorView substituted View, on which I draw HUD. Now I can track when the navigation bar enters and exits this mode. And I can not handle the appearance after the gesture and reverse immersion.
Bascially, you listen to the change with your listener (your code snippet). To reenter immersive mode again, run an async task that is launched after the user's interaction (e.g. responding to a touch-event) and that re-enables immersive mode after xxx milliseconds.
I do the same. For this, I have a data stream from getevent. I process touch from the navigation bar (in particular also from the bar status, because there are different immersion modes and gesture on the status bar also returns the navigation bar) as a gesture that returns the bar. The gesture must be completed within 1 second, then it returns. In general, I use getevent to process touches from the navigation bar. The system does not intercept the pressing of the navigation bar.
Therefore, you need to use the low-level command getevent, root and busybox.
https://photos.app.goo.gl/ywu6T2XopaHxlAnx1 - video
hello everybody,
I have a kenzo (Redmi Note 3) with RR Final Build (7.1.2) installed.
For me, OK Google Detection is not working while Screen off and charging .. So
I am trying to make it work with tasker, AutoVoice and secure Settings..
what I wanna do is
1. Turn on AutoVoice continues while the screen off + while device Orientation is face up (So that battery consumption may be a bit low when compared to AutoVoice continues always on). when we holding the mobile we can turn it on by ourselves right?
2. wake the device up and unlock it when I say a wake up phrase, as autovoice continues is already turned on..
( I wanna use secure settings to wake up and unlock)
3. After waking up the device Autovoice continues should turn off
4. After that I wanted to launch google assistant but I dont know how we can achieve that (with a intent or something?)
5. So for now as the device woke up I can say ok google to launch google assistant.
(Yes, I need to say my hot phrase to wake the device and ok google to launch google assistant)
=======================================
so I have done like this,
profile 1. Created profile > event with Display off + orientation face up (State) > in task turn on Autovoice continues & Secure settings > Pattern Lock > Enable (I will desable this while the screen
profile 2. Display On event > Turn off Autovoice continues
profile 3. Autovoice recognized + display state (off) > set hot phrase >
in task > secure settings > wake device (screen & keyboard)
secure settings > Pattern lock > Disable
=====================
when screen is turned off, autovoice continues is turning on but not recognizing my hot phrase..
sometimes I can hear the recognized sound (which google make a little sound when a voice command recognized). but its not turning on the screen and unlocking my device.
what am I doing wrong? please let me know..
all Profiles are attached. please check them and help me to get google Assistant
sorry for being so lengthy
I have posted this in AutoVoice forum also, Waiting for @joaomgcd to reply
anyone?
Hi there! what Android version do you use?
joaomgcd said:
Hi there! what Android version do you use?
Click to expand...
Click to collapse
Android 7.1.2 (Resurrection Remix Final)
Thanks!
Can you please export your profile's description (not xml) so I can take a look? Long-click the profile in Tasker->export description Thanks in advance
joaomgcd said:
Thanks!
Can you please export your profile's description (not xml) so I can take a look? Long-click the profile in Tasker->export description Thanks in advance
Click to expand...
Click to collapse
Sure here it is...
Display off - avc on
Profile: Display Off -avc On (39)
Event: Display Off
State: Orientation [ Is:Face Up ]
Enter: Always Ok Google (38)
A1: AutoVoice Continuous [ Configuration:
Starting continuous voice recognition without headset
Persistent Notification: true Timeout (Seconds):0 ]
A2: Say [ Text:Auto voice activated Engine:Voice:default:default Stream:3 Pitch:5 Speed:5 Respect Audio Focusn Networkff Continue Task Immediatelyff ]
A3: Secure Settings [ Configurationattern Lock Enabled Timeout (Seconds):0 ]
========================
Display on - avc off
Profile: Display On -avc Off (40)
Event: Display On
Enter: Close Ook Google (41)
A1: AutoVoice Continuous [ Configuration:
Stopping continuous voice recognition Timeout (Seconds):0 ]
A2: Say [ Text:Auto voice turned off Engine:Voice:default:default Stream:3 Pitch:5 Speed:5 Respect Audio Focusn Networkff Continue Task Immediatelyff ]
========÷===============
Wake with autovoice
Profile: Wake With Autovoice (45)
Event: AutoVoice Recognized [ Configuration:Easy Commands: hello kiran,hey kiran,kiran
Responses: hi ]
State: Display State [ Isff ]
Enter: Continues (46)
A1: Secure Settings [ Configuration:Screen & Keyboard Lights On
5 Seconds Timeout (Seconds):0 ]
A2: Secure Settings [ Configurationattern Lock Disabled Timeout (Seconds):0 ]
A3: Flash [ Text:Kiran Longff ]
Edit : Say command is not also working
Can you please check the AutoVoice logs after you say the command with the screen off? Are the commands beeing correctly recognized?
joaomgcd said:
Can you please check the AutoVoice logs after you say the command with the screen off? Are the commands beeing correctly recognized?
Click to expand...
Click to collapse
I have checked the logs and its been recognizing correctly..
Screenshot attached..
Try using different actions in the task. Do those work?
joaomgcd said:
Try using different actions in the task. Do those work?
Click to expand...
Click to collapse
I tried to turn bluetooth on when I say my command while screen is off... But nothing is happening.. autovoice continues is turning on and toast is showing up (set by me). That's it.
But "possible commands received" text is showing correctly ...
I don't know what's wrong
Profile: Test (42)
Event: AutoVoice Recognized [ Configuration:Easy Commands: testing,test,hey google ]
Enter: Test (47)
A1: Say [ Text:Test passed Engine:Voice:com.google.android.tts:eng-usa Stream:3 Pitch:5 Speed:5 Respect Audio Focusn Networkff Continue Task Immediatelyff ]
This task is triggering with autovoice recognise widget , but not with autovoice continues turned on..
I think problem is with my autovoice continues..
Edit : first try after turning on autovoice continues is working but the rest is not working.. (not recognising)
Edit 2 : sometimes autovoice is being recognised , but task is not triggering
What if you create a notification instead? Does that work?
joaomgcd said:
What if you create a notification instead? Does that work?
Click to expand...
Click to collapse
same thing is happening... like I said, First attempt brought me a notification successfully, but If I try again nothing is happening...
with the widget its working fine...
Hi guys,
I cooked up some tasker mods to address some of the graciously few problems I have with the software of the mate 20x. I thought they might be useful to some of you guys so I figured I'd share. The plugins used are AutoInput, AutoLaunch, AutoNotifications, and AutoTools.
Mod List:
1. Fixed Auto-rotate Lock: uses the quick tile to auto-rotate or lock to any orientation
2. Swipe Recent Apps Switcher: cycle through previous apps by swiping on the bottom of the screen ala iPhone
3. Auto-disable Eye comfort: pop-up prompt when activating chosen apps that automatically disables eye comfort mode
4. Automatic Screen Filter: activates the free app Night Screen when brightness is set to minimum and disables it when brightness is raised
1. Fix Auto-rotate Lock
There are two versions of this mod, one which uses the system quick tile and one which uses an AutoNotifications quick tile. The AutoNotifications quick tile is more reliable and allows you to seamlessly lock orientation in landscape or inverted. The system quick tile is more clunky and you cannot lock in inverted, but it's a bit faster. If anyone knows where to find the system quick tile icons please tell!
Simply import the profiles to Tasker and turn them on. Choose "Rotate On" for the system qt or "AltRotate On" for the AutoNotifications qt.
2. Swipe Recent Apps Switcher
This mod will track all activated apps in an array so they can be systematically called back. It also offers swipe gestures at the bottom of the screen which can be used to cycle through them. Swipe left or right to go back and forth through your recent apps. After settling on an app, the app list will be updated to bring your active app to the front.
To install, import and turn on all profiles and run the swipe task. The Swipe task must be ran to provide gestures. The overlay providing gestures is at the very bottom of the screen, so just swipe your finger along the screen edge. Modify your settings and profiles to make sure that Swipe, AutoTools, and Tasker stay on with full permissions. This mod requires that tasker monitoring use accessibility. In the no root version some apps will refresh their state when activated (es explorer). This is because apps are 'launched' and not 'brought to foreground'. In the root version this is not an issue.
3. Auto-disable Eye comfort
This will provide a discrete pop-up in the corner of your screen when you activate the selected apps. I set up the profile with the apps I use for photo and video editing. When you click the pop up it will automatically open the drawer and disable the eye comfort quick tile. The pop up will go away in 5 seconds if not clicked, or can be swiped away.
To install, place the "bubble" folder in your AutoTools webscreen folder. The file paths should match up, but you may need to modify them. Import and turn on. The no root plugin uses AutoInput to press the fourth quick tile. If you have eye comfort on another quick tile you will need to change the touch coordinates. The root option will, if prompted, automatically switch eye comfort on and off as you switch between monitored apps. If you dismiss the prompt it will not ask again until eye comfort is toggled.
4. Automatic Screen Filter
When brightness is lowered to the minimum level, this mod will launch the app Night Screen to lower the brightness with a screen filter. When the brightness is raised above minimum it will turn night screen off.
You can change the app used, but it must have a toggle or on/off activity to be launched by secure settings. I found Night Screen to be the best for me. Import and turn on profiles.
There may be some bugs due to inconsistent Tasker monitoring and the system messing with things. Unfortunately there is little I can do about this.
ps. the zip is NOT installable
Sorry I'm stumped about how to embed youtube videos. Here's links.
https://youtu.be/KZBQJX3Fges
https://youtu.be/AnVLVCdWC8U
https://youtu.be/SsVjmW-9KwI
I vastly improved the app switcher to function much more intuitively and more like a native function. It's works pretty much exactly like on the iPhone, accept the animations are going the wrong way. I'll test it out a bit then update the post.
You sir are incredible
Post has been updated with a new app switcher, a root app switcher which fixes the launching problem, and a root eye comfort prompt which modifies the setting directly and has enhanced functionality. Also now none of the mods are dependent on the Secure Settings plugin
cobram3 said:
You sir are incredible
Click to expand...
Click to collapse
glad somebody likes it :good:
Allan can I pay you to help/tutor me on creating Tasker apps for my own use?
Please message me
---------- Post added at 02:14 AM ---------- Previous post was at 02:13 AM ----------
AllanRSS said:
glad somebody likes it :good:
Click to expand...
Click to collapse
Such as:
Auto speakerphone when call connects by default
When I get in the car, show a list of media players as a popup (bc bt connected)
$60 via PayPal thx
I really appreciate the offer, but thats not how xda works. This is where people help people, and I've benefited far too much through the days on the generosity of others to be greedy now.
I took a quick look and it and there is a State profile called "BT Connected". You should be able to check your bluetooth settings for the exact name of your car and insert that into the Name field. Then you would make a Scene containing buttons corrosponding to your desired media player. This should be reletively straightforward. When the BT is connected, show the scene with the buttons then launch your choice. This can be done with the AutoLaunch plugin or by android intent by running code 'am start --activity-reorder-to-front PACKAGE_NAME/MAIN_ACTIVITY'. The main activity intent is easily found through terminal if you're rooted but I dont remember how to find it if you're not rooted.
For the call I would use the State profile "Call". I am not sure if this will activate after the call is connected or while the phone is ringing for incoming calls. If its when the phone is ringing I would then set up a loop with "AutoInput Query" to check whether the call was connected. Run a couple tests with the query to see what the variable values are when the call is connected and check for those values to escape the loop. When the call is connected, use auto input to click on the speakerphone button automaticly. You can use the auto option to configure this or you can go into developer mode on your phone and enable show pointer location to get the coordinates. Coordinates are faster that text matching, but you might have to add a wait for 500ms to avoid it touching too early.
That should be it, pretty straightforward. You've inspired me to update this list with my new rotate toolbar and fixes. Happy tinkering!
That being said, I would be willing to do it for you if you would rather pay for a finished solution. However, I greatly encourage you to give it a go yourself, the possibilities are endless once you get comfortable with Tasker.
I haven‘t been here for a few days and I found there were some similar apps already. But I have finished my work and tested it for a week, So I create this thread
warning:
it seems that if you have installed the app and let it notified you at least once, then when you uninstall it, s10 system will delete the aod related settings(key and value) in the system settings database. but in system settings UI, the AOD related settings are still correct. So if you install this app again, this app can not get the correct AOD related settings. the result is that when there isn't notification this app can not restore the AOD related settings correctly.
To avoid this issue, Before you install this app again ,please go to system settings to set AOD mode and AOD tap mode again even if all the settings are correct.
[06/19]Release v0.9.9
- Now it works on OneUI 3 with Android 11
- Android dark mode supported
- After updating to this version, You must REBOOT your phone
[06/19]Release v0.9.3
- Add accessibility service, you can get it more intelligent by enable the accessibility service in system settings
- Fix bugs
[06/05]Release v0.9.2
- add a primary engine to check whether the notification should be notified when the screen is on (don't consume battery)
- add an application package name line to application selection page
- reduce memory consumption
- add debug switch to menu
the previous version (0.9.0) has supported screen off edge light (not fully supported, will never fixed, see the related source code comments)
[06/01]Release v0.9.0
- Now "AOD schedule mode" can also work well
- Add some tips to show why the main service item is not activated
- Add time schedule mode to save more power
- Add optional function that turning screen on when a notification comes
[05/30]Release v0.8.1
- add "select all" and "search" function for application management page
Auto AOD is developed for Samsung s10/s10+/s10e. Other phone may be OK too.
Feature:
- Automatically enable AOD while notification comes and restore AOD state while you unlock the phone or clear notifications in locked screen
- Airplane mode optimization support to save battery
- Applications managerment
- Battery saved
As the notification LED is absent on Samsung S10 and Samsung company may not update the software solution, I create this app to take advantage of the Samsung's AOD(Always On Display) feature to show me the new un-read notifications. Other than some apps before, it just enable the system's AOD when a new notification comes instead of drawing a circle or showing some info on a black screen. When you unlock your phone, the AOD state will be restored.
This app is desired to save more battery, so it has any permissions/traces and unnecessary functions.
[source code]https://github.com/photongh/Auto-AOD
[download]https://github.com/photongh/Auto-AOD/releases
Attachments:
View attachment AutoAOD_v0.9.3.apk
Hi....just tried it and can say that it does exactly what i wanted ...
Well done [emoji106]
SM-G975F Exynos
tried it but the app doesnt have option to select all the apps at a go.. lil bit tiring for selecting app individually.. hope u add it soon so that i can keep the app installed
rahulkheria said:
tried it but the app doesnt have option to select all the apps at a go.. lil bit tiring for selecting app individually.. hope u add it soon so that i can keep the app installed
Click to expand...
Click to collapse
I'm sorry for the "select all button" missing, it will be added in the next release
photonxda said:
I'm sorry for the "select all button" missing, it will be added in the next release
Click to expand...
Click to collapse
waiting for it ..
[05/30]Release v0.8.1
- add "select all" and "search" function for application management page
photonxda said:
I haven‘t been here for a few days and I found there were some similar apps already. But I have finished my work and tested it for a week, So I create this thread
[05/30]Release v0.8.1
- add "select all" and "search" function for application management page
Auto AOD is developed for Samsung s10/s10+/s10e. Other phone may be OK too.
Feature:
- Automatically enable AOD while notification comes and restore AOD state while you unlock the phone or clear notifications in locked screen
- Airplane mode optimization support to save battery
- Applications managerment
- Battery saved
As the notification LED is absent on Samsung S10 and Samsung company may not update the software solution, I create this app to take advantage of the Samsung's AOD(Always On Display) feature to show me the new un-read notifications. Other than some apps before, it just enable the system's AOD when a new notification comes instead of drawing a circle or showing some info on a black screen. When you unlock your phone, the AOD state will be restored.
This app is desired to save more battery, so it has any permissions/traces and unnecessary functions.
[source code]https://github.com/photongh/Auto-AOD
[download]https://github.com/photongh/Auto-AOD/releases
Click to expand...
Click to collapse
I had a look at your source code, and noticed one thing in your code. Here is the function in your code.
Code:
public static int getAodMode(Context context) {
int mode = Settings.System.getInt(context.getContentResolver(),
"aod_tap_to_show_mode", 1);
switch (mode) {
case 0:
return MODE_AOD_ALWAYS_ON;
case 1:
default:
return MODE_AOD_TAP_ON;
}
}
In switch case 0 your result is that AOD mode is Always On. Which is not entirely true. If you have a schedule set, AOD will be working on schedule.
The correct way to do it, is to check whether there is a schedule assigned to the AOD. You can check it by using the following code:
Code:
int schedule_start = android.provider.Settings.System.getInt(resolver, "aod_mode_start_time", 0);
int schedule_end = android.provider.Settings.System.getInt(resolver, "aod_mode_end_time", 0);
if the result is, that schedule_start value is not equal to schedule_end value it means, that in your case 0 - AOD is using the schedule Mode. If schedule_start value is equal to schedule_end value (both are 0) AOD is in "Always On Mode".
I think that you should update your code, otherwise if someone has AOD set to schedule, and the time is past the scheduled time, you won't see the notificatication
photonxda said:
[05/30]Release v0.8.1
- add "select all" and "search" function for application management page
Click to expand...
Click to collapse
thank u vry much for it
Can't able to switch on main service toggle.
saxena1 said:
Can't able to switch on main service toggle.
Click to expand...
Click to collapse
Try to enable permission to change system settings in AutoAOD apk settings....
View attachment 4768341
SM-G975F Exynos
wes58 said:
I had a look at your source code, and noticed one thing in your code. Here is the function in your code.
Code:
public static int getAodMode(Context context) {
int mode = Settings.System.getInt(context.getContentResolver(),
"aod_tap_to_show_mode", 1);
switch (mode) {
case 0:
return MODE_AOD_ALWAYS_ON;
case 1:
default:
return MODE_AOD_TAP_ON;
}
}
In switch case 0 your result is that AOD mode is Always On. Which is not entirely true. If you have a schedule set, AOD will be working on schedule.
The correct way to do it, is to check whether there is a schedule assigned to the AOD. You can check it by using the following code:
Code:
int schedule_start = android.provider.Settings.System.getInt(resolver, "aod_mode_start_time", 0);
int schedule_end = android.provider.Settings.System.getInt(resolver, "aod_mode_end_time", 0);
if the result is, that schedule_start value is not equal to schedule_end value it means, that in your case 0 - AOD is using the schedule Mode. If schedule_start value is equal to schedule_end value (both are 0) AOD is in "Always On Mode".
I think that you should update your code, otherwise if someone has AOD set to schedule, and the time is past the scheduled time, you won't see the notificatication
Click to expand...
Click to collapse
OK, thanks for your check, I'll fix it in next release
Xode said:
Try to enable permission to change system settings in AutoAOD apk settings....
View attachment 4768341
SM-G975F Exynos
Click to expand...
Click to collapse
Yes, to ensure the main service switch be activated, the following two steps must be done:
1. the "android.permission.WRITE_SETTINGS" permission must be enabled
2. AOD setting must be set to on
Do all permission & aod is enabled but toggle still not working.
saxena1 said:
Do all permission & aod is enabled but toggle still not working.
Click to expand...
Click to collapse
Uninstall this v0.8.1 and try installing the first release v0.8.0 to see what happens...
SM-G975F Exynos
Xode said:
Uninstall this v0.8.1 and try installing the first release v0.8.0 to see what happens...
Same problem with v0.8.0
Click to expand...
Click to collapse
saxena1 said:
Xode said:
Uninstall this v0.8.1 and try installing the first release v0.8.0 to see what happens...
Same problem with v0.8.0
Click to expand...
Click to collapse
please try to change AOD mode to "tap to show" and have a try
Click to expand...
Click to collapse
please try to change AOD mode to "tap to show" and have a try[/QUOTE]
Now it works please add instruction in OP.
THANKS
Hi, I have one request. What do you think about, I see AOD, after checking notification only on lock screen and turn off screen without dissmiss or read them, AOD turn back to always on. Maybe then can AOD turn back off since we already saw notifications and turn on after receive new one.
Thanks
Thank you for your work. An schedule option would be very important in my opinion because I like to use it in tap to show mode, so the default schedule wouldn't work.
I wish the app also had a setting to turn AOD off after a few seconds. This would make it possible for me to achieve "wake on notifications" function like my Nexus had. I only want the AOD to wake up for a few seconds whenever a notification comes in, turning off again after those seconds have passed.