Abstract: The embodiments set forth a technique for dynamically adjusting a manner in which notifications are output on a computing device. According to some embodiments, a technique can include (1) identifying that at least one different computing device satisfies a physical proximity threshold relative to the computing device, (2) determining that the at least one different computing device is included in a list of known computing devices associated with the computing device, (3) determining, based on a configuration associated with the at least one computing device, that the at least one different computing device is associated with a respective notification profile maintained by the computing device, and (4) activating the respective notification profile at the computing device to adjust the manner in which notifications are output by the computing device.

Abstract: The embodiments set forth a technique for dynamically adjusting a manner in which notifications are output on a computing device. According to some embodiments, a technique can include (1) identifying that at least one different computing device satisfies a physical proximity threshold relative to the computing device, (2) determining that the at least one different computing device is included in a list of known computing devices associated with the computing device, (3) determining, based on a configuration associated with the at least one computing device, that the at least one different computing device is associated with a respective notification profile maintained by the computing device, and (4) activating the respective notification profile at the computing device to adjust the manner in which notifications are output by the computing device.

Abstract: A tracking architecture is provided that enables data for gestures and head positions to be provided to both native and non-native clients on a computing device. A pipeline component can obtain the raw image data and sensor data and synchronize that data to be processed to determine, for example, location and/or motion data that may correspond to device input. The data can be processed by separate components, such as an event publisher and an event provider, each capable of filtering the location, motion, and/or raw sensor data to generate a set of event data. The event data then can be published to registered listeners or provided in response to polling requests. Head coordinates, gesture data, and other such information can be passed through one or more interface layers enabling the data to be processed by a non-native client on the device.

Abstract: A computing device can be controlled based on changes in the angle of a user's head with respect to the device, such as due to the user tilting the device and/or the user tilting his head with respect to the device. Such control based on the angle of the user's head can be achieved even when the user is operating the device “off-axis” or when the device is not orthogonal and/or not centered with respect to the user. This can be accomplished by using an elastic reference point that dynamically adjusts to a detected angle of the user's head with respect to the device. Such an approach can account for differences between when the user is changing his natural resting position and/or the resting position of the device and when the user is intending to perform a gesture based on the angle of the user's head relative to the device.

Abstract: A device may recognize a tilt gesture when a device rotates about an axis and then back again. The gesture may be recognized using a state machine. Recognition of the gesture may be performed based on a context of a device, where the specific movement of the device during a tilt gesture may change based on the context. The tilt gesture may be confirmed using a classifier trained on features describing the gesture and the context.

Abstract: A tracking architecture is provided that enables data for gestures and head positions to be provided to both native and non-native clients on a computing device. A pipeline component can obtain the raw image data and sensor data and synchronize that data to be processed to determine, for example, location and/or motion data that may correspond to device input. The data can be processed by separate components, such as an event publisher and an event provider, each capable of filtering the location, motion, and/or raw sensor data to generate a set of event data. The event data then can be published to registered listeners or provided in response to polling requests. Head coordinates, gesture data, and other such information can be passed through one or more interface layers enabling the data to be processed by a non-native client on the device.