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.
> 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.
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.
> 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.
>> 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.
On Thursday, November 15, 2012 11:52:32 AM UTC-5, pir wrote:
> Pent <sup...@apps.dinglisch.net <javascript:>> 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.
On Thu, Nov 15, 2012 at 10:46 AM, Pent <supp...@apps.dinglisch.net> wrote:
> > 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
Did you by chance break it for ICS? My WiFI connected profile is not
firing since the update.
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?
> 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).
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???
On Friday, 16 November 2012 13:16:45 UTC+2, Pent wrote:
> > 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).
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.
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.
On Sat, Nov 17, 2012 at 6:48 AM, Philotes82
<stop.frustrating...@gmail.com>wrote:
> 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.
> 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.
> 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 ?
