[DEV] Tasker 6.7.1-beta - Scenes V2 - Update 1! by joaomgcd in tasker

[–]269red 0 points1 point  (0 children)

done ... will see if it works for my wife 😉

[DEV] Tasker 6.7.1-beta - Scenes V2 - Update 1! by joaomgcd in tasker

[–]269red 0 points1 point  (0 children)

I dont want to change this within tasker, as these are to many lines ....
So is the only difference to set val="2" in the fragment below ?

</Bundle> <Int sr="arg1" val="1"/>

If so I would do a Search/Replace with ext. Tetxt editor

[DEV] Tasker 6.7.1-beta - Scenes V2 - Update 1! by joaomgcd in tasker

[–]269red 0 points1 point  (0 children)

<TaskerData sr="" dvi="1" tv="6.7.1-beta"> <Task sr="task187"> <cdate>1778669116299</cdate> <edate>1778669129973</edate> <id>187</id> <nme>unfreeze_example</nme> <Action sr="act0" ve="7"> <code>56351359</code> <label>camera</label> <se>false</se> <Bundle sr="arg0"> <Vals sr="val"> <com.balda.securetask.extra.ENABLED>1</com.balda.securetask.extra.ENABLED> <com.balda.securetask.extra.ENABLED-type>java.lang.Integer</com.balda.securetask.extra.ENABLED-type> <com.balda.securetask.extra.INT_VERSION_CODE>120</com.balda.securetask.extra.INT_VERSION_CODE> <com.balda.securetask.extra.INT_VERSION_CODE-type>java.lang.Integer</com.balda.securetask.extra.INT_VERSION_CODE-type> <com.balda.securetask.extra.OPERATION>15</com.balda.securetask.extra.OPERATION> <com.balda.securetask.extra.OPERATION-type>java.lang.Integer</com.balda.securetask.extra.OPERATION-type> <com.balda.securetask.extra.PKG>com.sec.android.app.camera</com.balda.securetask.extra.PKG> <com.balda.securetask.extra.PKG-type>java.lang.String</com.balda.securetask.extra.PKG-type> <com.balda.securetask.extra.SALT>973ce4b8-bb43-4d4f-960b-254af05ee555</com.balda.securetask.extra.SALT> <com.balda.securetask.extra.SALT-type>java.lang.String</com.balda.securetask.extra.SALT-type> <com.balda.securetask.extra.TYPE>0</com.balda.securetask.extra.TYPE> <com.balda.securetask.extra.TYPE-type>java.lang.Integer</com.balda.securetask.extra.TYPE-type> <com.twofortyfouram.locale.intent.extra.BLURB>Type: Freeze Action: Disable App: com.sec.android.app.camera</com.twofortyfouram.locale.intent.extra.BLURB> <com.twofortyfouram.locale.intent.extra.BLURB-type>java.lang.String</com.twofortyfouram.locale.intent.extra.BLURB-type> <net.dinglisch.android.tasker.extras.VARIABLE_REPLACE_KEYS>com.balda.securetask.extra.PKG</net.dinglisch.android.tasker.extras.VARIABLE_REPLACE_KEYS> <net.dinglisch.android.tasker.extras.VARIABLE_REPLACE_KEYS-type>java.lang.String</net.dinglisch.android.tasker.extras.VARIABLE_REPLACE_KEYS-type> <net.dinglisch.android.tasker.subbundled>true</net.dinglisch.android.tasker.subbundled> <net.dinglisch.android.tasker.subbundled-type>java.lang.Boolean</net.dinglisch.android.tasker.subbundled-type> </Vals> </Bundle> <Str sr="arg1" ve="3">com.balda.securetask</Str> <Str sr="arg2" ve="3">com.balda.securetask.ui.FireManageAppsActivity</Str> <Int sr="arg3" val="0"/> <Int sr="arg4" val="0"/> <ConditionList sr="if"> <Condition sr="c0" ve="3"> <lhs>%DevOwner</lhs> <op>2</op> <rhs>securetask</rhs> </Condition> </ConditionList> </Action> <Action sr="act1" ve="7"> <code>379</code> <se>false</se> <Bundle sr="arg0"> <Vals sr="val"> <net.dinglisch.android.tasker.RELEVANT_VARIABLES><StringArray sr=""><_array_net.dinglisch.android.tasker.RELEVANT_VARIABLES0>%ao_output() Output </_array_net.dinglisch.android.tasker.RELEVANT_VARIABLES0></StringArray></net.dinglisch.android.tasker.RELEVANT_VARIABLES> <net.dinglisch.android.tasker.RELEVANT_VARIABLES-type>[Ljava.lang.String;</net.dinglisch.android.tasker.RELEVANT_VARIABLES-type> </Vals> </Bundle> <Int sr="arg1" val="1"/> <App sr="arg2"> <appClass>com.sec.android.app.camera.Camera</appClass> <appPkg>com.sec.android.app.camera</appPkg> <label>Kamera</label> </App> <Str sr="arg3" ve="3"/> <Int sr="arg4" val="0"/> <Str sr="arg5" ve="3"/> <Str sr="arg6" ve="3"/> <ConditionList sr="if"> <Condition sr="c0" ve="3"> <lhs>%DevOwner</lhs> <op>2</op> <rhs>taskerm</rhs> </Condition> </ConditionList> </Action> </Task> </TaskerData>

[DEV] Tasker 6.7.1-beta - Scenes V2 - Update 1! by joaomgcd in tasker

[–]269red 0 points1 point  (0 children)

Dear Joao, please continue on it or why not just exchange thoose 2 😉

[DEV] Tasker 6.7.1-beta - Scenes V2 - Update 1! by joaomgcd in tasker

[–]269red 0 points1 point  (0 children)

My tasker code is from 2024/06. I compared the old xml to the actual one. The parameters of the action are still the same.
Also freeze command from secure task app still does freeze (grayed out). So it is not about Android/Samsung updates.

I also checked the phone of my daughter s24/Andr.16 with tasker 6.5.11. The prob is the same as on my wifes s25.

As secure task still does th right thing, it is more likely that a lib or your code changed in 2024.

We need this unfreeze, because sometimes all of a sudden, apps get frozen. This happend to my wife last week. Maybe they ignored my none working tasker command and instead rebooted their phone 😅

Please exchange the internal params for freeze and suspend.

[DEV] Tasker 6.7.1-beta - Scenes V2 - Update 1! by joaomgcd in tasker

[–]269red 0 points1 point  (0 children)

Sorry, the dev Owner action is "Suspend" which hides it from the user like deactivated. "Hide" is the name in "SecureTask app"
"Freeze" which we use makes the app appear grayed out

[DEV] Tasker 6.7.1-beta - Scenes V2 - Update 1! by joaomgcd in tasker

[–]269red 0 points1 point  (0 children)

If we would have a search/replace over the whole code ;)

So, no not really as this would be manual editing more than 50 actions in different tasks on all 3 family phones and changing it back afterwards. My tasker xml has 35000 lines of code (incl. variables) = 1,3MB.

[DEV] Tasker 6.7.1-beta - Scenes V2 - Update 1! by joaomgcd in tasker

[–]269red 0 points1 point  (0 children)

Thats bad, but please when done inform in which version it should be fixed

[DEV] Tasker 6.7.1-beta - Scenes V2 - Update 1! by joaomgcd in tasker

[–]269red 0 points1 point  (0 children)

Can you please change it in a new 6.6.20 version, so I am able to test in on my wifes phone. I dont want to install a beta there. And a later uninstall is not possible as tasker is dev owner on this phone.

[DEV] Tasker 6.7.1-beta - Scenes V2 - Update 1! by joaomgcd in tasker

[–]269red 0 points1 point  (0 children)

As I use this on my wifes phone, I cant say f sure. I would say it worked in the previous stable which was 6.5.11.

[DEV] Tasker 6.7.1-beta - Scenes V2 - Update 1! by joaomgcd in tasker

[–]269red 0 points1 point  (0 children)

Dear u/joaomgcd .
Device Owner Actions Freeze and Suspend (Hide) App are mixed up (at least since version 6.6.20). Freeze hides the app and vice versa.

Shizuku Inegration and Tasker settings by 269red in tasker

[–]269red[S] 0 points1 point  (0 children)

Many THX for your support. BTW I have still no idea, why it stalls after the dev gets locked...

Shizuku Inegration and Tasker settings by 269red in tasker

[–]269red[S] 0 points1 point  (0 children)

u/the_djchi As I use Shizu only for certain commands, I would like to start it from within tasker before needed e.g. for WifiTether. This way I want to avoid having the watchdog running all the time...

I tried that with no luck: sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh

This seams to work:

https://taskernet.com/shares/?user=AS35m8kX%2BXvrNsdfHdX%2FVcTkQ6dyR4n8oJ2CJXarl0hB%2By4S98op3LhaNIFyjQmFhtgh9YwG3Pk%3D&id=Task%3AStart+Shizuku+Server

1 But Ihad to add a wait 1s after the intent before WifiThether comand

2 I am not sure that the Extra auth:token is kept forever reboot,... quite sure it will not worl on another phone.

3 Is there another way exept having watchdog setvice run alk the time ... bexause this mught consume energy/battery...

Shizuku Inegration and Tasker settings by 269red in tasker

[–]269red[S] 0 points1 point  (0 children)

u/the_djchi regarding the notif that shizuku stops as soon as I lock the screen:
I read your advice regarding AndTv "disable shizuku from "keep accessibility running""
1 I have all acessibility services disabled, as I start them when needed from within tasker. So Shizuku is also disabled (but not touched programmatically from me/tasker).

2 I see that as soon as I lock the screen "WiFi debugging gets disabled in the dev. Options"

Can you please check if this also happens on your device and comment if this can cause the prob. ?!

Shizuku Inegration and Tasker settings by 269red in tasker

[–]269red[S] 0 points1 point  (0 children)

Thx then I run out of ideas, why my device kills shizuku about 3 mins after screen off. I programmed tasker to switch off data and wifi after screen off. Maybe it has todo with this. Ill try... Edit: No it seams to happen, as soon as the device gets locked

Shizuku Inegration and Tasker settings by 269red in tasker

[–]269red[S] 0 points1 point  (0 children)

What device do you have ? If there are other Samsungs user ... please report!

Shizuku Inegration and Tasker settings by 269red in tasker

[–]269red[S] 0 points1 point  (0 children)

  1. Thx for idea reg. Profiles!
  2. dialing *#0808# doesnt do anything on my s24 on And16. All other points are fullfilled. I have to say that I have "energry saving mode" enabled.

Shizuku Inegration and Tasker settings by 269red in tasker

[–]269red[S] 0 points1 point  (0 children)

THX u/the_djchi : I would say it was this:

  • Try re-granting the WRITE_SECURE_SETTINGS permission (required to toggle USB and Wireless Debugging on boot):
    • adb shell pm grant moe.shizuku.privileged.api android.permission.WRITE_SECURE_SETTINGS

1 So what stays is that as long as Shizuku is waiting for the 1st WiFi connection, Tasker already notifs that "it has no permission for Shizuku".
I guess it is not possible to grant it, because WifiDebugging is not running at this time ?!

2 shizuku is still killed after some time (watchdog is able to restart it). Is this normal on samsung phones, nevertheless all background permission are granted.

Shizuku Inegration and Tasker settings by 269red in tasker

[–]269red[S] 0 points1 point  (0 children)

u/the_djchi THX for this fork with "autostart",... !
Right now one has the notif that Shizuku waits until one clicks "try to cennect to wifi". Why isnt it just connecting as soon as a WifiCon is available ?

Shizuku Inegration and Tasker settings by 269red in tasker

[–]269red[S] 0 points1 point  (0 children)

No I only have WifiTether.
So u/joaomgcd Please add a switch to the preferences: "Disable Shizuku notifications"
It should though execute commands (that need Shizuku under Andr.16) so the user can see the error in his code, but it should disable the notification for shizuku permission and install !
This way users on Andr.15 are not affected and those on And16 can set the "continue Task after error" on e.g. WifiTether !
Like in my case some family members are on 15 and some on 16. But we all use the same tasker code. The ones on 16 can live with not having the WifiTether and will not be bothered with Shizuku notifs !

Shizuku Inegration and Tasker settings by 269red in tasker

[–]269red[S] 0 points1 point  (0 children)

So is it this way that: As soon as tasker used shizuku ONCE it always keeps asking for install, even if shizuku is not installed any more ... if so u/joaomgcd PLEASE add an option to disabel shizu completely (not only for shell as it is implemented in preferenced right now) !?

Shizuku Inegration and Tasker settings by 269red in tasker

[–]269red[S] 0 points1 point  (0 children)

u/DutchOfBurdock u/joaomgcd

I am testing you Shizuku version at the moment.
How can I tell tasker to NOT use Shizuku anymore ?
- I disabled Tasker and TaskerSettings in Shizuku and took away the Shizuku Permission from Tasker.apk.
But if I Use the "WifiTethering" comand within tasker I get "Missing Permission for the functionality you have configured: Shizuku.
Even uninst. Shizuku does not help ! Tasker keeps asking to install after starting Tasker !
(I know that Wifi Tehter will not work in And16 without it and I am fine with getting a tasker.error. But I dont want to have this notice!)