Tunip3

Capability Kerfuffles

Category Capability Description
Capability allJoyn Enables AllJoyn-enabled apps and devices on a network to discover and interact with each other.
Capability backgroundMediaPlayback Changes the behavior of the media-specific APIs like the MediaPlayer and AudioGraph classes to enable media playback while your app is in the background. All active audio streams will no longer mute, but will continue to be audible when an app transitions to the background. Additionally, app lifetime will be extended automatically while playback is occurring.
Capability codeGeneration Enables apps to access the following functions which provide JIT capabilities to apps.
Capability internetClient Indicates that apps can receive incoming data from the Internet. Cannot act as a server. No local network access.
Capability internetClientServer Indicates that apps can receive incoming data from the Internet. Can act as a server. No local network access. You don’t need to specify internetClient when you specify internetClientServer.
Capability privateNetworkClientServer Provides inbound and outbound access to home and work networks through the firewall. This capability is typically used for games that communicate across the local area network (LAN), and for apps that share data across a variety of local devices. If your app specifies musicLibrary, picturesLibrary, or videosLibrary, you don’t need to use this capability to access the corresponding library in a Home Group. On Windows, this capability does not provide access to the Internet.
Capability remoteSystem Enables apps to have access to a list of devices associated with the user’s Microsoft Account. Access to the device list is necessary to perform any operations that persist across devices. This capability is required to access to all members of the following. Windows.System.RemoteSystems namespace Windows.System.RemoteLauncher class AppServiceConnection.OpenRemoteAsync method
Capability spatialPerception Enables programmatic access to spatial mapping data, giving mixed reality apps information about surfaces in application-specified regions of space near the user. Declare the spatialPerception capability only when your app will explicitly use these surface meshes, as the capability is not required for mixed reality apps to perform holographic rendering based on the user’s head pose.
Capability userNotificationListener Unknown, source unknown
DeviceCapability - Unknown, dumped from bluray app so likely something to do with ode
DeviceCapability - Unknown, dumped from bluray app so likely something to do with ode
DeviceCapability - HDMI Access
DeviceCapability - Graphics KMD Access
DeviceCapability activity Enables apps to detect the current motion of the device. This capability is required to use some APIs in the Windows.Devices.Sensors namespace
DeviceCapability bluetooth Enables apps to communicate with already paired bluetooth devices over both Generic Attribute (GATT) or Classic Basic Rate (RFCOMM) protocol. This capability is required to use some APIs in the Windows.Devices.Bluetooth namespace.
DeviceCapability gazeInput Enables apps to detect where the user is looking within the application bounds when a compatible eye tracking device is connected or for Mixed Reality devices that support gaze tracking. This capability is required to use some APIs in the Windows.Devices.Input.Preview namespace. For Mixed Reality devices, this capability is required for APIs in the Windows.Perception.People.EyesPose.
DeviceCapability humaninterfacedevice Enables access to APIs in the How to specify device capabilities for HID.
DeviceCapability location Enables access to location functionality that is retrieved from dedicated hardware like a GPS sensor in the PC or is derived from available network info. Apps must handle the case in which the user has disabled location services from the Settings charm.
DeviceCapability lowLevel Enables access to GPIO, I2C, SPI, and PWM devices. This capability is required to use the APIs in the following namespaces: Windows.Devices.Gpio, Windows.Devices.I2c, Windows.Devices.Spi,Windows.Devices.Pwm.
DeviceCapability microphone Enables access to the microphone’s audio feed, which allows the app to record audio from connected microphones. Apps must handle the case in which the user has disabled the microphone from the Settings charm.
DeviceCapability optical Enables apps to access functions on optical disk drives such as CD, DVD, and Blu-ray. This capability is required to use some APIs in the Windows.Devices.Custom namespace.
DeviceCapability pointOfService Enables access to APIs in the Windows.Devices.PointOfService namespace. This namespace lets your app access Point of Service (POS) barcode scanners and magnetic stripe readers. The namespace provides a vendor-neutral interface for accessing POS devices from various manufacturers from a UWP app.
DeviceCapability proximity Enables multiple devices in close proximity to communicate with one another. This capability is typically used in casual multi-player games and in apps that exchange information. Devices attempt to use the communication technology that provides the best possible connection, including Bluetooth, Wi-Fi, and the Internet. This capability is used only to initiate communication between the devices.
DeviceCapability radios Enables apps to toggle the Wi-Fi and Bluetooth radios. This capability is required to use the APIs in the Windows.Devices.Radios namespace.
DeviceCapability serialcommunication Enables access to APIs in the Windows.Devices.SerialCommunication namespace, which allows a Windows app to communicate with a device that exposes a serial port or some abstraction of a serial port. This capability is required to use the APIs in the Windows.Devices.SerialCommnication namespace.
DeviceCapability usb Enables access to APIs in the Updating the app manifest package for a USB device.
DeviceCapability webcam Enables access to the video feed of a built-in camera or external webcam, which allows the app to capture photos and videos. On Windows, apps must handle the case in which the user has disabled the camera from the Settings charm. The webcam capability only grants access to the video stream. In order to grant access to the audio stream as well, the microphone capability must be added.
DeviceCapability wiFiControl Enables apps to scan and connect to Wi-Fi networks. This capability is required to use some APIs in the Windows.Devices.WiFi namespace.
iot:Capability lowLevelDevices Enables apps to access custom devices when a number of additional requirements are met. This capability should not be confused with the lowLevel device capability, which allows access to GPIO, I2C, SPI, and PWM devices. If you develop a custom driver that exposes a device interface and you wish to open a handle to this device and send IOCTLs, you must: Enable the lowLevelDevices capability in your application manifest: <Capabilities><iot:Capability Name="lowLevelDevices"/></Capabilities>, Enable embedded mode, Mark the device interface as restricted, either in your INF or by calling WdfDeviceAssignInterfaceProperty() in your driver. You can then use Windows.Devices.Custom.CustomDevice to open a handle to your device.
iot:Capability systemManagement Enables apps to have basic system administration privileges such as shutting down or rebooting, locale, and timezone. This capability is required to access some of the APIs in the Windows.System namespace.
mobile:Capability recordedCallsFolder Enables apps to access the recorded calls folder.
uap:Capability appointments Enables read access to appointments obtained from the synced network accounts and to other apps that write to the appointment store. It also enables your app to create new calendars and write appointments to calendars that it creates.
uap:Capability blockedChatMessages Enables apps to read SMS and MMS messages that have been blocked by the Spam Filter app. This capability is required to access the blocked messages using APIs in the Windows.ApplicationModel.Chat namespace.
uap:Capability contacts Enables access to the aggregated view of the contacts from various contacts stores. This capability gives the app limited access (network permitting rules apply) to contacts that were synced from various networks and the local contact store.
uap:Capability documentsLibrary Enables programmatic access to the user’s Documents library, filtered to the file type associations declared in the package manifest. For example, if a word processing app declared a .doc file type association, it can open .doc files in the user’s Documents library.
uap:Capability enterpriseAuthentication Windows domain credentials enable a user to log into remote resources using their credentials, and act as if a user provided their user name and password. The enterpriseAuthentication capability is typically used in line-of-business apps that connect to servers within an enterprise.
uap:Capability musicLibrary Enables programmatic access to the user’s Music library, allowing the app to enumerate and access all files in the library without user interaction. This capability is typically used in jukebox apps that make use of the entire Music library.
uap:Capability objects3D Enables apps to have programmatic access to the 3D object files. This capability is typically used in 3D apps and games that need access to the entire 3D objects library. This capability is required to access the folder that contains the 3D objects using APIs in the Windows.Storage namespace.
uap:Capability phoneCall Enables apps to access all of the phone lines on the device and perform the following functions: place a call on the phone line and show the system dialer without prompting the user, access line-related metadata, access line-related triggers, allows the user-selected spam filter app to set and check block list and call origin information.
uap:Capability phoneCallHistoryPublic Enables apps to read cellular and some VoIP call history information on the device. This capability also allows the app to write VoIP call history entries. This capability is required to access all members of the PhoneCallHistoryStore class.
uap:Capability picturesLibrary Enables programmatic access to the user’s Pictures library, allowing the app to enumerate and access all files in the library without user interaction. This capability is typically used in photo apps that make use of the entire Pictures library.
uap:Capability removableStorage Enables programmatic access to files on removable storage, like USB keys and external hard drives, filtered to the file-type associations declared in the package manifest. For example, if a document-reader app declares a .doc file-type association, it can open .doc files on the removable storage device, but not other types of files. Be careful when you declare this capability, because users may include a variety of info in their removable storage devices, and will expect your app to provide a valid justification for programmatic access to the removable storage for all files of the declared type.
uap:Capability sharedUserCertificates Enables an app to add and access software and hardware-based certificates in the Shared User store, such as certificates stored on a smart card. This capability is typically used for financial or enterprise apps that require a smart card for authentication.
uap:Capability userAccountInformation Enables apps to access the user’s name and picture. This capability is required to access some APIs in the Windows.System.UserProfile namespace.
uap:Capability videosLibrary Enables programmatic access to the user’s Videos, allowing the app to enumerate and access all files in the library without user interaction. This capability is typically used in movie-playback apps that make use of the entire Videos library.
uap:Capability voipCall Enables apps to access the VoIP calling APIs in the Windows.ApplicationModel.Calls namespace.
uap6:Capability graphicsCapture  
uap7:Capability globalMediaControl Enables apps to access to playback sessions throughout the system that have integrated with SystemMediaTransportControls to provide playback info and allow remote control. This capability is required to use some APIs in the Windows.Media.Control namespace. This capability is defined in the uap7:Capability element.