Abstract: Low drift force sensing conductors include small conductive balls in the ink used to create the conductor. The use of conductive balls reduces sensor drift while avoiding unwanted side-effects like temperature sensitivity. The conductive balls are made of sized synthetic graphite, a derivative of petroleum pitch or coal tar or any other suitable substance. Force sensors incorporating these balls also demonstrate enhanced sensitivity to low forces.

Abstract: Embodiments of the disclosure provide access to data in a compressed container through dynamic redirection, without storing decompressed data in persistent memory. The compressed container is stored in a first portion of memory. User data and reference files, with redirect pointers, for accessing corresponding files in the compressed container are stored in a second portion of memory. A command to access data is detected by a computing device. The redirect pointer in the reference file associated with the command redirects access to the corresponding compressed version of data stored in the compressed container. The corresponding accessed compressed version of data is decompressed on the fly and provided in response to the command without storing the decompressed data in persistent memory. Some embodiments provide integrity protection to validate the data coming from the compressed container.

Abstract: Embodiments of the disclosure provide access to data in a compressed container through dynamic redirection, without storing decompressed data in persistent memory. The compressed container is stored in a first portion of memory. User data and reference files, with redirect pointers, for accessing corresponding files in the compressed container are stored in a second portion of memory. A command to access data is detected by a computing device. The redirect pointer in the reference file associated with the command redirects access to the corresponding compressed version of data stored in the compressed container. The corresponding accessed compressed version of data is decompressed on the fly and provided in response to the command without storing the decompressed data in persistent memory. Some embodiments provide integrity protection to validate the data coming from the compressed container.

Abstract: A software system, such as an operating system, that has multiple parts can be deployed to a computing device incrementally, rather than all at once. The software system self-adapts to the user's needs by installing and removing system extensions automatically without user intervention. A core part of the software system is deployed in the computing device, and system extensions are delivered to the computing device when needed. The software system is aware of the system extensions, so they appear to be part of the system, even though they have not yet been downloaded. The system extensions can be delivered to the computing system on demand or over time during idle times of the computing device. Unused system extensions can be removed from the computing device, and can be downloaded again when next needed.

Abstract: A system manages version information for a group of software components by maintaining a version repository containing version information for all of the components. The system determines a baseline for the components, modifies data in the repository in connection with updating software components, and accesses the data in the repository to determine version information for the components. The system described herein also determines if a group of software components correspond to a particular baseline by maintaining baseline information in the version repository. The system obtains the particular baseline for the group of components, compares the version information for each of the components with a corresponding minimum version provided in connection with the baseline, and determines whether a group of software components correspond to the particular baseline.

Abstract: A software system, such as an operating system, that has multiple parts can be deployed to a computing device incrementally, rather than all at once. The software system self-adapts to the user's needs by installing and removing system extensions automatically without user intervention. A core part of the software system is deployed in the computing device, and system extensions are delivered to the computing device when needed. The software system is aware of the system extensions, so they appear to be part of the system, even though they have not yet been downloaded. The system extensions can be delivered to the computing system on demand or over time during idle times of the computing device. Unused system extensions can be removed from the computing device, and can be downloaded again when next needed.