Application tune manifests and tune state recovery
View Patent ↗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.
1. A method implemented in a device, the method comprising:
receiving a request at the device to run an application, the application having an associated tune manifest identifying one or more hardware resources of the device that the application may use;
comparing the tune manifest to a device resource record stored on the device;
checking, 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;
running the application if the one or more resources identified in the tune manifest can be satisfied by the device, otherwise presenting a notification of a conflict between the application and the device;
identifying when the application is exited;
retrieving, in response to the application being exited, a device tune state that identifies a content source to which the device was tuned prior to running the application; and
restoring the device to the device tune state including tuning the device to the content source.
2. A method as recited in claim 1 , further comprising obtaining, in response to the request, the application from a remote service, and wherein the application includes the associated tune manifest.
3. A method as recited in claim 1 , wherein the checking is further based at least in part on resources that may be used by an additional application that is running on the device.
4. A method as recited in claim 1 , wherein the device resource record identifies one or more hardware resources of the device.
5. A method as recited in claim 3 , wherein the one or more hardware resources of the device comprises both an amount of memory of the device and a bandwidth capacity of a network to which the device is coupled.
6. A method as recited in claim 3 , wherein the device resource record further identifies resources that may be used by an additional application that is running on the device.
7. A method as recited in claim 1 , further comprising:
receiving a request to run an additional application;
checking whether an additional tune manifest is associated with the additional application; and
for the additional application, performing the comparing, checking, and running only if the additional tune manifest is associated with the additional application.
8. A method as recited in claim 1 , further comprising:
receiving, in response to the notification, a request to cancel running of the application; and
canceling running of the application in response to the request to cancel running of the application.
9. A method as recited in claim 1 , further comprising altering one or more settings of the device based on the tune manifest.
10. A method as recited in claim 1 , further comprising changing a configuration setting of the device to free resources that were reserved for tuning to a higher resolution content stream.
11. A method as recited in claim 1 , wherein the device tune state further identifies a location in content being received from the content source at which playback of the content is to be resumed.
12. A method as recited in claim 1 , wherein the device tune state further identifies a channel of the content source to which the device was tuned prior to running the application.
13. One or more non-transitory computer-readable storage media having stored thereon multiple instructions that, when executed by one or more processors of a device, cause the one or more processors to:
receive a request on the device to run an application, the application having an associated tune manifest identifying one or more resources of the device that the application may use;
save a device tune state including a content source to which the device is tuned;
compare the tune manifest to a device resource record stored on the device;
check, based at least in part on the comparison, 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:
run the application;
identify when the application is exited;
retrieve, in response to the application being exited, the device tune state; and
restore the device to the device tune state including tuning the device to the content source; and
if the one or more resources identified in the tune manifest cannot be satisfied by the device, then display a notification of a conflict between the application and the device.