Android 10
225 views
Skip to first unread message
the_...@onlinehome.de
Dec 11, 2019, 1:28:42 PM12/11/19
to Automate
Hy,
after updating my S10 to Android 10 a well tested flow for setting my AOD does not work.
It seems like setting modifying a system setting are broken... maybe due update
It seems like setting modifying a system setting are broken... maybe due update
System setting set
2019-12-11 18:34:13.19712 FAIL 2371@52:
android.os.RemoteException: Remote stack trace: at
android.content.ContentProvider.validateIncomingAuthority(ContentProvider.java:2230)
at
android.content.ContentProvider.access$200(ContentProvider.java:108)
at
android.content.ContentProvider$Transport.call(ContentProvider.java:472)
at
android.content.ContentProviderNative.onTransact(ContentProviderNative.java:277)
at
android.os.Binder.execTransactInternal(Binder.java:1021)
Any ideas?
Thank you for helping!
Henrik "The Developer" Lindqvist
Dec 11, 2019, 4:06:10 PM12/11/19
to Automate
What category is the setting in?
As a test, try using the Shell command block instead, to execute:
setting put <category> <setting name> <value>
the_...@onlinehome.de
Dec 12, 2019, 7:46:48 AM12/12/19
to Automate
The Block is Settings: System settings set
As for the shell command block...I have totally no idea how to use it... sorry
As for the shell command block...I have totally no idea how to use it... sorry
Henrik "The Developer" Lindqvist
Dec 12, 2019, 8:30:37 AM12/12/19
to Automate
If you click the System setting set block, what is the Category, Name and Value field set to?
the_...@onlinehome.de
Dec 12, 2019, 10:36:30 AM12/12/19
to Automate
The category is system, name is "aod_mode" value is 0
The modify system is on (I even put it off and on again) before Upgrade it worked well... no reboot etc did help.
The modify system is on (I even put it off and on again) before Upgrade it worked well... no reboot etc did help.
Henrik "The Developer" Lindqvist
Dec 16, 2019, 8:53:20 AM12/16/19
to automa...@googlegroups.com
Seems like the workaround for the "private" settings bug has been blocked in Android 10, at least for how the System setting set block did it.
A new settings extension add-on will likely have to be released, to work for users without ADB.
If you grant Automate the "modify secure settings" privilege, the Shell command should work to execute: settings put system aod_mode 0
detlev....@googlemail.com
Jan 14, 2020, 7:53:46 AM1/14/20
to Automate
Hello,
I have exactly the same error. Galaxy S10 with Android 10 and latest patch.
Modifying AOD with a flow: Category: System - Name: ="aod_mode" - Value 0 or 1
the above Java exception is thrown.
I connect my S10 to the ADB shell and put
pm grant com.llamalab.automate android.permission.WRITE_SECURE_SETTINGS
pm grant com.llamalab.automate android.permission.CHANGE_CONFIGURATION
in.
But still the same error...
on the adb shell "settings put system aod_mode 0" is working
Thanks in advanced for any help.
Henrik "The Developer" Lindqvist
Jan 14, 2020, 3:00:33 PM1/14/20
to Automate
Please try the latest Alpha, opt-in at:
detlev....@googlemail.com
Jan 15, 2020, 3:14:27 AM1/15/20
to Automate
Perfect!
with this version it works again as exspected.
Many thanks for the fast and good support.
Best regards
Reply all
Reply to author
Forward
0 new messages