YourPhone.Connectivity.Bluetooth.Managed

Returns whether the device is rejecting connections. One possible cause is that the device's Bluetooth is in a partially disabled state (i.e., where Bluetooth is enabled, but the phone actively rejects incoming connections). Currently only checking for 2 or more services running into this error since its possible for other profiles to timeout.

Initializes a new instance of the class. This class watches for changes to the BluetoothDevice name and updates the DeviceData object as appropriate. We use BT Classic for this since a Bluetooth LE connection does not appear to fire the NameChanged event.

When a device is removed from Windows Bluetooth Settings, we need to react. We already do this on (cold) app start, but doing so proactively eliminates a point of friction where the user may get stuck in a pairing loop (caused by Windows Swift pair) when PL next attempts a connection in this state.

Devices may have been unpaired from Bluetooth while the app was not running.

Compares an incoming device's bluetooth device id with the calling ID stored in IDeviceData. This id is stored by the HfpDeviceManager after it registers a device for calling.

Compares an incoming device's bluetooth device id with the Bluetooth Classic ID stored in IDeviceData.

Compares bluetooth addresses of an incoming device with the calling address stored in IDeviceData. This address is stored only when going through the universal pairing flow (currently only applicable to Android devices) and is retained here for backcompat

This is a reverse mapping of the method above

Boolean indicating whether the filter can be represented as a BluetoothLEAdvertisementFilter.

For telemetry log purposes only

This is a best effort method which tries to notify the remote device that pairing has succeeded.

Android 12 (API level 31) gates the Bluetooth name behind a runtime permission. Without this permission, LTW sends us a fallback display name which can be different from the Bluetooth name for certain devices. Since this name is used to select a device for BT pairing, once the user grants us required permissions on LTW, we need to refresh this value.

Stops the unpaired device watcher, and waits for the Stopped event. This is a documented requirement before calling DeviceWatcher.Start()

InitializeComponent()

Connect()

GetBindingConnector(int connectionId, object target)

InitializeComponent()

Connect()

GetBindingConnector(int connectionId, object target)

The deferral must be completed on a background thread. Not calling Deferral.Complete() or calling it from the main thread results in bad behavior (the DeviceInformationCustomPairing.PairAsync call that initiated this pairing operation will hang, and the PC-phone combination stays in a bad state until the PC restarts

InitializeComponent()

Connect()

GetBindingConnector(int connectionId, object target)

InitializeComponent()

Connect()

GetBindingConnector(int connectionId, object target)

InitializeComponent()

Connect()

GetBindingConnector(int connectionId, object target)

InitializeComponent()

Connect()

GetBindingConnector(int connectionId, object target)

ClearSessionAsync() currently potentially does too much. Specifically, writing to the CCCD is theoretically unnecessary and in cases where we do this when the GATT session is not active, is much more likely to fail, exacerbating the well-known "limited resources" bug

This API supports the logging infrastructure and is not intended to be used directly from your code. It is subject to change in the future.

This function writes None to the ClientCharacteristicConfigurationDescriptor and then removes the ValueChanged listener.

Result of the Write operation on the ClientCharacteristicConfigurationDescriptor

This function only removes the ValueChanged listener on the underlying Characteristic, without writing to the ClientCharacteristicConfigurationDescriptor. Use this when you need to dispose of a handler object without changing the underlying CCCD.

Either permission is denied or it's possible the phone is locked

This must be kept in sync with LtwScenario.swift and YourPhone.OnboardingSDK.Bluetooth.Pairing.Utilities.LtwScenario.cs

This class manages interactions with our custom LE GATT service used for pairing the PC and Phone during onboarding flows. Currently, this is used to support iOS devices only.

Read the ProtocolVersion from the pairing service. Default behavior is to use a locally cached value, if available.

Force a request to the device to load the current protocol version. String representing the protocol version, e.g. "1.0"

Read the PairingId from the pairing service. Default behavior is to query the device to ensure the latest ID is retrieved.

Return the last-read value (or null) of the PairingId. Byte array containing the pairing ID, or null if an error.

Constants related to the LE Pairing Service. These UUIDs/Constants must match those at: /ios/apps/LTW/LTW/Bluetooth/BluetoothPairingService.swift

This allows us to differentiate between the case where the Rfcomm service was simply unavailable (e.g., no server listening) and the case where the PC failed to even talk to the remote device

If the user enables and then disables this toggle, all subsequent PBAP operations continue reporting Success but with an empty body. Thus, the interpretation of this property is left up to the caller

Pbap sync uses its own fine-grained policies

Create a policy that allows only requests to execute at a time, with at most other requests queued. If reqeusts succeed with a non-empty result, then a delay/cooldown period equaling is introduced

A Polly policy

Create a policy that allows only requests to execute at a time, with at most other requests queued. If requests succeed with a non-empty result then a delay/cooldown period equaling is introduced

A Polly policy

Basic retry policy

A Polly policy

Basic retry policy with no rate limits

A Polly policy

Basic retry policy since scenario is responsible for rate limiting

A Polly policy

A bare minimum retry policy. This is due to the large number of thumbnail requests that can be dispatched simultaneously

A Polly policy

Defines the source generated JSON serialization contract metadata for a given type.

Defines the source generated JSON serialization contract metadata for a given type.

Defines the source generated JSON serialization contract metadata for a given type.

Defines the source generated JSON serialization contract metadata for a given type.

The default associated with a default instance.

The source-generated options associated with this context.

The P90 for each run through bluetooth pairing + hfp work is 130 seconds as of 3/7/2024. Doubling this leaves sufficient room for retries.

Trace event logger

Whether we should skip writing to the CCCD if it already had the Notify flag when we read it from the server.

Defines the source generated JSON serialization contract metadata for a given type.

Defines the source generated JSON serialization contract metadata for a given type.

Defines the source generated JSON serialization contract metadata for a given type.

Defines the source generated JSON serialization contract metadata for a given type.

The default associated with a default instance.

The source-generated options associated with this context.

This indicates that we successfully wrote to the CCCD at some point without a teardown of some sort during the current app session. This still means that we overwrote the CCCD, despite the Notify flag already being present on the server.

This indicates that the server already had the Notify flag present on this CCCD (from our previous successful attempt in the past), and therefore did not write(or overwrite) it on the server. This is how CCDs are supposed to work. Barring unexpected bad behavior, this is expected to replace . CCCD values set by a client on a server when the devices are bonded are guaranteed to be persistent across sessions(Vol 3 Part G Section 3.3.3.3)

Generates an LTW pairing URI.

Pass PairingSourceType.Dcg to get a URI that is not necessarily Bluetooth specific 16 byte pairing id. This corresponds to IDeviceData.Id Id used for telemetry The DCG client id of the phone. Used for BT recovery scenarios Name of the logged in MSA

Generates an LTW pairing URI (legacy)

8 byte pairing id Id used for telemetry

Main class for providing metadata for the app or library

GetXamlType(Type)

GetXamlType(String)

GetXmlnsDefinitions()

Defines options that can be applied when adding a package dependency.

No options are applied.

If multiple packages are present in the package graph with the same rank as the call to **AddPackageDependency**, the resolved package is added before others of the same rank. For more information, see [AddPackageDependency](nf-appmodel-addpackagedependency.md).

Defines options that can be applied when creating a package dependency by using the TryCreatePackageDependency function.

No options are applied.

Disables dependency resolution when pinning a package dependency. This is useful for installers running as user contexts other than the target user (for example, installers running as LocalSystem).

Defines the package dependency for the system, accessible to all users (by default, the package dependency is defined for a specific user). This option requires the caller has administrative privileges.

Specifies values that indicate the type of artifact that is used to define the lifetime of a package dependency.

The current process is the lifetime artifact. The package dependency is implicitly deleted when the process terminates.

The lifetime artifact is an absolute filename or path. The package dependency is implicitly deleted when this is deleted.

The lifetime artifact is a registry key in the format *root*\\*subkey*, where *root* is one of the following: HKEY_LOCAL_MACHINE, HKEY_CURRENT_USER, HKEY_CLASSES_ROOT, or HKEY_USERS. The package dependency is implicitly deleted when this is deleted.

Defines the processor architectures for a framework package dependency that you create by using the TryCreatePackageDependency function.

No processor architecture is specified.

Specifies the neutral architecture.

Specifies the x86 architecture.

Specifies the x64 architecture.

Specifies the ARM architecture.

Specifies the ARM64 architecture.

Specifies the x86/A64 architecture.

Represents the package version information.

Learn more about this API from docs.microsoft.com.

Represents a Win32 handle that can be closed with .

The BLUETOOTH_FIND_RADIO_PARAMS structure facilitates enumerating installed Bluetooth radios.

Learn more about this API from docs.microsoft.com.

Size of the BLUETOOTH_FIND_RADIO_PARAMS structure, in bytes.

Contains information about a Bluetooth radio.

Learn more about this API from docs.microsoft.com.

Size, in bytes, of the structure.

Address of the local Bluetooth radio.

Name of the local Bluetooth radio.

Device class for the local Bluetooth radio.

This member contains data specific to individual Bluetooth device manufacturers.

Manufacturer of the Bluetooth radio, expressed as a BTH_MFG_Xxx value. For more information about the Bluetooth assigned numbers document and a current list of values, see the Bluetooth specification at www.bluetooth.com.

The **HRESULT** data type is the same as the [SCODE](scode.md) data type. An **HRESULT** value consists of the following fields: - A 1-bit code indicating severity, where zero represents success and 1 represents failure. - A 4-bit reserved value. - An 11-bit code indicating responsibility for the error or warning, also known as a facility code. - A 16-bit code describing the error or warning. Most MAPI interface methods and functions return **HRESULT** values to provide detailed cause formation. **HRESULT** values are also used widely in OLE interface methods. OLE provides several macros for converting between **HRESULT** values and **SCODE** values, another common data type for error handling. > [!NOTE] > In 64-bit MAPI, **HRESULT** is still a 32-bit value. For information about the OLE use of **HRESULT** values, see the *OLE Programmer's Reference*. For more information about the use of these values in MAPI, see [Error Handling](error-handling-in-mapi.md) and any of the following interface methods: [IABLogon::GetLastError](iablogon-getlasterror.md) [IMAPISupport::GetLastError](imapisupport-getlasterror.md) [IMAPIControl::GetLastError](imapicontrol-getlasterror.md) [IMAPITable::GetLastError](imapitable-getlasterror.md) [IMAPIProp::GetLastError](imapiprop-getlasterror.md) [IMAPIViewAdviseSink::OnPrint](imapiviewadvisesink-onprint.md) Read more on docs.microsoft.com. A pointer to the IErrorInfo interface that provides more information about the error. You can specify to use the current IErrorInfo interface, or new IntPtr(-1) to ignore the current IErrorInfo interface and construct the exception just from the error code. , if it does not reflect an error.

A pointer to a null-terminated, constant character string.

A pointer to the first character in the string. The content should be considered readonly, as it was typed as constant in the SDK.

Gets the number of characters up to the first null character (exclusive).

Returns a with a copy of this character array, up to the first null character (exclusive).

A , or if is .

Returns a span of the characters in this string, up to the first null character (exclusive).

Returns a span of the characters in this string, up to the first null character (exclusive).

The length of the inline array.

Gets a ref to an individual element of the inline array. ⚠ Important ⚠: When this struct is on the stack, do not let the returned reference outlive the stack frame that defines it.

Gets this inline array as a span.

⚠ Important ⚠: When this struct is on the stack, do not let the returned span outlive the stack frame that defines it.

Gets this inline array as a span.

⚠ Important ⚠: When this struct is on the stack, do not let the returned span outlive the stack frame that defines it.

The length of the inline array.

Gets a ref to an individual element of the inline array. ⚠ Important ⚠: When this struct is on the stack, do not let the returned reference outlive the stack frame that defines it.

Gets this inline array as a span.

⚠ Important ⚠: When this struct is on the stack, do not let the returned span outlive the stack frame that defines it.

Gets this inline array as a span.

⚠ Important ⚠: When this struct is on the stack, do not let the returned span outlive the stack frame that defines it.

Copies the fixed array to a new string up to the specified length regardless of whether there are null terminating characters.

Thrown when is less than 0 or greater than .

Copies the fixed array to a new string, stopping before the first null terminator character or at the end of the fixed array (whichever is shorter).

Contains extern methods from "ADVAPI32.dll". Contains extern methods from "BluetoothApis.dll". Contains extern methods from "KERNEL32.dll". Contains extern methods from "KERNELBASE.dll".

Frees a security identifier (SID) previously allocated by using the AllocateAndInitializeSid function.

A pointer to the SID structure to free. Read more on docs.microsoft.com. If the function succeeds, the function returns NULL. If the function fails, it returns a pointer to the SID structure represented by the pSid parameter. Learn more about this API from docs.microsoft.com.

The BluetoothFindRadioClose function closes the enumeration handle associated with finding Bluetooth radios.

Enumeration handle to close, obtained with a previous call to the BluetoothFindFirstRadio function. Returns TRUE when the handle is successfully closed. Returns FALSE if the attempt fails to close the enumeration handle. For additional information on possible errors associated with closing the handle, call the GetLastError function. Learn more about this API from docs.microsoft.com.

The BluetoothFindFirstRadio function begins the enumeration of local Bluetooth radios.

Pointer to a BLUETOOTH_FIND_RADIO_PARAMS structure. The dwSize member of the BLUETOOTH_FIND_RADIO_PARAMS structure pointed to by pbtfrp must match the size of the structure. Pointer to where the first enumerated radio handle will be returned. When no longer needed, this handle must be closed via CloseHandle. In addition to the handle indicated by phRadio, calling this function will also create a HBLUETOOTH_RADIO_FIND handle for use with the BluetoothFindNextRadio function. When this handle is no longer needed, it must be closed via the BluetoothFindRadioClose. Returns NULL upon failure. Call the GetLastError function for more information on the error. The following table describe common errors: This doc was truncated. Learn more about this API from docs.microsoft.com.

Obtains information about a Bluetooth radio.

A handle to a local Bluetooth radio, obtained by calling the BluetoothFindFirstRadio or similar functions, or the SetupDiEnumerateDeviceInterfances function. A pointer to a BLUETOOTH_RADIO_INFO structure into which information about the radio will be placed. The dwSize member of the BLUETOOTH_RADIO_INFO structure must match the size of the structure. The following table lists common return values. This doc was truncated. Learn more about this API from docs.microsoft.com.

Closes an open object handle.

A valid handle to an open object. If the function succeeds, the return value is nonzero. If the function fails, the return value is zero. To get extended error information, call GetLastError. If the application is running under a debugger, the function will throw an exception if it receives either a handle value that is not valid or a pseudo-handle value. This can happen if you close a handle twice, or if you call CloseHandle on a handle returned by the FindFirstFile function instead of calling the FindClose function. The CloseHandle function closes handles to the following objects: This doc was truncated. Read more on docs.microsoft.com.

Retrieves a handle to the default heap of the calling process.

If the function succeeds, the return value is a handle to the calling process's heap. If the function fails, the return value is NULL. To get extended error information, call GetLastError. The GetProcessHeap function obtains a handle to the default heap for the calling process. A process can use this handle to allocate memory from the process heap without having to first create a private heap using the HeapCreate function. Windows Server 2003 and Windows XP:  To enable the low-fragmentation heap for the default heap of the process, call the HeapSetInformation function with the handle returned by GetProcessHeap. Read more on docs.microsoft.com.

Frees a memory block allocated from a heap by the HeapAlloc or HeapReAlloc function.

A handle to the heap whose memory block is to be freed. This handle is returned by either the HeapCreate or GetProcessHeap function. Read more on docs.microsoft.com. The heap free options. Specifying the following value overrides the corresponding value specified in the flOptions parameter when the heap was created by using the HeapCreate function. This doc was truncated. Read more on docs.microsoft.com. A pointer to the memory block to be freed. This pointer is returned by the HeapAlloc or HeapReAlloc function. This pointer can be NULL. Read more on docs.microsoft.com. If the function succeeds, the return value is nonzero. If the function fails, the return value is zero. An application can call GetLastError for extended error information. You should not refer in any way to memory that has been freed by HeapFree. After that memory is freed, any information that may have been in it is gone forever. If you require information, do not free memory containing the information. Function calls that return information about memory (such as HeapSize) may not be used with freed memory, as they may return bogus data. Calling HeapFree twice with the same pointer can cause heap corruption, resulting in subsequent calls to HeapAlloc returning the same pointer twice. Serialization ensures mutual exclusion when two or more threads attempt to simultaneously allocate or free blocks from the same heap. There is a small performance cost to serialization, but it must be used whenever multiple threads allocate and free memory from the same heap. Setting the HEAP_NO_SERIALIZE value eliminates mutual exclusion on the heap. Without serialization, two or more threads that use the same heap handle might attempt to allocate or free memory simultaneously, likely causing corruption in the heap. The HEAP_NO_SERIALIZE value can, therefore, be safely used only in the following situations: This doc was truncated. Read more on docs.microsoft.com.

Creates an install-time reference for a framework package dependency for the current app, using the specified package family name, minimum version, and additional criteria.

Type: PSID The user scope of the package dependency. If NULL, the caller's user context is used. Must be NULL if [CreatePackageDependencyOptions_ScopeIsSystem](ne-appmodel-createpackagedependencyoptions.md) is specified. Read more on docs.microsoft.com. Type: PCWSTR The package family name of the framework package on which to take dependency. Read more on docs.microsoft.com. Type: PACKAGE_VERSION The minimum version of the framework package on which to take dependency. Read more on docs.microsoft.com. Type: PackageDependencyProcessorArchitectures The processor architectures of the package dependency. Read more on docs.microsoft.com. Type: PackageDependencyLifetimeKind The type of artifact to use to define the lifetime of the package dependency. For more information, see the remarks. Read more on docs.microsoft.com. Type: PCWSTR The name of the artifact used to define the lifetime of the package dependency. Must be NULL if the *lifetimeKind* parameter is [PackageDependencyLifetimeKind_Process](ne-appmodel-packagedependencylifetimekind.md). For more information, see the remarks. Read more on docs.microsoft.com. Type: CreatePackageDependencyOptions The options to apply when creating the package dependency. Read more on docs.microsoft.com. Type: PWSTR* When this method returns, contains the address of a pointer to a null-terminated Unicode string that specifies the ID of the new package dependency. The caller is responsible for freeing this resource once it is no longer needed by calling [HeapFree](/windows/win32/api/heapapi/nf-heapapi-heapfree). Read more on docs.microsoft.com. Type: HRESULT If the function succeeds it returns ERROR_SUCCESS. Otherwise, the function returns an error code. The possible error codes include the following. | Return code | Description | |-------------|-------------| | E_INVALIDARG | The *packageDependencyId* parameter is NULL on input. | In your app's installer or during the first run of your app, call this method to specify a set of criteria for a framework package you want to use in your app. This informs the OS that your app has a dependency upon a framework package that meets the specified criteria. If one or more framework packages are installed that meet the criteria, Windows will ensure that at least one of these framework packages will remain installed until the install-time reference is deleted. For more information, see [Use the dynamic dependency API to reference MSIX packages at run time](/windows/apps/desktop/modernize/framework-packages/use-the-dynamic-dependency-api). This function fails if the specified dependency criteria cannot be resolved to a specific package. This package resolution check is skipped if [CreatePackageDependencyOptions_DoNotVerifyDependencyResolution](ne-appmodel-createpackagedependencyoptions.md) is specified for the *options* parameter. This is useful for installers running as user contexts other than the target user (for example, installers running as LocalSystem). Read more on docs.microsoft.com.

Resolves a previously defined PackageDependency to a specific package and adds it to the invoking process' package graph. After the dependency has been added, other code-loading methods (such as LoadLibrary and CoCreateInstance) can find the binaries in the resolved package.

Type: PCWSTR The ID of the package dependency to be resolved and added to the invoking process' package graph. This parameter must match a package dependency defined by using the [TryCreatePackageDependency](nf-appmodel-trycreatepackagedependency.md) function for the calling user or the system (via the [CreatePackageDependencyOptions_ScopeIsSystem](ne-appmodel-createpackagedependencyoptions.md) option), or else an error is returned. Read more on docs.microsoft.com. Type: INT32 The rank to use to add the resolved package to the caller's package graph. For more information, see the remarks. Read more on docs.microsoft.com. Type: AddPackageDependencyOptions The options to apply when adding the package dependency. Read more on docs.microsoft.com. Type: PACKAGEDEPENDENCY_CONTEXT* The handle of the added package dependency. This handle is valid until it is passed to RemovePackageDependency. Read more on docs.microsoft.com. Type: PCWSTR* When this method returns, contains the address of a pointer to a null-terminated Unicode string that specifies the full name of the package to which the dependency has been resolved. The caller is responsible for freeing this resource once it is no longer needed by calling [HeapFree](/windows/win32/api/heapapi/nf-heapapi-heapfree). Read more on docs.microsoft.com. Type: HRESULT If the function succeeds it returns ERROR_SUCCESS. Otherwise, the function returns an error code. The possible error codes include the following. | Return code | Description | |-------------|-------------| | E_INVALIDARG | The *packageDependencyId* or *packageDependencyContext* parameter is NULL on input. | Calling this method resolves the framework package dependency to a specific package on the system. It also informs the OS that the framework package is in active use and to handle any version updates in a side-by-side manner (effectively delay uninstalling or otherwise servicing the older version until after your app is done using it). Package resolution is specific to a user and can return different values for different users on a system. Each successful **AddPackageDependency** call adds the resolved package to the calling process' package graph, even if already present. There is no duplicate detection or filtering applied by the API (that is, multiple references from a package is not harmful). After resolution is complete, the package dependency stays resolved for that user until the last reference across all processes for that user is removed via [RemovePackageDependency](nf-appmodel-removepackagedependency.md) or the process is terminated. After this method successfully returns, your app can activate types and use content from the framework package until [RemovePackageDependency](nf-appmodel-removepackagedependency.md) is called. If multiple packages are present in the package graph with the same rank as the call to **AddPackageDependency**, the resolved package is (by default) added after others of the same rank. To add a package before others of the same rank, specify [AddPackageDependencyOptions_PrependIfRankCollision](ne-appmodel-addpackagedependencyoptions.md) for the *options* parameter. For more information, see [Use the dynamic dependency API to reference MSIX packages at run time](/windows/apps/desktop/modernize/framework-packages/use-the-dynamic-dependency-api). Read more on docs.microsoft.com.