As it turns out, it is not trivial to control the audio volume of an Android device using ADB. At the time of writing, the only way appears to be using the service tool. Actually, the service command allows to 'connect' to a number of services (104 on Android 6.0.1) and invoke functions. Not knowing much about this tool, I managed to completely mute all sounds and speakers of my Nexus 5, and I was stuck without any sound for quite some time. I did not find a way to unmute the sound from within the system UI, so I got to dive a little deeper into this.

Hard Disk Serial Number Changer (Size 652 KB) is an application with a pretty self-explanatory name, as it allows users to change the serial number of their hard disk. Here is the complete list of ADB Commands and Fastboot Commands with its use cases and functions or operations it performs. In the Login Window set the 'Connection Type' to 'Android over ADB' and provide the path to the Android SDK. This path will be saved to the user preferences and it will get populated automatically onwards. If you have two or more Android devices connected to the computer set the 'Device Serial No.' Field to the serial number of your device. If I change it it DB then I have to reboot the device for the changes to be. For example, when i use the adb 'devices' command, the serial number of my.

If you know which service you want to use, you then need to find its interface declaration. The command

gives you a list of all services with the associated interfaces, if applicable:

For me, the audio service was relevant, which appeared at index 32. The associated interface is android.media.IAudioService, so the next thing you will want to do is find the source code of that file. And, even more importantly, find the correct version of that file (this was my mistake in the first place). For 6.0.1, you can find the interface declaration here. If you select a different branch on GitHub, you will see that the file differs from release to release.

In order to call a function of the interface, we need to know its index in the interface declaration. For example, to mute all sound, I will use IAudioService.setMasterMute. This function is the 8th method in the interface declaration. We will need this index soon, and it appears to start with 1 (so the first function has the index 1, not 0!). Additionally, we need to supply the correct arguments to the function. The declaration looks like this:

We will only supply the first two arguments, which are a boolean and an integer, which are both treated as integers for now.

In the ADB shell, the command

mutes all sounds on my Nexus 5 (6.0.1). service call audio is self explanatory, 8 is the function index, i32 1 represents the boolean value true and i32 0 represents the integer 0 for the flags parameter.

We can use the function IAudioService.isMasterMute to verify the result (or you could just try to make a call or watch a video, you should hear nothing, no matter what you set your volume to). Its signature is simple:

It is the 7th function in the interface, so we can call it using

After issuing the command, it should output something like

Note that the last digit is set to 1, and as isMasterMute() should return a boolean, we interpret this as true.

Unmuting is as simple as muting the device:

Again, use isMasterMute() to verify the result:

All zeroes represent the value false, so the result is correct!

Basically, whenever possible. The command and the interfaces are documented poorly and they are subject to change from release to release. You can use the command for manual debugging (and that might be the reason it was developed), but if you intend to use it in scripting, you will eventually run into problems. You need to change the command for each release, possibly even depending on the device, and I have no idea how much CyanogenMod and friends care about such compatibility. Many features are available without using service, and if there is a better interface to it, use it.

The Android Debug Bridge (ADB) is a versatile command line tool that lets you communicate with and control an Android-powered device over a USB link from a computer. It comes along with other useful tools and code bundled with the Android Software Development Kit (SDK).

The ADB program includes three components:

A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.

Setting Up ADB

On Windows and Linux

If you installed the Android SDK, the Android Debug Bridge will already be installed along with it. Otherwise, follow our guide on installing the Android SDK.

On Mac

If you have already downloaded the Android SDK, launch the SDK Manager by typing into a Terminal window:

<sdk>/tools/android

where <sdk> is the path to the tools directory. For example, if the Android SDK is located on the desktop, then you have to type into the terminal window:

/Users/MyName/Desktop/android-sdk-mac_86/tools/android

As soon as the SDK Manager is launched, click “Available packages”, then “Android Repository.” When the list of available packages pops up, choose the offered revision of “Android SDK Platform-tools”. Click “Install Selected.” If it is installed, the adb executable binary will be located in the platform-tools subdirectory.

If you don’t have the Android SDK installed yet, download its latest version and unzip it into an appropriate destination folder then follow the instructions above.

We want to make sure that ADB is now working. First, see to it that your Android device is set up for debugging. On your Android device running Gingerbread, go to the Settings > Applications > Development screen and make sure “USB Debugging” is checked. If you’re already on Ice Cream Sandwich, go to Settings > Developer options and tick “Android debugging” or “USB debugging.”

Connect your computer and Android device with a USB cable. Then, open a terminal on your computer and run the following command:

adb devices

You should see something like this:

List of devices attached XXXXXXXXXXXX device

A result like that (where the X’s represent your device’s actual serial number) confirms that your ADB is set up and working.

Learning the Codes

Now that ADB is already set up on your machine, you might want to know how to use its various flags and command options.

Flags

-d: directs command to the only connected USB device; returns an error if more than one USB device is present.
-e: directs command to the only running emulator; returns an error if more than one emulator is running.
-s <serial number>: directs command to the USB device or emulator with the given serial number. Overrides ANDROID_SERIAL environment variable.
-p <product name or path>: simple product name like ‘sooner’, or a relative/absolute path to a product out directory like ‘out/target/product/sooner’. If -p is not specified, the ANDROID_PRODUCT_OUT environment variable is used, which must be a

Adb Change Serial Number Android