Android Core

https://source.android.com/docs/core/
Admin
Android Core provides comprehensive documentation for developers on the fundamental architecture,...
Tokens:3,408,738
Snippets:19,038
Trust Score:10
Update:1 month ago
Show doc for...
Tokens:
Raw
### Example output of adb shell cmd overlay dump

Source: https://source.android.com/docs/core/runtime/rro-troubleshoot

Example output from the dump command. It shows the overlay is available for users 0 and 10, with mState STATE_MISSING_TARGET, meaning the target package isn't installed. The mState values help identify the cause: STATE_ENABLED/IMMUTABLE means enabled, STATE_NO_IDMAP indicates idmap setup issues, and STATE_UNKNOWN points to OverlayManagerService problems.

```text
com.android.car.rotaryplayground.googlecarui.rro:0 {
  mPackageName...........: com.android.car.rotaryplayground.googlecarui.rro
  mUserId................: 0
  mTargetPackageName.....: com.android.car.rotaryplayground
  mTargetOverlayableName.: car-ui-lib
  mBaseCodePath..........: /product/overlay/googlecarui-com-android-car-rotaryplayground/googlecarui-com-android-car-rotaryplayground.apk
  mState.................: STATE_MISSING_TARGET
  mIsEnabled.............: true
  mIsMutable.............: true
  mPriority..............: 10
  mCategory..............: BypassIdMapV1
}
com.android.car.rotaryplayground.googlecarui.rro:10 {
  mPackageName...........: com.android.car.rotaryplayground.googlecarui.rro
  mUserId................: 10
  mTargetPackageName.....: com.android.car.rotaryplayground
  mTargetOverlayableName.: car-ui-lib
  mBaseCodePath..........: /product/overlay/googlecarui-com-android-car-rotaryplayground/googlecarui-com-android-car-rotaryplayground.apk
  mState.................: STATE_MISSING_TARGET
  mIsEnabled.............: true
  mIsMutable.............: true
  mPriority..............: 10
  mCategory..............: BypassIdMapV1
}
```

--------------------------------

### Navigate to boot classpath JAR files

Source: https://source.android.com/docs/core/runtime/boot-image-profiles

Builds the distribution and lists the boot.zip file in the product output directory.

```shell
m dist
ls $ANDROID_PRODUCT_OUT/boot.zip
```

--------------------------------

### FMQ MessageQueue Creation Examples

Source: https://source.android.com/docs/core/architecture/hidl/fmq

Code examples for creating MessageQueue objects in FMQ setup.

```cpp
#include <fmq/MessageQueue.h>
using android::hardware::kSynchronizedReadWrite;
using android::hardware::kUnsynchronizedWrite;
using android::hardware::MQDescriptorSync;
using android::hardware::MQDescriptorUnsync;
using android::hardware::MessageQueue;
....
// For a synchronized nonblocking FMQ
mFmqSynchronized =
  new (std::nothrow) MessageQueue<uint16_t, kSynchronizedReadWrite>
      (kNumElementsInQueue);
// For an unsynchronized FMQ that supports blocking
mFmqUnsynchronizedBlocking =
  new (std::nothrow) MessageQueue<uint16_t, kUnsynchronizedWrite>
```

```cpp
MessageQueue<T, flavor>::MessageQueue(const MQDescriptor<T, flavor>& Desc, bool resetPointers)
```

--------------------------------

### Set up repack_bootimg environment

Source: https://source.android.com/docs/core/tests/vts/vts-on-gsi?hl=it

Unzip otatools.zip and add its bin directory to PATH, then verify repack_bootimg is available with --help.

```bash
unzip otatools.zip -d otatools
export PATH="${PWD}/otatools/bin:${PATH}"
repack_bootimg --help

```

--------------------------------

### Install repo and bazel-bootstrap

Source: https://source.android.com/docs/core/architecture/bootloader/generic-bootloader/gbl-dev

Install the required tools for building GBL. Run this command before initializing the source tree.

```bash
sudo apt install repo bazel-bootstrap

```

--------------------------------

### Start remote tool and run end-to-end tests

Source: https://source.android.com/docs/core/graphics/winscope/run

Before running end-to-end tests, start the remote tool and install the Chrome driver. The `run test:e2e` command automatically installs the Chrome driver.

```bash
$ npm run start
$ npm run start:remote_tool_mock
$ npm run test:e2e

```

--------------------------------

### Example output from tradefed.sh run instrumentations

Source: https://source.android.com/docs/core/tests/tradefed/testing/through-tf/instrumentation

Example output showing tests starting and the run ending. The output includes lines like 'Starting test: android.animation.cts.ValueAnimatorTest#testOfArgb' and 'Run ended in 2m 20s'.

```text
07-17 10:55:32 D/InvocationToJUnitResultForwarder: Starting test: android.animation.cts.ValueAnimatorTest#testOfArgb
07-17 10:55:33 D/InvocationToJUnitResultForwarder: Starting test: android.animation.cts.ValueAnimatorTest#testIsRunning
07-17 10:55:34 D/InvocationToJUnitResultForwarder: Starting test: android.animation.cts.ValueAnimatorTest#testGetCurrentPlayTime
07-17 10:55:35 D/InvocationToJUnitResultForwarder: Starting test: android.animation.cts.ValueAnimatorTest#testStartDelay
07-17 10:55:35 I/InvocationToJUnitResultForwarder: Run ended in 2m 20s

```

--------------------------------

### Run helloworld with FileLogger and observe saved log paths

Source: https://source.android.com/docs/core/tests/tradefed/fundamentals/full_example

Command to run the helloworld example after adding FileLogger, and the output showing the paths of saved device and host logs.

```text
tf >run example/helloworld
…
05-16 21:38:21 I/XmlResultReporter: Saved device_logcat log to /tmp/0/inv_6390011618174565918/device_logcat_1302097394309452308.txt
05-16 21:38:21 I/XmlResultReporter: Saved host_log log to /tmp/0/inv_6390011618174565918/host_log_4255420317120216614.txt
…

```

--------------------------------

### Install Python 3.10 and distutils

Source: https://source.android.com/docs/core/tests/development/android-test-station/ats-user-guide

Installs a specific Python version (example: 3.10) and its distutils package.

```bash
sudo apt-get update
sudo apt install python3.10 python3.10-distutils

```

--------------------------------

### AB_OTA_POSTINSTALL_CONFIG für system-Partition konfigurieren

Source: https://source.android.com/docs/core/ota/ab/ab_implement?hl=de

Konfiguriert den Post-Install-Schritt für die Systempartition. Gibt den Pfad zum Post-Install-Programm relativ zum Dateisystemstamm an (z.B. usr/bin/postinst) und den Dateisystemtyp für mount(2). Fügen Sie dies den Produkt- oder Geräte-.mk-Dateien hinzu.

```makefile
AB_OTA_POSTINSTALL_CONFIG += \
  RUN_POSTINSTALL_system=true \
  POSTINSTALL_PATH_system=usr/bin/postinst \
  FILESYSTEM_TYPE_system=ext4

```

--------------------------------

### Run example/helloworld with default reporter

Source: https://source.android.com/docs/core/tests/tradefed/fundamentals/full_example

Executes the HelloWorldTest config and shows the default TextResultReporter output to stdout.

```text
tf> run example/helloworld
04-29 18:25:55 I/TestInvocation: Invocation was started with cmd: /tmp/helloworld.xml
04-29 18:25:55 I/TestInvocation: Starting invocation for 'stub' with '[ BuildInfo{bid=0, target=stub, serial=876X00GNG} on device '876X00GNG']
04-29 18:25:55 I/HelloWorldTest: Hello, TF World! I have device 876X00GNG
04-29 18:25:55 I/InvocationToJUnitResultForwarder: Running helloworldrun: 1 tests
04-29 18:25:55 W/InvocationToJUnitResultForwarder:
Test com.example.TestClassName#sampleTest failed with stack:
 oh noes, test failed
04-29 18:25:55 I/InvocationToJUnitResultForwarder: Run ended in 0 ms

```

--------------------------------

### Init script to install kernel module with insmod

Source: https://source.android.com/docs/core/ota/vendor-apex

Example init script in the vendor partition that installs a kernel module from a vendor APEX using insmod. Kernel modules must be installed explicitly.

```rc
on early-boot
  insmod /apex/myapex/etc/modules/my.ko
  ..

```

--------------------------------

### Initialize repo with uefi-gbl-mainline manifest

Source: https://source.android.com/docs/core/architecture/bootloader/generic-bootloader/gbl-dev

Initialize the current directory for source control using the uefi-gbl-mainline manifest and sync the repository.

```bash
repo init -u https://android.googlesource.com/kernel/manifest -b uefi-gbl-mainline
repo sync -j16

```

--------------------------------

### Install extra test APKs with test-file-name options

Source: https://source.android.com/docs/core/tests/development/instrumentation

Example lines from frameworks/base/core/tests/coretests/ that install extra apps. Include these in your Android.mk or test configuration when your test requires additional APKs.

```xml
<option name="test-file-name" value="FrameworksCoreTests.apk" />
<option name="test-file-name" value="BstatsTestApp.apk" />

```
Tokens:
Raw