Completed
Add support to trigger Samsung Modes & Routines
Samsung's Modes & Routines (M&R) app exposes a few different hidden content providers that can be used by Tasker to run Routines and turn Modes on/off. The advantage of M&R is that it's a system app, so it can control many things that Tasker cannot do alone. For instance, users can toggle Wi-Fi or disconnect a Bluetooth device without needing Shizuku/ADB Wi-Fi. Additionally, there are many other Samsung-specific actions (not going to list them all here). If Tasker could tap into these actions, it would really open up the door for Samsung users to automate things more easily and automate things that weren't possible before.
I tested this method out in a simple Android project that displays a menu of all the manual routines, and when the user selects one, it runs that Routine.
Documentation
AndroidManifest.xml
<uses-permission android:name="com.samsung.android.app.routines.permission.READ_ROUTINE_INFO" />That permission allows you to access a few content providers which allow you to find and/or run the user's modes and routines.
To GET Routines:
context.contentResolver.query(uri, null, null, null, null)Valid URIs:
- content://com.samsung.android.app.routines.externalprovider/routine_list?routine_type=normal&condition_type=manual
- condition_type can also be "auto," but this is not useful for Tasker because "auto" routines cannot be run manually
- Also accepts query param "only enabled=0" which will return disabled routines as well
- content://com.samsung.android.app.routines.routineinfoprovider/manual_enabled_routines
Columns are: {"uuid", "name", "icon_resource_id", "icon_color", "is_running", "is_enabled", "is_oneoff"}
To GET Modes AND Routines:
context.contentResolver.query(uri, null, null, null, null)Valid URIs:
- content://com.samsung.android.app.routines.domainmodel.routinetestprovider/routine_uuid_list
- Also returns automatic routines
Columns are {_uuid, name}
To GET Modes:
I couldn't find a content provider with a URI that is externally accessible which returns just the modes. However, you could "get all," "get manual routines" (condition_type=manual), and "get auto routines" (condition_type=auto), then remove the overlapping routines to get just the modes.
I've also found full UUIDs for the modes in logcat. The standard modes seem to be numbered 100, 101, 102, etc. Custom modes have random UUIDs. You could have the user navigate to the modes screen and read from logcat. You cannot do this for the routines, as it doesn't show the full UUID, only the first 6 digits. The content provider is a safer way to get the routines anyway.
Finally, this may not even be necessary because you can use a Routine to turn a Mode on/off. It's slightly annoying because you need a Routine for each Mode you want to toggle with Tasker, but not impossible.
To RUN/STOP a Mode or Routine:
use context.contentResolver.call(Uri uri, String flag, null, Bundle bundle)Valid URIs:
- content://com.samsung.android.app.routines.externalprovider
- Flag should be one of {"start_manual_routine", "toggle_manual_routine", "end_manual_routine"}
- Bundle should have one long of key "uuid" and value should be UUID of routine to be started/toggled/stopped
- content://com.samsung.android.app.routines.domainmodel.routinetestprovider
- Flag should be one of {"run_routine", "stop_routine"}
- Bundle should have one long of key "_uuid" and value should be UUID of routine to be started/toggled/stopped
My guess is the "externalprovider" URIs are preferred/intentional, as they are labeled "external". However, "routinetestprovider" (seems like a debugging/test tool of sorts) is the only way to get Modes indirectly from a content provider. Weirdly, "routineinfoprovider" is externally accessible, but "routinemodeprovider" is not.
Viewing M&R Source Code
I found the source code by pulling the APK:
- adb shell pm path com.samsung.android.app.routines
- adb pull <path from step 1>
Then I decompiled the APK with JADK. I looked in the manifest for services, receivers, and providers. Most of them require permissions that are locked to signature/system access only, the ones I found that are externally accessible were listed above.
