Enable and Use Developer Options

This guide is intended for users who are aware of the risks associated with accessing developer options and have familiarized themselves with the capabilities of ADB. Volla assumes no liability for data loss or device issues resulting from these actions.

Using this tutorial is at your own risk and is expressly not recommended for users without experience.

Activating Developer Mode

• Open Settings:
  • Go to the "Settings" app on your Volla Phone (often represented by a gear icon).
• Navigate to "About Phone":
  • Scroll down and select "About Phone".
• Find the Build Number:
  • Look for an entry called "Build Number" at the bottom of the list.
• Tap the Build Number seven times:
  • Quickly tap the "Build Number" seven times in succession. A message like "You are now a developer!" or "Developer mode has been activated" will appear. On some devices, you may need to enter a PIN or password.
• Return to Settings:
  • Go back to the main Settings menu. The Developer Mode ("Developer Options") should now be visible under "System".
• Open Developer Options:
  • Tap "Developer Options" to view the available settings.

Most Common Developer Mode Settings

Be cautious, as changes can affect device functionality!

• Memory:
  • Displays the usage/load of the device's RAM.
• Bug Report:
  • Allows you to choose between different modes for generating bug reports.
• Stay Awake:
  • Description: Keeps the screen on while charging. Useful for app development or data transfer between the phone and a desktop.
• USB Debugging:
  • Description: Enables communication between the device and a computer via ADB (Android Debug Bridge), e.g., for development or rooting.
  • Enable: Toggle the switch next to "USB Debugging" after connecting the device to a PC via USB.
  • Tip: Often used for app development or data recovery.
• Adjust Animations:
  • Description: Modifies the speed of transition animations (e.g., window animations, transition animations).
  • Setting: Look for "Window Animation Scale", "Transition Animation Scale", and "Animator Duration Scale". Default is 1x; set to 0.5x for a faster feel or "Off" for no animations.
  • Tip: Many users disable animations to make the device feel "faster".
• OEM Unlocking (for highly experienced users only):
  • Description: Allows unlocking the bootloader, e.g., for installing custom ROMs or gaining root access.
  • Enable: Toggle the switch (if available; not visible on all devices).
  • Note: This may void the warranty and requires caution, as it can lead to data loss.
• Force GPU Rendering:
  • Description: Uses the GPU instead of the CPU for 2D rendering to optimize performance.
  • Enable: Toggle "Force GPU Rendering" on.
  • Note: May cause issues on older devices.
• Limit Background Processes:
  • Description: Sets the number of apps allowed to run in the background.
  • Setting: Choose an option (e.g., "Max. 2 Processes" or "Standard Limit").
  • Tip: Can save battery life but may delay notifications.
• USB Configuration:
  • Description: Changes the default behavior when connecting to a PC (e.g., MTP for file transfer, charging only).
  • Setting: Select the desired option from the list.
• Disable Developer Mode (if needed):
  • Go to Developer Options and toggle the main switch off to hide the options. The Build Number activation persists until the device is reset.

Important Notes

• Caution: Changes in Developer Mode can make the device unstable or cause data loss (e.g., with OEM Unlocking).
• Security: Enable USB Debugging only when necessary, as it poses a security risk.

Explanation of USB Debugging

USB Debugging is a feature in Android’s Developer Mode that enables direct communication between an Android device and a computer via a USB connection. It relies on the Android Debug Bridge (ADB), a command-line tool that allows developers (and advanced users) to interact with the device, execute commands, install apps, or retrieve system information. In short: USB Debugging creates a "debugging bridge" that lets you control your device from a PC.

What is USB Debugging used for?

USB Debugging serves various purposes, depending on whether you're a developer, power user, or simply curious. Here are the most common use cases:

• App Development and Testing:
  • Developers use USB Debugging to test apps directly on a physical device instead of relying on an emulator.
  • With tools like Android Studio, they can load code onto the device and analyze errors (debugging) in real-time.
• Troubleshooting:
  • You can retrieve logs (log files) from the device to investigate issues like app crashes.
• File and System Access:
  • Via ADB, you can copy files, execute system commands, or create backups that are normally inaccessible.
• Rooting and Modification:
  • For advanced users, USB Debugging is often a step toward gaining root access or installing custom ROMs.
• Screen Recording or Control:
  • Tools like "scrcpy" use USB Debugging to mirror the screen to a PC or control the device from the computer.

How does USB Debugging work?

• Prerequisites:
  • Developer Mode must be activated (see my previous guide).
  • A USB cable and a computer with installed ADB (part of the Android SDK or downloadable separately) are required.
• Activation:
  • Go to Developer Options and toggle the "USB Debugging" switch.
  • Connect your device to the computer via USB.
  • On the VollaOS screen, a prompt appears: "Allow USB Debugging?" with the computer’s fingerprint. Confirm this (optionally select "Always allow").
• Communication via ADB:
  • On the PC, open a terminal (e.g., Command Prompt on Windows or Terminal on macOS/Linux) and enter ADB commands, e.g.:
    • adb devices: Lists connected devices.
    • adb shell: Opens a shell on the device.
    • adb install <app.apk>: Installs an APK file.
• Security Mechanism:
  • USB Debugging is only active when the device is unlocked and the connection is authorized, preventing misuse.

Example: A Simple ADB Command

Assuming USB Debugging is enabled and your device is connected:

• Open a terminal on the PC.
• Enter: adb devices
• Result: A serial number like "1234567890abcdef device" indicates the connection is established.
• Test further, e.g., with adb shell ls, to open a shell.

Advantages and Risks

Advantages:

• Direct device access for development or diagnostic purposes.
• Flexibility for power users, e.g., removing bloatware with ADB commands.

Risks:

• Security: If USB Debugging remains enabled and the device is connected to an untrusted PC, unauthorized access could occur.
• User Error: Incorrect ADB commands could damage the system (e.g., by deleting critical files).

Tip: Disable USB Debugging when not needed to minimize risks.

Wireless Debugging

Wireless Debugging is an extension of traditional USB Debugging, introduced with Android 11. It allows communication between a Volla Phone and a computer over a Wi-Fi connection instead of a USB cable. Like USB Debugging, it relies on the Android Debug Bridge (ADB) but eliminates the need for a physical connection. The goal is to provide developers and advanced users with more flexibility. In short: Wireless Debugging lets you debug, execute commands, or install apps wirelessly over your Wi-Fi network.

What is Wireless Debugging used for?

The use cases are similar to USB Debugging, but without a cable:

• App Development: Developers can test apps directly over Wi-Fi.
• Troubleshooting: Read logs or analyze system issues.
• Screen Mirroring: Tools like "scrcpy" work wirelessly to mirror the screen to a PC.
• File Access: Transfer files or execute system commands.
• Convenience: No cable required – ideal when the device is not near the PC.

The main advantage is convenience: You can move your device freely while controlling it from the computer.

Prerequisites

• Android Version: At least Android 11 (older versions do not support this natively).
• Developer Mode: Must be activated (see my first guide).
• Wi-Fi: The device and computer must be on the same Wi-Fi network.
• ADB: Installed on the computer (either via the Android SDK or as a standalone tool).

How do I set up Wireless Debugging?

1. Open Developer Options

• Go to Settings > Developer Options on your Volla Phone (if not visible, activate Developer Mode by tapping the Build Number seven times, as described earlier).

2. Enable Wireless Debugging

• Scroll to "Wireless Debugging" in Developer Options (often under "Debugging" or "Network").
• Toggle the switch next to "Wireless Debugging" on.
• Tap "Wireless Debugging" to open its settings.

3. Pair the Device

There are two ways to connect the device to the computer:

Option A: Pairing with Pairing Code (easier method)

• On the device: Tap "Pair device with pairing code" in the Wireless Debugging settings.
• A pairing code (e.g., "123456") and an IP address with port (e.g., "192.168.1.100:37000") will appear.
• On the computer:
  • Open a terminal.
  • Enter: adb pair <IP-address>:<port> (e.g., adb pair 192.168.1.100:37000).
  • Enter the displayed pairing code when prompted.
  • Confirm on the device if a security prompt appears.

Option B: Direct Connection (without pairing code)

• Note the IP address and port under "Wireless Debugging" (e.g., "192.168.1.100:5555").
• On the computer:
  • Enter: adb connect <IP-address>:<port> (e.g., adb connect 192.168.1.100:5555).
  • Note: This only works if the device was previously authorized via USB or the connection is already trusted.

4. Verify Connection

• Enter in the terminal: adb devices.
• If successful, you’ll see, e.g., "192.168.1.100:5555 device" – the device is connected.

5. Usage

• You can now execute ADB commands like adb shell, adb install, or adb logcat wirelessly.

Important Notes

• Stability: The connection may be unstable if the Wi-Fi network is weak or overloaded. USB is often more reliable.
• Security: Anyone on the same Wi-Fi network could theoretically access your device if they know the IP and port. Disable Wireless Debugging when not needed.
• Battery: Wireless Debugging can drain the battery faster, as the device constantly communicates with the network.
• Port: The port (e.g., 5555) may vary. Always check it in the Wireless Debugging menu.

Example: Establishing a Connection

• Device shows: IP "192.168.1.100" and port "37000" with pairing code "123456".
• Terminal: adb pair 192.168.1.100:37000
• Input: 123456
• Terminal: adb devices → Result: "192.168.1.100:37000 device"
• Test: adb shell → You’re in the device’s shell!

Advantages and Disadvantages

Advantages:

• No cable needed, offering more freedom of movement.
• Ideal for devices not near a USB port.

Disadvantages:

• Dependent on Wi-Fi quality.
• Slightly more complex to set up than USB Debugging.
• Security risks in public networks.

Troubleshooting

• No connection?
  • Ensure both devices are on the same Wi-Fi network.
  • Check that the firewall on the PC isn’t blocking ADB.
• Pairing code not displayed?
  • Restart the Wireless Debugging option or the device.
• Connection drops?
  • The IP address may change (dynamic IP). Use a static IP or check it regularly.

This guide is intended for users who are aware of the risks associated with accessing developer options and have familiarized themselves with the capabilities of ADB. Volla assumes no liability for data loss or device issues resulting from these actions.