Abstract: Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for managing the panic level of a device are disclosed. In one aspect, a method includes the actions of generating first diagnostic data that is associated with the computing device. The actions further include transmitting, to a server, the first diagnostic data. The actions further include receiving, from the server, an error response that indicates an error occurred because of transmitting the first diagnostic data. The actions further include, in response to receiving the error response, ceasing transmitting, to the server, second diagnostic data that is associated with the computing device.

Abstract: The present technology relates to location request management using freshness metrics. A request manager is disclosed that manages location requests at a computing device. The request manager receives an updateable location freshness configuration specifying a location freshness metric for each of one or more location estimation requesters. Upon receiving a location estimation request from a requester, the request manager requests a prior location estimate from a location API. The location API returns the prior location estimate and the amount of time elapsed since it was determined to the request manager. The request manager determines if the elapsed time satisfies the freshness metric. If so, the request manager satisfies the location request with the prior location estimate. If not, the request manager retrieves a current location estimate from the API and satisfies the location request with the current location estimate.

Abstract: Aspects of the present disclosure relate to implementing on-device latency detection into operating system (OS)-level functionality of a client device in client-server and/or network communications. An example method includes extracting packet headers from data-connection packets transmitted between a local application client and a remote application server. Data records including packet headers and timestamps are stored. Data records for related data-connection packets (e.g., queries and responses, handshakes) are identified via the packet headers, and timestamps of the identified data records are compared to determine latency measurements. Latency measurements are then distributed to relevant application clients locally residing on an upper layer. The latency measurements are presented in dashboard display to an end user and used for server-side dynamic load balancing.

Abstract: Aspects of the present disclosure relate to implementing on-device latency detection into operating system (OS)-level functionality of a client device in client-server and/or network communications. An example method includes extracting packet headers from data-connection packets transmitted between a local application client and a remote application server. Data records including packet headers and timestamps are stored. Data records for related data-connection packets (e.g., queries and responses, handshakes) are identified via the packet headers, and timestamps of the identified data records are compared to determine latency measurements. Latency measurements are then distributed to relevant application clients locally residing on an upper layer. The latency measurements are presented in dashboard display to an end user and used for server-side dynamic load balancing.

Abstract: Aspects of the present disclosure relate to implementing on-device latency detection into operating system (OS)-level functionality of a client device in client-server and/or network communications. An example method includes extracting packet headers from data-connection packets transmitted between a local application client and a remote application server. Data records including packet headers and timestamps are stored. Data records for related data-connection packets (e.g., queries and responses, handshakes) are identified via the packet headers, and timestamps of the identified data records are compared to determine latency measurements. Latency measurements are then distributed to relevant application clients locally residing on an upper layer. The latency measurements are presented in dashboard display to an end user and used for server-side dynamic load balancing.