Abstract: Selectively caching content related to routing data in a computing device. Prior to traversing a route, one or more access points to a network are identified. An expected level of access to a network (e.g., signal strength) along the route is determined. Portions of the route are selected based on the expected level of access. Content corresponding to at least one of the selected portions is received and stored for access during traversal of the route. For example, map images for areas expected to have poor network connectivity are cached prior to traversing the route to ensure that routing data is displayed to a user when in those areas. During transversal of the route, content is obtained and cached if a current level of access is less than a defined threshold.

Abstract: Selectively caching content related to routing data in a computing device. Prior to traversing a route, one or more access points to a network are identified. An expected level of access to a network (e.g., signal strength) along the route is determined. Portions of the route are selected based on the expected level of access. Content corresponding to at least one of the selected portions is received and stored for access during traversal of the route. For example, map images for areas expected to have poor network connectivity are cached prior to traversing the route to ensure that routing data is displayed to a user when in those areas. During transversal of the route, content is obtained and cached if a current level of access is less than a defined threshold.

Abstract: Described is a system and method used in manufacturing computer devices, in which a single manufacturing image file contains an internal partition and file system layout into which individual operating system component packages are written. The image file is independent of any particular storage technology. To generate the file, a disk image utility tool inputs a memory configuration file and a package-to-partition mapping file to create the partitions/file systems within the image file. The operating system components (package) are written into the partitions. To store (e.g., flash) the image file's data on a particular storage device, the image file is post-processed to customize the data for a particular storage device.

Abstract: Described is a system and method in which software updates in the form of self-contained, secure entities are applied to an embedded device's non-volatile storage in a failsafe manner. Various types of software updates may be applied, and updates may contain executable code and/or data. Following a reboot, an initial program loader determines an update mode, and if updating, boots to a special update loader. The update loader processes update packages to apply the updates. Kernel partition, system partition and reserve section updates may be updated with entire files or binary difference files, with failure handling mechanisms are provided for each type of update. Updates may be simulated before committing them. Updates may be relocated in memory as appropriate for a device.