# **Android Observability as Process**

**Introduction**
Qualcomm TPS android observability is distributed as a standalone application (APK) for the Android platform. The app is created to start during bootup. The app runs in background and report observability metrics independently without integrating the SDK in client application.
In order to be properly registered in the system, the app must be installed as a privileged system app signed with the platform key.

**Installation**
In order to be properly registered in the system, the app must be signed with the platform key and installed as a privileged system app in:

/system/priv-app/

**Configuration**
The app requires a config file to be installed at the following path:

/system/etc/qualcomm-obs.conf

The config file qualcomm-obs.conf should contain the following parameters:

ObsKey = <KEY>
ObsPeriod = 600

ObsKey should be populated with the key that you received from Qualcomm specified in the Implementation section.

ObsPeriod is the desired period of observability updates in seconds.

**Starting and stopping**

The following command can be used to start and stop the Observability service:

adb shell am start-service -n com.qualcomm.obs/.ObsService
adb shell am stop-service -n com.qualcomm.obs/.ObsService

**Logging**

To enable logcat logging, add the following parameters in the config file:

LogEnabled = true
LogLevel = DEBUG

The following log levels are supported:

- DEBUG
- INFO
- WARN
- ERROR

Last Published: Feb 18, 2026

[Previous Topic
Data delivery](https://docs.qualcomm.com/bundle/publicresource/80-87346-1/topics/Implementation.md) [Next Topic
Observability Metrics](https://docs.qualcomm.com/bundle/publicresource/80-87346-1/topics/Metrics.md)