Permission issues, WRITE_SETTINGS

[Henrik "The Developer" Lindqvist]

Some users are having issue with the transition from the old permission add-ons, to the (new) Android 6+ run-time permission model, resulting in security failures such as:

java.lang.SecurityException: com.llamalab.automate.ext.* was not granted this permission: android.permission.WRITE_SETTINGS.

The issue seems to mostly affect the Wi-Fi hotspot set state block, if you're using an Android 8+ device, try enabling the "Private setting" or "Extension" option in the "Wi-Fi hotspot workaround" setting.

If that doesn't work, the issue seems to be (temporarily) fixed by ensuring that the main app package is installed first, i. e.:

1. Stop all flows
2. Make a backup, see settings
3. Uninstall Automate
   
4. Uninstall all permission add-ons, see system Apps settings.
   
5. Reboot the device
6. Reinstall Automate
7. Restore backup
   
8. Optional, use ADB to grant "superuser" permission, see:
   https://groups.google.com/d/topic/automate-user/HUm7yZPv578/discussion
9. Grant "privileges" required by flows
   
10. Restart flows

If it still doesn't work. Please let me know if you has Automate installed prior to version 1.11.3, i.e. the old permission model, or not.

Include Android version, device model, which block is causing it. If only the Wi-Fi hotspot set state block is affected, enable the "Debug logging" option in settings and run the block to see debug info, please post it here.

I need to determine if this issue is caused by the transition, or the new model, in which case i may have to abandon the remaining three add-ons.

[peka...@gmail.com]

Hi,

I followed steps you described (except optional step 8) and still have problem. But my error has changed from

java.lang.SecurityException: com.llamalab.automate.ext.settings was not granted  this permission: android.permission.WRITE_SETTINGS.

to

java.lang.SecurityException: com.llamalab.automate.ext.network was not granted  this permission: android.permission.WRITE_SETTINGS.

It looks to me, that Automate network extension is trying to WRITE_SETTINGS, but that extension has no option to allow write system settings in android app settings. Only Automate has that advanced settings.

Jan

Dne pátek 8. června 2018 21:50:09 UTC+2 Henrik "The Developer" Lindqvist napsal(a):

Some users are having issue with the transition from the old permission add-ons, to the (new) Android 6+ run-time permission model, resulting in security failures such as:

java.lang.SecurityException: com.llamalab.automate.ext.* was not granted this permission: android.permission.WRITE_SETTINGS.

Fix which seems to work for most users:

1. Stop all flows
2. Make a backup, see settings
3. Uninstall Automate
   
4. Uninstall all permission add-ons, see system Apps settings.
   
5. Reboot the device
6. Reinstall Automate
7. Restore backup
   
8. Optional, use ADB to grant "superuser" permission, see:
   https://groups.google.com/d/topic/automate-user/HUm7yZPv578/discussion
9. Grant "privileges" required by flows
   
10. Restart flows
    

Please let me know if you has Automate installed prior to version 1.11.3, i.e. the old permission model, or not.

[Henrik "The Developer" Lindqvist]

Thanks for reporting back. What device and Android version?

[Fran T]

Aren't the Network, Settings, and Superuser add-ons still needed?

https://groups.google.com/forum/m/#!topic/automate-user/iom824EjmVQ

[peka...@gmail.com]

Android 8.0.0 on LG-H870
I had Automate 1.11.1. before and it was working without problems.
Also downgrade from 1.11.3 to 1.11.1 brought back functionality that on 1.11.3. isn't working (start WiFi tethering).

Dne sobota 9. června 2018 1:32:45 UTC+2 Henrik "The Developer" Lindqvist napsal(a):

[peka...@gmail.com]

SOLVED!

When I uninstalled all Automated add-ons and installed clean Automate 1.11.3 it asked me for Automate connectivity permissions (network), when creating WiFi tethering flow but not for Automate settings permission.

I installed "Automate settings permission" add-on and flow started to work without error.

It looks that new Automate will not ask user to install all necessary add-ons.


Dne sobota 9. června 2018 1:39:08 UTC+2 Fran T napsal(a):

[Henrik "The Developer" Lindqvist]

Yes, you'll be prompted to install them again in step #9.

The critical part may be that Automate is installed first.

[Henrik "The Developer" Lindqvist]

The Wi-Fi hotspot set state block should request the "modify system settings" privilege, that should suffice.

The Settings add-on, i.e. the "modify private settings" privilege, should only be requested for the System settings set and Screen brightness set blocks.

[slam...@gmail.com]

Same for me, thanks!

Reinstalling all automate and its permissions helped but I also had to install "Automate settings permission" manually. Automate didn't ask for it to be installed.

I did all the steps (including adb shell) but It looks like I was missing this one apk. I had it installed previously but it wan't working correctly.

I would add to the list as step 6a: make sure you have installed "Automate settings permission".

[Henrik "The Developer" Lindqvist]

Odd, the Automate main apk already include the WRITE_SETTINGS permission, it's only required to work around an Android bug.

[peka...@gmail.com]

Today it stopped working for me. App was trying to use com.llamalab.automate.ext.network to WRITE_SETTINGS but that addon doesn't have these rights..
A have still 1.11.3 Automate version and "settings permission" addon installed. It looks, that Automate is randomly using plugins for that WRITE access?

Jan

2018-06-11 09:36:10.643 FAIL 85@2: java.lang.SecurityException: com.llamalab.automate.ext.network was not granted  this permission: android.permission.WRITE_SETTINGS.

Dne neděle 10. června 2018 10:03:41 UTC+2 slam...@gmail.com napsal(a):

[peterr...@gmail.com]

I also have problems getting it working. I have there problems when i have upgraded to android 8.0 on Samsung Galxy S7 and installed latest 1.11/3 automate version....

Op maandag 11 juni 2018 16:36:05 UTC+2 schreef peka...@gmail.com:

[Henrik "The Developer" Lindqvist]

It's an Android problem, it seem to check permissions for the wrong package name, i.e com.llamalab.automate.ext.network instead of com.llamalab.automate.

If this issue is affecting everyone, even new version 1.11.3 users, and keeps on reappearing, i'll be forced to stop add-ons entirely.

[peka...@gmail.com]

But I had no problem with 1.11.1. Yesterday I downgraded and stopped updates and I will see.
Something has changed between current and previous version and that change (from my point of view) is hitting Android bug..

JP

Dne pondělí 11. června 2018 22:48:44 UTC+2 Henrik "The Developer" Lindqvist napsal(a):

[Henrik "The Developer" Lindqvist]

As the change log said, the whole permission model has changed, it now uses Android 6+ run-time permission instead, where possible.

http://llamalab.com/automate/doc/security.html

[brains...@googlemail.com]

Ok, i had reinstalled the App and the permissions yesterday completely… and what can i say… it worked. No Write setting failures anymore.

For a Time.

Now, 6h later, i had the same problem again.

[Henrik "The Developer" Lindqvist]

Thanks for reporting back.

Which block is causing it, and what Android version and device model are you using?

[brains...@googlemail.com]

Uhm, please wait.
Just checked it… now its working again. Will having an eye on it and send you all information when the problem comming back.

[Fran T]

I've run into a similar situation with MODIFY_PHONE_STATE permission for the End Call block. The flow fails on that block, saying it lacks that permission. The flow has "directly call phone numbers", "read phone status and identity", and "read your contacts" permissions. The flow that's failing is:

http://llamalab.com/automate/community/flows/7137

I'm on a Pixel 2 XL running Oreo 8.1.

[Fran T]

Separately, I have the Connectivity and Settings permission plug-ins also installed.

[Henrik "The Developer" Lindqvist]

The Call end block is an unrelated issue:

https://groups.google.com/d/topic/automate-user/vffTiAkVf8M/discussion

[Florent Fievez]

Same issue here, the installation of automate settings permissions does not solve the problem. I tried to uninstall, reinstall, uninstall the settings apps, ... 

[Henrik "The Developer" Lindqvist]

As the post say, the main Automate app and all permission add-on apps has to be uninstalled.

[Florent Fievez]

What I did but I have one flow which force reinstallation of "Automate connectivity permission". I don't know if it's the problem cause. 

--
You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/XFRTWIpJ1e8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at https://groups.google.com/group/automate-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/bac0a7e9-e3fe-42fb-b8ea-77196911a157%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Henrik "The Developer" Lindqvist]

Even if you're asked to install it again, make sure to uninstall everything first, as described in the original post:

https://groups.google.com/d/msg/automate-user/XFRTWIpJ1e8/UA07QZ8aAwAJ

On Monday, June 18, 2018 at 11:09:42 PM UTC+2, Florent Fievez wrote:

What I did but I have one flow which force reinstallation of "Automate connectivity permission". I don't know if it's the problem cause. 

[slam...@gmail.com]

After a few days it stopped working again with the same error... I don't know what is going on but I need to have it working so I installed old version from apkmirror and disabled automatic updates. Now it works correctly as it was working for over a year.

[Florent Fievez]

I followed your post, two time to be sure, and the problem always come back. If the permission are now granted to the "main" application why this addon is still required ? Is it work in progress ?

---
Florent Fievez

Gsm: +32 494 43 08 51
florent...@fievel.be

--

You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/XFRTWIpJ1e8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at https://groups.google.com/group/automate-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/c9785785-0644-4de3-8719-b9f5d196f6a9%40googlegroups.com.

[Henrik "The Developer" Lindqvist]

Why the add-ons are used, please read:

http://llamalab.com/automate/doc/security.html

But it seems like i may have to abandon this idea.

On Tuesday, June 19, 2018 at 9:50:31 AM UTC+2, Florent Fievez wrote:

I followed your post, two time to be sure, and the problem always come back. If the permission are now granted to the "main" application why this addon is still required ? Is it work in progress ?

---
Florent Fievez

Gsm: +32 494 43 08 51

[lars....@googlemail.com]

Hello,
I just want to let you know I had the same issue also after reinstalling everything twice. Then, I went to settings privileges and enabled some privileges that were disabled before. Unfortunately I am not sure which one finally solved the problem, but there were two things to mention. At one setting android said that I have to disable "secure phone start" because it cannot work together if this certain privilege was granted to automate. Another setting was I think the personal settings for access to notifications. After ticking the box I was forwarded to an android system setting to allow access for automate. Sorry I cannot explain more precisely, but issue is fixed for me now.
Regards
Lars

[lars....@googlemail.com]

Remark:
- Galaxy s7 edge, problem occurred after oreo update
- I could re-enable the android feature of "secure start" and it still works.

[ianha...@gmail.com]

Coming back to this thread, as I'd posted on the topic previously but things have moved on...

Like others, I was having the problem, but I thought I'd resolved it by forcing the permissions. However, I upgraded my 'phone to Android 7, and the permission model doesn't allow the same control, so the WRITE_SETTINGS error re-appeared.

This time, I uninstalled everything (not even keeping a backup), and started again from scratch. All was well...

... until it wasn't. It started failing again. So, again, I uninstalled/reinstalled everything, and then things worked... 

... until they didn't. Simply uninstalling and re-installing the extensions doesn't seem to fix anything, so the problem is perhaps with the core application. I scratch my head at the idea that Android is granting and then revoking permissions, however, so I'm at a loss as to why it's changing. Code doesn't do random things.

I haven't granted superuser permissions, nor have I tried granting Automate device admin privileges. Happy to try those things in a controlled manner if it's helpful ... I just wanted to report back that what was fixed is now not-fixed once again.

LG G4 H815. Android 7.0, kernel 3.10.84

Automate 1.11.3, but this time it's a clean installation, not an upgrade from a previous one (well, it was initially installed from backup, then wiped, then re-installed from Play).

[Henrik "The Developer" Lindqvist]

Thanks for reporting back.

Which block is causing the WRITE_SETTINGS permission error?

Is the Settings add-on installed?

If so, is "Modify system settings" enabled in system Apps settings, Automate settings extension, Advanced?

I don't think every device is affected, but i'll likely have to abandon three remaining add-ons for those who are.

[Florent Fievez]

Ok I found a working workaround at least on my device: 

Automate > settings > privileges > modify private settings 

This trigger installation of "Automate settings permissions" add on and it works. 

Don't have you forgot to enable a permission in the main app ?

--

You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/XFRTWIpJ1e8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at https://groups.google.com/group/automate-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/d5c25ceb-4033-44ee-943b-5f567e2d2540%40googlegroups.com.

[Henrik "The Developer" Lindqvist]

Not forgot. Only the System setting set and Screen brightness set blocks need the "modify private settings" privilege. Any flow using them should request it on the flow details screen as usual.

On Friday, June 22, 2018 at 11:12:46 PM UTC+2, Florent Fievez wrote:

Ok I found a working workaround at least on my device: 

Automate > settings > privileges > modify private settings 

This trigger installation of "Automate settings permissions" add on and it works. 

Don't have you forgot to enable a permission in the main app ?

[ka...@lublewski.pl]

I have a problem with permission denied:

com,llamalab.automate.ext.network was not granted this permission: adnroid.permission.WRITE_SETTINGS

I get this error "Enable Wi-Fi hotspot" block, while "Enable Bluetooth" works fine. 

I have Samsung S8 with Android 8.0.0. Automated version is 1.11.3.

I installed that version 2 weeks ago because I got the same error on previous version. So I uninstalled everything and installed back - it worked 2 weeks, probably untill recent samsung firmware update. 

Yesterday when it stopped to work I did:

1. Uninstall all apps

2. Re-install, import my flow, reboot phone

3. It didn't work.

4. As suggested somewhere above I enabled "change privete settings" and it worked yesterday at least once (I made simple flow with one block enabling Hotspot and it passed).

5. Today I used my regular flow which enabled Hotspot in the car and it didn't work. Now also that simple one-block flow fails. 

I checked all privileges and they are the same. 

I disabled automatic updates, but there were no updated for Automate nor for Android since yesterday so I wonder why it stopped to work overnight. 

[Florent Fievez]

+1 I thought it was fixed but just worked a couple of times before it failed again. 

Do you plan releasing an update for this (or force downgrade to the working version until you find a solution)?

--

You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/XFRTWIpJ1e8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at https://groups.google.com/group/automate-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/dd48b78a-f125-4da3-a591-4804a0fae01f%40googlegroups.com.

[Henrik "The Developer" Lindqvist]

Is the Wi-Fi hotspot set state block using the rooted method, i.e. is the "Wi-Fi hotspot rooted" option enabled in settings?

Please post the error message, or use the Help & feedback menu to send me the system log.

[Henrik "The Developer" Lindqvist]

It is the Wi-Fi hotspot set state block in your case too?

If so, rooted?

Android version?

Of course i will have to fix it, but it could require major changes, abandon all add-ons, so i really want to ensure they are the cause first.

It seems to mostly/only affect the Wi-Fi hotspot set state block, which is odd since any "permission" issue would affect any block requiring the network or settings add-on.

On Monday, July 2, 2018 at 1:00:16 PM UTC+2, Florent Fievez wrote:

+1 I thought it was fixed but just worked a couple of times before it failed again. 

Do you plan releasing an update for this (or force downgrade to the working version until you find a solution)?

[ka...@lublewski.pl]

No, it is using regular method. "rooted" option is diabled and it has been always like that. 

2018-07-03 05:42:27.504 INFO 14@7: Power source plugged?
2018-07-03 05:42:27.507 INFO 14@9: Bluetooth set state
2018-07-03 05:42:27.546 INFO 14@3: Bluetooth device connected?
2018-07-03 05:42:27.875 INFO 14@25: Audio player control
2018-07-03 05:42:28.001 INFO 14@4: Wi-Fi hotspot set state
2018-07-03 05:42:28.214 FAIL 14@4: java.lang.SecurityException: com.llamalab.automate.ext.network was not granted  this permission: android.permission.WRITE_SETTINGS.
2018-07-03 05:42:28.215 INFO 14@4: Stopped by failure

Btw. I noticed that I have some infinite loop of PowerSourcePlugged and Bluetooth set state, so maybe this has some impact. I will check that by modofying my flow to remove the loop. 

[Florent Fievez]

Yes wifi hotspot set state. Non-rooted device. 

Android 8.0.0 (Samsung flavor)

Don't hesitate if you want me to do some tests in order to help you debug this thing. 

--

You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/XFRTWIpJ1e8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at https://groups.google.com/group/automate-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/f8a440a1-c46d-4a25-8c58-91fc2dd635bb%40googlegroups.com.

[Henrik "The Developer" Lindqvist]

Thanks. I'll see if i can workaround this issue with the hotspot hack.

On Wednesday, July 4, 2018 at 12:39:31 AM UTC+2, Florent Fievez wrote:

Yes wifi hotspot set state. Non-rooted device. 

Android 8.0.0 (Samsung flavor)

Don't hesitate if you want me to do some tests in order to help you debug this thing. 

[kin...@gmail.com]

LG G6

All permissions have been provided. Works only once or twice then error reappears. 

Removed app and permissions twice. 

On Friday, June 8, 2018 at 10:50:09 PM UTC+3, Henrik "The Developer" Lindqvist wrote:

Some users are having issue with the transition from the old permission add-ons, to the (new) Android 6+ run-time permission model, resulting in security failures such as:

java.lang.SecurityException: com.llamalab.automate.ext.* was not granted this permission: android.permission.WRITE_SETTINGS.

The issue seems to be fixed by ensuring that the main app package is installed first, i. e.:

1. Stop all flows
2. Make a backup, see settings
3. Uninstall Automate
   
4. Uninstall all permission add-ons, see system Apps settings.
   
5. Reboot the device
6. Reinstall Automate
7. Restore backup
   
8. Optional, use ADB to grant "superuser" permission, see:
   https://groups.google.com/d/topic/automate-user/HUm7yZPv578/discussion
9. Grant "privileges" required by flows
   
10. Restart flows

Please let me know if you has Automate installed prior to version 1.11.3, i.e. the old permission model, or not.

Include Android version, device model, and which block is causing it!

I need to determine if this issue is caused by the transition, or the new model, in which case i may have to abandon the remaining three add-ons.

[Henrik "The Developer" Lindqvist]

Which block is causing the error?

[djxe...@gmail.com]

Hi,

I am using Automate for a few weeks and I have also an issue with the WRITE_SETTINGS.

My flow needs it to turn on Bluetooth Tethering. It asked me to install the Automate settings permission which I did. It worked for 1-2 days then the flow started failing because of the SecurityException (WRITE_SETTINGS). The Automate settings permission was still installed and activated in the main app. After some testing I can say, that it seems to help to uninstall and reinstall the Automate settings permission. Then it will work for another 1-2 days. Looks like that there is some Android background task that removes the permission or something. I have Automate 1.11.3 on Android 8.0.0 on a Samsung Galaxy S7, not rooted.

I can also do some testings to help debugging, just let me know.

[kin...@gmail.com]

Wifi hotspot enabling

[Henrik "The Developer" Lindqvist]

Next release, coming today or tomorrow, will include another workaround, dunno if it works but worth a try. See settings. Join the Alpha:

https://play.google.com/apps/testing/com.llamalab.automate

[k.lu...@gmail.com]

It seems that it works now. I tested it yesterday and today few times and it worked each time. However I didn't test it with my main flow that I use in the car but with simple flow with 2 blocks. Today I will check it in the car.
Thanks.

[ka...@lublewski.pl]

Thanks. It works now - I tested it for 3 days and WiFi hotspot is enabled without any issues. 

[Florent Fievez]

It seem to work well. For information no uninstall/reinstall needed, just a device reboot. Let see in 2-3 days but seem to be good.

---
Florent Fievez

Gsm: +32 494 43 08 51

florent...@fievel.be

--

You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/XFRTWIpJ1e8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at https://groups.google.com/group/automate-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/7360b542-c42f-4fe1-961b-82e502313700%40googlegroups.com.

[marcelo13k]

I hope the new release fixes it. Are you going to release it?

Android 7.0

Samsung C5, experience version 8.1

Automate from Google play, 1.11.3

Did the unistall/re-install steps as instructed but hotspot block gives still

java.lang.SecurityException: com.llamalab.automate.ext.settings was not granted   this permission: android.permission.WRITE_SETTINGS.

Did reboot and still the same message

[Henrik "The Developer" Lindqvist]

Join the Alpha to test it now:

https://play.google.com/apps/testing/com.llamalab.automate

[lars....@googlemail.com]

Hello.
I just want to report I am still having this issue with Hotspot. Sometimes it works after remove and reinstall some rights, next day or some hours later it will again not work. I have installed the beta Programme version and tried all possible workarounds in the settings (except root, because my device is not rooted). I hope there will be a permanent solution soon as I really like the app. Thanks.

Lars

[Fran T]

Here's my workaround for the Hotspot issues:

http://llamalab.com/automate/community/flows/21295

The flow detects whether the Oreo UI workaround is needed by checking for an exception from a Wi-Fi Hotspot block during setup.

[marcelo13k]

Reporting the use of alpha channel version 1.12.0

1. I updated Automate form Google play --> Problem persisted, HotSpot block permissions error

2. I rebooted the phone, no uninstall, just reboot --> So far it looks good, no error and the HotSpot is being enabled/disabled as expected

3. If step 2 would not have worked, I was ready to uninstall everything and permissions and re-install. Luckily it was not necessary

Thank you Henrik again, impressive level of support for the Automate community!

[djxe...@gmail.com]

Sorry for my late answer.

I loaded the aplha about a week ago. The WRITE_SETTINGS permission still gets lost after some time but with the alpha it seems to last longer than with the stable build. I would say 2-3 days instead of 1-2 days. I didn't a complete reinstall of Automate though but my device is restarted every night (if I don't forget).

I will try if a reinstall of Automate will help. It didn't do so for other users, but it might be different with the alpha.

[Henrik "The Developer" Lindqvist]

So you did enable the "Private setting" workaround and installed the Settings add-on?

[Henrik "The Developer" Lindqvist]

So you did enable the "Private setting" workaround and installed the Settings add-on?

[mouta...@gmail.com]

Hello
I'm following this thread and here is my own experience.
My phone is a Samsung Galaxy A5 2017 running Nougat v7.0 stock ROM and the latest version of Automate from Play store.
I've got the same problem as the others (on the Bluetooth tethering block), uninstalled, reinstalled and the problem came back.
So I've enabled the privilege "modify private settings", installed the app "settings permission" from the store and now it works again.
I'll check continuously during the next days and let you know.
Thanks for the fix/workaround.
Luc

[lars....@googlemail.com]

Hi,
I already made some posts here. Just want to let you know it's still the same. After fresh reinstall it works fine for about a day, maybe less. Tried all ideas from this thread.

Lars

[marcelo13k]

Having Nougat (7.0) and joined the Automate Alpha channel -->  this configuration worked OK for a few days, but then it stopped (back to the WRITE_SETTINGS problem)

Only then, I checked the "Use Private Settings" option (which I thought was for Oreo and up)

This was 10 days ago and everything works fine since.

[Karol Lublewski]

It worked for me for a month but stopped again today, was there any update?

pt., 27 lip 2018, 17:27 użytkownik marcelo13k <marce...@gmail.com> napisał:

Having Nougat (7.0) and joined the Automate Alpha channel -->  this configuration worked OK for a few days, but then it stopped (back to the WRTIE_SETTINGS problem)

--

You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/XFRTWIpJ1e8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at https://groups.google.com/group/automate-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/89987a63-4e27-4870-8463-74e2bf533bcc%40googlegroups.com.

[Henrik "The Developer" Lindqvist]

Yes, version 1.12.2 has been release to the Alpha branch. So we can conclude every update will cause the issue.

Please enable "Debug logging" in settings, execute a flow with the Wi-Fi hotspot set state block, then post the flow log here, it should contains info which may help be debug the cause.

Also, please post your Android version and device brand/model.

On Friday, July 27, 2018 at 7:57:46 PM UTC+2, Karol Lublewski wrote:

It worked for me for a month but stopped again today, was there any update?

[Henrik "The Developer" Lindqvist]

Have you also tried the "Private setting" option in the Wi-Fi hotspot workaround setting?

Please enable "Debug logging" in settings, execute a flow with the Wi-Fi hotspot set state block, then post the flow log here, it should contains info which may help be debug the cause.

Also, please post your Android version and device brand/model.

[Karol Lublewski]

Galaxy S8 and android 8.0.0

2018-07-28 09:06:22.544 INFO 80@1: Flow beginning
2018-07-28 09:06:22.550 INFO 80@2: Wi-Fi hotspot set state
2018-07-28 09:06:22.561 DBUG 80@2: package=com.llamalab.automate, packages=[com.llamalab.automate.ext.network, com.llamalab.automate, com.llamalab.automate.ext.settings]
2018-07-28 09:06:22.562 DBUG 80@2: uid=10304, callingUid=10304
2018-07-28 09:06:22.563 DBUG 80@2: WRITE_SETTINGS=false, OPSTR_WRITE_SETTINGS=0, canWrite=true
2018-07-28 09:06:22.572 DBUG 80@2: com.llamalab.automate.ext.costly: not installed
2018-07-28 09:06:22.574 DBUG 80@2: com.llamalab.automate.ext.location: not installed
2018-07-28 09:06:22.575 DBUG 80@2: com.llamalab.automate.ext.media: not installed
2018-07-28 09:06:22.586 DBUG 80@2: com.llamalab.automate.ext.network: uid=10304, WRITE_SETTINGS=false, OPSTR_WRITE_SETTINGS=0, canWrite=false
2018-07-28 09:06:22.587 DBUG 80@2: com.llamalab.automate.ext.personal: not installed
2018-07-28 09:06:22.590 DBUG 80@2: com.llamalab.automate.ext.settings: uid=10304, WRITE_SETTINGS=false, OPSTR_WRITE_SETTINGS=0, canWrite=true
2018-07-28 09:06:22.592 DBUG 80@2: com.llamalab.automate.ext.storage: not installed
2018-07-28 09:06:22.593 DBUG 80@2: com.llamalab.automate.ext.superuser: not installed
2018-07-28 09:06:22.595 DBUG 80@2: com.llamalab.automate.ext.telephony: not installed
2018-07-28 09:06:22.612 FAIL 80@2: java.lang.SecurityException: com.llamalab.automate.ext.network was not granted  this permission: android.permission.WRITE_SETTINGS.
2018-07-28 09:06:22.613 INFO 80@2: Stopped by failure

--

You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/XFRTWIpJ1e8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at https://groups.google.com/group/automate-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/6ef0c245-4e1f-4539-849a-1c69d3d534bc%40googlegroups.com.

[mouta...@gmail.com]

Hello,
I'm coming back with bad news.
Unfortunately and in spite of having applied the workaround, the problem came back today.
If you need anything to debug this case, please let me know.
Thanks.
Luc

[Karol Lublewski]

It works again with the latest Google Play version and after reboot.

--
You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/XFRTWIpJ1e8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at https://groups.google.com/group/automate-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/8b0ca94b-c0b8-4a47-b85d-7006357bf60a%40googlegroups.com.

[Henrik "The Developer" Lindqvist]

I suspect the order of the "packages" is the cause, com.llamalab.automate has to be first or it wont work on the affected devices. It shouldn't be relevant, but due to Android bugs it is.

2018-07-28 09:06:22.561 DBUG 80@2: package=com.llamalab.automate, packages=[com.llamalab.automate.ext.network, com.llamalab.automate, com.llamalab.automate.ext.settings]

The only recourse will likely be to create another extension, which exclusively enable/disable Wi-Fi hotspot.

On Saturday, July 28, 2018 at 9:11:35 AM UTC+2, Karol Lublewski wrote:

Galaxy S8 and android 8.0.0

2018-07-28 09:06:22.544 INFO 80@1: Flow beginning
2018-07-28 09:06:22.550 INFO 80@2: Wi-Fi hotspot set state
2018-07-28 09:06:22.561 DBUG 80@2: package=com.llamalab.automate, packages=[com.llamalab.automate.ext.network, com.llamalab.automate, com.llamalab.automate.ext.settings]
2018-07-28 09:06:22.562 DBUG 80@2: uid=10304, callingUid=10304
2018-07-28 09:06:22.563 DBUG 80@2: WRITE_SETTINGS=false, OPSTR_WRITE_SETTINGS=0, canWrite=true
2018-07-28 09:06:22.572 DBUG 80@2: com.llamalab.automate.ext.costly: not installed
2018-07-28 09:06:22.574 DBUG 80@2: com.llamalab.automate.ext.location: not installed
2018-07-28 09:06:22.575 DBUG 80@2: com.llamalab.automate.ext.media: not installed
2018-07-28 09:06:22.586 DBUG 80@2: com.llamalab.automate.ext.network: uid=10304, WRITE_SETTINGS=false, OPSTR_WRITE_SETTINGS=0, canWrite=false
2018-07-28 09:06:22.587 DBUG 80@2: com.llamalab.automate.ext.personal: not installed
2018-07-28 09:06:22.590 DBUG 80@2: com.llamalab.automate.ext.settings: uid=10304, WRITE_SETTINGS=false, OPSTR_WRITE_SETTINGS=0, canWrite=true
2018-07-28 09:06:22.592 DBUG 80@2: com.llamalab.automate.ext.storage: not installed
2018-07-28 09:06:22.593 DBUG 80@2: com.llamalab.automate.ext.superuser: not installed
2018-07-28 09:06:22.595 DBUG 80@2: com.llamalab.automate.ext.telephony: not installed
2018-07-28 09:06:22.612 FAIL 80@2: java.lang.SecurityException: com.llamalab.automate.ext.network was not granted  this permission: android.permission.WRITE_SETTINGS.
2018-07-28 09:06:22.613 INFO 80@2: Stopped by failure

[Henrik "The Developer" Lindqvist]

Does your device have multiple users?

If so try installing Automate as the "primary" user. As always remember to backup first.

On Monday, July 30, 2018 at 8:37:29 AM UTC+2, Karol Lublewski wrote:

It works again with the latest Google Play version and after reboot.

[mouta...@gmail.com]

Thanks for replying.
No I only have one user on the phone.
Besides I think there's no way to create multiple users on my Samsung ROMs.

And to reply to your other post, I always install Automate first.
Then I select each flow to enable required privileges.
And when I tick "access local network, internet and nearly devices" I'm asked to install the connectivity permission app.

Thanks.
Luc

[mouta...@gmail.com]

About Bluetooth tethering, here is my log.

2018-07-30 18:29:54.227 INFO 7589@1: Flow beginning
2018-07-30 18:29:54.229 INFO 7589@2: Bluetooth device connected?
2018-07-30 20:16:45.563 INFO 7589@3: Bluetooth tethering set state
2018-07-30 20:16:45.688 FAIL 7589@3: java.lang.SecurityException: com.llamalab.automate.ext.network was not granted this permission: android.permission.WRITE_SETTINGS.
2018-07-30 20:16:45.700 INFO 7589@3: Stopped by failure

[Henrik "The Developer" Lindqvist]

So the Bluetooth tethering set state block is also affected. That's expected since all tethering use the same buggy Android API.

As said, i'll likely make an tethering extension app.

[djxe...@gmail.com]

Hi,

A dedicated tethering extension app would be really nice! :)

[mouta...@gmail.com]

Since last update I haven't gotten any problem.
Still on observation...
Thanks

[mouta...@gmail.com]

Unfortunately, I got the same error today again although it worked perfectly many times from yesterday.
It seemed to bug after a reboot of the phone, weird, isn't it ?
Tell me if you need the log.

[dani...@gmail.com]

In the last update, reinstalling the private and superuser privileges worked fine as well, the annoying thing is doing this method each time there is a system update.

On Friday, June 8, 2018 at 10:50:09 PM UTC+3, Henrik "The Developer" Lindqvist wrote:

Some users are having issue with the transition from the old permission add-ons, to the (new) Android 6+ run-time permission model, resulting in security failures such as:

java.lang.SecurityException: com.llamalab.automate.ext.* was not granted this permission: android.permission.WRITE_SETTINGS.

The issue seems to mostly affect the Wi-Fi hotspot set state block, if you're using an Android 8+ device, try enabling the "Private setting" option in the "Wi-Fi hotspot workaround" setting.

The issue seems to be fixed by ensuring that the main app package is installed first, i. e.:

1. Stop all flows
2. Make a backup, see settings
3. Uninstall Automate
   
4. Uninstall all permission add-ons, see system Apps settings.
   
5. Reboot the device
6. Reinstall Automate
7. Restore backup
   
8. Optional, use ADB to grant "superuser" permission, see:
   https://groups.google.com/d/topic/automate-user/HUm7yZPv578/discussion
9. Grant "privileges" required by flows
   
10. Restart flows

If it still doesn't work. Please let me know if you has Automate installed prior to version 1.11.3, i.e. the old permission model, or not.

Include Android version, device model, which block is causing it. If only the Wi-Fi hotspot set state block is affected, enable the "Debug logging" option in settings and run the block to see debug info, please post it here.

I need to determine if this issue is caused by the transition, or the new model, in which case i may have to abandon the remaining three add-ons.

[Henrik "The Developer" Lindqvist]

Is it the Wi-Fi hotspot set state block failing?

[Florent Fievez]

Personally from last "beta" update, I had no permissions issues anymore on all the blocks which were causing problems. So for me issue is solved. 

---
Florent Fievez

Gsm: +32 494 43 08 51
florent...@fievel.be

--

You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/XFRTWIpJ1e8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at https://groups.google.com/group/automate-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/53f06590-8c41-428f-b41c-98c1d81e7254%40googlegroups.com.

[lars....@googlemail.com]

Hello,
Same for me. Since version 1.12.3 there are no problems anymore. I have enabled the private settings workaround.

Thank you!
Lars

[Fran T]

Unfortunately, the private setting never worked for me on my Verizon Pixel 2 XL running Oreo, and now Pie. Here's the extended debug trace I get when the Mobile hotspot block fails; the only privileges I don't have enabled are root, take pictures, and mock GPS (it looks like the debug trace is still looking for the old plugin versions of them). I'm running this demo flow:

http://llamalab.com/automate/community/flows/21295

2018-08-24 10:42:55.833 DBUG 35067@46: package=com.llamalab.automate, packages=[com.llamalab.automate.ext.network, com.llamalab.automate.ext.settings, com.llamalab.automate]
2018-08-24 10:42:55.834 DBUG 35067@46: uid=10028, callingUid=10028
2018-08-24 10:42:55.835 DBUG 35067@46: WRITE_SETTINGS=false, OPSTR_WRITE_SETTINGS=0, canWrite=true
2018-08-24 10:42:55.836 DBUG 35067@46: com.llamalab.automate.ext.costly: not installed
2018-08-24 10:42:55.836 DBUG 35067@46: com.llamalab.automate.ext.location: not installed
2018-08-24 10:42:55.837 DBUG 35067@46: com.llamalab.automate.ext.media: not installed
2018-08-24 10:42:55.838 DBUG 35067@46: com.llamalab.automate.ext.network: uid=10028, WRITE_SETTINGS=false, OPSTR_WRITE_SETTINGS=0, canWrite=false
2018-08-24 10:42:55.839 DBUG 35067@46: com.llamalab.automate.ext.personal: not installed
2018-08-24 10:42:55.840 DBUG 35067@46: com.llamalab.automate.ext.settings: uid=10028, WRITE_SETTINGS=false, OPSTR_WRITE_SETTINGS=0, canWrite=true
2018-08-24 10:42:55.840 DBUG 35067@46: com.llamalab.automate.ext.storage: not installed
2018-08-24 10:42:55.841 DBUG 35067@46: com.llamalab.automate.ext.superuser: not installed
2018-08-24 10:42:55.841 DBUG 35067@46: com.llamalab.automate.ext.telephony: not installed

[Henrik "The Developer" Lindqvist]

I suspect the "Private settings" workaround may only work on Android 8.1

Anyhow, next release will include yet another workaround.

[mouta...@gmail.com]

Thanks for this promising reply.
My phone is running Oreo 8.0.0 and the private option didn't solve the problem.
Looking forward testing the new version.
Luc

[lars....@googlemail.com]

Unfortunately, against my previous reply. The problem appeared again after I restarted ma phone after several days. I had again to deinstall and reinstall probate settings and now it seems to work again....

[Henrik "The Developer" Lindqvist]

Opt-in for the Alpha and test the new workaround:
https://play.google.com/apps/testing/com.llamalab.automate

[wesse...@gmail.com]

Hi Henrik,
Thanks a lot. After lot in for the Alpha,I was able to start and stop the WLAN Hotspot through automate again.

I am running a Samsung Note8 with Android 8.0.0

Regards Björn

[dawid...@gmail.com]

Thank you for you answer, that what i do, i used ADB. i add you the star :D

Le vendredi 8 juin 2018 21:50:09 UTC+2, Henrik "The Developer" Lindqvist a écrit :

Some users are having issue with the transition from the old permission add-ons, to the (new) Android 6+ run-time permission model, resulting in security failures such as:

java.lang.SecurityException: com.llamalab.automate.ext.* was not granted this permission: android.permission.WRITE_SETTINGS.

The issue seems to mostly affect the Wi-Fi hotspot set state block, if you're using an Android 8+ device, try enabling the "Private setting" or "Extension" option in the "Wi-Fi hotspot workaround" setting.

If that doesn't work, the issue seems to be (temporarily) fixed by ensuring that the main app package is installed first, i. e.:

1. Stop all flows
2. Make a backup, see settings
3. Uninstall Automate
   
4. Uninstall all permission add-ons, see system Apps settings.
   
5. Reboot the device
6. Reinstall Automate
7. Restore backup
   
8. Optional, use ADB to grant "superuser" permission, see:
   https://groups.google.com/d/topic/automate-user/HUm7yZPv578/discussion
9. Grant "privileges" required by flows
   
10. Restart flows

[Luc M.]

Thanks for the version 1.15.0 which solves the problem of enabling/disabling bluetooth tethering.
Here is how I did:
-make a backup,
-uninstall all Automate privilege apps,
-install Automate update
-restore backup
-check all flows to enable every privilege needed
Even after a reboot, the block doesn't crash any more.
Thanks for the turnaround.
Luc

[Luc M.]

My bad, I spoke too fast. The problem is still here with bluetooth tethering even with private privilege enabled:
2018-09-14 11:25:13.547 FAIL 7630@3: java.lang.SecurityException: com.llamalab.automate.ext.network was not granted this permission: android.permission.WRITE_SETTINGS.

Can you please have a look?
Thanks

[Henrik "The Developer" Lindqvist]

Yeah, the workarounds only work for the Wi-Fi hotspot sets state block. I'll try it for BT as well.

[zsolt...@gmail.com]

Same here, switching on bt tethering kills its thread.
Interesting: switching bt off works.

[Henrik "The Developer" Lindqvist]

Any error message?

[Maarten]

I still cannot get Wifi hotspot to work.

Android 7.0

Samsung A5 (2016)

Automate 1.15.0

I followed the steps as described. Granted access local network. Without the Wi-Fi workaround setting, I get the WRITE_SETTING security exception. If I set the Wi-Fi workaround setting to extension, I get "Neither user 10219 nor current process has android.permission.ACCESS_NETWORK_STATE". I tried a number of permutation in order and reboots, also tried granting "modify system settings" and "modify private settings". But it does not help. The error has now changed to "You need MANAGE_USERS or CREATE_USERS permission to: query user". If now remove the permissions an turn off the Wi-Fi workaround, just granting access local network, it stays with this last error message.

Any ideas?

[Henrik "The Developer" Lindqvist]

Try this updated extension:

https://drive.google.com/file/d/1mK0EPM0Paa4-r7gTMrcKplkkI1_i22zZ/view?usp=sharing

[Luc M.]

Probably the same as mine:
2018-09-22 17:00:02.264 FAIL 7589@3: java.lang.SecurityException: com.llamalab.automate.ext.network was not granted this permission: android.permission.WRITE_SETTINGS.

[zsolt...@gmail.com]

2018-09-17 07:00:32.903 INFO 1@6: Bluetooth tethering set state
2018-09-17 07:00:32.944 FAIL 1@6: java.lang.SecurityException: com.llamalab.automate.ext.network was not granted this permission: android.permission.WRITE_SETTINGS.
2018-09-17 07:00:32.966 INFO 1@6: Stopped by failure
...
2018-09-20 07:00:10.731 INFO 5@6: Bluetooth tethering set state
2018-09-20 07:00:10.842 FAIL 5@6: java.lang.SecurityException: com.llamalab.automate.ext.storage was not granted this permission: android.permission.WRITE_SETTINGS.
2018-09-20 07:00:10.858 INFO 5@6: Stopped by failure
2018-09-20 07:30:12.967 INFO

-------
Sorry for slow response. So it's usually about storage but sometimes network permission.

[Henrik "The Developer" Lindqvist]

Next release will include workarounds for Bluetooth tethering too.