Patent Publication Number: US-8994713-B2

Title: Smart pad operation with differing display parameters applied to different display elements

Description:
CROSS REFERENCE TO RELATED APPLICATION 
     This application is a continuation-in-part and claims the benefits of and priority to U.S. patent application Ser. No. 13/247,581, filed Sep. 28, 2011, which claims the benefits of and priority, under 35 U.S.C. §119(e), to U.S. Provisional Application Ser. Nos. 61/389,000, filed Oct. 1, 2010, entitled “DUAL DISPLAY WINDOWING SYSTEM;” 61/389,117, filed Oct. 1, 2010, entitled “MULTI-OPERATING SYSTEM PORTABLE DOCKETING DEVICE;” 61/389,087, filed Oct. 1, 2010, entitled “TABLET COMPUTING USER INTERFACE;” 61/458,150, filed Nov. 17, 2010, entitled “DUAL SCREEN EMAIL CLIENT;” and 61/539,884, filed Sep. 27, 2011, entitled “MOBILE DEVICE.” Each of the aforementioned documents is incorporated herein by this reference in their entirety for all that they teach and for all purposes. 
    
    
     BACKGROUND 
     A substantial number of handheld computing devices, such as cellular phones, tablets, and E-Readers, make use of a touch screen display not only to deliver display information to the user but also to receive inputs from user interface commands. While touch screen displays may increase the configurability of the handheld device and provide a wide variety of user interface options, this flexibility typically comes at a price. The dual use of the touch screen to provide content and receive user commands, while flexible for the user, may obfuscate the display and cause visual clutter, thereby leading to user frustration and loss of productivity. 
     The small form factor of handheld computing devices requires a careful balancing between the displayed graphics and the area provided for receiving inputs. On the one hand, the small display constrains the display space, which may increase the difficulty of interpreting actions or results. On the other, a virtual keypad or other user interface scheme is superimposed on or positioned adjacent to an executing application, requiring the application to be squeezed into an even smaller portion of the display. 
     This balancing act is particularly difficult for single display touch screen devices. Single display touch screen devices are crippled by their limited screen space. When users are entering information into the device, through the single display, the ability to interpret information in the display can be severely hampered, particularly when a complex interaction between display and interface is required. 
     SUMMARY 
     There is a need for a dual multi-display handheld computing device that provides for enhanced power, energy storage device life, and/or versatility compared to conventional single display handheld computing devices. These and other needs are addressed by the various aspects, embodiments, and/or configurations of the present disclosure. Also, while the disclosure is presented in terms of exemplary embodiments, it should be appreciated that individual aspects of the disclosure can be separately claimed. 
     In an embodiment, a method, device, and microprocessor readable and executable instructions are provided that: 
     determine, based on a sensed electronic storage device (ESD) parameter, to reduce energy usage of first display elements, but not second display elements, one or more displays; and 
     apply a first set of display parameters to the first display elements and a second set of display parameters to the second display elements, the values of one or more display parameters in the first and second sets of display parameters being different, whereby a first level of energy/unit area used by the first display elements is less than a second level of energy/unit area used by the second display elements. 
     The ESD parameter is typically one or more of ESD voltage, current in and/or out of the ESD, ESD capacitance, ESD inductance, ESD current drain rate, ESD current discharge rate, ESD temperature, ESD state of charge, ESD depth of discharge, and ESD state of health. 
     The first and second sets of display parameters generally comprise one or more of luminance, brightness, intensity, aspect ratio, viewable image size, display resolution, refresh rate, response time, contrast ratio, and delta-E. 
     In one configuration, the first and second display elements used approximately the same amount of energy/unit area before the applying step, and, as a result of application of the first set of display parameters, the first level of energy/unit area is no more than about 85% of the second level of energy/unit area. 
     In one configuration, the first display elements are in a first display and the second display elements are in a second display. A first value of a first display parameter in the first set of display parameters is no more than 75% of a second value of the first display parameter in the second set of display parameters. The first level of energy/unit area is no more than about 75% of the second level of energy/unit area. 
     In one configuration, the first and second display elements are in a common display, most of the first display elements have a black color while most of the second display elements have a non-black color. The first level of energy/unit area is no more than about 50% of the second level of energy/unit area. 
     In one configuration, the applying step comprises assigning a different value to each of a plurality of pixel and/or vector values to be displayed by the first display elements but not to each of a plurality of pixel and/or vector values to be displayed by the second display elements. 
     In one configuration, the method, device, and microprocessor readable and executable instructions: 
     determine, at a second later time based on a sensed electronic storage device (ESD) parameter, to reduce further energy usage of the first display elements; and 
     in response, apply a third set of display parameters to the first display elements, the values of one or more display parameters in the first and third sets of display parameters being different, whereby a first level of energy/unit area used by the first display elements is less than a third level of energy/unit area used by the first display elements in response to the third set of display parameters. 
     The present disclosure can provide a number of advantages depending on the particular aspect, embodiment, and/or configuration. 
     For example, computational device can take one or more power measures to control energy usage by displays, thereby prolonging significantly energy storage device life. The user, in his or her discretion, can configure the power conservation measures from among a plurality of possible power conservation measures as well as the thresholds at which each selected power conservation measure is triggered. 
     Additional advantages are directed toward managing the display of one or more windows associated with one or more applications on a multi-display device on a single display device. 
     Further advantages are directed toward emulation of multi-screen content on a single screen device. 
     These and other advantages will be apparent from the disclosure. 
     The phrases “at least one”, “one or more”, and “and/or” are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions “at least one of A, B and C”, “at least one of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B, or C” and “A, B, and/or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together. 
     The term “a” or “an” entity refers to one or more of that entity. As such, the terms “a” (or “an”), “one or more” and “at least one” can be used interchangeably herein. It is also to be noted that the terms “comprising”, “including”, and “having” can be used interchangeably. 
     The term “automatic” and variations thereof, as used herein, refers to any process or operation done without material human input when the process or operation is performed. However, a process or operation can be automatic, even though performance of the process or operation uses material or immaterial human input, if the input is received before performance of the process or operation. Human input is deemed to be material if such input influences how the process or operation will be performed. Human input that consents to the performance of the process or operation is not deemed to be “material”. 
     The term “computer-readable medium” refers to any storage and/or transmission medium that participate in providing instructions to a processor for execution. Such a medium is commonly tangible and non-transient and can take many forms, including but not limited to, non-volatile media, volatile media, and transmission media and includes without limitation random access memory (“RAM”), read only memory (“ROM”), and the like. Non-volatile media includes, for example, NVRAM, or magnetic or optical disks. Volatile media includes dynamic memory, such as main memory. Common forms of computer-readable media include, for example, a floppy disk (including without limitation a Bernoulli cartridge, ZIP drive, and JAZ drive), a flexible disk, hard disk, magnetic tape or cassettes, or any other magnetic medium, magneto-optical medium, a digital video disk (such as CD-ROM), any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, a solid state medium like a memory card, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read. A digital file attachment to e-mail or other self-contained information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. When the computer-readable media is configured as a database, it is to be understood that the database may be any type of database, such as relational, hierarchical, object-oriented, and/or the like. Accordingly, the disclosure is considered to include a tangible storage medium or distribution medium and prior art-recognized equivalents and successor media, in which the software implementations of the present disclosure are stored. Computer-readable storage medium commonly excludes transient storage media, particularly electrical, magnetic, electromagnetic, optical, magneto-optical signals. 
     The term “composited display” refers to a logical structure that defines a display that can encompass one or more screens. A multi-screen display can be associated with a composite display that encompasses all the screens. The composite display can have different display characteristics based on the various orientations of the device. 
     The term “desktop” refers to a metaphor used to portray systems. A desktop is generally considered a “surface” that typically includes pictures, called icons, widgets, folders, etc. that can activate show applications, windows, cabinets, files, folders, documents, and other graphical items. The icons are generally selectable to initiate a task through user interface interaction to allow a user to execute applications or conduct other operations. 
     The terms “determine”, “calculate” and “compute,” and variations thereof, as used herein, are used interchangeably and include any type of methodology, process, mathematical operation or technique. 
     The term “display” refers to a portion of one or more screens used to display the output of a computer to a user. A display may be a single-screen display or a multi-screen display, referred to as a composite display. A composite display can encompass the touch sensitive display of one or more screens. A single physical screen can include multiple displays that are managed as separate logical displays. Thus, different content can be displayed on the separate displays although part of the same physical screen. 
     The term “displayed image” refers to an image produced on the display. A typical displayed image is a window or desktop. The displayed image may occupy all or a portion of the display. 
     The term “display orientation” refers to the way in which a rectangular display is oriented by a user for viewing. The two most common types of display orientation are portrait and landscape. In landscape mode, the display is oriented such that the width of the display is greater than the height of the display (such as a 4:3 ratio, which is 4 units wide and 3 units tall, or a 16:9 ratio, which is 16 units wide and 9 units tall). Stated differently, the longer dimension of the display is oriented substantially horizontal in landscape mode while the shorter dimension of the display is oriented substantially vertical. In the portrait mode, by contrast, the display is oriented such that the width of the display is less than the height of the display. Stated differently, the shorter dimension of the display is oriented substantially horizontal in the portrait mode while the longer dimension of the display is oriented substantially vertical. 
     The term “gesture” refers to a user action that expresses an intended idea, action, meaning, result, and/or outcome. The user action can include manipulating a device (e.g., opening or closing a device, changing a device orientation, moving a trackball or wheel, etc.), movement of a body part in relation to the device, movement of an implement or tool in relation to the device, audio inputs, etc. A gesture may be made on a device (such as on the screen) or with the device to interact with the device. 
     The term “gesture capture” refers to a sense or otherwise a detection of an instance and/or type of user gesture. The gesture capture can occur in one or more areas of the screen, A gesture region can be on the display, where it may be referred to as a touch sensitive display or off the display where it may be referred to as a gesture capture area. 
     It shall be understood that the term “means” as used herein shall be given its broadest possible interpretation in accordance with 35 U.S.C., Section 112, Paragraph 6. Accordingly, a claim incorporating the term “means” shall cover all structures, materials, or acts set forth herein, and all of the equivalents thereof. Further, the structures, materials or acts and the equivalents thereof shall include all those described in the summary of the invention, brief description of the drawings, detailed description, abstract, and claims themselves. 
     The term “module” as used herein refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and software that is capable of performing the functionality associated with that element. 
     A “multi-screen application” refers to an application that is capable of multiple modes. The multi-screen application mode can include, but is not limited to, a single screen mode (where the application is displayed on a single screen) or a composite display mode (where the application is displayed on two or more screens). A multi-screen application can have different layouts optimized for the mode. Thus, the multi-screen application can have different layouts for a single screen or for a composite display that can encompass two or more screens. The different layouts may have different screen/display dimensions and/or configurations on which the user interfaces of the multi-screen applications can be rendered. The different layouts allow the application to optimize the application&#39;s user interface for the type of display, e.g., single screen or multiple screens. In single screen mode, the multi-screen application may present one window pane of information. In a composite display mode, the multi-screen application may present multiple window panes of information or may provide a larger and a richer presentation because there is more space for the display contents. The multi-screen applications may be designed to adapt dynamically to changes in the device and the mode depending on which display (single or composite) the system assigns to the multi-screen application. In alternative embodiments, the user can use a gesture to request the application transition to a different mode, and, if a display is available for the requested mode, the device can allow the application to move to that display and transition modes. 
     The term “screen,” “touch screen,” or “touchscreen” refers to a physical structure that includes one or more hardware components that provide the device with the ability to render a user interface and/or receive user input. A screen can encompass any combination of gesture capture region, a touch sensitive display, and/or a configurable area. The device can have one or more physical screens embedded in the hardware. However a screen may also include an external peripheral device that may be attached and detached from the device. In embodiments, multiple external devices may be attached to the device. Thus, in embodiments, the screen can enable the user to interact with the device by touching areas on the screen and provides information to a user through a display. The touch screen may sense user contact in a number of different ways, such as by a change in an electrical parameter (e.g., resistance or capacitance), acoustic wave variations, infrared radiation proximity detection, light variation detection, and the like. In a resistive touch screen, for example, normally separated conductive and resistive metallic layers in the screen pass an electrical current. When a user touches the screen, the two layers make contact in the contacted location, whereby a change in electrical field is noted and the coordinates of the contacted location calculated. In a capacitive touch screen, a capacitive layer stores electrical charge, which is discharged to the user upon contact with the touch screen, causing a decrease in the charge of the capacitive layer. The decrease is measured, and the contacted location coordinates determined. In a surface acoustic wave touch screen, an acoustic wave is transmitted through the screen, and the acoustic wave is disturbed by user contact. A receiving transducer detects the user contact instance and determines the contacted location coordinates. 
     A “single-screen application” refers to an application that is capable of single screen mode. Thus, the single-screen application can produce only one window and may not be capable of different modes or different display dimensions. A single-screen application may not be capable of the several modes discussed with the multi-screen application. 
     The term “window” refers to a, typically rectangular, displayed image on at least part of a display that contains or provides content different from the rest of the screen. The window may obscure the desktop. 
     The preceding is a simplified summary of the disclosure to provide an understanding of some aspects of the disclosure. This summary is neither an extensive nor exhaustive overview of the disclosure and its various aspects, embodiments, and/or configurations. It is intended neither to identify key or critical elements of the disclosure nor to delineate the scope of the disclosure but to present selected concepts of the disclosure in a simplified form as an introduction to the more detailed description presented below. As will be appreciated, other aspects, embodiments, and/or configurations of the disclosure are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1A  includes a first view of an embodiment of a multi-screen user device; 
         FIG. 1B  includes a second view of an embodiment of a multi-screen user device; 
         FIG. 1C  includes a third view of an embodiment of a multi-screen user device; 
         FIG. 1D  includes a fourth view of an embodiment of a multi-screen user device; 
         FIG. 1E  includes a fifth view of an embodiment of a multi-screen user device; 
         FIG. 1F  includes a sixth view of an embodiment of a multi-screen user device; 
         FIG. 1G  includes a seventh view of an embodiment of a multi-screen user device; 
         FIG. 1H  includes a eighth view of an embodiment of a multi-screen user device; 
         FIG. 1I  includes a ninth view of an embodiment of a multi-screen user device; 
         FIG. 1J  includes a tenth view of an embodiment of a multi-screen user device; 
         FIG. 2  is a block diagram of an embodiment of the hardware of the device; 
         FIG. 3A  is a block diagram of an embodiment of the state model for the device based on the device&#39;s orientation and/or configuration; 
         FIG. 3B  is a table of an embodiment of the state model for the device based on the device&#39;s orientation and/or configuration; 
         FIG. 4A  is a first representation of an embodiment of user gesture received at a device; 
         FIG. 4B  is a second representation of an embodiment of user gesture received at a device; 
         FIG. 4C  is a third representation of an embodiment of user gesture received at a device; 
         FIG. 4D  is a fourth representation of an embodiment of user gesture received at a device; 
         FIG. 4E  is a fifth representation of an embodiment of user gesture received at a device; 
         FIG. 4F  is a sixth representation of an embodiment of user gesture received at a device; 
         FIG. 4G  is a seventh representation of an embodiment of user gesture received at a device; 
         FIG. 4H  is a eighth representation of an embodiment of user gesture received at a device; 
         FIG. 5A  is a block diagram of an embodiment of the device software and/or firmware; 
         FIG. 5B  is a second block diagram of an embodiment of the device software and/or firmware; 
         FIG. 6A  is a first representation of an embodiment of a device configuration generated in response to the device state; 
         FIG. 6B  is a second representation of an embodiment of a device configuration generated in response to the device state; 
         FIG. 6C  is a third representation of an embodiment of a device configuration generated in response to the device state; 
         FIG. 6D  is a fourth representation of an embodiment of a device configuration generated in response to the device state; 
         FIG. 6E  is a fifth representation of an embodiment of a device configuration generated in response to the device state; 
         FIG. 6F  is a sixth representation of an embodiment of a device configuration generated in response to the device state; 
         FIG. 6G  is a seventh representation of an embodiment of a device configuration generated in response to the device state; 
         FIG. 6H  is a eighth representation of an embodiment of a device configuration generated in response to the device state; 
         FIG. 6I  is a ninth representation of an embodiment of a device configuration generated in response to the device state; 
         FIG. 6J  is a tenth representation of an embodiment of a device configuration generated in response to the device state; 
         FIG. 7A  is representation of a logical window stack; 
         FIG. 7B  is another representation of an embodiment of a logical window stack; 
         FIG. 7C  is another representation of an embodiment of a logical window stack; 
         FIG. 7D  is another representation of an embodiment of a logical window stack; 
         FIG. 7E  is another representation of an embodiment of a logical window stack; 
         FIG. 8  is block diagram of an embodiment of a logical data structure for a window stack; 
         FIG. 9  is a flow chart of an embodiment of a method for creating a window stack; 
         FIG. 10  illustrates an exemplary smartpad (SP). 
         FIG. 11  illustrates an exemplary method of associating the smartpad with the device. 
         FIG. 12  illustrates a docked device with the smartpad. 
         FIGS. 13A-13B  illustrate an exemplary method for screen orientation. 
         FIG. 14  illustrates a method for displaying an application when the SP is in a landscape mode. 
         FIG. 15  illustrates a method for displaying an application when the SP is in a portrait mode. 
         FIG. 16  illustrates an example of a dual screen application in portrait max mode. 
         FIG. 17  illustrates an example of a dual screen application in max mode landscape. 
         FIG. 18  illustrates an example of keyboard management on the SP. 
         FIG. 19  illustrates an example of keyboard management on the SP with an application area in max mode. 
         FIG. 20  illustrates another example of keyboard management for the SP in landscape mode. 
         FIG. 21  illustrates an example of a dual screen application running in a dual screen emulation mode on the SP with a virtual keyboard. 
         FIG. 22  illustrates an example of application window stack management on the SP. 
         FIG. 23  illustrates another example of application window stack management on the SP. 
         FIG. 24  illustrates an example of multi application mode of the SP, wherein in the multi application mode the SP emulates the device in its mini-tablet form. 
         FIG. 25  illustrates another example of multi application mode of the SP. 
         FIG. 26  illustrates another example of multi application mode of the SP. 
         FIG. 27  illustrates another example of multi application mode of the SP. 
         FIG. 28  illustrates a method for managing screen display. 
         FIG. 29  illustrates an exemplary method for managing screen display with the desktop. 
         FIG. 30  illustrates an exemplary method of managing screen display with a keyboard. 
         FIGS. 31A and 31B  illustrate desktop management on the SP. 
         FIGS. 32A and 32  B illustrate exemplary methods for desktop panel management. 
         FIG. 33  illustrates exemplary notification management on the SP. 
         FIGS. 34A and 34B  illustrate exemplary techniques for application management. 
         FIGS. 35A and 35B  illustrate an exemplary method for providing desktop previews or hints. 
         FIG. 36  illustrates an exemplary carousel application window stack. 
         FIG. 37  illustrates an exemplary carousel application window stack with a virtual keyboard. 
         FIG. 38  illustrates an exemplary method for associating the device and the SP. 
         FIG. 39  illustrates an exemplary method for application reorientation based on SP orientation. 
         FIG. 40  illustrates an exemplary method for managing the keyboard on the SP. 
         FIG. 41  illustrates an exemplary method for window manipulation based on one or more gestures. 
         FIG. 42  illustrates an exemplary method for application highlighting when an application is in focus in multi application mode. 
         FIG. 43  illustrates an exemplary method for application maximization. 
         FIG. 44  illustrates an exemplary method for transitioning from an application window to the desktop. 
         FIG. 45  illustrates an exemplary method for managing the display of the desktop and/or one or more panels on the SP. 
         FIG. 46  illustrates an exemplary method for merging panels for display on the SP. 
         FIG. 47  illustrates an exemplary method for previewing one or more panels on the SP. 
         FIG. 48  illustrates an exemplary method for stack management in multi application mode. 
         FIG. 49  illustrates an exemplary method for managing screen display. 
         FIG. 50  illustrates an exemplary method for managing screen display. 
         FIG. 51  illustrates an exemplary method for managing screen display. 
         FIG. 52  illustrates an exemplary method for managing screen display. 
         FIG. 53  illustrates an exemplary method for managing screen display. 
         FIG. 54  illustrates exemplary logic for screen display control. 
     
    
    
     In the appended figures, similar components and/or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a letter that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label. 
     DETAILED DESCRIPTION 
     Presented herein are embodiments of a device. The device can be a communications device, such as a cellular telephone, or other smart device. The device can include two screens that are oriented to provide several unique display configurations. Further, the device can receive user input in unique ways. The overall design and functionality of the device provides for an enhanced user experience making the device more useful and more efficient. 
     Mechanical Features: 
       FIGS. 1A-1J  illustrate a device  100  in accordance with embodiments of the present disclosure. As described in greater detail below, device  100  can be positioned in a number of different ways each of which provides different functionality to a user. The device  100  is a multi-screen device that includes a primary screen  104  and a secondary screen  108 , both of which are touch sensitive. In embodiments, the entire front surface of screens  104  and  108  may be touch sensitive and capable of receiving input by a user touching the front surface of the screens  104  and  108 . Primary screen  104  includes touch sensitive display  110 , which, in addition to being touch sensitive, also displays information to a user. Secondary screen  108  includes touch sensitive display  114 , which also displays information to a user. In other embodiments, screens  104  and  108  may include more than one display area. 
     Primary screen  104  also includes a configurable area  112  that has been configured for specific inputs when the user touches portions of the configurable area  112 . Secondary screen  108  also includes a configurable area  116  that has been configured for specific inputs. Areas  112   a  and  116   a  have been configured to receive a “back” input indicating that a user would like to view information previously displayed. Areas  112   b  and  116   b  have been configured to receive a “menu” input indicating that the user would like to view options from a menu. Areas  112   c  and  116   c  have been configured to receive a “home” input indicating that the user would like to view information associated with a “home” view. In other embodiments, areas  112   a - c  and  116   a - c  may be configured, in addition to the configurations described above, for other types of specific inputs including controlling features of device  100 , some non-limiting examples including adjusting overall system power, adjusting the volume, adjusting the brightness, adjusting the vibration, selecting of displayed items (on either of screen  104  or  108 ), operating a camera, operating a microphone, and initiating/terminating of telephone calls. Also, in some embodiments, areas  112   a -C and  116   a -C may be configured for specific inputs depending upon the application running on device  100  and/or information displayed on touch sensitive displays  110  and/or  114 . 
     In addition to touch sensing, primary screen  104  and secondary screen  108  may also include areas that receive input from a user without requiring the user to touch the display area of the screen. For example, primary screen  104  includes gesture capture area  120 , and secondary screen  108  includes gesture capture area  124 . These areas are able to receive input by recognizing gestures made by a user without the need for the user to actually touch the surface of the display area. In comparison to touch sensitive displays  110  and  114 , the gesture capture areas  120  and  124  are commonly not capable of rendering a displayed image. 
     The two screens  104  and  108  are connected together with a hinge  128 , shown clearly in  FIG. 1C  (illustrating a back view of device  100 ). Hinge  128 , in the embodiment shown in FIGS.  1 A- 1 J, is a center hinge that connects screens  104  and  108  so that when the hinge is closed, screens  104  and  108  are juxtaposed (i.e., side-by-side) as shown in  FIG. 1B  (illustrating a front view of device  100 ). Hinge  128  can be opened to position the two screens  104  and  108  in different relative positions to each other. As described in greater detail below, the device  100  may have different functionalities depending on the relative positions of screens  104  and  108 . 
       FIG. 1D  illustrates the right side of device  100 . As shown in  FIG. 1D , secondary screen  108  also includes a card slot  132  and a port  136  on its side. Card slot  132  in embodiments, accommodates different types of cards including a subscriber identity module (SIM). Port  136  in embodiments is an input/output port (I/O port) that allows device  100  to be connected to other peripheral devices, such as a display, keyboard, or printing device. As can be appreciated, these are merely some examples and in other embodiments device  100  may include other slots and ports such as slots and ports for accommodating additional memory devices and/or for connecting other peripheral devices. Also shown in  FIG. 1D  is an audio jack  140  that accommodates a tip, ring, sleeve (TRS) connector for example to allow a user to utilize headphones or a headset. 
     Device  100  also includes a number of buttons  158 . For example,  FIG. 1E  illustrates the left side of device  100 . As shown in  FIG. 1E , the side of primary screen  104  includes three buttons  144 ,  148 , and  152 , which can be configured for specific inputs. For example, buttons  144 ,  148 , and  152  may be configured to, in combination or alone, control a number of aspects of device  100 . Some non-limiting examples include overall system power, volume, brightness, vibration, selection of displayed items (on either of screen  104  or  108 ), a camera, a microphone, and initiation/termination of telephone calls. In some embodiments, instead of separate buttons two buttons may be combined into a rocker button. This arrangement is useful in situations where the buttons are configured to control features such as volume or brightness. In addition to buttons  144 ,  148 , and  152 , device  100  also includes a button  156 , shown in  FIG. 1F , which illustrates the top of device  100 . In one embodiment, button  156  is configured as an on/off button used to control overall system power to device  100 . In other embodiments, button  156  is configured to, in addition to or in lieu of controlling system power, control other aspects of device  100 . In some embodiments, one or more of the buttons  144 ,  148 ,  152 , and  156  are capable of supporting different user commands. By way of example, a normal press has a duration commonly of less than about 1 second and resembles a quick tap. A medium press has a duration commonly of 1 second or more but less than about 12 seconds. A long press has a duration commonly of about 12 seconds or more. The function of the buttons is normally specific to the application that is currently in focus on the respective display  110  and  114 . In a telephone application for instance and depending on the particular button, a normal, medium, or long press can mean end call, increase in call volume, decrease in call volume, and toggle microphone mute. In a camera or video application for instance and depending on the particular button, a normal, medium, or long press can mean increase zoom, decrease zoom, and take photograph or record video. 
     There are also a number of hardware components within device  100 . As illustrated in  FIG. 1C , device  100  includes a speaker  160  and a microphone  164 . Device  100  also includes a camera  168  ( FIG. 1B ). Additionally, device  100  includes two position sensors  172 A and  172 B, which are used to determine the relative positions of screens  104  and  108 . In one embodiment, position sensors  172 A and  172 B are Hall effect sensors. However, in other embodiments other sensors can be used in addition to or in lieu of the Hall effect sensors. An accelerometer  176  may also be included as part of device  100  to determine the orientation of the device  100  and/or the orientation of screens  104  and  108 . Additional internal hardware components that may be included in device  100  are described below with respect to  FIG. 2 . 
     The overall design of device  100  allows it to provide additional functionality not available in other communication devices. Some of the functionality is based on the various positions and orientations that device  100  can have. As shown in  FIGS. 1B-1G , device  100  can be operated in an “open” position where screens  104  and  108  are juxtaposed. This position allows a large display area for displaying information to a user. When position sensors  172 A and  172 B determine that device  100  is in the open position, they can generate a signal that can be used to trigger different events such as displaying information on both screens  104  and  108 . Additional events may be triggered if accelerometer  176  determines that device  100  is in a portrait position ( FIG. 1B ) as opposed to a landscape position (not shown). 
     In addition to the open position, device  100  may also have a “closed” position illustrated in  FIG. 1H . Again, position sensors  172 A and  172 B can generate a signal indicating that device  100  is in the “closed” position. This can trigger an event that results in a change of displayed information on screen  104  and/or  108 . For example, device  100  may be programmed to stop displaying information on one of the screens, e.g., screen  108 , since a user can only view one screen at a time when device  100  is in the “closed” position. In other embodiments, the signal generated by position sensors  172 A and  172 B, indicating that the device  100  is in the “closed” position, can trigger device  100  to answer an incoming telephone call. The “closed” position can also be a preferred position for utilizing the device  100  as a mobile phone. 
     Device  100  can also be used in an “easel” position which is illustrated in  FIG. 1I . In the “easel” position, screens  104  and  108  are angled with respect to each other and facing outward with the edges of screens  104  and  108  substantially horizontal. In this position, device  100  can be configured to display information on both screens  104  and  108  to allow two users to simultaneously interact with device  100 . When device  100  is in the “easel” position, sensors  172 A and  172 B generate a signal indicating that the screens  104  and  108  are positioned at an angle to each other, and the accelerometer  176  can generate a signal indicating that device  100  has been placed so that the edge of screens  104  and  108  are substantially horizontal. The signals can then be used in combination to generate events that trigger changes in the display of information on screens  104  and  108 . 
       FIG. 1J  illustrates device  100  in a “modified easel” position. In the “modified easel” position, one of screens  104  or  108  is used as a stand and is faced down on the surface of an object such as a table. This position provides a convenient way for information to be displayed to a user in landscape orientation. Similar to the easel position, when device  100  is in the “modified easel” position, position sensors  172 A and  172 B generate a signal indicating that the screens  104  and  108  are positioned at an angle to each other. The accelerometer  176  would generate a signal indicating that device  100  has been positioned so that one of screens  104  and  108  is faced downwardly and is substantially horizontal. The signals can then be used to generate events that trigger changes in the display of information of screens  104  and  108 . For example, information may not be displayed on the screen that is face down since a user cannot see the screen. 
     Transitional states are also possible. When the position sensors  172 A and B and/or accelerometer indicate that the screens are being closed or folded (from open), a closing transitional state is recognized. Conversely when the position sensors  172 A and B indicate that the screens are being opened or folded (from closed), an opening transitional state is recognized. The closing and opening transitional states are typically time-based, or have a maximum time duration from a sensed starting point. Normally, no user input is possible when one of the closing and opening states is in effect. In this manner, incidental user contact with a screen during the closing or opening function is not misinterpreted as user input. In embodiments, another transitional state is possible when the device  100  is closed. This additional transitional state allows the display to switch from one screen  104  to the second screen  108  when the device  100  is closed based on some user input, e.g., a double tap on the screen  110 , 114 . 
     As can be appreciated, the description of device  100  is made for illustrative purposes only, and the embodiments are not limited to the specific mechanical features shown in  FIGS. 1A-1J  and described above. In other embodiments, device  100  may include additional features, including one or more additional buttons, slots, display areas, hinges, and/or locking mechanisms. Additionally, in embodiments, the features described above may be located in different parts of device  100  and still provide similar functionality. Therefore,  FIGS. 1A-1J  and the description provided above are nonlimiting. 
     Hardware Features: 
       FIG. 2  illustrates components of a device  100  in accordance with embodiments of the present disclosure. In general, the device  100  includes a primary screen  104  and a secondary screen  108 . While the primary screen  104  and its components are normally enabled in both the opened and closed positions or states, the secondary screen  108  and its components are normally enabled in the opened state but disabled in the closed state. However, even when in the closed state a user or application triggered interrupt (such as in response to a phone application or camera application operation) can flip the active screen, or disable the primary screen  104  and enable the secondary screen  108 , by a suitable command. Each screen  104 ,  108  can be touch sensitive and can include different operative areas. For example, a first operative area, within each touch sensitive screen  104  and  108 , may comprise a touch sensitive display  110 ,  114 . In general, the touch sensitive display  110 ,  114  may comprise a full color, touch sensitive display. A second area within each touch sensitive screen  104  and  108  may comprise a gesture capture region  120 ,  124 . The gesture capture region  120 ,  124  may comprise an area or region that is outside of the touch sensitive display  110 ,  114  area, and that is capable of receiving input, for example in the form of gestures provided by a user. However, the gesture capture region  120 ,  124  does not include pixels that can perform a display function or capability. 
     A third region of the touch sensitive screens  104  and  108  may comprise a configurable area  112 ,  116 . The configurable area  112 ,  116  is capable of receiving input and has display or limited display capabilities. In embodiments, the configurable area  112 ,  116  may present different input options to the user. For example, the configurable area  112 ,  116  may display buttons or other relatable items. Moreover, the identity of displayed buttons, or whether any buttons are displayed at all within the configurable area  112 ,  116  of a touch sensitive screen  104  or  108 , may be determined from the context in which the device  100  is used and/or operated. In an exemplary embodiment, the touch sensitive screens  104  and  108  comprise liquid crystal display devices extending across at least those regions of the touch sensitive screens  104  and  108  that are capable of providing visual output to a user, and a capacitive input matrix over those regions of the touch sensitive screens  104  and  108  that are capable of receiving input from the user. 
     One or more display controllers  216   a ,  216   b  may be provided for controlling the operation of the touch sensitive screens  104  and  108 , including input (touch sensing) and output (display) functions. In the exemplary embodiment illustrated in  FIG. 2 , a separate touch screen controller  216   a  or  216   b  is provided for each touch screen  104  and  108 . In accordance with alternate embodiments, a common or shared touch screen controller  216  may be used to control each of the included touch sensitive screens  104  and  108 . In accordance with still other embodiments, the functions of a touch screen controller  216  may be incorporated into other components, such as a processor  204 . 
     The processor  204  may comprise a general purpose programmable processor or controller for executing application programming or instructions. In accordance with at least some embodiments, the processor  204  may include multiple processor cores, and/or implement multiple virtual processors. In accordance with still other embodiments, the processor  204  may include multiple physical processors. As a particular example, the processor  204  may comprise a specially configured application specific integrated circuit (ASIC) or other integrated circuit, a digital signal processor, a controller, a hardwired electronic or logic circuit, a programmable logic device or gate array, a special purpose computer, or the like. The processor  204  generally functions to run programming code or instructions implementing various functions of the device  100 . 
     A communication device  100  can also include an energy storage device manager  280 , such as a battery management system. As will be appreciated, a battery management system is an electronic system that manages a rechargeable battery (cell or battery pack), such as by monitoring its state, calculating secondary data, reporting that data, protecting the battery, controlling the battery&#39;s environment, and/or balancing the battery. In one configuration, the energy storage manager  280  interfaces with various sensors to collect one or more sensed ESD parameters (discussed below). 
     A communication device  100  may also include memory  208  for use in connection with the execution of application programming or instructions by the processor  204 , and for the temporary or long term storage of program instructions and/or data. As examples, the memory  208  may comprise RAM, DRAM, SDRAM, or other solid state memory. Alternatively or in addition, data storage  212  may be provided. Like the memory  208 , the data storage  212  may comprise a solid state memory device or devices. Alternatively or in addition, the data storage  212  may comprise a hard disk drive or other random access memory. 
     In support of communications functions or capabilities, the device  100  can include a cellular telephony module  228 . As examples, the cellular telephony module  228  can comprise a GSM, CDMA, FDMA and/or analog cellular telephony transceiver capable of supporting voice, multimedia and/or data transfers over a cellular network. Alternatively or in addition, the device  100  can include an additional or other wireless communications module  232 . As examples, the other wireless communications module  232  can comprise a Wi-Fi, BLUETOOTH™, WiMax, infrared, or other wireless communications link. The cellular telephony module  228  and the other wireless communications module  232  can each be associated with a shared or a dedicated antenna  224 . 
     A port interface  252  may be included. The port interface  252  may include proprietary or universal ports to support the interconnection of the device  100  to other devices or components, such as a dock, which may or may not include additional or different capabilities from those integral to the device  100 . In addition to supporting an exchange of communication signals between the device  100  and another device or component, the docking port  136  and/or port interface  252  can support the supply of power to or from the device  100 . The port interface  252  also comprises an intelligent element that comprises a docking module for controlling communications or other interactions between the device  100  and a connected device or component. 
     An input/output module  248  and associated ports may be included to support communications over wired networks or links, for example with other communication devices, server devices, and/or peripheral devices. Examples of an input/output module  248  include an Ethernet port, a Universal Serial Bus (USB) port, Institute of Electrical and Electronics Engineers (IEEE) 1394, or other interface. 
     An audio input/output interface/device(s)  244  can be included to provide analog audio to an interconnected speaker or other device, and to receive analog audio input from a connected microphone or other device. As an example, the audio input/output interface/device(s)  244  may comprise an associated amplifier and analog to digital converter. Alternatively or in addition, the device  100  can include an integrated audio input/output device  256  and/or an audio jack for interconnecting an external speaker or microphone. For example, an integrated speaker and an integrated microphone can be provided, to support near talk or speaker phone operations. 
     Hardware buttons  158  can be included for example for use in connection with certain control operations. Examples include a master power switch, volume control, etc., as described in conjunction with  FIGS. 1A through 1J . One or more image capture interfaces/devices  240 , such as a camera, can be included for capturing still and/or video images. Alternatively or in addition, an image capture interface/device  240  can include a scanner or code reader. An image capture interface/device  240  can include or be associated with additional elements, such as a flash or other light source. 
     The device  100  can also include a global positioning system (GPS) receiver  236 . In accordance with embodiments of the present invention, the GPS receiver  236  may further comprise a GPS module that is capable of providing absolute location information to other components of the device  100 . An accelerometer(s)  176  may also be included. For example, in connection with the display of information to a user and/or other functions, a signal from the accelerometer  176  can be used to determine an orientation and/or format in which to display that information to the user. 
     Embodiments of the present invention can also include one or more position sensor(s)  172 . The position sensor  172  can provide a signal indicating the position of the touch sensitive screens  104  and  108  relative to one another. This information can be provided as an input, for example to a user interface application, to determine an operating mode, characteristics of the touch sensitive displays  110 ,  114 , and/or other device  100  operations. As examples, a screen position sensor  172  can comprise a series of Hall effect sensors, a multiple position switch, an optical switch, a Wheatstone bridge, a potentiometer, or other arrangement capable of providing a signal indicating of multiple relative positions the touch screens are in. 
     Communications between various components of the device  100  can be carried by one or more buses  222 . In addition, power can be supplied to the components of the device  100  from a power source and/or power control module  260 . The power control module  260  can, for example, include a battery, an AC to DC converter, power control logic, and/or ports for interconnecting the device  100  to an external source of power. 
     Device State: 
       FIGS. 3A and 3B  represent illustrative states of device  100 . While a number of illustrative states are shown, and transitions from a first state to a second state, it is to be appreciated that the illustrative state diagram may not encompass all possible states and/or all possible transitions from a first state to a second state. As illustrated in  FIG. 3 , the various arrows between the states (illustrated by the state represented in the circle) represent a physical change that occurs to the device  100 , that is detected by one or more of hardware and software, the detection triggering one or more of a hardware and/or software interrupt that is used to control and/or manage one or more functions of device  100 . 
     As illustrated in  FIG. 3A , there are twelve exemplary “physical” states: closed  304 , transition  308  (or opening transitional state), easel  312 , modified easel  316 , open  320 , inbound/outbound call or communication  324 , image/video capture  328 , transition  332  (or closing transitional state), landscape  340 , docked  336 , docked  344  and landscape  348 . Next to each illustrative state is a representation of the physical state of the device  100  with the exception of states  324  and  328 , where the state is generally symbolized by the international icon for a telephone and the icon for a camera, respectfully. 
     In state  304 , the device is in a closed state with the device  100  generally oriented in the portrait direction with the primary screen  104  and the secondary screen  108  back-to-back in different planes (see  FIG. 1H ). From the closed state, the device  100  can enter, for example, docked state  336 , where the device  100  is coupled with a docking station, docking cable, or in general docked or associated with one or more other devices or peripherals, or the landscape state  340 , where the device  100  is generally oriented with the primary screen  104  facing the user, and the primary screen  104  and the secondary screen  108  being back-to-back. 
     In the closed state, the device can also move to a transitional state where the device remains closed by the display is moved from one screen  104  to another screen  108  based on a user input, e.g., a double tap on the screen  110 ,  114 . Still another embodiment includes a bilateral state. In the bilateral state, the device remains closed, but a single application displays at least one window on both the first display  110  and the second display  114 . The windows shown on the first and second display  110 ,  114  may be the same or different based on the application and the state of that application. For example, while acquiring an image with a camera, the device may display the view finder on the first display  110  and displays a preview for the photo subjects (full screen and mirrored left-to-right) on the second display  114 . 
     In state  308 , a transition state from the closed state  304  to the semi-open state or easel state  312 , the device  100  is shown opening with the primary screen  104  and the secondary screen  108  being rotated around a point of axis coincidence with the hinge. Upon entering the easel state  312 , the primary screen  104  and the secondary screen  108  are separated from one another such that, for example, the device  100  can sit in an easel-like configuration on a surface. 
     In state  316 , known as the modified easel position, the device  100  has the primary screen  104  and the secondary screen  108  in a similar relative relationship to one another as in the easel state  312 , with the difference being one of the primary screen  104  or the secondary screen  108  are placed on a surface as shown. 
     State  320  is the open state where the primary screen  104  and the secondary screen  108  are generally on the same plane. From the open state, the device  100  can transition to the docked state  344  or the open landscape state  348 . In the open state  320 , the primary screen  104  and the secondary screen  108  are generally in the portrait-like orientation while in landscaped state  348  the primary screen  104  and the secondary screen  108  are generally in a landscape-like orientation. 
     State  324  is illustrative of a communication state, such as when an inbound or outbound call is being received or placed, respectively, by the device  100 . While not illustrated for clarity, it should be appreciated the device  100  can transition to the inbound/outbound call state  324  from any state illustrated in  FIG. 3 . In a similar manner, the image/video capture state  328  can be entered into from any other state in  FIG. 3 , with the image/video capture state  328  allowing the device  100  to take one or more images via a camera and/or videos with a video capture device  240 . 
     Transition state  322  illustratively shows primary screen  104  and the secondary screen  108  being closed upon one another for entry into, for example, the closed state  304 . 
       FIG. 3B  illustrates, with reference to the key, the inputs that are received to detect a transition from a first state to a second state. In  FIG. 3B , various combinations of states are shown with in general, a portion of the columns being directed toward a portrait state  352 , a landscape state  356 , and a portion of the rows being directed to portrait state  360  and landscape state  364 . 
     In  FIG. 3B , the Key indicates that “H” represents an input from one or more Hall Effect sensors, “A” represents an input from one or more accelerometers, “T” represents an input from a timer, “P” represents a communications trigger input and “I” represents an image and/or video capture request input. Thus, in the center portion  376  of the chart, an input, or combination of inputs, are shown that represent how the device  100  detects a transition from a first physical state to a second physical state. 
     As discussed, in the center portion of the chart  376 , the inputs that are received enable the detection of a transition from, for example, a portrait open state to a landscape easel state—shown in bold—“HAT.” For this exemplary transition from the portrait open to the landscape easel state, a Hall Effect sensor (“H”), an accelerometer (“A”) and a timer (“T”) input may be needed. The timer input can be derived from, for example, a clock associated with the processor. 
     In addition to the portrait and landscape states, a docked state  368  is also shown that is triggered based on the receipt of a docking signal  372 . As discussed above and in relation to  FIG. 3 , the docking signal can be triggered by the association of the device  100  with one or more other device  100   s , accessories, peripherals, smart docks, or the like. 
     User Interaction: 
       FIGS. 4A through 4H  depict various graphical representations of gesture inputs that may be recognized by the screens  104 ,  108 . The gestures may be performed not only by a user&#39;s body part, such as a digit, but also by other devices, such as a stylus, that may be sensed by the contact sensing portion(s) of a screen  104 ,  108 . In general, gestures are interpreted differently, based on where the gestures are performed (either directly on the display  110 ,  114  or in the gesture capture region  120 ,  124 ). For example, gestures in the display  110 , 114  may be directed to a desktop or application, and gestures in the gesture capture region  120 ,  124  may be interpreted as for the system. 
     With reference to  FIGS. 4A-4H , a first type of gesture, a touch gesture  420 , is substantially stationary on the screen  104 , 108  for a selected length of time. A circle  428  represents a touch or other contact type received at particular location of a contact sensing portion of the screen. The circle  428  may include a border  432 , the thickness of which indicates a length of time that the contact is held substantially stationary at the contact location. For instance, a tap  420  (or short press) has a thinner border  432   a  than the border  432   b  for a long press  424  (or for a normal press). The long press  424  may involve a contact that remains substantially stationary on the screen for longer time period than that of a tap  420 . As will be appreciated, differently defined gestures may be registered depending upon the length of time that the touch remains stationary prior to contact cessation or movement on the screen. 
     With reference to  FIG. 4C , a drag gesture  400  on the screen  104 , 108  is an initial contact (represented by circle  428 ) with contact movement  436  in a selected direction. The initial contact  428  may remain stationary on the screen  104 , 108  for a certain amount of time represented by the border  432 . The drag gesture typically requires the user to contact an icon, window, or other displayed image at a first location followed by movement of the contact in a drag direction to a new second location desired for the selected displayed image. The contact movement need not be in a straight line but have any path of movement so long as the contact is substantially continuous from the first to the second locations. 
     With reference to  FIG. 4D , a flick gesture  404  on the screen  104 , 108  is an initial contact (represented by circle  428 ) with truncated contact movement  436  (relative to a drag gesture) in a selected direction. In embodiments, a flick has a higher exit velocity for the last movement in the gesture compared to the drag gesture. The flick gesture can, for instance, be a finger snap following initial contact. Compared to a drag gesture, a flick gesture generally does not require continual contact with the screen  104 , 108  from the first location of a displayed image to a predetermined second location. The contacted displayed image is moved by the flick gesture in the direction of the flick gesture to the predetermined second location. Although both gestures commonly can move a displayed image from a first location to a second location, the temporal duration and distance of travel of the contact on the screen is generally less for a flick than for a drag gesture. 
     With reference to  FIG. 4E , a pinch gesture  408  on the screen  104 , 108  is depicted. The pinch gesture  408  may be initiated by a first contact  428   a  to the screen  104 , 108  by, for example, a first digit and a second contact  428   b  to the screen  104 , 108  by, for example, a second digit. The first and second contacts  428   a,b  may be detected by a common contact sensing portion of a common screen  104 , 108 , by different contact sensing portions of a common screen  104  or  108 , or by different contact sensing portions of different screens. The first contact  428   a  is held for a first amount of time, as represented by the border  432   a , and the second contact  428   b  is held for a second amount of time, as represented by the border  432   b . The first and second amounts of time are generally substantially the same, and the first and second contacts  428   a, b  generally occur substantially simultaneously. The first and second contacts  428   a, b  generally also include corresponding first and second contact movements  436   a, b , respectively. The first and second contact movements  436   a, b  are generally in opposing directions. Stated another way, the first contact movement  436   a  is towards the second contact  436   b , and the second contact movement  436   b  is towards the first contact  436   a . More simply stated, the pinch gesture  408  may be accomplished by a user&#39;s digits touching the screen  104 , 108  in a pinching motion. 
     With reference to  FIG. 4F , a spread gesture  410  on the screen  104 , 108  is depicted. The spread gesture  410  may be initiated by a first contact  428   a  to the screen  104 , 108  by, for example, a first digit and a second contact  428   b  to the screen  104 , 108  by, for example, a second digit. The first and second contacts  428   a,b  may be detected by a common contact sensing portion of a common screen  104 , 108 , by different contact sensing portions of a common screen  104 , 108 , or by different contact sensing portions of different screens. The first contact  428   a  is held for a first amount of time, as represented by the border  432   a , and the second contact  428   b  is held for a second amount of time, as represented by the border  432   b . The first and second amounts of time are generally substantially the same, and the first and second contacts  428   a, b  generally occur substantially simultaneously. The first and second contacts  428   a, b  generally also include corresponding first and second contact movements  436   a, b , respectively. The first and second contact movements  436   a, b  are generally in a common direction. Stated another way, the first and second contact movements  436   a, b  are away from the first and second contacts  428   a, b . More simply stated, the spread gesture  410  may be accomplished by a user&#39;s digits touching the screen  104 , 108  in a spreading motion. 
     The above gestures may be combined in any manner, such as those shown by  FIGS. 4G and 4H , to produce a determined functional result. For example, in  FIG. 4G  a tap gesture  420  is combined with a drag or flick gesture  412  in a direction away from the tap gesture  420 . In FIG.  4 H, a tap gesture  420  is combined with a drag or flick gesture  412  in a direction towards the tap gesture  420 . 
     The functional result of receiving a gesture can vary depending on a number of factors, including a state of the device  100 , display  110 ,  114 , or screen  104 ,  108 , a context associated with the gesture, or sensed location of the gesture. The state of the device commonly refers to one or more of a configuration of the device  100 , a display orientation, and user and other inputs received by the device  100 . Context commonly refers to one or more of the particular application(s) selected by the gesture and the portion(s) of the application currently executing, whether the application is a single- or multi-screen application, and whether the application is a multi-screen application displaying one or more windows in one or more screens or in one or more stacks. Sensed location of the gesture commonly refers to whether the sensed set(s) of gesture location coordinates are on a touch sensitive display  110 ,  114  or a gesture capture region  120 ,  124 , whether the sensed set(s) of gesture location coordinates are associated with a common or different display or screen  104 , 108 , and/or what portion of the gesture capture region contains the sensed set(s) of gesture location coordinates. 
     A tap, when received by an a touch sensitive display  110 ,  114 , can be used, for instance, to select an icon to initiate or terminate execution of a corresponding application, to maximize or minimize a window, to reorder windows in a stack, and to provide user input such as by keyboard display or other displayed image. A drag, when received by a touch sensitive display  110 ,  114 , can be used, for instance, to relocate an icon or window to a desired location within a display, to reorder a stack on a display, or to span both displays (such that the selected window occupies a portion of each display simultaneously). A flick, when received by a touch sensitive display  110 ,  114  or a gesture capture region  120 ,  124 , can be used to relocate a window from a first display to a second display or to span both displays (such that the selected window occupies a portion of each display simultaneously). Unlike the drag gesture, however, the flick gesture is generally not used to move the displayed image to a specific user-selected location but to a default location that is not configurable by the user. 
     The pinch gesture, when received by a touch sensitive display  110 ,  114  or a gesture capture region  120 ,  124 , can be used to minimize or otherwise increase the displayed area or size of a window (typically when received entirely by a common display), to switch windows displayed at the top of the stack on each display to the top of the stack of the other display (typically when received by different displays or screens), or to display an application manager (a “pop-up window” that displays the windows in the stack). The spread gesture, when received by a touch sensitive display  110 ,  114  or a gesture capture region  120 ,  124 , can be used to maximize or otherwise decrease the displayed area or size of a window, to switch windows displayed at the top of the stack on each display to the top of the stack of the other display (typically when received by different displays or screens), or to display an application manager (typically when received by an off-screen gesture capture region on the same or different screens). 
     The combined gestures of  FIG. 4G , when received by a common display capture region in a common display or screen  104 , 108 , can be used to hold a first window stack location in a first stack constant for a display receiving the gesture while reordering a second window stack location in a second window stack to include a window in the display receiving the gesture. The combined gestures of  FIG. 4H , when received by different display capture regions in a common display or screen  104 , 108  or in different displays or screens, can be used to hold a first window stack location in a first window stack constant for a display receiving the tap part of the gesture while reordering a second window stack location in a second window stack to include a window in the display receiving the flick or drag gesture. Although specific gestures and gesture capture regions in the preceding examples have been associated with corresponding sets of functional results, it is to be appreciated that these associations can be redefined in any manner to produce differing associations between gestures and/or gesture capture regions and/or functional results. 
     Firmware and Software: 
     With reference to  FIG. 5A , the memory  208  may store and the processor  204  may execute one or more software components. These components can include at least one operating system (OS)  516 , an application manager  562 , a desktop  566 , and/or one or more applications  564   a  and/or  564   b  from an application store  560 . The OS  516  can include a framework  520 , one or more frame buffers  548 , one or more drivers  512 , previously described in conjunction with  FIG. 2 , and/or a kernel  518 . The OS  516  can be any software, consisting of programs and data, which manages computer hardware resources and provides common services for the execution of various applications  564 . The OS  516  can be any operating system and, at least in some embodiments, dedicated to mobile devices, including, but not limited to, Linux, ANDROID™, iPhone OS (IOS™), WINDOWS PHONE 7™, etc. The OS  516  is operable to provide functionality to the phone by executing one or more operations, as described herein. 
     The applications  564  can be any higher level software that executes particular functionality for the user. Applications  564  can include programs such as email clients, web browsers, texting applications, games, media players, office suites, etc. The applications  564  can be stored in an application store  560 , which may represent any memory or data storage, and the management software associated therewith, for storing the applications  564 . Once executed, the applications  564  may be run in a different area of memory  208 . 
     The data output of the applications  564  to be processed by the framework  520  can take many forms, whether text, audio, video, or multimedia. In one configuration, the media output is a digital image, typically of a vector or raster type, which are typically bitmap or pixmap images, or a combination thereof. Vector images comprise plural vectors, each vector being a point having both direction and length. Raster images have a finite set or grid of digital values called picture elements or pixels. Each pixel has a corresponding value representing a brightness of a given color at a respective point in an image to be rendered by the display. Pixels are generally stored in memory as a raster image or raster map, which is commonly a two-dimensional array of small integers, which values are frequently transmitted or stored in a compressed form using a lossless or lossy compression algorithm. 
     The image file can have any of a variety of formats. Vector formats include CGM, Gerber format (RS-274×), SVG, and other 2 and 3-dimensional vector formats. Raster formats include JPEG/JFIF, JPEG 2000, Exif, TIFF, RAW, PNG, GIF, BMP, PPM, PGM, PBM, PNM, WEBP, and others. Other formats include compound formats, such as Metafile formats, stereo formats, page description language formats (or formats used to describe the layout of a printed page containing text, objects, and images), and other formats apparent to those of ordinary skill in the art. 
     The framework  520  may be any software or data that allows the multiple tasks running on the device to interact. In embodiments, at least portions of the framework  520  and the discrete components described hereinafter may be considered part of the OS  516  or an application  564 . However, these portions will be described as part of the framework  520 , but those components are not so limited. The framework  520  can include, but is not limited to, a Multi-Display Management (MDM) module  524 , a Surface Cache module  528 , a Window Management module  532 , an Input Management module  536 , a Task Management module  540 , an Application Model Manager  542 , a Display Controller, one or more frame buffers  548 , a task stack  552 , one or more window stacks  550  (which is a logical arrangement of windows and/or desktops in a display area), and/or an event buffer  556 . 
     The MDM module  524  includes one or more modules that are operable to manage the display of applications or other data on the screens of the device. An embodiment of the MDM module  524  is described in conjunction with  FIG. 5B . In embodiments, the MDM module  524  receives inputs from the other OS  516  components, such as, the drivers  512 , and from the applications  564  to determine continually the state of the device  100 . The inputs assist the MDM module  524  in determining how to configure and allocate the displays according to the application&#39;s preferences and requirements, and the user&#39;s actions. Once a determination for display configurations is made, the MDM module  524  can bind the applications  564  to a display. The configuration may then be provided to one or more other components to generate a window with a display. 
     The Surface Cache module  528  includes any memory or storage and the software associated therewith to store or cache one or more images of windows. A series of active and/or non-active windows (or other display objects, such as, a desktop display) can be associated with each display. An active window (or other display object) is currently displayed. A non-active windows (or other display objects) were opened and, at some time, displayed but are now not displayed. To enhance the user experience, before a window transitions from an active state to an inactive state, a “screen shot” of a last generated image of the window (or other display object) can be stored. The Surface Cache module  528  may be operable to store a bitmap of the last active image of a window (or other display object) not currently displayed. Thus, the Surface Cache module  528  stores the images of non-active windows (or other display objects) in a data store. 
     In embodiments, the Window Management module  532  is operable to manage the windows (or other display objects) that are active or not active on each of the displays. The Window Management module  532 , based on information from the MDM module  524 , the OS  516 , or other components, determines when a window (or other display object) is visible or not active. The Window Management module  532  may then put a non-visible window (or other display object) in a “not active state” and, in conjunction with the Task Management module Task Management  540  suspends the application&#39;s operation. Further, the Window Management module  532  may assign, through collaborative interaction with the MDM module  524 , a display identifier to the window (or other display object) or manage one or more other items of data associated with the window (or other display object). The Window Management module  532  may also provide the stored information to the application  564 , the Task Management module  540 , or other components interacting with or associated with the window (or other display object). The Window Management module  532  can also associate an input task with a window based on window focus and display coordinates within the motion space. 
     The Input Management module  536  is operable to manage events that occur with the device. An event is any input into the window environment, for example, a user interface interactions with a user. The Input Management module  536  receives the events and logically stores the events in an event buffer  556 . Events can include such user interface interactions as a “down event,” which occurs when a screen  104 ,  108  receives a touch signal from a user, a “move event,” which occurs when the screen  104 ,  108  determines that a user&#39;s finger is moving across a screen(s), an “up event, which occurs when the screen  104 ,  108  determines that the user has stopped touching the screen  104 ,  108 , etc. These events are received, stored, and forwarded to other modules by the Input Management module  536 . The Input Management module  536  may also map screen inputs to a motion space which is the culmination of all physical and virtual display available on the device. 
     The motion space is a virtualized space that includes all touch sensitive displays  110 , 114  “tiled” together to mimic the physical dimensions of the device  100 . For example, when the device  100  is unfolded, the motion space size may be 960×800, which may be the number of pixels in the combined display area for both touch sensitive displays  110 ,  114 . If a user touches on a first touch sensitive display  110  on location ( 40 ,  40 ), a full screen window can receive touch event with location ( 40 ,  40 ). If a user touches on a second touch sensitive display  114 , with location ( 40 ,  40 ), the full screen window can receive touch event with location ( 520 ,  40 ), because the second touch sensitive display  114  is on the right side of the first touch sensitive display  110 , so the device  100  can offset the touch by the first touch sensitive display&#39;s  110  width, which is 480 pixels. When a hardware event occurs with location info from a driver  512 , the framework  520  can up-scale the physical location to the motion space because the location of the event may be different based on the device orientation and state. The motion space may be as described in U.S. patent application Ser. No. 13/187,026, filed Jul. 20, 2011, entitled “Systems and Methods for Receiving Gesture Inputs Spanning Multiple Input Devices,” which is hereby incorporated by reference in its entirety for all that it teaches and for all purposes. 
     A task can be an application and a sub-task can be an application component that provides a window with which users can interact to do something, such as dial the phone, take a photo, send an email, or view a map. Each task may be given a window in which to draw a user interface. The window typically fills a display (for example, touch sensitive display  110 , 114 ), but may be smaller than the display  110 , 114  and float on top of other windows. An application usually consists of multiple sub-tasks that are loosely bound to each other. Typically, one task in an application is specified as the “main” task, which is presented to the user when launching the application for the first time. Each task can then start another task or sub-task to perform different actions. 
     The Task Management module  540  is operable to manage the operation of one or more applications  564  that may be executed by the device. Thus, the Task Management module  540  can receive signals to launch, suspend, terminate, etc. an application or application sub-tasks stored in the application store  560 . The Task Management module  540  may then instantiate one or more tasks or sub-tasks of the application  564  to begin operation of the application  564 . Further, the Task Management Module  540  may launch, suspend, or terminate a task or sub-task as a result of user input or as a result of a signal from a collaborating framework  520  component. The Task Management Module  540  is responsible for managing the lifecycle of applications (tasks and sub-task) from when the application is launched to when the application is terminated. 
     The processing of the Task Management Module  540  is facilitated by a task stack  552 , which is a logical structure associated with the Task Management Module  540 . The task stack  552  maintains the state of all tasks and sub-tasks on the device  100 . When some component of the operating system  516  requires a task or sub-task to transition in its lifecycle, the OS  516  component can notify the Task Management Module  540 . The Task Management Module  540  may then locate the task or sub-task, using identification information, in the task stack  552 , and send a signal to the task or sub-task indicating what kind of lifecycle transition the task needs to execute. Informing the task or sub-task of the transition allows the task or sub-task to prepare for the lifecycle state transition. The Task Management Module  540  can then execute the state transition for the task or sub-task. In embodiments, the state transition may entail triggering the OS kernel  518  to terminate the task when termination is required. 
     Further, the Task Management module  540  may suspend the application  564  based on information from the Window Management Module  532 . Suspending the application  564  may maintain application data in memory but may limit or stop the application  564  from rendering a window or user interface. Once the application becomes active again, the Task Management module  540  can again trigger the application to render its user interface. In embodiments, if a task is suspended, the task may save the task&#39;s state in case the task is terminated. In the suspended state, the application task may not receive input because the application window is not visible to the user. 
     The frame buffer  548  is a logical structure(s) used to render the user interface. The frame buffer  548  can be created and destroyed by the OS kernel  518 . However, the Display Controller  544  can write the image data, for the visible windows, into the frame buffer  548 . A frame buffer  548  can be associated with one screen or multiple screens. The association of a frame buffer  548  with a screen can be controlled dynamically by interaction with the OS kernel  518 . A composite display may be created by associating multiple screens with a single frame buffer  548 . Graphical data used to render an application&#39;s window user interface may then be written to the single frame buffer  548 , for the composite display, which is output to the multiple screens  104 , 108 . The Display Controller  544  can direct an application&#39;s user interface to a portion of the frame buffer  548  that is mapped to a particular display  110 , 114 , thus, displaying the user interface on only one screen  104  or  108 . The Display Controller  544  can extend the control over user interfaces to multiple applications, controlling the user interfaces for as many displays as are associated with a frame buffer  548  or a portion thereof. This approach compensates for the multiple physical screens  104 , 108  that are in use by the software component above the Display Controller  544 . 
     The Application Manager  562  is an application that provides a presentation layer for the window environment. Thus, the Application Manager  562  provides the graphical model for rendering by the Task Management Module  540 . Likewise, the Desktop  566  provides the presentation layer for the Application Store  560 . Thus, the desktop provides a graphical model of a surface having selectable application icons for the Applications  564  in the Application Store  560  that can be provided to the Window Management Module  556  for rendering. 
     Further, the framework can include an Application Model Manager (AMM)  542 . The Application Manager  562  may interface with the AMM  542 . In embodiments, the AMM  542  receives state change information from the device  100  regarding the state of applications (which are running or suspended). The AMM  542  can associate bit map images from the Surface Cache Module  528  to the tasks that are alive (running or suspended). Further, the AMM  542  can convert the logical window stack maintained in the Task Manager Module  540  to a linear (“film strip” or “deck of cards”) organization that the user perceives when the using the off gesture capture area  120  to sort through the windows. Further, the AMM  542  may provide a list of executing applications to the Application Manager  562 . 
     An embodiment of the MDM module  524  is shown in  FIG. 5B . The MDM module  524  is operable to determine the state of the environment for the device, including, but not limited to, the orientation of the device, whether the device  100  is opened or closed, what applications  564  are executing, how the applications  564  are to be displayed, what actions the user is conducting, the tasks being displayed, etc. To configure the display, the MDM module  524  interprets these environmental factors and determines a display configuration, as described in conjunction with  FIGS. 6A-6J . Then, the MDM module  524  can bind the applications  564  or other device components to the displays. The configuration may then be sent to the Display Controller  544  and/or the other components within the OS  516  to generate the display. The MDM module  524  can include one or more of, but is not limited to, a Display Configuration Module  568 , a Preferences Module  572 , a Device State Module  574 , a Gesture Module  576 , a Requirements Module  580 , an Event Module  584 , and/or a Binding Module  588 . 
     The Display Configuration Module  568  determines the layout for the display. In embodiments, the Display Configuration Module  568  can determine the environmental factors. The environmental factors may be received from one or more other MDM modules  524  or from other sources. The Display Configuration Module  568  can then determine from the list of factors the best configuration for the display. Some embodiments of the possible configurations and the factors associated therewith are described in conjunction with  FIGS. 6A-6F . 
     The Preferences Module  572  is operable to determine display preferences for an application  564  or other component. For example, an application can have a preference for Single or Dual displays. The Preferences Module  572  can determine an application&#39;s display preference (e.g., by inspecting the application&#39;s preference settings) and may allow the application  564  to change to a mode (e.g., single screen, dual screen, max, etc.) if the device  100  is in a state that can accommodate the preferred mode. However, some user interface policies may disallow a mode even if the mode is available. As the configuration of the device changes, the preferences may be reviewed to determine if a better display configuration can be achieved for an application  564 . 
     The Device State Module  574  is operable to determine or receive the state of the device. The state of the device can be as described in conjunction with  FIGS. 3A and 3B . The state of the device can be used by the Display Configuration Module  568  to determine the configuration for the display. As such, the Device State Module  574  may receive inputs and interpret the state of the device. The state information is then provided to the Display Configuration Module  568 . 
     The Gesture Module  576  is shown as part of the MDM module  524 , but, in embodiments, the Gesture module  576  may be a separate Framework  520  component that is separate from the MDM module  524 . In embodiments, the Gesture Module  576  is operable to determine if the user is conducting any actions on any part of the user interface. In alternative embodiments, the Gesture Module  576  receives user interface actions from the configurable area  112 , 116  only. The Gesture Module  576  can receive touch events that occur on the configurable area  112 , 116  (or possibly other user interface areas) by way of the Input Management Module  536  and may interpret the touch events (using direction, speed, distance, duration, and various other parameters) to determine what kind of gesture the user is performing. When a gesture is interpreted, the Gesture Module  576  can initiate the processing of the gesture and, by collaborating with other Framework  520  components, can manage the required window animation. The Gesture Module  576  collaborates with the Application Model Manager  542  to collect state information with respect to which applications are running (active or paused) and the order in which applications must appear when a user gesture is performed. The Gesture Module  576  may also receive references to bitmaps (from the Surface Cache Module  528 ) and live windows so that when a gesture occurs it can instruct the Display Controller  544  how to move the window(s) across the display  110 , 114 . Thus, suspended applications may appear to be running when those windows are moved across the display  110 , 114 . 
     Further, the Gesture Module  576  can receive task information either from the Task Manage Module  540  or the Input Management module  536 . The gestures may be as defined in conjunction with  FIGS. 4A through 4H . For example, moving a window causes the display to render a series of display frames that illustrate the window moving. The gesture associated with such user interface interaction can be received and interpreted by the Gesture Module  576 . The information about the user gesture is then sent to the Task Management Module  540  to modify the display binding of the task. 
     The Requirements Module  580 , similar to the Preferences Module  572 , is operable to determine display requirements for an application  564  or other component. An application can have a set display requirement that must be observed. Some applications require a particular display orientation. For example, the application “Angry Birds” can only be displayed in landscape orientation. This type of display requirement can be determined or received, by the Requirements Module  580 . As the orientation of the device changes, the Requirements Module  580  can reassert the display requirements for the application  564 . The Display Configuration Module  568  can generate a display configuration that is in accordance with the application display requirements, as provided by the Requirements Module  580 . 
     The Event Module  584 , similar to the Gesture Module  576 , is operable to determine one or more events occurring with an application or other component that can affect the user interface. Thus, the Event Module  584  can receive event information either from the event buffer  556  or the Task Management module  540 . These events can change how the tasks are bound to the displays. The Event Module  584  can collect state change information from other Framework  520  components and act upon that state change information. In an example, when the phone is opened or closed or when an orientation change has occurred, a new message may be rendered in a secondary screen. The state change based on the event can be received and interpreted by the Event Module  584 . The information about the events then may be sent to the Display Configuration Module  568  to modify the configuration of the display. 
     The Binding Module  588  is operable to bind the applications  564  or the other components to the configuration determined by the Display Configuration Module  568 . A binding associates, in memory, the display configuration for each application with the display and mode of the application. Thus, the Binding Module  588  can associate an application with a display configuration for the application (e.g. landscape, portrait, multi-screen, etc.). Then, the Binding Module  588  may assign a display identifier to the display. The display identifier associated the application with a particular display of the device  100 . This binding is then stored and provided to the Display Controller  544 , the other components of the OS  516 , or other components to properly render the display. The binding is dynamic and can change or be updated based on configuration changes associated with events, gestures, state changes, application preferences or requirements, etc. 
     The power management module  592 , based on input from the energy storage device (“ESD”) manager (“ESDM”)  280 , interacts with other components of the framework  520  to control system operations to conserve power and prolong the life of the energy storage device (e.g., battery). For example and as discussed in more detail below, the power management module  592 , based on one or more of monitored ESD state, ESDM calculated secondary data, ESD sensed power parameters, and other factors controls application and/or display operations (hereinafter referred to individually and collectively as “sensed ESD parameter(s)”). 
     User Interface Configurations: 
     With reference now to  FIGS. 6A-J , various types of output configurations made possible by the device  100  will be described hereinafter. 
       FIGS. 6A and 6B  depict two different output configurations of the device  100  being in a first state. Specifically,  FIG. 6A  depicts the device  100  being in a closed portrait state  304  where the data is displayed on the primary screen  104 . In this example, the device  100  displays data via the touch sensitive display  110  in a first portrait configuration  604 . As can be appreciated, the first portrait configuration  604  may only display a desktop or operating system home screen. Alternatively, one or more windows may be presented in a portrait orientation while the device  100  is displaying data in the first portrait configuration  604 . 
       FIG. 6B  depicts the device  100  still being in the closed portrait state  304 , but instead data is displayed on the secondary screen  108 . In this example, the device  100  displays data via the touch sensitive display  114  in a second portrait configuration  608 . 
     It may be possible to display similar or different data in either the first or second portrait configuration  604 ,  608 . It may also be possible to transition between the first portrait configuration  604  and second portrait configuration  608  by providing the device  100  a user gesture (e.g., a double tap gesture), a menu selection, or other means. Other suitable gestures may also be employed to transition between configurations. Furthermore, it may also be possible to transition the device  100  from the first or second portrait configuration  604 ,  608  to any other configuration described herein depending upon which state the device  100  is moved. 
     An alternative output configuration may be accommodated by the device  100  being in a second state. Specifically,  FIG. 6C  depicts a third portrait configuration where data is displayed simultaneously on both the primary screen  104  and the secondary screen  108 . The third portrait configuration may be referred to as a Dual-Portrait (PD) output configuration. In the PD output configuration, the touch sensitive display  110  of the primary screen  104  depicts data in the first portrait configuration  604  while the touch sensitive display  114  of the secondary screen  108  depicts data in the second portrait configuration  608 . The simultaneous presentation of the first portrait configuration  604  and the second portrait configuration  608  may occur when the device  100  is in an open portrait state  320 . In this configuration, the device  100  may display one application window in one display  110  or  114 , two application windows (one in each display  110  and  114 ), one application window and one desktop, or one desktop. Other configurations may be possible. It should be appreciated that it may also be possible to transition the device  100  from the simultaneous display of configurations  604 ,  608  to any other configuration described herein depending upon which state the device  100  is moved. Furthermore, while in this state, an application&#39;s display preference may place the device into bilateral mode, in which both displays are active to display different windows in the same application. For example, a Camera application may display a viewfinder and controls on one side, while the other side displays a mirrored preview that can be seen by the photo subjects. Games involving simultaneous play by two players may also take advantage of bilateral mode. 
       FIGS. 6D and 6E  depicts two further output configurations of the device  100  being in a third state. Specifically,  FIG. 6D  depicts the device  100  being in a closed landscape state  340  where the data is displayed on the primary screen  104 . In this example, the device  100  displays data via the touch sensitive display  110  in a first landscape configuration  612 . Much like the other configurations described herein, the first landscape configuration  612  may display a desktop, a home screen, one or more windows displaying application data, or the like. 
       FIG. 6E  depicts the device  100  still being in the closed landscape state  340 , but instead data is displayed on the secondary screen  108 . In this example, the device  100  displays data via the touch sensitive display  114  in a second landscape configuration  616 . It may be possible to display similar or different data in either the first or second portrait configuration  612 ,  616 . It may also be possible to transition between the first landscape configuration  612  and second landscape configuration  616  by providing the device  100  with one or both of a twist and tap gesture or a flip and slide gesture. Other suitable gestures may also be employed to transition between configurations. Furthermore, it may also be possible to transition the device  100  from the first or second landscape configuration  612 ,  616  to any other configuration described herein depending upon which state the device  100  is moved. 
       FIG. 6F  depicts a third landscape configuration where data is displayed simultaneously on both the primary screen  104  and the secondary screen  108 . The third landscape configuration may be referred to as a Dual-Landscape (LD) output configuration. In the LD output configuration, the touch sensitive display  110  of the primary screen  104  depicts data in the first landscape configuration  612  while the touch sensitive display  114  of the secondary screen  108  depicts data in the second landscape configuration  616 . The simultaneous presentation of the first landscape configuration  612  and the second landscape configuration  616  may occur when the device  100  is in an open landscape state  340 . It should be appreciated that it may also be possible to transition the device  100  from the simultaneous display of configurations  612 ,  616  to any other configuration described herein depending upon which state the device  100  is moved. 
       FIGS. 6G and 6H  depict two views of a device  100  being in yet another state. Specifically, the device  100  is depicted as being in an easel state  312 .  FIG. 6G  shows that a first easel output configuration  618  may be displayed on the touch sensitive display  110 .  FIG. 6H  shows that a second easel output configuration  620  may be displayed on the touch sensitive display  114 . The device  100  may be configured to depict either the first easel output configuration  618  or the second easel output configuration  620  individually. Alternatively, both the easel output configurations  618 ,  620  may be presented simultaneously. In some embodiments, the easel output configurations  618 ,  620  may be similar or identical to the landscape output configurations  612 ,  616 . The device  100  may also be configured to display one or both of the easel output configurations  618 ,  620  while in a modified easel state  316 . It should be appreciated that simultaneous utilization of the easel output configurations  618 ,  620  may facilitate two-person games (e.g., Battleship®, chess, checkers, etc.), multi-user conferences where two or more users share the same device  100 , and other applications. As can be appreciated, it may also be possible to transition the device  100  from the display of one or both configurations  618 ,  620  to any other configuration described herein depending upon which state the device  100  is moved. 
       FIG. 6I  depicts yet another output configuration that may be accommodated while the device  100  is in an open portrait state  320 . Specifically, the device  100  may be configured to present a single continuous image across both touch sensitive displays  110 ,  114  in a portrait configuration referred to herein as a Portrait-Max (PMax) configuration  624 . In this configuration, data (e.g., a single image, application, window, icon, video, etc.) may be split and displayed partially on one of the touch sensitive displays while the other portion of the data is displayed on the other touch sensitive display. The Pmax configuration  624  may facilitate a larger display and/or better resolution for displaying a particular image on the device  100 . Similar to other output configurations, it may be possible to transition the device  100  from the Pmax configuration  624  to any other output configuration described herein depending upon which state the device  100  is moved. 
       FIG. 6J  depicts still another output configuration that may be accommodated while the device  100  is in an open landscape state  348 . Specifically, the device  100  may be configured to present a single continuous image across both touch sensitive displays  110 ,  114  in a landscape configuration referred to herein as a Landscape-Max (LMax) configuration  628 . In this configuration, data (e.g., a single image, application, window, icon, video, etc.) may be split and displayed partially on one of the touch sensitive displays while the other portion of the data is displayed on the other touch sensitive display. The Lmax configuration  628  may facilitate a larger display and/or better resolution for displaying a particular image on the device  100 . Similar to other output configurations, it may be possible to transition the device  100  from the Lmax configuration  628  to any other output configuration described herein depending upon which state the device  100  is moved. 
     The device  100  manages desktops and/or windows with at least one window stack  700 ,  728 , as shown in  FIGS. 7A and 7B . A window stack  700 ,  728  is a logical arrangement of active and/or inactive windows for a multi-screen device. For example, the window stack  700 ,  728  may be logically similar to a deck of cards, where one or more windows or desktops are arranged in order, as shown in  FIGS. 7A and 7B . An active window is a window that is currently being displayed on at least one of the touch sensitive displays  110 ,  114 . For example, windows  104  and  108  are active windows and are displayed on touch sensitive displays  110  and  114 . An inactive window is a window that was opened and displayed but is now “behind” an active window and not being displayed. In embodiments, an inactive window may be for an application that is suspended, and thus, the window is not displaying active content. For example, windows  712 ,  716 ,  720 , and  724  are inactive windows. 
     A window stack  700 ,  728  may have various arrangements or organizational structures. In the embodiment shown in  FIG. 7A , the device  100  includes a first stack  760  associated with a first touch sensitive display  110  and a second stack associated with a second touch sensitive display  114 . Thus, each touch sensitive display  110 ,  114  can have an associated window stack  760 ,  764 . These two window stacks  760 ,  764  may have different numbers of windows arranged in the respective stacks  760 ,  764 . Further, the two window stacks  760 ,  764  can also be identified differently and managed separately. Thus, the first window stack  760  can be arranged in order from a first window  704  to a next window  720  to a last window  724  and finally to a desktop  722 , which, in embodiments, is at the “bottom” of the window stack  760 . In embodiments, the desktop  722  is not always at the “bottom” as application windows can be arranged in the window stack below the desktop  722 , and the desktop  722  can be brought to the “top” of a stack over other windows during a desktop reveal. Likewise, the second stack  764  can be arranged from a first window  708  to a next window  712  to a last window  716 , and finally to a desktop  718 , which, in embodiments, is a single desktop area, with desktop  722 , under all the windows in both window stack  760  and window stack  764 . A logical data structure for managing the two window stacks  760 ,  764  may be as described in conjunction with  FIG. 8 . 
     Another arrangement for a window stack  728  is shown in  FIG. 7B . In this embodiment, there is a single window stack  728  for both touch sensitive displays  110 ,  114 . Thus, the window stack  728  is arranged from a desktop  758  to a first window  744  to a last window  756 . A window can be arranged in a position among all windows without an association to a specific touch sensitive display  110 ,  114 . In this embodiment, a window is in the order of windows. Further, at least one window is identified as being active. For example, a single window may be rendered in two portions  732  and  736  that are displayed on the first touch sensitive screen  110  and the second touch sensitive screen  114 . The single window may only occupy a single position in the window stack  728  although it is displayed on both displays  110 ,  114 . 
     Yet another arrangement of a window stack  760  is shown in  FIGS. 7C through 7E . The window stack  760  is shown in three “elevation” views. In  FIG. 7C , the top of the window stack  760  is shown. Two sides of the window stack  760  are shown in  FIGS. 7D and 7E . In this embodiment, the window stack  760  resembles a stack of bricks. The windows are stacked on each other. Looking from the top of the window stack  760  in  FIG. 7C , only the top most windows in the window stack  760  are seen in different portions of the composite display  764 . The composite display  764  represents a logical model for the entire display area of the device  100 , which can include touch sensitive display  110  and touch sensitive display  114 . A desktop  786  or a window can occupy part or all of the composite display  764 . 
     In the embodiment shown, the desktop  786  is the lowest display or “brick” in the window stack  760 . Thereupon, window  1   782 , window  2   782 , window  3   768 , and window  4   770  are layered. Window  1   782 , window  3   768 , window  2   782 , and window  4   770  only occupy a portion of the composite display  764 . Thus, another part of the stack  760  includes window  8   774  and windows  5  through  7  shown in section  790 . Only the top window in any portion of the composite display  764  is actually rendered and displayed. Thus, as shown in the top view in  FIG. 7C , window  4   770 , window  8   774 , and window  3   768  are displayed as being at the top of the display in different portions of the window stack  760 . A window can be dimensioned to occupy only a portion of the composite display  760  to “reveal” windows lower in the window stack  760 . For example, window  3   768  is lower in the stack than both window  4   770  and window  8   774  but is still displayed. A logical data structure to manage the window stack can be as described in conjunction with  FIG. 8 . 
     When a new window is opened, the newly activated window is generally positioned at the top of the stack. However, where and how the window is positioned within the stack can be a function of the orientation of the device  100 , the context of what programs, functions, software, etc. are being executed on the device  100 , how the stack is positioned when the new window is opened, etc. To insert the window in the stack, the position in the stack for the window is determined and the touch sensitive display  110 ,  114  to which the window is associated may also be determined. With this information, a logical data structure for the window can be created and stored. When user interface or other events or tasks change the arrangement of windows, the window stack(s) can be changed to reflect the change in arrangement. It should be noted that these same concepts described above can be used to manage the one or more desktops for the device  100 . 
     A logical data structure  800  for managing the arrangement of windows or desktops in a window stack is shown in  FIG. 8 . The logical data structure  800  can be any data structure used to store data whether an object, record, file, etc. The logical data structure  800  can be stored in any type of database or data storage system, regardless of protocol or standard. In embodiments, the logical data structure  800  includes one or more portions, fields, attributes, etc. that store data in a logical arrangement that allows for easy storage and retrieval of the information. Hereinafter, these one or more portions, fields, attributes, etc. shall be described simply as fields. The fields can store data for a window identifier  804 , dimensions  808 , a stack position identifier  812 , a display identifier  816 , and/or an active indicator  820 . Each window in a window stack can have an associated logical data structure  800 . While only a single logical data structure  800  is shown in  FIG. 8 , there may be more or fewer logical data structures  800  used with a window stack (based on the number of windows or desktops in the stack), as represented by ellipses  824 . Further, there may be more or fewer fields than those shown in  FIG. 8 , as represented by ellipses  828 . 
     A window identifier  804  can include any identifier (ID) that uniquely identifies the associated window in relation to other windows in the window stack. The window identifier  804  can be a globally unique identifier (GUID), a numeric ID, an alphanumeric ID, or other type of identifier. In embodiments, the window identifier  804  can be one, two, or any number of digits based on the number of windows that can be opened. In alternative embodiments, the size of the window identifier  804  may change based on the number of windows opened. While the window is open, the window identifier  804  may be static and remain unchanged. 
     Dimensions  808  can include dimensions for a window in the composite display  760 . For example, the dimensions  808  can include coordinates for two or more corners of the window or may include one coordinate and dimensions for the width and height of the window. These dimensions  808  can delineate what portion of the composite display  760  the window may occupy, which may the entire composite display  760  or only part of composite display  760 . For example, window  4   770  may have dimensions  880  that indicate that the window  770  will occupy only part of the display area for composite display  760 , as shown in  FIGS. 7   c  through  7 E. As windows are moved or inserted in the window stack, the dimensions  808  may change. 
     A stack position identifier  812  can be any identifier that can identify the position in the stack for the window or may be inferred from the window&#39;s control record within a data structure, such as a list or a stack. The stack position identifier  812  can be a GUID, a numeric ID, an alphanumeric ID, or other type of identifier. Each window or desktop can include a stack position identifier  812 . For example, as shown in  FIG. 7A , window  1   704  in stack  1   760  can have a stack position identifier  812  of 1 identifying that window  704  is the first window in the stack  760  and the active window. Similarly, window  6   724  can have a stack position identifier  812  of 3 representing that window  724  is the third window in the stack  760 . Window  2   708  can also have a stack position identifier  812  of 1 representing that window  708  is the first window in the second stack  764 . As shown in  FIG. 7B , window  1   744  can have a stack position identifier  812  of 1, window  3 , rendered in portions  732  and  736 , can have a stack position identifier  812  of 3, and window  6   756  can have a stack position identifier  812  of 6. Thus, depending on the type of stack, the stack position identifier  812  can represent a window&#39;s location in the stack. 
     A display identifier  816  can identify that the window or desktop is associated with a particular display, such as the first display  110  or the second display  114 , or the composite display  760  composed of both displays. While this display identifier  816  may not be needed for a multi-stack system, as shown in  FIG. 7A , the display identifier  816  can indicate whether a window in the serial stack of  FIG. 7B  is displayed on a particular display. Thus, window  3  may have two portions  732  and  736  in  FIG. 7B . The first portion  732  may have a display identifier  816  for the first display while the second portion  736  may have a display identifier  816  for the second display  114 . However, in alternative embodiments, the window may have two display identifier  816  that represent that the window is displayed on both of the displays  110 ,  114 , or a display identifier  816  identifying the composite display. In another alternate embodiment, the window may have a single display identifier  816  to represent that the window is displayed on both of the displays  110 ,  114 . 
     Similar to the display identifier  816 , an active indicator  820  may not be needed with the dual stack system of  FIG. 7A , as the window in stack position  1  is active and displayed. In the system of  FIG. 7B , the active indicator  820  can indicate which window(s) in the stack is being displayed. Thus, window  3  may have two portions  732  and  736  in  FIG. 7 . The first portion  732  may have an active indicator  820  while the second portion  736  may also have an active indicator  820 . However, in alternative embodiments, window  3  may have a single active indicator  820 . The active indicator  820  can be a simple flag or bit that represents that the window is active or displayed. 
     An embodiment of a method  900  for creating a window stack is shown in  FIG. 9 . While a general order for the steps of the method  900  is shown in  FIG. 9 . Generally, the method  900  starts with a start operation  904  and ends with an end operation  928 . The method  900  can include more or fewer steps or can arrange the order of the steps differently than those shown in  FIG. 9 . The method  900  can be executed as a set of computer-executable instructions executed by a computer system and encoded or stored on a computer readable medium. Hereinafter, the method  900  shall be explained with reference to the systems, components, modules, software, data structures, user interfaces, etc. described in conjunction with  FIGS. 1-8 . 
     A multi-screen device  100  can receive activation of a window, in step  908 . In embodiments, the multi-screen device  100  can receive activation of a window by receiving an input from the touch sensitive display  110  or  114 , the configurable area  112  or  116 , a gesture capture region  120  or  124 , or some other hardware sensor operable to receive user interface inputs. The processor may execute the Task Management Module  540  may receive the input. The Task Management Module  540  can interpret the input as requesting an application task to be executed that will open a window in the window stack. 
     In embodiments, the Task Management Module  540  places the user interface interaction in the task stack  552  to be acted upon by the Display Configuration Module  568  of the Multi-Display Management Module  524 . Further, the Task Management Module  540  waits for information from the Multi-Display Management Module  524  to send instructions to the Window Management Module  532  to create the window in the window stack. 
     The Multi-Display Management Module  524 , upon receiving instruction from the Task Management Module  540 , determines to which touch portion of the composite display  760 , the newly activated window should be associated, in step  912 . For example, window  4   770  is associated with the a portion of the composite display  764  In embodiments, the device state module  574  of the Multi-Display Management Module  524  may determine how the device is oriented or in what state the device is in, e.g., open, closed, portrait, etc. Further, the preferences module  572  and/or requirements module  580  may determine how the window is to be displayed. The gesture module  576  may determine the user&#39;s intentions about how the window is to be opened based on the type of gesture and the location of where the gesture is made. 
     The Display Configuration Module  568  may use the input from these modules and evaluate the current window stack  760  to determine the best place and the best dimensions, based on a visibility algorithm, to open the window. Thus, the Display Configuration Module  568  determines the best place to put the window at the top of the window stack  760 , in step  916 . The visibility algorithm, in embodiments, determines for all portions of the composite display, which windows are at the top of the stack. For example, the visibility algorithm determines that window  3   768 , window  4   770 , and window  8   774  are at the top of the stack  760  as viewed in  FIGS. 7C through 7E . Upon determining where to open the window, the Display Configuration Module  568  can assign a display identifier  816  and possibly dimensions  808  to the window. The display identifier  816  and dimensions  808  can then be sent back to the Task Management Module  540 . The Task Management Module  540  may then assign the window a stack position identifier  812  indicating the windows position at the top of the window stack. 
     In embodiments, the Task Management Module  540  sends the window stack information and instructions to render the window to the Window Management Module  532 . The Window Management Module  532  and the Task Management Module  540  can create the logical data structure  800 , in step  924 . Both the Task Management Module  540  and the Window Management Module  532  may create and manage copies of the window stack. These copies of the window stack can be synchronized or kept similar through communications between the Window Management Module  532  and the Task Management Module  540 . Thus, the Window Management Module  532  and the Task Management Module  540 , based on the information determined by the Multi-Display Management Module  524 , can assign dimensions  808 , a stack position identifier  812  (e.g., window  1   782 , window  4   770 , etc.), a display identifier  816  (e.g., touch sensitive display  1   110 , touch sensitive display  2   114 , composite display identifier, etc,), and an active indicator  820 , which is generally always set when the window is at the “top” of the stack. The logical data structure  800  may then be stored by both the Window Management Module  532  and the Task Management Module  540 . Further, the Window Management Module  532  and the Task Management Module  540  may thereinafter manage the window stack and the logical data structure(s)  800 . 
     The Smart Pad: 
     Demand for portable electronic devices with high levels of functionality continues to rise and personal electronic devices continue to become increasingly more portable. While computer power, battery life, screen size and overall functionality of portable phones and smart phones continue to increase, user reliance on these devices increases. Many users of such devices rely heavily on such devices for general communication, accessing the internet, cloud computing, and accessing various locally stored information such as contact information, files, music, pictures and the like. It is often desirable therefore to connect such heavily relied on devices to an additional computing device or display, such as a monitor or tablet device, such as a SmartPad (SP)  1000  (see  FIG. 10 ). 
     Accordingly, it is desirable for the device  100  to be able to interface with an additional device, such as the SmartPad  1000 , that enables functionality similar to, for example, both a tablet computer system and smart phone. Furthermore, a need exists for the above-described device to allow for various pre-existing features of both devices, such as sending and receiving phone calls and further allowing for the accessibility of applications running on the device  100 . A need also exists for the above device  100  to provide the benefits of both a tablet computer system and cellular phone in one integrative device by allowing for common operations and functionality without compromising the form factor of the device. 
     One exemplary embodiment is directed toward a selectively removable device and smartpad system. The smartpad system is discussed in greater detail hereinafter, and can have various features for complementing the communications device, such as a smart phone or device  100 . For example, the smartpad may supplement the device  100  by providing increased screen size, increased processor size, increased battery or power supply, or the like. Similarly, the device  100  may compliment the SP  1000  by providing connectivity through one or more wireless networks, access to various stored information, and the like. It will expressly recognized therefore that two or more devices of the present invention may be provided in a connected or docked and generally symbiotic relationship. It will further be recognized that the devices provide various features, benefits and functionality in their independent state(s). 
     In accordance with one exemplary embodiment, the device  100  is capable of being received by the SP  1000  through a recessed feature of the SP  1000  having corresponding dimensions to the device  100 . In one exemplary embodiment, the SP  1000  is provided and preferably sized for receiving a predetermined device  100 . In alternative embodiments, however, it is contemplated that the SP  1000  is provided, the smartpad capable of receiving a plurality of communications devices of different sizes. In such embodiments, the SP  1000  may receive communications devices of various sizes by, for example, the inclusion of additional elements, such as spacers and various adjustable features. 
     In accordance with one exemplary embodiment, the device  100  and SP  1000  have a docking relationship that is established when the device  100  is connected to the SP  1000  during various modes of operation. For example, in one embodiment, a system is provided comprising the SP  1000  and the device  100 , the SP  1000  capable of physically receiving the device  100 , wherein the device  100  is operable as the primary computing device. In such an embodiment, the SP  1000  may, for example, simply provide enhanced audio and visual features for the device  100  that comprises its own CPU, memory, and the like. It is further contemplated that the system can be placed in a mode of operation wherein the device  100  docked to the SP  1000  provide it in a more passive mode where, for example, the device  100  draws power from the SP  1000  such as to recharge a battery of the device  100 . 
     In accordance with another exemplary embodiment, the device  100  and SP  1000  are provided wherein the device  100  is received or docked with the SP  1000  and wherein a substantial area of the device  100  is positioned within one or more compartments of the SP  1000 . For example, where as various known devices comprise docking features which require or result in the docked item to be generally exposed, thereby substantially altering the external dimensions of the host device and/or creating a potential for damaging one or both devices upon impact, an exemplary embodiment contemplates the SP  1000  which receives the device  100  in a manner such that the external dimensions of the SP  1000  are not substantially altered when the devices are connected. In such an arrangement, the device  100  and associated connection means are generally protected and the SP  1000  is allowed to substantially maintain its original shape. In accordance with one exemplary embodiment, the SP  1000  is capable of receiving and/or docking the device  100  wherein the device  100  is received in lockable association with the SP  1000 . As used herein, the term “lockable” is not intended to designate or limit it to any particular arrangement. Rather, lockable is intended to refer to various embodiments as described herein and will be recognized by one of ordinary skill in the art. In one embodiment, the device  100  is connectable to the SP  1000  wherein the SP  1000  comprises extension springs for first electively securing the device  100  in a docked manner and an ejection feature for releasing the device  100  from the SP  1000 . Moreover, as will be described in greater detail below, it should be appreciated that the device  100  and SP  1000  can communicate using wired and/or wireless technology(ies) with equal success. Moreover, and in accordance with another exemplary embodiment, the hinged device  100  is selectively connectable to the SP  1000  wherein the device  100  is received by the SP  1000  in an open position and where in one or more preexisting ports of the SP  1000  correspond with internal receiving features of the SP  1000 , such that the device  100  and the SP  1000  may be operated simultaneously in various modes of use. 
     In accordance with some exemplary embodiments, the SP  1000  is provided with an eject or release button to facilitate the removal of a stored or docked device  100 . 
       FIG. 10  illustrates an exemplary SmartPad (SP)  1000  according to an exemplary embodiment. The exemplary SmartPad at least provides a larger touch sensitive display operatively coupleable to device  100 . 
     While the following description uses the term “smart” in conjunction with the display device  1000 , it is to be appreciated that this term does not necessarily connotate that there is intelligence in the SmartPad. Rather, it is to be appreciated that there can be “intelligence,” including one or more of a processor(s), memory, storage, display drivers, etc., in the SmartPad, and/or one or more of these elements shared with the device  100  via, for example, one or more of a port, bus, connection, or the like. In general, any one or more of the functions of the device  100  is extendable to the SmartPad  700  and vice versa. 
     The exemplary SmartPad  700  includes a screen  1004 , a SP touch sensitive display  1010 , a SP configurable area  1008 , a SP gesture capture region(s)  1012  and a SP camera  1016 . The SP  1000  also includes a port (not visible in this orientation) adapted to receive the device  100  as illustrated at least in  FIG. 11 . 
     The device  100  docks with the SmartPad  1000  via the port on the SP  1000  and the corresponding port  136  on device  100 . As discussed, port  136  in some embodiments is an input/output port (I/O port) that allows the device  100  to be connected to other peripheral devices, such as a display, keyboard, printing device and/or SP  1000 . In accordance with one exemplary embodiment, the docking is accomplished by the device  100  sliding into the left-hand side of the SP  1000 , with the device  100  being in an open state and the device  100  engaging a port in the SP  1000  corresponding to port  136 . In accordance with one exemplary embodiment, the device  100  engages a doored cassette-like slot in the SP  1000  into which the device  100  slides. (See for example  FIG. 13 ) It should be appreciated however that there may be other configurations for physically and electrically engaging the two devices—in general, the manner of engagement is not important provided the device  100  and SP  1000  are in electrical communication with one another. 
     The SP  1000  includes a screen  1004 . In some embodiments, the entire front surface of the SP  1000  may be touch sensitive and capable of receiving input by a user touching the front surface of the screen  1004 . The screen  1004  includes touch sensitive display  1010 , which, in addition to being touch sensitive, is also capable of displaying information to a user. 
     The screen  1004  also includes a configurable area  1008  that has been configured for specific inputs when the user touches portions of the configurable area  1008 . Area  1012   a  is configured to receive a “back” input indicating that a user would like to view information previously displayed. Area  1012   b  is configured to receive a “menu” input indicating that the user would like to view options from a menu. Area  1012   c  is configured to receive a “home” input indicating that the user would like to view information associated with a “home” view. 
     In other embodiments, areas  1012   a - c  may be configured, in addition to the configurations described above, for other types of specific inputs including controlling features of device  100  and/or device  1000 , some non-limiting examples including adjusting overall system power, adjusting the volume, adjusting the brightness, adjusting the vibration, selecting of displayed items on screen  1004 , operating the SP camera  1016 , operating a microphone, and initiating/terminating of telephone calls. Also, in some embodiments, areas  1012   a - c  may be configured for specific inputs depending upon the application running on device  100 /SP  1000  and/or information displayed on the touch sensitive displays  1010 . 
     In addition to touch sensing, screen  1004  may also include areas that receive input from a user without requiring the user to touch the display area of the screen. For example, screen  1004  can include gesture capture area  1012 . These areas are able to receive input by recognizing gestures made by a user without the need for the user to actually touch the surface of the display area. In comparison to touch sensitive display  1010  and  1014 , the gesture capture area  1012  may not be capable of rendering a displayed image. 
     While not illustrated, there may also be a number of hardware components within SP  1000 . As illustrated in  FIG. 10 , SP  1000  can include a speaker, a microphone and one or more cameras  1016 . Upon docking the device  100  in the SP  1000 , the corresponding device(s) (e.g., the speaker) in the device  100  could be disabled in favor of the speaker in the SP  1000 . Similarly, other components, such as the screen  1004 , microphone, speaker, etc, could be disabled on the device  100  in favor of the SP  1000 . 
     In general, the touch sensitive display  1010  may comprise a full color, touch sensitive display. A second area within each touch sensitive screen  1004  may comprise the SP gesture capture region  1012 . The SP gesture capture region  1012  may comprise an area or region that is outside of the SP touch sensitive display  1010  area that is capable of receiving input, for example in the form of gestures provided by a user. However, the SP gesture capture region  1012  does not necessarily include pixels that can perform a display function or capability. 
     A third region of the SP touch sensitive screen  1004  may comprise the configurable area  1012 . The configurable area  1012  is capable of receiving input and has display or limited display capabilities. In embodiments, the configurable area  1012  may present different input options to the user. For example, the configurable area  1012  may display buttons or other relatable items. Moreover, the identity of displayed buttons, or whether any buttons are displayed at all within the configurable area  1012  of the SP touch sensitive screen  1004  may be determined from the context in which the device  1000  is used and/or operated. In an exemplary embodiment, the touch sensitive screen  1004  comprise liquid crystal display devices extending across at least those regions of the touch sensitive screen  1004  that is capable of providing visual output to a user, and a capacitive input matrix over those regions of the touch sensitive screen  1004  that is capable of receiving input from the user. 
     As discussed above with reference to  FIGS. 4A through 4H , the various graphical representations of gesture inputs that may be recognized by the screens  104 ,  108  are also recognizable by screen  1004 . As discussed, the gestures may be performed not only by a user&#39;s body part, such as a digit, but also by other devices, such as a stylus, that may be sensed by the contact sensing portion(s) of a screen  1004 . In general, gestures are interpreted differently, based on where the gestures are performed (either directly on the display  1004  or in the gesture capture region  1020 ). For example, gestures in the display  1010  may be directed to a desktop or application, and gestures in the gesture capture region  1020  may be interpreted as for the system. 
     In addition to the above, the SP touch sensitive screen  1004  may also have an area that assists a user with identifying which portion of the screen is in focus. This could be a bar of light or in general and indicator that identifies which one or more portions of the SP touch sensitive screen  1004  are in focus. (See for example,  FIG. 29 ) 
     One or more display controllers (such as display controllers  216   a ,  216   b  and/or dedicated display controller(s) on the SP  1000 ) may be provided for controlling the operation of the touch sensitive screen  1004  including input (touch sensing) and output (display) functions. 
     In accordance with one exemplary embodiment, a separate touch screen controller is provided for the SP  1000  in addition to each of the controllers for the touch screens  104  and  108 . In accordance with alternate embodiments, a common or shared touch screen controller may be used to control any one or more of the touch sensitive screens  104  and  108 , and/or  1004 . In accordance with still other embodiments, the functions of the touch screen controllers may be incorporated into other components, such as a processor and memory or dedicated graphics chip(s). 
     In a similar manner, the SP  1000  may include a processor complementary to the processor  204 , either of which may comprise a general purpose programmable processor or controller for executing application programming or instructions. In accordance with at least some embodiments, the processors may include multiple processor cores, and/or implement multiple virtual processors. In accordance with still other embodiments, the processors may include multiple physical processors. As a particular example, the processors may comprise a specially configured application specific integrated circuit (ASIC) or other integrated circuit, a digital signal processor, a controller, a hardwired electronic or logic circuit, a programmable logic device or gate array, a special purpose computer, or the like. The processors generally function to run programming code or instructions implementing various functions of the device  100  and/or SP  1000 . 
     The SP  1000  can also optionally be equipped with an audio input/output interface/device(s) (not shown) to provide analog audio to an interconnected speaker or other device, and to receive analog audio input from a connected microphone or other device. As an example, the audio input/output interface/device(s)  256  may comprise an associated amplifier and analog to digital converter usable with SP  1000 . Alternatively or in addition, the device  100  can include an integrated audio input/output device  256  and/or an audio jack for interconnecting an external speaker or microphone via SP  1000 . For example, an integrated speaker and an integrated microphone can be provided, to support near talk or speaker phone operations. 
     Hardware buttons (not shown) but similar to hardware buttons  158  can be included for example for use in connection with certain control operations. Examples include a master power switch, volume control, etc., as described in conjunction with  FIGS. 1A through 1J . One or more image capture interfaces/devices  1016 , such as a camera, can be included for capturing still and/or video images. Alternatively or in addition, an image capture interface/device  1016  can include a scanner or code reader. An image capture interface/device  1016  can include or be associated with additional elements, such as a flash or other light sources. 
     Communications between various components of the device  100  and SP  1000  can be carried by one or more buses and/or communications channels. In addition, power can be supplied to one or more of the components of the device  100  and Sp  1000  from a power source and/or power control module  260 . The power control module  260  and/or device  100  and/or SP  1000  can, for example, include a battery, an AC to DC converter, power control logic, and/or ports for interconnecting the device  100 / 1000  to an external source of power. 
     The middleware  520  may also be any software or data that allows the multiple processes running on the devices to interact. In embodiments, at least portions of the middleware  520  and the discrete components described herein may be considered part of the OS  516  or an application  564 . However, these portions will be described as part of the middleware  520 , but those components are not so limited. The middleware  520  can include, but is not limited to, a Multi-Display Management (MDM) class  524 , a Surface Cache class  528 , a Window Management class  532 , an Activity Management class  536 , an Application Management class  540 , a display control block, one or more frame buffers  548 , an activity stack  552 , and/or an event buffer  556 —all of the functionality thereof extendable to the SP  1000 . A class can be any group of two or more modules that have related functionality or are associated in a software hierarchy. 
     The MDM class  524  also includes one or more modules that are operable to manage the display of applications or other data on the screen of the SP  1000 . An embodiment of the MDM class  524  is described in conjunction with  FIG. 5B . In embodiments, the MDM class  524  receives inputs from the OS  516 , the drivers  512  and the applications  564 . The inputs assist the MDM class  524  in determining how to display the information required by the user. Once a determination for display configurations is determined, the MDM class  524  can bind the applications  564  to a display configuration. The configuration may then be provided to one or more other components to generate the display on the SP  1000 . 
       FIG. 11  illustrates an exemplary embodiment showing the device  100  docking with the SP  1000 . More specifically, the device  100  is being inserted into a slot (not shown) on the SP  1000 . On completion of the inserting of device  100  into SP  1000  (See  FIG. 12 ), device  100  communicates with the SP  1000  via bus or other wired or wireless electrical means  1204 . The device  100  is also connected with, for example, the camera/video camera  1016 , microphone (Mic), and power port  1208 . 
     In conjunction with the docking of device  100  with SP  1000 , one or more of the devices can begin power management. For example, one or more of the device  100  and SP  1000  can include power supplies, such as batteries, solar, or in general any electrical supply, any one or more of which being usable to supply one or more of the device  100  and SP  1000 . Furthermore, through the use of, for example, an AC power adaptor connected to port  1208 , the SP  1000  can supply power to device  100 , such as to charge device  100 . It will be appreciated that the power management functionality described herein can be distributed between one or more of the device  100  and SP  1000 , with power being sharable between the two devices. 
     In addition to power management functions, upon the device  100  being docked with the SP  1000 , the displays on device  100  can be turned off to, for example, save power. Furthermore, electrical connections are established between the device  100  and SP  1000  such that the speaker, microphone, display, input capture region(s), inputs, and the like, received by SP  1000  are transferrable to device  100 . Moreover, the display on device  1000  is enabled such that information that would have been displayed on one or more of the touch sensitive displays  110  and  114  is displayed on touch sensitive display  1010 . As will be discussed in greater detail herein, the SP  1000  can emulate the dual display configuration of the device  100  on the single display  1010 . 
     The SP  1000  can optionally be equipped with the headphone jack  1212  and power button  1216 . Moreover, any hardware buttons or user input buttons on the device  100  could be extended to and replicated on the SP  1000 . 
     This dock event between the device  100  and SP  1000  can be seen as states  336  or  344  in  FIG. 3A . As will be appreciated, and in accordance with one of the illustrative embodiments herein, the device  100  is docked with SP  1000  with the device being in the open state  210 . However, it is to be appreciated that the device  100  can be docked with the SP  1000  in the closed state  304 , or docked via, for example, a cable without the device  100  necessarily being inserted into the SP  1000 . 
       FIGS. 13A-B  illustrate application reorientation according to an exemplary embodiment of the invention. In particular,  FIG. 13A  illustrates the device  100  being inserted into the SP  1000 . Before being associated with the SP  1000 , the device  100  has two applications, both in the landscape mode, represented by application “B” in landscape on a first screen and application “C” in landscape on a second screen (partially obscured by SP  1000 ). 
       FIG. 13B  illustrates the re-orientation of the windows for the two applications based on the device  100  being associated with the SP  1000 , the SP  1000  being in the landscape orientation. In accordance with this exemplary embodiment, application “B” on the device  100  is re-oriented to be in the portrait orientation on the SP  1000 , and in a similar manner, application “C” on the device  100  is reoriented to the portrait orientation on the right-hand side the touch sensitive display  1010 . As will be appreciated, the reorientation of the application(s) from the device  100  to the SP  1000  can occur in a similar manner for a single application running on the device  100 . For example, if there is only one application running on device  100 , and the application is running in landscape mode, when the device  100  is docked with the SP  1000 , the orientation of the application is reoriented to be appropriate for the current orientation of the SP  1000 . For example, if the application on the device  100  is in portrait mode, and the SP  1000  is in landscape mode, the application is reoriented from portrait mode on the device  100  to landscape mode on the SP  1000 . In a similar manner, if the application on the device is in landscape mode, and upon being docked to the SP  1000  in portrait mode, the application is reoriented into portrait mode for appropriate viewing on the SP  1000 . 
     In accordance with one exemplary embodiment, the accelerometer  176  on device  100  is used to determine the orientation of both the device  100  and SP  1000 , and consequently the orientation of the touch screen display  1010 . Therefore, the accelerometer(s)  176  outputs a signal that is used in connection with the display of information to control the orientation and/or format in which information is to be displayed to the user on display  1010 . As is to be appreciated, reorientation can include one or more of a portrait to landscape conversion, a landscape to portrait conversion, a resizing, a re-proportioning and/or a redrawing of the window(s) associated with the application(s). 
     On reorienting of the running application(s), the application(s) is displayed on display  1010  on SP  1000 . 
     In accordance with an optional exemplary embodiment, priority can be given to the application that is in focus. For example, and using again applications “B” and “C” as illustrated in  FIG. 13B , if instead application C was in focus before docking, application C could be reoriented and displayed on the left-hand portion of display  1010 , and application B, which was not in focus before docking, displayed on the right-hand portion of display  1010  upon docking. 
     In accordance with another optional embodiment, the application in focus could be displayed in full-screen mode on display  1010  with the application(s) not in focus placed into a window stack that is, for example, in a carousel-type arrangement as discussed hereinafter. 
       FIG. 14  illustrates an exemplary embodiment of a single application mode for the SP  1000 . In the single application mode, all applications are launched and displayed in full screen. The single application mode can be indicated by a multi-tasking icon in the enunciator bar, or at some other location on screen  1004 . 
     Displaying of the application(s) are managed by one or more of the display controller  544 , framework  520 , window management module  532 , display configuration module  568 , as well as middleware  520  and associated classes. In single application mode, all dual screen capable applications can be launched in either a dual screen or max mode, where the application is displayed substantially filling the display  1010 . This is applicable to when the SP  1000  is either in the portrait mode, as illustrated in  FIG. 14 , or in the landscape mode, as illustrated in  FIG. 15 . In these figures, the “A” represents the single application with the X 1 , X 2  being variables representing the coordinates and/or location of the window in which the application “A” is to be displaced. A similar notation is used hereinafter for the multi-application mode, with it being appreciated that, for example, X 1  may contain the coordinate information for the displaying of the window for a first application, and X 2  may contain the coordinate information for the displaying of a window corresponding to a second application, and so on. 
     Therefore, in one exemplar embodiment, when a single application is executed, a single application can launch in the full screen mode and can be correlated to the max mode as discussed in relation to  FIG. 6I  where a single application spans both screens of the device  100 . This max mode is applicable to both the portrait and landscape orientations as illustrated in  FIG. 14  and  FIG. 15  with the display configuration module  568  appropriately (re)sizing the window for the application to fit on substantially all or all of the display  1010 . 
     This resizing can occur regardless of whether a native application on the device  100  actually supports the orientation of the SP  1000 . Therefore, even if the application does not support a particular orientation on device  100 , the display configuration module  568  can appropriately re-render and/or re-size the window for the application for appropriate display on the SP  1000 . 
       FIG. 16  and  FIG. 17  illustrate an exemplary method of rending a single application, that is a dual screen application, in the portrait max mode and landscape max mode, respectively. More specifically, in  FIG. 16 , the rendering of a dual screen application in portrait mode will display on display  1010  one of the two screens substantially or completely filling display  1010 . A user then, for example using a gesture, could scroll between the two screens of the single application. In the landscape mode, as illustrated in  FIG. 17 , the screen  1010  is divided into a first portion  1704  and a second portion  1708 . In this exemplary embodiment, the first screen of the dual screen application is rendered in first portion  1704 , and the second screen of the dual screen application is rendered in the second portion  1708 . While a certain portion of the screen  1010  is illustratively logically divided for the first portion  1704  and the second portion  1708 , it should be appreciated that the screen real estate assigned to each portion can vary, for example, based on one or more of optimum display for the window(s), type of information being displayed in each portion, user preferences, rules associated with the application, and/or the like. 
     In accordance with a first example, the first portion is allocated one third of the screen  1010 &#39;s resolution, while the second portion  1708  is allocated two thirds of the screen real estate. In accordance with another example, the screen  1010  is split 50/50. In accordance with yet another example, the first portion could be allocated 70% of the screen  1010 &#39;s real estate, while the second portion  1708  could be allocated 30%. The managing and resizing of these windows can again be done in cooperation with the display configuration module  568 , as well as the windows management module  532  and display controllers for successful rendering of the location of the window(s) on the SP  1000 . 
     As will be appreciated, and in a manner similar to the operation of device  1000 , should the SP  1000  change orientation (e.g., from landscape to portrait or vice versa) the window(s) for the application(s) can be redrawn in the appropriate orientation taking into account window prioritization based on whether a particular application and current focus is for a dual screen application or a single screen application. 
     Focus can also be taken into consideration when determining which window of the application should be displayed when the SP  1000  is in the portrait position. For example, if the application is an e-mail client, and the application natively is displayed on dual screens on device  1000  (a first screen being directed toward showing inbox content, and the second screen being a preview window for a specific item in the inbox) the system can evaluate which window is currently in focus, and ensure that window is displayed in the portrait max mode when the SP  1000  is in the portrait orientation. 
     In  FIG. 17  the SP  1000  is configured to merge windows from the dual screen application on to a single display  1010 . In this landscape orientation, data (e.g., a single image, application, window, icon, video, etc.) from a first window is displayed in a first portion of the display  1010  while data (e.g., a single image, application, window, icon, video, etc.) is shown in a second portion of the display  1010 . Similar to other output configurations, it may be possible to transition the SP  1000  from the shown output configuration to any other output configuration described herein, depending on, for example, into which state the SP  1000  is moved. 
     Some other exemplary embodiments of windows management within the SP  1000  upon the device  100  docking with the SP  1000  are as follows: For example, a device  100  is docked to the SP  1000 , with the SP  1000  in a portrait orientation and there are two single-screen applications running on the device  1000 , the application in focus is placed in a lower portion of the display  1010 , and the application not in focus is placed on an upper portion of the display  1010 . Another exemplary scenario, where the device  100  is docked to a portrait-oriented SP  1000  where one dual-screen application is running on the device  100  and the SP  1000  is in a dual application mode, applies gravity drop as discussed herein. 
     In another exemplary scenario, where the device  100  is running two single-screen applications, and the SP  1000  is in a landscape dual application mode, the first application is assigned to a first portion of the display  1010  and the second application is assigned to a second portion of the display  1010 . 
     In yet another exemplary scenario where the device  100  is running one dual-screen application and the SP  1000  is in dual application landscape mode, both screens of the dual screen application can be shown on the SP  1000 . 
     Stickiness can also apply to the SP  1000  such that, for example, when a first application is in focus, upon docking to a single application mode SP  1000 , the application remains visible after docking. As another example of stickiness, if a second application is in focus upon docking to a single application mode SP  1000 , application two remains visible after docking. 
     In accordance with another example, the device  100  is running one dual-screen application and is docked to a landscape-oriented SP  1000  in max mode, the windows are re-oriented to be side-by-side, opposed to one above the other. 
       FIGS. 18  through  FIG. 21  generally illustrate the management and display of a virtual keyboard  1804  on display  1010 . More specifically, in  FIG. 18 , in portrait mode, the virtual keyboard  1804  is positioned below application area  1808 , where an application is displayed in, for example, max mode. In general, it is preferred that the keyboard can be glued to the lower-portion of the display  1010 , regardless of whether the SP is in the landscape or portrait mode. However, it is to be appreciated that, for example, based on user preferences, the screen can be glued to another portion of the screen, or can be moved to another location via, for example, a gesture. In  FIG. 18 , the application area  1808  displays, for example, a standard application with the virtual keyboard  1804  being displayed in the lower portion of display  1010 . In  FIG. 19 , for example, the application area  1908  is showing a dual-screen enabled application in max mode. The keyboard  1804  is again similarly displayed in the lower portion of the display  1010 . 
     In  FIG. 20 , in SP landscape mode, the keyboard  1804  is displayed in the lower portion of display  1010  with the application area  2004  substantially or completely filling the displayable area above the keyboard  1804 . In  FIG. 21 , the SP is again in landscape mode and displaying a dual-screen enabled application in max mode, the application area  1   2104  and application area  2   2108 , the keyboard  1804  is displayed below the two application areas. 
     In general, in the embodiments illustrated in  FIG. 18  through  FIG. 21 , a first determination is made as to whether a keyboard should be displayed. If the keyboard is to be displayed, the next determination is made as to the orientation of the SP. If the SP is in a portrait mode, the virtual keyboard is presented also in a portrait mode, preferable on the lower portion of the screen. If the SP is in a landscape mode, the keyboard is optionally re-sized to be substantially displayed on a lower portion of the display with, for example, one or more application windows being located above the virtual keyboard. With the orientation of the SP change, the keyboard is also reoriented to be coincident with the orientation of the SP. Similarly, when the keyboard is no longer required, the keyboard is hidden with the application area(s) being expanded to again substantially fill the display  1010 . 
       FIG. 22  and  FIG. 23  illustrate exemplary methods of managing window positions on the SP  1000 . In particular, in  FIG. 22 , application X  2204  is in view on display  1010 . On receiving user input, such as the swipe motion represented by  2208  in the gesture capture region  1020 , application X is “scrolled” to the left to be replaced with the dual-screen application A 1 |A 2 , as shown in  FIG. 23 . If the same gesture  2208  were to be repeated again, application Z would come into view. Similarly, if in  FIG. 22  gesture  2208  was in the opposite direction, to the right, application Y would come into view on display  1010 . Scrolling through available windows is of course applicable to both the landscape and portrait mode of the SP in a similar manner. For example, in portrait mode, instead of the gesture traversing from left to right or right to left, the gesture could traverse in a downward motion, or in an upward motion, with the virtual stacks of the windows being located “above” or “below” the device, similar to a rolodex. Thus, when the user initiates a downward type gesture, the next application “above” is displayed on display  1010 . 
       FIG. 24  illustrates the multi application mode of the SP  1000 , wherein in the multi application mode the SP  1000  emulates the device  100  in its mini-tablet form—with this mode optionally being invoked by selection of a multi application button (shown and described hereinafter). A simplified way of understanding this mode is to appreciate that the mode emulates the device  100  being opened. In this multi application mode, the SP  1000  can inherit the rules regarding the display of information on the device  100 —For example, that all applications are launched in single screen mode. One exception could be applications that support a max mode can be by default automatically expanded to this mode if provided the opportunity. 
     In this mode, each application has the ability to determine how the application appears in each orientation (e.g., portrait and landscape). 
       FIG. 26  illustrates an exemplary method of managing the multiple application mode of the SP  1000 . In the multiple application mode, multiple applications can be managed and displayed within the display  1010 . In multi application mode, the SP  1000  having the single screen emulates the dual screens of the device  100 . To initiate the multiple application mode, a button/toggle  2618  is selected, which allows the user to select multiple applications for display in the display  1010 . In this exemplary embodiment, a first application  2604  C, is shown in the upper-portion of the portrait mode SP  1000  and a second application  2608  D, is shown in a lower-portion of screen  1010 . In conjunction with the displaying of multiple applications in the multiple application mode, focus indicator  2616  can be provided to assist the user with identifying which application is in focus. As discussed, this focus indicator can be a light bar, or other indicator (such as an indicator in the screen  1010  or beside  2608 ) drawing the user&#39;s attention to which application is in focus. In the exemplary embodiment in  FIG. 26 , application D  2608  is in focus as represented by the focus bar  2616 . In accordance with this exemplary embodiment, and while the focus bar  2616  is shown in the gesture capture region  1020 , it should be appreciated that the focus indicator could be located in some other portion of the SP  1000 . For example, the window for the application in focus could be slightly re-sized to allow for the display of a bar of pixels adjacent to the window, which would similarly alert the user to the fact that that application is in focus. Similarly, the application in focus could appear at normal brightness while the application not in focus could be slightly dimmed. In general, any technique could be used to assist the user in readily determining which application is in focus. 
     To change focus, a user could use any of the gestures discussed herein or could, for example, simply touch the area where application C is displayed, thereby changing focus to application C, at which point a corresponding relocation of the focus indicator  2616  to adjacent to application C would occur. 
       FIG. 27  illustrates a similar scenario for a landscape mode SP  1000 . In particular, and upon selection of the multi application mode, the display  1010  is divided between, in this example, a first application D  2712 , and a second application F  2708 . Here, application D is displayed on the right-hand portion of display  1010  and application F displayed on the left-hand portion of display  1010 . While in this exemplary embodiment, the display real estate is split 50/50 between the two applications, it should be appreciated that one application could be displayed on a larger portion of the display  1010  than the other. In this particular exemplary embodiment, application D is in focus, as represented by focus indicator  2416 . 
     In the multiple application mode, in both portrait and landscape orientations, each application could have its own associated window stack as show in  FIG. 22  and  FIG. 23 , or there could be one stack shared between all of the displayed applications. More specifically, if each application has its own stack, with a stack structure similar to that illustrated in  FIG. 22 , a stack would be available for the first application, such as application C, and a similar stack would be available for application D. Each of these stacks could be independently scrolled through using, for example, a gesture as discussed above. 
       FIG. 28  illustrates an exemplary method for managing screen display characteristics according to another embodiment of this invention. In accordance with this embodiment, a determination is made whether an application can be maximized, and if it can be maximized, it is expanded to the dual screen mode or max mode, as appropriate, to substantially fill the display  1010  as illustrated in the figure. Here, application E 1 , which is an application that can be maximized, has been expanded using the max mode to substantially or completely fill display  1010 . 
     In  FIG. 28 , button  2618  allows a user to toggle between a single screen mode (as illustrated in  FIG. 28 ) and an emulated dual screen mode, for example, as illustrated in  FIG. 26  and  FIG. 27 . Here, button  2618  does not include the “|” therefore indicating to the user the SP  1000  is in single screen mode. 
       FIG. 29  illustrates an exemplary method of managing windows. In this exemplary embodiment, and similar to the operation of the device  100 , when the last application in the stack is moved to the side, the desktop is displayed. Even more specifically, as shown in  FIG. 29 , application F  2908  is displayed in an upper portion of display  1010  and the desktop  2912  is displayed in the lower portion of display  1010 . Here the desktop is in focus, as illustrated by the focus indicator  2916 . This configuration is available since the user has selected the dual-screen emulation mode button  2618 . 
       FIG. 30  illustrates an exemplary method of displaying a keyboard according to one embodiment. In particular, when the SP is in portrait mode, the SP will have a keyboard area  3004  and an application area  3008 . Upon display of the keyboard  3004 , the application in application area  3008  is resized to substantially or completely fill the area of the screen not occupied by the keyboard  3004 . 
       FIG. 31A  and  FIG. 31B  illustrate desktop availability in both the single application mode and dual application mode in both the SP landscape mode and SP portrait mode. In particular, and in accordance with an exemplary embodiment, the desktop  3104  will occupy the entirety of the screen  1010 . Additionally, and in accordance with this exemplary embodiment where the desktop is shown in a full-screen mode, the enunciator bar  1312  can be expanded across the entirety of the screen  1010 . This can occur in both the portrait mode as shown in  FIG. 31A  as well as the landscape mode as illustrated in  FIG. 31B . From here, upon selection of the application launcher  3116 , the application launcher can optionally expand across the entirety of the screen  1010  in either the portrait or landscape mode. Similarly, the file explorer, which is launched by pressing the file explorer button  3120 , can be similarly expanded into substantially all or all of the screen  1010  space. 
       FIG. 32A  and  FIG. 32B  illustrate screen redrawing that may be required to transition the desktop from the device  100  to the SP  1000 . In particular, in  FIG. 32A , six exemplary desktop panels are shown  3204 - 3224 . These desktop panels are moveable in a carousel-like fashion based on gesture input from a user. However, it may not be possible to directly translate these panels to display correctly on the SP  1000  without the panels being distorted or not occupying the entirety of the screen  1010 . Accordingly, in accordance with one exemplary embodiment, one or more of the panels  3204 - 3224  can be resized when displayed on the SP  1000  to accommodate all or substantially all of the screen  1010 . In accordance with another exemplary embodiment, more than two of the panels can be shown on the screen  1010 , such as a portion of panel D 2   3208 , a portion of panel D 3   3212  and a portion of panel D 4   3216 . In this manner, the desktop illustrated on the SP  1000  will have a similar look-and-feel to the desktop panels shown on device  100 . The same carousel-like motion is available via a gesture input to the SP  1000  such that a user can scroll to the one or more panels of the desktop. 
       FIG. 33  illustrates an exemplary notifications display that behaves on the SP  1000  in a very similar manner to that of the device  100 . In particular, and whether in the portrait or landscape mode, notifications and status/toggle buttons are provided that allow the user to, for example, toggle on or off Bluetooth®, WiFi, screen lock, dual or single screen mode, power options, and the like. These, as well as other options are generally shown in area  3304 . Additional notifications can also be shown in area  3308  including one or more of carrier information, notification information, communication information, and the like as discussed above. 
     In more detail, area  3304  provides some buttons for standard widgets such as WiFi toggle on and off, Bluetooth® toggle on and off, and the like. The screen lock toggle can allow, for example, user to lock the screen thereby prohibiting it from rotating despite the orientation of the SP  1000 . The toggle can change color or display characteristics to indicate whether screen lock has been enabled. The single/dual application mode button toggles, for example, three different states including a dual application mode state, a single application mode state, and a single application lock state. The power mode toggle toggles between a handset optimized, SP optimized, hybrid power consumption, or of the like. These power modes can be associated with power levels, as indicated by the two battery status indicators  3312  and  3316  which correspond to the power levels in the device  100  and SP  1000 , respectively. 
       FIG. 34A  and  FIG. 34B  show exemplary methods of launching and displaying the application launcher upon selection of the application launcher button  3116 . In both the portrait mode illustrated in  FIG. 34A  and landscape mode illustrated in  34 B, and when the SP is in single application mode, the application launcher can appear in a bubble so as to not necessarily take up the entirety of the screen  1010 . However, for example, upon receiving an appropriate gesture or input by the user, the application launcher can be expanded to take up the entirety of the screen  1010 . This could further be classified in a preference such that the default is to always open the application launcher in a bubble so as to not take up the entirety of the screen  1010 , or to always open in full screen mode, taking up substantially all or all, of the screen  1010 . 
       FIG. 35A  and  FIG. 35B  illustrate an optional embodiment whereby the system could provide “hints” as to the content of desktop panels that are not fully in view. More specifically,  FIG. 35A  shows the first embodiment of the desktop panels D 1 -D 6 ,  3504 - 3524  respectively. As discussed, a user is able to scroll through these panels in a carousel-type fashion, revealing any of the content in D 1 -D 6 . In accordance with the optional embodiment illustrated in  FIG. 35B , where the same panels D 1 -D 6  are available for viewing by user, the user is given a preview of one or more adjacent panels, here D 2   3508  and D 5   3520 . In this configuration, this user is able to “peek” at the content of the adjacent panel(s) without necessarily scrolling in a carousel like fashion to view the entirety of the panel. More specifically, the entirety of panel D 3   3512  and D 4   3516  is shown on the display  1010 . In addition, approximately one third of panel D 2   3508  and one third of panel D 5   3520  are also shown on the display  1010 . As will be appreciated, more or less of panels D 2  and D 5  could be shown, with the greater of the panel being shown, the more visibility into that portion of the desktop the user would have. 
       FIG. 36  illustrates an optional embodiment for managing in a multiple application mode the stack of windows. This elegant method reinforces the conceptual model and assists the user with visualizing spatially the “carousel” type arrangement of the stack in the multi application mode. As is to be appreciated, while the exemplary embodiment shown in  FIG. 36  is directed toward portrait mode of SP  1000 , it can work equally well in the landscape mode with the difference being instead of the carousel rotating from a top to bottom or bottom to top type arrangement, the “carousel” could be manipulated in a left to right or right to left type operation. However, the carousel could also work in a top to bottom or bottom to top mode in landscape mode as well. 
     In this exemplary embodiment, when multi-application mode is enabled via button  2618 , application C  3604  and application D  3608  can be displayed, separated by separator  3612 . In accordance with this optional exemplary embodiment, there are also one or more overflow applications behind application C  3604 , here the overflow applications being  3424  and  3428 . In a similar manner, there can be one or more overflow applications behind application D  3608 , here application  3416  and application  3420 . In this particular exemplary embodiment, the back and menu buttons  3432  can be enabled with a portion of the desktop  3436  being viewable behind the application stack. Upon receipt of one or more input gestures, such as gesture  3440 , a user can scroll through the “carousel” of applications, in this instance, relocating application D  3608  to application C  3604 &#39;s position, and thereby revealing application  3416 . In addition, the focus indicator can be displayed near the application that is in focus. In this particular example, focus indicator  3444  is displayed beside application D. In accordance with an optional exemplary embodiment, instead of the stack “stopping” when the user reaches the last application, such as application  3420  or application  3428 , the applications can be stacked in a circular manner, and continuously rotate in response to one or more input gestures by a user. 
     These concepts can be extended to the situation where the keyboard is also displayed in the multiple application mode. For example, and as illustrated in  FIG. 37 , the keyboard  3704  is displayed below the application stack  3708 . “Behind” the application stack  3708 , are additional applications  3712  and  3716  that the user can access via, for example, initiation of gesture  3720 . This exemplary embodiment has the applications scroll in a carousel-like fashion into and out of view, with the keyboard  3704  remaining visible, for example, at the bottom of display  1010 . As with the embodiment in  FIG. 35 , the back and menu buttons can be enabled and, for example, virtually displayed on the display  1010  as illustrated by graphical button  3724 . 
       FIG. 38  outlines an exemplary method for docking the device  100  with the smartpad  1000 . In particular, control begins in step S 3802  and continues to step S 3804 . In step S 3804  the insertion of the device into the SP is detected. Next, in step S 3806 , power management can optionally begin. For example, and as discussed, the SP can be used as a power source for the device, the device can be used as a power source for the SP, power can be shared between the two devices and/or the SP can be plugged in, via for example, an AC adaptor, which is capable of charging one or more of the SP and the device  100 . Then, in step S 3808 , the display of the device  100  is optionally turned off to, for example, conserve power. Control then continues to step S 3810 . In step S 3810 , communication and/or connectivity are established between the device  100  and the SP. Next, in step S 3812 , display and other input/output functions on the SP are enabled. Then, in step S 3814 , the device software settings are mapped to the smartpad hardware settings. Control then continues to step S 3816 . 
     In step S 3816 , the screen orientation of the device is automatically aligned to the orientation of the SP. Next, in step S 3818 , the last application in focus on the device remains in focus and is displayed on the SP. Normal operation and interaction with the SP then continues utilizing, for example, the same gestures as are usable with the device  100 . Control then continues to step S 3820  where the control sequence ends. 
       FIG. 39  illustrates an exemplary method of application/display orientation/reorientation. In particular, control begins in step S 3900  and continues to step S 3902 . In step S 3902 , the orientation of the SP is detected. Next, in step S 3904 , the application orientation on the device is detected. Then, in step S 3906 , one or more displayed applications are reoriented to be in the same orientation as the SP. In addition, and based on the need for reorientation, a re-drawing or re-sizing of the application can also occur with the application(s) being displayed on the SP. Control then continues to step S 3908  where the control sequence ends. 
       FIG. 40  outlines an exemplary method for managing the keyboard. In particular, control begins in step S 4000  and continues to step S 4002 . In step S 4002 , determination is made as to whether a keyboard request has been detected. If a keyboard request has not been detected, control jumps back to step S 4000  with control otherwise continuing to step S 4004 . In step S 4004 , a determination is made as to the orientation of the SP. If the SP is in the landscape orientation, control jumps to step S 4010  with control otherwise continuing to step S 4006  with the SP being in the portrait orientation. In step S 4006 , the keyboard is displayed in the portrait mode. 
     Next, in step S 4008 , a determination is made as to whether there has been an orientation change. If there has been an orientation change, control jumps to step S 4010  with control otherwise continuing to step S 4014 . 
     In step S 4010 , the keyboard is displayed in the landscape mode. Next, in step S 4012 , a determination is made as to whether there has been a change in orientation of the SP. If there has been a change in the orientation, control jumps to step S 4006  with control otherwise continuing to S 4014 . 
     In step S 4014 , a determination is made as to whether the keyboard should be hidden. If the keyboard should be hidden, control continues to step S 4016  with control otherwise continuing back to step S 4004 . 
     In step S 4016 , the keyboard is hidden with control continuing to step S 4018  where the control sequence ends. 
       FIG. 41  illustrates an exemplary method for window management. In particular, control begins in step S 4100  and continues to step S 4102 . In step S 4102  a gesture is detected. As will be appreciated, and similar to the device  100 , this gesture can be on the touch-sensitive display, in a configurable area, and/or in the gesture capture region(s). In step S 4104 , gesture direction can also optionally be detected. Then, in step S 4106 , the next application window can be brought into view, enabling, for example, a user to scroll through application window stack. A determination is then made as to whether another gesture has been detected. If another gesture has been detected, control jumps back to step S 4104  with control otherwise continuing to step S 4110 . 
       FIG. 42  outlines an exemplary method for screen management. In particular, control begins in step S 4200  and continues to step S 4202 . In step S 4202 , multiple application mode is enabled via, for example, selection of a button or toggle. Next, in step S 4204 , a user is optionally prompted to select which applications will be displayed. In an alternative embodiment, two adjacent applications in the stack are displayed, with one of the applications being the application that is currently in focus. Then, in step S 4206 , the screen is split with the first portion of the screen displaying a first application and a second portion of the screen displaying a second application. Next, in S 4208 , the application that was detected to be in focus is then highlighted on the SP in step S 4210 . Control then continues to step S 4212 . 
     In step S 4212 , a determination is made as to whether a new application has been brought into focus. If a new application has been brought into focus, control jumps back to step S 4210  where that application is highlighted with an “in-focus” indicator. Otherwise, control continues to step S 4214  where the control sequence ends. 
       FIG. 43  outlines an exemplary method for windows management. In particular, control begins in step S 4300  and continues to step S 4302 . In step S 4302 , a determination is made as to whether the application can be maximized. Next, in step S 4304 , if the application is maximizable, control jumps to step S 4306  where the application is expanded to either the dual screen mode or the max mode. Control then continues to step S 4308  where the control sequence ends. 
       FIG. 44  outlines an exemplary method for transitioning from an application window to the desktop. In particular, control begins in step S 4400  and continues to step S 4402 . In step S 4402 , the last application in the application window stack is detected. Next, in step S 4404 , a gesture is detected, the gesture requesting a “next” window however the current window is the last application in the window stack. In this scenario, in step S 4406 , the desktop is displayed in that there are no further windows to display in the application window stack. Control then continues to step S 4408  where the control sequence ends. 
       FIG. 45  illustrates an exemplary method of emulating the multi-screen display of the device  100  on the SP  1000 . In particular, control beings in step S 4500  and continues to step S 4502 . In step S 4502 , the desktop is displayed on the SP. Next, in step S 4504 , the desktop is logically divided on the SP into, for example, two sections. Then in step S 4506 , a first screen of the desktop is displayed in a first logical portion of the SP display. Then, in step S 4508 , a second screen of the desktop is displayed in a second logical portion of the SP display. Control then continues to step S 4510 . 
     In step S 4510 , carousel movement of the “panels” shown in the display can be initiated through user input, such as a gesture. Control then continues to step S 4512  where the control sequence ends. 
       FIG. 46  outlines an exemplary method of displaying multiple “panels” of the desktop on the SP. In particular, control begins in step S 4600  and continues to step S 4602 . In step S 4602 , a portion of the desktop is displayed on the SP. Next, in step S 4604 , the desktop is logically divided on the smartpad to accommodate multiple desktop “panels.” Then, in step S 4608 , the first screen or panel of the desktop is displayed in one logical portion of the SP display. Then, in step S 4610 , a second screen or panel of the desktop is displayed bridging a first and a second logical portion of the SP display. Then, a third screen or panel of the desktop is displayed in the second logical portion of the SP display. Control then continues to step S 4614 . 
     In step S 4614  carousel movement of the panels can be affected by, for example, an input of a gesture by the user. Control then continues to step S 4616  where the control sequence ends. 
       FIG. 47  outlines an exemplary method of displaying one or more portions of the desktop. In particular, control begins in step S 4700  and continues to step S 4702 . In step S 4702 , an access request to the desktop is detected. Next, in step S 4704 , at least one desktop panel is displayed. Then, in step S 4706 , at least one additional desktop panel is partially displayed on the desktop. Control then continues to step S 4708 . 
     In step S 4708 , and upon detection of a gesture, the partially displayed panel can be completely displayed on the display of the SP. Control then continues to step S 4710  where the control sequence ends. 
       FIG. 48  outlines an exemplary method of windows management in multiple application mode. In particular, control begins in step S 4800  and continues to step S 4802 . In step S 4802 , multiple application mode is entered. Next, in step S 4804 , the windows stack is arranged with one or more applications being partially visible behind a first application. Next, in step S 4806 , the stack can be arranged with one or more applications also partially being visible behind a second application. Then, in step S 4808 , and upon receiving an input gesture from a user, carousel-like scrolling can be enabled through the stack until the end of the stack is reached, or in a second embodiment, the stack can have a “circular” arrangement where continuous scrolling through the stack is possible. Control then continues to step S 4810  where the control sequence ends. 
     Power Management: 
     Power management is an important function in a portable device with a limited energy storage capacity. One of the largest consumers of energy is the display, particularly in a dual-display device. “Sleep” or “power-saving” mode powers down displays when not used or fail to receive a video-input signal for a determined period of time. Organic light-emitting diodes (“OLEDs”) generally consume less energy compared to conventional light-emitting diodes (“LEDs”), liquid crystal display (“LCD”), and electroluminescent displays (“ELDs”). TFT LCD is a variant of LCD that is used for computer monitors. While many techniques have been developed to conserve energy and prolong battery life, improvements remain highly desirable. “Display elements” shall refer to each individually and independently energizable light-emitting device in a display. A display element includes, without limitation, an OLED, LED, liquid crystal, and the like. 
     This disclosure is directed to the use of one or more altered display parameters to manage power consumption. In other words, one or more display parameters are varied in response to a change in a sensed ESD parameter and/or other ESDM output and/or user input. 
     As used herein, a “display parameter” is one or more of luminance (measured in candelas per square meter), intensity, or brightness, aspect ratio (the ratio of the horizontal length to the vertical length, e.g., 4:3, 5:4, 16:10, and 16:9), viewable image size (measured diagonally), display resolution (the number of distinct energized pixels in each dimension that are displayed), dot pitch (the distance between energized subpixels of the same color in millimeters), refresh rate (the number of times in a second that a display is illuminated), response time (the time a pixel in a monitor takes to go from active (white) to inactive (black) and back to active (white) again, measured in milliseconds), contrast ratio (the ratio of the luminosity of the brightest color (white) to that of the darkest color (black) that the display is capable of producing), delta-E (color accuracy measured in delta-E), and viewing angle (the maximum angle at which an image on a display can be viewed, without excessive image degradation). 
     The sensed ESD parameter can be any suitable parameter for determining power consumption and/or accessible energy storage device capacity. Typically, the sensed ESD parameter is one or more of voltage, capacitance, inductance, current in and/or out of the energy storage device, charge cycle, current drain or energy discharge rate, energy storage device temperature, state of charge, depth of discharge, and state of health (a defined measurement of the overall condition of a battery). 
     In a first example of power management operation, a first portion of the primary and/or secondary display is energized differently than a second portion of the primary and/or secondary display. Typically, energy (e.g., amperes) applied per unit area to the first portion is no more than about 95%, more typically no more than about 85%, more typically no more than about 75%, and even more typically no more than about 50% of the energy applied per unit area to the second portion. The amount of energization applied to each of the first and second portions, and the difference between the relative degrees of energization of the portions, may be a function of a sensed ESD parameter and/or its relationship to plural thresholds. 
     Throughout the examples, with reference to  FIGS. 49-53  the “first portion” refers to the shaded portion or area of the display while the second portion refers to the unshaded portion or area of the display. 
     In a second example, typically at least most, more typically at least about 75%, and even more typically at least about 95% of the display elements in a first portion of the primary and/or secondary display has a black color while at least most, more typically at least about 75%, and even more typically at least about 95% of the display elements in a second portion of the primary and/or secondary display has a color other than black. For instance, the first portion may have a black background with white lettering while the second portion has a white background with black lettering. A black color is less energy consumptive to produce compared to a white color. The colors of each of the first and second portions, and the relative spectral difference between the colors, may be a function of a sensed ESD parameter and/or its relationship to plural thresholds. 
     In a third example, a first portion of the primary and/or secondary display has a display resolution lower than more typically no more than about 95%, more typically no more than about 85%, more typically no more than about 75%, and even more typically no more than about 50% of a display resolution of a second portion of the primary and/or secondary display. In one application, this is effected by having different pixel sizes for at least most of the pixels in the first portion relative to at least most of the pixels in the second portion. The display resolution of each of the first and second portions, and the relative difference between the display resolutions of the portions, may be a function of a sensed ESD parameter and/or its relationship to plural thresholds. 
     In a fourth example, a first portion of the primary and/or secondary display has a dot pitch greater than and more typically at least about 125% of a dot pitch of a second portion of the primary and/or secondary display. The dot pitch of each of the first and second portions, and the relative difference between the dot pitches of the portions, may be a function of a sensed ESD parameter and/or its relationship to plural thresholds. 
     In a fifth example, typically at least most, more typically at least about 75%, and even more typically at least about 95% of the display elements in a first portion of the primary and/or secondary display has a refresh rate lower than more typically no more than about 95%, more typically no more than about 85%, more typically no more than about 75%, and even more typically no more than about 50% of the display elements in a second portion of the primary and/or secondary display. The refresh rate of each of the first and second portions, and the relative difference between the refresh rates of the portions, may be a function of a sensed ESD parameter and/or its relationship to plural thresholds. 
     In a sixth example, typically at least most, more typically at least about 75%, and even more typically at least about 95% of the display elements in a first portion of the primary and/or secondary display has a response time lower than more typically no more than about 95%, more typically no more than about 85%, more typically no more than about 75%, and even more typically no more than about 50% of the display elements in a second portion of the primary and/or secondary display. The response time of each of the first and second portions, and the relative difference between the response times of the portions, may be a function of a sensed ESD parameter and/or its relationship to plural thresholds. 
     In a seventh example, typically at least most, more typically at least about 75%, and even more typically at least about 95% of the display elements in a first portion of the primary and/or secondary display has a luminance (or intensity or brightness) lower than, more typically no more than about 95%, more typically no more than about 85%, more typically no more than about 75%, and even more typically no more than about 50% of a luminance (or intensity or brightness) of typically at least most, more typically at least about 75%, and even more typically at least about 95% of the display elements in a second portion of the primary and/or secondary display. The luminance (or intensity or brightness) of each of the first and second portions, and the relative difference between the luminance (or intensity or brightness) of the portions, may be a function of a sensed ESD parameter and/or its relationship to plural thresholds. For instance, the first portion can appear to be dimmed relative to the second portion. The displayed image, though dimmed in the first portion, can still be visible to the user. 
     In an eighth example, a first portion of the primary and/or secondary display has a contrast ratio lower than, more typically no more than about 95%, more typically no more than about 85%, more typically no more than about 75%, and even more typically no more than about 50% of a contrast ratio of a second portion of the primary and/or secondary display. The contrast ratio of each of the first and second portions, and the relative difference between the contrast ratios of the portions, may be a function of a sensed ESD parameter and/or its relationship to plural thresholds. 
     In a ninth example, typically at least most, more typically at least about 75%, and even more typically at least about 95% of the display elements in a first portion of the primary and/or secondary display has a delta-E lower than, more typically no more than about 95%, more typically no more than about 85%, more typically no more than about 75%, and even more typically no more than about 50% of a delta-E of typically at least most, more typically at least about 75%, and even more typically at least about 95% of the display elements in a second portion of the primary and/or secondary display. The delta-E of each of the first and second portions, and the relative difference between the delta-E values of the portions, may be a function of a sensed ESD parameter and/or its relationship to plural thresholds. 
     In a tenth example, the power management module  592  causes the multi-display management module  524 , application manager  562 , and/or display controller  544 , as appropriate, to enable a multi-screen application to operate in a single screen mode only and disables a composite display mode. As a consequence, the multi-screen application would essentially become a single-screen application. 
     In an eleventh example, the power management module  592  causes the multi-display management module  524 , application manager  562 , and/or display controller  544 , as appropriate, to further require multi- and single-screen applications to use only one (the primary) display  110  in the primary screen  104 . The other (secondary) display  114  in the secondary screen  108  would essentially be disabled. This example would apply even when the communication device  100  is in the opened position or state. 
     In a twelfth example, the aspect ratio and/or viewable image size of the primary and secondary displays  110  and  114  are the same in a first mode and different in a second mode. This example is particularly beneficial in a smart pad (“SP”)  1000  having an SP touch sensitive display  1010 . By way of illustration, assume at a first time the ESD has a first value of an ESDM sensed ESD parameter (e.g., remaining charge) above (or below) a selected threshold and at a later second time the ESD has a second value of the ESDM sensed ESD parameter (below (or above) the selected threshold. The change in the ESDM sensed ESD parameter value indicates that ESD charge has dropped to an unsatisfactory level. In response, the power management module  592  causes the multi-display management module  524  and/or display controller  544 , as appropriate, to redefine the aspect ratios and/or viewable image sizes of first and second virtual segmented displays of the SP touch sensitive display  1010  from being equal to unequal. Referring to  FIG. 50 , the seam  3612  is depicted at the first time in a center position such that the first and second aspect ratios of application areas  1  and  2  are approximately equivalent. At the second time associated with  FIG. 49 , the seam  3612  is moved to the right making the aspect ratio and/or viewable image size of application  1  (which is the fully active display segment) (represented by the unshaded area) smaller than that of application  2  (which is now a partially active or fully inactive display segment) (represented by the shaded area). At a third later time the ESD has dropped below a third threshold, and, as shown by  FIG. 51 , the seam  3612  is moved to the left making the aspect ratio and/or viewable image size of application  1  (which is the fully active display segment) (represented by the unshaded area) smaller than that of application  2  (which is the partially active or fully inactive display segment) (represented by the shaded area). At a fourth later time the ESD has dropped below a fourth threshold, and, as shown by  FIG. 52 , the seam  3612  is moved to the center making the aspect ratio and/or viewable image size of application  1  substantially the same as that of application  2 . However, to decrease power consumption over a prior stage of operation, the active display area  5200   a  and  5200   b , in total, (represented by the unshaded area) is smaller than that of either application areas shown in  FIG. 50 . The exterior of the display (represented by the shaded area) is now only partially active or fully inactive, thereby conserving energy. The steps described can progressively decrease power consumption, thereby prolonging ESD life. {general trend is active display area grows smaller as ESD capacity decreases and vice versa} 
     “Partially inactive” commonly means that one or more of display resolution, dot pitch, refresh rate, response time, contrast ratio, delta-E, and/or viewing angle is different between the fully active and partially inactive display areas. By way of illustration, the fully active display area has a display resolution, refresh rate, response time, contrast ratio, delta-E, and/or viewing angle that is greater than (and typically about 25% greater than) the corresponding display resolution, refresh rate, response time, contrast ratio, delta-E, and/or viewing angle of the partially inactive display area. In a further illustration, the fully active display area has a dot pitch that is less than (and typically no more than about 75% of) a dot pitch of the partially inactive display area. 
     In a thirteenth example, common digital data output of an application is provided to the framework  520  and at least some of a first portion of the digital data output to be displayed by the first portion of the display is assigned a different display parameter (e.g., luminance, brightness, and/or color) than a second portion of the digital data output to be displayed by the second portion of the display. For vector-type digital images, a portion of the vector values can be changed, and for raster-type digital images, pixel values can be changed. This can cause displayed images of the same type to appear or be rendered differently by the first and second display portions. 
     In a further example, various thresholds are selected and, when each threshold is reached, changes are made to the display and/or displayed images to save energy over the previous stage. For instance, when a first threshold is reached a first set of display parameters are implemented that differ from a previously used original set of display parameters. When a second threshold is reached a different second set of display parameters are implemented that differ from the first set of display parameters. The first and second set of display parameters can have common display parameter members and one or more uncommon display parameter members or no common display parameter members. The net result is that a level of energy used to provide the user with the display and/or displayed image before the first threshold is reached is greater than a level of energy used to provide the user with the display and/or displayed image after the first set of display parameters are implemented. Similarly, the level of energy used to provide the user with the display and/or displayed image using the first set of display parameters is greater than that used to provide the user with the display and/or displayed image using the second set of display parameters. The reverse is also true. When the ESD is charged, the display parameters are altered in a reverse manner in response to the ESD state exceeding the second and first thresholds. In other words, when the ESD state exceeds the second threshold the first set of display parameters are used instead of the second set of display parameters. When the ESD state exceeds the first threshold, the original set of display parameters are used instead of the first set of display parameters. 
     The use of thresholds can be applied to any of the above examples. 
     The above examples can be used to produce different display types. With reference to  FIG. 52 , the first portion is located exteriorly of the second portion, such that the viewable area and viewing angle of the second portion is less than the entire display area when not in power saving mode. This display type can be used to display an application control window or other displayed image through the first portion, such as for a VoIP or cellular call application when an incoming call is received, an interrupt when a trigger event occurs, an application window, such as a window in minimized mode, a virtual numeric, alphabetical, or alphanumeric keypad, a virtual set of controls, or other displayed image that occupies less than the entire display area. Although the displayed image is shown as spanning the seam and occupying both displays, the displayed image may be located in a portion of only one display. With reference to  FIG. 53 , the first portion is located interiorly of the second portion to reveal tool bar, menu bar, task bar, quick launch bar, tray, notification area, and other command menus and options, which are typically located around the exterior of the display. 
     As will be appreciated, the various examples are not discrete but may be combined in a given application. When one or more display parameters are different between the first and second portions of the display, the other display parameters typically remain substantially the same. 
     A method according to an embodiment will now be discussed with reference to  FIG. 54 . 
     In step  5400 , a stimulus is detected by the multi-display management module  524 , display configuration module  568 , windows management module  532 , and/or display controller(s)  544 . The stimulus can be, for example, user input, a sensed ESD parameter absolutely or relative to a selected threshold (received from the ESDM) (e.g., thet sensed ESD parameter falls below or rises above a selected threshold), an application requirement, and the like. User input can be, for example, user preferences, user selection of the first portion or a feature of the first portion, user selection of a power conservation mode, user selection of a multi-screen application, user request to remove the power conservation mode, and the like. The sensed ESD parameter can be any one or more of the parameters noted above. The application requirement can be a multi-screen application or a single-screen application. 
     In response, the multi-display management module  524 , display configuration module  568 , windows management module  532 , and/or display controller(s)  544 , in step  5404 , determines a current display state, including display mode (e.g., single or dual displays currently enabled), display parameters (any of the display parameters noted above), and currently displayed application type (single- or multi-screen application), of one or both of the touch sensitive display(s) and/or current ESD state (e.g., as defined by any of the ESD parameters noted above). 
     In step  5408 , the multi-display management module  524 , display configuration module  568 , windows management module  532 , and/or display controller(s)  544  determines other parameters impacting the touch sensitive display configuration. Other parameters include user defined display and/or displayed image preferences. 
     In step  5412 , the multi-display management module  524 , display configuration module  568 , windows management module  532 , and/or display controller(s)  544  determine applicable rules regarding touch sensitive displays and/or displayed images. Rules include implementing one or more of the display parameter changes or other requirements referenced above in the examples. 
     In decision diamond  5416 , the multi-display management module  524 , display configuration module  568 , windows management module  532 , and/or display controller(s)  544  determine, based on a mapping of the collected information in steps  5404  and  5408 , whether to change the touch sensitive display(s) and/or displayed image(s). 
     When the current configuration(s) of the touch sensitive display(s) and/or displayed image(s) are not to be changed, control passes to step  5400  to await a next stimulus. 
     When the current configuration(s) of the touch sensitive display(s) and/or displayed image(s) are to be changed, control passes to step  5420 , where the multi-display management module  524 , display configuration module  568 , windows management module  532 , and/or display controller(s)  544  effects the requisite changes to one or more selected touch sensitive displays and/or displayed images. Control then passes to step  5400 . 
     As will be appreciated, any of the above embodiments and configurations can be applied to physically or logically different displays that are on common or different screens. The embodiments and configurations also apply to landscape and portrait modes and maximized and minimized displayed images. 
     The exemplary systems and methods of this disclosure have been described in relation to a smartphone, smartpad, and interaction with the devices. However, to avoid unnecessarily obscuring the present disclosure, the preceding description omits a number of known structures and devices. This omission is not to be construed as a limitation of the scopes of the claims. Specific details are set forth to provide an understanding of the present disclosure. It should however be appreciated that the present disclosure may be practiced in a variety of ways beyond the specific detail set forth herein. 
     For example, the present disclosure may be used not only with smart phones and tablet computers but also with other types of computational or processing devices, particularly those with multiple displays, such as an ereader, laptop, and personal computer. 
     In a further example, the smartphone, smartpad (or tablet computer), ereader, laptop, personal computer, or other computational device could have multiple physical and/or logical screens/displays. Additionally, the smartphone, smartpad (or tablet computer), ereader, laptop, personal computer, or other computational device could be used with one or more input devices such as a stylus, mouse, or the like. Moreover, the smartpad (or tablet computer), ereader, laptop, personal computer, or other computational device could be populated with a processor, memory, communications means and the like that would allow for stand-alone operation. Even further, the smartpad (or tablet computer), ereader, laptop, personal computer, or other computational device could be associated or docked with other types of communications devices such as a smartphone such that the smartpad (or tablet computer), ereader, laptop, personal computer, or other computational device could be used as a display and/or I/O interface therefore. 
     Furthermore, while the exemplary aspects, embodiments, and/or configurations illustrated herein show the various components of the system collocated, certain components of the system can be located remotely, at distant portions of a distributed network, such as a LAN and/or the Internet, or within a dedicated system. Thus, it should be appreciated, that the components of the system can be combined in to one or more devices, such as a tablet-like device, or collocated on a particular node of a distributed network, such as an analog and/or digital telecommunications network, a packet-switch network, or a circuit-switched network. It will be appreciated from the preceding description, and for reasons of computational efficiency, that the components of the system can be arranged at any location within a distributed network of components without affecting the operation of the system. For example, the various components can be located in a switch such as a PBX and media server, gateway, in one or more communications devices, at one or more users&#39; premises, or some combination thereof. Similarly, one or more functional portions of the system could be distributed between a telecommunications device(s) and an associated computing device. 
     Furthermore, it should be appreciated that the various links connecting the elements can be wired or wireless links, or any combination thereof, or any other known or later developed element(s) that is capable of supplying and/or communicating data to and from the connected elements. These wired or wireless links can also be secure links and may be capable of communicating encrypted information. Transmission media used as links, for example, can be any suitable carrier for electrical signals, including coaxial cables, copper wire and fiber optics, and may take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications. 
     Also, while the flowcharts have been discussed and illustrated in relation to a particular sequence of events, it should be appreciated that changes, additions, and omissions to this sequence can occur without materially affecting the operation of the disclosed embodiments, configuration, and aspects. 
     In yet another embodiment, the systems and methods of this disclosure can be implemented in conjunction with a special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element(s), an ASIC or other integrated circuit, a digital signal processor, a hard-wired electronic or logic circuit such as discrete element circuit, a programmable logic device or gate array such as PLD, PLA, FPGA, PAL, special purpose computer, any comparable means, or the like. In general, any device(s) or means capable of implementing the methodology illustrated herein can be used to implement the various aspects of this disclosure. Exemplary hardware that can be used for the disclosed embodiments, configurations and aspects includes computers, handheld devices, telephones (e.g., cellular, Internet enabled, digital, analog, hybrids, and others), and other hardware known in the art. Some of these devices include processors (e.g., a single or multiple microprocessors), memory, nonvolatile storage, input devices, and output devices. Furthermore, alternative software implementations including, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein. 
     In yet another embodiment, the disclosed methods may be readily implemented in conjunction with software using object or object-oriented software development environments that provide portable source code that can be used on a variety of computer or workstation platforms. Alternatively, the disclosed system may be implemented partially or fully in hardware using standard logic circuits or VLSI design. Whether software or hardware is used to implement the systems in accordance with this disclosure is dependent on the speed and/or efficiency requirements of the system, the particular function, and the particular software or hardware systems or microprocessor or microcomputer systems being utilized. 
     In yet another embodiment, the disclosed methods may be partially implemented in software that can be stored on a storage medium, executed on programmed general-purpose computer with the cooperation of a controller and memory, a special purpose computer, a microprocessor, or the like. In these instances, the systems and methods of this disclosure can be implemented as program embedded on personal computer such as an applet, JAVA® or CGI script, as a resource residing on a server or computer workstation, as a routine embedded in a dedicated measurement system, system component, or the like. The system can also be implemented by physically incorporating the system and/or method into a software and/or hardware system. 
     Although the present disclosure describes components and functions implemented in the aspects, embodiments, and/or configurations with reference to particular standards and protocols, the aspects, embodiments, and/or configurations are not limited to such standards and protocols. Other similar standards and protocols not mentioned herein are in existence and are considered to be included in the present disclosure. Moreover, the standards and protocols mentioned herein and other similar standards and protocols not mentioned herein are periodically superseded by faster or more effective equivalents having essentially the same functions. Such replacement standards and protocols having the same functions are considered equivalents included in the present disclosure. 
     The present disclosure, in various aspects, embodiments, and/or configurations, includes components, methods, processes, systems and/or apparatus substantially as depicted and described herein, including various aspects, embodiments, configurations embodiments, subcombinations, and/or subsets thereof. Those of skill in the art will understand how to make and use the disclosed aspects, embodiments, and/or configurations after understanding the present disclosure. The present disclosure, in various aspects, embodiments, and/or configurations, includes providing devices and processes in the absence of items not depicted and/or described herein or in various aspects, embodiments, and/or configurations hereof, including in the absence of such items as may have been used in previous devices or processes, e.g., for improving performance, achieving ease and\or reducing cost of implementation. 
     The foregoing discussion has been presented for purposes of illustration and description. The foregoing is not intended to limit the disclosure to the form or forms disclosed herein. In the foregoing Detailed Description for example, various features of the disclosure are grouped together in one or more aspects, embodiments, and/or configurations for the purpose of streamlining the disclosure. The features of the aspects, embodiments, and/or configurations of the disclosure may be combined in alternate aspects, embodiments, and/or configurations other than those discussed above. This method of disclosure is not to be interpreted as reflecting an intention that the claims require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed aspect, embodiment, and/or configuration. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate preferred embodiment of the disclosure. 
     Moreover, though the description has included description of one or more aspects, embodiments, and/or configurations and certain variations and modifications, other variations, combinations, and modifications are within the scope of the disclosure, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights which include alternative aspects, embodiments, and/or configurations to the extent permitted, including alternate, interchangeable and/or equivalent structures, functions, ranges or steps to those claimed, whether or not such alternate, interchangeable and/or equivalent structures, functions, ranges or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter.