1.3.3 Published

257 views
Skip to first unread message

Pent

unread,
Nov 15, 2012, 7:49:36 AM11/15/12
to Tasker
Takes a while to appear on Market.

Pent

Peter Radcliffe

unread,
Nov 15, 2012, 9:17:09 AM11/15/12
to Tasker
Pent <sup...@apps.dinglisch.net> probably said:
>Takes a while to appear on Market.

With Tasker 1.3.3 on Android 4.2 I'm not seeing wifi connected working
at all, even with no SSID selected.

I have a simple test profile, the only context is wifi connected *, *,
* and it never goes active.

P.

--
pir

Peter Radcliffe

unread,
Nov 15, 2012, 9:30:35 AM11/15/12
to Tasker
15-11-2012 M: 14.20.25#M: loc setup
15-11-2012 M: 14.20.25#M: sensor
15-11-2012 M: 14.20.25#M: pen var
15-11-2012 M: 14.20.25#M: done init: true
15-11-2012 M: 14.20.25#M: initial match checks
15-11-2012 M: 14.20.25#M: queried plugins done
15-11-2012 M: 14.20.25#M: map, no devices
15-11-2012 M: 14.20.25#M: wifi connection, major type: 1 connected: true
15-11-2012 M: 14.20.25#M: have wifi connection info: "wpa.rfc.pir.net"
15-11-2012 M: 14.20.25#M: record wifi connection state: true
15-11-2012 M: 14.20.25#M: checkMatchStates: handleChanges: false handle:
15-11-2012 State: 14.20.25#State: checkMatch: code 10: false -> true
15-11-2012 State: 14.20.25#State: checkMatch: code 10: false -> true
15-11-2012 TaskerContext: 14.20.25#TaskerContext: call: wantednum: wantin: tru
e wantout: true havein: haveout:
15-11-2012 Utils: 14.20.25#Utils: wifi ssid workaround 4.2, matched with quotes
: "wpa.rfc.pir.net"
15-11-2012 Expr: 14.20.25#Expr: warning: null or empty pattern with target 00:2
4:36:ab:30:7f
15-11-2012 Utils: 14.20.25#Utils: wifi ssid workaround 4.2, matched with quotes
: "wpa.rfc.pir.net"
15-11-2012 Expr: 14.20.25#Expr: warning: null or empty pattern with target 00:2
4:36:ab:30:7f
15-11-2012 Expr: 14.20.25#Expr: warning: null or empty pattern with target 00:2
4:36:ab:30:7f
15-11-2012 M: 14.20.25#M: checkMatchStates: done
15-11-2012 M: 14.20.25#M: recmatch done
15-11-2012 M: 14.20.25#M: checkMatchLocs: done
15-11-2012 M: 14.20.25#M: checkMatchApp: done
15-11-2012 M: 14.20.25#M: check instant activation id: 11: not active
15-11-2012 M: 14.20.25#M: check instant activation id: 41: not active
15-11-2012 M: 14.20.25#M: check instant activation id: 33: not active
15-11-2012 M: 14.20.25#M: check instant activation id: 39: not active
15-11-2012 M: 14.20.25#M: check instant activation id: 44: not active
15-11-2012 M: 14.20.25#M: check instant activation id: 37: not active
15-11-2012 M: 14.20.25#M: check instant activation id: 67: not active
15-11-2012 M: 14.20.25#M: initial match checks: done

WiFiTest is never listed in a 'profile -> ' log line, of any kind.

P.

--
pir

ashburn15 (Syed Abu Bakar)

unread,
Nov 15, 2012, 9:34:04 AM11/15/12
to tas...@googlegroups.com
Release notes for the v1.3.3 says "04/11/2012: v1.3.2u1" at the top..

UncleMike

unread,
Nov 15, 2012, 10:06:22 AM11/15/12
to tas...@googlegroups.com
Same here, but on Android 4.1.2.  A profile with a single context of "Wifi Connected" with no parameters specified, does not activate.  Profiles using similar contexts were working fine with Tasker 1.3.3b2.

Pent

unread,
Nov 15, 2012, 10:18:16 AM11/15/12
to Tasker
> Same here, but on Android 4.1.2.  A profile with a single context of "Wifi
> Connected" with no parameters specified, does not activate.  Profiles using
> similar contexts were working fine with Tasker 1.3.3b2.

OK, testing, thanks.

Pent

Scott Miller

unread,
Nov 15, 2012, 8:09:26 AM11/15/12
to tas...@googlegroups.com
It seems that WiFi connected is not being detected in the release. It was working in b2. I reinstalled b2 and all is well. No other changes on my end.

Direct version, Android 4.0.4, rooted, stock.

Scott

Pent

unread,
Nov 15, 2012, 10:28:49 AM11/15/12
to Tasker
I'm uploading a new release (u1) now.

Pent

Scott Miller

unread,
Nov 15, 2012, 11:26:12 AM11/15/12
to tas...@googlegroups.com
Thanks. Much better. :-)

Scott

UncleMike

unread,
Nov 15, 2012, 11:35:19 AM11/15/12
to tas...@googlegroups.com
With Tasker 1.3.3u1 and Android 4.1.2, Wifi Connected contexts appear to be working both with and without an SSID specified, including a single specific SSID and an SSID using pattern matching.

Pent

unread,
Nov 15, 2012, 11:46:22 AM11/15/12
to Tasker
> With Tasker 1.3.3u1 and Android 4.1.2, Wifi Connected contexts appear to be
> working both with and without an SSID specified, including a single
> specific SSID and an SSID using pattern matching.

Result!

I can fix anything with a German wheat beer by my side.

Pent

Peter Radcliffe

unread,
Nov 15, 2012, 11:52:25 AM11/15/12
to Tasker
Pent <sup...@apps.dinglisch.net> probably said:
>> With Tasker 1.3.3u1 and Android 4.1.2, Wifi Connected contexts appear to be
>> working both with and without an SSID specified, including a single
>> specific SSID and an SSID using pattern matching.

Yep, looks good here too. Thanks for the quick fix, Pent.

>Result!
>I can fix anything with a German wheat beer by my side.

That's quite a superpower!

P.

--
pir

UncleMike

unread,
Nov 15, 2012, 12:09:43 PM11/15/12
to tas...@googlegroups.com
A powerful ally indeed.  :)

And... thanks here too!

Brad Minion

unread,
Nov 15, 2012, 12:35:58 PM11/15/12
to tas...@googlegroups.com
Did you by chance break it for ICS?  My WiFI connected profile is not firing since the update.

Brad Minion

unread,
Nov 15, 2012, 12:43:29 PM11/15/12
to tas...@googlegroups.com


On Thu, Nov 15, 2012 at 11:35 AM, Brad Minion <br...@bradminion.com> wrote:

Did you by chance break it for ICS?  My WiFI connected profile is not firing since the update.

Nevermind. I just got the U1 update and it's working again.

Rob

unread,
Nov 16, 2012, 6:07:17 AM11/16/12
to tas...@googlegroups.com
I am getting "Expr: warning: null or empty pattern with target 74:44:01:74:a4:6f" with my call recording task that was working fine on all previous versions.

Any idea how I can debug this or find out what this "target" is?

PS: is there any way to determine which task threw the error that pops up when going into Tasker? And if so, to determine which part of the task caused it?

Thanks

Pent

unread,
Nov 16, 2012, 6:16:42 AM11/16/12
to Tasker
> I am getting "Expr: warning: null or empty pattern with target
> 74:44:01:74:a4:6f" with my call recording task that was working fine on all
> previous versions.

You're the second one this morning. I guess that string is a MAC
address in a Wifi Connected state. Do you have the latest Tasker
version (1.3.3u1) (see Menu / Info / About in the Tasker main screen).

Pent

Rob

unread,
Nov 16, 2012, 7:08:50 AM11/16/12
to tas...@googlegroups.com
I thought I did, but I see that I have the previous one. Updating now....
Thanks for the quick response!

Whilst I think about it, I have never figured out how to "monitor" a variable so that it gets updated.
For instance, when I try to store the outgoing/incoming call number, it is always one number behind (previous number).
Please explain how I can monitor these variables so that they get updated. I have tried suggestions from other threads but never managed to figure this out.
Unless the call variables are always one behind by design???

THANKS.

Pent

unread,
Nov 16, 2012, 7:37:23 AM11/16/12
to Tasker
Did you read the documentation about the variables in the Variables
section of the userguide ?

Pent

Rob

unread,
Nov 16, 2012, 9:24:23 AM11/16/12
to tas...@googlegroups.com
I have indeed. It says that %CNUM, for instance, is monitored, but is it monitored by the system just because I have used it in a task, or is there something specific that I need to do to monitor it?
I am a programmer but this is the only thing I cannot figure out.

Please forgive me and point me to something that will show me what I am missing here. Thank you Pent.

Philotes82

unread,
Nov 17, 2012, 7:48:21 AM11/17/12
to Tasker
Pent,
My Appfactory kids fc on the target device, before this release( and
the beta) my kids were fine.
Now the same project crashes upon start, I get repeating fc after x
minutes.
Any idea?
Thanks.

Pent

unread,
Nov 17, 2012, 7:58:13 AM11/17/12
to Tasker

Daniel Stříbrný

unread,
Nov 17, 2012, 8:30:11 AM11/17/12
to tas...@googlegroups.com
Have same problem from 1.3.3 stable. When export as app should start, Tasked FC occurred... I will send log during today...

Brad Minion

unread,
Nov 17, 2012, 2:48:28 PM11/17/12
to tas...@googlegroups.com
I had this same problem. After install and pressing the app ICON, it would think about it for a while and then pop up some message about the app closing down. Sorry I don't remember what it said but the words "force close" was not part of the test. More like, it's having a problem and must shut down.

What seemed to work for me was to reboot after installing the app. Now it doesn't force close, but it doesn't work either. Unfortunately, the kid app is still not recognizing Wifi Connect automatically, even after your permissions fix, Pent. The only way it will work is for me to click the app ICON.

BradM

Pent

unread,
Nov 18, 2012, 3:52:09 AM11/18/12
to Tasker

> What seemed to work for me was to reboot after installing the app. Now it
> doesn't force close, but it doesn't work either. Unfortunately, the kid app
> is still not recognizing Wifi Connect automatically, even after your
> permissions fix, Pent. The only way it will work is for me to click the app
> ICON.

Could you tell me which permissions are shown in the 'advanced' part
of the kid config screen ?

Thanks,

Pent

Brad Minion

unread,
Nov 18, 2012, 9:26:04 AM11/18/12
to tas...@googlegroups.com
On Sun, Nov 18, 2012 at 2:52 AM, Pent <sup...@apps.dinglisch.net> wrote:
Could you tell me which permissions are shown in the 'advanced' part
of the kid config screen ?
Pent

WAKE_LOCK
ACCESS_NETWORK_STATE
RECEIVE_BOOT_COMPLETED

Pent

unread,
Nov 18, 2012, 12:04:49 PM11/18/12
to Tasker
> ACCESS_NETWORK_STATE

OK, that was the one it was complaining about in the last log. Guess
something else is going wrong now, any chance of another log ?

Pent

Brad Minion

unread,
Nov 18, 2012, 6:05:18 PM11/18/12
to tas...@googlegroups.com
Logs sent with subject line: WiFi Connected Child App not sensing Wifi connect - BradM

NMat

unread,
Nov 20, 2012, 2:54:47 AM11/20/12
to tas...@googlegroups.com
Hi Pent,

FYI.
I noticed that Continuous Input in the Samsung keyboard gets disabled when I turn on the Tasker - JB Accessibility Service.

Pent

unread,
Nov 20, 2012, 3:42:19 AM11/20/12
to Tasker
> I noticed that Continuous Input in the Samsung keyboard gets disabled when
> I turn on the Tasker - JB Accessibility Service.

Thanks for mentioning, but there's nothing I can do about that, it's
two parts of the operating system interacting. Tasker doesn't itself
turn off Continuous Input (though I'm not entirely sure what that
is :-))

There have been other Android problems with turning an app's
accessibility service on causing side effects in OS components.

Pent
Reply all
Reply to author
Forward
0 new messages