Related
Hi everyone!
I'd like to have a new feature to my S7 Always on Display, kind of like Motorola did with their Ambient Display.
In particular I want to toggle the AOD on and off when the display is off by waving over the proximity sensor or double tap on the display.
And as an extra (nice to have but not absolutely necessary), it would be nice to turn AOD on when I grab my phone and I have notifications.
I've tried my best, but the AOD won't get to work when the display is off. So I hope here are some talented users who can do something like that (or even have it already done).
I appreciate every help from you guys.
If you're rooted I used tasker to do exactly this. I could export an apk file for you.
I have a few versions:
- wave hand over proximity and AOD turns on for 10 seconds, then back off
- AOD turns off when proximity covered (so it's not on in your pocket) and turns back on when proximity uncovered.
- wave hand over proximity and wake to lockscreen
- wave hand over proximity to unlock (requires longpress home to unlock option enabled)
Edit: Wow...i just realized this IS the tasker forum, sorry!
Run Shell [settings put system aod_mode 0] use root: on
That will turn AOD off, if it's currently displayed
To turn it on, you set to 1 but its a little more tricky... you have to toggle the screen on/off after setting aod_mode to 1....but that will make your screen flash on for a split second (which you dont want)....so.... create a full screen, black scene...show the scene before toggling screen on and destroy it after toggling screen off..... you'll never know...
Code:
Profile: Proximity AOD Off (595)
State: Proximity Sensor
State: Display State [ Is:eek:ff ]
Enter: AOD Off (621)
A1: Run Shell [ Command:settings put system aod_mode 0 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]
Exit: AOD On (622)
A1: Run Shell [ Command:settings put system aod_mode 1 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]
A2: If [ %SCREEN ~ off ]
A3: Show Scene [ Name:Blocking Display As:Activity, Full Display, No Bar Horizontal Position:100 Vertical Position:100 Animation:System Show Exit Button:eek:ff Show Over Keyguard:eek:n Continue Task Immediately:eek:n ]
A4: Run Shell [ Command:input keyevent 1015
input keyevent 6 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]
A5: Destroy Scene [ Name:Blocking ]
A6: End If
Sent from my SM-G955F using Tapatalk
RuggedHunter said:
- wave hand over proximity and AOD turns on for 10 seconds, then back off
- AOD turns off when proximity covered (so it's not on in your pocket) and turns back on when proximity uncovered.
Click to expand...
Click to collapse
Wow, that seems to be pretty complicated. Could you upload the xml file for the quotes things above for me? That would be great
ichbinich said:
Wow, that seems to be pretty complicated. Could you upload the xml file for the quotes things above for me? That would be great
Click to expand...
Click to collapse
Its really not all that complicated. Here ya go:
Air AOD
Proximity AOD Off
Blocking Scene
?
Of course, you don't want to use both of these at the same time.... they're sorta opposites. If you keep AOD Off normally and want it took appear for 10 seconds when you wave your hand, use AOD. If you keep AOD On normally and want it to turn off when in your pocket, etc...Then back on when out of pocket...use Proximity AOD Off.
Sent from my SM-G955F using Tapatalk
RuggedHunter said:
Its really not all that complicated. Here ya go
Click to expand...
Click to collapse
Thank you very much for sharing, I really appreciate that. But for some reason I cannot import those because they are invisible when I want to select them for importing. Any suggestions on that?
Make sure you've put the files in the proper folders.
/sdcard/Tasker/Profiles
/sdcard/Tasker/Scenes
Sent from my SM-G955F using Tapatalk
Thanks! It's working pretty well but is it the same with your device?
- After waving over the proximity sensor it takes about 5 seconds or so for AOD to show up
- Before AOD shows up, the light of softkeys as well as a SuperSU message are showing up for a short time
It takes a second or two, yes. If you're seeing soft keys and/or toasts, then the blocking scene probably needs to be tweaked for display size. Play around with it, you'll get it.
Sent from my SM-G955F using Tapatalk
RuggedHunter said:
It takes a second or two, yes. If you're seeing soft keys and/or toasts, then the blocking scene probably needs to be tweaked for display size. Play around with it, you'll get it.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
I set the scene up with my size (1080x1920) but I still get this:
1) less than 1 second the lockscreen (or homescreen, cannot say properly, it goes that fast)
2) SuperSU toast + softkey lights
3) black screen
4) than finally the AOD
that is awkward that it doesn't work properly on my device. Do you have any further ideas what I can check in order to get it working?
ichbinich said:
I set the scene up with my size (1080x1920) but I still get this:
1) less than 1 second the lockscreen (or homescreen, cannot say properly, it goes that fast)
2) SuperSU toast + softkey lights
3) black screen
4) than finally the AOD
that is awkward that it doesn't work properly on my device. Do you have any further ideas what I can check in order to get it working?
Click to expand...
Click to collapse
Hmmm.... I'm really not sure. Which profile are you using...Air AOD or Proximity AOD?
Are you saying that the display turns on and you see the whole lockscreen.... then it goes black except for the nav buttons and toast?
Sent from my SM-G955F using Tapatalk
RuggedHunter said:
Hmmm.... I'm really not sure. Which profile are you using...Air AOD or Proximity AOD?
Are you saying that the display turns on and you see the whole lockscreen.... then it goes black except for the nav buttons and toast?
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
I'm using the Air AOD. Please look at the attached video (the softkey lights starting at the moment when the lockscreen is on).
ichbinich said:
I'm using the Air AOD. Please look at the attached video (the softkey lights starting at the moment when the lockscreen is on).
Click to expand...
Click to collapse
I see...The purpose of the blocking screen is to prevent that from happening. I think if you turn that Wait action on in A4 it might work for you.
However I see that the profile I linked is an old version that I must have uploaded a while ago...it doesn't match the description that I posted above. It shouldn't be the reason you're having problems, but I recommend deleting that profile from Tasker and from /sdcard/Tasker/ then import this one. Sorry about that.
https://www.dropbox.com/s/3zpgje43mhijxh6/Air_AOD.prf.xml?dl=0
I anticipate you'll have the exact same issue. If so, if you insert a Wait Acton between A2 and A3 for 1 sec or so, I think it'll work.
Sent from my SM-G955F using Tapatalk
Unfortunately that didn't change anything.
ichbinich said:
Unfortunately that didn't change anything.
Click to expand...
Click to collapse
Huh, I'm out of ideas unfortunately. Sorry it's not working for ya. It works well on my s8+
Sent from my SM-G955F using Tapatalk
Hello, @RuggedHunter
I'm sorry for bumping a 6+ months old topic but I think you can help me out with my problem. Here goes:
AOD is set to be 'Always' on from its settings.
I am using the second option from this tutorial: https://www.xda-developers.com/automatically-toggle-samsungs-always-on-display-when-charging-app which toggles the AOD option to on when the device is lying on a table for example with the screen facing upwards and toggles it off if this condition is not met. Now this works perfectly, but my problem is as follows.
If the screen is turned off, the new AOD setting won't take effect unless I turn the screen back on and turn it off again. So, for example, if my phone's in my hand and AOD is off with the screen off, when I leave it on the table facing up AOD won't show up, despite the proper condition being met. Now I tried the SecureSettings plugin way to wake up my screen for 1 sec but that didn't work at all for some reason. Could you help me out with this thing, please? I saw that you've made some black overlay and turn on the screen then apply this blocking overlay until it turns back off, but I'm no expert with Tasker so it was a bit confusing. Would you explain to me what to do in Tasker (step-by-step if possible, I know the basics things like how to make profile, task, etc btw) in order to make that AOD switch profile work perfect (aka to set aod_mode, turn on screen, show black blocking overlay while it's on, turn, screen back off, destroy overlay when screen turns off)?
Sorry for such a long post, I'm using a ported S8 ROM on my Galaxy S5 called Nemesis Reborn V4 but the "aod_mode" stuff works so anything S8 should.
@koragg97 yeah I had the same problem and worked around it like this... Here's my AOD ON task. The blocking scene is just a full display overlay blocking that is all black #FFFFFF and the keyevents toggle the dismay on/off quickly... they can both be 6 if you want.
AOD On (622)
A1: Run Shell [ Command:settings put system aod_mode 1 Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: ]
A2: If [ %SCREEN ~ off ]
A3: Show Scene [ Name:Blocking Display As:Activity, No Bar, No Status Horizontal Position:100 Vertical Position:100 Animation:System Show Exit Buttonff Show Over Keyguardn Continue Task Immediatelyn ]
A4: Run Shell [ Command:input keyevent 1015
input keyevent 6 Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: ]
A5: Destroy Scene [ Name:Blocking ]
A6: End If
Sent from my SM-G955F using Tapatalk
RuggedHunter said:
@koragg97 yeah I had the same problem and worked around it like this... Here's my AOD ON task. The blocking scene is just a full display overlay blocking that is all black #FFFFFF and the keyevents toggle the dismay on/off quickly... they can both be 6 if you want.
AOD On (622)
A1: Run Shell [ Command:settings put system aod_mode 1 Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: ]
A2: If [ %SCREEN ~ off ]
A3: Show Scene [ Name:Blocking Display As:Activity, No Bar, No Status Horizontal Position:100 Vertical Position:100 Animation:System Show Exit Buttonff Show Over Keyguardn Continue Task Immediatelyn ]
A4: Run Shell [ Command:input keyevent 1015
input keyevent 6 Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: ]
A5: Destroy Scene [ Name:Blocking ]
A6: End If
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
Had to change the keyevent apparently but it works nicely. I also made a check so that it works just when the phone is locked to prevent accidental screen turn off if I cover the proximity sensor when I'm just using the phone. Also added an InCall safeguard since phone is technically locked during a call and the power button simulation ends the call lol
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".
Hello all!
So I posted this in the Tasker reddit too so was looking to pick as many brains as possible as I'm running into road blocks and not getting the desired results
So I'm trying to extend the time DND is active on only Saturday and Sunday. 1st try failed..
https://i.imgur.com/7CIm3Hw.jpg
https://i.imgur.com/XZ047lz.jpg
https://i.imgur.com/Mt9zGI3.jpg
Not quite sure why it's not worked. Phone DND settings are limited at it disables at 7am daily. The weekend task was meant to place it into DND at 7:01 until later..
I later tweaked to have separate profiles per day..
So having tried the separate days it's taking the day over the timing.
https://i.imgur.com/O7zvMsX.jpg
So it's simply ignored the fact I wanted time to also go into the equation and set it to the day and nothing else matters!
Sent from my SM-N960F using Tapatalk
jr866gooner said:
Hello all!
So I posted this in the Tasker reddit too so was looking to pick as many brains as possible as I'm running into road blocks and not getting the desired results
So I'm trying to extend the time DND is active on only Saturday and Sunday. 1st try failed..
Not quite sure why it's not worked. Phone DND settings are limited at it disables at 7am daily. The weekend task was meant to place it into DND at 7:01 until later..
I later tweaked to have separate profiles per day..
So having tried the separate days it's taking the day over the timing.
So it's simply ignored the fact I wanted time to also go into the equation and set it to the day and nothing else matters!
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
It helps substantially more if you post the task or profile rather than use screenshots.
When setting DND settings in an entry task, you must proactively disable DND in an exit task. It will not revert settings automatically on exit. That was a change, specific to DND, introduced rather silently several tasker versions ago.
Why not use Android's built in DND automatic settings rules?
ktmom said:
It helps substantially more if you post the task or profile rather than use screenshots.
When setting DND settings in an entry task, you must proactively disable DND in an exit task. It will not revert settings automatically on exit. That was a change, specific to DND, introduced rather silently several tasker versions ago.
Why not use Android's built in DND automatic settings rules?
Click to expand...
Click to collapse
Thanks! How do I add an exit task please?
The default Samsung DND settings dont specify a separate weekend time setting.
Sent from my SM-N960F using Tapatalk
Long press on the entry task on the profile tab, then a context menu will pop-up. The entry task has a green, right facing arrow. An exit task will have a red, left facing arrow.
ktmom said:
Long press on the entry task on the profile tab, then a context menu will pop-up. The entry task has a green, right facing arrow. An exit task will have a red, left facing arrow.
Click to expand...
Click to collapse
Thanks! I'll have a play.
For clarity this is one of the problematic profiles.
Profile: DND sat (14)
Time: From 07:02 Till 08:10
Day: Sat
Enter: DND On (8)
A1: Do Not Disturb [ Moderiority ]
Hope this makes it a little clearer. Apologies it's my first time in the forum for tasker at XDA!
Sent from my SM-N960F using Tapatalk
My apologies I failed to mention that this now works and is set as follows!
Profile: DND sat (14)
Time: From 07:02 Till 08:10
Day: Sat
Enter: DND On (8)
A1: Do Not Disturb [ Moderiority ]
Same setup for sunday too so I am very pleased indeed and thanks to anyone that had patience and found time to read my post.
Sent from my SM-N960F using Tapatalk
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.
Hi,
I have set up the display timeout option with the settings below but it doesn't seem to work. I am using an oppo phone on Android 12.
Create a new task. Select the “+” button. Select “Display” followed by “Display timeout” Select the time span you want to set and then save. Now select “Profile” and click “+” and then “Applications” Mark the applications for which you want to activate this Tasker profile.
Then I open the app but after 15 seconds the screen turns off which is the default device screen timeout.
Is there no way to override this? Maybe get tasker to somehow keep interacting with the screen to keep it on?
I've tried this on a few apps and have got two different messages..
One says screen will stay on for 15 seconds which is the system screen time out.
Other says tasker will keep screen on but still times out after 15 seconds.
Really want this to work as some apps like games I don't want timing out after 15 seconds and I don't want to increase the system time to couple of mins for every app.
Hi,
I have the same problem on my OPPO A74 with Android 11 ((ColorOS Version V11.1). It seems impossible to create a task to change the screen time out; not in connection with a profile, shortcut or widget. The amazing thing, though - when you test the task in Tasker it works perfectly fine.
Media Volume, I think, also doesn't work. Other app connected profiles like autorotate or display brightness work well. I wanted to test more but I can't find the time.
I really miss the screen timeout though. It drains the battery too much to set it constantly to 15 minutes or so, but for some apps less simply is annoying.
The developer created some apk to help with some OPPO related problems, unfortunately, it didn't help with this one (sorry, I can't remember exactly what it was).
A kind of workaround: Once you've activated the Developer Options an your phone you can enable "Keep screen on while charging". When you need longer screen time, just plug into a charger.
But using a Tasker Profile would be much nicer.
Hope somebody knows a better trick.
Not sure if following could help your situation ( only for your gaming situation )
Create a new Profile, choose > apps > add your game apps in it. click left top arrow when finisning add gaming apps.
Tasker will pops-up task list > creat new task > Screen > Turn on.
** when above profile is complete , click the task when you are still in Profile list. Hold the task, it should pops-up with option exit task. Choose this as exit task.
Play around to see if this profile is working when gaming apps in foreground, screen never turn off.
EDIT: Try first not move the task as exit task. ( make the task as normal entry task )
eeeemc said:
Not sure if following could help your situation ( only for your gaming situation )
Create a new Profile, choose > apps > add your game apps in it. click left top arrow when finisning add gaming apps.
Tasker will pops-up task list > creat new task > Screen > Turn on.
** when above profile is complete , click the task when you are still in Profile list. Hold the task, it should pops-up with option exit task. Choose this as exit task.
Play around to see if this profile is working when gaming apps in foreground, screen never turn off.
Click to expand...
Click to collapse
Thanks for your reply.
Creating the profile is not the problem. It just seems that Tasker cannot change the system's setting. As mentioned, there is no problem when you create a profile allowing the screen to rotate using a speciffic app (and others as well ) I have no idea, why it does not work for the screen timeout.
Dreamcatcher0664 said:
Thanks for your reply.
Creating the profile is not the problem. It just seems that Tasker cannot change the system's setting. As mentioned, there is no problem when you create a profile allowing the screen to rotate using a speciffic app (and others as well ) I have no idea, why it does not work for the screen timeout.
Click to expand...
Click to collapse
I use no screen timeout, I use "screen turn on" in your situation as my op., enough I've not tried it on my Samsung A71.
eeeemc said:
I use no screen timeout, I use "screen turn on" in your situation as my op., enough I've not tried it on my Samsung A71.
Click to expand...
Click to collapse
"Display / turn on" works fine when I want the screen to turn on with a notification. But the screen turns dark after the system timeout has passed. I've also tried "Display / Stay On / with Wireless, AC or USB Power" and with the AutoInput Plugin "Screen Off Or On: Turn On / Timeout Never" but the screen always turns dark.
Those Profiles always worked on my other Smartphones (LG -D405, LG-K10 and Moto G6). I believe, it's the ColorOs that's causing the trouble.
Dreamcatcher0664 said:
"Display / turn on" works fine when I want the screen to turn on with a notification. But the screen turns dark after the system timeout has passed. I've also tried "Display / Stay On / with Wireless, AC or USB Power" and with the AutoInput Plugin "Screen Off Or On: Turn On / Timeout Never" but the screen always turns dark.
Those Profiles always worked on my other Smartphones (LG -D405, LG-K10 and Moto G6). I believe, it's the ColorOs that's causing the trouble.
Click to expand...
Click to collapse
below is a task ONLY FOR ROOTED DEVICE., no harm to try even if your's not root.
New task , run shell command , in the command input
there is a button 'use root' , check that button also.
settings put system screen_off_timeout 200000
** 200000 I'm not sure sure equals to how many second., just give it a try and if you get a longer screen on time from your issue it means it is working.
also, make another separate task, search for 'custom setting'. look up from there I thingk it is in system something about screen timeout.
EDIT: run shell command task suggest you run it manually., than see if it works. if not, restart device to check if it requires a restart in order to accept new timeout settings.
eeeemc said:
below is a task ONLY FOR ROOTED DEVICE., no harm to try even if your's not root.
New task , run shell command , in the command input
there is a button 'use root' , check that button also.
settings put system screen_off_timeout 200000
** 200000 I'm not sure sure equals to how many second., just give it a try and if you get a longer screen on time from your issue it means it is working.
also, make another separate task, search for 'custom setting'. look up from there I thingk it is in system something about screen timeout.
EDIT: run shell command task suggest you run it manually., than see if it works. if not, restart device to check if it requires a restart in order to accept new timeout settings.
Click to expand...
Click to collapse
I feel like I'm in Star Trek - "To boldly go, where no one has gone before" XD
When I try your suggestion, I only receive the message that my device isn't rooted.
Btw, for some tasks it is necessary to enable the Write Secure Setting Permission (f.e. Set Assistant), where xou have to setup ADB on your PC. Would such a procedure be registered by the phone as rooting? Anyway, I don't think I would dare to do something I know so little of.
Another solution I was thinking of, is it possible to create a tasker quick tile/ quick setting to change the system screen timeout.
So instead of having it change for certain apps which isn't working at the moment.
Maybe if we can change it from the system so will be for all apps. You can create two separate quick tiles to toggle between different screen timeout settings.
The newest version of Tasker (6.0.9) comes with Tasky.
Tasky offers the possibility to activate premade profiles. One of them is "Keep Display Awake For Apps". And that one works with my OPPO Phone.
I also tried "Auto-Mute Apps", another profile I couldn't get working. It also works fine.
To switch between Tasker and Tasky you just have to click on the "Three-Dots-Button" in the right top corner. It's not like switching apps but using different user interfaces.
Good luck!
- Sorry to say, but this seems to work for some apps and not for others. But at least sometimes it does work.
Thanks for replying back to this thread to inform me. I tried it and it works for the app I was trying to make it work for which is good! Makes it so much easier now.