Tasker Beta 5.1.4b

[joaomgcd]

New Beta is out! I'm dipping my toes in making small changes to Tasker so bear with me :)

Here's the changelog for this release.

• Moved to runtime permissions (Android 6+). Will now ask for needed permissions when your Tasker data is saved (main app tick or backing out of Tasker).
• manifest permission WRITE_SECURE_SETTINGS: enable via adb command - adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS
• action Input/Lock Screen (Android P+)
• action Input/System Screenshot (Android P+)

To remind everyone:

• I'll be using Google Play Beta publishing from now on, so please sign up for it here if you're interested: https://play.google.com/apps/testing/net.dinglisch.android.taskerm
• By signing up to the beta you'll get beta releases whenever they're available on Google Play. No more manual downloading.
• For now, app factory betas still have to be downloaded manually. Get this version here: http://appfactory.dinglisch.net/releases/AppFactory.5.1.4b.apk

Let me know how this works! :)

[Peter Bongé]

This version crashes as soon as I hit the back or home key to exit it. System crash report just sent.

[Peter Bongé]

Here is the crash log:

13.25

Attempt to invoke virtual method 'java.lang.String java.lang.String.replaceFirst(java.lang.String, java.lang.String)' on a null object reference

net.dinglisch.android.taskerm.bo.a(Unknown Source:15)

net.dinglisch.android.taskerm.Main.a(Unknown Source:32)

net.dinglisch.android.taskerm.Main.aU(Unknown Source:81)

net.dinglisch.android.taskerm.Main.b(Unknown Source:240)

net.dinglisch.android.taskerm.Main.onBackPressed(Unknown Source:3)

android.app.Activity.onKeyUp(Activity.java:2976)

[joaomgcd]

Thank you. Does that happen every single time? Or just sometimes?

[Peter Bongé]

Every single time. And after some time it seems to start in the background. I can see the notification icon re-appearing.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/WhfQuCm3t5g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[João Dias]

Is every Tasker requested permission granted when you check Tasker permissions in the Android settings?

To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/WhfQuCm3t5g/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.

[Peter Bongé]

Yes.

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/WhfQuCm3t5g/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/WhfQuCm3t5g/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[joaomgcd]

Ok, found the issue. Update coming up.

[joaomgcd]

Ok, pushed fix to Google Play now. Hopefully that fixes it.

[Peter Bongé]

Tasker doesn't crash anymore, but now I get a message about missing permissions for:

- (auto) brightness settings

- display timeout

- notification pulse

And it doesn't make a difference whether I click on OK or Cancel. So the dialog isn't really helpful.

I have granted all permissions (except the new ADB thing) and all worked fine before!

And plugins doesn't seem to work correctly anymore. I have some tasks with AutoTools dialogs and clicking on anything doesn't work anymore. The task just doesn't continue.

[João Dias]

Thanks again.

Those permissions don't seem to be part of the regular permissions so they can not be accepted by I user. I have to stop requesting them.

About the plugins, fix incoming thanks again.

[Peter Bongé]

I forgot: The action "Notification Pulse" gives me the error "You cannot change private secure settings", but it worked before.

--

[joaomgcd]

I forgot: The action "Notification Pulse" gives me the error "You cannot change private secure settings", but it worked before.

Hmm, it seems that if I target Android M or above it seems that setting is considered private and cannot be changed anymore :(

[Peter Bongé]

I'm a little bit confused. I just wanted to answer your last post, but you deleted it...

[João Dias]

Sorry about that. I deleted because I published the update to Google Play and I got the response from another user :) Forgot to mention here sorry.

--

You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/WhfQuCm3t5g/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.

[Nuno Guerreiro]

Still having this problem:

Some months ago everything was running fine. I had a couple of profiles that were SSID dependent. After a while, think around 8.1 devs for my nexus, no more those tasks would run again. Only if I take SSID specific name, the profile it will work again. This is my solution for now, until a fix is released!! In order to my profile run again I have to remove the SSID from the wifi profile, but now I only have one profile for home and work which is bad.

Any ideas when it can be fixed?

Also, android tells me that Tasker is using battery on the notifications. In reallity it isn't... is there something that can be made to not be displayed that?? A few months ago I had a Nexus 6P and in 8.1 didn't show that notification. Since I change to a OG Pixel XL, I have that notification all the time...

Thkx in advance.

[João Dias]

Still having this problem:

Some months ago everything was running fine. I had a couple of profiles that were SSID dependent. After a while, think around 8.1 devs for my nexus, no more those tasks would run again. Only if I take SSID specific name, the profile it will work again. This is my solution for now, until a fix is released!! In order to my profile run again I have to remove the SSID from the wifi profile, but now I only have one profile for home and work which is bad.

So to clarify, if you use an SSID it'll not work but if you use no SSID at all it works?

 

Also, android tells me that Tasker is using battery on the notifications. In reallity it isn't... is there something that can be made to not be displayed that?? A few months ago I had a Nexus 6P and in 8.1 didn't show that notification. Since I change to a OG Pixel XL, I have that notification all the time...

 

Funny you should ask :D Check this out! Released today exactly for that purpose!

[Peter Bongé]

OK.

And what about the "Notification Pulse" problem?

What's the benefit of targeting Android M or above? Maybe it broke other things, too?

Am Donnerstag, 15. März 2018 18:11:36 UTC+1 schrieb joaomgcd:

Sorry about that. I deleted because I published the update to Google Play and I got the response from another user :) Forgot to mention here sorry.

On Thu, Mar 15, 2018 at 5:02 PM, Peter Bongé <peter...@gmail.com> wrote:

I'm a little bit confused. I just wanted to answer your last post, but you deleted it...

Am Donnerstag, 15. März 2018 15:45:22 UTC+1 schrieb joaomgcd:

I forgot: The action "Notification Pulse" gives me the error "You cannot change private secure settings", but it worked before.

Hmm, it seems that if I target Android M or above it seems that setting is considered private and cannot be changed anymore :(

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/WhfQuCm3t5g/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[joaomgcd]

OK.

And what about the "Notification Pulse" problem?

What's the benefit of targeting Android M or above? Maybe it broke other things, too?

There's no apparent benefit, but I'm forced to do so. At the end of the year all apps will have to target Android Oreo or above or else they can't post updates :( Sorry! 

[Peter Bongé]

OK, but then the option needs to be removed or marked as "root only", I think.

--

[Rich D]

I had installed 5.5.3b.bf and all seemed good. I just installed Version: 5.1.4b.bf3 and now get the the attached dialog everytime when I go to exit tasker. There does not seem to be a way to grant this permission .

I have a 'stock' pixel c tablet  /  Android 8.0 

[João Dias]

OK, but then the option needs to be removed or marked as "root only", I think.

Yes, that it does. Thanks  

[João Dias]

I had installed 5.5.3b.bf and all seemed good. I just installed Version: 5.1.4b.bf3 and now get the the attached dialog everytime when I go to exit tasker. There does not seem to be a way to grant this permission .

I have a 'stock' pixel c tablet  /  Android 8.0 

 Thank you. Fixed for next release.

[Gerard Gil Bragais]

Hi,

I have Tasker Version: 5.1.4b.bf3 and I can't seem to find these new actions:
* action Input/Lock Screen (Android P+)
* action Input/System Screenshot (Android P+)

Do I need to install a different verion to get this? I am a beta tester but is this the correct version?

[joaomgcd]

Just to confirm, you are running Android P? 

[Gilles P]

• manifest permission WRITE_SECURE_SETTINGS: enable via adb command - adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS

Could someone give a working sample of how to use this new feature to change any system/secure/global setting in plain Tasker?

(I'm currently using different methods do do this because I found none which works for every settings I need)

[Nuno Guerreiro]

Yep, that's right.

If I use a specific SSID on the State edit on Wifi Connected, my profile doesn't work. This start to happen after Android 8.1 (If I can remember). Now, in order to work, I can't have any specific SSID on the Wifi Connected State. I see more people complaining here https://groups.google.com/forum/#!topic/tasker/a1Hp-UI1-Oc

This used to work just fine. I had two profiles for this, on when I was at work and another at home... now I have to use the same for everywhere I connect to wifi...

[Gerard Gil Bragais]

Nevermine, my bad. I missed that this is only for Android P.

[1337 357]

Refer to this XDA thread, currently it requires a custom Java Function:

https://www.xda-developers.com/tasker-beta-secure-settings-permission-lock-screen-screenshot-action-android-p/

[Roger Mitchell]

I am getting a prompt saying Notification access service is disabled when it is not.  This is preventing do not disturb modes from changing

07.40.55/NSI return last filter: -1

07.40.55/E cur mode: unknown wanted: priority

07.40.55/NSI no service interface, notification access service enabled in Android settings ?

07.40.55/E result: stop task (error)

07.40.55/E Error: 1

07.40.55/MacroEdit action finished exeID 1 action no 0 code 312 status: Err next 0 

[Gilles P]

Refer to this XDA thread, currently it requires a custom Java Function:

https://www.xda-developers.com/tasker-beta-secure-settings-permission-lock-screen-screenshot-action-android-p/

Yes, I was aware this require a Java function (I already read that thread BTW). It is a working sample implementation (Tasker task) I was looking for and there are none in that thread (the two screenshots are incomplete)

Anyway, I think I'll manage to use the same code provided there replacing %par1 by %launch_data

[Sơn Minh]

Hi pro, I created a scene overplay to open a scenes activity containing a textedit. But every time I hit the home button, the scenes activity was exited and could not be opened again by the scenes overplay. So how to restore the scenes activity after pressing the home key.
thanks for reading

[Rich D]

 So how to restore the scenes activity after pressing the home key.

you can either 'Destroy' or 'Hide' the scene first. 

[Keir Stiegler]

Has anyone been able to modify adaptive brightness levels with Java on the new beta? I've granted the ADB permission and the task runs correctly but there is no effect from the Java action that changed the brightness level in the pre-beta release. Here are the task details (also attached): https://docs.google.com/document/d/1NgAYfrpqN9K6eGkpdgZNgCeAZTQT6JN73HK1jubxDf8/edit?usp=sharing 

I can provide more logs if needed.

(I deleted my previous post because I'd accidentally quoted the entire OP...)

[Sơn Minh]

I created app by Tasker app factory. 

Vào 18 thg 3, 2018 18:49, "Rich D" <ricp...@gmail.com> đã viết:

 So how to restore the scenes activity after pressing the home key.

you can either 'Destroy' or 'Hide' the scene first. 

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

[Sơn Minh]

When i press  home scene hidden , can not open scene how to ? Please 

Vào 19 thg 3, 2018 04:26, "Sơn Minh" <duongmi...@gmail.com> đã viết:

[Rich D]

When i press  home scene hidden , can not open scene how to ? Please 

Does it work as you expect in tasker before you export to app?

Could you give more details?

To post your profile or task here...  Long press on the profile or task name / ( 3 dot menu with 4.0+ ) export / export "DESCRIPTION" to clipboard (not XML)

Any linked tasks will be exported with the profile they are linked to..

To be able to export, The beginner mode needs to be off and the profile needs to be named by you (Not the Tasker listed name.  Tasker will list your profile with the context name if you have not given it one).

[Sơn Minh]

It works great on the tasker but can not work after exported

Vào 19 thg 3, 2018 04:46, "Rich D" <ricp...@gmail.com> đã viết:

[phobiac]

I'm on 5.1.4b.bf3 and the %INTERRUPT variable doesn't seem to work. I have a few profiles that use it to check do not disturb state and using a test task that just flashes the value of %INTERRUPT it responds with "%INTERRUPT", as if the variable isn't being seen as a variable at all.

[joaomgcd]

Yep, that's right.

If I use a specific SSID on the State edit on Wifi Connected, my profile doesn't work. This start to happen after Android 8.1 (If I can remember). Now, in order to work, I can't have any specific SSID on the Wifi Connected State. I see more people complaining here https://groups.google.com/forum/#!topic/tasker/a1Hp-UI1-Oc

This used to work just fine. I had two profiles for this, on when I was at work and another at home... now I have to use the same for everywhere I connect to wifi...

Very weird. It still works for me with no issues :/

Can you please export your profile's description (not xml) so I can take a look? Long-click the profile in Tasker->export description Thanks in advance

 

Can you try rebooting and see if that fixes it? 

On that XDA post you have an example:

cr = CONTEXT.getContentResolver(); 

Secure.putString(cr, sysui_nav_bar, space,recent;home;back,menu_ime) 

 Can you try with putString instead? I really need to create an action to make this easier I see :)

On Monday, March 19, 2018 at 11:14:04 AM UTC, phobiac wrote:

I'm on 5.1.4b.bf3 and the %INTERRUPT variable doesn't seem to work. I have a few profiles that use it to check do not disturb state and using a test task that just flashes the value of %INTERRUPT it responds with "%INTERRUPT", as if the variable isn't being seen as a variable at all.

Can you check if the notification service is running? If it is, try rebooting. The service is maybe in a "stuck" state. Thanks!

[Gilles P]

On Friday, March 16, 2018 at 4:59:49 PM UTC, Gilles P wrote:

Refer to this XDA thread, currently it requires a custom Java Function:

https://www.xda-developers.com/tasker-beta-secure-settings-permission-lock-screen-screenshot-action-android-p/

Yes, I was aware this require a Java function (I already read that thread BTW). It is a working sample implementation (Tasker task) I was looking for and there are none in that thread (the two screenshots are incomplete)

Anyway, I think I'll manage to use the same code provided there replacing %par1 by %launch_data

On that XDA post you have an example:

cr = CONTEXT.getContentResolver(); 

Secure.putString(cr, sysui_nav_bar, space,recent;home;back,menu_ime) 

Yup, you're right. That code work but I'll rather use the "Tasker Toggle Setting" task from the reddit post which I've given the link. 

Meantime I've tested it within Tasker and seem to just work fine and it's generic.

[João Dias]

Great to know, thanks!

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/WhfQuCm3t5g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.

[Keir Stiegler]

With putString instead of putFloat but no other changes to the action, the task runs without errors but there is no effect.

[N Mok]

not sure what's going on, but I have 3 devices... my main one, which has been running fine is also where my main Tasker config gets created from. a second device Google Pixel, which I recently obtained, I was able to restore data using TitaniumBackup from the main device and have it running with no issues. my third device, which was a backup to my main, I recently wiped and am having difficulties getting my main Tasker config restored to. using TitaniumBackup I can restore data to this third device, but backing out of Tasker keeps crashing, as well as running any task or profile. if I bring over the config.xml to Tasker/configs/user on the third device I'm told "Error: couldn't read backup data, sorry". the contents of the file look normal and can be read into the main and Pixel devices... any suggestions?

one thing to note, restoring the backup from TitaniumBackup on the Google Pixel was done prior to these latest releases...

[Gilles P]

That code work but I'll rather use the "Tasker Toggle Setting" task from the reddit post which I've given the link.

Meantime I've tested it within Tasker and seem to just work fine and it's generic.

 

I've been to optimistic :-( The code is not working 

For instance, the following sequence of actions has no effect (do not throw any error though):

Java Function [
    Return:cr
    Class Or Object:CONTEXT
    Function:getContentResolver {ContentResolver} ()
]
Java Function [
    Return:
    Class Or Object:Secure
    Function:putString {boolean} (ContentResolver, String, String)
    Param:cr
    Param:aod_mode
    Param:1
]

("aod_mode" is a system setting specific to some Samsung devices with Active Display feature)

Strangely after that, the following "getString" function on the same value returns  "1" 

Java Function [
    Return:%res
    Class Or Object:Secure
    Function:getString {String} (ContentResolver, String)
    Param:cr
    Param:aod_mode

]

One could think it has succeeded but the mode is not effectively set (as can be seen in Android parameters)

NB, the old (and outdated) Secure Settings plugin still works for that item.

 

[João Dias]

not sure what's going on, but I have 3 devices... my main one, which has been running fine is also where my main Tasker config gets created from. a second device Google Pixel, which I recently obtained, I was able to restore data using TitaniumBackup from the main device and have it running with no issues. my third device, which was a backup to my main, I recently wiped and am having difficulties getting my main Tasker config restored to. using TitaniumBackup I can restore data to this third device, but backing out of Tasker keeps crashing, as well as running any task or profile. if I bring over the config.xml to Tasker/configs/user on the third device I'm told "Error: couldn't read backup data, sorry". the contents of the file look normal and can be read into the main and Pixel devices... any suggestions?

one thing to note, restoring the backup from TitaniumBackup on the Google Pixel was done prior to these latest releases...

Are you maybe using different Tasker versions on those devices?

[João Dias]

NB, the old (and outdated) Secure Settings plugin still works for that item.

 

Did you check if the  setting "sticks" if you change it with Secure Settings? 

[Gilles Pion]

Did you check if the  setting "sticks" if you change it with Secure Settings? 

Totally:

 it even survive a device restart.

[João Dias]

Sorry, I meant if you list the secure settings again with ADB. Does it have the correct value there?

[N Mok]

what I had done on the main and the Pixel was install the version from Google Play Store, which was the version prior to your first release. on both those devices I then upgraded to your version and they have been working fine, at least in terms of functionality. with the third device I had recently wiped it clean so I had to start from scratch, whereby the version of Tasker was already your recent release... this shouldn't have mattered as I backed up the data using TitaniumBackup with your latest release and restored that onto the third device. when that didn't work I tried exporting the config.xml from the main device and importing it into the third device... that didn't work as well so I posted here. what I ended up doing was grabbing a backup made from November 2017 on my computer and restored that version of Tasker along with its data with TitaniumBackup and then updated Tasker through Google Play Store to bring all 3 devices to the same version released from you.

[João Dias]

Interesting. So it seems that importing an old export with my version doesn't work for you? Is that it?

--

[N Mok]

Correct, not exactly sure why since the export/import is happening from the same version, with the exception that the config was created a while back. that said, TitaniumBackup should have restored a working version from the backup made on your version from the main device...

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[Nuno Guerreiro]

Is this want you want??
Hope it helps

Profile: Wifi Work Connected (17)
State: Wifi Connected [ SSID:* MAC:* IP:* Active:Yes ]
Enter: Anon (18)
A1: Auto Brightness [ Set:On ]
A2: Display Brightness [ Level:1 Disable Safeguard:Off Ignore Current Level:Off Immediate Effect:Off ]
A3: Ringer Volume [ Level:3 Display:Off Sound:Off ]

Exit: Anon (10)
A1: Ringer Volume [ Level:5 Display:Off Sound:Off ]
A2: Auto Brightness [ Set:On ]

[Gilles P]

Sorry, I meant if you list the secure settings again with ADB. Does it have the correct value there?

Yes

Here what I've done:

1. disable AOD manually (using device settings native app)
2. adb shell settings list system > before.txt
3. set aod_mode on using secure settings
4. adb shell settings list system > after.txt
5.  result :
   
   $ diff before.txt after.txt

   59c59

   < aod_mode=0

   ---

   > aod_mode=1
   
   

To be complete, I've tried using Java function again:

1. disable AOD manually.
2. run  Tasker task to set aod_mode using Java API
3. $ adb shell settings list system | find "aod_mode="

   aod_mode=0 # expected "1"

[Stipe]

Unfortunately it doesn't fix it for me.
The same issue with the same error log persists (running version 5.1.4b.bf3 on rooted Samsung Galaxy Note 4, Android 5.1.1 with Xposed framework.
Otherwise everyting seems to work OK, it just crashes and service restarts few seconds later everytime I hit the Back key...


Dne četrtek, 15. marec 2018 14.59.55 UTC+1 je oseba joaomgcd napisala:

Ok, pushed fix to Google Play now. Hopefully that fixes it.

[João Dias]

Nuno, that's the one that works right? How does it look like when it doesn't work?

Gilles P do you have root on your device?

Stipe, what error is that exactly? So everytime you hit the back key on your device Tasker crashes?

--

You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/WhfQuCm3t5g/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.

[Gilles P]

Gilles P do you have root on your device?

No I don't   (and I cant': I'm using it for work too. This is not allowed for security reasons)

[João Dias]

Ok, thanks. Didn't know you could perform the adb shell list command without root :)

On Thu, Mar 22, 2018 at 12:57 PM, Gilles P <gille...@gmail.com> wrote:

Gilles P do you have root on your device?

No I don't   (and I cant': I'm using it for work too. This is not allowed for security reasons)

--

[Gilles P]

Ok, thanks. Didn't know you could perform the adb shell list command without root :)

Yes: it's only USB debugging which is is required for those commands.

[João Dias]

ah interesting! Thank you! :)

[João Dias]

Yes, whenever I hit back or even when I just hit the menu key (so Tasker looses focus), it crashes, but the service itself restarts again (not the app). At the same time Tasker looses Accessibility Permissions, so profiles depending on it are not running anymore. Then I switch it back on and it's OK until next Back/Menu hit and the story repeats :).
For now it is unreliable (profiles not firing), so I switched back to previous (Direct purchase) version, which works perfectly.

Thank you. Can you please let me know which Android version you're using? Thanks! 

[Stipe]

Android 5.1.1, rooted, additional Xposed framework installed (not sure if it matters).
I wish I saved a crash.txt, when I had it (I sent a crash report with this error included), but unfortunately it got lost/overwritten when restoring the old version from Titanium Backup.


Dne četrtek, 22. marec 2018 14.22.05 UTC+1 je oseba joaomgcd napisala:

[joaomgcd]

Thank you, I'll check out the crash reports!

[joaomgcd]

Android 5.1.1, rooted, additional Xposed framework installed (not sure if it matters).
I wish I saved a crash.txt, when I had it (I sent a crash report with this error included), but unfortunately it got lost/overwritten when restoring the old version from Titanium Backup. 

Can you please try with this version?  Thanks in advance! :)

[Stipe]

After a quick test (cca 10 minutes) it seems to work perfectly... I'll try it more in details in the evening, but I think, that you found the correct bug :).
Thank you very much for your support and responsivness.


Dne četrtek, 22. marec 2018 16.25.43 UTC+1 je oseba joaomgcd napisala:

[joaomgcd]

Awesome :D

[joaomgcd]

Ok, pushed fix to Google Play now.

I'm also preparing for a change that allows plugins to work much faster and not be dependent on the sometimes ultra-slow broadcastreceivers on Android. Let's hope it works as expected! :)

[Jay M]

sounds cooler than the cool side of the pillow

On Thu, 22 Mar 2018, 19:11 joaomgcd, <joao...@gmail.com> wrote:

Ok, pushed fix to Google Play now.

I'm also preparing for a change that allows plugins to work much faster and not be dependent on the sometimes ultra-slow broadcastreceivers on Android. Let's hope it works as expected! :)

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--

Jay M ︻芫══一

[Stipe]

OK, just confirmig, after thorough testing everthing seems to be perfect :).
Thx again.


Dne četrtek, 22. marec 2018 16.51.16 UTC+1 je oseba joaomgcd napisala:

Awesome :D

[Rich D]

Ok, pushed fix to Google Play now.

I do not see a update on Google play. I am still on 5.1.4b.bf3.  Is there a more current version?

[João Dias]

Yes, the current beta version is 5.1.4b.bf4 :)

On Thu, Mar 22, 2018 at 9:53 PM, Rich D <ricp...@gmail.com> wrote:

Ok, pushed fix to Google Play now.

I do not see a update on Google play. I am still on 5.1.4b.bf3.  Is there a more current version?

--

You received this message because you are subscribed to the Google Groups "Tasker" group.

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

[Gilles P]

Ok, pushed fix to Google Play now.

I'm still facing that issue with it:

 

[João Dias]

And you have those apps installed?

--

You received this message because you are subscribed to the Google Groups "Tasker" group.

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

[Gilles P]

Le vendredi 23 mars 2018 13:32:40 UTC+1, joaomgcd a écrit :

And you have those apps installed?

All of them yes:

com.balda.securetask : https://play.google.com/store/apps/details?id=com.balda.securetask 
com.joaomgcd.autoappshub https://play.google.com/store/apps/details?id=com.joaomgcd.autoappshub

[Gilles P]

And you have those apps installed?

All of them yes:

com.balda.securetask : https://play.google.com/store/apps/details?id=com.balda.securetask 
com.joaomgcd.autoappshub https://play.google.com/store/apps/details?id=com.joaomgcd.autoappshub

getting that error for com.joaomgcd.autonotification too

[João Dias]

Do you get that error for all of your plugins?

[Gilles P]

Do you get that error for all of your plugins?

Only the ones I've  previously signaled (and I'm using many others).

BTW I've been unable to capture those errors in plain text

It appears on a popup when launching Tasker when the following option is set:

the help text refers to a "file" but I haven't found it.

 

[Christophe]

Hi,

For your info, there is an issue with the localization of greather than / less than sign, at least in French

Regards

Christophe

[João Dias]

Gilles I think I know what's up :) Do those actions still work correctly? I think it's just a logging issue

Thanks for the report Christophe!

--

[Gilles P]

Gilles I think I know what's up :) Do those actions still work correctly? 

I think they do. But due to the fact that I'm not notified of those errors in real time it's pretty difficult to match individual errors with effective tasks execution (I have a fairly obfuscated Tasker setup which include many tasks and profiles, which does not help here)

 

I think it's just a logging issue

Ok, you confirm they can safely be ignored ?

Note that if I've choosen to set option "popup errors/warning" its because i thought would be useful when participating to beta program.

[João Dias]

Yes, that is useful, thanks :) I'll try to get rid of those in the next version.

--

[Christophe]

Hi Joao,
Is there a way to implement an option to let user to use root action even if Tasker won't detect su package ?
This is an issue when using hidden Magisk Manager.
Regards
Christophe

[João Dias]

I'll check thanks. Ideally I would like to fix Tasker's inability to figure out that you're not rooted.

[krabbs]

Am Donnerstag, 15. März 2018 12:14:00 UTC+1 schrieb joaomgcd:

• manifest permission WRITE_SECURE_SETTINGS: enable via adb command - adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS

i am a long-term user of Tasker and bought Tasker without playstore. 

By changing the necessary shell line I get the following:

Operation not allowed: java.lang.SecurityException: Package net.dinglisch.android.tasker has not requested permission android.permission.WRITE_SECURE_SETTINGS

i am currently running Tasker 5.1b4 downloaded from the tasker website.

Cheers and keep up the good work!

[João Dias]

Hi there. Unfortunately that version didn't have that permission yet. The version discussed here was 5.1.4b and not 5.1b

Sorry!

--

[krabbs]

no worry

no hurry :D

i will stick to playstore. buy yourself a beer for the extra money =) 

Am Montag, 7. Mai 2018 10:48:28 UTC+2 schrieb joaomgcd:

Hi there. Unfortunately that version didn't have that permission yet. The version discussed here was 5.1.4b and not 5.1b

Sorry!

On Mon, May 7, 2018 at 9:14 AM, 'krabbs' via Tasker <tas...@googlegroups.com> wrote:

Am Donnerstag, 15. März 2018 12:14:00 UTC+1 schrieb joaomgcd:

• manifest permission WRITE_SECURE_SETTINGS: enable via adb command - adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS

i am a long-term user of Tasker and bought Tasker without playstore. 

By changing the necessary shell line I get the following:

Operation not allowed: java.lang.SecurityException: Package net.dinglisch.android.tasker has not requested permission android.permission.WRITE_SECURE_SETTINGS

i am currently running Tasker 5.1b4 downloaded from the tasker website.

Cheers and keep up the good work!

--
You received this message because you are subscribed to the Google Groups "Tasker" group.

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

[Landon Muscle]

🤙😁

[João Dias]

Thank you very much :D

🤙😁

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

[Rich B]

I have a new phone. I've installed the latest beta (way beyond this one). Do we still need to use the ADB SHELL command below if we change phones and reinstall Tasker.?Thanks.

On Thursday, March 15, 2018 at 7:14:00 AM UTC-4, joaomgcd wrote:

New Beta is out! I'm dipping my toes in making small changes to Tasker so bear with me :)

Here's the changelog for this release.

[João Dias]

Yes, you do :)

[Rich B]

Is this in the manual somewhere? I couldn't find (doesn't mean it wasn't there, just that I couldn't find it! ;-)). I didn't see it listed as something to do when reading the Tasker description in the play store. Or maybe it's something under preferences or help? For now, I've saved the instructions in an email to myself in an "apps" folder (along with instructions for a plugin that needs ADB commands as well). Thanks.

On Thursday, July 19, 2018 at 4:55:14 AM UTC-4, joaomgcd wrote:

Yes, you do :)

[João Dias]

It's in every action that needs it. For example, check the (i) page of the Custom Setting action.

[Rich B]

Got it. Although I didn't even think to look in the ? help while trying to use a command. ;-)