Complete guide to Developer Options for improved performance

Android Guides » Android Devices » Complete Guide to Developer Options for Improved Performance

If your Android phone is lagging, slow to open apps, or overheating, you can probably give it a significant boost by tweaking a few hidden settings. These settings are located within Developer Options , a menu that might seem intimidating at first glance, but when used correctly, can greatly improve performance, battery life, and even gaming.

In this guide, we'll see, step by step, how the Developer Options screen works to improve performance , how to activate it on almost any device (Pixel, Samsung, OnePlus, Wear OS, etc.), which settings are safe to change and which are best left alone. You'll also see some more advanced ADB tricks to get even more out of your phone and measure performance if you feel like tinkering a bit.

How to enable Developer Options on Android?

Before changing anything, you first need to unlock this hidden menu. Android hides it precisely to prevent a distracted user from accidentally touching something important, but the activation process is very simple: you just need to keep repeating the build number.

In Android 4.1 and earlier versions, the developer options menu was visible by default. From Android 4.2 onwards, it must be enabled manually, and the exact path depends on the manufacturer. However, the idea is always the same: locate the build number within the system information and tap it repeatedly.

Typical paths to find the build number

According to the manufacturer, the build number option is hidden in slightly different areas of the settings menu. Here are some common examples so you don't have to search blindly:

• Google Pixel (phone): Settings > About phone > Build number.
• Google Pixel WatchSettings > System > About > Versions > Build number.
• Samsung Galaxy S8 and later: Settings > About phone > Software information > Build number.
• LG G6 and later: Settings > About phone > Software information > Build number.
• HTC U11 and later: Settings > About > Software information > More > Build number, or Settings > System > About phone > Software information > More > Build number.
• OnePlus 5T and later: Settings > About phone > Build number.

Once you locate the build number, the trick is to tap it seven times in a row . Halfway through, the system will display messages like "Five taps away from becoming a developer," so just keep tapping until you see the notification that developer options are enabled.

When you return to the previous settings screen, you'll see a new menu called Developer options (sometimes under System > Advanced). At the top of this menu, you'll find a master switch that allows you to turn the set of options on or off; for any changes to take effect, this switch must remain on.

Enable USB debugging and wireless debugging

One of the key settings in this menu is USB debugging . It's the gateway for tools like Android Studio or ADB on your computer to communicate with your mobile device and execute advanced commands, create backups, capture the screen, or debug apps in real time.

The location of USB debugging varies slightly depending on the Android version, but it's always within Developer Options. Here are the most common paths so you don't have to delve too deeply:

• Wear OS 6 (API 36 and later)Settings > Developer options > ADB debugging.
• Android 9 and laterSettings > System > Advanced > Developer options > USB debugging.
• Android 8.0 and 8.1Settings > System > Developer options > USB debugging.
• Android 7.1 and earlierSettings > Developer options > USB debugging.

Regarding wireless debugging (via Wi-Fi), the concept is the same, only instead of relying on a USB cable, the mobile phone and computer communicate through the network:

• Android 16 (API 36 and later)Settings > System > Developer options > Wireless debugging.
• Wear OS 6 (API 36 and later)Settings > Developer options > Wireless debugging.

After enabling wireless debugging on your device, you'll need to pair it with your computer using ADB, following the on-screen wizard. This is very useful if you don't want to be tethered to a cable every time you want to run commands or test things with your phone.

General options useful for everyday life

Within the developer menu, there's a general options area that, while designed for programmers, is also incredibly useful for advanced users. One of the most practical features is the ability to add specific cards to the Quick Settings panel to activate developer functions without having to navigate through menus.

The process is simple: From Developer Options, click on the Quick Settings cards for developers and select the ones you want to have readily available. Then open the Quick Settings panel, enter edit mode (pencil icon), and drag those cards to the visible panel. When you're finished, click the pencil icon again, and the new layout will be saved.

In addition to those cards, it's helpful to know some general settings that can help you better control memory, generate error reports, or capture cleaner screenshots without notifications:

• Conference proceedings: Displays detailed statistics on RAM usage: average usage, performance, total available memory, free space, and the memory each app is consuming. Perfect for identifying which apps are using the most resources.
• Start bug reportThis generates a package of system and application logs that you can share with technical support or a developer. You'll see a notification to send the report when it's ready.
• System UI demo modeThis command is used to take cleaner screenshots. It activates a generic status bar, without low battery icons or notifications. It can be combined with demo mode commands via ADB, although these commands are only officially supported on Nexus and Pixel devices.
• Desktop Backup Password: allows you to set a password for backups made using ADB, so that the apps and exported data are protected.
• Do not deactivateThis feature keeps the screen on while the device is plugged in. Very useful if you're testing things, debugging, or leaving an app open for a long time.
• Bluetooth HCI RegistrationIf you enable "Enable Bluetooth Host Controller Interface (HCI) search logging," the system will save all Bluetooth HCI packets to the /sdcard/btsnoop_hci.log file. You can then analyze this file with programs like Wireshark to troubleshoot Bluetooth connection or performance issues.

Debug settings to fine-tune apps and performance

The debugging section offers tools to control how apps communicate with the system and the development computer. The most well-known setting here is, again, USB debugging, but there are some interesting extras when working with specific applications.

For example, if you select an app in the "Select application to debug" section, you can enable "Wait for debugger ." This way, the application won't fully launch until a debugger connects from your computer, which is great for catching hard-to-reproduce bugs, although for a typical user, this setting is usually unnecessary.

Network options to improve Wi-Fi, data, and Bluetooth audio

Another key area for optimizing the mobile experience is the network options . Here you can control everything from how the USB behaves when you connect the phone to the PC to the level of detail in Wi-Fi logs or the sound quality via Bluetooth.

In the USB section, you have the "Select USB settings" option, which defines how the computer will recognize the cable when you connect it. Typical options include charging only, file transfer (MTP), photo transfer (PTP), using the phone as a modem (RNDIS), or audio/MIDI connection. Setting this correctly prevents your phone from constantly asking what you want to do every time you connect it.

For wireless audio, Bluetooth options are especially useful if you have high-quality headphones and want to ensure you're getting the most out of their codec and sound depth. Key options include:

• Bluetooth audio codecThis allows you to force the codec to be used. You'll see options like SBC, AAC, aptX, aptX HD, or LDAC, each with its own balance between quality and bandwidth consumption.
• Bluetooth audio sampling rateThis adjusts how many audio samples per second are transmitted (e.g., 44,1 kHz, 48 kHz, etc.). The higher the value, the greater the potential quality, but also the more resources are consumed.
• Bits per sampleThis defines how many bits are used to encode each audio sample. 16 bits, 24 bits, etc. More bits mean better dynamic range, although transmission requirements increase.
• Channel mode: allows you to choose between mono and stereo; most users will want to leave it in stereo except in very specific cases.
• LDAC-specific settingsIf you use LDAC, you can choose whether to prioritize audio quality, connection stability, or an adaptive mode that balances both.

In addition to audio, this area includes options to control Wi-Fi and DHCP behavior :

• Wireless display certification: activates advanced menus related to Miracast and the Wi-Fi Display specification, intended more for testing than for everyday use.
• Detailed Wi-Fi LogThis increases the level of wireless network logging, adding data such as signal strength (RSSI) for each SSID. Useful if you want to troubleshoot connection drops or speed drops.
• Prioritize switching from Wi-Fi to mobile network: allows the system to switch to mobile data more efficiently when the Wi-Fi signal is poor, reducing interruptions in browsing or streaming.

Input options: taps and on-screen pointer

If you want to record tutorials or simply better understand how Android detects your gestures, the input options are especially useful. From here you can view taps, movements, and coordinates in real time.

With "Show Pressure" enabled, every time you touch the screen you'll see a small circle that follows the movement of your finger or stylus. This acts as a virtual pointer, perfect for recording videos where it's clear which part of the screen is being touched.

The "Pointer Location" setting goes a step further: it activates a bar at the top of the screen with the exact coordinates of your touches and traces lines on the panel following your movements. This tool is widely used for debugging problems with touch panels or gestures that aren't recognized correctly.

Drawing options: animations, design boundaries, and secondary screens

The drawing section contains several of the best-known tricks for making your phone "fly." These are settings that don't actually increase the processor's power, but they do reduce the feeling of sluggishness by shortening animation times and allowing you to better see how the interface behaves.

One of the most commonly used features is "Show Design Boundaries," which displays the margins, cutouts, and other contours of the user interface on the screen. It's ideal for app designers, as it allows them to check if elements are positioned and sized as intended.

In the same section, you'll find three key settings to enhance the feeling of fluidity: Window Animation Scale , Transition Animation Scale , and Animator Duration Scale . These are typically set to 1x by default. If you adjust them to 0,5x, animations will play twice as fast, giving you the impression that your phone responds much more immediately when opening apps, switching between them, or navigating menus. If you prefer to disable animations entirely, that option is also available, although it generally feels less natural in everyday use.

There are also other interesting tools, such as "Force right to left layout," which forces the interface to be rendered from right to left (intended for testing languages ​​such as Arabic or Hebrew), or "Simulate secondary displays," which generates an extra screen superimposed on the physical panel to simulate external displays using the Presentation API.

Hardware-accelerated and GPU rendering: where you can gain performance

Moving on to the hardware-accelerated rendering section , we find settings that can significantly improve the smoothness of scrolling, animations, and applications with many graphic elements, especially on mid-range or low-end devices.

Among the most interesting options is "Force GPU Rendering" (or similar names depending on the manufacturer's interface). Enabling this forces apps to draw most of the 2D interface using the GPU instead of the CPU. This can result in a smoother interface and more stable animations, freeing up the main processor for other tasks such as reading databases, design calculations, or responding to new user input.

However, it's important to keep in mind that on some devices, the GPU can consume more power than the CPU. Many users have estimated an increase in battery consumption of around 5-15% with this option enabled, especially on older phones. Therefore, it's generally recommended for phones with weaker CPUs, where the improved performance outweighs the extra power consumption, and less so for powerful multi-core processors where the system already has ample performance. If your device uses a Snapdragon processor and you want to reduce power consumption, check out how to improve your Snapdragon's battery life with undervolting and advanced settings.

Other options in this section that may interest you are:

• Choose GPU processor: in some models it allows changing the OpenGL graphics engine to Skia, useful for testing compatibility and performance with different engines.
• View GPU updates: highlights the areas of the screen that are being drawn by the GPU, to analyze the cost of certain visual elements.
• Debug GPU overlays: colors the pixels on screen based on the number of times they are redrawed in the same frame, helping to detect areas with redundant graphics work.
• Debug non-rectangular clipping operations: disables certain restrictions of the drawing area to test atypical clipping cases (highly geared towards debugging complex interfaces).
• Force MSAA 4x: Enables anti-aliasing (multisampling) in apps and games that use OpenGL ES 2.0. Improves the visual appearance of graphics, but can affect performance and increase power consumption, especially on low-end hardware.
• Disable HW overlaysThis forces apps to share video memory without using separate hardware layers. It's usually left disabled, as it involves more checks to prevent incorrect clipping and can negatively impact performance.

An additional audio-related setting is "Disable USB audio routing." With this enabled, the system stops automatically routing sound to external USB devices connected to the computer, which can interfere with apps that manage their own USB connections. Furthermore, since Android 11, when an app without RECORD_AUDIO permission attempts to access a USB audio device with capture capabilities, a notification appears requesting explicit permission from the user, who must grant it each time.

Real-time performance monitoring

If you want to monitor how the phone behaves while you play games or test an app, the monitoring options give you very clear visual data about performance, especially with regard to the GPU.

The most representative option is “GPU Profile Rendering”. If you choose the “On-screen as bars” mode, you’ll see vertical graphs over different areas of the interface, helping you see at a glance whether the phone is maintaining a stable rendering speed or if there are load spikes that could explain stuttering and frame drops.

Background app management and battery

In the Apps section , there are several useful levers for controlling the number of open processes and, consequently, the available RAM and energy consumption. This is especially helpful on phones with limited resources, where having too many apps running in the background can make the experience unbearable; clearing the cache can help.

One of the most straightforward options is "Background Process Limit." Here you can define how many processes Android can keep active simultaneously behind the main app. Options like "Maximum 2 processes" or "Maximum 3 processes" help free up memory for the app you're using, reducing forced closures or lag when switching apps, at the cost of some apps having to reload from scratch when you return to them.

Another interesting option is "Delete activities," which instructs the system to completely delete activities as soon as the user leaves the main view. This reduces background resource consumption and can slightly extend battery life, but it almost always requires the app to be restarted from scratch when the user returns.

You'll also find settings like "Reset ShortcutManager frequency limit during testing," which allows background apps to continue creating shortcuts until they reach the frequency limits again, or "Disable protections when sharing screen," which temporarily disables safeguards that normally hide sensitive content during screen sharing. The latter is intended for demonstrations and one-off testing only.

Advanced ADB tricks for optimization after an update

Beyond what can be directly adjusted on the phone, some users turn to ADB (Android Debug Bridge) to further fine-tune the system, especially after a major firmware update. Since Android 7.0, the system optimizes background apps over time, which can cause a feeling of sluggishness and overheating right after updating.

One way to speed up this process is to install the Android Platform Tools on your computer, enable USB debugging on your phone, and run a few specific commands. The flow is usually as follows:

• Install the platform tools from the official Android website (download and unzip the package for your operating system).
• Activate Developer Options and USB debugging on your mobile device, and connect it via cable.
• In the platform-tools folder, open a terminal and run adb devices; accept the authorization window on your mobile device.
• Use commands like adb shell pm disable-user com.android.traceur to disable certain plotting tools, or adb shell cmd package bg-dexopt-job to force the optimization of apps in the background.

Once these processes are complete (optimization can take a while depending on the number of installed apps), many users notice that performance returns to similar or better levels than before the update, and overheating is reduced because the system is no longer recompiling as many apps in the background. In addition, simple measures like occasionally restarting the phone can accelerate stabilization after the update.

Key developer settings to improve performance without complicating things

If you don't want to go crazy tweaking dozens of options, there are a few settings within Developer Options that make a big difference in perceived speed , memory management, and graphics performance, without needing to be a developer or delve into ADB:

• Reduce animation scales (window, transition and animator duration) from 1x to 0,5x so that everything moves much more smoothly.
• Limit background processes 2 or 3 on modest mobiles so that the current app has more resources and the battery lasts a little longer.
• Force GPU rendering to offload more graphics work to the graphics processor, smoothing out movements and animations, especially on devices with a somewhat weak CPU.

In addition to these, it's worth noting USB debugging (for its possibilities with ADB and backups), adjusting the log buffer size if you want to fine-tune things on high-end mobiles, or limiting network searches to reduce unnecessary consumption in areas with poor coverage.

By using Developer Options wisely, you can make your Android device feel faster, smoother, and more stable without installing anything unusual. Simply take advantage of built-in tools that, while designed for developers, are also a treasure trove of tricks for any user who wants to get the most out of their phone. Share this information so more users can learn about it.