Database Develop

keep active program?

Is there a program to keep my screen active when i am using a 3rd party GPS program? with TomTom it keeps staying active, but with for instance GPS Performance, it will go inactive after a while, and then my screen turns off..

Can't help you with that, my only idea is set the "screen turn off if not used for x min" to lots of minutes before entering app, and set it back after you exit the app

yeah, but that is a crappy way..

Unless I'm mistaken, MortScript is free. Install that and write a script to:
1. Change backlight setting.
2. Launch GPS Performance.
3. Change one of the hardware keys to execute the application's exit routine (if it's not simply hiting "X" in the corner - some aren't).
4. Reset the backlight settings.

[HELP] Launch app on security lock screen

How launch app when screen is off and security lock? (I want the radio to wake me up) I try: 1. Secure settings --> Configuration:Screen & Keyboard Light On (10sek) 2. Wait 1sek 3. Show Scene --> Name: Popup ,Display As: Activity 4. launch App: "(in my case is "eskaGO" This task try launch this app but can't launch to the end. When Task is end nothing happened. But when I manually unlock screen and see what app work in background I see this app. It's look like this task try launche app but can't launch it to the end.
I try too with AutoLunch but is this same.
Can anybody help??

Can you use Smartlock to prevent your device from locking at home?

lauralbaby said:
Can you use Smartlock to prevent your device from locking at home?
Click to expand...
Click to collapse
This not solves the problem. I don't need this only in home. I a lot travelling.
I try with secureTask plugin with off and on keyguard but this disable all securelock.

Well it sounds like the app just can't launch over the keyguard, so the task can't complete till the phone is unlocked. If you're comfortable with it, you can change the timeout (time it takes for the lock to be activated) to a really high number before you go to sleep, then after the app wakes you up, have it changed back to normal.

Thanks for solution but this not solve the problem. In Your idea every day before I go to sleep (when I activate alarm) I should count how many time screen should be unlock. I not everyday wake on this same time or it's time when I stay 1-2 weeks in this same place and wake up every day in this same time.
Every time when I set alarm I must count and set unlock screen Is not good idea.
Maybe somone else have Idea how to launch it?

gonzolex said:
Thanks for solution but this not solve the problem. In Your idea every day before I go to sleep (when I activate alarm) I should count how many time screen should be unlock. I not everyday wake on this same time or it's time when I stay 1-2 weeks in this same place and wake up every day in this same time.
Every time when I set alarm I must count and set unlock screen Is not good idea.
Maybe somone else have Idea how to launch it?
Click to expand...
Click to collapse
which counting are you talking about? I think he meant setting the grace time of lock screen to something like 7*24 hours, that way even if screen is off, you don't really engage the lock.
This could be a security drawback and might affect your Moto display/Samsung Always screen on function if you have them.

OK maybe I something wrong understand.
Maybe You can write how I should configure this task? It will be very helpful to me
Now in task profile I set time to start and end my alarm task.

alienyd said:
which counting are you talking about? I think he meant setting the grace time of lock screen to something like 7*24 hours, that way even if screen is off, you don't really engage the lock.
This could be a security drawback and might affect your Moto display/Samsung Always screen on function if you have them.
Click to expand...
Click to collapse
lauralbaby said:
Well it sounds like the app just can't launch over the keyguard, so the task can't complete till the phone is unlocked. If you're comfortable with it, you can change the timeout (time it takes for the lock to be activated) to a really high number before you go to sleep, then after the app wakes you up, have it changed back to normal.
Click to expand...
Click to collapse
Can You help me understand this and write how should look like this task?

gonzolex said:
OK maybe I something wrong understand.
Maybe You can write how I should configure this task? It will be very helpful to me
Now in task profile I set time to start and end my alarm task.
Click to expand...
Click to collapse
When the screen is turned off, it takes time to activate the keyguard/lock. Usually it's set to 1 second or less, so as soon as the display is off, the lockscreen is on. This can be changed (and in fact this is what Smart Lock does) so it won't activate as fast. Smart lock won't work in your conditions, so we can use Tasker plugins.
You need to get the plugin Secure Task if you are not rooted, Secure Settings if you are. Secure Task needs permissions granted in ADB, but the Help will explain the process.
Once you have it working, you can add the "secure settings" action for lockscreen timeout (see screenshots, it may be called something different on your device.)
There's a read action as well as write, you should read the initial value before changing it, save it, and restore it after the alarm goes off.
(In the Secure Settings plugin it's called Device Settings but other than that similar.)

Thanks for this
Now I undarstand that:
I have other profile where is task what will launch my app and where I set time to start this profile.
If I want that profile work - app launch correctly - I must before I go sleep launch other task (this what You wrote) what don't secure lock my screen.
Right? Did I understood correctly?

Yes, if you have a sleep profile, or if not, set it to activate at 2230 or whenever your bedtime is. The task will simply be Secure Task - secure settings - Read secure lockscreen_timeout (or whatever your device shows), so you can have a global variable of the typical timeout. Then Write secure lockscreen_timeout 99999999, as I posted in the screen shots.
And then have your wake up task activate at 7 or whenever, and then redo the lock timeout to the saved variable.

Ok,
But for example:
1. If I set this task to start 23:30 but since 23:10 i will not touch my phone this not work because screen still wil be secure lock ?
2. If I set this task to start earlier for ex. 21:00. On this time my phone is not protect if some one stole it and any one who get my phone will be have full access. Not always in this same time I will in the home.
Idea to solve my problem is good maybe someone else will need it.
For me is not good
It's not solve my problem
Maybe somone else have any idea how I can launch app when screen is secure lock

+ wifi condition
+ cell location

alienyd said:
+ wifi condition
+ cell location
Click to expand...
Click to collapse
yes, yes
+ anti theft application
I don't know what happened because to March everything working in my phone. In March I musted do factory reset and launch app in secure screen stoped working ;/
Earlier I use to tasker autoinput plugin and was working , now it write that autoinput can't unlock screen :|
So maybe something was changed/app had update and to launch app in secure screen now is other plugin

hmm that's weird. You must have done/changed something. I don't think any app, especially Tasker has changed anything since then.

alienyd said:
hmm that's weird. You must have done/changed something. I don't think any app, especially Tasker has changed anything since then.
Click to expand...
Click to collapse
I know that that is weird. But I don't know what happened because I done nothing special. Just made a task and profile and that was working. Earlier when I changed Rom and restore task everthing work good. Now stop working and I dont know why :|
Better... When this stop working I had try allone and try searching solution.
I made task like this:
1. Secure Settings - Configuration: Screen & Keyboard Light 10sek
2. Status Bar Set Expanded
3. Launch App: eskaGO
4. Wait 10 sek
5. Autoinput Action - Configuration Type: Text Value: Tasker
6. Autoinput Global Action - Configuration Action: Home
And this WORKED! it worked but every second time. Exactly the second time.
Because I thinked that is problem with my phone I made factory reset one more time and this it stopped working completely.
So I don't want belive that so powerful app like Tasker where is so much plugin and a lot of people who very good know this aplication that no one find solution for this.

Sorry I still don't understand your explanation...
If I have it right, you are trying to make an alarm clock out of the radio app.
Here is what I did to implement this idea:
trigger:
- display off
task:
launch app: notepad
alert: beep
result:
as soon as the screen turns off, I heard the beep. When I turned on the screen, I saw notepad app in the foreground.
requirement:
you will need to add something to trigger this during screen off. That extra condition should not turn on the screen. If it does, you should re-consider this whole condition.
The fact that notepad is running in foreground after unlocking means that the task was carried out as intended. If you can run the radio app, the playing should be turned on automatically the moment the app starts, or error you will have radio app running without actually doing anything.
if all these fail, please post a screenshot of your profile, task and log.
good luck!

How about using Appcloner for this? You clone the app and give it the capability to run on to of the lock screen. That's it. Good luck.

jdelcaribe said:
How about using Appcloner for this? You clone the app and give it the capability to run on to of the lock screen. That's it. Good luck.
Click to expand...
Click to collapse
I will try It
Can You tell me where in this app is this setting?

gonzolex said:
I will try It
Can You tell me where in this app is this setting?
Click to expand...
Click to collapse
Sure. Under display options, then choose " show app on lock screen".

Profile triggered by %time variable not firing

Phone is Pixel 3a running Android 10, Tasker is up-to-date.
I have a profile called PwrConnect that runs a task called Clock. The task simply launches my alarm clock app on the phone. The profile is primarily triggered when any power is connected to the phone but it has a secondary condition that specifies the time must be between 10:30pm and 6:00am.
When I plug my charger into the phone the profile is not triggered. If I remove the secondary condition (the time constraint) then the profile triggers when I plug in. But here's where it gets kind of strange. If I include the secondary condition (the time constraint) and I have the Tasker app open when I plug the charger in then the profile fires and runs the task which launches the clock app. Alternatively, I have also tried putting the time constraint in the task (%time > 2230) but that does not work either.
What am I doing wrong??? Or, is this a bug? Anyone else see anything like this?

Do you have "reliable alarms" enabled?
Have you tried a simple profile to just test the time context?

ktmom said:
Do you have "reliable alarms" enabled?
Have you tried a simple profile to just test the time context?
Click to expand...
Click to collapse
I'm not sure what "reliable alarms" is. Is that a setting in Tasker or Android?
Anyway, I have done some more testing. I added another step to the Clock task to simply flash a message when the task runs and I have found that the task (and therefore the profile) is indeed being executed as it should be - that is: when power is connected and the time is between 10:30pm and 6:00am. I can tell this because the message flashes on the screen when I connect power. BUT... the clock app only launches if I have the Tasker app open when I connect power. If the Tasker app is not open then I see the message flash but the clock app does not launch.

Reliable alarms is a tasker setting in preferences on the monitor tab. It helps tasker accurately execute time related activities.
What device and ROM are you on?
The following profile works fine for me with Tasker not in the foreground:
Code:
Time: From 11:44AM Till 3:44PM
State: Power [
Source:Any
]
Enter: Open App
A1: Launch App [
App:Clock
Data:
Exclude From Recent Apps: Off
Always Start New Copy: Off
]

ktmom said:
Reliable alarms is a tasker setting in preferences on the monitor tab. It helps tasker accurately execute time related activities.
What device and ROM are you on?
Click to expand...
Click to collapse
Device: Pixel 3a, ROM: stock Android 10 (not rooted)
I am fairly certain that the problem lies with the clock app that I am using. When I change the task so that it launches the stock, built-in clock app then everything works as it should. The clock app that I am trying to use (Kaloer Clock) is no longer in the PlayStore so has not been updated in a while. So, I suspect that there is something about it that Android 10 does not like. The app still functions fine and I can manually start it or Tasker will start it IF Tasker is running in the foreground. In fact this app has a setting that should start it automatically when power is plugged in but that stopped working about the time that I upgraded to Android 10, which is why I was trying to automate it with Tasker. I hate to give up on this app though because it is the only clock app I have found that allows me to tap anywhere on the screen to snooze the alarm (or long-press to cancel it). Everything else I have tried makes you tap an on-screen button which is difficult without my glasses.

Using AutoNotification (or any tasker notification listener plugin), a scene and intents, you can make the Google Clock have a full screen snooze/dismiss "button".
I slapped together an example that I put on Taskernet. It's full screen, a tap snoozes and long press dismisses.
To run it as is, you will need AutoNotification installed. The "ktm" after the profile/task/scene names can be removed. I do this to help prevent name collisions with anything already existing during import.

ktmom said:
Using AutoNotification (or any tasker notification listener plugin), a scene and intents, you can make the Google Clock have a full screen snooze/dismiss "button".
I slapped together an example that I put on Taskernet. It's full screen, a tap snoozes and long press dismisses.
To run it as is, you will need AutoNotification installed. The "ktm" after the profile/task/scene names can be removed. I do this to help prevent name collisions with anything already existing during import.
Click to expand...
Click to collapse
Ktmom,
I installed AutoNotification and imported your project. I am assuming that I need to delete either step 2 or 3 in the Stop Alarm ktm task. But, the scene does not appear unless I have Tasker running in the foreground when the alarm fires. Just wondered if you have test this in Android 10? Seems as though all my problems started after I upgraded.

dremelts said:
Ktmom,
I installed AutoNotification and imported your project. I am assuming that I need to delete either step 2 or 3 in the Stop Alarm ktm task. But, the scene does not appear unless I have Tasker running in the foreground when the alarm fires. Just wondered if you have test this in Android 10? Seems as though all my problems started after I upgraded.
Click to expand...
Click to collapse
The action that you're not using can be deleted or left paused.
And no, sorry, I'm always slow to update to major releases. But, there's something to try.
Edit the scene that your using, without changing anything else, tap the 3-dot menu. Select "properties" and change the "property type" to "activity". Save out of the scene.
Now edit the task -> show scene action that you are using and change "display as" to "activity".
Save out of the task, and Tasker, then test again.

Game mode profile

So I think just about every game on my oneplus 7 pro triggers a built in thing called gaming mode. Is it possible to create a profile that begins when that gaming mode starts and ends when that gaming mode ends. In this way I adjust things like volume levels and screen on time along with what the gaming mode does. And once for all of them instead of a profile for every game.

My guess is there is a custom setting that defines the status of the gaming mode. That's only a guess since I don't have a One plus.
You could use the native tasker settings -> custom setting action to see if you can identify what changes when the game mode turns on. Tapping the magnifying icon [emoji361] will bring up an assistant. Once you identify the setting, it can be used in a profile context (system -> custom setting).
From some online reading, I also think that the games that trigger game mode are entered in a list by a user. You could use an app context with each of those games selected so your profile activates whenever the game is in the foreground.
Hitting the gear/cog icon when the profile is selected will bring up settings for the profile. One of those settings is a toggle for restoring settings when the profile exits. In the case of an app trigger, when a different app is in the foreground, the settings made in your entry task will revert.

ktmom said:
My guess is there is a custom setting that defines the status of the gaming mode. That's only a guess since I don't have a One plus.
You could use the native tasker settings -> custom setting action to see if you can identify what changes when the game mode turns on. Tapping the magnifying icon [emoji361] will bring up an assistant. Once you identify the setting, it can be used in a profile context (system -> custom setting).
Click to expand...
Click to collapse
Upon starting a game that starts game mode the only thing that this method finds is a screen brightness change. when used from state. And nothing when used from event. Strange because if a game is triggering a system setting or something there should be something for tasker to see get triggered so a profile could tie into running while it is active. Much like a profile that would trigger upon phone charging for example and end when not plugged in to charge any more. Any other idea how i can identify what is triggered (for game mode on/off) to set a profile to run along with it?
ktmom said:
From some online reading, I also think that the games that trigger game mode are entered in a list by a user. You could use an app context with each of those games selected so your profile activates whenever the game is in the foreground.
Hitting the gear/cog icon when the profile is selected will bring up settings for the profile. One of those settings is a toggle for restoring settings when the profile exits. In the case of an app trigger, when a different app is in the foreground, the settings made in your entry task will revert.
Click to expand...
Click to collapse
Yes in game mode you add whatever games you want to trigger the mode. On my LG G4 I had a profile for each game but the profiles were problematic. Some of them would turn on and off while the game was still running. If I can have a profile that runs when game mode is active and ends when game mode is not then I would completely avoid having a new profile for every game.

I was suggesting using the custom setting action in a task to determine the setting. Then use that information in a profile to monitor it.
You can attempt to manually identify the custom setting (if that's what is controlling game mode). See here.
I'm thinking the mode reverts as soon as you leave the game to return to Tasker, so the built in assistant may not catch the change. Grabbing the settings via ADB and running a diff on the before and after may be the only way to go.
Otherwise, someone in the device forums might have insight how this mode is monitored.
As far as the app trigger approach, sometimes you can stabilize the task by putting a wait action at the start of an exit task and then stop the exit task of the calling profile is active (%PACTIVE).

Thanks for the reply with a method to identify the setting. Assuming that it is a setting. Using the custom setting action is a task when tapping on the icon it says to toggle the setting and return to tasker to find out what it is the results ended the same as attempting to use it by the other ways. It returned nothing or brightness found. I'll have to give the method in the link a try and see what happens. Will report back, might be a couple days.

I finally was able to identify the setting for making the profile, thanks much for the help.

Can Tasker create an icon to set the volume to a specific value...

...and to set the brightness to a specific value? I can do this easily in Windows, but not in Android.

Perhaps you figured it out by now, but just in case, the answer is definitely yes, I use that very functionality for brightness on my phone:
1. Create a new task
2. Add a "Display Brightness" action to this task (the value in this action doesn't represent percentage, so you might need to experiment with the number to get the desired brightness)
3. Add a "Tasker Shortcut" widget to your home screen. It will lead you to select the name of the task you created.
-It will also require you to select an icon for the widget, which you will do with the 9 squares at the bottom of the task edit screen (I already selected an Android robot icon in the picture).
-When adding the widget, you may also encounter an error message requiring you to open Tasker and exit with the back button to close it out properly in order for the widget to work.
There would be a similar process for volume, but you'd have to choose the appropriate action for which volume you want to adjust: ringer/system/media, etc.

Yes, I did figure it out, but thanks for posting that clear explanation, which is rare. It will probably help someone.
My most interesting program so far is a reliable way to turn the display off and on automatically to save battery power and, more importantly, to extend the lifetime of the power button.
Even with a reliable program, though, Tasker sometimes delays responding when it is closed and the display is off, so I've found that Tasker must be left running all the time. This is easy to arrange: in Android task viewing mode, click the lock icon at the top right of the screen view pane so that it becomes solid.
Such locks persist forever, I think, and are therefore quite confusing to newcomers to Adenoid, I mean Android.

You're welcome. Hopefully it might. I sympathize with the new user, since often it's difficult to get a solid, helpful answer from an advanced user regarding a beginner's topic.
As for Tasker being killed on occasion, unfortunately the circumstances surrounding that vary dramatically between devices. For example, whatever lock icon you're talking about to fix the issue on your device is not on my phone at all, so it would not work as a solution for me.
Do you have the option to "Use reliable alarms" in Tasker? I'm not sure if its presence varies between Android versions. I have that option set to "always"*, and I've never had a single time where Tasker fired late or was killed. It uses a persistent system alarm to keep tasker "in mind" all the time.
*And battery optimization for Tasker turned off, of course
david0001 said:
Yes, I did figure it out, but thanks for posting that clear explanation, which is rare. It will probably help someone.
My most interesting program so far is a reliable way to turn the display off and on automatically to save battery power and, more importantly, to extend the lifetime of the power button.
Even with a reliable program, though, Tasker sometimes delays responding when it is closed and the display is off, so I've found that Tasker must be left running all the time. This is easy to arrange: in Android task viewing mode, click the lock icon at the top right of the screen view pane so that it becomes solid.
Such locks persist forever, I think, and are therefore quite confusing to newcomers to Adenoid, I mean Android.
Click to expand...
Click to collapse

Enabling Use Reliable Alarms doesn't help. I think at this point I would say that getting Tasker to work when the display is locked is not obvious. Perhaps it is documented somewhere.
Basically, the bad symptom is as follows: after the display has been locked for a few minutes, moving the device fails to turn the display on again. Something kicks or locks Tasker out, but only after more than just a few seconds.
Sorry about not realizing that locking an app in memory is not part of Android. I'm using an inexpensive TCL A3 device sold by Tracfone. Locking is nice when you want to avoid startup delays for a task.