ADB Wi-Fi Setup Guidefor Smarter + Tasker Integration
Enable advanced automation features in your Uber Driver app with this comprehensive, no-computer-required setup guide.
What You'll Achieve
Before You Begin
Tasker (US $3.49 one-time purchase) is required for Smarter's automation features
You'll need to re-establish the ADB connection after each device restart.
Tasker support cannot assist with Smarter configuration. Please use the Smarter community for setup help.
Setup Instructions
Follow these steps carefully. All commands are executed in Termux.
Install Termux & ADB Tools
Install Termux from the Google Play Store:
Install Termux from Google PlayOpen Termux and run these commands:
pkg update -ypkg install android-tools -yTroubleshooting: If Android tools fail to install, try: pkg install adb
Verify installation with:
adb versionEnable Wireless Debugging
Navigate to your device settings:
Turn on Wireless debugging and keep this screen open for the next step.
Note: Don't have Developer options? Go to About Phone and tap Build Number 7 times to enable it.
Establish ADB Wireless Connection
Important: This connection process must be repeated after each device restart.
Use split-screen mode to easily work with both Termux and the wireless debugging settings:
- In the wireless debugging window, tap "Pair device with pairing code"
- Take note of the displayed IP address, port number, and 6-digit pairing code
- Switch to the Termux window and enter the pairing command:
adb pair [IP_ADDRESS]:[PORT]# Example: adb pair 192.168.1.120:37487When prompted, enter the pairing code you noted earlier. Wait for the confirmation that pairing was successful.
Complete ADB Connection
After pairing, return to the wireless debugging screen. Look for the connection details (different from the pairing information) that should now be displayed.
adb connect [IP_ADDRESS]:[PORT]# Example: adb connect 192.168.1.120:41235Important: The IP address and port for this connection step are different from the pairing step. Make sure to use the connection details displayed on the wireless debugging screen after pairing is complete.
Configure ADB for Future Connections
Now set ADB to listen on a standard port (5555) for easier future connections:
adb tcpip 5555restarting in TCP mode port: 5555What this does: This command configures ADB to restart and listen on TCP port 5555. After this step, future connections (after device reboots) will use port 5555 instead of the random port assigned earlier.
Grant Write Secure Settings Permission
This permission allows Tasker to modify system settings required for advanced automation features:
adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGSWhy this is needed: WRITE_SECURE_SETTINGS allows Tasker to control system-level settings like display timeout, rotation lock, and other features that Smarter uses for automation.
You should see no output if successful. This means the permission was granted correctly.
Import the Tasker Automation Profile
Now that Tasker has the necessary permissions, import the pre-configured automation profile:
Click the link below to download the profile:
Smarter Advanced Tasker Profile- Tap the link above - This will open Tasker and prompt you to import the profile
- Confirm import - When the import dialog appears, select Yes to proceed
- Wait for completion - Tasker will automatically install all necessary components
Note: This profile contains all the automation tasks and configurations needed for Smarter to work seamlessly with your Uber Driver app.
Setup Complete!
Your device is now fully configured for Smarter automation features.
The Smarter Advanced Tasker profile is installed and ready to use.
After Setup
You only need to run: adb connect [IP_ADDRESS]:5555 (using port 5555 as set in Step 5)
Steps 1-3, 5, 6, and 7 are one-time only. After Step 5, you'll use port 5555 for all future connections.
The WRITE_SECURE_SETTINGS permission persists until Tasker is uninstalled.
The imported profile will automatically handle all Smarter automation tasks.
Troubleshooting
Ensure you have the latest version of Tasker installed. Older versions may not support the profile format.
Ensure you're connected via ADB (Step 4) before running the permission command. The device must show as "connected" in Termux.
Verify ADB installation in Step 1. Run adb version to confirm.
Make sure both devices are on the same Wi-Fi network and wireless debugging is still enabled.
If you can't connect to port 5555 after a restart, you may need to repeat Steps 3-4 to re-pair, then run adb tcpip 5555 again.