Aod display method and electronic device

Abstract

This application relates to the field of terminal technology, providing an AOD (Always-On Display) method and an electronic device. The electronic device is equipped with a full-screen always-on mode, which means that the electronic device displays a full-screen AOD interface when the screen is off. In this method, when the electronic device is in a screen-off state, it displays the user interface corresponding to the launched application. Then, in response to the screen-off operation, the electronic device switches to displaying the full-screen AOD interface. This application can improve the display effect of full-screen AOD.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to an AOD display method and electronic device. Background Technology

[0002] Currently, electronic devices offer a variety of interaction methods, providing users with a rich experience when using them. Typically, electronic devices can have a screen-on state and a screen-off (or locked) state. In the screen-on state, users can perform various operations on the electronic device; in the screen-off state, the electronic device enters sleep mode. If a user wants to view information such as the time, date, or notifications in the screen-off state, they need to press the power button to trigger the electronic device's saver interface to obtain this information, which is inconvenient for the user.

[0003] As a result, always-on display (AOD) technology emerged, enabling electronic devices to continuously display useful information, such as time, date, and notifications, even when the screen is off. However, AOD technology has limitations in the information it displays and its display quality is not ideal. Summary of the Invention

[0004] This application provides an AOD display method and electronic device to improve the AOD display effect.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, an AOD (Always-On Display) method is provided for use on electronic devices. The electronic device has a full-screen always-on display mode, meaning that the electronic device displays a full-screen AOD interface while the screen is off. In this method, when the screen is off, the electronic device displays the user interface corresponding to the launched application. Subsequently, in response to the screen-off operation, the electronic device switches to displaying the full-screen AOD interface.

[0007] In this application, if a screen-off operation is detected when an electronic device is displaying the interface of a launched application (i.e., the electronic device is forcibly turned off), the electronic device can still return to display the full-screen AOD interface. In other words, as long as the electronic device is forcibly turned off, the full-screen AOD interface will be displayed. This achieves accurate display of the full-screen AOD interface; that is, as long as the electronic device is equipped with the full-screen AOD display function, it can display the full-screen AOD interface when the electronic device is turned off, reducing the occurrence of situations where the full-screen AOD interface cannot be displayed in a timely manner due to the electronic device being turned off, improving the display effect of the full-screen AOD, and thus enhancing the user experience.

[0008] In one possible implementation of the first aspect, the process of the electronic device displaying the user interface may specifically include: when the electronic device is in a screen-off state, in response to the launch operation of any application in the electronic device, the electronic device displays the user interface corresponding to the launched application.

[0009] In one possible implementation of the first aspect, the process of the electronic device displaying the user interface may further include: if the electronic device is in a screen-off state, and the launch operation of any application in the electronic device is detected, the electronic device displays the user interface corresponding to the launched application.

[0010] In this application, the launched application can be launched before the electronic device is in a screen-off state, that is, before the electronic device performs a screen-locking operation, or it can be launched after the electronic device performs a screen-locking operation. In this way, as long as the launched application has an overlay function, the user interface of the launched application can be displayed when the electronic device is in a screen-off state. That is, the electronic device can launch the corresponding application without the user unlocking the device, which simplifies the user's operation steps and improves the user experience.

[0011] In one possible implementation of the first aspect, the aforementioned electronic device includes a system-side overlay state and a lock screen-side overlay state. The system-side overlay state is used to characterize whether the electronic device detects the application launch operation when the electronic device is in a screen-off state. The lock screen-side overlay state is used to characterize whether the electronic device switches to display a full-screen AOD interface.

[0012] In this application, the coverage state of applications in electronic devices is divided into system-side coverage state and lock screen-side coverage state. The attribute value of the system-side coverage state indicates whether the electronic device has detected the application's launch operation, and the attribute value of the lock screen-side coverage state indicates whether the electronic device has switched to displaying a full-screen AOD interface. In this way, the display interface can be accurately displayed, the occurrence of full-screen AOD interface display errors can be reduced, and the display effect of full-screen AOD can be improved.

[0013] In one possible implementation of the first aspect, the process of the electronic device displaying the user interface may specifically include: when the electronic device is in a screen-off state, the electronic device updates the system-side overlay state. Then, when the system-side overlay state is updated to a first value, the electronic device displays the user interface corresponding to the launched application. Here, the system-side overlay state being the first value indicates that the electronic device has detected the launch operation of the launched application.

[0014] In this application, if the electronic device is in a screen-off state and any application in the electronic device is launched, the electronic device can change the system-side overlay state from the second value to the first value to indicate that the electronic device has detected the launch operation of the launched application. Therefore, the electronic device can display the user interface corresponding to the launched application to achieve accurate display of the display interface and reduce the occurrence of situations where an application is launched but the electronic device still displays other interfaces (such as full-screen AOD interface, lock screen interface, etc.), thereby improving the user's interactive experience.

[0015] In one possible implementation of the first aspect, after the electronic device displays the user interface, the method further includes: updating the system-side overlay state in response to an exit operation of the launched application. Then, if the system-side overlay state is updated to a second value, the electronic device updates the lock screen-side overlay state to the second value and displays a full-screen AOD interface. Here, the system-side overlay state being the second value indicates that the electronic device has detected an exit operation of the launched application.

[0016] In this application, if an exit operation of a launched application is detected, it indicates that the user no longer wishes to use the launched application, meaning the electronic device does not need to display the application's interface. Therefore, the electronic device can change the system-side overlay state from a first value to a second value to indicate that the electronic device has detected an exit operation of the launched application. Afterward, the electronic device can switch to displaying a full-screen AOD interface. This achieves precise display of the interface, reduces the likelihood of the electronic device failing to switch to the full-screen AOD interface in a timely manner due to the user wanting to exit the launched application's interface, improves the display effect of the full-screen AOD, and thus enhances the user's interactive experience.

[0017] In one possible implementation of the first aspect, after the electronic device displays the user interface, the method further includes: the electronic device saving the user interface of the launched application.

[0018] In this application, the electronic device can save the user interface of the launched application, which is convenient for subsequent display of the interface. This not only reduces the drawing time of the user interface and improves the display efficiency of the user interface, but also reduces unnecessary resource loss and improves the utilization rate of drawing resources.

[0019] In one possible implementation of the first aspect, the process of the electronic device switching to display a full-screen AOD interface may specifically include: in response to the screen-off operation of the electronic device, the electronic device modifies the screen-side overlay state, and when the screen-side overlay state is modified to a second value, the electronic device switches to display a full-screen AOD interface. Here, the screen-side overlay state being a second value indicates that the electronic device switches to display a full-screen AOD interface.

[0020] In this application, if a screen-off operation is detected while the electronic device is displaying the interface of a launched application, the electronic device can change its screen-locked state from a first value to a second value to indicate that it is switching to display a full-screen AOD interface. Afterwards, the electronic device can switch to displaying the full-screen AOD interface. This achieves precise display of the interface, reduces the occurrence of situations where the electronic device cannot switch to the full-screen AOD interface in a timely manner after the screen is turned off, improves the display effect of the full-screen AOD, and thus enhances the user's interactive experience.

[0021] In one possible implementation of the first aspect, after the aforementioned electronic device switches to display a full-screen AOD interface, the method further includes: in response to the screen-on operation of the electronic device, the electronic device switches to display a user interface.

[0022] In this application, if a screen-on operation is detected while the electronic device is displaying a full-screen AOD interface, the electronic device can return to displaying the user interface of the launched application. This allows the user to continue operating on that user interface without having to reopen the application, thus improving the user experience.

[0023] In one possible implementation of the first aspect, the process of the electronic device switching the display interface may specifically include: in response to the screen-on operation of the electronic device, if the system-side coverage state is a first value and the lock screen-side coverage state is a second value, the electronic device modifies the lock screen-side coverage state, and when the lock screen-side coverage state is modified to the first value, the electronic device switches the display interface. Here, the lock screen-side coverage state being the first value indicates that the electronic device exits the full-screen AOD interface display.

[0024] In this application, during the display of a full-screen AOD interface on an electronic device, if a screen-on operation is detected, and the system-side overlay state is a first value while the lock-screen-side overlay state is a second value, the electronic device can change the lock-screen-side overlay state from the second value to the first value to indicate that the electronic device is exiting the full-screen AOD interface. Afterward, the electronic device can return to displaying the user interface of the launched application. This achieves accurate display of the interface, reduces the occurrence of situations where the user interface cannot be displayed promptly after the screen is turned on, improves the display effect of the electronic device, and thus enhances the user's interactive experience.

[0025] In one possible implementation of the first aspect, the first value mentioned above is true, and the second value mentioned above is false.

[0026] In one possible implementation of the first aspect, after the aforementioned electronic device switches to display a full-screen AOD interface, the method further includes: in response to the screen-on operation of the electronic device, the electronic device displays a lock screen interface.

[0027] In this application, if a screen-on operation is detected while the electronic device is displaying a full-screen AOD interface, the electronic device can display a lock screen interface. This not only makes it easier for users to view notifications or reselect the desired application, reducing the need for additional steps due to exiting the user interface, thus simplifying user operations, but also reduces storage space wastage caused by saving the user interface, improving the phone's storage utilization.

[0028] Secondly, this application provides an electronic device, which includes a display screen, a memory, and one or more processors; the display screen, the memory, and the processors are coupled; the display screen is used to display a full-screen AOD interface or the user interface of a launched application, the memory is used to store computer program code, the computer program code including computer instructions; when the processor executes the computer instructions, the electronic device performs the method described above.

[0029] Thirdly, this application provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the method described above.

[0030] Fourthly, this application provides a computer program product that, when run on an electronic device, causes the electronic device to perform the method described above.

[0031] Fifthly, a chip is provided, comprising: an input interface, an output interface, a processor, and a memory, wherein the input interface, the output interface, the processor, and the memory are connected via an internal connection path, and the processor is used to execute code in the memory, wherein when the code is executed, the processor is used to execute the method described above.

[0032] The beneficial effects that the electronic device described in the second aspect, the computer-readable storage medium described in the third aspect, the computer program product described in the fourth aspect, and the chip described in the fifth aspect can achieve can be referred to the beneficial effects of the first aspect and any of its possible design embodiments, and will not be repeated here. Attached Figure Description

[0033] Figure 1 This is a schematic diagram of a mobile phone interface without AOD display function provided in an embodiment of this application;

[0034] Figure 2 This is a schematic diagram of an interface for setting up a partial AOD display function on a mobile phone, provided in an embodiment of this application.

[0035] Figure 3 This application provides a schematic diagram of an interface for setting up a full-screen AOD display function on a mobile phone.

[0036] Figure 4 This is a schematic diagram of a mobile phone interface for launching a camera application on top of displaying a lock screen interface, provided as an embodiment of this application.

[0037] Figure 5 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0038] Figure 6 A schematic diagram of the software structure of an electronic device provided in an embodiment of this application;

[0039] Figure 7 A flowchart illustrating an AOD display method provided in this application embodiment;

[0040] Figure 8 This is a schematic diagram illustrating the settings of a full-screen AOD display function provided in an embodiment of this application;

[0041] Figure 9 A schematic diagram of an alarm clock display interface provided in an embodiment of this application;

[0042] Figure 10 This is a schematic diagram of a mobile phone performing screen-off and screen-on operations on top of displaying a camera interface, as provided in an embodiment of this application.

[0043] Figure 11 A schematic diagram illustrating the process of displaying a full-screen AOD interface on a mobile phone when the application corresponding to the user interface is exited, as provided in this application embodiment;

[0044] Figure 12 This is a schematic diagram illustrating a process for switching to full-screen AOD display on a mobile phone when the screen is turned off, as provided in an embodiment of this application.

[0045] Figure 13 This is a schematic diagram illustrating a process for a mobile phone to return to and display the user interface of a launched application when the screen is turned on, as provided in an embodiment of this application. Detailed Implementation

[0046] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings. In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to limit the application. As used in the specification and appended claims of this application, the singular expressions "a," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more (including two). The term "and / or" is used to describe the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0047] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

[0048] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0049] The following section will explain some of the terms.

[0050] 1. Lock screen operation

[0051] Screen lock operation refers to the operation triggered by an electronic device while it is running. For example, this screen lock operation can be automatically triggered after the electronic device has not received any trigger operation from the user on the current display interface for a long time, or it can be triggered after the electronic device receives a user pressing the power button; there is no specific limitation.

[0052] 2. Screen off operation

[0053] A screen-off operation refers to an action triggered by an electronic device when the screen is off and the user interface of the launched application is displayed. In other words, the screen-off operation is an action that causes the electronic device to exit the display of the user interface. For example, the screen-off operation could be determined based on the user pressing the power button. Alternatively, it could be determined based on the duration of time the user interface is displayed; that is, if the duration of time spent on the user interface reaches a preset time, the electronic device can automatically trigger the screen-off operation.

[0054] 3. Screen-on operation

[0055] A screen-on operation refers to an operation triggered by an electronic device when the screen is off and the device is displaying a full-screen AOD (Always-On) interface. In other words, this operation wakes up the device's display to initiate its operation. For example, this operation could be a user pressing the power button, a double-click on the display screen, or a user focusing on a specific area of ​​the screen; the specific action is not limited. The "targeted gaze" operation refers to the user focusing on the display screen for a preset duration.

[0056] In some embodiments, if the electronic device is in a screen-off state (or screen-off state), the electronic device enters standby mode to display a screen-off interface. This screen-off state refers to the state switched to after the electronic device triggers a screen lock operation. It is understood that this screen-off interface does not display any information. Subsequently, if the user wants to view some dynamic information (such as time, date, notifications from any application, etc.) in the screen-off state, they need to press the power button to control the electronic device to display the lock screen interface. This lock screen interface is used to display this dynamic information. It is understood that this lock screen interface is not the same as the screen-off interface.

[0057] For example, such as Figure 1 The interface shown in (a) is the initial screen, which includes multiple application icons and the application name corresponding to each icon. Then, in response to the user pressing the power button A, the phone displays the off-screen interface, meaning the phone can display something like... Figure 1The screen shown in (b) is completely black. If the power button A is pressed again, it indicates the user wants to view some dynamic information; therefore, the phone can display the lock screen, which is the screen that displays... Figure 1 The interface shown in (c) is a lock screen that displays the current time (08:00), the current date (Monday, January 15th), and one notification from a social media app.

[0058] It's understandable that while pressing the power button allows users to view dynamic information, it requires user interaction, preventing direct access and resulting in a poor user experience. Therefore, to improve the user experience, electronic devices can be equipped with an always-on display (AOD) function. Devices with this AOD function can continuously display the aforementioned dynamic information, such as the time, date, and the application icon of the notification's parent application, even when the screen is off. Specifically, the device displays an AOD interface while the screen is off, continuously showing dynamic information. This allows users to view real-time information like the time and date even when the screen is off, and to identify the source of the notification (the application it belongs to) through the displayed application icon. This helps users determine whether to view the notification and its importance. If the notification is important, the user can press the power button to display the lock screen and view its details. If the notification is unimportant, the user can ignore it.

[0059] For example, such as Figure 2 The interface shown in (a) is the initial screen, which includes multiple application icons and the application name corresponding to each icon. Then, in response to the user pressing the power button A, the phone displays the AOD (Always On Demand) screen, meaning the phone can display something like... Figure 2 The interface shown in (b) displays the current time (08:00), the current date (Monday, February 15th), and the application icon (e.g., a music icon) corresponding to the application to which the notification belongs. If the power button A is pressed again, it indicates that the user wants to view the details of the notification; therefore, the phone can display the lock screen, which shows... Figure 2 The interface shown in (c) is a lock screen that displays the current time (08:00), the current date (Monday, February 15th), and a notification from the music app.

[0060] However, according to the above Figure 2As shown in Figure (b), the AOD interface indicates that the electronic device only displays dynamic information in a limited area of ​​the screen (such as the central area), resulting in a relatively limited range of information displayed. Furthermore, because this AOD interface is only bright in the area displaying dynamic information (or the display area), and dark in the non-display areas (i.e., displaying a pure black screen), if the electronic device displays dynamic information in the same area for an extended period, screen burn-in may occur, affecting the subsequent use of the electronic device.

[0061] Therefore, to improve the lifespan of electronic devices, this application provides an AOD (Always-On Display) method that can display AOD across the entire area of ​​the screen. In some embodiments, the brightness of the full-screen AOD interface can be lower than that of the lock screen interface, which can reduce the power consumption of the electronic device and improve the utilization rate of its resources. For example, when the content displayed on the full-screen AOD interface is the same as that displayed on the lock screen interface, the brightness of the full-screen AOD interface is dimmer than that of the lock screen interface. In other embodiments, if a notification message from any application is received while the electronic device is displaying the full-screen AOD interface, the electronic device can highlight the notification message on the full-screen AOD interface. This allows for targeted reminders to the user, making it easier for the user to determine the importance of the notification message and improving the user experience.

[0062] For example, such as Figure 3 The interface shown in (a) is the initial screen, which includes multiple application icons and the application name corresponding to each icon. Then, in response to the user pressing the power button A, the phone displays a full-screen AOD (Always-On) interface, meaning the phone can display... Figure 3 The interface shown in (b) is a full-screen AOD screen displaying the current time (08:00), current date (Monday, January 15th), and notifications from applications on the phone (one notification from a social media app). If the power button A is pressed again, it indicates the user wants to view more details of the activity; therefore, the phone can display the lock screen, which shows... Figure 3 The interface shown in (c) is a lock screen that displays the current time (08:00), the current date (Monday, January 15th), and one notification from a social media app.

[0063] It can be seen that the above Figure 3 The full-screen AOD interface shown in (b) is similar to the one in the image. Figure 3Compared to the lock screen shown in (c), the full-screen AOD interface is dimmer. Specifically, the phone uses gray or white background colors to indicate the brightness of the display; a gray background indicates a full-screen AOD interface, while a white background indicates a lock screen. This allows users to access real-time information while reducing power consumption and extending the lifespan of the electronic device.

[0064] Under normal circumstances, for electronic devices equipped with full-screen AOD (Always-On Display) functionality, when the device is in a screen-off state, in response to the launch of any application, the device can display the user interface corresponding to the launched application. Specifically, the application on the device must be an application with overlay functionality; that is, the application is set to overlay state, allowing its user interface to continue displaying on top of the lock screen. For example, if the launched application is a music application, the user interface could be a lyrics player. Or, if the launched application is a camera application, the user interface could be a camera shutter button.

[0065] In some embodiments, applications with overlay functionality in the aforementioned electronic devices can achieve this by adding a "showWhenLocked" tag to the activity. It can be understood that if "showWhenLocked" is true, it means the electronic device can display the application's user interface while the lock screen is displayed. Specifically, during the display of the user interface, the user interface is overlaid on the lock screen, meaning the lock screen (keyguard) is in an overlaid state, and the corresponding occluded attribute of the lock screen is true. The occluded attribute being true indicates that the current lock screen is occluded, meaning the lock screen will not be displayed even if the electronic device is not unlocked. It can be understood that whether the electronic device displays the lock screen can be indicated by the NotificationShade window (or lock screen window). This NotificationShade window is used to display system notifications (such as notification messages from any application). Specifically, if the electronic device displays the NotificationShade window, it means the electronic device is displaying the lock screen; if the electronic device does not display the NotificationShade window, it means the electronic device is not displaying the lock screen.

[0066] Subsequently, while the electronic device is displaying the aforementioned user interface, in response to the screen-off operation, the electronic device remains in a screen-off state. In other words, the electronic device continues to display the screen-off interface (i.e., a pure black interface), causing the full-screen AOD interface to fail to display in a timely manner, thereby affecting the user experience.

[0067] For example, such as Figure 4 As shown, the phone is displaying the lock screen, that is, the phone is displaying... Figure 4 The interface shown in (a) is as follows. Subsequently, in response to the user's swipe-up operation on the "camera" control 401 in the lock screen, the phone can display the shooting interface, which is as shown in (a). Figure 4 The interface shown in (b) is shown below. Afterwards, in response to the user pressing the power button A, the phone can display the off-screen interface by default, that is, the phone can display something like... Figure 4 The pure black interface shown in (c) means that the phone cannot return to display the full-screen AOD interface, which prevents the phone from implementing the full-screen AOD function. As a result, the full-screen AOD interface cannot be displayed in time, thus affecting the user experience.

[0068] Therefore, to improve the user experience, this application provides an AOD (Always-On Display) method applied to electronic devices with full-screen AOD functionality. In this method, when the electronic device is in a screen-off state, after displaying the user interface corresponding to the launched application, the electronic device switches to displaying a full-screen AOD interface in response to a screen-off operation. This screen-off operation is used to cause the electronic device to exit the user interface display, thereby controlling the electronic device to enter standby mode.

[0069] In this embodiment, when the electronic device displays the user interface of the launched application, if a screen-off operation is detected (i.e., the electronic device is forcibly turned off), the electronic device can still return to display the full-screen AOD interface. In other words, as long as the electronic device is forcibly turned off, the full-screen AOD interface will be displayed. This achieves accurate display of the full-screen AOD interface; that is, as long as the electronic device has a full-screen AOD display function, it can display the full-screen AOD interface when the electronic device is turned off, reducing the occurrence of situations where the full-screen AOD interface cannot be displayed in a timely manner due to the electronic device being turned off, improving the display effect of the full-screen AOD, and thus enhancing the user experience.

[0070] In some examples, the electronic devices in this application embodiment may be mobile phones, tablets, wearable devices, in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), and other electronic devices capable of AOD display. This application embodiment does not impose any restrictions on the specific type of electronic device.

[0071] For example, Figure 5 A schematic diagram of the structure of electronic device 200 is shown. For example... Figure 5 As shown, the electronic device 200 may include a processor 210, an external memory interface 220, an internal memory 221, a charging management module 211, a power management module 212, a battery 213, an antenna 1, an antenna 2, a mobile communication module 240, a wireless communication module 250, a sensor module 280, a button 290, an indicator 292, and a display screen 294, etc.

[0072] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 200. In other embodiments of this application, the electronic device 200 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0073] Processor 210 may include one or more processing units, such as application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0074] The controller can be the nerve center and command center of the electronic device 200. The controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.

[0075] The processor 210 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. This memory can store instructions or data that the processor 210 has just used or that are used repeatedly. If the processor 210 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 210, and thus improves the efficiency of the system. In some embodiments, the processor 210 may include one or more interfaces.

[0076] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the electronic device 200. In other embodiments of this application, the electronic device 200 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0077] The charging management module 211 receives charging input from the charger. While charging the battery 213, the charging management module 211 can also supply power to the electronic device through the power management module 212.

[0078] The wireless communication function of electronic device 200 can be implemented through antenna 1, antenna 2, mobile communication module 240, wireless communication module 250, modem processor, and baseband processor. Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Mobile communication module 240 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G on electronic device 200. Modem processor can include modulator and demodulator. Wireless communication module 250 can provide solutions for wireless communication applications on electronic device 200.

[0079] Electronic device 200 implements display functions through a GPU, a display screen 294, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 210 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0080] The display screen (or screen) 294 is used to display images, videos, etc. The display screen 294 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 200 may include one or N display screens 294, where N is a positive integer greater than 1.

[0081] In some embodiments, the display screen 294 is used to display a lock screen interface, a full-screen AOD interface, etc. In one example, the electronic device displays a full-screen AOD interface in response to a user pressing the power button. In another example, if the power button is pressed again or the full-screen AOD interface is touched while the electronic device is displaying the full-screen AOD interface, the electronic device can display a lock screen interface.

[0082] The external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 200. The internal memory 221 can be used to store computer executable program code, which includes instructions.

[0083] Buttons 290 include a power button, volume buttons, etc. Buttons 290 can be mechanical buttons or touch-sensitive buttons. Electronic device 200 can receive button input and generate key signal inputs related to user settings and function control of electronic device 200. Indicator 292 can be an indicator light.

[0084] The sensor module 280 may include pressure sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, accelerometers, distance sensors, proximity sensors, fingerprint sensors, temperature sensors, touch sensors, ambient light sensors, bone conduction sensors, etc.

[0085] For example, the software system of the aforementioned electronic device 200 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This embodiment of the invention uses the layered architecture Android system as an example to illustrate the software structure of the electronic device 200.

[0086] Figure 6 This is a software structure block diagram of an electronic device 200 according to an embodiment of this application.

[0087] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer (application layer), the application framework layer (framework layer), the Android runtime and system libraries, and the kernel layer (or driver layer). The application layer can include a series of application packages.

[0088] The application layer can include a series of application packages. This application layer can include multiple application packages. For example... Figure 6 As shown, the application package may include camera, gallery, music, alarm clock, system UI, etc.

[0089] The aforementioned systemUI is the user interface for interacting with electronic devices. It provides user interface elements such as a status bar and navigation bar to help users quickly access various functions and notification messages of the electronic device. In some embodiments, the systemUI may include a keyguard service, a keyguardview mediator, and a full-screen AOD mediator.

[0090] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions. For example... Figure 6 As shown, the application framework layer may include a window manager, content provider, phone manager, resource manager, system server, etc.

[0091] The window manager manages windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots. The content provider stores and retrieves data, making it accessible to applications. This data may include video, images, audio, made and received calls, browsing history and bookmarks, phone books, etc. The phone manager provides communication functionality for electronic devices, such as managing call status (including connection and disconnection). The resource manager provides applications with various resources, such as localized strings, icons, images, layout files, video files, etc.

[0092] The system server described above is used to create the core services of the system, which may include a power manager service, a window manager service, etc. In some embodiments, the system server may include a phone window manager and a power manager. The phone window manager is used to manage window-related interfaces, that is, to control the window hierarchy and display order. The power manager is used to manage the power-on and power-off of the display screen.

[0093] The Android runtime consists of core libraries and a virtual machine. The Android runtime is responsible for scheduling and managing the Android system.

[0094] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0095] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0096] System libraries can include multiple functional modules. For example: media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), surface managers, etc.

[0097] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG. The 3D graphics processing library is used for 3D graphics drawing, image rendering, compositing, and layer processing. The 2D graphics engine is the drawing engine for 2D graphics. The surface manager manages the display subsystem and provides fusion of 2D and 3D layers for multiple applications.

[0098] The kernel layer is the layer between hardware and software. The kernel layer includes at least display drivers, camera drivers, and audio drivers.

[0099] Understandable, Figure 6The layers in the illustrated structure and the components contained in each layer do not constitute a specific limitation on the electronic device 200, i.e., the foldable screen device. In other embodiments of this application, the structure may include more or fewer layers than illustrated, and each layer may include more or fewer components; this application does not impose any limitations.

[0100] Based on the electronic devices described above, this application provides an AOD (Always-On Display) method. This method can be applied to scenarios where an electronic device with a full-screen always-on mode (or full-screen AOD mode) is in a screen-off state. The method of this application embodiment will be described below using a mobile phone as an example. Specifically, as... Figure 7 As shown, the AOD display method may include S701 to S704.

[0101] The S701 displays a full-screen AOD interface when the phone screen is off.

[0102] The aforementioned screen-off state refers to the phone entering standby mode to conserve power. This standby state is a state where the phone is powered on without any operation. In other words, if the phone detects a user pressing any button (such as the power button) or launching any application on the phone, it indicates that the phone has exited standby mode.

[0103] In some embodiments, in response to a user pressing the power button, the phone can lock the screen, meaning the phone is in a screen-off state.

[0104] In other embodiments, when the phone's sleep time reaches a preset sleep time, it indicates that the phone has not been used by the user for a long time, meaning the phone has not received any touch operations from the user for an extended period. Therefore, the phone can automatically lock the screen. The preset sleep time refers to the time the phone's display screen remains off after the user has not performed any operation. It can be understood that if the phone's sleep time has not reached the preset sleep time, it indicates that the phone has been used by the user for a short period, meaning the phone received touch operations from the user for a short time. Therefore, the phone can continue to display the current interface without locking the screen. For example, the preset sleep time can be a default setting on the phone or a setting pre-defined by the user according to actual needs; there is no specific limitation. For example, the preset sleep time can be 30 seconds, 1 minute, etc.

[0105] It's understandable that when a phone's screen is off, the phone can determine the display interface based on the AOD (Always-On Display) settings. These settings indicate whether the AOD function is enabled by the user. In one example, for a phone without AOD enabled, when the screen is off, the phone can directly display the off-screen interface without showing any information or screen; that is, the display interface after the screen is off is the off-screen interface. In another example, for a phone with a partial off-screen mode (or partial AOD mode), when the screen is off, the phone can directly display a partial AOD interface (such as...). Figure 2 The interface shown in (b) indicates that the display interface after the screen is off is a partial AOD interface. In another example, for a phone with a full-screen always-on display mode, when the phone is in a screen-off state, the phone can directly display a full-screen AOD interface (such as...). Figure 3 The interface shown in (b) means that the display interface after the screen is turned off is a full-screen AOD interface.

[0106] In one implementation, the setting result of the aforementioned AOD function can be determined based on the setting control clicked in the AOD function setting interface. For example, such as... Figure 8 The interface shown in (a) is the user interface for setting the Always-On Display (AOD) function. This user interface includes an always-on display control 801. Specifically, when the user clicks the always-on display control 801 in the user interface, the phone can further display the always-on display mode settings interface, that is, display as shown in (a). Figure 8 The interface shown in (b) is as follows. This settings interface includes the full-screen always-on display (AOD) effect interface and full-screen controls, as well as the partial always-on display (AOD) effect interface and partial controls. When the user clicks the full-screen controls in the settings interface, it indicates that the user has selected the full-screen always-on display mode. Therefore, even when the phone screen is off, the phone can directly display the full-screen Always-On Display (AOD) interface.

[0107] It should be noted that the above Figure 8 The interface shown for setting AOD (Always-On Display) is just an example; users can also control AOD in other ways. For instance, the phone can directly display the screen-off mode option, allowing users to directly select whether to enable or disable full-screen or partial screen-off mode. In other words, if the user clicks the control corresponding to full-screen screen-off mode, the phone can directly determine that the full-screen screen-off mode has been enabled.

[0108] In another implementation, the AOD (Always-On Display) function settings can be the phone's default settings. For example, the phone can be set to full-screen always-on mode by default, which means AOD is enabled by default.

[0109] S702: When the phone detects the launch of any application on the phone, the phone displays the user interface corresponding to the launched application.

[0110] The application on the phone is one with overlay functionality, meaning it can display its interface on top of the lock screen even when the phone screen is off. Examples include alarm clock apps and camera apps.

[0111] It should be noted that some applications on a phone may not have an overlay function. This means that when the phone is in a screen-off state, the phone will not display the interface for that application on top of the lock screen. For example, applications without an overlay function could be social media apps, video apps, etc., and there are no specific limitations.

[0112] In some embodiments, the aforementioned launch operation can be a user-triggered operation for any application with overlay functionality. This triggering operation can be a click, double-click, swipe up, etc., and is not specifically limited. For example, taking a camera application as an example, please refer to [link to relevant documentation]. Figure 4 In response to the user's swipe-up action on the camera control 401, the phone can... Figure 4 Based on the interface in (a), the camera application's shooting interface (i.e., the display) is overlaid. Figure 4 (The interface shown in (b)). It can be understood that the user's swipe up operation on the camera control 401 is equivalent to the start operation, and the shooting interface of the camera application displayed on the mobile phone is equivalent to the above-mentioned user interface.

[0113] In other embodiments, the above-described startup operation can also be an automatic startup operation triggered by an application with overlay functionality on the mobile phone. For example, taking an alarm clock application as an example, and the mobile phone having an alarm set to 9:00 AM, please refer to [link to relevant documentation]. Figure 9 If the current time is 9:00 AM, the phone can display an alarm reminder interface, which means it will display something like this: Figure 9 The interface shown is as follows. This alarm clock reminder interface includes the current time (9:00 AM), the current date (Monday, January 15th), and a control to turn off the alarm. It's understandable that if the user slides the control to turn off the alarm, it means the user wants to turn off the alarm; therefore, the phone can return to the lock screen.

[0114] In one implementation, when the phone displays the user interface corresponding to the launched application, that is, before detecting a screen-off operation of the electronic device, the phone can save the aforementioned user interface so that the phone can continue to display the user interface later. This not only reduces the rendering time of the user interface and improves the display efficiency of the user interface, but also reduces unnecessary resource loss and improves the utilization rate of rendering resources.

[0115] In response to the screen-off operation, the S703 returns to display the aforementioned full-screen AOD interface.

[0116] Specifically, after the phone displays the user interface, if a screen-off operation is detected, it means the user interface has been forcibly closed. Therefore, the phone can continue to display the aforementioned full-screen AOD (Always-On Display) interface. This ensures accurate display of the full-screen AOD interface, reducing the likelihood of it failing to display again due to the phone covering other interfaces, thus improving the display effect of the full-screen AOD and ultimately enhancing the user experience. The screen-off operation is used to put the phone back into standby mode; in other words, this operation allows the phone to exit the display of the user interface.

[0117] In one example, the screen-off action described above could be determined based on the user's press of the power button. For example, see [link to relevant documentation]. Figure 10 When the phone screen is off, but the phone is displaying the camera app's photo-taking interface, that is, when it is displaying... Figure 10 In the case of the interface shown in (a), in response to the user pressing the power button A, the phone can display a full-screen AOD interface, that is, display... Figure 10 The interface shown in (b) is a full-screen AOD interface that displays the current time (08:00), the current date (Monday, January 15th), and one notification from a social media app.

[0118] In another example, the screen-off operation can also be determined based on the dwell time of the user interface. That is, if the dwell time on the user interface reaches a preset dwell time (e.g., 5 seconds), the phone can automatically trigger the screen-off operation. This preset dwell time can be pre-set by the phone or set by the user according to actual needs; there is no specific limitation. It can be understood that if the dwell time on the user interface reaches the preset dwell time, it means that the user has not been using the application corresponding to the user interface, and it may have been accidentally displayed. Therefore, in order to reduce power consumption, the phone can trigger the screen-off operation to put the phone into standby mode, improve the phone's battery life, and thus improve the user experience.

[0119] S704, in response to the user's screen-on operation, the phone continues to display the above-mentioned user interface.

[0120] The aforementioned screen-on operation is used to wake up the phone's display, causing the phone to switch from standby mode back to working mode. For example, this screen-on operation can be a user pressing the power button, a user double-tapping the display, or a user focusing on a specific area of ​​the display, etc., without specific limitations. The target focus operation refers to the user focusing on the display for a preset focus time.

[0121] Specifically, after the phone returns to the aforementioned full-screen AOD interface, if it detects a user's screen-on operation, it can continue displaying the previous interface. This allows users to continue operating on that interface without having to reopen the application associated with it, thus improving the user experience.

[0122] For example, please continue to see Figure 10 On the phone display Figure 10 In the case of a full-screen AOD interface as shown in (b), if the phone receives a press operation from the user on the power button A, it can continue to display the camera app's shooting interface, that is, display... Figure 10 The interface shown in (c) is designed to facilitate continued photo taking, simplifying the process, reducing time, and ultimately enhancing the user's shooting experience.

[0123] In some embodiments, after detecting a user's screen-on operation on the phone, the phone may display a lock screen interface (such as...). Figure 3 As shown in interface (c), the phone does not return to display the aforementioned user interface. This not only makes it easier for users to view notifications or reselect the desired application, reducing the need for additional steps due to the phone exiting the user interface, but also reduces wasted storage space caused by saving the user interface, thus improving the phone's storage utilization.

[0124] In one implementation, the launch operation of any application on the phone can be performed before the phone screen is off. That is, in response to the user's launch operation for any application on the phone, the phone performs the launch operation for the launched application. Afterwards, when the phone screen is off, the phone can directly display the user interface corresponding to the launched application; that is, the phone can choose not to display the aforementioned full-screen AOD interface. Then, upon detecting a screen-off operation, the phone switches to displaying the full-screen AOD interface. Finally, in response to the user's screen-on operation, the phone continues to display the user interface.

[0125] For example, taking a music app as an example, which has a lock screen lyrics display function, in response to the user's launch of the music app, the phone displays the default interface corresponding to the music app. Then, if the user clicks on any music in this default interface, the phone can play the audio content of the clicked music. Afterwards, if the phone is in a screen-off state, the phone can directly display the user interface of the launched app, that is, the lyrics playback interface of the clicked music. Then, if the screen-off operation is detected, the phone switches to a full-screen AOD interface. Afterwards, in response to the user's screen-on operation, the phone continues to display the lyrics playback interface of the clicked music.

[0126] It's important to note that to accurately and promptly display the full-screen AOD interface, the phone can divide the overlay state (or lock screen overlay state) into a system-side overlay state and a lock screen-side overlay state. The system-side overlay state is determined by whether any application with overlay functionality is launched on the phone; that is, whether the phone detects the launch of such an application. Specifically, if any application with overlay functionality is launched, it means the user wants to use the application, and the phone needs to display its interface. Therefore, the phone can change the system-side overlay state attribute from false to true. If any application with overlay functionality is closed, it means the user does not want to use the application, and the phone does not need to display its interface. Therefore, the phone can change the system-side overlay state attribute from true to false. In other words, when the system-side overlay state attribute is true, it means the phone has detected the launch of an application with overlay functionality; when the system-side overlay state attribute is false, it means the phone has detected the closure of an application with overlay functionality, i.e., the phone has detected the closure of the launched application.

[0127] The aforementioned lock screen-side overlay state is determined based on whether the phone switches to displaying a full-screen AOD interface. Whether the phone switches to displaying a full-screen AOD interface can be determined based on whether the phone detects the screen-off operation. That is, if the screen-off operation is detected, the phone can switch to displaying a full-screen AOD interface; if the screen-off operation is not detected, the phone can choose not to switch to displaying a full-screen AOD interface, meaning the phone can continue displaying the aforementioned user interface or exit the lock screen display. Specifically, when the lock screen-side overlay state attribute is false, it indicates that the phone switches to displaying a full-screen AOD interface. When the lock screen-side overlay state attribute is true, it indicates that the phone exits the full-screen AOD display.

[0128] In some embodiments, when an application with overlay functionality is launched or exited on the phone, the system server on the phone will cause a change in the system overlay state. Specifically, in response to the launch of any application with overlay functionality on the phone, the system server on the phone will change the system-side overlay state attribute from false to true; or, in response to the exit operation of the currently displayed user interface on the phone, the system server on the phone will change the system-side overlay state attribute from true to false. Then, when the system-side overlay state attribute is false, the system user interface on the phone will update the lock screen-side overlay state to false to control the phone to return to displaying the full-screen AOD interface. The following will combine the above... Figure 6 The structure shown and Figure 11 The interface display process shown details how a mobile phone's screen displays a full-screen AOD interface when the application corresponding to the user interface is exited.

[0129] S1101. When the visibility of the display interface changes, the telephone window manager in the system server determines the system-side overlay attribute.

[0130] The change in the visibility of the aforementioned display interface refers to a change in the interface type to which the display interface belongs. This interface type can include at least one of the following: a lock screen interface, the user interface of an application with overlay functionality, and a full-screen AOD (Always-On) interface. For example, if the display interface changes from a lock screen interface to the user interface of any application with overlay functionality on the phone, it indicates that the user has launched that application, meaning the user wants to use it. Therefore, the system server can determine that the visibility of the display interface has changed. Conversely, if the display interface continues to show the user interface of any application with overlay functionality on the phone, it indicates that the user has not exited the application, meaning they are still using it. Therefore, the system server can determine that the visibility of the display interface has not changed.

[0131] It should be noted that whether the visibility of the aforementioned display interface has changed can be determined based on whether the system server has received an activity visibility update indication. In one example, if the system server receives an activity visibility update indication, it can determine that the visibility of the display interface has changed. In another example, if the system server does not receive an activity visibility update indication, it can determine that the visibility of the display interface has not changed.

[0132] In some embodiments, after determining that the visibility of the displayed interface has changed, the phone window manager in the system server can determine the system-side overlay attribute. This system-side overlay attribute characterizes whether the lock screen interface is overlaid. It can be understood that when an application with overlay functionality is launched on the phone, i.e., when the phone displays the interface of the launched application, the phone window manager can change the system-side overlay attribute from false to true. When the launched application is exited, the phone window manager can change the system-side overlay attribute from true to false. If the phone continuously displays the lock screen interface or a full-screen AOD interface, the phone window manager may not modify the system-side overlay attribute; that is, the system-side overlay attribute remains false.

[0133] S1102, The Telephone Window Manager sends an overriding setting command to the Lock Screen Service class in the system user interface.

[0134] Specifically, after determining the system-side overlay attributes, the phone window manager in the system server can send an overlay setting command to the lock screen service class in the system user interface. This overlay setting (setOccluded) command carries the system-side overlay attributes.

[0135] S1103. When the lock screen service class receives the overlay setting instruction sent by the system server, the lock screen service class sends the overlay setting instruction to the lock screen view intermediary class in the system user interface.

[0136] Specifically, after receiving the aforementioned overlay setting instruction, the lock screen service class in the system user interface can send the overlay setting instruction to the lock screen view intermediary class in the system user interface. This allows the lock screen view intermediary class to determine whether to display the full-screen AOD interface based on the system-side overlay attribute carried by the overlay setting instruction, thus providing a foundation for accurate AOD display in the future.

[0137] S1104. When the lock screen view intermediary class receives the overlay setting instruction sent by the lock screen service class, the lock screen view intermediary class sends the overlay setting instruction to the full-screen AOD intermediary class in the system user interface.

[0138] Specifically, after receiving the aforementioned overlay setting instruction, the lock screen view intermediary class in the system user interface can send the overlay setting instruction to the full-screen AOD intermediary class in the system user interface, so that the full-screen AOD intermediary class can save the system-side overlay attributes carried by the overlay setting instruction, providing a basis for subsequently restoring the original interface display.

[0139] S1105. When the full-screen AOD mediator receives the overlay setting instruction sent by the lock screen view mediator, the full-screen AOD mediator saves the system-side overlay attributes carried by the overlay setting instruction.

[0140] In some embodiments, after receiving the aforementioned overlay setting instruction, the full-screen AOD intermediary class in the system user interface can save the system-side overlay attribute carried by the instruction. This allows for direct subsequent invocation of the display interface corresponding to the system-side overlay attribute. In other words, if the system-side overlay attribute is true, the phone can directly display the interface of the launched target application after the screen is turned on again. If the system-side overlay attribute is false, the phone can directly display the full-screen AOD interface after the screen is turned off again. This reduces the secondary rendering time of the display interface, improves display efficiency, and ultimately enhances the user experience.

[0141] S1106. If the system-side overlay attribute carried by the above overlay setting instruction is not specified, the lock screen view intermediary class determines whether the phone has a full-screen off-screen mode set.

[0142] The aforementioned full-screen always-on display mode refers to a mode in which the phone displays a full-screen Always-On Display (AOD) interface when the phone screen is off.

[0143] In some embodiments, after receiving the aforementioned overlay setting instruction, the lock screen view intermediary class in the system user interface can determine the system-side overlay attribute carried by the overlay setting instruction. If the system-side overlay attribute carried by the overlay setting instruction is true, it means that the phone is currently displaying the user interface of the launched application, that is, the lock screen interface is currently being overlaid. Therefore, the phone does not need to update the lock screen-side overlay attribute. This reduces unnecessary resource loss and improves the utilization rate of system resources. If the system-side overlay attribute carried by the overlay setting instruction is false, it means that the phone is not displaying the user interface of the launched application, that is, the lock screen interface is not currently being overlaid. Therefore, the phone can further determine whether the phone has a full-screen always-on display mode set. It can be understood that the phone can only display a full-screen Always-On Display (AOD) interface when a full-screen always-on display mode is set.

[0144] In one implementation, the aforementioned lock screen view intermediary class determines whether the phone has a full-screen always-on display (AOD) mode enabled by the user's settings for the full-screen AOD mode. For example, if the user selects the full-screen control associated with the full-screen AOD mode, it means the user wants to enable that mode. Therefore, the phone can determine that a full-screen AOD mode is enabled, meaning the phone can display the full-screen AOD interface. If the user does not select the full-screen control associated with the full-screen AOD mode, or if the user selects a partial control associated with the partial AOD mode, it means the user does not want to enable that mode. Therefore, the phone can determine that a full-screen AOD mode is not enabled, meaning the phone cannot display the full-screen AOD interface.

[0145] In another implementation, the aforementioned lock screen view intermediary class determines whether the phone has a full-screen always-on display (AOD) mode enabled based on the phone's default AOD function. For example, if the phone's AOD function is disabled by default, and the phone has not received any user settings for a full-screen always-on display mode, the phone can determine that a full-screen always-on display mode is not enabled, meaning the phone cannot display a full-screen AOD interface. If the phone's default AOD function has a full-screen always-on display mode enabled, the phone can determine that a full-screen always-on display mode is enabled, meaning the phone can display a full-screen AOD interface.

[0146] S1107. When the phone is set to full-screen always-on display mode, the lock screen view intermediary class updates the lock screen side overlay property and displays the full-screen always-on display interface.

[0147] Specifically, after confirming that the phone has a full-screen always-on display (AOD) mode enabled, the lock screen view intermediary class can update the lock screen-side overlay property to false and load the notification shade window, thus displaying the full-screen AOD interface. This allows the phone to accurately and promptly switch to displaying the AOD interface when the user interface of a launched application exits, improving the accuracy of the phone's interface display and enhancing the AOD display effect.

[0148] It should be noted that the execution order of the system-side overlay attribute saving process in S1104-S1105 and the full-screen AOD interface display process in S1106-S1107 is not limited. Specifically, the execution steps of S1104-S1105 and S1106-S1107 can be executed simultaneously or in a preset order, without limitation. For example, the preset order can be that the system user interface executes the execution steps of S1104-S1105 first, and then executes the execution steps of S1106-S1107, or the system user interface executes the execution steps of S1106-S1107 first, and then executes the execution steps of S1104-S1105.

[0149] In some embodiments, when the phone displays the user interface corresponding to the launched application (i.e., the system-side overlay attribute carried by the aforementioned overlay setting instruction is true), if the phone's power manager receives a screen-off operation, it means the phone's display is forcibly turned off, i.e., the phone enters the full-screen AOD lifecycle. Therefore, the phone can modify the lock screen-side overlay attribute to make the phone display a full-screen AOD interface. The following will combine the above... Figure 6 The structure shown and Figure 12 The interface display process shown details how a mobile phone's screen displays a full-screen AOD interface when the phone screen is off.

[0150] S1201. When the mobile phone displays the user interface corresponding to the launched application, the power manager in the system server receives the screen-off operation.

[0151] The aforementioned screen-off operation is used to put the phone back into standby mode, meaning it's an operation that causes the phone to exit the displayed user interface. For example, this screen-off operation could be based on the user pressing the power button. Alternatively, it could be based on the duration the user has been on the screen; that is, if the duration reaches a preset time (e.g., 5 seconds), the phone can automatically trigger the screen-off operation. It's understandable that if the user hasn't intended to use the launched application, it means the screen was accidentally displayed. Therefore, to reduce power consumption, the phone can trigger the screen-off operation to put it into standby mode, improving battery life and ultimately enhancing the user experience.

[0152] S1202. Upon receiving the aforementioned screen-off operation, the power manager sends a first screen-on instruction to the telephone window manager in the system server.

[0153] Specifically, upon receiving the aforementioned screen-off operation, the power manager can send a first screen-on instruction to the phone window manager in the system server. This first screen-on instruction notifies the phone window manager to perform the first screen-on process, which refers to displaying a full-screen AOD interface.

[0154] In one implementation, the power manager can send a first screen-on indication to the phone window manager by calling the onWakefulnessChangeStarted function to control the phone to display a full-screen AOD interface.

[0155] S1203. Upon receiving the first screen-on instruction from the power manager, the telephone window manager sends a sleep instruction to the lock screen service class in the system user interface.

[0156] Specifically, after the phone window manager receives the aforementioned screen-on instruction, it can send a sleep instruction to the lock screen service class in the system user interface. This sleep instruction carries the reason for the screen turning off. This reason refers to the reason why the phone triggered the screen-off operation.

[0157] In one implementation, the phone window manager can send a sleep instruction to the lock screen service class in the system user interface by calling the onStartedGoingToSleep function, thereby controlling the display to complete the sleep process, that is, to put the display into standby mode.

[0158] S1204. Upon receiving a hibernation instruction from the Telephone Window Manager, the Lock Screen Service class sends a hibernation instruction to the Full-Screen AOD Mediator class in the system user interface.

[0159] In some embodiments, after receiving the above-mentioned sleep instruction, the lock screen service class in the system user interface can send the sleep instruction to the full-screen AOD mediation class in the system user interface to further control the display screen to complete the sleep process.

[0160] S1205. When the full-screen AOD intermediary class receives a sleep instruction sent by the lock screen service class, if the system-side overlay state attribute is yes, it modifies the lock screen-side overlay state attribute to obtain the first lock screen-side overlay state attribute.

[0161] Specifically, after receiving the aforementioned sleep instruction, the full-screen AOD intermediary class in the system user interface can re-invoke the system-side overriding attributes. It can be understood that after the visibility of the displayed interface changes, the full-screen AOD intermediary class has already saved the system-side overriding attributes. Therefore, upon receiving the sleep instruction, the full-screen AOD intermediary class can directly call the previously saved system-side overriding attributes. This improves the efficiency of overriding attribute retrieval and provides a foundation for the timely display of the full-screen AOD interface.

[0162] In some embodiments, if the system-side overlay attribute is determined to be true, it means that the lock screen-side overlay attribute is also true. However, since the power manager has already received the screen-off operation, the full-screen AOD mediator class needs to change the lock screen-side overlay attribute from true to false, that is, the first lock screen-side overlay attribute is false, in order to control the phone to display the full-screen AOD interface. It can be understood that if the system-side overlay attribute is false, it means the lock screen-side overlay attribute is also false, and the full-screen AOD mediator class does not need to modify the lock screen-side overlay attribute, thus reducing the utilization of phone resources.

[0163] S1206. The lock screen view intermediary class in the system user interface receives the first lock screen side overlay state attribute sent by the full-screen AOD intermediary class.

[0164] Specifically, after the full-screen AOD mediator class obtains the aforementioned first lock screen-side overlay attribute, the full-screen AOD mediator class can send the first lock screen-side overlay attribute to the lock screen view mediator class in the system user interface.

[0165] In one implementation, the full-screen AOD intermediary class can send the aforementioned first lock screen side overlay attribute to the lock screen view intermediary class by sending setOccluded(false).

[0166] S1207. The lock screen view intermediary class displays the full-screen AOD interface according to the first lock screen side overlay state attribute mentioned above.

[0167] Specifically, after the lock screen view intermediary class receives the aforementioned first lock screen-side overlay state attribute, it can load the notification shade window based on this attribute, thus displaying the full-screen AOD interface. This ensures accurate display of the full-screen AOD interface, reducing the likelihood of it not displaying promptly due to the phone screen being off, improving the display effect of the full-screen AOD, and ultimately enhancing the user experience.

[0168] In one implementation, the process of displaying a full-screen AOD interface using the aforementioned lock screen view intermediary class can be achieved through the handleSetOccluded() function.

[0169] Understandably, if the system user interface in the phone does not execute the steps S1205 to S1207 above, the phone will directly display the always-on display, which is a completely black screen, instead of the full-screen AOD screen mentioned above.

[0170] In some embodiments, when the phone displays the aforementioned full-screen AOD interface, if the phone's power manager receives a screen-on operation, it indicates that the phone has been woken up, meaning the phone has exited the full-screen AOD lifecycle. Therefore, the phone can modify the lock screen-side overlay attribute to allow the phone to return to displaying the target application's user interface. The following will combine the above... Figure 6 The structure shown and Figure 13 The interface display process shown details how the phone's screen returns to the user interface when the phone is turned on.

[0171] S1301. When the mobile phone displays a full-screen AOD interface, the power manager in the system server receives the screen-on operation.

[0172] The aforementioned screen-on operation is used to wake up the phone's display, causing the phone to switch from standby mode back to working mode. For example, this screen-on operation can be a user pressing the power button, a user double-tapping the display, or a user focusing on a specific area of ​​the display, etc., without specific limitations. The target focus operation refers to the user focusing on the display for a preset focus time (e.g., 3 seconds).

[0173] It is understandable that if the user gazes at the screen for the aforementioned preset gazing time, it means that the user has been gazing at the screen for a relatively long time, which means that the user may want to use the phone. Therefore, in order to simplify the user's operation process, the phone can directly trigger the screen to light up, thereby improving the user's experience.

[0174] S1302. Upon receiving the aforementioned screen-on operation, the power manager sends a second screen-on instruction to the telephone window manager in the system server.

[0175] Specifically, upon receiving the aforementioned screen-on operation, the power manager can send a second screen-on instruction to the phone window manager in the system server. This second screen-on instruction notifies the phone window manager to perform a second screen-on process, which refers to returning to and displaying the user interface of the launched application.

[0176] In one implementation, the power manager can send a second screen-on instruction to the phone window manager by calling the onWakefulnessChangeStarted function, thereby controlling the phone to display the user interface of the aforementioned launched application.

[0177] S1303. Upon receiving the second screen-on instruction from the power manager, the telephone window manager sends a wake-up instruction to the lock screen service class in the system user interface.

[0178] Specifically, after the phone window manager receives the second screen-on instruction, it can send a wake-up instruction to the lock screen service class in the system user interface. This wake-up instruction is used to instruct the lock screen service class to wake up the display and continue showing the user interface of the launched application.

[0179] In one implementation, the phone window manager can send a wake-up instruction to the lock screen service class in the system user interface by calling the onStartedWakingUp function, so that the display screen can continue to show the user interface of the launched application.

[0180] S1304. Upon receiving a wake-up instruction from the Telephone Window Manager, the Lock Screen Service Class sends a pre-wake-up instruction to the Full-Screen AOD Mediation Class in the system user interface.

[0181] Specifically, after receiving the wake-up instruction, the lock screen service class in the system user interface can send a pre-wake-up instruction to the full-screen AOD intermediary class in the system user interface. This pre-wake-up instruction is used to notify the full-screen AOD intermediary class to wake up the display screen and continue showing the user interface of the launched application.

[0182] In one implementation, the lock screen service class can send a pre-wake instruction to the full-screen AOD mediator class in the system user interface by calling the onPreStartedWakingUp function, so as to further wake up the display screen to continue displaying the user interface of the target application.

[0183] S1305. When the full-screen AOD intermediary class receives a pre-wake-up instruction sent by the lock screen service class, if the system-side coverage state attribute is yes, it modifies the lock screen-side coverage state attribute to obtain the second lock screen-side coverage state attribute.

[0184] Specifically, after receiving the aforementioned pre-wake-up instruction, the full-screen AOD intermediary class in the system user interface can re-invoke the system-side overlay attributes. It can be understood that after the visibility of the displayed interface changes, the full-screen AOD intermediary class has already saved the system-side overlay attributes. Therefore, upon receiving the pre-wake-up instruction, the full-screen AOD intermediary class can directly call the previously saved system-side overlay attributes. This improves the efficiency of overlay attribute retrieval and provides a foundation for the timely display of the full-screen AOD interface.

[0185] In some embodiments, if the system-side overlay state attribute is determined to be true and the first lock screen-side overlay state is false, it indicates that the power manager has received the screen-on operation. Therefore, the full-screen AOD mediator class needs to change the lock screen-side overlay state from false to true, that is, the second lock screen-side overlay state attribute is true, to control the phone to continue displaying the user interface of the launched application. In other words, if the system-side overlay state attribute is false and the first lock screen-side overlay state attribute is also false, it indicates that no application with overlay functionality has been launched. Therefore, to reduce unnecessary resource consumption, the full-screen AOD mediator class does not need to modify the lock screen-side overlay state attribute.

[0186] S1306, The lock screen view intermediary class in the system user interface receives the second lock screen side overlay state attribute sent by the full-screen AOD intermediary class.

[0187] Specifically, after the full-screen AOD mediator class obtains the aforementioned second lock screen-side overlay attribute, the full-screen AOD mediator class can send the second lock screen-side overlay attribute to the lock screen view mediator class in the system user interface.

[0188] In one implementation, the full-screen AOD mediator class can send the aforementioned second lock screen-side overlay attribute to the lock screen view mediator class by sending setOccluded(true).

[0189] S1307. The lock screen view intermediary class returns and displays the user interface of the launched application according to the second lock screen side overlay state attribute mentioned above.

[0190] Specifically, after the lock screen view intermediary class receives the aforementioned second lock screen-side overlay state attribute, it can return to display the user interface of the launched application based on this attribute. This ensures accurate display of the user interface, reducing the likelihood of the user being unable to return to the previous interface due to the phone screen being on. This allows users to continue operating on the interface without needing to relaunch the application, thus improving the user experience.

[0191] In one implementation, the process of displaying a full-screen AOD interface using the aforementioned lock screen view intermediary class can be achieved through the handleSetOccluded() function.

[0192] It should be understood that the corresponding steps performed by each module in the aforementioned mobile phone can also be performed by other modules in the mobile phone. For example, the process of the full-screen AOD mediator class modifying the lock screen-side overlay attribute can also be modified by the lock screen view mediator class. Specifically, after the full-screen AOD mediator class calls the system-side overlay attribute, it can directly send the system-side overlay attribute to the lock screen view mediator class. Then, if the system-side overlay attribute is true, the lock screen-side overlay attribute is modified.

[0193] In some embodiments, this application provides a computer storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the method described above.

[0194] In some embodiments, this application provides a computer program product that, when run on an electronic device, causes the electronic device to perform the method described above.

[0195] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0196] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0197] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0198] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0199] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0200] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An AOD display method, characterized in that, This invention relates to an electronic device equipped with a full-screen always-on display (AOD) mode. The full-screen always-on display mode refers to the electronic device displaying a full-screen always-on display (AOD) interface when the screen is off. The electronic device includes a lock screen-side overlay state and a system-side overlay state. The lock screen-side overlay state indicates whether the electronic device switches to displaying the full-screen always-on display (AOD) interface. The system-side overlay state is used to characterize whether the electronic device detects the launch operation of an application with overlay function when the electronic device is in a screen-off state. The method includes: When the electronic device is in a screen-off state, if the system-side coverage state is a first value, the electronic device displays the user interface corresponding to the launched application; the system-side coverage state being a first value indicates that the electronic device has detected the launch operation of the launched application with coverage function. In response to the screen-off operation of the electronic device, the electronic device modifies the screen lock side coverage state. If the screen lock side coverage state is modified to a second value, the electronic device switches to displaying the full-screen always-on display (AOD) interface. The screen lock side coverage state being the second value indicates that the electronic device switches to displaying the full-screen always-on display (AOD) interface.

2. The method according to claim 1, characterized in that, When the electronic device is in a screen-off state, if the system-side coverage state is a first value, the electronic device displays a user interface corresponding to the launched application, including: When the electronic device is in a screen-off state, the electronic device updates the system-side overlay state; When the system-side coverage state is updated to the first value, the electronic device displays a user interface corresponding to the launched application.

3. The method according to claim 2, characterized in that, The method further includes: In response to the exit operation of the launched application, the electronic device updates the system-side overlay state; When the system-side coverage state is updated to the second value, the electronic device updates the lock screen-side coverage state to the second value and displays the full-screen always-on display (AOD) interface; wherein, the system-side coverage state being the second value indicates that the electronic device has detected the exit operation of the launched application.

4. The method according to any one of claims 1-3, characterized in that, When the electronic device is in a screen-off state, and the system-side overlay state is updated to a first value, the electronic device displays a user interface corresponding to the launched application, including: When the electronic device is in a screen-off state, in response to the launch operation of any application on the electronic device, and when the system-side overlay state is updated to a first value, the electronic device displays the user interface corresponding to the launched application; or, If the launch operation of any application in the electronic device is detected, and the electronic device is in a screen-off state, and the system-side overlay state is updated to a first value, the electronic device displays the user interface corresponding to the launched application.

5. The method according to any one of claims 1-3, characterized in that, After the electronic device switches to display the full-screen always-on display (AOD) interface, the method further includes: In response to the screen-on operation of the electronic device, the electronic device switches to display the user interface.

6. The method according to claim 5, characterized in that, In response to the screen-on operation of the electronic device, the electronic device displays the user interface, including: In response to the screen-on operation of the electronic device, if the system-side coverage state is a first value and the lock screen-side coverage state is a second value, the electronic device modifies the lock screen-side coverage state; When the screen lock state is modified to the first value, the electronic device switches to display the user interface; wherein, the screen lock state being the first value indicates that the electronic device exits the display of the full-screen always-on display (AOD) interface.

7. An electronic device, characterized in that, The electronic device includes a display screen, a memory, and one or more processors; the display screen, the memory, and the processors are coupled; the display screen is used to display a full-screen always-on display (AOD) interface or the user interface of a launched application; the memory is used to store computer program code, the computer program code including computer instructions; when the processor executes the computer instructions, the electronic device performs the method as described in any one of claims 1 to 6.

8. A computer-readable storage medium, characterized in that, Includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1 to 6.

9. A computer program product, characterized in that, Includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1 to 6.

Images