• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Anyone using Tasker?

Yeah, I could use handcent, if I wanted to use handcent's interface. But, I kind of like the standard sms interface. I already have Tasker, so I don't need another app to do something Tasker is capable of doing on its own.

Alrighty, then all you should have to do is turn off notifications in the main Messaging app. That should keep you from getting duplicate notifications.
 
Alrighty, then all you should have to do is turn off notifications in the main Messaging app. That should keep you from getting duplicate notifications.

That's what I figured. I haven't programmed Tasker to do it yet, but wanted to see what would happen before I do so.
 
I believe i have just set up my Wifi so when im home it comes on and leave it goes off.

context: Wifi Near (ssid/mac info)
Toggle Wifi - On - done

context: Wifi Connected (ssid/mac info) - done
exit task: WiFi Off


now i wanted to know is this good enough or is there a simpler way of doing this?
 
Hi all,
I've just bought Tasker and am also hoping to use it in place of buying the full Juicedefender. I'm a bit out of my depth (a lot actually) with all the options, but what I'd like to do is this:-

Screen Off = Wifi Off
Screen On = Wifi On

I've managed to do the above BUT

I also want Tasker to check for emails say on a 30 minute interval whilst my screen is off, but do this whilst I'm at home using my Wifi connection.

Could anyone guide me through this please? :confused:
 
I'd set up a separate profile that enables/disables (Tasker>Profile Status>Set On/Off) your Wifi on/off profiles depending on whether or not you're at home, but that's just me.

Tasker looks pretty amazing actually, thinking on getting it.

One question though, does it have any noticeable negative effects on your battery life?

Yes and no. There are certain profile contexts (like whether or not an app is running) that Tasker checks quite frequently, and that can cause a battery drain. My main profiles are set up using only ones that it doesn't check incredibly often (like date/time), which then enable (and disable upon exit) the battery-heavy profiles as needed. Really, how you use Tasker determines whether it uses 0.01% or 50% of your battery.
 
Hi all,
I've just bought Tasker and am also hoping to use it in place of buying the full Juicedefender. I'm a bit out of my depth (a lot actually) with all the options, but what I'd like to do is this:-

Screen Off = Wifi Off
Screen On = Wifi On

I've managed to do the above BUT

I also want Tasker to check for emails say on a 30 minute interval whilst my screen is off, but do this whilst I'm at home using my Wifi connection.

Could anyone guide me through this please? :confused:

If you have mobile data enabled, the default behavior in Android is for Wifi to sleep when the device sleeps. I'm not sure if that has the same effect as turning Wifi off.

First a profile to turn Wifi off when the screen goes off:

Context: Display Off
Task:
Wifi Off

Next, a profile to turn Wifi on when the screen comes on:

Context: Display On
Task:
Wifi On

Finally, a profile to turn Wifi on every 30 minutes, for 2 minutes:

Context: Time [Every 30 minutes] (leave the From and To times unchecked)
Context: Variable Value %SCREEN matches off
Exit Task:
Wifi On
Wait 2 minutes
Wifi Off

Create this like a normal profile, but tape the wrench-looking button in the task editor and set the task to keep the device awake. When you're done, tap on the task in the right-hand column of the profile list, and select Move to Exit. The reason we want to make it an Exit Task instead of the usual Enter Task is that repeating profiles (which is what we're creating) are only active for 1 minute at a time. If we use an Enter Task, Tasker will turn Wifi back off after 1 minute - sooner than we want.
 
If I want to use Tasker to play different notification tones depending on the sender, will the Tasker tones override the phone settings or will I get two notification tones?

As it pertains to a sender, Tasker can only react to SMS or K-9 Email. In either case, you could disable notifications in the app that normally produces the notifications, and then produce one with Tasker.

Take a look at this post from JGGRN.
 
I believe i have just set up my Wifi so when im home it comes on and leave it goes off.

context: Wifi Near (ssid/mac info)
Toggle Wifi - On - done

context: Wifi Connected (ssid/mac info) - done
exit task: WiFi Off


now i wanted to know is this good enough or is there a simpler way of doing this?

That's the best way to do it if you want Wifi to turn off as soon as you disconnect. Otherwise you could leave out the second profile and Wifi will eventually turn off after two cycles of Tasker not seeing your ssid/mac info.

If you wanted to, you could add a location (network only) context to the first profile, to have Tasker only check the Wifi Near when you're "in the neighborhood". This might save some battery power.
 
I found a tast somewhere that looked up the sunset time via an rss feed and showed it on the screen as a message. I want to extend that, but I can't find a proper rss feed.

I think I found the same profile that you mention. The RSS feed it used did not work for me, either, so I found a different one that works (if you're in the US).

I used: weather.yahooapis.com/forecastrss?w=12776597

the numbers after the w= are particular to my area, so you need to use your own location, but this works great. You can get the explanation and more details on how to find your location from here: Yahoo! Weather - Yahoo! Developer Network
 
Im trying to set a task so when i activate my app Car Dock V2.1 it
will turn on speakerphone, as well as GPS. And then turn off of course
when i exit the app. This works.


But in Car Dock V2.1 when i select my Maps app for navigation purpose,
it sees as exiting car dock and turns GPS off (because when i enter
maps it cant locate where i am, and if i quickly go to home screen it
shows GPS off). And also if i click on dialer from Car Dock v2.1 and
try to make a call, its not in speakerphone.
All help is appreciated! Thanks!

Maybe you could remove the GPS on from your car dock activation and instead change that to a task that turns on GPS when your Maps app opens. That way when you run your car dock app, it turns on speaker phone and when you run Maps from inside car dock, it will trigger the GPS? and then in your original car dock profile, add an exit task to turn off GPS?

I'm not familiar with your Car Dock app so just throwing out an idea.
 
So I happily set up my "Home" and "School" profiles using a "Wifi Connected" toggle (Wifi Near seemed to have issues for me), but I have the following problem. I'd set my data to turn off after 15 minutes when the phone is asleep in the interest of saving battery, but then my wifi disconnects and the profile shuts down. I can't really use a location context, since my home and school are fairly close (within the error reported by my network). Anybody have any good ideas for getting around this?
 
So I happily set up my "Home" and "School" profiles using a "Wifi Connected" toggle (Wifi Near seemed to have issues for me), but I have the following problem. I'd set my data to turn off after 15 minutes when the phone is asleep in the interest of saving battery, but then my wifi disconnects and the profile shuts down. I can't really use a location context, since my home and school are fairly close (within the error reported by my network). Anybody have any good ideas for getting around this?

What setting are you using for having your data turn off?
 
that's the best way to do it if you want wifi to turn off as soon as you disconnect. Otherwise you could leave out the second profile and wifi will eventually turn off after two cycles of tasker not seeing your ssid/mac info.

If you wanted to, you could add a location (network only) context to the first profile, to have tasker only check the wifi near when you're "in the neighborhood". This might save some battery power.

how would i set that up?
All in all including the location part
 
So I happily set up my "Home" and "School" profiles using a "Wifi Connected" toggle (Wifi Near seemed to have issues for me), but I have the following problem. I'd set my data to turn off after 15 minutes when the phone is asleep in the interest of saving battery, but then my wifi disconnects and the profile shuts down. I can't really use a location context, since my home and school are fairly close (within the error reported by my network). Anybody have any good ideas for getting around this?

What issues were you having with Wifi Near? Maybe we can work on resolving that?

To stick with your current approach...

Profile 1
Context: Wifi Connected <school>
Enter Task:
Variable Set %ATSCHOOL 1
Exit Task:
Variable Clear %ATSCHOOL If %WIFI matches on

Profile 2
Context: Variable Value %ATSCHOOL = 1
Enter Task: <settings you want>

Profile 3
Context: Variable Value %WIFI matches on
Enter Task:
Wait 1 minute
Variable Clear %ATSCHOOL If %WIFII Doesn't Match *<SchoolSSID>*

When you connect to your school Wifi, the %ATSCHOOL variable will be set to 1, causing profile 2 to activate, setting the settings you want.

If you disconnect from your school Wifi while Wifi is on, the %ATSCHOOL variable will be cleared and profile 2 will exit - causing Tasker to restore your settings. If you disconnect because Wifi is off, then the variable won't be cleared and profile 2 will remain active.

After Wifi has been off, when you turn it back on, profile 3 will become active, and if you are not connected to your school Wifi within 1 minute (you may need to adjust this time), the %ATSCHOOL variable will be cleared, causing profile 2 to exit and Tasker to restore your settings.

This series of profiles basically ignores the fact that you're disconnected while Wifi is off, and gives it a minute to reconnect after turning back on before it determines if you're still at school.
 
how would i set that up?
All in all including the location part

Take the first profile you currently have and add a location context to it. Use Network only (turn off the GPS when you are setting the location). That's it.

Since the Network location uses less power than the Wifi Near, Tasker will check for the location first. Once the location is satisfied, it will start scanning to find the Wifi Near.

Remember, either the location or the Wifi Near will cause the profile to exit.

I had a problem because, for some reason, at home my network location goes wonky. It will occasionally be unable to detect any location at all, and that drops me out of the profile even though my Wifi is connected. So, see if it works for you. If not, you can stick with using only the Wifi Near (that's what I do) and it's not a huge difference battery-wise.
 
What issues were you having with Wifi Near? Maybe we can work on resolving that?

To stick with your current approach...

Profile 1
Context: Wifi Connected <school>
Enter Task:
Variable Set %ATSCHOOL 1
Exit Task:
Variable Clear %ATSCHOOL If %WIFI matches on

Profile 2
Context: Variable Value %ATSCHOOL = 1
Enter Task: <settings you want>

Profile 3
Context: Variable Value %WIFI matches on
Enter Task:
Wait 1 minute
Variable Clear %ATSCHOOL If %WIFII Doesn't Match *<SchoolSSID>*

When you connect to your school Wifi, the %ATSCHOOL variable will be set to 1, causing profile 2 to activate, setting the settings you want.

If you disconnect from your school Wifi while Wifi is on, the %ATSCHOOL variable will be cleared and profile 2 will exit - causing Tasker to restore your settings. If you disconnect because Wifi is off, then the variable won't be cleared and profile 2 will remain active.

After Wifi has been off, when you turn it back on, profile 3 will become active, and if you are not connected to your school Wifi within 1 minute (you may need to adjust this time), the %ATSCHOOL variable will be cleared, causing profile 2 to exit and Tasker to restore your settings.

This series of profiles basically ignores the fact that you're disconnected while Wifi is off, and gives it a minute to reconnect after turning back on before it determines if you're still at school.

Okay, that makes sense! I was having issues with "Wifi Near" because sometimes I would check my phone and my wifi would be turned off, which I thought had something to do with the "Toggle Wifi" option. I'm just now realizing that was probably just being caused by the data timeout.

For the record, when "Toggle Wifi" is enabled, if the Wifi is off it will turn on so every so often to scan for the network, and when "Toggle Wifi" is disabled, if the Wifi is off, Tasker will never do any Wifi scans and then the profile will never come on, right?

Finally, how does "Wifi Near" behave when the Wifi shuts off? Does it just assume that you're still near the network until it scans and finds otherwise? If that's the case, then just changing the context to "Wifi Near" would leave the profile active even when the data shut off after 15 minutes?

Thanks for the help!
 
UncleMike, I didn't have time to reply earlier but thank you very much for that information, I shall have a go and see how I get on. :)
 
Take the first profile you currently have and add a location context to it. Use Network only (turn off the GPS when you are setting the location). That's it.

Since the Network location uses less power than the Wifi Near, Tasker will check for the location first. Once the location is satisfied, it will start scanning to find the Wifi Near.

Remember, either the location or the Wifi Near will cause the profile to exit.

I had a problem because, for some reason, at home my network location goes wonky. It will occasionally be unable to detect any location at all, and that drops me out of the profile even though my Wifi is connected. So, see if it works for you. If not, you can stick with using only the Wifi Near (that's what I do) and it's not a huge difference battery-wise.

I was doing something similar and similar issues with my network only location. At times it would report that I was about 8 miles away. Maybe I was connecting to a distant tower due to my location in the house, or maybe a closer tower was providing bogus information. Either way, it was a problem. Here's what I did:

Profile: Home Area
Context: Location <home>
Enter Task:
Variable Add %HOME 1
Exit Task:
Variable Subtract %HOME 1

Profile: Home Wifi
Context: Variable Value %HOME > 0
Context: Wifi Near <home Wifi> [Toggle Wifi]
Enter Task:
Variable Add %HOME 1
Wifi On
Exit Task:
Variable Subtract %HOME 1

Profile: (cleanup)
Context: Device Shutdown
Task:
Variable Clear %HOME

After any reboot, %HOME is uninitialized (has a value of ZERO for math operations).

When I get close to home, the Home Area profile activates and %HOME is incremented to a value of 1. This satisfies the first context in the Home Wifi profile, allowing Tasker to start toggling Wifi to see if the second context is satisfied. When I REALLY close to home, my home Wifi is detected and the Home Wifi profile activates, turning on Wifi and %HOME is incremented to a value of 2.

If I temporarily get a wonky network location, causing the Home Area profile to deactivate, %HOME is decremented by 1 to a value of 1, but this does not cause the Home Wifi profile to deactivate. The only way that Home Wifi exits is if BOTH the Wifi Near context and the Location context are no longer satisfied.

The reason the cleanup profile is necessary is that Tasker does not (yet?) execute exit tasks upon shutdown, and if you shutdown when %HOME is > 0 then the values are screwed up when your device starts up again.
 
For the record, when "Toggle Wifi" is enabled, if the Wifi is off it will turn on so every so often to scan for the network, and when "Toggle Wifi" is disabled, if the Wifi is off, Tasker will never do any Wifi scans and then the profile will never come on, right?

Finally, how does "Wifi Near" behave when the Wifi shuts off? Does it just assume that you're still near the network until it scans and finds otherwise? If that's the case, then just changing the context to "Wifi Near" would leave the profile active even when the data shut off after 15 minutes?

Thanks for the help!

Yes, Toogle Wifi allows Tasker to turn Wifi on periodically to check available Wifi signals. If Wifi is off and Toggle Wifi is not checked (in at least one enabled profile using a Wifi Near context), the the profiles using Wifi Near will never activate.

If Wifi shuts off during an active profile using a Wifi Near context, Tasker may (I'm not sure) use cached information for some period before determining that it should exit, but it will eventually exit even if Wifi is not turned on again. Debate on how Tasker should behave in this situation is the reason for the Toggle Wifi option - it was decided to leave it up to the user.
 
Context: Variable Value %SCREEN matches off

I'm looking at the different options shown under 'Select Variable Action', which one should I select?


  • Clear
  • Add
  • Join
  • Split
  • Subtract
  • List
  • Randomize
Thanks again.
 
Can someone help me set up when my phone is on vibrate to mute the media volume? I've looked everywhere but cannot set the value. When I try it says it cannot be used.
 
Can someone help me set up when my phone is on vibrate to mute the media volume? I've looked everywhere but cannot set the value. When I try it says it cannot be used.

Try this:

Context: Variable Value %SILENT Matches vibrate
Enter Task:
Media Volume 0

I think there might be a bug in the current version where %SILENT is not considered dynamic and can't be monitored this way. (I'm using a beta, so I can't say for sure).
 
  • Like
Reactions: oo3
I was doing something similar and similar issues with my network only location. At times it would report that I was about 8 miles away. Maybe I was connecting to a distant tower due to my location in the house, or maybe a closer tower was providing bogus information. Either way, it was a problem. Here's what I did:

This is great Mike, thanks! I'm going to save your post and I might try it in the future.

Recently I decided to simplify my profiles. I found that I can do everything I need using Wifi Near and I don't have any location contexts anymore.

How great is the difference in battery usage between Network-only location and Wifi Near contexts? I know Network location uses less, but how much less?

The reason I ask is because I don't know if it's better to set up:

1) all profiles with Wifi Near only, and no location-based profiles

(Wifi Near uses more power than location, but phone is never checking for location...)

or

2) all profiles with Network Location first, then Wifi Near once I am within the location area

(Phone checks for location, and then (when in a location area) phone is checking for location AND scanning Wifi Near)
 
Back
Top Bottom