Abstract: A downhole tool including a gravel pack assembly, a remotely addressable actuator connected to the gravel pack assembly, and a valve responsive to the actuator, the valve opening and closing a washdown path through the tool. A method for gravel packing a borehole including running a tool to a target depth in the borehole, flowing washdown fluid through the tool, sending an electric signal to the actuator to close the valve, and flowing through a cross over port of the gravel pack assembly. A borehole system including a borehole in a subsurface formation, a tool disposed within the borehole.

Abstract: An apparatus can include a thermal component. The thermal component can include a first side of the thermal component. The thermal component can include a second side of the thermal component. The first side of the thermal component can couple with a battery cell. The second side of the thermal component can couple with a structural member. The structural member can support the battery cell.

Abstract: Disclosed are various approaches for secure inter-application communication with unmanaged applications using certificate enrollment. A certificate signing request can be received from an unmanaged application via an inter-application communication method supported by an operating system of a computing device, and an identity of the unmanaged application can be verified. The certificate signing request can be provided to a certifying authority, and a certificate can be received from the certifying authority. The certificate can be provided to the unmanaged application.

Abstract: Disclosed are various embodiments for replacing hard-coded certificate pinning with blockchain based certificate pinning. A signing device can obtain a public key from an endpoint device, produce a signature for the public key, and store the public key on a distributed data store, such as a blockchain. A client device can obtain and validate the public keys from the distributed data store and use the public keys to establish a secure connection between the client device and the endpoint device.

Abstract: Scheduling optimizations for services are described. In one example, a priority category, such as a high, low, or other priority category, can be determined for a service of an application executing on a computing device. If the application is running as a background application on the computing device, an exception to the start of the service can be returned by the operating system of the device, due to background execution limits on the device. In that case, the start of the service can be managed by a service manager of the application based on the priority category for the service. If the priority category for the service is high, the background application can call a foreground service. The call for the foreground service can bring the application to the foreground, and the service manager can again call for the start of the service after the foreground service is running.

Abstract: Scheduling optimizations for services are described. In one example, a priority category, such as a high, low, or other priority category, can be determined for a service of an application executing on a computing device. If the application is running as a background application on the computing device, an exception to the start of the service can be returned by the operating system of the device, due to background execution limits on the device. In that case, the start of the service can be managed by a service manager of the application based on the priority category for the service. If the priority category for the service is high, the background application can call a foreground service. The call for the foreground service can bring the application to the foreground, and the service manager can again call for the start of the service after the foreground service is running.

Abstract: Systems herein allow an email application to manage passcode-based encryption (“PBE”) operations on an operating system (OS) that deletes a user passcode from memory. The email application can utilize a lock safe component that implements OS lifecycle classes. The lock safe component can receive an OS event, such as an activity, fragment, service, or SyncManager event. Before causing the email application to handle the OS event, the lock safe component can check whether the user passcode exists in memory. If it does not, the lock safe component can queue services for later operation once the passcode exists. Likewise, the lock safe component can cause the email application to prompt for the user passcode before a user interface (“UI”) performs activities or fragments, and pass state information to the email application for performing the activities or fragments.

Abstract: Systems herein allow an email application to manage passcode-based encryption (“PBE”) operations on an operating system (OS) that deletes a user passcode from memory. The email application can utilize a lock safe component that implements OS lifecycle classes. The lock safe component can receive an OS event, such as an activity, fragment, service, or SyncManager event. Before causing the email application to handle the OS event, the lock safe component can check whether the user passcode exists in memory. If it does not, the lock safe component can queue services for later operation once the passcode exists. Likewise, the lock safe component can cause the email application to prompt for the user passcode before a user interface (“UI”) performs activities or fragments, and pass state information to the email application for performing the activities or fragments.