User interface for a secondary display module of a mobile electronic device

A user interface (UI) for use with a secondary display module of a mobile electronic device. The UI allows the user to access application data without activating the operating system (OS) of the main portion of the mobile electronic device. The UI can allow the user to access application data by activating the OS and an associated low-power application without launching the application. The UI also provides a simple mechanism to disable wireless components of the mobile electronic device while allowing the user to use other non-wireless components. The secondary display module can be detached from a main portion of the mobile electronic device, with the UI being automatically activated. The UI can be automatically activated (or deactivated) in response to deactivation (or activation) of the UI of the main display of the mobile electronic device.

FIELD

The present disclosure relates generally to electronic devices and, more particularly but not exclusively to user interfaces for use on secondary display modules of a mobile electronic device, such as a hand-held portable computer.

BACKGROUND

Mobile electronic devices typically include a display to present a user interface (UI) that provides visual information to a user. The UI also generally allows the user to input control and data information to the mobile electronic device. For example, cellular telephones (one type of mobile electronic device) typically have a liquid crystal display (LCD) and a keypad to present a UI that allows the user to make telephone calls, store telephone numbers, find stored phone numbers etc.

Some mobile electronic devices have a “clamshell” design in which the mobile electronic device is separated into two portions attached by a hinge mechanism so that the device can be “opened” and “closed”. In a typical clamshell design, one portion contains the display and the other contains a keypad. When open, the display and keypad are visible to the user. When closed, the display and keypad are typically positioned to face each other so that they are somewhat protected from the environment and not visible to the user.

In some clamshell designs, the mobile electronic device includes a secondary display that is visible to the user when the mobile electronic device is closed. This secondary display typically has limited functionality. For example, in a clamshell type cellular telephone the time and date may be shown on the secondary display or, when receiving a telephone call, the cellular telephone may show the name or telephone number of the caller on the secondary display. In a typical design, a cellular telephone does not provide a UI on the secondary display.

Further, mobile electronic devices are typically battery-powered. Consequently, power conservation is an important design consideration.

SUMMARY

In accordance with aspects of the various embodiments, a UI is provided for use with a secondary display module of a mobile electronic device having a main display. In one aspect, the secondary display module UI allows a user to access application data (e.g. email messages) without activating the system resources (such as the central processing unit, networking device, operating system, etc.) of the mobile electronic device, which helps to conserve power in some embodiments.

In another aspect, selected “full” applications residing in the mobile electronic device have associated low-power applications that are optimized to provide information to be displayed in the secondary display module UI (which provides functions that are more simplified than those provided by the UI used with the main display). The secondary display module UI allows the user to access application data using an associated low-power application without launching the full application, which helps to conserve power in some embodiments.

In yet another aspect, the UI of the secondary display module provides a simple mechanism to turn off or disable wireless components of the mobile electronic device. This aspect can advantageously allow a user to easily and quickly turn off wireless communication components of the mobile electronic device when in an airplane as typically required when the airplane is in the air. In a further refinement, the wireless portions can be disabled when the mobile electronic device is turned on thereby allowing the user to use the mobile electronic device while other non-wireless components are operating.

In still another aspect, the secondary display module can be detached from a main portion of the mobile electronic device, with the UI of the secondary display module being automatically activated. In a further refinement of this aspect, the UI can be automatically reoriented (e.g. from a “landscape” to “portrait” orientation) on the display of the secondary display module. In a related aspect, the UI of the secondary display module can be automatically activated (or deactivated) in response to deactivation (or activation) of the UI of the main display of the mobile electronic device.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

FIGS. 1-2show an example mobile electronic device, in this case a hand-held portable computer100in which an embodiment may be implemented. While the portable computer100is used as the illustrative example throughout this application, other embodiments may be implemented with devices that may not necessarily be thought of as a “computer” by the average individual or with devices that may not necessarily have the same portability feature, shape, and/or appearance as the portable computer100ofFIGS. 1-2. Examples include wireless communication devices, display devices, monitors, stationary desktop computers, audio-video equipment, consumer electronic devices, or other electronic devices that may or may not have a reduced form factor.

As shown, the portable computer100is similar in appearance to a laptop computer, in that it comprises first and second portions102and104, respectively. The first portion102can include a keyboard110and housing for the internal electronic components (such as one or more processors, machine-readable storage media, graphics drivers, and so forth). The second portion104folds over the first portion102(when in a closed position, such as shown inFIG. 2), and includes a display screen108for displaying information (such as an email inbox, emails, downloaded attachments, and/or indicators that indicate the presence of emails, attachments, etc. in an inbox or email folder) while the second portion104is unfolded to an upright position as shown inFIG. 1.

Unlike a conventional laptop computer, however, an embodiment of the portable computer100is substantially smaller in size in terms of both volume and weight. An example dimensional size of the portable computer100is 140 mm long, 101 mm wide, and 30 mm thick (while closed), with a weight of approximately one pound. The display screen108on the second portion104is of a resolution comparable to a desktop computer monitor. In general, the size of the display screen108, the size of the internal components (e.g. chips and circuit boards) located within the first portion102, and the strategic placement of the internal components (e.g. density), and other factors will influence the overall form factor of the portable computer100. As illustrated inFIGS. 1-2, the portable computer100has a size such that it can be held securely in a hand106of a user whether in the open or closed position.

FIG. 2further illustrates an embodiment of the portable computer100that has a low-power display114positioned on the top surface (lid) of the second portion104. As described later below, the low-power display114can form part of a secondary module for displaying attachment listings or an email inbox, and which provides controls to select an email to read, select an attachment to download, or to perform other operations.

Examples of the portable computer100in which embodiments of the UI may be implemented are disclosed in U.S. patent application Ser. No. 10/338,802, entitled “SYSTEM AND METHOD FOR HEAT REMOVAL FROM A HAND-HELD PORTABLE COMPUTER WHILE DOCKED”; U.S. patent application Ser. No. 10/338,815, entitled “NAVIGATION AND SELECTION CONTROL FOR A HAND-HELD PORTABLE COMPUTER”; U.S. patent application Ser. No. 10/338,761, entitled “HEAT DISSIPATION FROM A HAND-HELD PORTABLE COMPUTER”; and U.S. patent application Ser. No. 10/338,791, entitled “KEYBOARD WITH MOUSE FOR A HAND-HELD PORTABLE COMPUTER”, all filed Jan. 7, 2003.

FIG. 3and the accompanying discussion provide a description of a suitable computing environment in which embodiments can be implemented. Although not required, embodiments will be described in the general context of hardware and computer-executable instructions, such as program application modules, objects, drivers, services, or macros being executed by a computer (such as by the portable computer100). Embodiments can be practiced with other computer systems and/or network configurations as well.

FIG. 3shows a computing system300, and in particular shows an embodiment of the portable computer100in more detail. The computing system300includes the portable computer100and a server computing system302. The server computing system302may be located at one or more network locations, for example, at one or more Internet Service Provider (ISP) locations to store and serve email information and to serve other information to the portable computer100.

The portable computer100includes a processing unit304for high-power processing, at least one system memory306, and a system bus308that couples various system components, including the system memory306, to the processing unit304. The processing unit304may be any logic processing unit, such as one or more central processing units (CPUs), digital signal processors (DSPs), graphics processors, application-specific integrated circuits (ASICs), etc.

In an embodiment, the portable computer100may also include a low-power processing unit310for low power processing, and which may or may not necessarily operate with the same operating system as the processing unit304. For example, in one embodiment separate operating systems, memory, applications, or other components can be provided for the processing unit304and for the low-power processing unit310. It is also possible in an embodiment for the processing unit304and for the low-power processing unit310to share certain components, rather than having separate dedicated components.

The system bus308can employ any suitable bus structure or architecture, including a memory bus with memory controller, a peripheral bus, and a local bus. The system memory306may include one or more read-only memories (ROM(s))310and one or more random access memories (RAM(s))312. In one embodiment, separate ROM310, RAM312, and/or other memory can be dedicated for the low power display114. A BIOS314, for example, which can be stored in the ROM310, contains routines that help transfer information between elements within the portable computer100, such as during start-up. Operation of an embodiment of the BIOS314in connection with a low power mode will be described in further detail below.

The portable computer100may include a hard disk drive316for reading from and writing to a hard disk318. The hard disk drive316communicates with the processing unit304via the system bus308. The hard disk drive316may include interfaces or controllers (not shown) coupled between the hard disk drive316and the bus308. The hard disk drive316and its associated hard disk318provide nonvolatile or otherwise persistent storage of computer readable instructions, data structures, program modules and other data for the portable computer100. Although the depicted portable computer100employs the hard disk drive316and the hard disk318, other types of drives and computer-readable media that can store data accessible by a computer may be employed, such as compact disks (CDs), magnetic cassettes, flash memory cards, digital video disks (DVDs), Bernoulli cartridges, RAMs, ROMs, smart cards, etc. In one embodiment, the hard disk drive316and/or other drives are not integrated within a housing of the portable computer100itself, but instead are external devices that are accessible via hardwire or wireless communication interfaces.

The hard disk drive316can operate in conjunction with the hard disk318to store media files, such as MP3 files or other types of audio files. In an embodiment, these media files can be read from the hard disk318during a full power mode or during the low power mode, where attempts to access the hard disk318during the low power mode to read media files are minimized as much as possible during the low power mode.

The system memory306can be used for storing various program modules, such as one or more operating systems320, one or more application programs322(such as an email program, the low power media player, an installed media player, or other applications that can operate in a high power mode or in a low power mode), other programs or modules324, and program data326. A non-limiting example of an operating system320that may be used is Windows XP™ commercially available from Microsoft Corporation of Redmond, Washington. Windows XP™ or other suitable operating systems may include a power management subsystem. An embodiment provides power management capabilities in connection with the low power mode that supplements power management provided by the power management subsystem of the operating systems320.

The other programs/modules324can include libraries, application program interfaces (APIs), objects, or other components. The program data326can include cached data, such as cached songs or other media files, in one embodiment. As such, parts of the system memory306provide volatile or otherwise non-persistent memory capability, (such as an operating system cache, a RAM312, or other cache or non-persistent storage location) for storing media files.

The program data326can be stored as a data structure, file, or other data format in a cache, database, or other storage unit integrated in or separate from the system memory306. In one embodiment, the program data326also includes power profiles and other power management data indicative of the power requirements of particular services, software, and hardware of the portable computer100. This power management data is used in one embodiment to determine which component of the portable computer100to keep ON or to turn OFF during the low power mode, the length of time to keep the component ON or OFF, the sequence for turning various components ON or OFF, and to determine other parameters and settings. A detailed discussion of the other programs/modules324that interact to manage and control the portable computer400in the low power mode and the operations of application programs322(and more specifically, for managing and controlling the operation of low power mode application programs) is included in pending U.S. patent application Ser. No. 10/857,628 (Pub. No. US2005/0076256), entitled “METHOD AND APPARATUS FOR OPERATING AN ELECTRONIC DEVICE IN A LOW POWER MODE” filed May 28, 2004, which subject matter is hereby incorporated by reference.

The portable computer100may also include a web browser328for permitting the portable computer100to access and exchange data with sources such as Internet web sites, corporate intranets, extranets, and/or other networks as described below, as well as other server applications on server computers. For purposes of clarity the browser328is shown separately inFIG. 3. According to various embodiments, the browser328can comprise one of the application programs322, one of the other programs/modules324, and/or may be integrated in some manner with the operating system(s)320. While shown inFIG. 3as being stored in the system memory306, the operating systems320, application programs322, other programs/modules324, program data326, and browser328can be stored in the hard disk318of the hard disk drive316and/or other computer-readable media in another embodiment. Moreover, the various elements depicted as being stored in the system memory306need not necessarily reside on the same physical memory. For example, in embodiments where the low-power processing unit310and the low power display114can be operatively detached from the portable computer100or otherwise operate independently of other components of the portable computer100, separate memory (having an operating system, RAM, ROM, applications, and other elements stored thereon) can be operatively decoupled from the portable computer100along with the low-power processing unit310and the low power display114. In such an embodiment, the decoupleable components can be integrated in a secondary display module.

A user can enter commands and information into the portable computer100through one or more input devices (such as the keyboard110) and a pointing device (such as a mouse330that may be, for example, built into the keyboard110, an example embodiment of which is disclosed in U.S. patent application Ser. No. 10/338,791), or through such other types of devices usable for providing user input. Alternatively or additionally, the mouse330can be embodied as a touch pad as compared to physical buttons. Another input device may take the form of one or more buttons332on the side of the keyboard110, with the button(s)332usable for scrolling and clicking via turning and pressing of the button(s)332. Other possible input devices can include a microphone, joystick, game pad, scanner, etc. (not shown). These and other input devices are connected to the processing unit304through an interface334such as a serial port interface that couples to the bus308, although the portable computer100may employ other interfaces such as a parallel port, a game port or a wireless interface or a universal serial bus (USB). The interface334can be any suitable communication interface to the bus308and need not necessarily be a port per se. In one embodiment, the input devices such as a mouse, joystick, game pad, keyboard, etc. are integrated directly into the housing of the portable computer100, rather than or in addition to being couple-able via a serial or parallel port interface.

The display screen108operates as the main display and is coupled to the bus308via a graphics interface336, such as a video adapter or other graphics component that will allow video and other graphics to be rendered on the display screen108. The low power display114(and its associated user interfaces) may also be present in one embodiment to allow presentation of data (e.g. presentation on the outside surface of the second portion104of the portable computer100) during the low power mode, when the lid is closed on the portable computer100. The low power display114may be coupled to the bus308by way of the graphics interface336(or other interface) or may be directly coupled to the bus308. The low power display114can provide its user interface with various controls, such as buttons and menus, which may be used to control various aspects of applications operating in the low power mode. Also as depicted inFIG. 3, the lid switch112can be coupled to the system bus308to allow the various components of the portable computer100to detect and respond to a closing or opening of the lid of the portable computer100.

The portable computer100can operate in a networked environment using logical connections to one or more remote computers and/or devices external to the portable computer100, such as the server computing system302and a network device340, such as a printer or network storage unit. The portable computer100is logically connected to one or more remote computing systems or devices under any suitable method of permitting computers to communicate, such as through a wireless local area network (WLAN)342, a wireless wide area network (WWAN), or any other network344, including wired and wireless networks that use or can communicate with the Internet (e.g. World Wide Web). Various embodiments can be implemented to communicate with several types of communication networks, including but not limited to, telecommunications networks, cellular networks, paging networks, wired and wireless enterprise-wide computer networks, intranets, extranets, the Internet, and other types of networks. Examples of wireless systems and protocols with which the portable computer100can communicate, include but are not limited to, WiFi, Bluetooth, IEEE 802.11, and others.

When used in a LAN networking environment, the portable computer100can be connected to the LAN342through an adapter or network interface346(communicatively linked to the bus308). When used in a WWAN or other network344, the portable computer100may include a modem, transceiver348or other device, such as the network interface346, for establishing communications in this networked environment or for otherwise communicating with external devices. The transceiver348as shown inFIG. 3is communicatively linked between the interface334and the network344. The transceiver348may be one or more transmitters, receivers, or other communication devices that are compliant with, for example, IEEE 802.11, GPS, Bluetooth, cellular (TDMA, FDMA, and/or CDMA), WiFi, virtual private network (VPN), and/or other communication standard or technique.

In one embodiment, the portable computer100is communicatively linked to the server computing system302through the LAN342and/or the network344with the Transmission Control Protocol/Internet Protocol (TCP/IP) or other network protocols, such as the User Datagram Protocol (UDP). The network connections shown inFIG. 3are illustrative examples of communication links between computers, and other links can be used, including both hardwire and wireless links.

The server computing system302includes one or more servers350. In the context of email, the server350can comprise an email server. An example of such a server is a Microsoft Exchange™ server, and the principles described herein are not to be limited to only email implementations that use a Microsoft Exchange™ server.

FIG. 4illustrates a portable computer400in which a secondary display module402(referred to in this embodiment as a Low Power Interactive Display module or “LID module”) can be detached from the rest of the portable computer400, according to one embodiment. The portion of the portable computer400excluding the LID module402is referred to herein as the “main portion” of the portable computer400. In one embodiment, the LID module402is detachably attached to a portion of the portable computer400that is similar to the second portion104(FIG. 2). In other embodiments, the LID module402may be detachably attached to another portion of the portable computer400. In this embodiment, in addition to the previously described main display108, processor unit304, BIOS314, system memory306, the main portion of the portable computer400includes a battery404, a wireless network unit408and a side wheel410. In some embodiments, wireless network unit408provides functionality for wireless networks that conform to IEEE Standard 802.11b and/or 802.11g. Side wheel410is an input device that allows a user to scroll through data being displayed in either main display108or low-power display114on the LID module402.

The LID module402, in this embodiment, includes the previously described low-power processor unit310, and low-power display114. In one embodiment, low-power processing unit310is an application specific integrated circuit device that includes an embedded ARM7 core (available from ARM Ltd., Cambridge, UK), non-volatile and volatile memory, Bluetooth circuitry and RF circuitry. In some embodiments, low-power processing unit310and other circuitry of the LID module402can communicate with the rest of the portable computer400via one or more universal serial bus (USB) connections such as USB430. Further, in some embodiments, low-power processing unit310can communicate with other circuitry of the rest of portable computer400via an Inter-Integrated circuit (I2C) bus432.

This embodiment of the LID module402also includes a keypad420, a wide area network (WAN) module422, and removable data storage424(e.g. LID module402may include a slot for secure data (SD) cards or other removable storage media). The WAN module422can include a cellular module and/or a global positioning system (GPS) module for wireless communication of voice and data information. In some embodiments, the LID module402can be detached from the main portion of the portable computer400so that the WAN module422can provide the LID module402with standalone cellular telephone and GPS functionalities. In some embodiments, the removable data storage424and/or the WAN module422may be omitted.

FIG. 5is a block diagram of software components of the portable computer400and the LID module402. In this embodiment, the main portion of the portable computer400includes a LID interface module502, which supports a LID module application protocol used to transfer control and data between the portable computer400and the LID module402. In this exemplary embodiment, the portable computer400also includes: a low-power media player504and an associated “normal” or standard media player505(e.g. Windows Media Player available from Microsoft Corp., Redmond, Wash.); a low-power email application506and an associated normal email application507(e.g. Outlook available from Microsoft); and a low-power voice memo application510and an associated normal voice memo application511. The portable computer400can also include one or more other pairs of low-power and “normal” applications such as a low-power application514and a normal application515, as well as an operating system (OS)520and the previously described BIOS314. The OS520can be any suitable operating system, such as Microsoft Window, Linux, Mac OS, etc.

The portable computer400, in this embodiment, also includes a GPS application522for displaying GPS information received from a GPS receiver (e.g. a GPS receiver integrated in the WAN module422described above in conjunction withFIG. 4), and a Bluetooth module524(with Bluetooth profiles and services, protocol stack, and drivers) for supporting wireless communication with other Bluetooth devices (e.g. some models of headphones, keyboards, cellular telephones, personal digital assistants, etc.).

The LID module402, in this embodiment, includes: applications530to be run on the LID module402; a graphical user interface (GUI) framework532to display icons, buttons, information, etc. so that a user can interact with applications530and other modules of the LID module402; device drivers534; a real time operating system (RTOS)536to be executed by low-power processor unit310(FIG. 4), a Bluetooth module544(which includes profiles, stack, etc. for interacting with Bluetooth-capable devices); a cellular module546to operate cellular telephone circuitry of the WAN module422, and a GPS module542to operate GPS circuitry of the WAN module422. The RTOS536can be any type of RTOS suitable for the low-power processor unit310(FIG. 3). In an embodiment, real time operating system536and operating system520can be the one or more operating systems320in system memory306.

FIG. 6illustrates an exemplary UI depicted by the low-power display114of the LID module402. InFIG. 6, the LID module402is attached to the main portion of portable computer400, and includes an exemplary keypad420. In this embodiment, the low-power display114depicts the UI, which in turn includes several interactive screens. These screens include a main UI screen, an example of which is shown inFIG. 6. From the main UI screen, a user can navigate to other screens (not shown), such as “feature” screens providing various functions supported by the UI. In this embodiment, the main UI screen has icons and/or touch-sensitive buttons (in embodiments in which low-power display114is a touch screen display)601-608. Icons and touch-sensitive buttons are referred to herein as buttons. Embodiments of these buttons are described below. When a button is activated, the main UI screen transitions to a feature screen for the activated function (e.g. a main email screen, a main calendar screen).

The button601is an inbox button for accessing a streamlined set of email features via the LID module402without launching the email application507(FIG. 5). In one embodiment, if the user only wants to view email information that is cached locally on the LID module402, then the OS520(FIG. 5) is not activated. This operation is described for a general application in conjunction withFIG. 7, below. By avoiding activation of the email application507and the OS520, this feature can enable significant reductions in power dissipation by the portable computer400.

In one embodiment, activating the inbox button601allows the user to selectively check for new messages, read messages in the inbox, delete individual messages, mark messages as read or unread. The main email screen changes to a different screen for each of the above email operations. Additional options may be displayed via a pop-up menu (described further below in conjunction withFIG. 8). In this embodiment, more complex email operations are performed via the main portion of the portable computer400and the launching of the email application507.

Button602is a settings button for customizing selected features of the LID module402. In one embodiment, the settings button602can be used to set up security features (e.g. security codes/password, security timer), set up the wireless functions of the LID module402(e.g. enable/disable Bluetooth, radio, cellular telephone, WiFi features), change display settings (e.g. backlight timer, font size, contrast, scroll rate, etc.), and change sound settings (e.g. alerts for email, low power warning, etc.).

Button603is a calendar button for accessing a streamlined set of calendar features via the LID module402without launching a calendar application. For example, the application514(FIG. 5) can be a calendar application or part of the email application507that includes calendar functions. In this embodiment, the calendar button603allows a user to view calendar entries and receive reminders for events entered into the calendar. In one embodiment, the LID module402locally caches calendar information for a preselected period of time (e.g. five weeks). From the main calendar screen, a user can view additional screens that display calendar information for a specific month or week or day. The main calendar screen may display buttons that allow the user to scroll through the calendar. These additional screens may also include buttons to allow a user to navigate to other screens showing details of the reminders (e.g. an appointment entered into the calendar).

Button604is a lock keypad button for disabling most of the keys of the keypad420and the buttons depicted by the low-power display114to prevent inadvertent operation of the LID module402. The LID module402can be unlocked by pressing a preselected sequence of keys of the keypad420. In one embodiment, a user can select an option requiring a security code or password to be entered before the LID module402can be unlocked.

Button605is a wireless on/off (flight mode) button for turning wireless radios (e.g. Bluetooth features, WiFi features, cellular telephone features, etc.) on and off. This feature can be advantageously used during a flight on an airplane (which typically prohibits such radio activity for the duration of the flight). This feature provides a quick and easy method to ensure that the prohibited radio features are turned off, even while the user is using other (non-radio) features of the portable computer400.

Button606is a contacts button for accessing a streamlined set of contact features via the LID module402without launching a contacts application. For example, the application514(FIG. 5) can be a contacts application or part of the email application507that includes contact functions. In this embodiment, the contacts button606allows a user to find and view contact entries by entering the first few letters of the contact's name via buttons displayed from the contacts main screen. The main contacts screen may also display buttons that allow the user to select how the contacts will be displayed (e.g. sorted by first or last name, company, phone number, etc.). The screen displaying the contacts may also include buttons that allow the user to navigate to other screens displaying more detailed contact information about the contact.

Button607is an audio player button for accessing a streamlined set of audio player features via the LID module402without launching the media player application505. In this embodiment, the audio player button607allows a user to browse and play audio files. From the main audio player screen, a user can navigate through a series of screens to find particular audio tracks or files. In one embodiment, when the audio player button607is activated, the LID module402displays an audio library screen with buttons that allow the user to browse the library. For example, the audio library screen may include buttons for browsing by artists, albums, genres, tracks, user-defined play lists, all tracks, etc. After selecting a browsing method, the LID module displays a screen showing the artists, albums, genres etc. with buttons that allow the user to scroll or navigate through the displayed artists, albums, etc. The user can then select an artist, album etc., which causes the LID module to display the tracks associated with the selection. The user can then activate a “play” button displayed on the screen to play the tracks. In some embodiments, the user may navigate to additional screens that display track information such as title, artist, composer, album, track size (in KB or MB), duration, bit-rate, etc. In some embodiments, the user may also navigate to additional screens that allow the user to change settings on the audio player (e.g. volume, repeat, shuffle, etc.).

Button608is a voice memo button for accessing a streamlined set of voice memo features via the LID module402, without launching the voice memo application511. In this embodiment, the voice memo button608allows a user to record and play voice memos through the LID module402. In one embodiment, if there are no voice memos stored in the LID module402, activating the voice memo button608causes a “record memo” screen to be displayed. If there are stored voice memos, a “display memos” screen is displayed instead.

In one embodiment, the “record memo” screen displays buttons that allow a user to start, pause and stop recording. This screen may also display the duration of the memo as it is being recorded. When the stop button is activated, the LID module402automatically displays the “display memos” screen, in one embodiment.

The “display memos” screen lists all of the stored voice memos, and buttons for playing and deleting the displayed memos. This screen may also include a button for recording new memos, which causes the LID module402to display the aforementioned “record memo” screen. When the user activates the play button, the LID module displays play, pause and stop buttons, and a graphic that shows the remaining duration of the memo.

FIG. 7is a flow diagram illustrating operation flow of the LID module402(FIG. 5) in starting an application residing in the main portion of the portable computer400(FIG. 5). In one embodiment, these operations will be initiated when the LID module402accesses information that resides in the main portion of the portable computer400(e.g. the information is not cached in the LID module402) in response to the user activating a button on the main UI screen (e.g., see the main UI screen shown inFIG. 6) of the LID module402.

Referring toFIGS. 5 and 7, in a block702, LID module402receives a signal to start an application. In this embodiment, the LID module402can receive such a signal when the user activates a button displayed from the main UI screen (FIG. 6). For example, if the user activates the inbox button601, the GUI framework532of the LID module402receives a signal to start an email application on the main portion of the portable computer400.

In block704, the LID module402determines whether the OS520of the main portion of the portable computer400is active. If in a decision block706the LID module402determines that the OS520is not active, the operation flow proceeds to a block708in which the LID module402sends a wake-up signal to the main portion of the portable computer400. In one embodiment, the low-power processing unit310(FIG. 4) sends the wake up signal to the BIOS314of the main portion of the portable computer400, bypassing the LID interface module502. The main portion of the portable computer400can then send a message to the LID module402that the OS520is active, via the LID interface module502. The operational flow then returns to block706. If in block706the LID module402determines that the OS520is active, then operational flow proceeds to a block710.

In a block710, the LID module402sends a start application signal or message to the main portion of the portable computer400via the LID interface module502. In this embodiment, the LID interface module502causes the low-power application514associated with the “full” application to start, leaving the full application unlaunched. As previously described, this feature allows the LID module402to reduce the power dissipation of the portable computer400and to provide the low power application514with access to associated data while still providing one or more of the features of the “full” application. The low-power application514typically provides a subset of the features provided by the corresponding full application, but in some embodiments the low-power application514may provide feature(s) that are not supported by the full application. Continuing the email example described in conjunction with the block702, the low-power email application506would be started without launching the email application507, as disclosed in pending U.S. patent application Ser. No. 10/871,870 (Pub. No. US2005/0066006), entitled “LOW POWER EMAIL FUNCTIONALITY FOR AN ELECTRONIC DEVICE” filed Jun. 17, 2004 and incorporated herein by reference.

In a block712, when the low-power application506is ready, the LID module402sends a message with a command (e.g. request for data) to the low-power application via the LID interface module502. For example, the main portion of the portable computer400may send a message indicating the low-power application is ready/not ready for the next message or command. The LID module402can then send message(s) in response to the user's activation of buttons depicted on feature screens of the UI (described above in conjunction withFIG. 6).

In a block714, the low power application514may provide features that are not supported by the full application. For instance, the low power application514may provide one or more features that are not supported by its associated full application in addition to the corresponding low power application514being accessible on the secondary display module402and being accessible without engaging the OS320of the main logic processor unit304.

In a block716, the LID module402then receives data to be displayed in the UI (e.g. in one of the feature” screens of the application described above in conjunction withFIG. 6) via the LID interface module502.

In a block718, the LID module402then updates the UI depicted in the low-power display114(FIG. 4) with the data received from the main portion of the portable computer400in response to the message sent in the block716. In this embodiment, the GUI framework532handles display of the received data in the UI. Operational flow can then return to the block712until the user terminates the session.

FIG. 8illustrates an exemplary pop-up menu displayed in the UI of the LID module402, according to one embodiment. In this example, the LID module402displays a main email screen802(described above in conjunction withFIG. 6) when the inbox button601is activated. When the user selects a particular email message (e.g. the highlighting of the first email message indicates that it is selected), a pop-up menu804is displayed. This pop-up menu allows the user to select one of several possible operations to be performed (e.g. delete, mark as read, etc.). Although an email example is shown, pop-up menus can be used with other features that can be activated from the main screen of the UI.

FIG. 9illustrates reorientation of the UI displayed by the LID module402when detached from the main portion of the portable computer400, according to one embodiment. In this embodiment, when the LID module402is attached, the UI is oriented so that the displayed buttons are in a “landscape” orientation (i.e., with the top of the buttons oriented toward one of the long sides of the LID module402. This landscape orientation is shown inFIG. 6. When the LID module402is detached from the main portion of the portable computer400, the UI is automatically reoriented into a “portrait” orientation (i.e., with the top of the buttons oriented toward one of the short sides of the LID module402). In one embodiment, the portrait orientation has the keypad420located below the low-power display114. This feature causes the LID module402to have a configuration similar to typical cellular telephones (i.e., with the keypad below the LCD display).

In other embodiments, a user may selectively reorient the UI displayed by LID module402. For example, when using one of the cellular telephone features of the LID module402, the LID module402may be configured to automatically reorient the UI into the portrait orientation even if the LID module402is attached to the main portion of the portable computer400. In some other embodiments, the LID module402may include a component that can sense the orientation of the LID module402(e.g., the orientation of the LID module402relative to the direction of the force of gravity) and, in response to changes in orientation, automatically adjust the orientation the UI with the LID module402.

An implementation of these modules and techniques may be stored on some form of computer readable media. Computer readable media can be any media that can be accessed by a computer. By way of example, and not limitation, computer readable media may comprise “computer readable storage media.”

Reference has been made throughout this specification to “one embodiment,” “an embodiment,” or “an example embodiment” meaning that a particular described feature, structure, or characteristic is included in at least one embodiment of the present invention. Thus, usage of such phrases may refer to more than just one embodiment. Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

One skilled in the relevant art may recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, resources, materials, etc. In other instances, well known structures, resources, or operations have not been shown or described in detail merely to avoid obscuring aspects of the invention.

While example embodiments and applications have been illustrated and described, it is to be understood that the invention is not limited to the precise configuration and resources described above. Various modifications, changes, and variations apparent to those skilled in the art may be made in the arrangement, operation, and details of the methods and systems of the present invention disclosed herein without departing from the scope of the claimed invention.