Patent Grant
11233923
Modern information handling devices (“devices”), for example smart phones, tablets, laptop and personal computers, other electronic devices, and the like, comprise a front-facing camera integrated into the device that is capable of capturing images, videos, etc. Conventionally, most front-facing cameras were integrated into a top portion of the bezel that surrounds a display screen of the device. Advances in technology have led to near bezel-less displays, where the display screen occupies nearly the entire front area of the device. Accordingly, in these situations, many bezel-less, or near bezel-less, devices integrate the front-facing camera into a notch that protrudes down from the top of the device into an upper portion of the display screen area.
In summary, one aspect provides a method, comprising: receiving, at an information handling device, an indication to activate a camera positioned underneath a display portion of the information handling device; identifying, using a processor, a location of at least one pixel on the display portion positioned overtop the camera; disabling, based on the identifying, the at least one pixel; performing, subsequent to the disabling and using the camera, a function; and enabling, responsive to identifying that the function was performed, the at least one pixel.
Another aspect provides an information handling device, comprising: a display portion; a camera positioned underneath the display portion; a processor; a memory device that stores instructions executable by the processor to: receive an indication to active the camera; identify a location of at least one pixel on the display portion positioned overtop the camera; disable, based on the identifying, the at least one pixel; perform, subsequent to the disabling and using the camera, a function; and enable, responsive to identifying that the function was performed, the at least one pixel.
A further aspect provides a product, comprising: a storage device that stores code, the code being executable by a processor and comprising: code that receives an indication to activate a camera positioned underneath a display portion of an information handling device; code that identifies a location of at least one pixel on the display portion positioned overtop the camera; code that disables, based on the identifying, the at least one pixel; code that performs, subsequent to the disabling and using the camera, a function; and code that enables, responsive to identifying that the function was performed, the at least one pixel.
The foregoing is a summary and thus may contain simplifications, generalizations, and omissions of detail; consequently, those skilled in the art will appreciate that the summary is illustrative only and is not intended to be in any way limiting.
For a better understanding of the embodiments, together with other and further features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying drawings. The scope of the invention will be pointed out in the appended claims.
It will be readily understood that the components of the embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations in addition to the described example embodiments. Thus, the following more detailed description of the example embodiments, as represented in the figures, is not intended to limit the scope of the embodiments, as claimed, but is merely representative of example embodiments.
Reference throughout this specification to “one embodiment” or “an embodiment” (or the like) means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearance of the phrases “in one embodiment” or “in an embodiment” or the like in various places throughout this specification are not necessarily all referring to the same embodiment.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that the various embodiments can be practiced without one or more of the specific details, or with other methods, components, materials, et cetera. In other instances, well known structures, materials, or operations are not shown or described in detail to avoid obfuscation.
Many devices, smart phones in particular, are moving toward a bezel-less display. Such a design may not only be aesthetically pleasing to a user but may also allow applications to leverage their utility across a greater surface area. Another advantage may be that a user may be provided with a larger screen in a smaller package. However, the current trend of integrating the front-facing camera (“camera”) into a notch (i.e., an area that extends down from the top of the device into a portion of the display area) prevents a full bezel-less display from being achieved.
One potential method of removing the notch is to situate the camera underneath the display area. This configuration may allow the display area to be fully extended up to the top of the device, thereby allowing the display area to occupy all, or nearly all, of the front region of the device. However, one issue with this solution is that the light capturing abilities of the camera are degraded by the pixels situated in front it. Additionally, if the pixels are white/emitting, i.e., for organic light-emitting diode (OLED) displays, the degradation may be 100% because each pixel in an OLED display provides its own illumination.
Accordingly, an embodiment provides a method for disabling one or more pixels positioned in front of a display-covered camera during image/video capture. In an embodiment, an indication may be received at the device to activate a camera (e.g., a front-facing camera, etc.). The camera may be positioned underneath one or more pixels of a display area of the device. An embodiment may identify a location of the pixels positioned above the camera and thereafter disable (i.e., turn off) those pixels. Subsequent to disabling the pixels, an embodiment may perform a function using the camera (e.g., capture an image, a video, perform another function, etc.). Responsive to identifying that the function is performed, an embodiment may thereafter enable the disabled pixels. Such a method may allow a device to achieve a substantially bezel-less design while also preserving the functionality of the camera.
The illustrated example embodiments will be best understood by reference to the figures. The following description is intended only by way of example, and simply illustrates certain example embodiments.
While various other circuits, circuitry or components may be utilized in information handling devices, with regard to smart phone and/or tablet circuitry 100, an example illustrated in
There are power management chip(s) 130, e.g., a battery management unit, BMU, which manage power as supplied, for example, via a rechargeable battery 140, which may be recharged by a connection to a power source (not shown). In at least one design, a single chip, such as 110, is used to supply BIOS like functionality and DRAM memory.
System 100 typically includes one or more of a WWAN transceiver 150 and a WLAN transceiver 160 for connecting to various networks, such as telecommunications networks and wireless Internet devices, e.g., access points. Additionally, devices 120 are commonly included, e.g., an image sensor such as a camera, audio capture device such as a microphone, motion sensor such as an accelerometer or gyroscope, etc. System 100 often includes one or more touch screens 170 for data input and display/rendering. System 100 also typically includes various memory devices, for example flash memory 180 and SDRAM 190.
The example of
In
In
The system, upon power on, may be configured to execute boot code 290 for the BIOS 268, as stored within the SPI Flash 266, and thereafter processes data under the control of one or more operating systems and application software (for example, stored in system memory 240). An operating system may be stored in any of a variety of locations and accessed, for example, according to instructions of the BIOS 268. As described herein, a device may include fewer or more features than shown in the system of
Information handling device circuitry, as for example outlined in
Referring now to
In an embodiment, the indication may be derived from a user-command to activate the camera. In one non-limiting example, a user may provide touch input to a camera application icon displayed on the display screen. As another non-limiting example, a user may provide a voice command (e.g., to an audio capture device operatively coupled to the device, etc.) to activate the camera. Alternatively, an embodiment may derive this indication dynamically from context analysis. For example, an embodiment may automatically activate a camera responsive to detecting that a user is within a predetermined threshold distance from the device (e.g., using one or more proximity sensors, using data gathered by other devices and transmitted to the device, etc.). In another non-limiting example, an embodiment may automatically activate a camera responsive to detecting that the device is in a camera-activating orientation (e.g., a user has raised their device from a horizontal position to a vertical position, etc.).
At 302, an embodiment may identify a location and/or numbers of pixels on the display portion that are situated overtop the camera. In an embodiment, the foregoing pixel data may be specific to each device, or each device type, and may be programmed and stored in a database. More particularly, the database may comprise information associated with the size and location of the camera for each device as well as identifying information regarding the pixels situated above the camera. An embodiment may thereafter be able to refer to this database to identify which pixels are located above the camera. For example, a camera sensor of a device may comprise an approximate 4 mm radius. For a screen density of 500 ppi (20 ppmm2), the 4 mm radius may correspond to an area on the display surface comprising about 1000 pixels. The identity and/or location of these 1000 pixels may be identified and thereafter stored in the database. In an embodiment, the database may be stored locally, on the device, or may be stored at a remote storage location (e.g., on another device or server, etc.) and accessible by the device via a wired or wireless connection.
At 303, an embodiment may disable the pixels identified as being on the display area positioned on top of the camera. In the context of this application, disabled pixels may refer to pixels that have become transparent (e.g., pixels that do not emit any light or pixels which are not being illuminated by any light, etc.). In an embodiment, the process for making the crystals transparent may be dependent on the type of display screen positioned over the camera. For example, in the case of a light-emitting diode (LED) display screen, disabling a pixel may refer to the deactivation of the particular light-emitting diodes that may illuminate the pixels positioned above the camera. As another example, in the case of an organic light-emitting diode (OLED) display screen, disabling a pixel may refer to the severance of an electrical current to the particular pixels positioned above the camera. In both of the aforementioned examples, other pixels on the display may remain enabled while the pixels located above the camera are disabled. More particularly, an illumination source or an electrical current may be actuated on or against all other pixels while an illumination source or an electrical current is not actuated on or against the pixels above the camera.
In an embodiment, the pixels may be disabled for the duration of time that the camera is activated. In an embodiment, the camera may be considered activated when it is actively in use (e.g., while the camera is capturing images, recording video, performing another function, etc.), when an application that utilizes the camera is in use, etc. Responsive to identifying that the camera is no longer active, the pixels may be reactivated. For example, the pixels may be deactivated while a front-facing setting in a camera application is active and thereafter reactivated responsive to detecting that the camera application is no longer active or that the front-facing setting on the camera application is no longer active.
In an embodiment, responsive to receiving the indication to activate a camera, an embodiment may initiate a one-handed mode setting. In an embodiment, the one-handed mode setting may adjust the dimensional characteristics and/or layout of an active display area so that a user may more easily interact with applications in the display area by utilizing only one hand. For example, an embodiment may decrease the size of the display area to 75% of its normal size and move the reduced display area toward a bottom portion of the device. This may allow a user to more easily interact with an application by using their thumb and also ensure that the reduced display area is not in the camera area. Furthermore, in an embodiment, some or all pixels outside of the reduced display area may be deactivated. In this situation, all portions of the display area outside of the reduced display may appear black. The deactivation of pixels in these other areas may lessen the visual impact of just deactivating the pixels situated on top of the camera. In an embodiment, the one-handed mode may be automatically activated without the receipt of additional user input. For example, the one-handed mode may automatically activate when the indication to activate the camera is received. Alternatively, an embodiment may query the user (e.g., by an audio or visual notification query, etc.) whether they want to enter one-handed mode while the camera is active. Responsive to receiving confirmation input from the user, an embodiment may initiate one-handed mode. In an embodiment, the one-handed mode may be automatically deactivated responsive to identifying that the camera is no longer activated. In this sense, an embodiment may reactivate any and all pixels that were deactivated outside the border of the reduced display area.
In an embodiment, a plurality of other pixels, not directly above the camera, may also be disabled to form a predetermined pattern. A motivation for this may be to reduce the potential aesthetic disturbance the disabling of a plurality of pixels on an edge to edge display may cause. Accordingly, an embodiment may disable certain other pixels surrounding the pixels positioned above the camera in order to form a predetermined shape or device feature. For example, an embodiment may disable the pixels directly above and around the camera in order to form a shape such as a circle, rectangle, star, etc. As another example, a plurality of other pixels located at the top of the display area may be deactivated to form the appearance of a conventional notch. Other shapes, patterns, and designs not explicitly mentioned here may also be utilized as long as the shape, pattern or design covers all of pixels overtop of the camera. In an embodiment, the shape or device feature formed by the deactivation of the other pixels may be originally set by a manufacturer and thereafter adjusted by a user.
In an embodiment, the deactivation of pixels of the pixels above the camera may cause applications to adjust one of more of their characteristics (e.g., location, behavior, etc.). For example, responsive to receiving an indication to activate a camera, the OS/framework may report that there is a notch and applications should behave accordingly (e.g., applications should not display content on a portion occupied by the simulated notch, applications should adjust a top border of the application window to terminate below a bottom edge of the simulated notch, etc.). In an embodiment, when the camera is deactivated, applications may automatically resume their normal functionality.
Responsive to disabling, at 303, the pixels above the camera, an embodiment may, at 304, perform a function using the camera. In an embodiment, the function may be virtually any function for which a camera must be utilized (e.g., an image capture function, a video capture function, a facial recognition function, a gaze tracking function, etc.). Responsive to identifying, at 305, that the function was performed with the camera, an embodiment may, at 307, enable the pixels that were disabled. Conversely, responsive to identifying, at 305, that the function has not yet been performed by the camera, an embodiment may, at 306, keep the pixels disabled.
The various embodiments described herein thus represent a technical improvement to conventional camera utilization techniques. Using the techniques described herein, an embodiment may allow for a substantially bezel-less display area while simultaneously preserving the functionality of a front-facing camera. In an embodiment, the camera may be positioned at a location underneath the display area. More particularly, the pixels of the display area may be positioned overtop a light capturing lens of the camera. Responsive to receiving an indication to activate the camera, an embodiment may disable those pixels identified as being positioned over the lens of the camera, thereby allowing the camera to capture a sufficient amount of light and image data. Once the pixels are disabled, an embodiment may utilize the camera to perform one or more functions. Such a method may preserve the functionality of a camera positioned beneath a display area and also may prevent the degradation of camera image quality when the camera is in use.
As will be appreciated by one skilled in the art, various aspects may be embodied as a system, method or device program product. Accordingly, aspects may take the form of an entirely hardware embodiment or an embodiment including software that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects may take the form of a device program product embodied in one or more device readable medium(s) having device readable program code embodied therewith.
It should be noted that the various functions described herein may be implemented using instructions stored on a device readable storage medium such as a non-signal storage device that are executed by a processor. A storage device may be, for example, a system, apparatus, or device (e.g., an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device) or any suitable combination of the foregoing. More specific examples of a storage device/medium include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a storage device is not a signal and “non-transitory” includes all media except signal media.
Program code embodied on a storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, et cetera, or any suitable combination of the foregoing.
Program code for carrying out operations may be written in any combination of one or more programming languages. The program code may execute entirely on a single device, partly on a single device, as a stand-alone software package, partly on single device and partly on another device, or entirely on the other device. In some cases, the devices may be connected through any type of connection or network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made through other devices (for example, through the Internet using an Internet Service Provider), through wireless connections, e.g., near-field communication, or through a hard wire connection, such as over a USB connection.
Example embodiments are described herein with reference to the figures, which illustrate example methods, devices and program products according to various example embodiments. It will be understood that the actions and functionality may be implemented at least in part by program instructions. These program instructions may be provided to a processor of a device, a special purpose information handling device, or other programmable data processing device to produce a machine, such that the instructions, which execute via a processor of the device implement the functions/acts specified.
It is worth noting that while specific blocks are used in the figures, and a particular ordering of blocks has been illustrated, these are non-limiting examples. In certain contexts, two or more blocks may be combined, a block may be split into two or more blocks, or certain blocks may be re-ordered or re-organized as appropriate, as the explicit illustrated examples are used only for descriptive purposes and are not to be construed as limiting.
As used herein, the singular “a” and “an” may be construed as including the plural “one or more” unless clearly indicated otherwise.
This disclosure has been presented for purposes of illustration and description but is not intended to be exhaustive or limiting. Many modifications and variations will be apparent to those of ordinary skill in the art. The example embodiments were chosen and described in order to explain principles and practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
Thus, although illustrative example embodiments have been described herein with reference to the accompanying figures, it is to be understood that this description is not limiting and that various other changes and modifications may be affected therein by one skilled in the art without departing from the scope or spirit of the disclosure.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7808540 | Cok | Oct 2010 | B2 |
| 9754526 | Evans, V | Sep 2017 | B2 |
| 9843736 | Evans, V | Dec 2017 | B2 |
| 20090009628 | Janicek | Jan 2009 | A1 |
| 20110279689 | Maglaque | Nov 2011 | A1 |
| 20130182062 | Son | Jul 2013 | A1 |
| 20140189583 | Yang | Jul 2014 | A1 |
| 20160349985 | Ibaraki | Dec 2016 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20200314295 A1 | Oct 2020 | US |
