Abstract: In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.

Abstract: In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.

Abstract: In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.

Abstract: In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.

Abstract: Provided herein are methods, devices, and systems of wireless communication. In one embodiment, a method for wireless communication between a first electronic device and a second electronic device includes: providing information symbols to the first electronic device, transmitting a pairing request from the first electronic device to the second electronic device, obtaining a pairing password by accessing a database, and establishing a wireless communication channel between the first electronic device and the second electronic device. In some embodiments, the information symbols are provided audibly or visually by the second electronic device and include a wireless communication address of the second electronic device. In some embodiments, the pairing password is obtained using the wireless communication address. In some embodiments, the wireless communication channel is obtained using the obtained pairing password.

Abstract: In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.

Abstract: In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.

Abstract: In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.

Abstract: Provided herein are methods, devices, and systems of wireless communication. In one embodiment, a method for wireless communication between a first electronic device and a second electronic device includes: providing information symbols to the first electronic device, transmitting a pairing request from the first electronic device to the second electronic device, obtaining a pairing password by accessing a database, and establishing a wireless communication channel between the first electronic device and the second electronic device. In some embodiments, the information symbols are provided audibly or visually by the second electronic device and include a wireless communication address of the second electronic device. In some embodiments, the pairing pass word is obtained using the wireless communication address. In some embodiments, the wireless communication channel is obtained using the obtained pairing password.

Abstract: In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.

Abstract: This document describes tools that enable a computing device to retrieve large data in smaller blocks. The tools also allow the computing device to receive and display data that does not include display formatting information through the use of templates.

Abstract: This document describes tools capable of updating media-location data for media-playing entities. These tools allow a developer of an application to use data binding to update media-location data for the media-playing entities without the need to write custom code.

Abstract: Access restriction for computing content is provided by operating a computing device with a first profile, recognizing an attempt to log off of the first profile, and requesting a user to supply a log off credential. If the log off credential is not correct, the computing device continues to operate with the first profile, and if the log off credential is correct, the computing device operates without the first profile.

Abstract: Selective content loading based on complexity is provided by a method of selectively loading content which includes receiving markup data at a client computing device and determining a markup weight for the markup data at the client computing device. The method further includes determining if the markup weight is less than a threshold value at the client computing device. The method further includes, if the markup weight is less than the threshold value, loading the markup data at the client computing device, and if the markup weight is not less than the threshold value, not allowing the markup data to load at the client computing device.

Abstract: This document describes tools that enable a computing device to retrieve large data in smaller blocks. The tools also allow the computing device to receive and display data that does not include display formatting information through the use of templates.

Abstract: This document describes tools capable of updating media-location data for media-playing entities. These tools allow a developer of an application to use data binding to update media-location data for the media-playing entities without the need to write custom code.

Abstract: In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.