Patent Description:
End users have more electronic device choices than ever before. A number of prominent technological trends are currently afoot and these trends are changing the electronic device landscape. Some of the technological trends involve clamshell devices. Generally, clamshell devices are devices where a first housing is rotatably coupled to a second housing. For example, a laptop, notebook computer, etc., is a small, portable personal computer with a clamshell form factor typically having a computer display mounted on the inside of an upper first housing of the clamshell and an alphanumeric keyboard on the inside of a lower second housing of the clamshell. The clamshell device is opened to use the device and folded shut for transportation or storage.

<CIT> discloses systems and methods for hinge actions and virtual extended display modes for a multi-form factor Information Handling System (IHS). In an embodiment, an IHS may include: a processor; and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the IHS to: detect a change in an angle of a hinge coupling a first display to a second display; and in response to the detection, provide a Graphical User Interface (GUI) feature.

The invention is defined in the appended independent claims. Advantageous, optional features of the invention are then set out in the appended dependent claims.

The FIGURES of the drawings are not necessarily drawn to scale, as their dimensions can be varied considerably without departing from the scope of the present disclosure.

The following detailed description sets forth examples of apparatuses, methods, and systems relating to enabling a system and method for dynamically reconfiguring a display in a multi-display device in accordance with an embodiment of the present disclosure. Features such as structure(s), function(s), and/or characteristic(s), for example, are described with reference to one embodiment as a matter of convenience; various embodiments may be implemented with any suitable one or more of the described features.

In the following description, various aspects of the illustrative implementations will be described using terms commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. However, it will be apparent to those skilled in the art that the embodiments disclosed herein may be practiced with only some of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth in order to provide a thorough understanding of the illustrative implementations. However, it will be apparent to one skilled in the art that the embodiments disclosed herein may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the illustrative implementations.

In the following detailed description, reference is made to the accompanying drawings which form a part hereof, wherein like numerals designate like parts throughout, and in which is shown by way of illustration, embodiments in which the subject matter of the present disclosure may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. For the purposes of the present disclosure, the phrase "A or B" means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase "A, B, or C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).

The description may use perspective-based descriptions such as top/bottom, in/out, over/under, and the like. Such descriptions are merely used to facilitate the discussion and are not intended to restrict the application of embodiments described herein to any particular orientation. The description may use the phrase "in an example," which may each refer to one or more of the same or different examples.

The term "coupled with," along with its derivatives, may be used herein. The term "coupled" may mean one or more of the following. The term "coupled" may mean that two or more elements are in direct physical or electrical contact. However, the term "coupled" may also mean that two or more elements indirectly contact each other, but yet still cooperate or interact with each other, and may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term "directly coupled" may mean that two or elements are in direct contact. The term "about" indicates a tolerance of five percent (<NUM>%). For example, about forty-five degrees (<NUM>°) would include forty-five degrees (<NUM>°) and ± <NUM> degrees (<NUM>°) from forty-five degrees (<NUM>°).

<FIG> is a simplified block diagram of an electronic device configured to enable a system and method for dynamically reconfiguring a display in a multi-display device, in accordance with an embodiment of the present disclosure. In an example, electronic device <NUM> can include a first housing <NUM> and a second housing <NUM>. First housing <NUM> can be pivotably coupled to second housing <NUM> using a hinge <NUM>. First housing <NUM> can include a primary display <NUM> and a camera <NUM>. Second housing <NUM> can include a secondary display <NUM>. In some examples, secondary display is a touch display. Electronic device <NUM> may be in communication with cloud services <NUM>, server <NUM>, and/or network elements <NUM> using network <NUM>.

Turning to <FIG> is a simplified block diagram of electronic device <NUM> configured to enable a system and method for dynamically reconfiguring a display in a multi-display device, in accordance with an embodiment of the present disclosure. In an example, electronic device <NUM> can include first housing <NUM> and second housing <NUM>. Electronic device <NUM> can further include hinge <NUM> which pivotably couples first housing <NUM> to second housing <NUM>. First housing <NUM> can include primary display <NUM> and camera <NUM>. Second housing <NUM> can include secondary display <NUM>.

In an example, camera <NUM> can include a head position tracking sensor <NUM> and an eye tracking system <NUM>. Head position tracking sensor <NUM> can be a low power inferred heat position tracking sensor and eye tracking system <NUM> can capture the user's eye(s) position and eye(s) movement to track the user's eye(s). In some examples, camera <NUM> can include an image sensor to capture images or video of the user. In some embodiments, the captured images or video can include the upper torso or head of the user and eye tracking system <NUM> may include head and/or eye tracking software to determine the direction that the user is looking. In some embodiments, eye tracking system <NUM> can include both head and eye tracking software for coarse and fine tracking of where the user is looking and head position tracking sensor <NUM> is not present in electronic device <NUM>. Second housing <NUM> can include touch sensors 126a and 126b, user tracking logic <NUM>, display reconfiguration engine <NUM>, and peripheral detection engine <NUM>. User tracking logic <NUM> can include a secondary sensor <NUM>. In some examples, user tracking logic <NUM> and/or display reconfiguration engine <NUM> may be located in first housing <NUM>. Secondary sensor <NUM> can receive and collect user related data from touch sensors 126a and 126b and peripheral detection engine <NUM>. User tracking logic <NUM> can use data from head position tracking sensor <NUM>, eye tracking system <NUM>, and the user related data from secondary sensor <NUM> to determine an intent of the user. Eye tracking system <NUM>, user tracking logic <NUM>, display reconfiguration engine <NUM>, peripheral detection engine <NUM>, and/or secondary sensor <NUM>, can be software or logic to be run on one or more processors within electronic device <NUM>. Head position tracking sensor may be a combination of hardware and software or may be software to be run on one or more processors within electronic device <NUM>.

Peripheral detection engine <NUM> can detect when a peripheral <NUM> is being used to interact with electronic device <NUM> and when the user is interacting with peripheral <NUM>. For example, as illustrated in <FIG>, peripheral <NUM> may be a peripheral <NUM> being used to interact with primary display <NUM> and/or secondary display <NUM>. In addition, the user may pick up, turn on, activate, or otherwise interact with peripheral <NUM> before interacting with primary display <NUM> and/or secondary display <NUM>. More specifically, peripheral <NUM> may be a stylus and peripheral detection engine <NUM> can detect when peripheral <NUM> being used to interact with primary display <NUM> and/or secondary display <NUM> or, to try an obtain a faster response, peripheral detection engine <NUM> can detect when the user interacts with peripheral <NUM> in anticipation of peripheral <NUM> being used to interact with primary display <NUM> and/or secondary display <NUM>. Peripheral <NUM> is a peripheral input device and/or output device used to interact with primary display <NUM> and/or secondary display <NUM> (e.g., headphones, microphone, mouse, trackpad, image scanner, etc.).

Camera <NUM> can be configured to include software to allow the head position of a user, the face of the user, and/or an eye or eyes of the user to be tracked or can collect data that can be used by electronic device <NUM> to track the head position of a user, the face of the user, and/or an eye or eyes of the user. More specifically, head position tracking sensor <NUM> can be configured to help detect the head position of the user and eye tracking system <NUM> can be configured to help detect the eye or eyes of the user. In some examples, head position tracking sensor <NUM> is an infrared (IR) sensor or some other relatively lower power head position tracking sensor that uses less power than eye tracking system <NUM>. Secondary display <NUM> can be a touch display. Electronic device <NUM> can include a peripheral detection engine <NUM> configured to detect whether one or more palms or fingers of the user are touching the touch display. In another embodiment, electronic device <NUM> can include one or more touch sensors 126a and 126b on secondary display <NUM>. In some examples, one or more touch sensors 126a and 126b can be disposed near an edge of secondary display <NUM>. Touch sensors 126a and 126b can be configured to detect the presence of the user's palms or hands. For example, one or more touch sensors 126a and 126b may be disposed where a user would normally place their palms when typing on a virtual keyboard displayed on secondary display <NUM>. Peripheral detection engine <NUM>, is configured to determine when peripheral <NUM> is being used to interact with primary display <NUM> and/or secondary display <NUM>.

User tracking logic <NUM> can be configured to use camera <NUM>, head position tracking sensor <NUM>, and/or eye tracking system <NUM>, to help determine a head position of the user, a location of the face of the user, a location of an eye or eyes of the user, determine a gaze of the user, and/or other features of a user. Peripheral detection engine <NUM> can be used to supply supplemental information to user tracking logic <NUM> to determine the intent of the user, the head position of the user, the location of the face of the user, the location of an eye or eyes of the user, determine the gaze of the user, and/or other features of a user. The term "gaze" refers to a position of the head of the user relative to primary display <NUM>, a position of the user's eyes relative to primary display <NUM>, a pupil orientation relative to primary display <NUM>, and/or a relative distance of the user's face and eyes from primary display <NUM>. User tracking logic <NUM> can determine the user's intent based on the detected user's head position, palm position, face, eyes, the user related data from secondary sensor <NUM> and/or other features of the user. User tracking logic <NUM> can determine the gaze of the user and if the user is looking at primary display <NUM>, secondary display <NUM>, or towards some other area (e.g., to a person standing next to electronic device <NUM> or something in the distance and past or above electronic device <NUM> like a window or television device).

User tracking logic <NUM> can communicate data about the intent of the user (e.g., relative head position, relative face position, relative eye position, etc. to primary display <NUM>, palm position, the user's interaction with a peripheral, etc.) to display reconfiguration engine <NUM>. Display reconfiguration engine <NUM> can be configured to receive the data about the intent of the user from user tracking logic <NUM> and determine if the configuration of primary display <NUM> and/or secondary display <NUM> should be changed. If the configuration of primary display <NUM> and/or secondary display <NUM> should be changed, then display reconfiguration engine <NUM> can change the configuration of primary display <NUM> and/or secondary display <NUM>. In some examples, the change in configuration is a change from a first user interface configuration (e.g., a keyboard user interface configuration) to a different second user interface configuration (e.g., a notetaking user interface configuration).

In an illustrative example, a user may be looking at secondary display <NUM> in a note taking configuration and taking notes and then looks at primary display <NUM> to use an Internet browsing application and tries to use a touchpad on secondary display <NUM> to move a cursor on primary display <NUM> or to type content into primary display <NUM> using secondary display <NUM>. However, in some current systems, the current systems do not know that the user has started looking at primary display <NUM> and secondary display <NUM> does not change configuration from a note taking configuration to a keyboard and touchpad configuration and continues to be in the note taking configuration. This can result in a bad user experience.

Another issue with current systems is when the user continuously looks at primary display <NUM> and is not using secondary display <NUM> but secondary display <NUM> continues to display content and consume power. This can cause unnecessary power loss and reduces battery life. User tracking logic <NUM> can detect the user's head position, palm position, face, eyes, and/or other features of the user, and based on the data from head position tracking sensor <NUM>, eye tracking system <NUM>, and the user related data from secondary sensor <NUM>, user tracking logic <NUM> can determine the intent of the user and if the user is looking at primary display <NUM>, secondary display <NUM>, or towards some other area. Display adjustment engine <NUM> can be configured to receive the data about the intent of the user from user tracking logic <NUM> and determine if the configuration of primary display <NUM> and/or secondary display <NUM> should be changed. More specifically, display reconfiguration engine <NUM> can be configured to receive the data about the intent of the user from user tracking logic <NUM> and determine that an application on primary display <NUM> and/or secondary display <NUM> should be changed, the user interface configuration on primary display <NUM> and/or the user interface configuration of secondary display <NUM> should change, or primary display <NUM> and/or secondary display <NUM> should enter into a low power configuration or standby mode to conserve power and/or battery. In some examples, the relatively low power head position tracking sensor <NUM> can be used to determine the user's intent. In other examples, palm detection areas 126a and 126b and/or peripheral detection engine <NUM> are used to determine the user's intent or to supplement data from head position tracking sensor <NUM> to determine the user's intent. If user tracking logic <NUM> cannot use head position tracking sensor <NUM>, touch sensors 126a and 126b, and/or peripheral detection engine <NUM> to determine a user's intent, then eye tracking system <NUM> is used to determine the user's intent.

It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present disclosure. Substantial flexibility is provided by electronic device <NUM> in that any suitable arrangements and configuration may be provided without departing from the teachings of the present disclosure.

As used herein, the term "when" may be used to indicate the temporal nature of an event. For example, the phrase "event 'A' occurs when event 'B' occurs" is to be interpreted to mean that event A may occur before, during, or after the occurrence of event B, but is nonetheless associated with the occurrence of event B. For example, event A occurs when event B occurs if event A occurs in response to the occurrence of event B or in response to a signal indicating that event B has occurred, is occurring, or will occur. Reference to "one embodiment" or "an embodiment" in the present disclosure means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase "in one embodiment" or "in an embodiment" are not necessarily all referring to the same embodiment.

Elements of <FIG> and <FIG> may be coupled to one another through one or more interfaces employing any suitable connections (wired or wireless), which provide viable pathways for network (e.g., network <NUM>, etc.) communications. Additionally, any one or more of the elements of <FIG> may be combined or removed from the architecture based on particular configuration needs. Network <NUM> may include a configuration capable of transmission control protocol/Internet protocol (TCP/IP) communications for the transmission or reception of packets in a network. Electronic device <NUM> may also operate in conjunction with a user datagram protocol/IP (UDP/IP) or any other suitable protocol where appropriate and based on particular needs.

For purposes of illustrating certain example techniques of electronic device <NUM>, the following foundational information may be viewed as a basis from which the present disclosure may be properly explained. Generally, clamshell devices are devices where a first housing is pivotably coupled to a second housing. For example, a clamshell device can be a laptop, notebook computer or other a small, portable personal computer with a clamshell form factor typically having a computer display mounted on the inside of an upper first housing of the clamshell and an alphanumeric keyboard on the inside of a lower second housing of the clamshell. The clamshell is opened to use the device and folded shut for transportation or storage.

Dual display devices are becoming more popular and getting more attention. Having two displays can often provide a relatively good user experience and can help increase productivity by allowing a device to operate in a tablet configuration, a notebook configuration, a tent configuration, a laptop configuration, etc. One use case for dual display devices is in a clam shell configuration where the primary display is used as a lid to display content and the secondary display is used as a base for either an on-screen keyboard and touchpad, to display full video, or an application on the display without an on-screen keyboard and touchpad. In cases where the user is using both displays for displaying content and not using the secondary display as keyboard and touchpad, the user may turn their face upwards to view the primary display or turn their face downwards to view the secondary display. Based on the intent of the user and/or the user's head and eye position, the secondary display needs to change quickly to either a keyboard and touchpad configuration or a full display screen configuration for application content.

In some examples, when the gaze of the user and/or the user's head/eye position is upwards and viewing the primary display (e.g., a pitch angle is less than a critical angle), the secondary display should behave like keyboard and touch pad. When the gaze of the user and/or the user's head/eye position is downwards and viewing the secondary display (e.g., a pitch angle is greater than a critical angle), the system should be able to automatically change the secondary display's configuration to a note taking configuration. Currently there is no automated way to do this change of the secondary display for dual display devices. In current devices, the user needs to manually select the configuration of the secondary display to display the keyboard and touch pad, to enter a note taking configuration, to enter a full display configuration for displaying content, or a configuration where half of the display is displaying content or an application and the other half is a keyboard and is with or without a touch pad.

Currently, there are systems with eye tracking to determine an active display. Also, there are systems with head pose estimation, but none of the current systems address the specific problem of a dual display in a clamshell mode. In addition, previous solutions do not address the specific use case of a dual display in clamshell mode where a specific switching of configurations is needed between a keyboard and touchpad configuration and a full screen content display configuration or a note taking configuration. Further, some current systems do not allow for power saving to be achieved by keeping the non-engaged display in a low power state by lowering the brightness and refresh rate or forcing the system to a panel self-refresh state or configuration. Also, most current systems use eye tracking but current eye tracking systems can be power and computation hungry and may not be needed in all cases as head pose estimation may be enough to determine a user's intent in some use cases. Hence a combination of head and eye tracking is needed. What is needed is a system and method to allow for dynamically reconfiguring a display in a multi-display device.

A device to help facilitate a system and method for dynamically reconfiguring a display in a multi-display device, as outlined in <FIG> and <FIG>, can resolve these issues (and others). In an example, an electronic device (e.g., electronic device <NUM>) can include a system and method for dynamically reconfiguring a display in a multi-display device that can adjust the configuration of one or more displays based on a intent of the user (e.g., the relative distance of the user's face and eyes from the display, the position of the eyes relative to the display, the pupil orientation relative to the display, and/or the position of the head of the user relative to the display). The adjustment of the configuration of one or more displays based on the user's intent may be automatic and performed without requiring the user to manually adjust the configuration of one or more displays. More specifically, cameras, IR sensors, and/or eye tracking systems can be used to monitor and measure the eye pupil of a user and/or the face angle of the user and use the information to determine the user's gaze and based on the user's gaze, determine the user's intent, and automatically adjust the configuration of one or more displays based on the determined user's intent. The configuration of one or more displays can allow the user to use clamshell form factors with greater convenience and comfort as compared to some current devices and can help with power savings. The term "automatically adjust the configuration of one or more displays" means that the user does not need to manually adjust the configuration of one or more displays and the system will adjust the configuration of the one or more displays.

In an example, the system can be configured to use a camera (with minimum resolution and frames per second) with head orientation detection and eye tracking to determine the gaze of the user and the content to be displayed on a secondary display (e.g., either a keyboard and touch pad configuration or a full display screen configuration for applications such as a note taking application). Also, using user tracking logic <NUM> and display reconfiguration engine <NUM>, the system can cause the display that is not engaged with the user to go to a low power mode by lowering the brightness and refresh rate or forcing the system to a panel self-refresh state or configuration (e.g., gradual dimming/PSRl/<NUM>).

The system can include a user facing camera for estimating the head pose or eye tracking or both as a hybrid and to change the secondary display configuration (e.g., either keyboard and touch pad or a full display screen) when the dual display is used in clamshell mode. With the help of the camera and user tracking logic <NUM>, the system can determine head/eye position of the user, the gaze of the user, and whether the user is looking at the primary display or the secondary display.

In an example, if user looks at the primary display, the secondary display automatically changes to a keyboard and touch pad configuration. In the example where a user looks at the secondary display, a full screen configuration can be used for displaying an application such as a note taking application. Also, based on the user's activity, the display that is not engaged with the user can enter into a low power configuration or mode by lowering the brightness and refresh rate or forcing the system to a panel self-refresh state or configuration (e.g., gradual dimming/ PSR1/<NUM>). This allows the system to improve responsiveness, adapt to user's roles, and increases the battery life. It can also provide a better user experience, as the secondary display automatically changes based on the user's engagement.

Power savings can be achieved using a hybrid methodology of head-pose and eye tracking use whichever is relevant based on the position of the user. Continuous eye tracking is not required in most of the use case scenarios. For example, when the user's head is tilted down, the eyes are not visible or when the user's head is tilted upwards the user can only see the primary display. Using only the head position to determine the user's intent can save power compared to continuous eye tracking. Also, adaptive dimming and a low power configuration or mode for the non-engaged display can help to save power.

In an illustrative example, when a user is in front of electronic device <NUM>, the system (e.g., a camera <NUM>, head position tracking sensors <NUM>, eye tracking system <NUM>, touch sensors 126a and 126b, user tracking logic <NUM>, peripheral detection engine <NUM>, etc.) can be configured to detect, determine, and monitor the intent of the user. The data regarding the intent of the user is used to help adjust the configuration of one or more displays, for example, to a note taking application while the user is viewing a lecture or presentation on the primary display. The system can include a user engagement detection engine (e.g., user tracking logic <NUM>) that tracks the user based on the user's head position and eye tracking. Additional inputs from the user, like engagement with the touchscreen of the secondary display (e.g., palms rested while using a virtual keyboard, use of a stylus, etc.) can be used to supplement the tracking methodology. For example, when the user's palms are rested on secondary display, there is no need for eye tracking as the user is most likely engaged with the primary display and the user is typing or preparing to type.

In an illustrative example, a user is sitting in front of a dual display device. The system is used in clamshell mode, both displays are on, and an application or applications are opened on both displays. For example, the primary display can display web browsing and the secondary display can be used in a virtual keyboard configuration. A user tracking engine (e.g., user tracking logic <NUM>) can determine the use's intent and if the user is engaged with the primary display or the secondary display. In some examples, to determine the intent of the user, the following priority may be used, first head tracking (pitch angle comparison with critical angle), then palm detection and palm resting on secondary display and peripheral detection, and finally eye tracking (pitch angle comparison with critical angle).

If the user's head/eye position is greater than a critical angle, the system can dim the primary display and allow the secondary display to have full power to allow the user to use an application on the secondary display (e.g., the note taking application). If the user's head/eye position is less than a critical angle, then the system can determine that the user is engaged with primary display. The system can make the secondary display enter a keyboard and touch pad configuration and dim the secondary display for power savings and the primary display will operate and without any brightness changes.

Regarding the palm rest detection, the system can use the palm rest status to determine the user's intention. For example, the user's head position may be upwards, eye balls looking down (like a peeping or thief look). In this example, if the palms are rested on the secondary display, the relative power-hungry eye tracking can be ignored or not used and the system may use the head position only to determine the user's intent. If the user's palms are not rested on the secondary display, then the system can determine that the user intends to see the content on the secondary display. In some examples, artificial intelligence and deep learning can be used to improve the accuracy. In a clamshell mode, palm resting percentage is lot higher due to the secondary display being mostly used as a keyboard for typing. In this example, the head position tracking percentage is more dominant than the head and eye tracking percentage. Since the system is tracking mostly the head position, the power saving will be more compared to eye tracking, as eye tracking consumes a greater amount of power than tracking the head position.

There will be some corner cases like typing without resting the palms etc. and to address the corner cases and the false detections, artificial intelligence and deep learning can be used. Artificial intelligence can be combined with deep learning methodologies where the typing behavior or usage behavior of a large number of users can be used to train a deep learning engine so that the system can infer the best possible outcome to avoid the false detection. In some examples, cloud services <NUM>, server <NUM>, and/or network element <NUM> can include a network false detection engine that includes the artificial intelligence and deep learning methodologies. The network false detection engine can use network <NUM> to collect data and employ deep learning methodologies to try and mitigate or reduce the amount of false detections. In addition, the user can be given an option to switch configurations manually with stroke keys in case of the false detection.

Turning to the infrastructure of <FIG>, network <NUM> represents a series of points or nodes of interconnected communication paths for receiving and transmitting packets of information. Network <NUM> offers a communicative interface between nodes, and may be configured as any local area network (LAN), virtual local area network (VLAN), wide area network (WAN), wireless local area network (WLAN), metropolitan area network (MAN), Intranet, Extranet, virtual private network (VPN), and any other appropriate architecture or system that facilitates communications in a network environment, or any suitable combination thereof, including wired and/or wireless communication.

In network <NUM>, network traffic, which is inclusive of packets, frames, signals, data, etc., can be sent and received according to any suitable communication messaging protocols. Suitable communication messaging protocols can include a multi-layered scheme such as Open Systems Interconnection (OSI) model, or any derivations or variants thereof (e.g., Transmission Control Protocol/Internet Protocol (TCP/IP), user datagram protocol/IP (UDP/IP)). Messages through the network could be made in accordance with various network protocols, (e.g., Ethernet, Infiniband, OmniPath, etc.). Additionally, radio signal communications over a cellular network may also be provided. Suitable interfaces and infrastructure may be provided to enable communication with the cellular network.

The term "packet" as used herein, refers to a unit of data that can be routed between a source node and a destination node on a packet switched network. A packet includes a source network address and a destination network address. These network addresses can be Internet Protocol (IP) addresses in a TCP/IP messaging protocol. The term "data" as used herein, refers to any type of binary, numeric, voice, video, textual, or script data, or any type of source or object code, or any other suitable information in any appropriate format that may be communicated from one point to another in electronic devices and/or networks.

In an example implementation, electronic device <NUM>, is meant to encompass a computer that has a clamshell form factor, a laptop or electronic notebook, network elements that have a clamshell form factor, or any other device, component, element, or object that has a clamshell form factor, design, profile, etc. Electronic device <NUM> may include any suitable hardware, software, components, modules, or objects that facilitate the operations thereof, as well as suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information. Electronic device <NUM> may include virtual elements.

In regards to the internal structure, electronic device <NUM> can include memory elements for storing information to be used in the operations outlined herein. Electronic device <NUM> may keep information in any suitable memory element (e.g., random access memory (RAM), read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), application specific integrated circuit (ASIC), etc.), software, hardware, firmware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein should be construed as being encompassed within the broad term `memory element. ' Moreover, the information being used, tracked, sent, or received could be provided in any database, register, queue, table, cache, control list, or other storage structure, all of which can be referenced at any suitable timeframe. Any such storage options may also be included within the broad term `memory element' as used herein.

In certain example implementations, the functions outlined herein may be implemented by logic encoded in one or more tangible media (e.g., embedded logic provided in an ASIC, digital signal processor (DSP) instructions, software (potentially inclusive of object code and source code) to be executed by a processor, or other similar machine, etc.), which may be inclusive of non-transitory computer-readable media. In some of these instances, memory elements can store data used for the operations described herein. This includes the memory elements being able to store software, logic, code, or processor instructions that are executed to carry out the activities described herein.

In an example implementation, electronic device <NUM> may include software modules (e.g., user tracking logic <NUM>, display reconfiguration engine <NUM>, etc.) and/or circuity and logic to achieve, or to foster, operations as outlined herein. These modules may be suitably combined in any appropriate manner, which may be based on particular configuration and/or provisioning needs. In example embodiments, such operations may be carried out by hardware, implemented externally to these elements, or included in some other network device to achieve the intended functionality. Furthermore, the modules can be implemented as software, hardware, firmware, or any suitable combination thereof. These elements may also include software (or reciprocating software) that can coordinate with other network elements in order to achieve the operations, as outlined herein.

Additionally, electronic device <NUM> may include a processor that can execute software or an algorithm to perform activities as discussed herein. A processor can execute any type of instructions associated with the data to achieve the operations detailed herein. In one example, the processors could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array (FPGA), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM)) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof. Any of the potential processing elements, modules, and machines described herein should be construed as being encompassed within the broad term 'processor.

Turning to <FIG> a simplified diagram of a user's head <NUM> is show with illustrative details in accordance with an embodiment of the present disclosure. In an example, user's head <NUM> can include a yaw axis <NUM> and a pitch axis <NUM>. User's head <NUM> is rotated on yaw axis <NUM> when user's head <NUM> is moved to the left or right. User's head <NUM> is rotated on pitch axis <NUM> when user's head is moved up and down. User's head <NUM> can also include a roll axis (not shown).

In an illustrative example, a primary display center plane <NUM> can be defined as an axis that is relative to primary display <NUM> when the user is looking at a middle portion of primary display <NUM> or the user's gaze is towards a middle portion of primary display <NUM>. The user can rotate user's head <NUM> on pitch axis <NUM> up or down relative to primary display center plane <NUM> to view primary display <NUM>. For example, the user may rotate user's head <NUM> up an upper angle <NUM> on pitch axis <NUM> to upper critical plane <NUM>. If the user rotates user's head <NUM> past upper critical plane <NUM>, the user will no longer be looking at primary display <NUM> but instead will be looking over display <NUM>. In addition, the user may rotate user's head <NUM> down a downward angle <NUM> on pitch axis <NUM> to lower critical plane <NUM>. If the user rotates user's head <NUM> past lower critical plane <NUM>, the user will no longer be looking at primary display <NUM> but instead the user's gaze will be down and the user will be looking at lower display <NUM>.

Turning to <FIG> is a simplified diagram of a user's head <NUM> is show with illustrative details in accordance with an embodiment of the present disclosure. In an example, user's head <NUM> can include yaw axis <NUM> and pitch axis <NUM>. User's head <NUM> is rotated on yaw axis <NUM> when user's head <NUM> is moved to the left or right. User's head <NUM> is rotated on pitch axis <NUM> when user's head is moved up and down. In an illustrative example, primary display center plane <NUM> can be defined as an axis that is relative to primary display <NUM> when the user is looking at a middle portion of primary display <NUM> or the user's gaze is towards a middle portion of primary display <NUM>. The user can rotate user's head <NUM> on pitch axis <NUM> up or down relative to primary display center plane <NUM>. If the user rotates user's head <NUM> past upper critical plane <NUM>, the user will no longer be looking at primary display <NUM> but instead the user's gaze will be past upper critical plane <NUM> and the user will be looking over primary display <NUM>, as illustrated in <FIG>.

Turning to <FIG> is a simplified diagram of a user's head <NUM> is show with illustrative details in accordance with an embodiment of the present disclosure. In an example, user's head <NUM> can include yaw axis <NUM> and pitch axis <NUM>. User's head <NUM> is rotated on yaw axis <NUM> when user's head <NUM> is moved to the left or right. User's head <NUM> is rotated on pitch axis <NUM> when user's head is moved up and down. In an illustrative example, primary display center plane <NUM> can be defined as an axis that is relative to primary display <NUM> when the user is looking at a middle portion of primary display <NUM> or the user's gaze is towards a middle portion of primary display <NUM>. The user can rotate user's head <NUM> on pitch axis <NUM> up or down relative to primary display center plane <NUM>. If the user rotates user's head <NUM> past lower critical plane <NUM>, the user will no longer be looking at primary display <NUM> but instead the user's gaze will be past lower critical plane <NUM> and the user will be looking at secondary display <NUM>, as illustrated in <FIG>.

Turning to <FIG> is a simplified diagram of a user's head <NUM> is show with illustrative details in accordance with an embodiment of the present disclosure. In an example, user's head <NUM> can include yaw axis <NUM> and pitch axis <NUM>. User's head <NUM> is rotated on yaw axis <NUM> when user's head <NUM> is moved to the left or right. User's head <NUM> is rotated on pitch axis <NUM> when user's head is moved up and down. In an illustrative example, the user can rotate user's head <NUM> on yaw axis <NUM> left or right relative to primary display center plane <NUM> to view primary display <NUM>. For example, the user may rotate user's head <NUM> to the left on yaw axis <NUM> to left critical plane <NUM> or to the right on yaw axis <NUM> to right critical plane <NUM>. If the user rotates user's head <NUM> past left critical plane <NUM> or past right critical plane <NUM>, the user will no longer be looking at primary display <NUM> but instead will be looking to the left of primary display <NUM> or to the right of primary display <NUM>. For example, as illustrated in <FIG>, the user's gaze is past right critical plane <NUM> and the user is looking to the right past right critical plane <NUM> and is not looking at primary display <NUM>.

Turning to <FIG> is a simplified block diagram of a portion of electronic device <NUM> configured to include a system and method for dynamically reconfiguring a display in a multi-display device. In an example, electronic device <NUM> can include first housing <NUM> and second housing <NUM>. First housing <NUM> can be pivotably coupled to second housing <NUM> using hinge <NUM>. First housing <NUM> can include primary display <NUM> and camera <NUM>. Second housing <NUM> can include secondary display <NUM>. When the user is looking at electronic device <NUM>, primary display center plane <NUM> can be defined as an axis that is relative to primary display <NUM> when the user is looking at a middle portion of primary display <NUM> or the user's gaze is towards a middle portion of primary display <NUM>. The user can rotate user's head <NUM> on pitch axis <NUM> up or down relative to primary display center plane <NUM> to view primary display <NUM>. For example, the user may rotate user's head <NUM> up an upper angle <NUM> on pitch axis <NUM> to upper critical plane <NUM>. If the user rotates user's head <NUM> past upper critical plane <NUM>, the user will no longer be looking at primary display <NUM> but instead the gaze of the user will be past upper critical plane <NUM> and the user will be looking over primary display <NUM>. In addition, the user may rotate user's head <NUM> down a downward angle <NUM> on pitch axis <NUM> to lower critical plane <NUM>. If the user rotates user's head <NUM> past lower critical plane <NUM>, the user will no longer be looking at primary display <NUM> but instead the gaze of the user will be past lower critical plane <NUM> and the user will be looking at secondary display <NUM>. <FIG> illustrates where user is using both displays for displaying applications. More specifically, as illustrated in <FIG>, primary display <NUM> is being used for web browsing or other content and secondary display <NUM> is being used as a keyboard.

Turning to <FIG> is a simplified block diagram of a portion of electronic device <NUM> configured to include a system and method for dynamically reconfiguring a display in a multi-display device. In an example, electronic device <NUM> can include first housing <NUM> and second housing <NUM>. First housing <NUM> can be pivotably coupled to second housing <NUM> using hinge <NUM>. First housing <NUM> can include primary display <NUM> and camera <NUM>. Second housing <NUM> can include secondary display <NUM>. When the user is looking at electronic device <NUM>, primary display center plane <NUM> can be defined as an axis that is relative to primary display <NUM> when the user is looking at a middle portion of primary display <NUM> or the user's gaze is towards a middle portion of primary display <NUM>. The user can rotate user's head <NUM> on pitch axis <NUM> up or down relative to primary display center plane <NUM>. For example, the user may rotate user's head <NUM> down on pitch axis <NUM> past lower critical plane <NUM> and the user will no longer be looking at primary display <NUM> but instead will be looking at lower display <NUM>. More specifically, as illustrated in <FIG>, the user is no longer looking at primary display <NUM> but instead the gaze of the user is past lower critical plane <NUM> and the user is looking at secondary display <NUM> while primary display <NUM> is displaying a lecture or presentation. Display reconfiguration engine <NUM> can be configured to cause secondary display <NUM> to be configured as a full screen with a note taking application and allow the user to take notes during the lecture or presentation.

In an example, the system can be configured to use camera <NUM> and user tracking logic <NUM> to determine head/eye position. Display reconfiguration engine <NUM> can be configured to receive data from user tracking logic <NUM> and change the contents and/or power level of primary display <NUM> and/or secondary display <NUM>. When the user's head/eye position is upwards and viewing primary display <NUM>, display reconfiguration engine <NUM> can be configured to change the configuration of secondary display <NUM> to a keyboard and/or touch pad configuration. When the user's head/eye position is downwards and viewing secondary display <NUM>, display reconfiguration engine <NUM> can be configured to cause secondary display <NUM> to be configured as a full screen with a note taking application. As user tracking logic <NUM> is continuously monitoring the user's head/eye position, display reconfiguration engine <NUM> can dynamically change to configuration and behavior of primary display <NUM> and/or secondary display <NUM>. In some examples, camera <NUM> can be running at a minimal FPS and resolution based on the usage and head/eye tracking.

Turning to <FIG> is a simplified block diagram of a portion of electronic device 100a configured to include a system and method for dynamically reconfiguring a display in a multi-display device. In an example, electronic device 100a can include first housing 102a, second housing 104a, and third housing <NUM>. First housing 102a can be pivotably coupled to second housing 104a using hinge 106a. Third housing <NUM> can be rotatably coupled to second housing 104a using second hinge <NUM>. First housing 102a can include primary display 108a and camera <NUM>. Second housing <NUM> can include secondary display 110a. Third housing <NUM> can include third display <NUM>. In one configuration of electronic device 100a, the combination of second housing <NUM> and third housing <NUM> may be relatively the same size and/or form factor as first housing 102a such that first housing <NUM> can pivot or rotate over second housing <NUM> and third housing <NUM> in a closed clamshell configuration. In other configurations of electronic device 100a, one or more of first housing 102a, second housing <NUM>, and third housing <NUM> can be relatively the same size and/or form factor.

User's head <NUM> can include yaw axis <NUM> and pitch axis <NUM>. The user can rotate user's head <NUM> on pitch axis <NUM> up or down. to view primary display 108a. For example, the user may rotate user's head <NUM> between primary display upper critical plane <NUM> and primary display lower critical plane <NUM> to view primary display 108a. If the user rotates user's head <NUM> past primary display upper critical plane <NUM>, the user will no longer be looking at primary display 108a but instead will be looking over primary display 108a. In addition, the user may rotate user's head <NUM> down to primary display lower critical plane <NUM>. If the user rotates user's head <NUM> past primary display lower critical plane <NUM>, the user will no longer be looking at primary display 108a but instead will be looking at secondary display 110a. The user may rotate user's head <NUM> between primary display lower critical plane <NUM> and second display lower critical plane <NUM> to view secondary display 110a. While viewing secondary display 110a, if the user rotates user's head <NUM> up past primary display lower critical plane <NUM>, the user will no longer be looking at secondary display 110a but instead will be looking at primary display 108a. In addition, while viewing secondary display 110a, the user may rotate user's head <NUM> down to second display lower critical plane <NUM>. If the user rotates user's head <NUM> past second display lower critical plane <NUM>, the user will no longer be looking at secondary display 110a but instead will be looking at third display <NUM>. The user may rotate user's head <NUM> between second display lower critical plane <NUM> and third display lower critical plane <NUM> to view third display <NUM>. While viewing third display <NUM>, if the user rotates user's head <NUM> up past second display lower critical plane <NUM>, the user will no longer be looking at third display <NUM> but instead will be looking at secondary display 110a. In addition, while viewing third display <NUM>, the user may rotate user's head <NUM> down to third display lower critical plane <NUM>. If the user rotates user's head <NUM> past third display lower critical plane <NUM>, the user will no longer be looking at third display <NUM> but instead will be looking past third display <NUM> (e.g., at a surface supporting electronic device 100a). Based on the intent of the user and/or other features of a user, the configuration and/or power state of primary display 108a, secondary display 110a, and/or third display <NUM> can be changed.

Turning to <FIG> is an example flowchart illustrating possible operations of a flow <NUM> that may be associated with enabling a system and method for dynamically reconfiguring a display in a multi-display device, in accordance with an embodiment. The flowchart may be implemented in computer readable instructions which may be executed by a processor within an electronic device having multiple displays. In one example, at least one of the displays is a touch display. In an embodiment, one or more operations of flow <NUM> may be performed by user tracking logic <NUM> or display reconfiguration engine <NUM>. At block <NUM>, user tracking logic <NUM> determines that the user is actively engaged with a primary display of the electronic device. Active engagement can mean that the user's focus is on the primary display or that the user intends to interact with the primary display. The user's focus on the primary display can be the user viewing an application outputted on the primary display. Similarly, the user's intent to interact with the primary display can be the user interacting with an application outputted on the primary display. At block <NUM>, user tracking logic <NUM> periodically identifies the display that the user is actively engaged in. At block <NUM>, user tracking logic <NUM> detects whether the display that the user is actively engaged with has changed. If there is no change, use tracking logic <NUM> returns to block <NUM>. If a change is detected, user tracking logic <NUM> notifies display reconfiguration engine <NUM> of the change at block <NUM>. At block <NUM>, display reconfiguration engine can reconfigure one or more displays of the electronic device. Reconfiguration of the one or more displays can be to improve the user experience or to improve the power savings of electronic device. In one example, display reconfiguration engine <NUM> may reduce the power consumption of the display that the user is no longer actively engaged in. Reduction of the power consumption can include reducing the refresh cycle of the display panel, reducing the brightness or luminance of the display panel, or reducing the resolution of the display panel. In display panels that can partially dim, reduction of the power consumption can include reducing the brightness or luminance of portions of the display panel. In another example, display reconfiguration engine <NUM> may increase the power consumption of the display that the user is now actively engaged in. This may be to improve the user experience by improving the brightness, luminance, refresh cycle, or resolution of the display that the user is actively engaged with. While brightness, luminance, refresh cycle, and resolution are mentioned here, it's clear to those of skill in the art that display reconfiguration engine <NUM> may also alter other properties of the display to either improve the visual appearance of the display or to reduce the power consumption of the display.

Turning to <FIG> is an example flowchart illustrating possible operations of a flow <NUM> that may be associated with enabling a system and method for dynamically reconfiguring a display in a multi-display device, in accordance with an embodiment. In an embodiment, one or more operations of flow <NUM> may be performed by user tracking logic <NUM> or display reconfiguration engine <NUM>. At <NUM>, a dual display device in a clamshell mode has a first application being displayed on a first display (e.g., primary display <NUM>) and a second application being displayed on a second display (e.g., secondary display <NUM>). At <NUM>, the system detects that the user is viewing the first application that is displayed on the first display. At <NUM>, the system determines if the user is engaged with the first application on the first display. For example, the system may determine that the user is no longer viewing the first application that is displayed on the first display. If the user is engaged with the first application on the first display, then the displays do not change, as in <NUM>. If the user is not engaged with the first application on the first display, then the first application that is displayed on the first display changes, the second application that is displayed on the second display changes, the first display enters into a low power mode, and/or the second display enters into a low power mode. The system can determine the intent of the user and if the user is engaged with the first application on the first display using data from head position tracking sensor <NUM>, eye tracking system <NUM>, and the user related data from secondary sensor <NUM> to determine an intent of the user.

Turning to <FIG> is an example flowchart illustrating possible operations of a flow <NUM> that may be associated with enabling a system and method for dynamically reconfiguring a display in a multi-display device, in accordance with an embodiment. In an embodiment, one or more operations of flow <NUM> may be performed by user tracking logic <NUM> or display reconfiguration engine <NUM>. At <NUM>, a device with a first area having a first configuration and a second area having a second configuration is accessed by a user. At <NUM>, the user is viewing the first area with the first configuration. At <NUM>, the system determines if the area where the user is looking changes (the gaze of the user changes). If the system determines that the area where the user is looking does not change, then the system again determines if the area where the user is looking changes, as in <NUM>. If the system determines that the area where the user is looking does change, then the configuration of the second area is changed, as in <NUM>. At <NUM>, the system determines if the configuration of the first area needs to be changed. If the configuration of the first area needs to be changed, then the configuration of the first area is changed, as in <NUM>. If the configuration of the first area does not need to be changed, then the process ends.

Turning to <FIG> is an example flowchart illustrating possible operations of a flow <NUM> that may be associated with enabling a system and method for dynamically reconfiguring a display in a multi-display device, in accordance with an embodiment. In an embodiment, one or more operations of flow <NUM> may be performed by user tracking logic <NUM> or display reconfiguration engine <NUM>. At <NUM>, a device with at least a first display and a second display is accessed by a user. At <NUM>, the device determines that the user is engaged with the first display. At <NUM>, the device determines if the user switched to engaging with the second display. If the user did not switch to engaging with the second display, then the device again determines if the user switched to engaging with the second display, as in <NUM>. If the device determines the user switched to engaging with the second display, then a configuration (e.g., typing user interface configuration, note taking user interface configuration, etc.) or mode of the second display is changed, as in <NUM>. The system can determine if the user switched to engaging with the second display by using data from head position tracking sensor <NUM>, eye tracking system <NUM>, and the user related data from secondary sensor <NUM> to determine an intent of the user.

Turning to <FIG> is an example flowchart illustrating possible operations of a flow <NUM> that may be associated with enabling a system and method for dynamically reconfiguring a display in a multi-display device, in accordance with an embodiment. In an embodiment, one or more operations of flow <NUM> may be performed by user tracking logic <NUM> or display reconfiguration engine <NUM>. At <NUM>, a device with a first display and a second display is accessed by a user. At <NUM>, the user is engaged with the first display and the second display has a first input configuration (e.g., typing user interface configuration, note taking user interface configuration, etc.) or mode. At <NUM>, the system determines if the user switched to engaging with the second display. If the user did not switch to engaging with the second display, then the system again determines if the user switched to engaging with the second display, as in <NUM>. If the user switched to engaging with the second display, then the input configuration of the second display is changed to a second configuration (e.g., changed from a typing user interface configuration to a note taking user interface configuration), as in <NUM>. At <NUM>, the system determines if the user switched to engaging with the first display. If the user did not switch to engaging with the first display, then the system again determines if the user switched to engaging with the first display, as in <NUM>. If the user switched to engaging with the first display, then the input configuration of the second display is changed to the first input configuration (e.g., changed from a note taking user interface configuration to a typing user interaction configuration), as in <NUM>. The system can determine if the user switched to engaging with the second display by using data from head position tracking sensor <NUM>, eye tracking system <NUM>, and the user related data from secondary sensor <NUM> to determine an intent of the user.

Turning to <FIG> is an example flowchart illustrating possible operations of a flow <NUM> that may be associated with enabling a system and method for dynamically reconfiguring a display in a multi-display device, in accordance with an embodiment. In an embodiment, one or more operations of flow <NUM> may be performed by user tracking logic <NUM> or display reconfiguration engine <NUM>. At <NUM>, a device with a first display and a second display is accessed by a user. At <NUM>, the system determines if head position estimation can be used to determine the display the user is viewing and intent of the user. If head position estimation can be used to determine the display the user is viewing and the intent of the user, then head position estimation is used to determine the display the user is viewing and the intent of the user, as in <NUM>. If head position estimation cannot be used to determine the display the user is viewing and the intent of the user, then the system determines if data from a secondary sensor can be used to determine the display the user is viewing and the intent of the user, as in <NUM>. If the data from the secondary sensor can be used to determine the display the user is viewing and the intent of the user, then the data from the secondary sensor is used to determine the display the user is viewing and the intent of the user, as in <NUM>. If the data from the secondary sensor cannot be used to determine the display the user is viewing and the intent of the user, then the system determines if eye tracking can be used to determine the display the user is viewing and the intent of the user, as in <NUM>. If eye tracking can be used to determine the display the user is viewing and the intent of the user, then eye tracking is used to determine the display the user is viewing and the intent of the user, as in <NUM>. If eye tracking cannot be used to determine the display the user is viewing and the intent of the user, then an error message is generated, as in <NUM>. The system can determine the display the user is viewing and the intent of the user by using data from head position tracking sensor <NUM>, eye tracking system <NUM>, and the user related data from secondary sensor <NUM>.

Turning to <FIG> is an example flowchart illustrating possible operations of a flow <NUM> that may be associated with enabling a system and method for dynamically reconfiguring a display in a multi-display device, in accordance with an embodiment. In an embodiment, one or more operations of flow <NUM> may be performed by user tracking logic <NUM> or display reconfiguration engine <NUM>. At <NUM>, a device with a first display and a second display is accessed by a user. At <NUM>, the system determines if the display the display the user is viewing can be determined by head tracking and/or data from a secondary sensor. If the display the user is viewing can be determined by head tracking and/or data from a secondary sensor, then the display the user is viewing is determined by head tracking and/or the secondary sensor, as in <NUM>. If the display the user is viewing cannot be determined by head tracking and/or data from the secondary sensor, then the display the user is viewing is determined by eye tracking, as in <NUM>. Secondary sensor <NUM> can received user related data from touch sensors 126a and 126b and peripheral detection engine <NUM> and the data can be used by user tracking logic <NUM> to determine the display the user is viewing or the data can be used to supplement data from head position tracking sensor <NUM> to determine the display the user is viewing.

Turning to <FIG> is an example flowchart illustrating possible operations of a flow <NUM> that may be associated with enabling a system and method for dynamically reconfiguring a display in a multi-display device, in accordance with an embodiment. In an embodiment, one or more operations of flow <NUM> may be performed by user tracking logic <NUM> or display reconfiguration engine <NUM>. At <NUM>, a device with a first display and a second display is accessed by a user. At <NUM>, the system determines if the display the user is viewing can be determined by eye tracking. If the display the user is viewing can be determined by eye tracking, then the display the user is viewing is determined by eye tracking, as in <NUM>. If the display the user is viewing cannot be determined by eye tracking, then the display the user is viewing is determined by head tracking and/or data from a secondary sensor, as in <NUM>. Secondary sensor <NUM> can received user related data from touch sensors 126a and 126b and peripheral detection engine <NUM> and the data can be used by user tracking logic <NUM> to determine the display the user is viewing or the data can be used to supplement data from head position tracking sensor <NUM> to determine the display the user is viewing.

It is also important to note that the operations described above and in the preceding flow diagram (i.e., <FIG>) illustrate only some of the possible correlating scenarios that may be executed by, or within, electronic device <NUM>. Some of these operations may be deleted or removed where appropriate, or these operations may be modified or changed considerably without departing from the scope of the present disclosure. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by electronic device <NUM> in that any suitable arrangements, chronologies, configurations, and mechanisms may be provided without departing from the teachings of the present disclosure.

Although the present disclosure has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the present disclosure. Moreover, certain components may be combined, separated, eliminated, or added based on particular needs and implementations. Additionally, although electronic device <NUM> has been illustrated with reference to particular elements and operations that facilitate a system and method for dynamically reconfiguring a display in a multi-display device, these elements and operations may be replaced by any suitable architecture, protocols, and/or processes that achieve the intended functionality of electronic device <NUM>.

Claim 1:
An electronic device (<NUM>) having at least two displays, the electronic device comprising:
a primary display (<NUM>) housed in a first housing (<NUM>);
a secondary display (<NUM>) housed in a second housing (<NUM>);
a hinge (<NUM>) coupling the first housing to the second housing;
a user facing camera (<NUM>) housed in the first housing to capture image data of a user of the electronic device, the user facing camera configured with a head position tracking sensor (<NUM>) and an eye tracking system (<NUM>), wherein the image data describes a head position of the user tracked by head position tracking sensor, and eye gaze of the user tracked by the eye tracking system;
user tracking logic (<NUM>) to determine, based on the image data and sensor data describing a user action, that a user of the electronic device is engaged with or about to engage with the secondary display; and
reconfiguration logic (<NUM>) to reconfigure at least one of the primary display and the secondary display in response to the determination,
wherein the second housing includes at least one palm detection area to generate the sensor data to determine a presence of user's palm or palms; F H
the device being characterized by:
if a presence of the user's palm or palms is detected resting on the secondary display, the device is configured to not use the eye tracking system to track the eye gaze of the user, and to use the head position tracking sensor to only track the head position of the user to determine the user's intent.