ADB Usage
# ADB Usage
This article details the usage of Android Debug Bridge (ADB) for server administrators managing MediaWiki installations that interface with Android devices (e.g., for mobile app testing, debugging, or data synchronization). ADB is a versatile command-line tool that allows communication with a device. This guide assumes a basic understanding of command-line interfaces and server administration.
What is ADB?
Android Debug Bridge (ADB) is a command-line tool included with the Android SDK. It's primarily used for developers, but server administrators can leverage it for testing and troubleshooting applications interacting with the MediaWiki platform. It allows you to install and uninstall apps, execute shell commands, transfer files, and view device logs. Understanding LocalSettings.php configuration relating to mobile access is crucial alongside ADB.
Prerequisites
Before using ADB, ensure you have the following:
- **Android SDK Platform-Tools:** Download and install the Android SDK Platform-Tools from the official Android Developers website: [https://developer.android.com/studio/releases/platform-tools](https://developer.android.com/studio/releases/platform-tools).
- **ADB in your PATH:** Add the directory containing `adb` to your system's PATH environment variable. This allows you to run `adb` from any terminal window. Refer to your operating system's documentation for instructions on modifying the PATH variable.
- **Android Device:** An Android device connected to your server (either via USB or network). USB is generally more reliable for initial setup. Ensure USB debugging is enabled on the device (see below).
- **USB Drivers:** If connecting via USB, install the appropriate USB drivers for your Android device on the server.
- Ensure USB debugging is enabled.
- Verify the USB connection and drivers.
- Restart the ADB server: `adb kill-server` followed by `adb start-server`.
- Check Firewall configuration if using a network connection.
- **Testing Mobile App Authentication:** Use `adb logcat` to monitor authentication requests and responses between the mobile app and the MediaWiki API. This is especially useful when OAuth is configured.
- **Debugging Data Synchronization:** If your mobile app synchronizes data with MediaWiki, use `adb logcat` to track data transfer and identify any errors. Consider using API:REST API for data exchange.
- **Inspecting Application Storage:** Use `adb shell` to access the app's internal storage and examine data files. This is important when debugging database interaction or caching issues.
- **Simulating Network Conditions:** While not directly part of ADB, tools used *with* ADB can simulate different network conditions (e.g., slow internet) to test app behavior.
- Android Developers: [https://developer.android.com/studio/command-line/adb](https://developer.android.com/studio/command-line/adb)
- MediaWiki API documentation: API:Main page
- MediaWiki Mobile configuration: Mobile access
- Configuration values affecting mobile access.
- Telegram: @powervps Servers at a discounted price
Enabling USB Debugging
USB debugging must be enabled on your Android device. The exact steps vary by device and Android version, but generally involve:
1. Go to Settings > About Phone (or About Tablet). 2. Tap "Build number" seven times to unlock Developer options. 3. Go to Settings > Developer options. 4. Enable "USB debugging". You might also need to authorize your server's computer when prompted. See also Security Considerations for mobile access.
Basic ADB Commands
Here's a table of some common ADB commands:
| Command | Description |
|---|---|
| `adb devices` | Lists connected Android devices. Crucial for verifying connectivity. |
| `adb install |
Installs an APK file onto the device. |
| `adb uninstall |
Uninstalls an application from the device. |
| `adb shell` | Opens a shell session on the device, allowing you to execute commands directly. |
| `adb logcat` | Displays the device's system logs. Useful for debugging. |
| `adb pull |
Copies a file from the device to your server. |
| `adb push |
Copies a file from your server to the device. |
Connecting to a Device
After installing the SDK and enabling USB debugging, connect your Android device to the server via USB. Run `adb devices`. You should see your device listed. If not:
Advanced ADB Usage and MediaWiki
ADB can be used to test and debug mobile applications that interact with your MediaWiki installation. For example:
ADB over TCP/IP
If you need to connect to an Android device over a network (without USB), you can use ADB over TCP/IP.
1. Connect the device to the server via USB initially.
2. Run `adb tcpip 5555` (or another port number).
3. Disconnect the USB cable.
4. Find the device’s IP address.
5. Run `adb connect
The following table details the network setup:
| Parameter | Value |
|---|---|
| ADB TCP Port | 5555 (default, configurable) |
| Device IP Address | Obtain from device settings |
| Server IP Address | Server's IP address on the network |
| Firewall Rule | Allow traffic on port 5555 (or configured port) |
Troubleshooting
| Problem | Solution |
|---|---|
| Device not listed in `adb devices` | Check USB connection, drivers, USB debugging, restart ADB server. |
| ADB commands failing | Ensure ADB is in your PATH, device is authorized, and the correct package name is used. |
| Slow data transfer | Use USB connection if possible, optimize file transfer settings, check network bandwidth. |
| Connection refused (ADB over TCP/IP) | Verify IP address, port number, firewall settings, and that TCP/IP mode is enabled on the device. |
Further Resources
Intel-Based Server Configurations
| Configuration | Specifications | Benchmark |
|---|---|---|
| Core i7-6700K/7700 Server | 64 GB DDR4, NVMe SSD 2 x 512 GB | CPU Benchmark: 8046 |
| Core i7-8700 Server | 64 GB DDR4, NVMe SSD 2x1 TB | CPU Benchmark: 13124 |
| Core i9-9900K Server | 128 GB DDR4, NVMe SSD 2 x 1 TB | CPU Benchmark: 49969 |
| Core i9-13900 Server (64GB) | 64 GB RAM, 2x2 TB NVMe SSD | |
| Core i9-13900 Server (128GB) | 128 GB RAM, 2x2 TB NVMe SSD | |
| Core i5-13500 Server (64GB) | 64 GB RAM, 2x500 GB NVMe SSD | |
| Core i5-13500 Server (128GB) | 128 GB RAM, 2x500 GB NVMe SSD | |
| Core i5-13500 Workstation | 64 GB DDR5 RAM, 2 NVMe SSD, NVIDIA RTX 4000 |
AMD-Based Server Configurations
| Configuration | Specifications | Benchmark |
|---|---|---|
| Ryzen 5 3600 Server | 64 GB RAM, 2x480 GB NVMe | CPU Benchmark: 17849 |
| Ryzen 7 7700 Server | 64 GB DDR5 RAM, 2x1 TB NVMe | CPU Benchmark: 35224 |
| Ryzen 9 5950X Server | 128 GB RAM, 2x4 TB NVMe | CPU Benchmark: 46045 |
| Ryzen 9 7950X Server | 128 GB DDR5 ECC, 2x2 TB NVMe | CPU Benchmark: 63561 |
| EPYC 7502P Server (128GB/1TB) | 128 GB RAM, 1 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (128GB/2TB) | 128 GB RAM, 2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (128GB/4TB) | 128 GB RAM, 2x2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (256GB/1TB) | 256 GB RAM, 1 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (256GB/4TB) | 256 GB RAM, 2x2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 9454P Server | 256 GB RAM, 2x2 TB NVMe |
Order Your Dedicated Server
Configure and order your ideal server configurationNeed Assistance?
⚠️ *Note: All benchmark scores are approximate and may vary based on configuration. Server availability subject to stock.* ⚠️