Android Debug Bridge (ADB) is a tool created by Google for developers to debug their applications and system, however, you may also control your STB using it. You can ADB to your devices by connecting through the network. This guide is to walk you through the steps required to how H200 can be controlled over the network.
An adb input event allows you to send certain events like channel or volume change on your device. Please see the following examples.
adb shell input keyevent 166
adb shell input keyevent 167
adb shell input keyevent 24
adb shell input keyevent 25
Sideload the given full OTA package
adb sideload ota.zip
Get packets installed
Prints all packages
adb shell pm list packages
See their associated APK file
adb shell pm list packages -f
To dump all services
adb shell dumpsys
Only list services, do not dump them
adb shell dumpsys -l
This command reboots your device in normal mode.
Android devices have a recovery mode, which is a special bootable partition. If you are encountering issues with your Android device, then you may be able to fix these problems by booting into recovery mode.
If you wish to reboot your device into recovery mode, then you can issue the following command:
adb reboot recovery
To factory reset your device you can issue the following command:
adb shell input keyevent 65535
Get STB properties
Gets the system properties, or lists them all
adb shell getprop
Show property types instead of values
adb shell getprop -T
How to collect Syslog
To run logcat through the adb shell, the general usage is:
[adb] logcat [<option>] ... [<filter-spec>] ...
You can run logcat as an adb command or directly in a shell prompt of your emulator or connected device. To view log output using adb, navigate to your SDK platform-tools/ directory and execute:
You can create a shell connection to a device and execute:
$ adb shell # logcat
For more ADB commands, please visit the android developers site: https://developer.android.com/studio/command-line/adb