Tasker Beta 4.3b8+

[Pent]

http://tasker.dinglisch.net/beta.html

No more features going in after this one, just bug fixes.

Pent

Cumulative Changes To b8

• added: developers: TaskerPlugin: constants for requested timeouts NONE, MAX and NEVER
• added: multiple If conditions in actions
• added: search: search names of installed plugins and show as features
• bugfix: app creation: icons used in notify actions could cause crashes in some circumstances
• bugfix: action plugin: Never timeout was stopping after an hour
• bugfix: plugin lists weren't alphabetic
• bugfix: Run An Action: action edit was finishing if file selection dialog was used
• bugfix: state plugins: requery when the plugin package is updated
• bugfix: state Calendar Entry: UI wasn't allowing variables in Calendar parameter (despite showing selector...)
• added: built-in local variable %priority, also to userguide
• change: Run Log: when going to edit entry, use name to retrieve entity if ID doesn't exist (where possible)
• change: profile list: show export option for unnamed profiles, demand name if clicked
• change: action edit: Label parameter vis controlled with checkbox
• change: action edit: rearranged bottom fixed params
• change: Run Log: long-click for options instead of single click to go to item
• change: don't allow Beginner Mode (or show option for it) if have projects in data
• bugfix: main screen, beginner mode, + button wasn't centered
• beta: bugfix: BT Near: Name/Address selector appends with / instead of replacing
• beta: change: Run Shell root timeout: try explicit kill via another root process
• bugfix: BT Connected: Name/Address selector appends with / instead of replacing
• beta: bugfix: HTTP Get/Post (SSL): don't do hostname verification when Trust All Certs is enabled (man-in-the-middle can include any hostname anyway)
• added: Run Log: long-click option Filter On
• added: Run Log: help page in userguide
• change: Run Log: record and restore current position until exiting Tasker
• change: Run Log: returning from task edit launched via Run Log returns to Run Log, not main screen
• change: Run Log: only allow most-recent-top direction, faster and works better with restoring position
• bugfix: upgrading some old photo actions to the unified version was failing
• bugfix: JS: shell function: was losing newlines in output
• bugfix: app creation: JS: prompt/alert/confirm was crashing
• change: Search Tasker: returning from task/scene edit launched via Search Tasker returns to search screen, not main screen

[Pent]

BTW, the presentation for the action edit screen multiple If conditions is a first attempt :-)

I will happily read all suggestions for improvements.

Pent

[David Wang]

A 404 Not Found error was encountered when I click the "App Factory Download" link for 4.3b8 on "Tasker Beta Download" page just now.

David

[David Wang]

BTW, the presentation for the action edit screen multiple If conditions is a first attempt :-)

 Awesome! The multiple If conditions is a good attempt. But I'm confused about the "tight binding“ logic. Unfortunately, I cann't fnd any related information about the term in the help files of Tasker. Only got a page about "Tight binding" on wikipedia. And it seems that the term is about physics. Any examples about the "tight binding" AND/OR logic?

David

[Bob Hansen]

While on the If action screen use Menu > Help: This Screen

[Pent]

A 404 Not Found error was encountered when I click the "App Factory Download" link for 4.3b8 on "Tasker Beta Download" page just now.

Sorry, fixed.

Pent

[Pent]

 Awesome! The multiple If conditions is a good attempt. But I'm confused about the "tight binding“ logic. Unfortunately, I cann't fnd any related information about the term in the help files of Tasker. Only got a page about "Tight binding" on wikipedia. And it seems that the term is about physics. Any examples about the "tight binding" AND/OR logic?

As Bob says.

Note also that the userguide in the betas is only updated for the Download To SD version.

Maybe I should have used 'precedence', I think that's the official term. May change it.

Pent

[Bob Hansen]

The new multiple If condition feature is great! 

I've been playing with it and I think your approach to implementing it is brilliant.

One suggest: It is not clear how to delete an If condition. I figured it out, but I could not find it in the help anywhere.

Should add a statement about the "None" condition operator. (Would "Remove" be more descriptive?)

[Rich D]

Thanks for all the run log updates.....  :)

One issue so far..
1. Open run log
2. Long press on item / edit
3. Tasker opens to edit view of item
4. Hit back button
5. Tasker returns to run log but to a seemingly random time below the previously selected item time. And will now return to this time no matter what other times are selected for edit and then hit the back button.

While testing I also saw this strange listing .. note the times in the screen shot..

The chronological order is reversed and  10.15.47 is out of place..

[Pent]

I've been playing with it and I think your approach to implementing it is brilliant.

Glad you like it. I had to muse over it a few days first and didn't want to spend too much
time on it.

One suggest: It is not clear how to delete an If condition. I figured it out, but I could not find it in the help anywhere.

Good point.  I would like to put a trashcan button next to each condition, but think there's
already a shortage of space. Or a 'delete above' and 'delete below' button of some kind on the right side of
each boolean line ?

Should add a statement about the "None" condition operator. (Would "Remove" be more descriptive?)

Also crossed my mind. Waiting to see if there are other suggestions for deleting
a condition (since then the None can be removed anyway).

Pent

[Rich D]

Sorry forgot my stats...

I have a rooted Motorola Droid 4 / Stock ROM   / Tasker  / Version: 4.3b8m / Android version 4.1.2

[Bob Hansen]

One thing does not seem logical to me is what happens when you select "None" (delete) in a multiple condition. I created the condition below and when I delete the middle OR condition I expected that I would be left with the AND condition. However, the OR condition remained and the AND condition was removed. 

I suspect that things like this were a concern with implementing this;>)

It will be only a matter of time before someone wants to be able to move conditions around. 

Still the editting of the multiple If conditions is minor compared to the overall improvement of having the feature.

Thanks!

[Scott Miller]

>when I delete the middle OR condition I expected that I would be left with the AND condition. However, the OR condition remained and the AND condition was removed. 
>

This makes perfect sense to me. It's evaluating the operator precedence rules to determine which to remove. The AND operator has a higher precedence than OR, and would have been evaluated first in the original statement. Removing one of the values from the AND portion naturally would also remove the AND operator. I'm not saying this is the right way, just that it makes sense.

[Rich D]

>
> One thing does not seem logical to me is what happens when you select "None" (delete) in a multiple condition. I created the condition below and when I delete the middle OR condition I expected that I would be left with the AND condition. However, the OR condition remained and the AND condition was removed. 

Would it make more sense to add a delete option to the condition operator menu to delete the entire statement.  That is what I tried first to remove the entire statement..

This would fix both mentioned issues...  

[Rich D]

> > One thing does not seem logical to me is what happens when you select "None" (delete) in a multiple condition. I created the condition below and when I delete the middle OR condition I expected that I would be left with the AND condition. However, the OR condition remained and the AND condition was removed. 
>
> Would it make more sense to add a delete option to the condition operator menu to delete the entire statement.  That is what I tried first to remove the entire statement..
>
> This would fix both mentioned issues...  

After another look that does not make sense as you could not delete the first statement....   :(

[Milan Roubal]

The problem with Galaxy Note 3 power status still remains in Tasker 4.3b8m. Detail description (copy from Tasker Beta 4.3b4+ thread)

Hi,
I have Galaxy Note 3 / Stock ROM   / Tasker  / Version: 4.3b8m / Android version 4.3. 
Connection to the wall shows Power Wireless same as connection to charging pad. I had before Tasker Version 4.3b3m and there it was vice versa - connection to wall and laying on chargin pad were showing Power AC. Attached please find the log file - First the phone was laying on wireless charger, that I have connected him to AC power and than I have connected him to USB power.

I don't have /sys/class/power_supply/

battery/charging_source file on my note 3, I have only file named /sys/class/power_supply/battery/batt_charging_source with this values:
1 = no chargin source
3 = USB wall AC
4 = computer USB
10 = Wireless
   Best Regards
   Milan

[Rich D]

A few more on the run log..

1. Open run log
2. Long press on a 'profile' item / edit
3. Tasker opens to profile in edit screen
4. Press back button
5. Tasker exits instead of returning to run log.

---------------------------

The help screen shows..
Pause/Play Button

The Pause/Play button toggles whether the list of entries updates live while the run log is being viewed. Some people find live updates to a log they are viewing disturbing.

This makes it sound like I should be able to press the button and toggle it at any time.

On my device I can not select the play or pause button (press on it and nothing happens) if I scroll all the way to the bottom the button will change to play and it will be live. If start Scrolling up the button will change to a pause and it will be paused. 

As I recall it has always been this way which makes perfect sense and in my opinion should stay like this. I do not think anyone would want a live log when viewing the history because it would always be jumping down to show the latest entry when the log changes..

Perhaps I am not reading the help entry correctly..

[UncleMike]

I found that setting the condition to 'none' that the condition is removed, but I think a more intuitive method or removal would be to have a 'minus' next to the condition.  This is in keeping with the 'plus' used to add a condition, as well as how the native People app allows removal of individual contact details.

BTW, speaking of unintuitive/missing removal methods, how do you remove individual actions within a Notify action?

[UncleMike]

Since space may be an issue, how about swiping them away like a notification?  I think this would be less intuitive than 'none', but I just thought I would throw it out there.

[UncleMike]

Still on the multiple If presentation...

What about indenting conditions and operators to indicate precedence, similar to how actions within an If are indented in the Task editor?

On Sunday, March 2, 2014 5:58:17 AM UTC-5, Pent wrote:

[Rich D]

The more I use the variable time context the more it seems there should be either a null value option or some sort of time delay for setting the variables for the context times. Here is one example..

Unless I am missing something.

To set the from and until times to the same value to achieve a event time context can not be done without activating the profile. If I set both variables to the same value "6.00" and the profile fires now when I go to change them to fire at "7.00" the instant I set  the 'from'  time variable the profile will fire as a state context. This does not happen every time. When running a test loop with just setting the context variables and writing the data to a file it failed 1 out of 9 times the data is attached.

The way I am currently handling this is to use a additional 'variable value' context to disable the profile then set the times then enable the profile by changing the that variable again

My first thought Would be to it make  a null value like zero to effectively disable the profile so you could set 'from' to 0 then set until to 7.00 then set 'from' to 7.00

Or make a small time delay before the settings activate to give time to set both.

Or something else????

This would also be very useful for the state context as well to disable the profile without the use of another context or throwing a error from a unset variable.

This profile sets the time variables to (current time + 2 minute) for a event context

Profile: Set Dynamic (321)
Time: Every 4m Till 23:59
Enter: Set Dynamic (327)
A1: Variable Set [ Name:%calc To:%TIMES+(2*60) Do Maths:On Append:Off ]
A2: Variable Convert [ Name:%calc Function:Seconds to Date Time Store Result In:%calc2 ]
A3: Variable Split [ Name:%calc2 Splitter: Delete Base:Off ]
A4: Variable Set [ Name:%Timetestoff To:%calc22 Do Maths:Off Append:Off ]
A5: Variable Set [ Name:%Timeteston To:%Timetestoff Do Maths:Off Append:Off ]
A6: Write File [ File:dynamic time test.txt Text:Time on %Timeteston ----- Time off %Timetestoff Append:On Add Newline:On ]

Profile: Dynamic Var (230)
Time: From %Timeteston Till %Timetestoff
Enter: Dynamic Var On (231)
A1: Flash [ Text:Dynamic on Long:Off ]
A2: Write File [ File:dynamic time test.txt Text:profille on--- %TIME Append:On Add Newline:On ]

Exit: Dynamic Off (300)
A1: Flash [ Text:Dynamic off Long:Off ]
A2: Write File [ File:dynamic time test.txt Text:profille off--- %TIME Append:On Add Newline:On ]

You can see in the attached screen shot it failed at 21.44

[Pent]

1. Open run log
2. Long press on item / edit
3. Tasker opens to edit view of item
4. Hit back button
5. Tasker returns to run log but to a seemingly random time below the previously selected item time.

I can't reproduce that. Could you give me more details ? What kind of item, name ID etc.

While testing I also saw this strange listing .. note the times in the screen shot..

The chronological order is reversed and  10.15.47 is out of place..

Don't suppose you can send me the relevant part of runlog.txt ? (or all of it if you like)

I suspect it's related to a previous bug where newlines in e.g. Cell Near descriptions were disrupting the file format.

Pent

[Pent]

I have Galaxy Note 3 / Stock ROM   / Tasker  / Version: 4.3b8m / Android version 4.3. 
Connection to the wall shows Power Wireless same as connection to charging pad. I had before Tasker Version 4.3b3m and there it was vice versa - connection to wall and laying on chargin pad were showing Power AC. Attached please find the log file - First the phone was laying on wireless charger, that I have connected him to AC power and than I have connected him to USB power.

Sorry, there's not  much log there, and nothing showing a change in profile state, just some task running. You need to send me more log.

Pent

[Pent]

1. Open run log
2. Long press on a 'profile' item / edit
3. Tasker opens to profile in edit screen
4. Press back button
5. Tasker exits instead of returning to run log.

Yes, I think from the main screen people expect to go out, and there's no 'profile edit screen'.
 

The help screen shows..
Pause/Play Button

The Pause/Play button toggles whether the list of entries updates live while the run log is being viewed. Some people find live updates to a log they are viewing disturbing.

This makes it sound like I should be able to press the button and toggle it at any time.

Yeah, completely wrong, I was thinking of the original implementation, thanks for mentioning.

Pent

[Pent]

Since space may be an issue, how about swiping them away like a notification?  I think this would be less intuitive than 'none', but I just thought I would throw it out there.

Space is definitely an issue, most devices are portrait. Swiping isn't going to work because most of the swipable but is
edittext which past experience shows don't work well with swiping.

Pent

[Pent]

What about indenting conditions and operators to indicate precedence, similar to how actions within an If are indented in the Task editor?

Operators are indented on my device. Could you double check that ? Indending conditions goes back to the space problem.

Maybe I should split the conditions onto two lines, then the indenting and the delete button would be possible. Think think.

Pent

[Pent]

The more I use the variable time context the more it seems there should be either a null value option or some sort of time delay for setting the variables for the context times. Here is one example..

Why not just disable the profile while you make your changes ?

Pent

[Milan Roubal]

Hi Pent,
first file: log power profile off send - All profiles disabled,
9:59 - wireless charging pad
10:00 - Power AC
10:01 - Power USB
second file: log power profile on send - 3 profiles enabled,
10:19 - wireless charging pad
10:20 - Power AC
10:21 - Power USB
third file: profiles - Definition of 3 profiles

10:19 - Active profile 19 - correct
10:20 - Active profile 19 - wrong, should be profile 29
10:21 - Active profile 65 - correct

If you need any more logs please specify which one.
   Thank you very much for help
   Milan

Dne pondělí, 3. března 2014 8:12:24 UTC+1 Pent napsal(a):

[Pent]

I went for a trash can on each line for the multi conditions. Trying to get the edit texts to wrap when they're full, but they're resisting.

Pent

[Pent]

I went for a trash can on each line for the multi conditions. Trying to get the edit texts to wrap when they're full, but they're resisting.

Yes, that feels a lot better. Added Xor too, so next update some bools will change, sorry about that.

Pent

[Pent]

To continue my monologue, will also add multi-conditions with the variable value, since the code can be easily shared.

The main point is to allow several variable value specifications for a profile while keeping within the 3-state-context-and-5-overall-contexts
profile limit.

I could relatively easily add an optional condition to every event and state, but decided it was getting too complex.

Pent

[Mike Yin]

data share not working on my Nexus 7(2013)

[Pent]

data share not working on my Nexus 7(2013)

What's 'data share' ?

Pent

[Mike Yin]

tasker data backup/restore/share option

[Joshua Watson]

Thanks for listening! Great work on this Pent.

[Pent]

>tasker data backup/restore/share option

OK, what do you mean by 'not working' ? Does anything happen, if so what ?

Pent

[Mike Yin]

nothing happened after clicking share option,but it's working on my ole Nexus S.

[Pent]

nothing happened after clicking share option,but it's working on my ole Nexus S.

Perhaps you have nothing installed that listens for the share intent.

I'll add a check with a warning for that case.

Pent

[Rich D]

> I can't reproduce that. Could you give me more details ? What kind of item, name ID etc.

1. Open run log
2. Screen is centered on action 16.40.02 - 390.1 destroy scene / long press this action  / edit
3. Tasker opens to edit view of correct task 'phone any on'
4. Hit back button
5. Tasker returns to run log but centered on  a seemingly random time below the previously selected item time. 16,45.43  new time sheet /action / variable section

I have attached screen shots of #2,#3,#5 as well as the entire run log..

>
>

While testing I also saw this strange listing .. note the times in the screen shot, the chronological order is wrong.

> Don't suppose you can send me the relevant part of runlog.txt ? (or all of it if you like)

This is in the same run log at time - 16.46.10. Again the screen shot is attached as well

[Rich D]

>> The more I use the variable time context the more it seems there should be either a null value option or some sort of time delay for setting the variables for the context times. Here is one example..
>
>
> Why not just disable the profile while you make your changes ?
>

Oh... that works...  I guess I have always avoided the disable/ enable profile because it seemed to be kind of resource intensive..  If I have the availability ( have not used the max# of contexts) is it better to do this with a additional context or disable/enable or does it not matter?

[Michael Starks]

On 03/02/2014 04:23 AM, Pent wrote:
> http://tasker.dinglisch.net/beta.html
>
> No more features going in after this one, just bug fixes.
>
> Pent

Notify LED is still broken on the Nexus 5.

[Pent]

> Why not just disable the profile while you make your changes ?
>

Oh... that works... 

I've added the situation you described to the userguide as a warning, with a suggestion to disable before changing.
 

I guess I have always avoided the disable/ enable profile because it seemed to be kind of resource intensive..  If I have the availability ( have not used the max# of contexts) is it better to do this with a additional context or disable/enable or does it not matter?

Disable/enable is better. An extra context is an extra context that needs to be checked in several situations.

Pent

[Pent]

Notify LED is still broken on the Nexus 5.

Works fine on mine (stock 4.4.2).

Screen must be off when the action is executed as described in help text.

Pent

[Pent]

1. Open run log
2. Screen is centered on action 16.40.02 - 390.1 destroy scene / long press this action  / edit
3. Tasker opens to edit view of correct task 'phone any on'
4. Hit back button
5. Tasker returns to run log but centered on  a seemingly random time below the previously selected item time. 16,45.43  new time sheet

I created a task with the same ID and name and loaded your Run Log but still couldn't reproduce.

I've added a load of logging, could you send me an SD log after the next update (of the time when using the run log goes wrong, not when the original task ran). Thanks!

While testing I also saw this strange listing .. note the times in the screen shot, the chronological order is wrong.

> Don't suppose you can send me the relevant part of runlog.txt ? (or all of it if you like)

This is in the same run log at time - 16.46.10. Again the screen shot is attached as well

Sorry, I didn't get that. The runlog.txt you sent me ended at 16.46.10 and was only from 16.28. I didn't see any out-of-order entries
except these ones (also wrong in the file):

20140303 16.45.21 E Stop     ID0:0.0  TaskService
20140303 16.45.20 P Inactive ID389    Phone Any
20140303 16.45.20 P Instant  ID517    Phone Idle
20140303 16.45.20 E Start    ID0:0.0  TaskService
20140303 16.45.21 T Running  ID161    Phone Any Off
20140303 16.45.21 A OK       ID161.1  Phone Any Off.Variable Set

Which I can't imagine how that happened after a check of the code.

Pent

[Manu Pinazo]

I know you said no more features in this release, but I don't really see the point of the %priority var if you can't specify a variable in the priority field in "perform action" ;-)

Loving the "multiple if's" feature BTW, good work!

[Chris Heddleson]

The new beta wouldn't install over 4.3b7, so I uninstalled to upgrade to to b8 (after doing a manual backup).  The problem I have now is that the new beta is not validating my purchase (bought Jan 27 through the Google play store), and it will not allow me to restore the backup and is telling me on the validation page that this is the 7 day trial.  Is there someway I can resolve this?

[Marta Hintz]

Almost sounds like you choose the wrong beta. You need the one from play store column maybe?

[Pent]

I know you said no more features in this release, but I don't really see the point of the %priority var if you can't specify a variable in the priority field in "perform action" ;-)

Deselect prefs / ui / beginner mode, then you click the cross arrows to enter a variable in the Perform Task action.

Pent

[Pent]

The new beta wouldn't install over 4.3b7, so I uninstalled to upgrade to to b8 (after doing a manual backup).  The problem I have now is that the new beta is not validating my purchase (bought Jan 27 through the Google play store), and it will not allow me to restore the backup and is telling me on the validation page that this is the 7 day trial.  Is there someway I can resolve this?

As the beta page says, you should install it only over an already-validated stable release.

And make sure you are trying to install the Play Store beta.

Pent

[Daniel Söderlund]

Hello 

in my eyes this is a bug.

I have activated Lock Code, when you start the application and you left it in a task or any other place except the main screen you don't have to enter the code. 

When you get the prompt for entering the lock code the keyboard are not shown, I have to press the input filed to get the keyboard.

I have a Nexus 5, standard ROM(ROOTED) and standard keyboard. 

KR

Daniel

[Michael Starks]

I also have a stock N5. I created a task to wait 5 seconds, then illuminate the LED. This gives me time to turn the screen off. It just doesn't work no matter how I test it or try to use it normally. Light Flow does work. I would be happy to send you some debug logs if you like. 

[UncleMike]

The operators are definitely indented here.

On Monday, March 3, 2014 2:20:17 AM UTC-5, Pent wrote:

What about indenting conditions and operators to indicate precedence, similar to how actions within an If are indented in the Task editor?

Operators are indented on my device. Could you double check that ? Indending conditions goes back to the space problem.

Maybe I should split the conditions onto two lines, then the indenting and the delete button would be possible. Think think.

Pent

[Pent]

in my eyes this is a bug.

I have activated Lock Code, when you start the application and you left it in a task or any other place except the main screen you don't have to enter the code. 

I don't view that as a bug.
 

When you get the prompt for entering the lock code the keyboard are not shown, I have to press the input filed to get the keyboard.

Will look at that.

Pent

[Pent]

Works fine on mine (stock 4.4.2).

Screen must be off when the action is executed as described in help text.

I also have a stock N5. I created a task to wait 5 seconds, then illuminate the LED. This gives me time to turn the screen off. It just doesn't work no matter how I test it or try to use it normally. Light Flow does work. I would be happy to send you some debug logs if you like. 

That's exactly how I test it and it does work... Does the notification show up ? Tried different colours ? Entered text and title ? Different priorities (I only tried 3 and rate 500).

Maybe you've disabled notifications for Tasker in Android settings ? Maybe you have some other app blocking it ? Light Flow ?

Pent

[Pent]

The operators are definitely indented here.

Then I'm lost as to why you suggested indenting them in your first post on the subject ?

Pent

[Manu Pinazo]

I'm pretty sure the crossed arrows weren't there this morning, maybe I just need glasses... thanks!

[Michael Starks]

Well, what do ya know--it was a conflict with Light Flow. It doesn't work even when you go into the Light Flow settings and disable it, but if I force-stop Light Flow, then Tasker LED works. I could have sworn that I installed Light Flow because I couldn't get Tasker to work, but I guess that doesn't matter now. Sorry for the noise.

[Daniel Söderlund]

Den tisdagen den 4:e mars 2014 kl. 18:13:05 UTC+1 skrev Pent:

in my eyes this is a bug.

I have activated Lock Code, when you start the application and you left it in a task or any other place except the main screen you don't have to enter the code. 

I don't view that as a bug.

Okay, just my thought :) I need to remember to back out of the app 

 

 

When you get the prompt for entering the lock code the keyboard are not shown, I have to press the input filed to get the keyboard.

Will look at that.

Pent

 Okay thanks :) 

PS I guess alot of ppl has asked you to why you not use google app beta feature?  Ds

[Pent]

PS I guess alot of ppl has asked you to why you not use google app beta feature?  Ds

It's come up before, a search might bring it up.

Pent

[Pent]

The problem with Galaxy Note 3 power status still remains in Tasker 4.3b8m. Detail description (copy from Tasker Beta 4.3b4+ thread)

Thanks for you efforts, unfortunately I need some more info and have added some more debugging code. Could you make another log after the next update ?

I don't need three logs, just a connect and disconnect of each type.

Thanks,

Pent

[Chris Heddleson]

Thanks, got it working right this time.  That's what I get for assuming I know what I'm doing. 

[Milan Roubal]

Yes, no problem. Waiting for Tasker 4.3b9m. Today I have received update to Kitkat 4.4.2, behavior remains unchanged.

Dne středa, 5. března 2014 11:22:30 UTC+1 Pent napsal(a):

[Pent]

Yes, no problem. Waiting for Tasker 4.3b9m.

Thanks, today or tomorrow I think.

Looking at the code, you might also have been having problems with sensor activation when display off.

Pent

[legaldeejay]

Hi . I am having a problem exporting profiles. They all have names and beginner mode is disabled. When I long press on a profile heading, I am able to choose to export, but error messages appear saying they cannot be exported because only named profiles can be exported. But as I said, all my profiles are named. Please help.

[Bob Hansen]

It is very likely your profile is not named and you are seeing Tasker's profile description. Long press on the profile then select the A icon. Enter a name.

I would also suggest that you go into Tasker;s menu and enable "Ask for new profile name".

Menu > Preferences > UI tab > scroll down to  "Ask for new profile name" and check it.

[legaldeejay]

That was it Bob, thanks. I think what I was doing was renaming the descriptions. On the Profile screen, I would tap the Profile heading/description, and then it would show the description on the left in smaller print with a half filled circle, and on the right would be the associated tasks. Then, when I long press the description, there is an option to rename. Then I go back to long press the larger heading, choose export, but that error came up.

[Tobias Hau]

Hey Pent! Have found a bug in beta8

When I plug out power this profile no longer work: http://tasker.wikidot.com/bluetooth-auto-turn-off

It shuts off directly bluetooth and wlan is shut off also.

With beta7 no problem.

Perhabs you can look at it?

Am Sonntag, 2. März 2014 11:23:37 UTC+1 schrieb Pent:

http://tasker.dinglisch.net/beta.html

No more features going in after this one, just bug fixes.

Pent

[Paul [sabret00the]]

As has already been reported, share isn't working. I wanted to share my backup to my Dropbox and nothing happened.

Also for the "and" condition, any chance of a double ampersand && along with a double pipe for "or" condition ||?

I know it's only a nitpick, but it's how I learned how to read code, so I thought it was worth an ask.

[Pent]

On Friday, 7 March 2014 01:47:59 UTC+1, Paul [sabret00the] wrote:

As has already been reported, share isn't working. I wanted to share my backup to my Dropbox and nothing happened.

That wasn't clear if you're not getting *any* suggested apps for sharing or just not getting dropbox.

I'm using a pretty basic intent usage, it's well documented.

For the next update I'll try adding a chooser, I guess it's possible that you've already set a default for sharing text/*

Also for the "and" condition, any chance of a double ampersand && along with a double pipe for "or" condition ||?

No, I want to keep it less voodoo for non-programmers.

Pent

[Pent]

b9 is out.

Could be I accidentally added some things even though I said I wouldn't.

Pent

• added: developers: support String [] in values of TaskerPlugin.addVariableBundle()
• added: action edit: search menu option
• added: developers: support for ArrayList in plugin data bundles and TaskerPlugin.addVariableBundle()
• added: state Variable Value: multi conditions
• beta: change: Share: wrap intent in chooser
• beta: added: trash button for multi conditions
• beta: added: state Variable Value: multi-condition
• beta: change: multi-conditions: tight binding -> high precedence
• beta: change: multi-conditions: better horizontal compaction of boolean buttons to fit more levels
• beta: bugfix: multi-conditions: unary operators weren't hiding RHS for already existing condition
• beta: multi-conditions: various small problems and improvements
• beta: bugfix: Share: when no apps found to handle the intent, say that
• bugfix: UI lock wasn't bringing up keyboard automatically
• bugfix: changing array index wasn't triggering array change in some situations
• change: removed None operator in conditions, default to Matches
• beta: bugfix: handle Note 3 battery intent format also for internal determination of whether charging

[Tobias Hau]

Sorry to distrubt again but bluetooth toggle like I posted before doesn't work with b9 also...

[Pent]

When I plug out power this profile no longer work: http://tasker.wikidot.com/bluetooth-auto-turn-off

It shuts off directly bluetooth and wlan is shut off also.

With beta7 no problem.

Which part no longer works ?

Check in Menu / More / Run Log what's going on.

Pent

[Tobias Hau]

I can reproduce the problem when I make this:

Turn bluetooth on if %BLUE !~ on
Wait 3 sec
Turn bluetooth off if %BLUE !~ off

Then I lose wlan and bluetooth connectivity.

In the sample above bluetooth keeps strungelin on and off

It doesn't wait for the check. I think it has to do with the blue variable.

[Pent]

Just running that task from the action edit screen, otherwise what are the profile conditions ?

Pent

[Milan Roubal]

Dear Pent,
here is the log from the new beta regarding the Wireless Power Charging on Galaxy Note 3.

Wireless charger
07-03-2014 Log: 11.52.01#Log: cps
07-03-2014 : 11.52.01#:     technology / Li-ion (java.lang.String)
07-03-2014 : 11.52.01#:     icon-small / 17303409 (java.lang.Integer)
07-03-2014 : 11.52.01#:     health / 2 (java.lang.Integer)
07-03-2014 : 11.52.01#:     online / 10 (java.lang.Integer)
07-03-2014 : 11.52.01#:     status / 2 (java.lang.Integer)
07-03-2014 : 11.52.01#:     plugged / 4 (java.lang.Integer)
07-03-2014 : 11.52.01#:     present / true (java.lang.Boolean)
07-03-2014 : 11.52.01#:     level / 67 (java.lang.Integer)
07-03-2014 : 11.52.01#:     scale / 100 (java.lang.Integer)
07-03-2014 : 11.52.01#:     temperature / 317 (java.lang.Integer)
07-03-2014 : 11.52.01#:     current_avg / 640 (java.lang.Integer)
07-03-2014 : 11.52.01#:     voltage / 3978 (java.lang.Integer)
07-03-2014 : 11.52.01#:     charge_type / 1 (java.lang.Integer)
07-03-2014 : 11.52.01#:     invalid_charger / 0 (java.lang.Integer)
AC charger
07-03-2014 : 11.53.04#:     technology / Li-ion (java.lang.String)
07-03-2014 : 11.53.04#:     icon-small / 17303409 (java.lang.Integer)
07-03-2014 : 11.53.04#:     health / 2 (java.lang.Integer)
07-03-2014 : 11.53.04#:     online / 3 (java.lang.Integer)
07-03-2014 : 11.53.04#:     status / 2 (java.lang.Integer)
07-03-2014 : 11.53.04#:     plugged / 1 (java.lang.Integer)
07-03-2014 : 11.53.04#:     present / true (java.lang.Boolean)
07-03-2014 : 11.53.04#:     level / 67 (java.lang.Integer)
07-03-2014 : 11.53.04#:     scale / 100 (java.lang.Integer)
07-03-2014 : 11.53.04#:     temperature / 320 (java.lang.Integer)
07-03-2014 : 11.53.04#:     current_avg / 1200 (java.lang.Integer)
07-03-2014 : 11.53.04#:     voltage / 4048 (java.lang.Integer)
07-03-2014 : 11.53.04#:     charge_type / 1 (java.lang.Integer)
07-03-2014 : 11.53.04#:     invalid_charger / 0 (java.lang.Integer)
USB charger
07-03-2014 : 11.54.07#:     technology / Li-ion (java.lang.String)
07-03-2014 : 11.54.07#:     icon-small / 17303409 (java.lang.Integer)
07-03-2014 : 11.54.07#:     health / 2 (java.lang.Integer)
07-03-2014 : 11.54.07#:     online / 4 (java.lang.Integer)
07-03-2014 : 11.54.07#:     status / 2 (java.lang.Integer)
07-03-2014 : 11.54.07#:     plugged / 2 (java.lang.Integer)
07-03-2014 : 11.54.07#:     present / true (java.lang.Boolean)
07-03-2014 : 11.54.07#:     level / 67 (java.lang.Integer)
07-03-2014 : 11.54.07#:     scale / 100 (java.lang.Integer)
07-03-2014 : 11.54.07#:     temperature / 320 (java.lang.Integer)
07-03-2014 : 11.54.07#:     current_avg / 450 (java.lang.Integer)
07-03-2014 : 11.54.07#:     voltage / 3901 (java.lang.Integer)
07-03-2014 : 11.54.07#:     charge_type / 1 (java.lang.Integer)
07-03-2014 : 11.54.07#:     invalid_charger / 0 (java.lang.Integer)

Thank you
   Best Regards
   Milan

Dne pátek, 7. března 2014 9:16:22 UTC+1 Pent napsal(a):

[Tobias Hau]

Just try this with b8 or b9 -> http://tasker.wikidot.com/bluetooth-auto-turn-off

It doesn't work anymore. It keeps jumping directly on and off with the bluetooth unless the wait period in it.

I think it must have something to do with the %BLUE variable...

Sorry for my bad english...

[Paul [sabret00the]]

On B9, attempting to share data results in a crash.

[Pent]

here is the log from the new beta regarding the Wireless Power Charging on Galaxy Note 3.

I'm getting a bit sick of Samsung.

In the previous log I saw (Android 4.3) they were setting 'plugged' to 0 or 1
(connected or not) and 'charge_type' to the type of charge.

In the log here (4.4.2) they're apparently using 'charge_type' to indicate whether it's
connected, and 'plugged' for the type of charge.

And the values don't match what they were before either.

I guess I'll try to differentiate based on the OS version. Sheeshk.

Pent

[Pent]

According to those values, they're back to matching standard Android with version 4.4.2 except
for the extra charge_type field which I'll ignore.

Pent

[Tobias Hau]

Sorry Pent! Now it works. Don't know what it was but after delete an start new it works! Thx!

[Pent]

On B9, attempting to share data results in a crash.

Well I can catch the exception, but I don't know why you apparently have no apps installed
that can handle text/*

Could you send me an SD log next update ?

Thanks,

Pent

[Bob Hansen]

I also now get a crash when using Menu > Data > Share. On B7 when attempting to use Share it didn't crash but it also didn't open anything. I have many apps that handle text yet none were shown. I didn't, however, have one set as default. I set 920 Text Editor as the default and tried again but still crashed. I also have several sharing apps installed.

What app(s) should work?

Droid RAZR HD 4.1.2 stock rooted

[Bob Hansen]

I noticed that my profile to read incoming email had stopped working and installed B8 over B9. After installing B8 Tasker went into a loop of starting, crashing and restarting. Had to reinstall B9. 

I was going to confirm that the email notifications not being read by Tasker was related to the B9 and not something else - although nothing else was changed and Tasker was reading the emails fine immediately before the update to B9. It appears Tasker is no longer triggering on the email (gmail app) notification.

[Bob Hansen]

Murphy's Law is alive and well. 

After sending the above post I get an email notification from the group and Tasker reads it. So forget the email notification problem.

The inability to restore to a previous version, I think is a problem.

[Milan Roubal]

I have got also crash,
here is the logfile.

07-03-2014 MAS: 15.49.55#MAS: java.lang.NullPointerException
07-03-2014 MAS: 15.49.55#MAS: getTargetPack: failed
07-03-2014 MAS: 15.49.55#MAS: xxx:targetpackage
07-03-2014 MAS: 15.49.55#MAS: use first text for notification title
07-03-2014 MyPM: 15.49.55#MyPM: getApplicationInfo: android.content.pm.PackageManager$NameNotFoundException:
07-03-2014 : 15.49.55#: android.app.ApplicationPackageManager.getApplicationInfo(ApplicationPackageManager.java:249)
07-03-2014 : 15.49.55#: net.dinglisch.android.taskerm.sb.e(Unknown Source)
07-03-2014 : 15.49.55#: net.dinglisch.android.taskerm.sb.f(Unknown Source)
07-03-2014 : 15.49.55#: net.dinglisch.android.taskerm.MonitorService.a(Unknown Source)
07-03-2014 : 15.49.55#: net.dinglisch.android.taskerm.MonitorService.b(Unknown Source)
07-03-2014 : 15.49.55#: net.dinglisch.android.taskerm.MonitorService.i(Unknown Source)

Best Regards
  Milan

Dne pátek, 7. března 2014 14:59:29 UTC+1 Pent napsal(a):

[Pent]

I also now get a crash when using Menu > Data > Share. On B7 when attempting to use Share it didn't crash but it also didn't open anything. I have many apps that handle text yet none were shown. I didn't, however, have one set as default. I set 920 Text Editor as the default and tried again but still crashed. I also have several sharing apps installed.

What app(s) should work?

When I do it, I get a choice of Bluetooth, Email or Hangouts (SMS).

Pent

[Pent]

On B9, attempting to share data results in a crash.

Which Android version ?

Thanks,

Pent

[Pent]

After sending the above post I get an email notification from the group and Tasker reads it. So forget the email notification problem.

The inability to restore to a previous version, I think is a problem.

Tasker has never been compatible that way.

In b9, there's a new data format to handle the multi-condition for the Variable Value state, b8 won't understand
it. Disappointing that it crashes, I agree.

Pent

[Bob Hansen]

4.1.2 stock rooted Droid RAZR HD.

[Pent]

I have got also crash,

From what ?
 

here is the logfile.

07-03-2014 MAS: 15.49.55#MAS: java.lang.NullPointerException
07-03-2014 MAS: 15.49.55#MAS: getTargetPack: failed
07-03-2014 MAS: 15.49.55#MAS: xxx:targetpackage
07-03-2014 MAS: 15.49.55#MAS: use first text for notification title
07-03-2014 MyPM: 15.49.55#MyPM: getApplicationInfo: android.content.pm.PackageManager$NameNotFoundException:
07-03-2014 : 15.49.55#: android.app.ApplicationPackageManager.getApplicationInfo(ApplicationPackageManager.java:249)
07-03-2014 : 15.49.55#: net.dinglisch.android.taskerm.sb.e(Unknown Source)
07-03-2014 : 15.49.55#: net.dinglisch.android.taskerm.sb.f(Unknown Source)
07-03-2014 : 15.49.55#: net.dinglisch.android.taskerm.MonitorService.a(Unknown Source)
07-03-2014 : 15.49.55#: net.dinglisch.android.taskerm.MonitorService.b(Unknown Source)
07-03-2014 : 15.49.55#: net.dinglisch.android.taskerm.MonitorService.i(Unknown Source)

That's not a crash, it's just logging that it *would* have crashed if it hadn't caught the exception from Android.

Pent

[Pent]

>4.1.2 stock rooted Droid RAZR HD.

I saw yours already, I was trying to get Paul's to compare :-)

Pent

[Milan Roubal]

attempting to share data results in a crash. Blue screen, application just closes and then restarts and run all active profiles. Compared to other applications in it NOT writing that Application has stopped.

Android 4.4.2, Galaxy Note 3.

Dne pátek, 7. března 2014 16:39:09 UTC+1 Pent napsal(a):

[Pent]

attempting to share data results in a crash.

Does it show you some options first ?
 

Blue screen, application just closes and then restarts and run all active profiles. Compared to other applications in it NOT writing that Application has stopped.

Hmm, interesting.

I thought this would be a trivial function to implement :-)

Pent

[Milan Roubal]

No, no options shown.

Now something even generated crash.txt, I have attached it.


Dne pátek, 7. března 2014 16:51:51 UTC+1 Pent napsal(a):

[Pent]

Now something even generated crash.txt, I have attached it.

I guess you have a large amount of profiles etc defined ? Probably that's
also the case for the other 2 people with problems.

Could you try:

- Menu / Data / Backup
- Menu / Data / Clear
- exit Tasker via Back
- return to Tasker
- Menu / Data / Share

Thanks,

Pent