The present disclosure relates to electronic devices, including but not limited to, portable electronic devices having touch-sensitive displays and their control.
Electronic devices, including portable electronic devices, have gained widespread use and may provide a variety of functions including, for example, telephonic, electronic messaging and other personal information manager (PIM) application functions. Portable electronic devices include, for example, several types of mobile stations such as simple cellular telephones, smart phones, wireless personal digital assistants (PDAs), and laptop computers with wireless 802.11 or Bluetooth capabilities.
Portable electronic devices such as PDAs or smart telephones are generally intended for handheld use and ease of portability. Smaller devices are generally desirable for portability. A touch-sensitive display, also known as a touchscreen display, is particularly useful on handheld devices, which are small and have limited space for user input and output. The information displayed on the touch-sensitive displays may be modified depending on the functions and operations being performed. With continued demand for decreased size of portable electronic devices, touch-sensitive displays continue to decrease in size.
Improvements in devices with touch-sensitive displays are desirable.
The following describes an apparatus for and method of controlling a display. A gesture is detected while the display is in a low-power condition also referred to as a sleep state. The device may or may not be locked in the low-power condition. Informational icons to be displayed are identified, such as icons associated notifications of application information, such as email or text messaging, or device information, such as time or battery level. In one example, while the gesture continues to be detected, e.g., by a touch-sensitive display, the display is progressively illuminated while displaying the identified informational icons. The process may be reversed, for example, by changing the direction of the gesture or by releasing contact with the touch-sensitive display.
A gesture includes a static or moving touch detected by a touch-sensitive display, a 3-dimensional (3D) spatial movement detected by spatial sensors, a touch or 3D spatial movement detected by an optical sensor, an audible input, including a voice command, detected by a speech or audible recognition device, depression of a physical key or button, and so forth. Other types of gestures may be successfully utilized.
Although many examples described herein refer to a gesture detected by a touch-sensitive display, other methods of gesture detection may be utilized. For example, a gesture may be a generalized trajectory description characterized as a sequence of 3D points in time, and as such many different sensors may be utilized to detect such a gesture. The gesture may be performed by moving a portable electronic device or moving one or more body parts, such as fingers or thumbs as a 3D spatial gesture. For example, sensors, such as an accelerometer/gyroscope, or proximity sensors, or time-of-flight cameras may detect such gestures. Gesture recognition and detection techniques of this type are known.
For simplicity and clarity of illustration, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. Numerous details are set forth to provide an understanding of the examples described herein. The examples may be practiced without these details. In other instances, well-known methods, procedures, and components are not described in detail to avoid obscuring the examples described. The description is not to be considered as limited to the scope of the examples described herein.
The disclosure generally relates to an electronic device, such as a portable electronic device or non-portable electronic device. Examples of portable electronic devices include mobile, or handheld, wireless communication devices such as pagers, cellular phones, cellular smart-phones, wireless organizers, personal digital assistants, wirelessly enabled notebook computers, tablet computers, mobile internet devices, electronic navigation devices, and so forth. The portable electronic device may be a portable electronic device without wireless communication capabilities, such as handheld electronic games, digital photograph albums, digital cameras, media players, e-book readers, and so forth. Examples of non portable electronic devices include desktop computers, electronic white boards, smart boards utilized for collaboration, built-in monitors or displays in furniture or appliances, and so forth.
A block diagram of an example of a portable electronic device 100 is shown in
The processor 102 interacts with other components, such as Random Access Memory (RAM) 108, memory 110, a display 112 optionally including a touch-sensitive overlay 114 operably coupled to an electronic controller 116 that together comprise a touch-sensitive display 118, one or more actuators 120, one or more force sensors 122, an auxiliary input/output (I/O) subsystem 124, a data port 126, a speaker 128, a microphone 130, short-range communications 132, and other device subsystems 134. Input via a graphical user interface is provided via the touch-sensitive overlay 114. The processor 102 interacts with the touch-sensitive overlay 114 via the electronic controller 116. Information, such as text, characters, symbols, images, icons, and other items that may be displayed or rendered on a portable electronic device, is displayed on the touch-sensitive display 118 via the processor 102. The display 112 may be any suitable type of display, including a liquid crystal display (LCD), an organic light-emitting diode (OLED) display, and so forth. The processor 102 may interact with an one or more spatial sensors 136, including accelerometers or gyroscopes that may be utilized to detect direction of gravitational forces or gravity-induced reaction forces, proximity sensors, optical sensors, and so forth.
To identify a subscriber for network access, the portable electronic device 100 may utilize a Subscriber Identity Module or a Removable User Identity Module (SIM/RUIM) card 138 for communication with a network, such as the wireless network 150. Alternatively, user identification information may be programmed into memory 110.
The portable electronic device 100 includes an operating system 146 and software programs, applications, or components 148 that are executed by the processor 102 and are typically stored in a persistent, updatable store such as the memory 110. Additional applications or programs may be loaded onto the portable electronic device 100 through the wireless network 150, the auxiliary I/O subsystem 124, the data port 126, the short-range communications subsystem 132, or any other suitable subsystem 134.
A received signal such as a text message, an e-mail message, or web page download is processed by the communication subsystem 104 and input to the processor 102. The processor 102 processes the received signal for output to the display 112 and/or to the auxiliary I/O subsystem 124. A subscriber may generate data items, for example e-mail messages, which may be transmitted over the wireless network 150 through the communication subsystem 104. For voice communications, the overall operation of the portable electronic device 100 is similar. The speaker 128 outputs audible information converted from electrical signals, and the microphone 130 converts audible information into electrical signals for processing.
The touch-sensitive display 118 may be any suitable touch-sensitive display, such as a capacitive, resistive, infrared, surface acoustic wave (SAW) touch-sensitive display, strain gauge, optical imaging, dispersive signal technology, acoustic pulse recognition, and so forth, as known in the art. A capacitive touch-sensitive display includes a capacitive touch-sensitive overlay 114. The overlay 114 may be an assembly of multiple layers in a stack including, for example, a substrate, a ground shield layer, a barrier layer, one or more capacitive touch sensor layers separated by a substrate or other barrier, and a cover. The capacitive touch sensor layers may comprise any suitable material, such as indium tin oxide (ITO).
One or more touches, also known as touch contacts, touch events or gestures, may be detected by the touch-sensitive display 118. The processor 102 may determine attributes of the touch, including a location of a touch. Touch location data may include data for an area of contact or data for a single point of contact, such as a point at or near a center of the area of contact. The location of a detected touch may include x and y components, e.g., horizontal and vertical components, respectively, with respect to one's view of the touch-sensitive display 118. For example, the x location component may be determined by a signal generated from one touch sensor, and the y location component may be determined by a signal generated from another touch sensor. A signal is provided to the controller 116 in response to detection of a touch. A touch may be detected from any suitable input member, such as a finger, thumb, appendage, or other objects, for example, a stylus, pen, or other pointer, depending on the nature of the touch-sensitive display 118. Multiple simultaneous touches may be detected.
An accelerometer or gyroscope 136 may be utilized to detect 3D spatial gestures. A sequence of acceleration values may be detected in the different spatial dimensions as a function of time and constitute trajectory information that can be recognized as a gesture. For example, a quick flick or tilt of the portable electronic device 100 are examples of detectable gestures. A 3D spatial gesture includes a continuous movement, a sequence of movements, and a series of continuous movements or sequences of movements. Proximity sensors, optical sensors, and/or cameras may be utilized to detect 3D spatial gestures comprising motion of objects spaced from the device 100. Scanning of any of these sensors or devices may take place every 100 to 500 ms during low-power condition or at any other suitable time period.
The actuator(s) 120 may be depressed or activated by applying sufficient force to the touch-sensitive display 118 to overcome the actuation force of the actuator 120. The actuator(s) 120 may be actuated by pressing anywhere on the touch-sensitive display 118. The actuator(s) 120 may provide input to the processor 102 when actuated. Actuation of the actuator(s) 120 may result in provision of tactile feedback. When force is applied, the touch-sensitive display 118 is depressible, pivotable, and/or movable. Such a force may actuate the actuator(s) 120. The touch-sensitive display 118 may, for example, float with respect to the housing of the portable electronic device, i.e., the touch-sensitive display 118 may not be fastened to the housing. A mechanical dome switch actuator may be utilized. In this example, tactile feedback is provided when the dome collapses due to imparted force and when the dome returns to the rest position after release of the switch. Alternatively, the actuator 120 may comprise one or more piezoelectric (piezo) devices that provide tactile feedback for the touch-sensitive display 118.
Optional force sensors 122 may be disposed in conjunction with the touch-sensitive display 118 to determine or react to forces applied to the touch-sensitive display 118. The force sensor 122 may be disposed in line with a piezo actuator 120. The force sensors 122 may be force-sensitive resistors, strain gauges, piezoelectric or piezoresistive devices, pressure sensors, quantum tunneling composites, force-sensitive switches, or other suitable devices. Force as utilized throughout the specification, including the claims, refers to force measurements, estimates, and/or calculations, such as pressure, deformation, stress, strain, force density, force-area relationships, thrust, torque, and other effects that include force or related quantities. Optionally, force information related to a detected touch may be utilized to select information, such as information associated with a location of a touch. For example, a touch that does not meet a force threshold may highlight a selection option, whereas a touch that meets a force threshold may select or input that selection option. Selection options include, for example, displayed or virtual keys of a keyboard; selection boxes or windows, e.g., “cancel,” “delete,” or “unlock”; function buttons, such as play or stop on a music player; and so forth. Different magnitudes of force may be associated with different functions or input. For example, a lesser force may result in panning, and a higher force may result in zooming.
A front view of a portable electronic device is shown in
An example of progressively illuminating a display while displaying informational icons is shown in
The gesture continues to be detected as the gesture moves upward, as shown in
The gesture continues to be detected as the gesture continues to move upward, as shown in
The gesture continues to be detected as the gesture reverses direction and continues downward to the location 602 shown in
Alternatively, the gesture may continue upward from the bottom of the display until the gesture is detected at the touch location 702, which results in a gesture greater than or equal to a predetermined distance or length as shown in
A flowchart illustrating a method of controlling a display such as a touch-sensitive display is shown in
The portable electronic device is maintained 802 in a low-power condition, for example, by displaying no information on the display 112 of the touch-sensitive display 118, e.g., the display 112 is blank or black with no pixels illuminated. The processing activities of the device 100 are typically significantly reduced during a low-power condition. Minimal touch sensing is active on the touch-sensitive display 118, such that power usage is minimal. For example, scanning of touch sensors may take place every 100 to 500 ms or at a reduced rate from active touch sensing when in low-power condition. While the display 112/touch-sensitive display 118 is in low-power condition, a gesture is detected 804 on the touch-sensitive display 118, which at least minimally wakes-up the device. The gesture may be a simple touch or a touch that moves. The gesture may be simple or complex. For example, the gesture may be a swipe that moves in a single direction along the display or a touch that hovers or is maintained at or near the same location. Any other gesture may be utilized. The gesture may begin anywhere on the touch-sensitive display 118, although advantage may be gained, for example, by detecting a touch starting at any edge of the display, such as the bottom of the display or a corner of the display. The gesture may be a series or sequence of taps on the touch-sensitive display 118. The location of the taps may or may not be relevant to detecting the gesture.
Informational icons 304, 404 are identified and displayed 806. Identifying informational icons 304, 404 includes, for example, identifying at least one notification to be displayed. Notifications include, for example, notice of a received email, notice of a text message, notice of a missed phone call, a calendar event, a social networking notice, device condition, and so forth. Device conditions include, for example, time of day, date, battery level, network signal strength indication, error condition, software problem, and so forth. Informational icons 304, 404 that are associated with each notification are identified and displayed, such as an envelope for email, a balloon for a text message, a phone for a missed call, an open envelope for a meeting invitation, and so forth. All of the informational icons 304, 404 identified at 806 may be displayed upon detection of the gesture. Alternatively, the informational icons 304, 404 may be progressively or gradually displayed while the gesture is continuously detected, e.g., the quantity of informational icons 304, 404 increases, such as one at a time as the gesture continues 808. Alternatively, the informational icons 304, 404 may be gradually displayed or revealed as the gesture is continuously detected. This effect may be achieved by progressively decreasing the transparency of the displayed informational icons 304, 404, e.g., starting with a transparent or ghosted version of the icon and gradually increasing the opacity of the icon 304, 404 until the informational icons 304, 404 are fully displayed. Transparency in this sense includes the visual effect of being able to see the background through the icons 304, 404. Increasing the opacity of the icon 304, 404 includes reducing the amount of background visible through the icon 304, 404 until to the background cannot be seen through the icon 304, 404 anymore.
While detection of the gesture continues 808, the touch-sensitive display 118 is progressively illuminated 810 while displaying the identified informational icons 304, 404, such as described above. Detection of the gesture continuing includes detecting a continuation of the gesture's movement along the touch-sensitive display 118 and/or detecting a continuation of the gesture in time at or near a single location on the touch-sensitive display 118, e.g., a successive tap with little or no movement of the gesture. The gesture may include a combination of movement and holding of a touch at or near one location on the display 118. Progressively illuminating the display 118 may be performed in a number of ways. For example, the touch-sensitive display 118 may be illuminated beginning at the one end of the display and continuing toward an opposite end of the display, such as shown in the examples in
Optionally, when the duration of the gesture meets a predetermined threshold 812, such as a period of time or a distance, an unlock option or screen is displayed 814, such as shown in
Another option includes progressively dimming the display 118 after the display 118 is illuminated. For example, upon detection 816 of a change in direction of the gesture, illumination of the touch-sensitive display 118 may be progressively reduced as the gesture continues. In a more specific example, the gesture may comprise a touch beginning at the bottom of the display 118 and moving toward the top of the display, followed by moving back toward the bottom of the display 118, such as when the user sees all or as many of the informational icons 304, 404 as desired. In this situation, the touch-sensitive display 118 is gradually illuminated until the touch is detected moving back toward the bottom of the display 118, at which time the display 118 is progressively dimmed 818 until the gesture ends (detection of the gesture does not continue), the display 118 fades to black, or the gesture changes direction again to progressively illuminate the display 118, in which case the process continues at 810. An end of the gesture may be discontinuation of detection of touch data on the touch-sensitive display 118, discontinuation of a recognizable 3D spatial gesture, or end of any other type of gesture. The gesture may be discontinued, for example, when a user gathered the information the user is interested in, such as time, date, notifications, and so forth. An end of the gesture returns the device 100 to the previous low-power or sleep condition.
Another example of progressively illuminating a display while displaying informational icons is shown in
The gesture continues to be detected as the gesture moves upward, as shown in
The gesture continues to be detected as the gesture continues to move upward, as shown in
The gesture continues to be detected as the gesture reverses direction and continues downward to the location 1202 shown in
Alternatively, the gesture may continue upward from the bottom of the display until the gesture is detected at the touch location 1302, which results in a gesture greater than or equal to a predetermined distance or length as shown in
An alternative option is shown in
Although more of the informational icons 304, 404 are displayed as the gesture continues in the above examples, such a gradual display of the informational icons 304, 404 is not essential. For example, upon first detection of the gesture, all of the identified informational icons 304, 404 may be displayed. Such display facilitates a quick and reversible look or peek at the informational icons 304, 404 without requiring completion or continuation of the gesture, and facilitates a quick view of information followed by a quick return to a low-power condition or blank screen.
The above examples illustrate an upward and/or downward gesture beginning at the bottom of the display as the device is oriented. Optionally, different gestures or gestures associates with different edges or sides or corners may be utilized, including static or non-moving gestures. The user may be provided with the option to select the type of gesture, location of gesture, and/or origin of gesture.
When utilizing a touch-sensitive display 118 to detect a gesture, the gesture may comprise a series of taps on the touch-sensitive display 118. The detection of successive taps is detection of continuation of the gesture. A threshold time period may be applied to the detection of the sequence of taps. This series of taps may facilitate the gradual nature of modifying the visual display of informational icons. For example, a first tap may result in activating the display 112 at a first brightness level. A second tap may result in activating the display 112 at a second brightness level, and a third tap may result in activating the display 112 at a third brightness level. The third brightness level may be comparable to the normal brightness level when the device is in full active mode. The number or quantity of taps may also affect the number of informational icons 304, 404 displayed. For example, one tap may result in displaying the time icon 304, two taps may result in displaying informational icons 404 related to applications, and three taps may result in displaying all informational icons 304, 404. Alternatively, one tap may result in displaying informational icons 304 related to device condition, two taps may result in displaying all informational icons 304,404, and three taps may result in returning the display 112 to the low-power condition. The taps may be detected on the display or non-display area and need not be associated with a specific location or the same location. The number of taps may be applied to the brightness level of the display, the quantity of informational icons 304, 404 displayed, or both.
In another example utilizing a touch-sensitive display 118, the gesture may comprise a hovering touch, which may include simply detecting presence of a touch anywhere on the display 118. In one example, detection of motion or movement of the touch is unnecessary, and detection of localized contact for a pre-determined period of time is regarded as a gesture. Differing periods of time may be correlated to different brightness levels. For example, a hovering touch exceeding a first duration may result in activating the display 112 at a first brightness level. The hovering touch continuing and exceeding a second duration may result in activating the display 112 at a second brightness level, and the hovering touch continuing and exceeding a third duration may result in activating the display 112 at a third brightness level. The third brightness level may be comparable to the normal brightness level when the device is in full active mode. The different durations may be entered by a user. The duration of the hovering touch may also be applied to the quantity of informational icons 304, 404 displayed. The duration of the hovering touch may be applied to the brightness level of the display, the quantity of informational icons 304, 404 displayed, or both.
Alternatively, the brightness levels may vary linearly as a function of the duration of the long press up to the level of the normal brightness level when the device is in full active mode. This gradual effect from a black screen until the gesture is no longer detected or normal brightness level is reached.
In another example, one or more infrared sensors may be utilized to detect a simplistic but specific gesture. For example, one or more infrared sensors may detect a hand waving across the display at a predetermined distance.
The gesture may be a combination of gesture types or a compound gesture. For example, the gesture may initially comprise a 3D spatial gesture or voice command that triggers initial wakening of the device 100 followed by a touch detected by the touch-sensitive display 118 as the continuation of the gesture, which causes gradual or progressive change in display of the informational icons 304, 404, gradual or progressive change in the brightness of the display, or both.
In one example, the informational icons 304, 404 may all be displayed upon detection of a gesture during low-power condition, and the display may be gradually illuminated as the gesture continues, thus gradually waking-up the device 100. Alternatively, the informational icons 304, 404 may be gradually displayed in quantity and/or transparency as the gesture continues.
In one example, upon initial detection of the gesture at the location 302 in
Priority levels may be associated with the informational icons 304, 404 to control the order in which the informational icons are displayed when revealed gradually. For example, when multiple locations are of interest, prioritization of the information icons may be associated by importance of the locations to the user.
The illuminated areas 306, 406, 506, 606, 906, 1006, 1106, and 1206 in need not be rectangles, and may be any suitable shape, for example, semi-circular, circular, elliptical, or other shape including complex shapes.
Optionally, contrast levels of the image being displayed may be varied in order to achieve the same or similar result as progressively varying the brightness of the display.
Although information, such as informational icons, keys, or an unlock option, is shown displayed in particular locations in the example, the information may be displayed in any location on the display.
Although the method is advantageous for portable electronic devices due to the limited display size on a portable electronic device, such as a smartphone, the method may be applied to other electronic devices that have a larger display size.
The location of informational icons may be adjusted by the user. For example, the use may identify the quantity, order, or arrangement of informational icons to be displayed.
A method comprises, while a touch-sensitive display is in a low-power condition, detecting a gesture on the touch-sensitive display and identifying any informational icons to be displayed. While the gesture continues to be detected, the touch-sensitive display is progressively illuminated while displaying the identified informational icons. When the gesture comprises a touch at or near a single location on the display, detecting continuation of the gesture may comprise continually detecting the touch. A portable electronic device may comprise the touch-sensitive display.
A method comprises, while a portable electronic device is in a low-power condition, detecting, by the portable electronic device, a gesture. Any informational icons to be displayed are identified. The identified informational icons are displayed without fully illuminating a display of the portable electronic device. Discontinuation of the gesture may result in a return to the low-power condition in which the display is not illuminated. Displaying the identified informational icons may comprise illuminating the informational icons without illuminating a remainder of the display, e.g., an area of the display where the informational icons are not displayed.
Although the above examples illustrate various different features, the features of any example may be utilized with any other example unless the features conflict. For example, features of
The terms left, right, top, bottom, and so forth are utilized herein for purpose of providing a perspective for reference but are not otherwise limiting.
Advantages of the method include providing the ability for the user to gain information from a device without requiring a full wake-up of the device at the normal brightness level of the device. Previously, when a device was asleep or locked, a notification that a new communication was received was viewable only after fully illuminating the display and awakening the device. When the user only wanted to check the time, the user was required to fully illuminate or wake-up the device. In both cases, fully awakening the device may be disadvantageous in terms of power consumption and time to access the desired information. In some situations, fully illuminating the device may be undesirable. For example, in dark locations, light could disrupt the user or other people, e.g., in a theatre, cinema, while in bed, and so forth. A gradual wake-up in these situations avoids unnecessary disruption, and possibly reduces power consumption. Advantageously, power consumption of an OLED display is reduced because a black OLED pixel consumes negligible power compared to a white OLED pixel. Therefore, by reducing the brightness levels and/or reducing the illuminated area of the display reduces power consumption.
Another advantage results from the reversible capability of this method. Either changing direction of the gesture or discontinuing the gesture results in the device returning to the low power condition by dimming the display. This dimming is a particular benefit for users who only want to perform a quick check on their device, e.g., device conditions and/or notifications, and who want to quickly return to the sleep state without requiring a time period to elapse. This capability is useful for users who forget to lock their device, which may result in unintended action of the device, such as “pocket dialing.”
Furthermore, physical keys used to unlock devices are normally placed on top, bottom, or along the sides of devices. When a user desires to utilize one hand to operate the device, pushing unlock buttons may require a shift in grip or inability to operate the device with one hand. Many of the examples do not require a user to shift grip to proceed with operating the device.
The present disclosure may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the disclosure is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.
Number | Name | Date | Kind |
---|---|---|---|
5305435 | Bronson | Apr 1994 | A |
5570109 | Jenson | Oct 1996 | A |
5651107 | Frank et al. | Jul 1997 | A |
5668960 | Kataoka | Sep 1997 | A |
6073109 | Flores et al. | Jun 2000 | A |
6333973 | Smith et al. | Dec 2001 | B1 |
6584181 | Aktas et al. | Jun 2003 | B1 |
7250955 | Beeman et al. | Jul 2007 | B1 |
7283808 | Castell et al. | Oct 2007 | B2 |
7308653 | Lin-Hendel | Dec 2007 | B2 |
7370284 | Andrea et al. | May 2008 | B2 |
7385875 | May et al. | Jun 2008 | B2 |
7430409 | Klassen et al. | Sep 2008 | B2 |
7484213 | Mathew et al. | Jan 2009 | B2 |
7539945 | Conrad et al. | May 2009 | B2 |
7642901 | Kato et al. | Jan 2010 | B2 |
7647559 | Yozell-Epstein et al. | Jan 2010 | B2 |
7752279 | Hardy et al. | Jul 2010 | B2 |
7802206 | Davis et al. | Sep 2010 | B1 |
7844915 | Platzer et al. | Nov 2010 | B2 |
7900074 | Reece et al. | Mar 2011 | B2 |
7904828 | Conrad et al. | Mar 2011 | B2 |
7996045 | Bauer et al. | Aug 2011 | B1 |
8032482 | Rosenberg et al. | Oct 2011 | B2 |
8032597 | Khoo | Oct 2011 | B2 |
8082518 | Flake et al. | Dec 2011 | B2 |
8099681 | Flanagan et al. | Jan 2012 | B2 |
8122364 | Yozell-Epstein et al. | Feb 2012 | B2 |
8134727 | Shmunis et al. | Mar 2012 | B1 |
8140115 | Kahn et al. | Mar 2012 | B1 |
8140975 | Lemay et al. | Mar 2012 | B2 |
8176411 | Palmieri | May 2012 | B2 |
8237664 | Swanbufg et al. | Aug 2012 | B2 |
8239785 | Hinckley et al. | Aug 2012 | B2 |
8249664 | Bauer et al. | Aug 2012 | B1 |
8253695 | Ganatra et al. | Aug 2012 | B2 |
8261213 | Hinckley et al. | Sep 2012 | B2 |
8271660 | Schulzrinne et al. | Sep 2012 | B2 |
8271907 | Kim et al. | Sep 2012 | B2 |
8280962 | Muniz et al. | Oct 2012 | B2 |
8291344 | Chaudhri | Oct 2012 | B2 |
8296332 | Boley et al. | Oct 2012 | B2 |
8300005 | Tateuchi et al. | Oct 2012 | B2 |
8301701 | Goodman et al. | Oct 2012 | B2 |
8356256 | Olsen | Jan 2013 | B2 |
8359017 | Bruchelt | Jan 2013 | B2 |
8359335 | Coker et al. | Jan 2013 | B2 |
8392837 | Li | Mar 2013 | B2 |
8402384 | Scott | Mar 2013 | B2 |
8447264 | Reich et al. | May 2013 | B2 |
8453057 | Stallings et al. | May 2013 | B2 |
8473843 | Lundy et al. | Jun 2013 | B2 |
8473870 | Hinckley et al. | Jun 2013 | B2 |
8479122 | Hotelling et al. | Jul 2013 | B2 |
8539384 | Hinckley et al. | Sep 2013 | B2 |
8659557 | Simmons et al. | Feb 2014 | B2 |
8665214 | Forutanpour et al. | Mar 2014 | B2 |
8689146 | Lazaridis et al. | Apr 2014 | B2 |
8726198 | Rydenhag et al. | May 2014 | B2 |
8730242 | Hao et al. | May 2014 | B2 |
20020098831 | Castell et al. | Jul 2002 | A1 |
20020126155 | Lin-Hendel | Sep 2002 | A1 |
20030070000 | Coker et al. | Apr 2003 | A1 |
20040068545 | Daniell et al. | Apr 2004 | A1 |
20040117451 | Chung | Jun 2004 | A1 |
20040128353 | Goodman et al. | Jul 2004 | A1 |
20040196259 | Bradski | Oct 2004 | A1 |
20040243677 | Curbow et al. | Dec 2004 | A1 |
20050108655 | Andrea et al. | May 2005 | A1 |
20060026521 | Hotelling et al. | Feb 2006 | A1 |
20060075046 | Yozell-Epstein et al. | Apr 2006 | A1 |
20060123360 | Anwar et al. | Jun 2006 | A1 |
20060156240 | Lemay et al. | Jul 2006 | A1 |
20060190833 | SanGiovanni et al. | Aug 2006 | A1 |
20060250377 | Zadesky et al. | Nov 2006 | A1 |
20060270461 | Won et al. | Nov 2006 | A1 |
20060284852 | Hofmeister et al. | Dec 2006 | A1 |
20070011258 | Khoo | Jan 2007 | A1 |
20070016958 | Bodepudi et al. | Jan 2007 | A1 |
20070083600 | Bakos et al. | Apr 2007 | A1 |
20070139372 | Swanburg et al. | Jun 2007 | A1 |
20070152977 | Ng et al. | Jul 2007 | A1 |
20070236468 | Tuli | Oct 2007 | A1 |
20070256035 | Matsuzawa et al. | Nov 2007 | A1 |
20080005247 | Khoo | Jan 2008 | A9 |
20080008163 | Castell et al. | Jan 2008 | A1 |
20080034047 | Rosenberg et al. | Feb 2008 | A1 |
20080046824 | Li et al. | Feb 2008 | A1 |
20080094369 | Ganatra et al. | Apr 2008 | A1 |
20080165151 | Lemay et al. | Jul 2008 | A1 |
20080165160 | Kocienda | Jul 2008 | A1 |
20080174570 | Jobs et al. | Jul 2008 | A1 |
20080189622 | Sanchez et al. | Aug 2008 | A1 |
20080261569 | Britt et al. | Oct 2008 | A1 |
20080272927 | Woolley et al. | Nov 2008 | A1 |
20080273014 | Lowles et al. | Nov 2008 | A1 |
20090006991 | Lindberg et al. | Jan 2009 | A1 |
20090013282 | Mercer | Jan 2009 | A1 |
20090064055 | Chaudhri et al. | Mar 2009 | A1 |
20090094562 | Jeong et al. | Apr 2009 | A1 |
20090095540 | Zachut et al. | Apr 2009 | A1 |
20090135162 | Van De Wijdeven et al. | May 2009 | A1 |
20090144661 | Nakajima et al. | Jun 2009 | A1 |
20090160785 | Chen et al. | Jun 2009 | A1 |
20090174679 | Westerman | Jul 2009 | A1 |
20090195518 | Mattice et al. | Aug 2009 | A1 |
20090199130 | Tsern et al. | Aug 2009 | A1 |
20090237367 | Ryu et al. | Sep 2009 | A1 |
20090249247 | Tseng et al. | Oct 2009 | A1 |
20090252312 | Muniz et al. | Oct 2009 | A1 |
20090267909 | Chen et al. | Oct 2009 | A1 |
20090273583 | Norhammar | Nov 2009 | A1 |
20090278806 | Duarte et al. | Nov 2009 | A1 |
20090292690 | Culbert | Nov 2009 | A1 |
20090307631 | Kim et al. | Dec 2009 | A1 |
20100011304 | Van Os | Jan 2010 | A1 |
20100013782 | Liu et al. | Jan 2010 | A1 |
20100017695 | Palmieri | Jan 2010 | A1 |
20100042954 | Rosenblatt et al. | Feb 2010 | A1 |
20100058226 | Flake et al. | Mar 2010 | A1 |
20100060586 | Pisula et al. | Mar 2010 | A1 |
20100066698 | Seo | Mar 2010 | A1 |
20100079392 | Chiang et al. | Apr 2010 | A1 |
20100079508 | Hodge et al. | Apr 2010 | A1 |
20100095224 | Yozell-Epstein et al. | Apr 2010 | A1 |
20100095239 | McCommons et al. | Apr 2010 | A1 |
20100107067 | Vaisanen et al. | Apr 2010 | A1 |
20100153951 | Jones | Jun 2010 | A1 |
20100156656 | Duarte et al. | Jun 2010 | A1 |
20100169722 | Wu et al. | Jul 2010 | A1 |
20100171753 | Kwon | Jul 2010 | A1 |
20100175018 | Petschnig et al. | Jul 2010 | A1 |
20100182248 | Chu | Jul 2010 | A1 |
20100185989 | Shiplacoff et al. | Jul 2010 | A1 |
20100214237 | Echeverri et al. | Aug 2010 | A1 |
20100218130 | Conrad et al. | Aug 2010 | A1 |
20100231533 | Chaudhri | Sep 2010 | A1 |
20100248689 | Teng et al. | Sep 2010 | A1 |
20100251178 | Lee et al. | Sep 2010 | A1 |
20100289760 | Jonoshita et al. | Nov 2010 | A1 |
20100295772 | Alameh et al. | Nov 2010 | A1 |
20100302172 | Wilairat | Dec 2010 | A1 |
20100306693 | Brinda | Dec 2010 | A1 |
20100306705 | Nilsson | Dec 2010 | A1 |
20110034208 | Gu et al. | Feb 2011 | A1 |
20110035708 | Damale | Feb 2011 | A1 |
20110083111 | Forutanpour et al. | Apr 2011 | A1 |
20110099490 | Barraclough et al. | Apr 2011 | A1 |
20110163970 | Lemay | Jul 2011 | A1 |
20110175839 | Prabhu | Jul 2011 | A1 |
20110185318 | Hinckley et al. | Jul 2011 | A1 |
20110209088 | Hinckley et al. | Aug 2011 | A1 |
20110209097 | Hinckley et al. | Aug 2011 | A1 |
20110209104 | Hinckley et al. | Aug 2011 | A1 |
20110210983 | Theimer et al. | Sep 2011 | A1 |
20110231499 | Stovicek et al. | Sep 2011 | A1 |
20110252369 | Chaudhri | Oct 2011 | A1 |
20110252381 | Chaudhri | Oct 2011 | A1 |
20110256848 | Bok et al. | Oct 2011 | A1 |
20110271181 | Tsai et al. | Nov 2011 | A1 |
20110294467 | Kim et al. | Dec 2011 | A1 |
20110296163 | Abernethy et al. | Dec 2011 | A1 |
20120013552 | Ahn | Jan 2012 | A1 |
20120026194 | Wagner et al. | Feb 2012 | A1 |
20120032979 | Blow et al. | Feb 2012 | A1 |
20120084697 | Reeves | Apr 2012 | A1 |
20120084698 | Sirpal et al. | Apr 2012 | A1 |
20120090004 | Jeong | Apr 2012 | A1 |
20120105358 | Momeyer et al. | May 2012 | A1 |
20120115449 | Bruchelt | May 2012 | A1 |
20120144331 | Tolonen et al. | Jun 2012 | A1 |
20120159380 | Kocienda et al. | Jun 2012 | A1 |
20120192108 | Kolb | Jul 2012 | A1 |
20120206392 | Ng et al. | Aug 2012 | A1 |
20120210214 | Yoo et al. | Aug 2012 | A1 |
20120235930 | Lazaridis et al. | Sep 2012 | A1 |
20120236037 | Lessing et al. | Sep 2012 | A1 |
20120266082 | Webber | Oct 2012 | A1 |
20120280917 | Toksvig et al. | Nov 2012 | A1 |
20120284673 | Lamb et al. | Nov 2012 | A1 |
20120290946 | Schrock et al. | Nov 2012 | A1 |
20120304108 | Jarrett | Nov 2012 | A1 |
20120311444 | Chaudhri | Dec 2012 | A1 |
20120326984 | Ghassabian | Dec 2012 | A1 |
20120331424 | Lazaridis et al. | Dec 2012 | A1 |
20130002524 | Sirpal et al. | Jan 2013 | A1 |
20130007612 | Kangas et al. | Jan 2013 | A1 |
20130033477 | Sirpal et al. | Feb 2013 | A1 |
20130063383 | Anderssonreimer et al. | Mar 2013 | A1 |
20130083260 | Minami | Apr 2013 | A1 |
20130097556 | Louch | Apr 2013 | A1 |
20130117689 | Lessing et al. | May 2013 | A1 |
20130117718 | Lazaridis et al. | May 2013 | A1 |
20130141371 | Hallford et al. | Jun 2013 | A1 |
20130143518 | Singer et al. | Jun 2013 | A1 |
20130167066 | Scott | Jun 2013 | A1 |
20130185650 | Gutowitz | Jul 2013 | A1 |
20130187863 | Rydenhag et al. | Jul 2013 | A1 |
20130187869 | Rydenhag et al. | Jul 2013 | A1 |
20130191791 | Rydenhag et al. | Jul 2013 | A1 |
20130215061 | Rydenhag et al. | Aug 2013 | A1 |
20130227495 | Rydenhag et al. | Aug 2013 | A1 |
Number | Date | Country |
---|---|---|
2015176 | Jan 2009 | EP |
2045700 | Apr 2009 | EP |
2068236 | Jun 2009 | EP |
2109030 | Oct 2009 | EP |
2383636 | Nov 2011 | EP |
2458493 | May 2012 | EP |
2485138 | Aug 2012 | EP |
10-2008-0041809 | May 2008 | KR |
10-2009-0036578 | Apr 2009 | KR |
10-2010-0032660 | Mar 2010 | KR |
2004051451 | Jun 2004 | WO |
2009097555 | Aug 2009 | WO |
2009120925 | Oct 2009 | WO |
2010040670 | Apr 2010 | WO |
2012097385 | Jul 2012 | WO |
2012128795 | Sep 2012 | WO |
Entry |
---|
Office Action in related U.S. Appl. No. 13/619,213 issued Apr. 18, 2013, 47 pages. |
International Searching Authority, International Search Report and Written Opinion issued in related International Application No. PCT/US2013/022511, dated May 10, 2013, 10 pages. |
“User Guide” Samsung Epic 4G, A Galaxy S Phone, Sprint Oct. 8, 2010, pp. 268. |
Office Action issued Jul. 16, 2013, related U.S. Appl. No. 13/826,657, 31 pages. |
http://www.evernote.com/peek/ Retrieved Aug. 27, 2012, 2 pages. |
International Searching Authority, International Search Report and Written Opinion issued in connection with International Application No. PCT/US2012/022197, dated Sep. 5, 2012, 14 pages. |
http://www.jimblackler.net/blog/?p=67/ “QuickCalendar, an application for Android written in Java” Retrieved Oct. 18, 2012, 6 pages. |
http://www.support.apple.com/kb/HT3756/ “iOS: Understanding Notifications” Retrieved Oct. 18, 2012, 3 pages. |
Android Users Guide 2.3 (Google, Inc.) Dec. 13, 2010, see pp. 29-30, pp. 380. (English). |
Android Users Guide 2.3 (Google, Inc.) Dec. 13, 2010, see pp. 27-28, pp. 368. (Korean). |
http://www.gigaom.com/2011/10/12/ios-5-notifications-and-notification-center/, Retrieved May 2, 2013, Asch, Josh, “iOS 5: Notifications and Notification Center”, Tech News and Analysis, Oct. 12, 2011, four pages. |
Office Action issued in corresponding U.S. Appl. No. 13/619,213 issued Nov. 19, 2012, 36 pages. |
European Patent Office, Communication pursuant to Rules 161(1) and 162 EPC issued in connection with EP Application 12702697.9, dated Sep. 4, 2014, 2 pages. |
Number | Date | Country | |
---|---|---|---|
20130187863 A1 | Jul 2013 | US |