chrlswltrs
Extreme Android User
Can someone please explain how the WiFi near context works? How does it affect battery life? From reading the other posts am I correct to assume that it works even when WiFi is turned off.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Anyone using Tasker?
- Thread starter myko14
- Start date
I've tried to save a little wear and tear on my N1's power button by creating a profile that simply changes the screen timeout to the minimum (7 seconds) when I place my phone face down. Otherwise, I keep my timeout at 15 minutes.
This works most of the time, but every now and then it just won't turn off the screen, and I'm not sure why. I added a notify message and a short vibrate to the beginning of my profile so I could check if it was running. Every time I place the phone face down, within a few seconds it will vibrate to let me know the profile has started. However, as I mentioned, there are times it still does not turn off the screen.
If I keep the phone face down, but hold it up high enough to view the screen, I can see my profile message is displayed in the notification area, and the Tasker icon indicates my profile is active. Strangely enough, if I pull down the notification area "windowshade" and wait with it in the down position, the screen does shut down within 7 seconds from then, every time. I tried different home screens, in case a widget was causing a conflict somehow, but the profile still is intermittent now and then.
Can anyone offer any opinions/suggestions how to get this to work consistently?
Thanks.
This works most of the time, but every now and then it just won't turn off the screen, and I'm not sure why. I added a notify message and a short vibrate to the beginning of my profile so I could check if it was running. Every time I place the phone face down, within a few seconds it will vibrate to let me know the profile has started. However, as I mentioned, there are times it still does not turn off the screen.
If I keep the phone face down, but hold it up high enough to view the screen, I can see my profile message is displayed in the notification area, and the Tasker icon indicates my profile is active. Strangely enough, if I pull down the notification area "windowshade" and wait with it in the down position, the screen does shut down within 7 seconds from then, every time. I tried different home screens, in case a widget was causing a conflict somehow, but the profile still is intermittent now and then.
Can anyone offer any opinions/suggestions how to get this to work consistently?
Thanks.
Wifi Near will work even when Wifi is off *IF* you check the Toggle Wifi setting in the context. With this option checked, Tasker will turn on Wifi if necessary for the purpose of scanning for nearby networks, at a frequency determined by the Wifi Scan time under Preferences. See the Tasker help for how Tasker ranks Wifi Near in terms of power consumption.
If you want, you can further limit it's use to certain geographic areas by adding a Location (network) or Cell Near context. Tasker checks contexts in order of ascending power consumption, so Wifi Near would not be checked at all unless these other contexts are satisfied first.
You seem to have verified that the task is running, and that the setting is being set (screen turns off after additional interaction), so at this point I would suggest reporting this in the Tasker discussions at Google Groups. The developer should pick up on the message and may ask for a log.
Do you have any tasks defined that are set to keep the device awake? If so, is it possible that one of them is running at the time?
I'll ask there. Thanks. No, I don't have any tasks that have a keep device awake. Just a few location ones so if I go shopping at various stores a list of items particular to that store pops up (thanks to Astrid plugin), and the usual night time quiet mode stuff. Everything else works great. Just this one profile is giving me a bit of trouble.
Thanks for the input.
I seem to have another weird problem now. The profile with the Wifi Near context seems to randomly go inactive while I'm in the near home radius and still connected to wifi. Any other profiles I have set to turn on as a result of wifi near also go inactive, but the tasks, including wifi on, all stay running. If I stop and start tasker, the profiles all go active again. The Home Near profile stays active the whole time, though.
I'm at a loss here. You might want to bring this over to the Tasker Google Group.
SlvrScoobie
Android Enthusiast
sounds like what im having problems with here. I can see that tasker is running the near home task, wifi is on, but it seems to be using 1X data. ??
This may have been asked/answered already, but I can't find it. I'm using the headset plugged profile here. Launch Menu of Music Apps When Headset Inserted - Tasker Wiki
Works fine, except I don't see the names. I thought I saw a fix at some point, but can't find it again. Also, I tried adding to it to set the media volume to 10, but when I add that, the volume =10 shows up in the menu that pops up to select the media player. Do I need a sep profile?
Works fine, except I don't see the names. I thought I saw a fix at some point, but can't find it again. Also, I tried adding to it to set the media volume to 10, but when I add that, the volume =10 shows up in the menu that pops up to select the media player. Do I need a sep profile?
SlvrScoobie
Android Enthusiast
So is there a way to have tasker turn off the screen? Couldnt find one in the wiki or this page.. would be nice for my night time profile.
Yeah, I think I'll do that. Thanks for all your help.
Have reading a bit of the WiFi Near profiles and it doesn't match anything I have.
Does this seem correct?
Profile: Wifi Near
Context: SSID (Router Name)
Channel: 11
Toggle Wifi: Checked
Task
WiFi: SetOn
Exit Task
WiFi: SetOff
It seems so simple compared to others I've seen on here.
Does this seem correct?
Profile: Wifi Near
Context: SSID (Router Name)
Channel: 11
Toggle Wifi: Checked
Task
WiFi: SetOn
Exit Task
WiFi: SetOff
It seems so simple compared to others I've seen on here.
I'm nat familiar with the Wiki entry, but it sounds like adding a Stop action the task will fix this. There's a bug that causes the labels not to display under certain circumstances.
A task can be either a menu task or an execute task, not both. If you need to set the volume as part of the profile, you have to make the menu task a separate task that you run using the Perform Task action from within the task that changes the volume, like this:
Media Volume 10
Perform Task <menu>
No. The closest you can get is to set the display timeout to 7 seconds (minimum value).
That should work fine. It only gets more complicated if you want to limit it further, like only when near home (using a location context), or if you want to turn of Wifi sooner than it would happen with this profile (it might take 20 minutes with your profile).
I notice when I'm somewhere else and I turn on the screen it always turns on WiFi. Is that supposed to happen? My understanding is that its supposed to turn on every 120 seconds and check to see if my SSID is in range.
amlothi
Android Expert
Does Wifi stay on? Or is it only on momentarily?
There are different settings in Tasker for how often it will check. One setting is for how often when the screen is off, and another for how often when the screen is on.
Due to the different settings for check frequecy when the screen is on versus off, turning the screen on triggers a check. If you keep the device awake, Wifi is turned on to check for nearby networks as specified in the Preferences.
vpraveenis
Newbie
I just started using tasker and see that it is so very powerful. I tried to learn the ropes by trying out a "simple" tasker widget which will toggle screen rotation ON/OFF. After feeling my way around the app for sometime..... and failing, I turned to google to help me out. There were examples of how to enable/disable screen rotation on opening an app etc.. I could not find how to make a toggle widget.
Can someone please post basic steps on how to create a tasker widget which will toggle screen rotation. I looked at tasker wiki, but could not find any variable which gave me the status of current screen rotation setting value.
Can someone please post basic steps on how to create a tasker widget which will toggle screen rotation. I looked at tasker wiki, but could not find any variable which gave me the status of current screen rotation setting value.
Ok, thanks guys. Just wasn't sure if it was normal for it to turn on and check every-time I turned on the screen.
i need some help here
i have it set up so when i plug headphones into my droid x, a menu with the choice of music or slacker appear. and when i take out the jack, it is suppose to kill these 2. this worked PERFECT before i had the OTA the other day.
here is what i have
Context: Headset Plugged (any)
Enter: Load App Music. Load App Slacker.
Task type - Menu
Context: Headset Plugged (any)
enter: Display Brightness 255, Widgetlocker Suspend, Keyguard Off
exit: Widgetlocker Resume, Display Brightness 30.
please help!
i have it set up so when i plug headphones into my droid x, a menu with the choice of music or slacker appear. and when i take out the jack, it is suppose to kill these 2. this worked PERFECT before i had the OTA the other day.
here is what i have
Context: Headset Plugged (any)
Enter: Load App Music. Load App Slacker.
Task type - Menu
Context: Headset Plugged (any)
enter: Display Brightness 255, Widgetlocker Suspend, Keyguard Off
exit: Widgetlocker Resume, Display Brightness 30.
please help!
chrlswltrs
Extreme Android User
Were you on 2.1 or 2.2 before the OTA? If you were on 2.1 then your problem is easily explained. In 2.2 Google took away the ability for an app to kill another app, this includes Tasker killing apps.
This was very frustrating to me when I first updated to 2.2 also. There is no work around right now, it is just a problem with 2.2 that google thought was a good thing
A.Nonymous
Extreme Android User
My understanding (from reading the Location without tears section on their site) is that Tasker uses the least power hungry context first. I've got a profile that launches an app if I'm plugged into AC power during a certain time of day. The first thing Tasker does in this case is check the time of day. If the time of day isn't the time the profile isn't active it doesn't even bother to check AC power status. So if you have wi-fi near set as a context, Tasker will try to check the other less power requiring contexts first (time, power, etc.....) I don't think it will check wifi if wifi is off, but I don't know that for sure.
chrlswltrs
Extreme Android User
*** deleted, I responded to the wrong post, sorry
Were you on 2.1 or 2.2 before the OTA? If you were on 2.1 then your problem is easily explained. In 2.2 Google took away the ability for an app to kill another app, this includes Tasker killing apps.
This was very frustrating to me when I first updated to 2.2 also. There is no work around right now, it is just a problem with 2.2 that google thought was a good thing
this is a sad day indeed....
i wonder if the dev will have a work around to this