text:
A computer-implemented method for use in conjunction with a computing device with a touch screen display comprises displaying a first soft keyboard. While displaying the first soft keyboard, a key for selecting a second soft keyboard different from the first soft keyboard is displayed. A first contact is detected on the key for selecting the second soft keyboard. In response to detecting the first contact, the second soft keyboard is displayed. Movement of the first contact is detected to a character-insertion key in the second soft keyboard. Lift off of the first contact is detected at the character-insertion key in the second soft keyboard to which the first contact moved. In response to detecting the lift off, a character is inserted that corresponds to the character-insertion key in the second soft keyboard to which the first contact moved and the display of the second soft keyboard is ceased.
This application is a continuation of U.S. patent application Ser. No. 14/042,472, filed Sep. 30, 2013, which is a continuation of U.S. patent application Ser. No. 12/163,886, filed Jun. 27, 2008, both of which are incorporated by reference herein in their entirety.
This application is related to the following applications: (1) U.S. patent application Ser. No. 10/188,182, “Touch Pad For Handheld Device,” filed Jul. 1, 2002; (2) U.S. patent application Ser. No. 10/722,948, “Touch Pad For Handheld Device,” filed Nov. 25, 2003; (3) U.S. patent application Ser. No. 10/643,256, “Movable Touch Pad With Added Functionality,” filed Aug. 18, 2003; (4) U.S. patent application Ser. No. 10/654,108, “Ambidextrous Mouse,” filed Sep. 2, 2003; (5) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (6) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (7) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices” filed Jan. 18, 2005; (8) U.S. patent application Ser. No. 11/057,050, “Display Actuator,” filed Feb. 11, 2005; (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006; and (10) U.S. patent application Ser. No. 11/850,635, “Touch Screen Device, Method, and Graphical User Interface for Determining Commands by Applying Heuristics,” filed Sep. 5, 2007. All of these applications are incorporated by reference herein in their entirety.
The disclosed embodiments relate generally to electronic devices with touch screen displays, and more particularly, to electronic devices having a user interface for inserting a character from an alternate keyboard on the touch screen display.
As portable electronic devices become more compact, and the number of functions performed by a given device increase, it has become a significant challenge to design a user interface that allows users to easily interact with a multifunction device. This challenge is particular significant for handheld portable devices, which have much smaller screens than desktop or laptop computers. This situation is unfortunate because the user interface is the gateway through which users receive not only content but also responses to user actions or behaviors, including user attempts to access a device's features, tools, and functions. Some portable communication devices (e.g., mobile telephones, sometimes called mobile phones, cell phones, cellular telephones, and the like) have resorted to adding more pushbuttons, increasing the density of push buttons, overloading the functions of pushbuttons, or using complex menu systems to allow a user to access, store and manipulate data. These conventional user interfaces often result in complicated key sequences and menu hierarchies that must be memorized by the user.
Many conventional user interfaces, such as those that include physical pushbuttons, are also inflexible. This may prevent a user interface from being configured and/or adapted by either an application running on the portable device or by users. When coupled with the time consuming requirement to memorize multiple key sequences and menu hierarchies, and the difficulty in activating a desired pushbutton, such inflexibility is frustrating to most users.
Electronic devices with touch screens may display a variety of different soft keyboards. For example, letter keys may be accessed on one soft keyboard while numbers, punctuation, and other symbols are inserted using another soft keyboard. In conventional user interfaces, accessing two different soft keyboard layouts may be tedious and awkward when a user desires to enter a character from an alternate keyboard.
Accordingly, there is a need for electronic devices with touch screen displays that have more transparent and intuitive user interfaces for using multiple soft keyboards. Such interfaces increase efficiency and user satisfaction with such electronic devices.
The above deficiencies and other problems associated with user interfaces for devices with touch screen displays are reduced or eliminated by the disclosed multifunction device. In some embodiments, the device is portable. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen”) with a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through finger contacts and gestures on the touch-sensitive display. In some embodiments, the functions may include telephoning, video conferencing, c-mailing, instant messaging, blogging, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. Instructions for performing these functions may be included in a computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a computer-implemented method is performed at a portable electronic device with a touch screen display. The computer-implemented method includes displaying a first soft keyboard. The first soft keyboard contains a plurality of character-insertion keys. While displaying the first soft keyboard, a key for selecting a second soft keyboard different from the first soft keyboard is displayed. The second soft keyboard contains a plurality of character-insertion keys. A first contact is detected on the key for selecting the second soft keyboard. In response to detecting the first contact on the key for selecting the second soft keyboard, the second soft keyboard is displayed. The first contact is detected moving on the touch screen display to a character-insertion key in the second soft keyboard. Lift off of the first contact is detected from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved. In response to detecting lift off of the first contact from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved, a character is inserted that corresponds to the character-insertion key in the second soft keyboard to which the first contact moved and the display of the second soft keyboard is ceased.
In accordance with some embodiments, a graphical user interface on a portable electronic device with a touch screen display includes a first soft keyboard containing a plurality of character-insertion keys; a key for selecting a second soft keyboard different from the first soft keyboard; and the second soft keyboard, the second soft keyboard containing a plurality of character-insertion keys. The key for selecting the second soft keyboard is displayed while displaying the first soft keyboard. In response to detecting a first contact on the key for selecting the second soft keyboard, the second soft keyboard is displayed. The first contact is detected moving on the touch screen display to a character-insertion key in the second soft keyboard. Lift off of the first contact from the touch screen display is detected at the character-insertion key in the second soft keyboard to which the first contact moved. In response to detecting lift off of the first contact from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved, a character is inserted that corresponds to the character-insertion key in the second soft keyboard to which the first contact moved and the display of the second soft keyboard is ceased.
In accordance with some embodiments, a portable electronic device includes: a touch screen display; one or more processors; memory; and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for: displaying a first soft keyboard, the first soft keyboard containing a plurality of character-insertion keys; while displaying the first soft keyboard, displaying a key for selecting a second soft keyboard different from the first soft keyboard, the second soft keyboard containing a plurality of character-insertion keys; detecting a first contact on the key for selecting the second soft keyboard; in response to detecting the first contact on the key for selecting the second soft keyboard, displaying the second soft keyboard; detecting the first contact moving on the touch screen display to a character-insertion key in the second soft keyboard; detecting lift off of the first contact from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved; and in response to detecting lift off of the first contact from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved, inserting a character that corresponds to the character-insertion key in the second soft keyboard to which the first contact moved and ceasing to display the second soft keyboard.
In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which when executed by a portable electronic device with a touch screen display, cause the portable electronic device to: display a first soft keyboard, the first soft keyboard containing a plurality of character-insertion keys; while displaying the first soft keyboard, display a key for selecting a second soft keyboard different from the first soft keyboard, the second soft keyboard containing a plurality of character-insertion keys; detect a first contact on the key for selecting the second soft keyboard; in response to detecting the first contact on the key for selecting the second soft keyboard, display the second soft keyboard; detect the first contact moving on the touch screen display to a character-insertion key in the second soft keyboard; detect lift off of the first contact from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved; and in response to detecting lift off of the first contact from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved, insert a character that corresponds to the character-insertion key in the second soft keyboard to which the first contact moved and cease to display the second soft keyboard.
In accordance with some embodiments, a portable electronic device includes: a touch screen display; means for displaying a first soft keyboard, the first soft keyboard containing a plurality of character-insertion keys; while displaying the first soft keyboard, means for displaying a key for selecting a second soft keyboard different from the first soft keyboard, the second soft keyboard containing a plurality of character-insertion keys; means for detecting a first contact on the key for selecting the second soft keyboard; in response to detecting the first contact on the key for selecting the second soft keyboard, means for displaying the second soft keyboard; means for detecting the first contact moving on the touch screen display to a character-insertion key in the second soft keyboard; means for detecting lift off of the first contact from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved; and in response to detecting lift off of the first contact from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved, means for inserting a character that corresponds to the character-insertion key in the second soft keyboard to which the first contact moved and means for ceasing to display the second soft keyboard.
Thus, the invention provides a simple, efficient, and easy-to-use interface for inserting a character from an alternate keyboard on an electronic device with a touch screen display.
FIGS. 1A and 1B are block diagrams illustrating portable multifunction devices with touch-sensitive displays in accordance with some embodiments.
FIG. 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.
FIGS. 3A-3C illustrate exemplary user interfaces for unlocking a portable electronic device in accordance with some embodiments.
FIGS. 4A and 4B illustrate exemplary user interfaces for a menu of applications on a portable multifunction device in accordance with some embodiments.
FIGS. 5A-5H illustrate exemplary user interfaces for inserting a character from an alternate keyboard on a touch screen display in accordance with some embodiments.
FIGS. 6A-C is a flow diagram illustrating a method of inserting a character from an alternate keyboard on a touch screen display in accordance with some embodiments.
It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first gesture could be termed a second gesture, and, similarly, a second gesture could be termed a first gesture, without departing from the scope of the present invention.
The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the description of the invention and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of a portable multifunction device, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device such as a mobile telephone that also contains other functions, such as PDA and/or music player functions.
The user interface may include a physical click wheel in addition to a touch screen or a virtual click wheel displayed on the touch screen. A click wheel is a user-interface device that may provide navigation commands based on an angular displacement of the wheel or a point of contact with the wheel by a user of the device. A click wheel may also be used to provide a user command corresponding to selection of one or more items, for example, when the user of the device presses down on at least a portion of the wheel or the center of the wheel. Alternatively, breaking contact with a click wheel image on a touch screen surface may indicate a user command corresponding to selection. For simplicity, in the discussion that follows, a portable multifunction device that includes a touch screen is used as an exemplary embodiment. It should be understood, however, that some of the user interfaces and associated processes may be applied to other devices, such as personal computers and laptop computers, which may include one or more other physical user-interface devices, such as a physical click wheel, a physical keyboard, a mouse and/or a joystick.
The device supports a variety of applications, such as one or more of the following: a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a blogging application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that may be executed on the device may use at least one common physical user-interface device, such as the touch screen. One or more functions of the touch screen as well as corresponding information displayed on the device may be adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch screen) of the device may support the variety of applications with user interfaces that are intuitive and transparent.
The user interfaces may include one or more soft keyboard embodiments. The soft keyboard embodiments may include standard (QWERTY) and/or non-standard configurations of symbols on the displayed icons of the keyboard, such as those described in U.S. patent application Ser. No. 11/459,606, “Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, and Ser. No. 11/459,615, “Touch Screen Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, the contents of which are hereby incorporated by reference in their entirety. The keyboard embodiments may include a reduced number of icons (or soft keys) relative to the number of keys in existing physical keyboards, such as that for a typewriter. This may make it easier for users to select one or more icons in the keyboard, and thus, one or more corresponding symbols. The keyboard embodiments may be adaptive. For example, displayed icons may be modified in accordance with user actions, such as selecting one or more icons and/or one or more corresponding symbols. One or more applications on the portable device may utilize common and/or different keyboard embodiments. Thus, the keyboard embodiment used may be tailored to at least some of the applications. In some embodiments, one or more keyboard embodiments may be tailored to a respective user. For example, one or more keyboard embodiments may be tailored to a respective user based on a word usage history (lexicography, slang, individual usage) of the respective user. Some of the keyboard embodiments may be adjusted to reduce a probability of a user error when selecting one or more icons, and thus one or more symbols, when using the soft keyboard embodiments.
Attention is now directed towards embodiments of the device. FIGS. 1A and 1B are block diagrams illustrating portable multifunction devices 100 with touch-sensitive displays 112 in accordance with some embodiments. The touch-sensitive display 112 is sometimes called a “touch screen” for convenience, and may also be known as or called a touch-sensitive display system. The device 100 may include a memory 102 (which may include one or more computer readable storage mediums), a memory controller 122, one or more processing units (CPU's) 120, a peripherals interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input/output (I/O) subsystem 106, other input or control devices 116, and an external port 124. The device 100 may include one or more optical sensors 164. These components may communicate over one or more communication buses or signal lines 103.
It should be appreciated that the device 100 is only one example of a portable multifunction device 100, and that the device 100 may have more or fewer components than shown, may combine two or more components, or a may have a different configuration or arrangement of the components. The various components shown in FIGS. 1A and 1B may be implemented in hardware, software or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits.
Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of the device 100, such as the CPU 120 and the peripherals interface 118, may be controlled by the memory controller 122.
The peripherals interface 118 couples the input and output peripherals of the device to the CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for the device 100 and to process data.
In some embodiments, the peripherals interface 118, the CPU 120, and the memory controller 122 may be implemented on a single chip, such as a chip 104. In some other embodiments, they may be implemented on separate chips.
The RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. The RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. The RF circuitry 108 may include well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. The RF circuitry 108 may communicate with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication may use any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11 n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), and/or Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS)), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
The audio circuitry 110, the speaker 111, and the microphone 113 provide an audio interface between a user and the device 100. The audio circuitry 110 receives audio data from the peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal to human-audible sound waves. The audio circuitry 110 also receives electrical signals converted by the microphone 113 from sound waves. The audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to the peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or the RF circuitry 108 by the peripherals interface 118. In some embodiments, the audio circuitry 110 also includes a headset jack (e.g. 212, FIG. 2). The headset jack provides an interface between the audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone).
The I/O subsystem 106 couples input/output peripherals on the device 100, such as the touch screen 112 and other input/control devices 116, to the peripherals interface 118. The I/O subsystem 106 may include a display controller 156 and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input/control devices 116 may include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) may include an up/down button for volume control of the speaker Ill and/or the microphone 113. The one or more buttons may include a push button (e.g., 206, FIG. 2). A quick press of the push button may disengage a lock of the touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) may turn power to the device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
The touch-sensitive touch screen 112 provides an input interface and an output interface between the device and a user. The display controller 156 receives and/or sends electrical signals from/to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.
A touch screen 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. The touch screen 112 and the display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on the touch screen 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on the touch screen. In an exemplary embodiment, a point of contact between a touch screen 112 and the user corresponds to a finger of the user.
The touch screen 112 may use LCD (liquid crystal display) technology, or LPD (light emitting polymer display) technology, although other display technologies may be used in other embodiments. The touch screen 112 and the display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with a touch screen 112.
A touch-sensitive display in some embodiments of the touch screen 112 may be analogous to the multi-touch sensitive tablets described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, a touch screen 112 displays visual output from the portable device 100, whereas touch sensitive tablets do not provide visual output.
A touch-sensitive display in some embodiments of the touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
The touch screen 112 may have a resolution in excess of 100 dpi. In an exemplary embodiment, the touch screen has a resolution of approximately 160 dpi. The user may make contact with the touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which are much less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, the device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
In some embodiments, the device 100 may include a physical or virtual click wheel as an input control device 116. A user may navigate among and interact with one or more graphical objects (henceforth referred to as icons) displayed in the touch screen 112 by rotating the click wheel or by moving a point of contact with the click wheel (e.g., where the amount of movement of the point of contact is measured by its angular displacement with respect to a center point of the click wheel). The click wheel may also be used to select one or more of the displayed icons. For example, the user may press down on at least a portion of the click wheel or an associated button. User commands and navigation commands provided by the user via the click wheel may be processed by an input controller 160 as well as one or more of the modules and/or sets of instructions in memory 102. For a virtual click wheel, the click wheel and click wheel controller may be part of the touch screen 112 and the display controller 156, respectively. For a virtual click wheel, the click wheel may be either an opaque or semitransparent object that appears and disappears on the touch screen display in response to user interaction with the device. In some embodiments, a virtual click wheel is displayed on the touch screen of a portable multifunction device and operated by user contact with the touch screen.
The device 100 also includes a power system 162 for powering the various components. The power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
The device 100 may also include one or more optical sensors 164. FIGS. 1A and 1B show an optical sensor coupled to an optical sensor controller 158 in I/O subsystem 106. The optical sensor 164 may include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. The optical sensor 164 receives light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with an imaging module 143 (also called a camera module), the optical sensor 164 may capture still images or video. In some embodiments, an optical sensor is located on the back of the device 100, opposite the touch screen display 112 on the front of the device, so that the touch screen display may be used as a viewfinder for either still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user's image may be obtained for videoconferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 may be used along with the touch screen display for both video conferencing and still and/or video image acquisition.
The device 100 may also include one or more proximity sensors 166. FIGS. 1A and 1B show a proximity sensor 166 coupled to the peripherals interface 118. Alternately, the proximity sensor 166 may be coupled to an input controller 160 in the I/O subsystem 106. The proximity sensor 166 may perform as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call). In some embodiments, the proximity sensor keeps the screen off when the device is in the user's pocket, purse, or other dark area to prevent unnecessary battery drainage when the device is a locked state.
The device 100 may also include one or more accelerometers 168. FIGS. 1A and 1B show an accelerometer 168 coupled to the peripherals interface 118. Alternately, the accelerometer 168 may be coupled to an input controller 160 in the I/O subsystem 106. The accelerometer 168 may perform as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers.
In some embodiments, the software components stored in memory 102 may include an operating system 126, a communication module (or set of instructions) 128, a contact/motion module (or set of instructions) 130, a graphics module (or set of instructions) 132, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and applications (or set of instructions) 136.
The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
The communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by the RF circuitry 108 and/or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used on iPod (trademark of Apple Computer, Inc.) devices.
The contact/motion module 130 may detect contact with the touch screen 112 (in conjunction with the display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred, determining if there is movement of the contact and tracking the movement across the touch screen 112, and determining if the contact has been broken (i.e., if the contact has ceased). Determining movement of the point of contact may include determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations may be applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, the contact/motion module 130 and the display controller 156 also detects contact on a touchpad. In some embodiments, the contact/motion module 130 and the controller 160 detects contact on a click wheel.
The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112, including components for changing the intensity of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
The text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, blogging 142, browser 147, and any other application that needs text input).
Examples of other applications 136 that may be stored in memory 102 include other word processing applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the contacts module 137 may be used to manage an address book or contact list, including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in the address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, the videoconferencing module 139 may be used to initiate, conduct, and terminate a video conference between a user and one or more other participants.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the e-mail client module 140 may be used to create, send, receive, and manage e-mail. In conjunction with image management module 144, the e-mail module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 may be used to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, image management module 144, and browsing module 147, the blogging module 142 may be used to send text, still images, video, and/or other graphics to a blog (e.g., the user's blog).
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, the camera module 143 may be used to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 may be used to arrange, modify or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, and speaker 111, the video player module 145 may be used to display, present or otherwise play back videos (e.g., on the touch screen or on an external, connected display via external port 124).
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, the music player module 146 allows the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files. In some embodiments, the device 100 may include the functionality of an MP3 player, such as an iPod (trademark of Apple Computer, Inc.).
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the browser module 147 may be used to browse the Internet, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail module 140, and browser module 147, the calendar module 148 may be used to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.).
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the search module 151 may be used to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms).
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the notes module 153 may be used to create and manage notes, to do lists, and the like.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, the map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data).
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, c-mail client module 140, and browser module 147, the online video module 155 allows the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the content of which is hereby incorporated by reference in its entirety.
Each of the above identified modules and applications correspond to a set of instructions for performing one or more functions described above. These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. For example, video player module 145 may be combined with music player module 146 into a single module (e.g., video and music player module 152, FIG. 1B). In some embodiments, memory 102 may store a subset of the modules and data structures identified above. Furthermore, memory 102 may store additional modules and data structures not described above.
In some embodiments, the device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen 112 and/or a touchpad. By using a touch screen and/or a touchpad as the primary input/control device for operation of the device 100, the number of physical input/control devices (such as push buttons, dials, and the like) on the device 100 may be reduced.
The predefined set of functions that may be performed exclusively through a touch screen and/or a touchpad include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main, home, or root menu from any user interface that may be displayed on the device 100. In such embodiments, the touchpad may be referred to as a “menu button.” In some other embodiments, the menu button may be a physical push button or other physical input/control device instead of a touchpad.
FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen may display one or more graphics within user interface (UI) 200. In this embodiment, as well as others, a user may select one or more of the graphics by making contact or touching the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the contact may include a gesture, such as one or more taps, one or more swipes (from left to right, right to left, upward and/or downward) and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with the device 100. In some embodiments, inadvertent contact with a graphic may not select the graphic. For example, a swipe gesture that sweeps over an application icon may not select the corresponding application when the gesture corresponding to selection is a tap.
The device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, the menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI in touch screen 112.
In one embodiment, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, a Subscriber Identity Module (SIM) card slot 210, a head set jack 212, and a docking/charging external port 124. The push button 206 may be used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, the device 100 also may accept verbal input for activation or deactivation of some functions through the microphone 113.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on a portable multifunction device 100.
In some embodiments, in addition to or in place of wallpaper image 314, an unlock user interface may include a device charging status icon 316 and a headset charging status icon 318 (e.g., UI 300B, FIG. 3B). The device charging status icon 316 indicates the battery status while the device 100 is being recharged (e.g., in a dock). Similarly, headset charging status icon 318 indicates the battery status of a headset associated with device 100 (e.g., a Bluetooth headset) while the headset is being recharged (e.g., in another portion of the dock).
In some embodiments, the device detects contact with the touch-sensitive display (e.g., a user's finger making contact on or near the unlock image 302) while the device is in a user-interface lock state. The device moves the unlock image 302 in accordance with the contact. The device transitions to a user-interface unlock state if the detected contact corresponds to a predefined gesture, such as moving the unlock image across channel 306. Conversely, the device maintains the user-interface lock state if the detected contact does not correspond to the predefined gesture. This process saves battery power by ensuring that the device is not accidentally awakened. This process is easy for users to perform, in part because of the visual cue(s) provided on the touch screen.
In some embodiments, after detecting an unlock gesture, the device displays a passcode (or password) interface (e.g., UI 300C, FIG. 3C) for entering a passcode to complete the unlock process. The addition of a passcode protects against unauthorized use of the device. In some embodiments, the passcode interface includes an emergency call icon that permits an emergency call (e.g., to 911) without entering the passcode. In some embodiments, the use of a passcode is a user-selectable option (e.g., part of settings 412).
As noted above, processes that use gestures on the touch screen to unlock the device are described in U.S. patent application Ser. No. 11/322,549, “Unlocking A Device By Performing Gestures On An Unlock Image,” filed Dec. 23, 2005, and Ser. No. 11/322,550, “Indication Of Progress Towards Satisfaction Of A User Input Condition,” filed Dec. 23, 2005, which are hereby incorporated by reference in their entirety.
Online video module 155, also referred to as YouTube (trademark of Google, Inc.) module 155.
In some embodiments, UI 400A or 400B displays all of the available applications 136 on one screen so that there is no need to scroll through a list of applications (e.g., via a scroll bar). In some embodiments, as the number of applications increase, the icons corresponding to the applications may decrease in size so that all applications may be displayed on a single screen without scrolling. In some embodiments, having all applications on one screen and a menu button enables a user to access any desired application with at most two inputs, such as activating the menu button 204 and then activating the desired application (e.g., by a tap or other finger gesture on the icon corresponding to the application). In some embodiments, a predefined gesture on the menu button 204 (e.g., a double tap or a double click) acts as a short cut that initiates display of a particular user interface in a particular application. In some embodiments, the short cut is a user-selectable option (e.g., part of settings 412). For example, if the user makes frequent calls to persons listed in a Favorites UI (e.g., UI 2700A, FIG. 27A) in the phone 138, the user may choose to have the Favorites UI be displayed in response to a double click on the menu button. As another example, the user may choose to have a UI with information about the currently playing music (e.g., UI 4300S, FIG. 43S) be displayed in response to a double click on the menu button.
In some embodiments, UI 400A or 400B provides integrated access to both widget-based applications and non-widget-based applications. In some embodiments, all of the widgets, whether user-created or not, are displayed in UI 400A or 400B. In other embodiments, activating the icon for user-created widget 149-6 may lead to another UI that contains the user-created widgets or icons corresponding to the user-created widgets.
In some embodiments, a user may rearrange the icons in UI 400A or 400B, e.g., using processes described in U.S. patent application Ser. No. 11/459,602, “Portable Electronic Device With Interface Reconfiguration Mode,” filed Jul. 24, 2006, which is hereby incorporated by reference in its entirety. For example, a user may move application icons in and out of tray 408 using finger gestures.
In some embodiments, UI 400A or 400B includes a gauge (not shown) that displays an updated account usage metric for an account associated with usage of the device (e.g., a cellular phone account), as described in U.S. patent application Ser. No. 11/322,552, “Account Information Display For Portable Communication Device,” filed Dec. 23, 2005, which is hereby incorporated by reference in its entirety.
In some embodiments, a signal strength indicator 402 (FIG. 4B) for a WiFi network is replaced by a symbol for a cellular network (e.g., the letter “E” for an EDGE network, FIG. 4A) when the device switches from using the WiFi network to using the cellular network for data transmission (e.g., because the WiFi signal is weak or unavailable).
FIGS. 5A-5H illustrate exemplary user interfaces for inserting a character from an alternate keyboard on a touch screen in accordance with some embodiments. FIG. 5A, for example, includes a UI 500A for creating and sending an email message (e.g., “Barbeque on Saturday” shown in UIs 500A-H, FIGS. 5A-5H).
Attach icon 510 that when activated (e.g., by a finger tap on the icon), displays a UI for adding attachments (not shown).
Alternate keyboard selector key 556 that when activated (e.g., by a finger contact or tap on the icon) initiates the display of a different keyboard (e.g., letter keyboard 516, FIG. 5A).
In some embodiments, a first keyboard (e.g., letter keyboard 516) is displayed that contains a plurality of character-insertion keys (e.g., letter keys A-Z and the space bar on the letter keyboard 516). In some embodiments, while displaying the letter keyboard 516, a contact 560-1 is detected on the alternate keyboard selector key 552 (UI 500B, FIG. 5B). In response to detecting the contact 560-1 (FIG. 5B) on the alternate keyboard selector key 552, a second soft keyboard (e.g. number/symbol keyboard 518) is displayed (UI 500C, FIG. 5C).
In some embodiments, the second soft keyboard contains a plurality of number and/or symbol insertion keys (e.g., number keys 0-9, space bar and symbol keys on the number/symbol keyboard 518) and includes another alternate keyboard selector key 556. In some embodiments, the character-insertion keys in the number/symbol keyboard 518 (FIG. 5C) and the other keyboards are visually distinguished from keys that do not insert characters. For example, character-insertion keys for letters, numbers, punctuation marks, a space, or other symbols may have a different shading or color than keys in the second keyboard that do not insert characters such as a deletion key, a return key, a shift key, or a key for selecting another soft keyboard. In user interfaces 500A-500H (FIGS. 5A-5H), the keys that do not insert characters are shaded slightly darker than the keys used to insert characters.
In some embodiments, the contact 560 is a finger contact. In some embodiments, the contact 560 is a stylus contact.
In some embodiments, displaying the number/symbol keyboard 518 (FIG. 5C) in response to detecting the contact 560 (FIG. 5B) on the alternate keyboard selector key 552 (FIG. 5B) includes ceasing to display the letter keyboard 516 (first displayed in FIG. 5A).
In some embodiments, in response to detecting a contact (e.g., contact 560-2, FIG. 5D) over a character-insertion key (e.g., “?” key 564, FIG. 5D), an image with an enlarged version of the character in the character-insertion key is displayed (e.g., image 563 with an enlarged version of the “?” character in key 564, FIG. 5E) to indicate that the corresponding character-insertion key (e.g., 564) will be selected if the contact 560 lifts off at its current position. In some embodiments, in response to detecting a contact (e.g., contact 560-2, FIG. 5D) over a character-insertion key (e.g., “?” key 564, FIG. 5D), an enlarged version of the character-insertion key is displayed to indicate that the character-insertion key will be selected if the contact 560 lifts off at its current position. In some embodiments, if lift off of the contact 560-2 is detected at a character-insertion key, the corresponding character 574 is inserted at the insertion marker 538 (FIG. 5F) and the number/symbol keyboard 518 ceases to be displayed (UI 500F, FIG. 5F). In some embodiments, the letter keyboard 516 (the first keyboard to be displayed) is redisplayed (UI 500F, FIG. 5F) when the number/symbol keyboard 518 ceases to be displayed.
In some embodiments, if the contact 560-1 (FIG. 5G) is moved (e.g., movements 571 and 575) to keys that do not insert characters (e.g., keys that are shaded on keyboard 518 in UI 500G, FIG. 5G), and lift off is detected over such keys (e.g., contacts 560-4, 560-5, FIG. 5G), then the display of the alternate keyboard (e.g., number/symbol keyboard 518 in UI 500H, FIG. 5H) is maintained. In some embodiments, the display of the alternate keyboard (e.g., number/symbol keyboard 518 in UI 500H, FIG. 5H) is maintained if lift off is detected in regions of the touch screen display other than keys for inserting characters. For example, if the contact 560 is moved as shown by movement 565 from 560-1 to 560-3 and lift off is detected at 560-3, the number/symbol keyboard is maintained (UI 500H, FIG. 5H).
The user interfaces in FIGS. 5A-5H are used to illustrate the process described below with respect to FIGS. 6A-6C.
FIG. 6A is flow diagram illustrating a method 6000 of inserting a character from an alternate keyboard on a touch screen display in accordance with some embodiments. The method 6000 is performed at a device with a touch screen display. In some embodiments, the method 6000 is performed at a portable multifunction device with a touch screen display (e.g., portable multifunction device 100). As described below, the method 6000 provides an efficient way for a user to insert a character from an alternate keyboard.
The device displays (6020) a first soft keyboard. The first soft keyboard contains a plurality of character-insertion keys (e.g., keyboard 516 with keys A-Z and space bar, FIG. 5A).
While displaying the first soft keyboard, the device displays (6040) a key for selecting a second soft keyboard different from the first soft keyboard (e.g., key 552, FIG. 5A). The second soft keyboard contains a plurality of character-insertion keys (e.g., keyboard 518 with number keys, space bar, and symbol keys, FIG. 5C).
The device detects (6060) a first contact 560 on the key for selecting the second soft keyboard (e.g., contact 560-1 on key 552, FIG. 5B).
In some embodiments, the first contact 560 is a finger contact (6080). In some embodiments, the first contact 560 is a stylus contact (6100).
In response to detecting the first contact 560 on the key for selecting the second soft keyboard, the device displays (6120) the second soft keyboard (e.g., keyboard 518, FIG. 5C).
In some embodiments, the character-insertion keys in the second keyboard are (6140) visually distinguished from keys in the second keyboard that do not insert characters. For example, character-insertion keys for letters, numbers, punctuation marks, a space, or other symbols may have a different shading or color than keys in the second keyboard that do not insert characters such as a deletion key, a return key, a shift key, or a key for selecting another soft keyboard. In user interfaces 500A-500H (FIGS. 5A-5H), the keys that do not insert characters are shaded slightly darker than the keys used to insert characters.
In some embodiments, displaying the second soft keyboard in response to detecting the first contact 560 on the key for selecting the second soft keyboard includes (6160) ceasing to display the first soft keyboard. For example, in response to detecting contact 560-1 on key 552 (FIG. 5B), the device displays keyboard 518 and ceases to display keyboard 516 (FIG. 5C). Conversely, in some embodiments, all or part of the first keyboard is still displayed (e.g., on devices with large touch screens, not shown).
The device detects (6180) the first contact 560 moving on the touch screen display to a character-insertion key in the second soft keyboard. For example, the device detects contact 560 (FIG. 5D) moving 562 from key 556 to character-insertion key 564 (FIG. 5D), a “?” key.
The device detects (6200) lift off of the first contact 560 from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved. For example, the device detects lift off of the first contact 560 at the “?” key 564 (FIG. 5D or 5E).
First contact 560 is a continuous contact with the touch screen display. In other words, the first contact 560 maintains contact with the touch screen display from the time the first contact (e.g., 560-1) is detected on the key for selecting the second soft keyboard until the time that lift off of the first contact (e.g., 560-2) from the touch screen display is detected at the character-insertion key in the second soft keyboard to which the first contact moved.
In response to detecting lift off of the first contact 560 from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved, the device inserts (6220) a character that corresponds to the character-insertion key in the second soft keyboard to which the first contact moved (e.g., the device inserts the “?” character 574, FIG. 5F) and ceases to display the second soft keyboard (e.g., keyboard 518 is no longer displayed in FIG. 5F). For example, a character such as a letter, number, punctuation mark, a space, or other symbol may be inserted in a text input area (e.g., message box 512) on the touch screen display.
In some embodiments, ceasing to display the second soft keyboard 518 in response to detecting lift off of the first contact from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved may also include the device redisplaying (6240) the first soft keyboard (e.g., 516, FIG. 5F).
In some embodiments, the display of the second keyboard 518 is maintained (6260) if lift off of the first contact 560 is detected at a location on the touch screen display other than the location of a character-insertion key in the second keyboard (e.g., as described above with respect to FIGS. 5G and 5H). For example, display of the second keyboard 518 is maintained if lift off is detected at a text input area, at a deletion key, at a return key, at a shift key, or at a key for selecting another soft keyboard.
A graphical user interface on a portable electronic device with a touch screen display includes: a first soft keyboard containing a plurality of character-insertion keys (e.g., keyboard 516, FIG. 5A); a key for selecting a second soft keyboard different from the first soft keyboard (e.g., key 552, FIG. 5A); and the second soft keyboard (e.g., keyboard 518, FIG. 5C), the second soft keyboard containing a plurality of character-insertion keys. The key 552 for selecting the second soft keyboard is displayed while displaying the first soft keyboard 516. In response to detecting a first contact on the key for selecting the second soft keyboard (e.g., contact 560-1, FIG. 5B), the second soft keyboard 518 is displayed (e.g., UI 500C, FIG. 5C). The first contact 560 is detected moving on the touch screen display (e.g., from 560-1 to 560-2, FIG. 5D) to a character-insertion key in the second soft keyboard (e.g., key 564, FIGS. 5D-5E). Lift off of the first contact (e.g., contact 560-2, FIG. 5D) from the touch screen display is detected at the character-insertion key in the second soft keyboard to which the first contact moved. In response to detecting lift off of the first contact from the touch screen display at the character-insertion key in the second soft keyboard to which the first contact moved, a character (e.g., character 574, FIG. 5F) is inserted that corresponds to the character-insertion key (e.g., key 564, FIG. 5E) in the second soft keyboard to which the first contact moved, and display of the second soft keyboard is ceased (e.g., UI 500F, FIG. 5F).
ceasing to display the second plurality of character insertion keys.
wherein each of the keys in the second plurality of character insertion keys are displayed at a location apart from the single contact.
3. The method of claim 1, wherein the single contact is a finger contact.
4. The method of claim 1, wherein the single contact is a stylus contact.
5. The method of claim 1, wherein displaying the second plurality of character insertion keys at least partially occludes the soft keyboard.
6. The method of claim 1, wherein displaying the second plurality of character insertion keys does not occlude the key of the soft keyboard.
7. The method of claim 1, wherein continuing to display the key of the soft keyboard comprises displaying the key of the soft keyboard in a manner that is visually distinguished from the second plurality of character insertion keys.
9. The portable electronic device of claim 8, wherein each of the keys in the second plurality of character insertion keys are displayed at a location apart from the single contact.
10. The portable electronic device of claim 8, wherein the single contact is a finger contact.
11. The portable electronic device of claim 8, wherein the single contact is a stylus contact.
12. The portable electronic device of claim 8, wherein displaying the second plurality of character insertion keys at least partially occludes the soft keyboard.
13. The portable electronic device of claim 8, wherein displaying the second plurality of character insertion keys does not occlude the key of the soft keyboard.
14. The portable electronic device of claim 8, wherein continuing to display the key of the soft keyboard comprises displaying the key of the soft keyboard in a manner that is visually distinguished from the second plurality of character insertion keys.
cease to display the second plurality of character insertion keys.
16. The non-transitory computer readable storage medium of claim 15, wherein each of the keys in the second plurality of character insertion keys are displayed at a location apart from the single contact.
17. The non-transitory computer readable storage medium of claim 15, wherein the single contact is a finger contact.
18. The non-transitory computer readable storage medium of claim 15, wherein the single contact is a stylus contact.
19. The non-transitory computer readable storage medium of claim 15, wherein displaying the second plurality of character insertion keys at least partially occludes the soft keyboard.
20. The non-transitory computer readable storage medium of claim 15, wherein displaying the second plurality of character insertion keys does not occlude the key of the soft keyboard.
21. The non-transitory computer readable storage medium of claim 15, wherein continuing to display the key of the soft keyboard comprises displaying the key of the soft keyboard in a manner that is visually distinguished from the second plurality of character insertion keys.
"Centroid", Online Available at <http://faculty.evansville.edu/ck6/tcenters/class/centroid.html>, Apr. 28, 2006, 1 page.
"Centroid", Online available at <http://www.pballew.net/centroid.html>, Apr. 28, 2006, 3 pages.
"Compare Keyboards with the Keyboard Compatibility Chart, Learn more About Alternative Keyboards", Solutions for Humans, Online Available at <http://www.keyalt.com/kkeybrdp.htm>, Dec. 8, 2005, 5 pages.
"Devices", Technology Loan Catalog, Online Available at <http://www.tsbvi.edu/outreach/techioan/catalog.html>, retrieved on Dec. 8, 2005, 10 pages.
"Fastap Keypads Redefine Mobile Phones", DigitWireless, Online Available at <http://www.digitwireless.com/about/how it works.html>, retrieved on Nov. 18, 2005, 10 pages.
"Fastap", DigitWireless, Online Available at <http://www.digitwireless.com/about/faq.html>, Dec. 6, 2005, 5 pages.
"Four-Button Keyboard", WikiPodlinux, available at <http://ipodlinux.org/Four_Button_Keyboard>, retrieved on Dec. 5, 2005, 2 pages.
"LG Develops New Touch Pad Cell Phones", Textually, available at <http://textually.ora/textually/archives/2005/06/009903.html>, retrieved on Nov. 18, 2005, 1 page.
"P900 User Guide", Sony Ericsson Mobile Communications AB, Online Available at <http://www.sonyericcson.com/downloads/P900_UG_R1b_EN.pdf>, Sep. 2003, 98 pages.
"Samsung Releases Keyboard Phone in US", Textually, Online available at <http://www.textually.ora/textually/archives/2005/11 /01 0482. htm>, retrieved on Nov. 18, 2005, 1 page.
"T9® Text Input for Keypad Devices", Online Available at <http://tegic.com>, 1 page.
"Text Input (legacy)", WikiPodlinux, Online Available at <http://ipodlinux.org/Text Input_%28legacy%29>, retrieved on Dec. 5, 2005, 8 pages.
"Text Input Concepts", WikiPodlinux, Online Available at <http:I/web.archive.ora/web/20051211165254/http:I/ipodlinux.ora/Text_Input_Co ncepts>, Dec. 2005, 3 pages.
"Text Input Methods", WikiPodlinux, Online Available at <http://ipodlinux.org/Text_Input_Methods>, retrieved on Dec. 5, 2005, 5 pages.
"You Heard of Touch Screens Now Check Out Touch Keys", Phoneyworld, Online Available at <http://www.phonevworld.com>, retrieved on Nov. 18, 2005, 2 pages.
Casario, M., "Hands on Macromedia World: Touch Screen Keypad for Mobile Phone by DoCoMo", Online Available at <http://casario.bloqs.com/mmworld/2005/10/touch_screen_ke. html>, retrieved on Nov. 18, 2005, 1 page.
Day, B., "Will Cell Phones Render iPods Obsolete?", Online Available at <http://weblogs.iavanet/pub/wig/883>, Dec. 12, 2005, 3 pages.
Final Office Action received for U.S. Appl. No. 11/228,700, dated May 12, 2009, 14 pages.
Final Office Action received for U.S. Appl. No. 11/459,615, dated Dec. 8, 2009, 12 pages.
Final Office Action received for U.S. Appl. No. 11/696,701, dated Jul. 27, 2012, 14 pages.
Final Office Action received for U.S. Appl. No. 11/696,701, dated Nov. 26, 2010, 13 pages.
Final Office Action received for U.S. Appl. No. 12/163,886, dated Apr. 24, 2013, 14 pages.
Final Office Action received for U.S. Appl. No. 12/163,886, dated Nov. 7, 2011, 13 pages.
Final Office Action Received for U.S. Appl. No. 12/790,479, dated Dec. 4, 2013, 24 pages.
Final Office Action Received for U.S. Appl. No. 12/790,479, dated Mar. 4, 2013, 26 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2010/062318, dated Jul. 19, 2012, 12 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/060119, dated Apr. 11, 2008, 18 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/088904, dated Sep. 15, 2008, 16 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2010/062318, dated Mar. 23, 2011, 14 pages.
Introducing the Ultimate Smartphone Keypad, Delta II™ Keypads, Online Available at <http://www.chicagologic.com>, retrieved on Nov. 18, 2005, 2 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2007/060119, dated Jan. 2, 2008, 9 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2007/088904, dated Jun. 23, 2008, 8 pages.
Microsoft New-Smart Phone Interface: Your Thumb, Textually, available at <htto://www.textuallv.org>, retrieved on Nov. 18, 2005, 2 pages.
Non-Final Office Action received for U.S. Appl. No. 11/228,700, dated Sep. 17, 2008, 19 pages.
Non-Final Office Action received for U.S. Appl. No. 11/459,606, dated May 28, 2009, 19 pages.
Non-Final Office Action received for U.S. Appl. No. 11/459,615, dated Apr. 13, 2010, 10 pages.
Non-Final Office Action received for U.S. Appl. No. 11/459,615, dated May 22, 2009, 10 pages.
Non-Final Office Action received for U.S. Appl. No. 11/696,701, dated Dec. 22, 2011, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 11/696,701, dated Jun. 10, 2010, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 11/961,663, dated Nov. 18, 2010, 22 pages.
Non-Final Office Action received for U.S. Appl. No. 12/163,886, dated Apr. 13, 2011, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 12/163,886, dated Jun. 21, 2012, 13 pages.
Non-Final Office Action Received for U.S. Appl. No. 12/790,479, dated Jul. 12, 2013, 23 pages.
Non-Final Office Action Received for U.S. Appl. No. 12/790,479, dated Sep. 4, 2012, 30 pages.
Non-Final Office Action received for U.S. Appl. No. 14/042,472, dated Sep. 4, 2014, 14 pages.
Notice of Acceptance received for Australian Patent Application No. 2006295354, dated Oct. 8, 2010, 2 pages.
Notice of Allowance Received for Chinese Patent Application No. 201080063760.7, dated Jul. 6, 2016, 4 pages (2 pages of English Translation and 2 pages of Official copy).
Notice of Allowance received for Korean Patent Application No. 10-2010-7022243, dated Sep. 28, 2011, 2 pages (Official Copy Only).
Notice of Allowance received for U.S. Appl. No. 12/163,886, dated Sep. 5, 2013, 6 pages.
Notice of Allowance received for U.S. Appl. No. 12/790,479, dated Mar. 28, 2014, 9 pages.
Notice of Allowance received for U.S. Appl. No. 14/042,472, dated Jul. 13, 2015, 10 pages.
Notice of Allowance received for U.S. Appl. No. 14/042,472, dated Nov. 23, 2015, 10 pages.
Office Action received for Australian Patent Application No. 2006295354, dated Jul. 24, 2009, 2 pages.
Office Action received for Chinese Patent Application No. 200680033890.X, dated Jan. 29, 2010, 3 pages (English translation Only).
Office Action received for Chinese Patent Application No. 200780006621.9, dated Aug. 16, 2010, 4 pages. (English Translation only).
Office Action received for Chinese Patent Application No. 201080063760.7, dated Jun. 10, 2015, 8 pages. (Official Copy Only).
Office Action Received for Chinese Patent Application No. 201080063760.7, dated Oct. 30, 2015, 16 pages (10 pages of English Translation and 6 pages of Official Copy).
Office Action received for Chinese Patent Application No. 201080063760.7, dated Sep. 3, 2014, 7 pages (Official Copy Only).
Office Action received for European Patent Application dated Aug. 10, 2017, 13 pages.
Office Action received for European Patent Application No. 06801347.3, dated Dec. 15, 2011, 5 pages.
Office Action received for European Patent Application No. 06801347.3, dated May 22, 2012, 5 pages.
Office Action received for European Patent Application No. 07709955.4, dated Jul. 31, 2009, 6 pages.
Office Action received for European Patent Application No. 07709955.4, dated Oct. 10, 2008, 5 pages.
Office Action received for Japanese Patent Application No. 2008-531107, dated Feb. 28, 2011, 5 pages (English Translation Only).
Office Action received for Japanese Patent Application No. 2008-531107, dated Nov. 4, 2011, 4 pages (English translation only).
Office Action received for Korean Patent Application No. 10-2008-7006262, dated Aug. 25, 2010, 6 pages (3 pages of English Translation and 3 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2008-7006262, dated Jan. 11, 2010, 11 pages (7 pages of English Translation and 4 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2008-7019114, dated Aug. 31, 2010, 4 pages (1 page of English Translation and 3 pages of Official copy).
Office Action received for Korean Patent Application No. 10-2010-7022243, dated Dec. 11, 2010, 3 pages (English Translation Only).
O'Neal, "Smart Phones with Hidden Keyboards", available at <http://msc.com/4250-6452_16-6229969-1.html>, Nov. 18, 2005, 3 pages.
Sears et al., "Data Entry for Mobile Devices Using Soft Keyboards: Understanding the Effects of Keyboard Size and User Tasks", Abstract, Int'l Journal of Human-Computer Interaction, vol. 16, No. 2, 2003, pp. 163-184.

matches:
Application No. 60
Application No. 2006295354
Application No. 201080063760
Application No. 10
Application No. 2006295354
Application No. 200680033890
Application No. 200780006621
Application No. 201080063760
Application No. 201080063760
Application No. 201080063760
Application No. 06801347
Application No. 06801347
Application No. 07709955
Application No. 07709955
Application No. 2008
Application No. 2008
Application No. 10
Application No. 10
Application No. 10
Application No. 10


This matter comes before the Court on defendants' motion to remand plaintiff's naturalization application to United States Citizenship and Immigration Services ("USCIS"), and on plaintiff's motion for a naturalization hearing. For the reasons set forth below, the Court grants defendants' motion and denies plaintiff's motion.
On January 27, 2004, plaintiff filed his N-400 application for naturalization with USCIS (the "application"). USCIS interviewed Mr. Ahmed on December 6, 2004, but then failed to adjudicate his application in a timely fashion. On September 9, 2008, plaintiff filed his petition for a naturalization hearing with this Court pursuant to 8 U.S.C. § 1447(b). The Court ordered defendants to show cause why plaintiff should not be naturalized and, if appropriate, provide a proposed plan for the prompt administrative adjudication of his application (Dkt. #4). The Court granted the parties a continuance to allow USCIS to interview plaintiff on December 8, 2008 (Dkt. #6). Subsequently, defendants responded to the Court's order to show cause and moved to remand on January 23, 2009. Plaintiff filed a cross-motion for a naturalization hearing on January 29, 2009.
If there is a failure to make a determination under [ 8 U.S.C. § 1446] before the end of the 120-period after the date on which the examination is conducted under such section, the applicant may apply to the United States district court for the district in which the applicant resides for a hearing on the matter. Such court has jurisdiction over the matter and may either determine the matter or remand the matter, with appropriate instructions, to the Service to determine the matter.
8 U.S.C. § 1447(b) (2006). USCIS first interviewed Mr. Ahmed on December 6, 2004. Plaintiff still awaits a decision on his application over four years later. Accordingly, this Court has jurisdiction over plaintiff's complaint. See Hovsepian v. United States, 359 F.3d 1144, 1164 (9th Cir. 2004). The Court may either review the application de novo or remand the matter to USCIS.
Defendants argue that USCIS is still evaluating plaintiff's eligibility for naturalization, and urge the Court to remand. Specifically, defendants cite information from the Federal Bureau of Investigation ("FBI") which suggests that plaintiff may be a national security risk. See Dkt. #8 (Brouillard Decl.), Ex. 1. Defendants do not disclose when the agency first learned of the FBI's concerns, but nevertheless claim that USCIS cannot adjudicate Mr. Ahmed's petition without further investigation.
The Court will grant plaintiff Ahmed's unopposed motion (Dkt. #13) to seal the FBI memorandum. The Clerk of Court is hereby directed to seal Dkt. # 8-2 in the above-captioned matter.
Plaintiff adamantly rejects his characterization as a possible security risk, and urges the Court to conduct a naturalization hearing. Plaintiff argues that remand would be futile because USCIS has already decided to deny his application. Yet the record does not support that conclusion; defendants request more time to make a determination. Plaintiff cites a number of cases in which courts have granted an evidentiary hearing, including some from this district. For example, in Ghanim v. Gonzales, No. 07-594MJP, 2007 U.S. Dist. LEXIS 57182 (W.D. Wash. Aug. 6, 2007), the court granted a hearing over defendant's objection that the petitioner's "name check" was not complete. The government claimed that a backlog within the agency prevented USCIS from timely adjudicating the application. This is distinguishable from the facts in the present case. Here, defendants do not claim procedural delays. Rather, defendants assert that a background check raised national security concerns that warrant further investigation.
This Court sympathizes with Mr. Ahmed's understandable frustration over the prolonged delay. However, he may not obtain a more favorable or expeditious result from this Court, which would have to conduct a de novo hearing following discovery by the parties. Based on the documents defendants submitted, the agency may have a legitimate reason for delaying adjudication. Most importantly, the agency is in the best position to render a decision on plaintiff's application because it is the designated agency responsible for determining the issuance of immigration benefits. This Court is not equipped to conduct the kind of investigation required to determine whether an applicant presents a risk to national security or public safety. See Aslam v. Gonzales, No. 06-614MJP, 2006 U.S. Dist. LEXIS 91747, at *6 (W.D. Wash. Dec. 19, 2006) (citing El-Daour v. Chertoff, 417 F. Supp. 2d 679, 684 (W.D. Pa. 2005)). Still, this Court recognizes that plaintiff remains in a state of limbo until USCIS reaches a decision. Plaintiff can request a hearing before an immigration officer only after USCIS decides his claim. 8 U.S.C. § 1421(c), (d); 8 U.S.C. § 1447(a); 8 C.F.R. § 336.2. While defendants urge the Court to remand without time restrictions, a court-imposed time frame is appropriate given the previous delay. Defendants have not offered any information regarding how long the investigation might take, raising concerns that it could drag on indefinitely without an established time frame. Accordingly, this Court remands the matter back to the USCIS with instructions to complete adjudication within ninety days. This time frame considers both defendants' interest in public safety and national security, and plaintiff Ahmed's individual interest in having his naturalization application adjudicated in a timely manner. If USCIS is unable to adjudicate his application within ninety days, defendants may move the Court to reopen the case and request additional time.
For all of the foregoing reasons, the Court GRANTS plaintiff's motion (Dkt. #13) to seal Dkt. #8-2, GRANTS defendants' motion to remand and dismiss (Dkt. #7), DENIES plaintiff's motion for a naturalization hearing (Dkt. #9), REMANDS this case to USCIS for adjudication of plaintiff's naturalization application within ninety days, and DISMISSES this action without prejudice.


§ 1-3 Execution against property.
§ 1-4 Rules of construction.
§ 1-7 Adoption of ordinance.
§ 1-8 Enactment of Code of Ordinances.
First offense. Any person who shall violate any provision of this Code subject to a penalty shall, upon conviction thereof, forfeit not less than $5 nor more than $500, together with the cost of prosecution and a penalty assessment as provided under Wisconsin law, plus all court costs, including fees prescribed under Wisconsin law, and, in default of payment of such forfeiture and costs of prosecution, may be imprisoned in the county jail until such forfeiture and costs are paid, but not to exceed 90 days.
Second and further offenses. Any person found guilty of violating any ordinance or part of an ordinance of the Town Code who shall previously have been convicted of a violation of the same ordinance within one year shall, upon conviction thereof, forfeit not less than $10 nor more than $1,500 for each such offense, together with the costs of prosecution and any penalty assessment as provided under Wisconsin law, plus court costs and fees, and, in default of payment of such forfeiture and costs, may be imprisoned in the county jail until such forfeiture and costs of prosecution are paid, but not to exceed 90 days.
Each violation and each day a violation continues or occurs shall constitute a separate offense. Nothing in this Code shall preclude the Town of Barton from maintaining an appropriate action to prevent, enjoin or remove a violation of any provision of this Code.
Whenever any person or entity fails to pay any forfeiture and costs of prosecution upon the order of a court or forfeiture for violation of any ordinance of the Town, the court may, in lieu of ordering imprisonment of the defendant(s), or after the defendant(s) has been released from custody, issue an execution against the property of the defendant(s) for such forfeiture and costs.
Shall and may. "Shall" is mandatory; "may" is permissive.
Tense. The present tense includes the past and future tenses, and the future includes the present.
The purpose of this ordinance is to enact the codification for the Code of the Town of Barton that has been prepared and authorized by the Town Board for the Town of Barton.
The Town Board of the Town of Barton, Washington County, Wisconsin, has the specific authority under § 66.0103, Wis. Stats. to prepare and enact a Code of General Ordinances by enacting an ordinance that incorporates the Code by reference.
This ordinance, adopted by a majority of the Town Board on a roll call vote with a quorum present and voting and proper notice having been given. provides the authority for the Town to enact the Code of the "Town of Barton by enacting an ordinance that incorporates the Code by reference.
The Code of the Town of Barton in book form which is entitled "Code of the Town of Barton," having been placed on file and open to the public for inspection in the office of the Town Clerk for a period of two weeks commencing October 5. 2015, pursuant to § 66.0103, Wis. Stats., is adopted as the General Code in and for the Town of Barton, Washington County, Wisconsin. The Code of the Town of Barton is incorporated in this ordinance by reference.
This ordinance is effective on publication or posting. The Town Clerk shall properly post or publish this ordinance as required under § 60.80, Wis. Stats.


Source Credit Pub. L. 90-321, title VI, §615, as added Pub. L. 91-508, title VI, §601, Oct. 26, 1970, 84 Stat. 1133; amended Pub. L. 104-208, div. A, title II, §2411, Sept. 30, 1996, 110 Stat. 3009-443; Pub. L. 108-159, title I, §§114, 154(b), 155, title II, §213(a), title III, §311(a), title VIII, §811(h), Dec. 4, 2003, 117 Stat. 1960, 1967, 1978, 1988, 2012; Pub. L. 111-203, title X, §§1088(a)(2)(C), (7)-(9), 1100F, July 21, 2010, 124 Stat. 2087, 2088, 2112; Pub. L. 111-319, §2(a), Dec. 18, 2010, 124 Stat. 3457.
Whenever credit for personal, family, or household purposes involving a consumer is denied or the charge for such credit is increased either wholly or partly because of information obtained from a person other than a consumer reporting agency bearing upon the consumer's credit worthiness, credit standing, credit capacity, character, general reputation, personal characteristics, or mode of living, the user of such information shall, within a reasonable period of time, upon the consumer's written request for the reasons for such adverse action received within sixty days after learning of such adverse action, disclose the nature of the information to the consumer. The user of such information shall clearly and accurately disclose to the consumer his right to make such written request at the time such adverse action is communicated to the consumer.
(E) the consumer may exercise the right referred to in subparagraph (D) by notifying a notification system established under section 1681b(e) of this title.
(B) be presented in such format and in such type size and manner as to be simple and easy to understand, as established by the Commission, by rule, in consultation with the Federal banking agencies and the National Credit Union Administration.
(D) include the contact information specified by that consumer reporting agency for obtaining such consumer reports (including a toll-free telephone number established by the agency in the case of a consumer reporting agency described in section 1681a(p) of this title).
The Commission and the Board shall jointly prescribe rules.
2010—Subsec. (e)(4). Pub. L. 111–319 added par. (4).
Subsec. (e). Pub. L. 108–159, §811(h), repealed Pub. L. 104–208, §2411(c). See 1996 Amendment note below.
Pub. L. 108–159, §114, added subsec. (e) and struck out former subsec. (e) designation that had been added with no heading or text by Pub. L. 104–208, §2411(c). See note above and 1996 Amendment note below.
Subsec. (f). Pub. L. 108–159, §154(b), added subsec. (f).
Subsec. (g). Pub. L. 108–159, §155, added subsec. (g).
Subsec. (h). Pub. L. 108–159, §311(a), added subsec. (h).
Subsec. (b). Pub. L. 104–208, §2411(e), inserted subsec. heading, designated existing provisions as par. (1) and inserted heading, and added par. (2).
Subsec. (c). Pub. L. 104–208, §2411(d), substituted “this section” for “subsections (a) and (b) of this section”.
Subsec. (d). Pub. L. 104–208, §2411(b), added subsec. (d).
Subsec. (e). Pub. L. 104–208, §2411(c), which added subsec. (e) containing subsec. designation, but no heading or text, was repealed by Pub. L. 108–159, §811(h).


§ 628.26 Laws outlining identity theft in MI, the jurisdiction identity theft can be prosecuted in and the penalties after prosecution. Defines phishing and how it is prosecuted. Law enforcement is required to take any report of identity theft. Victims are entitled to free copies of court documents relating to their case upon written request.
§609.652 Law regarding the use and illegal use/forging of Driver’s Licenses and ID cards.
§325E.64 Laws regarding the improper use of payment cards and the penalties for using and selling card information.
§325E.59 Law regarding how transmission and sharing of Social Security numbers.
§13.04 Right to correct fraudulent criminal history.
§325E.64 Laws regarding proper procedure in the event of an information security breach.
§13C.016 Law regarding application and terms of a credit freeze.