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: 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: In embodiments of media asset voting, a voting application is executed at a controllable device to interface the controllable device with portable devices via a wireless network. The voting application may be initiated at the controllable device by one of the portable devices. A request can be communicated from the controllable device to the portable devices to initiate each of the portable devices sending a user-selected vote for media asset selection at the controllable device. The controllable device receives the user-selected votes from one or more of the portable devices, and the voting application can aggregate each received vote to determine voting results. A media asset can then be selected at the controllable device based on the voting results. Alternatively or in addition, the voting results can be displayed for viewing on a display device that corresponds to the controllable 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: In embodiments of media asset voting, a voting application is executed at a controllable device to interface the controllable device with portable devices via a wireless network. The voting application may be initiated at the controllable device by one of the portable devices. A request can be communicated from the controllable device to the portable devices to initiate each of the portable devices sending a user-selected vote for media asset selection at the controllable device. The controllable device receives the user-selected votes from one or more of the portable devices, and the voting application can aggregate each received vote to determine voting results. A media asset can then be selected at the controllable device based on the voting results. Alternatively or in addition, the voting results can be displayed for viewing on a display device that corresponds to the controllable 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: Embodiments of seamlessly cycled video resources are described. In embodiments, program previews can be displayed where each program preview corresponds to a channel that is user-selectable for viewing a program. A subsequent channel can be determined that is user-selectable to display a program preview of an additional program, where the subsequent channel is included in a channel list that sequentially lists the channels. The subsequent channel that corresponds to the additional program can be pre-tuned before the subsequent channel is selected to display the program preview of the additional program.

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 capable of enabling a media device to assign available resources to media content prior to receiving a request to display that media content. In one embodiment, the tools determine a next media content to be requested and available resources on a media device to display that next content. The tools may assign the available resources to the next page of media content prior to receiving a request to display the next page of media content.