Configuration options for Bluetooth audio streaming (bt-a2dp).

no description

The method to play audio when sink is enabled.

The source for audio when A2DP source is enabled.

The audio stack to use in the platform.

Configuration options for the Bluetooth HFP Audio Gateway component (‘bt-hfp-audio-gateway’).

The internal layout of blobfs.

Platform configuration options for Bluetooth. The default platform configuration does not include any Bluetooth packages.

These control security and behavioral settings within the platform, and can change the platform packages placed into the assembled product image.

Platform configuration options for the component id index which describes consistent storage IDs to use for component monikers. If the monikers change, the IDs can stay consistent, ensuring that the storage does not need to be migrated to a new location.

The data format to use inside the fvm.

The platform's base service level.

This is the basis for the contract with the product as to what the minimal set of services that are available in the platform will be. Features can be enabled on top of this most-basic level, but some features will require a higher basic level of support.

These were initially based on the product definitions that are used to provide the basis for all other products:

bringup.gni (Bootstrap) +--> minimal.gni (Minimal) +--> core.gni +--> (everything else)

The Utility level is between Bootstrap and Minimal, adding the /core realm and those children of /core needed by all systems that include /core.

The standard (default) level is Minimal. It is the level that should be used by products' main system.

no description

Whether the filesystem should be placed in a separate partition, in a ramdisk, or nonexistent.

Configuration options for the Bluetooth HFP Hands Free component (‘bt-hfp-hands-free’).

verify_components are capable of blocking an update if they do not report a healthy status.

no description

Available versions of Memory Monitor

Sets the memory reclamation strategy of the device's kernel.

Amount of memory.

Whether the network manager feature should be included in the Starnix container.

Which networking type to use (standard or basic).

What should happen if the device runs out-of-memory.

Options for user page tables the reclamation policy.

Used to turn on updating the UTC value recorded in the RTC with the most current UTC estimate on a periodic basis.

A periodic update is strictly in addition to the “as needed” basis, which is always done. Periodic update might be useful on systems where there is a weaker guarantee that RTC remains recording usable value.

Normally we rely on RTC making independent progress and tracking UTC as we record values to it. However, sometimes we want to make sure that any RTC drift with respect to our most current UTC estimate is neutralized, at which point we may want to order periodic updates. These updates come with a cost of more timekeeper activity, and hence more aggressive power usage. As a result, the resolution of this value is 1 minute, and it is recommended that the value is set to 10 minutes or more if a custom setting is needed.

no description

This config exists in both board and platform configs, to allow board config to override static defaults, and to allow platform config to override board config.

This is a high-level operation that takes a more abstract description of what is desired in the assembled product images, and then generates the complete Image Assembly configuration (ImageProductConfig) from that.

This also includes configuration for those packages:

json5 packages: { base: { package_a: { manifest: “path/to/package_a/package_manifest.json”, }, package_b: { manifest: “path/to/package_b/package_manifest.json”, config_data: { “foo.cfg”: “path/to/some/source/file/foo.cfg”, “bar/more/data.json”: “path/to/some.json”, }, }, ], cache: [] }

json5 session: { url: “fuchsia-pkg://fuchsia.com/my_session#meta/my_session.cm”, initial_element: { collection: “elements”, url: “fuchsia-pkg://fuchsia.com/my_component#meta/my_component.cm” view_id_annotation: “my_component” } }

no description

no description

The policy for how to handle RTC readings that are in the past with respect to the current boot clock.

Severities a log message can have, often called the log's “level”.

Specifies the configuration for the Bluetooth Snoop component (bt-snoop).

How starnix treats socket marks.

no description

no description

If set, this field specifies the name of the volume which the main Starnix component will store its mutable data in. If unset, Starnix will rely on a storage capability instead.

Which system recovery implementation to include in the image

Configuration strategy for TEE.

no description

The type if intl configuration to be used.

The UpdateChecker enum represents the particular implementation of the update-checker tool on the target that the update package depends on

no description

VisualDebuggingLevel used to enable visualized debug features. It has 3 level for now:

How to configure the filesystem volume. Some systems may configure this without actually generating filesystem images in order to configure fshost without needing an actual filesystem.

no description

no description

Options for zero page scanner configuration.